Constant Request To Change Filament
So I'm a bit rusty, but just upgraded to latest firmware. I have a i3 MK2 upgraded to MK2.5 upgraded to 2.5S with MMU 2 but never have used the MMU2.
So I first loaded the MK2.5S firmware, then the MK2.5S with MMU2 firmware, same problem.
So have slicer set to "Original Prusa i3 MK2.5S MMU2S Single."
Anyway, first when I print I get a "G-Code Sliced For A Different Printer" So I say Print Anyway.
So it starts to print, then stops and tells me to "Unload the Filament" I have no other choice. Then I reload the same filament. Then this repeats OVER and OVER. Unload the filament, then reload, OVER and OVER. I tried with filament sensor OFF and filament sensor ON. No difference.
How do I fix this? Help.
Best Answer by Chicago Keri:
To me this sounds like Slicr configuration, not the printer.
Constant requests for "change filament" sounds like the gcode is asking for a tool change, as if one is printing a multi-color thing.
Did you add any custom gcode with M600 commands?
How many extruders are set in PrusaSlicr? If printing with one material, I would set it to 1 extruder.
Good Luck!
RE: Constant Request To Change Filament
Set slicer to "Original Prusa i3 MK2.5S" and I no longer get the G-Code mismatch, but printer STILL constantly asks me to change filament. There doesn't even seem to be a way to say NO.
RE: Constant Request To Change Filament
To me this sounds like Slicr configuration, not the printer.
Constant requests for "change filament" sounds like the gcode is asking for a tool change, as if one is printing a multi-color thing.
Did you add any custom gcode with M600 commands?
How many extruders are set in PrusaSlicr? If printing with one material, I would set it to 1 extruder.
Good Luck!
¡no entiendo Español!
Nein! Nicht Versteh!
Я немного говорю по-руÑÑки но не очень хорошо, и...
I'm not very good at English either! Maybe someday I'll find a language I'm good at?
RE: Constant Request To Change Filament
You were correct. Thanks. I looked through all the Slicer settings, but couldn't find anything unusual. I don't see a way to reset everything to default, so I completely removed it and reinstalled. I have to say, I'm surprised, but it is working. Thanks.