PLC-5 on DH+ still running a line — ENET-to-DH+ or bite the ControlLogix bullet?

TS ControlsThe answer

A gateway is a bridge, not a strategy. It is still a good bridge if you know what it buys you and when it ends. Before you decide, separate three questions that usually get lumped together: the network, the processor, and the HMI.

You may already have Ethernet. The E in PLC-5/40E means the processor has a built-in Ethernet port, so if management’s goal is getting data off this line over Ethernet, you may not need a gateway at all. Check the port, the processor series and revision, and whether anything else on DH+ (the PanelView, other nodes, a SCADA driver) still needs the DH+ link. The other common bridge is a 1756-DHRIO module in a ControlLogix chassis with an Ethernet module beside it. That chassis routes messages between DH+ and EtherNet/IP, and it often becomes the first piece of the migration anyway.

A bridge fixes connectivity. It does nothing for the bigger risk on a PLC-5 line, which is spare parts. Rockwell discontinued the remaining PLC-5 processors in 2017, so what is on your shelf, or on the used market, is the supply. Before you commit to two more years, take an inventory: the processor, the power supply, every 1771 I/O module type in the racks, the Remote I/O adapters, and the PanelView. Any part you have no spare for sets your timeline, not the network.

Treat the HMI as its own decision. If it is a PanelView Standard terminal, that family is discontinued, and a failed unit cannot be replaced like for like. If the HMI is tired, that is the strongest reason to plan the cutover now instead of in pieces. Moving to a PanelView Plus with FactoryTalk View ME means converting the application, so plan for screens to be reworked, not just imported.

If you go to ControlLogix or CompactLogix, convert the program first and expect to finish it by hand. Rockwell’s migration tool turns an RSLogix 5 program into a file Studio 5000 Logix Designer can import, but conversion is the start, not the finish. These are the places that need manual work.

Addressing: data files such as N7 and B3 become arrays of converted tags. Decide early whether you keep the converted names, which is fast but hard to read, or build clean UDTs for the HMI interface, which takes longer and is much easier to maintain.

Block transfers: BTR and BTW instructions to 1771 analog and specialty modules become block-transfer MSG instructions if the 1771 I/O stays on Remote I/O, or module-defined tags if the I/O moves to 1756 modules.

Indirect addressing and file instructions: COP, FAL, and indirect addresses such as N[N7:0]:5 need checking line by line, because Logix data types and indexing do not always behave the way the PLC-5 did.

Timers: PLC-5 timers count in 0.01 s or 1.0 s time bases, and Logix timers count in milliseconds. Check every preset after conversion, especially presets that logic writes with a MOV.

Messages: every MSG to another DH+ node needs a new path.

Then pick an I/O strategy. There are three realistic options. The first is to keep the 1771 I/O on Remote I/O for now and scan it from the new controller through a supported RIO scanner module. It is fast, but you are still running 1771 hardware. The second is a 1771-to-1756 wiring conversion system, which moves the field wiring to new I/O without re-terminating it wire by wire. That means fewer wiring errors and a shorter outage. The third is to rewire to new I/O, which gives the cleanest result and the longest outage.

Plan one weekend for the processor and the HMI together, not half a migration. Running half the line on DH+ and half on Ethernet means debugging two systems at once during the outage. Before that weekend, get a verified backup of the running PLC-5 program by uploading it from the processor, not by trusting the file on the engineering laptop. Build a documented I/O list that maps each old address to its new tag. Test the converted program offline and simulate where you can. Write the fallback plan down: the PLC-5 stays mounted and wired until the new system has run production.

The short version: if the process is stable, spares exist, and the HMI is healthy, the built-in Ethernet port or a DHRIO bridge can buy you time to plan properly. If any of those three is shaky, plan the ControlLogix cutover now, while you still get to choose the weekend.

Need hands on it? Send the project file, the symptom, and your outage window to sales@ts-controls.com or through the RFQ form, or call the office at (877) 524-6674, Monday–Friday, 9:00am–5:00pm Eastern. Line down right now? Call (877) 790-4697, 24/7, subject to personnel availability.