Octoprint loses connection mid print

Get Help Networking
1

What is the problem?

I have been having issues with Longer LK5 Pro randomly disconnecting from Octoprint mid print. It had worked fine for about a year then sometime last year I started having issues with it disconnecting mid print for no reason. I ended up having another issue with the printer which resulted in me getting a new mother board, but the disconnecting issue still exists.

The error message I see on my computer screen in Octoprint is "Communication Error: There was a communication error while talking to your computer. Please consult the terminal output and octoprint.log for details.
Error: Too many consecutive timeouts, printer still connected and alive?"

I have two Ender 3 Pros and a Voxlab Aquila all with their own raspberry pi's working without issue. The longer LK5 is the only machine losing connection.

What did you already try to solve it?

-In addition to the new mother board on my LK5 Pro I have done the following:
-Replaced the USB cable (I've actually tried 3 different cables).
-I swapped Raspberry Pi devices between two printers so it is a completely different Pi 4B with the same issue.
-I tried re-imaging the SD card with Octoprint using a new SD card.
-I also tried replacing the power cable to my Raspberry Pi with a new one (this one is specifically for a Raspberry Pi).
-I tried a brand new Raspberry Pi to see if that would help and the issue happened again.
-If I run the printer from the SD card it runs fine.

Have you tried running in safe mode?

I have not tried that.

Did running in safe mode solve the problem?

Did not try

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog... no bundle, no support, unless the reason you couldn't retrieve the bundle is your network issues

WRITE HERE

Additional information about your setup

Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ... as much data as possible

WRITE HERE

2

Hello @MollyWaters !

Please attach the systeminfo bundle to your next post.

3

please see attached for the system bundle
octoprint-systeminfo-20240427040059.zip (3.8 MB)

4

The octoprint.log in the bundle was quite small, but luckily the serial logging was enabled and I found this:

2024-04-22 06:02:14,081 - 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.
2024-04-22 06:02:14,093 - Send: N121269 M105*24
2024-04-22 06:02:17,096 - 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.
2024-04-22 06:02:17,108 - Send: N121270 M105*16
2024-04-22 06:02:20,111 - 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.
2024-04-22 06:02:20,121 - Send: N121271 M105*17
2024-04-22 06:02:23,124 - 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.
2024-04-22 06:02:23,136 - Send: N121272 M105*18
2024-04-22 06:02:26,139 - 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.
2024-04-22 06:02:26,150 - Send: N121273 M105*19
2024-04-22 06:02:29,152 - No response from printer after 6 consecutive communication timeouts, considering it dead. Configure long running commands or increase communication timeout if that happens regularly on specific commands or long moves.
2024-04-22 06:02:29,178 - Changing monitoring state from "Printing" to "Offline after error"
2024-04-22 06:02:29,190 - Connection closed, closing down monitor
2024-04-22 15:34:18,076 - Changing monitoring state from "Offline" to "Opening serial connection"
2024-04-22 15:34:18,079 - Connecting to port /dev/ttyUSB0, baudrate 115200
2024-04-22 15:34:18,107 - Changing monitoring state from "Opening serial connection" to "Connecting"
2024-04-22 15:34:18,108 - Connected to: Serial<id=0xae631ef8, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2024-04-22 15:34:18,114 - Send: N0 M110 N0*125

The issue is with the printer, not with OctoPrint and it's ability to communicate with OctoPrint. Somehow the printer denied further cooperation.

During the print, the printer randomly, but often goes into busy state:

2024-04-22 03:48:07,370 - Recv: echo:busy: processing

Did you speed up the print by increasing the feedrate?

Maybe a printer firmware update can help:

5

It might be EMI which can cause communications errors. A high-quality, shielded USB cable with ferrite beads and/or isolating the AC power with a small UPS or a line filter.

Pay attention to the routing of both the AC power and the USB cable. Sometimes moving the USB cable from the right side to the left side or from the front to the back can help.