Good to know.
Thanks for looking into that for me.
Anyways that was a bit more involved than I expected…
It looks like I have the issue pointed out by abcd567 pertaining to the graphs straightened out as well as a few others items effected by the issue he found. Most of my testing today has been within a virtual machine with no SDR dongle attached. However I did upgrade my advanced portal features development machine from v2.3.0 to v2.4.0 no problem. There is not much more I can do as far as testing goes on an actual device until I am able to find more free time later tonight.
Until then those who are impatient can feel free to have a go at v2.4.0 which is available now in the repository contained within the master branch.
Or wait for the official announcement and images I hope to have released this evening after I am done testing things out on an actual physical device.
This release adds dump1090-fa support as well as an easier way to update the adsb-receiver repository.
With the addition of dump1090-fa support there are now two images available for use.
adsb-receiver_2.4.0_dump1090-fa_raspbian-jessie-lite.zip Contains both dump1090-fa and PiAware preinstalled as well as the packages needed to setup the web portal.
adsb-receiver_2.4.0_dump1090-mutability_raspbian-jessie-lite.zip The image everyone is used to seeing released containing dump1090-mutability as well as the packages needed to setup the web portal.
I am looking forward to hearing your feed back especially pertaining to the dump1090-fa addition.
In the mean time back to work on twitter and email notifications…
Joe, so I have read this right, the mutability map version the normal setup as we are use to, with updates, and the portal package already installed for the portal. The FA version, obviously the FA map, piaware and the option to install the portal if required?? In essence, the main change is that you have added the portal features to a FA version of 1090??
I take it that you need to make the first choice of FA or mutability before installing, no changing once down loaded and installed, within the system?
Do you have to fresh install or can you update a pre existing version, is the option to go FA or muta, in that update procedure?
@ abcd. Re your recent posts about adding colour to the system, this procedure will still work, just applying it to what ever version you chose to go with and I take it you go the FA way, you don’t have to worry about changing the .php to FA, that is already done.
Correct. The dump1090-mutability image is more or less what was offered in the past. The main difference between the two images is of course dump1090-fa is installed in place of dump190-mutability and being PiAware is pretty much a requirement for dump1090-fa Piaware is installed as well. The portal has been modified to work with dump1090-fa as well as dump1090-mutability and the same code is used for both.
Just a little FYI as to how things work as far as the portal and image are concerned. The portal technically isn’t “installed” on the image. A couple releases back I decided to only install the prerequisite packages for the portal on the image in order to save time getting the receiver up and running. However when running install.sh the first time to set up the image the files making up the portal itself are put into place and the needed setup is performed. This route was chosen in order to not install extra items and packages not needed by some portal installation options. On top of that doing this this way makes it easier for me to maintain the image.sh file being I no longer have two separate portal setup scripts to modify when a change is needed.
Yes choose carefully. When executing the setup process on a fresh image you will be presented with the option to choose to install either dump1090-mutability or dump1090-fa. You must choose one in order to continue. If you choose to install dump1090-fa PiAware will be installed as well no ifs, ands, or buts about it. At this time the only way to switch between the two will be to start over from scratch. Of course you can back up any pertinent information and files before doing so so that you do not loose data as in the past. All data collected and saved pertaining to the portal is transferable.
Updating existing setups remains the same as in the past to get to this version. However after installing this version install.sh will automatically update the local adsb-receiver repository so there will no longer be a need to run the Git update commands prior to running install.sh to upgrade items. There is no upgrade path to switch from dump1090-mutability to dump1090-fa available so if you wish to switch you will need to set things up on a new image and transfer over any data you wish to preserve to the new receiver.
I may or may not look into adding the ability to change the version of dump1090 being used in the future. Right now I would rather focus efforts on adding features to the portal.
TL;DR
Yes it adds the portal to a manually built dump1090-fa/PiAware setup.
You cannot “easily” switch between dump1090-mutability and dump1090-fa once one is chosen.
You can upgrade existing ADS-B Receiver Project receivers the same way as in the past to get to this version.
You cannot “upgrade” from dump1090-mutability to dump1090-fa.
Started the adsb-receiver_2.4.0_dump1090-mutability_raspbian-jessie-lite.img install as per instruction on this page, github.com/jprochazka/adsb-rece … iver-Image, on a clean formatted 4g SD card.
Thanks Joe, well explained. With the FA version, it still disables the auto update at the FA end, when looking at your FA stats, as it is with the muta version now??
With the FA version, still the option to add ADS-B exchange feeding as now?? I think thats it… lol
Jeff
SUCCESSFULL INSTALL OF “adsb-receiver_2.4.0_dump1090-mutability_raspbian-jessie-lite.img”
Map OK
Data feeders Piaware, Planefinder, Flightradar24, and Adsexchange OK
Graphs OK
SUCCESSFULL INSTALL OF “adsb-receiver_2.4.0_dump1090-fa_raspbian-jessie-lite.img”
On ALL pages, the menu button “Live Dump1090 Map” opens page xxx.xxx.xx.xx/dump1090.php which shows 404 - Not Found.
Map displayed by manually typing the address xxx.xxx.xx.xx/dump1090-fa/index.html OK
Data feeders Piaware, Planefinder, Flightradar24, and Adsexchange OK
Graphs OK
Successful install of both Fa and muta 2.4 versions . Same issue as abcd re the map for FA version and same fix worked. Realised how versatile the muta version is in tweaking things I.E. tweaking gains, so I think I will stay with the muta version at this time. All very good. Well done Joe
This change is not needed on receivers running dump1090-mutability.
I committed a change to the repository to allow cross-origin resource sharing for the virtual dump1090 directory which may fix this issue. If you already have a v2.4.0 receiver setup either execute install.sh and select to reinstall the portal or add the following to the file /etc/lighttpd/conf-available/89-adsb-portal.conf.
My planefinder feeder stopped after redoing the whole shebang yesterday. I thought I checked yesterday and I thought it was working, but I am not sure. It is not feeding this morning.
Everything else in the script worked and I did the FA-Mutablilty directory swap so my DUMP1090 looks great.
The first time I did the script, several days ago, Plane Finder feed started right up.
This morning, I reviewed the steps, even went back to the web and configured again. It all appears good, but I am not feeding. Any ez troubleshooting or fixes?
Thanks Joe for update, but before you posted it, I have done a work-around for menu button “Live Dump1090 Map” showing “404 NOT FOUND” as follows:
cd ~
#preserved the original file dump1090.php by renaming it, to enable revert
sudo mv /var/www/html/dump1090.php /var/www/html/original-dump1090.php
#created a new blank file dump1090.php
sudo nano /var/www/html/dump1090.php
#added following code in blank file, saved (ctrl+o) exit (ctrl+x)
<?php
header('Location: /dump1090-fa/index.html');
?>
#now clicked menu button "Live Dump1090 Map" and it opened page http://xxx.xxx.xx.xx/dump1090-fa/index.html
@abcd567
Appreciate the work around and those encountering the issue and need the feature up and running right away should use it. However it is defiantly not a long term fix and would break things for those choosing to use dump1090-mutability. I modified things to add the additional Lighttpd configuration lines and uploaded a new dump1090-fa image to the release page. Guess we will see where that leads us. Sadly it is an issue I cannot recreate using the image even after using the image three times now…
As stated before you can test out the change by executing install.sh and choosing to reinstall the portal when asked.
@jcinnb
Check the pfclient logs which should be located in the directory /var/log/.
UPDATED
After setting up the dump1090-fa image I went ahead and installed the Planfinder ADS-B Client and am feeding data to them no problem. Make sure your sharecode is right and the settings were typed in properly in particular:
Data Format: Beast
Tcp Address: 127.0.0.1
Tcp Port: 30005
