-
Notifications
You must be signed in to change notification settings - Fork 16.9k
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
Plane:options for airspeed sensor failure #2787
Comments
How many seconds to you have in flight to analyze, what is the cause of an unwanted behaviour. But the question is; could APM plane provide a logic to detect, if the airspeed gives still valid values? And if there is a missmatch, give back an imediate warn message, that you should switch to manual. Like "airspeed sensor failure detected, switch to manual". Maybe it is even ok to use "stabilized", I assume, there is no airspeed used for stabilized mode. |
something as simple as if the airspeed doesn't change for 5 seconds throw up a BAD AIRSPEED HEALTH error and just continue to fly as if it never had a sensor. Pixhawk does not support dual airspeed sensors yet I don't think but even then how would it know what one was accurate. |
The solution here is not to switch to manual, that will crash most planes
|
You want to switch it off manually, or by logic from APM? I am not that much a fan of "switching manually". I already lost 3 fixed wing uav's (crashed) by not finding the switch to "manual-mode" fast enough, or when I found it, my plane was already out of sight in the sky.... And I disagree - most Airplanes can be flown on manual mode by fpv with some experience. |
This needs to be done automatically, not manually. See #1628 |
i recently lost a bixler 2 after the airspeed sensor failed mid flight, the sensor started reporting 250mph causing the plane to cut the throttle and pull up, stalling the plane. it would be very useful to be able to switch the airspeed sensor off and on using ch7 or 8 the same way you can with a rangefinder.
The text was updated successfully, but these errors were encountered: