Warning: the height map has a substantial Z offset

printingforfun

@norder sorry if I offended you,
Vanadium Nozzle 0,40 -35.80€
Mosquito Thermistor -29.00€
Mosquito 24V 50W Heater -22.50€
Mosquito 24V Fan -7.90€
Mosquito Boron Nitride Paste -10.22€
Mosquito Hotend -153.41€
Shipping -20€
Total:278.83€
When you put that in the contents of the hot end model and price, you are probably take a good care of it....

printingforfun

@norder with IR probe just want to rule out the possibility of a faulty Omron probe, the problem is that the mesh bed is up, didn't change anything on the printer or the settings except the z offset because probing the bed,now shows bed is up significantly, as the Warning and title of the post is saying, and yes, I make at least 10 trigger height and make a average of the results(with a clean nozzle and without filament in the hotend, with a printing temperature for bed and hotend, have macros for PID tuning, depending on what material is used, mostly PETG-222,80 / ABS,ABS+,ASA -240,100)

printingforfun

@norder thanks, anyway!

Norder

@printingforfun said in Warning: the height map has a substantial Z offset:

sorry if I offended you,

No, you didn't insult me.
I know what it's like to have such an expensive hotend.
Look in my signature, there's a link to my print head, it's almost twice as expensive.
Nevertheless, one can be careless and forget to wipe the nozzle tip before determining the Z offset.

If you had a different z-offset value before the firmware update and everything was OK and you now have a different z-offset value in the config.g and the mesh of the heightmap is still hovering over the print bed, then the problem is already there solved.
Enter the old value again or measure the Z offset again.

Or did I misunderstand something here from the Google translation?
You followed @Phaedrux tip, and if that didn't solve the problem... Z offset value !

Google Translate
-- Original Text --

Nein, Du hast mich nicht beleidigt.
Ich weiß wie es ist so ein teures Hotend zu haben.
Gucke in meiner Signatur, dort ist mein Druckkopf verlinkt, der ist fast doppelt so teuer.
Trotzdem kann man unvorsichtig sein und vergessen vor dem ermitteln des Z-Offset die Düsenspitze vorher abzuwischen.

Wenn Du vor dem Firmware Update einen anderen Z-Offset Wert hattest und alles OK war und Du jetzt einen anderen Z-Offset Wert in der config.g stehen hast und das mesh der heightmap schwebt weiter über dem Druckbett, dann ist das Problem ja schon gelöst.
Alten Wert wieder eintragen oder Z-Offset neu vermessen.

Oder habe ich hier durch die Google Übersetzung etwas falsch verstanden ?
Den Tipp von @Phaedrux hast Du ja befolgt, und wenn das Problem dadurch nicht behoben werden konnte... Z-Offset Wert !

Phaedrux

@printingforfun said in Warning: the height map has a substantial Z offset:

proximity probe Omron 5mm

Does it have a consistent trigger height at all locations on the bed?

How are you measuring the trigger height?

If you use homeall and then command the nozzle to Z0, does it touch the bed, or is there a gap?

printingforfun

@phaedrux Does it have a consistent trigger height all locations on the bed?
Yes, the error Is marginal about 0.02-0.04max

How are you measuring the trigger height?
G30 S-1

If you use homeall and then command the nozzle to Z0, does it touch the bed, or is there a gap?
It's touching the bed, no gap, Z=datum is as set initially, Z0

I don't get it how or why does the extra +2.5-3.0mm difference comes from?
Just printed and crimped the wires for the duet IR probe and will mount it tomorrow, if that shows the same results, I'm gonna compile everything from scratch.... Thanks for your effort!
I see that I'm not the only one with this problem and dc42 moderator is puzzled by this and provided similar advice to no avail....

Phaedrux

And when you measure the trigger height you are putting it into G31 in config.g?

If you send G31 by itself, does it report back the same value?

Can you homeall, then move the probe to the center of the bed, and send G30 to probe. Then send G29 S0 to create a fresh heightmap and see how it looks?

What other thread are you alluding to?

printingforfun

@phaedrux And when you measure the trigger height you are putting it into G31 in config.g?
Yes

If you send G31 by itself, does it report back the same value?
Yes

Can you homeall, then move the probe to the center of the bed, and send G30 to probe. Then send G29 S0 to create a fresh heightmap and see how it looks?
Same, no change:-(

What other thread are you alluding to?
Just google: Warning: the height map has a substantial Z offset.... the first 5-7 results, I think the majority is from this forum... Don't get me wrong that guy dc42(I think) is for me number1 in anything related to Duet...

Phaedrux

@printingforfun said in Warning: the height map has a substantial Z offset:

Just google: Warning: the height map has a substantial Z offset.... the first 5-7 results,

Well the warning is telling you there is an offset. The reason is usually a misconfiguration or order of operations out of whack.

Can you make a video of the process so we can see it in action?

Norder

@printingforfun
Have you ever tried to reduce the immersion speed of the probe when measuring?
If the speed is too high, some probes may supply incorrect values because the motors cannot stop as quickly.
So I would suggest switching from F400 to F200 for testing purposes.

M558 P5 C"zprobe.in" H9 F400 T6000 ; set Z probe type to unmodulated and the dive height + speeds

printingforfun

@norder already tried that with less than half of the speed that I have.... F160