faup1090 was using the wrong constant, MODES_NET_SERVICES_NUM, rather than
FAUP_NET_SERVICES_NUM, so it ran off the end of an array binding random
ports until failing when it tried to bind the FlightAware port a second time.
Thanks to Oliver Jowett (github user "mutability") for the fix.
* Install dump1090 and faup1090 to /usr/bin (It's Linux-standard, not my
first choice.)
* Build dump1090 to expect HTML and Javascript files in
/usr/share/dump1090/public_html
* Make 'make -f makefaup1090 install' install the dump1090 HTML and Javscript
files in the above directory.
* With this build style dump1090 can be invoked from anywhere and it will
find its files.
* With --net-only switch dump1090 wouldn't look for an RTLSDR device
* Without --net-only switch dump1090 would abort if it couldn't find an RTLSDR
device.
* Now with --net --no-rtlsdr-ok dump1090 will try to find an RTLSDR device but
go ahead and start either way.
* It isn't needed.
* Also include /usr/share/dpkg/buildflags.mk in Makefile and makefaup1090
and add our compile-specific CFLAGS to the CFLAGS that sets up
so we compile with the preferred Debian build flags.
* If faup1090 can't start because the 10001 port is already in use it will now
exit with an exit status of 98 (EADDRINUSE).
* Emit the faup1090 version number if faup1090 is run with the --help argument.
* Make wicked sure we don't come up on any other ports that we shouldn't be on.
* Add "install" argument to faup1090 makefile makefaup1090.
BUGZID:
Release of COAA PlanePlotter MLAT and SMU support for RPi
ppup1090 now supports Ground Stations functions required for MLAT and
SMU operation. This is *ONLY* available for RPi and similar linux
hardware.
Also included are sample startup scripts for dump1090 only and
dump1090+ppup1090 together.
* connects to dump1090 a la ppup1090
* extracts the data, filters, batches packets and compresses to use very littl bandwidth
* requires FA "ADS-B adept" software to actually move the data.