Bed on Ulis Notes https://wolf-u.li/en/tag/bed/ Recent content in Bed on Ulis Notes Hugo -- 0.155.3 en Copyright 2006-CURRENTYEAR Uli Wolf - All rights reserved Sat, 27 May 2023 11:52:07 +2700 Klipper: bed_mesh: min/max points too close together https://wolf-u.li/klipper-bed-mesh-min-max-points-too-close-together/ Sat, 27 May 2023 11:52:07 +2700 https://wolf-u.li/klipper-bed-mesh-min-max-points-too-close-together/ <p>After having implemented <link rel=dns-prefetch href=//github.com /> <a href="https://github.com/kyleisah/Klipper-Adaptive-Meshing-Purging" title="KAMP (Klipper Adaptive Meshing)" target="_blank" rel="nofollow noopener noreferrer" > KAMP (Klipper Adaptive Meshing)&nbsp;<svg xmlns="http://www.w3.org/2000/svg" class="icon" aria-hidden="true" focusable="false" viewBox="0 -128 512 640"> <path d="M384 320c-17.67 0-32 14.33-32 32v96H64V160h96c17.67 0 32-14.32 32-32s-14.33-32-32-32L64 96c-35.35 0-64 28.65-64 64V448c0 35.34 28.65 64 64 64h288c35.35 0 64-28.66 64-64v-96C416 334.3 401.7 320 384 320zM488 0H352c-12.94 0-24.62 7.797-29.56 19.75c-4.969 11.97-2.219 25.72 6.938 34.88L370.8 96L169.4 297.4c-12.5 12.5-12.5 32.75 0 45.25C175.6 348.9 183.8 352 192 352s16.38-3.125 22.62-9.375L416 141.3l41.38 41.38c9.156 9.141 22.88 11.84 34.88 6.938C504.2 184.6 512 172.9 512 160V24C512 10.74 501.3 0 488 0z"/> </svg></a> on my Klipper instance, no print worked anymore as i always got the following message in the Klipper Console:</p> After having implemented KAMP (Klipper Adaptive Meshing)  on my Klipper instance, no print worked anymore as i always got the following message in the Klipper Console:

1

bed_mesh: min/max points too close together

The reason is relatively simple - it is a bug  in my currently used slicer, OrcaSlicer . It appears to be related to having multiple build plates visible in the slicer - hence it might not happen to you immediately as long as you do not use that feature.

The solution is to either slice only single plates, to switch of “Exclude Objects” or to simply update OrcaSlicer to a version higher or equal to 1.6.2 and you should be able to get rid of this issue.

]]>