R9M telemetry receiving

[sky-ozone]

Hello Jonathan,

I was trying to forward telmetry receiving from R9M via USB VCP ( edgeTX Radiomaster tx16). I am using mLRS. I can see telemetry on webinter face , but in the bottom of mwpTools i receive CRSF Manual . Also after 20 s, i receive small popup of No Data counter for 5seconds. In the log also i do not find telemetry data . Is it because it inverted format? but then how mwptools show gps data on the UI and some other data like voltage, Alt. etc... Thank you.

[stronnag]

1. Please create a raw log with mwp --raw-log and post that here
2. Please also post the mwp_stderr log from the same session

see the user guide, note carefully the last sentence of that section.

[sky-ozone]

Here are the logs attached. Thank you.
Screenshot 2025-07-28 222753.zip

[stronnag]

No, you sent me a msp JSON log, not the raw log.
There is no evidence that you even attempted to generate raw (it would be recorded in the stderr log if you had done).
Last chance ....

[sky-ozone]

attached.

mwp.COM11.2025-07-28T230803.zip

[stronnag]

If I replay your raw log, it seem fine. I get positional data, LQ, heading, attitude, altitude, voltage, current etc.
There is the "no data" message which means no MSP/LTM (and I should probably fix, it's a relic of older times).

# In one terminal:
$ mwp --no-poll -d udp://:3000
# when mwp loads, click  "Connect"
# In another terminal

$ mwp-log-replay -d udp://localhost:3000 mwp.COM11.2025-07-28T230803.raw 

data looks fine in mwp.

Likewise, running mwp's CRSF parser, I see a couple of new CRSF messages mwp doesn't handle, seems like the flight mode may be a bit different from some other samples, but everything else looks fine.

$ crsfparser mwp.COM11.2025-07-28T230803.raw
...
   0.45s: LINKSTATS: rssi1 211 rssi2 0 UpLQ 100 UpSNR 0 ActAnt 0 RFMode ??Hz TXPwr 100mW DnRSSI 216 DnLQ 100 DnSNR 2
   0.45s: UNKNOWN: Type 29 0x1d, payload len 6
   0.45s: UNKNOWN: Type 28 0x1c, payload len 5
   0.45s: BAT: 15.70V 0.50A 46mah 71%
   0.49s: GPS: 61.439877 23.892466 5m 0.0m/s 83.1° 7 sats
   0.49s: ATTI: p 5.70 r 0.80 y 213.00
   0.50s: LINKSTATS: rssi1 223 rssi2 0 UpLQ 100 UpSNR 0 ActAnt 0 RFMode ??Hz TXPwr 100mW DnRSSI 229 DnLQ 100 DnSNR 3
   0.50s: UNKNOWN: Type 29 0x1d, payload len 6
   0.50s: UNKNOWN: Type 28 0x1c, payload len 5
   0.62s: GPS: 61.439877 23.892466 5m 0.0m/s 83.1° 7 sats
...

I should have a look at the missing messages, but fundamentally, it looks sane.

So what's the problem??

[sky-ozone]

THe problem I face is , There is no GPS info in telemetry log file , see below,so tracker does not receive any data ( Dlink )
{"type":"environment","utime":1753730837.196301,"host":"Windows 10.0 (26100) via msys2","mwpinfo":"7f26d496 (master) / 2025-07-05T08:15:59+01:00","mwpid":"25.07.05"}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"analog2","utime":1753730837.196301,"voltage":15.800000000000001,"power":0,"rssi":1023,"amps":0}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"analog2","utime":1753730837.196301,"voltage":15.800000000000001,"power":0,"rssi":1023,"amps":0}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"analog2","utime":1753730837.196301,"voltage":15.800000000000001,"power":0,"rssi":1023,"amps":0}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"armed","utime":1753730837.196301,"armed":false,"flags":0,"sensors":0,"telem":false}
{"type":"analog2","utime":1753730837.196301,"voltage":15.800000000000001,"power":0,"rssi":1023,"amps":0}

[stronnag]

THe problem I face is , There is no GPS info in telemetry log file , see below,so tracker does not receive any data ( Dlink )

That there is no data in the JSON file is irrelevant.
Only MSP, LTM and MAVLink messages are forwarded (at the moment).
I've been thinking about also enabling CRSF to be forwarded, that will probably happen in the next day or so.

[stronnag]

So your CSRF sends ACRO* while other example send just ACRO. Wonderful ....

[stronnag]

Done. the development branch can forward CRSF out as MSP, LTM or MAVLink. That was easyish.

[sky-ozone]

Thanks Jonathan. That was quick .