# BL Touch 3.1 issue (again...) **URL:** \ **Category:** General Discussion\ **Created:** [August 4, 2022, 6:29am UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722 "2022-08-04T06:29:40Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![yvautrin](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@yvautrin](https://klipper.discourse.group/u/yvautrin)\ **Post date:** [August 4, 2022, 6:29am UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/1 "2022-08-04T06:29:40Z")
When running the initial tests as described in the Klipper documentation, BL Touch respond fine to the BLTOUCH\_DEBUG COMMAND=pin\_down and BLTOUCH\_DEBUG COMMAND=pin\_up commands. Then when I carry on with the instructions ( 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’). it shows “probe: TRIGGERED” instead of “probe: OPEN”… when i push gently on the probe with my nail, again…“probe: TRIGGERED”… any idea where the problem comes from? ---
**Author:** ![yvautrin](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@yvautrin](https://klipper.discourse.group/u/yvautrin)\ **Post date:** [August 4, 2022, 2:00pm UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/2 "2022-08-04T14:00:39Z")
Couldn’t fix this issue, so I carried on with Z homing, probe and bed calibration, all went fine so far… Ready for first print test, crossing fingers! ---
**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:** [August 4, 2022, 4:02pm UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/3 "2022-08-04T16:02:56Z")
You are sure that this is a genuine BLTouch? This behavior is known from clones. See [BL-Touch - Klipper documentation](https://www.klipper3d.org/BLTouch.html#bl-touch-clones) Quote: > Some “clone” devices do not support `touch_mode` and as a result the `QUERY_PROBE` command does not work. Despite this, it may still be possible to perform probing and homing with these devices. On these devices the `QUERY_PROBE` command during the [initial tests](https://www.klipper3d.org/BLTouch.html#initial-tests) will not succeed, however the subsequent `G28` (or `PROBE`) test does succeed. ---
**Author:** ![yvautrin](https://avatars.discourse-cdn.com/v4/letter/y/d07c76/32.png) [@yvautrin](https://klipper.discourse.group/u/yvautrin)\ **Post date:** [August 4, 2022, 4:20pm UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/4 "2022-08-04T16:20:43Z")
Yep, it is a genuine one, I checked with the QR code and the srial number on the official website! ---
**Author:** ![jgm](https://avatars.discourse-cdn.com/v4/letter/j/96bed5/32.png) [@jgm](https://klipper.discourse.group/u/jgm)\ **Post date:** [August 27, 2022, 3:04pm UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/5 "2022-08-27T15:04:57Z")
I have same issue but I am unable to home on Z axis with error “BLTouch failed to verify sensor state”, X and Y axis do homing correctly, the endstops are triggered and detected. when I test the probe with debug commands, the probe deploy and stow the pin but when the pin is deployed, the z endstop is shown as triggered. Using a bltouch 3.1 genuine also, it does not work with probe\_with\_touch\_mode: True neither false any clue? attached log and printer config, klipper version on mcu v0.10.0-554-g9e4994cb [klippy.log](https://klipper.discourse.group/uploads/short-url/hItYYnfCaPjZRYwqMDrkmaBwtPM.log) (114.7 KB) [printer.cfg](https://klipper.discourse.group/uploads/short-url/u7sSXTwkaBhGdf1RvKQxD1Qb3LP.cfg) (10.6 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 10, 2024, 9:04pm UTC](https://klipper.discourse.group/t/bl-touch-3-1-issue-again/3722/6 "2024-05-10T21:04:07Z")