Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot select or receive S.Port telemetry with external module using SBUS protocol #5944

Open
1 task done
nspector8 opened this issue Feb 25, 2025 · 1 comment
Open
1 task done
Labels
bug 🪲 Something isn't working triage Bug report awaiting review / sorting

Comments

@nspector8
Copy link

nspector8 commented Feb 25, 2025

Is there an existing issue for this problem?

  • I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

While using v2.11.0-RC1 firmware with TX16S mkII radio with RFD TXMOD in external bay, "Sub Type" drop down box opens normally in "External Radio Module" settings page for SBUS protocol, however "SPort" cannot be selected or changed from "No Telemetry".

After powering and connecting FC, RC control is correctly established, radio audibly reports "Telemetry Connected", all sensors are detected and show active (flashing dots) on Telemetry page in Model settings, however no values are presented next to the sensors, and no telemetry is passed through to yaapu. Additionally, an error/crash page presents itself in the yaapu script, which can be seen below.

SBUS RC control and S.Port telemetry with yaapu both still operate normally in v2.9.4 (when rolled back to that version).

ETA: I didn’t try it, but I would suspect that telemetry into Mission Planner 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. In other words, it appears there has never been any issue with the TXMOD sending S.Port telemetry data to MP via TCP/UDP over wifi.

Expected Behavior

Expected behavior is that telemetry values are detected and shown in the radio, and then passed through S.Port to the yaapu script in order to be utilized.

Steps To Reproduce

  1. Power on TX16S mkII running v2.11.0-RC1 and latest yaapu telemetry script (v2.0.0 beta3), with RFD TXMOD 2.0 in external bay.
  2. Power on aircraft/FC with connected RFD modem (RFD900ux in my case).

Version

2.11.0-rc

Transmitter

RadioMaster TX16S / TX16SMK2

Operating System (OS)

No response

OS Version

No response

Anything else?

This issue has also been discussed and worked on in issue #5064 and fix #5689.

Screenshot of yaapu error:

Image

@nspector8 nspector8 added bug 🪲 Something isn't working triage Bug report awaiting review / sorting labels Feb 25, 2025
@rccam
Copy link

rccam commented Mar 4, 2025

Same for me with unpossibility to persist Sport as telemetry when external SBUS module used.

Also for UI enhancement there is weird behawior when none option is available in some popup list so list is completely invisible but still all screen is treated as background so dimmed. (That happening in lots of situations but for example also when testing that bug when for trainer mode is set Master/Sbus Module there is no option on list for External RF Mode)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working triage Bug report awaiting review / sorting
Projects
None yet
Development

No branches or pull requests

2 participants