The PLC that has been running your conveyor, pump station, or process unit without incident for fifteen years is a liability you can no longer see. The vendor has stopped selling spare parts. The programming software doesn’t run on Windows 11. The person who wrote the logic retired three years ago and nobody has the source code. You are one CPU failure away from a recovery process that takes days, not hours.
Legacy PLC migration is one of the most common projects in industrial automation, and one of the most frequently underestimated. This article covers what a planned migration from legacy platforms to Rockwell ControlLogix actually involves, and how to plan it without losing production.
Why ControlLogix
ControlLogix is not the only migration target, but it is the most common in Queensland industrial operations for several reasons. It is widely used across mining, sugar, ports, and utilities. The local support network of spare parts, software licences, and engineering knowledge is well established. Studio 5000 Logix Designer is a mature, well-documented development environment. And for sites already running other Rockwell equipment, adding ControlLogix maintains a consistent vendor ecosystem for commissioning and maintenance.
For sites currently running Schneider, Siemens, or other platforms where a Rockwell migration doesn’t fit the existing ecosystem, the planning principles below apply equally, with the target platform substituted.
Phase 1: Get the program off the old hardware
The first task in any legacy PLC migration is extracting the existing program from the installed hardware. This sounds simple. It is frequently not.
Common complications:
- The program is password-protected and the password was not retained. The only option may be a physical read of the CPU memory, which some legacy platforms support via the programming port without a password.
- The programming software is no longer available or will not run on a modern operating system. A virtual machine running a compatible legacy Windows version (Windows XP, Windows 7) is often required.
- The installed program version does not match what is in the project files on the engineering PC. The PLC was modified in-situ without updating the master copy, which is more common than most sites expect.
A virtual machine environment with the appropriate legacy programming software is the standard approach for extraction. For Rockwell RSLogix 500 (SLC), RSLogix 5 (PLC-5), GE Proficy Machine Edition (RX3i), and Omron CX Programmer, virtual machine installations running compatible Windows versions provide a stable working environment.
Never assume the program in the running PLC matches the project files on the engineering PC. Always upload from the PLC first. Confirm the comparison before beginning migration work.
Phase 2: Logic translation
Translating logic from a legacy PLC to ControlLogix is not a mechanical find-and-replace. Legacy platforms use instruction sets, data types, and memory structures that do not have direct equivalents in Studio 5000. Each instruction must be understood and replicated in intent, not just syntax.
The most common translation challenges:
- SLC 500 integer file addressing: SLC programs use file-based addressing (N7:0, B3/0, T4:0) that must be converted to ControlLogix tag-based addressing. This is a structural change, not a cosmetic one.
- Legacy timer and counter instructions: SLC timers accumulate in 10ms increments; ControlLogix in 1ms. Logic that checks timer accumulated values needs careful review.
- File instructions: SLC COP, FLL, and FAL instructions that operate on integer files need to be replicated using ControlLogix array operations.
- PTO/PWM instructions: motion control instructions on legacy platforms may not have direct ControlLogix equivalents and may require restructuring.
The translation work is done offline. The new ControlLogix program should be simulated using RSLogix Emulate or SoftLogix before the hardware is available, verifying that the translated logic behaves identically to the original under the same input conditions.
Phase 3: Pre-build and test
The ControlLogix hardware (chassis, CPU, I/O modules, communications modules) should be fully assembled and pre-configured in the workshop, not on site. Power the rack, download the translated program, and verify that the hardware operates correctly before anything is taken to site.
For a migration that involves rewiring I/O, replacing individual I/O cards with different form-factor ControlLogix I/O, the wiring terminations should be pre-labelled and tested in the workshop where possible. Every minute of rewiring time that is moved from the shutdown window to the workshop is risk taken out of the cutover.
Phase 4: The shutdown cutover
The shutdown window is used for three things: physical hardware swap, field I/O verification, and handover. Everything else should be completed before the window opens.
A tightly planned cutover sequence:
- Remove legacy PLC hardware from the panel or rack
- Install ControlLogix hardware
- Connect wiring: field I/O, communications, power
- Power on and verify communications
- Download program and verify all I/O in program mode: force outputs one at a time and verify field response, check all inputs with field signals
- Run in program mode with operators present: walk through the operational sequences before switching to run
- Switch to run mode: monitor closely for the first operational cycle
- Document as-built state: all changes made during the cutover
Planning the documentation
A legacy PLC migration should produce a documentation package that future maintainers can use. At minimum: the translated ControlLogix project (.ACD file), an I/O list comparing old and new addressing, a wiring schedule if any rewiring was done, and a brief description of any logic that was restructured during translation. If the original program had no comments, add them during the translation. The migration is the opportunity.
About the author
Dennis Murphy RPEQ has delivered legacy PLC migrations across multiple platforms, including SLC 500 to ControlLogix, GE/Emerson RX3i to current Proficy ME, and Omron CPM1A to Schneider M251, across mining, sugar, and manufacturing operations in Queensland. Contact: [email protected]