CHIRP

Is this something you really want/need to be able to control from CHIRP? If so, then we can add it, but just because there's a bit in memory that isn't exposed in the settings doesn't necessarily mean we need to plumb it through.

Can you explain why this is important/useful?

If it is needed for the radio to be set to B, then all that needs to be done is set the radio to B and then download from the radio to CHIRP. The value will be stored in unknown2. Any uploads back to the radio will set the selection to B. It isn't worth the effort to implement a setting in the CHIRP U/I.

No, I don't need to control it from CHIRP and yes, I do know that I can set / download / edit / upload.

I just made the assumption that you were writing drivers to be feature complete and thus provided additional information for that purpose.

Thanks Peter. I didn't meant to sound unappreciative, I was just trying to zero in on the request. My bias against exposing all the runtime state bits was obviously showing :)

How about I change the driver to properly annotate the field you found so that it's at least mapped correctly, so that it's documented for the future if nothing else? That should be easy given the work you did to suss it out.

Thanks!