[UFO2_HEARTBEAT:#] Required Heartbeat 1 Tag 0 31 / None – (IF-Node1) The ExDesc must start with the Updated by the case sensitive string: Interface on [UFO2_HEARTBEAT:#] IFNode1 The number following the colon (:) must be the Failover ID for the interface running on IFNode1. The pointsource must match the point source. interfaces’ Location1 must match the ID for the interfaces. [UFO2_HEARTBEAT:#] Required Heartbeat 2 Tag 0 31 / None – (IF-Node2) The ExDesc must start with the Updated by the case sensitive string: Interface on [UFO2_HEARTBEAT:#] IFNode2 The number following the colon (:) must be the Failover ID for the interface running on IFNode2. The pointsource must match the point source. interfaces’ Location1 must match the id for the interfaces. [UFO2_DEVICESTAT :#] Required Device Status 1 Tag 0 99 / None – (IF-Node1) The ExDesc must start with the Updated by the case sensitive string: Interface on [UFO2_HEARTBEAT:#] IFNode1 The value following the colon (:) must be the Failover ID for the interface running on IF-Node1 The pointsource must match the point source. interfaces’ Location1 must match the id for the interfaces. A lower value is a better status and the interface with the lower status will attempt to become the primary interface. The failover 1 device status tag is very similar to the UniInt Health Device Status tag except the data written to this tag are integer values. A value of 0 is good and a value of 99 is OFF. Any value between these two extremes may result in a failover. The interface client code updates these values when the health device status tag is updated.
[UFO2_HEARTBEAT:#] (IF-Node1) Required Heartbeat 1 Tag The ExDesc must start with the case sensitive string: [UFO2_HEARTBEAT:#] The number following the colon (:) must be the Failover ID for the interface running on IFNode1. The pointsource must match the interfaces’ point source. Location1 must match the ID for the interfaces. 0 – 31 / None Updated by the Interface on IFNode1 [UFO2_HEARTBEAT:#] (IF-Node2) Required Heartbeat 2 Tag The ExDesc must start with the case sensitive string: [UFO2_HEARTBEAT:#] The number following the colon (:) must be the Failover ID for the interface running on IFNode2. The pointsource must match the interfaces’ point source. Location1 must match the id for the interfaces. 0 – 31 / None Updated by the Interface on IFNode2 [UFO2_DEVICESTAT :#] (IF-Node1) Required Device Status 1 Tag The ExDesc must start with the case sensitive string: [UFO2_HEARTBEAT:#] The value following the colon (:) must be the Failover ID for the interface running on IF-Node1 The pointsource must match the interfaces’ point source. Location1 must match the id for the interfaces. A lower value is a better status and the interface with the lower status will attempt to become the primary interface. The failover 1 device status tag is very similar to the UniInt Health Device Status tag except the data written to this tag are integer values. A value of 0 is good and a value of 99 is OFF. Any value between these two extremes may result in a failover. The interface client code updates these values when the health device status tag is updated. 0 – 99 / None Updated by the Interface on IFNode1
PI_ModbusS_4.0.7.61.docx