PaparazziUAV - User contributions [en]

Users

2009-04-02T22:29:03Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

==Need help adding your information?==
To have your information added by another paparazzi user, please send me an [http://www.rcgroups.com/forums/showpost.php?p=6575288&postcount=1 EMAIL] at with the
following:

*Name
*Email
*Location
*Hardware
*Join date
*Current activities / project status

== Wiki pages ==
add a link to your users wiki page.

[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]

[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]

[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]

[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]

[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]

[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]

[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]

[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]

[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]

==Asia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|- style="background:bisque; color:black"
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet
|- style="background:bisque; color:black"
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon
|}

==Europe==
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe

! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.

|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz, Austria || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.

|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.

|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.

|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues

|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.

|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009

|- style="background:bisque; color:black"
| [mailto:felix.ruess_at_gmail.com FelixR] || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter

|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.

|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.

|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.

|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.

|- style="background:bisque; color:black"
| [mailto:chebuzz_at_gmail.com David "Buzz" Carlson] || Cyprus || Tiny 2.11, Lynx EDF & GWS SloStick, 9XTend datalink ||| 2008 || Quite a few AUTO2 flights. Plane currently grounded due to a TX run-in with a 1 year-old. Currently working on getting new TX and completing CBP store setup.

|- style="background:bisque; color:black"
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || none || 2008 || Starting

|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==North America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status

|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]

|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] [http://paparazzi.enac.fr/wiki/User:John_Burt wiki page]|| Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Initial flight tests w/ Easystar in AUTO1 & AUTO2.

|- style="background:bisque; color:black"
| [mailto:ogar0007@umn.edu Pat O'Gara] || St. Paul, MN || Tiny 2.11 and TWOG (PPZUAV) |||Oct. 2008 || Completed and flown FunJet and Minimag in Auto 2. Currently rebuilding MiniMag as an improved development platform. http://www.patogara.com

|- style="background:bisque; color:black"
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.

|- style="background:bisque; color:black"
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 ||

|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.

|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937.

|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.

|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU Fuel Cell UAV] || Fort Collins, Co || Tiny 2.11 + LEA-5H (PPZUAV), 2.4Ghz XBPro ||| Mar 2009 || Maiden flight complete Feb 28. New Airframe in development.

|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV). Multiplex Mentor ||| 2008 || Seven flights now. Flights 6 & 7 in Auto2. Now only a matter of fine tuning.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Gallery

2009-03-30T20:08:36Z

Joekadet: /* User's Aircraft Gallery */

== User's Gallery ==
=== User's Aircraft Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.JPG|Multiplex Mentor Joekadet, 7 flights, Auto2 working now.
</gallery>
|

|}

==Video==

http://www.youtube.com/watch?v=M1k_TLcQ2ic

== Flight competitions ==
=== [http://www.nal.res.in/MAV08/ MAV08] ===
; Agra, India, (March 10th -- 15th, 2008)
Best Mission Performance:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Paparazzi Slicer (ENAC)
* Paparazzi Glass One(s) (Martin Mueller Engineering)
* Paparazzi Dragonfly (University of Arizona)

Best Hover Performance/Rotorcraft:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Indian Institute of Technology, Bombay (IITB)

Best Autonomous Micro Air Vehicle:
* Paparazzi Slicer (ENAC)

Best Exotic Design Micro Air Vehicle:
* Paparazzi Dragonfly (University of Arizona)

Best UGV Performance:
* [http://cmr.mech.unsw.edu.au/mavstar/ MAVSTAR] (UNSW)

{|
|-valign="top"
|
<gallery caption="MAV08, Agra, India">
Image:Slicer.jpg|Slicer ENAC
Image:Glassone.jpg|Glass One 
Image:MAVSTAR.jpg|MAVSTAR 
</gallery>
|}

=== MAV07 ===
; Toulouse, France, (September 19th - 22nd, 2007)
* 1st place (shared): Paparazzi ''Dragon Slayer''
* 1st place (shared): Micropilot ''Ping Wing''
* 3rd place : Paparazzi ''Tyto'' (Supaero)
* 4th place : Paparazzi ''MAC 07'' (Martin Mueller Engineering)
* 5th place : Paparazzi ''Storm1'' (Murat Bronz)
{|
|-valign="top"
|
<gallery caption="MAV07, Toulouse">
Image:Slayer-105416sm.jpg|Dragon Slayer Miraterre Flight Systems
Image:Twisted_1413sm.jpg|Twisted Logic Miraterre Flight Systems
Image:Storm1.jpg|Storm1 Murat BRONZ
Image:Pingwing.jpg|Ping Wing Sweden
Image:Tyto.jpg|Tyto Supaero
Image:Redone.jpg|Red One/MAC 07 
</gallery>
|}

=== MAV06 ===
; Sandestin, Florida, USA (October 29th - November 2nd, 2006)
* 1st place : Procerus Kestrel (Bringham Young University)
* 2nd place : Paparazzi ''Dualing Slayers'' (ENAC / Miraterre)
* 3rd place : Paparazzi ''Black One'' ("fake" Martin Mueller Engineering)
{|
|-valign="top"
|
<gallery caption="MAV06, Florida">
Image:MAC-OrangeOne-MAV06.jpg|Orange One Martin Mueller and Christian Lindenberg
Image:MAC-BlackOne-MAV06.jpg|Black One Martin Mueller and Christian Lindenberg
Image:ENAC-Planning-MAV06.jpg|ENAC Team
Image:Slayers-MAV06.jpg|Dragon Slayers Slayers acquiring GPS fix 
Image:Michel_vs_Slayer-MAV06.jpg|Catch! Michel bravely catching the Slayer in an autonomous landing 
Image:BYU-MAV06.jpg|BYU's Winning Design BYU used the Procerus Kestrel autopilot 
</gallery>
|}

=== EMAV2006 ===
; Braunschweig, Niedersachsen, Germany (25-26 July 2006)
* 1st place : Paparazzi ''DragonSlayer/BlackOne/Microjet''
* 2nd place : Paparazzi ''JeanMav360''

{|
|-valign="top"
|
[[Image:emav2006_paparazzies.jpg|thumb|left|EMAV06 Paparazzi Team]]
 
|}

=== MAV05 ===
; Garmisch-Partenkirchen, Bavaria, Germany (17-23 September 2005)
* 1st place : Paparazzi ''Dragonfly''
* 2nd place : Paparazzi ''Glotzer''
* 3rd place : Paparazzi ''Plaster''
* 4th place : Paparazzi ''Plaster duo''

{|
|-valign="top"
|
<gallery caption="MAV05, Germany"
Image:MAV05_paparazzies.jpg|The Paparazzi teams in Garmisch
Image:mav05_dragonfly.jpg|Dragonfly ''University of Arizona''
Image:mav05_depronazzi.jpg|Glotzer ''Martin Mueller and Christian Lindenberg''
Image:mav05_ladybug.jpg|Ladybug ''ENAC''
Image:mav05_enac.jpg|ENAC Team
</gallery>
|}

=== 4eme Journées microdrones ===
; Toulouse, France ( 15 septembre 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
| [[Image:Paparazzi_Equiped_Aircraft.jpg|thumb|left|Microjet]] 
|}

=== EMAV2004 ===
; Braunschweig, Niedersachsen, Germany (13 July 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
|
<gallery caption="EMAV2004">
Image:emav04_01.jpg|The Paparazzi team
Image:emav04_02.jpg|Spectators
Image:emav04_03.jpg|Automatic tracking antenna
</gallery>
|}

=== EMAV2003 ===
; Toulouse, France ( 3 october 2003)
* 1st place : Paparazzi ''Twinstar''

{|-valign="top"
|
<gallery caption="EMAV2003">
Image:emav03_01.jpg|Twinstar ready for flight
Image:emav03_02.jpg|Paparazzi team
</gallery>
|
|}

== Scientific campaigns ==

=== FLOHOF 2007 ===
; Around the Hofsjökull glacier, Iceland, (August 2007)
{|
|-valign="top"
|
<gallery caption="FLOHOF 2007, Iceland">
Image:Kerlingafjoll.jpg|Flying southwest of the glacier
Image:High_alt.png|Climb slope
</gallery>
|}

=== THORPEX/Svalbard 2008 ===
; On and around Svalbard, Arctic Sea, (February 25th - March 15th, 2008)
{|
|-valign="top"
|
<gallery caption="THORPEX 2008, Svalbard">
Image:Kv_svalbard_ice.jpg|KV Svalbard
Image:Hangar.jpg|The KV Svalbard hangar
Image:Funjet_spitsbergen.jpg|Flying over the icy sea near Spitsbergen
Image:Waves.jpg|Waves in rough sea
Image:Breaking_ice.jpg|Breaking the ice
Image:Longyearbyen.jpg|Preparing the aircraft
Image:Landing_spitsbergen.jpg|Landing near Longyearbyen
</gallery>
|}

Users

2009-03-16T00:48:31Z

Joekadet: /* Central America */

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

==Need help adding your information?==
To have your information added by another paparazzi user, please send me an [http://www.rcgroups.com/forums/showpost.php?p=6575288&postcount=1 EMAIL] at with the
following:

*Name
*Email
*Location
*Hardware
*Join date
*Current activities / project status

== Wiki pages ==
add a link to your users wiki page.

[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]

[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]

[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]

[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]

[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]

[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]

[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]

[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]

==Asia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|- style="background:bisque; color:black"
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet
|- style="background:bisque; color:black"
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon
|}

==Europe==
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe

! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz, Austria || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| FelixR || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter
|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.
|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.
|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.
|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.
|- style="background:bisque; color:black"
| [mailto:chebuzz_at_gmail.com David "Buzz" Carlson] || Cyprus || Tiny 2.11, Lynx EDF & GWS SloStick, 9XTend datalink ||| 2008 || Quite a few AUTO2 flights. Plane currently grounded due to a TX run-in with a 1 year-old. Currently working on getting new TX and completing CBP store setup.
|- style="background:bisque; color:black"
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || none || 2008 || Starting
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==North America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] [http://paparazzi.enac.fr/wiki/User:John_Burt wiki page]|| Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Initial flight tests w/ Easystar in AUTO1 & AUTO2.
|- style="background:bisque; color:black"
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.
|- style="background:bisque; color:black"
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 ||
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| CSU FC UAV || Fort Collins, Co || Tiny 2.11 + LEA-5H (PPZUAV), 2.4Ghz XBPro ||| Mar 2009 || Maiden flight complete Feb 28. New Airframe in development.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV). Multiplex Mentor ||| 2008 || Five flights now and AUTO1 is dialed in. AUTO2 next.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Gallery

2009-03-16T00:46:03Z

Joekadet: /* User's Gallery */

== User's Gallery ==
=== User's Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.JPG|Multiplex Mentor Joekadet, 5 flights, Auto1 done, need to get Auto2 to working.
</gallery>
|

|}

== Flight competitions ==
=== [http://www.nal.res.in/MAV08/ MAV08] ===
; Agra, India, (March 10th -- 15th, 2008)
Best Mission Performance:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Paparazzi Slicer (ENAC)
* Paparazzi Glass One(s) (Martin Mueller Engineering)
* Paparazzi Dragonfly (University of Arizona)

Best Hover Performance/Rotorcraft:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Indian Institute of Technology, Bombay (IITB)

Best Autonomous Micro Air Vehicle:
* Paparazzi Slicer (ENAC)

Best Exotic Design Micro Air Vehicle:
* Paparazzi Dragonfly (University of Arizona)

Best UGV Performance:
* [http://cmr.mech.unsw.edu.au/mavstar/ MAVSTAR] (UNSW)

{|
|-valign="top"
|
<gallery caption="MAV08, Agra, India">
Image:Slicer.jpg|Slicer ENAC
Image:Glassone.jpg|Glass One 
Image:MAVSTAR.jpg|MAVSTAR 
</gallery>
|}

=== MAV07 ===
; Toulouse, France, (September 19th - 22nd, 2007)
* 1st place (shared): Paparazzi ''Dragon Slayer''
* 1st place (shared): Micropilot ''Ping Wing''
* 3rd place : Paparazzi ''Tyto'' (Supaero)
* 4th place : Paparazzi ''MAC 07'' (Martin Mueller Engineering)
* 5th place : Paparazzi ''Storm1'' (Murat Bronz)
{|
|-valign="top"
|
<gallery caption="MAV07, Toulouse">
Image:Slayer-105416sm.jpg|Dragon Slayer Miraterre Flight Systems
Image:Twisted_1413sm.jpg|Twisted Logic Miraterre Flight Systems
Image:Storm1.jpg|Storm1 Murat BRONZ
Image:Pingwing.jpg|Ping Wing Sweden
Image:Tyto.jpg|Tyto Supaero
Image:Redone.jpg|Red One/MAC 07 
</gallery>
|}

=== MAV06 ===
; Sandestin, Florida, USA (October 29th - November 2nd, 2006)
* 1st place : Procerus Kestrel (Bringham Young University)
* 2nd place : Paparazzi ''Dualing Slayers'' (ENAC / Miraterre)
* 3rd place : Paparazzi ''Black One'' ("fake" Martin Mueller Engineering)
{|
|-valign="top"
|
<gallery caption="MAV06, Florida">
Image:MAC-OrangeOne-MAV06.jpg|Orange One Martin Mueller and Christian Lindenberg
Image:MAC-BlackOne-MAV06.jpg|Black One Martin Mueller and Christian Lindenberg
Image:ENAC-Planning-MAV06.jpg|ENAC Team
Image:Slayers-MAV06.jpg|Dragon Slayers Slayers acquiring GPS fix 
Image:Michel_vs_Slayer-MAV06.jpg|Catch! Michel bravely catching the Slayer in an autonomous landing 
Image:BYU-MAV06.jpg|BYU's Winning Design BYU used the Procerus Kestrel autopilot 
</gallery>
|}

=== EMAV2006 ===
; Braunschweig, Niedersachsen, Germany (25-26 July 2006)
* 1st place : Paparazzi ''DragonSlayer/BlackOne/Microjet''
* 2nd place : Paparazzi ''JeanMav360''

{|
|-valign="top"
|
[[Image:emav2006_paparazzies.jpg|thumb|left|EMAV06 Paparazzi Team]]
 
|}

=== MAV05 ===
; Garmisch-Partenkirchen, Bavaria, Germany (17-23 September 2005)
* 1st place : Paparazzi ''Dragonfly''
* 2nd place : Paparazzi ''Glotzer''
* 3rd place : Paparazzi ''Plaster''
* 4th place : Paparazzi ''Plaster duo''

{|
|-valign="top"
|
<gallery caption="MAV05, Germany"
Image:MAV05_paparazzies.jpg|The Paparazzi teams in Garmisch
Image:mav05_dragonfly.jpg|Dragonfly ''University of Arizona''
Image:mav05_depronazzi.jpg|Glotzer ''Martin Mueller and Christian Lindenberg''
Image:mav05_ladybug.jpg|Ladybug ''ENAC''
Image:mav05_enac.jpg|ENAC Team
</gallery>
|}

=== 4eme Journées microdrones ===
; Toulouse, France ( 15 septembre 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
| [[Image:Paparazzi_Equiped_Aircraft.jpg|thumb|left|Microjet]] 
|}

=== EMAV2004 ===
; Braunschweig, Niedersachsen, Germany (13 July 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
|
<gallery caption="EMAV2004">
Image:emav04_01.jpg|The Paparazzi team
Image:emav04_02.jpg|Spectators
Image:emav04_03.jpg|Automatic tracking antenna
</gallery>
|}

=== EMAV2003 ===
; Toulouse, France ( 3 october 2003)
* 1st place : Paparazzi ''Twinstar''

{|-valign="top"
|
<gallery caption="EMAV2003">
Image:emav03_01.jpg|Twinstar ready for flight
Image:emav03_02.jpg|Paparazzi team
</gallery>
|
|}

== Scientific campaigns ==

=== FLOHOF 2007 ===
; Around the Hofsjökull glacier, Iceland, (August 2007)
{|
|-valign="top"
|
<gallery caption="FLOHOF 2007, Iceland">
Image:Kerlingafjoll.jpg|Flying southwest of the glacier
Image:High_alt.png|Climb slope
</gallery>
|}

=== THORPEX/Svalbard 2008 ===
; On and around Svalbard, Arctic Sea, (February 25th - March 15th, 2008)
{|
|-valign="top"
|
<gallery caption="THORPEX 2008, Svalbard">
Image:Kv_svalbard_ice.jpg|KV Svalbard
Image:Hangar.jpg|The KV Svalbard hangar
Image:Funjet_spitsbergen.jpg|Flying over the icy sea near Spitsbergen
Image:Waves.jpg|Waves in rough sea
Image:Breaking_ice.jpg|Breaking the ice
Image:Longyearbyen.jpg|Preparing the aircraft
Image:Landing_spitsbergen.jpg|Landing near Longyearbyen
</gallery>
|}

Gallery

2009-03-14T15:52:19Z

Joekadet: /* User's Gallery */

== User's Gallery ==
=== User's Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.JPG|Multiplex Mentor Joekadet, 2 flights, in process of tuning in auto1
</gallery>
|

|}

== Flight competitions ==
=== [http://www.nal.res.in/MAV08/ MAV08] ===
; Agra, India, (March 10th -- 15th, 2008)
Best Mission Performance:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Paparazzi Slicer (ENAC)
* Paparazzi Glass One(s) (Martin Mueller Engineering)
* Paparazzi Dragonfly (University of Arizona)

Best Hover Performance/Rotorcraft:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Indian Institute of Technology, Bombay (IITB)

Best Autonomous Micro Air Vehicle:
* Paparazzi Slicer (ENAC)

Best Exotic Design Micro Air Vehicle:
* Paparazzi Dragonfly (University of Arizona)

Best UGV Performance:
* [http://cmr.mech.unsw.edu.au/mavstar/ MAVSTAR] (UNSW)

{|
|-valign="top"
|
<gallery caption="MAV08, Agra, India">
Image:Slicer.jpg|Slicer ENAC
Image:Glassone.jpg|Glass One 
Image:MAVSTAR.jpg|MAVSTAR 
</gallery>
|}

=== MAV07 ===
; Toulouse, France, (September 19th - 22nd, 2007)
* 1st place (shared): Paparazzi ''Dragon Slayer''
* 1st place (shared): Micropilot ''Ping Wing''
* 3rd place : Paparazzi ''Tyto'' (Supaero)
* 4th place : Paparazzi ''MAC 07'' (Martin Mueller Engineering)
* 5th place : Paparazzi ''Storm1'' (Murat Bronz)
{|
|-valign="top"
|
<gallery caption="MAV07, Toulouse">
Image:Slayer-105416sm.jpg|Dragon Slayer Miraterre Flight Systems
Image:Twisted_1413sm.jpg|Twisted Logic Miraterre Flight Systems
Image:Storm1.jpg|Storm1 Murat BRONZ
Image:Pingwing.jpg|Ping Wing Sweden
Image:Tyto.jpg|Tyto Supaero
Image:Redone.jpg|Red One/MAC 07 
</gallery>
|}

=== MAV06 ===
; Sandestin, Florida, USA (October 29th - November 2nd, 2006)
* 1st place : Procerus Kestrel (Bringham Young University)
* 2nd place : Paparazzi ''Dualing Slayers'' (ENAC / Miraterre)
* 3rd place : Paparazzi ''Black One'' ("fake" Martin Mueller Engineering)
{|
|-valign="top"
|
<gallery caption="MAV06, Florida">
Image:MAC-OrangeOne-MAV06.jpg|Orange One Martin Mueller and Christian Lindenberg
Image:MAC-BlackOne-MAV06.jpg|Black One Martin Mueller and Christian Lindenberg
Image:ENAC-Planning-MAV06.jpg|ENAC Team
Image:Slayers-MAV06.jpg|Dragon Slayers Slayers acquiring GPS fix 
Image:Michel_vs_Slayer-MAV06.jpg|Catch! Michel bravely catching the Slayer in an autonomous landing 
Image:BYU-MAV06.jpg|BYU's Winning Design BYU used the Procerus Kestrel autopilot 
</gallery>
|}

=== EMAV2006 ===
; Braunschweig, Niedersachsen, Germany (25-26 July 2006)
* 1st place : Paparazzi ''DragonSlayer/BlackOne/Microjet''
* 2nd place : Paparazzi ''JeanMav360''

{|
|-valign="top"
|
[[Image:emav2006_paparazzies.jpg|thumb|left|EMAV06 Paparazzi Team]]
 
|}

=== MAV05 ===
; Garmisch-Partenkirchen, Bavaria, Germany (17-23 September 2005)
* 1st place : Paparazzi ''Dragonfly''
* 2nd place : Paparazzi ''Glotzer''
* 3rd place : Paparazzi ''Plaster''
* 4th place : Paparazzi ''Plaster duo''

{|
|-valign="top"
|
<gallery caption="MAV05, Germany"
Image:MAV05_paparazzies.jpg|The Paparazzi teams in Garmisch
Image:mav05_dragonfly.jpg|Dragonfly ''University of Arizona''
Image:mav05_depronazzi.jpg|Glotzer ''Martin Mueller and Christian Lindenberg''
Image:mav05_ladybug.jpg|Ladybug ''ENAC''
Image:mav05_enac.jpg|ENAC Team
</gallery>
|}

=== 4eme Journées microdrones ===
; Toulouse, France ( 15 septembre 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
| [[Image:Paparazzi_Equiped_Aircraft.jpg|thumb|left|Microjet]] 
|}

=== EMAV2004 ===
; Braunschweig, Niedersachsen, Germany (13 July 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
|
<gallery caption="EMAV2004">
Image:emav04_01.jpg|The Paparazzi team
Image:emav04_02.jpg|Spectators
Image:emav04_03.jpg|Automatic tracking antenna
</gallery>
|}

=== EMAV2003 ===
; Toulouse, France ( 3 october 2003)
* 1st place : Paparazzi ''Twinstar''

{|-valign="top"
|
<gallery caption="EMAV2003">
Image:emav03_01.jpg|Twinstar ready for flight
Image:emav03_02.jpg|Paparazzi team
</gallery>
|
|}

== Scientific campaigns ==

=== FLOHOF 2007 ===
; Around the Hofsjökull glacier, Iceland, (August 2007)
{|
|-valign="top"
|
<gallery caption="FLOHOF 2007, Iceland">
Image:Kerlingafjoll.jpg|Flying southwest of the glacier
Image:High_alt.png|Climb slope
</gallery>
|}

=== THORPEX/Svalbard 2008 ===
; On and around Svalbard, Arctic Sea, (February 25th - March 15th, 2008)
{|
|-valign="top"
|
<gallery caption="THORPEX 2008, Svalbard">
Image:Kv_svalbard_ice.jpg|KV Svalbard
Image:Hangar.jpg|The KV Svalbard hangar
Image:Funjet_spitsbergen.jpg|Flying over the icy sea near Spitsbergen
Image:Waves.jpg|Waves in rough sea
Image:Breaking_ice.jpg|Breaking the ice
Image:Longyearbyen.jpg|Preparing the aircraft
Image:Landing_spitsbergen.jpg|Landing near Longyearbyen
</gallery>
|}

Gallery

2009-03-14T15:47:19Z

Joekadet: /* User's Gallery */

== User's Gallery ==
=== User's Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.JPG|Joekadet 2 Flights, in process of tuning in auto1
</gallery>
|

|}

== Flight competitions ==
=== [http://www.nal.res.in/MAV08/ MAV08] ===
; Agra, India, (March 10th -- 15th, 2008)
Best Mission Performance:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Paparazzi Slicer (ENAC)
* Paparazzi Glass One(s) (Martin Mueller Engineering)
* Paparazzi Dragonfly (University of Arizona)

Best Hover Performance/Rotorcraft:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Indian Institute of Technology, Bombay (IITB)

Best Autonomous Micro Air Vehicle:
* Paparazzi Slicer (ENAC)

Best Exotic Design Micro Air Vehicle:
* Paparazzi Dragonfly (University of Arizona)

Best UGV Performance:
* [http://cmr.mech.unsw.edu.au/mavstar/ MAVSTAR] (UNSW)

{|
|-valign="top"
|
<gallery caption="MAV08, Agra, India">
Image:Slicer.jpg|Slicer ENAC
Image:Glassone.jpg|Glass One 
Image:MAVSTAR.jpg|MAVSTAR 
</gallery>
|}

=== MAV07 ===
; Toulouse, France, (September 19th - 22nd, 2007)
* 1st place (shared): Paparazzi ''Dragon Slayer''
* 1st place (shared): Micropilot ''Ping Wing''
* 3rd place : Paparazzi ''Tyto'' (Supaero)
* 4th place : Paparazzi ''MAC 07'' (Martin Mueller Engineering)
* 5th place : Paparazzi ''Storm1'' (Murat Bronz)
{|
|-valign="top"
|
<gallery caption="MAV07, Toulouse">
Image:Slayer-105416sm.jpg|Dragon Slayer Miraterre Flight Systems
Image:Twisted_1413sm.jpg|Twisted Logic Miraterre Flight Systems
Image:Storm1.jpg|Storm1 Murat BRONZ
Image:Pingwing.jpg|Ping Wing Sweden
Image:Tyto.jpg|Tyto Supaero
Image:Redone.jpg|Red One/MAC 07 
</gallery>
|}

=== MAV06 ===
; Sandestin, Florida, USA (October 29th - November 2nd, 2006)
* 1st place : Procerus Kestrel (Bringham Young University)
* 2nd place : Paparazzi ''Dualing Slayers'' (ENAC / Miraterre)
* 3rd place : Paparazzi ''Black One'' ("fake" Martin Mueller Engineering)
{|
|-valign="top"
|
<gallery caption="MAV06, Florida">
Image:MAC-OrangeOne-MAV06.jpg|Orange One Martin Mueller and Christian Lindenberg
Image:MAC-BlackOne-MAV06.jpg|Black One Martin Mueller and Christian Lindenberg
Image:ENAC-Planning-MAV06.jpg|ENAC Team
Image:Slayers-MAV06.jpg|Dragon Slayers Slayers acquiring GPS fix 
Image:Michel_vs_Slayer-MAV06.jpg|Catch! Michel bravely catching the Slayer in an autonomous landing 
Image:BYU-MAV06.jpg|BYU's Winning Design BYU used the Procerus Kestrel autopilot 
</gallery>
|}

=== EMAV2006 ===
; Braunschweig, Niedersachsen, Germany (25-26 July 2006)
* 1st place : Paparazzi ''DragonSlayer/BlackOne/Microjet''
* 2nd place : Paparazzi ''JeanMav360''

{|
|-valign="top"
|
[[Image:emav2006_paparazzies.jpg|thumb|left|EMAV06 Paparazzi Team]]
 
|}

=== MAV05 ===
; Garmisch-Partenkirchen, Bavaria, Germany (17-23 September 2005)
* 1st place : Paparazzi ''Dragonfly''
* 2nd place : Paparazzi ''Glotzer''
* 3rd place : Paparazzi ''Plaster''
* 4th place : Paparazzi ''Plaster duo''

{|
|-valign="top"
|
<gallery caption="MAV05, Germany"
Image:MAV05_paparazzies.jpg|The Paparazzi teams in Garmisch
Image:mav05_dragonfly.jpg|Dragonfly ''University of Arizona''
Image:mav05_depronazzi.jpg|Glotzer ''Martin Mueller and Christian Lindenberg''
Image:mav05_ladybug.jpg|Ladybug ''ENAC''
Image:mav05_enac.jpg|ENAC Team
</gallery>
|}

=== 4eme Journées microdrones ===
; Toulouse, France ( 15 septembre 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
| [[Image:Paparazzi_Equiped_Aircraft.jpg|thumb|left|Microjet]] 
|}

=== EMAV2004 ===
; Braunschweig, Niedersachsen, Germany (13 July 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
|
<gallery caption="EMAV2004">
Image:emav04_01.jpg|The Paparazzi team
Image:emav04_02.jpg|Spectators
Image:emav04_03.jpg|Automatic tracking antenna
</gallery>
|}

=== EMAV2003 ===
; Toulouse, France ( 3 october 2003)
* 1st place : Paparazzi ''Twinstar''

{|-valign="top"
|
<gallery caption="EMAV2003">
Image:emav03_01.jpg|Twinstar ready for flight
Image:emav03_02.jpg|Paparazzi team
</gallery>
|
|}

== Scientific campaigns ==

=== FLOHOF 2007 ===
; Around the Hofsjökull glacier, Iceland, (August 2007)
{|
|-valign="top"
|
<gallery caption="FLOHOF 2007, Iceland">
Image:Kerlingafjoll.jpg|Flying southwest of the glacier
Image:High_alt.png|Climb slope
</gallery>
|}

=== THORPEX/Svalbard 2008 ===
; On and around Svalbard, Arctic Sea, (February 25th - March 15th, 2008)
{|
|-valign="top"
|
<gallery caption="THORPEX 2008, Svalbard">
Image:Kv_svalbard_ice.jpg|KV Svalbard
Image:Hangar.jpg|The KV Svalbard hangar
Image:Funjet_spitsbergen.jpg|Flying over the icy sea near Spitsbergen
Image:Waves.jpg|Waves in rough sea
Image:Breaking_ice.jpg|Breaking the ice
Image:Longyearbyen.jpg|Preparing the aircraft
Image:Landing_spitsbergen.jpg|Landing near Longyearbyen
</gallery>
|}

Gallery

2009-03-14T15:42:17Z

Joekadet: /* User's Gallery */

== User's Gallery ==
=== User's Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.jpg|Joekadet 2 Flights, in process of tuning in auto1
</gallery>
|

|}

== Flight competitions ==
=== [http://www.nal.res.in/MAV08/ MAV08] ===
; Agra, India, (March 10th -- 15th, 2008)
Best Mission Performance:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Paparazzi Slicer (ENAC)
* Paparazzi Glass One(s) (Martin Mueller Engineering)
* Paparazzi Dragonfly (University of Arizona)

Best Hover Performance/Rotorcraft:
* [http://www.asctec.de/ Ascending Technologies GmbH] Hornet hexa-rotor (MIT)
* Indian Institute of Technology, Bombay (IITB)

Best Autonomous Micro Air Vehicle:
* Paparazzi Slicer (ENAC)

Best Exotic Design Micro Air Vehicle:
* Paparazzi Dragonfly (University of Arizona)

Best UGV Performance:
* [http://cmr.mech.unsw.edu.au/mavstar/ MAVSTAR] (UNSW)

{|
|-valign="top"
|
<gallery caption="MAV08, Agra, India">
Image:Slicer.jpg|Slicer ENAC
Image:Glassone.jpg|Glass One 
Image:MAVSTAR.jpg|MAVSTAR 
</gallery>
|}

=== MAV07 ===
; Toulouse, France, (September 19th - 22nd, 2007)
* 1st place (shared): Paparazzi ''Dragon Slayer''
* 1st place (shared): Micropilot ''Ping Wing''
* 3rd place : Paparazzi ''Tyto'' (Supaero)
* 4th place : Paparazzi ''MAC 07'' (Martin Mueller Engineering)
* 5th place : Paparazzi ''Storm1'' (Murat Bronz)
{|
|-valign="top"
|
<gallery caption="MAV07, Toulouse">
Image:Slayer-105416sm.jpg|Dragon Slayer Miraterre Flight Systems
Image:Twisted_1413sm.jpg|Twisted Logic Miraterre Flight Systems
Image:Storm1.jpg|Storm1 Murat BRONZ
Image:Pingwing.jpg|Ping Wing Sweden
Image:Tyto.jpg|Tyto Supaero
Image:Redone.jpg|Red One/MAC 07 
</gallery>
|}

=== MAV06 ===
; Sandestin, Florida, USA (October 29th - November 2nd, 2006)
* 1st place : Procerus Kestrel (Bringham Young University)
* 2nd place : Paparazzi ''Dualing Slayers'' (ENAC / Miraterre)
* 3rd place : Paparazzi ''Black One'' ("fake" Martin Mueller Engineering)
{|
|-valign="top"
|
<gallery caption="MAV06, Florida">
Image:MAC-OrangeOne-MAV06.jpg|Orange One Martin Mueller and Christian Lindenberg
Image:MAC-BlackOne-MAV06.jpg|Black One Martin Mueller and Christian Lindenberg
Image:ENAC-Planning-MAV06.jpg|ENAC Team
Image:Slayers-MAV06.jpg|Dragon Slayers Slayers acquiring GPS fix 
Image:Michel_vs_Slayer-MAV06.jpg|Catch! Michel bravely catching the Slayer in an autonomous landing 
Image:BYU-MAV06.jpg|BYU's Winning Design BYU used the Procerus Kestrel autopilot 
</gallery>
|}

=== EMAV2006 ===
; Braunschweig, Niedersachsen, Germany (25-26 July 2006)
* 1st place : Paparazzi ''DragonSlayer/BlackOne/Microjet''
* 2nd place : Paparazzi ''JeanMav360''

{|
|-valign="top"
|
[[Image:emav2006_paparazzies.jpg|thumb|left|EMAV06 Paparazzi Team]]
 
|}

=== MAV05 ===
; Garmisch-Partenkirchen, Bavaria, Germany (17-23 September 2005)
* 1st place : Paparazzi ''Dragonfly''
* 2nd place : Paparazzi ''Glotzer''
* 3rd place : Paparazzi ''Plaster''
* 4th place : Paparazzi ''Plaster duo''

{|
|-valign="top"
|
<gallery caption="MAV05, Germany"
Image:MAV05_paparazzies.jpg|The Paparazzi teams in Garmisch
Image:mav05_dragonfly.jpg|Dragonfly ''University of Arizona''
Image:mav05_depronazzi.jpg|Glotzer ''Martin Mueller and Christian Lindenberg''
Image:mav05_ladybug.jpg|Ladybug ''ENAC''
Image:mav05_enac.jpg|ENAC Team
</gallery>
|}

=== 4eme Journées microdrones ===
; Toulouse, France ( 15 septembre 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
| [[Image:Paparazzi_Equiped_Aircraft.jpg|thumb|left|Microjet]] 
|}

=== EMAV2004 ===
; Braunschweig, Niedersachsen, Germany (13 July 2004)
* 1st place : Paparazzi ''Microjet''

{|
|-valign="top"
|
<gallery caption="EMAV2004">
Image:emav04_01.jpg|The Paparazzi team
Image:emav04_02.jpg|Spectators
Image:emav04_03.jpg|Automatic tracking antenna
</gallery>
|}

=== EMAV2003 ===
; Toulouse, France ( 3 october 2003)
* 1st place : Paparazzi ''Twinstar''

{|-valign="top"
|
<gallery caption="EMAV2003">
Image:emav03_01.jpg|Twinstar ready for flight
Image:emav03_02.jpg|Paparazzi team
</gallery>
|
|}

== Scientific campaigns ==

=== FLOHOF 2007 ===
; Around the Hofsjökull glacier, Iceland, (August 2007)
{|
|-valign="top"
|
<gallery caption="FLOHOF 2007, Iceland">
Image:Kerlingafjoll.jpg|Flying southwest of the glacier
Image:High_alt.png|Climb slope
</gallery>
|}

=== THORPEX/Svalbard 2008 ===
; On and around Svalbard, Arctic Sea, (February 25th - March 15th, 2008)
{|
|-valign="top"
|
<gallery caption="THORPEX 2008, Svalbard">
Image:Kv_svalbard_ice.jpg|KV Svalbard
Image:Hangar.jpg|The KV Svalbard hangar
Image:Funjet_spitsbergen.jpg|Flying over the icy sea near Spitsbergen
Image:Waves.jpg|Waves in rough sea
Image:Breaking_ice.jpg|Breaking the ice
Image:Longyearbyen.jpg|Preparing the aircraft
Image:Landing_spitsbergen.jpg|Landing near Longyearbyen
</gallery>
|}

File:Mentor.JPG

2009-03-14T15:39:26Z

Joekadet: Flying and tuning

Flying and tuning

Users

2009-03-03T00:02:55Z

Joekadet: /* Central America */

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

==Need help adding your information?==
To have your information added by another paparazzi user, please send me an [http://www.rcgroups.com/forums/showpost.php?p=6575288&postcount=1 EMAIL] at with the
following:

*Name
*Email
*Location
*Hardware
*Join date
*Current activities / project status

== Wiki pages ==
add a link to your users wiki page.

[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]

[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]

[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]

[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]

[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]

[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]

[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]

[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]

==Asia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|- style="background:bisque; color:black"
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet
|- style="background:bisque; color:black"
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon
|}

==Europe==
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe

! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz, Austria || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| FelixR || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter
|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.
|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.
|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.
|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.
|- style="background:bisque; color:black"
| [mailto:chebuzz_at_gmail.com David "Buzz" Carlson] || Cyprus || Tiny 2.11, Lynx EDF & GWS SloStick, 9XTend datalink ||| 2008 || Quite a few AUTO2 flights. Plane currently grounded due to a TX run-in with a 1 year-old. Currently working on getting new TX and completing CBP store setup.
|- style="background:bisque; color:black"
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || none || 2008 || Starting
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==North America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Tuning IR sensors, building removable sensor mount. Preparing for flight tests w/ Easystar.
|- style="background:bisque; color:black"
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 ||
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| CSU FC UAV || Fort Collins, Co || Tiny 2.11 + LEA-5H (PPZUAV), 2.4Ghz XBPro ||| Mar 2009 || Maiden flight complete Feb 28. New Airframe in development.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV). Multiplex Mentor ||| 2008 || First flight 22nd of February manual mode trim flight. Second flight 1st of March. Manual is dialed in now need to continue with tuning using GCS.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Airframe Configuration

2009-02-27T05:11:55Z

Joekadet: /* Infrared */

The airframe configuration file is located in <tt>conf/airframes</tt> and contains
all the hardware and software settings for an aircraft. This is an [http://en.wikipedia.org/wiki/Xml XML] document containing some [http://en.wikipedia.org/wiki/Makefile Makefile] code at the bottom. All gains, trims, and behavior settings are defined with standard XML elements. The hardware definitions such as processor type, modem protocol, servo driver, etc. are contained in the makefile raw section.

== Selecting the Airframe File ==
Each airframe file must be assigned a name, unique ID, flight plan, etc. in [[Conf.xml|<tt>conf/conf.xml</tt>]] as follows:
<?xml version="1.0"?>
<conf>
<aircraft
name="Twin1"
ac_id="1"
airframe="airframes/twinstar1.xml"
radio="radios/mc3030.xml"
flight_plan="flight_plans/mav05_cw.xml"
telemetry="telemetry/default.xml"
gui_color="blue"
/>
<aircraft
name="Plaster"
ac_id="2"
airframe="airframes/plaster1.xml"
radio="radios/cockpitMM.xml"
telemetry="telemetry/default.xml"
flight_plan="flight_plans/dummy.xml"
/>
.
.
.
</conf>
Then, to compile and flash the airframe settings and associated flight plan to your autopilot, simply select the appropriate A/C and target in the [[Paparazzi_Center|Paparazzi Center]] or specify your airframe name in the flash command typed from the prompt:
make AIRCRAFT=Twin1 ap.upload
More information can be found on the [[Conf.xml|conf.xml]] page

== XML Parameters ==
=== Commands ===

The <tt>commands</tt> lists the abstract commands you need to control the aircraft. In our example, we have only three:
<tt>
<commands>
<axis name="THROTTLE" failsafe_value="0"/>
<axis name="ROLL" failsafe_value="0"/>
<axis name="PITCH" failsafe_value="0"/>
</commands></tt>
Each command is associated with a failsafe value which will be used if no controller is active (during initialization for example). The range of these values is [-9600:9600]. Note that these commands do not necessarily match the servo actuators. For example, the ROLL command is typically linked to two aileron actuators.

=== Servos ===

The above commands get translated to the <tt>servos</tt> here. In this example we use two ailevons (surfaces used for both pitch and roll as on a flying wing) and a motor. These are listed in the <tt>servos</tt> section:
<tt>
<servos>
<servo name="THROTTLE" no="0" min="1000" neutral="1000" max="2000"/>
<servo name="AILEVON_LEFT" no="1" min="2000" neutral="1500" max="1000"/>
<servo name="AILEVON_RIGHT" no="2" min="1000" neutral="1500" max="2000"/>
</servos></tt>
where names are associated to the corresponding servo channel number on the autopilot and the neutral value, total range and direction are defined. Min/max/neutral values are expressed in milliseconds and the direction of travel can be reversed by exchanging min with max (as in <tt>"AILEVON_LEFT"</tt>, above). The ''standard'' travel for a hobby servo is 1000ms - 2000ms with a 1500ms neutral. Trim can be added by changing this neutral value, and absolute travel limits can be increased or reduced with the min/max values. The <tt>"THROTTLE"</tt> servo typically has the same value for the <tt>neutral</tt> and <tt>min</tt>. Note the following tips:
* Reverse the servo direction by exchanging min/max
* Trim should always be adjusted mechanically if possible to avoid asymetrical travel
* Any reduction of the total travel range should be done mechanically to maintain precision
* Many servos will respond well to values slightly outside the normal 1000-2000ms range but experiment carefully as the servo may not operate reliably outside this range and may even suffer permanent damage.

The <tt>servos</tt> are then linked to the commands in the <tt>command_laws</tt> section:
<tt>
<command_laws>
<let var="aileron" value="@ROLL * 0.3"/>
<let var="elevator" value="@PITCH * 0.7"/>
<set servo="THROTTLE" value="@THROTTLE"/>
<set servo="AILEVON_LEFT" value="$elevator + $aileron"/>
<set servo="AILEVON_RIGHT" value="$elevator - $aileron"/>
</command_laws></tt>
[[Image:airframe_sign_conventions.jpg|thumb|Sign conventions for flight dynamics]]
where the third line is the simplest: the throttle servo value equals throttle command value. The other lines define and control the pitch/roll mixing. Ailevon values are computed with a combination of two commands, '''ROLL''' and '''PITCH'''. This ''mixer'' is defined with two intermediate variables '''aileron''' and '''elevator''' introduced with the <tt>let</tt> element. The '''@''' symbol is used to reference a command value in the <tt>value</tt> attribute of the <tt>set</tt> and <tt>let</tt> elements. In the above example, the servos are limited to +/- 70% of their full travel for pitch and 30% for roll, only in combination can the servos reach 100% deflection. Note that these numbers ''should add up 100% or more, never less''. For example, you may want 100% travel available for pitch - this means if a roll is commanded along with maximum pitch only one servo will respond to the roll command as the other has already reached its mechanical limit. If you find after tuning that these numbers add to less than 100% consider reducing the surface travel mechanically.

Note that the signs used in the description follow the standard convention.

=== Manual ===
The <tt>rc_command</tt> sections links the channels of the RC transmitter (defined in the [[Radio_Control|Radio Control]] file) to the <tt>commands</tt> defined above:

<rc_commands>
<set command="THROTTLE" value="@THROTTLE"/>
<set command="ROLL" value="@ROLL"/>
<set command="PITCH" value="@PITCH"/>
</rc_commands>

This example looks trivial since the channel values have the same name than the commands.

=== Autopilot Only Commands ===
For certain missions it might be required to control servos (payload) from the autopilot (gcs) at all times (even during manual flight). These commands should not be in the <rc_commands> block but in the special <ap_only_commands> block. This allows for instance the pantilt operator to keep working when in manual flight, or safety logic to automatically close cameras below a certain altitude during manual landings.

<ap_only_commands>
<copy command="PAN"/>
<copy command="TILT"/>
<copy command="SHOOT"/>
</ap_only_commands>

=== Auto1 ===
The next section, named <tt>AUTO1</tt>, gives the maximum roll and pitch (in radians) allowed for the augmented stability mode.
<tt>
<section name="AUTO1" prefix="AUTO1_">
<define name="MAX_ROLL" value="RadOfDeg(35)"/>
<define name="MAX_PITCH" value="RadOfDeg(35)"/>
</section>
</tt>
 

=== ADC ===
In the "adc" section, you will find the conformity between arguments and their assigned pins on the autopilot board.
<section name="adc" prefix="ADC_CHANNEL_">
<define name="IR1" value="ADC_1"/>
<define name="IR2" value="ADC_2"/>
<define name="IR_TOP" value="ADC_0"/>
</section>
'''Important note''': To ''activate'' an ADC entry, a flag must be defined in the <tt>makefile</tt> section. For the previous example, we would have to write:

ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2
ap.srcs += $(SRC_ARCH)/adc_hw.c

==== ADC Generic ====

In addition, if you want to receive the value of some ADC channel, you can use the "ADC Generic" service. When activated, the aircraft sends 2 values corresponding to the selected ADC channels. They can be read from the "Messages" application.
ap.CFLAGS += -DUSE_ADC_GENERIC -DUSE_ADC_3 -DADC_CHANNEL_GENERIC1=ADC_3 -DUSE_ADC_4 -DADC_CHANNEL_GENERIC2=ADC_4
ap.srcs += adc_generic.c
In this example, the ADC channels 3 and 4 are read and sent by telemetry at 4Hz:
<message name="ADC_GENERIC" ID="18">
<field name="val1" type="uint16"/>
<field name="val2" type="uint16"/>
</message>
Only two channels can be defined. If only one is activated, 0 will send for the second value.

=== Infrared ===
The <tt>INFRARED</tt> section describes the configuration of the infrared sensors.

The first definitions are relative to the electronic neutral of the sensors (a sensor here is a pair of thermopiles). A perfect sensor should give 512 if it measures the same value on both sides.

<section name="INFRARED" prefix="IR_">
<define name="ADC_IR1_NEUTRAL" value="512"/>
<define name="ADC_IR2_NEUTRAL" value="512"/>
<define name="ADC_TOP_NEUTRAL" value="512"/>

These neutrals are tuned with the "cupboard test": Put the sensor in a close box (a cupboard) and read the values of the IR_SENSORS message (ir1, ir2 and vertical). Set the neutrals (they are subtracted from the measurement) to get null values. E.g. if you read 5 for the ir1 value with ADC_IR1_NEUTRAL equal to 512, change the latter to 517.

The next lines define the installation of the horizontal and vertical sensors. The vertical sensor must give a positive value when the temperature under the aircraft is higher than the temperature above. The two channels of the horizontal sensor must give positive values when it is warmer on the right side and the rear side. To adjust these signs, use the following declarations:

<define name="IR1_SIGN" value="-1"/>
<define name="IR2_SIGN" value="-1"/>
<define name="TOP_SIGN" value="-1"/>

Then, define how the horizontal sensor is connected to the airframe, orientation '''aligned''' or '''tilted'''. In the aligned case, ir'''1''' is along the lateral axis and ir'''2''' along the longitudian one. In the '''tilted''' case, the sensors are tilted by 45 degrees; ir'''1''' is along rear-left -- front-right, and ir'''2''' along rear-right -- front-left. The parameter "value" has no effect! If the airframe construction allows choose an aligned sensor orientation since this gives the best stabilization response results.

For help with orientation of '''Previous Versions of Infrared Sensor Boards''' try here : http://paparazzi.enac.fr/wiki/Previous_Infrared_Sensors

<define name="HORIZ_SENSOR_ALIGNED" value="1"/>
or
<define name="HORIZ_SENSOR_TILTED" value="1"/>

The three axis must give similar values for similar contrasts. The following factors can be used to scale these values. For example with an horizontal tilted sensor, the following ratios are usually needed:

<define name="LATERAL_CORRECTION" value="0.7"/>
<define name="LONGITUDINAL_CORRECTION" value="0.7"/>
<define name="VERTICAL_CORRECTION" value="1."/>
Default values are 1.

It may be hard to align the horizontal sensor with the aircraft. A tuning in flight will be needed to adjust the following neutrals. Adjust the roll neutral to fly straight. Adjust the pitch neutral to fly level with the desired throttle.
<define name="ROLL_NEUTRAL_DEFAULT" value="-2.5" unit="deg"/>
<define name="PITCH_NEUTRAL_DEFAULT" value="6" unit="deg"/>

Finally, an asymmetric (left/right, front/rear) correction can be added with a last set of factors.
<define name="CORRECTION_UP" value="1."/>
<define name="CORRECTION_DOWN" value="1."/>
<define name="CORRECTION_LEFT" value="1."/>
<define name="CORRECTION_RIGHT" value="1."/>
</section>
These corrections are set on the angles.

The old way to define the parameters is still possible, but must not be mixed with the new one describe above.

=== Gyro ===
Defines the type of gyro installed, each axis neutral, and any required temperature compensation. If the gyro has two axes, the pitch neutral is defined as well. Many gyros output their internal temperature and require a temperature-dependent linear correction be made to the neutral value. No correction is done for the temperature in this example.(<tt>ADC_TEMP_SLOPE=0</tt>).

<tt>
<section name="GYRO" prefix="GYRO_"
<define name="ADC_ROLL_COEFF" value="1"/>
<define name="ROLL_NEUTRAL" value="500"/>
<define name="ADC_TEMP_NEUTRAL" value="476"/>
<define name="ADC_TEMP_SLOPE" value="0"/>
</section>
</tt>

=== Bat ===
This section give characteristics for the monitoring of the main power battery. <tt>MILLIAMP_PER_PERCENT</tt> represents the consumption (in mA) for one percent of THROTTLE and for one time unit. It is used to compute the <tt>energy</tt> value of the <tt>BAT</tt> message.

The <tt>CATASTROPHIC_BAT_LEVEL</tt> (was previously <tt>LOW_BATTERY</tt>) value defines the voltage at which the autopilot will lock the throttle at 0% in autonomous mode (kill_throttle mode). This value is also used by the ground server to issue a '''CATASTROPHIC''' alarm message on the bus (this message will be displayed in the console of the GCS). <tt>CRITIC</tt> and <tt>LOW</tt> values will also used as threshold for '''CRITIC''' and '''WARNING''' alarms. They are optional and the respective defaults are 10.0 and 10.5V.

The <tt>MAX_BAT_LEVEL</tt> may be specified to improve the display of the battery gauge in the strip. This definition is optional with a default value of 12.5V.

<tt>
<section name="BAT">
<define name="MILLIAMP_PER_PERCENT" value="0.86"/>
<define name="VOLTAGE_ADC_A" value="0.0177531"/>
<define name="VOLTAGE_ADC_B" value="0.173626"/>
<define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B)"/>
<define name="CATASTROPHIC_BAT_LEVEL" value="6.0" unit="V"/>
<define name="CRITIC_BAT_LEVEL" value="6.5" unit="V"/>
<define name="LOW_BAT_LEVEL" value="7.0" unit="V"/>
<define name="MAX_BAT_LEVEL" value="8.4" unit="V"/>
</section>
</tt>

=== Horizontal Control ===
<tt>
<section name="HORIZONTAL CONTROL" prefix="H_CTL_">
<define name="COURSE_PGAIN" value="-0.4"/>
<define name="ROLL_MAX_SETPOINT" value="0.35" unit="radians"/>
<define name="ROLL_ATTITUDE_GAIN" value="-7500."/>
<define name="ROLL_RATE_GAIN" value="-1500"/>
<define name="PITCH_PGAIN" value="-8000."/>
<define name="ELEVATOR_OF_ROLL" value="1250"/>
</section>
</tt>

The outer loop acts on the route. It will produce a roll command from a course setpoint and a course measurement. The COURSE_PGAIN parameter is the factor multiplied by the course error (in radian) to get a roll setpoint (in radian). So if the plane is expected to go north (course=0) and is actually flying to 57 degrees (course=1 radian, i.e. ENE), with a gain of '''-0.4''', a roll of -0.4 (23 degrees) will be set for the lower control loop.

The ROLL_ATTITUDE_GAIN is used to compute a ROLL command from the roll error (setpoint minus measurement). If a gyro in installed, the ROLL_RATE_GAIN to keep a null roll rate. So these two gains provide a P-D controller.

===Vertical Control===

<section name="VERTICAL CONTROL" prefix="V_CTL_">

<define name="ALTITUDE_PGAIN" value="-0.1" unit="(m/s)/m"/>

<define name="ALTITUDE_MAX_CLIMB" value="3." unit="m/s"/>
These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c. These are outer loop parameters that calculate a desired climb rate based on altitude error. Here, if the altitude error is 10m, the climb setpoint will be set to 1m/s. ALTITUDE_MAX_CLIMB is a bounded value (in m/s) so that the outer loop does not calculate too large of a climb rate
<define name="AUTO_THROTTLE_NOMINAL_CRUISE_THROTTLE" value="0.65" unit="%"/>
<define name="AUTO_THROTTLE_MIN_CRUISE_THROTTLE" value=".4" unit="%"/>
<define name="AUTO_THROTTLE_MAX_CRUISE_THROTTLE" value="1" unit="%"/>
<define name="AUTO_THROTTLE_LOITER_TRIM" value="1000" unit="pprz_t"/>
<define name="AUTO_THROTTLE_DASH_TRIM" value="-2500" unit="pprz_t"/>
<define name="AUTO_THROTTLE_CLIMB_THROTTLE_INCREMENT" value="0.15" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_PGAIN" value="-0.008" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_IGAIN" value="0.25"/>
<define name="AUTO_THROTTLE_PITCH_OF_VZ_PGAIN" value="0.35" unit="rad/(m/s)"/>

These lines are associated with vertical rate control loops contained in ./sw/airborne/fw_v_ctl.c and are used by default in most cases. The default vertical control law is for the vertical rate to be managed by a combination of throttle and pitch.

<define name="AUTO_PITCH_PGAIN" value="-0.1"/>
<define name="AUTO_PITCH_IGAIN" value="0.025"/>
<define name="AUTO_PITCH_MAX_PITCH" value="0.5"/>
<define name="AUTO_PITCH_MIN_PITCH" value="-0.5"/>

These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c but are not used in default. The non-default vertical control law is for the vertical rate to be managed by the pitch.

<define name="THROTTLE_SLEW_LIMITER" value="2" unit="s"/>
THROTTLE_SLEW_LIMITER is the required time is seconds to change throttle from 0% to 100%.

=== Misc ===
<tt>
<section name="MISC">
<define name="NOMINAL_AIRSPEED" value ="12." unit="m/s">
<define name="CARROT" value="5." unit="s"/>
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
<define name="CONTROL_RATE" value"60" unit="Hz"/>
</section>
</tt>

* The "NOMINAL_AIRSPEED" is mainly used in the simulator.
* "CARROT" gives the distance (in seconds, so ground speed is taken into account) between the carrot and the aircraft.
* "KILL_MODE_DISTANCE" is the threshold distance to switch the autopilot into KILL mode (defined descent with no throttle)
* "CONTROL_RATE" is the rate of the low level control loops in Hertz (60 or 20).

== Hardware definitions - Makefile ==

The airframe file must include the description of the controller board and it's low-level settings. This is done in one <tt>makefile</tt> section starting with the autopilot model and flashing mode:
{{Box Code|conf/airframes/myplane.xml|
<makefile>
include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile
<nowiki>FLASH_MODE=IAP</nowiki>
.
.
.
</makefile>
}}
Below this are the definintions and configuration of the peripherals and interfaces.

=== Radio Control ===
The Paparazzi autpilot can interface directly with the PWM signal from any standard hobby R/C receiver. Signal decoding configuration settings for this are stored in the [[Radio_Control|Radio Control]] file.

If you have a Tiny v1.1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4015_MAT_hw.h\" -DSERVOS_4015_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4015_MAT_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you have a Tiny v2 or TWOG v1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you want to output standard PPM to a R/C receiver:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_ppm_hw.h\" -DSERVOS_PPM_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_ppm_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
This is used in the case where you want to directly drive a receiver which has a microcontroller to do the decoding and driving of the servos (not a 4015 or 4017 decoder chip). The PPM is output on the SERV_CLK pin. The PPM frame rate, pulse width, and number of channels can be adjusted in the "servos_ppm_hw.h" file to suit your particular receiver.

If you have a Classix Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.EXTRA_SRCS += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_direct_hw.h\"</nowiki>
<nowiki>ap.EXTRA_SRCS += $(SRC_ARCH)/servos_direct_hw.c</nowiki>
}}

You can set RADIO_CONTROL_TYPE to RC_FUTABA, for falling edge PPM, or RC_JR for rising edge PPM. "RC_FUTABA" is for the Futaba or compatible brands, and "RC_JR" for JR (a.k.a Graupner outside of the USA) or compatible brands.

For the Classix, you must specify which pins to use for PWM by adding "-DPWM_SERVO_0, etc." to the line fbw.CFLAGS. This activate the PWM channel.
<tt>wiring on classix PWM connector
connector LPC shared port
PWM1 PWM5 AD1_6 CAP1_3 P0.21
PWM2 PWM3 RXD0 EINT0 P0.1
PWM3 PWM1 TXD0 P0.0
PWM4 PWM6 RXD1 EINT3 P0.9
PWM5 PWM4 TXD1 AD1_1 P0.8
PWM6 PWM2 SSEL0 EINT2 P0.7</tt>
PWM1 and PWM6 should be safe. PWM4 and PWM5 should be OK if you're not using UART1 on the FBW processor - same for PWM2 and PWM3 if you're not using UART0 (disable FBW telemetry for that ).

=== Modem ===
The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.

Paparazzi supports the following modem protocols:
* Standard transparent serial (pprz) - this is compatible with all modems and can be used to connect the autopilot directly to a PC for testing without a modem.
* Maxstream API protocol (xbee) - compatible with all Maxstream modems including the 9XTend and Zigbee. This protocol enables hardware addressing, allowing multiple aircraft to be managed from a single ground modem.
* Coronis Wavecard - necessary for operation with the unusual Coronis Wavecard modem.
Select the baud/protocol in the airframe file by commenting/uncommenting the appropriate section as follows:
==== Configuring The Serial Protocol ====
New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAV there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="PPRZ"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
The above example tells the autopilot to send and recieve data in standard serial form.

{{Box Code|conf/airframes/myplane.xml - makefile section at the bottom|
# Serial modem
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DPPRZ_UART=Uart0 -DDATALINK=PPRZ -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the serial transport protocol (pprz_transport.c). Use the "#" symbol to comment lines in this section of the airframe file.
 
Note:
* The autopilot and modem serial port baud rates must match at all times and also must match the ground modem rate, check your modem documentation to find the default baud rate and configure a different rate as needed.

 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>

<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

==== Configuring The Maxstream API Protocol ====
The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>
...
</section></nowiki>
}}
The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match eachother at all times.
 
Notes:
* Maxtream modems are factory configured for 9600 baud, in order to change baud rates, first configure the autopilot serial port to match the modem (DUART0_BAUD=B9600), boot the system so that the baud rate change command is sent to the modem (ATBD6) and permanently saved (ATWR), allow 30 seconds for the modem configuration to complete, then reprogram the autopilot with the new baud rate (DUART0_BAUD=B57600) and disabled modem configuration string <tt><define name="NO_XBEE_API_INIT" value="TRUE"/> </tt>.
* The ac_id defined in <tt>conf/conf.xml</tt> is permanently programmed into the modem so this procedure would need to be re-run if the modem is moved to another plane.
* For temporary boot-time API configuration remove any baud rate changes, remove <tt>ATWR\r</tt> from the end of the string.
* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.

 

{{Box Code|confAgain/airframes/myplane.xml - makefile section at the bottom|
<nowiki># Maxstream API protocol</nowiki>
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=XBeeTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DXBEE_UART=Uart0 -DDATALINK=XBEE -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the Maxstream transport protocol (xbee.c). Use the "#" symbol to comment lines in this section of the airframe file.
 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>
<arg flag="-transport" constant="xbee"/>
<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]
=====Alternate Method=====
This is the way it is done in funjet1.xml and has been tested to work by Danstah

{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>

...
</section></nowiki>
}}
Also use this
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>

<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="XBEE"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
And Finally use this in the makefile section
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600
ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c
</nowiki>
}}
By reading all the information above you should be able to infer what the above does.

Now keep in mind that the ground modem baud rate and airplanes modem baud rates do not have to match. The only things that need to match are the the modem on the planes baud rate and the rate defined in the airframe file. For example this planes modem is set to 9600 and this could be used with the ground modem configured above using 57600...
Also for multiple UAV's a good way to configure them is to use 9600 for the ap and use a ground modem configured to 57600 and its not a bad idea to use minimal telemetry.

=== GPS ===
The serial port settings must match that of the GPS and are configured here along with the necessary files to interpret the u-blox UBX binary protocol:

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400</nowiki>
<nowiki>ap.srcs += gps_ubx.c gps.c</nowiki>
}}
'''Note:'''
* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thru the [[Compiling#USB_flashing|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center Configured with|u-center]]

If using the u-blox LEA-5H, add the flag -DGPS_USE_LATLONG in the makefile section of the airframe xml file in the gps section. This flag must be inserted above "ap.srcs += gps_ubx.c gps.c" for proper operation.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400 -DGPS_USE_LATLONG
ap.srcs += gps_ubx.c gps.c</nowiki>
}}

