<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Tools</categorytree>
__TOC__

The <tt>tcp aircraft server</tt> (in <tt>sw/tools/tcp_aircraft_server/</tt>) is an agent that re-broadcasts the ivy telemetry stream from a specified vehicle over tcp to a specified remote ip which hosts its own local ground segment ivy network. This allows the broadcast of a vehicle telemetry stream over the internet to a remote party without the need for VPNs.

== Usage ==

=== Broadcast Ground Station ===

Set your Paparazzi src and home directories for eg:
export PAPARAZZI_SRC=~/path/to/paparazzi
export PAPARAZZI_HOME=~/path/to/paparazzi

Then, from your Paparazzi directory, run:
./sw/ground_segment/tmtc/ivy_tcp_aircraft -id <ac_id_number> -h <remote IP>

=== Recipient Computer ===

Run:
./sw/tools/tcp_aircraft_server/tcp_aircraft_server.py

Then open [http://wiki.paparazziuav.org/wiki/Paparazzi_Center Paparazzi Center] using the -n option for the [http://wiki.paparazziuav.org/wiki/Server Server] unless you wish to log messages locally, and use the tools within Paparazzi Center as you would do normally.

The recipient side of the setup broadcasts locally over the default Paparazzi ivy bus 127.255.255.255:2010

[[Category:Tools]] [[Category:User_Documentation]]

Psinha: /* Aspirin IMU */

== Paparazzi IMU ==

'''IMU''' = inertial measurement unit: only measures the accelerations and rotation rates (and magnetic field)
'''AHRS''' = attitude and heading reference system: uses IMU data + extra (airspeed/GPS/baro/...) to do sensor fusion and provide pitch and roll
'''INS''' = integrated navigation system: uses IMU + Navigation sensor(s) (e.g. GPS) + even more complex algorithms that besides pitch and roll also interpolates positions and velocities using the attitude corrected acceleration measurements.

=== Booz IMU v 1.2 ===

*High quality analog devices sensors
*16bit ADC capable of 200 000 samples per second
*Special attention to clean power with onboard linear supplies
*Efficient high-speed SPI for minimal microcontroller overhead and ultra-low latency (=better controller performance).
*Fits on Booz, Lisa AND Tiny/TWOG autopilots.

While originally designed for use with rotorcrafts, code is now available for use with fixed wing.

[[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].

=== YAI v1.0 ===

Why "yet another imu" while there are already so many out there?

[[Image:yai_assemb.jpg|240px]]

*Designed to be completely compatible with original booz IMU and its code
*Cheaper sensors (lower bias stability)
*Higher resolution (16bits) and frequency (200ksps) and cleaner onboard power supply, better grounding and shielding than compared with e.g. external sparkfun breakout boards
*Fast low latency SPI communication (no uart as the tiny/twog miss uarts)
*The most important part of attitude determination is proper kinematic compensation using for instance GPS, pressure sensors etc etc. When using IMU with external processors there is often less flexibility. Things as timing for instance are as important as the quality of the gyros themselves.

Board, BOM -> [ http://svn.savannah.nongnu.org/viewvc/paparazzi-hardware/trunk/sensors/yai/?root=paparazzi Hardware Repository]

=== Aspirin IMU ===

[[Image:Aspirin_imu_front.jpg|240px]]

[[AspirinIMU|Next generation flat imu.]] This little imu with latest generation of integrated high rate high resolution gyros's moreover has very low noise and stable power supplies and outputs all sensors interrupt pins for optimal performance.

Note: while the main intended use is the very low latency high performance spi+i2c+interrupts connection (e.g. on lisa/M), please note that aspirin v2 can also be used with any tiny/twog for fixedwing aircraft with the same 4-wire interface and identical software as the PPZUAV-IMU. (connect Aspirin-SCK and aspirin-SCL to the I2C-SCL, aspirin-mosi and aspirin-SDA to I2C-SDA, Vcc to 5V (preferably linear), aspirin-gnd and aspirin-miso to GND, and aspirin-CS to 3.3V.)

Detailed information about the [[AspirinIMU|Aspirin IMU]] is available [[AspirinIMU|here.]]

== 3rd Party IMU ==

'''Loose Terminology Note:''' Like the sparkfun website, the following text incorrectly equates the term "degree-of-freedom" with sensor measurement. Unless we're talking about articulated arms (which paparazzi to date isn't involved with), a body can only have 6 physical DOFs and that would correspond to translation and rotations in the x,y,z cartesian directions of 3D space. If the vehicle state vector includes positions and velocities for each degree of freedom, the state vector would have a dimension of 6 x 2 = 12 states. The goal is to reconstruct these vehicle states using sensor measurements, as once the states can be obtained with reasonable certainty, a control algorithm can have a shot at controlling the system. Using various filtering techniques, multiple sensor types can be combined to estimate these states.

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.

=== PPZUAV IMU 9DOF ===
<gallery>
Image:Ppz9dofimu.jpg|9DOM IMU
Image:Ppz9dofimumed.jpg|Example Wiring to Tiny2.11
Image:Ppz9domschematic.jpg|Schematic
</gallery>

<p>
Possibly the smallest Paparazzi IMU/sensor board available.<br>
Features: I2C out 5v input. Interrupts Testing now. So far so good. It's open like Paparazzi.<br>
PCBs available for a few dollars. Schematic open, design is Altium Designer, gerbers available.<br>
</p>
<p>There is a module to just read the raw sensor data that can be added to any working airframe:<br>
<pre>
<modules>
<load name="ins_ppzuavimu.xml" />
</modules>
</pre>

but to use it for flying you need to add a little more to your airframe. you will need to add the <subsystem name="imu" type="ppzuavimu" /> to read the sensor, but also a filter to merge the data like for instance the <subsystem name="ahrs" type="ic" /> which is a fast integer complementary 3D filter. But besides that you need to add sensor calibration defines to your airframe, and preferably also the local magnetic field vector at your location. A sample airframe illustrating all calibration issues and reading and merging the sensor at 100Hz with minimal control delays is in the repository to get you started:

airframe: PPZUAV/fixedwing/tiny_imu.xml
settings: tuning_basic_ins.xml
telemetry: default_fixedwing_imu.xml

Credit and thanks go out to Christophe for making the code and testing.
</p>
<p>Media
YouTube: http://www.youtube.com/watch?v=OaMTyJ-s-PU
<br style="clear:both">

=== Ryan Mechatronics CHIMU AHRS ===

Very nice product: using the ultra high speed ultra low latency 200Hz SPI-slave mode (even 200Hz innerloop control of fixedwing is possible) or simple 4-wire connection via serial port to any TWOG/TINY/LISA/YAPA.

Don't want to spend time testing AHRS filters? Nor calibrating IMU? This module with molex connector can be bought calibrated and does all the filtering internally.

Use it with highspeed SPI on LPC-based boards: http://www.youtube.com/watch?v=mxx-f3Ur0L8

<modules>
<load name="ins_chimu_spi.xml" />
</modules>

...

<subsystem name="spi_slave_hs"/>

Use CHIMU with simple uart connection on both lisa or tiny/twog

<modules>
<load name="ins_chimu_uart.xml">
<configure name="CHIMU_UART_NR" value="0"/>
</load>
</modules>

=== 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 and the series resistors to the MC of the 5V analog inputs. The code to fly normal plane is currently in the repository. Christoph is working on improvements look here: http://paparazzi.enac.fr/wiki/User:Christoph

[[Media:Wiring_Razor_IMU.pdf|Connections and wiring to the tiny13]]

<br style="clear:both">

=== SparkFun SEN-10121 ===
IMU Digital Combo Board - 6 Degrees of Freedom ITG3200/ADXL345
http://www.sparkfun.com/products/10121

Details of configuring the [http://paparazzi.enac.fr/wiki/IMU/SEN-10121 SEN-10121] can be found [http://paparazzi.enac.fr/wiki/IMU/SEN-10121 here]

=== 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]

[[ArduIMU|Paparazzi Wiki Page]]

* 3 axis accelerometer + 3 axis gyroscope
* Low cost
* Has been integrated in Paparazzi by ZHAW, Winterthur, Switzerland.
* A magnetometer has been integrated in the software to compensate drift in yaw.
* GPS data from the Tiny is passed over I2C to the AHRS on the IMU.
* Is sold by [http://www.sparkfun.com/products/9956 Sparkfun] and [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]

There is a [[Modules|module]] for this AHRS (ins_vn100.xml for fixedwings).

<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]

In sensor fusion, calibration and timing are crucial. If you want latency compensated ADXRS gyro integrated attitude done by an efficient and optimized Blackfin DSP you need an XSens. For rotorcraft the 100Hz is a bit slow, but for fixedwing it's perfect. Directly compatible with [[Yapa]] and [[Lisa]] and all needed code in paparazi.

<br style="clear:both">

=== MemSense MAG3 ===

MAG3 - 6 DOF Analog IMU with Triaxial Magnetometer

[http://www.memsense.com/index.php/Product-Pages/mag3-worlds-smallest-analog-inertial-measurement-unit.html Official website mag3]

== 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 [http://en.wikipedia.org/wiki/Specific_force "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). This situation can also occur in plane flying in very strong winds.

The theory of the DCM algorithm (used in Paparazzi for the AdruIMU and Razzor hardware) can be found here:[[Media:DCMDraft2.pdf|DCMDraft2.pdf]]
[[Category:Hardware]]