Multispeed DX coils not following specified minimum flow rates with no cooling or heating load
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by running the attached in.idf.txt and inspecting the AirLoopHVAC:UnitarySystem handling for multispeed DX systems during continuous fan operation with no load. Compare the simulated no-load supply airflow with the configured minimum rate and confirm that the fan uses the minimum airflow rather than the maximum; add or update coverage for this scenario if the existing test structure identifies a suitable location.
Written by the indexing model from the issue text.
Description
Issue overview
I am modeling a multispeed DX heat pump system (representing a variable speed commercial heat pump RTU). The fan operation is set to be continuous during operating hours, and cycling during non-operating hours. I am using the "AirLoopHVAC:UnitarySystem" system type.
For timesteps when no heating or cooling load is present, but the fan operation schedule is "continuous", the fan appears to use the maximum airflow rate rather than the airflow rate specified in the "No Load Supply Air Flow Rate" field. This is resulting in the highest airflows occurring during times when there is little to no load.
This is shown in the figure below at the beginning and end of the building operating hours when there is no heating or cooling load. The unitary multispeed DX system correctly chooses speed 0, heating and cooling loads are 0, but the fan operates at the maximum flow rate around 0.65kg/s, rather than the minimum airflow rate (speed 1 airflow).
When the cooling load appears in the middle of the day, the unitary DX system speed increases stages, and the fan flow responds accordingly as expected. Additionally, during unoccupied hours, the fan and DX system appear to cycle as expected.
I have attached the IDF.
- Dominant language
- C++
- Stars
- 1.6k
- Forks
- 490
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 22
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NatLabRockies/EnergyPlus
-
Triage UnconfirmedDefect
Difficulty 4/5 3-5 days Newbie friendliness 62/100
NatLabRockies/EnergyPlus#11798 · 3 comments ·
-
Windows arm64 release build broken due to Cmake detection of Fortran compiler on Github Actions OpenDefect Developer Issue
NatLabRockies/EnergyPlus#11797 · 1 assignee ·
-
Defect Documentation
NatLabRockies/EnergyPlus#11783 · 1 comment · 1 assignee ·
-
Triage UnconfirmedDefect
NatLabRockies/EnergyPlus#11771 · 1 assignee ·
-
HeatPump:PlantLoop:EIR - calcPowerUsage uses load-side heat transfer instead of reference capacity OpenTriage UnconfirmedDefect
NatLabRockies/EnergyPlus#11764 · 1 comment · 1 assignee ·
All issues in NatLabRockies/EnergyPlus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·