Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
In my understanding, Temperature Difference Between Cutout And Setpoint is implemented by changing thermostat setpoints, eg. for heating if the setpoint is 70F and the difference is 2F, it changes the thermostat setpoint to be 72F when HVAC is operating, then back to 70F when zone temperature reaches cutout temperature.
You can output these two variables to see its behaviors: Output:Variable,,Zone Thermostat Heating Setpoint Temperature,hourly; !- HVAC Average [C] Output:Variable,,Zone Thermostat Cooling Setpoint Temperature,hourly; !- HVAC Average [C]
Due to this implementation, my guess is that the unmet hour is calculated based on the thermostat setpoint temperatures which didn't consider deadband operations, and that's why "The thermostat setpoint not met hours are incorrect with this option." is called out. Hope this helps.
| | 2 | No.2 Revision |
In my understanding, Temperature Difference Between Cutout And Setpoint Setpoint is implemented by changing thermostat setpoints, eg. for heating if the setpoint is 70F and the difference is 2F, it changes the thermostat setpoint to be 72F when HVAC is operating, then back to 70F when zone temperature reaches cutout temperature.
You can output these two variables to see its behaviors:
behaviors:
Output:Variable,,Zone
ThermostatThermostat Heating SetpointTemperature,hourly;Temperature,hourly; !- HVAC Average [C] Output:Variable,,ZoneThermostatThermostat Cooling SetpointTemperature,hourly;Temperature,hourly; !- HVAC Average [C]
Due to this implementation, my guess is that the unmet hour is calculated based on the thermostat setpoint temperatures which didn't consider deadband operations, and that's why "The thermostat setpoint not met hours are incorrect with this option." is called out. Hope this helps.
