EKF3 IMU0 MAG0 ground mag anomaly, yaw re-aligned

Hello! To begin with, I will tell you a little about my aircraft.
My frame size is 800x800x500mm.
I use Cube Orange, Here3 GNSS, Hobbywing XRotor Pro X6 motors and 2 LiPO 22000mah batteries.
I’ve been flying steadily for a few months, but recently I’ve been getting the “EKF3 IMU0 MAG0 ground mag anomaly, yaw re-aligned” error when climbing. When this error occurs, my drone behaves very unstable. After I climb to a height of 10-15 meters, the compass is recalibrated and the drone behaves stably. I tried to solve this problem by replacing the compass with a PM3100, and installing a helix antenna. Then he tried to move the compass to a distance of 15 centimeters from the power wires. Changed the value of the parameter “EK3_MAG_M_NSE” to 0.07 to reduce the sensitivity of the magnetometer. But all this did not help.
I will leave a video of one of my flights and a log file. I will be glad for any help

https://drive.google.com/drive/folders/1_ph5LgvXjAAS3ioRQrogPOCklhygfLG_?usp=sharing

Update to the latest firmware, 4.3.3.

Both compasses are reacting directly to the throttle output, so they are showing signs of interference. Not just the compass, but look at how the wires go to and from the compass to see if you can get those away from the power leads.


If you can do a flight for a few minutes with several 360 degree turns then you can run MagFit and get an updated COMPASS_MOT offset.

Thanks for the answer!
I tried to use different firmware starting from 4.3.0
I tried to move the compass away from the power wires (10, 15, 20 cm), but it did not help.
Once the drone gains altitude, it stabilizes and I can fly, but the climb is terrible.
I’ve noticed that this doesn’t happen everywhere I fly, but most of the time it does.

I understand that the reason may be the place where I fly. But I need stability. How can I achieve it?

You have an hardware issue.
Please use ArduCopter 4.3.3 and fix the issue.
Do not waist your time with 4.3.0

1 Like

I have same problem, I am using pixhawk cube orange 2 22000mah lipo battery and X8 Pro Motor with X8 quadcopter configuraiton. Can you fix this problem?

same problem to me. take off in alt-hold fine and after 15 second it start to bounce and EKF ground mag anormally apear. i will try to update to 4.3.3. i will inform you. (octoquad black cube arducopter 4.0.3)

Please do update to ArduCopter 4.3.5

hi, have you solved the problem? i use 4.1.3 with the same problem

Hello, I have the same problem with Arducopter v4.3.6.
Can anyone help me solve the problem?
Thank!
@rmackay9 Any idea? thank you!

Same issue! X6 Plus Rotor in a 25kg MTOW hexa, dual GPS Here3, using copter 4.2.3.

Please explain, in detail, why you re not using ArduCopter 4.4.1 ?

Because we have a whole fleet in several different cities and several different countries and we cannot run FW updates every three months. When there is a critical safety correction, of course, we stop everything to do it.

Also, Autopilot FW update goes through a validation by the local CAA, in some cases.

Do you use Magfit to calibrate the compass on that fleet of craft?

2 Likes

Yes, we are using magfit calibration. The log is in the link below:

What are you reporting as a problem? Just the fact that there is a mag anomaly message after take-off?

Yes, because earlier this year, we got a similar behavior in a prototype - we “ignored” it and during one of the takeoffs it did an “emergency yaw reset”, quite dangerous, and we comanded a flight termination (crash).
On that prototype, the position of the GPS/Compass wasn’t ideal, that’s true, but in the log above it is positioned the same way as the rest of the fleet.

I suppose it’s for the same reason. Not particularly unusual.

1 Like

hello
I have built a quadcopter drone using pixhawak2.4.8 flight controller, i have done all the calibration on mission planner then I try to takeoff the drone 10-15 second it behave normal (Stable) , but after 10-15 second the drone get outoff control and not controlled by transmitter, then I use “Land” flight mode to land the drone after crash. I have also attached the message of the drone when drone is connected to mp

