Project

General

Profile

Actions

Bug #10672

closed

Baofeng UV-9R PRO Value 16665 not in range 130-179

Added by David Rudd over 1 year ago. Updated 12 months ago.

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

0%

Estimated time:
Chirp Version:
next
Model affected:
Baofeng UV-9R PRO
Platform:
MacOS
I read the instructions above:
Yes

Description

Hello, I have been trying to program my new radio I can change the memories but when ever I click on the settings page I get the error message that "Value 16665 not in range 130-179" I've tried resetting my radio and even tried uploading the settings from my wife's radio to mine but nothing seems to change it. We both have the same model Baofeng UV-9R PRO both with firmware NT5101 Mine gets the message hers does not. I am running the most recent CHIRP next-20230622 on Python 3.8.2 wxPython 4.2.0 osx-cocoa (phoenix) wxWidgets 3.2.0. The attached Baofeng IMG file is the original download from the radio. The David IMG is the one I put on after I set the uploaded from my wife's radio and changed the memories. and the Mia IMG is the one that is on my wife's radio and is working just fine.


Files

Baofeng_UV-9R Pro_20230618.img (8.2 KB) Baofeng_UV-9R Pro_20230618.img David Rudd, 06/25/2023 05:26 PM
David Handheld.img (8.2 KB) David Handheld.img David Rudd, 06/25/2023 05:30 PM
Mia Handheld.img (8.77 KB) Mia Handheld.img David Rudd, 06/25/2023 05:30 PM
Baofeng_UV-9R Pro_20230618(fixed).img (8.2 KB) Baofeng_UV-9R Pro_20230618(fixed).img Jim Unroe, 06/25/2023 07:49 PM
David Handheld(fixed).img (8.2 KB) David Handheld(fixed).img Jim Unroe, 06/25/2023 07:49 PM

Updated by Jim Unroe over 1 year ago

Something has wiped out the band limits on 2 of the images. I have repaired them. Keep an eye on it.

Jim KC9HI

Actions #2

Updated by Fernando Sainz about 1 year ago

David Rudd wrote:

Hello, I have been trying to program my new radio I can change the memories but when ever I click on the settings page I get the error message that "Value 16665 not in range 130-179" I've tried resetting my radio and even tried uploading the settings from my wife's radio to mine but nothing seems to change it. We both have the same model Baofeng UV-9R PRO both with firmware NT5101 Mine gets the message hers does not. I am running the most recent CHIRP next-20230622 on Python 3.8.2 wxPython 4.2.0 osx-cocoa (phoenix) wxWidgets 3.2.0. The attached Baofeng IMG file is the original download from the radio. The David IMG is the one I put on after I set the uploaded from my wife's radio and changed the memories. and the Mia IMG is the one that is on my wife's radio and is working just fine.

Hello. I also got that error when downloading the image from the radio.
I went to the line in the "settings.py" file that gave the error and saw that when it receives a value outside the range it throws an exception and does not continue loading the data.

def set_value(self, value):
    try:
        value = int(value)
    except Exception:
        raise InvalidValueError("An integer is required")
    """ To probe i make this and it continue. them i change values."""
    if value > self._max or value < self._min:
        value = self._min
    if value > self._max or value < self._min:
        raise InvalidValueError("Value %i not in range %i-%i" %
                                (value, self._min, self._max))
    RadioSettingValue.set_value(self, value)

It would be possible instead of throwing an exception to assign a valid value: "self._min" for example and prevent it from continuing.
A warning message could be given so that we were aware that this value must be adjusted.
Greetings.

Actions #3

Updated by Dan Smith about 1 year ago

No, setting self._min in settings.py is not the right thing to do, but the driver should do its own bounds checking and/or catch the exception and do something other than crash.

Actions #4

Updated by Jim Unroe 12 months ago

  • Status changed from New to Closed
  • I read the instructions above set to Yes

I am closing this ticket since the changes made to baofeng_common.py in relation to ticket #10505 should have resolved this issue and prevent it from happening in the future.

Actions

Also available in: Atom PDF