other-platforms
Skill0 starsChanged 37 days agoMITView on GitHub
Platform knowledge for Beckhoff TwinCAT 3 (.TcPOU/.TcDUT/.TcGVL/.TcIO XML with CDATA, pragmas/attributes, FB_init, __NEW, PLC++), CODESYS V3.5 (SP22, PLCopenXML and .export, File-Based Storage, Static Analysis SA/NC rules, scriptengine), ABB Freelance (DCS: .prt block export, whole-project Unicode .csv, .plc/.ple, Bulk Data Manager) plus ABB Automation Builder (AC500) and 800xA Control Builder M, and Rockwell Studio 5000 Logix Designer (L5X/L5K, RLL neutral text XIC/XIO/OTE/TON, v36 IEC mnemonic renames, AOIs, FBD_TIMER in ST). Use when working with any of these tools or files. For Siemens and Schneider use their dedicated skills.
In this repository12 other files it gives its agents.
- convertSkill
- debugSkill
- developSkill
- exchange-formatsSkill
- iec-61131-3Skill
- iec-61499Skill
- new-pouSkill
- packml-isa88-opcuaSkill
- reviewSkill
- schneiderSkill
- siemensSkill
- validateSkill
The file
Files
Other platforms: Beckhoff, CODESYS, ABB, Rockwell
Load the reference for the platform in play. Each one lists the file format, the dialect's differences from IEC 61131-3, and the traps.
| Platform | Current as of 2026-09 | Text/XML an assistant can safely write | Reference |
| Beckhoff TwinCAT 3 | 3.1 Build 4026; PLC++ announced (plain-text files, "almost fully compliant" with 61131-3 Ed.4), GA unverified | .TcPOU / .TcDUT / .TcGVL / .TcIO with ST bodies only | references/beckhoff-twincat.md |
| CODESYS V3.5 | SP22 (Patch 2); SP23 planned Q1 2027 | PLCopenXML (tc6_0200), .export (native), File-Based Storage *.st (preview) | references/codesys.md |
| ABB Freelance (DCS) | Freelance 2024 (announced 2024-10-02); manuals read: 2019 | read the .csv export; bulk-edit via BDM Excel; never hand-edit .prt/.csv for re-import without a backup | references/abb.md |
| ABB AC500 (Automation Builder) | CODESYS-based | PLCopenXML, .export (same-version only) | references/abb.md |
| Rockwell Studio 5000 | v38 (Sept 2025) | L5X component exports, RLL neutral text, L5K | references/rockwell-logix.md |
Cross-platform rules
- Never hand-generate a graphical object archive. That covers TwinCAT
<NWL>/<SFC>/<CFC>XmlArchiveimplementations and CODESYS CFC XML. Write ST, or go through PLCopenXML import. - Version-pin every exchange file:
- The TwinCAT
ProductVersionis optional, but keep it when editing. - Automation Builder
.exportimports only into the same version. - An L5X names its
SoftwareRevision.
- The TwinCAT
- Qualify names the way the target expects:
- TwinCAT/CODESYS GVLs and enums with
{attribute 'qualified_only'}needGVL.xandE_X.Member. - Logix has no qualifier: tags are controller- or program-scoped.
- TwinCAT/CODESYS GVLs and enums with
Validate: python3 ${CLAUDE_PLUGIN_ROOT}/scripts/plc_validate.py <file-or-dir>.
- TwinCAT rules: TC0xx.
- Logix rules: LX0xx. The operand counts accept both the v36 IEC names and the older mnemonics.
- CSV lists: CS0xx.
For a new TwinCAT POU, start from assets/FB_Template.TcPOU.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.