CHIRP

Yeah, the UV17Pro driver does not expose airband, but the UV17ProGPS model does, as well as several other siblings. Your image shows that you do indeed have a base UV17Pro, which chirp thinks does not support air band at all. If that's wrong, can you program an airband frequency into one channel manually with the radio, download and image with chirp and attach here? If it's just a matter of telling the base driver that airband is okay, it's a simple fix.

I will do more testing during the day tomorrow, but the first try looks like it works!  I'll let you know more tomorrow afternoon my time.  I'm Mountain Standard Time (not Daylight time) or -7 hours from GMT.

Dennis, N7NTM

"A life is like a garden. Perfect moments can be had, but not preserved, except in memory." -Leonard Nimoy

Sent from Yahoo Mail on PC

On Tuesday, September 24, 2024 at 02:36:55 PM MST, Dan Smith redmine@chirpmyradio.com wrote:

Okay thanks. I'm going to go ahead and merge this because it's pretty straightforward assuming it works at all, but always good to get plenty of confirmation.

I'm planning to do another build soon, so feedback by tomorrow afternoon will be okay and I'll shoot for a build Thursday. Just comment on this (soon to be closed) bug with any feedback.

Good early afternoon Dan,
I have a couple of questions regarding the patch.
1.  Whenever I start up CHIRP, do I need to reload the patch from the issue number every time?  It wouldn't work for me this morning until I loaded the patch again.
2.  Doesn't the Air Band also use the 136.000 MHz frequency?  When I put that one in for a test, it informed me that the modulation must be FM and not AM.
Here are a couple of comments.
1.  I tested the band edges and was able to enter 108.000 and 136.000.
2.  After entering the first few Air Band frequencies, the note regarding that the frequency must be in AM, got annoying.  I really don't have a recommendation on that one without having you add a temporary flag to temporarily turn off the message. 
3.  The upload and download looks like it is working very well.  I don't know if it is my newer laptop computer, or if some programming changes have been made, but the upload and download seems to be quicker than older radios
Thank you for the quick turn around on this.  :)
Dennis, N7NTM

"A life is like a garden. Perfect moments can be had, but not preserved, except in memory." -Leonard Nimoy

Sent from Yahoo Mail on PC

On Tuesday, September 24, 2024 at 08:21:34 PM MST, Dan Smith redmine@chirpmyradio.com wrote:

1.  Whenever I start up CHIRP, do I need to reload the patch from the issue number every time?  It wouldn't work for me this morning until I loaded the patch again.

Yes (per note 1 on LoadingTestModules) until it's included in a regular build.

2.  Doesn't the Air Band also use the 136.000 MHz frequency? 

Depends on what the radio does. The FM-only versions of this model define the lower bound for VHF to be 136.000MHz, obviously FM. I would hope the AM-capable variants don't change that. However, CHIRP isn't actually in control of the AM- or FM-ness of a channel, which is why it's so difficult to get this to work properly for these kinds of radios that infer the mode from the frequency. Most of the radios that implicitly support AM like this were revisions of an original one that did not, and I think they're just hacking in AM support, inferring it by band so they don't have to make any other changes. That's frustrating for CHIRP, which of course, expects that if you support AM, we can actually control when and where it's used.

If you tell me that manually entering 136.000MHz into the radio gives you AM and 136.001MHz gives you FM, then I'll need to change it. Otherwise, since CHIRP is just mirroring the radio's behavior, we don't have a choice.

Here are a couple of comments.
1.  I tested the band edges and was able to enter 108.000 and 136.000.
2.  After entering the first few Air Band frequencies, the note regarding that the frequency must be in AM, got annoying.  I really don't have a recommendation on that one without having you add a temporary flag to temporarily turn off the message. 

It is indeed annoying (to me). However, I've had other users say they like it, and rather need it to not get confused when they try to set it to something and it just flips back (try changing a 144MHz channel to AM - without the warning, it looks like it is "not working"). Unfortunately, these ultra-low-cost radios do a lot of weird stuff like this that runs counter to kinda general good practice. In order for the device-agnostic GUI to handle all the devices and their quirks, some of this is necessary. The warning coming back from the radio is actually part of the signaling that tells the GUI not to consider the mode change to be an error. I can do some thinking about how I might allow that to be squelched temporarily, but it's not something the users of most higher-quality radios have to worry about so it's a tradeoff.

One workaround is just File->New, punch them all in there quickly and then copy/paste them in.

3.  The upload and download looks like it is working very well.  I don't know if it is my newer laptop computer, or if some programming changes have been made, but the upload and download seems to be quicker than older radios

That's definitely not related to the module or the change :)

I just tried the radio in VFO mode, and the AM area is only from 108.00000 to 135.99750 MHz.  So, I would say that it is good to go.
Thank you for your help, and for letting me test for you.  :)

Dennis Betz, N7NTM

"A life is like a garden. Perfect moments can be had, but not preserved, except in memory." -Leonard Nimoy

Sent from Yahoo Mail on Android

On Wed, Sep 25, 2024 at 15:20, Dan Smithredmine@chirpmyradio.com wrote:

I figured as much :)

Thanks for your help as well. The other users of this radio will, of course, appreciate it as well.