Most of the detection zone covered by my station (using R2 and cavity filter) is quite busy in summer (near Budapest) but the message rate still has a daily peak of “only” around 2400-2500 - rarely reaching 2600.
In addition to the amount of traffic and the reception quality of the station, some settings can also result in extra data packets, although their real value may be questionable.
I try to feed a clean data stream to the service providers, using a stricter “whitelist_threshold” (10) and the “non_crc_preamble_filter” is also used normally, in the range of 5-8. By increasing the latter value, the number of packets can be increased somewhat further, but they may contain an increasing number of erroneous data.
In my opinion, it is not worth prioritizing the message rate. Usability is a greater value than the quantity itself. I think.
You have terrain limitations yes?
Others see more aircraft thus higher message rates.
It also depends on how much radar interrogation is going on.
Which is varied based on frequency congestion.
So more planes in the air means the Eurocontrol will lower interrogation rates on their radar sites i believe.
Thus you can have a high message rate that doesn’t really go up when there are more planes.
There was a long thread about Adsbcompare – compare.sh script but i can’t find it.
That was discussing message rates more extensively.
But just a couple of those graphs give some info on the relationship.
Interestingly the position rate stagnates even more than the message rate.
Probably frequestion congestion (overlapping messages) affecting the longer messages more than the shorter messages.
Thanks @wiedehopf for the edited reply, makes totally sense and @caius for the link
Will read through it. Just for my understanding, not really an issue
Yes, my terrain is limited partially in some directions, especially in these, they are significant lower than my max range:
You are terrain limited in all directions, no?
Well all stations are terrain limited but i’m comparing to a reasonable flat terrain which will get you a range around 240 nmi.
More or less, yes. My max range to the south (Switzerland) is around 180 Nm which i do not reach in any other direction (apart from some single aircraft)
Just a quick informal announcement: We have had many problems with the US distributor lagging on order fulfillment and support, and are currently serving the US market directly. I will be personally assisting the Itead support team to get up to speed. Gain of utility. Thanks!
Have a pretty basic question regarding using the AirSpy device. AirSpy code is doing the demod and decoding of ads-b signals on an RPi. But dump1090-fa or readsb is still running (depending on which is installed). What are they doing in that case?
Also supposedly the AirSpy device can be used in “native mode” where it feeds IQ data to dump1090-fa or readsb. Does anyone use that mode or is it not particularly worthwhile?
I have a problem trying to get an Airspy running on a new Raspberry Pi5 with a fresh install of PiAware (SD Card) 10.2.
I have been running my Airspy on a PI4 for years no issue, when I run Wiedehopf’s script on the new PI5, Flightaware cannot see my Airspy at all.
I ran his check script sudo journalctl -e -u airspy_adsb and below is the result:-
Aug 29 16:58:14 piaware systemd[1]: Started airspy_adsb.service - Airspy ADS-B receiver.
Aug 29 16:58:14 piaware airspy_adsb[1522]: airspy_adsb v2.2-RC31
Aug 29 16:58:14 piaware airspy_adsb[1522]: Listening for beast clients on port 47787
Aug 29 16:58:14 piaware airspy_adsb[1522]: Acquired Airspy device with serial 522861C82D5D1407
Aug 29 16:58:14 piaware airspy_adsb[1522]: Decoding started at 12 MSPS (Gain: auto; CPU target: 85 %)
Aug 29 16:58:15 piaware airspy_adsb[1522]: Push client connected to 127.0.0.1:30004 (beast)
Aug 29 16:58:15 piaware airspy_adsb[1522]: Push client disconnected from 127.0.0.1:30004 (beast)
Aug 29 16:58:28 piaware airspy_adsb[1522]: Push client connected to 127.0.0.1:30004 (beast)
Aug 29 16:58:28 piaware airspy_adsb[1522]: Push client disconnected from 127.0.0.1:30004 (beast)
Aug 29 16:58:41 piaware airspy_adsb[1522]: Push client connected to 127.0.0.1:30004 (beast)
Aug 29 16:58:41 piaware airspy_adsb[1522]: Push client disconnected from 127.0.0.1:30004 (beast)
Aug 29 16:58:54 piaware airspy_adsb[1522]: Push client connected to 127.0.0.1:30004 (beast)
Aug 29 16:58:54 piaware airspy_adsb[1522]: Push client disconnected from 127.0.0.1:30004 (beast)
If I swap in an old Flightaware pro dongle, the Flightaware site starts running and works fine.
I am not in any way good with Linux, it looks like the script isn’t modifying the latest SD card Image and its still running like a default install.
Really i’d recommend just using adsb.im as an image.
I’m not sure i’m keen on keeping up with random piaware sd-card changes.
Suppose i might still do that but regardless.