Nozzle rams into bed when not near center
-
G29 89 points probed, min error -0.240, max error 0.062, mean -0.035, deviation 0.046 -
the picture please
-
Sorry about that.
-
did you use M500 to save the calibration or did you put the values in config.g?
-
I did not run an M500 immediately after running the mesh grid compensation, no. I wasn't aware that was necessary, I figured it stored that information automatically after it ran. Thanks for the tip on that.
I will run another auto-calibration, then another mesh bed compensation routine, then I will run an M500 and try the print again.
As a side note, is there ever an instance where you would not want to store the results of a calibration or mesh bed routine? Shouldn't that be done automatically (in a macro maybe)?
-
No change in behaviour after running calibration, G29, M500, then starting print. Nozzle hits the bed near the "top left" part of the print, starts to actually rotate the glass bed with it, and even managed to dislodge one of the magnetic arms from the ball before the emergency stop halted the motion and reset the board.
-
This post is deleted! -
@deltwalrus said in Nozzle rams into bed when not near center:
I figured it stored that information automatically after it ran.
It does, but only while the printer is powered on. The values are lost after a power cycle unless they are either saved to config-override.g with M500 and adding M501 to the end of config.g to load it. Or manually copying the resulting calibration command into config.g
-
@deltwalrus said in Nozzle rams into bed when not near center:
I did not run an M500 immediately after running the mesh grid compensation, no. I wasn't aware that was necessary, I figured it stored that information automatically after it ran. Thanks for the tip on that.
G32 not G29.
-
I just got the new mirrors today, will test them for thermal suitability then give the problematic print another go.
-
It appears either my old glass plate was warped, or in the process of removing it and installing the mirror I fixed this issue, because a larger print is going right now and the bed ramming seems to be resolved.
Go figure.
