Move an Allen-Bradley program to another PLC — free.

Free tool · runs in your browser · Studio 5000 .L5X to PLCopen XML

Drop a Studio 5000 export (.L5X). You get the same program as PLCopen XML, the open IEC 61131-10 format, made for OpenPLC Editor and CODESYS-based tools, and a list of everything that needs a person. The file never leaves your computer.

No e-mail, no sign-up · converted on your computer (WebAssembly), never uploaded · the exporter is LK On's own code

Convert your program

Drop the export
Drop the .L5X export here — or click to choose Studio 5000 Logix Designer → File → Save As → “Logix Designer XML File (*.L5X)”

No export at hand? Convert a sample program to see what you get.

Next: unzip it. The folder is laid out for OpenPLC Editor, and plc.xml is the file for CODESYS-based tools. REPORT.txt inside lists what needs a person, routine by routine. To read the rungs, drop the same file into the L5X ladder viewer.

What you get

  • Ladder stays ladder. Every rung becomes a ladder network, structured text stays text, function block and SFC charts stay graphical.
  • Logix habits come along. Timers with .PRE, .ACC and .DN, one-shots, shift registers and FIFOs come as a small open library of function blocks, inside the file.
  • An honest list. Motion, messages, safety and module status are listed by routine and rung, never faked.

What is in the ZIP

One folder, named after your file:

plc.xmlThe program as a PLCopen XML project (TC6 XML 2.01, IEC 61131-10): the data types, every tag as a variable, the I/O at located addresses, every routine, Add-On Instruction, program and task, and a short self-test program to run once on the new PLC.
beremiz.xmlA small project file, so the folder is laid out the way OpenPLC Editor expects a project.
REPORT.txtPlain words: how much translated, what needs a person and where (routine and rung), what became of each task.
report.jsonThe same report, for scripts.

How

  1. Drop the .L5X.
  2. Download the ZIP.
  3. Unzip and open the folder in OpenPLC Editor, or import plc.xml in CODESYS.

The ZIP is made for those two, but we have not yet opened it on OpenPLC Editor and CODESYS installs: that check is still being done.

A starting point, not a finished machine program. Test it on the bench before it touches a machine. Safety logic is never converted.

In progress, release soon: LK On will keep this file with the machine and make the same export on the device, from the program it keeps.

Questions

FAQ
Is my program uploaded?

No. The conversion runs entirely in your browser (WebAssembly): the .L5X is read on your computer and the ZIP is made there. You can watch the browser's network inspector while it runs, or convert the sample once (that loads the engine), disconnect from the network and then drop your file.

Which controllers?

Any Studio 5000 export: CompactLogix and ControlLogix, a whole project or one program. An .ACD project has to be saved as .L5X first: File → Save As → “Logix Designer XML File (*.L5X)”.

Will it open in OpenPLC Editor or CODESYS?

It is built to. The folder is laid out for OpenPLC Editor (the beremiz.xml file makes it a project) and plc.xml is PLCopen TC6 XML for CODESYS-based tools. We have not yet opened it on those installs; that check is still being done, so open it on the bench first and send us what you see.

What needs a person?

Motion, messages (MSG), safety instructions, module status and settings the library does not carry, and calls of source-protected Add-On Instructions. They stay in the program as blocks with their Logix interface that report an error until someone connects them to the new PLC's own functions; REPORT.txt lists each one with its routine and rung.

Siemens?

Not yet. The converter reads Allen-Bradley Studio 5000 exports, and we know of no PLCopen ladder import in TIA Portal.

Price?

Free. No e-mail, no sign-up.

Moving a machine to another PLC?

An engineer answers

Tell us the controller, the new PLC and what worries you. We answer with concrete steps, or an honest «not yet».