Announcement

Collapse
No announcement yet.

How to Feed Data to Multiple Sites - A Brief Guide

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • abcd567
    replied
    It seems you have older version of OS(Stretch or Buster), and trying to install a piaware version for Bullseye. To know your OS version, please issue following command and post it's outputs.

    lsb_release -a

    NOTE
    The piaware packages are available for both the Bullseye and Buster, but their installation commands are different


    .
    Last edited by abcd567; 2022-07-06, 14:22.

    Leave a comment:


  • Oblivian
    replied
    Thats to do with your pi/version of OS. Not really the installer
    there is a command after
    : Unable to correct problems, you have held broken packages.

    It suggests running. Start there.
    But depending on space/when you installed it. The version may not be supported which will need
    Apt-get update
    and possibly
    apt-get dist- upgrade

    Leave a comment:


  • nick223
    replied
    trying to install flightaware on my FR24 image but when i try to install piAware i get this any idea on a fix?

    The following packages have unmet dependencies:
    piaware : Depends: libboost-program-options1.74.0 (>= 1.74.0) but it is not installable
    Depends: libboost-regex1.74.0-icu67 but it is not installable
    Depends: libc6 (>= 2.29) but 2.28-10+rpt2+rpi1 is to be installed
    Depends: libffi7 (>= 3.3~20180313) but it is not installable
    Depends: libgcc-s1 (>= 3.5) but it is not installable
    Depends: libmpdec3 but it is not installable
    Depends: libreadline8 (>= 7.0~beta) but it is not installable
    Depends: libstdc++6 (>= 9) but 8.3.0-6+rpi1 is to be installed
    E: Unable to correct problems, you have held broken packages.

    Leave a comment:


  • Antonf
    replied
    Originally posted by abcd567 View Post
    Assuming that 192.168.0.12 is IP address of Flightaware feeder,

    Host/IP 127.0.0.1:30005

    Should be changed to

    Host/IP 192.168.0.12:30005
    OMW, what a very basic mistake to make!
    Thanks a lot abcd567!

    Leave a comment:


  • abcd567
    replied
    Assuming that 192.168.0.12 is IP address of Flightaware feeder,

    Host/IP 127.0.0.1:30005

    Should be changed to

    Host/IP 192.168.0.12:30005

    Leave a comment:


  • Antonf
    replied
    I have a Flightaware feeder and I want to feed to FR24.
    I installed the latest FR24 image on a new Raspberry 3B sitting right next to the Flightaware feeder but get an error that the receiver is down.
    What can I do to rectify that?
    Edit: In the image below MLAT is still YES, I changed it after I made the screenshot.

    Settings:
    FR24 settings.jpg
    Last edited by Antonf; 2022-06-10, 10:56.

    Leave a comment:


  • Dilandau
    replied
    Hi,
    for me it took some minutes to get the right settings for the planefinder client. I am using the Pi image provided from FR24 with a DVBT-Stick.

    fr24setting.png

    So I needed to configure the PF client to Port 30002:

    pf.png

    Now, I can also see planes there.

    Leave a comment:


  • panosig
    replied
    Originally posted by abcd567 View Post
    panosig:

    Sometimes RB24 feeder wrongly sets itself to use its integral dump1090. The integral dump1090 of RB24 grabs the DVB-T, because of which there is no DVB-T dongle left fo use by dump1090-mutability and it fails. Also as RB24's dump1090 does not output data on port 30005 from which other feeders can get it, all other feeders fail.


    Please open file rbfeeder.ini

    Code:
    sudo nano /etc/rbfeeder.ini
    Check that network_mode is set to true, and port & host are set as shown below in red
    Code:
    [client]
    [Color=#ff0000][b]network_mode=true[/b][/color]
    log_file=/var/log/rbfeeder.log
    key=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    sn=EXTRPI000nnn
    
    [network]
    [Color=#ff0000][b]mode=beast
    external_port=30005
    external_host=127.0.0.1
    [/b][/color]

    If different from above, edit the file to make red entries as shownabove. Alternatively instead of editing the file /etc/rbfeeder.ini, you can fix the wrong & missing entries by commands shown below:

    Give following 4 commands one by one:

    Code:
    sudo rbfeeder --set-network-mode on --no-start   
    
    sudo rbfeeder --set-network-host 127.0.0.1 --no-start   
    
    sudo rbfeeder --set-network-port 30005 --no-start   
    
    sudo rbfeeder --set-network-protocol beast --no-start
    After above 4 commands you must restart rbfeeder by following command:

    Code:
    sudo systemctl restart rbfeeder
    After restart, give following command and post its output:

    Code:
    cat /etc/rbfeeder.ini

    Hi again

    i follow the instructions and everything seems to be ok.

    Below you can see the log you asked for

    log_file=/var/log/rbfeeder.log

    key=***********************************

    sn=EXTRPI00******

    [network]
    mode=beast
    external_port=30005
    external_host=127.0.0.1

    [mlat]

    I am thankful for your help.

    Leave a comment:


  • abcd567
    replied
    panosig:

    Sometimes RB24 feeder wrongly sets itself to use its integral dump1090. The integral dump1090 of RB24 grabs the DVB-T, because of which there is no DVB-T dongle left fo use by dump1090-mutability and it fails. Also as RB24's dump1090 does not output data on port 30005 from which other feeders can get it, all other feeders fail.


    Please open file rbfeeder.ini

    Code:
    sudo nano /etc/rbfeeder.ini
    Check that network_mode is set to true, and port & host are set as shown below in red
    Code:
    [client]
    [Color=#ff0000][b]network_mode=true[/b][/color]
    log_file=/var/log/rbfeeder.log
    key=aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    sn=EXTRPI000nnn
    
    [network]
    [Color=#ff0000][b]mode=beast
    external_port=30005
    external_host=127.0.0.1
    [/b][/color]

    If different from above, edit the file to make red entries as shownabove. Alternatively instead of editing the file /etc/rbfeeder.ini, you can fix the wrong & missing entries by commands shown below:

    Give following 4 commands one by one:

    Code:
    sudo rbfeeder --set-network-mode on --no-start   
    
    sudo rbfeeder --set-network-host 127.0.0.1 --no-start   
    
    sudo rbfeeder --set-network-port 30005 --no-start   
    
    sudo rbfeeder --set-network-protocol beast --no-start
    After above 4 commands you must restart rbfeeder by following command:

    Code:
    sudo systemctl restart rbfeeder
    After restart, give following command and post its output:

    Code:
    cat /etc/rbfeeder.ini
    Last edited by abcd567; 2019-10-11, 22:15.

    Leave a comment:


  • panosig
    replied
    Hi
    I have an armbian orange pi with dump1090-mutability v1.15 + fr24 + Flightaware + Planefinder + OpenSky Network data feeders
    Everything used to work smooth for about 2 years until a week ago that i decide to install Radarbox24 feeder.
    After installation all feeders stop to send data and only Radarbox24 feeder works.
    Any suggestions?

    Thanks in advance.
    Last edited by panosig; 2019-10-11, 16:34.

    Leave a comment:


  • sander815
    replied
    i am trying to install piaware as additional feeder, but i cannot get it running
    i think because its listening on port 30005?
    no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s

    I have dump1090 mutability running, because i wanted to have openstreetmap in fr24 map. Maybe thats the problem?

    pi@raspberrypi:~/ dump1090 $ sudo service piaware status
    ● piaware.service - FlightAware ADS-B uploader
    Loaded: loaded (/ lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
    Active: active (running) since Sun 2019-09-01 13:20:11 UTC; 14min ago
    Main PID: 1263 (piaware)
    CGroup: /system.slice/piaware.service
    └─1263 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json

    Sep 01 13:32:40 raspberrypi piaware[1263]: attempting to start dump1090..
    Sep 01 13:32:40 raspberrypi piaware[1263]: can't start dump1090, no services that look like dump1090 found
    Sep 01 13:32:50 raspberrypi sudo[1507]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --nume
    Sep 01 13:32:50 raspberrypi sudo[1507]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Sep 01 13:32:50 raspberrypi sudo[1507]: pam_unix(sudo:session): session closed for user root
    Sep 01 13:32:50 raspberrypi piaware[1263]: no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
    Sep 01 13:33:50 raspberrypi sudo[1516]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --nume
    Sep 01 13:33:50 raspberrypi sudo[1516]: pam_unix(sudo:session): session opened for user root by (uid=0)
    Sep 01 13:33:51 raspberrypi sudo[1516]: pam_unix(sudo:session): session closed for user root
    Sep 01 13:33:51 raspberrypi piaware[1263]: no ADS-B data program seen listening on port 30005 for 71 seconds, next check in 60s

    Leave a comment:


  • abcd567
    replied
    Originally posted by arash
    Which one is ok for VM?

    This thread is for Raspberry Pi, and NOT for VM on Windows PC or Mac.

    For VM, please see this thread:

    Feed options for depreciated windows feeder
    Last edited by abcd567; 2019-07-09, 19:31.

    Leave a comment:


  • abcd567
    replied
    Originally posted by wiedehopf
    The bundle i made is an alternative to dump1090-mutability 1.15.

    The bundle will remove 1.15 and install dump1090-fa.
    But the dump1090-mutability map is still offered using the data from dump1090-fa.

    Upon using the uninstall for the bundle it will go back to dump1090-mutability 1.14.
    (Or to 1.15 if you installed it via the method i linked before)

    Doesn't matter when you install the bundle, it should install and remove cleanly, pretty much no matter what you did before
    Yesterday I have tested wiedehopf's bundle on PI24 image, first install and then later uninstall.
    Both worked perfectly well. emoji-3.png


    (1) PI24 image - After running Install
    wiedehopf-1.14-to-3.7.1.png


    (2) PI24 image - After running Uninstall - Back to normal
    wiedehopf-3.7.1-to-1.14.png

    Leave a comment:


  • wiedehopf
    replied
    You might want to take a look at this:
    Solutions to common problems using dump1090 variants and ADS-B feeders - wiedehopf/adsb-wiki


    and maybe this:

    Leave a comment:


  • wiedehopf
    replied
    Independent of that, you really want dump1090-mutability 1.15:

    Code:
    sudo bash -c "$(wget -O - https://raw.githubusercontent.com/abcd567a/dump1090/master/PI24_replace_dump1090_v1.14_by_v1.15.sh)"
    (as discussed here: https://forum.flightradar24.com/thre...l=1#post122259)

    Otherwise you can't for example feed flightaware and take part in their MLAT because version 1.14 can't handle MLAT results.
    Generally version 1.15 is better.

    Or you might even like dump1090-fa some day, but let's stick with 1.15 for now.

    Leave a comment:

Working...
X