Executes the compiled control application
The runtime loads, schedules and executes the application produced by the CODESYS Development System.
CODESYS · Control execution
CODESYS Runtime
Runtime Execution Layer for CODESYS Control Applications
CODESYS Runtime is the execution layer that turns a compatible target into a programmable controller. The application is created in the Development System, compiled for the selected target, and executed by CODESYS Control—either already integrated by an OEM or installed as a ready-to-use Control SL SoftPLC on a supported platform.
Local and remote I/ORetentive dataPLC shellOptional visualisationMotion add-ons
Execution layerCODESYS Control
SoftPLC routeControl SL
Alternative routeOEM CODESYS controller
PerformanceTarget-specific
Product role
Execution layer for a CODESYS control application
CODESYS Runtime is the execution layer that turns a compatible target into a programmable controller. The application is created in the Development System, compiled for the selected target, and executed by CODESYS Control—either already integrated by an OEM or installed as a ready-to-use Control SL SoftPLC on a supported platform.
Executes the compiled control applicationThe runtime loads, schedules and executes the application produced by the CODESYS Development System.
Supports multiple target strategiesProjects can run on OEM controllers with CODESYS Control integrated or on supported hardware equipped with a Control SL SoftPLC.
Defines real execution performanceTask timing, jitter, I/O update behaviour and available protocol roles depend on the selected hardware, operating system and runtime configuration.
Architecture role
From compiled application to machine execution
Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.
01Development System
02Compiled application
03CODESYS Control / Control SL
04I/O & fieldbus
05Machine / process
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope
Runtime responsibilities and performance boundaries
These capabilities define what the CODESYS component contributes to the architecture and what must still be provided by the controller, host platform, network or machine design.
Supports multiple target strategies
Projects can run on OEM controllers with CODESYS Control integrated or on supported hardware equipped with a Control SL SoftPLC.
Defines real execution performance
Task timing, jitter, I/O update behaviour and available protocol roles depend on the selected hardware, operating system and runtime configuration.
Technical selection
Target platform and runtime qualification
Use this table as a requirement-capture guide. The final implementation should be checked against current CODESYS product documentation, Store data, target documentation and—where relevant—certificates and safety manuals.
| CODESYS Control | The runtime technology that executes CODESYS applications on a controller or computing platform. |
|---|---|
| Control SL | Ready-to-use SoftPLC products for supported general-purpose or industrial computing platforms. |
| OEM controller route | Many controller manufacturers integrate CODESYS Control directly; these devices are programmed through the matching device package. |
| Real-time behaviour | Processor, operating system, scheduler, drivers, I/O topology and runtime configuration determine achievable task performance. |
| Communication and I/O | Fieldbus stacks, master/device roles, local I/O access and higher-level communication are target- and licence-dependent. |
| Optional functions | Visualization, motion, redundancy and communication extensions require a compatible target and the corresponding product/licence scope. |
Project workflow
Runtime selection, integration and acceptance workflow
Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.
Define the target platform
Confirm processor architecture, operating system, real-time requirement and I/O access.
Select the runtime route
Choose an OEM controller with CODESYS Control integrated, or licence a Control SL runtime for the platform.
Integrate the control system
Connect I/O, fieldbus, visualisation and any motion functions the application requires.
Validate operation
Verify timing, restart behaviour, retentive data, diagnostics, backup and recovery.
Platform context
Runtime, virtual control and communication choices
Start with the physical or virtual target strategy, then verify I/O, communication, HMI and optional motion requirements against that runtime.
Current page
CODESYS Runtime
CODESYS Runtime is the execution layer that turns a compatible target into a programmable controller. The application is created in the Development System, compiled for the selected target, and executed by CODESYS Control—either already integrated by an OEM or installed as a ready-to-use Control SL SoftPLC on a supported platform.
View role in the platform →EngineeringCODESYS Development System
CODESYS Development System is the core engineering environment for creating industrial control applications. It combines IEC 61131-3 programming, device and I/O configuration, libraries, compilation, debugging and online commissioning in one project. The application is engineered here and executed later by a compatible CODESYS runtime.
View role in the platform →Virtual PLCCODESYS Virtual Control SL
CODESYS Virtual Control SL provides a containerized IEC 61131-3 runtime for virtual PLC deployment on supported Linux systems. The engineering workflow remains CODESYS-based, while controller instances, compute resources, networking, I/O access and lifecycle operations are managed on the host platform.
View role in the platform →Documentation & requirement capture
Official CODESYS documentation and project inputs
Use the official product page for current product information, then provide the project-specific details below so the architecture can be reviewed against the actual machine or system.
Official CODESYS Runtime informationOpen CODESYS ↗Complete CODESYS platform architecturePlatform overview →
Application scopeMachine/process functions, operating modes, cycle-time expectations and whether the project is new design, retrofit or migration.
Target & software baselineController/IPC, CPU architecture, operating system, CODESYS runtime, device package, compiler profile and existing project version.
I/O & communicationLocal/remote I/O, fieldbuses, Industrial Ethernet, OPC UA, MQTT, controller-to-controller links and required protocol roles.
HMI & user accessDisplay hardware, browser clients, independent HMI requirements, alarms, trends, recipes, user roles and remote-service policy.
Motion & functional safetyAxis count, drives, kinematics, CNC/robotics requirements, safe I/O, safe communication and required PL/SIL where relevant.
Deployment & lifecycleController quantity, sites, licensing, backups, certificates, update process, rollback expectations and maintenance ownership.