gCode not sliced correctly for filament presets for MMU2S
Have had this issue for awhile but becoming more urgent to fix. This is for a MK3S+ with MMU2S, current PrusaSlicer, current firmware. If we have a model with 2 preset filaments (say Atomic and Hatchbox) as in the attached example, and if the different filaments are both evident on the first few layers, and then after that are just one or the other on a particular layer, the temperatures are not being applied correctly. This doesn't matter tremendously if the PLA filaments are close in temp, but does matter if one is regular PLA and the other is PLA+ or Silk PLA etc.
In the example Atomic PLA is 220/215 and Hatchbox is 215/210. I have a sample part that has a blue circle for 2 layers (Atomic) inside a green square (Hatchbox) from 1 to 2mm I use Mod Mesh to make those layers Blue. So the print proceeds as follows:
- Atomic layer 1 prints correctly at 220.
- Hatchbox layer 1 then prints correctly at 215.
- Hatchbox layer 2 then prints correctly at 210
- Atomic layer 2, however, prints INCORRECTLY at 210
- Hatchbox then prints solid squares up to the color band correctly at 210
- Atomic blue color band then prints CORRECTLY at 215
- Hatchbox then prints correctly at 210 for the remainder of the print
If I change around the order I can have instances where the first solid section up to the color band is all at the wrong temp.
Again not a huge issue if close but if have a Silk PLA that will not load and unload at 210 then becomes a problem.
Attaching pics and hopefully the zipped project file. Any ideas are appreciated.
A couple of other items:
- was going to mention the load/unload temp issue but just saw post by @anachronist that we are very excited to see if it works.
- As seen in the pics the temp legend still doesn't work for us (can't recall why that is)
- Currently to solve this issue we have to manually change temps but even that isn't great as the temp will then be over-ridden by the slicer when get to different layers. Not sure if there is a way to make manual temp changes "Stick".
Thanks for any input
RE: gCode not sliced correctly for filament presets for MMU2S
2nd layer temp
RE: gCode not sliced correctly for filament presets for MMU2S
Project file
RE: gCode not sliced correctly for filament presets for MMU2S
I had really hoped someone had run into and solved this issue, or could point out mistakes we may have made.
It looks like a bug to me, but I realize we may be doing something wrong.
Is this wrong sub-forum? Should it be put to devs on github? Any thoughts?
RE: gCode not sliced correctly for filament presets for MMU2S
So looking at the gCode it is not that it set the temp wrong for the 2nd layer Atomic filament (blue), it is that there is no M104 at all with the filament change, so it just keeps using M104 S210 from the Hatchbox (green) that already printed on that layer.
PrusaSlicer is not using M104 when it should (still completely open to hearing we are the ones messing this up by missing a toggle or something somewhere 🙂 ).
RE: gCode not sliced correctly for filament presets for MMU2S
This is the gCode where M104 S215 does not show up on layer 2 when it should
RE: gCode not sliced correctly for filament presets for MMU2S
Hey Rick,
I've been trying to figure things out with G-code myself and I definitely do not know much about it but I noticed a comment on line 429 of the code. It says "; stop printing object Temperature Issues id:0 copy 0" At what I think is a similar point in my code I got "; stop printing object Vent Assy C.stl id:0 copy 0" I don't know if that means anything or not. I did a search in my code and the phrase "Temperature Issues" did not show up.
I do know that it is possible to have different temperatures for different filaments because I have had that happen in prints where I id not set things up the way I wanted.