MLAT on dump1090-mutability v1.14 and piaware 2.1-5

Hi Everybody ,

I have do an upgrade on My PI2 I install dump1090-mutability v1.14 and piaware 2.1-5 and now MLAT doesn’t work anymore.

Before I used dump1090-mutability faup1090-2.1-3-1-gc55c71b with this option and it work perfectly :


--net --gain -10 --ppm 72 --net-beast --no-fix --modeac --mlat --aggressive --net-http-port 80 --net-ro-port 30002 --net-sbs-port 30003  --net-bo-port 30005 --net-fatsv-port 10002 --measure-noise"


Now with the new version of dump I have these parameters :

–net --gain -10 --ppm 72 --fix --phase-enhance --aggressive --lat 45.723626862182617 --lon 4.85315561294556 --max-range 300 --net-http-port 8080 --net-ri-port 30001 --net-ro-port 30002 --net-bi-port 30104 --net-bo-port 30005 --net-sbs-port 30003 --net-fatsv-port 10002 --net-heartbeat 60 --net-ro-size 500 --net-ro-interval 1 --net-buffer 2 --stats-every 3600 --write-json /run/dump1090-mutability --write-json-every 1 --json-location-accuracy 2 --quiet --mlat --modeac --net-beast

**
My config files is this one : **



# 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="-10"

# RTLSDR frequency correction in PPM
PPM="72"

# If yes, enable sampling at 2.4MHz. Otherwise, 2.0MHz is used.
OVERSAMPLE="no"

# If yes, enables phase-enhancement of messages
PHASE_ENHANCE="yes"

#
# Decoding options
#

# If yes, fixes messages with correctable CRC errors.
FIX_CRC="yes"

# If yes, enables aggressive fixes to damaged messages.
# Use with caution - it can increase the rate of undetected errors.
AGGRESSIVE="yes"

# If set, supplies a reference location for local position decoding.
LAT="45.723626862182617"
LON="4.85315561294556"

# 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 HTTP connections. 0 disables.
# HTTP defaults to being disabled unless you specify something here. I
# that you do not enable this, and instead serve the contents of
# /usr/share/dump1090-mutability and JSON_DIR (below) using a proper
# webserver. See /etc/lighttpd/conf-available/90-dump1090.conf
# for an example configuration ("sudo lighty-enable-mod dump1090" to enable)
HTTP_PORT="8080"

# 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="30104"**


# Port to listen on for Beast-format output connections. 0 disables.
BEAST_OUTPUT_PORT="30005"

# Port to listen on for FATSV-format output connections. 0 disables.
FATSV_OUTPUT_PORT="10002"

# 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=""

#
# 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="exact"

# 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="--mlat --modeac --net-beast"



My piaware config is this one :


contents of piaware config file '/root/.piaware':
autoUpdate 1
manualUpdate 1
mlatResults 1
mlatResultsFormat {beast,connect,localhost:30104 ext_basestation,listen,30106}
password xxxxxxxx
user xxxxxx


COULD YOU HELP ME PLEASE ?

check /tmp/piaware.out or /var/log/piaware.log for newer versions
And /var/log/dump1090-mutability.log

I suspect there is an issue with FAUP1090 connecting to dump1090-mut

Did you set your location on the website? That is where FAUP1090 gets its info from.

Enabling this may allow you to see more traffic

If yes, enable sampling at 2.4MHz. Otherwise, 2.0MHz is used.

OVERSAMPLE=“no”

I think if you change to 1.15-dev, you will be fine.

Hello

This is a part of the mutability.log :



Statistics: Wed May 25 07:39:25 2016 CEST - Wed May 25 19:05:11 2016 CEST
Local receiver:
  627391 sample blocks processed
  0 sample blocks dropped
  7416515 Mode A/C messages received
  80271304 Mode-S message preambles received
    14963717 with bad message format or invalid CRC
    8055600 with unrecognized ICAO address
    7906872 accepted with correct CRC
    539588 accepted with 1-bit error repaired
    108850 accepted with 2-bit error repaired
  0 messages with signal power above -3dBFS
Messages from network clients:
  0 Mode A/C messages received
  0 Mode S messages received
    0 with bad message format or invalid CRC
    0 with unrecognized ICAO address
    0 accepted with correct CRC
    0 accepted with 1-bit error repaired
    0 accepted with 2-bit error repaired
