<![CDATA[[muorb] [ekf2] resetQuatStateYaw called]]>I get this error: "[muorb] [ekf2] resetQuatStateYaw called:"

I know that this is expected behavior as the UAV stops listening to the compass and uses GPS for heading. My question is to the background of this, as I would LIKE to use the compass.

  1. Was this done as the power consumption from the motors messes up the heading of the UAV
  2. If the answer to #1 was yes, I am curious if we could do a compass power compensation: https://docs.px4.io/main/en/advanced_config/compass_power_compensation, or if this was already tried and didnt work
  3. If we can not listen to the compass at all, I am wondering if there is a recommended way to disable the compass prearm check so that when we land in position mode, and go to takeoff again, the pre-arm checks dont yell at us that our compass is missing. - I know we can program something ourselves, but want to see if there is a recommended way that you guys have looked into. Just dont want to duplicate work.

Any advice would be much welcomed, and thank you for your assistance!

Some logs as well with high rate logging turned on:
https://review.px4.io/plot_app?log=ea8fad6d-1e00-4441-a70b-2726c6e8501b
https://review.px4.io/plot_app?log=fc2f0d95-0ef7-434d-88b2-1b1d8e0243d5

]]>https://forum.modalai.com/topic/5234/muorb-ekf2-resetquatstateyaw-calledRSS for NodeTue, 02 Jun 2026 02:27:59 GMTMon, 01 Jun 2026 21:33:04 GMT60<![CDATA[Reply to [muorb] [ekf2] resetQuatStateYaw called on Mon, 01 Jun 2026 22:54:36 GMT]]>@wilkinsaf You can disable compass with SYS_HAS_MAG = 0 and EKF2_MAG_TYPE = 5. But if you enable it and it isn't healthy you won't be able to arm. Power compensation may work, it depends on your particular drone model and use case.

]]>https://forum.modalai.com/post/25974https://forum.modalai.com/post/25974Mon, 01 Jun 2026 22:54:36 GMT