prusa3d / Prusa-Firmware

Firmware for Original Prusa i3 3D printer by PrusaResearch
GNU General Public License v3.0
2.02k stars 1.05k forks source link

[FEATURE REQUEST] MMU3 Spool Join and muli-color printing reload used filament #4566

Closed x-malet closed 4 months ago

x-malet commented 8 months ago

Printer type: MK3S+ i3 + revo Printer firmware: e3d_REVO_fw_MK3_MK3S_MK3S+_3_13_2_7080

MMU: MMU3 MMU firmware: 3.13.2 (3.0.1)

When making a long multi-color print, I had a spool than run off (let's says, filament 1) and the next one (logically filament 2) was used because the Spool Join option was on. The problem is than when switching back to this color, it used the empty filament tray (filament 1) then change it to the next one (filament 2).

The problem is that the filament 1 is loaded then unloaded and filament 2 is loaded. The print head move to the front-right corner of the print bed and then, the print head is purged.

Problem:

The purge filament can cause print error because it's not purged on the wipe tower but, in the air.

Request:

Can it "save" the new filament to used when doing a multi-color print with Spool Join ON or, wipe the old filament on the wipe tower ?

Thanks !

Step to reproduce:

  1. Activate Spool Join
  2. Make a object with 2 colors
  3. Make sure than one of the color is "empty" (the filament have to be inserted in the MMU so the MMU detect the filament and can load it to the print head)
  4. Start printing with the "not empty" color
  5. Check the color change for the "empty" color a. The old color is wiped on the wipe tower b. The filament will be loaded to the print head c. The filament will be unloaded to the MMU d. The new filament is loaded e. The print head move to front-right and purge the old "empty" color
github-actions[bot] commented 5 months ago

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.

github-actions[bot] commented 4 months ago

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.