You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I run your firmware on 20 machines and today this happened the 4th time on different machines, so this cannot be random: While printing a single color print, after 3-4 hours the selector simply tries to move while printing. No check for loaded filament, nothing. It simply moves and shears the filament, so that the printer does not extrude any more. This happens since some weeks, perhaps already in 4.0.1. I could not recognize some ideas what triggers this, but ain't there a query if the filament is loaded through FINDA?
It's a pity for the failed prints, often they are 12h and longer in a production environment.
To Reproduce
Steps to reproduce the behavior:
Print some single color prints on mmu
The text was updated successfully, but these errors were encountered:
I am unable to reproduce this issue @eurohell.
unless your mmu is going into an unknown state (hanging/crashing) then there is always checks done to ensure the selector isn’t moved while loaded.
Feel free to investigate further.
TZB-MMU2S Release Version
4.0.2
Describe the bug
I run your firmware on 20 machines and today this happened the 4th time on different machines, so this cannot be random: While printing a single color print, after 3-4 hours the selector simply tries to move while printing. No check for loaded filament, nothing. It simply moves and shears the filament, so that the printer does not extrude any more. This happens since some weeks, perhaps already in 4.0.1. I could not recognize some ideas what triggers this, but ain't there a query if the filament is loaded through FINDA?
It's a pity for the failed prints, often they are 12h and longer in a production environment.
To Reproduce
Steps to reproduce the behavior:
Print some single color prints on mmu
The text was updated successfully, but these errors were encountered: