Printer reboots midway through print
I'm having an issue that I can't seem to find a solution for. After months of successful printing, my MK2 decided to stop/reboot at random times. I've tried new SD cards as well as printing from OctoPrint. I've also tried gcode files that have printed without issue before and I still see the random reboot.
Currently the printer is running 3.0.12 firmware which I upgraded to when the problem started. The odd thing is that the reboot is completely random. This past weekend I printed the parts to upgrade to a MK2s and didn't have an issue.
When logging with OctoPrint, just before the printer stops, I see a Recv: start come through after a 9 second pause. My first thought is to try a new controller but I thought I'd reach out to the forum to see if I'm missing something simple. Below is the tail end of the last unsuccessful print:
2017-10-12 00:32:04,345 - Recv: ok
2017-10-12 00:32:04,348 - Send: N63121 G1 X149.848 Y100.427 E0.01966*101
2017-10-12 00:32:04,534 - Recv: ok
2017-10-12 00:32:05,648 - Send: N63122 G1 X144.702 Y105.574 E0.24744*97
2017-10-12 00:32:14,681 - Recv: start
2017-10-12 00:32:14,683 - Printer sent 'start' while already operational. External reset? Resetting line numbers to be on the safe side
2017-10-12 00:32:14,689 - Recv: echo:echo: Last Updated: Jul 11 2017 16:36:40 | Author: (none, default config)
2017-10-12 00:32:14,692 - Recv: Compiled: Jul 11 2017
2017-10-12 00:32:14,695 - Recv: echo: Free Memory: 2370 PlannerBufferBytes: 1280
2017-10-12 00:32:14,698 - Recv: echo:Stored settings retrieved
2017-10-12 00:32:16,785 - Recv: echo:SD card ok
2017-10-12 00:33:16,840 - Communication timeout while printing, trying to trigger response from printer. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2017-10-12 00:33:16,845 - Send: N63123 M105*34
2017-10-12 00:33:16,859 - Recv: Error:Line Number is not Last Line Number+1, Last Line: 0
2017-10-12 00:33:16,861 - Recv: Resend: 1
2017-10-12 00:33:16,863 - Printer requested line 1 but no sufficient history is available, can't resend
2017-10-12 00:33:16,865 - Changing monitoring state from 'Printing' to 'Error: Printer requested line 1 but no sufficient history is available, can't resend'
Re: Printer reboots midway through print
Check your OctoPrint time out. I recall the default being very short (10 sec?), so any ColorPrint pauses or other things will cause it to restart.
That would not affect it unless there was a filament change or pause in the GCode, and would not affect it unless you are printing from OctoPrint.
Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage or loss. If you solve your problem, please post the solution…
Re: Printer reboots midway through print
2017-10-12 00:32:14,681 - Recv: start
This line from the log tells us that the printer has restarted itself, but it doesn't tell us why.
Can I suggest that you copy the same G-code file to the SD card and try printing it directly from the LCD menu, with OctoPrint disconnected.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: Printer reboots midway through print
Copying the G-Code to the SD was one of my first steps. I even went so far as to load up Slic3r on a different computer to make sure the g-code was good. Is there anyway to log what the controller is doing?
Re: Printer reboots midway through print
Is there anyway to log what the controller is doing?
Only by re-compiling the firmware with diagnostics turned on, and even then you may not get what you expect.
Does this happen at the same/similar/different parts of the print? (apologies if you have mentioned this previously..)
Possible causes: Slicer issue (very doubtful), short of a heater cable (or other component - I think I read that the thermistor short can cause issues) at a certain position, something else that I can't think of right now... You should also check inside the RAMBo case to ensure there are no metallic foreign objects in there and that ann the connectors are tight.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: Printer reboots midway through print
It happens at different layers of a print. I know because I have more of one particular failed part in a box than I care to admit 🙂
This past weekend I completed the MK2 -> MK2S upgrade so I had a chance to verify all the connections are tight and correct with the RAMBo board. The thermistor theory is intriguing. When I put the hotend into the new holder, I noticed the thermistor leads were looking a little crusty but not necessarily bad. I had a print go bad one night and woke up to a large blob of PLA wrapped around the hotend and PINDA probe but I've had many successful prints after that happened but before this issue.
Is there a part number or vendor I can source the correct thermistor from in the US?
Re: Printer reboots midway through print
Filastruder: https://www.filastruder.com/collections/e3d-spare-parts-and-accessories/products/v6-volcano-cartridge-style-upgrade select thermistor only, but you may also want the lead.
You should first check the thermistor cables at the hot end to ensure they maintain some separation - Kapton tape may assist.
Peter
Please note: I do not have any affiliation with Prusa Research. Any advices given are offered in good faith. It is your responsibility to ensure that by following my advice you do not suffer or cause injury, damage…
Re: Printer reboots midway through print
I was really hoping that replacing the hotend thermistor would do the trick but unfortunately it didn't. At this point I can only assume it's a power supply or a RAMBo issue. Any pointers on my next troubleshooting steps?