Need assistance w/ Monoprice Cadet

What is the problem?
Cannot get OctoPrint to connect to the Monoprice Cadet 3D printer (product link)

What did you already try to solve it?

  • Tried automatic detection, got Error: No more baudrates to test, and no suitable baudrate found.
  • Could not find any documentation detailing the required baudrate for the printer over USB (manual).
  • Selected /dev/ttyUSB0
  • Have tried all of the baudrates, some of which result in gibberesh sent back, others send back nothing at all.

Details

  • OctoPrint Version 1.4.0
  • Printer is an IIIP printer

It is a mystery to me why people asking for help supply everything in the template but...

Logs (octoprint.log, serial.log or output on terminal tab at a minimum, browser error console if UI issue ... no logs, no support!)

Hint: note that logs above are links to a document that details how to find and supply them.

Logs for 250000 baudrate:

Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6a972bb0, open=True>(port='/dev/ttyUSB0', baudrate=250000, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
Recv: 1\x95\x961¥\x95%\x01!%¡!\x94\x84\x05\x11\x08
Recv: -¯¡51¡-\x10\xffÔ!çõ\xffÆ\xff-¡1¡!á!1\xff1\xff-0±\xff-0±\xff·\xff·\xff¯¡%õ\x14¤\x08\x94Ñ\x10F\xff±\x10\x08¡õ\x10\x081\xff0\x12nVF\xff¡0\x12\x86V\x08\x84\xff0\x12\x86VF\xff1ú0\x12\x86\x16÷F\xff1ú0\x12\x86\x16÷\x08¡0½R\x08!ú0\x90F\xffñõ°\x80Vç\x86\xff°F\xff\x84\xff°\x02F\xff!Õ\x8e\x10F\xff!Ô°\x10¤\x08ÆÑY
Recv: \x7f\x08Ä\xff°\x00F\xff%\xff\x000±F\xff¡\x00ð\x86V\x08\x04\xff\x000±F\xff1ú\x000±\x10F\xff1ú\x100±\x10\x08¡\x000±¾R\x08!ÕÀ0±\x00F\xff%\xff\x000±\x80F\xff\x86\xff\x000±\x96\x08\x84\xff\x000±\x10F\xffñÔ\x000±\x10¤\x08ÆÑ\x08w\x08Æ\xff\x08\x7f\x08\x96\xff\x12¡õ¯á%õ»¤\x08\x94Ñ\x10F\xff±\x10\x08¡õ\x10\x081\xff0\x12\x86VF\xff¡0\x12\x86V\x08\x84\xff0\x12\x86VF\xff1úð\x000±\x10F\xff1ú0\x12\x86~\x10\x08¡0åF\xff!ú°\xffF\xff!õ°\x80F\xff\x86\xff°F\xff\x84\xff°\x02F\xff!Õ°\x10F\xff!Ô°\x10¤\x08ÆÑ0

Logs for 230400 baudrate

Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6a9d88f0, open=True>(port='/dev/ttyUSB0', baudrate=230400, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125
Recv: \x8b¶©\x14\x99Z\x8aå\x05Ñ\x1e\x8bÀÀ|±<Í`
\x92àÂþ\x9a°\x19ç\xff\x98\xffÙÏÆÄ\x93\x99¦Mý[TÏ\xff[r\x12$³\xff\бù\x93Eâvö\x14\x8aþ]³\x8dÙ\xff\x95Ì\x06\xff0\x84&\x93ë\xff\x14Ñ\x85&\x93â:\xff\x98\x84\x1aÓ5f\xff\x83¡Ó³\x8dF\xff\x92ó>÷Ì]°b¤þ½\xffØ\x99\x8aþFø\x98È\x8bþ&\x91\x8aþP\xff;\â
ÁRë\x8d\x06\xff5ÛeÌÙÝ5¬\x03ó$\xff\x18ESãd\xffLæ¶\x8aþ]\x14\x9a\x99\x18$\xffÌ\x98pÓ\x8dOø\x85Ó\x93\x8b\xffÍø\x85\x9a\x93â¥\xffÌ润ãÍöÌ8¶\x0c\x8dt\xffL\x9aÓææ\x90Å\x85\x9a\x996_þ ù\x85Ó\x93\x8bþ\x06\xff\x98\x1aö\x8b5\x12ô<fæ\x92\xffíBãÑ\xff²\x8b\xff\\x89´\xff>E|{ÍÜ\x8a\xff\x06\x9cÌ\x0fðÜ\x9d\xff
ðÑ\x9d\x9a\x93\x8b\xff ùñ¡ÓÚ\x8d\x145Ìæ¶\x8a\xffOùÑ\x85Ó\x99\x98ÌFùÑ\x14\x9a\x93\x9d\xfføÍ\x87Ãâ]ùÃÕ\x8d\x0fù\x12{ÜÙ\xff\x91\x8aþÒ\xff\x18\x8e\x8aþ
Á0Ú```

Logs for `115200` and below:
```Connecting to: /dev/ttyUSB0
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6aa110b0, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from "Opening serial port" to "Connecting"
Send: N0 M110 N0*125```

You may install this:
Malyan/Monoprice Connection Fix

1 Like

That is a typical response when the baudrate is not correct. OctoPrint should keep trying other rates until it 1) finds one it likes or 2) runs out of baudrates to try. My guess is that one of the baudrates selected may be the right one but the printer response is not what OctoPrint expects.

Edit: What @Ewald_Ikemann said!

1 Like

Unfortunately, the Monoprice plugin doesn't appear to resolve the issue.

Will continue my search & reply when I've found a solution. Thanks to all who've provided pointers thus far.

Connecting to: /dev/ttyUSB0
Using Malyan/Monoprice Connection Fix Plugin to create serial connection
Changing monitoring state from "Offline" to "Opening serial port"
Connected to: Serial<id=0x6f616e10, open=True>(port='/dev/ttyUSB0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Starting baud rate detection...
Changing monitoring state from "Opening serial port" to "Detecting baudrate"
Trying baudrate: 9600
Send: N0 M110 N0*125
Recv: {ùý\xffû>lþ\xff¿\xffþþ_þ÷\xff\xff\xff\x7fþ\x9bßo\xff÷6<þüû
Recv: ¿
Recv: \x9f¿
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 115200
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 250000
Send: N0 M110 N0*125
Recv: \x9011ú@\x01\x91\x91?
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 230400
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Recv: \x11\x05o
Recv: ä\x00\x1b\xff
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 57600
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 38400
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Recv: é\x91
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Trying baudrate: 19200
Send: N0 M110 N0*125
Baudrate test retry #1
Send: N0 M110 N0*125
Baudrate test retry #2
Send: N0 M110 N0*125
Baudrate test retry #3
Send: N0 M110 N0*125
Baudrate test retry #4
Send: N0 M110 N0*125
Recv: þþ
Changing monitoring state from "Detecting baudrate" to "Error: No more baudrates to test, and no suitable baudrate found."
Changing monitoring state from "Error: No more baudrates to test, and no suitable baudrate found." to "Offline (Error: No more baudrates to test, and no suitable baudrate found.)"
Connection closed, closing down monitor```
1 Like

Inquired with Monoprice team in the Questions section at:
https://www.monoprice.com/product?p_id=40108

Hello, I had the same problem. I found out by looking at the included WiiBuilder configuration for the Monoprice Cadet that the serial port communicates at 1000000 baud. Yes, that is 1 million baud. you can confirm by connecting to the serial port with a terminal, but the short fix is to modify your local octoprint to show 1 million baud. You would need to modify the octoprint/util/comm.py file to include 1000000 in the list of potential baud rates.

1 Like

Nice! I'll try that today! Thank you @worklife_balance!

No, you would not. Adding additional baudrates is what Settings > Serial > Additional Baudrates is for.

1 Like

Worked great. Thanks, @worklife_balance & @foosel!