Looks like we have a new arrangement for the MLAT regions (4 and 5) in Europe. Cutting Germany into 2 pieces, will result in losing most of the low flying MLAT traffic in Germany. Sad news
Germany is in one piece. New region boundary is Polish border (now we bolong to Asia ). Probably now James is playing with boundaries to test server load. MFG Marcin
You won't lose most of low flying aircraft in Germany. In fact, it should improve the MLAT by splitting up the load between server instances. Feeders only MLAT aircraft they have in range anyway.
Yes, you are right. At least if there is anyone else in your area which is able to join the MLAT calculation. At the moment below 10.000ft I can only look to the east now. Mostly, because I can not communicate with the other feeders which are 20 or 50 km to the west. FA MLAT results have overtaken Adsbex for the first time since 2015. And I am pretty sure that's the same situation for anyone which is located along that border. Are you calculating MLAT between the regions as well? I know it is difficult to define the borders. It is always a compromise. Regards Stefan
James, did you look into region 6? There are some feeders which now doesn't belong to any region (probebly between 1 and 2 degrees East).
So the issue is not only does the MLAT server have a limit to the connected clients, but it has a limit to the number of messages it can process. Moving the borders around will help, you are only going to get MLAT data for aircraft your feeder can see. So at low altitude it shouldn't matter a great deal if you are on a border. FlightAware groups feeders into clusters locally, in a round robin, so they aren't actually processing all feeders and all data. Since FA employs Oliver the developer of the original MLAT server, client , and the dump1090 mutability fork - they have got him to stop development on the software that isn't FlightAware. FlightAware wants to shut everyone down, they believe they own ADS-B data around the globe and all the rights to sell it. It is what it is, if anyone wants to fork and pick up improving where he left off - code is on github. Until that time, or until ADSBx can afford to pay a developer with the skills to develop better MLAT. We do what we can and try to get around FlightAware road blocks.
This issue has to do with how the MLAT client connects. We look that connection string, but it doesn't send the string in the same order. We look for 'lon' and route accordingly - sometimes it doesn't send it and feeders end in MLAT 6 as the 'catch all'. Some feeders like ED, who get consistently put in there, you can probably put that issue on the feeder and having an Internet connection that might be losing packets, etc. So we never get the 'lon' and it just gets put in 6. My idea to improve is to have new feeder images check the configured feeder lat/lon .. then use the appropriate port when connecting to MLAT for thier region. For guys like Ed that have problems, we can login and change the MLAT client port to point to the port for his zone. But getting some people to put ZT on it so I can edit and monitor is an issue - for others it is not. Makes sense?
In this case I think there is a gap between region boundaries. Freqman is feeding for a long time without any issues and now landed in region 6.
I can look today.. Possibly ... I keep not seeing feeders on Western Coastal Ireland which is odd too
See if that changes anything. I haven't moved one of the regions to the new server yet, just been too busy.
https://www.axios.com/russian-military-gps-nato-war-games-2b7d7e1f-1095-4ea0-9770-ca7b447a60fe.html Did you read this? Might explain some of the coverage failures.
But not for MLAT aircrafts . This position is "estimated". It could cause some problems with tracking of some ADSB aircrafts (it can explain why once I've seen one over Norway and after few minutes over Germany).
@James Compliments! The matrix of Sync4 is now much faster accessible and after a reboot of my Rpi it is accepted a lot earlier. A lot of people have to be happy about that!
Coverage-3 over UK still getting smashed. I'll see if I can get that on a 5GHZ alone before too long.
Yes, the sync matrix is now working much faster. But the overlap around the borders is only working for aircraft at high altitude. Below 10.000ft there is nearly no overlap. As you can see on the 2 attached pictures (comparision), currently no MLAT possible below 5000ft in south-west Germany (west of the border). Some weeks ago, we could see landing aircraft at Stuttgart (MLAT) till 900ft. Regards Stefan
Not much I can do. Get more feeders on each side of the wall .. Looking at the map .. that shouldn't be an issue ... maybe someone's feed in that area is down.
