Every other academy here teaches one vendor's tool. CODESYS is the odd one out: it's the programming system embedded inside 1000+ devices from 400+ manufacturers. Your program targets the CODESYS runtime, not the silicon โ so the exact same code runs on a WAGO, a Festo, or a Raspberry Pi. Compile it once and download to all three.
Here's your program โ a tiny blinker-and-counter POU. Below are three controllers from three different vendors. Each runs the CODESYS runtime on top of its own hardware. Press โ๏ธ Compile & download to all and the very same compiled app drops onto every target โ then they all run in perfect lockstep, because they're running identical code on an identical runtime.
๐ All three lamps blink together and the counters stay in sync โ same logic, same runtime, three completely different vendors' hardware. The only thing that differs per target is the I/O mapping (which physical pin xLamp drives). Change targets and your logic never changes; only the mapping does.
Source : codesys.com
๐ Skills transfer. Learn CODESYS once and you can program WAGO, Festo, Eaton, ABB, Beckhoff (TwinCAT is CODESYS-derived) and countless OEM controllers. One skillset, a whole industry.
๐ช No lock-in. Outgrew a controller? Re-target the project to a bigger CODESYS device, remap the I/O, download. Your application โ the valuable part โ comes with you.
๐งช Cheap to learn. The CODESYS runtime even runs on a Raspberry Pi โ a full IEC 61131-3 PLC for the price of a snack. Prototype on the Pi, deploy on the industrial target.
๐งฉ Standards-pure. CODESYS is reference-grade IEC 61131-3 (and pushed OOP into it). Concepts you learn here are the concepts the standard defines โ they carry everywhere.
You finish a project on a WAGO controller, then must redeploy it to an Eaton controller. What has to change?