Bug #8539
closedBaofeng_BF-F8HP does not display anything in settings
100%
Description
With my brand new Baofeng UV-5R with 3 power levels, I attempted to download an image from the radio as if it was a Baofeng BF-F8HP. This was done on my Linux Mint 20 using the latest available chirp-daily-20201128.flatpak. (I would have preferred to use the Ubuntu ppa.launchpad.net/dansmith/chirp-snapshots/ubuntu but I just get "Unable to locate package chirp-daily"). After the download, the Chirp "Memories" tab shows the pre-programmed channels, but the Chirp "Settings" tab is just blank. There was no log file found, but the output on my terminal contained the following:
ERROR: Failed to parse settings: Traceback (most recent call last):
File "/app/lib/python2.7/site-packages/chirp/drivers/uv5r.py", line 1686, in get_settings
return self._get_settings()
File "/app/lib/python2.7/site-packages/chirp/drivers/uv5r.py", line 1494, in _get_settings
TXPOWER3_LIST[_vfoa.txpower3]))
IndexError: list index out of range
Traceback (most recent call last):
File "/app/lib/python2.7/site-packages/chirp/ui/settingsedit.py", line 219, in _build_ui
raise Exception("Invalid Radio Settings")
Exception: Invalid Radio Settings
If I chose instead to download the image as if the radio is a Baofeng UV-5R, then the settings are successfully downloaded, but I have only 2 power levels.
I also have a slightly older Baofeng UV-5R with 3 power levels, and Chirp successfully downloads both memories and settings for this slightly older radio using the Baofeng_BF-F8HP profile. So this suggests that Baofeng has changed something in this newest 3-power UV-5R that Chirp does not yet accommodate.
Files
Updated by Curtis Fast almost 4 years ago
I just noticed the suggestion in Bug#8519 to set different power levels in VFO mode before attempting to download from the radio. I set both the VFO A and B lines to low power, and then successfully downloaded the image -- including the settings!
Updated by Jim Unroe almost 4 years ago
- Status changed from New to Resolved
Thanks for the follow up. Good you hear you have it resolved. Have fun with your radio.
Jim KC9HI
Updated by Curtis Fast almost 4 years ago
Isn't this still a bug that could be fixed? I'm just successfully using a workaround...
Updated by Jim Unroe almost 4 years ago
It is a bug in the radio. It had a setting that was out-of-range. By you setting it to a new value using the radio's keypad, you changed the setting to a valid one. The problem was with the radio, not CHIRP.
Jim KC9HI
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Resolved to Closed
- Platform changed from Linux to All
Updated by Jim Unroe almost 4 years ago
- Status changed from Closed to In Progress
- Assignee set to Jim Unroe
- Target version set to chirp-legacy
- % Done changed from 0 to 100
Patch submitted to force out-of-range TXP values in the VFOs to a valid values.
Jim KC9HI
Updated by Jim Unroe almost 4 years ago
- Status changed from In Progress to Resolved
Updated by Anonymous almost 4 years ago
- Status changed from Resolved to Closed
Applied in changeset commit:f31d24275923.