Marcus AAkesson

If I restart vdlm2dec it will start working again, but this is a headless, remote client and I need to keep it running unattended. acarsserv does not need to be...

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...

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...

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

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

I have another one here that is stuck right now if you need further details. Here the other side is actually dump1090-fa on another Rpi. ``` INPUT_OPTIONS="--net 192.168.1.8:30005" OUTPUT_OPTIONS="--listen localhost:30005:BCdfGi...

Revisiting. In my experience with TCP data in NMEA & AIS networks, where data is similar and often unidirectional, there is a need to have a data timeout on the...

Re-visiting. Same problem on another host. It has sat there for a week now thinking the connection is up. A data timeout is needed. 9404 /usr/bin/beast-splitter --net 192.168.0.102:10002 --listen localhost:30005:RCdfGi...

My understanding is that Beast-splitter "knows" on a data level that it is not receiving status messages (it is a Radarcape), therefor the "Not connected..." messages , but the TCP...

> I doubt I'll get to this any time soon - can you look at doing a PR for this? I will look, but my programming skills are unfortunately more...