<?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=Kevindehecker</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=Kevindehecker"/>
	<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/wiki/Special:Contributions/Kevindehecker"/>
	<updated>2026-04-29T14:58:42Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.37.1</generator>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23874</id>
		<title>Xvert</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23874"/>
		<updated>2017-10-09T15:34:10Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 15%&amp;quot;&amp;gt;&amp;lt;categorytree style=&amp;quot;float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;&amp;quot; mode=pages&amp;gt;Autopilots&amp;lt;/categorytree&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[Image:XVert.jpg|right|500px|XVert]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 40%&amp;quot;&amp;gt;__TOC__&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
By default the [https://www.horizonhobby.com/product/airplanes/airplanes-14501--1/ready-to-fly/x-vert-vtol-rtf-efl1800 XVert] from [https://www.horizonhobby.com/ Horrizon Hobby] is a two-prop hybrid VTOL fixed wing, designed to be controlled with DSMX RC. It features a STM32F3 board, which can be reprogrammed with Paparazzi through SWD. A GPS, magneto en datalink can be added by using the expansion ports on this board so that autonomous flight can be achieved.&lt;br /&gt;
&lt;br /&gt;
= Getting started =&lt;br /&gt;
&lt;br /&gt;
== What you need==&lt;br /&gt;
# An XVert EFL1800&lt;br /&gt;
# The Hobbyking Joystick&lt;br /&gt;
# A Black Magic Probe (BMP) or similar SWD programmer&lt;br /&gt;
# A GPS + magneto&lt;br /&gt;
# An XBee datalink &lt;br /&gt;
# A laptop with Ubuntu and paparazzi installed&lt;br /&gt;
&lt;br /&gt;
Steps to follow: &lt;br /&gt;
# Upgrade the XVert with the XBee and GPS&lt;br /&gt;
# Install Paparazzi via [http://wiki.paparazziuav.org/wiki/Installation the one liner to be found here]. Just Cut 'n Paste (CTRL+C from webbrowser then CTRL+SHIFT+V in your Linux terminal) and press ENTER&lt;br /&gt;
# Start Paparazzi Center with the TUDelft configuration&lt;br /&gt;
# In the Paparazzi center choose &amp;quot;Xvert&amp;quot; in the airframe dropdown menu&lt;br /&gt;
# Power up the XVert&lt;br /&gt;
# Connect the SWD pins of the BMP as shown in the image TODO&lt;br /&gt;
# Press the &amp;quot;Upload&amp;quot; button in the Paparazzi Center, wait...&lt;br /&gt;
# Plug in the XBee to the laptop&lt;br /&gt;
# Select Hobbyking in the session menu&lt;br /&gt;
# Press execute &lt;br /&gt;
# Select FlightUSB0 in the session menu&lt;br /&gt;
# Press execute again&lt;br /&gt;
&lt;br /&gt;
Voila, you should get telemetry from your XVert. Now it is up to you how and where to fly.&lt;br /&gt;
&lt;br /&gt;
= Features =&lt;br /&gt;
&lt;br /&gt;
Hardware that has to be added manually is marked with an (*).&lt;br /&gt;
&lt;br /&gt;
== Connectivity ==&lt;br /&gt;
* CYRF DSMX RC radio chip (not yet supported)&lt;br /&gt;
* XBee datalink(*)&lt;br /&gt;
&lt;br /&gt;
== Structure ==&lt;br /&gt;
* 2 Brushless Outrunner motors&lt;br /&gt;
* EPO foam wing&lt;br /&gt;
* Two elerons&lt;br /&gt;
&lt;br /&gt;
== Battery ==&lt;br /&gt;
* Lithium Polymer 2S 800 mAh&lt;br /&gt;
* Flight time: ?&lt;br /&gt;
&lt;br /&gt;
== Sensors ==&lt;br /&gt;
* 3-axes magnetometer (TODO)(*)&lt;br /&gt;
* 3-axes gyroscope (MPU 6500)&lt;br /&gt;
* 3-axes accelerometer (MPU 6500)&lt;br /&gt;
* Pressure Baro sensor (M.E.A.S 5607? TODO)&lt;br /&gt;
&lt;br /&gt;
==Processor ==&lt;br /&gt;
STM32F373CCT6&lt;br /&gt;
&lt;br /&gt;
==Motors ==&lt;br /&gt;
* 2 BL280 2600Kv&lt;br /&gt;
* 2 4 Gram Servo (SPMSA220)&lt;br /&gt;
&lt;br /&gt;
== Geo-location ==&lt;br /&gt;
* TODO (*)&lt;br /&gt;
&lt;br /&gt;
== Dimensions ==&lt;br /&gt;
* TODO&lt;br /&gt;
&lt;br /&gt;
== Weight ==&lt;br /&gt;
* Without TODO&lt;br /&gt;
* With add-ons TODO&lt;br /&gt;
&lt;br /&gt;
= Pinout =&lt;br /&gt;
&lt;br /&gt;
[[File:Xvertboardtop.png|thumb|Top view XVert board]]&lt;br /&gt;
[[File:Xvertboardbottom.png|thumb|Top view XVert board]]&lt;br /&gt;
&lt;br /&gt;
Extension UART port&lt;br /&gt;
pa3 (corner)  	UART2RX&lt;br /&gt;
pa2		UART2TX&lt;br /&gt;
vdd&lt;br /&gt;
vss&lt;br /&gt;
&lt;br /&gt;
Baro / GPS / Magneto I2C port&lt;br /&gt;
pf6		I2C scl2&lt;br /&gt;
pf7		I2C sda2&lt;br /&gt;
vdd&lt;br /&gt;
vss (corner)&lt;br /&gt;
&lt;br /&gt;
Servo 1&lt;br /&gt;
vss&lt;br /&gt;
vdd&lt;br /&gt;
PA13 		SWDIO&lt;br /&gt;
&lt;br /&gt;
Servo 2&lt;br /&gt;
vss (corner)&lt;br /&gt;
vdd&lt;br /&gt;
pa11&lt;br /&gt;
&lt;br /&gt;
SWD connection to Black Magic Probe:&lt;br /&gt;
----|-----PA13 (SWDIO) -&amp;gt; TP17&lt;br /&gt;
----|-----gnd&lt;br /&gt;
----|-----pa14 (swclk) -&amp;gt; TP12 &lt;br /&gt;
----|-----Not connected (trace)&lt;br /&gt;
&lt;br /&gt;
I2C IMU MPU6500:&lt;br /&gt;
pb6&lt;br /&gt;
pb7&lt;br /&gt;
&lt;br /&gt;
escs&lt;br /&gt;
ftdi orangje (TX) 	--&amp;gt; A10 (RX)  	--&amp;gt; U10&lt;br /&gt;
ftdi geel (RX) 		--&amp;gt; A9 (TX) 	--&amp;gt; TP15&lt;br /&gt;
&lt;br /&gt;
I2CSDA1 A14 B7 B9&lt;br /&gt;
I2CSCL1 A15 B6 B8&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Something analog  on pa5 and pa6?&lt;br /&gt;
&lt;br /&gt;
The CYRF seems to be on spi.&lt;br /&gt;
&lt;br /&gt;
== First time flash ==&lt;br /&gt;
The first time the xvert is flashed, some extra steps are required to delete the protected programming. &lt;br /&gt;
&lt;br /&gt;
Black magic probe steps:&lt;br /&gt;
* target extended-remote /dev/ttyACM0&lt;br /&gt;
* monitor tpwr enable&lt;br /&gt;
* monitor swdp_scan&lt;br /&gt;
* attach 1&lt;br /&gt;
* mon option erase&lt;br /&gt;
* load /home/houjebek/paparazzi/var/aircrafts/aaf3d/ap/ap.elf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
=  Actuators =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Autopilots]]&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23873</id>
		<title>Xvert</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23873"/>
		<updated>2017-10-09T15:33:09Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 15%&amp;quot;&amp;gt;&amp;lt;categorytree style=&amp;quot;float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;&amp;quot; mode=pages&amp;gt;Autopilots&amp;lt;/categorytree&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[Image:XVert.jpg|right|500px|XVert]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 40%&amp;quot;&amp;gt;__TOC__&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
By default the [https://www.horizonhobby.com/product/airplanes/airplanes-14501--1/ready-to-fly/x-vert-vtol-rtf-efl1800 XVert] from [https://www.horizonhobby.com/ Horrizon Hobby] is a two-prop hybrid VTOL fixed wing, designed to be controlled with DSMX RC. It features a STM32F3 board, which can be reprogrammed with Paparazzi through SWD. A GPS, magneto en datalink can be added by using the expansion ports on this board so that autonomous flight can be achieved.&lt;br /&gt;
&lt;br /&gt;
= Getting started =&lt;br /&gt;
&lt;br /&gt;
== What you need==&lt;br /&gt;
# An XVert EFL1800&lt;br /&gt;
# The Hobbyking Joystick&lt;br /&gt;
# A Black Magic Probe (BMP) or similar SWD programmer&lt;br /&gt;
# A GPS + magneto&lt;br /&gt;
# An XBee datalink &lt;br /&gt;
# A laptop with Ubuntu and paparazzi installed&lt;br /&gt;
&lt;br /&gt;
Steps to follow: &lt;br /&gt;
# Upgrade the XVert with the XBee and GPS&lt;br /&gt;
# Install Paparazzi via [http://wiki.paparazziuav.org/wiki/Installation the one liner to be found here]. Just Cut 'n Paste (CTRL+C from webbrowser then CTRL+SHIFT+V in your Linux terminal) and press ENTER&lt;br /&gt;
# Start Paparazzi Center with the TUDelft configuration&lt;br /&gt;
# In the Paparazzi center choose &amp;quot;Xvert&amp;quot; in the airframe dropdown menu&lt;br /&gt;
# Power up the XVert&lt;br /&gt;
# Connect the SWD pins of the BMP as shown in the image TODO&lt;br /&gt;
# Press the &amp;quot;Upload&amp;quot; button in the Paparazzi Center, wait...&lt;br /&gt;
# Plug in the XBee to the laptop&lt;br /&gt;
# Select Hobbyking in the session menu&lt;br /&gt;
# Press execute &lt;br /&gt;
# Select FlightUSB0 in the session menu&lt;br /&gt;
# Press execute again&lt;br /&gt;
&lt;br /&gt;
Voila, you should get telemetry from your XVert. Now it is up to you how and where to fly.&lt;br /&gt;
&lt;br /&gt;
= Features =&lt;br /&gt;
&lt;br /&gt;
Hardware that has to be added manually is marked with an (*).&lt;br /&gt;
&lt;br /&gt;
== Connectivity ==&lt;br /&gt;
* CYRF DSMX RC radio chip (not yet supported)&lt;br /&gt;
* XBee datalink(*)&lt;br /&gt;
&lt;br /&gt;
== Structure ==&lt;br /&gt;
* 2 Brushless Outrunner motors&lt;br /&gt;
* EPO foam wing&lt;br /&gt;
* Two elerons&lt;br /&gt;
&lt;br /&gt;
== Battery ==&lt;br /&gt;
* Lithium Polymer 2S 800 mAh&lt;br /&gt;
* Flight time: ?&lt;br /&gt;
&lt;br /&gt;
== Sensors ==&lt;br /&gt;
* 3-axes magnetometer (TODO)(*)&lt;br /&gt;
* 3-axes gyroscope (MPU 6500)&lt;br /&gt;
* 3-axes accelerometer (MPU 6500)&lt;br /&gt;
* Pressure Baro sensor (M.E.A.S 5607? TODO)&lt;br /&gt;
&lt;br /&gt;
==Processor ==&lt;br /&gt;
STM32F373CCT6&lt;br /&gt;
&lt;br /&gt;
==Motors ==&lt;br /&gt;
* 2 BL280 2600Kv&lt;br /&gt;
* 2 4 Gram Servo (SPMSA220)&lt;br /&gt;
&lt;br /&gt;
== Geo-location ==&lt;br /&gt;
* TODO (*)&lt;br /&gt;
&lt;br /&gt;
== Dimensions ==&lt;br /&gt;
* TODO&lt;br /&gt;
&lt;br /&gt;
== Weight ==&lt;br /&gt;
* Without TODO&lt;br /&gt;
* With add-ons TODO&lt;br /&gt;
&lt;br /&gt;
= Pinout =&lt;br /&gt;
&lt;br /&gt;
[[File:Xvertboardtop.png|thumb|Top view XVert board]]&lt;br /&gt;
[[File:Xvertboardbottom.png|thumb|Top view XVert board]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Extension UART port&lt;br /&gt;
pa3 (corner)  	UART2RX&lt;br /&gt;
pa2		UART2TX&lt;br /&gt;
vdd&lt;br /&gt;
vss&lt;br /&gt;
&lt;br /&gt;
Baro I2C&lt;br /&gt;
pf6		I2C scl2&lt;br /&gt;
pf7		I2C sda2&lt;br /&gt;
vdd&lt;br /&gt;
vss (corner)&lt;br /&gt;
&lt;br /&gt;
vss&lt;br /&gt;
vdd&lt;br /&gt;
PA13 		SWDIO&lt;br /&gt;
&lt;br /&gt;
vss (corner)&lt;br /&gt;
vdd&lt;br /&gt;
pa11&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
SWD connection to Black Magic Probe:&lt;br /&gt;
----|-----PA13 (SWDIO) -&amp;gt; TP17&lt;br /&gt;
----|-----gnd&lt;br /&gt;
----|-----pa14 (swclk) -&amp;gt; TP12 &lt;br /&gt;
----|-----Not connected (trace)&lt;br /&gt;
&lt;br /&gt;
I2C IMU MPU6500:&lt;br /&gt;
pb6&lt;br /&gt;
pb7&lt;br /&gt;
&lt;br /&gt;
escs&lt;br /&gt;
ftdi orangje (TX) 	--&amp;gt; A10 (RX)  	--&amp;gt; U10&lt;br /&gt;
ftdi geel (RX) 		--&amp;gt; A9 (TX) 	--&amp;gt; TP15&lt;br /&gt;
&lt;br /&gt;
I2CSDA1 A14 B7 B9&lt;br /&gt;
I2CSCL1 A15 B6 B8&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Something analog  on pa5 and pa6?&lt;br /&gt;
&lt;br /&gt;
The CYRF seems to be on spi.&lt;br /&gt;
&lt;br /&gt;
== First time flash ==&lt;br /&gt;
The first time the xvert is flashed, some extra steps are required to delete the protected programming. &lt;br /&gt;
&lt;br /&gt;
Black magic probe steps:&lt;br /&gt;
* target extended-remote /dev/ttyACM0&lt;br /&gt;
* monitor tpwr enable&lt;br /&gt;
* monitor swdp_scan&lt;br /&gt;
* attach 1&lt;br /&gt;
* mon option erase&lt;br /&gt;
* load /home/houjebek/paparazzi/var/aircrafts/aaf3d/ap/ap.elf&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
=  Actuators =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Autopilots]]&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Xvertboardbottom.png&amp;diff=23872</id>
		<title>File:Xvertboardbottom.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Xvertboardbottom.png&amp;diff=23872"/>
		<updated>2017-10-09T15:32:28Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Bottom view of XVert board&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Xvertboardtop.png&amp;diff=23871</id>
		<title>File:Xvertboardtop.png</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Xvertboardtop.png&amp;diff=23871"/>
		<updated>2017-10-09T15:31:47Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Top of XVert board&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23870</id>
		<title>Xvert</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Xvert&amp;diff=23870"/>
		<updated>2017-10-09T14:46:25Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: Created page with &amp;quot;&amp;lt;div style=&amp;quot;float: right; width: 15%&amp;quot;&amp;gt;&amp;lt;categorytree style=&amp;quot;float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;&amp;quot; mode=pages&amp;gt;Autopilots&amp;lt;/categoryt...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 15%&amp;quot;&amp;gt;&amp;lt;categorytree style=&amp;quot;float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;&amp;quot; mode=pages&amp;gt;Autopilots&amp;lt;/categorytree&amp;gt;&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[Image:XVert.jpg|right|500px|XVert]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&amp;lt;div style=&amp;quot;float: right; width: 40%&amp;quot;&amp;gt;__TOC__&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
