Initial indications are that there is no detectable difference in the output
Uh oh, it would appear I spoke too soon !
Since hooking RB up to the EGLL web server I've started to see anomalies like a Final Alt of 38000' for an aircraft on the LHR ILS.
After doing a bit of troubleshooting, it appears these are instances of the previously-reported bug where RadarBox gets confused between two aircraft with similar hex codes.
For example, here's an extract from the RBL log showing G-EUUL/4009D9 inbound on the BAW501 earlier today:
$PTA,20100513123850654,4009D9,,1800,,,,,51.4781,-0.2946,,
$PTA,20100513123850654,4009D9,,1800,163.0,269.6,-768,,51.4781,-0.2934,,
$PTA,20100513123850654,4009D9,,1825,,,,,51.4781,-0.2922,,
$PTA,20100513123854791,4009D9,,1725,164.0,269.3,-1088,,51.4780,-0.3012,,
$PTA,20100513123854791,4009D9,,1750,164.0,269.7,-896,,51.4780,-0.2977,,
$PTA,20100513123858910,4009D9,,1650,,,,,51.4780,-0.3024,,
$PTA,20100513123858910,4009D9,,1650,164.0,269.3,-896,,51.4780,-0.3036,,
$PTA,20100513123903039,4009D9,,1600,162.0,270.0,-768,,51.4780,-0.3108,7474,
$PTA,20100513123903039,4009D9,,1600,162.0,270.0,-896,,51.4780,-0.3098,,
$PTA,20100513123903039,4009D9,,1625,163.0,269.3,-768,,51.4780,-0.3087,,
$PTA,20100513123907170,4009D9,,1550,162.0,270.0,-1024,,51.4780,-0.3147,,
$PTA,20100513123907170,4009D9,,1575,,,,,51.4780,-0.3134,,
$PTA,20100513123911293,4009D9,BAW501,1500,161.0,270.4,-960,,51.4780,-0.3168,,
$PTA,20100513123915421,4009D9,,1450,,,,,51.4780,-0.3248,,
$PTA,20100513123915421,4009D9,,1450,152.0,270.0,-448,,51.4780,-0.3236,,
$PTA,20100513123919554,4009D9,,1425,146.0,269.2,-768,,51.4780,-0.3278,,
$PTA,20100513123923679,4009D9,,1350,,,,,,,,
$PTA,20100513123927810,4009D9,,1300,,,,,,,,
$PTA,20100513124347567,4009DD,,38000,446.4,15.6,0,,,,,
$PTA,20100513124404066,4009D9,,38000,,,,,,,,$PTA,20100513124408102,4009DD,,38000,,,,,,,,
$PTA,20100513124412131,4009DD,,38000,,,,,,,,
$PTA,20100513124416165,4009DD,,38000,,,,,,,,
$PTA,20100513124420207,4009DD,,38000,,,,,,,,
$PTA,20100513124424333,4009DD,,38000,,,,,,,,
$PTA,20100513124428392,4009DD,,38000,446.4,15.6,0,,,,,
$PTA,20100513124432435,4009D9,,38000,,,,,,,,$PTA,20100513124432435,4009DD,TOM9HP,38000,446.2,15.5,0,,51.2292,-0.7585,5353,
$PTA,20100513124436474,4009DD,TOM9HP,38000,,,,,51.2330,-0.7568,,
$PTA,20100513124440525,4009D9,,37975,,,,,,,,$PTA,20100513124440525,4009DD,,38000,,,,,,,,
$PTA,20100513124444586,4009D9,,38000,,,,,,,,$PTA,20100513124444586,4009DD,,38000,446.2,15.5,0,,,,,
$PTA,20100513124448635,4009DD,,38000,446.2,15.5,0,,51.2610,-0.7445,5353,
$PTA,20100513124448635,4009DD,TOM9HP,38000,,,,,51.2628,-0.7437,5353,
$PTA,20100513124452676,4009DD,,38000,,,,,51.2651,-0.7426,,
$PTA,20100513124452676,4009DD,,38000,,,,,51.2709,-0.7401,,
$PTA,20100513124452676,4009DD,,38000,446.2,15.5,0,,51.2671,-0.7417,5353,
$PTA,20100513124456732,4009D9,,38000,,,,,,,,$PTA,20100513124456732,4009DD,,38000,,,,,51.2727,-0.7393,,
The log lines in red clearly belong to G-OOBC/4009DD, which was airborne at that time, and not to 4009D9, which was safely on the ground at LHR by 1244z.
So, whereas previously the bug was only though to affect
callsigns being shown against the wrong aircraft, it now appears that navigation info is also being wrongly assigned. RB has been similarly confused today with 4009D8/400CD8 and 4008E5/4008F1, so it's certainly not just a one-off.
AirNav, is there any progress on a fix for this ?
Frankly, it's a PITA not being able to use RadarBox as a substitute while my SBS-1 is otherwise engaged, as I'd hoped - in fact I've had to take the LHR website offline for the time being - not a good advert for RadarBox !
