ScnRev CARRIER does not always stop for the required time

[tehmha]

I regularly have a problem with the ScnRev CARRIER option. I set it to 10 seconds. Most of the time it works, but sometimes the scan detects something, my speaker opens, but the scan starts again very quickly (less than a second). And if I press the M button, then it does indeed go back to the last channel on which there was a signal (the one that activated only a second before the scan resumed).

It also happens that the scan stops on a channel that is receiving a signal. Reception is discontinuous, and the scan restarts after 10 seconds while reception continues (with interruptions).

[armel]

Hello,

Thank you for your message and the detailed description of the issue.

I've run multiple tests today to try and reproduce the behavior you're seeing, but without success. Everything seems to be working as expected on my side, and I haven’t noticed any such anomaly so far.

Are you able to reproduce this issue consistently on your end?

I’ll keep this issue open in case other users can confirm, invalidate, or provide additional insights.

Armel, F4HWN.

[DanielGekeler]

While I cannot reproduce this issue, I did encounter it as well. It is triggered by a very short pulsed signal.
Sometimes I hear a short sound on the speaker and sometimes the green LED just lights up and the scan continues after a fraction of a second without hearing anything.

[armel]

Ok, I take note of that.
Now, it’s difficult for me to fix a problem that I can’t reproduce and therefore can’t understand and analyze.

[yesilug]

This may be because it receives a DMR signal. It does not stop at signals whose tone does not match.

[armel]

Hello,

I don’t have a DMR radio on hand to run the test, but it’s definitely an interesting lead to explore.

Armel, F4HWN.

[DanielGekeler]

I did encounter this issue a few more time since I last commented here. It was on the frequencies of FM relays and it was just a very short pulse. Since a DMR signal is digital, there probably are some pulses that could trigger this as well. It might be possible to reproduce this by quickly pressing the PTT on another radio for a time less than 200ms, shorter is better.

Could this be caused by a race condition due to the way the interrupt works?