-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug. Stallguard not functioning without pwm_autoscale on tmc2209 #6
Comments
@wakass I tend to agree, in fact it seems the drivers will operate in open loop with velocity based current scaling (requiring motor specific settings) with pwm_autoscale set to false. In this context the motors will stall during jogging regardless of stallguard threshold. On the other hand when pwm_autoscale is set to true stalling is only occurring during homing with reasonable stallguard threshold settings that work with my motors. |
👀 I've been trying to get stallguard working for days! I'll give this a try too. Otherwise I'm having trouble with are setting the tCoolThrs and TPWMThrs to any value other than 0, and the driver status is always reporting stealth as 0 (meaning spreadcycle and not stealthchop) |
It looks like this boolean is set to true in the version of grblHAL I downloaded in Dec 2024. Thanks! |
It was fixed a year ago. |
Stallguard does not function properly (or as expected?) on a 2209 driver. The following line is relevant, and setting autoscale to true recovers proper stallguard behaviour on my system:
Trinamic-library/tmc2209hal.c
Line 162 in 9eae92b
I'm not sure how this works in other driver modules, but I can't find any reference on stallguard requiring disabling pwm_autoscaling. Just tcoolthrs < tstep < tpwmthres
The text was updated successfully, but these errors were encountered: