ETX 3.0 UI feedback(s)

[MrBlackmidi]

Starting here with feedback from Jonas Wackershauser https://discord.com/channels/839849772864503828/839849772864503832/1425443448651255818

I personally haven't tried the UI for ETX 3.0 myself since I don't own a radio yet (will be coming soon™)

[pfeerick]

If you want to give it a try in the meantime, you can always grab a successful build of Companion from the main development branch, and use the simulator ;)

For the latest version testing version of Companion, from the link below for your preferred operating system, pick the most recent successful build (will have a green checkmark next to it). On the resulting page, the link to download the installer package is under the Artifacts heading near the bottom.

Companion (main branch):

• Windows => https://github.com/EdgeTX/edgetx/actions/workflows/win_cpn-64.yml?query=branch%3Amain
• Mac => https://github.com/EdgeTX/edgetx/actions/workflows/macosx_cpn.yml?query=branch%3Amain
• Linux => https://github.com/EdgeTX/edgetx/actions/workflows/linux_cpn.yml?query=branch%3Amain

[andika207]

@pfeerick well done.
the FLYSKY PL18U and the IFLIGHT C14 are still missing though
on the other hand the HELLORADIO V12 has not been officially released yet and it will be based on the F4 crap !!!
I want to guess that ETX dev team won't develop or maintain the firmware for it. https://edgetx.org/supportedradios/

[pfeerick]

C14 is not supported by EdgeTX (yet), hence why not on the list. Thanks for catching the PL18U. The V12 information is outdated and will be removed until the radio is launched. There is nothing wrong with F4 hardware, it is still perfectly capable.

[andika207]

@pfeerick EdgeTX is lightweight so any CPU should do the job but when loading badly optimized LUA scripts it will struggle and the screen lag will be noticeable when sliding the screen menus left and right
Frsky ETHOS is driven by the H7 processor however sometimes it freezes or hangs on start up with multiple bitmaps
I wonder if EdgeTx in the future will benefit from multiple core CPUs
https://www.youtube.com/watch?v=ax-quxn8KKk&feature=youtu.be

[andika207]

@pfeerick you can list the V12 back now that we know for sure that it features a H7 MCU
https://www.youtube.com/watch?v=Uubtl2cLIC4
I have read of somebody asking HELLORADIOSKY for a fix for the V16 but he's been ignored and this is the down side of a Tx without official support from ETX team, it's pretty much kind of buying an obsolete Eachine TX16s

[pfeerick]

Now that there is public information about it from the manufacturer I can. They hadn't mentioned yet that it was public though, so thanks for sharing the video. And yeah, that's the potential hazard of a manufacturer supported radio rather than one supported by the project proper. It would be interesting to see this issue though. Do you still have the link for it?

[MrBlackmidi]

Tried it out yesterday, nowhere near as bad as I thought (prolly because I won't use the touchscreen as I have kind of fat sausage fingers (though hopefully we can have UI scaling one day)). I am not disregarding Jonas' feedback on the 3.0 UI, just wanted to have my opinion on this.

[n4t3y]

On TX15 running the 15/10/25 radiomaster firmware, so not sure if this is the fully current implementation of the 3.0 UI.

screen-2025-12-09-201855.bmp

There doesn't appear to be a "close" button for the black menu, however when you press on the top right hand corner, it exits from the black menu.

[pfeerick]

so to exit completely you need to press it twice.

If you are two levels deep, long press RTN to exit ;)

so it is clear to the user that they have exited out of that second level of menu.

The second level greying out, and the selection cursor/box moving back to the top level isn't enough in your opinion? What do you think should happen when you then scroll to the next top level entry... should it not show the second tier greyed out (meaning you can't see what entries are there without actively selecting it first?

[n4t3y]

If you are two levels deep, long press RTN to exit ;)

Ah that makes sense

The second level greying out, and the selection cursor/box moving back to the top level isn't enough in your opinion? What do you think should happen when you then scroll to the next top level entry... should it not show the second tier greyed out (meaning you can't see what entries are there without actively selecting it first?

Ok so I haven't really played around with it too much but it does actually make sense the way it works currently when you use the scroll wheel to go between the first level menus. I think the confusing thing is that the model select second level is blank compared to the other menus and so it seems like the others should be blank as well until you select them but it does make sense now the way it is currently.

[pfeerick]

Indeed... I wonder if it makes sense for that to show models from your favourites / most recent (I think we have capability but perhaps not implementation for that) + an entry to select a model... thus making the mange model section exactly the same as the others. Perhaps also with a LONG_ENTER shortcut if you want to do that right from the upper level (or just rely on the long MDL shortcut for faster access to manage models).

[n4t3y]

