printing multi colors manually
How do I print multi colors manually? (without an MMU)
I want to print the Core One lid in this model. I am using PETG. I have white, orange, black all PETG.
https://www.printables.com/model/545197-prusa-tool-box-core-one-core-one-l-mk4s-mk4-xl-mk3
Prusa Core One
RE: printing multi colors manually
In Printables pick the 3MF file for the box lid an slice it which will send it to PrusaSlicer
Next change the first extruder filament to PETG and transfer the settings
Then select the same PETG for the other two
RE: printing multi colors manually
I did exactly this but the display on C1 stated that the wrong filament was loaded.
In Printables pick the 3MF file for the box lid an slice it which will send it to PrusaSlicer
Next change the first extruder filament to PETG and transfer the settings
Then select the same PETG for the other two
Prusa Core One
RE:
I did exactly this but the display on C1 stated that the wrong filament was loaded.
That is completely normal. Just ignore it and hit "OK" on the screen (if I remember that right) to proceed.
RE: printing multi colors manually
I did exactly this but the display on C1 stated that the wrong filament was loaded.
That is completely normal. Just ignore it and hit "OK" on the screen (if I remember that right) to proceed.
Any way to get rid of the error completely? I mean, what is it in the gcode that triggers the warning?
I use a similar approach for one of my custom parts and I have to dismiss this warning every time I print the part, its annoying AF as often I'll send it to the printer, wander off and do something else and come back an hour later to find the print obviously hasn't even started.
RE:
I did exactly this but the display on C1 stated that the wrong filament was loaded.
That is completely normal. Just ignore it and hit "OK" on the screen (if I remember that right) to proceed.
Any way to get rid of the error completely? I mean, what is it in the gcode that triggers the warning?
I use a similar approach for one of my custom parts and I have to dismiss this warning every time I print the part, its annoying AF as often I'll send it to the printer, wander off and do something else and come back an hour later to find the print obviously hasn't even started.
I think it's a bug. I haven't done many manual multi-color prints since it's a royal PITA. So I haven't spent much time to investigate. It's only the initial filament load that triggers this. Could probably write a python script to massage the g-code to make it go away but it's not worth it in my opinion.
RE:
I did exactly this but the display on C1 stated that the wrong filament was loaded.
That is completely normal. Just ignore it and hit "OK" on the screen (if I remember that right) to proceed.
Any way to get rid of the error completely? I mean, what is it in the gcode that triggers the warning?
I use a similar approach for one of my custom parts and I have to dismiss this warning every time I print the part, its annoying AF as often I'll send it to the printer, wander off and do something else and come back an hour later to find the print obviously hasn't even started.I think it's a bug. I haven't done many manual multi-color prints since it's a royal PITA. So I haven't spent much time to investigate. It's only the initial filament load that triggers this. Could probably write a python script to massage the g-code to make it go away but it's not worth it in my opinion.
Yeah , this part uses a PP script anyway but for the life of me I cant see what in the gcode triggers it. Most of the gcode checks can be disabled on the printer itself, but I dont really want to do that, they can be useful for wrong nozzle type etc.
I think you're right in that it's a bug, as I'm not trying to use a filament I havent got loaded etc.
It's not really a bug, it's more of a sanity check: If you have, say, ASA loaded but start a print sliced for PETG then it's likely to fail and the printer is warning you - you can override.
You have the option to tell the printer, at load time, that you have a very different filament and you can set the loading parameters under 'Custom' - which allows for all sorts of exotic experiments.
The comparison is between the filament type selected at load time and the filament specified when slicing - the slicer supplies the type specified in the filament preset(s) [ Filaments > Advanced > Filament type ]. If you have an exotic filament declare it as the most similar one of the supplied types, this is only for loading, or if none is similar you will have to use Custom(above).
I have a filament that is definitely not PLA but as it requires similar loading procedures I have written a preset that declares it as PLA - but within the rest of the preset the other parameters are tailored and will be used by the g-code - I tell the printer to load it as PLA and all is well.
Cheerio,
RE: printing multi colors manually
Another reference for manual MMU is a remix that I recently posted for printing the back plastic covers of the C1+. I did this on my MK4S right before tearing it down for my conversion to the C1OG with C1+ upgrade kit. The "basic gist" section of my remix goes through how I would set up a Manual MMU print on any printer in PrusaSlicer. Others have a slightly different Manual MMU settings setup that I do, but this is how I developed doing it for myself and it works well for me. I usually print through OctoPi and Prusa printers using the xBuddy board don't show M117 messages on the screen. So I use the OctoPrint M117PopUp plugin so I can see the M117 messages on my OctoPi interface on a computer next to my printer (though I don't mention this detail in my remix).
https://www.printables.com/model/1554234-core-one-power-and-nfc-cover-color-manual-mmu
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
RE:
I did exactly this but the display on C1 stated that the wrong filament was loaded.
When transferring the setting from the original PLA over to PETG, did you accidentally also transfer the filament type and print temperatures over? (Your error seems to indicate this.) I think @hyiger only meant for you to transfer the shown settings (not all) over. Otherwise you'll accidentally be trying to print PETG at PLA temperatures, a guaranteed print fail.
Though, I'd argue that you also don't need to transfer the Print Dependencies section over.
See my (limited) designs on:
Printables - https://www.printables.com/@Sembazuru
Thingiverse - https://www.thingiverse.com/Sembazuru/designs
RE: printing multi colors manually
I did exactly this but the display on C1 stated that the wrong filament was loaded.
When transferring the setting from the original PLA over to PETG, did you accidentally also transfer the filament type and print temperatures over? (Your error seems to indicate this.) I think @hyiger only meant for you to transfer the shown settings (not all) over. Otherwise you'll accidentally be trying to print PETG at PLA temperatures, a guaranteed print fail.
Though, I'd argue that you also don't need to transfer the Print Dependencies section over.
Even when I do a hand-rolled multi-color print, i.e. set up a multi material single extruder from scratch I still get a filament mismatch warning even though PETG is loaded and PETG is configured.
Interesting. I don't have a Core one to try it on but my old Mk3 did, and still does, handle it seamlessly and the situation doesn't arise with the XL.
Is there any spacing or formatting in your filament type declaration that might cause mismatching? - clutching at straws I know...
Cheerio,
RE: printing multi colors manually
Interesting. I don't have a Core one to try it on but my old Mk3 did, and still does, handle it seamlessly and the situation doesn't arise with the XL.
Is there any spacing or formatting in your filament type declaration that might cause mismatching? - clutching at straws I know...
Cheerio,
Very far away from my printer at the moment but it would have just been the filament selection from the dropdown. Nothing exotic.
RE: printing multi colors manually
It's not really a bug, it's more of a sanity check: If you have, say, ASA loaded but start a print sliced for PETG then it's likely to fail and the printer is warning you - you can override.
Surely it's a bug if the printer is saying wrong filament type, when the only filament defined in the slicer/gcode is currently loaded into the printer?