Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: FR24feed uploader - Additional Info

  1. #11
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    Basic DVBT stick setup:

    DVB-T sticks must have a RTL2832U chipset and 802T/802T2 tuner.
    Those supplied with FC0013 or similar are not suitable

    DVBT.JPG

    Note
    - Don't populate HOST field
    - Don't populate COM/DEV/PATH field

    Feed from PiAware / Alternate Dump1090 version or AVR TCP capable output:

    Note
    - Requires IP/Port populated
    - Don't populate COM/DEV/PATH field*
    * - Only populate COM/DEV/PATH to dump1090 version installed if FR24FEED required to force start it on loading (not already running as service)
    - Disable other data outputs fields as controlled by external Dump1090 configuration
    - For Beast format use port 30005



    MicroADSB Stick:

    Note
    - (linux/Pi) Run sudo lsusb and dmesg | grep tty to confirm device port to populate - CASE SENSITIVE!

    MicroADSB.JPG

    Configuration planning should be based around intentions
    To Run FR24feed as the 'connector' or Decoder
    Or
    To Run FR24feed as a client behind other decoder application

    Each program has in and out data flow:

    ADSB.jpg
    Last edited by Oblivian; 2019-03-23 at 11:37.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  2. #12
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    Windows (10) Feeder Specifics - to be retired
    Last edited by Oblivian; 2019-05-13 at 07:30.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  3. #13
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    FR24 LOG FILE ROTATION


    The Log file rotation on Linux/Rpi is notorious for not clearing logs (filling SD card) or rotating correctly in some situations

    Thanks to "SlashbNL" there is an adjustment to the code that can assist here

    But still be aware, SD cards can only have a finite write count. Logs are better suited for enabling for diagnosis purpose only, or relocating to temporary flash/RAM

    sudo nano /etc/logrotate.d/fr24feed

    Modify to following:

    /var/log/fr24feed/*.log {
    daily
    missingok
    rotate 5
    compress
    su fr24 fr24
    create 0644 fr24 fr24
    copytruncate
    notifempty
    postrotate
    if
    /bin/systemctl status fr24feed.service > /dev/null ; then \
    /bin/systemctl restart fr24feed.service > /dev/null; \
    fi;
    endscript
    }
    Last edited by Oblivian; 2019-03-23 at 00:51.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  4. #14
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    Migrating USB Devices (MicroADSB/Beast/SBS) to Raspberry Pi (Linux) from Windows feeder

    Dump1090 is usually only needed for RTL USB devices (DVBT sticks) and not other USB Receivers (SBS, Beast, TransponderMouse, MicroADSB)
    Therefore some options in the FR24feed setup page become more important to control

    When setting up your desired OS/Feeder setup. Or creating/adjusting existing FR24feed config
    The default port when no other usb devices are installed to enter into the COM/DEV/PATH: field is likely to be:
    /dev/ttyUSB0

    If this does not work as expected (no AC Tracked or feeder not started), some commands are needed to confirm correct device details

    Check for device detection:
    sudo lsusb
    Result output will list the chip used to emulate a serial port on USB. For Beast:
    Bus 001 Device 006: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC

    Check for port details:
    dmesg | grep tty

    Resulting Port listed beside FTDI device:
    usb 1-1.2: FTDI USB Serial Device converter now attached to ttyUSB0

    This gives a serial device ID to add to FR24feed 'COM/DEV/PATH' field - The number may change
    /dev/ttyUSBx

    OTHER OPTIONS

    As the data from Mode-S Beast is 'native' to the feed software..
    Host/IP: Should remain blank
    Process Arguments: Should remain blank

    If using other software (Planeplotter/VRS etc) the following options become valid (as dump1090 does not run):
    RAW Data (30002/30334)
    and
    Decoded Data (30003)

    Software should now be configured for TCP connections on the above depending on data type required

    *For multiple client connections see here

    beastusb.jpg
    Last edited by Oblivian; 2019-04-04 at 08:17.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  5. #15
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    RETIRED WINDOWS FEEDER SOLUTIONS:

    WINDOWS (remains) HOST, PI FEEDER

    The trickier / likely less reliable method

    If like me, your Windows is multi-role or tasked there are alternate methods to continue to feed FlightRadar24 solely from a RPi type device
    However this requires a detailed/specific setup depending on device and software in use. And may still cause this 'bad data' reported

    Assuming you have a working windows feed receiver or Basestation setup:

    Existing Planeplotter -
    Stop data
    IO Settings
    TCP/IP Server
    Enable x | RAW x | IP 30333 (better to use non standard port to stop conflicts)
    OK
    Start feed again

    FR24feed PI Config:
    Set Receiver to beast-TCP
    Set Host/IP to <ip of windows>:30333
    Start/restart fr24feed

    Kinetic Basestation (untested) -
    When the SBS-3 is connected to BaseStation, the main data port is in use by BaseStation, and does not support a second connection. Third party applications can however still connect Via Ethernet to port 30006 on BaseStation to obtain the raw data.
    Other applications may connect to port 30003 on baseStation to obtain decoded positions and other data for aircraft
    FR24feed Pi Config:
    Set Receiver to SBSx via Basestation
    Set Host/IP to <ip of windows>:30006
    Restart + test
    Or..
    Set Receiver to avr-tcp
    Set Host/IP to <ip of windows>:30003
    Restart + test

    Potential optional requirement to allow above on SBS-3:
    Settings - Non-Volatile Memory Setting
    Select Standalone mode
    Configure feed for SBS3 Network

    WINDOWS (remains) HOST, VIRTUAL LINUX FEEDER
    aka - no new hardware spend method

    SBS + Basestation users may prefer this..

    Later testing has found it is possible to run a virtual OS under windows and feed from Basestation
    Please see this thread for instructions:

    https://forum.flightradar24.com/thre...l=1#post116947
    Last edited by Oblivian; 2019-05-13 at 08:09.
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  6. #16
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    DATA AND HOW IT RELATES TO FR24FEED AND RECEIVERS

    Aircraft send different types of small data packets.
    Much of the data you see on FlightRadar (or any track sites) is a mixture of received transponder data, database and 3rd party information grouped to populate the additional fields and calculated data

    http://woodair.net/sbs/article/bareb...ocket_data.htm

    What must be understood is the HEX displayed CAN NOT be changed as it is part of the data sent from aircraft. Hard coded to the transponder, and should be changed when aircraft exported to different country (often not)

    Only registration and other details referenced/associated to the HEX can be adjusted

    Standard message from aircraft (decoded):
    Code:
    MSG,3,333,111,7C77FA,211,2019/03/23,14:22:16.487,2019/03/23,14:22:16.487,,33000,,,-41.39008,171.26131,,,0,0,0,0
    MSG,3,333,107,C8216E,207,2019/03/23,14:22:16.487,2019/03/23,14:22:16.487,,36025,,,-40.95753,173.33350,,,0,0,0,0
    MSG,3,333,91,C81D8E,191,2019/03/23,14:22:16.487,2019/03/23,14:22:16.487,,3800,,,-43.41779,172.38673,,,0,0,0,0
    MSG,3,333,96,C8195B,196,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,21000,,,-43.68602,172.20180,,,0,0,0,0
    MSG,6,333,104,C81845,204,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,20525,,,,,,1422,0,0,0,0
    MSG,6,333,104,C81845,204,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,20525,,,,,,1422,0,0,0,0
    MSG,8,333,96,C8195B,196,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,,,,,,,,,,,0
    MSG,6,333,103,7C6B0B,203,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,26175,,,,,,5556,0,0,0,0
    MSG,6,333,104,C81845,204,2019/03/23,14:22:16.542,2019/03/23,14:22:16.542,,20525,,,,,,1422,0,0,0,0
    MSG,6,333,105,C8237A,205,2019/03/23,14:22:16.543,2019/03/23,14:22:16.543,,9925,,,,,,5553,0,0,0,0
    MSG,6,333,105,C8237A,205,2019/03/23,14:22:16.543,2019/03/23,14:22:16.543,,9925,,,,,,5553,0,0,0,0
    MSG,4,333,111,7C77FA,211,2019/03/23,14:22:16.543,2019/03/23,14:22:16.543,,,465.0,88.9,,,0,,,,,
    As the link details the data is formatted as:
    Data Type, Message type, Session ID, AircraftID, Hex, FlightID, Date (gen), Time(gen), Date, Time, Callsign, Altitude, GoundSpeed, Track (EW NS Calc), lat, Lon, VRate, SQ, (other flags and on ground/taxi flag)

    2 messages were received from 7C77FA, An Airborne Position update, and an airborne Velocity update
    (Missing type 6 Squawk/callsign identifier as seen
    MSG,6,333,105,C8237A,205,2019/03/23,14:22:16.543,2019/03/23,14:22:16.543,,9925,,,,,,5553,0,0,0,0)

    MSG = Downlink
    3 = Position update
    7C77FA = HEX
    2019/03/23 = Date message created
    14:22:16.487 = Time Message Created
    33000 = Altitude
    -41.39008 = Latitude from GPS
    171.26131 = Longitude from GPS
    MSG = Downlink
    4 = Velocity Update

    7C77FA = Hex
    2019/03/23 = Date Message Created
    14:22:16.543 = Time Message Created
    465.0 = Ground Speed
    88.9 = Track
    0 = Vertical rate neutral/cruise
    Non GPS equipped aircraft may only supply message, HEX, Time, Squawk, Altitude

    The server uses this basic data to calculate positions/Calibrated adjustments/Direction etc

    datasources.jpg
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

  7. #17
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,802
    UPDATED USB BEAST SHARING OTHER PROGRAMS/FEEDERS

    Supplemental to preceding guides

    Experienced issues with Pi FR24feed crashing as primary decoder of BEAST via USB after a period and multiple RAW data re-connection attempts

    USB -> Pi -> FR24feed
    FR24feed -> Planeplotter (raw 30334) + Piaware (raw 30334) + Database (30003) + ModeSMil (30003)

    The more stable alternate:

    FR24feed-Page-2.jpg

    Install Beast-Splitter
    - Utility to connect to BEAST and feed multiple formats/clients via TCP - similar to Dump1090 this requires sole control
    - Disconnect USB BEAST if installed
    - 2 Methods of install. Package Build, or using FlightFeeder repository

    Option 1: Refer to abcd567 pre-built guide to build the git .deb directly
    Click Here

    Option 2:
    Install FlightFeeder (refer external) which includes source information.
    Sudo apt-get install beast-splitter


    Ensure /dev/beast emulator Installed *1
    - Should output 'beast' if found.

    ls /dev | grep beast

    Test beast-splitter *2

    Connect BEAST USB cable

    beast-splitter --serial /dev/beast --listen 30333:B

    If successful/ no errors - Ctrl-C
    Working:
    beast-splitter[23201]: serial(/dev/beast): autobaud selected 3000000 bps
    Configure Service configuration

    Sudo nano /etc/default/beast-splitter
    ENABLED="yes" - Enables config when started as service
    INPUT_OPTIONS="--serial /dev/beast" - configures for above /dev/beast device
    OUTPUT_OPTIONS="--listen 30333:B" - creates classic beast output data on port 30333
    Start as service

    sudo service beast-splitter restart

    sudo service beast-splitter status

    beast-splitter.service - Mode S Beast data forwarder
    Loaded: loaded (/lib/systemd/system/beast-splitter.service; enabled; vendor preset: enabled)
    Active: active (running) since Thu 2019-04-04 20:45:28 NZDT; 5min ago
    Docs: https://github.com/flightaware/beast-splitter
    Main PID: 23201 (beast-splitter)
    CGroup: /system.slice/beast-splitter.service
    └─23201 /usr/bin/beast-splitter --serial /dev/beast --listen 30333:B --status-file /run/beast-splitter/status.json

    <errors/output displayed here>
    Configure FR24feed as normal.

    Feed Type: Beast-TCP
    Port/IP: Localhost:30333
    Host/IP: Should remain blank
    Process Arguments: Should remain blank

    Restart feeder and ensure data working

    Multiple other feeders can now be configured to use data from beast-splitter/30333 as a virtual Beast device

    Notes:
    *1
    If 'Beast' is not reported, or blank result - install device rules with the following

    sudo nano /etc/udev/rules.d/beast-splitter.rules

    Add this data
    Code:
    ACTION=="remove", GOTO="beast_splitter_end"
    SUBSYSTEM!="tty", GOTO="beast_splitter_end"
    
    IMPORT{builtin}="usb_id"
    ENV{ID_MODEL}=="Mode-S_Beast*", ENV{ID_USB_INTERFACE_NUM}=="00", SYMLINK+="beas$
    
    LABEL="beast_splitter_end"
    *2
    Default port is 30005 - changed to 30333 to prevent conflict to any system with dump1090/FlightAware installed
    Individual configurations may vary
    B denotes classic beast. R can be used for purchased radarcapes to add GPS data
    Last edited by Oblivian; 2019-05-13 at 07:45.
    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
  •