fa-mlat-client 0.2.4 crashes when connecting to local airspy_adsb about piaware HOT 18 CLOSED

Both piaware and fa-mlat-client expect a beast-format stream, not an AVR stream.

from piaware.

Understood, is there a way you could add reading an AVR stream using piaware-config or otherwise, this would mean people can use their airspy running from a pi to push data to flightware

from piaware.

Newer mlat-clients understand AVR. faup1090 is a bit trickier. You can't produce a Beast stream?

from piaware.

Actually, looking at that error more closely, it is a plain AVR stream with no timestamps, not the avrmlat format, so even with an updated mlat-client it will be no good for mlat.

from piaware.

Uhm, strange i'm running : airspy_adsb v1.1 with -e (Enable the extended output (MLAT and RSSI))

ping @bvernoux and @touil

from piaware.

The decoder is complaining that the first byte of the stream is 0x2A - this is '*', the standard format with just the message data. The format which has RSSI and timestamp would start with '<'.

Beast-format data is pretty much the de-facto standard these days, I am surprised airspy_adsb can't generate it. If the source for airspy_adsb was available, I would take a look, but a quick search doesn't find it so I suspect it's just another closed-source thing.

from piaware.

uhm, indeed that seems to be the case,

@bvernoux and @touil can you add beast output ?

from piaware.

In the mean time, is there a way to tell piaware to connect to a remote dump1090/VRS port ?

from piaware.

Not on the current version of piaware. It's in the next version.

from piaware.

Perfect, thanks

from piaware.

btw is this hardcoded? faup1090 --net-bo-ipaddr localhost
I can just change it to connect elsewhere ?

from piaware.

The software is still experimental but fully usable with PlanePlotter. Currently we use this extended format:
*;<32bit MLAT>;<8bit MLAT Frequency>;<16bit RSSI>;

The <8bit MLAT Frequency> tag is the oversampling multiplier: 1 => 2MHz; 2 => 4MHz; … 10 => 20MHz; etc. Zero is an invalid value.

from piaware.

Yep, sure, you can tweak that directly. The change in the next piaware version is just to hook that argument up to the config system so it's easy to change. See https://github.com/flightaware/piaware/blob/dev/programs/piaware/faup1090.tcl#L144

from piaware.

Frankly I doubt I'm going to support yet another format in mlat-client if it's only generated by one piece of closed-source software.

from piaware.

Your call.

from piaware.

OK, so airspy_adsb is unsupported for mlat at the moment.

from piaware.

fast support by @touil , new version with beast support, https://t.co/XwKelfwuL9 (-f beast)
however
mlat(7442): Problem reading receiver messages: Out of range timestamp seen (last 4142366797, now 553222221)
maybe issue like : mutability/mlat-client#1

from piaware.

I think it is generating the timestamps as little-endian; they should be big-endian.

from piaware.