Virtualizes the safety-controller function
The safety application is processed through two logically diverse software channels, enabling a certified safety-control architecture without a conventional dedicated dual-channel PLC hardware design.
CODESYS · Virtual safety control
CODESYS Virtual Safe Control SL
SIL3-Certified Virtual Safety Control with Container Technology
CODESYS Virtual Safe Control SL implements a virtual safety controller using two logically diverse software-processing channels rather than a conventional dual-channel hardware controller. It is certified for IEC 61508 SIL3 applications within the documented product, deployment and communication scope.
Virtual safety instanceDiverse software channelsSafe communicationDocumented configurations
CertificationIEC 61508 SIL3
AssessmentTÜV SÜD
ArchitectureDual logical software channels
Safe networksPROFIsafe · FSoE
Product role
Virtual safety control within a certified SIL3 scope
CODESYS Virtual Safe Control SL implements a virtual safety controller using two logically diverse software-processing channels rather than a conventional dual-channel hardware controller. It is certified for IEC 61508 SIL3 applications within the documented product, deployment and communication scope.
Virtualizes the safety-controller functionThe safety application is processed through two logically diverse software channels, enabling a certified safety-control architecture without a conventional dedicated dual-channel PLC hardware design.
Integrates with virtual-control systemsIt is intended to complement CODESYS virtual standard-control architectures and can be deployed with CODESYS tooling in the supported certified environment.
Keeps certification boundaries explicitThe SIL3 claim applies only within the documented certification scope; arbitrary container hosts or unverified I/O architectures must not be assumed to be covered.
Architecture role
From safety project to safe I/O through virtual control
Define the interfaces and ownership boundaries first; version, licence and target selection should follow the architecture rather than lead it.
01Safety application
02Virtual Safe Control SL
03Certified container deployment
04PROFIsafe / FSoE
05Safe I/O / machine safe state
Confirm the exact target, product version, device package, protocol role, licence and—where applicable—certified safety scope before release to production.
Engineering scope
Certified virtual-safety capabilities and 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.
Integrates with virtual-control systems
It is intended to complement CODESYS virtual standard-control architectures and can be deployed with CODESYS tooling in the supported certified environment.
Keeps certification boundaries explicit
The SIL3 claim applies only within the documented certification scope; arbitrary container hosts or unverified I/O architectures must not be assumed to be covered.
Technical selection
Certificate, host, safe-network and deployment 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.
| Certification | CODESYS Virtual Safe Control SL is certified by TÜV SÜD to IEC 61508 for SIL3 applications within its documented scope. |
|---|---|
| Technical principle | The safety application is executed in two logically diverse processing channels with coded processing, continuous comparison and control-flow monitoring. |
| Safe communication | PROFIsafe in F-Host role and EtherCAT Safety (FSoE) are documented safe-communication routes. |
| Engineering prerequisite | The compatible CODESYS Safety Extension and documented engineering/deployment workflow are required. |
| Deployment qualification | CPU architecture, operating system, container engine, deployment tool, safe-fieldbus configuration and product version must be checked against the current certificate and safety documentation. |
| Project obligations | Safe I/O selection, response-time calculation, fault reaction, verification, validation, version control and proof of the complete machine safety function remain project responsibilities. |
Project workflow
Certified deployment and validation workflow
Move from architecture qualification to engineering, commissioning and lifecycle evidence in a controlled sequence.
Confirm the certified configuration
Select only documented processor, operating-system, container and safe-fieldbus combinations.
Prepare the safety engineering
Use the compatible engineering package, approved libraries and a controlled project workflow.
Deploy the safe instance
Configure the virtual safety controller, safe addresses, PROFIsafe or FSoE communication and safe I/O.
Validate the safety function
Calculate response time and verify fault reaction, safe state, restart, versions and deployment evidence.
Platform context
Virtual Safe Control SL in a virtual-control platform
Use the product only when the documented certified virtual-safety architecture matches the target host, safe network, I/O and required SIL3 application scope.
Current page
CODESYS Virtual Safe Control SL
CODESYS Virtual Safe Control SL implements a virtual safety controller using two logically diverse software-processing channels rather than a conventional dual-channel hardware controller. It is certified for IEC 61508 SIL3 applications within the documented product, deployment and communication scope.
View role in the platform →Functional safetyCODESYS Safety
CODESYS Safety is a portfolio of certified software solutions for functional-safety applications. A safety claim applies only to the specific CODESYS safety product, controller or virtual-control architecture, safe communication and safe I/O covered by the relevant certification and project design.
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 Virtual Safe 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.