New Products | news
New Products | Asset Monitoring Gateway with Snap ID
Success Story | news
Success Story | news
Success Story | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
New Products | news
Application | ABR Barcode
Application | iVU Barcode Reader
Application | iVu TG
New Products | news
New Products | news
New Products | R95C Modbus Hub
New Products | news
New Products | news
New Products | news
New Products | news
New Products | Asset Monitoring Gateway with Snap ID
Success Story | DXM
Success Story | Wireless Solutions
Success Story | Wireless Gateways and Nodes
Success Story | QS18
Success Story | R58
Success Story | Smart Sensors
Success Story | IRIS
Success Story | CL50
Success Story | IVU
Success Story | IVU
Success Story | PTL110
Success Story | PTL110
Success Story | PTL Products
Success Story | WLB32
Success Story | K50L
Success Story
Success Story | iVu Plus TG
Success Story | K50 Touch
Monitoring node health is important to do in a wireless network to ensure that all radios are communicating and providing up-to-date data. This example will cover using a DXM to monitor node health and send an output when a node drops communication.
The health register for performance nodes is always I/O 8 (register 24 for node 1, register 40 for node 2, register 56 for node 3, etc.). The value of this register will be “128” when the node is in normal operation. When the value is NOT 128, then this usually indicates some type of error. The most common error code to appear here is “13569” which indicates a link loss. However, it is usually best (and easiest) to monitor this input and fire an output whenever the value is NOT “128”.