PowerFlarm still picking up Transponder

[Rob Cluxton[_2_]]

After previous advice on here, I reconfigured my PowerFlarm via the .configtxt file. I am now seeing ADS-B traffic (definitely need to lower the altitude and distance parameters) but when I run my own transponder in ALT mode it’s still picking up traffic at 12 o’clock, .6 miles and around my altitude.

Anything else to recommend I try?

Thanks,
Rob
“4D”

[[email protected]]

Shot in the dark here, are you sure the code in your transponder matches what's in your Flarm config / which should be the one in the FAA database for your glider.

[Rob Cluxton[_2_]]

I’m sure the code/config file matches the Flarm ICAO code. Guess I have to try and find what the FAA has.

[Dan Daly[_2_]]

On Sunday, May 24, 2020 at 10:14:26 AM UTC-4, Rob Cluxton wrote:
> I’m sure the code/config file matches the Flarm ICAO code. Guess I have to try and find what the FAA has.

It would help if you post your flarmcfg.txt file here.

[[email protected]]

What brand of transponder are you using? Trig? If so, you’ll want to check what code is in the transponder. Not the 1202 VFR glider code, but your assigned aircraft code.

Go to the following link and start on page 29. Hold down the Fn button when you turn on your transponder and it will go into setup mode. Use the ENT button to move forward through the options. #2 should be the ICAO code and this should match what the FAA has assigned you and what is in your Flarm config file.


https://www.trig-avionics.com/library/00560-00%20AQ%20TT21TT22%20Installation%20Manual.pdf

[George Haeh]

If your transponder is Mode C, none of this will work.

1. The transponder, if Mode S, has to be configured to your ICAO code. Note that this is a specific process for your particular transponder that is set out in your transponder installation manual by the transponder manufacturer.

2. the PowerFLARM configuration file has to have the same ICAO code.

From Configuration tool:

" empty to use the device specific radio id..."

[Rob Cluxton[_2_]]

It’s a Garrecht VT-01

[Rob Cluxton[_2_]]

On Sunday, May 24, 2020 at 10:36:46 AM UTC-4, Dan Daly wrote:
> On Sunday, May 24, 2020 at 10:14:26 AM UTC-4, Rob Cluxton wrote:
> > I’m sure the code/config file matches the Flarm ICAO code. Guess I have to try and find what the FAA has.
>
> It would help if you post your flarmcfg.txt file here.


Here it is:

################################################## ############################
# Cerated by LXNAV PowerFlarmConfig version 1.2.5
#
# This configuration file must be text only and reside in the top directory
# of the USB stick, SD card or FLARM Tool.
# This configuration file must be named FLARMCFG.TXT
# If you wish to change the settings, you can use PowerFlarmTool
# from: https://gliding.lxnav.com/lxdownloads/software/
################################################## ############################

# Basic Settings
$PFLAC,S,ID,AC2D0E
$PFLAC,S,NMEAOUT1,1
$PFLAC,S,NMEAOUT2,1
$PFLAC,S,ACFT,1
$PFLAC,S,CFLAGS,0
$PFLAC,S,PRIV,0
$PFLAC,S,NOTRACK,0
$PFLAC,S,THRE,1

# IGC Settings
$PFLAC,S,LOGINT,4
$PFLAC,S,PILOT,undefined
$PFLAC,S,COPIL,undefined
$PFLAC,S,COMPCLASS,undefined
$PFLAC,S,COMPID,undefined
$PFLAC,S,GLIDERID,undefined
$PFLAC,S,GLIDERTYPE,undefined

# Baud rate
$PFLAC,S,BAUD1,2
$PFLAC,S,BAUD2,2

# Range
$PFLAC,S,MODEC,1
$PFLAC,S,OWNMODEC,0
$PFLAC,S,XPDR,2
$PFLAC,S,MODESALT,0
$PFLAC,S,PCASRANGE,7408
$PFLAC,S,PCASVRANGE,610
$PFLAC,S,PCASPFLAU1,0
$PFLAC,S,PCASPFLAU2,0
$PFLAC,S,PCASBEEP,1
$PFLAC,S,PCASCALIBRATION,30
$PFLAC,S,ADSBRANGE,65535
$PFLAC,S,ADSBVRANGE,65535
$PFLAC,S,RANGE,2000
$PFLAC,S,VRANGE,500

# Device Settings
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100
$PFLAC,S,BATTERYTYPE,0
$PFLAC,S,BRIGHTNESS,100
$PFLAC,S,VOL,3

[Richard Pfiffner[_2_]]

On Sunday, May 31, 2020 at 7:06:57 AM UTC-7, Rob Cluxton wrote:
> On Sunday, May 24, 2020 at 10:36:46 AM UTC-4, Dan Daly wrote:
> > On Sunday, May 24, 2020 at 10:14:26 AM UTC-4, Rob Cluxton wrote:
> > > I’m sure the code/config file matches the Flarm ICAO code. Guess I have to try and find what the FAA has.
> >
> > It would help if you post your flarmcfg.txt file here.
>
>
> Here it is:
>
> ################################################## ############################
> # Cerated by LXNAV PowerFlarmConfig version 1.2.5
> #
> # This configuration file must be text only and reside in the top directory
> # of the USB stick, SD card or FLARM Tool.
> # This configuration file must be named FLARMCFG.TXT
> # If you wish to change the settings, you can use PowerFlarmTool
> # from: https://gliding.lxnav.com/lxdownloads/software/
> ################################################## ############################
>
> # Basic Settings
> $PFLAC,S,ID,AC2D0E
> $PFLAC,S,NMEAOUT1,1
> $PFLAC,S,NMEAOUT2,1
> $PFLAC,S,ACFT,1
> $PFLAC,S,CFLAGS,0
> $PFLAC,S,PRIV,0
> $PFLAC,S,NOTRACK,0
> $PFLAC,S,THRE,1
>
> # IGC Settings
> $PFLAC,S,LOGINT,4
> $PFLAC,S,PILOT,undefined
> $PFLAC,S,COPIL,undefined
> $PFLAC,S,COMPCLASS,undefined
> $PFLAC,S,COMPID,undefined
> $PFLAC,S,GLIDERID,undefined
> $PFLAC,S,GLIDERTYPE,undefined
>
> # Baud rate
> $PFLAC,S,BAUD1,2
> $PFLAC,S,BAUD2,2
>
> # Range
> $PFLAC,S,MODEC,1
> $PFLAC,S,OWNMODEC,0
> $PFLAC,S,XPDR,2
> $PFLAC,S,MODESALT,0
> $PFLAC,S,PCASRANGE,7408
> $PFLAC,S,PCASVRANGE,610
> $PFLAC,S,PCASPFLAU1,0
> $PFLAC,S,PCASPFLAU2,0
> $PFLAC,S,PCASBEEP,1
> $PFLAC,S,PCASCALIBRATION,30
> $PFLAC,S,ADSBRANGE,65535
> $PFLAC,S,ADSBVRANGE,65535
> $PFLAC,S,RANGE,2000
> $PFLAC,S,VRANGE,500
>
> # Device Settings
> $PFLAC,S,AUDIOOUT,0
> $PFLAC,S,AUDIOVOLUME,100
> $PFLAC,S,BATTERYTYPE,0
> $PFLAC,S,BRIGHTNESS,100
> $PFLAC,S,VOL,3

Why are you using a LXNAV config file instead of a Powerflarm cfg tool.. They are not the same device, similar but not the same. the LXNAV is for config your PowerMouse, FlarmBat, FlarmMouse. It appears you are missing many config items. Let us start with a very important setting.

#PFLAC,S,DEF Sets Default
$PFLAC,S,DEF

Try turning off the PCAS $PFLAC,S,PCASRANGE,0 and see what happens.

Richard,

[[email protected]]

Just a side note, the VT-01 is not capable of supporting the necessary SIL level for use as ADSB-Out in the USA, at least. Where are you located?

[Jonathan St. Cloud]

On Sunday, May 31, 2020 at 10:22:47 AM UTC-7, wrote:
> Just a side note, the VT-01 is not capable of supporting the necessary SIL level for use as ADSB-Out in the USA, at least. Where are you located?

Didn't they advertise it was ADS-B out capable?

[Tango Whisky]

It is. I have the CAI302 Tx going into the VT-01 Rx, and it works well. There is no SIL capability however.

[[email protected]]

If memory serves me correctly, without SIL 1 or 3, any of the large aircraft out there, and ATC, may simply ignore you. Better than nothing, but don’t you want to be seen by everyone? I’ll defer to Daryl Ramm who has been the resident expert on this stuff.

[Tango Whisky]

That is correct. But my aim was to have a transponder, and connecting the 2 wires didn't cost me anything. But then, you get what you pay for...
Where I fly (Europe/Alpes), Flarm is first priority, transponder second, and ADSB-out doesn't give you much. Airspace is configured such that you don't mix with heavy metal, and if you do, it's under ATC control with mode S.
Most of the time, it's natural separation - heavy metal don't like looking up at mountain tops :-)

[[email protected]]

To the original poster. Look at the following starting on page 35. Did you enter your aircraft ID?

https://www.delta-omega.com/download/garrecht/VT-01Install_E.pdf

[George Haeh]

I don't see the ICAO code set in your config file.

I'm away from home; so, can't compare with my config file.

Perhaps somebody can post a config file that works with their Mode S transponder.

[[email protected]]

It’s there, right at the top. AC2D0E and matches what the FAA shows it should be.

Question is if the VT-01 has that programmed?

[[email protected]]

Did some how to debug experiments on my box.

If you power the flarm up with an empty flash drive plugged in and wait till no blinking for 60 seconds, what does it write on the flash drive?

Aside from a bunch of IGC's, mine wrote a .csv and .txt file.

Each showed the transponder id.

To debug flarm, I sometimes boot with a blank flash except for versions of this flarmcfg.txt to get it to dump the write info into a log.


################################################## ##################################
#Sets Default
#PFLAC,S,DEF

################################################## ######################
#Clears IGC Logs
#PFLAC,S,CLEARLOGS

################################################## ######################
# This allows you to confirm your settings.
$debug_out,fat,scheduler|config|baro|rf|gps|pffsm, all

################################################## ######################
# Writes a diagnostic dump (PFSSSSS.DMP) to the USB stick.
# Existing files with the same file name will be overwritten
# file is ?format binary.
#file,dump

[George Haeh]

My mistake, I was looking for a hex string beginning with C0, Canadian prefix. Just reminded that it's AC in the US – until there's more than 64K registered aircraft in the US, or maybe there's already AB and/or AD.

[Jonathan St. Cloud]

On Sunday, May 31, 2020 at 10:49:59 AM UTC-7, Tango Whisky wrote:
> It is. I have the CAI302 Tx going into the VT-01 Rx, and it works well. There is no SIL capability however.

So what functionality does that give you?

[Rob Cluxton[_2_]]

I used the PowerFlarm config tool v1.2.5 because that is what came up on a search for it. LXnav just seems to be advertising on it?

[Rob Cluxton[_2_]]

Yes, it does. Comes up when I power the unit on.

[Rob Cluxton[_2_]]

I am picking up ADS-B traffic, with or without the transponder set to ON. My PowerFlarm has a mark on the top of the case that has ADS-B marked.

[Rob Cluxton[_2_]]

Thanks. I will try that next, in lieu of better advice.

Rob “4D”

[Richard Pfiffner[_2_]]

On Tuesday, June 2, 2020 at 3:33:57 PM UTC-7, Rob Cluxton wrote:
> Thanks. I will try that next, in lieu of better advice.
>
> Rob “4D”

https://flarm.com/support/tools-software/


Richard
www.craggyaero.com

[Rob Cluxton[_2_]]

Booting it up with an empty USB stick worked! I then cleared the stick, again, and loaded one more time with the config file. All is well...

Thanks,
Rob