PaparazziUAV - User contributions [en]

Users

2009-06-22T17:32:31Z

Muralha: /* Europe */

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]

[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]

[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]

==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"
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.
|- 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 || Tiny 2.11 || 2008 || Starting

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting

|- style="background:bisque; color:black"
| [mailto:kostalexis@ece.upatras.gr AneMos-Group] || Patras, Greece || Tiny 2.11, Quadrotor VTOL ||| 2008 || Working on IMU, Trying to implement Constrained Control for the quadrotor trajectory flight

|- style="background:bisque; color:black"
| [mailto:allan.ojala@gmail.com Allan Ojala] || Vaasa, Finland || TWOG, with AC4790 radio and LEA-5H GPS ||| 2009 || Just constructed my own first RC airplane SIG KADET.

|- 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 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops 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.

|- 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"
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison] || Neutral Bay, NSW || Tiny v2.11, Vertical + Horizontal IR sensors, XBee modems, Futaba T6EXAP TX, Futaba R136F RX, Funjet, MacBook laptop ||| August 2008 || Finished getting all the hardware together for a basic Funjet. Now putting it all together.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

Users

2009-04-14T20:01:08Z

Muralha: /* Europe */

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]

[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]

==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"
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.
|- 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 || On hold

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

Users

2009-03-02T20:39:42Z

Muralha: /* Europe */

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

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

Software Wish List

2008-05-08T12:32:11Z

Muralha: /* Ground Station Suggestions */

