[Equest-users] CAUTION: Variable Speed Drive FPLR???

[Carol Gardner]

Hi Nick,

I don't know why but this came across as Wide. I find my tiny brain cannot
focus on it when it is WIDE.

Help me!
Carol

On Fri, May 7, 2010 at 3:34 PM, Nick Caton <ncaton at smithboucher.com> wrote:

>  Eric,
>
>
>
> I’m following your line of thinking… but I’m still stumped as to the root
> cause…  If the design CFM was too low and that’s why Z>1.0, wouldn’t there
> be a warning for that?  I have a bunch of items referencing the library VSD
> curve in question so it’s not easy for me to check all the potentially awry
> hourly results – but I may need to go down that path…
>
>
>
> Carol,
>
>
>
> ATTN is the report we can look at in the SIM file after running a
> simulation – a screenshot follows.  It displays any cautions/warnings/errors
> encountered when a simulation is attempted/completed.  Sorry for the minor
> censoring but this is one of those “top-secret nuclear facilities” we keep
> referencing for which I might get in actual trouble otherwise =).  It’s a
> different project but similar caution popping up on the last day of the
> year.
>
>
>
> As a related aside and general DOE2 inquiry – I’ve been trying to enter the
> following line into my .inp file in various locations prior to running a
> simulation, but I cannot get it to stick (eQuest seems to ignore or erase it
> wherever I put it as soon as I try to run a simulation):  DIAGNOSTIC
> WARNINGS ..
>
>
>
> The idea is to have this ATTN report, which I’m occasionally asked to
> present along with explanations, not show cautions (after determining they
> are indeed erroneous, of course!).  Am I chasing my own tail trying to put
> this into the .inp file?  Is there somewhere in the eQuest interface we’re
> permitted to specify a DIAGNOSTIC option other than the default CAUTIONS?
>
>
>
>
>
> [image: untitled.PNG]
>
>
>
> [image: cid:489575314 at 22072009-0ABB]**
>
> * *
>
> *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:* Carol Gardner [mailto:cmg750 at gmail.com]
> *Sent:* Friday, May 07, 2010 12:23 AM
> *To:* Eric O'Neill
> *Cc:* Nick Caton; eQUEST Users List
>
> *Subject:* Re: [Equest-users] CAUTION: Variable Speed Drive FPLR???
>
>
>
> What the heck is an ATTN screen?? Is it a LEED thingy??
>
> Confused in Portland,
> Carol
>
> On Thu, May 6, 2010 at 12:39 PM, Eric O'Neill <elo at michaelsengineering.com>
> wrote:
>
> Nick,
>
>
>
> I’m not sure I can answer your question. Maybe someone can pick up on this
> line of thought though to answer the question.
>
>
>
> If you play with the numbers, a PLR of 1.1 is yielding that fan vsd signal
> of 1.257. I believe the PLR is calculated as (the current hour’s
> CFM)/(design CFM). So whatever’s going on here is causing the system to call
> for (or think it has) a CFM value 10% greater than design. Also, the
> function is supposed to set any outputs above the set maximum (in this case
> 1) to the maximum, so I’m not sure what about the last day of the year is
> causing it to ignore the maximum output value.
>
>
>
> When I look at the hourly reports on a system that’s using that curve and
> getting that error at 12/31/24, my PLR (variable 60) looks fine, and the CFM
> is at its minimum. So I don’t think it’s a real issue. I’m also not very
> BDL/DOE2 literate, so I might be looking at this wrong.
>
>
>
> Also, if you really wanted a clean ATTN screen, you could just set your max
> output from that function to 1.28 ;-)
>
>
>
> Cheers,
>
>
>
> Eric
>
>
>
> *From:* equest-users-bounces at lists.onebuilding.org [mailto:
> equest-users-bounces at lists.onebuilding.org] *On Behalf Of *Nick Caton
> *Sent:* Thursday, May 06, 2010 12:32 PM
> *To:* Carol Gardner
>
>
> *Cc:* eQUEST Users List
> *Subject:* Re: [Equest-users] CAUTION: Variable Speed Drive FPLR???
>
>
>
> Thanks Carol!
>
>
>
> I’m glad to see some supporting information to assure me this CAUTION is
> likely not a big deal, but it still kinda irks me that this is message is
> often the only thing between me and a perfectly blank ATTN report in my
> models…
>
>
>
> If anyone can offer some insight regarding this VSD curve message’s meaning
> and/or root-causes, I’d be very grateful to either figure out a way to
> eliminate these CAUTIONS, or to otherwise be able to sleep at night knowing
> I can provide an in-depth response regarding its meaning and why it’s not a
> big deal and ignore-able.
>
>
>
> ~Nick
>
>
>
> [image: cid:489575314 at 22072009-0ABB]
>
> * *
>
> *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:* Carol Gardner [mailto:cmg750 at gmail.com]
> *Sent:* Thursday, May 06, 2010 12:25 PM
> *To:* Nick Caton
> *Cc:* eQUEST Users List
> *Subject:* Re: [Equest-users] CAUTION: Variable Speed Drive FPLR???
>
>
>
> Here you go Nick. This is in your 3-63 data area as DOE-2.chm. There is
> tons of info there. Cautions are the least of your worries.
>
> ERRORS                      Diagnostics deal with problems in the input
> that must be corrected before the simulation will execute.
>
> WARNINGS                 Diagnostics are concerned with input data that can
> be used in the simulation but are probably erroneous (such as a temperature
> input of 700 instead of 70.0).
>
> CAUTIONS                   Diagnostics are much less severe than WARNINGS
> messages and deal with questionable input value that do not significantly
> affect the results of the simulation. This is the default level.
>
> Regards,
>
> Carol
>
>
>
> On Thu, May 6, 2010 at 9:32 AM, Nick Caton <ncaton at smithboucher.com>
> wrote:
>
> On many projects, I’ve run into the following typical CAUTION in my SIM
> ATTN report:
>
>
>
>
>
>
>  **CAUTION**********************************************************************
>
>              In curve: Variable Speed Drive FPLR        the dependent value
>
>              is exceeding the limits.
>
>              Value/Min/Max/First time:          1.257
> 0.100          1.000  12/31/24
>
>
>
>
>
> It’s *always* referencing this specific library VSD curve, and it *always*occurs in the last hours of the very last day of the modeled year.  I’ve
> seen it so much I’m pretty certain that particular value 1.257 is always
> present too.
>
>
>
> What are the implications here to the modeled behavior?  Is this caution
> something of concern?  Is something off with the library curve?
>
>
>
> I’ve always assumed that if something is only off in the last hours of the
> modeled year, it shouldn’t be a big deal – but it’s bugging me that I’m
> seeing this come up again and again and I don’t know what it really means…
>
>
>
> ~Nick
>
>
>
>
>
> [image: cid:489575314 at 22072009-0ABB]
>
> * *
>
> *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* *
>
>
>
>
> _______________________________________________
> Equest-users mailing list
> http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
> To unsubscribe from this mailing list send  a blank message to
> EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100507/a27b4df1/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 32146 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100507/a27b4df1/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100507/a27b4df1/attachment-0002.jpeg>