=== Sensors ===

=== Control loops ===

The control loops can be divided in two largely independent groups : the vertical ones and the horizontal ones (files sw/airborne/fw_h_ctl.c and sw/airborne/fw_v_ctl.c ). Those loops can be commanded at different levels by either the R/C transmitter or the autonomous navigation routine.

First the horizontal loop:
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM
ap.srcs += nav.c fw_h_ctl.c fw_v_ctl.c
</nowiki>
}}

Airframe Configuration

2009-02-27T05:05:54Z

Joekadet: /* Infrared */

The airframe configuration file is located in <tt>conf/airframes</tt> and contains
all the hardware and software settings for an aircraft. This is an [http://en.wikipedia.org/wiki/Xml XML] document containing some [http://en.wikipedia.org/wiki/Makefile Makefile] code at the bottom. All gains, trims, and behavior settings are defined with standard XML elements. The hardware definitions such as processor type, modem protocol, servo driver, etc. are contained in the makefile raw section.

== Selecting the Airframe File ==
Each airframe file must be assigned a name, unique ID, flight plan, etc. in [[Conf.xml|<tt>conf/conf.xml</tt>]] as follows:
<?xml version="1.0"?>
<conf>
<aircraft
name="Twin1"
ac_id="1"
airframe="airframes/twinstar1.xml"
radio="radios/mc3030.xml"
flight_plan="flight_plans/mav05_cw.xml"
telemetry="telemetry/default.xml"
gui_color="blue"
/>
<aircraft
name="Plaster"
ac_id="2"
airframe="airframes/plaster1.xml"
radio="radios/cockpitMM.xml"
telemetry="telemetry/default.xml"
flight_plan="flight_plans/dummy.xml"
/>
.
.
.
</conf>
Then, to compile and flash the airframe settings and associated flight plan to your autopilot, simply select the appropriate A/C and target in the [[Paparazzi_Center|Paparazzi Center]] or specify your airframe name in the flash command typed from the prompt:
make AIRCRAFT=Twin1 ap.upload
More information can be found on the [[Conf.xml|conf.xml]] page

== XML Parameters ==
=== Commands ===

The <tt>commands</tt> lists the abstract commands you need to control the aircraft. In our example, we have only three:
<tt>
<commands>
<axis name="THROTTLE" failsafe_value="0"/>
<axis name="ROLL" failsafe_value="0"/>
<axis name="PITCH" failsafe_value="0"/>
</commands></tt>
Each command is associated with a failsafe value which will be used if no controller is active (during initialization for example). The range of these values is [-9600:9600]. Note that these commands do not necessarily match the servo actuators. For example, the ROLL command is typically linked to two aileron actuators.

=== Servos ===

The above commands get translated to the <tt>servos</tt> here. In this example we use two ailevons (surfaces used for both pitch and roll as on a flying wing) and a motor. These are listed in the <tt>servos</tt> section:
<tt>
<servos>
<servo name="THROTTLE" no="0" min="1000" neutral="1000" max="2000"/>
<servo name="AILEVON_LEFT" no="1" min="2000" neutral="1500" max="1000"/>
<servo name="AILEVON_RIGHT" no="2" min="1000" neutral="1500" max="2000"/>
</servos></tt>
where names are associated to the corresponding servo channel number on the autopilot and the neutral value, total range and direction are defined. Min/max/neutral values are expressed in milliseconds and the direction of travel can be reversed by exchanging min with max (as in <tt>"AILEVON_LEFT"</tt>, above). The ''standard'' travel for a hobby servo is 1000ms - 2000ms with a 1500ms neutral. Trim can be added by changing this neutral value, and absolute travel limits can be increased or reduced with the min/max values. The <tt>"THROTTLE"</tt> servo typically has the same value for the <tt>neutral</tt> and <tt>min</tt>. Note the following tips:
* Reverse the servo direction by exchanging min/max
* Trim should always be adjusted mechanically if possible to avoid asymetrical travel
* Any reduction of the total travel range should be done mechanically to maintain precision
* Many servos will respond well to values slightly outside the normal 1000-2000ms range but experiment carefully as the servo may not operate reliably outside this range and may even suffer permanent damage.

The <tt>servos</tt> are then linked to the commands in the <tt>command_laws</tt> section:
<tt>
<command_laws>
<let var="aileron" value="@ROLL * 0.3"/>
<let var="elevator" value="@PITCH * 0.7"/>
<set servo="THROTTLE" value="@THROTTLE"/>
<set servo="AILEVON_LEFT" value="$elevator + $aileron"/>
<set servo="AILEVON_RIGHT" value="$elevator - $aileron"/>
</command_laws></tt>
[[Image:airframe_sign_conventions.jpg|thumb|Sign conventions for flight dynamics]]
where the third line is the simplest: the throttle servo value equals throttle command value. The other lines define and control the pitch/roll mixing. Ailevon values are computed with a combination of two commands, '''ROLL''' and '''PITCH'''. This ''mixer'' is defined with two intermediate variables '''aileron''' and '''elevator''' introduced with the <tt>let</tt> element. The '''@''' symbol is used to reference a command value in the <tt>value</tt> attribute of the <tt>set</tt> and <tt>let</tt> elements. In the above example, the servos are limited to +/- 70% of their full travel for pitch and 30% for roll, only in combination can the servos reach 100% deflection. Note that these numbers ''should add up 100% or more, never less''. For example, you may want 100% travel available for pitch - this means if a roll is commanded along with maximum pitch only one servo will respond to the roll command as the other has already reached its mechanical limit. If you find after tuning that these numbers add to less than 100% consider reducing the surface travel mechanically.

Note that the signs used in the description follow the standard convention.

=== Manual ===
The <tt>rc_command</tt> sections links the channels of the RC transmitter (defined in the [[Radio_Control|Radio Control]] file) to the <tt>commands</tt> defined above:

<rc_commands>
<set command="THROTTLE" value="@THROTTLE"/>
<set command="ROLL" value="@ROLL"/>
<set command="PITCH" value="@PITCH"/>
</rc_commands>

This example looks trivial since the channel values have the same name than the commands.

=== Autopilot Only Commands ===
For certain missions it might be required to control servos (payload) from the autopilot (gcs) at all times (even during manual flight). These commands should not be in the <rc_commands> block but in the special <ap_only_commands> block. This allows for instance the pantilt operator to keep working when in manual flight, or safety logic to automatically close cameras below a certain altitude during manual landings.

<ap_only_commands>
<copy command="PAN"/>
<copy command="TILT"/>
<copy command="SHOOT"/>
</ap_only_commands>

=== Auto1 ===
The next section, named <tt>AUTO1</tt>, gives the maximum roll and pitch (in radians) allowed for the augmented stability mode.
<tt>
<section name="AUTO1" prefix="AUTO1_">
<define name="MAX_ROLL" value="RadOfDeg(35)"/>
<define name="MAX_PITCH" value="RadOfDeg(35)"/>
</section>
</tt>
 

=== ADC ===
In the "adc" section, you will find the conformity between arguments and their assigned pins on the autopilot board.
<section name="adc" prefix="ADC_CHANNEL_">
<define name="IR1" value="ADC_1"/>
<define name="IR2" value="ADC_2"/>
<define name="IR_TOP" value="ADC_0"/>
</section>
'''Important note''': To ''activate'' an ADC entry, a flag must be defined in the <tt>makefile</tt> section. For the previous example, we would have to write:

ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2
ap.srcs += $(SRC_ARCH)/adc_hw.c

==== ADC Generic ====

In addition, if you want to receive the value of some ADC channel, you can use the "ADC Generic" service. When activated, the aircraft sends 2 values corresponding to the selected ADC channels. They can be read from the "Messages" application.
ap.CFLAGS += -DUSE_ADC_GENERIC -DUSE_ADC_3 -DADC_CHANNEL_GENERIC1=ADC_3 -DUSE_ADC_4 -DADC_CHANNEL_GENERIC2=ADC_4
ap.srcs += adc_generic.c
In this example, the ADC channels 3 and 4 are read and sent by telemetry at 4Hz:
<message name="ADC_GENERIC" ID="18">
<field name="val1" type="uint16"/>
<field name="val2" type="uint16"/>
</message>
Only two channels can be defined. If only one is activated, 0 will send for the second value.

=== Infrared ===
The <tt>INFRARED</tt> section describes the configuration of the infrared sensors.

The first definitions are relative to the electronic neutral of the sensors (a sensor here is a pair of thermopiles). A perfect sensor should give 512 if it measures the same value on both sides.

<section name="INFRARED" prefix="IR_">
<define name="ADC_IR1_NEUTRAL" value="512"/>
<define name="ADC_IR2_NEUTRAL" value="512"/>
<define name="ADC_TOP_NEUTRAL" value="512"/>

These neutrals are tuned with the "cupboard test": Put the sensor in a close box (a cupboard) and read the values of the IR_SENSORS message (ir1, ir2 and vertical). Set the neutrals (they are subtracted from the measurement) to get null values. E.g. if you read 5 for the ir1 value with ADC_IR1_NEUTRAL equal to 512, change the latter to 517.

The next lines define the installation of the horizontal and vertical sensors. The vertical sensor must give a positive value when the temperature under the aircraft is higher than the temperature above. The two channels of the horizontal sensor must give positive values when it is warmer on the right side and the rear side. To adjust these signs, use the following declarations:

<define name="IR1_SIGN" value="-1"/>
<define name="IR2_SIGN" value="-1"/>
<define name="TOP_SIGN" value="-1"/>

Then, define how the horizontal sensor is connected to the airframe, orientation '''aligned''' or '''tilted'''. In the aligned case, ir'''1''' is along the lateral axis and ir'''2''' along the longitudian one. In the '''tilted''' case, the sensors are tilted by 45 degrees; ir'''1''' is along rear-left -- front-right, and ir'''2''' along rear-right -- front-left. The parameter "value" has no effect! If the airframe construction allows choose an aligned sensor orientation since this gives the best stabilization response results.
For help with orientation of '''Previous Versions of Infrared Sensor Boards''' try here : http://paparazzi.enac.fr/wiki/Previous_Infrared_Sensors

<define name="HORIZ_SENSOR_ALIGNED" value="1"/>
or
<define name="HORIZ_SENSOR_TILTED" value="1"/>

The three axis must give similar values for similar contrasts. The following factors can be used to scale these values. For example with an horizontal tilted sensor, the following ratios are usually needed:

<define name="LATERAL_CORRECTION" value="0.7"/>
<define name="LONGITUDINAL_CORRECTION" value="0.7"/>
<define name="VERTICAL_CORRECTION" value="1."/>
Default values are 1.

It may be hard to align the horizontal sensor with the aircraft. A tuning in flight will be needed to adjust the following neutrals. Adjust the roll neutral to fly straight. Adjust the pitch neutral to fly level with the desired throttle.
<define name="ROLL_NEUTRAL_DEFAULT" value="-2.5" unit="deg"/>
<define name="PITCH_NEUTRAL_DEFAULT" value="6" unit="deg"/>

Finally, an asymmetric (left/right, front/rear) correction can be added with a last set of factors.
<define name="CORRECTION_UP" value="1."/>
<define name="CORRECTION_DOWN" value="1."/>
<define name="CORRECTION_LEFT" value="1."/>
<define name="CORRECTION_RIGHT" value="1."/>
</section>
These corrections are set on the angles.

The old way to define the parameters is still possible, but must not be mixed with the new one describe above.

=== Gyro ===
Defines the type of gyro installed, each axis neutral, and any required temperature compensation. If the gyro has two axes, the pitch neutral is defined as well. Many gyros output their internal temperature and require a temperature-dependent linear correction be made to the neutral value. No correction is done for the temperature in this example.(<tt>ADC_TEMP_SLOPE=0</tt>).

<tt>
<section name="GYRO" prefix="GYRO_"
<define name="ADC_ROLL_COEFF" value="1"/>
<define name="ROLL_NEUTRAL" value="500"/>
<define name="ADC_TEMP_NEUTRAL" value="476"/>
<define name="ADC_TEMP_SLOPE" value="0"/>
</section>
</tt>

=== Bat ===
This section give characteristics for the monitoring of the main power battery. <tt>MILLIAMP_PER_PERCENT</tt> represents the consumption (in mA) for one percent of THROTTLE and for one time unit. It is used to compute the <tt>energy</tt> value of the <tt>BAT</tt> message.

The <tt>CATASTROPHIC_BAT_LEVEL</tt> (was previously <tt>LOW_BATTERY</tt>) value defines the voltage at which the autopilot will lock the throttle at 0% in autonomous mode (kill_throttle mode). This value is also used by the ground server to issue a '''CATASTROPHIC''' alarm message on the bus (this message will be displayed in the console of the GCS). <tt>CRITIC</tt> and <tt>LOW</tt> values will also used as threshold for '''CRITIC''' and '''WARNING''' alarms. They are optional and the respective defaults are 10.0 and 10.5V.

The <tt>MAX_BAT_LEVEL</tt> may be specified to improve the display of the battery gauge in the strip. This definition is optional with a default value of 12.5V.

<tt>
<section name="BAT">
<define name="MILLIAMP_PER_PERCENT" value="0.86"/>
<define name="VOLTAGE_ADC_A" value="0.0177531"/>
<define name="VOLTAGE_ADC_B" value="0.173626"/>
<define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B)"/>
<define name="CATASTROPHIC_BAT_LEVEL" value="6.0" unit="V"/>
<define name="CRITIC_BAT_LEVEL" value="6.5" unit="V"/>
<define name="LOW_BAT_LEVEL" value="7.0" unit="V"/>
<define name="MAX_BAT_LEVEL" value="8.4" unit="V"/>
</section>
</tt>

=== Horizontal Control ===
<tt>
<section name="HORIZONTAL CONTROL" prefix="H_CTL_">
<define name="COURSE_PGAIN" value="-0.4"/>
<define name="ROLL_MAX_SETPOINT" value="0.35" unit="radians"/>
<define name="ROLL_ATTITUDE_GAIN" value="-7500."/>
<define name="ROLL_RATE_GAIN" value="-1500"/>
<define name="PITCH_PGAIN" value="-8000."/>
<define name="ELEVATOR_OF_ROLL" value="1250"/>
</section>
</tt>

The outer loop acts on the route. It will produce a roll command from a course setpoint and a course measurement. The COURSE_PGAIN parameter is the factor multiplied by the course error (in radian) to get a roll setpoint (in radian). So if the plane is expected to go north (course=0) and is actually flying to 57 degrees (course=1 radian, i.e. ENE), with a gain of '''-0.4''', a roll of -0.4 (23 degrees) will be set for the lower control loop.

The ROLL_ATTITUDE_GAIN is used to compute a ROLL command from the roll error (setpoint minus measurement). If a gyro in installed, the ROLL_RATE_GAIN to keep a null roll rate. So these two gains provide a P-D controller.

===Vertical Control===

<section name="VERTICAL CONTROL" prefix="V_CTL_">

<define name="ALTITUDE_PGAIN" value="-0.1" unit="(m/s)/m"/>

<define name="ALTITUDE_MAX_CLIMB" value="3." unit="m/s"/>
These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c. These are outer loop parameters that calculate a desired climb rate based on altitude error. Here, if the altitude error is 10m, the climb setpoint will be set to 1m/s. ALTITUDE_MAX_CLIMB is a bounded value (in m/s) so that the outer loop does not calculate too large of a climb rate
<define name="AUTO_THROTTLE_NOMINAL_CRUISE_THROTTLE" value="0.65" unit="%"/>
<define name="AUTO_THROTTLE_MIN_CRUISE_THROTTLE" value=".4" unit="%"/>
<define name="AUTO_THROTTLE_MAX_CRUISE_THROTTLE" value="1" unit="%"/>
<define name="AUTO_THROTTLE_LOITER_TRIM" value="1000" unit="pprz_t"/>
<define name="AUTO_THROTTLE_DASH_TRIM" value="-2500" unit="pprz_t"/>
<define name="AUTO_THROTTLE_CLIMB_THROTTLE_INCREMENT" value="0.15" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_PGAIN" value="-0.008" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_IGAIN" value="0.25"/>
<define name="AUTO_THROTTLE_PITCH_OF_VZ_PGAIN" value="0.35" unit="rad/(m/s)"/>

These lines are associated with vertical rate control loops contained in ./sw/airborne/fw_v_ctl.c and are used by default in most cases. The default vertical control law is for the vertical rate to be managed by a combination of throttle and pitch.

<define name="AUTO_PITCH_PGAIN" value="-0.1"/>
<define name="AUTO_PITCH_IGAIN" value="0.025"/>
<define name="AUTO_PITCH_MAX_PITCH" value="0.5"/>
<define name="AUTO_PITCH_MIN_PITCH" value="-0.5"/>

These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c but are not used in default. The non-default vertical control law is for the vertical rate to be managed by the pitch.

<define name="THROTTLE_SLEW_LIMITER" value="2" unit="s"/>
THROTTLE_SLEW_LIMITER is the required time is seconds to change throttle from 0% to 100%.

=== Misc ===
<tt>
<section name="MISC">
<define name="NOMINAL_AIRSPEED" value ="12." unit="m/s">
<define name="CARROT" value="5." unit="s"/>
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
<define name="CONTROL_RATE" value"60" unit="Hz"/>
</section>
</tt>

* The "NOMINAL_AIRSPEED" is mainly used in the simulator.
* "CARROT" gives the distance (in seconds, so ground speed is taken into account) between the carrot and the aircraft.
* "KILL_MODE_DISTANCE" is the threshold distance to switch the autopilot into KILL mode (defined descent with no throttle)
* "CONTROL_RATE" is the rate of the low level control loops in Hertz (60 or 20).

== Hardware definitions - Makefile ==

The airframe file must include the description of the controller board and it's low-level settings. This is done in one <tt>makefile</tt> section starting with the autopilot model and flashing mode:
{{Box Code|conf/airframes/myplane.xml|
<makefile>
include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile
<nowiki>FLASH_MODE=IAP</nowiki>
.
.
.
</makefile>
}}
Below this are the definintions and configuration of the peripherals and interfaces.

=== Radio Control ===
The Paparazzi autpilot can interface directly with the PWM signal from any standard hobby R/C receiver. Signal decoding configuration settings for this are stored in the [[Radio_Control|Radio Control]] file.

If you have a Tiny v1.1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4015_MAT_hw.h\" -DSERVOS_4015_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4015_MAT_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you have a Tiny v2 or TWOG v1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you want to output standard PPM to a R/C receiver:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_ppm_hw.h\" -DSERVOS_PPM_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_ppm_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
This is used in the case where you want to directly drive a receiver which has a microcontroller to do the decoding and driving of the servos (not a 4015 or 4017 decoder chip). The PPM is output on the SERV_CLK pin. The PPM frame rate, pulse width, and number of channels can be adjusted in the "servos_ppm_hw.h" file to suit your particular receiver.

If you have a Classix Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.EXTRA_SRCS += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_direct_hw.h\"</nowiki>
<nowiki>ap.EXTRA_SRCS += $(SRC_ARCH)/servos_direct_hw.c</nowiki>
}}

You can set RADIO_CONTROL_TYPE to RC_FUTABA, for falling edge PPM, or RC_JR for rising edge PPM. "RC_FUTABA" is for the Futaba or compatible brands, and "RC_JR" for JR (a.k.a Graupner outside of the USA) or compatible brands.

For the Classix, you must specify which pins to use for PWM by adding "-DPWM_SERVO_0, etc." to the line fbw.CFLAGS. This activate the PWM channel.
<tt>wiring on classix PWM connector
connector LPC shared port
PWM1 PWM5 AD1_6 CAP1_3 P0.21
PWM2 PWM3 RXD0 EINT0 P0.1
PWM3 PWM1 TXD0 P0.0
PWM4 PWM6 RXD1 EINT3 P0.9
PWM5 PWM4 TXD1 AD1_1 P0.8
PWM6 PWM2 SSEL0 EINT2 P0.7</tt>
PWM1 and PWM6 should be safe. PWM4 and PWM5 should be OK if you're not using UART1 on the FBW processor - same for PWM2 and PWM3 if you're not using UART0 (disable FBW telemetry for that ).

=== Modem ===
The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.

Paparazzi supports the following modem protocols:
* Standard transparent serial (pprz) - this is compatible with all modems and can be used to connect the autopilot directly to a PC for testing without a modem.
* Maxstream API protocol (xbee) - compatible with all Maxstream modems including the 9XTend and Zigbee. This protocol enables hardware addressing, allowing multiple aircraft to be managed from a single ground modem.
* Coronis Wavecard - necessary for operation with the unusual Coronis Wavecard modem.
Select the baud/protocol in the airframe file by commenting/uncommenting the appropriate section as follows:
==== Configuring The Serial Protocol ====
New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAV there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="PPRZ"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
The above example tells the autopilot to send and recieve data in standard serial form.

{{Box Code|conf/airframes/myplane.xml - makefile section at the bottom|
# Serial modem
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DPPRZ_UART=Uart0 -DDATALINK=PPRZ -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the serial transport protocol (pprz_transport.c). Use the "#" symbol to comment lines in this section of the airframe file.
 
Note:
* The autopilot and modem serial port baud rates must match at all times and also must match the ground modem rate, check your modem documentation to find the default baud rate and configure a different rate as needed.

 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>

<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

==== Configuring The Maxstream API Protocol ====
The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>
...
</section></nowiki>
}}
The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match eachother at all times.
 
Notes:
* Maxtream modems are factory configured for 9600 baud, in order to change baud rates, first configure the autopilot serial port to match the modem (DUART0_BAUD=B9600), boot the system so that the baud rate change command is sent to the modem (ATBD6) and permanently saved (ATWR), allow 30 seconds for the modem configuration to complete, then reprogram the autopilot with the new baud rate (DUART0_BAUD=B57600) and disabled modem configuration string <tt><define name="NO_XBEE_API_INIT" value="TRUE"/> </tt>.
* The ac_id defined in <tt>conf/conf.xml</tt> is permanently programmed into the modem so this procedure would need to be re-run if the modem is moved to another plane.
* For temporary boot-time API configuration remove any baud rate changes, remove <tt>ATWR\r</tt> from the end of the string.
* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.

 

{{Box Code|confAgain/airframes/myplane.xml - makefile section at the bottom|
<nowiki># Maxstream API protocol</nowiki>
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=XBeeTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DXBEE_UART=Uart0 -DDATALINK=XBEE -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the Maxstream transport protocol (xbee.c). Use the "#" symbol to comment lines in this section of the airframe file.
 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>
<arg flag="-transport" constant="xbee"/>
<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]
=====Alternate Method=====
This is the way it is done in funjet1.xml and has been tested to work by Danstah

{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>

...
</section></nowiki>
}}
Also use this
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>

<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="XBEE"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
And Finally use this in the makefile section
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600
ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c
</nowiki>
}}
By reading all the information above you should be able to infer what the above does.

Now keep in mind that the ground modem baud rate and airplanes modem baud rates do not have to match. The only things that need to match are the the modem on the planes baud rate and the rate defined in the airframe file. For example this planes modem is set to 9600 and this could be used with the ground modem configured above using 57600...
Also for multiple UAV's a good way to configure them is to use 9600 for the ap and use a ground modem configured to 57600 and its not a bad idea to use minimal telemetry.

=== GPS ===
The serial port settings must match that of the GPS and are configured here along with the necessary files to interpret the u-blox UBX binary protocol:

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400</nowiki>
<nowiki>ap.srcs += gps_ubx.c gps.c</nowiki>
}}
'''Note:'''
* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thru the [[Compiling#USB_flashing|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center Configured with|u-center]]

If using the u-blox LEA-5H, add the flag -DGPS_USE_LATLONG in the makefile section of the airframe xml file in the gps section. This flag must be inserted above "ap.srcs += gps_ubx.c gps.c" for proper operation.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400 -DGPS_USE_LATLONG
ap.srcs += gps_ubx.c gps.c</nowiki>
}}

=== Sensors ===

=== Control loops ===

The control loops can be divided in two largely independent groups : the vertical ones and the horizontal ones (files sw/airborne/fw_h_ctl.c and sw/airborne/fw_v_ctl.c ). Those loops can be commanded at different levels by either the R/C transmitter or the autonomous navigation routine.

First the horizontal loop:
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM
ap.srcs += nav.c fw_h_ctl.c fw_v_ctl.c
</nowiki>
}}

Airframe Configuration

2009-02-27T05:01:23Z

Joekadet: /* Infrared */

The airframe configuration file is located in <tt>conf/airframes</tt> and contains
all the hardware and software settings for an aircraft. This is an [http://en.wikipedia.org/wiki/Xml XML] document containing some [http://en.wikipedia.org/wiki/Makefile Makefile] code at the bottom. All gains, trims, and behavior settings are defined with standard XML elements. The hardware definitions such as processor type, modem protocol, servo driver, etc. are contained in the makefile raw section.

== Selecting the Airframe File ==
Each airframe file must be assigned a name, unique ID, flight plan, etc. in [[Conf.xml|<tt>conf/conf.xml</tt>]] as follows:
<?xml version="1.0"?>
<conf>
<aircraft
name="Twin1"
ac_id="1"
airframe="airframes/twinstar1.xml"
radio="radios/mc3030.xml"
flight_plan="flight_plans/mav05_cw.xml"
telemetry="telemetry/default.xml"
gui_color="blue"
/>
<aircraft
name="Plaster"
ac_id="2"
airframe="airframes/plaster1.xml"
radio="radios/cockpitMM.xml"
telemetry="telemetry/default.xml"
flight_plan="flight_plans/dummy.xml"
/>
.
.
.
</conf>
Then, to compile and flash the airframe settings and associated flight plan to your autopilot, simply select the appropriate A/C and target in the [[Paparazzi_Center|Paparazzi Center]] or specify your airframe name in the flash command typed from the prompt:
make AIRCRAFT=Twin1 ap.upload
More information can be found on the [[Conf.xml|conf.xml]] page

== XML Parameters ==
=== Commands ===

The <tt>commands</tt> lists the abstract commands you need to control the aircraft. In our example, we have only three:
<tt>
<commands>
<axis name="THROTTLE" failsafe_value="0"/>
<axis name="ROLL" failsafe_value="0"/>
<axis name="PITCH" failsafe_value="0"/>
</commands></tt>
Each command is associated with a failsafe value which will be used if no controller is active (during initialization for example). The range of these values is [-9600:9600]. Note that these commands do not necessarily match the servo actuators. For example, the ROLL command is typically linked to two aileron actuators.

=== Servos ===

The above commands get translated to the <tt>servos</tt> here. In this example we use two ailevons (surfaces used for both pitch and roll as on a flying wing) and a motor. These are listed in the <tt>servos</tt> section:
<tt>
<servos>
<servo name="THROTTLE" no="0" min="1000" neutral="1000" max="2000"/>
<servo name="AILEVON_LEFT" no="1" min="2000" neutral="1500" max="1000"/>
<servo name="AILEVON_RIGHT" no="2" min="1000" neutral="1500" max="2000"/>
</servos></tt>
where names are associated to the corresponding servo channel number on the autopilot and the neutral value, total range and direction are defined. Min/max/neutral values are expressed in milliseconds and the direction of travel can be reversed by exchanging min with max (as in <tt>"AILEVON_LEFT"</tt>, above). The ''standard'' travel for a hobby servo is 1000ms - 2000ms with a 1500ms neutral. Trim can be added by changing this neutral value, and absolute travel limits can be increased or reduced with the min/max values. The <tt>"THROTTLE"</tt> servo typically has the same value for the <tt>neutral</tt> and <tt>min</tt>. Note the following tips:
* Reverse the servo direction by exchanging min/max
* Trim should always be adjusted mechanically if possible to avoid asymetrical travel
* Any reduction of the total travel range should be done mechanically to maintain precision
* Many servos will respond well to values slightly outside the normal 1000-2000ms range but experiment carefully as the servo may not operate reliably outside this range and may even suffer permanent damage.

The <tt>servos</tt> are then linked to the commands in the <tt>command_laws</tt> section:
<tt>
<command_laws>
<let var="aileron" value="@ROLL * 0.3"/>
<let var="elevator" value="@PITCH * 0.7"/>
<set servo="THROTTLE" value="@THROTTLE"/>
<set servo="AILEVON_LEFT" value="$elevator + $aileron"/>
<set servo="AILEVON_RIGHT" value="$elevator - $aileron"/>
</command_laws></tt>
[[Image:airframe_sign_conventions.jpg|thumb|Sign conventions for flight dynamics]]
where the third line is the simplest: the throttle servo value equals throttle command value. The other lines define and control the pitch/roll mixing. Ailevon values are computed with a combination of two commands, '''ROLL''' and '''PITCH'''. This ''mixer'' is defined with two intermediate variables '''aileron''' and '''elevator''' introduced with the <tt>let</tt> element. The '''@''' symbol is used to reference a command value in the <tt>value</tt> attribute of the <tt>set</tt> and <tt>let</tt> elements. In the above example, the servos are limited to +/- 70% of their full travel for pitch and 30% for roll, only in combination can the servos reach 100% deflection. Note that these numbers ''should add up 100% or more, never less''. For example, you may want 100% travel available for pitch - this means if a roll is commanded along with maximum pitch only one servo will respond to the roll command as the other has already reached its mechanical limit. If you find after tuning that these numbers add to less than 100% consider reducing the surface travel mechanically.

Note that the signs used in the description follow the standard convention.

=== Manual ===
The <tt>rc_command</tt> sections links the channels of the RC transmitter (defined in the [[Radio_Control|Radio Control]] file) to the <tt>commands</tt> defined above:

<rc_commands>
<set command="THROTTLE" value="@THROTTLE"/>
<set command="ROLL" value="@ROLL"/>
<set command="PITCH" value="@PITCH"/>
</rc_commands>

This example looks trivial since the channel values have the same name than the commands.

=== Autopilot Only Commands ===
For certain missions it might be required to control servos (payload) from the autopilot (gcs) at all times (even during manual flight). These commands should not be in the <rc_commands> block but in the special <ap_only_commands> block. This allows for instance the pantilt operator to keep working when in manual flight, or safety logic to automatically close cameras below a certain altitude during manual landings.

<ap_only_commands>
<copy command="PAN"/>
<copy command="TILT"/>
<copy command="SHOOT"/>
</ap_only_commands>

=== Auto1 ===
The next section, named <tt>AUTO1</tt>, gives the maximum roll and pitch (in radians) allowed for the augmented stability mode.
<tt>
<section name="AUTO1" prefix="AUTO1_">
<define name="MAX_ROLL" value="RadOfDeg(35)"/>
<define name="MAX_PITCH" value="RadOfDeg(35)"/>
</section>
</tt>
 

=== ADC ===
In the "adc" section, you will find the conformity between arguments and their assigned pins on the autopilot board.
<section name="adc" prefix="ADC_CHANNEL_">
<define name="IR1" value="ADC_1"/>
<define name="IR2" value="ADC_2"/>
<define name="IR_TOP" value="ADC_0"/>
</section>
'''Important note''': To ''activate'' an ADC entry, a flag must be defined in the <tt>makefile</tt> section. For the previous example, we would have to write:

ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2
ap.srcs += $(SRC_ARCH)/adc_hw.c

==== ADC Generic ====

In addition, if you want to receive the value of some ADC channel, you can use the "ADC Generic" service. When activated, the aircraft sends 2 values corresponding to the selected ADC channels. They can be read from the "Messages" application.
ap.CFLAGS += -DUSE_ADC_GENERIC -DUSE_ADC_3 -DADC_CHANNEL_GENERIC1=ADC_3 -DUSE_ADC_4 -DADC_CHANNEL_GENERIC2=ADC_4
ap.srcs += adc_generic.c
In this example, the ADC channels 3 and 4 are read and sent by telemetry at 4Hz:
<message name="ADC_GENERIC" ID="18">
<field name="val1" type="uint16"/>
<field name="val2" type="uint16"/>
</message>
Only two channels can be defined. If only one is activated, 0 will send for the second value.

=== Infrared ===
The <tt>INFRARED</tt> section describes the configuration of the infrared sensors.

The first definitions are relative to the electronic neutral of the sensors (a sensor here is a pair of thermopiles). A perfect sensor should give 512 if it measures the same value on both sides.

<section name="INFRARED" prefix="IR_">
<define name="ADC_IR1_NEUTRAL" value="512"/>
<define name="ADC_IR2_NEUTRAL" value="512"/>
<define name="ADC_TOP_NEUTRAL" value="512"/>

These neutrals are tuned with the "cupboard test": Put the sensor in a close box (a cupboard) and read the values of the IR_SENSORS message (ir1, ir2 and vertical). Set the neutrals (they are subtracted from the measurement) to get null values. E.g. if you read 5 for the ir1 value with ADC_IR1_NEUTRAL equal to 512, change the latter to 517.

The next lines define the installation of the horizontal and vertical sensors. The vertical sensor must give a positive value when the temperature under the aircraft is higher than the temperature above. The two channels of the horizontal sensor must give positive values when it is warmer on the right side and the rear side. To adjust these signs, use the following declarations:

<define name="IR1_SIGN" value="-1"/>
<define name="IR2_SIGN" value="-1"/>
<define name="TOP_SIGN" value="-1"/>

Then, define how the horizontal sensor is connected to the airframe, orientation '''aligned''' or '''tilted'''. In the aligned case, ir'''1''' is along the lateral axis and ir'''2''' along the longitudian one. In the '''tilted''' case, the sensors are tilted by 45 degrees; ir'''1''' is along rear-left -- front-right, and ir'''2''' along rear-right -- front-left. The parameter "value" has no effect! If the airframe construction allows choose an aligned sensor orientation since this gives the best stabilization response results.
For help with orientation of "Previous Versions of ... Sensor Boards" try here : http://paparazzi.enac.fr/wiki/Previous_Infrared_Sensors

<define name="HORIZ_SENSOR_ALIGNED" value="1"/>
or
<define name="HORIZ_SENSOR_TILTED" value="1"/>

The three axis must give similar values for similar contrasts. The following factors can be used to scale these values. For example with an horizontal tilted sensor, the following ratios are usually needed:

<define name="LATERAL_CORRECTION" value="0.7"/>
<define name="LONGITUDINAL_CORRECTION" value="0.7"/>
<define name="VERTICAL_CORRECTION" value="1."/>
Default values are 1.

It may be hard to align the horizontal sensor with the aircraft. A tuning in flight will be needed to adjust the following neutrals. Adjust the roll neutral to fly straight. Adjust the pitch neutral to fly level with the desired throttle.
<define name="ROLL_NEUTRAL_DEFAULT" value="-2.5" unit="deg"/>
<define name="PITCH_NEUTRAL_DEFAULT" value="6" unit="deg"/>

Finally, an asymmetric (left/right, front/rear) correction can be added with a last set of factors.
<define name="CORRECTION_UP" value="1."/>
<define name="CORRECTION_DOWN" value="1."/>
<define name="CORRECTION_LEFT" value="1."/>
<define name="CORRECTION_RIGHT" value="1."/>
</section>
These corrections are set on the angles.

The old way to define the parameters is still possible, but must not be mixed with the new one describe above.

=== Gyro ===
Defines the type of gyro installed, each axis neutral, and any required temperature compensation. If the gyro has two axes, the pitch neutral is defined as well. Many gyros output their internal temperature and require a temperature-dependent linear correction be made to the neutral value. No correction is done for the temperature in this example.(<tt>ADC_TEMP_SLOPE=0</tt>).

<tt>
<section name="GYRO" prefix="GYRO_"
<define name="ADC_ROLL_COEFF" value="1"/>
<define name="ROLL_NEUTRAL" value="500"/>
<define name="ADC_TEMP_NEUTRAL" value="476"/>
<define name="ADC_TEMP_SLOPE" value="0"/>
</section>
</tt>

=== Bat ===
This section give characteristics for the monitoring of the main power battery. <tt>MILLIAMP_PER_PERCENT</tt> represents the consumption (in mA) for one percent of THROTTLE and for one time unit. It is used to compute the <tt>energy</tt> value of the <tt>BAT</tt> message.

The <tt>CATASTROPHIC_BAT_LEVEL</tt> (was previously <tt>LOW_BATTERY</tt>) value defines the voltage at which the autopilot will lock the throttle at 0% in autonomous mode (kill_throttle mode). This value is also used by the ground server to issue a '''CATASTROPHIC''' alarm message on the bus (this message will be displayed in the console of the GCS). <tt>CRITIC</tt> and <tt>LOW</tt> values will also used as threshold for '''CRITIC''' and '''WARNING''' alarms. They are optional and the respective defaults are 10.0 and 10.5V.

The <tt>MAX_BAT_LEVEL</tt> may be specified to improve the display of the battery gauge in the strip. This definition is optional with a default value of 12.5V.

<tt>
<section name="BAT">
<define name="MILLIAMP_PER_PERCENT" value="0.86"/>
<define name="VOLTAGE_ADC_A" value="0.0177531"/>
<define name="VOLTAGE_ADC_B" value="0.173626"/>
<define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B)"/>
<define name="CATASTROPHIC_BAT_LEVEL" value="6.0" unit="V"/>
<define name="CRITIC_BAT_LEVEL" value="6.5" unit="V"/>
<define name="LOW_BAT_LEVEL" value="7.0" unit="V"/>
<define name="MAX_BAT_LEVEL" value="8.4" unit="V"/>
</section>
</tt>

