search

flightaware / beast-splitter

Utility that distributes Mode-S Beast output to multiple clients
BSD 2-Clause "Simplified" License
29 stars 9 forks source link

P/p option not documented #4

Open marcus-aa opened 5 years ago

marcus-aa commented 5 years ago

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

Is it working?

marcus-aa commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

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 commented 5 years ago

Looks like this regex needs updating: https://github.com/flightaware/beast-splitter/blob/master/splitter_main.cc#L126

marcus-aa commented 5 years ago

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