Difference between revisions of "Subsystem/ahrs"
Jump to navigation
Jump to search
| Line 41: | Line 41: | ||
=== Complementary Quaternion (fixed point) === | === Complementary Quaternion (fixed point) === | ||
* Estimates the gyro bias. | * Estimates the gyro bias. | ||
* The version on the master branch is | * The version on the '''master branch is currently not recommended for fixedwings''', as this filter doesn't compensate for centrifugal force when flying turns. | ||
* | * In the dev branch: | ||
** Compensation of centrifugal force (via AHRS_GRAVITY_UPDATE_COORDINATED_TURN which is set by default for a fixedwing firmware). | |||
** GPS based heading estimation: https://github.com/paparazzi/paparazzi/issues/130 | |||
Other flags of interest are: | Other flags of interest are: | ||
Revision as of 05:02, 15 February 2012
AHRS subsystem
The AHRS subsystem specifies which attitude estimation filter you are using.
Currently possible AHRS subsystems are
e.g. for the latest complementary filter:
| File: conf/airframes/myplane.xml |
<firmware name="fixedwing or rotorcraft">
...
<subsystem name="ahrs" type="int_cmpl_quat"/>
</firmware>
|
Implementations
There is a test program ( sw/airborne/test/ahrs/compare_ahrs.py ) to compare different AHRS implementations on simple test cases.
Please also see issue 93 about proper handling of BODY_TO_IMU in all AHRS algorithms.
Complementary Euler (fixed point)
Not recommended for fixedwings, as this filter doesn't compensate for centrifugal force when flying turns.
| File: conf/airframes/myplane.xml |
<firmware name="fixedwing or rotorcraft">
...
<subsystem name="ahrs" type="int_cmpl_euler"/>
</firmware>
<section name="MISC">
<define name="FACE_REINJ_1" value="1024"/> <!-- optional, defaults to 1024 -->
</section>
|
Complementary Quaternion (fixed point)
- Estimates the gyro bias.
- The version on the master branch is currently not recommended for fixedwings, as this filter doesn't compensate for centrifugal force when flying turns.
- In the dev branch:
- Compensation of centrifugal force (via AHRS_GRAVITY_UPDATE_COORDINATED_TURN which is set by default for a fixedwing firmware).
- GPS based heading estimation: https://github.com/paparazzi/paparazzi/issues/130
Other flags of interest are:
- AHRS_PROPAGATE_LOW_PASS_RATES : apply a low pass filter on rotational velocity
- AHRS_MAG_UPDATE_YAW_ONLY : use mag to update yaw only (recommended in most cases, already default in dev branch)
For the latest integer complementary quaternion filter (int_cmpl_quat):
| File: conf/airframes/myplane.xml |
<firmware name="fixedwing or rotorcraft">
...
<subsystem name="ahrs" type="int_cmpl_quat">
<define name="AHRS_MAG_UPDATE_YAW_ONLY"/>
</subsystem>
</firmware>
<section name="AHRS" prefix="AHRS_">
<define name="H_X" value=" 0.51562740288882"/>
<define name="H_Y" value="-0.05707735220832"/>
<define name="H_Z" value=" 0.85490967783446"/>
</section>
|
Also see the Local Magnetic Field section.
Complementary Rotation Matrix (floating point)
- Estimates the gyro bias.
- The version on the master branch is is currently not recommended for fixedwings, as this filter doesn't compensate for centrifugal force when flying turns.
- In the dev branch this is fixed (but untested) and the needed AHRS_GRAVITY_UPDATE_COORDINATED_TURN already set by default for a fixedwing firmware.
- You need to define either AHRS_PROPAGATE_RMAT or AHRS_PROPAGATE_QUAT (select if the propagation is done in rotation matrix or quaternion representation).
Other flags of interest are:
- AHRS_PROPAGATE_LOW_PASS_RATES : apply a low pass filter on rotational velocity
- AHRS_MAG_UPDATE_YAW_ONLY : use mag to update yaw only (recommended in most cases, already default in dev branch)
- AHRS_GRAVITY_UPDATE_NORM_HEURISTIC: lower the gain of the gravity update based on a acceleration norm heuristic (e.g. good for bungee takeoff)
| File: conf/airframes/myplane.xml |
<firmware name="rotorcraft or fixedwing">
...
<subsystem name="ahrs" type="float_cmpl_rmat">
<define name="AHRS_PROPAGATE_RMAT"/>
<define name="AHRS_MAG_UPDATE_YAW_ONLY"/>
</subsystem>
</firmware>
<section name="AHRS" prefix="AHRS_">
<define name="H_X" value=" 0.51562740288882"/>
<define name="H_Y" value="-0.05707735220832"/>
<define name="H_Z" value=" 0.85490967783446"/>
</section>
|
Also see the Local Magnetic Field section.
DCM (floating point)
- No direct gyro bias estimation.
- Similar in principle to the float_cmpl_rmat filter (but less cleanly written).
The main aspects are:
- using the centrifugal force by a rotation with the center in the z axis for calculating the attitude (you can fly circles for long time without any problems). Careful, it doesn't handle all BODY_TO_IMU rotations (mounting positions) correctly! If you like to help out improving this part of the sourcecode contact the paparazzi developers via the mailinglist.
- Correcting the matrix elements of the direction cosine matrix for every calculation step (typ. every 25ms) to archive the orthogonality of the matrix (small errors of the integration and calculations are not accumulated, the algorithm gives almost exact results).
The algorithm was developed by William Premerlani and Paul Bizard. The theory can be found here: DCMDraft2.pdf The algorithm is also used in the AHS systems of the AdruIMU and SparkFun Razor 6DOF IMU.
Other flags of interest are:
- USE_MAGNETOMETER : use magnetometer to update yaw (untested ? The magnetometer code has to be improved, since ferromagnetic materials affect the magnetic field. This is currently not implemented.)
| File: conf/airframes/myplane.xml |
<firmware name="rotorcraft or fixedwing">
...
<subsystem name="ahrs" type="float_dcm"/>
</firmware>
|
Infrared
Local Magnetic Field
To calculate the normalised local magnetic field insert the relevant location coordinates hereand calculate.
Screenshot of noaa page.
Copy the north(x),east(y),vertical(z) component values into scilab and execute "X/norm(X)".
Screenshot of scilab page.
