<p>You should un-comment the following line to get rid of the <code>Probing failed</code> error message:</p>

<pre><code>// #define MIN_SOFTWARE_ENDSTOP_Z // Line # 0907 Commented
</code></pre>

<p>to</p>

<pre><code>#define MIN_SOFTWARE_ENDSTOP_Z
</code></pre>

<p>You have basically disabled the use of the minimum Z endstop, while in fact you are using one, the difference is that it is a sensor now, not a mechanical switch.</p>

<p>Please note the distance of the sensor to the bed, it looks as though it is pretty far away. Before sending an auto home command, it is better to test the endstop triggering beforehand; an external application (e.g. Pronterface, Repetier-Host, OctoPrint, etc.), USB cable and a laptop/computer can be used to send G-code commands through the terminal of the external application. Code <code>M119</code> will output the endstop trigger status to the terminal.</p>

CC BY-SA 4.0
2019-01-31T03:47:10.297Z
I'll make this change and push firmware again. Will get back on this. I do not know why the guy in the video commented this out.
DoomerDGR8
CC BY-SA 4.0
2019-02-08T15:47:11.193Z
@HassanGulzar Have you fixed this, if not update your question so that other people may answer, or an update can be made.
0scar
CC BY-SA 4.0
2019-02-08T15:48:27.687Z
Not yet. I have to redo the setup to verify if I've done anything wrong
DoomerDGR8
CC BY-SA 4.0
2019-02-23T10:31:11.880Z
I tried with the line uncommented but the result is the same. The head still pushed down on the hot plate such that the springs are a bit compressed.
DoomerDGR8
CC BY-SA 4.0
2019-02-24T21:38:54.593Z
@HassanGulzar As far as can be seen the configuration is fine, to be sure add a link to your configuration.h file. What you describe now is that it works correctly, but it is not tuned correctly.
0scar
CC BY-SA 4.0
2019-01-30T19:48:02.107Z
2019-02-23T22:39:24.930Z
2019-02-23T22:39:24.930Z
0scar
<p>I got things moving from the <a href="https://3dprinting.stackexchange.com/a/8086/12450">answer to a previous question</a>. Now, since the base-video I'm following is non-English, I want the next phase fixed: <code>Probing failed</code></p>

<p><a href="https://youtu.be/MeEs7pwrEUA" rel="nofollow noreferrer">Auto Homing showing failing Z-homing</a></p>

<p><a href="https://i.sstatic.net/0OEPQ.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/0OEPQ.jpg" alt="ProbeErrorLCD"></a></p>

<p>After the final adjusted firmware upload, and bringing the sensor up, I see that the extruder pushes the bed down a bit when I auto home and then the LCD screen says probing failed.</p>

<p>If compare to the latest (v1.1.9) Configuration.h file from <a href="https://github.com/MarlinFirmware/Marlin/blob/1.1.x/Marlin/example_configurations/Anet/A8/Configuration.h" rel="nofollow noreferrer">GitHub</a>, here are the changes:</p>

<pre><code>#define FIX_MOUNTED_PROBE // Line #0719, Uncommented

#define X_PROBE_OFFSET_FROM_EXTRUDER 16  // Line # 0779, Was 0
#define Y_PROBE_OFFSET_FROM_EXTRUDER 58  // Line # 0780, Was 0

#define Z_HOMING_HEIGHT 5 // Line # 0870, Was 4  

// #define MIN_SOFTWARE_ENDSTOP_Z // Line # 0907 Commented

#define AUTO_BED_LEVELING_LINEAR // Line # 0977, Uncommented

#define LEFT_PROBE_BED_POSITION  (X_PROBE_OFFSET_FROM_EXTRUDER + MIN_PROBE_EDGE) // Line # 1027, Uncommented
#define RIGHT_PROBE_BED_POSITION (X_BED_SIZE                   - MIN_PROBE_EDGE) // Line # 1028, Uncommented
#define FRONT_PROBE_BED_POSITION (Y_PROBE_OFFSET_FROM_EXTRUDER + MIN_PROBE_EDGE) // Line # 1029, Uncommented
#define BACK_PROBE_BED_POSITION  (Y_BED_SIZE                   - MIN_PROBE_EDGE) // Line # 1030, Uncommented

#define Z_SAFE_HOMING // Line # 1144, Uncommented
</code></pre>

<p>From the above changeset, lines 1027-1030 are from the other SO question I mentioned above, the remaining are following the video.</p>

<p>After completing the steps up to the point where I push the firmware and have to lift the ROKO up <a href="https://youtu.be/uY4GlbV4kGU?t=1222" rel="nofollow noreferrer">I followed instructions in this video</a>, my "Auto Home" operation is failing.</p>

<p><strong>Update 1</strong></p>

<p>I used Pronterface as recommended by @dgrat in comments below and got this result:</p>

<pre><code>&gt;&gt;&gt; M119
SENDING:M119
Reporting endstop status
x_min: open
y_min: open
z_min: TRIGGERED
</code></pre>

<p>I did not get the Probing failed message this time.</p>

<p>What's next?</p>

<p><strong>Update 2</strong></p>

<p>I also went ahead and tried out the <a href="https://3dprinting.stackexchange.com/a/8098/12450">second answer</a>, where @0scar is recommending to uncomment <code>#define MIN_SOFTWARE_ENDSTOP_Z</code>.</p>

<p>The results are exactly the same: The head hits the hotbed and goes back and then comes down slowly hitting and compressing the spring a bit before stopping. I did not get the Probing failed message this time.</p>

