
The Allen-Bradley 1756-DHRIO/C is a ControlLogix communication interface module designed to connect ControlLogix systems with Data Highway Plus (DH+) and Universal Remote I/O networks. It provides two communication channels, allowing the controller to exchange data with compatible PLCs, remote I/O adapters, and other devices in legacy industrial automation installations.
When communication problems occur, the cause may be related to the module itself, the ControlLogix chassis, network wiring, node addressing, Remote I/O rack configuration, or communication routing. A fault affecting one channel does not necessarily mean that the other channel has failed.
This guide provides a practical diagnostic approach for identifying common 1756-DHRIO/C problems. It covers front-panel indicators, alphanumeric status messages, DH+ communication faults, Remote I/O scanner faults, controller messaging errors, and module replacement considerations.
| Fault Symptom | Possible Cause | Recommended Inspection |
|---|---|---|
| Module does not start normally | Chassis power problem, incomplete insertion, or internal module fault | Check chassis power, module seating, and status indicators |
| DH+ network communication is unavailable | Incorrect node address, damaged cable, or network configuration problem | Inspect node settings, cable continuity, and network termination |
| Duplicate node message appears | Two DH+ devices use the same node address | Check the address settings of all devices on the affected link |
| Remote I/O adapters are faulted | Adapter power loss, cable failure, or incorrect rack configuration | Check remote rack power, network wiring, and adapter status |
| Remote I/O channel reports no active link | No responding adapters or an incorrect network connection | Check the complete Remote I/O link and connected adapters |
| Controller MSG instruction fails | Incorrect destination, routing path, or unavailable communication connection | Review the MSG configuration and routing path |
| Communication is intermittent | Loose wiring, poor termination, electrical noise, or unstable power | Inspect connectors, cable routing, grounding, and power supply |
| Module displays a configuration fault | Incorrect module configuration, chassis slot mismatch, or routing configuration problem | Review the project and communication settings |
Before replacing the module, determine whether the fault affects the complete ControlLogix system, one communication channel, or only a particular network device.
Recording the original status information is important. Restarting the module before recording its display messages may remove useful diagnostic evidence.
The 1756-DHRIO/C uses an alphanumeric status display and several indicators to show its operating condition. The display cycles through information for Channel A and Channel B, including the network type and channel status.
| Indicator State | General Meaning | Recommended Action |
|---|---|---|
| Off | Module is not operating | Check chassis power and confirm that the module is fully inserted |
| Flashing green | Module is operating but may not be routing messages or transferring I/O | Determine whether communication activity is expected and review configuration |
| Red, then off | Module is performing its startup self-test | Allow the startup sequence to complete |
| Green | Module is operating and routing messages | Normal operating condition |
| Steady red | Major module fault | Record the display message and follow the approved restart procedure; replace the module if the fault returns |
| Flashing red | Major fault or configuration fault | Check the alphanumeric display and investigate the indicated condition |
| Indicator State | DH+ Interpretation | Remote I/O Interpretation |
|---|---|---|
| Off | Channel is not online | Channel is not online |
| Green | Channel is operating normally | Active Remote I/O link; adapters are present and not faulted |
| Flashing green | No other node detected on the network | One or more nodes are faulted or have failed |
| Steady red | Hardware fault | Hardware fault |
| Flashing red | Duplicate node detected | Faulted adapters detected |
Indicator behavior must be interpreted together with the selected channel mode. For example, a flashing channel indicator has different diagnostic meanings in DH+ and Remote I/O operation.
The alphanumeric display is one of the most useful diagnostic features of the 1756-DHRIO/C. It identifies the channel, network type, and current communication condition. Record the complete message rather than relying on a single momentary display segment.
| Display Message | Meaning | Recommended Troubleshooting |
|---|---|---|
| OFF LINE | DH+ link is in the STOP state | Review the channel configuration and place the link online using the approved configuration procedure |
| DUPL NODE | Duplicate DH+ node address detected | Identify the conflicting devices and assign a unique node address |
| ONLY NODE | No other node is detected on the DH+ link | Inspect the network cable, connectors, termination, and power status of other devices |
| CNFG FALT | Incorrect DH+ routing table or Data Highway object configuration | Review the module slot, controller configuration, and routing information |
| OK | Channel is operating normally | No corrective action is required |
| Display Message | Meaning | Recommended Troubleshooting |
|---|---|---|
| MUTE LINK | No Remote I/O adapters have been detected | Check that compatible adapters are installed, powered, and connected |
| RACK OVER | Remote I/O rack address overlap | Review rack assignments and remove overlapping rack addresses |
| DUPL SCAN | Duplicate scanner condition | Check the network design and adapter configuration for conflicting scanner assignments |
| MAX DEV | Maximum device or rack limit exceeded | Review the number of connected devices and rack assignments against the network limits |
| CHAT LINK | Excessive or abnormal communication activity has been detected | Inspect Remote I/O devices, network connections, and possible communication faults |
| OFF LINE | Channel is not attempting Remote I/O communication | This can be normal when no controller is controlling the Remote I/O channel; verify the intended operating state |
| OK | Remote I/O channel is operating normally | No corrective action is required |
If the DH+ network is unavailable, start by checking the channel’s node address and physical network connection. DH+ devices on the same link must use unique node addresses and compatible communication settings.
Review the address settings of the 1756-DHRIO/C and all other devices connected to the same DH+ link. A duplicate address can prevent normal communication and cause the channel to report a duplicate-node condition.
A DH+ link may fail because of an open conductor, loose connector, damaged cable, incorrect wiring, or unsuitable termination. Inspect the complete network rather than only the cable connected directly to the ControlLogix module.
Where the network contains multiple devices, a fault at another node or cable segment may affect communication at the ControlLogix end.
When a channel is configured as a Remote I/O scanner, the 1756-DHRIO/C communicates with compatible remote adapters and their connected I/O racks. A scanner fault may result from an adapter losing power, a damaged network cable, an incorrect rack address, or an incompatible configuration.
Begin by checking the power status of each affected remote rack. If several adapters become unavailable at the same time, a common power supply or network problem may be responsible.
Review the Remote I/O configuration for rack numbers, starting groups, rack sizes, and adapter assignments. Overlapping rack assignments can produce a rack-overlap fault. Incorrect or duplicated scanner arrangements can also prevent normal communication.
Check the project configuration against the actual installed equipment. Pay particular attention to changes made during replacement of remote adapters or expansion of the I/O network.
Check the cable route from the scanner channel to the remote adapters. Inspect connectors, terminal blocks, cable shielding, and network termination. If a channel reports faulted adapters, investigate both the affected rack and the shared cable path.
The 1756-DHRIO/C can route messages between ControlLogix systems and compatible DH+ devices. If an MSG instruction fails, the problem may be related to the destination address, communication path, module configuration, or an unavailable network connection.
A local DH+ message-routing error may indicate that the module cannot route the message using the configured path. For messages to remote DH+ devices, check the gateway node, link identification, destination node, and routing tables of intermediate modules.
If a message reports an unavailable connection, review the number of active communication connections and the resources available on the channel. Do not assume that changing the MSG timeout will correct an incorrect routing path or an offline destination device.
For applications that use block transfers, confirm that the target I/O module is present, correctly configured, and responding on the Remote I/O network. Check the block-transfer read or write configuration, rack and module addressing, and controller diagnostic information.
If a block transfer repeatedly times out, investigate the remote adapter and I/O module before changing application timing parameters. A timeout may be the result of a communication failure rather than an incorrect timeout setting.
A configuration fault may appear after a module replacement, chassis change, project modification, or routing-table update. The module’s stored configuration must correspond to the actual ControlLogix installation and intended communication design.
Recommended checks include:
Do not repeatedly download configuration files or change routing settings without first identifying the mismatch. Preserve a copy of the working project before making changes.
In some installations, a DH+ communication path involving a 1784-KT or 1784-PCMK communication card may report a “Received Frame with Bad CRC” message. This message does not necessarily indicate that the DH+ link has stopped operating.
Check the DH+ network termination and inspect the cable installation. Confirm that the network is wired and terminated according to the applicable design. If the message appears alongside actual communication failures, investigate cable quality, connectors, grounding, and other network devices.
Do not replace the 1756-DHRIO/C solely because this message appears. First determine whether normal DH+ communication is still functioning.
A restart may be appropriate when the module reports a persistent hardware or major fault, but it should not be the first response to every communication alarm. Before restarting, record the display messages, channel indicator states, and controller diagnostics.
Restarting or restoring a Remote I/O communication path can affect remote I/O data and connected outputs. Coordinate the work with the process control team and follow the plant’s approved shutdown, isolation, and recovery procedures.
Do not assume that a replacement module will automatically inherit the original module’s stored configuration. Verify the actual settings after installation. Confirm compatibility for the exact series and system revision before substituting another catalog number.
It provides communication between a ControlLogix system and compatible Data Highway Plus and Remote I/O networks. It is commonly used to integrate legacy PLCs and remote I/O equipment into ControlLogix applications.
This message indicates that another device on the DH+ network is using the same node address. Check the address assignments of all devices on the affected link and correct the conflict.
It means the module does not detect another node on the DH+ network. Check the network cable, connectors, termination, and power status of other devices.
A MUTE LINK message indicates that the Remote I/O channel has not detected an adapter. Check adapter power, network wiring, connector condition, and channel configuration.
In DH+ mode, flashing green indicates that no other node has been detected on the network. In Remote I/O scanner mode, it indicates that one or more nodes are faulted or have failed. Interpret the indicator according to the selected channel mode.
Review the Remote I/O rack assignments and check for overlapping rack addresses. Compare the configured rack layout with the actual network and adapter arrangement.
This message indicates an incorrect DH+ routing table or Data Highway object configuration. Check the module’s chassis slot, controller configuration, and routing information.
Yes. Loose connectors, damaged conductors, incorrect termination, and poor cable routing can cause intermittent communication or prevent other nodes from being detected.
No. A Bad CRC message may occur in certain DH+ communication arrangements and does not necessarily stop normal link operation. Check network termination and determine whether actual communication failures are also present.
Replacement should be considered when a persistent hardware fault remains after approved restart and diagnostic checks, or when testing confirms an internal module failure. First rule out chassis power, network wiring, configuration, and remote device problems.
The Allen-Bradley 1756-DHRIO/C ControlLogix communication module supports integration between ControlLogix controllers, DH+ networks, and Remote I/O systems. Reliable operation depends on correct channel configuration, unique network addresses, valid routing information, suitable cable installation, and stable power at the local and remote equipment.
Effective troubleshooting begins with the module’s alphanumeric display and OK, CHA, and CHB indicators. DH+ faults generally require checking node addresses, cable continuity, termination, and routing configuration. Remote I/O faults require checking adapter power, rack assignments, scanner configuration, and network connections.
Before restarting or replacing the module, record the existing diagnostic information and consider the effect on remote I/O and connected equipment. A structured troubleshooting process helps identify the actual cause, reduce unnecessary hardware replacement, and maintain reliable communication in ControlLogix installations.