MK3S Restart itself instead of printing
Hello everybody,
i do own my mk3s for several months now and have never had any problems until now.
Today I wanted to print the Ceasar statue with a 0.25 nozzle and 0.05 layer height and my printer is on strike. The g-code file size is with 380mb the largest file yet but I havent read anything about a maximum file size so I dont know if this is the problem. Has anyone experienced something similar?
The process is that I heat everything up, insert my SD-Card (not the problem), select print from SD, select the file and the next thing that happens is a reboot of the printer. So the Display shows the " Original Prusa ..." logo and continues with the infoscreen.
Print settings are 20% infill gyroid, and everything else the standart mk3s 0.25 settings from Prusa slicer.
Sorry for my not so perfect english and thanks in advance
greetz from germany
MK3S - PrusaSlicer 2.3.1 - Slack Lack Enclosure
RE: MK3S Restart itself instead of printing
Hello everybody,
i do own my mk3s for several months now and have never had any problems until now.
Today I wanted to print the Ceasar statue with a 0.25 nozzle and 0.05 layer height and my printer is on strike. The g-code file size is with 380mb the largest file yet but I havent read anything about a maximum file size so I dont know if this is the problem. Has anyone experienced something similar?
The process is that I heat everything up, insert my SD-Card (not the problem), select print from SD, select the file and the next thing that happens is a reboot of the printer. So the Display shows the " Original Prusa ..." logo and continues with the infoscreen.
Print settings are 20% infill gyroid, and everything else the standart mk3s 0.25 settings from Prusa slicer.
Sorry for my not so perfect english and thanks in advance
greetz from germany
I would use an SD card with a maximum storage capacity of 32 GB and make sure that it is FAT32 formatted. I have never had problems printing gcode of this size. I think the max file size is 2 GB.
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.
RE: MK3S Restart itself instead of printing
Thanks for your answer karl-herbert, but it's not the SD card. #30+ hours print time no problems
I changed the infill from gyroid to grid, which decreased the file size to 180MB and now it works. 😶?
Same card, same settings but I'm not quite sure why. The gyroid infill obviously generates more lines of g-code but I don't think the printer runs all of them when starting the print nor that it should. In the end a cnc functions the same way by reading one line after another (duh)
So just a bug by the slicer or the maschine?
Would be interesting if I'm the first one experiencing this problem.
MK3S - PrusaSlicer 2.3.1 - Slack Lack Enclosure
RE: MK3S Restart itself instead of printing
It may not load them all at the same time but as the lines are so short its might hit some throughput limit on the 8 bit controller board when it comes to actually reading them from the sd card/parsing them or spooling them out from the internal buffer and then acting on them.
This also *could* theoretically be caused by a slower max read speed sd card too, especially if it was right on the edge of proper operation. There's just too many possible interacting factors to tell without some serious debugging with the machine and sd card, at the line level and being able to read buffers or getting something out of the serial log. Then again I've known using the serial logging on embedded devices to change the results as it adds an extra timing factor into the equation.
If you want very similar strength and speed from your infill to gyroid but using a LOT less segments give cubic a try.
Some people have had PS crash on them when slicing large models with gyroid due to memory problems but I don't recall seeing anyone have any printer issues with it.
RE: MK3S Restart itself instead of printing
It may not load them all at the same time but as the lines are so short its might hit some throughput limit on the 8 bit controller board when it comes to actually reading them from the sd card/parsing them or spooling them out from the internal buffer and then acting on them.
This also *could* theoretically be caused by a slower max read speed sd card too, especially if it was right on the edge of proper operation. There's just too many possible interacting factors to tell without some serious debugging with the machine and sd card, at the line level and being able to read buffers or getting something out of the serial log. Then again I've known using the serial logging on embedded devices to change the results as it adds an extra timing factor into the equation.
If you want very similar strength and speed from your infill to gyroid but using a LOT less segments give cubic a try.
Some people have had PS crash on them when slicing large models with gyroid due to memory problems but I don't recall seeing anyone have any printer issues with it.
Thank you for your answer, there are indeed too many factors to definitly say what causes the problem. When the print is finished I will give the maschine a closer look. I will try cubic for my next model, so far i works fine with grid.
And yes maybe this would function with a 32bit controller.
MK3S - PrusaSlicer 2.3.1 - Slack Lack Enclosure
RE: MK3S Restart itself instead of printing
@3dmark
Perhaps only briefly mentioned in passing:
I also had problems with my MK3 in an enclosure. In the middle of the printing process, the printer reset after I approached the printer and wanted to check the progress. After a longer test I could see that this was due to electrostatic charge on my part. Dry air increases the chance of electrical discharges.
Statt zu klagen, dass wir nicht alles haben, was wir wollen, sollten wir lieber dankbar sein, dass wir nicht alles bekommen, was wir verdienen.