CODESYS · the system & its add-ons

The development system & add-ons

CODESYS has two parts: the CODESYS Development System V3 (the IDE you program in) and the CODESYS Control runtime that vendors embed in their devices. Optional add-ons provide motion, safety, connectivity, HMI and cloud functions within that system.

🧩 Development System V3⚙️ Control runtime
01 · One system, any device

Program devices from different vendors

You engineer in the CODESYS Development System V3 and download to the CODESYS Control runtime, which hundreds of vendors embed in their devices. You can select a target from those vendors instead of working with a single hardware brand.

A few of the manufacturers shipping the CODESYS runtime:

WAGOBeckhoffSchneiderFestoBosch RexrothEatonABBRaspberry Pi
1000+
device types
400+
manufacturers
1
development system

Source : codesys.com

02 · The add-ons

Bolt on what the machine needs

The base system does IEC 61131-3 logic. Everything beyond is an optional add-on within the same project and runtime. Select the functions your machine needs, then tap each add-on below to add it to the project.

Source : codesys.com

03 · Choosing a controller and add-ons

Match the system to your machine

The programming system stays the same when you move between vendors' devices. Choose a controller for the machine's hardware requirements, then select the add-ons for the functions it needs.

🌱 New to this? Beginner

CODESYS is a programming system used on other companies' controllers. You choose the hardware separately from the software used to program it.

  • You write in one IDE (the CODESYS Development System) and download to the CODESYS Control runtime.
  • That runtime is built into 1000+ device types from 400+ vendors, including WAGO, Festo, Bosch Rexroth and Raspberry Pi devices.
  • Add only what you need: SoftMotion (motion), Safety, OPC UA, Visualization, Automation Server (cloud).

Compare it with a browser: one website can run on different phones and laptops. CODESYS has a similar relationship to the vendors' controllers: the programming system stays the same across devices.

⚙️ Go deeper Advanced

You can re-target the same project to devices from different vendors. The add-ons work within that project and its runtime.

  • The base system runs IEC 61131-3 logic (LD, FBD, ST, SFC, IL/CFC).
  • Add-ons extend the same project & runtime: SoftMotion + CNC, functional Safety, OPC UA, built-in Visualization, Automation Server for managing a fleet.
  • Targets range from a Raspberry Pi to industrial PCs and vendor PLCs. Select the hardware for the job while using the same CODESYS system.

When choosing a device, check its I/O, motion and environmental requirements first. Confirm that it ships with a CODESYS Control runtime, then enable only the add-ons the machine needs. The rest of your project stays the same.

🧩
Picture it
A universal remote gives you one set of controls for TVs, soundbars and projectors from different makers. CODESYS works on the same idea: the skills you learn with one vendor's controller transfer to another.
⏱️
Pick your CODESYS setup in 10 seconds
1Check the machine's physical requirements, then choose the device (I/O, motion, ruggedness) from any of the 400+ vendors.
2Does it ship the CODESYS Control runtime? If it does, you can download your project to it.
3For extra motion, safety, HMI or cloud functions, enable the matching add-on, same project.
⚠️
Common mistake
An add-on or project does not belong to a single hardware vendor. CODESYS is device-independent: the same project and add-ons move across devices running the Control runtime, as long as the new device supports each add-on and carries its licence. CODESYS Safety also needs hardware built to support it.

Source : codesys.com

04 · Check yourself

One quick question

What are CODESYS SoftMotion, Safety, OPC UA, Visualization and the Automation Server?