At the end it doesn’t matter if you have a result with 325, 327 or 317 aircraft in the script. That’s no evidence about proper gain setting, just a clue about the right path.
I would rely more on that > 3dBFS thing and the range provided by the graphs. Everything in between should be fine.
I’ve got my antenna on the roof and have connected it down into the house using about 25 feet of RG-6 (75 Ohm) TV/Cable coax, and then I have a TypeF/SMA adapter to connect to the ADSB Dongle. Based on other posts here (and elsewhere on web) it seemed like the impedance mismatch when the cable reached dongle and changed from 75 Ohm to 50 Ohm wasn’t a big concern - as long as it’s in a Rx situation (for Tx the reflected energy is large enough to cause issues). It didn’t occur to me there’s also a potential for a mismatch at the start of the cable, where the antenna plugs in.
So given my current set up, I think it would make (technical) sense to have the antenna impedance match the 75 Ohm cable, and I should bend the radials down to 90 degrees. However, I’m not sure it it make practical sense to do that - it loses the ground plane (doesn’t it?) and if one 50-75 Ohm interface isn’t a huge deal, would two make a big difference?
@abcd567 how are you calculating the antenna impedance - is that coming out of 4nec2?
Finally - I feel like this very interesting, valuable thread has morphed into about 3 or 4 conversations. Is there some method or protocol to “fork” it? I almost “replied” here by starting a new thread (“Antenna Impedance and Gain Predictions”, or some such) and linking back to the last relevant post in this thread, but I wasn’t sure if that “good form” or not for the forum.
Also, as I mentioned earlier, if you are feeding FlightAware while running the tests, the MLAT sync will be lost. Maybe should stop piaware while running the tests? sudo systemctl stop piaware
No, I meant while the script is running, should you stop piaware? The script does a restart of dump1090-fa after each gain change. This causes problems for the mlat-client.