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

    Unsolved Duet 3 losing connection whilst printing

    Beta Firmware
    5
    34
    1.3k
    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 gloomyandy

      Can you check your rPi syslog file (/var/log/syslog) and look for warnings/errors from duet control server. if there are any do they match up with when you had the lost connections?

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

        @gloomyandy said in Duet 3 losing connection whilst printing:

        /varlog/syslog

        Yes, I just started the heater, and instantly saw warnings in that log file, as below

        Jan 24 13:17:49 duet3 DuetWebServer[564]: [DoCode] Executing code 'M140 P0 S60'
        Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Mvc.Infrastructure.ContentResultExecutor[1]
        Jan 24 13:17:49 duet3 DuetWebServer[564]: Executing ContentResult with HTTP Response ContentType of text/plain; charset=utf-8
        Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
        Jan 24 13:17:49 duet3 DuetWebServer[564]: Executed action DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer) in 121.9828ms
        Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
        Jan 24 13:17:49 duet3 DuetWebServer[564]: Executed endpoint 'DuetWebServer.Controllers.MachineController.DoCode (DuetWebServer)'
        Jan 24 13:17:49 duet3 DuetWebServer[564]: #033[40m#033[32minfo#033[39m#033[22m#033[49m: Microsoft.AspNetCore.Hosting.Diagnostics[2]
        Jan 24 13:17:49 duet3 DuetWebServer[564]: Request finished in 124.107ms 200 text/plain; charset=utf-8
        Jan 24 13:17:49 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x00000022)
        Jan 24 13:17:49 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x00000011)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x000000b2)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0x02635649)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0xabbbd02c)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xe20300be, got 0x66f47fab)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because the number of maximum retries has been exceeded
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x00000074)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [info] Connection to Duet established
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xfee53e33, got 0x29af8a10)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0x0000002c)
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
        Jan 24 13:17:50 duet3 DuetControlServer[3086]: [info] Connection to Duet established
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0xffffffe1)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x0000007a)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0x147bc906, got 0x094245ad)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0x147bc906, got 0xb45e66d9)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x00000070)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0xffffff77)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad data response was received (0xffffff77)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Bad data CRC32 (expected 0xf639780f, got 0x6abe97ec)
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Lost connection to Duet (Board is not available (no header))
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [info] Connection to Duet established
        Jan 24 13:17:51 duet3 DuetControlServer[3086]: [warn] Restarting transfer because a bad header response was received (0x000000de)

        Dan1990undefined 1 Reply Last reply Reply Quote 0
        • 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