Import an L5X project
Bring an existing Studio 5000 project into PLCcode. About a minute.
Bring an existing Studio 5000 project into PLCcode. Takes about a minute — and on a self-hosted plan, your file never needs to leave your network.
1. Export from Studio 5000
In Studio 5000 Logix Designer, export your project as an .L5X file:
File → Save As → L5X. Export the full project, not a partial routine — PLCcode uses the
tag database and UDT definitions to understand your logic.
ACD files: PLCcode reads L5X, not ACD. ACD is a binary format only Studio 5000 can open — the L5X export is lossless for logic, tags, and comments.
2. Upload to PLCcode
- Open your workspace and hit New project → Import L5X.
- Drop the file in. Parsing starts immediately — rungs, routines, tags, UDTs, and AOIs are indexed.
- Large projects (10k+ rungs) take a couple of minutes. You can watch the routine count climb.
// What PLCcode indexes from your L5X
Programs → routines, rungs, comments
Tags → controller + program scope, aliases
UDTs / AOIs → definitions and every usage
✓ Ready → ask PLCchat anything about it3. Verify the import
Open the project and spot-check a routine you know well. Rung comments, tag descriptions,
and AOI parameters should all be there. A quick way to confirm: ask PLCchat
what does R031_Conveyor do? — the answer cites the exact rungs it read.
Import a copy of the running program, not an old backup. PLCchat's answers are only as current as the file you gave it.
Importing doesn't connect to your PLC. Nothing touches the controller — this reads a file. Going online with hardware is a separate, deliberate step via PLCconnect.
What's next
Your project is versioned in GitPLC from the moment it lands — every change from here is tracked and reversible. Made it worse? Put it back, in one click.