| ECS-L Home Automation and Security Archives |
| Subject: From: Date: | RE: [ECS] Anyone using multiple Leopards? Nathan Brown Wed, 13 Dec 2000 11:18:37 -0800 |
Kevin, From what I've seen on the Adicon user list it seems like the advanced features of the Leopard (such as displaying text) can only be accessed from the rs232 interface and not the adicon network. This would mean that you would need to run a serial line to each Leopard and have enough ports on your PC to handle it. This would mean that you wouldn't need put the leopards on the adicon net at all, unless you wanted to. Then you would setup an Ocelot device for each one of your Leopards. Then the key would be to ensure that each Touchscreen device would know what Leopard to go to. I don't know how complex this would make the event logic. It would be nice to find a way that would allow you to setup the events that wouldn't need to get duplicated for each Leopard you want to install. Instead they would reference which ever one they needed. I don't have ECS in front of me, and I'm starting to confuse myself. I need to tell my client that I need to leave a few days early and play with my HA stuff. Nathan -----Original Message----- From: Kevin Trainor Sent: Wed 12/13/2000 10:30 AM To: ecs-list@netbloc.com Cc: Subject: Re: [ECS] Anyone using multiple Leopards? Nathan: I do not have more than one Leopard yet. I would be willling to buy a second one if I saw the support for it. As to the design, I know that the internal Leopard event code seems to recognize a module number & button number combination. I assume that module number refers to multiple Leopards. So, this would seem to support what we want to do. I don't see support in Mark's interface. Also, I don't know if this is supported through the serial interface at all. Then, there is the matter of screen switching. I know this is done in internal Leopard code by changing the value of Paramater #63. I can't recall if there is support for doing it on another unit. Again, I don't know if this is supported through the serial interface. From an architectural point of view, it would seem simplest to treat the entire network of leopards as one device. Then instead of just sensing a button press, you would sense a leopard number & button press combination. Likewise, when switching screens or writing text, you would specify the leopard number. Any multithreading would have to be done in your ECS application logic. Since most of the keypresses in my application will be stand-alone events, I won't have much need to remember where I am in a dialog. The exception to this would be something like getting a password sequence from a screen set up as a keypad. It might get challenging to keep track of more than one password dialog at the same time. Well. Those are my thoughts. What about yours. Kevin ----- Original Message ----- From: "Nathan Brown" <nbrown@thystonius.com> To: <ecs-list@netbloc.com> Sent: Wednesday, December 13, 2000 10:59 AM Subject: RE: [ECS] Anyone using multiple Leopards? > Kevin, > I am interested in this also. Do you have two Leopards to test with? I > haven't gone that far yet, but I am very interested in doing so. How do > you think it should be implemented in ECS? If we can pull together a > clear design then we could pass that on to Mark. > > Nathan > > -----Original Message----- > From: Kevin Trainor > Sent: Wed 12/13/2000 8:10 AM > To: ecs-list@netbloc.com > Cc: > Subject: [ECS] Anyone using multiple Leopards? > > > > All: > > Are any of you using multiple Leopards? On first examination, I > can't see how to set up the items in ECS to make that work. I am > thinking of using these units as home automation consoles. So, I would > like to be able to handle more than one at the same time. Any ideas? > > Kevin > >