CC-16 displays 'Comms Failure' and is not detected during scan

Summary
One or more CC-16s are displaying ‘Comm Failure’ and are not detected during a scan of the network.

Cause
One possible cause is that the ‘2X’ DIP switch is incorrectly set (see related Knowledge Base article).

CC-16 not detected or ‘Comms Failure’ displayed but wiring is proven correct

Otherwise this would typically indicate a data communication issue between the ESP-88 and the CC-16s. The ESP-88 sends out a regular ‘heartbeat’ to the CC-16 to maintain communication. If the CC-16 is powered up but not receiving the ‘heartbeat’ then it is interpreted as a ‘Comm Failure’.

In order for the ESP and CC-16s to communicate correctly the polarity of the RS485 data connections must be maintained (eg. A to A, B to B etc) all the way through the chain (and on each spur). Reversing the polarity at any point will prevent one or more CC-16s from communicating with the ESP.

Data grade cable should be used and a maximum cable length of approximately 610m (2000ft) should be observed for a single daisy-chain (less if multiple home-runs are used). Only the last CC-16 on the chain should be terminated (or the last CC-16 on the longest two runs if ‘star’ wiring is used).

Product
ESP-88 (v1.001 or later), CC-16 (v1.5 or later)

Workaround
Not Applicable

Resolution
Not Applicable

Links
CC-16 not detected or ‘Comms Failure’ displayed but wiring is proven correct

.