Skip to content
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

Split up auto-throttle and altitude hold for fixed wing #3251

Closed
FinalFrag opened this issue May 21, 2018 · 3 comments
Closed

Split up auto-throttle and altitude hold for fixed wing #3251

FinalFrag opened this issue May 21, 2018 · 3 comments
Labels

Comments

@FinalFrag
Copy link
Contributor

I'd like to suggest a new feature. Well, splitting up an existing feature actually. This is for fixed wing specifically.

Right now when you activate altitude hold mode, iNav also enables auto throttle. It would be nice to have these on 2 separate modes, so you can have altitude hold, but manual control over throttle/speed.

When I try to do follow footage with a friend, it's hard enough to find each other. When you finally get on the same line (using altitude hold, heading in osd, lots of communication, etc) you want to get as close to each other as possible. But once you click out of AH, it's hard to get closer AND maintain altitude manually. When these 2 features are separate, I could click out of auto-throttle but stay in AH and just increase throttle to get closer.

I understand stalls might become a problem, so maybe let iNav control the minimum throttle value, but give priority to the throttle stick if its above that value?

@shellixyz
Copy link
Collaborator

I'm going to work on this.

I understand stalls might become a problem, so maybe let iNav control the minimum throttle value, but give priority to the throttle stick if its above that value?

Yes the idea is for the minimum throttle to still be automatic but to be able to increase it by moving the throttle stick past the mid point (>1500) like it is done in Arduplane. All the auto modes could have the throttle manually adjusted unless in failsafe. Then the throttle would be automatic just like now.

@stale
Copy link

stale bot commented Jul 20, 2018

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

@stale stale bot added the Inactive label Jul 20, 2018
@stale
Copy link

stale bot commented Aug 3, 2018

Automatically closing as inactive.

@stale stale bot closed this as completed Aug 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants