-
-
Notifications
You must be signed in to change notification settings - Fork 361
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.
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
Probe stowed during mesh levelling, Z-Axis still goes down #1306
Comments
Hi, this is not a general printer support forum. Many problems can be easily solved by reading the firmware Wiki please check the calibration guide. This Issue Queue is for firmware bug reports and development-related issues, and we prefer not to handle user-support questions here. For best results getting help with configuration and troubleshooting, please use the following resources: Enhanced support in Patreon: https://www.patreon.com/mriscoc Free community support:
|
My apologies, I didn't read that far into the mesh levelling page. I appreciate the prompt response. |
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. |
Did you test with a precompiled firmware?
Yes, and the problem still exists.
Bug Description
At random points during the mesh levelling procedure, my CR touch probe will stow, but the Z-axis still goes down, causing the nozzle to crash into the bed and a NaN point to appear in the mesh. Happens in both manual mesh levelling and AML process.
Bug Timeline
At update to 20240125
Expected behavior
I expected the probe not to stow and properly probe the bed.
Actual behavior
The probe stowed at random time and the nozzle crashed into the bed.
Steps to Reproduce
Version of Professional Firmware
20240125
Printer model
Ender 3 v2 NEO
Electronics
Board 4.2.2
LCD/Controller
No response
Other add-ons
CR Touch
Bed Leveling
UBL Bilinear mesh
Your Slicer
Cura
Host Software
None
Additional information & file uploads
No response
The text was updated successfully, but these errors were encountered: