Bug #1001
closed
Added by Charlie Duncan almost 11 years ago.
Updated about 10 years ago.
Model affected:
BAOFENG UV-B5
I read the instructions above:
Description
I have a brand new radio (3 days old).
Except for just a couple of times I am now continuously getting "unsupported model" error even after downloading and installing the daily build.
Factory software works just fine.
The UV-B5 has a bug such that when programming software has settings a particular way and they are written to the radio, the 'ident' of the radio is changed. The OEM software either doesn't use the 'ident' or accommodates this change so it isn't affected by it.
Resetting the radio will return the 'ident' back to normal but it wipes out your channels and settings. While investigating this issue over the weekend, a non-destructive way to return the 'ident' back to normal using the OEM software was discovered.
On the Baofeng UV-B5 software's Optional Features menu, set Radio Work Mode(A) and Radio Work Mode(B) to Freq Mode and write the changes to the radio. The radio's 'ident' will be restored and CHIRP will recognize the UV-B5 again.
To keep this from happening in the future...
- Before reading from the radio, set both displays to VFO mode.
- Before writing to the radio (both CHRIP and OEM software), set Radio Work Mode(A) and Radio Work Mode(B) to Freq Mode.
Jim KC9HI
- Status changed from New to Resolved
- Assignee set to Jim Unroe
- Target version set to 0.4.0
- Platform changed from Windows to All
A patch for this has been submitted and applied.
Jim KC9HI
There is one more issue: if VFO is set to CTCS, Chirp will report unknown device too.
Quick fix is just to change VFO to memory channel without CTCS.
If this is true, you will have to be more specific. I just switched to VFO mode and set R-CODE and T-CODE both to a CTCSS tone (lowest and highest) and cloning was successful.
Jim KC9HI
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
Also available in: Atom
PDF