Yeah that might make it seem a bit more uniform compared to the other menus. I also have noticed that when you go into the model selection, then back into the black screen menu, when you then exit out of the black screen menu, you are taken back to the model selection menu rather than the model home screen. I understand that this is probably because the model selection screen is a completely different type of menu compared to the various settings menus but the way that works currently is not super logical.

[pfeerick]

If I understand the sequence correctly... that would be expected... you are closing the menu, not exiting the underlying screen... i.e. if you go to model setup -> mixes, then bring up the menu (touch the etx logo or press SYS) ... change your mind so touch anywhere across the top "EDGETX" banner / long RTN to close the menu... you are back/still in model-> setup mixes... the menu pops up over the current screen, not replaces it. Same for model select / manage models, etc.

[pH7-JP1]

My TX15 came with an original 3.0, but I needed to update in order to specify a 3-POS shoulder switch. Now I am coping with this new main menu. I hope this is just some intermediate stage because this is very inconvenient to use.

1. When you are already in one of the Model Setup menus (for example "Inputs") and you want to switch to another (for example "Logical Switches") I used to be able to press RTN and then tap "Logical Switches". Now the RTN takes me all the way out. I need to tap the "EdgeTX" then "Logical Switches".
2. Even more irritating, from any of the Model Setup menus I used to be able to press MDL to immediately show the channel monitor screen and exiting the monitor screen brought me right back to were I was. Now if I want to check the monitor screen: RTN, Tools, Channel Monitor [was 1 button press, is now 1 button press and 2 taps] and then to get back to where I was: RTN, EdgeTX, Model Setup, then the menu I was in [what was 1 button press is now 1 button press and 3 taps]. This is terrible. If I were using the scroll wheel instead of the touch screen it would be even worse.

[pH7-JP1]

Just a suggestion - If you are in the monitor, could a long press TELE just return to where you were? (It does nothing now.)

[pfeerick]

Ok, so the catch 22 with the UI for 3.0 is that you will be able to choose where the long and short presses of SYS/MDL/TELE keys take you. So, for consistency of behaviour, the shortcut of MDL for channel monitor had to go... So, the situation is "if" you have a long press of TELE assigned to channel monitor (which I will be proposing should be changed to a short press now that the end user can reassign what they keys do if they prefer the old behaviour due to muscle memory, etc), will a repeat press of that button combination take you to where you where before... and just for the channel monitor?

[pH7-JP1]

For any of these 6 user definable button assignments, if the screen is already where the user assigned, what should happen? It seems to me that the only logical answers are 1) stay on that screen (i.e. do nothing) or 2) return to the previous screen. I suppose that the user could, for each of these, choose between those 2 options of what to do if we are already on the requested screen.

[zsdr-bln]

repeat press of that button

Return to previous menu screen seems more logical to me 👍

[pH7-JP1]

To explicitly answer pfeerick's question. No, I don't think channel monitor needs special treatment. Each of the 6 button presses (long or short SYS/MDL/TELE) will have a customizable destination. In use, if the destination is already displayed when one of these buttons is pressed, return to the previous screen.

The part in italics above is my own opinion. Is there something that I need to do to make it an official suggestion, or is this discussion sufficient? (I am very new to github as you might already have guessed.)

[zsdr-bln]

To 1.

Instead of RTN you can use the SYS button which takes you directly back to the menu where you can switch to other model menus (i.e. from Inputs to LogicalSwitches).

[pfeerick]

Also, you can still use the page keys to step through all the screens at that level... I.e. model setup, modes, inputs, mixes, LS, SF, etc...

But yes, it is intermediate work as clearly we are not getting enough feedback from people using it, so you should get an update soon from RM that is for 2.12.

[pH7-JP1]

Using SYS to get to the list of Model Menus is counter-intuitive to me, but it is nice to know. Yes, I had thought of using the page keys, but that requires that I remember the order so that I know whether next or previous is the direction to go and still is several presses (5 in my examples.)

The news that RM will have a 2.12 to support the TX15 is great news. Thank you for all the info.

[pfeerick]

It probably helps to not think of it (SYS/Quick Menu) as the list of model menus, but as the main menu... period... letting you jump to any section of the UI from anywhere else. Once 2.12 enters RC the TX15 will also be officially available as part of EdgeTX releases, rather than needing to use a nightly.

[offer-shmuely]

since running the scripts is very common this days,
especially with ELRS & Rotorflight,
can we locate the "APPS" button on the first level? (instead under "tools")

[runmodedev]

Would it be possible to set the activation button of serial ports aux1 and aux2 on the model setup page (like for the HF modules) instead of the radio setup page?
For my trainers models connected to student radio, I use an RP2 receiver connected to the aux5 port of my TX15, which works very well, and I use it on aux1 trainer SBUS. But I don't need activate it on my other models.