Hi There
I was testing a new gimbal today and I just bothered to do an autoanalysys of the log. of my OCTO
Log File C:/Program
Files/Mission Planner/logs/OCTOROTOR/1/2016-05-02 15-36-00.log
Size (kb)
15367.5751953125
No of lines 186149
Duration 0:10:17
Vehicletype ArduCopter
Firmware Version
V3.3.2
Firmware Hash 7f16e4d6
Hardware Type
Free Mem 0
Skipped Lines 0
Test: Autotune = NA -
Test: Balance/Twist =
NA -
Test: Brownout = GOOD
Test: Compass = WARN -
Moderate change in mag_field (25.98%)
Test: Dupe Log Data =
GOOD -
Test: Empty = GOOD -
Test: Event/Failsafe =
GOOD -
Test: GPS = GOOD -
Test: IMU Mismatch =
GOOD - (Mismatch: 0.24, WARN: 0.75, FAIL: 1.50)
Test: Parameters =
GOOD -
Test: PM = NA -
Test: Pitch/Roll = NA
Test: Thrust = NA -
Test: VCC = WARN - VCC
min/max diff 0.393v, should be <0.3v
I am still trying to learn to read the logs, may someone please have a look at the log
I am worried about the VCC WARN as I never had it before. I noticed that while in stabilize and AltHold the power to the Pixhawk is pretty herratic and as soon as I switched to PosHold it becames even. Is this normal?
The compass WARN doesn’t seem to be a big issue, even if it is weird as I was just flewing it at home, as I usually do and never had it before, could it be the new gimbal creating some interference? I ll give a try to redo the compass calibration.
Last and not least if someone could shed some light on the Baro Temp log as it s not clear to me what it records as the increase of degrees is too huge to be real.
Thanks for the help
F