Jim Unroe wrote in #note-5:
Amazing. I believe that I just figured it out and I come here to get the ticket number for the commit message and I see that you figured out half of it!
if tone == 0xC000 or tone == 0xffff:
Nice. That makes sense and works perfectly!
Thank you!
An update regarding the supported modes/supported tones:
Cross in "Tone" mode; 67.0; 254,1 (and quansheng vice versa) - results in the radio indicating tones are on (I was missing the cross mode setting yesterday), and the quansheng reveiving and transmitting to the RB615 both with same settings. Without tones set in the quansheng it receives from the rb615 but the rb615 does not receive from the quansheng, which is how it is supposed to be I guess. So selecting "tone" seems to translate into a valid setting, that is correctly shown by the radio after all, even in the settings (ct50/ct1).
Regarding the "56.0" to "64.0" Tones/TSQL, I cannot select those tones on the quansheng to cross test. But testing it with the other RB615 show the following.
- When selecting 56.0 as TX tone. Radio indicates tone in display (even though it only shows "ctn5" in settings again). But the Radio only transmits half of the time alternating on and of twice a second, evectively rendering the tx useless, this is only heard when monitoring though, since the rx radio doesnt recognise the 56.0 tone at all.
- 57.0 works fine with rx and tx. (Radio indicates tone, but only ctn5 in settings)
- 64.0 works fine with rx and tx. (Radio indicates tone, but only ctn5 in settings)
So it seems only the 56.0 Tone is unsupported in the end. I cannot find anything in the documentation how to limit the squelch tones range. So I guess, if you dont have a quick fix at hand, we might consider it a hardware/software bug in the radio itself (maybe the reason the official software doesnt support this tone set/range after all) and leave everything as it is, since it is really not that much of an issue tbh.
Last but not least, a huge thank you from my side for all your help, work and tinkering on this!
The Driver was hardly usable two days ago and now works perfectly fine and that painful stock software has never to be used again by nobody.
