Hello-
Had a run-away crash last weekend and I am still trying to figure out just what's happening. Looking at the logs I see several short-lived failsafe events that looked like this...
1) So what might have caused this brief failsafe event? I was a short distance from the quad the whole time just practicing STAB and ALT_HOLD, so I have a hard time believing I lost radio signal. No telemetry or video RF to interfere.
2) When FS cleared on line 5309, would the mode have also changed? Or would it stay in RTL? Like I said, I did not notice these events during the flight. I think that I would have noticed an RTL.
Here is another example...
3) What are the EV log entries? How do I intemperate them? Is there documentation for this?
Then this shows up in the log...
The quad might have already been chewing up the honeysuckle bush at this point, so maybe this is not important, but...
4) What is ErrorCode 3? Is there documentation for these ErrorCode definitions someplace?
5) What does the DATA line tell us?
Thanks in advance for the help.
Replies
Ted and Rick-
Thanks for your prompt reply. That's exactly what I need to know. I can dig in from here.
I *think* that in 2.9.1b, ERR FS 2 is the throttle failsafe, and FS 3 is battery.
When the failsafe clears, it won't change out of RTL until you change modes.
EV15 - auto armed
EV28 - Reached Altitude
EV29 - Ascending
EV30 - Descending
Data 7 is the AP state bitfield. In this case, you have 11010011010001, which maps to:
If you look in git as Ted suggests, make sure you pick the right branch, as some of the values have changed.
i think this is what you are looking for:
the event (EV) codes are found in the defines.h file @line 303:
#define DATA_[condition] [code #]
https://github.com/diydrones/ardupilot/blob/master/ArduCopter/defin...
not fully confident that these aqre the right codes, but the ERR codes in the defines.h file @ line 414:
https://github.com/diydrones/ardupilot/blob/master/ArduCopter/defin...