On the latest Raspberry Pi OS 32-bit image with updates performed and kernel as shown below, CODESYS Control for Raspberry PI runtime exits after about 30 seconds.
Linux raspberrypi 5.10.92-v7l+ #1514 SMP Mon Jan 17 17:38:03 GMT 2022 armv7l
Maybe I'm wrong, but I think you need a fresh install, not an update. Even Rasperrypi.org recommend not to update the distribution in case you update to bullseye. Could you try this.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
The solution with the "corrected file" from the german forum is working but after a certain random time the runtime stop (waiting wheel on the WebVisu) and the connection to Codesys is stoped (if login). I still can "talk" to the Raspi via PuTTY so is not a network problem.
If I run the command
sudo service codesyscontrol restart
then all come back live again.
Any suggestions...?
Last edit: yann2021 2022-02-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello
I had the same issue with runtime :
ii codesyscontrol 4.2.0.0 armhf codesyscontrol based on SDK 3.5.17.10 , from Fri Aug 27 12:04:56 CEST 2021 [121], Release build
On the latest Raspberry Pi OS 32-bit image with updates performed and kernel as shown below, CODESYS Control for Raspberry PI runtime exits after about 30 seconds.
Linux raspberrypi 5.10.92-v7l+ #1514 SMP Mon Jan 17 17:38:03 GMT 2022 armv7l
Related
Talk.ru: 1
more posts ...
Maybe I'm wrong, but I think you need a fresh install, not an update. Even Rasperrypi.org recommend not to update the distribution in case you update to bullseye. Could you try this.
This was a fresh install.
I performed the following:
After the above commands, the runtime terminates.
fresh install is flash an empty sd card with bullseye from my point of view or do you mean you update bullseye?
Last edit: eschwellinger 2022-01-22
With a fresh install of the latest Raspberry Pi OS image,
https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2021-11-08/2021-10-30-raspios-bullseye-armhf-lite.zip
it will work fine and run, however, after running the previously mentioned update and upgrade commands, it it fail to load after restart. This behavior was observed in both the Raspberry Pi 3B as well as 4B (4GB).
think this change in this scrpit should solve it:
https://forge.codesys.com/forge/talk/Deutsch/thread/b03a511b8c/?limit=25#467a
(/opt/codesys/scripts/init-functions)
Last edit: eschwellinger 2022-01-22
That fixed it. When can we expect an official fixed release?
Hello,
I think I have the same problem. What should I do after I downloaded the script file from the German topic ?
Many thanks for your help.
Last edit: yann2021 2022-01-27
Download the file and overwrite the following file:
/opt/codesys/scripts/init-functions
Restart the CODESYS Control service:
sudo service codesyscontrol restart
After 30 seconds or so, check the status of the service to see that it is still running:
sudo service codesyscontrol status
Hello "sumkrnboy",
Many thanks, now I can again see my devices when I click on the "Scan Network" button.
Hello,
The solution with the "corrected file" from the german forum is working but after a certain random time the runtime stop (waiting wheel on the WebVisu) and the connection to Codesys is stoped (if login). I still can "talk" to the Raspi via PuTTY so is not a network problem.
If I run the command
sudo service codesyscontrol restart
then all come back live again.
Any suggestions...?
Last edit: yann2021 2022-02-01
check the plclogger for more information
cat/tmp/codesyscontrol.log
I fear there is maybe an problem with latest bullseye from 2022-01-28 release
Last edit: eschwellinger 2022-02-01
sudo ln -sf /dev/vcio /dev/char_dev
no need to override the init-functions file after that
You have to do this after each restart, or add the command to /etc/rc.local
Hello
I had the same issue with runtime :
ii codesyscontrol 4.2.0.0 armhf codesyscontrol based on SDK 3.5.17.10 , from Fri Aug 27 12:04:56 CEST 2021 [121], Release build
Solution:
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2