@fcwilt its an anycubic chiron ultrabase

@jmshep That may have been the case in 3.0 because there were still some default pin associations, but in 3.1.1 all default associations are removed and you no longer need to use nil to undefine them. Rather you now must define the pins being used.

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

@dc42 said in PINDA Z-Probe Configuration:

The reading needs to be around 0 when not triggered (no metal under the probe) and 1000 when triggered. Try removing the i1 parameter from your M558 command in config.g.

well, that did the trick. Thanks a lot.

It's not as easy to work with Duet, being used to Marlin for years...

I found it. Researching the answers for @Phaedrux , I realized I was resetting M558 in my homeall.g file which was overriding my M558 from config.g.

You may also find these wiki pages useful:

https://duet3d.dozuki.com/Wiki/Connecting_a_Z_probe#Section_BLTouch
https://duet3d.dozuki.com/Wiki/Test_and_calibrate_the_Z_probe
https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCartesianPrinter#Section_Homing_Z_using_a_Z_probe