Communication timeout on Labists ET4

Get Help
1

What is the problem?

My Octoprint sometimes pauses the print on random layers/locations. It stays at the position for some seconds and then resumes the print.

My problem is that at the "pause position" the filament leaks a bit and i get a spot with too much filament.

What did you already try to solve it?

I changed the PSU, because the first one had only 2A.

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

Didn't try it.

Complete Logs

2021-04-22 17:25:06,569 - Send: N6520 G1 X133.19 Y114.303 E276.75306106
2021-04-22 17:25:06,601 - Recv: ok
2021-04-22 17:25:06,604 - Send: N6521 G1 X133.274 Y115.382 E276.8070587
2021-04-22 17:25:36,681 - 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-04-22 17:25:36,692 - Send: N6522 M10520
2021-04-22 17:25:36,700 - Recv: 807ok T:220 /220 B:70 /70
2021-04-22 17:26:06,754 - 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-04-22 17:26:06,757 - Send: N6523 M10521
2021-04-22 17:26:06,779 - Recv: ok T:222 /220 B:69 /70
2021-04-22 17:26:06,785 - Send: N6524 M10518
2021-04-22 17:26:06,793 - Recv: ok T:222 /220 B:69 /70
2021-04-22 17:26:06,799 - Send: N6525 G1 X133.239 Y116.325 E276.8541385
2021-04-22 17:26:06,806 - Recv: ok
2021-04-22 17:26:06,809 - Send: N6526 G1 X133.102 Y117.254 E276.90098*88
2021-04-22 17:26:06,818 - Recv: ok

Additional information about your setup

  • Labists ET4 (Printer)
  • Raspberry Pi 3B
  • OctoPrint 1.5.3
  • Python 3.7.3
  • OctoPi 0.18.0
2

2022-03-16 21:38:11,286 - octoprint.filemanager.analysis - INFO - Analysis of entry local:AET4_bedcable1-54hr.gcode finished, needed 7.55s
2022-03-16 21:38:15,174 - octoprint.printer.standard.job - INFO - Print job selected - origin: local, path: AET4_bedcable1-54hr.gcode, owner: root, user: root
2022-03-16 21:38:15,189 - octoprint.util.comm - INFO - Changing monitoring state from "Operational" to "Starting"
2022-03-16 21:38:15,189 - octoprint.printer.standard.job - INFO - Print job started - origin: local, path: AET4_bedcable1-54hr.gcode, owner: root, user: root
2022-03-16 21:38:15,205 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2022-03-16 21:38:15,221 - octoprint.util.comm - INFO - Changing monitoring state from "Starting" to "Printing"
2022-03-16 21:38:45,336 - octoprint.util.comm - INFO - Timeout while in an active heatup, considering heatup to be over.
2022-03-16 21:38:55,371 - octoprint.util.comm - INFO - No response from printer after 6 consecutive communication timeouts, considering it dead.
2022-03-16 21:38:55,386 - octoprint.util.comm - INFO - Changing monitoring state from "Printing" to "Offline after error"
2022-03-16 21:38:55,386 - octoprint.plugins.action_command_notification - INFO - Notifications cleared
2022-03-16 21:39:10,038 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial connection"
2022-03-16 21:39:10,038 - octoprint.util.comm - INFO - Connecting to port COM6, baudrate 115200

3

Just posting a few log lines is not enough to help you :smiley:
I guess you got a similar problem?

Please activate serial logging, try it again and upload the systeminfo bundle afterwards.