CHIRP

Recent versions of CHIRP detect the mode (Normal, GMRS, Ham) so that is not the problem. Your system info shows no USB serial ports on your system. You're choosing /dev/cu.debug-console (and others) which is not your radio and that's why it's not connecting. You need to see your radio show up in system info when you plug it in via USB in order for CHIRP to talk to it. That means either your cable is bad, not fully seated, or the radio is not actually doing serial over the USB (some only charge via their USB ports).

See related issue #11578 that indicates that you can use the USB-C on the side of the radio for programming on the TD-H3. That user had a similar behavior as you, and it turned out to be the USB cable. Perhaps these radios are very finicky about the USB-C cable/connector they will support.

Thank you for the quick response. I will look into updating the firmware of the radio. I have tried multiple cables and still no luck, just thought it may have been the updated CHIRP software I had recently installed

On Jan 18, 2025, at 1:44 PM, Dan Smith redmine@chirpmyradio.com wrote:

New firmware is unlikely to do much I think. Note that macOS needs a driver for the USB chip doing the serial transfer, but your USB device list doesn't show anything other than hubs connected to your mac. Even without a driver, it should enumerate there so I suspect a low-level connectivity issue.

Figured it out. New dongle for multi connection apparently needs power to see connected devices. Thanks!

On Jan 18, 2025, at 2:00 PM, Dan Smith redmine@chirpmyradio.com wrote: