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
Bug in 25sec Auto-Disarm feature #166
Comments
Excellent. thanks for the report. I had the feeling there was something a little off in the disarm code 'cuz occasionally I've seen it disarm faster than i expected. |
Welcome :) Looks like I'm found one possible bug with another failsafe routine: Main loop hang detection. bool failsafe_check(uint32_t tnow)
{
if (mainLoop_count != failsafe_last_mainLoop_count) {
// the main loop is running, all is OK
failsafe_last_mainLoop_count = mainLoop_count;
failsafe_last_timestamp = tnow;
in_failsafe = false;
return true;
}
.... UPD: Volatile variable won't help. Never mind. |
The original issue has been fixed in master. thanks! I've never heard of this failsafe occurring while users are flying. I'll check into it further if you think the issue is real though. |
* Terrain failsafe land instead of RTL in events.cpp
ArduCopter has safety feature which Auto-Disarm copter if you not increased Throttle, but:
2a. Wait less than 25sec after init (after "READY TO FLY" message)
2b. ARM, do not increase Throttle - after ~5sec (instead of 25sec) it will Auto-Disarm.
If you guru in copter and do all operations fast - it's not problem. But if you novice, you wait too long before increase Throttle, and copter audo-disarm. This confusing some people.
Ok, possible solutions:
We encountered this problem in MegaPirateNG project and I'm fixed it by 1. solution, but still not hard tested it.
The text was updated successfully, but these errors were encountered: