After shorten the center tube I could tune the filter to 1090MHz.
I’ve installed a 10db attenuator and after set “Relative” on Spektrum I got -2.6db @ 1089.6Mhz
Would be interesting to see the inside of your box and how you are assembling/holding it all together.
It appears to be copper?
Though I see you have some steel looking bolt heads - are those isolated from touching the copper? If they are nickel or chromed you should be ok. If not you will get a galvanic reaction over time.
Handy chart I use for reference when working with mixed metals:
@mikkyo the rods and the tuning screws are made with brass and the big screws are stainless steel. The inicial plan was to hold the rods using the screws, but due to poor thread in the rod they were soldered and the screws aren’t properly tight.
@geckoVN apparently what is happening is that the filter is having a higher loss with weak signals (I wish it was the other way ).
Not sure if this is related with poor construction and I also don’t know how strong is the noise generator signal compared with a real ADSB signal.
One thing I’ve already concluded, even with it’s poor construction I’m getting better results (more aircraft and messages) than without filters. Near my site and in line of view (500m) have probably 8 cell towers and at 1.5km there’s a cluster of antennas (sorry but right now the sky isn’t clear to post a real picture)
As i did not have that many to do today i made made again a few non-representative tests with my primary receiver, Antenna outdoor.
I am using the blue ProPlus Stick with the Jetvision Antenna.
For that i’ve installed the dark blue FA filter (1090MHz) for testing purposes again.
See the comments in the graphs what was done when.
As stated, not representative as it is my individual environment but it looks that there is no filter required here for further improvement. This can be of course totally different for other users.
The graphs are looking the same as the days before with the typical ups and downs over the day. Maybe someone else wants to do the same trial.
python scripts cannot be excecuted directly.
You need to run it with the command “python” in front of it. It’s a processor based language, not an excecutable file
This is not correct. Look up “shebang”. Scripts designed to be run directly start with a line indicating the interpreter to use. The problem here is that the interpreter can’t be found; there is a lot of disagreement between distributions about what the python interpreter should called (is it python2, python2.7, python3, python3.8, or just “python” and does that refer to a python 2 or python 3 interpreter?)
Try editing the script and change “python” to “python2” (I guess that it’s a python 2 script, anyway) in the first line. You may need to explicitly install python2 if it’s not already there as wiedehopf suggests
).
