Looking for a little help interpreting log file

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...

3691029070?profile=original

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...

3691029126?profile=original

 3) What are the EV log entries? How do I intemperate them? Is there documentation for this?

Then this shows up in the log...

3691028749?profile=original

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?

2013-06-02%2016-13%2098.log

Thanks in advance for the help. 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

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:

    1. Home is Set
    2. Battery is low
    3. Armed
    4. Auto Armed
    5. Takeoff complete
    6. Compass healthy
    7. GPS healthy

    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...

    // DATA - event logging
    #define DATA_MAVLINK_FLOAT 1
    #define DATA_MAVLINK_INT32 2
    #define DATA_MAVLINK_INT16 3
    #define DATA_MAVLINK_INT8 4
    #define DATA_AP_STATE 7
    #define DATA_INIT_SIMPLE_BEARING 9
    #define DATA_ARMED 10
    #define DATA_DISARMED 11
    #define DATA_AUTO_ARMED 15
    #define DATA_TAKEOFF 16
    #define DATA_LAND_COMPLETE 18
    #define DATA_LOST_GPS 19
    #define DATA_BEGIN_FLIP 21
    #define DATA_END_FLIP 22
    #define DATA_EXIT_FLIP 23
    #define DATA_SET_HOME 25
    #define DATA_SET_SIMPLE_ON 26
    #define DATA_SET_SIMPLE_OFF 27

    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...

    // Error message sub systems and error codes
    #define ERROR_SUBSYSTEM_MAIN 1
    #define ERROR_SUBSYSTEM_RADIO 2
    #define ERROR_SUBSYSTEM_COMPASS 3
    #define ERROR_SUBSYSTEM_OPTFLOW 4
    #define ERROR_SUBSYSTEM_FAILSAFE_RADIO 5
    #define ERROR_SUBSYSTEM_FAILSAFE_BATT 6
    #define ERROR_SUBSYSTEM_FAILSAFE_GPS 7
    #define ERROR_SUBSYSTEM_FAILSAFE_GCS 8
    #define ERROR_SUBSYSTEM_FAILSAFE_FENCE 9
    ...looks like ERR 2 = radio error
    ERR 0 = resolved? i think... maybe someone with more expertise than me can chime in here
    EDIT: sorry, it looks like you have already found this info. i was too quick to try and help, but thats the extent of my knowledge.
This reply was deleted.

Activity

Santiago Perez liked Santiago Perez's profile
Saturday
More…