Routes Reversed

[Runway 31]

Yes Chris, I have the network on and route updates ticked,

Alan

[tarbat]

Okay, I just did some more testing and I'm 99% sure this is being caused by corrupted routes being sent out on the network.  Remember, when a network aircraft transitions to hardware reception, it keeps the route information from the network, it doesn't use the route from navdata routes table.

Airnav, you need to focus on fixing the route information being sent out on the network.

[bratters]

Okay, I just did some more testing and I'm 99% sure this is being caused by corrupted routes being sent out on the network.  Remember, when a network aircraft transitions to hardware reception, it keeps the route information from the network, it doesn't use the route from navdata routes table.

So where do the corrupted network routes orginate tarbat?

[tarbat]

So where do the corrupted network orginate tarbat?

My guess is in the server software routines that Airnav use to do route lookup on network aircraft on their central server.

[Runway 31]

Just got DLH4YL inbound Edinburgh from Frankfurt.  D/b Explorer is blank apart from the timestamp of 201103027144912.

Myflights is showing Hamburg-Frankfurt which is wrong.

I just had a crash of Airnav and on starting up again the ANZ1 and BAW269 are now showing the correct route details

Alan

[tarbat]

Alan, were they received on your local hardware BEFORE the network populated?  The corrupted routes are coming from the Airnav central server, NOT from your local navdata database.  But if the aircraft is received on your local hardwarw BEFORE appearing on the network, the route data is retrieved from your local navdata database.

[sted]

Alan, were they received on your local hardware BEFORE the network populated?  The corrupted routes are coming from the Airnav central server, NOT from your local navdata database.  But if the aircraft is received on your local hardwarw BEFORE appearing on the network, the route data is retrieved from your local navdata database.

That's exactly what I can observe on my machine as well.

[bratters]

So where do the corrupted network orginate tarbat?

My guess is in the server software routines that Airnav use to do route lookup on network aircraft on their central server.

Well if the Airnav central server is as bad as it was when so many of us switched it off and started using FDL, then is it reasonable to assume that network flights have been showing wrong route information for ages?

(Not having Network I can't check this for myself)

[tarbat]

Well if the Airnav central server is as bad as it was when so many of us switched it off and started using FDL, then is it reasonable to assume that network flights have been showing wrong route information for ages?

(Not having Network I can't check this for myself)

Using FDL doesn't change what routes get put on network flights.  Turning off route population doesn't change what routes get put on network flights.  The routes on network flights get sent with the flight itself from Airnav's central server.  When a network flight transitions to a local flight, the corrupted route gets used.

It looks like Airnav have changed something in the software on their central server that processes network flights.  It appears to be using the route data from the previous flight of the aircraft.  Just my guesswork, maybe Airnav can confirm this diagnosis.

[sted]

Glad to see that this long persisting bug gets finally nailed!

[bratters]

Yes yes I follow that but what I'm suggesting is that the airnav server has been churning out bad routes for ages, therefore this problem should not just have surfaced?

[orkney]

Hello

This isn't a long persisting bug. There have always been issues with routes but this is a separate issue that started within the last 24-48 hours.

Andrew

[tarbat]

Yes yes I follow that but what I'm suggesting is that the airnav server has been churning out bad routes for ages, therefore this problem should not just have surfaced?

You're confusing the route lookup routines (that deliver route data to local PCs) and the network aircraft server routines.

I don't think the airnav server is churning out any more bad routes than normal.  What this bug is about is the Airnav server assigning route data to all network flights based on the previous flight of that aircraft.  Test this by:

1. Turn hardware off.
2. Turn network on.
3. See all the corrupted routes (100's).
4. Turn network off.
5. Turn hardware on.
6. See correct routes.

[Runway 31]

I dont know Chris, they were populated before I noted them but I would go along with what you are stating with the exception that I wouldnt agree with the previous flight data being used.  Take ANZ1, its previous flight took it to Heathrow yet it is showing Auckland-Melbourne and it would have reached Heathrow from New Zealand without going to Australia, whether it went east or west.

My observation on the routes before this started is that I thought the routes were being processed quite well with the odd blip but I dont pay particular attention to them as my main priority is the aircraft itself.

Alan

[tarbat]

I dont know Chris, they were populated before I noted them but I would go along with what you are stating with the exception that I wouldnt agree with the previous flight data being used.  Take ANZ1, its previous flight took it to Heathrow yet it is showing Auckland-Melbourne and it would have reached Heathrow from New Zealand without going to Australia, whether it went east or west.

You may be right Alan.  I was just guessing that maybe the corrupted route data was the previous flight.  We need Airnav to confirm how this corruption of routes for network aircraft is happening on their server.

I suspect this response from Airnav may explain the corruption:

2.) We have uploaded data from other sources recently to our online database. We will check to see whether this has been corrupted, can you also confirm its new data which is looking strange (the row will a timestamp) ?