On Saturday, March 10, 2018 at 9:29:57 PM UTC-5, wrote:
Greetings,

Installed my new Trig and TN72 and today when I powered up both my Flarm and the Trig, the Flarmview reported my own ADSB Out signal as a ADSB target.

PowerFlarm Core - 6.42 Firmware
Flarmview - 2.39 Firmware

Flarm Config ID shows identical to ADSB Out ID

FlarmView is showing my target as my contest number so it's correctly matching my ADSB Out ID to my contest number based on current FlarmNet.

Flarmview shows correct Flarm ID when Flarm - Configuration is selected.


Am I missing something? Is this a PowerFlarm issue or a FlarmView issue? I was expecting that the Flarm/FlarmView would ignore my own signal based on the ID.

All of this was stationary on the ground testing, but I doubt that it would be different if I was flying.

Thanks for any help or advice.

Mark

Hi Mark - here are some settings you may wish to look at in your flarmcfg.txt file:

################################################## ######################
# transponder and PCAS configuration
################################################## ######################

# do Mode C signal processing, ie, PCAS mode (0=no, 1=yes)
$PFLAC,S,MODEC,1

# own Mode C signal filtering (to eliminate your own xpdr)
# 0=aggressive (use w/ Mode C Xpdr), 1=normal (no Xpdr or Mode S)
# normal sometimes results in false PCAS alerts about every 10 min
$PFLAC,S,OWNMODEC,1

# PCAS antenna gain (30=default, higher makes PCAS targets closer)
$PFLAC,S,PCASCALIBRATION,30

# transponder type (0=None, 1=Mode C, 2=Mode S)
$PFLAC,S,XPDR,2

# use Mode S barometric altitude for PCAS height calc (0=no, 1=yes)
$PFLAC,S,MODESALT,1

Cheers
Dan