Navigation

    Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Stall detection on Duet 3 Mini

    General Discussion
    7
    11
    521
    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.
    • dc42
      dc42 administrators last edited by dc42

      We've discovered a bug in how stall detection sensitivity is set on the Duet 3 Mini, due to a change in how the TMC2209 stall sensitivity is programmed compared to other drivers. This is being fixed in the forthcoming 3.3 release. Meanwhile it may be helpful to know that in firmware 3.2, this is how I expect the M915 S parameter to behave on the Duet 3 Mini:

      Most sensitive ....... least sensitive
      -1 -2 -3 ... -64 63 62 ... 2 1 0

      Whereas on TMC2260 drivers (Duet 2) and TMC5160 drivers (Duet 3 MB6HC) it is:

      Most sensitive ....... least sensitive
      -64 -63 ... -2 -1 0 1 2 ... 63

      Additionally, the TMC2209 is capable of some other sensitivity settings that cannot currently be selected using M915.

      Thanks to Andy Shaw for pointing out this issue.

      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 2
      • Veti
        Veti last edited by

        that explains why i could not get stall detection to work when i tested with -64

        1 Reply Last reply Reply Quote 0
        • mendenmh
          mendenmh last edited by

          Or, to make it more sensible, they have changed from a signed representation on [-64,63] with 63 being least sensitive to an unsigned representation on [0,127] with zero being least sensitive and 127 being most sensitive, with 7-bit math.

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

            Actually on TMC2209 they have changed the range as well... it runs 0..255 with 255 being most sensitive.

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

              I've put a new unofficial 3.3beta build of Duet3MiniFirmware.uf2 at https://www.dropbox.com/sh/wme9k0z86sytg33/AAAT6wrHp2eeJHK-dYoW1Um4a?dl=0. This version accepts M915 S parameters between -128 (most sensitive) and +127 (least sensitive) for TMC2209 drivers.

              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

              fcwilt 1 Reply Last reply Reply Quote 1
              • fcwilt
                fcwilt @dc42 last edited by

                @dc42 said in Stall detection on Duet 3 Mini:

                I've put a new unofficial 3.3beta build of Duet3MiniFirmware.uf2 at https://www.dropbox.com/sh/wme9k0z86sytg33/AAAT6wrHp2eeJHK-dYoW1Um4a?dl=0. This version accepts M915 S parameters between -128 (most sensitive) and +127 (least sensitive) for TMC2209 drivers.

                Hmm...

                So what is wrong with 0 to 255?

                Thanks.

                Frederick

                Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

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

                  @fcwilt said in Stall detection on Duet 3 Mini:

                  So what is wrong with 0 to 255?

                  1. If we change M915 to always accept 0 .. 255, that will break existing Duet 2 and 3 user configurations. In particular, stall homing will fail, which may cause damage to user's machines. Not all users read the upgrade notes.

                  2. If we make M915 accept values of -64 .. +63 for Duet 2 and Duet 3 MB6HC, and 255 .. 0 for Duet 3 Mini and tool boards, that will be confusing to users, especially in those systems that have both TMC5160 and TMC2209 drivers.

                  I may introduce an additional parameter that accepts 0 .. 255 and when it is present is used instead of the S parameter. We would have to map it back to +63 .. -64 when used with TMC2660 or TMC5160 drivers. We could then deprecate the S parameter.

                  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

                  fcwilt 1 Reply Last reply Reply Quote 1
                  • Veti
                    Veti last edited by

                    i kind of like 0 beeing the default in the middle.

                    because you can make it less - or more + sensitive.

                    1 Reply Last reply Reply Quote 1
                    • fcwilt
                      fcwilt @dc42 last edited by

                      @dc42 said in Stall detection on Duet 3 Mini:

                      @fcwilt said in Stall detection on Duet 3 Mini:

                      So what is wrong with 0 to 255?

                      1. If we change M915 to always accept 1 .. 255, that will break existing Duet 2 and 3 user configurations. In particular, stall homing will fail, which may cause damage to user's machines. Not all users read the upgrade notes.

                      2. If we make M915 accept values of -64 .. +63 for Duet 2 and Duet 3 MB6HC, and 255 .. 0 for Duet 3 Mini and tool boards, that will be confusing to users, especially in those esystems that have both TMC5160 and TMC2209 drivers.

                      I may introduce an additional parameter that accepts 0 .. 255 and when it is present is used instead of the S parameter. We would have to map it back to +63 .. -64 when used with TMC2660 or TMC5160 drivers. We could then deprecate the S parameter.

                      Thanks for the edification - that all makes perfect sense.

                      Frederick

                      Printers: A FT-5 with the 713 upgrade bits. A custom MarkForged style. A small Utilmaker style and a CoreXY from kits. Various hotends. Using Duets (2 and 3) running 3.4.1

                      1 Reply Last reply Reply Quote 0
                      • Sotidii
                        Sotidii last edited by

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • carcamerarig
                          carcamerarig last edited by

                          @dc42 What did you end up doing here? For clarity does the Gcode dictionary reflect the changes you made as the thread went cold and no definitive answer?
                          For my 0.9 LDO motors I have M915 X S-50 F0 H400 R0 on the mini, it homes but im having a hell of a game with motors banging, crashing, thumping however you want to call it. I had some help to try to keep spreadcycle active except for homing but still the bang / layer shift continues.
                          when I purchased the board @T3P3Tony said the 2209's ran nicely with 0.9's (bit off topic here) but I could seriously do with some help, im on the verge of scrapping it.

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