PilotAware

British Forum => General Discussion => Topic started by: roweda on December 18, 2015, 08:38:11 pm

Title: PilotAware Release 20151218 - Bugs
Post by: roweda on December 18, 2015, 08:38:11 pm

Lee

I love the 5 second scrolling between Registration and Flight Number, but there seem to be some serious errors with the Registrations depicted when I compare the same Hex Codes and Registrations reported by FR24.

A couple of examples at approx. 20:35 are

PAW - VP-BDL Hex 4242F4 - FR24 VP-BBS
PAW - TF-IFD Hex 4CC4D4 - FR24 TF-SIS

Also the Traffic screen is showing DIST-KM. Surely this should be NM?

Dave

Title: Re: PilotAware Release 20151218 - Bugs
Post by: Admin on December 18, 2015, 09:27:05 pm

Hi Dave

Thanks for the feedback.
Please double check your findings, if the hex code is a different value, its a different signature.
The reg is simply a mapping from the hex code

Please let me know if you still think there are bugs.

I was considering making the alternation configurable, ie

Display can be one of ...
-flightid
-reg
-alternate

Thx
Lee

Title: Re: PilotAware Release 20151218 - Bugs
Post by: roweda on December 18, 2015, 09:32:48 pm

I'm just looking at ETH505 heading SE to SW of Southend. PAW - ET-AOB, which is actually a 737. FR24 has ET-ANO, a 777. It is out of Dublin to Addis Ababa so would be a 777.

I like the idea of being able to choose as some people may just want Registration only.

Dave

Title: Re: PilotAware Release 20151218 - Bugs
Post by: Admin on December 19, 2015, 10:52:28 am

Quote from: roweda on December 18, 2015, 08:38:11 pm

Lee

I love the 5 second scrolling between Registration and Flight Number, but there seem to be some serious errors with the Registrations depicted when I compare the same Hex Codes and Registrations reported by FR24.

A couple of examples at approx. 20:35 are

PAW - VP-BDL Hex 4242F4 - FR24 VP-BBS
PAW - TF-IFD Hex 4CC4D4 - FR24 TF-SIS

Also the Traffic screen is showing DIST-KM. Surely this should be NM?

Dave

Hi Dave

Great Catch!
OK, it was a real bug which was pulling in adjacent entries in the ICAO/REG database.
it was overlapping on the last nibble of the ICAO Address, so was only exposed when entries had the same leading 20 bits, but different last 4 bits.

I am about to do a rebuild and upload the fix overwriting the existing release
10 stars for catching this  ;D
Thx
Lee

Title: Re: PilotAware Release 20151218 - Bugs
Post by: Admin on December 19, 2015, 02:21:19 pm

Fix uploaded

http://forum.pilotaware.com/index.php/topic,300.msg4114.html#msg4114

Title: Re: PilotAware Release 20151218 - Bugs
Post by: flying_john on December 20, 2015, 01:08:59 pm

Quote

I love the 5 second scrolling between Registration and Flight Numbe

Is this on the logging screen or on the Skydemon/Runway HD display , because all I get is a Fleche and an altitude displayed on the RunwayHD screen.  Nothing happens if I touch the displayed aircraft, in another thread someone alluded to being able to touch the displayed threat and get further information, can everyone do this ?

John

Title: Re: PilotAware Release 20151218 - Bugs
Post by: Admin on December 20, 2015, 01:57:23 pm

Quote from: flying_john on December 20, 2015, 01:08:59 pm

Quote

I love the 5 second scrolling between Registration and Flight Numbe

Is this on the logging screen or on the Skydemon/Runway HD display , because all I get is a Fleche and an altitude displayed on the RunwayHD screen.  Nothing happens if I touch the displayed aircraft, in another thread someone alluded to being able to touch the displayed threat and get further information, can everyone do this ?

John

Hi john
Unfortunately, this feature is only currently supported by SD.
As you say, RunwayHD only annotates the alt difference

Thx
Lee