# Adaptive mesh leveling not working anymore

**URL:** <https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011>\
**Category:** General Discussion\
**Created:** [October 14, 2025, 12:52pm UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011 "2025-10-14T12:52:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![printeruser](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@printeruser](https://klipper.discourse.group/u/printeruser)\
**Post date:** [October 14, 2025, 12:52pm UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011/1 "2025-10-14T12:52:54Z")

</div>

### Basic Information:

Printer Model: Prusa i3MK3S+  
 MCU / Printerboard: Einsy  
 Host / SBC: Pi5

[klippy\_adaptive\_layering\_notworking.log](https://klipper.discourse.group/uploads/short-url/x8nulNwRn2Arpr5VlPVy8ShLmEB.log) (283.2 KB)

klippy.log

_Fill out above information and_ _ **in all cases attach your** _ **`klippy.log` _file_** (use zip to compress it, if too big). _Pasting your_ `printer.cfg` _is **not** needed_  
_ **Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there** _

### Describe your issue:

Hello, I am using Klipper with OrcaSlicer. In the past, Adaptive Mesh Leveling was working fine but not anymore. As I recall, the problem started when I kept getting a “bed\_mesh: min/max points too close together” error and no print job could be run. If I recall correctly, from the internet, I came across a post on solving it by disabling “Label objects” under Process (Global)→Others→G-code output. in the slicer. Since then, the error disappeared and I could print again. However, the printer lost the ability of Adaptive Mesh Leveling. At the beginning of each print job, the printer goes through the entire build plate to measure the level rather than just the region where the print will be made. How can I get back Adaptive Mesh Leveling and also avoid that “bed\_mesh: min/max points too close together” error at the same time?

---

<div class="post-metadata">

**Author:** ![printeruser](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@printeruser](https://klipper.discourse.group/u/printeruser)\
**Post date:** [October 17, 2025, 1:12pm UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011/2 "2025-10-17T13:12:26Z")

</div>

Hello, the problem still remains. Any possible way to fix this?

---

<div class="post-metadata">

**Author:** ![why\_me1](https://avatars.discourse-cdn.com/v4/letter/w/df788c/32.png) [@why\_me1](https://klipper.discourse.group/u/why_me1)\
**Post date:** [October 17, 2025, 2:46pm UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011/3 "2025-10-17T14:46:39Z")

</div>

label object is required for adaptive meshing to work. when you disable it, klipper will do a full mesh.

Your log does not contain the error. but my guess would be that your faulty regions of your bed are causing some shifts that result in this error.  
Adding a adaptive margin to your mesh command might help. Try “BED\_MESH\_CALIBRATE ADAPTIVE=1 ADAPTIVE\_MARGIN=5“ for example.

---

<div class="post-metadata">

**Author:** ![printeruser](https://avatars.discourse-cdn.com/v4/letter/p/ac8455/32.png) [@printeruser](https://klipper.discourse.group/u/printeruser)\
**Post date:** [October 17, 2025, 10:29pm UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011/4 "2025-10-17T22:29:54Z")

</div>

This seems to be working. Thank you. Not sure if it is related to the “Move out of range” error which happened when I issued a M600.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [November 17, 2025, 8:30am UTC](https://klipper.discourse.group/t/adaptive-mesh-leveling-not-working-anymore/25011/5 "2025-11-17T08:30:35Z")

</div>

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