[Equest-users] CAUTION and WARNING Messages

[Nick Caton]

Varkie,

 

If it’s any consolation, I’ve dug deep at this CAUTION and come up with little.  There’s an extended discussion between myself and others on the list trying to determine the root of these FPLR cautions, but to the best of my knowledge it’s a mystery.  I can say these cautions appear erroneous, as the CFM’s modeled by the corresponding fans appear to remain within expected ranges.  For further reading, search for “CAUTION: Variable Speed Drive FPLR” in the archives.

 

Once I determined the cautions were erroneous, I went on to try and figure out how to have eQuest not report cautions, so I could get a clean ATTN report, but I’ve yet to successfully use the line DIAGNOSTIC WARNINGS ..  within an *.inp (I’m not sure it’s possible, actually).  I’d be interested to hear if you can come up with any new information…

Best of luck!

 

~Nick

 

 

 

NICK CATON, E.I.T.

PROJECT ENGINEER

25501 west valley parkway

olathe ks 66061

direct 913 344.0036

fax 913 345.0617

Check out our new web-site @ www.smithboucher.com 

 

From: equest-users-bounces at lists.onebuilding.org [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Varkie C Thomas
Sent: Monday, July 19, 2010 9:18 AM
To: Carol Gardner
Cc: equest-users at onebuilding.org
Subject: Re: [Equest-users] CAUTION and WARNING Messages

 

Carol.

 

There were no changes to the FPLR curve data.  I am trying to create case studies for teaching based on projects that were modeled with DOE21E.  It could be any program.  The buildings are modified and simplified to eliminate repetitive details and to demonstrate design issues.  With eQ the building and the envelope (even complex ones) can be created within a couple of hours by tracing ACAD drawings.  But on large project you cannot recognize any of the components names in the reports.  The DOE2 programs require a component name before entering the data.  eQ should make this a priority in future versions.  I think I will continue creating the building model in eQ and use the dimensional data in eQ (azimuths, coordinates, lengths, areas, etc) in creating DOE21E models and analyze the options in DOE21E.  

 

Varkie

 

----- Original Message -----

From: Carol Gardner <cmg750 at gmail.com>

Date: Monday, July 19, 2010 0:58 am

Subject: Re: [Equest-users] CAUTION and WARNING Messages 

Varkie,

I took a quick look at this and I don't see the problem either. Did you make any changes to the FPLR curve data?

Carol

 

 

 

I hope someone can help me.  I am getting CAUTION messages � In curve: Variable Speed Drive FPLR  the dependent value is exceeding the limits. Etc.,�  

 

The first one (my attempt at modeling the baseline without WSE that I enquired about earlier) used all eQUEST defaults for the bldg type �High-Tech & Bio-Tech� including dimensions.  Only the Misc-Eqp was changed to 5 watts/sf.  The attached eQ inp-pd2 files are in Detailed-Edit. There were about 20 pages of �curve� CAUTION messages.

 

The second is for a hotel bldg.  The attached eQ inp-pd2 files are In Design-Development.  You can view them in DD.  Except for minor changes, the input for all Shells used eQ defaults.  The component names (schedules, spaces, zones, etc) are also eQ defaults.  There were about 2000 pages of �curve� CAUTION messages. 

 

The third is for an office bldg. 

In Run-1, except for changing the component names, the input for all Shells used eQ defaults.  There were about 2000 pages of �curve� CAUTION messages. No WARNING messages

Run-2 used OA-FROM-SYSTEM.  There were several WARNING regarding heat capacity and the CAUTION messages of Run-1.

 

I have attached (1) the eQ inp & pd2 files ; (2) the CAUTION & WARNING messages; and (3) the project descriptions of all the examples.

 

Varkie.

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100719/2888eb38/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100719/2888eb38/attachment-0001.jpeg>