FlightAware Discussions

Piaware+V-hiper win10x64

Hello. I feed to fa under win10 x64. I use debian, support under hiper-V.
my config dump1090 v.1.15:
dump1090.exe --device-index 1 --gain 49 --net --interactive --net-bo-port 30005 --modeac --max-range 500 --fix --phase-enhance --aggressive --metric
pause
My config piaware:
feeder-id c5ec0bfa-****-47dd-8d84-9c99380601c4 # updated by fa_piaware_config
allow-auto-updates yes # updated by fa_piaware_config
allow-manual-updates yes # updated by fa_piaware_config
allow-mlat yes # updated by fa_piaware_config
mlat-results yes # updated by fa_piaware_config
mlat-results-format beast,listen,30105 ext_basestation,listen,30106 # updated by fa_piaware_config
I have two receiver to VRS: 1-st port 30005, 2-nd port 30106
and one Merged Feed (1+2 receiver to one)/
I see my feed to https://flightaware.com/adsb/stats/user/rikifromgomel
BUT MLAT RED!!! and don’t work.

service ntp install. service synchronize time on win10 off.
MY log on flightaware.com:
no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-16 22:05 +03] no ADS-B data program seen listening on port 30005 for 371 seconds, trying to start it…
[2020-05-16 22:05 +03] can’t start beast-splitter, no services that look like beast-splitter found
[2020-05-16 22:05 +03] attempting to start beast-splitter…
[2020-05-16 22:05 +03] no ADS-B data program seen listening on port 30005 for 10 seconds, next check in 60s
[2020-05-16 22:05 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-16 22:05 +03] failed to run netstat: \nchild process 5863 exited with status 1
[2020-05-16 22:06 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-16 22:06 +03] 20 msgs recv’d from the Mode-S Beast serial port (9 in last 5m); 20 msgs sent to FlightAware
[2020-05-16 22:06 +03] my feeder ID is c5ec0bfa-****-47dd-8d84-9c99380601c4
[2020-05-16 22:06 +03] multilateration data requested
[2020-05-16 22:06 +03] Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn’t open “/var/cache/piaware/feeder_id.new”: permission denied
[2020-05-16 22:06 +03] logged in to FlightAware as user rikifromgomel
[2020-05-16 22:06 +03] failed to run netstat: \nchild process 5881 exited with status 1
[2020-05-16 22:06 +03] adept reported location: 52.35954, 31.02601, 433ft AMSL
[2020-05-16 22:06 +03] site statistics URL: https://flightaware.com/adsb/stats/user/rikifromgomel#stats-108864
[2020-05-16 22:06 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
Help me please!!!
Kirill from belarus. UMGG

Maybe this thread gives you some support:

My system work, but mlat dont work only

Most likely it is due to hiper-V.
I faced mlat problem when running piaware & dump1090-fa on Windows through Oracle VM.

Here is a thread descussing this issue:

No MLATs when running piaware using VirtualBox on a PC

These log messages do not match the configuration you posted.
What is your full configuration?

Please remove --aggressive from this command line.

You have some piaware installation problems; piaware is running as the wrong user.

My log now:
UAT support disabled by local configuration setting: uat-receiver-type
[2020-05-17 16:58 +03] no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
[2020-05-17 16:58 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-17 16:58 +03] multilateration data requested
[2020-05-17 16:58 +03] site statistics URL: https://flightaware.com/adsb/stats/user/rikifromgomel#stats-108864
[2020-05-17 16:58 +03] logged in to FlightAware as user rikifromgomel
[2020-05-17 16:58 +03] adept reported location: 52.35954, 31.02601, 433ft AMSL
[2020-05-17 16:58 +03] Failed to update feeder ID file at /var/cache/piaware/feeder_id: couldn’t open “/var/cache/piaware/feeder_id.new”: permission denied
[2020-05-17 16:58 +03] my feeder ID is c5ec0bfa-fc12-****-8d84-9c99380601c4
[2020-05-17 16:58 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-17 16:58 +03] 0 msgs recv’d from the Mode-S Beast serial port; 0 msgs sent to FlightAware

Please see this post:

1 Like

Sorry, but i confused :-((((((((((((
my piaware.config now:
allow-auto-updates yes # updated by fa_piaware_config
allow-manual-updates yes # updated by fa_piaware_config
allow-mlat yes # updated by fa_piaware_config
mlat-results yes # updated by fa_piaware_config

mlat-results-format beast,listen,30005 ext_basestation,listen,30106 # updated by fa_piaware_config

receiver-type other # updated by fa_piaware_config
receiver-host 192.168.100.2 # updated by fa_piaware_config
receiver-port 30005 # updated by fa_piaware_config
but my mlat red :frowning:

log now
[2020-05-25 21:13 +03] my feeder ID is c5ec0bfa-fc12-47dd-8d84-9c99380601c4
[2020-05-25 21:13 +03] adept reported location: 52.35954, 31.02601, 433ft AMSL
[2020-05-25 21:13 +03] logged in to FlightAware as user rikifromgomel
[2020-05-25 21:13 +03] site statistics URL: https://flightaware.com/adsb/stats/user/rikifromgomel#stats-108864
[2020-05-25 21:13 +03] multilateration data requested
[2020-05-25 21:13 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-25 21:13 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-25 21:13 +03] multilateration data requested
[2020-05-25 21:13 +03] UAT support disabled by local configuration setting: uat-receiver-type
[2020-05-25 21:13 +03] my feeder ID is c5ec0bfa-fc12-47dd-8d84-9c99380601c4
[2020-05-25 21:13 +03] adept reported location: 52.35954, 31.02601, 433ft AMSL
[2020-05-25 21:13 +03] site statistics URL: https://flightaware.com/adsb/stats/user/rikifromgomel#stats-108864
[2020-05-25 21:13 +03] no ADS-B data program seen listening on port 30005 for 3 seconds, next check in 60s
[2020-05-25 21:13 +03] failed to run netstat: \nchild process 1400 exited with status 1
[2020-05-25 21:13 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-25 21:13 +03] failed to run netstat: \nchild process 1401 exited with status 1
[2020-05-25 21:13 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-25 21:13 +03] 0 msgs recv’d from the ADS-B data program at 192.168.100.2/30005; 0 msgs sent to FlightAware
[2020-05-25 21:13 +03] 0 msgs recv’d from the ADS-B data program at 192.168.100.2/30005; 0 msgs sent to FlightAware
[2020-05-25 21:13 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-25 21:13 +03] failed to run netstat: \nchild process 1409 exited with status 1

**now have log: **
[2020-05-26 22:14 +03] mlat-client(4430): Input connected to 192.168.100.2:30005
[2020-05-26 22:14 +03] mlat-client(4430): fa-mlat-client 0.2.10 starting up
[2020-05-26 22:14 +03] mlat-client(4430): Using UDP transport to 70.42.6.228 port 18272
[2020-05-26 22:14 +03] UAT support disabled by local configuration setting: uat-receiver-type
[2020-05-26 22:14 +03] my feeder ID is c5ec0bfa-fc12-47dd-8d84-9c99380601c4
[2020-05-26 22:14 +03] multilateration data requested
[2020-05-26 22:14 +03] logged in to FlightAware as user rikifromgomel
[2020-05-26 22:14 +03] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr 192.168.100.2 --net-bo-port 30005 --stdout --lat 52.360 --lon 31.026
[2020-05-26 22:14 +03] adept reported location: 52.35954, 31.02601, 433ft AMSL
[2020-05-26 22:14 +03] mlat-client(4446): fa-mlat-client 0.2.10 starting up
[2020-05-26 22:14 +03] mlat-client(4446): Listening for Beast-format results connection on port 30005
[2020-05-26 22:14 +03] mlat-client(4446): Input connected to 192.168.100.2:30005
[2020-05-26 22:14 +03] mlat-client(4446): Using UDP transport to 70.42.6.232 port 12608
[2020-05-26 22:14 +03] failed to run netstat: \nchild process 4447 exited with status 1
[2020-05-26 22:14 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-26 22:14 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-26 22:14 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
[2020-05-26 22:14 +03] failed to run netstat: \nchild process 4450 exited with status 1
[2020-05-26 22:14 +03] failed to run netstat: \nchild process 4449 exited with status 1
[2020-05-26 22:14 +03] no ADS-B data program is serving on port 30005, not starting multilateration client yet
my piaware-config.txt
# RECEIVER CONFIGURATION
#
# For a complete list of receiver types and their associated settings,
# see the Advanced Configuration page linked at the top of this file.

# For a receiver type of ‘rtlsdr’, this setting controls the dongle gain.
# -10 means AGC / maximum gain; other values mean a gain value in dB.
rtlsdr-gain 48.6
receiver-type other # updated by fa_piaware_config
receiver-host 192.168.100.2 # updated by fa_piaware_config
receiver-port 30005 # updated by fa_piaware_config
#
# OTHER CONFIGURATION
#

# Should automatic system updates (initiated by FlightAware) be allowed?
allow-auto-updates yes

# Should manual system updates (initiated by you from the website control
# panel) be allowed?
allow-manual-updates yes

# Should PiAware enable multilateration where possible?
# You may need to disable this if multilateration overloads your receiver.
allow-mlat yes
mlat-results yes
mlat-results-format beast,listen,30005 ext_basestation,listen,30106

# Should PiAware enable reception of Mode A/C messages when requested?
# You may need to disable this if processing Mode A/C overloads your receiver.
allow-modeac yes

But my MLAT icon on the site RED :frowning:

You still have some kind of fundamental install problem, possibly two copies of piaware running.