Schedule exports and imports (master/slave)

Using the driver architecture, you can create master/slave schedules to share schedule configuration among devices. This allows you to globally update the configuration of any slave schedule by making changes to its master schedule.

The typical application for export and import is a multi-station NiagaraNetwork, where you import a schedule component from another station. Typically, you import a schedule component that resides in a Supervisor station. This creates a local copy that you can use and link into control logic, but cannot otherwise configure (change events, and so on).

When you import the schedule, the scheduler automatically creates a schedule export descriptor in the sending (master) station under the Station component that represents the receiving side. This allows for sending-side management of configuration synchronization.

If you are using the BACnet driver, the same basic architecture is available. You can import BACnet Schedule and Calendar objects from a BACnet device, and model them as schedule components.

NOTE: The BACnet driver lets you export schedules from the station to existing BACnet Schedule and Calendar objects in a BACnet device, acting as the master source. Also, you can expose schedule components as BACnet Schedule or Calendar objects for access by any networked BACnet device. You do this through configuration of the Export Table under the BacnetNetwork’s Local Device.

Schedule exports and imports (master/slave)

Related Links