Another Mesh leveling thread…!
-
Your welcome, I borrowed it off someone else here at some point.
-
Another Question!
Using G29 for bed leveling, does that move the Z physically like G32 does? Or does it handle the transform differently?
-Casey
-
Yes it moves the head in the Z direction to follow the contours of the bed.
-
I'm curious about a couple things with mesh bed leveling.
Does it move the head up and down to account for bumps or is it just a plane correction?
If you have a slight effector tilt (that is compensated for via H adjustments in the bed.g), how does the G29 command adjust for this (if at all?)
Thanks!!
-
G29 compensation moves the head up and down to follow the contours of the bed. Long moves get segmented into shorter ones to make this possible.
If you have varying Z probe trigger height due to effector tilt or anything else, currently the only way to compensate for it is to edit the height map file and reload it.
-
Would you do that the same way you do the h values in bed.g? For each point measured, calculate the difference from the center measurement and add/subtract it to the height map point?
-
Yes.
-
If you taper off with 10mm does that mean that it starts allready on second layer and has zero compensation at 10mm?
I did a G29 today after i printet a part on glass bed with glue on it. I had a huge error of 0.5mm where the printed part was peeled off compared to the rest of the bed. Normally it is within 0.1mm. Is this normal? Does it mean I only should run G29 with a washed glass plate? Really annoying as I sometimes have to take glass on/off for removing print and then I'd like to run G29 again to be sure it's seated the same as last time. Now I have to wash between every print
-
mesh leveling has caused me quite a lot of problems. I'm starting to wonder if it's really useful to me.
I've added G29 to my bed macro, and my slicer adds a G32 at the beginning of the gcode files.
Most of the time it works ok, but every now and then, at least once a day it fails. Probably because glass is not cleansed enough, or sometimes some bits of filament fell on the bed during the probes…
How about adding a new parameter to specify a acceptable deviation from G29 ?
My maximum deviations are often between -0.08 and 0.08. I'd love to be able to skip the whole G29 results if there are values outside of this range. (I guess I would also love RRP to cancel the print if G29 is triggered from a gcode file) -
Unless you are swapping bed plates around, why don't you use G29 S1 to load a known good height map instead of probing each time?
-
yes, that's what I thought.
I've been spending a lot of time playing with my duet, which is under the bed, so I decided to put G29 in bed macro. I guess I don't need it anymore.i guess I don't need to run G32 before every prints either.
