Results 1 to 4 of 4

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
    1,874

    How to Feed Data to Multiple Sites - A Brief Guide

    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

    1. Pi24 image from Flightradar24.com
      1. Burn microSD card with Pi24 image. This image contains: Raspbian Jessie Lite OS + dump1090 (MR) + fr24 data feeder.
      2. Install Planefinder, Flightaware and Radarbox24 feeders from respective sites.

      The above installation does not work OK for Planefinder and Flightaware feeders, for following reasons: [S O L V E D - For Workaround, see next two posts].

      • 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.



    2. 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.


    3. 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

    1. If NO external decoder (like dump1090 MR, dump1090-mutability, dump1090-fa, or ModeSDeco2) is installed and only integral dump1090 of Pi24 or the fr24feed package install is used, then:
      • Select "Receiver: DVB-T". See screenshot below.
      • Set "Process Arguments: --net --net-http-port 8080" to see map.
        The map will be displayed in Browser at http://<IP of Pi>:8080
      • If feeders of other sites are also installed, set "Process Arguments: --net --net-http-port 8080 --net-bo-port 30005"
      • To change gain of Receiver (DVB-T) from default 49.6, set "Process Arguments: --net --net-http-port 8080 --net-bo-port 30005 --gain xx" , where xx is the gain value you want to set.



      Pi24 no ext dump - config.png


    2. If an external decoder (like dump1090 MR, dump1090-mutability, dump1090-fa, or ModeSDeco2) is installed, then select "Receiver: AVR(TCP)" and "HOST/IP: 127.0.0.1:30002". See screenshot below.

      Pi24+dump1090 - config.png


    GOOD LUCK!
    Last edited by abcd567; 2017-11-21 at 16:07.

  2. #2
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    1,874
    [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; 2017-06-19 at 04:22.

  3. #3
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    1,874
    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

    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; 2017-06-19 at 10:54.

  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.

Posting Permissions

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