Octoprint stopped connecting to Prusa MK3S due to timeout

What is the problem?

After running for 2+ years Octoprint won't connect to a Prusa MK3S. After completing its last job successfully, the terminal output now shows the output below.

There were no commanded changes (ex. software updates) applied prior to this error occurring - octoprint just wouldn't connect after successfully completing a job.

Terminal output:

(without safe mode enabled)

Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyACM0, baudrate 115200
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0x6eadeb10, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=40.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Recv: start
Send: N0 M110 N0*125
Recv: Command not found!
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

(with safe mode enabled)

Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyACM0, baudrate 115200
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0x6eb58a30, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=40.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Recv: start
Send: N0 M110 N0*125
There was a timeout while trying to connect to the printer
Changing monitoring state from "Connecting" to "Offline"
Connection closed, closing down monitor

What did you already try to solve it?

  • Reboot printer and Octoprint respectively
  • Try connecting with AUTO / AUTO for serial port and baud rate
  • Upgrade Octoprint to latest (V1.8.1)
  • Upgrade printer firmware to latest (V3.11.0)
  • Increase Communication timeout to 30s (from 10 default)
  • Set Max. consecutive timeouts while idle to 0 to disable
  • Connect to different USB ports on Rpi
  • Change USB cable to new cable
  • Change Rpi power cable to new cable

Have you tried running in safe mode?

Yes

Did running in safe mode solve the problem?

No

Systeminfo Bundle

octoprint-systeminfo-20220608194531.zip (55.6 KB)

Additional information about your setup

Octopi Version 0.18.0, running on Raspberry Pi 3 Model B Plus Rev 1.3
Octoprint Version 1.8.1
Printer: Prusa MK3S
Printer Firmware: V3.11.0

This issue was encountered on previous versions of all of the above stack though persists when everything is upgraded to latest.

The Prusa firmware has the ability to use either the USB connector or an internal serial port intended for use with an imbedded RPi Zero. My guess is that this has somehow gotten into the wrong state.

I don't own a Prusa printer but search this forum for "Prusa switch serial port" and you should find details on how to switch it.

1 Like

This one

1 Like

Thank you both so much!

This was it - likely a fat finger while doing a live adjust Z (due to weird dial that sometimes selects the menu item above it) between prints.

Setting Rpi Port to off fixed this.

I am having the same issue of not connecting...timing out...offline.
It previously worked for several years.
I also have Prusa MK3S+ connected via USB cable. The RPI is "off" in hardward settings.
I have changed Cat 5 cables. Did have Cat 5 going from computer to router and a second from router to Raspberry PI. Now I only have cable from Raspberry Pi to router. (my internet on pc is working great). My router reports the Octopi is connected.
I can monitor my webcam, both from my pc and iPhone. I cannot connect, tranfer, nor control from either.
I have Octopi versus 1.7.3
I have rebooted both the Raspberry Pi and PC, swapped USB ports.
haproxy.log (142.5 KB)
octoprint.log (105.3 KB)
[plugin_pluginmanager_console.log|attachment]
(upload://tAcbcREMRxZ3OmqQOJnnEbOoyXz.log) (21.3 KB)
plugin_softwareupdate_console.log (27.0 KB)
webcamd.log (10.4 KB)
serial.log (592 Bytes)

serial.log (592 Bytes)
webcamd.log (10.4 KB)

If the RPi Port is set to off, then you don't have the same issue, since that was the solution here - I would recommend opening your own post.

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