Based on your log, your printer stopped responding to commands sent by OctoPrint at 23:04
2018-07-19 23:04:42,929 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-07-19 23:05:12,963 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-07-19 23:05:42,996 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-07-19 23:06:13,019 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-07-19 23:06:43,067 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2018-07-19 23:07:13,110 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2018-07-19 23:07:13,177 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: Too many consecutive timeouts, printer still connected and alive?)"
Subsequent attempts to reconnect to it this morning also didn't work out:
2018-07-20 05:39:51,381 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2018-07-20 05:39:51,417 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
[...]
2018-07-20 05:40:26,536 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Offline"
[...]
2018-07-20 05:40:49,509 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2018-07-20 05:40:49,541 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2018-07-20 05:40:49,595 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
[...]
2018-07-20 05:41:24,653 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Offline"
[...]
2018-07-20 05:41:53,891 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial port"
2018-07-20 05:41:53,921 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial port" to "Connecting"
2018-07-20 05:41:53,969 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
[...]
2018-07-20 05:42:29,083 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Offline"
The log hints at the printer also not responding to the handshake M110
that OctoPrint sends out there.
So, based on just this log and without any access to the terminal output or a serial.log
, it looks like for some reason the printer started giving OctoPrint the silent treatment, which of course made it impossible to run a print job. I note that you also have Octolapse installed and active based on the two present logs of resend requests which both happened exactly after M400
+ M114
probably sent by Octolapse:
2018-07-19 22:15:50,673 - octoprint.util.comm - INFO - Got a resend request from the printer: requested line = 83006, current line = 83008
| Last lines in terminal:
| Send: N82997 G1 Z7.990 F1002*19
| Recv: ok
| Send: N82998 G1 E0.2000 F4200*51
| Recv: ok
| Send: N82999 G92 E0*68
| Recv: ok
| Recv: ok
| Send: N83000 M83*19
| Recv: ok
| Send: N83001 G1 E-6.50000 F5100*37
| Send: N83002 G91*24
| Send: N83003 G1 Z0.200 F1000*17
| Send: N83004 G90*31
| Send: N83005 G1 X150.000 Y150.000 F3600*68
| Send: N83006 M400*42
| Send: N83007 M114*43
| Recv: ok
| Recv: ok
| Recv: Error:checksum mismatch, Last Line: 83005
| Recv: Resend: 83006
I'm not aware of any printer timeout issues between 1.3.8 and Octolapse, but maybe @FormerLurker has some more insight there than me.
Finally:
Not really. You could try measuring the z-height, manually adjusting your GCODE file so that it starts at the point it most likely stopped and then run that. But if that will work out depends on a ton of factors and is somewhat unlikely.