@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

@norder

Probe Offsets are correct Margin about 15mm, because the limitations added by the printhead dimensions

It was the M parameter or better the P parameter i lack off, so many thanks
i suggested the M one are beginning at zero.
at least i was excepting a gap at end like 270/10.

solved then

@sonderzug I thought that was a relation between this post and the last video of ThisOldTony!😀😀😀

@Aquilux A simple thanks but no thanks will suffice.

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

@dc42 said in Probe Accuracy Test Macro [Issues]:

@CCS86 said in Probe Accuracy Test Macro [Issues]:

@dc42: Does it sound like a bug for the probe offset to be applied over and over on repeated G30 P3 X0 Y180 Z-99999 F2000 calls?

That doesn't sound right. Please post the complete macro file you are running, and your config.g file, and tell us which firmware version you are running.

I was originally on 3.0, and now on 3.01-RC4

Unfortunately, I did not save the macro before modifying it. That is my fault.

I did find one error in my code, in asking it to probe at X0, when my probe has a +12mm offset. I feel like the firmware should catch this more gracefully though. It appears that it ignores the endstop switch and the X0 minimum designation, and tries to aggressively get the probe to X0 anyway, which hard crashes into the machine limit and jumps the belts.

Also, it appears that I can't probe more than 32 points before I am "out of range"

f5cb5f29-c4cd-481d-8a66-404810d82659-image.png