Project

General

Profile

Actions

Bug #2897

closed

Settings blank Baofeng BF-888

Added by Richard Pastrick about 9 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
10/05/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Baofeng BF-888
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Expected behavior:
See settings when clicking on settings tab for my radio

Observed behavior:
Blank area where settings should be

Problem reproduces 100% of the time.

Reproduction steps:

Launch CHIRP

Download from radio

click settings tab and observe no settings

I have tried the following builds:

  • chirp-daily-20150118-installer
  • chirp-daily-20150607-installer
  • chirp-daily-20151005-installer

Problem reproduces on both of my radios. Attached debug.log shows an exception when attempting to get settings.


Files

debug.log (50.9 KB) debug.log debug log showing exception when going to settings tab Richard Pastrick, 10/05/2015 11:30 PM
Blank CHIRP settings.png (11.6 KB) Blank CHIRP settings.png Picture showing blank settings tab Richard Pastrick, 10/05/2015 11:30 PM
CHIRP Browser settings section.png (37.4 KB) CHIRP Browser settings section.png Richard Pastrick, 10/05/2015 11:41 PM
CHIRP Browser settings section2.png (33.8 KB) CHIRP Browser settings section2.png Richard Pastrick, 10/05/2015 11:41 PM

Updated by Richard Pastrick about 9 years ago

Additional images showing the browser tab which shows the read values. The issue appears to be that line 412 of chirp/drivers/h777.py directly uses the voicelanguage value but for some reason it is at 255 which is out of range for the VOICE_LIST list.

Actions #2

Updated by Richard Pastrick about 9 years ago

Similar issue happens on line 431 with (_settings.voxlevel + 1) being out of the 1-5 specified range. I ended up using the browser to program valid values for the items causing the exceptions and then I was able to see the settings.

I guess one solution is to add some bounds checking so these exceptions aren't thrown and the settings page will display even if the values are out of range in some way. Although I guess a try catch would also work. I'm not sure what the more pythonic way to fix it is, otherwise I'd write up a patch.

Second exception here:

[2015-10-05 23:44:40,960] chirp.ui.common - ERROR: Exception running RadioJob: Value 256 not in range 1-5
[2015-10-05 23:44:40,961] chirp.ui.reporting - DEBUG: Reporting exception
[2015-10-05 23:44:40,961] chirp.ui.common - ERROR: -- Exception: --
[2015-10-05 23:44:40,963] chirp.ui.common - ERROR: Traceback (most recent call last):
File "chirp\ui\common.pyo", line 116, in execute
File "chirp\drivers\h777.pyo", line 431, in get_settings
File "chirp\settings.pyo", line 77, in __init
_
File "chirp\settings.pyo", line 86, in set_value
InvalidValueError: Value 256 not in range 1-5

Actions #3

Updated by Bernhard Hailer over 4 years ago

  • Status changed from New to Feedback
  • Target version set to chirp-legacy
  • Model affected changed from BF-888 to Baofeng BF-888

Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?
Remark: this behavior might be caused by some settings in the radio being out-of-range.

Actions #4

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed

No more feedback.

Actions

Also available in: Atom PDF