Unlike most “fieldbus” drivers such as Bacnet and Lonworks, the status of an NdioNetwork can be “down,” in addition to the normal “ok” or less typical “fault” (fault might result from misconfiguration of a network component). A down status might occur in the case of external I/O where the physical connection to the JACE was removed (no communications are possible).

The Health slot contains historical timestamp properties that record the last network status transitions from ok to any other status. The “Fault Cause” property further explains any fault status.

As in other driver networks, the NdioNetwork has an available “Alarm Source Info” container slot you can use to differentiate Ndio network alarms from other component alarms in the station. See “About network Alarm Source Info” in the Drivers Guide for more details.