Flarm Config File Parser/Interpreter?

[Papa3]

Has anyone built a utility that reads a config file and spits out a "readable" interpretation of the parameters and values? I'm sitting with the manual and my config file trying to make sure all of the values are what I expected based on what I thought I put into the configuration utility. I can do this - I just don't want to. Can't imagine how someone without an IT background makes sense of how their FLARM is configured.

P3

[MNLou]

FWIW - I do a screen print of my selections before I create the file. Once the file is created, I print out the config file.

Comparing the two is pretty easy.

I file those with my FLARM documentation so I know what to select the next time I update FLARM.

Lou

[JS]

On Monday, April 10, 2017 at 11:42:31 AM UTC-7, Papa3 wrote:
> Has anyone built a utility that reads a config file and spits out a "readable" interpretation of the parameters and values? I'm sitting with the manual and my config file trying to make sure all of the values are what I expected based on what I thought I put into the configuration utility. I can do this - I just don't want to. Can't imagine how someone without an IT background makes sense of how their FLARM is configured.
>
> P3

Erik:
Here's my version. John Carlyle sent this with most of the remarks and I changed a few bits and bobs.
To add more comments, start the line with #
Jim


########################################################################
# This configuration file must be text only and reside in the top
# directory of the USB stick. It must be named FLARMCFG.TXT
# Insert stick before power up, remove when normal display is seen,
# (but don't do this if you are writing a debug file - see below)
########################################################################

# Original reset line. Clears PowerFlarm, sets all parameters to default values
# $PFLAC,S,DEF

# Complete factory reset. Use once in a one-line config file.
# $PFLAR,99

########################################################################
# dataport configuration
########################################################################

# nmeaout1 = RJ45 connector, nmeaout2 = DB9 connector
# 71 = v7 GPS + Traffic, 72 = v7 GPS only, 73 = v7 Traffic only
# baud1 = Baud rate on RJ45, baud2 = Baud rate on DB9
# 0 = 4800, 1 = 9600, 2 = 19200, 3 = 28800, 4 = 38400, 5 = 57600

# configure RJ-45 port
$PFLAC,S,NMEAOUT1,73
$PFLAC,S,BAUD1,5

# configure D-SUB 9 port
$PFLAC,S,NMEAOUT2,73
$PFLAC,S,BAUD2,5

########################################################################
# Range
# warning horizontal range and vertical range in meters
########################################################################

$PFLAC,S,RANGE,65535
$PFLAC,S,VRANGE,2000
$PFLAC,S,ADSBRANGE,6000
$PFLAC,S,ADSBVRANGE,1000
$PFLAC,S,PCASRANGE,3000
$PFLAC,S,PCASVRANGE,800

########################################################################
# 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 in my ship results in false PCAS alerts about every 10 min
$PFLAC,S,OWNMODEC,0

# 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

# create PCAS beeps (0=no, 1=yes)
$PFLAC,S,PCASBEEP,0

# PCAS output to RJ45 (0=no, 1=yes)
$PFLAC,S,PCASPFLAU1,1

# PCAS output to DB9 (0=no, 1=yes)
$PFLAC,S,PCASPFLAU2,1

# audio out (0=no, 1=yes)
$PFLAC,S,AUDIOOUT,0
$PFLAC,S,AUDIOVOLUME,100

########################################################################
# aircraft configuration
########################################################################

# aircraft ICAO code (hex)
$PFLAC,S,ID,YOUR 6-DIG

# aircraft type (1=Glider, 2=Towplane, 8=Reciprocating Powerplane)
$PFLAC,S,ACFT,1

$PFLAC,S,PILOT,YOUR NAME HERE
$PFLAC,S,LOGINT,4
$PFLAC,S,GLIDERID,YOUR REGISTRATION
$PFLAC,S,GLIDERTYPE,YOUR GLIDER
$PFLAC,S,COMPCLASS,YOUR CLASS
$PFLAC,S,COMPID,YOUR ID

########################################################################
# Tracking
########################################################################

# Stealth Mode (0 no, 1 yes)
$PFLAC,S,PRIV,0

# Third Party Tracking (0 Track, 1 No Track)
$PFLAC,S,NOTRACK,0

[Papa3]

Thanks Jim. I've got the specs and can read them. Just annoyingly time-consuming in this day and age. What I was looking for was a simple utility that reads "FLARMCFG.TXT" and spits out a readable file of the control parameters and their values interpreted for human consumption.

So, something like:

$PFLAC,S,PRIV,0 would translate to Stealth Mode = Off whereas
$PFLAC,S,PRIV,1 would translate to Stealth Mode = On

And so on down the $PFLAC line.

Reading my file today, I discovered that my Flarm ID was set to high values (FFFFFF). Not sure if I mis-typed or left it blank earlier, but wondering if this had anything to do with my perceived poor range recently. Anyway, I've now got the factory default reset Config plus my customized Config. Of course, this means I need my laptop so I can swap them out of the root directory as I go through the whole reset procedure.

Used to be that early Spring flights entailed bringing the toolbox, grease and oil, inspection mirrors, and air pig to the field. Now it's thumb drives, USB cables, SD Cards, and one or more computing devices.

P3

[Richard Pfiffner]

The FFFFFF PowerFlarm ID is the default for a PowerFlarm and will have no effect on range.

Richard
www.craggyaero.com

[JS]

On Monday, April 10, 2017 at 6:44:28 PM UTC-7, Papa3 wrote:

It was called FLARMtool. I've used versions 2.x and 3.x.
You download the FLARMtool for the latest version of FLARM and connected your FLARM to it. FLARMtool would update your FLARM and you could choose all the configureable items in an understandable way.
All that went away with PowerFLARM.
Jim

[JS]

Missed the "install FLARMtool on your computer" bit.
Jim

[Dennis vreeken]

How about we just smoke barographs and take photos . Let's make it harder for us over 60 crowd. 😀

[Karl Kunz]

Don't know if this will help but Flarm does have a downloadable FLARM CONFIGURATION SPECIFICATION
manual available https://flarm.com/support/manuals-documents/

On Monday, April 10, 2017 at 11:42:31 AM UTC-7, Papa3 wrote:

[Dan Marotta]

Hahahahahahahahahaaaaaaaaaa... Us old farts got all of our badges with
photos and barographs... And maps, too!

On 4/10/2017 10:35 PM, Dennis vreeken wrote:
> How about we just smoke barographs and take photos . Let's make it harder for us over 60 crowd. 😀

--
Dan, 5J

[Brad Alston]

'Papa3[_2_ Wrote:
> ;943084']Has anyone built a utility that reads a config file and spits

I don't know if anyone has built a utility, other than what has been
mentioned on this thread, so I took a look at the Flarm Configuration
Specification today and agree that it is written by IT geeks for IT
geeks...although I've seen worse! I did a little coding tonight and
could probably provide something of interest for you in a few days time.
Yes, I'm one of those IT geeks!

If interested in seeing what I come up with, when I get it, email me
direct at alstonbk at gmail dot com.

Safe soaring!

Brad.




--
Brad Alston

[markde...@gmail.com]

I'm about 95% finished coding a nice iPhone based Powerflarm configurator.
My Flarmview had been giving me a message that said their was an issue with the config file and I finally tracked down the not so obvious detail on Sunday.

I need to do the storyboard for the iphone 5 screen size and then submit to Apple, so it's pretty close to being finished.

I had hoped to utilize the iXpand USB stick from SanDisk to go direct from iphone to PowerFlarm, but I'm not sure the PowerFlarm will play nice with the SanDisk USB. I need to test that again.

Plan B is iphone app to email to clubhouse computer to USB to PowerFlarm.

Mark

[t...@serkowski.com]

On Wednesday, April 12, 2017 at 4:16:58 AM UTC-7, markde...@gmail.com wrote:
> I had hoped to utilize the iXpand USB stick from SanDisk to go direct from
> iphone to PowerFlarm, but I'm not sure the PowerFlarm will play nice with the
> SanDisk USB. I need to test that again.

I've had good luck using the HooToo USB drive to transfer files from the PowerFLARM to iPhone.

And I would be very interested in the config utility as well.

-Tom

[Papa3]

What's an "iPhone"? :-)

[markm...@gmail.com]

What's an "iPhone"?   :-)

The iPhone is a slightly more sophisticated communication system than the telegraph or teletype, requiring a basic knowledge of a "QWERTY" typewriter keyboard and thumbs that will eventually evolve into pinpoints. Also used to eliminate basic rules of proper grammar and spelling ability, as Apple knows what you really meant. Usually used by introverts afraid to communicate by voice. Less sophisticated than the "telephone," which allowed users to transmit and receive data via simple conversation. Also encourages and reinforces Pavlovian response to stimulus, as another iPhone user's ding, ring or other signal is often misinterpreted by others as a "CRITICAL" alert which requires them to reflexively twitch and reach for their own electronic leash.

[cliff...@gmail.com]

Mark , you missed your calling, you should have been a technical writer for Apple! Lol

[Dan Marotta]

Yes, and he can spell and punctuate, too!

On 4/13/2017 8:42 PM, cliff...@gmail.com wrote:
> Mark , you missed your calling, you should have been a technical writer for Apple! Lol

--
Dan, 5J

[christoph...@googlemail.com]

For PowerFLARM: http://www.butterfly-avionics.com/tools/pf_core_config.php

Not sure if this works for older FLARM.

Christoph

[Brad Alston]

'Papa3[_2_ Wrote:
> ;943084']Has anyone built a utility that reads a config file and spits

> out a "readable" interpretation of the parameters and values?

> P3

Finished the initial coding for the FLARMCFG.TXT file parsing; output
below based on the example file JS provided previously. This is pretty
ugly but can be polished up without too much trouble...if anyone is
still interested?

Safe soaring!
Brad.

Parameter: NMEAOUT1 Setting: 73 NMEA Ver. 7 - FLARM (inc. PGRMZ) only
Parameter: BAUD1 Setting: 5 57.6 kBaud
Parameter: NMEAOUT2 Setting: 73 NMEA Ver. 7 - FLARM (inc. PGRMZ) only
Parameter: BAUD2 Setting: 5 57.6 kBaud
Parameter: RANGE Setting: 65535 (Unlimited)
Parameter: VRANGE Setting: 2000 m (6562 ft)
Parameter: ADSBRANGE Setting: 6000 m (19685 ft)
Parameter: ADSBVRANGE Setting: 1000 m (3281 ft)
Parameter: PCASRANGE Setting: 3000 m (9843 ft)
Parameter: PCASVRANGE Setting: 800 m (2625 ft)
Parameter: MODEC Setting: 1 (On)
Parameter: OWNMODEC Setting: 0 (Off)
Parameter: PCASCALIBRATION Setting: 30
Parameter: XPDR Setting: 2 (Mode-S)
Parameter: MODESALT Setting: 1 (On)
Parameter: PCASBEEP Setting: 0 (Off)
Parameter: PCASPFLAU1 Setting: 1
Parameter: PCASPFLAU2 Setting: 1
Parameter: AUDIOOUT Setting: 0 (Off)
Parameter: AUDIOVOLUME Setting: 100
Parameter: ID Setting: YOUR 6-DIG
Parameter: ACFT Glider/Motor Glider Setting: 1
Parameter: PILOT Setting: YOUR NAME HERE
Parameter: LOGINT Setting: 4 s
Parameter: GLIDERID Setting: YOUR REGISTRATION
Parameter: GLIDERTYPE Setting: YOUR GLIDER
Parameter: COMPCLASS Setting: YOUR CLASS
Parameter: COMPID Setting: YOUR ID
Parameter: PRIV Setting: 0 (Off)
Parameter: NOTRACK Setting: 0 (Off)




--
Brad Alston