=== Horizontal Control ===
<tt>
<section name="HORIZONTAL CONTROL" prefix="H_CTL_">
<define name="COURSE_PGAIN" value="-0.4"/>
<define name="ROLL_MAX_SETPOINT" value="0.35" unit="radians"/>
<define name="ROLL_ATTITUDE_GAIN" value="-7500."/>
<define name="ROLL_RATE_GAIN" value="-1500"/>
<define name="PITCH_PGAIN" value="-8000."/>
<define name="ELEVATOR_OF_ROLL" value="1250"/>
</section>
</tt>

The outer loop acts on the route. It will produce a roll command from a course setpoint and a course measurement. The COURSE_PGAIN parameter is the factor multiplied by the course error (in radian) to get a roll setpoint (in radian). So if the plane is expected to go north (course=0) and is actually flying to 57 degrees (course=1 radian, i.e. ENE), with a gain of '''-0.4''', a roll of -0.4 (23 degrees) will be set for the lower control loop.

The ROLL_ATTITUDE_GAIN is used to compute a ROLL command from the roll error (setpoint minus measurement). If a gyro in installed, the ROLL_RATE_GAIN to keep a null roll rate. So these two gains provide a P-D controller.

===Vertical Control===

<section name="VERTICAL CONTROL" prefix="V_CTL_">

<define name="ALTITUDE_PGAIN" value="-0.1" unit="(m/s)/m"/>

<define name="ALTITUDE_MAX_CLIMB" value="3." unit="m/s"/>
These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c. These are outer loop parameters that calculate a desired climb rate based on altitude error. Here, if the altitude error is 10m, the climb setpoint will be set to 1m/s. ALTITUDE_MAX_CLIMB is a bounded value (in m/s) so that the outer loop does not calculate too large of a climb rate
<define name="AUTO_THROTTLE_NOMINAL_CRUISE_THROTTLE" value="0.65" unit="%"/>
<define name="AUTO_THROTTLE_MIN_CRUISE_THROTTLE" value=".4" unit="%"/>
<define name="AUTO_THROTTLE_MAX_CRUISE_THROTTLE" value="1" unit="%"/>
<define name="AUTO_THROTTLE_LOITER_TRIM" value="1000" unit="pprz_t"/>
<define name="AUTO_THROTTLE_DASH_TRIM" value="-2500" unit="pprz_t"/>
<define name="AUTO_THROTTLE_CLIMB_THROTTLE_INCREMENT" value="0.15" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_PGAIN" value="-0.008" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_IGAIN" value="0.25"/>
<define name="AUTO_THROTTLE_PITCH_OF_VZ_PGAIN" value="0.35" unit="rad/(m/s)"/>

These lines are associated with vertical rate control loops contained in ./sw/airborne/fw_v_ctl.c and are used by default in most cases. The default vertical control law is for the vertical rate to be managed by a combination of throttle and pitch.

<define name="AUTO_PITCH_PGAIN" value="-0.1"/>
<define name="AUTO_PITCH_IGAIN" value="0.025"/>
<define name="AUTO_PITCH_MAX_PITCH" value="0.5"/>
<define name="AUTO_PITCH_MIN_PITCH" value="-0.5"/>

These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c but are not used in default. The non-default vertical control law is for the vertical rate to be managed by the pitch.

<define name="THROTTLE_SLEW_LIMITER" value="2" unit="s"/>
THROTTLE_SLEW_LIMITER is the required time is seconds to change throttle from 0% to 100%.

=== Misc ===
<tt>
<section name="MISC">
<define name="NOMINAL_AIRSPEED" value ="12." unit="m/s">
<define name="CARROT" value="5." unit="s"/>
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
<define name="CONTROL_RATE" value"60" unit="Hz"/>
</section>
</tt>

* The "NOMINAL_AIRSPEED" is mainly used in the simulator.
* "CARROT" gives the distance (in seconds, so ground speed is taken into account) between the carrot and the aircraft.
* "KILL_MODE_DISTANCE" is the threshold distance to switch the autopilot into KILL mode (defined descent with no throttle)
* "CONTROL_RATE" is the rate of the low level control loops in Hertz (60 or 20).

== Hardware definitions - Makefile ==

The airframe file must include the description of the controller board and it's low-level settings. This is done in one <tt>makefile</tt> section starting with the autopilot model and flashing mode:
{{Box Code|conf/airframes/myplane.xml|
<makefile>
include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile
<nowiki>FLASH_MODE=IAP</nowiki>
.
.
.
</makefile>
}}
Below this are the definintions and configuration of the peripherals and interfaces.

=== Radio Control ===
The Paparazzi autpilot can interface directly with the PWM signal from any standard hobby R/C receiver. Signal decoding configuration settings for this are stored in the [[Radio_Control|Radio Control]] file.

If you have a Tiny v1.1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4015_MAT_hw.h\" -DSERVOS_4015_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4015_MAT_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you have a Tiny v2 or TWOG v1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you want to output standard PPM to a R/C receiver:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_ppm_hw.h\" -DSERVOS_PPM_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_ppm_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
This is used in the case where you want to directly drive a receiver which has a microcontroller to do the decoding and driving of the servos (not a 4015 or 4017 decoder chip). The PPM is output on the SERV_CLK pin. The PPM frame rate, pulse width, and number of channels can be adjusted in the "servos_ppm_hw.h" file to suit your particular receiver.

If you have a Classix Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.EXTRA_SRCS += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_direct_hw.h\"</nowiki>
<nowiki>ap.EXTRA_SRCS += $(SRC_ARCH)/servos_direct_hw.c</nowiki>
}}

You can set RADIO_CONTROL_TYPE to RC_FUTABA, for falling edge PPM, or RC_JR for rising edge PPM. "RC_FUTABA" is for the Futaba or compatible brands, and "RC_JR" for JR (a.k.a Graupner outside of the USA) or compatible brands.

For the Classix, you must specify which pins to use for PWM by adding "-DPWM_SERVO_0, etc." to the line fbw.CFLAGS. This activate the PWM channel.
<tt>wiring on classix PWM connector
connector LPC shared port
PWM1 PWM5 AD1_6 CAP1_3 P0.21
PWM2 PWM3 RXD0 EINT0 P0.1
PWM3 PWM1 TXD0 P0.0
PWM4 PWM6 RXD1 EINT3 P0.9
PWM5 PWM4 TXD1 AD1_1 P0.8
PWM6 PWM2 SSEL0 EINT2 P0.7</tt>
PWM1 and PWM6 should be safe. PWM4 and PWM5 should be OK if you're not using UART1 on the FBW processor - same for PWM2 and PWM3 if you're not using UART0 (disable FBW telemetry for that ).

=== Modem ===
The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.

Paparazzi supports the following modem protocols:
* Standard transparent serial (pprz) - this is compatible with all modems and can be used to connect the autopilot directly to a PC for testing without a modem.
* Maxstream API protocol (xbee) - compatible with all Maxstream modems including the 9XTend and Zigbee. This protocol enables hardware addressing, allowing multiple aircraft to be managed from a single ground modem.
* Coronis Wavecard - necessary for operation with the unusual Coronis Wavecard modem.
Select the baud/protocol in the airframe file by commenting/uncommenting the appropriate section as follows:
==== Configuring The Serial Protocol ====
New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAV there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="PPRZ"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
The above example tells the autopilot to send and recieve data in standard serial form.

{{Box Code|conf/airframes/myplane.xml - makefile section at the bottom|
# Serial modem
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DPPRZ_UART=Uart0 -DDATALINK=PPRZ -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the serial transport protocol (pprz_transport.c). Use the "#" symbol to comment lines in this section of the airframe file.
 
Note:
* The autopilot and modem serial port baud rates must match at all times and also must match the ground modem rate, check your modem documentation to find the default baud rate and configure a different rate as needed.

 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>

<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

==== Configuring The Maxstream API Protocol ====
The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>
...
</section></nowiki>
}}
The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match eachother at all times.
 
Notes:
* Maxtream modems are factory configured for 9600 baud, in order to change baud rates, first configure the autopilot serial port to match the modem (DUART0_BAUD=B9600), boot the system so that the baud rate change command is sent to the modem (ATBD6) and permanently saved (ATWR), allow 30 seconds for the modem configuration to complete, then reprogram the autopilot with the new baud rate (DUART0_BAUD=B57600) and disabled modem configuration string <tt><define name="NO_XBEE_API_INIT" value="TRUE"/> </tt>.
* The ac_id defined in <tt>conf/conf.xml</tt> is permanently programmed into the modem so this procedure would need to be re-run if the modem is moved to another plane.
* For temporary boot-time API configuration remove any baud rate changes, remove <tt>ATWR\r</tt> from the end of the string.
* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.

 

{{Box Code|confAgain/airframes/myplane.xml - makefile section at the bottom|
<nowiki># Maxstream API protocol</nowiki>
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=XBeeTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DXBEE_UART=Uart0 -DDATALINK=XBEE -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the Maxstream transport protocol (xbee.c). Use the "#" symbol to comment lines in this section of the airframe file.
 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>
<arg flag="-transport" constant="xbee"/>
<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]
=====Alternate Method=====
This is the way it is done in funjet1.xml and has been tested to work by Danstah

{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>

...
</section></nowiki>
}}
Also use this
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>

<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="XBEE"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
And Finally use this in the makefile section
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600
ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c
</nowiki>
}}
By reading all the information above you should be able to infer what the above does.

Now keep in mind that the ground modem baud rate and airplanes modem baud rates do not have to match. The only things that need to match are the the modem on the planes baud rate and the rate defined in the airframe file. For example this planes modem is set to 9600 and this could be used with the ground modem configured above using 57600...
Also for multiple UAV's a good way to configure them is to use 9600 for the ap and use a ground modem configured to 57600 and its not a bad idea to use minimal telemetry.

=== GPS ===
The serial port settings must match that of the GPS and are configured here along with the necessary files to interpret the u-blox UBX binary protocol:

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400</nowiki>
<nowiki>ap.srcs += gps_ubx.c gps.c</nowiki>
}}
'''Note:'''
* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thru the [[Compiling#USB_flashing|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center Configured with|u-center]]

If using the u-blox LEA-5H, add the flag -DGPS_USE_LATLONG in the makefile section of the airframe xml file in the gps section. This flag must be inserted above "ap.srcs += gps_ubx.c gps.c" for proper operation.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400 -DGPS_USE_LATLONG
ap.srcs += gps_ubx.c gps.c</nowiki>
}}

=== Sensors ===

=== Control loops ===

The control loops can be divided in two largely independent groups : the vertical ones and the horizontal ones (files sw/airborne/fw_h_ctl.c and sw/airborne/fw_v_ctl.c ). Those loops can be commanded at different levels by either the R/C transmitter or the autonomous navigation routine.

First the horizontal loop:
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM
ap.srcs += nav.c fw_h_ctl.c fw_v_ctl.c
</nowiki>
}}

Airframe Configuration

2009-02-27T04:51:51Z

Joekadet: /* Infrared */

