<p>After troubleshooting I have managed to fix the sensor problems.</p>
<p><em>(Please take note of the <strong>update</strong> at the end of the answer below as the problem started again shortly after the so-called fix...)</em></p>
<p>Digging into several posts I found <a href="http://www.geeetech.com/forum/viewtopic.php?f=27&amp;t=18263" rel="nofollow noreferrer">this post</a> that hints to a solution:</p>
<p><a href="https://i.sstatic.net/8YlLa.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/8YlLa.jpg" alt="Instructions to adjust the 3DTouch sensor" /></a></p>
<p>After readjusting, the sensor worked and I was able to produce a print, but the next day it failed again... What I found is that the bed and extruder are <strong>NOT</strong> shut off while probing although that should have been enabled in Marlin 1.1.8. I assumed that this de-powering is only during the actual probe lowering, so very short. So I figured that this might be an EMI problem. In a last resort I updated to Marlin 1.1.9 which has the functionality to shut the power off for heater and bed and everything now seems to work perfectly. I now see that the de-powering is a bit longer and in fact the extruder temperature drops slightly, this has never been seen with the previous firmware version.</p>
<hr />
<p><strong>Update</strong>:<br>
Not long after the &quot;update&quot;/&quot;fix&quot; the problem manifested itself again... Further troubleshooting revealed that it was a bad connection of the connectors of the sensor that got temporarily &quot;fixed&quot; as the cables had been fiddled with during the firmware update.</p>
<p><em>I have to note that the quality of these non-genuine sensors is not close the the original BLTouch. The BLTouch has never failed me to date, while several 3DTouch sensors did...</em></p>

CC BY-SA 4.0
2018-09-21T14:09:12.673Z
2022-06-01T13:48:10.060Z
2022-06-01T13:48:10.060Z
0scar
<p>I'm using a <strong>3DTouch sensor</strong> (from Geeetech) on a <a href="https://www.thingiverse.com/make:540590" rel="nofollow noreferrer">self-build CoreXY printer</a> (<a href="https://www.thingiverse.com/thing:2254103" rel="nofollow noreferrer">HyperCube Evolution</a>). The sensor worked perfectly until not being used for a month.</p>

<p>The <strong>symptoms</strong> are that it <strong>fails to deploy the pin on the second probe deployment</strong> so basically it fails after the first probe is triggered by the raised platform.</p>

<p>On homing Z (not only for <code>G28</code> or "home all" but also for <code>G28 Z</code> to "home Z axis") and goes into some sort of a fail-safe mode where the LED keeps flashing. Sometimes it does deploy and finishes the homing instructions and continues to the <code>G29</code> instruction (note that double probing <code>#define MULTIPLE_PROBING 2</code> is enabled in the Marlin 1.1.8 firmware) and show similar symptoms as described above for the <code>G28</code> command. Note that failing to deploy the probe sometimes leads to a rising build platform that does not stop, other times some fail safe kicks in and the bed lowers and aborts the print.</p>

<p>To lift the fail-safe condition, a reset of the sensor is required (this can be done through the LCD or by command <code>M280 P0 S160</code>).</p>

<p><strong>What I have done to solve the problem</strong> is to isolate the wires from the 3D touch sensor as I was under the impression that this was related to electromagnetic interference (therefore when the sensor is probing, the bed and heater cartridge are not powered momentarily), but that did not help. </p>

<p>Any suggestions and solutions to get it working again are appreciated.</p>

CC BY-SA 4.0
2018-09-20T12:46:25.847Z
Have you checked wire connectivity while moving the wires around? If the sensor wire for the probe (assuming a three wire setup), if the sensor wire (not power or ground wires to the probe) is failing at certain angles, it might give you something like you're stating. Yes, I'm grasping for straws.
Pᴀᴜʟsᴛᴇʀ2
CC BY-SA 4.0
2018-09-20T15:24:48.590Z
Any time I run into a "ran when parked" situation (old joke from used-car collectors),  I suspect dirt, dust, grime leading to mechanical failures. See if there's any way to do a careful cleaning.
Carl Witthoft
<marlin><z-probe><bed-leveling><3dtouch>
3DTouch sensor fails after probe deployment and triggering
0scar
# 3DTouch sensor fails after probe deployment and triggering

(Asked by: username_0 on 2018-09-20)

I'm using a **3DTouch sensor** (from Geeetech) on a [self-build CoreXY printer](https://www.thingiverse.com/make:540590) ([HyperCube Evolution](https://www.thingiverse.com/thing:2254103)). The sensor worked perfectly until not being used for a month.

The **symptoms** are that it **fails to deploy the pin on the second probe deployment** so basically it fails after the first probe is triggered by the raised platform.

On homing Z (not only for `G28` or "home all" but also for `G28 Z` to "home Z axis") and goes into some sort of a fail-safe mode where the LED keeps flashing. Sometimes it does deploy and finishes the homing instructions and continues to the `G29` instruction (note that double probing `#define MULTIPLE_PROBING 2` is enabled in the Marlin 1.1.8 firmware) and show similar symptoms as described above for the `G28` command. Note that failing to deploy the probe sometimes leads to a rising build platform that does not stop, other times some fail safe kicks in and the bed lowers and aborts the print.

To lift the fail-safe condition, a reset of the sensor is required (this can be done through the LCD or by command `M280 P0 S160`).

**What I have done to solve the problem** is to isolate the wires from the 3D touch sensor as I was under the impression that this was related to electromagnetic interference (therefore when the sensor is probing, the bed and heater cartridge are not powered momentarily), but that did not help.

Any suggestions and solutions to get it working again are appreciated.

**Tags:** marlin, z-probe, bed-leveling, 3dtouch
> **Comments:**
> **username_1**: Have you checked wire connectivity while moving the wires around? If the sensor wire for the probe (assuming a three wire setup), if the sensor wire (not power or ground wires to the probe) is failing at certain angles, it might give you something like you're stating. Yes, I'm grasping for straws.  
> **username_2**: Any time I run into a "ran when parked" situation (old joke from used-car collectors),  I suspect dirt, dust, grime leading to mechanical failures. See if there's any way to do a careful cleaning.  

---

## 1 answers

### Answer by username_0 on 2018-09-21. Score: 1 | Accepted answer

After troubleshooting I have managed to fix the sensor problems.

*(Please take note of the **update** at the end of the answer below as the problem started again shortly after the so-called fix...)*

Digging into several posts I found [this post](http://www.geeetech.com/forum/viewtopic.php?f=27&t=18263) that hints to a solution:

[![Instructions to adjust the 3DTouch sensor](https://i.sstatic.net/8YlLa.jpg)](https://i.sstatic.net/8YlLa.jpg)

After readjusting, the sensor worked and I was able to produce a print, but the next day it failed again... What I found is that the bed and extruder are **NOT** shut off while probing although that should have been enabled in Marlin 1.1.8. I assumed that this de-powering is only during the actual probe lowering, so very short. So I figured that this might be an EMI problem. In a last resort I updated to Marlin 1.1.9 which has the functionality to shut the power off for heater and bed and everything now seems to work perfectly. I now see that the de-powering is a bit longer and in fact the extruder temperature drops slightly, this has never been seen with the previous firmware version.

---

**Update**:  
Not long after the "update"/"fix" the problem manifested itself again... Further troubleshooting revealed that it was a bad connection of the connectors of the sensor that got temporarily "fixed" as the cables had been fiddled with during the firmware update.

*I have to note that the quality of these non-genuine sensors is not close the the original BLTouch. The BLTouch has never failed me to date, while several 3DTouch sensors did...*


---

