Use Opentopodata for elevations

• Use Opentopodata (vice Bing) for elevations
• add --rebase option to set the base location (i.e. scenario relocation)

Add support for BulletGCSS / MQTT

Add fl2mqtt application. Generates MQTT data to stimulate the on-line Ground Control Station BulletGCSS

fl2mqtt

The MQTT option (for BulletGCSS) requires two or three comma separated parameters:

• A MQTT broker, default broker.emqx.io
• A MQTT topic
• The broker port, defaults to 1883

$ fl2mqtt --help
Usage of fl2mqtt [options] file...
  -cafile string
        CA file for TLS broker
  -dump
        Dump log headers and exit
  -index int
        Log index
  -interval int
        Sampling Interval (ms) (default 1000)
  -mission string
        Optional mission file name
  -mqtt string
        Mqtt options [broker,topic,port]

The BulletGCSS wiki describes how these values are used; in general:

• It is safe to use broker.emqx.io as the MQTT broker, this is default if nothing appears before the comma in the -mqtt option.
• You should use a unique topic for publishing your own data, this is slash separated string, for example foo/bar/quux/demo; the topic should include at least three elements.
• If you want to use a TLS (encrypted) connection to the broker, you must supply the broker's CA CRT (PEM) file. A reputable test broker will provide this via their web site.

Example:

## the default broker is used ##
$ fl2mqtt -mqtt ",org/mwptools/mqtt/playotx" openTXlog.csv`
$ fl2mqtt -mqtt ",org/mwptools/mqtt/playbbl" blackbox.TXT`

## broker is test.mosquitto.org, over TLS,
## note the TLS port is also given (8883 in this case)
$ /fl2mqtt -cafile mosquitto.org.crt  --mqtt test.mosquitto.org,fl2mqtt/fl2mtqq/test,8883 -mission simple_jump.mission BBL_102629.TXT

At the time of publication, a contrived demonstration scenario for BulletGCSS using broker.emqx.io, port 8084, topic org/mwptools/mqtt/otxplayer is available. See the BulletGCSS wiki for details on how to configure the web client. This demo:

• Runs every two hours (00:00, 02:00, 04:00 .. 22:00) UTC and;
• Runs for about 40 minutes.

Generated from the openTX log jtest.csv and mission files narita.mission :

$ fl2mqtt -mqtt "broker.emqx.io,org/mwptools/mqtt/otxplayer" -mission narita.mission jtest.csv

0.8.5-rc1

GUI Experimental

Overview

The archives in the release provide experimental GUIs for most of the supported platforms.
As described in #12, there may be one or two GUI applications provide; the purpose of two is to see which, if any, work on platforms to which I have no non-virtual access.

UI

The UI is quite simple:

• Use the "Log" button to load a log (BBL or OTX)
• This will enable the "Run" button; clicking this will (should) perform the conversion.

Both the GTK and Fyne UIs should work in the same way.

Details

Linux 32 and 64 bit

Two GUI programs, fl2kmlgtk and fl2kmlfyne are built on Debian and should work on most reasonably recent distro releases. The gtk variant requires that a GTK runtime is installed. Having any GTK program on your machine should have satisfied this requirement. Please let me know if this is not the case.

MacOS

Only fl2kmlfyne is provided, mainly so I don't have to pack up all the dependencies. If you have a homebrew GTK development environment installed, building the GTK variant should be easy (make gui) and it should run without issues.

Windows

The large archive includes both fl2kmlgtk and fl2kmlfyne and all the required GTK dependencies. The directory structure under flightlog2kml\ should NOT be changed as it is required for fl2kmlgtk to find libraries and other dependencies.

Please note that there is a bug in that for fl2kmlgtk, the generated KML/Z file ends up in the flightlog2kml\bin directory; this will be fixed in the next version.

blackbox_decode

It is necessary that the applications can find blackbox-decode; for Windows, a suitable version is included in the archive.

Reporting Results

Please report any test results under #12. I'm particularly interested in:

• Does fl2kmlfyne run on Windows and MacOS on real hardware? It fails in my VMs.
• Does fl2kmlgtk run on Windows?

Unified flightlog2kml application

• Provide a single flightlog2kml application that can process both Blackbox and OpenTX logs
• Discard OTX logs with minimal (< 64 lines) content

Please remove the bbl2kml and otx2kml application; they are obsolete.
Note that it is possible to process both log types in a single invocation of the application

$ flightlog2kml OTXLog-2021-01-01.csv LOG00042.TXT

Irrationality of version numbers

Just to show that release numbers are figments of one's imagination, here's a point release with lots of new stuff and cleanups.

• New colour gradients (--gradient NAME), red (red), red/green (rdgn), yellow/orange/red (yor)
• Efficiency mode display (requires --efficiency option)
• Major internal cleanups, in preparation for:
  • Unification of bbl2kml and otx2kml into flightlog2kml
  • GUI (don't hold your breath, but it's a possibility)

Please see the front page README; there are some new settings and behaviours.

Add OpenTX log display

Big version bump as there has been a significant functionality increase:

• Added otx2kml to generate KML/Z animations from OpenTX / inav-S.port logs
• Improved fail-safe display (track point icons with central circle, maintaining flight-mode colouring). Improved F/S detection for OTx logs.
• Added summary information for OTx logs (previously done only for BBL)
• Added voltage / current information to track-point popup.
• Internal refactoring to further abstract data structures and interfaces.

0.2.1 Correct Altitude Handling

• Fixed altitude visualisation errors identified in #8
• Improve pop-iup appearance, remove Googles "Directions" link

Thanks to @wilco1967 for his perceptive analysis and data samples

Note this is a bugfix release; the OpenTX log parser will be formally released in a near future feature release, however working code is in the repository and binaries are available in #7

Mission file visualisation

Another version bump as there is new functionality:

• A mission file may be added to the KML/Z, particularly for viewing WP missions
• A standalone mission2kml application is provided
• Mission files may use an optional on-line elevation service to provide above terrain visualisation
• More workarounds / fixes for handling damaged or corrupt Blackbox logs.

BBL with mission

mission2kml, mission altitudes adjusted to terrain base

0.1.1 Improve recognition of legacy nav modes

• Greatly improve the recognition of navigation modes; all versions of inav from pre-1.0 to current development should be supported
• Support ancient BBL with no GPS time stamps
• Don't process logs with no geospatial data

Generate two folders (Flight Mode and RSSI)

• Generate both Flight Mode and RSSI folders
• Provide flight summary (double click on top-level folder)