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:
HBAC-Interface-B and ECS 4.1.010
Bill Walters
Mon, 20 Sep 1999 19:08:16 -0500
Mon, 20 Sep 1999 19:08:16 -0500
All,

OK, I'm sure that I'm going to "kick" myself on this later for asking such a foolish
question, but here goes....

I've installed 4.1.010 and having a problem with my RC-80 thermostat control stuff...

I  Created several events which controlled the RC-80 thermostat (HVAC-Interface-B) and
they worked OK in 4.1.04....  sometimes serial input would "stutter" and ECS would be
unable to read the stat, so I thought changing to 4.1.010 might, just might help that,
since some of the serial COM/IO buffer stuff had been changed........

OK.....  Now to my question....

To account for someone changing the thermostat at the thermostat itself, I wrote an
event to "Read" the thermostat settings every 30 minutes.  I then compared the ACTUAL
thermostat Cool setpoint to the setpoint I wanted, which was defined in ECS by a state-holder,
with a sub type of HVAC-Setting-B.  If the actual setpoint was different than ECS desired
setpoint, then I issued a change to the actual setpoint.

Here's a "snippet" of code:\

|Item:UPS Cool CMD       Type:State-Holder       Acc:User/User
|      Initial State:78                                           Backup:No
|      Sub-Type:HVAC-Setting-B
|Item:UPS Heat CMD       Type:State-Holder       Acc:User/User
|      Initial State:60
|      Sub-Type:HVAC-Setting-B

If I want to change the temp from within ECS, I set the new temp I desire to UPS Cool
CMD or UPS Heat CMD (whichever appropriate), then set a flag to tell system temps settings
are altered.  A second event looks for the "altered" flag, or a 30 minute timer.  If
either true, it reads in the stat values, and compares them against my CMD values (all
contained in State-Holder types)... If the stat values are different from the CMD values,
ECS resets the stat to the CMD values.  This way, I have control whether I'm actually
changing the temp from ECS or resetting a desired temp, due to someone altering the
setting of the stat.  

Anyway, it all worked ok in ECS 4.1.040...

What I'm now seeing, is that ECS tells me there is an error with the defined value of
any of my "state-holder" items....  

Here's the error message from within ECS:
4:20:52: ERROR:Value 111 is not a valid selection (Item "UPS Heat CMD") (GRP ITM DLG
PRC)

4:20:54: ERROR:Value 131 is not a valid selection (Item "UPS Cool CMD") (GRP ITM DLG
PRC)



You can see the defined values for both items....  Why is this error message coming
up?  Has something changed that I'm not seeing or is this an error within ECS 4.1.010?

Again......event works fine  from ECS 4.1.04

Any ideas?

Bill Walters





All,
 
OK, I'm sure that I'm going to "kick" myself on this later for asking such a foolish question, but here goes....
 
I've installed 4.1.010 and having a problem with my RC-80 thermostat control stuff...
 
I  Created several events which controlled the RC-80 thermostat (HVAC-Interface-B) and they worked OK in 4.1.04....  sometimes serial input would "stutter" and ECS would be unable to read the stat, so I thought changing to 4.1.010 might, just might help that, since some of the serial COM/IO buffer stuff had been changed........
 
OK.....  Now to my question....
 
To account for someone changing the thermostat at the thermostat itself, I wrote an event to "Read" the thermostat settings every 30 minutes.  I then compared the ACTUAL thermostat Cool setpoint to the setpoint I wanted, which was defined in ECS by a state-holder, with a sub type of HVAC-Setting-B.  If the actual setpoint was different than ECS desired setpoint, then I issued a change to the actual setpoint.
 
Here's a "snippet" of code:\
 
|Item:UPS Cool CMD       Type:State-Holder       Acc:User/User
|      Initial State:78                                           Backup:No
|      Sub-Type:HVAC-Setting-B
|Item:UPS Heat CMD       Type:State-Holder       Acc:User/User
|      Initial State:60
|      Sub-Type:HVAC-Setting-B
 
If I want to change the temp from within ECS, I set the new temp I desire to UPS Cool CMD or UPS Heat CMD (whichever appropriate), then set a flag to tell system temps settings are altered.  A second event looks for the "altered" flag, or a 30 minute timer.  If either true, it reads in the stat values, and compares them against my CMD values (all contained in State-Holder types)... If the stat values are different from the CMD values, ECS resets the stat to the CMD values.  This way, I have control whether I'm actually changing the temp from ECS or resetting a desired temp, due to someone altering the setting of the stat. 
 
Anyway, it all worked ok in ECS 4.1.040...
 
What I'm now seeing, is that ECS tells me there is an error with the defined value of any of my "state-holder" items.... 
 
Here's the error message from within ECS:

4:20:52: ERROR:Value 111 is not a valid selection (Item "UPS Heat CMD") (GRP ITM DLG PRC)

4:20:54: ERROR:Value 131 is not a valid selection (Item "UPS Cool CMD") (GRP ITM DLG PRC)

 

You can see the defined values for both items....  Why is this error message coming up?  Has something changed that I'm not seeing or is this an error within ECS 4.1.010?

Again......event works fine  from ECS 4.1.04

Any ideas?

Bill Walters

 


  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
.