My Ender 3 V2 with CR-Touch Klipper config Issues

General Discussion
1

Basic Information:

Printer Model: Creality Ender 3 V2 with CR-Touch the only mod
MCU / Printer board: MCU stm32f103 / Printer Main Board 4.2.2
SBC / Host: Raspberry Pi 4B Debian 12
klippy.log
klippy-20241110-2250.log (2.8 MB)

Describe your issue:

In testing of my printer.cfg, when I do “Home All”, the Ender 3 V2 doesn’t stop when the printer head hits the print bed, but rather it tries to keep going lower requiring an emergency stop or power off.

Background and Actions so far:

Let me apologise up front for the length of this post, but I’ve been trying for about 3 weeks to sort out my Klipper printer.cfg for my (stock) Creality Ender 3 V2 3D Printer with a CR Touch & a 4.2.2 mainboard.
I built a Klipper Pad, using a Raspberry Pi 4B with Raspberry Pi 64-bit Lite and used the Kiauh script. I have used the script to install Klipper, Moonraker, Mainsail, KlipperScreen, Crowsnest. I also have installed and set up GuppyFlo and Spoolman (using Docker) on the same Raspberry Pi.

I started with printer.cfg posted by Devenv here. I’ve amended this in line with the config changes proposed by a couple of YT Videos by people with similar hardware) and I’ve tested the config using commands recommended in these videos:

M84 - Disable All Motors
M112 - Klipper Shutdown
SET_STEPPER_ENABLE STEPPER=stepper_x ENABLE=1
SET_STEPPER_ENABLE STEPPER=stepper_y ENABLE=1
SET_STEPPER_ENABLE STEPPER=stepper_z ENABLE=1
QUERY_ENDSTOPS
STEPPER_BUZZ STEPPER=stepper_x
STEPPER_BUZZ STEPPER=stepper_y
STEPPER_BUZZ STEPPER=stepper_z

All these tests successfully completed, but when I do “Home All”, the Ender 3 doesn’t stop when the printer head hits the print bed, but rather it tries to keep going lower requiring an emergency stop or power off.

I’ve also spent a lot of time reading the Klipper3D website & discord server, including reviewing sample configuration files referenced, plus lots of other related articles and Github printer.cfg suggestions for the Ender 3 series with BL Touch or CR-Touch.

I’ve have carefully been through my config file to check the settings and annotated changes I’ve made to explain what I have done.
But unfortunately I haven’t been able to solve have my problem.

One suggestion I have tried was to raise the Z Axis / tool head gantry and then try doing a Home All letting the probe hit my finger, which does seem to reacts correctly and stops.
I don’t seem to be making progress and would really appreciate any assistance / suggestions anyone can offer!

2

Validate that your probe works like expected according to BL-Touch - Klipper documentation. If it does not see the “clone” information further down the page.

3

I’ve finally managed to get enough time to complete and document the initial BL Touch tests.

Initial Tests

  • Verify that the BL-Touch is mounted at the correct height, the pin should be roughly 2 mm above the nozzle when retracted. [Pass]
  • When you turn on the printer, the BL-Touch probe should perform a self-test and move the pin up and down a couple of times. [Pass]
  • Once the self-test is completed, the pin should be retracted and the red LED on the probe should be lit. [Pass]
  • If there are any errors, for example the probe is flashing red or the pin is down instead of up, please turn off the printer and check the wiring and configuration. [Pass]
  • If the above test pass, next test the control pin is working correctly by running BLTOUCH_DEBUG COMMAND=pin_down. Verify the pin moves down and the red LED on the probe turns off. If not, check your wiring and configuration again. [Pass]
  • Issue BLTOUCH_DEBUG COMMAND=pin_up. Verify that the pin moves up, and that the red light turns on again. If it’s flashing then there’s some sort of a problem. [Pass]
  • The next step is to confirm that the sensor pin is working correctly. Run BLTOUCH_DEBUG COMMAND=pin_down, verify that the pin moves down, run BLTOUCH_DEBUG COMMAND=touch_mode, run QUERY_PROBE, and verify that command reports “probe: open”. [Pass]
  • While gently pushing the pin up slightly with the nail of your finger run QUERY_PROBE again. Verify the command reports “probe: TRIGGERED”. If either query doesn’t report the correct message then it usually indicates an incorrect wiring or configuration (though some clones may require special handling). [Pass]
  • At the completion of this test run BLTOUCH_DEBUG COMMAND=pin_up and verify the pin moves up. [Pass]
  • After completing the BL-Touch control pin and sensor pin tests, it is now time to test probing, but with a twist. Instead of letting the probe pin touch the print bed, let it touch the nail on your finger. Position the toolhead far from the bed, issue a G28 (or PROBE if not using probe:z_virtual_endstop), wait until the toolhead starts to move down, and stop the movement by very gently touching the pin with your nail. You may have to do it twice, since the default homing configuration probes twice. Be prepared to turn off the printer if it doesn’t stop when you touch the pin. [Pass] Message displayed during the G@* command, possibly after the second probe down: “No trigger on z after full movement”
  • If that was successful, do another G28 (or PROBE) but this time let it touch the bed as it should. [Fail] Correctly probed but didn’t stop and there is a repetitive clicking until emergency stop or power off.

I’m struggling to work out what if any of the next paths I should following from the BL Touch goes Bad - any help on how to debug this is appreciated and heart-felt thanks to all those who read it. I have also uploaded more recent log outputs.
klippy-20241116-0035.log (385.2 KB)

4

Not sure about your report here:

5

I was finally able to resolve my problem once demonstrating it to my son, who is a more knowledgeable 3D Printer aficionado than myself. As part of the my Klipper upgrade, I had replaced the original glass print bed surface with a PEI plate with a magnetic (sticker) base but had not removed the original Z Stop sensor (which was only just disconnected) and that was stopping the print head and hence the CR Touch couldn’t trigger as it wasn’t reaching the plate!

Dah :person_facepalming:

6

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