Yet again - ghost target 100 feet above

[Steve6443]

Up until about 3 months ago, my Pilotaware was running fine, however just recently (since updating to the latest version from May) it has started to show a ghost target 100 feet above me, no direction. Occasionally it will show as level. It doesn't show an ID, I'm pretty sure it's a ghost but what can have changed since the update?

My settings are correct, anyone got any hints what to test next? I've not moved anything around, It's all fitted as previously..... Cheers!

[Admin]

Hi Steve
I think I know the issue, I will have an enhancement in next release
Would you like to test out an engineering release ?
It would be good to get feedback

Thx
Lee

[rogerabc]

Hi Lee,

I would like to receive an engineering release please as my PAW is currently unusable due to ghost warnings.

Thanks,


Roger

[Admin]

I would like to receive an engineering release please as my PAW is currently unusable due to ghost warnings.

Roger,

This should not make it unusable, if it is unusable, then there is another problem.

As a minimum you should be able to operate without Mode-C support, which will continue to provide
Mode-S, ADS-B, P3I, OGN-R.

Please confirm the issue you are seeing is only Mode-C returns for false-positives.
(BTW, is your transponder Mode-C or Mode-S, can you provide a model reference ?)

I can provide a link to an engineering release, but please ensure you are using a second MicroSD card so that you have a backup

I think the root problem here, is that ModeC is only accurate to within 100ft, with no indication of rounding (up, down or to nearest)

Thx
Lee

[rogerabc]

You are entirely correct Lee.
I will use a different card.

[rogerabc]

It’s an old  Bendix mode c with ameriking encoder.

[Admin]

It’s an old  Bendix mode c with ameriking encoder.

Hi Roger
I dug out the specs here :-
http://contrails.free.fr/temp/9.1.23.pdf
Quite surprised to read on page 14 (of the PDF) that the correspondence error is +/-125ft
I wonder if that is why we are seeing this issue with your setup ?

IIRC you provided me with a track file, and what I could see is that it was being reported just outside the 100ft limits for each warning.

Thx
Lee

[Steve6443]

Hi Lee,

my transponder is a GTX330ES, non ADS-B out and if you have a new release to test, please let me know, I'd love to trial it.

Thanks.

[malcflyer]

I seem to be getting the same "ghost" reports. These indicated C-045F and C031E (twice) whilst flying along south coast. All three were +100ft.  This was my first proper flight with SkyDemon and other contacts were displaying correctly. There were still, of course, visual contacts which did not display but they probably had no transponder (or were just careless). I have screen prints of the "contacts" if this is any help?

[Nexus6]

I have been having the exact same issue since upgrading to the latest software. My transponder is a Mode S Garmin GTX 330.

[Admin]

Hi all
Can I get track files in order to verify ?
Thx
Lee

[Welsh Pilot]

I'm also getting ghost reports 100 feet above and below since upgrading the firmware. Becker Mode S and Ameriking encoder, non ADS-B out.

[Admin]

Ok, tracks please, and does this happen in a climb/descend by any chance ?
Interesting the same encoder which has +/-125ft accuracy
Thx
Lee

[Steve6443]

Hi all
Can I get track files in order to verify ?
Thx
Lee

Wilco.... hope to get them this evening and will send to you....

[rogerabc]

I was wrong on the brand, Garmin GTX 320.
But right on encoder,  Ameriking AK-350.