Group – Air Path[LINK]
AirLoopHVAC:SupplyPath, AirLoopHVAC:ReturnPath[LINK]
The zone supply and return air paths are used to describe the configuration of the flow path that the supply air takes in moving from the main air handler to the zone terminal units and that the return air takes on leaving the zones and returning to the central return air duct. The air paths consist of a group of components AirLoopHVAC:ZoneSplitters and AirLoopHVAC:SupplyPlenums for the supply path and AirLoopHVAC:ReturnPlenums and AirLoopHVAC:ZoneMixers for the return path. The connectivity of the paths is established by the components node connections. There are no branches defined in the zone air path constructs.
For a typical single duct air system there will be one AirLoopHVAC:SupplyPath and one AirLoopHVAC:ReturnPath. A typical dual duct system would have 2 AirLoopHVAC:SupplyPaths one for the hot air and one for the cold air and 1 AirLoopHVAC:ReturnPath.
The AirLoopHVAC:SupplyPlenum component provides the capability to have supply air distributed to the conditioned zones through one or more plenum zones such as would occur in an underfloor air distribution system (UFAD). The AirLoopHVAC:ReturnPlenum component allows the program to model return air plenums. Of course plenums are always optional. The simplest AirLoopHVAC:SupplyPath would consist of only an AirLoopHVAC:ZoneSplitter; similarly the simplest return air path consists of a single AirLoopHVAC:ZoneMixer. A UFAD system supply air path might consist of a single AirLoopHVAC:ZoneSplitter connecting to multiple AirLoopHVAC:SupplyPlenums which in turn could each supply one or more conditioned zones. A system with return plenums would have an AirLoopHVAC:ReturnPath in which the conditioned zones connect to the return plenum inlets and the outlets of the return plenum connect to a single AirLoopHVAC:ZoneMixer.
Both the zone supply and return plenums are solved in the heat balance as thermal zones which couple through heat conduction with adjacent zones. Since they are solved as thermal zones the solution scheme involves the zone predictor-corrector technique which will lag the temperature at the system timestep in every zone. See Summary of Predictor-Corrector Procedure in the EnergyPlus Engineering Reference.
Below are the descriptions of the zone supply and return path statements. Note that each statement type has an identifying name, a single inlet/outlet node name, and a list of component type/name pairs. For a single zone being served by an air loop, the inlet to its air distribution unit and the zone return air outlet can be the zone equipment inlet and outlet nodes directly, thus eliminating the need to specify an AirLoopHVAC:SupplyPath and an AirLoopHVAC:ReturnPath.
AirLoopHVAC:SupplyPath[LINK]
The AirLoopHVAC:SupplyPath lists one or more AirLoopHVAC:ZoneSplitter and AirLoopHVAC:SupplyPlenum components comprising the path. The components are listed in flow order: upstream to downstream and may be in series, parallel, or both. Connectivity is established by means of the individual component inlet and outlet nodes.
Unique name to identify the supply air path..
Field: Supply Air Path Inlet Node Name[LINK]
The name of an inlet node for the zone equipment half of the air loop. This should be one of the nodes named in the AirLoopHVAC field: Demand Side Inlet Node Names.
Field Set Component Type and Name[LINK]
The remaining fields are sets of two repeated times: a component type and a name. These pairs of fields define the components on the supply air path.
Field: Component <#> Object Type[LINK]
Start of the component list for the AirLoopHVAC:SupplyPath. This field should contain either AirLoopHVAC:SupplyPlenum or AirLoopHVAC:ZoneSplitter.
Field: Component <#> Name[LINK]
Unique name of the AirLoopHVAC:SupplyPlenum or AirLoopHVAC:ZoneSplitter component.
AirLoopHVAC:ReturnPath[LINK]
The AirLoopHVAC:ReturnPath lists one or more AirLoopHVAC:ZoneMixer and AirLoopHVAC:ReturnPlenum components comprising the path. The components are listed in flow order: upstream to downstream and may be in series, parallel, or both. Connectivity is established by means of the individual component inlet and outlet nodes. At this time there can only be 1 AirLoopHVAC:ZoneMixer in an AirLoopHVAC:ReturnPath.
Unique name to identify the return air path.
Field: Return Air Path Outlet Node Name[LINK]
The name of the node that is the outlet to the air loop from the AirLoopHVAC:ReturnPath. This should be the same node named in the AirLoopHVAC field: Demand Side Outlet Node Name.
Field Set Component Type and Name[LINK]
The remaining fields are sets of two repeated times: a component type and a name. These pairs of fields define the components on the return air path.
Field: Component <#> Object Type[LINK]
Start of the component list for the AirLoopHVAC:ReturnPath. This field should contain either AirLoopHVAC:ReturnPlenum or AirLoopHVAC:ZoneMixer.
Field: Component <#> Name[LINK]
Unique name of the AirLoopHVAC:ReturnPlenum or AirLoopHVAC:ZoneMixer.
Example inputs are shown below
AirLoopHVAC:SupplyPath,
SupplyAirPath 1, !- Name
Zone Equip In Node, !- Supply Air Path Inlet Node Name
AirLoopHVAC:SupplyPlenum, !- Component 1 Object Type
Supply-Plenum-1, !- Component 1 Name
AirLoopHVAC:ZoneSplitter, !- Component 2 Object Type
Zone Supply Air Splitter 1; !- Component 2 Name
AirLoopHVAC:ReturnPath,
ReturnAirPath1, !- Name
PLENUM-1 Out Node, !- Return Air Path Outlet Node Name
Zone Return Plenum, !- Component 1 Object Type
Return-Plenum-1; !- Component 1 Name
AirLoopHVAC:ReturnPlenum[LINK]
The simple building shown in the figure below consists of a controlled zone and a return plenum zone that is used for the return air. This simple configuration contains a ground floor controlled zone with a window and a return plenum zone which handles the roof load. The return air plenum is a special type of component since there is both a heat balance connection and building description and a system airflow connection that transfers the airflow directly from the controlled zone to the return plenum zone in the system air simulation. The input described in this section is mainly just for the system airflow connections in the HVAC algorithms. In addition the return plenum zone must be fully input as a zone object for the heat balance calculation. The zone description needs to contain the wall descriptions - the interzone ceiling and floor, and for this simple case the roof. All the other attributes of a zone that can be specified in the building description can be used with a return plenum zone if necessary: scheduled loads, windows, etc.
After all the building zone attributes are specified, the AirLoopHVAC:ReturnPlenum object is specified and included as one of the named components in an AirLoopHVAC:ReturnPath.
A unique identifying name identifying the AirLoopHVAC:ReturnPlenum system component.
Field: Zone Name[LINK]
The zone name specified in the heat balance portion of the input. This piece of input connects the zone return plenum system component to the heat balance data structure.
Field: Zone Node Name[LINK]
The name of the zone node. The zone node name connects the heat balance data structure to the system airflow data structure through this node. This node name must be unique otherwise a warning is reported. Do not use the Zone Air Node Name specified in any ZoneHVAC:EquipmentConnections object, and since this zone is a plenum a ZoneHVAC:EquipmentConnections object is not required for the zone named in the previous field.
Field: Outlet Node Name[LINK]
The name of the return plenum outlet node. For the zone return plenum there is only one outlet node that can be specified.
Field: Induced Air Outlet Node or NodeList Name[LINK]
The name of an induced air outlet node or the name of a NodeList of such nodes. These nodes are to be used as the secondary inlet air nodes of powered induction terminal units (See AirTerminal:SingleDuct:SeriesPIU:Reheat and AirTerminal:SingleDuct:ParallelPIU:Reheat).
Field: Inlet <#> Node Name[LINK]
The name of a plenum inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 inlet node names.)
An IDF example of a zone return plenum component specification:
AirLoopHVAC:ReturnPlenum,
Return-Plenum-1, !- Name
PLENUM-1, !- Zone Name
PLENUM-1 Node, !- Zone Node Name
PLENUM-1 Out Node, !- Outlet Node Name
PLENUM-1 Induced Air Nodes, !- Induced Air Outlet Node or NodeList Name
SPACE1-1 Out Node, !- Inlet 1 Node Name
SPACE2-1 Out Node, !- Inlet 2 Node Name
SPACE3-1 Out Node, !- Inlet 3 Node Name
SPACE4-1 Out Node, !- Inlet 4 Node Name
SPACE5-1 Out Node; !- Inlet 5 Node Name
NodeList,
PLENUM-1 Induced Air Nodes, !- Name
SPACE1-1 ATU Sec Node, !- Node 1 Name
SPACE2-1 ATU Sec Node, !- Node 2 Name
SPACE3-1 ATU Sec Node, !- Node 3 Name
SPACE4-1 ATU Sec Node; !- Node 4 Name
Below is an example of the AirLoopHVAC:ReturnPath for the simple case shown above.
AirLoopHVAC:ReturnPath,
ReturnAirPath1, !- Name
PLENUM-1 Out Node, !- Return Air Path Outlet Node Name
AirLoopHVAC:ReturnPlenum, !- Component 1 Object Type
Return-Plenum-1; !- Component 1 Name
AirLoopHVAC:SupplyPlenum[LINK]
The building shown in the figure below consists of three controlled zones served by an AirLoopHVAC:SupplyPlenum beneath the floor.
The AirLoopHVAC:SupplyPlenum has a heat balance connection and building description, and a system airflow connection which transfers the airflow from the supply plenum zone to the controlled zones in the system simulation. The input described in this section is mainly just for the system airflow connections in the HVAC algorithms. In addition the supply plenum zone must be fully input in the building zone description. The supply plenum zone description needs to contain the wall descriptions, the interzone ceiling and floor, and the ground connection. All the other attributes of a zone that can be specified in the building description can be utilized with a supply plenum zone if necessary, i.e. scheduled loads, windows, etc.
After all the building zone attributes are specified, the AirLoopHVAC:SupplyPlenum object is specified and included as one of the named components in an AirLoopHVAC:SupplyPath.
A unique identifying name identifying the AirLoopHVAC:SupplyPlenum system component.
Field: Zone Name[LINK]
The zone name specified in the heat balance portion of the input. This piece of input connects the AirLoopHVAC:SupplyPlenum system component to the heat balance data structure.
Field: Zone Node Name[LINK]
The name of the zone node. The zone node name connects the heat balance data structure to the system airflow data structure through this node. This node name is defined by the user in the field Zone Air Node Name in the ZoneHVAC:EquipmentConnections object for the zone named in the previous field.
Field: Inlet Node Name[LINK]
The name of the inlet node to the supply plenum. The AirLoopHVAC:SupplyPlenum component can send air to many outlets, but there is only one inlet.
Field: Outlet <#> Node Name[LINK]
The name of a plenum outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 outlet node names.)
An IDF example of an AirLoopHVAC:SupplyPlenum component specification:
AirLoopHVAC:SupplyPlenum,
Supply Plenum 1, ! Name
SUPPLY PLENUM ZONE, ! Zone Name
Supply Plenum 1 Zone Node, ! Zone Node Name
Zone Equipment Inlet Node, ! Inlet Node Name
Supply Plenum 1 Outlet Node; ! Outlet 1 Node Name
Below is an example of the AirLoopHVAC:SupplyPath for the building shown above.
AirLoopHVAC:SupplyPath,
TermReheatSupplyPath, ! Name
Zone Equipment Inlet Node, ! Supply Air Path Inlet Node Name
AirLoopHVAC:SupplyPlenum, ! Component 1 Object Type
Supply Plenum 1, ! Component 1 Name
AirLoopHVAC:ZoneSplitter, ! Component 2 Object Type
Zone Supply Air Splitter; ! Component 2 Name
AirLoopHVAC:ExhaustSystem[LINK]
The AirLoopHVAC:ExhaustSystem and ZoneHVAC:ExhaustControl objects are used to describe the way that the exhaust air streams are configured. These objects provide a way for the exhaust air streams from multiple zones to be rerouted and recombined to form a new central exhausts. The exhaust system is composed of a central exhaust fan and a zone mixer).
The AirLoopHVAC:ExhaustSystem will take the following input fields:
The name of the exhaust system.
Field: Zone Mixer Name[LINK]
This is the name of the AirLoopHVAC:ZoneMixer object that connects the exhaust air streams from multiple zones. The zone mixer will have the inlet nodes for the exhaust system defined; and typically each inlet node must be the outlet node of a ZoneHVAC:ExhaustControl object.
Field: Fan Object Type[LINK]
This is the type of fan object for the central exhaust fan. The available choices are Fan:SystemModel or Fan:ComponentModel.
Field: Fan Name[LINK]
This is a required field for the name of the central exhaust fan.
An example of the AirLoopHVAC:ExhaustSystem input object is like this:
AirLoopHVAC:ExhaustSystem,
Central Exhaust 1, !- Name
AirLoopExhaustMixer1, !- Zone Mixer Name
Fan:SystemModel, !- Fan Object Type
CentralExhaustFan1; !- Fan Name
The following output will be added the to the new exhaust system:
HVAC,Average,Central Exhaust Fan Mass Flow Rate [kg/s]
HVAC,Average,Central Exhaust Fan Volumetric Flow Rate Standard [m3/s]
HVAC,Average,Central Exhaust Fan Volumetric Flow Rate Current [m3/s]
HVAC,Average,Central Exhaust Fan Power [W]
HVAC,Sum,Central Exhaust Fan Energy [J]
Central Exhaust Fan Mass Flow Rate [kg/s][LINK]
Mass flow rate of the central exhaust fan in [kg/s].
Central Exhaust Fan Volumetric Flow Rate Standard [m3/s][LINK]
Volumetric flow rate of the central exhaust fan in [m3/s] under standard conditions.
Central Exhaust Fan Volumetric Flow Rate Current [m3/s][LINK]
Volumetric flow rate of the central exhaust fan in [m3/s] under current fan outlet conditions.
Central Exhaust Fan Power [W][LINK]
Power consumption of the central exhaust fan in [W].
Central Exhaust Fan Energy [J][LINK]
Energy usage of the central exhaust fan in [J].
ZoneHVAC:ExhaustControl[LINK]
The input fields for the ZoneHVAC:ExhaustControl object are as follows.
This is the name of the ZoneHVAC:ExhaustControl.
Field: Availability Schedule Name[LINK]
This is the availability schedule name of the ZoneHVAC:ExhaustControl equipment. A schedule value of zero means off, and >0 means on. If the connected AirloopHVAC:ExhaustSystem is on, then this schedule may be used to turn on (or off) the ZoneHVAC:ExhaustControl system. If the connected AirloopHVAC:ExhaustSystem is off, then this ZoneHVAC:ExhaustControl system will be off, and this schedule will be ignored.
Field: Zone Name[LINK]
The name of the zone that the exhaust is located within.
Field: Inlet Node Name[LINK]
This is the inlet node name of the ZoneHVAC:ExhaustControl object. This should be an exhaust node of the zone.
Field: Outlet Node Name[LINK]
This is the outlet node name of the ZoneHVAC:ExhaustControl object. This node must be connected to an AirLoopHVAC:ExhaustSystem object as an inlet node.
Field: Design Flow Rate m3/s[LINK]
This numerical field is the design exhaust flow rate of the exhaust system in [m3/s]. This field could be autosized. The default is autosize.
Field: Flow Control Type[LINK]
This field is the control type on how the exhaust flows are controlled. The available choices are: Scheduled or FollowSupply. Scheduled means that the target exhaust flow rate will be the Design Flow Rate times the Flow Fraction Schedule. FollowSupply means that the target exhaust flow rate will be the current total flow rate at the node(s) specified in Supply Node or NodeList Name times the Flow Fraction Schedule. For both control types, if the central exhaust fan is not able to meet the total target exhaust flow rate for all of its inlets, then the flow rate will be reduced proportionally to match the available fan flow.
Field: Flow Fraction Schedule Name[LINK]
This is the schedule name for the exhaust flow fraction. If left empty, the default value is 1.0. This schedule is only applied for Flow Control Type - Schedules.
Field: Supply Node or NodeList Name[LINK]
This is the supply air node or nodelist name used for the FollowSupply flow control type.
Field: Minimum Zone Temperature Limit Schedule Name[LINK]
This will be the minimum zone temperature limit schedule name. It will be used to shut down the exhaust flow rate to the Minimum Flow Fraction Schedule value if the zone temperature get below this limit.
Field: Minimum Flow Fraction Schedule Name[LINK]
This is the schedule name for the minimum exhaust flow fraction. If left empty, the default value would be 1.0.
Field: Balanced Exhaust Fraction Schedule Name[LINK]
This field is optional. If it is not used, then all the exhaust air flow is assumed to be unbalanced by any simple air flows, such as infiltration, ventilation, or zone mixing. Unbalanced exhaust is then modeled as being provided by the outdoor air system in the central air system. The modeling of unbalanced will reduce the flow rates at the zone’s return air node by the flow rate that is being exhausted and will ensure that the outdoor air flow rate is sufficient to serve the exhaust. If this field is used, then enter the name of a schedule with fractional values between 0.0 and 1.0, inclusive. This fraction is applied to the exhaust fan flow rate and the model tracks the portion of the exhaust that is balanced. Balanced exhaust is then modeled as being provided by simple airflows and does not impact the central air system return air or outdoor air flow rates. For example, if a kitchen zone with an exhaust fan is designed to draw half of its make up air from a neighboring dining room and the other half from the outdoor air system, then a schedule value of 0.5 could be used here. This input field must be blank when the zone air flow balance is enforced. If user specifies a schedule and zone air flow balance is enforced, then EnergyPlus throws a warning error message, ignores the schedule and simulation continues.
An example of the ZoneHVAC:ExhaustControl input object is like this:
ZoneHVAC:ExhaustControl,
Zone2 Exhaust System, !-Name
HVACOperationSchd, !- Availability Schedule Name
Zone2, !- Zone Name
Zone2 Exhaust Node, !- Inlet Node Name
Zone2 ExhaustSystem Node, !- Outlet Node Name
0.1, !- Design Flow Rate {m3/s}
Scheduled, !- Flow Control Type (Scheduled or FollowSupply)
Zone2 Exhaust Flow Sched, !- Flow Fraction Schedule Name
, !- Supply Node or NodeList Name (used with FollowSupply control type)
, !- System Availability Manager Name
, !- Minimum Zone Temperature Limit Schedule Name
Zone2 Min Exhaust Flow Sched, !- Minimum Flow Fraction Schedule Name
FlowBalancedSched; !- Balanced Exhaust Fraction Schedule Name
AirLoopHVAC:ZoneSplitter[LINK]
The AirLoopHVAC:ZoneSplitter is a component that splits airflow from a single inlet to multiple outlets. This component must be referenced in an AirLoopHVAC:SupplyPath object. The input contains only node connection information.
Unique name for this zone splitter.
Field: Inlet Node Name[LINK]
The name of the single inlet node going into the splitter.
Field: Outlet <#> Node Name[LINK]
The name of a splitter outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 outlet node names.)
An example is shown below.
AirLoopHVAC:ZoneSplitter,
Zone Supply Air Splitter, ! Name
Zone Equipment Inlet Node, ! Inlet Node Name
Zone 1 Damper Inlet Node, ! Outlet 1 Node Name
Zone 2 Damper Inlet Node, ! Outlet 2 Node Name
Zone 3 Damper Inlet Node; ! Outlet 3 Node Name
AirLoopHVAC:ZoneMixer[LINK]
The AirLoopHVAC:ZoneMixer takes the air from multiple inlets and mixes the streams together to be sent out of a single outlet node. This is a simple process of summing flows and averaging the air properties. This component may be part of an air loop return path, an air loop exhaust system, or part of an induction terminal unit. When used as a return air mixer, this component must be listed in an AirLoopHVAC:ReturnPath object, and the inlets may be zone return air nodes or AirLoopHVAC:ReturnPlenum outlet nodes. When used as an exhaust air mixer, this component must be listed in an AirLoopHVAC:ExhaustSystem object, and the inlets may be zone exhaust air nodes. When used in an induction terminal unit (ref. AirTerminal:SingleDuct:SeriesPIU:Reheat, AirTerminal:SingleDuct:ParallelPIU:Reheat, and AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction), one inlet node is the supply (primary) air inlet from the central air handler, and the second inlet node is the induced (secondary) air inlet. These node names should match equivalent node names in the terminal unit.
Unique name for this zone mixer.
Field: Outlet Node Name[LINK]
The name of the single outlet node leaving the mixer.
Field: Inlet <#> Node Name[LINK]
The name of a mixer inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 inlet node names.)
An input example is shown below.
AirLoopHVAC:ZoneMixer,
Zone Return Air Mixer, ! Name
Return Air Mixer Outlet Node, ! Outlet Node Name
Zone 1 Outlet Node, ! Inlet 1 Node Name
Zone 2 Outlet Node, ! Inlet 2 Node Name
Zone 3 Outlet Node; ! Inlet 3 Node Name
AirLoopHVAC:DedicatedOutdoorAirSystem[LINK]
The AirLoopHVAC:DedicatedOutdoorAirSystem is a central dedicated outdoor air system (DOAS) and deliveres outdoor air to multiple AirLoopHVAC systems. The amount of delivered outdoor air is based on a sum of outdoor air flow rates from outdoor air stream nodes defined in the OutdoorAir:Mixer. These OutdoorAir:Mixer objects are a component of served multiple AirLoopHVAC systems. The central DOAS system also pretreates outdoor air before outdoor air distribution into multiple AirLoopHVAC, with given precool and preheat air conditions.
After the object name, the object has four fields to provide the name of AirLoopHVAC:OutdoorAirSystem, system availability, and names of AirLoopHVAC:Mixer and AirLoopHVAC:Splitter. The AirLoopHVAC:OutdoorAirSystem lists a controller to perform controls, and coils and fans to pretreat outdoor air before delivery to served AirLoopHVAC. The Availability Schedule determines times when a system is operationa or shutdownl. The AirLoopHVAC:Mixer and AirLoopHVAC:Splitter provide connection into distribution and relief nodes, respectively.
The next four fields requires inputs for pretreat air conditions, including precooling and preheating.
The last section lists the number of AirLoopHVAC to be served and names of served AirLoopHVAC objects.
This field is a unique, user assigned name for a single instance of an AirLoopHVAC:DedicatedOutdoorAirSystem object. Any other object referencing this AirLoopHVAC:DedicatedOutdoorAirSystem will use this name.
Field: AirLoopHVAC:OutdoorAirSystem Name[LINK]
This field is the name of a AirLoopHVAC:OutdoorAirSystem object. It handles outdoor air based on its own controller.
Availability Schedule Name[LINK]
The name of a schedule that specifies when the system is available.
Field: Preheat Design Temperature[LINK]
The design air temperature exiting the preheat coil (if any) in degrees Celsius.
Field: Preheat Design Humidity Ratio[LINK]
The design humidity ratio exiting the preheat coil (if any) in kilograms of water per kilogram of dry air. (kgWater/kgDryAir)
Field: Precool Design Temperature[LINK]
The design air temperature exiting the precooling coil (if any) in degrees Celsius.
Field: Precool Design Humidity Ratio[LINK]
The design humidity ratio exiting the precooling coil (if any) in kilograms of water per kilogram of dry air. (kgWater/kgDryAir)
Field: Number of AirLoopHVAC[LINK]
The number of AirLoopHVAC, which will be served by this central DOAS.
Field: AirLoopHVAC <#> Name[LINK]
The name of an AirLoopHVAC. There is no limit to the number of AirLoopHVACs, and there may be no duplicate AirLoopHVAC names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 20 AirLoopHVAC names.)
An example of this statement in an IDF is:
AirLoopHVAC:DedicatedOutdoorAirSystem,
AirLoopHVAC DOAS, !- Name
AirLoopDOAS OA system, !- AirLoopHVAC:OutdoorAirSystem Name
ALWAYS_ON, !- Availability Schedule Name
AirLoopDOASMixer, !- AirLoopHVAC:Mixer Name
AirLoopDOASSplitter, !- AirLoopHVAC:Splitter Name
4.5, !- Preheat Design Temperature {C}
0.004, !- Preheat Design Humidity Ratio {kgWater/kgDryAir}
17.5, !- Precool Design Temperature {C}
0.012, !- Precool Design Humidity Ratio {kgWater/kgDryAir}
5, !- Number of AirLoopHVAC
PSZ-AC:1, !- AirLoopHVAC 1 Name
PSZ-AC:2, !- AirLoopHVAC 2 Name
PSZ-AC:3, !- AirLoopHVAC 3 Name
PSZ-AC:4, !- AirLoopHVAC 4 Name
PSZ-AC:5; !- AirLoopHVAC 5 Name
AirLoopHVAC:Mixer[LINK]
The AirLoopHVAC:Mixer takes the air from multiple inlets and mixes the streams together to be sent out of a single outlet node. This is a simple process of summing flows and averaging the air properties. This component must be referenced in an AirLoopHVAC:DedicatedOutdoorAirSystem object. The multiple inlet nodes are relief nodes of OutdoorAir:Mixer, which is a component of AirLoopHVAC, served by the AirLoopHVAC:DedicatedOutdoorAirSystem object. The single outlet node is connected into either outdoor or a heat exchanger. The heat exchanger must be listed as a component in AirLoopHVAC:OutdoorAirSystem, referenced in the AirLoopHVAC:DedicatedOutdoorAirSystem object.
Unique name for this mixer.
Field: Outlet Node Name[LINK]
The name of the single outlet node leaving the mixer.
Field: Inlet <#> Node Name[LINK]
The name of a mixer inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 50 inlet node names.)
An input example is shown below.
AirLoopHVAC:Mixer,
AirLoopDOASMixer, !- Name
AirLoopDOASMixerOutlet, !- Outlet Node Name
PSZ-AC:1_OARelief Node, !- Inlet 1 Node Name
PSZ-AC:2_OARelief Node, !- Inlet 2 Node Name
PSZ-AC:3_OARelief Node, !- Inlet 3 Node Name
PSZ-AC:4_OARelief Node, !- Inlet 4 Node Name
PSZ-AC:5_OARelief Node; !- Inlet 5 Node Name
AirLoopHVAC:Splitter[LINK]
The AirLoopHVAC:Splitter is a component that splits airflow from a single inlet to multiple outlets. This component must be referenced in an AirLoopHVAC:DedicatedOutdoorAirSystem object. The input contains only node connection information. The multiple outlet nodes must be outdoor air stream nodes of OutdoorAir:Mixer, which is a component of AirLoopHVAC, served by the AirLoopHVAC:DedicatedOutdoorAirSystem object.
Unique name for this splitter.
Field: Inlet Node Name[LINK]
The name of the single inlet node going into the splitter.
Field: Outlet <#> Node Name[LINK]
The name of a splitter outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 50 outlet node names.)
An input example is shown below.
AirLoopHVAC:Splitter,
AirLoopDOASSplitter, !- Name
AirLoopDOASSplitterInlet, !- Inlet Node Name
PSZ-AC:1_OAInlet Node, !- Outlet 1 Node Name
PSZ-AC:2_OAInlet Node, !- Outlet 2 Node Name
PSZ-AC:3_OAInlet Node, !- Outlet 3 Node Name
PSZ-AC:4_OAInlet Node, !- Outlet 4 Node Name
PSZ-AC:5_OAInlet Node; !- Outlet 5 Node Name
Group – Air Path[LINK]
AirLoopHVAC:SupplyPath, AirLoopHVAC:ReturnPath[LINK]
The zone supply and return air paths are used to describe the configuration of the flow path that the supply air takes in moving from the main air handler to the zone terminal units and that the return air takes on leaving the zones and returning to the central return air duct. The air paths consist of a group of components AirLoopHVAC:ZoneSplitters and AirLoopHVAC:SupplyPlenums for the supply path and AirLoopHVAC:ReturnPlenums and AirLoopHVAC:ZoneMixers for the return path. The connectivity of the paths is established by the components node connections. There are no branches defined in the zone air path constructs.
For a typical single duct air system there will be one AirLoopHVAC:SupplyPath and one AirLoopHVAC:ReturnPath. A typical dual duct system would have 2 AirLoopHVAC:SupplyPaths one for the hot air and one for the cold air and 1 AirLoopHVAC:ReturnPath.
The AirLoopHVAC:SupplyPlenum component provides the capability to have supply air distributed to the conditioned zones through one or more plenum zones such as would occur in an underfloor air distribution system (UFAD). The AirLoopHVAC:ReturnPlenum component allows the program to model return air plenums. Of course plenums are always optional. The simplest AirLoopHVAC:SupplyPath would consist of only an AirLoopHVAC:ZoneSplitter; similarly the simplest return air path consists of a single AirLoopHVAC:ZoneMixer. A UFAD system supply air path might consist of a single AirLoopHVAC:ZoneSplitter connecting to multiple AirLoopHVAC:SupplyPlenums which in turn could each supply one or more conditioned zones. A system with return plenums would have an AirLoopHVAC:ReturnPath in which the conditioned zones connect to the return plenum inlets and the outlets of the return plenum connect to a single AirLoopHVAC:ZoneMixer.
Both the zone supply and return plenums are solved in the heat balance as thermal zones which couple through heat conduction with adjacent zones. Since they are solved as thermal zones the solution scheme involves the zone predictor-corrector technique which will lag the temperature at the system timestep in every zone. See Summary of Predictor-Corrector Procedure in the EnergyPlus Engineering Reference.
Below are the descriptions of the zone supply and return path statements. Note that each statement type has an identifying name, a single inlet/outlet node name, and a list of component type/name pairs. For a single zone being served by an air loop, the inlet to its air distribution unit and the zone return air outlet can be the zone equipment inlet and outlet nodes directly, thus eliminating the need to specify an AirLoopHVAC:SupplyPath and an AirLoopHVAC:ReturnPath.
AirLoopHVAC:SupplyPath[LINK]
The AirLoopHVAC:SupplyPath lists one or more AirLoopHVAC:ZoneSplitter and AirLoopHVAC:SupplyPlenum components comprising the path. The components are listed in flow order: upstream to downstream and may be in series, parallel, or both. Connectivity is established by means of the individual component inlet and outlet nodes.
Inputs[LINK]
Field: Name[LINK]
Unique name to identify the supply air path..
Field: Supply Air Path Inlet Node Name[LINK]
The name of an inlet node for the zone equipment half of the air loop. This should be one of the nodes named in the AirLoopHVAC field: Demand Side Inlet Node Names.
Field Set Component Type and Name[LINK]
The remaining fields are sets of two repeated times: a component type and a name. These pairs of fields define the components on the supply air path.
Field: Component <#> Object Type[LINK]
Start of the component list for the AirLoopHVAC:SupplyPath. This field should contain either AirLoopHVAC:SupplyPlenum or AirLoopHVAC:ZoneSplitter.
Field: Component <#> Name[LINK]
Unique name of the AirLoopHVAC:SupplyPlenum or AirLoopHVAC:ZoneSplitter component.
AirLoopHVAC:ReturnPath[LINK]
The AirLoopHVAC:ReturnPath lists one or more AirLoopHVAC:ZoneMixer and AirLoopHVAC:ReturnPlenum components comprising the path. The components are listed in flow order: upstream to downstream and may be in series, parallel, or both. Connectivity is established by means of the individual component inlet and outlet nodes. At this time there can only be 1 AirLoopHVAC:ZoneMixer in an AirLoopHVAC:ReturnPath.
Inputs[LINK]
Field: Name[LINK]
Unique name to identify the return air path.
Field: Return Air Path Outlet Node Name[LINK]
The name of the node that is the outlet to the air loop from the AirLoopHVAC:ReturnPath. This should be the same node named in the AirLoopHVAC field: Demand Side Outlet Node Name.
Field Set Component Type and Name[LINK]
The remaining fields are sets of two repeated times: a component type and a name. These pairs of fields define the components on the return air path.
Field: Component <#> Object Type[LINK]
Start of the component list for the AirLoopHVAC:ReturnPath. This field should contain either AirLoopHVAC:ReturnPlenum or AirLoopHVAC:ZoneMixer.
Field: Component <#> Name[LINK]
Unique name of the AirLoopHVAC:ReturnPlenum or AirLoopHVAC:ZoneMixer.
Example inputs are shown below
AirLoopHVAC:ReturnPlenum[LINK]
The simple building shown in the figure below consists of a controlled zone and a return plenum zone that is used for the return air. This simple configuration contains a ground floor controlled zone with a window and a return plenum zone which handles the roof load. The return air plenum is a special type of component since there is both a heat balance connection and building description and a system airflow connection that transfers the airflow directly from the controlled zone to the return plenum zone in the system air simulation. The input described in this section is mainly just for the system airflow connections in the HVAC algorithms. In addition the return plenum zone must be fully input as a zone object for the heat balance calculation. The zone description needs to contain the wall descriptions - the interzone ceiling and floor, and for this simple case the roof. All the other attributes of a zone that can be specified in the building description can be used with a return plenum zone if necessary: scheduled loads, windows, etc.
Illustration of Zone Return Plenum
After all the building zone attributes are specified, the AirLoopHVAC:ReturnPlenum object is specified and included as one of the named components in an AirLoopHVAC:ReturnPath.
Inputs[LINK]
Field: Name[LINK]
A unique identifying name identifying the AirLoopHVAC:ReturnPlenum system component.
Field: Zone Name[LINK]
The zone name specified in the heat balance portion of the input. This piece of input connects the zone return plenum system component to the heat balance data structure.
Field: Zone Node Name[LINK]
The name of the zone node. The zone node name connects the heat balance data structure to the system airflow data structure through this node. This node name must be unique otherwise a warning is reported. Do not use the Zone Air Node Name specified in any ZoneHVAC:EquipmentConnections object, and since this zone is a plenum a ZoneHVAC:EquipmentConnections object is not required for the zone named in the previous field.
Field: Outlet Node Name[LINK]
The name of the return plenum outlet node. For the zone return plenum there is only one outlet node that can be specified.
Field: Induced Air Outlet Node or NodeList Name[LINK]
The name of an induced air outlet node or the name of a NodeList of such nodes. These nodes are to be used as the secondary inlet air nodes of powered induction terminal units (See AirTerminal:SingleDuct:SeriesPIU:Reheat and AirTerminal:SingleDuct:ParallelPIU:Reheat).
Field: Inlet <#> Node Name[LINK]
The name of a plenum inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 inlet node names.)
An IDF example of a zone return plenum component specification:
Below is an example of the AirLoopHVAC:ReturnPath for the simple case shown above.
AirLoopHVAC:SupplyPlenum[LINK]
The building shown in the figure below consists of three controlled zones served by an AirLoopHVAC:SupplyPlenum beneath the floor.
Illustration of AirLoopHVAC:SupplyPlenum
The AirLoopHVAC:SupplyPlenum has a heat balance connection and building description, and a system airflow connection which transfers the airflow from the supply plenum zone to the controlled zones in the system simulation. The input described in this section is mainly just for the system airflow connections in the HVAC algorithms. In addition the supply plenum zone must be fully input in the building zone description. The supply plenum zone description needs to contain the wall descriptions, the interzone ceiling and floor, and the ground connection. All the other attributes of a zone that can be specified in the building description can be utilized with a supply plenum zone if necessary, i.e. scheduled loads, windows, etc.
After all the building zone attributes are specified, the AirLoopHVAC:SupplyPlenum object is specified and included as one of the named components in an AirLoopHVAC:SupplyPath.
Inputs[LINK]
Field: Name[LINK]
A unique identifying name identifying the AirLoopHVAC:SupplyPlenum system component.
Field: Zone Name[LINK]
The zone name specified in the heat balance portion of the input. This piece of input connects the AirLoopHVAC:SupplyPlenum system component to the heat balance data structure.
Field: Zone Node Name[LINK]
The name of the zone node. The zone node name connects the heat balance data structure to the system airflow data structure through this node. This node name is defined by the user in the field Zone Air Node Name in the ZoneHVAC:EquipmentConnections object for the zone named in the previous field.
Field: Inlet Node Name[LINK]
The name of the inlet node to the supply plenum. The AirLoopHVAC:SupplyPlenum component can send air to many outlets, but there is only one inlet.
Field: Outlet <#> Node Name[LINK]
The name of a plenum outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 outlet node names.)
An IDF example of an AirLoopHVAC:SupplyPlenum component specification:
Below is an example of the AirLoopHVAC:SupplyPath for the building shown above.
AirLoopHVAC:ExhaustSystem[LINK]
The AirLoopHVAC:ExhaustSystem and ZoneHVAC:ExhaustControl objects are used to describe the way that the exhaust air streams are configured. These objects provide a way for the exhaust air streams from multiple zones to be rerouted and recombined to form a new central exhausts. The exhaust system is composed of a central exhaust fan and a zone mixer).
Inputs[LINK]
The AirLoopHVAC:ExhaustSystem will take the following input fields:
Field: Name[LINK]
The name of the exhaust system.
Field: Zone Mixer Name[LINK]
This is the name of the AirLoopHVAC:ZoneMixer object that connects the exhaust air streams from multiple zones. The zone mixer will have the inlet nodes for the exhaust system defined; and typically each inlet node must be the outlet node of a ZoneHVAC:ExhaustControl object.
Field: Fan Object Type[LINK]
This is the type of fan object for the central exhaust fan. The available choices are Fan:SystemModel or Fan:ComponentModel.
Field: Fan Name[LINK]
This is a required field for the name of the central exhaust fan.
An example of the AirLoopHVAC:ExhaustSystem input object is like this:
Outputs[LINK]
The following output will be added the to the new exhaust system:
HVAC,Average,Central Exhaust Fan Mass Flow Rate [kg/s]
HVAC,Average,Central Exhaust Fan Volumetric Flow Rate Standard [m3/s]
HVAC,Average,Central Exhaust Fan Volumetric Flow Rate Current [m3/s]
HVAC,Average,Central Exhaust Fan Power [W]
HVAC,Sum,Central Exhaust Fan Energy [J]
Central Exhaust Fan Mass Flow Rate [kg/s][LINK]
Mass flow rate of the central exhaust fan in [kg/s].
Central Exhaust Fan Volumetric Flow Rate Standard [m3/s][LINK]
Volumetric flow rate of the central exhaust fan in [m3/s] under standard conditions.
Central Exhaust Fan Volumetric Flow Rate Current [m3/s][LINK]
Volumetric flow rate of the central exhaust fan in [m3/s] under current fan outlet conditions.
Central Exhaust Fan Power [W][LINK]
Power consumption of the central exhaust fan in [W].
Central Exhaust Fan Energy [J][LINK]
Energy usage of the central exhaust fan in [J].
ZoneHVAC:ExhaustControl[LINK]
The input fields for the ZoneHVAC:ExhaustControl object are as follows.
Inputs[LINK]
Field: Name[LINK]
This is the name of the ZoneHVAC:ExhaustControl.
Field: Availability Schedule Name[LINK]
This is the availability schedule name of the ZoneHVAC:ExhaustControl equipment. A schedule value of zero means off, and >0 means on. If the connected AirloopHVAC:ExhaustSystem is on, then this schedule may be used to turn on (or off) the ZoneHVAC:ExhaustControl system. If the connected AirloopHVAC:ExhaustSystem is off, then this ZoneHVAC:ExhaustControl system will be off, and this schedule will be ignored.
Field: Zone Name[LINK]
The name of the zone that the exhaust is located within.
Field: Inlet Node Name[LINK]
This is the inlet node name of the ZoneHVAC:ExhaustControl object. This should be an exhaust node of the zone.
Field: Outlet Node Name[LINK]
This is the outlet node name of the ZoneHVAC:ExhaustControl object. This node must be connected to an AirLoopHVAC:ExhaustSystem object as an inlet node.
Field: Design Flow Rate m3/s[LINK]
This numerical field is the design exhaust flow rate of the exhaust system in [m3/s]. This field could be autosized. The default is autosize.
Field: Flow Control Type[LINK]
This field is the control type on how the exhaust flows are controlled. The available choices are: Scheduled or FollowSupply. Scheduled means that the target exhaust flow rate will be the Design Flow Rate times the Flow Fraction Schedule. FollowSupply means that the target exhaust flow rate will be the current total flow rate at the node(s) specified in Supply Node or NodeList Name times the Flow Fraction Schedule. For both control types, if the central exhaust fan is not able to meet the total target exhaust flow rate for all of its inlets, then the flow rate will be reduced proportionally to match the available fan flow.
Field: Flow Fraction Schedule Name[LINK]
This is the schedule name for the exhaust flow fraction. If left empty, the default value is 1.0. This schedule is only applied for Flow Control Type - Schedules.
Field: Supply Node or NodeList Name[LINK]
This is the supply air node or nodelist name used for the FollowSupply flow control type.
Field: Minimum Zone Temperature Limit Schedule Name[LINK]
This will be the minimum zone temperature limit schedule name. It will be used to shut down the exhaust flow rate to the Minimum Flow Fraction Schedule value if the zone temperature get below this limit.
Field: Minimum Flow Fraction Schedule Name[LINK]
This is the schedule name for the minimum exhaust flow fraction. If left empty, the default value would be 1.0.
Field: Balanced Exhaust Fraction Schedule Name[LINK]
This field is optional. If it is not used, then all the exhaust air flow is assumed to be unbalanced by any simple air flows, such as infiltration, ventilation, or zone mixing. Unbalanced exhaust is then modeled as being provided by the outdoor air system in the central air system. The modeling of unbalanced will reduce the flow rates at the zone’s return air node by the flow rate that is being exhausted and will ensure that the outdoor air flow rate is sufficient to serve the exhaust. If this field is used, then enter the name of a schedule with fractional values between 0.0 and 1.0, inclusive. This fraction is applied to the exhaust fan flow rate and the model tracks the portion of the exhaust that is balanced. Balanced exhaust is then modeled as being provided by simple airflows and does not impact the central air system return air or outdoor air flow rates. For example, if a kitchen zone with an exhaust fan is designed to draw half of its make up air from a neighboring dining room and the other half from the outdoor air system, then a schedule value of 0.5 could be used here. This input field must be blank when the zone air flow balance is enforced. If user specifies a schedule and zone air flow balance is enforced, then EnergyPlus throws a warning error message, ignores the schedule and simulation continues.
An example of the ZoneHVAC:ExhaustControl input object is like this:
AirLoopHVAC:ZoneSplitter[LINK]
The AirLoopHVAC:ZoneSplitter is a component that splits airflow from a single inlet to multiple outlets. This component must be referenced in an AirLoopHVAC:SupplyPath object. The input contains only node connection information.
Inputs[LINK]
Field: Name[LINK]
Unique name for this zone splitter.
Field: Inlet Node Name[LINK]
The name of the single inlet node going into the splitter.
Field: Outlet <#> Node Name[LINK]
The name of a splitter outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 outlet node names.)
An example is shown below.
AirLoopHVAC:ZoneMixer[LINK]
The AirLoopHVAC:ZoneMixer takes the air from multiple inlets and mixes the streams together to be sent out of a single outlet node. This is a simple process of summing flows and averaging the air properties. This component may be part of an air loop return path, an air loop exhaust system, or part of an induction terminal unit. When used as a return air mixer, this component must be listed in an AirLoopHVAC:ReturnPath object, and the inlets may be zone return air nodes or AirLoopHVAC:ReturnPlenum outlet nodes. When used as an exhaust air mixer, this component must be listed in an AirLoopHVAC:ExhaustSystem object, and the inlets may be zone exhaust air nodes. When used in an induction terminal unit (ref. AirTerminal:SingleDuct:SeriesPIU:Reheat, AirTerminal:SingleDuct:ParallelPIU:Reheat, and AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction), one inlet node is the supply (primary) air inlet from the central air handler, and the second inlet node is the induced (secondary) air inlet. These node names should match equivalent node names in the terminal unit.
Inputs[LINK]
Field: Name[LINK]
Unique name for this zone mixer.
Field: Outlet Node Name[LINK]
The name of the single outlet node leaving the mixer.
Field: Inlet <#> Node Name[LINK]
The name of a mixer inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 500 inlet node names.)
An input example is shown below.
AirLoopHVAC:DedicatedOutdoorAirSystem[LINK]
The AirLoopHVAC:DedicatedOutdoorAirSystem is a central dedicated outdoor air system (DOAS) and deliveres outdoor air to multiple AirLoopHVAC systems. The amount of delivered outdoor air is based on a sum of outdoor air flow rates from outdoor air stream nodes defined in the OutdoorAir:Mixer. These OutdoorAir:Mixer objects are a component of served multiple AirLoopHVAC systems. The central DOAS system also pretreates outdoor air before outdoor air distribution into multiple AirLoopHVAC, with given precool and preheat air conditions.
After the object name, the object has four fields to provide the name of AirLoopHVAC:OutdoorAirSystem, system availability, and names of AirLoopHVAC:Mixer and AirLoopHVAC:Splitter. The AirLoopHVAC:OutdoorAirSystem lists a controller to perform controls, and coils and fans to pretreat outdoor air before delivery to served AirLoopHVAC. The Availability Schedule determines times when a system is operationa or shutdownl. The AirLoopHVAC:Mixer and AirLoopHVAC:Splitter provide connection into distribution and relief nodes, respectively.
The next four fields requires inputs for pretreat air conditions, including precooling and preheating.
The last section lists the number of AirLoopHVAC to be served and names of served AirLoopHVAC objects.
Inputs[LINK]
Field: Name[LINK]
This field is a unique, user assigned name for a single instance of an AirLoopHVAC:DedicatedOutdoorAirSystem object. Any other object referencing this AirLoopHVAC:DedicatedOutdoorAirSystem will use this name.
Field: AirLoopHVAC:OutdoorAirSystem Name[LINK]
This field is the name of a AirLoopHVAC:OutdoorAirSystem object. It handles outdoor air based on its own controller.
Availability Schedule Name[LINK]
The name of a schedule that specifies when the system is available.
Field: Preheat Design Temperature[LINK]
The design air temperature exiting the preheat coil (if any) in degrees Celsius.
Field: Preheat Design Humidity Ratio[LINK]
The design humidity ratio exiting the preheat coil (if any) in kilograms of water per kilogram of dry air. (kgWater/kgDryAir)
Field: Precool Design Temperature[LINK]
The design air temperature exiting the precooling coil (if any) in degrees Celsius.
Field: Precool Design Humidity Ratio[LINK]
The design humidity ratio exiting the precooling coil (if any) in kilograms of water per kilogram of dry air. (kgWater/kgDryAir)
Field: Number of AirLoopHVAC[LINK]
The number of AirLoopHVAC, which will be served by this central DOAS.
Field: AirLoopHVAC <#> Name[LINK]
The name of an AirLoopHVAC. There is no limit to the number of AirLoopHVACs, and there may be no duplicate AirLoopHVAC names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 20 AirLoopHVAC names.)
An example of this statement in an IDF is:
AirLoopHVAC:Mixer[LINK]
The AirLoopHVAC:Mixer takes the air from multiple inlets and mixes the streams together to be sent out of a single outlet node. This is a simple process of summing flows and averaging the air properties. This component must be referenced in an AirLoopHVAC:DedicatedOutdoorAirSystem object. The multiple inlet nodes are relief nodes of OutdoorAir:Mixer, which is a component of AirLoopHVAC, served by the AirLoopHVAC:DedicatedOutdoorAirSystem object. The single outlet node is connected into either outdoor or a heat exchanger. The heat exchanger must be listed as a component in AirLoopHVAC:OutdoorAirSystem, referenced in the AirLoopHVAC:DedicatedOutdoorAirSystem object.
Inputs[LINK]
Field: Name[LINK]
Unique name for this mixer.
Field: Outlet Node Name[LINK]
The name of the single outlet node leaving the mixer.
Field: Inlet <#> Node Name[LINK]
The name of a mixer inlet node. There is no limit to the number of inlet nodes, and there may be no duplicate inlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 50 inlet node names.)
An input example is shown below.
AirLoopHVAC:Splitter[LINK]
The AirLoopHVAC:Splitter is a component that splits airflow from a single inlet to multiple outlets. This component must be referenced in an AirLoopHVAC:DedicatedOutdoorAirSystem object. The input contains only node connection information. The multiple outlet nodes must be outdoor air stream nodes of OutdoorAir:Mixer, which is a component of AirLoopHVAC, served by the AirLoopHVAC:DedicatedOutdoorAirSystem object.
Inputs[LINK]
Field: Name[LINK]
Unique name for this splitter.
Field: Inlet Node Name[LINK]
The name of the single inlet node going into the splitter.
Field: Outlet <#> Node Name[LINK]
The name of a splitter outlet node. There is no limit to the number of outlet nodes, and there may be no duplicate outlet node names. This object is extensible, so additional fields of this type can be added to the end of this object. (Note that some EnergyPlus editing tools may allow only 50 outlet node names.)
An input example is shown below.
Documentation content copyright © 1996-2022 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.