-
Notifications
You must be signed in to change notification settings - Fork 246
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
[BFW-5476] [BUG] Pinda going out of bed for large prints #3971
Labels
bug
Something isn't working.
Comments
CZDanol
changed the title
[BUG] Pinda out of bed
[BUG] Pinda going out of bed for large prints
May 3, 2024
CZDanol
changed the title
[BUG] Pinda going out of bed for large prints
[BFW-5476] [BUG] Pinda going out of bed for large prints
May 3, 2024
Internal ticket: BFW-5476 |
CZDanol
added
the
scheduled
We are working on it or we have scheduled it for one of the next releases.
label
May 3, 2024
danopernis
added
duplicate
This issue or pull request already exists.
and removed
scheduled
We are working on it or we have scheduled it for one of the next releases.
labels
Jun 27, 2024
Issue more insidious than that! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Printer
Mk3.5
Original FW 6.0.0
Prusa Mk3S to Mk3.5 Upgrade Kit (Standard)
USB Drive
Problem
If an object on the print bed extends beyond about X = 180mm (or so), then Auto Mesh Levelling will fail.
After AutoHome, the printhead will travel to XMAX placing the PINDA probe beyond the printbed.
Moving to the first Mesh probe point, the first probe will try to drive the nozzle through the printbed, generating a Failure.
Mimic
Place any object on the furthest right limit (XMAX), and slice with PrusaSlicer 2.7.4.
Save bGCode and Print.
Expected behavior
It should have printed.
I consider the PINDA X Offset might be involved? Or not contemplated by the new Mesh algorithm?
G-code
PS generates BGCode (not supported by GitHub), so file attached as .ZIP
fuse3 Mk3.5_0.4n_0.2mm_PLA_MK3.5_5h21m.zip
The text was updated successfully, but these errors were encountered: