PLC System Software & User Program in 2026: Runtime, Firmware & IEC 61131-3
On this page
PLC System Software & User Program in 2026: Runtime, Firmware & IEC 61131-3
is no longer "the firmware in the rack", it is a layered runtime with versioned firmware, an IEC 61131-3 editor, an OPC UA stack, and a growing set of cybersecurity and cloud hooks. This Engineering Note refreshes our 2024 article on the same topic and walks through what changed, what engineers should pin in their maintenance procedures, and where to source the runtime components you still cannot
Detail
PLC "system software" in 2026 means a runtime, firmware, and editor, not a single binary.
IEC 61131-3 v4 (2026 draft) adds semantic versioning, OO extensions, and time-deterministic POUs.
OPC UA over TSN is the default fieldbus-to-cloud bridge; PROFINET / EtherNet/IP remain on the floor.
Cybersecurity (IEC 62443-4-2 SL2) is now a firmware-level requirement, not an add-on.
AI-assisted code generation ships inside the editor: TIA Portal V20 Assistant, Studio 5000 Copilot, CODESYS AI.
A 2026 PLC separates the runtime, the firmware, and the user program; engineers can update each layer independently while keeping IEC 61131-3 v4, OPC UA, and IEC 62443-4-2 in scope.
Our original 2024 post grouped PLC system software into three components, operating system, programming environment, and communication protocols. Two years on, the grouping still holds, but each component has shifted under the engineer's feet. The runtime is now a container, the firmware ships with a signed manifest, the editor hosts an AI assistant, and the protocol stack carries a cybersecurity certificate that procurement will ask for. This Engineering Note keeps the 2024 vocabulary and overlays what is genuinely new in 2026.
Sourcing help
Send the BOM for one quote covering active stock, EOL stock and cross-references.
Need a quote for this part?
Send us the part number or article link — we will confirm price, availability and lead time.