Data Center Server Heat Load - 3.63

8 posts / 0 new
Last post

I'm a newbie with eQuest and can't determine how to add server load to
my bldg. The 'Heat Rejection' and 'Refrigeration' sections are all
zeroes after a simulation. Where do I add that load so that the HVAC
will see the heat load? Thanks, Greg

Greg Ryerson

Ryerson, Gregory's picture
Joined: 2011-09-30
Reputation: 0

Hi Greg:
?
You reached the Nirvana of eQuest information. If my solution isn't the best for you, some other esteemed member will give you his or hers.
?
Is your server load cooled by DX units or chilled water? If DX, you probably want the server load only satisfied by the DX units, not the other HVAC units in the space. eQuest (DOE-2 engine) cannot have tow systems satisfying one load.
?
For this situation, I would divide up the room into two zones. The first being the actual space dimensions, mius the server space. In this space, put your DX/chilled water HVAC unit. In the 2nd space, use the server sq.ft and add the server load as Process Load, to be satisfied by the Server HVAC
?
If your server is cooled by chilled water, I believe it should be the same procedure.?However, the process load could be placed directly on the Chilled Water loop as a load. No HVAC required for the server space.
?
Others may have a more elegant solution.
?
John Aulbach

John Aulbach's picture
Offline
Joined: 2011-09-30
Reputation: 1

My HVAC is all DX. What portion of eQuest allows me the opportunity to
add the server load as 'Process Load'?

My goal is to generate 2 reports - one at 72 deg server inlet temp and
one at 80 deg for comparison.

Thanks much, Greg

Ryerson, Gregory's picture
Joined: 2011-09-30
Reputation: 0

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

$ *********************************************************
$ ** **
$ ** HVAC Systems / Zones **
$ ** **
$ *********************************************************

"HVAC1 System" = SYSTEM
TYPE = PVAVS
HEAT-SOURCE = NONE
ZONE-HEAT-SOURCE = ELECTRIC
BASEBOARD-SOURCE = NONE
SIZING-RATIO = 1.15
MAX-SUPPLY-T = 95
MIN-SUPPLY-T = 55
ECONO-LIMIT-T = 65
ECONO-LOCKOUT = YES
OA-CONTROL = FIXED
FAN-SCHEDULE = "HVAC1 Fan Sch"
FAN-CONTROL = FAN-EIR-FPLR
SUPPLY-STATIC = 3.569
SUPPLY-EFF = 0.521452
RETURN-EFF = 0.53
FAN-EIR-FPLR = "Variable Speed Drive FPLR"
REHEAT-DELTA-T = 15
COOLING-CAPACITY = 379900
COOLING-EIR = 0.324232
CRANKCASE-HEAT = 0
FURNACE-HIR = 1.24067
..
"Zone Space 1A" = ZONE
TYPE = CONDITIONED
MIN-FLOW-RATIO = 0.3
FLOW/AREA = 0.5
OA-FLOW/PER = 155.325
EXHAUST-FLOW = 1130
EXHAUST-STATIC = 0.75
EXHAUST-EFF = 0.411758
DESIGN-HEAT-T = 68
HEAT-TEMP-SCH = "HVAC1 Heat Sch"
DESIGN-COOL-T = 76
COOL-TEMP-SCH = "HVAC1 Cool Sch"
SIZING-OPTION = ADJUST-LOADS
SPACE = "Space 1A Space"
..

Lars Fetzek's picture
Offline
Joined: 2011-09-30
Reputation: 0

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

Brett Fero's picture
Offline
Joined: 2011-09-30
Reputation: 0

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

*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 * ..

Lars Fetzek's picture
Offline
Joined: 2011-09-30
Reputation: 0

eQuesters,

I have solved my problem, described below (from previous e-mails). My
solution leads me to send the following advice to everyone:

Be aware that adding comments (i.e. text preceded by a dollar sign) in a
.inp file, even at the end of an already functional line of code, can cause
mysterious problems in eQuest's interpretation of other (seemingly
unrelated) lines of code.

Lars Fetzek, EI

Lars Fetzek's picture
Offline
Joined: 2011-09-30
Reputation: 0

You GO, Lars. Experience in this program is the best teacher.

John Aulbach's picture
Offline
Joined: 2011-09-30
Reputation: 1