# Z Tilt Adjust making bed alignment far worse

**URL:** <https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583>\
**Category:** General Discussion\
**Created:** [August 31, 2024, 9:36pm UTC](https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583 "2024-08-31T21:36:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![m.lewis.everley](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/m.lewis.everley/32/13875_2.png) [@m.lewis.everley](https://klipper.discourse.group/u/m.lewis.everley)\
**Post date:** [August 31, 2024, 9:36pm UTC](https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583/1 "2024-08-31T21:36:17Z")

</div>

SOLVED:

Thanks to this post on Reddit: [Reddit - Please wait for verification](https://www.reddit.com/r/klippers/comments/q2xqio/z_tilt_moving_wrong_direction/)

I actually had my motor assignments wrong… What a prat! I swapped the pin assignments over in config and now it works perfectly.

### Basic Information:

Printer Model:  
Custom DBOT style CoreXY with BLTouch and 400x400 bed.

MCU / Printerboard:  
BTT Octopus 1.1

Host / SBC:  
Official Raspberry Pi Zero 2w

[klippy.log.zip](https://klipper.discourse.group/uploads/short-url/dJog4gk64JnBInXRy4e220b7uB4.zip) (575.5 KB)

### Describe your issue:

So I have pretty much finished a custom CoreXY printer build using a load of old parts I had lying around.

Tuned resonance compensation and pressure advance and getting some nice prints.

At the moment the bed is managed by duel independent Z stepper motors and every now and then I have to check that both are aligned and then re-align them manually, I wanted to use something like `G34` in Marlin to automatically probe using the Z Probe (knock off BLTouch) to ensure the bed steppers are aligned.

Reading the docs, looks like Z TILT ADJUST should do this? But whenever I try I end up with one side of the bed a good 5 or 6 mm lower than the other and then Klipper errors out with `Retries aborting: Probed points range is increasing`.

I have also noticed that occasionally the probe reported invalid results while performing a bed mesh and then had to re-probe.

Is this just because of a crappy probe? My last probe was also the same, but that was also a crappy clone BLTouch.

Cheers,

Mo

Console Log:

```auto
22:13:29 $ G28 X
22:13:34 $ G28 Y
22:13:37 $ G28 Z
22:17:15 $ Z_TILT_ADJUST
22:17:21 // probe at 0.000,194.000 is z=0.981250
22:17:27 // probe at 0.000,194.000 is z=0.972500
22:17:35 // probe at 320.000,194.000 is z=1.713750
22:17:41 // probe at 320.000,194.000 is z=1.700000
22:17:41 // Making the following Z adjustments:
// stepper_z = -0.267773
// stepper_z1 = 0.904805
22:17:41 // Retries: 0/3 Probed points range: 0.730000 tolerance: 0.050000
22:17:50 // probe at 0.000,194.000 is z=0.214023
22:17:56 // probe at 0.000,194.000 is z=0.187773
22:18:04 // probe at 320.000,194.000 is z=1.852773
22:18:10 // probe at 320.000,194.000 is z=1.842773
22:18:10 // Making the following Z adjustments:
// stepper_z = -0.916039
// stepper_z1 = 1.729255
22:18:10 // Retries: 1/3 Probed points range: 1.646875 tolerance: 0.050000
22:18:19 // probe at 0.000,194.000 is z=-1.272711
22:18:25 // probe at 0.000,194.000 is z=-1.267711
22:18:33 // probe at 320.000,194.000 is z=2.506039
22:18:39 // probe at 320.000,194.000 is z=2.479789
22:18:39 // Making the following Z adjustments:
// stepper_z = -2.727810
// stepper_z1 = 3.316724
22:18:39 // Retries: 2/3 Probed points range: 3.763125 tolerance: 0.050000
22:18:39 !! Retries aborting: Probed points range is increasing.

```

---

<div class="post-metadata">

**Author:** ![m.lewis.everley](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/m.lewis.everley/32/13875_2.png) [@m.lewis.everley](https://klipper.discourse.group/u/m.lewis.everley)\
**Post date:** [September 3, 2024, 2:00pm UTC](https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583/2 "2024-09-03T14:00:23Z")

</div>

Anyone got any thoughts?

---

<div class="post-metadata">

**Author:** ![LifeOfBrian](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/lifeofbrian/32/2380_2.png) [@LifeOfBrian](https://klipper.discourse.group/u/LifeOfBrian)\
**Post date:** [September 3, 2024, 2:25pm UTC](https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583/3 "2024-09-03T14:25:55Z")

</div>

If your motor assignments are correct then your probe and joint points are not correct.  
It is essential that those are measured properly and referenced correctly to 0.0, otherwise the algorithm can’t get it right.  
Also possible probe offsets have to be right.

Check this for better understanding:

> [@Understanding X and Y Axes Limits and Homing](https://klipper.discourse.group/t/understanding-x-and-y-axes-limits-and-homing/10779):
>
> The X and Y Axis Klipper needs to know from its printer.cfg settings how far the X and Y axes can safely move without hitting the printer’s frame. It also needs to know where the origin (X=0 / Y=0) is. This origin is the beginning of the usable printer bed. In the following, we assume a Cartesian printer that follows the conventions of a [Cartesian Coordinate System](https://en.wikipedia.org/wiki/Cartesian_coordinate_system). This is also the reason why it is a quasi-standard to define the origin as the left-front corner of the bed. This way, all logic…

---

<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 2, 2024, 2:26pm UTC](https://klipper.discourse.group/t/z-tilt-adjust-making-bed-alignment-far-worse/18583/4 "2024-11-02T14:26:02Z")

</div>

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