Project

General

Profile

Actions

Bug #2663

closed

uv-5r not supported by chirp

Added by warren fullerton over 9 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
06/22/2015
Due date:
% Done:

0%

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

Description

I have been having problems connecting my baofeng uv5r to chirp. I have the latest daily build as of today 22/6/15.
Every time i try to connect to chirp i keep getting the error message saying un supported model. radio is version bfb297.
Radio and program lead work with the oem vip software with no issues what so ever.

Actions #1

Updated by JP Bernier over 9 years ago

HI Warren,

I had the same issue for a while. I had previously cloned my 5R's on a Windows Vista laptop, but the laptop died. The cable, the radio, CHIRP, everything worked fine so I knew it wasn't an equipment problem. I replaced my laptop with a Windows 7 (SP1), and could not make the UV-5R clone to save my life. My error code was "Radio refused clone". My solution came from the Miklor website found here: http://www.miklor.com/COM/UV_Drivers.php

The trick was that the new USB cable driver auto installed by Win7 was somehow incompatible with either the cable itself, or CHIRP or something else (??). Anyway, downloading the Miklor driver and replacing the windows default driver solved the problem right away.

I noticed however that after installing the driver, Windows recognized that it was outdated and tried to update it to the one I had just removed -- so make sure you cancel that if you see Windows trying to do that.

Best regards,

JP. Bernier
Cottonwood Heights, UT
KF7QJY

Actions #2

Updated by Jim Unroe over 9 years ago

  • Status changed from New to Feedback

Warren,

Either your radio has a firmware version numbering format that CHIRP doesn't recognize, or it is one of the few radios that left the factory with the 14 bytes that CHIRP uses to identify the radio vendor and model not programmed with data. If it is the latter, there is not much that can be done. If it is the former, CHIRP can be updated to add support to recognize your radio.

Please provide a "debug log":http://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues to this issue to assist with determine which it is.

Jim KC9HI

Actions #3

Updated by Bernhard Hailer almost 5 years ago

  • Status changed from Feedback to Closed
  • Model affected changed from uv5 r to Baofeng UV-5R

No more feedback by submitter.

Actions

Also available in: Atom PDF