-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[toolchanger] [PrusaXL] M104.1 inserted before purge #6285
Comments
AFAIK a proper multi toolhead support (incl. Prusa XL) is not available in 2.1.1 (see #6087) |
my wrong on version number. I was using the latest dev, so the bug is still there. See the discord |
Probably a firmware bug. Sunday evening I will test it (prusaslicer, with default stealth on, adds a Q param to m104.1) |
as explained here #6345, M104.1 is useless because it is processed as it was standard M104 by prusa fw... |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
M104.1 should be disabled, at least for current tool |
Orca bot: this issue is stale because it has been open for 90 days with no activity. |
M104.1 should be disabled, at least for current tool |
Is there an existing issue for this problem?
OrcaSlicer Version
2.1.1 (Nightly Builds)
Operating System (OS)
Linux
OS Version
Ubuntu 24.04 LTS
Printer
Original Prusa XL 5T
How to reproduce
m104.1 gcode is inserted before the first tool (T0) purge, cause a pause of printing to heat after the purge. Image from slicer, video and project include:
Slicer:

Video:
https://youtu.be/l22OXJjX8fE?feature=shared&t=23
Actual results
m104.1 gcode inserted wrongfully
Expected results
m104.1 gcode should not appear before purging (at least for T0 )
Project file & Debug log uploads
preheatProject.zip
The text was updated successfully, but these errors were encountered: