# Faster QUAD\_GANTRY\_LEVEL Macro

**URL:** <https://klipper.discourse.group/t/faster-quad-gantry-level-macro/19044>\
**Category:** Macros\
**Created:** [September 26, 2024, 5:54pm UTC](https://klipper.discourse.group/t/faster-quad-gantry-level-macro/19044 "2024-09-26T17:54:12Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![garethky](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/garethky/32/956_2.png) [@garethky](https://klipper.discourse.group/u/garethky)\
**Post date:** [June 2, 2025, 6:16pm UTC](https://klipper.discourse.group/t/faster-quad-gantry-level-macro/19044/13 "2025-06-02T18:16:19Z")

</div>

I actually did this with the load cell recently. You can pass the `PROBE_SPEED=5` argument to `QUAD_GANTRY_LEVEL` to override the probing speed.

There is a lot to be said for the idea that faster speeds shake the printer and reduce accuracy. A better idea is to use lower speeds but for much shorter distances for the same speedup. e.g. my `sample_retract_distance` is 0.3mm and my standard probing speed is 2mm/s.

I have a [thread](https://klipper.discourse.group/t/adaptive-horizontal-move-z-for-bed-mesh/23455) about making the `horizontal_move_z` a relative move so it can adapt to taco bed shapes. IMHO, the focus on fast probing exists largely because the current `horizontal_move_z` behavior in klipper is bad for automated probes.

---

_[View the full topic](https://klipper.discourse.group/t/faster-quad-gantry-level-macro/19044)._