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

    Preview version of CNC optimized DWC.

    Scheduled Pinned Locked Moved
    CNC
    40
    191
    21.8k
    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.
    • chimaeraghundefined
      chimaeragh @Sindarius
      last edited by

      @sindarius I have tried that, but I seem to lose my current Z zero position so I've commented it out and gone back to calling homez.g which works fine

      Duet 2 Wifi, Ooznest Workbee CNC 1510

      chimaeraghundefined 1 Reply Last reply Reply Quote 0
      • chimaeraghundefined
        chimaeragh @chimaeragh
        last edited by chimaeragh

        @Sindarius I have just noticed that tool position coordinates do not update in real time, but only after starting a new segment of gcode. Is this intentional or a bug?

        Duet 2 Wifi, Ooznest Workbee CNC 1510

        Sindariusundefined 1 Reply Last reply Reply Quote 0
        • Sindariusundefined
          Sindarius @chimaeragh
          last edited by

          @chimaeragh The position is how it is reported through the object model. What I normally see is tool position updates when the move starts and machine position updates after a move has completed. It's not a DWC-CNC specific behavior.

          chimaeraghundefined 1 Reply Last reply Reply Quote 1
          • chimaeraghundefined
            chimaeragh @Sindarius
            last edited by chimaeragh

            @sindarius OK. I think it worked differently on RRF2. Curious why it was changed but it's not too much of a problem.
            Jogging updates in real time though

            Duet 2 Wifi, Ooznest Workbee CNC 1510

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

              @chimaeragh I'm not sure it was any different in RRF2 though.

              In RRF 3.3 you could try decreasing the segment size to make for smaller move lengths. That might let it update more frequently, but I'm not certain. See M669 S and T

              https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_Parameters_for_Cartesian_CoreXY_CoreXZ_CoreXYU_CoreXYUV_MarkForged_kinematics_RRF_2_03_and_later_only

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • Sindariusundefined
                Sindarius @chimaeragh
                last edited by Sindarius

                @chimaeragh

                G91
                G1 H3 Z90 F500
                G90
                G1 X0 Y0 F6000
                G1 Z0
                

                I set this up on my test CNC machine and it worked fine for a go to zero macro. you can set the Z value greater than you z travel and it should stop when the limit is hit.

                chimaeraghundefined 1 Reply Last reply Reply Quote 1
                • chimaeraghundefined
                  chimaeragh @Sindarius
                  last edited by

                  @sindarius Thanks

                  Duet 2 Wifi, Ooznest Workbee CNC 1510

                  1 Reply Last reply Reply Quote 0
                  • chimaeraghundefined
                    chimaeragh
                    last edited by

                    @Sindarius @dc42 @raymondstone Has anybody been able to get power loss resume working with the latest release? Maybe a macro if not implemented in the UI itself? I'm able to run some very long jobs and I'm very nervous as utility power supply is not quite stable at the moment.

                    Duet 2 Wifi, Ooznest Workbee CNC 1510

                    chimaeraghundefined 1 Reply Last reply Reply Quote 0
                    • chimaeraghundefined
                      chimaeragh @chimaeragh
                      last edited by

                      @chimaeragh Found it. Simply sending M916 via console was the solution. Thanks everyone. Should always search the wiki before asking dumb questions 😅

                      Duet 2 Wifi, Ooznest Workbee CNC 1510

                      1 Reply Last reply Reply Quote 0
                      • bitminterundefined
                        bitminter @Sindarius
                        last edited by

                        @sindarius any updates on the probe integration? That would be very helpful to say the least 🙂 thanks again for all your hard work!

                        1 Reply Last reply Reply Quote 0
                        • chimaeraghundefined
                          chimaeragh
                          last edited by

                          @bitminter There's a probe plugin available now here...

                          CNC Probe Plugin

                          Duet 2 Wifi, Ooznest Workbee CNC 1510

                          bitminterundefined 1 Reply Last reply Reply Quote 0
                          • bitminterundefined
                            bitminter @chimaeragh
                            last edited by

                            @chimaeragh that is AWESOME!! Trying it out now! Thanks again!

                            1 Reply Last reply Reply Quote 0
                            • Shanian79undefined
                              Shanian79
                              last edited by

                              1 year with the Duet3 running the CNC.undefined

                              JoergS5undefined 1 Reply Last reply Reply Quote 1
                              • JoergS5undefined
                                JoergS5 @Shanian79
                                last edited by JoergS5

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