-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
[FR]: Use screw locations for corrections #553
Comments
I have been working on a method to average the quadrants of the probed locations to get a simple plane for this purpose. I would also recommend you look into my other plugin Bed Leveling wizard, and potentially even better the Autobim plugin that will guide you through the leveling process. translucent overlay of reference plane I do have options in 1.1.2rc2 that allow you to define margins which kinds of fits some of this request, but still the calculations to determine exact offsets from those aren't exactly what you are after for adjustments and the math to intercept that surface plane is beyond my ability.
just to be clear, the firmware is doing the adjustments in all cases, the plugin just visualizes the points that the firmware has determined from probing. |
Is your feature request related to a problem? Please describe.
The graph on UBL can be quite extensive, as the more probe points, the more detailed the software corrections can be.
However, most beds only have 3 or 4 screws to align the bed.
Therefor the extensive list of 'angle adjustments is rather useless.
Describe the solution you'd like
It would be great if you are able to submit the screw locations in x,y, or in offset from the bed edge.
The angle adjustments would/could/should then only be needed for the differences between those 4 (or 3) points. The rest is mostly built in bed level issues or will straighten out when adjusted.
Describe alternatives you've considered
an alternative can be to just probe the bed in those 4 points, but that makes the mesh-adjustments by the software obsolete
Additional context
The text was updated successfully, but these errors were encountered: