Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
marcus-aa opened this issue Apr 20, 2017 · 1 comment
Open

Comments

@marcus-aa
Copy link

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
Copy link
Owner

There's no difference in input formats. The only real difference is that you might want different estimates of receiver clock stability/jitter depending on whether the receiver hardware is a rtlsdr or a Beast.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants