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

Failure to transition, and uncontrolled climbing due to interaction of VTOL & FW profiles #7062

Closed
nick2204 opened this issue Oct 10, 2017 · 3 comments
Assignees

Comments

@nick2204
Copy link
Contributor

nick2204 commented Oct 10, 2017

Issue details

In certain conditions it is possible for a VTOL aircraft to fail to complete transition and continue climbing due to an interaction of the VTOL and FW power systems.

If a FW loiter is initiated and transition is incomplete and the current altitude is higher than the desired altitude, the aircraft attempts to lower the forward thrust to in order to descend, as the pitch control is restricted in this state, but if this prevents the vehicle reaching transition speed, then the VTOL motors can prevent it from loosing altitude.

This can lead to a situation where transition speed is never reached, and Altitude continues to climb.

Version

Arduplane 3.8.2-dev (running in SITL)
Q_enable =1 (quadplane)
Q_guided_mode = 0 (FW loiter)
Q_RTL_mode = 1 (land in VTOL once RTL reached)

Platform

[ ] All
[ ] AntennaTracker
[ ] Copter
[ x ] Plane
[ ] Rover
[ ] Submarine

Airframe type

Quadplane

Hardware type

PH2.1
SITL

Logs

SITLROM_PARAM.zip

@nick2204
Copy link
Contributor Author

Generally this state can be avoided by ensuring that enough distance/time is left left between transition and FW loiter.

Fix could simply be prevention of FW loiter until transition has completed.
Alternately if Loiter is required vehicle could either:

  • VTOL loiter
  • finish transition on current heading then return to location for FW loiter

@tridge
Copy link
Contributor

tridge commented Oct 21, 2017

I've fixed this properly with PR #7102

@OXINARF
Copy link
Member

OXINARF commented Oct 22, 2017

#7102 is now merged.

@OXINARF OXINARF closed this as completed Oct 22, 2017
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants