Still looking at the positions, 50000 ADS-B FA stats positions per hour compared to 33000 for your setup is quite an improvement!
Hi all
got my new airspy thismorning
been trying out all options rasbian, piaware install versions on FA none going any where soon
using pi3b+ it just dont work right
aany pointers if theres a foolproff image hiding some where
many thanks
john
The script is as foolproof as it gets.
It works with the piaware sd-card image.
Did you check the links in the first post of this thread?
Yes i did use both but i will redo sdcard again see how i get on
Use the sd-card with the script, that is the easiest combination probably.
Also be more specific.
Ok pi3b+ fresh install piaware and run
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/wiedehopf/airspy-conf/master/install.sh)"
and it returned this
sudo bash -c ā$(wget -O - https://raw.githubusercontent.com/wiede hopf/airspy-conf/master/install.sh)ā
ā2019-05-14 17:47:51-- https://raw.githubusercontent.com/wiedehopf/airspy-conf /master/install.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)ā¦ 151.101.16.13 3
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.16.1 33|:443ā¦ connected.
HTTP request sent, awaiting responseā¦ 200 OK
Length: 2715 (2.7K) [text/plain]
Saving to: āSTDOUTā
-
100%[===================>] 2.65K --.-KB/s in 0s
2019-05-14 17:47:51 (13.6 MB/s) - written to stdout [2715/2715]
Failed to stop airspy_adsb.service: Unit airspy_adsb.service not loaded.
Created symlink /etc/systemd/system/multi-user.target.wants/airspy_adsb.service ā /lib/systemd/system/airspy_adsb.service.
Set receiver-type to relay in /boot/piaware-config.txt:84
Set receiver-host to localhost in /boot/piaware-config.txt:85
Set receiver-port to 47787 in /boot/piaware-config.txt:86
i then rerun above command and no problems
loaded skyview no faults but no data
It takes a minute before beast-splitter picks up the airspy_adsb output.
Maybe just reboot, wait 2 minutes.
It could be that piaware doesnāt start beast-splitter and you need to reboot after installation.
Iāve added a step to the install script so beast-splitter is restarted and there is no need for a reboot.
Nope still no data coming through
any commands to run in pi perhaps
the mind boggles
checked usb v/a showing 5.17v 0.06 a dont seem enough really pi is rather warm
Sure letās check if everything is connected to each other:
journalctl --no-pager -u beast-splitter
journalctl --no-pager -u airspy_adsb
heres output
journalctl --no-pager -u beast-splitter
ā Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Tue 2019-05-14 18:19:14 UTC. ā
May 06 18:15:00 piaware systemd[1]: Started Mode S Beast data forwarder.
May 06 18:15:02 piaware beast-splitter[430]: Listening on 0.0.0.0:30005
May 06 18:15:02 piaware beast-splitter[430]: Listening on [::]:30005
May 06 18:15:02 piaware beast-splitter[430]: localhost:30104: connected to [::1]:30104 with settings R
May 06 18:15:02 piaware beast-splitter[430]: net(localhost:47787): configured with settings: BCdfGHijk
May 06 18:15:02 piaware beast-splitter[430]: net(localhost:47787): connection to [::1]:47787 failed: Connection refused
May 06 18:15:02 piaware beast-splitter[430]: net(localhost:47787): i/o error: Broken pipe
May 06 18:15:05 piaware beast-splitter[430]: [::]:30005: accepted a connection from [::1]:49998 with settings R
May 06 18:15:05 piaware beast-splitter[430]: [::1]:49998: settings changed to RCdfj
May 14 18:12:25 piaware beast-splitter[430]: [::1]:49998: connection closed
May 14 18:12:26 piaware systemd[1]: Stopping Mode S Beast data forwarderā¦
May 14 18:12:26 piaware systemd[1]: Stopped Mode S Beast data forwarder.
May 14 18:12:27 piaware systemd[1]: Started Mode S Beast data forwarder.
May 14 18:12:27 piaware beast-splitter[842]: Listening on 0.0.0.0:30005
May 14 18:12:27 piaware beast-splitter[842]: Listening on [::]:30005
May 14 18:12:27 piaware beast-splitter[842]: localhost:30104: connected to [::1]:30104 with settings R
May 14 18:12:27 piaware beast-splitter[842]: net(localhost:47787): configured with settings: BCdfGHijk
May 14 18:12:27 piaware beast-splitter[842]: net(localhost:47787): connection to [::1]:47787 failed: Connection refused
May 14 18:12:27 piaware beast-splitter[842]: net(localhost:47787): i/o error: Broken pipe
May 14 18:12:37 piaware beast-splitter[842]: [::]:30005: accepted a connection from [::1]:50006 with settings R
May 14 18:12:37 piaware beast-splitter[842]: [::1]:50006: settings changed to RCdfj
May 14 18:13:27 piaware beast-splitter[842]: net(localhost:47787): connection to [::1]:47787 failed: Connection refused
May 14 18:13:27 piaware beast-splitter[842]: net(localhost:47787): connected to 127.0.0.1:47787
May 14 18:13:27 piaware beast-splitter[842]: net(localhost:47787): configured with settings: BCdfGHijk
May 14 18:13:30 piaware beast-splitter[842]: net(localhost:47787): configured with settings: BCdfGHijk
journalctl --no-pager -u airspy_adsb
ā Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Tue 2019-05-14 18:20:27 UTC. ā
May 06 18:14:56 piaware systemd[1]: Started Airspy ADS-B receiver.
May 06 18:14:56 piaware airspy_adsb[272]: Listening for asavr clients on port 47806
May 06 18:14:56 piaware airspy_adsb[272]: Listening for beast clients on port 47787
May 06 18:14:56 piaware airspy_adsb[272]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
May 06 18:14:57 piaware airspy_adsb[272]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
May 06 18:14:58 piaware airspy_adsb[272]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
May 06 18:14:59 piaware airspy_adsb[272]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
found an error
That just means the airspy isnāt working correctly.
If you reboot and the log shows this again, itās defective iād say.
Can you try using the airspy under Windows to check if itās working?
Yer ok will try that
just my luck hehe
No go in pc either grrr
i did think there was a problem as i normally get it right
returning dongle
Sorry for that.
Anyway it was set up correctly!
Ok strange hole on side of dongle with switch inside moved it and working now how wierd tried on dif pi aswell
1 Like
Airspy dongle working very well
Would i be right in saying if i use wifi instead of ethernet on pi i would then increase bandwidth for usb dongle for using m20 instead of m12
also i have seen posts having used 2.5MSPS would or could i use another figure say 14MSPS? before i jump in the deep end and try this
regards
john
Bottleneck is the CPU most of the time.
With as many planes you see in England, no chance for -m20 on the RPi.
dump1090-fa using rtl-sdr dongles uses 2.4 MHz samplerate.
The airspy already does plenty of oversampling with a samplerate of 12 MHz.
20 MHz usually doesnāt result in much improvement compared to 12 MHz.
Thanks for info
i will leave well alone
regards
john
I saw a slight increase in reception of aircrafts far away when I changed to 20 MHz. Picked them up a little bit sooner and squeezed a few more messages out of them. More obvious during the slow hours when there are fewer planes in the air thus less ads-b transmissions that interfere with eachother. When running with 12 MHz I had about 3-4 Nm less average range (all directions) compared to running with 20 MHz. This can perhaps be attributed to changes in traffic pattern, flight levels due to weather conditions, general atmospheric conditions and so on, but I run each gain setting and 12/20 Mhz for a week so it should be fairly accurate.
But every station is different. I have 4-6 times more positions (and 2-3 times more aircrafts) at 160 Nm+ than at <40 Nm. Maybe my site benefits more from 20 Mhz than a site with the bulk of positions and aircrafts more close by.
I ran mine for a couple of hours earlier this week at 20 and had it monitoring but didnāt see a single dropped whatsit. However, I didnāt really see any noticeable difference in performance so put it back. I really ought to run it for a few days for a proper comparison though.