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

Fixedwing throttle control in various flight modes. #1985

Closed
oleost opened this issue Aug 9, 2017 · 4 comments
Closed

Fixedwing throttle control in various flight modes. #1985

oleost opened this issue Aug 9, 2017 · 4 comments
Labels

Comments

@oleost
Copy link
Contributor

oleost commented Aug 9, 2017

Think it's needed to rethink how the throttle stick should act in various flight modes, with and without airspeed sensor.

Specific:

  1. Althold
  2. Poshold
  3. Poshold and althold combined

My thoughts so far

New variables named nav_fw_speed_mode which can be gps_speed or air_speed

Althold:
0-95% controls speed it controls scales between new variables nav_fw_minspeed and nav_fw_maxspeed.
Above 95% it override speed controller and give 100% throttle. Minimum throttle will still be constrained by "nav_fw_min_thr"

@SoulPictures
Copy link

Sounds like an idea, but should be usable as a MODE due to possibilities of not noticing dirt or other stuff within the pitot tube... ? Maybe as an Mode with configurable Speed as 50% Throttle? so you could set the best cruise speed for your model as 50% throttle and scale up and down from there through stick movement ?

@fiam
Copy link
Member

fiam commented Oct 7, 2017

@oleost I think it would be better to put that on a POT, to avoid accidental triggers. Also, I think is better to leave the THR stick alone while in NAV modes, so it will be on a position that will make the aircraft fly when you switch to manual control again.

@stale
Copy link

stale bot commented May 13, 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
Copy link

stale bot commented May 27, 2018

Automatically closing as inactive.

@stale stale bot closed this as completed May 27, 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

3 participants