Bug #10134: radio did not respond - CHIRP

Actions

Copy link

Bug #10134

closed

radio did not respond

Added by fred down over 2 years ago. Updated over 2 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

11/24/2022

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

baofeng uv-5r 8w

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Hello
I have UV-5R and I can't connect it to chirp.
First I thought it was because I used a retevis usb cable (wich work fine with retevis). so I bought an official baofeng cable for uv-5r.
I received it with a small size cd in chinese. It seems it contains some driver instalers. I ran a few.
But I always have this message.

I can configure it without chirp but I'd like at least save the configuration.

Thanks for your help

Actions

Copy link

Updated by Jim Unroe over 2 years ago

Status changed from New to Incomplete

If the Retevis programming cable is made with a Prolific type USB-to-Serial chip (very common), then you must download, install and select the older Prolific v3.2.0.0 device driver. The device driver that is automatically installed by Windows does not support this chip any longer.

If the Retevis programming cable is made with a WCH CH340/CH341 USB-to-Serial chip, Windows is known to load the Prolific device driver by mistake. The workaround is to download and install the WCH driver from the chip vendor's website.

See the Miklor "USB Cable Drivers":https://www.miklor.com/COM/UV_Drivers.php page for a links to all the common USB-to-Serial device drivers and instructions for manually selecting the Prolific v3.2.0.0 device driver.

Jim KC9HI

Actions

Copy link