Adaptive Bedmesh: "min/max points too close together"

General Discussion
1

Basic Information:

Printer Model: Ender 5 Plus
MCU / Printerboard: BTT SKR 3 EZ
Host / SBC: Mainsail, Raspi 4B
klippy.log

Describe your issue:

Adaptive Bedmesh leveling reports:
“bed_mesh: min/max points too close together”
while want to print a tiny piece.

klippy.log (7.3 MB)

2

Seems strange. Can you post the gcode?
From the mesh it looks like your object is a line with 0.42mm width and Klipper complains that it cannot fit a mesh there

3

Sure, here it comes:
BLTouch-Arm-rear_PLA_54m29s.gcode (2.1 MB)

4

I’m not sure. It looks like Klipper is misinterpreting the bounding box of the object, but this needs to be looked at by some experts.
Maybe @Arksine or @voidtrance could take a look at it.

5

I had the same issue with a very thin piece.
Re-slicing with prusa slices yielded the same result.
I “solved” by rotating the piece 180° on Z and slicing again, even though it shouldn’t have done nothing…

6

From your config:

[bed_mesh]
speed = 120
horizontal_move_z = 5
mesh_min = 20,0
mesh_max = 350,200

From the sliced file:

CENTER=125.636,236.881 POLYGON=[[87.555,204.586],[87.555,263.085],[147.306,263.085],[147.306,204.586]]

All of these points are outside of your defined mesh_max, so the code clamps it and ends up with an unusable area:

Original mesh bounds: ((20.0, 0.0),(350.0, 200.0))
Adapted mesh bounds: ([82.555, 199.586],[152.306, 200.0])
1 Like
7

It looks like it is trying to create a 3,3 probe in X and Y and the minimum probe has to be atleast 1mm apart where it looks like from the log your model is shows as

Adapted mesh bounds: ([82.555, 199.586],[152.306, 200.0])

According to the gcode you are using adaptive, I would suggest adding a margin. so that no matter what you wont fall below the 1mm probe distance. If you cant do that then i suggest just adding a simple skirt that will allow for a larger probe area. or just rotate your model 45 degrees.

BED_MESH_CALIBRATE ADAPTIVE=1 ADAPTIVE_MARGIN=5

But since you are using orcaslicer then i would suggest adding this to your machine start gcode and then use the adaptive mesh settings under your printers basic information tab. There is still a few quirks that i have noticed that need to be reconciled using adaptive. Plus you can specify your probe distance.

Add this before homing but after the bed temperature command
BED_MESH_CLEAR

Then add this after homing
BED_MESH_CALIBRATE mesh_min={adaptive_bed_mesh_min[0]},{adaptive_bed_mesh_min[1]} mesh_max={adaptive_bed_mesh_max[0]},{adaptive_bed_mesh_max[1]} ALGORITHM=[bed_mesh_algo] PROBE_COUNT={bed_mesh_probe_count[0]},{bed_mesh_probe_count[1]} ADAPTIVE=0 ADAPTIVE_MARGIN=0

8

This will not help, because it’s not the problem (and there’s already a margin configured.) The issue, as I already pointed out, is the incorrect mesh_max.

9

Sorry, you are right, i didn’t even think about looking at that in the log and i didn’t even open the gcode in a viewer assuming that the model was just tiny. Either they need to let the slicer specify all of the parameters in my “slicer defined bed_mesh_calibrate” like my second example, redefine the mesh_max, or move the model within the existing defined mesh boundaries.

10

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.