Hello all,
I am attempting to model horizontal blind controls in eQuest / DOE2 in conjunction with daylight dimming controls for lighting in a high rise office tower using eQuest 3.64.
In the past I have generally modelled windows using simplified glass type definitions or import from WINDOW 5, but this time around I'm using the window layers commands as this allows controlled horizontal blinds to be simulated (at least in theory). The blind control system is controlled by a sun tracking system located on the roof of the building. The designer has supplied me with detailed scheduled hourly schedules of the blind slat angle per fa?ade orientation.
My understanding of the blind control capability in eQuest/ DOE2 is that blinds can be controlled using a SCHEDULE(s) of the type FRACTION for the window coverage and slat angle respectively. As such, I have developed two schedules, 1) for lowering and raising of the blinds [ window coverage] and 2) blind slat angle adjustment.
My problem is I'm getting an error (typical eQuest nonsense) stating
BDL error: Error in blind control: Adjustment type SCHEDULE for BLIND should be SCHEDULE
I don't see what the error is. I have pasted the BDL below
*1142 * "Window 71" = WINDOW
*1143 * GLASS-TYPE = "GL7"
*1144 * WIN-SPEC-METHOD = LAYERS-INPUT
*1145 * FRAME-WIDTH = 0
*1146 * X = 31.5
*1147 * Y = {parameter("Window sill ht")}
*1148 * HEIGHT = {parameter("Window ht")}
*1149 * WIDTH = 5.9
*1150 * LEFT-FIN-D = 1.1
*1151 * RIGHT-FIN-D = 1.1
*1152 * FRAME-CONDUCT = 2.781
*1153 * WINDOW-LAYERS = ( "GL7layer", "Air-6.3mm", "Metal-1in-Lt" )
*1154 * SLAT-SCHEDULE = "E blind slat annual"
*1155 * SLAT-ADJ-TYPE = SCHEDULE
*1156 * BLIND-SCHEDULE = "E blind deploy annual"
*1157 * BLIND-ADJ-TYPE = SCHEDULE
*1158 * ..
*ERROR****************************************************************************************
*ERROR****************************************************************************************
The DOE2 documentation is sparse on this subject and I'm basically chasing my tail on this. If anyone out there has successfully modelled blind controls and has suggestions or has an alternative way of modelling automatic horizontal blinds with daylight light control dimming, I would be very grateful.
Thank in advance,
Shuichi Hendrickson, LEED AP
Hi Shuichi,
I have not actively used this area of eQUEST, but I can pretty much
guarantee that there will not be a schedule ever in eQUEST that is just
called "SCHEDULE". The reason for that is that there are just too many
schedules in eQUEST for any one of them to claim the glorified name of
"SCHEDULE". That coupled with the fact that schedules are also, of
necessity, split into DAY-SCHEDULE, WEEK-SCHEDULE, AND ANNUAL-SCHEDULE, you
can see that when you find yourself typing simply "SCHEDULE" after your
command an alarm should go off in your head that says something like "Oh,
oh, I'm putting some nonsense into eQUEST that may cause the program to go
off in some sort of GI/GO loop, I guess I'd better research the topic a bit
more."
You sound like a user of some experience so I will just encourage you to dig
a little deeper, keeping in mind the schedule structure in eQUEST and the
use of the Building Description Language.
Cheers,
Carol
Shuichi:
Don't you just love it when someone responds to your query and tells you to look
it up!
Anyway, Did you define the window shade type? I recently did a project and my
BDL input looks like the below:
*19094* "E6 North Win (G.E1.E3.W1)" = WINDOW
*19095* GLASS-TYPE = "Resto & Retail Glass"
*19096* SHADING-SCHEDULE = "Wind Shading Sch"
*19097* FRAME-WIDTH = 0.13
*19098* X = 4.43
*19099* Y = 0
*19100* HEIGHT = 8
*19101* WIDTH = 13
*19102* WIN-SHADE-TYPE = MOVABLE-INTERIOR
*19103* FRAME-CONDUCT = 1.8
*19104* ..
You have some other variables such as fin sizes. Is the Win-Shade-Type defined
in your BDL file? Notice that the Shading-Schedule is right after the
Glass-Type.
Paul Diglio
Hi Carol and Paul,
Thank you for your responses.
Carol,
I think I have the schedules input correctly. To clarify see my notes below.
*1154 * SLAT-SCHEDULE = "E blind slat annual" [This is the annual schedule name; week and day schedules are defined accordingly]
*1155 * SLAT-ADJ-TYPE = SCHEDULE [This designates the control type = SCHEDULE; the options are SCHEDULE, SOLAR INTENSITY, and ROOM TEMP]
*1156 * BLIND-SCHEDULE = "E blind deploy annual" [This is the annual schedule name; week and day schedules are defined accordingly]
*1157 * BLIND-ADJ-TYPE = SCHEDULE [This designates the control type = SCHEDULE; the options are SCHEDULE, SOLAR INTENSITY, and ROOM TEMP]
The error says
BDL error: Error in blind control: Adjustment type SCHEDULE for BLIND should be SCHEDULE
It seems that this is correctly defined, so Im wondering if this could be a bug. Any additional thoughts on this are highly appreciated.
Paul,
I've used the interior shade functions before, but my understanding is that this is more for curtains and more uniformly diffuse/opaque shades. Do you know if it is possible to model the changes in visible light using the shade functions? I wanted to use the blinds controls so I could get a better handle on the synergy between the blinds and the daylight dimming light controls. The shade schedule seems to be used only for describing changes in solar gain.
I guess Im kind of answering my own question here, but I did come across a definition that can be used to schedule the VLT (below). I guess to do this, I need to get a better handle on the relationship of VLT to slat angle. Have you dealt with this before?
VIS-TRANS-SCH
Takes the U-name of a schedule (of TYPE=MULTIPLIER) that gives the daylight transmittance of the window shading device when it covers the window; required for daylighting calculation if SHADING-SCHEDULE is specified. (If WIN-SHADE-TYPE = MOVABLE-INTERIOR or MOVABLE-EXTERIOR, the program will use a transmittance multiplier value of 1.0 when the shade is retracted.) Typical visible transmittance values for translucent drapes and shades are given in Table 42. A transmittance schedule is used, rather than a single fixed value, to allow seasonal change in the transmittance of the shading device. This schedule is used only for windows in a space with DAYLIGHTING = YES. For these windows, be sure to specify not only VIS-TRANS-SCH, but also SHADING-SCHEDULE (and CONDUCT-SCHEDULE if the change in window conductance with the shade in place is significant). In the daylighting calculation, shading surfaces are modeled as perfect diffusers with a daylight transmittance that is independent of angle of incidence. For this reason, slat-type devices, such as Venetian blinds, whose transmittance is a strong function of the angle at which light enters the device, should be modeled as a blind layer (see WINDOW-LAYERS keyword, above, and WINDOW-LAYER command).
Any additional thoughts on this are highly appreciated.
Cheers,
Shuichi
Shuichi,
Well this is what I found in the documentation:
Volume 2: Dictionary > Envelope> > Window Blind Control
Components
WINDOW
SLAT-SCHEDULE
Takes the U-name of a schedule that adjusts the slat angle to a fraction of
SLAT-ANGLE-MAX or SLAT-ANGLE-MIN. This schedule is used only if
SLAT-ADJ-TYPE = SCHEDULE. A schedule value of *f* gives
slat angle = *f* * [SLAT-ANGLE-MAX], if *f* *>* 0
slat angle = *f* * [SLAT-ANGLE-MIN], if *f* *<* 0
The schedule should have TYPE = FRACTION if only positive values of *f* are
used, in which case *f* should be between 0 and 1. If positive and negative
values of *f* are used than the schedule should have TYPE = EXP-FRACTION, in
which case *f* should be between -1 and 1.
I don't know if there's anything here but be sure to check that the schedule
typess are specified correctly. And sorry, I was wrong about the SHCEDULE.
Carol
Carol,
Thanks for the input and no worries. I have read through the info you pasted previously. I think I may punt on this one and try to infer a VLT schedule from the slat angle schedules I have and use the shade functions, unless others chime in with some additional thoughts.
Kind regards,
Shuichi
Hi Shuichi,
I have not actively used this area of eQUEST, but I can pretty much
guarantee that there will not be a schedule ever in eQUEST that is just
called "SCHEDULE". The reason for that is that there are just too many
schedules in eQUEST for any one of them to claim the glorified name of
"SCHEDULE". That coupled with the fact that schedules are also, of
necessity, split into DAY-SCHEDULE, WEEK-SCHEDULE, AND ANNUAL-SCHEDULE, you
can see that when you find yourself typing simply "SCHEDULE" after your
command an alarm should go off in your head that says something like "Oh,
oh, I'm putting some nonsense into eQUEST that may cause the program to go
off in some sort of GI/GO loop, I guess I'd better research the topic a bit
more."
You sound like a user of some experience so I will just encourage you to dig
a little deeper, keeping in mind the schedule structure in eQUEST and the
use of the Building Description Language.
Cheers,
Carol