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
GPS RTH issue: Max altitude doesn't reset with disarm #7243
Comments
Yes, this looks like a bug. I'll look into it. |
@aowi7280 Can you please test this version to see if it fixes the problem? |
OK, I will flash it in tonight. |
Flashed in OK, but wind speeds of 35 to 50 MPH today. I will test it as soon as I can. |
That solves the max altitude problem. But I think I found another bug. It does not respect the minimum distance before it allows GPS Rescue. I can power up, arm, fly 20 feet, activate rescue mode with a switch and it tries to return to home. |
This is unrelated. So you have the sanity checks enabled? What's your value for |
Thanks for fixing that first problem. No, Sanity_checks = off |
That's the reason. The minimum distance to home when manually activating is a sanity check. |
Not a bug. Good to know. Thanks. |
Describe the bug
After landing and disarming, the new location is set as the GPS home position (correct behavior), but the max altitude is kept from the previous flight. It should reset the altitude to zero.
To Reproduce
Arm, fly to new location and note max altitude reached, land, disarm. Rearm without disconnecting battery, fly away and activate GPS-Rescue. The craft will climb to the previous flight's altitude+the GPS Altitude setting, but return to the new home location.
Expected behavior
After landing and disarming, both the Home position and Max altitude reached should reset to the new position and zero altitude.
Flight controller configurationTarget: OMNIBUSF4SD
Name/Version: 4.0.0 #1283
Binary: betaflight_4.0.0_OMNIBUSF4SD-1283-3b93361ac.hex
Date: 12-12-2018 05:43
Setup / Versions
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: