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

VRF heating issue: same heating power with different compressor speed at low heating load #10427

Open
1 of 3 tasks
yujiex opened this issue Mar 6, 2024 · 0 comments · May be fixed by #10416
Open
1 of 3 tasks

VRF heating issue: same heating power with different compressor speed at low heating load #10427

yujiex opened this issue Mar 6, 2024 · 0 comments · May be fixed by #10416
Assignees
Labels
Defect Includes code to repair a defect in EnergyPlus

Comments

@yujiex
Copy link
Collaborator

yujiex commented Mar 6, 2024

Issue overview

Cycling issue at low speed for heating mode

From 12:30 to 13:00, the compressors are running at the lowest speed in both cases, zone temperature are the same but both system have cycling ratio = 1. This shouldn't happen as they have different compressor curves corresponding to the lowest speed.
From 13:10 to 13:40, the one with minimum speed = 1320 has larger cycling ratio (runs for longer period) than the one with minimum speed = 900.

image

The problem is likely related to two issues in the cycling ratio calculation.

  1. The position of the cycling ratio calculation

Similar to the cycling ratio problem in the cooling side. Whether the demand is less than minimum speed capacity is checked at two places. The first one will short-circuit and prevent the Te adjustment step (orange box in the following simplified flow diagram)

image

The following is the diagram in the documentation

image
  1. Discontinuity

When the demand is very low, the cycling ratio is calculated as follows. When Q_h_TU_PL <= CompEvaporatingPWRSpdMin, it will enter branch 1. When Q_h_TU_PL > CompEvaporatingPWRSpdMin, it will enter branch 2. C_cap_operation is generally close to 1. However, when Q_h_TU_PL is close to CompEvaporatingPWRSpdMin, depending on which branch it ended up in, the result could be very different. If we assume CompEvaporatingPWRSpdMin and CompEvaporatingCAPSpdMin have similar magnitude, and C_cap_operation is indeed close to one,

  • when Q_h_TU_PL is slightly smaller than CompEvaporatingPWRSpdMin, then CyclingRatio is close to 1
  • when Q_h_TU_PL is slightly larger than CompEvaporatingPWRSpdMin, then CyclingRatio is close to 0
        Q_c_OU = max(0.0, Q_h_TU_PL - CompEvaporatingPWRSpdMin);
        ...
            if (Q_c_OU == 0) { // branch 1
                // Q_h_TU_PL is less than or equal to CompEvaporatingPWRSpdMin
                CyclingRatio = Q_h_TU_PL / CompEvaporatingPWRSpdMin;
                this->EvaporatingTemp = OutdoorDryBulb;
            } else { // branch 2
                // Q_h_TU_PL is greater than CompEvaporatingPWRSpdMin
                CyclingRatio = Q_c_OU * C_cap_operation / CompEvaporatingCAPSpdMin;
                this->EvaporatingTemp = max(CapMinTe, RefTLow);
            }
02/20 13-1,branch 2 ----- cyclingRatio=0.5424031528859093,Q_h_TU_PL=772.3616736028802,CompEvaporatingPWRSpdMin=191.07128170025996,C_cap_operation=0.895930180163394
02/20 13-2,branch 2 ----- cyclingRatio=0.010679792435435032,Q_h_TU_PL=202.516754863906,CompEvaporatingPWRSpdMin=191.07128170025996,C_cap_operation=0.895930180163394
02/20 13-3,branch 1 ----- cyclingRatio=0.7196798169795096,Q_h_TU_PL=137.5101450440834,CompEvaporatingPWRSpdMin=191.07128170025996
02/20 13-4,branch 1 ----- cyclingRatio=0.9347582121695664,Q_h_TU_PL=178.6054496790826,CompEvaporatingPWRSpdMin=191.07128170025996

Defect files

US+SF+CZ4A+hp+crawlspace+IECC_2006_VRF_minSpd900.idf.txt
US+SF+CZ4A+hp+crawlspace+IECC_2006_VRF_minSpd1320.idf.txt
USA_NY_New.York-John.F.Kennedy.Intl.AP.744860_TMY3.epw.txt

Details

Some additional details for this issue (if relevant):

  • Platform (Operating system, version)
  • Version of EnergyPlus (if using an intermediate build, include SHA)
  • Unmethours link or helpdesk ticket number

Checklist

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

  • Defect file added (list location of defect file here)
  • Ticket added to Pivotal for defect (development team task)
  • Pull request created (the pull request will have additional tasks related to reviewing changes that fix this defect)
@yujiex yujiex added the Defect Includes code to repair a defect in EnergyPlus label Mar 6, 2024
@yujiex yujiex self-assigned this Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Defect Includes code to repair a defect in EnergyPlus
Projects
None yet
1 participant