#Constantly increasing BLTouch z reading.

2 messages · Page 1 of 1 (latest)

frank bane
#

Hello, I'm relatively new to both Klipper and Mainsail, so I'm hoping I'm just running into a simple configuration error here and one of you can quickly identify it for me.

I've setup a Raspberry Pi 4 with Mainsail, configured, compiled and flashed Klipper to an SKR Mini E3 V3 that replaced my Ender 3's 8 bit board.

I thought I had everything set up as needed, ensured fans/extruder/heated bed/etc.. all work as expected. I went through the probe calibration klipper documentation and got the x/y dialed in and seem to be running into issues with the Z offset/probe accuracy. I ran through the PROBE_CALIBRATE, did the paper test, accepted, ran SAVE_CONFIG and thought I'd be good to go.

When I began the repeatability check via PROBE_ACCURACY, I'm seeing the Z reading increase with every probe reading.

PROBE_ACCURACY at X:117.500 Y:117.500 Z:10.000 (samples=10 retract=2.000 speed=5.0 lift_speed=5.0)

probe at x,y is z=2.445000
probe at x,y is z=2.467500
probe at x,y is z=2.475000
probe at x,y is z=2.495000
probe at x,y is z=2.507500
probe at x,y is z=2.517500
probe at x,y is z=2.530000
probe at x,y is z=2.552500
probe at x,y is z=2.560000
probe at x,y is z=2.572500
probe accuracy results: maximum 2.572500, minimum 2.445000, range 0.127500, average 2.512250, median 2.512500, standard deviation 0.040132

G28 Z

PROBE_ACCURACY at X:117.500 Y:117.500 Z:10.000 (samples=10 retract=2.000 speed=5.0 lift_speed=5.0)

probe at x,y is z=2.452500
probe at x,y is z=2.467500
probe at x,y is z=2.467500
probe at x,y is z=2.487500
probe at x,y is z=2.497500
probe at x,y is z=2.510000
probe at x,y is z=2.522500
probe at x,y is z=2.530000
probe at x,y is z=2.547500
probe at x,y is z=2.560000
probe accuracy results: maximum 2.560000, minimum 2.452500, range 0.107500, average 2.504250, median 2.503750, standard deviation 0.034224

I think I also have some confusion between gcode z offset and the probe z offset, it seems to want to print in the air.

trim citrus
#

when using a probe dont use the the gcode z offset