In my previous reply, I have shown you how a HVACtemplate object looks like.
After running this IDF, you will find another file with expansion .expIDF. This latter file is actually used for simulation. You can change the extension to IDF, and it will run directly from EPlaunch. The error messages are generated from running the expIDF. That may be the reason why you do not see the line mentioned in the error message in the original .IDF fiie.
The template will generate some of the compact schedules for you. The following is an example of some of them in the .expIDF.
ScheduleTypeLimits,
HVACTemplate Any
Number; !- Name
ThermostatSetpoint:DualSetpoint,
Thermostat Dual SP Control, !- Name
Htg_Sch_temp, !- Heating Setpoint Temperature Schedule Name
Clg_Sch_temp; !- Cooling Setpoint Temperature Schedule Name
Schedule:Compact,
HVACTemplate-Always 1, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
1; !- Field 4
Schedule:Compact,
HVACTemplate-Always 4, !- Name
HVACTemplate Any Number, !- Schedule Type Limits Name
Through:
12/31, !- Field 1
For: AllDays, !- Field 2
Until: 24:00, !- Field 3
4; !- Field 4
ZoneControl:Thermostat,
Space1-1 Control, !- Name
Space1-1, !- Zone or
ZoneList Name
HVACTemplate-Always 4, !- Control Type Schedule Name
ThermostatSetpoint:DualSetpoint, !- Control Object Type
Thermostat Dual SP Control;
!- =========================
The Zone name used above is different from the last mail, because because I wanted to show you that the name can be changed from All Zones to a particular zone name.
There are about 6 ScheduleTypeLimits in a standard IDF. If the template does not want to use yours, it will create another with the prefix
HVACTemplate.
ZoneControl:Thermostat,
SPACE1-1 Control, !- Name
SPACE1-1, !- Zone or ZoneList Name
HVACTemplate-Always 4, !- Control Type Schedule Name
ThermostatSetpoint:SingleCooling, !- Control 1 Object Type
CoolingSetPoint, !- Control 1 Name
ThermostatSetpoint:SingleHeating, !- Control 2 Object Type
HeatingSetpoint, !- Control 2 Name
ThermostatSetpoint:DualSetpoint, !- Control 3 Object Type
DualSetPoint; !- Control 3 Name
!- ==========================
The above is the full expansion.
ZoneControl:Thermostat,
SPACE1-1 Control, !- Name
SPACE1-1, !- Zone or ZoneList Name
HVACTemplate-Always 2, !- Control Type Schedule Name
ThermostatSetpoint:SingleCooling, !- Control 1 Object Type
CoolingSetPoint; !- Control 1 Name
!- =========================
Schedule:Compact,HVACTemplate-Always
2 is the same Schedule:Compact,HVACEemplate-Always 4 with the number 4 changed to 2. You may not need to make all these changes. If
you delete the heating in the original IDF, the expIDF may have the schedules changed for you.
Remember that any changes made in the expIDF will be lost if you re-run the original IDF. If possible, the changes should be made in the original IDF with the template objects.
By the way, where is the
Energy Research Group UBD. I am from Singapore, and it is also in the tropical zone.
Dr. Li
To: EnergyPlus_Support@xxxxxxxxxxxxxxx
From: veronikashabunko@xxxxxxxxx
Date: Fri, 3 Aug 2012 23:25:09 -0700
Subject: [EnergyPlus_Support] AC adding
Hello everyone ,
I am doing the simulation of existing building in tropics with 10 zones. In 5 out of 10 zones I have an Air conditioner .
I am having trouble to understand how I can add it to the E+.( I am not an expert in HVAC). I believe that AC is a part of HVAC so therefore I should add to the HVACTemplate:Thermostat,HVACTemplate:Zone:IdealLoadsAirSystem
Questions are : what is the right procedure of adding AC to all 5 zones and how is adding AC related with ScheduleTypeLimits Name, Schedule:Compact Name ( this is the errors that I've got while adding AC information to the HVACTemplate:Thermostat,
HVACTemplate:Zone:IdealLoadsAirSystem )
Any help and suggestion will be highly appreciated.
Thank you.
Best regards, Veronika
Energy Research Group UBD