Device Error - Communications Timed Out

Rowan Chase

Created: ; updated: .

This error can be identified from Monitor.


It can also be identified in Manage Equipment: 



"Communications timed out waiting for device response" will be reported if one of the following is true:

  • Cable is not connected properly to the device or field unit.
  • Cabling to sensor is damaged or the cable is not the correct type: See the related articles in the next section for more information about cables. Furthermore, 
    • Ensure that the correct type of interface cable is used.
    • Inspect the cable for any damage
    • Even if damage is not apparent from external inspection, in order to rule out this possibility, the cable should be replaced with a test cable that is known for sure to work. 
  • The sensor is not plugged into the configured Port: You can check the configuration of the sensor from Manage Equipment. See this article for more details. Refer to the relevant Technical Note to see which port the sensor should be plugged into. 
  • The sensor has failed electrically and is not responding: One way to test this would be to replace the device with one that is known for sure to work.


Related Articles

Cable Guidance

Illustration — C3 Device Cabling

Illustration — Solo Device Cabling

Table — Device Cabling to C3 Field Unit Ports — Color Codes

Table — Device Cabling to Solo Field Unit Ports — Color Codes

How to Choose the Right Port Settings



Have more questions? Submit a request
Powered by Zendesk