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] Crash when stopping print sliced as "sequential printing" #3623

Closed
1 of 2 tasks
Min-Tec opened this issue Sep 23, 2022 · 4 comments
Closed
1 of 2 tasks

[BUG] Crash when stopping print sliced as "sequential printing" #3623

Min-Tec opened this issue Sep 23, 2022 · 4 comments

Comments

@Min-Tec
Copy link

Min-Tec commented Sep 23, 2022

Description of the bug

When stopping a print which was sliced as "sequential printing" the extruder (nozzle) crashed into another (already printed) part while the printer was moving to its home position.

Gcode which had the problem is attached. The print was stopped when the fourth object started printing (1 to 3 already fully printed).

Could be solved when the z-axis would fully rise to the top before the x- and y-axis would move to their home position.

Project file & How to reproduce

Object_0.2mm_ASA_MK3S_2h35m.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

Version 2.5.0+win64

Operating system

Windows 10

Printer model

Prusa i3 MK3s

@Min-Tec Min-Tec added the bug label Sep 23, 2022
@wavexx
Copy link
Collaborator

wavexx commented Sep 25, 2022

This is internally related to #3496. Looks like we need to keep track of the maximum Z seen on the current print to handle both.

Copy link

github-actions bot commented Nov 9, 2023

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

@ulab
Copy link

ulab commented Nov 9, 2023

This is still something that should be looked at.

@3d-gussner
Copy link
Collaborator

@ulab Thanks for the reminder, but it is a duplicate and I assigned the #3496 to myself to follow up this request.
Closing it.

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

No branches or pull requests

4 participants