Identifier ioConfigConnector not defined. CODESYS IDE V3.5SP6 corruption after installation of CODESYS IDE V3.5SP10 ^{CODESYS Forge talk (Thread)}
Identifier ioConfigConnector not defined. CODESYS IDE V3.5SP6 corruption after installation of CODESYS IDE V3.5SP10
Last updated: 2017-10-20

[HELP] Connecting Codesys v2.3 program with a Codesys HMI SL project in V3 ^{CODESYS Forge talk (Thread)}
[HELP] Connecting Codesys v2.3 program with a Codesys HMI SL project in V3
Last updated: 2021-10-18

Codesys sales and support. Is it true that Codesys wants to get more customers? ^{CODESYS Forge talk (Thread)}
Codesys sales and support. Is it true that Codesys wants to get more customers?
Last updated: 2023-07-03

how to convert library from CodeSys 2.3 to CodeSys 3.x ? ^{CODESYS Forge talk (Thread)}
how to convert library from CodeSys 2.3 to CodeSys 3.x ?
Last updated: 2026-04-29

Post by reinier-geers on License problem gateway ^{CODESYS Forge talk (Post)}
The hole setup is made by 3s. So its a comination of one not two. If Epis decide not to support extra licence whats then the funtion of providing an option with a single license ?? So the idee by 3s has a flod. Epis change the system to add the Stick. I send controller inc stick to Epis. On my software i can see the stick. An then you tel me i need a other license to use an license ?? Makes completly no sense. Codesys should be flexible but is not. I tried Delta. But has no HMI and has its own Codesys ?? Why ?? Then i tried Crist. The block there own system by a password. But dont know the password and cant switch it off. At the end the want me to pay for support to solve ther own made problem. So i send it al back. The extra license is adviced by 3s . Now a few month later still no working solution.
Last updated: 2024-05-01

Post by gunstr on CODESYS control on RPi starts, shortly runs, then exits ^{CODESYS Forge talk (Post)}
Thank you very much for the quick answer! The RPi hw were delivered last week so it's probably a resent version. I found an old scrapped board (2 years or so) with a broken GPIO that I tested with the same SD card image and with that board Codeys can run for the full 2h demo period without issues. Then I went back the the new board to test the 4.17.0.0 release but the installation fails... [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesyscontrol started [WARNING] Unable to detect Raspberry Pi Architecture. Setting armv6l as default, you can change this through the settings panel. [INFORMATION] Standard output: codesyscontrol stopped [ERROR] Expected exit value of command failed: expected 0, received 1 [WARNING] Error setting the Raspberry Pi Architecture [ERROR] Error installing codesyscontrol Do you have any idea what could be the reason? I'm using an OS image including Python drivers for LCD and some I/O:s from last year to keep things stable, but also after upgrading with sudo apt update && sudo apt upgrade I still get the same error Reverting back to 4.15.00 works fine: [INFORMATION] Standard output: create and install daemon [INFORMATION] Standard output: codesysedge started [INFORMATION] Successfully installed codesyscontrol [INFORMATION] Successfully started CODESYS Edge Gateway for Linux [INFORMATION] Successfully started CODESYS Control for Raspberry Pi SL but as before the Codesys services stops after 30 seconds. And I noticed that the Codesys control stops and is not reachable also if I have no application loaded.
Last updated: 2025-09-02

Post by kevinl on Weidmüller und u-OS bugs ^{CODESYS Forge talk (Post)}
Hallo zusammen Wir setzen mehrere Weidmüller UC20-WL2000 mit CODESYS Runtime und System-Bus ein und kämpfen seit einiger Zeit mit Problemen, für die wir bisher keine Ursache finden konnten. Aktuell beobachten wir zwei Phänomene: System-Bus Probleme Bei einer Anlage verlieren die I/O-Module sporadisch die Verbindung. Im Log erscheinen Meldungen wie: SLIO:CheckModule missing NotReachable Module Unplugged Nach diversen Updates (u-OS 2.7, aktuelle Runtime, aktuelles CODESYS) wurde das Verhalten eher schlechter statt besser. Anfangs traten die Fehler sporadisch auf, inzwischen funktioniert der System-Bus teilweise gar nicht mehr. Auch ein Downgrade auf eine ältere u-OS Version half nicht wirklich, aber ev ist es mit der aktuellen Runtime nicht kompatibel. Probleme nach Spannungsunterbruch / Neustart Mehrfach hatten wir bereits den Fall, dass eine Steuerung nach einem Spannungsunterbruch oder Neustart nicht mehr vollständig hochkommt. Teilweise startet die CODESYS Runtime nicht mehr (vermutlich aufgrund von Problemen mit Persistent-Daten), in einem aktuellen Fall ist zusätzlich das u-OS Backend nicht mehr erreichbar. Die Welcome-Seite erscheint noch, beim Login läuft der Request jedoch in einen 504 Gateway Timeout. Hardware: UC20-WL2000 u-OS 2.x System-Bus mit mehreren UR20 Modulen CODESYS Control SL Runtime Mich würde interessieren: Hat jemand ähnliche Erfahrungen mit UC20-WL2000 oder u-OS gemacht? Gibt es bekannte Probleme mit dem System-Bus? Gibt es Workarounds bezüglich Persistent-Daten oder Recovery nach Spannungsunterbruch? Hat jemand ähnliche 504-Fehler im u-OS Backend gesehen? Vielen Dank für jeden Hinweis.
Last updated: 2026-06-05

Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200 ^{CODESYS Forge talk (Thread)}
Problems connecting to Codesys 4.9.0.0 runtime on my Wago PFC200
Last updated: 2023-08-26

CODESYS Automation Server Connector for 3.5 SP11 ^{CODESYS Forge talk (Thread)}
CODESYS Automation Server Connector for 3.5 SP11
Last updated: 2023-08-30

Introductory short video series on PLC programming (CODESYS) ^{CODESYS Forge talk (Thread)}
Introductory short video series on PLC programming (CODESYS)
Last updated: 2023-08-28

Network Variable List in Codesys 3.5 on CAN ^{CODESYS Forge talk (Thread)}
Network Variable List in Codesys 3.5 on CAN
Last updated: 2023-08-05

How to read structure in CodeSys using pythong script? ^{CODESYS Forge talk (Thread)}
How to read structure in CodeSys using pythong script?
Last updated: 2017-10-09

Barcode-Reader O2I (TCP/IP) mit Codesys auslesen ^{CODESYS Forge talk (Thread)}
Barcode-Reader O2I (TCP/IP) mit Codesys auslesen
Last updated: 2018-04-01

Compiling CoDeSys project using the command line interface ^{CODESYS Forge talk (Thread)}
Compiling CoDeSys project using the command line interface
Last updated: 2021-01-27

CodeSys v3 Vendors/PLCs with C-Integration ^{CODESYS Forge talk (Thread)}
CodeSys v3 Vendors/PLCs with C-Integration
Last updated: 2018-03-05

General question about Codesys and control RTE ^{CODESYS Forge talk (Thread)}
General question about Codesys and control RTE
Last updated: 2020-01-27

Using ScriptEngine in C# for Creating Codesys Project ^{CODESYS Forge talk (Thread)}
Using ScriptEngine in C# for Creating Codesys Project
Last updated: 2019-06-24

Newbie questions regarding CodeSys V3 Modbus RTU ^{CODESYS Forge talk (Thread)}
Newbie questions regarding CodeSys V3 Modbus RTU
Last updated: 2016-06-09

Codesys Wago Going Online from Different Computer ^{CODESYS Forge talk (Thread)}
Codesys Wago Going Online from Different Computer
Last updated: 2022-12-15

Adding a CANBUS device on Codesys Control Linux SL ^{CODESYS Forge talk (Thread)}
Adding a CANBUS device on Codesys Control Linux SL
Last updated: 2022-05-25

CODESYS Control Not Showing Up in Devices ^{CODESYS Forge talk (Thread)}
CODESYS Control Not Showing Up in Devices
Last updated: 2023-01-02

Datenaustausch zwischen mehreren Codesys-SPS in Echtzeit ^{CODESYS Forge talk (Thread)}
Datenaustausch zwischen mehreren Codesys-SPS in Echtzeit
Last updated: 2022-11-18

Codesys 2.3 Größere Texte, Strings in Visu darstellen ^{CODESYS Forge talk (Thread)}
Codesys 2.3 Größere Texte, Strings in Visu darstellen
Last updated: 2010-12-10

CoDeSys Beipiel mit Balluff Ident-System gesucht. ^{CODESYS Forge talk (Thread)}
CoDeSys Beipiel mit Balluff Ident-System gesucht.
Last updated: 2009-02-03

Importing variable list from Excel into Codesys ^{CODESYS Forge talk (Thread)}
Importing variable list from Excel into Codesys
Last updated: 2018-03-21

Sort by relevance or date