View Single Post
  #9  
Old September 17th 12, 01:31 PM posted to rec.aviation.soaring
Jim[_32_]
external usenet poster
 
Posts: 49
Default PowerFlarm PCAS performance

On Monday, September 17, 2012 7:33:52 AM UTC-4, joesimmers wrote:
Thanks for posting your config files guys, (mine is below)



I downloaded my config file from powerflarm us website, it appears I am missing a large amount of the info that you guys have for pcas and adsb ranges.



Where did you download your config files from?



Thanks, Joe











################################################## ######################

#

# 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,0



# 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,ADE5B2



# 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 DB9 serial port (both GPS and FLARM).

# Needed if you want this data !

# Ignored on portable.

$pflac,s,nmeaout2,1



# 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


You can "roll your own" config file (if you are competent) by using the FLARM tool located at:
http://www.butterfly-avionics.com/in...core-config-en

I didn't use this tool because I just used MS Notbook to edit the txt file myself using the FLARM documentation. If you do it this way be sure to refer to the current documentation at:

http://powerflarm.us/manuals-softwar...release-notes/

Especially important is the "PowerFLARM dataport addendum" at the bottom of the page too