Creating the day schedule (one-time exception), 396 scheduling – Echelon SmartServer 2.2 User Manual
Page 395

396
Scheduling
SunRise
0
100
60
AM
Peak Time
Starts
AM
Peak Time
Ends
PM
Peak Time
Starts
PM
Peak Time
Ends
SunDown
END
ON_100
Priority 210
OFF
Priority 200
ON_60
Priority 220
Day Schedule (One-Time Exception)
Night Schedule
Peak Time Schedule (One-Time Exception)
Light
Level
Time
END
END
In this example, three recurring exceptions are used in a single Event Schedulers to turn off, turn on,
brighten, and dim a luminaire through its SNVT_switch data point: the Day Schedule (OTE) turns off
the luminaire every day, the Peak Time Schedule (OTE) turns on the luminaire and sets its brightness
to 100% every weekday, and the Night Schedule dims the luminaire to 60% every day.
Note: In this example, additional user-defined presets have been created for the SNVT_switch data
point on the luminaire. These presets include ON_60 and ON_100, which set the SNVT_switch data
point to 60.0.1 (60% brightness and on) and 100.0 1 (100% brightness and on), respectively. These
presets are used in addition to the pre-defined OFF preset, which sets the SNVT_switch data point to
0.0.0 (0% brightness and off). See the Selecting Data Points section earlier in this chapter for more
information on creating presets for data points that have been added to the Event Scheduler.
Creating the Day Schedule (One-Time Exception)
The example Day Schedule (OTE) turns off the luminaire at sunrise. Designing the Day Schedule
(OTE) entails creating a one-time exception that recurs every day with a single event:
1. An OFF event with a 200 priority that is scheduled to start at sunrise and end at sundown. At
sunrise, this event sets the luminaire’s SNVT_switch data point to 0.0 0, turning the luminaire off.
The OFF event executes because its priority (200) is higher than that of the current ON_60 event
(220) or ON_100 event (210). At sundown, the OFF event ends, which resets its priority to 255
and releases its lock on the luminaire’s SNVT_switch data point. The highest-priority event
occurring prior to the OFF event (if any) is executed. If there are no such events, the next
highest-priority event will execute at its scheduled time.