[ENHANCEMENT] Filament change temps

[DanidCH]

I’m wondering if for a filament change it wouldn’t be better to use the hottest of two temperatures (between last filament and new filament) during the purge. This would probably make the change easier.

Here is a specific case to illustrate how this would help: let’s say I used ASA for my print where hotend is set to 260c and I next want to use PLA, while purging the hot end will be set to 215c (recommendation for PLA) when there is probably some ASA left.

Probably setting the hotend temp to the higher temperature will help the purging process.

Enter what type of printer or upgrade the enhancement applies to. Printer type - [MINI]

[zoltan-l]

Hi @DanidCH , thanks for your input, we will look at it

[TerTerro]

Agree on this. I always do, load PLA after ASA, but specify I'm loading ASA, purging 3-5 times and then unload and load again same PLA with PLA temps. Would be great option to have, switching to purge at old filament temps.

[jwidess]

Couldn't agree more on this, would love to see this as a feature. Often when I'm printing PC and go to print PLA I will try to do it as quickly as possible to keep the nozzle temp high to get all the PC out of the hotend.

[SnickCH]

+1

[kozross]

It's been over 18 months since this was reported, and I just had a more current issue closed in favour of this one, along with two others in the last four months. Is there any ETA on this being dealt with? Given that we can't manually load filament into the MINI+ without going through this system, and I personally have clogged my printer a few times this way already, it'd be good to have a roadmap, or even an explicit statement that we shouldn't wait for a solution.

[Prusa-Support]

I'm sorry, no estimated time available and I'm not sure this is in the current development plans. The issue will stay open.

Michele Moramarco Prusa Research

[Tupson444]

One of the basic advices for 3D printing is e.g. "when changing between PLA and ABS, set the temperature for ABS". This is an obvious overlook that should be fixed.

[mjablon1]

@Prusa-Support can you try again putting this into the development roadmap, please?

[bkerler]

I wrote a PR #3681 for it. Only tested so far in the simulator, but it should work fine :)

[Prusa-Support]

I'll try my best to escalate. 🙂 During the last year, our developers worked tirelessly and released more than a dozen firmware stable releases in this repository, and there is still a lot to do.

This issue will remain open as inspiration for future development but opening a Pull Request would probably be more effective. Thanks for it.

Michele Moramarco Prusa Research

[Zappes]

@Prusa-Support Please try to actually read the comments before answering in your usual way... @bkerler HAS created a pull request and actually linked to it.

[Prusa-Support]

@Prusa-Support Please try to actually read the comments before answering in your usual way... @bkerler HAS created a pull request and actually linked to it.

I even thanked for it.

.

As highlighted by our collaborator in the MK3 FW repository - https://github.com/prusa3d/Prusa-Firmware/issues/3114#issuecomment-1990881827 - switching between vastly different materials could actually be troublesome if neither is correctly removed first. For example, PLA will probably carbonize and harden in no time if un/loaded at PC temperature. A feature that automatically picks the higher temperature has to be carefully considered and thoroughly tested.

In most cases, a cold pull between material changes is very recommended.

Michele Moramarco Prusa Research

[KrisasMan]

I ended up in the wrong repository for my own version of this request. (https://github.com/prusa3d/Prusa-Firmware/issues/4675)

My experience has been that if you keep PLA flowing the entire time it won't carbonize. The key would be to have the printer start at the higher temp and then, after sufficient purging, drop the temp and continue purging to drop the temp to PLA temp.

[github-actions[bot]]

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]]

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