91
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by A_Vinning33 on May 20, 2025, 10:52:02 am »I'll begin trying to replicate this issue on FX here.
Recent Posts
92
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by Timothy 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.
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.
93
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by PaulSS on May 19, 2025, 07:30:28 pm »I've seen lots of ghosting when the target has SafeSky on board, in addition to something else (ADSB Out, SkyEcho) but I know that is not the point of this thread and that is usually because they've got the free version of SafeSky and/or haven't bothered to set it up correctly.
The question is why are we seeing so many HEX codes. Is it my imagination or did this problem not exist with the Classic or Rosetta? Is it something to do with the way in which the FX processes the data?
The other thing I am thinking is is this being caused by seeing SkyEcho and/or Flarm in the target aircraft? My basic empirical evidence suggests I often see HEX codes with SkyEcho but I don't know if that is just coincidence or, again, the way the FX processes.
The question is why are we seeing so many HEX codes. Is it my imagination or did this problem not exist with the Classic or Rosetta? Is it something to do with the way in which the FX processes the data?
The other thing I am thinking is is this being caused by seeing SkyEcho and/or Flarm in the target aircraft? My basic empirical evidence suggests I often see HEX codes with SkyEcho but I don't know if that is just coincidence or, again, the way the FX processes.
94
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by buzz53 on May 19, 2025, 07:28:45 pm »Timothy,
Sorry, I know you're techie but I obviously presumed too much PAW specifics. PAW maintains a text based "track" file for each flight containing useful information about, well, your track but also the traffic information sent to your downstream device, and other internal status information. Unfortunatey the format is not public but it's mostly obvious, although some records need a bit of "interpretation". You can download the file from the PAW to your tablet/phone but it sounds like this would need to await your next visit to the aircraft.
Hopefully you have used the PAW web interface on 192.168.1.1? one of the many items is (from memory!) TRACKS, displaying a date and time ordered list of files. Hit "Download" to copy any of them interest to your device. I'm not an Apple user so I'll need to leave you to figure out where they get stored and how to email them to yourself.
One official use of the files is via the flight replay app:
https://playback.pilotaware.com/playback/
Upload the track file and you can then drag the little white circle in the lower part of the display to replay your flight. You will see your own aircraft and also all the traffic that was reported during the flight. Hover or click on the traffic to see it's identity. If you can recall a situation of interest (and your posted screenshots would be examples) it would be interesting to see if the ID displayed corresponds.
Alternatively, and perhaps more interestingly if you're that way inclined, viewing the track file in a text editor will show the detail of what was sent to your device. Admin previously described the $PFLAA messages that convey traffic information, and the differing formats with and without callsign. I expect that this will simply confirm that PAW is at times just omitting the callsign but who knows? There may be some pattern or other clue.
About 5 seconds or so prior to the first $PFLAA message for a particular aircraft you should see a lengthy $PALOG message containing the it's hex code and which appears to convey (not very obviously) the source of the traffic. I assume this message indicates the first receipt of information about that aircraft (and BTW why the 5 second delay in informing the downstream device)? I wonder if this message might reveal anything.
Might be easiest just to send me the file? I'm not saying any of this will help, so don't go out of your way to retrieve it, but sometimes an indirect route leads to useful clues and as you say things have ground to a halt otherwise.
Alan (no connection to PAW, just a mis-spent youth).
PS should just add that I have a PAW Classic, not an FX but I hope and believe that the track logging functionality has not changed.
Sorry, I know you're techie but I obviously presumed too much PAW specifics. PAW maintains a text based "track" file for each flight containing useful information about, well, your track but also the traffic information sent to your downstream device, and other internal status information. Unfortunatey the format is not public but it's mostly obvious, although some records need a bit of "interpretation". You can download the file from the PAW to your tablet/phone but it sounds like this would need to await your next visit to the aircraft.
Hopefully you have used the PAW web interface on 192.168.1.1? one of the many items is (from memory!) TRACKS, displaying a date and time ordered list of files. Hit "Download" to copy any of them interest to your device. I'm not an Apple user so I'll need to leave you to figure out where they get stored and how to email them to yourself.
One official use of the files is via the flight replay app:
https://playback.pilotaware.com/playback/
Upload the track file and you can then drag the little white circle in the lower part of the display to replay your flight. You will see your own aircraft and also all the traffic that was reported during the flight. Hover or click on the traffic to see it's identity. If you can recall a situation of interest (and your posted screenshots would be examples) it would be interesting to see if the ID displayed corresponds.
Alternatively, and perhaps more interestingly if you're that way inclined, viewing the track file in a text editor will show the detail of what was sent to your device. Admin previously described the $PFLAA messages that convey traffic information, and the differing formats with and without callsign. I expect that this will simply confirm that PAW is at times just omitting the callsign but who knows? There may be some pattern or other clue.
About 5 seconds or so prior to the first $PFLAA message for a particular aircraft you should see a lengthy $PALOG message containing the it's hex code and which appears to convey (not very obviously) the source of the traffic. I assume this message indicates the first receipt of information about that aircraft (and BTW why the 5 second delay in informing the downstream device)? I wonder if this message might reveal anything.
Might be easiest just to send me the file? I'm not saying any of this will help, so don't go out of your way to retrieve it, but sometimes an indirect route leads to useful clues and as you say things have ground to a halt otherwise.
Alan (no connection to PAW, just a mis-spent youth).
PS should just add that I have a PAW Classic, not an FX but I hope and believe that the track logging functionality has not changed.
95
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by Timothy 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!
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!
96
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by buzz53 on May 19, 2025, 11:11:09 am »Would it be helpful to download the PAW track file and see what is displayed using the PAW track replay utility, but also have a look with a text editor? If nothing else it will check that the erratic data is indeed being emitted by PAW but you never know what other clues may show up. You can also get some insight into the ultimate source of the data although this needs a bit of imagination as the log format is not documented. The joys of a closed system! Search for the ICAO code obviously. It seems that the source log entry $PAWRT is only written on first contact but you might, for example, see multiple entries if it is flipping between ADSB/PAW as the source perhaps. PM me the file if you like.
Alan
Alan
97
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by PaulSS on May 19, 2025, 09:19:00 am »As already mentioned I, too, see lots of HEX codes without registrations.
There was an explanation on page 1 of why this might be.
I've never had SafeSky anywhere near my aircraft (and won't).
There was an explanation on page 1 of why this might be.
I've never had SafeSky anywhere near my aircraft (and won't).
98
General Discussion / Re: Trig Transponder GPS input from Pilotaware FX
« Last Post by Hap Hazard on May 19, 2025, 08:46:47 am »Thanks guys,
Just ordered up a splitter....
Cheers,
B
Just ordered up a splitter....
Cheers,
B
99
General Discussion / Re: Trig Transponder GPS input from Pilotaware FX
« Last Post by tnowak on May 19, 2025, 08:03:19 am »Steveu,
To avoid confusion, I think some clarification is needed regarding your slightly confusing comments:
"... so a lot of stuff (certified) will screen you out...."
I think you meant to say that airliners and "high end GA", equipped with very fancy and expensive integrated Traffic displays, MAY screen out SIL/SDA=0 ADS-B data.
Most "normal" end GA (our aircraft types), equipped with lower cost ADS-B In receivers, will still see and process SIL/SDA=0 ADS-B data.
Also, our certified Mode S/ES transponders will still interact with aircraft that are equipped with TCAS..
Hope this helps..
To avoid confusion, I think some clarification is needed regarding your slightly confusing comments:
"... so a lot of stuff (certified) will screen you out...."
I think you meant to say that airliners and "high end GA", equipped with very fancy and expensive integrated Traffic displays, MAY screen out SIL/SDA=0 ADS-B data.
Most "normal" end GA (our aircraft types), equipped with lower cost ADS-B In receivers, will still see and process SIL/SDA=0 ADS-B data.
Also, our certified Mode S/ES transponders will still interact with aircraft that are equipped with TCAS..
Hope this helps..
100
Technical Support / Re: ICAO HEX Code, not Callsign
« Last Post by Timothy 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.
Am I the only one seeing this? I feel quite isolated and unsupported.