Prusa Mk3S+ v3.10.0 Comm Loss during Heatup Only

Get Help
1

What is the problem?

Prusa i3 Mk3s+ with F/W 3.10.0. Octoprint v1.7.2 on RPi 4.
RasPi Port Off in Prusa Menu

Everytime startign a print from Octoprint with a "cold" printer, get communication error and printer throws M112. If I preheat the printer, no issues at all.

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

What did you already try to solve it?

Read about making sure the GPIO RasPi is disabled.
Reflashed Printer
Reinstalled OctoPrint
Reflashed OctoPi

Have you tried running in safe mode?

No

Did running in safe mode solve the problem?

NA

Systeminfo Bundle

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

browser.user_agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/96.0.4664.93 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: 842829824
env.os.bits: 32
env.os.id: linux
env.os.platform: linux
env.plugins.pi_support.model: Raspberry Pi 4 Model B Rev 1.1
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.7.2
systeminfo.generator: systemapi

Additional information about your setup

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

OctoPrint version: 1.7.2
OctoPi version: 0.18.0
Printer: Prusa Original i3 MK3S+
Firmware: 3.10.0

2

Hi :slight_smile:

Please enable serial logging, replicate your issue and upload the systeminfo bundle so we can see what was going on.

3

octoprint-systeminfo-20211213145452.zip (177.3 KB)
Trimmed the serial.log to the start of the job.

4

Below are a series of exports from your serial.log. At 14:48:49 the temperature commands are sent with the last one being the M190 S85, heat the bed and wait. While the firmware is "waiting", the MMU starts communicating and at 14:48:52 (a little more than a minute later) the first communication timeout occurs. The nozzle reaches its temperature at 14:50:30 and the bed finally reaches its temperature at 14:52:26 (just under 4 minutes after the command).

The communication timeout seems to indicate that the timeout isn't long enough. By preheating, the time it takes to complete the M190 is shortened.

Another possibility is that the MMU communications are confusing OctoPrint. The ok response to the M190 may be getting lost (unless its the one at 14:52:26.654).

Try increasing the communication timeout and see if that helps.

2021-12-13 14:48:49,980 - Send: N14 M104 S230*81
2021-12-13 14:48:49,984 - Recv: ok
2021-12-13 14:48:49,985 - Send: N15 M140 S85*108
2021-12-13 14:48:49,988 - Recv: ok
2021-12-13 14:48:49,989 - Send: Tx
2021-12-13 14:48:49,989 - Send: N16 M190 S85*98
2021-12-13 14:48:50,574 - Recv: T:27.4 /230.0 B:32.1 /85.0 T0:27.4 /230.0 @:127 B@:127 P:0.0 A:34.2
2021-12-13 14:48:52,298 - Recv: echo:busy: paused for user
2021-12-13 14:48:52,299 - Printer seems to support the busy protocol, will adjust timeouts and set busy interval accordingly

2021-12-13 14:49:57,476 - Recv: T:184.4 /230.0 B:53.5 /85.0 T0:184.4 /230.0 @:127 B@:127 P:0.0 A:41.9
2021-12-13 14:49:57,775 - Recv: T:184.74 E:0 B:53.6
2021-12-13 14:49:57,776 - 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-12-13 14:50:28,992 - Recv: T:229.6 /230.0 B:62.9 /85.0 T0:229.6 /230.0 @:63 B@:127 P:0.0 A:43.7
2021-12-13 14:50:29,889 - Recv: T:230.39 E:0 B:63.2
2021-12-13 14:50:30,893 - Recv: T:231.25 E:0 B:63.5
2021-12-13 14:50:30,894 - 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-12-13 14:50:30,898 - Send: N29 M105*28
2021-12-13 14:50:31,089 - Recv: T:231.3 /230.0 B:63.6 /85.0 T0:231.3 /230.0 @:43 B@:127 P:0.0 A:43.8

2021-12-13 14:52:26,650 - Recv: T:230.5 /230.0 B:85.1 /85.0 T0:230.5 /230.0 @:26 B@:40 P:0.0 A:45.1
2021-12-13 14:52:26,653 - Recv: LCD status changed
2021-12-13 14:52:26,654 - Recv: ok
5

Also, when you got a MMU, it will end with in a Filament changing loop (99% before print finished)

Got the same problems you have.

6

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