Page 1 of 1

Congestion of planes who are not active anymore

Posted: Sat Mar 03, 2018 7:52 pm
by jaapr
Hello,

I'm running a VRS on Ubuntu/Mono for a year now and this week I added a 2nd feed to the VRS (both feeds are on remote locations). All is fine, except one annoying thing: it looks like planes from the new feed remain in a kind of active status in the List overview and sticky on the map while they are already out of the area (or landed at nearby airport).
For example on final for the runway there is a congestion of about 25 planes, looks like they are all stalled.

I tried to troubleshoot, but I can't see any errors in the server. Also I thought about performance of the server (running virtual in the cloud) but load is very low. I have the database plugin installed and thought about I/O issue, but this also looks fine.

Is this behavior seen before ?

Many thanks,
Jaap

Re: Congestion of planes who are not active anymore

Posted: Tue Mar 06, 2018 12:33 am
by Radio Active
Is this 2nd feed from a 2nd person?

Re: Congestion of planes who are not active anymore

Posted: Tue Mar 06, 2018 5:11 pm
by jaapr
Hi,

Thanks for the reply !

Yes, the 2nd feed is from a 2nd receiver from a different location. Both receivers send the output from dump1090 to the remote VRS. Both receivers have a mlat-client to adsb-exchange and they forward also the mlat results to the VRS.

In summary, the VRS receives data on 4 inbound ports from 2 receivers. This worked fine from 1 receiver (dump1090 and mlat-results), but with the 2nd receiver there is the congestion of planes around the airports but also scattered over less busy areas.

It looks like it can not handle the outdated planes (or maybe garbage collection are a better words?). Let me know if my config is not correct, should I just combine the inbound data in 2 ports ?

Kind regards,
Jaap

Re: Congestion of planes who are not active anymore

Posted: Mon Mar 19, 2018 12:04 am
by agw
From what I remember aircraft from MLAT feeds have higher display timeouts because the MLAT client can have large intervals between each update for them. However, I'm not sure that those timeouts are configurable, I think they're a multiple of other timeouts.

I'll be revisiting the handling of MLAT and its configurability (or lack thereof) for the next release.

Re: Congestion of planes who are not active anymore

Posted: Tue Mar 27, 2018 9:47 am
by jaapr
OK. Thanks for the reply.
I will experiment a bit and turn-off the mlat-data for a while and see if the issue disappears.

Cheers,
Jaap