No telemetry after EdgeTX 2.10.0 firmware update

Hardware Radios
1

After updating my TX16S mkII to EdgeTX 2.10.0, loading all default SD contents for 2.10.0, and reinstalling yaapu following “Installation on Horus radios”, no telemetry is being detected by the radio or shown by yaapu, however the RFD TXMOD in the module bay is still able to send all telemetry to Mission Planner over WIFI via TCP.

The yaapu widgets display correctly in the radio but no telemetry.

Attempted “Delete all” and “Discover new” in telemetry settings but nothing appears to be coming into the radio. Also no “telemetry connected” message as described in the summary of changes since v2.9.

Rolling firmware back to EdgeTX “Providence” v2.9.4 results in telemetry restored into both radio and yaapu.

Any of you having a similar problem?

2

Hey Mike thanks for this heads up, yes i think i have the same problem.
No telemetry after update to 2.10.0. i have been pulling my hair out trying to get the rfd900x / txmod going with yaapu and now i have a lifeline!
i will update to previous version and hope it works
Thanks for your help

3

For what its worth I am using 2.10.4 with yaapu without issue.

4

Hi Andy, are you using an external module with SBUS? The issue was found to be specific to this circumstance.

The EdgeTX developers made a fix which will have external modules with a drop-down sub type box for selecting telemetry type for use with PPM and SBUS, but I don’t believe that it’s been included in an official release, but probably in the next after v2.10.5.

Fix 5689

5

I am using an external module with CRSF.

6

I tried the latest EdgeTX version 2.10.6 and could not get telemetry working between the TXMOD and Yaapu.
Rolled back to 2.9.4 and all OK again. I did have to do the hardware calibration in the radio and set a couple of pots and sliders to the correct type.

7

I’m on 2.10.5 without issue. I suspect problems of this nature stem from avoidance of “dev” or “latest” releases of the Yaapu suite.

8

Mine shows Yaapu Telemetry Widget 2.0.x dev (6cccb30)
The radio is TX16S Max with TXMODv2

Last time I went through this dance I had tried reloading and setting up Yaapu, but it was the same story - no telem

9

May need to go back through setup and rediscover sensors + make sure CRSF support is still enabled.

I’ve noticed some quirks, but I’ve never failed to get it working.

My firmware hash is 1997425 with the same 2.0.x dev tag. TX16S Max with external JR bay ExpressLRS module and no mods of consequence to telemetry.

10

We dont use the CRSF option with the TXMOD, it’s more like Frsky telemetry in the backend I believe.
I’ll give it another shot when I feel so inclined.

The fix is meant to have a telemetry option after selecting SBUS or PPM for the output type, which we dont see yet.

1 Like
11

The TXMOD seems to be the difference here, and I have no experience with that. Wish I could be of more help.

12

I recently tried v2.11.0-RC1 but still not working.

I opened an issue on the EdgeTX github that gives the details of what my experience was with that firmware.

13

Yep…the dropdown in SBUS to select telemetry is present since 2.11.0-RC1, but for me the “SPort” option is grayed out and can’t be selected (stays on “No Telemetry”).

The radio will audibly alert “Telemetry Connected”, and you can see the sensors being detected, but no values are reported in the radio or in yaapu.

I didn’t try it, but I would suspect that telemetry into MP is working normally as it has for all of the previous EdgeTX firmware versions back to v2.9.4, where everything, including yaapu works correctly. There doesn’t seem to be an issue with the TXMOD sending the telemetry data to MP via TCP/UDP over wifi.