Reported stall detection in console while printing

jay_s_uk

@moth4017 yes, you can adjust the S value https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m915-configure-motor-stall-detection
if its detecting a stall but there isn't one then you need to reduce the sensitivity somewhat

moth4017

@jay_s_uk

o yes i know about that thanks im up to s127 H400 still get the warnings

pro3d

@moth4017

I thought you turned off stallguard after the homing sequence? Can you do this?

moth4017

@pro3d I have forced the stepper drivers into spread cycle after homing

oliof

@moth4017 It's easy to get stall detection misreports on Z from fast Z hops. You could try M915 Z R0; that should disable any logging on the Z axis.

moth4017

@oliof
Its not reporting z its driver 0 an 1 which is the A B motors

oliof

@moth4017 Ah, I misread the logs. You could still do M915 P0:1 R0 to disable the logs.

What's driver 5 though? that's also triggering a stall warning.

moth4017

@oliof Hi Driver 5 is a Z motor, i think that stall was correct because it had homed at that point, i seem to get many driver 0 an1 stall warnings, i know i can turn the logging off but why are there so many , i can get as many as 20 to 30 while printing

oliof

@moth4017 it's just back emf from direction changes. Maybe try to reduce jerk.

moth4017

@oliof Are yes jerk would do that, thats worth a try, i thought stallguard was only active in stealth chop, or does it always monitor back emf

oliof

@moth4017 I'm pretty sure that you can't really turn it off without resetting the driver completely after you used it once.