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] Question About Light Control Using ECS
joerut.epix.net
Tue, 29 Aug 2000 16:14:29 -0400

Kevin

You will notice the command "IS NOW" in those events means it 
only happens ONCE in the scan when the ITEM state CHANGES. 

ex. If 		Time 			IS NOW 		10:00PM

This means this Statement is TRUE only at the TRANSITION from 
9:59PM to 10:00PM.

Hope this helps
Joe Rut 



On 29 Aug 2000, at 13:53, Kevin Trainor wrote:

> I have downloaded a trial copy of ECS.  As a proof of concept, I am trying to duplicate
the light control system that I am currently using that is based upon the CM11A and
ActiveHome.  When I look at the default light control event coding that installs with
ECS, I am a bit confused about how it 
works.  The "Outside Lights" and "Inside Lights" events both appear to send an ON command
or an OFF command to their respective list of lights on every ECS pass.  I'm wondering
if this is standard coding practice for light control or not.  Does this cause a steady
stream of commands to be sent to 
the PLC interface?  Or, are they intercepted somewhere and not transmitted because they
are redundant?
> 
> With my current CM11A/ActiveHome setup, I find that I often need to code repetitive
ON commands in order to make sure that certain lights in my house do indeed turn on.
 Is this coding technique simply an elegant way of dealing with that problem?  If so,
doesn't this techniqe pollute the 
circuit with a lot of unnecessary commands?
> 
> Thanks in advance for your help.  I know that this is a simple matter.  But, I am
just not figuring it out on my own.
> 
> Kevin
> 



  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
.