To use weekly schedules and the trigger schedule, you link the component’s “Out” slot (as source) to a slot on another component. The same schedule can be linked this way to many target components.
Typically, you do not link a CalendarSchedule. Instead, you reference one or more CalendarSchedules from a weekly schedule, in its “special events” setup. This allows global editing of day definitions.
Typically, you link a weekly schedule to one or more “writable” control points. For some examples, you could link the Out slot of weekly schedule types as follows:
BooleanSchedule to a BooleanWritable that is a proxy point for a Binary Output object in a BACnet device.
NumericSchedule to a NumericWritable that is a proxy point for setpoint NVI in a LON device.
By convention, when linking to a target writable point (with 16-level priority array), you select “In16” among its different priority array inputs. However, you are free to select any available input level.
In a few cases, you may wish to “chain” weekly schedules from “Out” slot to “In” slot. This technique is typically useful only if one of the chained schedules is “effective” during any period in time. In this case, the default output value of all schedule components (except last in chain) must be null.
Typically, you link a trigger schedule to an action of a control point or perhaps even more often, an action of a point extension. For example, you could link a TriggerSchedule to the “ResetElapsedActiveTime” action of a DiscreteTotalizerExt, a point extension for a BooleanPoint used to accumulate runtime. If the trigger schedule was configured to fire only on the first day of every month (at 12:00am) that extension could be used to hold the current month’s runtime.
Copyright © 2000-2014 Tridium Inc. All rights reserved.