[chirp_devel] Call for help

[Dominick C. Pastore]

I tried the VX-6R. Downloading, changing a memory, and uploading works. I'm having trouble with the banks and settings though.

For the banks:

I can download them from the radio, add and remove memories from banks, and upload to the radio, but the UI in this tab is a bit glitchy. For one thing, it's very sluggish, especially when scrolling. But also, when trying to add a memory to a bank, it doesn't actually show the checkmark until clicking on another cell in the table (unchecking is slightly slow but otherwise works normally). Lastly, in the py2 release, there's an extra tab to change the bank names. Not sure if it's on purpose, but that tab is missing in the py3 build, and there doesn't seem to be another way to change the names.

For the settings tab:

This one is completely broken for me, raising an exception (see below) and leaving the tab blank. But I tried it in the py2 release and it's broken there too, so it doesn't seem to be a regression. It's possible this exception may be my fault. It's been quite a while since I've done anything with this radio in CHIRP, but I could have sworn the settings page used to work. I do know that I later spent some time trying to reverse engineer some of the settings missing from CHIRP, so I'm wondering if I may have corrupted the image a little.

Here are the exceptions from the settings tab in the py3 branch:

Traceback (most recent call last):
  File "/home/dominickpastore/chirp/chirp/drivers/vx6.py", line 823, in get_settings
    return self._get_settings()
  File "/home/dominickpastore/chirp/chirp/drivers/vx6.py", line 640, in _get_settings
    val = RadioSettingValueString(0, 16,
  File "/home/dominickpastore/chirp/chirp/settings.py", line 215, in __init__
    self.set_value(current)
  File "/home/dominickpastore/chirp/chirp/settings.py", line 229, in set_value
    raise InvalidValueError("Value contains invalid " +
chirp.settings.InvalidValueError: Value contains invalid character `'

ERROR: Context raised unexpected_exception
Traceback (most recent call last):
  File "/home/dominickpastore/chirp/chirp/wxui/settingsedit.py", line 49, in _initialize
    self._load_settings()
  File "/home/dominickpastore/chirp/chirp/wxui/settingsedit.py", line 59, in _load_settings
    for group in self._settings:
TypeError: 'NoneType' object is not iterable
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/wx/core.py", line 3285, in <lambda>
    lambda event: event.callable(*event.args, **event.kw) )
  File "/home/dominickpastore/chirp/chirp/wxui/settingsedit.py", line 49, in _initialize
    self._load_settings()
  File "/home/dominickpastore/chirp/chirp/wxui/settingsedit.py", line 59, in _load_settings
    for group in self._settings:
TypeError: 'NoneType' object is not iterable

And here are the exceptions from the settings tab in the py2 build:

Traceback (most recent call last):
  File "/app/lib/python2.7/site-packages/chirp/drivers/vx6.py", line 823, in get_settings
    return self._get_settings()
  File "/app/lib/python2.7/site-packages/chirp/drivers/vx6.py", line 642, in _get_settings
    _settings.arts_cwid_alpha))
  File "/app/lib/python2.7/site-packages/chirp/settings.py", line 212, in __init__
    self.set_value(current)
  File "/app/lib/python2.7/site-packages/chirp/settings.py", line 227, in set_value
    "character `%s'" % char)
InvalidValueError: Value contains invalid character `'

Traceback (most recent call last):
  File "/app/lib/python2.7/site-packages/chirp/ui/settingsedit.py", line 220, in _build_ui
    raise Exception("Invalid Radio Settings")
Exception: Invalid Radio Settings


On Fri, Dec 9, 2022, at 7:14 PM, Dan Smith via chirp_devel wrote:
>> That's cool, a VX-6 would be good to knock off the list, and I think it's likely to "just work" because it shares a lot in common with the other radios in that vintage (VX-7, VX-8, etc). That said, I haven't actually tested those since 2019, so I should re-do that just to be sure. I'll try to do that today, but will look forward to your report about the VX-6.
>
> I confirmed that my VX-7 and VX-8DR radios are still good, so I suspect 
> your VX-6 will be no problem.
>
> Also, this morning I scraped some data out of our error reports and 
> added a "Market Share" column to the testing matrix, which gives us an 
> idea of which radios are the most important to get tested.
>
> https://github.com/kk7ds/chirp/blob/py3/tests/Python3_Driver_Testing.md
>
> Luckily, we've got all the major ones already, and even though only 53% 
> of models have been tested as working, that represents 77% of the share 
> of chirp users, which is pretty good. Interestingly, the VX-6 is oddly 
> popular amongst its siblings:
>
> Yaesu_VX-3   0.08%
> Yaesu_VX-5   0.07%
> Yaesu_VX-6   0.16%
> Yaesu_VX-7   0.09%
> Yaesu_VX-8DR 0.03%
>
> Still tiny compared to the almighty UV-5R, but going strong compared to peers.
>
> I'm also thinking of marking all the Kenwood live radios as implied 
> tested, as these are almost all the same code, and being string-based, 
> pretty solid. That will increase our numbers a bit more. After the 
> initial conversion, I've not encountered any problems with any of those 
> that I've tried.
>
> I think starting to push users to the newer builds (especially if 
> they're on platforms like Linux and MacOS that desperately need a 
> modern platform) when 80% of them will be supported is pretty 
> reasonable.
>
> --Dan
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers