Announcement

Collapse
No announcement yet.

Linux feeder software for Flightradar24 (Old software)

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ptl
    replied
    Hi,

    what do I need to do if/when I want to have several "antennas" for one "feeder"?

    Here is the set-up I've been thinking:

    Feeder host
    - running fr24feed and feeding to FR24
    - runs dump1090 (with --net-only if there is no DVB-T stick)
    - can have a DVB-T stick
    - just one per site

    Antenna host
    - does not run fr24feed
    - has a DVB-T stick and runs dump1090
    - 1-2 per site, different antenna configuration/location

    The motivation is mainly to test new antennas without disturbing steady the feed to FR24.

    I can have 1+2 hosts (all with DVB-T sticks) at home and 1+1 (both with DVB-T sticks) at the garage (different location, i.e. different feed with separate key).

    My very first idea was to do this:

    nc antennahostX 30002 | nc feederhost 30001
    but I'm not sure if this works, the number of total usable messages does not seem to add up.

    I was expecting that the number of total usable messages from the feeder is the sum of number of total usable messages from all the antennas, but this does not seem to be the case.

    I have --stats-every 600 so I see the summary every 10 minutes, although the reporting periods are not exactly the same, it depends on when each dump1090 was started, but since I live in an area that does not have the sky full of flights all the time I can compare the number of messages somewhat accurately. Simplified example: one flight goes by, antenna1 has 3 messages, antenna2 has 4 messages, and the feeder (with it's own antenna) has 6 messages.

    Many of the messages are (or at least should be) duplicates, does the feeder dump1090 ignore these (identical messages received about the same time)?

    Or is this completely wrong? Is 30002/30001 the right port pair, or should I use 30005/30004? The fr24feed connects to 30003, which is BaseStation output port, but dump1090 does not have BaseStation input port.

    -Paavo
    Last edited by ptl; 2014-11-29, 09:36.

    Leave a comment:


  • n6ly
    replied
    Originally posted by obj View Post
    Quick bug report: the feeder exhausts available file descriptors after a while and stops feeding data properly. The website stats show the feeder "online" but no data available.

    Logs have periodic complaints with errno 24 (24 is EMFILE - "too many open files"):

    Code:
    [n]pinging the server
    [i]sent 37 planes in 1 packets
    [i]sent 37 planes in 1 packets
    [i]sent 36 planes in 1 packets
    [i]sent 34 planes in 1 packets
    [e]Socket is not valid, errno: 24
    [i]sent 36 planes in 1 packets
    [e]Socket is not valid, errno: 24
    The process file descriptors look like this:

    Code:
    pi@rpi ~ $ sudo lsof -p 2129
    COMMAND    PID USER   FD   TYPE    DEVICE SIZE/OFF      NODE NAME
    fr24feed_ 2129 adsb  cwd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  rtd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  txt    REG     179,2   791538    144509 /usr/local/adsb/bin/fr24feed_arm-rpi_242
    fr24feed_ 2129 adsb  mem    REG     179,2    71528      7920 /lib/arm-linux-gnueabihf/libresolv-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    18040      5520 /lib/arm-linux-gnueabihf/libnss_dns-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    42692      7880 /lib/arm-linux-gnueabihf/libnss_files-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2  1200240      7900 /lib/arm-linux-gnueabihf/libc-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   130448      1885 /lib/arm-linux-gnueabihf/libgcc_s.so.1
    fr24feed_ 2129 adsb  mem    REG     179,2   427628      7431 /lib/arm-linux-gnueabihf/libm-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   800736      1249 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.19
    fr24feed_ 2129 adsb  mem    REG     179,2    87792      5181 /lib/arm-linux-gnueabihf/libz.so.1.2.7
    fr24feed_ 2129 adsb  mem    REG     179,2   116462      7878 /lib/arm-linux-gnueabihf/libpthread-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    10170     25003 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so
    fr24feed_ 2129 adsb  mem    REG     179,2   126236      7434 /lib/arm-linux-gnueabihf/ld-2.13.so
    fr24feed_ 2129 adsb    0r   CHR       1,3      0t0        21 /dev/null
    fr24feed_ 2129 adsb    1w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    2w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    3u  IPv4 360960925      0t0       UDP *:41058 
    fr24feed_ 2129 adsb    4u  IPv4 264769977      0t0       TCP localhost:47243->localhost:30003 (ESTABLISHED)
    fr24feed_ 2129 adsb    5r  FIFO       0,9      0t0 305654561 pipe
    fr24feed_ 2129 adsb    6r  FIFO       0,9      0t0 269894173 pipe
    fr24feed_ 2129 adsb    7r  FIFO       0,9      0t0 256578387 pipe
    fr24feed_ 2129 adsb    8r  FIFO       0,9      0t0  45787475 pipe
    [... lots more ...]
    fr24feed_ 2129 adsb 1021r  FIFO       0,9      0t0 305610871 pipe
    fr24feed_ 2129 adsb 1022r  FIFO       0,9      0t0 305654149 pipe
    fr24feed_ 2129 adsb 1023w  FIFO       0,9      0t0 359848218 pipe
    This is using "fr24feed_arm-rpi_242". The process has been up for a bit over a month at this point (but it might have stopped feeding a while back - I don't check it too often)
    I'm having the same problem. This is the second time in a month that this has happened.

    Leave a comment:


  • jeffwingo
    replied
    Done that. There are people on this one that are doing what I am trying to do. I look forward to hearing from them.

    Leave a comment:


  • equi
    replied
    You know, PiAware is from FlightAware - maybe you should get in touch on their Forums

    Leave a comment:


  • jeffwingo
    replied
    I could use some configuration help.
    I have a Raspberry Pi and have installed both FR24FEED and PIAWARE. The FR24 is working great but PIAWARE is working at all.
    pi@raspberrypi ~ $ sudo piaware-status
    dump1090 is not running.
    faup1090 is not running.
    piaware is not running.
    no program appears to be listening for connections on port 30005.
    no program appears to be listening for connections on port 10001.
    piaware is NOT connected to port 10001.
    piaware is NOT connected to FlightAware.
    got 'couldn't open socket: connection refused'
    maybe dump1090 is NOT producing data on port 30005.
    got 'couldn't open socket: connection refused'
    maybe dump1090 is NOT producing data on port 10001.
    I also noticed that after installing everything, there are three folders where dump1090 exists. Can someone give me some insight as to how I get piaware working alongside fr24. If you need to see any files or configurations, help me by being explicit as to how to get what you need to see since I am new to LINUX.

    Leave a comment:


  • Ressy
    replied
    Originally posted by ptl View Post

    Roughly how often the stat pages are updated, i.e. how long does it take (min/max/typical) berore the flights seen and reported by my feeders get to the stat pages?

    -Paavo
    hourly or so, and the day/date resets at 0000 UTC

    Leave a comment:


  • obj
    replied
    Quick bug report: the feeder exhausts available file descriptors after a while and stops feeding data properly. The website stats show the feeder "online" but no data available.

    Logs have periodic complaints with errno 24 (24 is EMFILE - "too many open files"):

    Code:
    [n]pinging the server
    [i]sent 37 planes in 1 packets
    [i]sent 37 planes in 1 packets
    [i]sent 36 planes in 1 packets
    [i]sent 34 planes in 1 packets
    [e]Socket is not valid, errno: 24
    [i]sent 36 planes in 1 packets
    [e]Socket is not valid, errno: 24
    The process file descriptors look like this:

    Code:
    pi@rpi ~ $ sudo lsof -p 2129
    COMMAND    PID USER   FD   TYPE    DEVICE SIZE/OFF      NODE NAME
    fr24feed_ 2129 adsb  cwd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  rtd    DIR     179,2     4096         2 /
    fr24feed_ 2129 adsb  txt    REG     179,2   791538    144509 /usr/local/adsb/bin/fr24feed_arm-rpi_242
    fr24feed_ 2129 adsb  mem    REG     179,2    71528      7920 /lib/arm-linux-gnueabihf/libresolv-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    18040      5520 /lib/arm-linux-gnueabihf/libnss_dns-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    42692      7880 /lib/arm-linux-gnueabihf/libnss_files-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2  1200240      7900 /lib/arm-linux-gnueabihf/libc-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   130448      1885 /lib/arm-linux-gnueabihf/libgcc_s.so.1
    fr24feed_ 2129 adsb  mem    REG     179,2   427628      7431 /lib/arm-linux-gnueabihf/libm-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2   800736      1249 /usr/lib/arm-linux-gnueabihf/libstdc++.so.6.0.19
    fr24feed_ 2129 adsb  mem    REG     179,2    87792      5181 /lib/arm-linux-gnueabihf/libz.so.1.2.7
    fr24feed_ 2129 adsb  mem    REG     179,2   116462      7878 /lib/arm-linux-gnueabihf/libpthread-2.13.so
    fr24feed_ 2129 adsb  mem    REG     179,2    10170     25003 /usr/lib/arm-linux-gnueabihf/libcofi_rpi.so
    fr24feed_ 2129 adsb  mem    REG     179,2   126236      7434 /lib/arm-linux-gnueabihf/ld-2.13.so
    fr24feed_ 2129 adsb    0r   CHR       1,3      0t0        21 /dev/null
    fr24feed_ 2129 adsb    1w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    2w   REG     179,2 35906793    271294 /var/log/adsb/fr24feed.log
    fr24feed_ 2129 adsb    3u  IPv4 360960925      0t0       UDP *:41058 
    fr24feed_ 2129 adsb    4u  IPv4 264769977      0t0       TCP localhost:47243->localhost:30003 (ESTABLISHED)
    fr24feed_ 2129 adsb    5r  FIFO       0,9      0t0 305654561 pipe
    fr24feed_ 2129 adsb    6r  FIFO       0,9      0t0 269894173 pipe
    fr24feed_ 2129 adsb    7r  FIFO       0,9      0t0 256578387 pipe
    fr24feed_ 2129 adsb    8r  FIFO       0,9      0t0  45787475 pipe
    [... lots more ...]
    fr24feed_ 2129 adsb 1021r  FIFO       0,9      0t0 305610871 pipe
    fr24feed_ 2129 adsb 1022r  FIFO       0,9      0t0 305654149 pipe
    fr24feed_ 2129 adsb 1023w  FIFO       0,9      0t0 359848218 pipe
    This is using "fr24feed_arm-rpi_242". The process has been up for a bit over a month at this point (but it might have stopped feeding a while back - I don't check it too often)

    Leave a comment:


  • feci
    replied
    Hello,

    signup via the feeder for linux (using Ubuntu 14.04) does not work.
    dump1090 on the other works flawlessly.
    See the thread that I've opened: http://forum.flightradar24.com/threa...-from-the-quot
    I tried both the x86 and 64bit clients.
    If anyone had this problem please reply.

    Leave a comment:


  • ptl
    replied
    Hi,

    Hi, just reporting that fr24feed_arm-rpi_242 works well on top of dump1090 (from https://github.com/MalcolmRobb/dump1090) on a fairly basic Raspi.

    This is what I did

    # git clone & make etc. to build dump1090
    # wget & tar etc. to get latest fr24feed_xxx_xxx

    # remove dvb_usb_rtl28xxu kernel module if it is present
    if [ -n "$(lsmod | grep dvb_usb_rtl28xxu)" ] ; then rmmod dvb_usb_rtl28xxu ; fi

    tmpdir="$(pwd)" # save current working dir
    workdir="/path/to/smewhere" # need to have the dump1090 public_html dir here
    cd "$workdir" # to find ./public_html directory and e.g. gmap.html file in it

    # going to replace "--stats-every 600" with "--quiet" when I get the antenna done
    nohup /path/to/dump1090 --net --fix --aggressive --stats-every 600 > /var/log/dump1090.log 2>&1 < /dev/null &

    cd "$tmpdir" # back to original working dir
    sleep 1 # sleep a while to allow dump1090 to start properly, not sure if this is really needed

    # use /path/to/fr24feed_x64_242 in the bigger box
    nohup /path/to/fr24feed_arm-rpi_242 --fr24key=mykey --bs-ip=localhost --bs-port=30003 > /var/log/fr24feed.log 2>&1 < /dev/null &
    All of that was really straight forward both in Raspi and in a Fedora 20 x86_64 box where my other receiver is connected to.
    About the only extra things I needed to do were to install some libusbxx-devel packages in the Fedora, and Raspi needed a reboot after various mumudvb etc. tests (using dvb_usb_rtl28xxu kernel module) before dump1090 started to work.

    But I have a question, too: my receivers have seen and reported several flights during the last hour or so,
    but my stat pages (https://www.flightradar24.com/premiu...s.php?id=14xxx) do show these yet.

    Roughly how often the stat pages are updated, i.e. how long does it take (min/max/typical) berore the flights seen and reported by my feeders get to the stat pages?

    Warm thanks to everybody who have built FR24 service and enabled contributing interesting data so easily and with dirt-cheap HW.
    I paid 40€ or the Raspi with a 2A power supply, and 10€ a pop for the DVB-T sticks.

    Now I need to build a better antenna for both receivers, probably going following this guidance: http://antirez.com/news/46

    -Paavo
    Last edited by ptl; 2014-11-09, 10:00.

    Leave a comment:


  • loplo
    replied
    Any of the compiled versions compatible with openwrt?

    Leave a comment:


  • Angelus1971
    replied
    Originally posted by Angelus1971 View Post
    Hi

    It came back about 10 mins ago. I thought the data was live but it looks like it on a 1hr update, I'll see around 12:15 this afternoon as it hasn't updated in the last 10 mins. It seems to be fine. All the data is there, not gaps just not as it happens (within reason and processing etc etc...)

    Not a new Pi, just an OS update and I'm trying to move all my feeds to the Pi - just not sure about Planefinder as I've been told it hogs the CPU - might try it on an B+ and see what happens.
    I'm using 242 - is there a newer build?

    Thanks
    That's an update - 1hr 6 mins after last one - that must be the update schedule.

    Leave a comment:


  • Angelus1971
    replied
    Originally posted by peterhr View Post
    FR24 stats seem to go vanisf for 20 minutes before and after any periods when you are offline.

    If this is a new Pi, make sure you are using version 241 feeder or later (the earlier ones don't update stats)

    Hi

    It came back about 10 mins ago. I thought the data was live but it looks like it on a 1hr update, I'll see around 12:15 this afternoon as it hasn't updated in the last 10 mins. It seems to be fine. All the data is there, not gaps just not as it happens (within reason and processing etc etc...)

    Not a new Pi, just an OS update and I'm trying to move all my feeds to the Pi - just not sure about Planefinder as I've been told it hogs the CPU - might try it on an B+ and see what happens.
    I'm using 242 - is there a newer build?

    Thanks
    Last edited by Angelus1971; 2014-10-30, 11:29.

    Leave a comment:


  • peterhr
    replied
    Originally posted by Angelus1971 View Post
    Hi

    I've got a build from last week for my Pi, and Malcolm Robbs dump1090 fork and everything was working fine until I decided to feed to Flight Aware with PiAware this morning.

    Everything seems ok. FR24 logs says its sending a/c to the server and I have seen my Feed on the Fr24 world feed. Flight Aware stats are showing I'm feeding there also.

    What has stopped is the updates on my FR24 statistics page. Even though I am feeding a/c and positions (according to the logs) and they are showing (stats says I'm online and seen ~5mins), my main graph stats and aircraft positions reported
    stats have stopped updating.

    The stats say I went offline at 10:01 this morning (its now 10:57) and that's when my PiAware went live (ish) - It was actually about 3-4 mins before that.

    So, has the stats page broken or is PiAware affecting what seem to be a working connection?


    Thanks
    FR24 stats seem to go vanisf for 20 minutes before and after any periods when you are offline.

    If this is a new Pi, make sure you are using version 241 feeder or later (the earlier ones don't update stats)

    Leave a comment:


  • Angelus1971
    replied
    Originally posted by peterhr View Post
    yes - do make sure your dump1090 is up to date though
    Hi

    I've got a build from last week for my Pi, and Malcolm Robbs dump1090 fork and everything was working fine until I decided to feed to Flight Aware with PiAware this morning.

    Everything seems ok. FR24 logs says its sending a/c to the server and I have seen my Feed on the Fr24 world feed. Flight Aware stats are showing I'm feeding there also.

    What has stopped is the updates on my FR24 statistics page. Even though I am feeding a/c and positions (according to the logs) and they are showing (stats says I'm online and seen ~5mins), my main graph stats and aircraft positions reported
    stats have stopped updating.

    The stats say I went offline at 10:01 this morning (its now 10:57) and that's when my PiAware went live (ish) - It was actually about 3-4 mins before that.

    So, has the stats page broken or is PiAware affecting what seem to be a working connection?


    Thanks

    Leave a comment:


  • peterhr
    replied
    yes - do make sure your dump1090 is up to date though

    Leave a comment:

Working...
X