I’ve just installed a new piaware to my rasberry pi and am having some issues getting data produced by dump1090 to be seen by piaware.
I’m pretty sure that I’m missing a command to set the data to be visible over the network when starting dump1090, but I can’t figure out what it is I’m missing.
I start dump1090 through the command line using ./dump1090 --interactive --net-http-port 8081 (to avoid a clash with another use of the 8080 port)
This seems to work - I can see some entries for planes in the dump1090 output to screen, but no stats are being recorded at FlightAware (although the installation is registered)
So I’ve then checked the /tmp/piaware.out file and see the following:
03/21/2015 15:01:19 ****************************************************
03/21/2015 15:01:19 piaware version 1.20 is running, process ID 2077
03/21/2015 15:01:19 your system info is: Linux raspberrypi 3.18.7+ #755 PREEMPT Thu Feb 12 17:14:31 GMT 2015 armv6l GNU/Linux
03/21/2015 15:01:19 connecting to FlightAware eyes.flightaware.com/1200
03/21/2015 15:01:20 FlightAware server SSL certificate validated
03/21/2015 15:01:20 encrypted session established with FlightAware
03/21/2015 15:01:20 autoUpdate in adept config is enabled, allowing update
03/21/2015 15:01:20 manualUpdate in adept config is enabled, allowing update
03/21/2015 15:01:20 no ADS-B data program is serving on port 30005, next check in 60s
03/21/2015 15:01:20 no ADS-B producer program seen for 2 seconds (or since piaware started), will attempt to start it next check after 360 seconds...
03/21/2015 15:01:20 no ADS-B producer (dump1090, modesmixer, etc) appears to be running or is not listening for connections on port 30005, next check in 5m
03/21/2015 15:01:20 logged in to FlightAware as user Mrf01
03/21/2015 15:02:09 0 msgs recv'd from (not currently connected to an adsb source); 0 msgs sent to FlightAware
03/21/2015 15:02:20 no ADS-B data program is serving on port 30005, next check in 60s
03/21/2015 15:02:38 server is sending alive messages; we will expect them
03/21/2015 15:03:21 no ADS-B data program is serving on port 30005, next check in 60s
03/21/2015 15:04:21 no ADS-B data program is serving on port 30005, next check in 60s
03/21/2015 15:05:21 no ADS-B data program is serving on port 30005, next check in 60s
How do I get dump1090 and piaware to communicate over port 30005 ?
Great - thanks for that. I’ll wait until the kids are finished on minecraft and try again with an additional --net command prior to the one setting the port.
UPDATE - that worked a treat - now on line and logging data over the web. Thanks again obj
I am absolutely new to the project. I installed piaware by manual but but the pi will not receive/transmit any signal.
I couldn’t find a solution for fixing the dongle error.
I would appreciate any help.
pi@piaware ~ $ sudo piaware-status
dump1090 is running.
faup1090 is not running.
piaware is running.
dump1090 is listening for connections on port 30005.
dump1090 is listening for connections on port 10001.
piaware is connected to port 10001.
piaware is connected to FlightAware.
dump1090 is producing data on port 30005.
dump1090 is NOT producing data on port 10001.
Using device 0: Dexatek DK DVB-T Dongle (Logilink VG0002A)
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
Failed to open rtlsdr device #0.
Using device 0: Dexatek DK DVB-T Dongle (Logilink VG0002A)
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
Failed to open rtlsdr device #0.
This is normal while dump1090 is running, you need to stop dump1090 before trying rtl_test.
However - the problem is probably with the type of dongle you have.
The “Logilink VG0002A” apparently has a FCI2580 tuner (see rtl-sdr.com/forum/viewtopic.php?f=7&t=127). 1090MHz - needed for ADS-B signals - looks like it is out of range for that tuner - the supported range is “146 - 308 MHz and 438 - 924 MHz”.
Ideally if you can replace the DVB-T dongle with one that uses the R820T or R820T2 tuner (they are pretty common), then things might work better.
