firmware or slicer? blade isn't used
I'm assuming that the blade should be used to cut strings and other debree that wasn't fully pulled back from the selector.
However, when the selector moves it's not moving in a way that would cut the filaments - it needs to take a step up/right to be able to cut the filament when moving back left (the blade cuts to the left).
Is this a Slic3r, MK3 or MMU2 firmware issue?
(Test case: The blade will NEVER cut filament number 5.)
Re: firmware or slicer? blade isn't used
What is even the intended use for the blade? Is this something that was lost from prototyping?
Re: firmware or slicer? blade isn't used
It would be great if the blade or cutter function as announced. Since day 1 I never seen any cut filament.
I wish there is option to cut on every filament change to prevent jamming.
Re: firmware or slicer? blade isn't used
It would be great if the blade or cutter function as announced. Since day 1 I never seen any cut filament.
I wish there is option to cut on every filament change to prevent jamming.
Better to solve the cause of the problem than use a work-around which would not be 100% reliable.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: firmware or slicer? blade isn't used
Better to solve the cause of the problem than use a work-around which would not be 100% reliable.
Are you saying the blade has no purpose?
It seems to me that it would serve the same purpose as good ramming, and a backup in case the ramming randomly generates a string. But then it should make sure it always cuts.
The blade seems to be in the wrong direction for an immediate cut?
Re: firmware or slicer? blade isn't used
Are you saying the blade has no purpose?
No, just saying that it's better to solve the cause of the stringing. If you cur the filament end straight with the blade, you can cause more problems.
I haven't had the blade in place since early on in the beta; the firmware does not currently implement end cutting with it. I have a feeling that the only reason it's there is for marketing purposes.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: firmware or slicer? blade isn't used
If it's not used the selector could be much better crafted. I might make a version for that.
Edit:
How about this filament path? It should give less amount of snags.