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
I am working with the following:
- Codesys V3.5 SP17 Patch 3 + (64-bit)
- 4.2.0.0 runtime
- Raspberry Pi 4 compute and standard IO board using fresh image of raspbian "bullseye"
The only thing that I've noticed that seems a bit off is when I start the runtime in Codesys I get the following message prompt:
"Standard Output: cat: /sys/devices/virtual/bcm2708_vcio/vcio/dev: No such file or directory"
This message may be completed unrelated to my connection issue; not sure.
To describe my connection issue in more detail:
I can start and stop the runtime just fine from my engineering environment of Codesys. However, I have only been able to connect to the Pi immediately after starting the runtime. Otherwise I get the message "No device is responding to the scan request"
Another interesting issue is that if I start the runtime then immediately connect to to the pi in the Device communication settings this connection doesn't last very long. I would say maybe 10 seconds elapse and I lose connection to the Pi. On top of that I notice that my EtherCAT master must also be losing connection because my slave device throws an error that it lost comms with the EtherCAT master.
Any thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can also re-create these exact symptoms using a Pi 4B+ too. My Pi 4B+ is running the exact same Raspbian OS as well. I start the runtime, connect to the pi, code runs for about 10 seconds then I lose connection.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks! I suspected as much... I will try rolling back to an older Raspbian build. Any suggestions on a stable build? I was using "Buster" in the past.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just as eschwellinger posted the issue for me was that I was using the latest build of the Raspberry Pi OS with the current Codesys runtime build. Just downgrade the Raspberry Pi OS to Buster and you should be fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just as eschwellinger posted the issue for me was that I was using the latest build of the Raspberry Pi OS with the current Codesys runtime build. Just downgrade the Raspberry Pi OS to Buster and you should be fine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello All!
First post here so be kind...
I am working with the following:
- Codesys V3.5 SP17 Patch 3 + (64-bit)
- 4.2.0.0 runtime
- Raspberry Pi 4 compute and standard IO board using fresh image of raspbian "bullseye"
The only thing that I've noticed that seems a bit off is when I start the runtime in Codesys I get the following message prompt:
"Standard Output: cat: /sys/devices/virtual/bcm2708_vcio/vcio/dev: No such file or directory"
This message may be completed unrelated to my connection issue; not sure.
To describe my connection issue in more detail:
I can start and stop the runtime just fine from my engineering environment of Codesys. However, I have only been able to connect to the Pi immediately after starting the runtime. Otherwise I get the message "No device is responding to the scan request"
Another interesting issue is that if I start the runtime then immediately connect to to the pi in the Device communication settings this connection doesn't last very long. I would say maybe 10 seconds elapse and I lose connection to the Pi. On top of that I notice that my EtherCAT master must also be losing connection because my slave device throws an error that it lost comms with the EtherCAT master.
Any thoughts?
I can also re-create these exact symptoms using a Pi 4B+ too. My Pi 4B+ is running the exact same Raspbian OS as well. I start the runtime, connect to the pi, code runs for about 10 seconds then I lose connection.
yes, since release from 28.1 Bulleye either downgrade to older version of the OS or wait til 4.4.0.0 release of the runtime end of February.
Thanks! I suspected as much... I will try rolling back to an older Raspbian build. Any suggestions on a stable build? I was using "Buster" in the past.
Hi,
Can you solve this problem? If you can solve it, can you help me?
Just as eschwellinger posted the issue for me was that I was using the latest build of the Raspberry Pi OS with the current Codesys runtime build. Just downgrade the Raspberry Pi OS to Buster and you should be fine.
Just as eschwellinger posted the issue for me was that I was using the latest build of the Raspberry Pi OS with the current Codesys runtime build. Just downgrade the Raspberry Pi OS to Buster and you should be fine.
Thank you, i solved too. :)
now 4.4.0.0 is released...just update to it (use the CODESYS installer)
Last edit: eschwellinger 2022-03-01
Hello eschwellinger,
I'm having trouble upgrading. Recieve this error message (se picture attached). Any suggestions ?
I have now solved this issue, so you can just ignore my comment :-)