Group – Air Distribution[LINK]
Air loops along with zone equipment form the entire forced air heating and cooling system (air side). The main statement for defining an air loop is the AirLoopHVAC object described here. As with the main plant and condenser statements, several of the items in the AirLoopHVAC object definition are actually names that refer to other objects in the input file. After the AirLoopHVAC object name, four such list pointers are encountered: for controllers, system availability, branches, and connectors. The Controller List defines how the air loop will respond due to various inputs (control signals). The Availability Manager List refers to methods for controlling when a system is operational. This may be as simple as a schedule to define when the system is shutdown. The Branch List lists the branches that comprise the primary air system. Finally, the Connector List lists the connections between the branches. The branches and connections together define the primary air system topology.
The only numeric input is the design primary air flow rate. This item is input just before the BranchList name.
The next series of names refer to nodes for the various inlet and outlet points of the air loop. The air loop starts where the zone equipment ends. This is a single point consisting of the return air duct once all of the zone return air streams have been collected (if the loop has a return path). While in reality, there is really only one point, for clarity within the simulation components and consistency with the other HVAC loop sections, this point in the systems is defined as two points: one that resides with the zone equipment simulation and one that is acted upon by the air loop simulation. Both node names must be entered into the input file (if the loop has a return path), and both nodes must have unique names. Similarly, the end points of the air loop that also correspond to the beginning points of the zone equipment loop must also be defined. These consist of names referencing lists of up to three pairs of node names as shown below. Up to three air loop outlets are allowed to accommodate the simulation of three deck systems.
Schedules And Availability Manager[LINK]
Regarding component schedules, the general rule is don’t schedule any components except the supply fan and the corresponding availability manager(s). Beyond that, every component should always be available and let the controls determine what runs or doesn’t run. If a component other than the supply fan is scheduled off, then it will remain off even if the night cycle manager turns on the system.
This field is a unique, user assigned name for a single instance of an AirLoopHVAC object. Any other object referencing this AirLoopHVAC will use this name.
Field: Controller List Name[LINK]
This field is the name of a ControllerList object. A Controller List is simply a list of controllers giving both controller name and type. This Controller List specifies all the controllers that will act on this primary air loop. The order of the controllers in the list is significant: controllers are simulated sequentially in the order given in the Controller List.
Field: Availability Manager List Name[LINK]
This field is the name of a AvailabilityManagerList object. A Availability Manager List is a list of Availability Managers giving both Availability Manager type and name. The availability managers in the list apply to this primary air loop. That is, they determine when and if this air loop is on or off, overriding the control provided by the central fan on/off schedule.
Field: Design Supply Air Flow Rate[LINK]
This is the system primary air design volumetric flow rate in cubic meters per second.
Field: Branch List Name[LINK]
This field is the object name of a BranchList object (see BranchList and Branch). The BranchList named here specifies all the branches composing the primary air system. These branches, together with the Connectors listed in the ConnectorList, define the primary air system topology.
Field: Connector List Name[LINK]
This field is the name of ConnectorList object. This ConnectorList object lists all the Connectors (by type and name) that are included in this primary air system. These Connectors, together with the Branches in the BranchList, define the topology of the primary air system.
Field: Supply Side Inlet Node Name[LINK]
The name of the air entrance node of this primary air system. If this air loop has a return path, then this is the inlet node for return air for this air system. If this air loop does not have a return path, then this node is where outdoor air or other air enters the supply side.
Field: Demand Side Outlet Node Name[LINK]
The name of the air outlet node for the zone equipment group (ZoneHVAC:EquipmentConnections objects) attached to the primary air system. This should be the outlet node of a AirLoopHVAC:ZoneMixer or AirloopHVAC:ReturnPlenum in the AirLoopHVAC:ReturnPath for the zone equipment group attached to this primary air system. Leave this field blank if this air loop does not have a return path.
Field: Demand Side Inlet Node Names[LINK]
This field can be the name of a node which is the air inlet node for the zone equipment group (see ZoneHVAC:EquipmentConnections objects) attached to this primary air system. Or, this field can be the name of a node list containing one or more nodes (up to 3). These nodes should be the inlet nodes to the AirLoopHVAC:ZoneSplitter or AirLoopHVAC:SupplyPlenum in each of the AirLoopHVAC:SupplyPaths for the zone equipment groups attached to this primary air system. For single duct systems, there is only one node name in this list. For two and three duct systems, the order of the nodes in this list must correspond with the order of the nodes in the Supply Side Outlet Node Names list.
Field: Supply Side Outlet Node Names[LINK]
This field can be the name of a node which is the air outlet node for each supply duct of this primary air system. Or, this field can be the name of a node list containing one or more nodes (up to 3). The list can contain the names of up to three nodes. For single duct systems, there is only one node name in this list. For two and three duct systems, the order of the nodes in this list must correspond with the order of the nodes in the Demand Side Inlet Node Names list.
Field: Design Return Air Flow Fraction of Supply Air Flow[LINK]
This field specifies the design air loop return air flow rate as a fraction of the supply flow rate when there is no exhaust flow. It may be used to set zero return air flow for a DOAS system or to model a pressurized system where the return flow is a fraction of the supply flow. The return air flow rate will never be greater than the current supply air flow rate multiplied by this fraction. It may be less if there is unbalanced exhaust from any zones served by this airloop. The default is 1.0. If the air loop has no return path, then this field is ignored.
An example of this statement in an IDF is:
AirLoopHVAC,
Main Dual Duct Air Loop, !- Name
Dual Duct System 1 Controllers, !- Controller List Name
Dual Duct System 1 Schedule List , !- Availability Manager List Name
1.3 , !- Design Supply Air Flow Rate {m3/s}
Dual Duct Air Loop Branches , !- Branch List Name
Dual Duct Connectors , !- Connector List Name
Supply Fan Inlet Node , !- Supply Side Inlet Node Name
Return Air Mixer Outlet , !- Demand Side Outlet Node Name
Zone Equipment Inlet Node List , !- Demand Side Inlet Node Names
Air Loop Outlet Node List, !- Supply Side Outlet Node Names
1.0; !- Design Return Air Flow Fraction of Supply Air Flow
HVAC,Average,Air System Simulation Cycle On Off Status
HVAC,Sum,HVAC System Solver Iteration Count []
HVAC,Sum,Air System Solver Iteration Count []
HVAC,Sum,Air System Simulation Maximum Iteration Count []
HVAC,Sum,Air System Simulation Iteration Count []
HVAC,Sum,Air System Component Model Simulation Calls []
Air System Simulation Cycle On Off Status[LINK]
This field is the availability status of an AirLoopHVAC. This status flag is a result of the calculations made by the System Availability Manager(s) listed in a System Availability Manager List. When a single availability manager is used in a System Availability Manager List, this is also the availability status reported by the specific availability manager (Ref. System Availability Manager Outputs). When multiple availability managers are used in a System Availability Manager List, the loop availability status is determine by the rules associated with AirLoopHVACs (see rules described for Group – System Availability Managers). The control status outputs are represented using integers 0 through 3.. These integers represent NoAction (0), ForceOff (1), CycleOn (2), and CycleOnZoneFansOnly (3). Since the status output is averaged, the output result may not correspond to the values described here when output variable frequencies other than detailed are used. Use the “detailed” reporting frequency (Ref. Output:Variable object) to view the availability status at each simulation timestep.
HVAC System Solver Iteration Count []
[LINK]
Air System Solver Iteration Count []
[LINK]
Air System Simulation Maximum Iteration Count []
[LINK]
Air System Simulation Iteration Count []
[LINK]
Air System Component Model Simulation Calls []
[LINK]
These variables are simply counters of how many iterations were executed. The count for any given HVAC time step will be the iterations executed before convergence was achieved, or the max allowed in which case the simulation throws a warning and proceeds to the next time step.
This section provides more detailed information on the reporting available for outdoor air ventilation. Sixteen cooling and heating load variables and eight energy summary variables are available that report the impact of system outdoor air on zone loads, system demand and total energy use. The representative air system shown in the diagram below shows outdoor air (OA), return air (RA), supply air (SA) and mixed air (MA).
The overall effect of outdoor air on the system shown above can be summarized by considering the mixing box. In this system, part or all of the return air is replaced by outdoor air. The presence of any heat recovery will already be taken into account and thus will automatically be accounted for by using the outdoor air inlet conditions to the mixing box (point OA in the diagram) rather than actual outdoor air conditions. Thus, the overall energy impact of outdoor air (ventilation) on a particular system can be evaluated by multiplying the outdoor air mass flow rate by the enthalpy difference between the outdoor air entering the mixing box (OA) and the return air entering the mixing box (RA’) as shown in the following equation.
˙qOA=˙mOA(hOA−hRA′)=˙msys(hMA−hRA′)
Ventilation Flow Outputs[LINK]
The fresh air flow into each zones are reported using the ventilation flow output variables. The total outdoor air flow in a primary air system is divided to each zone based on the fraction of flow each zone is supplied. There are six variables which deals with the mechanical ventilation flow reporting. Those six variables are:
Zone Mechanical Ventilation Mass Flow Rate [kg/s]
[LINK]
Reports the average outdoor air mass flow rate to any zone over the reporting interval.
Zone Mechanical Ventilation Mass [kg]
[LINK]
Reports the total outdoor air mass that has been supplied to any zone over the reporting interval.
Zone Mechanical Ventilation Standard Density Volume Flow Rate [m3/s]
[LINK]
Reports the average outdoor air volume flow rate to any zone over the reporting interval, calculated using a standard density for air. Standard density in EnergyPlus corresponds to 20ºC drybulb, dry air, and nominally adjusted for elevation.
Zone Mechanical Ventilation Standard Density Volume [m3]
[LINK]
Reports the total outdoor air volume that has been supplied to a zone over the reporting interval, calculated using a standard density for air. Standard density in EnergyPlus corresponds to 20ºC drybulb, dry air, and nominally adjusted for elevation.
Zone Mechanical Ventilation Current Density Volume Flow Rate [m3/s]
[LINK]
Reports the average outdoor air volume flow rate to any zone over the reporting interval, calculated using the current density for zone air.
Zone Mechanical Ventilation Current Density Volume [m3]
[LINK]
Reports the total outdoor air volume that has been supplied to a zone over the reporting interval, calculated using the current density for zone air.
Zone Mechanical Ventilation Air Changes per Hour [ach]
[LINK]
Reports the air changes per hour in the zone due to the outside fresh air supplied by mechanical ventilation system.
The example syntax below shows the basic ventilation flow variables reported on an hourly basis.
Output:Variable,*,Zone Mechanical Ventilation Mass Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Mass,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Standard Density Volume Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Standard Density Volume,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Current Density Volume Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Current Density Volume,Hourly;
Output:Variable,*, Zone Mechanical Ventilation Air Changes per Hour,Hourly;
Ventilation Load Reports[LINK]
The impact of system outdoor air on a particular zone may be calculated by summing the mass flow weighted ˙qOA over the supply air paths (both cooling and heating) serving the zone as follows:
˙qOA,Zone1=AirPathNum∑n=1˙qOA˙mn˙msys
Four output variables each for cooling and heating report the impact of the ventilation air on the zone load in the absence of ventilation air system interactions. The ventilation load output variables are:
Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy [J]
[LINK]
Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy [J]
[LINK]
The cooling/heating load that would occur once ventilation air met the zone cooling/heating load and continued to overcool/overheat the zone. No system effects are accounted for.
Zone Mechanical Ventilation Cooling Load Decrease Energy [J]
[LINK]
Zone Mechanical Ventilation Heating Load Decrease[J]
[LINK]
The decrease in zone cooling/heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
Zone Mechanical Ventilation No Load Heat Removal Energy [J]
[LINK]
Zone Mechanical Ventilation No Load Heat Addition Energy [J]
[LINK]
The addition or removal of heat to a zone with no load. The heat addition or removal is due to mechanical ventilation while the zone thermostat is in the deadband.
To summarize:
Cooling:
1. Zone Mechanical Ventilation No Load Heat Removal Energy [J]
Cooling that would be provided directly to zone by ventilation air. Ventilation occurred with no zone load.
2. Zone Mechanical Ventilation Cooling Load Increase Energy [J]
The increase in zone cooling load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
3. Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy [J]
The cooling load that would occur once ventilation air met the zone heating load and continued to overheat the zone. No system effects are accounted for.
4. Zone Mechanical Ventilation Cooling Load Decrease Energy [J]
The decrease in zone cooling load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
Heating:
1. Zone Mechanical Ventilation No Load Heat Addition Energy [J]
Heating that would be provided directly to zone by ventilation air. Ventilation occurred with no zone load.
2. Zone Mechanical Ventilation Heating Load Increase Energy [J]
The increase in zone heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
3. Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy [J]
The heating load that would occur once ventilation air met the zone cooling load and continued to overcool the zone. No system effects are accounted for.
4. Zone Mechanical Ventilation Heating Load Decrease Energy [J]
The decrease in zone heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
The output variables are calculated by comparing the zone ventilation load with the zone cooling or heating load. ‘Ventilation cooling’ decreases the zone cooling load until the cooling load has been eliminated. The remaining ‘ventilation cooling’ is reported as ‘overcooling’. ‘Overheating’ is calculated in the same manner. The actual system operation, which determines whether or not an ‘overcooling’ or ‘overheating’ load actually results in increased energy consumption, is not considered in the calculation of these output variables.
The ventilation zone load output variables are shown in Table. The variables report the maximum potential “cost” or “benefit” of ventilation air introduced directly into the zone.
Ventilation Load Output Variables
| Ventilation Cooling |
Zone Mechanical Ventilation No Load Heat Removal Energy |
Zone Mechanical Ventilation Cooling Load Decrease Energy |
Zone Mechanical Ventilation Heating Load Increase Energy |
|
Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy |
|
|
|
| Ventilation Heating |
Zone Mechanical Ventilation No Load Heat Addition Energy |
Zone Mechanical Ventilation Cooling Load Increase Energy |
Zone Mechanical Ventilation Heating Load Decrease Energy |
|
Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy |
|
|
|
The example syntax below shows the basic ventilation load variables reported on a monthly basis.
Output:Variable,*,Zone Mechanical Ventilation Heating Load Increase Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Heating Load Decrease Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation No Load Heat Addition Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Cooling Load Increase Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Cooling Load Decrease Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation No Load Heat Removal Energy,monthly;
Reporting on a timestep or hourly level would produce a detailed report with variables intermingled with the other output variables that might be requested in the input file.
Another method will more easily encapsulate the report:
OutputControl:Table:Style, HTML; !- ColumnSeparator
Output:Table:Monthly,
Ventilation Loads, !- Name
, !- DigitsAfterDecimal
Zone Mechanical Ventilation No Load Heat Removal Energy,
SumOrAverage,
Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy,
SumOrAverage,
Zone Mechanical Ventilation Cooling Load Decrease Energy,
SumOrAverage,
Zone Mechanical Ventilation Cooling Load Increase Energy,
SumOrAverage,
Zone Mechanical Ventilation No Load Heat Addition Energy,
SumOrAverage,
Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy,
SumOrAverage,
Zone Mechanical Ventilation Heating Load Decrease Energy,
SumOrAverage,
Zone Mechanical Ventilation Heating Load Increase Energy,
SumOrAverage;
This combination will report the ventilation loads on a monthly basis in a HTML style report that can be easily read in a web browser. Review the Output:Table:Monthly object for other methods of display or further options on this report item.
Systems Level Reporting[LINK]
Most output variables are a single entity reporting. Meters are a combination of like variables – specifically for Energy Consumption. This section introduces a slightly different concept – where output variables described herein are a combination of several similar items – specifically targeted at HVAC/System level reporting. This reporting is coupled with an Air Loop (ref: AirLoopHVAC)
All items shown in this section are typical “output variables” and can be reported with the Output:Variable object.
Or, as is shown by example here, perhaps a more readable form is to generate them in Tabular Form with the “Output:Table:Monthly” object.
System Loads Outputs[LINK]
In this category, the total system load is reported. Two aspects are reported here: Heating and Cooling. The following two variables report the heat energy that system components (including packaged equipment, fans, main coils, reheat coils, humidifiers, desiccant dehumidifiers, evaporative coolers and heat exchangers) add or remove from the air loop. Each variable within these grouping wil
Air System Total Heating Energy[LINK]
Heat Addition to the Air Loop (Sum of all components) in Joules
Air System Total Cooling Energy[LINK]
Heat Removal from the Air Loop (Sum of all components) in Joules
In ‘Output:Table:Monthly’ format shown below.
OutputControl:Table:Style,HTML;
Output:Table:Monthly,
System Loads, !- Name
, !- DigitsAfterDecimal
Air System Total Heating Energy, SumOrAverage,
Air System Total Cooling Energy, SumOrAverage;
System Energy Use Outputs[LINK]
System Energy Use consists of six output variables that report the total energy (in Joules) and water consumption (in m3) for all system components and including packaged equipment, fans, main coils, reheat coils, humidifiers, desiccant dehumidifiers, and evaporative coolers. The output variables shown below show hot and cold water, steam, electric and gas energy. Hot and cold water energy includes all ‘district cooling’ and ‘district heating’ energy.
Air System Hot Water Energy[LINK]
Hot Water Consumption for the system (Joules).
Air System Steam Energy[LINK]
Steam Consumption for the system (Joules).
Air System Chilled Water Energy[LINK]
Chilled Water Consumption for the system (Joules).
Air System Electric Energy[LINK]
Electric Consumption for the system (Joules).
Air System Gas Energy[LINK]
Gas (Natural Gas and Propane) Consumption for the system (Joules).
Air System Water Volume[LINK]
Water Consumption for the system (humidifiers and evaporative coolers) (m3).
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Energy and Water Use”.
OutputControl:Table:Style,HTML;
Output:Table:Monthly,
Air Loop System Energy and Water Use, !- Name
, !- DigitsAfterDecimal
Air System Hot Water Energy , SumOrAverage,
Air System Steam Energy , SumOrAverage,
Air System Chilled Water Energy, SumOrAverage,
Air System Electric Energy, SumOrAverage,
Air System Gas Energy, SumOrAverage,
Air System Water Volume, SumOrAverage;
System Component Loads Outputs[LINK]
Reporting System Component Loads shows the energy transferred to or extracted from the air loop by system component type. Fans, Cooling Coils, Heating Coils, Heat exchangers, humidifiers, evaporative coolers, and desiccant dehumidifiers show heat transfer rates in Joules. The components may be located in outdoor air systems bundled with packaged equipment or specified as stand-alone components. The reporting accounts for both main branch and reheat coils.
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Component Loads”.
OutputControl:Table:Style,HTML;
Output:Table:Monthly,
Air Loop System Component Loads, !- Name
, !- DigitsAfterDecimal
Air System Fan Air Heating Energy, SumOrAverage,
Air System Cooling Coil Total Cooling Energy, SumOrAverage,
Air System Heating Coil Total Heating Energy, SumOrAverage,
Air System Heat Exchanger Total Heating Energy, SumOrAverage,
Air System Heat Exchanger Total Cooling Energy, SumOrAverage,
Air System Humidifier Total Heating Energy, SumOrAverage,
Air System Evaporative Cooler Total Cooling Energy, SumOrAverage,
Air System Desiccant Dehumidifier Total Cooling Energy, SumOrAverage;
Air System Fan Air Heating Energy[LINK]
Energy added to the air loop by Fans (Joules)
Air System Cooling Coil Total Cooling Energy[LINK]
Energy removed from air loop by Cooling Coils (Joules)
Air System Heating Coil Total Heating Energy[LINK]
Energy added to air loop by Heating Coils (Joules)
Air System Heat Exchanger Total Heating Energy[LINK]
Energy added to air loop by air-to-air heat recovery heat exchangers (Joules)
Air System Heat Exchanger Total Cooling Energy[LINK]
Energy removed from air loop by air-to-air heat recovery heat exchangers (Joules)
Air System Humidifier Total Heating Energy[LINK]
Energy added to air loop by humidifiers (Joules)
Air System Evaporative Cooler Total Cooling Energy[LINK]
Energy removed from air loop by evaporative coolers (Joules)
Air System Desiccant Dehumidifier Total Cooling Energy[LINK]
Energy removed from air loop by desiccant dehumidifiers (Joules)
Air System Solar Collector Total Heating Energy[LINK]
Energy added to air loop by solar collectors (Joules)
Air System Solar Collector Total Cooling Energy[LINK]
Energy removed from air loop by solar collectors (Joules)
Air System User Defined Air Terminal Total Heating Energy[LINK]
Energy added to air loop by user defined air terminal units (Joules)
Air System User Defined Air Terminal Total Cooling Energy[LINK]
Energy removed from air loop by user defined air terminal units (Joules)
System Component Energy Use Outputs[LINK]
Reporting System Component Energy Use consists of eleven output variables that report the total energy consumption (in Joules) of system components by energy type and coil type. Electric energy consumption is reported for fans, heating and cooling coils in packaged (DX) systems, electric resistance heating coils, humidifiers, evaporative coolers and desiccant dehumidifiers.
Air System Fan Electric Energy[LINK]
Electric consumption for fans. (Joules)
Air System Heating Coil Hot Water Energy[LINK]
Consumption for heating coil hot water (both purchased and plant supplied) (Joules)
Air System Cooling Coil Chilled Water Energy[LINK]
Consumption for cooling coil chilled water (both purchased and plant supplied) (Joules)
Air System DX Heating Coil Electric Energy[LINK]
Compressor plus condenser fan electricity use. (Joules)
Air System DX Cooling Coil Electric Energy[LINK]
Compressor plus condenser fan electricity use. (Joules)
Air System Heating Coil Electric Energy[LINK]
Electricity consumption for the heating coil. (Joules)
Air System Heating Coil Gas Energy[LINK]
Gas (Propane and Natural Gas) consumption for the heating coil. (Joules)
Air System Heating Coil Steam Energy[LINK]
Steam consumption for the heating coil (steam coils). (Joules)
Air System Humidifier Electric Energy[LINK]
Electricity consumption for the humidifiers. (Joules)
Air System Evaporative Cooler Electric Energy[LINK]
Electricity consumption for the evaporative coolers. (Joules)
Air System Desiccant Dehumidifier Electric Energy[LINK]
Electricity consumption for the desiccant dehumidifiers. (Joules)
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Component Energy Use”.
OutputControl:Table:Style,HTML;
Output:Table:Monthly,
Air Loop System Component Energy Use, !- Name
, !- DigitsAfterDecimal
Air System Fan Electric Energy, SumOrAverage,
Air System Heating Coil Hot Water Energy, SumOrAverage,
Air System Cooling Coil Chilled Water Energy, SumOrAverage,
Air System DX Heating Coil Electric Energy, SumOrAverage,
Air System DX Cooling Coil Electric Energy, SumOrAverage,
Air System Heating Coil Electric Energy, SumOrAverage,
Air System Heating Coil Gas Energy, SumOrAverage,
Air System Heating Coil Steam Energy, SumOrAverage,
Air System Humidifier Electric Energy, SumOrAverage,
Air System Evaporative Cooler Electric Energy, SumOrAverage,
Air System Desiccant Dehumidifier Electric Energy, SumOrAverage;
Overall Air Loop Syntax[LINK]
A map for Air Loop input syntax is shown in the following diagram.
AirLoopHVAC:ControllerList[LINK]
The syntax for the AirLoopHVAC:ControllerList definition is shown below. As with other lists in EnergyPlus input, the object title and identifying name are followed by type-name pairs. In this case, the types are controller types. The order in which controllers appear on this list also define the priority as described below. The identifying name refers back to the name recorded in the AirLoopHVAC statement.
The user designated unique name of an instance of a Controller List. Any object referencing this Controller List will do so using this name.
Field Set (Object Type, Controller Name) up to 8[LINK]
After the identifying name, input for the controller list consists of up to 8 pairs of data items: a controller type and a controller name. The first controller listed has the highest priority, the second the second highest priority, and so forth.
Field: Controller <x> Object Type[LINK]
The type of controller. This should be a key word defining a class of controllers such as Controller:WaterCoil.
Field: Controller <x> Name[LINK]
The name of a controller object (such as a Controller:WaterCoil) defined elsewhere in the input file.
An example of this statement in an IDF is:
AirLoopHVAC:ControllerList,
Dual Duct System 1 Controllers,
Controller:WaterCoil, Main Cooling Coil Controller,
Controller:WaterCoil, Main Heating Coil Controller;
AvailabilityManagerAssignmentList[LINK]
The AvailabilityManagerAssignmentList defines the applicable managers used for an AirLoopHVAC or PlantLoop. The priority of availability managers is based on a set of rules and are specific to the type of loop. The output from each Availability Manager is an availability status flag. This flag can have the values NoAction, ForceOff, CycleOn, or CycleOnZoneFansOnly (used only for air loops). The availability status flags for the Availability Managers referenced by an air or plant loop are used to set the availability status flag for each loop. For the air loops, ForceOff takes precedence: if any of the loop’s availability managers are showing status ForceOff, the loop status will be ForceOff. Next in precedence is CycleOnZoneFansOnly, followed by CycleOn, and NoAction. For the plant loops, there is no precedence among the Availability Manager status flag values. Instead, the first availability manager giving a status flag value other than NoAction sets the status for the loop. The Availability Managers are executed in Availability Manager List order.
Special rules also apply for which managers may be listed in a Availability Manager list. The Hybrid Ventilation Control Manager (object: AvailabilityManager:HybridVentilation) is a special type of manager and is never specified in a Availability Manager List (it is used stand-alone for a specific air loop). All other types of availability managers may be listed in the Availability Manager List used for AirLoopHVACs. For Plant Loops, the Night Cycle and Night Ventilation managers (objects: AvailabilityManager:NightCycle and AvailabilityManager:NightVentilation) are not allowed in the Availability Manager List.
The name of the AvailabilityManagerAssignmentList object. This is referenced by AirLoopHVAC and PlantLoop objects.
Field Set (Availability Manager Object Type, Name)[LINK]
Managers are listed by pairs of data items: Availability Manager Object Type and Availability Manager Name. The managers are simulated down the list and calculate a control status for use by the AirLoopHVAC or PlantLoop. The priority of each manager used for a specific loop is based on the rules described above. Availability managers are not currently used for condenser loops. The availability managers, along with the AirLoopHVAC and PlantLoop object, report the control status calculated each simulation timestep. These output variables can be used to prioritize the managers according to the required control strategy. Six managers are accomodated in the list by default, however, this IDD specification is extensible. Additional pairs may be added by directly editing the IDD.
Field: Availability Manager <x> Object Type[LINK]
The key word defining the type of manager, e.g. AvailabilityManager:NightCycle.
Field: Availability Manager<x> Name[LINK]
The name of a AvailabilityManager object defined elsewhere in the input file.
An example of this statement in an IDF is:
AvailabilityManagerAssignmentList,
Collector Loop Availability Manager List, !- Name
AvailabilityManager:HighTemperatureTurnOff, !- System Availability Manager Type 1
High Temperature Turn Off Availability Manager, !- System Availability Manager Name 1
AvailabilityManager:LowTemperatureTurnOn , !- System Availability Manager Type 2
Low Temperature Turn On Availability Manager, !- System Availability Manager Name 2
AvailabilityManager:DifferentialThermostat, !- System Availability Manager Type 3
Differential Thermostat Availability Manager; !- System Availability Manager Name 3
AirLoopHVAC:OutdoorAirSystem[LINK]
The Outside Air System (object AirLoopHVAC:OutdoorAirSystem) is a subsystem of an AirLoopHVAC. It handles the mixed air portion of the primary air system: the system relief air, the outside air inlet, and any components and controllers associated with the system relief air and outside air streams. From the perspective of the primary air loop the Outside Air System is treated as a single component. As a subsystem, it can contain one or more components and controllers.
The input for the Outside Air System consists of a system name, a controller list name, an equipment list name, and an availability manager list name. The controller list simply lists, by type and unique name, all the controllers in the subsystem. The controllers will be simulated in list order. The equipment list lists all the components in the subsystem, by type and name. The equipment is simulated in list order. Finally, the availability manager list gives the type and name of the availability managers used by the subsystem.
The equipment inlet/outlet must be sequential with no loops - the simulation can only handle a straight-through air path, both on the primary air side and on the secondary air side, if any. Heat exchanger secondary air inlets need to be independent of the primary air stream – usually relief air is used.
The unique, user assigned name for a single instance of an Outside Air System. Any other object referencing this Outside Air System will use this name.
Field: Name: Controller List Name[LINK]
This field is the name of a AirLoopHVAC:ControllerList object. A AirLoopHVAC:ControllerList is simply a list of controllers giving both controller name and type. This Controller List specifies all the controllers that will act on this outside air system. The order of the controllers in the list is significant: controllers are simulated sequentially in the order given in the Controller List. Typically the Controller List would contain a Controller:OutdoorAir. If there are chilled water or hot water coils in the outdoor air system, each such coil will need a Controller:WaterCoil.
Field: Outdoor Air Equipment List Name[LINK]
This field is the name of an AirLoopHVAC:OutdoorAirSystem:EquipmentList object. An AirLoopHVAC:OutdoorAirSystem:EquipmentList is simply a list of components giving both component name and type. This Outdoor Air Equipment List specifies all the components that will be simulated in this outside air system. The order of the components in the list is significant: components are simulated sequentially in the order given in the Outdoor Air Equipment List. Typically the equipment list would contain at least an OutdoorAir:Mixer. If there is more than one component, the components must be listed in order from the outside air to the OutdoorAir:Mixer (the OutdoorAir:Mixer is last).
Field: Availability Manager List Name[LINK]
This field is the name of a AvailabilityManagerAssignmentList object. An Availability Manager List is a list of Availability Managers giving both Availability Manager Object Type and Name. Use of this input is optional. This field may be omitted; it is not currently used by the program.
An IDF example, including the AirLoopHVAC, and the controller and equipment lists.
AirLoopHVAC,Typical Terminal Reheat 1,
Reheat System 1 Controllers,
Reheat System 1 Avail List,
1.3,
Air Loop Branches,,
Air Loop Inlet Node, Return Air Mixer Outlet,
Zone Equipment Inlet Node, Air Loop Outlet Node;
AirLoopHVAC:ControllerList,
Reheat System 1 Controllers,
Controller:WaterCoil, Main Cooling Coil Controller;
BranchList, Air Loop Branches,
Air Loop Main Branch;
Branch, Air Loop Main Branch,
1.3,
AirLoopHVAC:OutdoorAirSystem, OA Sys 1,
Air Loop Inlet Node, Mixed Air Node,PASSIVE
Fan:ConstantVolume, Supply Fan 1,
Mixed Air Node, Cooling Coil Air Inlet Node, ACTIVE,
Coil:Cooling:Water:DetailedGeometry, Detailed Cooling Coil,
Cooling Coil Air Inlet Node, Air Loop Outlet Node;
AvailabilityManagerAssignmentList, Reheat System 1 Avail List,
AvailabilityManager:Scheduled, Reheat System 1 Avail;
AvailabilityManager:Scheduled, Reheat System 1 Avail,
FanAndCoilAvailSched;
AirLoopHVAC:OutdoorAirSystem,
OA Sys 1,
OA Sys 1 Controllers,
OA Sys 1 Equipment;
AirLoopHVAC:ControllerList,
OA Sys 1 Controllers,
Controller:OutdoorAir, OA Controller 1;
AirLoopHVAC:OutdoorAirSystem:EquipmentList,
OA Sys 1 Equipment,
HeatExchanger:AirToAir:FlatPlate,OA Heat Recovery 1,
OutdoorAir:Mixer, OA Mixing Box 1;
The impact of using outside air/mechanical ventilation is described in the section: Outdoor Air Ventilation Outputs.
AirLoopHVAC:OutdoorAirSystem:EquipmentList[LINK]
Used to specify the components in the outdoor air system. The components will be simulated in the order in which they occur in the list.
The following HVAC equipment types are allowed as outdoor air system equipment. The component matrix shows which coils and fans are allowed with which equipment models.
The user designated unique name of an instance of an Air Loop Equipment List. Any object referencing this Air Loop Equipment List will do so using this name.
Field Set (Component Object Type,, Component Name) up to 8[LINK]
After the identifying name, the list consists of up to 8 pairs of data items:
Field: Component <x> Object Type[LINK]
This field specifies the keyword for the type of component used.
Field: Component <x> Name[LINK]
This field is the unique name of the component specified in the previous field. This named object must appear in the IDF.
An example from an IDF:
AirLoopHVAC:OutdoorAirSystem:EquipmentList,
OA Sys 1 Equipment,
HeatExchanger:AirToAir:FlatPlate,OA Heat Recovery 1,
OutdoorAir:Mixer, OA Mixing Box 1;
OutdoorAir:Node[LINK]
The OutdoorAir:Node object declares an HVAC system node for outdoor air conditions. The program automatically sets the air conditions at these nodes to correspond to the ambient environmental conditions at the beginning of every timestep. The outdoor air node is typically used as the inlet air node to an HVAC component such as the OutdoorAir:Mixer object. Multiple OutdoorAir:Node objects can be used in an input file, however, duplicate node names are not allowed.
The Height Above Ground field is used to adjust the weather file air conditions, e.g., outdoor dry-bulb and wet-bulb air temperatures, for atmospheric variation with height. This variation can become a significant factor when modeling tall buildings. See the Engineering Reference section on Atmospheric Variation for a description of the algorithm for variation of atmospheric properties with height. A blank entry or a value less than zero for this field indicates that the height will be ignored and the weather file conditions will be used.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions. OutdoorAir:Node modifies the weather file conditions if a height has been specified. OutdoorAir:NodeList does not have a height input and always uses the weather file conditions without modification. The same node name may not be used with both of these objects.
When declared in surface property objects SurfaceProperty:LocalEnvironment, in zone property objects ZoneProperty:LocalEnvironment, or as an external node in the airflow network calculation linking to a surface node AirflowNetwork:Multizone:Surface, the object can also be used to define local outdoor air conditions for surfaces, zones or air loop components. The local outdoor air conditions would be used in the EnergyPlus calculations for:
-
Convection coefficients used in the exterior surface heat balance
If the user declares a local surface outdoor air node to overwrite the surface level environmental data, the convection coefficients would be calculated based on the local outdoor air node data accordingly based on surface level outdoor dry-bulb temperature, humidity ratio and wind speed.
-
Zone air infiltration and simple ventilation
If the user declares a local zone outdoor air node to overwrite zone level environmental data, global environmental variables used in the subroutines for infiltration and ventilation calculation, including outdoor air temperature, humidity ratio, enthalpy, wind speed and direction, would be overwritten accordingly with zone level data.
-
External air nodes used in the AirFlowNetwork
When used in the airflow network for wind pressure calculation, global environmental variables used in the subroutines for wind pressure calculation, including outdoor air temperature, humidity ratio, air density, wind speed and direction, would be overwritten accordingly with local data.
When used in these cases, optional schedule inputs of local ambient air conditions, including dry-bulb temperature, wet-bulb temperature, wind velocity, and wind direction, can be defined in the optional fields. When used in the airflow network for wind pressure calculation, the wind pressure coefficient curve name and calculation details should also be defined.
The unique name for this outdoor air node.
Field: Height Above Ground[LINK]
The height [m] of the node above ground level. A value greater than zero allows the weather file conditions, e.g., outdoor dry-bulb and wet-bulb air temperatures, to be adjusted according to atmospheric variation with height.
A blank entry or value less than zero indicates that the height will be ignored and the weather file conditions will be used.
Field: Drybulb Temperature Schedule Name[LINK]
This field is used to supply a schedule name of the local dry bulb temperature of this node. When the field is left blank, global values would be used in calculation.
Field: Wetbulb Temperature Schedule Name[LINK]
This field is used to supply a schedule name of the local wet bulb temperature of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Speed Schedule Name[LINK]
This field is used to supply a schedule name of the local wind speed of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Direction Schedule Name[LINK]
This field is used to supply a schedule name of the local wind direction of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Pressure Coefficient Curve Name[LINK]
The name of a specific AirflowNetwork:MultiZone:WindPressureCoefficientValues object (which gives wind pressure coefficients for the façade as a function of angle of wind incident on the façade).
Field: Symmetric Wind Pressure Coefficient Curve[LINK]
This field is used to specify whether the pressure curve is symmetric or not. Yes for curves that should be evaluated from 0 to 180 degrees. No for curves that should be evaluated from 0 to 360 degrees.
Field: Wind Angle Type[LINK]
This field is used to specify whether the angle used to compute the wind pressure coefficient is absolute or relative. Relative for computing the angle between the wind direction and the surface azimuth. Absolute for using the wind direction angle directly.
An example IDF:
OutdoorAir:Node,
OA Node 1; !- Name
OutdoorAir:Node,
Floor 10 Outdoor air Inlet Node, !- Name
30.0; !- Height Above Ground {m}
OutdoorAir:Node,
LocalOutdoorAirNode:0001, !- Name
, !- Height Above Ground
OutdoorAirNodeDryBulb:0001, !- Drybulb Temperature Schedule Name
OutdoorAirNodeWetBulb:0001, !- Wetbulb Temperature Schedule Name
OutdoorAirNodeWindSpeed:0001, !- Wind Speed Schedule Name
OutdoorAirNodeWindDir:0001; !- Wind Direction Schedule Name
NFacade_WPCValue, !- Wind Pressure Coefficient Curve Name
No, !- Symmetric Wind Pressure Coefficient Curve
Absolute; !- Wind Angle Type
Outdoor Air Node outputs:[LINK]
The ambient dry-bulb, wet-bulb air temperature, wind speed and direction, and flow rate at the outdoor air node can be monitored using the system node output variables:
HVAC,Average,System Node Temperature [C]
HVAC,Average,System Node Wetbulb Temperature [C]
HVAC,Average,System Node Wind Speed [m/s]
HVAC,Average,System Node Wind Direction [degree]
HVAC,Average,System Node Mass Flow Rate [kg/s]
e.g.
Output:Variable,
Floor 10 Outdoor air Inlet Node,
System Node Temperature,
Hourly;
OutdoorAir:NodeList[LINK]
The program needs to know which HVAC system nodes are inlets for outdoor air. Knowing this, the program can set the conditions at these nodes to the outdoor conditions at the start of each major timestep. The OutdoorAir:NodeList provides the means for specifying which nodes are outdoor air nodes.
The input is flexible: there may be one or more OutdoorAir:NodeList in each input file. Each list contains up to 25 names. The names can be the name of a unique HVAC system node, or the name of a Node List which will contain the actual node names. Duplicate node names are ignored.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions. OutdoorAir:Node modifies the weather file conditions if a height has been specified. OutdoorAir:NodeList does not have a height input and always uses the weather file conditions without modification. The same node name may not be used with both of these objects.
Field: Node or NodeList name[LINK]
The name of an HVAC system node or of a NodeList object. There can be up to 25 names.
An example IDF:
OutdoorAir:NodeList,
OutsideAirInletNodes;
NodeList,OutsideAirInletNodes,
Outdoor air Inlet Node;
OutdoorAir:Mixer[LINK]
The OutdoorAir:Mixer is the most common component used in an outdoor air system. The outdoor air mixer has 2 inlet air streams: the system return air and the outdoor air. It has 2 outlet air streams: the system relief air and the mixed air. This is a passive component. It takes the inlet mass flows and conditions plus the relief air mass flow and calculates the mixed air flow rate and conditions (as well as the relief air conditions). The inlet and relief mass flow must be set outside the component – most commonly by an outdoor air controller. The OutdoorAir:Mixer can also be used in compound components such as a fan coil unit.
Input for this object is very simple: a unique name plus the node names of the 2 inlet nodes and the 2 outlet nodes.
A unique user assigned name for a particular outdoor air mixer component. Any reference to this component by another object will use this name.
Field: Mixed Air Node Name[LINK]
The name of the HVAC system node which is the outlet for the mixed air stream.
Field: Outdoor Air Stream Node Name[LINK]
The name of the HVAC system node which is the inlet for the outdoor air stream.
Field: Relief Air Stream Node Name[LINK]
The name of the HVAC system node which is the outlet for the system relief air.
Field: Return Air Stream Node Name[LINK]
The name of the HVAC system node which is the inlet for the return air stream.
An IDF example:
OutdoorAir:Mixer,
Zone1WindACOAMixer, ! name
Zone1WindACOAMixerOutletNode, ! mixer outlet node
Zone1WindACOAInNode, ! mixer OA node
Zone1WindACExhNode, ! mixer relief node
Zone1WindACAirInletNode; ! mixer inlet node
Group – Air Distribution[LINK]
AirLoopHVAC[LINK]
Air loops along with zone equipment form the entire forced air heating and cooling system (air side). The main statement for defining an air loop is the AirLoopHVAC object described here. As with the main plant and condenser statements, several of the items in the AirLoopHVAC object definition are actually names that refer to other objects in the input file. After the AirLoopHVAC object name, four such list pointers are encountered: for controllers, system availability, branches, and connectors. The Controller List defines how the air loop will respond due to various inputs (control signals). The Availability Manager List refers to methods for controlling when a system is operational. This may be as simple as a schedule to define when the system is shutdown. The Branch List lists the branches that comprise the primary air system. Finally, the Connector List lists the connections between the branches. The branches and connections together define the primary air system topology.
The only numeric input is the design primary air flow rate. This item is input just before the BranchList name.
The next series of names refer to nodes for the various inlet and outlet points of the air loop. The air loop starts where the zone equipment ends. This is a single point consisting of the return air duct once all of the zone return air streams have been collected (if the loop has a return path). While in reality, there is really only one point, for clarity within the simulation components and consistency with the other HVAC loop sections, this point in the systems is defined as two points: one that resides with the zone equipment simulation and one that is acted upon by the air loop simulation. Both node names must be entered into the input file (if the loop has a return path), and both nodes must have unique names. Similarly, the end points of the air loop that also correspond to the beginning points of the zone equipment loop must also be defined. These consist of names referencing lists of up to three pairs of node names as shown below. Up to three air loop outlets are allowed to accommodate the simulation of three deck systems.
Schedules And Availability Manager[LINK]
Regarding component schedules, the general rule is don’t schedule any components except the supply fan and the corresponding availability manager(s). Beyond that, every component should always be available and let the controls determine what runs or doesn’t run. If a component other than the supply fan is scheduled off, then it will remain off even if the night cycle manager turns on the system.
Inputs[LINK]
Field: Name[LINK]
This field is a unique, user assigned name for a single instance of an AirLoopHVAC object. Any other object referencing this AirLoopHVAC will use this name.
Field: Controller List Name[LINK]
This field is the name of a ControllerList object. A Controller List is simply a list of controllers giving both controller name and type. This Controller List specifies all the controllers that will act on this primary air loop. The order of the controllers in the list is significant: controllers are simulated sequentially in the order given in the Controller List.
Field: Availability Manager List Name[LINK]
This field is the name of a AvailabilityManagerList object. A Availability Manager List is a list of Availability Managers giving both Availability Manager type and name. The availability managers in the list apply to this primary air loop. That is, they determine when and if this air loop is on or off, overriding the control provided by the central fan on/off schedule.
Field: Design Supply Air Flow Rate[LINK]
This is the system primary air design volumetric flow rate in cubic meters per second.
Field: Branch List Name[LINK]
This field is the object name of a BranchList object (see BranchList and Branch). The BranchList named here specifies all the branches composing the primary air system. These branches, together with the Connectors listed in the ConnectorList, define the primary air system topology.
Field: Connector List Name[LINK]
This field is the name of ConnectorList object. This ConnectorList object lists all the Connectors (by type and name) that are included in this primary air system. These Connectors, together with the Branches in the BranchList, define the topology of the primary air system.
Field: Supply Side Inlet Node Name[LINK]
The name of the air entrance node of this primary air system. If this air loop has a return path, then this is the inlet node for return air for this air system. If this air loop does not have a return path, then this node is where outdoor air or other air enters the supply side.
Field: Demand Side Outlet Node Name[LINK]
The name of the air outlet node for the zone equipment group (ZoneHVAC:EquipmentConnections objects) attached to the primary air system. This should be the outlet node of a AirLoopHVAC:ZoneMixer or AirloopHVAC:ReturnPlenum in the AirLoopHVAC:ReturnPath for the zone equipment group attached to this primary air system. Leave this field blank if this air loop does not have a return path.
Field: Demand Side Inlet Node Names[LINK]
This field can be the name of a node which is the air inlet node for the zone equipment group (see ZoneHVAC:EquipmentConnections objects) attached to this primary air system. Or, this field can be the name of a node list containing one or more nodes (up to 3). These nodes should be the inlet nodes to the AirLoopHVAC:ZoneSplitter or AirLoopHVAC:SupplyPlenum in each of the AirLoopHVAC:SupplyPaths for the zone equipment groups attached to this primary air system. For single duct systems, there is only one node name in this list. For two and three duct systems, the order of the nodes in this list must correspond with the order of the nodes in the Supply Side Outlet Node Names list.
Field: Supply Side Outlet Node Names[LINK]
This field can be the name of a node which is the air outlet node for each supply duct of this primary air system. Or, this field can be the name of a node list containing one or more nodes (up to 3). The list can contain the names of up to three nodes. For single duct systems, there is only one node name in this list. For two and three duct systems, the order of the nodes in this list must correspond with the order of the nodes in the Demand Side Inlet Node Names list.
Field: Design Return Air Flow Fraction of Supply Air Flow[LINK]
This field specifies the design air loop return air flow rate as a fraction of the supply flow rate when there is no exhaust flow. It may be used to set zero return air flow for a DOAS system or to model a pressurized system where the return flow is a fraction of the supply flow. The return air flow rate will never be greater than the current supply air flow rate multiplied by this fraction. It may be less if there is unbalanced exhaust from any zones served by this airloop. The default is 1.0. If the air loop has no return path, then this field is ignored.
An example of this statement in an IDF is:
Outputs[LINK]
HVAC,Average,Air System Simulation Cycle On Off Status
HVAC,Sum,HVAC System Solver Iteration Count []
HVAC,Sum,Air System Solver Iteration Count []
HVAC,Sum,Air System Simulation Maximum Iteration Count []
HVAC,Sum,Air System Simulation Iteration Count []
HVAC,Sum,Air System Component Model Simulation Calls []
Air System Simulation Cycle On Off Status[LINK]
This field is the availability status of an AirLoopHVAC. This status flag is a result of the calculations made by the System Availability Manager(s) listed in a System Availability Manager List. When a single availability manager is used in a System Availability Manager List, this is also the availability status reported by the specific availability manager (Ref. System Availability Manager Outputs). When multiple availability managers are used in a System Availability Manager List, the loop availability status is determine by the rules associated with AirLoopHVACs (see rules described for Group – System Availability Managers). The control status outputs are represented using integers 0 through 3.. These integers represent NoAction (0), ForceOff (1), CycleOn (2), and CycleOnZoneFansOnly (3). Since the status output is averaged, the output result may not correspond to the values described here when output variable frequencies other than detailed are used. Use the “detailed” reporting frequency (Ref. Output:Variable object) to view the availability status at each simulation timestep.
HVAC System Solver Iteration Count [] [LINK]
Air System Solver Iteration Count [] [LINK]
Air System Simulation Maximum Iteration Count [] [LINK]
Air System Simulation Iteration Count [] [LINK]
Air System Component Model Simulation Calls [] [LINK]
These variables are simply counters of how many iterations were executed. The count for any given HVAC time step will be the iterations executed before convergence was achieved, or the max allowed in which case the simulation throws a warning and proceeds to the next time step.
Outputs[LINK]
This section provides more detailed information on the reporting available for outdoor air ventilation. Sixteen cooling and heating load variables and eight energy summary variables are available that report the impact of system outdoor air on zone loads, system demand and total energy use. The representative air system shown in the diagram below shows outdoor air (OA), return air (RA), supply air (SA) and mixed air (MA).
Example System for Ventilation Loads Report
The overall effect of outdoor air on the system shown above can be summarized by considering the mixing box. In this system, part or all of the return air is replaced by outdoor air. The presence of any heat recovery will already be taken into account and thus will automatically be accounted for by using the outdoor air inlet conditions to the mixing box (point OA in the diagram) rather than actual outdoor air conditions. Thus, the overall energy impact of outdoor air (ventilation) on a particular system can be evaluated by multiplying the outdoor air mass flow rate by the enthalpy difference between the outdoor air entering the mixing box (OA) and the return air entering the mixing box (RA’) as shown in the following equation.
˙qOA=˙mOA(hOA−hRA′)=˙msys(hMA−hRA′)
Ventilation Flow Outputs[LINK]
The fresh air flow into each zones are reported using the ventilation flow output variables. The total outdoor air flow in a primary air system is divided to each zone based on the fraction of flow each zone is supplied. There are six variables which deals with the mechanical ventilation flow reporting. Those six variables are:
Zone Mechanical Ventilation Mass Flow Rate [kg/s] [LINK]
Reports the average outdoor air mass flow rate to any zone over the reporting interval.
Zone Mechanical Ventilation Mass [kg] [LINK]
Reports the total outdoor air mass that has been supplied to any zone over the reporting interval.
Zone Mechanical Ventilation Standard Density Volume Flow Rate [m3/s] [LINK]
Reports the average outdoor air volume flow rate to any zone over the reporting interval, calculated using a standard density for air. Standard density in EnergyPlus corresponds to 20ºC drybulb, dry air, and nominally adjusted for elevation.
Zone Mechanical Ventilation Standard Density Volume [m3] [LINK]
Reports the total outdoor air volume that has been supplied to a zone over the reporting interval, calculated using a standard density for air. Standard density in EnergyPlus corresponds to 20ºC drybulb, dry air, and nominally adjusted for elevation.
Zone Mechanical Ventilation Current Density Volume Flow Rate [m3/s] [LINK]
Reports the average outdoor air volume flow rate to any zone over the reporting interval, calculated using the current density for zone air.
Zone Mechanical Ventilation Current Density Volume [m3] [LINK]
Reports the total outdoor air volume that has been supplied to a zone over the reporting interval, calculated using the current density for zone air.
Zone Mechanical Ventilation Air Changes per Hour [ach] [LINK]
Reports the air changes per hour in the zone due to the outside fresh air supplied by mechanical ventilation system.
The example syntax below shows the basic ventilation flow variables reported on an hourly basis.
Output:Variable,*,Zone Mechanical Ventilation Mass Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Mass,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Standard Density Volume Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Standard Density Volume,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Current Density Volume Flow Rate,Hourly;
Output:Variable,*,Zone Mechanical Ventilation Current Density Volume,Hourly;
Output:Variable,*, Zone Mechanical Ventilation Air Changes per Hour,Hourly;
Ventilation Load Reports[LINK]
The impact of system outdoor air on a particular zone may be calculated by summing the mass flow weighted ˙qOA over the supply air paths (both cooling and heating) serving the zone as follows:
˙qOA,Zone1=AirPathNum∑n=1˙qOA˙mn˙msys
Four output variables each for cooling and heating report the impact of the ventilation air on the zone load in the absence of ventilation air system interactions. The ventilation load output variables are:
Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy [J] [LINK]
Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy [J] [LINK]
The cooling/heating load that would occur once ventilation air met the zone cooling/heating load and continued to overcool/overheat the zone. No system effects are accounted for.
Zone Mechanical Ventilation Cooling Load Decrease Energy [J] [LINK]
Zone Mechanical Ventilation Heating Load Decrease[J] [LINK]
The decrease in zone cooling/heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
Zone Mechanical Ventilation No Load Heat Removal Energy [J] [LINK]
Zone Mechanical Ventilation No Load Heat Addition Energy [J] [LINK]
The addition or removal of heat to a zone with no load. The heat addition or removal is due to mechanical ventilation while the zone thermostat is in the deadband.
To summarize:
Cooling:
1. Zone Mechanical Ventilation No Load Heat Removal Energy [J]
Cooling that would be provided directly to zone by ventilation air. Ventilation occurred with no zone load.
2. Zone Mechanical Ventilation Cooling Load Increase Energy [J]
The increase in zone cooling load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
3. Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy [J]
The cooling load that would occur once ventilation air met the zone heating load and continued to overheat the zone. No system effects are accounted for.
4. Zone Mechanical Ventilation Cooling Load Decrease Energy [J]
The decrease in zone cooling load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
Heating:
1. Zone Mechanical Ventilation No Load Heat Addition Energy [J]
Heating that would be provided directly to zone by ventilation air. Ventilation occurred with no zone load.
2. Zone Mechanical Ventilation Heating Load Increase Energy [J]
The increase in zone heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
3. Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy [J]
The heating load that would occur once ventilation air met the zone cooling load and continued to overcool the zone. No system effects are accounted for.
4. Zone Mechanical Ventilation Heating Load Decrease Energy [J]
The decrease in zone heating load that would occur as a result of ventilation air introduced directly into the zone. No system effects are accounted for.
The output variables are calculated by comparing the zone ventilation load with the zone cooling or heating load. ‘Ventilation cooling’ decreases the zone cooling load until the cooling load has been eliminated. The remaining ‘ventilation cooling’ is reported as ‘overcooling’. ‘Overheating’ is calculated in the same manner. The actual system operation, which determines whether or not an ‘overcooling’ or ‘overheating’ load actually results in increased energy consumption, is not considered in the calculation of these output variables.
The ventilation zone load output variables are shown in Table. The variables report the maximum potential “cost” or “benefit” of ventilation air introduced directly into the zone.
The example syntax below shows the basic ventilation load variables reported on a monthly basis.
Output:Variable,*,Zone Mechanical Ventilation Heating Load Increase Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Heating Load Decrease Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation No Load Heat Addition Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Cooling Load Increase Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation Cooling Load Decrease Energy,monthly;
Output:Variable,*,Zone Mechanical Ventilation No Load Heat Removal Energy,monthly;
Reporting on a timestep or hourly level would produce a detailed report with variables intermingled with the other output variables that might be requested in the input file.
Another method will more easily encapsulate the report:
This combination will report the ventilation loads on a monthly basis in a HTML style report that can be easily read in a web browser. Review the Output:Table:Monthly object for other methods of display or further options on this report item.
Systems Level Reporting[LINK]
Most output variables are a single entity reporting. Meters are a combination of like variables – specifically for Energy Consumption. This section introduces a slightly different concept – where output variables described herein are a combination of several similar items – specifically targeted at HVAC/System level reporting. This reporting is coupled with an Air Loop (ref: AirLoopHVAC)
All items shown in this section are typical “output variables” and can be reported with the Output:Variable object.
Or, as is shown by example here, perhaps a more readable form is to generate them in Tabular Form with the “Output:Table:Monthly” object.
View of System Level Reporting
System Loads Outputs[LINK]
In this category, the total system load is reported. Two aspects are reported here: Heating and Cooling. The following two variables report the heat energy that system components (including packaged equipment, fans, main coils, reheat coils, humidifiers, desiccant dehumidifiers, evaporative coolers and heat exchangers) add or remove from the air loop. Each variable within these grouping wil
Air System Total Heating Energy[LINK]
Heat Addition to the Air Loop (Sum of all components) in Joules
Air System Total Cooling Energy[LINK]
Heat Removal from the Air Loop (Sum of all components) in Joules
In ‘Output:Table:Monthly’ format shown below.
System Energy Use Outputs[LINK]
System Energy Use consists of six output variables that report the total energy (in Joules) and water consumption (in m3) for all system components and including packaged equipment, fans, main coils, reheat coils, humidifiers, desiccant dehumidifiers, and evaporative coolers. The output variables shown below show hot and cold water, steam, electric and gas energy. Hot and cold water energy includes all ‘district cooling’ and ‘district heating’ energy.
Air System Hot Water Energy[LINK]
Hot Water Consumption for the system (Joules).
Air System Steam Energy[LINK]
Steam Consumption for the system (Joules).
Air System Chilled Water Energy[LINK]
Chilled Water Consumption for the system (Joules).
Air System Electric Energy[LINK]
Electric Consumption for the system (Joules).
Air System Gas Energy[LINK]
Gas (Natural Gas and Propane) Consumption for the system (Joules).
Air System Water Volume[LINK]
Water Consumption for the system (humidifiers and evaporative coolers) (m3).
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Energy and Water Use”.
System Component Loads Outputs[LINK]
Reporting System Component Loads shows the energy transferred to or extracted from the air loop by system component type. Fans, Cooling Coils, Heating Coils, Heat exchangers, humidifiers, evaporative coolers, and desiccant dehumidifiers show heat transfer rates in Joules. The components may be located in outdoor air systems bundled with packaged equipment or specified as stand-alone components. The reporting accounts for both main branch and reheat coils.
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Component Loads”.
Air System Fan Air Heating Energy[LINK]
Energy added to the air loop by Fans (Joules)
Air System Cooling Coil Total Cooling Energy[LINK]
Energy removed from air loop by Cooling Coils (Joules)
Air System Heating Coil Total Heating Energy[LINK]
Energy added to air loop by Heating Coils (Joules)
Air System Heat Exchanger Total Heating Energy[LINK]
Energy added to air loop by air-to-air heat recovery heat exchangers (Joules)
Air System Heat Exchanger Total Cooling Energy[LINK]
Energy removed from air loop by air-to-air heat recovery heat exchangers (Joules)
Air System Humidifier Total Heating Energy[LINK]
Energy added to air loop by humidifiers (Joules)
Air System Evaporative Cooler Total Cooling Energy[LINK]
Energy removed from air loop by evaporative coolers (Joules)
Air System Desiccant Dehumidifier Total Cooling Energy[LINK]
Energy removed from air loop by desiccant dehumidifiers (Joules)
Air System Solar Collector Total Heating Energy[LINK]
Energy added to air loop by solar collectors (Joules)
Air System Solar Collector Total Cooling Energy[LINK]
Energy removed from air loop by solar collectors (Joules)
Air System User Defined Air Terminal Total Heating Energy[LINK]
Energy added to air loop by user defined air terminal units (Joules)
Air System User Defined Air Terminal Total Cooling Energy[LINK]
Energy removed from air loop by user defined air terminal units (Joules)
System Component Energy Use Outputs[LINK]
Reporting System Component Energy Use consists of eleven output variables that report the total energy consumption (in Joules) of system components by energy type and coil type. Electric energy consumption is reported for fans, heating and cooling coils in packaged (DX) systems, electric resistance heating coils, humidifiers, evaporative coolers and desiccant dehumidifiers.
Air System Fan Electric Energy[LINK]
Electric consumption for fans. (Joules)
Air System Heating Coil Hot Water Energy[LINK]
Consumption for heating coil hot water (both purchased and plant supplied) (Joules)
Air System Cooling Coil Chilled Water Energy[LINK]
Consumption for cooling coil chilled water (both purchased and plant supplied) (Joules)
Air System DX Heating Coil Electric Energy[LINK]
Compressor plus condenser fan electricity use. (Joules)
Air System DX Cooling Coil Electric Energy[LINK]
Compressor plus condenser fan electricity use. (Joules)
Air System Heating Coil Electric Energy[LINK]
Electricity consumption for the heating coil. (Joules)
Air System Heating Coil Gas Energy[LINK]
Gas (Propane and Natural Gas) consumption for the heating coil. (Joules)
Air System Heating Coil Steam Energy[LINK]
Steam consumption for the heating coil (steam coils). (Joules)
Air System Humidifier Electric Energy[LINK]
Electricity consumption for the humidifiers. (Joules)
Air System Evaporative Cooler Electric Energy[LINK]
Electricity consumption for the evaporative coolers. (Joules)
Air System Desiccant Dehumidifier Electric Energy[LINK]
Electricity consumption for the desiccant dehumidifiers. (Joules)
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop System Component Energy Use”.
Overall Air Loop Syntax[LINK]
A map for Air Loop input syntax is shown in the following diagram.
Air Loop Input Syntax Map
AirLoopHVAC:ControllerList[LINK]
The syntax for the AirLoopHVAC:ControllerList definition is shown below. As with other lists in EnergyPlus input, the object title and identifying name are followed by type-name pairs. In this case, the types are controller types. The order in which controllers appear on this list also define the priority as described below. The identifying name refers back to the name recorded in the AirLoopHVAC statement.
Inputs[LINK]
Field: Name[LINK]
The user designated unique name of an instance of a Controller List. Any object referencing this Controller List will do so using this name.
Field Set (Object Type, Controller Name) up to 8[LINK]
After the identifying name, input for the controller list consists of up to 8 pairs of data items: a controller type and a controller name. The first controller listed has the highest priority, the second the second highest priority, and so forth.
Field: Controller <x> Object Type[LINK]
The type of controller. This should be a key word defining a class of controllers such as Controller:WaterCoil.
Field: Controller <x> Name[LINK]
The name of a controller object (such as a Controller:WaterCoil) defined elsewhere in the input file.
An example of this statement in an IDF is:
AvailabilityManagerAssignmentList[LINK]
The AvailabilityManagerAssignmentList defines the applicable managers used for an AirLoopHVAC or PlantLoop. The priority of availability managers is based on a set of rules and are specific to the type of loop. The output from each Availability Manager is an availability status flag. This flag can have the values NoAction, ForceOff, CycleOn, or CycleOnZoneFansOnly (used only for air loops). The availability status flags for the Availability Managers referenced by an air or plant loop are used to set the availability status flag for each loop. For the air loops, ForceOff takes precedence: if any of the loop’s availability managers are showing status ForceOff, the loop status will be ForceOff. Next in precedence is CycleOnZoneFansOnly, followed by CycleOn, and NoAction. For the plant loops, there is no precedence among the Availability Manager status flag values. Instead, the first availability manager giving a status flag value other than NoAction sets the status for the loop. The Availability Managers are executed in Availability Manager List order.
Special rules also apply for which managers may be listed in a Availability Manager list. The Hybrid Ventilation Control Manager (object: AvailabilityManager:HybridVentilation) is a special type of manager and is never specified in a Availability Manager List (it is used stand-alone for a specific air loop). All other types of availability managers may be listed in the Availability Manager List used for AirLoopHVACs. For Plant Loops, the Night Cycle and Night Ventilation managers (objects: AvailabilityManager:NightCycle and AvailabilityManager:NightVentilation) are not allowed in the Availability Manager List.
Inputs[LINK]
Field: Name[LINK]
The name of the AvailabilityManagerAssignmentList object. This is referenced by AirLoopHVAC and PlantLoop objects.
Field Set (Availability Manager Object Type, Name)[LINK]
Managers are listed by pairs of data items: Availability Manager Object Type and Availability Manager Name. The managers are simulated down the list and calculate a control status for use by the AirLoopHVAC or PlantLoop. The priority of each manager used for a specific loop is based on the rules described above. Availability managers are not currently used for condenser loops. The availability managers, along with the AirLoopHVAC and PlantLoop object, report the control status calculated each simulation timestep. These output variables can be used to prioritize the managers according to the required control strategy. Six managers are accomodated in the list by default, however, this IDD specification is extensible. Additional pairs may be added by directly editing the IDD.
Field: Availability Manager <x> Object Type[LINK]
The key word defining the type of manager, e.g. AvailabilityManager:NightCycle.
Field: Availability Manager<x> Name[LINK]
The name of a AvailabilityManager object defined elsewhere in the input file.
An example of this statement in an IDF is:
AirLoopHVAC:OutdoorAirSystem[LINK]
The Outside Air System (object AirLoopHVAC:OutdoorAirSystem) is a subsystem of an AirLoopHVAC. It handles the mixed air portion of the primary air system: the system relief air, the outside air inlet, and any components and controllers associated with the system relief air and outside air streams. From the perspective of the primary air loop the Outside Air System is treated as a single component. As a subsystem, it can contain one or more components and controllers.
The input for the Outside Air System consists of a system name, a controller list name, an equipment list name, and an availability manager list name. The controller list simply lists, by type and unique name, all the controllers in the subsystem. The controllers will be simulated in list order. The equipment list lists all the components in the subsystem, by type and name. The equipment is simulated in list order. Finally, the availability manager list gives the type and name of the availability managers used by the subsystem.
The equipment inlet/outlet must be sequential with no loops - the simulation can only handle a straight-through air path, both on the primary air side and on the secondary air side, if any. Heat exchanger secondary air inlets need to be independent of the primary air stream – usually relief air is used.
Inputs[LINK]
Field: Name[LINK]
The unique, user assigned name for a single instance of an Outside Air System. Any other object referencing this Outside Air System will use this name.
Field: Name: Controller List Name[LINK]
This field is the name of a AirLoopHVAC:ControllerList object. A AirLoopHVAC:ControllerList is simply a list of controllers giving both controller name and type. This Controller List specifies all the controllers that will act on this outside air system. The order of the controllers in the list is significant: controllers are simulated sequentially in the order given in the Controller List. Typically the Controller List would contain a Controller:OutdoorAir. If there are chilled water or hot water coils in the outdoor air system, each such coil will need a Controller:WaterCoil.
Field: Outdoor Air Equipment List Name[LINK]
This field is the name of an AirLoopHVAC:OutdoorAirSystem:EquipmentList object. An AirLoopHVAC:OutdoorAirSystem:EquipmentList is simply a list of components giving both component name and type. This Outdoor Air Equipment List specifies all the components that will be simulated in this outside air system. The order of the components in the list is significant: components are simulated sequentially in the order given in the Outdoor Air Equipment List. Typically the equipment list would contain at least an OutdoorAir:Mixer. If there is more than one component, the components must be listed in order from the outside air to the OutdoorAir:Mixer (the OutdoorAir:Mixer is last).
Field: Availability Manager List Name[LINK]
This field is the name of a AvailabilityManagerAssignmentList object. An Availability Manager List is a list of Availability Managers giving both Availability Manager Object Type and Name. Use of this input is optional. This field may be omitted; it is not currently used by the program.
An IDF example, including the AirLoopHVAC, and the controller and equipment lists.
Outputs[LINK]
The impact of using outside air/mechanical ventilation is described in the section: Outdoor Air Ventilation Outputs.
AirLoopHVAC:OutdoorAirSystem:EquipmentList[LINK]
Used to specify the components in the outdoor air system. The components will be simulated in the order in which they occur in the list.
The following HVAC equipment types are allowed as outdoor air system equipment. The component matrix shows which coils and fans are allowed with which equipment models.
Inputs[LINK]
Field: Name[LINK]
The user designated unique name of an instance of an Air Loop Equipment List. Any object referencing this Air Loop Equipment List will do so using this name.
Field Set (Component Object Type,, Component Name) up to 8[LINK]
After the identifying name, the list consists of up to 8 pairs of data items:
Field: Component <x> Object Type[LINK]
This field specifies the keyword for the type of component used.
Field: Component <x> Name[LINK]
This field is the unique name of the component specified in the previous field. This named object must appear in the IDF.
An example from an IDF:
OutdoorAir:Node[LINK]
The OutdoorAir:Node object declares an HVAC system node for outdoor air conditions. The program automatically sets the air conditions at these nodes to correspond to the ambient environmental conditions at the beginning of every timestep. The outdoor air node is typically used as the inlet air node to an HVAC component such as the OutdoorAir:Mixer object. Multiple OutdoorAir:Node objects can be used in an input file, however, duplicate node names are not allowed.
The Height Above Ground field is used to adjust the weather file air conditions, e.g., outdoor dry-bulb and wet-bulb air temperatures, for atmospheric variation with height. This variation can become a significant factor when modeling tall buildings. See the Engineering Reference section on Atmospheric Variation for a description of the algorithm for variation of atmospheric properties with height. A blank entry or a value less than zero for this field indicates that the height will be ignored and the weather file conditions will be used.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions. OutdoorAir:Node modifies the weather file conditions if a height has been specified. OutdoorAir:NodeList does not have a height input and always uses the weather file conditions without modification. The same node name may not be used with both of these objects.
When declared in surface property objects SurfaceProperty:LocalEnvironment, in zone property objects ZoneProperty:LocalEnvironment, or as an external node in the airflow network calculation linking to a surface node AirflowNetwork:Multizone:Surface, the object can also be used to define local outdoor air conditions for surfaces, zones or air loop components. The local outdoor air conditions would be used in the EnergyPlus calculations for:
Convection coefficients used in the exterior surface heat balance
If the user declares a local surface outdoor air node to overwrite the surface level environmental data, the convection coefficients would be calculated based on the local outdoor air node data accordingly based on surface level outdoor dry-bulb temperature, humidity ratio and wind speed.
Zone air infiltration and simple ventilation
If the user declares a local zone outdoor air node to overwrite zone level environmental data, global environmental variables used in the subroutines for infiltration and ventilation calculation, including outdoor air temperature, humidity ratio, enthalpy, wind speed and direction, would be overwritten accordingly with zone level data.
External air nodes used in the AirFlowNetwork
When used in the airflow network for wind pressure calculation, global environmental variables used in the subroutines for wind pressure calculation, including outdoor air temperature, humidity ratio, air density, wind speed and direction, would be overwritten accordingly with local data.
When used in these cases, optional schedule inputs of local ambient air conditions, including dry-bulb temperature, wet-bulb temperature, wind velocity, and wind direction, can be defined in the optional fields. When used in the airflow network for wind pressure calculation, the wind pressure coefficient curve name and calculation details should also be defined.
Inputs[LINK]
Field: Name[LINK]
The unique name for this outdoor air node.
Field: Height Above Ground[LINK]
The height [m] of the node above ground level. A value greater than zero allows the weather file conditions, e.g., outdoor dry-bulb and wet-bulb air temperatures, to be adjusted according to atmospheric variation with height.
A blank entry or value less than zero indicates that the height will be ignored and the weather file conditions will be used.
Field: Drybulb Temperature Schedule Name[LINK]
This field is used to supply a schedule name of the local dry bulb temperature of this node. When the field is left blank, global values would be used in calculation.
Field: Wetbulb Temperature Schedule Name[LINK]
This field is used to supply a schedule name of the local wet bulb temperature of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Speed Schedule Name[LINK]
This field is used to supply a schedule name of the local wind speed of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Direction Schedule Name[LINK]
This field is used to supply a schedule name of the local wind direction of this node. When the field is left blank, global values would be used in calculation.
Field: Wind Pressure Coefficient Curve Name[LINK]
The name of a specific AirflowNetwork:MultiZone:WindPressureCoefficientValues object (which gives wind pressure coefficients for the façade as a function of angle of wind incident on the façade).
Field: Symmetric Wind Pressure Coefficient Curve[LINK]
This field is used to specify whether the pressure curve is symmetric or not. Yes for curves that should be evaluated from 0 to 180 degrees. No for curves that should be evaluated from 0 to 360 degrees.
Field: Wind Angle Type[LINK]
This field is used to specify whether the angle used to compute the wind pressure coefficient is absolute or relative. Relative for computing the angle between the wind direction and the surface azimuth. Absolute for using the wind direction angle directly.
An example IDF:
Outdoor Air Node outputs:[LINK]
The ambient dry-bulb, wet-bulb air temperature, wind speed and direction, and flow rate at the outdoor air node can be monitored using the system node output variables:
HVAC,Average,System Node Temperature [C]
HVAC,Average,System Node Wetbulb Temperature [C]
HVAC,Average,System Node Wind Speed [m/s]
HVAC,Average,System Node Wind Direction [degree]
HVAC,Average,System Node Mass Flow Rate [kg/s]
e.g.
OutdoorAir:NodeList[LINK]
The program needs to know which HVAC system nodes are inlets for outdoor air. Knowing this, the program can set the conditions at these nodes to the outdoor conditions at the start of each major timestep. The OutdoorAir:NodeList provides the means for specifying which nodes are outdoor air nodes.
The input is flexible: there may be one or more OutdoorAir:NodeList in each input file. Each list contains up to 25 names. The names can be the name of a unique HVAC system node, or the name of a Node List which will contain the actual node names. Duplicate node names are ignored.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions. OutdoorAir:Node modifies the weather file conditions if a height has been specified. OutdoorAir:NodeList does not have a height input and always uses the weather file conditions without modification. The same node name may not be used with both of these objects.
Inputs[LINK]
Field: Node or NodeList name[LINK]
The name of an HVAC system node or of a NodeList object. There can be up to 25 names.
An example IDF:
OutdoorAir:Mixer[LINK]
The OutdoorAir:Mixer is the most common component used in an outdoor air system. The outdoor air mixer has 2 inlet air streams: the system return air and the outdoor air. It has 2 outlet air streams: the system relief air and the mixed air. This is a passive component. It takes the inlet mass flows and conditions plus the relief air mass flow and calculates the mixed air flow rate and conditions (as well as the relief air conditions). The inlet and relief mass flow must be set outside the component – most commonly by an outdoor air controller. The OutdoorAir:Mixer can also be used in compound components such as a fan coil unit.
Input for this object is very simple: a unique name plus the node names of the 2 inlet nodes and the 2 outlet nodes.
Inputs[LINK]
Field: Name[LINK]
A unique user assigned name for a particular outdoor air mixer component. Any reference to this component by another object will use this name.
Field: Mixed Air Node Name[LINK]
The name of the HVAC system node which is the outlet for the mixed air stream.
Field: Outdoor Air Stream Node Name[LINK]
The name of the HVAC system node which is the inlet for the outdoor air stream.
Field: Relief Air Stream Node Name[LINK]
The name of the HVAC system node which is the outlet for the system relief air.
Field: Return Air Stream Node Name[LINK]
The name of the HVAC system node which is the inlet for the return air stream.
An IDF example:
Documentation content copyright © 1996-2017 The Board of Trustees of the University of Illinois and the Regents of the University of California through the Ernest Orlando Lawrence Berkeley National Laboratory. All rights reserved. EnergyPlus is a trademark of the US Department of Energy.
This documentation is made available under the EnergyPlus Open Source License v1.0.