Unresponsive Devices

Overview

• If a Who-Is is sent to a device, and no I-Am is received, that device is flagged as unresponsive.

Why it fails

• Bad programming links.
• Bad graphics links (phantom devices).
• Incorrect Data Exchange.
• No power (unplugged, failed, or intermittent power supply).
• No network (not physically plugged in, wire broken, intermittent).
• Loss of communication.
• Too many devices on the same transformer.
• Router above it is offline or overloaded (*Check for Unresponsive Routers first).

How to fix it

• Check to ensure there are no Unresponsive Routers first. If there are, fix them. (This is very common)
• Identify the devices that are unresponsive.
• Check if they are physically there (look at a list or check in person).
• If they are there and are supposed to be there, put them back online.
• If they aren’t supposed to be there, trace the source in Visual BACnet, and fix the device that keeps asking for it.
• If it keeps going offline, track how much traffic is being sent to the destination to see if it’s being overloaded (use the graphs).

Watch us troubleshoot unresponsive devices in this live troubleshooting webinar on a university! Skip ahead to 1:11 and 3:57 for the unresponsive devices diagnostic check.