PowerFLARM parameters for Silver badge?

From the Sporting Code:

4.2.1 Declaration content
a. Date of flight.
b. Name of the pilot-in-command, and the flight crew if any.
c. Glider type, and its registration or serial number or unique NAC-assigned contest number.
d. The make, model and serial number of the FR used (as recorded in the .igc file for the flight). For any barograph or PR used, the make, model, and serial number as verified by the OO before flight.
Additional content for distance and speed flights:
e. Way points and, for a closed course, the sequence to be flown. When any way point is declared using a word description, abbreviation, or code with coordinates, the coordinates are definitive. When only a word description, abbreviation, or code is used to declare a way point, its coordinates must be taken from a published source designated by the NAC.

Further:

4.2 DECLARATION REQUIREMENTS
All flights require a pre-flight declaration except straight distance badge flights using only a barograph for verification. Only the most recent declaration is the valid one.
a. For record flights, the declaration must be input to a FR and appear in its .igc file.
b. For badge flights, the declaration shall be input to a FR and appear in its .igc file or be written, either on a single sheet of paper or transmitted via the internet. If the latter, the pilot shall e-mail the OO or input to a NAC-approved website. The declaration time shall be the time that the e-mail is received by the OO or the website. See Annex C-3.5 for notes on internet-based declarations.
c. For any straight distance flight claimed from release to the landing or to a finish fix, the relevant details of 4.2.1 shall be certified by the OO..
d. If the pilot or glider information is omitted or incorrect in the FR declaration for a Silver or Gold badge flight, the OO certificate required by 5.2.4 shall take precedence.
e. When more than one FR is used, they must have identical flight task data input, and if one fails, the other becomes the direct replacement.
f. A written declaration shall be retained by the OO and submitted with other claim materials.

You can use the online tool at http://www.segelflug-software.de/flarmcfg/ to generate a declaration which is input to your PowerFLARM by the resulting flarmcfg.txt file. There is also a stand-alone tool also available (for Windows) - http://www.segelflug-software.de/prod_flarmcfgtool.html - you can change the waypoints file for your local ones.

2D

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

On Friday, March 6, 2015 at 10:56:13 AM UTC-5, Dan Daly wrote:
You can use the online tool at http://www.segelflug-software.de/flarmcfg/ to generate a declaration which is input to your PowerFLARM by the resulting flarmcfg.txt file. There is also a stand-alone tool also available (for Windows) - http://www.segelflug-software.de/prod_flarmcfgtool.html - you can change the waypoints file for your local ones.

2D

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

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

On Friday, March 6, 2015 at 12:32:38 PM UTC-5, Bob Pasker wrote:
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.

I'd recommend that you get used to doing declarations on every flight; then, when Silver Distance day comes, it will be a habit, and not another detail on what will be a hectic day. If you get in the habit of inserting declarations and downloading the files, you will be able to analyze your flying against others ("how did she stay up when I could not?") and gain OLC points (OLC is a great place to store flights for later).

Paper declarations are good for initial attempts; however, the table in Appendix 2 to Annex C of the Sporting Code indicates you don't need one for Silver Height or Duration - just fly the flight and download the file for the Height, and use either the file or a Certificate of Continuous Observation for the Duration...

Annex C is very readable. Recommended reading.

On Friday, March 6, 2015 at 1:02:18 PM UTC-5, Dan Daly wrote:
others ("how did she stay up when I could not?") and gain OLC points (OLC is a great place to store flights for later).


Flights downloaded from OLC have been altered. They will not verify and therefore are not valid for badges.

Walter

On Friday, March 6, 2015 at 9:32:38 AM UTC-8, Bob Pasker wrote:
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.


As you start exploring XC I would try to start making declarations, just for the experience to see how it works, and get used to all the extra complexity associated with different starts and finishes etc. Once you think you've done even the shortest declared flight, download it and play in SeeYou and see if you think the flight really qualifies...