The airframe configuration file is located in <tt>conf/airframes</tt> and contains
all the hardware and software settings for an aircraft. This is an [http://en.wikipedia.org/wiki/Xml XML] document containing some [http://en.wikipedia.org/wiki/Makefile Makefile] code at the bottom. All gains, trims, and behavior settings are defined with standard XML elements. The hardware definitions such as processor type, modem protocol, servo driver, etc. are contained in the makefile raw section.

== Selecting the Airframe File ==
Each airframe file must be assigned a name, unique ID, flight plan, etc. in [[Conf.xml|<tt>conf/conf.xml</tt>]] as follows:
<?xml version="1.0"?>
<conf>
<aircraft
name="Twin1"
ac_id="1"
airframe="airframes/twinstar1.xml"
radio="radios/mc3030.xml"
flight_plan="flight_plans/mav05_cw.xml"
telemetry="telemetry/default.xml"
gui_color="blue"
/>
<aircraft
name="Plaster"
ac_id="2"
airframe="airframes/plaster1.xml"
radio="radios/cockpitMM.xml"
telemetry="telemetry/default.xml"
flight_plan="flight_plans/dummy.xml"
/>
.
.
.
</conf>
Then, to compile and flash the airframe settings and associated flight plan to your autopilot, simply select the appropriate A/C and target in the [[Paparazzi_Center|Paparazzi Center]] or specify your airframe name in the flash command typed from the prompt:
make AIRCRAFT=Twin1 ap.upload
More information can be found on the [[Conf.xml|conf.xml]] page

== XML Parameters ==
=== Commands ===

The <tt>commands</tt> lists the abstract commands you need to control the aircraft. In our example, we have only three:
<tt>
<commands>
<axis name="THROTTLE" failsafe_value="0"/>
<axis name="ROLL" failsafe_value="0"/>
<axis name="PITCH" failsafe_value="0"/>
</commands></tt>
Each command is associated with a failsafe value which will be used if no controller is active (during initialization for example). The range of these values is [-9600:9600]. Note that these commands do not necessarily match the servo actuators. For example, the ROLL command is typically linked to two aileron actuators.

=== Servos ===

The above commands get translated to the <tt>servos</tt> here. In this example we use two ailevons (surfaces used for both pitch and roll as on a flying wing) and a motor. These are listed in the <tt>servos</tt> section:
<tt>
<servos>
<servo name="THROTTLE" no="0" min="1000" neutral="1000" max="2000"/>
<servo name="AILEVON_LEFT" no="1" min="2000" neutral="1500" max="1000"/>
<servo name="AILEVON_RIGHT" no="2" min="1000" neutral="1500" max="2000"/>
</servos></tt>
where names are associated to the corresponding servo channel number on the autopilot and the neutral value, total range and direction are defined. Min/max/neutral values are expressed in milliseconds and the direction of travel can be reversed by exchanging min with max (as in <tt>"AILEVON_LEFT"</tt>, above). The ''standard'' travel for a hobby servo is 1000ms - 2000ms with a 1500ms neutral. Trim can be added by changing this neutral value, and absolute travel limits can be increased or reduced with the min/max values. The <tt>"THROTTLE"</tt> servo typically has the same value for the <tt>neutral</tt> and <tt>min</tt>. Note the following tips:
* Reverse the servo direction by exchanging min/max
* Trim should always be adjusted mechanically if possible to avoid asymetrical travel
* Any reduction of the total travel range should be done mechanically to maintain precision
* Many servos will respond well to values slightly outside the normal 1000-2000ms range but experiment carefully as the servo may not operate reliably outside this range and may even suffer permanent damage.

The <tt>servos</tt> are then linked to the commands in the <tt>command_laws</tt> section:
<tt>
<command_laws>
<let var="aileron" value="@ROLL * 0.3"/>
<let var="elevator" value="@PITCH * 0.7"/>
<set servo="THROTTLE" value="@THROTTLE"/>
<set servo="AILEVON_LEFT" value="$elevator + $aileron"/>
<set servo="AILEVON_RIGHT" value="$elevator - $aileron"/>
</command_laws></tt>
[[Image:airframe_sign_conventions.jpg|thumb|Sign conventions for flight dynamics]]
where the third line is the simplest: the throttle servo value equals throttle command value. The other lines define and control the pitch/roll mixing. Ailevon values are computed with a combination of two commands, '''ROLL''' and '''PITCH'''. This ''mixer'' is defined with two intermediate variables '''aileron''' and '''elevator''' introduced with the <tt>let</tt> element. The '''@''' symbol is used to reference a command value in the <tt>value</tt> attribute of the <tt>set</tt> and <tt>let</tt> elements. In the above example, the servos are limited to +/- 70% of their full travel for pitch and 30% for roll, only in combination can the servos reach 100% deflection. Note that these numbers ''should add up 100% or more, never less''. For example, you may want 100% travel available for pitch - this means if a roll is commanded along with maximum pitch only one servo will respond to the roll command as the other has already reached its mechanical limit. If you find after tuning that these numbers add to less than 100% consider reducing the surface travel mechanically.

Note that the signs used in the description follow the standard convention.

=== Manual ===
The <tt>rc_command</tt> sections links the channels of the RC transmitter (defined in the [[Radio_Control|Radio Control]] file) to the <tt>commands</tt> defined above:

<rc_commands>
<set command="THROTTLE" value="@THROTTLE"/>
<set command="ROLL" value="@ROLL"/>
<set command="PITCH" value="@PITCH"/>
</rc_commands>

This example looks trivial since the channel values have the same name than the commands.

=== Autopilot Only Commands ===
For certain missions it might be required to control servos (payload) from the autopilot (gcs) at all times (even during manual flight). These commands should not be in the <rc_commands> block but in the special <ap_only_commands> block. This allows for instance the pantilt operator to keep working when in manual flight, or safety logic to automatically close cameras below a certain altitude during manual landings.

<ap_only_commands>
<copy command="PAN"/>
<copy command="TILT"/>
<copy command="SHOOT"/>
</ap_only_commands>

=== Auto1 ===
The next section, named <tt>AUTO1</tt>, gives the maximum roll and pitch (in radians) allowed for the augmented stability mode.
<tt>
<section name="AUTO1" prefix="AUTO1_">
<define name="MAX_ROLL" value="RadOfDeg(35)"/>
<define name="MAX_PITCH" value="RadOfDeg(35)"/>
</section>
</tt>
 

=== ADC ===
In the "adc" section, you will find the conformity between arguments and their assigned pins on the autopilot board.
<section name="adc" prefix="ADC_CHANNEL_">
<define name="IR1" value="ADC_1"/>
<define name="IR2" value="ADC_2"/>
<define name="IR_TOP" value="ADC_0"/>
</section>
'''Important note''': To ''activate'' an ADC entry, a flag must be defined in the <tt>makefile</tt> section. For the previous example, we would have to write:

ap.CFLAGS += -DADC -DUSE_ADC_0 -DUSE_ADC_1 -DUSE_ADC_2
ap.srcs += $(SRC_ARCH)/adc_hw.c

==== ADC Generic ====

In addition, if you want to receive the value of some ADC channel, you can use the "ADC Generic" service. When activated, the aircraft sends 2 values corresponding to the selected ADC channels. They can be read from the "Messages" application.
ap.CFLAGS += -DUSE_ADC_GENERIC -DUSE_ADC_3 -DADC_CHANNEL_GENERIC1=ADC_3 -DUSE_ADC_4 -DADC_CHANNEL_GENERIC2=ADC_4
ap.srcs += adc_generic.c
In this example, the ADC channels 3 and 4 are read and sent by telemetry at 4Hz:
<message name="ADC_GENERIC" ID="18">
<field name="val1" type="uint16"/>
<field name="val2" type="uint16"/>
</message>
Only two channels can be defined. If only one is activated, 0 will send for the second value.

=== Infrared ===
The <tt>INFRARED</tt> section describes the configuration of the infrared sensors.

The first definitions are relative to the electronic neutral of the sensors (a sensor here is a pair of thermopiles). A perfect sensor should give 512 if it measures the same value on both sides.

<section name="INFRARED" prefix="IR_">
<define name="ADC_IR1_NEUTRAL" value="512"/>
<define name="ADC_IR2_NEUTRAL" value="512"/>
<define name="ADC_TOP_NEUTRAL" value="512"/>

These neutrals are tuned with the "cupboard test": Put the sensor in a close box (a cupboard) and read the values of the IR_SENSORS message (ir1, ir2 and vertical). Set the neutrals (they are subtracted from the measurement) to get null values. E.g. if you read 5 for the ir1 value with ADC_IR1_NEUTRAL equal to 512, change the latter to 517.

The next lines define the installation of the horizontal and vertical sensors. The vertical sensor must give a positive value when the temperature under the aircraft is higher than the temperature above. The two channels of the horizontal sensor must give positive values when it is warmer on the right side and the rear side. To adjust these signs, use the following declarations:

<define name="IR1_SIGN" value="-1"/>
<define name="IR2_SIGN" value="-1"/>
<define name="TOP_SIGN" value="-1"/>

Then, define how the horizontal sensor is connected to the airframe, orientation '''aligned''' or '''tilted'''. In the aligned case, ir'''1''' is along the lateral axis and ir'''2''' along the longitudian one. In the '''tilted''' case, the sensors are tilted by 45 degrees; ir'''1''' is along rear-left -- front-right, and ir'''2''' along rear-right -- front-left. The parameter "value" has no effect! If the airframe construction allows choose an aligned sensor orientation since this gives the best stabilization response results.
For help with Previous Sensor orientation try here : http://paparazzi.enac.fr/wiki/Previous_Infrared_Sensors

<define name="HORIZ_SENSOR_ALIGNED" value="1"/>
or
<define name="HORIZ_SENSOR_TILTED" value="1"/>

The three axis must give similar values for similar contrasts. The following factors can be used to scale these values. For example with an horizontal tilted sensor, the following ratios are usually needed:

<define name="LATERAL_CORRECTION" value="0.7"/>
<define name="LONGITUDINAL_CORRECTION" value="0.7"/>
<define name="VERTICAL_CORRECTION" value="1."/>
Default values are 1.

It may be hard to align the horizontal sensor with the aircraft. A tuning in flight will be needed to adjust the following neutrals. Adjust the roll neutral to fly straight. Adjust the pitch neutral to fly level with the desired throttle.
<define name="ROLL_NEUTRAL_DEFAULT" value="-2.5" unit="deg"/>
<define name="PITCH_NEUTRAL_DEFAULT" value="6" unit="deg"/>

Finally, an asymmetric (left/right, front/rear) correction can be added with a last set of factors.
<define name="CORRECTION_UP" value="1."/>
<define name="CORRECTION_DOWN" value="1."/>
<define name="CORRECTION_LEFT" value="1."/>
<define name="CORRECTION_RIGHT" value="1."/>
</section>
These corrections are set on the angles.

The old way to define the parameters is still possible, but must not be mixed with the new one describe above.

=== Gyro ===
Defines the type of gyro installed, each axis neutral, and any required temperature compensation. If the gyro has two axes, the pitch neutral is defined as well. Many gyros output their internal temperature and require a temperature-dependent linear correction be made to the neutral value. No correction is done for the temperature in this example.(<tt>ADC_TEMP_SLOPE=0</tt>).

<tt>
<section name="GYRO" prefix="GYRO_"
<define name="ADC_ROLL_COEFF" value="1"/>
<define name="ROLL_NEUTRAL" value="500"/>
<define name="ADC_TEMP_NEUTRAL" value="476"/>
<define name="ADC_TEMP_SLOPE" value="0"/>
</section>
</tt>

=== Bat ===
This section give characteristics for the monitoring of the main power battery. <tt>MILLIAMP_PER_PERCENT</tt> represents the consumption (in mA) for one percent of THROTTLE and for one time unit. It is used to compute the <tt>energy</tt> value of the <tt>BAT</tt> message.

The <tt>CATASTROPHIC_BAT_LEVEL</tt> (was previously <tt>LOW_BATTERY</tt>) value defines the voltage at which the autopilot will lock the throttle at 0% in autonomous mode (kill_throttle mode). This value is also used by the ground server to issue a '''CATASTROPHIC''' alarm message on the bus (this message will be displayed in the console of the GCS). <tt>CRITIC</tt> and <tt>LOW</tt> values will also used as threshold for '''CRITIC''' and '''WARNING''' alarms. They are optional and the respective defaults are 10.0 and 10.5V.

The <tt>MAX_BAT_LEVEL</tt> may be specified to improve the display of the battery gauge in the strip. This definition is optional with a default value of 12.5V.

<tt>
<section name="BAT">
<define name="MILLIAMP_PER_PERCENT" value="0.86"/>
<define name="VOLTAGE_ADC_A" value="0.0177531"/>
<define name="VOLTAGE_ADC_B" value="0.173626"/>
<define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B)"/>
<define name="CATASTROPHIC_BAT_LEVEL" value="6.0" unit="V"/>
<define name="CRITIC_BAT_LEVEL" value="6.5" unit="V"/>
<define name="LOW_BAT_LEVEL" value="7.0" unit="V"/>
<define name="MAX_BAT_LEVEL" value="8.4" unit="V"/>
</section>
</tt>

=== Horizontal Control ===
<tt>
<section name="HORIZONTAL CONTROL" prefix="H_CTL_">
<define name="COURSE_PGAIN" value="-0.4"/>
<define name="ROLL_MAX_SETPOINT" value="0.35" unit="radians"/>
<define name="ROLL_ATTITUDE_GAIN" value="-7500."/>
<define name="ROLL_RATE_GAIN" value="-1500"/>
<define name="PITCH_PGAIN" value="-8000."/>
<define name="ELEVATOR_OF_ROLL" value="1250"/>
</section>
</tt>

The outer loop acts on the route. It will produce a roll command from a course setpoint and a course measurement. The COURSE_PGAIN parameter is the factor multiplied by the course error (in radian) to get a roll setpoint (in radian). So if the plane is expected to go north (course=0) and is actually flying to 57 degrees (course=1 radian, i.e. ENE), with a gain of '''-0.4''', a roll of -0.4 (23 degrees) will be set for the lower control loop.

The ROLL_ATTITUDE_GAIN is used to compute a ROLL command from the roll error (setpoint minus measurement). If a gyro in installed, the ROLL_RATE_GAIN to keep a null roll rate. So these two gains provide a P-D controller.

===Vertical Control===

<section name="VERTICAL CONTROL" prefix="V_CTL_">

<define name="ALTITUDE_PGAIN" value="-0.1" unit="(m/s)/m"/>

<define name="ALTITUDE_MAX_CLIMB" value="3." unit="m/s"/>
These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c. These are outer loop parameters that calculate a desired climb rate based on altitude error. Here, if the altitude error is 10m, the climb setpoint will be set to 1m/s. ALTITUDE_MAX_CLIMB is a bounded value (in m/s) so that the outer loop does not calculate too large of a climb rate
<define name="AUTO_THROTTLE_NOMINAL_CRUISE_THROTTLE" value="0.65" unit="%"/>
<define name="AUTO_THROTTLE_MIN_CRUISE_THROTTLE" value=".4" unit="%"/>
<define name="AUTO_THROTTLE_MAX_CRUISE_THROTTLE" value="1" unit="%"/>
<define name="AUTO_THROTTLE_LOITER_TRIM" value="1000" unit="pprz_t"/>
<define name="AUTO_THROTTLE_DASH_TRIM" value="-2500" unit="pprz_t"/>
<define name="AUTO_THROTTLE_CLIMB_THROTTLE_INCREMENT" value="0.15" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_PGAIN" value="-0.008" unit="%/(m/s)"/>
<define name="AUTO_THROTTLE_IGAIN" value="0.25"/>
<define name="AUTO_THROTTLE_PITCH_OF_VZ_PGAIN" value="0.35" unit="rad/(m/s)"/>

These lines are associated with vertical rate control loops contained in ./sw/airborne/fw_v_ctl.c and are used by default in most cases. The default vertical control law is for the vertical rate to be managed by a combination of throttle and pitch.

<define name="AUTO_PITCH_PGAIN" value="-0.1"/>
<define name="AUTO_PITCH_IGAIN" value="0.025"/>
<define name="AUTO_PITCH_MAX_PITCH" value="0.5"/>
<define name="AUTO_PITCH_MIN_PITCH" value="-0.5"/>

These lines are associated with vertical control loops contained in ./sw/airborne/fw_v_ctl.c but are not used in default. The non-default vertical control law is for the vertical rate to be managed by the pitch.

<define name="THROTTLE_SLEW_LIMITER" value="2" unit="s"/>
THROTTLE_SLEW_LIMITER is the required time is seconds to change throttle from 0% to 100%.

=== Misc ===
<tt>
<section name="MISC">
<define name="NOMINAL_AIRSPEED" value ="12." unit="m/s">
<define name="CARROT" value="5." unit="s"/>
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
<define name="CONTROL_RATE" value"60" unit="Hz"/>
</section>
</tt>

* The "NOMINAL_AIRSPEED" is mainly used in the simulator.
* "CARROT" gives the distance (in seconds, so ground speed is taken into account) between the carrot and the aircraft.
* "KILL_MODE_DISTANCE" is the threshold distance to switch the autopilot into KILL mode (defined descent with no throttle)
* "CONTROL_RATE" is the rate of the low level control loops in Hertz (60 or 20).

== Hardware definitions - Makefile ==

The airframe file must include the description of the controller board and it's low-level settings. This is done in one <tt>makefile</tt> section starting with the autopilot model and flashing mode:
{{Box Code|conf/airframes/myplane.xml|
<makefile>
include $(PAPARAZZI_SRC)/conf/autopilot/tiny.makefile
<nowiki>FLASH_MODE=IAP</nowiki>
.
.
.
</makefile>
}}
Below this are the definintions and configuration of the peripherals and interfaces.

=== Radio Control ===
The Paparazzi autpilot can interface directly with the PWM signal from any standard hobby R/C receiver. Signal decoding configuration settings for this are stored in the [[Radio_Control|Radio Control]] file.

If you have a Tiny v1.1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4015_MAT_hw.h\" -DSERVOS_4015_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4015_MAT_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you have a Tiny v2 or TWOG v1 Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_4017_hw.h\" -DSERVOS_4017</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_4017_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
If you want to output standard PPM to a R/C receiver:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_ppm_hw.h\" -DSERVOS_PPM_MAT</nowiki>
<nowiki>ap.srcs += $(SRC_ARCH)/servos_ppm_hw.c actuators.c</nowiki>
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.srcs += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
}}
This is used in the case where you want to directly drive a receiver which has a microcontroller to do the decoding and driving of the servos (not a 4015 or 4017 decoder chip). The PPM is output on the SERV_CLK pin. The PPM frame rate, pulse width, and number of channels can be adjusted in the "servos_ppm_hw.h" file to suit your particular receiver.

If you have a Classix Autopilot:
{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DRADIO_CONTROL -DRADIO_CONTROL_TYPE=RC_FUTABA</nowiki>
<nowiki>ap.EXTRA_SRCS += radio_control.c $(SRC_ARCH)/ppm_hw.c</nowiki>
<nowiki>ap.CFLAGS += -DACTUATORS=\"servos_direct_hw.h\"</nowiki>
<nowiki>ap.EXTRA_SRCS += $(SRC_ARCH)/servos_direct_hw.c</nowiki>
}}

You can set RADIO_CONTROL_TYPE to RC_FUTABA, for falling edge PPM, or RC_JR for rising edge PPM. "RC_FUTABA" is for the Futaba or compatible brands, and "RC_JR" for JR (a.k.a Graupner outside of the USA) or compatible brands.

For the Classix, you must specify which pins to use for PWM by adding "-DPWM_SERVO_0, etc." to the line fbw.CFLAGS. This activate the PWM channel.
<tt>wiring on classix PWM connector
connector LPC shared port
PWM1 PWM5 AD1_6 CAP1_3 P0.21
PWM2 PWM3 RXD0 EINT0 P0.1
PWM3 PWM1 TXD0 P0.0
PWM4 PWM6 RXD1 EINT3 P0.9
PWM5 PWM4 TXD1 AD1_1 P0.8
PWM6 PWM2 SSEL0 EINT2 P0.7</tt>
PWM1 and PWM6 should be safe. PWM4 and PWM5 should be OK if you're not using UART1 on the FBW processor - same for PWM2 and PWM3 if you're not using UART0 (disable FBW telemetry for that ).

=== Modem ===
The modem protocol and baud rate must be set in both the airframe file and ground station. Any standard baud rate can be used, with 9600 being adequate and 57600 recommended for most users to allow high speed telemetry for more detailed flight data analysis. The actual data rate is determined by the number of messages being sent and the period of each message as defined in <tt>conf/telemetry/default.xml</tt>. Those wishing to experiment with "alternative" modems can reduce the number and period of each telemetry message to fit within most any bandwidth constraint.

