Hi everyone!
I'm trying to test the Codesys control on a Raspberry PI 4 with 2 Gb of RAM.
My problem is that it is only running for a few seconds.
If anyone had a similar problem please help me.
Thank you!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you eschwellinger!
Please! When will it be released?
I already tried several alternatives to solve. Of course I'm not an expert on linux, raspberry or codesys but I'm already feeling like an idiot.
Hi Edwin,
We are using 3.5SP16Patch2, but we still have this problem. It is stop after 30 seconds.(code=exited, status=0/SUCCESS) How can we solve this? Is there any way to debug what is the cause of this?
Thank you in advance.
Kind regards,
Januar
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Everyone,
I have pi4 8gb and codesys raspberry pi control runtime is stopping after ten seconds or so. I did downgrade with the command as follow, and it worked fine. I will be checking if there is new version, and I will keep it with this verion, won't upgrade. I suggest you better do this for the new patch release.
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
Hi everyone,
I had the same issue. The downgrade solved the problem but now I can't use the Pi Touchscreen anymore. After updateing with rpi-update the touchscreen works again and the CODSYS runtime stops again after 20-30 seconds. I checked the log but the last entry was "CODESYS control ready". Anyone having an idea what elso to try ?
regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone!
I'm trying to test the Codesys control on a Raspberry PI 4 with 2 Gb of RAM.
My problem is that it is only running for a few seconds.
If anyone had a similar problem please help me.
Thank you!
Hi kodiac,
see this thread, in particular the post with the solution https://forge.codesys.com/forge/talk/Runtime/thread/4d43247a3a/#9bcd
Cheers, Ian
Thanks i-campbell!
I will try this.
Last edit: kodiac 2020-09-10
...and will be solved with 3.5SP16Patch2 release.
Thank you eschwellinger!
Please! When will it be released?
I already tried several alternatives to solve. Of course I'm not an expert on linux, raspberry or codesys but I'm already feeling like an idiot.
Regards,
JosΓ© Carlos Rago
Hi Edwin,
We are using 3.5SP16Patch2, but we still have this problem. It is stop after 30 seconds.(code=exited, status=0/SUCCESS) How can we solve this? Is there any way to debug what is the cause of this?
Thank you in advance.
Kind regards,
Januar
use 4.0.1.0 release, then it will work..
BR Edwin
Ok, Thank you Edwin.
Hi,
3.5SP16Patch2 is scheduled for 24th September
Thank you!
Hi Everyone,
I have pi4 8gb and codesys raspberry pi control runtime is stopping after ten seconds or so. I did downgrade with the command as follow, and it worked fine. I will be checking if there is new version, and I will keep it with this verion, won't upgrade. I suggest you better do this for the new patch release.
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2
regards
selcuk_e
Thank you seculke!
I don't know if is the same but Codesys people says that the new release of runtime in 24th September will correct this problem
Regards
i had the same issue and got it solved with :
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2
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
Hi everyone,
I had the same issue. The downgrade solved the problem but now I can't use the Pi Touchscreen anymore. After updateing with rpi-update the touchscreen works again and the CODSYS runtime stops again after 20-30 seconds. I checked the log but the last entry was "CODESYS control ready". Anyone having an idea what elso to try ?
regards
Hi markant75,
@eschwellinger Said :
This problem will be solved with 4.4.0.0 release end of February (24th)
@eschwellinger
will the new 4.4.0.0 work with the newest 5.10 kernel?
yes
@eschwellinger
Great! Do you know when this will be released?