ADS-B Receiver Project Setup Scripts

My install wasn’t on a clean system. The second install went well with the same 30104 issue.
Took a few seconds to fix.
:slight_smile:

due to an errant / in a mv command (not recommended to ever type this on your pi: sudo mv /* /xxxxx), I had to do a quick reimage and rebuild this AM. All worked well, just a couple items to note (I haven’t had a chance to do any troubleshooting as I had to do a quick rebuild and get out the door):

  1. browsing to the IP wanted to start with blog.php rather than dump1090, which 404 errored
  2. When you say No to check for updates, it still checks

Feature request:

  1. Maybe have a disk size check prior to starting for those of us who are in a hurry and forget to expand the filesystem
  2. ability to enter PPM offset in the setup script
  3. ability to assign non-standard html port (eg. something other than 80)
  4. quiet install. Have it ask me for everything it needs up front and once I hit go, I can walk away

Good job on the script!!!

I got this on my second install too “2. When you say No to check for updates, it still checks”

@usafpride
You can change the default web page by logging into the administration area found at your-ip-address/admin/.
The default login name and password are:
Login: admin
Password: adsbfeeder
(You will be propted to change these credentials after your first login.)

@usafpride and @jonhawkes2030
Regarding updates.
What you see run is the command apt-get update. In order to avoid issues when installing prerequisite packages it is some times necessary to re-synchronize the package index files from their sources which is what this command does. In order to be safe the command is ran each time install.sh is ran. The command apt-get update does not install newer versions of any software. However if you choose to update the command apt-get upgrade is ran which does in fact install newer packages after apt-get update.

@usafpride

Feature request:

  1. Maybe have a disk size check prior to starting for those of us who are in a hurry and forget to expand the filesystem
  2. ability to enter PPM offset in the setup script
  3. ability to assign non-standard html port (eg. something other than 80)
  4. quiet install. Have it ask me for everything it needs up front and once I hit go, I can walk away

Some good ideas here I will see what I can do to accommodate them.
The quiet install is surely something I plan to look into once installation logging is in place.

when you say >
for those of us who are in a hurry and forget to expand the filesystem < how do you do that ? I remember reading it here some where long ago and even I think did it but cant for the life of me know how or where now , when I format my 8 g sd with sdformat windows reports 7.xx gig but once I put it in my pie it reports it as around 4 gig and runs out of memory with Jessie installed when trying to run the script

sudo raspi-config


sudo fs_resize

thanks guys yep remember now , just another senior moment

I installed the updated graphs with admin. Awesome work. I was able to install this last night on my other Pi with no issues. But tonight I am having a issue. I have Dump1090, Dump978, Piaware and the graphs installed.

When I goto my Pi IP address, I get a 404 error. But I am able to goto 192.168.0.1/admin with no issue. I know on the other graphs before the admin add, I used to type just the IP of the Pi and go right to the graphs and dump.

Any help would be great. Thanks for all the hard work on this awesome project.

I have finished update of my yesterdays install, and noted following problem:
(1)Web admin portal main page, which appeared when I typed the ip address of RPi, does not appear anymore. Instead another page “blog.php” appears which has only “404 - Not Found”.

(2) I feed adsbexchange not on port 30005, but another port 3xxxxx, which shows my receiver name not “us-east xxxxx”, but “CYYZ-1”. In yesterday’s installed when I noted piaware.out file showing connection refused to feed.adsbexchange.com:30005, I edited adsbexchange-maint.sh and changed the port number from " nc feed.adsbexchange.com 30005" to 3xxxx, rebooted the RPi, and piaware log stopped to show “failed to connect to adsbexchange”, and receiver CYYZ-1 started showing on feed.adsbexchange.com/VirtualRadar site.

I was able to get it to show the map and graphs…

I want to Pi IP/dump1090.php

Is there a way to see if UAT 978 s running or working. I can see the map on the graphs. I have 2 dongles plugged in.

Thanks.

Same with me… feed.adsbexchange.com:3005 = Errno 110

It works for me. I saw my first aircraft today after running it for a few weeks. I was just lucky.
I don’t see very many. I can go for days without a log entry.

It should autostart. If the webpage does show an error, they it has started.

check the logs /var/log/dump978.log

-08ace1943a34f1960aa02d691012ab401f0cd21385ed2d0bbaa5e080002c50000000;rs=4;
-00ace1943a34f19609dc2d691012ab602a00;rs=1;
-00ace1943a34ef9609682d69100eabe02900;rs=3;
-10ace1943a34ef9608cc2d69100eabe0290000000000000000000000002c50000000;rs=4;
-08ace1943a34eb9606382d69100eabe02f0cd21385ed2d0b76a5e080002c50000000;rs=7;
-00ace1943a34eb9605c22d69100eabc01900;rs=3;
-10ace1943a34e996048c2d69100eabc01f0000000000000000000000002c50000000;rs=2;
-00ace1943a34e99604162d69100eabc01800;rs=2;
-00ace1943a34e79603062d69100eac401800;rs=4;
-08ace1943a34e79602422d69100eac40180dea3d50e6c40bfaa5e280002c50000000;rs=5;
-00ace1943a34e79601f42d69100eac401a00;rs=5;
-00ace1943a34e395ff842d69100eac401900;rs=3;

Ok. Does it auto start or do you have to start dump978 with a command? I used Dump978 before, but not this way. Thanks.

Taken following steps to resolve adsbexchange connection [Err111] in piaware log.



pi@raspberrypi:~ $ sudo cp adsb-feeder/build/adsbexchange/adsbexchange-maint.sh /etc/init.d/adsbexchange-maint.sh

pi@raspberrypi:~ $ sudo chmod  +  /etc/init.d/adsbexchange-maint.sh

pi@raspberrypi:~ $ sudo reboot


Still unable to connect to adsbexchange.

adsbexchange-maint.sh seems ok



pi@raspberrypi:~ $ cat adsb-feeder/build/adsbexchange/adsbexchange-maint.sh

#! /bin/sh
while true
  do
    sleep 30
    /bin/nc 127.0.0.1 30005 | /bin/nc feed.adsbexchange.com 30005
  done

pi@raspberrypi:~ $


Now piaware says error110 timed out:



mlat(1071): Beast-format results connection with feed.adsbexchange.com:30005: [Errno 110] Connection timed out


My setup added the following to /etc/rc.local
/home/pi/adsb-feeder/build/dump978/dump978-maint.sh &

For info, ADSBExchange running fine for me, feeder US-East-51141
CYYZ-1 does show as big red “splat” on feed.adsbexchange.com/VirtualRadar/desktop.html# but no traffic.

I did not add 978 during the install.

Phill

Solved the problem of piaware unable to feed adsbexchange, as shown in code below, and feed.adsbexchange.com/VirtualRadar started showing planes for Receiver CYYZ-1 (both the MLAT & non-MLAT).


 
pi@raspberrypi:~ $ sudo piaware-config -mlatResultsFormat "beast,connect,localhost:30104" 
pi@raspberrypi:~ $ sudo service piaware restart

pi@raspberrypi:~ $ sudo piaware-config -show
contents of piaware config file '/root/.piaware':
mlatResultsFormat beast,connect,localhost:30104
password xxxxxxxx
user xxxxxxxx


pi@raspberrypi:~ $ sudo nano /etc/rc.local
#inserted the following line just before the last line (exit 0)
adsb-feeder/build/adsbexchange/adsbexchange-maint.sh &
#saved & exit rc.local
pi@raspberrypi:~ $ cd adsb-feeder/build/adsbexchange/
pi@raspberrypi:~ $ sudo chmod 755 ./adsbexchange-maint.sh
pi@raspberrypi:~ $ sudo reboot


EDIT: Later removed line “adsb-feeder/build/adsbexchange/adsbexchange-maint.sh &” (which I have inserted) as found that a line “home/pi/adsb-feeder/build/adsbexchange/adsbexchange-maint.sh &” was already there. Rebooted, and Receiver CYYZ-1 continued showing on feed.adsbexchange.com/VirtualRadar/desktop.html

Adsbexchange is now fed through rc.local+script “adsbexchange-maint.sh”, and the burden has been taken off Piaware.



pi@raspberrypi:~ $ cat /tmp/piaware.out
01/29/2016 10:30:41 ****************************************************
01/29/2016 10:30:41 piaware version 2.1-5 is running, process ID 554
01/29/2016 10:30:41 your system info is: Linux raspi-2 4.1.13-v7+ #826 SMP PREEMPT Fri Nov 13 20:19:03 GMT 2015 armv7l GNU/Linux
01/29/2016 10:30:41 Connecting to FlightAware adept server at piaware.flightaware.com/1200
01/29/2016 10:30:41 Connection to adept server at piaware.flightaware.com/1200 failed: couldn't open socket: no such device or address (Temporary failure in name resolution)
01/29/2016 10:30:41 reconnecting in 96 seconds...
01/29/2016 10:30:41 ADS-B data program 'dump1090-mutabi' is listening on port 30005, so far so good
01/29/2016 10:30:41 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.580 --lon -79.624
01/29/2016 10:30:41 Started faup1090 (pid 750) to connect to dump1090-mutabi
01/29/2016 10:30:42 piaware received a message from dump1090-mutabi!
01/29/2016 10:31:11 33 msgs recv'd from dump1090-mutabi; 0 msgs sent to FlightAware
01/29/2016 10:32:17 Connecting to FlightAware adept server at piaware.flightaware.com/1200
01/29/2016 10:32:17 Connection with adept server at piaware.flightaware.com/1200 established
01/29/2016 10:32:17 FlightAware server SSL certificate validated
01/29/2016 10:32:17 encrypted session established with FlightAware
01/29/2016 10:32:17 autoUpdate is not configured in /etc/piaware or by piaware-config
01/29/2016 10:32:17 manualUpdate is not configured in /etc/piaware or by piaware-config
01/29/2016 10:32:17 multilateration support enabled (use piaware-config to disable)
01/29/2016 10:32:18 logged in to FlightAware as user xxxxxxxx
01/29/2016 10:32:18 multilateration support enabled (use piaware-config to disable)
01/29/2016 10:32:18 multilateration data requested, enabling mlat client
01/29/2016 10:32:18 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --udp-transport 70.42.6.197:7599:4044916507
01/29/2016 10:32:19 mlat(1055): fa-mlat-client 0.2.4 starting up
01/29/2016 10:32:19 mlat(1055): Using UDP transport to 70.42.6.197:7599
01/29/2016 10:32:19 mlat(1055): Input connected to localhost:30005
01/29/2016 10:32:19 mlat(1055): Beast-format results connection with localhost:30104: connection established
01/29/2016 10:32:23 piaware has successfully sent several msgs to FlightAware!
01/29/2016 10:36:11 355 msgs recv'd from dump1090-mutabi (322 in last 5m); 240 msgs sent to FlightAware
01/29/2016 10:41:11 728 msgs recv'd from dump1090-mutabi (373 in last 5m); 613 msgs sent to FlightAware
01/29/2016 10:46:11 1075 msgs recv'd from dump1090-mutabi (347 in last 5m); 960 msgs sent to FlightAware
01/29/2016 10:47:19 mlat(1055): Receiver status: connected
01/29/2016 10:47:19 mlat(1055): Server status:   synchronized with 28 nearby receivers
01/29/2016 10:47:19 mlat(1055): Receiver:  111.4 msg/s received      2.0kB/s from receiver
01/29/2016 10:47:19 mlat(1055): Server:      0.2 kB/s from server    0.0kB/s TCP to server   0.6kB/s UDP to server
01/29/2016 10:47:19 mlat(1055): Results:  79.3 positions/minute
01/29/2016 10:47:19 mlat(1055): Aircraft: 4 of 9 Mode S, 9 of 20 ADS-B used
pi@raspberrypi:~ $