Bug #6071
closedFTDI software disabled - Mac OS (High Sierra 10.13.6)
0%
Description
Hello all,
I'm having difficulty with the BaoFeng BF-F8HP radio connecting to CHIRP software. Zero issues with BF-F8HP and genuine FTDI cable connecting to Windows 10.
On a Mac running High Sierra (10.13.6), latest CHIRP daily and what I presume to be the latest Python runtime, I get: 'An error has occurred. Radio did not respond'.
PC03 FTDI Dual Pin Cable - genuine cable from BaoFeng Tech (BTech) connected to a Mac Mini 4.1 - (I know, old school. but it works!)
Vendor ID: 0x0403 (Future Technology Devices International Limited)
Version: 6.00
Serial Number: A107HJ5A
Speed: Up to 12 Mb/sec
Manufacturer: FTDI
Location ID: 0x04100000 / 2
Current Available (mA): 500
Current Required (mA): 90
Mac System Information reports the FTDI cable as an FT232R USB UART
CHIRP/Python version info:
GTK 2.24.10
PyGTK 2.22.0
Python 2.7.2
I keep seeing the UV-5R driver mentioned throughout the debug log. The BF-F8HP is genuine and purchased from BaoFeng Tech.
Examples from debug log:
[2018-08-28 09:32:41,066] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
DEBUG: Reporting model usage: Baofeng_BF-F8HP,download,True
[2018-08-28 09:32:37,737] chirp.ui.mainapp - DEBUG: User selected Baofeng BF-F8HP on port /dev/cu.usbserial-A107HJ5A
[2018-08-28 09:32:37,755] chirp.ui.clone - DEBUG: Clone thread started
[2018-08-28 09:32:37,765] chirp.drivers.uv5r - INFO: Sending Magic: 000: 50 bb ff 20 12 07 25 00 P.....%.
[2018-08-28 09:32:37,972] chirp.drivers.uv5r - DEBUG: '\x00'
[2018-08-28 09:32:37,972] chirp.drivers.uv5r - ERROR: uv5r._ident_radio: Radio did not respond
Why is CHIRP looking for UV-5R drivers?
The cable is definitely trying to communicate with the BF-F8HP. During cloning attempts, the beacon or flashlight on top of the radio blinks once, and the display appears to show all icons and number blocks displayed in a dot-matrix pattern,
similar to when powering on the radio. The backlight also illuminates when attempting to clone.
Anyone with a Mac running High Sierra 10.13.6 feel free to chime in. This one has me stumped.
Updated by Rick W over 6 years ago
Figured it out, CHIRP is now communicating with my BF-F8HP!
In my case, it ended up being a simple command issued through Terminal and some changes made in Network. More info below.
The FT232R USB UART should not show up in System Preference > Network, otherwise it will see the cable as a PPP connection and treat it as such. Remove it from the list, but answer 'Yes' to the prompt to see the device again, then reboot. Do not add the cable to the list.
"An ownership or permissions problem is preventing the system from making the device accessible. Check that the driver is owned by root and wheel. The most common symptom is the group for FTDIUSBSerialDriver is not wheel.
To change the group, login as root and perform the following script in a Terminal window (Go > Applications > Utilities > Terminal):
cd /system/library/extensions
chgrp -R wheel FTDIUSBSerialDriver.kext
Reboot for the change to take effect".
https://discussions.apple.com/thread/7656357 - many thanks to the author of this thread.
I spent way too much time trying to figure this out. I will admit I know more about Windows OS than Mac OS, but I'm starting to slowly figure it out.
Hope this helps someone out if they're experiencing the same problem.
Updated by Bernhard Hailer over 4 years ago
- Status changed from New to Closed
- Target version set to chirp-legacy
- Chirp Version changed from 0.4.0 to daily
- Model affected changed from BF-F8HP to Baofeng BF-F8HP
Resolved by submitter.