Bacnet Schedule Export (bacnet-BacnetScheduleExport)

This component exports the configuration of a schedule or calendar into a specific Schedule or Calendar object in a BACnet device. The schedule in the remote BACnet device functions as the subordinate schedule. The driver periodically synchronizes the values by writing its local values to the remote device using WriteProperty service requests. You add BacnetScheduleExports using the Bacnet Schedule Export Manager view.

Figure 75. Bacnet Schedule Export properties

You can export any schedule component (residing anywhere in the station), into a device’s existing BACnet Schedule or Calendar object. In this case, the schedule has supervisory control over the remote BACnet Schedule object, essentially swapping in its configuration.

In addition to the common properties (Status, Enabled and Fault Cause), this component has these properties.

Property	Value	Description
State	read-only	Indicates the condition of the BACnet schedule.
Last Attempt	read-only	Reports the date and time of the last attempted execution.
Last Success	read-only	Reports the last time the station successfully performed this function.
Last Failure	read-only timestamp	Reports the last time the system failed to perform this function. Refer to `Fault Cause` for details.
Supervisor Ord	additional properties	Identifies the local station ORD for the schedule.
Object Id	drop-down list and number (from 0 to 4194302)	Identifies each device and component by the type of entity (`Object Id`) combined with a unique `Instance Number`. For devices (controllers, instruments, meters, etc.), `Instance Number` must be unique within the BACnet internetwork. For components (points, schedules, analog inputs, files, groups, multi state inputs, etc.), it must be unique within the device.
Data Type	read-only	Reports the ASN (Abstract Syntax Notation) data type for a device property. The driver automatically converts values to this appropriate type. For example, an analog input present value is an ASN REAL that can be interpreted by a string point as a character string. ENUMERATED is another example.
Priority for Writing	numeric text values 1 through 16	Reports schedule priority, which defaults to 16.
Skip Writes	read-only	Adjusts which property types in a target BACnet schedule object the system writes to upon an export from a weekly schedule component.
Write Enum As	drop-down list	Defines how to write Enum data as Unsigned: ENUMERATED or as an INTEGER.

About schedule export Skip Writes

Depending on the BACnet device’s implementation by vendor, some properties of its schedule objects may be read-only. For example, a BACnet schedule object may allow writes to its weekly schedule events, but not to its exception schedule (special events), if they are read-only (or perhaps do not even exist). Or, the object’s Priority_For_Writing property may be read-only, or the object may not even have a weekly schedule or exception schedule (a schedule must only have one or the other, it may have both).

To allow for this, a BacnetScheduleExport component provides a Skip Writes property in which you can specify the properties to be written upon an export from the software. From the property sheet, click the far-right side control for a popup Facets Editor.

Figure 76. Skip Writes property of BacnetScheduleExport component

As shown above, the default is to not skip writing any properties upon export (false for all), meaning that all property areas of the source schedule component are written to the target BACnet Schedule object. As needed, set any of these in the Facets Editor to true, such that the software does not attempt to write to them. This can allow an export without a fault.

NOTE: Skip Writes does not apply if exporting to a BACnet Calendar (from a CalendarSchedule).

The Skip Write property areas (facets) are:

weeklySchedule — Corresponds to the regular day-of-week events of the source schedule, as defined in its Weekly Scheduler view.
exceptionSchedule — Corresponds to all special events of the source schedule.
effectivePeriod — As defined by the Effective Period in the source schedule.
priorityForWriting — As defined by the Priority For Writing property in the BacnetScheduleExport component itself (instead of the source schedule).