Bug #11010
openBaofeng UV-5R+ Settings chirp.settings.InvalidValueError: Value 255 not in range 0-123
0%
Description
UV-5R+, optional features loads fine with Baofeng VIP v120725 BFB291 (BF5R_VIP_v120725_BFB291_ENG(VB6).zip) from https://www.miklor.com/UV5R/UV5R-Software.php
but chirp is failing to parse it
I might have written the img from a UV-5R with different firmware version to this UV-5R+, but why would chirp fail on parsing settings while Baofeng VIP doesn't have this problem?
[2023-12-13 06:42:23,340] chirp.wxui.main - INFO: Saved backup to C:\Users\user\AppData\Roaming\CHIRP\backups\Baofeng_UV-5R_20231213T064223.img
[2023-12-13 06:43:51,416] chirp.drivers.uv5r - ERROR: Failed to parse settings: Traceback (most recent call last):
File "chirp\drivers\uv5r.py", line 1799, in get_settings
File "chirp\drivers\uv5r.py", line 1790, in get_settings
File "chirp\settings.py", line 99, in __init_
File "chirp\settings.py", line 107, in set_value
chirp.settings.InvalidValueError: Value 255 not in range 0-123[2023-12-13 06:43:51,417] chirp.wxui.common - ERROR: Context raised unexpected_exception
Traceback (most recent call last):
File "chirp\wxui\settingsedit.py", line 51, in _initialize
File "chirp\wxui\settingsedit.py", line 81, in _load_settings
TypeError: 'NoneType' object is not iterable
Traceback (most recent call last):
File "wx\core.py", line 3427, in
File "chirp\wxui\settingsedit.py", line 51, in _initialize
File "chirp\wxui\settingsedit.py", line 81, in _load_settings
TypeError: 'NoneType' object is not iterable
Files
Updated by Sam Fisher 5 months ago
I forgot to backup this UV-5R+'s (poweron shows BFB298 / 191031M) img before uploading the other UV-5R's (power on shows BFB298 / 210223M) img
did not get any warning / error when I programmed the same img to multiple radios (my mistake), but most of them now show different string with poweron + 6 than what is in img's 0x1818
Updated by Sam Fisher 5 months ago
at this point I am not even sure which firmware I should use from https://kc9hi.dyndns.org/uv5r/programming/CHIRPrecovery/ to get the radio back into a known state, since the information is img could be wrong (because I upload img from 1 radio to another)?
Updated by Jim Unroe 5 months ago
- File Baofeng_UV-5R_20231213T064223(added_service_settings).img Baofeng_UV-5R_20231213T064223(added_service_settings).img added
Because the VIP software doesn't know about, care about or support the service settings. Your radio was either missing those settings or the VIP software removed them.
I have added some stock values from another image.
Updated by Sam Fisher 5 months ago
Thanks so much. This img did fix the settings issue.
a few questions about aux data
- can Chirp populate missing aux data with defaults automatically / or simply leaving them empty while still show other settings?
- firmware_msg / sixpoweron_msg is grayed out in UI as a safety mechanism? but the value does get overwritten if img is uploaded to other radios, and then there is no way to tell what firmware the radio is actually on? I thought there are some additional safeguards in the radio / chirp to prevent overwriting these fields?
- what is line2 for firmware_msg / sixpoweron_msg? the field is 8-byte (8 characters) in img, where does line2 come from (empty for both in my case)?
- the value of poweron+3 / 6 is not anywhere in img, is the expected?