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

E+ code for CIBSE TM52 comfort assessment

asked 2017-03-21 11:08:26 -0600

andrea.botti's avatar

updated 2017-03-21 14:47:19 -0600

Hello, I am trying to integrate CIBSE TM52 adaptive criteria.

My idf files are generated through a combination of jeplus parameters and epmacro scripts that collect input from separated idf files. As I cannot copy the whole idf files in a post, I have tried to extract the objects that are relevant for the CIBSE TM52 assessment (done via an EMS program). The schedules referenced by B1_People are all existing (although not copied here).

!- SCHEDULES
Schedule:Compact,
    Always On,               !- Name
    Fraction,                !- Schedule Type Limits Name
    Through: 12/31,          !- Field 1
    For: AllDays,            !- Field 2
    Until: 24:00,            !- Field 3
    1.0;                     !- Field 4

Schedule:Compact,
    Dwell_DomBed_Occ_B1_TM52,       !- Name
    Fraction,                       !- Schedule Type Limits Name
    Through: 12/31,                 !- Field 1
    For: AllDays,                   !- Field 2
    Until: 24:00,                   !- Field 3
    1;                              !- Field 4

!- PEOPLE
People,
    B1_People,                      !- Name
    B1_Zone,                                !- Zone or ZoneList Name
    1_Bd-People 24hr Modified,      !- Number of People Schedule Name
    People,                         !- Number of People Calculation Method
    2,                              !- Number of People
    ,                               !- People per Zone Floor Area
    ,                               !- Zone Floor Area per Person
    0.3,                                !- Fraction Radiant
    AutoCalculate,                  !- Sensible Heat Fraction
    Activity Schedule 78,           !- Activity Level Schedule Name
    3.82e-08,                       !- Carbon Dioxide Generation Rate
    No,                             !- Enable ASHRAE 55 Comfort Warnings
    ZoneAveraged,                   !- Mean Radiant Temperature Calculation Type
    ,                               !- Surface NameAngle Factor List Name
    Work efficiency,                !- Work Efficiency Schedule Name
    ClothingInsulationSchedule,     !- Clothing Insulation Calculation Method
    ,                               !- Clothing Insulation Calculation Method Schedule Name
    ,                               !- Clothing Insulation Schedule Name
    AirVelocitySchedule;            !- Air Velocity Schedule Name

and then:

! EMS SENSORS
EnergyManagementSystem:Sensor,
    Adaptive_Model_Temperature,             !- Name
    B1_People,                          !- Output:Variable or Output:Meter Index Key Name
    Zone Thermal Comfort CEN 15251 Adaptive Model Temperature;  !- Output:Variable or Output:Meter Name 


! EMS ACTUATOR
EnergyManagementSystem:Actuator,
    B1_EMS_Actuator_TM52_OCC,   !- Name
    Dwell_DomBed_Occ_B1_TM52,   !- Actuated Component Unique Name
    Schedule:Constant,          !- Actuated Component Type
    Schedule Value;             !- Actuated Component Control Type

and:

! OUTPUT VARIABLES
Output:Variable,
    B1_People,
    Zone Thermal Comfort CEN 15251 Adaptive Model Temperature,
    daily,
    Always On;

Output:Variable,
    B1_People,
    Zone Thermal Comfort CEN 15251 Adaptive Model Running Average Outdoor Air Temperature,
    runperiod,
    Always On;

Output:Variable,
    B1_People,
    Zone Thermal Comfort CEN 15251 Adaptive Model Running Average Outdoor Air Temperature,
    runperiod,
    Always On;

I receive the following error:

   ** Severe  ** Invalid Output:Variable or Output:Meter Name =ZONE THERMAL COMFORT CEN 15251 ADAPTIVE MODEL RUNNING AVERAGE OUTDOOR AIR TEMPERATURE
   **   ~~~   ** Entered in EnergyManagementSystem:Sensor=RUNNING_AVERAGE_OUTDOOR_AIR_TEMPERATURE
   **   ~~~   ** Output:Variable Name not found
   ** Severe  ** Invalid Output:Variable or Output:Meter Name =ZONE THERMAL COMFORT CEN 15251 ADAPTIVE MODEL TEMPERATURE
   **   ~~~   ** Entered in EnergyManagementSystem:Sensor=ADAPTIVE_MODEL_TEMPERATURE
   **   ~~~   ** Output:Variable Name not found
   ** Severe  ** Invalid Actuated Component Unique Name =DWELL_DOMBED_OCC_B1_TM52
   **   ~~~   ** Entered in EnergyManagementSystem:Actuator=B1_EMS_ACTUATOR_TM52_OCC
   **   ~~~   ** Component Unique key name not found 
   **   ~~~   ** Use Output:EnergyManagementSystem object to create .edd file for valid component names.
   ** Severe  ** Invalid Actuated Component Control Type =SCHEDULE VALUE
   **   ~~~   ** Entered in EnergyManagementSystem:Actuator=B1_EMS_ACTUATOR_TM52_OCC
   **   ~~~   ** Control Type not found
   **   ~~~   ** Use Output:EnergyManagementSystem object to create .edd file for valid component control types.
   **  Fatal  ** Errors found in processing Energy Management System input. Preceding condition causes termination.

I am struggling to understand why each of those 3 severe errors occur. Thanks, Andrea

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2017-03-21 18:40:28 -0600

Output:Variable and Output:Meter objects generated by EnergyPlus depend upon what objects are part of the IDF. For example, if there are no Lights objects in the IDF, then EnergyPlus will not generate any output variables or meters related to internal lights. To see the full list of all Output:Variable and Output:Meter objects for your IDF, check the RDD output file after running a simulation (it should still be created even if your simulation fails). The file name should be ###.rdd, where ###.idf is the IDF file used for the simulation, and it should be saved in the same folder as the IDF.

The first two errors are saying that the Output:Variable named ZONE THERMAL COMFORT CEN 15251 ADAPTIVE MODEL RUNNING AVERAGE OUTDOOR AIR TEMPERATURE and ZONE THERMAL COMFORT CEN 15251 ADAPTIVE MODEL TEMPERATURE are not available, which means they are not listed in the RDD output file. This is most likely because the People object named B1_People doesn't include the input field that specifies which thermal comfort model to use. Making that change (see below) should generate those two output variables.

People,
    B1_People,                      !- Name
    ...
    ,                               !- Clothing Insulation Schedule Name
    AirVelocitySchedule,            !- Air Velocity Schedule Name
    AdaptiveCEN15251;       !- Thermal Comfort Model 1 Type

The third and fourth errors are because the EMS actuator named B1_EMS_ACTUATOR_TM52_OCC lists Schedule:Constant as the object type, but the Dwell_DomBed_Occ_B1_TM52 schedule you're trying to modify with the actuator is a Schedule:Compact object (slightly different object class). Making that change (see below) should remove the errors.

EnergyManagementSystem:Actuator,
    B1_EMS_Actuator_TM52_OCC,   !- Name
    Dwell_DomBed_Occ_B1_TM52,   !- Actuated Component Unique Name
    Schedule:Compact,          !- Actuated Component Type
    Schedule Value;             !- Actuated Component Control Type

Similar to the RDD output file showing the list of all Output:Variable objects for the model, the EDD output file shows the list of all EnergyManagementSystem:Actuator objects for the model. To generate the EDD and see that list of actuators only, you will need to have a Output:EnergyManagementSystem object in the IDF file with the following input fields:

Output:EnergyManagementSystem,
  Verbose,    ! Actuator Availability Dictionary Reporting
  None,    ! Internal Variable Availability Dictionary Reporting
  None; ! EnergyPlus Runtime Language Debug Output Level

As you debug the EMS code and want to examine the internal variables and EMS errors, you should change the last two input fields to other options so that their information also is generated in the EDD output file.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Training Workshops

Careers

Question Tools

1 follower

Stats

Asked: 2017-03-21 11:08:26 -0600

Seen: 486 times

Last updated: Mar 21 '17