hover point throttle curve adjustment #4245
Open
+14
−5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- added input for value adjustment - added text to locales - adjusted throttle curve math to take hover point into account
✅ Deploy Preview for origin-betaflight-app ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
There is no need to add translations beside |
|
Oh okay, sorry. Should I remove the other ones? |
haslinghuis
requested changes
Nov 8, 2024
| @@ -113,6 +113,7 @@ pid_tuning.initialize = function (callback) { | |||
|
|
|||
| $('.throttle input[name="mid"]').val(FC.RC_TUNING.throttle_MID.toFixed(2)); | |||
| $('.throttle input[name="expo"]').val(FC.RC_TUNING.throttle_EXPO.toFixed(2)); | |||
| $('.throttle input[name="hover"]').val(FC.throttle_HOVER.toFixed(2)); | |||
There was a problem hiding this comment.
FC.THROTTLE_HOVER should be a member of some PG to be decided in firmware.
- adjusted control point positions to avoid a step in the throttle curve
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I'd like to propose a new feature / change to an existing feature: setting the hover point of a quad to 50% of the throttle stick range.
I have been using subtrim in EdgeTX in center only mode to achieve this already, but it is a quad specific setting which I'd like to have in Betaflight.
Setting the hover point to 50% stick travel gives you a lot more "resolution" between 0 throttle and the hover point, therefore making flying at lower throttle in tight spaces a lot easier.
https://discord.com/channels/868013470023548938/1303071076342956072
hover_point.mp4