Jeff,

When I get this message it is one of two problems:

The first is I go between steps (Menus) to fast. I slow down and give about 5 to 10 seconds between steps. and the radio programing works.

or

I do not have the cable pushed in far enough. What I do then is push the cable into the radio quite hard and while still holding the cable and radio run the progaming (Make sure not transmit at the same time).

I do not know if that is the problem you are having, the these ”fixes” work for me.

N7IY, Peter

----- Peter J. McClosky, N7IY Eugene, Oregon pmcclosky@earthlink.net n7iy@arrl.net http://home.earthlink.net/~pmcclosky/

On May 29, 2017, at 7:22 PM, Jeff Davis kf5hqe.jeff@gmail.com wrote:

Hi Folks,

I’m running a MacBook Pro using OS 10.12.5. I’ve received three different radios along with USB to BaoFang connection cables.

When I open Chrip, the Mac OS systems report shows the USB port and the device so the Mac Sees it.

But when I run the Radio/Download from Radio command, I get the <Screen Shot 2017-05-29 at 9.18.23 PM.png>

Any ideas? I’ve tried all three cables and tried it with this radio as well as two UV-5R’s, same results.

Thank you in advance.

Jeff Davis KF5HQE

---

chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Peter at pmcclosky@earthlink.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com

On Mon, May 29, 2017 at 10:22 PM, Jeff Davis kf5hqe.jeff@gmail.com wrote:

Hi Folks,

I’m running a MacBook Pro using OS 10.12.5. I’ve received three different radios along with USB to BaoFang connection cables.

When I open Chrip, the Mac OS systems report shows the USB port and the device so the Mac Sees it.

But when I run the Radio/Download from Radio command, I get the

Any ideas? I’ve tried all three cables and tried it with this radio as well as two UV-5R’s, same results.

Thank you in advance.

Jeff Davis KF5HQE

You don't have a working connection between the radio and computer. This is most likely caused by your programming cable is manufactured with a counterfeit Prolific chip (nearly 100% of the Proliric type chips in programming cables are counterfeit). The Prolific written drivers since about 2008 have been intentionally incompatible with these counterfeit chips.

Windows user can download, install and select an older driver (from 2007) that was available before Prolific decided to do something about the unauthorized copies of their chips. This workaround isn't available for a Mac.

I've read where this third party device driver has solved the issue from some Mac users.

https://www.mac-usb-serial.com/

Switching to a programming cable with an FTDI chip is and even better solution because it will work with the native Apple FTDI driver. Here is one of many sources for such a programming cable.

https://www.amazon.com/gp/product/B00HUB0ONK/

Jim