mlat-server by mutability

Want to post something that doesn't quite fit into the other forums? This is the place for that.
jonfear
Posts: 365
Joined: Sat Feb 09, 2013 12:15 pm
Location: Wick St Lawrence
Contact:

Re: mlat-server by mutability

Postby jonfear » Mon Jan 11, 2016 7:38 am

Jayme

I guess this is for your app.

The server only returns the MLAT data for aircraft seen by the client. The whole picture is retained on the server.

Cheers

Jon
http://www.360radar.co.uk, the new name for MLAT Radar in the UK and Western Europe.

Former PP feeder Bm. No longer feeding. I do not have time to sort out imaginary problems with NTP
when it has been working fine for 2+ Years.

Jayme
Posts: 2
Joined: Fri Jan 08, 2016 12:57 am

Re: mlat-server by mutability

Postby Jayme » Mon Jan 11, 2016 8:31 am

Thanks for the quick reply Jon.

big
Posts: 1
Joined: Fri Feb 12, 2016 8:59 am

Re: mlat-server by mutability

Postby big » Wed Mar 09, 2016 7:11 pm

How to synchronize clients ?

On the www of mlat-server any cell (table) is grey :(

Pliz help

Skibox
Posts: 113
Joined: Mon Apr 07, 2014 7:06 pm
Location: ESGG

Re: mlat-server by mutability

Postby Skibox » Thu May 12, 2016 11:27 am

big wrote:How to synchronize clients ?
On the www of mlat-server any cell (table) is grey :(


Same answer as earlier in thread: What does the logs and consoles say? What type of clients are you using ?

REPOST:

Your main problem seems to be that the clients never sync. Therefor my questions about your clients.

On each client console you should see something like this:

Fri Dec 11 12:03:39 2015 Server status: ready
Fri Dec 11 12:03:39 2015 Receiver: 106.0 msg/s received 2.0kB/s from receiver
Fri Dec 11 12:03:39 2015 Server: 0.0 kB/s from server 0.5kB/s TCP to server 0.0kB/s UDP to server
Fri Dec 11 12:03:39 2015 Aircraft: 5 of 5 Mode S, 9 of 15 ADS-B used
Fri Dec 11 12:18:39 2015 Receiver status: connected

If not, You are not getting data the client can work with!

This should also be obvious from the sync stats output, var/www/html/sync

When you get useable data in, you should see more than just connect messages in your server log:

20151126 20:56:15.209 INFO client [xxx] Handshake successful (RX1 v3 dump1090 0.2.4 tcp zlib2)'
20151126 20:56:16.113 INFO client [yyy] Accepted new client connection
20151126 20:56:16.115 INFO client [yyy] Handshake successful (RX2 v3 sbs 0.2.4 tcp zlib2)'
20151126 20:56:51.508 INFO client [zzz] Accepted new client connection
20151126 20:56:51.511 INFO client [zzz] Handshake successful (RX3 v3 dump1090 0.2.4 tcp zlib2)'
20151126 20:57:02.758 INFO kalman 4CA7DE acquiring.
20151126 20:57:03.392 INFO kalman 502C7D acquiring.
20151126 20:57:03.474 INFO kalman 489788 acquiring.
20151126 20:57:03.660 INFO kalman 502C7C acquiring.
20151126 20:57:06.351 INFO kalman 502C50 acquiring.
20151126 20:57:11.872 INFO kalman 43EA6E acquiring.
20151126 20:57:29.842 INFO kalman 502C7D acquired. <------ Here a position is found
20151126 20:57:40.115 INFO kalman 502C7E acquiring.
20151126 20:57:45.027 INFO kalman 3C4DD8 acquiring.
20151126 20:57:57.683 INFO root Halting on SIGTERM
20151126 20:57:57.683 INFO root Server shutting down.
20151126 20:57:57.683 INFO client [RX1] Disconnected
20151126 20:57:57.683 INFO client [RX2] Disconnected



/M

maxspb
Posts: 2
Joined: Tue Nov 08, 2016 12:32 pm

Re: mlat-server by mutability

Postby maxspb » Tue Nov 08, 2016 12:38 pm

I've got RTL2838 USB dongle as a receiver and I try to deploy mlat-server with one client just for test. After that I want to deploy 3 more clients. FlightAware's dump1090-fa takes data from the receiver:
and outputs it via port 30005 to mlat-client in beast format. mlat-client is deployed at the same virtual machine with dump1090 and separate to mlat-server. Every time I see about 3 to 7 planes with or without coordinates, so dump1090 receives well. Also I can draw planes with modesmixer2 app, so messages translated through port 30005 are correct.
dump1090 params: dump1090-fa --interactive --net
mlat-client params: mlat-client --input-connect 127.0.0.1:30005 --input-type beast --lat 55.xxx --lon 37.xxx --alt 6 --user maxspb --server 10.10.10.10:9999 --results basestation,listen,8888 --no-udp
mlat-server params: ./mlat-server --client-listen 9999:9999 --work-dir /home/maxspb/work/mlat/mlat-server/work_dir --write-csv csv --basestation-connect 10.10.10.9:8888
After launch, mlat-client stays for a long time in such state:

Code: Select all

Tue Nov  8 14:47:30 2016 Handshake complete.
Tue Nov  8 14:47:30 2016   Compression:       zlib2
Tue Nov  8 14:47:30 2016   UDP transport:     disabled
Tue Nov  8 14:47:30 2016   Split sync:        disabled
Tue Nov  8 14:47:30 2016 Input connected to 127.0.0.1:30005
Tue Nov  8 14:47:30 2016 Input format changed to BEAST, 12MHz clock


And after that it changes to:

Code: Select all

Tue Nov  8 15:02:31 2016 Receiver status: connected
Tue Nov  8 15:02:31 2016 Server status:   ready
Tue Nov  8 15:02:31 2016 Receiver:   11.2 msg/s received 1.4 msg/s processed (12%)
Tue Nov  8 15:02:31 2016 Server: 0.0 kB/s from server 0.0kB/s TCP to server 0.0kB/s UDP to server
Tue Nov  8 15:02:31 2016 Aircraft: 0 of 0 Mode S, 0 of 1 ADS-B used


So nothing goes to server. Please, help me to trace the problem.

Is this about just one client connected to the server?
Is this about standart USB-dongle antenna?
Something configured in a wrong way?

Yours faithfully, maxspb.
P.S. Sorry for mistakes, I'm not a native english speaker.

Skibox
Posts: 113
Joined: Mon Apr 07, 2014 7:06 pm
Location: ESGG

Re: mlat-server by mutability

Postby Skibox » Tue Nov 08, 2016 3:25 pm

It is normal, just add more clients.

/M

r0b0tix
Posts: 1
Joined: Fri Dec 09, 2016 12:51 pm

Re: mlat-server by mutability

Postby r0b0tix » Fri Dec 09, 2016 12:58 pm

sorry to tag onto this thread but i'm curious. is mlat-server responsible for delivering ADSB derived positions to all clients connected? if not, what solutions are being used for that?

My understanding is that mlat-server and mlat-client may use ADSB positions to judge the range/position of non-broadcasting aircraft, so it does compare them to a point, unless i'm terribly mistaken.

Skibox
Posts: 113
Joined: Mon Apr 07, 2014 7:06 pm
Location: ESGG

Re: mlat-server by mutability

Postby Skibox » Wed Dec 14, 2016 3:05 am

r0b0tix wrote:is mlat-server responsible for delivering ADSB derived positions to all clients connected? if not, what solutions are being used for that?
My understanding is that mlat-server and mlat-client may use ADSB positions to judge the range/position of non-broadcasting aircraft, so it does compare them to a point, unless i'm terribly mistaken.


mlat-client gets all the adsb data locally from the receiver/dump1090. It then uses this data to send sync info to mlat-server, who compares and syncs receiever pairs. This is not optional but an absolute must, to find the TDOA.

/M

Eivndo
Posts: 1
Joined: Fri May 26, 2017 8:43 pm

Re: mlat-server by mutability

Postby Eivndo » Fri May 26, 2017 8:55 pm

Hi. Bringing up this old post, cus I have the same problem.

Code: Select all

Fri May 26 19:44:54 2017 Receiver status: connected
Fri May 26 19:44:54 2017 Server status:   ready
Fri May 26 19:44:54 2017 Receiver:   16.0 msg/s received        5.5 msg/s processed (34%)
Fri May 26 19:44:54 2017 Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Fri May 26 19:44:54 2017 Aircraft: 0 of 0 Mode S, 0 of 4 ADS-B used


But the difference is, i have 3 recievers, with 40-70km space between, all are recieving the same airplanes, but still nothing sendt to server. Do i need 4 or?

Im using dump1090-mutability on the RPI clients.

Edit/Update

My sync table is gray, but how come when all recievers see the same airplanes?

Running on clients x3 ./dump1090 --net --interactive
Running on clients x3 ./mlat-client --input-type dump1090 --input-connect 127.0.0.1:30005 --lat 5x.xxxx --lon 1x.xxxxx --alt 165 --server xx.xxx.xxx.xxx:yyyy --user R
Running on server x1 ./mlat-server --client-listen xxxx:xxxx --work-dir /home/xxx/mlat-server/

Skibox
Posts: 113
Joined: Mon Apr 07, 2014 7:06 pm
Location: ESGG

Re: mlat-server by mutability

Postby Skibox » Mon Jun 12, 2017 10:47 pm

Eivndo wrote:Hi. Bringing up this old post, cus I have the same problem.

My sync table is gray, but how come when all recievers see the same airplanes?


What does the sever log say?

/Skibox


Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 1 guest