[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [EnergyPlus_Support] Re: Thermostat Deadband





Hi, Ven
 
I am interested to see your .IDF file, because there are now more than one ways to use the DeadBand.
 
In the older version, the deadband comes with the type 4 thermostat setpoints.  I believe it is still there in version 4.  However, some template models do not seems to need to declare this any more, because of the smarter managers..
 
I am interested, because I am a collector of error messages.  The best way to learn computer programming  is to make errors and then try to follow the error messages and debug the problem.
 
It is possible that your schedule  is enter in the wrong field of the calling object.
 
The schedules themselves are correct as the year:day schedule for thermostat.  I usually use 'temperature' for the Schedule Type Limits Name. ('Any Number' has no limit.)
 
 Dr. Li  



 

To: EnergyPlus_Support@xxxxxxxxxxxxxxx
From: eplusven@xxxxxxxx
Date: Wed, 11 Nov 2009 16:56:33 +0000
Subject: [EnergyPlus_Support] Re: Thermostat Deadband

 
Yes that is true. I have specified heating as well as cooling schedules. But I did not find any provision to sepcify the deadband temparature difference.

The following are heat and cool schedules for the thermostat I am using.

Schedule:Compact,
HEATSCHEDULE, !- Name
Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: Alldays, !- Field 2
Until: 05:29, 13, !- Field 4
Until:19:30, 22, !- Field 6
Until:24:00, 13; !- Field 8

Schedule:Compact,
COOLSCHEDULE, !- Name
Any Number, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: Alldays, !- Field 2
Until: 05:29, 32, !- Field 4
Until:19:30, 23, !- Field 6
Until:24:00, 32; !- Field 8

--- In EnergyPlus_Support@yahoogroups.com, Don Shirey <shirey@...> wrote:
>
> Seems like you would want to use the "Heating Setpoint Schedule Name"
> and "Cooling Setpoint Schedule Name" input fields in the
> HVACTemplate:Thermostat object to define your heating and cooling
> setpoints throughout the year.
>
> The HVACTemplate:Thermostat object will be translated into the required
> "native" EnergyPlus objects (ZoneControl:Thermostat) when using
> EP-Launch. The "HVACTemplate" objects the you define remain in the
> resulting input data file but are commented out.
>
>
> eplusven wrote:
> > Thanks Don!
> >
> > Could anyone throw some light on my first question
> >
> > "I am modeling an office Packaged VAV HVAC using "HVACTemplate:System:PackagedVAV" and thermostat using "HVACTemplate:Thermostat". My office has deadband thermostat.
> >
> > In summer the dead band is 1 F and in winter deadband is 3F for a base temparature 71F. The documentation specifies HVACTemplate:Thermostat uses dualsetpoint with deadband. But I was not able understand how. Could anyone help me how do I model this Thermostat with deadband offset. "
> >
> >
> > Thanks
> > -Ven
> >
>




Windows Live: Keep your friends up to date with what you do online.

__._,_.___


The primary EnergyPlus web site is found at:
http://www.energyplus.gov

The group web site is:
http://groups.yahoo.com/group/EnergyPlus_Support/

Attachments are currently allowed but be mindful that not everyone has a high speed connection.  Limit attachments to small files.

EnergyPlus Documentation is searchable.  Open EPlusMainMenu.pdf under the Documentation link and press the "search" button.




Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe

__,_._,___