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

[MT12] Inconsistency in trim position and name #5581

Open
1 task done
chofchop opened this issue Oct 2, 2024 · 8 comments
Open
1 task done

[MT12] Inconsistency in trim position and name #5581

chofchop opened this issue Oct 2, 2024 · 8 comments
Labels
bug 🪲 Something isn't working triage Bug report awaiting review / sorting

Comments

@chofchop
Copy link

chofchop commented Oct 2, 2024

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

In the current MT12 firmware, trim 1 is assigned to trim RH on the screen, and trim 2 is assigned to trim LH on the screen.
In this case, the physical trim position and the trim position on the screen are reversed left and right, so it is very unnatural and cannot be operated intuitively.
Also, on the UI, trim 1 is named "ST" and trim 2 is named "TH", so if the display positions of trim 1 and trim 2 are reversed horizontally, the trim names will be inconsistent.

Expected Behavior

Display trim 1 at trim LH and trim 2 at trim RH on the screen.

Name trim 1 as "T1" and trim 2 as "T2" (do not use "ST" or "TH").

Steps To Reproduce

All firmware after the official release of EdgeTX v2.10 seems to have the same specifications.

Version

2.10.4

Transmitter

RadioMaster MT12

Operating System (OS)

No response

OS Version

No response

Anything else?

It is obviously unnatural that the trim position is horizontally reversed, so it needs to be corrected.

Unlike stick radios, there is no clear correlation between each input axis and each trim switch on the MT12.
There are markings “T1”, “T2”, “T3”... on the MT12 body. Calling them "ST", "TH", "T3"... on the UI causes confusion.
In fact, the MT12's trim switch is often used for purposes other than trim, and throttle trim cannot be used. (I'll explain later). I don't think it's a good idea to use "ST" or "TH" in trim names.

@chofchop chofchop added bug 🪲 Something isn't working triage Bug report awaiting review / sorting labels Oct 2, 2024
@3djc
Copy link
Collaborator

3djc commented Oct 2, 2024

Done on purpose

@chofchop
Copy link
Author

chofchop commented Oct 2, 2024

If you don't mind, could you please tell me the purpose?

@3djc
Copy link
Collaborator

3djc commented Oct 2, 2024

This MT12 is targeted at surface community; and therefore matches de facto standards found in other surface radios

@chofchop
Copy link
Author

chofchop commented Oct 2, 2024

Thank you for answering. You're talking about Trim's name.

What do you think about the physical and on-screen positions of T1 and T2 being flipped horizontally?
Was this also done on purpose?

@3djc
Copy link
Collaborator

3djc commented Oct 2, 2024

Yes, our initial implementation was different, but we got feedback that it was unnatural for seasoned surface drivers

@chofchop
Copy link
Author

chofchop commented Oct 2, 2024

Thank you, I understand. But I'm very disappointed.

@chofchop
Copy link
Author

chofchop commented Oct 2, 2024

This is off-topic, but regarding the matter I said "I'll explain later" above.

For RC cars, it may be necessary to move the neutral position of the throttle (drag brakes, etc.). This requires Δ mode (Center Only) trim. In EdgeTX, Δ mode can only be used for output line sub-trim.
Therefore, throttle trim cannot be used directly and must be used via the GV assigned to sub-trim.

@inventor7777
Copy link

inventor7777 commented Oct 25, 2024

I also wish the first two trims could be renamed to just T1 and T2, but it’s a pretty minor issue.

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

3 participants