ICAO HEX Code, not Callsign

[Timothy]

I heard nothing in General Discussion, so I'll try here:

I have FX, iPhone, iPad.

The FX connects to the iPhone for iGrid and iPad connects to FX by WiFi...all standard stuff.

The iPhone also runs SafeSky and SkyDemon on GDL90.

Why is it that (fairly often but not consistently) the callsign on the iPad shows the ICAO Hex code, not the reg?

[Timothy]

Another example:

[grahambaker]

It could be that the aircraft in question has not been found on the lookup for some reason, so the box is displaying the ICAO ID by default.

[PaulSS]

That would make sense but I have to admit I am seeing more and more HEX codes, whereas I used to see none. Quite often I'll see a HEX code and then iGrid kicks in and the registration appears.

I think SafeSky complicates matters, especially when there are loads of people who haven't set it up correctly and end up ghosting themselves but I think FLARM seems to upset the whole HEX/registration matter as well.

I don't really know why I have the registrations turned on. After all, it's not going to make any difference in avoiding. Turn the function off and that may solve the HEX code problem 

[tnowak]

Are the aircraft depicted in your screenshots coming from FX or Safesky?
Or can't you tell which system is providing those aircraft targets?
Tony

[grahambaker]

I don't really know why I have the registrations turned on. After all, it's not going to make any difference in avoiding. Turn the function off and that may solve the HEX code problem 

I think there is some value, as you can link a radio call to a specific target. On more than occasion a numpty inbound on a similar track has reported a position when they’ve been at nothing like it according to the traffic display and the visual contact I may have had.

[Timothy]

I find the registrations or call signs invaluable. It greatly increases situational awareness in the approach to the airfield and in the circuit.

I’m glad it’s not just me seeing this new phenomenon.

The question is, what can be done about it?

[Timothy]

Are the aircraft depicted in your screenshots coming from FX or Safesky?
Or can't you tell which system is providing those aircraft targets?
Tony

I have two systems, which I believe to be independent.  The two pictures are from an iPad which is connected by WiFi to FX, which is picking up a mobile data signal from the iPhone for iGrid.

It so happens that the same iPhone is separately running SafeSky and SD (connected locally to SS by GDL90) but I don't believe that there any data touchpoints between the two (it being annoyingly impossible to run a hotspot for iGrid while connecting the WiFi to PAW.)

So everything you see is pure PAW/iGrid, and SafeSky is a red herring.  I can certainly run the whole thing when I next fly without SafeSky, so the iPhone is nothing but a hostspot for iGrid, but I know that I'll see the same.

[Timothy]

No word from PAW HQ?

[Admin]

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

[Timothy]

Well, at least a cogent explanation. 

There are two systems in the affected aircraft, and I don't believe that they are connected at any protocol level:

[Admin]

I saw mention of SafeSky, is that not correct?

Can you describe in detail the connections to the FX and the software being run ?
Thx

[Timothy]

I thought that was exactly what that picture did?

Though a picture speaks 1000 words, I'll try again in words, mainly copying from the first post:

I have FX, iPhone, iPad.

iPad connects to FX by WiFi, running SkyDemon, using Pilotaware as its source.

iPhone runs SafeSky and SkyDemon,  set to GDL90.  It only uses mobile data.

The two iDevices are mutually entirely independent.

However, the FX connects to the iPhone for iGrid using the iPhone hotspot. 

Unless you tell me differently, I do not believe that the FX using the iPhone as a hotspot would introduce SafeSky in any way to FX.

However, I am making four flights on Saturday, and I will simply run the iPhone as a source of mobile data for iGrid and nothing else, and see whether the problem persists.  I am convinced it will.

[Admin]

Interested to hear results of experiments

do you have the premium version of safesky that allows you to connect to Pilotaware, if so I am pretty sure that will be what causes the issue

[Timothy]

Indeed I do and I will check at the weekend, but I would be amazed if SafeSky can “see” PAW simply because it is using the iPhone as a hotspot!