Communication errors and timeouts

What is the problem?

communication errors and timeouts, stop printing

What did you already try to solve it?

reinstall octoprint
try another raspberri pi

Have you tried running in safe mode?

no

Did running in safe mode solve the problem?

WRITE HERE

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

WRITE HERE

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

browser.user_agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36
connectivity.connection_check: 1.1.1.1:53
connectivity.connection_ok: true
connectivity.enabled: false
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: false
octoprint.version: 1.6.1
printer.firmware: Marlin TH3D U1.R2.B5
systeminfo.generator: systemapi
octoprint-systeminfo-20211006192948.zip (352.0 KB)
serial.log (1.5 MB)

the latest sent commands
Recv: ok

Send: N13974 G1 X222.085 Y91.379 E2.1246*99

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.

Send: N13975 M105*46

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.

Send: N13976 M105*45

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.

Send: N13977 M105*44

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.

Send: N13978 M105*35

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.

Send: N13979 M105*34

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.

Changing monitoring state from "Printing" to "Offline after error"

Recv: ok

Send: N13974 G1 X222.085 Y91.379 E2.1246*99

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.

Send: N13975 M105*46

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.

Send: N13976 M105*45

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.

Send: N13977 M105*44

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.

Send: N13978 M105*35

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.

Send: N13979 M105*34

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.

Changing monitoring state from "Printing" to "Offline after error"

Connection closed, closing down monitor

and thanks

Hi :slight_smile:

You should try another USB cable - preferably a quality one with ferrite beads.
Try to keep the cable as short as possible and don't run it next to the stepper motors.

Also is there something nearby that could emit EMI (like a fridge, an ac, etc)?

Some Creality printers are themselves the source of EMI / RFI. Since the OP didn't tell us what printer, we can only guess at this point.

I also think running is safe mode would help.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.