Aircraft displaying incorrect info?

[John Racars]

Assuming that the crew hasn't forgotten to program the correct flight number (which, in my experience, happens rarely)

If that is the case there should be come more and stronger punitive measures....

[DaveReid]

I think I am right in saying RB only checks the route when a new aircraft comes into coverage.

That sounds reasonable, but could you confirm and get back to us ?

It doesn't sound good when Support responds to an issue with an answer that starts "I think ..."

[AirNav Support]

Yes dev will confirm if that's the case. I am sure you understand that we don't always know everything :) we are human.

[John Racars]

we are human.

Hi Support, I thought so!

Do you have enough information from me in this case or should I go on reporting incorrect route info?

Please let me know.

[John Racars]

Hi Support and All,

Until sofar no answer on my latest question to Support so I am reporting you a new one in this "story of the incorrected"....

FYI: BAW909U should be (and so it is in my local database EDDF-EGLL)

[jgrloit]

Hi John,
Seems that a remote data source is being preferred to known local data (Routes table in DB) just like the overwritting by photgraphic sourced data of the GATS aircraft information.

[tarbat]

John, that latest one looks like another corrupted ModeS hex code:

4008B4 = 10000000000100010110100
4008B0 = 10000000000100010110000

Just one corrupted bit.

[DaveReid]

Seems that a remote data source is being preferred to known local data (Routes table in DB) just like the overwritting by photgraphic sourced data of the GATS aircraft information.

No, I don't think it's a routes lookup problem.

The route being displayed in the pop-up for BAW909U is actually the correct route for BAW820, where the hex codes for the two aircraft operating those respective flights differ by only one bit.

Clearly, as Tarbat says, hex codes are getting corrupted somewhere along the line - the question is whether this is happening in the course of the transmission, or after the packet has been received by John's RB.  I suspect the latter, given that there are few, if any, reports of similar problems from anyone else.

If I were in AirNav's shoes, I'd offer John a box swap, if only to troubleshoot the problem.

[John Racars]

where the hex codes for the two aircraft operating those respective flights differ by only one bit.

Hi Dave,

I expected a remark like this all the time; I taked this shot later this afternoon and it looks here goes everything allright:

[DaveReid]

I expected a remark like this all the time; I taked this shot later this afternoon and it looks here goes everything allright:

No, the point I'm trying to make is that when you are picking up two aircraft with hex codes only one bit apart, your RadarBox will sometimes confuse them.  I'm not suggesting that will always be the case.

[John Racars]

your RadarBox will sometimes confuse them.  I'm not suggesting that will always be the case.

OK Dave, clear to me. This all concern my RB only? Or is this a "normal" phenomenon with all RB users?

[RodBearden]

I've never noticed it myself, John, but if MyFlights ever gets to 100 aircraft, it's a very busy day!

Rod

[John Racars]

but if MyFlights ever gets to 100 aircraft, it's a very busy day!

Rod, you must be a verry happy and unstressed person.....

[RodBearden]

It's the red wine keeps me sane ;-)

Rod

[John Racars]

On your health!