{|
|-valign="top"
|__TOC__
|Please use the [[Talk:Software_Wish_List|Discussion]] tab at the top of the page, as appropriate
|}
== Ground Station Suggestions ==
* Path interpreter
* Divide the flight plan into 3 separate files [[User:Jeremy|(Jeremy)]]
*: Takeoff/Landing - flight plan blocks describing the complex routines and using altitudes and waypoints from the ''User'' file
*: Generic - a file that users should never need to edit, containing circles, rectangles, figure-8's, and surveys that appear on command when GCS buttons are pressed. Altitude/locations could be relative to the ''User'' file
*: User - Here we can specify fixed or dynamic ''Home'' point and add complex routines or simply save certain basic routines.
* How about the possibility to use multiple ground modem connected to a single ground station. The RSSI could be use to dynamically choose which currently has the best signal. This would alow the use of different antennas on each of the modems or have antenna pointing in different directions
* PFD - the horizon and the sky shouldn't move only the main line. '''Because we are on the ground''' and we really need to see the roll angle of the uav and not the real PFD like on a real airplane. And we could also see, the pitch angle, to see if the uav is climbing or going down.
* Language packs - English, French, German, Italian, Spanish, Portuguese, ... (i can help on portuguese)

== Airborne Software Suggestions ==
=== Stability ===
=== Navigation ===
* Flight plan stage sensing
*: Carrot should continue past the waypoint toward the next point, but the point should not be officially acknowledged until the plane has passed it. This way we can have smooth, intelligent navigation while still considering waypoint triggers such as still-photo, sensor drop, or throttle off.

=== Other ===
* '''Revised autopilot modes''' [[User:Jeremy|(Jeremy)]]
*: I propose a restructuring of the modes as follows - create 3 top-level modes: '''Man, Stab,'''and '''Auto''', each with an appended autonomous sub-mode (i.e. '''Man'''/''Climb'', '''Stab'''/''Kill'', '''Auto'''/''Landing'', etc.) This will give the operator much more information and a much better indication of what the plane will do when switched to autonomous mode in a concise manner. Furthermore, I see an advantage in having simple behaviors like ''Climb, Landing'', etc. be defined as sub-modes so that operator is always alerted of changes such as ''Descent'' or can easily configure trim, gains, and payload options in the airframe file (i.e. if mode = ''Landing'' then retract camera, turn off video system, use landing trim, etc.)
** ''Sub-modes''
*# ''Ground'' - The default boot mode. In this mode the throttle is locked at 0% or not armed at all (no PWM signal), stability is disabled (servos locked in neutral position), and video power is off, but flight plan blocks are processed. This will improve safety and aid in lost plane retreival as the servos, and video will not drain the battery if landing detection is implemented. ''Ground'' mode should exit '''only''' if ''Takeoff'' is manually triggered.
*# ''Takeoff'' - 3 possible triggers: GCS button, GPIO button, or R/C throttle. Checks for error modes and desired climb, then arms/unlocks throttle, initates "Takeoff" flight plan block, and instantly deroutes to ''Climb'' mode. Deroutes to ''Descent'' mode without unlocking throttle if not OK. ''Takeoff'' could simply be a flag rather than a "mode".
*# ''Climb'' - Triggered anytime "aggressive climb" is active
*# ''Descent'' - Triggered anytime "aggressive descent" is active
*# ''Nav'' - Normal level flight
*# ''Landing'' - Same as ''Nav'' but using the "Landing" flight plan block and any airframe gains/trims/payload options as defined in airframe.xml
*# ''Kill'' - Triggered manually - locks throttle at 0% and uses pitch/roll settings from Airframe.xml.
** ''Error sub-modes''
*# ''No GPS'' - A temporary mode using pitch/roll settings from airframe.xml
*# ''Home'' - Triggered by distance in '''Auto''' mode or by distance/RC loss in '''Stab''' mode (after ''n'' seconds, as defined in airframe.xml). Exits upon manual block/mode change requests from the GCS and cannot be re-initiated for 30 seconds.

* '''Continually broadcast last known location'''
*: AP should continue to broadcast the last known GPS coordinate in the event of GPS loss. (i.e. upside-down crashed plane should continue to send last known position in case it was out of data range prior to the crash.)

Software Wish List

2008-04-29T13:59:27Z

Muralha: /* Ground Station Suggestions */

{|
|-valign="top"
|__TOC__
|Please use the [[Talk:Software_Wish_List|Discussion]] tab at the top of the page, as appropriate
|}
== Ground Station Suggestions ==
* Path interpreter
* Divide the flight plan into 3 separate files [[User:Jeremy|(Jeremy)]]
*: Takeoff/Landing - flight plan blocks describing the complex routines and using altitudes and waypoints from the ''User'' file
*: Generic - a file that users should never need to edit, containing circles, rectangles, figure-8's, and surveys that appear on command when GCS buttons are pressed. Altitude/locations could be relative to the ''User'' file
*: User - Here we can specify fixed or dynamic ''Home'' point and add complex routines or simply save certain basic routines.
* How about the possibility to use multiple ground modem connected to a single ground station. The RSSI could be use to dynamically choose which currently has the best signal. This would alow the use of different antennas on each of the modems or have antenna pointing in different directions
* PFD - the horizon and the sky shouldn't move only the main line. '''Because we are on the ground''' and we really need to see the roll angle of the uav and not the real PFD like on a real airplane. And we could also see, the pitch angle, to see if the uav is climbing or going down.

== Airborne Software Suggestions ==
=== Stability ===
=== Navigation ===
* Flight plan stage sensing
*: Carrot should continue past the waypoint toward the next point, but the point should not be officially acknowledged until the plane has passed it. This way we can have smooth, intelligent navigation while still considering waypoint triggers such as still-photo, sensor drop, or throttle off.

=== Other ===
* '''Revised autopilot modes''' [[User:Jeremy|(Jeremy)]]
*: I propose a restructuring of the modes as follows - create 3 top-level modes: '''Man, Stab,'''and '''Auto''', each with an appended autonomous sub-mode (i.e. '''Man'''/''Climb'', '''Stab'''/''Kill'', '''Auto'''/''Landing'', etc.) This will give the operator much more information and a much better indication of what the plane will do when switched to autonomous mode in a concise manner. Furthermore, I see an advantage in having simple behaviors like ''Climb, Landing'', etc. be defined as sub-modes so that operator is always alerted of changes such as ''Descent'' or can easily configure trim, gains, and payload options in the airframe file (i.e. if mode = ''Landing'' then retract camera, turn off video system, use landing trim, etc.)
** ''Sub-modes''
*# ''Ground'' - The default boot mode. In this mode the throttle is locked at 0% or not armed at all (no PWM signal), stability is disabled (servos locked in neutral position), and video power is off, but flight plan blocks are processed. This will improve safety and aid in lost plane retreival as the servos, and video will not drain the battery if landing detection is implemented. ''Ground'' mode should exit '''only''' if ''Takeoff'' is manually triggered.
*# ''Takeoff'' - 3 possible triggers: GCS button, GPIO button, or R/C throttle. Checks for error modes and desired climb, then arms/unlocks throttle, initates "Takeoff" flight plan block, and instantly deroutes to ''Climb'' mode. Deroutes to ''Descent'' mode without unlocking throttle if not OK. ''Takeoff'' could simply be a flag rather than a "mode".
*# ''Climb'' - Triggered anytime "aggressive climb" is active
*# ''Descent'' - Triggered anytime "aggressive descent" is active
*# ''Nav'' - Normal level flight
*# ''Landing'' - Same as ''Nav'' but using the "Landing" flight plan block and any airframe gains/trims/payload options as defined in airframe.xml
*# ''Kill'' - Triggered manually - locks throttle at 0% and uses pitch/roll settings from Airframe.xml.
** ''Error sub-modes''
*# ''No GPS'' - A temporary mode using pitch/roll settings from airframe.xml
*# ''Home'' - Triggered by distance in '''Auto''' mode or by distance/RC loss in '''Stab''' mode (after ''n'' seconds, as defined in airframe.xml). Exits upon manual block/mode change requests from the GCS and cannot be re-initiated for 30 seconds.

* '''Continually broadcast last known location'''
*: AP should continue to broadcast the last known GPS coordinate in the event of GPS loss. (i.e. upside-down crashed plane should continue to send last known position in case it was out of data range prior to the crash.)

Software Wish List

2008-04-29T13:57:53Z

Muralha: /* Ground Station Suggestions */

{|
|-valign="top"
|__TOC__
|Please use the [[Talk:Software_Wish_List|Discussion]] tab at the top of the page, as appropriate
|}
== Ground Station Suggestions ==
* Path interpreter
* Divide the flight plan into 3 separate files [[User:Jeremy|(Jeremy)]]
*: Takeoff/Landing - flight plan blocks describing the complex routines and using altitudes and waypoints from the ''User'' file
*: Generic - a file that users should never need to edit, containing circles, rectangles, figure-8's, and surveys that appear on command when GCS buttons are pressed. Altitude/locations could be relative to the ''User'' file
*: User - Here we can specify fixed or dynamic ''Home'' point and add complex routines or simply save certain basic routines.
* How about the possibility to use multiple ground modem connected to a single ground station. The RSSI could be use to dynamically choose which currently has the best signal. This would alow the use of different antennas on each of the modems or have antenna pointing in different directions
* PFD - the horizon and the sky shouldn't move only the main line. '''Because we are on the ground''' and we really need to see the turn rate of the uav and not the real PFD like on a real airplane. And we could also see, the pitch angle, to see if the uav is climbing or going down.

== Airborne Software Suggestions ==
=== Stability ===
=== Navigation ===
* Flight plan stage sensing
*: Carrot should continue past the waypoint toward the next point, but the point should not be officially acknowledged until the plane has passed it. This way we can have smooth, intelligent navigation while still considering waypoint triggers such as still-photo, sensor drop, or throttle off.

=== Other ===
* '''Revised autopilot modes''' [[User:Jeremy|(Jeremy)]]
*: I propose a restructuring of the modes as follows - create 3 top-level modes: '''Man, Stab,'''and '''Auto''', each with an appended autonomous sub-mode (i.e. '''Man'''/''Climb'', '''Stab'''/''Kill'', '''Auto'''/''Landing'', etc.) This will give the operator much more information and a much better indication of what the plane will do when switched to autonomous mode in a concise manner. Furthermore, I see an advantage in having simple behaviors like ''Climb, Landing'', etc. be defined as sub-modes so that operator is always alerted of changes such as ''Descent'' or can easily configure trim, gains, and payload options in the airframe file (i.e. if mode = ''Landing'' then retract camera, turn off video system, use landing trim, etc.)
** ''Sub-modes''
*# ''Ground'' - The default boot mode. In this mode the throttle is locked at 0% or not armed at all (no PWM signal), stability is disabled (servos locked in neutral position), and video power is off, but flight plan blocks are processed. This will improve safety and aid in lost plane retreival as the servos, and video will not drain the battery if landing detection is implemented. ''Ground'' mode should exit '''only''' if ''Takeoff'' is manually triggered.
*# ''Takeoff'' - 3 possible triggers: GCS button, GPIO button, or R/C throttle. Checks for error modes and desired climb, then arms/unlocks throttle, initates "Takeoff" flight plan block, and instantly deroutes to ''Climb'' mode. Deroutes to ''Descent'' mode without unlocking throttle if not OK. ''Takeoff'' could simply be a flag rather than a "mode".
*# ''Climb'' - Triggered anytime "aggressive climb" is active
*# ''Descent'' - Triggered anytime "aggressive descent" is active
*# ''Nav'' - Normal level flight
*# ''Landing'' - Same as ''Nav'' but using the "Landing" flight plan block and any airframe gains/trims/payload options as defined in airframe.xml
*# ''Kill'' - Triggered manually - locks throttle at 0% and uses pitch/roll settings from Airframe.xml.
** ''Error sub-modes''
*# ''No GPS'' - A temporary mode using pitch/roll settings from airframe.xml
*# ''Home'' - Triggered by distance in '''Auto''' mode or by distance/RC loss in '''Stab''' mode (after ''n'' seconds, as defined in airframe.xml). Exits upon manual block/mode change requests from the GCS and cannot be re-initiated for 30 seconds.

* '''Continually broadcast last known location'''
*: AP should continue to broadcast the last known GPS coordinate in the event of GPS loss. (i.e. upside-down crashed plane should continue to send last known position in case it was out of data range prior to the crash.)

Software Wish List

2008-04-28T11:49:47Z

Muralha: /* Ground Station Suggestions */

{|
|-valign="top"
|__TOC__
|Please use the [[Talk:Software_Wish_List|Discussion]] tab at the top of the page, as appropriate
|}
== Ground Station Suggestions ==
* Path interpreter
* Divide the flight plan into 3 separate files [[User:Jeremy|(Jeremy)]]
*: Takeoff/Landing - flight plan blocks describing the complex routines and using altitudes and waypoints from the ''User'' file
*: Generic - a file that users should never need to edit, containing circles, rectangles, figure-8's, and surveys that appear on command when GCS buttons are pressed. Altitude/locations could be relative to the ''User'' file
*: User - Here we can specify fixed or dynamic ''Home'' point and add complex routines or simply save certain basic routines.
* How about the possibility to use multiple ground modem connected to a single ground station. The RSSI could be use to dynamically choose which currently has the best signal. This would alow the use of different antennas on each of the modems or have antenna pointing in different directions
* PFD - the horizon and the sky shouldn't move only the main line. '''Because we are on the ground''' and we really need to see the turn rate of the uav and not the real PFD like on a real airplane.

== Airborne Software Suggestions ==
=== Stability ===
=== Navigation ===
* Flight plan stage sensing
*: Carrot should continue past the waypoint toward the next point, but the point should not be officially acknowledged until the plane has passed it. This way we can have smooth, intelligent navigation while still considering waypoint triggers such as still-photo, sensor drop, or throttle off.

=== Other ===
* '''Revised autopilot modes''' [[User:Jeremy|(Jeremy)]]
*: I propose a restructuring of the modes as follows - create 3 top-level modes: '''Man, Stab,'''and '''Auto''', each with an appended autonomous sub-mode (i.e. '''Man'''/''Climb'', '''Stab'''/''Kill'', '''Auto'''/''Landing'', etc.) This will give the operator much more information and a much better indication of what the plane will do when switched to autonomous mode in a concise manner. Furthermore, I see an advantage in having simple behaviors like ''Climb, Landing'', etc. be defined as sub-modes so that operator is always alerted of changes such as ''Descent'' or can easily configure trim, gains, and payload options in the airframe file (i.e. if mode = ''Landing'' then retract camera, turn off video system, use landing trim, etc.)
** ''Sub-modes''
*# ''Ground'' - The default boot mode. In this mode the throttle is locked at 0% or not armed at all (no PWM signal), stability is disabled (servos locked in neutral position), and video power is off, but flight plan blocks are processed. This will improve safety and aid in lost plane retreival as the servos, and video will not drain the battery if landing detection is implemented. ''Ground'' mode should exit '''only''' if ''Takeoff'' is manually triggered.
*# ''Takeoff'' - 3 possible triggers: GCS button, GPIO button, or R/C throttle. Checks for error modes and desired climb, then arms/unlocks throttle, initates "Takeoff" flight plan block, and instantly deroutes to ''Climb'' mode. Deroutes to ''Descent'' mode without unlocking throttle if not OK. ''Takeoff'' could simply be a flag rather than a "mode".
*# ''Climb'' - Triggered anytime "aggressive climb" is active
*# ''Descent'' - Triggered anytime "aggressive descent" is active
*# ''Nav'' - Normal level flight
*# ''Landing'' - Same as ''Nav'' but using the "Landing" flight plan block and any airframe gains/trims/payload options as defined in airframe.xml
*# ''Kill'' - Triggered manually - locks throttle at 0% and uses pitch/roll settings from Airframe.xml.
** ''Error sub-modes''
*# ''No GPS'' - A temporary mode using pitch/roll settings from airframe.xml
*# ''Home'' - Triggered by distance in '''Auto''' mode or by distance/RC loss in '''Stab''' mode (after ''n'' seconds, as defined in airframe.xml). Exits upon manual block/mode change requests from the GCS and cannot be re-initiated for 30 seconds.

* '''Continually broadcast last known location'''
*: AP should continue to broadcast the last known GPS coordinate in the event of GPS loss. (i.e. upside-down crashed plane should continue to send last known position in case it was out of data range prior to the crash.)

Installation/Linux

2008-02-11T14:58:43Z

Muralha: /* LiveCd */

Precompiled binaries can be downloaded and executed with the ''paparazzi-bin'' package but to maintain the power and flexibility of open-source code, most operations within Paparazzi involve recompilation of autopilot and/or ground station code. Therefore the typical installation requires all of the necessary C and OCaml compilers as well as some XML and [http://www.tls.cena.fr/products/ivy/ Ivy] handlers. These tools are provided by the ''paparazzi-dev'' package.

The Paparazzi sources are hosted by [http://savannah.nongnu.org/cvs/?group=paparazzi Savannah].

The Paparazzi packages are hosted at the [http://www.recherche.enac.fr/paparazzi/debian ENAC repository].

== Installation on Debian based distributions ==

Paparazzi is packaged for Debian as well as all of its dependencies. The [http://www.recherche.enac.fr/paparazzi/debian repository] hosted at ENAC holds their latest version.

=== Installation from the Command Line===
Just add the following line to your repository list (/etc/apt/sources.list). Replace etch by sarge (oldstable distribution) or sid (unstable distribution) if needed. Note: It is no longer required to specify both sarge and etch.
{{Box Code|/etc/apt/sources.list|
deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> etch main
}}
Then, update your sources and install the precompiled binaries
apt-get update
apt-get install paparazzi-bin
or the dependencies needed for recompiling from the source (dev), and the cross-compiler (arm7) :
apt-get update
apt-get install paparazzi-dev
apt-get install paparazzi-arm7
Note: It is not recommended to install both <tt>paparazzi-bin</tt> and <tt>paparazzi-dev</tt>. While the bin package is self-contained and should be sufficient for users who do not want to patch the code, the dev meta-package provides only the tools to compile the source code which must be separately downloaded, from an archive or the CVS repository.

Note: Installation works fine on the Ubuntu 7.10 distribution (using the etch distro).

==== Optional/Obsolete Packages ====
Users of older AVR based boards will also need the paparazzi-avr package.

==== Extra for Ubuntu 7.04 and 7.10 ====

The Braille TTY driver interferes with FTDI USB Serial adapters and should be removed:

sudo apt-get remove brltty

=== Installation thru Synaptic Package Manager ===
* Launch ''Synaptic Package Manager'' (''Applications/System'' Tools Menu)
* In '''Settings/Repositories''', add a new repository on URI = '''<nowiki>http://paparazzi.enac.fr/debian</nowiki>''', Distribution = '''etch''' (or '''sarge''' or '''sid'''), Section = '''main'''
* Search for <tt>paparazzi-bin</tt>, <tt>paparazzi-dev</tt>, and <tt>paparazzi-arm7</tt> packages (use the ''Search'' button)
* Mark them for installation (right-click on package names)
* Left-click on ''Apply''

== Manual Installation of Individual Packages ==
Users of other Linux flavors or anyone needing manual control of each individual package can install them independently. The list of dependencies of the Debian package is located in the [http://cvs.savannah.gnu.org/viewvc/paparazzi/paparazzi3/debian/control.etch?revision=1.16&view=markup <tt> debian/control.etch</tt>] file and may help users of other distributions.

The binary packages and some corresponding source tarballs can be downloaded from

http://paparazzi.enac.fr/debian/dists/etch/main/binary-i386/

For distributions using RPM packaging, the [http://packages.debian.org/unstable/source/alien alien] tool can be used to translate a .deb package into a .rpm package.

For Fedora (Core8) users, you can install the following packages from standard repository:
* ocaml.i386
* ocaml-camlimages-devel.i386
* ocaml-lablgtk-devel.i386
* ocaml-xml-light-devel.i386
* boa.i386
* libgnomecanvas-devel.i386
* libusb-devel.i386
* pcre-devel.i386
* arm-gp2x-linux-gcc.i386
* arm-gp2x-linux-binutils.i386
* glade2.i386
* and gcc, make, cvs, gnuplot, imagemagik...

Then you need [http://packages.debian.org/unstable/source/alien alien] tool to convert packages from the paparazzi repository:
* ivy-c
* ivy-c-dev
* ivy-ocaml (WARNING: debian and fedora have different path for ocaml (/usr/lib/ocaml/<version> vs. /usr/lib/ocaml), so you need to move by hand the files in /usr/lib/ocaml/<version> to /usr/lib/ocaml)
* lpc21isp

== Installing the Source Code (not needed with paparazzi-bin) ==
After the <tt>paparazzi-dev</tt> package is installed the complete source code should be downloaded from the CVS repository. See the [http://savannah.nongnu.org/cvs/?group=paparazzi project page] at Savannah for more details. From the directory of your choice type:
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/paparazzi co paparazzi3
This will download all of the code and install it into <tt>paparazzi3/</tt>

If you cannot use the CVS install, dayly updated tarballs can also be fetched from the [[Downloads|Downloads]] page.

== Launching the Software ==

If you are using the <tt>paparazzi-bin</tt> package or the Live-CD, just launch the <tt>paparazzi</tt> binary application and you will be guided through the installation of your personal configuration files.

If you are using the source code, the first step is to compile it. From the <tt>paparazzi3</tt> directory (<tt>cd paparazzi3</tt>), run

make

You will have to run these command after each update of the source (<tt>cvs update</tt> command).
Launch the software from the <tt>paparazzi3</tt> directory with

./paparazzi

From the [[Paparazzi_Center|Paparazzi Center]] interface, select the ''MJ5'' aircraft, select the ''sim'' target and ''Build'' it. Then ''Execute'' the ''Simulation'' session.

If ('''and only if''') you want to directly launch some Paparazzi agents (the ''Tools'' of the [[Paparazzi_Center|Paparazzi Center]]), without using the Paparazzi Center, you must have the Paparazzi source and home environment variables set correctly in your shell. These variables can be automatically set in your shell by adding the following lines to your .bashrc file:
{{Box Code|/home/your_username/.bashrc|
export PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
export PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''
}}
If you wish to manually set the env variables (i.e. when compiling a backup copy of your code in a different folder) execute the following command from the folder you wish to set as your active paparazzi folder:
export PAPARAZZI_HOME=`pwd`;export PAPARAZZI_SRC=`pwd`
Verify that your variables are set correctly with the following command:
env | grep PAPARAZZI
which should return the following:
PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''

== Setting access rights for USB download ==

This is required to flash the Paparazzi-boards via USB. For details, see [[Compiling]].

For USB download as non root you need permission to access the "raw" USB bus. You should be member of the ''plugdev'' group. The original user mentioned in the Linux install process usually is member, otherwise add your login using

sudo adduser <your login> plugdev

then logout and relogin. Tell the system to allow access by adding the following

# all (fake VID 0x7070) LPCUSB devices (access through libusb)
BUS=="usb", SYSFS{idVendor}=="7070", GROUP="plugdev"

through copying the file "10-paparazzi.rules" as root from $PAPARAZZI_HOME/conf/system/udev/rules/ to /etc/udev/rules.d/

== Software Updates ==
Paparazzi is a very rapidly evolving project and as such, you will find that variables and functions are frequently added, changed, or removed. Update your software with care and caution, and always test the functionality on the ground and in the air as some updates will affect tuning parameters. Your airframe file will not be updated by the CVS system and therefore any new or modified variable names will need to be added manually. The compiler will usually identify the problem variables at which point you can look at some of the most recent airframe files on the CVS to find the proper syntax. See the [[Compiling]] page for more help if needed.
 
That said, keeping your software up to date is easy with the CVS system. The system will compare all source code files with the server and update any that are needed, automatically merging any minor changes that you have incorporated along the way.

To download and automatically merge any updated source files, run the following command from your Paparazzi directory
cvs update -d
where the <tt>-d</tt> is needed to get any new directories.

After any CVS update or source code modification the code can be recompiled from ''your paparazzi3 directory'' with the following command:

make

The ''make'' command will only recompile portions of the software where changed have been detected. If it does not behave as expected you can deleted all compiled files and recompile from scratch with the following commands:

make clean
make

See the [[Compiling]] page for more info.

Users making changes to their code structure may prefer to have more control over the updating and merging process and may wish to install and use '''tkcvs''' instead which provides highlighted comparisons of any files that differ between your code and the CVS server and allows for a file by file update.

To update your Linux distribution as well as any dependencies of Paparazzi (seldom necessary), run the following as root:
apt-get update
apt get upgrade

== LiveCd ==

The LiveCD is an easy way to test Paparazzi: no installation is required and no changes are made to your computer. Simply burn the image as a boot CD and reboot! The LiveCD includes Linux and the complete paparazzi binary package (code source, tools and cross compilers). It is intended for demonstration only and not frequently updated but it contains the complete system and can store changed files on a pen drive or compressed file on your hard drive so that it can compile, flash, and operate any aircraft, albeit slowly.

The CD image is available from the [[Downloads|Downloads]] page.

The Paparazzi demo is launchable on the Live CD from the Paparazzi icon.

Knoppix allows for all the user data to be saved on a hard disk partition (most file systems are supported) or on a removable device (typically a USB pendrive). Note that this action is not destructive: the user data tree is compressed and stored on your file system as a single file (<tt>knoppix.img</tt>).
* From the Knoppix menu (second from bottom left), choose '''Configure''', '''Create a persistent KNOPPIX disk image'''
* Choose your media (be sure to connect your USB pendrive before booting!)
* Choose if you want an encrypted filesystem (to protect your flight plan designed for the next MAV competition :-) )
* Choose the size of your home directory (100Mb is recommended)
On the next reboot, this saved state will be automatically located and loaded.

Using this persistent feature, the Paparazzix Live CD can really be used to configure, simulate and fly an aircraft with the Paparazzi system.

The Live CD can also be used to install a Debian system on the hard disk, using the <tt>knoppix-installer</tt> command. Be sure to backup the hard disk before trying ...

[[Image:Lightscribe_CD_Cover_1.JPG|thumb|320px|LightScribe CD Cover]] A LiveCD needs some looks... In color or in LightScribe format, your CD will always look cool.
* Get the PDF version for download here [http://paparazzi.enac.fr/wiki_images/Lightscribe_CD_Cover_1.pdf LightScribe CD Cover 1].

* The LightScribe version is in Nero Cover Design format (.ncd) and it's here for download [http://paparazzi.enac.fr/wiki_images/Lightscribe_CD_Cover_1.zip LightScribe CD Cover 1]

Installation/Linux

2008-02-09T22:43:43Z

Muralha: /* LiveCd */

Precompiled binaries can be downloaded and executed with the ''paparazzi-bin'' package but to maintain the power and flexibility of open-source code, most operations within Paparazzi involve recompilation of autopilot and/or ground station code. Therefore the typical installation requires all of the necessary C and OCaml compilers as well as some XML and [http://www.tls.cena.fr/products/ivy/ Ivy] handlers. These tools are provided by the ''paparazzi-dev'' package.

The Paparazzi sources are hosted by [http://savannah.nongnu.org/cvs/?group=paparazzi Savannah].

The Paparazzi packages are hosted at the [http://www.recherche.enac.fr/paparazzi/debian ENAC repository].

== Installation on Debian based distributions ==

Paparazzi is packaged for Debian as well as all of its dependencies. The [http://www.recherche.enac.fr/paparazzi/debian repository] hosted at ENAC holds their latest version.

=== Installation from the Command Line===
Just add the following line to your repository list (/etc/apt/sources.list). Replace etch by sarge (oldstable distribution) or sid (unstable distribution) if needed. Note: It is no longer required to specify both sarge and etch.
{{Box Code|/etc/apt/sources.list|
deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> etch main
}}
Then, update your sources and install the precompiled binaries
apt-get update
apt-get install paparazzi-bin
or the dependencies needed for recompiling from the source (dev), and the cross-compiler (arm7) :
apt-get update
apt-get install paparazzi-dev
apt-get install paparazzi-arm7
Note: It is not recommended to install both <tt>paparazzi-bin</tt> and <tt>paparazzi-dev</tt>. While the bin package is self-contained and should be sufficient for users who do not want to patch the code, the dev meta-package provides only the tools to compile the source code which must be separately downloaded, from an archive or the CVS repository.

Note: Installation works fine on the Ubuntu 7.10 distribution (using the etch distro).

==== Optional/Obsolete Packages ====
Users of older AVR based boards will also need the paparazzi-avr package.

==== Extra for Ubuntu 7.04 and 7.10 ====

The Braille TTY driver interferes with FTDI USB Serial adapters and should be removed:

sudo apt-get remove brltty

=== Installation thru Synaptic Package Manager ===
* Launch ''Synaptic Package Manager'' (''Applications/System'' Tools Menu)
* In '''Settings/Repositories''', add a new repository on URI = '''<nowiki>http://paparazzi.enac.fr/debian</nowiki>''', Distribution = '''etch''' (or '''sarge''' or '''sid'''), Section = '''main'''
* Search for <tt>paparazzi-bin</tt>, <tt>paparazzi-dev</tt>, and <tt>paparazzi-arm7</tt> packages (use the ''Search'' button)
* Mark them for installation (right-click on package names)
* Left-click on ''Apply''

== Manual Installation of Individual Packages ==
Users of other Linux flavors or anyone needing manual control of each individual package can install them independently. The list of dependencies of the Debian package is located in the [http://cvs.savannah.gnu.org/viewvc/paparazzi/paparazzi3/debian/control.etch?revision=1.16&view=markup <tt> debian/control.etch</tt>] file and may help users of other distributions.

The binary packages and some corresponding source tarballs can be downloaded from

http://paparazzi.enac.fr/debian/dists/etch/main/binary-i386/

For distributions using RPM packaging, the [http://packages.debian.org/unstable/source/alien alien] tool can be used to translate a .deb package into a .rpm package.

For Fedora (Core8) users, you can install the following packages from standard repository:
* ocaml.i386
* ocaml-camlimages-devel.i386
* ocaml-lablgtk-devel.i386
* ocaml-xml-light-devel.i386
* boa.i386
* libgnomecanvas-devel.i386
* libusb-devel.i386
* pcre-devel.i386
* arm-gp2x-linux-gcc.i386
* arm-gp2x-linux-binutils.i386
* glade2.i386
* and gcc, make, cvs, gnuplot, imagemagik...

Then you need [http://packages.debian.org/unstable/source/alien alien] tool to convert packages from the paparazzi repository:
* ivy-c
* ivy-c-dev
* ivy-ocaml (WARNING: debian and fedora have different path for ocaml (/usr/lib/ocaml/<version> vs. /usr/lib/ocaml), so you need to move by hand the files in /usr/lib/ocaml/<version> to /usr/lib/ocaml)
* lpc21isp

== Installing the Source Code (not needed with paparazzi-bin) ==
After the <tt>paparazzi-dev</tt> package is installed the complete source code should be downloaded from the CVS repository. See the [http://savannah.nongnu.org/cvs/?group=paparazzi project page] at Savannah for more details. From the directory of your choice type:
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/paparazzi co paparazzi3
This will download all of the code and install it into <tt>paparazzi3/</tt>

If you cannot use the CVS install, dayly updated tarballs can also be fetched from the [[Downloads|Downloads]] page.

== Launching the Software ==

If you are using the <tt>paparazzi-bin</tt> package or the Live-CD, just launch the <tt>paparazzi</tt> binary application and you will be guided through the installation of your personal configuration files.

If you are using the source code, the first step is to compile it. From the <tt>paparazzi3</tt> directory (<tt>cd paparazzi3</tt>), run

make

You will have to run these command after each update of the source (<tt>cvs update</tt> command).
Launch the software from the <tt>paparazzi3</tt> directory with

./paparazzi

From the [[Paparazzi_Center|Paparazzi Center]] interface, select the ''MJ5'' aircraft, select the ''sim'' target and ''Build'' it. Then ''Execute'' the ''Simulation'' session.

If ('''and only if''') you want to directly launch some Paparazzi agents (the ''Tools'' of the [[Paparazzi_Center|Paparazzi Center]]), without using the Paparazzi Center, you must have the Paparazzi source and home environment variables set correctly in your shell. These variables can be automatically set in your shell by adding the following lines to your .bashrc file:
{{Box Code|/home/your_username/.bashrc|
export PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
export PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''
}}
If you wish to manually set the env variables (i.e. when compiling a backup copy of your code in a different folder) execute the following command from the folder you wish to set as your active paparazzi folder:
export PAPARAZZI_HOME=`pwd`;export PAPARAZZI_SRC=`pwd`
Verify that your variables are set correctly with the following command:
env | grep PAPARAZZI
which should return the following:
PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''

== Setting access rights for USB download ==

This is required to flash the Paparazzi-boards via USB. For details, see [[Compiling]].

For USB download as non root you need permission to access the "raw" USB bus. You should be member of the ''plugdev'' group. The original user mentioned in the Linux install process usually is member, otherwise add your login using

sudo adduser <your login> plugdev

then logout and relogin. Tell the system to allow access by adding the following

# all (fake VID 0x7070) LPCUSB devices (access through libusb)
BUS=="usb", SYSFS{idVendor}=="7070", GROUP="plugdev"

through copying the file "10-paparazzi.rules" as root from $PAPARAZZI_HOME/conf/system/udev/rules/ to /etc/udev/rules.d/

== Software Updates ==
Paparazzi is a very rapidly evolving project and as such, you will find that variables and functions are frequently added, changed, or removed. Update your software with care and caution, and always test the functionality on the ground and in the air as some updates will affect tuning parameters. Your airframe file will not be updated by the CVS system and therefore any new or modified variable names will need to be added manually. The compiler will usually identify the problem variables at which point you can look at some of the most recent airframe files on the CVS to find the proper syntax. See the [[Compiling]] page for more help if needed.
 
That said, keeping your software up to date is easy with the CVS system. The system will compare all source code files with the server and update any that are needed, automatically merging any minor changes that you have incorporated along the way.

To download and automatically merge any updated source files, run the following command from your Paparazzi directory
cvs update -d
where the <tt>-d</tt> is needed to get any new directories.

After any CVS update or source code modification the code can be recompiled from ''your paparazzi3 directory'' with the following command:

make

The ''make'' command will only recompile portions of the software where changed have been detected. If it does not behave as expected you can deleted all compiled files and recompile from scratch with the following commands:

make clean
make

See the [[Compiling]] page for more info.

Users making changes to their code structure may prefer to have more control over the updating and merging process and may wish to install and use '''tkcvs''' instead which provides highlighted comparisons of any files that differ between your code and the CVS server and allows for a file by file update.

To update your Linux distribution as well as any dependencies of Paparazzi (seldom necessary), run the following as root:
apt-get update
apt get upgrade

== LiveCd ==

The LiveCD is an easy way to test Paparazzi: no installation is required and no changes are made to your computer. Simply burn the image as a boot CD and reboot! The LiveCD includes Linux and the complete paparazzi binary package (code source, tools and cross compilers). It is intended for demonstration only and not frequently updated but it contains the complete system and can store changed files on a pen drive or compressed file on your hard drive so that it can compile, flash, and operate any aircraft, albeit slowly.

The CD image is available from the [[Downloads|Downloads]] page.

The Paparazzi demo is launchable on the Live CD from the Paparazzi icon.

Knoppix allows for all the user data to be saved on a hard disk partition (most file systems are supported) or on a removable device (typically a USB pendrive). Note that this action is not destructive: the user data tree is compressed and stored on your file system as a single file (<tt>knoppix.img</tt>).
* From the Knoppix menu (second from bottom left), choose '''Configure''', '''Create a persistent KNOPPIX disk image'''
* Choose your media (be sure to connect your USB pendrive before booting!)
* Choose if you want an encrypted filesystem (to protect your flight plan designed for the next MAV competition :-) )
* Choose the size of your home directory (100Mb is recommended)
On the next reboot, this saved state will be automatically located and loaded.

Using this persistent feature, the Paparazzix Live CD can really be used to configure, simulate and fly an aircraft with the Paparazzi system.

The Live CD can also be used to install a Debian system on the hard disk, using the <tt>knoppix-installer</tt> command. Be sure to backup the hard disk before trying ...

[[Image:Lightscribe_CD_Cover_1.JPG|thumb|320px|LightScribe CD Cover]] A LiveCD needs some looks... In color or in LightScribe format, your CD will always look cool.
Get the PDF version for download here [http://paparazzi.enac.fr/wiki_images/Lightscribe_CD_Cover_1.pdf LightScribe CD Cover 1].

The LightScribe version is in Nero Cover Design format (.ncd) and it's here for download [http://paparazzi.enac.fr/wiki_images/Lightscribe_CD_Cover_1.zip LightScribe CD Cover 1]

File:Lightscribe CD Cover 1.zip

2008-02-09T22:34:17Z

Muralha:

Installation/Linux

2008-02-09T22:25:45Z

Muralha: /* LiveCd */

Precompiled binaries can be downloaded and executed with the ''paparazzi-bin'' package but to maintain the power and flexibility of open-source code, most operations within Paparazzi involve recompilation of autopilot and/or ground station code. Therefore the typical installation requires all of the necessary C and OCaml compilers as well as some XML and [http://www.tls.cena.fr/products/ivy/ Ivy] handlers. These tools are provided by the ''paparazzi-dev'' package.

The Paparazzi sources are hosted by [http://savannah.nongnu.org/cvs/?group=paparazzi Savannah].

The Paparazzi packages are hosted at the [http://www.recherche.enac.fr/paparazzi/debian ENAC repository].

== Installation on Debian based distributions ==

Paparazzi is packaged for Debian as well as all of its dependencies. The [http://www.recherche.enac.fr/paparazzi/debian repository] hosted at ENAC holds their latest version.

=== Installation from the Command Line===
Just add the following line to your repository list (/etc/apt/sources.list). Replace etch by sarge (oldstable distribution) or sid (unstable distribution) if needed. Note: It is no longer required to specify both sarge and etch.
{{Box Code|/etc/apt/sources.list|
deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> etch main
}}
Then, update your sources and install the precompiled binaries
apt-get update
apt-get install paparazzi-bin
or the dependencies needed for recompiling from the source (dev), and the cross-compiler (arm7) :
apt-get update
apt-get install paparazzi-dev
apt-get install paparazzi-arm7
Note: It is not recommended to install both <tt>paparazzi-bin</tt> and <tt>paparazzi-dev</tt>. While the bin package is self-contained and should be sufficient for users who do not want to patch the code, the dev meta-package provides only the tools to compile the source code which must be separately downloaded, from an archive or the CVS repository.

Note: Installation works fine on the Ubuntu 7.10 distribution (using the etch distro).

==== Optional/Obsolete Packages ====
Users of older AVR based boards will also need the paparazzi-avr package.

==== Extra for Ubuntu 7.04 and 7.10 ====

The Braille TTY driver interferes with FTDI USB Serial adapters and should be removed:

sudo apt-get remove brltty

=== Installation thru Synaptic Package Manager ===
* Launch ''Synaptic Package Manager'' (''Applications/System'' Tools Menu)
* In '''Settings/Repositories''', add a new repository on URI = '''<nowiki>http://paparazzi.enac.fr/debian</nowiki>''', Distribution = '''etch''' (or '''sarge''' or '''sid'''), Section = '''main'''
* Search for <tt>paparazzi-bin</tt>, <tt>paparazzi-dev</tt>, and <tt>paparazzi-arm7</tt> packages (use the ''Search'' button)
* Mark them for installation (right-click on package names)
* Left-click on ''Apply''

== Manual Installation of Individual Packages ==
Users of other Linux flavors or anyone needing manual control of each individual package can install them independently. The list of dependencies of the Debian package is located in the [http://cvs.savannah.gnu.org/viewvc/paparazzi/paparazzi3/debian/control.etch?revision=1.16&view=markup <tt> debian/control.etch</tt>] file and may help users of other distributions.

The binary packages and some corresponding source tarballs can be downloaded from

http://paparazzi.enac.fr/debian/dists/etch/main/binary-i386/

For distributions using RPM packaging, the [http://packages.debian.org/unstable/source/alien alien] tool can be used to translate a .deb package into a .rpm package.

For Fedora (Core8) users, you can install the following packages from standard repository:
* ocaml.i386
* ocaml-camlimages-devel.i386
* ocaml-lablgtk-devel.i386
* ocaml-xml-light-devel.i386
* boa.i386
* libgnomecanvas-devel.i386
* libusb-devel.i386
* pcre-devel.i386
* arm-gp2x-linux-gcc.i386
* arm-gp2x-linux-binutils.i386
* glade2.i386
* and gcc, make, cvs, gnuplot, imagemagik...

Then you need [http://packages.debian.org/unstable/source/alien alien] tool to convert packages from the paparazzi repository:
* ivy-c
* ivy-c-dev
* ivy-ocaml (WARNING: debian and fedora have different path for ocaml (/usr/lib/ocaml/<version> vs. /usr/lib/ocaml), so you need to move by hand the files in /usr/lib/ocaml/<version> to /usr/lib/ocaml)
* lpc21isp

== Installing the Source Code (not needed with paparazzi-bin) ==
After the <tt>paparazzi-dev</tt> package is installed the complete source code should be downloaded from the CVS repository. See the [http://savannah.nongnu.org/cvs/?group=paparazzi project page] at Savannah for more details. From the directory of your choice type:
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/paparazzi co paparazzi3
This will download all of the code and install it into <tt>paparazzi3/</tt>

If you cannot use the CVS install, dayly updated tarballs can also be fetched from the [[Downloads|Downloads]] page.

== Launching the Software ==

If you are using the <tt>paparazzi-bin</tt> package or the Live-CD, just launch the <tt>paparazzi</tt> binary application and you will be guided through the installation of your personal configuration files.

If you are using the source code, the first step is to compile it. From the <tt>paparazzi3</tt> directory (<tt>cd paparazzi3</tt>), run

make

You will have to run these command after each update of the source (<tt>cvs update</tt> command).
Launch the software from the <tt>paparazzi3</tt> directory with

./paparazzi

From the [[Paparazzi_Center|Paparazzi Center]] interface, select the ''MJ5'' aircraft, select the ''sim'' target and ''Build'' it. Then ''Execute'' the ''Simulation'' session.

If ('''and only if''') you want to directly launch some Paparazzi agents (the ''Tools'' of the [[Paparazzi_Center|Paparazzi Center]]), without using the Paparazzi Center, you must have the Paparazzi source and home environment variables set correctly in your shell. These variables can be automatically set in your shell by adding the following lines to your .bashrc file:
{{Box Code|/home/your_username/.bashrc|
export PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
export PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''
}}
If you wish to manually set the env variables (i.e. when compiling a backup copy of your code in a different folder) execute the following command from the folder you wish to set as your active paparazzi folder:
export PAPARAZZI_HOME=`pwd`;export PAPARAZZI_SRC=`pwd`
Verify that your variables are set correctly with the following command:
env | grep PAPARAZZI
which should return the following:
PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''

== Setting access rights for USB download ==

This is required to flash the Paparazzi-boards via USB. For details, see [[Compiling]].

For USB download as non root you need permission to access the "raw" USB bus. You should be member of the ''plugdev'' group. The original user mentioned in the Linux install process usually is member, otherwise add your login using

sudo adduser <your login> plugdev

then logout and relogin. Tell the system to allow access by adding the following

# all (fake VID 0x7070) LPCUSB devices (access through libusb)
BUS=="usb", SYSFS{idVendor}=="7070", GROUP="plugdev"

through copying the file "10-paparazzi.rules" as root from $PAPARAZZI_HOME/conf/system/udev/rules/ to /etc/udev/rules.d/

== Software Updates ==
Paparazzi is a very rapidly evolving project and as such, you will find that variables and functions are frequently added, changed, or removed. Update your software with care and caution, and always test the functionality on the ground and in the air as some updates will affect tuning parameters. Your airframe file will not be updated by the CVS system and therefore any new or modified variable names will need to be added manually. The compiler will usually identify the problem variables at which point you can look at some of the most recent airframe files on the CVS to find the proper syntax. See the [[Compiling]] page for more help if needed.
 
That said, keeping your software up to date is easy with the CVS system. The system will compare all source code files with the server and update any that are needed, automatically merging any minor changes that you have incorporated along the way.

To download and automatically merge any updated source files, run the following command from your Paparazzi directory
cvs update -d
where the <tt>-d</tt> is needed to get any new directories.

After any CVS update or source code modification the code can be recompiled from ''your paparazzi3 directory'' with the following command:

make

The ''make'' command will only recompile portions of the software where changed have been detected. If it does not behave as expected you can deleted all compiled files and recompile from scratch with the following commands:

make clean
make

See the [[Compiling]] page for more info.

Users making changes to their code structure may prefer to have more control over the updating and merging process and may wish to install and use '''tkcvs''' instead which provides highlighted comparisons of any files that differ between your code and the CVS server and allows for a file by file update.

To update your Linux distribution as well as any dependencies of Paparazzi (seldom necessary), run the following as root:
apt-get update
apt get upgrade

== LiveCd ==

The LiveCD is an easy way to test Paparazzi: no installation is required and no changes are made to your computer. Simply burn the image as a boot CD and reboot! The LiveCD includes Linux and the complete paparazzi binary package (code source, tools and cross compilers). It is intended for demonstration only and not frequently updated but it contains the complete system and can store changed files on a pen drive or compressed file on your hard drive so that it can compile, flash, and operate any aircraft, albeit slowly.

The CD image is available from the [[Downloads|Downloads]] page.

The Paparazzi demo is launchable on the Live CD from the Paparazzi icon.

Knoppix allows for all the user data to be saved on a hard disk partition (most file systems are supported) or on a removable device (typically a USB pendrive). Note that this action is not destructive: the user data tree is compressed and stored on your file system as a single file (<tt>knoppix.img</tt>).
* From the Knoppix menu (second from bottom left), choose '''Configure''', '''Create a persistent KNOPPIX disk image'''
* Choose your media (be sure to connect your USB pendrive before booting!)
* Choose if you want an encrypted filesystem (to protect your flight plan designed for the next MAV competition :-) )
* Choose the size of your home directory (100Mb is recommended)
On the next reboot, this saved state will be automatically located and loaded.

Using this persistent feature, the Paparazzix Live CD can really be used to configure, simulate and fly an aircraft with the Paparazzi system.

The Live CD can also be used to install a Debian system on the hard disk, using the <tt>knoppix-installer</tt> command. Be sure to backup the hard disk before trying ...

[[Image:Lightscribe_CD_Cover_1.JPG|thumb|320px|LightScribe CD Cover]] A LiveCD needs some looks... In color or in LightScribe format, your CD will always look cool.
Get the PDF version for download here [http://paparazzi.enac.fr/wiki_images/Lightscribe_CD_Cover_1.pdf LightScribe CD Cover 1].

Installation/Linux

2008-02-09T22:07:52Z

Muralha: /* LiveCd */

Precompiled binaries can be downloaded and executed with the ''paparazzi-bin'' package but to maintain the power and flexibility of open-source code, most operations within Paparazzi involve recompilation of autopilot and/or ground station code. Therefore the typical installation requires all of the necessary C and OCaml compilers as well as some XML and [http://www.tls.cena.fr/products/ivy/ Ivy] handlers. These tools are provided by the ''paparazzi-dev'' package.

The Paparazzi sources are hosted by [http://savannah.nongnu.org/cvs/?group=paparazzi Savannah].

The Paparazzi packages are hosted at the [http://www.recherche.enac.fr/paparazzi/debian ENAC repository].

== Installation on Debian based distributions ==

Paparazzi is packaged for Debian as well as all of its dependencies. The [http://www.recherche.enac.fr/paparazzi/debian repository] hosted at ENAC holds their latest version.

=== Installation from the Command Line===
Just add the following line to your repository list (/etc/apt/sources.list). Replace etch by sarge (oldstable distribution) or sid (unstable distribution) if needed. Note: It is no longer required to specify both sarge and etch.
{{Box Code|/etc/apt/sources.list|
deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> etch main
}}
Then, update your sources and install the precompiled binaries
apt-get update
apt-get install paparazzi-bin
or the dependencies needed for recompiling from the source (dev), and the cross-compiler (arm7) :
apt-get update
apt-get install paparazzi-dev
apt-get install paparazzi-arm7
Note: It is not recommended to install both <tt>paparazzi-bin</tt> and <tt>paparazzi-dev</tt>. While the bin package is self-contained and should be sufficient for users who do not want to patch the code, the dev meta-package provides only the tools to compile the source code which must be separately downloaded, from an archive or the CVS repository.

Note: Installation works fine on the Ubuntu 7.10 distribution (using the etch distro).

==== Optional/Obsolete Packages ====
Users of older AVR based boards will also need the paparazzi-avr package.

==== Extra for Ubuntu 7.04 and 7.10 ====

The Braille TTY driver interferes with FTDI USB Serial adapters and should be removed:

sudo apt-get remove brltty

=== Installation thru Synaptic Package Manager ===
* Launch ''Synaptic Package Manager'' (''Applications/System'' Tools Menu)
* In '''Settings/Repositories''', add a new repository on URI = '''<nowiki>http://paparazzi.enac.fr/debian</nowiki>''', Distribution = '''etch''' (or '''sarge''' or '''sid'''), Section = '''main'''
* Search for <tt>paparazzi-bin</tt>, <tt>paparazzi-dev</tt>, and <tt>paparazzi-arm7</tt> packages (use the ''Search'' button)
* Mark them for installation (right-click on package names)
* Left-click on ''Apply''

== Manual Installation of Individual Packages ==
Users of other Linux flavors or anyone needing manual control of each individual package can install them independently. The list of dependencies of the Debian package is located in the [http://cvs.savannah.gnu.org/viewvc/paparazzi/paparazzi3/debian/control.etch?revision=1.16&view=markup <tt> debian/control.etch</tt>] file and may help users of other distributions.

The binary packages and some corresponding source tarballs can be downloaded from

http://paparazzi.enac.fr/debian/dists/etch/main/binary-i386/

For distributions using RPM packaging, the [http://packages.debian.org/unstable/source/alien alien] tool can be used to translate a .deb package into a .rpm package.

For Fedora (Core8) users, you can install the following packages from standard repository:
* ocaml.i386
* ocaml-camlimages-devel.i386
* ocaml-lablgtk-devel.i386
* ocaml-xml-light-devel.i386
* boa.i386
* libgnomecanvas-devel.i386
* libusb-devel.i386
* pcre-devel.i386
* arm-gp2x-linux-gcc.i386
* arm-gp2x-linux-binutils.i386
* glade2.i386
* and gcc, make, cvs, gnuplot, imagemagik...

Then you need [http://packages.debian.org/unstable/source/alien alien] tool to convert packages from the paparazzi repository:
* ivy-c
* ivy-c-dev
* ivy-ocaml (WARNING: debian and fedora have different path for ocaml (/usr/lib/ocaml/<version> vs. /usr/lib/ocaml), so you need to move by hand the files in /usr/lib/ocaml/<version> to /usr/lib/ocaml)
* lpc21isp

== Installing the Source Code (not needed with paparazzi-bin) ==
After the <tt>paparazzi-dev</tt> package is installed the complete source code should be downloaded from the CVS repository. See the [http://savannah.nongnu.org/cvs/?group=paparazzi project page] at Savannah for more details. From the directory of your choice type:
cvs -z3 -d:pserver:anonymous@cvs.savannah.nongnu.org:/sources/paparazzi co paparazzi3
This will download all of the code and install it into <tt>paparazzi3/</tt>

If you cannot use the CVS install, dayly updated tarballs can also be fetched from the [[Downloads|Downloads]] page.

== Launching the Software ==

If you are using the <tt>paparazzi-bin</tt> package or the Live-CD, just launch the <tt>paparazzi</tt> binary application and you will be guided through the installation of your personal configuration files.

If you are using the source code, the first step is to compile it. From the <tt>paparazzi3</tt> directory (<tt>cd paparazzi3</tt>), run

make

You will have to run these command after each update of the source (<tt>cvs update</tt> command).
Launch the software from the <tt>paparazzi3</tt> directory with

./paparazzi

From the [[Paparazzi_Center|Paparazzi Center]] interface, select the ''MJ5'' aircraft, select the ''sim'' target and ''Build'' it. Then ''Execute'' the ''Simulation'' session.

If ('''and only if''') you want to directly launch some Paparazzi agents (the ''Tools'' of the [[Paparazzi_Center|Paparazzi Center]]), without using the Paparazzi Center, you must have the Paparazzi source and home environment variables set correctly in your shell. These variables can be automatically set in your shell by adding the following lines to your .bashrc file:
{{Box Code|/home/your_username/.bashrc|
export PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
export PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''
}}
If you wish to manually set the env variables (i.e. when compiling a backup copy of your code in a different folder) execute the following command from the folder you wish to set as your active paparazzi folder:
export PAPARAZZI_HOME=`pwd`;export PAPARAZZI_SRC=`pwd`
Verify that your variables are set correctly with the following command:
env | grep PAPARAZZI
which should return the following:
PAPARAZZI_HOME<nowiki>=</nowiki>''your paparazzi3 directory''
PAPARAZZI_SRC<nowiki>=</nowiki>''your paparazzi3 directory''

== Setting access rights for USB download ==

This is required to flash the Paparazzi-boards via USB. For details, see [[Compiling]].

For USB download as non root you need permission to access the "raw" USB bus. You should be member of the ''plugdev'' group. The original user mentioned in the Linux install process usually is member, otherwise add your login using

sudo adduser <your login> plugdev

then logout and relogin. Tell the system to allow access by adding the following

# all (fake VID 0x7070) LPCUSB devices (access through libusb)
BUS=="usb", SYSFS{idVendor}=="7070", GROUP="plugdev"

through copying the file "10-paparazzi.rules" as root from $PAPARAZZI_HOME/conf/system/udev/rules/ to /etc/udev/rules.d/

== Software Updates ==
Paparazzi is a very rapidly evolving project and as such, you will find that variables and functions are frequently added, changed, or removed. Update your software with care and caution, and always test the functionality on the ground and in the air as some updates will affect tuning parameters. Your airframe file will not be updated by the CVS system and therefore any new or modified variable names will need to be added manually. The compiler will usually identify the problem variables at which point you can look at some of the most recent airframe files on the CVS to find the proper syntax. See the [[Compiling]] page for more help if needed.
 
That said, keeping your software up to date is easy with the CVS system. The system will compare all source code files with the server and update any that are needed, automatically merging any minor changes that you have incorporated along the way.

To download and automatically merge any updated source files, run the following command from your Paparazzi directory
cvs update -d
where the <tt>-d</tt> is needed to get any new directories.

After any CVS update or source code modification the code can be recompiled from ''your paparazzi3 directory'' with the following command:

make

The ''make'' command will only recompile portions of the software where changed have been detected. If it does not behave as expected you can deleted all compiled files and recompile from scratch with the following commands:

make clean
make

See the [[Compiling]] page for more info.

Users making changes to their code structure may prefer to have more control over the updating and merging process and may wish to install and use '''tkcvs''' instead which provides highlighted comparisons of any files that differ between your code and the CVS server and allows for a file by file update.

To update your Linux distribution as well as any dependencies of Paparazzi (seldom necessary), run the following as root:
apt-get update
apt get upgrade

== LiveCd ==

The LiveCD is an easy way to test Paparazzi: no installation is required and no changes are made to your computer. Simply burn the image as a boot CD and reboot! The LiveCD includes Linux and the complete paparazzi binary package (code source, tools and cross compilers). It is intended for demonstration only and not frequently updated but it contains the complete system and can store changed files on a pen drive or compressed file on your hard drive so that it can compile, flash, and operate any aircraft, albeit slowly.

The CD image is available from the [[Downloads|Downloads]] page.

The Paparazzi demo is launchable on the Live CD from the Paparazzi icon.

Knoppix allows for all the user data to be saved on a hard disk partition (most file systems are supported) or on a removable device (typically a USB pendrive). Note that this action is not destructive: the user data tree is compressed and stored on your file system as a single file (<tt>knoppix.img</tt>).
* From the Knoppix menu (second from bottom left), choose '''Configure''', '''Create a persistent KNOPPIX disk image'''
* Choose your media (be sure to connect your USB pendrive before booting!)
* Choose if you want an encrypted filesystem (to protect your flight plan designed for the next MAV competition :-) )
* Choose the size of your home directory (100Mb is recommended)
On the next reboot, this saved state will be automatically located and loaded.

Using this persistent feature, the Paparazzix Live CD can really be used to configure, simulate and fly an aircraft with the Paparazzi system.

The Live CD can also be used to install a Debian system on the hard disk, using the <tt>knoppix-installer</tt> command. Be sure to backup the hard disk before trying ...

A LiveCD needs some looks... [[Image:Lightscribe_CD_Cover_1.JPG|thumb]]
Get the PDF version for download here [[Media:Lightscribe_CD_Cover_1.PDF]].

File:Lightscribe CD Cover 1.pdf

2008-02-09T21:59:42Z

Muralha:

File:Lightscribe CD Cover 1.JPG

2008-02-09T21:51:36Z

Muralha: