Hello,
Thanks again a lot for supporting this issue.
The latest examples needs to be interpreted right. Let’s focus on one:
SKY48FD60>OGNSKY,qAS,SafeSky:/083915h5359.04N/01626.91E’290/099/A=004435 !W20! id2048FD60 +000fpm gps4x1
Means that station called “SKY48FD60” coming from the APRS TO-CALL transmission system is “OGNSKY”. This station is transmiting a position for id “48FD60”.
Because it’s coming from OGNSKY with a station starting with SKY, this ID is NOT intended to be a ICAO hex code as defined by ATDB - ICAO 24-bit addresses - Decode
We had some exchange with the team at OGN tonight, and they confirm that when an ICAO hex code is to be used as an official ID, the expected message format is:
ICA48FD60>OGNSKY,qAS,SafeSky:/083915h5359.04N/01626.91E’290/099/A=004435 !W20! id2048FD60 +000fpm gps4x1
Where the station name starts with “ICA”.
From OGN documentation: Aprs Interaction Examples - Open Glider Network Project
Therefore, as agreed with OGN team, we have just applied a patch to use ICA as a station prefix for ICAO codes.
When we now use ICAO hex “4497C3”, we are getting the correct messages (see screenshot).
We are also in touch with PilotAware team to ensure we are all aligned on the approach.
Fly Safe,
Tristan
