Engineering system
IEC 61131-3 programming, device configuration, libraries, debugging and commissioning are handled in one engineering environment.
Build IEC 61131-3 control applications, operator interfaces and motion functions on compatible industrial and embedded controller platforms. Integrate safety functions through supported CODESYS Safety products and application-specific safety hardware selected from the machine risk assessment.
Field values, commands and machine states
Logic, sequencing and coordinated motion
Visualization, diagnostics and alarms
Compatible industrial and embedded controllers
The portfolio combines CODESYS engineering, runtime, visualization and motion functions with application-specific machine-safety components. Standard control and functional safety are engineered as separate responsibilities and integrated through defined interfaces.
IEC 61131-3 programming, device configuration, libraries, debugging and commissioning are handled in one engineering environment.
SoftPLC and virtual-control options turn compatible industrial or embedded platforms into application controllers.
Target, web and remote visualization provide operator access without separating HMI engineering from the control project.
PLCopen motion, coordinated axes, CNC functions and robotic kinematics can be added where the machine requires them.
Software-integrated safety and independent field-safety components cover different parts of the safety architecture and must be selected against the machine risk assessment.
Fieldbus, industrial Ethernet, OPC UA and MQTT connect the controller to devices, supervisory systems and edge applications.
Use the platform for machine control, distributed software controllers, motion-enabled equipment and safety-related machinery with hardware and software selected for the application.
Combine logic, visualization, recipes, alarms and device communication in one project for stand-alone machines and production equipment.
Deploy runtime instances on industrial PCs or embedded controllers while keeping common engineering methods across machine variants.
Coordinate drives, axes and process logic from the same application when sequence and motion behaviour must remain synchronized.
Combine certified or otherwise approved safety software and controllers with suitable relays, safety sensors and safe-motion functions. The complete safety function must be validated against the required PL or SIL.
A typical system separates engineering, runtime execution, visualization, field communication and controller operations while maintaining a controlled application model.
Develop and test the application, configure devices and maintain reusable libraries.
Run the application on a compatible PLC, industrial PC, embedded controller or virtualized control platform.
Present machine state, alarms, trends and commands through local or browser-based visualization.
Connect controllers to supervisory systems and manage deployed projects through supported server services.
The CODESYS Development System implements IEC 61131-3 and brings programming, device configuration and diagnostics into one workflow.
Use Structured Text, Ladder Diagram, Function Block Diagram and Sequential Function Chart according to application and team practice.
Configure supported devices, networks and I/O mappings alongside the control application.
Online monitoring, forcing, trace, watch lists and breakpoints help verify machine behaviour during startup.
Libraries, interfaces and project templates support controlled reuse across machine families.
Programming editors, device and fieldbus configuration, visualization design and online diagnostics are brought into a common project environment. This keeps software, I/O mapping and commissioning information aligned as the machine is developed.
The runtime layer executes the control application and provides the device interfaces needed by the selected target.
Use compatible Linux, Windows or embedded targets where a software controller is appropriate.
Separate cyclic, event-driven and background tasks according to timing and workload.
Keep the application portable by isolating hardware-specific I/O and communication details.
Define startup, watchdog, retained-data and update behaviour for the actual machine environment.
Visualization is engineered from the same project so variables, alarms and user actions stay aligned with the controller application.
Run operator screens on a panel PC or controller-connected display.
Serve browser-based interfaces to authorized clients on the machine or plant network.
Build trends, alarms, recipes, user roles and diagnostic views around the machine workflow.
Adapt screens to the target display rather than duplicating the control project for every device.
Motion functions can be introduced where coordinated positioning, path control or robotics are part of the machine sequence.
Use PLCopen-aligned motion blocks for positioning, gearing, camming and synchronized movement.
Add interpolation and path planning where the machine follows defined trajectories.
Integrate supported kinematic models with the PLC application for coordinated machine and robot behaviour.
Match bus cycle, drive profile, feedback and safety functions to the required motion performance.
Machine safety is designed from the risk assessment. Depending on the application, the safety chain can include emergency-stop devices, guard switches and locking, light curtains, scanners or radar, safety relays, configurable safety controllers, safe I/O and safe motion.
Use compatible safety controllers and CODESYS Safety components only within supported and certified architectures for the intended safety function.
Monitor emergency stops, guards, light curtains and other safety functions with components selected to the application complexity.
Apply guard switches, locking devices, light curtains, scanners or area monitoring according to the hazard and access concept.
Monitor standstill, speed and motion limits where access during setup or maintenance is required.
Communication is selected around ownership of the data, required cycle time and the systems that consume it.
Connect supported EtherCAT, PROFINET, CANopen and other device networks through the appropriate master or slave components.
Expose structured controller data to SCADA, MES or edge systems with authenticated and encrypted sessions where configured.
Publish selected machine data to an MQTT broker without treating cloud connectivity as part of the deterministic control loop.
Keep safety, real-time control and business-data traffic separated according to their timing and security requirements.
CODESYS Automation Server supports centralized management of connected controllers, applications, projects, users, certificates and authorized remote-service workflows. The deployment model and network access must follow the plant cybersecurity policy.
Organize supported controllers and their project associations in a managed environment.
Deploy applications and supporting files to authorized targets using defined user permissions.
Maintain shared project access and controlled transfer between engineering and operations teams.
Review the SaaS service and the current on-premises product availability against cybersecurity, network, data-sovereignty and governance requirements.
Controller inventory, project coordination, remote maintenance and application deployment are handled above the runtime layer. The operating model, network access and user permissions still need to match the plant cybersecurity policy.