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

    Stallguard not working

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    3
    25
    1.0k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      You don't mention which board you're actually using. If it's the Maestro, it does not support stall detection with the 2224 drivers. If it's a wifi/ethernet then it does.

      Have you seen this? https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing

      For firmware you should use this one: https://github.com/dc42/RepRapFirmware/releases/tag/2.05.1

      you'll need Duet2CombinedFirmware.bin, Duet2CombinedFirmware.bin, and DuetWiFiServer-1.23.bin.

      For motor current you should target 70 to 85% of the rated max of the motor.

      Z-Bot CoreXY Build | Thingiverse Profile

      1 Reply Last reply Reply Quote 0
      • xorloschundefined
        xorlosch
        last edited by

        Ah, thanks. Sorry I forgot to mention: I am using a Duet Wifi.
        My firmware is this one:

        Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
        Firmware Electronics: Duet WiFi 1.02 or later
        Firmware Version: 2.03beta1 (2019-02-03b3)
        So maybe it does not work with my version? I will try to update the Frimware next then

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

          It should work, but yes, would be best to update.

          Also re-read the stall detection page and see if you are running into any of the limitations noted there.

          Z-Bot CoreXY Build | Thingiverse Profile

          xorloschundefined 1 Reply Last reply Reply Quote 0
          • xorloschundefined
            xorlosch @Phaedrux
            last edited by

            Still not working after the update. I also reread the webpage how to set the stall detection up several times aready but it just won't activate. but maybe I have to increase the current of the motors a bit more ( I was just running at 70%). is there something else which could be wrong? Having the M915 command at the end of config.g is ok, or does it need a special place to be?

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

              Having M915 in config.g should be fine.

              Can you send M915 in the console by itself and see what it reports back just to confirm it's settings are actually being applied?

              Z-Bot CoreXY Build | Thingiverse Profile

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

                How fast are you moving when you're trying to trigger it?

                Z-Bot CoreXY Build | Thingiverse Profile

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

                  @xorlosch said in Stallguard not working:

                  M92 X44.31 Y44.30

                  I wonder if the low steps per mm on X and Y would have something to do with it? @dc42

                  Z-Bot CoreXY Build | Thingiverse Profile

                  1 Reply Last reply Reply Quote 0
                  • xorloschundefined
                    xorlosch
                    last edited by

                    The command is applied. I now try M915 X Y S-50 F1 R2. That should trigger on anything hopefully and then stop the print. how fast I a going is a loaded question. As far as I understood this only works while printing, so I set it u to print something. max speed should be 50 I think. lowest speed?

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

                      Ok, so just to confirm, you are testing it during an actual print? As far as I recall that's really the only way it will work.

                      Have you experimented with the H parameter yet?

                      Hnnn (optional) Minimum motor full steps per second for stall detection to be considered reliable, default 200 (try 400 for 0.9deg motors)

                      I think this may be where your low steps per mm on X and Y may be coming into play.

                      Z-Bot CoreXY Build | Thingiverse Profile

                      1 Reply Last reply Reply Quote 0
                      • xorloschundefined
                        xorlosch
                        last edited by

                        the low settings for M92 X and Y should be quite typically for a belt driven carthesian printer. but maybe that is the problem. I just tried again and it still won't register. maybe also my current reduction to 30% is at fault. Or my jerk and acceleartion settings. I give up for now. maybe i can get it to stopp skipping layers by crancking up the current(which my last board did). Or I have to stop using mikrostepping, as that also seem to loose some torque for the single steps

                        1 Reply Last reply Reply Quote 0
                        • xorloschundefined
                          xorlosch
                          last edited by

                          As I understood the H settings are to prevent too many wrong triggers. Of course I could try to reduce it but 200 (which is also the dfault) should be the correct settings for my motors. And Yes: I started a print ech time I tested if the stal detection was working

                          1 Reply Last reply Reply Quote 0
                          • xorloschundefined
                            xorlosch
                            last edited by

                            but now that I think about it , that might be what stops me here, as the direct driven belts have the low steps per mm values, I might have been slightly below that vaue of 200 steps /s

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

                              @xorlosch said in Stallguard not working:

                              I might have been slightly below that vaue of 200 steps /s

                              That's what I mean. Try setting it lower. 100 or even 50 just to see if you can even get a trigger.

                              @xorlosch said in Stallguard not working:

                              maybe also my current reduction to 30% is at fault

                              You're only using 30% current?

                              Z-Bot CoreXY Build | Thingiverse Profile

                              1 Reply Last reply Reply Quote 0
                              • xorloschundefined
                                xorlosch
                                last edited by

                                Ok that worked. I went to an agressive S-50 H10 and it instantly triggered. So now I have a at least a starting point for finetuning. I will post my settings when i am done (in the next days).
                                30% I had as reduced power for my stepper motors :M906 X1050 Y1250 Z1100 E900 I30
                                would that be too low?

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

                                  @xorlosch said in Stallguard not working:

                                  30% I had as reduced power for my stepper motors :M906 X1050 Y1250 Z1100 E900 I30
                                  would that be too low?

                                  Do you mean the I30? That's for idle hold, not normal operation.

                                  The current for X Y and Z look reasonable, but as I said earlier. Target 70-85% of the max for the motor.

                                  Z-Bot CoreXY Build | Thingiverse Profile

                                  1 Reply Last reply Reply Quote 0
                                  • xorloschundefined
                                    xorlosch
                                    last edited by

                                    yes those values I had both set to 70%. now i increased to 82%

                                    1 Reply Last reply Reply Quote 0
                                    • xorloschundefined
                                      xorlosch
                                      last edited by

                                      I tried setting up the stall detection but the axis is just too slow for stallguard to work. seems to be better suited for delta printers or core xy than carthesian printers :(. I had to go lower than H50 to detect stalls and then acutally all o them were false and it did not trigger on any real stalls. I will try installing smaller toothed gears for te belts (so that the motor neeeds more stes per mm) but i don't have high hopes. Has anybody got the Stall detection to work with carthesian printer with ow steps per turn?

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

                                        @xorlosch said in Stallguard not working:

                                        I had to go lower than H50 to detect stalls

                                        What was the S value?

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        xorloschundefined 1 Reply Last reply Reply Quote 0
                                        • xorloschundefined
                                          xorlosch @Phaedrux
                                          last edited by

                                          @Phaedrux with an S value of 7 or lower i detect a lot of false stalls. with a higher vslue i detect no stalls. but eitherway with both higher and lower s values (as low as 3) i could not detect real stalls.

                                          droftartsundefined 1 Reply Last reply Reply Quote 0
                                          • droftartsundefined
                                            droftarts administrators @xorlosch
                                            last edited by

                                            @xorlosch Bearing in mind the limitations of stall detection https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing#Section_Limitations_of_stall_detection

                                            • What motors do you have? Are they high inductance?
                                            • What speeds are you trying to measure? What is your standard printing/travel speeds?

                                            With you X and Y steps of 44.3 steps per mm (which is pretty low, nowadays), and 16x microstepping, this means you get 2.769 FULL steps per mm. If you're printing/moving at 50mm/s, that's 138 full steps per second, which is under the default H parameter of 200 full steps per second. You would need to move at 73mm/s to hit this. An H value of 50 is 18mm/s, which seems very slow, and is unlikely to produce good results. Are you really moving the axes this slow? Try reducing your accelerations (M201) to see if that helps.

                                            You could increase the full steps per mm by changing pulleys, as you've suggested, changing motors to 0.9º step angle motors, or use a gearbox on the motors. It just depends how important Stallguard is to you, and how much you're willing to spend to get it working!

                                            Ian

                                            Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

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