Properties of the Device Object under the Bacnet Config Device Ext are populated when the device was learned. These represent BACnet Device object properties. Included are several properties that show the various protocol services and objects supported by that device.
The default view of the Bacnet Config Device Ext is the Bacnet Config Manager (Figure 26).
From this view, you can learn other config-type objects, each representing a BACnet object in that device. You might do this to “evaluate” a BACnet device, rather than for permanent station engineering. In this case, remember to delete the config-type objects afterwards, as they consume station resources. See About Bacnet Config objects.
An alternate method to evaluate the objects in a device is via its “Virtual Gateway.” This may actually be easier, as the
resulting “virtual components” are automatically removed after browsing. For more details, see Bacnet virtual points.
If a BACnet AWS Supervisor based on the AX-3.6 or later bacnetAws module, the equivalent Bacnet Aws Config Manager view on the Config device extension of each BacnetAwsDevice provides two additional buttons at the bottom (apart from those shown in Figure 26). These buttons allow you to create and/or delete BACnet objects in the device, providing that the device supports these services. For more details, see Bacnet Aws Config Manager.
A config object provides a view of a BACnet object in its native format—where all properties of that object are presented as a whole. Figure 27 shows the property sheet of an Analog Input config object.
Unlike Bacnet proxy points that you create using the Bacnet Point Manager, when subscribed, config objects poll all properties—not as efficient as the selective proxy point model. In addition, slots of Bacnet config objects use primitive or special data types, not compatible with normal linking logic.
Config objects are expected to be useful for one-time commissioning, or for proprietary objects for which the proxy point interaction may be insufficient.