Results 1 to 7 of 7

Thread: How to Feed Data to Multiple Sites - A Brief Guide

  1. #1
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,031

    How to Feed Data to Multiple Sites - A Brief Guide

    Last update - April 14, 2018:

    It has become very common that users want to install multiple feeders to feed multiple sites like FlightRadar24, Flightaware, Planefinder, Adsbexchange, Radarbox24, etc etc.

    Basically feeding to any site requires following software:
    (1) An Operating System like Noobs, Raspbian, Ubuntu etc.
    (2) A Decoder software like dump1090 MR, dump1090-mutability, dump1090-fa, ModeSDeco2 etc.
    (3) An exclusive data feeder for each site like fr24feed (FlightRadar24), Piaware feeder (Flightaware), PFClient (Planefinder), rbfeeder (RadarBox24) etc. The data feeder of a Flightaware & Adsbexchange (which provides feedback of MLAT results) also have a built-in MLAT Client.

    Various Options to Install Software

    (A) Pi24 image from Flightradar24.com
    1. Burn microSD card with Pi24 image. This image contains: Raspbian Jessie Lite OS + dump1090-mutability v1.14 + fr24 data feeder.
    2. Powerup and signup by command sudo fr24feed --signup.
    3. Configure FR24 Feeder as shown below
    4. Install Planefinder, Flightaware and Radarbox24 feeders from respective sites.


    (B) Raspbian image from Raspberrypi.org
    1. Burn microSD card with Raspbian Jessie Lite image. This image contains only Operating system.
    2. Install either dump1090-mutability or dump1090-fa
    3. Install Flightradar24, Flightaware, Planefinder, Adsbexchange, and Radarbox24 feeders from respective sites.


    (C) Piaware image from Flightaware.com
    1. Burn microSD card with Piaware SD card image. This image contains: Raspbian Jessie Lite OS + dump1090-fa + Piaware data feeder
    2. Install Flightradar24, Planefinder, Adsbexchange, and Radarbox24 feeders from respective sites.


    FR24 FEEDER CONFIGURATION

    OPTION-1:
    If If NO external decoder (like dump1090 MR, dump1090-mutability, dump1090-fa, or ModeSDeco2 etc) is installed,
    and you want to use dump1090-mutability v1.14 provided by Pi24, then:
    • Select "Receiver: DVB-T". See screenshot below.
    • Set "Process Arguments: --net --lat xx.xxxx --lon yy.yyyy".
    • To see map, in your Browser type address http://<IP of Pi>/dump1090/gmap.html
    • If Flightaware feeder Piaware is also installed, you will need to enable MLAT input to port 30104. To do this, set "Process Arguments: --net --net-bi-port 30104 --lat xx.xxxx --lon yy.yyyy"
    • To change gain of Receiver (DVB-T) from default "max" (=49.6), add --gain to process arguments like this: "Process Arguments: --net --net-bi-port 30104 --lat xx.xxxx --lon yy.yyyy --gain zz" , where zz is the gain value you want to set.

    fr24feed setting using integral dump1090-mutability v1.14.png


    OPTION-2:
    If an external decoder (like dump1090 MR, dump1090-mutability, dump1090-fa, or ModeSDeco2) is installed, then select:

    "Receiver: ModeS Beast (TCP)" and "HOST/IP: 127.0.0.1:30005"
    OR
    "Receiver: AVR(TCP)" and "HOST/IP: 127.0.0.1:30002".

    See screenshot below.

    fr24feed setting BEAST-TCP using dump1090-fa or dump1090-mut v1.15.png . fr24feed setting AVR-TCP using dump1090-fa or dump1090-mut v1.15.png


    BLOCK DIAGRAMS
    FR24 Block Diagram - Receiver DVBT-2.png . FR24 Block Diagram - Receiver AVR or Beast-2.png
    Last edited by abcd567; 2018-04-14 at 06:43.

  2. #2
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,031
    Last update, April 14, 2018:
    The problem and solution given below existed in the Pi24 at the time this post was originally written.
    The current version Pi24-2.0.0 does not have this problem, and the solution given below is neither needed nor applicable to it.


    The installation of Planefinder and Flightaware feeders on Pi24 does not work OK for following reasons:
    • The Planefinder feeder, which works ok on install, crashes when Pi is rebooted, and fails to start even manually by command "sudo systemctl restart pfclient".
    • Flightaware MLAT results feed-back is not displayed on map. The built-in dump1090 (MR) does not have facility to keep MLAT feedback separate from the data received by DVB-T and combine it only on map display.

      This facility is available in dump1090-mutability and dump1090-fa. Unfortunately if dump1090-mutability or dump1090-fa is installed on Pi24 image, map display stops. The reason is that both dump mutability and dump fa display map through lighttpd, which fails to start when istalled on Pi24. Even giving command "sudo systemctl restart lighttpd" does not succees to start it.



    [S O L V E D]:
    Failure of lighttpd and pfclient on Pi24 image.

    Code:
    sudo systemctl status lighttpd -l
    
    raspberrypi systemd[1]: Started Lighttpd Daemon.
    raspberrypi lighttpd[631]: 2017-06-17 20:24:34: (log.c.118) opening errorlog '/var/log/lighttpd/error.log' 
    failed: No such file or directory
    raspberrypi systemd[1]: lighttpd.service: main process exited, code=exited, status=255/n/a
    raspberrypi systemd[1]: Unit lighttpd.service entered failed state.

    Code:
    sudo systemctl status pfclient -l
    
    Starting pfclient: pfclient/etc/init.d/pfclient: 35: /etc/init.d/pfclient: cannot create /var/log/pfclient/error.log: 
    Directory nonexistent
    raspberrypi pfclient[539]: failed!
    Manually created following folders and files:

    folder /var/log/lighttpd and file /var/log/lighttpd/error.log

    folder /var/log/pfclient and file /var/log/pfclient/error.log

    On reboot found all these folder and files are deleted, and lighttpd and pfclient again failed.

    WORKAROUND
    Arranged to recreate needed folders & files at boot, by adding following code to file rc.local just before last line (exit0).
    Code:
    sudo nano /etc/rc.local
    
    #added following lines at the end of file, just before exit0
    
    mkdir -p /var/log/lighttpd
    touch /var/log/lighttpd/error.log                
    chmod 666 /var/log/lighttpd/error.log            
    systemctl restart lighttpd
    
    mkdir -p /var/log/pfclient                       
    touch /var/log/pfclient/error.log
    chmod 666 /var/log/pfclient/error.log
    systemctl restart pfclient
    Now lighttpd, dump1090-mutability, Piaware data feeder and Piaware MLAT feed-back plane's display on map, are all working OK on Pi24 image.
    .
    Last edited by abcd567; 2018-04-14 at 06:52.

  3. #3
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,031
    The Pi24 image has a tmpfs entry for /var/log folder in it's /etc/fstab file.
    This entry causes deletion of contents of /var/log folder on reboot.

    Pi24 image
    Code:
    cat /etc/fstab
    proc            /proc           proc    defaults          0       0
    /dev/mmcblk0p1  /boot           vfat    defaults          0       2
    /dev/mmcblk0p2  /               ext4    defaults,noatime  0       1
    tmpfs   /var/log    tmpfs    defaults,noatime,nosuid,mode=0755,size=100m    0 0
    Update April 10, 2018
    Above comments about Pi24 were valid for the version current at the time this post was originally written. These comments are no more applicable to the current version Pi24-2.0.0.

    Raspbian Jessie image
    In Respbian Jessie image tmpfs entry is not there, and that is why the contents of folder /var/log are not deleted on reboot
    Code:
    cat /etc/fstab
    proc            /proc           proc    defaults          0       0
    PARTUUID=b2dfebce-01  /boot           vfat    defaults          0       2
    PARTUUID=b2dfebce-02  /               ext4    defaults,noatime  0       1
    # a swapfile is not a swap partition, no line here
    #   use  dphys-swapfile swap[on|off]  for that


    Piaware 3.5.0 image
    In Piaware image, tmpfs entry is there, but the folder /var/log is not associated with tmpfs entry, and that is why the contents of folder /var/log are not deleted on reboot
    Code:
    cat /etc/fstab
    /dev/mmcblk0p1 /boot vfat defaults 0 2
    /dev/mmcblk0p2 / ext4 errors=remount-ro,noatime 0 1
    tmpfs /tmp tmpfs defaults,nodev,nosuid 0 0
    Last edited by abcd567; 2018-04-11 at 01:18.

  4. #4
    Passenger TomNJerry's Avatar
    Join Date
    Nov 2017
    Posts
    2
    This is a very comprehensive, useful and important guide. Deserves to be made sticky.

  5. #5
    Passenger
    Join Date
    Apr 2018
    Posts
    1
    Hi abcd thanks for that great guide!

    I just set the fr24 port to 30005 instead of 30002 and it started working.

    It kinda makes sense because we just set the fr24 to Beast tcp input but 30002 is the raw output of dump1090 and 30005 is the beast output.
    Or am I confusing this?

  6. #6
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,031
    @wiedehopf:
    Any of the following two settings are valid. Personally I prefer Beast setting.

    "Host/IP = 127.0.0.1:30002" is used with "Receiver = AVR(TCP)".

    "Host/IP = 127.0.0.1:30005" is used with "Receiver: ModeS Beast (TCP)".

    FR24 Settings with dump1090-fa or mut for multiple feed by Pi.png

  7. #7
    Passenger
    Join Date
    Apr 2018
    Posts
    1
    @abcd567 I'm sorry i accidentally selected beast with fr24feed --reconfigure (running on an x86_64 debian right now).

    So of course it wasn't working.

    Thank you for clarifying.

    P.S.: Also if you install piaware manually alongside fr24 it's nice to manually visit flightaware /adsb/piaware/claim/FEEDER_ID
    with feeder_id replaced with the id piaware shows you on the command line since you don't have piaware-web (i mean you could install it)
    (had to compile all the stuff too, but i guess all that does not really belong here)

  8. #8
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,031
    @wiedehopf

    Some times ago, I have installed both FR24 feeder and Piaware feeder on following OS by compiling its .deb package from source:

    1. Ubuntu 16.04 x86_64 on my Desktop with intel processor.

    2. Raspbian Jessie x86 rpd desktop running in Oracle VM on my Windows 8.1 Desktop.

    I used J Prochazka's automated scripts which detect the architecture and compile the package automatically. I have created following thread in this forum in Sept 2016, describing J Prochazka's method:

    Automated Installation of Dump1090-Mutability, Data Feeders, and Performance Graphs

    .
    Last edited by abcd567; 2018-04-10 at 15:38.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •