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

Allow Connector:Splitter and Connector:Mixer to be used to create bypass branch on AirLoopHVAC supply side #4358

Open
eringold opened this issue Jun 14, 2021 · 0 comments

Comments

@eringold
Copy link
Contributor

Enhancement Request

The EnergyPlus example file '5ZoneSupRetPlenRAB.idf' demonstrates how Connector:Splitter, Connector:Mixer, and Duct components can be used to create a supply-side bypass branch on an AirLoopHVAC. The HVAC-Diagram output of this file shows the following (labels not shown because of broken HVAC-Diagram in 9.5):
image (1)

Connector:Splitter, Connector:Mixer, and Duct are all implemented in OpenStudio, however it appears that Connector:Splitter on an air loop forces a dual-duct configuration of that loop, and it doesn't seem that Connector:Mixer can be added anywhere.

This file uses SetpointManager:ReturnAirBypassFlow to set flow on the bypass loop. That object should be added to enable bypass operation.

Implementation should support creating/adding components to a branch before the Splitter and after the Mixer, and on any of the parallel branches between the two. SetpointManager:ReturnAirBypassFlow references the AirLoop (not a specific node).

@eringold eringold added Enhancement Request Triage Issue needs to be assessed and labeled, further information on reported might be needed labels Jun 14, 2021
@eringold eringold changed the title Allow Connector:Splitter and Connector:Mixer to be used to create bypass branches on AirLoopHVAC supply side Allow Connector:Splitter and Connector:Mixer to be used to create bypass branch on AirLoopHVAC supply side Jun 14, 2021
@tijcolem tijcolem removed the Triage Issue needs to be assessed and labeled, further information on reported might be needed label Jun 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants