Print stop in the middle with Pi Zero W

What is the problem?
I use pi zero w and found print has been stopped a few times in the middle of the print.

What did you already try to solve it?
I do not really know where to start, except for checking the logger. But I did not find any clue.

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

2020-01-01 06:15:46,846 - octoprint.util.comm - ERROR - Unexpected error while reading from serial port
Traceback (most recent call last):
  File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/util/comm.py", line 2793, in _readline
    ret = self._serial.readline()
  File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/util/comm.py", line 4932, in readline
    c = self.read(1)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/serial/serialposix.py", line 501, in read
    'device reports readiness to read but returned no data '
SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2020-01-01 06:15:46,886 - octoprint.util.comm - ERROR - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2020-01-01 06:15:46,997 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793)"
2020-01-01 06:15:48,636 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': 'local', 'reason': 'error', 'commerror_text': "SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793", 'file': '140e2d0f94e56c7d24d6ed946a74e6ee5397cd8f', 'elapsed': 5929}
2020-01-01 06:21:44,575 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-01-01 06:22:14,822 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 98133}
2020-01-01 06:36:44,585 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-01-01 06:37:14,613 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 99033}
2020-01-01 06:51:44,595 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2020-01-01 06:52:14,646 - octoprint.plugins.tracking - INFO - Sent tracking event ping, payload: {'octoprint_uptime': 99933}
2020-01-01 07:06:44,604 - octoprint.server.heartbeat - INFO - Server heartbeat <3
Traceback (most recent call last):
  File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/util/comm.py", line 2793, in _readline
    ret = self._serial.readline()
  File "/home/pi/oprint/local/lib/python2.7/site-packages/octoprint/util/comm.py", line 4932, in readline
    c = self.read(1)
  File "/home/pi/oprint/local/lib/python2.7/site-packages/serial/serialposix.py", line 501, in read
    'device reports readiness to read but returned no data '
SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
2020-01-01 06:15:46,886 - octoprint.util.comm - ERROR - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2020-01-01 06:15:46,997 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline (Error: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793)"
2020-01-01 06:15:48,636 - octoprint.plugins.tracking - INFO - Sent tracking event print_failed, payload: {'origin': 'local', 'reason': 'error', 'commerror_text': "SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2793", 'file': '140e2d0f94e56c7d24d6ed946a74e6ee5397cd8f', 'elapsed': 5929}

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible)
octopi 0.17.
octoprint 1.3.12

It could be a number of things:

  • your serial cable should have internal metallic shielding or a ferrite core
  • your Pi should have enough power so that it's not running in an under-voltage situation (you'd see this in the status bar at the top of OctoPrint with a lightning bolt icon)
  • the Pi Zero is under-powered and not recommended for the average OctoPrint installation (try Pi 3B or better)

You didn't mention which printer you have. Delta style printers involve more last-minute calculations which can lead to blobbing due to small pauses like you've described (often associated with 8-bit controllers). You didn't mention which slicer you're using. Too-small segments for curves can also result in overrunning your firmware's receive buffer. Many people solve this problem by reconfiguring their Marlin firmware to increase the receive buffer.

1 Like

thank you and sorry for the late reply. I have 12 printers powered by pi zero. Only one has this problem. I sawp the pi zero, cables etc. It is still paused during the print. I suspect it might be printer firmware issue. By the way, I am using ender3 with simplify3d for slicing. Thanks