Beofeng Cable Driver Mac

  1. Usb Driver For Baofeng Cable
  2. Baofeng Cable Driver Mac Os

Plug and play with latest windows and mac systems! Driver supplied on cd-rom for windows 98/me/2000, windows xp, windows vista, windows7. Usb programming cable, 44 3/8 112.7cm requires baofeng usb cable driver and programming software, works with baofeng uv-5r, uv-82, uv-b6 and bf-f9 dual band amateur radios. I did not load any drivers, Windows actually did its job and took care of it for me. In minutes, I was programming a variety of Baofeng and Wouxun radios. My strong recommendation at this point is to use the Chirp software and get a FTDI-based programming cable. You will be a much happier Baofeng or Wouxun owner. We re going to serial driver. As soon as i can borrow a windows pc, i will give it a go. Original baofeng 1 pin usb programming cable for baofeng bf-t8 bf-u9 uv-3r mini walkie talkie ham two way radio feature, this item is the cable that using to connect your radio and pc, then writes the program setting and frequency of the walkie-talkie by pc.

How to Fix FTDI Driver Issue on Mac and macOS

Ongoing macOS FTDI driver issues plague many users connecting the Arduino IDE to boards that use an FTDI chip. Since our boards use an FTDI chip for USB-to-serial communication, we have witnessed some of these issues when working with our boards using Mac and macOS.

The symptoms we have observed generally include the spontaneous loss of the USB serial port connection to the board or loss of the port after disconnecting and then reconnecting the board from the USB programming cable.

Rebooting the system can temporarily restore the port, but the problem eventually comes back. Since we’ve seen this issue pop up internally and with many customers, we decided to share what solution has been working for us so far.

The exact cause of this problem is not certain, but it seems to be related to Apple’s support, or lack thereof, for FTDI drivers in the operating system. Earlier versions of Mac OS X did not support FTDI drivers, so users would have to install third-party FTDI drivers. Somewhere around the release of macOS 10.12 Sierra (and maybe earlier), native support for FTDI drivers was included.

So, if you have followed an upgrade path from an older version of the OS without native FTDI support to a new version that has it, there can be contention between the native and third-party drivers. This potentially leads to the mysterious port disappearance issue.

We have found uninstalling the third-party drivers to be a solution. The instructions below have seemed to work for anyone here at Alorium Technology that was observing the FTDI issues.

Instructions

  1. To uninstall FTDI drivers you must be logged on to your computer as a root user. Follow Apple’s directions if this needs to be enabled on your computer.
    • Be careful! By enabling root, you have privileges to change and delete files that are required by your computer.
  2. Follow steps 4.1 and 4.2 in FTDI Chip’s “FTDI Driver Installation Guide” to uninstall all third-party drivers on your computer.
  3. Disable root on your computer. Follow Apple’s directions below.
  4. Reboot your system

Want More Info?

Join our mailing list to stay in the loop with the latest news regarding Alorium products and other interesting things we are doing. Your email will not be shared, and we won't pester you very often!

Posted by8 years ago
Archived

I wanted to write this post, as I went through many trials and tribulations to get Mac OS X to program my Baofeng uv-5r radio using CHIRP and the USB cable. I am happy to report success! Success was not easy, and the path to success was a test of my patience. I am hoping that this post will help someone that struggled just as I did.

Usb Driver For Baofeng Cable

For the record, this process worked for both my Mac Mini running OS 10.8.5 and my Macbook Air running OS 10.9.1.

My USB cable was purchased on Amazon and has Baofeng written right on the cable. It looks like it came from the same factory as the radio. So I had tried the “genuine” driver first. That driver produced an error in CHIRP. Next I installed the “counterfeit” driver and that did not work either. I tried a few other drivers, and none seemed to work. After a few hours, I was at my wits end!

Baofeng Cable Driver Mac Os

As I was installing each of the different drivers, I was not removing the previous one that I had installed. Instructions to remove drivers are much more difficult to find across the interwebs! After much consternation and frustration, I realized that the “counterfeit” driver was the correct driver. However, the “genuine” driver that I had installed before the “counterfeit” driver, was conflicting with the “counterfeit” driver, and preventing the “counterfeit” driver from working properly.

There are many instructions out there for installing the drivers. So I won’t go through how to do that, since it may vary with the driver you are installing. Some of them require command line to install, others are offered in a *.pkg file so they can be installed graphically. I will give you the instructions to remove the drivers and my instructions require the command line. If you don’t know which is the correct driver to use with your cable, install one, test, then remove it if it does not work. Don’t install the next driver for testing, until the previous driver is removed. Installing and removing device drivers in Mac OS X is not that easy, but not that difficult either.

Here is my disclaimer: These instructions will utilize commands from the command line. Using the commands that I give you, it is possible to completely mess up OS X. Make certain that you have good backup before proceeding. Be prepared to do a complete re-install of your entire system. It’s not likely to happen if you are careful. But it can happen. You have been warned.

No matter what method you used to install a driver for the USB 2303 chipset, a kext file is placed in the following path: /System/Library/Extensions You must delete the kext file to remove the driver. I had three different drivers installed, each of them had a different file name. To remove the drivers: open a command prompt and change to the appropriate directory.

cd /System/Library/Extensions

See if you have any existing 2303 drivers installed:

ls grep 2303

This will output a list of any .kext files that have 2303 in the name. All the various drivers that I tried to install, all of them had 2303 in the filename. There were no critical system files on my system that have 2303 in the name. I can give you a command to delete all of these files, all at one time, but I would not recommend that! I would carefully delete each of kext files individually, one at a time. Type the following to delete one of the files:

sudo rm -r name.of.the.file.to.delete.kext

Beofeng Cable Driver MacBeofeng Cable Driver Mac

If you want to remove one driver that you think is offending, you can just remove that kext only, and then test your radio. If you have quite a few drivers installed and you wish to start fresh, delete all of them with 2303 in the name, one at at time. Do not delete any of the other files in this directory. Deleting the wrong file could cause you major problems.

After you get all the drivers ripped out, reinstall each of them, one at a time. Test the driver. If it does not work then go back and follow my instructions to remove it. Then you can try another, then remove it. Keep going until you find which one works. Here is a link to the “counterfeit” driver and instructions that made my cable work:

Of course, this will only work if you have the exact same cable as I do, with the exact same chipset. This is the driver for the counterfeit and/or generic cables.

When you install CHIRP, make sure to install python as well. The details are well documented on the CHIRP website. Programing with CHIRP is so much more simple then using the clunky menu system, plus you can add names to your channels. It’s very nice!

TL;DR make sure to remove 2303 drivers from OS X, before installing the next one when trying to figure out which driver is the correct driver. Two drivers can conflict and cause the correct driver not to work.

EDIT: fixxed Speeling errrors.

21 comments