-
Notifications
You must be signed in to change notification settings - Fork 77
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
Feature Request: Add a separate variable for the back-off distance after sensorless homing #86
Comments
I believe the difference between this and #78 (I think you meant that issue?) is that this request doesn't change the homing process, but it would add a second variable to distinguish between the backoff distance (homing retract) and the minimum distance required to reliably home with sensorless. |
Yep, mixed up my tabs, thanks! It sounds like they are achieving the same goal, but I like the additional flexibility of this one. |
#78 is mostly asking for built-in checks for sensorless homing failures. Seems you just want a separate configurable variable for minimum homing distance. I think this would be an easy change. Make it default to retract distance, but make it configurable |
Correct, without a minimum distance I find sometimes it doesn't trigger at all. |
@nielsvz is the problem that if you set the retract distance to 20-40, it backs off too much after a successful home? because other than that, it should result in the behavior you want |
#90 will resolve this |
#90 has been merged now |
Sensorless homing is a bit tricky with high current low impedance motors (LDO 2804AH). I find they're most reliable when using the following steps, per axis:
It would be nice if the good sensorless feature had an additional setting, such as
sensorless_minimum_dist
, that value could be compared to the distance moved as well (currently usinghoming_retract_dist
).Homing would then follow this process, per axis:
homing_retract_dist
sensorless_minimum_dist
sensorless_minimum_dist
and re-home if requiredThe text was updated successfully, but these errors were encountered: