Results 1 to 10 of 12

Thread: FR24feed uploader - Additional Info

Threaded View

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

    FR24feed uploader - Additional Info

    Feel free to post/discuss on this thread here

    This guide is not to be taken as a representation of officially sourced support information.
    It is contributor-made to assist in answering queries before new threads are created -
    Information has been repeated many times in existing threads but their size deters 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 developers have made a package uploader that consists of 3 core parts:
    Direct hardware access files
    FR24 log, filter, bundle and upload data 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)
    - Pass data to be uploaded
    - Output any connection or various errors during startup

    Collecting received data:
    Your data and Hardware will be connected to in 2 ways depending on receiver type:

    - Feeder will be loaded and 'liven' USB or Com port specified
    - Dump1090 will gather data and make available for FR24feeder to collect
    - FR24feeder will connect to dump1090 output

    - FR24feeder will bypass Dump1090 and connect direct to hardware (if readable format output)

    Data is gathered, bundled and sent around every 5 seconds.
    Your status may falsely show 'online' if the connector portion is running, but cannot connect to specified hardware/ports for data collection
    Status may show offline if no data is collected and sent (bad reception or no traffic)

    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/configure the software when you are sure FR24feed core app is running
    (to fix wizard setup errors found on first run)

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

    !You can also edit the config manually - but variable options will need to be known!

    USB DVBT Feeding:

    Dump1090/FR require a Realtek/RTL 28xx chipset, and E4000 or R820 tuner
    FitPower/FC will likely not not work

    Suggested to run FR24feed standalone with no software such as RTL1090 (or Dump1090) present, or any additional commands such as --interactive as this will cause new or inexperienced users issues.

    To run with other software you must first turn off data-out of other software and FR24feed RAW/Decoded and SBS options to stop conflicts

    ! These MAY be enabled after for more advanced data use again if running certain hardware and are sure nothing will conflict by doing so !

    - Reconfigure/Configure FR24feed to DVBT (or AVR-TCP mode for already running Dump1090)
    - if not already identified on launch add --net to additional commands to enable web output port (8080,30002)
    - Adjust other software data source settings to open AVR/RAW port (added by --net) on localhost:30002
    - Save and restart feeder

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

    Cross Platform
    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 MR-Dump1090 and may allocate an additional radar ID during setup questionnaire even if you had an active ID previously

    RaspberryPi with FR24feed & PiAware or currently running Dump1090:
    If you have previously installed PiAware separate (or Dump1090) - it may be installed and running standalone. In this instance configure your feeder as AVR-TCP as above NOT USB DVBT or you will face errors similar to error examples below

    AVRTCP config example when running Dump1090/Dump1090-mutability/Piaware/
    *FR24feed Setup Wizard may auto-detect running instance and assist selecting right option
    16-3-16 Developers working on fixing re-sharing of FA data incorrectly

    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 config will open 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 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 1x ADSB reference aircraft).

    Attributed on the map calculated from FR24 boxes majority:
    T-MLAT (Europe/Africa)
    T-MLAT2 (North and South America)
    T-MLAT5 (Asia/India/Japan)
    T-MLAT3 (Oceania)

    Attributed on the map calculated from RPi majority:

    FR24FEED Visual Log Checks

    [main][i]Version: 1.0.18-9/generic
    Connecting to Generic receiver via (exe://mr-dump1090.exe  --raw --net --net-http-port 8080)
    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:

    mr-dump1090.exe = Identified as Windows Dump1090 launching
    --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 = Advanced web output enabled for local radar view on http://localhost:8080

    Connecting to Generic receiver via (exe:///usr/bin/dump1090-mutability  --raw --net)
    Rpi with Dump1090 Mutability (PiAware) installed appears slightly different
    - Dump1090-MR included with FR24 package
    [reader]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    AVR (TCP) detected valid usable output ports

    If you are using a DVBT and see any errors under
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    See Below post for common issues

    Common Ports:
    Here you can see some examples of software that open live ports if built in options are enabled which can cause conflicts

    FR24 RAW: 30002 (DVBT) / 30334(other hardware)
    FR24 BS: 30003
    FR24 SBS: 20072
    RTL1090 Raw out: 31001
    RTL1090 BS out: 31004
    Kinetic Basestation:
    RAW out: 30006
    BS out: 30003
    SDR: 30005
    AIS: 30007
    SBS3 'standalone' mode: 10001, 30006
    Dump1090 AVR Raw out: 30002
    Dump1090 Beast out (if enabled): 30005
    Dump1090 BS out: 30003
    Dump1090 in: 30001 *

    *Caution with Dump1090 and other software output - it can 'listen' for data on 30001 for multi-DVB or merged feeds and re-broadcasts out 30002. If false positions are feed to this port issues can occur server end

    Some output ports can be tested in the web-browser

    For instance basestation/BS format can often be seen visiting http://localhost:30003

    For others see telnet tests below
    Last edited by Oblivian; 2017-08-13 at 21:25.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

Posting Permissions

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