Hexa crash V3.6.9

ArduCopter Copter 3.6
1

Hi all, there who can help me, with the crash my hexa a destruction frame, gimbal and camera.
No hardware changes.
With the Large change in mag_field (432.34%) in vevsion V3.6.9 and with version V3.6.8. Moderate change in mag_field (28.25%)

Attached flight registration and autoanalysis of both versions.
I do not understand.

regards

Size (kb) 10663.8896484375
No of lines 128106
Duration 0:06:04
Vehicletype ArduCopter
Firmware Version V3.6.8
Firmware Hash 2f409678
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = WARN - Moderate change in mag_field (28.25%)

Test: Dupe Log Data = GOOD -
Test: Empty = FAIL - Empty log? Throttle never above 20%
Test: Event/Failsafe = GOOD -
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.48, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = GOOD - Motor channel averages = [179, 174, 177, 178, 171, 182]
Average motor output = 176
Difference between min and max motor averages = 11
Test: NaNs = FAIL - Found NaN in CTUN.DSAlt

Test: OpticalFlow = FAIL - FAIL: no optical flow data

Test: Parameters = FAIL - ‘THR_MIN’ not found
Test: PM = GOOD -
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = UNKNOWN - No CURR log data

Size (kb) 6792.5654296875
No of lines 82451
Duration 0:03:54
Vehicletype ArduCopter
Firmware Version V3.6.9
Firmware Hash 632be63f
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = UNKNOWN - No ATUN log data
Test: Brownout = GOOD -
Test: Compass = FAIL - Large change in mag_field (432.34%)
Min mag field length (88.94) < recommended (120.00)

Test: Dupe Log Data = GOOD -
Test: Empty = FAIL - Empty log? Throttle never above 20%
Test: Event/Failsafe = GOOD -
Test: GPS = GOOD -
Test: IMU Mismatch = GOOD - (Mismatch: 0.50, WARN: 0.75, FAIL: 1.50)
Test: Motor Balance = GOOD - Motor channel averages = [179, 175, 178, 177, 175, 179]
Average motor output = 177
Difference between min and max motor averages = 4
Test: NaNs = FAIL - Found NaN in CTUN.DSAlt

Test: OpticalFlow = FAIL - FAIL: no optical flow data

Test: Parameters = FAIL - ‘THR_MIN’ not found
Test: PM = GOOD -
Test: Pitch/Roll = GOOD -
Test: Thrust = GOOD -
Test: VCC = UNKNOWN - No CURR log data

https://1drv.ms/f/s!AooDAPL3CvnOguJr-e9_U488oFHbpA

2

hi
looking at IMU values everything looks good

1
1.jpg1704×528 159 KB

RCOUT also showing no motor lose and good balance

rcout
rcout.jpg1705×527 165 KB

your gps data shows no gps glitch

gps
gps.jpg1705×528 70.5 KB

you have large change in your mag but it cant causing crash (i was flight with bigger change)
i think you lost power in air because your FC suddenly stopped recording data

there is no any data about losing altitude

altitude
altitude.jpg1703×527 80.1 KB

also there is no any data about battery voltage comes up after crash

batt
batt.jpg1705×529 80.3 KB

every time you crash or land your FC must record altitude data and battery voltage like this (battery voltage must comes up and altitude must zero)

batt61
batt61.png1705×527 11.3 KB

altitude61
altitude61.jpg1706×527 111 KB

i suggest you check battery wires and power module

1 Like
3

here is a example altitude data from my Hexa crash :sweat_smile:

Untitled
Untitled.jpg1705×526 68.5 KB

2 Likes
4

Hello hosein_gh and thank you very much for your analysis, when I had v369 after the crash, connect it to my pc and it gave me the message of “Magnetic Field”
I have returned to version v368 and the message “Magnetic Field” did not come back

regards

1 Like