[Equest-users] 答复: Problem of design flow rate autosize

MatthewRLarson at Eaton.com MatthewRLarson at Eaton.com
Tue Jul 12 08:05:14 PDT 2011


Yu,

 

If you can’t change the altitude, what you can do is take your supply cfm, 60343 in this case, and divide it by the altitude factor which you can find in the top left corner of the SV-A report.  So if your altitude factor was 1.2, you would input 50286 instead and you should get the 60343 cfm as your resulting supply flow.  If you are using kW/cfm for your fan power, you would need to apply this same logic by multiplying your calculated kW/cfm by the altitude factor.

 

Thanks,

 

Matthew Larson, LEED AP BD+C
Project Engineer

Energy Solutions Group

E M C Engineers, Inc.
Eaton’s Electrical Services & Systems 
143 Union Blvd, Suite 350
Lakewood, CO 80228
tel: +1 303 328-3419
mobile: +1 303 668-2511
fax: +1 303 974-1239

MatthewRLarson at Eaton.com 
www.eaton.com/energysolutions  

 

 

From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of ??
Sent: Monday, July 11, 2011 8:35 PM
To: 'Keith Swartz'; equest-users at lists.onebuilding.org
Subject: [Equest-users] 答复: Problem of design flow rate autosize

 

Thanks Keith,

 

I think that would be the reason but the program doesn’t allow me to change Altitude, it change back to blank after I input value and leave the box. User-Defined Default Value doesn’t ether (it did work for Latitude and Longitude input). My location in international -or- User-defined.

 

Yu Liu

+8615010414883

elaneinside at hotmail.com

 

发件人: Keith Swartz [mailto:kswartz at ecw.org] 
发送时间: 2011年7月12日 4:59
收件人: 刘宇; equest-users at lists.onebuilding.org
主题: RE: [Equest-users] Problem of design flow rate autosize

 

Hello, Yu,

 

The difference may be due to eQUEST’S air density correction based on the elevation of your project location. The auto-calculated value is adjusted for the altitude. The air flow you enter is assumed to be at sea level (standard conditions). If this density correction calculation is causing the difference you see, then changing the elevation to 0 feet should get them to match.  To change the elevation, in the Detailed Interface click on “Project & Site” in the upper left, then in the Component Tree on the left side double-click on “Site Data” (4th one down from the top). The field for Altitude is near the middle of the Basic Specifications tab.

 

________________________________

Keith Swartz, P.E., LEED AP


Energy Engineer / Senior Project Manager
Energy Center of Wisconsin
455 Science Drive, Suite 200, Madison, WI 53711
Phone: 608.238.8276 x123
Fax: 608.238.0523

The Buildings Team

Design decisions through energy, economics and emissions analysis.

www.ecw.org/Buildings 


Energy Center University
Your gateway to sustainable design training and online education programs.
www.ecw.org/university/ <http://www.ecw.org/university/> 

From: 刘宇 [mailto:elaneinside at hotmail.com] 
Sent: Sunday, July 10, 2011 10:34 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Problem of design flow rate autosize

 

Hi

 

I’m trying to model baseline system 7 HVAC system using ‘Variable Air Volume’ system with zone HW reheat. When I leave design supply flow blank to let equest auto size, I have 60343 cfm supply flow and 320 unmet heat hour in system summary table. But when I input 60343 cfm in system design flow box and recalculate, then I have 105 unmet hours, and nothing else changed in system summary table. Is that a bug of software or there are some reason I don’t know.

 

Yu Liu

+8615010414883

elaneinside at hotmail.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110712/0bb079b6/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 39998 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110712/0bb079b6/attachment-0002.jpeg>


More information about the Equest-users mailing list