News

What lives here?

Each release this page summarises the important changes, in chronological order (newest first). Format:

  • Short summary — what it means for you as a user
  • Technical note — pointers to specific commits, spec sections and new documentation pages
  • Migration / breaking changes when present

To stay current: APT update as usual (sudo apt update && sudo apt upgrade); or follow the source tree via GitHub / Forgejo.


Posts

News entries are listed here automatically by date (newest first). For an RSS feed: available at /news/index.xml.

Open language backend: matiec → matiec++ → rustly evolution path

Three IEC 61131-3 backends in parallel — in a clear order: matiec today, matiec++ next, rustly as the goal.

IO-list roundtrip: a CSV bridge between electrician and programmer

bus.import_iolist + bus.export_iolist — 14-column CSV with EPLAN-property headers, idempotent import, no variable invention

IEC standard library as a learning reference with LLM auto-fix

Every IEC 61131-3 function and function block with a textbook explanation, the matiec quirks, and a machine-readable auto-fix block for the AI assistant.

Federation + team trust: multiple workstations, controllable trust

ForgeIEC now connects multiple workstations into a team — with verifiable identities and a clear role model

From the first byte: the ForgeIEC story

How an OpenPLC fork became an independent IEC 61131-3 platform — and why

The AI assistant in the editor: from chat to platform

Built-in AI assistant with ~80 tools, multi-persona workflow, open connector for Claude Desktop, VS Code, ChatGPT

Live diagnostics: monitor + oscilloscope for IEC 61131-3

Live variable values, FB-member resolution, oscilloscope with trigger, CSV recording, measured jitter — commissioning tools at industry level

Security architecture in 3 layers

Per-variable force gate, Confirmation State Machine, build-time gating — how ForgeIEC prevents an AI or a misclick from moving real hardware

Tongs — modular fieldbus bridges with a fault model

One daemon per protocol, uniform status wire format, diagnostic bits from the FDD — no vendor plugin sprawl

Manufacturer data as first-class citizen: FDD system

Device descriptions with embedded PDF data sheets, diagnostic-bit resolution, module picker — no more PDF hunting