Skip to content
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

VAV design minimum cooling air flow fraction > 1.0 when system adjusts zone flows #6327

Closed
5 tasks done
mjwitte opened this issue Sep 20, 2017 · 1 comment
Closed
5 tasks done
Labels
PriorityHigh This defect or feature has been declared high priority

Comments

@mjwitte
Copy link
Contributor

mjwitte commented Sep 20, 2017

Issue overview

   ************* SizeHVACSingleDuct: Potential issue with equipment sizing for AirTerminal:SingleDuct:VAV:NoReheat = "CORE_BOTTOM ATU".
   **   ~~~   ** User-Specified Minimum Cooling Air Flow Fraction of 1.00000 [m3/s]
   **   ~~~   ** differs from Design Size Minimum Cooling Air Flow Fraction of 1.47043 [m3/s]
   **   ~~~   ** This may, or may not, indicate mismatched component sizes.

Pretty sure this came is as a result of #6140.

Preliminary look at this says it's because system sizing is using ventilation requirement so the original cooling vol flow rate has been reduced. But then why is the DesCoolVolFlowMin > the OA requirement which should result in a 1.0 min frac.
One solution is in SingleDuct::SizeSys around line 2116, MinAirFlowFracDes should be limited to no more that 1.0.
That's probably useful, but either DesCoolVolFlowMin or Sys.MaxAirVolFlowRate is wrong at this point.

  • Also, noticed there are twice as many TermUnitSizing objects as zones when debugging.
    That's correct. There is one TermUnitsizing object for each zone inlet node, so if there is zone equipment there will be extra instances of TermUnitSizing.

Details

Some additional details for this issue (if relevant):

  • Platform (Operating system, version)
  • Version of EnergyPlus 8.8.0 9bd43c6

Checklist

Add to this list or remove from it as applicable. This is a simple templated set of guidelines.

@Myoldmopar
Copy link
Member

Closed via #6338

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PriorityHigh This defect or feature has been declared high priority
Projects
None yet
Development

No branches or pull requests

2 participants