Paparazzi supports the following modem protocols:
* Standard transparent serial (pprz) - this is compatible with all modems and can be used to connect the autopilot directly to a PC for testing without a modem.
* Maxstream API protocol (xbee) - compatible with all Maxstream modems including the 9XTend and Zigbee. This protocol enables hardware addressing, allowing multiple aircraft to be managed from a single ground modem.
* Coronis Wavecard - necessary for operation with the unusual Coronis Wavecard modem.
Select the baud/protocol in the airframe file by commenting/uncommenting the appropriate section as follows:
==== Configuring The Serial Protocol ====
New users are advised to start with the standard serial protocol before attempting to setup an addressed API link. There are no real reasons for the novice user to use the xbee protocol over the standard PPRZTransport. Even if you are using a Maxstream modem you should still start out with the standard. Lastly it should be pointed out that using a single UAV there is no disadvantage and that the [http://www.engr.usu.edu/wiki/index.php/OSAM OSAM] Paparazzi Team at UAS 2008 took second place using the STANDARD protocol. The serial protocol works with virtually any modem as well as direct cable connections. The baud rates of the airborne modem, autopilot, ground modem, and PC must be configured correctly. The PC and autopilot serial ports do not need to be set to the same baud rate, i.e. when running multiple aircraft from a single ground modem, the ground modem may require a higher baud rate than any of the airborne modems in order to stream the data from multiple simultaneous sources.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="PPRZ"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
The above example tells the autopilot to send and recieve data in standard serial form.

{{Box Code|conf/airframes/myplane.xml - makefile section at the bottom|
# Serial modem
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=PprzTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DPPRZ_UART=Uart0 -DDATALINK=PPRZ -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c pprz_transport.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the serial transport protocol (pprz_transport.c). Use the "#" symbol to comment lines in this section of the airframe file.
 
Note:
* The autopilot and modem serial port baud rates must match at all times and also must match the ground modem rate, check your modem documentation to find the default baud rate and configure a different rate as needed.

 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>

<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]

==== Configuring The Maxstream API Protocol ====
The optional API protocol enables hardware addressing so that multiple aircraft can be managed from a single ground modem, or multiple aircraft and multiple ground stations can work simultaneously without interference from one another. API mode is enabled by sending an escape sequence (+++) followed by AT commands, this can be done automatically at each boot or can be permanently configured with the "ATWR" command for greater reliability.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\ATBD6\rATWR\r\""/>
...
</section></nowiki>
}}
The above example will program the Maxstream to API mode, 100mW power (ATPL2), 57600 baud (ATBD6), and permanently store the changes (ATWR). After flashing allow 30 seconds for the modem to store the changes, then disable the init string by adding the line <tt><define name="NO_XBEE_API_INIT" value="TRUE"/></tt> (the parameter "value" has no effect), update the baud rate as needed, and re-flash the autopilot. The modem and autopilot serial port baud rates must match eachother at all times.
 
Notes:
* Maxtream modems are factory configured for 9600 baud, in order to change baud rates, first configure the autopilot serial port to match the modem (DUART0_BAUD=B9600), boot the system so that the baud rate change command is sent to the modem (ATBD6) and permanently saved (ATWR), allow 30 seconds for the modem configuration to complete, then reprogram the autopilot with the new baud rate (DUART0_BAUD=B57600) and disabled modem configuration string <tt><define name="NO_XBEE_API_INIT" value="TRUE"/> </tt>.
* The ac_id defined in <tt>conf/conf.xml</tt> is permanently programmed into the modem so this procedure would need to be re-run if the modem is moved to another plane.
* For temporary boot-time API configuration remove any baud rate changes, remove <tt>ATWR\r</tt> from the end of the string.
* Upgrade your Maxstream firmware to the latest version before attempting API mode operation.

 

{{Box Code|confAgain/airframes/myplane.xml - makefile section at the bottom|
<nowiki># Maxstream API protocol</nowiki>
<nowiki>ap.CFLAGS += -DDOWNLINK -DUSE_UART0 -DDOWNLINK_TRANSPORT=XBeeTransport -DDOWNLINK_FBW_DEVICE=Uart0 -DDOWNLINK_AP_DEVICE=Uart0 -DXBEE_UART=Uart0 -DDATALINK=XBEE -DUART0_BAUD=B57600</nowiki>
<nowiki>ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c</nowiki>
}}
The above example configures the autopilot serial port (Uart0) to 57,600 baud and calls the Maxstream transport protocol (xbee.c). Use the "#" symbol to comment lines in this section of the airframe file.
 

Ensure that the ground station is using the same protocol and an equal or higher baud rate:
{{Box Code|conf/control_panel.xml|
<nowiki>
<session name="USB">
<program name="link">
<arg flag="-d" constant="/dev/paparazzi/ttyUSB0"/>
<arg flag="-transport" constant="xbee"/>
<arg flag="-uplink" constant=""/>
<arg flag="-s" constant="57600"/>
</program>
...
</session>
</nowiki>
}}
Use this constant /dev/paparazzi/ttyUSB0 when using either the ftdi cable or a Maxstream USB ground modem.. Otherwise use /dev/ttyUSB0 (the ttyUSB0 being the device that you are using. Note: it might not always be ttyUSB0). This paparazzi directory in the dev folder is created when setting the udev rules. [http://paparazzi.enac.fr/wiki/index.php/Installation#Setting_access_rights_for_USB_download Setting Udev rules]
=====Alternate Method=====
This is the way it is done in funjet1.xml and has been tested to work by Danstah

{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
<section name="MISC">
...
<define name="XBEE_INIT" value="\"ATPL2\rATRN1\rATTT80\r\""/>

...
</section></nowiki>
}}
Also use this
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>

<section name="DATALINK" prefix="DATALINK_">
<define name="DEVICE_TYPE" value="XBEE"/>
<define name="DEVICE_ADDRESS" value="...."/>
</section>
</nowiki>
}}
And Finally use this in the makefile section
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>
ap.CFLAGS += -DDOWNLINK -DUSE_UART1 -DDOWNLINK_TRANSPORT=XBeeTransport -DXBEE_UART=Uart1 -DDATALINK=XBEE -DUART1_BAUD=B9600
ap.srcs += downlink.c $(SRC_ARCH)/uart_hw.c datalink.c xbee.c
</nowiki>
}}
By reading all the information above you should be able to infer what the above does.

Now keep in mind that the ground modem baud rate and airplanes modem baud rates do not have to match. The only things that need to match are the the modem on the planes baud rate and the rate defined in the airframe file. For example this planes modem is set to 9600 and this could be used with the ground modem configured above using 57600...
Also for multiple UAV's a good way to configure them is to use 9600 for the ap and use a ground modem configured to 57600 and its not a bad idea to use minimal telemetry.

=== GPS ===
The serial port settings must match that of the GPS and are configured here along with the necessary files to interpret the u-blox UBX binary protocol:

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400</nowiki>
<nowiki>ap.srcs += gps_ubx.c gps.c</nowiki>
}}
'''Note:'''
* u-blox GPS modules are factory configured for 9600 baud, 38,400 baud is recommended along with the other required changes. The GPS can be accessed directly thru the [[Compiling#USB_flashing|UART Tunnel]] and [[GPS#GPS_configuration_using_U-Center Configured with|u-center]]

If using the u-blox LEA-5H, add the flag -DGPS_USE_LATLONG in the makefile section of the airframe xml file in the gps section. This flag must be inserted above "ap.srcs += gps_ubx.c gps.c" for proper operation.

{{Box Code|conf/airframes/myplane.xml|
<nowiki>ap.CFLAGS += -DGPS -DUBX -DUSE_UART1 -DGPS_LINK=Uart1 -DUART1_BAUD=B38400 -DGPS_USE_LATLONG
ap.srcs += gps_ubx.c gps.c</nowiki>
}}

=== Sensors ===

=== Control loops ===

The control loops can be divided in two largely independent groups : the vertical ones and the horizontal ones (files sw/airborne/fw_h_ctl.c and sw/airborne/fw_v_ctl.c ). Those loops can be commanded at different levels by either the R/C transmitter or the autonomous navigation routine.

First the horizontal loop:
{{Box Code|conf/airframes/funjet1.xml|
<nowiki>ap.CFLAGS += -DNAV -DAGR_CLIMB -DLOITER_TRIM
ap.srcs += nav.c fw_h_ctl.c fw_v_ctl.c
</nowiki>
}}

Previous Infrared Sensors

2009-02-22T16:53:04Z

Joekadet: /* '''Sensor Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]
The sensor marked "TOP" goes up.

----

With the above '''"Sensor Orientation"'''s IR1_SIGN, IR2_SIGN, and TOP_SIGN values ended up "1" in the Airframe file. For more information look in ( ~/paparazzi3/sw/airborne/infrared.c ) file on your system.

Previous Infrared Sensors

2009-02-22T05:16:52Z

Joekadet: /* '''Sensor Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]

With the above '''"Sensor Orientation"'''s IR1_SIGN, IR2_SIGN, and TOP_SIGN values ended up "1" in Airframe file. For more information look in ( ~/paparazzi3/sw/airborne/infrared.c ) file on your system.

Previous Infrared Sensors

2009-02-22T05:00:36Z

Joekadet: /* '''Sensor Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]

With the above '''"Sensor Orientation"'''s IR1_SIGN, IR2_SIGN, and TOP_SIGN values ended up "1" in Airframe file. For more information look in ~/paparazzi3/sw/airborne/infrared.c file on your system.

Previous Infrared Sensors

2009-02-21T15:30:29Z

Joekadet: /* '''Sensor Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]

With the above '''"Sensor Orientation"'''s IR1_SIGN, IRH2_SIGN, and TOP_SIGN values ended up "1" in Airframe file.

Previous Infrared Sensors

2009-02-21T15:26:35Z

Joekadet: /* '''Sensor Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]

The above '''"Sensor Orientation"s''' give me "1" for IR1_SIGN, IRH2_SIGN, and TOP_SIGN values in Airframe file.

Previous Infrared Sensors

2009-02-21T15:22:26Z

Joekadet: /* '''Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Sensor Orientation''' ===
[[Image:Z_Sensor.jpg]]

The above sensor orientations gave me "1" for IR1_SIGN, IRH2_SIGN, and TOP_SIGN values in Airframe file.

Previous Infrared Sensors

2009-02-21T15:20:30Z

Joekadet: /* '''Orientation''' */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]

=== '''Sensor Orientation''' ===
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

=== '''Orientation''' ===
[[Image:Z_Sensor.jpg]]

The above sensor orientations gave me "1" for IR1_SIGN, IRH2_SIGN, and TOP_SIGN values in Airframe file.

Previous Infrared Sensors

2009-02-21T15:13:36Z

Joekadet: /* Pinout */

File:Z Sensor.jpg

2009-02-21T15:06:50Z

Joekadet: Added "TOP" to existing drawing.

Added "TOP" to existing drawing.

Previous Infrared Sensors

2009-02-21T01:43:54Z

Joekadet: /* Pinout */

Previous Infrared Sensors

2009-02-21T01:34:27Z

Joekadet: /* Pinout */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

----

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

Previous Infrared Sensors

2009-02-21T01:32:12Z

Joekadet: /* Pinout */

== Dual Axis Board ==
[[Image:Ir_sensor_bot_small.jpg]]
=== Pinout ===

[[Image:IR_Sensor_2-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1|||IR2||IR Signal Output Axis 2||style="background:grey; color:white"|Grey
|-
|2||GND||Ground||style="background:black; color:white"|Black
|-
|3||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|4||IR1||IR Signal Output Axis 1||style="background:sienna; color:white"|Braun
|}
 
 
[[Image:Ir_dual.jpg]]
[[ Image:Tilted_Sensor.jpg]]

Align arrows FWD and AFT on fuselage, SM components up, Connector down.
Either arrow can be forward. Follow Wiki airframe configuration file
instructions.

== Single Axis Board ==
=== Pinout ===

[[Image:IR_Sensor_1-Axis_Pinout.jpg|frame|left|Component Side View]]

{| border="1" cellspacing="0" style="text-align:center" cellpadding="6"
!''Pin #''!!''Name''!!''Notes''!!width="50"|''Suggested Color''
|-
|1||IR||IR Signal Output||style="background:purple; color:white"|Purple
|-
|2||VCC|| +3.3v Power Supply||style="background:red; color:white"|Red
|-
|3||GND||Ground||style="background:black; color:white"|Black
|-
|}
 

[[Image:Ir_sensor_single_rotated.jpg]]

File:Tilted Sensor.jpg

2009-02-21T01:13:26Z

Joekadet: Align the arrows fwd and aft on fuselage, SM components up, connector down. Either arrow can be forward. Follow Wiki instructions. It's a snap from here

Align the arrows fwd and aft on fuselage, SM components up, connector down. Either arrow can be forward. Follow Wiki instructions. It's a snap from here

Users

2009-02-14T23:04:52Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| FelixR || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter
|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.
|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.
|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.
|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Tuning IR sensors, building removable sensor mount. Preparing for flight tests w/ Easystar.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro 2.4 GHz (PPZUAV). Multiplex Mentor ||| 2008 || Paparazzi AP and RF modems are installed, wired and working. Need to install IR modules, complete airframe build and tune AP. On track for first flight the end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Users

2009-02-14T23:01:18Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [[ email = hendrix at vivodinet dot gr| Chris Efstathiou]] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| FelixR || Edinburgh, Scotland || Booz2 quadrotor ||| 2008 || remote controlled flight, working on Kalman Filter
|- style="background:bisque; color:black"
| [mailto:azoreanuav_at_gmail.com Rui Costa] || Portugal, Azores || Outrunner Twinstar II with Tiny 2.11, Aerocomm datalink, 1W video tx ||| 2008 || Only ground test and software configuration.
|- style="background:bisque; color:black"
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.
|- style="background:bisque; color:black"
| [[User:G R|Gareth R]] || Sheffield, UK || Tiny 2.11, video, bunch of helicopters, pair of homebuilt Zagi's ||| 2008 || Telemetry flights finished, starting to tune.
|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 + LEA-4H (PPZUAV), Multiplex Cularis/Easystar, 9Xtend modem, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Tuning IR sensors, building removable sensor mount. Preparing for flight tests w/ Easystar.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing. Routine autonomous flight.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P, RF Modems XBee Pro Series 2 (PPZUAV). Multiplex Mentor ||| 2008 || Paparazzi AP and RF modems are installed, wired and working. Need to install IR modules, complete airframe build and tune AP. On track for first flight the end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Users

2009-01-27T19:56:32Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [mailto:hendrix_at_vivodinet.gr Chris Efstathiou] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 from PPZUAV, Multiplex Cularis, 9Xtend modems, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Debugging Tiny-GCS interface. Possibly first test flights in late Jan 09.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11/LEA-4P (PPZUAV) No RF Modems yet. Multiplex Mentor ||| 2008 || Working on Airframe build. Paparazzi AP is wired and working awaiting integration into airframe. First flight hopefully end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Users

2009-01-27T18:41:02Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [mailto:hendrix_at_vivodinet.gr Chris Efstathiou] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 from PPZUAV, Multiplex Cularis, 9Xtend modems, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Debugging Tiny-GCS interface. Possibly first test flights in late Jan 09.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama' || Tiny v2.11 (PPZUAV) Multiplex Mentor ||| 2008 || Working on Airframe build. Paparazzi AP is wired and working awaiting integration into airframe. First flight hopefully end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Users

2009-01-27T18:38:13Z

Joekadet:

Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Asia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|- style="background:bisque; color:black"
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Europe
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV.
|- style="background:bisque; color:black"
| [mailto:st.jr_at_gmx.at TomS] || Graz || Tiny 2.11 ||| 2008 || Starting to complete the wiring for the tiny and then trying to apply it to my TwinStar II.
|- style="background:bisque; color:black"
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny 2.11, EeePC as GCS, Multiplex FunJet ||| 2008 || Many successful flights.
|- style="background:bisque; color:black"
| [mailto:x-microdrones@2007.polytechnique.org X-MicroDrones] || Paris, France || Tiny 2.11, Quad-Tilt-Rotor VTOL ||| 2008 || Wiring completed, first flights soon... We're trying to adapt Paparazzi to a Quad-Tilt-Rotor VTOL able to perform both airplane-like and helicopter-like flights. Working on inertial measurement units implementation.
|- style="background:bisque; color:black"
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues
|- style="background:bisque; color:black"
| [mailto:spam1_at_marzer.com CedricM] || Geneva, Switzerland || Tiny 2.11, Multiplex FunJet with video camera ||| 2008 || Many successful flights working on an osd module and weather probes.
|- style="background:bisque; color:black"
| [mailto:hendrix_at_vivodinet.gr Chris Efstathiou] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ North America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
|Vancouver, WA [http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=98663&sll=37.0625,-95.677068&sspn=64.664844,101.953125&ie=UTF8&ll=45.606112,-122.643471&spn=0.222411,0.398254&z=12 98663]
| Tiny v2.11 || Nov. 2008 || Getting geared up for a maiden flight soon hopefully. Skype: pauldanielcox Gtalk: [use email]
|- style="background:bisque; color:black"
| [mailto:quill_at_u.washington.edu John Burt] || Portland, Oregon || Tiny v2.11 from PPZUAV, Multiplex Cularis, 9Xtend modems, T7CAP TX, ground station: EEE PC701 and/or Nokia N810 ||| Jan 2009 || Debugging Tiny-GCS interface. Possibly first test flights in late Jan 09.
|- style="background:bisque; color:black"
| [mailto:bmw330i@me.com David Conger] || San Diego (Ramona), California || Tiny1.3 (PPZUAV) ||| Sept 2007 || Flying Wing MAV with onboard video. Test platform for the new 900mhz XBPro 900 RF modems.
|- style="background:bisque; color:black"
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing
|- style="background:bisque; color:black"
| [http://www.engr.usu.edu/wiki/index.php/OSAM USU OSAM-UAV] || Logan, UT || TWOG (PPZUAV) ||| June 2007 || 2x72" 5x48" 1x60" Flying Wings. Research backyard for AggieAir Remote Sensing
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Central America
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:joschau@comcast.net Joekadet] || David Panama || Tiny v2.11 Multiplex Mentor ||| 2008 || Working on Airframe build. Paparazzi AP is wired and working awaiting integration into airframe. First flight hopefully end of February.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}
----
{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ Australia
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:todd_soaring@yahoo.com.au Todd Sandercock] || Adelaide, SA || Tiny v2.11, Multiplex Twinjet, 9Xtend modems ||| Jan 2008 || Completed successful flight testing. Now designing new airframe.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}