[Equest-users] Error question

Hiroko Masuda hirokomasuda at tees.tamus.edu
Thu Dec 31 17:15:14 PST 2009


Hello,

I am adding a comment to an old thread posted by Lars in September 2009, attached bellow.
When I used a .inp file generated by eQuest in DOE2.2, I encountered the same problem as Lars explained.

In my case, the reason for the error was the "Variable Speed Drive FPLR" was not defined in the DOE2.2 library "BDLLIB.DAT". This library file is at "C:\doe22\exent" by default. There are several ways to solve this problem.

1) In the same directory as "BDLLIB.DAT", there are some libraries for eQuest such as "eQ_Lib.363.dat". When you run DOE2.2, select an eQuest library file with appropriate version instead of "BDLLIB.DAT".

2) Use a curve which is already defined in the DOE2.2 library "BDLLIB.DAT" such as "Fan-Pwr-fPLR-w/VFD". I plotted "Fan-Pwr-fPLR-w/VFD" in DOE2.2 library and "Variable Speed Drive FPLR" in eQuest library to see the difference. These curves are almost identical. However, as the comment in the library file says, "Fan-Pwr-fPLR-w/VFD" includes +0.05 to points to account for the VSD losses, and at each point, "Fan-Pwr-fPLR-w/VFD" curve is about 0.05 larger than "Variable Speed Drive FPLR" curve.

3) Copy the following portion of the definition of "Variable Speed Drive FPLR" to the library "BDLLIB.DAT".

$LIBRARY-ENTRY Variable Speed Drive FPLR       CURVE-FIT       Fan EIR-FPLR
$Any fan with Variable Speed Drive
   TYPE             = QUADRATIC
   INPUT-TYPE       = COEFFICIENTS
   OUTPUT-MIN       = 0.10
   OUTPUT-MAX       = 1
   COEFFICIENTS     = ( .219762, -0.874784,  1.652597 )

I tested only 1) and 2), but I think 3) would work. 1) would solve other incompatibility problems related to the definition in libraries. It would be helpful if anyone could tell me how to assign several different library files when you run DOE2.2.

I hope this information would save someone's time.

Hiroko Masuda
Graduate Research Assistant at Energy Systems Laboratory
Texas A&M University

  _____

eQuesters & Brett,
 
    Thanks for your help, Brett.  The BDL file shows the following.  It also showed the same error with or without quotes around the U-name in line 3017 and with or without the $ in line 3010.  Evidently, eQuest is just not recognizing the parent system that I defined line lines 2994 - 3016.
    Does anyone know why this would be - especially when, as explained in the original e-mail (below), I based this code on that generated by eQuest?
 
Lars Fetzek, EI
Phoenix Engineering Group
Tampa, Florida
 
 
    *2988 * $ *********************************************************
     *2989 * $ **                                                     **
     *2990 * $ **               HVAC Systems / Zones                  **
     *2991 * $ **                                                     **
     *2992 * $ *********************************************************
     *2993 *  
     *2994 * "HVAC1 System" = SYSTEM
     *2995 *    TYPE             = PVAVS
     *2996 *    HEAT-SOURCE      = NONE
     *2997 *    ZONE-HEAT-SOURCE = ELECTRIC
     *2998 *    BASEBOARD-SOURCE = NONE
     *2999 *    SIZING-RATIO     = 1.15
     *3000 *    MAX-SUPPLY-T     = 95
     *3001 *    MIN-SUPPLY-T     = 55
     *3002 *    ECONO-LIMIT-T    = 65
     *3003 *    ECONO-LOCKOUT    = YES
     *3004 *    OA-CONTROL       = FIXED
     *3005 *    FAN-SCHEDULE     = "HVAC1 Fan Sch"
     *3006 *    FAN-CONTROL      = FAN-EIR-FPLR
     *3007 *    SUPPLY-STATIC    = 3.569
     *3008 *    SUPPLY-EFF       = 0.521452
     *3009 *    RETURN-EFF       = 0.53
     *3010 * $   FAN-EIR-FPLR     = "Variable Speed Drive FPLR"
     *3011 *    REHEAT-DELTA-T   = 15
     *3012 *    COOLING-CAPACITY = 379900
     *3013 *    COOLING-EIR      = 0.324232
     *3014 *    CRANKCASE-HEAT   = 0
     *3015 *    FURNACE-HIR      = 1.24067
     *3016 *    ..
     *3017 * Zone-Space-1A = ZONE
*ERROR**********************************************************************
******************
*ERROR*****A PARENT SYSTEM must be defined before you can define this ZONE
     *3018 *    TYPE             = CONDITIONED
     *3019 *    MIN-FLOW-RATIO   = 0.3
     *3020 *    FLOW/AREA        = 0.5
     *3021 *    OA-FLOW/PER      = 155.325
     *3022 *    EXHAUST-FLOW     = 1130
     *3023 *    EXHAUST-STATIC   = 0.75
     *3024 *    EXHAUST-EFF      = 0.411758
     *3025 *    DESIGN-HEAT-T    = 68
     *3026 *    HEAT-TEMP-SCH    = "HVAC1 Heat Sch"
     *3027 *    DESIGN-COOL-T    = 76
     *3028 *    COOL-TEMP-SCH    = "HVAC1 Cool Sch"
     *3029 *    SIZING-OPTION    = ADJUST-LOADS
     *3030 *    SPACE            = "Space 1A Space"
     *3031 *    ..

  _____  

From: Brett Fero [mailto:bfero at robsonwoese.com]
Sent: Monday, September 14, 2009 3:22 PM
To: Lars Fetzek; equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] Error question



Lars,

 

My suggestion would be to open the bdl file and search for "error".  This
will indicated direct you to where error occurred.  Too many errors and
eQuest gives up.

 

If you are manually editing the inp file, make sure you have two periods
".." at the end of you commands as required.  

 

Brett Fero, P.E., LEED AP

RobsonWoese Inc.

 <mailto:bfero at robsonwoese.com> bfero at robsonwoese.com

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Lars Fetzek
Sent: Monday, September 14, 2009 3:08 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Error question

 

eQuesters,

 

    I included the following text in my .inp file, copied-and-pasted from an
.inp file that eQuest generated.  My intention is to edit it to reflect the
conditions of the present project, which I really really don't want to have
to re-create in the wizard, since I've already composed about 3,000 lines of
.inp code for complex geometry, schedules, etc.  As of yet, the only thing
that I've edited are the U-names referring to the fan schedule, the heat
schedule, the cool schedule, and the space - so that they match the present
project.  Scrolling down in this e-mail, you'll see the lovely error
messages that appear when I load the .inp file into eQuest.  Can anyone tell
me what is wrong and how to fix it?  (Yes, I clicked on the errors, but
eQuest tells me nothing helpful.)

    By the way, my concern here is only with HVAC errors and not with the
electric meter error, which simply results from me having commented-out the
electric meter code in the .inp file.

    Thanks if you have advice...

 

Lars Fetzek, EI

Phoenix Engineering Group

Tampa, Florida



More information about the Equest-users mailing list