Oliver Jowett
Oliver Jowett
That is the AVR-style "raw" connection for 1090MHz data: https://github.com/wiedehopf/readsb/blob/c4a0e401d12b7e0c545eee20794abf940b5893bd/net_io.c#L947 UAT is here (note "no_heartbeat" currently, but that's actually a red herring anyway since IIRC it is output-side-only): https://github.com/wiedehopf/readsb/blob/c4a0e401d12b7e0c545eee20794abf940b5893bd/net_io.c#L964
Try the dev branch.,
Yeah, looks wrong. piaware doesn't actually rely on this path which is possibly why I never noticed ..
If it can produce Beast-format output with a stable clock, it's already supported. Otherwise, what output format does it produce?
master HEAD already supports that, try a receiver type of "auto" or "avrmlat" and let me know if it works OK
OK, that's because mlat-server is slightly out of sync with mlat-client at the moment; you'll need to wait until I update the server code.
This seems like the wrong solution given that mlat-client is python3-only
Assuming the error is "Lost connection to multilateration server, no need for input data". This is telling you that the TCP connection to the server went down. Either you have...
What is this pull request about?
Probably "." isn't in your PATH, try ./mlat-server