thanks, most helpful answer yet. i'm not ready to do distance, just altitude gain and duration, so I don't yet have to worry about the declaration.

On Friday, March 6, 2015 at 11:24:30 AM UTC-5, Dan Daly wrote:
On Friday, March 6, 2015 at 11:05:18 AM UTC-5, Bob Pasker wrote:
thanks. unfortunately, i cant fill out the form until I know all the parameters, and that won't happen till I'm at the airport

Similar problem at our club - 3 flarm-fitted club gliders. Members fill out multiple declarations, and use the one for the glider they fly. The flarmcfg - Tool is very easy to use. The type of glider and registration should be available. Class is important for records only. For PowerFLARM, 4 seconds gives a nice looking trace and keeps data records smaller. The declaration is last - this is our club std 50 km flight (takeoff, start, turnpoint, finish, landing) for a 100km out and return). Creating it takes only a few seconds... Keep all in folders for each a/c (or have a different USB stick for each) and move a single flarmcfg.txt file to the highest level of the stick. Insert into usb slot, turn on, let load, go fly, download file, bask in the adulation of your peers.

Here's what the output of the flarm tool looks like; note, it doesn't change flarm or transponder settings - only declaration things.

//FLARM configuration file created with flarmcfg - Tool
//�2009-2011 powered by www.Segelflug-Software.de
//am: 23/02/2014 um 10:06:23 AM


//Pilot Name
$PFLAC,S,PILOT,Daniel Daly

//Co-Pilot Name
$PFLAC,S,COPIL,

//Aircraft Type
$PFLAC,S,GLIDERTYPE,SZD 55

// Aircraft registration
$PFLAC,S,GLIDERID,C-GXDD

//Competition ID
$PFLAC,S,COMPID,2D

//Competition class
$PFLAC,S,COMPCLASS,Club

//Logger interval
$PFLAC,S,LOGINT,4

//Task declaration
$PFLAC,S,NEWTASK,silver d
$PFLAC,S,ADDWP,4529250N,07505650W,01Pendle
$PFLAC,S,ADDWP,4529250N,07505650W,01Pendle
$PFLAC,S,ADDWP,4538383N,07422217W,80Lachut
$PFLAC,S,ADDWP,4529250N,07505650W,01Pendle
$PFLAC,S,ADDWP,4529250N,07505650W,01Pendle