CHIRP

Hi Mike,

Afraid no one has got around to adding settings to this driver yet. I've a WIP version that can set the welcome message but that's not committed yet.

Mike Verdecanna wrote:

Additionally when using chirp to program the channels it erases all the other settings back to factory defaults.

This is unexpected - please could you describe how to reproduce it? If you can include your chirp debug log (see How_to_report_issues) and a before and after image from the radio that would be really helpful.

Thanks

For the price, this is a pretty decent radio. The manufacturer software, though usable, is VERY clunky.

At the very least PLEASE do "Function Setup" and "Key Assignment" (as labeled in the mfgr. software). You will probably cover 95% of users' needs with those 2.
... and thank you.

Mike Verdecanna wrote:

Thank you Joe. You are correct on the unexpected erasing other settings. It is not happening. It must have been when I was also using the factory software (which is horrible compared to Chirp). I found if I load my channels with Chirp to the radio, then use the factory SW to download, then update my general settings in the factory SW, upload back to the radio, then download with Chirp and edit from there it is working.

That's good to know, thanks Mike.

Hi Joe,
I started testing the test driver module. Appears to be working fine. I did notice one item but it may be because it was a setting I didnt use prior. In chirp settings, at the bottom there is a knob mode setting. This seems to control the P6 soft button. When set to channel, P6 gets set to channel and when set to voice P6 gets set to voice. I know you said you were working on key assignment later so maybe that is intended. I will keep testing and let you know any findings. I assume when you do the key assignments you will do both the main unit and mic programmable keys. Nice work and thank you very much!
-Mike KD2UWR

Mike Verdecanna wrote:

Hi Joe,
I started testing the test driver module. Appears to be working fine. I did notice one item but it may be because it was a setting I didnt use prior. In chirp settings, at the bottom there is a knob mode setting. This seems to control the P6 soft button. When set to channel, P6 gets set to channel and when set to voice P6 gets set to voice. I know you said you were working on key assignment later so maybe that is intended. I will keep testing and let you know any findings. I assume when you do the key assignments you will do both the main unit and mic programmable keys. Nice work and thank you very much!
-Mike KD2UWR

Hi Mike,

Jim here. I am the volunteer developer reverse engineering the global settings support.

The CHIRP Knob Mode setting manipulates the same memory bit as the factory software's Knob Mode setting. "0" = Volume and "1" = Channel. What the radio does when this bit is changed is controlled by the radio's firmware and not CHIRP.

Only when the "Knob mode" is set to "Volume" and "Key mode P6" is set to "VOL" is the [P6] key is overridden to "FRQ" and tapping the [P6] key will control the frequency/channel when the knob is turned. If "Key mode P6" is set to any value except "VOL", the [P6] key will be configured as selected by the "Key mode P6" selection and the know will control that feature based on the "Key mode P6" selection.

But thanks for your observation. It is the kind of thoroughness in testing that I am looking for.

Jim KC9HI

Joe Milbourn wrote:

Jim Unroe wrote:

I am looking forward to your feedback.

Well, there's one obvious bug - stick your name up at the top ;)

I had a play around, and I hit this (my _radio_settings.vfomrModeB == 0x04, I've attached the image).
[...]

Cheers
Joe

Thanks Joe. I'm on it.

Jim KC9HI

Jim, MANY thanks. Your work on this is very much appreciated. So far, what I have tested on both modules works well, and I have not experienced any bugs.

Total nit-pick here...
Busy channel lockout: In the mfgr. software, this is assigned to each channel. I don't know if it is possible to make this a global setting. It's something that I do use on select channels, but it is by no means a critical item, and I don't want it to causes spec. creep for what you are working on here (I've written many lines of code and I absolutely hate spec. creep with a passion). If it is not something that can be handled globally, I will open another ticket for it. Again, a total nit-pick and not a show stopper by any means.

I wish I could offer more to this project than just testing, but the learning curve on this would require more time than I have at the moment. Again, thank you for your time and efforts on this.

-BK
KC3QMT
Hopefully changing to KC3RJF soon. It appears that the FCC takes the whole 'working at the speed of government' thing very seriously.

Bobby Kirbos wrote:

Jim, MANY thanks. Your work on this is very much appreciated. So far, what I have tested on both modules works well, and I have not experienced any bugs.

Total nit-pick here...
Busy channel lockout: In the mfgr. software, this is assigned to each channel. I don't know if it is possible to make this a global setting. It's something that I do use on select channels, but it is by no means a critical item, and I don't want it to causes spec. creep for what you are working on here (I've written many lines of code and I absolutely hate spec. creep with a passion). If it is not something that can be handled globally, I will open another ticket for it. Again, a total nit-pick and not a show stopper by any means.

I wish I could offer more to this project than just testing, but the learning curve on this would require more time than I have at the moment. Again, thank you for your time and efforts on this.

-BK
KC3QMT
Hopefully changing to KC3RJF soon. It appears that the FCC takes the whole 'working at the speed of government' thing very seriously.

Hi BK,

BCL appears to not have been implemented in the initial driver release (I believe I also read a comment in the code to that effect). BCL is a per-channel setting. Common per-channel settings can be applied to multiple channels at the same time. For example to disable TX and skip when scanning on all 7 of the NOAA WX Radio channels at the same time...

1. click, shift-click and/or ctrl-click as needed to highlight the 7 channels
2. click the [Properties] button at the top of the "spreadsheet style memory editor" (brings up the "Memory Properties" editor
3. tick the box to the left of "Duplex:" to enable editing and set the value to "off"
4. tick the box to the left of "Skip:" to enable editing and set the value to "S"
5. click the [OK] button

That's it all 7 channels will not transmit if the [PTT] button is pressed and all 7 will be skipped when scanning.

The same could be done to set common CTCSS tone, bandwidths and transmit power levels across multiple channels at the same time.

Unless Joe was planning on adding them, maybe I could take a look at BCL and any of the other "other" type settings when I have finished this project.

Jim

Hi Jim, this is awesome, many thanks. I tried it out and no bugs. Seems to cover every option that is available in the factory software.

Jim Unroe wrote:

Here is the Key Assignment tab which also includes the Function Setup tab. So as of right now, this is the one to test.

Looking good Jim - only found one small niggle, my radio doesn't have lower case letters in the character set so we need to force the welcome message to upper case.

Joe

Joe Milbourn wrote:

Jim Unroe wrote:

Here is the Key Assignment tab which also includes the Function Setup tab. So as of right now, this is the one to test.

Looking good Jim - only found one small niggle, my radio doesn't have lower case letters in the character set so we need to force the welcome message to upper case.

Joe

Joe. This is definitely something I would like to do. Can you offer come ideas on how you can do this? My only solution so far is to have CHIRP notify you that a lower case character is not valid. Thanks.

Jim

Jim Unroe wrote:

Joe Milbourn wrote:

Jim Unroe wrote:

Here is the Key Assignment tab which also includes the Function Setup tab. So as of right now, this is the one to test.

Looking good Jim - only found one small niggle, my radio doesn't have lower case letters in the character set so we need to force the welcome message to upper case.

Joe

Joe. This is definitely something I would like to do. Can you offer come ideas on how you can do this? My only solution so far is to have CHIRP notify you that a lower case character is not valid. Thanks.

Jim

Joe, I figured out something I am happy with. But I would still be OK with seeing something that you would suggest.

Jim

Jim Unroe wrote:

Joe, I figured out something I am happy with. But I would still be OK with seeing something that you would suggest.

You made it into a challenge, that's not fair. How about sub-classing RadioSettingValueString to RadioSettingValueStringUpper and forcing everything to upper case (and the right charset) there? Something like this:

diff --git a/chirp/drivers/anytone778uv_keyassignment.py b/chirp/drivers/anytone778uv.py
index ffee91c..b20f3de 100755
--- a/chrip/drivers/anytone778uv_keyassignment.py
+++ b/chirp/drivers/anytone778uv.py
@@ -595,6 +595,15 @@ def dtcs_code_val_to_bits(code):
     val = chirp_common.ALL_DTCS_CODES.index(code)
     return (val & 0xFF), ((val >> 8) & 0x01)

+class RadioSettingValueStringUpper(RadioSettingValueString):
+    def set_value(self, value):
+        nval = ''
+        for char in value.upper():
+            if char in self._charset:
+                nval += char
+            else:
+                nval += ' '
+        RadioSettingValueString.set_value(self, nval)

 class AnyTone778UVBase(chirp_common.CloneModeRadio,
                        chirp_common.ExperimentalRadio):
@@ -1085,7 +1094,8 @@ class AnyTone778UVBase(chirp_common.CloneModeRadio,
             name += chr(self._memobj.starting_display.line[i])
         name = name.rstrip()  # remove trailing spaces

-        rs = RadioSettingValueString(0, 7, name)
+        rs = RadioSettingValueStringUpper(0, 7, name,
+                                          charset=CHARSET_ASCII_PLUS)
         rset = RadioSetting("starting_display.line", "Starting display", rs)
         function.append(rset)

Joe Milbourn wrote:

Jim Unroe wrote:

Joe, I figured out something I am happy with. But I would still be OK with seeing something that you would suggest.

You made it into a challenge, that's not fair. How about sub-classing RadioSettingValueString to RadioSettingValueStringUpper and forcing everything to upper case (and the right charset) there? Something like this:

[...]

Joe,

That's pretty cool. I've never don't anything like that before. I did try it out. It does work. But I think what I came up with does the same thing with less changes to the code.

Jim

I don't know why I didn't receive the "build test" email, but the patches were accepted and are supported in today's CHIRP daily build.

Jim KC9HI