You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I upgraded my fully functional ender 3 creality board 4.2.7 to a SKR mini 3.0 (NOT 3.0.1) that was using a BLTouch.
I verified my config with issuing the klipper debug commands BLTOUCH_DEBUG COMMAND=pin_down and BLTOUCH_DEBUG COMMAND=pin_up. Both worked successfully. I also verified continuity in the wiring to ensure all the pins were connected to the board properly.
Despite that, I was getting an error when homing the z-axis with Klipper reporting "BLTouch failed to verify sensor state".
I changed this line to include the caret (^) in front of the pin PC14 like this: sensor_pin: ^PC14
After I did that single change, everything worked. I was able to home my z axis. I suggest this should be changed in the sample config referenced above.
The text was updated successfully, but these errors were encountered:
I upgraded my fully functional ender 3 creality board 4.2.7 to a SKR mini 3.0 (NOT 3.0.1) that was using a BLTouch.
I verified my config with issuing the klipper debug commands BLTOUCH_DEBUG COMMAND=pin_down and BLTOUCH_DEBUG COMMAND=pin_up. Both worked successfully. I also verified continuity in the wiring to ensure all the pins were connected to the board properly.
Despite that, I was getting an error when homing the z-axis with Klipper reporting "BLTouch failed to verify sensor state".
After some digging around I changed the BLTouch pin configuration as referenced here: https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/blob/master/firmware/V3.0/Klipper/SKR-mini-E3-V3.0-klipper.cfg
I changed this line to include the caret (^) in front of the pin PC14 like this: sensor_pin: ^PC14
After I did that single change, everything worked. I was able to home my z axis. I suggest this should be changed in the sample config referenced above.
The text was updated successfully, but these errors were encountered: