New Slicer problem with mmu2s
I just installed the new slicer and I found a huge issue on slicing multi material objects.
I sliced with 3 different colors (1 orange - 2 white and - 3 black) and when I started printing it uses only the first and the third (1 orange and - 3 black) and exchanged the second one with the third.
Any solutions?
RE: New Slicer problem with mmu2s
Not to knock you, but are you sure the correct extruder is selected in the slicer?
Does the preview show it using the correct extruder or is it too incorrect?
RE: New Slicer problem with mmu2s
On the preview I see everything ok, that is why it problems me
RE: New Slicer problem with mmu2s
a print screen of why I want to print
RE: New Slicer problem with mmu2s
a picture of what i get when I start this printing
RE: New Slicer problem with mmu2s
I guess next I'd check the gcode to see if there are T1 (filament 2 (T0 would be 1 and T2 would be 3)) commands in it. If there are, then the issue is with the printer/MMU. If they are not there, then the issue is indeed with the slicer.
For what it's worth I sliced a 5 color print with the release version of PrusaSlicer last week and the printer used the correct filaments at the correct times.
RE: New Slicer problem with mmu2s
I checked the gcode and indeed there are. what can I check next. Before the upgrade of the drivers I was printing with no color issues
RE: New Slicer problem with mmu2s
So T1 shows up (presumably the correct number of times), but it doesn't use that selector? That suggests that the printer/MMU is at fault rather than the slicer.
Try writing a little gcode file your self that is nothing but T0, T1, T2, T3, and T4 commands ordered randomly (or you can use the printer's serial interface to manually enter them) and see if the selector moves as desired (make sure you've unloaded it first).
That may not be a good test case though as I haven't looked into the details of a filament change to see what other commands may be appropriate and could be the source of the issue. Those T commands, however, are telling the selector which filament path to move to so that seems like the most logical starting point.
You might start by simply resetting your MMU (little button hidden next to the USB port). Plenty of odd behavior seems to get corrected by this and you can even do it mid print while the printer is paused (say with a failed (un)load that won't cooperate otherwise).
RE: New Slicer problem with mmu2s
Since I'm not familiar with gcode writting I tried the reset which didn't solve the problem. I then re-flashed the latest firmwares on both printer/mmu and the problem solved
Thanks for the suggestions and the help in general
RE: New Slicer problem with mmu2s
Glad you got it fixed. That's the important part.