Please help diagnose a print failure


#1

I just had a 36-hour print fail at the 67% mark. It printed all day yesterday, but when I checked on it this morning, I found OctoPrint reporting an Operational status and a communication error.

Checking the log, I see this:

2018-04-03 12:16:12,970 - octoprint.util.comm - ERROR - Unexpected error while writing to serial port

Traceback (most recent call last):

  File "/home/pi/Volume/venv/local/lib/python2.7/site-packages/OctoPrint-1.3.6-py2.7.egg/octoprint/util/comm.py", line 2499, in _do_send_without_checksum

    result = self._serial.write(to_send)

  File "/home/pi/Volume/venv/local/lib/python2.7/site-packages/octoprint_GPX/gpxprinter.py", line 131, in write

    self._append(gpx.write("%s" % data))

IOError: Generic Packet error

2018-04-03 12:16:13,046 - octoprint.filemanager.analysis - INFO - Starting analysis of local:Observer_Housing_Base_v5.gcode

2018-04-03 12:16:13,059 - octoprint.plugin - ERROR - Error while calling plugin printhistory

Traceback (most recent call last):

  File "/home/pi/Volume/venv/local/lib/python2.7/site-packages/OctoPrint-1.3.6-py2.7.egg/octoprint/plugin/__init__.py", line 225, in call_plugin

    result = getattr(plugin, method)(*args, **kwargs)

  File "/home/pi/Volume/venv/local/lib/python2.7/site-packages/octoprint_printhistory/__init__.py", line 146, in on_event

    return eventHandler.eventHandler(self, event, payload)

  File "/home/pi/Volume/venv/local/lib/python2.7/site-packages/octoprint_printhistory/eventHandler.py", line 38, in eventHandler

    fileName = payload["name"]

KeyError: 'name'

2018-04-03 12:16:13,063 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/Volume/venv/bin/python -m octoprint analysis gcode --speed-x=2500 --speed-y=2500 --max-t=10 --throttle=0.0 --throttle-lines=100 --offset 0.0 0.0 /home/pi/.octoprint/uploads/Observer_Housing_Base_v5.gcode

2018-04-03 12:34:04,672 - octoprint.filemanager.analysis - INFO - Analysis of entry local:Observer_Housing_Base_v5.gcode finished, needed 1071.63s

It looks like a generic communication error, which I suppose could be attributed to a failure of the UART on this new Raspberry Pi 3B+ that I just swapped in last week. But if that's the case, then preventive measures are probably limited - maybe only to replacing the RPi with a new device.

Any other ideas?