PLC Software Composition: 2026 Engineering Notes on Firmware, OS, Runtime

Detail

Since 2024 the runtime layer has absorbed edge analytics, security stacks, and partial safety logic, user programs now ride a much richer OS than the bare scheduler of the 2010s.

Picking firmware/hardware that match your existing user program is the single biggest factor in avoiding downtime during repairs and EOL migrations.

A PLC's software stack is firmware plus RTOS plus your IEC 61131-3 user program. In 2026 the runtime carries OPC UA FX, security, and edge containers.

you author in an IEC 61131-3 language. This 2026 engineering note rewrites the original 2024 article with the new runtime stack, OPC UA FX, signed firmware, container sidecars, and partial safety integration, and explains how to keep them aligned during repairs and migrations.

PLCs are deterministic controllers, but the software that runs them is no longer a single monolithic firmware blob. A 2026 controller stacks three distinct layers, each owned by a different team:

, the vendor-shipped IEC 61131-3 execution engine, communication stacks (EtherNet/IP, PROFINET, Modbus TCP, OPC UA, OPC UA FX), web server, and security stack.

, a real-time OS or hypervisor (vendor-tuned RTOS, Linux RT, or VxWorks) that schedules tasks, manages memory, and isolates the runtime from optional sidecar containers.