Advanced Compass Setup¶
This article provides advanced guidance for how to setup the system compass(es) and advanced compass related features.
Users who have only internal compasses or an external compass using a UBlox GPS + compass combination,such as UBlox GPS + Compass Module, and have mounted it in the default orientation can usually perform a simple “Onboard Calibration” as described in Compass Calibration).
Accurately setting up the compass is critical because it is the primary source of heading information. Without an accurate heading the vehicle will not move in the correct direction in autopilot modes (i.e. AUTO, LOITER, PosHold, RTL, etc). This can lead to circling (aka “toiletbowling”) or fly-aways.
ArduPilot allows multiple compasses to be connected, but only three are used at one time. And usually, only the primary compass is used, unless there are consistency problems with its readings versus other compasses and/or other sensors. In this case, the autopilot will automatically determine which of the first three compasses to use.
While many autopilots have an internal compass or compasses, many applications will instead use an external compass. This provides more reliable data than an internal compass because of the separation from other electronics. See Autopilot Hardware Options for details about the specific autopilot to determine how many built-in compasses the autopilot may have, if any.
The Mission Planner Compass Setup screen can be found in menu Setup | Mandatory Hardware | Compass in the sidebar. This screen is used for setting compass ordering, priority, calibration, and use. No other settings are required for normal use.
Compass Ordering and Priority¶
During boot, ArduPilot automatically detects the compasses present in the system, adds them to a list, and assigns the first three a priority (1-3) linked to their DEV ID (
COMPASS_PRIOx_ID), according to the order in which they are discovered. This priority determines which compass is used by the EKF lanes. The primary compass (highest priority, 1) will be used by all lanes, and fallback to the next viable compass in the first three priorities, if the primary becomes unhealthy.
The list of discovered compasses and their priority is maintained across boots.
If a user wishes to change to a different compass for one of the three priorities, he can change the
COMPASS_PRIOx_ID to that compass’s
COMPASS_DEV_IDx ID value. If a
COMPASS_PRIOx_ID is set to zero, the compasses will be moved up contiguously, in order, to fill that priority slot on the next reboot. This is easily done in Mission Planner with the arrows on the right side.
never change a compass’s
COMPASS_DEV_IDx ID value manually and then reboot!
If a previously discovered compass is missing or not detected on boot, and is in one of the three priority positions, a pre-arm failure will occur warning the user. The user will need to either remove the compass from the priority position, or correct the problem in order to prevent the pre-arm failure. Mission Planner provides a button to remove an undetected compass on the above screen.
Compasses not present or detected during a calibration will automatically be removed.
Any one of the first three compasses can be disabled. This would leave only the remaining ones to be used by the autopilot. You may wish to disable any internal compasses if you are consistently seeing the “inconsistent compasses” pre-arm message often and you are sure that the external compass is calibrated.
Compasses should always be enabled for Copter/Rover, but may be disabled (not recommended, if one is available) for Plane.
The setting of the orientation of external compasses is no longer required. It’s determined automatically during Compass Calibration now. This can be disabled, or only report the orientation determined during Compass Calibration, using the COMPASS_AUTO_ROT parameter. The orientation determination CAN fail if the magnetic fields are compromised by nearby metal or other interference, especially on 45 deg offset orientations. If the compass is known to be mounted on a 45 degree bias to the accelerometers, and fails to determine orientation during the Compass Calibration, then setting COMPASS_AUTO_ROT to “3” and repeating the calibration, may yield a successful completion.
automatic determination of compass orientation ONLY occurs using normal Compass Calibration. In-flight Calibration and Large Vehicle Mag Calibration require that the orientation be properly set BEFORE attempting these types of calibration.
However, if the need to double-check the orientation of a compass should arise:
When rotating your aircraft through all axes each of the compasses should move in the same direction, and should be of approximately the same values:
- Northern Hemisphere:
Z-component should be positive
when pitching the vehicle down, the X component should increase in value
when rolling the vehicle right, the Y component should increase in value
- Southern Hemisphere:
Z-component should be negative
when pitching the vehicle down, the X component should decrease in value
when rolling the vehicle right, the Y component should decrease in value
Earlier versions of ArduPilot did not incorporate the world magnetic model database, and a locations magnetic declination might need to manually entered, or learned through flight. This is not necessary now. In addition, this allows the declination to be continuously updated on long distance flights.
Also, learning the compass offsets in flight, instead of ground calibration, is an option for vehicles difficult to move in order to calibrate. But is not recommended, since the Large Vehicle MagCal option is now available. See Compass Calibration page for details.
Automatic Offset Calibration¶
In the 4.0 releases of ArduPilot, an automatic offset learning feature is available. The COMPASS_LEARN parameter determines how this feature works. This is for advanced users and not recommended.
If set to 3, the offsets will be learned automatically during flight, be saved, and this parameter reset to 0. Position control modes (Loiter, Auto, etc.) should not be used while the offsets are being learned.
Setting COMPASS_LEARN to 1 or 2 is not recommended. These modes are deprecated and are either non-functional, or still in development.
The procedure for COMPASS_LEARN = 3 is:
set COMPASS_LEARN = 3. The message “CompassLearn: Initialised” will appear on the MP’s message tab (it does not appear in red letters on the HUD).
“Bad Compass” will appear but this is nothing to be worried about. We will hopefully make this disappear before the final release.
Arm and drive/fly the vehicle around in whatever mode you like, do some turns “CompassLearn: have earth field” should appear on MP’s message tab and then eventually “CompassLearn: finished”.
You MUST have a GPS lock and signal for this to be successful. Be sure the GPS has a clear “view” of the sky and there are no obstructions blocking the GPS signals.
If you want you can check the COMPASS_LEARN parameter has been set back to zero (you may need to refresh parameters to see this) and the COMPASS_OFS_X/Y/Z values will have changed.
This method can also be evoked using the RCxOPTION for “Compass Learn”. It will activate when the channel goes above 1800uS and automatically complete and save.
Compass error messages¶
Compass Health: The compass has not sent a signal for at least half a second.
Compass Variance: In the EKF solution, compass heading disagrees with the heading estimate from other inertial sensors. Clicking the EKF button on the Mission Planner HUD will show the magnitude of the error.
Compass Not Calibrated: The compass needs to be calibrated.
Compass Offsets High: One of your compass offsets exceeds 600, indicating likely magnetic interference. Check for sources of interference and try calibrating again.