PaparazziUAV - User contributions [en]

Inertial Measurement Units

2011-11-15T23:35:07Z

Bendespain: /* 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.)

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


Possibly the smallest Paparazzi IMU/sensor board available. 
Features: I2C out 5v input. Interrupts Testing now. So far so good. It's open like Paparazzi. 
PCBs available for a few dollars. Schematic open, design is Altium Designer, gerbers available. 

There is a module to just read the raw sensor data that can be added to any working airframe: 
<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.

Media
YouTube: http://www.youtube.com/watch?v=OaMTyJ-s-PU
 

=== Ryan Mechatronics CHIMU ===

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:

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

 

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

 

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

=== 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).

 

=== MicroStrain 3DM-GX2 ===
[[Image:3DM-GX2.jpg|thumb|left|MicroStrain 3DM-GX2]]

[http://www.microstrain.com/3dm-gx2.aspx Official website]

More info soon.

 

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

 

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

[[Category:Hardware]]

Modems

2011-11-01T23:43:16Z

Bendespain: /* Pinout */

The Paparazzi autopilot features a 5V tolerant 3V TTL serial port to interface with any common radio modem. The bidirectional link provides real-time telemetry and in-flight tuning and navigation commands. The system is also capable overlaying the appropriate protocols to communicate thru non-transparent devices such as the Coronis Wavecard or Maxstream API-enabled products, allowing for hardware addressing for multiple aircraft or future enhancements such as data-relaying, inter-aircraft communication, RSSI signal monitoring and automatic in-flight modem power adjustment. Below is a list of some of the common modems used with Paparazzi, for details on configuring your modem see the [[Airframe_Configuration#Telemetry_.28Modem.29|Airframe Configuration]] and [[XBee_configuration|XBee Configuration]] pages.

== Digi XBee modules ==

Digi (formerly Maxstream) offers an increasing variety of Zigbee protocol modems well suited for Paparazzi in 2.4 GHz, 900MHz and 868Mhz frequencies. The "Pro" series are long range, up to 40km! Standard series are slightly smaller/lighter/lower power consumption and very short range. All versions are all pin compatible and weigh around 2 grams with wire antennas. All Digi modems can be operated in transparent mode (as a serial line replacement) or in "API mode" with hardware addressing, managed networking, and RSSI (signal strength) data with the Paparazzi "Xbee" option. Three antenna options are offered: the SMA version is ideal for ground modems, wire antennas for aircraft, and chip antennas for those with very limited space.

* XBee (PRO) ZB (the current series)
* XBee (PRO) ZNet 2.5 (formerly Series 2) (only legacy -> use XBee-PRO ZB)
The XBee & XBee-PRO ZB share hardware (ember stack) with XBee & XBee-PRO ZNet 2.5. As a result, modules can be "converted" from one platform to another by loading different firmware onto a given module.

These two also share the same hardware and can be converted from one to another by flashing a different firmware:
* XBee-PRO 802.15.4 (formerly Series 1)
* XBee-PRO DigiMesh 2.4

'''Note: Modules based on Freescale chipset (formerly Series 1) are not compatible with Ember chipset based modules (Series 2).'''
Also see the [http://www.jsjf.demon.co.uk/xbee/faq.htm| unofficial XBee FAQ] for this.

See the [[XBee_configuration|XBee Configuration]] page. This [http://pixhawk.ethz.ch/tutorials/how_to_configure_xbee tutorial] is also good to configure and get started with XBee Pro.

=== Module Comparison ===
{|border="1"
|-valign="top"
||'''Module'''||'''Point-to-Multipoint'''||'''ZigBee/Mesh'''||'''Chipset'''|||'''Software stack'''||'''Frequency'''||'''TX Power normal/PRO'''||'''Notes'''
|-
|'''XBee ZB'''
|
|yes
|Ember
|EmberZNet PRO 3.1 (ZigBee 2007)
|2.4 GHz
|2mW/50mW
|coordinator needed
|-
|'''XBee ZNet 2.5'''
|
|yes
|Ember
|EmberZNet 2.5 ZigBee
|2.4 GHz
|2mW/50mW
|(only legacy -> use XBee-PRO ZB) coordinator needed
|-
|'''XBee DigiMesh 2.4'''
|
|yes
|Freescale
|
|2.4 GHz
|
|all nodes equal (no special coordinators/routers/end-devices)
|-
|'''XBee 802.15.4'''
|yes
|
|Freescale
|
|2.4 GHz
|
|
|-
|'''XBee-PRO 868'''
|yes
|
|?
|
|868 MHz
|500mW
|Only High Power Frequency allowed in the UK. 2.4GHz limited to 10mW
|}

==== Comparison Conclusion ====

(Copied from DIGI manual)

''If the application strictly needs to communicate in a point-to-point or a point-to-multipoint
fashion, 802.15.4 will be able handle all the communications between your devices and will
be simpler to implement than trying to use a module with ZigBee firmware to accomplish the
same goal. ZigBee is necessary if you need to use repeating or the mesh networking
functionality.''

-Interpretation for paparazzi: if inter-aircraft communication is required one should go for the zigbee ZB series 2 modules.

==== Pinout ====

[[Image:Maxstream_Xbee_pinout.jpg|left|thumb|Maxstream XBee pinout]]
 

{|border="1"
|-valign="top"
||''Xbee 20-pin Header''||''Name''||''Notes''||''Suggested Color''||
|-
|1
| +3.3v
| Power
|Red
|-
|2
|DOUT
|Tx output - connect to Autopilot Rx
|Green
|-
|3
|DIN
|Rx input - connect to Autopilot Tx
|Blue
|-
|10
|GND
| Ground
|Black
|}

The image view is from above, top, thus NOT at the side where the connector pins come out

Note : DTR and RTS need to be wired for upgrading firmware

=== GCS Adaptation ===

There are several vendors of hardware to connect the ground XBee radio modem to the GCS computer.

====Adafruit====

[[Image:xbeeadapter_LRG.jpg|thumb|left|Adafruit XBee adapter board]][[Image:xbeeadapterftdi_LRG.jpg|thumb|Adafruit XBee adapter with FTDI cable]]
[http://www.adafruit.com/index.php?main_page=product_info&cPath=29&products_id=126 Adafruit] (yes, that really is their name) offers a great adapter board kit for the Xbee modules that includes a 5-3.3V voltage regulator, power and activity LEDs, and pins to connect directly to your FTDI cable for $10! Some assembly required.

 

====Droids====

[[Image:XBee_Simple_Board.jpg|thumb|left|XBee Simple Board]]

[[Image:XBee_USB_Board.jpg|thumb|left|XBee USB Board]]

[http://www.droids.it/cmsvb4/content.php?143-990.001-XBee-Simple-Board XBee Simple Board]

Simpler, lighter, smaller footprint, bit more expensive, comes assembled and tested. --GR

[http://www.droids.it/cmsvb4/content.php?152-990.002-XBee-USB-Board XBee USB Board]

For direct connection to USB (no FTDI cable required)

 

====PPZUAV====

[[Image:FTDI_Utility_Board.jpg|thumb|left|FTDI Utility Board 1.0‎]]

[https://mini.ppzuav.com/osc/product_info.php?cPath=13&products_id=111 ppzuav.com]

FTDI Utility Board 1.0 (no FTDI cable required)

 

====Sparkfun====

[[Image:XBee_Explorer_USB.jpg|thumb|left|XBee Explorer USB]]

[http://www.sparkfun.com/products/8687 sparkfun.com]

XBee Explorer USB (no FTDI cable required)

 

=== Digi XBee Pro DigiMesh / 802.15.4 ("Series 1") ===
*Note: Products based on XBee ZNet 2.5 (formerly Series 2) modules do not communicate with products based on XBee DigiMesh / 802.15.4 (formerly Series 1) modules.

These relatively cheap and light modules implement the [http://www.zigbee.org/en/index.asp ZigBee/IEEE 802.15.4] norm. They allow up to 1.6km (1 mile) range (Paparazzi tested to 2.5km (1.5 miles)). The main drawback of using such 2.4Ghz modules for datalink is that it will interfere with the 2.4Ghz analog video transmitters and a inevitable decrease in range when in proximity to any wifi devices. For the plane, get the whip antenna version if you are not planning to build a custom antenna.

{|
|-valign="top"
|[[Image:Xbee_Pro_USB_RF_Modem.jpg|thumb|left|XBee Pro USB Stand-alone Modem (XBP24-PKC-001-UA)]]
|
* Frequency Band 2.4Ghz
* Output Power 100mW (Xbee Pro)
* Sensitivity -100 dBm
* RF Data Rate Up to 250 Kbps
* Interface data rate Up to 115.2 Kbps
* Power Draw (typical) 214 mA TX / 55 mA RX
* Supply Voltage 3.3v
* Range (typical, depends on antenna & environment) Up to 1500m line-of-sight
* Dimensions 24 x 33mm
* Weight 4 grams
* Interface 20-pin mini connector
* Chip antenna, ¼ monopole integrated whip antenna or a U.FL antenna connector (3 versions)
* Price: Approximately $32
|
[[Image:XBee_pro.jpg|thumb|left|XBee Pro OEM Modem]]
|}
Mouser: [http://au.mouser.com/Search/ProductDetail.aspx?qs=sGAEpiMZZMtJacPDJcUJYzVn8vIv7g2fIpf5DCzJqko%3d 888-XBP24-PKC-001-UA] 
NOTE: If you wish to use this unit with another XBee type other than the 802.15.4 (i.e. XBee-PRO ZB) then purchase a modem with the U.fl connector.

==== Documentation ====

* [http://www.maxstream.net/products/xbee/xbee-pro-oem-rf-module-zigbee.php product page]
* [http://www.maxstream.net/products/xbee/datasheet_XBee_OEM_RF-Modules.pdf datasheet]
* [http://www.maxstream.net/products/xbee/product-manual_XBee_OEM_RF-Modules.pdf user manual]
* To program your Xbee you need X-CTU you can download it [http://www.digi.com/support/productdetl.jsp?pid=3352&osvid=57&tp=5&s=316 here]. (only windows)
* explanation on X-CTU [http://www.ladyada.net/make/xbee/configure.html here].
* [http://ftp1.digi.com/support/firmware/update/xbee/ Drivers for XB24 and XBP24 modules]

=== Digi XBee Pro ZB / ZNet 2.5 ("Series 2") ===

The low-power XBee ZB and extended-range XBee-PRO ZB use the ZigBee PRO Feature Set for advanced mesh networking.

{|
|-valign="top"
|[[Image:XBee_Pro_2SB.jpg|thumb|left|Digi XBee Pro ZB]]
|
* Low-cost, low-power mesh networking
* Interoperability with ZigBee PRO Feature Set devices from other vendors*
* Support for larger, more dense mesh networks
* 128-bit AES encryption
* Frequency agility
* Over-the-air firmware updates (change firmware remotely)
* ISM 2.4 GHz operating frequency
* XBee: 2 mW (+3 dBm) power output (up to 400 ft RF LOS range)
* XBee-PRO: 50 mW (+17 dBm) power output (up to 1 mile RF LOS range)
* RPSMA connector, U.FL connector, Chip antenna, or Wired Whip antenna
* price : ~34 USD
|
|}
These are available from Mouser: 
[http://au.mouser.com/Search/Refine.aspx?Keyword=888-XBP24-Z7WIT-004 888-XBP24-Z7WIT-004] XBee-PRO ZB with whip antenna 
[http://au.mouser.com/Search/Refine.aspx?Keyword=XBP24-Z7SIT-004 888-XBP24-Z7SIT-004] XBee-PRO ZB with RPSMA

See [[XBee_configuration|XBee Configuration]] for setup.

==== Documentation ====
* [http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp]

=== Digi XBee Pro 868 ===

'''WARNING - THESE MODEMS HAVE A 10% DUTY CYCLE, AND CURRENTLY HAVE SEVERE ISSUES WITH PAPARAZZI'''

868MHz is a limited band. Please read the [[868MHz Issues]]

XBee-PRO 868 modules are long range embedded RF modules for European applications. Purpose-built for exceptional RF performance, XBee-PRO 868 modules are ideal for applications with challenging RF environments, such as urban deployments, or where devices are several kilometers apart.

{|
|-valign="top"
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro 868]]
|
* 868 MHz short range device (SRD) G3 band for Europe
* Software selectable Transmit Power
* 40 km RF LOS w/ dipole antennas
* 80 km RF LOS w/ high gain antennas (TX Power reduced)
* Simple to use peer-to-peer/point-to-mulitpoint topology
* 128-bit AES encryption
* 500 mW EIRP
* 24 kbps RF data rate
* price : ~70 USD
|
|}

See [[XBee_configuration#XBee_Pro_868_MHZ|XBee Configuration]] for setup.

==== Documentation ====
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp]

=== Digi XBee Pro XSC 900MHz ===

Maxstream has recently announced a promising new line of modems combining the small size and low cost of their popular Xbee line with the long range and 2.4 GHz video compatibility of their high end 900 MHz models. Sounds like the perfect modem for anyone who can use 900 MHz. Give them a try and post your results here!
{|
|-valign="top"
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro XSC]]
|
* Frequency Band 900 MHz
* Output Power 100 mW (+20 dBm)
* Sensitivity -100 dBm
* Data Rate: 9600 bps
* Range (typical, depends on antenna & environment) Up to 24km (15 miles) line-of-sight
* Interface 20-pin mini connector (Xbee compatible pinout)
* RPSMA, integrated whip antenna or U.FL antenna connector (3 versions)
* price : ~75 USD
|
|}

==== Documentation ====
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp]
==== Trials ====
Tested one today and it worked great. Going to try a multiUAV test with it soon
--Danstah
 
 
MultiUAV tests concluded this is probably not the best module to use. Even though it says you can change the baudrate inside x-ctu that is not the case, it is fixed at 9600 bps. This is a great modem however for single UAV's and I do recommend.
--Danstah
 
 
Why would the European (868 MHz) be good to 24kbps and this only to 9600? When I was altering my XBees (2.4Ghz Pro's) I had this problem altering baud rates until I read you have to send a "commit and reboot" type command after setting the baud rate. Could this be the case? --GR

== Maxstream 9XTend ==

These larger units have been tested on the 900Mhz band, but are also available in 2.4Ghz. They are a bit on the heavy side, about 20 grams, but give good performance at range. They have adjustable transmit power settings from 100mW to 1W. Testing has shown range up to 5.6km (3.5 Miles) with XTend set to 100mW with small 3.1dB dipole antenna.

{|
|-valign="top"
|
[[Image:XTend_USB_RF_Modem.jpg|frame|left|9XTend USB Modem]]
|
* Frequency Band 900Mhz and 2.4Ghz (2 versions)
* Output Power 1mW to 1W software selectable
* Sensitivity -110 dBm (@ 9600 bps)
* RF Data Rate 9.6 or 115.2 Kbps
* Interface data rate up to 230.4 Kbps
* Power Draw (typical) 730 mA TX / 80 mA RX
* Supply Voltage 2.8 to 5.5v
* Range (typical, depends on antenna & environment) Up to 64km line-of-sight
* Dimensions 36 x 60 x 5mm
* Weight 18 grams
* Interface 20-pin mini connector
* RF connector RPSMA (Reverse-polarity SMA) or MMCX (2 versions)
* price : ~179 USD
|
[[Image:Xtend_module.jpg|frame|left|9XTend OEM Modem]]
|}

=== Pinout ===

[[Image:Maxstream_9XTend_Pinout.gif|thumb|left|Maxstream 9XTend Pinout]]

{| border="1"
|-valign="top"
||'''''9XTend 20-pin Header'''''||'''''Name'''''||'''''Tiny Serial-1 Header'''''||'''''Notes'''''
|-
||1||GND||1 (GND)||Ground
|-
||2||VCC||2 (5V)||5V power (150mA - 730mA Supplied from servo bus or other 5V source)
|-
||5||RX||8 (TX)||3-5V TTL data input - connect to Tiny TX
|-
||6||TX||7 (RX)||5V TTL data output - connect to Tiny RX
|-
||7||Shutdown||2||This pin must be connected to the 5V bus for normal operation
|}
Notes: 
* 9XTend can run on voltages as low as 2.8V but users are strongly advised against connecting any modem (especially high power models) to the sensitive 3.3V bus supplying the autopilot processor and sensors.
 

=== Documentation ===

* [http://www.maxstream.net/products/xtend/oem-rf-module.php product page]
* [http://www.maxstream.net/products/xtend/datasheet_XTend_OEM_RF-Module.pdf datasheet]
* [http://www.maxstream.net/products/xtend/product-manual_XTend_OEM_RF-Module.pdf user manual]

== Aerocomm ==
Aerocomm's API mode is already implemented but some system integration is required. Full API more with addressed packets works well and was tested with AC4790-1x1 5mW low power modules. Maximim range achieved with a whip quater-wave antenna was 1Km.

How to use this modem on ground station side? [http://paparazzi.enac.fr/wiki/index.php/User:SilaS#SDK-AC4868-250_ground_modem_part]

See folder paparazzi3 / trunk / sw / aerocomm. It has all the required files to use this modem on the airborne and ground station side. The link.ml file is a direct replacement of the "main" link.ml file of the ground sttaion and will be merged into it in the future.. or you can do it as well.

{|
|
=== AC4868-250 ===
* Frequency Band 868MHz (For Europe). 868MHz is a limited band. Please read the [[868MHz Issues]]
* Output Power (w/ 2dBi antenna) 250 mW
* Sensitivity (@ full RF data rate) -103 dB
* RF Data Rate Up to 28.8 Kbps
* INterface Data Rate Up to 57.6 Kbps
* Power Draw (typical) 240 mA TX / 36 mA RX
* Supply Voltage 3.3v & 5V or 3.3v only
* Range (typical, depends on antenna & environment) Up to 15 kilometers line-of-sight
* Dimensions 49 x 42 x 5mm
* Weight < 21 grams
* Interface 20-pin mini connector
* Antenna MMCX jack Connector
* price : ~80$
|
[[Image:ConnexLink_USB_RF_Modem.jpg|thumb|Aerocomm USB Stand-alone Modem]]
|-
|

=== AC4790-200 ===
* Frequency 902-928MHz (North America, Australia, etc).
* Output Power 5-200mW
* Sensitivity (@ full RF data rate) -110dB
* RF Data Rate up to 76.8 Kbps
* INterface Data Rate Up to Up to 115.2 Kbps
* Power Draw (typical) 68 mA
* Supply Voltage 3.3v & 5.5V
* Range (typical, depends on antenna & environment) Up to 6.4 kilometers line-of-sight
* Dimensions 42 x 48 x 5mm
* Weight < 20 grams
* Interface 20-pin mini connector
* Antenna MMCX jack Connector or internal
* price : ~80$
|
[[Image:ac4868_transceiver.jpg|thumb|left|AC4868 OEM Modem]]
|
|-
|

=== AC4790-1000 ===
* Frequency 902-928MHz (North America, Australia, etc).
* Output Power 5-1000mW
* Sensitivity (@ full RF data rate) -99dB
* RF Data Rate up to 76.8 Kbps
* INterface Data Rate Up to Up to 115.2 Kbps
* Power Draw (typical) 650 mA
* Supply Voltage 3.3V only
* Range (typical, depends on antenna & environment) Up to 32 kilometers with high-gain antenna
* Dimensions 42 x 48 x 5mm
* Weight < 20 grams
* Interface 20-pin mini connector
* Antenna MMCX jack Connector
* price : ~80$
|}

=== Pinout ===

[[Image:Aerocomm_AC4868_pinout.jpg|thumb|left|Aerocomm AC4868 modem pinout]]
[[Image:Aerocomm_AC4490-200_wired.jpg|thumb|left|Aerocomm AC4490 wiring example]]
 

{| border="1"
|+ Wiring the Aerocomm AC4868 to the Tiny
|-valign="top"
||'''''AC4868 20-pin Header'''''||'''''Name'''''||'''''Color'''''||'''''Tiny v1.1 Serial-1'''''||'''''Tiny v2.11 Serial'''''||'''''Notes'''''
|-
||2||Tx||green||7||7||''(Note 1)''
|-
||3||Rx||blue||8||8||''(Note 1)''
|-
||5||GND||black||1||1|| -
|-
||10+11||VCC||red||2||3||+3.3v ''(Note 2)''
|-
||17||C/D||white||3||?||Low = Command High = Data
|}
''Note 1 : names are specified with respect to the AEROCOMM module''

''Note 2 : AC4790-1000 needs pins 10 and 11 jumped to work properly''

=== Documentation ===
* [http://www.aerocomm.com/rf_transceiver_modules/ac4790_mesh-ready_transceiver.htm AC4790 product page]
* [http://www.aerocomm.com/docs/Datasheet_AC4790_HI.pdf AC4790 Datasheet]
* [http://www.aerocomm.com/docs/User_Manual_AC4790.pdf AC4790 Manual]
* [http://www.aerocomm.com/rf_transceiver_modules/ac4868_868mhz_rf_transceiver.htm AC4848 product page]
* [http://www.aerocomm.com/docs/Datasheet_AC4868_HI.pdf AC4868 Datasheet]
* [http://www.aerocomm.com/docs/User_Manual_AC4868.pdf AC4868 user manual]

== Radiotronix ==
These Radiotronix modems are used in transparent mode. Use the WI232EUR Evaluation Software for configuring the modems for the set speed. Connect /CMD and CTS for programming. The DTS version for the US market might cause severe interference with GPS reception, it is not recommended. For a nice ground station modem just add a FTDI232 USB->serial cable, a 3.3V regulator with 100nF capacitors from supplies to ground, solder a SMA cable/connector and put it in a nice case. Make sure you only connect RTS to /CMD if you want to reprogram the modem with the Evaluation software (see the open jumper connection in the picture, green wire) and leave it floating otherwise as connected RTS/CTS sporadically leads to a reprogramming of the modem. The ANT-GXD105-FME/F from [http://www.roundsolutions.com Roundsolutions] was used as a ground station antenna at many competitions. Note that a 1/2 wave dipole antenna works best on-board as it doesn't require a ground-plane and has a reasonably omnidirectional radiation pattern.
{|
|
=== WI232EUR ===
* Frequency Band: 868 MHz (for Europe)
* Output Power: 32 mW
* RF Data Rate: Up to 76.8 kbps
* Interface Data Rate: up to 115.2 kbps
* Power Draw (typical): 65 mA TX / 20 mA RX
* Supply Voltage: 3.3v
* Range (typical, depends on antenna & environment): 500 meters line-of-sight
* Dimensions: 24 x 21 x 4mm
* Weight: ~2 grams
* Interface: solder connector
* Antenna: solder connector
* Price: ~25$
|
[[Image:Wi232eur_wiring.jpg|thumb|WI232EUR Modem (picture shows connection to Tiny 1.1)]]
|-
|

=== Pinout ===

 

{| border="1"
|+ Wiring the WI232EUR to the Tiny v1.1
|-valign="top"
||'''''WI232 pins'''''||'''''Name'''''||'''''Tiny Serial-1'''''||'''''Notes'''''
|-
||6||TxD||7||''(Note 1)''
|-
||5||RxD||8||''(Note 1)''
|-
||15-18||GND||1|| -
|-
||19||VCC||2||+3.3v
|-
||4||/CMD||-||''(Note 2)''
|-
||7||CTS||-||''(Note 3)''
|}
''Note 1 : names are specified with respect to the Radiotronix module''

''Note 2 : connect to RTS to program device with Evaluation software''

''Note 3 : connect to CTS to program device with Evaluation software''

|
[[Image:Wi232eur_bopla.jpg|thumb|WI232EUR Modem in BOPLA case]]
|-
|
|}
=== Documentation ===
* [http://www.radiotronix.com/datasheets/new/eur_um.pdf WI232EUR data sheet]
* [http://www.radiotronix.com/datasheets/new/rk-eur_um.pdf WI232EUR user's manual]
* [http://www.radiotronix.com/downloads/software/EUR/setup.exe Evaluation software]

== Bluetooth ==
These modems do not give you a great range but Bluetooth can be found in a lot of recent laptops built-in. Maybe not useful for fixed wing aircrafts it might be used for in-the-shop testing or quadcopters. Make sure you get a recent Class 1 EDR 2.0 stick if you buy one for your computer.
{|
|
=== "Sparkfun" Roving Networks (WRL-08497) ===
* Frequency Band 2.4GHz
* Output Power 32 mW
* RF Data Rate up to ~300 kbps in SPP
* Interface Data Rate up to 921 kbps
* Power Draw (typical) 50 mA TX / 40 mA RX
* Supply Voltage 3.3v
* Range (typical, depends on antenna & environment) 100 meters line-of-sight
* Dimensions 26 x 13 x 2mm
* Weight ~1.5 grams
* Interface solder connector
* price : ~45$
|
[[Image:roving_nw_wiring.jpg|thumb|Roving Networks modem wiring]]
|-
|

To connect to it, get the MAC address of the bluetooth modem

me@mybox:~$ hcitool scan
Scanning ...
00:06:66:00:53:AD FireFly-53AD

either make a virtual connection to a Bluetooth serial port each time you connect

sudo rfcomm bind 0 00:06:66:00:53:AD

or configure it once in /etc/bluetooth/rfcomm.conf

rfcomm0 {
bind yes;
device 00:06:66:00:53:AD;
}

now you can use Bluetooth as '''/dev/rfcomm0''' with the Paparazzi 'link'. You might need to restart 'link' in case you get out of range and it disconnects (tbd). Set the Tiny serial speed to 115200 as the modules come preconfigured to that.
|}

== Coronis WaveCard ==

These relatively inexpensive and light modules implement a Coronis proprietary protocol. Low power consumption - high latency - I would not recommend these modules mostly because of the low quality of the distribution and support. The documentation is rather poor and not easily available.

'''Suport for these modems has been removed from the airborne code on Dec 10th, 2007.'''
{|
|-valign="top"
|
* Frequency Band 400MHz, 868Mhz and 915MHz (3 versions)
* Output Power 25mW and 500mW (2 versions)
* Sensitivity -110 dBm (@ 9600 bps)
* Data Rate 100 Kbps
* Power Draw (typical) 45mA (25mW), 450mA (500mW) TX / 15 mA RX
* Supply Voltage ...
* Range (typical, depends on antenna & environment) Up to 1km (25mW) , 5km (500mW) line-of-sight
* Dimensions 30 x 28 x 7mm (25mW), 37 x 30 x 7mm (500mW)
* 50 ohm RF port for antenna connection
|
[[Image:wavecard.jpg|Coronis Wavecard]]
|}

=== Documentation ===

* [http://www.coronis-systems.com/produit.php?lang=EN&id=WCA www.coronis-systems.com]
* [[Media:CS-COM-SPRD-WAVECARD-E03B.pdf|Wavecard datasheet]]

== Telemetry via Video Transmitter==

[[Image:video_tx_small.jpg|thumb|2.4GHz Video Transmitter]]
In order for the UAV to transmit video from an onboard camera, an analog video transmitter can be used. These vary in power, and thus range, and run normally on 2.4Ghz. Small UAVs can get about 600m of range from the 50mW version, and extended range can be achieved using units up to 1W. Weight for these units varies from a couple grams to about 30 for the 1W with shielding. Please check for your countries regulations on 2.4Ghz transmission, as each is different.

It is possible to use the audio channel to send simple telemetry data to the groundstation. Uploading telemetry not possible via analog audio transmitter only.
 

== Antennas ==

Here are some examples of lightweight and efficient 868MHz antennas developped by the RF laboratory at ENAC.
[[Image:868mhz_twinstar_antenna_1.jpg|thumb|left|868MHz copper foil antenna attached to the aircraft tail]]
[[Image:868mhz_twinstar_antenna_2.jpg|thumb|left|868MHz copper foil antenna bottom view]]
[[Image:868mhz_ground_antenna.jpg|thumb|left|868MHz ground antenna]]
 

This wiki page might give some ideas about antennas: http://en.wikipedia.org/wiki/Dipole_antenna

[[Category:Hardware]]

Tiny v1.1

2011-11-01T23:38:52Z

Bendespain: /* Features */

The Tiny autopilot was designed with an end user application in mind.

== Features ==

* Single LPC2148 MCU
* 8 Analog input channels 0V - 3.3V
* 1 3.3V TTL UART (5V tolerant)
* 7 PWM outputs
* 1 R/C receiver PPM frame input
* 1 [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] bus
* 1 [http://en.wikipedia.org/wiki/I2c I2C] bus
* 1 USB (client)
* Integrated GPS receiver and patch antenna (4Hz update)
* 5V/2A switching power supply & 3.3V linear regulator (input voltage max: 20v)
* 2 LEDs (status display)
* 1 button (initiate launch)
* 25 grams
* 63 x 35mm (smaller then a business card)

The Tiny autopilot uses a single Philips LPC2148 ARM7 based microcontroller.
The [http://www.arm.com/products/CPUs/families/ARM7Family.html ARM7] is a low-power 32-bit RISC processor core and the [http://www.standardics.philips.com/products/lpc2000/ Philips LPC2148] has 512KB on-chip Flash ROM, 40KB RAM and can be clocked at 60MHz.

Although critical control code such as the R/C interface and servo output are well segregated in Paparazzi software and well protected from interference from flaws in the stability/navigation/comm/payload code, great care must be taken when experimenting with new software as some errors can cause a the processor to halt or stall for extended periods causing total loss of control. The dual processor [[Classix]] addresses this risk by runnning critical code on a separate independent processor.

The schematics are available from the [http://cvs.savannah.nongnu.org/viewcvs/paparazzi3/hw/controller/?root=paparazzi CVS repository]. Be aware that the Tiny 13 V1.1 is a four layer PCB with a dedicated ground and power supply layer.
 
<gallery>
Image:Tin13_bottom.jpg|Top
Image:Tin13_top.jpg|Bottom
</gallery>

== Architecture ==

[[Image:Tiny_v099_Architecture.gif]]

== Pinout ==
'''(Tiny13 v1.1)'''

[[Image:Tiny13_v1_1_pinout.gif]]
 

''Pins Name and Type are specified with respect to the Autopilot Board''

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''SERIAL 1'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3v||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||SDA0||I/O O.D.||I2C0 data||
|-
|4||SCL0||I/O O.D.||I2C0 clock||
|-
|5||P0.14||IN||In-Circuit Serial Programming (ISP) enable - LOW on this pin during boot up to enable ''(Note 1)''||
|-
|6||RESET||IN||External Reset - A LOW on this pin performs a MCU hardware reset||
|-
|7||RXD_0||IN||UART0 Serial Input (used by ISP Serial Bootloader) (5V Tolerant)||style="background:green; color:white"|Green
|-
|8||TXD_0||OUT||UART0 Serial Output (used by ISP Serial Bootloader) (5V Tolerant)||style="background:blue; color:white"|Blue
|}

''Note 1 : Holding this pin low for at least 3mS after a RESET (or power up) instructs the controller to enter programming mode.''

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''SERIAL 2'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3V||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||SCK||I/O||SPI0 Serial clock. Clock output from master or input to slave||
|-
|4||MISO||I/O||SPI0 Master In Slave Out. Data input to master or data output from slave||
|-
|5||MOSI||I/O||SPI0 Master Out Slave In. Data output from master or data input to slave||
|-
|6||SSEL||IN||SSP Slave Select. Selects the SSP interface as a slave (SSEL1)||
|-
|7||INT||IN||External interrupt 2 input (EINT2)||
|-
|8||USB+||I/O||USB bidirectional D+ line||style="background:green; color:white"|Green
|-
|9||USB-||I/O||USB bidirectional D- line||style="background:white; color:black"|White
|-
|10||P0.23||IN||Indicates the presence of USB bus power (VBUS) (5V Tolerant)||style="background:orange; color:white"|Orange
|}

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''RC'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +5v||PWR||5v Rail from Tiny to R/C receiver supply||style="background:red; color:white"|Red
|-
|3||PPM_IN||IN||PPM Stream from RC Receiver (5V TOLERANT)||style="background:white; color:black"|White
|-
|4||NC||-||''no connection''||
|-
|5||NC||-||''no connection''||
|}

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''ANALOG'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3V||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||ADC_0||IN||Analog to Digital Converter Input #0||
|-
|4||ADC_1||IN||Analog to Digital Converter Input #1||
|-
|5||ADC_2||IN||Analog to Digital Converter Input #2||
|-
|6||ADC_3||IN||Analog to Digital Converter Input #3||
|-
|7||ADC_4||IN||Analog to Digital Converter Input #4||
|-
|8||ADC_5||IN||Analog to Digital Converter Input #5||
|-
|9||ADC_6||IN||Analog to Digital Converter Input #6||
|-
|10||ADC_7||IN||Analog to Digital Converter Input #7||
|}

== Schematic ==

<gallery>
Image:Tiny_v1-1_schematic_1.png|Tiny v1.1 Schematic (1/2)
Image:Tiny_v1-1_schematic_2.png|Tiny v1.1 Schematic (2/2)
</gallery>

== Bill of Materials (BOM) ==

Please note that there are differences between 0.9, 0.99, and 1.1. Choose the version that matches your hardware.

'''Warning''': C20 needs to be a low ESR capacitor and the one listed on the BOM isn't. A proper replacement would be B45197A2226K209. This could potentially cause instability of the 3V3 supply which, of course, is critical.

=== Tiny 1.1 BOM ===

[http://www.recherche.enac.fr/paparazzi/wiki_images/b/b1/1.1_bom.zip 1.1_bom.zip]

Addendum: There are digikey part numbers for two more of the components.
Murata inductor is 490-1116-1-ND
Tactile Switch is either SW1020CT-ND (grounded) or SW1021CT-ND.

=== Tiny 0.99 BOM ===

{|
|-valign="top"
|Qty ||Value||Device||Parts||Manufacturer||PN||distr PN
|-valign="top"
||7 || - ||53047-03 ||CAMERA, RC_RX, S0, S1, S3, S4, S5 ||Molex ||53047-0310 ||DK WM1732-ND
|-valign="top"
||1 || - ||53047-04 ||VIDEO_TX ||Molex ||53047-0410 ||DK WM1733-ND
|-valign="top"
||1 || - ||53047-08 ||SERIAL_1 ||Molex ||53047-0810 ||DK WM1737-ND
|-valign="top"
||2 || - ||53047-10 ||ANALOG, SERIAL_2 ||Molex ||53047-1010 ||DK WM1739-ND
|-valign="top"
||1 ||FUTABA_BEND ||FUTABA_BEND ||CON_ESC || - || - || -
|-valign="top"
||2 ||LEDCHIP ||LED0805 ||LED1, LED2 ||Kingbright ||APT2012EC ||MO 604-APT2012EC
|-valign="top"
||1 ||B3S ||B3S ||SW1 || OMRON ELECTRONICS || B3S-1002 || RS 183-717
|-valign="top"
||1 ||0.47uH ||L-EUL2012C ||L2 || WURTH ELEKTRONIK || 74479032 || RS 308-8564
|-valign="top"
||1 ||15uH ||WE_PD ||L1 ||Pulse ||P1168.153T ||MO 673-P1168.153T
|-valign="top"
||2 ||33R ||R-EU_R1005 ||R9, R10 ||Yageo ||RC0402JR-0733L ||DK 311-33JRCT-ND
|-valign="top"
||1 ||150R ||R-EU_R1005 ||R12 ||Yageo ||RC0402JR-07150L ||DK 311-150JRCT-ND
|-valign="top"
||3 ||1K ||R-EU_R1005 ||R2, R3, R8 ||Yageo ||RC0402JR-071KL ||DK 311-1.0KJRCT-ND
|-valign="top"
||1 ||1.5K ||R-EU_R1005 ||R11 ||Yageo ||RC0402JR-071K5L ||DK 311-1.5KJRCT-ND
|-valign="top"
||2 ||3.3K ||R-EU_R1005 ||R6, R15 ||Yageo ||RC0402JR-073K3L ||DK 311-3.3KJRCT-ND
|-valign="top"
||1 ||4.7K ||R-EU_R1005 ||R1 ||Yageo ||RC0402JR-074K7L ||DK 311-4.7KJRCT-ND
|-valign="top"
||7 ||10K ||R-EU_R1005 ||R4, R5, R13, R14, R16, R17, R18 ||Yageo ||RC0402JR-0710KL ||DK 311-10KJRCT-ND
|-valign="top"
||2 ||12K ||R-EU_R1005 ||R103, R105 ||Yageo ||RC0402JR-0712KL ||DK 311-12KJRCT-ND
|-valign="top"
||1 ||15K ||R-EU_R1005 ||R7 ||Yageo ||RC0402JR-0715KL ||DK 311-15KJRCT-ND
|-valign="top"
||2 ||56K ||R-EU_R1005 ||R102, R104 ||Yageo ||RC0402JR-0756KL ||DK 311-56KJRCT-ND
|-valign="top"
||1 ||100K ||R-EU_R1005 ||R101 ||Yageo ||RC0402JR-07100KL ||DK 311-100KJRCT-ND
|-valign="top"
||3 ||18pF ||C-EUC0402K ||C3, C7, C10 ||TDK ||C1005C0G1H180J ||DK 445-1238-1-ND
|-valign="top"
||2 ||22pF ||C-EUC0402K ||C8_1, C9_1 ||Yageo ||CC0402JRNPO9BN220 ||DK 311-1018-1-ND
|-valign="top"
||1 ||100pF ||C-EUC0402K ||C103 ||Kemet ||C0402C101J3GACTU ||DK 399-1022-1-ND
|-valign="top"
||1 ||220pF ||C-EUC0402K ||C102 ||Kemet ||C0402C221K5RACTU ||DK 399-1030-1-ND
|-valign="top"
||1 ||220pF/50V ||C-EUC1206K ||C4 ||Yageo ||CC1206KRX7R9BB221 ||DK 311-1164-1-ND
|-valign="top"
||1 ||1nF ||C-EUC0402K ||C104 ||Kemet ||C0402C102K3RACTU ||DK 399-1031-1-ND
|-valign="top"
||1 ||3.3nF ||C-EUC0402K ||C101 ||Kemet ||C0402C332K5RACTU ||DK 399-3070-1-ND
|-valign="top"
||1 ||22nF/50V ||C-EUC1206K ||C6 ||Yageo ||CC1206KRX7R9BB222 ||DK 311-1176-1-ND
|-valign="top"
||8 ||100nF ||C-EUC0402K ||C1_1, C2, C3_1, C4_1, C5_1, C6_1, C7_1, C106 ||Kemet ||C0402C104K8PACTU ||DK 99-3027-1-ND
|-valign="top"
||3 ||100nF ||C-EUC0603 ||C8, C9, C21 ||Kemet ||C0603C104J4RACTU ||DK 399-1097-1-ND
|-valign="top"
||1 ||10uF ||CPOL-EUA/3216-18R ||C18, C105 ||Kemet ||T491A106M010AS ||DK 399-1564-1-ND MO-80-T491A106K010
|-valign="top"
||1 ||22uF ||CPOL-EUB/3528-21R ||C20 ||Kemet ||B45196H1226M209 ||DK 495-2185-1-ND
|-valign="top"
||1 ||47uF/16V ||CPOL-EUD/7343-31R ||C5 ||Kemet ||B45197A3476K409 ||DK 495-1544-1-ND
|-valign="top"
||1 ||330uF/10V ||CPOL-EUD/7343-31R ||C1 ||Kemet ||B45197A2337K509 ||DK 495-1536-1-ND
|-valign="top"
||1 ||0.2F ||J1ROUND ||C77 ||Panasonic - ECG ||EEC-EN0F204J1 ||DK P11070CT-ND
|-valign="top"
||1 ||AD8552RU ||AD8552RU ||IC2 ||Analog Devices Inc ||AD8552ARU ||DK AD8552ARU-ND
|-valign="top"
||1 ||BAS70 ||BAS70 ||D1 ||Micro Commercial Co. ||BAS40-TP ||DK BAS40TPMSCT-ND
|-valign="top"
||1 ||STPS2L ||STPS2L ||D2 ||STMicroelectronics ||STPS2L30A ||DK 497-3759-1-ND
|-valign="top"
||1 ||CD4015B ||CD4015B ||IC1 ||Texas Instruments ||CD4015BPWR ||DK 296-14090-1-ND
|-valign="top"
||1 ||12MHz ||CRYSTAL_CTS ||Q1 ||CTS-Frequency Controls ||405C35B12M00000 ||DK CTX639CT-ND
|-valign="top"
||1 ||DDTA143 ||MUN2111T1 ||T1 ||Diodes Inc ||DDTA143ZCA-7 ||DK DDTA143ZCADICT-ND
|-valign="top"
||1 ||L5973D ||L5973D ||REG1 ||STMicroelectronics ||L5973D013TR ||DK 497-3638-1-ND
|-valign="top"
||1 ||REG1117 ||REG1117 ||REG2 ||National Semiconductor ||LM1117MP-3.3 ||DK LM1117MP-3.3CT-ND
|-valign="top"
||1 ||LEA-4P ||LEA-4P ||GPS ||Microblox ||LEA-4P-0-000-0 || -
|-valign="top"
||1 ||GPS_ANT_13 ||GPS_ANT_13 ||ANTENNA ||Sangshin || KSA-ST1580MS13 || -
|-valign="top"
||1 ||LPC2148 ||LPC2148 ||MCU ||Philips ||LPC2148FBD64-S ||DK 568-1765-ND
|-
|}

DK = digikey

MO = mouser

RS = radiospares


== Home Assembly ==

Visit here for the wiki page on [[Tiny_Assembly|Self Assembly Tips and Techniques]]. This page also includes Hardware Troubleshooting.

== Programming ==
[[Image:Tiny_test_wiring.jpg|thumb|Example wiring for programming and telemetry]]
The Philips LPC21xx series ARM7 microcontrollers include hardware ISP (InCircuit Serial Programming) and can be programmed through the serial interface UART0 (Serial1) by holding pin P0.14 low during power-up. Paparazzi software includes a USB bootloader program that allows for easy 1-second programming through a standard USB port with no adapters needed. This allows us to upload new settings, flight plans, or software updates quickly and conveniently without the need to disconnect the modem from UART0. See the [[Compiling|Compiling and Flashing]] page for instructions on installing the bootloader and autopilot software.

[[Category:Hardware]]

Tiny v1.1

2011-11-01T23:37:42Z

Bendespain: /* Features */

The Tiny autopilot was designed with an end user application in mind.

== Features ==

* Single LPC2148 MCU
* 8 Analog input channels 0V - 3.3V
* 1 3.3V TTL UART (5V tolerant)
* 7 PWM outputs
* 1 R/C receiver PPM frame input
* 1 [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] bus
* 1 [http://en.wikipedia.org/wiki/I2c I2C] bus
* 1 USB (client)
* Integrated GPS receiver and patch antenna (4Hz update)
* 5V/2A switching power supply & 3.3V linear regulator (input voltage max: 20V)
* 2 LEDs (status display)
* 1 button (initiate launch)
* 25 grams
* 63 x 35mm (smaller then a business card)

The Tiny autopilot uses a single Philips LPC2148 ARM7 based microcontroller.
The [http://www.arm.com/products/CPUs/families/ARM7Family.html ARM7] is a low-power 32-bit RISC processor core and the [http://www.standardics.philips.com/products/lpc2000/ Philips LPC2148] has 512KB on-chip Flash ROM, 40KB RAM and can be clocked at 60MHz.

Although critical control code such as the R/C interface and servo output are well segregated in Paparazzi software and well protected from interference from flaws in the stability/navigation/comm/payload code, great care must be taken when experimenting with new software as some errors can cause a the processor to halt or stall for extended periods causing total loss of control. The dual processor [[Classix]] addresses this risk by runnning critical code on a separate independent processor.

The schematics are available from the [http://cvs.savannah.nongnu.org/viewcvs/paparazzi3/hw/controller/?root=paparazzi CVS repository]. Be aware that the Tiny 13 V1.1 is a four layer PCB with a dedicated ground and power supply layer.
 
<gallery>
Image:Tin13_bottom.jpg|Top
Image:Tin13_top.jpg|Bottom
</gallery>

== Architecture ==

[[Image:Tiny_v099_Architecture.gif]]

== Pinout ==
'''(Tiny13 v1.1)'''

[[Image:Tiny13_v1_1_pinout.gif]]
 

''Pins Name and Type are specified with respect to the Autopilot Board''

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''SERIAL 1'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3v||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||SDA0||I/O O.D.||I2C0 data||
|-
|4||SCL0||I/O O.D.||I2C0 clock||
|-
|5||P0.14||IN||In-Circuit Serial Programming (ISP) enable - LOW on this pin during boot up to enable ''(Note 1)''||
|-
|6||RESET||IN||External Reset - A LOW on this pin performs a MCU hardware reset||
|-
|7||RXD_0||IN||UART0 Serial Input (used by ISP Serial Bootloader) (5V Tolerant)||style="background:green; color:white"|Green
|-
|8||TXD_0||OUT||UART0 Serial Output (used by ISP Serial Bootloader) (5V Tolerant)||style="background:blue; color:white"|Blue
|}

''Note 1 : Holding this pin low for at least 3mS after a RESET (or power up) instructs the controller to enter programming mode.''

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''SERIAL 2'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3V||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||SCK||I/O||SPI0 Serial clock. Clock output from master or input to slave||
|-
|4||MISO||I/O||SPI0 Master In Slave Out. Data input to master or data output from slave||
|-
|5||MOSI||I/O||SPI0 Master Out Slave In. Data output from master or data input to slave||
|-
|6||SSEL||IN||SSP Slave Select. Selects the SSP interface as a slave (SSEL1)||
|-
|7||INT||IN||External interrupt 2 input (EINT2)||
|-
|8||USB+||I/O||USB bidirectional D+ line||style="background:green; color:white"|Green
|-
|9||USB-||I/O||USB bidirectional D- line||style="background:white; color:black"|White
|-
|10||P0.23||IN||Indicates the presence of USB bus power (VBUS) (5V Tolerant)||style="background:orange; color:white"|Orange
|}

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''RC'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +5v||PWR||5v Rail from Tiny to R/C receiver supply||style="background:red; color:white"|Red
|-
|3||PPM_IN||IN||PPM Stream from RC Receiver (5V TOLERANT)||style="background:white; color:black"|White
|-
|4||NC||-||''no connection''||
|-
|5||NC||-||''no connection''||
|}

{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"
|+'''ANALOG'''
!''Pin #''!!''Name''!!''Type''!!''Desription''!!width="50"|''Suggested Color''
|-
|1||GND||PWR||common ground||style="background:black; color:white"|Black
|-
|2|| +3.3V||PWR||3.3v Rail from Tiny||style="background:red; color:white"|Red
|-
|3||ADC_0||IN||Analog to Digital Converter Input #0||
|-
|4||ADC_1||IN||Analog to Digital Converter Input #1||
|-
|5||ADC_2||IN||Analog to Digital Converter Input #2||
|-
|6||ADC_3||IN||Analog to Digital Converter Input #3||
|-
|7||ADC_4||IN||Analog to Digital Converter Input #4||
|-
|8||ADC_5||IN||Analog to Digital Converter Input #5||
|-
|9||ADC_6||IN||Analog to Digital Converter Input #6||
|-
|10||ADC_7||IN||Analog to Digital Converter Input #7||
|}

== Schematic ==

<gallery>
Image:Tiny_v1-1_schematic_1.png|Tiny v1.1 Schematic (1/2)
Image:Tiny_v1-1_schematic_2.png|Tiny v1.1 Schematic (2/2)
</gallery>

== Bill of Materials (BOM) ==

Please note that there are differences between 0.9, 0.99, and 1.1. Choose the version that matches your hardware.

'''Warning''': C20 needs to be a low ESR capacitor and the one listed on the BOM isn't. A proper replacement would be B45197A2226K209. This could potentially cause instability of the 3V3 supply which, of course, is critical.

=== Tiny 1.1 BOM ===

[http://www.recherche.enac.fr/paparazzi/wiki_images/b/b1/1.1_bom.zip 1.1_bom.zip]

Addendum: There are digikey part numbers for two more of the components.
Murata inductor is 490-1116-1-ND
Tactile Switch is either SW1020CT-ND (grounded) or SW1021CT-ND.

=== Tiny 0.99 BOM ===

{|
|-valign="top"
|Qty ||Value||Device||Parts||Manufacturer||PN||distr PN
|-valign="top"
||7 || - ||53047-03 ||CAMERA, RC_RX, S0, S1, S3, S4, S5 ||Molex ||53047-0310 ||DK WM1732-ND
|-valign="top"
||1 || - ||53047-04 ||VIDEO_TX ||Molex ||53047-0410 ||DK WM1733-ND
|-valign="top"
||1 || - ||53047-08 ||SERIAL_1 ||Molex ||53047-0810 ||DK WM1737-ND
|-valign="top"
||2 || - ||53047-10 ||ANALOG, SERIAL_2 ||Molex ||53047-1010 ||DK WM1739-ND
|-valign="top"
||1 ||FUTABA_BEND ||FUTABA_BEND ||CON_ESC || - || - || -
|-valign="top"
||2 ||LEDCHIP ||LED0805 ||LED1, LED2 ||Kingbright ||APT2012EC ||MO 604-APT2012EC
|-valign="top"
||1 ||B3S ||B3S ||SW1 || OMRON ELECTRONICS || B3S-1002 || RS 183-717
|-valign="top"
||1 ||0.47uH ||L-EUL2012C ||L2 || WURTH ELEKTRONIK || 74479032 || RS 308-8564
|-valign="top"
||1 ||15uH ||WE_PD ||L1 ||Pulse ||P1168.153T ||MO 673-P1168.153T
|-valign="top"
||2 ||33R ||R-EU_R1005 ||R9, R10 ||Yageo ||RC0402JR-0733L ||DK 311-33JRCT-ND
|-valign="top"
||1 ||150R ||R-EU_R1005 ||R12 ||Yageo ||RC0402JR-07150L ||DK 311-150JRCT-ND
|-valign="top"
||3 ||1K ||R-EU_R1005 ||R2, R3, R8 ||Yageo ||RC0402JR-071KL ||DK 311-1.0KJRCT-ND
|-valign="top"
||1 ||1.5K ||R-EU_R1005 ||R11 ||Yageo ||RC0402JR-071K5L ||DK 311-1.5KJRCT-ND
|-valign="top"
||2 ||3.3K ||R-EU_R1005 ||R6, R15 ||Yageo ||RC0402JR-073K3L ||DK 311-3.3KJRCT-ND
|-valign="top"
||1 ||4.7K ||R-EU_R1005 ||R1 ||Yageo ||RC0402JR-074K7L ||DK 311-4.7KJRCT-ND
|-valign="top"
||7 ||10K ||R-EU_R1005 ||R4, R5, R13, R14, R16, R17, R18 ||Yageo ||RC0402JR-0710KL ||DK 311-10KJRCT-ND
|-valign="top"
||2 ||12K ||R-EU_R1005 ||R103, R105 ||Yageo ||RC0402JR-0712KL ||DK 311-12KJRCT-ND
|-valign="top"
||1 ||15K ||R-EU_R1005 ||R7 ||Yageo ||RC0402JR-0715KL ||DK 311-15KJRCT-ND
|-valign="top"
||2 ||56K ||R-EU_R1005 ||R102, R104 ||Yageo ||RC0402JR-0756KL ||DK 311-56KJRCT-ND
|-valign="top"
||1 ||100K ||R-EU_R1005 ||R101 ||Yageo ||RC0402JR-07100KL ||DK 311-100KJRCT-ND
|-valign="top"
||3 ||18pF ||C-EUC0402K ||C3, C7, C10 ||TDK ||C1005C0G1H180J ||DK 445-1238-1-ND
|-valign="top"
||2 ||22pF ||C-EUC0402K ||C8_1, C9_1 ||Yageo ||CC0402JRNPO9BN220 ||DK 311-1018-1-ND
|-valign="top"
||1 ||100pF ||C-EUC0402K ||C103 ||Kemet ||C0402C101J3GACTU ||DK 399-1022-1-ND
|-valign="top"
||1 ||220pF ||C-EUC0402K ||C102 ||Kemet ||C0402C221K5RACTU ||DK 399-1030-1-ND
|-valign="top"
||1 ||220pF/50V ||C-EUC1206K ||C4 ||Yageo ||CC1206KRX7R9BB221 ||DK 311-1164-1-ND
|-valign="top"
||1 ||1nF ||C-EUC0402K ||C104 ||Kemet ||C0402C102K3RACTU ||DK 399-1031-1-ND
|-valign="top"
||1 ||3.3nF ||C-EUC0402K ||C101 ||Kemet ||C0402C332K5RACTU ||DK 399-3070-1-ND
|-valign="top"
||1 ||22nF/50V ||C-EUC1206K ||C6 ||Yageo ||CC1206KRX7R9BB222 ||DK 311-1176-1-ND
|-valign="top"
||8 ||100nF ||C-EUC0402K ||C1_1, C2, C3_1, C4_1, C5_1, C6_1, C7_1, C106 ||Kemet ||C0402C104K8PACTU ||DK 99-3027-1-ND
|-valign="top"
||3 ||100nF ||C-EUC0603 ||C8, C9, C21 ||Kemet ||C0603C104J4RACTU ||DK 399-1097-1-ND
|-valign="top"
||1 ||10uF ||CPOL-EUA/3216-18R ||C18, C105 ||Kemet ||T491A106M010AS ||DK 399-1564-1-ND MO-80-T491A106K010
|-valign="top"
||1 ||22uF ||CPOL-EUB/3528-21R ||C20 ||Kemet ||B45196H1226M209 ||DK 495-2185-1-ND
|-valign="top"
||1 ||47uF/16V ||CPOL-EUD/7343-31R ||C5 ||Kemet ||B45197A3476K409 ||DK 495-1544-1-ND
|-valign="top"
||1 ||330uF/10V ||CPOL-EUD/7343-31R ||C1 ||Kemet ||B45197A2337K509 ||DK 495-1536-1-ND
|-valign="top"
||1 ||0.2F ||J1ROUND ||C77 ||Panasonic - ECG ||EEC-EN0F204J1 ||DK P11070CT-ND
|-valign="top"
||1 ||AD8552RU ||AD8552RU ||IC2 ||Analog Devices Inc ||AD8552ARU ||DK AD8552ARU-ND
|-valign="top"
||1 ||BAS70 ||BAS70 ||D1 ||Micro Commercial Co. ||BAS40-TP ||DK BAS40TPMSCT-ND
|-valign="top"
||1 ||STPS2L ||STPS2L ||D2 ||STMicroelectronics ||STPS2L30A ||DK 497-3759-1-ND
|-valign="top"
||1 ||CD4015B ||CD4015B ||IC1 ||Texas Instruments ||CD4015BPWR ||DK 296-14090-1-ND
|-valign="top"
||1 ||12MHz ||CRYSTAL_CTS ||Q1 ||CTS-Frequency Controls ||405C35B12M00000 ||DK CTX639CT-ND
|-valign="top"
||1 ||DDTA143 ||MUN2111T1 ||T1 ||Diodes Inc ||DDTA143ZCA-7 ||DK DDTA143ZCADICT-ND
|-valign="top"
||1 ||L5973D ||L5973D ||REG1 ||STMicroelectronics ||L5973D013TR ||DK 497-3638-1-ND
|-valign="top"
||1 ||REG1117 ||REG1117 ||REG2 ||National Semiconductor ||LM1117MP-3.3 ||DK LM1117MP-3.3CT-ND
|-valign="top"
||1 ||LEA-4P ||LEA-4P ||GPS ||Microblox ||LEA-4P-0-000-0 || -
|-valign="top"
||1 ||GPS_ANT_13 ||GPS_ANT_13 ||ANTENNA ||Sangshin || KSA-ST1580MS13 || -
|-valign="top"
||1 ||LPC2148 ||LPC2148 ||MCU ||Philips ||LPC2148FBD64-S ||DK 568-1765-ND
|-
|}

DK = digikey

MO = mouser

RS = radiospares


== Home Assembly ==

Visit here for the wiki page on [[Tiny_Assembly|Self Assembly Tips and Techniques]]. This page also includes Hardware Troubleshooting.

== Programming ==
[[Image:Tiny_test_wiring.jpg|thumb|Example wiring for programming and telemetry]]
The Philips LPC21xx series ARM7 microcontrollers include hardware ISP (InCircuit Serial Programming) and can be programmed through the serial interface UART0 (Serial1) by holding pin P0.14 low during power-up. Paparazzi software includes a USB bootloader program that allows for easy 1-second programming through a standard USB port with no adapters needed. This allows us to upload new settings, flight plans, or software updates quickly and conveniently without the need to disconnect the modem from UART0. See the [[Compiling|Compiling and Flashing]] page for instructions on installing the bootloader and autopilot software.

[[Category:Hardware]]