Weekly schedule output processing

For any weekly schedule (BooleanSchedule, EnumSchedule, NumericSchedule, StringSchedule), output recalculation occurs upon any of the following:

Any saved change to its configuration
Any change at its input
Station startup
Any change to the system clock

Each component has an Out slot and an Out Source slot. In addition, Next Time and Next Value slots are available. By default, all of these slots are “pinned” on the component’s shape on the wire sheet, as shown in Figure 313. Upon any output change, all of these slots are updated.

Out slot

A schedule’s output value is determined by the following, in highest-to-lowest priority:

To any “non-null” value at its In slot (if linked)

This value is immediately passed to its output. Otherwise (if null), processing continues.
If the schedule is not effective, the output goes to the default output value.

If the schedule is effective, the output goes to the (highest priority) active special event (if any).
To the active weekly schedule event (if any).
To the default output value.

For more details on effective schedules, see Effective Period.

Out Source slot

Out Source provides a string “source description” of the current output, as one of the following:

Input
Special Event: <SpecialEventName>
Week: <day_of_week>
Default Output

Examples might appear as “Week: monday” or “Special Event: Christmas Break”

Next Time and Next Value slots

These slots provide “look-ahead” data: the next known schedule output value, and its time of change.

Next Time — Displays in Baja AbsTime format, for example: 03-Feb-05 5:00 PM
Next Value — The next scheduled output value.

Typical application is for informational display. If needed, slots can be linked into control logic. For example, TimeDifference and CurrentTime objects (kitControl, Timer) provide AbsTime slots too.