The highest I’ve seen is about 3050/s, but yeah that was before covid. I think Keith has seen slightly higher, but not by much.
I have e set to 10.75 with the pi running at 2Ghz now. I’m not sure it’s made much difference with current traffic levels, but reducing the gain from 17 to 14 did get me an increase in positions. Have to wait for things to get busy to see big numbers again.
Thanks I’ve installed Graphs… Will post in a few days when its run a while.
I’ve dropped my gain to 18… Will see how it runs.
Thanks everyone this forum is brilliant !!
Yup, just over 3100/s but that’s only been a handful of times.
After seeing caius’ comments previously, I’ve also dropped my gain a notch and I’m at 12 now but I’m not sure if it’s made any noticeable difference.
I’m really looking forward to when things open up again. It’s been a long time since I’ve seen over 500 aircraft at a time and I miss having over 1,000,000 position reports/day 
simple to follow ! Thanks - /?pTracks up and running with range outline at 40,000ft. Going to change /?pTracks to 24hrs
In advance of the arrival of an Airspy Mini, please could someone confirm if the Automatic Installation Scripts work for add-on Dump1090-fa and Piaware installations which is my current setup or are they specific to the Piaware sd-card image?
Many thanks
@wiedehopf scripts work like a breeze. No issues. I have only used them with the add-on, not the Piaware sd-card image.
@NigelRichardson
Would you please be so kind to post your experiences here. I am thinking off buying an Airspy mini as well, but somewhat afraid for the installation
Thanks
If you follow the link to the manual installation instructions you can see what the scripts do. It’s a series of small configuration changes and moving files around. It’s not hard and a good idea to understand what the scripts do in case you want to tweak or troubleshoot after installation.
Generally, all of wiedehopf’s scripts and utilities are reliable and fresh. The only glitches usually come from previously installing unique software or configurations that differ from the norm.
@davidinjp
Thank you for the reply. I know that Wiedehopfs scripts are good. Use them for Graphs, Tar1090 and the timelaps.
But I also read that some of the user did face some problems. And being an absolute non tech guy I am somewhat reluctant, but moving to “I will try it”
I’ve received my Airspy Mini today but have hit a snag in getting it running. I have followed the automatic installation scripts at the top of this post, and edited the options to include -b as I’m using a Uputronics lna powered by the Airspy bias-t. However, when I restart the Airspy using: sudo systemctl restart airspy_adsb dump1090-fa, I get the following error message:
Failed to restart airspy.adsb service: Unit airspy.adsb service is masked
Any suggestions of what I should do?
Many thanks
Using a . instead of _ will not work.
Thanks. I’m no longer getting that error message. The restart command seems to work fine but I’m still not receiving anything. I’ve tried with the lna disconnected but still nothing. I actually followed your manual scripts not the automatic ones
Thanks
Did you check if it has up to date firmware?
Just received a new R2 and it had old firmware in it.
Unless the firmware is really old it doesn’t matter for ADS-B … pretty sure.
Then use the automatic ones … you probably screwed it up and i don’t care to debug it if automatic scripting is available.
Otherwise check the logs, check the TCP connection to dump1090-fa is being made …
Check the dump1090-fa log that it’s running well.
I’ve checked and double checked everything
Unfortunately I don’t have your expertise so have no idea where to start on your other suggestions
Thanks
I’ve just completed a check for lost samples using:
sudo journalctl -u airspy_adsb -f -n50
and obtained the output below. Does this indicate the Airspy is working ok? What would I be looking for to identify lost samples?
Thank you
pi@raspberrypi:~ $ sudo journalctl -u airspy_adsb -f -n50
-- Logs begin at Sat 2021-05-15 14:17:01 BST. --
May 15 15:28:00 raspberrypi airspy_adsb[306]: Decoding stopped
May 15 15:28:00 raspberrypi airspy_adsb[306]: Push client disconnected from localhost:30004 (beast)
May 15 15:28:00 raspberrypi systemd[1]: airspy_adsb.service: Succeeded.
May 15 15:28:00 raspberrypi systemd[1]: Stopped Airspy ADS-B receiver.
May 15 15:28:00 raspberrypi systemd[1]: Started Airspy ADS-B receiver.
May 15 15:28:00 raspberrypi airspy_adsb[6337]: airspy_adsb v1.85
May 15 15:28:00 raspberrypi airspy_adsb[6337]: Listening for beast clients on port 29999
May 15 15:28:00 raspberrypi airspy_adsb[6337]: Listening for asavr clients on port 47806
May 15 15:28:00 raspberrypi airspy_adsb[6337]: Acquired Airspy device with serial 285467E633873093
May 15 15:28:00 raspberrypi airspy_adsb[6337]: Decoding started at 12 MSPS
May 15 15:28:04 raspberrypi airspy_adsb[6337]: Push client connected to localhost:30004 (beast)
May 15 15:50:47 raspberrypi airspy_adsb[6337]: Caught signal 15
May 15 15:50:47 raspberrypi systemd[1]: Stopping Airspy ADS-B receiver...
May 15 15:50:47 raspberrypi airspy_adsb[6337]: Decoding stopped
May 15 15:50:47 raspberrypi airspy_adsb[6337]: Push client disconnected from localhost:30004 (beast)
May 15 15:50:47 raspberrypi systemd[1]: airspy_adsb.service: Succeeded.
May 15 15:50:47 raspberrypi systemd[1]: Stopped Airspy ADS-B receiver.
May 15 15:50:47 raspberrypi systemd[1]: Started Airspy ADS-B receiver.
May 15 15:50:47 raspberrypi airspy_adsb[13869]: airspy_adsb v1.85
May 15 15:50:47 raspberrypi airspy_adsb[13869]: Listening for beast clients on port 29999
May 15 15:50:47 raspberrypi airspy_adsb[13869]: Listening for asavr clients on port 47806
May 15 15:50:47 raspberrypi airspy_adsb[13869]: Acquired Airspy device with serial 285467E633873093
May 15 15:50:47 raspberrypi airspy_adsb[13869]: Decoding started at 12 MSPS
May 15 15:50:51 raspberrypi airspy_adsb[13869]: Push client connected to localhost:30004 (beast)
May 15 18:19:30 raspberrypi airspy_adsb[13869]: Caught signal 15
May 15 18:19:30 raspberrypi systemd[1]: Stopping Airspy ADS-B receiver...
May 15 18:19:30 raspberrypi airspy_adsb[13869]: Decoding stopped
May 15 18:19:30 raspberrypi airspy_adsb[13869]: Push client disconnected from localhost:30004 (beast)
May 15 18:19:30 raspberrypi systemd[1]: airspy_adsb.service: Succeeded.
May 15 18:19:30 raspberrypi systemd[1]: Stopped Airspy ADS-B receiver.
May 15 18:19:30 raspberrypi systemd[1]: Started Airspy ADS-B receiver.
May 15 18:19:30 raspberrypi airspy_adsb[29377]: airspy_adsb v1.85
May 15 18:19:30 raspberrypi airspy_adsb[29377]: Listening for beast clients on port 29999
May 15 18:19:30 raspberrypi airspy_adsb[29377]: Listening for asavr clients on port 47806
May 15 18:19:30 raspberrypi airspy_adsb[29377]: Acquired Airspy device with serial 285467E633873093
May 15 18:19:30 raspberrypi airspy_adsb[29377]: Decoding started at 20 MSPS
May 15 18:19:34 raspberrypi airspy_adsb[29377]: Push client connected to localhost:30004 (beast)
May 15 20:33:07 raspberrypi airspy_adsb[29377]: Caught signal 15
May 15 20:33:07 raspberrypi systemd[1]: Stopping Airspy ADS-B receiver...
May 15 20:33:07 raspberrypi airspy_adsb[29377]: Decoding stopped
May 15 20:33:07 raspberrypi airspy_adsb[29377]: Push client disconnected from localhost:30004 (beast)
May 15 20:33:07 raspberrypi systemd[1]: airspy_adsb.service: Succeeded.
May 15 20:33:07 raspberrypi systemd[1]: Stopped Airspy ADS-B receiver.
May 15 20:33:07 raspberrypi systemd[1]: Started Airspy ADS-B receiver.
May 15 20:33:07 raspberrypi airspy_adsb[7823]: airspy_adsb v1.85
May 15 20:33:07 raspberrypi airspy_adsb[7823]: Listening for beast clients on port 29999
May 15 20:33:07 raspberrypi airspy_adsb[7823]: Listening for asavr clients on port 47806
May 15 20:33:07 raspberrypi airspy_adsb[7823]: Acquired Airspy device with serial 285467E633873093
May 15 20:33:07 raspberrypi airspy_adsb[7823]: Decoding started at 20 MSPS
May 15 20:33:11 raspberrypi airspy_adsb[7823]: Push client connected to localhost:30004 (beast)
It looks like Airspy is running just fine without lost samples.
In case you had lost samples they would appear below the ‘Decoding started at 12MSPS line’
Like this:
May 13 18:35:11 raspberrypi airspy_adsb[322]: /!\ Lost 131072 samples /!
May 13 18:35:11 raspberrypi airspy_adsb[322]: /!\ Lost 131072 samples /!
etc etc
Many thanks, now I know what to look out for, especially when things are busier.