| ECS-L Home Automation and Security Archives |
| Subject: From: Date: | Re: [ECS] Leopard Tom Hutchins Sun, 8 Oct 2000 20:56:35 -0400 |
Bill, Thanks for the input. I have been working this with Mark directly offlist, and one of the things we did was to create the very simple CFG file as you suggested. That helped enormously. The problem is just about wrapped up, and I'm sure there will be an update soon since Mark is so good at keeping the program current. Thanks again, Tom ----- Original Message ----- From: "Bill Walters" <wtwalters@earthlink.net> To: <ecs-list@netbloc.com> Sent: Friday, October 06, 2000 12:59 AM Subject: Re: [ECS] Leopard > <sorry, sent message too soon> > > Or, write VERY simple CFG file with only touchscreen-k type device and your > sample event w/basement light... Turn Debug on and try a few presses on > your Leapord touchscreen. Then turn debug off and examine the contents of > your dbg file (to see what, if anything, the touchscreen-k type item was > "transmitting"). > > As I mentioned, I used the LOG file capability to capture various > states/conditions of the Napco panel when I first interfaced it to ECS. You > have to know what ECS is actually capturing from your interface in order to > be able to test it. Mark is absolutely marvelous at integrating something > via only the "specs" but then doesn't really know how it behaves as he never > has hands on a unit (unless someone sends him one for testing)... This by > the way, is NOT a criticism, but a compliment to his prowess of getting > things to work without ever having his hands on them! It means a little > more work for us when we begin using a newly integrated device, but the > alternative is non-support, which none of us want... > > Thanks MARK for everything you do for us! > > Bill Walters > > ----- Original Message ----- > From: "Tom Hutchins" <thutchins@cinci.rr.com> > To: <ecs-list@netbloc.com> > Sent: Thursday, October 05, 2000 5:47 PM > Subject: Re: [ECS] Leopard > > > > Mark, > > > > Had a few minutes so I tried it out. > > Now I'm able to set up the TOUCHSCREEN-K item with no error message! > > Unfortunately, I don't seem to be able to get it to work right. > > > > Here's what I got > > Leopard is set up with multiple screens and loaded via CMAX... no actions, > > just buttons that take you from screen to screen and then some buttons for > > lights. > > > > Example : Basement light (object #33) > > > > In ECS I have TOUCHSCREEN-K set up as TOUCHSCREEN-K type and MAIN as > unit#. > > Basement Light set up as H1(works when tested directly from ECS) > > > > Then I have an event: > > > > IF TOUCHSCREEN-K is now 33 > > And Basement light is OFF > > Then Basement light set ON > > > > IF TOUCHSCREEN-K is now 33 > > And Basement light is ON > > Then Basement light set OFF > > > > I think that this should work? > > Anyway nothing happens. I also added TOUCHSCREEN-K item to my ECS group > > screen and then touch the Leopard buttons and it's state never changes > from > > "idle" > > > > Ant ideas? > > > > Thanks, > > > > Tom > > ----- Original Message ----- > > From: "Mark Gilmore" <omnip@usit.net> > > To: <ecs-list@netbloc.com> > > Sent: Thursday, October 05, 2000 5:26 PM > > Subject: [ECS] Leopard > > > > > > > Hi all, > > > Wasn't someone out there going to test the new beta > > > with the Leopard acting AS the Ocelot ???? > > > Whomever want's best test it now, or I'll forget it > > > (it's REALLY tough to diagnose code many days after I added it). > > > Thanks, > > > -- > > > Mark Gilmore > > > Omnipotence (ECS home automation software) > > > http://omnipotencesoftware.com > > > 423-745-0026 > > > Hours: Mon-Sat, 9AM-8PM/EST > > > > >