Highly recommended. One may also want to test the new -x mode.
1 Like
Upgraded and restarted. I’m running with -x and -C 95. The new -C parameter is working out really well. No dropped packages and it reached 97% and then dropped down to the previous good value (this is from RC2):
Aug 26 17:03:14 Spy airspy_adsb[15380]: CPU 92.0 %, target 95.0 %, adjusting preamble filter: 25.00 -> 25.18
Aug 26 17:03:24 Spy airspy_adsb[15380]: CPU 92.6 %, target 95.0 %, adjusting preamble filter: 25.18 -> 25.32
Aug 26 17:03:34 Spy airspy_adsb[15380]: CPU 92.8 %, target 95.0 %, adjusting preamble filter: 25.32 -> 25.46
Aug 26 17:05:24 Spy airspy_adsb[15380]: CPU 92.9 %, target 95.0 %, adjusting preamble filter: 25.46 -> 25.58
Aug 26 17:46:14 Spy airspy_adsb[15380]: CPU 93.0 %, target 95.0 %, adjusting preamble filter: 25.58 -> 25.70
Aug 26 17:54:22 Spy airspy_adsb[15380]: CPU 92.9 %, target 95.0 %, adjusting preamble filter: 25.70 -> 25.83
Aug 26 17:57:12 Spy airspy_adsb[15380]: CPU 92.9 %, target 95.0 %, adjusting preamble filter: 25.83 -> 25.95
Aug 27 06:47:13 Spy airspy_adsb[15380]: CPU 92.9 %, target 95.0 %, adjusting preamble filter: 25.95 -> 26.08
Aug 27 12:13:37 Spy airspy_adsb[15380]: CPU 93.0 %, target 95.0 %, adjusting preamble filter: 26.08 -> 26.20
Aug 27 12:57:27 Spy airspy_adsb[15380]: CPU 92.9 %, target 95.0 %, adjusting preamble filter: 26.20 -> 26.32
Aug 27 13:32:39 Spy airspy_adsb[15380]: CPU 93.0 %, target 95.0 %, adjusting preamble filter: 26.32 -> 26.45
Aug 27 13:42:07 Spy airspy_adsb[15380]: CPU 93.0 %, target 95.0 %, adjusting preamble filter: 26.45 -> 26.57
Aug 27 23:13:04 Spy airspy_adsb[15380]: CPU 97.0 %, target 95.0 %, adjusting preamble filter: 26.57 -> 26.45
For clarity it may be a good thing if the logging function prints out the current CPU percentage and preamble value after a decrease?
Let’s watch the stats over a few hours.
1 Like
Yeah, it will be really slow during the night. Perhaps 30 aircrafts in total for the next 8 hours. Nothing much happening here during the dark hours, mostly intercontinental traffic to/from Asia and the EU and most of it at 250+ Nm away…
1 Like
Going for it, let’s see what happens. Rare DX is good (I’ve just applied for a DXCC endorsement, up to 282/282 now).
1 Like
I’ve reverted -w to 4 and enabled -x. Will leave to run and see what happens to positions with a single track, and “other” aircraft. Very slow here too - Covid lockdown and the weekend.
airspy_adsb.service - Airspy ADS-B receiver
Loaded: loaded (/lib/systemd/system/airspy_adsb.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-08-28 07:57:53 AEST; 45s ago
Docs: https://discussions.flightaware.com/t/howto-airspy-mini-piaware-dump1090-fa-configuration/44343
Main PID: 12897 (airspy_adsb)
Tasks: 4 (limit: 4165)
CGroup: /system.slice/airspy_adsb.service
└─12897 /usr/local/bin/airspy_adsb -v -f 1 -t 300 -w 4 -e 12.0 -C 87 -x -l 47787:beast -c localhost:30004:beast -g 20 -m 20
Aug 28 07:57:53 raspi4-1 systemd[1]: Started Airspy ADS-B receiver.
Aug 28 07:57:53 raspi4-1 airspy_adsb[12897]: airspy_adsb v2.0-RC3
Aug 28 07:57:53 raspi4-1 airspy_adsb[12897]: Listening for beast clients on port 47787
Aug 28 07:57:53 raspi4-1 airspy_adsb[12897]: Acquired Airspy device with serial B8B067DC3623901F
Aug 28 07:57:53 raspi4-1 airspy_adsb[12897]: Decoding started at 20 MSPS
Aug 28 07:57:57 raspi4-1 airspy_adsb[12897]: Push client connected to localhost:30004 (beast)
Aug 28 07:58:03 raspi4-1 airspy_adsb[12897]: CPU 80.4 %, target 87.0 %, adjusting preamble filter: 12.00 -> 12.39
There is a more aggressive version unpublished. Maybe we should consider it if the output is clean.
3 Likes
RC4:
https://github.com/wiedehopf/airspy-conf/raw/master/dev/airspy_adsb-linux-arm.tgz
https://github.com/wiedehopf/airspy-conf/raw/master/dev/airspy_adsb-linux-arm64.tgz
https://github.com/wiedehopf/airspy-conf/raw/master/dev/airspy_adsb-linux-x86_64.tgz
Files might change to next RC at some point or whatever version is current.
Me personally i’d never use -x but that’s just me 
Any chance of telling us how RC4 differs from RC3?
whitelist scoring.
-w 5 is recommended and should be more messages than -w 3 before RC4.
But -w3 is fine as well with RC4, testing didn’t show any issues in regards to single messages or stuff like that.
Well at least not bogus single messages.
Single messages can be valid decodes of planes that are almost out of range.
Also, the filtering of the duplicates was improved further.
Thanks will give it a try with -w 5 - this is a brief run with RC3 and -w 4. Single position tracks came back. Earlier was RC2 and -w 5
1 Like
Hi all
had a bit of a job but abcd helped out
so i got so far that sdr rtl not installed
i see map -fa and skyaware but no planes
pi4 with debian 11 4gb arm64 installed
flightaware dongle dont work nor do the resident airspy mini i want to use
aomething missing
can you help
@suffolk3000
What is output of rtl_test - t with prostick pluggedin ? This is important.
Ok Dx mode, something to do with long distance detections???
Linux rpi4-20210823 5.10.0-8-arm64 #1 SMP Debian 5.10.46-4 (2021-08-03) aarch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Aug 27 22:41:58 2021 from 192.168.0.2
pi@rpi4-20210823:~$ rtl_test - t
Found 1 device(s):
0: ▒/P▒▒▒, ▒▒O▒▒▒, SN:
Using device 0: Generic RTL2832U
usb_open error -3
Please fix the device permissions, e.g. by installing the udev rules file rtl-sd r.rules
Failed to open rtlsdr device #0.
I have posted solution few days ago here:
added rebooting now
pi@rpi4-20210823:~$ rtl_test -t
Found 1 device(s):
0: , , SN:
Using device 0: Generic RTL2832U
usb_claim_interface error -6
Failed to open rtlsdr device #0.
still no planes
(1) Unplug, then replug prostick
(2) Restart dump1090-fa or Reboot Pi