<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>

[{'answer_id': 8362, 'author': 'aaron elsey', 'author_id': 14671, 'author_profile': 'https://3dprinting.stackexchange.com/users/14671', 'pm_score': 0, 'selected': False, 'text': '<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>\n'}, {'answer_id': 11922, 'author': 'D DD', 'author_id': 19973, 'author_profile': 'https://3dprinting.stackexchange.com/users/19973', 'pm_score': 1, 'selected': False, 'text': '<p>First, make sure to check if stow, deploy and the trigger are working correctly.</p>\n\n<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>\n\n<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>\n\n<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>\n\n<pre><code>#define Z_MIN_PROBE_USES_Z_MIN_ENDSTOP_PIN\n</code></pre>\n\n<p>If this has been used, Z-min probe will use Z-min endstop pin instead of Z-min probe.</p>\n'}, {'answer_id': 14720, 'author': 'Marcos Moura', 'author_id': 25175, 'author_profile': 'https://3dprinting.stackexchange.com/users/25175', 'pm_score': 1, 'selected': False, 'text': '<p>In case someone still has this problem I have a solution for what happened in my case.</p>\n<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>\n'}, {'answer_id': 18598, 'author': 'Nela Aguilar', 'author_id': 32366, 'author_profile': 'https://3dprinting.stackexchange.com/users/32366', 'pm_score': 1, 'selected': False, 'text': '<p>I solved the same issue.</p>\n<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>\n<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>\n'}]
['https://3dprinting.stackexchange.com/questions/8271', 'https://3dprinting.stackexchange.com', 'https://3dprinting.stackexchange.com/users/14383/']