1
Technical Support / Re: ICAO HEX Code, not Callsign
« on: May 12, 2025, 09:20:13 pm »
This is a long story.
in the FLARM protocol, there is no way to communicate the tailreg/flightID, only the ICAO code.
SD added an extension to the protocol, such that you could append a tailreg to the ICAO code, so in the message that goes from PilotAware to SD the ID changed from (for example)
400ABC
to
400ABC!G-ABCD
Unfortunately, this illegal syntax causes foreflight to crash.
So we try to detect in the following manner.
If there is only a PilotAware connection using UDP (when you tell SD to connect using PilotAware), we will send the registration.
If any device connects using TCP (which is used by Foreflight) we have to disable sending the tailreg, otherwise if the connection is foreflight - it will crash.
Can I ask how you are connecting SD to the FX, and is this the only connection to FX ?
I hear mention of safesky in this thread, I dont know if safesky connects using TCP to FX, if so we have to assume it could be foreflight
thx
Lee
in the FLARM protocol, there is no way to communicate the tailreg/flightID, only the ICAO code.
SD added an extension to the protocol, such that you could append a tailreg to the ICAO code, so in the message that goes from PilotAware to SD the ID changed from (for example)
400ABC
to
400ABC!G-ABCD
Unfortunately, this illegal syntax causes foreflight to crash.
So we try to detect in the following manner.
If there is only a PilotAware connection using UDP (when you tell SD to connect using PilotAware), we will send the registration.
If any device connects using TCP (which is used by Foreflight) we have to disable sending the tailreg, otherwise if the connection is foreflight - it will crash.
Can I ask how you are connecting SD to the FX, and is this the only connection to FX ?
I hear mention of safesky in this thread, I dont know if safesky connects using TCP to FX, if so we have to assume it could be foreflight
thx
Lee