PLC-5 to ControlLogix Migration: Complete Guide

The Allen-Bradley PLC-5 was discontinued in 2017 after more than 450,000 installations worldwide. Spare parts are increasingly scarce and expensive. ControlLogix is the direct successor for large-scale applications. This guide covers the complete migration path.

Why Migrate Now#

• PLC-5 discontinued in 2017 — spare parts are secondary market only, prices rising annually
• DH+ network is obsolete — no new DH+ modules available, EtherNet/IP is the standard
• RSLogix 5 is end-of-life — limited compatibility with modern Windows versions
• No path to Industry 4.0 — PLC-5 cannot connect to MES, cloud, or OPC UA

Migration Overview#

Phase 1: Assessment#

Before touching any code or hardware:

Document what you have: Program size (number of files, rungs), I/O count (discrete + analog), communication networks (DH+, Remote I/O, Ethernet), HMI connections (PanelView, RSView).

Identify risks: Custom instructions or rarely-used functions that may not convert automatically. Indirect addressing (N7:[N10:0]) requires careful conversion. Message instructions (MSG) referencing DH+ addresses must be restructured for EtherNet/IP.

Phase 2: Software Conversion#

Rockwell provides conversion tools built into Studio 5000:

1. Export from RSLogix 5: Save the PLC-5 program as a .ACD export file
2. Import into Studio 5000: File → Import → Select the exported file
3. Select target controller: ControlLogix 1756-L7x or L8x series
4. I/O mapping: Choose "Keep I/O" (adds bridge module for legacy Remote I/O) or "Update All I/O" (migrate to 1756-series modules)
5. Review Program Conversion Errors (PCE): The tool flags instructions that could not be converted automatically

What converts automatically:

• Basic ladder logic (XIC, XIO, OTE, OTL, OTU, timers, counters, math, comparisons)
• Program structure (subroutines → programs/routines)
• Comments and descriptions

What requires manual work:

• Indirect addressing (N7:[N10:0] must become array-based tag access)
• Message instructions (MSG) — DH+ addresses replaced with CIP paths
• Block Transfer instructions (BTR/BTW) — replaced with MSG blocks for EtherNet/IP modules
• PID instructions — SLC/PLC-5 PID structure differs from ControlLogix PIDE
• I/O addressing — every I/O reference must be remapped

Phase 3: Hardware#

Phase 4: Network Migration (DH+ → EtherNet/IP)#

This is often the most complex part. DH+ is a token-passing network; EtherNet/IP is TCP/IP-based. They are fundamentally different.

Option A: Full migration — Replace all DH+ devices with EtherNet/IP equivalents. Preferred but requires updating every PLC, HMI, and drive on the network.

Option B: Bridge — Use a 1756-DHRIO module to connect the new ControlLogix to the existing DH+ network. Legacy devices remain unchanged. This is a transition strategy, not a permanent solution.

MSG instruction conversion: PLC-5 MSG instructions reference DH+ node addresses (e.g., station 5 on DH+ channel A). ControlLogix MSG instructions use CIP paths (e.g., 1,0,2,192.168.1.10,1,0). Every MSG instruction must be manually reconfigured.

Common Pitfalls#

1. Integer overflow: PLC-5 uses 16-bit integers. ControlLogix defaults to 32-bit DINT. Bit patterns and negative number behavior can change. Test arithmetic-heavy code carefully.

2. Scan time differences: ControlLogix may execute faster than PLC-5. If your program relies on scan-time timing (instead of timers), the behavior changes. Always use timers for time-dependent logic.

3. PanelView HMI migration: PanelView terminals connected via DH+ need reconfiguration for EtherNet/IP. PanelView Plus terminals may need a FactoryTalk View ME project update. PanelView 550/600 (legacy) cannot communicate via EtherNet/IP and must be replaced.

How PLCcheck Pro Helps#

PLCcheck Pro analyzes PLC-5 programs and generates:

• Complete documentation of all files and rungs
• I/O inventory for hardware specification
• Instruction usage report (flags potential conversion issues)
• MSG instruction inventory (identifies DH+ references that need conversion)

Upload PLC-5 code for analysis →

Frequently Asked Questions#

How long does a PLC-5 to ControlLogix migration take?

Small system (< 1000 rungs, 64 I/O): 2–4 weeks. Medium system (1000–5000 rungs, 256 I/O): 4–8 weeks. Large system (5000+ rungs, 500+ I/O, multiple networks): 8–16 weeks.

Can I keep my Remote I/O racks?

Yes, temporarily. The 1756-DHRIO module allows ControlLogix to scan existing Remote I/O racks. But Remote I/O hardware is itself obsolete — plan to replace it with EtherNet/IP I/O.

---

Maintained by PLCcheck.ai. Not affiliated with Rockwell Automation, Inc.