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.
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