23-08-2024 15:43:48 : r reboot
23-08-2024 15:43:48 : PreArm: AHRS: EKF3 Yaw inconsistent 84 deg. Wait o
23-08-2024 15:43:18 : r reboot
23-08-2024 15:43:18 : PreArm: AHRS: EKF3 Yaw inconsistent 86 deg. Wait o
23-08-2024 15:42:47 : r reboot
23-08-2024 15:42:47 : PreArm: AHRS: EKF3 Yaw inconsistent 87 deg. Wait o
23-08-2024 15:42:29 : Flight plan received
23-08-2024 15:42:17 : r reboot
23-08-2024 15:42:17 : PreArm: AHRS: EKF3 Yaw inconsistent 82 deg. Wait o
23-08-2024 15:41:47 : r reboot
23-08-2024 15:41:47 : PreArm: AHRS: EKF3 Yaw inconsistent 70 deg. Wait o
23-08-2024 15:41:17 : r reboot
23-08-2024 15:41:17 : PreArm: AHRS: EKF3 Yaw inconsistent 29 deg. Wait o
23-08-2024 15:40:54 : r reboot
23-08-2024 15:40:54 : PreArm: AHRS: EKF3 Yaw inconsistent 62 deg. Wait o
23-08-2024 15:40:24 : r reboot
23-08-2024 15:40:24 : PreArm: AHRS: EKF3 Yaw inconsistent 73 deg. Wait o
23-08-2024 15:39:26 : EKF3 IMU1 MAG0 in-flight yaw alignment complete
23-08-2024 15:39:26 : EKF3 IMU0 MAG0 in-flight yaw alignment complete
23-08-2024 15:39:23 : EKF3 IMU1 MAG0 ground mag anomaly, yaw re-aligned
23-08-2024 15:39:23 : EKF3 IMU0 MAG0 ground mag anomaly, yaw re-aligned
23-08-2024 15:39:00 : Arm: Yaw (RC4) is not neutral
23-08-2024 15:37:46 : Battery Failsafe - Disarming
23-08-2024 15:37:46 : Battery 1 is low 11.37V used 8 mAh
23-08-2024 15:37:35 : Arm: Yaw (RC4) is not neutral
23-08-2024 15:35:40 : RCInput: decoding PPM(1)
23-08-2024 15:35:14 : PreArm: RC not found
23-08-2024 15:34:57 : GCS Failsafe Cleared
23-08-2024 15:34:57 : GCS Failsafe
23-08-2024 15:34:44 : PreArm: RC not found
23-08-2024 15:34:25 : Frame: QUAD/X
23-08-2024 15:34:25 : IMU0: fast sampling enabled 8.0kHz/1.0kHz
23-08-2024 15:34:25 : RCOut: PWM:1-14
23-08-2024 15:34:25 : IOMCU: 410 2003 412FC231
23-08-2024 15:34:25 : Pixhawk1 00440029 33305118 37383630
23-08-2024 15:34:25 : ChibiOS: 6a85082c
23-08-2024 15:34:25 : ArduCopter V4.5.5 (142aece2)
23-08-2024 15:34:24 : Frame: QUAD/X
23-08-2024 15:34:24 : IMU0: fast sampling enabled 8.0kHz/1.0kHz
23-08-2024 15:34:24 : RCOut: PWM:1-14
23-08-2024 15:34:24 : IOMCU: 410 2003 412FC231
23-08-2024 15:34:24 : Pixhawk1 00440029 33305118 37383630
23-08-2024 15:34:24 : ChibiOS: 6a85082c
23-08-2024 15:34:24 : ArduCopter V4.5.5 (142aece2)
23-08-2024 15:34:23 : Frame: QUAD/X
23-08-2024 15:34:23 : IMU0: fast sampling enabled 8.0kHz/1.0kHz
23-08-2024 15:34:23 : RCOut: PWM:1-14

here is the link of videos

Share a log for better analysis, but a glance through those GCS messages shows this thing probably wasn’t ready to fly at all.

It appears you have massive compass calibration issues, ignored warnings, armed, took off, and immediately experienced a battery failsafe.

Follow the tuning steps outlined in the documentation carefully. Pay particular attention to compass calibration. Do not disable arming checks. Consider using the Methodic Configurator software.