where is the mistake ?
As far as I know, it still works with SDR# 1811.
I don't use that version of SDR#.
The PDF is (still) apart of the archive which is available in the link below.
The version of the Frequency Scanner available here (in this thread) is not the same as the one in the community installer.
This version has many improvements over that one.
As far as I know, it still works with SDR# 1811.
I don't use that version of SDR#.
Latest version (v2.2.8.0) can be found here: MEGA - Download
Thank you very much for that straight-forward explanation of where to find this article. I was surprised even with your clear instructions of how long it took me to extract that PDF, as I have never worked with a 7 Zip archive before. I kept using a regular zip extractor, with no results. I finally threw in the towel, and downloaded the 7 zip, and finally figured out how to work it and got the PDF. Thanks!View attachment 102790
Click on Frequency_Scanner
Right Click on frequency_scanner_v2.2.8.0.7z
Download awayView attachment 102791
Unzip with 7-Zip
View attachment 102792
Download WinRAR that handles all formats incl 7-zip. That's the only program I use to compress and decompress files and have never failed.I finally threw in the towel, and downloaded the 7 zip, and finally figured out how to work it and got the PDF.
The MilAir crowd love using Airspy with the scanner as they can scan the entire MirAir band in 2-3 secs.
Yes; the milair band is what I am trying to scan. It does scan the entire band, but nowhere near 2-3 seconds. I'll try playing with the "Detect" settings.
BTW I have RTL dongles, as well as Airspy and Airspy mini. I am currently trying with the Airspy mini.
Thanks for the clarification, I didn't realize there were two versions. I'll see if I can delete that post. of mine.This thread is for the updated version of the Frequency Scanner plug-in and not the outdated version that is in the community package.
Linking that video is just bad advice for setting up and using this version of the Frequency Scanner plug-in which has many different options compared to the outdated one.
The use of the community package is not recommended as:
- Most of the plug-ins are outdated and for earlier versions of SDR# (pre v1717). They may still work with newer SDR# versions but don't look right because of the different UI/themes SDR# now uses.
- Gives (new) users the impression that they can install as many (outdated) plug-ins as they like and does not make the user aware that doing so will cause problems.
Latest version (v2.2.8.0) can be found here: MEGA - Download
Why do you need to manage the lockouts externally to the running plug-in?Thanks a lot for your plugin.
I am facing with the task of menaging the list of prohibited frequencies that are stored in the "scanner_entryes.xml" file using a third-party application. But as I understand it, this file is read only once when the application is launched, and then it is rewritten during the process. That is, any changes made from outside will be ignored and will be taken into account only after a restart (in case that they was not rewritten at all).
Could you add the ability to periodically re-read "scanner_entryes.xml" and apply changes while Frequency Scanner is running? Something like the "Reset noise floor" option with a choice of period.
Why do you need to manage the lockouts externally to the running plug-in?
What requirements do you need to manage the lockouts via the plug-in that it currently doesn't have.
I don't see any reason to add complexity to the loading/usage of the "scanner_entryes.xml" for a one off random "third-party application".
Latest version (v2.2.8.0) can be found here: MEGA - Download