Will not connect on reboot, BUT

Get Help
1

What is the problem?

OctopPrint will not connect on reboot
BUT if I set to auto and let that error out then it goes ahead and connects to the default setting.Bundle

What did you already try to solve it?

Rebooted everything several times

Have you tried running in safe mode?

Yes, same

Did running in safe mode solve the problem?

No

Systeminfo Bundle

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

WRITE HERE

Additional information about your setup

Build 2022.01.20.112925 with "webcamd", based on OctoPi 0.18.0, running on Raspberry Pi 4 Model B Rev 1.4

OctoPrint Version 1.9.3

Prusa MK3 s MMU2 3.13.1
Brave Version 1.59.124 Chromium: 118.0.5993.117 (Official Build) (64-bit)

Windows 10 home 22H2

WRITE HERE
Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyS0@115200, /dev/ttyS0@250000, /dev/ttyS0@230400, /dev/ttyS0@57600, /dev/ttyS0@38400, /dev/ttyS0@19200, /dev/ttyS0@9600
Trying port /dev/ttyS0, baudrate 115200
Connecting to port /dev/ttyS0, baudrate 115200
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 115200 from hook default: error: '(22, 'Invalid argument')' @ comm.py:_open_serial:3920
Could not open port /dev/ttyS0, baudrate 115200, skipping
Trying port /dev/ttyS0, baudrate 250000
Connecting to port /dev/ttyS0, baudrate 250000
Unexpected error while connecting to serial port /dev/ttyS0, baudrate 250000 from hook default: error: '(22, 'Invalid argument')' @ comm.py:_open_serial:3920
Could not open port /dev/ttyS0, baudrate 250000, skipping
Trying port /dev/ttyS0, baudrate 230400
Connecting to port /dev/ttyS0, baudrate 230400
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0xacbc9b90, open=True>(port='/dev/ttyS0', baudrate=230400, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0125
Trying port /dev/ttyS0, baudrate 57600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0125
Trying port /dev/ttyS0, baudrate 38400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0125
Trying port /dev/ttyS0, baudrate 19200
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0125
Trying port /dev/ttyS0, baudrate 9600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0125
Changing monitoring state from "Detecting serial connection" to "Error"
Changing monitoring state from "Error" to "Offline after error"
Connection closed, closing down monitor
Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to port /dev/ttyS0, baudrate 115200
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0xacbc9eb0, open=True>(port='/dev/ttyS0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0125
Recv: ok
Send: N0 M110 N0125
Changing monitoring state from "Connecting" to "Operational"
Recv: ok
Send: N0 M110 N0125
Recv: ok
Send: N1 M115*39
Recv: FIRMWARE_NAME:Prusa-Firmware 3.13.1 based on Marlin FIRMWARE_URL:GitHub - prusa3d/Prusa-Firmware: Firmware for Original Prusa i3 3D printer by PrusaResearch PROTOCOL_VERSION:1.0 MACHINE_TYPE:Prusa i3 MK3S EXTRUDER_COUNT:1 UUID:00000000-0000-0000-0000-000000000000
Recv: Cap:AUTOREPORT_TEMP:1
Recv: Cap:AUTOREPORT_FANS:1
Recv: Cap:AUTOREPORT_POSITION:1
Recv: Cap:EXTENDED_M20:1
Recv: Cap:PRUSA_MMU2:1
Recv: ok
Send: M155 S2
Recv: ok
Recv: T:21.3 /0.0 B:21.1 /0.0 T0:21.3 /0.0 @:0 B@:0 P:0.0 A:29.7

2

You need to attach the system info bundle.

3

I am sorry, I thought I had done that...
Will check and find out what I did wrong...

4

octoprint-systeminfo-20231029190704.zip (116.9 KB)

5

OK, so any help then?
Or do I need to start over?

Regards
Randall

6

Looking at your log. There is a lot of serial communication errors. I would suggest that your issue is more of a serial communications issue and not a cant connect on reboot. You should start by checking your serial USB cable and making some improvements where you can. I suggest that you do as many of these actions as possible to see if they help.

  • I would use a shielded cable. (this is to reduce any noise)
  • Also maybe have a ferrite bead on it the cable. (this is to reduce any noise)
  • The cable should be only as long as necessary. (this is to reduce any noise)
  • Add a +5v blocking cable or adapter (This will help if there is any issue around the printer pulling too much power from the USB port on your Pi.) You can find many suggestions on how to do this in this thread.

Try some of this and let us know how you make out. If you are still having issues, make sure you turn on the serial logging (it's not on in the bundle you posted) and reproduce the issue and then I would suggest that you give us an updated bundle.

7

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