Add Ardupilot `*.bin` (dataflash) logs

This build adds support for Ardupilot *.bin logs. This has an external dependency:

• mavlogdump.py.

Log replay via LTM (e.g. in mwp) should start more quickly.

Note that the Ardupilot support is somewhat experimental (offers of logs for further development appreciated). In particular, the translation of flight modes may not be entirely correct.

Positive current

Doesn't report negative current draw in blackbox logs (should never happen, but it does).

Minor updates

• Update mission file readers and writer (as impload)
• Improve mission index defaults for log2mission and fl2ltm

Efficiency as you see fit

• Fixes the colour of efficiency "outlier" points that fell outside of the 0.05 ... 0.90 quantile used for colour range selection. (#19)
• Add the option to use with mAh/km or Wh/km for determining the colour gradient for efficiency plots. Both units are shown in the track point popup. The energy unit to use for defining the gradient fill is set by the new -energy-unit option:

   -energy-unit string
    	Energy unit [mah, wh] (default "mah")
  

  This can be set in the config file if required. (#19)
• Better 'Fatal' diagnostics.
• Minor fixes to LTM replay and Bullet log parsing and processing.

Replay Bullet Logs to LTM

Mainly (solely) for mwp, fl2ltm can replay Bullet logs.

Requires contemporary mwp for mwp visualisation.

Nothing to see here

Just some tidying ...

• Fix reading Bullet logs
• Support inav 3.0 absolute altitude mission files

Your mission, should you choose to accept it ...

log2mission

This release adds a new application log2mission that will generate an inav mission file (MWXML) from a flight log (Blackbox, OpenTx, BulletGCSS).

• You want to create a mission definition from a BBL (or part of it, maybe when in Cruise Mode).
• You have a log from a WP mission, but you've mislaid the mission file and would like to recreate it.

The generated mission file can be edited in an inav mission planner if required (mwp, Inav Configurator, Drone-helper) and / or uploaded to the flight controller (e.g. using mwp, Inav Configurator, Drone-helper or impload).

Please see the log2mission description in the README, in particular how the epsilon parameter affects the generation of mission points, and use of the time and flight mode filter options.

Addresses #16

BulletGCSS logs

BulletGCSS log files are now a supported log format (in addition to Blackbox and OpenTX) and are auto-detected. You can thus use BulletGCSS logs to generate KML/Z or missions. KML/Z in Google Earth is a somewhat effective means to identify GPRS black-spots.

Addresses #15

Standards are for wimps, not web giants

Ardupilot OpenTX logs

This build provides some support for Ardupilot/yappu OpenTX logs (#13). There are a number of constraints and restrictions:

• This functionality is based on one sample log; it may not be representative of other AP/OpenTX logs
• Compared to the INAV log, there are fewer useful fields (much of the data available to the yappu widget is not logged), hence:
  • The flight mode will always be ACRO, the number of satellites 13 and a fix assumed when the craft is armed (this information is not available from the log)
  • Heading and Altitude may not be updated (they are not in the sample log).

Thanks to @skorokithakis for the idea and sample log.

Placemark / Folder visibility

@CapnBry reported that the visibility of placemarks in folders differs between the desktop and web Google Earth applications.
What a mess; the OGC KML standard mandates a particular behaviour; however Google declines to implement this in the desktop application as "changing this would break existing code" . As most the users use the desktop (vice the web) application flightlog2kml follows Google's lead on this. However, this release offers an option to override this and set the required behaviour as a command option or in the configuration file if you want to make a behaviour your personal choice.

$ flightlog2kml -help
Usage of flightlog2kml [options] file...
 ...
  -visibility int
    	0=folder value,-1=don't set,1=all on

Anything other than the default of 0 causes the desktop client to behave badly, and the web client to behave more rationally. However, it's much easier to un-check folders in the desktop than it is to un-check every placemark in the web app.

Configuration File

There is now an optional configuration file. Default settings may be set in a JSON formatted configuration file.

• On POSIX platforms (Linux, FreeBSD, MacOS), $HOME/.config/fl2x/config.json
• On Windows %APPDIR%\fl2x\config.json

The keys in the file are the relevant command line options, the following are recognised:

• dms
• extrude
• kml
• rssi
• efficiency
• split-time
• home-alt
• blackbox-decode
• gradient
• outdir
• blt-vers
• type
• visibility

For example:

{
    "dms": true,
    "extrude": true,
    "gradient": "yor",
    "efficiency": true
}

Deprecation Notice

The settings of default values via the environment variable $BBL2KML_OPTS may be removed in a future release.

Not much happens -- or not

NOTE The Linux image was recreated 2021-03-14 to remove a glibc version dependency.

This build adds a LTM (Lightweight Telemetry) generator, fl2ltm. This is intended to be a replacement for mwp's replay_bbox_ltm.rb and otxlog Blackbox log and OpenTX logs replay tools.

Note that fl2ltm is not provided in the build archives and there is no separate Makefile target, rather it is necessary to invoke fl2mqtt as fl2ltm; on POSIX (Unix like) systems this is most easily done by creating a link (hard or soft) between fl2mqtt and fl2ltm .

# cd <install location>
# ln -sf fl2mqtt fl2ltm

mwp automatically recognises fl2ltm and uses it in preference to the older tools.

Other changes:

• Improve generation of nav_mode
• Use BBL craft name for mqtt / ltm modes
• Improve support of ancient log versions
• Support BBL files where the number of BBL columns varies between flight indices (BBL originally recorded to EEPROM).
• Minor cleanups

Support all inav WP types for mqtt generation

• Support all inav WP types (including those not fully supported by BulletGCSS)
• Generate current WP no data when a mission file is provided
• Fully static binaries on all platforms