Weird Bed Mesh Behavior after Z-Leveling

[natewalck]

Here is the correct data:

config.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/config.g
homeall.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homeall.g
homex.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homex.g
homey.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homey.g
homez.g: https://github.com/natewalck/railcoreiiduet/blob/master/300ZL/sys/homez.g

Doing the same exact process as in post # 18 (with the bed showing 0.1 too low):

And here is the M122 output after each command:

After G28:

0_1561083216074_M122_after_G28.txt

After G32 run 1:

0_1561083226991_M122_after_G32x1.txt

After G32 run 2:

0_1561083235889_M122_after_G32x2.txt

After G28 Z:

0_1561083244610_M122_after_G28_Z.txt

After G29 command (As shown above):

0_1561083256472_M122_after_G29.txt

As you can see, the bed still appears ~ 0.1mm too low using the above sequence.

Also, I don't see "comp offset" anywhere in the M122 outputs. It shows no bed compensation being used at all.

Thanks!

Nate

[dc42]

@natewalck said in Weird Bed Mesh Behavior after Z-Leveling:

Also, I don't see "comp offset" anywhere in the M122 outputs. It shows no bed compensation being used at all.

I guess you are not using firmware 2.03 then. Please repeat the tests using firmware 2.03.

When you home Z, you probe first at 500mm/min then at 50mm/min. What probing speed do you use when you run G29?

Edit: also you are using an old beta firmware version, which is unsupported.