Hi,
Try to install readsb first, then run the install script you mentioned in your post.
https://github.com/wiedehopf/adsb-scripts/wiki/Automatic-installation-for-readsb
Having readsb as a base worked better for me…
I cannot use readsb with the PiAware Image, as the readsb script outputzs:
You are using the piaware image, this setup script would mess up the configuration.
Is anybody using the PiAware 8.2 SD card image and has managed to get data from AirSpy mini?
EDIT: I installed again and see data for around 20 seconds:
-- Journal begins at Wed 2022-12-14 23:30:05 UTC, ends at Mon 2023-04-10 12:42:24 UTC. --
Apr 10 12:41:30 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 12:41:30 piaware airspy_adsb[1231]: airspy_adsb v2.2-RC30-test
Apr 10 12:41:30 piaware airspy_adsb[1231]: Listening for beast clients on port 47787
Apr 10 12:41:30 piaware airspy_adsb[1231]: Acquired Airspy device with serial A74068C8336941>
Apr 10 12:41:30 piaware airspy_adsb[1231]: Decoding started at 12 MSPS (Gain: auto; CPU targ>
Apr 10 12:41:30 piaware airspy_adsb[1231]: Caught signal SIGTERM
Apr 10 12:41:30 piaware airspy_adsb[1231]: Push client connected to 127.0.0.1:30004 (beast)
Apr 10 12:41:30 piaware systemd[1]: Stopping Airspy ADS-B receiver...
Apr 10 12:41:30 piaware airspy_adsb[1231]: Decoding stopped
Apr 10 12:41:30 piaware airspy_adsb[1231]: Push client disconnected from 127.0.0.1:30004 (be>
Apr 10 12:41:30 piaware systemd[1]: airspy_adsb.service: Succeeded.
Apr 10 12:41:30 piaware systemd[1]: Stopped Airspy ADS-B receiver.
Apr 10 12:41:30 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 12:41:30 piaware airspy_adsb[1245]: airspy_adsb v2.2-RC30-test
Apr 10 12:41:30 piaware airspy_adsb[1245]: Listening for beast clients on port 47787
Apr 10 12:41:30 piaware airspy_adsb[1245]: Acquired Airspy device with serial A74068C8336941>
Apr 10 12:41:30 piaware airspy_adsb[1245]: Decoding started at 12 MSPS (Gain: auto; CPU targ>
Apr 10 12:41:31 piaware airspy_adsb[1245]: Client connected from 127.0.0.1:44504 (beast)
lines 1
After that period of time I get:
Apr 10 12:43:17 piaware airspy_adsb[1245]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
What is wrong here?
I deleted the above post, because it is not relevant anymore. I was slow with the answer…
Preventing anomalies, get rid of all other USB devices connected.
Sometimes I had problem with USB 3.0 - so, try a 2.0 one to check if it’s more stable (though mini with 12 Mbps is not a chellenging speed at all)
Which type of power supply are you using? What kind of LNA are you using?
An Airspy requires a good power supply to the Raspberry and an LNA is required otherwise the Airspy is almost deaf
1 Like
Okay, I changed my Samsung FIT USB3.0 Stick with an SD-card. Still no single plane on the map.
The AirSpy mini is connected to the USB2.0 port of the rPi4 8GB.
I am using the original Raspberry power supply, rated 3A, but tried my MacBook Pro 2022 USB-C power supply as well. Still no data…
I am using the Triple Filter ADS-B 1090 Mhz LNA from RTL-SDR.com
I also tried the Raspberry Pi OS Lite 32-Bit (Bullseye) Image and did the following:
sudo bash -c "$(wget -O - https://github.com/wiedehopf/adsb-scripts/raw/master/readsb-install.sh)"
sudo reboot
sudo bash -c "$(wget -O - https://raw.githubusercontent.com/wiedehopf/airspy-conf/master/install.sh)"
sudo reboot
Still no data displayed under http://192.168.1.28/tar1090/
My rPi3 with the Nooelec NESDR SMArTee v2 R820T2 dongle is working fine, but I want to enhance this setup with the rPi4 and the AirSpy mini.
Any other ideas!?
I am not sure about mini, but my R2 has only a low - 50mA - limit for the built-in bias-T max current.
Try to use an external bias-T circuit and a low-noise power source for feeding the amplifier. (Easy to build one with some of the 7805 stabilizer IC and a few capacitors. 7805 has its noise in the 10-50 micro-Volt range)
Without examining the available logs, my guess is that mini’s bias circuit is overloaded and it is switching off - as if it is shorted. Restarting the kit may reset the restriction for some seconds - then it gets off again. Ofc, I can not be 100% sure…
One more thing: Check: your detected planes, on “your IP”:8504 (eg. 192.168.2.106:8504)
comes into my mind: Is user mode driver installed?
prereq:
sudo apt-get install build-essential cmake libusb-1.0-0-dev pkg-config
then
wget https://github.com/airspy/airspyone_host/archive/master.zip
unzip master.zip
cd airspyone_host-master
mkdir build
cd build
cmake ../ -DINSTALL_UDEV_RULES=ON
make
sudo make install
sudo ldconfig
clean temp files
cd airspyone_host-master/build
rm -rf *
Have you enabled the bias tee on the Airspy?
Can you show us the airspy_adsb configuration file at /etc/default/airspy_adsb
And perhaps the result of piaware-status command. This will give us an idea on what is going on with your system.
Specific airspy status is available via this command:
journalctl -eu airspy_adsb --no-pager
hope this helps.
What logs do you need?
No planes to see. The output map seems to me the same as with the URL http://192.168.1.28/tar1090/
All done with the Raspberry Pi OS Lite 32-Bit (Bullseye) Image on SD-card. Still no planes to see.
Sure, I added the -b parameter to the /etc/default/airspy_adsb config file.
To keep it simple I really just did what I saif before, so the config file is standard. I only added the -b parameter for the BIAS tee to activate.
Okay, so I switched back from the Raspberry Pi OS Lite 32-Bit (Bullseye) Image to the PiAware Image but without the user mode driver that janoskonya mentioned here and this is the output:
pi@piaware:~ $ piaware-status
PiAware master process (piaware) is running with pid 490.
PiAware ADS-B client (faup1090) is running with pid 564.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (beast-splitter) is running with pid 480.
beast-splitter (pid 480) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.
the ADS-B data program at localhost/47787 is NOT producing data on localhost:47787.
Local ADS-B relay is NOT producing data on localhost:30005.
Your feeder ID is eba2103c-13a5-4f13-828d-f002b795e601 (from /var/cache/piaware/feeder_id)
Here is the output:
pi@piaware:~ $ journalctl -eu airspy_adsb --no-pager
-- Journal begins at Wed 2022-12-14 23:30:05 UTC, ends at Mon 2023-04-10 23:53:51 UTC. --
Apr 10 23:43:38 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 23:43:38 piaware airspy_adsb[1597]: airspy_adsb v2.2-RC30-test
Apr 10 23:43:38 piaware airspy_adsb[1597]: Listening for beast clients on port 47787
Apr 10 23:43:38 piaware airspy_adsb[1597]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:43:38 piaware airspy_adsb[1597]: Caught signal SIGTERM
Apr 10 23:43:38 piaware systemd[1]: Stopping Airspy ADS-B receiver...
Apr 10 23:43:38 piaware systemd[1]: airspy_adsb.service: Succeeded.
Apr 10 23:43:38 piaware systemd[1]: Stopped Airspy ADS-B receiver.
Apr 10 23:43:38 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 23:43:38 piaware airspy_adsb[1616]: airspy_adsb v2.2-RC30-test
Apr 10 23:43:38 piaware airspy_adsb[1616]: Listening for beast clients on port 47787
Apr 10 23:43:38 piaware airspy_adsb[1616]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
...
...
...
Apr 10 23:43:44 piaware airspy_adsb[1616]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:43:44 piaware systemd[1]: Stopping Airspy ADS-B receiver...
Apr 10 23:43:44 piaware airspy_adsb[1616]: Caught signal SIGTERM
Apr 10 23:43:44 piaware systemd[1]: airspy_adsb.service: Succeeded.
Apr 10 23:43:44 piaware systemd[1]: Stopped Airspy ADS-B receiver.
-- Boot 194dafeb14fa4b7ca153a6f656cdf922 --
Apr 10 23:43:48 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 23:43:48 piaware airspy_adsb[295]: airspy_adsb v2.2-RC30-test
Apr 10 23:43:48 piaware airspy_adsb[295]: Listening for beast clients on port 47787
Apr 10 23:43:48 piaware airspy_adsb[295]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:43:49 piaware airspy_adsb[295]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
...
...
...
Apr 10 23:48:55 piaware airspy_adsb[295]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:48:56 piaware airspy_adsb[295]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:48:57 piaware airspy_adsb[295]: Caught signal SIGTERM
Apr 10 23:48:57 piaware systemd[1]: Stopping Airspy ADS-B receiver...
Apr 10 23:48:57 piaware systemd[1]: airspy_adsb.service: Succeeded.
Apr 10 23:48:57 piaware systemd[1]: Stopped Airspy ADS-B receiver.
Apr 10 23:48:57 piaware systemd[1]: airspy_adsb.service: Consumed 3.259s CPU time.
-- Boot 6c1a5e59baee43538ec59b1ff792f61e --
Apr 10 23:49:01 piaware systemd[1]: Started Airspy ADS-B receiver.
Apr 10 23:49:01 piaware airspy_adsb[299]: airspy_adsb v2.2-RC30-test
Apr 10 23:49:01 piaware airspy_adsb[299]: Listening for beast clients on port 47787
Apr 10 23:49:01 piaware airspy_adsb[299]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:49:02 piaware airspy_adsb[299]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:49:03 piaware airspy_adsb[299]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
...
...
...
Apr 10 23:53:50 piaware airspy_adsb[299]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
Apr 10 23:53:51 piaware airspy_adsb[299]: airspy_open() failed: AIRSPY_ERROR_NOT_FOUND (-5)
what does it say for “lsusb” ?
I’m on the PiAware Image again as I said before and currently did not do the user mode driver install.
This is the output of lsusb:
pi@piaware:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Try to install the usermode driver first,
then switch off the bias option to check what it answers for lsusb
(NOT FOUND is not good enough)
Your amp draws 150 mA current. I think, mini can not handle that amount… (External bias-t circuit is necessary.)
One of them would be fine (of course a cheaper one is also ok)
https://janielectronics.com/index.php?route=product/search&search=bias%20tee
lsusb for R2 looks like this:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1d50:60a1 OpenMoko, Inc. Airspy
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
You may test your mini on a windows machine to check its working state. On win machine it does not need a driver…
Switch the bias off (erease “-b”),
remove and reconnect mini, (forcing the recognition)
restart airspy (sudo systemctl restart airspy_adsb),
…check lsusb again
It will not work while it is not shown in the list
It seems the Airspy Mini bias tee might be able to handle the current demands even though it is only rated for 50mA - see this thread - Airspy and bias tee
I can’t comment from personal experience as I use an Uputronics LNA/Filter that is powered from a separate USB port on the my Raspi 4 with my Airspy Mini.
lsusb output for the mini is the same as the R2:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 1d50:60a1 OpenMoko, Inc. Airspy
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Dumb question, but have you got the triple filter connected the right way around? 
I have a vague memory of another thread where someone confused the signal path direction of the in and out labels - in is from the antenna.
Thanks for the link to bias tee subject.
Reading the posts there, I met with “RTL-SDR LNA” only. I think, it should be the wideband one - not the triple filtered with 3 amplifier unit inside. The wideband one draws ~80-90 mA (not 150)
Of course, due to my lack of experience with the mini, I can’t state as a fact that it definitely causes problems, but overloading the bias circuit would result in the circuit being disconnected (due to the internal protection mechanism). The exact load at which the protection is activated can only be determined by measurement…
1 Like
In this case your Airspy is not recognized. As long as this is not given, all other troubleshooting attempts will fail.
1 Like
I will do so and come back here with the resultst, once I get a Windows maschine, because I only have Macs. 
I disabled BIAS tee, removed the LNA and antenna, restarted, but the AirSpy mini ist still not visible under lsusb.
I will check it’s working state under a Windows maschine soon.
1 Like
You have one more step.
Plug your mini into the rpi3 - just for the detection purpose. (lsusb)
I guess, an RTL chip based dongle is already installed there. Is it a proper method to check your mini? We"ll see…