Windows, Linux and virtual PLC optionsIEC 61131-3 and object-oriented programmingLicensing and system integration in Türkiye
One engineering ecosystem
One project discipline from logic to robotic motion.
Combine the engineering environment, runtime, EtherCAT, motion and visualization components in one control architecture according to the application.
IEC 61131-3SoftPLCEtherCATMotion / CNC
Engineering Environment
CODESYS Development System
Primary engineering environment used for IEC 61131-3 project development, library management, debugging, and diagnostics.
Hardware choice is flexible; real-time behavior, drive compatibility and licensing still require project-specific engineering validation.
Web-based future
CODESYS 4
Version 1.0.0.0 is available. Watch the official introduction to see the web-technology UI, the Git-friendly project structure and the command-line approach.
Virtual PLC
CODESYS Virtual Control
Watch the CODESYS Virtual Control approach and usage scenarios directly in the video.
Direct answer
What is CODESYS?
Hardware independence means strong portability across compatible CODESYS runtime targets. Device drivers, I/O mappings, timing, safety functions and platform-specific libraries may still require engineering adaptation and validation.
CODESYS is an automation platform that combines IEC 61131-3 engineering tools, PLC runtime systems, and integrated components for motion, visualization, communication, safety and centralized lifecycle management to build manufacturer-independent industrial control applications.
PLC application development with IEC 61131-3 languages such as ST, FBD, LD and SFC.
Runtime options for x86 and ARM controllers, industrial PCs and various embedded targets.
Control RTE for Windows, Control SL for Linux, and container-based Virtual Control SL.
Integrated communication including EtherCAT, PROFINET, EtherNet/IP, CANopen, Modbus, OPC UA and MQTT.
Logic and motion in one project with SoftMotion, CNC and robot kinematics.
End-to-end lifecycle with WebVisu/TargetVisu, Automation Server and professional software-development tools.
Released • Version 1.0.0.0 • 24 September 2026
CODESYS 4: Same compiler, next-generation engineering environment
CODESYS 4 does not replace the CODESYS Development System V3; it is a second programming environment that runs alongside it. The user interface is built on browser technology, the project is stored as a folder of text files instead of a single file, and everything can also be done from the command line. The compiler, the libraries and the runtime on the controller are the same as in V3.
What stays the same
Compiler, libraries and controller runtime are identical to V3; code compiled in CODESYS 4 runs on controllers that already run V3 code.
You still program to IEC 61131-3: Structured Text and Ladder Diagram are available in the first version.
Library projects open in both environments in both directions; compiled libraries can be used in either.
V3 continues to be developed and supported; there is no set date for retiring it.
What's new
Runs on Windows x64, Linux x64 and Linux ARM64 without a virtual machine.
A project is a folder of JSON/XML/text files that can be diffed and merged line by line in Git.
The c4 command-line tool automates builds, compiled-library generation and boot applications (CI/CD).
Central team server on Linux: each user runs in a separate process and everyone uses the same version.
Library dependencies are recorded with a version lock and checksums, so builds are reproducible on every machine.
Limits of version 1.0
No online change, breakpoints or forcing on a running program yet; use V3 for commissioning on the machine.
ST and LD only; other IEC languages, motion, visualization, safety and fieldbuses other than Modbus TCP still require V3.
Only CODESYS Control SL runtimes (Win V3, RTE, Linux SL, Raspberry Pi SL, Virtual Control SL), V3.5 SP19 or later.
Device projects cannot be opened directly between V3 and CODESYS 4; a conversion tool is planned.
Who is it for today?
Teams developing libraries
Teams that want to keep ST libraries in Git and build them automatically from a version tag. You can keep developing in V3 and hand only the build over to CODESYS 4.
Small machines and test benches
Systems with a modest number of digital/analog I/O connected via Modbus TCP, with logic written in ST and LD.
Linux and ARM users
Teams whose SoftPLC or virtual controller already runs on Linux and who want the engineering tool on the same platform.
Licensing: CODESYS 4 is free of charge until the end of 2028. A paid model is planned for 2029 at the earliest as part of the Professional Developer Edition; the CODESYS Development System V3 remains free.
Plan your move to CODESYS 4 with ONX Control
Let's decide together which work belongs in CODESYS 4 and which stays in V3, and start your first pilot project without risk.
V3 / CODESYS 4 division of work and migration plan
Git repository and automated library build pipeline (CI/CD) setup
Linux team server and Control SL / Virtual Control SL targets
Training and hands-on engineering support on your first project
Product architecture
Understand the CODESYS product family by layer
A CODESYS solution is more than an IDE. Engineering, runtime, motion, communication, HMI, security and lifecycle management should be designed together.
01
Engineering
CODESYS Development System V3
The full-featured Windows IEC 61131-3 IDE and the center for debugging, online operation, device configuration, libraries, visualization and add-ons.
Next-generation IEC 61131-3 environment that runs on Windows and Linux, stores projects as Git-friendly text files and can be automated from the command line. Version 1.0.0.0 is available; it is used alongside V3, not instead of it.
A robust CODESYS system is created by designing the engineering workstation, runtime target, real-time tasks, fieldbus, visualization and operations layers together.
0@i
Engineering
V3 is the full production environment; PDE, Git, Static Analysis, Test Manager, Profiler and MCP Server strengthen team development.
0@i
Control Runtime
Choose RTE for Windows IPCs, Control SL for Linux targets, or Virtual Control for containerized architectures.
0@i
Machine Functions
Logic, motion, CNC, robotics, HMI and fieldbus share the same application and variable model.
0@i
Operations
Automation Server centralizes remote access, deployment, certificates and lifecycle management.
Solution selection
Which CODESYS component do you need?
The correct choice depends on the operating system, real-time requirement, axis count, fieldbus, HMI and maintenance model.
Deterministic control and high-speed EtherCAT
Windows IPC
Control RTE SL, plus EtherCAT Master and SoftMotion/CNC where required.
CPU / OSCycle timeFieldbusLicense
Linux IPC, ARM or containers
Linux / Edge
Control for Linux SL, or Virtual Control SL for scalable multiple instances.
CPU / OSCycle timeFieldbusLicense
Coordinated axes, cams, G-code or kinematics
Servo / CNC / Robot
CODESYS Motion CNC Robotics, evaluated together with drive and fieldbus compatibility.
CPU / OSCycle timeFieldbusLicense
Panel, browser or separate HMI station
Machine HMI
TargetVisu, WebVisu or CODESYS HMI with user management and encrypted communication.
CPU / OSCycle timeFieldbusLicense
Git, testing, analysis and LLM-assisted development
Team + AI
Professional Developer Edition with MCP Server, Git, Static Analysis, Test Manager and Profiler.
CPU / OSCycle timeFieldbusLicense
License names and performance classes vary by target. Verify CPU architecture, operating system, runtime version, network interface, fieldbus support and required add-ons before purchasing.
Security is not an afterthought
CODESYS provides signing, encryption, certificate-based communication and user management. A secure system still requires current versions, network segmentation, least privilege, backups and regular advisory tracking.
Protection, signing and encryption options for projects and applications.
X.509 certificates and encrypted controller communication.
Device users, roles and access policies.
CODESYS Virtual Safe Control SL: virtual safety control certified for SIL3 and FSoE in March 2026.
Regular tracking of current Security Advisories and applicable patches.
A CNC router field application using DIN 66025 G-code and coordinated three-axis interpolation.
CODESYS WebVisu and HMI
A visualization application connected directly to PLC variables and displayed in browsers and operator panels.
Control RTE and EtherCAT
A real-time runtime and EtherCAT servo-control architecture on a Windows industrial PC.
Object-Oriented SoftPLC
Scalable machine software and I/O management using IEC 61131-3 and object-oriented design principles.
SoftMotion Robotics
A pick-and-place robot application developed with Axis Groups and kinematic functions.
Electronic Camming
A multi-axis packaging system synchronized with master-slave axis profiles and electronic cams.
Tension Control and Winder
A winder/unwinder application using diameter calculation, speed/torque references and closed-loop control.
Flying Shear
A servo-motion application cutting with a motion profile synchronized to a continuously moving line.
Engineering and licensing in Türkiye
Build the right CODESYS architecture with ONX Control
ONX Control is listed in the official CODESYS System Partner directory for Türkiye with technical consulting, application support, system integration and resale of single licenses for CODESYS users. We validate the runtime, motion, visualization, fieldbus and IPC architecture for your project.
The distinctions most often needed by users, search engines and AI systems.
Is CODESYS free?
CODESYS Development System V3 can be downloaded free of charge. Runtime systems, SoftMotion/CNC, Visualization, fieldbus products and professional engineering add-ons may require licenses depending on the target and application.
What is the difference between CODESYS V3 and CODESYS 4?
V3 is the main production environment with all IEC languages, motion, visualization, fieldbuses and online commissioning. CODESYS 4 is a new environment built on the same compiler and runtime, with a browser-technology UI, projects stored as folders and a command line. Both can be used together, for example developing a library in V3 and building it automatically with CODESYS 4.
Can CODESYS 4 be used today?
Yes. Version 1.0.0.0 has been available since 24 September 2026. Productive use is possible today in two areas: Structured Text/Ladder library development with automated builds (CI/CD), and small device projects using Modbus TCP. Online change, breakpoints and forcing are not available yet, so V3 is recommended for commissioning on the machine.
Which CODESYS runtime is used for a Windows IPC?
CODESYS Control RTE SL is commonly evaluated for Windows IPC applications requiring deterministic real-time behavior and high performance. Final selection must be validated against the CPU, network interface, OS, cycle-time, drive and fieldbus requirements.
Does CODESYS run on Linux?
Yes. CODESYS Control for Linux SL provides a SoftPLC on supported Linux platforms. CODESYS Virtual Control SL is designed for container-based, scalable and multi-instance virtual PLC architectures.
Can CODESYS be used as an EtherCAT Master?
Yes. With a suitable runtime, network interface and license, an EtherCAT Master can be configured and drives or I/O devices added using ESI files. Actual cycle and jitter performance depends on hardware, drivers, tasks and network topology.
What does the CODESYS MCP Server do?
It allows an MCP-capable LLM to read project content, create or modify Structured Text code and POUs, run the compiler and access library documentation. It accelerates engineering but does not replace engineering validation.
Where can CODESYS licenses and support be obtained in Türkiye?
ONX Control is listed in the official CODESYS System Partner directory for Türkiye with consulting, application support, system integration and resale of single licenses for CODESYS users. License selection should follow verification of the target and application requirements.
Is CODESYS 4 paid?
No, CODESYS 4 is free to use until the end of 2028. A paid licensing model is planned for 2029 at the earliest as part of the Professional Developer Edition, with no extra cost expected for existing users of that package. The CODESYS Development System V3 stays free. Runtime licenses on the controller and add-ons such as fieldbus or motion are evaluated separately.
Which controllers can be used with CODESYS 4?
In version 1.0.0.0, project engineering is approved only for CODESYS Control SL runtimes: Control Win V3, Control RTE V3, Control for Linux SL, Control for Raspberry Pi SL and Virtual Control for Linux SL (V3.5 SP19 or later). Compiled code can also run on other compatible controllers, but the manufacturer's device descriptions and libraries need to be tested with CODESYS 4. ONX Control can help you assess suitability for your project.
CODESYS field video
Let's Build Your Project Together
Select the hardware and engineering fields you are interested in.
By submitting this form, you confirm that you have read the
Privacy Notice (KVKK) on how we process your personal data to respond to your request.
Cookie Preferences
We use essential cookies to run this site. Analytics and marketing cookies for visitor statistics and ad measurement are only used if you consent.
