Medium Office ClgSetp Winter Design Day has no setback. Only setPt will be changed.
Medium Office ClgSetp Rule 1 Day Schedule has no setback. Only setPt will be changed.
Medium Office ClgSetp Winter Design Day has no setback. Only setPt will be changed.
Medium Office HtgSetp Summer Design Day has no setback. Only setPt will be changed.
Medium Office HtgSetp Winter Design Day has no setback. Only setPt will be changed.
Medium Office HtgSetp Rule 1 Day Schedule has no setback. Only setPt will be changed.
Medium Office HtgSetp Summer Design Day has no setback. Only setPt will be changed.
Medium Office HtgSetp Winter Design Day has no setback. Only setPt will be changed.
If I apply a schedule like so, do I need to supply zone Setpoint/Setback then? And what will happen if I will leave that empty, will it just use the supplied Cooling/Heating setpoint schedule?
I was trying first to model it by using Setpoints/Setbacks, eg for spaces that are Heated only, the setbacks for cooling will be 99, and so on. But I run into a problem that not every building program supports setbacks.
So I decided to create schedules that are mimicking the setbacks. (Null schedules):
But this approach is very odd, and creates lots of errors, like:
Convergence error in SolveForWindowTemperatures for window
or
DualSetPointWithDeadBand: Effective heating set-point higher than effective cooling set-point - increase deadband if using unmixed air model
So I am not sure that I am doing it correctly.
I am reading UnmetHours forum, but cannot find a solution to this…
What would be a clever solution to model “partially conditioned” thermal zones?