Recent Posts

81

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by Timothy 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!  )

82

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by buzz53 on May 23, 2025, 10:19:43 am »

Timothy, my apologies for wasting your time. I have the older PAW unit which records the track (and other data including received traffic information) internally. I didn't realise (and it's disappointing) that the new model no longer has that facility. Steve, if you look back you'll see that the ground based track logs won't help here.

Alan

83

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by steveu on May 23, 2025, 07:54:54 am »

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

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

Visit this URL, if that's a good enough explanation? Fill in the boxes with the correct data. Leave Stations set to all.

https://playback.pilotaware.com/playback/groundstations/

84

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by Timothy 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?

85

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by steveu on May 22, 2025, 10:13:28 pm »

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."

This was a thrown away comment to say this it is easy for any device to find out what else is on the network, and act accordingly. Just one line of code.

So if you say:

"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!"

I work with stuff that can see other stuff even when not on the same VLAN and with the ability to reconfigure network devices wrongly configured.

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

Until you look at latency (SafeSky) and RF performance (SE2) - I've got side by side of SE2 and the older Rosetta in the same aircraft on the same flight. Just works... not for me. Ditto looking at SafeSky with aircraft flying over a reference point.

As I understand it, FX doesn't have log files. But I haven't looked at it for 4 months, as that aircraft has been getting fixed. Head over to playback and use the "groundstations" option for a track log.

86

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by Timothy 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!

87

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by PaulSS on May 22, 2025, 06:48:36 pm »

I'm really beginning to regret this purchase.

Why, simply because you can't see a callsign?

What do you see on TCAS.......loaded question.

88

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by Timothy 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.

89

Technical Support / Re: ICAO HEX Code, not Callsign

« Last Post by PaulSS on May 20, 2025, 05:38:53 pm »

Spitfire G-TCHI just flew right over my house. My ATOM station only saw his HEX code, despite him being equipped with PAW and ADSB Out (not SkyEcho). He remained HEX code only until landing at Goodwood.

90

Technical Support / Re: License renewal - multiple years

« Last Post by A_Vinning33 on May 20, 2025, 10:53:20 am »

Hi,

It's not something that we usually offer, but if you want to make a special request we'd be happy to accomodate.

I'll send you a PM.

Thanks,

Ashley