Z- Probing G28 works but G29 gives Probing failed

Dear Forum,

I am having a pretty weired behavior on my Core- XY type printer.

I use Marlin 2.0 bugfix and an inductive probe.

If I send G28 homing of all axis works like a charm. If I send G29 afterwards, autobed leveling is running without any difficulties. I can see the LED of the probe changing on all spots that are probed, meaning that the build plate has been detected successfully. But after bed leveling I get a "probing failed" message on the display.

Any ideas what's going wrong?

Thanks in advance for your appreciated help.

P.S.: I will post the config as soon as I can access it because it is burried in a computer without network and thumbrive

Edited 2 time(s). Last edit at 05/09/2019 03:46PM by Louis Cypher.

I did somer more debugging using the debug option. The printer stops the bed leveling and says. SLOW Probe Failed.

any ideas? I have been searching for the problem a couple of nights already and would highly appreciate help.

echoEBUG:LEVELING
ok
  current_position=(102.00, 42.00, -0.70) : >>> G29
Machine Type: Core
Probe: FIX_MOUNTED_PROBE
Probe Offset X:5 Y:65 Z:-1.30 (Right-Back & Below Nozzle)
Auto Bed Leveling: LINEAR
 (disabled)

  current_position=(102.00, 42.00, -0.70) : set_probe_deployed
deploy: 1
do_probe_raise(10.00)
>>> do_blocking_move_to(102.00, 42.00, 11.30)
<<< do_blocking_move_to
echo:busy: processing
>>> do_blocking_move_to(102.00, 42.00, 11.30)
<<< do_blocking_move_to
>>> probe_pt(75.00, 75.00, raise, 0, probe_relative)
  current_position=(102.00, 42.00, 11.30) : 
>>> do_blocking_move_to(70.00, 10.00, 11.30)
<<< do_blocking_move_to
  current_position=(70.00, 10.00, 11.30) : set_probe_deployed
deploy: 1
  current_position=(70.00, 10.00, 11.30) : >>> run_z_probe
  current_position=(70.00, 10.00, 11.30) : >>> do_probe_move
