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

Thread: FR24feed uploader - Additional Info

  1. #11
    Super Moderator
    Join Date
    May 2011
    Location
    T-NZCH1, PP:PH New Zealand
    Posts
    4,498
    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,498
    Windows (10) Feeder Specifics - to be retired

    When using DVBT stick with windows feeder (mr-dump1090.exe) startup messages may not be passed to the uploader app during launch so errors are not as easily seen.

    When USB not detected or configured wrong you may see:
    [main][i]FR24 Feeder/Decoder
    [main][i]Version: 1.0.18-9/generic
    [main][i]Built on Apr 21 2017 14:51:08 (???/Windows/i386)

    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    [reader][i]Configured, processing messages
    [reader][i]Connection terminated
    [reader][i]Connecting to DVBT receiver via (exe://mr-dump1090.exe --raw)
    [reader][i]Connected to the receiver, configuring
    Despite it saying connected to the receiver, it is not.

    To confirm the USB is detected with correct tuner present, you can run mr-dump1090.exe from installation folder:
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60
    Setting gain to: 49.60
    Exact sample rate is: 2000000.052982 Hz
    Gain reported by device: 49.60
    Any messages relating to Tuner like below, indicate no Rafael Micro tuner is not present and will likely not be able to receive ADSB signals or be poor at doing so

    [FC0012] no valid PLL combination found for 1090000000 Hz!
    Exact sample rate is: 2000000.052982 Hz
    This is a fitpower FC0012 tuner, only capable of 22 – 948.6 MHz when ADSB is 1090 MHz

    Newer Windows 10/USB installations may detect more than 1 device. Dump1090 can pick the wrong device

    Found 2 device(s):
    0: ■, ┤■, SN: (currently selected)
    1: Realtek, RTL2838UHIDIR, SN: 00000001:
    usb_open error -12
    Error opening the RTLSDR device: No error
    This may require additional commands to be added to the FR24feed config page
    For example above:
    --device-index 1

    It can also be tested at a CMD prompt with dump1090-mr --device-index 1
    Last edited by Oblivian; 2019-03-22 at 23:57.
    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,498
    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,498
    Migrating USB Devices (MicroADSB/Beast/SBS) to Raspberry Pi from Windows feeder

    As Dump1090 is usually not needed for non RTL based USB devices (like DVBT sticks) 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

    And yes, it appears to be case sensitive

    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 is the serial device ID to add to 'COM/DEV/PATH' field. The number may change
    /dev/<result port>

    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

    SHARING DATA TO OTHER PROGRAMS/FEEDERS

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

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

    beastusb.jpg
    Last edited by Oblivian; 2019-03-23 at 11:45.
    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,498
    WINDOWS HOST, PI FEEDER

    The trickier / likely less reliable method

    If like me, your Windows Device 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

    Many use ModeSMixer to do this and provide various data output

    Assuming you have a working windows feed receiver:

    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:
    Set to beast-TCP <ip of windows>:30333
    Start/restart fr24feed

    Kinetic Basestation (untested) (not available on SBS-1) -
    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
    Settings - Non-Volatile Memory Setting
    Select Standalone mode

    FR24feed:
    Set to SBS3 TCP <ip of windows>:30006
    Restart + test
    Or..
    Set to avr-tcp <ip of windows>:30003
    Restart + test
    Last edited by Oblivian; 2019-03-23 at 11:26.
    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,498
    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

Posting Permissions

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