Stall detection works, but not during moves to hard stops?
-
I have stall detection successfully triggering during prints if I turn the S value down 2 notches to S17 or below during print:
M915 X Y S19 F0 R3
driver-stall.g executes here and displays a message and rehomes.
However, when doing moves to hard stops with the axis limits removed, it detects no stall and the steppers skip, no matter how low I make the S value (-63) or how fast the move is? I also tried changing H and motor torque during the test, nothing has made it trigger even once here.
-
@r3cvr said in Stall detection works, but not during moves to hard stops?:
However, when doing moves to hard stops with the axis limits removed, it detects no stall and the steppers skip, no matter how low I make the S value (-63) or how fast the move is? I also tried changing H and motor torque during the test, nothing has made it trigger even once here.
I think it would help if you explained this a little more. What sort of move are you doing here? Is it a normal move during a print, or is it some "special" move, like homing, tool change etc? Providing the actual gcode of the move would probably help us understand what is happening.
Can you also provided details of your board, firmware version and the contents of your config.g file and any macro files that are involved in either the move in question (so homing files if this is a homing move) or configuration of the printer.
-
@gloomyandy The moves that do not trigger stall detection are manual moves from DWC, or issuing gcode to the console like G91; G1 X25 F5000 to move the toolhead (or Z platform) past the physical stops so the motor hard stalls.
Machine is a FlashForge Creator Pro with Duet2Wifi 3.4.5
An additional experiment I tried was setting the motor stall up as an axis endstop. That didn't work either. Although I haven't been able to gather from the documentation if two endstops on a single axis are supported (microswitch and one end and stall detection at the other).
Config attached. config-2.g
