Help for BLTouch setup

Basic Information:

Printer Model: Ender 3
MCU / Printerboard: MKS Gen l V1
Host / SBC ?
klippy.log
klippy.log (4.9 MB)

Describe your issue:

Hey,
I’ve recentlty bought a copy of the BLTouch on Amazon and set it up with this video :
BL Touch complete setup for Klipper!

But the video wasn’t perfect and I had problems that I keept during the setup with could be the problem. And he was on Fluid and I am on Maisail.
My problem is after the bed-mesh is done when a print start, my printer doesn’t go to the good z-offset it goes even lower than my plate. Even if I do a probe setup, nothing changes.

Here is my print-start gcode on Cura :

; Ender 3 Custom Start G-code
G92 E0 ; Reset Extruder
G28 ; Home all axes
BED_MESH_CALIBRATE
G1 Z10 F3000 ; 
G1 Z2.0 F3000 ; 
G1 X0.1 Y20 Z0.3 F5000.0 ; Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 ; Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 ; Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 ; Draw the second line
G92 E0 ; Reset Extruder
G1 Z2.0 F3000 ; Move Z Axis up little to prevent scratching of Heat Bed
G1 X5 Y20 Z0.3 F5000.0 ; Move over to prevent blob squish

Maybe I am doing something wrong, but I am new to Klipper and Maisail (the 3d printing world actually) and that could be a very beginner mistake.

Thank you for your help!
Anas,

Please use Preformatted Text instead of Blockquote for code.

Format

I have a very similar problem and have already read half the internet. I had installed KAMP (which didn’t work either) and now the native mesh from Klipper doesn’t work either. I have reinstalled and reconfigured everything. The mesh actually looks very good:
Size 7x7
Max [185.0, 59.8] 0.145 mm
Min [70.1, 84.8] 0.000 mm
Span 0.145 mm
but is definitely not used, even though I explicitly load it.

andré

mcu (stm32f103xe)
Version: v0.12.0-404-g80d185c94
Auslastung: 0.01, Wach: 0.00, Freq: 72 MHz, Temp: 26°C

Host (aarch64, 64bit)
Version: v0.12.0-404-g80d185c94
OS: Debian GNU/Linux 11 (bullseye)
Distribution: MainsailOS 1.3.2 (bullseye)

The solution was pretty dumb… When I made the probe command, idk why but the z_offset was way to in the bed, so I put 0 to the z-offset and started a fast print and reduce the z-offset until it was close enough.

1 Like