# CR-Touch always triggered **URL:** \ **Category:** General Discussion\ **Created:** [May 30, 2022, 11:07am UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028 "2022-05-30T11:07:41Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 11:07am UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/1 "2022-05-30T11:07:41Z")
Hi, I have been printing using marlin for a couple of months now with no major issues. I figured I would give Klipper a try to further optimize my prints. When I got to the part of the [guide](https://www.klipper3d.org/BLTouch.html) regarding bltouch I began experiencing errors The Issue: When I type query\_probe into the terminal klipper invariably returns : // probe: TRIGGERED Raising, lowering, and resetting has no effect on this output. Additionally this error is thrown after firmware restart. $ FIRMWARE\_RESTART // Failed to verify BLTouch probe is raised; retrying. // Failed to verify BLTouch probe is raised; retrying. // Failed to verify BLTouch probe is raised; retrying. // Klipper state: Ready As the crtouch works fine with marlin I am assuming this is a software/config issue. Additionally the color of the light on the probe changes when I manually trigger the probe. The CRtouch uses a 5 pin cable harness while the bltouch uses a 3 pin. I suspect there is an issue with my sensor\_pin however all the documentation points to using sensor\_pin: ^PB1 I am running a stock ender 3 v2 with the crealty 4.2.2 board. For ease of reading here are the relevant excerpts from my config file: [bltouch] sensor\_pin: ^PB1 control\_pin: PB0 x\_offset: -42 y\_offset: -10 z\_offset: 0 [stepper\_z] step\_pin: PB6 dir\_pin: !PB5 enable\_pin: !PC3 microsteps: 16 rotation\_distance: 8 endstop\_pin: probe:z\_virtual\_endstop # position\_endstop: 0.0 position\_max: 250 position\_min: -5 #for bltouch [printer.cfg](https://klipper.discourse.group/uploads/short-url/z7NXjYpRnIrBlbPQ6262GD3qsHL.cfg) (4.7 KB) ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 30, 2022, 12:35pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/2 "2022-05-30T12:35:46Z")
You may check if the control works correct/the wiring is ok. PB0 seems to be ok. You maybe caught the wrong wire? When the sensor pin does not move out even there is enough space below the CR-Touch, that may be the culprit. > [@runespirit](#): > > bltouch uses a 3 pin Not quite correct: ![grafik](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/d/dcbf65516bb123c9df35c8fa0f37901a4cc4e741.png) ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 12:42pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/3 "2022-05-30T12:42:32Z")
The connection to the motherboard is seated as is the connection to the probe. I can move the pin up and down via the terminal. The light changes from blue to red when I trigger the pin in the down position. Thanks for clarifying on the bl touch having 5 wires. I saw a workaround somewhere suggesting moving the sensor wires to the z axis limit switch port but but am unable to do that with the cr touch as all 5 wires are placed in the same plug. ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/6/61a1beeb2dbbb027803e8e8beb040f592b587698.jpeg) ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 12:47pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/4 "2022-05-30T12:47:25Z")
I also tried adding the below as suggested in the [docs](https://www.klipper3d.org/Config_Reference.html#bltouch) [bltouch] … pin\_up\_touch\_mode\_reports\_triggered: False This had no effect. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 30, 2022, 12:52pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/5 "2022-05-30T12:52:40Z")
Have you seen this:? [https://www.klipper3d.org/BLTouch.html#bl-touch-clones](https://www.klipper3d.org/BLTouch.html#bl-touch-clones) ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 12:59pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/6 "2022-05-30T12:59:53Z")
yes. My understanding is that touch\_mode is false by default. Executing G28 immediately after restarting klipper and klippy yields: 07:56:02 $ FIRMWARE\_RESTART 07:56:05 // Failed to verify BLTouch probe is raised; retrying. 07:56:07 // Failed to verify BLTouch probe is raised; retrying. 07:56:09 // Klipper state: Ready 07:56:11 $ G28 07:56:26 // Failed to verify BLTouch probe is raised; retrying. 07:56:28 // Failed to verify BLTouch probe is raised; retrying. 07:56:29 !! BLTouch failed to raise probe ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 1:17pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/7 "2022-05-30T13:17:04Z")
Adding [bltouch] … pin\_up\_reports\_not\_triggered: False yields: 08:14:22 $ FIRMWARE\_RESTART 08:14:25 // Klipper state: Ready 08:14:31 $ G28 08:14:45 !! BLTouch failed to deploy The pin does deploy then immediately retracts. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [May 30, 2022, 1:42pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/8 "2022-05-30T13:42:05Z")
You may can experiment on this parameter: ```auto #pin_move_time: 0.680 # The amount of time (in seconds) to wait for the BLTouch pin to # move up or down. The default is 0.680 seconds. ``` ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [May 30, 2022, 2:25pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/9 "2022-05-30T14:25:31Z")
Redid all of the above commands with pin\_move\_time: 5.0 and the results are slower but the output identical. I have been skimming through the github looking for the boolean function that determines if the pin is triggered or not but have yet to find it. Seems like the issues is related to the trigger function. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [May 30, 2022, 3:25pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/10 "2022-05-30T15:25:43Z")
The Ender 3 Max uses the same board and also has the CR-Touch. A verified cfg can be found here: [klipper/printer-creality-ender3max-2021.cfg at master · Klipper3d/klipper · GitHub](https://github.com/Klipper3d/klipper/blob/master/config/printer-creality-ender3max-2021.cfg) Edit: Also make sure that your bed is sufficiently far away so that the probe can actually deploy. Also according to my experience an “offended” Touchy might require a full power cycle (reset is not enough) of the board to become cooperative again. ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [June 2, 2022, 3:15pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/11 "2022-06-02T15:15:00Z")
This appears to be a hardware issue, not a software issue. I reflashed marlin and the cr touch no longer works with marlin. I suspect either the cable or the cr touch failed. I will attempt to get a replacement via warranty and try again with a new one. Thanks for all the help. ---
**Author:** ![runespirit](https://avatars.discourse-cdn.com/v4/letter/r/b3f665/32.png) [@runespirit](https://klipper.discourse.group/u/runespirit)\ **Post date:** [June 9, 2022, 11:03am UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/12 "2022-06-09T11:03:33Z")
Confirming that it was a mechanical failure. A new wire harness fixed the isse. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [September 19, 2025, 5:00pm UTC](https://klipper.discourse.group/t/cr-touch-always-triggered/3028/13 "2025-09-19T17:00:43Z")