FLARM Installations instructions screwed up

I am installing a couple of new FLARM devices for our club aircraft.

In order to generate a FLARM-CFG.TXT file, in the manual it clearly states to use the online configurator at:

http://flarm.com/powerflarm/configurator

But this clearly does not work. There are no additional instructions in the manual for alternatives to get a FLARM-CFG.TXT file.

Does anyone have a workaround?



Mark Lenox

http://www.air-avionics.com/air/inde...e-configurator

Sure, though the first thing I notice is: there shouldn't be a hyphen between flarm & cfg. The config file is a simple text file, one of the most basic ways you can give instructions to a computer. The tool you refer to is just a more user friendly way to do it, so open your text editor and create one yourself. Ensure it's saved with the same Flarmcfg.txt file name. I'll post a template for you to use below: Anything that starts with a # is commented out, in other words it will be ignored by Flarm. Anything that starts with an $ is an actual instruction.

So just to be clear:
1). Copy the text below, from the line of ########'s all the way down to '#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa'
2). Paste it into a text file using word pad, textedit or any other text editor of your choice
3). Make the required changes for the glider info and config settings you desire
4). Save the file as Flarmcfg.txt It's not case sensitive.
5). Move that file to your USB stick of choice, taking care to ensure it's of the size (=32Gb) and format (FAT) PowerFlarm requires.
6). Follow the normal update instructions.

CJ

################################################## ######################
#
# Template PowerFLARM configuration file for you to customize...
#
# Each time PowerFLARM is powered on, it looks for the file FLARMcfg.TXT
# in the top directory of the micro-SD card (portable) or USB stick (brick)..
# PowerFLARM does NOT look at this file if the memory card/stick is
# inserted after the PowerFLARM has been powered on.
#
# FLARMcfg.TXT contains a series of commands that configure the
# PowerFLARM. These commands are in the same NMEA data format as used
# to control the FLARM over the NMEA serial data ports (lines starting
# with a dollar sign "$"). Lines starting with # are comments.
#
# Configuration settings from these commands are saved by PowerFLARM
# (except for diagnostic commands). The next time PowerFLARM is powered
# on without the memory stick/card, the settings are still in effect.
#
# Prepare your own version of FLARMcfg.TXT by editing this file
# (following the instructions below), and copy it to your memory
# device (SD card for portable, USB stick for brick). Make SURE
# it is named FLARMCFG.TXT in the top directory.
#
# After preparing your memory device, configure your PowerFLARM:
# (1) With power OFF, insert the memory device into PowerFLARM.
# (2) Turn on the power. PowerFLARM will read FLARMcfg.TXT and
# save your settings.
# (2a) Brick will blink a green LED once for every command
# processed - when it stops blinking or alternating colors,
# remove the USB stick.
# (2b) Portable will show "configuration read from FLARMCFG.TXT"
# on the screen.
# Note: Portable PowerFLARM can also be configured through its user
# interface; Brick REQUIRES configuration via USB stick .
#
# When you load a new software version into PowerFLARM, all
# configuration settings are reset to factory default. Copy your
# FLARMcfg.TXT file and the new software version to your memory device.
# Turn off PowerFLARM, insert memory stick, then turn on PowerFLARM.
# Brick will load new software - give it a few minutes !
# Portable loads new software after you click MenuInfoUpdate.
# As soon as the newly loaded software version starts, it reads your
# FLARMcfg.TXT file and saves your settings as above.

# Set aircraft type to glider (glider is aircraft type 1).
# Replace "1" below with "2" for towplane, or "8" for powerplane.
$pflac,s,acft,1

# Set what kind of transponder you have installed:
# 0 ... no XPDR (default)
# 1 ... Mode C
# 2 ... Mode S
$pflac,s,xpdr,2

# For a Mode S transponder, you MUST set the ICAO code of the
# aircraft (which is also programmed into your transponder).
# Replace FFFFFF below with your aircraft's HEXADECIMAL code.
#
# The ICAO code for N-number registered aircraft is available
# on the FAA web site. Look up your N-number at
# http://registry.faa.gov/aircraftinquiry
# Find your aircraft's "Mode S code".
# Unfortunately, FAA gives it in "Octal" notation.
# Since the late 1970's nobody in the world uses Octal. Except FAA.
# So, we didn't program Octal input support.
# So, you need to convert the FAA's foolish Octal into hex:
# - In LibreOffice, use the conversion function =OCT2HEX(0751243)
# - In Microsoft Excel, Tools AddIns enable Analysis Toolpak,
# and then use =OCT2HEX as in LibreOffice (its always harder
# with Microsoft - "Where do you want to waste time today ?").
$pflac,s,id,AB7DB2

# Set vertical ADS-B range in meters.
# For gliders, a vertical range of +-1000m is recommended
$pflac,s,adsbvrange,1000

# For brick, turn on output data on RJ45 serial port (both GPS and FLARM).
# Needed if you want this data !
# The 6 indicates to use protocol 6 with Mode C and Mode S traffic
# Ignored on portable.
$pflac,s,nmeaout,61

# For brick, turn on output data on DB9 serial port (both GPS and FLARM).
# Needed if you want this data !
# The 6 indicates to use protocol 6 with Mode C and Mode S traffic
# Ignored on portable.
$pflac,s,nmeaout2,61


# Other data

$PFLAC,S,PILOT,Joe Bloggs

$PFLAC,S,GLIDERID,N999PF

$PFLAC,S,COMPID,F1

$PFLAC,S,GLIDERTYPE,Discus B

$PFLAC,S,COMPCLASS,FAI-15m


# Write a debug log file to micro-SD card during flight.
# Brick ignores this if you remove USB stick (you must remove USB stick
# for flight)
$debug_out,fat,scheduler|config|baro|rf|gps|pffsm, all

# Task Declaration
#$PFLAC,S,NEWTASK,5MAY14
#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa
#$PFLAC,S,ADDWP,4042167N,07811550W,TyroneNo
#$PFLAC,S,ADDWP,4113000N,07651300W,NorthEnd
#$PFLAC,S,ADDWP,4034200N,07818083W,AltoonaP
#$PFLAC,S,ADDWP,4113350N,07658600W,Williams
#$PFLAC,S,ADDWP,4042167N,07811550W,TyroneNo
#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa

Very helpful, thanks. I wish the PF documentation was as good.


Mark

Quick additional question:

If all I want to do is make a declaration, do I still need all the other, preceding, commands?

I'd suggest no, they should stay the same unless updated by a more recent command from a flarmcfg.txt file. I'd include the declaration data (pilot, glider, etc) anytime you load a task though; just to be sure to be sure.

My personal method when creating a task declaration in my Flarm is to take a pre-filled flarmcfg.txt template I keep on my USB stick and then just edit the task data as required. As you say, it's unnecessary to reload the other data this way but at a cost of 15 seconds I'm fine with it.

If you'd like to take a more visual, user friendly path, try the free tool at http://www.segelflug-software.de/flarmcfg/index.php

It has waypoint data for 16 countries (though not the USA unfortunately). It sounds like SeeYou should create a 'export task as flarmcfg.txt file' option. Easy as pie to program.

CJ

One small note. The FAA registry now gives the Mode S code in both Hex and Octal. The conversion information is no longer needed.



Mark

On Friday, March 13, 2015 at 10:29:08 PM UTC-4, wrote:
Sure, though the first thing I notice is: there shouldn't be a hyphen between flarm & cfg. The config file is a simple text file, one of the most basic ways you can give instructions to a computer. The tool you refer to is just a more user friendly way to do it, so open your text editor and create one yourself. Ensure it's saved with the same Flarmcfg.txt file name. I'll post a template for you to use below: Anything that starts with a # is commented out, in other words it will be ignored by Flarm. Anything that starts with an $ is an actual instruction.

So just to be clear:
1). Copy the text below, from the line of ########'s all the way down to '#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa'
2). Paste it into a text file using word pad, textedit or any other text editor of your choice
3). Make the required changes for the glider info and config settings you desire
4). Save the file as Flarmcfg.txt It's not case sensitive.
5). Move that file to your USB stick of choice, taking care to ensure it's of the size (=32Gb) and format (FAT) PowerFlarm requires.
6). Follow the normal update instructions.

CJ

################################################## ######################
#
# Template PowerFLARM configuration file for you to customize...
#
# Each time PowerFLARM is powered on, it looks for the file FLARMcfg.TXT
# in the top directory of the micro-SD card (portable) or USB stick (brick).
# PowerFLARM does NOT look at this file if the memory card/stick is
# inserted after the PowerFLARM has been powered on.
#
# FLARMcfg.TXT contains a series of commands that configure the
# PowerFLARM. These commands are in the same NMEA data format as used
# to control the FLARM over the NMEA serial data ports (lines starting
# with a dollar sign "$"). Lines starting with # are comments.
#
# Configuration settings from these commands are saved by PowerFLARM
# (except for diagnostic commands). The next time PowerFLARM is powered
# on without the memory stick/card, the settings are still in effect.
#
# Prepare your own version of FLARMcfg.TXT by editing this file
# (following the instructions below), and copy it to your memory
# device (SD card for portable, USB stick for brick). Make SURE
# it is named FLARMCFG.TXT in the top directory.
#
# After preparing your memory device, configure your PowerFLARM:
# (1) With power OFF, insert the memory device into PowerFLARM.
# (2) Turn on the power. PowerFLARM will read FLARMcfg.TXT and
# save your settings.
# (2a) Brick will blink a green LED once for every command
# processed - when it stops blinking or alternating colors,
# remove the USB stick.
# (2b) Portable will show "configuration read from FLARMCFG.TXT"
# on the screen.
# Note: Portable PowerFLARM can also be configured through its user
# interface; Brick REQUIRES configuration via USB stick .
#
# When you load a new software version into PowerFLARM, all
# configuration settings are reset to factory default. Copy your
# FLARMcfg.TXT file and the new software version to your memory device.
# Turn off PowerFLARM, insert memory stick, then turn on PowerFLARM.
# Brick will load new software - give it a few minutes !
# Portable loads new software after you click MenuInfoUpdate.
# As soon as the newly loaded software version starts, it reads your
# FLARMcfg.TXT file and saves your settings as above.

# Set aircraft type to glider (glider is aircraft type 1).
# Replace "1" below with "2" for towplane, or "8" for powerplane.
$pflac,s,acft,1

# Set what kind of transponder you have installed:
# 0 ... no XPDR (default)
# 1 ... Mode C
# 2 ... Mode S
$pflac,s,xpdr,2

# For a Mode S transponder, you MUST set the ICAO code of the
# aircraft (which is also programmed into your transponder).
# Replace FFFFFF below with your aircraft's HEXADECIMAL code.
#
# The ICAO code for N-number registered aircraft is available
# on the FAA web site. Look up your N-number at
# http://registry.faa.gov/aircraftinquiry
# Find your aircraft's "Mode S code".
# Unfortunately, FAA gives it in "Octal" notation.
# Since the late 1970's nobody in the world uses Octal. Except FAA.
# So, we didn't program Octal input support.
# So, you need to convert the FAA's foolish Octal into hex:
# - In LibreOffice, use the conversion function =OCT2HEX(0751243)
# - In Microsoft Excel, Tools AddIns enable Analysis Toolpak,
# and then use =OCT2HEX as in LibreOffice (its always harder
# with Microsoft - "Where do you want to waste time today ?").
$pflac,s,id,AB7DB2

# Set vertical ADS-B range in meters.
# For gliders, a vertical range of +-1000m is recommended
$pflac,s,adsbvrange,1000

# For brick, turn on output data on RJ45 serial port (both GPS and FLARM)..
# Needed if you want this data !
# The 6 indicates to use protocol 6 with Mode C and Mode S traffic
# Ignored on portable.
$pflac,s,nmeaout,61

# For brick, turn on output data on DB9 serial port (both GPS and FLARM).
# Needed if you want this data !
# The 6 indicates to use protocol 6 with Mode C and Mode S traffic
# Ignored on portable.
$pflac,s,nmeaout2,61


# Other data

$PFLAC,S,PILOT,Joe Bloggs

$PFLAC,S,GLIDERID,N999PF

$PFLAC,S,COMPID,F1

$PFLAC,S,GLIDERTYPE,Discus B

$PFLAC,S,COMPCLASS,FAI-15m


# Write a debug log file to micro-SD card during flight.
# Brick ignores this if you remove USB stick (you must remove USB stick
# for flight)
$debug_out,fat,scheduler|config|baro|rf|gps|pffsm, all

# Task Declaration
#$PFLAC,S,NEWTASK,5MAY14
#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa
#$PFLAC,S,ADDWP,4042167N,07811550W,TyroneNo
#$PFLAC,S,ADDWP,4113000N,07651300W,NorthEnd
#$PFLAC,S,ADDWP,4034200N,07818083W,AltoonaP
#$PFLAC,S,ADDWP,4113350N,07658600W,Williams
#$PFLAC,S,ADDWP,4042167N,07811550W,TyroneNo
#$PFLAC,S,ADDWP,4053033N,07754450W,RidgeSoa

Hmmm, those comments sure look familiar ;-)

On Friday, March 13, 2015 at 11:54:05 PM UTC-4, wrote:
One small note. The FAA registry now gives the Mode S code in
both Hex and Octal. The conversion information is no longer needed.

Right, I wrote that prior FAA provided HEX...

You created a living, breathing file Dave!