New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdoor Air Schedule Name in DesignSpecification:OutdoorAir does not work #10101
Comments
Taking the 5ZoneFanCoilDOASCool_rev.idf example you shared: AirTerminal:SingleDuct:VAV:NoReheat,
SPACE1-1 DOAS Air Terminal, !- Name
, !- Availability Schedule Name
SPACE1-1 DOAS Supply Inlet, !- Air Outlet Node Name
SPACE1-1 Zone Equip Inlet, !- Air Inlet Node Name
autosize, !- Maximum Air Flow Rate {m3/s}
- Constant, !- Zone Minimum Air Flow Input Method
- 1.0, !- Constant Minimum Air Flow Fraction
, !- Fixed Minimum Air Flow Rate {m3/s}
, !- Minimum Air Flow Fraction Schedule Name
+ SZ DSOA SPACE1-1; !- Design Specification Outdoor Air Object Name EnergyPlus/src/EnergyPlus/SingleDuct.cc Lines 3953 to 3962 in 07b51a2
CalcOAMassFlow correctly calculates it to be zero because of the OutdoorAirAvailSched. But:
So it's always going to be 0.12 anyways because the Minimum Air Flow Fraction is constant at 1.0. You'll see a change in results (but still not what you probably expect) if you set this to 0.0. If you want to model this properly, you also probably want to add a Controller:MechanicalVentilation object on the AirLoopHVAC's Controller:OutdoorAir, and list the zones + DSOAs onto that Controller:MV. |
This is working as designed, but could probably use some documentation updates to help clarify (I/O Reference and IDD notes). |
Issue overview
As per the title. Outdoor Air Schedule Name in DesignSpecification:OutdoorAir does not change outdoor air flow rate. Please refer to the Unmethours link below for more details on the issue.
Details
Some additional details for this issue (if relevant):
Checklist
Add to this list or remove from it as applicable. This is a simple templated set of guidelines.
The text was updated successfully, but these errors were encountered: