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

    Sensorless homing, not working

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    4
    13
    822
    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.
    • T3P3Tonyundefined
      T3P3Tony administrators @StevePS3
      last edited by

      @steveps3

      Set the S parameter to the lowest value at which you do not get false stall reports. Typical values for nema 17 motors are between 1 and 3. False stall reports are most likely during fast travel moves, because the acceleration increases the load on the motor. False stall reports are also more likely when the motors are hot.

      Have you tried reducing the S parameter until you get a stall?

      https://duet3d.dozuki.com/Wiki/M915

      Snnn Stall detection threshold (-64 to +63, values below -10 not recommended). Lower values make stall detection more sensitive. S3 is a good starting point for many motors.

      At some point there will be an S value that stalls when you reach the end of the axis. For most motors/setups that should be a higher number than what you get when you have it so low that it detects a stall on a normal move.

      www.duet3d.com

      StevePS3undefined 1 Reply Last reply Reply Quote 0
      • StevePS3undefined
        StevePS3 @T3P3Tony
        last edited by

        @t3p3tony I set it to -64 and it still doesn't stall

        M915 X Y S-64 R0 F0

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

          @steveps3 said in Sensorless homing, not working:

          Board: Duet 3 Mini 5+ (Mini5plus)
          Firmware: RepRapFirmware for Duet 3 Mini 5+ 3.2.2 (2021-02-11)

          Upgrade there firmware to 3.3. There is a known issue with sensorless homing on Duet 3 Mini using firmware 3.2.2 and earlier. There is a workaround for it, but it is simpler to upgrade to firmware 3.3.

          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

          StevePS3undefined 1 Reply Last reply Reply Quote 0
          • StevePS3undefined
            StevePS3 @dc42
            last edited by

            @dc42 Thanks, I'll give that a try.

            StevePS3undefined 1 Reply Last reply Reply Quote 0
            • StevePS3undefined
              StevePS3 @StevePS3
              last edited by

              OK, I am now on 3.3 and the results are the same. Just lots of belt slipping as the head crashes into the side of the printer.

              1 Reply Last reply Reply Quote 0
              • StevePS3undefined
                StevePS3
                last edited by

                I have reduced the current to the steppers so that they stall as soon as they start to move. Yet all they do is continue to try to move. I was assuming that they would stop moving as soon as they stall?

                jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                • jay_s_ukundefined
                  jay_s_uk @StevePS3
                  last edited by

                  @steveps3 make sure you have something like D3 V40 on each M569 you want to run sensorless on so they are in stealthchop.
                  This is a nice bit of test code to make sure your motors are stalling

                  M915 P0 S-127 H10 R1 ; Set very sensitive stall detect
                  M574 X1 S3 ; configure endstop for stall detection
                  G1 X200 H1 ; Should stall pretty much immediately
                  

                  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

                  StevePS3undefined 1 Reply Last reply Reply Quote 0
                  • StevePS3undefined
                    StevePS3 @jay_s_uk
                    last edited by StevePS3

                    @jay_s_uk
                    Yes, that worked. OK, so now maybe I can start to tweak the settings until it works. -127 definitely causes an instant stall 🙂

                    StevePS3undefined 2 Replies Last reply Reply Quote 1
                    • StevePS3undefined
                      StevePS3 @StevePS3
                      last edited by

                      This post is deleted!
                      1 Reply Last reply Reply Quote 0
                      • StevePS3undefined
                        StevePS3 @StevePS3
                        last edited by

                        A value of about 30 seems to work just fine.

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