Using the NiagaraAX driver architecture, you can create “master/slave” schedules in order to share schedule configuration between devices. This allows you to globally update the configuration of any slave schedule by simply making changes to its master schedule.
The typical application of this is in a multi-station Niagara network, where you:
-
Import a schedule component from another station. Typically, you do this in a JACE station, importing 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 a NiagaraAX schedule, a “schedule export descriptor” is automatically created on the sending (master) station, under the NiagaraStation component that represents the receiving side. This allows for “sending-side” management of configuration synchronization. For more details, refer to the section “Station Schedules import/export notes” in the Drivers Guide.
If 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 NiagaraAX schedule components.
For more details, see the following topics in the Drivers Guide:
The Bacnet driver lets you export NiagaraAX schedules from the station to existing BACnet Schedule and Calendar objects in a BACnet device, acting as the “master”
source. Also, you can expose Niagara 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.” For more
details, see the Bacnet Users Guide.