Geting mwp working with ELRS CRSF telemetry from a BT USB Adapter

[Pelado-Mat]

Im currently using Telemetry APP to display telemetry on my phone, but I would like to use my PC too.
My setup is a RM Zorro ELRS with a non-BLE BT Module on AUX 1 configured as telemetry mirror. It works fine with the app.

I'm trying to use mwp with the same setup, but the telemetry never gets into mwp:

2024-04-10T15:55:59-0400 Try connect 0B:3A:0D:12:54:45 RM Zorro@115200
2024-04-10T15:55:59-0400 Connected 0B:3A:0D:12:54:45 RM Zorro@115200
2024-04-10T15:55:59-0400 Serial ready
2024-04-10T15:55:59-0400 Comm error count 34
2024-04-10T15:55:59-0400 expected header0 (ea)
2024-04-10T15:55:59-0400 Comm error count 35
2024-04-10T15:55:59-0400 MAVCRC Fail, got 64e3 != f805 (cmd=234, len=119)
2024-04-10T15:56:00-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:01-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:02-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:03-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:04-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:05-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:06-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:06-0400 Comm error count 36
2024-04-10T15:56:06-0400 fail on header1 ea
2024-04-10T15:56:07-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:08-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:09-0400 Comm error count 37
2024-04-10T15:56:09-0400 MAVCRC Fail, got dea != 6fc5 (cmd=238, len=234)
2024-04-10T15:56:09-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:10-0400 MSP Timeout (MSP_CMDS_IDENT)
2024-04-10T15:56:10-0400 Comm error count 38
2024-04-10T15:56:10-0400 fail on header1 ea

I tried to follow the online manual, but can't find how to force CRSF telemety.

[stronnag]

I have a RM Boxer here with ELRS and it works OK, using EdgeTX TELEM Mirror and the Boxer USB port.
Telem mirror also works with a TX16S, BT and either Frsky or IBUS.

Can you please capture the raw data by running MWP from the command line as:

mwp --raw-log # and anything else you wish

This will create a file in the current directory, for example mwp._dev_ttyACM0.2024-04-10T210403.raw (i.e some combination of mwp, device name and date, .raw.

Post that file here, together with the full mwp_stderr file (not some subset).

[Pelado-Mat]

Hope it helps.
Im running EdgeTX 2.10rc3, the BT Module is working an 115200 bauds

mwp_stderr.txt
mwp_2024-04-10_161556.raw.txt
mwp_2024-04-10_161547.log
mwp_2024-04-10_161533.raw.txt
mwp_2024-04-10_161315.raw.txt
mwp_2024-04-10_161203.raw.txt
mwp_2024-04-10_161054.raw.txt

[stronnag]

Final chance. A complete, unadulterated ~/mwp_stderr_2024-04-10.txt. Otherwise I'm not prepared to play guessing names.

[Pelado-Mat]

Sorry, I did not get that the program created that file. Here is attached.

mwp_stderr_2024-04-10.txt

[stronnag]

Thank you.
Could you also record some longer raw data? Like several minutes. And ensure there is more valid telemetry from the radio?

I ran all 14s of mwp_2024-04-10_161054.raw.txt through mwp's crsfparser tool, see attached log: crsf.log

There's not much useful for mwp here, but attitude, RSSI and flight mode are recognised and (see below) displayed.

The log was then replayed into mwp (today's github master branch (for which --no-poll works correctly)).
Having first started mwp as:

mwp -d udp://:3000 -a --no-poll

And selected the CRSF filter before replaying the logged data:

mwp-log-replay -d udp://localhost:3000  /home/jrh/dl/mwp_2024-04-10_161054.raw.txt

So as far as I can see:

• The data is decoded and displayed correctly.
• There's not such data to test
• There's little useful in data (no useful GPS or VBAT for example)
• Selecting the CRSF filter will help

[Pelado-Mat]

That's weird! on my PC I cannot select CRSF. I swa it on the docs but assumed it was an old screen capture

So as far as I can see:

* The data is decoded and displayed correctly.

* There's not such data to test

* There's little useful in data (no useful GPS or VBAT for example)

* Selecting the [CRSF filter](https://www.daria.co.uk/mwptools/mwp-multi-procotol/#auto-detection) will help

[Pelado-Mat]

Well I find the problem.... I had installed in my ~/.local an really ancient mwptools version 4.x. I really do not remember when I did that...

mwp f23d52f / 2021-08-15T10:45:24+01:00 4.227.350 on Wayland 

I now remove it and reinstalled the .deb from the releases page. After fighting with dconf I finally could connect!

Sorry for the time spent and thanks for all the help.