I had a really great print going and when I came back to check on it a few hours later, the printer was stopped and Octoprint was at the "Connect" prompt. I looked at the log and didn't see anything specific as to what happened and what to investigate further
Here's the log
Help! And thanks!
(Printer is a FolgerTech FT-5 and using a Raspberry Pi 3, current on all the updates)
2019-09-30 01:30:07,561 - Recv: ok
2019-09-30 01:30:07,566 - Send: N40869 G1 X196.432 Y116.681 E83.5919*108
2019-09-30 01:30:07,752 - Recv: T:204.86 /205.00 B:59.99 /60.00 @:70 B@:53
2019-09-30 01:30:08,074 - Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'device reports readiness to read but returned no data (device disconnected or multiple access on port?)' @ comm.py:_readline:2739
2019-09-30 01:30:08,077 - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2019-09-30 01:30:08,096 - 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:2739)"
2019-09-30 01:30:08,120 - Connection closed, closing down monitor
Is your power supply sufficient? A weak or unstable power supply can cause all kinds of problems
Did you test other usb cables? A bad cable can be responsible for all kinds of print errors.
Do you have other electrical devices nearby? My ender 3 did the same thing when I turned off the light (fluorescent tubes). That problem disappeared after I switched from stock fw to my own marin.
The power supply doesn’t seem to be the culprit. I have the same make/model/brand Raspberry Pi 3/power supply bundles I bought last year. Other Octoprints work fine.
The USB cord has worked fine for other tasks, like firmware updates via Arduino and calibration via Simplify3D.
Electrical...not really. The cable is pretty much a direct shot from the mounted raspberry pi to the FT-5 USB port.
I was hoping the logging might reveal something. Or perhaps reimage the SD card?