-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
hover point throttle curve adjustment #4245
base: master
Are you sure you want to change the base?
Conversation
- 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? |
@@ -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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FC.THROTTLE_HOVER should be a member of some PG to be decided in firmware.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to use FC.RC_TUNING.throttle_HOVER
it should be added to firmware MSP message.
- adjusted control point positions to avoid a step in the throttle curve
Quality Gate passedIssues Measures |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within a week. |
@marc-frank , if it is not clear, please understand if you wish to achieve this feature, the firmware must be modified as well as previously stated by @haslinghuis . @bw1129, @ChrisRosser , any thoughts on this feature? |
I have a draft for the modification of the FC firmware. Not completed yet and I haven't figured out how I can test it myself. I'll keep working on it. |
I think it's a natural extension of the control we have over throttle feel right now. Throttle MID and EXPO allow fine resolution around the hover point but don't allow you to control where the hover point is in terms of stick travel. This feature accomplishes that. I don't like the way it creates a discontinuity in the throttle curve. I think modifying the underlying throttle curve as a bezier with HOVER POINT would give the same effect without a discontinuity of gradient. MID and EXPO could then work on that bezier curve to add expo. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
req change
@marc-frank @nerdCopter @haslinghuis @ChrisRosser I really like this! As Chris said, a natural extension/improvement to what's there. |
Here is a simple example of how to make Hoverpoint smooth. |
that looks nice. another good way to do it
|
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