This is another problem with the third party input programs or the templates.
The always 4 schedule is used for temperature or thermostat type. (Limit = any number, i.e., no type nor limits.)
Always 20, always 23, etc. for temperature without using the 'temperature' as type limits.
0 is the name for always off, and 'any number' was the type.
Because many examples are given as such, the need for the shedulte type limit is lost to some uwers.
At one time, I remember that the 0 and 0.0 would flag a warning if not properly used.
Dr. Li.
To: EnergyPlus_Support@xxxxxxxxxxxxxxx
From: RRaustad@xxxxxxxxxxxx
Date: Mon, 22 Aug 2011 08:49:14 -0400
Subject: Re: [EnergyPlus_Support] Thermostat Setpoints Schedule
If you look at the temperature schedule, you can't tell if that number is a temperature, but the limits object tells you it is. You also don't know if 22.512C is allowed without looking at the limits object (it is allowed since it is a continuous [real] number between -60 and 200). You also don't know if 15C or 20C is within the allowed range without looking at the limits object.
I am also a little unsure of the syntax used in your example. Here are examples that look correct to me. Notice how the compact schedule has "temperature" for the Schedule Type Limits Name which points to the ScheduleTypeLimits object with the name "temperature". And the Unit Type in the limits object is "temperature", not "Unit Temperature". The numbers in the schedule compact are also real numbers, although you are allowed to use integers which would then be converted to real numbers by the program (since the limit object tells the program they are real numbers).
ScheduleTypeLimits,
Temperature, !- Name
-60, !- Lower Limit Value
200, !- Upper Limit Value
CONTINUOUS, !- Numeric Type
Temperature; !- Unit Type
Schedule:Compact,
HEATING SETPOINTS, !- Name
TEMPERATURE, !- Schedule Type Limits Name
Through: 12/31, !- Field 1
For: Weekdays Weekends Holiday, !- Field 2
Until: 8:00,15.00, !- Field 3
Until: 18:00,20.00, !- Field 5
Until: 24:00,15.00, !- Field 7
For: SummerDesignDay, !- Field 9
Until: 24:00,20.00, !- Field 10
For: WinterDesignDay, !- Field 12
Until: 24:00,20.00, !- Field 13
For: CustomDay1 CustomDay2, !- Field 15
Until: 8:00,15.00, !- Field 16
Until: 18:00,20.00, !- Field 18
Until: 24:00,15.00; !- Field 20
On 8/21/2011 9:53 AM, artitecture82 wrote:
Hi All,
Im a bit confused about the use of ScheduleType Limits to constrain the Schdule:Compact used in the ThermostatSetpoint object.
I found an example with these values
ScheduleTypeLimits
------------------
Temperature
lower -60
upper 200
CONTINUOS
UNit Temperature
ScheduleCompact
-----------------
ScheduleTypeLImits:Temperature,
Through: 12/31,
For: AllDays,
Until: 7:00,
15.
Until: 17:00,
20.
Until: 24:00,
15
While I pretty understand what are the values of the ScheduleCompact, I dont understand what the ScheduleTypelimits does.
Can anyone help me to understand?
thanks
-- Richard A. Raustad Senior Research Engineer Florida Solar Energy Center University of Central Florida 1679 Clearlake Road Cocoa, FL 32922-5703 Phone: (321) 638-1454 Fax: (321) 638-1439 or 1010 Visit our web site at: http://www.fsec.ucf.edu UCF - From Promise to Prominence: Celebrating 40 Years
__._,_.___
Primary EnergyPlus support is found at:
http://energyplus.helpserve.com or send a message to energyplus-support@xxxxxxxx
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.
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
__,_._,___