mwp Windows native application (Msys2).

[stronnag]

Overview

There is now a somewhat functional wintest branch that supports building mwptools using the Windows Msys2 toolchain with the aim of providing a native Windows version of mwp.

Status

Somewhat experimental, however most things work.

Purpose

To ascertain the demand for a Window native version, some metrics:

• PRs improving Windows support are submitted
• Issues are generated for Windows issues.
• Reports of success are provided.

Should there be evidence of participation then Windows can become a "maintained" platform.
If there is no indication of user participation, then this experiment can die here.

Building

It is necessary to install the Msys2 toolchain. As Msys2 uses the Arch Linux pacman package manager, the required packages should be those in the AUR package, e.g:

System Dependencies

Add export LC_ALL=C.utf8 to .profile so the blueprint UI defs will compile.
Set your Msys terminal to UTF-8 as well (Options from the title bar icon)

Then install dependencies.

 pacman -S  --needed mingw-w64-ucrt-x86_64-gtk4 mingw-w64-ucrt-x86_64-gstreamer mingw-w64-ucrt-x86_64-cairo \
   mingw-w64-ucrt-x86_64-pango mingw-w64-ucrt-x86_64-mosquitto mingw-w64-ucrt-x86_64-libshumate \
   mingw-w64-ucrt-x86_64-libadwaita mingw-w64-ucrt-x86_64-libsecret mingw-w64-ucrt-x86_64-libsoup3 git \
   mingw-w64-ucrt-x86_64-vala mingw-w64-ucrt-x86_64-meson mingw-w64-ucrt-x86_64-go \
   mingw-w64-ucrt-x86_64-blueprint-compiler mingw-w64-ucrt-x86_64-gcc mingw-w64-ucrt-x86_64-gtk4-media-gstreamer

Optional, but recommended:

pacman -S --needed unzip mingw-w64-ucrt-x86_64-gnuplot mingw-w64-ucrt-x86_64-ruby

• Note that the packages are (mainly) prefixed mingw-w64-ucrt- (vice standard Arch Linux).

Then follow the documented build instructions using meson and ninja.

See also the PKGBUILD note below to automate the process.

Status

Quite a lot is working already. See known issues below.

• User Interface

• Maps, including user defined map sources

• Elevation database and elevation display

• Settings. Configuration files are under $LOCALAPPDIR/mwp. gsettings in the registry.

• RCData processing

  • MSP
  • LTM
  • CRSF
  • Mavlink
  • Flysky AA (untested, probably works)
  • Frsky S.port

• RC Transports

  • Serial USB, probably Bluetooth via COM port
  • TCP, UDP (SITL, mwp-log-replay, fl2ltm (blackbox replay) etc.).
  • MQTT

• Replay tools

  • mwp JSON logs
  • Blackbox replay
  • OTX replay
  • mwp raw log replay

• Missions and Management

  • File open / save
  • Upload / Download FC
  • Editing
  • Preview
  • Terrain Analysis (Msys ucrt gnuplot now works).
  • LOS Analysis

• Geozones

  • File open / save
  • Upload / Download FC
  • Editing

• Safehomes

  • File open / save
  • Upload / Download FC
  • Editing

• Static (KML) overlays

• Preferences

• Survey Area Planner

• Mission Manager

• Map Seeder

• Places Manager

• Distance measure tools

• Radar View and ADSB targets

• Telemetry Tracker (working, /any same omissions as in dev/master).

• GCS Icon

• Help menu functions

• Audio. No solution identified Working with external application --voice-command espeak.exe

• CLI terminal. No solution identified

• Embedded Video (unlikely to work, looks like gtk4 on Windows limitation)

Known issues

TODO

• Enumerate COM ports
• Suspend and Resume for replays

Paths and Home directories

Just do a "system" install and the issues below disappear.

MSys2 and Windows have separate ideas of the home directory ($HOME) for a given user ($USER / %USERNAME%).

• Msys2: /home/$USER, aka /c/msys64/home/$USER aka c:\msys64\home\%USERNAME%
• Windows: C:\Users\%USERNAME% aka /c/Users/$USER

This affects where stuff gets installed, as meson --prefix=~/.local will install to the Windows home (C:\Users\%USERNAME%\.local aka /c/Users/$USER/.local/.

Settings Schema

As a consequence of the above, the settings schema is installed to the Windows home path. This only matters if you want to manually change settings using gsettings or dconf-editor, in which case it's necessary to set the schema path:

gsettings.exe --schemadir /c/Users/$USER/.local/share/glib-2.0/schemas/  list-recursively org.stronnag.mwp

A system install (see the PKGBUILD note below) solves the PATH related problems.

Replay suspend / resume

Not yet working, due to lack of obvious Windows process suspend /resume API. At some stage the well known but un-obvious API will be implemented.

Audio

Requires a spawned "helper". The Windows espeak port works perfectly as an external helper via --voice-command espeak (having set an appropriate PATH). The --voice-command option may be set permanently in $LOCALAPPDATA/map/cmdopts, for example (ignore the local radar device) :

# cat $LOCALAPPDATA/mwp/cmdopts

--voice-command espeak.exe
--rings 50,20
--mod-points 4
--radar-device http://jagular.daria.co.uk/dump1090/data/aircraft.json
MWP_TIME_FMT=%T.%f

Reporting Issues

Please see the general guidance, in particular:

• Build issues require the full build text, not just some random subset
• Run time issues require the "stderr" log (mwp_stderr_YYYY-MM_DD.txt) as well as any artefacts that cause an issue (BBL, ETX log, mission files etc.).

[stronnag]

SITL, artefacts load from "FC Eeprom"

Blackbox replay, artefacts from CLI file

Mission Line of Sight Analysis

[stronnag]

More fixes:

• Ensure we shutdown any spawned --voice-command applications on shutdown
• Vigorously prefer IPv6 over IPv4
• Requires fl2ltm 1.0.26 (Ipv6 priority) for replays.
• Please install DejaVu Sans Mono font to avoid the monospace font ugliness.
• Report Windows OS version in log.

[stronnag]

Note that mwp creates and consumes IP services. Please ensure it's white-listed in the Windows firewall.

[stronnag]

• Terrain Analysis works (Msys2 gnuplot)
• Note better panel fonts with DejaVu Sans Mono installed (Wn10, the Win11 fonts are usable as-is).

[stronnag]

MQTT (GCSS shema) ... either mosquitto or the paho library.

[stronnag]

PKGBUILD

Here's a build helper:

The attached PKGBUILD.txt can be used to build mwp on a base Msys2 system. It will download the required dependencies and build an installable package.

• Create / enter a build directory, any name your like, e.g.

   mkdir msys-builds && cd msys-builds
  

• Download PKGBUILD.txt and rename it (because Github has this inane idea that "extensions" mean something).

  mv PKGBUILD.txt PKGBUILD
  

• Now you can build the package:

  makepkg-mingw
  

  This will generate a Msys2 package names like (the name includes a git tag and commit id) mingw-w64-x86_64-mwptools-24.12.02.r76.c1e34843-1-any.pkg.tar.zst which can be installed with pacman

  pacman -U mingw-w64-x86_64-mwptools-24.12.02.r76.c1e34843-1-any.pkg.tar.zst
  

• Note that you can build and install in one command:

  makepkg-mingw -i
  

After you've done this once, subsequently, after the repo has been updated, you can rerun the build / package generation by rerunning makepkg-mingw (and pacman to install) as required.

This will perform a "system install" (i.e. under /mingw64 ; thus /mingw64/bin/mwp etc.).

[stronnag]

Today's package
mingw-w64-ucrt-x86_64-mwptools-24.12.02.r85.67cd4ada-1-any.pkg.tar.zst.zip

[b14ckyy]

Lets add findings, issues, requests as replies to this Post to keep the thread clean.

[stronnag]

On the multiple map layers, mwp tries to keep two layers in the stack, so slow loading doesn't give a blank map. So if neither is loaded then you'll see two loading.

[stronnag]

On map loading speed, you might also try one or both of

• File Manager: Navigate to C:\ucrt64\bin and launch from the mwp.exe icon
• Experiment with the GSK_RENDERER environment variable (see Migration Guide ).

If any of the GSK_RENDERER values (listed in the Migration Guide ) proves better (a) please let me know and (b) you can set in permanently it in $LOCALAPPDATA/mwp/cmdopts (aka %LOCALAPPDATA%\mwp\cmdopts aka $Env:LOCALAPPDATA\mwp\cmdopts`)

Example cmdopts :

# Default options for mwp
--rings 50,20
--dont-maximise
--mod-points 4
--radar-device http://woozle/readsb/data/aircraft.pb
--voice-command espeak.exe

MWP_BLACK_TILE=/home/jrh/.config/mwp/mars.png
MWP_TIME_FMT=%T.%f
GSK_RENDERER=vulkan

And for the "hint-proof" reader , I really recommend you read the Migration Guide even if you're not migrating from legacy mwp.

[b14ckyy]

I think I found the Map speed issue. Seems to be caused by Bing Proxy only.
When I start with OSM Mapnik, all is fine and fast. When I switch to Bing Proxy the loading takes very long. Even switching back to OSM keeps it very slow (probably because it holds 2 map layers as you mentioned?) But when I then switch to ESRI Maps all loads very fast as expected. Same when switching back to OSM again.

[stronnag]

OK. I see at least two problems here.

• The cache directory is set incorrectly for the Windows case.
• I changed from the old http sources to the new https sources. This may be less of an issue.

[stronnag]

I broke the Bing URL selector when I switched base URI. Fixed in development branch. Yes, wintest is no more, we've gone main-line.

With latest development commit, you can see the out-going GET requests, and visually see that the map updates in a timely manner.

# See map GET requests ...
mwp --debug-flags 2048

[stronnag]

You wanted COM auodetect (not pushed, as it doesn't action removal ... yet)

OK, not as informative as LInux, but it's a start (and the Windows USB enumeration APIs suck) ... and we still can't use the BT devices. But a start.

[b14ckyy]

You said "not as informative as Linux" but to be fair, what it shows is all what we usually need. Thats great already!

[stronnag]

Done, pushed to wintest. There will be a new package later today (probably c. 22:00 UTC).

[stronnag]

• Network and serial errors are often reported as "Successfully completed", which is something of an oxymoron. This is a result of the rather Unixy way of reporting system errors; in Windows the OS has moved on by the time we ask for what the error was.
  Will be fixed at some stage.
  This is more complex than I thought. OS Errors are thread specific. On POSIX platforms, I/O event occur in the main thread (epoll / kqueue / select ) mechanism. For Windows, the "RC Data" I/O has to run in a separate thread. As by errors are evinced /displayed by the main thread, this works fine on the POSIX platforms, but not on Windows, as the main thread is "error free".

[stronnag]

You wanted legacy BT .... please look carefully at the picture ...
This is mega a mega ugly hack.

First a question, mwp detects (as does device manager) 2 BTmodems (COMx and COMx+1 for a single BT dongle). Is this normal?
Anyway, connecting to the second (COMx+1) gives:

Not yet merged.

[b14ckyy]

Unfortunately, that's what I did about 5 times already and looks exactly like in your example. But with no luck.
I start to think it has something to do with Win11 compared to your Win10 environment. This weekend I will set up a Win10 VM and try there.

[stronnag]

I appreciate your fustration, which I'm probably going to make worse by telling you the first time I built mwp on Windows was in a clean Win11 (new Msys2 /ucrt64) install. So I have no further ideas.

[b14ckyy]

In this case I think the problem is my German Language windows 11 installation. Thats the only difference that makes sense. In this case I will make a english one in a VM and try there.
I wonder if that issue also is the reason for my font not being the right one? as you can see in my screenshots.

[stronnag]

So export LANG=en does not help?

For the font, if you mean the panel, then see the #182 (reply in thread). It this works for you, consider adding it the facebook posting.

[b14ckyy]

Yes that worked with the font. Will add that.

I think I tried export LANG=en as well But not sure. Windows is really strange with its localization. In my company we had also trouble in the past with our own applications not working correctly or even crash if a non-english native OS installation is used or specific languages. What mattered was always the installation language, no matter what you switch to afterwards.

So maybe we have a similar problem here.

[stronnag]

Windows/Msys Package for 2024-12-04

• Serial device auto-detection
• Save / restore window size / state.
• Support BT Legacy devices
• Correctly interpret Terrain Analysis exit status
• Make sure map proxies exit on mwp exit.

mingw-w64-ucrt-x86_64-mwptools-24.12.04.r96.137e2371-1-any.pkg.tar.zst.zip

[b14ckyy]

Looks good so far. This is BT connection through mLRS.
Window Size is properly saved and restored.

[stronnag]

Windows/Msys Package for 2024-12-05

• wintest and development branches are now identical
• Fix various subprocess status faults (e.g. affecting Terrain Analysis "climb/dive" output)

mingw-w64-ucrt-x86_64-mwptools-24.12.05.r33.a2654dd6-1-any.pkg.tar.zst.zip

Note: If you want a cutesy Desktop icon, in the Window File Manager:

• Navigate to c:\msys64\ucrt64\bin\mwp.exe
• Right mouse click menu, "Create Shortcut"
• Drag shortcut icon to Desktop, rename as required.

Yes, it's that real a Windows' Application.

[b14ckyy]

Simple user guide for Msys2 Installation:

MWP (MultiWiiPlanner) Ground Control for Windows - How to install?

Since Stronnag made good progress and everything important is running fine so far, I want to give you a quick guide how to install and run MWP on Windows. In the future we might get a standalone installer but the process is still pretty straight forward.

First time Install preparation:

• Install Msys2 from here: https://www.msys2.org/
• Keep the default installation path or use a custom path that does not need Admin rights to prevent problems
• Launch Msys2 UCRT64 Variant (There are multiple Launchers for Msys2)

Installing/Updating Pre-built MWP:

• Go here: https://github.com/stronnag/mwptools/discussions/182
• Scroll down to the latest post that has a link to the latest pre-built test version, download and unzip it so you get a *.pkg.tar.zst file
• Copy this file to C:\msys64\home\[USER]\
• In the Msys2 Terminal window type pacman -U mingw-w64-ucrt-x86_64-mwptools-24.12.05.r33.a2654dd6-1-any.pkg.tar.zst and hit ENTER
• (You can just write pacman -U min and then press TAB to auto-complete)
• Confirm the dependency installation with Y and hit enter

In a first time installation, this process can take a few minutes. After completion, you can launch MWP by just typing mwp in the terminal and hit enter.
Alternatively you can go to C:\msys64\ucrt64\bin and search for mwp.exe. Right click and send a shortcut to your start menu or Desktop to start it directly from there.

[stronnag]

Post Install tasks:

• The monospace font in the right panel (and elsewhere) is very ugly. By default the Gtk Toolkit uses "DejaVuMono" which is standard on most Linux distributions. Without this, it will fallback to Courier New
• You can install this font in Windows to make it pretty:

pacman -S ucrt64/mingw-w64-ucrt-x86_64-ttf-dejavu

Then, in the Windows file explorer, navigate to \C:\msys64\ucrt64\share\fonts\TTF and for each of the Mono files:

• DejaVuSansMono.ttf
• DejaVuSansMono-Oblique.ttf
• DejaVuSansMono-Bold.ttf
• DejaVuSansMono-BoldOblique.ttf

Right click, and "Install for all users".

Now your mono fonts are less ugly.

[stronnag]

You may also download the fonts directly (without the Msys2 package)

[stronnag]

In the unlikely event that anyone was building from the PKGBUILD published earlier, please update to this updated PKGBUILD.txt which is now using development branch (rename to PKGBUILD before use).

[stronnag]

Issues related to any hyperthetical Windows Installer

• As the installer has to include many Gtk libraries, it will be around 43MB
• The user will have to install third party gnuplot (for Terrain Analysis) and unzip (for KMZ files).
• The user will have to install blackbox_decode and fl2ltm in order to replay blackbox / ETX files.
• The above external files will need to be on the PATH available to the installed mwp
• The mwp installer will install gsettings, will need C:\Program Files\mwptools\bin to be on the PATH or cd "C:\Program Files\mwptools" and invoke bin/gsettings`.
• It will be necessary to enable mwp in the Windows firewall for log replays etc.

e.g.

PS C:\Users\win11> $env:Path += ";C:\Program Files\mwptools\bin"
PS C:\Users\win11> gsettings.exe list-recursively org.stronnag.mwp
org.stronnag.mwp adjust-tz true
...

[stronnag]

Just in case you think this is something new.

Checkout the date in the bottom right corner of the image.

(for the date format challenged, that's 3rd January 2016).

[b14ckyy]

The inav version is even more impressive 😁

[stronnag]

5 days after the first ever (documented, successful) WP mission flight).

[Phil-MC]

I followed the Msys2 install with downloading the pre-built test version then pacman -U min and TAB to complete. It ran and I answered Y to install. It appeared to be writing something like 'War and Peace' and eventually stopped.

Typing 'mwp' didn't run anything. I looked in D:\Philip\msys2\ucrt64\bin and mwp.exe was there. Double clicking it caused it to partially load, then my AntiVirus had a fit and locked it away. I rescued it and the familiar view of mwp opened. I was able to get the Bing Map up.

How do I load a BlackBox file?

[Phil-MC]

Thanks, I've done it before with the linux version. I was wondering about the Windows version.

[b14ckyy]

forget that with the BIN folder. Does not work. Needs to be placed elsewhere and then added to path in the system environment variables.

[Phil-MC]

I guess there was no system path to the bin folder. This looks like an insulated Linux install system. Probably needs to be in the correct C: programs folder. Though I often run downloaded standalone packages (eg CONFIGURATOR) from the Downloads or similar folder so I can have all the current ones available.

[stronnag]

When / if the hypothetical installer appears, there will be a system wide install in Program Files (with blackbox_code, fl2ltm and unzip).

Until that date, the easiest thing is to create a system folder (C:\mwpbin, C:\Program Files\mwpbin) or whatever you like, drop the ancillary files in there, and add the folder to the system PATH via the Control Panel.

Or if you don't mind polluting the distro path, just drop blackbox_decode and fl2ltm in C:\msys64\ucrt64\bin.

Likewise, if you install the 3rd party gnuplot (for Terrain Analsys), then add its bin folder to the system path as well.

Then these additional files will be accessible to both the Msys2 shell, a Desktop Icon and Windows shellls (PS, cmd).

And really, I am the last person who should be giving out Windows advice.

[Phil-MC]

Thanks, Jonathan, for that info. That will help a lot. I can work something out from that. I expect you will sort it all out soon.
We all get problems with something.... Mine is Nextcloud updates. I seem to waste a lot of time with each update sorting out bugs in my home cloud system!@#£%^

[stronnag]

Windows/Msys Package 2024-12-07

• Add cliterm
• Re-engineer mwp / mwp-plot-elevations / gnuplot interaction to improve usage in Windows

mingw-w64-ucrt-x86_64-mwptools-24.12.07.r11.380808b1-1-any.pkg.tar.zst.zip

[stronnag]

Experimental Windows Installer

At this stage it is recommended that you run mwp from Msys2. However, there is now an experimental installer.

Overview

• Does not require installing Msys2
• Includes tools for Blackbox and other logs replay
• Include DejaVu Mono fonts

Download page

Unzip the archive and run the installer. Select the option to install a desktop icon if you wish.

Binary Components and Open Source Licences

The Windows installer includes components distributed under various Open Source Licences:

• DejuVu Fonts: Bitsream Licence and other see https://dejavu-fonts.github.io/License.html
• Gtk and dependencies: LGPL2 see https://gitlab.gnome.org/GNOME/gtk
• miniunzip: Zlib see https://www.winimage.com/zLibDll/minizip.html

The above binary components are from the Msys2 Project.

• INAV blackbox_decode : GPL3 https://github.com/iNavFlight/blackbox-tools

Notes

• As the installer has to include many Gtk libraries, it is around 44MB

• The user will have to install third party gnuplot (for Terrain Analysis).

• The above external files will need to be a PATH available to the installed mwp

• The mwp installer will install gsettings, this will need C:\Program Files\mwptools\bin to be on the PATH or cd "C:\Program Files\mwptools" and invoke bin/gsettings. e.g.:

  PS C:\Users\win11> $env:Path += ";C:\Program Files\mwptools\bin"
  PS C:\Users\win11> gsettings.exe list-recursively org.stronnag.mwp
  org.stronnag.mwp adjust-tz true
  ...
  

• It may be necessary to allow mwp in the Windows firewall for log replays etc.

Monospace Font

The installer includes DejaVuMono.

Audio

Requires a spawned "helper". The Windows espeak port works perfectly as an external helper via --voice-command espeak (having set an appropriate PATH). The --voice-command option may be set permanently in $LOCALAPPDATA/map/cmdopts, for example (ignore the local SDR radar device) :

# cat $LOCALAPPDATA/mwp/cmdopts

--voice-command espeak.exe
--rings 50,20
--mod-points 4
--radar-device http://jagular.daria.co.uk/dump1090/data/aircraft.json
MWP_TIME_FMT=%T.%f

Other links

• Gnuplot Windows binary. Install the Msys2 version.
• espeak Windows binary

Data Locations

• Configuration Files: C:\Users\<USER>\AppData\Local\mwp
• Map tiles cache: C:\Users\<USER>\AppData\Local\Microsoft\Windows\INetCache\shumate

Reporting Issues

Please see the general guidance, in particular:

• Build issues require the full build text, not just some random subset
• Run time issues require the "stderr" log (mwp_stderr_YYYY-MM_DD.txt) as well as any artefacts that cause an issue (BBL, ETX log, mission files etc.).

[b14ckyy]

And I also need to learn how to use the dconf stuff in windows to change the advanced settings under windows. the dconf-editor I use in linux with a simple graphical interface is not available in windows.

[stronnag]

gsettings. The Notes section in #182 (comment) is a start then:

gsetting get org.stronnag.mwp KEY
gsetting set org.stronnag.mwp KEY VALUE

e.g.

gsetting set org.stronnag.mwp default-map 'ESRI Clarity'

All the keys are documented in the User Guide (and migration guide, but that may be not entirely current).

[stronnag]

Not ideal on Windows. "Someone" should write a graphical tool for all the advanced settings.

[b14ckyy]

Write the mwp_stderr*.txt log to Documents on Windows (vice $HOME)

regarding that, can you make it a sub folder /Documents/mwp by default? too many applications already clutter that folder without asking. Especially some Java stuff and a few others. I know we can change it afterwards but it would be nice to have it a bit cleaner from the start.

[stronnag]

Please keep a note of these trivia things.
I'll consider them once I've fixed the real crashers (like the post-replay crash).
In the mean time, the user can already configure the logs to wherever she likes https://www.daria.co.uk/mwptools/mwp-Configuration/#environment-variables

[Phil-MC]

regedit in windows.  Save copy before changing anything!Sent from my Galaxy -------- Original message --------From: b14ckyy ***@***.***> Date: 09/12/2024 11:26 (GMT+00:00) To: stronnag/mwptools ***@***.***> Cc: Philip ***@***.***>, Mention ***@***.***> Subject: Re: [stronnag/mwptools] mwp Windows native application (Msys2). (Discussion #182) And I also need to learn how to use the dconf stuff in windows to change the advanced settings under windows. the dconf-editor I use in linux with a simple graphical interface is not available in windows. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[stronnag]

i.e. it follow the XDG standard. End of story.

[b14ckyy]

Ah right you mean the default folder that opens when I save a mission for example. Yes I noticed that.
But anyway, of logs are in a mwp subfolder in /Dcouments that would be ideal. Rest is then on the user.

[stronnag]

Until just now, these folders defaulted to GLib's Environment.get_home_dir() which was $HOME / %HOME% everywhere.
Now they default to:

• Normal (POSIX) OS: Environment.get_user_special_dir(UserDirectory.DOCUMENTS); which is also $HOME, so no breaking change.
• Windows: Environment.get_user_special_dir(UserDirectory.DOCUMENTS) / mwp which is Documents/mwp . This means for Msys2, you now get the same directory regardless of whether you're the Windows user or the Msys2 user (i.e. c:/Users/<NAME>/Documents/mwp.

Note also:

• This is as yet unpublished (it will be pushed later this evening)
• The defaults are established /stored in the settings / registry at first (ever) run. So if you originally ran mwp as the Msys user from terminal, the defaults set in gsettings (registry) will the /home/<USER> . If you then run it from the installer (or a shortcut), you're the Windows user and the defaults are not what you expected. In the latter case, you may wish to change the settings via gsettings or regedit.
• This dichotomy will be less of an issue once most Windows users are using the (work in progress) installer.

Hope that's clear.

[stronnag]

It is also the case that if you have a vanilla Windows 11 install where "big brother" Microsoft knows what's best for you, defaulting to Documents means that the user will get scary popups warning them that the nefarious mwp is writing to their protected directory. But that's fine .... it's want you wanted,

[b14ckyy]

Yep I expected things like that. And yes I know that protected folder thing very well... caused me some headache in the past :D Luckily the popup notification comes up every single time until the user final does click on it and allows MWP to do its thing.

[stronnag]

Windows/Msys Package 2024-12-09

Here's a Msys2 package for 2024-12-09 with some significant fixes:

• Fix the RC data I/O mechanism on Windows so mwp no longer crashes after multiple log replays.
• Add the missing gstreamer packages for media playback
• Default the log directory (and other path settings) to Documents/mwp
• Fix error messages (no more "something bad happened, but we don't know what")
• (Installer) Add icon for menu shortcut

mingw-w64-ucrt-x86_64-mwptools-24.12.09.r0.86e84e99-1-any.pkg.tar.zst.zip

[Phil-MC]

Could it be a gap in the data. I've had logs where the SPI BUS looks as though it has been congested and the data has not gone through intact. Reducing the load on the bus made it work. I couldn't read the log in BB VIEWER. But another showed gaps.

[b14ckyy]

gaps in the data field stream should be visible in the blackbox explorer. I have not noticed any but the log is also over 30min long. Will check that.

[stronnag]

I would not waste your time. The issue is down to massively corrupt headers.

[b14ckyy]

at least this is repairable if I have another intact log from the same craft and config, So I an just copy the header from that.

[stronnag]

mwp will now replay the log, however it's somewhat futile as the flight modes are "random". I doubt the almost whole flight was in RTH. Without FC type and revesion, we cannot accurately decode flight modes, without Vbat (and current) references, power data is wrong, without Acc 1G the attitude is unreliable .... etc.

[b14ckyy]

Unrelated to the Windows version but I wanted to check with you. I found this Repo here of espeak-NG https://github.com/[espeak-ng](https://github.com/espeak-ng) that seems to be in active development. It seems to be fully compatible with the old (and I think discontinued?) espeak commands + more.
Default voice is pretty much the same. I wanna play around with that a bit and figure out how it works.

[stronnag]

Most Linux distros ship espeak-ng in preference to espeak (with maybe a compatibility module). mwp prefers espeak-ng but will use espeak if that's all available (meson/meson.build).

In src/clib/speech_wrapper.c the only difference is the header file names and name of the dynamically loaded library.

Unfortunately the voice quality is still no where near that of the commercial offerings.

[stronnag]

mwptools Windows Installer 2024-12-10

http://seyrsnys-mwptools-win64.surge.sh

• Fixes crashes when playing more than 1 Blackbox log
• Provides warning about corrupt Blackbox logs
• More tolerant of replaying corrupt Blackbox logs
• Breaking change defaults to Documents\mwp for application (mwp_stderr* log files (also default for mission files, BBLs etc. for new installs)).
• Should provide more sensible Windows errors (failure to open COM port etc.).

The download really is Zip file this time, containing the executable installer.

The installer is not quite there yet, but I think we are close.

[Phil-MC]

Looks good.
I'm quite looking forward to trying it.

[stronnag]

2024-12-12 Installer

Installer 2024-12-12

• Adds multimedia files for video replay (e.g. accompanying BBL replay)
• Correct video URI generation for Windows video files
• Fix BBL replay pause / video pause interaction
• The above link also documents mwp's usage of voice.exe, a TTS (Text to speech) program using Microsoft's Speech Synthesis for a more natural voice.

[stronnag]

The Window's specific changes list is getting smaller ...

[stronnag]

2024-12-14 Installer

Installer 2024-12-14

• Improve display update performance (noticeable for BBL replay)
• Fix buffer out of bounds access (thanks to @Jetrell's "crasher" BBL file)

Small change list, but quite significant architectural changes (for the better, everywhere) for the performance improvement. Test results are appreciated.

[b14ckyy]

Would make no sense as the MSP link on a UART at the same time is solid (for mLRS RC and Telemetry). But onver the same UART I also get a stall.
Anyway I need to look at that later again. A friend of mine just tested the same and for him it also works well. So something is wrong on my end but also on 2 different PCs and 2 different INAV versions and connection types on one FC.

[stronnag]

And you just have MSP on the port (no other telemety when armed?)

[stronnag]

And thanks for the friend confirmation, it means I don't have to make condescending suggestions like:

• try a different cable
• reboot the PC
• sacrifice a goat

As far as mwp is concerned, for just MSP polling, whether you're armed or not doesn't make much difference.

[b14ckyy]

Yeah I have nothing else on that. Its VCP and can't even change it anymore in ports anyway. Behaves the same over USB and through mLRS, even mLRS transperent.
But I will check other FCs. Maybe something is off here. That makes no sense to me.

[Phil-MC]

Best of luck Marc with that. If the only thing you haven't changed is the FC then that must be the culprit, or the firmware on it, unless you have tried alternatives.

[stronnag]

2024-12-16 Installer

Another day, another installer. More Windows weirdness addressed.

Installer 2024-12-16

• Modify Windows I/O (again) so subprocess suspend / resume works (e.g. for BBL replay)
• Improve Windows TimeZone processing
• Fix various shortcuts
• Implement Windows idle / screensaver processing (requires setting manage-power true). So the screen will not blank nor the CPU sleep while push telemetry is being received.
• Generic: improve processing of "damaged" BBL files
• Don't display the armed "spinner" on Windows as it appears to disagree with someone's systems ...

[stronnag]

Windows specific change list seems to have grown again ... whatever than means

[b14ckyy]

For the record: Blackbox replay and additonally my "Telemetry Stall" when armed are both fixed with the removal of the spinner widget. Turned out that one caused a ton of CPU load causing all the stall issues on the UI.

[Phil-MC]

Has anyone considered the case of FCs with shared SPI BUS. I have two with BBOX and OSD traffic over the same BUS eg SpeedyBee F405v3 and a MATEK one. This causes errors when both uses are attempted together. Though using MSP DISPLAY PORT reduces the errors. They cope with telemetry to my RadioMaster but I wonder if the MWP load is of the same order or going to cause any issues. I am not sure which SPI busses are in use overall. I was talking to Pawel about them when they came out, and at the time the shared SPI bus was not multiplexed so problems were inevitable.

I don't know how common this arrangement is and wether it might affect your testing...

[stronnag]

It's utterly irrelevant (again).

[b14ckyy]

@Phil-MC I was talking about this widget:

This is fixed now and it has nothing to do with anything the FC does. It was just a render issue in Windows, where the render process is handling the load poorly. As mentioned before: INAV is a Real Time System that runs directly on hardware. Every calculation, every piece of code in the processing loop has to run within its given timeframe or it will get terminated or causes a complete FC stall. If ANYTHING in INAV would cause exorbitant CPU load to cause issues, your Aircraft would crash and MSP would not work at all. Does not matter if armed or not.

[Phil-MC]

Thanks

…

________________________________ From: b14ckyy ***@***.***> Sent: Tuesday, December 17, 2024 10:41 AM To: stronnag/mwptools ***@***.***> Cc: Philip ***@***.***>; Mention ***@***.***> Subject: Re: [stronnag/mwptools] mwp Windows native application (Msys2). (Discussion #182) @Phil-MC<https://github.com/Phil-MC> I was talking about this widget: image.png (view on web)<https://github.com/user-attachments/assets/9e8408d4-084f-4791-879c-92a9ff32967a> This is fixed now and it has nothing to do with anything the FC does. It was just a render issue in Windows, where the render process is handling the load poorly. As mentioned before: INAV is a Real Time System that runs directly on hardware. Every calculation, every piece of code in the processing loop has to run within its given timeframe or it will get terminated or causes a complete FC stall. If ANYTHING in INAV would cause exorbitant CPU load to cause issues, your Aircraft would crash and MSP would not work at all. Does not matter if armed or not. — Reply to this email directly, view it on GitHub<#182 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/APRK6SXLPCSYWCVQ22EBCO32F75T5AVCNFSM6AAAAABSY57YGOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJZGE3DCNI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[stronnag]

2024-12-17 Installer

Installer 2024-12-17

• Addresses issue with Line of Sight (LOS) failing on locales that use "comma" (,) , vice "period" (.) as the decimal separator.
• Includes locale info and numeric formatting sample in the mwp_stderr* log to assist in tracking down any similar instances

If anyone is still having issues with LOS, please:

• Ensure you are using the 2024-12-17 installer (or build from Github for other platforms)
• Run mwp with `--debug-flags 512'

  mwp --debug-flags 512
  

• Provide the mwp_stderr_YYYY-MM-DD.txt log file in any failure reports.

[stronnag]

2024-12-22 Installer

Installer 2024-12-22

• Rework Windows serial I/O (again ...)
• Rework Line of Sight
  • Improve visualisation (appearance and efficiency)

The above changes may help with issues when connected via MLRS (which I'm unable to reproduce).
MSP polling during LOS Analysis is enabled again; it may be disabled by setting the environment variable MWP_LOSA_PAUSE_POLLER (to anything).

Testing / test reports appreciated.

• Enable LOS and MSP debug: mwp --debug-flags 516
• Set MWP_LOSA_PAUSE_POLLER if you have issues without it.
• With "pause polling" during LOS Analysis: mwp --debug-flags 516 MWP_LOSA_PAUSE_POLLER=1

In order to run mwp from a shell (e.g. powershell)

PS C:\Users\win11> $env:Path += ";C:\Program Files\mwptools\bin"
PS C:\Users\win11> mwp [options]

• Please provide the mwp_stderr_YYYY-MM-DD.txt log file in any failure reports.

[stronnag]

LOS / Win10 / Low b/w serial link active in background (HC12 433MHz telemetry radio, 9600 baud).

los.mp4

• No MSP timeouts
• No errors/ timeouts in console log
• Relatively smooth LOS visualisation

[fatbaldmen]

Issue with hc-05 using telemetry mirror from jumper t15. Mwptools is not reading flight pack voltage. It's seams to read the current just fine. Sensor in edgetx is read as "rxbt". Which give the flightnpack a value of 16.5v at the time. I am not sure if this is just a product of telemetry mirror (crsf protocol). Is there a way to get Mwptools to see this sensor. Connecting straight to the fc, i get the flight pack voltage showing in Mwptools.

[stronnag]

Regardless of Github's terminology, there are no releases of mwp, just occasional snapshots for those who don't wish to build from source. The timing of such snapshots is non-deterministic. But seems to be weekly at moment ...

[stronnag]

You can probably drop the enclosed mwp.exe over the installed version (back it up first), and get CRSF voltage.

mwp-exe-2024-12-29-crsfV.zip

[fatbaldmen]

You my have to speak to me like a child haha. Where do I drop this file into?. Copying it to the mwp folder just gives me errors. Dropping it on top of the shortcut icon gives me 5 errors.

[stronnag]

Replace Program Files/mwptools/bin/mwp.exe (with the mwp.exe from the zip file).

[fatbaldmen]

Sorry for my stupidity. I did not see that in the bin file at first. Replaced, and running. All works well with auto and crsf. Thank you thank you.