Will do. Also on the antenna side I am planing an upgrade.
I had the same challenge before i moved. There i had the antenna in the attic. For testing i put it outside the house and had surprisingly the same reception. Seem to be that the roof didnāt block signal that much.
Make sure you keep the cable as short as possible and use a good one.
Now with the 1090 uputronics there is quite some improvement. Next step is to optimize the airspy_adsb parameters and for this I would appreciate if someone could elaborate a bit more on them because ā-hā only shows some minimal info. E.g. how quickly is āauto gainā reacting? What is the difference between RMS and SNR mode? Is there no documentation available?
Another important question is how critical the max. temp of 40 degrees is as in typical setup this might be difficult to achieve, even with an attached fan in a closed outside box.
https://github.com/wiedehopf/airspy-conf
That is the extent of the documentation.
There is tons of discussion in this thread but itās hard to search.
autogain reacts very quickly but iād have to look at the source exactly how quickly ⦠probably 1 gain step per second or something like that.
But i prefer just running one gain setting as it makes it easier to see changes in the graphs.
The airspy has enough dynamic range so some quick acting autogain isnāt really necessary.
Thank you for your reply - ~1 gain step per second is more than enough to react if a signal is coming close to the receiver (e.g. landing aircraft). So if I understand you correctly, you are providing the binary and it is not open source?
I had it running in a closed box with a Raspberry 4B over last summer where temperatures reached 35°C outside. The Raspberry SoC was at around 65°C.
I didnāt measure the Airspy stick, but it was too hot to touch. However, it did not fail a single minute.
Some users have attached heat sink to it, documented also in this thread:
I have autogain running on my receiver and find that in practice the gain only really changes with overall traffic levels. During the day itās almost always at 15 or 16 and usually stays on the same value all day. At night the gain goes up to 18, and occasionally dips a level or two if thereās a period with more aircraft in sight.
It doesnāt jump about when thereās more than a few aircraft visible though, so Iām happy to let it sort itself out.
Same is shown on my device with different values. Over the day it goes down to 19, but stays there for the entire day. During night with low traffic it comes up to 20 or 21, but overall the number of changes is less than five.
Iāve helped improve it but in the end itās still Youssefs code which he prefers to keep private.
There was no need to have it react better like the new readsb autogain.
Thatās just due to how the airspy deals with very strong signals, it will give data that can be decoded even beyond what you would expect for the ADC dynamic range.
At least for ADS-B with its very simple modulation.
On rtl-sdr you get frontend issues with strong signals before the ADC is even at maximum.
In the airspy_adsb config file, currently have -f 1. If I change this to -f 0, will it be less taxing on the pi? Landing page says cpu usage of 85% on the pizero2w but I have no idea if thats on the limit, hence reviewing a few options.
Also, I notice I dont use the -e or -E options - am I missing something?