<p>In case someone still has this problem I have a solution for what happened in my case.</p>
<p>I am using a 3DTouch and I also encountered the same problem and it was solved by commenting <code>//#define BLTOUCH_HS_MODE</code></p>

CC BY-SA 4.0
2020-11-03T15:21:47.183Z
The High Speed mode is not recommended, so indeed this line must be commented out.
0scar
CC BY-SA 4.0
2020-11-03T19:12:37.547Z
Welcome, and please take the [tour](https://3dprinting.stackexchange.com/tour).
Davo
CC BY-SA 4.0
2020-11-03T14:09:39.257Z
2020-11-03T15:20:57.710Z
2020-11-03T15:20:57.710Z
Marcos Moura
<p>I solved the same issue.</p>
<p>I had the same problem, just send the G-code <code>M502</code> to your printer through Cura or whatever it is you use. The reason is that you already did an auto bed leveling and you more than likely send the G-code <code>M500</code> which saves your auto mesh data so that you don't have to auto home for every print.</p>
<p>So <a href="/q/11483"><code>M502</code> restores everything to its factory settings</a> after you reset don't forget to send <code>M500</code> to save the default settings or else your printer will be fixed up until the next time you turn it on and you'll have to start all over again hope this helps.</p>

CC BY-SA 4.0
2021-12-19T21:34:39.267Z
2021-12-20T08:16:14.450Z
2021-12-20T08:16:14.450Z
Nela Aguilar
<p>This sounds like the firmware setting for your BLtouch is not set up properly. Look at the line in Config H where it deploys the BLtouch. make sure nothing is commented out and that the 2nd deploy is shown. </p>

CC BY-SA 4.0
2019-03-01T00:42:36.647Z
"2nd deploy is shown", Can you be a bit more specific about this?
David Souza
CC BY-SA 4.0
2019-04-14T09:54:29.250Z
Could you expand upon your answer please?
Greenonline
CC BY-SA 4.0
2019-04-15T12:14:32.150Z
If the 2nd Deploy is shown on the line make sure that line is not commented out. Remove the "#" in front of the 2nd Deploy to activate that line.
aaron elsey
CC BY-SA 4.0
2019-02-27T20:17:26.863Z
2019-02-27T20:17:26.863Z
aaron elsey
<p>First, make sure to check if stow, deploy and the trigger are working correctly.</p>

<p>Second, check the pins files to make sure you put it in the correct pins. Black and White probe pin might need to go to Z-min or probe pin depending on. Make sure to check that.</p>

<p>Third, add "BLTOUCH delay". It might be triggering too slow or too fast for the next one to react. So after the first trigger, there should be a time for it to "re-setup" for the second. But if there is no time to do that then it won't trigger. </p>

<p>To add examples: If you have SKR 1.4 Turbo, then use BLTouch probe pins (black and white) on the board. IT will NOT recognize. You have to use Z-min endstop pins. Reason for this?:</p>

<pre><code>#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN
</code></pre>

<p>If this has been used, Z-min probe will use Z-min endstop pin instead of Z-min probe.</p>

CC BY-SA 4.0
2020-01-31T03:47:53.387Z
2020-01-31T07:30:51.807Z
2020-01-31T07:30:51.807Z
D DD
<p>When double-probing, sometimes the BLTouch will hit the bed before the z-axis goes down:</p>

<ol>
<li>The BLTouch deploys </li>
<li>The bed goes up</li>
<li>The sensor triggers</li>
<li>The BLTouch stows</li>
<li>The BLTouch deploys and crashes the bed before the z-axis goes down for the second probe</li>
</ol>

<p>It happens only on the second probe of double-probing (slow speed) - the bed can't move out of the way fast enough.
This happens in 2/16 probe points.</p>

<p><em>Probe Accuracy Test result:</em></p>

<ul>
<li><em>Mean: 0.023075 mm</em></li>
<li><em>Min: 0.018 mm</em></li>
<li><em>Max: 0.027 mm</em></li>
<li><em>Range: 0.008 mm</em></li>
<li><em>Standard Deviation: 0.002584 mm</em></li>
</ul>

CC BY-SA 4.0
2020-10-27T09:09:41.033Z
Hello David, I noticed your question has been up for a while now. Have any of the answers below been able to solve your question? If so, would you mind accepting the appropriate answer. If not, what is missing so that we may help you further? Also, if you have figured it out on your own, you can always answer and accept (after 48 hours) your own solution. Thank you!
0scar
CC BY-SA 4.0
2021-08-05T17:18:05.017Z
Sounds like the height the printer is supposed to go to before second probe is too low.
Justin
<calibration><bed-leveling><z-probe><bltouch>
The BLTouch is hitting the bed on the double-probing
David Souza
# The BLTouch is hitting the bed on the double-probing

(Asked by: username_0 on 2019-02-13)

When double-probing, sometimes the BLTouch will hit the bed before the z-axis goes down:

1. The BLTouch deploys
2. The bed goes up
3. The sensor triggers
4. The BLTouch stows
5. The BLTouch deploys and crashes the bed before the z-axis goes down for the second probe

It happens only on the second probe of double-probing (slow speed) - the bed can't move out of the way fast enough.
This happens in 2/16 probe points.

*Probe Accuracy Test result:*

* *Mean: 0.023075 mm*
* *Min: 0.018 mm*
* *Max: 0.027 mm*
* *Range: 0.008 mm*
* *Standard Deviation: 0.002584 mm*

**Tags:** calibration, bed-leveling, z-probe, bltouch

> **Comments:**
> **username_1**: Hello username_0, I noticed your question has been up for a while now. Have any of the answers below been able to solve your question? If so, would you mind accepting the appropriate answer. If not, what is missing so that we may help you further? Also, if you have figured it out on your own, you can always answer and accept (after 48 hours) your own solution. Thank you!  
> **username_2**: Sounds like the height the printer is supposed to go to before second probe is too low.  

---

## 4 answers

### Answer by username_3 on 2020-11-03. Score: 1

In case someone still has this problem I have a solution for what happened in my case.

I am using a 3DTouch and I also encountered the same problem and it was solved by commenting `//#define BLTOUCH_HS_MODE`

> **Comments:**
> **username_1**: The High Speed mode is not recommended, so indeed this line must be commented out.  
> **username_4**: Welcome, and please take the [tour](https://3dprinting.stackexchange.com/tour).  

---

### Answer by username_5 on 2021-12-19. Score: 1

I solved the same issue.

I had the same problem, just send the G-code `M502` to your printer through Cura or whatever it is you use. The reason is that you already did an auto bed leveling and you more than likely send the G-code `M500` which saves your auto mesh data so that you don't have to auto home for every print.

So [`M502` restores everything to its factory settings](/q/11483) after you reset don't forget to send `M500` to save the default settings or else your printer will be fixed up until the next time you turn it on and you'll have to start all over again hope this helps.


---

### Answer by username_8 on 2020-01-31. Score: 1

First, make sure to check if stow, deploy and the trigger are working correctly.

Second, check the pins files to make sure you put it in the correct pins. Black and White probe pin might need to go to Z-min or probe pin depending on. Make sure to check that.

Third, add "BLTOUCH delay". It might be triggering too slow or too fast for the next one to react. So after the first trigger, there should be a time for it to "re-setup" for the second. But if there is no time to do that then it won't trigger.

To add examples: If you have SKR 1.4 Turbo, then use BLTouch probe pins (black and white) on the board. IT will NOT recognize. You have to use Z-min endstop pins. Reason for this?:

```
#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN

```

If this has been used, Z-min probe will use Z-min endstop pin instead of Z-min probe.


---

### Answer by username_6 on 2019-02-27. Score: 0

This sounds like the firmware setting for your BLtouch is not set up properly. Look at the line in Config H where it deploys the BLtouch. make sure nothing is commented out and that the 2nd deploy is shown.

> **Comments:**
> **username_0**: "2nd deploy is shown", Can you be a bit more specific about this?  
> **username_7**: Could you expand upon your answer please?  
> **username_6**: If the 2nd Deploy is shown on the line make sure that line is not commented out. Remove the "#" in front of the 2nd Deploy to activate that line.  

---

