DC42 IR probe

[downshift64]

been using the probe for awhile been working great, now i cant figure out how to fix this

in console it reads 1.65 the status window reads 1.62. Iam getting G29
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
25 points probed, min error 0.085, max error 0.322, mean 0.196, deviation 0.055
Height map saved to file 0:/sys/heightmap.csv
i have ran the nozzle to the bed used G92 Z0 to set the offset over and over,
the i move the head up 5mm and G30 -S1 that's where the 2 different offsets come in i have tried using both and come out with the same result, its been working great i don't know what happened.

[dc42]

@downshift64 do you have mesh compensation enabled? I think the Z height reported in DWC is the height after compensation, whereas the stop height reported in the console is the raw value before compensation is applied. Do they read the same if you use G29 S2 to disable compensation?

[downshift64]

@dc42 i will look and see if i do but i havent changed anything, i finished a print then started a new print and and that warning popped up and my height map went from around .05 .095 to .350 above the plate

[downshift64]

@downshift64 === Move ===
DMs created 83, segments created 6, maxWait 232449ms, bed compensation in use: mesh, comp offset -0.180

[downshift64]

@downshift64 === Move ===
DMs created 83, segments created 3, maxWait 315314ms, bed compensation in use: mesh, comp offset 0.000

does this need to have a offset instead of zero

[downshift64]

i dont know what i did i have been using the IR probe for maybe 6 or more months and the mesh has always been good green light blue area, and the first point has always been close to zero , now its this

[downshift64]

i cant figure out how this happened to fix it
G29
Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
25 points probed, min error 0.115, max error 0.342, mean 0.224, deviation 0.056
Height map saved to file 0:/sys/heightmap.csv

[Phaedrux]

Please share your config.g and homing files. Bed.g if you use it. Slicer start gcode as well. For completeness also send M122 and M98 P"config.g" in the gcode console and copy and paste the results here.

[Norder]

@downshift64
Did you "manually" level your print bed before retrieving the mesh?

If I get this error message, the print bed has shifted, so I have to level it manually on the level wheels.

This can happen when the print surface has been reground or a different bed temperature has been set and the print bed has a different expansion.
Some cross holders (holder between the print bed and the printer frame) bend when a printing plate is cleaned with excessive pressure.

So take a piece of paper or a feeler gauge with 0.05mm or 0.1mm thickness and level the print bed with the bed level screws.
Paper or feeler gauge between nozzle and print bed.

Then you call up the mesh again with G29.

Google Translate
-- Original Text --

Hast Du Dein Druckbett "manuell" gelevelt bevor Du das Mesh abgerufen hast ?

Wenn ich diese Fehlermeldung bekomme, hat sich das Druckbett verstellt, so dass ich es manuell an den Levelrädern leveln muss.

Das kann passieren wenn die Druckoberfläche neu geschliffen wurde oder eine andere Betttemperatur eingestellt ist und das Druckbett eine andere Ausdehnung hat.
Manche Kreuzhalter (Halterung zwischen Druckbett und Druckerrahmen) verbiegen sich wenn eine Druckplatte mit zu hohem Druck gereinigt wird.

Nimm also ein Blatt Papier oder eine Fühllehre mit 0,05mm oder 0,1mm Stärke und level das Druckbett mit den Bettlevelschrauben.
Papier bzw Fühllehre zwischen Düse und Druckbett.

Danach rufst Du erneut das Mesh mit G29 ab.