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

    Duet3+SBC print stops - DWC unresponsive -

    Scheduled Pinned Locked Moved Unsolved
    General Discussion
    jubilee
    6
    18
    579
    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.
    • Wallyundefined
      Wally @BryanH
      last edited by

      @BryanH Thanks for the details. Suggest changing your main board jumpers and power the Pi independently (separate power source like an AC adapter) to see if that helps resolve.

      1 Reply Last reply Reply Quote 1
      • BryanHundefined
        BryanH
        last edited by

        @Wally Thanks for the suggestion but I was really hoping for some diagnostics / troubleshooting. Does anyone know if we can connect the Pi to the Duet3 via USB while in operation to capture the debug output on the USB port? I've already set the DSF / DWC to debug logging and will be trying some increasingly longer prints to see if I can reproduce the issue.

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Trying to power the pi separately might be worthwhile. It would be interesting to see if that helped or not.

          It could also very likely be an issue with DSF. Duet3 + SBC is still one of the more cutting edge implementations.

          You may be able to get some more info via this technique to enable debugging

          https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • BryanHundefined
            BryanH
            last edited by

            @Phaedrux Thanks for the info - I'm running the debug monitoring now - Found what looks like an out of memory dump in the Pi's logs at or about the time of the last failure - Should I post it here?
            Thanks!

            Phaedruxundefined 1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator @BryanH
              last edited by

              @BryanH said in Duet3+SBC print stops - DWC unresponsive -:

              Should I post it here?

              Sure.

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • BryanHundefined
                BryanH
                last edited by

                JubileePiLogDump.txt

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined
                  Phaedrux Moderator
                  last edited by

                  Thanks. Perhaps @chrishamm will be able to take a look.

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • BryanHundefined
                    BryanH
                    last edited by

                    Great, that's from the kernel log - I'm pulling the syslog to see if there's anything there.

                    1 Reply Last reply Reply Quote 0
                    • BryanHundefined
                      BryanH
                      last edited by

                      Syslog with the observed issue https://drive.google.com/file/d/1qGrD7uS_jXZGs1kyyUrE6AGbiEL8Fvxc/view?usp=sharing

                      1 Reply Last reply Reply Quote 0
                      • chrishammundefined
                        chrishamm administrators
                        last edited by

                        Unfortunately there is no useful information in the logs you provided. Please start DuetControlServer with debug log level using a terminal on the Pi - just be aware that a print will be terminated once that is closed:

                        sudo systemctl stop duetcontrolserver
                        sudo /opt/dsf/bin/DuetControlServer -l debug
                        

                        I need to know what exactly is causing the hang. Did you observe any pattern when the hangs occurred? When it hangs, you should be able to run M122 "DSF" from the G-code console to get a diagnostics output only from DCS.

                        If it really runs out of memory at some point, I need to reproduce that. Can you compress your system directory files plus the file you were trying to print?

                        Duet software engineer

                        1 Reply Last reply Reply Quote 0
                        • BryanHundefined
                          BryanH
                          last edited by

                          Thank you, I'm running DCS in debug mode - and will be running jobs beginning tomorrow morning with the last jobs to see if I can reproduce the issue.

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