Color change not working?
I'm trying to insert a color change for one of my MMU prints. I was expecting the slicer to insert a M600, but it looks like it's inserting a M601 pause instead. When the print gets to the layer, the printer just pauses and doesn't initiate any filament swap. What am I doing wrong?
RE:
Update: It seems that the slicer will correctly insert a M600 if there is no multmaterial painting. However, for multimaterial painted objects, like in my example, it inserts a M601 pause instead. That makes no sense to me.
https://help.prusa3d.com/article/colorprint-with-the-mmu_124861
Scenario 3 suggests that this is not the correct behavior.
RE: Color change not working?
Joan would be the one to ask for certain but I don't think you can. With a MMU its extruder change and colour change doesnt work.
when I select MMU as a printer option and add a colour change to an object the icon on the layer slider changes to a ! and the tooltip for it says this code wont be processed during gcode generation.
If you want to change colour at a specific layer then you need to add a height range modifier and then select the extruder you want to use for that height range.
RE: Color change not working?
Prusa's only document suggests that this is possible ( https://help.prusa3d.com/article/colorprint-with-the-mmu_124861 - Scenario 3). I did get the same error you got "gcode wont be processed".. But that's because I selected an extruder that would be no longer used to apply the color change, which makes sense. But if you were you paint two objects at different heights the same color, then apply color change to that extruder in between the two objects, you will in fact get the color change, at least in the slicer. What I'm experiencing is that the generated gcode doesn't match what the slicer is showing.
RE: Color change not working?
I believe you are misinterpreting scenario 3. What you are trying to do falls under that big red prohibited notice.
When it says colour change it does not mean filament change, ie M600. It means you can redefine an area that already has a extruder/colour assigned to it. So on your model you could in theory change the pink coloured areas to be orange. Ie a colour change. Or you could paint an area and assign it a different extruder. Then the MMU process takes care of it. You can not mix M600 with an MMU. Unless its in single mode and then its not really acting as an MMU is it.
I already mentioned in my previous post the method you have to use to get the equivalent of a M600. You have to define the area using a modifier. Either a mesh modifier or a layer height modifier which more closely resembles the actions of a M600 change filament at layer xx. Or paint it. Basically anything that lets you assign an extruder to it.
RE:
That's not what I'm doing.
- I imported a raw STL
- I painted it with 5 colors using multimaterial painter.
- I sliced
- I set the height slider to z23.6
- I insert color change for extruder 3 and set color to white. It used to be beige, but is no longer needed past 23.6.
- Slice again.
The sliced preview looks correct. However, the generated gcode doesn't insert M600 - color change, it inserts M601 - pause. I'm not switching printer profiles or changing any extruder assignments.
RE:
I just talked to support and they think it's a bug.
RE: Color change not working?
I'll say again, I don't think that's allowed. Which the software operation would agree with. With a MMU you basically don't use the slider to add colour changes. At all. From your description you are using that scenario 3 from the link you posted and as soon as you insert the colour change using the slider then that's scenario 2, so mixed and it wont allow it.
If you think its a bug then please go to the Prusa Slicer github and add a new one. https://github.com/prusa3d/PrusaSlicer/issues
You will need to attach your project file to demonstrate exactly the issue and a step by step like you did above. If you do want to open an issue please do a thourough search of both open and closed existing issues to see if its been reported before. Given there are over 5000 open issues and over 8000 closed ones its a busy github.
Without your actual project to examine its hard to tell what may be happening. For example you may be running into this issue https://github.com/prusa3d/PrusaSlicer/issues/12639
There are already several open for example this one https://github.com/prusa3d/PrusaSlicer/issues/14379 which sounds similar for the problem.