Virtualizes controller instances
Multiple PLC instances can share a compute platform where available resources and machine architecture allow consolidation.
CODESYS · Virtual PLC
CODESYS Virtual Control SL
Container-Based Virtual PLC for Linux Automation Platforms
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.
Central computeInstance isolationDeploy ToolSoftware-defined control
ArchitectureContainerized PLC
HostSupported Linux
CPU familiesx86-64 · ARM / ARM64
I/O pathIndustrial Ethernet
Product role
Virtual PLC execution on a shared Linux platform
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.
Virtualizes controller instancesMultiple PLC instances can share a compute platform where available resources and machine architecture allow consolidation.
Preserves the CODESYS engineering modelApplications are created in the Development System and deployed to the virtual runtime like other CODESYS targets.
Enables IT-style lifecycle methodsContainer deployment, versioning, orchestration and centralized maintenance can be applied without moving deterministic control logic into an IT management layer.
Architecture role
Virtual-control host, instance and I/O architecture
Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.
01Development System
02Virtual Control SL instance
03Linux + container engine
04Industrial Ethernet
05Remote I/O / drives
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope
Virtualization, scaling and lifecycle capabilities
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.
Preserves the CODESYS engineering model
Applications are created in the Development System and deployed to the virtual runtime like other CODESYS targets.
Enables IT-style lifecycle methods
Container deployment, versioning, orchestration and centralized maintenance can be applied without moving deterministic control logic into an IT management layer.
Technical selection
Host, container, network and real-time requirements
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.
| Deployment model | Containerized runtime instances execute on a supported Linux host rather than on a dedicated PLC hardware platform. |
|---|---|
| Host qualification | Linux distribution, kernel, processor architecture, container engine, permissions, network interfaces and available resources must meet current product requirements. |
| I/O architecture | Field I/O is typically reached through Industrial Ethernet. Network cycle time, redundancy and fault behaviour therefore become part of the controller architecture. |
| Instance scaling | The practical number of PLC instances depends on CPU, memory, networking, real-time requirements and application load—not on a fixed marketing count. |
| Lifecycle | Deployment, restart, update, rollback, monitoring and host-failure recovery should be engineered and acceptance-tested. |
| Licensing | Current Virtual Control SL licensing is application-based and includes network-licensing requirements documented by CODESYS. |
Project workflow
Qualification and deployment workflow for virtual PLCs
Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.
Qualify the host platform
Confirm operating system, processor architecture, container technology and resource capacity against the product documentation.
Allocate resources per instance
Reserve CPU, memory, network interfaces and licences, and define the isolation between instances.
Engineer the I/O network
Design Industrial Ethernet topology, cycle times, diagnostics and behaviour on link failure.
Prove lifecycle operations
Test deployment, restart, update, rollback, monitoring and recovery from host failure.
Platform context
Virtual Control SL application and engineering scope
Use Virtual Control SL when consolidation and lifecycle flexibility justify a virtual PLC architecture and the host/network can meet the control-performance requirement.
Current page
CODESYS 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 →Control executionCODESYS 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 →Controller and project managementCODESYS Automation Server
CODESYS Automation Server provides a centralized operations layer for connected CODESYS controllers and engineering projects. It supports device management, project/application versioning, remote engineering access, controlled rollouts, certificates, users and data analysis while local controllers continue to execute machine control independently.
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 Virtual Control SL 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.