Mlat coverage?

:imp: :imp: :smiling_imp: :smiling_imp:

Forbidden
You don’t have permission to access /posting.php on this server.

Works, thanks.

04/03/2017 01:27:31 mlat-client(1345): Input format changed to BEAST, 12MHz clock
04/03/2017 01:27:31 mlat-client(1345): Input format changed to RADARCAPE, 1000MHz clock
04/03/2017 01:28:01 ADS-B data program ‘beast-splitter’ is listening on port 30005, so far so good

04/03/2017 01:35:12 mlat-client(1345): Server status: synchronized with 4 nearby receivers

" Supported / Enabled (synchronized with 27 nearby receivers)"

4 or 27 ?? anyway, it works…

/M

You are absolutely correct, I force --input-type radarcape_gps and it works. I assumed setting piaware-config receiver-type radarcape would do the same.

/M

(sorry for the multiple posts, trying to avoid the permission problem…)

04/03/2017 02:05:13 mlat-client(1345): Server status: synchronized with 15 nearby receivers

“Supported / Enabled (synchronized with 15 nearby receivers)”

More in sync…

The synchronized with X receivers is just a snapshot of the state at a point in time, probably you had different synchronization when mlat-client logged versus when the server side recorded info for the stats page.

Radarcape now supports MLAT and piaware locally installed.
See here for more details
wiki.modesbeast.com/Radarcape:Ra … stallation

I just updated my radarcape
flightaware.com/adsb/stats/user/ … tats-43617