Probe not deactivating after bed mesh

General Discussion
1

Basic Information:

Printer Model: DIY based on Trident
MCU / Printerboard: Octopus
Host / SBC Rpi 3B
klippy.log
klippy.log (2.3 MB)

Good morning.
I’ve not updated Klipper for a while, but when updating to the latest update, v0.12.0-302-g87ac6936, my Z homing probe does not deactivate after bed mesh. If I start a print, adaptive bed mesh will run but probe stays deployed and drags on the bed.

After trial and error, rolling back commits to v0.12.0-293 > v0.12.0-302 fixes the problem.

2

There have been changes in this area, so a regression is not entirely impossible.

Nevertheless, your description and config is not entirely clear:

  • Can you control the servo manually with the respective SET_SERVO commands?
  • ENABLE has been deprecated ages ago in SET_SERVO
  • KAMP is deprecated in favor of built-in adaptive meshing
3

Yes I can control the servo via the consol and macros for stow and deply are working normally. Z homing works normally. Only be mesh and adaptive mesh have the issue.

You say built-in adaptive mesh? Built in to Klipper or the slicer? I use Orca.

4

It’s in the docs:

https://www.klipper3d.org/Bed_Mesh.html#adaptive-meshes

5

Thank you, I will have a look.

6

I’ve been playing with this and finally got it working again.

I disabled KAMP and made changes to get built-in adaptive mesh working, same issue.

I started looking at the probe itself, and after trial and error, I found that commenting out the line ‘SET_SERVO SERVO=BFPTouch WIDTH=0’, it fixed my issue.

[probe]
pin: EBBCan: PB7  # #using BLTOUCH pin
x_offset: -20
y_offset: 30
speed: 3.0
samples: 2
samples_result: average
deactivate_on_each_sample: False 
activate_gcode:
    SET_SERVO SERVO=BFPTouch ANGLE=60 #ENABLE=0
    G4 P500
    # SET_SERVO SERVO=BFPTouch WIDTH=0
deactivate_gcode:
    SET_SERVO SERVO=BFPTouch ANGLE=2 #ENABLE=0
    # SET_SERVO SERVO=BFPTouch WIDTH=0

Thanks for your help.

1 Like
7

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