<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://wiki.paparazziuav.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rufus</id>
	<title>PaparazziUAV - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://wiki.paparazziuav.org/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Rufus"/>
	<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/wiki/Special:Contributions/Rufus"/>
	<updated>2026-05-19T02:33:08Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=16465</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=16465"/>
		<updated>2014-01-07T22:30:12Z</updated>

		<summary type="html">&lt;p&gt;Rufus: removed Aerofu (sob)&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [https://github.com/paparazzi/paparazzi-hardware freely available on GitHub] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Autopilots=&lt;br /&gt;
&lt;br /&gt;
== [[File:1bitsquared_logo.png|100px|link=http://1bitsquared.com]] 1 BIT SQUARED ==&lt;br /&gt;
&lt;br /&gt;
Paparazzi UAV, development, production and consulting company. Manufacturers and distributors of [[Lisa/S]] nano autopilot.&lt;br /&gt;
&lt;br /&gt;
== [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] www.ppzuav.com [[Image:ApogeeV1_img01sm.JPG|thumb|400px|Paparazzi controllers]] ==&lt;br /&gt;
Providing professionally assembled and tested hardware and PCBs for your Paparazzi Projects since 2007&amp;lt;br/&amp;gt;&lt;br /&gt;
''' Yes we have [[SUMO]] bundles and [[SUMO/prepare_electronics|SUMO electronics]].'''&amp;lt;br/&amp;gt;&lt;br /&gt;
'''Yes we have [[https://www.ppzuav.com/osc/product_info.php?products_id=154 Apogee V1]] [[Apogee/v1.00|Apogee Fixed wing controller]].'''&amp;lt;br/&amp;gt;&lt;br /&gt;
eMail to: sales@ppzuav.com for details.&lt;br /&gt;
&lt;br /&gt;
We want to help you get your Paparazzi project off the ground. We have helped hundreds of projects become successful. Confused what to buy? Just give us an email and we will help you decide (sales@ppzuav.com).&lt;br /&gt;
&lt;br /&gt;
Whatever the part we make all the Paparazzi hardware available either via bare PCBs or fully assembled ready to program. TWOG, Umarim, Apogee controllers available now. NOTE: Special orders welcome. Just let us know which item and the quantity.&lt;br /&gt;
&lt;br /&gt;
If you do not see what you need just ask. Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible.&lt;br /&gt;
&lt;br /&gt;
Visit the PPZUAZ [https://www.ppzuav.com/osc WebStore] to see the latest offerings.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== [http://transition-robotics.com [[Image:Transition_Robotics_Logo.png|100px]] Transition Robotics Inc.] [[Image:LisaM_V2_0_TopView.JPG|thumb|Lisa/M V2.0 top view]][[Image:LisaM_V2_0_BottomView.JPG|thumb|Lisa/M V2.0 bottom view]] ==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Transition Robotics Inc. is a young company developing new solutions for and with the Paparazzi UAV platform. Their core product is the [[Image:Quadshot_Logo.jpg|100px|link=http://thequadshot.com|Quadshot]], a VTOL transitioning aircraft.&lt;br /&gt;
&lt;br /&gt;
Beside the Quadshot itself they develop and provide hardware and software that is especially optimized for Paparazzi, such as the Lisa Autopilots, Aspirin IMUs and associated accessories.&lt;br /&gt;
&lt;br /&gt;
They have a shop on their [http://transition-robotics.com Quadshot product page].&lt;br /&gt;
&lt;br /&gt;
As of February 2012, Transition Robotics, Inc. has acquired all IP and Paparazzi related inventory from Joby Robotics. We are thankful to Joby Robotics for their important and faithful support of Paparazzi related hardware projects, and hope to carry on this tradition. Hardware formerly supplied by Joby Robotics may now be purchased at the [http://transition-robotics.com/collections/all Transition Robotics/Quadshot webstore.]&lt;br /&gt;
&lt;br /&gt;
The [http://transition-robotics.com/collections/all TRI/Quadshot Webstore] also stocks pre-crimped Molex Picoblade wires and connector housings.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Other =&lt;br /&gt;
&lt;br /&gt;
==[http://www.sparkfun.com Sparkfun]==&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Development boards&lt;br /&gt;
* GPS&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters (XBEE adapter)&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Sparkfun distributors in Europe'''&lt;br /&gt;
&lt;br /&gt;
Incomplete list.&lt;br /&gt;
*http://www.lipoly.de/index.php?main_page=index&amp;amp;cPath=880_883&amp;amp;language=en&lt;br /&gt;
*http://www.watterott.com/en/SparkFun&lt;br /&gt;
&lt;br /&gt;
==Mouser==&lt;br /&gt;
&lt;br /&gt;
Elektronic distributor, sells all kinds of elektronic parts or modules.&lt;br /&gt;
Free shipping as of 60€.&lt;br /&gt;
&lt;br /&gt;
== [https://store.diydrones.com/ DIYDrones] ==&lt;br /&gt;
Mainly focused on ArduPilot hardware. But carries Paparazzi compatible Telemetry and sensor boards.&lt;br /&gt;
&lt;br /&gt;
'''DIYDrones distributors in Europe'''&lt;br /&gt;
*http://www.lipoly.de/index.php?main_page=index&amp;amp;cPath=880_1912 [DE]&lt;br /&gt;
*http://www.unmannedtechshop.co.uk/ [UK]&lt;br /&gt;
*http://www.buildyourowndrone.co.uk/ [UK]&lt;br /&gt;
&lt;br /&gt;
==u-Blox GPS receivers==&lt;br /&gt;
&lt;br /&gt;
* [http://www.navilock.de/produkte/gruppen/13/Boards_und_Module navilock.de] (also available on [http://www.amazon.de Amazon.de])&lt;br /&gt;
* [http://www.rfdesign.co.za/pages/5645456/Products/GPS-Products/Antaris-4-Modules.asp rfdesign.co.za] (Also [http://www.rfdesign.co.za/pages/5645456/Products/GPS-Products/u-blox-5-Modules.asp u-blox 5] and [http://www.rfdesign.co.za/pages/5645456/Products/GPS-Products/u-blox-6-Modules.asp u-blox 6] modules avialable)&lt;br /&gt;
* [http://www.expedienttech.com/ expedittech.com]&lt;br /&gt;
* [http://www.csgshop.com/category.php?id_category=16 csgshop.com US UBLOX MAX-6Q] ( Lithuania )&lt;br /&gt;
* [https://www.ppzuav.com/osc/product_info.php?cPath=13&amp;amp;products_id=75 ppzuav.com GPS13] (USA)&lt;br /&gt;
* [http://www.hobbyking.com/hobbyking/store/__31135__neo_6m_gps_module.html hobbyking.com NEO-6M] 22$&lt;br /&gt;
&lt;br /&gt;
==Airspeed Sensors==&lt;br /&gt;
&lt;br /&gt;
Eagle Tree Systems makes a small standalone airspeed sensor that can be connected via i2c. They also sell pitot tubes standalone for other differential pressure sensors.&lt;br /&gt;
*[http://www.eagletreesystems.com/Standalone/standalone.htm Eagle Tree Systems] (Also available from a number of distributors)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== DIGI XBee telemetry modules ==&lt;br /&gt;
For detailed shopping guide see [Modems]&lt;br /&gt;
*http://www.watterott.com/en/Digi (DE EU)&lt;br /&gt;
*https://store.diydrones.com/ (US See above for local distributors)&lt;br /&gt;
*http://unmannedtechshop.co.uk/UAV-Components/UAV-telemetry (UK)&lt;br /&gt;
*http://mouser.com/ (AU and other regions)&lt;br /&gt;
&lt;br /&gt;
=PCB=&lt;br /&gt;
==PPZUAV==&lt;br /&gt;
They sell some Autopilot PCB's [https://www.ppzuav.com/osc/index.php?cPath=1 here].&lt;br /&gt;
&lt;br /&gt;
==[http://www.olimex.com/pcb/ Olimex]==&lt;br /&gt;
*Fast PCB Prototypes [http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
*Development Boards [http://www.olimex.com/dev/index.html www.olimex.com/dev/]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==[http://www.platinensammler.de/%C3%BCber-mich/| platinensammler.de]==&lt;br /&gt;
&lt;br /&gt;
Cheap 2 and 4 layer boards from Germany, he orders around once a month 2 layer and only some infrequently 4 layer's by a german manufacturer.&lt;br /&gt;
&lt;br /&gt;
*2 layer 1cm² ~ 0.30€&lt;br /&gt;
*4 layer 1cm² ~ 0.60€&lt;br /&gt;
&lt;br /&gt;
==[http://oshpark.com/| OSH Park]==&lt;br /&gt;
Cheap 2 and 4 Layer boards.&lt;br /&gt;
Free wordwide shipping.&lt;br /&gt;
&lt;br /&gt;
in²&lt;br /&gt;
*3x 2 Layer 1in² = 5$&lt;br /&gt;
*3x 4 Layer 1in² = 10$&lt;br /&gt;
&lt;br /&gt;
cm²&lt;br /&gt;
*3x 2 Layer 1cm² = 0.78$&lt;br /&gt;
*3x 4 Layer 1cm² = 1.55$&lt;br /&gt;
(minimum order is 3 pcs, standard price is already for 3 pcs)&lt;br /&gt;
&lt;br /&gt;
= Old vendors =&lt;br /&gt;
&lt;br /&gt;
Here is a list of former paparazzi hardware vendors for reference. They were providing a great service to the Paparazzi community.&lt;br /&gt;
&lt;br /&gt;
* [http://chebuzz.com/paparazzi Chebuzz Pprz] had to move back to US and close his store, [http://aerofu.com/ AeroFu] is carrying on his business.&lt;br /&gt;
* [http://jobyrobotics.com Joby Robotics] stock and IP was bought by [http://transition-robotics.com Transition Robotics] that is carrying on their business.&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Contributing&amp;diff=14889</id>
		<title>Contributing</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Contributing&amp;diff=14889"/>
		<updated>2013-04-21T12:02:03Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Software development */  git remote add upstream, and fetch, before checking out a branch from upstream/master&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to contribute ==&lt;br /&gt;
There are of course lots of ways to contribute to Paparazzi and get involved.&lt;br /&gt;
&lt;br /&gt;
Help is always welcome on all aspects of the project. May this be documentation, wiki, maintenance, electronics or code contributions/fixes.&lt;br /&gt;
&lt;br /&gt;
=== Wiki ===&lt;br /&gt;
Just create an account and you can start adding information, cleaning it up or just fixing some typo you just noticed :-)&lt;br /&gt;
&lt;br /&gt;
Some information and links on how to edit the wiki can be found at [[Help:Editing]].&lt;br /&gt;
&lt;br /&gt;
Please be aware of past edits and page histories. Try not to remove this; if you are moving/renaming a page, use the '''move''' tab at the top of a page. This ensures the revision history is moved with the page.&lt;br /&gt;
&lt;br /&gt;
=== Software development ===&lt;br /&gt;
We use the distributed version control system [http://git-scm.com/ git]. The [http://github.com/paparazzi/paparazzi/ Papaprazzi master repository is hosted on Github].&lt;br /&gt;
&lt;br /&gt;
Also see the [[Git|Git wiki page]] for more details about setting up Git and cloning the source-code and data repository.&lt;br /&gt;
&lt;br /&gt;
Please also have a look at the [http://paparazzi.github.com/docs/latest/styleguide.html Coding Style Guide].&lt;br /&gt;
&lt;br /&gt;
Here is the short version if you already know git:&lt;br /&gt;
# Create an account on [http://github.com/ github].&lt;br /&gt;
# Fork the [http://github.com/paparazzi/paparazzi/ papaprazzi repo] on github. (After logging in press the '''fork''' button).&lt;br /&gt;
# '''git clone git@github.com:&amp;lt;yourname&amp;gt;/paparazzi.git'''&lt;br /&gt;
# '''git remote add upstream git@github.com:paparazzi/paparazzi.git'''&lt;br /&gt;
# '''git fetch upstream'''&lt;br /&gt;
# checkout a new branch based on the development branch (master):&amp;lt;br/&amp;gt;'''git checkout -b upstream/master my_new_feature'''&lt;br /&gt;
# fix/code and commit in logical units&lt;br /&gt;
# push your feature/bugfix branch&lt;br /&gt;
# Send us a [http://help.github.com/pull-requests/ pull request] on github. (Or send patches to the mailing list).&lt;br /&gt;
&lt;br /&gt;
=== Issue/Feature Tracker ===&lt;br /&gt;
To report bugs, issues and feature request please use either the mailing list or even better the simple [https://github.com/paparazzi/paparazzi/issues issue tracker on github]&lt;br /&gt;
&lt;br /&gt;
=== Continuous Integration Builds ===&lt;br /&gt;
We have a [http://paparazzi.gondwana.com.au build server] running some [[Builds/Tests|CI tests]].&lt;br /&gt;
&lt;br /&gt;
[[Category:Developer_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14338</id>
		<title>Modems</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14338"/>
		<updated>2013-02-07T10:10:48Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* SiLabs Si1000 SoC based modems */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Paparazzi autopilots generally feature a 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.&lt;br /&gt;
&lt;br /&gt;
== Digi XBee modules ==&lt;br /&gt;
&lt;br /&gt;
Digi (formerly Maxstream) offers an increasing variety of Zigbee protocol modems well suited for Paparazzi in 2.4 GHz, 900MHz and 868Mhz frequencies.  The &amp;quot;Pro&amp;quot; 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 &amp;quot;API mode&amp;quot; with hardware addressing, managed networking, and RSSI (signal strength) data with the Paparazzi &amp;quot;Xbee&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
* XBee (PRO) ZB (the current series)&lt;br /&gt;
* XBee (PRO) ZNet 2.5 (formerly Series 2) (only legacy -&amp;gt; use XBee-PRO ZB)&lt;br /&gt;
The XBee &amp;amp; XBee-PRO ZB share hardware (ember stack) with XBee &amp;amp; XBee-PRO ZNet 2.5. As a result, modules can be &amp;quot;converted&amp;quot; from one platform to another by loading different firmware onto a given module.&lt;br /&gt;
&lt;br /&gt;
These two also share the same hardware and can be converted from one to another by flashing a different firmware:&lt;br /&gt;
* XBee-PRO 802.15.4 (formerly Series 1)&lt;br /&gt;
* XBee-PRO DigiMesh 2.4&lt;br /&gt;
&lt;br /&gt;
'''Note: Modules based on Freescale chipset (formerly Series 1) are not compatible with Ember chipset based modules (Series 2).'''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Module Comparison ===&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''Module'''||'''Point-to-Multipoint'''||'''ZigBee/Mesh'''||'''Chipset'''|||'''Software stack'''||'''Frequency'''||'''TX Power normal/PRO'''||'''Notes'''&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZB'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet PRO 3.1 (ZigBee 2007)&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZNet 2.5'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet 2.5 ZigBee&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|(only legacy -&amp;gt; use XBee-PRO ZB) coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee DigiMesh 2.4'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|all nodes equal (no special coordinators/routers/end-devices)&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee 802.15.4'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee-PRO 868'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|?&lt;br /&gt;
|&lt;br /&gt;
|868 MHz&lt;br /&gt;
|500mW&lt;br /&gt;
|Only High Power Frequency allowed in the UK. 2.4GHz limited to 10mW&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Comparison Conclusion ====&lt;br /&gt;
&lt;br /&gt;
(Copied from DIGI manual)&lt;br /&gt;
&lt;br /&gt;
''If the application strictly needs to communicate in a point-to-point or a point-to-multipoint &lt;br /&gt;
fashion, 802.15.4 will be able handle all the communications between your devices and will &lt;br /&gt;
be simpler to implement than trying to use a module with ZigBee firmware to accomplish the &lt;br /&gt;
same goal. ZigBee is necessary if you need to use repeating or the mesh networking &lt;br /&gt;
functionality.'' &lt;br /&gt;
&lt;br /&gt;
-Interpretation for paparazzi: if inter-aircraft communication is required one should go for the zigbee ZB series 2 modules. &lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_Xbee_pinout.jpg|left|thumb|Maxstream XBee pinout]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||''Xbee 20-pin Header''||''Name''||''Notes''||''Suggested Color''||&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
| +3.3v&lt;br /&gt;
| Power&lt;br /&gt;
|Red&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|DOUT&lt;br /&gt;
|Tx output - connect to Autopilot Rx&lt;br /&gt;
|Green&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|DIN&lt;br /&gt;
|Rx input - connect to Autopilot Tx&lt;br /&gt;
|Blue&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|GND&lt;br /&gt;
| Ground&lt;br /&gt;
|Black&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The image view is from above, top, thus NOT at the side where the connector pins come out&lt;br /&gt;
&lt;br /&gt;
Note : DTR and RTS need to be wired for upgrading firmware&lt;br /&gt;
&lt;br /&gt;
=== GCS Adaptation ===&lt;br /&gt;
&lt;br /&gt;
There are several vendors of hardware to connect the ground XBee radio modem to the GCS computer.&lt;br /&gt;
&lt;br /&gt;
====Adafruit====&lt;br /&gt;
&lt;br /&gt;
[[Image:xbeeadapter_LRG.jpg|thumb|left|Adafruit XBee adapter board]][[Image:xbeeadapterftdi_LRG.jpg|thumb|Adafruit XBee adapter with FTDI cable]]&lt;br /&gt;
[http://www.adafruit.com/index.php?main_page=product_info&amp;amp;cPath=29&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Droids====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Simple_Board.jpg|thumb|left|XBee Simple Board]]&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_USB_Board.jpg|thumb|left|XBee USB Board]]&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?143-990.001-XBee-Simple-Board XBee Simple Board]&lt;br /&gt;
&lt;br /&gt;
Simpler, lighter, smaller footprint, bit more expensive, comes assembled and tested. --GR&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?152-990.002-XBee-USB-Board XBee USB Board]&lt;br /&gt;
&lt;br /&gt;
For direct connection to USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====PPZUAV====&lt;br /&gt;
&lt;br /&gt;
[[Image:FTDI_Utility_Board.jpg|thumb|left|FTDI Utility Board 1.0‎]]&lt;br /&gt;
&lt;br /&gt;
[https://mini.ppzuav.com/osc/product_info.php?cPath=13&amp;amp;products_id=111 ppzuav.com]&lt;br /&gt;
&lt;br /&gt;
FTDI Utility Board 1.0 (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Sparkfun====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Explorer_USB.jpg|thumb|left|XBee Explorer USB]]&lt;br /&gt;
&lt;br /&gt;
[http://www.sparkfun.com/products/8687 sparkfun.com]&lt;br /&gt;
&lt;br /&gt;
XBee Explorer USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro DigiMesh / 802.15.4 (&amp;quot;Series 1&amp;quot;) ===&lt;br /&gt;
*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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:Xbee_Pro_USB_RF_Modem.jpg|thumb|left|XBee Pro USB Stand-alone Modem (XBP24-PKC-001-UA)]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 2.4Ghz&lt;br /&gt;
* Output Power 100mW (Xbee Pro)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* RF Data Rate Up to 250 Kbps&lt;br /&gt;
* Interface data rate Up to 115.2 Kbps&lt;br /&gt;
* Power Draw (typical) 214 mA TX / 55 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1500m line-of-sight &lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Chip antenna, ¼ monopole integrated whip antenna or a U.FL antenna connector (3 versions)&lt;br /&gt;
* Price: Approximately $32&lt;br /&gt;
|&lt;br /&gt;
[[Image:XBee_pro.jpg|thumb|left|XBee Pro OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
Mouser: [http://au.mouser.com/Search/ProductDetail.aspx?qs=sGAEpiMZZMtJacPDJcUJYzVn8vIv7g2fIpf5DCzJqko%3d 888-XBP24-PKC-001-UA]&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/xbee-pro-oem-rf-module-zigbee.php  product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/datasheet_XBee_OEM_RF-Modules.pdf  datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/product-manual_XBee_OEM_RF-Modules.pdf  user manual]&lt;br /&gt;
* To program your Xbee you need X-CTU you can download it [http://www.digi.com/support/productdetl.jsp?pid=3352&amp;amp;osvid=57&amp;amp;tp=5&amp;amp;s=316 here]. (only windows)&lt;br /&gt;
* explanation on X-CTU [http://www.ladyada.net/make/xbee/configure.html here].&lt;br /&gt;
* [http://ftp1.digi.com/support/firmware/update/xbee/ Drivers for XB24 and XBP24 modules]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro ZB / ZNet 2.5 (&amp;quot;Series 2&amp;quot;) ===&lt;br /&gt;
&lt;br /&gt;
The low-power XBee ZB and extended-range XBee-PRO ZB use the ZigBee PRO Feature Set for advanced mesh networking.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:XBee_Pro_2SB.jpg|thumb|left|Digi XBee Pro ZB]]&lt;br /&gt;
|&lt;br /&gt;
* Low-cost, low-power mesh networking&lt;br /&gt;
* Interoperability with ZigBee PRO Feature Set devices from other vendors*&lt;br /&gt;
* Support for larger, more dense mesh networks&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* Frequency agility&lt;br /&gt;
* Over-the-air firmware updates (change firmware remotely)&lt;br /&gt;
* ISM 2.4 GHz operating frequency&lt;br /&gt;
* XBee: 2 mW (+3 dBm) power output (up to 400 ft RF LOS range)&lt;br /&gt;
* XBee-PRO: 50 mW (+17 dBm) power output (up to 1 mile RF LOS range)&lt;br /&gt;
* RPSMA connector, U.FL connector, Chip antenna, or Wired Whip antenna&lt;br /&gt;
* price : ~34 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
These are available from Mouser:&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=888-XBP24-Z7WIT-004 888-XBP24-Z7WIT-004] XBee-PRO ZB with whip antenna&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=XBP24-Z7SIT-004 888-XBP24-Z7SIT-004] XBee-PRO ZB with RPSMA&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 868 ===&lt;br /&gt;
&lt;br /&gt;
'''WARNING - THESE MODEMS HAVE A 10% DUTY CYCLE, AND CURRENTLY HAVE SEVERE ISSUES WITH PAPARAZZI'''&lt;br /&gt;
&lt;br /&gt;
868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro 868]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G3 band for Europe&lt;br /&gt;
* Software selectable Transmit Power&lt;br /&gt;
* 40 km RF LOS w/ dipole antennas&lt;br /&gt;
* 80 km RF LOS w/ high gain antennas (TX Power reduced)&lt;br /&gt;
* Simple to use peer-to-peer/point-to-mulitpoint topology&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* 500 mW EIRP&lt;br /&gt;
* 24 kbps RF data rate&lt;br /&gt;
* price : ~70 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration#XBee_Pro_868_MHZ|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee 868LP ===&lt;br /&gt;
&lt;br /&gt;
XBee 868LP modules are a low-power 868 MHz RF module for use in Europe. The range is shorter than it's brother the XBee PRO-868, but it can use the 868 G4 band with hopping which does not have restrictions on it's duty cycle. This is a big advantage if one want to have a good stream of telemetry data&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:868lp.jpg|thumb|left|XBee 868LP]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G4 band for Europe&lt;br /&gt;
* 4 km RF LOS w/ u.fl antennas&lt;br /&gt;
* 5 mW EIRP&lt;br /&gt;
* 80 kbps RF data rate&lt;br /&gt;
* price : ~23 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview]&lt;br /&gt;
&lt;br /&gt;
==== Trial ====&lt;br /&gt;
&lt;br /&gt;
With a quickly crafted and not optimal positioned antenna on the airframe we managed to get the advertised 4000 meter range. Data throughput was not high and the Iridium Telemetry XML configuration document was therefore used. All in all, cheap, easy to setup, pin compatible with regular modules and quite a range and usable in Europe without hassle.&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 900 (XBEE09P) ===&lt;br /&gt;
&lt;br /&gt;
XBee Pro 900 modules are long range embedded RF modules for US applications. Purpose-built for exceptional RF performance, XBee-Pro 900 modules are ideal for applications with challenging RF environments, such as urban deployments, or where devices are several kilometers apart.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [ftp://ftp1.digi.com/support/documentation/90000903_a.pdf]&lt;br /&gt;
&lt;br /&gt;
I've been using a pair of these for about 6 months now and they works great. To set it up I just used a serial terminal app like CoolTerm or screen and made sure I could send messages between the two of them. - cwozny&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro XSC 900MHz ===&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro XSC]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900 MHz&lt;br /&gt;
* Output Power 100 mW (+20 dBm)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* Data Rate: 9600 bps&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 24km (15 miles) line-of-sight &lt;br /&gt;
* Interface 20-pin mini connector (Xbee compatible pinout)&lt;br /&gt;
* RPSMA, integrated whip antenna or U.FL antenna connector (3 versions)&lt;br /&gt;
* price : $39 USD (on DigiKey)&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp]&lt;br /&gt;
==== Trials ====&lt;br /&gt;
Tested one today and it worked great. Going to try a multiUAV test with it soon&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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 &amp;quot;commit and reboot&amp;quot; type command after setting the baud rate. Could this be the case? --GR&lt;br /&gt;
&lt;br /&gt;
=== Digi 9XTend ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
[[Image:XTend_USB_RF_Modem.jpg|frame|left|9XTend USB Modem]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900Mhz and 2.4Ghz (2 versions)&lt;br /&gt;
* Output Power 1mW to 1W software selectable&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* RF Data Rate 9.6 or 115.2 Kbps&lt;br /&gt;
* Interface data rate up to 230.4 Kbps&lt;br /&gt;
* Power Draw (typical) 730 mA TX / 80 mA RX &lt;br /&gt;
* Supply Voltage 2.8 to 5.5v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 64km line-of-sight &lt;br /&gt;
* Dimensions 36 x 60 x 5mm&lt;br /&gt;
* Weight 18 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* RF connector RPSMA (Reverse-polarity SMA) or MMCX (2 versions)&lt;br /&gt;
* price : ~179 USD&lt;br /&gt;
|&lt;br /&gt;
[[Image:Xtend_module.jpg|frame|left|9XTend OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_9XTend_Pinout.gif|thumb|left|Maxstream 9XTend Pinout]]&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''9XTend 20-pin Header'''''||'''''Name'''''||'''''Tiny Serial-1 Header'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||1||GND||1 (GND)||Ground &lt;br /&gt;
|-&lt;br /&gt;
||2||VCC||2 (5V)||5V power (150mA - 730mA Supplied from servo bus or other 5V source)&lt;br /&gt;
|-&lt;br /&gt;
||5||RX||8 (TX)||3-5V TTL data input - connect to Tiny TX&lt;br /&gt;
|-&lt;br /&gt;
||6||TX||7 (RX)||5V TTL data output - connect to Tiny RX&lt;br /&gt;
|-&lt;br /&gt;
||7||Shutdown||2||This pin must be connected to the 5V bus for normal operation&lt;br /&gt;
|}&lt;br /&gt;
Notes:&amp;lt;br&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/oem-rf-module.php product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/datasheet_XTend_OEM_RF-Module.pdf datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/product-manual_XTend_OEM_RF-Module.pdf user manual]&lt;br /&gt;
&lt;br /&gt;
==== Configuration ====&lt;br /&gt;
&lt;br /&gt;
These modems need to be carefully configured based on your usage scenario to obtain the best possible range and link quality. In addition, it is always good to make sure the firmware is up to date.&lt;br /&gt;
&lt;br /&gt;
Some typical configurations that may work well, but can still depend your particular situation, are given below. For further details, be sure to consult the XTend users manual. Your application may need a different or modified configuration. The radiomodems do not need identical settings and can in fact be optimized with different settings. A good example is delays and retries: if each radio has the same number of retries and no delay, when a collision occurs each will continuously try to re-transmit, locking up the transmission for some time with no resolution or successful packet delivery. Instead, it is best to set the module whose data should have a lower latency to have no delay and a lower number of retries, while the other module has a delay set (RN &amp;gt; 0) and a greater number of retries. See acknowledged mode example below.&lt;br /&gt;
&lt;br /&gt;
* Acknowledged Polling Mode ('''Recommended'''):&lt;br /&gt;
** This causes one radio to be the base and the other(s) to be the remote(s). It eliminates collisions because remotes do not send data unless requested by the base. It can work in acknowledged mode (RR&amp;gt;0), basic reliable mode (MT&amp;gt;0) or in basic mode (no acknowledgement or multiple packets). It is recommended that the lower latency and/or higher data rate side be configured as the base (i.e. if you are sending lots of telemetry then the air module configured as the base is probably a good idea, but if you are using datalink joystick control, the ground side might be better as the base. It may require some experimentation).&lt;br /&gt;
* Acknowledged Point-to-(Multi)Point Mode:&lt;br /&gt;
** Each radio sends a packet and requests and acknowledgement that the packet was sent from the receiving side. The retries and delays must be set appropriately to ensure packet collisions are dealt with appropriately. It can also work without acknowledgements in basic reliable mode (MT&amp;gt;0) without any acknowledgements (RR=0, MT=0). Some experimentation may be required.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''Setting Name'''''||colspan=&amp;quot;2&amp;quot;|'''''Acknowledged Mode'''''||colspan=&amp;quot;2&amp;quot;|'''''Polling Mode (Acknowledged)'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
|| ||'''''Airside Module'''''||'''''Groundside Module'''''||'''''Base Module'''''||'''''Remote Module'''''||&lt;br /&gt;
|-&lt;br /&gt;
||BD||6||6||6||6||Adjust to match your configured autopilot and ground station baud rates (default for these is 57600bps)&lt;br /&gt;
|-&lt;br /&gt;
||DT||default||default||0x02||0x01||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MD||default||default||3 (0x03)||4 (0x04)||&lt;br /&gt;
|-&lt;br /&gt;
||MT||0||0||0||0||Use this to enable Basic Reliable transmission, link bandwidth requirement increases (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MY||default||default||0x01||0x02||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PB||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PD||default||default||default||default||Can be adjusted to increase polling request rate and DI buffer flush timeout (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PE||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PL||default||default||default||default||''Transmit power level should be reduced for lab testing!!''&lt;br /&gt;
|-&lt;br /&gt;
||RN||0 (0x00)||8 (0x08)||default||default||&lt;br /&gt;
|-&lt;br /&gt;
||RR||6 (0x06)||12 (0x0C)||6 (0x06)||12 (0x0C)||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Note:''' All settings are assumed to be default except those listed. Those listed are in decimal unless hex 0x prefix included. Depending on your firmware version, slight modifications may be necessary.&lt;br /&gt;
&lt;br /&gt;
Here is some additional information and alternative instructions to configure the polling mode from the Digi site: [http://www.digi.com/support/kbase/kbaseresultdetl?id=2178 Polling Mode for the 9XTend Radio Modem]&lt;br /&gt;
&lt;br /&gt;
== SiLabs Si1000 SoC based modems ==&lt;br /&gt;
&lt;br /&gt;
The Si1000 radio System on Chip (SOC) produced by  SiLabs is found in a number of radio modules, for example the cheap and widely used HopeRf module. There is [https://github.com/tridge/SiK open source firmware] for these radios which makes them suitable for use in MAVs. &lt;br /&gt;
&lt;br /&gt;
Note that (unlike some XBee modules) the SiK firmware does not support mesh topologies, it is strictly a point-to-point link. If you are working with swarming vehicles they may not be the best choice.&lt;br /&gt;
&lt;br /&gt;
Online documentation for the Sik firmware shows how to configure it for various jurisdictions. The firmware supports 433 MHz, 470 MHz, 868 MHz and 900 MHz radios, if you are aware of any hardware supporting the European spectrum licences (868 MHz) please add them to this wiki.&lt;br /&gt;
&lt;br /&gt;
Note: When using a SiK firmware radio with paparazzi, you should set &amp;quot;ATS6=0&amp;quot; (MavLink packing off) and configure paparazzi for transparent serial mode.&lt;br /&gt;
&lt;br /&gt;
[http://www.rfdesign.com.au/index.php/rfd900 This module] is well proven and supports antenna diversity. A combination of 6dbi Yagi plus a dipole on the ground station, with a pair of  orthogonality oriented dioples in the airframe, has been extensively tested and proven reliable at &amp;gt;8km range (theoretical range of ~40km).&lt;br /&gt;
&lt;br /&gt;
Alternatively, for shorter range a pair of cheap generic HopeRF-based modems [http://rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=815 such as these]&lt;br /&gt;
&lt;br /&gt;
The RFD900 can be paired with cheap generic (single front-end) modules, if for example you use a small short range airframe with a ground station that's also used for long range operations.&lt;br /&gt;
&lt;br /&gt;
== Aerocomm ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
How to use this modem on ground station side? [http://paparazzi.enac.fr/wiki/index.php/User:SilaS#SDK-AC4868-250_ground_modem_part]&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;main&amp;quot; link.ml file of the ground sttaion and will be merged into it in the future.. or you can do it as well.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== AC4868-250 ===&lt;br /&gt;
* Frequency Band 868MHz (For Europe). 868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
* Output Power (w/ 2dBi antenna) 250 mW &lt;br /&gt;
* Sensitivity (@ full RF data rate) -103 dB &lt;br /&gt;
* RF Data Rate Up to 28.8 Kbps &lt;br /&gt;
* INterface Data Rate Up to 57.6 Kbps &lt;br /&gt;
* Power Draw (typical) 240 mA TX / 36 mA RX &lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5V or 3.3v only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 15 kilometers line-of-sight &lt;br /&gt;
* Dimensions 49 x 42 x 5mm &lt;br /&gt;
* Weight &amp;lt; 21 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector &lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ConnexLink_USB_RF_Modem.jpg|thumb|Aerocomm USB Stand-alone Modem]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-200 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-200mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -110dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 68 mA&lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5.5V&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 6.4 kilometers line-of-sight &lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector or internal&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ac4868_transceiver.jpg|thumb|left|AC4868 OEM Modem]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-1000 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-1000mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -99dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 650 mA&lt;br /&gt;
* Supply Voltage 3.3V only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 32 kilometers with high-gain antenna&lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Aerocomm_AC4868_pinout.jpg|thumb|left|Aerocomm AC4868 modem pinout]]&lt;br /&gt;
[[Image:Aerocomm_AC4490-200_wired.jpg|thumb|left|Aerocomm AC4490 wiring example]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the Aerocomm AC4868 to the Tiny&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''AC4868 20-pin Header'''''||'''''Name'''''||'''''Color'''''||'''''Tiny v1.1 Serial-1'''''||'''''Tiny v2.11 Serial'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||2||Tx||green||7||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||3||Rx||blue||8||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||GND||black||1||1|| -&lt;br /&gt;
|-&lt;br /&gt;
||10+11||VCC||red||2||3||+3.3v ''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||17||C/D||white||3||?||Low = Command High = Data&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the AEROCOMM module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : AC4790-1000 needs pins 10 and 11 jumped to work properly''&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4790_mesh-ready_transceiver.htm AC4790 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4790_HI.pdf AC4790 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4790.pdf AC4790 Manual]&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4868_868mhz_rf_transceiver.htm AC4848 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4868_HI.pdf AC4868 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4868.pdf AC4868 user manual]&lt;br /&gt;
&lt;br /&gt;
== Laird (ex Aerocomm) ==&lt;br /&gt;
&lt;br /&gt;
=== Laird LT2510 ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Lt2510_prm123.jpg|thumb|LT2510 Modem]]&lt;br /&gt;
&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 50mW (European version)&lt;br /&gt;
* Sensitivity  -98/-94 dBm &lt;br /&gt;
* RF Data Rate 280/500 kbps&lt;br /&gt;
* Interface data rate Up to 460800 kbps&lt;br /&gt;
* Power Draw (typical) 85mA TX / 10mA RX (European version)&lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 2400m line-of-sight (European version)&lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector (solder pad or XBee compatible)&lt;br /&gt;
* Chip antenna, or a U.FL antenna connector&lt;br /&gt;
* Price: Approximately $31&lt;br /&gt;
&lt;br /&gt;
The LT2510 uses frequency hopping which needs a client/server model. That means that one modem (most appropriately the ground station modem) needs to be set to server mode. It will transmit a beacon message and have all client modems synchronize to that in a time and frequency hopping scheme manner. For that all modems need to have the same channel (in fact the hopping scheme) and system-id. Clients can be set to auto-channel and auto-system-id to follow any/the first visible server.&lt;br /&gt;
&lt;br /&gt;
All acknowledged messages transmitted need to be adressed to the non-changeable MAC address of the destination modem. There are is a way to automatically set destination adresses but this procedure does have drawbacks (see below).&lt;br /&gt;
&lt;br /&gt;
Make sure you short circuit &amp;quot;D1&amp;quot; if you use the Sparkfun WRL-09132 &amp;quot;XBee Explorer Regulated&amp;quot; adapter. The Laird does not have a pull-up resistor on DIN that Sparkfun assumes.&lt;br /&gt;
&lt;br /&gt;
==== Basic setup ====&lt;br /&gt;
&lt;br /&gt;
You can download a Windows configuration utility from [http://www.lairdtech.com/Products/Wireless-M2M-and-Telematics-Solutions/Proprietary-Radio-Modules/ here], click &amp;quot;Product Information&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
 Set client to client mode (default).&lt;br /&gt;
 Set server to server mode.&lt;br /&gt;
&lt;br /&gt;
 Set speed on both modems to 57600 baud, the Paparazzi standard.&lt;br /&gt;
&lt;br /&gt;
 Choose RF profile with low speed (280kbps) for long range (default).&lt;br /&gt;
&lt;br /&gt;
===== Transparent mode =====&lt;br /&gt;
&lt;br /&gt;
The transparent mode is different from the XBee modems transparent mode. It will only allow two modems to communicate with each other.&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with hard coded address ======&lt;br /&gt;
&lt;br /&gt;
In this mode the destination MAC address is permanently set in the EEPROMs of the modems. Only these two modems can communicate with each other. The advantage of this mode is that other modems can not confuse the communication. You have to read out both modems MAC adresses as they are not printed on the case.&lt;br /&gt;
&lt;br /&gt;
 Set server MAC address in client&lt;br /&gt;
 Set client MAC address in server&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with auto-address ======&lt;br /&gt;
&lt;br /&gt;
The server will start emitting beacon messages and the client locks to these, starting to send messages to the servers MAC address. The server will then respond to that clients data messages. In this mode only one server can talk to one client. Any appearance of another server or client modem will confuse/disrupt the communication.&lt;br /&gt;
&lt;br /&gt;
 Set server to auto-destination.&lt;br /&gt;
 Set client to auto-destination and auto-destination-beacons-only.&lt;br /&gt;
&lt;br /&gt;
===== API mode =====&lt;br /&gt;
&lt;br /&gt;
We need at least a simple form of address resolution as the modems own (MAC) address can not be changed. This makes the ground station link and on-board software a little more complicated than the XBee API mode.&lt;br /&gt;
&lt;br /&gt;
 tbd&lt;br /&gt;
&lt;br /&gt;
== Radiotronix ==&lt;br /&gt;
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-&amp;gt;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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== WI232EUR ===&lt;br /&gt;
* Frequency Band: 868 MHz (for Europe)&lt;br /&gt;
* Output Power: 32 mW &lt;br /&gt;
* RF Data Rate: Up to 76.8 kbps &lt;br /&gt;
* Interface Data Rate: up to 115.2 kbps &lt;br /&gt;
* Power Draw (typical): 65 mA TX / 20 mA RX &lt;br /&gt;
* Supply Voltage: 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment): 500 meters line-of-sight &lt;br /&gt;
* Dimensions: 24 x 21 x 4mm &lt;br /&gt;
* Weight: ~2 grams&lt;br /&gt;
* Interface: solder connector  &lt;br /&gt;
* Antenna: solder connector &lt;br /&gt;
* Price: ~25$&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_wiring.jpg|thumb|WI232EUR Modem (picture shows connection to Tiny 1.1)]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the WI232EUR to the Tiny v1.1&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''WI232 pins'''''||'''''Name'''''||'''''Tiny Serial-1'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||6||TxD||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||RxD||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||15-18||GND||1|| - &lt;br /&gt;
|-&lt;br /&gt;
||19||VCC||2||+3.3v&lt;br /&gt;
|-&lt;br /&gt;
||4||/CMD||-||''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||7||CTS||-||''(Note 3)''&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the Radiotronix module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : connect to RTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
''Note 3 : connect to CTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_bopla.jpg|thumb|WI232EUR Modem in BOPLA case]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/eur_um.pdf WI232EUR data sheet]&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/rk-eur_um.pdf WI232EUR user's manual]&lt;br /&gt;
* [http://www.radiotronix.com/downloads/software/EUR/setup.exe Evaluation software]&lt;br /&gt;
&lt;br /&gt;
== Bluetooth ==&lt;br /&gt;
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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== &amp;quot;Sparkfun&amp;quot; Roving Networks (WRL-08497) ===&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 32 mW &lt;br /&gt;
* RF Data Rate up to ~300 kbps in SPP&lt;br /&gt;
* Interface Data Rate up to 921 kbps &lt;br /&gt;
* Power Draw (typical) 50 mA TX / 40 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) 100 meters line-of-sight &lt;br /&gt;
* Dimensions 26 x 13 x 2mm &lt;br /&gt;
* Weight ~1.5 grams&lt;br /&gt;
* Interface solder connector  &lt;br /&gt;
* price : ~45$&lt;br /&gt;
|&lt;br /&gt;
[[Image:roving_nw_wiring.jpg|thumb|Roving Networks modem wiring]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
To connect to it, get the MAC address of the bluetooth modem&lt;br /&gt;
&lt;br /&gt;
 me@mybox:~$ hcitool scan&lt;br /&gt;
 Scanning ...&lt;br /&gt;
        00:06:66:00:53:AD       FireFly-53AD&lt;br /&gt;
&lt;br /&gt;
either make a virtual connection to a Bluetooth serial port each time you connect&lt;br /&gt;
&lt;br /&gt;
 sudo rfcomm bind 0 00:06:66:00:53:AD&lt;br /&gt;
&lt;br /&gt;
or configure it once in /etc/bluetooth/rfcomm.conf&lt;br /&gt;
&lt;br /&gt;
 rfcomm0 {&lt;br /&gt;
   bind yes;&lt;br /&gt;
   device 00:06:66:00:53:AD;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Coronis WaveCard ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''Suport for these modems has been removed from the airborne code on Dec 10th, 2007.'''&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 400MHz, 868Mhz and 915MHz (3 versions)&lt;br /&gt;
* Output Power 25mW and 500mW (2 versions)&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* Data Rate 100 Kbps&lt;br /&gt;
* Power Draw (typical) 45mA (25mW), 450mA (500mW) TX / 15 mA RX &lt;br /&gt;
* Supply Voltage ...&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1km (25mW) , 5km (500mW) line-of-sight &lt;br /&gt;
* Dimensions 30 x 28 x 7mm (25mW), 37 x 30 x 7mm (500mW)&lt;br /&gt;
* 50 ohm RF port for antenna connection&lt;br /&gt;
|&lt;br /&gt;
[[Image:wavecard.jpg|Coronis Wavecard]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.coronis-systems.com/produit.php?lang=EN&amp;amp;id=WCA  www.coronis-systems.com]&lt;br /&gt;
* [[Media:CS-COM-SPRD-WAVECARD-E03B.pdf|Wavecard datasheet]]&lt;br /&gt;
&lt;br /&gt;
== Telemetry via Video Transmitter==&lt;br /&gt;
&lt;br /&gt;
[[Image:video_tx_small.jpg|thumb|2.4GHz Video Transmitter]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Antennas ==&lt;br /&gt;
&lt;br /&gt;
Here are some examples of lightweight and efficient 868MHz antennas developped by the RF laboratory at ENAC.&lt;br /&gt;
[[Image:868mhz_twinstar_antenna_1.jpg|thumb|left|868MHz copper foil antenna attached to the aircraft tail]] &lt;br /&gt;
[[Image:868mhz_twinstar_antenna_2.jpg|thumb|left|868MHz copper foil antenna bottom view]] &lt;br /&gt;
[[Image:868mhz_ground_antenna.jpg|thumb|left|868MHz ground antenna]] &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This wiki page might give some ideas about antennas: http://en.wikipedia.org/wiki/Dipole_antenna&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14321</id>
		<title>Modems</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14321"/>
		<updated>2013-02-04T11:29:19Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Availability */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Paparazzi autopilots generally feature a 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.&lt;br /&gt;
&lt;br /&gt;
== Digi XBee modules ==&lt;br /&gt;
&lt;br /&gt;
Digi (formerly Maxstream) offers an increasing variety of Zigbee protocol modems well suited for Paparazzi in 2.4 GHz, 900MHz and 868Mhz frequencies.  The &amp;quot;Pro&amp;quot; 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 &amp;quot;API mode&amp;quot; with hardware addressing, managed networking, and RSSI (signal strength) data with the Paparazzi &amp;quot;Xbee&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
* XBee (PRO) ZB (the current series)&lt;br /&gt;
* XBee (PRO) ZNet 2.5 (formerly Series 2) (only legacy -&amp;gt; use XBee-PRO ZB)&lt;br /&gt;
The XBee &amp;amp; XBee-PRO ZB share hardware (ember stack) with XBee &amp;amp; XBee-PRO ZNet 2.5. As a result, modules can be &amp;quot;converted&amp;quot; from one platform to another by loading different firmware onto a given module.&lt;br /&gt;
&lt;br /&gt;
These two also share the same hardware and can be converted from one to another by flashing a different firmware:&lt;br /&gt;
* XBee-PRO 802.15.4 (formerly Series 1)&lt;br /&gt;
* XBee-PRO DigiMesh 2.4&lt;br /&gt;
&lt;br /&gt;
'''Note: Modules based on Freescale chipset (formerly Series 1) are not compatible with Ember chipset based modules (Series 2).'''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Module Comparison ===&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''Module'''||'''Point-to-Multipoint'''||'''ZigBee/Mesh'''||'''Chipset'''|||'''Software stack'''||'''Frequency'''||'''TX Power normal/PRO'''||'''Notes'''&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZB'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet PRO 3.1 (ZigBee 2007)&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZNet 2.5'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet 2.5 ZigBee&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|(only legacy -&amp;gt; use XBee-PRO ZB) coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee DigiMesh 2.4'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|all nodes equal (no special coordinators/routers/end-devices)&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee 802.15.4'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee-PRO 868'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|?&lt;br /&gt;
|&lt;br /&gt;
|868 MHz&lt;br /&gt;
|500mW&lt;br /&gt;
|Only High Power Frequency allowed in the UK. 2.4GHz limited to 10mW&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Comparison Conclusion ====&lt;br /&gt;
&lt;br /&gt;
(Copied from DIGI manual)&lt;br /&gt;
&lt;br /&gt;
''If the application strictly needs to communicate in a point-to-point or a point-to-multipoint &lt;br /&gt;
fashion, 802.15.4 will be able handle all the communications between your devices and will &lt;br /&gt;
be simpler to implement than trying to use a module with ZigBee firmware to accomplish the &lt;br /&gt;
same goal. ZigBee is necessary if you need to use repeating or the mesh networking &lt;br /&gt;
functionality.'' &lt;br /&gt;
&lt;br /&gt;
-Interpretation for paparazzi: if inter-aircraft communication is required one should go for the zigbee ZB series 2 modules. &lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_Xbee_pinout.jpg|left|thumb|Maxstream XBee pinout]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||''Xbee 20-pin Header''||''Name''||''Notes''||''Suggested Color''||&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
| +3.3v&lt;br /&gt;
| Power&lt;br /&gt;
|Red&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|DOUT&lt;br /&gt;
|Tx output - connect to Autopilot Rx&lt;br /&gt;
|Green&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|DIN&lt;br /&gt;
|Rx input - connect to Autopilot Tx&lt;br /&gt;
|Blue&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|GND&lt;br /&gt;
| Ground&lt;br /&gt;
|Black&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The image view is from above, top, thus NOT at the side where the connector pins come out&lt;br /&gt;
&lt;br /&gt;
Note : DTR and RTS need to be wired for upgrading firmware&lt;br /&gt;
&lt;br /&gt;
=== GCS Adaptation ===&lt;br /&gt;
&lt;br /&gt;
There are several vendors of hardware to connect the ground XBee radio modem to the GCS computer.&lt;br /&gt;
&lt;br /&gt;
====Adafruit====&lt;br /&gt;
&lt;br /&gt;
[[Image:xbeeadapter_LRG.jpg|thumb|left|Adafruit XBee adapter board]][[Image:xbeeadapterftdi_LRG.jpg|thumb|Adafruit XBee adapter with FTDI cable]]&lt;br /&gt;
[http://www.adafruit.com/index.php?main_page=product_info&amp;amp;cPath=29&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Droids====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Simple_Board.jpg|thumb|left|XBee Simple Board]]&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_USB_Board.jpg|thumb|left|XBee USB Board]]&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?143-990.001-XBee-Simple-Board XBee Simple Board]&lt;br /&gt;
&lt;br /&gt;
Simpler, lighter, smaller footprint, bit more expensive, comes assembled and tested. --GR&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?152-990.002-XBee-USB-Board XBee USB Board]&lt;br /&gt;
&lt;br /&gt;
For direct connection to USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====PPZUAV====&lt;br /&gt;
&lt;br /&gt;
[[Image:FTDI_Utility_Board.jpg|thumb|left|FTDI Utility Board 1.0‎]]&lt;br /&gt;
&lt;br /&gt;
[https://mini.ppzuav.com/osc/product_info.php?cPath=13&amp;amp;products_id=111 ppzuav.com]&lt;br /&gt;
&lt;br /&gt;
FTDI Utility Board 1.0 (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Sparkfun====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Explorer_USB.jpg|thumb|left|XBee Explorer USB]]&lt;br /&gt;
&lt;br /&gt;
[http://www.sparkfun.com/products/8687 sparkfun.com]&lt;br /&gt;
&lt;br /&gt;
XBee Explorer USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro DigiMesh / 802.15.4 (&amp;quot;Series 1&amp;quot;) ===&lt;br /&gt;
*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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:Xbee_Pro_USB_RF_Modem.jpg|thumb|left|XBee Pro USB Stand-alone Modem (XBP24-PKC-001-UA)]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 2.4Ghz&lt;br /&gt;
* Output Power 100mW (Xbee Pro)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* RF Data Rate Up to 250 Kbps&lt;br /&gt;
* Interface data rate Up to 115.2 Kbps&lt;br /&gt;
* Power Draw (typical) 214 mA TX / 55 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1500m line-of-sight &lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Chip antenna, ¼ monopole integrated whip antenna or a U.FL antenna connector (3 versions)&lt;br /&gt;
* Price: Approximately $32&lt;br /&gt;
|&lt;br /&gt;
[[Image:XBee_pro.jpg|thumb|left|XBee Pro OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
Mouser: [http://au.mouser.com/Search/ProductDetail.aspx?qs=sGAEpiMZZMtJacPDJcUJYzVn8vIv7g2fIpf5DCzJqko%3d 888-XBP24-PKC-001-UA]&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/xbee-pro-oem-rf-module-zigbee.php  product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/datasheet_XBee_OEM_RF-Modules.pdf  datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/product-manual_XBee_OEM_RF-Modules.pdf  user manual]&lt;br /&gt;
* To program your Xbee you need X-CTU you can download it [http://www.digi.com/support/productdetl.jsp?pid=3352&amp;amp;osvid=57&amp;amp;tp=5&amp;amp;s=316 here]. (only windows)&lt;br /&gt;
* explanation on X-CTU [http://www.ladyada.net/make/xbee/configure.html here].&lt;br /&gt;
* [http://ftp1.digi.com/support/firmware/update/xbee/ Drivers for XB24 and XBP24 modules]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro ZB / ZNet 2.5 (&amp;quot;Series 2&amp;quot;) ===&lt;br /&gt;
&lt;br /&gt;
The low-power XBee ZB and extended-range XBee-PRO ZB use the ZigBee PRO Feature Set for advanced mesh networking.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:XBee_Pro_2SB.jpg|thumb|left|Digi XBee Pro ZB]]&lt;br /&gt;
|&lt;br /&gt;
* Low-cost, low-power mesh networking&lt;br /&gt;
* Interoperability with ZigBee PRO Feature Set devices from other vendors*&lt;br /&gt;
* Support for larger, more dense mesh networks&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* Frequency agility&lt;br /&gt;
* Over-the-air firmware updates (change firmware remotely)&lt;br /&gt;
* ISM 2.4 GHz operating frequency&lt;br /&gt;
* XBee: 2 mW (+3 dBm) power output (up to 400 ft RF LOS range)&lt;br /&gt;
* XBee-PRO: 50 mW (+17 dBm) power output (up to 1 mile RF LOS range)&lt;br /&gt;
* RPSMA connector, U.FL connector, Chip antenna, or Wired Whip antenna&lt;br /&gt;
* price : ~34 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
These are available from Mouser:&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=888-XBP24-Z7WIT-004 888-XBP24-Z7WIT-004] XBee-PRO ZB with whip antenna&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=XBP24-Z7SIT-004 888-XBP24-Z7SIT-004] XBee-PRO ZB with RPSMA&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 868 ===&lt;br /&gt;
&lt;br /&gt;
'''WARNING - THESE MODEMS HAVE A 10% DUTY CYCLE, AND CURRENTLY HAVE SEVERE ISSUES WITH PAPARAZZI'''&lt;br /&gt;
&lt;br /&gt;
868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro 868]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G3 band for Europe&lt;br /&gt;
* Software selectable Transmit Power&lt;br /&gt;
* 40 km RF LOS w/ dipole antennas&lt;br /&gt;
* 80 km RF LOS w/ high gain antennas (TX Power reduced)&lt;br /&gt;
* Simple to use peer-to-peer/point-to-mulitpoint topology&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* 500 mW EIRP&lt;br /&gt;
* 24 kbps RF data rate&lt;br /&gt;
* price : ~70 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration#XBee_Pro_868_MHZ|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee 868LP ===&lt;br /&gt;
&lt;br /&gt;
XBee 868LP modules are a low-power 868 MHz RF module for use in Europe. The range is shorter than it's brother the XBee PRO-868, but it can use the 868 G4 band with hopping which does not have restrictions on it's duty cycle. This is a big advantage if one want to have a good stream of telemetry data&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:868lp.jpg|thumb|left|XBee 868LP]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G4 band for Europe&lt;br /&gt;
* 4 km RF LOS w/ u.fl antennas&lt;br /&gt;
* 5 mW EIRP&lt;br /&gt;
* 80 kbps RF data rate&lt;br /&gt;
* price : ~23 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview]&lt;br /&gt;
&lt;br /&gt;
==== Trial ====&lt;br /&gt;
&lt;br /&gt;
With a quickly crafted and not optimal positioned antenna on the airframe we managed to get the advertised 4000 meter range. Data throughput was not high and the Iridium Telemetry XML configuration document was therefore used. All in all, cheap, easy to setup, pin compatible with regular modules and quite a range and usable in Europe without hassle.&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 900 (XBEE09P) ===&lt;br /&gt;
&lt;br /&gt;
XBee Pro 900 modules are long range embedded RF modules for US applications. Purpose-built for exceptional RF performance, XBee-Pro 900 modules are ideal for applications with challenging RF environments, such as urban deployments, or where devices are several kilometers apart.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [ftp://ftp1.digi.com/support/documentation/90000903_a.pdf]&lt;br /&gt;
&lt;br /&gt;
I've been using a pair of these for about 6 months now and they works great. To set it up I just used a serial terminal app like CoolTerm or screen and made sure I could send messages between the two of them. - cwozny&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro XSC 900MHz ===&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro XSC]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900 MHz&lt;br /&gt;
* Output Power 100 mW (+20 dBm)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* Data Rate: 9600 bps&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 24km (15 miles) line-of-sight &lt;br /&gt;
* Interface 20-pin mini connector (Xbee compatible pinout)&lt;br /&gt;
* RPSMA, integrated whip antenna or U.FL antenna connector (3 versions)&lt;br /&gt;
* price : $39 USD (on DigiKey)&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp]&lt;br /&gt;
==== Trials ====&lt;br /&gt;
Tested one today and it worked great. Going to try a multiUAV test with it soon&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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 &amp;quot;commit and reboot&amp;quot; type command after setting the baud rate. Could this be the case? --GR&lt;br /&gt;
&lt;br /&gt;
=== Digi 9XTend ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
[[Image:XTend_USB_RF_Modem.jpg|frame|left|9XTend USB Modem]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900Mhz and 2.4Ghz (2 versions)&lt;br /&gt;
* Output Power 1mW to 1W software selectable&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* RF Data Rate 9.6 or 115.2 Kbps&lt;br /&gt;
* Interface data rate up to 230.4 Kbps&lt;br /&gt;
* Power Draw (typical) 730 mA TX / 80 mA RX &lt;br /&gt;
* Supply Voltage 2.8 to 5.5v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 64km line-of-sight &lt;br /&gt;
* Dimensions 36 x 60 x 5mm&lt;br /&gt;
* Weight 18 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* RF connector RPSMA (Reverse-polarity SMA) or MMCX (2 versions)&lt;br /&gt;
* price : ~179 USD&lt;br /&gt;
|&lt;br /&gt;
[[Image:Xtend_module.jpg|frame|left|9XTend OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_9XTend_Pinout.gif|thumb|left|Maxstream 9XTend Pinout]]&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''9XTend 20-pin Header'''''||'''''Name'''''||'''''Tiny Serial-1 Header'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||1||GND||1 (GND)||Ground &lt;br /&gt;
|-&lt;br /&gt;
||2||VCC||2 (5V)||5V power (150mA - 730mA Supplied from servo bus or other 5V source)&lt;br /&gt;
|-&lt;br /&gt;
||5||RX||8 (TX)||3-5V TTL data input - connect to Tiny TX&lt;br /&gt;
|-&lt;br /&gt;
||6||TX||7 (RX)||5V TTL data output - connect to Tiny RX&lt;br /&gt;
|-&lt;br /&gt;
||7||Shutdown||2||This pin must be connected to the 5V bus for normal operation&lt;br /&gt;
|}&lt;br /&gt;
Notes:&amp;lt;br&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/oem-rf-module.php product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/datasheet_XTend_OEM_RF-Module.pdf datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/product-manual_XTend_OEM_RF-Module.pdf user manual]&lt;br /&gt;
&lt;br /&gt;
==== Configuration ====&lt;br /&gt;
&lt;br /&gt;
These modems need to be carefully configured based on your usage scenario to obtain the best possible range and link quality. In addition, it is always good to make sure the firmware is up to date.&lt;br /&gt;
&lt;br /&gt;
Some typical configurations that may work well, but can still depend your particular situation, are given below. For further details, be sure to consult the XTend users manual. Your application may need a different or modified configuration. The radiomodems do not need identical settings and can in fact be optimized with different settings. A good example is delays and retries: if each radio has the same number of retries and no delay, when a collision occurs each will continuously try to re-transmit, locking up the transmission for some time with no resolution or successful packet delivery. Instead, it is best to set the module whose data should have a lower latency to have no delay and a lower number of retries, while the other module has a delay set (RN &amp;gt; 0) and a greater number of retries. See acknowledged mode example below.&lt;br /&gt;
&lt;br /&gt;
* Acknowledged Polling Mode ('''Recommended'''):&lt;br /&gt;
** This causes one radio to be the base and the other(s) to be the remote(s). It eliminates collisions because remotes do not send data unless requested by the base. It can work in acknowledged mode (RR&amp;gt;0), basic reliable mode (MT&amp;gt;0) or in basic mode (no acknowledgement or multiple packets). It is recommended that the lower latency and/or higher data rate side be configured as the base (i.e. if you are sending lots of telemetry then the air module configured as the base is probably a good idea, but if you are using datalink joystick control, the ground side might be better as the base. It may require some experimentation).&lt;br /&gt;
* Acknowledged Point-to-(Multi)Point Mode:&lt;br /&gt;
** Each radio sends a packet and requests and acknowledgement that the packet was sent from the receiving side. The retries and delays must be set appropriately to ensure packet collisions are dealt with appropriately. It can also work without acknowledgements in basic reliable mode (MT&amp;gt;0) without any acknowledgements (RR=0, MT=0). Some experimentation may be required.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''Setting Name'''''||colspan=&amp;quot;2&amp;quot;|'''''Acknowledged Mode'''''||colspan=&amp;quot;2&amp;quot;|'''''Polling Mode (Acknowledged)'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
|| ||'''''Airside Module'''''||'''''Groundside Module'''''||'''''Base Module'''''||'''''Remote Module'''''||&lt;br /&gt;
|-&lt;br /&gt;
||BD||6||6||6||6||Adjust to match your configured autopilot and ground station baud rates (default for these is 57600bps)&lt;br /&gt;
|-&lt;br /&gt;
||DT||default||default||0x02||0x01||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MD||default||default||3 (0x03)||4 (0x04)||&lt;br /&gt;
|-&lt;br /&gt;
||MT||0||0||0||0||Use this to enable Basic Reliable transmission, link bandwidth requirement increases (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MY||default||default||0x01||0x02||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PB||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PD||default||default||default||default||Can be adjusted to increase polling request rate and DI buffer flush timeout (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PE||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PL||default||default||default||default||''Transmit power level should be reduced for lab testing!!''&lt;br /&gt;
|-&lt;br /&gt;
||RN||0 (0x00)||8 (0x08)||default||default||&lt;br /&gt;
|-&lt;br /&gt;
||RR||6 (0x06)||12 (0x0C)||6 (0x06)||12 (0x0C)||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Note:''' All settings are assumed to be default except those listed. Those listed are in decimal unless hex 0x prefix included. Depending on your firmware version, slight modifications may be necessary.&lt;br /&gt;
&lt;br /&gt;
Here is some additional information and alternative instructions to configure the polling mode from the Digi site: [http://www.digi.com/support/kbase/kbaseresultdetl?id=2178 Polling Mode for the 9XTend Radio Modem]&lt;br /&gt;
&lt;br /&gt;
== SiLabs Si1000 SoC based modems ==&lt;br /&gt;
&lt;br /&gt;
The Si1000 radio System on Chip (SOC) produced by  SiLabs is found in a number of radio modules, for example the cheap and widely used HopeRf module. There is [https://github.com/tridge/SiK open source firmware] for these radios which makes them suitable for use in MAVs. &lt;br /&gt;
&lt;br /&gt;
Note that (unlike some XBee modules) the SiK firmware does not support mesh topologies, it is strictly a point-to-point link. If you are working with swarming vehicles they may not be the best choice.&lt;br /&gt;
&lt;br /&gt;
Online documentation for the Sik firmware shows how to configure it for various jurisdictions. There may not be any SiK hardware that support European spectrum licences, please update this wiki if you know of any.&lt;br /&gt;
&lt;br /&gt;
Note: When using a SiK firmware radio with paparazzi, you should set &amp;quot;ATS6=0&amp;quot; (MavLink packing off) and configure paparazzi for transparent serial mode.&lt;br /&gt;
&lt;br /&gt;
[http://www.rfdesign.com.au/index.php/rfd900 This module] is well proven and supports antenna diversity. A combination of 6dbi Yagi plus a dipole on the ground station, with a pair of  orthogonality oriented dioples in the airframe, has been extensively tested and proven reliable at &amp;gt;8km range (theoretical range of ~40km).&lt;br /&gt;
&lt;br /&gt;
Alternatively, for shorter range a pair of cheap generic HopeRF-based modems [http://rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=815 such as these]&lt;br /&gt;
&lt;br /&gt;
The RFD900 can be paired with cheap generic (single front-end) modules, if for example you use a small short range airframe with a ground station that's also used for long range operations.&lt;br /&gt;
&lt;br /&gt;
== Aerocomm ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
How to use this modem on ground station side? [http://paparazzi.enac.fr/wiki/index.php/User:SilaS#SDK-AC4868-250_ground_modem_part]&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;main&amp;quot; link.ml file of the ground sttaion and will be merged into it in the future.. or you can do it as well.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== AC4868-250 ===&lt;br /&gt;
* Frequency Band 868MHz (For Europe). 868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
* Output Power (w/ 2dBi antenna) 250 mW &lt;br /&gt;
* Sensitivity (@ full RF data rate) -103 dB &lt;br /&gt;
* RF Data Rate Up to 28.8 Kbps &lt;br /&gt;
* INterface Data Rate Up to 57.6 Kbps &lt;br /&gt;
* Power Draw (typical) 240 mA TX / 36 mA RX &lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5V or 3.3v only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 15 kilometers line-of-sight &lt;br /&gt;
* Dimensions 49 x 42 x 5mm &lt;br /&gt;
* Weight &amp;lt; 21 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector &lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ConnexLink_USB_RF_Modem.jpg|thumb|Aerocomm USB Stand-alone Modem]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-200 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-200mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -110dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 68 mA&lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5.5V&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 6.4 kilometers line-of-sight &lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector or internal&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ac4868_transceiver.jpg|thumb|left|AC4868 OEM Modem]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-1000 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-1000mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -99dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 650 mA&lt;br /&gt;
* Supply Voltage 3.3V only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 32 kilometers with high-gain antenna&lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Aerocomm_AC4868_pinout.jpg|thumb|left|Aerocomm AC4868 modem pinout]]&lt;br /&gt;
[[Image:Aerocomm_AC4490-200_wired.jpg|thumb|left|Aerocomm AC4490 wiring example]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the Aerocomm AC4868 to the Tiny&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''AC4868 20-pin Header'''''||'''''Name'''''||'''''Color'''''||'''''Tiny v1.1 Serial-1'''''||'''''Tiny v2.11 Serial'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||2||Tx||green||7||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||3||Rx||blue||8||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||GND||black||1||1|| -&lt;br /&gt;
|-&lt;br /&gt;
||10+11||VCC||red||2||3||+3.3v ''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||17||C/D||white||3||?||Low = Command High = Data&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the AEROCOMM module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : AC4790-1000 needs pins 10 and 11 jumped to work properly''&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4790_mesh-ready_transceiver.htm AC4790 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4790_HI.pdf AC4790 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4790.pdf AC4790 Manual]&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4868_868mhz_rf_transceiver.htm AC4848 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4868_HI.pdf AC4868 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4868.pdf AC4868 user manual]&lt;br /&gt;
&lt;br /&gt;
== Laird (ex Aerocomm) ==&lt;br /&gt;
&lt;br /&gt;
=== Laird LT2510 ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Lt2510_prm123.jpg|thumb|LT2510 Modem]]&lt;br /&gt;
&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 50mW (European version)&lt;br /&gt;
* Sensitivity  -98/-94 dBm &lt;br /&gt;
* RF Data Rate 280/500 kbps&lt;br /&gt;
* Interface data rate Up to 460800 kbps&lt;br /&gt;
* Power Draw (typical) 85mA TX / 10mA RX (European version)&lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 2400m line-of-sight (European version)&lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector (solder pad or XBee compatible)&lt;br /&gt;
* Chip antenna, or a U.FL antenna connector&lt;br /&gt;
* Price: Approximately $31&lt;br /&gt;
&lt;br /&gt;
The LT2510 uses frequency hopping which needs a client/server model. That means that one modem (most appropriately the ground station modem) needs to be set to server mode. It will transmit a beacon message and have all client modems synchronize to that in a time and frequency hopping scheme manner. For that all modems need to have the same channel (in fact the hopping scheme) and system-id. Clients can be set to auto-channel and auto-system-id to follow any/the first visible server.&lt;br /&gt;
&lt;br /&gt;
All acknowledged messages transmitted need to be adressed to the non-changeable MAC address of the destination modem. There are is a way to automatically set destination adresses but this procedure does have drawbacks (see below).&lt;br /&gt;
&lt;br /&gt;
Make sure you short circuit &amp;quot;D1&amp;quot; if you use the Sparkfun WRL-09132 &amp;quot;XBee Explorer Regulated&amp;quot; adapter. The Laird does not have a pull-up resistor on DIN that Sparkfun assumes.&lt;br /&gt;
&lt;br /&gt;
==== Basic setup ====&lt;br /&gt;
&lt;br /&gt;
You can download a Windows configuration utility from [http://www.lairdtech.com/Products/Wireless-M2M-and-Telematics-Solutions/Proprietary-Radio-Modules/ here], click &amp;quot;Product Information&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
 Set client to client mode (default).&lt;br /&gt;
 Set server to server mode.&lt;br /&gt;
&lt;br /&gt;
 Set speed on both modems to 57600 baud, the Paparazzi standard.&lt;br /&gt;
&lt;br /&gt;
 Choose RF profile with low speed (280kbps) for long range (default).&lt;br /&gt;
&lt;br /&gt;
===== Transparent mode =====&lt;br /&gt;
&lt;br /&gt;
The transparent mode is different from the XBee modems transparent mode. It will only allow two modems to communicate with each other.&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with hard coded address ======&lt;br /&gt;
&lt;br /&gt;
In this mode the destination MAC address is permanently set in the EEPROMs of the modems. Only these two modems can communicate with each other. The advantage of this mode is that other modems can not confuse the communication. You have to read out both modems MAC adresses as they are not printed on the case.&lt;br /&gt;
&lt;br /&gt;
 Set server MAC address in client&lt;br /&gt;
 Set client MAC address in server&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with auto-address ======&lt;br /&gt;
&lt;br /&gt;
The server will start emitting beacon messages and the client locks to these, starting to send messages to the servers MAC address. The server will then respond to that clients data messages. In this mode only one server can talk to one client. Any appearance of another server or client modem will confuse/disrupt the communication.&lt;br /&gt;
&lt;br /&gt;
 Set server to auto-destination.&lt;br /&gt;
 Set client to auto-destination and auto-destination-beacons-only.&lt;br /&gt;
&lt;br /&gt;
===== API mode =====&lt;br /&gt;
&lt;br /&gt;
We need at least a simple form of address resolution as the modems own (MAC) address can not be changed. This makes the ground station link and on-board software a little more complicated than the XBee API mode.&lt;br /&gt;
&lt;br /&gt;
 tbd&lt;br /&gt;
&lt;br /&gt;
== Radiotronix ==&lt;br /&gt;
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-&amp;gt;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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== WI232EUR ===&lt;br /&gt;
* Frequency Band: 868 MHz (for Europe)&lt;br /&gt;
* Output Power: 32 mW &lt;br /&gt;
* RF Data Rate: Up to 76.8 kbps &lt;br /&gt;
* Interface Data Rate: up to 115.2 kbps &lt;br /&gt;
* Power Draw (typical): 65 mA TX / 20 mA RX &lt;br /&gt;
* Supply Voltage: 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment): 500 meters line-of-sight &lt;br /&gt;
* Dimensions: 24 x 21 x 4mm &lt;br /&gt;
* Weight: ~2 grams&lt;br /&gt;
* Interface: solder connector  &lt;br /&gt;
* Antenna: solder connector &lt;br /&gt;
* Price: ~25$&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_wiring.jpg|thumb|WI232EUR Modem (picture shows connection to Tiny 1.1)]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the WI232EUR to the Tiny v1.1&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''WI232 pins'''''||'''''Name'''''||'''''Tiny Serial-1'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||6||TxD||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||RxD||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||15-18||GND||1|| - &lt;br /&gt;
|-&lt;br /&gt;
||19||VCC||2||+3.3v&lt;br /&gt;
|-&lt;br /&gt;
||4||/CMD||-||''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||7||CTS||-||''(Note 3)''&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the Radiotronix module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : connect to RTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
''Note 3 : connect to CTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_bopla.jpg|thumb|WI232EUR Modem in BOPLA case]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/eur_um.pdf WI232EUR data sheet]&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/rk-eur_um.pdf WI232EUR user's manual]&lt;br /&gt;
* [http://www.radiotronix.com/downloads/software/EUR/setup.exe Evaluation software]&lt;br /&gt;
&lt;br /&gt;
== Bluetooth ==&lt;br /&gt;
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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== &amp;quot;Sparkfun&amp;quot; Roving Networks (WRL-08497) ===&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 32 mW &lt;br /&gt;
* RF Data Rate up to ~300 kbps in SPP&lt;br /&gt;
* Interface Data Rate up to 921 kbps &lt;br /&gt;
* Power Draw (typical) 50 mA TX / 40 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) 100 meters line-of-sight &lt;br /&gt;
* Dimensions 26 x 13 x 2mm &lt;br /&gt;
* Weight ~1.5 grams&lt;br /&gt;
* Interface solder connector  &lt;br /&gt;
* price : ~45$&lt;br /&gt;
|&lt;br /&gt;
[[Image:roving_nw_wiring.jpg|thumb|Roving Networks modem wiring]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
To connect to it, get the MAC address of the bluetooth modem&lt;br /&gt;
&lt;br /&gt;
 me@mybox:~$ hcitool scan&lt;br /&gt;
 Scanning ...&lt;br /&gt;
        00:06:66:00:53:AD       FireFly-53AD&lt;br /&gt;
&lt;br /&gt;
either make a virtual connection to a Bluetooth serial port each time you connect&lt;br /&gt;
&lt;br /&gt;
 sudo rfcomm bind 0 00:06:66:00:53:AD&lt;br /&gt;
&lt;br /&gt;
or configure it once in /etc/bluetooth/rfcomm.conf&lt;br /&gt;
&lt;br /&gt;
 rfcomm0 {&lt;br /&gt;
   bind yes;&lt;br /&gt;
   device 00:06:66:00:53:AD;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Coronis WaveCard ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''Suport for these modems has been removed from the airborne code on Dec 10th, 2007.'''&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 400MHz, 868Mhz and 915MHz (3 versions)&lt;br /&gt;
* Output Power 25mW and 500mW (2 versions)&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* Data Rate 100 Kbps&lt;br /&gt;
* Power Draw (typical) 45mA (25mW), 450mA (500mW) TX / 15 mA RX &lt;br /&gt;
* Supply Voltage ...&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1km (25mW) , 5km (500mW) line-of-sight &lt;br /&gt;
* Dimensions 30 x 28 x 7mm (25mW), 37 x 30 x 7mm (500mW)&lt;br /&gt;
* 50 ohm RF port for antenna connection&lt;br /&gt;
|&lt;br /&gt;
[[Image:wavecard.jpg|Coronis Wavecard]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.coronis-systems.com/produit.php?lang=EN&amp;amp;id=WCA  www.coronis-systems.com]&lt;br /&gt;
* [[Media:CS-COM-SPRD-WAVECARD-E03B.pdf|Wavecard datasheet]]&lt;br /&gt;
&lt;br /&gt;
== Telemetry via Video Transmitter==&lt;br /&gt;
&lt;br /&gt;
[[Image:video_tx_small.jpg|thumb|2.4GHz Video Transmitter]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Antennas ==&lt;br /&gt;
&lt;br /&gt;
Here are some examples of lightweight and efficient 868MHz antennas developped by the RF laboratory at ENAC.&lt;br /&gt;
[[Image:868mhz_twinstar_antenna_1.jpg|thumb|left|868MHz copper foil antenna attached to the aircraft tail]] &lt;br /&gt;
[[Image:868mhz_twinstar_antenna_2.jpg|thumb|left|868MHz copper foil antenna bottom view]] &lt;br /&gt;
[[Image:868mhz_ground_antenna.jpg|thumb|left|868MHz ground antenna]] &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This wiki page might give some ideas about antennas: http://en.wikipedia.org/wiki/Dipole_antenna&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14320</id>
		<title>Modems</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Modems&amp;diff=14320"/>
		<updated>2013-02-04T01:03:41Z</updated>

		<summary type="html">&lt;p&gt;Rufus: added section for SiLabs modems with open source firmware&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The Paparazzi autopilots generally feature a 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.&lt;br /&gt;
&lt;br /&gt;
== Digi XBee modules ==&lt;br /&gt;
&lt;br /&gt;
Digi (formerly Maxstream) offers an increasing variety of Zigbee protocol modems well suited for Paparazzi in 2.4 GHz, 900MHz and 868Mhz frequencies.  The &amp;quot;Pro&amp;quot; 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 &amp;quot;API mode&amp;quot; with hardware addressing, managed networking, and RSSI (signal strength) data with the Paparazzi &amp;quot;Xbee&amp;quot; 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.&lt;br /&gt;
&lt;br /&gt;
* XBee (PRO) ZB (the current series)&lt;br /&gt;
* XBee (PRO) ZNet 2.5 (formerly Series 2) (only legacy -&amp;gt; use XBee-PRO ZB)&lt;br /&gt;
The XBee &amp;amp; XBee-PRO ZB share hardware (ember stack) with XBee &amp;amp; XBee-PRO ZNet 2.5. As a result, modules can be &amp;quot;converted&amp;quot; from one platform to another by loading different firmware onto a given module.&lt;br /&gt;
&lt;br /&gt;
These two also share the same hardware and can be converted from one to another by flashing a different firmware:&lt;br /&gt;
* XBee-PRO 802.15.4 (formerly Series 1)&lt;br /&gt;
* XBee-PRO DigiMesh 2.4&lt;br /&gt;
&lt;br /&gt;
'''Note: Modules based on Freescale chipset (formerly Series 1) are not compatible with Ember chipset based modules (Series 2).'''&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Module Comparison ===&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''Module'''||'''Point-to-Multipoint'''||'''ZigBee/Mesh'''||'''Chipset'''|||'''Software stack'''||'''Frequency'''||'''TX Power normal/PRO'''||'''Notes'''&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZB'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet PRO 3.1 (ZigBee 2007)&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee ZNet 2.5'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Ember&lt;br /&gt;
|EmberZNet 2.5 ZigBee&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|2mW/50mW&lt;br /&gt;
|(only legacy -&amp;gt; use XBee-PRO ZB) coordinator needed&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee DigiMesh 2.4'''&lt;br /&gt;
|&lt;br /&gt;
|yes&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|all nodes equal (no special coordinators/routers/end-devices)&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee 802.15.4'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|Freescale&lt;br /&gt;
|&lt;br /&gt;
|2.4 GHz&lt;br /&gt;
|&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|'''XBee-PRO 868'''&lt;br /&gt;
|yes&lt;br /&gt;
|&lt;br /&gt;
|?&lt;br /&gt;
|&lt;br /&gt;
|868 MHz&lt;br /&gt;
|500mW&lt;br /&gt;
|Only High Power Frequency allowed in the UK. 2.4GHz limited to 10mW&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==== Comparison Conclusion ====&lt;br /&gt;
&lt;br /&gt;
(Copied from DIGI manual)&lt;br /&gt;
&lt;br /&gt;
''If the application strictly needs to communicate in a point-to-point or a point-to-multipoint &lt;br /&gt;
fashion, 802.15.4 will be able handle all the communications between your devices and will &lt;br /&gt;
be simpler to implement than trying to use a module with ZigBee firmware to accomplish the &lt;br /&gt;
same goal. ZigBee is necessary if you need to use repeating or the mesh networking &lt;br /&gt;
functionality.'' &lt;br /&gt;
&lt;br /&gt;
-Interpretation for paparazzi: if inter-aircraft communication is required one should go for the zigbee ZB series 2 modules. &lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_Xbee_pinout.jpg|left|thumb|Maxstream XBee pinout]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||''Xbee 20-pin Header''||''Name''||''Notes''||''Suggested Color''||&lt;br /&gt;
|-&lt;br /&gt;
|1&lt;br /&gt;
| +3.3v&lt;br /&gt;
| Power&lt;br /&gt;
|Red&lt;br /&gt;
|-&lt;br /&gt;
|2&lt;br /&gt;
|DOUT&lt;br /&gt;
|Tx output - connect to Autopilot Rx&lt;br /&gt;
|Green&lt;br /&gt;
|-&lt;br /&gt;
|3&lt;br /&gt;
|DIN&lt;br /&gt;
|Rx input - connect to Autopilot Tx&lt;br /&gt;
|Blue&lt;br /&gt;
|-&lt;br /&gt;
|10&lt;br /&gt;
|GND&lt;br /&gt;
| Ground&lt;br /&gt;
|Black&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The image view is from above, top, thus NOT at the side where the connector pins come out&lt;br /&gt;
&lt;br /&gt;
Note : DTR and RTS need to be wired for upgrading firmware&lt;br /&gt;
&lt;br /&gt;
=== GCS Adaptation ===&lt;br /&gt;
&lt;br /&gt;
There are several vendors of hardware to connect the ground XBee radio modem to the GCS computer.&lt;br /&gt;
&lt;br /&gt;
====Adafruit====&lt;br /&gt;
&lt;br /&gt;
[[Image:xbeeadapter_LRG.jpg|thumb|left|Adafruit XBee adapter board]][[Image:xbeeadapterftdi_LRG.jpg|thumb|Adafruit XBee adapter with FTDI cable]]&lt;br /&gt;
[http://www.adafruit.com/index.php?main_page=product_info&amp;amp;cPath=29&amp;amp;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.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Droids====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Simple_Board.jpg|thumb|left|XBee Simple Board]]&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_USB_Board.jpg|thumb|left|XBee USB Board]]&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?143-990.001-XBee-Simple-Board XBee Simple Board]&lt;br /&gt;
&lt;br /&gt;
Simpler, lighter, smaller footprint, bit more expensive, comes assembled and tested. --GR&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[http://www.droids.it/cmsvb4/content.php?152-990.002-XBee-USB-Board XBee USB Board]&lt;br /&gt;
&lt;br /&gt;
For direct connection to USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====PPZUAV====&lt;br /&gt;
&lt;br /&gt;
[[Image:FTDI_Utility_Board.jpg|thumb|left|FTDI Utility Board 1.0‎]]&lt;br /&gt;
&lt;br /&gt;
[https://mini.ppzuav.com/osc/product_info.php?cPath=13&amp;amp;products_id=111 ppzuav.com]&lt;br /&gt;
&lt;br /&gt;
FTDI Utility Board 1.0 (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====Sparkfun====&lt;br /&gt;
&lt;br /&gt;
[[Image:XBee_Explorer_USB.jpg|thumb|left|XBee Explorer USB]]&lt;br /&gt;
&lt;br /&gt;
[http://www.sparkfun.com/products/8687 sparkfun.com]&lt;br /&gt;
&lt;br /&gt;
XBee Explorer USB (no FTDI cable required)&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro DigiMesh / 802.15.4 (&amp;quot;Series 1&amp;quot;) ===&lt;br /&gt;
*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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:Xbee_Pro_USB_RF_Modem.jpg|thumb|left|XBee Pro USB Stand-alone Modem (XBP24-PKC-001-UA)]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 2.4Ghz&lt;br /&gt;
* Output Power 100mW (Xbee Pro)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* RF Data Rate Up to 250 Kbps&lt;br /&gt;
* Interface data rate Up to 115.2 Kbps&lt;br /&gt;
* Power Draw (typical) 214 mA TX / 55 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1500m line-of-sight &lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Chip antenna, ¼ monopole integrated whip antenna or a U.FL antenna connector (3 versions)&lt;br /&gt;
* Price: Approximately $32&lt;br /&gt;
|&lt;br /&gt;
[[Image:XBee_pro.jpg|thumb|left|XBee Pro OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
Mouser: [http://au.mouser.com/Search/ProductDetail.aspx?qs=sGAEpiMZZMtJacPDJcUJYzVn8vIv7g2fIpf5DCzJqko%3d 888-XBP24-PKC-001-UA]&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/xbee-pro-oem-rf-module-zigbee.php  product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/datasheet_XBee_OEM_RF-Modules.pdf  datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xbee/product-manual_XBee_OEM_RF-Modules.pdf  user manual]&lt;br /&gt;
* To program your Xbee you need X-CTU you can download it [http://www.digi.com/support/productdetl.jsp?pid=3352&amp;amp;osvid=57&amp;amp;tp=5&amp;amp;s=316 here]. (only windows)&lt;br /&gt;
* explanation on X-CTU [http://www.ladyada.net/make/xbee/configure.html here].&lt;br /&gt;
* [http://ftp1.digi.com/support/firmware/update/xbee/ Drivers for XB24 and XBP24 modules]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro ZB / ZNet 2.5 (&amp;quot;Series 2&amp;quot;) ===&lt;br /&gt;
&lt;br /&gt;
The low-power XBee ZB and extended-range XBee-PRO ZB use the ZigBee PRO Feature Set for advanced mesh networking.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:XBee_Pro_2SB.jpg|thumb|left|Digi XBee Pro ZB]]&lt;br /&gt;
|&lt;br /&gt;
* Low-cost, low-power mesh networking&lt;br /&gt;
* Interoperability with ZigBee PRO Feature Set devices from other vendors*&lt;br /&gt;
* Support for larger, more dense mesh networks&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* Frequency agility&lt;br /&gt;
* Over-the-air firmware updates (change firmware remotely)&lt;br /&gt;
* ISM 2.4 GHz operating frequency&lt;br /&gt;
* XBee: 2 mW (+3 dBm) power output (up to 400 ft RF LOS range)&lt;br /&gt;
* XBee-PRO: 50 mW (+17 dBm) power output (up to 1 mile RF LOS range)&lt;br /&gt;
* RPSMA connector, U.FL connector, Chip antenna, or Wired Whip antenna&lt;br /&gt;
* price : ~34 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
These are available from Mouser:&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=888-XBP24-Z7WIT-004 888-XBP24-Z7WIT-004] XBee-PRO ZB with whip antenna&amp;lt;br&amp;gt;&lt;br /&gt;
[http://au.mouser.com/Search/Refine.aspx?Keyword=XBP24-Z7SIT-004 888-XBP24-Z7SIT-004] XBee-PRO ZB with RPSMA&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp http://www.digi.com/products/wireless/zigbee-mesh/xbee-zb-module.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 868 ===&lt;br /&gt;
&lt;br /&gt;
'''WARNING - THESE MODEMS HAVE A 10% DUTY CYCLE, AND CURRENTLY HAVE SEVERE ISSUES WITH PAPARAZZI'''&lt;br /&gt;
&lt;br /&gt;
868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro 868]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G3 band for Europe&lt;br /&gt;
* Software selectable Transmit Power&lt;br /&gt;
* 40 km RF LOS w/ dipole antennas&lt;br /&gt;
* 80 km RF LOS w/ high gain antennas (TX Power reduced)&lt;br /&gt;
* Simple to use peer-to-peer/point-to-mulitpoint topology&lt;br /&gt;
* 128-bit AES encryption&lt;br /&gt;
* 500 mW EIRP&lt;br /&gt;
* 24 kbps RF data rate&lt;br /&gt;
* price : ~70 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See [[XBee_configuration#XBee_Pro_868_MHZ|XBee Configuration]] for setup.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-868.jsp]&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee 868LP ===&lt;br /&gt;
&lt;br /&gt;
XBee 868LP modules are a low-power 868 MHz RF module for use in Europe. The range is shorter than it's brother the XBee PRO-868, but it can use the 868 G4 band with hopping which does not have restrictions on it's duty cycle. This is a big advantage if one want to have a good stream of telemetry data&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:868lp.jpg|thumb|left|XBee 868LP]]&lt;br /&gt;
|&lt;br /&gt;
* 868 MHz short range device (SRD) G4 band for Europe&lt;br /&gt;
* 4 km RF LOS w/ u.fl antennas&lt;br /&gt;
* 5 mW EIRP&lt;br /&gt;
* 80 kbps RF data rate&lt;br /&gt;
* price : ~23 USD&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview http://www.digi.com/products/wireless-wired-embedded-solutions/zigbee-rf-modules/zigbee-mesh-module/xbee-868lp#overview]&lt;br /&gt;
&lt;br /&gt;
==== Trial ====&lt;br /&gt;
&lt;br /&gt;
With a quickly crafted and not optimal positioned antenna on the airframe we managed to get the advertised 4000 meter range. Data throughput was not high and the Iridium Telemetry XML configuration document was therefore used. All in all, cheap, easy to setup, pin compatible with regular modules and quite a range and usable in Europe without hassle.&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro 900 (XBEE09P) ===&lt;br /&gt;
&lt;br /&gt;
XBee Pro 900 modules are long range embedded RF modules for US applications. Purpose-built for exceptional RF performance, XBee-Pro 900 modules are ideal for applications with challenging RF environments, such as urban deployments, or where devices are several kilometers apart.&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [ftp://ftp1.digi.com/support/documentation/90000903_a.pdf]&lt;br /&gt;
&lt;br /&gt;
I've been using a pair of these for about 6 months now and they works great. To set it up I just used a serial terminal app like CoolTerm or screen and made sure I could send messages between the two of them. - cwozny&lt;br /&gt;
&lt;br /&gt;
=== Digi XBee Pro XSC 900MHz ===&lt;br /&gt;
&lt;br /&gt;
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!&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:xbeeproxsc-rpsma.jpg|thumb|left|Maxstream XBee Pro XSC]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900 MHz&lt;br /&gt;
* Output Power 100 mW (+20 dBm)&lt;br /&gt;
* Sensitivity  -100 dBm &lt;br /&gt;
* Data Rate: 9600 bps&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 24km (15 miles) line-of-sight &lt;br /&gt;
* Interface 20-pin mini connector (Xbee compatible pinout)&lt;br /&gt;
* RPSMA, integrated whip antenna or U.FL antenna connector (3 versions)&lt;br /&gt;
* price : $39 USD (on DigiKey)&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
* [http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp http://www.digi.com/products/wireless/point-multipoint/xbee-pro-xsc.jsp]&lt;br /&gt;
==== Trials ====&lt;br /&gt;
Tested one today and it worked great. Going to try a multiUAV test with it soon&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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.&lt;br /&gt;
--Danstah&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
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 &amp;quot;commit and reboot&amp;quot; type command after setting the baud rate. Could this be the case? --GR&lt;br /&gt;
&lt;br /&gt;
=== Digi 9XTend ===&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
[[Image:XTend_USB_RF_Modem.jpg|frame|left|9XTend USB Modem]]&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 900Mhz and 2.4Ghz (2 versions)&lt;br /&gt;
* Output Power 1mW to 1W software selectable&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* RF Data Rate 9.6 or 115.2 Kbps&lt;br /&gt;
* Interface data rate up to 230.4 Kbps&lt;br /&gt;
* Power Draw (typical) 730 mA TX / 80 mA RX &lt;br /&gt;
* Supply Voltage 2.8 to 5.5v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 64km line-of-sight &lt;br /&gt;
* Dimensions 36 x 60 x 5mm&lt;br /&gt;
* Weight 18 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* RF connector RPSMA (Reverse-polarity SMA) or MMCX (2 versions)&lt;br /&gt;
* price : ~179 USD&lt;br /&gt;
|&lt;br /&gt;
[[Image:Xtend_module.jpg|frame|left|9XTend OEM Modem]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==== Pinout ====&lt;br /&gt;
&lt;br /&gt;
[[Image:Maxstream_9XTend_Pinout.gif|thumb|left|Maxstream 9XTend Pinout]]&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''9XTend 20-pin Header'''''||'''''Name'''''||'''''Tiny Serial-1 Header'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||1||GND||1 (GND)||Ground &lt;br /&gt;
|-&lt;br /&gt;
||2||VCC||2 (5V)||5V power (150mA - 730mA Supplied from servo bus or other 5V source)&lt;br /&gt;
|-&lt;br /&gt;
||5||RX||8 (TX)||3-5V TTL data input - connect to Tiny TX&lt;br /&gt;
|-&lt;br /&gt;
||6||TX||7 (RX)||5V TTL data output - connect to Tiny RX&lt;br /&gt;
|-&lt;br /&gt;
||7||Shutdown||2||This pin must be connected to the 5V bus for normal operation&lt;br /&gt;
|}&lt;br /&gt;
Notes:&amp;lt;br&amp;gt;&lt;br /&gt;
* 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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Documentation ====&lt;br /&gt;
&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/oem-rf-module.php product page]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/datasheet_XTend_OEM_RF-Module.pdf datasheet]&lt;br /&gt;
* [http://www.maxstream.net/products/xtend/product-manual_XTend_OEM_RF-Module.pdf user manual]&lt;br /&gt;
&lt;br /&gt;
==== Configuration ====&lt;br /&gt;
&lt;br /&gt;
These modems need to be carefully configured based on your usage scenario to obtain the best possible range and link quality. In addition, it is always good to make sure the firmware is up to date.&lt;br /&gt;
&lt;br /&gt;
Some typical configurations that may work well, but can still depend your particular situation, are given below. For further details, be sure to consult the XTend users manual. Your application may need a different or modified configuration. The radiomodems do not need identical settings and can in fact be optimized with different settings. A good example is delays and retries: if each radio has the same number of retries and no delay, when a collision occurs each will continuously try to re-transmit, locking up the transmission for some time with no resolution or successful packet delivery. Instead, it is best to set the module whose data should have a lower latency to have no delay and a lower number of retries, while the other module has a delay set (RN &amp;gt; 0) and a greater number of retries. See acknowledged mode example below.&lt;br /&gt;
&lt;br /&gt;
* Acknowledged Polling Mode ('''Recommended'''):&lt;br /&gt;
** This causes one radio to be the base and the other(s) to be the remote(s). It eliminates collisions because remotes do not send data unless requested by the base. It can work in acknowledged mode (RR&amp;gt;0), basic reliable mode (MT&amp;gt;0) or in basic mode (no acknowledgement or multiple packets). It is recommended that the lower latency and/or higher data rate side be configured as the base (i.e. if you are sending lots of telemetry then the air module configured as the base is probably a good idea, but if you are using datalink joystick control, the ground side might be better as the base. It may require some experimentation).&lt;br /&gt;
* Acknowledged Point-to-(Multi)Point Mode:&lt;br /&gt;
** Each radio sends a packet and requests and acknowledgement that the packet was sent from the receiving side. The retries and delays must be set appropriately to ensure packet collisions are dealt with appropriately. It can also work without acknowledgements in basic reliable mode (MT&amp;gt;0) without any acknowledgements (RR=0, MT=0). Some experimentation may be required.&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''Setting Name'''''||colspan=&amp;quot;2&amp;quot;|'''''Acknowledged Mode'''''||colspan=&amp;quot;2&amp;quot;|'''''Polling Mode (Acknowledged)'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
|| ||'''''Airside Module'''''||'''''Groundside Module'''''||'''''Base Module'''''||'''''Remote Module'''''||&lt;br /&gt;
|-&lt;br /&gt;
||BD||6||6||6||6||Adjust to match your configured autopilot and ground station baud rates (default for these is 57600bps)&lt;br /&gt;
|-&lt;br /&gt;
||DT||default||default||0x02||0x01||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MD||default||default||3 (0x03)||4 (0x04)||&lt;br /&gt;
|-&lt;br /&gt;
||MT||0||0||0||0||Use this to enable Basic Reliable transmission, link bandwidth requirement increases (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||MY||default||default||0x01||0x02||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PB||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PD||default||default||default||default||Can be adjusted to increase polling request rate and DI buffer flush timeout (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PE||default||default||0x02||default||Can be adjusted if consistency maintained across addressing functionalities (see manual)&lt;br /&gt;
|-&lt;br /&gt;
||PL||default||default||default||default||''Transmit power level should be reduced for lab testing!!''&lt;br /&gt;
|-&lt;br /&gt;
||RN||0 (0x00)||8 (0x08)||default||default||&lt;br /&gt;
|-&lt;br /&gt;
||RR||6 (0x06)||12 (0x0C)||6 (0x06)||12 (0x0C)||&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Note:''' All settings are assumed to be default except those listed. Those listed are in decimal unless hex 0x prefix included. Depending on your firmware version, slight modifications may be necessary.&lt;br /&gt;
&lt;br /&gt;
Here is some additional information and alternative instructions to configure the polling mode from the Digi site: [http://www.digi.com/support/kbase/kbaseresultdetl?id=2178 Polling Mode for the 9XTend Radio Modem]&lt;br /&gt;
&lt;br /&gt;
== SiLabs Si1000 SoC based modems ==&lt;br /&gt;
&lt;br /&gt;
The Si1000 radio System on Chip (SOC) produced by  SiLabs is found in a number of radio modules, for example the cheap and widely used HopeRf module. There is [https://github.com/tridge/SiK open source firmware] for these radios which makes them suitable for use in MAVs. &lt;br /&gt;
&lt;br /&gt;
Note that (unlike some XBee modules) the SiK firmware does not support mesh topologies, it is strictly a point-to-point link. If you are working with swarming vehicles they may not be the best choice.&lt;br /&gt;
&lt;br /&gt;
Online documentation for the Sik firmware shows how to configure it for various jurisdictions. There may not be any SiK hardware that support European spectrum licences, please update this wiki if you know of any.&lt;br /&gt;
&lt;br /&gt;
Note: When using a SiK firmware radio with paparazzi, you should set &amp;quot;ATS6=0&amp;quot; (MavLink packing off) and configure paparazzi for transparent serial mode.&lt;br /&gt;
&lt;br /&gt;
=== Availability ===&lt;br /&gt;
&lt;br /&gt;
[http://www.rfdesign.com.au/index.php/rfd900 This module] is well proven and supports antenna diversity. A combination of 6dbi Yagi plus a dipole on the ground station, with a pair of  orthogonality oriented dioples in the airframe, has been extensively tested and proven reliable at &amp;gt;8km range.&lt;br /&gt;
&lt;br /&gt;
Alternatively, for shorter range a pair of cheap generic HopeRF-based modems [http://rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=815 such as these]&lt;br /&gt;
&lt;br /&gt;
The RFD900 can be paired with cheap generic (single front-end) modules, if for example you use a small short range airframe with a ground station that's also used for long range operations.&lt;br /&gt;
&lt;br /&gt;
== Aerocomm ==&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
How to use this modem on ground station side? [http://paparazzi.enac.fr/wiki/index.php/User:SilaS#SDK-AC4868-250_ground_modem_part]&lt;br /&gt;
&lt;br /&gt;
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 &amp;quot;main&amp;quot; link.ml file of the ground sttaion and will be merged into it in the future.. or you can do it as well.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== AC4868-250 ===&lt;br /&gt;
* Frequency Band 868MHz (For Europe). 868MHz is a limited band. Please read the [[868MHz Issues]]&lt;br /&gt;
* Output Power (w/ 2dBi antenna) 250 mW &lt;br /&gt;
* Sensitivity (@ full RF data rate) -103 dB &lt;br /&gt;
* RF Data Rate Up to 28.8 Kbps &lt;br /&gt;
* INterface Data Rate Up to 57.6 Kbps &lt;br /&gt;
* Power Draw (typical) 240 mA TX / 36 mA RX &lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5V or 3.3v only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 15 kilometers line-of-sight &lt;br /&gt;
* Dimensions 49 x 42 x 5mm &lt;br /&gt;
* Weight &amp;lt; 21 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector &lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ConnexLink_USB_RF_Modem.jpg|thumb|Aerocomm USB Stand-alone Modem]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-200 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-200mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -110dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 68 mA&lt;br /&gt;
* Supply Voltage 3.3v &amp;amp; 5.5V&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 6.4 kilometers line-of-sight &lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector or internal&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|&lt;br /&gt;
[[Image:ac4868_transceiver.jpg|thumb|left|AC4868 OEM Modem]]&lt;br /&gt;
|&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== AC4790-1000 ===&lt;br /&gt;
* Frequency 902-928MHz (North America, Australia, etc).&lt;br /&gt;
* Output Power 5-1000mW&lt;br /&gt;
* Sensitivity (@ full RF data rate) -99dB&lt;br /&gt;
* RF Data Rate up to 76.8 Kbps&lt;br /&gt;
* INterface Data Rate Up to Up to 115.2 Kbps &lt;br /&gt;
* Power Draw (typical) 650 mA&lt;br /&gt;
* Supply Voltage 3.3V only&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 32 kilometers with high-gain antenna&lt;br /&gt;
* Dimensions 42 x 48 x 5mm &lt;br /&gt;
* Weight &amp;lt; 20 grams&lt;br /&gt;
* Interface 20-pin mini connector  &lt;br /&gt;
* Antenna MMCX jack Connector&lt;br /&gt;
* price : ~80$&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Aerocomm_AC4868_pinout.jpg|thumb|left|Aerocomm AC4868 modem pinout]]&lt;br /&gt;
[[Image:Aerocomm_AC4490-200_wired.jpg|thumb|left|Aerocomm AC4490 wiring example]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the Aerocomm AC4868 to the Tiny&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''AC4868 20-pin Header'''''||'''''Name'''''||'''''Color'''''||'''''Tiny v1.1 Serial-1'''''||'''''Tiny v2.11 Serial'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||2||Tx||green||7||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||3||Rx||blue||8||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||GND||black||1||1|| -&lt;br /&gt;
|-&lt;br /&gt;
||10+11||VCC||red||2||3||+3.3v ''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||17||C/D||white||3||?||Low = Command High = Data&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the AEROCOMM module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : AC4790-1000 needs pins 10 and 11 jumped to work properly''&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4790_mesh-ready_transceiver.htm AC4790 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4790_HI.pdf AC4790 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4790.pdf AC4790 Manual]&lt;br /&gt;
* [http://www.aerocomm.com/rf_transceiver_modules/ac4868_868mhz_rf_transceiver.htm AC4848 product page]&lt;br /&gt;
* [http://www.aerocomm.com/docs/Datasheet_AC4868_HI.pdf AC4868 Datasheet]&lt;br /&gt;
* [http://www.aerocomm.com/docs/User_Manual_AC4868.pdf AC4868 user manual]&lt;br /&gt;
&lt;br /&gt;
== Laird (ex Aerocomm) ==&lt;br /&gt;
&lt;br /&gt;
=== Laird LT2510 ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Lt2510_prm123.jpg|thumb|LT2510 Modem]]&lt;br /&gt;
&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 50mW (European version)&lt;br /&gt;
* Sensitivity  -98/-94 dBm &lt;br /&gt;
* RF Data Rate 280/500 kbps&lt;br /&gt;
* Interface data rate Up to 460800 kbps&lt;br /&gt;
* Power Draw (typical) 85mA TX / 10mA RX (European version)&lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 2400m line-of-sight (European version)&lt;br /&gt;
* Dimensions 24 x 33mm&lt;br /&gt;
* Weight 4 grams&lt;br /&gt;
* Interface 20-pin mini connector (solder pad or XBee compatible)&lt;br /&gt;
* Chip antenna, or a U.FL antenna connector&lt;br /&gt;
* Price: Approximately $31&lt;br /&gt;
&lt;br /&gt;
The LT2510 uses frequency hopping which needs a client/server model. That means that one modem (most appropriately the ground station modem) needs to be set to server mode. It will transmit a beacon message and have all client modems synchronize to that in a time and frequency hopping scheme manner. For that all modems need to have the same channel (in fact the hopping scheme) and system-id. Clients can be set to auto-channel and auto-system-id to follow any/the first visible server.&lt;br /&gt;
&lt;br /&gt;
All acknowledged messages transmitted need to be adressed to the non-changeable MAC address of the destination modem. There are is a way to automatically set destination adresses but this procedure does have drawbacks (see below).&lt;br /&gt;
&lt;br /&gt;
Make sure you short circuit &amp;quot;D1&amp;quot; if you use the Sparkfun WRL-09132 &amp;quot;XBee Explorer Regulated&amp;quot; adapter. The Laird does not have a pull-up resistor on DIN that Sparkfun assumes.&lt;br /&gt;
&lt;br /&gt;
==== Basic setup ====&lt;br /&gt;
&lt;br /&gt;
You can download a Windows configuration utility from [http://www.lairdtech.com/Products/Wireless-M2M-and-Telematics-Solutions/Proprietary-Radio-Modules/ here], click &amp;quot;Product Information&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
 Set client to client mode (default).&lt;br /&gt;
 Set server to server mode.&lt;br /&gt;
&lt;br /&gt;
 Set speed on both modems to 57600 baud, the Paparazzi standard.&lt;br /&gt;
&lt;br /&gt;
 Choose RF profile with low speed (280kbps) for long range (default).&lt;br /&gt;
&lt;br /&gt;
===== Transparent mode =====&lt;br /&gt;
&lt;br /&gt;
The transparent mode is different from the XBee modems transparent mode. It will only allow two modems to communicate with each other.&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with hard coded address ======&lt;br /&gt;
&lt;br /&gt;
In this mode the destination MAC address is permanently set in the EEPROMs of the modems. Only these two modems can communicate with each other. The advantage of this mode is that other modems can not confuse the communication. You have to read out both modems MAC adresses as they are not printed on the case.&lt;br /&gt;
&lt;br /&gt;
 Set server MAC address in client&lt;br /&gt;
 Set client MAC address in server&lt;br /&gt;
&lt;br /&gt;
====== Transparent mode with auto-address ======&lt;br /&gt;
&lt;br /&gt;
The server will start emitting beacon messages and the client locks to these, starting to send messages to the servers MAC address. The server will then respond to that clients data messages. In this mode only one server can talk to one client. Any appearance of another server or client modem will confuse/disrupt the communication.&lt;br /&gt;
&lt;br /&gt;
 Set server to auto-destination.&lt;br /&gt;
 Set client to auto-destination and auto-destination-beacons-only.&lt;br /&gt;
&lt;br /&gt;
===== API mode =====&lt;br /&gt;
&lt;br /&gt;
We need at least a simple form of address resolution as the modems own (MAC) address can not be changed. This makes the ground station link and on-board software a little more complicated than the XBee API mode.&lt;br /&gt;
&lt;br /&gt;
 tbd&lt;br /&gt;
&lt;br /&gt;
== Radiotronix ==&lt;br /&gt;
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-&amp;gt;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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== WI232EUR ===&lt;br /&gt;
* Frequency Band: 868 MHz (for Europe)&lt;br /&gt;
* Output Power: 32 mW &lt;br /&gt;
* RF Data Rate: Up to 76.8 kbps &lt;br /&gt;
* Interface Data Rate: up to 115.2 kbps &lt;br /&gt;
* Power Draw (typical): 65 mA TX / 20 mA RX &lt;br /&gt;
* Supply Voltage: 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment): 500 meters line-of-sight &lt;br /&gt;
* Dimensions: 24 x 21 x 4mm &lt;br /&gt;
* Weight: ~2 grams&lt;br /&gt;
* Interface: solder connector  &lt;br /&gt;
* Antenna: solder connector &lt;br /&gt;
* Price: ~25$&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_wiring.jpg|thumb|WI232EUR Modem (picture shows connection to Tiny 1.1)]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
=== Pinout ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
|+ Wiring the WI232EUR to the Tiny v1.1&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
||'''''WI232 pins'''''||'''''Name'''''||'''''Tiny Serial-1'''''||'''''Notes'''''&lt;br /&gt;
|-&lt;br /&gt;
||6||TxD||7||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||5||RxD||8||''(Note 1)''&lt;br /&gt;
|-&lt;br /&gt;
||15-18||GND||1|| - &lt;br /&gt;
|-&lt;br /&gt;
||19||VCC||2||+3.3v&lt;br /&gt;
|-&lt;br /&gt;
||4||/CMD||-||''(Note 2)''&lt;br /&gt;
|-&lt;br /&gt;
||7||CTS||-||''(Note 3)''&lt;br /&gt;
|}&lt;br /&gt;
''Note 1 : names are specified with respect to the Radiotronix module''&lt;br /&gt;
&lt;br /&gt;
''Note 2 : connect to RTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
''Note 3 : connect to CTS to program device with Evaluation software''&lt;br /&gt;
&lt;br /&gt;
|&lt;br /&gt;
[[Image:Wi232eur_bopla.jpg|thumb|WI232EUR Modem in BOPLA case]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
|}&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/eur_um.pdf WI232EUR data sheet]&lt;br /&gt;
* [http://www.radiotronix.com/datasheets/new/rk-eur_um.pdf WI232EUR user's manual]&lt;br /&gt;
* [http://www.radiotronix.com/downloads/software/EUR/setup.exe Evaluation software]&lt;br /&gt;
&lt;br /&gt;
== Bluetooth ==&lt;br /&gt;
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.&lt;br /&gt;
{|&lt;br /&gt;
|&lt;br /&gt;
=== &amp;quot;Sparkfun&amp;quot; Roving Networks (WRL-08497) ===&lt;br /&gt;
* Frequency Band 2.4GHz&lt;br /&gt;
* Output Power 32 mW &lt;br /&gt;
* RF Data Rate up to ~300 kbps in SPP&lt;br /&gt;
* Interface Data Rate up to 921 kbps &lt;br /&gt;
* Power Draw (typical) 50 mA TX / 40 mA RX &lt;br /&gt;
* Supply Voltage 3.3v&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) 100 meters line-of-sight &lt;br /&gt;
* Dimensions 26 x 13 x 2mm &lt;br /&gt;
* Weight ~1.5 grams&lt;br /&gt;
* Interface solder connector  &lt;br /&gt;
* price : ~45$&lt;br /&gt;
|&lt;br /&gt;
[[Image:roving_nw_wiring.jpg|thumb|Roving Networks modem wiring]]&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&lt;br /&gt;
To connect to it, get the MAC address of the bluetooth modem&lt;br /&gt;
&lt;br /&gt;
 me@mybox:~$ hcitool scan&lt;br /&gt;
 Scanning ...&lt;br /&gt;
        00:06:66:00:53:AD       FireFly-53AD&lt;br /&gt;
&lt;br /&gt;
either make a virtual connection to a Bluetooth serial port each time you connect&lt;br /&gt;
&lt;br /&gt;
 sudo rfcomm bind 0 00:06:66:00:53:AD&lt;br /&gt;
&lt;br /&gt;
or configure it once in /etc/bluetooth/rfcomm.conf&lt;br /&gt;
&lt;br /&gt;
 rfcomm0 {&lt;br /&gt;
   bind yes;&lt;br /&gt;
   device 00:06:66:00:53:AD;&lt;br /&gt;
 }&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Coronis WaveCard ==&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
'''Suport for these modems has been removed from the airborne code on Dec 10th, 2007.'''&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
* Frequency Band 400MHz, 868Mhz and 915MHz (3 versions)&lt;br /&gt;
* Output Power 25mW and 500mW (2 versions)&lt;br /&gt;
* Sensitivity  -110 dBm (@ 9600 bps)&lt;br /&gt;
* Data Rate 100 Kbps&lt;br /&gt;
* Power Draw (typical) 45mA (25mW), 450mA (500mW) TX / 15 mA RX &lt;br /&gt;
* Supply Voltage ...&lt;br /&gt;
* Range (typical, depends on antenna &amp;amp; environment) Up to 1km (25mW) , 5km (500mW) line-of-sight &lt;br /&gt;
* Dimensions 30 x 28 x 7mm (25mW), 37 x 30 x 7mm (500mW)&lt;br /&gt;
* 50 ohm RF port for antenna connection&lt;br /&gt;
|&lt;br /&gt;
[[Image:wavecard.jpg|Coronis Wavecard]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Documentation ===&lt;br /&gt;
&lt;br /&gt;
* [http://www.coronis-systems.com/produit.php?lang=EN&amp;amp;id=WCA  www.coronis-systems.com]&lt;br /&gt;
* [[Media:CS-COM-SPRD-WAVECARD-E03B.pdf|Wavecard datasheet]]&lt;br /&gt;
&lt;br /&gt;
== Telemetry via Video Transmitter==&lt;br /&gt;
&lt;br /&gt;
[[Image:video_tx_small.jpg|thumb|2.4GHz Video Transmitter]]&lt;br /&gt;
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. &lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Antennas ==&lt;br /&gt;
&lt;br /&gt;
Here are some examples of lightweight and efficient 868MHz antennas developped by the RF laboratory at ENAC.&lt;br /&gt;
[[Image:868mhz_twinstar_antenna_1.jpg|thumb|left|868MHz copper foil antenna attached to the aircraft tail]] &lt;br /&gt;
[[Image:868mhz_twinstar_antenna_2.jpg|thumb|left|868MHz copper foil antenna bottom view]] &lt;br /&gt;
[[Image:868mhz_ground_antenna.jpg|thumb|left|868MHz ground antenna]] &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This wiki page might give some ideas about antennas: http://en.wikipedia.org/wiki/Dipole_antenna&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=13382</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=13382"/>
		<updated>2012-11-01T23:43:42Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Project notes: Raspberry Pi ground control station =&lt;br /&gt;
&lt;br /&gt;
I want a cheap headless GCS that speaks to me (possibly via CB radio), keeps logs, and provides a convenient place for me to tinker with agents and such (development time) with a maximally simple setup at the field. I will probably want a build system (for reflashing firmware at the field) and integration with FPV video, but those jobs are for later.&lt;br /&gt;
&lt;br /&gt;
I started with a Raspberry pi (rpi) running debian squeeze, which is what I run on my field laptop, but that was a dead end. Ocaml on squeeze is 3.11.2 (with no backport available), and that version doesn't support ocamlopt on ARM architectures. So far I've learned that I should be on a wheeze-based distribution (ocaml &amp;gt; 3.11, supporting ocamlopt on ARM), and I probably want to utilise the hardware float so that means I'll move to raspbian next.&lt;br /&gt;
&lt;br /&gt;
http://www.raspbian.org/&lt;br /&gt;
&lt;br /&gt;
My plan is to mudde through and get it working, then publish an install script that makes the install process repeatable. After that I might look into packaging, but I don't know much about that (yet).&lt;br /&gt;
&lt;br /&gt;
= About me =&lt;br /&gt;
&lt;br /&gt;
I'm an open source UAV enthusuiast from Canberra (Australia), with a penchant for paparazzi and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me Rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com. But don't call me Christopher, only my mum does that (and then only when I'm in trouble) so it's creepy/weired. Call me Chris.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* On GitHub I'm monkeypants, on eBay I'm monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing planes and am slowly moving to STM32, but mostly still LPC.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=13381</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=13381"/>
		<updated>2012-11-01T23:22:28Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Current project: Lisa/M Quad */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Talk:ArduIMU&amp;diff=13380</id>
		<title>Talk:ArduIMU</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Talk:ArduIMU&amp;diff=13380"/>
		<updated>2012-11-01T14:09:13Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please post info on magnetometer installation... Has this been done already? Is the code in the git repo?&lt;br /&gt;
&amp;lt;BR&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;BR&amp;gt;&lt;br /&gt;
What is the max polling rate we can use?&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
Looking at the code and it seems to be version 1.7 which is old.. Can you give documentation on how to integrate the changes that were made to make the arduimu code work for pprz?&lt;br /&gt;
&amp;lt;BR&amp;gt;--Danstah&lt;br /&gt;
&lt;br /&gt;
&amp;lt;BR&amp;gt;&lt;br /&gt;
Is this comment obsolete?&lt;br /&gt;
&lt;br /&gt;
  You may have to comment out the following two lines in the file&lt;br /&gt;
   ../paparazzi/sw/airborne/modules/ins/ins_arduimu.c for the code to compile:&lt;br /&gt;
  // float throttle_slew;&lt;br /&gt;
  // throttle_slew = V_CTL_THROTTLE_SLEW;&lt;br /&gt;
&lt;br /&gt;
Perhaps it should say:&lt;br /&gt;
&lt;br /&gt;
  With older versions of the code, you may have to...&lt;br /&gt;
&lt;br /&gt;
--Rufus&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13379</id>
		<title>ArduIMU</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13379"/>
		<updated>2012-11-01T13:45:05Z</updated>

		<summary type="html">&lt;p&gt;Rufus: note about ahrs subsystem for sim&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:ArduIMU_xs.JPG|thumb|right|ArduIMU with i2c wires and serial connector]]&lt;br /&gt;
[[Image:Tiny13wIMU_001.jpg|thumb|right|Tiny13 w/IMU]]&lt;br /&gt;
[[Image:Ppzfunjetaimu01.jpg|thumb|right|TWOG w/IMU]]&lt;br /&gt;
This page describes how to integrate an [http://code.google.com/p/ardu-imu/wiki/HomePage?tm=6 ArduIMU+ V2 (flat)] into an existing Airframe/Paparazzi-Code.&lt;br /&gt;
#The ArduIMU communicates over i2c with the Paparazzi-AP. The wiring is pretty easy to do. Connect SDA, SCL, ground at the i2c pins. Supply the IMU with 5V at one of the three 5V pins. The 3.3V i2c pin stays unconnected. Do not connect 3.3V from the Paparazzi-AP to the ArduIMU as it internally generates it's own stable 3.3v supply.&lt;br /&gt;
#Integration into the Paparazzi software is realized as a module. This is an easy way to connect and test the software. &lt;br /&gt;
#This description shows how to use the ArduIMU without a separate GPS-Receiver and without a Compass/Magnetometer. The GPS-Data is sent by the Paparazzi-AP over i2c to the ArduIMU.&lt;br /&gt;
#There is an other airframe/main-AP we wrote which uses a magnetometer for yaw-drift compensation. We haven't written an installation guide for this configuration yet. But we will try to do this as soon as possible. &lt;br /&gt;
&lt;br /&gt;
The Code has been integrated into the Paparazzi build system.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Airframe Adjustments ==&lt;br /&gt;
&lt;br /&gt;
First, remove the infrared configuration and substitute the IMU configuration (which uses I2C) as follows :&lt;br /&gt;
&lt;br /&gt;
In your airframe file (found usually in conf/airframes with a name like &amp;quot;MyAirframe.xml&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* (1) '''Insert''' the software module :&lt;br /&gt;
 &amp;lt;modules&amp;gt;&lt;br /&gt;
   &amp;lt;load name=&amp;quot;ins_arduimu.xml&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/modules&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (2) Increase i2c queue length to 16, and reduce i2c clock speed:&lt;br /&gt;
 &amp;lt;target name=&amp;quot;ap&amp;quot;    board=&amp;quot;...&amp;quot;&amp;gt;&lt;br /&gt;
           ...&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C_TRANSACTION_QUEUE_LEN&amp;quot; value=&amp;quot;16&amp;quot;/&amp;gt; &amp;lt;!-- default is 8 --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLL&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- default clock speed 37.5KHz with our 15MHz PCLK I2C0_CLOCK=PCLK/(I2C0_SCLL+I2C0_SCLH) --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLH&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- Default values are 200 and must be the same for both SCLL and SCLH --&amp;gt;&lt;br /&gt;
 &amp;lt;/target&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you don't already have it, you will also need to add this to your ap target too:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;define name=&amp;quot;USE_I2C0&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (3) '''Insert''' INS neutrals:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;section name=&amp;quot;INS&amp;quot; prefix=&amp;quot;INS_&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;ROLL_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;PITCH_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (4) '''Remove''' the infrared estimation :&lt;br /&gt;
&lt;br /&gt;
 remove the line that looks like the following:&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;ahrs&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
 or if you still have the older subsystem&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;attitude&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may have to comment out the following two lines in the file ../paparazzi/sw/airborne/modules/ins/ins_arduimu.c for the code to compile:&lt;br /&gt;
&lt;br /&gt;
  // float throttle_slew;&lt;br /&gt;
  // throttle_slew = V_CTL_THROTTLE_SLEW;&lt;br /&gt;
&lt;br /&gt;
Also, if you want to be able to run SITL simulations on this airframe, you will need to add an ahrs subsystem to your simulation target:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;target name=&amp;quot;sim&amp;quot; board=&amp;quot;pc&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;subsystem name=&amp;quot;ahrs&amp;quot; type=&amp;quot;float_dcm&amp;quot;/&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
  &amp;lt;/target&amp;gt;&lt;br /&gt;
&lt;br /&gt;
TODO: link to sample working airframe in git&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' Martin Mueller has committed some ArduIMU changes to&lt;br /&gt;
https://github.com/martinmm/paparazzi for review.&lt;br /&gt;
&lt;br /&gt;
It is based on ArduIMU v1.7 and fixes the main issue which was printing serial data while in I2C interrupt, also includes Steve Joyce's fixes. &lt;br /&gt;
&lt;br /&gt;
Additional features are running at 60Hz, having the possibility to use the Paparazzi ROLL_RATE loop and transferring the gps data as it is received rather than at a constant, non synchronized rate. The v1.7 uses gps 3D speed for centrifugal correction whereas the v1.8.2 uses 2D speed. &lt;br /&gt;
&lt;br /&gt;
Bill Premerlani's paper is a little vague on that but it is thought that 3D should be more precise when climbing/descending. Maybe 2D is used as simple gps receivers don't have 3D speed?&lt;br /&gt;
&lt;br /&gt;
An example airframe file is at /conf/airframes/mm/fixed-wing/fw_ins_arduimu.xml It controlled a Funjet in 55m circles climbing 6m/s nicely.&lt;br /&gt;
&lt;br /&gt;
== Aircraft Settings ==&lt;br /&gt;
&lt;br /&gt;
* (5) Use this '''Settings''' file: settings/tuning_basic_ins.xml&lt;br /&gt;
&lt;br /&gt;
== Magnetometer (Ignore for now) ==&lt;br /&gt;
TODO: post Magnetometer integration guide&lt;br /&gt;
&lt;br /&gt;
== Flash the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
(6) Programming the ArduIMU for use with the Tiny includes using : &lt;br /&gt;
# Adapted software in '''sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps'''. &lt;br /&gt;
# Standard USB FTDI cable plugged into the header that comes with the arduimu (Match the wire colors with those written on the arduimu silkscreen GRN=Green BLK=Black)&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
&lt;br /&gt;
*Plug in USB FTDI Cable to PC and ArduIMU (this also provides power)&lt;br /&gt;
&lt;br /&gt;
*Install the Arduino IDE using the Ubuntu Software Center or the following command line:&lt;br /&gt;
  $ sudo apt-get install arduino&lt;br /&gt;
&lt;br /&gt;
*Launch the Arduino IDE using the Dash (in Ubuntu 11.04) or the following command line:&lt;br /&gt;
  $ arduino&lt;br /&gt;
[[Image:arduino_open_sketch.png|thumb]]&lt;br /&gt;
(TODO: Using the graphical interface is probably not necessary as the flashing seems to use avrdude command line utility)&lt;br /&gt;
&lt;br /&gt;
* Open project/sketch (File-&amp;gt;open , point to paparazzi/sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps/arduimu/arduime.pde)&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;verify&amp;quot; button compiles&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;upload&amp;quot; button flashes&lt;br /&gt;
** You may need to select your com port in menu Tools-&amp;gt;Serial Port&lt;br /&gt;
** You may need to select Atmega328 in menu Tool-&amp;gt;Board&lt;br /&gt;
&lt;br /&gt;
For more information concerning flashing of the ArduIMU, read:  http://code.google.com/p/ardu-imu/wiki/Code&lt;br /&gt;
&lt;br /&gt;
Do we still need this or is everything in git now?&lt;br /&gt;
 You can find the original ZHAW code [https://home.zhaw.ch/~schmiemi/Arduimu4Paprazzi.rar here].&lt;br /&gt;
&lt;br /&gt;
== Install and test the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
* The current firmware does not implement a full rotation matrix calculation and instead assumes that the arduimu's &amp;quot;x&amp;quot; axis is aligned with the fuselage. When installing the device in your aircraft be sure to respect this constraint.&lt;br /&gt;
&lt;br /&gt;
* Clean and build your aircraft target in paparazzi center and flash your Tiny as usual&lt;br /&gt;
&lt;br /&gt;
* With your GCS session running, you should see attitudes messages including the new messages &amp;quot;xxx&amp;quot; and &amp;quot; xxx&amp;quot; &lt;br /&gt;
[[Image:arduimu_gcs_messages.png|thumb]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Considerations ==&lt;br /&gt;
&lt;br /&gt;
So far, this setup has been successfully flown in the Maja and EasyStar aircraft. For faster more agile aircraft such as the Merlin or Funjet, the polling rate needs to be changed from 15 Hz to 50 Hz in the '''/conf/modules/ins_arduimu.xml''' file.&lt;br /&gt;
&lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodic()&amp;quot; freq=&amp;quot;50&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodicGPS()&amp;quot; freq=&amp;quot;4&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The ArduIMU is sensitive to vibrations. Mount it on a thick piece of foam to dampen the vibrations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have Fun !&lt;br /&gt;
&lt;br /&gt;
== Analysis and Results ==&lt;br /&gt;
&lt;br /&gt;
TODO: Compare IR and arduimu estimations for various flight conditions&lt;br /&gt;
TODO: Fuse the two estimates together for robustness?&lt;br /&gt;
&lt;br /&gt;
Please Post Results Here... Issues?&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]] [[Category:Modules]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13378</id>
		<title>ArduIMU</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13378"/>
		<updated>2012-11-01T13:40:45Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Airframe Adjustments */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:ArduIMU_xs.JPG|thumb|right|ArduIMU with i2c wires and serial connector]]&lt;br /&gt;
[[Image:Tiny13wIMU_001.jpg|thumb|right|Tiny13 w/IMU]]&lt;br /&gt;
[[Image:Ppzfunjetaimu01.jpg|thumb|right|TWOG w/IMU]]&lt;br /&gt;
This page describes how to integrate an [http://code.google.com/p/ardu-imu/wiki/HomePage?tm=6 ArduIMU+ V2 (flat)] into an existing Airframe/Paparazzi-Code.&lt;br /&gt;
#The ArduIMU communicates over i2c with the Paparazzi-AP. The wiring is pretty easy to do. Connect SDA, SCL, ground at the i2c pins. Supply the IMU with 5V at one of the three 5V pins. The 3.3V i2c pin stays unconnected. Do not connect 3.3V from the Paparazzi-AP to the ArduIMU as it internally generates it's own stable 3.3v supply.&lt;br /&gt;
#Integration into the Paparazzi software is realized as a module. This is an easy way to connect and test the software. &lt;br /&gt;
#This description shows how to use the ArduIMU without a separate GPS-Receiver and without a Compass/Magnetometer. The GPS-Data is sent by the Paparazzi-AP over i2c to the ArduIMU.&lt;br /&gt;
#There is an other airframe/main-AP we wrote which uses a magnetometer for yaw-drift compensation. We haven't written an installation guide for this configuration yet. But we will try to do this as soon as possible. &lt;br /&gt;
&lt;br /&gt;
The Code has been integrated into the Paparazzi build system.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Airframe Adjustments ==&lt;br /&gt;
&lt;br /&gt;
First, remove the infrared configuration and substitute the IMU configuration (which uses I2C) as follows :&lt;br /&gt;
&lt;br /&gt;
In your airframe file (found usually in conf/airframes with a name like &amp;quot;MyAirframe.xml&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* (1) '''Insert''' the software module :&lt;br /&gt;
 &amp;lt;modules&amp;gt;&lt;br /&gt;
   &amp;lt;load name=&amp;quot;ins_arduimu.xml&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/modules&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (2) Increase i2c queue length to 16, and reduce i2c clock speed:&lt;br /&gt;
 &amp;lt;target name=&amp;quot;ap&amp;quot;    board=&amp;quot;...&amp;quot;&amp;gt;&lt;br /&gt;
           ...&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C_TRANSACTION_QUEUE_LEN&amp;quot; value=&amp;quot;16&amp;quot;/&amp;gt; &amp;lt;!-- default is 8 --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLL&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- default clock speed 37.5KHz with our 15MHz PCLK I2C0_CLOCK=PCLK/(I2C0_SCLL+I2C0_SCLH) --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLH&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- Default values are 200 and must be the same for both SCLL and SCLH --&amp;gt;&lt;br /&gt;
 &amp;lt;/target&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you don't already have it, you will also need to add this to your ap target too:&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;define name=&amp;quot;USE_I2C0&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (3) '''Insert''' INS neutrals:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;section name=&amp;quot;INS&amp;quot; prefix=&amp;quot;INS_&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;ROLL_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;PITCH_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (4) '''Remove''' the infrared estimation :&lt;br /&gt;
&lt;br /&gt;
 remove the line that looks like the following:&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;ahrs&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
 or if you still have the older subsystem&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;attitude&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may have to comment out the following two lines in the file ../paparazzi/sw/airborne/modules/ins/ins_arduimu.c for the code to compile:&lt;br /&gt;
&lt;br /&gt;
  // float throttle_slew;&lt;br /&gt;
  // throttle_slew = V_CTL_THROTTLE_SLEW;&lt;br /&gt;
&lt;br /&gt;
TODO: link to sample working airframe in git&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' Martin Mueller has committed some ArduIMU changes to&lt;br /&gt;
https://github.com/martinmm/paparazzi for review.&lt;br /&gt;
&lt;br /&gt;
It is based on ArduIMU v1.7 and fixes the main issue which was printing serial data while in I2C interrupt, also includes Steve Joyce's fixes. &lt;br /&gt;
&lt;br /&gt;
Additional features are running at 60Hz, having the possibility to use the Paparazzi ROLL_RATE loop and transferring the gps data as it is received rather than at a constant, non synchronized rate. The v1.7 uses gps 3D speed for centrifugal correction whereas the v1.8.2 uses 2D speed. &lt;br /&gt;
&lt;br /&gt;
Bill Premerlani's paper is a little vague on that but it is thought that 3D should be more precise when climbing/descending. Maybe 2D is used as simple gps receivers don't have 3D speed?&lt;br /&gt;
&lt;br /&gt;
An example airframe file is at /conf/airframes/mm/fixed-wing/fw_ins_arduimu.xml It controlled a Funjet in 55m circles climbing 6m/s nicely.&lt;br /&gt;
&lt;br /&gt;
== Aircraft Settings ==&lt;br /&gt;
&lt;br /&gt;
* (5) Use this '''Settings''' file: settings/tuning_basic_ins.xml&lt;br /&gt;
&lt;br /&gt;
== Magnetometer (Ignore for now) ==&lt;br /&gt;
TODO: post Magnetometer integration guide&lt;br /&gt;
&lt;br /&gt;
== Flash the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
(6) Programming the ArduIMU for use with the Tiny includes using : &lt;br /&gt;
# Adapted software in '''sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps'''. &lt;br /&gt;
# Standard USB FTDI cable plugged into the header that comes with the arduimu (Match the wire colors with those written on the arduimu silkscreen GRN=Green BLK=Black)&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
&lt;br /&gt;
*Plug in USB FTDI Cable to PC and ArduIMU (this also provides power)&lt;br /&gt;
&lt;br /&gt;
*Install the Arduino IDE using the Ubuntu Software Center or the following command line:&lt;br /&gt;
  $ sudo apt-get install arduino&lt;br /&gt;
&lt;br /&gt;
*Launch the Arduino IDE using the Dash (in Ubuntu 11.04) or the following command line:&lt;br /&gt;
  $ arduino&lt;br /&gt;
[[Image:arduino_open_sketch.png|thumb]]&lt;br /&gt;
(TODO: Using the graphical interface is probably not necessary as the flashing seems to use avrdude command line utility)&lt;br /&gt;
&lt;br /&gt;
* Open project/sketch (File-&amp;gt;open , point to paparazzi/sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps/arduimu/arduime.pde)&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;verify&amp;quot; button compiles&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;upload&amp;quot; button flashes&lt;br /&gt;
** You may need to select your com port in menu Tools-&amp;gt;Serial Port&lt;br /&gt;
** You may need to select Atmega328 in menu Tool-&amp;gt;Board&lt;br /&gt;
&lt;br /&gt;
For more information concerning flashing of the ArduIMU, read:  http://code.google.com/p/ardu-imu/wiki/Code&lt;br /&gt;
&lt;br /&gt;
Do we still need this or is everything in git now?&lt;br /&gt;
 You can find the original ZHAW code [https://home.zhaw.ch/~schmiemi/Arduimu4Paprazzi.rar here].&lt;br /&gt;
&lt;br /&gt;
== Install and test the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
* The current firmware does not implement a full rotation matrix calculation and instead assumes that the arduimu's &amp;quot;x&amp;quot; axis is aligned with the fuselage. When installing the device in your aircraft be sure to respect this constraint.&lt;br /&gt;
&lt;br /&gt;
* Clean and build your aircraft target in paparazzi center and flash your Tiny as usual&lt;br /&gt;
&lt;br /&gt;
* With your GCS session running, you should see attitudes messages including the new messages &amp;quot;xxx&amp;quot; and &amp;quot; xxx&amp;quot; &lt;br /&gt;
[[Image:arduimu_gcs_messages.png|thumb]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Considerations ==&lt;br /&gt;
&lt;br /&gt;
So far, this setup has been successfully flown in the Maja and EasyStar aircraft. For faster more agile aircraft such as the Merlin or Funjet, the polling rate needs to be changed from 15 Hz to 50 Hz in the '''/conf/modules/ins_arduimu.xml''' file.&lt;br /&gt;
&lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodic()&amp;quot; freq=&amp;quot;50&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodicGPS()&amp;quot; freq=&amp;quot;4&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The ArduIMU is sensitive to vibrations. Mount it on a thick piece of foam to dampen the vibrations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have Fun !&lt;br /&gt;
&lt;br /&gt;
== Analysis and Results ==&lt;br /&gt;
&lt;br /&gt;
TODO: Compare IR and arduimu estimations for various flight conditions&lt;br /&gt;
TODO: Fuse the two estimates together for robustness?&lt;br /&gt;
&lt;br /&gt;
Please Post Results Here... Issues?&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]] [[Category:Modules]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13377</id>
		<title>ArduIMU</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=ArduIMU&amp;diff=13377"/>
		<updated>2012-11-01T13:40:03Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Airframe Adjustments */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Image:ArduIMU_xs.JPG|thumb|right|ArduIMU with i2c wires and serial connector]]&lt;br /&gt;
[[Image:Tiny13wIMU_001.jpg|thumb|right|Tiny13 w/IMU]]&lt;br /&gt;
[[Image:Ppzfunjetaimu01.jpg|thumb|right|TWOG w/IMU]]&lt;br /&gt;
This page describes how to integrate an [http://code.google.com/p/ardu-imu/wiki/HomePage?tm=6 ArduIMU+ V2 (flat)] into an existing Airframe/Paparazzi-Code.&lt;br /&gt;
#The ArduIMU communicates over i2c with the Paparazzi-AP. The wiring is pretty easy to do. Connect SDA, SCL, ground at the i2c pins. Supply the IMU with 5V at one of the three 5V pins. The 3.3V i2c pin stays unconnected. Do not connect 3.3V from the Paparazzi-AP to the ArduIMU as it internally generates it's own stable 3.3v supply.&lt;br /&gt;
#Integration into the Paparazzi software is realized as a module. This is an easy way to connect and test the software. &lt;br /&gt;
#This description shows how to use the ArduIMU without a separate GPS-Receiver and without a Compass/Magnetometer. The GPS-Data is sent by the Paparazzi-AP over i2c to the ArduIMU.&lt;br /&gt;
#There is an other airframe/main-AP we wrote which uses a magnetometer for yaw-drift compensation. We haven't written an installation guide for this configuration yet. But we will try to do this as soon as possible. &lt;br /&gt;
&lt;br /&gt;
The Code has been integrated into the Paparazzi build system.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Airframe Adjustments ==&lt;br /&gt;
&lt;br /&gt;
First, remove the infrared configuration and substitute the IMU configuration (which uses I2C) as follows :&lt;br /&gt;
&lt;br /&gt;
In your airframe file (found usually in conf/airframes with a name like &amp;quot;MyAirframe.xml&amp;quot;)&lt;br /&gt;
&lt;br /&gt;
* (1) '''Insert''' the software module :&lt;br /&gt;
 &amp;lt;modules&amp;gt;&lt;br /&gt;
   &amp;lt;load name=&amp;quot;ins_arduimu.xml&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/modules&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (2) Increase i2c queue length to 16, and reduce i2c clock speed:&lt;br /&gt;
 &amp;lt;target name=&amp;quot;ap&amp;quot;    board=&amp;quot;...&amp;quot;&amp;gt;&lt;br /&gt;
           ...&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C_TRANSACTION_QUEUE_LEN&amp;quot; value=&amp;quot;16&amp;quot;/&amp;gt; &amp;lt;!-- default is 8 --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLL&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- default clock speed 37.5KHz with our 15MHz PCLK I2C0_CLOCK=PCLK/(I2C0_SCLL+I2C0_SCLH) --&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;I2C0_SCLH&amp;quot; value=&amp;quot;400&amp;quot;/&amp;gt; &amp;lt;!-- Default values are 200 and must be the same for both SCLL and SCLH --&amp;gt;&lt;br /&gt;
 &amp;lt;/target&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you don't already have it, you will also need to add this to your ap target&lt;br /&gt;
&lt;br /&gt;
  &amp;lt;define name=&amp;quot;USE_I2C0&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (3) '''Insert''' INS neutrals:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;section name=&amp;quot;INS&amp;quot; prefix=&amp;quot;INS_&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;ROLL_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;define name=&amp;quot;PITCH_NEUTRAL_DEFAULT&amp;quot; value=&amp;quot;0&amp;quot; unit=&amp;quot;deg&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/section&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* (4) '''Remove''' the infrared estimation :&lt;br /&gt;
&lt;br /&gt;
 remove the line that looks like the following:&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;ahrs&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
 or if you still have the older subsystem&lt;br /&gt;
 &amp;lt;subsystem name=&amp;quot;attitude&amp;quot;         type=&amp;quot;infrared&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You may have to comment out the following two lines in the file ../paparazzi/sw/airborne/modules/ins/ins_arduimu.c for the code to compile:&lt;br /&gt;
&lt;br /&gt;
  // float throttle_slew;&lt;br /&gt;
  // throttle_slew = V_CTL_THROTTLE_SLEW;&lt;br /&gt;
&lt;br /&gt;
TODO: link to sample working airframe in git&lt;br /&gt;
&lt;br /&gt;
'''NOTE:''' Martin Mueller has committed some ArduIMU changes to&lt;br /&gt;
https://github.com/martinmm/paparazzi for review.&lt;br /&gt;
&lt;br /&gt;
It is based on ArduIMU v1.7 and fixes the main issue which was printing serial data while in I2C interrupt, also includes Steve Joyce's fixes. &lt;br /&gt;
&lt;br /&gt;
Additional features are running at 60Hz, having the possibility to use the Paparazzi ROLL_RATE loop and transferring the gps data as it is received rather than at a constant, non synchronized rate. The v1.7 uses gps 3D speed for centrifugal correction whereas the v1.8.2 uses 2D speed. &lt;br /&gt;
&lt;br /&gt;
Bill Premerlani's paper is a little vague on that but it is thought that 3D should be more precise when climbing/descending. Maybe 2D is used as simple gps receivers don't have 3D speed?&lt;br /&gt;
&lt;br /&gt;
An example airframe file is at /conf/airframes/mm/fixed-wing/fw_ins_arduimu.xml It controlled a Funjet in 55m circles climbing 6m/s nicely.&lt;br /&gt;
&lt;br /&gt;
== Aircraft Settings ==&lt;br /&gt;
&lt;br /&gt;
* (5) Use this '''Settings''' file: settings/tuning_basic_ins.xml&lt;br /&gt;
&lt;br /&gt;
== Magnetometer (Ignore for now) ==&lt;br /&gt;
TODO: post Magnetometer integration guide&lt;br /&gt;
&lt;br /&gt;
== Flash the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
(6) Programming the ArduIMU for use with the Tiny includes using : &lt;br /&gt;
# Adapted software in '''sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps'''. &lt;br /&gt;
# Standard USB FTDI cable plugged into the header that comes with the arduimu (Match the wire colors with those written on the arduimu silkscreen GRN=Green BLK=Black)&lt;br /&gt;
&lt;br /&gt;
Steps:&lt;br /&gt;
&lt;br /&gt;
*Plug in USB FTDI Cable to PC and ArduIMU (this also provides power)&lt;br /&gt;
&lt;br /&gt;
*Install the Arduino IDE using the Ubuntu Software Center or the following command line:&lt;br /&gt;
  $ sudo apt-get install arduino&lt;br /&gt;
&lt;br /&gt;
*Launch the Arduino IDE using the Dash (in Ubuntu 11.04) or the following command line:&lt;br /&gt;
  $ arduino&lt;br /&gt;
[[Image:arduino_open_sketch.png|thumb]]&lt;br /&gt;
(TODO: Using the graphical interface is probably not necessary as the flashing seems to use avrdude command line utility)&lt;br /&gt;
&lt;br /&gt;
* Open project/sketch (File-&amp;gt;open , point to paparazzi/sw/airborne/firmwares/non_ap/arduimu_Firmware_WithGps/arduimu/arduime.pde)&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;verify&amp;quot; button compiles&lt;br /&gt;
&lt;br /&gt;
* Clicking the &amp;quot;upload&amp;quot; button flashes&lt;br /&gt;
** You may need to select your com port in menu Tools-&amp;gt;Serial Port&lt;br /&gt;
** You may need to select Atmega328 in menu Tool-&amp;gt;Board&lt;br /&gt;
&lt;br /&gt;
For more information concerning flashing of the ArduIMU, read:  http://code.google.com/p/ardu-imu/wiki/Code&lt;br /&gt;
&lt;br /&gt;
Do we still need this or is everything in git now?&lt;br /&gt;
 You can find the original ZHAW code [https://home.zhaw.ch/~schmiemi/Arduimu4Paprazzi.rar here].&lt;br /&gt;
&lt;br /&gt;
== Install and test the ArduIMU ==&lt;br /&gt;
&lt;br /&gt;
* The current firmware does not implement a full rotation matrix calculation and instead assumes that the arduimu's &amp;quot;x&amp;quot; axis is aligned with the fuselage. When installing the device in your aircraft be sure to respect this constraint.&lt;br /&gt;
&lt;br /&gt;
* Clean and build your aircraft target in paparazzi center and flash your Tiny as usual&lt;br /&gt;
&lt;br /&gt;
* With your GCS session running, you should see attitudes messages including the new messages &amp;quot;xxx&amp;quot; and &amp;quot; xxx&amp;quot; &lt;br /&gt;
[[Image:arduimu_gcs_messages.png|thumb]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Considerations ==&lt;br /&gt;
&lt;br /&gt;
So far, this setup has been successfully flown in the Maja and EasyStar aircraft. For faster more agile aircraft such as the Merlin or Funjet, the polling rate needs to be changed from 15 Hz to 50 Hz in the '''/conf/modules/ins_arduimu.xml''' file.&lt;br /&gt;
&lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodic()&amp;quot; freq=&amp;quot;50&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
   &amp;lt;periodic fun=&amp;quot;ArduIMU_periodicGPS()&amp;quot; freq=&amp;quot;4&amp;quot; autorun=&amp;quot;TRUE&amp;quot;/&amp;gt; &lt;br /&gt;
&lt;br /&gt;
The ArduIMU is sensitive to vibrations. Mount it on a thick piece of foam to dampen the vibrations.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Have Fun !&lt;br /&gt;
&lt;br /&gt;
== Analysis and Results ==&lt;br /&gt;
&lt;br /&gt;
TODO: Compare IR and arduimu estimations for various flight conditions&lt;br /&gt;
TODO: Fuse the two estimates together for robustness?&lt;br /&gt;
&lt;br /&gt;
Please Post Results Here... Issues?&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]] [[Category:Modules]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Control_Loops&amp;diff=11973</id>
		<title>Control Loops</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Control_Loops&amp;diff=11973"/>
		<updated>2012-03-15T11:47:50Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Roll loop */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page presents the default control loops used by the Paparazzi airborne code for navigation, guidance and control.&lt;br /&gt;
&lt;br /&gt;
= General Information =&lt;br /&gt;
&lt;br /&gt;
All the possible combinations of control loops might not be fully detailed. This is especially the case when using extra features such as '''AGR_CLIMB''', '''STRONG_WIND''', etc.&lt;br /&gt;
&lt;br /&gt;
In the following diagrams, the block '''s''' is used for the '''derivative''' function and '''1/s''' is used for the '''integrator''' function.&lt;br /&gt;
&lt;br /&gt;
The variables' names are the one used in the airborne code (written in '''C'''). Most of this name can the used capitalized in the [[Airframe Configuration]] file in order to define the default value of these variables. If in capital letters in the diagrams, the value is fixed and cannot be changed using [[Settings]] mechanism.&lt;br /&gt;
&lt;br /&gt;
The best way to determine vehicle behavior is to look at the source code. For determining which control loops are engaged by various flight plan blocks and stages, it may be helpful to look at sw/airborne/subsystems/nav.h and the generated flightplan file in var/&amp;lt;AIRCRAFT_NAME&amp;gt;/generated/flight_plan.h.&lt;br /&gt;
&lt;br /&gt;
= Fixed-wing autopilot =&lt;br /&gt;
&lt;br /&gt;
== Global view ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_general.png|General overview]]&lt;br /&gt;
&lt;br /&gt;
The elements '''servos''', '''rc_commands''', '''commands''' and '''command_laws''' correspond to specific section of the [[Airframe Configuration]] file. Most of the code located in these blocks is generated from the xml of th configuration file.&lt;br /&gt;
&lt;br /&gt;
The value '''+/-9600''' correspond to '''+/-MAX_PPRZ'''. This '''pprz''' unit is used as a normalized internal unit for input and output values of the '''control_laws''' block.&lt;br /&gt;
&lt;br /&gt;
== Navigation loop ==&lt;br /&gt;
&lt;br /&gt;
The navigation loop is located in '''sw/airborne/subsystems/nav.*'''. The navigation routines are called from the [[Flight Plans]]. Advanced navigation routines are in '''sw/airborne/subsystems/navigation/'''.&lt;br /&gt;
&lt;br /&gt;
== Course loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_course_loop.png|Course loop]]&lt;br /&gt;
&lt;br /&gt;
The course loop is the upper stage of the horizontal control.&lt;br /&gt;
It is located in '''sw/airborne/firmwares/fixedwing/stabilization/stabilization_attitude.c''' (formerly fw_h_ctl.c).&lt;br /&gt;
&lt;br /&gt;
== Roll loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_roll_loop.png|Roll loop]]&lt;br /&gt;
&lt;br /&gt;
The roll loop is the lower stage of the horizontal control and is used for lateral attitude stabilization. It is located in '''stabilization_attitude.c'''.&lt;br /&gt;
If &amp;lt;tt&amp;gt;H_CTL_ROLL_ATTITUDE_GAIN&amp;lt;/tt&amp;gt; is undefined, the code will fallback to a attitude-only loop, where &amp;lt;tt&amp;gt;estimator_p&amp;lt;/tt&amp;gt; is disregarded and the gain for &amp;lt;tt&amp;gt;estimator_phi&amp;lt;/tt&amp;gt; is &amp;lt;tt&amp;gt;H_CTL_ROLL_PGAIN&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Note; estimator_phi is the measured roll angle, and estimator_p is the measured rate of change in roll angle.&lt;br /&gt;
&lt;br /&gt;
== Altitude loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_altitude_loop.png|Altitude loop]]&lt;br /&gt;
&lt;br /&gt;
The altitude loop is the upper stage of the vertical control.&lt;br /&gt;
It is located in '''sw/airborne/firmwares/fixedwing/guidance/guidance_v.c''' (formerly fw_v_ctl.c)&lt;br /&gt;
If AGR_CLIMB is defined in the airframe file, the altitude loop also sets the v_ctl_auto_throttle_submode for use in the climb loop.&lt;br /&gt;
&lt;br /&gt;
== Auto Throttle and Auto Pitch climb loops ==&lt;br /&gt;
&lt;br /&gt;
Two climb loops are available. The are called from the [[Flight Plans#Navigation_modes|flight plan]] by changing the vertical navigation mode. The default mode is '''Auto Throttle'''. The '''Auto Pitch''' loop is only available if '''V_CTL_AUTO_PITCH_PGAIN''' is defined. Only one loop is active at a time. Note also that if '''USE_AIRSPEED''' is defined, then the Auto Throttle loop is replaced by the Auto Airspeed loop, see [Control_Loops#Control_loops_using_Airspeed_Sensor|below].&lt;br /&gt;
&lt;br /&gt;
=== Auto throttle loop ===&lt;br /&gt;
[[Image:Diagram_auto_throttle_loop.png|Auto Throttle climb loop]]&lt;br /&gt;
&lt;br /&gt;
If '''AGR_CLIMB''' is defined, then the auto throttle submode is used to determine setpoint outputs. This may be the standard control loop outputs, the aggressive outputs (static setpoints defined in airframe file) or a blend of both.&lt;br /&gt;
&lt;br /&gt;
=== Auto pitch loop ===&lt;br /&gt;
[[Image:Diagram_auto_pitch_loop.png|924px|Auto Pitch climb loop]]&lt;br /&gt;
&lt;br /&gt;
The climb loop is the intermediate stage of the vertical control. It is located in '''guidance_v.c'''.&lt;br /&gt;
&lt;br /&gt;
== Pitch loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_pitch_loop.png|Pitch loop]]&lt;br /&gt;
&lt;br /&gt;
The pitch loop is the lower stage of the vertical control and is used for longitudinal attitude stabilization. It is located in '''stabilization_attitude.c'''.&lt;br /&gt;
The first sum block of the diagram is not completely accurate. The input to the pitch stabilization loop is h_ctl_pitch_setpoint, though v_ctl_pitch_of_vz is not a direct input. Rather h_ctl_pitch_setpoint is assigned in the main autopilot loop from nav_pitch, in general (in auto1, it is assigned directly from the pitch r/c input). The nav_pitch value is obtained in a few ways, depending on which control loop(s) are active. If auto throttle is active, nav_pitch is the sum of v_ctl_pitch_of_vz and a fixed setpoint defined using the pitch attribute in the flightplan. If AGR_CLIMB is set, nav_pitch is either the airframe file defined ascent and descent pitch setpoints, the standard sum, or a blend of each. If auto pitch is active, nav_pitch is defined directly from the output of that loop. If airspeed is active, nav_pitch is defined in the auto airspeed pitch loop.&lt;br /&gt;
&lt;br /&gt;
== Control loops using Airspeed Sensor ==&lt;br /&gt;
&lt;br /&gt;
Adding an airspeed sensor measures actual airspeed resulting in better throttle control and aircraft performance especially in windy conditions. The use of an airspeed sensor is described [[Airspeed_sensor|here]].&lt;br /&gt;
&lt;br /&gt;
[[Image:Diagram_auto_airspeed_loop.png|Auto Airspeed climb loop]]&lt;br /&gt;
&lt;br /&gt;
The auto airspeed cascaded control loops control both pitch and throttle. This control loop set replaces the Auto Throttle climb loop; it is engaged in the same manner in the flight plan. It is located in '''guidance_v.c'''.&lt;br /&gt;
&lt;br /&gt;
= Rotorcraft autopilot =&lt;br /&gt;
&lt;br /&gt;
The schemes of the multi-rotor autopilot were made with the drawing tool from Google docs. To edit the drawings, send an e-mail to microuav@gmail.com.&lt;br /&gt;
&lt;br /&gt;
== Global View ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_autopilot_globalview.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this autopilot is located in '''sw/airborne/firmwares/rotorcraft'''.&lt;br /&gt;
&lt;br /&gt;
== Vertical Control ==&lt;br /&gt;
&lt;br /&gt;
Depending on the general mode selected, one of the following vertical modes is used.&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_V_MODE_RC_CLIMB ===&lt;br /&gt;
[[File:Rc_climb.png]]&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_V_MODE_CLIMB ===&lt;br /&gt;
[[File:Climb.png]]&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_V_MODE_HOVER ===&lt;br /&gt;
[[File:Z_hold.png]]&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_V_MODE_NAV ===&lt;br /&gt;
&lt;br /&gt;
== Reference generators ==&lt;br /&gt;
&lt;br /&gt;
=== from z set point ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Refgen_from_z_sp.png]]&lt;br /&gt;
&lt;br /&gt;
=== from z dot set point ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_refgen_zdot.png]]]&lt;br /&gt;
&lt;br /&gt;
The '''adjust accel''' is a simple algorithm to set acceleration to zero when velocity reaches boundaries.&lt;br /&gt;
&lt;br /&gt;
The code for these reference generators is located in '''guidance/guidance_v_ref.h'''&lt;br /&gt;
&lt;br /&gt;
== Vertical loop ==&lt;br /&gt;
[[File:vertical_loop.png]]&lt;br /&gt;
&lt;br /&gt;
the source code is located in '''guidance\guidance_v.c'''&lt;br /&gt;
&lt;br /&gt;
INV_M is basically the inverse of the mass. Since m.g=thrust when hovering in RC Direct mode, it can be calculated by INV_M=9.81/(thrust). (thrust message[0-256] in ROTORCRAFT_FP)&lt;br /&gt;
&lt;br /&gt;
if you specify INV_M, it will be used instead of the observer for the adaptive control (so in most cases it makes more sense to not specify this explicitly and use the adaptive controller instead)&lt;br /&gt;
the adaptative controller code is located in '''guidance\guidance_v_adpt.h'''&lt;br /&gt;
&lt;br /&gt;
== Horizontal Control ==&lt;br /&gt;
&lt;br /&gt;
Depending on the general mode selected, one of the following horizontal modes is used.&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_H_MODE_RATE ===&lt;br /&gt;
[[Image:GUIDANCE_H_MODE_RATE.png]]&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_H_MODE_ATTITUDE ===&lt;br /&gt;
[[Image:GUIDANCE_H_MODE_ATTITUDE.png]]&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_H_MODE_HOVER ===&lt;br /&gt;
&lt;br /&gt;
When this mode is entered, the measured position at the instance of initiation is set as guidance_h_pos_sp. This means that the rotorcraft will hover on that position.&lt;br /&gt;
&lt;br /&gt;
[[Image:GUIDANCE_H_MODE_HOVER.png]]&lt;br /&gt;
&lt;br /&gt;
rotation to body:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;\phi_{cmd_{body}}= -\sin \psi \cdot x_{cmd_{earth}} + \cos \psi \cdot y_{cmd_{earth}} &amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;math&amp;gt;\theta_{cmd_{body}}= -\left( \cos \psi \cdot x_{cmd_{earth}} + \sin \psi \cdot y_{cmd_{earth}} \right) &amp;lt;/math&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== mode: GUIDANCE_H_MODE_NAV ===&lt;br /&gt;
&lt;br /&gt;
The set points guidance_h_pos_sp (x and y coordinates) are obtained from the navigation carrot after a 'NED of ENU' transformation:&lt;br /&gt;
&lt;br /&gt;
guidance_h_pos_sp.x = navigation_carrot.y&lt;br /&gt;
&lt;br /&gt;
guidance_h_pos_sp.y = navigation_carrot.x&lt;br /&gt;
&lt;br /&gt;
[[Image:GUIDANCE_H_MODE_NAV.png]]&lt;br /&gt;
&lt;br /&gt;
Rotation to body is the same as in GUIDANCE_H_MODE_HOVER.&lt;br /&gt;
&lt;br /&gt;
== Reference generators ==&lt;br /&gt;
&lt;br /&gt;
=== from euler attitude angle set point ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_refgen_att.png]]&lt;br /&gt;
&lt;br /&gt;
Acceleration is set to zero when rate reaches min or max value.&lt;br /&gt;
&lt;br /&gt;
The code for this reference generator is located in '''stabilization/stabilization_attitude_ref_euler_int.c'''.&lt;br /&gt;
&lt;br /&gt;
=== from angular rate set point ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_refgen_rate.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this reference generator is located in '''stabilization/stabilization_rate.c'''.&lt;br /&gt;
&lt;br /&gt;
=== from pos set point ===&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_refgen_xy_sp.png]]&lt;br /&gt;
&lt;br /&gt;
Acceleration is set to zero when rate reaches min or max value.&lt;br /&gt;
&lt;br /&gt;
The code for this reference generator is located in '''guidance/guidance_h_ref.h'''.&lt;br /&gt;
&lt;br /&gt;
== Attitude loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:attitude_loop.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this loop is located in '''stabilization/stabilization_attitude_euler_int.c'''.&lt;br /&gt;
&lt;br /&gt;
== Rate loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:rate_loop.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this loop is located in '''stabilization/stabilization_rate.c'''.&lt;br /&gt;
&lt;br /&gt;
== Guidance horizontal hover loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:guidance_horizontal_hover.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this loop is located in '''guidance/guidance_h.c'''.&lt;br /&gt;
&lt;br /&gt;
== Guidance horizontal navigation loop ==&lt;br /&gt;
&lt;br /&gt;
[[Image:Booz_horizontal_nav.png]]&lt;br /&gt;
&lt;br /&gt;
The code for this loop is located in '''guidance/guidance_h.c'''&lt;br /&gt;
&lt;br /&gt;
(to be developed later..)&lt;br /&gt;
&lt;br /&gt;
Integral action or tracking algorithm:&lt;br /&gt;
&lt;br /&gt;
if (|guidance_h_pos_err| &amp;lt; HOLD_DISTANCE) -&amp;gt; intregal error * guidance_h_igain&lt;br /&gt;
&lt;br /&gt;
else -&amp;gt; path tracking error * guidance_h_ngain&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]] [[Category:Developer_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Tuning&amp;diff=11931</id>
		<title>Tuning</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Tuning&amp;diff=11931"/>
		<updated>2012-03-09T13:10:12Z</updated>

		<summary type="html">&lt;p&gt;Rufus: fixed link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;This page provides some tips and guidelines for tuning a new aircraft. Be sure to familiarize yourself with the theory of [[Theory_of_Operation#PID|PID Controllers]] before you begin. Use of the [[RTPlotter|real time plotter]] may help to visualize and understand the behavior of the control loops. Review [http://paparazzi.enac.fr/w/images/Users_manual.pdf User Manual] as well. Also reading [[http://www.av8n.com/how/ See How It Flies, by John S. Denker]] is very beneficial to get your airframe tuned well.&lt;br /&gt;
&lt;br /&gt;
== Sensors ==&lt;br /&gt;
&lt;br /&gt;
=== Neutrals ===&lt;br /&gt;
* Put the aircraft in a styrofoam container or completely seal the IR sensors with styrofoam or similar blocks and get a reading of the neutrals for each axis.  Also take the gyro neutrals at this time.  Update your airframe file, flash the AP and re-check the neutrals.&lt;br /&gt;
&lt;br /&gt;
Using the roll gyro as a worked example: Run up your GCS and ensure it &lt;br /&gt;
is communicating with your airframe. Make sure your airframe is roughly &lt;br /&gt;
level and that it cannot move. Now run the Messages Tool and the [[RTPlotter|real time plotter]] tool. The messages tool will have lots of flashing lights &lt;br /&gt;
indicating when it receives various telemetry packets.  In the Messages &lt;br /&gt;
tool, Click on Gyro Rates and you should see a list of variables.  Click &lt;br /&gt;
on Roll_ADC and drag and drop in onto the main window of the Real Time plotter.  Now give it a while to build a stable graph.&lt;br /&gt;
&lt;br /&gt;
Once things have been running this way for a while, in the Real Time &lt;br /&gt;
Plotter, click on Curves in the menu and select the &lt;br /&gt;
1:telemetry:GYRO_RATES:Roll_ADC entry.  As you select it, you should see &lt;br /&gt;
the average and standard deviation values.  We need the average value.  &lt;br /&gt;
Jot down the number you have.  I have -24.536.&lt;br /&gt;
&lt;br /&gt;
Now go edit your airframe file and look for the ADC_ROLL_NEUTRAL value. &lt;br /&gt;
In my airframe file the value is 520.  As my average value from the Plotter is a &lt;br /&gt;
negative figure, it indicates that the roll Neutral is too high, subtract the average value from the present setting. So I edited my airframe file to be 495.464 (520-24.536).&lt;br /&gt;
&lt;br /&gt;
Recompile and reflash (Don't worry about restarting the GCS, The &lt;br /&gt;
messages program or the other running processes - they will catch up just &lt;br /&gt;
fine after flashing).  Once the Board is back up and the plotter continues, reset it from the menu to get rid of the average. Watch it for a while and check that the line and acculmulated average is on or around 0. You are done.  Use the same process for the IR sensors!&lt;br /&gt;
&lt;br /&gt;
=== Directions ===&lt;br /&gt;
* Reverse any servos and make sure no mechanical binding occurs at the limits of travel in Manual mode.&lt;br /&gt;
* Take the plane outside and engage AUTO1.  Bank and pitch the plane and verify that the controls respond in the correct direction AND that the PFD in the notebook responds correctly.  Note that your body will have a tremendous impact on the measured angles if using IR sensors. If using an IMU, there is no need to be outside. See note.&lt;br /&gt;
* Verify that AUTO1 stick movements respond in the correct direction - important! See note.&lt;br /&gt;
* Move the plane rapidly to ensure the gyro response resists motion - increase the gain if needed for better visualization.&lt;br /&gt;
NOTE: If the PFD responds in the wrong direction to the motion, you should adjust parameters in the INFRARED or IMU parts of the airframe file. If the control surfaces respond in the wrong direction to counteract motion (stabilize the aircraft, bring it back to neutral), reverse the servos in the airframe file. If the manual input from R/C causes the control surfaces to respond in the wrong direction (want them to force motion, not counteract motion), then you must reverse the channel on the R/C transmitter. Be sure to recheck surface neutrals and endpoints after doing such modifications. Also double check the gain signs, make sure none are positive that should be negative.&lt;br /&gt;
&lt;br /&gt;
== R/C, Modem, and GPS ==&lt;br /&gt;
* Make sure the GPS signal is strong (outdoors) - you should have a 3-D fix in less than 1 minute and at least some satellite signals above 40dB. The plane should not drift on the map by more than 10 meters.&lt;br /&gt;
* Perform a range test of R/C and modem signals.&lt;br /&gt;
* Ensure that two way communications are in place. Check that the motor starts up when launch is commanded or move a waypoint and check that it's updated in the autopilot.&lt;br /&gt;
&lt;br /&gt;
== Trim ==&lt;br /&gt;
&amp;lt;b&amp;gt;Important: You must never keep any trim, mixers, or rates in your R/C transmitter.&amp;lt;/b&amp;gt;  R/C trim can be applied in flight but must be corrected and removed on the ground before attempting autonomous flight.  Exponential can be useful and will not adversely affect AUTO1 flight but if &amp;quot;low rates&amp;quot; are needed they should be programmed on the same transmitter switch with AUTO1 so that you always have full travel in AUTO1.&lt;br /&gt;
* Fly the plane at what you feel is a suitable &amp;quot;cruise&amp;quot; throttle setting and set the trims.  Note that setting in the GCS and try to return to that exact setting in subsequent tests.  Enter that throttle setting in your airframe file.&lt;br /&gt;
* Check maximum pitch and roll response and adjust the mixer parameters or mechanical linkages after landing.&lt;br /&gt;
* Land and adjust the linkages.  If necessary, the PPM values can be read from the GCS and servo neutrals adjusted electronically, but manual adjustment will produce far better results.&lt;br /&gt;
* Fly again to verify trim and control response.  If satisfactory, check for any significant throttle-dependent roll.  Again, this is best to correct mechanically but can be addressed with the ''AILERON_OF_THROTTLE'' mixer in the autopilot.  Check also for any odd behavior at full throttle.&lt;br /&gt;
* Make sure that GPS and modem data is reliable during these test flights. Note particularly any tendency for the aircraft to appear to fly sideways on the map - this is an indication of weak GPS signals.&lt;br /&gt;
&lt;br /&gt;
== Auto 1 ==&lt;br /&gt;
* Engage Auto1 and ''immediately'' make sure you can turn both left and right!&lt;br /&gt;
* Fly at your &amp;quot;cruise&amp;quot; throttle and adjust the ''ROLL_PGAIN'' until the plane doesn't quite oscillate&lt;br /&gt;
* Adjust the IR roll neutral as needed&lt;br /&gt;
* Verify adequate pitch response and adjust PITCH_PGAIN as needed&lt;br /&gt;
* Experiment with different throttle settings and tune P and D gains as needed&lt;br /&gt;
&lt;br /&gt;
If you are alone in the field while tuning, setting values via your RC transmitter may come in handy, see http://paparazzi.enac.fr/wiki/Telemetry#R.2FC_Transmitter_Data_Uplink&lt;br /&gt;
&lt;br /&gt;
== Auto 2 ==&lt;br /&gt;
* Engage Auto2 and you're done!&lt;br /&gt;
&lt;br /&gt;
==Alternate Tuning Procedure==&lt;br /&gt;
Danstah wrote up a tuning procedure on this website http://www.engr.usu.edu/wiki/index.php/OSAMtuning&lt;br /&gt;
&lt;br /&gt;
==Sample/Simple Altitude and Throttle Loop==&lt;br /&gt;
&lt;br /&gt;
The dash button changes the NOMINAL_CRUISE_THROTTLE to the MAX_CRUISE_THROTTLE while the loiter button changes it to MIN_CRUISE_THROTTLE. &lt;br /&gt;
&lt;br /&gt;
This makes it easy to suddenly make the UAV fly a bit slower or a bit faster. However, when chaging the throttle, you also need to change the elevator trim in order not to climb/descend too much. This it what AUTO_THROTTLE_LOITER_TRIM and AUTO_THROTTLE_DASH_TRIM are for. (I think the unit is MAX_PPRZ = 9600 = full deflection?) &lt;br /&gt;
&lt;br /&gt;
The auto-throttle loop is actually the most difficult loop to tune as it has both the speed and altitude that are correlated. Controlling both speed and altitude with high performance is very hard. It is way easier to control 1 entity (e.g. altitude) with higher performance and let the speed change a bit, or have an airspeed controller but then do the altitude slowly... &lt;br /&gt;
&lt;br /&gt;
Sample altitude controller:&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
Step1: outerloop: if altitude is not good -&amp;gt; compute a climb/descend rate. (including MAX_CLIMB)&lt;br /&gt;
&lt;br /&gt;
  climb_command = altitude_error x alt_pgain&lt;br /&gt;
&lt;br /&gt;
e.g. 10 m too low x 0.1 alt gain = climb_command at 1 m/s&lt;br /&gt;
e.g. 50 m too low x 0.1 alt gain = climb at 5 m/s &amp;gt; MAX_CLIMB(2) -&amp;gt; climb_command = 2m/s&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
Step2: innerloop: [many many options here, but since you ask for simple I'll only give one robust and simple:]&lt;br /&gt;
&lt;br /&gt;
too low -&amp;gt; pitch up and extra throttle (if you only apply throttle, airspeed will increase and might even start to dive with full throttle if the nose is a bit heavy, if you only apply pitch airspeed will decrease and could lead to stall, with proper tuning you can get a pretty constant speed even while climbing and descending) &lt;br /&gt;
&lt;br /&gt;
  pitch_command = climb_command x pitch_of_vz&lt;br /&gt;
  throttle_command = nominal_cruise_trim_throttle + climb_command x throttle_climb_increment&lt;br /&gt;
&lt;br /&gt;
e.g. climb_command at 1 m/s x pitch_of_vz 0.15 = 0.15 radians pitch = 9 degrees pitch up&lt;br /&gt;
&lt;br /&gt;
e.g. climb_command at 1 m/s x throttle_climb_increment 0.25 with nominal_cruise_trim_throttle 0.5 = 75% throttle&lt;br /&gt;
&lt;br /&gt;
-------------------&lt;br /&gt;
&lt;br /&gt;
If you use AGRESSIVE_CLIMB then if the altitude error is larger than the chosen threshold a precomputed pitch and throttle will be applied. &lt;br /&gt;
&lt;br /&gt;
AUTO_PITCH is for constant throttle and control height with elevator only&lt;br /&gt;
&lt;br /&gt;
auto_throttle_p/i/d_gains are to regulate the climb rate more precisely&lt;br /&gt;
&lt;br /&gt;
==Other Misc things before flying==&lt;br /&gt;
It's very important to address the issue of low voltage cut-off before flying. There's a good chance that the LVC will kick in on the brushless ESC before the Paparazzi detects it. If this happens, the ESC cut's off throttle, and there's no way the autopilot knows this, the plane keeps loosing altitude, the autopilot tries to increase throttle, but the ESC does not respond, almost always leading to a mishap. To avoid this, either turn off the LVC on the ESC, OR, make sure the autopilot kills throttle first, by programming the CATASTROPHIC_BAT_LEVEL to something higher than the ESC LVC. For example, set CATASTROPHIC_BAT_LEVEL to 9.5V, and the ESC LVC at 9V. Don't ask how we know, it was a safe landing into a small tree :) No damage. BUT you cant get lucky always!&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Flight_Plans&amp;diff=10896</id>
		<title>Flight Plans</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Flight_Plans&amp;diff=10896"/>
		<updated>2011-12-08T23:17:05Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Introduction */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
A '''flight plan''' is a XML document which one can create and store aboard an autopilot. The flight plan will describe how you want your aircraft to travel if released into into the wild blue yonder.&lt;br /&gt;
&lt;br /&gt;
== DTD ==&lt;br /&gt;
&lt;br /&gt;
The formal description of the flight plan file is given in the [http://en.wikipedia.org/wiki/Document_Type_Definition '''DTD'''] (located in &amp;lt;tt&amp;gt;conf/flight_plans/flight_plan.dtd&amp;lt;/tt&amp;gt;). This&lt;br /&gt;
DTD must be referenced in the header of your flight plan XML document using the following line:&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;!DOCTYPE flight_plan SYSTEM &amp;quot;flight_plan.dtd&amp;quot;&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The flight plans are stored in the &amp;lt;tt&amp;gt;conf/flight_plans&amp;lt;/tt&amp;gt; directory. The [[Flight_Plan_Editor|flight plan editor]] can be used to create basic flight plans via the GUI.&lt;br /&gt;
&lt;br /&gt;
== Structure==&lt;br /&gt;
&lt;br /&gt;
Extract from the [http://en.wikipedia.org/wiki/Document_Type_Definition DTD]:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;!ELEMENT flight_plan (header?,waypoints,sectors?,include*,exceptions?,blocks)&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A flight plan is composed of two mandatory elements: [[#waypoints|waypoints]] and [[#blocks|blocks]]&lt;br /&gt;
&lt;br /&gt;
The root &amp;lt;tt&amp;gt;flight_plan&amp;lt;/tt&amp;gt; element is specified with several attributes:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;flight_plan name lat0 lon0 ground_alt security_height qfu alt max_dist_from_home&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
* &amp;lt;tt&amp;gt;name&amp;lt;/tt&amp;gt;: the name of the mission (a text string)&lt;br /&gt;
* &amp;lt;tt&amp;gt;lat0, lon0&amp;lt;/tt&amp;gt;: describe the latitude and longitude of the point {0,0} in WGS84 degree coordinates&lt;br /&gt;
* &amp;lt;tt&amp;gt;ground_alt&amp;lt;/tt&amp;gt;: the ground altitude (in meters). It defines the &amp;lt;tt&amp;gt;GROUND_ALT&amp;lt;/tt&amp;gt; constant value which can be used to define waypoint altitudes&lt;br /&gt;
* &amp;lt;tt&amp;gt;security_height&amp;lt;/tt&amp;gt;:  the altitude used by the circle-home failsafe procedure&lt;br /&gt;
* &amp;lt;tt&amp;gt;qfu&amp;lt;/tt&amp;gt; (optional): defines the global constant &amp;lt;tt&amp;gt;QFU&amp;lt;/tt&amp;gt;. It usually is the magnetic heading in degrees (north=0, east=90) of the runway, the opposite of wind direction. This constant may be used in the mission description. It is also used by the simulator as the original course of the aircraft. So if you want to take off and climb to the West you would use qfu=270. &lt;br /&gt;
* &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt;: the default altitude of waypoints (Above Sea Level). So if your ground altitude is 400 then alt needs to be a value greater than ground altitude and above any obstructions in the flight plan. &lt;br /&gt;
* &amp;lt;tt&amp;gt;max_dist_from_home&amp;lt;/tt&amp;gt;: the maximum allowed distance (in meters) from the HOME waypoint. Exceeding this value will trigger an exception.&lt;br /&gt;
&lt;br /&gt;
Here is an example of the first line of a flight plan:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tt&amp;gt;&lt;br /&gt;
  &amp;lt;flight_plan name=&amp;quot;Example Muret&amp;quot;&lt;br /&gt;
   lat0=&amp;quot;43.46223&amp;quot; lon0=&amp;quot;1.27289&amp;quot; max_dist_from_home=&amp;quot;300&amp;quot; qfu=&amp;quot;270&amp;quot;&lt;br /&gt;
   ground_alt=&amp;quot;185&amp;quot; security_height=&amp;quot;25&amp;quot; alt=&amp;quot;250&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that a flight plan could also contain optional &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt;'s and &amp;lt;tt&amp;gt;exceptions&amp;lt;/tt&amp;gt; cases.&lt;br /&gt;
&lt;br /&gt;
=== Waypoints ===&lt;br /&gt;
&lt;br /&gt;
The waypoints are the geographic locations used to specify the trajectories. A waypoint is specified by it's name and coordinates:&lt;br /&gt;
 &amp;lt;tt&amp;gt; &amp;lt;waypoint name x y [alt] [height]/&amp;gt; &amp;lt;/tt&amp;gt;&lt;br /&gt;
where '''x''' and '''y''' are real positional coordinates, '''or''' relative coordinates in meters from your reference point {0,0} .  &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;height&amp;lt;/tt&amp;gt; are optional parameters and can be used to assign an altitude to a particular waypoint that is different from the globally defined &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt; parameter of the flightplan. To set the waypoint altitude relative to the ground altitude (&amp;lt;tt&amp;gt;ground_alt&amp;lt;/tt&amp;gt;) of the flight plan for this waypoint, use the &amp;lt;tt&amp;gt;height&amp;lt;/tt&amp;gt; attribute instead of &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
An example:&lt;br /&gt;
&amp;lt;tt&amp;gt;&lt;br /&gt;
 &amp;lt;waypoints&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;HOME&amp;quot; x=&amp;quot;0.0&amp;quot; y=&amp;quot;30.0&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;BRIDGEOVERRIVER&amp;quot; x=&amp;quot;-100.0&amp;quot; y=&amp;quot;60.0&amp;quot; alt=&amp;quot;270.&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;MyBarn&amp;quot; x=&amp;quot;-130.0&amp;quot; y=&amp;quot;217.5&amp;quot; alt=&amp;quot;3000.&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;3&amp;quot; x=&amp;quot;-30.0&amp;quot; y=&amp;quot;50&amp;quot; height=&amp;quot;50.&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;4&amp;quot; x=&amp;quot;-30.0&amp;quot; y=&amp;quot;50.&amp;quot; alt=&amp;quot;ground_alt + 50&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;waypoint name=&amp;quot;_MYHELPERSPOT&amp;quot; x=&amp;quot;-30.0&amp;quot; y=&amp;quot;60&amp;quot; height=&amp;quot;50.&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/waypoints&amp;gt;&lt;br /&gt;
&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tips'''&lt;br /&gt;
* Waypoints are easily adjusted with the [[Flight_Plan_Editor|flight plan editor]].&lt;br /&gt;
* If a waypoint name starts with an underscore, the waypoint is not displayed in the GCS, except in editor mode.&lt;br /&gt;
* The maximum number of waypoints is 254.&lt;br /&gt;
* A waypoint named &amp;lt;tt&amp;gt;HOME&amp;lt;/tt&amp;gt; is required if the failsafe HOME mode procedure are used.&lt;br /&gt;
&lt;br /&gt;
=== Sectors ===&lt;br /&gt;
&lt;br /&gt;
Flat ''Sectors'' can be described as an area defined by list of waypoint corners. Such an area will be displayed in the Ground Control Station (GCS) by colored lines.&lt;br /&gt;
A function is generated to check if a point, usually the aircraft itself, is ''inside'' this sector. Currently, this feature requires that the polygon is &amp;lt;b&amp;gt;convex&amp;lt;/b&amp;gt; and described in a &amp;lt;b&amp;gt;clockwise&amp;lt;/b&amp;gt; order. For a sector named &amp;lt;tt&amp;gt;sector&amp;lt;/tt&amp;gt;. Note that sector names are not allowed to contain spaces. The generated function is &amp;lt;tt&amp;gt;bool_t InsideSector(float x, float y);&amp;lt;/tt&amp;gt; where &amp;lt;tt&amp;gt;x&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;y&amp;lt;/tt&amp;gt; are east and north coordinated, in meters, relative to the geographic reference of the flight plan. If the flight plan is dynamically relocated, such a sector will be relocated but the display is currently not updated on the GCS. It would be great if one would help improving that part of the source code.&lt;br /&gt;
&lt;br /&gt;
For example, with the following element in a flight plan.&lt;br /&gt;
 &amp;lt;tt&amp;gt;&lt;br /&gt;
 &amp;lt;sectors&amp;gt;&lt;br /&gt;
  &amp;lt;sector name=&amp;quot;Muret&amp;quot; color=&amp;quot;red&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;corner name=&amp;quot;_1&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;corner name=&amp;quot;_2&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;corner name=&amp;quot;_3&amp;quot;/&amp;gt;&lt;br /&gt;
   &amp;lt;corner name=&amp;quot;_4&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/sector&amp;gt;&lt;br /&gt;
 &amp;lt;/sectors&amp;gt;&lt;br /&gt;
 &amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is then possible to write a exception. For example if the aircraft for some reason flies outside this sector the airframe will fly to a standby waypoint. The exclamation mark (!) means the boolean operator &amp;lt;tt&amp;gt;NOT&amp;lt;/tt&amp;gt; in this example. In regular language one would describe &amp;quot;If my airframe is NOT inside the Murret sector anymore then deroute it to the standby waypoint.&amp;quot; In Flightplan &amp;quot;Speak&amp;quot; this is written like: &lt;br /&gt;
&amp;lt;tt&amp;gt;&lt;br /&gt;
 &amp;lt;exception cond=&amp;quot;! InsideMuret(estimator_x, estimator_y)&amp;quot; deroute=&amp;quot;standby&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Tips'''&lt;br /&gt;
* A nice option in the corner notation is that one can add an underscore in front of the name; a corner or waypoint name that starts with an underscore is not displayed in the GCS. Only in editor mode it is visible, otherwise it would be not possible to edit or drag the corner or waypoint.&lt;br /&gt;
* The color of the sector is not fixed but can be defined by oneself if wished for via the color attribute.&lt;br /&gt;
&lt;br /&gt;
=== Includes ===&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; is used to add some flight plan elements defined in an external procedure. It’s useful to include pre-written procedures with only few arguments and then clarify the flight plan.&lt;br /&gt;
Here is the structure:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;include name procedure&amp;gt; [&amp;lt;arg name value /&amp;gt;]*[&amp;lt;with from to /&amp;gt;]*&amp;lt;/include&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
where &amp;lt;tt&amp;gt;name&amp;lt;/tt&amp;gt; attribute of the include element will be used in this flight plan to prefix the blocks of the &amp;lt;tt&amp;gt;procedure&amp;lt;/tt&amp;gt;, the XML referenced file.&lt;br /&gt;
Named arguments may be given with their value in the &amp;lt;tt&amp;gt;arg&amp;lt;/tt&amp;gt; elements. The &amp;lt;tt&amp;gt;with&amp;lt;/tt&amp;gt; tag allows to link labels (e.g. attribute of a deroute instruction or of an exception) from the procedure to blocks of the main flight plan.&lt;br /&gt;
Then, each block of the procedure is like any block of the flight plan and is designated with a dotted identifier: block &amp;lt;tt&amp;gt;b&amp;lt;/tt&amp;gt; of a procedure named &amp;lt;tt&amp;gt;p&amp;lt;/tt&amp;gt; is named &amp;lt;tt&amp;gt;b.p&amp;lt;/tt&amp;gt; .&lt;br /&gt;
&lt;br /&gt;
Here is an example:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&lt;br /&gt;
 &amp;lt;includes&amp;gt;&lt;br /&gt;
   &amp;lt;include name=&amp;quot;landing&amp;quot; procedure=&amp;quot;landing.xml&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/includes&amp;gt;&lt;br /&gt;
 &amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Blocks ===&lt;br /&gt;
&lt;br /&gt;
Block elements are the main part of a flight plan: they describe each unit of the mission.&lt;br /&gt;
They are made of various primitives, called stages and exceptions, you can put one after the other. When a&lt;br /&gt;
stage (or a block) is finished, the autopilot goes to the next one. The behaviour after the last stage of the last block is undefined.&lt;br /&gt;
&lt;br /&gt;
As described in the DTD, the &amp;lt;tt&amp;gt;blocks&amp;lt;/tt&amp;gt; element is composed of &amp;lt;tt&amp;gt;block&amp;lt;/tt&amp;gt; elements which are sequence of ''stages'':&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;!ELEMENT blocks (block+)&amp;gt;&lt;br /&gt;
 &amp;lt;!ELEMENT block (exception|while|heading|attitude|go|xyz|set|circle|deroute|stay|follow&lt;br /&gt;
                           |survey_rectangle)*&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block name=&amp;quot;circlehome&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;circle radius=&amp;quot;75&amp;quot; wp=&amp;quot;HOME&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/block&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can add a button in the [[GCS#Strips|strip of the aircraft]] with the attribute &amp;lt;tt&amp;gt;strip_button&amp;lt;/tt&amp;gt;:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block name=&amp;quot;descent&amp;quot; strip_button=&amp;quot;Descent&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp=&amp;quot;HOME&amp;quot; throttle=&amp;quot;0.0&amp;quot; pitch=&amp;quot;-15&amp;quot; vmode=&amp;quot;throttle&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/block&amp;gt; &amp;lt;/tt&amp;gt;&lt;br /&gt;
This button will activate the block. If the attribute &amp;lt;tt&amp;gt;group&amp;lt;/tt&amp;gt; is specified, all strip buttons of the same group will be placed vertically on top of each other.&lt;br /&gt;
&lt;br /&gt;
In the same way, a key shortcut can be specified:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block key=&amp;quot;D&amp;quot; name=&amp;quot;descent&amp;quot; strip_button=&amp;quot;Descent&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp=&amp;quot;HOME&amp;quot; throttle=&amp;quot;0.0&amp;quot; pitch=&amp;quot;-15&amp;quot; vmode=&amp;quot;throttle&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/block&amp;gt; &amp;lt;/tt&amp;gt;&lt;br /&gt;
Modifiers are allowed, using the syntax of [http://library.gnome.org/devel/gtk/2.15/gtk-Keyboard-Accelerators.html#gtk-accelerator-parse GTK accelerators].&lt;br /&gt;
&lt;br /&gt;
An icon can be specified to display the button. The &amp;lt;tt&amp;gt;strip_button&amp;lt;/tt&amp;gt; label then is a tooltip for the icon. The icon must be an image file available in the directory &amp;lt;tt&amp;gt;data/pictures/gcs_icons&amp;lt;/tt&amp;gt;:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block name=&amp;quot;Takeoff&amp;quot; strip_icon=&amp;quot;takeoff.png&amp;quot; strip_button=&amp;quot;Takeoff&amp;quot;&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can call functions before or after each execution of the block:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block name=&amp;quot;circlehome&amp;quot; pre_call=&amp;quot;function_to_call_before_circle()&amp;quot; post_call=&amp;quot;function_to_call_after_circle()&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp=&amp;quot;HOME&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/block&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===== Expressions =====&lt;br /&gt;
&lt;br /&gt;
Most of the numeric attributes in stages are analyzed as C expressions. The syntax of this C expression is restricted to &lt;br /&gt;
* numeric constants&lt;br /&gt;
* some internal autopilot variables (not fully documented, see examples)&lt;br /&gt;
* Some binary operators: &amp;lt;, &amp;gt;, &amp;lt;=, &amp;gt;=, &amp;lt;&amp;gt;, ==, +, -, /, *&lt;br /&gt;
* Some utility functions&lt;br /&gt;
&lt;br /&gt;
Some examples of usable expressions are given in the next sections.&lt;br /&gt;
&lt;br /&gt;
==== Exceptions ====&lt;br /&gt;
&lt;br /&gt;
The flight manager can handle exceptions. They consist in conditions checked periodically (at the same pace as the navigation control), allowing the control to jump to a given block. Here is the syntax of exceptions:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;exception cond=&amp;quot;...&amp;quot; deroute=&amp;quot;...&amp;quot;&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
where &amp;lt;tt&amp;gt;cond&amp;lt;/tt&amp;gt; is an expression and &amp;lt;tt&amp;gt;deroute&amp;lt;/tt&amp;gt; is the name of the block we want to switch to as soon as the condition is true.&lt;br /&gt;
&lt;br /&gt;
Here are some example of exceptions:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;exception cond=&amp;quot;10 &amp;gt; PowerVoltage()&amp;quot; deroute=&amp;quot;go_down&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;exception cond=&amp;quot;(ground_alt+10 &amp;gt; estimator_z)&amp;quot; deroute=&amp;quot;go_up&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;exception cond=&amp;quot;(estimator_flight_time &amp;gt; 840)&amp;quot; deroute=&amp;quot;quick_land&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Exceptions can be local to a block or global to the flight plan, in the &amp;lt;tt&amp;gt;&amp;lt;exceptions&amp;gt;&amp;lt;/tt&amp;gt; element. In the following example, time since last reception of a message from the ground station is monitored and the navigation is switched to the &amp;lt;tt&amp;gt;Standby&amp;lt;/tt&amp;gt; block if no message have been received for 22s. This exception is valid for '''all''' the blocks.&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;flight_plan ...&amp;gt;&lt;br /&gt;
  &amp;lt;waypoints&amp;gt; ... &amp;lt;/waypoints&amp;gt;&lt;br /&gt;
  &amp;lt;exceptions&amp;gt;&lt;br /&gt;
    &amp;lt;exception cond=&amp;quot;datalink_time &amp;gt; 22&amp;quot; deroute=&amp;quot;Standby&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/exceptions&amp;gt;&lt;br /&gt;
  &amp;lt;blocks&amp;gt; ...&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Deroute ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;deroute&amp;lt;/tt&amp;gt; is the ''goto'' directive of the flight plan; it switches the navigation to the given block:&lt;br /&gt;
&amp;lt;tt&amp;gt;&lt;br /&gt;
&amp;lt;deroute block=&amp;quot;landing&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that this primitive should not be used to execute loops which are provided by the following elements.&lt;br /&gt;
&lt;br /&gt;
==== Loops ====&lt;br /&gt;
&lt;br /&gt;
Unbounded loops are written with &amp;lt;tt&amp;gt;while&amp;lt;/tt&amp;gt; elements whose &amp;lt;tt&amp;gt;cond&amp;lt;/tt&amp;gt; attribute is a boolean expression.&lt;br /&gt;
Children  of &amp;lt;tt&amp;gt;while&amp;lt;/tt&amp;gt; are stages:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;while cond=&amp;quot;TRUE&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;go wp=&amp;quot;A&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;go wp=&amp;quot;B&amp;quot;/&amp;gt; &lt;br /&gt;
  &amp;lt;go wp=&amp;quot;C&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;while cond=&amp;quot;5 &amp;gt; stage_time&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/while&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
In this example, we run an infinite loop, lettin the aircraft try to go via waypoints &amp;lt;tt&amp;gt;A&amp;lt;/tt&amp;gt;, &amp;lt;tt&amp;gt;B&amp;lt;/tt&amp;gt; and &amp;lt;tt&amp;gt;C&amp;lt;/tt&amp;gt; and waiting for 5 seconds before repeating.&lt;br /&gt;
&lt;br /&gt;
Bounded loops are written with the &amp;lt;tt&amp;gt;for&amp;lt;/tt&amp;gt; tag:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;for var=&amp;quot;i&amp;quot; from=&amp;quot;0&amp;quot; to=&amp;quot;3&amp;quot;&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
 &amp;lt;/for&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
where the body of the loop will be run four times.&lt;br /&gt;
&lt;br /&gt;
The variable of a &amp;lt;tt&amp;gt;for&amp;lt;/tt&amp;gt; loop can be used inside expressions appearing as attributes of the stages:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;for var=&amp;quot;i&amp;quot; from=&amp;quot;1&amp;quot; to=&amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp=&amp;quot;HOME&amp;quot; radius=&amp;quot;75&amp;quot; alt=&amp;quot;ground_alt+50*$i&amp;quot; until=&amp;quot;stage_time&amp;gt;10&amp;quot; /&amp;gt;&lt;br /&gt;
 &amp;lt;/for&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In this example, the aircraft will circle around waypoint '''HOME''' for 10 seconds at and altitude above ground of 50m, 10 seconds at altitude 100 meter (50+50), ... until 250m (5x +50).&lt;br /&gt;
&lt;br /&gt;
Note: Two bounded loops using the same control variable are not allowed in the same block.&lt;br /&gt;
&lt;br /&gt;
==== Navigation modes ====&lt;br /&gt;
&lt;br /&gt;
Navigation modes give the description of the desired trajectory in 3D. While the horizontal mode is specified through&lt;br /&gt;
''stages'', the vertical control is specified with various attributes of these stages. The current available navigation stages are&lt;br /&gt;
* attitude : just keep a fixed attitude;&lt;br /&gt;
* heading : keep a given course;&lt;br /&gt;
* go : go to a given waypoint;&lt;br /&gt;
* circle : circle around a waypoint;&lt;br /&gt;
* stay : hold the position (hard to realize for a fixed-wing aircraft);&lt;br /&gt;
* follow : follow another aircraft;&lt;br /&gt;
* xyz : circle around a point moveable with the RC transmitter stick (obsolete with the datalink).&lt;br /&gt;
&lt;br /&gt;
The vertical control is achieved using the &amp;lt;tt&amp;gt;vmode&amp;lt;/tt&amp;gt; attribute of these stages. The possible values are &lt;br /&gt;
* '''alt''' (the default) : the autopilot keeps the desired altitude which is the altitude of the waypoint (if any) or the altitude specified with the &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt; attribute;&lt;br /&gt;
* '''climb''' : the autopilot keeps the desired vertical speed specified with the &amp;lt;tt&amp;gt;climb&amp;lt;/tt&amp;gt; attribute (in m/s);&lt;br /&gt;
* '''throttle''' : the autopilots sets the desired throttle specified with the &amp;lt;tt&amp;gt;throttle&amp;lt;/tt&amp;gt; attribute (between 0 and 1);&lt;br /&gt;
* '''glide''' : the autopilot keeps the desired slope between two waypoints&lt;br /&gt;
&lt;br /&gt;
The default control is done with the throttle. However, setting the &amp;lt;tt&amp;gt;pitch&amp;lt;/tt&amp;gt; attribute to '''auto''' and the &amp;lt;tt&amp;gt;throttle&amp;lt;/tt&amp;gt; attribute to a constant allows a vertical control only by controlling the attitude of the A/C.&lt;br /&gt;
The &amp;lt;tt&amp;gt;pitch&amp;lt;/tt&amp;gt; attribute also can be set to any value (in degrees) while the throttle control is in use: it usually affects the airspeed of the aircraft.  &lt;br /&gt;
&lt;br /&gt;
The different navigation modes are detailed in the next sections.&lt;br /&gt;
&lt;br /&gt;
==== Attitude ====&lt;br /&gt;
&lt;br /&gt;
Element &amp;lt;tt&amp;gt;attitude&amp;lt;/tt&amp;gt; is the navigation mode which corresponds to the current lowest control loop for horizontal mode.&lt;br /&gt;
The autopilot then keeps a constant attitude. The &amp;lt;tt&amp;gt;roll&amp;lt;/tt&amp;gt; attribute is required (in degrees, positive to put right wing low).&lt;br /&gt;
&lt;br /&gt;
To fly away, at constant airspeed:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;attitude roll=&amp;quot;0&amp;quot; vmode=&amp;quot;throttle&amp;quot;, throttle=&amp;quot;0.5&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
To fly around, holding a given altitude:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;attitude roll=&amp;quot;30&amp;quot; alt=&amp;quot;ground_alt+50&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that it is not a ''safe'' navigation mode since the geographic position of the plane is not controlled. However, this mode is useful to tune the roll attitude control loop.&lt;br /&gt;
&lt;br /&gt;
==== Heading ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tt&amp;gt;heading&amp;lt;/tt&amp;gt; primitive is relative to the second level loop for horizontal mode in the autopilot which will keep the given &amp;lt;tt&amp;gt;course&amp;lt;/tt&amp;gt;, a required attribute (in degrees, clockwise, north=0, east=90).&lt;br /&gt;
&lt;br /&gt;
One example to takeoff, following the QFU, 80% throttle, nose up (15 degrees) until height of 30m is reached:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;heading course=&amp;quot;QFU&amp;quot; vmode=&amp;quot;throttle&amp;quot; throttle=&amp;quot;0.8&amp;quot; pitch=&amp;quot;15&amp;quot; until=&amp;quot;(estimator_z &amp;gt; ground_alt+30)&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Go ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;go&amp;lt;/tt&amp;gt; primitive is probably the most useful one. Basically, the autopilot will try to join a given waypoint (&amp;lt;tt&amp;gt;wp&amp;lt;/tt&amp;gt;, the only required attribute). So the simplest thing you can ask for is&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;go wp=&amp;quot;HOME&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
which will set the '''HOME''' waypoint as the desired target position. Note than since &amp;lt;tt&amp;gt;vmode=&amp;quot;alt&amp;quot;&amp;lt;/tt&amp;gt; is the default, the altitude of the target waypoint is also taken into account. The navigation will switch to the next stage as soon as the target is reached.&lt;br /&gt;
&lt;br /&gt;
It is usually not a good idea to try to join a waypoint without asking for a precise trajectory, i.e. a given line.&lt;br /&gt;
Setting the &amp;lt;tt&amp;gt;hmode&amp;lt;/tt&amp;gt; attribute to '''route''', the navigation will go over a segment joining two waypoints:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;go from=&amp;quot;wp1&amp;quot; wp=&amp;quot;wp2&amp;quot; hmode=&amp;quot;route&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The target altitude is the altitude of the target waypoint; it can also be set with the &amp;lt;tt&amp;gt;alt&amp;lt;/tt&amp;gt; attribute. The following example keeps an altitude with fixed throttle:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;go from=&amp;quot;wp2&amp;quot; wp=&amp;quot;wp3&amp;quot; hmode=&amp;quot;route&amp;quot; pitch=&amp;quot;auto&amp;quot; throttle=&amp;quot;0.75&amp;quot; alt=&amp;quot;ground_alt+100&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The attributes related to the vertical control can also be set to replace the default altitude mode:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;go from=&amp;quot;wp1&amp;quot; wp=&amp;quot;wp2&amp;quot; hmode=&amp;quot;route&amp;quot; vmode=&amp;quot;climb&amp;quot; climb=&amp;quot;1.5&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Finally, the &amp;lt;tt&amp;gt;approaching_time&amp;lt;/tt&amp;gt; (in seconds) attribute helps to decide when the target is ''reached''. It can be set&lt;br /&gt;
to '''0''' to go over the target waypoint (default value is the '''CARROT''' time, set in the airframe configuration file).&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;go from=&amp;quot;wp1&amp;quot; wp=&amp;quot;wp2&amp;quot; hmode=&amp;quot;route&amp;quot; approaching_time=&amp;quot;1&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Circle ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;circle&amp;lt;/tt&amp;gt; primitive is the second main navigation mode: the trajectory is defined as a circle around a given waypoint with a given radius:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;circle wp=&amp;quot;HOME&amp;quot; radius=&amp;quot;75&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
A positive radius makes the UAS move clockwise, a negative counter-clockwise.&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;until&amp;lt;/tt&amp;gt; attribute may be used to control the end of the stage. The following example defines an ascending trajectory at constant throttle, nose up (15 degrees), over growing circles, until the battery level is low:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;circle wp=&amp;quot;wp1&amp;quot; radius=&amp;quot;50+(estimator_z-ground_alt)/2&amp;quot; vmode=&amp;quot;throttle&amp;quot; throttle=&amp;quot;0.75&amp;quot; pitch=&amp;quot;15&amp;quot; until=&amp;quot;10&amp;gt;PowerVoltage()&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Follow ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;follow&amp;lt;/tt&amp;gt; is a special primitive which makes the UAS follow another UAS (real or simulated, named with its &amp;lt;tt&amp;gt;ac_id&amp;lt;/tt&amp;gt;) at a given &amp;lt;tt&amp;gt;distance&amp;lt;/tt&amp;gt; (in meters) behind and at a given &amp;lt;tt&amp;gt;height&amp;lt;/tt&amp;gt; (in meters) above.&lt;br /&gt;
&lt;br /&gt;
In this example, the autopilot will try to follow A/C number '''4''', staying '''50'''m behind and '''20'''m above.&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;follow ac_id=&amp;quot;4&amp;quot; distance=&amp;quot;50&amp;quot; height=&amp;quot;20&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
Note that the &amp;lt;tt&amp;gt;traffic_info.c&amp;lt;/tt&amp;gt; file is required by this feature and the &amp;lt;tt&amp;gt;TRAFFIC_INFO&amp;lt;/tt&amp;gt; flag has to be set to enable it. Then, the following lines must be added in the airframe file:&lt;br /&gt;
 &amp;lt;tt&amp;gt;ap.srcs += traffic_info.c&amp;lt;/tt&amp;gt;&lt;br /&gt;
 &amp;lt;tt&amp;gt;ap.CFLAGS += -DTRAFFIC_INFO&amp;lt;/tt&amp;gt;&lt;br /&gt;
 &amp;lt;tt&amp;gt;sim.srcs += traffic_info.c&amp;lt;/tt&amp;gt;&lt;br /&gt;
 &amp;lt;tt&amp;gt;sim.CFLAGS += -DTRAFFIC_INFO&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Stay ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;stay&amp;lt;/tt&amp;gt; is a mode for UAS's able to hover:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;stay wp=&amp;quot;HOME&amp;quot; alt=&amp;quot;10&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== XYZ ====&lt;br /&gt;
&lt;br /&gt;
&amp;lt;tt&amp;gt;xyz&amp;lt;/tt&amp;gt; is a special mode where the UAS circles around a user moveable waypoint. This waypoint is moved with the RC sticks:&lt;br /&gt;
* YAW channel controls the point over the west-east axis;&lt;br /&gt;
* PITCH channel controls the point over the south-north axis;&lt;br /&gt;
* ROLL channel controls the altitude.&lt;br /&gt;
&lt;br /&gt;
Example (default radius is '''100'''):&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;xyz radius=&amp;quot;40&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Set ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;set&amp;lt;/tt&amp;gt; element is a dangerous one which should be used only by expert users: it is used to directly set an internal variable of the autopilot. For example, you can change the value of the default ground altitude, a variable used by the home mode failsafe procedure (and maybe by your own flight plan):&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;set var=&amp;quot;ground_alt&amp;quot; value=&amp;quot;ground_alt+50&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
This directive is extremely powerful and has great potential for error - use with caution.&lt;br /&gt;
&lt;br /&gt;
==== Call ====&lt;br /&gt;
&lt;br /&gt;
The &amp;lt;tt&amp;gt;call&amp;lt;/tt&amp;gt; allows the user to define its own navigation procedures in C. The &amp;lt;tt&amp;gt;value&amp;lt;/tt&amp;gt; must be a call to a boolean function which must return TRUE as long as the stage is not completed (a function which should be called only once would then return immediately FALSE).&lt;br /&gt;
This feature is illustrated with the '''line''' pattern:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;call fun=&amp;quot;nav_line_init()&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;call fun=&amp;quot;nav_line(WP_1, WP_2, nav_radius)&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
where &amp;lt;tt&amp;gt;nav_line_init()&amp;lt;/tt&amp;gt; returns FALSE and &amp;lt;tt&amp;gt;nav_line()&amp;lt;/tt&amp;gt; always returns TRUE (this stage never ends).&lt;br /&gt;
Such functions usually are defined in a supplementary C file which must be specified in the airframe file (in the &amp;lt;tt&amp;gt;makefile&amp;lt;/tt&amp;gt; section)&lt;br /&gt;
 &amp;lt;tt&amp;gt;ap.srcs += nav_line.c&lt;br /&gt;
 sim.srcs += nav_line.c&amp;lt;/tt&amp;gt;&lt;br /&gt;
These functions also must be declared in a header file which must be mentioned in the header element of the flight plan:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;header&amp;gt;&lt;br /&gt;
 #include &amp;quot;nav_line.h&amp;quot;&lt;br /&gt;
 &amp;lt;/header&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
These C source file and H header file must be located in the &amp;lt;tt&amp;gt;sw/airborne&amp;lt;/tt&amp;gt; directory.&lt;br /&gt;
&lt;br /&gt;
You can also call functions before or after each execution of the block:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;block name=&amp;quot;circlehome&amp;quot; pre_call=&amp;quot;function_to_call_before_circle()&amp;quot; post_call=&amp;quot;function_to_call_after_circle()&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp=&amp;quot;HOME&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/block&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Advanced Examples ==&lt;br /&gt;
Parameters used in a flight plan can be computed expressions. In this example, the plane is asked to perform 5 circles at progressively increasing altitudes for exactly one minute at each altitude:&lt;br /&gt;
 &amp;lt;for var = &amp;quot;i&amp;quot; from = &amp;quot;1&amp;quot; to = &amp;quot;5&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;circle wp = &amp;quot;HOME&amp;quot; radius=&amp;quot;75&amp;quot;&lt;br /&gt;
          alt = &amp;quot;ground_alt+50*$i&amp;quot;&lt;br /&gt;
          until = &amp;quot;stage_time&amp;gt;60&amp;quot; /&amp;gt;&lt;br /&gt;
 &amp;lt;/for&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Immobilize Actuators === &lt;br /&gt;
&lt;br /&gt;
h_ctl setpoints variable are set by the h_ctl_attitude_loop() (from fw_h_ctl.c) loop) which can be disabled with the&lt;br /&gt;
h_ctl_disabled flag:&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;set var=&amp;quot;h_ctl_disabled&amp;quot; value=&amp;quot;TRUE&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;set var=&amp;quot;h_ctl_aileron_setpoint&amp;quot; value=&amp;quot;0&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;set var=&amp;quot;h_ctl_elevator_setpoint&amp;quot; value=&amp;quot;MAX_PPRZ/2&amp;quot;/&amp;gt;&lt;br /&gt;
 .... waiting for a condition ...&lt;br /&gt;
 &amp;lt;set var=&amp;quot;h_ctl_disabled&amp;quot; value=&amp;quot;FALSE&amp;quot;/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Procedures ==&lt;br /&gt;
&lt;br /&gt;
Procedures are libraries which can be included in flight plans. They are composed of waypoints, sectors and blocks. The header of a procedure may contain some parameters which are replaced by arguments when the procedure is included.&lt;br /&gt;
&lt;br /&gt;
Extract of the DTD: a procedure is a sequence of parameters, waypoints, ...:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;!ELEMENT procedure (param*,header?,waypoints?,sectors?,exceptions?,blocks?)&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
A &amp;lt;tt&amp;gt;param&amp;lt;/tt&amp;gt;eter is just a name. A parameter is optional if it is declared with a default value.&lt;br /&gt;
An example with a required and an optional parameter:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;param name=&amp;quot;alt&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;param name=&amp;quot;radius&amp;quot; default_value=&amp;quot;75&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Procedures are called with the &amp;lt;tt&amp;gt;include&amp;lt;/tt&amp;gt; element in a flight plan. A procedure cannot be included twice or by another procedure. A procedure call requires:&lt;br /&gt;
&lt;br /&gt;
* the name of the procedure file, the name given to this inclusion; &lt;br /&gt;
* values for the parameters;&lt;br /&gt;
* backlinks for block name exits of the procedure.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;include name=&amp;quot;landing&amp;quot; procedure=&amp;quot;landing.xml&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Here is the corresponding procedure '''landing.xml''':&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;!DOCTYPE procedure SYSTEM &amp;quot;flight_plan.dtd&amp;quot;&amp;gt;&lt;br /&gt;
 &amp;lt;procedure&amp;gt;&lt;br /&gt;
  &amp;lt;waypoints&amp;gt;&lt;br /&gt;
    &amp;lt;waypoint name=&amp;quot;AF&amp;quot; x=&amp;quot;177.4&amp;quot; y=&amp;quot;45.1&amp;quot; alt=&amp;quot;30&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;waypoint name=&amp;quot;TD&amp;quot; x=&amp;quot;28.8&amp;quot; y=&amp;quot;57.0&amp;quot; alt=&amp;quot;0&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;waypoint name=&amp;quot;_BASELEG&amp;quot; x=&amp;quot;168.8&amp;quot; y=&amp;quot;-13.8&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/waypoints&amp;gt;&lt;br /&gt;
  &amp;lt;blocks&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
    &amp;lt;block name=&amp;quot;land&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;call fun=&amp;quot;nav_compute_baseleg(WP_AF, WP_TD, WP__BASELEG, nav_radius)&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;circle radius=&amp;quot;nav_radius&amp;quot; until=&amp;quot;NavCircleCount() &amp;gt; 0.5&amp;quot; wp=&amp;quot;_BASELEG&amp;quot;/&amp;gt;&lt;br /&gt;
      &amp;lt;circle radius=&amp;quot;nav_radius&amp;quot; until=&amp;quot;And(NavQdrCloseTo(DegOfRad(baseleg_out_qdr)-10), 10 &amp;gt; fabs(estimator_z - WaypointAlt(WP__BASELEG)))&amp;quot; wp=&amp;quot;_BASELEG&amp;quot;/&amp;gt;&lt;br /&gt;
    &amp;lt;/block&amp;gt;&lt;br /&gt;
 ...&lt;br /&gt;
  &amp;lt;/blocks&amp;gt;&lt;br /&gt;
 &amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Note that the name of procedure '''land''' block will be renamed into '''landing.land''':&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;deroute block=&amp;quot;landing.land&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
will jump to this procedure block.&lt;br /&gt;
&lt;br /&gt;
Suppose you have a go-around condition in your landing procedure. You would write it&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;exception cond=&amp;quot;...&amp;quot; deroute=&amp;quot;go-around&amp;quot;/&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
then you must link this block exit with one of your block (e.g. &amp;lt;tt&amp;gt;Standby&amp;lt;/tt&amp;gt;). So you would include the procedure as follows:&lt;br /&gt;
 &amp;lt;tt&amp;gt;&amp;lt;include name=&amp;quot;landing&amp;quot; procedure=&amp;quot;landing.xml&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;with from=&amp;quot;go-around&amp;quot; to=&amp;quot;Standby&amp;quot;/&amp;gt;&lt;br /&gt;
 &amp;lt;/include&amp;gt;&amp;lt;/tt&amp;gt;\&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
&lt;br /&gt;
There are many ways to skin a cat just as there are many ways to craft your flight plan. Following the best practices tips can save you from a lot of frustration and mishap.&lt;br /&gt;
&lt;br /&gt;
* Simulate your flight plan before taking it to the sky. Flight plans should always be carefully tested prior to flight, take a look at the [[Simulation|simulation]] page for details on how to simulate your plan.&lt;br /&gt;
* Make an subdirectory in the Flight_plan directory with your own name and add your flight plans there. Make sure that the location of the DTD is correct, e.g by using relative directory double dots as in &amp;lt;tt&amp;gt;&amp;lt;!DOCTYPE flight_plan SYSTEM &amp;quot;../flight_plan.dtd&amp;quot;&amp;gt;&amp;lt;/tt&amp;gt;&lt;br /&gt;
&lt;br /&gt;
* Take a good look at other flight plans included with Paparazzi. To learn from example flight plans please visit the [[Flight_Plan_Examples|flight plan examples]] page&lt;br /&gt;
* There are several option to build failsafe features into you flightplan, [[Failsafe|for some examples visit the Failsafe page]].&lt;br /&gt;
* Some flight plan examples define waypoint locations using relative coordinates. These are relative positions from the fixed lat and lon in the header of the flight plan. When simulating your flight plan the aircraft always use the lat/lon as defined in the flight plan since a regular simulation has no notion of you current position of you local PC where you simulate on. This is something to keep in mind if you test your flight plan in real flights.&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9916</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9916"/>
		<updated>2011-08-09T04:43:41Z</updated>

		<summary type="html">&lt;p&gt;Rufus: Chanel 5 on Spektrum DX5i won't mod to 3 position switch :/&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
= Current project: Lisa/M Quad =&lt;br /&gt;
I am currently gathering parts for a my first Quad project, which also be my first foray into STM32 paparazzi. So far, I have accumulated:&lt;br /&gt;
&lt;br /&gt;
* Lisa/M with Asprin (yay!) and a JTag thingy.&lt;br /&gt;
* orderd a [http://www.hoverthings.com/catalog/ VC-450] quad frame, expect to have it soon. &lt;br /&gt;
* These [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=121 1000 Kv motors], these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=146 30A ESCs], and these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=527 12 pairs or 10&amp;quot; * 4.5&amp;quot; counter rotating props]. I have no idea if these are any good, or even if they are fit for purpose, I only know they cheap.&lt;br /&gt;
* 2 Orange DSM2 satellite receivers from HobbyKing&lt;br /&gt;
* 900Hz xbees (international firmware, 915-928 MHz and power limited to fit withing the Australian ISM class licence)&lt;br /&gt;
* a new design NEO-6Q GPS (will fall back to a LEA-5H if this creates problems), etc&lt;br /&gt;
* plenty of lipos, picoblade bits and pieces, LEDs, etc.&lt;br /&gt;
&lt;br /&gt;
anticipated AUW ~1kg.&lt;br /&gt;
&lt;br /&gt;
The powertrain spec is similar to what most of the VC-450 setups on the RC Groups thread have, but I suspect that (on 3S lipos) those motors/ESCs will be slightly under-propped. My main concern is that the controllers won't be fast enough, expect I may need to replace them with something better, but given the size of this model it might be OK to run them a little slower. The props feel quite flimsy and I will certainly be balancing them well before I use them.&lt;br /&gt;
&lt;br /&gt;
I still need to acquire a DSM2 transmitter, probably a JR module for a Turnigy 9X.&lt;br /&gt;
&lt;br /&gt;
My plan is to build a robust and strait-forward quad, then learn to fly it. After that, I'd like to switch to 36 MHz PPM control (like my planes) or fly by joystick to free up 2.4 GHz for analog video. Then I'll probably move on to a smaller bespoke frame, I guess.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9915</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9915"/>
		<updated>2011-08-09T04:30:51Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
= Current project: Lisa/M Quad =&lt;br /&gt;
I am currently gathering parts for a my first Quad project, which also be my first foray into STM32 paparazzi. So far, I have accumulated:&lt;br /&gt;
&lt;br /&gt;
* Lisa/M with Asprin (yay!) and a JTag thingy.&lt;br /&gt;
* orderd a [http://www.hoverthings.com/catalog/ VC-450] quad frame, expect to have it soon. &lt;br /&gt;
* These [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=121 1000 Kv motors], these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=146 30A ESCs], and these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=527 12 pairs or 10&amp;quot; * 4.5&amp;quot; counter rotating props]. I have no idea if these are any good, or even if they are fit for purpose, I only know they cheap.&lt;br /&gt;
* 2 Orange DSM2 satellite receivers from HobbyKing&lt;br /&gt;
* 900Hz xbees (international firmware, 915-928 MHz and power limited to fit withing the Australian ISM class licence)&lt;br /&gt;
* a new design NEO-6Q GPS (will fall back to a LEA-5H if this creates problems), etc&lt;br /&gt;
* plenty of lipos, picoblade bits and pieces, LEDs, etc.&lt;br /&gt;
&lt;br /&gt;
anticipated AUW ~1kg.&lt;br /&gt;
&lt;br /&gt;
The powertrain spec is similar to what most of the VC-450 setups on the RC Groups thread have, but I suspect that (on 3S lipos) those motors/ESCs will be slightly under-propped. My main concern is that the controllers won't be fast enough, expect I may need to replace them with something better, but given the size of this model it might be OK to run them a little slower. The props feel quite flimsy and I will certainly be balancing them well before I use them.&lt;br /&gt;
&lt;br /&gt;
I still need to acquire a DSM2 transmitter. Either a Spectrum/JR module for a Turnigy 9X. The other alternative is to get a Spectrum 5i (if I can mod it's channel 5 into a 3 position switch, not sure if that will work yet.&lt;br /&gt;
&lt;br /&gt;
My plan is to build a robust and strait-forward quad, then learn to fly it. After that, I'd like to switch to 36 MHz PPM control (like my planes) or fly by joystick to free up 2.4 GHz for analog video. Then I'll probably move on to a smaller bespoke frame, I guess.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9914</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9914"/>
		<updated>2011-08-09T04:03:53Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
= Current project: Lisa/M Quad =&lt;br /&gt;
I am currently gathering parts for a my first Quad project, which also be my first foray into STM32 paparazzi. So far, I have accumulated:&lt;br /&gt;
&lt;br /&gt;
* Lisa/M with Asprin (yay!) and a JTag thingy.&lt;br /&gt;
* orderd a [http://www.hoverthings.com/catalog/ VC-450] quad frame, expect to have it soon. &lt;br /&gt;
* These [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=121 1000 Kv motors], these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=146 30A ESCs], and these [http://www.rctimer.com/index.php?gOo=goods_details.dwt&amp;amp;goodsid=527 12 pairs or 10&amp;quot; * 4.5&amp;quot; counter rotating props]. I have no idea if these are any good, or even if they are fit for purpose, I only know they cheap.&lt;br /&gt;
* 2 Orange DSM2 satellite receivers from HobbyKing&lt;br /&gt;
* 900Hz xbees (international firmware, 915-928 MHz and power limited to fit withing the Australian ISM class licence)&lt;br /&gt;
* a new design NEO-6Q GPS (will fall back to a LEA-5H if this creates problems), etc&lt;br /&gt;
* plenty of lipos, picoblade bits and pieces, etc.&lt;br /&gt;
&lt;br /&gt;
anticipated AUW ~1kg.&lt;br /&gt;
&lt;br /&gt;
The powertrain spec is similar to what most of the VC-450 setups on the RC Groups thread have, but I suspect that (on 3S lipos) those motors/ESCs will be slightly under-propped (wasted weight). My main concern is that the controllers won't be fast enough, expect I may need to replace them with something better. The props feel a little flimsy and I will certainly be balancing them well before I use them.&lt;br /&gt;
&lt;br /&gt;
I still need to acquire a DSM2 transmitter. Either a Spectrum/JR module for a Turnigy 9X (open source firmware, it's just an AVR with the right inputs), or borrow my friends spare Spectrum 5i. I'll find out if the 5i has a 3 position switch, I'll check it out before buying the Spectrum module.&lt;br /&gt;
&lt;br /&gt;
My plan is to build a robust and strait-forward quad, then learn to fly it. After that, I'd like to switch to 36 MHz PPM control (like my planes) or fly by joystick to free up 2.4 GHz for analog video.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9913</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9913"/>
		<updated>2011-08-09T03:35:00Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
= Current project: Lisa/M Quad =&lt;br /&gt;
I am currently gathering parts for a my first Quad project, which also be my first foray into STM32 paparazzi. So far, I have accumulated:&lt;br /&gt;
&lt;br /&gt;
* Lisa/M with Asprin (yay!) and a JTag thingy.&lt;br /&gt;
* orderd a [http://www.hoverthings.com/catalog/ VC-450] quad frame, expect to have it soon. &lt;br /&gt;
* 1000 Kv motors, (add link). These seem similar to what most of the VC-450 users on the RC Groups thread are using.&lt;br /&gt;
* 20A PWM controllers, (add link). No idea if they will support fast enough PWM, my plan is to try 400 Hz and see if it works. If not wind back until I find the fastest speed they do work at, and if it's not &amp;lt;200Hz use them anyhow, otherwise donate them to other projects and get something different.&lt;br /&gt;
* 10&amp;quot;*4.75&amp;quot; props (add link), not yet balanced but will before I use them.&lt;br /&gt;
* 2 cheap Orange DSM2 satellite receivers from HobbyKing&lt;br /&gt;
* 900Hz xbees (international firmware, 915-928 MHz and power limited to fit withing the Australian ISM class licence)&lt;br /&gt;
* plenty of xbees, batteries, picoblade, a new design NEO-6Q GPS (will fall back to a LEA-5H if this creates problems), etc&lt;br /&gt;
&lt;br /&gt;
I need to acquire a DSM2 transmitter. Either a Spectrum/JR module and a Turnigy 9X transmitter (because I like the idea of an open source transmitter), or a Spectrum 5i (because a friend has one he's not using that I can borrow). I don't know if the 5i has a 3 position switch, I'll check it out before buying the Spectrum module.&lt;br /&gt;
&lt;br /&gt;
My plan is to make a robust and strait-forward quad the easiest way I can find, and learn to fly it. After that, I'd like to switch to 36 MHz PPM control or fly by telemetry (joystick) to free up 2.4 GHz for analog video.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9912</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=9912"/>
		<updated>2011-08-09T03:34:26Z</updated>

		<summary type="html">&lt;p&gt;Rufus: update current projects&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I mostly fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
= Current project: Lisa/M Quad =&lt;br /&gt;
I am currently gathering parts for a my first Quad project, which also be my first foray into STM32 paparazzi. So far, I have accumulated:&lt;br /&gt;
&lt;br /&gt;
* Lisa/M with Asprin (yay!) and a JTag thingy.&lt;br /&gt;
* orderd a [http://www.hoverthings.com/catalog/ VC-450] quad frame, expect to have it soon. &lt;br /&gt;
* 1000 Kv motors, (add link). These seem similar to what most of the VC-450 users on the RC Groups thread are using.&lt;br /&gt;
* 20A PWM controllers, (add link). No idea if they will support fast enough PWM, my plan is to try 400 Hz and see if it works. If not wind back until I find the fastest speed they do work at, and if it's not &amp;lt;200Hz use them anyhow, otherwise donate them to other projects and get something different.&lt;br /&gt;
* 10&amp;quot;*4.75&amp;quot; props (add link), not yet balanced but will before I use them.&lt;br /&gt;
* 2 cheap Orange DSM2 satellite receivers from HobbyKing&lt;br /&gt;
* 900Hz xbees (international firmware, 915-928 MHz and power limited to fit withing the Australian ISM class licence)&lt;br /&gt;
* plenty of xbees, batteries, picoblade, a new design NEO-6Q GPS (will fall back to a LEA-5H if this creates problems), etc&lt;br /&gt;
&lt;br /&gt;
I need to acquire a DSM2 transmitter. Either a Spectrum/JR module and a Turnigy 9X transmitter (because I like the idea of an open source transmitter), or a Spectrum 5i (because a friend has one he's not using that I can borrow). I don't know if the 5i has a 3 position switch, I'll check it out before buying the Spectrum module.&lt;br /&gt;
&lt;br /&gt;
My plan is to make a robust and strait-forward quad the easiest way I can find, and learn to fly it. After that, I'd like to switch to 36 MHz PPM control or fly by telemetry (joystick) to free up 2.4 GHz for an analog video.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=9492</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=9492"/>
		<updated>2011-06-04T10:16:55Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com image:aerofu_logo.png  aerofu.com ] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com [[image:aerofu_logo.png]]  Aerofu.com ] =&lt;br /&gt;
&lt;br /&gt;
Low cost Paparazzi hardware from Australia. &lt;br /&gt;
Licenced to export to [http://aerofu.com/index.php?main_page=page&amp;amp;id=2 33 countries], including Europe and North America. Recentry restocked with:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=30 Tiny] &lt;br /&gt;
and&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=31 TWOG]&lt;br /&gt;
autopilots.&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
Complete Kits ([http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=48 Tiny] or [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=49 TWOG] based).&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=10&amp;amp;products_id=20 PPM Encoders] and [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=8&amp;amp;products_id=44 IR Sensors] from the Paparazzi project.&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
Inexpensive [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=7&amp;amp;products_id=12 uBlox LEA-5H GPS units].&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;various PCBs&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
Due to an unexpected change in my &amp;quot;real&amp;quot; job, I will regrettably be returning to the United States in the near future.  As such, I will be closing my webshop for good.  It has been a pleasure getting to know so many paparazzi users and an honor to supply hardware to you.  Thanks for all the help and support I have received.&lt;br /&gt;
&lt;br /&gt;
I apologize for the short notice.  But I will be taking orders until Friday 24 September, so anybody wishing to purchase paparazzi equipment from my store will be able to do so until that time.&lt;br /&gt;
&lt;br /&gt;
Thankfully somebody has offered to step up and take my place.  I have been working with Chris and AeroFu (aerofu.com) and he has agreed to continue providing paparazzi hardware and to selling out the remainder of my inventory.  I am confident he will continue to provide a high level of service and support for those looking to get into the hobby and into the paparazzi project.&lt;br /&gt;
&lt;br /&gt;
Again, thanks to all and happy flying!&lt;br /&gt;
&lt;br /&gt;
Buzz &lt;br /&gt;
 &lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|Paparazzi controllers]][[Image:Ppzbundlefeb2011gpsmed.jpg|thumb|400px|Bundle with GPS]] =&lt;br /&gt;
&amp;lt;h2&amp;gt;Providing professionally assembled and tested hardware for your Paparazzi Projects since 2007&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. &lt;br /&gt;
To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Our testing includes:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Burn in testing: We Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&amp;lt;b&amp;gt;We also make getting flying easy by offering bundled items that are tested and ready to connect together like this [https://store.ppzuav.com/osc/product_info.php?products_id=128 TWOG BUNDLE].&lt;br /&gt;
Visit the PPZUAZ [https://store.ppzuav.com WebStore] to see the latest offerings.&amp;lt;/b&amp;gt;&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Tiny&amp;diff=9340</id>
		<title>Tiny</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Tiny&amp;diff=9340"/>
		<updated>2011-05-08T02:49:02Z</updated>

		<summary type="html">&lt;p&gt;Rufus: disambiguate Tiny versions&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Tiny''' may refer to two Paparazzi autopilot designs.&lt;br /&gt;
* [[Tiny v2.11]]&lt;br /&gt;
* [[Tiny v1.1]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Compiling&amp;diff=9319</id>
		<title>Compiling</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Compiling&amp;diff=9319"/>
		<updated>2011-05-02T22:43:02Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Step 2 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Introduction ==&lt;br /&gt;
&lt;br /&gt;
The goal of this part of the documentation is to give you insight in how to give your Autopilot board a ''Brain''. Airborne autopilot code, flight plans and configuration settings are compiled into a single file, sometimes referred to as a ''binary image''. After compilation this file is transferred to the Autopilot board micro-controller flash ROM through use of an USB cable. Note that most tuning and flight plan parameters can be changed in-flight but after each power cycle, the autopilot reverts to the original settings. Permanent changes are made by recompiling the airborne code and it's new configurations settings, and re-upload this to the autopilot board. It may sound complicated but in fact it is quite simple if you follow the steps below.&lt;br /&gt;
&lt;br /&gt;
== Get access to your computers USB port ==&lt;br /&gt;
&lt;br /&gt;
Regular users, (also known as Non-Root) by default, as security measure, can not access and interact with hardware in- and output- devices (I/O), USB ports included. To make it possible, the user you are using to program the autopilot board must be a member of the ''plugdev'' group. Note that usually the original username you used when you installed your Linux OS is already a member. &lt;br /&gt;
&lt;br /&gt;
If you are '''not''' already a member, add yourself to this ''plugdev'' group with the following command:&lt;br /&gt;
&lt;br /&gt;
  $ sudo adduser $USER plugdev&lt;br /&gt;
&lt;br /&gt;
It will be effective only on your next login or after the command&lt;br /&gt;
&lt;br /&gt;
  $ newgrp plugdev&lt;br /&gt;
&lt;br /&gt;
== USB flashing ==&lt;br /&gt;
&lt;br /&gt;
The Paparazzi device rules are required for USB flashing.  Copy them into place if you haven't already done so:&lt;br /&gt;
 &lt;br /&gt;
  $ sudo cp $PAPARAZZI_HOME/conf/system/udev/rules/10-paparazzi.rules /etc/udev/rules.d/&lt;br /&gt;
&lt;br /&gt;
If you are using Ubuntu with a version '''lower''' than v9.10, the [http://mielke.cc/brltty/ Braille TTY] driver interferes with FTDI USB Serial adapters and should be removed by running the following in the command prompt&lt;br /&gt;
&lt;br /&gt;
 $ sudo apt-get remove brltty&lt;br /&gt;
&lt;br /&gt;
[[Image:Tiny_test_wiring.jpg|thumb|Example wiring for programming and telemetry]]&lt;br /&gt;
If the autopilot senses a connected USB cable during power-on, it will wait to receive a firmware image rather than booting normally.  The firmware can be compiled and flashed by several means, '''the simplest way using the [[Paparazzi_Center|Paparazzi Center]]''', the traditional way being:&lt;br /&gt;
 make AIRCRAFT=''myplane'' clean_ac ap.upload&lt;br /&gt;
 (where ''myplane'' is the name of your airframe as defined in &amp;lt;tt&amp;gt;conf/conf.xml&amp;lt;/tt&amp;gt;)&lt;br /&gt;
&lt;br /&gt;
This command erases any compiled autopilot code from the PC, recompiles everything from scratch, and then sends it to the autopilot.  &lt;br /&gt;
Variations include:&lt;br /&gt;
* make AIRCRAFT=''myplane'' sim&lt;br /&gt;
*: Compiles your code for use in the simulator - note that &amp;quot;clean_ac&amp;quot; will remove this code, so the simulator code must be rebuilt each time a clean has been performed.&lt;br /&gt;
* make AIRCRAFT=''myplane'' fbw.upload&lt;br /&gt;
*: This is needed when configuring the separate &amp;quot;fly by wire&amp;quot; MCU on the [[Classix]] autopilot.&lt;br /&gt;
* make AIRCRAFT=''myplane'' ap&lt;br /&gt;
*: This will simply build the portions of autopilot code that have changed since the last compile without attempting to flash.  Note: this method may not detect certain changes (i.e. changes to the airframe makefile section or CVS updated code).&lt;br /&gt;
* make AIRCRAFT=''myplane'' ap.upload FLASH_MODE=IAP&lt;br /&gt;
*: Specifies USB flashing.  This should be specified at the top of the makefile section of your airframe file but can be overridden here.  Use FLASH_MODE=IAS for serial flashing.&lt;br /&gt;
&lt;br /&gt;
=== Verify that above upload works ===&lt;br /&gt;
&lt;br /&gt;
==== Step 1 ====&lt;br /&gt;
&lt;br /&gt;
Connect an USB cable to the USB port on the autopilot board.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:Fase2_Insert_Flightplan_A.jpg|Board to mini USB connect&lt;br /&gt;
Image:Fase2_Insert_Flightplan_B.jpg|Make sure you have a connector for power ('''Don't''' power up yet!)&lt;br /&gt;
Image:Fase2_Insert_Flightplan_C.jpg|Connect USB to PC '''and''' Board&lt;br /&gt;
Image:Fase2_Insert_Flightplan_D.jpg|only '''now''', power up the board&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Now if you type the following command in your terminal...&lt;br /&gt;
&lt;br /&gt;
 $ dmesg | tail -5&lt;br /&gt;
&lt;br /&gt;
..you should see messages that look like:&lt;br /&gt;
&lt;br /&gt;
 [79212.484187] pl2303 1-2.3:1.0: device disconnected&lt;br /&gt;
 [82312.463077] usb 5-1: new high speed USB device using ehci_hcd and address 23&lt;br /&gt;
 [82327.555770] usb 5-1: device descriptor read/64, error -110&lt;br /&gt;
 [82342.752307] usb 5-1: device descriptor read/64, error -110&lt;br /&gt;
 [82342.968031] usb 5-1: new high speed USB device using ehci_hcd and address 24&lt;br /&gt;
&lt;br /&gt;
Which confirms that your device is powered up and working, and ready to accept new airborne code. In case you do not see this message, check your battery voltage and connections and make sure the cables are not broken.&lt;br /&gt;
&lt;br /&gt;
==== Step 2 ====&lt;br /&gt;
&lt;br /&gt;
Upload the compiled Autopilot code a.k.a, firmware&lt;br /&gt;
&lt;br /&gt;
   $ make AIRCRAFT=DEMO demo2.upload&lt;br /&gt;
&lt;br /&gt;
     make[1]: Leaving directory `/usr/share/paparazzi'&lt;br /&gt;
    cd sw/airborne; make PAPARAZZI_SRC=/usr/share/paparazzi PAPARAZZI_HOME=/home/dirkx/paparazzi TARGET=demo2 all&lt;br /&gt;
    make[1]: Entering directory `/usr/share/paparazzi/sw/airborne'&lt;br /&gt;
    /home/dirkx/paparazzi/var/demo/demo2/demo2.elf  :&lt;br /&gt;
    section    size         addr&lt;br /&gt;
    .text       956        16384&lt;br /&gt;
    .ctors        0        17340&lt;br /&gt;
    .dtors        0        17340&lt;br /&gt;
    .data         0   1073741824&lt;br /&gt;
    .bss         12   1073741824&lt;br /&gt;
    .stack     4096   1073742080&lt;br /&gt;
    .comment     54            0&lt;br /&gt;
    Total      5118&lt;br /&gt;
    make[1]: Leaving directory `/usr/share/paparazzi/sw/airborne'&lt;br /&gt;
    cd sw/airborne; make PAPARAZZI_SRC=/usr/share/paparazzi PAPARAZZI_HOME=/home/dirkx/paparazzi TARGET=demo2 upload&lt;br /&gt;
    make[1]: Entering directory `/usr/share/paparazzi/sw/airborne'&lt;br /&gt;
    /usr/share/paparazzi/sw/ground_segment/lpc21iap/lpc21iap  /home/dirkx/paparazzi/var/demo/demo2/demo2.elf&lt;br /&gt;
    .&lt;br /&gt;
    Found USB device&lt;br /&gt;
    BootROM code: 2.12&lt;br /&gt;
    Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)&lt;br /&gt;
    BootLoader version: 1.3&lt;br /&gt;
    #&lt;br /&gt;
    Starting software at 0x00004000&lt;br /&gt;
    make[1]: Leaving directory `/usr/share/paparazzi/sw/airborne'&lt;br /&gt;
    make: Leaving directory `/usr/share/paparazzi'&lt;br /&gt;
&lt;br /&gt;
Which confirms that your device has the bootloader functioning. The important bit of output is:&lt;br /&gt;
&lt;br /&gt;
    Found USB device&lt;br /&gt;
    BootROM code: 2.12&lt;br /&gt;
    Part ID: 0x0402FF25 (LPC2148, 512k Flash, 32k+8k RAM)&lt;br /&gt;
    BootLoader version: 1.3&lt;br /&gt;
    #&lt;br /&gt;
&lt;br /&gt;
In the rare case your autopilot board does not have a bootloader, [http://paparazzi.enac.fr/wiki/BootloaderUploadHowTo read and follow the instruction on how to install a bootloader first]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
NOTE: In the above example we're using a modified [http://paparazzi.enac.fr/wiki/Using_demo_programs_in_sw/airborne demo] - which flashes the LEDs with a Tiny2.1 board): Be aware that the demos involving serial ports do not currently work with Tiny V2's.&lt;br /&gt;
&lt;br /&gt;
==== Step 3 ====&lt;br /&gt;
&lt;br /&gt;
Observe the LEDs flashing.&lt;br /&gt;
&lt;br /&gt;
==== Step 4 ====&lt;br /&gt;
&lt;br /&gt;
Disconnect the USB cable, Disconnect the power and reconnect the power of the autopilot board. The LED's should flash again.&lt;br /&gt;
&lt;br /&gt;
==== Step 5 ====&lt;br /&gt;
&lt;br /&gt;
Select aircraft MJ5, build and upload.&lt;br /&gt;
&lt;br /&gt;
Select airframe funjet1.xml (if you have a Tiny V2)&lt;br /&gt;
&lt;br /&gt;
Connect the serial port of your tiny to your PC using a level converter and select session Flight USB serial@9600.&lt;br /&gt;
&lt;br /&gt;
If you are using funjet1.xml:&lt;br /&gt;
*Stop all the processes but do not remove them.&lt;br /&gt;
*Edit the line Data Link and add &amp;quot;-s 57600&amp;quot; to the end, to tell the data link the baud rate of the MJ5.&lt;br /&gt;
*Restart Data Link, Server and GCS in that order.&lt;br /&gt;
&lt;br /&gt;
If all went well, it should work and you should see messages coming in from the Tiny!&lt;br /&gt;
&lt;br /&gt;
== Installing the tunnel for direct access to the GPS ==&lt;br /&gt;
&lt;br /&gt;
This completely replaces the normal autopilot code (leaving the USB bootloader intact) with a simple serial-to-serial pass-thru that essentially connects the GPS serial port directly to the modem serial port or a USB-to-serial connection that creates a USB serial port that goes to GPS port or modem port. Use this only to gain direct access to the GPS for testing/configuration with [[GPS#GPS_configuration_using_U-Center|U-Center]] or other software.&lt;br /&gt;
&lt;br /&gt;
You have to add the tunnel targets to your airframe file if you want to use them:&lt;br /&gt;
  &amp;lt;firmware name=&amp;quot;setup&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;target name=&amp;quot;tunnel&amp;quot; board=&amp;quot;twog_1.0&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;target name=&amp;quot;usb_tunnel_0&amp;quot; board=&amp;quot;twog_1.0&amp;quot; /&amp;gt;&lt;br /&gt;
  &amp;lt;/firmware&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== UART tunnel ====&lt;br /&gt;
&lt;br /&gt;
Use this if you have a serial cable to connect. The LEDs will blink when data is transferred. Type the following command from your paparazzi folder, substituting the name of your airframe and paying attention to case sensitivity:&lt;br /&gt;
 make AIRCRAFT=''myplane'' tunnel.upload&lt;br /&gt;
Connect the USB cable and power on the autopilot to receive the code.&lt;br /&gt;
&lt;br /&gt;
This can be done without the USB bootloader by appending ''FLASH_MODE=ISP'' to the command line (specifying ISP serial loading).  This will require a serial cable connection (i.e. FTDI USB-to-TTL). '''WARNING!''' Installing tunnel code with the ISP method will erase any USB bootloader code. Make sure you are able to install a bootloader yourself.&lt;br /&gt;
&lt;br /&gt;
==== USB tunnel ====&lt;br /&gt;
&lt;br /&gt;
This can be done without a serial cable just by having USB. The LEDs will blink when data is transferred. It can connect to either serial port on the autopilot (for Tiny 2.11: uart0=gps, uart1=modem). To connect USB to the gps type the following command from your paparazzi folder, substituting the name of your airframe and paying attention to case sensitivity:&lt;br /&gt;
 make AIRCRAFT=''myplane'' usb_tunnel_0.upload&lt;br /&gt;
Connect the usb cable and power on the autopilot to receive the code. The code will switch the USB to emulate a serial port that you can access at '''/dev/ttyACMx'''. Windows user can extract the usbser.sys file from .cab file in C:\WINDOWS\Driver Cache\i386 and store it somewhere (C:\temp is a good place) along with the [[Media:Usbser.zip|usbser.inf]] file. Windows then creates an extra COMx port that you can use in a terminal program or with ucenter.&lt;br /&gt;
To use the USB tunnel make sure you first power the autopilot before connecting USB not to end up in the USB bootloader.&lt;br /&gt;
&lt;br /&gt;
== Firmware Architecture ==&lt;br /&gt;
More info on the firmware architecture &amp;lt;br&amp;gt;&lt;br /&gt;
[[FirmwareArchitecture]]&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
As a rapidly evolving open-source project, on occasion your software may fail to compile after a [[Installation#Software_Updates|SVN Update]]. This is most likely due to a new or changed variable name that is now required in your airframe, flight plan or somewhere else. Since the user-configured files are not updated automatically you may need to view the most recently changed sample airframe or flight plan files to find the required changes.&amp;lt;br&amp;gt;&lt;br /&gt;
See the [[Software_Troubleshooting|Software Troubleshooting]] page for help with common compilation errors.&lt;br /&gt;
&lt;br /&gt;
[[Category:Software]] [[Category:User_Documentation]] [[Category:Developer_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9269</id>
		<title>Infrared Sensors</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9269"/>
		<updated>2011-04-11T05:53:05Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
__NOEDITSECTION__&lt;br /&gt;
&lt;br /&gt;
{|style=&amp;quot;border-spacing:8px;margin:0px -8px&amp;quot; class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:100%;border:1px solid #9999bf;background-color:#f5fffa;vertical-align:top;color:#000; text-align: left;&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;h3 style=&amp;quot;-moz-border-radius-topright: 1em;-moz-border-radius-topleft: 1em; &lt;br /&gt;
background:#cedff2;margin:-2px;padding:4px;&amp;quot;&amp;gt;&lt;br /&gt;
[[Image:favicon32.png|32px]] Infrared Sensors&lt;br /&gt;
&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;padding:6px;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infrared_Sensors}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;!-- Start of right-column --&amp;gt;&lt;br /&gt;
| class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:70%;border:1px solid #cedff2;background-color:#f5fffa;vertical-align:top&amp;quot;|&lt;br /&gt;
{|width=&amp;quot;100%&amp;quot; cellpadding=&amp;quot;2&amp;quot; cellspacing=&amp;quot;5&amp;quot; style=&amp;quot;vertical-align:top;background-color:#f5fffa&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| &amp;lt;h2 style=&amp;quot;margin:0;background-color:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&amp;quot;&amp;gt;Hardware support for previous, currently in use and future infrared boards.&amp;lt;/h2&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:Ir_dual.jpg|IRH early design&lt;br /&gt;
Image:Ir_sensor_single_rotated.jpg|IRV early design&lt;br /&gt;
Image:Irsensors.jpg|New smaller and slimmer Paparazzi IRH and IRV sensor boards&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See also [[Paparazzi_Infrared_Sensors]] for hardware.&lt;br /&gt;
&lt;br /&gt;
== Infrared Stabilization Principle ==&lt;br /&gt;
The paparazzi autopilot uses infrared thermopiles for primary attitude sensing.  The theory is that at zero bank or pitch angle, the difference in the heat between the two sensors should be zero, and at 90 degrees it should be maximum.  From this relationship a linear regression is made and angles are calculated during flight.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted.png|400px|Two axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
Each pair of sensors measures one axis, a minimum of 2 pairs must be used to measure pitch and roll but best results are obtained thru the use of a 3&amp;lt;sup&amp;gt;rd&amp;lt;/sup&amp;gt; pair on the vertical axis.  Since the output signal from each sensor pair is proportional to both the attitude and the weather/terrain, systems with only x-y sensors require a ground calibration and may not provide accurate angle calculations as the aircraft travels over terrain with different IR radiation.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted_with_Z.png|400px|Three axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Architecture ==&lt;br /&gt;
&lt;br /&gt;
=== Horizontal Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_dual.jpg]]&lt;br /&gt;
&lt;br /&gt;
=== Vertical Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_single.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Thermopiles ==&lt;br /&gt;
&lt;br /&gt;
The Thermopiles are:&lt;br /&gt;
&lt;br /&gt;
* Manufacturer Part Number:	MLX90247-ESF-DSA ([http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;amp;name=MLX90247ESF-DSA-ND Digi-Key])&lt;br /&gt;
* Description:	IC SENS THERMOPILE W/THERM TO-39&lt;br /&gt;
* [http://www.melexis.com/Asset/IR-Sensor-MLX90247-DataSheet-DownloadLink-4763.aspx data sheet] (Melexis site)&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9139</id>
		<title>Infrared Sensors</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9139"/>
		<updated>2011-03-14T00:42:01Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
__NOEDITSECTION__&lt;br /&gt;
&lt;br /&gt;
{|style=&amp;quot;border-spacing:8px;margin:0px -8px&amp;quot; class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:100%;border:1px solid #9999bf;background-color:#f5fffa;vertical-align:top;color:#000; text-align: left;&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;h3 style=&amp;quot;-moz-border-radius-topright: 1em;-moz-border-radius-topleft: 1em; &lt;br /&gt;
background:#cedff2;margin:-2px;padding:4px;&amp;quot;&amp;gt;&lt;br /&gt;
[[Image:favicon32.png|32px]] Infrared Sensors&lt;br /&gt;
&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;padding:6px;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infrared_Sensors}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;!-- Start of right-column --&amp;gt;&lt;br /&gt;
| class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:70%;border:1px solid #cedff2;background-color:#f5fffa;vertical-align:top&amp;quot;|&lt;br /&gt;
{|width=&amp;quot;100%&amp;quot; cellpadding=&amp;quot;2&amp;quot; cellspacing=&amp;quot;5&amp;quot; style=&amp;quot;vertical-align:top;background-color:#f5fffa&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| &amp;lt;h2 style=&amp;quot;margin:0;background-color:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&amp;quot;&amp;gt;Hardware support for previous, currently in use and future infrared boards.&amp;lt;/h2&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:Ir_dual.jpg|IRH early design&lt;br /&gt;
Image:Ir_sensor_single_rotated.jpg|IRV early design&lt;br /&gt;
Image:Irsensors.jpg|New smaller and slimmer Paparazzi IRH and IRV sensor boards&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
See also [[Paparazzi_Infrared_Sensors]] for hardware.&lt;br /&gt;
&lt;br /&gt;
== Infrared Stabilization Principle ==&lt;br /&gt;
The paparazzi autopilot uses infrared thermopiles for primary attitude sensing.  The theory is that at zero bank or pitch angle, the difference in the heat between the two sensors should be zero, and at 90 degrees it should be maximum.  From this relationship a linear regression is made and angles are calculated during flight.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted.png|400px|Two axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
Each pair of sensors measures one axis, a minimum of 2 pairs must be used to measure pitch and roll but best results are obtained thru the use of a 3&amp;lt;sup&amp;gt;rd&amp;lt;/sup&amp;gt; pair on the vertical axis.  Since the output signal from each sensor pair is proportional to both the attitude and the weather/terrain, systems with only x-y sensors require a ground calibration and may not provide accurate angle calculations as the aircraft travels over terrain with different IR radiation.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted_with_Z.png|400px|Three axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Architecture ==&lt;br /&gt;
&lt;br /&gt;
=== Horizontal Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_dual.jpg]]&lt;br /&gt;
&lt;br /&gt;
=== Vertical Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_single.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Thermopiles ==&lt;br /&gt;
&lt;br /&gt;
The Thermopiles are:&lt;br /&gt;
&lt;br /&gt;
Manufacturer Part Number:	MLX90247-ESF-DSA ([http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;amp;name=MLX90247ESF-DSA-ND Digi-Key])&lt;br /&gt;
&lt;br /&gt;
Description:	IC SENS THERMOPILE W/THERM TO-39&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9138</id>
		<title>Infrared Sensors</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Infrared_Sensors&amp;diff=9138"/>
		<updated>2011-03-14T00:38:53Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
__NOEDITSECTION__&lt;br /&gt;
&lt;br /&gt;
{|style=&amp;quot;border-spacing:8px;margin:0px -8px&amp;quot; class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:100%;border:1px solid #9999bf;background-color:#f5fffa;vertical-align:top;color:#000; text-align: left;&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;h3 style=&amp;quot;-moz-border-radius-topright: 1em;-moz-border-radius-topleft: 1em; &lt;br /&gt;
background:#cedff2;margin:-2px;padding:4px;&amp;quot;&amp;gt;&lt;br /&gt;
[[Image:favicon32.png|32px]] Infrared Sensors&lt;br /&gt;
&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;padding:6px;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infrared_Sensors}}&lt;br /&gt;
&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;!-- Start of right-column --&amp;gt;&lt;br /&gt;
| class=&amp;quot;MainPageBG&amp;quot; style=&amp;quot;width:70%;border:1px solid #cedff2;background-color:#f5fffa;vertical-align:top&amp;quot;|&lt;br /&gt;
{|width=&amp;quot;100%&amp;quot; cellpadding=&amp;quot;2&amp;quot; cellspacing=&amp;quot;5&amp;quot; style=&amp;quot;vertical-align:top;background-color:#f5fffa&amp;quot;&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
| &amp;lt;h2 style=&amp;quot;margin:0;background-color:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3bfb1;text-align:left;color:#000;padding:0.2em 0.4em;&amp;quot;&amp;gt;Hardware support for previous, currently in use and future infrared boards.&amp;lt;/h2&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
|&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:Ir_dual.jpg|IRH early design&lt;br /&gt;
Image:Ir_sensor_single_rotated.jpg|IRV early design&lt;br /&gt;
Image:Irsensors.jpg|New smaller and slimmer Paparazzi IRH and IRV sensor boards&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
|}&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Hardware:&lt;br /&gt;
 * [[Infrared_Double_Small_Sensor_Board]]&lt;br /&gt;
&lt;br /&gt;
== Infrared Stabilization Principle ==&lt;br /&gt;
The paparazzi autopilot uses infrared thermopiles for primary attitude sensing.  The theory is that at zero bank or pitch angle, the difference in the heat between the two sensors should be zero, and at 90 degrees it should be maximum.  From this relationship a linear regression is made and angles are calculated during flight.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted.png|400px|Two axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
Each pair of sensors measures one axis, a minimum of 2 pairs must be used to measure pitch and roll but best results are obtained thru the use of a 3&amp;lt;sup&amp;gt;rd&amp;lt;/sup&amp;gt; pair on the vertical axis.  Since the output signal from each sensor pair is proportional to both the attitude and the weather/terrain, systems with only x-y sensors require a ground calibration and may not provide accurate angle calculations as the aircraft travels over terrain with different IR radiation.&lt;br /&gt;
&lt;br /&gt;
[[Image:Infrared_Stabilisation_Principle_tilted_with_Z.png|400px|Three axis infrared attitude measurement]]&lt;br /&gt;
&lt;br /&gt;
== Hardware Architecture ==&lt;br /&gt;
&lt;br /&gt;
=== Horizontal Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_dual.jpg]]&lt;br /&gt;
&lt;br /&gt;
=== Vertical Board ===&lt;br /&gt;
&lt;br /&gt;
[[Image:IR_Sensor_Board_Architecture_single.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Thermopiles ==&lt;br /&gt;
&lt;br /&gt;
The Thermopiles are:&lt;br /&gt;
&lt;br /&gt;
Manufacturer Part Number:	MLX90247-ESF-DSA ([http://search.digikey.com/scripts/DkSearch/dksus.dll?Detail&amp;amp;name=MLX90247ESF-DSA-ND Digi-Key])&lt;br /&gt;
&lt;br /&gt;
Description:	IC SENS THERMOPILE W/THERM TO-39&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8815</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8815"/>
		<updated>2011-03-03T05:54:07Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
* EasyStar.&lt;br /&gt;
* 450W 1.2m EPP wing (&amp;lt;1kg, based on windrider Beevolution)&lt;br /&gt;
* 650W 2.5m EPP wing (&amp;gt;3kg, based on windrider QueenBee)&lt;br /&gt;
&lt;br /&gt;
My current development focus is driven by:&lt;br /&gt;
&lt;br /&gt;
* a local OBC effort for 2011 (CanberraUAV), even though it's ArduPilot based :)&lt;br /&gt;
* a civillian &amp;quot;reconossance for off-road convoy&amp;quot; use-case.&lt;br /&gt;
* a livestock-tracking application.&lt;br /&gt;
&lt;br /&gt;
I'm currently working on:&lt;br /&gt;
&lt;br /&gt;
* evaluation of a possible MavLink &amp;lt;--&amp;gt; Ivy/Paparazzi &amp;quot;bridge&amp;quot;, so components of a Papparazzi UAS could interoperate components based on the MavLink protocol (e.g. QGroundControl).&lt;br /&gt;
* A dedicated EZ* for playing with the bomb navigation subsystem at night.&lt;br /&gt;
&lt;br /&gt;
I also plan to start getting into OpenCV in a few months. And maybe a TWOG/Asprin IMU project (if someone makes an asprin driver for it).&lt;br /&gt;
&lt;br /&gt;
Note to self: check this out some time [[DevGuide/USB-Serial]].&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8814</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8814"/>
		<updated>2011-03-03T05:22:02Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but it's not a good way to reach me.&lt;br /&gt;
* I rabble-rouse on GitHub as monkeypants.&lt;br /&gt;
* my eBay persona is monkeypants007.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I fly fixed-wing foam planes with Twogs/Tinys and IR;&lt;br /&gt;
&lt;br /&gt;
* EasyStar.&lt;br /&gt;
* 450W 1.2m EPP wing (&amp;lt;1kg, based on windrider Beevolution)&lt;br /&gt;
* 650W 2.5m EPP wing (&amp;gt;3kg, based on windrider QueenBee)&lt;br /&gt;
&lt;br /&gt;
My current development focus is driven by:&lt;br /&gt;
&lt;br /&gt;
* a local OBC effort for 2011 (CanberraUAV), even though it's ArduPilot based :)&lt;br /&gt;
* a civillian &amp;quot;reconossance for off-road convoy&amp;quot; use-case.&lt;br /&gt;
* a livestock-tracking application.&lt;br /&gt;
&lt;br /&gt;
I'm currently working on:&lt;br /&gt;
&lt;br /&gt;
* evaluation of a possible MavLink &amp;lt;--&amp;gt; Ivy/Paparazzi &amp;quot;bridge&amp;quot;, so components of a Papparazzi UAS could interoperate components based on the MavLink protocol (e.g. QGroundControl).&lt;br /&gt;
* A dedicated EZ* for playing with the bomb navigation subsystem at night.&lt;br /&gt;
&lt;br /&gt;
I also plan to start getting into OpenCV in a few months.&lt;br /&gt;
&lt;br /&gt;
Note to self: check this out some time [[DevGuide/USB-Serial]].&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8813</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8813"/>
		<updated>2011-03-03T04:41:39Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
= Who is this rufus character ?=&lt;br /&gt;
&lt;br /&gt;
* My name is Chris Gough, some people call me rufus (for reasons I don't fully understand).&lt;br /&gt;
* the best way to reach me is christopher (dot) d (dot) gough (at) gmail.com.&lt;br /&gt;
* my skype identity is christopher.d.gough, but you'd be lucky to catch me.&lt;br /&gt;
* on GitHub I'm monkeypants, but I haven't actually used it much.&lt;br /&gt;
* my eBay persona is monkeypants007, mostly a buyer.&lt;br /&gt;
* my phone number is (+61) 418441605 (a mobile, I don't have a land-line).&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
* http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
Aren't you glad you checked my wiki page.&lt;br /&gt;
&lt;br /&gt;
Note to self: check this out some time [[DevGuide/USB-Serial]].&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8796</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=8796"/>
		<updated>2011-03-01T01:18:00Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I'm a paparazzi enthusuiast from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;br /&gt;
&lt;br /&gt;
Note to self - [[DevGuide/USB-Serial]]&lt;br /&gt;
&lt;br /&gt;
I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=FunJet&amp;diff=8792</id>
		<title>FunJet</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=FunJet&amp;diff=8792"/>
		<updated>2011-02-28T10:23:07Z</updated>

		<summary type="html">&lt;p&gt;Rufus: undid some spam&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[http://www.recherche.enac.fr/paparazzi/wiki/index.php/Airframes &amp;lt;&amp;lt;] Back to Airframes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-valign=&amp;quot;top&amp;quot;&lt;br /&gt;
|[[Image:Funjet_flight_dawnron1.jpg|thumb|left|Multiplex FunJet]]&lt;br /&gt;
|&lt;br /&gt;
The MultiPlex FunJet is an electric pusher-prop jet made of very durable Elapor Particle Foam Construction.  It offers plenty of room internally for avionics in an attractive package.&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Features ==&lt;br /&gt;
&lt;br /&gt;
* Suggested Retail Price of $65 USD&lt;br /&gt;
* Elapor Particle Foam construction&lt;br /&gt;
* Assembles in minutes with only Medium CA glue&lt;br /&gt;
* Fiberglass Wing Spar&lt;br /&gt;
* Moderately priced&lt;br /&gt;
* Detachable canopy for access to internals&lt;br /&gt;
* Plastic Motor Mount&lt;br /&gt;
* Wide flight speed envelope (slow without stalling, through fast)&lt;br /&gt;
&lt;br /&gt;
== Specifications ==&lt;br /&gt;
&lt;br /&gt;
* Wingspan: 31.29&amp;quot; (795mm)&lt;br /&gt;
* Wing Area: 232 sq in (15 sq dm)&lt;br /&gt;
* Weight: 21oz (620g) _all up_&lt;br /&gt;
* Weight w/o powerplant (for estimation): 330g&lt;br /&gt;
* Bare weight: 165g&lt;br /&gt;
* Length: 29.52&amp;quot; (750mm)&lt;br /&gt;
* Airfoils: Airfoil: Semi-symmetrical, mid wing at the fuselage sides&lt;br /&gt;
&lt;br /&gt;
=== Payload Area ===&lt;br /&gt;
&lt;br /&gt;
* Fuselage is 1.60&amp;quot; (40.6mm) wide x 20&amp;quot; long&lt;br /&gt;
&lt;br /&gt;
== Recommended Setups ==&lt;br /&gt;
&lt;br /&gt;
=== Manufacturer Recommendation ===&lt;br /&gt;
&lt;br /&gt;
Remember this is a hot sport plane so the manufacturers recommendation reflects typical desired performance and may not be the best match for UAV operations.&lt;br /&gt;
&lt;br /&gt;
* Motor: Himax HB2815-3000 Brushless Motor&lt;br /&gt;
* Battery: 3S1P 2100-3200mah LiPo&lt;br /&gt;
* Servos: 2 Nano sized (HS-55)&lt;br /&gt;
&lt;br /&gt;
=== Group Member Setups ===&lt;br /&gt;
&lt;br /&gt;
====Martin====&lt;br /&gt;
&lt;br /&gt;
* Motor: AXI 2212/26&lt;br /&gt;
* Battery: 3S1P 2100mAh LiPo&lt;br /&gt;
* Prop: 9x6&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
====Matthew Currie====&lt;br /&gt;
{|&lt;br /&gt;
|[[Image:FJ_MC_ANGLE.jpg|thumb|left|Multiplex FunJet]]&lt;br /&gt;
|[[Image:FJ_MC_SIDE.jpg|thumb|left|Multiplex FunJet]]&lt;br /&gt;
|[[Image:FJ_UNDERSIDE.JPG|thumb|left|Multiplex FunJet]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
* Motor: AXI 2212/26&lt;br /&gt;
* Battery: LiPower Lites 3S1P 2100mAh 18C LiPo&lt;br /&gt;
* Prop: APC 9x6E (checked to draw ~ 11.5A)&lt;br /&gt;
* Receiver: Berg 4L&lt;br /&gt;
* Servos: 2x Hitec HS-55&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
====ENAC Team====&lt;br /&gt;
{|&lt;br /&gt;
|[[Image:Funjet_2_DigIR_049.jpg|thumb|left|ENAC Team special setup Multiplex FunJet]]&lt;br /&gt;
|[[Image:Funjet_2_DigIR_033.jpg|thumb|left|ENAC Team special setup Multiplex FunJet]]&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Servos ===&lt;br /&gt;
&lt;br /&gt;
Multiplex calls for 2 Hitec HS-55 or 2 HS-65 servos&lt;br /&gt;
&lt;br /&gt;
=== Hitec HS-55 ===&lt;br /&gt;
&lt;br /&gt;
* MSRP: $13 USD&lt;br /&gt;
* Torque: 13/16 oz/in @ 4.8/6.0v&lt;br /&gt;
* Speed: 0.09/0.08 seconds/ 60deg @ 4.8/6.0v&lt;br /&gt;
* Weight: 0.29 oz (7.8g)&lt;br /&gt;
* Size: 0.9 x 0.46 x 0.95&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Hitec HS-65HB ===&lt;br /&gt;
&lt;br /&gt;
* MSRP: &lt;br /&gt;
* Motor Type: 3 Pole Ferrite&lt;br /&gt;
* Bearing Type: Top Ball Bearing&lt;br /&gt;
* Torque 4.8/6.0v: 22 / 26 oz (1.6 / 1.9 kg.)&lt;br /&gt;
* Speed 4.8/6.0v: 0.16 / 0.13 second&lt;br /&gt;
* Size: 0.9&amp;quot;x 0.5&amp;quot;x 0.9&amp;quot; (24 x 12 x 24m)&lt;br /&gt;
* Weigh : 0.39oz. 11.2 g.&lt;br /&gt;
&lt;br /&gt;
== Recommended Motors ==&lt;br /&gt;
'''Himax HB2815-3000 Brushless Motor'''&lt;br /&gt;
&lt;br /&gt;
[http://www.maxxprod.com/pdf/HB2815-xx00.pdf PDF Datasheet]&lt;br /&gt;
&lt;br /&gt;
* MSRP $69.95 USD&lt;br /&gt;
* Dimensions: 27mm x 38mm&lt;br /&gt;
* Weight: 86g&lt;br /&gt;
* KV: 3000&lt;br /&gt;
* Max Amps: 30A&lt;br /&gt;
* Max Watts: 275W&lt;br /&gt;
&lt;br /&gt;
'''AXI 2212/26'''&lt;br /&gt;
&lt;br /&gt;
http://www.modelmotors.cz/index.php?page=61&amp;amp;product=2212&amp;amp;serie=26&amp;amp;line=GOLD&lt;br /&gt;
&lt;br /&gt;
MSRP $69.95 USD&lt;br /&gt;
* Dimensions: 1-3/32&amp;quot; diameter, 1-3/16&amp;quot; case length, 3.17mm (1/8&amp;quot;) shaft&lt;br /&gt;
* Weight: 57 g&lt;br /&gt;
* KV: 920&lt;br /&gt;
* Max Amps: 12A&lt;br /&gt;
* Max Watts: 275W&lt;br /&gt;
* Prop's: &lt;br /&gt;
9x6, 24.5 ounce thrust, 14:12 full throttle.&lt;br /&gt;
&lt;br /&gt;
8x6, 19.5 ounce thrust, 19:38 full throttle.&lt;br /&gt;
&lt;br /&gt;
== Funjet Back Plate Construction ==&lt;br /&gt;
{|&lt;br /&gt;
|[[Image:Funjet_Back_Plate_Components.jpg|thumb|left|Funjet back plate construction components]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
* A suitable precursor for the back plate is 5mmx75mmx75mm balsa sandwiched by 1mmx75mmx75mm plywood. The laminating adhesive used was PVA glue. The sandwich was left to dry overnight clamped by similar size wooden plates in a vice.&lt;br /&gt;
&lt;br /&gt;
* An outline of The 7mm elapor profile, cut from the back of the Funjet canopy, is drawn in a CAD/CAM program.    &lt;br /&gt;
:*download ''[[Media:Funjet_Back_Plate_CADopia.pdf|Funjet back plate CADopia drawing (pdf)]]''&lt;br /&gt;
&lt;br /&gt;
* A laser cutting firm transferred this outline to CorelDraw and cut an acrylic (Perspex) template.&lt;br /&gt;
:*download ''[[Media:Funjet_Back_Plate_CorelDraw .pdf|Funjet back plate CorelDraw drawing (pdf)]]''&lt;br /&gt;
&lt;br /&gt;
* The balsa/plywood sandwich was attached by double sided tape to the acrylic template and the correct outline achieved by routing around the acrylic border.&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|[[Image:Funjet_Back_Plate_Fitted.jpg|thumb|left|Funjet back plate fitted]]&lt;br /&gt;
|[[Image:Tiny_v2_1_Funjet.jpg|thumb|left|Tiny v2.1 in a Funjet]]&lt;br /&gt;
|}&lt;br /&gt;
* The fitted plate looks remarkably similar to that displayed in the image on the right found on the main page of the wiki.&lt;br /&gt;
&lt;br /&gt;
== Online Discussion on FunJet topics ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.rcgroups.com/forums/showpost.php?p=7257031&amp;amp;postcount=2856 Modifying the motor cowling to increase airflow]&lt;br /&gt;
* [http://www.rcgroups.com/forums/showthread.php?p=7593625#post7593625 Adding prop spacers to move prop further back]&lt;br /&gt;
* [http://www.rcgroups.com/forums/showpost.php?p=7081811&amp;amp;postcount=2582 Mounting a MicroDan 2505 Brushless Outrunner]&lt;br /&gt;
&lt;br /&gt;
== Photos ==&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
|-&lt;br /&gt;
|[[Image:Jet-motor-mount.jpg|thumb|Included Motor Mount]]&lt;br /&gt;
|[[Image:Funjet_highvis1_rycomm.jpg|thumb|Example of high visibility paint job]]&lt;br /&gt;
|[[Image:Funjet tipprotector sharkbyte.jpg|thumb|Idea for wing tip skid]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Misc Notes ==&lt;br /&gt;
&lt;br /&gt;
* [http://www.recherche.enac.fr/paparazzi/wiki_images/FunJet_Manual_English.pdf Multiplex FunJet Instruction Manual - English]&lt;br /&gt;
* [http://www.recherche.enac.fr/paparazzi/wiki_images/FunJet_Manual_Multilanguage.pdf Multiplex FunJet Instruction Manual - Original Multilanguage]&lt;br /&gt;
* Painting Elapor should be primed [http://www.phillsmodels.com/acatalog/index.html?http%3A//www.phillsmodels.com/acatalog/Online_Catalogue_Paint_882.html&amp;amp;CatalogBody primer]&lt;br /&gt;
* Fiberglass wing spar: 22.5&amp;quot; (571mm) x .25&amp;quot; (6.35mm)&lt;br /&gt;
* Motor Screws (to hold plastic motor plate to plastic motor cowl) are slot head and appear to be 3.0mm x 0.5mm (thread) x 16mm long&lt;br /&gt;
* Screws for AXI &amp;quot;outrunner&amp;quot; motor are 3.0mm Diameter x 0.5mm Thread x 6 mm Length&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Contributing&amp;diff=8413</id>
		<title>Contributing</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Contributing&amp;diff=8413"/>
		<updated>2011-01-18T02:14:46Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== How to contribute ==&lt;br /&gt;
There are of course lots of ways to contribute to Paparazzi and get involved.&lt;br /&gt;
&lt;br /&gt;
Help is always welcome on all aspects of the project. May this be documentation, wiki, maintenance, electronics or code contributions/fixes.&lt;br /&gt;
&lt;br /&gt;
=== Wiki ===&lt;br /&gt;
Just create an account and you can start adding information, cleaning it up or just fixing some typo you just noticed :-)&lt;br /&gt;
&lt;br /&gt;
=== Software development ===&lt;br /&gt;
We use the distribute version control system [http://git-scm.com/ git]. The [http://github.com/paparazzi/paparazzi/ papaprazzi master repo is hosed on github].&lt;br /&gt;
&lt;br /&gt;
Please also see the [[Git|git wiki page]] for more details about setting up git and cloning the repo.&lt;br /&gt;
&lt;br /&gt;
Here is the short version if you already know git:&lt;br /&gt;
# Create an account on [http://github.com/ github].&lt;br /&gt;
# Fork the [http://github.com/paparazzi/paparazzi/ papaprazzi repo] on github. (After logging in press the '''fork''' button).&lt;br /&gt;
# '''git clone git@github.com:&amp;lt;yourname&amp;gt;/paparazzi.git'''&lt;br /&gt;
# fix/code&lt;br /&gt;
# Send us a [http://help.github.com/pull-requests/ pull request] on github.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=ATmega168_PPM_Encoder_Board&amp;diff=8357</id>
		<title>ATmega168 PPM Encoder Board</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=ATmega168_PPM_Encoder_Board&amp;diff=8357"/>
		<updated>2011-01-09T23:52:23Z</updated>

		<summary type="html">&lt;p&gt;Rufus: makefile edits so LED blinks correctly on ATmega168  hardware&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;p&amp;gt;Thanks to Chris we have a way to use virtually any RC receiver with Paparazzi without any modifications to the receiver.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;This board plugs into the servo output ports on a R/C receiver and encodes them into a single PPM pulse suitable for the paparazzi autopilot. It is also possible to remap channels by changing the connection between the receiver and the encoder. Want Tx ch5 to be output on ch7 of the ppm stream? Just connect the Ch5 signal from the receiver to the Ch7 input on the encoder.&amp;lt;/p&amp;gt;&lt;br /&gt;
[[Image:Ppmencv3_sm.jpg|250px]]&lt;br /&gt;
&lt;br /&gt;
Note: see the [[ATmega328_PPM_Encoder_Board]] page for the more recent hardware version. Wiki refactor in progress, these pages will be merged.&lt;br /&gt;
&lt;br /&gt;
= Programming the PPM encoder =&lt;br /&gt;
&amp;lt;p&amp;gt;Programming the board can easily be accomplished using an AVR ISP (in-serial programming) programmer.  These are inexpensive and can be found many places online.  Once you have the ISP connected to the PPM encoder, simply use avrdude with the following command:&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;avrdude -p atmega168 -P &amp;lt;Insert port here&amp;gt; -c &amp;lt;Insert ISP type here&amp;gt; -U lfuse:w:0b00100010:m -U efuse:w:0b111:m -U flash:w:servo2ppm+bootloader.hex&amp;lt;/code&amp;gt;&lt;br /&gt;
-----&lt;br /&gt;
'''Source files'''&lt;br /&gt;
:*Link to firmware file: ''[[http://www.rcgroups.com/forums/showpost.php?p=14347844&amp;amp;postcount=2445 PPM Encoder Eagle and latest (4.3 Feb 2010) firmware (zip)]]''&lt;br /&gt;
&lt;br /&gt;
The above link is to ATmega326 firmware. If you load that onto ATmega168 hardware, the LED won't blink as described in the users manual (but otherwise the PPM encoder seems to work). To build firmware that works correctly on the ATmega168 hardware, edit the makefile. Find this:&lt;br /&gt;
&lt;br /&gt;
 # The below fuse settings are for the 328p&lt;br /&gt;
 #Low fuse is the same for the mega 328 and mega 168&lt;br /&gt;
 LOW_FUSE_328 = 0xDF&lt;br /&gt;
 #High fuse sets sets the bootsize on 328 and the bodlevel in 168&lt;br /&gt;
 HIGH_FUSE_328 = 0xD8&lt;br /&gt;
 #Extended fuse sets the bodlevel only on 328 but it sets the bootsize on 168&lt;br /&gt;
 EXTENDED_FUSE_328 = 0xFC&lt;br /&gt;
 LOCK_FUSE_328 = 0xFF&lt;br /&gt;
&lt;br /&gt;
and replace with:&lt;br /&gt;
&lt;br /&gt;
 # The below fuse settings are for the mega168&lt;br /&gt;
 #Low fuse is the same for the mega 328 and mega 168&lt;br /&gt;
 LOW_FUSE_168 = 0xC2&lt;br /&gt;
 #High fuse sets sets the bootsize on 328 and the bodlevel in 168&lt;br /&gt;
 HIGH_FUSE_168 = 0xDC&lt;br /&gt;
 #Extended fuse sets the bodlevel only on 328 but it sets the bootsize on 168&lt;br /&gt;
 EXTENDED_FUSE_168 = 0xF8&lt;br /&gt;
 LOCK_FUSE_168 = 0xFF&lt;br /&gt;
&lt;br /&gt;
Then &amp;quot;make program&amp;quot; (to write the fllash) and &amp;quot;make fuse_write&amp;quot; (to write the fuses).&lt;br /&gt;
&lt;br /&gt;
'''Gerber &amp;amp; Drill files'''&lt;br /&gt;
:*download &amp;quot;[[Media:Eagle_pcb.zip|PPM Encoder Eagle design files 4.3(zip)]]&amp;quot;&lt;br /&gt;
:*download ''[[Media:Gerber_for_PPM_Encoder.zip|PPM Encoder gerber &amp;amp; drill files (zip)]]''&lt;br /&gt;
:*download &amp;quot;[[Media:Servo2ppm_manual_v4_2.pdf|PPM Encoder manual (PDF)]]&amp;quot;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=ATmega328_PPM_Encoder_Board&amp;diff=8356</id>
		<title>ATmega328 PPM Encoder Board</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=ATmega328_PPM_Encoder_Board&amp;diff=8356"/>
		<updated>2011-01-09T23:48:56Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;p&amp;gt;Thanks to Chris we have a way to use virtually any RC receiver with Paparazzi without any modifications to the receiver.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;This board plugs into the servo output ports on a R/C receiver and encodes them into a single PPM pulse suitable for the paparazzi autopilot. It is also possible to remap channels by changing the connection between the receiver and the encoder. Want Tx ch5 to be output on ch7 of the ppm stream? Just connect the Ch5 signal from the receiver to the Ch7 input on the encoder.&amp;lt;/p&amp;gt;&lt;br /&gt;
[[Image:Ppmencv3_sm.jpg|250px]]&lt;br /&gt;
&lt;br /&gt;
Note: see the [[ATmega168_PPM_Encoder_Board]] page for the more recent hardware version. Wiki refactor in progress, these pages will be merged.&lt;br /&gt;
&lt;br /&gt;
= Programming the PPM encoder =&lt;br /&gt;
&amp;lt;p&amp;gt;Programming the board can easily be accomplished using an AVR ISP (in-serial programming) programmer.  These are inexpensive and can be found many places online.  Once you have the ISP connected to the PPM encoder, simply use avrdude with the following command:&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;code&amp;gt;avrdude -p atmega168 -P &amp;lt;Insert port here&amp;gt; -c &amp;lt;Insert ISP type here&amp;gt; -U lfuse:w:0b00100010:m -U efuse:w:0b111:m -U flash:w:servo2ppm+bootloader.hex&amp;lt;/code&amp;gt;&lt;br /&gt;
-----&lt;br /&gt;
'''Source files'''&lt;br /&gt;
:*Link to firmware file: ''[[http://www.rcgroups.com/forums/showpost.php?p=14347844&amp;amp;postcount=2445 PPM Encoder Eagle and latest (4.3 Feb 2010) firmware (zip)]]''&lt;br /&gt;
'''Gerber &amp;amp; Drill files'''&lt;br /&gt;
:*download &amp;quot;[[Media:Eagle_pcb.zip|PPM Encoder Eagle design files 4.3(zip)]]&amp;quot;&lt;br /&gt;
:*download ''[[Media:Gerber_for_PPM_Encoder.zip|PPM Encoder gerber &amp;amp; drill files (zip)]]''&lt;br /&gt;
:*download &amp;quot;[[Media:Servo2ppm_manual_v4_2.pdf|PPM Encoder manual (PDF)]]&amp;quot;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=RC_Receivers_and_Radios&amp;diff=8110</id>
		<title>RC Receivers and Radios</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=RC_Receivers_and_Radios&amp;diff=8110"/>
		<updated>2010-11-24T04:01:37Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* Receiver RX-7-SYNTH IPD receiver [http://www.multiplex-rc.de/hp/produkte/artikel_detail.jsp?lfdnr=55880&amp;amp;action=add2notice&amp;amp;qty=1&amp;amp;cachenepper=1227896925116 Multiplex-rc.de] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== 2.4GHz Systems==&lt;br /&gt;
To use a 2.4 GHz system a few requirements are necessary&lt;br /&gt;
# Must use ppm encoder board. (See [[Get_Hardware|Get Hardware]] page for suppliers) (Except for the Futaba FASST 7 channel receiver R617FS that has a 5 (not 7) channels combined pulse)&lt;br /&gt;
# Needs a three position switch&lt;br /&gt;
# Ability to set failsafe to any or at least 1 channel (pprz-mode) as desired&lt;br /&gt;
# At least one extra channel beyond those needed to control the servos and motor. (throttle-roll-pitch-mode)&lt;br /&gt;
=== Radios ===&lt;br /&gt;
&lt;br /&gt;
====Futaba FASST 7-channel receiver====&lt;br /&gt;
&lt;br /&gt;
[[Image:FAST7ch.jpg|thumb|right]]&lt;br /&gt;
&lt;br /&gt;
* Pin 8 (upper right corner in picture) of the small IC on the right contains 5 PPM pulses and can go directly to paparazzi. Pulse 6 and 7 go directly to the servos. &lt;br /&gt;
* Best is to remove the resistors of one of the channels and connect a small wire to pin 8 to get the combined 5 pulses on the robust 1/10th inch header.&lt;br /&gt;
* Do not forget to use channel 3 (only failsafe channel) as mode switch with fail safe &amp;quot;throttle off&amp;quot; as mode 2.&lt;br /&gt;
&lt;br /&gt;
====Spektrum DX-7====&lt;br /&gt;
[[Image:DX7.jpg|thumb|left]]&lt;br /&gt;
*7 Channels &lt;br /&gt;
* 20-Model memory&lt;br /&gt;
* Airplane and Heli software&lt;br /&gt;
* Switch assignment&lt;br /&gt;
* P-mixes&lt;br /&gt;
* Includes 4 powerful DS821 digital servos with high-tech resin gears&lt;br /&gt;
* 3-axis dual rate &amp;amp; expo&lt;br /&gt;
* 3-position flap (Airplane)&lt;br /&gt;
* 5-point throttle curve (Heli)&lt;br /&gt;
* 3 flight modes plus hold (Heli)&lt;br /&gt;
* Gyro programming (Heli)&lt;br /&gt;
* CCPM, 2-servo 90°, 3-servo 90°, &amp;amp; 3-servo 120°&lt;br /&gt;
* Price $320-$350&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
===== Switch Assignment =====&lt;br /&gt;
To assign the three position switch to any other channel but channel 7 follow these steps:&lt;br /&gt;
# Set up aux2(refers to aux2 on rx not the switch on the tx. aka ch7) with its input selected as 3 pos switch.&lt;br /&gt;
# Set up this mix - Gear to Gear (Up=-100, Down=-100, Offset =0). This inhibits the gear switch.&lt;br /&gt;
# Set up another mix - Aux2 to Gear (Up=100, Down=100, Offset = 0).&lt;br /&gt;
Notes: &lt;br /&gt;
#Gear on a DX-7 Air is Channel 5 and AUX2 is CH7. Once again i am referring to the inputs which are labeled on the RX not what the switches are named on the TX. If your using a DX-7 heli please substitute the names for what the rx channels are named into this guide&lt;br /&gt;
# DX7 Heli the 3-pos switch is named &amp;quot;flight mode&amp;quot;&lt;br /&gt;
# DX7 Air the 3-pos switch is named &amp;quot;flaps&amp;quot;&lt;br /&gt;
&lt;br /&gt;
===== Failsafe Setup =====&lt;br /&gt;
To set up the mode channel (3 pos switch) to default to auto2 if connection is lost between rx and tx follow these steps:&lt;br /&gt;
# Put 3 position Switch into AUTO2 Position&lt;br /&gt;
# Put in bind plug&lt;br /&gt;
# Power up&lt;br /&gt;
# REMOVE the bind plug&lt;br /&gt;
# Power up Tx while pushing bind button&lt;br /&gt;
# Wait until light becomes steady and not blinking (it may become steady right off but will then start blinking again so let it go at least 5 seconds)&lt;br /&gt;
&lt;br /&gt;
== PCM Systems ==&lt;br /&gt;
# Must use ppm encoder board. (See [[Get_Hardware|Get Hardware]] page for suppliers)&lt;br /&gt;
# Needs a three position switch&lt;br /&gt;
# Ability to set failsafe to any channel as desired&lt;br /&gt;
# At least one extra channel beyond those needed to control the servos and motor.&lt;br /&gt;
&lt;br /&gt;
== PPM Based Systems ==&lt;br /&gt;
=== Configuration ===&lt;br /&gt;
The [[Radio_Control]] page describes how to set up the radio.xml config file.&lt;br /&gt;
&lt;br /&gt;
=== Requirements ===&lt;br /&gt;
To use a 72/35/40/41 MHz **(uses ppm) system a few requirements are necessary&lt;br /&gt;
# Need a Transmitter with a three position switch&lt;br /&gt;
# At least one extra channel beyond those needed to control the servos and motor.&lt;br /&gt;
# A modified receiver which outputs the ppm signal. &lt;br /&gt;
===Adding a 3 position switch===&lt;br /&gt;
===== Futaba T6EXAP =====&lt;br /&gt;
For this particular transmitter, the Potentiometer on channel 6 can be replaced with a 3 position switch. Channel 5 appears not to be connected to an ADC converter; therefore it will not support a 3 position switch.&lt;br /&gt;
#Disconnect the potentiometer being careful not to shorten the wires&lt;br /&gt;
#Solder the switch and resistors onto the wires using the wiring diagram as a reference. (Any two equal value resistors should work). I used 10k resistors.&lt;br /&gt;
[[Image:SwitchWiringDiagram.JPG|thumb|left|Switch wiring diagram]]&lt;br /&gt;
[[Image:3positionswitch.JPG|thumb|left|Switch installed in transmitter]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
Suitable 3 position switches:&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
RS Components: [http://australia.rs-online.com/web/search/searchBrowseAction.html?method=getProduct&amp;amp;R=344-710 344-710]&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
Mouser: [http://au.mouser.com/Search/Refine.aspx?Keyword=633-M202402-RO 633-M202402-RO]&lt;br /&gt;
&lt;br /&gt;
=== R/C Receiver Interface===&lt;br /&gt;
All versions of the Paparazzi autopilot include a connector to interface with a standard R/C receiver for manual or semi-autonomous control during the testing and tuning phases.  Two interface options exist:&lt;br /&gt;
# Tap into the PPM signal running between the RF section and the servo driver of your receiver and route it to the Paparazzi.  Let the Paparazzi generate individual servo signals and connect all servos directly to the autopilot.  This method requires only 3 wires to the receiver (power and PPM), is compatible with all Paparazzi autopilots, and provides 8 manual R/C channels and the potential for more autonomous channels regardless of the capability of the R/C receiver.&lt;br /&gt;
# Cut the PPM trace and route it thru the autopilot and back to the receiver, using the servo driver IC on your R/C receiver to drive the servos.  This option requires 4 wires (Ground, PPM-in, PPM-out, Reset) and your receiver must have a supported servo driver IC.  This allows you to use the large servo connectors on your R/C receiver and does not require any modification to your servos or ESC but does require you to cut a trace on your R/C receiver and limits the number of servos to the capacity of your receiver.  Compatible with Classix and Tiny 1.1.&lt;br /&gt;
# Note that on the Classix the PPM_in pin is FOO2... &lt;br /&gt;
[[Image:RC_Receiver_Timing_Diagram.jpg|thumb|left|PPM Timing Diagram&amp;lt;small&amp;gt;Note 1: Exact value not critical. Depending on RC Transmitter type &amp;amp; Manufacturer.&amp;lt;br&amp;gt;Note 2: Depending on Transmitter number of Channels and t,,n,, durations.&amp;lt;br&amp;gt;Note 3: Not critical. Depending on Synchro detection method.&amp;lt;/small&amp;gt;]]&lt;br /&gt;
[[Image:RC_Receiver_Tiny.jpg|thumb|left|3-Wire setup, driving servos from the autopilot]]&lt;br /&gt;
[[Image:RC_Receiver_classix.jpg|thumb|left|4-Wire setup, driving servos from the R/C receiver]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Common demux chips ===&lt;br /&gt;
&lt;br /&gt;
Typical used chips are the cmos [http://www.doctronics.co.uk/4015.htm 4015] and [http://www.doctronics.co.uk/4017.htm 4017]. &lt;br /&gt;
&lt;br /&gt;
The 4015 uses either pin 1 or pin 9 for the clock and the input is on 7 and 15. The 4017 has just one shift register and has its clock input on pin 14 and the enable on pint 13.&lt;br /&gt;
&lt;br /&gt;
In most receivers you are after the clock; though some may be pulsed; in which case you need the enable. Note that the 4017 enable has inverted logic (low to be enabled) whereas the input on the 4015 can be either (typically high). If the enable pin is held low (4017) or if the input pin (4015) is held high always;e.g. connected to the ground or the Vcc - then it is fair to assume that the PPM signal is most propably on the clock input. &lt;br /&gt;
&lt;br /&gt;
=== Recommended 35/40Mhz R/C Receivers ===&lt;br /&gt;
&lt;br /&gt;
Note that there is information on modifying other receiver models at [http://mikrokopter.de/ucwiki/RC-Empf%C3%A4nger mikrokopter.de]. It's in German however the pictures contain most of the information or use google translate.&lt;br /&gt;
Shielded wire is recommended for receiver and autopilot connection, as unshielded one may cause noise in receiver. &lt;br /&gt;
&lt;br /&gt;
=====Futaba FP-R116FB 6 Channel FM 35MHz receiver=====&lt;br /&gt;
[[Image:Rc_fut_web.jpg|thumb|left|Wiring of a Futaba R136]]&lt;br /&gt;
*Orange wire is connected to PPM signal&lt;br /&gt;
*Red wire is connected to VCC&lt;br /&gt;
*Brown wire is connected to GND&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Futaba R136F 6 Channel FM receiver=====&lt;br /&gt;
[[Image:rx_futaba136.jpg|thumb|left|Wiring of a Futaba R136]]&lt;br /&gt;
*41 MHz&lt;br /&gt;
*White wire is connected to PPM signal&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
=====Futaba R168DF 8 Channel dual FM receiver=====&lt;br /&gt;
[[Image:rx_futaba168df.jpg|thumb|left|Wiring of a Futaba R168DF]]&lt;br /&gt;
*35 MHz&lt;br /&gt;
*PPM wire is connected to 862 receiver pin on the board. VCC and GND is on the 8/B original position.&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====ACT Micro-6 FM receiver=====&lt;br /&gt;
[[Image:rx_act_micro-6.jpg|thumb|left|Wiring of a ACT Micro-6]]&lt;br /&gt;
*Available in 35 or 40 MHz versions&lt;br /&gt;
*White wire is connected to PPM signal&lt;br /&gt;
*[http://www.acteurope.com/Micro_6anl.pdf Datasheet (German)]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====ACT DSL-4top [http://www.mikrokopter.de/ucwiki/DSL4top mikrokopter.de] version=====&lt;br /&gt;
[[Image:DSL4top.jpg|thumb|left|DSL-4top mikrokopter.de version]]&lt;br /&gt;
* Special version for mikrokopter.de - Only available in their [https://www.mikrocontroller.com/index.php?main_page=product_info&amp;amp;products_id=215&amp;amp;zenid=8ce8bab70f3e9d684e01f724316d9690 shop]!&lt;br /&gt;
* '''Outputs PPM directly''' on the channel 1 connector!&lt;br /&gt;
* No soldering necessary&lt;br /&gt;
* ACT Lifetime warranty&lt;br /&gt;
* Sells for ~45 euro&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Futaba R115F 5 Channel FM receiver=====&lt;br /&gt;
[[Image:pprz_rx115.jpg|thumb|left|Wiring of a Futaba R115]]&lt;br /&gt;
*Available in 35 and 40 MHz versions&lt;br /&gt;
*White wire is connected to PPM signal&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
=====JETI REX 5 plus (no MPD) receiver=====&lt;br /&gt;
[[Image:520_Jeti_5_plus.jpg|thumb|left|Wiring of a REX 5]]&lt;br /&gt;
&lt;br /&gt;
*Popular Czech made micro r/c receiver, available in 35 or 40 MHz versions&lt;br /&gt;
*´folded´ PCB design with parts inside, mostly inaccessable&lt;br /&gt;
*Small grey wire is connected to via with PPM signal&lt;br /&gt;
*Unusual connector used for testing, soldering recommended&lt;br /&gt;
*shielded wire recommended, this one taken from PC parts recycling (former soundcard to m/b connector cable)&lt;br /&gt;
*[http://www.jetimodel.cz/eng/navody_en/rex5_eng.pdf Datasheet (English)]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
[[Image:DSC02414.JPG|thumb|left|other Layout of REX 5]]&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=====Receiver RX-7-SYNTH IPD receiver [http://www.multiplex-rc.de/hp/produkte/artikel_detail.jsp?lfdnr=55880&amp;amp;action=add2notice&amp;amp;qty=1&amp;amp;cachenepper=1227896925116 Multiplex-rc.de]=====&lt;br /&gt;
[[Image:RX-7-SYNTH_IPD.jpg|thumb|left|Wiring of RX-7-SYNTH IPD]]&lt;br /&gt;
&lt;br /&gt;
*Available in 35, 36 and 40 MHz versions&lt;br /&gt;
*A compact, high-quality 7-channel single-conversion FM / PPM IPD receiver&lt;br /&gt;
*Easy modification through connectors, see pictures&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==== Protech 5FM 35 mHz Receiver ====&lt;br /&gt;
&lt;br /&gt;
The low cost Protech '5FM' receiver makes use of an SMD version of the standard 74AHC164[http://www.ic-on-line.cn/IOL/datasheet/74ahct164_18057.pdf] 8 bit shift register; you are after PIN 1 of this chip. The circuit board has a testpad for just this pin at the top side of the circuit board.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;gallery&amp;gt;&lt;br /&gt;
Image:protech-5fm.jpg|Figure 1. &amp;lt;br&amp;gt;Protech 5FM 35 mHZ Receiver, mark 2&lt;br /&gt;
Image:protech-5fm-pad.jpg|Figure 2. &amp;lt;br&amp;gt; PPM tap location for the Protech 5FM receiver, near the 74AHC164 shift register&lt;br /&gt;
Image:protech-5fm-scope.jpg|Figure 3.&amp;lt;br&amp;gt; Protech 5FM PPM signal - not very clean/digital&lt;br /&gt;
&amp;lt;/gallery&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Two physical versions exist; the older one [http://www.protech.be/Manuals/PRO205manual%20web.pdf] and a newer one pictured (fig 1). It has been distributed by protech with various ready-to-fly planes; such as the Skyraider[http://www.modelbouwforum.nl/forums/beginners/50677-protech-skyraider.html].&lt;br /&gt;
&lt;br /&gt;
The solder/testpad you are after the one right next the 74x164 chip its pin 1. In this image it has a jellow wire soldered to it (the yellow wire at the top left is the normal antenna connector (fig 2). Note however that the signal is not very clean (1v/div) - which may cause issues - as shown in the above image (fig 3). &lt;br /&gt;
&lt;br /&gt;
This is further compunded by the relatively noisy electrical engines; which are not brushless. A ferrite coil does not seem to help enough - Papparazi and GPS loose sync often through Xbee. Replacing the engine by a brushless outrunnen resolve the issue completely.&lt;br /&gt;
&lt;br /&gt;
==== Profi Penta 35 MHz ====&lt;br /&gt;
[[Image:DSC00547.JPG]]&lt;br /&gt;
[[Image:DSC00545.JPG]]&lt;br /&gt;
&lt;br /&gt;
=== Recommended 72Mhz R/C Receivers ===&lt;br /&gt;
====Castle Creations [http://www.castlecreations.com/products/berg_ms4l.html Berg 4L]====&lt;br /&gt;
[[Image:berg4L.jpg|thumb|Wiring of a Berg 4L]]&lt;br /&gt;
* Expect fantastic performance from these $40 USD parts but be warned that they are known to have unreliable crystal sockets and brittle antenna wire.  The ''Berg 7'' channel receiver should work equally well and is known to have a better crystal socket - note that either receiver will provide '''8 channels''' in manual R/C mode when used with Paparazzi.  Note: the rugged ''Berg 4'' cannot be modified, only the ''Berg 4L'' and ''Berg 7''.&lt;br /&gt;
To Modify a Berg4L, follow these instructions:&lt;br /&gt;
# Remove the shrink wrap. Use a good knife and be careful to not damage any of the components on the receiver. I would recommend that you cut on the sides (edge of the PCB) to be sure to avoid damaging the shielding&lt;br /&gt;
# Desolder the headers. We will not use them with tiny AP as the servos are connected directly to the AP. This is pretty easy to do when you have a hot air rework station. If you don't have one, your best bet is to cut the header off and remove the left over pins one by one with a regular iron. There is a piece of shielding material that is connected to one of the ground pins of the header. You need to remove it carefully from the header without damaging it and re-solder it to the gnd pad.&lt;br /&gt;
# You need to solder 3 wires to the receiver. Gnd, +5V and PPM. To locate the PPM signal, first locate the PIC micro controller close to the location of the headers. The PPM signal is on the corner pin closest to the corner of the receiver. Soldering a 28guage wire directly to the PIN isn't very difficult. For the power connection, use the pads that were used for the header. The outside pin is Gnd, the second pin is +5V. What I did is solder the wires on the pad going straight down, then I looped the 3 wires 360 degrees and glued them to the PCB with hot glue. This provides good strain relief.&lt;br /&gt;
# While you have the PCB in your hands, take the opportunity to remove the crystal connector and solder your crystal directly to the PCB for added reliability.&lt;br /&gt;
# I also used some hot glue to add more strain relief to the antenna&lt;br /&gt;
# Use some large shrink wrap to cover the entire receiver again&lt;br /&gt;
=====Hitec Electron 6 72MHz Reciever=====&lt;br /&gt;
This was written for MNAV from crossbow but is still usable with PPRZ.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
[[Image:Electron6mod.jpg]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=====Corona Synthesized Dual-Conv Receiver 8Ch=====&lt;br /&gt;
[http://www.corona-rc.com/coproductshowE.asp?ArticleID=63 manual] &amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
This receiver is available in 27,35,36,40,72 mhz and a Synthesized receiver, meaning you do not need to change frequency crystals.&lt;br /&gt;
&lt;br /&gt;
How to modify for combined signal&lt;br /&gt;
&lt;br /&gt;
# Cut the 8th channel PWM output pin near the PCB.&lt;br /&gt;
# Connected a pin from the Atmel (see picture) to the 8th channel PWM signal. (optionally, weaving the wire through some holes on the board.) Make sure you have a fine tip on your soldering iron and a magnifying glass strapped to your head! &lt;br /&gt;
# Glue the wire down (CA works)&lt;br /&gt;
# Be sure to glue the pin that you cut in place (previously, being soldered to the board was holding the pin in place)&lt;br /&gt;
&lt;br /&gt;
It is maybe possible to reprogram the atmel with your own firmware. If you succeed in this plz add relevant info here.&lt;br /&gt;
&lt;br /&gt;
That pin provides a 1V to 2V signal, it works with the PPRZ, although its a bit gittery (the slew rate is not real good).&lt;br /&gt;
[[Image:Corona_Synthesized_Receiver_72Mhz_bottom.jpg|thumb]]&lt;br /&gt;
[[Image:Corona_Synthesized_Receiver_72Mhz_top.jpg|thumb]]&lt;br /&gt;
[[Image:Corona_Synthesized_Receiver_72Mhz_top_atmel.jpg]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==433MHz UHF Systems==&lt;br /&gt;
&lt;br /&gt;
Note that in most countries an amateur radio license is required to use 433MHz UHF.&lt;br /&gt;
&lt;br /&gt;
===Scherrer UHF===&lt;br /&gt;
&lt;br /&gt;
[[Image:ScherrerUHF.jpg|thumb|left|Scherrer UHF Rx]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.webx.dk/rc/uhf-link3/uhf-link3.htm Scherrer UHF] is a high quality diversity radio control system. It has a PPM output and can be connected directely to Paparazzi. A ppm encoder board is not required. It has an RSSI output.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===ImmersionRC EzUHF===&lt;br /&gt;
&lt;br /&gt;
[[Image:EzUHFTx.jpg|thumb|left|ImmersionRC Tx]]&lt;br /&gt;
&lt;br /&gt;
The [http://www.immersionrc.com/products.htm ImmersionRC EzUHF] is a high quality diversity radio control system. It does not have a PPM output. A ppm encoder board is required to connect to Paparazzi. It connects directely to EzOSD and the TrackR2 which enables RSSI monitoring and head tracking for FPV.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7819</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7819"/>
		<updated>2010-09-17T02:02:00Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com [[image:aerofu_logo.png]]  aerofu.com ] =&lt;br /&gt;
&lt;br /&gt;
Low cost Paparazzi hardware direct from Australia. &lt;br /&gt;
Now with an [http://aerofu.com/index.php?main_page=page&amp;amp;id=2 export license] for 33 countries (including Europe and North America). That means we usually ship immediately, no more permiting delay.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=30 Tiny] &lt;br /&gt;
and&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=31 TWOG]&lt;br /&gt;
autopilots.&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
Complete Kits ([http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=48 Tiny] or [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=11&amp;amp;products_id=49 TWOG] based).&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
[http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=10&amp;amp;products_id=20 PPM Encoders] and [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=8&amp;amp;products_id=44 IR Sensors] from the Paparazzi project.&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
A couple of [http://www.aerofu.com/index.php?main_page=index&amp;amp;cPath=9 modem] options.&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;&lt;br /&gt;
Inexpensive [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=7&amp;amp;products_id=12 uBlox LEA-5H GPS units].&lt;br /&gt;
 &amp;lt;/li&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;PCBs (coming soon)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7818</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7818"/>
		<updated>2010-09-17T01:25:48Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
Australian Paparazzi hardware specialist, now [http://aerofu.com/index.php?main_page=page&amp;amp;id=2 licensed to export to 33 countries]. That means immediate shipping, no more delays.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits (and individual bits)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7809</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7809"/>
		<updated>2010-09-14T06:58:59Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
Australian Paparazzi hardware specialist, now [http://aerofu.com/index.php?main_page=page&amp;amp;id=2 licensed to export to 33 countries]. That means immediate shipping, no more delays.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits (and individual bits)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Prices are so low that it's worth logging in to see them :)&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7808</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7808"/>
		<updated>2010-09-14T06:57:51Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
Australian Paparazzi hardware specialist, now [http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=15&amp;amp;products_id=47 licensed to export to 33 countries]. That means immediate shipping, no more delays.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits (and individual bits)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Prices are so low that it's worth logging in to see them :)&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7807</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7807"/>
		<updated>2010-09-14T06:57:20Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
Australian Paparazzi hardware specialist, now [http://http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=15&amp;amp;products_id=47 licensed to export to 33 countries]. That means immediate shipping, no more delays.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits (and individual bits)&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Prices are so low that it's worth logging in to see them :)&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7806</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7806"/>
		<updated>2010-09-14T06:48:17Z</updated>

		<summary type="html">&lt;p&gt;Rufus: /* [http://aerofu.com Aerofu.com] */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
Paparazzi hardware specialists based in Australia.&lt;br /&gt;
Now licenced to export to 33 countries, see [http://http://www.aerofu.com/index.php?main_page=product_info&amp;amp;cPath=15&amp;amp;products_id=47 this page] for details.&lt;br /&gt;
For most customers that means no more delays, immediate shipping. &lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits and various bits&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi [[Image:CheBuzzPprz.gif]] CheBuzz Paparazzi] =&lt;br /&gt;
CheBuzz Paparazzi is back!  Thanks to all for your patience during my absence and as a thank you, I have lowered prices!  I am still located in the EU and that means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;[https://mini.ppzuav.com Visit the PPZUAV WebStore to see the latest offerings.]&amp;lt;/p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=7292</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=7292"/>
		<updated>2010-08-10T13:19:45Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[image:aerofu_logo.png]]&lt;br /&gt;
&lt;br /&gt;
Hi, I'm Chris Gough, and I like sending rambling left-handed emails to the paparazi mailing list and taking long walks on the beach.&lt;br /&gt;
&lt;br /&gt;
Despite rumors to the contrary I'm DEFINITELY NOT this guy:&lt;br /&gt;
&lt;br /&gt;
http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
I'm a software developer from Canberra (Australia) and the guy behind [http://aerofu.com aerofu.com].&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7291</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7291"/>
		<updated>2010-08-10T13:09:08Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com Aerofu.com] =&lt;br /&gt;
&lt;br /&gt;
[http://aerofu.com [[image:aerofu_logo.png]]]&lt;br /&gt;
&lt;br /&gt;
A brand new Paparazzi hardware supplier based in Australia.&lt;br /&gt;
&lt;br /&gt;
Currently stocking:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
 &amp;lt;li&amp;gt;Tiny and TWOG based systems&amp;lt;/li&amp;gt; &lt;br /&gt;
 &amp;lt;li&amp;gt;Complete kits and various bits&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&lt;br /&gt;
International orders are welcome, but due to Australian [http://www.aerofu.com/index.php?main_page=page&amp;amp;id=2 export control] laws they will experience some delay. The Aerofu site has a [http://www.aerofu.com/index.php?main_page=index&amp;amp;cPath=15 simple, free process] that preempts the red-tape and keeps the delay to a minimum. &lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi CheBuzz Paparazzi] =&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;h3&amp;gt;*Note - Due to my professional obligations, my webstore has temporarily been suspended until at least June 1, 2010.&amp;lt;/h3&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
CheBuzz Paparazzi is proud to become the first reseller of Paparazzi equipment in the EU.  That means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV will be limiting sales to assemblies only (i.e. no bundles) during August/Sept. We need a Summer Break.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
[http://www.ppzuav.com/osc Visit the PPZUAV WebStore to see the latest offerings.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Aerofu_logo.png&amp;diff=7290</id>
		<title>File:Aerofu logo.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Aerofu_logo.png&amp;diff=7290"/>
		<updated>2010-08-10T12:57:31Z</updated>

		<summary type="html">&lt;p&gt;Rufus: logo for aerofu.com&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;logo for aerofu.com&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7289</id>
		<title>Get Hardware</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Get_Hardware&amp;diff=7289"/>
		<updated>2010-08-10T12:55:13Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;As an open-source project, all source code and hardware plans are [http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/hw/?root=paparazzi freely available on the SVN Server] for anyone to produce, use, modify, and redistribute in accordance with the [http://www.gnu.org/licenses/gpl.txt GPL License Agreement] which requires only that the open-source nature of the project be maintained by all who redistribute it.&lt;br /&gt;
&lt;br /&gt;
We encourage the distribution of hardware for profit or otherwise and invite any users with paparazzi-related hardware to post links and purchasing information on this page.  Please use the [[Talk:Get_Hardware&amp;amp;action=edit|Discussion Tab]] to describe your experiences with any of these vendors.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;hr&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://aerofu.com AeroFu] =&lt;br /&gt;
A brand new Paparazzi hardware supplier based in Australia.&lt;br /&gt;
&lt;br /&gt;
Currently stocking Tiny and TWOG systems as complete kits (or various bits).&lt;br /&gt;
&lt;br /&gt;
International orders are welcome, but due to Australian [http://www.aerofu.com/index.php?main_page=page&amp;amp;id=2 export control] laws they will experience some delay. The Aerofu site has a [http://www.aerofu.com/index.php?main_page=index&amp;amp;cPath=15 simple, free process] that preempts the red-tape and reduces the delay to a minimum. &lt;br /&gt;
&lt;br /&gt;
= [http://chebuzz.com/paparazzi CheBuzz Paparazzi] =&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;h3&amp;gt;*Note - Due to my professional obligations, my webstore has temporarily been suspended until at least June 1, 2010.&amp;lt;/h3&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
CheBuzz Paparazzi is proud to become the first reseller of Paparazzi equipment in the EU.  That means faster shipping, no packages getting stuck in customs, and no having to pay import duties!  All equipment is thoroughly tested.  Your equipment is guaranteed to work upon arrival.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;h3&amp;gt;My Current Offerings:&amp;lt;/h3&amp;gt;&lt;br /&gt;
&amp;lt;ul&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=1 Tiny and TWOG customizable kits]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2 Tiny 2.11, TWOG, PPM Decoders and more]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=1 Horizontal IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=product_info&amp;amp;cPath=2&amp;amp;products_id=3 Vertical IR sensor]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=3 DIY components]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php?main_page=index&amp;amp;cPath=4 Cables and adapters]&lt;br /&gt;
&amp;lt;li&amp;gt;[http://chebuzz.com/paparazzi/index.php Much more!]&lt;br /&gt;
&amp;lt;/ul&amp;gt;&lt;br /&gt;
&amp;lt;br&amp;gt;Credit card processing on my [http://chebuzz.com/paparazzi/ website] is approved and installed! It is now my preferred form of payment.  I also will accept other most other common forms of payment.  E-mail me chebuzz@gmail.com to arrange other forms of payment.&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Trying to answer some common questions, I strive to make everything as &amp;quot;plug and play&amp;quot; as possible for you.  So of course that means the bootloader and GPS have been preprogrammed.  The PPM encoder is also preprogrammed and ready to go with the latest bootloader and firmware.  Kits come with all the cables necessary.  If you have any other suggestions, I would love to hear them.  Please email me and let me know.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.jobyrobotics.com/ [[Image:JobyRobotics.jpg]]] JobyRobotics.com [[Image:Lisa_L_top.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]][[Image:Lisa_L_bot.jpg|thumb|400px|Lisa/L STM32/Overo autopilot]] =&lt;br /&gt;
Joby Robotics is a young company which aims at delivering cutting edge and affordable solutions for hobby, research and industrial robotics.&lt;br /&gt;
 &lt;br /&gt;
Joby Robotics products are geared toward open standards and are, in particular, compatible with the Paparazzi free autopilot code base&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= [http://www.olimex.com/pcb/ Olimex] =&lt;br /&gt;
[[image:pcb-green.jpg|thumb|400px|Olimex PCBs]]&lt;br /&gt;
Fast PCB Prototypes&lt;br /&gt;
[http://www.olimex.com/pcb/ www.olimex.com/pcb]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.ppzuav.com/ [[Image:Ppzuav.jpg]]] PPZUAV.com [[Image:All ppz autopilots med.jpg|thumb|400px|All Paparazzi Autopilots]]=&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV Bundles will not be available during August and September.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;Apologies but only the bundles will be unavailable during this time to give me a summer break. The web shop will be open and shipping autopilots and accessories. You will just need to buy [http://uk.rs-online.com/web/search/searchBrowseAction.html?method=searchProducts&amp;amp;searchTerm=279-9516&amp;amp;x=0&amp;amp;y=0 the pre-made pre-crimped wiring] from online to complete your own wiring.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;h3&amp;gt;Our Items&amp;lt;/h3&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=122&amp;amp;osCsid=3sjpnaknjhgnaj2d0n69rib5ibmj41fn Booz IMU] &amp;lt;--need an IMU for that autopilot?&amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/product_info.php?products_id=110&amp;amp;osCsid=3qmme6ltuhngigah29mo08lm3jmck2np Booz GPS] &amp;lt;--need GPS for that Booz? &amp;lt;br&amp;gt;&lt;br /&gt;
*[https://mini.ppzuav.com/osc/index.php?cPath=2&amp;amp;osCsid=7kioth9gusks9iiqhjcd67kkcff7vj8o Paparazzi Autopilots] &amp;lt;--Hurry only a couple TWOG left &amp;lt;br&amp;gt;&lt;br /&gt;
*[http://www.ppzuav.com/osc/product_info.php?products_id=91 PPM Decoder Board] &amp;lt;--NEW item. Chris has made a perfect PPM encoder!!!&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Confused what to buy? Just give us an email and we will help you decide ('''sales@ppzuav.com''').&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;We make it simple. Each autopilot is &amp;lt;b&amp;gt;professionally assembled&amp;lt;/b&amp;gt; in a large factory by automated pick and place and reflow to ISO9000 standards. To be sure yours will work we open every one and test before shipping. If it fails we don't sell it.&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;The testsi:&lt;br /&gt;
&amp;lt;ol&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Power it with a current limited power supply to verify voltages and current draw&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Load the usb bootloader so it can be programmed via USB&amp;lt;/li&amp;gt;&lt;br /&gt;
&amp;lt;li&amp;gt;Configure the GPS module for Paparazzi&lt;br /&gt;
&amp;lt;li&amp;gt;Load a sample aircraft program and verify the program runs correctly. &lt;br /&gt;
&amp;lt;li&amp;gt;Verify the programmed LEDs flash correctly &lt;br /&gt;
&amp;lt;li&amp;gt;Then acquires a 3D fix in Paparazzi GCS using a direct serial uplink from the autopilot to the GCS&lt;br /&gt;
&amp;lt;/ol&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
Please eMail with any questions or special requests before you place your orders. We return emails as quickly as possible. If it's an easy question within hours. More complex or longer explanation requests may take some time to read then write your answer so be patient.&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
&amp;lt;p&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;PPZUAV will be limiting sales to assemblies only (i.e. no bundles) during August/Sept. We need a Summer Break.&amp;lt;/h2&amp;gt;&lt;br /&gt;
&amp;lt;/p&amp;gt;&lt;br /&gt;
[http://www.ppzuav.com/osc Visit the PPZUAV WebStore to see the latest offerings.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= [http://www.sparkfun.com Sparkfun] =&lt;br /&gt;
[[image:P1030095.jpg|thumb|400px|Sparkfun]]&lt;br /&gt;
Sparkfun is a great source of miscellaneous electronics like:&lt;br /&gt;
* Gyros&lt;br /&gt;
* Accelerometers&lt;br /&gt;
* Pressure sensors&lt;br /&gt;
* Ultrasonic distance sensors&lt;br /&gt;
* Temperature/humidity sensors&lt;br /&gt;
* USB to Serial converters&lt;br /&gt;
* LEDs&lt;br /&gt;
* Etc.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=6983</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=6983"/>
		<updated>2010-07-22T03:33:23Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, I'm Chris Gough and I hail from from Canberra, Australia. Despite rumours to the contrary, I'm NOT this guy:&lt;br /&gt;
&lt;br /&gt;
http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
Instead, I'm a software developer, working as a technical manager for the Australian Government (Dept. of Environment). Among other things, my interest in Paparazzi is as a nice technical challenge to keep me sane after reading/writing documents and going to meetings all day.&lt;br /&gt;
&lt;br /&gt;
My paparazzi rig is still an EasyStar, but I'll move that into my much larger QueenBee flying wing sooner or later... along with an FPV video kit (if I can figure out how to stop it jamming the modem) and a still camera. I regularly practice my manual control with an overpowered Windrider Bee (450W@900g, propped for ~40m/s). It's a bit twitchy but it bounces better than a funjet. I'm also gradually tooling-up my shed for vacuum bagging projects, but have no plans, time or space for a homebuilt CNC router (more's the pity).&lt;br /&gt;
&lt;br /&gt;
I use a TWOG, 2.4 Mhz zigbee modems use 36MHz radio gear.&lt;br /&gt;
&lt;br /&gt;
Long term, I'd like to routinely patrol/survey a farm taking geo-referenced digital photographs, and develop a ground-based post-processing facility to stitch/authorectify/etc them into a geodatabase...  I entertain the fantasy of one day building an automated kangaroo/cow/plant detector.&lt;br /&gt;
&lt;br /&gt;
I know a friendly farmer who lets me fly over her 300 Acre paddock, home to 90 cows (and probably as many kangaroos). I'm pretty sure my flights there are safe and legal.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=6982</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=6982"/>
		<updated>2010-07-22T01:02:45Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, I'm Chris Gough and I hail from from Canberra, Australia. Despite rumours to the contrary, I'm DEFINTELY NOT this guy:&lt;br /&gt;
&lt;br /&gt;
http://www.sott.net/articles/show/205982-Meet-Lt-Col-Chris-Gough-Killing-by-Drone-and-Proud-of-It&lt;br /&gt;
&lt;br /&gt;
Instead, I'm a software developer by trade, working as a technical manager for the Australian Government (Dept. of Environment). Among other things, my interest in Paparazzi is as a nice technical challenge to keep me sane after reading/writing documents and going to meetings all day.&lt;br /&gt;
&lt;br /&gt;
My paparazzi rig is still currently an EasyStar, but I'll move that into my much larger QueenBee flying wing sooner or later (along with my FPV video kit, and a still camera). I practice a manual skills with an overpowered Windrider Bee (450W@900g, propped for ~40m/s). A bit twitchy but it bounces better than a funjet. I'm also gradually tooling-up my shed for vacuum bagging projects, but have no plans (or time and space) for a homebuilt CNC router.&lt;br /&gt;
&lt;br /&gt;
I have a TWOG, 2.4 Mhz zigbee modems use 36MHz radio gear.&lt;br /&gt;
&lt;br /&gt;
Long term, I'd like to routinely patrol/survey a farm taking geo-referenced digital photographs, and develop a ground-based post-processing facility to stitch/authorectify/etc them into a geodatabase...  I entertain the fantasy of one day building an automated kangaroo/cow/plant detector.&lt;br /&gt;
&lt;br /&gt;
I know a friendly farmer who lets me fly over her 300 Acre paddock, home to 90 cows (and probably as many kangaroos). I think my flights there are safe and legal.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=5438</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=5438"/>
		<updated>2009-09-04T00:47:55Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, I'm Chris Gough and I hail from from Canberra, Australia. Thank you for visiting my page here.&lt;br /&gt;
&lt;br /&gt;
I'm a software developer by trade, but I work as a manager for the Australian Government (Dept. of Environment). Among other things, my interest in Paparazzi is as a nice technical challenge to keep me sane after reading/writing documents and going to meetings all day.&lt;br /&gt;
&lt;br /&gt;
I've not yet had any flights with paparazzi. I have acquired an EasyStar and had lots of practice - to the point where I can now launch/land reliably in adverse conditions, such as the tree-lined ridge across the road from my house. I also just finished assembling a &amp;quot;Boomerang 40&amp;quot; aileron trainer and converting it to electric power (~800W), and I intend to learn to fly that competently before using it (or something similar) as a UAV  platform after the EasyStar .&lt;br /&gt;
&lt;br /&gt;
I have a TWOG from CheBuzz, a pair of 2.4 Mhz zigbee modems and some 36MHz radio gear. With the help of [http://www.mannberg.co.uk/paparazzi/?p=5 this page] I seem to have my modems to working :). I plan to do AUTO1 and AUTO2 flights with the EasyStar by the end of the month (September 2009) or early October.&lt;br /&gt;
&lt;br /&gt;
Longer term (hopefully by the end of Summer), I'd like to build a UAV that routinely patrols/surveys a moderately large area (farm) taking geo-referenced digital photographs, and develop a ground-based post-processing facility to stitch/authorectify/etc them to maintain raster layers in a geodatabase... Machine learning is a bit of a hobby of mine, and I entertain the fantasy of eventually one day building an automated kangaroo/cow/plant detector.&lt;br /&gt;
&lt;br /&gt;
I know a friendly farmer who will let me fly over their 300 Acre paddock, home to 90 cows (and probably as many kangaroos). I've started the process of learning what I have to do to make my surveys there safe and legal, and expect to have the necessary approvals in place by Christmas. &lt;br /&gt;
&lt;br /&gt;
But for now, my &amp;quot;UAV&amp;quot; is a rather odd looking small cardboard box with a USB socket, a (power) switch and some IR sensors on a coreflute stalk.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Users&amp;diff=5437</id>
		<title>Users</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Users&amp;diff=5437"/>
		<updated>2009-09-04T00:44:32Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi&lt;br /&gt;
&lt;br /&gt;
==Need help adding your information?==&lt;br /&gt;
To have your information added by another paparazzi user, please send me an [http://www.rcgroups.com/forums/showpost.php?p=6575288&amp;amp;postcount=1 EMAIL] at with the &lt;br /&gt;
following:&lt;br /&gt;
&lt;br /&gt;
*Name&lt;br /&gt;
*Email&lt;br /&gt;
*Location&lt;br /&gt;
*Hardware&lt;br /&gt;
*Join date&lt;br /&gt;
*Current activities / project status&lt;br /&gt;
&lt;br /&gt;
== Wiki pages ==&lt;br /&gt;
add a link to your users wiki page.&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]&lt;br /&gt;
&lt;br /&gt;
[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]&lt;br /&gt;
&lt;br /&gt;
==Asia==&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
|+ Asia&lt;br /&gt;
|-&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new  wing like funjet  &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Europe==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:st.jr_at_gmx.at TomS] || Graz, Austria || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.&lt;br /&gt;
 &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet  ||| 2008 || Many successful flights. &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL  ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation. &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane  ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.&lt;br /&gt;
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera  ||| 2008 || Many successful flights working on an osd module and weather probes. &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009  &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [[User:Flixr|FelixR]] || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Azores, Portugal || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 &amp;amp; MaxStream ||| 2008 || Just starting.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, Multiplex Mentor, Multiplex Funjet, Multiplex Fox, GWS Formosa ||| 2008 || Several AUTO2 flights, currently debugging&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:chebuzz_at_gmail.com David &amp;quot;Buzz&amp;quot; Carlson] || Cyprus || Tiny 2.11, Lynx EDF &amp;amp; GWS SloStick, 9XTend datalink ||| 2008 || Quite a few AUTO2 flights.  Plane currently grounded due to a TX run-in with a 1 year-old.  Currently working on getting new TX and completing CBP store setup.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:kostalexis@ece.upatras.gr AneMos-Group] || Patras, Greece || Tiny 2.11, Quadrotor VTOL  ||| 2008 || Working on IMU, Trying to implement Constrained Control for the quadrotor trajectory flight&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://paparazzi.enac.fr/wiki/User:VAMK Allan Ojala (VAMK)] || Vaasa, Finland || TWOG, with AC4790 radio and LEA-5H GPS  ||| 2009 || Just constructed my own first RC airplane SIG KADET.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:maik.hoepfel_at_web.de Maik Hoepfel] || Berlin, Germany || TWOG, Graupner Elektro Trainer S, Futaba 9C 35 Mhz ||| August 2009 || Getting started, planning to eventually use Paparazzi for a powered parachute&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| New User || 1 || 2 ||| 3 || 4 &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==North America==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]  &lt;br /&gt;
|Vancouver, WA [http://maps.google.com/maps?f=q&amp;amp;source=s_q&amp;amp;hl=en&amp;amp;geocode=&amp;amp;q=98663&amp;amp;sll=37.0625,-95.677068&amp;amp;sspn=64.664844,101.953125&amp;amp;ie=UTF8&amp;amp;ll=45.606112,-122.643471&amp;amp;spn=0.222411,0.398254&amp;amp;z=12 &amp;lt;span title=&amp;quot;Google Map of 98663&amp;quot;&amp;gt;98663&amp;lt;/span&amp;gt;] &lt;br /&gt;
|    Tiny v2.11  ||  Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:quill_at_u.washington.edu John Burt] [http://paparazzi.enac.fr/wiki/User:John_Burt wiki page]|| Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Initial flight tests w/ Easystar in AUTO1 &amp;amp; AUTO2.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:ogar0007@umn.edu Pat O'Gara] || St. Paul, MN || Tiny 2.11 and TWOG (PPZUAV)  |||Oct. 2008 ||  Completed and flown FunJet and Minimag in Auto 2. Currently rebuilding MiniMag as an improved development platform. &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV)  ||| 2007 ||  currently flying a 48 inch zagi, 80 inch under construction.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA   ||| Feb 2009 || &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV)  ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV)  ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. &lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV)  ||| January 2009 || Building 72&amp;quot; Flying Wings which will be used for remote sensing. Routine autonomous flight.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV)  ||| June 2007 || 2x72&amp;quot; 5x48&amp;quot; 1x60&amp;quot; Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU Fuel Cell UAV] || Fort Collins, Co || Tiny 2.11 + LEA-5H (PPZUAV), 2.4Ghz XBPro ||| Mar 2009 || Maiden flight complete Feb 28.  New Airframe in development.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:armz12@gmail.com Armen Gharibans] || La Jolla, California || Tiny2.11 (PPZUAV)  ||| March 2009 || UCSD Project with Multiplex Mentor.  Completed August 2, 2009. Several Successful Auto2 Flights.  A LOT of help from David Conger.&lt;br /&gt;
&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| New User || 1 || 2 ||| 3 || 4 &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Central America==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV).  Multiplex Mentor  ||| 2008 || Seven flights now. Flights 6 &amp;amp; 7 in Auto2. Now only a matter of fine tuning.&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| New User || 1 || 2 ||| 3 || 4 &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Australia==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.  &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up &lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison] || Neutral Bay, NSW || Tiny v2.11, Vertical + Horizontal IR sensors, XBee PRO modems, Futaba T6EXAP TX, Futaba R136F RX, Funjet,  MacBook laptop ||| August 2008 || Configuring before first flight.&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Africa==&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;text-align:center;background:black; color:blue&amp;quot;&lt;br /&gt;
! Name !! Location !! Hardware !! Joined !! Current activities / project status&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
| [mailto:w1_th@yahoo.com W1th] || South Africa KZN || TWOG V1 ,LEA-5H GPS , RF Modems XBee Pro 868 (CheBuzz) ||| July 2009  || New to this , Got TWOG,GPS etc interfacing with Laptop and working ..Made a website [http://www.best-bargains.co.za/scarf/paparazzi.html SCARF] of my struggle ...&lt;br /&gt;
|- style=&amp;quot;background:bisque; color:black&amp;quot;&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=5436</id>
		<title>User:Rufus</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=User:Rufus&amp;diff=5436"/>
		<updated>2009-09-04T00:36:47Z</updated>

		<summary type="html">&lt;p&gt;Rufus: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hi, I'm Chris Gough and I hail from from Canberra, Australia. Thank you for visiting my page here. I'm a software developer by trade, but I work as a manager for the Australian Government (Dept. of Environment). Among other things, my interest in Paparazzi is as a nice technical challenge to keep my sane after reading/writing documents and going to meetings all day.&lt;br /&gt;
&lt;br /&gt;
I've not yet had any flights with paparazzi. I have acquired an EasyStar and had lots of practice - to the point where I can now launch/land reliably in adverse conditions, such as the tree-lined ridge across the road from my house. I also just finished assembling a &amp;quot;Boomerang 40&amp;quot; aileron trainer and converting it to electric power (~800W), and I intend to learn to fly that competently before using it (or something similar) as a UAV  platform after the EasyStar .&lt;br /&gt;
&lt;br /&gt;
I have a TWOG from CheBuzz, a pair of 2.4 Mhz zigbee modems and some 36MHz radio gear. With the help of [http://www.mannberg.co.uk/paparazzi/?p=5 this page] I seem to have my modems to working :). I plan to do AUTO1 and AUTO2 flights with the EasyStar by the end of the month (September 2009) or early October.&lt;br /&gt;
&lt;br /&gt;
Longer term (hopefully by the end of Summer), I'd like to build a UAV that routinely patrols/surveys a moderately large area (farm) taking geo-referenced digital photographs, and develop a ground-based post-processing facility to stitch/authorectify/etc them to maintain raster layers in a geodatabase... machine learning is a bit of a hobby of mine, and I entertain the fantasy of eventually one day building an automated kangaroo/cow/plant detector.&lt;br /&gt;
&lt;br /&gt;
I know a friendly farmer who will let me fly over their 300 Acre paddock, home to 90 cows (and probably as many kangaroos). I've started the process of learning what I have to do to make my surveys there safe and legal, and expect to have the necessary approvals in place by Christmas. &lt;br /&gt;
&lt;br /&gt;
But for now, my &amp;quot;UAV&amp;quot; is a rather odd looking small cardboard box with a USB socket, a (power) switch and some IR sensors on a coreflute stalk.&lt;/div&gt;</summary>
		<author><name>Rufus</name></author>
	</entry>
</feed>