You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using 4 Point Level, leveling mesh is applied if available resulting in ever growing Auto Leveling mesh values if used sequentially.
Steps to Reproduce
Level your bed somewhat - manually, for instance
Run Auto Leveling through printer menu
Note mesh values
Run 4 Point Level with a sheet of paper
Run Auto Leveling again
Note the entire grid up by approx the thickness of the sheet of paper
Iterate until run out of adjustment screw/spring length if you like :)
Expected behavior: [What you expect to happen]
No mesh offset applied, so 4 Point Leveling is true to the printer, not the current Auto Leveling mesh.
Actual behavior: [What actually happens]
Mesh offset is applied, so the 4 Point Leveling is true to the current Auto Leveling mesh, not the printer geometry.
Additional Information
Hardware: Mega_S_TMC_BLT_10, additional extruder with single nozzle setup, activated by toggling enable pins for the drivers.
Workaround: Issue M420 S0 through a terminal application before engaging 4Point Level.
The text was updated successfully, but these errors were encountered:
Bug Description
When using 4 Point Level, leveling mesh is applied if available resulting in ever growing Auto Leveling mesh values if used sequentially.
Steps to Reproduce
Expected behavior: [What you expect to happen]
No mesh offset applied, so 4 Point Leveling is true to the printer, not the current Auto Leveling mesh.
Actual behavior: [What actually happens]
Mesh offset is applied, so the 4 Point Leveling is true to the current Auto Leveling mesh, not the printer geometry.
Additional Information
Hardware: Mega_S_TMC_BLT_10, additional extruder with single nozzle setup, activated by toggling enable pins for the drivers.
Workaround: Issue M420 S0 through a terminal application before engaging 4Point Level.
The text was updated successfully, but these errors were encountered: