Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[BUG] 2.0.8 "Probing Failed" #21767

Closed
rq3 opened this issue May 1, 2021 · 18 comments
Closed

[BUG] 2.0.8 "Probing Failed" #21767

rq3 opened this issue May 1, 2021 · 18 comments
Labels
F: Calibration K: Deltabot

Comments

@rq3
Copy link

rq3 commented May 1, 2021

Did you test the latest bugfix-2.0.x code?

Yes, and the problem still exists.

Bug Description

Compiled 2.0.8 using the latest configuration/examples/delta/Anycubic/Predator configuration.h and configuration_adv.h
Compile went flawlessly, and bin file loaded fine. The printer prints. BUT, any attempt to use the probe for delta calibration, M48 repeatability, or bed leveling immediately results in a "Probing Failed" message after the effector lowers to the deploy/stow position.

Bug Timeline

New bug which showed up with 2.0.8. Marlin 2.0.7.2 works fine.

Expected behavior

I expect the machine to succeed with an M48 repeatability test, a delta calibration, or bed leveling.

Actual behavior

The machine goes to the deploy/stow position, requests a deploy, requests a stow, and then reports "Probing Failed".

Steps to Reproduce

  1. Download Marlin 2.0.8
  2. Download the Anycubic Predator configuration files for 2.0.8
  3. Modify platformio.ini for the trigorilla_pro environment
  4. Successfully compile 2.0.8 using Visual Studio
  5. Install the resulting firmware.bin on the printer
  6. Initialize the printer EEPROM
  7. Power cycle the printer
  8. Attempt to use the z axis probe in any way

Version of Marlin Firmware

2.0.8

Printer model

Anycubic Predator

Electronics

stock Chitu Trigorilla Pro

Add-ons

none

Your Slicer

Cura

Host Software

No response

Additional information & file uploads

No response
@thisiskeithb
Copy link
Member

Whenever there are homing or leveling issues, we now ask everyone to follow a standard procedure to gather more information:

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

@rq3
Copy link
Author

rq3 commented May 1, 2021

Here you go. Copied from the log in Repetier Host:

2.0.8_Probing_Failure.txt

@lujios
Copy link
Contributor

lujios commented May 2, 2021

I think I have located the bug. There is a recent modification in motion.cpp, which causes the mentioned error. If you think it is convenient, I will open a pull request, with the solution that I propose.
The solution is tested, with OK result.

@lujios lujios mentioned this issue May 2, 2021
Closed
@rq3
Copy link
Author

rq3 commented May 2, 2021 •
edited
Loading

I just compiled and installed the very latest bugfix (May 2 AM) with its associated example configuration files. It no longer says "Probing Failed". Instead it moves to the deploy/stow position and asks for a deploy. I did so. It then immediately says "Stow Probe". I did so. It then immediately says "Deploy Probe". This goes on, apparently, forever. The effector never moved after the first positioning.

Re-installed my 2.0.7.2 firmware, and back to successful probing and printing.

@rhapsodyv
Copy link
Member

Can you try reverting this commit 4044ed8 and test if the issue is gone?

@lujios
Copy link
Contributor

lujios commented May 2, 2021 •
edited
Loading

I am sorry.
My setup is ready for SENSORLESS_PROBING. It is very possible that for this reason it will not work if you have probe_Z.
Have you tried with your config files and modifying motion.cpp? It is not a configuration problem, if it was working before.
My pull request was not yet merged into bugfix_2.0.x, so you didn't use my fix.
Thank.

@rq3
Copy link
Author

rq3 commented May 2, 2021 via email

@rq3
Copy link
Author

rq3 commented May 2, 2021 via email

@lujios
Copy link
Contributor

lujios commented May 2, 2021

That works. I downloaded a fresh copy of the latest bugfix, replaced the motion.cpp file, and used the configuration files from my previous Marlin 2.0.8 installation. M48 works fine, and delta calibration appears to be doing its thing, although I did not let it go to completion. Would you like me to replace the motion.cpp file in my Marlin 2.0.8 and see what happens? Best Regards, Rip
…
On 5/2/2021 1:17 PM, Victor Oliveira wrote: Can you try reverting this commit 4044ed8 <4044ed8> and test if the issue is gone? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21767 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAZQMN7PQYWN7SW22JI36G3TLWCJHANCNFSM436VAJLQ.

I am glad to hear. If possible, I appreciate it. So I would test my solution with more configurations.

@rq3
Copy link
Author

rq3 commented May 2, 2021 •
edited
Loading

I should note that my delta has two z axis probes. One is the stock Anycubic microswitch, and the other is a prototype piezo sensor under the bed. I can switch between the two, and they both work with this motion.cpp change (neither would work before in 2.0.8).

Both probes trigger the same z-min pin on the Trigorilla Pro board.

It would appear that motion.cpp commit 4044ed8 is pretty robust, at least for this board. I think that if this commit can be merged into 2.0.8 you can close this issue.

@rhapsodyv
Copy link
Member

It would appear that motion.cpp commit 4044ed8 is pretty robust, at least for this board. I think that if this commit can be merged into 2.0.8 you can close this issue.

There're some confusion here. I think 4044ed8 added the bug by mistake.

@rhapsodyv rhapsodyv mentioned this issue May 2, 2021
Merged
@rhapsodyv
Copy link
Member

@rq3 can you test this PR #21781 ?

It fixes a typo in the code that introduced the issue.

@rq3
Copy link
Author

rq3 commented May 2, 2021 via email

@rq3
Copy link
Author

rq3 commented May 2, 2021 via email

@rhapsodyv
Copy link
Member

Now that you confirmed the fix in #21781 works, @thinkyhead may merge it right away.

@rq3
Copy link
Author

rq3 commented May 2, 2021

@rhapsodyv , sounds good. At least it solved all the issues I can see on my machine.

@rhapsodyv
Copy link
Member

Merged!

@Foxies-CSTL Foxies-CSTL mentioned this issue Jun 18, 2021
Merged
@github-actions
Copy link

github-actions bot commented Jul 2, 2021

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.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
F: Calibration K: Deltabot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rhapsodyv @rq3 @thisiskeithb @lujios