Using RTL-SDR for MilAir

[Jonnywithacamera]

I am having issues with my RTL-SDR V4 to monitor from 225-400mhz. I am pairing it with SDR# 1921 and the FMSuite plugin. My issue is the scan is very slow and often doesn’t pick up things I know are causing chatter. I have it set for -50 minimum signal strength and 3 seconds wait to resume. I’m wondering if my issue is the software/scanner settings or if I need to upgrade to something like an Airspy R2

 

[reconrider8]

My first thoughts are whats the performance on the computer? And the r2 does speed it way up

 

[Jonnywithacamera]

My first thoughts are whats the performance on the computer? And the r2 does speed it way up

I’m not a computer guy so bear with me. 16gb RAM 6400 MT/s. Processor says Intel(R) Core(TM) Ultra 5 125U. I’m wondering if I don’t have my SDR# setup properly or if the RTL-SDR just isn’t what I had in mind and need the R2 instead.

 

[reconrider8]

What scan speeds are you getting? And while its running pull task manager up and see how the performance looks and make sure nothing is maxing out

 

[Jonnywithacamera]

What scan speeds are you getting? And while its running pull task manager up and see how the performance looks and make sure nothing is maxing out

225-400mhz in 9-10 seconds and my CPU runs around 25% and memory around 50%. Really what I need to find out from you and anyone else who knows better than me is do I have my SDR# running poorly or do I need to buy an airspy. Another issue I have is the scanner isn’t working correctly like at my airport the ATIS (350.3) I know is chattering 24/7 but it won’t stop on it during the scan. I have a good antenna which is supposed to be able to hear aircraft far away but I’m having problems getting even local stuff during the scan

 

[RichM]

I had similar performance that you describe scanning MilAir with an RTLSDR V3, around 8-9 seconds for 220-380Mhz scan and missing some traffic. I switched to an Airspy Mini and now get around a 2 second scan and much better sensitivity.

I should add I’m using the Fast Scanner plug-in with a much older version of SDR# V1700. I also use an old laptop w/windows 7 and it works very well despite having rather primitive performance specs. I turn the waterfall off to save on CPU usage. The main thing I‘ve learned is you need to try different older versions of SDR# until you find one that works with your set up and the fast scanner plug in. I never was able to get SDR# V1900+ to work.

Here is a link to the archive of all the older versions Index of /software/SDRSharp. Spend some time downloading the 1700-1800 versions until you find something stable that works with your hardware. And make sure and use the Fast Scanner plug-in, it is the best tool for the job.

My plug in settings are: detect @40 & wait @ 0.5. Test it on civilian air to make sure it’s working, it should chatter nearly non stop in that band. Unfortunately SDR’s are not plug and play, they require a fair amount of experimentation because of individual and situational variances. Hope this helps, good luck.

 

[reconrider8]

225-400mhz in 9-10 seconds and my CPU runs around 25% and memory around 50%. Really what I need to find out from you and anyone else who knows better than me is do I have my SDR# running poorly or do I need to buy an airspy. Another issue I have is the scanner isn’t working correctly like at my airport the ATIS (350.3) I know is chattering 24/7 but it won’t stop on it during the scan. I have a good antenna which is supposed to be able to hear aircraft far away but I’m having problems getting even local stuff during the scan

Yea computer side sounds ok. I would grab an r2 and try it out. That's what I run and if everything is right mine will run 1.5-1.6 seconds. Something is going on with my laptop atm so it only runs like 3.5 seconds and I've yet to figure out exactly whats going on lol but it works just not quite as fast as it used to be. I run 2 r2s for different stuff but they are a beast

 

[gary123]

You may also find the SDR is not as sensitive as a scanner will be.

Also set the SDR so it is not trying to decode any plugin or data formats. Mil stuff is mostly AM and having the software look for DMR/P25 etc will slow it down even more.

 

[Jonnywithacamera]

I had similar performance that you describe scanning MilAir with an RTLSDR V3, around 8-9 seconds for 220-380Mhz scan and missing some traffic. I switched to an Airspy Mini and now get around a 2 second scan and much better sensitivity.

