Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

How to set cooling setpoint below heating setpoint

I'm getting the following error:

DualSetPointWithDeadBand: Effective heating set-point higher than effective cooling set-point - increase deadband if using unmixed air model * ~~~ * occurs in Zone=LOUNGE During Warmup, Environment=RUNPERIOD1, at Simulation time=01/01 00:00 - 00:15 * ~~~ * LoadToHeatingSetPoint=556.391, LoadToCoolingSetPoint=430.434 * ~~~ * Zone TempDepZnLd=226.72 * ~~~ * Zone TempIndZnLd=4607.84 * ~~~ * Zone Heating ThermostatSetPoint=22.78 * ~~~ * Zone Cooling ThermostatSetPoint=22.22

I realise this is because the cooling setpoint is lower than the heating sepoint, but the setpoints are derived from real life data where occupants have indicated this is what they use IRL. I have set the schedules so that they are not active during the same period:

Schedule:Compact, heating_sched, Control, Through: 03/31, For: AllDays, Until: 24:00, 1, Through: 10/20, For: AllDays, Until: 24:00, 0, Through: 12/31, For: AllDays, Until: 24:00, 1;

Schedule:Compact, cooling_sched, Control, Through: 06/30, For: AllDays, Until: 24:00, 0, Through: 09/15, For:AllDays, Until: 24:00, 1, Through: 12/31, For: AllDays, Until: 24:00, 0;

Am I missing something?

How to set cooling setpoint below heating setpoint

I'm getting the following error:

DualSetPointWithDeadBand: Effective heating set-point higher than effective cooling set-point - increase deadband if using unmixed air model * ~~~ * occurs in Zone=LOUNGE During Warmup, Environment=RUNPERIOD1, at Simulation time=01/01 00:00 - 00:15 * ~~~ * LoadToHeatingSetPoint=556.391, LoadToCoolingSetPoint=430.434 * ~~~ * Zone TempDepZnLd=226.72 * ~~~ * Zone TempIndZnLd=4607.84 * ~~~ * Zone Heating ThermostatSetPoint=22.78 * ~~~ * Zone Cooling ThermostatSetPoint=22.22

I realise this is because the cooling setpoint is lower than the heating sepoint, but the setpoints are derived from real life data where occupants have indicated this is what they use IRL. I have set the schedules so that they are not active during the same period:

Schedule:Compact, heating_sched, Control, Through: 03/31, For: AllDays, Until: 24:00, 1, Through: 10/20, For: AllDays, Until: 24:00, 0, Through: 12/31, For: AllDays, Until: 24:00, 1;

Schedule:Compact, cooling_sched, Control, Through: 06/30, For: AllDays, Until: 24:00, 0, Through: 09/15, For:AllDays, Until: 24:00, 1, Through: 12/31, For: AllDays, Until: 24:00, 0;

Am I missing something?

How to set cooling setpoint below heating setpoint

I'm getting the following error:

DualSetPointWithDeadBand: Effective heating set-point higher than effective cooling set-point - increase deadband if using unmixed air model
 *   ~~~   * **   ~~~   ** occurs in Zone=LOUNGE During Warmup, Environment=RUNPERIOD1, at Simulation time=01/01 00:00 - 00:15
 *   ~~~   * **   ~~~   ** LoadToHeatingSetPoint=556.391, LoadToCoolingSetPoint=430.434
 *   ~~~   * **   ~~~   ** Zone TempDepZnLd=226.72
 *   ~~~   * **   ~~~   ** Zone TempIndZnLd=4607.84
 *   ~~~   * **   ~~~   ** Zone Heating ThermostatSetPoint=22.78
 *   ~~~   * **   ~~~   ** Zone Cooling ThermostatSetPoint=22.22

ThermostatSetPoint=22.22

I realise this is because the cooling setpoint is lower than the heating sepoint, but the setpoints are derived from real life data where occupants have indicated this is what they use IRL. I have set the schedules so that they are not active during the same period:

Schedule:Compact,
 heating_sched,
 Control,
 Through: 03/31,
    For: AllDays,
    For: AllDays,
Until: 24:00, 1,
 Through: 10/20,
    For: AllDays,
    For: AllDays,
Until: 24:00, 0,
 Through: 12/31,
    For: AllDays,
    Until: 24:00, 1;

For: AllDays, Until: 24:00, 1; Schedule:Compact, cooling_sched, Control, Through: 06/30, For: AllDays, For: AllDays, Until: 24:00, 0, Through: 09/15, For:AllDays, Until: 24:00, 1, Through: 12/31, For: AllDays, Until: 24:00, 0;

For: AllDays, Until: 24:00, 0;

Am I missing something? something?