The Niagara name for the Bacnet proxy point. If you added the point from a discover (selecting the default “presentValue” property), and did not edit Object Name, this will be identical to the BACnet object’s name. As needed, you can edit when adding, or at any later time.

The current out value, including any point facets. For (presentValue) proxy points before AX-3.2, this includes both the BACnet “Present_Value” and the logical “OR” status merger of the BACnet object’s “Status_Flags” (in_alarm, fault, overridden, out_of_service) along with Niagara point status.

BACnet status flags “in_alarm” and “out_of_service” OR with Niagara status “alarm” and “disabled,” respectively. Status flags “overridden” and “fault” map OR to identically named Niagara statuses. For more details, see Status merger for Bacnet proxy points.

Also, (before AX-3.2) if a writable proxy point for a “priority type” BACnet object (Binary_Output, Analog_Output, etc.), the out value facets always include the active BACnet priority array level (1—16), as the object’s “Priority_Array” is also automatically polled. By default, this is formatted as “bac=n”. For example, a (presentValue) BooleanWritable point for a Binary_Output object may have an out of:

On {ok} @ 16 bac=16

Where here, the active Niagara point priority level (@ 16) agrees with the current BACnet priority level.

Starting in AX-3.2, out display of a proxy point defaults to only the single (configured) property value, along with Niagara status for the proxy point. However, you can edit point facets to poll for additional properties, such as the native “statusFlags” and/or “priorityArray” level. For details, see Facets usage to poll additional properties.

Just as in the Discovered table, this is the “Object_Identifier” property of the proxied BACnet object, which is a combination of BACnet object type and instance number (unique within that type). In this column, these two field appear separated by a “:”, using Niagara descriptors for type. For example:

The BACnet property name proxied by the point. For example “Present Value” or “Event State,” depending on selection.

Do not change Property ID on an existing Bacnet proxy point. This often produces undesirable results, especially if a different control point type would apply. Instead, make a new proxy point.

Applies only if an “arrayed” property, like “Priority Array” (otherwise it is “-1” for no index). Provides a numeric index into the property array.

The read-only “Read Status” of the ProxyExt, which is typically either “Polled,” “COV,” or “unsubscribed,” depending on a number of factors. If a read error occurs, other descriptive text may appear instead.

The read-only “Write” status of the ProxyExt, which is typically “readonly” if the proxy point is not writable, or if a writable point type, either “writable” or “ok” (last Niagara write occurred within effective Tuning Policy period). Or, if a write operation fails, the write status provides some descriptive text.

For example, if you create a writable point for a readonly object (say, a NumericWritable for presentValue of an Analog_Input object), and attempt to write from Niagara, following this the write status may show: “Property:Write Access Denied”. If the error is actually a BACnet Error, then this colon-separated format will contain the Error Class and Error Code returned by the device.