-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comments
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 How can it be forced to "p", no positions ? |
Like all the other options, Can you explain what you're actually trying to do here? |
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. |
If I add "p" to force it refuses it. root@__~#/usr/bin/beast-splitter ... ... --force RCdfGip --listen localhost:30005:RCdfGip |
Looks like this regex needs updating: https://github.com/flightaware/beast-splitter/blob/master/splitter_main.cc#L126 |
The P/p option is present in the list in beast_settings.h, but not in beast_settings.cc |
Update docs to describe the p/P options. Fixes #4 (better late than never..)
The P/p option to allow or suppress RC Position reports is not mentioned in the documentation.
Is it working?
The text was updated successfully, but these errors were encountered: