IMDHMIControls LibraryShop main store

How-to

How to route a ControlLogix MSG to a PLC-5 over DH+

Industrial networks Published 6 min read

Short answer

The CIP path is 1,5,2,10.60.28.60,1,2 and it ends at the 1756-DHRIO: out the local backplane to the ENBT/A in slot 5, over Ethernet to the bridge ENBT/A at 10.60.28.60, then across the bridge backplane to the DHRIO in slot 2. DH+ carries no CIP, so Channel A and DH+ node 67 are set on the message's communication tab, never appended to the path.

On this page
  1. Why the path ends at the DHRIO
  2. Fixes that cannot work
  3. Worked example: the path from slot 5 to a DHRIO in bridge slot 2
  4. Configure the message
  5. Check the route hop by hop
  6. Prove one read before repeating it
  7. Questions asked

The path is 1,5,2,10.60.28.60,1,2, and it ends at the 1756-DHRIO, not at the PLC-5. Read it as three port-and-address pairs: out the local backplane to the ENBT/A in slot 5, out Ethernet to the bridge-chassis ENBT/A at 10.60.28.60, then out that chassis backplane to the DHRIO in slot 2. DH+ carries no CIP, so the DH+ leg is never part of the path. You select Channel A and target node 67 on the message's communication tab, and the DHRIO puts the request on the DH+ wire itself.

Why the path ends at the DHRIO #

The transport changes inside the DHRIO module. ControlLogix carries the request over CIP — local backplane, Ethernet, bridge backplane — until the DHRIO receives it. The DHRIO pulls the embedded PLC-5 (PCCC) operation out of that request, executes it on DH+ at the channel and node you configured, and carries the PLC-5's reply back over CIP to the originating controller.

That boundary splits the configuration into three layers, and crossing them up is why these messages fail:

  • The CIP path routes the request to the DHRIO module.
  • The communication tab names the DH+ channel and target node — Channel A, node 67.
  • The message's data address and element count say what the PLC-5 reads or writes.

Each pair in the path is a port number followed by an address. Port 1 is the backplane, port 2 the first network port, and port 3 the second network port on modules that have one, such as the DHRIO. With that convention, any CIP route can be read pair by pair.

A browse that reaches 10.60.28.60 proves only the Ethernet pair. The same boundary rule governs a CompactLogix MSG to an SLC 5/04 through a DH+ gateway, where the route likewise stops at the DH+ interface module.

Fixes that cannot work #

Attempted fix Why it fails
Appending 2,67 or 3,67 after the DHRIO slot DH+ carries no CIP. The DHRIO terminates the path and processes the PCCC request using the channel and node from the communication tab.
Addressing the PLC-5 as an Ethernet endpoint The only Ethernet endpoint in the route is the bridge ENBT/A at 10.60.28.60; the PLC-5 has no address there.
Adding logic to the bridge controller The request crosses the bridge backplane between two modules; the bridge controller's program never touches it.
Retiming the message trigger Trigger timing cannot repair a wrong slot, IP address, channel, or node.
Counting slots from 1 The leftmost chassis slot is 0, so a one-slot error lands the request on the wrong module with every port number correct.

Worked example: the path from slot 5 to a DHRIO in bridge slot 2 #

Inputs, all from the machine layout:

  • Originating chassis: 1756-ENBT/A in slot 5, IP 10.60.28.97
  • Bridge chassis: 1756-ENBT/A in slot 1, IP 10.60.28.60
  • Bridge chassis: 1756-DHRIO in slot 2
  • Target: PLC-5, DH+ node 67, reached over Channel A
  • Port convention: 1 backplane, 2 first network port

The rule in words: a CIP path is a chain of port-and-address pairs from the originating controller to the last CIP-capable device, which here is the DHRIO. Each pair names the port you leave by and the address of the next device — a slot number across a backplane, an IP address across Ethernet. The DH+ node is not a pair; it is a message setting.

The arithmetic:

  • Leave the controller by port 1, address slot 5 → 1,5
  • Leave that ENBT/A by port 2, address 10.60.28.60 → 2,10.60.28.60
  • Leave the bridge ENBT/A by port 1, address slot 2 → 1,2
  • Join the pairs in order: 1,5 + 2,10.60.28.60 + 1,2 → 1,5,2,10.60.28.60,1,2

The result is three pairs, six values, ending on the DHRIO's slot. Two addresses deliberately do not appear: 10.60.28.97, because the originating module's own IP is not a destination, and slot 1, because the IP pair already landed the request on the bridge ENBT/A and the next pair starts from there.

The decision: the path is right when its last pair is the DHRIO's slot. Anything after 1,2 in your path belongs on the communication tab. If the message errors before the DHRIO, one of the three pairs is wrong — fix the pair, not the PLC-5 data address.

Configure the message #

  1. Open the MSG configuration and choose the PLC-5 typed read or write the application needs.
  2. Enter the ControlLogix tag and the PLC-5 data table address with its element count. PLC-5 elements are 16-bit integers (publication 1756-PM012), so make the Logix side an INT array at least as long as the element count.
  3. Enter the path 1,5,2,10.60.28.60,1,2. When the slot 5 ENBT/A is named MSI in the I/O tree, MSI,2,10.60.28.60,1,2 is the same route.
  4. On the communication tab, select Channel A and set the target DH+ node to 67.
  5. Confirm the DHRIO's Channel A is configured as DH+ rather than Remote I/O in the module's channel configuration, covered in the 1756-DHRIO manual (publication 1756-UM514). The connector alone does not set the mode.
  6. Trigger the message once from a one-shot and read its done and error status before allowing repeated execution.

Check the route hop by hop #

Work from the origin toward the PLC-5 so a DH+ fault is not chased as an Ethernet fault:

  1. Slot 5 of the originating chassis holds the ENBT/A, and MSI, if the path shows it, resolves to that module.
  2. 10.60.28.60 is reachable on Ethernet and is the bridge ENBT/A.
  3. The DHRIO physically sits in slot 2 of the bridge chassis, counting the leftmost slot as 0.
  4. Channel A reports DH+ mode and healthy status on the DHRIO.
  5. Node 67 is powered, active, and unique on the segment; when the DHRIO is reached but the PLC-5 stays silent, check DH+ cabling and termination.
  6. Compare the PLC-5 address, element count, and destination size last.

A failure that appears before the DHRIO points at the path. A request that reaches the DHRIO without a PLC-5 reply points at Channel A, node 67, or the DH+ segment. Once traffic flows, the same route can carry a PLC-5 heartbeat without the PLC-5 sending messages, so a later DH+ failure announces itself without new wiring.

Prove one read before repeating it #

Read first, choosing a PLC-5 value you can watch in its data table. Run the message once, then compare the whole requested range against the PLC-5, not just the first element — a partial match hides an element-count or destination-size error. Confirm the message reaches done without an error, that repeated reads happen only when triggered, and that other DH+ nodes keep communicating during the test.

Test any write with one controlled, noncritical value in an address nothing on the PLC-5 side uses: a successful read proves the route, not that an unrestricted write is safe on a running machine. Keep the trigger application-controlled so two executions cannot overlap.

Questions asked

Why does the working path show MSI instead of 1,5 at the start?

A module name in the I/O tree resolves to that module's port and slot. MSI,2,10.60.28.60,1,2 and 1,5,2,10.60.28.60,1,2 are the same route as long as MSI is the ENBT/A in slot 5. If MSI points at a different module or slot, the first pair is wrong and the request never leaves the originating chassis correctly.

Does the bridge controller need configuration or logic for this route?

No. The request crosses the bridge chassis backplane from the ENBT/A to the DHRIO, and the bridge controller's program neither forwards nor touches it. What must be right in that chassis are the module configurations: the ENBT/A's IP address and slot, and the DHRIO's channel mode and slot.

What changes when the PLC-5 is on a remote DH+ link?

The CIP path does not change; it still ends at the DHRIO. The message configuration grows instead: a remote DH+ target also needs the remote node and the local and remote link IDs, beyond the channel and local target node. Node 67 here sits on the Channel A link, so only the channel and target node are set.

How do PLC-5 element counts line up with Logix tags?

A PLC-5 data table element is a 16-bit integer, and a Logix DINT is 32 bits, so the element count and the destination array length have to be chosen together. Point the read at an INT array sized to the element count; pairing a DINT destination with 16-bit source elements is the usual cause of a short or garbled transfer.

Keep reading

  • How-to

    CompactLogix MSG to SLC 5/04 through a DH+ gateway

    The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.

    Industrial networks

  • Troubleshooting

    Troubleshooting ControlNet scanning of legacy 1771 specialty I/O

    When a legacy 1771 specialty module will not scan over ControlNet, separate three layers before touching hardware: the chassis backplane allows two master/slave connections and each expander-class module takes one, the TIC-chip ASIC conflict applies to specific pairs only, and RSLogix 5000 gives you no configuration wizards for 1771 block transfer. Bench-test the exact module-and-chassis combination before go-live.

    Industrial networks

  • Troubleshooting

    Fixing a TwinCAT EtherNet/IP slave connection from an Omron PLC

    The CIP1 fault is a Forward Open mismatch: each Omron direction must carry the full serialized TwinCAT assembly, not the process variables alone. With 2 bytes in and 2 bytes out, the 4-byte ConnCtrl on outputs and ConnState on inputs make each direction 6 bytes, and the instances must follow producer and consumer roles. If a capture shows the request and a rejection, read the sizes and instances the originator actually serialized.

    Industrial networks