At one time there was an issue with Cross Trims and Low Throttle only

[Gerty64p]

At one time a few Revisions ago there was an Issue when you tried to Set Only at Low Throttle Trim and setting the radio up to use Cross Trims
I got Hooked on Cross Trims when I had an old Kraft KP7Z and all my old ACE Micropros were set up this way
But I also like the Fact that you can set the QX 7 and X9+ so that trim is only effective at Low throttle

Does anyone know if they got this issue fixed yet with the newer Revisions

Thanks

 

[Wayne]

Yes, I believe it was fixed about 6 months ago. Pretty sure everyone is happy now, but maybe someone here will add to this if I am mistaken.

 

[sande005]

Not fixed yet. Was supposed to be done as part of OpenTX ver 2.2.3, but it was delayed. So now we wait to see if it is included in 2.2.4 (or 2.3.0 or whatever comes next).

 

[Wayne]

2.3 is in nightlies. I strongly suggest you check it out, and if the functions are not working, give them feedback ASAP so it can be sorted out for the release! If you wait for others to do it, you will be waiting a long time. This is clearly not a function the OpenTX team uses, that is why they need testers for the operation.

 

[sande005]

Not fixed as of 2.2.4, and no reference to it in the notes so far for 2.3. I just asked about it in the OpenTx forums, and on the RCGroups 2.3 thread.

 

[Wayne]

Need to go into their github to report issues and get fixes.

 

[sande005]

Over on RCGroups, one who I presume is a developer noted that is has again been delayed for a future 2.3.x release. Here's the Github entry, where it shows the same:
https://github.com/opentx/opentx/issues/5635

 

[davemcddd]

The OpenTx programming bug when using crossed trims with the Trim Idle Only activated has been a sore spot with me ever since I got my first Taranis about 5 years ago. The "fix" keeps getting delayed over and over and over again. I truly don't understand why the developers have zero interest in correcting the problem.

 

[Wayne]

Best thing to do is keep after them on Github. Squeaky wheel gets the oil.

 

[davemcddd]

Us squeaky wheels have been making noise about this issue for the past 6 years, and it still isn't fixed. The Trim Idle Only function is pretty much a standard feature on the mid and high level radios of the major brands that don't use OpenTx. Obviously the developers thought about the TIO function because they created a checkbox to enable or disable the TIO function. But it truly puzzles me about why they don't seem to care if the TIO function works correctly when the trims are crossed.

 

[Konrad]

I don't know what resource issues there may be, or if there are technical issues (software). As it seems like there are so few of us that have this issue, might it be possible to come up with a hardwire solution. What are the limitation to moving the wires or switches to the other side. Wouldn't this accomplish the same function? (keep the TIO function and have it on the other side. I seem to recall doing this with the Silver Seven and even the MicroPro 8000 TX. I moved the trim to the the upper left corner on my old TXs.

All the best,
Konrad

 

[davemcddd]

Crossing the aileron and rudder trims in the software works just fine, so a hardware solution isn't needed for them to work correctly.

My temporary (now semi-permanent) solution to the TIO with crossed trims problem was to add extensions to the internal wiring cable of the elevator and throttle trims. This extra cable length allows the throttle trim cable plug to reach across to the elevator trim switches, and the elevator trim cable plug to reach across to the throttle trim switches. This way when the TIO is activated it works normally because the elevator and throttle trims were crossed with hardware instead of software. The biggest downside to the hardware solution is that the trim displays don't get crossed, so the displayed trim is on the opposite side of the transmitter from the physical trim location. This is the main reason I'd like to see the software TIO selection box get fixed. Plus I've got to admit it's embarrassing when somebody points out that a bug in the software still hasn't been fixed after nearly 6 years. (Github issue first created November 29, 2013.)

 

[Konrad]

Ok so it is a display issue. Functionally you now have a working interface (ergonomically comfortable).

As for software issue we wouldn't be surprised to learn that there are a plethora for code issues that could be cleaned up.

In a resourced limited environment, (labor, memory etc.) this sounds like a good candidate to keep bouncing down the road.

All the best,
Konrad

 

[sande005]

Reviving this thread from the past. It looks like one of the developers finally took a look at the issue, and it has been tested for other impacts (use in Flight Mode trims, trims to subtrims, etc.) and has passed. So now slated to be part of 2.3.9 when that comes out. They'll have a new small section where one can specifically designate an alternate trim (maybe any source?) as throttle trim, then everything downstream works from that. Model specific.

 

[davemcddd]

I hope this fix turns out to be true! It's been over 6 1/2 years since the issue was brought to the attention of the OpenTx developers.

 

[sande005]

And bummer - it has now been bumped to 2.3.10 (!)

 

[Kilrah]

That's only becasue 2.3.9 had to be released straight away after 2.3.8 to fix a bug, no change on the issue progress...

 

[davemcddd]

Good news! The Trim Idle Only (TIO) issue when using software crossed trims has been solved with the official release of OpenTx 2.3.10!

 

[sande005]

Careful using this new fix....I was converting my models that used a work-around, and stumbled across....

If using the TTrim lever to control Elevator trim, and pick the option in Outputs to apply Trim→Subtrim, the subtrim does change correctly. But, the TTrm lever is not reset to 0, like it is for all the other trims when using the option. You have to move it back to center manually, otherwise you have double the amount of trim you intended.
Trim→Subtrim does work correctly with cross trims in older versions...but then, of course, Trim Idle Only and Instatrim doesn't.

Haven't yet tried using TTrm for some other variation of cross trims, but would assume it has the same issue with Trim→Subtrim.

(BTW - with the new fix, Instatrim is deliberately disabled if you have cross trims set up, so at least you can't get deep into trouble that way!)

Case opened over on Github.