Difference between revisions of "Inertial Measurement Units"

From PaparazziUAV
Jump to navigation Jump to search
(Redirecting to Sensors/IMU)
 
(29 intermediate revisions by 11 users not shown)
Line 1: Line 1:
== Paparazzi Booz IMU ==
#REDIRECT [[Sensors/IMU]]
 
Work is underway to use Kalman code from the Booz project with the Tiny autopilots. The first IMU have been assembled and are being calibrated. Look for updates soon.
 
The IMU will communicate over SPI with the TWOG/Tiny2.11
 
[[Image:IMU001.jpg|240px]]
 
The hardware description is [[BoozIMU|here]].
 
Available at [https://mini.ppzuav.com/osc/product_info.php?cPath=15&products_id=122&osCsid=bq9cget2u5c7ksa6kd9ssdf03lisuksq PPZUAV].
 
== 3rd Party IMU ==
 
IMU's measure rotation rates, acceleration (6DOF) and some also magnetic fields (9DOF). This data is used by an autopilot to estimate the state of the aircraft. They that can be used with a Paparazzi autopilot based UAS. If you happen to have such a device, we really would love to see that you share your IMU paparazzi autopilot integration projects information on this Wiki.
 
=== SparkFun Razor 6DOF IMU ===
 
[[Image:RazzorIMU.jpg|thumb|left|Razor IMU (top) with the tiny13 autopilot]]
 
[[Image:RazzorIMUb.jpg|thumb|left|Razor IMU in the tiny13 autopilot box]]
 
[http://www.sparkfun.com/commerce/product_info.php?products_id=10010  Official website]
 
6DOF - Ultra-Thin IMU
 
Very cheap, currently 62-72 Euro.  [http://www.watterott.com/de/Sensoren/IMU Shop in Europe]
 
 
Has been integrated in Paparazzi by Hochschule Bremen, Germany.
 
Remove the high pass filters of the RazorIMU to get better results.
 
For the Twog and Tiny 2.2 autopilots you have also remove the resistors to GND of the 5V analog inputs. 
 
More infos are in the branch HB in the paparazzi SVN.
 
[[Media:Wiring_Razor_IMU.pdf|Connections and wiring to the tiny13]]
 
<br style="clear:both">
 
=== Cloudcap Crista IMU ===
[[Image:crista_sensorhead.jpg|thumb|left|Christa IMU]]
 
[http://www.cloudcaptech.com/crista_sensorhead.shtm Official website]
 
More infos soon.
 
<br style="clear:both">
 
== 3rd Party INS ==
 
INS measure rates with their sensors and run algorithms to estimate the state on their own. They give this information the the autopilot (e.g. Euler angles) that can then use it for navigation.
 
===[http://diydrones.com/profiles/blogs/arduimu-v2-flat-now-available|DIYDrones ArduIMU+ V2 (Flat)] ===
[[Image:ArduIMU.jpg|thumb|left|ArduIMU]]
 
[http://code.google.com/p/ardu-imu/wiki/HomePage?tm=6 Official website]
3 axis Accelerometer + 3 axis Gyroscope.
 
Very cheap
Has been integrated in Paparazzi by ZHAW, Winterthur, Switzerland.
* A magnetometer has been integrated in the software to compensate drift in yaw.
* GPS from the Tiny is passed over I2C to the AHRS on the IMU
More info on integration can be found [[ArduIMU|here]].
Where can I buy ArduIMU?
<br>
[http://www.sparkfun.com/products/9956 Sparkfun]
<br>
[http://store.diydrones.com/ProductDetails.asp?ProductCode=KT-ArduIMU-20 DIYDrones Store]
<br style="clear:both">
 
=== Vector-Nav VN-100 ===
[[Image:VN-100.jpg|thumb|left|Vector-Nav VN-100]]
 
[http://www.vectornav.com/vn-100-features Official website]
 
More infos soon.
 
<br style="clear:both">
 
=== MicroStrain 3DM-GX2 ===
[[Image:3DM-GX2.jpg|thumb|left|MicroStrain 3DM-GX2]]
 
[http://www.microstrain.com/3dm-gx2.aspx Official website]
 
More info soon.
 
<br style="clear:both">
 
=== Xsens MTi and MTi-G (with GPS) ===
[[Image:MTi.jpeg|thumb|left|Xsens MTi]]
 
[[Image:MTi-G.jpeg|thumb|left|Xsens MTi-G (with GPS)]]
 
[http://www.xsens.com/en/general/mti Official website MTi]
 
[http://www.xsens.com/en/general/mti-g Official website MTi-G]
 
More info soon.
 
<br style="clear:both">
 
== The Very Short Essential Introduction To Inertial Attitude Estimation ==
 
The only physical entity related to attitude (pitch and roll) is the earth gravity vector (unless you use a multi-antenna phase-measuring GPS... $$$$). Unfortunately, the sensors that measure gravity (=accelerometers) also measure so-called kinematic accelerations or in other words: changes in speed: like centrifugal forces, Coriolis forces, linear accelerations etc... The sum of all these litteraly is "what you feel" and is called "specific force".
 
so
 
  accelerometer_value (specific force) = earth_gravity + change in velocity (linear accelerations) + velocity times turn rate (centrifugal etc)
 
or
 
  A = B + C + D 
 
You measure A and want to know B. What all "gyroscopes and accelerometer only" AHRS projects are doing in some way or another is to neglect the last 2 (C and D). In many situations this is not bad: for instance: when testing the AHRS attached to your computer: it can not accelerate for a very long time (at most a few meters: so if you accerate to the left, then you need to accelerate to the right directly after so the average is zero) and can not rotate to much either (or your cable gets strangled). This is why all AHRS videos on youtube look perfect. And on the desk they are perfect: you neglected 2 terms in the equation that in that situation are perfectly neglect-able. Also with a quadrotor that hovers and keeps its nose in the same direction all the time, these neglected terms are small.
 
Now what about the gyroscopes you might ask. I deliberately keep them only second as gyroscopes (turn rate or rotation speed sensors) do NOT give you attitude but ONLY HELP TO SOLVE SHORT TERM errors in the previous part. If gyroscopes would measure turn-rate perfectly, then they would help more but all MEMS/PIEZZO sensors are more or less sensitive to 1) temperature, 2) turnrate, 3) vibrations, 4) accelerations, 5) radiation, 6) power supply quality 7) non-linearity 8) ADC-quality 9) dynamic range and saturation problems, ... so if you integrate gyroscopes, sooner or later errors build up (drift). I put this list here so you know what to pay attention for: if using gyroscopes: always try to keep the temperature as constant as possible or let the temperature settle, reduce vibrations (dampers), use better ADC (e.g. 10bit ADC with +/- 1200 deg/sec gyros have a resolution of 2.4 degrees/s per ADC tick, so your phi/theta might drift 1.2deg/sec without noticing) and power supply filtering and shielding etc to start with. All of these define for how long (seconds!/minutes?) gyroscope integration is useful.
 
If you convert the accelerometer directly to attitude and plot it, it will vibrate a lot and will show errors when you accelerate the AHRS on your desk. During a coordinated turn of a fixedwing plane, the force you feel is perpendicular to the plane (not pointing to earth). The accelerometer only clearly is insufficient to know your attitude. One solution is to use gyroscopes that are so good that you can predict for many minutes (then the average acceleration during several turns would still point to earth). But if your gyros can only help for shorter terms (like all MEMS sensors of less than 500euro/each) then extra information is required. E.g: if you add GPS data or airspeed data however, from the flightpath you can quite accurately reconstruct the missing C and D terms. Together with the accelerometer you can know "where the earth is" even when you keep accelerating and turning. Here questions like latency, update rate, noisy derivatives (linear acceleration) are of importance.
 
Finally there is the heading... GPS ground-track is not the same as nose direction. Gyroscopes measure how much the nose has been turning, so using GPS to correct it induces errors that increase with corsswind. Magnetometers can help here, and become necessary whenever you do not move enough anymore (hovering).

Latest revision as of 03:38, 18 December 2011

Redirect to:

Retrieved from "http://wiki.paparazziuav.org/w/index.php?title=Inertial_Measurement_Units&oldid=11091"