Constant freezing while printing - mixed recv OK+status?

What is the problem?

The printer (Sunlu S8) while printing via USB freezes for a second or 2 and then continues.

What did you already try to solve it?

  • Updated TH3D firmware from 2.24 to 2.31
  • Updated Octoprint from 1.5.2. to 1.6.1.
  • Changed 4 usb cables (although none with ferite core, but performances were the same)
  • A suspect firmware of the board.... but no clue what to fix, as I freshly flashed the printer.

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

browser.user_agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.164 Safari/537.36
connectivity.connection_check : 1.1.1.1:53
connectivity.connection_ok : true
connectivity.enabled : true
connectivity.online : true
connectivity.resolution_check : octoprint.org
connectivity.resolution_ok : true
env.hardware.cores : 4
env.hardware.freq : 1500
env.hardware.ram : 3959984128
env.os.bits : 32
env.os.id : linux
env.os.platform : linux
env.plugins.pi_support.model : Raspberry Pi 4 Model B Rev 1.2
env.plugins.pi_support.octopi_version : 0.18.0
env.plugins.pi_support.throttle_state : 0x0
env.python.pip : 20.3.3
env.python.version : 3.7.3
env.python.virtualenv : true
octoprint.safe_mode : true
octoprint.version : 1.6.1
printer.firmware : Marlin TH3D UFW 2.31 (Jul 26 2021 19:07:12)
systeminfo.generator : systemapi

Additional information about your setup

OctoPrint version: 1.6.1
OctoPi version: 0.18.0
Printer: Sunlu S8, original board, added BLtouch
Board with OctoPi: Raspberry Pi 4
Firmware: TH3D 2.31
Browser: Chrome
Operating system: Windows 10

Points in serial.log where the problem happened:

2021-07-26 18:45:17,291 - Send: N9324 G1 F4800 X167.802 Y150.832 E152.33057*55
2021-07-26 18:45:17,575 - Recv: ok
**2021-07-26 18:45:17,577 - Send: N9325 G0 F12000 X168.257 Y150.721*79**
**2021-07-26 18:45:19,258 - Recv: o-á T:240.00 /240.00 B:80.00 /80.00 @:61 B@:0**
2021-07-26 18:45:21,258 - Recv:  T:240.00 /240.00 B:79.86 /80.00 @:63 B@:127
2021-07-26 18:45:21,259 - 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-07-26 18:45:21,273 - Send: N9326 M105*25
2021-07-26 18:45:21,285 - Recv: ok T:240.00 /240.00 B:79.86 /80.00 @:63 B@:127
2021-07-26 18:45:21,291 - Send: N9327 G1 F4800 X171.511 Y153.975 E152.48362*52
2021-07-26 18:45:21,301 - Recv: ok


2021-07-26 18:45:52,714 - Send: N10313 G1 X174.813 Y149.705 E165.25938*99
2021-07-26 18:45:52,722 - Recv: ok
**2021-07-26 18:45:52,722 - Send: N10314 G1 X174.813 Y149.716 E165.25975*111**
**2021-07-26 18:45:53,274 - Recv: o-á T:239.81 /24r‚‚þ B:79.82 /80.00 @:69 B@:127**
2021-07-26 18:45:55,274 - Recv:  T:239.94 /240.00 B:79.76 /80.00 @:66 B@:127
2021-07-26 18:45:57,279 - Recv:  T:239.94 /240.00 B:79.76 /80.00 @:66 B@:127
2021-07-26 18:45:57,279 - 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-07-26 18:45:57,292 - Send: N10315 M105*33
2021-07-26 18:45:57,316 - Recv: ok T:239.94 /240.00 B:79.83 /80.00 @:66 B@:127
2021-07-26 18:45:57,323 - Send: N10316 G1 X174.83 Y150.014 E165.26967*81
2021-07-26 18:45:57,332 - Recv: ok


2021-07-26 18:46:02,146 - Recv: ok
2021-07-26 18:46:02,147 - Send: N10617 G1 X140.68 Y143.388 E168.8414*107
**2021-07-26 18:46:03,279 - Recv: o-á T:239.88 /240.00 B:80.07 /80.00 @:68 B@:0**
**2021-07-26 18:46:05,279 - Recv:  T:239.88 /240.00 B:80.12 /80.00 @:68 B@:0**
2021-07-26 18:46:05,280 - 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-07-26 18:46:05,292 - Send: N10618 M105*41
2021-07-26 18:46:05,305 - Recv: ok T:239.88 /240.00 B:80.12 /80.00 @:68 B@:0
2021-07-26 18:46:05,312 - Send: N10619 G1 X140.828 Y143.611 E168.8503*91
2021-07-26 18:46:05,321 - Recv: ok

Octoprint.log

CCR10S_SmartTemperatureTower_PETG_220-265.gcode, owner: logocar3, user: logocar3
2021-07-26 18:34:33,791 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-07-26 18:34:33,799 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2021-07-26 18:40:45,207 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:41:07,208 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:41:21,412 - octoprint.server.heartbeat - INFO - Server heartbeat <3
2021-07-26 18:43:01,229 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:44:27,250 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:44:35,256 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:44:45,255 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:45:21,258 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:45:57,279 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.
2021-07-26 18:46:05,280 - octoprint.util.comm - INFO - Communication timeout while printing, trying to trigger response from printer.

Thank you for your help!

A cable with one or two ferrite cores is a nice thing but I guess you got a bigger problem then the cable if you get 3-4 communication timeouts per minute.

Do you have any other electrical devices nearby that could effect you connection with EMI?
Could be a fridge, a freezer, an AC, a washing machine and similar stuff.

I'm not sure that the cable is the problem: the place of the error is quite repeatable:

  • Instead of Recv: ok i get Recv: o-á

And of course, the Octoprint does not receive ack, so it stops.

It quite can be: Such errors often are a result of a bad/disturbed USB connection to the printer

I don't have any devices nearby only laptop 1 meter away, but the problem was persisted ever after airplane more.

Tried to put external ferrite cores on the cable, no difference.

One thing that maybe helps is that the freezes are more frequent with time: at the start there are like 5-10min that have single freeze, but after a while it gets to 1-5 frezzes per minute. No errors for overheating on octopi, printer electronics airflow is only warm nothing special.

Have you tried any other firmware? Since it is such a regular and exactly the same problem each time it seems it is unlikely to be interference. There's lots of issues caused by that, so it's right to rule it out.

You could try vanilla Marlin FW, or report the issue to TH3D to see if it is a bug they know about? The regular-ness of it is making me think that there's some kind of software bug.

Please enable the serial logging:

And then share the serial.log after you tried to print something.