-
Notifications
You must be signed in to change notification settings - Fork 478
Fix 5ZoneNightVent3.idf, and test FanPerformance:NightVentilation #11595
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
Changes from all commits
2361236
50557bd
17aeb8e
b4a57b7
9d38ab1
a19c0be
f8e0c15
a55462a
ceb9831
2d0f08b
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51482,15 +51482,16 @@ Fan:ZoneExhaust, | |
| FanPerformance:NightVentilation, | ||
| \memo Specifies an alternate set of performance parameters for a fan. These alternate | ||
| \memo parameters are used when a system manager (such as AvailabilityManager:NightVentilation) | ||
| \memo sets a specified flow rate. May be used with Fan:ConstantVolume, Fan:VariableVolume and | ||
| \memo Fan:ComponentModel. If the fan model senses that a fixed flow rate has been set, it | ||
| \memo sets a specified flow rate. May be used with Fan:ConstantVolume, Fan:VariableVolume, | ||
| \memo Fan:ZoneExhaust, and Fan:OnOff (not Fan:ComponentModel). Fan:SystemModel has its own | ||
| \memo night ventilation settings. If the fan model senses that a fixed flow rate has been set, it | ||
| \memo will use these alternate performance parameters. It is assumed that the fan will | ||
| \memo run at a fixed speed in the alternate mode. | ||
| A1 , \field Fan Name | ||
| \required-field | ||
| \type object-list | ||
| \object-list FansCVandVAV | ||
| \object-list FansComponentModel | ||
|
Comment on lines
-51492
to
-51493
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The docs say "At this time, it can be used with Fan:ConstantVolume, Fan:VariableVolume, Fan:ZoneExhaust, Fan:OnOff and Fan:SystemModel fans, but not with Fan:ComponentModel fans." |
||
| \object-list FansCVandOnOffandVAV | ||
|
joseph-robertson marked this conversation as resolved.
|
||
| \object-list FansZoneExhaust | ||
| N1 , \field Fan Total Efficiency | ||
| \type real | ||
| \required-field | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,7 +6,7 @@ | |
| ! Basic file description: 1 story building divided into 4 exterior and one interior conditioned zones and return plenum. | ||
| ! | ||
| ! Highlights: Illustrates night ventilation using night ventilation system availability manager and | ||
| ! night ventilation fan performance. | ||
| ! Fan:SystemModel built-in night ventilation settings. | ||
| ! | ||
| ! Simulation Location/Run: FRESNO_CA_USA TMY2-93193, 2 design days, 1 run period, | ||
| ! Run Control executes the run period using the weather file | ||
|
|
@@ -86,7 +86,7 @@ | |
| ! object. We ventilate the building in the early morning hours. | ||
| ! The runperiod is a summer week in Fresno. We assume a ventilation rate of 1/3 the | ||
| ! supply air design value and adjust the night ventilation fan performance | ||
| ! (FanPerformance:NightVentilation) object inputs accordingly. | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This did not get updated starting with v8.7.0 when Fan:SystemModel was introduced and this test file was updated Fan:VariableVolume/FanPerformance:NightVentilation -> Fan:SystemModel. |
||
| ! (Fan:SystemModel) object inputs accordingly. | ||
| ! Successful night ventilation modeling depends | ||
| ! critically on getting the ventilation fan consumption right. In | ||
| ! this case, we see no benefit with night ventilation compared to the | ||
|
|
@@ -1652,6 +1652,8 @@ | |
| For: AllDays, !- Field 2 | ||
| Until: 24:00,18.; !- Field 3 | ||
|
|
||
| Schedule:Constant,AlwaysOn,On/Off,1.0; | ||
|
|
||
| People, | ||
| SPACE1-1 People 1, !- Name | ||
| SPACE1-1, !- Zone or ZoneList or Space or SpaceList Name | ||
|
|
@@ -3104,7 +3106,7 @@ | |
|
|
||
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE1-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name | ||
|
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the fix to see nonzero airflow on the demand side of the loop during night ventilation. See https://unmethours.com/question/103089/how-to-model-night-purge/ for more information.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This does reveal an issue with system control that was not noticed until now. This example file shows that the TU availability schedule affects night cycle operation, and system operation for that matter if the TU avail sch was more restrictive than the parent and fan avail schedules. In a parent object (e.g., UnitarySystem) the fan is controlled based on parent availability schedule and fan availability schedule. It appears that TU availability schedule also matters (and there are multiple TUs for air systems, at least 1 would need to be available). This was never noticed before maybe because TU avail schedules are typically always on or at least using the least restrictive schedule or maybe because night ventilation/cycle is used less often.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm throwing out a possible fix of TUs don't have avail schedules, they are always ON/available. Would that break anything? Would that restrict anything? Would that have less flexibility than is provided now? |
||
| SPACE1-1 Zone Coil Air In Node, !- Damper Air Outlet Node Name | ||
| SPACE1-1 ATU In Node, !- Air Inlet Node Name | ||
| autosize, !- Maximum Air Flow Rate {m3/s} | ||
|
|
@@ -3124,7 +3126,7 @@ | |
|
|
||
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE2-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name | ||
| SPACE2-1 Zone Coil Air In Node, !- Damper Air Outlet Node Name | ||
| SPACE2-1 ATU In Node, !- Air Inlet Node Name | ||
| autosize, !- Maximum Air Flow Rate {m3/s} | ||
|
|
@@ -3144,7 +3146,7 @@ | |
|
|
||
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE3-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name | ||
| SPACE3-1 Zone Coil Air In Node, !- Damper Air Outlet Node Name | ||
| SPACE3-1 ATU In Node, !- Air Inlet Node Name | ||
| autosize, !- Maximum Air Flow Rate {m3/s} | ||
|
|
@@ -3164,7 +3166,7 @@ | |
|
|
||
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE4-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name | ||
| SPACE4-1 Zone Coil Air In Node, !- Damper Air Outlet Node Name | ||
| SPACE4-1 ATU In Node, !- Air Inlet Node Name | ||
| autosize, !- Maximum Air Flow Rate {m3/s} | ||
|
|
@@ -3184,7 +3186,7 @@ | |
|
|
||
| AirTerminal:SingleDuct:VAV:Reheat, | ||
| SPACE5-1 VAV Reheat, !- Name | ||
| FanAvailSched, !- Availability Schedule Name | ||
| AlwaysOn, !- Availability Schedule Name | ||
| SPACE5-1 Zone Coil Air In Node, !- Damper Air Outlet Node Name | ||
| SPACE5-1 ATU In Node, !- Air Inlet Node Name | ||
| autosize, !- Maximum Air Flow Rate {m3/s} | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.