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

    Detect Skipping Extruder?

    Scheduled Pinned Locked Moved
    General Discussion
    7
    13
    445
    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 @Adamfilip
      last edited by jay_s_uk

      @Adamfilip yes, you can set stall detection, assuming you have a board that supports it (most do)
      https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m915-configure-motor-stall-detection

      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

      Adamfilipundefined 1 Reply Last reply Reply Quote 0
      • Adamfilipundefined
        Adamfilip @jay_s_uk
        last edited by

        @jay_s_uk Can you set it to run a macro?

        Rn Action to take on detecting a stall from any of these drivers: 0 = no action (default), 1 = just log it, 2 = pause print, 3 = pause print, execute /sys/rehome.g, and resume print. See notes for RRF v3.4

        moth4017undefined jay_s_ukundefined T3P3Tonyundefined 3 Replies Last reply Reply Quote 0
        • moth4017undefined
          moth4017 @Adamfilip
          last edited by

          @Adamfilip you have given me an idea ... if the stall detection of the extruder was on the fist layer , could you auto baby step the nozzle away from the bed ?

          <

          Adamfilipundefined 1 Reply Last reply Reply Quote 1
          • Adamfilipundefined
            Adamfilip @moth4017
            last edited by

            @moth4017 interesting idea to compensate for being too close on layer 1

            moth4017undefined dc42undefined 2 Replies Last reply Reply Quote 0
            • moth4017undefined
              moth4017 @Adamfilip
              last edited by

              @Adamfilip yes

              <

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

                @Adamfilip yes. You can set it via macro or the console

                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
                • T3P3Tonyundefined
                  T3P3Tony administrators @Adamfilip
                  last edited by

                  @Adamfilip be aware that stall detection may not work well at typical extruder speeds, see this:

                  https://docs.duet3d.com/en/User_manual/Connecting_hardware/Sensors_stall_detection#minimum-recommended-speed-for-stall-detection

                  YMMV and you do need to tune it in.

                  From 3.4 your detected stalls will be handled by the event system:

                  In RRF v3.4 and later there is no longer a distinction between R2 and R3; both cause an event to be created when the driver stalls. To handle the event, RRF calls driver-stall.g passing the stalled local driver number in param.D and the CAN address of the board concerned in param.B. File rehome.g is no longer used. If file driver-stall.g is not found then the print is paused without running pause.g and the error is reported.

                  https://docs.duet3d.com/User_manual/RepRapFirmware/Events

                  www.duet3d.com

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

                    @Adamfilip a caveat is that if the extruder is driven by a TMC2209 then the driver would have to be in stealthChop mode for stall detection to work, and using stealthChop on extruder motors is almost certainly a bad idea. It might be OK using TMC2660 or TMC2160/5160 drivers, although stall detection is easier at reduced current.

                    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
                    • RandyL00123undefined
                      RandyL00123
                      last edited by

                      I started thinking of how stall detection works, and I was wondering if it's possible to monitor the extruder stepper voltage. It seems to me that if you have a filament run out, the voltage would suddenly drop significantly as the motor force would drop. On the other end of the spectrum, a filament snag would cause the motor voltage to spike before the extruder started to grind, leading to a reduction in motor torque as the filament disappeared from under the drive gear. So, is it possible to monitor the extruder stepper voltage, and have an acceptable range? Any voltage outside of that range would trigger a problem.

                      moth4017undefined T3P3Tonyundefined 2 Replies Last reply Reply Quote 0
                      • moth4017undefined
                        moth4017 @RandyL00123
                        last edited by

                        @RandyL00123 I'm not sure there is a way to monitor that in duet/DWC ,

                        <

                        1 Reply Last reply Reply Quote 0
                        • T3P3Tonyundefined
                          T3P3Tony administrators @RandyL00123
                          last edited by

                          @RandyL00123 see the reply here:
                          https://forum.duet3d.com/topic/31798/monitor-extruder-stepper-voltage-to-detect-filament-errors?_=1679398375558

                          www.duet3d.com

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