Sample Config file

Sample Configuration File

There is a sample flightlog2kml / fl2mqtt / fl2ltm sample configuration file below. This may be used as a template for your own file, located as (OS dependent):

• ~/.config/fl2x/config.json (Most OS)
• %LOCALAPPDATA%\fl2x\config.json (Microsoft Windows)

{
   "blackbox-decode" : "blackbox_decode",
   "blt-vers" : 2,
   "dms" : false,
   "efficiency" : false,
   "extrude" : false,
   "gradient" : "",
   "home-alt" : -999999,
   "kml" : false,
   "outdir" : "",
   "rssi" : false,
   "split-time" : 120,
   "type" : 0,
   "visibility" : 0,
   "max-wp" : 120,
   "attributes" : "",
   "fast-is-red" : false,
   "low-is-red" : false
}

The above values are the defaults; there's no need to include them unless you need to change them. If you'd also like a colour-coded efficiency plot, set efficiency to true. All the options (and defaults) can be seen by flightlog2kml --help.

attributes is a post-v0.13.0 feature (also post fl2xui v0.0.7), a punctuation separated string representing additional attributes to be plotted, for example:

effic,speed,altitude,battery

Note that effic (efficiency) effectively obsoletes the efficiency key, which remains for backwards compatibility.

You can specify the full path to blackbox_decode in the configuration file, so to perhaps differentiate between the INAV / βF variants, rename the inav version to inav_blackbox_decode and set the value in the configuration file.

   "blackbox-decode" : "inav_blackbox_decode",

Notes:

• Essentially "key" : value pairs, where the key is command line option.
• Not all CLI options are taken from the configuration file (i.e. log format or application dependent values are not included)
• Unrecognised values are ignored, so you could have a line such as: "comment" : "updated 2021-03-21 to show default values", ; such additions must be syntactically correct though.
• The value for home-alt is a sentinel that indicates "not defined" (as 0 is a perfectly valid value).
• The file must be syntactically correct JSON; the applications will warn of syntax errors
• Common Errors:
  • Not quoting or unbalanced quotes on the key names
  • Missing comma after a (not final) entry
  • Comma after the final entry
  • Missing curly bracket(s)

Windows Path

In order to have a sane setup for Windows drag and drop for both blackbox_decode and flightlog2kml, one strategy might be to have the required applications in a single directory.