Announcement

**Oblivian** · 2016-01-29, 06:40

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

**Oblivian** · 2016-01-29, 07:30

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

**Oblivian** · 2016-01-29, 12:42

Pi specific Information:

Putty Connection from Windows

WARNING: SELECTING 'DVBT' AS FEEDER AT ANY TIME WILL EXECUTE
/usr/lib/fr24/install_dump1090.sh
AND OVER-WRITE ANY CUSTOM DUMP1090 INSTALLS

Install FR24feed via script: *Not valid on Pi24 Image
sudo bash -c "$(wget -O - http://repo.feed.flightradar24.com/install_fr24_rpi.sh)" -

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

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 Graphical Interface (View your aircraft radar contacts):
FR24 installs Dump1090-Mutability 1.14 when 'DVBT' chosen with an inbuilt display map
--net option is added to additional parameters, and you then visit http://localhost:8080 / http://localhost:8080/dump1090 / http://localhost/dump1090/gmap.html (or host IP) (may also need /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

Dump1090 Dev Install *Not valid on Pi24 Image
(advanced users recommended only)
See thread for manual install of Dev version of Dump1090
http://forum.flightradar24.com/threa...-15-dev-on-RPi

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)

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

Check connectivity to Fr24 server distribution (IPv6 errors)
https://forum.flightradar24.com/thre...l=1#post109164

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

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

Uninstall or remove FR24feed (to remove radar ID if no longer able 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 pool.sks-keyservers.net --recv-keys 40C430F5
gpg --armor --export 40C430F5 | sudo apt-key add -

Status Variables
http://locahost:8754/monitor.txt
cat /dev/shm/decoder.txt

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

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

Associated files

Code:

pi@raspberrypi:~ $ dpkg-query -L fr24feed
/etc/udev/rules.d/rtl-sdr.rules
/etc/systemd/system/fr24feed.service
/etc/cron.d/fr24feed_updater
/etc/fr24feed.ini
/usr/bin/fr24feed-status
/usr/bin/fr24feed
/usr/lib/fr24
/usr/lib/fr24/public_html
/usr/lib/fr24/public_html/coolclock
/usr/lib/fr24/public_html/coolclock/excanvas.js
/usr/lib/fr24/public_html/coolclock/coolclock.js
/usr/lib/fr24/public_html/coolclock/moreskins.js
/usr/lib/fr24/public_html/options.js
/usr/lib/fr24/public_html/gmap.html
/usr/lib/fr24/public_html/config.js
/usr/lib/fr24/public_html/script.js
/usr/lib/fr24/public_html/style.css
/usr/lib/fr24/public_html/planeObject.js
/usr/lib/fr24/public_html/extension.js
/usr/lib/fr24/fr24feed_updater.sh
/usr/lib/fr24/install_dump1090.sh

Additional Diagnostic commands:
https://forum.flightradar24.com/thre...ostic-Commands

**Oblivian** · 2016-01-29, 13:12

Below is an example of the signup wizard on Rpi:

RPi Signup Wizard

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

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

**Oblivian** · 2016-02-06, 10:17

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.
https://forum.flightradar24.com/thre...-A-Brief-Guide

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 - https://www.flightradar24.com/account/data-sharing
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

use-http=yes
http-timeout=10
- restart your Pi and see if this helps.

**Oblivian** · 2016-02-06, 10:49

Possible SBS Configuration Setups:

It has become largely apparent that SBS support no longer exists. Data cannot be read directly using FR24feed again
(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
https://forum.flightradar24.com/thre...windows-feeder

SBS Family:
May '16 - 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

Dual Basestation (Application) + FR24feed - works?
Select SBSx via Basestation During setup and configure <IP>:30006
Open basestation as normal (receiver connection & 30006 out starts)
Open FR24feed (uses 30006 data)

SBS3 - Untested

1. FR24feed primary connection
Step 1
Configure FR24feed for SBS via USB or LAN (source port 10001)
Enable SBS relay/out option
Close FR24feed

Step 2
Configure basestation to FR24feed as network source:
(settings - hardware settings - network)
localhost:20072
Close Basestation
Open FR24feed (ensure connecting to SBS3)
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

SBS1 - FR24 advise against this method

Requires Basestation to be open and running before FR24feed launched as below:

Configure FR24feed for "SBSx via Basestation (localhost:30006)" or via LAN
Disable SBS relay
Set source as IPofPCWithBasestation:30006
Close FR24feed

Open Basestation software
Launch FR24feed

2nd Option
Configure FR24feed for SBS-USB
Enable SBS relay
Close FR24feed

Configure Basestation for network data
IPofPI:20072
Close

Run FR24feed - check connect via USB
Open basestation - check connect + display

**Oblivian** · 2016-02-06, 11:21

**Oblivian** · 2016-02-08, 03:55

Viewing local traffic from your receiver

Dump1090 can display local traffic by visiting the web page http://<custom IP address>:8080/Dump1090(see first post)

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
http://woodair.net/SBS/Utilities/Kin...s4_Bitmaps.htm

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

http://forum.flightradar24.com/threa...ll=1#post45960

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

Raw-data-client
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

Radarview

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 "logged in" icon and select radar view
Settings
Add checkmark to Show local (and adjust IP accordingly if Pi/external PC)

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

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

**Oblivian** · 2016-04-04, 02:25

WIP:

Generic flow of data

Optimised FR24feed as decoder:

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

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

**Oblivian** · 2016-09-17, 12:08

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

**Oblivian** · 2017-08-10, 09:01

Windows (10) Feeder Specifics - to be retired

**Oblivian** · 2018-08-24, 08:05

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
}

**Oblivian** · 2019-03-22, 23:56

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

**Oblivian** · 2019-03-23, 00:44

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

Announcement

FR24feed uploader - Additional Info

FR24feed uploader - Additional Info

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment