KlikyNG Probe unconsitant state

Basic Information:

Printer Model: VORON Legacy
MCU / Printerboard: BTT SKR 1.4
klippy-Legacy-31012024.log (1002.5 KB)

Describe your issue:

I Good morning,
I set up a VORON Legacy with an SKR1.4, a Raspberry Pi Zero 2W and a Klicky probe connected to the pins of the BL-Touch under Klipper Firmware. It turns out that when I ask for the status of the EndStops, I can get the right result or I can get the wrong one after 3 or 4 tests in a row.
I think it’s a communication problem between the Pi Zero 2W and the SKR1.4 since I had to put them in serial communication due to lack of suitable USB connectors.

Can you help me resolve my problem?

I’m not sure if the port you’re using for this probe has a hardware pullup on it. You should enable the pullup in your config to make sure. If the pin doesn’t have a hardware pullup, it can be in a floating state which would cause the issues you’re seeing.

[probe]
pin = ^P0.10
x_offset = 0
y_offset = 19.75
z_offset = 6.42
speed = 5
samples = 3
samples_result = median
sample_retract_dist = 2.0
samples_tolerance = 0.01
samples_tolerance_retries = 3
lift_speed = 15.0

I just test your advice and now Docked or Undocked the result is Triggered

20:46 _CheckProbe 20:46 probe: TRIGGERED 20:46 _CheckProbe 20:46 probe: TRIGGERED 20:46 _CheckProbe 20:46 probe: TRIGGERED 20:46 _CheckProbe 20:46 probe: TRIGGERED 20:46 QUERY_PROBE 20:46 probe: TRIGGERED 20:46 QUERY_PROBE 20:46 probe: TRIGGERED 20:46 QUERY_PROBE 20:47 probe: TRIGGERED 20:47 QUERY_PROBE 20:47 probe: TRIGGERED

The probe is attached to the toolhead

How is it wired? It should be connected to ground and the pin you have defined

And it’s how it is


The yellow wires

I have re done the Probe Mount with a multimeter in Continuity mode and test each step with the Klipper Console.
It’s done;

1 Like

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