Pat, you'll see from my other message that it was a driver issue and I found one that works. But no problem tossing terms like ".plist" at me! I've been a UNIX command-line user for decades, so I'm quite comfortable in the macOS Terminal program. Supposedly the communication drivers are in the /dev directory as .cu and .tty files; I don't know whether they also show up in plists. There's still no sign of the first few drivers I tried to install (if I get around to it I'll grep the system for them), but the one from Repleo (mac-usb-serial.com) is in the /dev directory and working fine.

Patty

----------

On Sunday, January 20, 2019, 10:33:56 AM PST, Pat Anderson <anderson5420@gmail.com> wrote:

The only other thing I can think of is that your cable might not be fully plugged into your radio. I do not think your Mac is "seeing" your radio - if you chose it from the drop-down boxes for Vendor and Model, CHIRP remembers these settings. Until you see a driver in the Port drop down box (other than Bluetooth etc.) there is no way your Mac or CHIRP is "seeing" the radio. I have not gone "down deep" in the Mac for about three years (when I switched to Linux, which has a mutual admiration society with CHIRP) but as I recall the Mac implements the driver through a .plist file, and it has pl2302 in the name.This is probably getting a bit beyond the normal expectations for user interaction on a Mac! Sorry can't be more helpful!