-
Notifications
You must be signed in to change notification settings - Fork 89
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
Servo travel too short at 150% servo travel #4959
Comments
What receiver/receiver firmware? |
Archer GR8 Firmware Version2.1.14 |
Indeed it is not possible |
That's true, but that's not the problem. The output of 150% is selectable and is required for the first application. And if the output shows 2268, that should also be output. |
The radio requests this value, but there is an element in the chain which doesn't allow it |
It is only mentioned for SBUS not to go over 125%, which is perfectly fine. But for other applications it may be necessary to extend the range to 150%. |
For flaps in fast gliders I generally need between 130 to 150% to maximize breaking for landing on tight spots with smallest possible lever for max force. With OTX it was no problem to go up to 150. I don’t use SBUS. If this is not possible it is a lost opportunity for the rc glider community. |
Do you have the same setup between OpenTX and Ethos? Because if you consider the OS it should work the same! |
Yes when programming the same glider under Ethos I noticed the flaps on 2 gliders (where I went over 125%) were missing some degrees in the end position compared to when I had it programmed in OTX. Same Offsets and same Mixer values. Those degrees make a difference in high wind / small patch landings. As Skippidy shows in his measurements above there is something missing |
Strange, I will check it |
When I look at the output of the servo travel at 125% (SBUS) and 150% (max), the 150% output is missing +/- 86μs.
This is clearly noticeable in the servo travel when you use this 150% .
Ethos 1.6.0
Receiver Tandem X20s
The text was updated successfully, but these errors were encountered: