F+* sometimes give a random result when the singal actually have no CTCSS
zhaoparrot opened this issue · 5 comments
I think i may have seen someone talk about this. not sure.
try to test this in the QS v2.01.31_publish.bin . it did not gives me a wrong result but it comes with the annoying scan fail timeout.
the orange radio is TXing with no CTCSS in this video.
petal_20231030_100304.mp4
I have conducted multiple experiments, and sometimes it works fine, continuously scanning when there is no sub-audible tone in the received signal. However, in rare cases, it provides random analog sub-audible tone results when there is no sub-audible tone in the signal. I suspect this issue won't affect many people, as regular individuals typically don't perform sub-audible tone scanning without the presence of sub-audible tones.
this also happens sometime with F+4
also, in F+4 mode scaning , the exit button occasionally doesn't respond promptly. Sometimes, it requires multiple presses before it responds.
I'll find the problem shortly, thank you for letting me know.
I've updated the code threshold levels and fixed the key pad input, let me know if it's still a bit iffy
I conducted some tests, and this feature is working fine now. Thank you so much! I will check your code to see what magic you have performed.