🔒 Your code never leaves your browser

Find PLC code issues before they find you

Upload your Allen-Bradley L5X file. Get instant analysis — VFD problems, logic errors, missing interlocks, and more. Free.

Analyze Your L5X File →
See what it finds in your code. No signup, no upload, no install.
FaultTrace — VacuumPC_Controller.L5X
2
Critical
14
Warnings
8
Info
6
Programs
847
Rungs
2,104
Tags
🔴 Duplicate OTE: Conv3_Fault
Tag "Conv3_Fault" has OTE in 2 locations (MainProgram/Conv3_Control R8, MainProgram/Safety_Interlocks R3). Last scanned wins — the earlier OTE is overwritten silently every scan.
→ Consolidate to one location, or use OTL/OTU if both rungs need to control this tag.
🟡 VFD fault reset with no one-shot: VSD_1150.Q_ResetFault
P0035_VacuumAPC/R0041_VFD Rung 13: ClearFaults runs every scan while conditions are true. The drive faults, resets, faults, resets — masking the real problem.
→ Add a ONS so the reset fires once per button press. Add a retry counter — 3 faults in 60 seconds, lock out and require maintenance.
🟡 Drive output with no safety check: VSD_3508:O.Start
P0060_HopperTanks/R0510_VSD Rung 84: The run command has no guard, E-stop, or safety interlock on this rung.
→ Add a safety interlock condition on this rung, or verify the permissive chain using the Trace tab.
+ 21 more findings...
33
real L5X files tested
12,000+
rungs analyzed
<3s
parse time
0
data uploaded

What you get

Drop an L5X, get answers

Code Analysis

Catches duplicate outputs, unconditional logic, latch/unlatch mismatches, unused tags, redundant rungs, and more.

🔌

VFD & Drive Safety

Finds run commands with no feedback, unhandled drive faults, reset loops without one-shots, missing guard interlocks.

🔍

Logic Tracing

Pick any output tag — see the full permissive chain, kill conditions, and single points of failure. Builds your troubleshooting checklist.

📊

Cross-Reference

Every tag, where it's read and written. Search by module name to see every rung that touches a drive or I/O point.

🏗️

AOI Deep Scan

Parses inside your Add-On Instructions — not just your main programs. Same analysis, same rules, everywhere.

📥

Export Report

Download findings as a text file. Attach to a work order, email to your team, or print and bring to the panel.

Your code stays yours

We collect anonymous usage stats to improve the tool. Here's what we never touch.

✅ What we collect
  • • File size and element counts
  • • Which rules fired (counts only)
  • • Parse and analysis times
  • • Processor type and firmware
  • • Country (via Cloudflare)
🚫 What we never capture
  • • Tag names or rung logic
  • • Program or routine names
  • • Your file contents — ever
  • • IP addresses
  • • Anything that identifies your project

FAQ

Does my file get uploaded anywhere?
No. Your L5X file is parsed entirely in your browser — nothing is uploaded, transmitted, or stored. You can disconnect from the internet before using it and it still works.
What files does it support?
Allen-Bradley L5X exports from Studio 5000 and RSLogix 5000 — ControlLogix and CompactLogix. Siemens TIA Portal support is coming soon.
Does it work on my phone?
Yes. Fully responsive — works on phone, tablet, and laptop. You can install it as an app from your browser. Useful at the panel.
Is there a paid version?
The code analyzer is completely free with no limits. We're building a premium tier with additional capabilities. Enter your email below to get notified when it launches.

See what it finds in your code

Drop your L5X — results in seconds.

Launch FaultTrace →

Get notified when new features launch: