MLAT not showing in Skyview

Hi all, apologies if this is a repeat of elsewhere, but I couldn’t find anything in the forum that matched…

Skyview is not showing any MLAT plots. Whereas upto midday(ish) yesterday it was showing a good number (upwards of 20 plots at any one time).

I am outputting MLAT via VRS and i’m connected & feeding FA as per the console report in the stats page. So it doesn’t appear to be a reception error.

I restarted piaware yesterday which gave me MLAT on skyview for a few hours then they vanished again. Restarting and indeed rebooting made no difference.

Any ideas what is happening?

Thanks!

For info: Pi 2b running flightaware 3.5 image. Blue prostick. VRS is running on PC.

Afternoon,

Same problem here.

I am near Moorabbin airport in Melbourne where there is much general aviation and hence lots of light planes.

Normally I see lots of training flights doing circuits and more than half the planes are reported as being MLAT.

I have three Pi receivers running vanilla Piaware images (2 x 3.3.0 with planefinder and 1 x 3.5.0 image with no changes.)

No MLAT displayed on any of them including Skyview.

My stats do indicate that I am sending some MLAT data to Flightaware.

Hopefully it will be fixed soon.

S.

Glad it’s not just me then!
Ironically, I’m showing MLAT again on skyview…

For info again: I have rebooted & restarted piaware and the Pi itself, cleared my browser cache and sworn at it rather profusely… I haven’t done anything more “technical” than that i.e. done software updates, changed settings etc.

Mlat looks normal here, so it may be a problem specific to one of the mlat regions. I’ll have a poke at it.

Can’t see any problems in the mlat infrastructure, but you have regular mlat message loss:



Jul 19 14:15:45 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 10% UDP message loss
Jul 19 17:06:37 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 20% UDP message loss
Jul 19 17:09:38 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 16% UDP message loss
Jul 19 17:16:39 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 15% UDP message loss
Jul 19 17:17:39 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 11% UDP message loss
Jul 19 17:19:40 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 28% UDP message loss
Jul 19 17:36:46 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 13% UDP message loss
Jul 19 17:48:51 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 11% UDP message loss
Jul 19 18:06:58 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 23% UDP message loss
Jul 19 18:09:01 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 27% UDP message loss
Jul 19 18:15:01 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 19% UDP message loss
Jul 19 18:16:01 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 22% UDP message loss
Jul 19 18:54:15 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 10% UDP message loss
Jul 19 18:55:16 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 14% UDP message loss
Jul 19 19:06:20 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 20% UDP message loss
Jul 19 19:08:21 grung fa_adept_server[58556]: fAT-6ac2d6ec- mlat: 24% UDP message loss


Thanks for having a look. What might be causing the loss? Is it setup related?

Sorry, unrelated question: Why would someone run three PiAware setups on the same location?

It is network related. It’s normal for the network to drop some UDP under congestion but dropping 15%+ is on the high side. Unfortunately it’s hard to say where the problem lies, it could be anywhere between your Pi and the FA servers.

Cool, thanks for the reply, MLAT is showing fine now, i’ll just monitor and see if any patterns develop.

I’m interested in propagation and antennae.

One of them is moving to a new location in the next few days.

I ran two of then on the same antenna whilst I experimented with filters and amplifiers. It was the only way I could see what the actual effect of making a change was.

Once I have found an optimum antenna I’ll end up running one and move on. :laughing:

S.

And it’s down again today. Still apparently feeding and syncd with >350 other sites but not showing on skyview. It was fine late pm yesterday when I was looking.
The gremlins are out and about…

Yeah, this is a system-wide problem now; the band-aid from Monday did not stem the bleeding sufficiently. See the announcement post.

I am working on a proper solution but it is probably a few days away.

Cheers, had limited internet access today so haven’t been able to check.

Morning,

Which specific announcement post were you refering to.

I don’t seem to be able to find anything relevant.

Thanks,

S.

http://discussions.flightaware.com/ads-b-flight-tracking-f21/multilateration-results-temporarily-unavailable-2017-07-21-t39329.html

S.

http://discussions.flightaware.com/ads-b-flight-tracking-f21/multilateration-results-temporarily-unavailable-2017-07-21-t39329.html

Thankyou. :smiley:

S.

MLAT working now here!

08:00 BST 22 July

MLAT has just started working here to at the moment :smiley:

Should all be fixed now, sorry for the hassle.

It’s back for me .

Thanks for your hard work behind the scenes!