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

    UVW Axis prediction bug?

    Scheduled Pinned Locked Moved
    Beta Firmware
    6
    12
    657
    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.
    • jay_s_ukundefined
      jay_s_uk @Kulitorum
      last edited by

      @kulitorum please update to 3.4.1 and report whether this is still an issue.

      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

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

        @kulitorum by default UVW are handled as linear axes and ABCD as rotational. You can change it with the M584 R parameter.
        https://duet3d.dozuki.com/Wiki/M584

        1 Reply Last reply Reply Quote 1
        • Kulitorumundefined
          Kulitorum
          last edited by

          Interesting development here: We renamed the Axis to A and the problem went away......

          We are updating now.

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

            @kulitorum the UVW axes are implemented just like XYZ. Their maximum speeds should be honoured at all times.

            Also, because UVW default to being linear, the U motion will be considered when interpreting the F parameter, which is almost certainly not what you want to do. I suggest that you either create U as a rotational axis in the M584 command, or use axis letter A instead (as you are now trying).

            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

            Kulitorumundefined 1 Reply Last reply Reply Quote 0
            • Kulitorumundefined
              Kulitorum @dc42
              last edited by

              @dc42 I know that's the theory. None the less, if we use the A axis everything is smooth, if we use the U axis it's not.

              This is true in both cases if we use rotational or linear configuration. Using A is Ok, Using U is not.

              PS: I'd still prefer to use U, so I don't have to re-explain this to all my customers and redo all the documentation, manuals etc. 🙂

              fcwiltundefined dc42undefined 2 Replies Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @Kulitorum
                last edited by

                @kulitorum said in UVW Axis prediction bug?:

                @dc42 I know that's the theory. None the less, if we use the A axis everything is smooth, if we use the U axis it's not.

                This is true in both cases if we use rotational or linear configuration. Using A is Ok, Using U is not.

                PS: I'd still prefer to use U, so I don't have to re-explain this to all my customers and redo all the documentation, manuals etc. 🙂

                What do your config lines for that look like when trying to use U as rotational?

                Thanks.

                Frederick

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

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

                  @kulitorum said in UVW Axis prediction bug?:

                  This is true in both cases if we use rotational or linear configuration. Using A is Ok, Using U is not.

                  I find that hard to understand. The only difference between how axis letters U and A are treated in firmware is that U defaults to linear while A default to rotational.

                  You can run M584 without parameters to see how the axes are configured. In the response, rotational axes will have (r) after them.

                  I note that you are running firmware 3.3RC3. Please note, RC version of firmware are unsupported an may contain bugs that are fixed in later versions. Please consider upgrading to firmware 3.4.1.

                  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

                  Kulitorumundefined 2 Replies Last reply Reply Quote 0
                  • Kulitorumundefined
                    Kulitorum @dc42
                    last edited by

                    @dc42 We are updating the firmware today, but this is not a new thing, it has been the case since forever. (4 years) - so I doubt updating will make any difference.

                    We spend 3 days trying to figure out why we have these uneven movements, and changing the axis "name" to A fixed it.

                    We will examine further, but it does feel like the Axies are somehow running different code.

                    1 Reply Last reply Reply Quote 0
                    • Kulitorumundefined
                      Kulitorum @dc42
                      last edited by

                      @dc42 Hello again.

                      We setup a test where we ran the same gcode with the nozzle rotation configured for the U axis and for the A Axis.

                      Thinking that the shaking would be clear, I mounted a gopro on the printhead - looking down - and put some gloves on the floor for reference. The most obvious result is that the whole print happens a lot faster when the nozzle is running as the A-axis, but looking at the printer in real life, you also notice some shaking and hard accelerations on the U-axis version.

                      I have uploaded an (unlisted) video here: https://youtu.be/abVquTFmLH8

                      I will mail the config files and gcode files (only the first layer) to you.

                      My conclusion is that the axies cannot be running the same code, something is not right.

                      Please have a look.

                      Michael

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

                        Thanks for the video. It will be interesting to see the config files.

                        Z-Bot CoreXY Build | Thingiverse Profile

                        Kulitorumundefined 1 Reply Last reply Reply Quote 0
                        • Kulitorumundefined
                          Kulitorum @Phaedrux
                          last edited by

                          @phaedrux I mailed it to DC42

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