1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

How to feed FlightAware with ADSBx Custom Image

Discussion in 'Tutorials' started by James, Mar 14, 2018.

  1. James

    James Administrator Staff Member

    Install the latest image from ADSBx.


    All you need to do is install the FlightAware client. Do not install dump1090-fa, this will break the feeder.

    ssh into the ADSBx Pi

    From linux or mac, for example if Pi Feeder is

    ssh [email protected] -p 3226

    password: adsb123 or if you changed it, whatever that is

    From windows - use an ssh client

    Then run the following commands .... one at a time

    cd /home/pi
    wget http://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_3.6.3_all.deb
    sudo dpkg -i piaware-repository_3.6.3_all.deb
    sudo apt-get update
    sudo apt-get install piaware
    sudo piaware-config allow-auto-updates no
    sudo piaware-config allow-manual-updates no
    sudo reboot
    Pi should reboot and connect to FlightAware

    Go to FlightAware and claim it like you normally would with a PiAware image.

    useful commands when shh'd into pi

    tail -f /var/log/piaware.log
    Last edited: Feb 14, 2019 at 6:50 PM
  2. JA Mcc

    JA Mcc New Member

    Question on PiAware - why disable updates?
  3. James

    James Administrator Staff Member

    Because do you really know what PiAware automatically does? Updates regularly break things without testing.
  4. JA Mcc

    JA Mcc New Member

    Fair enough.

    Seems a rather reasonable explanation :)
  5. James

    James Administrator Staff Member

    The ADSBx image does a lot more complex things than PiAware and PiAware does a lot of things in the interest of FA. Never let anyone auto-update anything even ADSBx. :D
  6. JA Mcc

    JA Mcc New Member

    Great point.

    Wondering aloud now... I started with the custom adsbx image - then added the rb24, plane finder, fr24, and piaware feeders. It seems like piaware (the deb installer) stomped on some of the original custom adsbx httpd settings.

    Is there any documentation to set which services and utilities are running on which http port?

    Btw was it correct to tell piaware to use beast mode data at localhost:30005? I didn’t believe it would be correct for piaware to try to control dump1090.
  7. James

    James Administrator Staff Member

    I tried to keep everything default for dump1090, etc. Grafana on 3000. Web server using lighttpd on 80. Prometheus and the exporters for it can be found in their configs.
  8. JA Mcc

    JA Mcc New Member

    Piaware also uses 80 and 8080 on their sd card build and seemingly also their Deb build. I wish their stuff was a little better documented.
  9. James

    James Administrator Staff Member

    piaware should be using lighttpd on 80 I assume .. since dump1090-fa is the same as mutability more or less at it's core
  10. JA Mcc

    JA Mcc New Member

    Cool. Thank you, by the way, for all the work you put into the custom feeder build.
  11. James

    James Administrator Staff Member

    No problem at all! More improvements coming .. I've got a few changes to make and a few ideas for additional features.
  12. AJohnsonME

    AJohnsonME New Member

    Can you update the tutorial to 3.6.3?

    had the same problem as this guy:

    discussions dot flightaware dot com/t/problem-with-reinstalling-piaware-on-raspberry-pi3-tcl-tls-is-unmet-dependency/40774/6
  13. James

    James Administrator Staff Member

    I will read the forums later but one can assume It's because FA overwrote the Raspbian software repository so they have control of the device.

    I think we just need to make an FA image that says "FU" to FA - just dump190-fa and base piaware feeder highly restricted.
    Last edited: Jan 21, 2019
  14. James

    James Administrator Staff Member

    Reading the forum this has to do with using a Jessie Pi to upgrade to the latest 3.6.3 it seems like.

    If you upgrade the Pi to Stretch, it should upgrade the repos. It is dangerous to just force Stretch software packages on prior Linux releases. Raspbian is basic and supports a lot of older ways of doing things (like emulating rc.local using systemd) but you wouldn't do this on a production server without thorough testing.

    There is a path to upgrade Jessie to Stretch. But since these images are small and typically not remote -- reburning SD card is usually the most reliable way to upgrade.