#BL Touch and SKR Mini E3 v3.0 w/ Klipper (SOLVED)

3 messages · Page 1 of 1 (latest)

jagged burrow
#

I have been going through an arduous process or replacing the main board on my CR-10v3 with a SKR Mini E3 v3.0. My OEM board as using Klipper without an issue, but for some reason I wasn't able get Mainsail to talk to the board firmware until last night when I reimaged the SD card for my RPI4 with the latest image. My guess the original install was missing something that I didn't know about, but that isn't important any longer. At this point the only problem I seem to be having is that its not seeing my BL Touch. Marlin was able to use it without issue, but I got tired of fighting with all of the other config issues it had, so I tried Klipper again. Anyway, when I try to home the printer, all I get is the following.

BLTouch failed to verify sensor state
BLTouch failed to verify sensor state; retrying.
BLTouch failed to verify sensor state; retrying.

I retrieved the current printer.cfg from the BTT site for the board, the changed the serial port for the mcu and it worked, which already came with the following for the BL Touch, the only things I have changed are the offsets which I pulled from my original config. I did try swapping the pins, but that didn't make a difference, but they are the correct pins based on the mask on the back of the board.

[bltouch]
sensor_pin: PC14
control_pin: PA1
x_offset: 48
y_offset: 0
z_offset: 1.445
#speed:

Any help would be appreciated, thank you.

jagged burrow
#

Further update...

The "BLTOUCH_DEBUG COMMAND=pin_up",, "BLTOUCH_DEBUG COMMAND=pin_down", and "QUERY_PROBE" all seem to work. It just seems that the actual z-homing functionality is the only thing that doesn't seem to be working as needed. Although, whether the pin is up or down, the "QUERY_PROBE" reports "probe: open"

jagged burrow
#

I found my problem, a look at my original config for the OEM board showed that the sensor_pin requires a pull-up resistor, so I changed "sensor_pin: PC14" to "sensor_pin: ^PC14" and functionality was normal again.