I looked at this again after sleeping on it. I will have to understand when I can modify valid_bands in order to change this to honor the current setting. If they don't overlap I don't have that problem. I'll play with this now.
On Sun, Nov 3, 2024 at 12:08 PM Michael K Johnson mcdanlj@gmail.com wrote:
Oh, yeah, I was sure it's something in the driver. Was reading other code to try to understand what in the driver it might be, because I don't understand all the details of the interface contacts in my first day looking at it. 😅
As you have time I'll appreciate whatever attention you can provide to it. I'm sure it's something simple that I missed...
Thanks!
On Sun, Nov 3, 2024, 10:34 Dan Smith via Developers < developers@lists.chirpmyradio.com> wrote:
No matter what I try, I can neither enter nor paste an Offset or Duplex
for a 1.25m repeater. Programming 1.25m repeaters was ultimately what was motivating me to do this work.
Even if I just unconditionally add 220-225Mhz to _txbands and comment
out my special handling of being sensitive to the current 52.200TX setting for testing, if I type "1.6" in the Offset column or - in the Duplex column, it silently goes away without printing an error. It works fine for 2m and 70cm bands. I've looked through chirp_common.py and I haven't been enlightened. I'd love a pointer to where I could next look to fix this.
That'd be something in the driver. I've got a busier day today but I'll try to look at your PR tonight or tomorrow and keep an eye out for what might be going on.
--Dan _______________________________________________ Developers mailing list -- developers@lists.chirpmyradio.com To unsubscribe send an email to developers-leave@lists.chirpmyradio.com