Nozzle prints outside of a model, then returns to printing.
Hi!
I seem to have an issue with my MK4 printer. During a print, sometimes the nozzle unexpectedly goes outside the model and prints outside of it. Then it returns to printing. Creating artifacts like that:
Printer: MK4, self-assebmly, Firmware 4.7.1
Slicer: PrusaSlicer 2.6.0
I am printing from LW-PLA single wall items (a plane from 3D LabPrint).
I tried reprinting the same GCode again and the same happened again. When looking at the GCode in Viewer it looks absolutely fine. There is no such a trajectory in the viewer.
There is the GCode: https://drive.google.com/file/d/1kUNalT0btmcMvT5Lz6t2nJ2Sl8gKjajH/view?usp=sharing
There is a video of that issue: https://photos.app.goo.gl/yJK76WHBrxUiuKX7A
Note that the printer seemed to be stuck and kept doing nothing for a while, then continued printing exhibiting the described issue.
How do you debug that issue? Has it happened to anyone else? Is that a known issue for MK4?
RE: Nozzle prints outside of a model, then returns to printing.
First thing I'd do is change the USB stick if you're printing with it. If it's reading badly it'll do things like this where one print move will zoom out in to space. While you're at it, power off the printer and make sure the cables connecting the front LCD screen are connected properly.
RE: Nozzle prints outside of a model, then returns to printing.
The USB stick might be a good point.
The one that shipped with the printer died after a few days for no reason so I replaced it with another one.
Is it common for a Prusa 3D printer to damage a USB stick? Can it indicate a deeper problem?
RE:
Additionally, are you sending the gcode via Prusa Connect/Link or by manually moving files onto the USB? If not manually, then this could be the g-code corruption issue.
RE: Nozzle prints outside of a model, then returns to printing.
I am transferring the gcode manually using USB stick from M2 Macbook.
I printed the item twice from the same gcode with the same bad result.
Then I took the USB back to my computer and investigated the gcode in a viewer. It looked normal. No issues were found in the viewer.