No matter the scan_overshoot setting I set (tried none set, 0, 1, 8), the bed mesh scan overshoots the mesh boundaries, leading to a crash if the probe count in X is set to less than 30.
The scan area is set to 30x30 to 270x270, which should not conflict with the AWD’s no-go zones.
The Siboor AWD has 20x50mm (X by Y) no-go/crash zones at both ends of X and Y=0. With 30 probe points, the bed mesh scan doesn’t attempt to enter these zones, but with lower probe_counts, it does.
Does anyone have any suggestions? Is it a bug I could fix in klippy?
I’m also considering writing a prohibited_zone patch for klippy, but IDK if it would be a welcome addition, and it might be hard to make it a plugin.
Absolutely a bug, luckily not in Klipper but in your config. The mesh boundaries are relative to the probe position, so you need to take the offsets into account.
The cartographer Klippy modification overrides BED_MESH_CALIBRATE with its own calibration routine. It’s possible that stock Klipper options such as scan_overshoot do not work correctly with it. Perhaps someone that is currently running a cartographer probe can provide assistance, otherwise you may want to consider asking the cartographer devs.
The overrun happens in X, and my probe offset in X is 0. Essentially, I want the tool head not to try to enter the strips ((0, 0), (20, 300)) and ((280, 0), (300, 300)) ((X, Y)). It is not trying to probe there but creates a sweeping motion there. However, if probe_counts is less than 30 it reaches into these regions, I think with 30, it goes something like X=21.
[scanner]
mesh_overscan: 7
# Distance to use for direction changes at mesh line ends. Omit this setting
# and a default will be calculated from line spacing and available travel.