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

P/p option not documented #4

Open
marcus-aa opened this issue Feb 24, 2019 · 6 comments
Open

P/p option not documented #4

marcus-aa opened this issue Feb 24, 2019 · 6 comments

Comments

@marcus-aa
Copy link

The P/p option to allow or suppress RC Position reports is not mentioned in the documentation.

Is it working?

@marcus-aa
Copy link
Author

Aha, it seems mlat-client overrides this when oening the port?

beast-splitter[25985]: 127.0.0.1:30005: accepted a connection from 127.0.0.1:40347 with settings RCdfGi
beast-splitter[25985]: 127.0.0.1:40347: settings changed to RCdfGij

How can it be forced to "p", no positions ?

@mutability
Copy link
Contributor

Like all the other options, --force should do this. nb: mlat-client doesn't touch this option, see https://github.com/mutability/mlat-client/blob/master/mlat/client/receiver.py#L127

Can you explain what you're actually trying to do here?

@marcus-aa
Copy link
Author

I'm trying to prevent RC position messages from reaching mlat-client, while keeping the GPS timestamps on normal traffic. I'm getting errors on mlat-server related to RC receivers and I'm trying to work out if they are related to these position updates.

@marcus-aa
Copy link
Author

If I add "p" to force it refuses it.

root@__~#/usr/bin/beast-splitter ... ... --force RCdfGip --listen localhost:30005:RCdfGip
the argument for option '--force' is invalid

@mutability
Copy link
Contributor

@marcus-aa
Copy link
Author

The P/p option is present in the list in beast_settings.h, but not in beast_settings.cc

mutability added a commit that referenced this issue Oct 6, 2022
Update docs to describe the p/P options.

Fixes #4 (better late than never..)
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