|
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: | 4.1.006 BETA (8/23/99) Mark Gilmore Mon, 23 Aug 1999 14:32:26 -0700 |
http://www.usit.com/omnip/ecsb.zip (BETA) has been uploaded:
4.1.006 (08/23/99)
71) The TX15 and TX15-B X-10 thermostats are now directly supported
via new Types HVAC-INTERFACE-C and HVAC-INTERFACE-D.
* 72) The numeric PHONE-INTERFACE-D States have been replaced by names
(the "PHONE-INTERFACE-DX" custom Type is no longer required).
73) Per #38 above, a problem has been corrected which prevented the
CID info from being written to LMCID.TXT when PHONE-INTERFACE-D
was used.
74) So as to free-up the CPU for other programs, ECS now "sleeps"
when no activity is pending and it has not fallen behind by
more than 1 second. A timer is used to assure that Events
are executed at least 4 times/second.
75) Added new Item Type (ACTIVE-GROUP) to allow Events to display
different Groups in the Group Screen.
76) In order to GREATLY increase the speed of cfg saves (as well as
simplify the logic which does so), ECS now writes an entire new
ECS.CFG on each save (rather than "surgically" searching/parsing
the existing file). The only downside to this approach is that
comments OUTSIDE of Events and any custom indentation you use
within Events are no longer preserved.
77) A bug has been corrected which triggered an error msg if one
attempted to edit an IR-SIGNAL-K Item whose Signal# was > 128.
78) Corrected problem with learning IR-SIGNAL-K Items whose Signal#s
were > 80 (signal #'s >80 are NOT monitored by the CPU-XA).
The signals WERE learned when received by the CPU-XA, but ECS
did not notify the user.
* 79) The Event "engine" logic has been overhauled:
BEGINIF and WHILE statements may now be followed by additional
AND/OR conditional statements.
There is also a suttle difference in the way that the "IS NOW"
operator works: Previously, ECS would detect the transition to
the desired State if it had occured "since THIS Event was last
executed". Now, it will be detected if it has occurred since ALL
Events were last executed. Specifically, ECS saves the old States
of all Items, reads the current States, and executes all Events.
These old States are used in evaluating "IS NOW" conditions.
I doubt that this change will effect the execution of anyone's
Events, but I wanted you to know (just in case).
--
Mark Gilmore
Omnipotence (ECS home automation software)
http://www.usit.com/omnip
omnip@usit.net
423-745-0026
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects