IMDHMIControls LibraryShop main store

How-to

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

Industrial networks Published 6 min read

Short answer

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.

On this page
  1. Where should the CIP path end for a message to an SLC 5/04 on DH+?
  2. How do I switch the MSG instruction from CIP to DH+?
  3. How do I build the path from the CompactLogix to the DHRIO?
  4. How does dual-IP mode change the route from port A2?
  5. Why can RSLinx see the SLC when the MSG instruction fails?
  6. What are the steps to configure the MSG instruction?
  7. How do I verify the DH+ message data before relying on it?
  8. Questions asked

End the CIP path at the 1756-DHRIO module and no further. On the MSG configuration tab of the CompactLogix, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields. The route to the gateway and the destination on DH+ are two separate pieces of addressing, and merging them into one long path is why the message fails. The physical route is port A2 of the 5069-L330ER, the 1756-ENBT, the remote backplane, and the DHRIO slot facing the SLC on Channel A. The sections below build the path, switch the method, check dual-IP routing, and test the data before you trust it.

Where should the CIP path end for a message to an SLC 5/04 on DH+? #

The path stops at the 1756-DHRIO module in the remote chassis: your CompactLogix routes over Ethernet to the 1756-ENBT, across that chassis backplane to the DHRIO slot, and nothing beyond it belongs in the path.

The CIP route carries your request as far as the DHRIO, and the DHRIO then runs the DH+ transaction itself, on the channel and node address you put in the message's DH+ settings. An SLC 5/04 on DH+ is not a CIP target, so extending the path to its node asks the route for something the network never delivers. Rockwell's legacy references for connecting PLC-5 processors and SLC controllers (publications 1785-RM005 and 1785-RM009) cover DH+ links through the processor's 3-pin connector with the port configured for DH+, and note that their communication modules can be configured to work with the SLC 5/04; the same division of labor applies here, with the module handling the legacy network while the controller only has to reach the module.

Keep three identifiers apart: the 1756-ENBT IP address finds the chassis, the DHRIO slot finds the module, and the SLC node address finds the station on DH+. They are not interchangeable.

How do I switch the MSG instruction from CIP to DH+? #

Open the message's configuration, change the communication method from CIP to DH+, and use the fields that then appear for the DH+ destination: select Channel A and type the SLC 5/04 node address there, never in the path.

Reaching the gateway does not select the legacy transaction; the communication method does. Left on CIP, the message is framed for a CIP exchange and the SLC never sees it: the request can arrive at a healthy DHRIO and still complete nowhere. Switching the method to DH+ tells the module to execute the DH+ transaction on your behalf, which is exactly what the separate channel and node fields exist for.

How do I build the path from the CompactLogix to the DHRIO? #

Build the path as four pieces: the local Ethernet interface, the IP address of the 1756-ENBT, the backplane of the remote chassis, and the slot number of the 1756-DHRIO; browse to the module rather than typing from memory when your software offers it.

Read the ENBT address and the DHRIO slot from the installed configuration, not from another chassis: a copied path sends a valid request to the wrong module. Worked example with illustrative values: the 1756-ENBT answers at 192.168.10.31 and the 1756-DHRIO sits in slot 4. The path is your controller's Ethernet interface, 192.168.10.31, the remote backplane, slot 4. The SLC sits at node 17 on Channel A, so 17 goes in the DH+ node field, not in the path. If the message reads SLC data file N7 from element 20 for a length of 10, it covers N7:20 through N7:29, because 20 + 10 - 1 = 29, and the destination array holds 10 elements.

How does dual-IP mode change the route from port A2? #

Dual-IP mode gives ports A1 and A2 separate IP addresses and network settings, so the controller reaches the gateway only if the ENBT's subnet is reachable from the interface and routing the controller actually uses.

Rockwell's support documentation for CompactLogix 5380 dual-IP mode defines it as assigning a unique IP address to each EtherNet/IP port, with port A1 able to sit on an enterprise network and the other port on a device network. The 5069-L330ER belongs to that 5380 family, so its two ports hold two configurations: confirm the subnet carrying the 1756-ENBT is attached to the port the message egresses, and that the controller's gateway address for that subnet is set. A perfectly configured message still times out if it leaves port A1 toward a network with no route to the chassis.

Why can RSLinx see the SLC when the MSG instruction fails? #

RSLinx browses from your workstation's network stack, not from the CompactLogix, so a successful browse proves the gateway chain works while telling you nothing about the controller's port, route, or message settings.

Use the browse as a fact-gathering tool: it hands you the ENBT address, the DHRIO slot, the channel, and the SLC node to copy into the message. Then compare those values against what the controller is actually configured to do.

What you observe What to change or check
The SLC browses fine, but the message is set to CIP Switch the communication method to DH+ and enter the node address in its own field
The path tries to continue past the DHRIO End the path at the module; the SLC address belongs in the DH+ settings
The workstation reaches the chassis, the controller does not Compare the controller's active port, subnet mask, and gateway address against the A2 network
The DHRIO answers, the SLC transaction fails Check Channel A, the node address, the message type, and the SLC data-table address
The message completes, the values are wrong Check the source file, the element count, and the destination tag type

What are the steps to configure the MSG instruction? #

Configure it in six steps: record the route, create the message, set the path, switch the method to DH+, enter Channel A with the node address, then test one transaction before wiring it into logic.

  1. Record the route values from the installed system: the controller port that carries the traffic, the 1756-ENBT IP address, the 1756-DHRIO slot number, and the SLC node address on Channel A.
  2. Add the MSG instruction to a rung and choose a message type suited to SLC data-table access; set the SLC file address, the destination tag, and the element count for the transfer you need.
  3. Set the path as the four pieces above, ending at the DHRIO slot.
  4. Change the communication method from CIP to DH+.
  5. Select Channel A and enter the SLC node address in the DH+ fields.
  6. Trigger one message from a test rung, read its completion and error status, and only then apply your controlled-change process and enable the production trigger, with logic that blocks a new request while one is still active.

How do I verify the DH+ message data before relying on it? #

Trigger one message, confirm it reaches completion rather than staying active or reporting an error, and compare a value you already know against the SLC data table before trusting the rest of the transfer.

Check the whole transfer, not the first element: with the example above, N7:29 must match its source as surely as N7:20 does. Test writes only against data-table areas reserved for testing, never against addresses a running machine uses for outputs or interlocks. Do not read an unchanged receive buffer as proof of live communications: a failed message leaves the previous contents in place, so track message success and data age in your logic and act on the message status, not on the buffer alone.

Questions asked

Does the CompactLogix have to stay in dual-IP mode for this message to work?

No. Dual-IP mode only decides how the two embedded Ethernet ports are addressed: in dual-IP, ports A1 and A2 each carry a unique IP address, while the linear/DLR setting has both ports share one address. The message works from either mode as long as the interface in use has a route to the subnet holding the 1756-ENBT.

Should the DHRIO be added to the CompactLogix I/O tree?

It is optional. An I/O tree entry lets you browse to the module when you build the message path, which reduces typing errors, but the message itself also works from a typed path with no tree entry. The entry never substitutes for the DH+ communication method, Channel A, or the node address.

Why do the SLC integer values land wrong even when the read completes?

SLC integer files hold 16-bit values, so point the destination at a 16-bit integer array sized to the element count you requested. A wider destination type no longer matches the SLC element size, so values can land shifted or merged. Verify the last element as well as the first before trusting the transfer.

What should I record when the DH+ message still fails?

Record the message's error code and extended status exactly as shown, plus the four values that decide the transaction: the ENBT IP address, the DHRIO slot, the channel, and the SLC node address. Then confirm the node you browsed sits on the same DHRIO channel the message uses.

Keep reading

  • How-to

    Reach a CompactLogix through a ControlNet bridge in RSLinx

    When autobrowse through a 1784-U2CN ControlNet path lists the bridge's EtherNet/IP module but no CompactLogix or third-party EtherNet/IP devices, add the target IP address manually under that module's Ethernet port in RSWho or the FactoryTalk Linx browse tree, then select the resulting device as the online path in the Logix programming software. The devices are reachable; only discovery fails, and a manual entry needs no discovery.

    Industrial networks

  • Troubleshooting

    Why CODESYS EtherCAT master xError stays false on cable pull

    `EtherCAT_Master.xError` stays FALSE because the master does not latch slave loss into the application variables when restart handling is off; the engineering tool reads device state directly, so it still shows the error. Tick `Automatically restart slaves` on the master and `Enable Diagnosis for Devices` for the extended instance, then pull-test: the loss reaches the program and the slave rejoins when the cable returns.

    Industrial networks

  • Troubleshooting

    Start and stop a PowerFlex 700 over EtherNet/IP from CompactLogix

    Yes — set PowerFlex700:O.DriveLogicRslt_Start and PowerFlex700:O.DriveLogicRslt_Stop in the controller output image; those :O members are the network start and stop commands. Parameter 271 [Drive Logic Rslt] inside the drive is a read-only diagnostic of the combined command, so writing it fails. Keep the hardwired drive enable as the safety path and set the comm-loss action to fault, then prove both by test.

    Drives and motion