I struggle with steting up my RPI to send data to FlightAware:
I am owning a ADS-B USB Dongle and it is connected to my Pi.
Then I followed the instructions on the tutorial site of FlightAware and i think everything went fine. I entered my username and password an restartet the service but unfortunalety no data is recieved by FlightAware, though i waited no for two days.
Since i have not the best knowledge about linux and the software used, does anyone has an idea what i could do?
I am running Rasbian Jessy, the piaware service is running (checked with services --status-all). Though there are no logs (or i didn’t find them, lol)
When the transmission to FlightAware is working, i also want to transmit my data to FlightRadar24, so i installed the software for that (but it isn’t currently running). When i installed the FR24 software, i was asked about long/lat/height of the reciever, which wasn’t the case when i installed the FlightAware software, so i wonder if i have to do this as well=
Well, that was also my thought, isn’t there a command to start dump1090 like i can start piaware? Unfortunalety i can’t set up an another sd-card the next days, so it would be great if i could manage to get it run as it is?
So, i checked everything again and found out, that i added the dump1090 package, but didn’t installed it (yes, newbie fault lol).
Now dump1090 is installed and running and when i enter dump1090 it says the device is busy…is it because piaware uses it?
pi@raspberrypi:~ $ sudo dump1090
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
usb_claim_interface error -6
Error opening the RTLSDR device: Device or resource busy
pi@raspberrypi:~ $ sudo dump1090
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
usb_claim_interface error -6
Error opening the RTLSDR device: Device or resource busy
I restartet piaware service and waiting now if everything is fine now and appears on the statistic page, or do you have further suggestions?
Likely a DVB kernel driver is running and claiming the dongle before dump1090 can. Do a lsmod and look for dvb_usb_rtl28xxu. If it is there, you need to blacklist it. Google for the instructions to blacklist, they are readily found.
This is probably a combination of USB/power problems + bugs in librtlsdr.
The “cb transfer status” message means that librtlsdr got a USB error trying to receive data from the dongle (this is the USB/power problem). Then it hangs while trying to shut down and exit (this is the librtlsdr bug).
The dongle did work for a little while though, you got a few messages before it broke.
Check your USB cabling and power. The “dmesg” command may give some hints too (look for USB related messages)
Definitely shed some hardware; try it without the cam and the extension cable. Look in dmesg for "USB disconnect"s, which usually means that something on the USB ran out of power.
It isn’t the problem here yet but I will mention that when you start dump1090 from the command line without the --net option (and maybe some others), it can receive aircraft, but won’t be able to link to piaware and thus you won’t upload anything. Once you have dump1090 running steady on the command line mode, reboot and let everyhing start automatically.
After rebooting, run piaware-status and you should see something like this:
...
piaware is connected to FlightAware.
dump1090-mutabi is producing data on port 30005.
Note that I’m running a different dump1090, yours will probably say dump1090-fa instead. But these last two lines prove a lot; that you have both piaware and dump1090 running, the Pi is connected to the Internet, and it is receiving signals from aircraft. The “is producing data” test actually waits for a signal (or the 1 minute “heartbeat” default packet), so if you check it late at night when air traffic is rare, it may take a while to appear.
Also you can use ps aux to confirm that dump1090 and piaware both auto-started and continue to run.
pi@raspberrypi:~ $ sudo piaware-status
dump1090 is running.
faup1090 is running.
piaware is running.
dump1090 is listening for connections on port 30005.
faup1090 is connected to port 30005.
piaware is connected to FlightAware.
dump1090 is NOT producing data on port 30005.
Also on the stats page it is shown now! Thank you verymuch!