Ok - got it working Code: Sat Dec 16 17:28:13 2017 mlat-client 0.2.6 starting up Sat Dec 16 17:28:13 2017 Connected to multilateration server at ...:31090, handshaking Sat Dec 16 17:28:14 2017 Beast-format results connection with ...:30104: connection established Sat Dec 16 17:28:20 2017 Server says: In-development v2 server. Expect odd behaviour. The multilateration server source code is available under the terms of the Affero GPL (v3 or later). You may obtain a copy of this server's source code at the following location: ... Sat Dec 16 17:28:20 2017 Handshake complete. Sat Dec 16 17:28:20 2017 Compression: zlib2 Sat Dec 16 17:28:20 2017 UDP transport: disabled Sat Dec 16 17:28:20 2017 Split sync: disabled Sat Dec 16 17:28:20 2017 Input connected to 127.0.0.1:30005 Sat Dec 16 17:28:20 2017 Input format changed to BEAST, 12MHz clock Sat Dec 16 17:43:14 2017 Receiver status: connected Sat Dec 16 17:43:14 2017 Server status: ready Sat Dec 16 17:43:14 2017 Receiver: 552.0 msg/s received 81.0 msg/s processed (15%) Sat Dec 16 17:43:14 2017 Server: 0.0 kB/s from server 1.2kB/s TCP to server 0.0kB/s UDP to server Sat Dec 16 17:43:14 2017 Results: 32.2 positions/minute Sat Dec 16 17:43:14 2017 Aircraft: 6 of 6 Mode S, 29 of 30 ADS-B used Data is now taken directly from dump1090 - the only thing I had to change was the input type from auto or anything else to dump1090 - looks like dump1090 is the only working option. I will now go ahead and try to get it working via a vrs feeed ... many thanks for your help!
Viva le MLAT! I briefly looked at the code on github for the client / server and I don't see where the username is important for anything but identifying a mlat-client so a server operator can give support.
Same problem like recently, only affecting MLAT. Connection to the server is just kept for a few seconds (probably exchanging key information - thus I'm still on the matrix), then connection gets lost - repeat every 30 or so seconds.
Do you know if they have monitoring for this kind of stuff or is there a recommended way to inform them?
When one of the MLAT servers CPU's is spiked at 100%, sometimes a server won't accept connections or will drop connections. It usually a short term issue. and gets load balanced out. We do montior them them but I need to work on improving the whole shabang! $ and time.