CC BY-SA 4.0
2019-01-30T11:37:51.420Z
Does the endstop trigger?
dgrat
CC BY-SA 4.0
2019-01-30T11:41:50.823Z
@dgrat How do I detect that trigger?
DoomerDGR8
CC BY-SA 4.0
2019-01-30T12:11:04.080Z
There is a command for that. http://marlinfw.org/docs/gcode/M119.html. I use it now and then with http://www.pronterface.com/. You are not the first one with such problems. I suggest to always test the switches before using the machine to avoid damage.
dgrat
CC BY-SA 4.0
2019-02-23T10:09:20.590Z
@dgrat please check update to thread
DoomerDGR8
CC BY-SA 4.0
2019-02-23T10:48:47.287Z
I also tested that raising the z-axis by just 2 nm makes the A4 paper on the bed move with an acceptable resistance. Have I hardcoded the Z position somehow?
DoomerDGR8
<marlin><anet-a8><bed-leveling><homing><inductive-sensor>
Anet A8 with Marlin firmware: Auto Home is crashing into bed
DoomerDGR8
# Anet A8 with Marlin firmware: Auto Home is crashing into bed

(Asked by: username_0 on 2019-01-30)

I got things moving from the answer to a previous question. Now, since the base-video I'm following is non-English, I want the next phase fixed: Probing failed
Auto Homing showing failing Z-homing

After the final adjusted firmware upload, and bringing the sensor up, I see that the extruder pushes the bed down a bit when I auto home and then the LCD screen says probing failed.
If compare to the latest (v1.1.9) Configuration.h file from GitHub, here are the changes:
#define FIX_MOUNTED_PROBE // Line #0719, Uncommented

#define X_PROBE_OFFSET_FROM_EXTRUDER 16  // Line # 0779, Was 0
#define Y_PROBE_OFFSET_FROM_EXTRUDER 58  // Line # 0780, Was 0

#define Z_HOMING_HEIGHT 5 // Line # 0870, Was 4  

// #define MIN_SOFTWARE_ENDSTOP_Z // Line # 0907 Commented

#define AUTO_BED_LEVELING_LINEAR // Line # 0977, Uncommented

#define LEFT_PROBE_BED_POSITION  (X_PROBE_OFFSET_FROM_EXTRUDER + MIN_PROBE_EDGE) // Line # 1027, Uncommented
#define RIGHT_PROBE_BED_POSITION (X_BED_SIZE                   - MIN_PROBE_EDGE) // Line # 1028, Uncommented
#define FRONT_PROBE_BED_POSITION (Y_PROBE_OFFSET_FROM_EXTRUDER + MIN_PROBE_EDGE) // Line # 1029, Uncommented
#define BACK_PROBE_BED_POSITION  (Y_BED_SIZE                   - MIN_PROBE_EDGE) // Line # 1030, Uncommented

#define Z_SAFE_HOMING // Line # 1144, Uncommented

From the above changeset, lines 1027-1030 are from the other SO question I mentioned above, the remaining are following the video.
After completing the steps up to the point where I push the firmware and have to lift the ROKO up I followed instructions in this video, my "Auto Home" operation is failing.
Update 1
I used Pronterface as recommended by @dgrat in comments below and got this result:
>>> M119
SENDING:M119
Reporting endstop status
x_min: open
y_min: open
z_min: TRIGGERED

I did not get the Probing failed message this time.
What's next?
Update 2
I also went ahead and tried out the second answer, where @0scar is recommending to uncomment #define MIN_SOFTWARE_ENDSTOP_Z.
The results are exactly the same: The head hits the hotbed and goes back and then comes down slowly hitting and compressing the spring a bit before stopping. I did not get the Probing failed message this time.

**Tags:** marlin, anet-a8, bed-leveling, homing, inductive-sensor
> **Comments:**
> **username_1**: Does the endstop trigger?  
> **username_0**: @dgrat How do I detect that trigger?  
> **username_1**: There is a command for that. http://marlinfw.org/docs/gcode/M119.html. I use it now and then with http://www.pronterface.com/. You are not the first one with such problems. I suggest to always test the switches before using the machine to avoid damage.  
> **username_0**: @dgrat please check update to thread  
> **username_0**: I also tested that raising the z-axis by just 2 nm makes the A4 paper on the bed move with an acceptable resistance. Have I hardcoded the Z position somehow?  

---

## 1 answers

### Answer by username_2 on 2019-01-30. Score: 1

You should un-comment the following line to get rid of the Probing failed error message:
// #define MIN_SOFTWARE_ENDSTOP_Z // Line # 0907 Commented

to
#define MIN_SOFTWARE_ENDSTOP_Z

You have basically disabled the use of the minimum Z endstop, while in fact you are using one, the difference is that it is a sensor now, not a mechanical switch.
Please note the distance of the sensor to the bed, it looks as though it is pretty far away. Before sending an auto home command, it is better to test the endstop triggering beforehand; an external application (e.g. Pronterface, Repetier-Host, OctoPrint, etc.), USB cable and a laptop/computer can be used to send G-code commands through the terminal of the external application. Code M119 will output the endstop trigger status to the terminal.

> **Comments:**
> **username_0**: I'll make this change and push firmware again. Will get back on this. I do not know why the guy in the video commented this out.  
> **username_2**: @HassanGulzar Have you fixed this, if not update your question so that other people may answer, or an update can be made.  
> **username_0**: Not yet. I have to redo the setup to verify if I've done anything wrong  
> **username_0**: I tried with the line uncommented but the result is the same. The head still pushed down on the hot plate such that the springs are a bit compressed.  
> **username_2**: @HassanGulzar As far as can be seen the configuration is fine, to be sure add a link to your configuration.h file. What you describe now is that it works correctly, but it is not tuned correctly.  

---

