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.

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

[BUG] Print bed is not probed for wipe tower, resulting in crashed nozzle and damaged print sheet #13983

Open
RichiH opened this issue Jan 14, 2025 · 4 comments
Labels

Comments

@RichiH
Copy link
Contributor

RichiH commented Jan 14, 2025

Printer model

XL 5T

Firmware version

6.1.3+7898

Upgrades and modifications

1T->5T

Printing from...

USB drive

Describe the bug

The XL 5T is only probing the main print area, not the wipe tower area. The nozzle crashed into my print sheet where the wipe tower is supposed to be. As enabling input shaping still forces disabling of crash detection, the crashed nozzle scraped and damaged the print bed.

The XL then stopped because it detected "stuck filament".

This would be funnier if it hadn't irreparably damaged my print bed.

Screenshot_20250114_123434
Screenshot_20250114_123502
Screenshot_20250114_124510

How to reproduce

No response

Expected behavior

No response

Files

bgcode.zip

@RichiH RichiH added the bug label Jan 14, 2025
@RichiH RichiH changed the title [BUG] Print bed is not probed for wipe tower [BUG] Print bed is not probed for wipe tower, resulting in crashed nozzle and damaged print sheet Jan 14, 2025
@RichiH
Copy link
Contributor Author

RichiH commented Jan 14, 2025

Adding the 3MF
project.zip

@hejllukas hejllukas transferred this issue from prusa3d/Prusa-Firmware-Buddy Jan 14, 2025
@RichiH
Copy link
Contributor Author

RichiH commented Jan 14, 2025

Happening on PrusaSlicer 2.9.0, Linux with flatpack

@rtyr
Copy link
Collaborator

rtyr commented Jan 15, 2025

I was not able to reproduce it with provided 3MF on 2.9.0 win64.

Print area was correct in my case:
M555 X25.4049 Y25.4088 W217.795 H127.365

But print area is indeed incorrect in provided bgcode:
M555 X25.4049 Y25.4088 W34.8217 H34.8307

We will try to figure out how it could happen.

@hejllukas
Copy link
Collaborator

Hi, we were able to reproduce your issue.
I created an internal issue, no. SPE-2645.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants