CHIRP

Jim Unroe wrote in #note-2:

I have attached the test driver module. Using CHIRP-next, use the instructions found here to test it: LoadingTestModules

It works for me. Let me know how it works for you. And thank you for the report.

Jim KC9HI

it definetely works! thanks i also noticed that there was an update today and that worked without adding the test driver module.

Andrea trk wrote in #note-3:

i also noticed that there was an update today and that worked without adding the test driver module.

This is not correct. Unfortunately CHIRP-next displays the setting how it is supposed to be set, not necessarily what it is currently been set at. This is why I didn't notice the issue right away and why it took me a little bit to come up with a working fix.

So if you don't use the test driver and you make a Tone change (or probably any other change) to a memory row that memory is set to High even though you see Low in CHIRP-next. After you upload the change to the radio, you will notice that when that channel is selected, the "L" icon will not be visible in the lower left of the display. The absence of the "L" icon means the radio's TX power level is (incorrectly) set to "high".

When you edit a memory using the test driver module, the memory row will no long be incorrectly set to High and when you edit any memory row that was incorrectly set to high by an unpatched CHIRP(-next), the test driver module will change the TX power level to the Low setting that it should be.

I will try to submit a patch later today so that it will be permanently fixed in future CHIRP-next builds.

Jim KC9HI