Too many consecutive timeouts

[Sean_Boyd]

What is the problem?

I am getting failed prints due to this error

What did you already try to solve it?

Updated Printer Firmware to TH3D 2.6 flashed via octoprint.
Changed usb cable 3 times and purchased a new shielded one from Amazon basics
Also put tape on 5v pin on USB cable, my cable does not have a ferrite core, i might try purchasing some clip on ones from Amazon

Have you tried running in safe mode?

Not yet

Did running in safe mode solve the problem?

Not sure yet

Systeminfo Bundle

It tells me my system info log is too big to upload, its currenly 6MB and your website limit is 4MB. ... no bundle, no support!)

WRITE HERE

Additional information about your setup

Using the latest version of Octoprint on a raspberry pi 4B

Here is a snippet of where it timed out, it seems to be command - Send: N74050 M105*33

Log snippet:

022-01-09 23:09:06,519 - Recv:  T:210.00 /210.00 B:60.00 /60.00 @:97 B@:0
2022-01-09 23:09:07,431 - Recv: ok
2022-01-09 23:09:07,434 - Send: N74048 G1 X182.056 Y149.349 E1710.91711*95
2022-01-09 23:09:07,927 - Recv: ok
2022-01-09 23:09:07,929 - Send: N74049 G1 X182.056 Y137.449 E1711.31291*86
2022-01-09 23:09:08,519 - Recv:  T:210.00 /210.00 B:59.99 /60.00 @:97 B@:0
2022-01-09 23:09:17,533 - 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.
2022-01-09 23:09:17,536 - Send: N74050 M105*33
2022-01-09 23:09:26,551 - 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.
2022-01-09 23:09:26,561 - Send: N74051 M105*32
2022-01-09 23:09:35,563 - 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.
2022-01-09 23:09:35,569 - Send: N74052 M105*35
2022-01-09 23:09:44,574 - 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.
2022-01-09 23:09:44,580 - Send: N74053 M105*34
2022-01-09 23:09:53,585 - 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.
2022-01-09 23:09:53,590 - Send: N74054 M105*37
2022-01-09 23:10:02,591 - 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.
2022-01-09 23:10:02,667 - Changing monitoring state from "Printing" to "Offline after error"
2022-01-09 23:10:02,703 - Connection closed, closing down monitor
2022-01-09 23:37:21,402 - Changing monitoring state from "Offline" to "Detecting serial connection"
2022-01-09 23:37:21,451 - Performing autodetection with 7 port/baudrate candidates: /dev/ttyUSB0@115200, /dev/ttyUSB0@250000, /dev/ttyUSB0@230400, /dev/ttyUSB0@57600, /dev/ttyUSB0@38400, /dev/ttyUSB0@19200, /dev/ttyUSB0@9600
2022-01-09 23:37:21,452 - Trying port /dev/ttyUSB0, baudrate 115200
2022-01-09 23:37:21,452 - Connecting to port /dev/ttyUSB0, baudrate 115200
2022-01-09 23:37:21,553 - Handshake attempt #1 with timeout 2.0s
2022-01-09 23:37:21,560 - Connected to: Serial<id=0xa88f4070, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2022-01-09 23:37:21,561 - Send: N0 M110 N0*125
2022-01-09 23:37:22,431 - Recv: start
2022-01-09 23:37:22,444 - Changing monitoring state from "Detecting serial connection" to "Operational"
2022-01-09 23:37:22,490 - Send: N0 M110 N0*125
2022-01-09 23:37:22,495 - Recv: Marlin TH3D UFW 2.36
2022-01-09 23:37:22,497 - Recv: 

[b-morgan]

You know a lot about your configuration, we know almost nothing. You failed to mention what printer you have. The more information you give us, the better answers we give you.

Delete the current logs, recreate the problem, and upload the systeminfo bundle.

[Sean_Boyd]

I have it running on a CR10-S, I wonder if the problem may have been overheating. When the issue occurred yesterday I had all 3 printers running in my room and the door was closed so the ambient temp was probably getting quite warm and I have no active cooling or heatsinks on my raspberry pi4, I wonder if it throtlled itself and locked up...

[b-morgan]

I'm going to guess EMI issues (and not overheating issues). Creality printers have a reputation for both being extremely sensitive to EMI and emitting a higher than normal amount of EMI. Not a good combination.

Others have been successful by using short, high quality, shielded USB cables with ferite beads at both ends, careful routing of cables and power cords, and in some cases, rerouting cables inside the printers. You can search this forum for solutions others have found.

[Sean_Boyd]

I would just like to comment back that I managed to fix these issues by buying ferite beads to clip onto my cables, I went a little over the top and put them on the power cable to the printer, the raspberry pi and the USB cable but I havent had a single timeout since and I have done about 20-30 prints.