EdgeTX
RadioMaster TX16S Screen and Audio Hang with Many Mixers
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
My radio will occasionally hang, the screen and audio freezing. This is noticeable as I'm running timers for F5J glider competitions and I'll hear the timer stop. The model is still controllable, and all the surfaces move. Additionally, opening the Mixers page on the Model takes 3-4 seconds. Here is a RCGroups topic with a few of us commenting about this: https://www.rcgroups.com/forums/showthread.php?3493859-RadioMaster-TX16S-16Ch-2-4ghz-Multi-Protocol-OpenTX-Radio-System/page1091#post53553273
Here are the steps I've taken to try to isolate the issue: Used a brand new SD card and installed the clean EdgeTX SD card contents. Then I copied over my models, scripts, model images, my custom glider sounds. Upgraded through several EdgeTx revisions/versions. I'm running ExpressLRS on Ranger Micro with the latest firmware upgrades to both the Tx and Rx. I've tried removing the ribbon cables, cleaning with IPA, and replacing them. I'm flying with a fairly complex template with a lot of curves, logical switches, global variables, etc. This is from the F5J templates on rc-soar.com. I've not been able to fix it, and the problem usually occurs in a few hours of flying. I did replace the onboard battery, the CR1220. Changed to my spare TX16S MKII transmitter with a different Ranger backpack. Disabled the ShowItAll widget.
None of these tests fixed the problem, and someone else also has hanging problems. I don't get any error on the radio screen, just the audio hangs, and after the audio comes back, the timer tries to count down fast to catch back up.
To me it feels like the radio CPU is overloaded and gets stuck. I can't help wondering if the complex F5J template I'm using is too much for the radio?
Expected Behavior
For timers etc not to freeze.
Steps To Reproduce
RadioMaster TX16S MKII running Edge 2.10.6 Install my SD card from link below - select models Eternity B or Eternity C or Eternity Light Try opening Mixers on the Model page - takes 3-4 seconds to open. The problem with freezing audio can take a few hours of flight to turn up, and the sound including timers and special function callouts freezes and no audio is produced for a period of time lasting roughly between 5-60 seconds.
Version
2.10.6
Transmitter
RadioMaster TX16S / TX16SMK2
Operating System (OS)
No response
OS Version
No response
Anything else?
A zipped copy of my SD card is here:
https://drive.google.com/file/d/1CDhex4t9lQnqZD3zQr08_xsiWDeDldtv/view?usp=sharing
I caught the bug happening on video here: https://drive.google.com/file/d/17djjQx3TVsvWlX07fQ9y7DziQCaT6mX-/view?usp=sharing
I've managed to replicate the "switch hang" issue on my TX16S running ETX 2.10.6, running the basic template. Though in my case it happened a few moments after switch on.
I've just been away in Larissa Greece for 10 days of full time practice and competition F5J gliding, and had the issue multiple times on both of my TX16S MKII radios. Sometimes it was a partial loss of sound, so a timer might reach 6m34s, but I'd hear "minutes seconds" and no numbers. Mostly it was the classic audio and screen hang as I've described at the start of this issue. At least I came 2nd in the first EuroTour competition of the season. I can work around the sound/timer issue as I can ask the person coaching me what time remains, or look at the timer board myself, but it's not ideal as it adds workload when I should keep my mind free for thermalling and tactics.
I've upgraded one of my radios to 2.11.0 and the issue is now far worse, to the extent that when powering on the radio the welcome wave file: "Welcome to EdgeTx" hangs partway through and the radio is locked for a while before the boot eventually completes. It's really bad.
Try opening Mixers on the Model page - takes 3-4 seconds to open.
This is more or less known and yes, due to the complexity of the model. We probably need to come up with a way to make this more direct.
The problem with freezing audio can take a few hours of flight to turn up, and the sound including timers and special function callouts freezes and no audio is produced for a period of time lasting roughly between 5-60 seconds.
Ok, so while flying, everything is behaving normally, and on a few occasions audio and callouts will just stop working properly for up to one minute. Do I get that right?
When you write "can take a few hours to turn up", that means it will work normally for multiple hours, and then happen, right? Anything special right before?
upgraded one of my radios to 2.11.0 and the issue is now far worse, to the extent that when powering on the radio the welcome wave file: "Welcome to EdgeTx" hangs partway through and the radio is locked for a while before the boot eventually completes.
Ok, does this happen on every boot with 2.11.0? Once boot completed, do things work normally?
I've managed to replicate the "switch hang" issue on my TX16S running ETX 2.10.6, running the basic template. Though in my case it happened a few moments after switch on.
What is the "switch hang" issue?
I've managed to replicate the "switch hang" issue on my TX16S running ETX 2.10.6, running the basic template. Though in my case it happened a few moments after switch on.
What is the "switch hang" issue?
It's been a while now, but as I recall shortly after switch on, sounds linked to flight modes were not sounding as I switched between fm's. It was as if the UI had frozen. It must have lasted around 5 seconds, then back to normal. This was without a model. This was with the basic E-Soar Plus (F5J) setup during a one off test to try and replicate the issue (I am not using the TX16S/ETX combo on a regular basis).
I've upgraded one of my radios to 2.11.0 and the issue is now far worse, to the extent that when powering on the radio the welcome wave file: "Welcome to EdgeTx" hangs partway through and the radio is locked for a while before the boot eventually completes. It's really bad.
Then I would suspect your SD card. Here is your SD content on a tx16s flashed with 2.11 (using buddy)
In my case using a freshly installed ETX 2.10.6. Sandisk Ultra card. Is there any mechanism other than physical SD card failure for this kind of UI freeze?
Let's try not to mix issues, I was responding to @BasculethiTellur that had a simple to replicate scenario, but I would suspect sd first in those similar scenarios. As can be seen in my video, replicating his scenario with his sd content works perfectly fine here
@RC-SOAR @BasculethiTellur
We introduced recently a new debugging tool to our arsenal, and I had a look at the model shared. I noticed that the radio never idles, and actually spend most of its time in the menu task, dealing with display. So I created a second empty screen, and when switching to this screen, everything looks much nicer system usage wise. Could you try something similar ? maybe switching to a nearly empty screen when you arm or something. It would be very interesting to know if this fix your issue
Sure, I’ll try that. Do you mean the widget/display screen? I should make a second telemetry screen that is blank and use this whilst flying to reduce CPU load and see if I can generate the bug condition?Sent from my iPhoneOn 25 May 2025, at 10:52, 3djc @.***> wrote:3djc left a comment (EdgeTX/edgetx#5976) @RC-SOAR @BasculethiTellur We introduced recently a new debugging tool to our arsenal, and I had a look at the model shared. I noticed that the radio never idles, and actually spend most of its time in the menu task, dealing with display. So I created a second empty screen, and when switching to this screen, everything looks much nicer system usage wise. Could you try something similar ? maybe switching to a nearly empty screen when you arm or something. It would be very interesting to know if this fix your issue
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
Many thanks for looking at this. It’ll be a while before I can check with a blank widgets page though, as I’m on holiday and only have my B/W radios.
On Sun, 25 May 2025 at 22:43, 3djc @.***> wrote:
3djc left a comment (EdgeTX/edgetx#5976) https://github.com/EdgeTX/edgetx/issues/5976#issuecomment-2908070550
Yes exactly 👍
— Reply to this email directly, view it on GitHub https://github.com/EdgeTX/edgetx/issues/5976#issuecomment-2908070550, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABQGLJZBJYHJMRS3FE427Y33AITO3AVCNFSM6AAAAABYRNB7N2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBYGA3TANJVGA . You are receiving this because you were mentioned.Message ID: @.***>
Yes exactly 👍
OK, I've done quite a lot of testing and fiddling, and have found the following: If I put a blank screen for telemetry, so that no widgets are in theory running, I still get the sound bug. Admittedly it seems to be shorter lasting and less often. If I delete all the widgets out of the /WIDGETS/ folder, I get much the same.
Last week I tried to work with a clean radio and clean setup: Flashed my spare TX16S MKII to Jolly Mon 2.11.1 Took a spare SD card with a 1GB partition, and formatted it with FAT32 4kb Applied a fresh downloaded SD card contents to that SD card (via direct download of the SD card and sound files for EN_Libby) Added ELRS lua v3 Downloaded latest Companion 2.11.1 Downloaded fresh version of ESoarPlus 3.10. Opened esoarplus_310.otx in Companion 2.10 and saved as .etx Opened that converted .etx in Companion 2.11.1 and altered camber to RS and motor to LS. Special function disable touch set to on. Timers configured Sound files from ESoarPlus 3.10 copied to SD Card Channel Change script downloaded and CH5/6/7 moved to 6/7/8 CH5 set to ARM ELRS (always armed). Bound this model to an Rx (ER8GV) Instead of my normal use of a momentary switch to play the timer, I set a special function to play the timer 1 every 10 seconds. That lets me run the radio on my desk at work and listen to it. You quickly hear any hang. I also created a new blank model with no config and no timers.
Results So far I've had a number of relatively brief hangs of the screen and audio, usually less than 10 seconds, sometimes more. Also had one where the timer number would not be called out - eg. 10 minutes would be read as "minutes" with the 10 not being said at all. With 2.11.1 Jolly Mon the Tx hangs on boot randomly. It was doing it every time, and then I swapped models a couple of times, and it stopped doing that. This hang lasts from 10s to over a minute randomly. The Tx also sometimes hangs when you switch from the new blank model to the ESoar Plus model. Having a blank screen with no widgets at all does not improve matters. I then put some of the basic widgets in to show RxBat, timers, TQly and RQly, 1RSS and 2RSS.
To be clear - Mike Shellim's template works fine on OpenTx, so the radio is quite clearly able to handle the fairly complex template. It's only EdgeTx that has this bug. Mike Shellim's template is a well written and very developed template used by a lot of pilots including at world championship level for F5J; this is not amateur work. https://rc-soar.com/edgetx/setups/esoarplus/index.php
The one thing I haven't yet tried is to swap to an FrSky receiver and use the internal 4-in-1 module and see if that makes any difference. (I'm currently running ELRS ranger micro backpack and ER8GV Rx).
Additional observations: Flying my "production" radio at Malvern, and I got a time when only a fraction of the soundfile was being played. There's a video showing this. When changing SA between Thermal, Cruise, and Speed, I'd hear only "The", "Cru", or "Sp".
Ok, I left yesterday afternoon the radio using your SD content and adding a SF that read time every 10secs. Impossible to replicate. Almost drove me mad listening to clock announcement.
Then this morning I decided to copy the very same content on a crap SD, and boom, go it right away, and really bad.
So it is SD card related, which is not a good news
Ok, I left yesterday afternoon the radio using your SD content and adding a SF that read time every 10secs. Impossible to replicate. Almost drove me mad listening to clock announcement.
Then this morning I decided to copy the very same content on a crap SD, and boom, go it right away, and really bad.
So it is SD card related, which is not a good news
I have the same results with all of my SD cards. These are the cards I'm using, although I tried some other brands too: SanDisk Extreme 32 GB microSDHC Memory Card + SD Adapter with A1 App Performance + Rescue Pro Deluxe, Up to 100 MB/s, Class 10, UHS-I, U3, V30, Red/Gold
What card do you suggest I try, and how should I format/partition the card?
Formating is easy Fat32 (NOT exFat). As for the card itself, it's a real pain as there are so many fakes around, even when purchased for places like Amazon or such. From the feedback we are getting, I would avoid any 'endurance', or heavy usage focused card (we are actually very gentle on write usage) as those include a lot of anti wear techniques that sometimes interfere with our usage
I used an external card reader on my Mac to copy your full sd content, and on the 'bad' card it took several minutes, and on the good one 25s about.
Here are the two ones I used:
Right came with a radio (don't have any idea which brand or model radio that was), the other was purchased from Amazon. But the difference is obvious using those, and the right one exhibit it nearly instant, when I was unable to replicate it with left one.
We will try to see if we can gain some understand of what is happening with the 'bad' card
OK, thank. I've ordered a couple of different brands, including the one you've used above. Let's see. I will point out that this is an intermittent error, so it may well not be the SD card and it may be that you just didn't run the test for long enough. In the flying field I can sometimes be flying for a couple of hours before the problem shows up.
Well the bad exhibit it very quickly,and consistently while the other, same radio same everything doesn't (or very rare does, I grant you that). That's enough to say it is sd related
I believe I suffer from a similar issue on the same radio. Mine has a sever delay when selecting the model or starting the radio with the model selected (Esoar 3 plus template). I tried removing all specific sound file and disabling all SF them in the model. It then is much faster. Also the startup delay is very irattic. sometimes 6 minutes and if I reboot directly, it can take 25 secunds to show the main dahboard.
I downgraded to 2.10.6 and all seems fine. Fairly sure it is not just an SD card issue.
For info, there are 9 custom audio files in E-Soar Plus, all are 16KHz, 16 bits, 256 kb/s, 1 channel, PCM. They vary in size between 13 KB and 46 KB
Thanks Arthur! Yes, I concur, it's not an SD card issue. I've had the same problem on @3djc 's suggested card above, a Lexar one, and a Transcend one. I bought a bunch more to try to eliminate this suggested cause. Plus before this I've used 4 different Sandisk gold and 1 Sandisk Silver. This bug occurs with all of these cards.
Given that the template works flawlessly on OpenTx, I suspect that EdgeTx is using resources in some way that overloads the RadioMaster when there are this many mixes, logical switches, curves, special functions etc. I'm told someone experienced the problem on a GX12 too.
I started a discord thread before when I was not aware of this bug report: https://discord.com/channels/839849772864503828/1380649776625881150
For info, there are 9 custom audio files in E-Soar Plus, all are 16KHz, 16 bits, 256 kb/s, 1 channel, PCM. They vary in size between 13 KB and 46 KB
I'm using a modidfied Esoar Plus F5J template on my Radiomaster Pocket with an extra audio file (10s countdown) that is rather large (> 500kb) and have not had any such problems so far. Could it be that this only happens with ELRS?
I'm using a modidfied Esoar Plus F5J template on my Radiomaster Pocket with an extra audio file (10s countdown) that is rather large (> 500kb) and have not had any such problems so far. Could it be that this only happens with ELRS?
So far the reports I've seen all refer to colour screen radios. No reports that I'm aware of this happening on mono screen radios, which also run ELRS.
As the Bug is for me not present in the 2.10.6 (I downgraded) but is present in 2.11.1, I assume it is an ETX bug. @BasculethiTellur can you confirm that for you the bug disapears if you downgrade to 2.10.6?
Also, an earlier version of eSoar plus with an F5J model in it (and 6 wing servo's) does not suffer from this in either version.
Just back from holiday, and have have just replaced OpenTX 2.3.15 with EdgeTX 2.11.1 on my spare Eachine TX16S to see if I could replicate this issue once again. This time I loaded my 6-servo F3F sailplane setup. A few minutes after switching on with the new setup, the UI froze for a few seconds while I was selecting a source in the Inputs editor. It then recovered. It feels like the UI is pausing for breath. The same setup as has been running on a Pocket without issue for several sessions, running ETX 2.10.6. Also fine on my TX16S running OpenTX 2.3.15.
What happens is that you hit a 5 seconds timeout delay on low level SD routines provided by STM. This freezes the UI and audio tasks for 5 seconds (mixer is totally unaffected), then recovers from it. It is 100% SD related, is not directly related to the complexity of the model (as in mixer lines), but obviously is scalling with the number of sd accesses (sounds, logs,...)
While we know exactly what happens, it is a very different story to understand why it happens, since it happens very infrequently, and been able to log this type of event is a bit beyond the capabilities of the equipment we have and also the ressources we have.