15971825 total usable messages
14 surface position messages received
627306 airborne position messages received
600386 global CPR attempts with valid positions
116 global CPR attempts with bad data
  5 global CPR attempts that failed the range check
  10 global CPR attempts that failed the speed check
1391 global CPR attempts with insufficient data
23584 local CPR attempts with valid positions
  22672 aircraft-relative positions
  912 receiver-relative positions
3234 local CPR attempts that did not produce useful positions
  3120 local CPR attempts that failed the range check
  100 local CPR attempts that failed the speed check
0 CPR messages that look like transponder failures filtered
58854 unique aircraft tracks
37287 aircraft tracks where only one message was seen
0 HTTP requests
CPU load: 26.8%
  9763371 ms for demodulation
  852432 ms for reading from USB
  398088 ms for network input and background tasks
Wed May 25 19:05:11 2016 CEST  Normal exit.
Wed May 25 19:05:12 2016 CEST  dump1090-mutability v1.14 starting up.
Preparing error correction tables.. done.
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
Found Rafael Micro R820T tuner
Using automatic gain control.
Exact sample rate is: 2000000.052982 Hz
Gain reported by device: 0.00 dB


Log in piaware.log:

05/25/2016 19:08:46 ****************************************************
05/25/2016 19:08:46 piaware version 2.1-5 is running, process ID 4250
05/25/2016 19:08:46 your system info is: Linux rpidump 4.4.10-v7+ #885 SMP Fri May 13 15:44:27 BST 2016 armv7l GNU/Linux
05/25/2016 19:08:47 lost connection to dump1090-mutab via faup1090
05/25/2016 19:08:47 reconnecting to dump1090-mutab
05/25/2016 19:08:47 ADS-B data program ‘dump1090-mutab’ is listening on port 30005, so far so good
05/25/2016 19:08:47 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 45.772 --lon 4.805
05/25/2016 19:08:47 Started faup1090 (pid 4259) to connect to dump1090-mutab
05/25/2016 19:08:48 Connecting to FlightAware adept server at piaware.flightaware.com/1200
05/25/2016 19:08:48 ADS-B data program ‘dump1090-mutab’ is listening on port 30005, so far so good
05/25/2016 19:08:48 Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 45.772 --lon 4.805
05/25/2016 19:08:48 Started faup1090 (pid 4261) to connect to dump1090-mutab
05/25/2016 19:08:48 Connection with adept server at piaware.flightaware.com/1200 established
05/25/2016 19:08:49 FlightAware server SSL certificate validated
05/25/2016 19:08:49 encrypted session established with FlightAware
05/25/2016 19:08:49 autoUpdate in adept config is enabled, allowing update

