2 or 3 mostly "illegal" hex values per plane

[bluebellDE]

Occasionally I have planes on my scren with 2 or 3 hex values. Mostly they are not from a known range. Any ideas?

[wiedehopf]

FlightAware MLAT Network Announcement :

@dbaker

We would like to solve this together as a community rather than have the government solve it for us. So, we’ve come up with a better alternative – for the small number of aircraft on this list (less than 1% of flights, most of which are in the US, and none of which are airline flights), we’ll continue to feed MLAT results to PiAware & FlightFeeder, but with an anonymized Mode S code and no ident. This means your maps will look the same and this has no impact on ADS-B flights or other Mode S data you’re tracking locally, which are decoded and displayed entirely within your device, without the involvement of FlightAware’s servers. We’ll also ask that people limit their use of the FlightAware MLAT results to themselves.

It’s anonymized MLAT results.

[bluebellDE]

Thanks for the explanation. I thought it was an elegant solution to run one dump1090 without a receiver, just to display data, and feed it with several Pis running at home and friends’ sites.

For the MLAT network this seems to look like a redistribution although in fact it’s no redistribution but a range extension.

I am afraid there will be no solution for this issue.

Or is it possible that only the collecting dump1090/piaware connects to the MLAT network to avoid this issue?

[wiedehopf]

@bluebellDE

Thanks for the explanation. I thought it was an elegant solution to run one dump1090 without a receiver, just to display data, and feed it with several Pis running at home and friends’ sites.

I’d call that personal use and wouldn’t worry about it.
At least that’s how i understand the post i linked to.

@bluebellDE

Or is it possible that only the collecting dump1090/piaware connects to the MLAT network to avoid this issue?

dump1090-fa does not forward MLAT messages normally.

So if you forward only 30005 and combine them it’s not problem at all.

Have a look at this if you want to combine multiple feeders:
GitHub - wiedehopf/combine1090: Combine data from multiple ADS-B receivers into one readsb decoder / tar1090 webinterface

Just disable port 30105, that is normally where MLAT results are available from piaware.

But as i said as long as the combined site is only for personal viewing, then i don’t see a problem a problem with MLAT results being in the mix.

The link above starts a separate dump1090-fa in net-only mode because once you combine data streams from multiple receivers, MLAT won’t work because the timestamps from the different receiver don’t match.
So i wouldn’t feed the combined feed to flightaware but rather the individual receivers and just combine them for viewing.

[bluebellDE]

Thanks, that was helpful.