Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Duet 3 losing connection whilst printing

    Scheduled Pinned Locked Moved Unsolved
    Beta Firmware
    5
    34
    1.9k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • gloomyandyundefined
      gloomyandy
      last edited by

      Looks like your heater may be introducing noise into the Duet/SBC connection. Obvious things are to check how the various cables are routed. How long is the cable between the rPi and the Duet? Perhaps some photos of how you have things set up?

      camcamnzundefined 1 Reply Last reply Reply Quote 0
      • camcamnzundefined
        camcamnz @gloomyandy
        last edited by

        @gloomyandy That was my first thought as well, so I moved the rPi out of the enclosure with the other electronics until it was sorted. It is that cable that came with the Duet ![alt text]duet.jpg

        1 Reply Last reply Reply Quote 0
        • Thoma308undefined
          Thoma308
          last edited by Thoma308

          @gloomyandy said in Duet 3 losing connection whilst printing:

          ter may be introducing noise into the Duet/SBC connection. Obvious things are to check how the various cables are routed. How long is the cable between the rPi and the Duet? Perhaps some photos of how you have things set up?

          SOLVED:
          The Heater is not the problem
          I plugged everything back in on the PI, keyboard, mouse,
          HDMI, USB touchscreen and connected the PI to the LAN.
          Also reinstalled Anydesk as a remote terminal.
          I accessed everything via http://duet3.local/ and locally via the screen on the PI again.

          AND NOW THE SOLUTION:
          The separtate power supply is the problem. You can power the SBC directly and power the Duet separately.
          there are jumpers for that on the board.
          And that was the problem with two separate power supplies.
          I now have a 4A power supply directly on the PI and through that I also feed the 5V in the Duet.
          -> and that was the solution

          2h printing without any error message

          https://duet3d.dozuki.com/Wiki/Duet_3_Mainboard_6HC_Hardware_Overview#Section_5V
          SBC->5V and 5V -> SBC both are now connected

          camcamnzundefined 1 Reply Last reply Reply Quote 0
          • camcamnzundefined
            camcamnz @Thoma308
            last edited by

            @Thoma308 In that case, your problem is different to mine, as I already tried all the variations of powering pi & duet

            1 Reply Last reply Reply Quote 0
            • Thoma308undefined
              Thoma308
              last edited by Thoma308

              But it probably has to do with the power supply. I would make some more attempts in this direction. I use a Raspberry Pi 4 Model B 4GB

              1 Reply Last reply Reply Quote 0
              • Dan1990undefined
                Dan1990
                last edited by

                I have the same problem but when I did connect it via duet->SBC still giving the same issue.

                1 Reply Last reply Reply Quote 0
                • Thoma308undefined
                  Thoma308
                  last edited by

                  @Thoma308 said in Duet 3 losing connection whilst printing:

                  SBC->5V and 5V -> SBC both are now connected

                  For me it runs perfectly now, but only with the power supply from the Pi and both jumper set
                  SBC->5V
                  5V -> SBC

                  1 Reply Last reply Reply Quote 0
                  • Dan1990undefined
                    Dan1990 @camcamnz
                    last edited by

                    @camcamnz

                    how did u access the:

                    /varlog/syslog

                    camcamnzundefined 1 Reply Last reply Reply Quote 0
                    • camcamnzundefined
                      camcamnz @Dan1990
                      last edited by

                      @Dan1990 via ssh/putty.
                      There is a typo it is actually /var/log/syslog
                      I ran the following command and watched the output once whilst testing:
                      tail -f /var/log/syslog

                      Dan1990undefined 1 Reply Last reply Reply Quote 0
                      • Dan1990undefined
                        Dan1990 @camcamnz
                        last edited by

                        @camcamnz

                        Thanks,

                        I have the same issue as you, and I think I have found a lead to solve it. I disconnected the bed and for now, everything looks fine.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA