I finally got my quad working nicely in the configuration I wanted, so I sent it out auto flight.
A minute after launch (after it had passed the first waypoint) it dropped out of the sky like a rock and smashed into several pieces.
I followed the instructions here in an attempt to diagnose the problem. The fact that Roll did not match DesRoll, and Pitch did not match DesPitch indicated to me that there was a mechanical problem.
However, when I hooked up and tested the motors after the crash they seemed to work fine.
The specs are as follows:
Motors: Emax 2216 (810Kv)
Battery: 5000MaH 4S
Controller: Pixhawk (clone)
Firmware: Arducopter 4.0.3
Here is the auto-analysis of the last flight:
Log File C:\Users\shane\AppData\Local\Temp\tmpCB22.tmp.log
Size (kb) 4668.23828125
No of lines 54875
Firmware Version V4.0.5
Firmware Hash 3f6b43e3
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = FAIL - Large change in mag_field (45.19%)
Test: Dupe Log Data = GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe = FAIL - ERRs found: FLT_MODE GPS_GLITCH
Test: GPS = UNKNOWN - join() takes exactly one argument (2 given)
Test: IMU Mismatch = GOOD - (Mismatch: 0.74, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = UNKNOWN - tuple index out of range
Test: NaNs = FAIL - Found NaN in CTUN.DSAlt
Test: OpticalFlow = FAIL - FAIL: no optical flow data
Test: Parameters = FAIL - ‘MAG_ENABLE’ not found
Test: PM = GOOD -
Test: Pitch/Roll = UNKNOWN - ‘BarAlt’
Test: Thrust = GOOD -
Test: VCC = UNKNOWN - No CURR log data
The logs from the last flight can be found here:
I’m not sure what would cause such a sudden, catastrophic, failure.
Could this be ESC sync failure?
Can someone please take a look at the log and let me know what you think the problem is?