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

    Firmware 1.21 release candidate 2 now available

    Scheduled Pinned Locked Moved
    Firmware installation
    22
    81
    11.2k
    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.
    • nytundefined
      nyt
      last edited by

      @dc42, here's a video that shows the issue much better.

      Instead of moving straight back after the resume, it goes diagonal across the square, then back to the position it should have moved to.

      It looks like when it resumes, it's inserting the next before the current move.

      https://www.youtube.com/watch?v=70KkYPV3kDU

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

        Thanks, that's much clearer. Can you share the resurrect.g file that was generated, and the original GCode file? The resurrect.g file will give me the exact offset in the GCode file at which the pause occurred.

        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

        1 Reply Last reply Reply Quote 0
        • nytundefined
          nyt
          last edited by

          I'll have to recreate it again, have a print running atm and have paused since. I'll recreate and upload it in a little bit.

          The gcode is pretty simple, just a bunch of this…

          ; layer 17, Z = 3.400
          ; inner perimeter
          M204 P 600
          G1 X175.600 Y224.400 F18000
          G1 Z3.400 F1200
          G1 E0.4000 F3600
          G1 X175.600 Y175.600 E1.5419 F2700
          G1 X224.400 Y175.600 E1.5419
          G1 X224.400 Y224.400 E1.5419
          G1 X175.600 Y224.400 E1.5419
          G1 X175.600 Y224.200 F3600
          ; outer perimeter
          M204 P 600
          G1 X175.200 Y224.800 F18000
          G1 X175.200 Y175.200 E1.5672 F1800
          G1 X224.800 Y175.200 E1.5672
          G1 X224.800 Y224.800 E1.5672
          G1 X175.200 Y224.800 E1.5672
          G1 E-0.4000 F3600
          G1 X175.200 Y224.600 F3600
          G1 Z3.700 F1200

          1 Reply Last reply Reply Quote 0
          • nytundefined
            nyt
            last edited by

            recreated again, http://rznt.com/resumebug.zip

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

              Thanks. I believe I have identified the problem and fixed it; so please can you test again with 1.21RC3 when I have released it.

              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

              1 Reply Last reply Reply Quote 0
              • kraegarundefined
                kraegar
                last edited by

                I scanned and did not see it, sorry if this is working as intended. I use the Z probe for homing Z. With multi-probe enabled, it still only probes once when homing Z. When I run bed.g, it probes twice (or more) as needed, though.

                Co-Creator of the RailcoreII CoreXY printer
                https://www.thingiverse.com/thing:2407174

                1 Reply Last reply Reply Quote 0
                • nytundefined
                  nyt
                  last edited by

                  I think that's intended, but it'd be nice to have multi tap when homing z

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

                    It might be possible already:

                    • Start with a plain G30 at whatever XY point you want
                    • Follow it with e.g. G30 X100 Y100 S0 (if that doesn't work, G30 P0 X100 Y100 S0 might)

                    Warning: I haven't tried this!

                    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

                    1 Reply Last reply Reply Quote 0
                    • whosrdaddyundefined
                      whosrdaddy
                      last edited by

                      David, can you explain what behavior we should expect?
                      Will the second G30 perform multitapping or not? (I tried without P0 but did not multitap)

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

                        I am closing this thread because 121RC3 is now available.

                        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

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