In addition to status flags that also apply to non-proxy points (refer to the User Guide section “How status flags are set”), some status flags in proxy points are set and cleared resulting from polled value or status updates received via the parent driver’s communications subsystem, for example:
-
down
Driver unable to receive reply from parent device, as per configuration in Monitor extension. In this case, all proxy point children of the device will have status down.
-
fault
Typically, this indicates an AX configuration error or license error. If a fault occurs following normal (ok) status, it could be a “native fault” condition detected within the device, or perhaps some other fault criteria that was met. The point’s proxy extension contains a “Fault Cause” text property that contains more information.
-
stale
Since the last poll update, the point’s value has not updated within the specified “Stale Time” of its Tuning Policy. This stale status clears upon next received poll value.
Statuses above are set automatically, but you typically set a fourth status for a proxy point manually:
-
disabled
Using the proxy extension’s Boolean property “Enabled” (default is true). While set to false (disabled), polling stops for that point, as well as any further status changes.
Typically, a proxy point has an alarm status only if its value falls in the “offnormal algorithm” limits specified in its own (NiagaraAX) alarm extension. If the
driver and protocol has “intrinsic” or “native” alarm determination methods (such as with BACnet), a proxy point may show
alarm status that originated locally within that device. In the case of the Niagara Bacnet driver, this also applies to override status, possibly a “native” condition for a proxied BACnet object.