37
Schedules may also be given differing ON and OFF priorities. Schedules that are assigned priorities MUST have both ON and OFF
events. This is required because the higher priority event must be canceled by an opposite event set at priority = LOW in order
to be canceled. A schedule with a higher priority ON event will hold the relays in the ON state until either the priority = LOW OFF
event for the same schedule occurs or a mapped input with a higher priority than the schedule ON occurs.
PRIORITY EXAMPLES
Example 1: The project has an area that requires a Manual-ON-Automatic-OFF control scenario where the switch at the entrance
of the space must be activated before the ceiling mounted motion sensor is allowed to turn lights ON. Once the lights are ON the
switch may be used to turn them OFF or the sensor will turn them OFF automatically once vacancy is detected and timeout period
has passed. Once lights are turned OFF the area is reset for the next ON event to be manual with the switch again.
Example 1 Programming Steps:
1. Set the wall switch priority as ON command = HIGH, OFF command = LOW.
2. Set the motion sensor priority as ON command = NORMAL (Default) OFF command = LOW.
How it works:
When an occupant enters the motion sensor will see them and initiate and ON command. The panel will check to see if there
are any other devices controlling the relay with a higher level priority ON command. In the case since the wall switch has an ON
command at priority HIGH and the sensor with priority ON command at Normal, the panel will ignore the sensor ON command until
the switch initiates its ON command. In order to turn the lights ON the occupant will rst need to initiate an ON command from the
switch.
When the occupant leaves the room the switch and the sensor have equal priority OFF command at LOW. This means that either
the switch or the sensor can turn the lights OFF at any time. Once the OFF event has been executed then the system returns to the
original manual ON state requiring the higher priority ON switch to be activated to turn lights ON.
Example 2: The project has time schedules set up during the day with a 7:00AM ON and an 8:00PM OFF schedule for Monday
through Friday. They do not want the wall switches to work at all during the day but would like them to work after the 8:00PM OFF
time.
Example 2 Programming Steps:
3. Set the wall switch priority as ON command = NORMAL (Default), OFF command = NORMAL (Default).
4. Set the 7:00AM ON schedule to be at the HIGH level. Set the 8:00PM OFF schedule to be at the LOW priority.
How it works:
At 7:00AM the time schedule will turn the lights on, with a priority level of HIGH. The lower priority wall switch will not be able to
work.
At 8:00PM the time schedule will turn the lights off, with a priority of LOW, releasing control of the relay to other inputs. The wall
switch will now work until the next 7:00AM priority level HIGH on Schedule activates.
ALTERNATE Method Using MASKING:
Example 2 – Alternate – Programming Steps:
1. Set the wall switch masking for the OFF command for a start time of 7:00AM and end at 8:00PM
2. Set the wall switch priority as ON command = NORMAL (Default), OFF command = NORMAL (Default).
3. Set the 7:00AM ON schedule to be at the NORMAL (Default) level. Set the 8:00PM OFF schedule to be at the NORMAL
(Default) priority.
How it works:
At 7:00AM the time schedule will turn the lights on, with a priority level of NORMAL.
Starting at 7:00AM the switch OFF commands will be ignored since they are masked. The wall switch will not be able to turn
lights OFF until the mask period ends at 8:00PM. During the mask period ON commands can still be sent, but since the relays
are already ON the state will not change. The purpose of leaving the ON un-masked is so that if for any reason relays are manual
turned OFF they can always be turned back ON.
To Next Page
Loading...
