Power Flarm Problems

[Charlie Flagg]

After addressing other issues with a new ship, I tackled the Power Flarm
early this summer. I read the manual, talked to folks and generated a
configuration file using the online flarm configuration tool on the
flarm.com site. After some hesitance, the configuration loaded and the
Power Flarm and Butterfly worked as I expected. A week later I turned the
system on and the configuration was gone. I have done this now three times
in the past couple of months and the configuration always disappears when I
check it a day or two later. The system consists of an LX9000 powering the
Power Flarm which, in turn, powers the Butterfly. Batteries are fully
charged. Any suggestions as to what is going on?

[Charlie Flagg]

[Dan Marotta]

I know nothing of the Flarm hardware so I ask, does it have an internal
battery or nonvolatile RAM? Does it lose its configuration if you
simply power down the ship and then power it back up?

--
Dan, 5J

[Charlie Flagg]

A dead battery was my first thought but from what I gather from the manual,
there is no backup lithium battery in the flarm.
Charlie, C

[kirk.stant]

Are you leaving a USB thumb drive installed in the PF when you start it up everytime? Is there a "default" config file in the USB drive?

You could post your config file here (minus identifying data, of course); there may be something in it...

Kirk
66

[Dan Daly]

Are you using FLARM version 6.06? If you post the header (minus identifying data) of one of your .igc files (the part above the B records), it will also help sort it out.

Has your FLARM firmware been updated with 365 days? According to manual 3.41, it must be....

It may be a mis-match between FLARM firmware and Butterfly display firmware. Both must be updated to function correctly...

Dan

[K m]

I think Kirk and Dan hit the nail here. Make sure you have the latest version firmware in all of your equipment (And Database if you want to team fly). I once dug up an old thumb drive to download a flight at a contest and the next day nothing worked. Turns out there was an old generic config file on the drive I randomly picked out of my flight kit. I was using the PF for my primary logger at the time so it was a scramble to figure out what happened and fix it on the grid.

[Charlie Flagg]

At 03:27 23 August 2016, K m wrote:
>I think Kirk and Dan hit the nail here. Make sure you have the latest

>versi=

>on firmware in all of your equipment (And Database if you want to team

>fly)=
>.. I once dug up an old thumb drive to download a flight at a contest and
>th=

>e next day nothing worked. Turns out there was an old generic config file

>o=

>n the drive I randomly picked out of my flight kit. I was using the PF
for

>=

>my primary logger at the time so it was a scramble to figure out what

>happe=

>ned and fix it on the grid.
>

Thanks for the suggestions. The PF was definitely updated this spring but
not the Butterfly. I'll check all the system updates this evening and see
what happens.
Charlie, C

[Charlie Flagg]

At 03:27 23 August 2016, K m wrote:

>I think Kirk and Dan hit the nail here. Make sure you have the latest

>versi=

>on firmware in all of your equipment (And Database if you want to team

>fly)=
>.. I once dug up an old thumb drive to download a flight at a contest and
>th=

>e next day nothing worked. Turns out there was an old generic config file

>o=

>n the drive I randomly picked out of my flight kit. I was using the PF
for

>=

>my primary logger at the time so it was a scramble to figure out what

>happe=

>ned and fix it on the grid.
>

[Dan Daly]

>
> Thanks for the suggestions. The PF was definitely updated this spring but
> not the Butterfly. I'll check all the system updates this evening and see
> what happens.
> Charlie, C

I do the club FLARMs - 5 so far, and my own. I had one setup that wouldn't work until I updated the associated Butterfly twice (second time with correct flarmnet file). Even if you don't like flarmnet, once one is in your Butterfly, you have to keep it current to the newest specification (FLARM and Butterfly talk when a new version comes out. 2017 will be a big FLARM update year). I've had difficulty with flarmnet files if I download them with my Macbook, and now just use the club PC.

If you select notrack in your flarmcfg.txt file, you won't be tracked by OGN receivers. From the latest flarm spec:

3.1.8 NOTRACK
Description:
Instructs third party receiving stations that (regardless of stealth mode setting) the received ID and position data must neither be stored nor made accessible in any time dimension (real-time, delayed, or archived) for any purpose. It is recommended NOT to enable this option! If enabled, it will impair logging service functionality and make Search and Rescue (SAR) impossible.
1 is notrack...

To find the specification, google FTD-14-FLARM-Configuration-Specification-1.02 .

Updating the flarm is a lot better since version 6; you just put the flarm firmware, the butterfly firmware, and the new flarmnet file at the highest level of a USB (CORE) or SD card (Portable). Turn on the flarm, and it updates each in the correct order, and leaves a file saying what it has done. It makes troubleshooting a lot easier. Once you've updated, move the firmware files to a folder on the drive, and the flarm won't see them there (but they are there if you ever need them).

[Paul Remde]

Hi Charlie,

What is your source of information that tells you that the configuration
data has been lost?

Best Regards,

Paul Remde
Cumulus Soaring, Inc.

"Charlie Flagg" wrote in message news:M%Duz.759789$Sx3.7...@fx04.fr7...

[Charlie Flagg]

Paul,
I have gotten the PF to work briefly in the past but no longer. The
indication that the configuration was lost has been that neither the LX9000
nor the Butterfly show the presence of the PF data. The Butterfly shows
two red squares while the LX9000 shows the correct PF serial number and
firmware version, 6.06, but no nearby aircraft tracks.

On unloading the configuration file, the PF creates a CVS and a TXT file.
Both of those look reasonable with no obvious error flags. The Butterfly
has firmware version 3.3 and took the updated flarmnet file, ...4978.bfn.
But still no flarm activity from either the LX9000 or the Butterfly.

Thanks, Charlie

[Dan Daly]

From the manual:
A red GPS-Indicator means that the connected collision warning unit does not have sufficient GPS reception to determine the current position.

Also, current version according to the manufacturer's webpage ( http://www.air-avionics.com/air/index.php/en/customer-support/butterfly-displays ) is 3.4. According to the changelog, the format of the flarmnet file was changed.

[kirk.stant]

On Wednesday, August 24, 2016 at 8:15:05 AM UTC-5, Charlie Flagg wrote:
The Butterfly shows
> two red squares while the LX9000 shows the correct PF serial number and
> firmware version, 6.06, but no nearby aircraft tracks.
>

Perhaps the GPS antenna is bad? Easy enough to try another one. With no GPS you will get the two red squares.

Kirk
66

[Charlie Flagg]

Hello Kirk, Dan and Paul,
Thanks for the suggestions. Updated the BF to 3.4 and got the same
result. Perhaps the GPS has died as Kirk suggested although that would be
rather unlikely. I'll check it out.
Charlie

[Dan Daly]

Easy way to check - borrow PF GPS you know is working and try it in your installation. They recommend GPS pucks, since they are semi-active, to be one foot apart (or as far apart as your installation permits up to a foot).

Alternately, you can see the inside of the GPS here https://sites.google.com/site/threeuniform/powerflarm/powerflarm-antennas with instructions on how to shorten it if you need to; using it, you could confirm whether the coax is soldered to the printed circuit board correctly. Same site, how to shorten the PF antennae - coiled coax can cause problems. I shorten the PF and GPS antennae for installations to make the whole thing neater. Bravo Zulu to 3U for a great site!

You say you updated the Butterfly - you MUST also update the flarmnet file, or it won't work - the old format file is not compatible, and it is there until you replace it.

Dan
2D

[K m]

Charlie,
You have not mentioned anything about the LED status lights on the PF Core. What do you see when the unit is on? From the Manual

GREEN: Core operates normally

AMBER
during
up to 20s after power ON: start-
up sequence

Permanent RED: Error condition, no operation possible (e.g. no GPS
receptio
n, low voltage)

Permanent
AMBER
: Warning cond
ition, operation possible (e.g.
obstacle
database out of date)

RED/GREEN flashing: on
-going data upload/download with USB memory
stick

OFF: no power

Also from the manual,

Indications while reading FLARMCFG.TXT files:

One long GREEN f
lash: USB stick detected

One short GREEN flash for each command executed successfully

One short RED flash for each command causing an error (verify
FLARMCFG.TXT in that case)

If this doesn't offer help try plugging in another GPS antenna.

[Charlie Flagg]

Hello Dan, Paul, Kirk and KM,
Following up on the GPS issue I found a pinch in the GPS cable. Should
have spotted that early on but in my defense, all the problems coincided
with attempts to update all the firmware. And I have 20+ year old GPS
units that are fine. Well, I know a lot more about these units now than
before thanks to you.
Thanks again, Charlie

At 14:33 25 August 2016, K m wrote:
>On Thursday, August 25, 2016 at 6:00:06 AM UTC-6, Charlie Flagg wrote:
>> Hello Kirk, Dan and Paul,
>> Thanks for the suggestions. Updated the BF to 3.4 and got the same
>> result. Perhaps the GPS has died as Kirk suggested although that would

>b=

>e
>> rather unlikely. I'll check it out.
>> Charlie

>>=20

>> At 23:06 24 August 2016, kirk.stant wrote:
>> >On Wednesday, August 24, 2016 at 8:15:05 AM UTC-5, Charlie Flagg
wrote:
>> >The Butterfly shows
>> >> two red squares while the LX9000 shows the correct PF serial number

>an=

>d
>> >> firmware version, 6.06, but no nearby aircraft tracks.

>> >>=20

>> >
>> >Perhaps the GPS antenna is bad? Easy enough to try another one. With
no
>> >GPS you will get the two red squares.
>> >
>> >Kirk
>> >66
>> >
>
>Charlie,
>You have not mentioned anything about the LED status lights on the PF

>Core.=

> What do you see when the unit is on? From the Manual
>
>GREEN: Core operates normally

>=EF=82=A1
>AMBER
> during=20

>up to 20s after power ON: start-
>up sequence

>=EF=82=A1

>Permanent RED: Error condition, no operation possible (e.g. no

>GPS=
> =20
>receptio
>n, low voltage)
>=EF=82=A1
>Permanent=20

>AMBER
>: Warning cond
>ition, operation possible (e.g.

> obstacle=20
>database out of date)
>=EF=82=A1
>RED/GREEN flashing: on
>-going data upload/download with USB memory =20
>stick
>=EF=82=A1

>OFF: no power
>
>Also from the manual,
>
>Indications while reading FLARMCFG.TXT files:

>=EF=82=A1
>One long GREEN f
>lash: USB stick detected=20
>=EF=82=A1

>One short GREEN flash for each command executed successfully

>=EF=82=A1

>One short RED flash for each command causing an error

>(=
>verify =20

[Dan Daly]

Fix the cable by shortening it using 3U's instructions.

[Richard]

I have seen several PowerFlarm Cfg files that have this command that is supposed to set the defaults in the PowerFlarm.

$PFLAC,DEFAULTS

This command is not correct and will not set defaults so if at one time you have set the stealth on and then used a different config file that did not have any stealth commands or and other commands that you want to change the unit would still have the old settings.

The correct Command to reset the defaults is $PFLAC,DEF

Richard
www.craggyaero.com

[Richard]

Sorry it should be $PFLAC,S,DEF

Richard
www.craggyaero.com

[Oscar-Hotel-Mike]

The FLARM default reset configuration file can be automatically created at https://flarm.com/support/tools-software/flarm-configuration-tool/ by clicking on the "Factory default" button. It will email you a FLARMCFG.TXT file that contains the text shown below with the key command string (like Richard said above). Save the file to the root of a USB memory stick, insert it into the FLARM and power it up. Of course, then you will need to manually configure the FLARM for your ship.

##############################################################################
# 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 revisit the online
# configuration tool at any time: http://www.flarm.com/
##############################################################################
$PFLAC,S,DEF