Messages

1

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 25, 2025, 09:39:21 pm »

It's an asterisk that's in the field and remains in there when you paste in the code!

Without it, it woks, thank you!

But, sadly, of course, it gets us no further.  As others have said, it doesn't show what I have received and why.

I wonder if any progress has been made on this reg thing?

2

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 25, 2025, 07:24:51 pm »

So, I am now at my desk, and I get this.

What am I doing wrong, or different?  This is driving me mad!

How are you all seeing me and I see nothing, on iPhone or PC browser?

3

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 24, 2025, 06:33:01 am »

I can’t be patronised, the depths of my ignorance are boundless and yes!

I have done a screenshot of my iPhone and tried to attach it, but I’m told that the size of the the file is too great to attach.

This is yet another frustration.  Why do they allow, even have a special button for, iPhone photos, and then not allow screenshots, the most obvious use of the feature?

Nothing seems to be tested by users before rollout any more!

Anyway, I have cropped it, let’s see if that works…

No, that doesn’t work because the cropped screenshot is a jpeg and it doesn’t accept jpeg.

It’s just one thing after another after another!

4

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 23, 2025, 10:34:56 pm »

That is, indeed, me. I don’t understand why I don’t get the same results from the same input

Today I flew in the other aircraft with SE2, but the same iPad and SD, and all the registrations were solid, so I hope that eliminates those two variables from the equation.

5

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 23, 2025, 11:23:53 am »

I’ve been to that URL, put in my ICAO code, put in All in both dropdowns, set the date and time to when I flew from Biggin to Sandown yesterday, with 3 hours set, and it doesn’t find anything.

I’m on an iPhone and can’t find a way of attaching a screenshot to this forum (yet another frustration!  )

6

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 23, 2025, 06:50:12 am »

Head over to playback and use the "groundstations" option for a track log.

Sorry, but I still don’t know what this means. 

I’d love to “head over to playback”and download a track lo, but is this on the web interface of the FX as Paul suggests (in which case where?), or on a PAW website, in which case which one? Vector?  Do I need to log on to get my own data, or is it in the public domain?

7

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 22, 2025, 07:01:28 pm »

No, but because it's all made so difficult. 

Lack of documentation and consistency. 

I spent ages in the aircraft, with the engine running, looking for the "Tracks" icon, finding no documentation as to where it was or how to find it.

Having to ask ChatGPT, getting home to find nothing useful on the website, trying to log on to the website to be told that I couldn't have a login in unless I agreed to accepting marketing emails, and not being able to uncheck that once I am logged and, having been through all that, there still being no way I could find to download the log files, so, presumably, the only thing I have achieved in an hour of faffing around is more spam.

Very little to do with absence of callsigns, but I am very aware that SE2 and SafeSky, my previous solution, "just works".

Since you ask...

Oh, and yes, Garmin TAS shows callsigns, since you asked what you thought was a loaded question!

8

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 22, 2025, 06:42:43 pm »

I tried to download the Tracks from the web interface today, but there was no Tracks icon.

I asked ChatGPT (as I couldn't find anything helpful on the PAW documentation, and the engine was running) and it seemed to be saying that on the FX, you don't download from the device, but from the web. But I can't find where on the web.

I tried logging in to pilotaware.com (which it would only let me do if I consented to receiving marketing emails, which I suspect is illegal), but still couldn't find anywhere to download the files.

I'm really beginning to regret this purchase.

9

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 19, 2025, 08:49:42 pm »

Alan,

Thank you.  It's going to be next week before I climb back aboard the little one with the FX installed, I will be living the life of "proper" TCAS until then, but I'll certainly have a go on the Web Interface then, thank you.

10

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 19, 2025, 06:42:44 pm »

I can report that with the burner phone used as a hotspot the problem persists, so this is definitively not a SafeSky Issue.

Comments like "arp -a" lead me to remind people that we are no longer in the world of Raspberry Pis and soldering irons.  This is now a commercial product sold for a not inconsiderable amount of money, on the premise that it "just works."

Alan, that leads me on to saying that I would love to take you up on the offer to look at the log file, but I don't know where to start.  Please give me step by step instructions (from an iPad.)  Thank you!

11

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 19, 2025, 07:44:48 am »

In today’s experiment, I will use a burner iPhone, with almost nothing installed on it, only as a hotspot, to see whether I still see ICAO HEX codes.

Am I the only one seeing this?  I feel quite isolated and unsupported.

12

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 17, 2025, 04:11:06 pm »

With SafeSky completely removed from the iPhone, I am still getting the same symptoms intermittently sometimes ICAO code sometimes Reg, even on the same aircraft.  Sometimes alternating between the two quite rapidly, sometimes just stuck on one or the other.

13

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 15, 2025, 08:27:45 pm »

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!

14

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 14, 2025, 10:26:53 pm »

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.

15

Technical Support / Re: ICAO HEX Code, not Callsign

« on: May 13, 2025, 10:20:20 pm »

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: