The Final Filter Shootout

Thinking about this overnight.

TomMuc has identified the filters which take out unwanted frequencies the best.

However, don’t we also need to collect parameters like aircraft reported, coverage, positions reported by distance etc for each of the filters.
I have a homemade coax stub filter which removes all the frequencies in the 920 - 960Mhz but also removes most of the 1090Mhz frequency too!

I haven’t been following all the threads regarding filters so please forgive me if this has already been done.

@triggers this is what i did too but what is not really easy to display the results. you can’t measure this with a single setup over long time as traffic, routes, weather, atmospheric things etc. change over time. range plots like vrs does are worth nothing especially over long time and/or mlat using. ads-b is not like astronomy or ham radio about distance records - it’s again worth nothing to sometimes pick up single or very few or bogus signals from far away. ads-b is about to pick up maximum numbers of messages over a maximum area.

there are two ways that work - to see what results in live ads-b mode different filters and lnas give. the first is very complex - using the same antenna, a splitter and behind that the different filter/lna/dongle/raspi setups. the problem here is to just exactly compensate the splitter loss and channel differences. then you have to find two dongles, cables with exact same behavior. and even then one dongle could interact with the other. i did all this for some filter/lna combinations - but it is really extremely time-consuming and still has lot room for wrong results.

what gives me by far the best results and is very fast. just use one receiver and antenna on different times of the day. run one setup for about 1-2 minutes and then another. doing this like a ko-system and repeatedly you get a very good overview what works best at your site. some of the results cannot be generalized but some can absolutely.

that said - my results in real ads-b numbers exactly match the seen results in the above band-scans. what can be generalized is:

  • it’s always the second best idea to combine two filters
  • an ideal filter has very low insertion loss and huge attenuation over a large frequency-band
  • the nearer noise-frequeny is to ads-b the bigger the challenge for filter/receiver
  • a filter in front of lna is better than behind but must have very very low insertion loss

=> from all filters i ever tested the jetvision 3-pole has by far the best overall performance
=> the by far best bang for the buck delivers the uputronics saw-filter/lna combo
=> the 10$ generic chinese dongle is an unbelievable good sdr

cheers
tom

1 Like

.
http://alignment.hep.brandeis.edu/Lab/Filter/Filter.html

added a new scan-set to top-post that contains the uputronics wideband lna without filter …

@triggers
please do not overrate this! but here are two vrs-range plots both over about 1-2 weeks not simultaneously. the first is uputronics saw/lna and the second is jetvision 3-pole filter/lna. as i often mentioned - this is something you should not really compare in detail - but the trend is obvious …

lna → saw-filter below:

lna → 3-pole-filter below:

1 Like

another parameter one have to keep in mind is that different filters have different passband (1090mhz) attenuation. so you maybe have to adapt the gain setting of dongle too. there are some scripts around here in the forum that automize this - but i’m not a friend of this method and in my testings often showed wrong results.

the easiest way to see what gain works best is to watch skyview for about 1-2 minutes → then alter the gain setting and again look on skyview for message-rate, aircraft numbers with/without position, aircraft pattern on map, highest aircraft distances and age of messages.

to change the gain setting in dump1090-mutability simply use the two below lines:

sudo sed -i -e 's/GAIN=".*"/GAIN="48.0"/g' /etc/default/dump1090-mutability
sudo /etc/init.d/dump1090-mutability force-reload

possible gain values are:

0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 agc

if you want to look into config file use:

sudo nano /etc/default/dump1090-mutability

to see actual dump1090 status:

sudo /etc/init.d/dump1090-mutability status | more

A quarter wave stub shouldn’t remove “most of the 1090Mhz frequency too”. The insertion loss in the pass-band should be quite low.
What type of coax did you use to make the filter?
and exactly how long did you make the stub?

@geckoVN why didn’t you plot some graphs with and without your stub and share it here? and/or other filters you use and/or your ferrite rings etc …

btw. here are two pictures from my tinker-lab. first shows what happens if one is too dumb to desolder a saw filter - the second shows inside of the minicircuits 2-way splitter zapd-2dc+

