Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
hi,
in my case this works like charm.
Could you check if predictcable network names are enabled?
This should be turned of under raspi-config .. you could start the plc manually by:
sudo /etc/init.d/codesyscontrol stop
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg
open second CLI
tail -f /tmp/codesyscontrol.log
for Multicore you need to use:
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg
to have detailed information.
BR
Edwin
Last edit: eschwellinger 2020-07-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hi i have same problem, pi 4b.
i have tried both full and lite version on your link(https://www.raspberrypi.org/downloads/raspberry-pi-os/). without updating.
codesys 3.5.16.10
tried both standard and multicore runtime.
codesyscontrol. disappears from "top" after 10 sec every time.
i got it working by :
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2
Last edit: muzel 2020-09-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the latest version installed from the same link. If I install the runtime, it will work. If I execute the following, then the kernel gets updated and the runtime will not run anymore.
sudoapt-getupgrade-y
When I look at the logs, it seems that the licensing parameters need to be updated as it thinks that the newly updated system is no longer a Raspberry Pi.
I can confirm this. I'm having exactly the same situation. The Codesys runtime stops within 10 seconds after starting it. I was using the trial license (2h trial).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes agree, but only PI4 seems to have this issue,
the workaround is:
just use 2020-05-27-raspios-buster-armhf.img without apply these updates.
Till this will be fixed ( hopefully in Patch2)
BR
Edwin
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Edwin,
i download and flash an sd with the image [ ] 2020-05-27-raspios-buster-armhf.zip
i installed it, everything seems ok,but the issue persist, after few second raspi stop the connection. What's wrong ?
Thanks,
BR
Matteo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I ran this command on my compute module 3 but it skipped the kernel. I'm still seeing the runtime stop after ~30s. Is there another way to implement this fix? I'm not very experienced when it comes to managing raspberry Pi's yet so any assistance would be much appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was facing same issue and decided to update to the latest RPi OS that's based on Buster (https://www.raspberrypi.org/downloads/raspberry-pi-os/). CoDeSys runtime 16/16.10 works great.
bego, normally you can reinstall the license with the restore-function. If it does not work (happened to me once), look at this doc: https://faq.codesys.com/pages/viewpage.action?pageId=1310825
Backing up the license update file from “c:\Program Data\CODESYS\Licenses\license ticket number” (on the PC where you have licensed the PI)
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi same problem form me:
RPI 4 with last raspberrypi OS and before i see this post i try the classic command:
sudoapt-getupdatesudoapt-getupgrade
without any benefit, always the same: it is not online on the network and if I do the RUN command I see it for about 10 seconds and then it disappears on its own.
Hopefully it will be fixed soon
thank you
Last edit: elsabz 2020-08-04
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 3 B + with a codesys license,
that works fine, I haven't updated, just in case.
for the raspberry pi 4 , I use it just for tests actually ,
so I will wait for a patch from codesys.
thank you
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i have a strange problem. I have 6 Raspberry Pi's 4B and all are running same Software. all of them have licences. Strangely 3 RPi stops after 2 hours.
Starting Log entry is :-
No Runtime License - running in Demo Mode (~120 minutes)
Though license Manager states also that they have multicore licenses.
i tried following
-RPi updates install
-Codesys Package reinstall
-License reinstall
please help me.
regards,
baldeep
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
are you working with images? ( to distribute the version to all this PI's?
Check the content of the cmact_licenses directory with the CODESYS file browser.
There should be only on license in there.. expect that you have two ( one from the original PI - now broken license the other correct licensed) But this does not work then.
If you work with sd images keep in mind that you need to delete this directory restart the Pi and license then this PI after doing this.
Maybe I'm wrong but you need to check.
Regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can anyone show me, if it's even currently possible, how to setup my raspberry 4 4GB to run latest Codesys runtime and USB boot. I specifically bought a SSD for stability and reliability of the application that I'm developing. I had SD cards die on me several times.
Thank you, for any kind of support.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately I don't think you'll be able to use a version of Rasbian that supports and works correctly with USB boot on the Pi 4 until the new Codesys update is out.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
what worked for me is:
Setup the Pi so that it is able to boot from SSD (with the bootloader that is stable for USB-boot).Keep the SD-card with the newer image.
Then you put the last image with 4.19 Kernel (should be "2020-05-27-raspios") on SSD.
The last step is to copy the .dat and .elf files from the SD-card to the boot partition on SSD and displace the files that are already there.
Don't do apt-get upgrade!!!
👍
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Then I downloaded the "2020-05-27-raspios" image. Again, I used Raspberry Pi imager to burn the image to the SSD.
The, I extracted the .elf and .dat files form the SD, copied them over on the SSD and voilà!
Thanks again! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hate to say, but now in 2023 this issue is back again.
Latest Raspbian on Pi4B will kill the service after 30 seconds with "ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-6, 0x00000BB8, 0xFFFFFFFB)"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today, I've updated the Raspberry Pi OS with the following commands:
The CODESYS runtime exits within seconds. I have tried the same on another build with similar results.
more posts ...
hi,
in my case this works like charm.
Could you check if predictcable network names are enabled?
This should be turned of under raspi-config .. you could start the plc manually by:
sudo /etc/init.d/codesyscontrol stop
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg
open second CLI
tail -f /tmp/codesyscontrol.log
for Multicore you need to use:
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg
to have detailed information.
BR
Edwin
Last edit: eschwellinger 2020-07-21
Edwin,
Predictable network interface names is already disabled.
On the Raspberry Pi 4B, this is my output:
In the second cli, I get the following:
Hi,
which version was installed before you apply these update command?
Could just install current version:
https://www.raspberrypi.org/downloads/raspberry-pi-os/
I'm pretty sure this will work then.
Best Regards
Edwin
hi i have same problem, pi 4b.
i have tried both full and lite version on your link(https://www.raspberrypi.org/downloads/raspberry-pi-os/). without updating.
codesys 3.5.16.10
tried both standard and multicore runtime.
codesyscontrol. disappears from "top" after 10 sec every time.
i got it working by :
sudo rpi-update e1050e94821a70b2e4c72b318d6c6c968552e9a2
Last edit: muzel 2020-09-01
Edwin,
I have the latest version installed from the same link. If I install the runtime, it will work. If I execute the following, then the kernel gets updated and the runtime will not run anymore.
When I look at the logs, it seems that the licensing parameters need to be updated as it thinks that the newly updated system is no longer a Raspberry Pi.
This is after updating:
This is before updating with the same image in the link.
OK we will check...
what does:
cat /proc/cpuinfo
report?
I can confirm this. I'm having exactly the same situation. The Codesys runtime stops within 10 seconds after starting it. I was using the trial license (2h trial).
This issue still persists in version 3.5.16.10 as well.
I second this, and the SysEthernet library is missing for 3.5.16.10 as well.. It keeps reporting download failed.
yes agree, but only PI4 seems to have this issue,
the workaround is:
just use 2020-05-27-raspios-buster-armhf.img without apply these updates.
Till this will be fixed ( hopefully in Patch2)
BR
Edwin
Hi Edwin,
i download and flash an sd with the image [ ] 2020-05-27-raspios-buster-armhf.zip
i installed it, everything seems ok,but the issue persist, after few second raspi stop the connection. What's wrong ?
Thanks,
BR
Matteo
Just use the newest Raspberry PI OS and 3.5.16.20 runtime...?!?
see now that my codesys downloaded on 23 @19.55 was 3.5.16.10
Downloading last version,
thank you,
BR
...even more important is to have the 3.5.16.20 Raspberry Pi package ;-)😉
it works, ;-)
Thank you,
This issue also happens on RPi 3B+ compute module after 30-ish seconds. I hope it's because of realtime kernel:
$ uname -a
Linux testPi 4.19.71-rt24-v7+ #2 SMP PREEMPT RT Mon Apr 13 17:34:00 PDT 2020 armv7l GNU/Linux
$ sudo service codesyscontrol status
● codesyscontrol.service - LSB: Prepares and starts codesyscontrol
Loaded: loaded (/etc/init.d/codesyscontrol; generated; vendor preset: enabled)
Active: active (exited) since Thu 2020-07-23 23:18:58 PDT; 35s ago
Docs: man:systemd-sysv-generator(8)
Process: 32763 ExecStop=/etc/init.d/codesyscontrol stop (code=exited, status=0/SUCCESS)
Process: 319 ExecStart=/etc/init.d/codesyscontrol start (code=exited, status=0/SUCCESS)
$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
NAME="Raspbian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
VERSION_CODENAME=stretch
ID=raspbian
ID_LIKE=debian
3.5.16.10 user here as well. No luck with getting it to run for more than 10 seconds, even with a purchased license. RPi4 B 8GB version.
Last edit: tl140 2020-07-30
Sure just use the workaroud..
The last kernel version that runs the runtime from the list of commits below is 4.19.118.
https://github.com/Hexxeh/rpi-firmware/commits/master
If you have devices already provisioned and/or deployed out in the field, you can run the following command to revert to the last working revision:
I ran this command on my compute module 3 but it skipped the kernel. I'm still seeing the runtime stop after ~30s. Is there another way to implement this fix? I'm not very experienced when it comes to managing raspberry Pi's yet so any assistance would be much appreciated.
I was facing same issue and decided to update to the latest RPi OS that's based on Buster (https://www.raspberrypi.org/downloads/raspberry-pi-os/). CoDeSys runtime 16/16.10 works great.
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 5.4.51-v7+ #1333 SMP Mon Aug 10 16:45:19 BST 2020 armv7l GNU/Linux
seems to be an different issue,
check:
sudo /etc/init.d/codesyscontrol stop
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol.bin -d /etc/CODESYSControl.cfg
open second CLI
tail -f /tmp/codesyscontrol.log
for Multicore you need to use:
cd /var/opt/codesys
sudo /opt/codesys/bin/codesyscontrol_armv7l_raspberry.bin -d /etc/CODESYSControl.cfg
we need this information
Hi, I have the same problem after the update of the OS.
Maybe a noob questions, when I re-image the pi will my bought licence (soft container) be lost?
bego, normally you can reinstall the license with the restore-function. If it does not work (happened to me once), look at this doc:
https://faq.codesys.com/pages/viewpage.action?pageId=1310825
Backing up the license update file from “c:\Program Data\CODESYS\Licenses\license ticket number” (on the PC where you have licensed the PI)
Hi same problem form me:
RPI 4 with last raspberrypi OS and before i see this post i try the classic command:
without any benefit, always the same: it is not online on the network and if I do the RUN command I see it for about 10 seconds and then it disappears on its own.
Hopefully it will be fixed soon
thank you
Last edit: elsabz 2020-08-04
Hello ,
I have the same problem after the update of the raspberry pi 4 ....
...use the workaround.😉
I have a raspberry pi 3 B + with a codesys license,
that works fine, I haven't updated, just in case.
for the raspberry pi 4 , I use it just for tests actually ,
so I will wait for a patch from codesys.
thank you
Any fix expectable? My Pi is running on ssd, not booting with the old versions.
Edit: Get it booting now. Fix would be still nice to keep the OS up to date.
Last edit: dav3 2020-08-23
It should be noted that the official Raspberry Pi OS release is now at kernel 5.4 (Release date: 2020-08-20).
https://www.raspberrypi.org/downloads/raspberry-pi-os/
The older version does not seem to be available now.
Here they are: https://downloads.raspberrypi.org/raspbian/images/
https://downloads.raspberrypi.org/raspios_armhf/images/
With the new software (2020-08-20) my pi 3 B + without a
codesys license, is running.
Jonte
Related
Talk.ru: 1
This just affects the Raspberry Pi 4B at the moment, I have tried the new Raspberry Pi OS image and I ran into the same issue.
If I revert to the older kernel in this build, via the method described in the link below, the runtime software runs without issue.
https://forge.codesys.com/forge/talk/Runtime/thread/4d43247a3a/#9bcd
Last edit: sumkrnboy 2020-08-25
Dear Helpers,
i have a strange problem. I have 6 Raspberry Pi's 4B and all are running same Software. all of them have licences. Strangely 3 RPi stops after 2 hours.
Starting Log entry is :-
No Runtime License - running in Demo Mode (~120 minutes)
Though license Manager states also that they have multicore licenses.
i tried following
-RPi updates install
-Codesys Package reinstall
-License reinstall
please help me.
regards,
baldeep
are you working with images? ( to distribute the version to all this PI's?
Check the content of the cmact_licenses directory with the CODESYS file browser.
There should be only on license in there.. expect that you have two ( one from the original PI - now broken license the other correct licensed) But this does not work then.
If you work with sd images keep in mind that you need to delete this directory restart the Pi and license then this PI after doing this.
Maybe I'm wrong but you need to check.
Regards
Dear Mr. Schwellinger,
your hint was exactly correct.
Sincere Regards and Thanks a lot
Baldeep Singh
Hello everyone.
Can anyone show me, if it's even currently possible, how to setup my raspberry 4 4GB to run latest Codesys runtime and USB boot. I specifically bought a SSD for stability and reliability of the application that I'm developing. I had SD cards die on me several times.
Thank you, for any kind of support.
Unfortunately I don't think you'll be able to use a version of Rasbian that supports and works correctly with USB boot on the Pi 4 until the new Codesys update is out.
Hi,
what worked for me is:
Setup the Pi so that it is able to boot from SSD (with the bootloader that is stable for USB-boot).Keep the SD-card with the newer image.
Then you put the last image with 4.19 Kernel (should be "2020-05-27-raspios") on SSD.
The last step is to copy the .dat and .elf files from the SD-card to the boot partition on SSD and displace the files that are already there.
Don't do apt-get upgrade!!!
Hi,
Where can i get the 2020-05-27 raspios?
https://downloads.raspberrypi.org/raspios_armhf/images/
https://downloads.raspberrypi.org/raspios_lite_armhf/images/
thanks
Hello @dav3.
Thank you, so much! This procedure works. I used Raspberry Pi imager to get latest OS. I put that on SD, did update, upgrade and stable bootloader using this guide: https://www.jeffgeerling.com/blog/2020/im-booting-my-raspberry-pi-4-usb-ssd
Then I downloaded the "2020-05-27-raspios" image. Again, I used Raspberry Pi imager to burn the image to the SSD.
The, I extracted the .elf and .dat files form the SD, copied them over on the SSD and voilà!
Thanks again! :)
Do you have any news with repair this? eschwellinger wrote that it should be in path 2 but it looks that is still same.
Yes, the news is that it is working with the recently released patch 2 (CODESYS V3.5 SP16 Patch 2).
Hate to say, but now in 2023 this issue is back again.
Latest Raspbian on Pi4B will kill the service after 30 seconds with "ooops... this runtime was built for RASPBERRYPI. Hardware version or firmware version not supported! (-6, 0x00000BB8, 0xFFFFFFFB)"
Hello all,
Same here with latest Raspbian on Pi5 (Bookworm) and Pi64 SL Runtime 4.10.0.0 and SDK 3.5.19.2.
Any suggestions?
Many thanks!
Fabian
We are working on a fix for 4.11.0.0 version.
Last edit: eschwellinger 2023-12-22