Vendor-neutral AI for PLC programming means one assistant that drafts, checks and converts IEC 61131-3 logic whatever controller the job uses, instead of a separate copilot inside each vendor's IDE. LADX, the Wartens group's AI product for controls teams, is built for that case: it compiles every AI answer with an open IEC 61131-3 compiler before you see it, and writes programs out to Structured Text, Siemens SCL, Rockwell neutral text or PLCopen XML.
That is a different job from the vendor assistants, and it is worth being clear about which tool is for what. A UK integrator might be on an S7-1500 at a water treatment works on Monday, a CompactLogix packaging cell on Wednesday and a CODESYS skid on Friday. Each vendor's assistant helps on one of those days.
What the vendor copilots are for
| Vendor tool | Where it lives | What the vendor says it does |
|---|---|---|
| Siemens Eigen Engineering Agent | Connected to TIA Portal | SCL and LAD generation, test logic, fixing compile errors |
| Rockwell FactoryTalk Design Studio Copilot | Cloud-based Logix design environment | Generates PLC code from prompts, explains rungs and routines |
| Beckhoff TwinCAT Chat | TwinCAT XAE engineering | LLM client for function block code, documentation, refactoring |
Siemens describes its Eigen Engineering Agent as a generative AI assistant connected to TIA Portal that reads the project structure. Rockwell's FactoryTalk Design Studio includes a generative AI copilot that takes natural language prompts and can explain inherited code. Beckhoff's TwinCAT Chat brings large language models into the TwinCAT engineering environment.
All three are reasonable tools if you live in one ecosystem. They know their own hardware, libraries and project structure better than any outsider can. The catch is the word own: none of them is designed to help you on the other vendor's controller.
Why UK integrators need vendor-neutral AI for PLC programming
The UK installed base is mixed. Water company estates often mix PLC platforms across regions and asset ages. Food and packaging SMEs buy machines from whichever OEM won the tender, so one factory floor can carry four PLC brands. Maintenance departments and integrators carry that mix every day, and they are the people least served by single-vendor tools.
What they need from AI is narrower and harder: logic that compiles, written in a portable form, with a clear record of what did not carry across between platforms.
How LADX checks code before you see it
A general chatbot writes plausible ladder. Plausible is not good enough when wrong code stops a line. LADX runs every answer through a loop: the model generates, matiec (the open IEC 61131-3 compiler) compiles it, iec-checker runs static analysis, and a PLCopen schema pass checks the structure. Anything that fails goes back to the model with the compiler's errors attached, and only a passing result reaches the canvas.
Generation is a loop rather than a single shot.
The answers arrive as rungs in the ladder editor, using the tags already in your project and the design basis you filled in, rather than as text you paste somewhere. You can select a rung and ask what it does, or ask for a permissive to be added to it.
Moving logic between platforms
LADX Convert reads a program into one intermediate representation built on PLCopen TC6 and writes it out as IEC 61131-3 Structured Text, Siemens SCL, Rockwell neutral text or PLCopen XML. Every element in the report is marked as converted cleanly, converted with a semantic difference worth reading, or needing a decision. The conversion runs in the browser, so customer code is not uploaded.
Be clear about the limits. Reading vendor projects back in is, in LADX's words, the half that is not built yet. Whole-project formats such as .ACD and .ap1x need a desktop bridge and your own licensed IDE. Bridged rungs are refused and preserved rather than approximated. For a full S7-300 to S7-1500 job you still need TIA Portal; see our S7-300 to S7-1500 migration plan for how that work runs.
Your model, your key, your code
- Bring your own provider. OpenRouter is the default, including its free models, alongside Anthropic, OpenAI or any OpenAI-compatible endpoint, including a local Ollama model. LADX holds no shared key and does not meter usage.
- Programs treated as trade secrets. LADX says code is encrypted at rest, scoped to your project, never used for training and deletable in one action. AI requests go only to the provider whose key you connected.
- No writes to live controllers. LADX does not download to a running PLC, by design. The vendor IDE remains the tool that touches hardware.
What it does not do
LADX drafts. Whether an interlock is sufficient for the hazard is an engineering judgement that stays with the engineer. A compiler proves code is valid, not that it is correct, and a passing simulation is not a safety case. Free models are rate-limited by their providers, so expect the occasional queue. None of this replaces a functional specification, peer review and a factory acceptance test.
The Siemens Industrial Copilot: A generative AI-powered assistant for the industry
Siemens Knowledge Hub
This video is hosted on YouTube. Playing it loads content from Google, which may set cookies.
Watch on YouTubeWhere Wartens fits
LADX is a product of the Wartens group. In the UK we deliver PLC and SCADA work as an engineering service, written in the platform the client specifies. Our PLC programming and SCADA engineering service covers Siemens, Rockwell and CODESYS jobs. If you want to try ladder before anything else, our guide to the free ladder logic simulator is a gentle start.
Next step
Try LADX on one function from a current job at ladx.ai. If you have a multi-vendor programme of PLC work that needs engineering capacity, tell us about it and we will reply with a written scope and price.
