Hi.
After updating to copter 3.6.0 with Chibios on an hexacopter with Pixhawk:
MSG, 80447492, ArduCopter V3.6.0 (2eedcf56)
MSG, 80447515, ChibiOS: ff603d11
MSG, 80447559, fmuv3 00430019 33375113 31313537
shortly after starting a mission (mode Auto), the drone flew away without control when descending towards a land waypoint, accelerated heavily and crashed.
The drone was being filmed from an external camera, and had also an onboard camera. The external camera video is this:
http://youtube.com/watch?v=2E7Z96ppuHk
The log is this:
Copter_20181101_14.bin
The fundamental problem is that a failure is clearly noticed on the video, but the first error apearing in the log (GPS glith) happens 5 seconds later. I don’t see the origin of the failure in the log.
The sequence of events which can be observed in the video are:
-Drone armed; mode Stabilize.
-24": mode changed to Auto (mission starts; yaw changed, pointing to ROI).
-33": failure. The drone descends normally towards a land waypoint, but being one meter above ground there is some kind of failure, height oscillates, the drone is accelerated heavily, and goes away without control, being stopped by a fence.
-41": the drone hits the fence. The GPS is disconnected (GPS logs stop, but not others); it was found 10m away.
So the most simple way to relate video and log is the instant of the last GPS message, which should correspond to second 41 in the video. It is:
87152 12:09:44.381 110893205
8" before should be the problem located, moreless at 12:09:36 102893205, around line 63312.
So the main events on both video and log are:
-Auto at 24" (35270 12:09:26.730 MODE 93242650 Auto).
-Failure at video 33" (moreless 63312 12:09:36 102893205).
-GPS Glitch (73569 12:09:39.948 MSG 106460143 GPS Glitch), 3.5" after the failure.
-Land mode change not obeyed (75624 12:09:40.448 106960070 Land), 4.4" after the failure.
-Moreless 4" after the failure RCOUT.C3 has a high value during 4.5". The drone, without control crashes.
-The crash is seen at second 41 in the video. The GPS is disconnected and thrown away (last GPS parameters at 87152 12:09:44.381 110893205).
-Log continues, so it seems that the electronics has been working all the time.
I can’t find anything going wrong around the instant of the failure as appears in the video. The first error message is a GPS glitch:
73568 12:09:39.948 ERR 106460126
73569 12:09:39.948 MSG 106460143 GPS Glitch
so that happens 4" after the failure is noticed in the video, and must be a consequence of other type of failure.
This is a graphic of ATT DesPitch and Pitch:
DesPitch starts to grow anormally around:
69437 12:09:38.248 104760026
so that happens 2" after the failure is noticed in the video. Something must have failed before.
This is a graphic with other events:
The white dotted line corresponds moreless to the failure noticed in the video.
GPS.Spd starts to grow abnormally at moreless:
72757 12:09:39.401 105913163
so that happens 3.4" after the failure is noticed in the video.
The first glitch (12m) in RFNDDist1 happens moreless at:
71283 12:09:39.043 105555302
so that happens 3.4" after the failure is noticed in the video, and is probably due because it is a sonar, and probably the drone, out of control, points to a distant point.
So up to now, something unknown to me has failed, and has measurable consequences. There is a Mode message change to Land:
75624 12:09:40.448 106960070 Land
so that happens 4" after the failure is noticed in the video, but the drone does not land.
This is a graphic of RCIN.C3 and RCOUT.C3:
so noticing the failure I pulled throttle to a minimum at
69679 12:09:38.648 105160350 1090
so that happens 2.6" after the failure is noticed in the video, but was useless since mode was Auto.
Instead, it is observed that from moreless
73178 12:09:39.848 RCOU 106360457 1858
to
86616 12:09:44.248 RCOU 110760243 1888
the drone is accelerated heavily making thing go much worse, and that happens during moreless 4.5", as can be checked in the video. The drone finally crashes. Not only the drone does not land, but being out of control is heavily accelerated.
The GPS is an RTK one. GPS.Status is 5 (RTK Float) at the crash. It goes to 4 during some instants, starting at:
72757 12:09:39.401 105913163
so that happens 3.4" after the failure is noticed in the video, coincident with the RFND.Dist1 glitch mentioned before, so can be explained because the antenna didn’t point up during some instants, and can’t be the cause of the failure.
Questions:
-What can be the primary cause of the failure observed at second 33 in the video?
-Why does not the drone land and stays out of control?
-How can it be that RCOUT.C3 after the failure can have high values and cause a crash?
-What can be done to prevent such a failure?
-Am I missing something
The video on the on board camera is:
http://youtube.com/watch?v=Gvwfjh8QWp0
but does not give much information, more than the motors noise at the failure.