Import OPC UA model to Codesys ^{CODESYS Forge talk (Thread)}
Import OPC UA model to Codesys
Last updated: 2024-03-12

CODESYS Installer CLI - commands syntax description ^{CODESYS Forge talk (Thread)}
CODESYS Installer CLI - commands syntax description
Last updated: 2024-03-20

Codesys v3.5 SP11 and Python scripts ^{CODESYS Forge talk (Thread)}
Codesys v3.5 SP11 and Python scripts
Last updated: 2024-04-05

Codesys 3.5.12 Module not Found ^{CODESYS Forge talk (Thread)}
Codesys 3.5.12 Module not Found
Last updated: 2024-04-17

Launch a *.exe file from codesys ^{CODESYS Forge talk (Thread)}
Launch a *.exe file from codesys
Last updated: 2024-04-19

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-20

Upgrade from codesys 3.5.19 to 3.5.20 ^{CODESYS Forge talk (Thread)}
Upgrade from codesys 3.5.19 to 3.5.20
Last updated: 2024-04-23

Trouble installing codesys 64 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Trouble installing codesys 64 3.5.19.0
Last updated: 2024-04-23

Raspberry Pi Codesys SPI Master ^{CODESYS Forge talk (Thread)}
Raspberry Pi Codesys SPI Master
Last updated: 2024-04-23

Codesys v3.5 Sint to byte ^{CODESYS Forge talk (Thread)}
Codesys v3.5 Sint to byte
Last updated: 2024-04-24

AG Abzug bei Codesys 3 ^{CODESYS Forge talk (Thread)}
AG Abzug bei Codesys 3
Last updated: 2024-05-08

CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Thread)}
CODESYS Control Standard S and Beaglebone
Last updated: 2024-05-11

Trouble installing codesys 64 3.5.19.0 ^{CODESYS Forge talk (Thread)}
Trouble installing codesys 64 3.5.19.0
Last updated: 2024-06-19

Toradex and CODESYS and licensing ^{CODESYS Forge talk (Thread)}
Toradex and CODESYS and licensing
Last updated: 2025-10-21

CODESYS HMI and 2 monitors ^{CODESYS Forge talk (Thread)}
CODESYS HMI and 2 monitors
Last updated: 2026-01-13

Exploring Creative Ideas with CODESYS ^{CODESYS Forge talk (Thread)}
Exploring Creative Ideas with CODESYS
Last updated: 2026-09-24

Hilscher cards CoDeSys Control RTE ^{CODESYS Forge talk (Thread)}
Hilscher cards CoDeSys Control RTE
Last updated: 2026-10-23

Engineering 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Discussions about the CODESYS Development System, IEC programming, CODESYS Professional Developer Edition
Last updated: 2026-10-31

Codesys complains about matching versions ^{CODESYS Forge talk (Thread)}
Codesys complains about matching versions
Last updated: 2025-12-16

Safe Editor in codesys v3.5sp21p30 ^{CODESYS Forge talk (Thread)}
Safe Editor in codesys v3.5sp21p30
Last updated: 2026-03-12

Pilz PBRT Robot with CoDeSys ^{CODESYS Forge talk (Thread)}
Pilz PBRT Robot with CoDeSys
Last updated: 2026-05-10

Forge 🇬🇧 ^{CODESYS Forge talk (Discussion)}
Discussions about CODESYS Forge projects and features of the CODESYS Forge website
Last updated: 2026-06-15

Post by miodusy on CODESYS Control Standard S and Beaglebone ^{CODESYS Forge talk (Post)}
Hi, CODESYS Control Standard S + CODESYS Visualization L, CODESYS Control for Beaglebone 4.11.0.0, CODESYS V3.5 SP20 + (64-bit) I have problem that license manager say that this device is not supported when i try active whole license. When I select only runtime and communication it is go next step, but then I no have license on in Visualistion section, all of rest of software metric licese is ok(IO, Istances of com et, code size etc.). Thanks!
Last updated: 2024-05-11

Post by maldus512 on How to adapt Codesys Control SL to custom board ^{CODESYS Forge talk (Post)}
Hello everyone, I have been given the task to develop I/O drivers for a custom made, Linux based board to allow for Codesys applications to run and control the hardware. I have successfully installed Codesys Control SL for ARM/Linux and tested it with a simple demo application. Now I should start interfacing the runtime to the actual hardware; I should be able to interact with 2 RS485 serial ports, a few GPIOs and an I2C port, all of which already have the corresponding /dev/ interface in the Linux system. I am having trouble understanding how it should be approached. I have found sporadic references that fail to lead to a really comprehensive documentation. For example: The store page (https://store.codesys.com/en/codesys-control-for-linux-arm-sl-1.html#options) mentions a "runtime package" that should allow "Integration of existing C code" and "Usage of local I/Os", which seems exactly what I need to interact with custom peripherals. I have found no further reference to Codesys-C interpop. The Codesys Help page for the runtime package has a page on the "Development of Drivers" (https://content.helpme-codesys.com/en/CODESYS%20Control/rtsllinuxrbpdriverdevelopment.html) that suggests to either "Implement a function block" or "Implement I/O drivers". Those in turn lead to this page (https://forge.codesys.com/drv/io-drivers/doc/Generic/) which describes briefly an XML schema to describe new devices; unfortunately, it doesn't mention what to do with such a description (i.e. how does the runtime know about it) or how it is in any way connected to the actual hardware. Could anyone give me some pointers? I should also mention I have no prior experience with Codesys, so maybe I'm missing an obvious answer.
Last updated: 2024-08-09

Post by mondinmr on Patched Wine packages for Ubuntu and CODESYS 3.5 ^{CODESYS Forge talk (Post)}
I have now published Ubuntu amd64 packages of my patched Wine build for CODESYS, targeting Ubuntu 22.04, 24.04, 26.04 and 26.10. The packages are based on Wine 11.20 and include all five compatibility patches covering NCrypt, thread suspension, security tokens, service tokens and local WMI marshalling. Both 32-bit and 64-bit Windows applications are supported through WoW64. In my working environment, CODESYS 3.5 SP21 successfully compiled and went online with a very complex project containing hundreds of thousands of lines of code and extensive use of polymorphism. PPA and installation All four binary builds have completed successfully and are now published and available through APT. Wine ADV for CODESYS PPA sudo add-apt-repository ppa:mondinmr/wine-adv sudo apt update sudo apt install wine-adv The runtime installs under /opt/wine-adv and provides dedicated commands, allowing it to coexist with your existing Wine installation. For example, to launch CODESYS from an existing dedicated prefix: WINEPREFIX="$HOME/.wine.codesys" wine-adv \ 'C:\Program Files\CODESYS 3.5.21.30\CODESYS\Common\CODESYS.exe' Adjust the executable path to match your installed version. Use the same WINEPREFIX when running the CODESYS installer or installing its prerequisites. The package contains the patched Wine runtime. CODESYS and its required Microsoft .NET components must be installed separately inside the prefix. Source code, patches and packaging are available on the project page. This is an experimental community build. Feedback and test results from other users are welcome! CODESYS Installer and CodeMeter licensing are also working in my setup. For CodeMeter, I use the native Linux CodeMeter runtime, while the Windows applications run under the patched Wine build.
Last updated: 2026-10-31

Sort by relevance or date