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

    Duet 3/Rpi + toolboard on 3.2b3 - G29 fails

    Scheduled Pinned Locked Moved
    Beta Firmware
    8
    65
    2.6k
    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.
    • oozeBotundefined
      oozeBot
      last edited by

      I just tried to lower the routine to a 49 point mesh and it still failed multiple times at different locations.

      Sigh.. I understand it's a Sunday, but if anyone sees this and has any ideas on how to capture detailed info on the issue before rolling back to 3.2b1 in a few hours, please let me know.

      1 Reply Last reply Reply Quote 0
      • gloomyandyundefined
        gloomyandy
        last edited by

        Run the same test but also run DCS in debug mode and capture the output.

        oozeBotundefined 1 Reply Last reply Reply Quote 0
        • oozeBotundefined
          oozeBot @gloomyandy
          last edited by

          @gloomyandy DCS is not an option, unless there is another way?

          Debugging disabled for modules: Platform(0) Network(1) Webserver(2) GCodes(3) Move(4) Heat(5) DDA(6) Roland(7) Scanner(8) PrintMonitor(9) Storage(10) PortControl(11) DuetExpansion(12) FilamentSensors(13) WiFi(14) Display(15) LinuxInterface(16) CAN(17)

          1 Reply Last reply Reply Quote 0
          • gloomyandyundefined
            gloomyandy
            last edited by

            Sorry should have provided more details. You need to do this on the rPi. This is the official doc: https://duet3d.dozuki.com/Wiki/Getting_Started_With_Duet_3#Section_Monitoring_optional

            I'm not sure if that is 100% correct for 3.2-beta3 though. In particular you may find that when you run DCS as root (which this will do), you can no longer connect via the web interface. But you should still be able to run the G29 via the USB console. You may also find that this produces a lot of output so you may find that changing the command to:
            sudo /opt/dsf/bin/DuetControlServer -l debug | tee log
            will help. This will send a copy of the output to a file called log in your current directory.

            oozeBotundefined 1 Reply Last reply Reply Quote 0
            • oozeBotundefined
              oozeBot @gloomyandy
              last edited by

              @gloomyandy here is the tail end of the output before it fails.. there is nothing valuable. It simply stops:

              [info] Finished macro file retractprobe.g
              [debug] HTTP: ==> Unfinished starting code: G29 S0
              [debug] HTTP: Disposing macro file retractprobe.g
              [debug] HTTP: Sent M566 Z600.00, remaining space 1472, needed 32
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Sent M201 Z600.00, remaining space 1440, needed 32
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Sent G1 X152.4 Y152.4 Z10, remaining space 1392, needed 48
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Suspending code M566 Z600.00
              [debug] HTTP: Suspending code M201 Z600.00
              [debug] HTTP: Suspending code G1 X152.4 Y152.4 Z10
              [debug] Macro file deployprobe0.g not found
              [debug] HTTP: ==> Starting code G29 S0
              [debug] HTTP: Disposing macro file deployprobe0.g
              [debug] HTTP: ==> Unfinished starting code: G29 S0
              [debug] HTTP: Sent M566 Z600.00, remaining space 1472, needed 32
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Sent M201 Z600.00, remaining space 1440, needed 32
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Sent G1 X152.4 Y152.4 Z10, remaining space 1392, needed 48
              [debug] HTTP: -> Resumed suspended code
              [debug] HTTP: Suspending code M566 Z600.00
              [debug] HTTP: Suspending code M201 Z600.00
              [debug] HTTP: Suspending code G1 X152.4 Y152.4 Z10
              [info] Starting macro file deployprobe.g on channel HTTP
              [debug] HTTP: ==> Starting code G29 S0
              [debug] Waiting for execution of M280 P0 S10 (macro code)
              [debug] Processing M280 P0 S10
              [debug] Waiting for finish of M280 P0 S10
              [debug] HTTP: Sent M280 P0 S10, remaining space 1496, needed 40
              [debug] Completed M280 P0 S10
              [debug] Finished codes from macro file deployprobe.g
              [info] Finished macro file deployprobe.g
              

              I tried running M122. It's added to the queue but since G29 is still running, it's blocked from executing. The only way I know out of this is to reboot, which clears any errors.

              1 Reply Last reply Reply Quote 0
              • gloomyandyundefined
                gloomyandy
                last edited by

                There may be something in there that is useful to Christian when he gets to look at it, so if you have the full log file please post it for him to be able to look at.

                oozeBotundefined 1 Reply Last reply Reply Quote 0
                • oozeBotundefined
                  oozeBot @gloomyandy
                  last edited by

                  @gloomyandy @chrishamm Here is the log. It also contains a bonus crash at line 362-364 where it lost connection and soft-rebooted itself. I hadn't seen that before..

                  I'm going to be rolling back to 3.2b1 here soon. Please let me know if there is anything else I can assist with testing..

                  log.txt

                  1 Reply Last reply Reply Quote 2
                  • jbarrosundefined
                    jbarros
                    last edited by jbarros

                    Just to add some data to this thread, I'm able to finish 210 point Mesh Probing on Duet3 with Toolboard with no SBC running 3.2 beta3:

                    09/11/2020, 12:27:29	210 points probed, min error -0.063, max error 0.349, mean 0.079, deviation 0.085
                    Height map saved to file 0:/sys/heightmap.csv
                    
                    dc42undefined 1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @jbarros
                      last edited by

                      @jbarros said in Duet 3/Rpi + toolboard on 3.2b3 - G29 fails:

                      Just to add some data to this thread, I'm able to finish 210 point Mesh Probing on Duet3 with Toolboard with no SBC:

                      09/11/2020, 12:27:29	210 points probed, min error -0.063, max error 0.349, mean 0.079, deviation 0.085
                      Height map saved to file 0:/sys/heightmap.csv
                      

                      Thanks, that's a very useful data point. Looks like it's something to do with running the deploy/retract files when they are held on the SBC, because the rest of the G29 probing function doesn't involve the SBC except at the start and end.

                      Duet WiFi hardware designer and firmware engineer
                      Please do not ask me for Duet support via PM or email, use the forum
                      http://www.escher3d.com, https://miscsolutions.wordpress.com

                      oozeBotundefined 1 Reply Last reply Reply Quote 0
                      • oozeBotundefined
                        oozeBot @dc42
                        last edited by

                        @dc42 I still have one machine running 3.2b3 if there is anything you or others want me to test on this issue.

                        I plan on rolling back to 3.2b1, creating a height map, and the moving then back to 3.2b3 for other testing by this afternoon though.

                        dc42undefined 1 Reply Last reply Reply Quote 0
                        • dc42undefined
                          dc42 administrators @oozeBot
                          last edited by

                          @oozeBot said in Duet 3/Rpi + toolboard on 3.2b3 - G29 fails:

                          @dc42 I still have one machine running 3.2b3 if there is anything you or others want me to test on this issue.

                          I plan on rolling back to 3.2b1, creating a height map, and the moving then back to 3.2b3 for other testing by this afternoon though.

                          @chrishamm, is there anything else you would like @oozeBot to test?

                          Duet WiFi hardware designer and firmware engineer
                          Please do not ask me for Duet support via PM or email, use the forum
                          http://www.escher3d.com, https://miscsolutions.wordpress.com

                          Touchthebitumundefined 1 Reply Last reply Reply Quote 0
                          • Touchthebitumundefined
                            Touchthebitum @dc42
                            last edited by

                            @dc42 said in Duet 3/Rpi + toolboard on 3.2b3 - G29 fails:

                            I plan on rolling back to 3.2b1, creating a height map, and the moving then back to 3.2b3 for other testing by this afternoon though.

                            I tried it yesterday and it seems to work but from 3.2b2 instead of 3.2b1 to 3.2b3

                            Sparkcube XL V 1.1 300x300x190, Radds, Raspberry, Keenovo silicone bedheat 220v, Big Booster Extruder, DIY building
                            BLV Cube 665mm Direct Drive with Duet3/SBC (RPi 4) Mosquito Magnum/Bond Tech Extruder/Vanadium Nozzle, Keenovo silicone bedheat 220v

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

                              @oozeBot Thanks for reporting this issue, I could reproduce it and I'm testing a potential fix for this problem.

                              Duet software engineer

                              oozeBotundefined 1 Reply Last reply Reply Quote 0
                              • oozeBotundefined
                                oozeBot @chrishamm
                                last edited by

                                @chrishamm great! I didn't get around to rolling this machine back to 3.2b1, so please let me know if you want me to test your fix..

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

                                  @oozeBot Yes, I am quite sure I could figure out what was going on. Please try out this firmware build with DSF 3.2-b3: https://pkg.duet3d.com/Duet3Firmware_MB6HC.bin You can upload it on the System page and confirm the update prompt.

                                  Duet software engineer

                                  oozeBotundefined 2 Replies Last reply Reply Quote 0
                                  • oozeBotundefined
                                    oozeBot @chrishamm
                                    last edited by oozeBot

                                    @chrishamm This appears to be fixed. I just completed a 196 probe mesh without issue. Thanks!

                                    1 Reply Last reply Reply Quote 0
                                    • oozeBotundefined
                                      oozeBot @chrishamm
                                      last edited by

                                      @chrishamm scratch that - while it did complete, DWC is still in a busy state where it will not accept any new commands.

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

                                        @oozeBot Please try to download and flash that file again - I just updated it once more with my other hotfix. If it remains in the "busy" state with that build, please share the debug log of DCS and I'll see what I can do.

                                        Duet software engineer

                                        oozeBotundefined 1 Reply Last reply Reply Quote 0
                                        • oozeBotundefined
                                          oozeBot @chrishamm
                                          last edited by

                                          @chrishamm will do it right now.. thanks

                                          oozeBotundefined 1 Reply Last reply Reply Quote 0
                                          • oozeBotundefined
                                            oozeBot @oozeBot
                                            last edited by oozeBot

                                            it stayed in a busy state. I'll capture the DCS log and upload here soon..

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