Types of objects to export

To export components you use the Export Table’s Bacnet Export Manager view. To export files, you use the Bacnet File Export Manager view. To export histories you use the Bacnet Niagara Log Export Manager view.

Objects for export as BACnet objects

Station component, file, or history type BACnet object choices Notes
Alarm Class Notification Class Alarm Class components (under the station’s AlarmService) export as BACnet Notification Class objects.
String Point, String Writable String Input Proxy points under any BACnet driver are supported.
BooleanPoint, BooleanWritable, various kitControl components (that is, Logic), which have a null ProxyExt. Binary Input Proxy points under any driver are supported.

Acceptable kitcontrol components to export include all Logic components. Typically, you export these as value-type objects (Analog Value, Binary Value, Multistate Value).

Binary Value
BooleanWritable (additional choices) Binary Output
Binary Value Prioritized
EnumPoint, EnumWritable Multi State Input Proxy points under any driver are supported. The facets, range, ordinal (integer) in the exported EnumPoint or EnumWritable must begin with 1, and not 0. The range must also be contiguous up to the maximum value (gaps in the range are not allowed).Otherwise, the object does not export to BACnet.
Multi State Value
EnumWritable (additional choices) Multi State Output
Multi State Value Prioritized
NumericPoint, NumericWritable, various kitControl components (that is, Math) Analog Input Proxy points under any driver are supported. Acceptable kitcontrol components to export include all Math components.
Analog Value
NumericWritables (additional choices) Analog Output
Analog Value Prioritized
LoopPoint Loop Loop object export is default. You can export a LoopPoint as a BACnet Loop object.
Analog Input
Analog Value
BooleanSchedule, EnumSchedule, NumericSchedule, StringSchedule Schedule

In addition, you can selectively export the configuration of a standard schedule or calendar into an existing Schedule object or Calendar object in a client BACnet device, using the Bacnet Schedule Export Manager view of that BacnetDevice’s Schedules extension.

You cannot export a TriggerSchedule because BACnet has no object equivalent.

CalendarSchedule Calendar
<file> (any) File Files under the station folder can be exported.
<history> (any) Trend Log Two different methods exist for exporting histories.