[BUG] ABL probing fails

[fuganater]

Bug Description

Auto Bed Level via the LCD and G29 via Pronterface fail after probe #3

My Configurations

BLV MNG Cube Config.zip

Steps to Reproduce

G29 - bed leveling fails after probe point #3 and says "probing failed"

Expected behavior: ABL to work

Actual behavior: Fails on probe #3

Additional Information

I'm using an SKR 1.3 with TMC 2209 drivers on a CoreXY printer. My Z sensor is a LJ12A3-4-Z connected with an optocoupler to Z min. I have a 5x5 grid and it probes each location 3 times. I'm running Marlin 2.0.5.3. I have this exact same setup on an i3 and it works as it should.

[sjasonsmith]

Please try the following:

1. Re-test with the latest state of the bugfix-2.0.x branch, if you have not already. It is possible your issue has already been fixed.
2. Enable leveling debug prints with M111 S32 (I see you already have DEBUG_LEVELING_FEATURE enabled in your Configuration.h)
3. Execute G29 to reproduce the failure.
4. Post the debug output here.

That debug output may provide insight into the reason it is failing. You may only need to provide the last portion of the output where the failure occurs. If you have a lot of data to post, consider putting it on pastebin and linking to it from here.

[sjasonsmith]

This is mostly a re-statement of what I said above, but I didn't provide the complete instructions which are now provided when debugging leveling/probing issues. Here it is for completeness:

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information so that we're not just taking stabs in the dark. Here is the boilerplate:

• Download Marlin bugfix-2.0.x to test with the latest code.
• Enable DEBUG_LEVELING_FEATURE and M114_DETAIL and re-flash the firmware.
• Connect to your printer from host software such as Cura, Printrun or Repetier Host.
• Send M502 and M500 to ensure your Configurations are applied.
• Issue the command M111 S247 to enable maximum logging.
• Perform a G28 to do your standard homing procedure.
• Do a G29 to probe the bed. This will also enable bed leveling.
• Do some of the moves that revealed problems before. Take notes.
• Copy the log output into a .TXT file and attach it to your next reply.
• Repeat this procedure, if needed, to demonstrate inconsistencies. From these logs we should hopefully get a better idea of what's going on with your machine.

[Dracrius]

@fuganater Try disabling/ commenting out #define ADAPTIVE_STEP_SMOOTHING I spent the last day dialing prob issues to this setting in #18598 .

I also had failures if I enabled #define MULTIPLE_PROBING and after checking your configs you have both settings enabled. After all my testing though I am sure you can leave #define MULTIPLE_PROBING 3 though it may be unneeded after you disable #define ADAPTIVE_STEP_SMOOTHING as my Bltouch meshes are fairly consistent with the default single probe mode.

As far as I can tell the outright failure with #define MULTIPLE_PROBING is because with multiple probing marlin must pickup the error in probing and throw a Probe Failure vs without where it just takes the odd readings from the ADAPTIVE_STEP_SMOOTHING bug as the bed depth resulting in a mesh with 1 or more -1mm dips.

[sjasonsmith]

This is not using a BLTouch, so it would not be related to the unstable PWM signal that ADAPTIVE_STEP_SMOOTHING can cause. I don't think there is anything actionable on this right now, until @fuganater replies with additional information.

[boelle]

@fuganater still with us? do you still have the problem or is it solved?

Please test the bugfix-2.0.x branch to see where it stands

[fuganater]

@fuganater still with us? do you still have the problem or is it solved?

Please test the bugfix-2.0.x branch to see where it stands

Yes I am here! I did upgrade to the newest Bugfix and it seems to have solved the issue!!

[thisiskeithb]

I did upgrade to the newest Bugfix and it seems to have solved the issue!!

Great 🙂

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.