Bug #3217
closedBaofeng 70cm freqs report as out of range
0%
Description
Baofeng UV-5R 70cm frequency's report as out of supported range.
Using Beofeng Software versoin BFB297
Files
| debug.log (27.1 KB) debug.log | Debug log | ||
| uv5r_new_fr_unlock2016v2.img (6.32 KB) uv5r_new_fr_unlock2016v2.img | image file | ||
| beofeng.png (210 KB) beofeng.png | OEM vip shows in vhf/uhf | ||
| beofeng2.png (136 KB) beofeng2.png | Image of error |
Updated by Tom Hayward over 8 years ago
- Status changed from New to Feedback
Cannot reproduce. Please see how to report issues.
Updated by Chris Svendsen over 8 years ago
Used the OEM VIP software and everything works fine with the OEM software.
Updated by Nick oe over 8 years ago
Which exact version of chirp are you using?
What platform?
What are the exact steps to reproduce your issue?
Updated by Chris Svendsen over 8 years ago
Chirp chirp-daily-20160116-installer.exe
On windows 10
Steps taken:
Download image from Baofeng UV-5R enter a frequency in the 70cm range and an alert box opens stating frequency is out of range and clears the frequency entered.
The frequency I was trying to enter was RX 442.6000 TX 447.6000 but I tried several different 70cm frequencies with the same result alert box "out or freq range"
Updated by Tom Hayward over 8 years ago
Please attach the two files requested in how to report issues.
Updated by Jim Unroe over 8 years ago
Chris,
The byte that CHIRP uses to determine if the radio is a VHF/UHF model of VHF/220 is set to the VHF/220 model. You can use the OEM VIP software to correct this.
Jim KC9HI
Updated by Chris Svendsen over 8 years ago
- File debug.log debug.log added
- File uv5r_new_fr_unlock2016v2.img uv5r_new_fr_unlock2016v2.img added
- File beofeng.png beofeng.png added
Updated by Chris Svendsen over 8 years ago
Thanks Jim I checked it out in oem vip and i believe from the image above beofeng.png it shows in vhf/uhf mode.
Updated by Chris Svendsen over 8 years ago
Ok think i figured it out i had expended the freq range in settings i think this is what caused the error because when i set it back i no longer get the error.
Updated by Bernhard Hailer about 4 years ago
- Status changed from Feedback to Closed
- Priority changed from High to Normal
Appears to be resolved.