Docs / Rockwell Studio 5000

Rockwell Studio 5000 audit guide

L5X XML export. Verified against ControlLogix / CompactLogix corpus v20 through v36.

Supported formats

Logix Designer XML export

stable

.L5X

v20-v36 verified. Partial exports (Module-only, DataType-only) also parse.

Rockwell Studio 5000-specific rules

These rules are vendor-gated and only fire on Rockwell Studio 5000 sources. Vendor-neutral rules (R001–R007, R014, R022, etc.) also apply.

R008

Controller revision missing

R010

Latch without unlatch

R012

Scan time excessive

R013

E-stop redundancy missing

R037

Multiple writers (split driver)

R040

OTL latches a physical input

R041

OTU unlatches a physical input

R044

OTL + OTU on same rung

R054

Routine-program name collision

R066

NOP-only rung (placeholder)

R067

Long rung text

R068

Magic-number comparison

R069

Rockwell system tag (S:XX) access

R070

Indirect array index

R093

Routine without description

Known limitations

AOI bodies parse for tag declaration tracking but routine-level reference graph is incomplete on some legacy AOIs.

ScheduledPrograms task scheduling read for R012; non-periodic tasks reported as 'continuous'.

GSV / SSV (Get/Set System Value) instructions partially recognised; not all system attributes are in the BUILTIN allowlist.

Workflow

1. Export your project from Studio 5000 via File → Save As → L5X.

2. Upload the .L5X through the audit form.

3. Findings group by severity (error / warn / info) and severity-class (safety / structural / etc.).

4. Each finding carries a Gemini-augmented explanation if a BYOK key is configured.