I don't really need help since it all works, this is more about understanding what happens.
What is the problem?
I configured Marlin (2.0.9.1) for 250000 baud instead of the prior 115200 baud.
Then set the connection settings top-left to AUTO on port and AUTO on baud rate and turned the printer's power on. the log goes like:
2021-11-24 18:17:01,423 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-11-24 18:17:01,479 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 7 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyACM0@250000, /dev/ttyACM0@230400, /dev/ttyACM0@57600, /dev/ttyACM0@38400, /dev/ttyACM0@19200, /dev/ttyACM0@9600
2021-11-24 18:17:01,480 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 115200
2021-11-24 18:17:01,481 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 115200
2021-11-24 18:17:01,495 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-11-24 18:17:01,502 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:17:03,505 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-11-24 18:17:03,515 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:17:05,472 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Operational"
2021-11-24 18:17:05,510 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:17:05,626 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2021-11-24 18:17:05,955 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin 2.0.9.1 (Nov 24 2021 15:56:51)"
And this is, what the ui tells me: 115200.
Did a test print, no problem whatsoever.
Disconnected, set baudrate to 250000, connect.
OctoPrint is fine with it:
2021-11-24 18:22:26,704 - octoprint.util.comm - INFO - Changing monitoring state from "Offline" to "Opening serial connection"
2021-11-24 18:22:26,713 - octoprint.util.comm - INFO - Connecting to port /dev/ttyACM0, baudrate 250000
2021-11-24 18:22:26,759 - octoprint.util.comm - INFO - Changing monitoring state from "Opening serial connection" to "Connecting"
2021-11-24 18:22:26,775 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:22:26,794 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:22:26,805 - octoprint.util.comm - INFO - Changing monitoring state from "Connecting" to "Operational"
2021-11-24 18:22:26,931 - octoprint.plugins.stats - INFO - Printer Stats - on_event
2021-11-24 18:22:26,953 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-11-24 18:22:27,304 - octoprint.util.comm - INFO - Printer reports firmware name "Marlin 2.0.9.1 (Nov 24 2021 15:56:51)"
2021-11-24 18:22:27,372 - octoprint.util.comm - INFO - Firmware states that it supports temperature autoreporting
2021-11-24 18:22:27,452 - octoprint.util.comm - INFO - Firmware states that it supports emergency GCODEs to be sent without waiting for an acknowledgement first
Another test print, all is smooth.
Still, I'm confused.
-
Does the baud rate not matter? I'd have expected an error.
-
Auto-detection did not detect Marlin's configured baud rate even though 250000 is one of the values it states to check. Apparently it received a handshake on the first attempt and settled for that.
octoprint-systeminfo-20211124183221.zip (676.7 KB)
This is 1.7.2 on 0.18.0, raspi 3B+