I should add I’m using the Fast Scanner plug-in with a much older version of SDR# V1700. I also use an old laptop w/windows 7 and it works very well despite having rather primitive performance specs. I turn the waterfall off to save on CPU usage. The main thing I‘ve learned is you need to try different older versions of SDR# until you find one that works with your set up and the fast scanner plug in. I never was able to get SDR# V1900+ to work.

Here is a link to the archive of all the older versions Index of /software/SDRSharp. Spend some time downloading the 1700-1800 versions until you find something stable that works with your hardware. And make sure and use the Fast Scanner plug-in, it is the best tool for the job.

My plug in settings are: detect @40 & wait @ 0.5. Test it on civilian air to make sure it’s working, it should chatter nearly non stop in that band. Unfortunately SDR’s are not plug and play, they require a fair amount of experimentation because of individual and situational variances. Hope this helps, good luck.

Do you know if the FMSuite plugin with the newer version of SDR# is good with the Airspy SDR’s? If it works just as well, the issue will definitely my RTL-SDR and that I need to upgrade to the Airspy

I had similar performance that you describe scanning MilAir with an RTLSDR V3, around 8-9 seconds for 220-380Mhz scan and missing some traffic. I switched to an Airspy Mini and now get around a 2 second scan and much better sensitivity.

I should add I’m using the Fast Scanner plug-in with a much older version of SDR# V1700. I also use an old laptop w/windows 7 and it works very well despite having rather primitive performance specs. I turn the waterfall off to save on CPU usage. The main thing I‘ve learned is you need to try different older versions of SDR# until you find one that works with your set up and the fast scanner plug in. I never was able to get SDR# V1900+ to work.

Here is a link to the archive of all the older versions Index of /software/SDRSharp. Spend some time downloading the 1700-1800 versions until you find something stable that works with your hardware. And make sure and use the Fast Scanner plug-in, it is the best tool for the job.

My plug in settings are: detect @40 & wait @ 0.5. Test it on civilian air to make sure it’s working, it should chatter nearly non stop in that band. Unfortunately SDR’s are not plug and play, they require a fair amount of experimentation because of individual and situational variances. Hope this helps, good luck.

another issue I have is the older versions of SDR# can’t seem to pick up any frequencies even intentionally set ones. The new version of SDR# is the only one I can get working but it has the FMSuite scanner plugin because it’s new and it does scan around 9-10 seconds rather than 2-3

 

[reconrider8]

If you havnt i would grab the community pack since it already has the most used pluggins pre-installed including the one for searching

 

[Jonnywithacamera]

If you havnt i would grab the community pack since it already has the most used pluggins pre-installed including the one for searching

Where is that located ?

 

[reconrider8]

I'll dm you. Its what I used to get my stuff up and running

 

[dave3825]

I use an older sdr with fast scanner. I will time it later and see how long for 225 to 380 and report back.

 

[reconrider8]

I use an older sdr with fast scanner. I will time it later and see how long for 225 to 380 and report back.

Mine is 3.1 seconds atm from 225-380 with an r2. Normally if everything is right it runs at 1.5-1.6 seconds and I rarely miss a thing in fact you can kind of hear multiple conversations depending on how long they are between transmissions and such

 

[RichM]

Do you know if the FMSuite plugin with the newer version of SDR# is good with the Airspy SDR’s? If it works just as well, the issue will definitely my RTL-SDR and that I need to upgrade to the Airspy

another issue I have is the older versions of SDR# can’t seem to pick up any frequencies even intentionally set ones. The new version of SDR# is the only one I can get working but it has the FMSuite scanner plugin because it’s new and it does scan around 9-10 seconds rather than 2-3

As I said I have never been successful with V1900+ so I can’t speak on that or the FM Suite plug in. I can say unequivocally that the Airspy Mini is more sensitive and better performing than the RTL-SDR V3, nearly on par with my hardware scanners. I should also add I have never tried the RTLSDR V4 but the specs are clearly not as good as an Airspy, lower sample rate, bandwidth etc.

What antenna and length and type of coax are you using? MilAir demands a good outdoor antenna with decent coax. Test your set up on a NOAA weather channel for your area and also civilian air. These are easy signals and if you’re having trouble with them you‘ll need to figure out why - perhaps RF interference, software settings or hardware or a combination of these or even all 3. Sorry I can’t be of more assistance, best of luck in your quest.