Troubleshooting
Reaching PLC-5 and SLC 500 data through a ControlLogix DH+ bridge
Short answer
Yes. An OPC UA server reaches PLC-5 and SLC 500 processors through a ControlLogix Ethernet-to-DH+ bridge when its Allen-Bradley driver documents routed legacy access. Confirm the driver, inventory the bridge modules, build each connection path to the DH+ node, and prove one read — the 1756-DHRIO carries 32 connections per DH+ channel.
On this page
- Can an OPC UA server talk to PLC-5 and SLC 500 processors through a ControlLogix bridge?
- What do I check on the replacement driver first?
- Which modules in the ControlLogix chassis carry the DH+ traffic?
- What goes in the connection path to a DH+ node?
- How many connections can the DH+ channel carry?
- Why do PLC-5 and SLC 500 tags behave differently from ControlLogix tags?
- How do I prove one routed read before adding the rest?
- What changes on the network when both servers poll in parallel?
- Questions asked
Yes. An OPC UA server can read PLC-5 and SLC 500 processors through the same ControlLogix Ethernet-to-DH+ route a Wonderware ABTCP connection uses, provided the Allen-Bradley driver inside the server documents routed legacy access — that support, not OPC UA itself, decides the job. The bridge is a standard arrangement: an Ethernet module and a 1756-DHRIO in a ControlLogix chassis, legacy processors on DH+. Work the problem in this order: driver support, gateway inventory, connection path to each DH+ node, one proven read, then polling load — a 1756-DHRIO DH+ channel supports 32 connections.
Can an OPC UA server talk to PLC-5 and SLC 500 processors through a ControlLogix bridge? #
Yes, when the server's Allen-Bradley driver documents routed access to PLC-5 and SLC 500 processors; a working arrangement is a ControlLogix chassis with an Ethernet module and a 1756-DHRIO reaching the legacy processors on DH+, with up to 32 connections per channel.
Separate the two communication legs before configuring anything. The consuming application talks to the server over OPC UA; the server's device driver talks to the processors over EtherNet/IP into the chassis and out onto DH+. Selecting an OPC UA endpoint configures nothing on the controller side.
The installed ABTCP system is the baseline. Keep it running during commissioning: it proves the route, the node addresses and the item addresses are valid, so any difference in the new server points at the new server's driver or its configuration.
One distinction decides what the new server reads. If the working system addresses PLC-5 and SLC 500 data-table items directly, the new driver needs the same routed access. If it reads ControlLogix tags that the L73 populates with MSG instructions, that is routing a ControlLogix MSG to a PLC-5 over DH+ — a copy path, not a bridge path — and the new server can read those same controller tags instead. Inspect the existing device definitions before choosing.
What do I check on the replacement driver first? #
The driver's documented device list, before any network or controller change: a driver that supports ControlLogix over EtherNet/IP does not necessarily support the legacy families behind the bridge, and no address work closes that gap.
- Identify the exact OPC UA server product and the exact Allen-Bradley driver inside it, with versions.
- Read the driver's supported-device documentation for three separate line items: PLC-5 support, SLC 500 support, and access through a ControlLogix DH+ bridge. Generic EtherNet/IP support covers none of the three.
- Find the documented syntax for the routed path; drivers encode gateway, slot, channel and node differently.
- Change nothing on the network — no Ethernet hardware swaps, no DH+ node address changes, no logic edits — until support is confirmed.
Decision: a driver whose supported list stops at ControlLogix cannot reach the legacy processors through this bridge at any address. Choose the driver or server first, then troubleshoot. If you are still weighing server software, the options covered for connecting SLC 500 processors to Ignition SCADA show what a documented SLC 500 connection looks like on the client side. If the replacement server also needs its own machine, an industrial mini PC in the cabinet beside the gateway hosts the OPC UA endpoint off the general-purpose desktops.
Which modules in the ControlLogix chassis carry the DH+ traffic? #
The Ethernet module and the DH+ interface module in the gateway chassis carry it — the L73 processor stays out of the route unless the existing application reads values it copies into its own tags.
A ControlLogix processor in the chassis says nothing about the bridge by itself. A commonly deployed arrangement for SLC 500 processors on DH+ is a 1756-ENBT/A Ethernet module with a 1756-DHRIO/C in the same chassis; treat that as the architecture to confirm, not as what is necessarily installed. Record:
- The gateway Ethernet module's IP address and chassis slot.
- The DH+ interface module's model, slot and the channel the network is wired to.
- Each target processor's model and DH+ node address.
- The working system's device definitions for the same targets.
Resolve any mismatch against the working configuration before creating the new device.
What goes in the connection path to a DH+ node? #
Four elements: the gateway's Ethernet address, the chassis route to the DH+ module's slot, the DH+ channel the network is wired to, and the destination node address of the target processor.
The device's Connection Path setting must describe the whole route to the legacy target, not just the chassis's Ethernet address. Build it from the four recorded elements in the selected driver's documented syntax — a path string copied from another product encodes the same elements differently and fails. The inventory half of this work, seen from a PC driver, is the same as reaching a PLC-5/30 DH+ network from a PC HMI driver.
| Symptom | Check first |
|---|---|
| New server cannot reach the gateway's Ethernet address | Destination address, network path and service access, against the working server |
| Gateway reachable, every DH+ target fails | Driver bridging support, then the DH+ module slot and channel in the path |
| One processor fails while the others answer | That processor's node address and status, not the shared route |
| Device connects, specific items fail | Those items' addresses, data types and access settings |
| Values good in the server, bad in the client | Endpoint, certificate trust, session and item mapping on the OPC UA side |
If every target fails through one bridge, the fault is in the shared route — stop checking processor programs. If one target fails while the others answer, leave the shared path alone and work that node.
How many connections can the DH+ channel carry? #
Thirty-two connections per DH+ channel on a 1756-DHRIO or 1756-DHRIOXT, and at most 5 of those 32 may be CIP connections, per the module user manual (publication 1756-UM514) — that is the ceiling to plan polling against.
Illustrative example, not a measured result. Assumptions: 9 legacy processors on one channel, one connection per polled processor per server.
- Old server alone: 9 × 1 = 9 connections; 32 − 9 = 23 spare.
- Old and new servers polling in parallel: 9 × 2 = 18; 32 − 18 = 14 spare. Commissioning fits.
- A maintenance laptop added, polling all 9: 18 + 9 = 27; 5 spare. Still fits.
- A fourth full-poll source: 27 + 9 = 36 > 32. It does not fit.
Decision: on a nine-processor channel, run at most three concurrent full-poll sources, and retire the old server's device definitions before connecting a fourth. If the driver opens two connections per device, the arithmetic halves the answer — two full sources need 9 × 2 × 2 = 36 > 32, so even two do not fit — so confirm per-device consumption in the module's connection diagnostics before planning parallel running. Because the manual caps CIP connections at 5, count how many active connections are CIP before adding a third source; that sub-ceiling binds first if the driver's links register as CIP.
Why do PLC-5 and SLC 500 tags behave differently from ControlLogix tags? #
PLC-5 and SLC 500 controllers use data-table files addressed by file number, data type and element, not named controller tags, so a valid route still needs the correct device family and its address syntax.
A connection that succeeds at the gateway does not make a ControlLogix tag reference valid for a processor behind it. Browse trees depend on what the driver exposes for file-based data tables, so an empty browse result is not proof the bridge failed: type one known address with its declared data type and test it explicitly before rebuilding the route.
How do I prove one routed read before adding the rest? #
Bring one known data-table item up on one processor with good quality and writes disabled, read the same item through the OPC UA client, and only then add targets and tags — never the reverse.
- Create one legacy device on the confirmed gateway and connection path.
- Add one known readable item with its existing address and declared data type, writes disabled.
- Read the value and quality inside the server. A device-side failure sends you back to the path and the processor's diagnostics; success continues.
- Compare the value with the working application or an authorized monitoring tool, allowing for different sample times on a changing value.
- Connect the OPC UA client and check endpoint, certificate trust, authentication and item mapping.
- Add the remaining processors one at a time, each by its DH+ node address, expanding the item list gradually while watching device errors and the old application's response behavior.
Keep writes disabled until reads are proven: a write routed to the wrong data-table element on a running processor commands real outputs. The sequence splits every fault at the protocol boundary — bad quality in the server is a route or processor problem; good server values with bad client values are an OPC UA problem.
What changes on the network when both servers poll in parallel? #
Poll traffic per processor doubles while the old and new servers run in parallel at the same rate, because DH+ is a shared network that carries every server's polls even when none of them writes.
Treat parallel running as a test condition, not a steady state: watch the existing application's response behavior throughout, expand item lists gradually instead of importing the full tag set at once, and disable the old server's device definitions at cutover so one poller per processor remains. Recheck the channel afterward — one server, nine processors, nine connections, 23 spare.
That is the whole decision. The driver's documented routed access to PLC-5 and SLC 500 makes the job possible; the four-element path to each node makes it work; the 32-connection channel and the 5-connection CIP sub-ceiling size it; one proven read, then the retirement of the old definitions, completes it.
Questions asked
Does the L73 processor have to copy the legacy values into its own tags first?
No. A driver with routed legacy access sends requests through the chassis to the DH+ module, which polls the target processor directly. To confirm which path your existing system uses, inspect its device definitions: direct PLC-5 and SLC 500 item addresses mean routed access, while ControlLogix tag names mean the values are copied by MSG instructions in the L73.
Can the old and new servers run in parallel during cutover?
Yes, and you should keep the old one as the comparison baseline. Before adding any polling source, read the DH+ module's active connection count from its diagnostics and subtract it from the 32-connection ceiling; if the driver's links register as CIP connections, the working ceiling is 5 instead, and a redundant server pair or a second client can reach it quickly.
Should the DH+ node addresses be changed during the migration?
No. Leave every node address, the DH+ wiring and the controller logic untouched; the new server targets the node addresses the working system already uses. Changing nodes mid-migration interrupts the existing application, forces every path to be rebuilt at once, and adds variables that make any read failure ambiguous.
Why does browsing return nothing for a legacy processor?
Because browse support depends entirely on what the selected driver exposes, and file-based data tables are not always listed. An empty browse tree is not evidence that the bridge has failed: type one known address with its declared data type and test it explicitly before touching the route.
Is the ControlLogix processor a bottleneck for the bridged reads?
No, not for routed traffic. The requests pass across the chassis backplane from the Ethernet module to the DH+ interface module; the processor only carries load if your logic simultaneously moves the same values with MSG instructions, so schedule large program downloads and heavy logic changes outside the cutover window.
What should I record on site before commissioning the new server?
The gateway Ethernet module's address and slot, the DH+ module's model, slot and wired channel, each target processor's model and DH+ node, the driver product and version, and the working system's device definitions. That record rebuilds any path quickly after a failure and is the baseline for deciding whether a new symptom is the route, the driver or the client.