
Programming Guide
11
How an EcoSystem
®
Bus Prioritizes Inputs
When programming a system, it is important to understand how the
ballasts prioritize inputs:
1
1.. E
Em
me
errg
ge
en
nc
cyy c
co
om
mm
ma
an
nd
d ((ttyyp
piic
ca
allllyy lliig
gh
htts
s tto
o ffu
ullll o
on
n)).. The ballast’s first
priority is to ensure that no emergency exists in the building. If an
emergency exists, all emergency fixtures are automatically set to
their emergency level and all manual lighting adjustments are
ignored. If an emergency does not exist, the ballast proceeds to
the next level of priority.
2
2.. P
Prro
og
grra
am
mm
miin
ng
g c
co
om
mm
ma
an
nd
ds
s.. The second priority is to respond to a
user programming the ballast. If programming commands are
being sent, the ballast responds to the commands, but ignores
any sensor or control device input. If no programming commands
are being sent, the next priority is queued.
3
3.. D
Da
ayylliig
gh
htt s
se
en
ns
so
orr iin
np
pu
utt.. The third priority is input from daylight
sensors. The daylight sensors are checked to set the “high level,”
or the maximum light level the ballasts can be manually set to.
4
4.. O
Oc
cc
cu
up
pa
an
nc
cyy s
se
en
ns
so
orr iin
np
pu
utt o
orr p
pe
errs
so
on
na
all c
co
on
nttrro
oll tth
hrro
ou
ug
gh
h IIR
R rre
em
mo
otte
e o
orr
w
wa
allll c
co
on
nttrro
oll.. After checking the daylight sensor, the ballast waits
for the occupant sensor to detect a person in the room or for
input from a manual control. Manual control inputs come from
users dimming the lights up or down with a wall control or IR
remote. The lights will go to the level requested by the
occupancy sensor or personal control that last changed.