No announcement yet.

FR24feed uploader - Additional Info

This topic is closed.
This is a sticky topic.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Oblivian

    Work in progress..

    Dump1090 is NOT needed or installed by fr24feed for a non DVBT/USB beast receiver. As a result some functionality is lost for local map views without using 3rd party apps like VRS or similar

    Supplemental to the above guide installing beast-splitter for Mode-S beast. It is also possible to re-instate a dump1090 like map on a PI itself if desired.

    If dump1090 is not installed with the fr24feed bundle, you can install it per guides found stickied on this forum

    Edit the default Dump1090 config to adjust for network based data only

    Set the receiver to network traffic
    --net-only --net-bo-port 0
    This disables the SDR/TV stick search and starts listening for data on network instead. '--net-bo-port 0' Switches off port 30005 which can conflict with other open ports.

    --net --net-heartbeat 60 --net-ro-size 1000 --net-ro-interval 1 --net-ri-port 0 --net-ro-port 0 --net-sbs-port 0 --net-bi-port 30004,30104
    This also turns off:
    port 30001 (net-ri-port)
    port 30002 (net-ro-port)
    port 30003 (net-sbs-port)

    The last setting is the source for the data. In my case --net-bi-port 30004,30104
    Port 30104 is for MLAT results returned from FlightAware client (only possible when FA installed, or append beast-splitter to push beast data with --connect localhost:30104:B )
    Port 30004 is a default Dump1090 beast input

    Restart dump1090
    sudo systemctl restart dump1090-x

    Check for open ports:
    sudo netstat -tlp

    Results should appear similar to:
    tcp        0      0 *               LISTEN      31396/fr24feed
    tcp        0      0 *               LISTEN      7269/dump1090-fa
    tcp        0      0 *               LISTEN      3068/beast-splitter
    tcp        0      0 *               LISTEN      21460/dump1090-fa

    You can see my choice of Dump1090 is listening for data on port 30004 + 30104(in), Splitter is listening for connections 30033, and fr24feed also supplying SBS on 30003 due to option enabled

    Test map output does not state dump1090 is unavailable

    With luck the map will begin to populate with local data as expected

    This setup can also work if you have SBS format 30003 data out from fr24feed or similar by adjusting the Dump1090 config to include

    --net-sbs-port 30003
    Last edited by Oblivian; 2019-07-01, 08:12.

    Leave a comment:

  • Oblivian

    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:


    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
    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
    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

    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
    ACTION=="remove", GOTO="beast_splitter_end"
    SUBSYSTEM!="tty", GOTO="beast_splitter_end"
    ENV{ID_MODEL}=="Mode-S_Beast*", ENV{ID_USB_INTERFACE_NUM}=="00", SYMLINK+="beas$
    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, 07:45.

    Leave a comment:

  • Oblivian

    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

    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):
    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 = 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


    Leave a comment:

  • Oblivian


    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)
    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
    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

    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:

    The following are tested alternatives for feeding if your receiver was a windows based setup TAKE NOTE: These instructions are not for the feint of heart. They are complex. They do involve some learning Some SBS Receivers are still NOT supported Raspberry PI + DVB Stick + PI24 although come with a cost. May be easier for some
    Last edited by Oblivian; 2019-05-13, 08:09.

    Leave a comment:

  • Oblivian
    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:

    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


    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)
    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

    Last edited by Oblivian; 2019-04-04, 08:17.

    Leave a comment:

  • Oblivian

    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 {
    rotate 5
    su fr24 fr24
    create 0644 fr24 fr24
    /bin/systemctl status fr24feed.service > /dev/null ; then \
    /bin/systemctl restart fr24feed.service > /dev/null; \
    Last edited by Oblivian; 2019-03-23, 00:51.

    Leave a comment:

  • Oblivian
    Windows (10) Feeder Specifics - to be retired
    Last edited by Oblivian; 2019-05-13, 07:30.

    Leave a comment:

  • Oblivian
    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


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

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

    - 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:

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


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

    Each program has in and out data flow:

    Last edited by Oblivian; 2019-03-23, 11:37.

    Leave a comment:

  • Oblivian

    Generic flow of data

    Optimised FR24feed as decoder:

    Decoder Configuration:
    'DVBT' (no advanced features)
    DVBT -> USB -> FR24feed -> 30005 (Beast-TCP if RAW/Net out enabled)
    DVBT -> USB -> FR24feed -> 30002 (AVR-TCP if RAW/Net out enabled)

    Separate Dump1090 as decoder:

    'BEAST-TCP' ( --NET)
    DVBT -> Dump1090 -> localhost:30005 -> FR24feed (Raw out/30002: NO)
    DVBT -> Dump1090 -> localhost:30005 -> Other Software
    'AVR-TCP' ( --NET)
    DVBT -> Dump1090 -> localhost:30002 -> FR24feed (Raw out/30002: NO)
    DVBT -> Dump1090 -> localhost:30002 -> Other Software

    Linux and non-FR24 bundled Dump1090
    If installing Dump1090 or compiling outside of FR24feed bundle, as above posts indicate you must configure FR24feed to connect to Dump1090 via AVR-TCP on 30002 / Beast TCP on 30005
    Attempting to do so on pre-compiled FR24feed or PiAware image without linux knowledge is NOT advised

    Suggested method in basic steps
    Install Dump1090 of choice
    - Configure with advanced options of choosing
    - confirm working using web view
    Install FR24/Piaware package - wizard will detect (if running correctly!) and assist
    - Do NOT agree to 'enable RAW out' or basestation when asked in FR24feed install
    Last edited by Oblivian; 2020-05-08, 11:41.

    Leave a comment:

  • Oblivian
    Viewing local traffic from your receiver

    Dump1090 can display local traffic by visiting the web page if enabled (Post #1)
    http://<host ip>:8080 / http://<host ip>:8080/dump1090 / http://<host ip>/dump1090/gmap.html

    ADSBScope & VRS example

    VirtualRadarServer or VRS as it is commonly seen described here is a graphical interface with the ability to show locally sourced aircraft position data on a web-page for you or the internet for friends etc.

    It has the ability to log these contacts in a database format (additional plugin required) and show icons and flags if added from basestation software suite or other such sources

    !! It is not designed for those of you without a receiver of some type, or access to data from one. !!

    Paradiselost has in the past made an example page with graphics on setting up VRS and ADSBScope downstream using the RAW output. The same goes for other software, such as tailing off FR24feed output ports (see common ports)

    ADSBScope and network data:
    ADSBScope has basic map settings for mobile ADSB use (at airport etc)
    Other-Network-Network setup

    Port:30005 (presumed dump1090 is running in --net mode)
    Dataformat: Binary
    URL: Pi.IP.Goes.Here

    CLOSE (you need to scroll down to it)

    And then
    Other - network - RAW-Data Client Active


    When you are actively feeding and have a premium account, radar view can be used to attached to your local traffic (fr24feed) and display in a basic format also

    Log in to premium
    Click the "Map View" drop-down and select radar view
    Add checkmark to Show local (and adjust IP accordingly if Pi/external PC)

    This method is not advised as data quality may not be optimized for FR24 use - Dump1090 has similar web server display capability

    RTL1090 will open port 31001* (Beast/AVR) OUT, 31004 (Basestation) OUT, 31002 IN when launched.

    Example FR24feed Configuration:
    Receiver: Beast-TCP
    Source: <rtl1090 PC IP>:31001*
    BS & RAW: OFF

    If the format is not recognised (Beast Binary) or other software requires strict AVR - you can over-ride when starting with a new shortcut or .cmd file - RTL1090.exe /AVR

    Other applications can connect to the same RAW/AVR out on 31001*. Or Basestation format on 31004

    *Default port is 31001
    Some systems may detect USB stick as 2nd device and change to 31011
    Output Port opened is shown on the bottom of the RTL1090 window!

    9-2-16 Added RTL1090 info
    14-3-16 added more regarding VRS
    28-1-19 adjust RTL1090 example
    24-3-19 adjust ADSBscope and RTl examples to eliminate windows feeder
    Last edited by Oblivian; 2020-05-08, 11:35.

    Leave a comment:

  • Oblivian
    <space holder>
    Last edited by Oblivian; 2019-03-23, 11:12.

    Leave a comment:

  • Oblivian
    Possible SBS Configuration Setups:

    It has become largely apparent that SBS support is difficult. Data cannot be read directly using FR24feed after updates
    (hardware has been unavailable for testing)

    Update - 8-Oct-19 - SBS feeding should now be possible from LinuxARM feeder 1.0.24-4 updates - TBC

    Virtual Pi can be used on windows instead of purchasing standalone

    Note the manual refers to using port 10001 - this is WRONG for reading data from. That port can only use 1 connection at a time - direct to the SBS when using via network

    Correct cloned output data port for other software to read while fr24feed is running is 20072

    SBS Family:
    Version 18-5 - 19-8 do NOT read SBS data as expected per below.
    Versions from 19-8 should work with SBS but often do not

    When NVM settings of SBS3 set as 'standalone' opens ports:
    10001 - primary encrypted data
    30005 - audio stream
    30006 - RAW Binary relay/out

    When Basestation Viewer Suite running:
    30005 - audio stream
    30006 - RAW Binary relay/out
    30003 - basestation format

    SBS3 - (and poss SBS1) Untested

    1. FR24feed primary device connection
    Step 1
    Configure FR24feed for 'SBSx' (USB or LAN - source port 10001)
    Enable 'SBS feed' - relay/out option (opens port 20072)
    Close FR24feed

    Step 2
    Configure basestation as network data source:
    (settings - hardware settings - network)
    Close Basestation

    Open FR24feed (ensure connecting to SBS)

    Open Basestation (ensure connecting to FR24feed relay on 20072)

    Other apps should share access to 20072 (+ 30006 if BS open)

    2. SBS3 Standalone mode
    Using basestation configure non-Volatile settings to 'standalone' mode - check default port 10001

    Configure Basestation source to network
    <SBS3 IP>:30006

    Close Basestation

    Configure FR24feed to SBS3 LAN
    Set port details as
    <SBS3 ip>:10001 (_test 2nd connection to 30006_)

    Start FR24feed
    Ensure working
    Open Basestation and ensure connects to SBS3 at same time

    'SBSx via Basestation' has been de-comissioned - do not select this on older versions

    Configure FR24feed for SBS1(USB)
    Enable 'SBS Feed' (relay out)
    Close FR24feed

    Configure Basestation for network data with the source of

    Run FR24feed - check connect via USB to SBS OK

    Open basestation - check connect to fr24feed output on 20072 as intended + displays
    Last edited by Oblivian; 2020-06-14, 10:40.

    Leave a comment:

  • Oblivian
    Can I run FR24feed on my FA FlightFeeder?
    No. It is against the policy agreed to when the device is supplied to modify or add to the core software supplied on the device.
    However you can purchase/use an additional Raspberry Pi and upload using the network data output ports with BEAST-TCP settings as outlined.

    *This differs from a FA ProStick - the optimised USB receiver that works like any other USB SDR tuner device

    Can I run FR24feed on my RPi with FA Pi-aware image installed?
    Yes* - as this is a generic Raspian install you can run the normal install BASH script and answer questions accordingly so the software work together
    *Both PiAware and Pi24 images have locked limitations and can not install variants of Dump1090-Mutability DEV editions.
    All about feeding data to Flightradar24 (The Flightradar24 receiver, Raspberry Pi and Windows feeding software). No discussions about Flightradar24 web or apps.

    Can I register 2 stations in my stats page?
    Yes - Email FR24 support with the second device location details and Radar code (if issued with one already) and request it linked to your account
    - This will become more user-automated in future

    My range decreased when switching from Windows to RPi using the same stick and antenna - can I do anything?
    Fine tune noise Adjustments can be made to USB tuners by issuing the additional arguments --gain xx
    Valid values:
    0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6

    I wish to move my receiver to a new location - will this effect anything?
    YES - If you contribute to MLAT any (significant) change in location will reflect on data calculation accuracy server side (setup at first signup)
    If temporary move, MLAT should be disabled. If permanent be sure to notify FR support of your ID and location change details or adjust in account settings -
    Dump1090 map centre can also be reconfigured if using the visual output such as sudo dpkg-reconfigure dump1090-mutability

    Can I view my radar contacts (alternate My radar alias does not appear on web site)
    Singling out your own data or ID on the main site map is not likely as it is a multi uploader data source database
    - Using the above methods for Dump1090 Graphical interface
    - Using RadarView
    - Using Virtual Radar Server

    What do the Radar Codes (Prefix / Alias) mean?
    Radar: NET1 = Users feeding from Planeplotter software.
    Radar: F-xxxx = FR24 boxes / Hardware feeders.
    Radar: T-xxxx = Users owned boxes uploading to FR24 / Software feeders.
    Radar: N-xxxx = Networked SBS-1 users uploading.
    Radar: R12* R13* are just temporary codes assigned automatically by the system, before FR24 receivers have been assigned correct code manually.
    Radar: R1a* = Temporary Radar codes on the upload Software & Server.
    Radar: T-PP1 = Users feeding with Planeplotter software.

    Why are my statistics broken/wrong
    In some cases the connection to the FR24 statistics server may have interruptions using UDP due to various ISP reasons
    Test with uploads in HTTP mode by changing fr24feed.ini
    - restart your Pi and see if this helps.
    Last edited by Oblivian; 2019-07-01, 07:38.

    Leave a comment:

  • Oblivian
    Below is an example of the signup wizard on Rpi:

    RPi Signup Wizard

    Email Address
    Existing Key if known (blank = request new)
    * old keys may be deleted if not feeding. Check stats

    Antenna Details:
    Latitude 00.0000
    Longitude 000.0000
    Altitude (ft)

    Step 1.3 - Would you like to participate in MLAT calculations? (yes/no)$

    - Only valid for certain receiver configurations

    ** Checks for running software **

    If Dump1090 already present:

    We have detected that you already have a dump1090 instance running. We can therefore automatically configure the FR24 feeder to use existing receiver configuration, or you can manually configure all the parameters.

    Would you like to use autoconfig (*yes*/no)$:

    If PiAware already present:

    We have detected that you already have a PiAware application instaled. We can therefore try to automatically configure the FR24 feeder to use existing receiver configuration, or you can manually configure all the parameters.

    Would you like to use autoconfig (*yes*/no)$:

    Autoconfig not available/not chosen:

    Step 4.1 - Receiver selection (in order to run MLAT please use DVB-T stick with dump1090 utility bundled with fr24feed):

    1 - DVBT Stick (USB)
    2 - SBS1/SBS1er (USB/Network)
    3 - SBS3 (USB/Network)
    4 - ModeS Beast (USB/Network)
    5 - AVR Compatible (DVBT over network, etc)
    6 - microADSB (USB/Network)
    7 - SBSx via Basestation (localhost:30006)

    Enter your receiver type (1-7)$:

    DVBT (with no other feeder software!):

    Step 4.2 - Please select connection type:

    1 - Network connection
    2 - USB directly to this computer

    Step 5.1 - Would you like to enable RAW data feed on port 30334 (yes/no)$:
    Step 5.2 - Would you like to enable Basestation data feed on port 30003 (yes/no)

    - Enables local server. If running Dump1090 or other software with these ports open select NO

    BEAST-TCP (established receiver data out)

    1 - Network connection
    2 - USB directly to this computer

    Step 4.3A - Please enter your receiver's IP address/hostname
    $:<device IP>

    Step 4.3B - Please enter your receiver's data port number
    $:<data port>

    Step 5.1 - Would you like to enable RAW data feed on port 30334 (yes/no)$:no
    Step 5.2 - Would you like to enable Basestation data feed on port 30003 (yes/no)$:no
    Last edited by Oblivian; 2019-07-14, 11:57.

    Leave a comment:

  • Oblivian
    Pi SSH specific Information:

    Putty Connection from Windows


    Install FR24feed via script: *Not valid on Pi24 Image
    sudo bash -c "$(wget -O -" -

    19-5+ Installer package includes:
    librtlsdr0 libusb-1.0-0 dirmngr lighttpd wget
    If not detected or 'DVBT' option chosen - Dump1090-mutability V1.15

    Auto configures Dump1090 startup to FALSE - run on Demand when fr24feed started only
    (!! Specific for DVBT stick and direct USB - will cause usb_claim_interface error -6 if dump1090 already started !!)

    Auto change made included = /auto-start boolean false | debconf-set-selections -v

    Dump1090 Dev Install *Not valid on Pi24 Image
    (advanced users recommended only)
    See thread for manual install of Dev version of Dump1090

    Common Linux Commands:
    Linux need not be scary for first time users. Although there is no graphical interface without starting one, the same commands are needed for FR24feed on GUI versions.

    Fixing broken components/upload/offline issues:

    Check fr24feed status
    sudo fr24feed-status
    (non-pi versions over 1.23: sudo fr24feed --status)

    Restart fr24feed
    sudo systemctl restart fr24feed
    (sudo service fr24feed restart)

    Stop fr24feed
    sudo systemctl stop fr24feed
    (sudo service fr24feed stop)

    Disable fr24feed auto start
    sudo systemctl disable fr24feed

    Check connectivity to Fr24 server distribution (IPv6 errors)

    Dump0190-Mutability checks:
    sudo service dump1090-mutability status (sudo systemctl status dump1090-mutability)
    sudo service dump1090-mutability restart (sudo systemctl restart dump1090-mutability)
    sudo service dump1090-mutability stop (sudo systemctl stop dump1090-mutability)
    sudo dpkg-reconfigure dump1090-mutability

    Start feed software with full screen output to diagnose possible errors (cannot run without first stopping service)
    sudo fr24feed
    (ctrl-C to terminate)

    Check for crashed/running instances causing port or start issues:
    - Following command will report a PID for each process (thats a small L)
    pgrep -l fr24feed - list running FR24 processes
    pgrep -l dump1090 - list dump1090 instances

    sudo kill -9 <pid> - replace <pid> with corresponding number from above to kill process

    re-Run Signup, re-enter key or reconfigure if web not accessible
    sudo fr24feed --signup
    (Enter the identical details as first signup)

    Edit config file manually
    sudo nano /etc/fr24feed.ini

    Kicking it off again:
    Start feed software as service in background (starts on reboot)
    sudo systemctl start fr24feed
    (sudo service fr24feed start)

    Uninstall or remove FR24feed (to remove radar ID email support)
    sudo apt-get remove fr24feed

    -Optionally, to also remove any associated dependencies (may break other software)
    sudo apt-get remove --purge fr24feed

    GPG and other errors - Update fr24feed
    sudo apt-get update - refresh available app update list
    sudo apt-get install fr24feed - manually check for update
    - Will search for a new version and advise if 0 bytes were to be installed (no change) or if a new update was to be.
    - Manually apply keys
    gpg --keyserver --recv-keys 40C430F5
    gpg --armor --export 40C430F5 | sudo apt-key add -

    Dump1090 Graphical Interface (View your aircraft radar contacts):
    FR24 installs Dump1090-Mutability 1.15 when 'DVBT' chosen with an inbuilt display map if
    --net option is added to additional parameters
    Visit http://<host ip>:8080 / http://<host ip>:8080/dump1090 / http://<host ip>/dump1090/gmap.html

    A further port change option can be specified --net-http-port xxxx if other services run on 8080 already
    See Dump1090 documentation for further assistance
    Dump1090 map is not loaded in AVR/TCP mode as it is not required - separate dump1090 or map software required

    Status Variables

    cat /dev/shm/decoder.txt

    mlat-uplink-stats = 0
    - Nothing uploaded, could be because not enough of other MLAT-receivers in the area.

    Lists the last known problem - may not indicate current fault
    - "no-config" comes from the decoder starting too soon to receive from server
    - both uploaded/not uploaded

    Associated files
    pi@raspberrypi:~ $ dpkg-query -L fr24feed
    Additional Diagnostic commands:
    Last edited by Oblivian; 2020-05-23, 04:18.

    Leave a comment: