Attached is a experimental log2mission that will take a supported flight log (Blackbox, OpenTX log, BulletGCSS log) and generate an inav mission file (MWXML). The generated log may then be edited in an inav mission planner (mwp, inav-Configurator, drone-helper etc.) and/or uploaded to the inav FC.

At the moment the whole log is considered (see below for some possible filter options) and the number of points generated is controlled by the opaque epsilon value. The default value seems to work for the very few logs tested to date. It may be that the default value gives to many or too few points. Decrease the value to increase the number of mission points.

Some ideas for future filters include:

• Time offsets, start - end (where end can be from the end of log), e.g 1 minute from start to 30 seconds from end
• Flight mode includes (e.g. 3D Cruise)
• And an 'AND' combination of the above.

Suggestions for (a) filters and feedback (especially on outrageously different epsilon, i.e. outside of say (0.01 - 0.02)) and samples of logs where it fails to give any sort of sane result will be appreciated.

$ log2mission --help
Usage of log2mission [options] file...
  -epsilon float
    	Epsilon (default 0.015)
  -index int
    	Log index
  -interval int
    	Sampling Interval (ms) (default 1000)
  -rebase string
    	rebase all positions on lat,lon[,alt]
  -split-time int
    	[OTX] Time(s) determining log split, 0 disables (default 120)

log2mission 0.98-rc2, commit: 988f039/2021-04-07

The mission file is created in the current directory, name derived from the source file and flight index, e,g, a BBL file LOG00666.TXT with a single flight would generate LOG00666.1.mission

The archive below contains Linux x86_64 and Win32 binaries for log2mission.
fl2kml_0.98-rc2.tar.gz

I've dumped a blackbox log to a kmz file and it worked great. However, the non-default Folder has every one of its points visibility set to false. This means when I load it up in earth.google.com/web/ it can't easily be toggled on and off. With just the default options, Flight Mode is visible, and RSSI has the no-eye (not visible) icon. Clicking the visible icon, nothing appears. If -rssi is added, then the flight mode exhibits this behavior but RSSI works. If -efficiency is added, then it matches the visibility of rssi (all disabled if Flight Mode is the default view, and usable if RSSI is the default view).

Looking at the code, it sets all the points visibility to the parent's visibility. Is there an issue that prevents it from being kml.Visibility(defviz)) but then addPoints(..., true) so that all the points are visible=true, but the Folder has the visibility set as it is now? Google Earth Web slows to a crawl if you try to enable each individual point, but works great just toggling the folder visibility.

Updated with better styling and proper style merging, so you can have f/s icon and extrude lines.

Not sure if I don't like this better than without the lines, OTOH, can always use BBL2KML_OPTS=--extrude

Damn, I now know more about KML than I ever thought I'd need to.

Originally posted by @stronnag in #10 (comment)

Mac, Linux, Windows binaries with this comment ... *-x3 includes --extrude in bbl2kml as well

bbl2kml-0.8.1-x3-macos.zip
bbl2kml-0.8.1-x3-linux-ia32.tar.gz
bbl2kml-0.8.1-x3-linux-x86_64.tar.gz
bbl2kml-0.8.1-x3-win32.zip

For the benefit of pilots who can't remember which firmware they're flying, it would be convenient if the flightlog2kml could also decode OpenTX logs from ArduPilot.

get run time error index out of range on whatever inav log file tried

(using european win setting - comma is delimiter for decimals, can cause issues ?)

Any hints ?

It would be useful to have KML/Z generated from a BulletGCSS log (created either by the BulletGCSS webUI or mqttcap ) as a means of easily and visually identifying areas of poor GPRS coverage.

Not sure how well this will work in practice, as we can get rogue positions when the location and 3D fix are not in sync (particularly in areas of bad coverage, unfortunately); however is some logic to try and mitigate this.

If the log contains mission information, that is also added to the generated KML/Z.

Experimental Linux x86_64 and Win32 binaries in the archive attached to this issue (dev branch commit c563583)
fl2kml_0.98-rc1.tar.gz

Trying to run the latest release on Ubuntu 20.04.1 fails with:

otx2kml: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by otx2kml)

Hi Jonathan,

Great piece of software again. Works beautifully.
Hope you don't mind me some nitpicking....

I fly in pretty flat surroundings (NL), but still happend to notice some strange behaviour.
I flew a WP mission, with long stretches of same altitude, but when plotting the mission, I noticed the track seemed to follow the landscape elevation below.
Although the actual landscape is flat, the reported elevation in google earth seems to pick up treetop hights occasionally, so it shows some 'hill', while there is actually nothing below (just a small wooded area).

The mission was flown at mostly 75 meter, and in the dot description, it is reported as precisely 75 meters, but still the dot's are drawn slightly higher / lower, following the ground elevation below.

iNav reported highed is relative to launch elevation, but somehow, google earth shows if following the landscape elevation while in fact it flew constant elevation.

If I plot the same flight, from the OTx log, and show it in google earth (using openTx companion logviewer), it shows a nice even elevation, but consistantly below the BBL/kmz file.

I'm guessing, google earth plots the points relative to ground level ?
Perhaps we'll have to plot them absolute, and recalculate each point elevation, to the ground elevation at the arming point (not current position) ?
Also, use the arming elevation, not the (safe)home point (which, btw, is shown correctly)

the -elev options didn't seem to make any difference.

Using windows 10, iNav 2.5.1 (older flightlog), MatekF722

BTW, it would be nice if you could add a (grey) ground track below.

Anyway, a very nice tools.... especially for flight outside of radio range (i.e. without OTx log).

attached, the 'offending' BBL file
LOG00074.TXT

Cross-platform GUIs are a pain in rear; cross-compiled more so. However:

• GTK is available on Linux, MacOS, Windows (the latter two a bit flaky but doable)
• Fyne is a cross-platform GUI pretty much where ever there is a Go compiler. Non-native, slightly ugly UIs but cross-compilable (which is important to me).
• The codebase is sufficiently abstracted that maintaining three UIs (CLI, 2xGUI frameworks) is not difficult; and I'd prefer the to do the work if it means I get a nicer / native UI on open source platforms.

So the plan is:

• The code base will support GTK and Fyne on Linux, MacOS and Windows
• Binary releases will be GTK for Linux, Fyne for everyone else
• If you want to build the GTK version for other platforms, you can. Instructions will be provided for MacOS and Windows.

GTK (Linux)

Fyne (on Linux, but same everywhere)

Work in Progress ... test data, needs to be wired up to the KML generator)

Hello! I am trying to process the .txt running with flightlog2kml.exe and the pop-up window to process is not activated.
I have tried only with the blackbox decoder and I got the 4 files to see in googlemaps, but I can't process the TXT to get the KMZ.
I clarify that the .json file was edited with the // indicating the corresponding path.
I have even deactivated the antivirus in case that would be generating a problem, but on the other hand the other files could be generated by the decode.
windows 10 64 bit operating system
Inav 6.1.1
Thank you very much if you can help me

Hi! I'm using opentx on a flysky i6x, which doesn't have SD card support, so there are no CSV files available. But we have telemetry mirror being output on the smartport, which in turn goes to the CrazyDude's Android app through bluetooth (HC-05).

Finally that app generates a .log binary file with the raw CRSF telemetry from ExpressLRS.

I couldn't find support for this decoding, how far do you think bbl2kml is from doing this?

Here's a feature request for basically the same: CrazyDude1994/android-taranis-smartport-telemetry#76

I may be able to help with this, but would have to check if it's easier here or in the Android app.

Thanks in advance!

It would be nice if the mission file could be embedded in the KML for visualisation of WP missions, thusly:

All the parts exist:

• mwptools' mission2kml.rb
• impload Golang mission file processing and conversion

The only problem is that misison files are relative to home altitude rather than above the terrain at the way point, however mwptools' Mission Elevation / Terrain Analysis tool already has some techniques solve this.

So it should be just an integration / porting exercise. In progress.

In addition to the elevated flight points, it would be useful to have an (optional) ground track. Single colour (grey). As suggested in #8, separate issue so it's not forgotten.