Bug #5575

Baofeng UV-5R - CHIRP does not display Apple FTDI driver in Comm port

Added by Matt Brown about 2 years ago. Updated 27 days ago.

Status:Feedback Start date:02/14/2018
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:Baofeng UV-5R

Description

I have verified that the Apple FTDI driver is installed and working. When I plug the Baofeng UV-5R Programming Cable in under System Report>USB i see the USB-Serial Controller display but when I open CHIRP and try to Download from Radio I do not see the USB-Serial Controller as an option: (See attachment)

CHIRP.jpg (33.8 kB) Matt Brown, 02/14/2018 08:02 am

USB.jpg - System Report>USB (102.2 kB) Matt Brown, 02/14/2018 02:19 pm

History

Updated by Jim Unroe about 2 years ago

  • Status changed from New to Feedback

Matt,

Then it doesn't sound like it is installed and working. Have you used CHIRP successfully other FTDI programming cables? Do you have the prerequisite KK7DS Python runtime for Mac OSX installed?

See the Troubleshooting section of the MacOS_Tips wiki page.

Jim KC9HI

Updated by Matt Brown about 2 years ago

Jim,

Thanks so much for the response.

I did a ls /dev/cu* in the Terminal and this is the result:
/dev/cu.Bluetooth-Incoming-Port /dev/cu.SOC
/dev/cu.MALS

System Report shows (see attached)

Installed KK7DS Python runtime and installed chirp-daily-20180204.app. I have not tried any other FTDI programming cables, just the Baofeng UV-5R programming cable Model:B00CP01474.

Just not sure what else I can do or try. I am a novice by the way, in case it doesn't already show. :)

Matt

Updated by Jim Unroe about 2 years ago

So it look to me like you have a programming cable with a Prolific USB-to-TTL chip. An FTDI driver would be of little use. Most programming cables that report having a Prolific type chip actually have a counterfeit version of the Prolific chip. The latest Prolific driver for OSX is designed to be incompatible with counterfeit Proliric chips.

Jim

Updated by Matt Brown about 2 years ago

Thanks Jim. Any suggestions?

Updated by Bernhard Hailer 27 days ago

  • Subject changed from Boafeng UV-5R - CHIRP does not display Apple FTDI driver in Comm port to Baofeng UV-5R - CHIRP does not display Apple FTDI driver in Comm port
  • Description updated (diff)
  • Target version set to chirp-daily
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to Baofeng UV-5R

The only suggestion would be to use a genuine FTDI cable (yes, it's not cheap). More input here:
CableGuide
CableGuide FTDI OEM Cables
RTSystemsCablesAndMavericks (if you're running MacOS)

Also available in: Atom PDF