|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | Re: [ECS] Timer problem Bruce Prager Fri, 22 Oct 1999 16:37:42 -0400 |
mark, I can see it not setting the timer at all. But how does IS vs. IS NOW
result in a wrong timer value?
-----Original Message-----
From: Mark Gilmore <omnip@usit.net>
To: ecs-list@netbloc.com <ecs-list@netbloc.com>
Date: Friday, October 22, 1999 6:34 AM
Subject: Re: [ECS] Timer problem
>Hi Bruce,
>The problem below is your use of "IS NOW" (instead of "IS").
>--
>Mark Gilmore
>Omnipotence (ECS home automation software)
>http://www.usit.com/omnip
>423-745-0026
>
>
>Bruce Prager wrote:
>>
>> Mark , the following event works fine EXCEPT
>> First time the timer code runs, I get a value set in ECS of 101
>> Any subsquent times the code fires while the timer > 0, it resets to 120
as
>> indicated by the code.
>> Once the timer reaches 0, the next time the timer is set, it again only
>> goes to 101.
>>
>> Any ideas?
>>
>> If Porch IR Sensor Is Now On
>> Or Driveway IR Sensor Is Now On
>> Or Driveway Mag Sensor Is Now On
>> Then Logical 1 Set True
>> Else Logical 1 Set False
>> ; Motion detected in Front yard. If nighttime, set the timer
>> BEGINIF Daytime Is False
>> And Logical 1 Is Now True
>> Do Front Lights Timer Set 120
>> ; If the lights are off, turn them on. The timer will
>> ; automatically turn them off
>> If Front-Yard Lights Is Off
>> Then Front-Yard Lights Set On
>> ENDIF
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects