I have a Raspberry Pi 4 we have been using for years to run CODESYS for development purposes.
I recently have had to re-install the OS (Raspberry OS lite). The only change to the default configuration is not creating the "pi" user during install. I (apparently successfully) installed the 4.10.0.0 control on the Raspberry Pi. We have licences on a dongle.
I am able to start the control. systemctl status shows it as running for a little while (exactly, precisely 30 seconds as per my tests, every time), then it becomes exited. I can restart the control, and the same thing happens again. Every time.
In the brief moments it is running, I can log in to the PLC. Working fast and restarting the control many times, I have been able to configure users. I have been able to download my application. I have been able to run the application, and stop on a breakpoint. I have been able to connect with the licence manager and confirm the dongle is detected and licences are listed as OK. I see nothing wrong until the service just exits.
I have found nothing in the logs. It is like the runtime just terminates with no error code or message after exactly 30 seconds.
Any help would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
4.11 appears to solve the problem. Thanks for your help.
I had first installed the 64-bit version of RPiOS, but looking at various posts and the product's page on the store which only lists 32-bit compatibility, I downgraded to the 32-bit version. I did this before trying 4.11, and it did not solve the problem. Thus my working system is 32-bit, and I am wondering if I can go back to 64-bit or not.
An 64-bit OS is not listed as compatible on the store's web page, but when installing there actually is a 64-bit version listed (automatically chosen when installing on 64-bit, but otherwise greyed out). Is 64-bit supported and the website is out-of-date, or is that some kind of work-in-progress?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have been using the Codesys Control for Rasberry Pi for several years in many installations without any major issues. But during summer the problem mentioned above has blocked further deliveries. We have made some minor upgrades to the application but I do not really see why that should have any impact.
HW is Raspberry Pi 4B, 2GB
OS is Booworm Lite
Codesys control is version 4.15 (have just installed a few systems lately with this version)
The system boots OK but after exactly 30 seconds Codesys is shut down and becomes unreachable.
We have tested several different combinations:
Upgrade of the Codeys Control to 4.16
Loading different Codesys applications
Changing to 4GB version of the Raspberry Pi
One of the test applications together with the 4GB HW seems to be stable, but all other combinations fails.
Any suggestion what we can do to resolve is appreciated - this is a real business blocker now.
Rgds
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
in case you are using latest hw revision, there have been added some mac adresses - for the 4.17.0.0
release this might solve it.
If not we need to investigate deeper.
If it is application related you need to check the plclogger.
Last edit: eschwellinger 2025-09-02
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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...
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
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.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem has been resolved. Two findings are described below for future reference.
The new RPi hw delivered during August 2025 has a MAC address from a new vendor series that is not supported by old runtimes. 4.17.0.0 or above is required.
4.17.0.0 does not pick up the correct architecture during installation and aarch64 has to be manually configured either in the GUI under operations or in /etc/codesyscontrol/CODESYSControl_User.cfg under the [CmpRasPi] section.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a Raspberry Pi 4 we have been using for years to run CODESYS for development purposes.
I recently have had to re-install the OS (Raspberry OS lite). The only change to the default configuration is not creating the "pi" user during install. I (apparently successfully) installed the 4.10.0.0 control on the Raspberry Pi. We have licences on a dongle.
I am able to start the control.
systemctl statusshows it as running for a little while (exactly, precisely 30 seconds as per my tests, every time), then it becomesexited. I can restart the control, and the same thing happens again. Every time.In the brief moments it is running, I can log in to the PLC. Working fast and restarting the control many times, I have been able to configure users. I have been able to download my application. I have been able to run the application, and stop on a breakpoint. I have been able to connect with the licence manager and confirm the dongle is detected and licences are listed as OK. I see nothing wrong until the service just exits.
I have found nothing in the logs. It is like the runtime just terminates with no error code or message after exactly 30 seconds.
Any help would be appreciated.
if you use Bookworm uodate to 4.11.0.0 version please.
4.11 appears to solve the problem. Thanks for your help.
I had first installed the 64-bit version of RPiOS, but looking at various posts and the product's page on the store which only lists 32-bit compatibility, I downgraded to the 32-bit version. I did this before trying 4.11, and it did not solve the problem. Thus my working system is 32-bit, and I am wondering if I can go back to 64-bit or not.
An 64-bit OS is not listed as compatible on the store's web page, but when installing there actually is a 64-bit version listed (automatically chosen when installing on 64-bit, but otherwise greyed out). Is 64-bit supported and the website is out-of-date, or is that some kind of work-in-progress?
it is supported for sure, send me the link the outdated webpage please.
https://us.store.codesys.com/codesys-control-for-raspberry-pi-sl.html
Quoted from the "additional requirements" section :
We have been using the Codesys Control for Rasberry Pi for several years in many installations without any major issues. But during summer the problem mentioned above has blocked further deliveries. We have made some minor upgrades to the application but I do not really see why that should have any impact.
HW is Raspberry Pi 4B, 2GB
OS is Booworm Lite
Codesys control is version 4.15 (have just installed a few systems lately with this version)
The system boots OK but after exactly 30 seconds Codesys is shut down and becomes unreachable.
We have tested several different combinations:
Upgrade of the Codeys Control to 4.16
Loading different Codesys applications
Changing to 4GB version of the Raspberry Pi
One of the test applications together with the 4GB HW seems to be stable, but all other combinations fails.
Any suggestion what we can do to resolve is appreciated - this is a real business blocker now.
Rgds
in case you are using latest hw revision, there have been added some mac adresses - for the 4.17.0.0
release this might solve it.
If not we need to investigate deeper.
If it is application related you need to check the plclogger.
Last edit: eschwellinger 2025-09-02
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...
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 upgradeI still get the same errorReverting back to 4.15.00 works fine:
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.
I now tried to install 4.17.0.0 on a fully clean installations:
sudo apt update && sudo apt full-upgradeLog output:
If I read the log correctly the control is actually installed but cannot start.
I'm running out of ideas how to proceeed now, any suggestions are welcome.
let me check - had a similar case today
The problem has been resolved. Two findings are described below for future reference.
aarch64has to be manually configured either in the GUI under operations or in/etc/codesyscontrol/CODESYSControl_User.cfgunder the[CmpRasPi]section.