Subject: From: Date:

Re: [ECS] Problem using Type Touchscreen-K Bill Walters Tue, 12 Dec 2000 15:36:51 -0600

---

Kevin,

Just getting started with Leopard touchscreen & ECS.  Have ECS&Ocelot combo
that works flawlessly.  However, even with that caveat, I think (again, my
opinion only..) that running separate "navigation" program in Leopard while
integrated to ECS is recipe for pulling your hair out strand by strand....

So far (testing only) I run EVERYTHING with ECS as far as the Leopard
goes...  I have "minimal" X-10 stuff running as a constant within Ocelot, so
Ocelot is the "master".  I've not yet had time to hook up the Leopard via
the RS-485 to Ocelot, which is linked to ECS.....  Testing only with rs-232
directly to ECS.

Yes, response could be 'quicker' but all in all, think it will be OK; will
know more with RS-485 connection established.....  For my use, I want
Leopard clearly to be interface/connection to/from ECS.

Bill Walters

----- Original Message -----
From: Kevin Trainor <kevin@thetrainors.com>
To: <ecs-list@netbloc.com>
Sent: Tuesday, December 12, 2000 8:51 AM
Subject: Re: [ECS] Problem using Type Touchscreen-K


> Mark:
>
> 2.  My three lines of code in the Leopard were the only ones that I have
> ever written.  So, I may easily have made a mistake.
>
> 3.  Do you think that most people are doing screen-to-screen navigation on
> the Leopard using direct ECS control.  I would imagine that if you used
> Ocelot/Leopard code to control navigation that it would be a bit quicker
and
> give the user a crisper response.  On the other hand, if you can't mix the
> two modes of navigation, then, it is probably just another novel recipe
for
> disaster.  What do you think that most ECS Leopard users are doing on this
> issue?
>
> Kevin
> ----- Original Message -----
> From: "Mark Gilmore" <omnip@usit.net>
> To: <ecs-list@netbloc.com>
> Sent: Tuesday, December 12, 2000 8:27 AM
> Subject: Re: [ECS] Problem using Type Touchscreen-K
>
>
> > Kevin,
> > Are we saying that the LEOPARD will not respond to
> > an ECS command(s) if it has it's own programming ?
> > Sounds like a problem for ADI.
> > BTW, you did not state if ECS was reporting an error message.
> > --
> > Mark Gilmore
> > Omnipotence (ECS home automation software)
> > http://omnipotencesoftware.com
> > 423-745-0026
> > Hours: Mon-Sat, 9AM-8PM/EST
> >
> >
> > > Kevin Trainor wrote:
> > >
> > > I am pleased to say that I solved that problem by deleting the minimal
> > > amount of event code that I had put into the Leopard.  Now, I seem to
> > > have full control of the Leopard from ECS.
> > >
> > > The small amount of event code that I originally loaded into the
> > > Leopard was to get the Leopard to bring up Screen 1 whenever it
> > > powered up.  Now, I am directing the Leopard to Screen1 via ECS
> > > command in my Startup event.  Has anyone had luck in using native
> > > Leopard/Ocelot code to control the default screen on the Leopard while
> > > doing the rest of the navigation with commands from ECS?
> > >
> > > Kevin
> > >
> > >      ----- Original Message -----
> > >      From: Kevin Trainor
> > >      To: ecs-list@netbloc.com
> > >      Sent: Monday, December 11, 2000 9:44 PM
> > >      Subject: [ECS] Problem using Type Touchscreen-K
> > >
> > >      All:
> > >
> > >      I am using ECS Version 4.4.013.
> > >
> > >      I just got a Leopard and I'm trying to interact with it via
> > >      the Touchscreen-K type.
> > >
> > >      I seem to be able to sense button presses on the Leopard
> > >      quite well when I test the state of the relevant item.
> > >
> > >      However, I don't seem to be able to get the Leopard to
> > >      switch to another screen by setting the item to the screen
> > >      number.
> > >
> > >      Can anyone think of what I might be doing wrong?
> > >
> > >      Thanks.
> > >
> > >      Kevin
> >
>
>

---