Bug #6417
closedBaofeng UV-3R PLUS Frequency Offset Wrong
0%
Description
If I put the proper number in Chirp editor (eg. 1.6 MHz) the radio wrongly set it to 160 MHz and off course doesn't transmit.
To obtain the proper value I have to write a "wrong", scaled number in the editor: 0.016.
See attached screenshot, with the wrong number in the editor the radio is set-up with the proper one.
Version: daily 20190120
I don't remember such a bug with Baofeng UV-3R (not PLUS) and I don't have such model anymore to test.
Files
| Screenshot.png (243 KB) Screenshot.png | |||
| UV-3R vs. Plus.png (268 KB) UV-3R vs. Plus.png |
Updated by Maurizio Marcovati almost 6 years ago
Updated by Maurizio Marcovati almost 6 years ago
- File UV-3R vs. Plus.png UV-3R vs. Plus.png added
Comparing the .img files from an old UV-3R and a new UV-3R PLUS it's clear (green areas in the picture) what appens.
For an unknown reason, Baofeng shifted the offset data by one byte in the memory map.
There is also an odd number in the same row for each channel; it seems to be the "tx freq", but it's only the sum of "rx freq" and the "offset" taken in the old stile. The number is, of course, totally wrong and the radio seems to ignore it (hopefully) and transmit on the proper offset frequency.
I'm not an expert in pyton, but I hope it's easy to adapt the driver to this "different" variant of UV-3R.
Thanks a lot.
Updated by M T over 5 years ago
Is that captured in https://chirp.danplanet.com/issues/4635#note-4 ? If so, should this be closed as a duplicate of #4635?
Updated by Maurizio Marcovati over 5 years ago
The bug 6417 IS the same of 4635, but note-4 is not yet inserted in CHIRP-daily up to now.
The file uploaded by Jesse Byrd one month ago has been inserted in the daily stream?
CHIRP daily-20190412 still has the bug.
Updated by Yegor Maksimov over 5 years ago
Really, why chirp developers ignore this problem? All latest versions of uv-3r have this bug. It must be fixed in official chirp release!!!
Updated by Dan Smith over 5 years ago
- Status changed from New to Rejected
Yegor Maksimov wrote:
Really, why chirp developers ignore this problem? All latest versions of uv-3r have this bug. It must be fixed in official chirp release!!!
Because we are volunteers. I don't have access to a newer UV-3R, nor do I know anyone that does. Just FYI, demanding a fix from volunteers is not an effective way to get something like this resolved.
Closing this as a duplicate of #4635