Issue with VRF with DOAS Measure
Hi,
To model VRF DOAS system, I use VRF with DOAS Measure (developed by Xcel Energy). Although VRF system is successfully replaced, the program fails due to an error when I run the Measure on Open Studio 3.0.1.
" *FATAL:GetVRFInput: Errors found in getting AirConditioner:VariableRefrigerantFlow system input. Preceding condition(s) causes termination"
Moreover, in some building models, an error Immediately occurs when I apply the measure to the model.
I would appreciate it if you could help me to figure out how to solve these problems
Comments
@yashar could you include the severe error line from the EnergyPlus error file created by OpenStudio? You should find it in the run folder within the folder that has the same name as your OSM (OpenStudio model file). That will give more information about why the VRF with DOAS Measure isn't working correctly.
Hi Aaron,
Thank you very much for your response. Unfortunately, It seems it is not possible to attach a file, but in the error file number of severe error is zero. It is the part of the error file:
program Version,EnergyPlus, Version 9.3.0-baff08990c, YMD=2021.01.12 11:41, * Warning * Sizing:System="DOAS - BUILDING STORY 1", invalid combination of inputs. * ~~~ * Type of Load to Size On = VENTILATIONREQUIREMENT and System Outdoor Air Method = VENTILATIONRATEPROCEDURE.
* Fatal * GetVRFInput: Errors found in getting AirConditioner:VariableRefrigerantFlow system input. Prec
CONDITIONER VARIABLE REFRIGERANT FLOW 1 HEATINGEIRLOWPLR 1 has out of range value. * ~~~ * ...Curve minimum value of X = 0.500 must be <= Minimum Heat Pump Part-Load Ratio = 0.250. * Fatal * GetVRFInput: Errors found in getting AirConditioner:VariableRefrigerantFlow system input. Preceding condition(s) causes termination. ...Summary of Errors that led to program termination: ..... Reference severe error count=0 ..... Last severe error= *** Warning: Node connection errors not checked - most system input has not been read (see previous warning).
@yashar thanks. Could you actually provide a link to the full text of the error file via Dropbox, Google Drive, etc.? Or update your post to show the full text instead of just the fatal error line? That would be easier to see all the model's issues. I can see two here, but there may be more.
@aaron, appreciate for your time and help. You can find the error file here link text.