About schedules

Schedules control the activities of other components. Schedules originate in a source station, Supervisor or remote controller and can be transferred to another station.

Schedules under the NiagaraNetwork

Under the NiagaraNetwork of a Supervisor or controller station, a schedule device extension (NiagaraScheduleDeviceExt) serves as a container component for schedules (Boolean, numeric, calendar, etc. NiagaraScheduleImportExts) imported from another station.

Figure 20.   Example of the Schedule Import Manager under the NiagaraNetwork
Image

The buttons at the bottom of the Schedule Import Manager create and configure the sharing of schedule components among stations. The receiving station manages this transfer. Unless you are working offline, you can use the learn mode (object discovery) in the receiving station to import schedules.

After it imports each schedule component, the software automatically creates a corresponding schedule export descriptor in the sending station. A separate Export Manager view provides access to schedule export descriptors. If necessary, you can review and adjust the export descriptor properties using the Schedule Export Edit window.

NiagaraStation schedules

A Supervisor station has an additional use for the schedule extensions. Under each of its NiagaraStations, a Schedule device extension contains the import schedule extensions found in each remote station. The manager views under each NiagaraStation work uniquely from the way they work in other drivers.

By default, when you import a schedule under a NiagaraStation using the Schedule Import Manager, the import/export setup is initially configured on both sides as follows:

  • On the receiving (slave) side, the driver configures each schedule import extension component with an Execution Time of Manual. Creating a schedule imports (pulls) the source schedule’s configuration only once. You can manually import it again.
  • On the sending (master) side, a corresponding export descriptor configures the schedule transfer with an Execution Time of Interval set to five (5) minutes. You can adjust this value using the Schedule Export Edit window.

    To review all properties of a schedule export descriptor, including Status, use its Property Sheet in the Nav tree under Schedules by double-clicking on the Export tool (Image).

    The default configuration does not mean that the driver continuously exports (pushes) the same schedule configuration to the remote schedule at the interval rate. Instead, the export descriptor keeps a Subordinate Version timestamp from the last export. If a configuration change occurs, the export descriptor compares this time against the configured interval, and, if necessary, exports the schedule to the remote station.

Reverse push

The default master push configuration is the most efficient (and recommended) way to keep imported schedules synchronized. However, if the network does not allow this method (perhaps due to firewall restrictions), you can configure things in reverse: set up the receiving sides Execution Time for Interval and disable the corresponding schedule export descriptors. This periodically re-pulls the schedule configuration.