Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Schedules can be "actuated" based on "sensor" values from other schedules using the EMS programming language.
| | 2 | No.2 Revision |
Schedules can be "actuated" based on "sensor" values from other schedules using the EMS programming language.language. Take a look at the EMS Application guide documentation.
| | 3 | No.3 Revision |
Schedules can be "actuated" based on "sensor" values from other schedules using the EMS programming language. Take a look at the EMS Application guide documentation.documentation:
Schedule Sensors:
The EnergyManagementSystem:Sensor object can also provide scheduled data for use in Erl programs. Because schedule values are available as outputs that use the “Schedule Value” output, they can also be mapped as sensors. You can use any of the various types of schedule input objects to define a schedule. The schedule does not need to be used elsewhere in the model. The value of the schedule is then mapped to an EMS variable with the Schedule Value report variable. When used with the Schedule:File input object, the sensor object can import time series data into the EMS from an external file. One application might be to test a proposed EMS algorithm with real experimental data.
Schedule Actuators:
A series of actuators is available for overriding schedule values. The following actuators are available with the control type called “Schedule Value”: Schedule:Year, Schedule:Compact, Schedule:File, and Schedule:Constant. The units are not known by the schedule and are determined by the model that references the schedule. The unique identifier is the name of schedule.
If you try to use a particular schedule as input to calculations that modify that schedule, you will be in a circular situation with unexpected results. The modified schedule will lose the original information (unless the actuator is set to Null) and the modifications will be reapplied on top of previous modifications. When this situation arises, use a copy of the original schedule as input to the Erl program so you have the original schedule values.
| | 4 | No.4 Revision |
Schedules You can be "actuated" create a EMS program to set an "actuator" schedule value based on a "sensor" values from other schedules using the EMS programming language. schedule value. This will happen dynamically during simulation runtime.
Take a look at the EMS Application guide documentation:
Schedule Sensors:
The EnergyManagementSystem:Sensor object can also provide scheduled data for use in Erl programs. Because schedule values are available as outputs that use the “Schedule Value” output, they can also be mapped as sensors. You can use any of the various types of schedule input objects to define a schedule. The schedule does not need to be used elsewhere in the model. The value of the schedule is then mapped to an EMS variable with the Schedule Value report variable. When used with the Schedule:File input object, the sensor object can import time series data into the EMS from an external file. One application might be to test a proposed EMS algorithm with real experimental data.
Schedule Actuators:
A series of actuators is available for overriding schedule values. The following actuators are available with the control type called “Schedule Value”: Schedule:Year, Schedule:Compact, Schedule:File, and Schedule:Constant. The units are not known by the schedule and are determined by the model that references the schedule. The unique identifier is the name of schedule.
If you try to use a particular schedule as input to calculations that modify that schedule, you will be in a circular situation with unexpected results. The modified schedule will lose the original information (unless the actuator is set to Null) and the modifications will be reapplied on top of previous modifications. When this situation arises, use a copy of the original schedule as input to the Erl program so you have the original schedule values.
