Any ideas what is causing this?
I have had some consistent trouble with a mk3s recently. A particular model is refusing to print fully. What happens is that at a certain layer height the filament appears to 'jam' and a little while later the printer nozzle stops (seemingly at 100%) but hovers in the middle right of the print bed and the display reads 'heating done' and stays on that setting.
The layer height appears consistent to within 3 mm. The same model (with the stl and gcode regenerated) has been tried more than a dozen times.
I also tried a benchy which _did_ print but with some awful artefacts. The heat bed was at 70C for this, which may explain some of the issues. Printed using Prusa PLA.
Pics and files attached. float_obj (v9.1). The first image is approximately what the failed print should look like
RE: Any ideas what is causing this?
Best way to debug these is to save the project file from Prusa Slicer. File > Save as.
That will save a .3mf file with the model and all your settings. While it could be the model it could also be the settings.
Also if you wouldn't mind including the output gcode in the archive too. Someone could take a look and see if there's anything out of the ordinary.
Your benchy issue looks like a problem with cooling, as well as a poor first layer adhesion at the front. Which given the amount of figer oils I can see on your bed isnt really a surprise.
Take that bed to the sink and give it a wash with plain dish soap and plenty of HOT water to rinse everything clean. It really does work better than anything else.
RE: Any ideas what is causing this?
I'm not sure what finger oils you're referring to but this last print was done just after a fairy-liquid bath. I wonder whether you are mistaking shadows and glares for oil-slicks? Anyway, another fairy bath can't hurt.
sorry for getting the format wrong. I should know better - more coffee needed Unfortunately the attached is a regenerated slice. I cannot be certain that it has produced the same gcode as before. But the process has been the same - set to standard prusa pla and 0.2 layer height. slice.
I'm trying the print again with a generic PETG as the one thing that I hadn't ruled out was bad filament. I've had quite a bit of trouble with Prusa filament in the past.
RE: Any ideas what is causing this?
@justin-adie
Possibly, looking at the 4th pic it looked like the dark patches behind the benchy are oily areas. If you are a fairy user you must be in the UK 🙂 Same here.
When I load in the .3mf project the Printer type is set to Mini. Looking at your pics that looks like a MK3 of some version, filament as type Generic PLA and Print settings as 0.2mm Speed @MK3. Which is weird if you are usong a mk3 and PETG filament.
RE: Any ideas what is causing this?
that is odd indeed. on my screen it is definitely a mk3S. Prusa Slicer did update itself a few days ago; which come to think of it is pretty much the time this stopped working.
the PETG print failed miserably after 3 layers. adhesion OK but filament 'spits' all over the place. I will try again with a clean bed and after extruding 30cm or so into the air.
I'm English but based in SW France. I do a car-run back to Blighty each year to stock up on fairy liquid and decent sausages...
RE: Any ideas what is causing this?
Justin I'm wondering if somethings got messed up in your profiles since the update. While a lot of the mini settings and MK3 settings are similar theres been changes for Linear Advance between the 2. If it is slicing with mini settings that could potentially cause lots of issues. Of course the profiles on my work machine could also be messed up 🙂
When i open the project and slice I'm definitely getting the temps for PLA at 210 degrees. So my version is slicing it with the profiles it thinks it should that match what the dropdowns are showing. I
If you slice and open up the gcode in a text editor and do a search for M104 you should be able to see what temps it is using. Or look for M900 which sets LA (linear advance) values.
RE: Any ideas what is causing this?
I've just opened a number of the failed gcode files and they all have the @MINI profiles. Perhaps the source of the problem, indeed! Time to reinstall Slicer and try again.
... a little while later this happened.
I do find these things frustrating; how the printer can start printing garbage after weeks of being in top form and literally nothing external intervening (although in this case there is the potential root cause of Prusa Slicer).