Log analysis results..Bad Compass?

Log Analysis -- deprecated Copter Logs -- deprecated
1

running a pixhawk and have not been able to get loiter dialed in right. Was looking at logs and did an analysis on the last flight. It came back with:

[i]Log File C:/Temp/Quad/Streak 800/APM Mission Planner/logs/QUADROTOR/1/2014-05-11 08-20-25.log
Size (kb) 1856.763671875
No of lines 25589
Duration 0:02:27
Vehicletype ArduCopter
Firmware Version ArduCopter
Firmware Hash
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Brownout = PASS -
Test: Compass = FAIL - Large compass off params (X:-43.87, Y:60.83, Z:234.28)
Large compass offset in MAG data:
Z: 234.00
mag_field interference within limits (4.44%)

Test: Dupe Log Data = PASS -
Test: Empty = PASS -
Test: Event/Failsafe = PASS -
Test: GPS = PASS -
Test: Parameters = PASS -
Test: PM = PASS -
Test: Pitch/Roll = PASS -
Test: Underpowered = PASS -
Test: VCC = PASS -[/i]

Is the large offset on Z the problem? Is it a compass hardware issue? Have done the live calibration several times. Full log attached. Thanks!

2

Did u find solution?
I have the same issue:
Test: Compass = FAIL - Large compass off params (X:-158.94, Y:115.60, Z:8.33)
No MAG data, unable to test mag_field interference

My system: APM 2.6, external compass LEA-6H GPS
Mission planner settings: External compass ROLL 180

Any idea?
Thanks

3

My new home-brew quad with a new pixhawk also shows the same in the log analysis:

[size=85]Log File C:/Program Files (x86)/Mission Planner/logs/QUADROTOR/1/2014-06-12 13-46-40.log
Size (kb) 2512.5087890625
No of lines 34800
Duration 0:02:31
Vehicletype ArduCopter
Firmware Version ArduCopter
Firmware Hash
Hardware Type
Free Mem 0
Skipped Lines 0

Test: Brownout = PASS -
Test: Compass = FAIL - Large compass off params (X:-133.73, Y:-59.77, Z:-177.84)
Large compass offset in MAG data:
Z: -177.00
mag_field interference within limits (7.96%)

Test: Dupe Log Data = PASS -
Test: Empty = PASS -
Test: Event/Failsafe = PASS -
Test: GPS = WARN - Min satellites: 5, Max HDop: 7.32
Test: Parameters = PASS -
Test: PM = PASS -
Test: Pitch/Roll = PASS -
Test: Underpowered = PASS -
Test: VCC = PASS - [/size]

It is running 3.2-rc2 and also would like to know if I should be concerned. MP is 1.3.5.

Log file attached.

4

You should be concerned because only very experienced users who specifically help the developers test the code should fly Beta firmwares and release candidates.

5

Maybe I should rephrase:

On copter.ardupilot.com/wiki/ac_com … padvanced/ in the Live Calibration of Compass Offsets section, it says:

[size=85]For the PX4 and Pixhawk it is OK if the values are greater 150 or less than -150 and it will still arm.[/size]

My log has a Pixhawk Compass value greater than 150, so I gather that is why it is flagged.

If it is okay, per the wiki, then MP shouldn’t be flagging it as a FAIL.

So, assuming the wiki is correct, and MP is in error, then there should not be a cause for concern, and MP is in error.

Yes, I am flying beta firmware, and I feel I am helping the developers by pointing out an issue. What I didn’t know is if it is a firmware issue, Pixhawk issue, MP issue, or wiki issue.