Author Topic: ICAO HEX Code, not Callsign  (Read 262825 times)

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #30 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?

steveu

Re: ICAO HEX Code, not Callsign
« Reply #31 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/

buzz53

Re: ICAO HEX Code, not Callsign
« Reply #32 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

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #33 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!  ;D)

buzz53

Re: ICAO HEX Code, not Callsign
« Reply #34 on: May 23, 2025, 12:51:57 pm »
Isn't this you?
Alan
« Last Edit: May 23, 2025, 12:54:04 pm by buzz53 »

PaulSS

Re: ICAO HEX Code, not Callsign
« Reply #35 on: May 23, 2025, 05:41:47 pm »
Yeah, that looks like Timothy and I've had a gander at his recent tracks as well.

PAW good and ADSB good.

All that is very well but it doesn't tell us why he (and me) are seeing lots of HEX codes instead of registrations.

I'm not too bothered about it but it is definitely a 'thing' and it seems to have got more prevalent with the FX versus the Pi versions.

On the other hand, my ATOM station is a Pi and it is seeing plenty of HEX codes (including the Spit the other day). Could the common denominator be iGrid/Internet, instead of FX?

I will try and note, next time I see a bunch of HEX codes, if I have a green iGrid blob or not. If none appear when iGrid has disconnected (due to poor 4G) then it might provide a clue........possibly, maybe.

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #36 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.

PaulSS

Re: ICAO HEX Code, not Callsign
« Reply #37 on: May 23, 2025, 11:56:08 pm »
Without wishing to sound patronising, are you dragging the lollipop (at the bottom of the screen) from left to right to drive the timeline?

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #38 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!

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #39 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?

grahambaker

Re: ICAO HEX Code, not Callsign
« Reply #40 on: May 25, 2025, 08:08:20 pm »
Why the asterisk at the start of the hex code?

Have you tried without it?

Timothy

Re: ICAO HEX Code, not Callsign
« Reply #41 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?

PaulSS

Re: ICAO HEX Code, not Callsign
« Reply #42 on: June 04, 2025, 06:16:56 pm »
Lots of HEX codes floating around today. The ones over Parham are likely to be Flarm, whereas the aircraft one the sea is probably SkyEcho.