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

Lack of filament change time on printer display #13031

Closed
1 of 2 tasks
taz43mca opened this issue Jul 5, 2024 · 14 comments
Closed
1 of 2 tasks

Lack of filament change time on printer display #13031

taz43mca opened this issue Jul 5, 2024 · 14 comments

Comments

@taz43mca
Copy link

taz43mca commented Jul 5, 2024

Description of the bug

Although the printer did stop at the designated layer for the filament change designated in slicer, the time to change did not show on the printer display. previous versions showed remaining time "R" and time to filament change "C" on printer display. My printer is a MK2.5S and both firmware and software are latest versions.

Project file & How to reproduce

Oval Frame C 1988 A STL_0.2mm_PLA_MK2.5S_2h9m_6.09mm_$0.47.gcode.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.8.0

Operating system

windows 11 Pro

Printer model

MK 2.5S

@benring
Copy link

benring commented Jul 7, 2024

I have experienced the exact same issue on my MK3S+. This happened recently when I upgraded from 2.74 to 2.8. I also tried upgrading the firmware on the printer from 3.13 to 3.14 and still had the same issue. I can also confirm that models sliced on 2.74 or earlier still work properly.

@gpapathanasiou
Copy link

I have the same problem with you. I also discovered that, when you slice a project with filament change, the result in the preview shows only the basic color.
image

@YuSanka
Copy link
Collaborator

YuSanka commented Jul 10, 2024

@gpapathanasiou, I believe your issue is the same as #13008 and isn't related with this issue.

@taz43mca and @benring, provide us please the 3mf file, perhaps evaluating your configuration can help us

@fe60
Copy link

fe60 commented Aug 20, 2024

This was reported for 2.8.0-alpha5 in #12849

@lukasmatena
Copy link
Collaborator

Fixed in 2.8.1-rc1. Closing.

@sarusani
Copy link

@lukasmatena Just testet it with 2.8.1-rc1 and it's not fixed. Still the same behavior as in 2.8.0. M73 Cxx codes are not generated for color changes.

@lukasmatena
Copy link
Collaborator

Thanks, my bad. The issue that was fixed was #13008, which seems to be what @gpapathanasiou mentioned here, but this issue was originally about something else. Reopening.

@lukasmatena lukasmatena reopened this Sep 16, 2024
@samdurnxn
Copy link

If it can help to resolve the bug. I made some tests with PrusaSlicer 2.8.1-RC1
Add a shape box.

If I add a break(M601) and a color change(M600). In the Gcode file, no problem M73 Cx and M73 Dy are correctly insert

But If I use multimaterial painting, Tx are correctly insert but not the M73 Cx and M73 Dy

It has been confirm by DanoPernis on the issue : prusa3d/Prusa-Firmware-Buddy#4089 (comment)

I can provide my test file if you need it.

@taz43mca
Copy link
Author

taz43mca commented Sep 18, 2024 via email

@LoakAudio
Copy link

LoakAudio commented Nov 2, 2024

Hi all,
This bug is present on an MK3.5, no MMU, firmware 6.1.3 & PS 2.8.1/Windows 10
Color Change is asked layer 26, gcode viewer show it and the print is ok, but "Prochain Changement : N/A" ("Next Change : N/A" in english I gess) is shown on the main screen during the print.
Here is the bgcode used :
Prusa i3 MK3 Memorial Plain_0.6n_0.32mm_PLA_MK3.5_4h4m.zip

@lukasmatena
Copy link
Collaborator

Can you please retest this with 2.9.0-rc1? It turns out there were multiple issues with the color change time estimate.

@taz43mca
Copy link
Author

taz43mca commented Dec 20, 2024 via email

@lukasmatena
Copy link
Collaborator

Thanks for the update. Closing.

@benring
Copy link

benring commented Dec 22, 2024 via email

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

No branches or pull requests

9 participants