No lost samples - i will leave that as it is.
Overall CPU is at 30%. The Raspberry is doing feeding only, it’s not used for other tasks
correct -26 and -30
Small but significant difference
No lost samples - i will leave that as it is.
Overall CPU is at 30%. The Raspberry is doing feeding only, it’s not used for other tasks
correct -26 and -30
Small but significant difference
I might be missing something simple here, well I hope so.
I have a working pi3 with dump1090-fa and fa dongle etc and I received my Airspy Mini today.
So I ran the install script referenced in the 1st post and then shutdown. I then swapped the dongles and powered up. I can ssh back onto the pi but I am getting no planes on SkyAware etc. Performance graphs are all empty also.
When I run the uninstall script and swap back to the FAdongle… all is well again?
Any ideas.
EDIT: Managed to find some info/help up above … See my results below… (i have the latest firmware installed)
pi@piaware:~ $ echo blacklist airspy |sudo tee /etc/modprobe.d/airspy-blacklist.conf ; sudo rmmod airspy
blacklist airspy
rmmod: ERROR: Module airspy is not currently loaded
pi@piaware:~ $ sudo systemctl status airspy_adsb
● airspy_adsb.service - Airspy ADS-B receiver
Loaded: loaded (/lib/systemd/system/airspy_adsb.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2021-07-01 14:15:10 UTC; 3min 49s ago
Docs: HOWTO: Airspy mini and Airspy R2: Piaware / dump1090-fa configuration
Main PID: 388 (airspy_adsb)
Tasks: 4 (limit: 2062)
CGroup: /system.slice/airspy_adsb.service
└─388 /usr/local/bin/airspy_adsb -v -f 1 -l 47787:beast -g 21 -m 12
Jul 01 14:15:10 piaware systemd[1]: Started Airspy ADS-B receiver.
Jul 01 14:15:10 piaware airspy_adsb[388]: airspy_adsb v1.85
Jul 01 14:15:10 piaware airspy_adsb[388]: Listening for beast clients on port 47787
Jul 01 14:15:10 piaware airspy_adsb[388]: Acquired Airspy device with serial 260868C82A844E9B
Jul 01 14:15:10 piaware airspy_adsb[388]: Decoding started at 12 MSPS
Jul 01 14:15:11 piaware airspy_adsb[388]: /!\ Lost 524288 samples /!
Jul 01 14:15:11 piaware airspy_adsb[388]: /!\ Lost 262144 samples /!
Jul 01 14:15:11 piaware airspy_adsb[388]: /!\ Lost 131072 samples /!
Jul 01 14:15:11 piaware airspy_adsb[388]: /!\ Lost 131072 samples /!\
Only lost samples to start an none after? But why rmmod: ERROR: Module airspy is not currently loaded
You’ll have to be more precise what your setup is.
But it seems airspy_adsb is running so it should be working.
(your status shows it working)
Maybe there was an issue with the SMA connection?
Thanks appreciate the reply, I am back on the blue flightaware dongle … all working OK with that.
But when I swap to AirSpy Mini, i get no planes showing up on SkyAware… (checked the switch on the AirSpy mini, and if in the wrong position systemctl status airspy_adsb gives an error. So I know the correct position of the switch)
More precise setup:
Raspberry Pi 3 Model B Rev 1.2
PiAware (Debian Package Add-on) 5.0
Uprtonics filter with external power (but have tried with this attached and not attached.
SMA connection has been made and remade a few time so it is not that.
Any thing else that may help?
It looks like you are dropping samples. That may be due to other USB-devices connected to the Pi, the Airspy makes heavy use of the USB-bus. It may also happen if you connect the Pi to the network via ethernet. On the Pi3 USB and ethernet share the same bus.
It may also be due to a poor power supply that doesn’t deliver enough voltage and/or current to the Pi. Usually the original power supply is the best solution. Phone chargers or cheap power bricks are seldom stable enough when the Pi requires more voltage and current.
So if possible, remove everything connected to the USB ports (except the airspy) and try again. You may also (if not done) connect the Pi via wifi instead of ethernet.
The Pi3 can run the airspy, but the Pi4 is more suitable due to a better CPU and separation between USB and ethernet.
What is your gain setting?
It may be too high with an LNA.
Thanks,
Only the airspy is connected, and I think only drop samples to start at boot time… I don’t seem to continue to drop samples after boot. My assumption I would continue to see new lines of drop samples if i was dropping them?
When Airspy is connected, “1090 Radio” stays red. While PiAware and FlightAware are happy in the green. So somehow there is an issue with SkyaAware connecting to the feed of the dongle I am thinking?
Short term plan was to get Airspy Mini running on this setup to see how it compares to the FA dongle, looks like I will be ordering a Pi4 tonight so I can start a build from scratch.
I have not tinkered with gain, but also tested with and without LNA. Also graphs1090 is blank for all ADSB related data when Airspy is plugged in. (also my previous post where status page isnt seeing the “1090 Radio”
Yes, if you don’t see a flow of new lines of dropped samples you should be ok. The Airspy can drop samples silently, but I don’t know how common that is.
That may be due to the fact that the Airspy uses it’s own decoder instead of dump1090-fa. Dump1090-fa is, in the airspy configuration, accepting data from airspy_adsb and does not handle the dongle directly by itself.
You can try to point your browser to port 47787 when the airspy is connected and configured.
http://the.ip.of.the.pi:47787/ and see if you get anything in the browser.
By doing that you connect directly to airspy_adsb that handles the decoding. That way you can see if that part is working.
That seem to be pretty normal, at least directly after starting the airspy_adsb service.
I see this in my logs every time i am starting/restarting the service, but then never again.
Are the dump1090-fa settings done properly so that it connects to the airspy stream and not any longer try to find the rtl stick?
Thanks again for the replies and advice… I will test again tomorrow… As now the kid is in bed and apparently me going up and down into the loft will wake them up
Will be ordering a new Pi4 in any case. But still interested in getting this to work.
I ran the auto script? So assume that configured all correctly as their were no errors shown. However tonight I will do some more light reading of this thread and the github page, and tomorrow I will double check and try and figure it out.
I’d say you have the file /boot/piaware-config.txt ?
That makes the airspy-conf think you are running a piaware image and the automatic configuration doesn’t work then.
Delete the file …
Your status shows the wrong commandline for a non piaware image install.
(missing the network connect for airspy_adsb to send the data)
@wiedehopf Re: Automatic installation for readsb
I just got my AirSpy and I want to make sure I have all my bases covered before plugging it in. I’m reading your manual installation instructions on Github where you say readsb is better for X86 PC, which is what I’m using. I have both dump978-fa and dump1090-fa installed using @abcd567 scripts. Your script will remove dump1090-fa. Will it have any effect on 978? I’ll only be using the AirSpy for 1090. Thanks.
I do have this file yes… Thanks this will be the first thing I try in the morning… Many thanks.
No i’m not saying that on that page, just that i recommend it.
The dump1090-fa install script linked via that page only works with ARM and not x86 as it uses the existing package.
That would be really bad if it had. No it doesn’t.
I suppose i should check differently if it’s a piaware image …
Can someone on the piaware image check this please:
sudo piaware-config -show manage-config
i suppose it’s yes on the image, no on the package install.
OK thanks very much.
I have a piaware image at a different location.
Result of “sudo piaware-config -show manage-config” on that is “yes”
Running it on the package install… result is “no” (the device I am having the issue on)
Just changed the airspy conf script, should work as expected for you now.
Genius! That worked like a charm this time round… pretty much plug and play. Small issue with graphs1090 but resolved once I did reinstall/update.
I am not precious about it, but I seem to have lost graph data back to midnight? Is that a known issue? I didn’t take a backup, but is there an easy way to avoid that for anyone that does similar in future?
Going to let it run for a bit so I can see where it’s baseline is and then start tinkering with gain etc.
@wiedehopf , thank you so much for helping, you (and everyone else who posts here) makes this the best adsb community that I know of!