MicroLogix 1400 spare is unobtanium — 5380 or 5069 without rewriting the world?

TS ControlsThe answer

First, a correction to the shorthand in the title. A 5380 and a 5069 are usually the same platform: CompactLogix 5380 controllers carry 5069-L3xx catalog numbers and use 5069 Compact 5000 I/O. The real choice is between three routes.

Route A is a CompactLogix 5380 in Studio 5000. It is the right choice if this skid should run another 15 years and you want it to look like the rest of a Logix plant. The MicroLogix data files (N7, B3, F8, T4) convert to tags. Map them once into a UDT so the logic stays readable and the HMI points at a clean structure.

The 5380 controllers have no built-in serial port, so the Modbus RTU link to the drives needs one of three things. One is a 5069 serial module; check the current Rockwell documentation for Modbus RTU master support on the module and the controller firmware you would buy. Another is a protocol gateway between EtherNet/IP and Modbus RTU, which is common and well understood. The third is moving the drives to EtherNet/IP if they take an option card, which is often the cleanest result if the drives are being touched anyway. Studio 5000 Logix Designer is licensed separately from RSLogix 500, so plan for the software as well as the hardware.

Route B is a Micro800 controller, such as a Micro850 or Micro870, in Connected Components Workbench. This is the closest small-controller replacement. Many models have an embedded serial port with Modbus RTU built in, so the drive link can stay as it is. The software is Connected Components Workbench, not RSLogix 500, so the program has to be re-entered or converted, and some instructions differ. It suits a self-contained pump skid that does not need to join a Logix architecture.

Route C is another used 1400. It buys time, not a fix. If you take it, buy from a source that tests units, load your verified program, and treat it as the bridge while route A or B is planned.

Keeping the same HMI pictures is a reasonable request from operations, and it depends more on the HMI tag mapping than on the PLC choice. If the HMI is a PanelView Plus running FactoryTalk View ME, keep the application and re-point its tags to the new controller. A clean UDT interface makes that a mapping exercise, not a redesign. If it is a PanelView Component or an older terminal, plan a conversion, and rebuild the screens to look the same instead of hunting for a converter that half works.

Do the swap in this order. Get the running program off the surviving 1400 with an online upload, and compare it to any file you have; on old skids they often differ. Document every Modbus RTU drive: node address, baud rate, parity, and register map, plus what the PLC reads and writes, including scaling. Convert and test offline, then bench-test the Modbus link against one spare drive or a simulator if you can. Cut over on a planned outage with the old controller kept as the fallback. After it runs, take a fresh backup and store it where the next person will find it.

Which to pick: if the plant is standardizing on Logix and Ethernet, go with a 5380 and fix the drive communication properly. If this is an island skid that just has to run and talk RTU, a Micro800 is the smaller jump.

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.