Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
That's exactly what the default thermostat in OpenStudio does. It is a ThermostatSetpoint:DualSetpoint.
If you put a heating schedule of 19°C and a cooling schedule of 26°C for example, heating will be on as required to heat up to 19°C. Conversely, the cooling will be on to cool down to 26°C. In between, what's called a "deadband", neither heating nor cooling is done.
| | 2 | No.2 Revision |
That's exactly what the default thermostat in OpenStudio does. It is a ThermostatSetpoint:DualSetpoint.
If you put a heating schedule of 19°C and a cooling schedule of 26°C for example, heating will be on as required to heat up to 19°C. Conversely, the cooling will be on to cool down to 26°C. In between, what's called a "deadband", neither heating nor cooling is done.
Like I said, this object takes two SCHEDULES, so it's easy to change the setpoints throughout the year.
| | 3 | No.3 Revision |
That's exactly what the default thermostat in OpenStudio does. It is a ThermostatSetpoint:DualSetpoint.
If you put a heating schedule of 19°C and a cooling schedule of 26°C for example, heating will be on as required to heat up to 19°C. Conversely, the cooling will be on to cool down to 26°C. In between, what's called a "deadband", neither heating nor cooling is done.
Like I said, this object takes two SCHEDULES, schedules, so it's easy to change the setpoints throughout the year.
