ECS-L Home Automation and Security Archives
  learn more | view messages for this month | NetBloc® | terms of use | search

Google
 


  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects

Subject:
From:
Date:
Re: [ECS] Fw: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
joerut.epix.net
Thu, 28 Sep 2000 22:33:38 -0400

Kevin

I am using ECS with ACE and 10 Epson EHT-400C pen 
touchscreens linked VIA wired and wireless LAN. With the 
combination of ECS and ACE it seems like ANYTHING can be 
accomplished. I presently have My caller ID info pop up on ALL 
touchscreens for 30 seconds. When the phone line is sensed off-
hook the touchscreen selects a page in ACE that I have set up as 
a sort of quick dialing directory. From any touchscreen you just 
touch the person you want to call and ECS dials the phone #. I 
also have a page that displays ALL of my WEATHER MONITOR II 
data along with HIGHS and LOWS for the day. I can go on and on 
for ever about my setup and how great these two programs work 
together. I picked up the touchscreens pretty cheap (about $100 
each) and had to add some extras that probally brought the cost 
for each touchscreen to about $200.00. I am not sure how that 
compares to the Leopard. If you would like any more info let me 
know.

Later 
Joe Rut




On 28 Sep 2000, at 11:11, Kevin Trainor wrote:

> Nathan:
> 
> Thanks for sharing you experience with the Leopard.  I have been thinking
> seriously of using the Leopard for my home automation consoles.  My main
> reservation has been that I don't see a way to display text messages on the
> Leopard.  Like you, I would like to display temperature, caller-id, etc.
> Also, I would like to be able to carry on a dialog with the user with a
> combination of text displays and buttons.  If you discover a way to do this
> on the Leopard, please let me know.  If I can find a way to address that
> requirement, the Leopard would be the ideal device for me.
> 
> Thanks.
> 
> Kevin
> ----- Original Message -----
> From: "Nathan Brown" <nbrown@thystonius.com>
> To: <ecs-list@netbloc.com>
> Sent: Thursday, September 28, 2000 10:55 AM
> Subject: RE: [ECS] Fw: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> 
> 
> Tom,
> No worries about the questions.  Writting this down helps me
> clarify it in my head.  The Leopards are connected to the ADNET bus and
> are slaves to the master Ocelot.  But they can still have their own
> programs.  The limitation is that the code run on the Leopards can't
> talk to the other modules.  Here is an example:
> Local Leopard:
> If Touchbutton 15 on self is Pressed Then Set Variable 63=5    'Goto
> screen 5
> If Touchbutton 25 on self is Pressed Then Send X10 A12 ON      'Turn
> Hall Light on
> If Receive IR 34 then Send X10 F10 ON  'Activate F10 sequence
> 
> Master Ocelot:
> If Touchbutton 26 on unit 4 is Pressed then close relay 4 on unit 2
> 'Turn on something
> 
> ECS:
> In this situation ECS "should" be able to recieve all the button presses
> on every touchscreen.  With this you could do anything from any button.
> 
> Wishlist:
> +All this to work
> +I haven't found a way to display configurable text messages (such as
> caller id information for message playback).
> 
> Are you planning to use the Bobcat devices (which ones)?  I haven't
> found a good way, for the reason above, to use other temp sensors and
> display that info on the touchscreens.
> 
> Lets keep this conversations going,
> Nathan
> 
> -----Original Message-----
> From: hutchins.ta@pg.com [mailto:hutchins.ta@pg.com]
> Sent: Thursday, September 28, 2000 5:01 AM
> To: ecs-list@netbloc.com
> Subject: RE: [ECS] Fw: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> 
> 
> 
> Nathan,
> 
> Sounds interesting. Let me see if I got this straight. You're using an
> OCELOT as
> the main interface to ECS and the house. Have multiple LEOPARDS
> throughout the
> house that are not connected to the OCELOT via the ADNET bus? Each of
> the
> LEOPARDS have their own programming for their touchscreens and for
> 'local' use
> such as room lights ect. Do they interact with each other? How? What are
> you
> using ECS to accomplish?
> 
> Sorry for all the questions, but I'm curious. Sounds like a robust
> system, even
> if one part goes down the rest still works.
> 
> Unfortunately, I was lucky to get a single Leopard with SECU16I and
> SECU16IR
> past the wife (mostly due to touchscreen - she understands the benfit of
> that!)
> and chances of getting an OCELOT are slim to none, so I need to maximize
> my bang
> for the buck using PC / ECS and a single LEOPARD!!
> 
> Tom
> 
> 
> 
> 
> From: "Nathan Brown" <nbrown@thystonius.com> on 09/28/2000 01:54 AM
> 
> Please respond to ecs-list@netbloc.com
> 
> To:   <ecs-list@netbloc.com>
> cc:    (bcc: Thomas Hutchins-TA/PGI)
> Subject:  RE: [ECS] Fw: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> 
> 
> One reason to have an ocelot is to be able to ditrubute the processing
> across multiple devices.  In my setup I have programs in each Leopard
> that deal with button processes and several "station" level commands and
> X10 transmission.  The central Ocelot then doesn't have to be programmed
> to deal with all button presses, it only has to deal with ones that
> affect other modules.  Also, my Leopards are not located where I want to
> run a serial cable back to the computer.
> This configuration utilizes the "smarts".
> 
> Nathan
> 
> -----Original Message-----
> From: Tom Hutchins [mailto:thutchins@cinci.rr.com]
> Sent: Wednesday, September 27, 2000 5:48 PM
> To: ecs-list@netbloc.com
> Subject: [ECS] Fw: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> 
> 
> One other thing, on the CPUXA list the current threads indicate that if
> you
> are setting up a new install and want to have the LEOPARD then there is
> no
> reason to have an OCELOT unless you want an additional IR reciever point
> in
> a separate room from the LEOPARD(basically the internal smarts of the
> extra
> OCELOT would be wasted).
>  Hope that helps.
> 
> Tom
> ----- Original Message -----
> From: "Tom Hutchins" <thutchins@cinci.rr.com>
> To: <ecs-list@netbloc.com>
> Sent: Wednesday, September 27, 2000 8:41 PM
> Subject: Re: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> 
> 
> > Mark,
> >
> > Sorry about that. I "assumed" that we were on the same page. My
> > understanding from the CPUXA list is that the Leopard is simply an
> OCELOT
> > with a touch screen. You use the same CMAX software for both and there
> is
> no
> > "special" coding for the Leopard other than for the touchscreen.
> >
> > Tom
> > ----- Original Message -----
> > From: "Mark Gilmore" <omnip@usit.net>
> > To: <ecs-list@netbloc.com>
> > Sent: Wednesday, September 27, 2000 7:05 PM
> > Subject: Re: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> >
> >
> > > Yes - this is CRITICAL information.
> > > I don't know if this will work at all,
> > > as this is not a supported configuration.
> > > And I know it won't work unless the Leopard
> > > acts exactly like the Ocelot.
> > > --
> > > Mark Gilmore
> > > Omnipotence (ECS home automation software)
> > > http://omnipotencesoftware.com
> > > 423-745-0026
> > > Hours: Mon-Sat, 9AM-8PM/EST
> > >
> > >
> > > Tom Hutchins wrote:
> > > >
> > > > Mark,
> > > >
> > > > There is no OCELOT. The Leopard is acting as the OCELOT as well as
> the
> > > > touchscreen, (has the touchscreen interface with the guts of the
> OCELOT)
> > and
> > > > the Leopard is the only thing attached to the computer!
> > > >
> > > > Does that help?
> > > >
> > > > Tom
> > > > ----- Original Message -----
> > > > From: "Mark Gilmore" <omnip@usit.net>
> > > > To: <ecs-list@netbloc.com>
> > > > Sent: Wednesday, September 27, 2000 6:51 PM
> > > > Subject: Re: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> > > >
> > > > > Tom,
> > > > > Do you have any OTHER kinds of modules ?
> > > > > Perhaps your Ocelot firmware is too old
> > > > > to recognize the Leopard (??).
> > > > > --
> > > > > Mark Gilmore
> > > > > Omnipotence (ECS home automation software)
> > > > > http://omnipotencesoftware.com
> > > > > 423-745-0026
> > > > > Hours: Mon-Sat, 9AM-8PM/EST
> > > > >
> > > > >
> > > > > Tom Hutchins wrote:
> > > > > >
> > > > > > Bob,
> > > > > >
> > > > > > I have the Leopard working fine using CMAX. However, CMAX
> doesn't
> > have
> > > > near
> > > > > > the ease of use as ECS. I don't have any other modules hooked
> up
> yet
> > as
> > > > I
> > > > > > prefer to make sure each thing is working properly before I
> add
> the
> > next
> > > > > > item. Sure makes troubleshooting easier.
> > > > > >
> > > > > > Tom
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: <bob.terfruchte@amd.com>
> > > > > > To: <ecs-list@netbloc.com>
> > > > > > Sent: Wednesday, September 27, 2000 6:34 PM
> > > > > > Subject: RE: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> > > > > >
> > > > > > > Tom,
> > > > > > >
> > > > > > > Can you "find" the modules with the C-Max software from
> ADI??
> > > > > > >
> > > > > > > Bob Terfruchte, Jr.
> > > > > > > Austin, TX
> > > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Mark Gilmore [mailto:omnip@usit.net]
> > > > > > > Sent: Wednesday, September 27, 2000 5:29 PM
> > > > > > > To: ecs-list@netbloc.com
> > > > > > > Subject: Re: [ECS] [Fwd: [ECS] AD "Bobcat" Modules]
> > > > > > >
> > > > > > >
> > > > > > > Tom,
> > > > > > > As I suspected, your dump shows that the OCELOT is
> > > > > > > reporting NO modules of any kind. You might want to
> > > > > > > call ADI on this (the 254's signify "no module"):
> > > > > > >
> > > > > > > Transmit ("get unit types" command):
> > > > > > > 42 0 0 1 176 0 148 39
> > > > > > >
> > > > > > > Received:              1st 2nd 3rd ...
> > > > > > > 42 0 0 1 176 0 254 254 254 254 254 254 254 254 254 254 254
> 254
> > > > > > > 254 254 254 254 254 254 254 254 254 254 254 254 254 254 254
> 254
> > > > > > > ....
> > > > > > > --
> > > > > > > Mark Gilmore
> > > > > > > Omnipotence (ECS home automation software)
> > > > > > > http://omnipotencesoftware.com
> > > > > > > 423-745-0026
> > > > > > > Hours: Mon-Sat, 9AM-8PM/EST
> >
> 
> 
> 
> 
> 
> 
> 
> 
> 



  subject (prev) or (next) | time (prev) or (next) | author (prev) or (next) | view more subjects




Services provided by [NetBloc]®! NetBloc Solutions Inc.
Terms of use. Indexing software (c) 1999 Lin-De, Inc
.