Been meaning to ask you how you setup rtl_power. My first attempt failed miserably and I haven’t got back to it.

The ferrites I used offer nothing at UHF. Some ferrites using Mix 61 could improve performance, but not the ones I have.

.

The rtl_power scan on Windows: Click here

install needed software:

sudo apt-get update
sudo apt-get install git build-essential cmake libusb-1.0-0-dev python-imaging
git clone https://github.com/keenerd/rtl-sdr.git
mkdir rtl-sdr/build
cd rtl-sdr/build
cmake ..
make rtl_power
wget https://raw.githubusercontent.com/keenerd/rtl-sdr-misc/master/heatmap/heatmap.py
chmod +x heatmap.py

now anything you need is installed and you can e.g. do those two scans:

sudo killall dump1090-mutability
./src/rtl_power -f 800M:1400M:300K -i 10 -c 50% -g 50 -e 20m -F 9 >scan_800_1400.csv
./src/rtl_power -f 24M:1700M:1M -i 10 -c 50% -g 50 -e 40m -F 9 >scan_24_1700.csv

when both scans are done - plot the graphs:

./heatmap.py scan_800_1400.csv scan_800_1400.png
./heatmap.py scan_24_1700.csv scan_24_1700.png

that’s it :slight_smile:

Thanks guys.
I’ll have another go and report.

1 Like

I used unknown manufacturer coax but the VF is 0.66. I used a “T” in the feedline. The distance from the centre of the “T” to the end of the open ended stub is 53mm. I started with a 60mm stub and gradually chopped bits off & re-ran rtl_power.
This is my raw data

This is with the 53mm stub

However, when I insert the stub the messages dropped from 880/sec to 710/sec and the plane count from 142 to 106. I also lost some of the distant planes too. Gain is 49.6

Antenna is a homebrew 8 element Coax Collinear located in the loft with approx 6m of coax with Flightaware Pro (Orange) dongle This is my test setup.

Any comments appreciated.

That could be your problem: An open 1/4 λ stub is a band-stop or notch filter which would certainly explain your poor performance (A shorted 1/4 λ stub operates as a band-pass filter)
If you need to avoid a DC short (you are using a bias-T etc.) then you need to use a 1/2 λ open stub to give you a band-pass filter.

There is so much variation in coax spec/performance that you may be setting yourself up for problems by guessing.
A Vf of 0.66 suggests you are using RG59 rather than RG6 which typically has a Vf around 0.82 (Belden does list an RG6 with Vf of 0.66 out of the 61 RG6 variants it offers).
If your coax does have a Vf of 0.66, than λ/4 should be around 45mm.

One thing to be careful of when using RG59 with type-F connectors is that the centre conductor is much slimmer than that of RG6, so may not make reliable contact particularly if the connector has been previously used with RG6.

@geckoVN - many thanks for your comments.
I know very little about filters etc. My thinking went along the lines of
I need to get rid of the frequencies at 920 - 960Mhz. 1/4 λ of 940Mhz is 79.8mm. I know the VF of my coax is 0.66 so stub length should be 53mm

I take your point about the diameter of the centre conductor. I’ll measure mine this afternoon.

When I get something working, I’ll have a go at this to eliminate the “T” http://dl4xav.sysve.de/coax.filter/step.3.jpg
image

[Edit] added this link http://www.hb9amo.net/img/sketch.jpg

Ah! I’d misunderstood what you were trying to achieve (or rather, how you are trying to achieve it).

I looked at Volker’s T-joint. It’s very neat, but is being used on a 146MHz transmitter to remove the third harmonic (70cm amateur band).
Replicating it precisely to be suitable for 1090 MHz will have it’s own set of problems. Continuing with a three-way adapter is certainly easier and probably more reliable.

@geckoVN but what about finally some facts a.k.a. frequency scans?

but already amped? the 920/960mhz and 1090mhz band looks so loud …

No external amp. Flightaware Orange dongle and gain set to 49.6