Arduino() doesn't find port on MacOS

Question

Arduino() doesn't find port on MacOS

jckantor opened this issue 7 years ago · comments

@APMonitor I'm testing with MacOS X (High Sierra) and Python 3.6 (Anaconda distribution). serial.tools.list_ports.comports() doesn't return a list of active ports, therefore Arduino.findport() fails.

One fix, not pretty, would be an optional argument to Arduino() to specify a port. If a port was specified, then findPort() wouldn't need to be called. The placeholder is already there, just need to modify the logic in init

Carl Sandrock · Answer 1 · Tue Jan 09 2018 15:34:47 GMT+0800 (China Standard Time)

I had issues with the drivers on my computer, solved by installing these drivers.

APMonitor · Answer 2 · Tue Jan 09 2018 17:36:15 GMT+0800 (China Standard Time)

Thanks for pointing to these drivers for MacOS. I've included a number of other initial setup and configuration tips here http://apmonitor.com/pdc/index.php/Main/ArduinoSetup

APMonitor · Answer 3 · Tue Feb 20 2018 10:10:02 GMT+0800 (China Standard Time)

One user reported that they don't want to install an additional driver on MacOS, citing a concern about the source of the driver. This user said that they overcame the driver issue by connecting a Raspberry Pi (Linux) to control the device. I suppose this is an option but still not optimal for MacOS users. The Windows and Linux experience seems much easier with respect to drivers. Any additional thoughts on this issue? Should the Hduino Uno be replaced with a different version for MacOS users to help with the driver issue?

Carl Sandrock · Answer 4 · Tue Feb 20 2018 15:08:59 GMT+0800 (China Standard Time)

I don't see any reason to doubt the validity of the drivers we link to in the README. They work perfectly for all the students and myself who use them with the Mac. I've had much more problems with Windows users with my units. It appears that the real problem is not so much the platform as the specific chips (CH34x).

Jeffrey Kantor · Answer 5 · Tue Feb 20 2018 20:36:38 GMT+0800 (China Standard Time)

I've been having good luck with the Leonardo which doesn't require a new driver for the Mac. The only issue is that Leonardo creates a new com port on each invocation of TCLab. So I agree with Carl, that the Mac with CH34x driver is actually the more consistently reliable platform. We only had a couple of macs (out of perhaps 40 or so) with stubborn problems. For those we substituted Leonardos as a fix. The hard problems have been recalcitrant Windows machines that, for some reason, just don't want to connect. Our experience is that if we can connect with the Arduino IDE then we're good to go with the TC lab. We have a few that just haven't worked. It's hard to identify a particular pattern to the problem. The NHduino is definitely faster than Leonardo. We get about 40 samples per second on NHduino vs 12-15 with Leonardo using the TCLab-sketch. I haven't benchmarked Firmata and am curious how that would compare. John ... we'll finish the substitution of Leonardos for NHDuinos over Spring break, and the unused units back to you. Jeff

…

On Tue, Feb 20, 2018 at 2:09 AM Carl Sandrock ***@***.***> wrote: I don't see any reason to doubt the validity of the drivers we link to in the README. They work perfectly for all the students and myself who use them with the Mac. I've had much more problems with Windows users with my units. It appears that the real problem is not so much the platform as the specific chips (CH34x). — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADGCC2b3O2vTsuv09W6V-jnOrvbdKJ-Mks5tWm-NgaJpZM4Pouhb> .

APMonitor · Answer 6 · Fri Apr 24 2020 09:05:03 GMT+0800 (China Standard Time)

We switched to Arduino Leonardos to resolve the driver concern. The TCLab now works on Linux, MacOS, and Windows without driver issues.