[chirp_devel] Problem with Out-of-Setting
I have a .img file from a radio that has one of the settings bytes out-of-range. This causes the settings menus to not show up.
The exposed setting is already set to only use bit 1 and bit 0 but this allows 4 values, 0, 1, 2 and 3 but the setting only has 3 choices, 0, 1 and 2.
The radio came from the factory with the byte set to 0xFF. This causes the value to be 3 which is out-of-range.
u8 unknown_flag_17:6, ponmsg:2;
options = ["Off", "Welcome", "V bat"] rs = RadioSetting("ponmsg", "Poweron message", RadioSettingValueList(options,
options[self._memobj.settings.ponmsg])) top.append(rs)
How do I get CHIRP to ignore the out-of-range value or change it to a valid one?
Thanks, Jim
On Sun, Jan 19, 2014 at 10:15 PM, Dan Smith dsmith@danplanet.com wrote:
How do I get CHIRP to ignore the out-of-range value or change it to a valid one?
Make the fourth entry in the list "Off", I'd say:
options = ["Off", "Welcome", "V bat", "Off"]
--Dan
That's too simple. Thanks :)
Jim
On Sun, Jan 19, 2014 at 10:15 PM, Dan Smith dsmith@danplanet.com wrote:
How do I get CHIRP to ignore the out-of-range value or change it to a valid one?
Make the fourth entry in the list "Off", I'd say:
options = ["Off", "Welcome", "V bat", "Off"]
--Dan
Apparently the Powerwerx KG-UV6X doesn't have a PONMSG menu in the radio or the setting their programming software. That is probably why the stuff the byte with 0xFF.
Anyway, if you set the value to 3 and upload it to my KG-UV-6D, then the Power-on Message is the battery voltage. So would it be better to say:
options = ["Off", "Welcome", "V bat", "V bat"]
I suppose another solution would be if PONMSG is equal to 0x99, assume that the radio is the X variant and skip the Power-on Message setting. But I suppose I should find out if the radio honors this setting or not. It could be it does even though the setting is absent in the radio and OEM software.
Jim
Apparently the Powerwerx KG-UV6X doesn't have a PONMSG menu in the radio or the setting their programming software. That is probably why the stuff the byte with 0xFF.
Yeah, so probably skip it entirely if we're on that model so that the user doesn't even see it, right?
--Dan
participants (2)
-
Dan Smith -
Jim Unroe