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

    3.3rc1 Polar Kinematic issue.

    Scheduled Pinned Locked Moved Solved
    Beta Firmware
    2
    8
    482
    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.
    • Phospherusundefined
      Phospherus
      last edited by Phospherus

      @dc42 This is an update to the Polar issue we spoke of in the other thread.

      I am getting a waviness on straight lines with the 3.3 Betas and the RC1, Firmware 3.2.2 is the newest that I do not see an issue.

      The following is with the same Gcode file.

      This is with the latest 3.3rc1 that DC42 linked to on Dropbox.

      20210502_042400.jpg

      This is 3.2.2 just to show that it is not a mechanical issue.

      20210502_043459.jpg

      These were done back to back for comparison and on Genuine Duet Ethernet 2.

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

        @phospherus please send M669 without parameters to check the segmentation settings.

        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

        Phospherusundefined 2 Replies Last reply Reply Quote 0
        • Phospherusundefined
          Phospherus @dc42
          last edited by

          @dc42

          M669
          Kinematics is Polar with radius 0.0 to 120.0mm, homed radius 0.3mm, segments/sec 100, min. segment length 0.20

          I checked both firmware versions this output above is the same.

          1 Reply Last reply Reply Quote 0
          • Phospherusundefined
            Phospherus @dc42
            last edited by

            @dc42

            Are these ok for segments/sec or do you see an issue?

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

              @phospherus thos segmentation value look OK to me. In the first image you posted, what is the approximate length of each wave; and what was the printing speed? It looks to me that the firmware was not using the configured segmentation settings but was using much larger segments instead.

              Did you try 3.3beta1, and if so, did that version show the same problem as the later betas?

              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
              • dc42undefined
                dc42 administrators @Phospherus
                last edited by

                @phospherus, I think I have found the bug. I will fix it in 3.3RC2. Meanwhile, I think a workaround would be to send M669 T0.2 (later than your main M669 command) or alternatively add parameter T0.2 to your existing M669 command.

                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

                Phospherusundefined 2 Replies Last reply Reply Quote 0
                • Phospherusundefined
                  Phospherus @dc42
                  last edited by

                  @dc42

                  Thank you for the info. Will reload 3.3 RC1 and try the fix and will let you know.

                  1 Reply Last reply Reply Quote 0
                  • Phospherusundefined
                    Phospherus @dc42
                    last edited by

                    @dc42

                    Confirmed that issue is fixed with the provided work around. Thank you

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