Hi guys, I'm back :)
I'm also feeding FlightAware and FlightRadar24 - three Rpi's, three antennas and ethernet cable everywhere.
PI # | | RadarBox24 Stn | | FlightAware Stn | | FlightRadar24 Stn | | PlaneFinder Stn | |
1 | EXTRPI000008 (https://www.radarbox24.com/stations/EXTRPI000008) | 5252 (https://flightaware.com/adsb/stats/user/abcd567#stats-5252) | T-CYYZ9 | 87806 |
2 | EXTRPI000035 (https://www.radarbox24.com/stations/EXTRPI000035) | 6396 (https://flightaware.com/adsb/stats/user/abcd567#stats-6396) | T-CYYZ21 | 87809 |
3 | EXTRPI000043 (https://www.radarbox24.com/stations/EXTRPI000043) | 76000 (https://flightaware.com/adsb/stats/user/abcd567#stats-76000) | T-CYYZ30 | 91995 |
Yes, each pi feeds just one site. I did setup an image that fed both FlightAware and FlightRadar24 but the range for both decreased significantly even though it was a pi 3 I was using.
I’ve still got the image on an SD card so I will experiment again, but I’m happy with one feed per pi.
apt-cache policy dump1090-fa
apt-cache policy dump1090-mutability
.... I had assumed that living out in the country I wouldn't need a filter.....
I've got a selection of USB receivers, 2 generic RTL type and a standard Flightaware Stick.
I think that maybe I'll order the Flightaware Pro Plus with the built in filter to play with. The maximum range I'm getting with all my receivers at the moment is about 140 miles with the occasional ping from further.
All I need to do now is to figure out how to feed RadarBox24 too. I'm sure you have instructions for that and I'll have a look around tomorrow.
I wonder which filter you use. I've seen the FlightAware filter and one from the Far East on eBay, but I need to do a bit more research.I use Flightaware Filter (US$14.95) (https://www.amazon.com/dp/B010GBQXK8), mainly because it is cheaper compared to other filters available, and it solved my problem.
pi@raspberrypi:~ $ sudo nano /etc/default/dump1090-mutability
# dump1090-mutability configuration file
# This is a POSIX shell fragment.
# You can edit this file directly, or use
# "dpkg-reconfigure dump1090-mutability"
# Set to "yes" to start dump1090 on boot.
START_DUMP1090="yes"
# User to run dump1090 as.
DUMP1090_USER="dump1090"
# Logfile to log to
LOGFILE="/var/log/dump1090-mutability.log"
#
# Receiver options
#
# RTLSDR device index or serial number to use
# If set to "none", dump1090 will be started in --net-only mode
DEVICE=""
# RTLSDR gain in dB.
# If set to "max" (the default) the maximum supported gain is used.
# If set to "agc", the tuner AGC is used to set the gain.
GAIN= 35
# RTLSDR frequency correction in PPM
PPM="0"
#
# Decoding options
#
# If yes, fixes messages with correctable CRC errors.
FIX_CRC="yes"
# If set, supplies a reference location for local position decoding.
LAT="43.xxxx"
LON="-79.xxxx"
# If set, provides the absolute maximum receiver range used to
# filter bad position reports, and to determine when local position
# decoding is safe to use. Specify this in nautical miles (NM).
MAX_RANGE="300"
#
# Networking options
#
# Port to listen on for raw (AVR-format) input connections. 0 disables.
RAW_INPUT_PORT="30001"
# Port to listen on for raw (AVR-format) output connections. 0 disables.
RAW_OUTPUT_PORT="30002"
# Port to listen on for SBS-format output connections. 0 disables.
SBS_OUTPUT_PORT="30003"
# Port to listen on for Beast-format input connections. 0 disables.
BEAST_INPUT_PORT="30004,30104"
# Port to listen on for Beast-format output connections. 0 disables.
BEAST_OUTPUT_PORT="30005"
# TCP heartbeat interval in seconds. 0 disables.
NET_HEARTBEAT="60"
# Minimum output buffer size per write, in bytes.
NET_OUTPUT_SIZE="500"
# Maximum buffering time before writing, in seconds.
NET_OUTPUT_INTERVAL="1"
# TCP buffer size, in bytes
NET_BUFFER="262144"
# Bind ports on a particular address. If unset, binds to all interfaces.
# This defaults to binding to localhost. If you need to allow remote
# connections, change this.
#NET_BIND_ADDRESS="127.0.0.1"
#
# Misc options
#
# Interval (in seconds) between logging stats to the logfile. 0 disables.
STATS_INTERVAL="3600"
# Path to write json state to (for use with an external webserver). Blank disables.
JSON_DIR="/run/dump1090-mutability"
# Interval between writing json state (in seconds). 0 disables.
JSON_INTERVAL="1"
# Accuracy of receiver location to write to json state, one of "exact" / "approximate" / "none"
JSON_LOCATION_ACCURACY="approximate"
# Set to yes to log all decoded messages
# This can get large fast!
LOG_DECODED_MESSAGES="no"
# Additional options that are passed to the Daemon.
EXTRA_ARGS=""
sudo systemctl restart dump1090-mutability
sudo systemctl restart piaware
sudo systemctl restart dump1090-fa
sudo nano /etc/default/dump1090-mutability
#after making changes, save file (Ctrl+o) and exit (Ctrl+x)
#restart dump1090-mutability
sudo /etc/init.d/dump1090-mutability restart
#alternative command to restart dump1090-mutability
sudo service dump1090-mutability restart
Thanks for that. I've been using slightly different restart instructions and I do see a change after the restart.Code: [Select]sudo nano /etc/default/dump1090-mutability
#after making changes, save file (Ctrl+o) and exit (Ctrl+x)
#restart dump1090-mutability
sudo /etc/init.d/dump1090-mutability restart
#alternative command to restart dump1090-mutability
sudo service dump1090-mutability restart