Software upgrade and ghosting

[marioair]

I’ve upgraded to latest software so I can take advantage of Igrid.
On the first flight yesterday I was getting regular ghosting.
Do the upgrades mess up the hex code?
Can some look at the log file if I send to see what was going on?

[Ian Melville]

Yes, though the updates are not supposed to, they can mess up the hex code. I would check that first.

Has happened a couple of times to me and is more likely if the pervious version is quite old.

[marioair]

I’ve check the logs and hex code is fine.
How can I send the log it’s 7MB.

[Ian Melville]

Host it somewhere like dropbox and send a link to support.

[Admin]

Hi Marioair
Can you explain the exact symptom ?
Bearingless or gps position ghost
Thx
Lee

[marioair]

Here's the full track file
https://drive.google.com/file/d/1mp9Z8d6Vy_OSjAl82E22nl0PMFmGeGRB/view?usp=sharing

Varios ghost report at follow times, for example.
https://aircrew.co.uk/playback/b2c97783

Fri Aug 26 2022 14:18:50
Fri Aug 26 2022 14:22:52
Fri Aug 26 2022 14:29:02
Fri Aug 26 2022 14:42:32
and so on

[Admin]

Hi Marioair

you have an aircraft with HexID 393F76 following very closely

Are you emitting any other types other than PilotAware ?
are you using safesky ?

Thx
Lee

[marioair]

Is their a reverse lookup to get the call sign from that hex?

[Admin]

There is no registration I can find of that code.
Are you using any other emitters / trackers ?

Thx
Lee

[marioair]

Maybe my pesky passenger. Told me he had just installed SafeSky. I’ll ask what callsign he had setup.
Haven’t looked at SafeSky manuals. I assume if it’s sakeSky then the PAW was picking it up via rebroadcast.  Does SS default to a code on install / should it be emitting / should PAW be re-emitting a code that doesn’t exist?

[Admin]

Maybe my pesky passenger

Interesting, I see you also posted on FF
Maybe worth reporting

Btw, you will receive those reports via multipath - ATOM, SkyGRID and iGRID
Another checklist item to add
- All passengers please disable cellular devices using SafeSky

Thx
Lee

[marioair]

I need to check if it was indeed a hex being produced by SafeSky. Will let you know.

But to the related question - if the hex doesn’t resolve to a call sign is that “normal”?

[steveu]

But to the related question - if the hex doesn’t resolve to a call sign is that “normal”?

Hex codes are issued for FLARM devices and they may not be in look up tables.

For collision avoidance you aren't too worried about the exact type of aircraft, just not hitting them when you get a very close proximity alert...

[marioair]

Yeah. But (I need to confirm with my friend) but he uses his SakeSky in a PA28. The code @Lee as mentioned is NOT his code. So stuck as to is this a SafeSky issue or PaW issue.
How do you check in SS what code is being transmitted?

[steveu]

Yeah. But (I need to confirm with my friend) but he uses his SakeSky in a PA28. The code @Lee as mentioned is NOT his code. So stuck as to is this a SafeSky issue or PaW issue.
How do you check in SS what code is being transmitted?

Ask SafeSky:

https://forum.safesky.app/t/transponder/729

Bottom of that thread:

For information, there is also another mean of filling your transponder ID when you don’t know it: simply toggle ON that you have a transponder, and leave the transponder code text field empty. When in flight, SafeSky will auto-detect that a ‘ghost’ plane is following you (since you will be seeing yourself from ADS-B as well). You will then get prompted with a question: « is this you? ». If so, your transponder code will be automatically filled and you won’t have a double echo of yourself.

Fly Safe,

Tristan

Tristan is one of their main men...