Exporting a schedule
You would export a schedule from a remote station to the Supervisor station connected to the BACnet network. A BacnetScheduleExport descriptor pushes schedules or calendars components to specific BACnet Schedule or Calendar objects in the Supervisor station.
Prerequisites: You are using
The BacnetNetwork’s contains a Bacnet Schedule Export Manager view, which permits exposing schedule components in the station as either BACnet schedule objects or calendar objects. This
server-type export makes exported components available to any networked BACnet device. It does not write to specific objects
in a BACnet device, which act as clients.
Perform the following steps:
- To create a schedule export descriptor, expand , right-click Schedules and click .The Bacnet Schedule Export Manager opens.
- Click New, accept the default
Type to Addand click OK.The New window opens.
- To define the location of the schedule, select the
Supervisor Ord.The Select Ord window opens.
- Set the
Priority For Writingas needed by the application in the BACnet device. - If needed, adjust the
Execution Time(write synchronization) or set toDailyor evenManual(which requires an export from the Bacnet Schedule Export Manager). - To create the schedule export job, click OK.The Framework adds the descriptor to the database, and makes an attempt to write the (source) configuration into the (target) BACnet schedule or calendar object. If successful, the status of the BacnetScheduleExport component remains ok, and its row in the Database table of the export manager remains white.
However, if any portion of the BACnet write failed, the BacnetScheduleExport reports a fault status, and its row in the export manager’s Database table appears orange.
- In the case of a fault, access the BacnetScheduleExport properties and examine the Fault Cause. If necessary adjust the
Skip Writesproperty. - To export the schedule, select the row in the table and click Export.
The manager automatically performs object ID maintenance on exported components, which ensures that the driver creates no
duplicate combinations of
Object Type and Instance Number. It also adds to each exported object an OutOfServiceExt.