Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-block Peaks that do not have a valid sonde decode after X decodes #946

Open
darksidelemm opened this issue Nov 24, 2024 · 2 comments
Open

Comments

@darksidelemm
Copy link
Member

An idea from Zigi's fork of auto_rx (which has other geographic-specific features which will not be added into auto_rx for various reasons...).

If a peak shows up in the scan result more than X times in a row, with no valid sonde detection, add it to the temporary block list (which locks out that peak for 2 hours by default). This should help with reducing scan time on 'birdies' or other non-radiosonde signals that are always present.

The value for X will need to be tuned to avoid sondes that might just be starting to become decodable to be locked out.

@darksidelemm
Copy link
Member Author

The other issue we see is non-radiosonde signals (in my case, trunked radio network channel) being detected as iMet sondes, and auto_rx starting up a decoder. The above approach wouldn't lock these out.

I guess we could also add something in that temporarily locks out a frequency if it's been detected as an iMet, but has timed out multiple times?

@helioshk
Copy link

Or make dft_detect smarter, so it can recognize unmodulated tones or trunked radio?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants