USB connection to Mac causes firmware to get wedged (and serial connection to fail)

Hi all. First time poster, recent patron.

I have successfully flashed the LCD and main board w/ the latest firmware versions on my Maker Select Plus. The LCD screen needed recalibration afterwards but that was fine. I had problems connecting Octoprint and Cura to the printer via the USB cable when I was using an M1 Mac, but when I switched to an Intel Mac (both running Big Sur), it worked fine. I drove several prints from the Mac using Octoprint earlier today.

This evening I did a minor mod on the printer (installing a new fan, doing the hot end calibration). Since then, I’m unable to establish a working USB/serial connection.

I have tried with and without the Monoprice/Manyan plugin, it makes no difference. I’ve tried both AUTO and manual settings on port and baud speed, with no effect.

The console logs are all the same basically:

Changing monitoring state from "Offline" to "Opening serial connection"
Connecting to: /dev/tty.usbserial-1410
Using Malyan/Monoprice Connection Fix Plugin to create serial connection
Changing monitoring state from "Opening serial connection" to "Connecting"
Connected to: Serial<id=0x10fc59c10, open=True>(port='/dev/tty.usbserial-1410', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
No answer from the printer within the connection timeout, trying another hello
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

One maybe interesting bit is as soon as the Mac starts to talk to the printer via USB, the LCD panel becomes unresponsive (it highlights the button being touched and beeps but doesn’t perform the action).

I should add that I’ve tried Octoprint, Cura, and Universal GCode Sender and all are failing to establish a serial connection (even though Cura did, and that’s how I upgraded the firmware). Also, I’ve tried different USB cables, and tried various orders of boot + connect operations.

I’m running out of ways to troubleshoot this. Any help welcome!

Partial log file:

2021-01-31 22:40:25,455 - Changing monitoring state from "Offline" to "Detecting serial connection"
2021-01-31 22:40:25,455 - Performing autodetection with 7 port/baudrate candidates: /dev/cu.usbserial-1420@115200, /dev/cu.usbserial-1420@250000, /dev/cu.usbserial-1420@230400, /dev/cu.usbserial-1420@57600, /dev/cu.usbserial-1420@38400, /dev/cu.usbserial-1420@19200, /dev/cu.usbserial-1420@9600
2021-01-31 22:40:25,456 - Trying port /dev/cu.usbserial-1420, baudrate 115200
2021-01-31 22:40:25,456 - Connecting to port /dev/cu.usbserial-1420, baudrate 115200
2021-01-31 22:40:25,463 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:25,467 - Connected to: Serial<id=0x10fdb2760, open=True>(port='/dev/cu.usbserial-1420', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2021-01-31 22:40:25,468 - Send: N0 M110 N0*125
2021-01-31 22:40:27,475 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:27,479 - Send: N0 M110 N0*125
2021-01-31 22:40:29,484 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:29,487 - Send: N0 M110 N0*125
2021-01-31 22:40:31,492 - Trying port /dev/cu.usbserial-1420, baudrate 250000
2021-01-31 22:40:31,495 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:31,498 - Send: N0 M110 N0*125
2021-01-31 22:40:33,499 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:33,502 - Send: N0 M110 N0*125
2021-01-31 22:40:35,507 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:35,511 - Send: N0 M110 N0*125
2021-01-31 22:40:37,514 - Trying port /dev/cu.usbserial-1420, baudrate 230400
2021-01-31 22:40:37,516 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:37,517 - Send: N0 M110 N0*125
2021-01-31 22:40:39,519 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:39,523 - Send: N0 M110 N0*125
2021-01-31 22:40:41,527 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:41,529 - Send: N0 M110 N0*125
2021-01-31 22:40:43,533 - Trying port /dev/cu.usbserial-1420, baudrate 57600
2021-01-31 22:40:43,535 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:43,539 - Send: N0 M110 N0*125
2021-01-31 22:40:45,538 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:45,541 - Send: N0 M110 N0*125
2021-01-31 22:40:47,545 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:47,547 - Send: N0 M110 N0*125
2021-01-31 22:40:49,548 - Trying port /dev/cu.usbserial-1420, baudrate 38400
2021-01-31 22:40:49,549 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:49,553 - Send: N0 M110 N0*125
2021-01-31 22:40:51,555 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:51,557 - Send: N0 M110 N0*125
2021-01-31 22:40:53,559 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:53,562 - Send: N0 M110 N0*125
2021-01-31 22:40:55,562 - Trying port /dev/cu.usbserial-1420, baudrate 19200
2021-01-31 22:40:55,563 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:40:55,566 - Send: N0 M110 N0*125
2021-01-31 22:40:57,568 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:40:57,571 - Send: N0 M110 N0*125
2021-01-31 22:40:59,574 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:40:59,579 - Send: N0 M110 N0*125
2021-01-31 22:41:01,584 - Trying port /dev/cu.usbserial-1420, baudrate 9600
2021-01-31 22:41:01,586 - Handshake attempt #1 with timeout 2.0s
2021-01-31 22:41:01,590 - Send: N0 M110 N0*125
2021-01-31 22:41:03,589 - Handshake attempt #2 with timeout 2.0s
2021-01-31 22:41:03,591 - Send: N0 M110 N0*125
2021-01-31 22:41:05,596 - Handshake attempt #3 with timeout 2.0s
2021-01-31 22:41:05,599 - Send: N0 M110 N0*125
2021-01-31 22:41:07,599 - Changing monitoring state from "Detecting serial connection" to "Error: No more candidates to test, and no working port/baudrate combination detected."
2021-01-31 22:41:07,603 - Changing monitoring state from "Error: No more candidates to test, and no working port/baudrate combination detected." to "Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)"
2021-01-31 22:41:07,604 - Connection closed, closing down monitor
2021-01-31 22:45:37,444 - Changing monitoring state from "Offline" to "Opening serial connection"
2021-01-31 22:45:37,445 - Connecting to port /dev/tty.usbserial-1420, baudrate 115200
2021-01-31 22:45:37,450 - Changing monitoring state from "Opening serial connection" to "Connecting"
2021-01-31 22:45:37,451 - Connected to: Serial<id=0x10fdc26d0, open=True>(port='/dev/tty.usbserial-1420', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
2021-01-31 22:46:05,262 - Unexpected error while reading serial port, please consult octoprint.log for details: SerialException: 'read failed: [Errno 6] Device not configured' @ comm.py:_readline:3831
2021-01-31 22:46:05,262 - Please see https://faq.octoprint.org/serialerror for possible reasons of this.
2021-01-31 22:46:05,265 - Changing monitoring state from "Connecting" to "Offline (Error: SerialException: 'read failed: [Errno 6] Device not configured' @ comm.py:_readline:3831)"
2021-01-31 22:46:05,266 - Connection closed, closing down monitor

For questions related to your printer and not to ADVi3++, please post under “Printers Stuff” category. “Get Help” is only for support about ADVi3++.

Are both computers laptops?

This probably means the printer is rebooting all the time because of you serial problem.

Ah apologies for the wrong categorization.

Yes both computers were laptops.

SOLVED: the problem was the power from the mac going back into the printer. Adding a cheap non-powered USB hub in between the mac and the printer solved the problem.

:tada:

No problem. I just try to keep things organized.

Very interesting. Thanks for sharing.

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