>>> do_blocking_move_to(70.00, 10.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
echo:busy: processing
echo:busy: processing
  current_position=(70.00, 10.00, 0.39) : sync_plan_position
  current_position=(70.00, 10.00, 0.39) : <<< do_probe_move
  current_position=(70.00, 10.00, 0.39) : <<< run_z_probe
>>> do_blocking_move_to(70.00, 10.00, 5.39)
<<< do_blocking_move_to
echo:busy: processing
<<< probe_pt
>>> probe_pt(104.00, 75.00, raise, 0, probe_relative)
  current_position=(70.00, 10.00, 5.39) : 
>>> do_blocking_move_to(99.00, 10.00, 5.39)
<<< do_blocking_move_to
  current_position=(99.00, 10.00, 5.39) : set_probe_deployed
deploy: 1
  current_position=(99.00, 10.00, 5.39) : >>> run_z_probe
  current_position=(99.00, 10.00, 5.39) : >>> do_probe_move
>>> do_blocking_move_to(99.00, 10.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
  current_position=(99.00, 10.00, 0.40) : sync_plan_position
  current_position=(99.00, 10.00, 0.40) : <<< do_probe_move
  current_position=(99.00, 10.00, 0.40) : <<< run_z_probe
>>> do_blocking_move_to(99.00, 10.00, 5.40)
<<< do_blocking_move_to
echo:busy: processing
<<< probe_pt
>>> probe_pt(133.00, 75.00, raise, 0, probe_relative)
  current_position=(99.00, 10.00, 5.40) : 
>>> do_blocking_move_to(128.00, 10.00, 5.40)
<<< do_blocking_move_to
  current_position=(128.00, 10.00, 5.40) : set_probe_deployed
deploy: 1
  current_position=(128.00, 10.00, 5.40) : >>> run_z_probe
  current_position=(128.00, 10.00, 5.40) : >>> do_probe_move
>>> do_blocking_move_to(128.00, 10.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
echo:busy: processing
  current_position=(128.00, 10.00, 0.50) : sync_plan_position
  current_position=(128.00, 10.00, 0.50) : <<< do_probe_move
  current_position=(128.00, 10.00, 0.50) : <<< run_z_probe
>>> do_blocking_move_to(128.00, 10.00, 5.50)
<<< do_blocking_move_to
<<< probe_pt
>>> probe_pt(133.00, 104.00, raise, 0, probe_relative)
  current_position=(128.00, 10.00, 5.50) : 
>>> do_blocking_move_to(128.00, 39.00, 5.50)
<<< do_blocking_move_to
  current_position=(128.00, 39.00, 5.50) : set_probe_deployed
deploy: 1
  current_position=(128.00, 39.00, 5.50) : >>> run_z_probe
  current_position=(128.00, 39.00, 5.50) : >>> do_probe_move
>>> do_blocking_move_to(128.00, 39.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
echo:busy: processing
  current_position=(128.00, 39.00, -0.50) : sync_plan_position
  current_position=(128.00, 39.00, -0.50) : <<< do_probe_move
  current_position=(128.00, 39.00, -0.50) : <<< run_z_probe
>>> do_blocking_move_to(128.00, 39.00, 4.50)
<<< do_blocking_move_to
echo:busy: processing
<<< probe_pt
>>> probe_pt(104.00, 104.00, raise, 0, probe_relative)
  current_position=(128.00, 39.00, 4.50) : 
>>> do_blocking_move_to(99.00, 39.00, 4.50)
<<< do_blocking_move_to
  current_position=(99.00, 39.00, 4.50) : set_probe_deployed
deploy: 1
  current_position=(99.00, 39.00, 4.50) : >>> run_z_probe
  current_position=(99.00, 39.00, 4.50) : >>> do_probe_move
>>> do_blocking_move_to(99.00, 39.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
  current_position=(99.00, 39.00, -0.60) : sync_plan_position
  current_position=(99.00, 39.00, -0.60) : <<< do_probe_move
  current_position=(99.00, 39.00, -0.60) : <<< run_z_probe
>>> do_blocking_move_to(99.00, 39.00, 4.40)
<<< do_blocking_move_to
echo:busy: processing
<<< probe_pt
>>> probe_pt(75.00, 104.00, raise, 0, probe_relative)
  current_position=(99.00, 39.00, 4.40) : 
>>> do_blocking_move_to(70.00, 39.00, 4.40)
<<< do_blocking_move_to
  current_position=(70.00, 39.00, 4.40) : set_probe_deployed
deploy: 1
  current_position=(70.00, 39.00, 4.40) : >>> run_z_probe
  current_position=(70.00, 39.00, 4.40) : >>> do_probe_move
>>> do_blocking_move_to(70.00, 39.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
echo:busy: processing
  current_position=(70.00, 39.00, -0.69) : sync_plan_position
  current_position=(70.00, 39.00, -0.69) : <<< do_probe_move
  current_position=(70.00, 39.00, -0.69) : <<< run_z_probe
>>> do_blocking_move_to(70.00, 39.00, 4.31)
<<< do_blocking_move_to
<<< probe_pt
>>> probe_pt(75.00, 133.00, raise, 0, probe_relative)
  current_position=(70.00, 39.00, 4.31) : 
>>> do_blocking_move_to(70.00, 68.00, 4.31)
<<< do_blocking_move_to
  current_position=(70.00, 68.00, 4.31) : set_probe_deployed
deploy: 1
  current_position=(70.00, 68.00, 4.31) : >>> run_z_probe
  current_position=(70.00, 68.00, 4.31) : >>> do_probe_move
>>> do_blocking_move_to(70.00, 68.00, -0.70)
<<< do_blocking_move_to
echo:busy: processing
echo:busy: processing
  current_position=(70.00, 68.00, -0.70) : sync_plan_position
  current_position=(70.00, 68.00, -0.70) : <<< do_probe_move
SLOW Probe fail!
  current_position=(70.00, 68.00, -0.70) : <<< run_z_probe
>>> do_blocking_move_to(70.00, 68.00, 4.30)
<<< do_blocking_move_to
  current_position=(70.00, 68.00, 4.30) : set_probe_deployed
deploy: 0
>>> do_blocking_move_to(70.00, 68.00, 4.30)
<<< do_blocking_move_to
Errorrobing failed
<<< probe_pt
  current_position=(70.00, 68.00, 4.30) : set_probe_deployed
deploy: 0
  current_position=(70.00, 68.00, 4.30) : > probing complete
<<< G29
X:70.00 Y:68.00 Z:4.30 E:0.00 Count A:11040 B:160 Z:11008
ok

My config as well as the complete debugging log is attached. Configuration.h Configuration_adv.h Fehlermeldung.txt

Hi there,

I get more or less the same error. I had a problem getting my inductive sensor working but it is working fine now, using an optocoupler. The problem is that if I do a g28 everything seems to run well. When I do a G29, my X and Y (alpha and beta) steppers start behaving erratically and it seems it does not know what to do and fails with "probing fails". This started happening last night. I have a re-arm board with a Ramps 1.4 and it is a coreyx machine. I have Marlin 2.0 installed on the re-arm. My config file for Marlin 2.0 did work perfectly on the Arduino Mega

I did not have time to look deeper into my problem yet but will give feedback when I know more.

Can you please give me a short rundown of how to do the leveling debugging, please.

Edited 1 time(s). Last edit at 05/10/2019 07:42AM by scratchbuild52@gmail.com.

You have to uncomment the respective line in the config, compile and send M111 S32 before sending G29.

Do you maybe have negative values in your step settings? I think your problem is by accident leveling related.

Best,

Louis

Edited 2 time(s). Last edit at 05/11/2019 01:58AM by Louis Cypher.

Hi, thanks for the reply, I found out my vref on my A4988 drivers were set too low and therefore behaved erratic. I am up and running again.


Thanks a lot

Hi all,

I'm getting the same issue here - I'm on Marlin 1.1.9 and here's my debug log:

G29
Machine Type: Cartesian
Probe: FIX_MOUNTED_PROBE
Probe Offset X:20 Y:0 Z:-2.75 (Right-Center & Below Nozzle)
Auto Bed Leveling: BILINEAR (disabled)

  current_position=(155.00, 25.00, 5.75) : set_probe_deployed
deploy: 1
do_probe_raise(5.00)
>>> do_blocking_move_to(155.00, 25.00, 7.75)
<<< do_blocking_move_to
>>> do_blocking_move_to(155.00, 25.00, 7.75)
<<< do_blocking_move_to
  current_position=(155.00, 25.00, 7.75) : setup_for_endstop_or_probe_move
>>> probe_pt(25.00, 25.00, raise, 0, probe_relative)
  current_position=(155.00, 25.00, 7.75) : 
>>> do_blocking_move_to(5.00, 25.00, 7.75)
echo:busy: processing
<<< do_blocking_move_to
  current_position=(5.00, 25.00, 7.75) : set_probe_deployed
deploy: 1
  current_position=(5.00, 25.00, 7.75) : >>> run_z_probe
  current_position=(5.00, 25.00, 7.75) : >>> do_probe_move
>>> do_blocking_move_to(5.00, 25.00, 0.75)
echo:busy: processing
<<< do_blocking_move_to
  current_position=(5.00, 25.00, 2.06) : sync_plan_position
  current_position=(5.00, 25.00, 2.06) : <<< do_probe_move
  current_position=(5.00, 25.00, 2.06) : <<< run_z_probe
>>> do_blocking_move_to(5.00, 25.00, 7.06)
echo:busy: processing
echo:busy: processing
<<< do_blocking_move_to
<<< probe_pt
>>> probe_pt(100.00, 25.00, raise, 0, probe_relative)
  current_position=(5.00, 25.00, 7.06) : 
>>> do_blocking_move_to(80.00, 25.00, 7.06)
<<< do_blocking_move_to
  current_position=(80.00, 25.00, 7.06) : set_probe_deployed
deploy: 1
  current_position=(80.00, 25.00, 7.06) : >>> run_z_probe
  current_position=(80.00, 25.00, 7.06) : >>> do_probe_move
>>> do_blocking_move_to(80.00, 25.00, 0.75)
echo:busy: processing
<<< do_blocking_move_to
  current_position=(80.00, 25.00, 1.37) : sync_plan_position
  current_position=(80.00, 25.00, 1.37) : <<< do_probe_move
  current_position=(80.00, 25.00, 1.37) : <<< run_z_probe
>>> do_blocking_move_to(80.00, 25.00, 6.37)
echo:busy: processing
echo:busy: processing
<<< do_blocking_move_to
<<< probe_pt
>>> probe_pt(175.00, 25.00, raise, 0, probe_relative)
  current_position=(80.00, 25.00, 6.37) : 
>>> do_blocking_move_to(155.00, 25.00, 6.37)
<<< do_blocking_move_to
  current_position=(155.00, 25.00, 6.37) : set_probe_deployed
deploy: 1
  current_position=(155.00, 25.00, 6.37) : >>> run_z_probe
  current_position=(155.00, 25.00, 6.37) : >>> do_probe_move
>>> do_blocking_move_to(155.00, 25.00, 0.75)
echo:busy: processing
echo:busy: processing
<<< do_blocking_move_to
  current_position=(155.00, 25.00, 0.75) : sync_plan_position
  current_position=(155.00, 25.00, 0.75) : <<< do_probe_move
SLOW Probe fail!
  current_position=(155.00, 25.00, 0.75) : <<< run_z_probe
>>> do_blocking_move_to(155.00, 25.00, 5.75)
echo:busy: processing
<<< do_blocking_move_to
Errorrobing failed
<<< probe_pt
  current_position=(155.00, 25.00, 5.75) : set_probe_deployed
deploy: 0
>>> do_blocking_move_to(155.00, 25.00, 5.75)
<<< do_blocking_move_to
  current_position=(155.00, 25.00, 5.75) : > probing complete
  current_position=(155.00, 25.00, 5.75) : clean_up_after_endstop_or_probe_move
<<< G29
X:155.00 Y:25.00 Z:5.75 E:0.00 Count X:12400 Y:2000 Z:14720
ok

This is using bilinear levelling.

Cheers

Joe

---

JK3D Blog - [jk3d.wordpress.com]

Just as a follow-up:

I didn't get anywhere with this issue on Marlin 1.1.9, so I thought I'd give an earlier version of Marlin a go and hey presto! 1.1.6 works just fine! Oh well, just glad it's functional again

---

JK3D Blog - [jk3d.wordpress.com]

Since that is the case I think we should file a bug report, right? I have the feeling that my problem as well is upgrade related. I will give dowgrading to a 1.x version a try as well.

I'll try 1.1.7 and 1.1.8 as well and see where it stops working.

---

JK3D Blog - [jk3d.wordpress.com]

Any findings on this? I currently disabled auto bed leveling which works "kind of fine"

I've had a few issues with Marlin 1.1.9 and moved on to 2.x and now these issues are gone. You could try out 2.x maybe

---

http://www.marinusdebeer.nl/

Thanks, I already did as you can read in my initial post. Still struggling to get this up and running. I filed an issue on GitHub.

I also got the probing failed error and just fifured out the problem.The reason was my bed was to badly unleveled and not firmly installed,difference between 2 probe points was over 4mm.
After tightening a few screws and adjusting the bed to a better level,auto calibration can work now.