As previously mentioned, starting in AX-3.2 only the single selected property of the BACnet object is polled by default, for any Bacnet proxy point.For example, if you add a proxy point for a Binary Input object and select “presentValue” as its Property Id, by default that is the only value polled in the source object. If that BACnet object was to have a native “in_alarm” status, you would have no indication in Niagara—it would show only Niagara point status, such as “ok”.

Starting in AX-3.7u1, a similar change was made for Bacnet proxy points using COV (not polling). For related details, see Changes in COV statusFlags reporting.

However (if needed), you can edit the point facets of any Bacnet proxy point to include additional properties (beyond the configured property) for polling—one of which could be “statusFlags.” Note this facets edit applies to the main point’s facets (and not “device facets” in its ProxyExt).

The facet edit sequence in Figure 41 shows facets editing (in AX-3.3) to include statusFlags.

Figure 41. Adding “statusFlags” facet to point’s facets for polling

To add to the point poll using this technique, add Boolean facet(s) with any of these (Key) names:

After adding additional facet(s), resulting metadata from additional polled properties is reflected in the status of a proxy point in the following ways:

To reproduce the “pre-AX-3.2” status display of a proxy point configured to poll for “presentValue” of a commandable BACnet object (with a priorityArray, such as an Analog_Output, Binary_Output, etc.), you need to use the technique described above to add two facets to the proxy point:

Advanced “add DOPR slot” to ProxyExt method

In AX-3.2 and later, in addition to editing the proxy point’s facets to poll additional properties (see Facets usage to poll additional properties), the point’s ProxyExt can have a slot added that points to a specific property for additional polling—even one in a different BACnet object and/or BACnet device. This technique is based on a “BacnetDeviceObjectPropertyReference” format (or DOPR, for short), where numerical codes are required for processing.

Figure 42 shows a slot of the proper type being added to the ProxyExt of a proxy point.

Figure 42. Adding slot in proxy point for DOPR poll method

After adding the slot, go to ProxyExt’s property sheet and edit the new slot’s properties to poll/display the property needed. Figure 43 shows a DOPR example for property “highLimit” (Property Id 45) of Analog Input 1 in the same device (device -1).

Figure 43. Configuring properties in DOPR slot in ProxyExt for DOPR poll method

Due to the complexity of this technique, it is expected to be infrequently used. However, in certain applications, such as with Event Enrollment objects (a BACnet object that monitors other objects for the purpose of generating alarms based on its own algorithm), it may prove useful.

The resulting metadata is included with the name of the DOPR. If it is an Event Enrollment object, and the DOPR property is Event_State (the alarm state of the EE object), the facet appears like:

<EEinstanceNumber>=<EE event state>

if another property, the facet is:

<EEinstanceNumber>_<EEpropId>=<prop value>