PaparazziUAV - User contributions [en]

Failsafe

2013-05-07T16:33:59Z

Jdyuen: /* 'Failsafe Switch' */

Paparazzi has several built-in failsafe features ranging from lowlevel to highlevel and from implied to optional.

On the lowest level, precise timing of the transmitter pulses creates safety that goes beyond traditional switches enabling safer use of old RC equipment.
On the highest level, the [[Flight_Plans#Exceptions|exceptions]] feature of the flight-plans allow for very flexible custom built failsafe features.

== FBW (Fly By Wire) ==

=== 'Failsafe Switch' ===

The lowest level of paparazzi is the FBW (Fly By Wire) controller that reads the RC, reads the autopilot commands and drives the servos based on the lowlevel failsafe options.

This is the 'switch' between '''manual''' or '''automatic''' modes. Therefore there is no need for another failsafe board. Indeed, the paparazzi FBW has evolved with so much intelligence that it is certainly safer than some and probably at least as safe as any other failsafe switches. This is amongst others (besides the highlevel validated code, separated process, ...) because paparazzi FBW unlike generic switches is given precise remote control information in its RC.xml. If you use a wrong type of transmitter (e.g. not the right amount of channels, or not the correct interval or sync pulse length) then even when on the same frequency the FBW will not listen to the commands. Also, if 2 transmitters are on the same frequency, then the chance of both signals together still being read as valid is very small. (This does NOT mean you can fly with 2 planes on the same frequency however. This only means that in this catastrophic scenario paparazzi does a pretty good job in delaying disaster from happening. )

Be aware that there exist many failsafe switches that use a pulse of the RC (e.g. channel 5) to switch
between autopilot or RC. When using analog RC equipment or any equipment that does not have correctly
programmed failsafe servo values this is very unsafe as whenever the RC is out of range the switch will
start switching back and forth putting the UAV out of control even if the autpilot is perfectly OK.

CAUTION! Common receivers today (especially 2.4GHz receivers) has own failsafe mode(s). Three mode are used in most cases:

# No failsafe: the receiver will switch off servo sinals in case of RC connection lost. Paparazzi own failsafe will be activated in case of RC connection lost.
# Last position: the receiver will keep the last valid servo positions in case of RC connection lost. Paparazzi own failsafe will NOT be activated. (The autopilot will not have information on RC signal lost.)
# Preset servo positions: the receiver will switch servo sinals to a preset value in case of RC connection lost. This values should be set directly in the receiver. (Read manual.) Paparazzi own failsafe will not be activated. BUT! If you set the failsafe value of the channel used for Mode control(Manual/Auto1/Auto2) to the value which commands Auto2, then paparazzi will switch automaticaly to Auto2 mode in case of RC connection lost.

=== FBW logic ===

* RC GOOD: listen to the MODE switch on the Transmitter (this means whenever the remote control is close enough the pilot has the final word)
* RC BAD: go to automatic mode (see further on for handling of automatic modes)
* RC BAD AND AUTOPILOT DATA TIMEOUT: failsafe command values from airframe configuration XML (do not omit to fill in useful failsafe values in the command section; usually slight pitch up for minimal speed, ailerons neutral in order not to roll inverted and of course throttle down: it is not recommended to try to make turns here with aileron deflections. A small rudder deflection on the other hand is recommended when available )

== AP (AutoPilot) ==

=== Home mode ===

The HOME mode is a failsafe mode where the standard navigation (own flightplan) is suspended and the aircraft
flies a circle around the HOME waypoint at a safe altitude (''security_height'' attribute in your flight-plan). This mode is triggered on different events.
Leaving this mode is done by clicking on the red HOME text in the GCS.

==== Too far from HOME ====

Home mode is triggered if the distance to the HOME waypoint is greater than a threshold ('''max_dist_from_home''' attribute) set in the
fight-plan (displayed as a circle on the GCS map).

==== RC link failure while manual or AUTO1 ====

Home mode is triggered if RC uplink is lost in '''MANUAL''' or '''AUTO 1''' modes.

* When '''MANUAL''' the manual mode is restored as soon as RC link is restored as expected.
* However: In '''AUTO 1''' mode, one must manually leave the HOME mode using the GCS

! Word of caution with respect to '''AUTO1''':
When flying auto1 with a lot of RC interference (which is not recommended anyway), be prepared that the plane might enter HOME mode.
Also, do not be tempted to fly far away in auto1 mode (possibly out of RC range) without a fully tuned auto2 autopilot or sufficient visual contact to allow manual control. As soon as you are so far that RC packets get lost, paparazzi will switch to HOME and will stay in HOME until you choose MANUAL of re-enable AUTO1 on the GCS !

===== Setting RC lost mode =====

By default when RC is lost (in Manual or Auto1) HOME mode is triggered, you can change this behaviour by setting the RC_LOST_MODE:

<define name="RC_LOST_MODE" value="PPRZ_MODE_AUTO2"/>

In this example RC_LOST_MODE is set to AUTO2, which can be useful if you experience glitches on your RC on the mode channel and want the aircraft to continue the mission instead of triggering HOME mode. '''BUT''' only use this if you have AUTO2 navigation set up properly and everything is initialized correctly! Another scenario to set this value is if you will fly out of your RC range in a long range mission.

You can disable HOME mode locking by adding the following line in your airframe file:

<define name="UNLOCKED_HOME_MODE" value="TRUE"/>

Then you can restore from HOME mode using the RC and do not need to do this on the GCS if in AUTO1.

'''Caution:''' Use these two settings with care, as they might deteriorate the failsafe security of your aircraft.

=== Kill mode ===

In this mode the throttle is killed (this is the default mode when switching on the autopilot). You can enter this mode manually with the kill button (with confirmation). Kill mode is also triggered in the following cases:

==== Catastrophic battery level ====

If the battery level goes under the catastrophic low level (defined in the airframe file)

==== Way too far from HOME ====

The plane goes into kill mode if it is too far away from the HOME waypoint. You can configure this '''KILL_MODE_DISTANCE''' in your airframe file:

<section name="MISC">
...
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
...
</section>

In this example it is set to 1.5 times the '''max_dist_from_home''' (attribute set in your flight plan).

=== GPS signal lost ===

In this mode, the autopilot uses the failsafe roll, pitch and throttle settings defined in the airframe file. It is recommended to disable throttle and make a shallow turn at low flight speed. When barometric information is available and compass heading information, it is recommended to disable this safety mode and train the GCS operator to bring the plane home on heading and altitude only.

Do not mix up the <commands> failsafe_value and the <section name="FAILSAFE" prefix="FAILSAFE_"> default values. The first result in fixed servo positions with the plane totally out of control, while the latter still involve the innerloop to stabilize the plane.

=== Lost datalink communication (optional) ===

This can be done via the a flight-plan exception, e.g. go to the Standby block after 30 seconds:
In your flightplan.xml:
<source lang="xml">
<header>
#include "subsystems/datalink/datalink.h"
</header>
...
<exceptions>
...
<exception cond="datalink_time > 30" deroute="Standby"/>
</exceptions>
</source>

=== Outside mission boundary (optional) ===

Also use exceptions and/or [[Flight_Plans#Call|function calls]] for this.

For an example see ''EMAV2009_safety.xml'' in the directory ''conf/flight_plans'' is an example of a safety procedure that can be included in other flight-plans.
It uses two [[Flight_Plans#Sectors|sectors]] defined in ''EMAV2009_data.xml'', a smaller Green "soft boundary" and a hard boundary defined by the Red sector.
<pre>
<procedure>
<exceptions>
<exception cond="Or(! InsideGreen(GetPosX(), GetPosY()), GetPosAlt() > ground_alt + 150)" deroute="Center"/>
</exceptions>

<blocks>
<block name="Center" pre_call="if (!InsideRed(GetPosX(), GetPosY())) NavKillThrottle();">
<circle wp="_CENTER" radius="DEFAULT_CIRCLE_RADIUS"/>
</block>
</blocks>

</procedure>
</pre>
The first exception deroutes the plane to the Center block below it, if it is outside the Green [[Flight_Plans#Sectors|sector]] or higher than 150m over ground.
While in the Center block the statement in the pre_call function gets evaluated each time, if the plane is now also outside of the Red sector throttle is killed.

[[Category:Software]] [[Category:User_Documentation]]

Failsafe

2013-05-07T16:31:03Z

Jdyuen: /* Setting RC lost mode */

Paparazzi has several built-in failsafe features ranging from lowlevel to highlevel and from implied to optional.

On the lowest level, precise timing of the transmitter pulses creates safety that goes beyond traditional switches enabling safer use of old RC equipment.
On the highest level, the [[Flight_Plans#Exceptions|exceptions]] feature of the flight-plans allow for very flexible custom built failsafe features.

== FBW (Fly By Wire) ==

=== 'Failsafe Switch' ===

The lowest level of paparazzi is the FBW (Fly By Wire) controller that reads the RC, reads the autopilot commands and drives the servo's based on the lowlevel failsafe options.

This is the 'switch' between '''manual''' or '''automatic''' modes. Therefor there is no need for an other failsafe board. Indeed, the paparazzi FBW has evolved with so much intelligence that it is certainly safer than some and probably at least as safe as any other failsafe switches. This is amongst others (besides the highlevel validated code, separated process, ...) because paparazzi FBW unlike generic switches is given precise remote control information in it's RC.xml. If you use a wrong type of transmitter (e.g. not the right amount of channels, or not the correct interval or sync pulse length) than even when on the same frequency the FBW will not listen to the commands. Also, when 2 transmitters should be on the same frequency, then the chance of both signals together still being read as valid is very small. (This does NOT mean you can fly with 2 planes on the same frequency however. This only means that in this catastrophic scenario paparazzi does a pretty good job in delaying disaster from happening. )

Be aware that there exist many failsafe switches that use a pulse of the RC (e.g. channel 5) to switch
between autopilot or RC. When using analog RC equipment or any equipment that does not have correctly
programmed failsafe servo values this is very unsafe as whenever the RC is out of range the switch will
start switching back and forth putting the UAV out of control even if the autpilot is perfectly OK.

CAUTION! Common receivers today (especially 2.4GHz receivers) has own failsafe mode(s). Three mode are used in most cases:

# No failsafe: the receiver will switch off servo sinals in case of RC connection lost. Paparazzi own failsafe will be activated in case of RC connection lost.
# Last position: the receiver will keep the last valid servo positions in case of RC connection lost. Paparazzi own failsafe will NOT be activated. (The autopilot will not have information on RC signal lost.)
# Preset servo positions: the receiver will switch servo sinals to a preset value in case of RC connection lost. This values should be set directly in the receiver. (Read manual.) Paparazzi own failsafe will not be activated. BUT! If you set the failsafe value of the channel used for Mode control(Manual/Auto1/Auto2) to the value which commands Auto2, then paparazzi will switch automaticaly to Auto2 mode in case of RC connection lost.

=== FBW logic ===

* RC GOOD: listen to the MODE switch on the Transmitter (this means whenever the remote control is close enough the pilot has the final word)
* RC BAD: go to automatic mode (see further on for handling of automatic modes)
* RC BAD AND AUTOPILOT DATA TIMEOUT: failsafe command values from airframe configuration XML (do not omit to fill in useful failsafe values in the command section; usually slight pitch up for minimal speed, ailerons neutral in order not to roll inverted and of course throttle down: it is not recommended to try to make turns here with aileron deflections. A small rudder deflection on the other hand is recommended when available )

== AP (AutoPilot) ==

=== Home mode ===

The HOME mode is a failsafe mode where the standard navigation (own flightplan) is suspended and the aircraft
flies a circle around the HOME waypoint at a safe altitude (''security_height'' attribute in your flight-plan). This mode is triggered on different events.
Leaving this mode is done by clicking on the red HOME text in the GCS.

==== Too far from HOME ====

Home mode is triggered if the distance to the HOME waypoint is greater than a threshold ('''max_dist_from_home''' attribute) set in the
fight-plan (displayed as a circle on the GCS map).

==== RC link failure while manual or AUTO1 ====

Home mode is triggered if RC uplink is lost in '''MANUAL''' or '''AUTO 1''' modes.

* When '''MANUAL''' the manual mode is restored as soon as RC link is restored as expected.
* However: In '''AUTO 1''' mode, one must manually leave the HOME mode using the GCS

! Word of caution with respect to '''AUTO1''':
When flying auto1 with a lot of RC interference (which is not recommended anyway), be prepared that the plane might enter HOME mode.
Also, do not be tempted to fly far away in auto1 mode (possibly out of RC range) without a fully tuned auto2 autopilot or sufficient visual contact to allow manual control. As soon as you are so far that RC packets get lost, paparazzi will switch to HOME and will stay in HOME until you choose MANUAL of re-enable AUTO1 on the GCS !

===== Setting RC lost mode =====

By default when RC is lost (in Manual or Auto1) HOME mode is triggered, you can change this behaviour by setting the RC_LOST_MODE:

<define name="RC_LOST_MODE" value="PPRZ_MODE_AUTO2"/>

In this example RC_LOST_MODE is set to AUTO2, which can be useful if you experience glitches on your RC on the mode channel and want the aircraft to continue the mission instead of triggering HOME mode. '''BUT''' only use this if you have AUTO2 navigation set up properly and everything is initialized correctly! Another scenario to set this value is if you will fly out of your RC range in a long range mission.

You can disable HOME mode locking by adding the following line in your airframe file:

<define name="UNLOCKED_HOME_MODE" value="TRUE"/>

Then you can restore from HOME mode using the RC and do not need to do this on the GCS if in AUTO1.

'''Caution:''' Use these two settings with care, as they might deteriorate the failsafe security of your aircraft.

=== Kill mode ===

In this mode the throttle is killed (this is the default mode when switching on the autopilot). You can enter this mode manually with the kill button (with confirmation). Kill mode is also triggered in the following cases:

==== Catastrophic battery level ====

If the battery level goes under the catastrophic low level (defined in the airframe file)

==== Way too far from HOME ====

The plane goes into kill mode if it is too far away from the HOME waypoint. You can configure this '''KILL_MODE_DISTANCE''' in your airframe file:

<section name="MISC">
...
<define name="KILL_MODE_DISTANCE" value="(1.5*MAX_DIST_FROM_HOME)"/>
...
</section>

In this example it is set to 1.5 times the '''max_dist_from_home''' (attribute set in your flight plan).

=== GPS signal lost ===

In this mode, the autopilot uses the failsafe roll, pitch and throttle settings defined in the airframe file. It is recommended to disable throttle and make a shallow turn at low flight speed. When barometric information is available and compass heading information, it is recommended to disable this safety mode and train the GCS operator to bring the plane home on heading and altitude only.

Do not mix up the <commands> failsafe_value and the <section name="FAILSAFE" prefix="FAILSAFE_"> default values. The first result in fixed servo positions with the plane totally out of control, while the latter still involve the innerloop to stabilize the plane.

=== Lost datalink communication (optional) ===

This can be done via the a flight-plan exception, e.g. go to the Standby block after 30 seconds:
In your flightplan.xml:
<source lang="xml">
<header>
#include "subsystems/datalink/datalink.h"
</header>
...
<exceptions>
...
<exception cond="datalink_time > 30" deroute="Standby"/>
</exceptions>
</source>

=== Outside mission boundary (optional) ===

Also use exceptions and/or [[Flight_Plans#Call|function calls]] for this.

For an example see ''EMAV2009_safety.xml'' in the directory ''conf/flight_plans'' is an example of a safety procedure that can be included in other flight-plans.
It uses two [[Flight_Plans#Sectors|sectors]] defined in ''EMAV2009_data.xml'', a smaller Green "soft boundary" and a hard boundary defined by the Red sector.
<pre>
<procedure>
<exceptions>
<exception cond="Or(! InsideGreen(GetPosX(), GetPosY()), GetPosAlt() > ground_alt + 150)" deroute="Center"/>
</exceptions>

<blocks>
<block name="Center" pre_call="if (!InsideRed(GetPosX(), GetPosY())) NavKillThrottle();">
<circle wp="_CENTER" radius="DEFAULT_CIRCLE_RADIUS"/>
</block>
</blocks>

</procedure>
</pre>
The first exception deroutes the plane to the Center block below it, if it is outside the Green [[Flight_Plans#Sectors|sector]] or higher than 150m over ground.
While in the Center block the statement in the pre_call function gets evaluated each time, if the plane is now also outside of the Red sector throttle is killed.

[[Category:Software]] [[Category:User_Documentation]]

Contact

2012-08-10T18:25:21Z

Jdyuen: /* Client Software */

Get in touch with active members of the group through any of the following means:

== Mailing List ==

The Paparazzi electronic mailing list is a special usage of email that allows for widespread distribution of information to many Paparazzi users. It is similar to a traditional mailing list — a list of names and addresses — as might be kept by an organization for sending publications to its members or customers, but typically refers to four things: a list of email addresses, the people ("subscribers") receiving mail at those addresses, the publications (e-mail messages) sent to those addresses, and a reflector, which is a single e-mail address that, when designated as the recipient of a message, will send a copy of that message to all of the subscribers. (Wikipedia)

Maybe get some answers already, browse the mailing list archives at: 
[http://lists.gnu.org/archive/html/paparazzi-devel/ http://lists.gnu.org/archive/html/paparazzi-devel/]

Or join the Paparazzi mailing list for burning new questions at: 
[http://lists.nongnu.org/mailman/listinfo/paparazzi-devel http://lists.nongnu.org/mailman/listinfo/paparazzi-devel]

After registering, you can send an e-mail to the entire group by using the address: paparazzi-devel@nongnu.org

Use the list wisely and it can help you getting answers to your questions. Once you learned about paparazzi, be nice and try to help out others in the future.

You can get the commit logs via email by joining the [http://lists.nongnu.org/mailman/listinfo/paparazzi-commits http://lists.nongnu.org/mailman/listinfo/paparazzi-commits] mailing list.

== The IRC Chat Channel ==
Network: Freenode
Network Host: irc.freenode.net
Channel: #paparazzi

On the '''freenode''' [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] server in the '''#paparazzi''' channel a dozen or so members are typically online. Stop by anytime and '''say hello''' to the group, but don't be discouraged by hours of inactivity at certain times of day.

The IRC conversations are also logged and available [http://colabti.org/irclogger/irclogger_logs/paparazzi here].

We also have an [[IRC_Bouncer|IRC bouncer]] running.

=== Web Based Access ===

You can use a [http://embed.mibbit.com/?server=irc.freenode.net&channel=%23paparazzi&noServerNotices=true web-based IRC portal] that makes it easy for people to jump in from any computer. Simply enter a unique ''nickname'', and '''say hello''' to the team! More active users will benefit from the power of conventional client software such as [http://www.xchat.org Xchat] or [http://www.mirc.com mIRC].

=== Client Software ===

A full featured IRC chat program is essential for active users. Download one of the many freeware/shareware IRC clients and put [irc://irc.freenode.net/#paparazzi irc://irc.freenode.net/#paparazzi] at the top of your favorites list!

* [http://www.xchat.org xchat-gnome] is a popular and easy to use application for Linux. To install run
sudo aptitude install xchat-gnome
* [http://www.silverex.org/download Xchat2] is a free version of Xchat for windows or download a [http://b0at.tx0.org/xchat/ XChat Windows build] or use closed source [http://www.mirc.com mIRC]
* [http://sourceforge.net/projects/xchataqua/ xchat-aqua] is an opensource free IRC client for OS-X

=== Usage ===

Choose '''FreeNode''' and some nicknames in the network list and click '''Edit''' to enter the '''#paparazzi''' channel and a Nicserv password. Follow the instructions below to register your chosen nickname and password on the network.

==== Registering on the Freenode IRC Network ====

Registering is optional but is required for private one-on-one chats. Private chats are useful for pasting large amounts of code back and forth without flooding the group or for any off-topic discussion you may wish to have. Commands in IRC begin with a forward slash '/'. Type these two commands into your IRC client to register and log on.

Select your own unique password and use it in place of ''<password>''. Make sure you are currently using the "nickname" that you would like to use.

/msg NickServ REGISTER <password>

You will now have registered your nickname to your hostmask (or IP address) and the Freenode IRC network will attempt to prevent others from using your nickname. You will need to identify yourself to the system now every time you log onto IRC with the command below. This can be added to the "perform" section of your software to be run automatically every time you log on.

/msg NickServ IDENTIFY <password>

These commands return output results as well, depending on what IRC client you are using to chat it may have appeared in either your main chat window or a separate server window where other server related messages appear. Check this window for confirmation.

Note: You may find that your IRC connection will occasionally be interrupted, leaving your nic floating on the server. When this happens the server will not let you log back on using the same nic until that nic has been dropped, usually within 30 minutes. The convention is to append an underscore to your original nic for temporary use.
'''Bold text'''

[[Category:Community]]

WeatherStationInterface

2012-08-10T17:59:46Z

Jdyuen: /* External Links */

= Weather Station Interface =

The weather station interface <tt>davis2ivy</tt> polls Davis VantagePro/VantagePro2 stations and broadcasts the current weather data (ambient pressure, temperature, wind speed and direction) over Paparazzi's message system.
Connect the station via a serial port.

<tt>davis2ivy</tt> may send messages with different aircraft IDs.
The simplest way is to use the ID of the actually flying aircraft, thus the messages will show up in the messages window and in the log file as if they were sent from that aircraft.
If you use another aircraft ID, you have to add the <tt>-a</tt> option to get the messages into the log file.

== Options ==
The program can be found in <tt>$PAPARAZZI_HOME/sw/ground_segment/misc</tt>.
* <tt>-a</tt> Send ALIVE message
* <tt>-b <bus></tt> Specify Ivy bus (default is 127.255.255.255:2010)
* <tt>-d <device></tt> Specify the weather station device (default is <tt>/dev/ttyUSB1</tt>)
* <tt>-i <number></tt> Specify the aircraft ID (default is 1)
* <tt>-s <number></tt> Specify the interval between station polls in seconds (default is 1)

== External Links ==
[http://www.davisnet.com/weather/products/vantage-pro-professional-weather-stations.asp Vantage Pro2 product page]

Data Logger

2012-08-09T20:40:19Z

Jdyuen: /* Option 3: Logomatic */

[[Image:sd_spi.jpg|thumb|micro SD card connected to SPI]]
This describes an external device that can be connected to the Paparazzi autopilot to store telemetry data to a mass storage medium on board the aircraft, e.g. an SD card (only non-SDHC cards). For now this is '''not''' done with the autopilot itself as the usage of a file system as well as possible lag you might get with a SD card (erase times) does not fit well with the real time nature of the used software scheduler. You need to use e.g. an additional TWOG.

== Mode of operation ==
The logger is connected between the autopilot and the modem. It stores all telemetry on a micro SD card when power is connected. At the end of the flight a button is pressed just before disconnecting the main battery to stop logging (other ways of stopping are not yet done, e.g. by telemetry message from the gcs or a battery buffered voltage-drop detection). When logging is stopped and the USB is connected the logger acts as USB mass storage device and the micro SD card content can be read with any PC supporting FAT file system. The telemetry data is converted to the standard .data and .log file with a Paparazzi tool. Logging can be started again through a long press of the button if USB was not connected.

== Hardware ==

We decided to use the well known LPC2148 to do the logging. That allows to use the Paparazzi configuration/tool chain and have a standard USB connection for read out with any PC. All designs have a STOP button. It has to be pressed to close the file and be able to read the data! The USB should be connected after the logger is stopped to prevent going into download mode when re-powered.

LED2 on: logging enabled, press button to stop
LED3 flashing: writing message to SD

LED2 flashing: logging stopped, connect USB to read out data or press button long to restart logging

LED1 on: USB mass storage enabled

=== Option 1: Paparazzi Logger HW ===

https://github.com/paparazzi/paparazzi-hardware/tree/master/controller/logger/v1.0

=== Option 2: TWOG ===

You can directly connect a micro SD card to a TWOG. Remember that micro SD cards do have a limited number of insertions and should not be plugged too often. The (micro) SD card is connected to the SPI1 of the TWOG following this scheme:

microSD TinyV2 SPI J3

8 nc
7 DO 5 MISO
6 GND 1 GND
5 CLK 7 SCK
4 Vcc 2 +3V3
3 DI 4 MOSI
2 CS 3 SSEL
1 nc

Looking onto the gold plated connector side of the microSD card:

###############
I 8
I 7
I 6
I 5
I 4
I 3
I 2
I 1
###### ##
\ I \
## ##

The start/stop button is connected to the BUTTON (P0.7) pin of the USB connector (J9). It is activated by pulling it low.

=== Option 3: Logomatic ===

There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board, just use

conf/airframes/logomatic.xml

Currently pprz data must be collected on UART0 for [[Data_Logger#Decoding|sd2log]] to work [20:40, 9 August 2012 (UTC)]

=== Option 4: OpenLog ===
If you don't want to add a complete TWOG or full-blown LPC-Board to you setup you can also use the Sparkfun [http://www.sparkfun.com/products/9530 OpenLog] board.
Take a look at [[Openlog|Openlog]].

== UART Connection ==
The two serial inputs LPC_RXD0 (J7) and RXD1 (J2) are used to receive data. The received data is not forwarded to TX0/1 by software (the UART TX pins are deactivated). If the logger is put in between Tiny and the modem the connection should be done with a wire so that a logger failure does not cause any data link issue.

== I2C Connection ==
tbd

== SPI Connection ==
tbd

== Configuration ==
The logger is defined just like an aircraft. Take the

conf/airframes/logger_sd.xml

as example. You can enable one or both UARTs for logging and have to set the serial speed

<configure name="UART0_BAUD" value="B9600" />
<configure name="UART1_BAUD" value="B9600" />

The message type can be switched between the PPRZ and the XBEE format

<configure name="LOG_MSG_FMT" value="LOG_PPRZ"/>
''or''
<configure name="LOG_MSG_FMT" value="LOG_XBEE"/>

The SD card can either be connected to SPI0 or SPI1

<configure name="SPI_CHANNEL" value="0" />
''or''
<configure name="SPI_CHANNEL" value="1" />

Now create a new A/C with the logger airframe. Although they will not be used, you still need to supply dummy files for Flight Plan, Settings, Radio and Telemetry.

== Decoding ==
The telemetry is written in the Paparazzi .tlm [[Messages_Format|format]] that adds a timestamp to each message. The logger starts with 00000000.TLM in the main folder of the SD and increases the number with each log session. Already used numbers will not be overwritten. This data can be converted back to the Paparazzi .log and .data format using sd2log (make sure [[Installation#Environment_Variables|environment variables]] are set before running pprz programs from the commandline)

me@home:~/media/usbstick$ ~/paparazzi3/sw/logalizer/sd2log 00000002.TLM
Renaming produced file ...
09_08_13__20_55_03_SD.data file produced
09_08_13__20_55_03_SD.log file produced
09_08_13__20_55_03_SD.tlm file saved

It creates timestamps from the .tlm and changes the filename to the take-off time if a GPS message with correct time was available in the file or the current local PC time if no GPS was available. The .log file will be re-created either from the current configuration (if still in existence) or the MD5-labeled files that are stored in var/conf each time you build an aircraft. All resulting files are stored in var/logs with an _SD extension.

[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Data Logger

2012-08-09T15:51:12Z

Jdyuen: /* Decoding */

[[Image:sd_spi.jpg|thumb|micro SD card connected to SPI]]
This describes an external device that can be connected to the Paparazzi autopilot to store telemetry data to a mass storage medium on board the aircraft, e.g. an SD card (only non-SDHC cards). For now this is '''not''' done with the autopilot itself as the usage of a file system as well as possible lag you might get with a SD card (erase times) does not fit well with the real time nature of the used software scheduler. You need to use e.g. an additional TWOG.

== Mode of operation ==
The logger is connected between the autopilot and the modem. It stores all telemetry on a micro SD card when power is connected. At the end of the flight a button is pressed just before disconnecting the main battery to stop logging (other ways of stopping are not yet done, e.g. by telemetry message from the gcs or a battery buffered voltage-drop detection). When logging is stopped and the USB is connected the logger acts as USB mass storage device and the micro SD card content can be read with any PC supporting FAT file system. The telemetry data is converted to the standard .data and .log file with a Paparazzi tool. Logging can be started again through a long press of the button if USB was not connected.

== Hardware ==

We decided to use the well known LPC2148 to do the logging. That allows to use the Paparazzi configuration/tool chain and have a standard USB connection for read out with any PC. All designs have a STOP button. It has to be pressed to close the file and be able to read the data! The USB should be connected after the logger is stopped to prevent going into download mode when re-powered.

LED2 on: logging enabled, press button to stop
LED3 flashing: writing message to SD

LED2 flashing: logging stopped, connect USB to read out data or press button long to restart logging

LED1 on: USB mass storage enabled

=== Option 1: Paparazzi Logger HW ===

https://github.com/paparazzi/paparazzi-hardware/tree/master/controller/logger/v1.0

=== Option 2: TWOG ===

You can directly connect a micro SD card to a TWOG. Remember that micro SD cards do have a limited number of insertions and should not be plugged too often. The (micro) SD card is connected to the SPI1 of the TWOG following this scheme:

microSD TinyV2 SPI J3

8 nc
7 DO 5 MISO
6 GND 1 GND
5 CLK 7 SCK
4 Vcc 2 +3V3
3 DI 4 MOSI
2 CS 3 SSEL
1 nc

Looking onto the gold plated connector side of the microSD card:

###############
I 8
I 7
I 6
I 5
I 4
I 3
I 2
I 1
###### ##
\ I \
## ##

The start/stop button is connected to the BUTTON (P0.7) pin of the USB connector (J9). It is activated by pulling it low.

=== Option 3: Logomatic ===

There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board, just use

conf/airframes/logomatic.xml

=== Option 4: OpenLog ===
If you don't want to add a complete TWOG or full-blown LPC-Board to you setup you can also use the Sparkfun [http://www.sparkfun.com/products/9530 OpenLog] board.
Take a look at [[Openlog|Openlog]].

== UART Connection ==
The two serial inputs LPC_RXD0 (J7) and RXD1 (J2) are used to receive data. The received data is not forwarded to TX0/1 by software (the UART TX pins are deactivated). If the logger is put in between Tiny and the modem the connection should be done with a wire so that a logger failure does not cause any data link issue.

== I2C Connection ==
tbd

== SPI Connection ==
tbd

== Configuration ==
The logger is defined just like an aircraft. Take the

conf/airframes/logger_sd.xml

as example. You can enable one or both UARTs for logging and have to set the serial speed

<configure name="UART0_BAUD" value="B9600" />
<configure name="UART1_BAUD" value="B9600" />

The message type can be switched between the PPRZ and the XBEE format

<configure name="LOG_MSG_FMT" value="LOG_PPRZ"/>
''or''
<configure name="LOG_MSG_FMT" value="LOG_XBEE"/>

The SD card can either be connected to SPI0 or SPI1

<configure name="SPI_CHANNEL" value="0" />
''or''
<configure name="SPI_CHANNEL" value="1" />

Now create a new A/C with the logger airframe. Although they will not be used, you still need to supply dummy files for Flight Plan, Settings, Radio and Telemetry.

== Decoding ==
The telemetry is written in the Paparazzi .tlm [[Messages_Format|format]] that adds a timestamp to each message. The logger starts with 00000000.TLM in the main folder of the SD and increases the number with each log session. Already used numbers will not be overwritten. This data can be converted back to the Paparazzi .log and .data format using sd2log (make sure [[Installation#Environment_Variables|environment variables]] are set before running pprz programs from the commandline)

me@home:~/media/usbstick$ ~/paparazzi3/sw/logalizer/sd2log 00000002.TLM
Renaming produced file ...
09_08_13__20_55_03_SD.data file produced
09_08_13__20_55_03_SD.log file produced
09_08_13__20_55_03_SD.tlm file saved

It creates timestamps from the .tlm and changes the filename to the take-off time if a GPS message with correct time was available in the file or the current local PC time if no GPS was available. The .log file will be re-created either from the current configuration (if still in existence) or the MD5-labeled files that are stored in var/conf each time you build an aircraft. All resulting files are stored in var/logs with an _SD extension.

[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Data Logger

2012-08-09T15:47:21Z

Jdyuen: /* Decoding */

[[Image:sd_spi.jpg|thumb|micro SD card connected to SPI]]
This describes an external device that can be connected to the Paparazzi autopilot to store telemetry data to a mass storage medium on board the aircraft, e.g. an SD card (only non-SDHC cards). For now this is '''not''' done with the autopilot itself as the usage of a file system as well as possible lag you might get with a SD card (erase times) does not fit well with the real time nature of the used software scheduler. You need to use e.g. an additional TWOG.

== Mode of operation ==
The logger is connected between the autopilot and the modem. It stores all telemetry on a micro SD card when power is connected. At the end of the flight a button is pressed just before disconnecting the main battery to stop logging (other ways of stopping are not yet done, e.g. by telemetry message from the gcs or a battery buffered voltage-drop detection). When logging is stopped and the USB is connected the logger acts as USB mass storage device and the micro SD card content can be read with any PC supporting FAT file system. The telemetry data is converted to the standard .data and .log file with a Paparazzi tool. Logging can be started again through a long press of the button if USB was not connected.

== Hardware ==

We decided to use the well known LPC2148 to do the logging. That allows to use the Paparazzi configuration/tool chain and have a standard USB connection for read out with any PC. All designs have a STOP button. It has to be pressed to close the file and be able to read the data! The USB should be connected after the logger is stopped to prevent going into download mode when re-powered.

LED2 on: logging enabled, press button to stop
LED3 flashing: writing message to SD

LED2 flashing: logging stopped, connect USB to read out data or press button long to restart logging

LED1 on: USB mass storage enabled

=== Option 1: Paparazzi Logger HW ===

https://github.com/paparazzi/paparazzi-hardware/tree/master/controller/logger/v1.0

=== Option 2: TWOG ===

You can directly connect a micro SD card to a TWOG. Remember that micro SD cards do have a limited number of insertions and should not be plugged too often. The (micro) SD card is connected to the SPI1 of the TWOG following this scheme:

microSD TinyV2 SPI J3

8 nc
7 DO 5 MISO
6 GND 1 GND
5 CLK 7 SCK
4 Vcc 2 +3V3
3 DI 4 MOSI
2 CS 3 SSEL
1 nc

Looking onto the gold plated connector side of the microSD card:

###############
I 8
I 7
I 6
I 5
I 4
I 3
I 2
I 1
###### ##
\ I \
## ##

The start/stop button is connected to the BUTTON (P0.7) pin of the USB connector (J9). It is activated by pulling it low.

=== Option 3: Logomatic ===

There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board, just use

conf/airframes/logomatic.xml

=== Option 4: OpenLog ===
If you don't want to add a complete TWOG or full-blown LPC-Board to you setup you can also use the Sparkfun [http://www.sparkfun.com/products/9530 OpenLog] board.
Take a look at [[Openlog|Openlog]].

== UART Connection ==
The two serial inputs LPC_RXD0 (J7) and RXD1 (J2) are used to receive data. The received data is not forwarded to TX0/1 by software (the UART TX pins are deactivated). If the logger is put in between Tiny and the modem the connection should be done with a wire so that a logger failure does not cause any data link issue.

== I2C Connection ==
tbd

== SPI Connection ==
tbd

== Configuration ==
The logger is defined just like an aircraft. Take the

conf/airframes/logger_sd.xml

as example. You can enable one or both UARTs for logging and have to set the serial speed

<configure name="UART0_BAUD" value="B9600" />
<configure name="UART1_BAUD" value="B9600" />

The message type can be switched between the PPRZ and the XBEE format

<configure name="LOG_MSG_FMT" value="LOG_PPRZ"/>
''or''
<configure name="LOG_MSG_FMT" value="LOG_XBEE"/>

The SD card can either be connected to SPI0 or SPI1

<configure name="SPI_CHANNEL" value="0" />
''or''
<configure name="SPI_CHANNEL" value="1" />

Now create a new A/C with the logger airframe. Although they will not be used, you still need to supply dummy files for Flight Plan, Settings, Radio and Telemetry.

== Decoding ==
The telemetry is written in the Paparazzi .tlm [[Messages_Format|format]] that adds a timestamp to each message. The logger starts with 00000000.TLM in the main folder of the SD and increases the number with each log session. Already used numbers will not be overwritten. This data can be converted back to the Paparazzi .log and .data format using sd2log (make sure environment variables are set before running pprz programs from the commandline: [[Installation#Environment_Variables]])

me@home:~/media/usbstick$ ~/paparazzi3/sw/logalizer/sd2log 00000002.TLM
Renaming produced file ...
09_08_13__20_55_03_SD.data file produced
09_08_13__20_55_03_SD.log file produced
09_08_13__20_55_03_SD.tlm file saved

It creates timestamps from the .tlm and changes the filename to the take-off time if a GPS message with correct time was available in the file or the current local PC time if no GPS was available. The .log file will be re-created either from the current configuration (if still in existence) or the MD5-labeled files that are stored in var/conf each time you build an aircraft. All resulting files are stored in var/logs with an _SD extension.

[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Data Logger

2012-06-19T21:56:19Z

Jdyuen: /* Configuration */

[[Image:sd_spi.jpg|thumb|micro SD card connected to SPI]]
This describes an external device that can be connected to the Paparazzi autopilot to store telemetry data to a mass storage medium on board the aircraft, e.g. an SD card (only non-SDHC cards). For now this is '''not''' done with the autopilot itself as the usage of a file system as well as possible lag you might get with a SD card (erase times) does not fit well with the real time nature of the used software scheduler. You need to use e.g. an additional TWOG.

== Mode of operation ==
The logger is connected between the autopilot and the modem. It stores all telemetry on a micro SD card when power is connected. At the end of the flight a button is pressed just before disconnecting the main battery to stop logging (other ways of stopping are not yet done, e.g. by telemetry message from the gcs or a battery buffered voltage-drop detection). When logging is stopped and the USB is connected the logger acts as USB mass storage device and the micro SD card content can be read with any PC supporting FAT file system. The telemetry data is converted to the standard .data and .log file with a Paparazzi tool. Logging can be started again through a long press of the button if USB was not connected.

== Hardware ==

We decided to use the well known LPC2148 to do the logging. That allows to use the Paparazzi configuration/tool chain and have a standard USB connection for read out with any PC. All designs have a STOP button. It has to be pressed to close the file and be able to read the data! The USB should be connected after the logger is stopped to prevent going into download mode when re-powered.

LED2 on: logging enabled, press button to stop
LED3 flashing: writing message to SD

LED2 flashing: logging stopped, connect USB to read out data or press button long to restart logging

LED1 on: USB mass storage enabled

=== Option 1: Paparazzi Logger HW ===

https://github.com/paparazzi/paparazzi-hardware/tree/master/controller/logger/v1.0

=== Option 2: TWOG ===

You can directly connect a micro SD card to a TWOG. Remember that micro SD cards do have a limited number of insertions and should not be plugged too often. The (micro) SD card is connected to the SPI1 of the TWOG following this scheme:

microSD TinyV2 SPI J3

8 nc
7 DO 5 MISO
6 GND 1 GND
5 CLK 7 SCK
4 Vcc 2 +3V3
3 DI 4 MOSI
2 CS 3 SSEL
1 nc

Looking onto the gold plated connector side of the microSD card:

###############
I 8
I 7
I 6
I 5
I 4
I 3
I 2
I 1
###### ##
\ I \
## ##

The start/stop button is connected to the BUTTON (P0.7) pin of the USB connector (J9). It is activated by pulling it low.

=== Option 3: Logomatic ===

There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board, just use

conf/airframes/logomatic.xml

== UART Connection ==
The two serial inputs LPC_RXD0 (J7) and RXD1 (J2) are used to receive data. The received data is not forwarded to TX0/1 by software (the UART TX pins are deactivated). If the logger is put in between Tiny and the modem the connection should be done with a wire so that a logger failure does not cause any data link issue.

== I2C Connection ==
tbd

== SPI Connection ==
tbd

== Configuration ==
The logger is defined just like an aircraft. Take the

conf/airframes/logger_sd.xml

as example. You can enable one or both UARTs for logging and have to set the serial speed

<configure name="UART0_BAUD" value="B9600" />
<configure name="UART1_BAUD" value="B9600" />

The message type can be switched between the PPRZ and the XBEE format

<configure name="LOG_MSG_FMT" value="LOG_PPRZ"/>
''or''
<configure name="LOG_MSG_FMT" value="LOG_XBEE"/>

The SD card can either be connected to SPI0 or SPI1

<configure name="SPI_CHANNEL" value="0" />
''or''
<configure name="SPI_CHANNEL" value="1" />

Now create a new A/C with the logger airframe. Although they will not be used, you still need to supply dummy files for Flight Plan, Settings, Radio and Telemetry.

== Decoding ==
The telemetry is written in the Paparazzi .tlm [[Messages_Format|format]] that adds a timestamp to each message. The logger starts with 00000000.TLM in the main folder of the SD and increases the number with each log session. Already used numbers will not be overwritten. This data can be converted back to the Paparazzi .log and .data format using sd2log

me@home:~/media/usbstick$ ~/paparazzi3/sw/logalizer/sd2log 00000002.TLM
Renaming produced file ...
09_08_13__20_55_03_SD.data file produced
09_08_13__20_55_03_SD.log file produced
09_08_13__20_55_03_SD.tlm file saved

It creates timestamps from the .tlm and changes the filename to the take-off time if a GPS message with correct time was available in the file or the current local PC time if no GPS was available. The .log file will be re-created either from the current configuration (if still in existence) or the MD5-labeled files that are stored in var/conf each time you build an aircraft. All resulting files are stored in var/logs with an _SD extension.

[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]

Gallery

2011-09-23T20:01:27Z

Jdyuen: /* User's Aircraft Gallery */

== User's Gallery ==
=== User's Aircraft Gallery ===
{|
|-valign="top"
|
<gallery caption="Paparazzi Aircraft">
Image:early_twinstar.jpg|Early Twinstar Antoine Drouin and Pascal Brisset
Image:glotzer.jpg|Glotzer Martin Mueller and Christian Lindenberg
Image:Dragonfly_0626.jpg|Dragonfly University of Arizona Span 30cm, mass 220g
Image:DragonSlayer_0948sm.jpg|Dragon Slayer Miraterre Flight Systems Span 33cm, mass 300g
Image:Twinstar_2_Twinjet_night.JPG|Night-equipped Twinstar and Twinjet Antoine Drouin and Pascal Brisset
Image:Orange_One_0999.jpg|M.A.C. Orange One Martin Mueller and Christian Lindenberg
Image:slayer_twinstar_ii.jpg|Slayer and Twinstar The Twinstar performs an autonomous aerial launch of the Slayer
Image:Sephiroth_Pre-Paparazzi.jpg|Sephiroth P-51 Mustang, off-board video processing for horizon-based stabilization
Image:Triple-X.JPG|Triple-X Prototype Miraterre Flight Systems Span 90cm, mass 1400g
Image:Cybereye.jpg|CyberEye Miraterre Flight Systems Span 130cm, mass 2kg
Image:osamuavs.jpg|Two Zagi's, and Aggiebird Wing Spans 48", 60", and 100" OSAM-UAV Team
Image:NoVa1.jpg|NoVa Quadrotor AJ Kochevar Attitude Stabilized quadrotor using Tiny 2.0
Image:nirvana.jpg|Nirvana The 3 Minimag used at the LAAS-CNRS Laboratory
Image:PPZFJ01.JPG| FJ1 The PPZUAV project aircraft and demo
Image:Paparazzitelema1.jpg | Telemaster Autonomous platform to get used to the system
Image:Easystar cropped w800.JPG| John Burt tested and flying
Image:UAV.JPG|Luke Ionno over at rcgroups
Image:Mentor.JPG|Multiplex Mentor Joekadet, 7 flights, Auto2 working now.
Image:Azorean_UAV_01.jpg|Twinstar II [[Rui Costa]] Azores - Portugal.
Image:Y-UAV1.JPG|Y-UAV [http://www.y-uav.com Home Page] Meilen - Switzerland.
Image:UMARS.JPG|UMARS [http://www.imes.zhaw.ch/de/engineering/imes/projekte/leichtbautechnik/umars/projektbeschreibung.html Home Page] Winterthur - Switzerland.
Image:eHawk.JPG|eHawk R. Büttner Meilen - Switzerland.
Image:TwinStar_stspies1.JPG|TwinStar II [http://paparazzi.enac.fr/wiki/User:Stspies Steffen] Germany.
Image:Mentormaur.jpg|Multiplex Mentor R. Maurer Bottighofen - Switzerland.
Image:Cougar.JPG|Cougar R. Büttner Meilen - Switzerland.
Image:UofA_UAP1.jpg|Senior Telemaster [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup U of A UAS Group] Edmonton - Canada.
</gallery>
|

|}

==Video==

[http://www.youtube.com/watch?v=M1k_TLcQ2ic Micro UAV climbing to 1500m on Spitsbergen/Arctic]

[http://www.youtube.com/user/aerovistapunktch#p/u/3/7OCcMA4vluM Desktop Record GCS Y-UAV]

[http://www.youtube.com/user/aerovistapunktch#p/u/1/o6auxzO93lU Bungee Launch Y-UAV]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

== Scientific campaigns ==

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

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

[[Category:Community]]

Help:Editing

2011-09-23T19:06:35Z

Jdyuen: /* External Links */

== External Links ==

[http://meta.wikimedia.org/wiki/Help:Editing Wikimedia Help:Editing]

[http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page Wikipedia:How To Edit a Page]

[http://en.wikipedia.org/wiki/Help:Contents/Site_map Wikipedia:Help Table of Contents]

[http://www.mediawiki.org/wiki/Help:Contents Mediawiki:Help Contents]

== Wiki wish list ==
* Upgrade to latest MediaWiki version (1.16.5)
* install [http://www.mediawiki.org/wiki/Extension:CategoryTree CategoryTree extension]
* install [http://www.mediawiki.org/wiki/Extension:UsabilityInitiative UsabilityInitiative] extension
* add syntax highlighting, e.g. [http://www.mediawiki.org/wiki/Extension:SyntaxHighlight_GeSHi SyntaxHighlight_GeSHi]
* update [http://www.mediawiki.org/wiki/Extension:GraphViz GraphViz extension]

Extensions that might be usefull
* [http://www.mediawiki.org/wiki/Extension:BreadCrumbs2 BreadCrumbs extension] adds a breadcrumbs like navigation in the subtitle of every page
* [http://www.mediawiki.org/wiki/Extension:Collection Collection] allows a user to organize personal selections of pages in a collection which then can be exported using the [http://www.mediawiki.org/wiki/Extension:PDF_Writer PDF writer]
* [http://www.mediawiki.org/wiki/Extension:Hierarchy Hierarchy] simplifies hierarchical and linear composition of articles. Very useful for HOWTO's and system documentation.
* [http://www.mediawiki.org/wiki/Extension:MultiUpload MultiUpload] The MultiUpload extension allows users to upload more than one file at a time, the extension tries to recreate all of the function of Special:Upload as possible.
* Some captcha plugin?

UAlberta UASGroup

2011-09-23T19:00:09Z

Jdyuen: /* University of Alberta Unmanned Aircraft Systems Group */

==University of Alberta Unmanned Aircraft Systems Group==

[[Image:UofAUASGroup_logoBW.png|400px|right|Group Logo]]

The [http://www.mece.engineering.ualberta.ca/en/Research/UnmannedAerialSystems.aspx University of Alberta UAS Group] is a fledgling team composed of a number of research groups, students and professors at the [http://www.ualberta.ca/ University of Alberta] in Edmonton, Alberta, Canada. The group is based out of the Department of Mechanical Engineering, with members from a variety of other departments, including Earth and Atmospheric Science and Electrical and Computer Engineering. We are currently preparing a small demonstration platform. This UAV platform will be the beginning of an attempt to foster UAS research at our university, and provide an initial starting point for researchers from a variety of disciplines and departments to begin research on unmanned aircraft systems directly (like controls), or, more likely, to investigate payloads and applications (like industrial monitoring).

== Current Work ==

The first platform is Unmanned Aircraft Platform 1, or UAP1.

=== UAP1 ===
''Airframe:''

[[Image:UofA_UAP1.jpg|thumb|600px|right|Telemaster Maiden Flight]]

* Type of aircraft: Hobby Lobby Senior Telemaster almost-ready-to-fly model aircraft
** Modified for bolt-on wing and tail-mounted servos
* Type of engine: 2-stroke 26cc Evolution 26GX with electronic ignition (2S 2500mAh Lipo)
* Dimensions: wing span 2.4 m (94 inches); fuselage 1.6m (64 inches)
* Actuators: Hitec programmable digital servos used throughout

''Autopilot Systems:''

* Spektrum DX8 system with AR8000 receiver and TM1000 telemetry module for safety pilot situational awareness
* 2S 4000mAh Lipo for servos and autopilot system
* Paparazzi autopilot
** TWOG v1.0
** Ublox LEA5H and Sarantel helical antenna
** Aspirin IMU via I2C
** Eagle Tree airspeed sensor
** ATMega168 based PPM encoder
** SmartFly optical ignition cut-off
* Digi XTend 900MHz radio modems
* Ground Segment:
** Macbook Pro with OS X 10.6 (running Paparazzi in OS X)

''Payload Systems:''

*Currently not determined, though initially a GoPro will be mounted onboard

====Flight Progress====
Currently, we have successfully flown UAP1 in manual and auto1. It took a long time to modify the model, install the autopilot systems and deal with vibration issues from the gas engine.

== Vibration (WORK IN PROGRESS)==

Vibration can be a major problem in small UAVs. Vibration can come from a variety of sources, but in UAVs the most significant source is rotating machinery, i.e. the primary powerplants in the airframe.

''Major Sources of Vibration:''
* Main electric motors
* Internal combustion engines
* Unbalanced propellers
''Minor Sources of Vibration:''
* Flutter or resonance in flight surfaces and airframe
* Actuators or servos for flight or payload control
In general, the main source of thrust will be the primary source of vibration.

* link to vibration background, how to calculate natural frequencies etc, perhaps some modeling discussion

=== Impacts of Vibration ===
* airframe fatigue
* wiring connection fatigue (including RF connections)
* lower efficiency
* increased sensor noise, bias (gyros, accelerometers, magnetometers, pressure transducers, etc)
* potential for sensor saturation (gyros, accelerometers in IMU)
* degradation of payload sensor data quality (especially imagery with CMOS sensors, increase in rolling shutter effects, motion blur, shaky video)
* discussion on how to identify vibration problems
* discussion of sensor noise effects, namely on DCM algorithm, give examples with aspirin IMU, add screenshots of logs

=== Mitigating Effects of Vibration ===
* mechanical methods, best, helps all parts of airframe
* calculating and testing
* recommended methods and materials
* things to keep an eye out for (resonance on parts)
* software filtering for IMU and other sensors, advantages and disadvantages, explain addition to fw aspirin i2c driver, video shake reduction
* show some samples from vibration testing
* pictures/sketches of mounting methods

UAlberta UASGroup

2011-09-23T18:59:19Z

Jdyuen: /* UAP1 */

==University of Alberta Unmanned Aircraft Systems Group==

[[Image:UofAUASGroup_logoBW.png|frameless|400px|right|Group Logo]]

The [http://www.mece.engineering.ualberta.ca/en/Research/UnmannedAerialSystems.aspx University of Alberta UAS Group] is a fledgling team composed of a number of research groups, students and professors at the [http://www.ualberta.ca/ University of Alberta] in Edmonton, Alberta, Canada. The group is based out of the Department of Mechanical Engineering, with members from a variety of other departments, including Earth and Atmospheric Science and Electrical and Computer Engineering. We are currently preparing a small demonstration platform. This UAV platform will be the beginning of an attempt to foster UAS research at our university, and provide an initial starting point for researchers from a variety of disciplines and departments to begin research on unmanned aircraft systems directly (like controls), or, more likely, to investigate payloads and applications (like industrial monitoring).

== Current Work ==

The first platform is Unmanned Aircraft Platform 1, or UAP1.

=== UAP1 ===
''Airframe:''

[[Image:UofA_UAP1.jpg|thumb|600px|right|Telemaster Maiden Flight]]

* Type of aircraft: Hobby Lobby Senior Telemaster almost-ready-to-fly model aircraft
** Modified for bolt-on wing and tail-mounted servos
* Type of engine: 2-stroke 26cc Evolution 26GX with electronic ignition (2S 2500mAh Lipo)
* Dimensions: wing span 2.4 m (94 inches); fuselage 1.6m (64 inches)
* Actuators: Hitec programmable digital servos used throughout

''Autopilot Systems:''

* Spektrum DX8 system with AR8000 receiver and TM1000 telemetry module for safety pilot situational awareness
* 2S 4000mAh Lipo for servos and autopilot system
* Paparazzi autopilot
** TWOG v1.0
** Ublox LEA5H and Sarantel helical antenna
** Aspirin IMU via I2C
** Eagle Tree airspeed sensor
** ATMega168 based PPM encoder
** SmartFly optical ignition cut-off
* Digi XTend 900MHz radio modems
* Ground Segment:
** Macbook Pro with OS X 10.6 (running Paparazzi in OS X)

''Payload Systems:''

*Currently not determined, though initially a GoPro will be mounted onboard

====Flight Progress====
Currently, we have successfully flown UAP1 in manual and auto1. It took a long time to modify the model, install the autopilot systems and deal with vibration issues from the gas engine.

== Vibration (WORK IN PROGRESS)==

Vibration can be a major problem in small UAVs. Vibration can come from a variety of sources, but in UAVs the most significant source is rotating machinery, i.e. the primary powerplants in the airframe.

''Major Sources of Vibration:''
* Main electric motors
* Internal combustion engines
* Unbalanced propellers
''Minor Sources of Vibration:''
* Flutter or resonance in flight surfaces and airframe
* Actuators or servos for flight or payload control
In general, the main source of thrust will be the primary source of vibration.

* link to vibration background, how to calculate natural frequencies etc, perhaps some modeling discussion

=== Impacts of Vibration ===
* airframe fatigue
* wiring connection fatigue (including RF connections)
* lower efficiency
* increased sensor noise, bias (gyros, accelerometers, magnetometers, pressure transducers, etc)
* potential for sensor saturation (gyros, accelerometers in IMU)
* degradation of payload sensor data quality (especially imagery with CMOS sensors, increase in rolling shutter effects, motion blur, shaky video)
* discussion on how to identify vibration problems
* discussion of sensor noise effects, namely on DCM algorithm, give examples with aspirin IMU, add screenshots of logs

=== Mitigating Effects of Vibration ===
* mechanical methods, best, helps all parts of airframe
* calculating and testing
* recommended methods and materials
* things to keep an eye out for (resonance on parts)
* software filtering for IMU and other sensors, advantages and disadvantages, explain addition to fw aspirin i2c driver, video shake reduction
* show some samples from vibration testing
* pictures/sketches of mounting methods

File:UofA UAP1.jpg

2011-09-23T18:37:16Z

Jdyuen: Maiden flight of UAlberta Telemaster

Maiden flight of UAlberta Telemaster

Users

2011-09-23T18:26:50Z

Jdyuen: /* North America */

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

== Wiki User Pages ==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ User Pages
|-
|- style="background:bisque; color:black"
|[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]
|- style="background:bisque; color:black"
|[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]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]
|[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]
|[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]
|[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]
|[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:Marc Marc]
|[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]
|[http://paparazzi.enac.fr/wiki/User:HWal HWal]
|[http://paparazzi.enac.fr/wiki/User:Aerodolphin Rui Costa]
|[http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:PaulCox Paul Cox]
|[http://paparazzi.enac.fr/wiki/User:Bruzzlee Bruzzlee]
|[http://paparazzi.enac.fr/wiki/User:Stspies Stspies]
|[http://paparazzi.enac.fr/wiki/User:Mzr Mzr]
|[http://brquad.blogspot.com AGRESSiVA]
|- style="background:bisque; color:black"
|add yourself here
|
|
|
|
|}

= Paparazzi Users sorted geographically =

==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:zhaojinhust@gmail.com ZHAOJin]|| China || Tiny2.11 ||| 2011|| Just Finished my hand-soldered Tiny2.11 board. Welcome to my blog: freikorps.blogcn.com (CHINESE中文)
|- style="background:bisque; color:black"
| [mailto:wangcfan@163.com Wangcfan]|| China || Tiny2.11 ||| 2008 || The beginning, is now in learning phase;Learning in Tiny2.11 using the method of IMU!
|- 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:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe
|- 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
|- style="background:bisque; color:black"
| [mailto:benybeejz@gmail.com benybee] || Bandar Lampung, Indonesia || Tiny13 1.1 ||| 2010 || trying to get wing dragon fully autonomus, for aireal photograph and research
|}

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

! Name !! Location !! Hardware !! Joined !! Current activities / project status

|- style="background:lightgreen; color:black"
|Austria

|- 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: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:lightgreen; color:black"
|France

|- 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"
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera

|- style="background:bisque; color:black"
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting

|- style="background:bisque; color:black"
| [mailto:limaiem@gmail.com Imed Limaiem] || Paris, France || TWOG 2.11, EPP-CF FPV ||| January 2010 || flight test; Town pollution measurement;

|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
| Toulouse
| 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:lightgreen; color:black"
|Germany

|- style="background:bisque; color:black"
| [mailto:maik.hoepfel_at_web.de Maik Hoepfel] || Berlin, Germany || TWOG, Borjet Maja, Futaba 9C 35 Mhz ||| August 2009 || Have flown different airframes and am flying a Borjet Maja right now; built a more rugged case and connecting board for PPRZ; taking surveying pictures

|- 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"
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz and Lisa/L ||| 2008 || coding more than flying.... unfortunately

|- style="background:bisque; color:black"
| [[User:TheJJ|Jonas Jelten]] || Augsburg, Germany || just our airframe ||| 2010 || "P-Seminar" for the new G8 at our Gymnasium ([http://www.solarflugzeug.de.tc solarflugzeug.de.tc])

|- style="background:bisque; color:black"
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successful AUTO2-Flights.

|- style="background:bisque; color:black"
| [[User:Martial|Martial Châteauvieux]] || Munich, Germany || Bormatec/Maja with TWOG and IR ||| 2011 || Every thing installed on board. First crash during test on field. I need to repair the airframe. Next test on Monday 15th of Aug.
|- style="background:bisque; color:black"
| [[User:Stspies|Steffen Spies]] || Wolfsburg, Germany || Multiplex TwinStar with Tiny V2.11 and IR ||| 2010 || Awaiting first flight.

|- style="background:bisque; color:black"
| [[User:Tobi|Tobias M]] || Germany || Multiplex TwinStar II TWOG v1 and IR/imu ||| 2007 || about 120h of flight tests in Auto2 with IR - coding and testing a new vertical control with airspeed - just changed from IR to Aspirin imu - about 3h Auto2 in that configuration

|- style="background:bisque; color:black"
| [[User:RoN|Rolf N]] || Bremen, Germany || Multiplex Acromaster with TWOG, airspeed and imu ||| 2010 || Several successful AUTO2 flights

|- style="background:lightgreen; color:black"
| Portugal

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

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

|- style="background:lightgreen; color:black"
|Switzerland

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

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

|- style="background:bisque; color:black"
| [mailto:reto.buettner_at_gmail.com RetoB] || Meilen, Switzerland || TWOG, Tiny 2.11, Cougar, eHawk, Y-UAV, EzOSD, Scherrer UHF ||| 2010 || Many successful flights. See [http://www.aerovista.ch/news.html www.aerovista.ch] and [http://www.y-uav.com www.y-uav.com] for current status.

|- style="background:bisque; color:black"
| [mailto:schmiemi_at_students.zhaw.ch EmilioS] || Winterthur, Switzerland || Tiny 2.11 incl. ArduIMU, Borjet Maja, UMARS||| 2010 || Many successful flights. See [http://www.imes.zhaw.ch/de/engineering/imes/projekte/leichtbautechnik/umars/projektbeschreibung.html UMARS] for current status.

|- style="background:bisque; color:black"
| [mailto:enso@zhaw.ch Oliver E] || Winterthur, Switzerland || Tiny 2.11 incl. ArduIMU, Kyosho Calmato, UMARS||| 2010 || Many Successful flights. A lot of experience as savety pilot. Experience with pich based speed control (best you can have). No programming skills unfortuanatley.

|- style="background:bisque; color:black"
| [mailto:samuelbryner_gmx.ch Samuel B.] || Winterthur, Switzerland || Tiny 2.11, Multiplex Easyglider ||| 2010 || Just starting. No flight so far :/

|- style="background:bisque; color:black"
| [mailto:rmaurer@sunrise.ch RetoM] || Bottighofen, Switzerland || Tiny 2.11, Multiplex Mentor ||| 2010 || First flight successfully performed on 16 July 2011, including auto-landing, more to go ...

|- style="background:bisque; color:black"
| [mailto:sjwilks_at_gmail.com Simon W.] || Aarau, Switzerland || TWOG with ArduIMU in Jamara Roo, Telink Tempest, Bormatec Maja and Lisa/L for the XAircraft X650 ||| 2010 || Many successful flights. See [http://sites.google.com/site/paparazziuav/ http://sites.google.com/site/paparazziuav/].

|- style="background:lightgreen; color:black"
| UK

|- 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, Multiplex Mentor, Multiplex Funjet, Multiplex Fox, GWS Formosa ||| 2008 || Came 4th in EMAV09 (although won the Golden Balls award for courage in the face of adversity and exceptional partying). Many AUTO2 flights with a camera and XBee868s. Current main airframe is a GWS Formosa (they are so cheap!).

|- style="background:lightgreen; color:black"
| Other

|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3,2.11, Twog 1.0 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV. Successfull. Now using it on large gliders and jets.

|- 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"
| [[User:openuas|OpenUAS]] || Amsterdam, The Netherlands || TWOG, Tiny, Lisa/L and various airframes || 2007 || Quite a few AUTO2 flights. Improving airspeed, IMU and strong wind integration

|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, two own hardware designs, 5 kg aerial photo plane, 2.5 kg survelliance uav, Easystar ||| 2007 || Use modified autopilot and GCS in professional tasks, add self desidned IMU

|- 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: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"
| [http://paparazzi.enac.fr/wiki/User:VAMK Allan Ojala (VAMK)] || Vaasa, Finland || TWOG, with AC4790 radio and LEA-5H GPS ||| 2009 || Ditched the SIG Kadet. Built a new big plane TaigaCam. Self-build model made out of EPP and a plastic tube.

|- style="background:bisque; color:black"
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up

|- style="background:bisque; color:black"
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor
|

|- style="background:bisque; color:black"
| [mailto:helgewal@gmail.com Helge] || Bergen, Norway || TWOG ||| 2009 || First Auto2 flight with Twinstar2 in October 2010

|- style="background:bisque; color:black"
| [mailto:kepler0@gmail.com Joaquín] || Málaga, Spain|| TWOG v1, Trex600, Cockpit SX, ArduImuV2, HMC5843 ||| September 2009 || Finished integration (navigation, control, actuators). Missing to realize an automatic engine control.
|}

==North America==

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

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee

|- 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"
| [mailto:armz12@gmail.com Armen Gharibans] || La Jolla, California || Tiny2.11 (PPZUAV) ||| March 2009 || UCSD Project with Multiplex Mentor. Completed August 2, 2009. Several Successful Auto2 Flights. A LOT of help from David Conger.

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:EldenC Elden Crom] || Tucson, AZ || Twog 1.0 ||| July 2009 || Multiplex Twinstar, XBee Pro. Several Successful Auto2 Flights. Working toward precise Auto-Takeoff and Auto-Land

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider] || Tucson, AZ || None, will use TWOG 1.0 ||| December 2009 || Super Dimona, Aerocomm. No Flight test. Working toward setting waypoints within Paparazzi code

|- style="background:bisque; color:black"
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project

|- style="background:bisque; color:black"
| Team UAV UALR Caleb Tenberge || Little Rock, AR || Using TWOG 1.0 ||| Feb 2010 || Using a Telemaster, we are learning the GCS and building our plane.

|- style="background:bisque; color:black"
| [mailto:changho.nam@asu.edu Arizona State University POLY - Capstone Team: Development of UAV /w surveillance System] || Mesa, AZ || Using TINY 2.1 - 2.4GHz Modem, CCD Camera /w 900 MHz Video Transmitter ||| March 2010 || 4-lbs Flying Wings. We made successful autonomous flights.

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer] || Edmonton, AB, CAN || Nothing Yet ||| Jan 2011 || Obtaining Hardware

|- style="background:bisque; color:black"
| [mailto:muratagenc@yahoo.com Murat A. Genc] || New York, NY || not decided yet ||| May 2011 || just started

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup University of Alberta UAS Group] || Edmonton, AB, CAN || TWOG 1.0, Asprin IMU ||| Aug 2011 || Completing tuning flights in Auto 1 on a Senior Telemaster with 26cc gas engine. Working towards a stable platform for research.

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

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! 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
|}

==South America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:gustavoviolato@gmail.com Gustavo Violato] || São José dos Campos, Brasil || Tiny v2.11/LEA-4P, Modem XBee Pro 2.4 GHz Swift II ||| 2009 || Flying autonomously and enjoying it. Planning to use the system for flight test data acquisition and aircraft parameter recognition.
|- style="background:bisque; color:black"
| [mailto:agressiva@hotmail.com Eduardo Lavratti] || Porto Alegre - RS, Brasil || TWOG / BOOZ, UBLOX, Xbee900 60mw||| 2011 || Working with geoprocessing - developping new modules and sensors to paparazzi.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:RH1N0 RH1N0] || Brisbane, QLD || TWOG, Multiplex Easystar, PPZGPS, H.264 live digital video, Ubiquiti modems ||| May 2011 || Multiple AUTO2 flights up to 40 min. Currently testing PPZIMU.
|- 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 PRO modems, Futaba T6EXAP TX, Futaba R136F RX, Funjet, MacBook laptop ||| August 2008 || Several flights in Auto1
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Adam.A Adam Amos] || Sydney, NSW || TWOG, IMU, BORJET MAJA || March 2010 || see [http://www.rescuerobotics.com.au www.rescuerobotics.com.au] for current status
|}

==Africa==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:w1_th@yahoo.com W1th] || South Africa KZN || TWOG V1 ,LEA-5H GPS , RF Modems XBee Pro 868 (CheBuzz) ||| July 2009 || Got TWOG,GPS etc interfacing with Laptop and working , Have not done anything to it recently but...Made a website [http://sites.google.com/site/scarfclub/paparazi-uav SCARF Paparazzi-UAV] of my struggle ...
|- style="background:bisque; color:black"
| [mailto:willie.smit@nwu.ac.za Willie Smit] || South Africa NW || Tiny v2.11, LEA-4P GPS, RF Modems XBee Pro ||| April 2010 || We are currently doing test flights. Also doing research on obstacle avoidance.
|- style="background:bisque; color:black"
|}

=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

[[Category:Community]]

User:Jdyuen

2011-09-23T18:03:18Z

Jdyuen: /* About Me */

== About Me ==
* Name: Jamie Yuen
* Location: Edmonton, Alberta, Canada
* Masters student in Mechanical Engineering at the University of Alberta
* Member of the [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup University of Alberta UAS Group]

I have limited experience with Paparazzi so far, but am starting to use it as part of the U of A UAS Group. I have been piloting for the group as we tune gains and am planning to use the resulting platform for remote sensing research.

My first exposure to UAV systems was withe the U of A Aerial Robotics Group, where I was co-team lead for 1 year and attended 2 AUVSI Student UAS competitions. We used the Micropilot MP2128g in our systems, but I am excited about the open nature and low cost of the Paparazzi system.

User:Jdyuen

2011-09-23T18:02:48Z

Jdyuen:

== About Me ==
* Name: Jamie Yuen
* Location: Edmonton, Alberta, Canada
* Masters student in Mechanical Engineering at University of Alberta
* Member of the [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup University of Alberta UAS Group]

I have limited experience with Paparazzi so far, but am starting to use it as part of the U of A UAS Group. I have been piloting for the group as we tune gains and am planning to use the resulting platform for remote sensing research.

My first exposure to UAV systems was withe the U of A Aerial Robotics Group, where I was co-team lead for 1 year and attended 2 AUVSI Student UAS competitions. We used the Micropilot MP2128g in our systems, but I am excited about the open nature and low cost of the Paparazzi system.

User:Scdwyer

2011-09-23T17:55:20Z

Jdyuen: /* About Me */

== About Me ==
* Name: Stephen Dwyer
* Location: Edmonton, Alberta, Canada
* Masters student in Mechanical Engineering at University of Alberta
* Member of the [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup University of Alberta UAS Group]
* Contact: scdwyerATualbertaDOTca

I have very little experience with Paparazzi thus far. I hope to remedy this in the near future, both for fun and (hopefully) as part of my Masters research. I have been following the wiki and mailing list for quite some time though.

I began working with small unmanned aircraft systems with the U of A Aerial Robotics Group, where I was team lead for 2 years, co-team lead for 1 year, and attended 3 AUVSI Student UAS competitions. We used the Micropilot MP2128g in our systems, and I gained valuable experience understanding the difficulty of autonomous system integration.

== Current Work ==
I am working with two other students as part of a larger University of Alberta Unmanned Aircraft Systems Group to prepare a small demonstration platform. This UAV platform will be the beginning of an attempt to foster UAS research at our university, and provide an initial starting point for researchers from a variety of disciplines and departments to begin research on unmanned aircraft systems directly, or, more likely, investigate payloads and applications.

The first platform is Unmanned Aircraft Platform 1, or UAP1.

=== UAP1 ===
''Airframe:''

* Type of aircraft: Hobby Lobby Senior Telemaster almost-ready-to-fly model aircraft
** Modified for bolt-on wing and tail-mounted servos
* Type of engine: 2-stroke 26cc Evolution 26GX with electronic ignition (2S 2500mAh Lipo)
* Dimensions: wing span 2.4 m (94 inches); fuselage 1.6m (64 inches)
* Actuators: Hitec programmable digital servos used throughout

''Autopilot Systems:''

* Spektrum DX8 system with AR8000 receiver and TM1000 telemetry module for safety pilot situational awareness
* 2S 4000mAh Lipo for servos and autopilot system
* Paparazzi autopilot
** TWOG v1.0
** Ublox LEA5H and Sarantel helical antenna
** Aspirin IMU via I2C
** Eagle Tree airspeed sensor
** ATMega168 based PPM encoder
** SmartFly optical ignition cut-off
* Digi XTend 900MHz radio modems
* Ground Segment:
** Macbook Pro with OS X 10.6

''Payload Systems:''

*Currently not determined, though initially a GoPro will be mounted onboard

== Vibration ==

Vibration can be a major problem in small UAVs. Vibration can come from a variety of sources, but in UAVs the most significant source is rotating machinery, i.e. the primary powerplants in the airframe.

''Major Sources of Vibration:''
* Main electric motors
* Internal combustion engines
* Unbalanced propellers
''Minor Sources of Vibration:''
* Flutter or resonance in flight surfaces and airframe
* Actuators or servos for flight or payload control
In general, the main source of thrust will be the primary source of vibration.

* link to vibration background, how to calculate natural frequencies etc, perhaps some modeling discussion

=== Impacts of Vibration ===
* airframe fatigue
* wiring connection fatigue (including RF connections)
* lower efficiency
* increased sensor noise, bias (gyros, accelerometers, magnetometers, pressure transducers, etc)
* potential for sensor saturation (gyros, accelerometers in IMU)
* degradation of payload sensor data quality (especially imagery with CMOS sensors, increase in rolling shutter effects, motion blur, shaky video)
* discussion on how to identify vibration problems
* discussion of sensor noise effects, namely on DCM algorithm, give examples with aspirin IMU, add screenshots of logs

=== Mitigating Effects of Vibration ===
* mechanical methods, best, helps all parts of airframe
* calculating and testing
* recommended methods and materials
* things to keep an eye out for (resonance on parts)
* software filtering for IMU and other sensors, advantages and disadvantages, explain addition to fw aspirin i2c driver, video shake reduction
* show some samples from vibration testing
* pictures/sketches of mounting methods

Users

2011-09-23T17:52:57Z

Jdyuen: /* North America */

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

== Wiki User Pages ==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|+ User Pages
|-
|- style="background:bisque; color:black"
|[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]
|- style="background:bisque; color:black"
|[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]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]
|[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]
|[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]
|[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]
|[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:Marc Marc]
|[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]
|[http://paparazzi.enac.fr/wiki/User:HWal HWal]
|[http://paparazzi.enac.fr/wiki/User:Aerodolphin Rui Costa]
|[http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer]
|- style="background:bisque; color:black"
|[http://paparazzi.enac.fr/wiki/User:PaulCox Paul Cox]
|[http://paparazzi.enac.fr/wiki/User:Bruzzlee Bruzzlee]
|[http://paparazzi.enac.fr/wiki/User:Stspies Stspies]
|[http://paparazzi.enac.fr/wiki/User:Mzr Mzr]
|[http://brquad.blogspot.com AGRESSiVA]
|- style="background:bisque; color:black"
|add yourself here
|
|
|
|
|}

= Paparazzi Users sorted geographically =

==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:zhaojinhust@gmail.com ZHAOJin]|| China || Tiny2.11 ||| 2011|| Just Finished my hand-soldered Tiny2.11 board. Welcome to my blog: freikorps.blogcn.com (CHINESE中文)
|- style="background:bisque; color:black"
| [mailto:wangcfan@163.com Wangcfan]|| China || Tiny2.11 ||| 2008 || The beginning, is now in learning phase;Learning in Tiny2.11 using the method of IMU!
|- 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:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe
|- 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
|- style="background:bisque; color:black"
| [mailto:benybeejz@gmail.com benybee] || Bandar Lampung, Indonesia || Tiny13 1.1 ||| 2010 || trying to get wing dragon fully autonomus, for aireal photograph and research
|}

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

! Name !! Location !! Hardware !! Joined !! Current activities / project status

|- style="background:lightgreen; color:black"
|Austria

|- 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: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:lightgreen; color:black"
|France

|- 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"
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera

|- style="background:bisque; color:black"
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting

|- style="background:bisque; color:black"
| [mailto:limaiem@gmail.com Imed Limaiem] || Paris, France || TWOG 2.11, EPP-CF FPV ||| January 2010 || flight test; Town pollution measurement;

|- style="background:bisque; color:black"
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox]
| Toulouse
| 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:lightgreen; color:black"
|Germany

|- style="background:bisque; color:black"
| [mailto:maik.hoepfel_at_web.de Maik Hoepfel] || Berlin, Germany || TWOG, Borjet Maja, Futaba 9C 35 Mhz ||| August 2009 || Have flown different airframes and am flying a Borjet Maja right now; built a more rugged case and connecting board for PPRZ; taking surveying pictures

|- 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"
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz and Lisa/L ||| 2008 || coding more than flying.... unfortunately

|- style="background:bisque; color:black"
| [[User:TheJJ|Jonas Jelten]] || Augsburg, Germany || just our airframe ||| 2010 || "P-Seminar" for the new G8 at our Gymnasium ([http://www.solarflugzeug.de.tc solarflugzeug.de.tc])

|- style="background:bisque; color:black"
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successful AUTO2-Flights.

|- style="background:bisque; color:black"
| [[User:Martial|Martial Châteauvieux]] || Munich, Germany || Bormatec/Maja with TWOG and IR ||| 2011 || Every thing installed on board. First crash during test on field. I need to repair the airframe. Next test on Monday 15th of Aug.
|- style="background:bisque; color:black"
| [[User:Stspies|Steffen Spies]] || Wolfsburg, Germany || Multiplex TwinStar with Tiny V2.11 and IR ||| 2010 || Awaiting first flight.

|- style="background:bisque; color:black"
| [[User:Tobi|Tobias M]] || Germany || Multiplex TwinStar II TWOG v1 and IR/imu ||| 2007 || about 120h of flight tests in Auto2 with IR - coding and testing a new vertical control with airspeed - just changed from IR to Aspirin imu - about 3h Auto2 in that configuration

|- style="background:bisque; color:black"
| [[User:RoN|Rolf N]] || Bremen, Germany || Multiplex Acromaster with TWOG, airspeed and imu ||| 2010 || Several successful AUTO2 flights

|- style="background:lightgreen; color:black"
| Portugal

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

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

|- style="background:lightgreen; color:black"
|Switzerland

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

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

|- style="background:bisque; color:black"
| [mailto:reto.buettner_at_gmail.com RetoB] || Meilen, Switzerland || TWOG, Tiny 2.11, Cougar, eHawk, Y-UAV, EzOSD, Scherrer UHF ||| 2010 || Many successful flights. See [http://www.aerovista.ch/news.html www.aerovista.ch] and [http://www.y-uav.com www.y-uav.com] for current status.

|- style="background:bisque; color:black"
| [mailto:schmiemi_at_students.zhaw.ch EmilioS] || Winterthur, Switzerland || Tiny 2.11 incl. ArduIMU, Borjet Maja, UMARS||| 2010 || Many successful flights. See [http://www.imes.zhaw.ch/de/engineering/imes/projekte/leichtbautechnik/umars/projektbeschreibung.html UMARS] for current status.

|- style="background:bisque; color:black"
| [mailto:enso@zhaw.ch Oliver E] || Winterthur, Switzerland || Tiny 2.11 incl. ArduIMU, Kyosho Calmato, UMARS||| 2010 || Many Successful flights. A lot of experience as savety pilot. Experience with pich based speed control (best you can have). No programming skills unfortuanatley.

|- style="background:bisque; color:black"
| [mailto:samuelbryner_gmx.ch Samuel B.] || Winterthur, Switzerland || Tiny 2.11, Multiplex Easyglider ||| 2010 || Just starting. No flight so far :/

|- style="background:bisque; color:black"
| [mailto:rmaurer@sunrise.ch RetoM] || Bottighofen, Switzerland || Tiny 2.11, Multiplex Mentor ||| 2010 || First flight successfully performed on 16 July 2011, including auto-landing, more to go ...

|- style="background:bisque; color:black"
| [mailto:sjwilks_at_gmail.com Simon W.] || Aarau, Switzerland || TWOG with ArduIMU in Jamara Roo, Telink Tempest, Bormatec Maja and Lisa/L for the XAircraft X650 ||| 2010 || Many successful flights. See [http://sites.google.com/site/paparazziuav/ http://sites.google.com/site/paparazziuav/].

|- style="background:lightgreen; color:black"
| UK

|- 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, Multiplex Mentor, Multiplex Funjet, Multiplex Fox, GWS Formosa ||| 2008 || Came 4th in EMAV09 (although won the Golden Balls award for courage in the face of adversity and exceptional partying). Many AUTO2 flights with a camera and XBee868s. Current main airframe is a GWS Formosa (they are so cheap!).

|- style="background:lightgreen; color:black"
| Other

|- style="background:bisque; color:black"
| [mailto:silas_at_silas.hu SilaS] || Budapest || Tiny 1.3,2.11, Twog 1.0 ||| 2007 || Applied tiny to GWS Estarter, finished long travels in AUTO2. Now transfert it to a Twinstar and working on pairing tiny with FPV. Successfull. Now using it on large gliders and jets.

|- 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"
| [[User:openuas|OpenUAS]] || Amsterdam, The Netherlands || TWOG, Tiny, Lisa/L and various airframes || 2007 || Quite a few AUTO2 flights. Improving airspeed, IMU and strong wind integration

|- style="background:bisque; color:black"
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, two own hardware designs, 5 kg aerial photo plane, 2.5 kg survelliance uav, Easystar ||| 2007 || Use modified autopilot and GCS in professional tasks, add self desidned IMU

|- 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: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"
| [http://paparazzi.enac.fr/wiki/User:VAMK Allan Ojala (VAMK)] || Vaasa, Finland || TWOG, with AC4790 radio and LEA-5H GPS ||| 2009 || Ditched the SIG Kadet. Built a new big plane TaigaCam. Self-build model made out of EPP and a plastic tube.

|- style="background:bisque; color:black"
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up

|- style="background:bisque; color:black"
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor
|

|- style="background:bisque; color:black"
| [mailto:helgewal@gmail.com Helge] || Bergen, Norway || TWOG ||| 2009 || First Auto2 flight with Twinstar2 in October 2010

|- style="background:bisque; color:black"
| [mailto:kepler0@gmail.com Joaquín] || Málaga, Spain|| TWOG v1, Trex600, Cockpit SX, ArduImuV2, HMC5843 ||| September 2009 || Finished integration (navigation, control, actuators). Missing to realize an automatic engine control.
|}

==North America==

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

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee

|- 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"
| [mailto:armz12@gmail.com Armen Gharibans] || La Jolla, California || Tiny2.11 (PPZUAV) ||| March 2009 || UCSD Project with Multiplex Mentor. Completed August 2, 2009. Several Successful Auto2 Flights. A LOT of help from David Conger.

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:EldenC Elden Crom] || Tucson, AZ || Twog 1.0 ||| July 2009 || Multiplex Twinstar, XBee Pro. Several Successful Auto2 Flights. Working toward precise Auto-Takeoff and Auto-Land

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider] || Tucson, AZ || None, will use TWOG 1.0 ||| December 2009 || Super Dimona, Aerocomm. No Flight test. Working toward setting waypoints within Paparazzi code

|- style="background:bisque; color:black"
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project

|- style="background:bisque; color:black"
| Team UAV UALR Caleb Tenberge || Little Rock, AR || Using TWOG 1.0 ||| Feb 2010 || Using a Telemaster, we are learning the GCS and building our plane.

|- style="background:bisque; color:black"
| [mailto:changho.nam@asu.edu Arizona State University POLY - Capstone Team: Development of UAV /w surveillance System] || Mesa, AZ || Using TINY 2.1 - 2.4GHz Modem, CCD Camera /w 900 MHz Video Transmitter ||| March 2010 || 4-lbs Flying Wings. We made successful autonomous flights.

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer] || Edmonton, AB, CAN || Nothing Yet ||| Jan 2011 || Obtaining Hardware

|- style="background:bisque; color:black"
| [mailto:muratagenc@yahoo.com Murat A. Genc] || New York, NY || not decided yet ||| May 2011 || just started

|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/UAlberta_UASGroup University of Alberta UAS Group] || Edmonton, AB, CAN || TWOG 1.0 ||| Aug 2011 || Completing tuning flights in Auto 1 on a Senior Telemaster with 26cc gas engine. Working towards a stable platform for research.

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

==Central America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! 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
|}

==South America==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:gustavoviolato@gmail.com Gustavo Violato] || São José dos Campos, Brasil || Tiny v2.11/LEA-4P, Modem XBee Pro 2.4 GHz Swift II ||| 2009 || Flying autonomously and enjoying it. Planning to use the system for flight test data acquisition and aircraft parameter recognition.
|- style="background:bisque; color:black"
| [mailto:agressiva@hotmail.com Eduardo Lavratti] || Porto Alegre - RS, Brasil || TWOG / BOOZ, UBLOX, Xbee900 60mw||| 2011 || Working with geoprocessing - developping new modules and sensors to paparazzi.
|- style="background:bisque; color:black"
| New User || 1 || 2 ||| 3 || 4
|}

==Australia==

{| class="wikitable" style="text-align:center;background:black; color:blue"
|-
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:RH1N0 RH1N0] || Brisbane, QLD || TWOG, Multiplex Easystar, PPZGPS, H.264 live digital video, Ubiquiti modems ||| May 2011 || Multiple AUTO2 flights up to 40 min. Currently testing PPZIMU.
|- 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 PRO modems, Futaba T6EXAP TX, Futaba R136F RX, Funjet, MacBook laptop ||| August 2008 || Several flights in Auto1
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn
|- style="background:bisque; color:black"
| [http://paparazzi.enac.fr/wiki/User:Adam.A Adam Amos] || Sydney, NSW || TWOG, IMU, BORJET MAJA || March 2010 || see [http://www.rescuerobotics.com.au www.rescuerobotics.com.au] for current status
|}

==Africa==

{| class="wikitable" style="text-align:center;background:black; color:blue"
! Name !! Location !! Hardware !! Joined !! Current activities / project status
|- style="background:bisque; color:black"
| [mailto:w1_th@yahoo.com W1th] || South Africa KZN || TWOG V1 ,LEA-5H GPS , RF Modems XBee Pro 868 (CheBuzz) ||| July 2009 || Got TWOG,GPS etc interfacing with Laptop and working , Have not done anything to it recently but...Made a website [http://sites.google.com/site/scarfclub/paparazi-uav SCARF Paparazzi-UAV] of my struggle ...
|- style="background:bisque; color:black"
| [mailto:willie.smit@nwu.ac.za Willie Smit] || South Africa NW || Tiny v2.11, LEA-4P GPS, RF Modems XBee Pro ||| April 2010 || We are currently doing test flights. Also doing research on obstacle avoidance.
|- style="background:bisque; color:black"
|}

=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

[[Category:Community]]

UAlberta UASGroup

2011-09-23T17:36:28Z

Jdyuen: /* University of Alberta Unmanned Aircraft Systems Group */

==University of Alberta Unmanned Aircraft Systems Group==

I'm adding stuff here.