By default the [https://www.horizonhobby.com/product/airplanes/airplanes-14501--1/ready-to-fly/x-vert-vtol-rtf-efl1800 XVert] from [https://www.horizonhobby.com/ Horrizon Hobby] is a two-prop hybrid VTOL fixed wing, designed to be controlled with DSMX RC. It features a STM32F3 board, which can be reprogrammed with Paparazzi through SWD. A GPS, magneto en datalink can be added by using the expansion ports on this board so that autonomous flight can be achieved.&lt;br /&gt;
&lt;br /&gt;
= Getting started =&lt;br /&gt;
&lt;br /&gt;
== What you need==&lt;br /&gt;
# An XVert EFL1800&lt;br /&gt;
# The Hobbyking Joystick&lt;br /&gt;
# A Black Magic Probe (BMP) or similar SWD programmer&lt;br /&gt;
# A GPS + magneto&lt;br /&gt;
# An XBee datalink &lt;br /&gt;
# A laptop with Ubuntu and paparazzi installed&lt;br /&gt;
&lt;br /&gt;
Steps to follow: &lt;br /&gt;
# Upgrade the XVert with the XBee and GPS&lt;br /&gt;
# Install Paparazzi via [http://wiki.paparazziuav.org/wiki/Installation the one liner to be found here]. Just Cut 'n Paste (CTRL+C from webbrowser then CTRL+SHIFT+V in your Linux terminal) and press ENTER&lt;br /&gt;
# Start Paparazzi Center with the TUDelft configuration&lt;br /&gt;
# In the Paparazzi center choose &amp;quot;Xvert&amp;quot; in the airframe dropdown menu&lt;br /&gt;
# Power up the XVert&lt;br /&gt;
# Connect the SWD pins of the BMP as shown in the image TODO&lt;br /&gt;
# Press the &amp;quot;Upload&amp;quot; button in the Paparazzi Center, wait...&lt;br /&gt;
# Plug in the XBee to the laptop&lt;br /&gt;
# Select Hobbyking in the session menu&lt;br /&gt;
# Press execute &lt;br /&gt;
# Select FlightUSB0 in the session menu&lt;br /&gt;
# Press execute again&lt;br /&gt;
&lt;br /&gt;
Voila, you should get telemetry from your XVert. Now it is up to you how and where to fly.&lt;br /&gt;
&lt;br /&gt;
= Features =&lt;br /&gt;
&lt;br /&gt;
Hardware that has to be added manually is marked with an (*).&lt;br /&gt;
&lt;br /&gt;
== Connectivity ==&lt;br /&gt;
* CYRF DSMX RC radio chip (not yet supported)&lt;br /&gt;
* XBee datalink(*)&lt;br /&gt;
&lt;br /&gt;
== Structure ==&lt;br /&gt;
* 2 Brushless Outrunner motors&lt;br /&gt;
* EPO foam wing&lt;br /&gt;
* Two elerons&lt;br /&gt;
&lt;br /&gt;
== Battery ==&lt;br /&gt;
* Lithium Polymer 2S 800 mAh&lt;br /&gt;
* Flight time: ?&lt;br /&gt;
&lt;br /&gt;
== Sensors ==&lt;br /&gt;
* 3-axes magnetometer (TODO)(*)&lt;br /&gt;
* 3-axes gyroscope (MPU 6500)&lt;br /&gt;
* 3-axes accelerometer (MPU 6500)&lt;br /&gt;
* Pressure Baro sensor (M.E.A.S 5607? TODO)&lt;br /&gt;
&lt;br /&gt;
==Processor ==&lt;br /&gt;
STM32F373CCT6&lt;br /&gt;
&lt;br /&gt;
==Motors ==&lt;br /&gt;
* 2 BL280 2600Kv&lt;br /&gt;
* 2 4 Gram Servo (SPMSA220)&lt;br /&gt;
&lt;br /&gt;
== Geo-location ==&lt;br /&gt;
* TODO (*)&lt;br /&gt;
&lt;br /&gt;
== Dimensions ==&lt;br /&gt;
* TODO&lt;br /&gt;
&lt;br /&gt;
== Weight ==&lt;br /&gt;
* Without TODO&lt;br /&gt;
* With add-ons TODO&lt;br /&gt;
&lt;br /&gt;
= Pinout =&lt;br /&gt;
&lt;br /&gt;
== Other ==&lt;br /&gt;
&lt;br /&gt;
=  Actuators =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Autopilots]]&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:XVert.jpg&amp;diff=23869</id>
		<title>File:XVert.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:XVert.jpg&amp;diff=23869"/>
		<updated>2017-10-09T13:37:04Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Horizon hobbies XVert VTOL&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23441</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23441"/>
		<updated>2017-01-17T11:11:08Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [[Iris]] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [[#Flashing|below]]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [[Iris]] drone. A list of features that are currently (not) supported in Paparazzi can be found [[#Features|here]].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [[#Flashing|Flashing]]. Details on step 1 can be found [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** Between 10 to 20 seconds after replugging, click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* If the Pixhawk is in view, one can monitor the system (B/E) led of the autopilot (left, FMU side). After 10 seconds, the system led will blink slower, meaning the autopilot has booted and the FBW can be flashed. After 20 second, the system led will blink slow (1Hz), meaning the FBW cannot be flashed any more.&lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 10 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 10s after start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the IMU to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 IMU:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
  &amp;lt;module name=&amp;quot;px4_flash&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;configure name=&amp;quot;PX4IO_UART&amp;quot; value=&amp;quot;uart6&amp;quot;/&amp;gt;&lt;br /&gt;
  &amp;lt;/module&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6000, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
Paparazzi UAV Pixhawk tutorial videos - by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab] &amp;lt;br&amp;gt;&lt;br /&gt;
{{#ev:youtubeplaylist|PL_KSX9GOn2P-CVsy-lRSHAnUwVF9wI_pZ}} &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots&amp;diff=23438</id>
		<title>Category:Autopilots</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots&amp;diff=23438"/>
		<updated>2017-01-09T13:06:37Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
__NOEDITSECTION__&lt;br /&gt;
&lt;br /&gt;
{{P Topic Table|{{P Header Box|ico=Autopilot.png|Autopilots}}&lt;br /&gt;
{{Category:Autopilots/Index}}&lt;br /&gt;
&amp;lt;!-- Start of right-column --&amp;gt;&lt;br /&gt;
|{{P Header Box|ico=Autopilot.png|Paparazzi Autopilots}}&lt;br /&gt;
&lt;br /&gt;
One of the great advantages of Paparazzi is support for many hardware designs. There is autopilot hardware that is specifically designed to work with Paparazzi from the start, but Paparazzi has also been ported to other popular autopilots. &lt;br /&gt;
[[Image:tiny13_family_top_sm.jpg|center|400px|Tiny 1.1 autopilots on the &amp;quot;assembly line&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt; Paparazzi designed hardware &amp;lt;/h3&amp;gt;&lt;br /&gt;
Most current autopilots are designed around two primary processors:&lt;br /&gt;
*STM32 series microcontrollers &lt;br /&gt;
*LPC21xx series microcontrollers&lt;br /&gt;
There are active and current autopilots designs using both architectures. Not all autopilots have the same capabilities, peripherals or features, but each has advantages in different applications.&lt;br /&gt;
&lt;br /&gt;
Currently, boards are designed around the STM32 microcontollers. Some of the autopilots use the STM32F1 and others the STM32F4 microcontrollers. This provides a wide range of choices resulting in a large variety of peripherals and speeds. Architecture-dependent firmware code is supported in part by [http://www.libopencm3.org libopencm3], as well as Chibi OS through the Paparazzi RT branch.&lt;br /&gt;
&lt;br /&gt;
The LPC21xx based boards use the LPC2148 and have been flying fixed wing and multi-rotors for many years. This architecture is more mature but at the expense of speed and extra ports available on the newer STM32 series processors. The [[Tiny]] series, [[Booz]], [[TWOG/v1.0 | TWOG]], [[YAPA]], [[Umarim_Lite_v2 | Umarim]] and [[NavGo_v3 | NavGo]] autopilots all use the LPC2148.&lt;br /&gt;
&lt;br /&gt;
Newer autopilots use either the STM32F1 or STM32F4 microcontrollers. You can choose from [[Lisa/M(X)]], [[Elle0]], [[Krooz]] or [[Apogee]] autopilots, depending on your processing and IO needs.&lt;br /&gt;
&lt;br /&gt;
Some autopilots have also been designed for close integration with small single-board computers, particularly those based on [[OMAP]] processors such as the [http://www.gumstix.com/ Gumstix] [https://www.gumstix.com Overo] series. The [[Lisa/L]] and [[Classix]] boards are designed with this in mind, though other autopilots can be easily interfaced. Further information can be found [[OMAP|here]]. &lt;br /&gt;
&lt;br /&gt;
A basic feature comparison table is presented to help in the autopilot hardware selection process.&lt;br /&gt;
&lt;br /&gt;
For information regarding architecture and firmware compatibility of various subsystems and modules, please see the appropriate [[Subsystems]] overview and [[Modules_list|Modules List]] pages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt; Other popular autopilot hardware support &amp;lt;/h3&amp;gt;&lt;br /&gt;
Using existing hardware is great to get started, as sometimes it just involves buying a stock drone and uploading paparazzi to it. Currently, Paparazzi supports many of the popular Parrot drones, such as the [[AR Drone 2]], [[Bebop]] and [[Rolling Spider]] airframes. These come with built in embedded Linux computers as their autopilot hardware, and Paparazzi runs as a Linux process interfacing at the lowest level possible with the hardware.&lt;br /&gt;
&lt;br /&gt;
Secondly, Paparazzi supports the [[Pixhawk]] autopilot, of which an example can be found in the [[Iris]] airframe. The Pixhawk is a duo processor board, with an autopilot chip and a separated Fly By Wire chip for safety.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Schematics, CAD files, Gerber files, BOM release strategy&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;About the hardware development and release process.&amp;lt;/h3&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://github.com/paparazzi/paparazzi-hardware Files needed to create the hardware can be found here]. It is always good to remind oneself of the email Antoine once wrote in the mailing list before you want to start producing your own PCB's.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;P&amp;gt;8 June 2011 13:25:47 Antoine Drouin wrote on the mailing list:&amp;lt;/P&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I've started this project together with Pascal 8 years ago and since then I have dedicated my time to try and make it successful. I'm utterly convinced of the benefits of open source, but observing how Paparazzi grew over time, I came to the conclusion that hardware is a bit different than software... &amp;quot;gcc tiny.brd&amp;quot; is not going to make a board magically appear on your desktop. &lt;br /&gt;
&lt;br /&gt;
I'll list here some of my arguments in favor of releasing CAD files after the board is mature.&lt;br /&gt;
&lt;br /&gt;
# Unlike software, where an unskilled user can type make and get a piece of complex software to successfully build, assembling hardware requires tools and skills. Providing gerbers and BOM have lured a bunch of new users into believing otherwise and has created tons of frustration. I've myself fixed a number of badly assembled boards and I even recall that while helping debugging a board (so after assembly), discovering that the person had manufactured two layers PCBs instead of four layers. As the technology of the autopilot increases, this problem becomes more and more important.&lt;br /&gt;
# The success of the project depends on the availability of affordable hardware. The price of hardware is directly and exponentially dependent on the number of manufactured units. If ten persons manufacture 10 boards each, the cost will be much higher than if one person manufactures 100.&lt;br /&gt;
# Last and not least, the quality of assembly also depends very much on the number of manufactured units. Good quality can only be achieved through the use of automated placing and soldering, and those processes can only be used if the number of units reach a certain amount.&lt;br /&gt;
&lt;br /&gt;
'''For the autopilot comparison table see below.'''&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
'''NOTE: This list contains only mature and fully supported autopilots designed specifically for the Paparazzi UAV project.'''&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Begin}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
{{P Autopilot Table/Divider | Developed by and for the Paparazzi Community}}&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Apogee&lt;br /&gt;
| version=V1.00&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[[Apogee/v1.00#Where_to_Buy | Buy]]&lt;br /&gt;
| mcu part=STM32F405RGT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=128 &amp;amp; 64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3 &amp;amp; 1Rx&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 3 (12bit)&lt;br /&gt;
| io pwm=6 + 1&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=1 (std &amp;amp; S.BUS)&lt;br /&gt;
| io gpio=0 + 4&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=DFU bootloader + USB storage&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=SDIO + USB storage&lt;br /&gt;
| periph rtc=yes + backup cap&lt;br /&gt;
| periph other=mini-USB B&lt;br /&gt;
| program debug=USB(DFU) + SWD&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=1 (5V)&lt;br /&gt;
| mechanical size=53 x 25 x 9mm&lt;br /&gt;
| mechanical weight=10g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2013&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Elle0&lt;br /&gt;
| version=V1.2&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/elle0-autopilot Pre-Order]&lt;br /&gt;
| mcu part=STM32F415RCT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=192kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2 &amp;amp; 2RX/TX&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=0&lt;br /&gt;
| io adc=2&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1-8&lt;br /&gt;
| io rc serial=2&lt;br /&gt;
| io gpio=&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=DFU bootloader&lt;br /&gt;
| io can=110&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=micro-USB B, JTAG&lt;br /&gt;
| program debug=USB (DFU) + JTAG&lt;br /&gt;
| power input=5V&lt;br /&gt;
| power output=2x299mA@3.3V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=36mm x 36mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=JST9 + 0.1&amp;amp;quot; pin header&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Winter 2015&lt;br /&gt;
| previous version=v1.1&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/S&lt;br /&gt;
| version=V1.1&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/lisa-s Buy]&lt;br /&gt;
| mcu part=STM32F103REY6&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=Y&lt;br /&gt;
| io uart=1 &amp;amp; 1RX&lt;br /&gt;
| io i2c=18&lt;br /&gt;
| io spi=0&lt;br /&gt;
| io adc=0&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=1&lt;br /&gt;
| io gpio=0&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=N&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=4 x brushed motor drivers&lt;br /&gt;
| program debug=SWD + UART&lt;br /&gt;
| power input=2.3V - 5.5V&lt;br /&gt;
| power output=1A@3.3V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=20mm x 20mm x 5mm&lt;br /&gt;
| mechanical weight=2g&lt;br /&gt;
| mechanical connectors=0.05&amp;amp;quot; header&lt;br /&gt;
| mechanical pcb=6-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2013&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/M&lt;br /&gt;
| version=V2.1&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/lisa-m-autopilot Buy]&lt;br /&gt;
| mcu part=STM32F105RCT6&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=256kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2 &amp;amp; 2RX&lt;br /&gt;
| io i2c=1 + 15&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=3 + 2 (12bit)&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=6 + 2&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=0 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=2&lt;br /&gt;
| io gpio=1&lt;br /&gt;
| io led=5&lt;br /&gt;
| io usb=DFU bootloader&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=JTAG&lt;br /&gt;
| program debug=USB (luftboot)+ JTAG + UART&lt;br /&gt;
| power input=5V - 16V&lt;br /&gt;
| power output=500mA@3.3V, 250mA@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=34mm x 60mm x 10mm&lt;br /&gt;
| mechanical weight=9.9g - 10.8g&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Winter 2012&lt;br /&gt;
| previous version=v2.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/L&lt;br /&gt;
| version=v1.1&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=STM32F103RE&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=Y&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3 &amp;amp; 1RX&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=2&lt;br /&gt;
| io adc=3 (12bit)&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=&lt;br /&gt;
| io led=8&lt;br /&gt;
| io usb=JTAG + UART&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=Overo Gumstix&lt;br /&gt;
| program debug=JTAG + UART&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=2.25@5V, 2.25A@3.3V, Other&lt;br /&gt;
| power switch=2&lt;br /&gt;
| mechanical size=~100mm x ~50mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Summer 2010&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=KroozSD&lt;br /&gt;
| version=&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://wiki.paparazziuav.org/wiki/KroozSD#Where_to_buy Buy]&lt;br /&gt;
| mcu part=STM32F405RGT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=128 &amp;amp; 64kB&lt;br /&gt;
| sensor imu=krooz/ext&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=4 + 1 (12bit)&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=10 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=Xbee&lt;br /&gt;
| periph sd=SPI&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=micro-USB B&lt;br /&gt;
| program debug=&lt;br /&gt;
| power input=7V - 32V&lt;br /&gt;
| power output=1.5A@3.3V, 5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=50mm x 60mm x 10mm&lt;br /&gt;
| mechanical weight=20g - 40g&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Spring 2013&lt;br /&gt;
| previous version=Krooz&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Umarim Lite v2 {{!}} Umarim Lite&lt;br /&gt;
| version=V2&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/umarim-lite-v2/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=86&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 4&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=mini-USB B&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=53mm x 25mm&lt;br /&gt;
| mechanical weight=8g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Umarim&lt;br /&gt;
| version=V1.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 4 (10bit)&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 4&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=56mm x 25mm&lt;br /&gt;
| mechanical weight=9g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Fall 2011&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=NavGo&lt;br /&gt;
| version=V3&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/navgo-v3-00/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 4 (10bit)&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=0 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 2&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 16V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=35mm x 35mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Tiny&lt;br /&gt;
| version=v2.11&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/tiny-v2-11/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=Y&lt;br /&gt;
| io uart=1&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 1 (10bit)&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=1&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=70.8mm x 40mm&lt;br /&gt;
| mechanical weight=24g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=no&lt;br /&gt;
| introduction date=Fall 2007&lt;br /&gt;
| previous version=v1.1&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=TWOG&lt;br /&gt;
| version=v1.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=8 (10bit)&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=1&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=40.2mm x 30.5mm&lt;br /&gt;
| mechanical weight=8g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=no&lt;br /&gt;
| introduction date=Spring 2008&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=YAPA&lt;br /&gt;
| version=v2.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=6 (10bit)&lt;br /&gt;
| io pwm=10&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=1&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=Xbee&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=RS232&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=2x 1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=80.0mm x 40.0mm?&lt;br /&gt;
| mechanical weight=23g w/ XBee?&lt;br /&gt;
| mechanical connectors=0.1&amp;amp;quot; Headers&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=4x M3&lt;br /&gt;
| introduction date=Spring 2011&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=HBmini&lt;br /&gt;
| version=v2.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=8 (10bit)(16bit)&lt;br /&gt;
| io pwm=10&lt;br /&gt;
| io ppm out=&lt;br /&gt;
| io ppm in=&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=11&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootlader&lt;br /&gt;
| io can=N&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=Buzzer&lt;br /&gt;
| program debug=JTAG&lt;br /&gt;
| power input=6.1-18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=4&lt;br /&gt;
| mechanical size=57x30mm&lt;br /&gt;
| mechanical weight=30&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Winter 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/End}}&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&lt;br /&gt;
&lt;br /&gt;
This table was created using a  [https://docs.google.com/spreadsheets/d/1TktQCAiIyBRtwVCMfdT2Y5R6Eyvzh24047Bab7tLsCM/edit?usp=sharing google document spreadsheet]. If you want to add or improve anything in the table, please contact [[User:Esden|Esden]] to get write access to the spreadsheet. This makes editing and maintaining of the table much easier!&lt;br /&gt;
&lt;br /&gt;
'''1.''' Only the newest revisions of the more commonly used autopilots are listed&lt;br /&gt;
&lt;br /&gt;
'''2.''' The extra 8kB of RAM on the LPC2148 shared with the USB DMA&lt;br /&gt;
&lt;br /&gt;
'''3.''' The onboard sensors are almost always supplemented with external sensors. For example, TWOG can use an external IMU or IR sensors, and also needs an external GPS.&lt;br /&gt;
&lt;br /&gt;
'''4.''' Input/Outputs listed are generally those easily accessible on regular autopilot connectors, customization/hacks can modify available I/O, for example free an extra I2C on Tiny and TWOG&lt;br /&gt;
&lt;br /&gt;
'''5., 6.''' Some features use shared resources - denoted by X + Y where Y is shared - and cannot be used simultaneously&lt;br /&gt;
&lt;br /&gt;
'''5.''' Lisa/M v2.0 shared resources include: one I2C is shared with 2 PWM outputs, two ADCs are shared with LEDs, one RX only UART is shared with the PPM capture&lt;br /&gt;
&lt;br /&gt;
'''6.''' Umarim v1.0 shared resources include: 4 ADCs are shared with 4 GPIOs&lt;br /&gt;
&lt;br /&gt;
'''7.''' Usually other unused pins can be used for additional GPIO with some code modifications&lt;br /&gt;
&lt;br /&gt;
'''8.''' Many of the pins have multiple purposes. Servo 5&amp;amp;6 can be used for i2c even though there is no dedicated connector.&lt;br /&gt;
&lt;br /&gt;
'''9.''' The two JST connectors, provide a combined RX and TX connection. The RX &amp;amp; TX lines are combined through a 100Ohm resistor. The GPS and Telemetry connectors are full TTL UARTs.&lt;br /&gt;
&lt;br /&gt;
'''10.''' Only the CAN RX&amp;amp;TX lines are exposed, no transceiver included on board.&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots/Index&amp;diff=23437</id>
		<title>Category:Autopilots/Index</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots/Index&amp;diff=23437"/>
		<updated>2017-01-09T12:52:08Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''STM32F1 based boards'''&lt;br /&gt;
&lt;br /&gt;
*[[Lisa|Lisa]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;STM32F1 based autopilots:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Lisa/S|&amp;lt;small&amp;gt;'''Lisa/S''']]&amp;lt;br&amp;gt;STM32 micro footprint autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Lisa/M_v10|&amp;lt;small&amp;gt;'''Lisa/M v1.0''']]&amp;lt;br&amp;gt;STM32 small footprint autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Lisa/M_v20|&amp;lt;small&amp;gt;'''Lisa/M v2.0''']]&amp;lt;br&amp;gt;Improved STM32 small footprint autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Lisa/L|&amp;lt;small&amp;gt;'''Lisa/L''']]&amp;lt;br&amp;gt;STM32/[[Gumstix|Overo]] high performance autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''STM32F4 based boards'''&lt;br /&gt;
&lt;br /&gt;
*[[Apogee]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;STM32F4 (ARM Cortex™-M4) based autopilot for fixed wing:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Apogee/v1.00|&amp;lt;small&amp;gt;'''Apogee v1.00''']]&amp;lt;br&amp;gt;Super small and lightweight autopilot, 9 DOF IMU, microSD high speed,  Baro, ,...&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Elle|Elle]]&amp;lt;br/&amp;gt;&amp;lt;small&amp;gt;STM32F4 autopilot system:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Elle0|&amp;lt;small&amp;gt;'''Elle0'''&amp;lt;span style=&amp;quot;color:red&amp;quot;&amp;gt; New!&amp;lt;/span&amp;gt;]]&amp;lt;br/&amp;gt;STM32F4 small and affordable autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Lisa|Lisa]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;STM32F4 based autopilots:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Lisa/M_v20|&amp;lt;small&amp;gt;'''Lisa/MX''']]&amp;lt;br/&amp;gt;STM32F4 versatile autopilot with crypto support&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Krooz|Krooz]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;STM32F4 Cortex™-M4 high integrated Rotorcraft autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Krooz|&amp;lt;small&amp;gt;'''Krooz''']]&amp;lt;br&amp;gt;STM32F4 Cortex™-M4 high integrated Rotorcraft autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[KroozSD|&amp;lt;small&amp;gt;'''KroozSD''']]&amp;lt;br&amp;gt;STM32F4 Cortex™-M4 high integrated autopilot, w. microSD slot, XBee conn.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Pixhawk|Pixhawk]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Duo processor with Autopilot core on a STM32F4 Cortex™-M4 and Fly By Wire core on a STM32F1 Cortex™-M1&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''LPC2148 based boards'''&lt;br /&gt;
&lt;br /&gt;
*[[Booz|Booz]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Quadrotor autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[NavGo|NavGo]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Multirotor autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[NavGo_v3|&amp;lt;small&amp;gt;'''NavGo v3''']]&amp;lt;br&amp;gt;Small and lightweight multirotor autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Umarim]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;LPC based embedded IMU autopilot designed for small fixed wing:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Umarim_v10|&amp;lt;small&amp;gt;'''Umarim v1''']]&amp;lt;br&amp;gt;full sensor set for small fixed wing&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Umarim_Lite_v2|&amp;lt;small&amp;gt;'''Umarim Lite v2''']]&amp;lt;br&amp;gt;light sensor set version of Umarim&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Tiny]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;GPS integrated lightweight autopilots:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Tiny/v0.99|&amp;lt;small&amp;gt;'''Tiny v0.99''']]&amp;lt;br&amp;gt;Tiny autopilot&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Tiny/v1.1|&amp;lt;small&amp;gt;'''Tiny v1.1''']]&amp;lt;br&amp;gt;Integrated GPS and 5V/2A supply&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[Tiny/v2.11|&amp;lt;small&amp;gt;'''Tiny v2.11''']]&amp;lt;br&amp;gt;Two layers PCB, 0603 components, big GPS groundplane, improved connectivity.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[TWOG/v1.0|TWOG v1.0]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;8 grams Tiny WithOut GPS autopilot, with external GPS option.&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[YAPA]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Yet Another Paparazzi Autopilot:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[YAPA/v1.0|&amp;lt;small&amp;gt;YAPA v1.0]]&amp;lt;br&amp;gt;Same as [[TWOG]], but bigger with XBee, 100mil headers, mounting holes, rs232&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[YAPA/v2.0|&amp;lt;small&amp;gt;YAPA v2.0]] Reduced component cost&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[Classix|Classix]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Dual [[MCU]]s, [[Gumstix]] connectivity&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
*[[HB]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Autopilots built in Bremen:&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[HB/v1.0|&amp;lt;small&amp;gt;'''HB v1.0''']]&amp;lt;br&amp;gt;Four layers PCB, no GPS, JTAG with IMU&amp;lt;/small&amp;gt;&lt;br /&gt;
**[[HB/mini|&amp;lt;small&amp;gt;'''HB mini''']]&amp;lt;br&amp;gt;Four layers planar PCB, JTAG, 10 sevos, 12g, no GPS, with IMU&amp;lt;/small&amp;gt;&lt;br /&gt;
&lt;br /&gt;
'''Aircraft With Embedded Autopilots'''&lt;br /&gt;
* Parrot&lt;br /&gt;
** [[AR Drone 2]]&lt;br /&gt;
** [[Bebop]]&lt;br /&gt;
** [[Rolling Spider]]&lt;br /&gt;
&lt;br /&gt;
'''Archive'''&lt;br /&gt;
*[[Previous_Autopilots|Previous Versions]]&amp;lt;br&amp;gt;&amp;lt;small&amp;gt;Schematics and support for previous versions&amp;lt;/small&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots&amp;diff=23436</id>
		<title>Category:Autopilots</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Category:Autopilots&amp;diff=23436"/>
		<updated>2017-01-09T11:10:31Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__NOTOC__&lt;br /&gt;
__NOEDITSECTION__&lt;br /&gt;
&lt;br /&gt;
{{P Topic Table|{{P Header Box|ico=Autopilot.png|Autopilots}}&lt;br /&gt;
{{Category:Autopilots/Index}}&lt;br /&gt;
&amp;lt;!-- Start of right-column --&amp;gt;&lt;br /&gt;
|{{P Header Box|ico=Autopilot.png|Paparazzi Autopilots}}&lt;br /&gt;
&lt;br /&gt;
Hardware support for Autopilot versions currently in use.&lt;br /&gt;
&lt;br /&gt;
[[Image:tiny13_family_top_sm.jpg|center|400px|Tiny 1.1 autopilots on the &amp;quot;assembly line&amp;quot;]]&lt;br /&gt;
&lt;br /&gt;
One of the great advantages of Paparazzi is support for many hardware designs. There is autopilot hardware that is specifically designed to work with Paparazzi from the start, but Paparazzi has also been ported to popular autopilots from external parties. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt; Paparazzi designed hardware &amp;lt;/h3&amp;gt;&lt;br /&gt;
Most current autopilots are designed around two primary processors:&lt;br /&gt;
*STM32 series microcontrollers &lt;br /&gt;
*LPC21xx series microcontrollers&lt;br /&gt;
There are active and current autopilots designs using both architectures. Not all autopilots have the same capabilities, peripherals or features, but each has advantages in different applications.&lt;br /&gt;
&lt;br /&gt;
Currently, boards are designed around the STM32 microcontollers. Some of the autopilots use the STM32F1 and others the STM32F4 microcontrollers. This provides a wide range of choices resulting in a large variety of peripherals and speeds. Architecture-dependent firmware code is supported in part by [http://www.libopencm3.org libopencm3], as well as Chibi OS through the Paparazzi RT branch.&lt;br /&gt;
&lt;br /&gt;
The LPC21xx based boards use the LPC2148 and have been flying fixed wing and multi-rotors for many years. This architecture is more mature but at the expense of speed and extra ports available on the newer STM32 series processors. The [[Tiny]] series, [[Booz]], [[TWOG/v1.0 | TWOG]], [[YAPA]], [[Umarim_Lite_v2 | Umarim]] and [[NavGo_v3 | NavGo]] autopilots all use the LPC2148.&lt;br /&gt;
&lt;br /&gt;
Newer autopilots use either the STM32F1 or STM32F4 microcontrollers. You can choose from [[Lisa/M(X)]], [[Elle0]], [[Krooz]] or [[Apogee]] autopilots, depending on your processing and IO needs.&lt;br /&gt;
&lt;br /&gt;
Some autopilots have also been designed for close integration with small single-board computers, particularly those based on [[OMAP]] processors such as the [http://www.gumstix.com/ Gumstix] [https://www.gumstix.com Overo] series. The [[Lisa/L]] and [[Classix]] boards are designed with this in mind, though other autopilots can be easily interfaced. Further information can be found [[OMAP|here]]. &lt;br /&gt;
&lt;br /&gt;
A basic feature comparison table is presented to help in the autopilot hardware selection process.&lt;br /&gt;
&lt;br /&gt;
For information regarding architecture and firmware compatibility of various subsystems and modules, please see the appropriate [[Subsystems]] overview and [[Modules_list|Modules List]] pages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt; Other popular autopilot hardware support &amp;lt;/h3&amp;gt;&lt;br /&gt;
Using existing hardware is great to get you started, as sometimes it just involves buying a stock drone, and uploading paparazzi to it. Currently, Paparazzi supports many of the popular Parrot drones, such as the [[AR Drone 2]], [[Bebop]] and [[Rolling Spider]] airframes. These come with built in embedded Linux computers as their autopilot hardware, and Paparazzi runs as a Linux process interfacing at the lowest level possible with the hardware.&lt;br /&gt;
&lt;br /&gt;
Secondly, Paparazzi supports the [[Pixhawk]] autopilot, of which an example can be found in the [[Iris]] airframe.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h2&amp;gt;Schematics, CAD files, Gerber files, BOM release strategy&amp;lt;/h2&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;h3&amp;gt;About the hardware development and release process.&amp;lt;/h3&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[https://github.com/paparazzi/paparazzi-hardware Files needed to create the hardware can be found here]. It is always good to remind oneself of the email Antoine once wrote in the mailing list before you want to start producing your own PCB's.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;P&amp;gt;8 June 2011 13:25:47 Antoine Drouin wrote on the mailing list:&amp;lt;/P&amp;gt;&lt;br /&gt;
&lt;br /&gt;
I've started this project together with Pascal 8 years ago and since then I have dedicated my time to try and make it successful. I'm utterly convinced of the benefits of open source, but observing how Paparazzi grew over time, I came to the conclusion that hardware is a bit different than software... &amp;quot;gcc tiny.brd&amp;quot; is not going to make a board magically appear on your desktop. &lt;br /&gt;
&lt;br /&gt;
I'll list here some of my arguments in favor of releasing CAD files after the board is mature.&lt;br /&gt;
&lt;br /&gt;
# Unlike software, where an unskilled user can type make and get a piece of complex software to successfully build, assembling hardware requires tools and skills. Providing gerbers and BOM have lured a bunch of new users into believing otherwise and has created tons of frustration. I've myself fixed a number of badly assembled boards and I even recall that while helping debugging a board (so after assembly), discovering that the person had manufactured two layers PCBs instead of four layers. As the technology of the autopilot increases, this problem becomes more and more important.&lt;br /&gt;
# The success of the project depends on the availability of affordable hardware. The price of hardware is directly and exponentially dependent on the number of manufactured units. If ten persons manufacture 10 boards each, the cost will be much higher than if one person manufactures 100.&lt;br /&gt;
# Last and not least, the quality of assembly also depends very much on the number of manufactured units. Good quality can only be achieved through the use of automated placing and soldering, and those processes can only be used if the number of units reach a certain amount.&lt;br /&gt;
&lt;br /&gt;
'''For the autopilot comparison table see below.'''&lt;br /&gt;
&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
'''NOTE: This list contains only mature and fully supported autopilots designed specifically for the Paparazzi UAV project.'''&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Begin}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
{{P Autopilot Table/Divider | Developed by and for the Paparazzi Community}}&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Apogee&lt;br /&gt;
| version=V1.00&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[[Apogee/v1.00#Where_to_Buy | Buy]]&lt;br /&gt;
| mcu part=STM32F405RGT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=128 &amp;amp; 64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3 &amp;amp; 1Rx&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 3 (12bit)&lt;br /&gt;
| io pwm=6 + 1&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=1 (std &amp;amp; S.BUS)&lt;br /&gt;
| io gpio=0 + 4&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=DFU bootloader + USB storage&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=SDIO + USB storage&lt;br /&gt;
| periph rtc=yes + backup cap&lt;br /&gt;
| periph other=mini-USB B&lt;br /&gt;
| program debug=USB(DFU) + SWD&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=1 (5V)&lt;br /&gt;
| mechanical size=53 x 25 x 9mm&lt;br /&gt;
| mechanical weight=10g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2013&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Elle0&lt;br /&gt;
| version=V1.2&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/elle0-autopilot Pre-Order]&lt;br /&gt;
| mcu part=STM32F415RCT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=192kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2 &amp;amp; 2RX/TX&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=0&lt;br /&gt;
| io adc=2&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1-8&lt;br /&gt;
| io rc serial=2&lt;br /&gt;
| io gpio=&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=DFU bootloader&lt;br /&gt;
| io can=110&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=micro-USB B, JTAG&lt;br /&gt;
| program debug=USB (DFU) + JTAG&lt;br /&gt;
| power input=5V&lt;br /&gt;
| power output=2x299mA@3.3V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=36mm x 36mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=JST9 + 0.1&amp;amp;quot; pin header&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Winter 2015&lt;br /&gt;
| previous version=v1.1&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/S&lt;br /&gt;
| version=V1.1&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/lisa-s Buy]&lt;br /&gt;
| mcu part=STM32F103REY6&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=Y&lt;br /&gt;
| io uart=1 &amp;amp; 1RX&lt;br /&gt;
| io i2c=18&lt;br /&gt;
| io spi=0&lt;br /&gt;
| io adc=0&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=1&lt;br /&gt;
| io gpio=0&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=N&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=4 x brushed motor drivers&lt;br /&gt;
| program debug=SWD + UART&lt;br /&gt;
| power input=2.3V - 5.5V&lt;br /&gt;
| power output=1A@3.3V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=20mm x 20mm x 5mm&lt;br /&gt;
| mechanical weight=2g&lt;br /&gt;
| mechanical connectors=0.05&amp;amp;quot; header&lt;br /&gt;
| mechanical pcb=6-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2013&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/M&lt;br /&gt;
| version=V2.1&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[http://1bitsquared.com/products/lisa-m-autopilot Buy]&lt;br /&gt;
| mcu part=STM32F105RCT6&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=256kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2 &amp;amp; 2RX&lt;br /&gt;
| io i2c=1 + 15&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=3 + 2 (12bit)&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=6 + 2&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=0 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=2&lt;br /&gt;
| io gpio=1&lt;br /&gt;
| io led=5&lt;br /&gt;
| io usb=DFU bootloader&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=JTAG&lt;br /&gt;
| program debug=USB (luftboot)+ JTAG + UART&lt;br /&gt;
| power input=5V - 16V&lt;br /&gt;
| power output=500mA@3.3V, 250mA@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=34mm x 60mm x 10mm&lt;br /&gt;
| mechanical weight=9.9g - 10.8g&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Winter 2012&lt;br /&gt;
| previous version=v2.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Lisa/L&lt;br /&gt;
| version=v1.1&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=STM32F103RE&lt;br /&gt;
| mcu clock=72MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=64kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=Y&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3 &amp;amp; 1RX&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=2&lt;br /&gt;
| io adc=3 (12bit)&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=&lt;br /&gt;
| io led=8&lt;br /&gt;
| io usb=JTAG + UART&lt;br /&gt;
| io can=1&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=Overo Gumstix&lt;br /&gt;
| program debug=JTAG + UART&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=2.25@5V, 2.25A@3.3V, Other&lt;br /&gt;
| power switch=2&lt;br /&gt;
| mechanical size=~100mm x ~50mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Summer 2010&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=KroozSD&lt;br /&gt;
| version=&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://wiki.paparazziuav.org/wiki/KroozSD#Where_to_buy Buy]&lt;br /&gt;
| mcu part=STM32F405RGT6&lt;br /&gt;
| mcu clock=168MHz&lt;br /&gt;
| mcu flash=1024kB&lt;br /&gt;
| mcu ram=128 &amp;amp; 64kB&lt;br /&gt;
| sensor imu=krooz/ext&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=3&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=4 + 1 (12bit)&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=10 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=Xbee&lt;br /&gt;
| periph sd=SPI&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=micro-USB B&lt;br /&gt;
| program debug=&lt;br /&gt;
| power input=7V - 32V&lt;br /&gt;
| power output=1.5A@3.3V, 5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=50mm x 60mm x 10mm&lt;br /&gt;
| mechanical weight=20g - 40g&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=4 x M3&lt;br /&gt;
| introduction date=Spring 2013&lt;br /&gt;
| previous version=Krooz&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Umarim Lite v2 {{!}} Umarim Lite&lt;br /&gt;
| version=V2&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/umarim-lite-v2/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=86&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 4&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=mini-USB B&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=53mm x 25mm&lt;br /&gt;
| mechanical weight=8g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Umarim&lt;br /&gt;
| version=V1.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 4 (10bit)&lt;br /&gt;
| io pwm=6&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 4&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 17V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=56mm x 25mm&lt;br /&gt;
| mechanical weight=9g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Fall 2011&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=NavGo&lt;br /&gt;
| version=V3&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/navgo-v3-00/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 4 (10bit)&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=0 + 1&amp;lt;sup&amp;gt;5&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=0 + 2&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io led=4&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=5.5V - 16V&lt;br /&gt;
| power output=1A@3.3V, 1.5A@5V&lt;br /&gt;
| power switch=N&lt;br /&gt;
| mechanical size=35mm x 35mm&lt;br /&gt;
| mechanical weight=&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Summer 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=Tiny&lt;br /&gt;
| version=v2.11&lt;br /&gt;
| active=Y&lt;br /&gt;
| buy=[https://www.ppzuav.com/shop/index.php/product/tiny-v2-11/ Buy]&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=Y&lt;br /&gt;
| io uart=1&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=0 + 1 (10bit)&amp;lt;sup&amp;gt;6&amp;lt;/sup&amp;gt;&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=1&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=70.8mm x 40mm&lt;br /&gt;
| mechanical weight=24g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=no&lt;br /&gt;
| introduction date=Fall 2007&lt;br /&gt;
| previous version=v1.1&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=TWOG&lt;br /&gt;
| version=v1.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=8 (10bit)&lt;br /&gt;
| io pwm=8&lt;br /&gt;
| io ppm out=1&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=2&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=40.2mm x 30.5mm&lt;br /&gt;
| mechanical weight=8g&lt;br /&gt;
| mechanical connectors=Picoblade&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=no&lt;br /&gt;
| introduction date=Spring 2008&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=YAPA&lt;br /&gt;
| version=v2.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=N&lt;br /&gt;
| sensor mag=N&lt;br /&gt;
| sensor baro=N&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=1&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=6 (10bit)&lt;br /&gt;
| io pwm=10&lt;br /&gt;
| io ppm out=N&lt;br /&gt;
| io ppm in=1&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=1&lt;br /&gt;
| io led=3&lt;br /&gt;
| io usb=bootloader&lt;br /&gt;
| io can=Y&lt;br /&gt;
| io modem=Xbee&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=RS232&lt;br /&gt;
| program debug=USB (pprz bootloader)&lt;br /&gt;
| power input=6.1V - 18V&lt;br /&gt;
| power output=2x 1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=1&lt;br /&gt;
| mechanical size=80.0mm x 40.0mm?&lt;br /&gt;
| mechanical weight=23g w/ XBee?&lt;br /&gt;
| mechanical connectors=0.1&amp;amp;quot; Headers&lt;br /&gt;
| mechanical pcb=2-layer&lt;br /&gt;
| mechanical mounting=4x M3&lt;br /&gt;
| introduction date=Spring 2011&lt;br /&gt;
| previous version=v1.0&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/Entry &lt;br /&gt;
| name=HBmini&lt;br /&gt;
| version=v2.0&lt;br /&gt;
| active=N&lt;br /&gt;
| buy=&lt;br /&gt;
| mcu part=LPC2148&lt;br /&gt;
| mcu clock=60MHz&lt;br /&gt;
| mcu flash=512kB&lt;br /&gt;
| mcu ram=32kB &amp;amp; 8kB&lt;br /&gt;
| sensor imu=Y&lt;br /&gt;
| sensor mag=Y&lt;br /&gt;
| sensor baro=Y&lt;br /&gt;
| sensor diff=N&lt;br /&gt;
| sensor gps=N&lt;br /&gt;
| io uart=2&lt;br /&gt;
| io i2c=2&lt;br /&gt;
| io spi=1&lt;br /&gt;
| io adc=8 (10bit)(16bit)&lt;br /&gt;
| io pwm=10&lt;br /&gt;
| io ppm out=&lt;br /&gt;
| io ppm in=&lt;br /&gt;
| io rc serial=&lt;br /&gt;
| io gpio=11&lt;br /&gt;
| io led=2&lt;br /&gt;
| io usb=bootlader&lt;br /&gt;
| io can=N&lt;br /&gt;
| io modem=N&lt;br /&gt;
| periph sd=N&lt;br /&gt;
| periph rtc=N&lt;br /&gt;
| periph other=Buzzer&lt;br /&gt;
| program debug=JTAG&lt;br /&gt;
| power input=6.1-18V&lt;br /&gt;
| power output=1A@3.3V, 2.25A@5V&lt;br /&gt;
| power switch=4&lt;br /&gt;
| mechanical size=57x30mm&lt;br /&gt;
| mechanical weight=30&lt;br /&gt;
| mechanical connectors=Picoblade &amp;amp; 0.1&amp;amp;quot; Servo&lt;br /&gt;
| mechanical pcb=4-layer&lt;br /&gt;
| mechanical mounting=4 x M2&lt;br /&gt;
| introduction date=Winter 2012&lt;br /&gt;
| previous version=&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
{{P Autopilot Table/End}}&lt;br /&gt;
&lt;br /&gt;
'''Notes:'''&lt;br /&gt;
&lt;br /&gt;
This table was created using a  [https://docs.google.com/spreadsheets/d/1TktQCAiIyBRtwVCMfdT2Y5R6Eyvzh24047Bab7tLsCM/edit?usp=sharing google document spreadsheet]. If you want to add or improve anything in the table, please contact [[User:Esden|Esden]] to get write access to the spreadsheet. This makes editing and maintaining of the table much easier!&lt;br /&gt;
&lt;br /&gt;
'''1.''' Only the newest revisions of the more commonly used autopilots are listed&lt;br /&gt;
&lt;br /&gt;
'''2.''' The extra 8kB of RAM on the LPC2148 shared with the USB DMA&lt;br /&gt;
&lt;br /&gt;
'''3.''' The onboard sensors are almost always supplemented with external sensors. For example, TWOG can use an external IMU or IR sensors, and also needs an external GPS.&lt;br /&gt;
&lt;br /&gt;
'''4.''' Input/Outputs listed are generally those easily accessible on regular autopilot connectors, customization/hacks can modify available I/O, for example free an extra I2C on Tiny and TWOG&lt;br /&gt;
&lt;br /&gt;
'''5., 6.''' Some features use shared resources - denoted by X + Y where Y is shared - and cannot be used simultaneously&lt;br /&gt;
&lt;br /&gt;
'''5.''' Lisa/M v2.0 shared resources include: one I2C is shared with 2 PWM outputs, two ADCs are shared with LEDs, one RX only UART is shared with the PPM capture&lt;br /&gt;
&lt;br /&gt;
'''6.''' Umarim v1.0 shared resources include: 4 ADCs are shared with 4 GPIOs&lt;br /&gt;
&lt;br /&gt;
'''7.''' Usually other unused pins can be used for additional GPIO with some code modifications&lt;br /&gt;
&lt;br /&gt;
'''8.''' Many of the pins have multiple purposes. Servo 5&amp;amp;6 can be used for i2c even though there is no dedicated connector.&lt;br /&gt;
&lt;br /&gt;
'''9.''' The two JST connectors, provide a combined RX and TX connection. The RX &amp;amp; TX lines are combined through a 100Ohm resistor. The GPS and Telemetry connectors are full TTL UARTs.&lt;br /&gt;
&lt;br /&gt;
'''10.''' Only the CAN RX&amp;amp;TX lines are exposed, no transceiver included on board.&lt;br /&gt;
&lt;br /&gt;
[[Category:Hardware]] [[Category:User_Documentation]]&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23435</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23435"/>
		<updated>2017-01-09T10:50:54Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [[Pixhawk|supports]] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
Paparazzi UAV Iris+ Pixhawk tutorial videos - by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab] &amp;lt;br&amp;gt;&lt;br /&gt;
{{#ev:youtubeplaylist|PL_KSX9GOn2P-CVsy-lRSHAnUwVF9wI_pZ}} &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [[Installation|installed]].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [[Pixhawk#Flashing|here] ]&lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build. Uploading is not necessary, this step is required to prevent md5 checksum errors.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select the &amp;lt;i&amp;gt;Flight USB0 @57600&amp;lt;/i&amp;gt; session in Paparazzi Center, and click execute. Paparazzi GCS will start.&lt;br /&gt;
# [[ImuCalibration|Calibrating the Magnetometer]] and [[#Calibrate the ESCs | calibrate the ESCs]] of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the &amp;lt;i&amp;gt;RC direct mode&amp;lt;/i&amp;gt;, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23434</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23434"/>
		<updated>2017-01-09T10:49:48Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: Changed video link&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [[Iris]] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [[#Flashing|below]]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [[Iris]] drone. A list of features that are currently (not) supported in Paparazzi can be found [[#Features|here]].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [[#Flashing|Flashing]]. Details on step 1 can be found [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 10s after start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the IMU to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 IMU:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6000, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
Paparazzi UAV Pixhawk tutorial videos - by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab] &amp;lt;br&amp;gt;&lt;br /&gt;
{{#ev:youtubeplaylist|PL_KSX9GOn2P-CVsy-lRSHAnUwVF9wI_pZ}} &lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23419</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23419"/>
		<updated>2016-12-13T11:00:34Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build. Uploading is not necessary, this step is required to prevent md5 checksum errors.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select the &amp;lt;i&amp;gt;Flight USB0 @57600&amp;lt;/i&amp;gt; session in Paparazzi Center, and click execute. Paparazzi GCS will start.&lt;br /&gt;
# [https://wiki.paparazziuav.org/wiki/ImuCalibration Calibrating the Magnetometer] and [[#Calibrate the ESCs | calibrate the ESCs]] of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the &amp;lt;i&amp;gt;RC direct mode&amp;lt;/i&amp;gt;, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23418</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23418"/>
		<updated>2016-12-13T10:55:27Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# [https://wiki.paparazziuav.org/wiki/ImuCalibration Calibrating the Magnetometer] and [[#Calibrate the ESCs | calibrate the ESCs]] of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the &amp;lt;i&amp;gt;RC direct mode&amp;lt;/i&amp;gt;, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23417</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23417"/>
		<updated>2016-12-13T10:54:13Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# [https://wiki.paparazziuav.org/wiki/ImuCalibration Calibrating the Magnetometer] and [[#calibrate the ESCs|calibrate the ESCs]] of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the &amp;lt;i&amp;gt;RC direct mode&amp;lt;/i&amp;gt;, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23416</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23416"/>
		<updated>2016-12-13T10:37:13Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the &amp;lt;i&amp;gt;RC direct mode&amp;lt;/i&amp;gt;, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23415</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23415"/>
		<updated>2016-12-13T10:27:20Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the RC direct mode, a change is required in the airframe xml configuration. Comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Optionally: change the following lines in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
to:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_RC_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This last step is not required, but properly communicates the new mode to the GCS software.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is &amp;lt;i&amp;gt;strongly&amp;lt;/i&amp;gt; recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware, and if the optional steps were taken, also build and upload the AP. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* On the RC&lt;br /&gt;
** Set the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;&lt;br /&gt;
** Disable manual kill by setting the kill switch (switch 1 in figure 2) to &amp;lt;i&amp;gt;on&amp;lt;/i&amp;gt;&lt;br /&gt;
** Put the throttle to max.&lt;br /&gt;
** Turn on the RC&lt;br /&gt;
* Plug in the usb cable to the Iris+. The AP can now boot. &lt;br /&gt;
* Wait approximately 10 seconds until the leds blinks slow (once per second).&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear a beep coming from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear confirmation beeps from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;br /&gt;
* Revert the changes made to the airframe xml, and upload the firmware(s).&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23414</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23414"/>
		<updated>2016-12-13T09:21:11Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Iris.jpg|thumb|The 3DR Iris+ with 3DR radio and 3DR RC receiver]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
# Optional: the 3DR Tarrot Gimbal and a GoPro 3.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris+.&lt;br /&gt;
&lt;br /&gt;
==Calibrate the ESCs==&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the RC direct mode, a change is required in the airframe xml configuration. Check if the following lines are configured in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Secondly, comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for safety it is strongly recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
Note: &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt; ignores the radio kill switch and software arm procedure, throttle is directly commanded through the stick.&lt;br /&gt;
&lt;br /&gt;
[[File:3DRRC.jpg|thumb|Close up of the 3DR RC receiver. 1) The manual Kill switch. 2) The Gimbal control. 3) The mode switch.]]&lt;br /&gt;
Build and upload the FBW firmware. &lt;br /&gt;
&lt;br /&gt;
The system is now ready to calibrate the ESCs. Perform the following steps:&lt;br /&gt;
* Power off the Iris+&lt;br /&gt;
* Turn on the RC,  the set radio mode (switch 3 in figure 2) to &amp;lt;i&amp;gt;std&amp;lt;/i&amp;gt;, and put the throttle to max.&lt;br /&gt;
* Plug in the battery to the Iris+ (with props removed!). You should hear two beeps from the ESCs.&lt;br /&gt;
* On the RC, put the throttle to zero. You should hear another beep from the ESCs.&lt;br /&gt;
* Validate the range of the throttle stick by slowly throttling up to max. The motors should spin accordingly.&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:3DRRC.jpg&amp;diff=23413</id>
		<title>File:3DRRC.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:3DRRC.jpg&amp;diff=23413"/>
		<updated>2016-12-13T09:00:49Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Close up of the 3DR RC receiver, with the switches as being used in Paparazzi&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Iris.jpg&amp;diff=23412</id>
		<title>File:Iris.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Iris.jpg&amp;diff=23412"/>
		<updated>2016-12-13T08:57:47Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The 3DR Iris+, with 3DR RC and 3DR radio.&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23411</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23411"/>
		<updated>2016-12-13T08:55:13Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris+ drone was manufactured by 3DR and is based around the Pixhawk autopilot. Paparazzi [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk hardware, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with the Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhawk should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris+.&lt;br /&gt;
&lt;br /&gt;
## Calibrate the ESCs&lt;br /&gt;
The original PX4 firmware calibrates the ESCs automatically, paparazzi does not support this. Therefor it is needed to calibrate the ESCs manually. For this two options are available:&lt;br /&gt;
* Calibrate by using a servo tester&lt;br /&gt;
* Calibrate using &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt;&lt;br /&gt;
The first option requires the user to have a servo tester, open up the Iris+ and disconnect wires. Therefor, this wiki describes the second option.&lt;br /&gt;
&lt;br /&gt;
In order to use the RC direct mode, a change is required in the airframe xml configuration. Check if the following lines are configured in the section AUTOPILOT:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_STARTUP&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;MODE_MANUAL&amp;quot; value=&amp;quot;AP_MODE_ATTITUDE_DIRECT&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Secondly, comment or temporarily remove the following line:&lt;br /&gt;
{{Box Code|conf/airframes/TUDELFT/tudelft_iris_indi.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;define name=&amp;quot;FBW_MODE_AUTO_ONLY&amp;quot; value=&amp;quot;true&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&amp;lt;b&amp;gt; Important: for your own safety it is strongly recommended to remove the propellers &amp;lt;/b&amp;gt; &amp;lt;br/&amp;gt;&lt;br /&gt;
Note: &amp;lt;i&amp;gt; mode RC direct&amp;lt;/i&amp;gt; ignores the radio kill switch and software arm procedure, throttle is directly commanded through the stick!&lt;br /&gt;
&lt;br /&gt;
Build and upload the AP. Turn on the radio, plug in the battery to the Iris+ (with props removed!), and the set radio mode to &amp;lt;i&amp;gt;std&amp;lt;i/&amp;gt; (see figure 2)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23410</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23410"/>
		<updated>2016-12-13T08:02:04Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris drone was manufactured by 3DR and is based arround the Pixhawk autopilot. Paparazzi fully [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with a Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhwak should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Make sure to set the target to AP again, and build.&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris.&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23409</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23409"/>
		<updated>2016-12-09T10:55:29Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing Flashing]. Details on step 1 can be found [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 10s after start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the IMU to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 IMU:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6000, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23408</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23408"/>
		<updated>2016-12-09T10:53:51Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing Flashing]. Details on step 1 can be found [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 10s after start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the imu to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 imu:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6000, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23407</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23407"/>
		<updated>2016-12-09T10:51:44Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing Flashing]. Details on step 1 can be found [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 10s after start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the imu to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 imu:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23406</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23406"/>
		<updated>2016-12-09T10:48:20Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found in [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing Flashing]. Details on step 1 can be found in [[#Airframe config|further below]].&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Airframe config=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, some Pixhawk specific configuration is required. &lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 after 10s start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the imu to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 imu:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23405</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23405"/>
		<updated>2016-12-09T10:40:10Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
= Pixhawk specific airframe config steps=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, the following configuration steps are required:&lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 after 10s start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the imu to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 imu:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
*Add the px4_flash module:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;modules main_freq=&amp;quot;512&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;px4_flash&amp;quot; /&amp;gt;&lt;br /&gt;
    ...&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
This enables uploading through the PX4 bootloading and activates the usb-serial device after startup.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23404</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23404"/>
		<updated>2016-12-09T10:36:47Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: Added airframe config&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
= Pixhawk specific airframe config steps=&lt;br /&gt;
&lt;br /&gt;
In order to fly a drone with the Pixhawk system in paparazzi, the following configuration steps are required:&lt;br /&gt;
&lt;br /&gt;
* Define seperate &amp;lt;firmware&amp;gt;'s for both the fbw and the ap:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;ap&amp;quot; board=&amp;quot;px4fmu_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;target name=&amp;quot;fbw&amp;quot; board=&amp;quot;px4io_2.4&amp;quot; /&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*Configure the interMCU communication to use UART 6 at the AP:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART6&amp;quot; /&amp;gt;&lt;br /&gt;
   &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt; &amp;lt;!-- This is only during first 10s start up, afterwards it is set to 230400--&amp;gt;&lt;br /&gt;
&amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
And at the FBW:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
    &amp;lt;define name=&amp;quot;INTERMCU_LOST_CNT&amp;quot; value=&amp;quot;100&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;module name=&amp;quot;intermcu&amp;quot; type=&amp;quot;uart&amp;quot;&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_PORT&amp;quot; value=&amp;quot;UART2&amp;quot; /&amp;gt;&lt;br /&gt;
      &amp;lt;configure name=&amp;quot;INTERMCU_BAUD&amp;quot; value=&amp;quot;B1500000&amp;quot; /&amp;gt;&lt;br /&gt;
    &amp;lt;/module&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Configuration of the baud at 1500000 is strongly recommended, as this will remain backwards compatible with the PX4 code and bootloader. However, in Paparazzi the baud rate is slowed down to 230400 after 10s start up, as the Pixhawk hardware actually does not seem to support flawless data transfers at those speeds. At least not in Paparazzi.&lt;br /&gt;
*Define the imu to be:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;px4fmu_v2.4&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
Which uses the l3gd20 gyro and the lsm303d accelero. The Pixhawk has two IMU's, so alternatively you can also use the MPU6000 imu:&lt;br /&gt;
{{Box Code|conf/airframes/&amp;lt;yourairframe&amp;gt;.xml|&amp;lt;source lang=&amp;quot;xml&amp;quot;&amp;gt;&lt;br /&gt;
&amp;lt;module name=&amp;quot;imu&amp;quot; type=&amp;quot;mpu6000&amp;quot;/&amp;gt;&lt;br /&gt;
&amp;lt;/source&amp;gt;}}&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23403</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23403"/>
		<updated>2016-12-04T12:07:54Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone]. A list of features that are currently (not) supported in Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Features here].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23402</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23402"/>
		<updated>2016-12-04T12:06:22Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide on how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23401</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23401"/>
		<updated>2016-12-04T12:03:54Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide of how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site]. Details on how to flash the board with Paparazzi can be found [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing below]. A complete step by step example on how to get a drone flying with Paparazzi + Pixhawk is provided with the [https://wiki.paparazziuav.org/wiki/Iris Iris drone].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23400</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23400"/>
		<updated>2016-12-04T11:54:44Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
An step-by-step example on flying Paparazzi with a Pixhawk can be found on the [https://wiki.paparazziuav.org/wiki/Iris Iris] page.&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide of how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23399</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23399"/>
		<updated>2016-12-04T11:53:06Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide of how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the [https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/TUDELFT/tudelft_iris_indi.xml Iris airframe] )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
* To flash the AP (See figure 2 and 3):&lt;br /&gt;
** Select your aircraft (1).&lt;br /&gt;
** Select the AP (2).&lt;br /&gt;
** Click the build button (3). &lt;br /&gt;
** After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (5). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (6). &lt;br /&gt;
&lt;br /&gt;
* To flash the FBW  (See figure 4 and 5): &lt;br /&gt;
** Select FBW (7).&lt;br /&gt;
** Click the build button (8).&lt;br /&gt;
** After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk.&lt;br /&gt;
** After 5 seconds click upload (10). &lt;br /&gt;
** You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Notes:&lt;br /&gt;
* After flashing the FBW, it is required to re-power the Pixhawk. &lt;br /&gt;
* The flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
* Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
* In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23398</id>
		<title>Iris</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Iris&amp;diff=23398"/>
		<updated>2016-12-04T11:42:20Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: Iris step-by-step initial&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= Introduction =&lt;br /&gt;
&lt;br /&gt;
The Iris drone was manufactured by 3DR and is based arround the Pixhawk autopilot. Paparazzi fully [https://wiki.paparazziuav.org/wiki/Pixhawk supports] the Pixhawk, and this page serves as simple step-by-step guide to get a Pixhawk based drone flying on with the Paparazzi autopilot. In this example, only standard Pixhawk hardware is used, as it comes delivered with the stock Iris.&lt;br /&gt;
&lt;br /&gt;
= Getting the Iris flight ready=&lt;br /&gt;
&lt;br /&gt;
You'll need:&lt;br /&gt;
# The stock Iris drone, (equipped with a Pixhawk), &lt;br /&gt;
# Its stock 3DR radio's and 3DR RC. &lt;br /&gt;
# The Pixhwak should still contain the PX4 / APM bootloader. &lt;br /&gt;
# A computer with Paparazzi [http://wiki.paparazziuav.org/wiki/Installation installed].&lt;br /&gt;
# A micro USB cable.&lt;br /&gt;
&lt;br /&gt;
Steps you will need to perform: &lt;br /&gt;
# Plug in the USB cable to the Iris. &amp;lt;b&amp;gt;Remove the props. Leave the battery disconnected.&amp;lt;/b&amp;gt;&lt;br /&gt;
# Flash both the AP and FBW. See [https://wiki.paparazziuav.org/wiki/Pixhawk#Flashing here] &lt;br /&gt;
# Power cycle the Pixhawk (e.g. replug USB).&lt;br /&gt;
# Plug in the 3DR radio to the computer. Select USB0 session in Paparazzi Center.&lt;br /&gt;
# Calibrate the IMU and the ESCs of the Iris.&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23396</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23396"/>
		<updated>2016-12-02T10:14:07Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: Spelling errors&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETHZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the USB port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide of how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in Paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3-axis acc + magneto, L3G 3-axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the Iris airframe )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the AP firmware&lt;br /&gt;
*3. Replug the USB, and upload the FBW code. Replug USB again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (AutoPilot on the PX4FMU)  and the FBW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed with Paparazzi first.&lt;br /&gt;
&lt;br /&gt;
To flash the AP, select your aircraft (1), select the AP (2), and click the build button (3). After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk, and after 5 seconds click upload (5). You should see &amp;quot;upload successful&amp;quot; (6). See figure 2 and 3.&lt;br /&gt;
&lt;br /&gt;
To flash the FBW, select FBW (7) and click the build button (8). After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk, and after 5 seconds click upload (10). You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Note: After flashing the FBW, it is required to re-power the Pixhawk. Secondly, the flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the USB device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23395</id>
		<title>Pixhawk</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=Pixhawk&amp;diff=23395"/>
		<updated>2016-11-30T14:33:05Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;div style=&amp;quot;float: right; width: 45%; overflow: hidden&amp;quot;&amp;gt;[[File:Pixhawk 1 v2.4.jpg|thumb|Pixhawk 1 v2.4]]&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=Paparazzi on Pixhawk=&lt;br /&gt;
&lt;br /&gt;
The Pixhawk is an open hardware autopilot that was originally developed by ETZ in the [https://pixhawk.ethz.ch/ PIXHAWK project]. Paparazzi now supports the Pixhawk and the firmware can be uploaded through the orignal PX4 custom bootloader, which happens directly through the usb port of the Pixhawk. This means that it is possible to easily switch between the Paparazzi AP and other projects that support the Pixhawk hardware (i.e. PX4 and APM). &lt;br /&gt;
&lt;br /&gt;
It is also possible to directly upload to the Pixhawk by means of the JTAG port, but this is not recommended as it involves soldering and permanently removes the PX4 bootloader (which means reverting to PX4 or APM firmware is complicated). Therefor, this wiki focuses on flashing through the PX4 bootloader.&lt;br /&gt;
&lt;br /&gt;
=Intro=&lt;br /&gt;
&lt;br /&gt;
This page is intended as a guide of how to get the Paparazzi autopilot running on a Pixhawk board. For the specifications and pin-out details we recommend to look at the [https://pixhawk.org/modules/pixhawk Pixhawk site].&lt;br /&gt;
&lt;br /&gt;
The Pixhawk consists of the PX4IO (designed around a stm32f1) and the PX4FMU (designed around a stm32f4), which are glued together in one pcb. Uploading of the autopilot (which runs only on the PX4FMU) happens directly from computer over USB to the PX4FMU, by means of the PX4 bootloader. In the original PX4 and APM Pixhawk software, the compiled PX4IO code (which runs the Fly By Wire) is embedded with the PX4FMU code, and the PX4FMU code would flash the PX4IO board at startup. But, in paparazzi, the PX4IO is flashed from the computer --&amp;gt; USB -&amp;gt; PX4FMU --&amp;gt; internal UART --&amp;gt; PX4IO, directly from Paparazzi Center. This means PX4IO board can be flashed without changing the autopilot, and vice versa.&lt;br /&gt;
&lt;br /&gt;
=Features=&lt;br /&gt;
The features that are currently supported by Paparazzi are the following:&lt;br /&gt;
&lt;br /&gt;
*The dual processor setup (main stm32f4 and co stm32f1 processor), in a AP (AutoPilot) + FBW (Fly By Wire)&lt;br /&gt;
*Dual IMU (selectable from airframe config)&lt;br /&gt;
**MPU6050, 3axis acc + gyro + magneto&lt;br /&gt;
**LSM303 3 axis acc + magneto, L3G 3 axis gyro&lt;br /&gt;
*External GPS + Magneto&lt;br /&gt;
*8+6 pwm outputs (8 on FBW, 6 on AP)&lt;br /&gt;
*Arm button led denotes mode info&lt;br /&gt;
*Spektrum RC, including binding through software&lt;br /&gt;
*PPM RC&lt;br /&gt;
&lt;br /&gt;
The features that are not yet supported by Paparazzi are the following:&lt;br /&gt;
*The multicolor led&lt;br /&gt;
*The buzzer&lt;br /&gt;
*The on-board arm button&lt;br /&gt;
*The SD card SDIO &lt;br /&gt;
*SBus out, RC downlink (e.g. gps info, battery info)&lt;br /&gt;
&lt;br /&gt;
=Getting started=&lt;br /&gt;
&lt;br /&gt;
In short, the steps you'll need to run through are roughly the following:&lt;br /&gt;
&lt;br /&gt;
*1. Define your aircraft and settings for the Pixhawk (e.g. see the Iris airframe )&lt;br /&gt;
*2. Connect the Pixhawk via USB to your computer, and upload the firmware&lt;br /&gt;
*3. Replug the usb, and upload the FBW code. Replug usb again.&lt;br /&gt;
&lt;br /&gt;
Details on steps 2 and 3 can be found below.&lt;br /&gt;
&lt;br /&gt;
=Flashing=&lt;br /&gt;
[[File:Build AP.jpg|thumb|Figure 2; building the AP]]&lt;br /&gt;
[[File:Upload AP.jpg|thumb|Figure 3; flashing the AP]]&lt;br /&gt;
[[File:Build FBW.jpg|thumb|Figure 4; building the FBW]]&lt;br /&gt;
[[File:Upload FBW.jpg|thumb|Figure 5; flashing the FBW]]&lt;br /&gt;
&lt;br /&gt;
In order to flash the Pixhawk, both the AP (autopilot on the PX4FMU)  and the FNW (Fly By Wire on the PX4IO) have to be flashed. Paparazzi uses the default PX4 bootloader to upload and flash the code in both systems, but the FBW is flashed through the AP. This means that at least for the first time, the AP has to be flashed first.&lt;br /&gt;
&lt;br /&gt;
To flash the AP, select your aircraft (1), select the AP (2), and click the build button (3). After the compilation was completed successfully (4), plug in the USB cable to computer and the Pixhawk, and click upload (5). You should see &amp;quot;upload successful&amp;quot; (6). See figure 2 and 3.&lt;br /&gt;
&lt;br /&gt;
To flash the FBW, select FBW (7) and click the build button (8). After the compilation was completed successfully (9), plug in the USB cable to computer and the Pixhawk, and click upload (10). You should see &amp;quot;upload successful&amp;quot; (11). &lt;br /&gt;
&lt;br /&gt;
Note: After flashing the FBW, it is required to re-power the Pixhawk. Secondly, the flashing of the FBW is disabled 20 seconds after power up. Re-power to reset the time. &lt;br /&gt;
&lt;br /&gt;
[[File:Upload problems.jpg|thumb|Figure 6; upload problems]]&lt;br /&gt;
In case of problems such as in figure 6, most of the time it can be solved by re-powering the Pixhawk (e.g. re-plugging the USB, and removing the battery), wait for 5 seconds for the computer to recognize the usb device, and click the upload button again.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Whether the current code is APM, PX4 or Paparazzi, the flashing steps remain the same.&lt;br /&gt;
&lt;br /&gt;
=Videos=&lt;br /&gt;
&lt;br /&gt;
{{#ev:youtube|h44Np-O_X0w|200|left}} Paparazzi UAV Pixhawk support teaser - Video by the [http://mavlab.lr.tudelft.nl/ TU Delft MAVLab]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;br style=&amp;quot;clear:both&amp;quot;&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=External links=&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Upload_problems.jpg&amp;diff=23394</id>
		<title>File:Upload problems.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Upload_problems.jpg&amp;diff=23394"/>
		<updated>2016-11-30T13:52:04Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Figure 6; upload problems&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Upload_FBW.jpg&amp;diff=23393</id>
		<title>File:Upload FBW.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Upload_FBW.jpg&amp;diff=23393"/>
		<updated>2016-11-30T13:45:45Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Flashing the FBW&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Build_FBW.jpg&amp;diff=23392</id>
		<title>File:Build FBW.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Build_FBW.jpg&amp;diff=23392"/>
		<updated>2016-11-30T13:44:36Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Building the FBW&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Upload_AP.jpg&amp;diff=23391</id>
		<title>File:Upload AP.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Upload_AP.jpg&amp;diff=23391"/>
		<updated>2016-11-30T13:43:52Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Flashing the AP&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Build_AP.jpg&amp;diff=23390</id>
		<title>File:Build AP.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Build_AP.jpg&amp;diff=23390"/>
		<updated>2016-11-30T13:42:10Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Building the autopilot screenshot&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
	<entry>
		<id>http://wiki.paparazziuav.org/w/index.php?title=File:Pixhawk_1_v2.4.jpg&amp;diff=23389</id>
		<title>File:Pixhawk 1 v2.4.jpg</title>
		<link rel="alternate" type="text/html" href="http://wiki.paparazziuav.org/w/index.php?title=File:Pixhawk_1_v2.4.jpg&amp;diff=23389"/>
		<updated>2016-11-30T08:49:57Z</updated>

		<summary type="html">&lt;p&gt;Kevindehecker: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Pixhawk 1 in hand&lt;/div&gt;</summary>
		<author><name>Kevindehecker</name></author>
	</entry>
</feed>