search

mutability / mlat-client

Mode S multilateration client
GNU General Public License v3.0
82 stars 75 forks source link

Receiver set to type Beast will not show sync with Rx type Radarcape. #23

Closed marcus-aa closed 7 years ago

marcus-aa commented 7 years ago

An actual beast, set to --input-type beast, will never show sync stats towards receivers of type radarcape. If set to dump1090, it will show sync.

The log file indicates that the receiver pair is used for solutions, so it actually has sync, but not shown in the sync stats table.

If 2 dump1090 system are both set to --input-type beast (for testing this issue, or by mistake), they will also not show sync with radarcapes, not with real beast systems, and not with each other, but with normal dump1090 systems....

(The client will auto-detect the correct format but has already informed the server of the manually set format, and as discussed, the on-the-fly format change is not implemented in mlat-server. )

What is the difference between beast and dump input formats?

mutability commented 7 years ago

This sounds like a server-side issue?

marcus-aa commented 7 years ago

Quite possible. It changes behaviour with --input-type in the client, but may very well be all in the server code.

Should I move it to the server issues?

mutability commented 7 years ago

Well, without a specific bug report about the client misbehaving, there's not much to be done in the client side. On the server side, unfortunately I have about zero spare time to look at it.

mutability commented 7 years ago

(this is probably just another case of the server code not understanding the client clock changes)

marcus-aa commented 7 years ago

I know. I'll document it there anyway.