November 12th 16, 10:06 PM
For the Powerflarm technical gurus in the community:
This is an update of a problem from earlier in the year regarding very frequent PCAS nuisance alerts on my PF display which I am still trying to resolve (described above). After a trial and error process I've narrowed the problem down to an interaction between my Trig xpdr and the PF Core. The PF Core installation manual has the following text:
"To ensure best alert quality, PowerFLARM Core does not use ADS-B data to
compute alerts for glider targets. Instead, it will exclusively rely on the target's much more precise FLARM data. This requires that all gliders which are equipped with FLARM and ADS-B transponders correctly configure their ADS-B out emitter category to glider."
I just ran my ADSB compliance report to check the system, and despite that fact that the Trig software is correctly set to Glider the compliance report states that the emitter category that is transmitted is for Parachutist/Skydiver.
So, the focused question I have is whether anyone knows if this emitter status is used by PF in any manner that could be related to the nuisance alerts? I'm working with the manufacturer to get the software glitch fixed, but it would be nice to know if this emitter category mismatch is a material contributor to the problem I'm experiencing.
This is an update of a problem from earlier in the year regarding very frequent PCAS nuisance alerts on my PF display which I am still trying to resolve (described above). After a trial and error process I've narrowed the problem down to an interaction between my Trig xpdr and the PF Core. The PF Core installation manual has the following text:
"To ensure best alert quality, PowerFLARM Core does not use ADS-B data to
compute alerts for glider targets. Instead, it will exclusively rely on the target's much more precise FLARM data. This requires that all gliders which are equipped with FLARM and ADS-B transponders correctly configure their ADS-B out emitter category to glider."
I just ran my ADSB compliance report to check the system, and despite that fact that the Trig software is correctly set to Glider the compliance report states that the emitter category that is transmitted is for Parachutist/Skydiver.
So, the focused question I have is whether anyone knows if this emitter status is used by PF in any manner that could be related to the nuisance alerts? I'm working with the manufacturer to get the software glitch fixed, but it would be nice to know if this emitter category mismatch is a material contributor to the problem I'm experiencing.