-
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
[ENHANCEMENT] Confirm filament type on automatic load, even if at previously set temp. #3114
Comments
I'd consider this a bug rather than an enhancement... |
@hajosc For clarification, do you mean that my proposed change to confirm filament temp on load when currently preheated would be considered buggy behavior if implemented, or that the current behavior of not confirming temps when loading is? |
Sorry for not being clear -- I consider it a bug that the printer does not confirm temperature when loading a new filament. If you switch from "coldest" to "hottest" filament the loading process might very well fail. |
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. |
While the issue is stale, it is still open for consideration for future firmware improvement. |
Also just noticed that bug. How to reproduce:
It should ask what filament type is being loaded and heat to proper temperature. Tested on MK3S+ with 3.13.2. |
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. |
Hello! Please don't automatically close this issue, actions bot! It may be old, but it's still relevant. |
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. |
Thanks for the idea and sorry for answering so late. Some (I would say most) users may find it annoying to be asked each time which filament type they want to load as they print mostly the same type of material. So it will not be easy to satisfy everyone. Workflow idea for you:
At this moment you tell the printer that the active filament is PLA to be unloaded
As most users change the same type of filament the printer at the moment assumes that you have PLA selected. Keep also in mind that the un-/ load procedures are used during filament runouts, filament changes and MMU.
It is NOT a bug as it works for the most used scenario, where users print mostly with the same material. Changing materials needs extra attention in my opinion. Here two examples with most extreme temperature differences. Change from PLA to PC:
Change from PC to PLA:
As this an edge case which most users may not use it we will not implement it. The workflow above should work for everyone just one additional manual step. If a volunteer is willing to work on it and provide a PR we may consider to review this PR. |
I meantime I've switched to MK3.5 (so Prusa-Firmware-Buddy) and it
No idea if the same procedure is used everywhere (mmu etc) like in 8bit firmware though. Also I'm ok with "wontfix" at this stage of 8bit fw life cycle coming (sooner or later) to the end. |
@arekm Thanks for the feedback. The 32-bit is different and has way more resources to do things and there might be a different approach to this. I think that especially switching from high temp material to lower temp needs several manual steps to prevent clogs. |
Enter what type of printer or upgrade the enhancement applies to.
Printer type - MK3S
Is your enhancement related to a problem? Please describe.
When swapping filament with Autoload enabled, I will often forget that the unload temps are currently active and the printer will automatically load filament without checking for filament type to change temps.
Describe the solution you'd like
Upon loading filament, I'd like a way to have the printer confirm the filament type that I'm loading, even if the printer is currently at-temp for, for example, PLA from a recent unload.
A preferred sequence of user steps would be as follows:
The text was updated successfully, but these errors were encountered: