Project

General

Profile

Actions

Bug #4471

closed

Radio not recognized Baofeng UV-5r and UV-5Rv2

Added by Jeff Grey over 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
01/28/2017
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng UV-5 series
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Receiving "radio not recognized" errors on both radios. Using the latest daily build (downloaded today) and the same cable that I have always used. Made sure to re download the proper cable driver from Miklor site.

Using the same programming PC I have always used as well as changing ports and was even able to read my Baofeng UV-82 with no issues with the same set up.

I cannot get any com port to read the UV-5's. I see others have had this issue without resolution. Any ideas?


Files

debug.log (22.6 KB) debug.log Jeff Grey, 01/29/2017 09:45 AM
ProlificDrivers2.jpg (158 KB) ProlificDrivers2.jpg Jim Unroe, 01/31/2017 03:05 AM
Actions #1

Updated by Jim Unroe over 7 years ago

  • Status changed from New to Feedback

Which version of Windows?
What others have this issue(or post to that issue number instead of opening a new one)?
Attach debug.log file.

Jim KC9HI

Actions #2

Updated by Jeff Grey over 7 years ago

Sorry thought I posted version

I am using Windows 7. Previous to this attempt I had no issues with these models.

Previous issue that mentions same is Bug# 4403 though that was using windows 10.

I am away from that PC today but will attempt to attach debug log later.
Thanks....

Actions #3

Updated by Jeff Grey over 7 years ago

  1. What is the behavior you are seeing? - Radio will not read to window 7 pc running latest Chirp build
  2. What is the behavior you were expecting? - Radio should download without issue.
  3. Can you reproduce the problem all the time? - Yes
  4. What are the steps required to reproduce the problem? - Standard steps to connect, read from and store data from HT
  5. Is this specific to a certain radio model (driver) or something that you can reproduce with another radio? - It only happens with the UV-% series. Using the same Chirp build and cable, I can read from at UV-82 with no issues.
Actions #4

Updated by Jim Unroe over 7 years ago

There is nothing CHIRP can do because your radio is not responding to the request to initiate cloning. This is almost always do to an issue with the programming cable (incorrect driver installed, poor connection between the 2-pin plug and radio, incompatible device driver selected to name a few). Until this is corrected, no programming software will work.

Go into Device Manager as shown on the Miklor website. It will show you which chip is in your programming cable and which device driver version is installed. If you have a Prolific chip based programming cable like I do, then you need to download, install and select the older, but compatible, v3.2.0.0 device driver.

Jim

Actions #5

Updated by Jeff Grey over 7 years ago

Thanks for the reply.
Having checked several times (and re downloading)I am using the Prolific driver (7/2007) and thats what shows in device manager. Again, this same cable has no issues when attempting to program my UV-82. It will both read and write to the radio fine. I have also used another uv-5 to no avail.

Actions #6

Updated by Jim Unroe over 7 years ago

Does the factory software work? If not, then you don't have the programming cable fully connected to the radio or the radio's speaker/mic socket has a problem.

Jim

Actions #7

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed
  • Model affected changed from UV-5 series to Baofeng UV-5 series

No more feedback by submitter.

Actions

Also available in: Atom PDF