Results 1 to 10 of 17

Thread: FR24feed uploader - Additional Info

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,751

    FR24feed uploader - Additional Info

    Feel free to post/discuss suggestions here
    http://forum.flightradar24.com/threa...4840#post74840

    This guide is not to be taken as officially sourced support information.
    It is contributor-made
    Information has been repeated many times in existing threads but skipped by most readers


    For Flightradar24 supplied HARDWARE please contact support as per supplied information pack/emails

    FR24feed Errors
    Linux/Pi feeder Specific Information
    Beast/Transponder Mouse
    ADSBScope / VRS / RTl1090
    SBS Example
    Web Config Examples

    How does it work?
    The Software is not a single application but a package that consists of 3 core parts:
    Direct hardware access libraries
    ADSB Decode software - Dump1090-Mutability 1.14
    FR24 log, filter, bundle and uploader application

    On startup the software will:
    - Scan the configuration file for your setup (answered during install)
    - Evaluate if chosen source type is native (dump1090 not used) or not (Dump1090 needed)
    - Start appropriate connection to receiver
    - Pass data to be uploaded
    - Output any connection or various errors during startup

    Collecting received data:
    FR24feed will connect to in 2 ways depending on 'receiver type' setup:

    1. Software Decoder Connection
    - Feeder will be loaded and 'liven' USB or Com port specified direct
    - Dump1090 will be launched and connect to DBVT for FR24feeder to collect (1 step)
    - FR24feeder connect to existing decoder software output (2 step required)

    2. Direct Collection
    - FR24feeder will ignore Dump1090 and connect direct to hardware (if readable device like Beast)

    Data is gathered, bundled and sent around every 5 seconds.
    Your status may falsely show 'online' if FR24 server connector is running, but have issues with data to send
    Status may show 'offline' if no data is collected or sent to server (bad reception or no traffic, Dump1090 errors).

    There are many reasons incorrect configuration and 3rd party software can cause issues if not configured correctly, So please read further!

    Web Page Configuration - (Fixing startup errors):
    This is the easiest way to check/re-configure the software when FR24feed core successfully running
    (to fix incorrect option errors entered/found on first run)

    --> http://localhost:8754 <--
    (replace localhost with the IP address of device running software)

    !You can also edit the config manually - but variable options are specific!

    USB DVBT Feeding:
    NOT ALL USB STICKS ARE THE SAME!!

    Dump1090/FR require a Realtek/RTL 28xx chipset, and E4000 or R820 tuner
    FitPower/FC will likely not not work
    http://osmocom.org/projects/sdr/wiki/rtl-sdr
    Requirements

    Users wishing to only feed FR24 should setup FR24feed without Preinstalling Dump1090 or similar, adding additional options such as --interactive will cause issues.

    Do NOT enable raw/basestation/SBS output unless you are familiar with data-flow or output settings on other software is disabled

    *Running additional software with FR24feed can be complicated. Not all instances or configuration examples can be given
    Ensure you search the following threads for further info from other helpful users:

    Raspberry Pi based

    Pi24 Image
    Pi24 is designed for first time feeders or those not familiar with linux SSH/Console. It automates the process of setting up the feed software and allocating a radar ID
    Image has a pre-installed version of Dump1090 designed for first/single setup - will allocate extra bogus radar ID during repeated setups. Use web config or 'fr24feed --reconfigure' setup after first try!


    Installs of FR24feed & PiAware or currently running Feed/Dump1090:
    If you have previously installed ADSB feeders (or Dump1090) - may be running already. In this instance configure your feeder as BEAST-TCP/AVR-TCP NOT USB DVBT or you will face errors similar to examples below

    Basics:
    - Configure FR24feed to DVBT only if first feed site (AVR-TCP/BEAST-TCP for already running Feeds)
    - if not obvious on startup add --net to additional commands to enable output ports
    - Adjust other software data source settings to read data (added by --net) on localhost:30005
    - Save and restart feeder

    *FR24feed Setup Wizard may auto-detect and assist selecting right option

    Connecting to Raspberry Pi Console
    https://www.raspberrypi.org/document...ssh/windows.md



    Other Hardware (not DVBT) Data Relay:

    The options found for RAW/Decoded and SBS data out are valid for other receivers.
    For instance RAW out enabled for a BEAST receiver will open port 30334. (While RAW using DVBT will open conflicting 2nd 30002)
    MPX/SBS out option when used with Kinetic hardware will repeat data on port 20072

    Configure Additional Software:

    Software such as VRS(virtual radar server) and ADSBScope can then be configured to NETWORK data source on those ports
    - You must start with other Server functions of these applications disabled to prevent conflict errors!


    MLAT
    MLAT contacts are server-side triangulated - Source data from Radarcape based receivers + GPS time (Primary) + RPi/DVBT/Dump1090 using NTP time tag (NOT GPS!!) secondary
    RPi MLAT will NOT be enhanced with a USB GPS module
    - due to interface/port transmission speeds adding jitter delays NTP is used for syncronised reference data

    MLAT requires 4+ in-range receivers:
    - Various combinations of Rpi + FR24 receivers contribute (1FR + 3 Pi, 2FR + 2Pi etc)
    - min. 1x FR24 receiver required in combination
    - Overlapping FR24 Receiver GPS-time MLAT prioritised
    - NTP used for commonreference on RPis alongside FR24 data
    - All receivers need to contact the same Mode-S Only aircraft (and 2+ ADSB reference aircraft).


    FR24FEED Startup Output

    Code:
    [main][i]Version: 1.0.23-8/generic < Version numbering
    [main][i]Built on Oct 16 2018 08:10:47 (/Linux/static_armel) < Build type
    [httpd][i]Server started, listening on 0.0.0.0:8754 < Started web server for configuring on :8754
    [main][i]Reader Thread Started< starting data reader
    
    [master][i]Starting processing thread < Starting data packaging
    
    [reader][i]Connecting to <receiver> via (avr-tcp://<IP: port>)
    [reader][i]Connected to the receiver, configuring 
    [reader][i]Configured, processing messages < data read and processing attempt
    [feed][i]Feed Connected < connected to data
    [feed][n]working < network connected
    [feed][i]sent 1,0 AC < sending data OK
    Code:
    ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
    Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability  --raw --mlat)
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60 dB
    Setting gain to: 49.60 dB
    Exact sample rate is: 2000000.052982 Hz
    Gain reported by device: 49.60 dB
    Breaking this down:
    Feed disabling module from stopping DVBT - normal
    DVBT stick detected
    Launching Dump1090 on-demand
    --raw = RAW time tagging is enabled - this means MLAT option checked
    --net = Advanced network out options of Dump1090 enabled (ports 30002,30003, (30005))
    --net-http-port 8080 = Set web output enabled for local radar map on http://localhost:8080


    Common Ports:
    Here you can see some examples of software that open the same live ports if options are enabled - causing errors/conflicts

    FR24:
    RAW: 30002 (DVBT) / 30334(other hardware)
    BS: 30003
    SBS: 20072
    Dump1090:
    AVR Raw out: 30002
    Beast out: 30005
    Dump1090 BS out: 30003
    AVR In: 30001
    RTL1090:
    Raw out: 31001
    BS out: 31004
    Kinetic Basestation:
    RAW out: 30006
    BS out: 30003
    SDR: 30005
    AIS: 30007
    SBS3 'standalone' mode: 10001, 30006
    Last edited by Oblivian; 2019-05-13 at 06:58.

Posting Permissions

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