EdgeTX
External Module serial connection is not stable.
Is there an existing issue for this problem?
- [x] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
Using the latest code from Nightly build of main (Nov 22). TX16s and Boxer. Using external modules, the telemetry is not working.
Added a bit of tracing and local compile of firmware, seems like is mostly missing the 1st byte of the telemetry stream. but sometimes, can be in the middle. Most protocols have traces to report that we are getting an invalid start of message, so is easy to see in the traces.
Tried with an external multi-module, no telemetry detected. (multiple RXs.. FrSky, DSM, etc) Tried an external DSMP, also no telemetry. Also somone else also reported on Discord similar behaviour with external ELRS.
On the outbound side, i also see corruption of the messages going out in some cases, but that one is more dificult to trace.
Everything works with Internal MM.
Expected Behavior
Telemetry on external modules should work.
Steps To Reproduce
Use an external multi-module. Try to use it.. Sometimes the outboud (sending channels) works, but what is consistent is that the telemetry is not working. Sometimes you have to go back to 2.11.3 to do the bind, and then upgrade back to 3.0, so that the RX is already connected.
With the multi-module, you don't need an external connection, but you will not get the Multi-Module version, that is telemetry between the MM and TX, no external RX needed.
Changing the firmware done with ETX Buddy, so that the bootloader and firmware are in sync.
Version
Nightly (Please give date/commit below)
Transmitter
RadioMaster TX16S / TX16SMK2 RadioMaster Boxer
Operating System (OS)
No response
OS Version
No response
Anything else?
Works well with Multi-Module on 2.11.3
Nightly build from Nov 22, https://github.com/EdgeTX/edgetx/commit/129203c28f8201ec75d25206746bbb709377a414
From some of my local DSMP testing on 3.0 (main)
From Discord using a external ELRS
If you cannot bind with 3.0, go back to 2.11.3, bind the model. Then move to the latest build (3.0). Sometimes the outbound (channel data) works, but has intermittent freezes.. and no telemetry. (Multi-Module).
Confirmed. Just extra information, did test external multi and CRSF modules on H7 hardware, this doesn't happen on those. Is however confirmed on F4
@raphaelcoeffic, since you are very familiar with the Uart code, maybe you have an idea on this one. The easiest way to test is if you have an external multi-module, you will not get the version on the status line.
Ah... one more breaks in 3.0 branch....... Doing a bisect maybe helpful to pin-point which commit cause the problem.
