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
Taranis X-lite Pro Sliders as Throttle Bug, Sliders T-Reverse and Sliders as Throttle Timer Bug #8520
Comments
For the timers you set your Throttle Source to your throttle channel and they will work as expected. |
Have you tried it on a X-lite? On Campanion your solution works on the radio it doesn't. |
not throttle stick (or pots in your case), the channel used for throttle |
Yes I know, but others have the same issue. Check here |
If you do so the timers work as exspected, but then the Throttle-Warning doesn‘t work properly (This problem occurs on my Tarranis X10s Express as well)! T-Reverse still has no effect! Companion simulates this case wrong. On the X-lite radio you have to go to the inputs tab and invert the throttle source S1 to -100 of weight to get the timers working. On Companion you have no need to do that. Your answer or solution is just a workaround. Why did you close my bug report? Other people are reporting and complaining the same issue. Just see the link of the frskyforum. On my Taranis X10s Express the sliders, the timers, T-Reverse work all properly. You don‘t have to set in the Setup-tab T-Source to the Thr-Ch. That would not be logical in my opinion. Here you put in the slider. So you also don‘t have the problem with this Throttle-Warning bug. Then it could not be, that you have to deactivate the Thr-Warning with your Thr-Stick if your Thr-Input on input-tab is a Slider, on Mixers Throttle is CH3 I:Thr and on the Setup-tab T-Source is Ch03? Thx for your help |
Throttle warning and Throttle reverse are hardcoded to the throttle stick, it's not a bug, it's just that these aren't currently implemented in a way that allows changing the control. Could be improved in the future. Can you post the otx that doesn't work the same in companion and radio? frsky-forum.de requires registration to see anything for no good reason so can't see things there. |
Hello thank you for your help. Today i have opened a new issue here, because i have thought this one is closed. Sorry. Here is the new one #8524 my otx file: The difference between Model 01 and 02 is only that model 02 has Thr-Input S1 -100. |
"Throttle warning and Throttle reverse are hardcoded to the throttle stick, it's not a bug, it's just that these aren't currently implemented in a way that allows changing the control. Could be improved in the future." This could lead to a safety-problem. If you do the "workaround" for getting the timers working properly (you set T-Source to CH3-Thr and the input for Thr to S1 with weight -100 in the input tab. If the Thr-Stick is in idle-position you don't get the Thr-Warning at startup even S1 is not idle, which is defined as Thr at the input tab! Using a slider, pot or a 3-position-switch for Thr is a usual thing for sail-plane-pilots. |
You can set a pot or slider warning instead |
I like to second this issue / bug! A pot / slider normally works CW and not CCW like with the X-Lite pro and pot / slider S1. It should be just as it is with the Companion, from left to right going from -100 to +100 and not vice versa. I would be happy to get this fixed ... thank you! |
from @kilrah: Its about version 2.3.11 as provided by @AlphaCharlyX in his initial update. In spite of any discussion whether this can be worked around and how, the behavior is supposed to be the same in Companion and the transmitter itself. And this is obviously not given. |
And companion is NOT targeted to match physical behaviour of radio (position, direction,…) only logical Also pot and sliders do not behave in the same way at all. Pots are cw, slider follow switch like rules |
[quote]> Also pot and sliders do not behave in the same way at all. Pots are cw, slider follow switch like rules[/quote] At the X-Lite Pro I would consider S1 a pot as it rotates like the pot S1 within Companion. Both pots (S1 and S2) should behave the same way: At the 0700 position -100 and +100 at the 0500 position (compared to a clock). Accordingly the bars at the display should run up with turning both pots CW (clock wise). If pots are programmed as throttle, the pot warning should work correspondingly and the throttle-timer should run when the motor runs. All of this can't be cured by mixer settings or the like (afaik). |
Might be related - Mapping throttle to S1, and setting timer activation to THR still uses the left stick to activate the timer. In other words, it seems that there is not way to count motor time if motor is mapped to S1. Seems like a bug to me. Fixing this would be important for glider pilots as the throttle stick is commonly used for flap control. |
Hi, |
Worked. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hello together,
there is a problem with starting the Timer (Ths, TH% and THt) and the T-Reverse (Throttle-Reverse doesn't work) when you define S1 or S2 (Sliders) for you throttle-input in your Taranis X-Lite Pro.
T-Reverse has no effect while using Throttle-Input with S1 or S2 sliders. The only way tho reverse Throttle is to set in the Input-tab or in the Mixers-tab or Outputs-tab the weight of Throttle to -100. In this cases then the problem is, that the timers (Ths, TH% and THt) doesn't start although the throttle is on. The timers only start, if throttle is off. This should work the opposite way.
Another bug is on the mainscreen. The bars for S1 and S2 are working the wrong way. They should go up or down the opposite way. If you push S1 (left Slider) to the right the left Slider S1 bar should go up. If you push S2 (right Slider) to the left the right Slider S2 bar should go up.
Please fix this bug quickly.
Thx und Greetings Andreas
General information
The text was updated successfully, but these errors were encountered: