PLC Code Checker
Check PLC code and ensure quality
With the PLC Code Checker, you can automatically analyse Structured Text (ST) and PLCopen XML projects. Syntax errors, quality issues and potential risks in PLC programs are detected and presented clearly.
The tool supports developers, programmers and automation engineers in checking PLC code before commissioning, release or maintenance.
What is the PLC Code Checker used for?
Errors in PLC programs can lead to unexpected plant behaviour, downtime or increased commissioning effort. The PLC Code Checker helps detect issues early.
Typical use cases:
- Checking Structured Text programs
- Code reviews and quality assurance
- Validation of PLCopen XML projects
- Preparation for commissioning
- Maintenance and modernisation of existing PLC applications
- Education and training
Supported formats
- Structured Text (ST)
- IEC 61131-3 source code
- PLCopen XML (IEC 61131-10)
- Project and export files from different PLC systems
What is checked?
- Syntax and compiler errors
- unreachable branches
- dead code and unused logic
- cyclic dependencies
- recursive calls
- Project structure and call hierarchies
- Inconsistencies in PLCopen XML files
How does the check work?
- Upload ST or PLCopen XML file
- Start analysis
- Review results and notes
- Fix detected errors
- Download check report
The analysis runs automatically and provides a structured overview of detected issues and improvement potential.
Which results are output?
- Error list
- Warnings and notes
- Call hierarchies
- Cyclic dependency checks
- Notes on unused program parts
- Project quality rating
- JSON report for documentation and archiving
Benefits of the PLC Code Checker
- early error detection
- higher code quality
- support for code reviews
- lower commissioning risk
- consistent quality control for PLC projects
Technical notes
The syntax check is based on IEC 61131-3 compliant analysis methods. In addition, project structures and call relationships are analysed to detect potential quality issues early.
Depending on project scope, the analysis can automatically evaluate multiple program areas and dependencies.