I will look into that this evening.
Only had my live feeder to test on and it was not a clean install instead an upgrade so I did not install PiAware.
Confirmed both show 403 - Forbidden.
I updated portal and have some more minor, even cosmetic things:
- etho instead of eth0 on selection button in admin area
- I don’t have dump978, but: title of dump978 page says Live Dump1090 map
- dump978, when it obviously can’t connect to dump978, it says: Maybe dump1090 is no longer running?
- imperial/metric selection does not seem to have any effect: I always have km for range and Celsius for temp. Besides, my preference is nm for range and Celsius for temperature, so a simple metric/imperial switch may not be enough
- etho instead of eth0 on selection button in admin area
Fixed.
- I don’t have dump978, but: title of dump978 page says Live Dump1090 map
I don’t have a mechanism in place yet to detect what is and is not installed. For now remove the links using the Navigation Settings in the admin area.
**- dump978, when it obviously can’t connect to dump978, it says: Maybe dump1090 is no longer running? **
That’s the default message displayed when the map is not receiving data from dump978 just like dump1090’s map because that’s what it is.
Again until I am able to put together a way to detect what is and is not installed simply uncheck the Enable live dump978 map link setting.
- imperial/metric selection does not seem to have any effect: I always have km for range and Celsius for temp.
Fixed. Seems I misspelled measurement in all but a couple places…
There were changes made to 4 files including settings.xml file. Might be easier to pull the changes using git and install just the portal again.
Besides, my preference is nm for range and Celsius for temperature, so a simple metric/imperial switch may not be enough
Something to add to the todo list. Things are a bit simplistic at the moment but more refinement will be in the works shortly.
Everyone thanks for the extra pairs of eyes it helps a lot. The little things get missed so easily when you have been staring at the stuff so long. 
thx for your work
but
bandwith usage (wlan0) , memory… and disc i.o
are not working again ;(
ive update to the latest version
What I meant to say was that some dump978 pages still refer to dump1090 in the title and the ‘cannot connect’ message. I guess they should all refer to dump978 instead.
In my previous install (which was done using jprochazka’s script before current upgrade), I added dump978 gmap.html following the procedure given by Oliver (obj) on dump978 github page, which I am copying below, with some modifications, as detailed in note below the code.
Map generation via uat2json
uat2json writes aircraft.json files in the format expected by dump1090’s map html/javascript.
To set up a live map feed:
- Get a copy of dump1090, we’re going to reuse its mapping html/javascript:
$ git clone github.com/mutability/dump1090 dump1090-copy
- Put the html/javascript somewhere your webserver can reach:
$ mkdir /var/www/html/dump978
$ cp -a dump1090-copy/public_html/* /var/www/html/dump978/
- Create an empty “data” subdirectory
$ mkdir /var/www/html/dump978/data
- Feed uat2json from dump978:
$ rtl_sdr -f 978000000 -s 2083334 -g 48 - | \ ./dump978 | \ ./uat2json /var/www/html/dump978/data
#item 4) not executed, see note (3) below.
- Go look at localhost/dump978/gmap.html
NOTE:
(1) path in github page was /var/www/. Used instead /var/www/html/ (for jessie)
(2) new folder name proposed in github was dump978map. Used dump978 to match jprochazka’s script.
(3) I did not execute step (4) as this was already included in jprochazka’s file adsb-feeder/build/dump978/dump978-maint.sh
(4) Tweaked config.js & gmap.html (both in /var/www/html/dump978 folder) to change title from “dump1090” to “dump978”.
Screenshot taken when there were no UAT planes, which appear only occassionally after long wait.
I would be interested as am sure many would
I think I got everything reported fixed in the admin branch including:
- dump1090 text showing on dump978 map.
- dump978 startup line being added each time scripts were ran.
- dump978 maintenance script being appended instead of being over written each run.
- Unwanted rtl_sdr modules are blacklisted when dump978 is installed fixing one of the errors outputted constantly.
- dump978 outputting to the terminal. (Still seeing output but only once when started but no longer repeats. Will be looking into suppressing all output tomorrow.)
Anyways my main feeder has been down now for a few hours so time to plug my secondary RTLSDR dongle back in and get it up and running again so I am done for the night…
Those who used the admin branch before 1/27/2016 at 1:00 AM should update their adsb-feeder files and execute install.sh and choose to reinstall the portal to apply changes made to the portal. If you chose the option to build dump978 when executing install.sh choose to rebuild dump978 as well.
Anyone capable of receiving UAT data your feedback would be greatly appreciated in regards to dump978. It is hard for me to confirm everything is working due to the fact I do not receive much UAT data without my 978MHz antenna up in the air.
Once dump978 is confirmed to be working and if no other issues are found I will be merging the admin branch into the master branch for public consumption.
(tomorrow I will try to address any other issues pertaining to specific feeders. You are not forgotten about!)
Started install on Fresh Jessie image.
Installation of dump978 is now complete.
Please look over the output generated to be sure no errors were encountered.
Press enter to continue…Found 2 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001
1: Realtek, RTL2838UHIDIR, SN: 00000001
Using device 1: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Exact sample rate is: 2083334.141630 Hz
Sampling at 2083334 S/s.
Tuned to 978000000 Hz.
Tuner gain set to 48.00 dB.
Reading samples in async mode…
#Installation halted at this point
#Installation continued after pressing Enter.
#Missing instruction “Press enter to continue…”
**ADMIN BRANCH FRESH INSTALL UPDATE **
Finished installation of the admin branch on fresh Jessie image on RPi Model2.
-
All graphs working ok
-
Dump1090 map showing ok. MLAT planes showing.
-
Piaware log ok, MLAT connected to port 30104.
-
Dump978 - waiting fot UAT planes to appear (these appear only occasionally)
(a) Dump978 map showing ok, but no UAT planes yet.
(b) File /var/log/dump978.log is empty now.
(c) Site marker & range circles were not shown, tweaked config.js in /var/www/html/dump978 folder. Now showing.
-
Planefinder datafeeder & map working ok.
-
Adsbexchange working ok (checked from piaware.out and feed.adsbexchange.com/VirtualRadar/desktop.html)
-
Manually installed Flightradar24 MLAT enabled feeder - sudo bash -c “$(wget -O - repo.feed.flightradar24.com/install_fr24_rpi.sh)”. Working ok.
.
DUMP978 UPDATE:
Checked dump978 log file about 3 hours after installation, found only one entry. Decoded it, found something I did not understand. Any ideas?
pi@raspberrypi:~ $ cat /var/log/dump978.log
-c7d3fd42be02f44132842ee0907baede18de23c8266080520fdcd711759f274d0347;rs=7;
pi@raspberrypi:~ $ sudo ./adsb-feeder/build/dump978/uat2text
-c7d3fd42be02f44132842ee0907baede18de23c8266080520fdcd711759f274d0347;rs=7;
HDR:
MDB Type: 24
Address: D3FD42 (reserved (7))
^Cpi@rasberrypi:~ $
It’s noise.
Oh! my only plane in 3 hrs turned out to be noise! 
You can tell it’s noise (well, probably) because
- the message itself is garbage: a bogus ICAO with a “reserved” address type and a MDB type that’s not in use AFAIK
- the raw message is tagged with rs=7 (rs for “Reed-Solomon”) which means that forward error correction fixed 7 bit errors. This is very high, right at the limit for what the RS code can handle; noise that manages to gets past the error detection/correction will tend to look like this.
(the “raw” output actually only shows the data bits; there are additional error correction bits that are also transmitted; dump978 uses those for error detection/correction then strips them off and outputs just the data bits, plus the rs= value as metadata about how much it fixed)
Thank you Oliver for detailed explanation.
This is the output I mentioned I still need to suppress. However this should not effect the installation.
I noticed last night as well just before calling it a night that the heywhatsthat.com position file is not being copied over to the dump978 folder as well.
Thanks for the info and looking into UAT for me.
Currently updating using the admin script version.
It’s been an odd day, my replacement pigtail still hasn’t arrived so ordered another. Whilst messing about I broke down the soldered coax to mcx lead and fitted an F connector/joiner/F connector with mcx lead from original mag mount pushed in. Range and a/c count increased…( where is the icon for banging head against wall?) 
Connected $10 Chinese amp, count dropped to zero…(#'~€).
I too would be interested in a full image, thanks.
I’ll report back when the pi finishes the upgrade.
Phi
Virtually seamless JP, great job.
No spare dongle for 978 and probably not much need this side of the pond, though it looks like there are a few USN a/c and a French E3C over this side of the med today.
Admin portal works fine.
eth0 graph is missing completely at the moment. Not even a place holder.
Thanks
Phill
PS I thought I’d have to redo Lignumaqua’s mods but they are still there. 
UPDATE 2 - DUMP978
Finally after a long wait, few UAT planes were there. Unfortunately, being fed up of watching deserted gmap.html, I have closed the browser, and missed these planes on the map, else I would have taken a screenshot. Anyway, I have decoded the raw data from log file. Given below are both the raw and decoded data:
EDIT: Close review revealed that “few planes” were actually one plane, as all messages are from one plane: C01FCF (ICAO address via ADS-B)
pi@raspberrypi:~ $ cat /var/log/dump978.log
-00c01fcf3e65a5900bfc084900ae37806800;rs=5;
-00c01fcf3e6671900910085900a638a08f00;rs=3;
-10c01fcf3e682f900228084900aa38a0280000000000000000000000000820000000;rs=7;
-00c01fcf3e689b900096084900ae38803f00;rs=4;
-08c01fcf3e68b990002c084900ae380048082f8b46e6c40b02a4c2a0000820000000;rs=4;
-00c01fcf3e68cb8fffea084900b238003800;rs=5;
-00c01fcf3e68ed8fff74085900ae38001800;rs=6;
-10c01fcf3e699d8ffcd8085900aa3920480000000000000000000000000820000000;rs=3;
##Above raw data decoded below:
pi@raspberrypi:~ $ sudo ./adsb-feeder/build/dump978/uat2text
-00c01fcf3e65a5900bfc084900ae37806800;rs=5;
-00c01fcf3e6671900910085900a638a08f00;rs=3;
-10c01fcf3e682f900228084900aa38a0280000000000000000000000000820000000;rs=7;
-00c01fcf3e689b900096084900ae38803f00;rs=4;
-08c01fcf3e68b990002c084900ae380048082f8b46e6c40b02a4c2a0000820000000;rs=4;
-00c01fcf3e68cb8fffea084900b238003800;rs=5;
-00c01fcf3e68ed8fff74085900ae38001800;rs=6;
-10c01fcf3e699d8ffcd8085900aa3920480000000000000000000000000820000000;rs=3;
HDR:
MDB Type: 0
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8729
Longitude: -78.7171
Altitude: 2275 ft (barometric)
N/S velocity: 42 kt
E/W velocity: -110 kt
Track: 290
Speed: 117 kt
Vertical rate: 320 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
HDR:
MDB Type: 0
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8751
Longitude: -78.7251
Altitude: 2300 ft (barometric)
N/S velocity: 40 kt
E/W velocity: -112 kt
Track: 289
Speed: 118 kt
Vertical rate: -448 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
HDR:
MDB Type: 2
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8799
Longitude: -78.7441
Altitude: 2275 ft (barometric)
N/S velocity: 41 kt
E/W velocity: -112 kt
Track: 290
Speed: 119 kt
Vertical rate: -64 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
AUXSV:
Sec. altitude: 2225 ft (geometric)
HDR:
MDB Type: 0
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8810
Longitude: -78.7484
Altitude: 2275 ft (barometric)
N/S velocity: 42 kt
E/W velocity: -112 kt
Track: 290
Speed: 119 kt
Vertical rate: 128 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
HDR:
MDB Type: 1
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8814
Longitude: -78.7495
Altitude: 2275 ft (barometric)
N/S velocity: 42 kt
E/W velocity: -111 kt
Track: 290
Speed: 118 kt
Vertical rate: 192 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
MS:
Emitter category: Light <= 7000kg
Callsign: CFMBE
Emergency status: No emergency
UAT version: 2
SIL: 3
Transmit MSO: 0
NACp: 10
NACv: 2
NICbaro: 0
Capabilities: CDTI ACAS
Active modes:
Target track type: true heading
AUXSV:
Sec. altitude: 2225 ft (geometric)
HDR:
MDB Type: 0
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8816
Longitude: -78.7502
Altitude: 2275 ft (barometric)
N/S velocity: 43 kt
E/W velocity: -111 kt
Track: 291
Speed: 119 kt
Vertical rate: 128 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
HDR:
MDB Type: 0
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8819
Longitude: -78.7515
Altitude: 2300 ft (barometric)
N/S velocity: 42 kt
E/W velocity: -111 kt
Track: 290
Speed: 118 kt
Vertical rate: 0 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
HDR:
MDB Type: 2
Address: C01FCF (ICAO address via ADS-B)
SV:
NIC: 9
Latitude: +43.8838
Longitude: -78.7587
Altitude: 2300 ft (barometric)
N/S velocity: 41 kt
E/W velocity: -113 kt
Track: 289
Speed: 120 kt
Vertical rate: -192 ft/min (from geometric altitude)
UTC coupling: yes
TIS-B site ID: 0
AUXSV:
Sec. altitude: 2225 ft (geometric)
Yes, great job by jprochazka. Installation was very smooth & trouble free, and trial run shows trouble free operation.