Height map has a substantial Z offset error with mesh
-
Back on topic tho... I'm running a new bed mesh now with the bed heated up to 60c... I'm sure the temp will be more accurate than before now.
but mesh has no luck, bed is still floating in midair on the mesh for some reason..
-
but it does work if you probe before every print?
-
@veti that will have same result, basically my mesh is like 0.7 mm higher than what its supposed to be, I can use the Z baby stepping in web gui to lower the nozzle to around -0.95 mm and it'll print OK. Before the lowest I have used is like -0.25 mm
-
i am guessing the you are doing the homing with the hotend and bed turned on.
did you create the heighmap under the same conditions? -
@veti yes everytime mesh is done it is at printing temp
-
@dc42 do you have any idea what could cause that behavior. I tried to help him find the issue but since z-homing with the mini IR works flawlessly I can't think of what it actually is.
it seems like it just adds a certain offset value to the probe values at some point for no reason.
as if z0 gets redefined after initial z homing. -
Just an update.. I did absolutely no modifications beside the heater stuff yesterday, however today i just did another mesh and there was 1 point that was below 0 and the warning message went away. I started another print and my z babystepping value went from -0.95mm to -0.45mm which is much better than before but still not what I had before which is max -0.25mm.
-
you are probing on glass with an Ir sensor.
check that the point where you are probing does not have any special feature, since its the center and that is where the thermistor is.do check the repeatrability of your probe at different places.
https://forum.duet3d.com/topic/6962/m48-measure-z-probe-repeatability-and-print-to-serial-output/7 -
Hey Veti,
no he's not probing on glass he uses a TH3D sheet, completely opak and it worked flawlessly before. That phenomenonm started to appear all of a sudden with nothing changed. Btw it got better again, but the repeatability is still rather bad.
Switchin the printer off and on again usually trows the settings off by about 0.3mm wich is way too much imo. -
I'm now having the identical issue. Origami did you ever solve this issue you were having???
-
I'm also seeing the problem.
Home Z works flawlessly, sets the distance exactly right, but mesh is always too high, which impacts the quality of the print...
-
Im wondering if it might have somthing to to with the distance of the sensor from the print surface, more than the progaming or the ver. Instaled. Could a new ver. affect the readout of bed leveling mesh? And does the value returned by the senor get funky at a certain hight??? I know sensors have a sweet spot. That would chainge with type of sensor Just a thought
-
That is a good question.
What I see is really weird.
I run G28 - everything gets set perfectly. I check if the nozzle touches the bed on z0 - it does. I move the carriage around a bit, come back to probing point - still, nozzle touches the bed just fine.
But the moment I hit G29 - it seems as if 0.25 is added to the readings. I don't exactly understand why only then this happens.
-
@pkos said in Height map has a substantial Z offset error with mesh:
But the moment I hit G29 - it seems as if 0.25 is added to the readings. I don't exactly understand why only then this happens.
We are missing a lot of information - you should start a new topic.
Did you move to the center of the bed and issue a G30 before creating the height map AND before loading the height map?
Frederick
-
Im encountering the same issue. My setup is a Duet Ethernet 2 + PanelDue 7i on an Ender5plus mechanicals which uses a BLtouch probe. My mesh has ~.5mm offset from Z-zero which I can assure you is not correct. The mesh values are generated by using the "built in"
mesh compensation routine P0. My observation is that the velocity which this routine runs the Z travel during probe is significantly faster than the velocity commands I use in my manual level macros. I would assume that the the velocity would affect the trigger point by the fixed sampling + filtering of the signal. -
@JKonopacki said in Height map has a substantial Z offset error with mesh:
The mesh values are generated by using the "built in" mesh compensation routine P0.
Are you talking about the symbol below the P0?
There is no built-in routine - that symbol just executes a G32 command which in turn invokes bed.g.
The intended purpose of bed.g is to implement one of the bed leveling features.
Somehow a lot of folks end up using it for mesh bed compensation which is something else entirely.
If it behaves differently it has something to do with your code.
Frederick
