@tcamguil thanks for confirming this.

@e4d Please post your config.g and the response to M122. An overview picture of your machine would be helpful too, as well as the bed.g you are using. Because it looks to me like you have a tramming problem in the X axis (linear rods not parallel), and the dip in the Y axis is probably caused by the weight of the X gantry. It looks like you're using a pretty thick, solid piece of aluminium for the bed, which is likely to be pretty flat, so the deviation in the bed is likely to be something else.

What kind of probe are you using? If the probe is offset from the nozzle, and the tool head is heavy, a twist in the axis due to the weight of the tool may cause an over- or under-reading by the probe. A small twist in the axis can cause a big deviation in probed height.

Ian

@merlin246 perhaps use

M376: Set bed compensation taper

Then after the taper height I guess there shouldn't be any mesh related z moves for the rest of the print?

Just a thought...
Cheers
Barry M

@Veti that's a very good point.

Fixing it to the correct values, there is no more error.
G31 P500 X-22 Y0 Z0.1

Thanks for pointing that out!

@osterac said in Automatic tilt correction of bed mesh:

The G29 J parameter does this:

I believe this is on the wish list for implementation already.

If anyone is interested, my friend and I developed a Cura post processing script.

You pass it a single parameter (mesh spacing), and it parses the first layer gcode for min/max X and Y coordinates, and then replaces the M557 line in your start gcode.

LevelingMeshOptimizer.py.txt

Just remove the .txt, and drop it here: C:\Program Files\Ultimaker Cura 4.5.0\plugins\PostProcessingPlugin\scripts\

You must have a static mesh leveling command in your start gcode, like: M557 X0:200 Y0:200 S20