[FR] G34 - Z Steppers Auto-Alignment #196
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
Enable G34 - Z Steppers Auto-Alignment
Feature Workflow
Additional Information
The Mega-S has dual z-motors but the Z_STEPPER_AUTO_ALIGN is commented out and the second Z motor is defined as E1 instead of Z2. More than anything I'm curious why this is defined as such and if it's possible to switch things around to allow the G34 in a BLTOUCH enabled release
I had implemented this feature before, but then expanded it again. It works satisfactorily with a printer with only one Z end stop, but with two Z motors aligning the X axis takes so long that leveling is no fun. Also, you are forced to do this every time you do G28.
For these reasons, I returned to the two Z limit switches and only use the BLTouch to compensate for unevenness.
Sorry.
Is there any chance that this could be implemented again in a separate version?
Having this feature would be really nice to have for many people I think.
It also seems that there is a pullrequest for this open but kinda abandoned?
https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/pull/61
And just a sidenote:
If the auto align takes too long it's usually an indicator that the amplification factor was just set too low.
The Z-axis steppers are quite far out from the measuring points on the Anycubic printers so the amplification factor has to be set higher than default.
Ignore my last comment 😄
I decided to dive into Marlin building myself and found that it actually wasn't too hard to implement this myself.
I have G34 working now with both Z-endstops removed and the BLtouch acting as the Z-min.
The BLtouch also uses the usual pins and not the Z-endstop pins making it easier to use if you already installed the BLtouch according to the guide.
With both Z-steppers somewhat out of sync it now synchronizes them back to 0.02mm tolerance in 3-4 iterations.
Should I create a pullrequest for this so that other people can make use of it as well?
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.