Mac os x don't use com numbers. You have to use something like ‘ser:devicename', 9600. 5: While entering the serial port name into the code in arduino IDE, enter the whole port address i.e: /dev/cu.usbmodem. or /dev/cu.UG-. where the. is the port number. And for the port number in case of mac just open terminal and type. Knowing the serial port, you can just type screen portname datarate to show the serial data on the screen. In my case, it was: screen /dev/tty.PL23D 9600. To quit the screen app, type control-A, then control. I don't think that this is very complete, but it worked for me and might help you to get your USB serial working. It's possible to know that port is busy (TYPEPORTBUSY) by using TIOCEXCL directive in.nix native library, but using of this directive make some troubles in Solaris OS, that's why TIOCEXCL not used in Solaris (!) Be careful with it. Also Solaris and Mac OS X versions of jSSC not support following events: ERR, TXEMPTY, BREAK.
By default, most Java web application servers are listening on port 8080, and it can easily cause the popular 8080 port conflict error. In Mac OSX, you can use sudo lsof -i :8080 | grep LISTEN to find out what program is listening on port 8080 :
In terminal
Mac os x don't use com numbers. You have to use something like ‘ser:devicename', 9600. 5: While entering the serial port name into the code in arduino IDE, enter the whole port address i.e: /dev/cu.usbmodem. or /dev/cu.UG-. where the. is the port number. And for the port number in case of mac just open terminal and type. Knowing the serial port, you can just type screen portname datarate to show the serial data on the screen. In my case, it was: screen /dev/tty.PL23D 9600. To quit the screen app, type control-A, then control. I don't think that this is very complete, but it worked for me and might help you to get your USB serial working. It's possible to know that port is busy (TYPEPORTBUSY) by using TIOCEXCL directive in.nix native library, but using of this directive make some troubles in Solaris OS, that's why TIOCEXCL not used in Solaris (!) Be careful with it. Also Solaris and Mac OS X versions of jSSC not support following events: ERR, TXEMPTY, BREAK.
By default, most Java web application servers are listening on port 8080, and it can easily cause the popular 8080 port conflict error. In Mac OSX, you can use sudo lsof -i :8080 | grep LISTEN to find out what program is listening on port 8080 :
In terminal
The name 'java' doesn't tell you anything, to get the detail, ps the java PID 12895 like this :
Java Serial Port Mac Os X El Capitan
The Eclipse IDE is using the port 8080.
Java Serial Port Mac Os X 10.13
References
Java Serial Port Mac Os X 10.10
Java Serial Port Mac Os X64
mkyong
Founder of Mkyong.com, love Java and open source stuff. Follow him on Twitter. If you like my tutorials, consider make a donation to these charities.