clock 1464203329 mac b8:27:eb:e4:ed:f9 message autoUpdate in adept config is enabled, allowing update type log user xxxxx
05/25/2016 19:08:49 manualUpdate in adept config is enabled, allowing update
clock 1464203329 mac b8:27:eb:e4:ed:f9 message manualUpdate in adept config is enabled, allowing update type log user xxxxxxxxxxxx
05/25/2016 19:08:49 multilateration support enabled (use piaware-config to disable)
clock 1464203329 mac b8:27:eb:e4:ed:f9 message multilateration support enabled (use piaware-config to disable) type log user xxxxxx
adsbprogram dump1090-mutab clock 1464203329 compression_version 1.2 dump1090_packages dump1090-mutability 1.14 image_type piaware_package local_auto_update_enable 1 local_iface eth0 local_ip 192.168.0.11 local_manual_update_enable 1 local_mlat_enable 1 mac b8:27:eb:e4:ed:f9 os_id raspbian os_version 7 (wheezy) os_version_id 7 password xxxxxxxx piaware_package_version 2.1-5 piaware_version 2.1 piaware_version_full 2.1-5 transprogram faup1090 type login uname Linux rpidump 4.4.10-v7+ #885 SMP Fri May 13 15:44:27 BST 2016 armv7l GNU/Linux user xxxxxxxxx
05/25/2016 19:08:49 piaware received a message from dump1090-mutab!
< clock 1464203329 status ok type login_response user xxxxxxxx
05/25/2016 19:08:49 logged in to FlightAware as user xxxxxxxx
!cha WEøBP^@·^@^@<90>o
!haq 9±g^@^@<80>è3G
!halmq 9PÇ^@^@<84>·B7û¦@<9f>ôI^P^@
!cha WEøC;wø^@^@^Uc
!chaq WEøB9±h^@^@<84>Ð^P^@
!chasqH WEøD<^L²^@^@<8c> ^B^L#0^@<
!ha L¤ò^@^@<90><88>
05/25/2016 19:08:53 piaware has successfully sent several msgs to FlightAware!
!hiasqH 9<85>©AF509XJ ^@^@<84>Ð^A<95>s’^A_
!chalm WEøG9<85>ª^@^@<83>YB:<89>Ï@<95>$Ý
!chialmsqH WEøJ4^T<8d>IBE3194 ^@^@<94>pB3d<99>@s¹^O^B^Y^P&^@<
!chialmsqH WEøK4D^LVLG6249 ^@^@<90><88>B6<90>!@Á^RZ^A<99>0V^@Æ
!hialmsqH <VåEWG7GH ^@^@+^QB75^C@¦HV^AO^P^@^@^E
!hialmsqH BCÕAFL2604 ^@^@<90><88>B4«S@c \^Aff^F^@ë
!hialmsqH ?<85>^WGAF574 ^@^@<94>pB7×­@<9c>2a^AÖ^PQ^@^G
!halmsqH P^@·^@^@<90>oB2ׯ@<96>¾Ë^B^D^P^@^@<81>
!halmsqH P^@·^@^@<90>oB2ׯ@<96>¾Ë^B^D^P^@^@<81>
!chialmsqH WEøL9PÇAF685VC ^@^@<84>·B8^O<86>@ /ì^A©^P^@^@^M
05/25/2016 19:09:00 piaware (process 4250) is shutting down because it received a shutdown signal (SIGINT) from the system…
! mac b8:27:eb:e4:ed:f9 message piaware (process 4250) is shutting down because it received a shutdown signal (SIGINT) from the system… type log user xxxxxxx
05/25/2016 19:09:00 piaware (process 4250) is exiting…
! mac b8:27:eb:e4:ed:f9 message piaware (process 4250) is exiting… type log user xxxxxx
05/25/2016 19:09:00 TLS alert: close notify
05/25/2016 19:12:50 7328 msgs recv’d from dump1090-mutab (365 in last 5m); 7306 msgs sent to FlightAware
05/25/2016 19:17:50 7593 msgs recv’d from dump1090-mutab (265 in last 5m); 7571 msgs sent to FlightAware
05/25/2016 19:22:50 7881 msgs recv’d from dump1090-mutab (288 in last 5m); 7859 msgs sent to FlightAware
05/25/2016 19:27:50 8170 msgs recv’d from dump1090-mutab (289 in last 5m); 8148 msgs sent to FlightAware
05/25/2016 19:32:50 8495 msgs recv’d from dump1090-mutab (325 in last 5m); 8473 msgs sent to FlightAware
05/25/2016 19:37:50 8870 msgs recv’d from dump1090-mutab (375 in last 5m); 8848 msgs sent to FlightAware
05/25/2016 19:42:50 9183 msgs recv’d from dump1090-mutab (313 in last 5m); 9161 msgs sent to FlightAware
05/25/2016 19:47:50 9522 msgs recv’d from dump1090-mutab (339 in last 5m); 9500 msgs sent to FlightAware
05/25/2016 19:52:50 9820 msgs recv’d from dump1090-mutab (298 in last 5m); 9798 msgs sent to FlightAware

I Will try to change OVERSAMPLE option

The oversample options gives up Mode A/C and there’s not meat :frowning:

Current github master will do mode A/C in --oversample mode just fine, try it.

**I try the new version thanks to this page :
**http://discussions.flightaware.com/ads-b-flight-tracking-f21/what-is-easiest-way-to-install-dump1090-mutability-t35431-25.html

But It don’t change anything . No Mlat and no mode A/C with oversample .

Nobody have a new Idea for me ??? now I am with mutability V.1.5-dev

Please help ME it don’t work :neutral_face: :confused: :confused:

Thank you all .
I find the solution i compile a legacy verrsion of piaware and now it Works well.
I think that there s a Problem in the fa mlat client on the new version of piaware bécasse the mlat client is not launch in the startup séquence of piaware

Yesterday I succeeded in installing dump1090-mutability 1.15~dev on “piaware-jessie-full-sd-card-2.1-5.img”.

Details are here: http://discussions.flightaware.com/post194380.html#p194380

.