Differences

This shows you the differences between two versions of the page.

--- run_bed_mesh [2025/09/14 03:54] – created dshoop
+++ run_bed_mesh [2025/09/14 03:56] (current) – dshoop
@@ Line 23: / Line 23: @@
 Full bed meshes aren't useful for production printing because they are stale almost immediately, yet they are useful to evaluate the shape of the bed. Having a large probe matrix, such as the Elegoo "Professional" size bed mesh, isn't going to tell us significantly more about the overall bed shape than a 6x6 or 9x9 mesh in less time. We'll want to be using Adaptive Bed Meshes run at print time for production prints and they'll have a denser mesh for just the object size.
-Note: the G29 gocode is a marlin gcode and not an actual gcode in [[Klipper], it's implemented as a [[macro]]. Klipper instead implements the ''BED_MESH_CALIBRATE'' command. As such consider using G29 instead of the Klipper command as unreliable and unpredictable as its behavior may change.
+Note: the G29 gocode is a marlin gcode and not an actual gcode in [[Klipper]], it's implemented as a [[macro]]. Klipper instead implements the ''BED_MESH_CALIBRATE'' command. As such consider using G29 instead of the Klipper command as unreliable and unpredictable as its behavior may change.
 ==== Full Bed Mesh ====
@@ Line 38: / Line 38: @@
 Use the following in Orca's Printer Machine Start gcode:
 <code>
+BED_MESH_CLEAR
 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
 </code>