If you are exporting large numbers of components to BACnet, it is recommended that you use the New Folder button in the Export Table’s manager view to make multiple Bacnet export folder containers, for logical organization of export descriptors. For example, you may wish to make such one or more folders for a certain driver network, and another for Niagara schedules. Each export folder provides the same set of export manager views as the Export Table.

Note that starting in AX-3.5, export folders are exposed to BACnet as Structured View Objects, allowing a hierarchical organization of BACnet objects. For related details, see Structured View Object server support.

Before deleting any source (exported) component in the station, first delete its corresponding Bacnet export descriptor, using the Bacnet Export Manager. Otherwise, the export descriptor may remain “orphaned” in the Export Table, showing “Invalid Ord!” in the Target Name and Value columns. If this occurs, you can delete the orphaned export descriptors manually.

Any exported points or components that contain an alarm extension are automatically exposed to BACnet with properties related to alarming available. For example, if you exported a NumericPoint with an OutOfRangeAlarmExt, its exposed BACnet object (say, Analog Value) will have properties “High Limit,” “Low Limit,” “Deadband,” and so on.