Hi all,
Homebuilt x525 with apm 2.6 that I put together the last month or so. I started with a KK board and had neverending problems getting it off the ground. Bought the APM and finally realized I was actually having motor and esc issues. Got those resolved, and have been learning to fly the thing in Stabilize mode the last week or so. Mostly pilot problems now I thought. I started trying out some of the other modes yesterday and got the telemetry up and running. It seems now that I cannot get any of the other modes to function. After a flyaway crash yesterday I started looking at logs and it seems like whenever I select any other mode it determines there is something wrong and goes into land mode. I found last night that the external compass that is supposed to be configured for roll 180 seems to actually be right side up! When I moved the copter to the NE it would go NW, etc. I fixed that and hoped that today would be better. The logs seem to show the same thing - change mode and then it goes to land. When it is flying it just kind of seems to be blown by the wind and losing altitude - so land mode kind of makes sense, Another crash today, a minor one, and then the next try same thing but I obviously loosened a prop and I had one fly off and then flip and more repairs to make. Help! :) Any suggestions would be great!
Drew
Replies
Your battery voltage spiked and then fell below 11v as the EKF fail safe error checks came in. I'm assuming you have a low voltage fail safe turned on. I can't tell without the settings, but it looks like it was your battery has a bad cell that is prematurely dropping your voltage. Could have happened after the fly away and landed real hard.
That's my best guess is that it was trying to land, but you kept feeding inputs into it while trying to enable the failsafe and it had to re-evaluate the error.
Okay, no takers, huh? Reading through the logs some more it looks like I am still having a compass problem that is causing the auto mode to fail. I get ERR subsys 16 Ecode 2 and ERR subsys 17 Ecode 1.
They are 16: EKF/InertialNav Check Bad variance and 17: EKF/InertialNav Failsafe Triggered
I thought the EKF checks were only on the new boards and not the APM 2.X?
Drew
Still no answer?
I have the same issue:
16: EKF/InertialNav Check
ECode 2: Bad Variance
ECode 0: Bad Variance cleared
I will follow the post
No more alarm with a GPS, maybe (or not) an electronic interference!
Okay, here is the REAL log file. I hope.
2015-02-10 18-10-54 27.bin.log
Sorry, I just realized I selected the wrong log file. Working on it~!