PiAware doesn't work on Raspberry Pi 2 with GNS 5890


#1

Hello,

I just wanna know how to set up PiAware on a Raspberry Pi 2 with a GNS 5890 dongle because when I check the status, I get this message :

dump1090 is not running.
faup1090 is not running.
piaware is running.
no program appears to be listening for connections on port 30005.
no program appears to be listening for connections on port 10001.
piaware is NOT connected to port 10001.
piaware is connected to FlightAware.
got 'couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 30005.
got 'couldn’t open socket: connection refused’
maybe dump1090 is NOT producing data on port 10001.

I need your help.


#2

03/28/2015 17:51:21 your system info is: Linux piaware 3.18.5-v7+ #225 SMP PREEMPT Fri Jan 30 18:53:55 GMT 2015 armv7l GNU/Linux
03/28/2015 17:51:21 connecting to FlightAware eyes.flightaware.com/1200
03/28/2015 17:51:22 FlightAware server SSL certificate validated
03/28/2015 17:51:22 encrypted session established with FlightAware
03/28/2015 17:51:22 autoUpdate in /etc/piaware is enabled, allowing update
03/28/2015 17:51:22 manualUpdate in /etc/piaware is enabled, allowing update
03/28/2015 17:51:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:51:22 no ADS-B producer program seen for 1 seconds (or since piaware started), will attempt to start it next check after 360 seconds…
03/28/2015 17:51:22 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/28/2015 17:51:22 logged in to FlightAware as user jeremy54
03/28/2015 17:52:05 0 msgs recv’d from (not currently connected to an adsb source); 0 msgs sent to FlightAware
03/28/2015 17:52:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:52:35 server is sending alive messages; we will expect them
03/28/2015 17:53:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:54:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:55:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:56:22 seconds since last message or startup (301) less than threshold for action (3600), waiting…
03/28/2015 17:56:22 no ADS-B producer program seen for 301 seconds (or since piaware started), will attempt to start it next check after 360 seconds…
03/28/2015 17:56:22 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/28/2015 17:56:22 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:56:52 0 msgs recv’d from (not currently connected to an adsb source) (0 in last 5m); 0 msgs sent to FlightAware
03/28/2015 17:57:23 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:58:23 no ADS-B data program is serving on port 30005, next check in 60s
03/28/2015 17:59:23 no ADS-B data program is serving on port 30005, next check in 60s


#3

Interesting device, but it may not be a RTL-SDR based device. Trying to dig up more info on it to see if it is compatible from the manufacturer’s web site only shows Windows and Android support.

Can you do a “lsusb” command and post the results?

If it is RTL based, you should see a line similar to this:
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T

Cheers!
LitterBug


#4

Thank you for your answer.

As you asked me, I copy the results :

root@piaware:~# lsusb
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
Bus 001 Device 004: ID 04d8:f8e8 Microchip Technology, Inc.


#5

I found the documentation on the manufacturers web site. http://www.gns-gmbh.com/index.php?eID=tx_nawsecuredl&u=0&file=fileadmin/user_upload/downloads/GNS_5890_Manual_EN_DE_V1.2.pdf&t=1427660223&hash=2dc79aa60e878969be89f4a3d5ed3a53
The installation instructions show steps to indicate this is a usb serial port based device. Dump1090 is not going to work with this device, but there may be other ways to feed it to piaware.

Cheers!
LitterBug


#6

Oh… Crap… I chose a bad dongle! Would you know other ways to feed it to piaware?


#7

Google for modesmixer2, it might be able to do the trick. I think it allows to take serial input and convert to a format that dump1090 can take, or piaware. I have no experience with it myself.


#8

Thank you, but I don’t know how to install modesmixer2 on raspberry pi…


#9

Easiest solution:
http://www.amazon.com/gp/product/B009U7WZCA?tag=fligh01-20
http://www.ebay.com/itm/NooElec-SDR-ADS-B-USB-Set-w-R820T-Tuner-USA-1090MHz-1090-MHz-RTL2832U-RTLSDR-/171163633489?pt=LH_DefaultDomain_0&hash=item27da25c751


#10

PiAware uses the RTL-SDR library to talk to the receiver. Any receiver that is in this library can work with PiAware.

Reddit has a compatibility list for the RTL library.
The vendor ID / USB ID can be found by running "lsusb"
reddit.com/r/RTLSDR/wiki/compatibility

To answer you question about using your specific USB stick.

PiAware can either take undecoded data directly from a RTL compatible device OR already AVR decoded data from anywhere. If you have a program that can decode ADSB messages you can feed it to PiAware with modemixer2.

Modemixer2 is a program that can feed data from one program (an ADSB decoder) to another program (PiAware). Modemixer2 doesn’t do ADSB decoding but act as a glue between programs.

amazon.com/GNS-5890-ADS-B-Re … B006VI3WAK
I checked your dongle and it says it comes with ADSB decoding software. If their software is able to output AVR format decoded messages you can send the output from the decoder to the input of PiAware with modemixer2.

I also suggest you get the RTL dongle. It is by far one of the best dongles on the market for ADSB tracking. The reviews of the GNS are saying that range on the RTL dongle is better.
It is also possible to increase the range of the RTL dongle to over 300km.