Selection guide
Migrating a MicroLogix 1500 machine to a current PLC
Short answer
Quote CompactLogix as the baseline for the rebuild: Rockwell's migration reference gives the MicroLogix 1500 two documented destinations, MicroLogix 1400 or CompactLogix 5370 (L1/L2), and a low-volume machine rebuild does not justify the Micro850 route. Take the Micro850 only for high build volume, after the 11 uncovered inputs, serial Modbus, the drive interface and a trial CCW import are verified.
On this page
Quote the rebuild around a CompactLogix controller. Rockwell's MicroLogix migration reference, publication 2080-RM002, names two documented destinations for a MicroLogix 1500: a MicroLogix 1400 or a CompactLogix 5370 (L1/L2) controller. A repeat machine build carrying roughly 59 digital inputs, 27 digital outputs, EtherNet/IP and a PowerFlex drive connection sits on the CompactLogix line, because engineering time dominates a low-volume build and the Studio 5000 platform carries the machine through its next service life. The Micro850 2080-L50E-24QBB with 2085 expansion modules is a lower-hardware-cost alternative on a different programming platform, so it enters the quote only for high build volume, and only after four checks pass: the 11 inputs its expansion bank leaves uncovered, the serial Modbus traffic, the drive interface, and a trial CCW import.
Read the old machine before quoting the new controller #
Nothing here is broken, so there is no processor fault to chase: the 1764-LRP MicroLogix 1500 family is discontinued, and the quote exists because a current build cannot use it. Extract the machine requirements from the installed design, then separate requirements that must survive from hardware choices that are open.
Build a point list from the electrical drawings and the RSLogix 500 project before any controller is specified. For every field device, record the signal function, the existing address, the voltage and the common group, and mark which spare terminals are real spares and which addresses are simply unused.
Record every device on the controller's ports as well: the HMI, any peer controllers, serial instruments, and the drive with its nameplate model and installed communication card. A drive link may carry only a speed reference and a run bit, or it may also carry status, faults and diagnostic data, and that difference sets the programming scope and the acceptance test.
The documented migration lines #
Publication 2080-RM002 puts the MicroLogix 1500 on two migration lines: MicroLogix 1400 for like-for-like continuity, or CompactLogix 5370 (L1/L2) for the current Logix platform. The Micro850 is on neither line, and a shared "Micro" prefix changes nothing: the Micro800 family programs in Connected Components Workbench (CCW), an environment unrelated to RSLogix 500.
Publication MIGRAT-PP015 describes the MicroLogix migration wizard in Integrated Architecture Builder (IAB), which steps through the system configuration and component selection for a CompactLogix destination. It is the documented starting point for sizing the replacement hardware.
Hardware reuse is its own documented fact. Publication 1769-TD006 covers 1769 Compact I/O as usable with MicroLogix 1500 or CompactLogix controllers, so a 1769-based CompactLogix can carry the existing expansion bank, subject to the exact module list and the new controller's configuration limits. A current 5069-class controller such as the 5069-L306 brings its own 5069 I/O family instead, which suits a fully new I/O design rather than a hand-me-down rack.
The MicroLogix 1400 line, for example a 1766-L32BXB, stays closest to RSLogix 500 practice, but its expansion family is 1762 rather than the 1500's 1769, so the bank rewires; check its lifecycle status and the customer's acceptance before quoting it.
Reconcile the input and output arithmetic #
The proposal — one 2085-IQ32T, one 2085-IB16 and two 2085-OB16 modules on a 2080-L50E-24QBB — needs arithmetic before it becomes a bill of materials.
Inputs first. The expansion bank carries 32 + 16 = 48 input channels against a requirement of roughly 59, which leaves 59 − 48 = 11 inputs to be supplied by the controller's embedded I/O. The decision follows directly: the Micro850 quote stands only if the 2080-L50E-24QBB specification shows at least 11 embedded inputs free after any high-speed or special-function assignments. If fewer remain free, the fix is hardware, not optimism — a second 2085-IQ32T raises expansion inputs to 80 and covers the full list with margin, at the cost of another expansion position, a revised power budget and cabinet space.
Outputs second. The two 2085-OB16 modules give 2 × 16 = 32 expansion outputs against roughly 27 required, leaving 32 − 27 = 5 spare channels. The count fits; the electrical fit does not come from the count. Match each output to its load — switching type, per-point and common current, voltage, isolation — and check whether any group needs relay rather than transistor outputs.
Close the assembly details: the 2085 expansion bank terminates with a 2085-ECR end cap, and the module arrangement has to satisfy the family's expansion limits and power budget.
- Usable inputs = embedded inputs + expansion inputs − channels claimed by counters, encoders or other special functions.
- Each output checked against its device: interposing relay, solenoid or indicator.
- Spares agreed after the point list closes, not added as a generic allowance to an approximate count.
What converts, and what gets rewritten #
Three programming environments are in play: RSLogix 500 for the MicroLogix 1500, CCW for the Micro850, and Studio 5000 Logix Designer for CompactLogix. Neither destination is a drop-in replacement.
CCW version 11 and later imports a MicroLogix program, with one preparation step: export the program from RSLogix 500 as a .SLC library file, then run the import. Run that trial conversion before you estimate the job and inspect the resulting project — the import's completeness on your actual program, not on paper, sets the rewrite allowance. Comment and symbol data move separately: export the tags from the CCW project, and export the RSLogix 500 database with Save As and the Export Database option.
CCW Standard also documents logic transfer between RSLogix 500 or Studio 5000 projects and a CCW project. That helps a Micro850 conversion; a CompactLogix destination is still budgeted as a rewrite in Studio 5000.
A converted project that compiles proves syntax, not behavior. Startup conditions, sequence transitions, timers, counters, retained values and fault recovery each need a live machine test, and the hardwired emergency-stop and safety circuits — which the conversion does not touch — must be proven to interrupt power with the controller out of the loop before the first production run.
The runtime links do not carry the program: Modbus RTU and EtherNet/IP move process data, not the project file — Why Modbus cannot transfer a PLC ladder program over TCP covers that distinction.
Serial Modbus and the PowerFlex interface #
Two interfaces decide real quote lines.
Serial Modbus first. Read the old RSLogix 500 project's communication setup and establish whether the 1500 exchanges Modbus RTU over its serial port; an Ethernet-only replacement plan silently drops that interface. The Micro800 family carries Modbus communications built in, so those exchanges re-host on the Micro850 directly. A CompactLogix build covers serial Modbus by adding a serial communication module or a Modbus gateway and rewriting the exchanges on the Logix side — real engineering time, and a real argument in the platform decision when the machine talks to serial instruments.
The drive second. The nameplate model and the installed communication card define the integration, not the PowerFlex family name. Over EtherNet/IP, explicit messaging exchanges data on request, while Class 1 connections exchange cyclic process data over configured connections; the controller's supported role and services must match the drive's interface card, and the acceptance test must show the data the machine actually needs — at minimum a speed reference and a run command, plus status and faults if the point list says so. Micro850 and Micro870 firmware version 21 reportedly improved EtherNet/IP Class 1 connection capability and configuration ease; verify that against the release notes for the exact firmware revision you will ship, rather than judging the platform by its older behavior. The start and stop mechanics on the CompactLogix path are the same ones used to start and stop a PowerFlex 700 over EtherNet/IP from CompactLogix.
The decision, case by case #
If this rebuild is one cell inside a wider plant revamp, make the controller choice part of the whole-platform picture — SCADA and PLC platform selection for plant revamps covers that larger decision — and decide the cell against it.
| Build case | Controller choice | Why | Close these first |
|---|---|---|---|
| Repeat build, low volume, Studio 5000 already in the toolbox | CompactLogix: 5370 (L1/L2) on the documented line, or 5069 with new I/O | Best-supported EtherNet/IP platform; no CCW conversion workload; engineering time dominates a one-off | Point list closed; 1769 reuse only on a 1769-based controller with the module list verified |
| High build volume, bill of materials dominates | Micro850 2080-L50E-24QBB with 2085 expansion | Lowest hardware cost per machine built; built-in Modbus; CCW import shortens the conversion | 11 uncovered inputs verified free or a second 2085-IQ32T added; drive card matched; firmware version 21 Class 1 behavior verified; trial CCW import inspected |
| One-off rebuild, shortest engineering path | MicroLogix 1400 | RSLogix 500 continuity with the least rework | 1762 expansion rewiring accepted; lifecycle status and customer acceptance confirmed |
For the quote as described — one machine, with build volume beyond it still unknown — quote CompactLogix and do not spend the customer's engineering budget proving out the Micro850 path. If a follow-on order makes hardware cost the argument, re-quote the Micro850 with the four checks closed and documented in the project file.
Questions asked
Can the existing 1769 expansion I/O move to a CompactLogix controller?
Yes, on a 1769-based CompactLogix: 1769 Compact I/O is documented for both MicroLogix 1500 and CompactLogix controllers, so the bank can stay in the panel. Verify each installed module against the new controller's configuration limits, recheck the bank's power budget, and confirm the end cap and termination hardware against the new assembly's rules before the first power-up.
Does the CCW import convert the whole RSLogix 500 program automatically?
No, not entirely. CCW version 11 and later imports a MicroLogix program after you export it from RSLogix 500 as a .SLC library file, and comments move through a separate tag and database export. The import resolves syntax, not machine behavior: startup conditions, sequence transitions, timers, counters, retained values and fault recovery still need a rung-by-rung review and a live machine test.
Why does MicroLogix 1400 keep coming up as a replacement?
It is the closest RSLogix 500 platform to the 1500 and one of the two destinations in the documented migration line, so addressing style, instruction set and programming habits carry over with the least rework. Its expansion family is 1762 rather than 1769, so the I/O bank rewires, and its lifecycle status and the customer's acceptance need confirming before you commit a new build to it.
With 5 spare expansion outputs, is the output side finished?
No. Channel count is only the first check. Verify each spare output against its device — interposing relay, solenoid or indicator — so switching type, per-point and common current, voltage, isolation and relay-versus-transistor needs are all confirmed. The 5-channel margin disappears quickly if the load list forces a different module mix, so close the output point list before freezing the bill of materials.