Connection drops with Raspberry Pi

cbro
2022-02-05
2022-03-02
  • cbro - 2022-02-05

    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?

     
  • cbro - 2022-02-05

    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.

     
  • eschwellinger

    eschwellinger - 2022-02-07

    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.

     
  • cbro - 2022-02-07

    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.

     
  • rsudecetin - 2022-03-01

    Hi,
    Can you solve this problem? If you can solve it, can you help me?

     
  • cbro - 2022-03-01

    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.

     
  • cbro - 2022-03-01

    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.

     
    • rsudecetin - 2022-03-02

      Thank you, i solved too. :)

       
  • eschwellinger

    eschwellinger - 2022-03-01

    now 4.4.0.0 is released...just update to it (use the CODESYS installer)

     

    Last edit: eschwellinger 2022-03-01
    • tobzi - 2022-03-01

      Hello eschwellinger,

      I'm having trouble upgrading. Recieve this error message (se picture attached). Any suggestions ?

       
      • tobzi - 2022-03-01

        I have now solved this issue, so you can just ignore my comment :-)

         

Log in to post a comment.