ImuCalibration

Theory

Accelerometers and Magnetometers calibration is critical for AHRS performances and can be performed using no special hardware. For the magnetometer, it is even very important that the calibration be performed in the fully assembled vehicle, with all systems powered. This is the so-called hard-iron calibration and will allow us to compensate for any constant parasitic magnetic field generated by the vehicle. The calibration process consist in finding a set of neutrals and scale factors for each sensor, such as

${\begin{pmatrix}physical\_value_{x}\\physical\_value_{y}\\physical\_value_{z}\end{pmatrix}}={\begin{pmatrix}sf_{x}&0&0\\0&sf_{y}&0\\0&0&sf_{z}\end{pmatrix}}*({\begin{pmatrix}sensor_{x}\\sensor_{y}\\sensor_{z}\end{pmatrix}}-{\begin{pmatrix}n_{x}\\n_{y}\\n_{z}\end{pmatrix}})$

The principle of the calibration is the following : An accelerometer, on a vehicle at rest measures a constant vector ( the opposite of gravity ) in the earth frame, expressed in the vehicle frame.

$DCM*{\begin{pmatrix}0\\0\\-9.81\end{pmatrix}}={\begin{pmatrix}sf_{x}&0&0\\0&sf_{y}&0\\0&0&sf_{z}\end{pmatrix}}*({\begin{pmatrix}sensor_{x}\\sensor_{y}\\sensor_{z}\end{pmatrix}}-{\begin{pmatrix}n_{x}\\n_{y}\\n_{z}\end{pmatrix}})$

DCM is a rotation matrix that converts between earth frame and body frame. It will change when we change the orientation of the vehicle. Nevertheless, a rotation conserves the norm of a vector. We can thus obtain the following scalar equation that doesn't depend on the vehicle orientation :

$9.81^{2}=(sf_{x}(sensor_{x}-n_{x}))^{2}+(sf_{y}(sensor_{y}-n_{y}))^{2}+(sf_{z}(sensor_{z}-n_{z}))^{2}$

We can then record an important number of measurements in different orientations and find the set of scale factor and neutral giving the norm closest to 9.81

calibration script installation

Paparazzi comes with an application written in the Python language to calibrate the accelerometers and magnetometer. The application can be found in the Paparazzi directory under

sw/tools/calibration/calibrate.py 

For the application to work howver you need additional Python softere, a so called library. If you already have the package paparazzi-dev installed, the needed libs were already installed as dependencies. If this is not the case you need to install python-scipy and python-matplotlib. This can be done via Synaptic or vai the command line of Ubuntu.

$ sudo apt-get install python-scipy
$ sudo apt-get install python-matplotlib

How to use it

• Flash the normal ap firmware if not already on it.

• Switch to the "raw sensors" telemetry mode and launch "server" to record a log.

• You really need to get the min/max on each axis.
  • To calibrate the accels turn the imu on all six sides of the cube ( upright, inverted, on nose, on tail, on right side, on left side ). You can also take some measurememts banking 45 degres.
    Try to get an homogeneous distribution of your measurements. I find it better to let the quad rest while measuring.
  • The most crucial part for the mag calibration. You really need to get the min/max on each axis, so align the mag axes along the local magnetic field vector and not just take the same orientations as when calibrating the accels... you can plot the values to see you get the maximum.

• You can then run the python script to get your calibration coefficients, e.g. for accelerometer calibration:

sw/tools/calibration/calibrate.py -i <your_ac_id> -s ACCEL <path_to_data_file var/logs/xxxxxxx.data>

(To get the ac_id, just open the *.data file - second column)

How it works

• It first makes an initial guess using min and max, ie for each axis
  • neutral = 0.5 * (max + min)
  • sensitivity = 0.5*(max-min)

• It then uses a datafit algorithm to optimise the initial guess

Screenshot of scilab version.

Note for magnetometer: Because the magnetic field changes depending where on the globe you are, you will have to recalibrate your mag to fly somewhere else. When you move the quad to different positions for logging make sure you align it along the direction of the magnetic field which will result in the maximum values for each axis ( or you can look up the inclination and declination of the magnetic field where you live here).

Normalised magnetic fields for int_cmpl_quat AHRS filter

See the Complementary Quaternion (fixed point) AHRS subsystem page for details.

Finding Signs

For supported IMUs, the correct default signs are already defined in the code. If using a new IMU or sign for yours are not in the code yet, here is the way to find them.

We're calibrating everything relative to the IMU frame - Paparazzi has a parameter to define the orientation of the IMU with respect to the body of the vehicle that we'll use later, once you'll have decided of a good mechanical mounting.

Paparazzi uses North East Down (NED) frame, that is positive x is pointing to the front, positive y to the right and positive z down.

Accelerometer:

An accelerometer measures the non gravitational acceleration, that is ${\ddot {x}}-g$. $g$ is pointing down, so $-g$ is pointing up. So stop moving, disregard earth rotation and you'll measure $-g$.

• When your IMU is level you should see x=0 y=0 z=-9.81
• When pitching up -g is aligning with x, so you should see x>0, y=0 and z<0
• When banking left -g is aligning with y, so you should see x=0, y>0 and z<0

Magnetometer:

A magnetometer measures the Earths magnetic vector. In the Northern hemisphere this points North and down and in the Southern hemisphere North and up.

Thus in the Northern hemisphere:

• When you align your IMU with the direction of north, you should see x>0, y=0, z>0
• when pitching down the IMU, the magnetic vector is aligning with x, so x should increase and z should decrease to zero.
• if yawing your IMU to the left, the magnetic vector is aligning with y, so y should be positive, x should decrease to zero and z stay positive

And in the Southern hemisphere:

• When you align your IMU with the direction of north, you should see x>0, y=0, z<0
• when pitching up the IMU, the magnetic vector is aligning with x, so x should increase and z should increase towards zero.
• if yawing your IMU to the left, the magnetic vector is aligning with y, so y should be positive, x should decrease to zero and z stay negative

Gyrometer:

You need some turntable to calibrate the scale factors of your gyros. For signs, the definition of the frame give the following properties:

• when rolling right, $p$ should be positive
• When pitching up, $q$ should be positive
• When yawing to the right, $r$ should be positive

Verification:

Switch to AHRS telemetry mode and look for the fields that are prefixed with imu_

• bank righ should give positive phi
• pitch up should give positive theta
• yaw right should give increasing psi

• the value you'll see after letting the IMU rest will end up being the "measure" ( that is accelerometer and mag ). If those are wrong the problem is in the calibration of your sensors
• the values you get while moving the IMU are influenced by the gyros. If what you see is the value going crazy when you move, then stabilizing to something good after you stop moving, the problem is in your gyros.

Body to IMU rotation

Provision is made within the software to physically locate supported IMUs in orientations with respect to the aircraft/rotorcraft frame which suit available mounting options.

• The in-line, parallel mount example:

Configured as:

File: conf/airframes/myplane.xml

<define name="BODY_TO_IMU_PHI" value="RadOfDeg( 0. )"/> <define name="BODY_TO_IMU_THETA" value="RadOfDeg( 0. )"/> <define name="BODY_TO_IMU_PSI" value="RadOfDeg( 0. )"/>

As noted further above, calibration and sign verification procedures are carried out relative to the IMU frame, hence defines should be left at zero until they are completed.

• The positive 90 degree offset, parallel mount example:

Configured as:

File: conf/airframes/myplane.xml

<define name="BODY_TO_IMU_PHI" value="RadOfDeg( 0, )"/> <define name="BODY_TO_IMU_THETA" value="RadOfDeg( 0. )"/> <define name="BODY_TO_IMU_PSI" value="RadOfDeg( 90. )"/>

• Another variation might include turning the IMU upside down in the parallel plane:

Configured as:

File: conf/airframes/myplane.xml

<define name="BODY_TO_IMU_PHI" value="RadOfDeg( 180.)"/> <define name="BODY_TO_IMU_THETA" value="RadOfDeg( 0. )"/> <define name="BODY_TO_IMU_PSI" value="RadOfDeg( 0. )"/>

In Flight Tuning

• Switch to AHRS telemetry mode and look for the fields that are prefixed with imu_

90 degree positive offset example

• Open a Real_time plotter from the paparazzi console tools tab and drag int32 body_phi and int32 body_theta into the plotter box.

• Hover rotorcraft (preferably indoors) to record data.

• Copy the (best fit) recorded values into the airframe BODY_TO_IMU defines:

File: conf/airframes/myplane.xml

<define name="BODY_TO_IMU_PHI" value="RadOfDeg( 1.5)"/> <define name="BODY_TO_IMU_THETA" value="RadOfDeg( -0.5 )"/> <define name="BODY_TO_IMU_PSI" value="RadOfDeg( 90. )"/>

• Ignore 'on the ground' resting values as depicted in the above image. They will change once the vehicle is in flight. The aim is to get the 'in flight' values of "int32 body_phi" & "int32 body_theta" as close to zero as possible.