I'm becoming crazy! I get "Communication timeout while printing"

[bulgaro80]

I found a lot of this type of posts and everyone has been solved in a different way... I tried I would say most of the suggested steps without beeing able to solve it...

What is the problem?

I'm experiencing an issue when I print objects with long straight lines. I can print small objects without problems.

Printing big objects with long straight lines I got several stop of the printer, getting below error message:

"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."

I have an Ender 3V2 Stock with BLTouch and filament sensor connected to Octoprint. In attach my Octoprint Log.

Octoprint it's connected with a USB cable where I removed the 5V.

Firmware used: "Ender3-V2-BLTouch-20210122.bin" and same issue even with "Ender3-V2-BLTouch-20210119.bin" from https://marlin.crc.id.au/

What did you already try to solve it?

• Upgraded the firmware
• Increased the Timeouts parameters in Octoprint menu
• Printed from SD (without Octoprint) and it works
• force reainstall Octprint 1.5.3

Have you tried running in safe mode?

No

Complete Logs

serial.log
2021-01-22 21:08:10,294 - Send: N31671 G0 X115.382 Y59.09720
2021-01-22 21:08:11,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:96 B@:52
2021-01-22 21:08:13,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:96 B@:52
2021-01-22 21:08:13,114 - 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.
2021-01-22 21:08:13,121 - Send: N31672 G1 E5.00000 F3000.00028
2021-01-22 21:08:15,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:96 B@:52
2021-01-22 21:08:17,112 - Recv: T:225.00 /225.00 B:79.99 /80.00 @:96 B@:55
2021-01-22 21:08:17,113 - 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.
2021-01-22 21:08:19,112 - Recv: T:225.00 /225.00 B:79.99 /80.00 @:96 B@:55
2021-01-22 21:08:21,112 - Recv: T:225.06 /225.00 B:80.00 /80.00 @:95 B@:52
2021-01-22 21:08:21,113 - 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.
2021-01-22 21:08:23,112 - Recv: T:225.81 /225.00 B:80.00 /80.00 @:76 B@:52
2021-01-22 21:08:25,112 - Recv: T:225.94 /225.00 B:80.00 /80.00 @:74 B@:52
2021-01-22 21:08:25,113 - 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.
2021-01-22 21:08:27,112 - Recv: T:225.31 /225.00 B:80.00 /80.00 @:90 B@:52
2021-01-22 21:08:29,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:95 B@:52
2021-01-22 21:08:29,113 - 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.
2021-01-22 21:08:31,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:93 B@:52
2021-01-22 21:08:33,112 - Recv: T:225.00 /225.00 B:80.00 /80.00 @:92 B@:52

Additional information about your setup

Octoprint Version 1.5.2, Raspberry PI 4, Creality 3V2 with BLTouch and filament sensor connected to Octoprint.

[Ewald_Ikemann]

Hello @bulgaro80!

@bulgaro80

Have you tried running in safe mode?

No

The please try.

@bulgaro80

Complete Logs

Please attach the complete logs as files.

[bulgaro80]

Many thanks for your answer. While I try in safe mode to replicate the issue, here in attach my complete Serial.log
serial.log (834.7 KB)

[Ewald_Ikemann]

The hiccup always takes exactly 2 sec. during temperature readout.

Have you tried this:

2021-01-22 19:42:59,226 - 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.

From time to time there are serial transfer issues.
You may try another (better/shorter) USB cable.

Bug "Communication timeout while printing"

What is the problem? Hi, Octoprint disconnects itself from the printer randomly. It is not a problem to restart the Raspberry because the uptime doesn't return to zero after the communication is cut. When an Octoprint serial break does not pause. In my case the printer is just waiting for further instructions, in the logs I can see that the connection comes back but octoprint doesn't do anything anymore. What did you already try to solve it? Full reinstallation of Octoprint Try it with seve…

[bulgaro80]

Regarding this below, I have only changed timeouts within Octoprint (see screenshot). Is there anything else I can do? Like "Configure long running commands". is there any specific command I can do?
2021-01-22 19:42:59,226 - 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.

[bulgaro80]

[bulgaro80]

I'm also going to try to change my USB cable, even if it's strange because the issue appears only with prints with long streight lines...

[Charlie_Powell]

Looks like you are using UI Customizer, so my view is not the same but the settings are available under Serial Connection > Firmware and Protocol > Protocol Fine Tuning > Advanced.

[bulgaro80]

Great, many thanks! I found it and added G1 in that line, because I see in the serial.log that G1 command is always before the error message. Any other suggestion or advice?

[b-morgan]

I'm going to date myself here but I remember taking a transistor radio inside the computer room and "listening" to the "songs" the computer played while it was operating. This phenomena is known as Electromagnetic interference ( EMI ) (actually it was RFI) and I'll bet that all of Creality's printers are "playing a frickin' concert".

The morale of this story is that you need a really good USB cable with ferrite beads (and tape over the 5V pin) to have even a ghost of a chance to avoid the dreaded "Communication timeout while printing".

[dafi]

Hey there,
I'm facing this exact problem with my Ender 3 V2 as well. It is a print with straight long lines (16cm) and I'm not seeing the issue when printing from SD card.
When the printer stops and Octoprint loses connection, the hotend just keeps sitting at a spot and nozzle and bed still heating properly. The first time it happened after 8h on the print. The printer's display is still responsive when it happens.
Trying to recover the print, I took the gcode and cut away everything before the last command and immediately started that as a new print. Except of a blob of PLA on the print that I have to clean up in the end, this worked. Not to mention that the print failed again from the same problem 2 more times already. I recovered from it every time and it's still printing as I write here.

Could this really be the cable? I'll add my logs (which don't help me at all, since it's all very normal, until the printer just doesn't answer anymore.

Hope someone has a good idea or solution

octoprint.log (46.8 KB)
serial.log (208.9 KB)

Ender 3 V2 on stock v1.0.2, Octoprint 1.5.3

Best,
Daniel

[bulgaro80]

Yep, to avoid that issue I printed via SD and it worked....

[daveatwork]

Hello,
I am also having issues with serial disconnections. Today I found out that when I turn off my fluorescent lamp (which is in the same domino plug) the serial connection interrupts.

I hope you have been helped with this.

[Charlie_Powell]

Likely some EMI (Electromagnetic interference) from the lamp, or noisy power lines that are kept under control by the lamp drawing more power.