How to export a PLCopenXML file

The tool accepts a PLCopenXML export. Below is how to get one in popular IDEs. The export path depends on the IDE, not the controller brand.

Three steps to export PLCopenXML from CODESYS: Project menu, select all objects, OK

CODESYS 3.5 (Russian UI): Project → Export PLCopenXML → Select → All → OK. Three steps, half a minute.

CODESYS 3.5 and OEM IDEs built on its engine

Menu Project → Export PLCopenXML… → select the whole tree (Device, all POUs, GVL) → Export.

Many vendor IDEs are a rebranded CODESYS with the same export: WAGO e!COCKPIT, ABB Automation Builder, Schneider EcoStruxure Machine Expert (SoMachine), Eaton XSOFT-CODESYS, Bosch Rexroth IndraWorks/ctrlX, Festo Automation Suite, Lenze PLC Designer, ifm, Berghof, Weintek, Raspberry Pi, etc. (500+ manufacturers use CODESYS).

TwinCAT 3 (Beckhoff)

Right-click the PLC project node → Export PLCopenXML….

Built on the CODESYS 3.5 engine — the format is compatible (verified). Hardware configuration is stored separately, so you'll get code analysis without the device tree.

TwinCAT 2 (Beckhoff)

PLC Control: Project → Export project to PLCopen XML….

Based on CoDeSys 2.3 (older) — the PLCopenXML format may differ from v3; compatibility not yet verified, send a file and we'll check.

Tip. To get device analysis (controller, modules, I/O mappings, watchdog) — include the Device node in the export. POU/GVL only → code analysis alone. The format is standard PLCopen TC6, so any other IEC 61131-3 IDE works too.

Didn't find your IDE? Write to us — we'll add instructions. The list grows as new IDEs appear.

← back to file check

Processing happens in memory — the uploaded code is not stored. The tool advises; code changes are up to the engineer (see what the linter can't see). What happens to your code → · Your code & privacy · Industry benchmark · Feedback · GitHub