Question-and-Answer Resource for the Building Energy Modeling Community
Get s tarted with the Help page

Revision history [back]

EMS Heating and Cooling setpoint actuators control Air temperature instead of Operative temperature

Hi Everyone,

I'm working on a script for heating or cooling setpoint temperatures. I need it to be portable to other models, so i'm trying to make it work with loops. The problem is that, although the temperature control calculation option is set to Operative Temperature, the EMS controls the Air temperature.

The script i'm using is quite simple:

<ForAllOccupiedZones>
EnergyManagementSystem:Actuator,
<LoopZoneVariableName>_FORSCRIPT_ACST_Schedule,
<LoopZoneIDFName>,
Zone Temperature Control,
Cooling Setpoint;
<LoopNextZone>

<ForAllOccupiedZones>
EnergyManagementSystem:Actuator,
<LoopZoneVariableName>_FORSCRIPT_AHST_Schedule,
<LoopZoneIDFName>,
Zone Temperature Control,
Heating Setpoint;
<LoopNextZone>

EnergyManagementSystem:ProgramCallingManager,
ApplyAST,
BeginTimestepBeforePredictor,
ApplyAST;

EnergyManagementSystem:Program,
ApplyAST,
<ForAllOccupiedZones>
Set <LoopZoneVariableName>_FORSCRIPT_ACST_Schedule = 26,
Set <LoopZoneVariableName>_FORSCRIPT_AHST_Schedule = 23;
<LoopNextZone>


This is a screenshot of the results, that show that Zone Air Temperature (instead of Operative Temperature) is 26°C. The Cooling setpoint is the blue line, but it's behind the zone air temperature and can not be seen. Does anyone know why is this happening?