Announcement

Collapse
No announcement yet.

FR24feed uploader - Additional Info

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

  • Oblivian
    replied
    Web Configuration Explained:

    DVBT Stick (default)

    DVB TV Dongle connected directly by USB to host device
    - Launches Dump1090 to contact hardware directly
    - Works only if other DVB/1090 programs not already running and using data from stick
    - host/ip settings ignored

    ModeS Beast (USB/Serial)
    ModeS Beast/Transponder mouse cabled with USB or serial
    - Com port must be specified in Host/IP field
    - Baudrate must be set

    ModeS Beast (TCP)
    ModeS Beast format from decoder software using ethernet
    Beast format output from decoding software
    - Host/IP must be specified in Host/IP field

    SBS1/1e (USB)
    SBS1 cabled directly to host
    - configure Com/Dev setting

    SBS1/1e (TCP)
    - Configure Host/IP

    SBS3 (USB)
    SBS3 (TCP)

    *During signup new option "SBSx via Basestation (localhost:30006)"
    - Exact details of function TBA however may allow reading when data relay enabled in basestation suite

    microADSB (USB)
    - Configure Com/Dev path

    AVR (USB/Serial)
    Other AVR capable receivers connected via cable
    - Specify com port details

    AVR (TCP) - v23 appears to fail
    AVR data from pre-configured Rpi running Dump1090
    Data from existing Dump1090/RTL1090 or other such software with AVR server enabled
    - Specify Host/IP details

    Example AVR data format:
    Code:
    *8D75805B9944F033C0045DA67C63;
    *8D75805B58C392AC308A95C63185;
    *8D75805B58C392AC7A8A80C6EFBA;
    Process arguments
    For devices that use Dump1090 (DVBT/AVR USB) that FR24feed launches - Process arguments field can be used
    Eg: -- NET, --NET-HTTP-PORT, --NET-BEAST

    RAW data Yes/No *note
    Open server port 30334
    - For Beast and other hardware
    Open server port 30002
    - For DVBT*

    SBS Feed Yes/No
    When Kinetic receiver specified data for basestation output on 20072
    - Configure Basestation software for Ethernet receiver. Specify IP of device FR24feed running and port 20072
    - Voice/ATC functions cannot be used in conjunction with this method

    Decoded Data Yes/No: *note
    Open server port 30003
    - Basestation format text for other capture software
    Code:
    MSG,8,111,11111,C816FE,111111,2016/01/29,20:26:58.197,2016/01/29,20:26:58.222,,,,,,,,,,,,0
    MSG,8,111,11111,C816FE,111111,2016/01/29,20:26:59.361,2016/01/29,20:26:59.399,,,,,,,,,,,,0
    Logfile
    This is for diagnostic purpose
    - May not auto delete and can fill Rpi cards
    To view from default location on RPi:
    cat /var/log/fr24feed/fr24feed.log

    MLAT
    Enable MLAT data out to FR24
    - DVBT device by USB or Dump1090 AVR only
    - Enables (or requires) --MLAT tag in Dump1090

    *Note = DO NOT USE IN CONJUNCTION WITH --NET DUMP1090 OPTIONS ENABLED!!
    Last edited by Oblivian; 2019-07-01, 07:33.

    Leave a comment:


  • Oblivian
    replied
    Asking for help
    If information here is not clear there are some basic things to try BEFORE making a new thread and asking for help.

    If you think you have installed FR24feed and it is running
    - Attempt to load the webpage as described on post 1 to confirm

    Run Commands in Linux using Putty or similar SSH client
    https://www.raspberrypi.org/document...ssh/windows.md

    Diagnostic Commands

    - Run command to check status
    sudo fr24feed-status
    .deb install does not have graphical status

    If not running, diagnose WHY
    - Did the installs script fail?
    - Did you complete the install script questionnaire correctly?
    - Did you wrongly chose DVBT stick when PiAware or other software was already working?
    - Check the basic commands
    sudo systemctl stop fr24feed
    old: sudo service fr24feed stop
    sudo systemctl start fr24feed
    old: sudo service fr24feed start


    Still not starting or MLAT etc not working? Visually check logging..
    - Stop FR24feed
    sudo systemctl stop fr24feed
    sudo service fr24feed stop

    - Start fr24feed with full output
    sudo fr24feed ( !! no 'Service' !! )

    Enable log file. Start for a while, stop, and review log
    cat /var/log/fr24feed/fr24feed.log


    If after this you still need help Please help us to help you!
    List your setup:
    Receiver type
    OS / Platform
    fr24feed version - apt-cache policy fr24feed
    Include copied text from Status of fr24feed window with the errors (remove @ !!)
    Config settings (Screenshot or list of config page settings)
    Any visible errors (screenshot or paste/describe)
    Additional software you may have running for other sites or feeds (or in the past)
    What checks have been performed to try and fix already


    Common Errors:

    Code:
    gpg: failed to start the dirmngr '/usr/bin/dirmngr': No such file or directory
    Stretch lacks a package needed for scripted install - DIRMNGR
    sudo apt-get install dirmngr

    Code:
    pi@piaware:~ $ fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-02-01 09:40:09.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: <radar>
    [ ok ] FR24 Tracked AC:0
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    - Dump1090 not actually running / unstable
    (Possible SDR device blacklist issue, Stick in Use by Dump1090 already or not present, wrong setting)
    - Feeder cannot upload to server

    Code:
    [FAIL] FR24 Link: failure ... failed!
    Cannot connect to FR24 server to upload
    - Ensure you can reach the FR24 servers:
    nslookup feed.flightradar24.com
    ping feed.flightradar24.com
    - No Response can mean server down
    - No Response can mean network issue with ISP or router
    www.cloudflarestatus.com

    Code:
    2016-01-26 22:20:05 | [reader][i]Connecting to Generic receiver via (exe://*dump1090*  --raw)
    2016-01-26 22:20:05 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:05 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:07 | [reader][i]Connection terminated
    2016-01-26 22:20:12 | [reader][i]Connecting to Generic receiver via (exe://*dump1090*  --raw)
    2016-01-26 22:20:12 | [reader][i]Connected to the receiver, authenticating
    2016-01-26 22:20:12 | [reader][i]Authenticated, processing messages
    2016-01-26 22:20:14 | [reader][i]Connection terminated
    Incorrect configuration set - Dump1090/Hardware not starting. Check for:
    - USB stick has required Realtek RTL28xx chipset or Rafael Tuner (not Fitpower)
    - Conflicting software locking USB device to 'in-use'
    - Error with additional commands causing Dump1090 to terminate
    - Dump1090 (or similar) already currently running
    - Lack of power to init stick properly (powered HUB or better PSU needed)

    Code:
    2016-01-26 22:20:05 | [bs][i]Starting server on 0.0.0.0:30003
    2016-01-26 22:20:05 | [bs][e]Could not bind socket to *:30003, errno=0
    The option for Decoded data/30003 out has been enabled. There is already software with that option running, locking port
    - Close other applications
    - Disable "Basestation Out" function on VRS/ADSBScope etc
    - Reconfigure other software output port number

    Code:
    2016-01-27 00:35:36 | [feed][n]ping 1
    2016-01-27 00:36:06 | [feed][n]ping 2
    2016-01-27 00:36:36 | [feed][n]ping 3
    2016-01-27 00:37:06 | [feed][n]ping 4
    2016-01-27 00:37:36 | [feed][n]ping 5
    2016-01-27 00:38:06 | [feed][n]ping 6
    2016-01-27 00:38:36 | [feed][n]ping 7
    No data is being received by hardware to upload
    - Check connections/Antenna
    - Incorrect data format received from receiver or software for chosen receiver type
    - Wrong port/type specified from software supplying data

    Code:
    [reader][w]Global timeout exceeded, 1 msgs, 0 resyncs, reconnecting
    [reader][i]Connection terminated
    As above - FR24 Server has not received any data so reset your connection

    Code:
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    
    Kernel driver is active, or device is claimed by second instance of librtlsdr.
    In the first case, please either detach or blacklist the kernel module
    (dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
    
    usb_claim_interface error -6
    Error opening the RTLSDR device: Device or resource busy
    USB device already locked/in use or blacklisted
    - Follow RPi RTL blacklist How-to guide here
    - Close other instances of Dump1090 (clean reboot)
    - Configure other software for Network data (remove exclusive USB need)

    Other Messages:

    Code:
    2016-01-26 22:20:24 | [raw][i]Starting server on 0.0.0.0:30002
    FR24feed set to RAW out enabled - attempting to open data port 30002

    Local Web view
    AJAX call failed (error: Not Found). Maybe dump1090 is no longer running?
    Raspbian requires further RTL blacklisting
    sudo wget -O /etc/udev/rules.d/rtl-sdr.rules "https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules"
    Version difference - Web port may have changed or need to be specified
    http://<ip>/dump1090
    http://<ip>:8080/dump1090

    "My account status shows online, but no planes or data uploaded"

    This can occur if FR24feed uploader starts, but the connection to USB or data source is not possible and retrying while you cannot see it
    Causes as above but not seen
    - '--interactive' option sent to Dump1090 (will output to screen not capture data)
    - Dump1090 not installed by script
    - Blacklisted USB drivers
    - Locked USB port/device or TCP port
    - Wrong data format
    - software not outputting data on specified data port (or in correct format)
    - Bad signal or data being ignored by server
    - Populated COM/DEV/PATH over-ride auto-detect

    As with most issues - Use above fault finding to stop, and manually start to observe FR24feed startup messages or errors

    Diagnosing port issues using telnet
    If you are experiencing port connection errors one method to ensure data is working is using the telnet utility
    http://windows.microsoft.com/en-nz/w...#1TC=windows-7

    telnet <host> <port>

    Where <host> can be:
    localhost
    127.0.0.1
    198.162.1.170

    and port (divided by a space, no other character like : )
    - as listed in port table for common ports
    eg:
    telnet 198.162.1.170 22
    telnet 192.162.1.180 8080

    A WORKING open port, will result in a black screen with cursor flashing. A blocked port will result in a failure to connect
    Last edited by Oblivian; 2019-09-07, 23:55.

    Leave a comment:


  • Oblivian
    started a topic FR24feed uploader - Additional Info

    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?
    We need to receive, process/decode. And finally send data to servers

    Feed Software is not a single application but a package needing 3 parts:
    Direct hardware access libraries
    ADSB Decode software - Dump1090-Mutability 1.14 (downloaded if 'DVBT' picked)
    FR24 log, filter, bundle and uploader

    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 DVBT for feeder to collect (1 step - when 'DVBT' chosen)
    - FR24feeder connect to existing decoder software output (RECOMMENDED)

    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!

    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 using the activate receiver page.
    Image is limited and has a run-on-demand version of Dump1090 designed for first/single feed setup - will allocate extra bogus radar ID during repeated setup.
    Use web config or 'fr24feed --reconfigure' setup after first try!
    This is NOT recommended for feeding multiple sites.

    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://feederIP:8754 <--
    (replace feederIP 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

    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 DVBT or you will face errors similar to examples below

    Basics:
    - only Configure FR24feed to DVBT if first feed site or Dump1090 gets reinstalled
    use 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 beast data 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-10-21, 21:04.
Working...
X