http://wiki.paparazziuav.org/w/api.php?action=feedcontributions&user=Christoph&feedformat=atomPaparazziUAV - User contributions [en]2024-03-29T14:43:10ZUser contributionsMediaWiki 1.37.1http://wiki.paparazziuav.org/w/index.php?title=RC_Receivers_and_Radios&diff=20838RC Receivers and Radios2016-01-18T20:07:31Z<p>Christoph: Added how to add failsafe for R410X</p>
<hr />
<div>= Introduction=<br />
<br />
To be able to test your airframe before it flies fully autonomous a regular RC transmitter in combination with a receiver can be used. This is essential for testing and tuning your airframe. For this to work the received steering commands have to leave the receiver. Only then with this flow of command data the autopilot when flown in manual mode can do something you tell it to. This page is to give you information of how to connect various receivers. Also how to modify receiver so they can talk to the autopilot.<br />
<br />
=Setup=<br />
<br />
Once you have physically connected your receiver we need to setup the transmitter and receiver combination correctly. This can be an complex task due to the overwhelming amount of options. [[rc_transmitter_and_receiver_setup| To assist you in this setup quest a specific wiki page]] is available to help you out.<br />
<br />
If you have a new Graupner HOTT system, the [[Graupner_HOTT_setup| Graupner HOTT setup]] page will provide all key information about setting up the Graupner transmitter and receiverand correctly output a ppm sum stream.<br />
<br />
=2.4GHz Receivers=<br />
<br />
There are three output type in use which you can connect a 2.4GHz receiver to your autopilot board:<br />
# CPPM, where the C stands for '''C'''ombined, the PPM sum stream output, supported on all current autopilot boards, <br />
# Spektrum serial data output<br />
# S-BUS data output<br />
<br />
If you come across the term "Satellite Receiver", it has nothing to do with satellites in earth orbit. It is just a term to describe an auxiliary receiver normally used to improve reception by plugging into the 'main' receiver.<br />
<br />
If your receiver can not output one of the signals above, maybe you need following:<br />
<br />
# Must have combined PPM pulsetrain out or use [[PPM_Encoder | PPM Encoder]] board. See the [[Get_Hardware| Get Hardware]] page for links to suppliers)<br />
# At least one extra channel beyond those needed to control the servos and motor. (throttle-roll-pitch-mode)<br />
<br />
=HOTT=<br />
<br />
==CPPM output==<br />
<br />
===Graupner GR-12/GR-16/GR-20 HOTT===<br />
<br />
GR-12/GR-16/GR-20 are Transmitters from the [http://www.graupner.de/en/products/1736df13-32af-4183-aa8e-80f31a7f03cb/productcategory.aspx Graupner HOTT Series].<br />
<br />
* 2.4 GHz FHSS system<br />
* regular software updates, good support<br />
* different languages (also with voice output)<br />
* receivers work with 3.6 V to 8.4 V (functional down to 2.5 V)<br />
* highly adjustable<br />
<br />
For a detailed instructions for updates and setup look at the [[Graupner_HOTT_setup]] page.<br />
<br />
=Spektrum=<br />
<br />
The wildly popular Spektrum and other brands of receivers using the spectrum protocol are widely available. Below a few of the tested ones. It is very likly others will also work well with Paparazzi, the only diffrence is, we did not thest them yet. Best of all the protocol is well reverse engineered and almost all details are known and implemented in various opensource libraries.<br />
<br />
==DSM2 v.s. DSMX==<br />
<br />
If you have no specific reason, use DSMX equipment. '''DSMX''' is more robust against interference and '''advised''' over DSM2 receivers. [http://www.rcmodelreviews.com/dx8dsmxreview.shtml This very good article explains it all in depth]. We could not have explained it better ourselves.<br />
<br />
==CPPM output==<br />
<br />
A nice solution for e.g. Tiny and TWOG autopilot boards is use modern DSM and your trusty based autopilot board with the CPPM inputoption. This works as well on LPC and STM based boards. Note that for a configuration radio file on should choose an own one '''not spektrum''' regardless that the connection is over DSM the pulses are PPM out not the serial DSM.<br />
<br />
===OrangeRx R410X===<br />
<br />
[[Image:Orange_RX410X_cppm_out.jpg|thumb|left|Orange R410X Receiver]]<br />
<br />
OrangeRx R410X DSMX compatible 4Ch with '''6 Channels''' PWM/CPPM out. This is the prefered modern alternative if you are looking to replace your "Classic" 35/36/40/41/72mHz receivers PWM/CPPM out for a robust DSMX receiver at almost no cost. Last time we looked the receivers where sold for about 8 Euro (~ 10 USD)<br />
<br />
In order to use the receiver, failsafe has to be deactivated so the AP can detect the loss of signal (the rx still outputs PPM-frames if you don't). To deactivate it you have to give full thottle and also give full trim. Then you have to (re-)bind the rx. Check carefully if the GCS displays NONE if you switch of the tx.<br />
<br />
<br style="clear:both"><br />
<br />
===OrangeRx R615X===<br />
<br />
[[Image:Orange_RX_615_with_CPPM.jpg|thumb|left|Orange R615X Receiver]]<br />
<br />
Another option is to use the OrangeRx R615X 6Ch 2.4GHz Receiver with CPPM out.<br />
<br />
<br style="clear:both"><br />
<br />
===DT RX31c===<br />
<br />
A Deltang, with software v3.5 also DSMX support, so small it is sure worth mentioning:<br />
[[Image:DT_RX31_CPPM.jpg|thumb|left|DT Receiver Rx31c 7ch SumPPM]]<br />
<br />
* Outputs combined PPM (Sum PPM),7 channels for e.g. a Spektrum DX8 and DX6 transmitter<br />
* Subminiature receiver with full range. Only 0.21 grams!. Cost about EUR 30.<br />
* The solution for very tiny aircraft.<br />
* The channels order with Spectrum DX8 in acro mode: Throttle, Roll,Pitch, Gear, Mix, Flap,Aux2<br />
[http://www.deltang.co.uk/rx31b.htm This manufacturer has more interesting receivers, worth a look]<br />
<br />
<br style="clear:both"><br />
<br />
==Direct serial output==<br />
<br />
===OrangeRx R110X===<br />
<br />
<gallery><br />
File:Orange_RX110X.jpg|Orange DSMX small receiver<br />
File:Orange_RX110XL.jpg|Orange DSMX small receiver with longer antenna<br />
</gallery><br />
<br />
OrangeRx R110X Satellite DSMX Receiver [http://www.hobbyking.com/hobbyking/store/__38393__OrangeRx_R110X_2_4Ghz_DSMX_Satellite_Receiver.html| R110X]. Works well, simple to connect. Although called, "Satellite Receiver" it is usable as a ful blown receiver when connected to an AP board. There is also a version with long antenna with two U.FL connectors on the PCB.<br />
<br />
<br style="clear:both"><br />
<br />
===Spektrum 9645===<br />
<br />
[[Image:Spektrum_9645_satellite_receiver.jpg|thumb|left|Spektrum 9645 satellite receiver]]<br />
<br />
[http://www.spektrumrc.com/Products/Default.aspx?ProdID=SPM9645| Spektrum 9645 satellite receiver]. Works well, simple to connect. the DSMX mode is not used, it is used in the DSM2 mode, the receiver is backards compatible with that protocol.<br />
<br style="clear:both"><br />
<br />
==S-Bus output Spektrum==<br />
<br />
Although drafted up by Futaba there are lots of receivers from other brands also giving S-Bus signal output. Paparazzi is perfectly capable to decode the S-Bus information from whatever receiver and use it.<br />
<br />
===Orange DSMX 3C 14ch SBus output===<br />
<br />
If you need a tiny DSMX receiver with SBus out to connect directly to your autopilot, a good option is to use this one<br />
<br />
[[File:Orange DSMX 3ch 14ch sbus out.jpg|thumbnail|left|Orange DSMX 14channel SBus output]]<br />
<br />
<br style="clear:both"><br />
<br />
===Orange DSMX 8C 14ch SBus output===<br />
<br />
For more reception redundancy, one can add a satellite receiver like the RX110XL, and still have SBus output<br />
<br />
<gallery><br />
File:Orange_RX800X.jpg|Orange DSMX 8 with 14CH SBus output<br />
File:Orange_RX800X_and_RX110XL.jpg|Orange DSMX and a satellite<br />
</gallery><br />
<br style="clear:both"><br />
<br />
=FASST=<br />
<br />
<br />
Futaba FASST, Robust receivers. Read more about the FASST system [http://www.futaba-rc.com/technology/fasst.html here].<br />
<br />
==CPPM output==<br />
<br />
===Futaba FASST 7-channel receiver===<br />
<br />
[[Image:rs617fasst.jpg|thumb|left|Futaba RS 617]]<br />
<br />
* Pin 8 (upper right corner in picture) of the small IC on the right contains 5 PPM pulses and can go directly to paparazzi. Pulse 6 and 7 go directly to the servos. <br />
* Best is to remove the resistors of one of the channels and connect a small wire to pin 8 to get the combined 5 pulses on the robust 1/10th inch header.<br />
* Do not forget to use channel 3 (only failsafe channel) as mode switch with fail safe "throttle off" as mode 2.<br />
<br style="clear:both"><br />
<br />
===Robbe RASST 7 & 8 channel receivers===<br />
<br />
Robbe has produced line of Futaba FASST compatible receivers that can output only PPM which results ablility to plug into autopilot without encoder.<br />
* [http://www.robbe.de/empfaenger-r-6007-sp-2-4-g-rasst.html R6007SP 2,4 GHz RASST] - 7 channel, for small aircraft<br />
* [http://www.robbe.de/empf-r6107sp-2-4-ghz-rasst.html R6107SP 2,4 GHz RASST] - 7 channel, >1000m range<br />
* [http://www.robbe.de/empf-r6008sp-2-4-ghz-rasst.html R6008SP 2,4 GHz RASST] - 8 channel, upto 3000m range<br />
<br />
====Switch Assignment====<br />
<br />
To assign the three position switch to any other channel but channel 7 follow these steps:<br />
# Set up aux2(refers to aux2 on rx not the switch on the tx. aka ch7) with its input selected as 3 pos switch.<br />
# Set up this mix - Gear to Gear (Up=-100, Down=-100, Offset =0). This inhibits the gear switch.<br />
# Set up another mix - Aux2 to Gear (Up=100, Down=100, Offset = 0).<br />
Notes: <br />
#Gear on a DX-7 Air is Channel 5 and AUX2 is CH7. Once again i am referring to the inputs which are labeled on the RX not what the switches are named on the TX. If your using a DX-7 heli please substitute the names for what the rx channels are named into this guide<br />
# DX7 Heli the 3-pos switch is named "flight mode"<br />
# DX7 Air the 3-pos switch is named "flaps"<br />
<br />
====Failsafe Setup====<br />
<br />
To set up the mode channel (3 pos switch) to default to auto2 if connection is lost between rx and tx follow these steps:<br />
# Put 3 position Switch into AUTO2 Position<br />
# Put in bind plug<br />
# Power up<br />
# REMOVE the bind plug<br />
# Power up Tx while pushing bind button<br />
# Wait until light becomes steady and not blinking (it may become steady right off but will then start blinking again so let it go at least 5 seconds)<br />
<br />
==S.bus output==<br />
<br />
===S.bus to CPPM===<br />
<br />
Frsky has an [http://www.frsky-rc.com/product/pro.php?pro_id=112 SBUS to CPPM converter] which can be used with S.bus receiver e.g. [http://www.gpdealera.com/cgi-bin/wgainf100p.pgm?I=FUTL7661 R6303SB]<br />
<br />
====Failsafe====<br />
<br />
To properly get the LOST bit when the S.bus receiver is out of range a hack for lpc21 is to use the led signal of the receiver (if the color is changed/tuned off when the signal is lost) and put this to a GPIO input. Then define some parameters to turn this into RC_LOST signal.<br />
<br />
See sw/airborne/arch/lpc21/subsystems/radio_control/ppm_arch.h:54<br />
And for the airframe (for pin P0.17):<br />
<br />
{{Box Code|conf/airframes/myplane.xml|<br />
<source lang="xml"><br />
<subsystem name="radio_control" type="ppm"><br />
<define name="USE_PPM_RSSI_GPIO"/><br />
<define name="PPM_RSSI_IOPIN" value="IO0PIN"/><br />
<define name="PPM_RSSI_PIN" value="17"/><br />
<define name="PPM_RSSI_VALID_LEVEL" value="0"/><br />
</subsystem><br />
</source><br />
}}<br />
<br />
=MULTIPLEX=<br />
<br />
==CPPM output==<br />
<br />
===Jeti Duplex 2.4 GHz Receiver Rsat 2===<br />
<br />
[[Image:Jeti_Duplex_Rsat2.jpg|thumb|left|Jeti RSat 2]]<br />
* Outputs PPM, no soldering or PPM board required<br />
* Only 12 gramms<br />
* Full duplex technology provides safe radio link and redundant telemetry to standard paparazzi telemetry.<br />
* [http://www.jetimodel.cz/index.php?page=products&old=0&category=4 Transmitter module] can be installed in any receiver.<br />
<br />
More information can be found a the [http://www.jetimodel.cz/index.php?page=product&id=165 Homepage of Jeti] and the [http://www.mikrokopter.de/ucwiki/JetiDuplex MikroKopter Wiki].<br />
<br style="clear:both"><br />
<br />
=PCM Receivers=<br />
<br />
Most of the known PCM transmitter also can be set to PPM mode. If this is set, then the regular description for PPM applies since the PCM receiver like a JR/Gaupner SMC16 Scan can output PPM perfectly. <br />
<br />
However if setting up you transmitter to PPM out then the following applies:<br />
<br />
# Must use ppm encoder board. (See [[Get_Hardware|Get Hardware]] page for suppliers)<br />
# At least one extra channel beyond those needed to control the servos and motor.<br />
<br />
= PPM Receivers =<br />
<br />
To use a 26/27/35/40/41/72/ MHz receiver a few requirements are necessary<br />
<br />
# At least one extra channel beyond those needed to control the servos and motor.<br />
# A receiver or modified receiver which outputs a full ppm signal.<br />
<br />
== R/C Receiver Interface==<br />
<br />
All versions of the Paparazzi autopilot include a connector to interface with a standard R/C receiver for manual or semi-autonomous control during the testing and tuning phases. Two interface options exist:<br />
# Tap into the PPM signal running between the RF section and the servo driver of your receiver and route it to the Paparazzi. Let the Paparazzi generate individual servo signals and connect all servos directly to the autopilot. This method requires only 3 wires to the receiver (power and PPM), is compatible with all Paparazzi autopilots, and provides 8 manual R/C channels and the potential for more autonomous channels regardless of the capability of the R/C receiver.<br />
# Cut the PPM trace and route it thru the autopilot and back to the receiver, using the servo driver IC on your R/C receiver to drive the servos. This option requires 4 wires (Ground, PPM-in, PPM-out, Reset) and your receiver must have a supported servo driver IC. This allows you to use the large servo connectors on your R/C receiver and does not require any modification to your servos or ESC but does require you to cut a trace on your R/C receiver and limits the number of servos to the capacity of your receiver. Compatible with Classix and Tiny 1.1.<br />
# Note that on the Classix the PPM_in pin is FOO2... <br />
<br />
Note 1: Exact value not critical. Depending on RC Transmitter type & Manufacturer.<br><br />
Note 2: Depending on Transmitter number of Channels and t,,n,, durations.<br><br />
Note 3: Not critical. Depending on Synchro detection method.</small>]]<br />
<br />
<gallery><br />
Image:RC_Receiver_Timing_Diagram.jpg||PPM Timing Diagram<br />
Image:RC_Receiver_Tiny.jpg|3-Wire setup, driving servos from the autopilot<br />
Image:RC_Receiver_classix.jpg|4-Wire setup, driving servos from the R/C receiver<br />
</gallery><br />
<br style="clear:both"><br />
<br />
=== Common demux chips ===<br />
<br />
Typical used chips are the cmos [http://www.doctronics.co.uk/4015.htm 4015] and [http://www.doctronics.co.uk/4017.htm 4017]. <br />
<br />
The 4015 uses either pin 1 or pin 9 for the clock and the input is on 7 and 15. The 4017 has just one shift register and has its clock input on pin 14 and the enable on pint 13.<br />
<br />
In most receivers you are after the clock; though some may be pulsed; in which case you need the enable. Note that the 4017 enable has inverted logic (low to be enabled) whereas the input on the 4015 can be either (typically high). If the enable pin is held low (4017) or if the input pin (4015) is held high always;e.g. connected to the ground or the Vcc - then it is fair to assume that the PPM signal is most propably on the clock input. <br />
<br />
== 35/40Mhz RC Receivers ==<br />
<br />
Note that there is information on modifying other receiver models at [http://mikrokopter.de/ucwiki/RC-Empf%C3%A4nger mikrokopter.de]. It's in German however the pictures contain most of the information or use google translate.<br />
Shielded wire is recommended for receiver and autopilot connection, as unshielded one may cause noise in receiver. <br />
<br />
=== Futaba FP-R116FB 6 Channel FM 35MHz receiver ===<br />
<br />
[[Image:Rc_fut_web.jpg|thumb|left|Wiring of a Futaba R136]]<br />
*Orange wire is connected to PPM signal<br />
*Red wire is connected to VCC<br />
*Brown wire is connected to GND<br />
<br style="clear:both"><br />
<br />
=== Futaba R136F 6 Channel FM receiver ===<br />
<br />
[[Image:rx_futaba136.jpg|thumb|left|Wiring of a Futaba R136]]<br />
*41 MHz<br />
*White wire is connected to PPM signal<br />
<br style="clear:both"><br />
<br />
=== Futaba R168DF 8 Channel dual FM receiver ===<br />
<br />
[[Image:rx_futaba168df.jpg|thumb|left|Wiring of a Futaba R168DF]]<br />
*35 MHz<br />
*PPM wire is connected to 862 receiver pin on the board. VCC and GND is on the 8/B original position.<br />
<br style="clear:both"><br />
<br />
=== ACT Micro-6 FM receiver ===<br />
<br />
[[Image:rx_act_micro-6.jpg|thumb|left|Wiring of a ACT Micro-6]]<br />
*Available in 35 or 40 MHz versions<br />
*White wire is connected to PPM signal<br />
*[http://www.acteurope.com/Micro_6anl.pdf Datasheet (German)]<br />
<br style="clear:both"><br />
<br />
=== ACT DSL-4top [http://www.mikrokopter.de/ucwiki/DSL4top mikrokopter.de] version ===<br />
<br />
[[Image:DSL4top.jpg|thumb|left|DSL-4top mikrokopter.de version]]<br />
* Special version for mikrokopter.de - Only available in their [https://www.mikrocontroller.com/index.php?main_page=product_info&products_id=215&zenid=8ce8bab70f3e9d684e01f724316d9690 shop]!<br />
* '''Outputs PPM directly''' on the channel 1 connector!<br />
* No soldering necessary<br />
* ACT Lifetime warranty<br />
* Sells for ~45 euro<br />
<br style="clear:both"><br />
<br />
=== Futaba R115F 5 Channel FM receiver ===<br />
<br />
[[Image:pprz_rx115.jpg|thumb|left|Wiring of a Futaba R115]]<br />
*Available in 35 and 40 MHz versions<br />
*White wire is connected to PPM signal<br />
<br style="clear:both"><br />
<br />
=== JETI REX 5 plus (no MPD) receiver ===<br />
<br />
[[Image:520_Jeti_5_plus.jpg|thumb|left|Wiring of a REX 5]]<br />
<br />
*Popular Czech made micro r/c receiver, available in 35 or 40 MHz versions<br />
*´folded´ PCB design with parts inside, mostly inaccessable<br />
*Small grey wire is connected to via with PPM signal<br />
*Unusual connector used for testing, soldering recommended<br />
*shielded wire recommended, this one taken from PC parts recycling (former soundcard to m/b connector cable)<br />
*[http://www.jetimodel.cz/eng/navody_en/rex5_eng.pdf Datasheet (English)]<br />
<br style="clear:both"><br />
[[Image:DSC02414.JPG|thumb|left|other Layout of REX 5]]<br />
<br />
=== Receiver RX-7-SYNTH IPD receiver [http://www.multiplex-rc.de/hp/produkte/artikel_detail.jsp?lfdnr=55880&action=add2notice&qty=1&cachenepper=1227896925116 Multiplex-rc.de] ===<br />
<br />
[[Image:RX-7-SYNTH_IPD.jpg|thumb|left|Wiring of RX-7-SYNTH IPD]]<br />
<br />
*Available in 35, 36 and 40 MHz versions<br />
*A compact, high-quality 7-channel single-conversion FM / PPM IPD receiver<br />
*Easy modification through connectors, see pictures<br />
<br style="clear:both"><br />
<br />
=== Protech 5FM 35 mHz Receiver ===<br />
<br />
The low cost Protech '5FM' receiver makes use of an SMD version of the standard 74AHC164[http://www.ic-on-line.cn/IOL/datasheet/74ahct164_18057.pdf] 8 bit shift register; you are after PIN 1 of this chip. The circuit board has a testpad for just this pin at the top side of the circuit board.<br />
<br />
<gallery><br />
Image:protech-5fm.jpg|Figure 1. <br>Protech 5FM 35 mHZ Receiver, mark 2<br />
Image:protech-5fm-pad.jpg|Figure 2. <br> PPM tap location for the Protech 5FM receiver, near the 74AHC164 shift register<br />
Image:protech-5fm-scope.jpg|Figure 3.<br> Protech 5FM PPM signal - not very clean/digital<br />
</gallery><br />
<br />
Two physical versions exist; the older one [http://www.protech.be/Manuals/PRO205manual%20web.pdf] and a newer one pictured (fig 1). It has been distributed by protech with various ready-to-fly planes; such as the Skyraider[http://www.modelbouwforum.nl/forums/beginners/50677-protech-skyraider.html].<br />
<br />
The solder/testpad you are after the one right next the 74x164 chip its pin 1. In this image it has a jellow wire soldered to it (the yellow wire at the top left is the normal antenna connector (fig 2). Note however that the signal is not very clean (1v/div) - which may cause issues - as shown in the above image (fig 3). <br />
<br />
This is further compunded by the relatively noisy electrical engines; which are not brushless. A ferrite coil does not seem to help enough - Papparazi and GPS loose sync often through Xbee. Replacing the engine by a brushless outrunnen resolve the issue completely.<br />
<br />
=== Profi Penta 35 MHz ===<br />
<br />
<gallery><br />
Image:DSC00547.JPG<br />
Image:DSC00545.JPG<br />
</gallery><br />
<br />
<br />
=== Graupner R16Scan ===<br />
<br />
The Graupner R16Scan and SMC16Scan are available in 35,36,40,41Mhz versions and belongs to one of the most reliable traditional receivers in it's class. It's a highly selective PLL SCAN narrow-band FM superhet receiver. Has 8 servo connections. And the best thing; No crystals swap is required with this receiver since it scans for your TX transmission frequency. Modified for PPM output, it can output 9 separate channels.<br />
<br />
To modify this receiver for use with an autopilot some soldering on tiny IC pins is needed. No additional electronic parts needed. <br />
<br />
# Desolder existing resistor from IC pin, fast and carefully<br />
# solder a short wire to the pin on the other side of the IC as on the picture, preferably als put some isolation over it<br />
# Solder this wire to the resistor, move isolation over resistor<br />
# Use a little UHU por glue to make sure nothing moves when flying in rought conditions<br />
<br />
The PPM combined data is now available on connector 8. You still can power the receiver seperatly via + - pins if you want to. Or straight from the AP board 5v out.<br />
<br />
<gallery><br />
Image:Graupner_R16Scan_pwm_modification_01.jpg|How to modify<br />
Image:Graupner_R16Scan_pwm_modification_02.jpg|Modification from other side<br />
Image:Graupner_R16Scan_pwm_modification_03.jpg|Modification Closeup<br />
Image:Graupner_R16Scan_pwm_modification_04.jpg|Well... why not change them all in one go.<br />
</gallery><br />
<br />
== 72Mhz Receivers ==<br />
<br />
=== Castle Creations [http://www.castlecreations.com/products/berg_ms4l.html Berg 4L] ===<br />
<br />
[[Image:berg4L.jpg|thumb|left|Wiring of a Berg 4L]]<br />
* Expect fantastic performance from these $40 USD parts but be warned that they are known to have unreliable crystal sockets and brittle antenna wire. The ''Berg 7'' channel receiver should work equally well and is known to have a better crystal socket - note that either receiver will provide '''8 channels''' in manual R/C mode when used with Paparazzi. Note: the rugged ''Berg 4'' cannot be modified, only the ''Berg 4L'' and ''Berg 7''.<br />
<br />
To Modify a Berg4L, follow these instructions:<br />
# Remove the shrink wrap. Use a good knife and be careful to not damage any of the components on the receiver. I would recommend that you cut on the sides (edge of the PCB) to be sure to avoid damaging the shielding<br />
# Desolder the headers. We will not use them with tiny AP as the servos are connected directly to the AP. This is pretty easy to do when you have a hot air rework station. If you don't have one, your best bet is to cut the header off and remove the left over pins one by one with a regular iron. There is a piece of shielding material that is connected to one of the ground pins of the header. You need to remove it carefully from the header without damaging it and re-solder it to the gnd pad.<br />
# You need to solder 3 wires to the receiver. Gnd, +5V and PPM. To locate the PPM signal, first locate the PIC micro controller close to the location of the headers. The PPM signal is on the corner pin closest to the corner of the receiver. Soldering a 28guage wire directly to the PIN isn't very difficult. For the power connection, use the pads that were used for the header. The outside pin is Gnd, the second pin is +5V. What I did is solder the wires on the pad going straight down, then I looped the 3 wires 360 degrees and glued them to the PCB with hot glue. This provides good strain relief.<br />
# While you have the PCB in your hands, take the opportunity to remove the crystal connector and solder your crystal directly to the PCB for added reliability.<br />
# I also used some hot glue to add more strain relief to the antenna<br />
# Use some large shrink wrap to cover the entire receiver again<br />
<br style="clear:both"><br />
<br />
=== Hitec Electron 6 72MHz Reciever ===<br />
<br />
This was written for MNAV from crossbow but is still usable with PPRZ.<br />
<br />
[[Image:Electron6mod.jpg|thumb|left]]<br />
<br style="clear:both"><br />
<br />
=== Corona Synthesized Dual-Conv Receiver 8Ch ===<br />
<br />
[http://www.corona-rc.com/coproductshowE.asp?ArticleID=63 manual]<br />
<br />
This receiver is available in 27,35,36,40,72 mhz and a Synthesized receiver, meaning you do not need to change frequency crystals.<br />
<br />
How to modify for combined signal<br />
<br />
# Cut the 8th channel PWM output pin near the PCB.<br />
# Connected a pin from the Atmel (see picture) to the 8th channel PWM signal. (optionally, weaving the wire through some holes on the board.) Make sure you have a fine tip on your soldering iron and a magnifying glass strapped to your head! <br />
# Glue the wire down (CA works)<br />
# Be sure to glue the pin that you cut in place (previously, being soldered to the board was holding the pin in place)<br />
<br />
It is maybe possible to reprogram the atmel with your own firmware. If you succeed in this plz add relevant info here.<br />
<br />
That pin provides a 1V to 2V signal, it works with the PPRZ, although its a bit gittery (the slew rate is not real good).<br />
<gallery><br />
Image:Corona_Synthesized_Receiver_72Mhz_bottom.jpg<br />
Image:Corona_Synthesized_Receiver_72Mhz_top.jpg<br />
Image:Corona_Synthesized_Receiver_72Mhz_top_atmel.jpg<br />
</gallery><br />
<br style="clear:both"><br />
<br />
= UHF Receivers =<br />
<br />
Note that in most countries an amateur radio license is required to use 433MHz UHF.<br/><br />
See also [[Modems#HAM_.2F_CEPT_Licence]].<br />
<br />
== Scherrer UHF ==<br />
[[Image:ScherrerUHF.jpg|thumb|left|Scherrer UHF Rx]]<br />
<br />
The [http://www.webx.dk/rc/uhf-link3/uhf-link3.htm Scherrer UHF] is a high quality diversity radio control system. It has a PPM output and can be connected directely to Paparazzi. A ppm encoder board is not required. It has an RSSI output.<br />
<br style="clear:both"><br />
<br />
== ImmersionRC EzUHF ==<br />
[[Image:EzUHFTx.jpg|thumb|left|ImmersionRC Tx]]<br />
<br />
The [http://www.immersionrc.com/products.htm ImmersionRC EzUHF] is a high quality diversity radio control system. The recent firmwares have a PPM output on Ch. 1, but this needs to be activated through the PC configuration software with the proper firmware loaded. It connects directly to EzOSD and the TrackR2 which enables RSSI monitoring and head tracking for FPV.<br />
<br />
Some people had issues with the exact timing, where the ROLL channel disappeared. If the radio has more than 6 channels, there may be methods to slave another channel to the roll channel (usually for the operation of dual ailerons). The ezuhf configuration file is using this method, where channel 1 is copied to channel 6. The EzUHF modules receive the PPM output stream from the radio and need to interpret it. For this reason, the ezuhf configuration file should be verified for proper functioning and you may find that channels are remapped to others with different purposes.<br />
<br />
Search "sander style" antennas for a way to build your own cheap, high-quality antennas for these rx modules and which provide a range well beyond the horizon.<br />
<br />
See [http://www.immersionrc.com/EzUHF.htm EzUHF manual+firmware] for more information.<br />
<br style="clear:both"><br />
<br />
==OrangeRx Open LRS 433MHz 9Ch Receiver==<br />
No Image? Indeed, if you have this device, plz upload a photo.<br />
<br />
Via a firmware update this receiver is capable of CPPM output on Pin 5. A good option if you need very long range RC control. If you are able, it is posible to wriggle telemetry output in return for this module also. The Paparazzi Team has not tried it. So if you want to land up in the PPRZ hal of fame, try it and report back, that would be awesome!<br />
<br />
<br style="clear:both"><br />
<br />
= Radios=<br />
<br />
The word radio here is a RC Transmitter (TX), nothing to do with a device to liten to your favorite music channel. Opensource enthousiasts as we are, there are also various opensource based RC transmiitter for even more flexibility.<br />
We won't advise of specific brand here, the only keyword here is reliability. For 100% autonomous flight one could argue, no RC transmitter is needed. That is true, but experience shows that it is better to have a backup control device.<br />
<br />
[[Category:Hardware]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=FlightGear&diff=19077FlightGear2014-10-23T16:52:53Z<p>Christoph: </p>
<hr />
<div><categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Simulation</categorytree><br />
__TOC__<br />
<br />
FlightGear Flight Simulator.<br />
<br />
See http://www.flightgear.org/<br />
<br />
== Installation ==<br />
<br />
=== Debian/Ubuntu ===<br />
The standard Debian/Ubuntu repositories contain FlightGear 2.4 or 2.6.<br />
<br />
The latest edition of FlightGear is available from Launchp PPA (contributed by Saikrishna Arcot).<br />
<br />
Install flightgear:<br />
sudo add-apt-repository ppa:saiarcot895/flightgear<br />
sudo apt-get update<br />
sudo apt-get install flightgear<br />
<br />
==== From source ====<br />
<br />
A great page to read in case you want to install Flightgear from source [http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu can be found here]<br />
<br />
== Adding Paparazzi models ==<br />
There are a few new models that come with paparazzi:<br />
* ''mikrokopter.xml'' quadrotor frame<br />
* ''hexa.xml'' hexacopter<br />
* ''simple_bipe.xml'' biplane/quadrotor hybrid (transitioning vehicle)<br />
<br />
To make them available in flightgear, make a link from ''/usr/share/games/flightgear/Models/Aircraft/paparazzi'' to ''<paparazzi_dir>/conf/simulator/flightgear/''<br />
sudo ln -s $PAPARAZZI_SRC/conf/simulator/flightgear/ /usr/share/games/flightgear/Models/Aircraft/paparazzi<br />
<br />
== Using FlightGear for Visualization ==<br />
For Flight Gear visualization of the simulation, version 2.6 or greater is best. If you wish to use version 2.4 or lower, you must add the following to the firmware section of your airframe file:<br />
{{Box Code|conf/airframes/myplane.xml|<br />
<source lang="xml"><br />
<firmware name="fixedwing or rotorcraft"><br />
...<br />
<define name="FG_2_4" value="1"/><br />
...<br />
</firmware><br />
</source><br />
}}<br />
<br />
* Launch Flight Gear with the following command:<br />
fgfs --fdm=null --native-gui=socket,in,30,,5501,udp<br />
or to e.g. use the mikrokopter quadrotor model:<br />
fgfs --fdm=null --native-gui=socket,in,30,,5501,udp --prop:/sim/model/path=Models/Aircraft/paparazzi/mikrokopter.xml<br />
<br />
== Loading scenery data ==<br />
Using [http://wiki.flightgear.org/TerraSync TerraSync] you can let FlightGear automatically download scenery for where you are flying in the background. Add the '''--enable-terrasync''' option, e.g<br />
fgfs --fdm=null --native-gui=socket,in,30,,5501,udp --prop:/sim/model/path=Models/Aircraft/paparazzi/mikrokopter.xml --enable-terrasync<br />
It seems to be a good idea, to start fgfs with terrasync first, let it initialize and start the sim then, otherwise fgfs sometimes won't start.<br />
<br />
[[Category:Simulation]] [[Category:Software]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Lisa/Bone&diff=18490Lisa/Bone2014-04-16T11:20:20Z<p>Christoph: /* Use cases */</p>
<hr />
<div>Lisa/Bone is a project consisting in designing a Paparazzi [http://beagleboard.org/Products/BeagleBone+Black Beaglebone Black] cape.<br />
<br />
For now, this page is a placeholder for the definition of the board.<br />
<br />
<br />
== MCU or not MCU ==<br />
<br />
BeagleBone Black (BBB) has all the peripherals needed to make an autopilot (PWM, ADC, SPI, I2C, UARTS, Capture, etc...). The daughter board could just be a connectors, supply and aspirin carrier board. It would minimize cost and complexity, but we'd lose the possibility of segregating critical code. Discarded for that reason<br />
<br />
I suggest a 64 pins STM F4 (like in Lisa/M)<br />
<br />
We don't need level converters. BBB is happy with 3.3V IOs<br />
<br />
My current plan is to base the cape on Lisa/M, rework supply and connectors.<br />
NeoFromMatrix: Maybe we could use a MCU with more IO and 0805 parts.<br />
The cape should provide enough parts and 0805 is easier tosolder by hand. <br />
<br />
Communications between F4 and BBB is through SPI (BBB master, F4 slave) in order to have high bandwith<br />
<br />
Gautier says he wants UART communications: <br />
can you justify and specify which UART of the F4 you'd use ?<br />
My argument against it is that UARTs are a scarce resource on the F4 - SPI is easy on BBB, from userland using SPIdev ( [http://elinux.org/BeagleBone_Black_Enable_SPIDEV see here]) <br />
On F4, Lisa/L's SPI code can be reused. This code is well validated (or did it get broken by the change to libopencm?)<br />
<br />
=> UART comminucation is still easier to use expecially for new-comers. It is also sufficient for high-level operations (controlling at navigation level) from the BB.<br />
SPI code on MCU side has changed a lot since Lisa/L, I wouldn't bet it is still working.<br />
I really don't care which UART is used.<br />
<br />
== Connectors ==<br />
<br />
Let's start from Lisa/M connectors. We have a little bit more space available<br />
- I would like 10 full size servo connectors - supply bus isolated<br />
<br />
NeoFromMatrix: how about 0.1" headers ? They are easier to solder by hand and molex connectors cost a bit...<br />
<br />
== Supply ==<br />
<br />
-If we're going for the code segregation thing, it makes sense to have two independent rails: one non-critical for BBB and one critical for F4<br />
<br />
-I would like to be able to power the whole thing from 3/4S flight pack<br />
<br />
-Should we go for the PTH8080 that were used on Lisa/L, a pair of them?<br />
<br />
-Any idea for a good connector for input supply ? Or do we just skip that and go for beefy solder pads as usual?<br />
<br />
-Beagle has the possibility to run on one lipo cell and has a chip capable of charging it from the 5V supply ( [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2013/08/10/bbb--rechargeable-on-board-battery-system see here] )<br />
Should we implement something like this to allow changing the vehicle's battery pack without having to shutdown the autopilot (or switch from lab power supply to flight pack) ?<br />
1400mAh give ~3h endurance and weights 25g, 500mAh is 10g<br />
Discarded, Bryan says it doesn't work<br />
<br />
== Misc ==<br />
<br />
-We want a push button for triggering BBB shutdown - maybe with a molex to be able to mount a button in a convenient place when in airframe (P9-9 to ground [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2014/03/05/bbb--sonos-like-sound-system see here])<br />
<br />
-If linux system is setup properly you will not have to shutdown the BB. You will be able to just pull power with no issues.<br />
<br />
-Maybe one or two GPIO in order to have status leds next to the button?<br />
<br />
-Do we want to be able to flash F4 from BBB?<br />
<br />
NeoFromMatrix: That would be nice.<br />
<br />
== Communications ==<br />
<br />
* BBB drives the xbee and tunnels communications to F4. Bad, we lose advantage of code segregation <br />
* BBB and F4 each have a xbee. Bad, we increase weight and power consumption :) <br />
* for short distances (rotorcraft), BBB through wifi(Bryan-wifi is not hard real time), F4 through wifi<br />
* BBB communicates throught internet stick, BBB forwards data to F4 <br />
* BBB uses internet stick, F4 uses xbee -> redundant communication, interent stick could be used for image/video<br />
* BBB to F4 SPI interconnect, for doing some things as userprocesss on BBB and realtime stuff on the F4<br />
* CAN has built in data framing and CRC with many-master-many-slave type data system.<br />
Lisa/M (the F4 board) has one can driver. Do we want to add a second driver for the BBB?<br />
<br />
== Use cases ==<br />
<br />
Let's describe a couple of scenarios of what we would do with that board:<br />
<br />
* I want to investigate autonomous soaring. F4 runs the current fixedwing code. BBB runs the autonomous soaring program written in Python/Numpy and talks to the navigation layer running on F4. BBB receives every sensor measurement, state estimation and actuators command from F4, for real time use and logging.<br />
<br />
* Someone runs image processing on BBB (using a usb webcam?) and current rotorcraft code in F4 - similar to case 1<br />
<br />
* OpenCV onboard for motion tracking and 2d ground tracking for extra stability systems.<br />
<br />
Does image processing require some kind of fancy camera with a fancy interface, or is USB good enough? BBB only has one USB... so webcam, or wifi, or hub.. <br />
Bryan: Cheap USB-webcam would be all we would need.<br />
<br />
Do we want a USB hub on the daughterboard - i would say no, keep it cheap and simple<br />
Bryan: We may be able to enable host mode on USB0 and get use of both USB0 and USB1 on the board.<br />
<br />
* Run code, used for research topics (maybe generated from Matlab/Simulink) on the BBB and let the F4 fly the plane and do the basic (realtime) stuff<br />
<br />
* What else?<br />
<br />
[[Category:Lisa]] [[Category:Autopilots]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Lisa/Bone&diff=18489Lisa/Bone2014-04-16T11:18:32Z<p>Christoph: /* Communications */</p>
<hr />
<div>Lisa/Bone is a project consisting in designing a Paparazzi [http://beagleboard.org/Products/BeagleBone+Black Beaglebone Black] cape.<br />
<br />
For now, this page is a placeholder for the definition of the board.<br />
<br />
<br />
== MCU or not MCU ==<br />
<br />
BeagleBone Black (BBB) has all the peripherals needed to make an autopilot (PWM, ADC, SPI, I2C, UARTS, Capture, etc...). The daughter board could just be a connectors, supply and aspirin carrier board. It would minimize cost and complexity, but we'd lose the possibility of segregating critical code. Discarded for that reason<br />
<br />
I suggest a 64 pins STM F4 (like in Lisa/M)<br />
<br />
We don't need level converters. BBB is happy with 3.3V IOs<br />
<br />
My current plan is to base the cape on Lisa/M, rework supply and connectors.<br />
NeoFromMatrix: Maybe we could use a MCU with more IO and 0805 parts.<br />
The cape should provide enough parts and 0805 is easier tosolder by hand. <br />
<br />
Communications between F4 and BBB is through SPI (BBB master, F4 slave) in order to have high bandwith<br />
<br />
Gautier says he wants UART communications: <br />
can you justify and specify which UART of the F4 you'd use ?<br />
My argument against it is that UARTs are a scarce resource on the F4 - SPI is easy on BBB, from userland using SPIdev ( [http://elinux.org/BeagleBone_Black_Enable_SPIDEV see here]) <br />
On F4, Lisa/L's SPI code can be reused. This code is well validated (or did it get broken by the change to libopencm?)<br />
<br />
=> UART comminucation is still easier to use expecially for new-comers. It is also sufficient for high-level operations (controlling at navigation level) from the BB.<br />
SPI code on MCU side has changed a lot since Lisa/L, I wouldn't bet it is still working.<br />
I really don't care which UART is used.<br />
<br />
== Connectors ==<br />
<br />
Let's start from Lisa/M connectors. We have a little bit more space available<br />
- I would like 10 full size servo connectors - supply bus isolated<br />
<br />
NeoFromMatrix: how about 0.1" headers ? They are easier to solder by hand and molex connectors cost a bit...<br />
<br />
== Supply ==<br />
<br />
-If we're going for the code segregation thing, it makes sense to have two independent rails: one non-critical for BBB and one critical for F4<br />
<br />
-I would like to be able to power the whole thing from 3/4S flight pack<br />
<br />
-Should we go for the PTH8080 that were used on Lisa/L, a pair of them?<br />
<br />
-Any idea for a good connector for input supply ? Or do we just skip that and go for beefy solder pads as usual?<br />
<br />
-Beagle has the possibility to run on one lipo cell and has a chip capable of charging it from the 5V supply ( [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2013/08/10/bbb--rechargeable-on-board-battery-system see here] )<br />
Should we implement something like this to allow changing the vehicle's battery pack without having to shutdown the autopilot (or switch from lab power supply to flight pack) ?<br />
1400mAh give ~3h endurance and weights 25g, 500mAh is 10g<br />
Discarded, Bryan says it doesn't work<br />
<br />
== Misc ==<br />
<br />
-We want a push button for triggering BBB shutdown - maybe with a molex to be able to mount a button in a convenient place when in airframe (P9-9 to ground [http://www.element14.com/community/community/knode/single-board_computers/next-gen_beaglebone/blog/2014/03/05/bbb--sonos-like-sound-system see here])<br />
<br />
-If linux system is setup properly you will not have to shutdown the BB. You will be able to just pull power with no issues.<br />
<br />
-Maybe one or two GPIO in order to have status leds next to the button?<br />
<br />
-Do we want to be able to flash F4 from BBB?<br />
<br />
NeoFromMatrix: That would be nice.<br />
<br />
== Communications ==<br />
<br />
* BBB drives the xbee and tunnels communications to F4. Bad, we lose advantage of code segregation <br />
* BBB and F4 each have a xbee. Bad, we increase weight and power consumption :) <br />
* for short distances (rotorcraft), BBB through wifi(Bryan-wifi is not hard real time), F4 through wifi<br />
* BBB communicates throught internet stick, BBB forwards data to F4 <br />
* BBB uses internet stick, F4 uses xbee -> redundant communication, interent stick could be used for image/video<br />
* BBB to F4 SPI interconnect, for doing some things as userprocesss on BBB and realtime stuff on the F4<br />
* CAN has built in data framing and CRC with many-master-many-slave type data system.<br />
Lisa/M (the F4 board) has one can driver. Do we want to add a second driver for the BBB?<br />
<br />
== Use cases ==<br />
<br />
Let's describe a couple of scenarios of what we would do with that board:<br />
<br />
* I want to investigate autonomous soaring. F4 runs the current fixedwing code. BBB runs the autonomous soaring program written in Python/Numpy and talks to the navigation layer running on F4. BBB receives every sensor measurement, state estimation and actuators command from F4, for real time use and logging.<br />
<br />
* Someone runs image processing on BBB (using a usb webcam?) and current rotorcraft code in F4 - similar to case 1<br />
<br />
* OpenCV onboard for motion tracking and 2d ground tracking for extra stability systems.<br />
<br />
Does image processing require some kind of fancy camera with a fancy interface, or is USB good enough? BBB only has one USB... so webcam, or wifi, or hub.. <br />
Bryan: Cheap USB-webcam would be all we would need.<br />
<br />
Do we want a USB hub on the daughterboard - i would say no, keep it cheap and simple<br />
Bryan: We may be able to enable host mode on USB0 and get use of both USB0 and USB1 on the board.<br />
<br />
<br />
* What else?<br />
<br />
[[Category:Lisa]] [[Category:Autopilots]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=STM32F4_Discovery&diff=18461STM32F4 Discovery2014-04-10T21:03:37Z<p>Christoph: /* Daughterboard */</p>
<hr />
<div>'''This page is for the [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery board with STM32F407VGT6], STM32F4 Disco is a familiar board with STM32F401VCT6, do not use this Files for the Disco board ! '''<br />
<br />
{| align=right<br />
|-<br />
|<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Autopilots</categorytree><br />
|}<br />
<br />
<div style="float: right; width: 65%"><br />
[[Image:STM32F4Discovery_front.jpg|300px]]<br />
[[Image:STM32F4Discovery_back.jpg|300px]]<br />
</div><br />
<br />
__TOC__<br />
<br />
<br />
==Overview==<br />
<br />
* STMicroelectronics STM32F4VGT6 Cortex M4 MCU, up to 168Mhz with floating point unit (FPU), 192 KB RAM, 1024 KB Flash<br />
* on-board STLinkv2 with SWD header (capable of programming onboard or external MCU)<br />
* on-board power regulator for the MCU (3V or 5V Input)<br />
* 1 x user push button<br />
* 4(5) x LED (orange, green, red, blue, green) <br />
* 4(6) x UART (UART1, UART2, UART3, (UART4, UART5), UART6)<br />
* 1(3) x SPI (SPI1, (SPI2, SPI3))<br />
* 2(3) x I2C (I2C1, I2C2, (I2C3))<br />
* 6 x ADC inputs (one is used for BAT voltage)<br />
* 1 x PPM input<br />
* 1 x Spektrum input (with bind pin)<br />
* 97 x 66 mm PCB<br />
* 4 x status LED (USB red, USB green, power, USB OTG green, USB OTG red)<br />
* LIS302DL MEMS 3 axis accelerometer on SPI1<br />
<br />
== Pinout ==<br />
<br />
[[Image:Stm32f4_discovery_left_bank.png|thumb|right|300px|left pin bank in relation to paparazzi(not up to date!)]]<br />
[[Image:Stm32f4_discovery_right_bank.png|thumb|right|300px|right pin bank in relation to paparazzi(not up to date!)]]<br />
The Discovery has a male 100 pin (2x25pin on both sides, also accessible on both sides of the pcb) pinout. <br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''LED'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''!!width="5%"|''Color''<br />
|-<br />
|PD13||LED_3||Out||above LIS302DL||style="background:orange; color:black"|Orange<br />
|-<br />
|PD12||LED_4||Out||left of LIS302DL||style="background:green; color:black"|Green<br />
|-<br />
|PD14||LED_5||Out||right of LIS302DL||style="background:red; color:black"|Red<br />
|-<br />
|PD15||LED_6||Out||below LIS302DL||style="background:blue; color:black"|Blue<br />
|-<br />
|PA9||LED_9||Out||same as USB power (VBUS, needs to be enabled in header file||style="background:green; color:black"|Green<br />
|} <br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB6||UART1 TX||Out||UART1 Serial Output, 4k7 pullup for I2C<br />
|-<br />
|PB7||UART1 RX||In||UART1 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD5||UART2 TX||Out||UART2 Serial Output<br />
|-<br />
|PD6||UART2 RX||In||UART2 Serial Input, also used for Spektrum input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART3'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD8||UART3 TX||Out||UART3 Serial Output<br />
|-<br />
|PD9||UART3 RX||In||UART3 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART4 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||UART4 TX||Out||UART4 Serial Output<br />
|-<br />
|PC11||UART4 RX||In||UART4 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART5 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC12||UART5 TX||Out||UART5 Serial Output<br />
|-<br />
|PD2||UART5 RX||In||UART5 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART6'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC6||UART6 TX||Out||UART6 Serial Output<br />
|-<br />
|PC7||UART6 RX||In||UART6 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1 (for onboard LIS302DL)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA5||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PA6||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PA7||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB3||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PB4||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PB5||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI2 (Can NOT be used if PWM10 & PWM11 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB13||SPI2 SCK||I/O||SPI2 Serial clock<br />
|-<br />
|PB14||SPI2 MISO||I/O||SPI2 Master In Slave Out<br />
|-<br />
|PB15||SPI2 MOSI||I/O||SPI2 Master Out Slave In<br />
|-<br />
|PE7||SPI SS1||I/O||SPI2 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI3 (Can NOT be used if UART4 & UART5 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||SPI3 SCK||I/O||SPI3 Serial clock<br />
|-<br />
|PC11||SPI3 MISO||I/O||SPI3 Master In Slave Out<br />
|-<br />
|PC12||SPI3 MOSI||I/O||SPI3 Master Out Slave In<br />
|-<br />
|PE3||SPI SS2||I/O||SPI3 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB8||I2C1 SCL||I/O||I2C1 Serial Clock<br />
|-<br />
|PB9||I2C1 SDA||I/O||I2C1 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB10||I2C2 SCL||I/O||I2C2 Serial Clock<br />
|-<br />
|PB11||I2C2 SDA||I/O||I2C2 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C3 (Can NOT be used if Spektrum bind / PPM input is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||I2C3 SCL||I/O||I2C3 Serial Clock<br />
|-<br />
|PC9||I2C3 SDA||I/O||I2C3 Serial Data<br />
|}<br />
Note: is disabled in header file, PA8 is used as Spektrum bind pin, PC9 is used as PPM (not Spektrum) input<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''ADC'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB1||AUX1||I/O||ADC_1<br />
|-<br />
|PC5||AUX2||I/O||ADC_2<br />
|-<br />
|PC4||AUX3||I/O||ADC_3<br />
|-<br />
|PA4||BAT||I/O||ADC_4, is used for BAT voltage<br />
|-<br />
|PC1||AUX5||I/O||ADC_5<br />
|-<br />
|PC2||AUX6||I/O||ADC_6<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PWM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PE9||PWM0||Out||Servo 1<br />
|-<br />
|PE11||PWM1||Out||Servo 2<br />
|-<br />
|PE13||PWM2||Out||Servo 3<br />
|-<br />
|PE14||PWM3||Out||Servo 4<br />
|-<br />
|PE5||PWM4||Out||Servo 5<br />
|-<br />
|PE6||PWM5||Out||Servo 6<br />
|-<br />
|PA3||PWM6||Out||Servo 7<br />
|-<br />
|PA2||PWM7||Out||Servo 8<br />
|-<br />
|PA1||PWM8||Out||Servo 9<br />
|-<br />
|PA0||PWM9||Out||Servo 10<br />
|-<br />
|PB14||PWM10||Out||Servo 11, Can not be used if SPI2 is active<br />
|-<br />
|PB15||PWM11||Out||Servo 12, Can not be used if SPI2 is active<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PPM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC9||PPM||In||PPM input (remember, you need 100 Ohm serial termination in order to use this) <br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Spektrum'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||Bind||Out||Spektrum bind pin<br />
|-<br />
|PA10||PPM||IN||Spektrum PPM in<br />
|}<br />
<br />
<br />
=== Jumper ===<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|JP1||JP1||Switch||MCU Current can be measured here<br />
|-<br />
|CN3||CN3||Switch||closed: STLinkV2 is connected to onboard MCU, open: is not connectec to onboard, only external header<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Soolder Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|SB17||SB17||Switch||Bypass for JP1, close this for security ! (if JP1 gets loose)<br />
|}<br />
<br />
==Daughterboard==<br />
<br />
comming soon :) [https://github.com/NeoFromMatrix/stm32f4discovery_daughterboard git repo]<br />
<br />
Components:<br />
<br />
Diode: Standard types (like 1N4007) will work<br/><br />
Resistors: 2k2 and 22k, 0,1%<br/><br />
Caps: Low ESR type, 10-50µF<br/><br />
<br />
Another option with Molex connectors, levelshifters for I2C and SPI, as well as connectors for Spektrum satellites and a can phy would be:<br />
<br />
[[Image:DiscoveryBreakout1_small.jpg|300px]]<br />
[[Image:DiscoveryBreakout2_small.jpg|300px]]<br />
<br />
Currently under testing, eagle files are coming, when its completely finished and airworthy :-)<br />
<br />
==Firmware Flashing==<br />
<br />
'''FLASH_MODE=STLINK''' is set as default<br />
<br />
STM32F4 Discovery can mainly be programmed in two different ways:<br />
<br />
===STLINK===<br />
<br />
* with onboard STLinkV2 over SWD<br />
* required hardware: usb to mini USB cable<br />
* required software: st_flash and st_util from [https://github.com/texane/stlink Texane]<br />
* more information: [[STLink]] page<br />
<br />
===DFU-UTIL===<br />
<br />
* with the MCU native (embedded in rom) DFU USB bootloader over the micro USB AB connector<br />
* required hardware: USB to micro and USB to mini usb cable <br />
* required external software: dfu-util <br />
* push MCU in DFU mode: connect mini(for power) and micro USB to PC, connect pin BOOT0 with 3V, press reset button(LED LD7 should light up now), disconnect BOOT0<br />
* more information: [[DFU]] page<br />
<br />
[[Category:Autopilots]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=STM32F4_Discovery&diff=18460STM32F4 Discovery2014-04-10T21:01:17Z<p>Christoph: </p>
<hr />
<div>'''This page is for the [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery board with STM32F407VGT6], STM32F4 Disco is a familiar board with STM32F401VCT6, do not use this Files for the Disco board ! '''<br />
<br />
{| align=right<br />
|-<br />
|<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Autopilots</categorytree><br />
|}<br />
<br />
<div style="float: right; width: 65%"><br />
[[Image:STM32F4Discovery_front.jpg|300px]]<br />
[[Image:STM32F4Discovery_back.jpg|300px]]<br />
</div><br />
<br />
__TOC__<br />
<br />
<br />
==Overview==<br />
<br />
* STMicroelectronics STM32F4VGT6 Cortex M4 MCU, up to 168Mhz with floating point unit (FPU), 192 KB RAM, 1024 KB Flash<br />
* on-board STLinkv2 with SWD header (capable of programming onboard or external MCU)<br />
* on-board power regulator for the MCU (3V or 5V Input)<br />
* 1 x user push button<br />
* 4(5) x LED (orange, green, red, blue, green) <br />
* 4(6) x UART (UART1, UART2, UART3, (UART4, UART5), UART6)<br />
* 1(3) x SPI (SPI1, (SPI2, SPI3))<br />
* 2(3) x I2C (I2C1, I2C2, (I2C3))<br />
* 6 x ADC inputs (one is used for BAT voltage)<br />
* 1 x PPM input<br />
* 1 x Spektrum input (with bind pin)<br />
* 97 x 66 mm PCB<br />
* 4 x status LED (USB red, USB green, power, USB OTG green, USB OTG red)<br />
* LIS302DL MEMS 3 axis accelerometer on SPI1<br />
<br />
== Pinout ==<br />
<br />
[[Image:Stm32f4_discovery_left_bank.png|thumb|right|300px|left pin bank in relation to paparazzi(not up to date!)]]<br />
[[Image:Stm32f4_discovery_right_bank.png|thumb|right|300px|right pin bank in relation to paparazzi(not up to date!)]]<br />
The Discovery has a male 100 pin (2x25pin on both sides, also accessible on both sides of the pcb) pinout. <br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''LED'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''!!width="5%"|''Color''<br />
|-<br />
|PD13||LED_3||Out||above LIS302DL||style="background:orange; color:black"|Orange<br />
|-<br />
|PD12||LED_4||Out||left of LIS302DL||style="background:green; color:black"|Green<br />
|-<br />
|PD14||LED_5||Out||right of LIS302DL||style="background:red; color:black"|Red<br />
|-<br />
|PD15||LED_6||Out||below LIS302DL||style="background:blue; color:black"|Blue<br />
|-<br />
|PA9||LED_9||Out||same as USB power (VBUS, needs to be enabled in header file||style="background:green; color:black"|Green<br />
|} <br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB6||UART1 TX||Out||UART1 Serial Output, 4k7 pullup for I2C<br />
|-<br />
|PB7||UART1 RX||In||UART1 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD5||UART2 TX||Out||UART2 Serial Output<br />
|-<br />
|PD6||UART2 RX||In||UART2 Serial Input, also used for Spektrum input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART3'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD8||UART3 TX||Out||UART3 Serial Output<br />
|-<br />
|PD9||UART3 RX||In||UART3 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART4 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||UART4 TX||Out||UART4 Serial Output<br />
|-<br />
|PC11||UART4 RX||In||UART4 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART5 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC12||UART5 TX||Out||UART5 Serial Output<br />
|-<br />
|PD2||UART5 RX||In||UART5 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART6'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC6||UART6 TX||Out||UART6 Serial Output<br />
|-<br />
|PC7||UART6 RX||In||UART6 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1 (for onboard LIS302DL)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA5||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PA6||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PA7||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB3||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PB4||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PB5||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI2 (Can NOT be used if PWM10 & PWM11 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB13||SPI2 SCK||I/O||SPI2 Serial clock<br />
|-<br />
|PB14||SPI2 MISO||I/O||SPI2 Master In Slave Out<br />
|-<br />
|PB15||SPI2 MOSI||I/O||SPI2 Master Out Slave In<br />
|-<br />
|PE7||SPI SS1||I/O||SPI2 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI3 (Can NOT be used if UART4 & UART5 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||SPI3 SCK||I/O||SPI3 Serial clock<br />
|-<br />
|PC11||SPI3 MISO||I/O||SPI3 Master In Slave Out<br />
|-<br />
|PC12||SPI3 MOSI||I/O||SPI3 Master Out Slave In<br />
|-<br />
|PE3||SPI SS2||I/O||SPI3 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB8||I2C1 SCL||I/O||I2C1 Serial Clock<br />
|-<br />
|PB9||I2C1 SDA||I/O||I2C1 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB10||I2C2 SCL||I/O||I2C2 Serial Clock<br />
|-<br />
|PB11||I2C2 SDA||I/O||I2C2 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C3 (Can NOT be used if Spektrum bind / PPM input is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||I2C3 SCL||I/O||I2C3 Serial Clock<br />
|-<br />
|PC9||I2C3 SDA||I/O||I2C3 Serial Data<br />
|}<br />
Note: is disabled in header file, PA8 is used as Spektrum bind pin, PC9 is used as PPM (not Spektrum) input<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''ADC'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB1||AUX1||I/O||ADC_1<br />
|-<br />
|PC5||AUX2||I/O||ADC_2<br />
|-<br />
|PC4||AUX3||I/O||ADC_3<br />
|-<br />
|PA4||BAT||I/O||ADC_4, is used for BAT voltage<br />
|-<br />
|PC1||AUX5||I/O||ADC_5<br />
|-<br />
|PC2||AUX6||I/O||ADC_6<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PWM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PE9||PWM0||Out||Servo 1<br />
|-<br />
|PE11||PWM1||Out||Servo 2<br />
|-<br />
|PE13||PWM2||Out||Servo 3<br />
|-<br />
|PE14||PWM3||Out||Servo 4<br />
|-<br />
|PE5||PWM4||Out||Servo 5<br />
|-<br />
|PE6||PWM5||Out||Servo 6<br />
|-<br />
|PA3||PWM6||Out||Servo 7<br />
|-<br />
|PA2||PWM7||Out||Servo 8<br />
|-<br />
|PA1||PWM8||Out||Servo 9<br />
|-<br />
|PA0||PWM9||Out||Servo 10<br />
|-<br />
|PB14||PWM10||Out||Servo 11, Can not be used if SPI2 is active<br />
|-<br />
|PB15||PWM11||Out||Servo 12, Can not be used if SPI2 is active<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PPM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC9||PPM||In||PPM input (remember, you need 100 Ohm serial termination in order to use this) <br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Spektrum'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||Bind||Out||Spektrum bind pin<br />
|-<br />
|PA10||PPM||IN||Spektrum PPM in<br />
|}<br />
<br />
<br />
=== Jumper ===<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|JP1||JP1||Switch||MCU Current can be measured here<br />
|-<br />
|CN3||CN3||Switch||closed: STLinkV2 is connected to onboard MCU, open: is not connectec to onboard, only external header<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Soolder Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|SB17||SB17||Switch||Bypass for JP1, close this for security ! (if JP1 gets loose)<br />
|}<br />
<br />
==Daughterboard==<br />
<br />
comming soon :) [https://github.com/NeoFromMatrix/stm32f4discovery_daughterboard git repo]<br />
<br />
Components:<br />
<br />
Diode: Standard types (like 1N4007) will work<br/><br />
Resistors: 2k2 and 22k, 0,1%<br/><br />
Caps: Low ESR type, 10-50µF<br/><br />
<br />
[[Image:DiscoveryBreakout1_small.jpg|300px]]<br />
[[Image:DiscoveryBreakout2_small.jpg|300px]]<br />
<br />
==Firmware Flashing==<br />
<br />
'''FLASH_MODE=STLINK''' is set as default<br />
<br />
STM32F4 Discovery can mainly be programmed in two different ways:<br />
<br />
===STLINK===<br />
<br />
* with onboard STLinkV2 over SWD<br />
* required hardware: usb to mini USB cable<br />
* required software: st_flash and st_util from [https://github.com/texane/stlink Texane]<br />
* more information: [[STLink]] page<br />
<br />
===DFU-UTIL===<br />
<br />
* with the MCU native (embedded in rom) DFU USB bootloader over the micro USB AB connector<br />
* required hardware: USB to micro and USB to mini usb cable <br />
* required external software: dfu-util <br />
* push MCU in DFU mode: connect mini(for power) and micro USB to PC, connect pin BOOT0 with 3V, press reset button(LED LD7 should light up now), disconnect BOOT0<br />
* more information: [[DFU]] page<br />
<br />
[[Category:Autopilots]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:DiscoveryBreakout2_small.jpg&diff=18459File:DiscoveryBreakout2 small.jpg2014-04-10T21:00:59Z<p>Christoph: </p>
<hr />
<div></div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:DiscoveryBreakout1_small.jpg&diff=18458File:DiscoveryBreakout1 small.jpg2014-04-10T20:58:56Z<p>Christoph: </p>
<hr />
<div></div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=STM32F4_Discovery&diff=18457STM32F4 Discovery2014-04-10T20:48:11Z<p>Christoph: /* Pinout */</p>
<hr />
<div>'''This page is for the [http://www.st.com/web/catalog/tools/FM116/SC959/SS1532/PF252419 STM32F4 Discovery board with STM32F407VGT6], STM32F4 Disco is a familiar board with STM32F401VCT6, do not use this Files for the Disco board ! '''<br />
<br />
{| align=right<br />
|-<br />
|<categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Autopilots</categorytree><br />
|}<br />
<br />
<div style="float: right; width: 65%"><br />
[[Image:STM32F4Discovery_front.jpg|300px]]<br />
[[Image:STM32F4Discovery_back.jpg|300px]]<br />
</div><br />
<br />
__TOC__<br />
<br />
<br />
==Overview==<br />
<br />
* STMicroelectronics STM32F4VGT6 Cortex M4 MCU, up to 168Mhz with floating point unit (FPU), 192 KB RAM, 1024 KB Flash<br />
* on-board STLinkv2 with SWD header (capable of programming onboard or external MCU)<br />
* on-board power regulator for the MCU (3V or 5V Input)<br />
* 1 x user push button<br />
* 4(5) x LED (orange, green, red, blue, green) <br />
* 4(6) x UART (UART1, UART2, UART3, (UART4, UART5), UART6)<br />
* 1(3) x SPI (SPI1, (SPI2, SPI3))<br />
* 2(3) x I2C (I2C1, I2C2, (I2C3))<br />
* 6 x ADC inputs (one is used for BAT voltage)<br />
* 1 x PPM input<br />
* 1 x Spektrum input (with bind pin)<br />
* 97 x 66 mm PCB<br />
* 4 x status LED (USB red, USB green, power, USB OTG green, USB OTG red)<br />
* LIS302DL MEMS 3 axis accelerometer on SPI1<br />
<br />
== Pinout ==<br />
<br />
[[Image:Stm32f4_discovery_left_bank.png|thumb|right|300px|left pin bank in relation to paparazzi(not up to date!)]]<br />
[[Image:Stm32f4_discovery_right_bank.png|thumb|right|300px|right pin bank in relation to paparazzi(not up to date!)]]<br />
The Discovery has a male 100 pin (2x25pin on both sides, also accessible on both sides of the pcb) pinout. <br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''LED'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''!!width="5%"|''Color''<br />
|-<br />
|PD13||LED_3||Out||above LIS302DL||style="background:orange; color:black"|Orange<br />
|-<br />
|PD12||LED_4||Out||left of LIS302DL||style="background:green; color:black"|Green<br />
|-<br />
|PD14||LED_5||Out||right of LIS302DL||style="background:red; color:black"|Red<br />
|-<br />
|PD15||LED_6||Out||below LIS302DL||style="background:blue; color:black"|Blue<br />
|-<br />
|PA9||LED_9||Out||same as USB power (VBUS, needs to be enabled in header file||style="background:green; color:black"|Green<br />
|} <br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB6||UART1 TX||Out||UART1 Serial Output, 4k7 pullup for I2C<br />
|-<br />
|PB7||UART1 RX||In||UART1 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD5||UART2 TX||Out||UART2 Serial Output<br />
|-<br />
|PD6||UART2 RX||In||UART2 Serial Input, also used for Spektrum input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART3'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PD8||UART3 TX||Out||UART3 Serial Output<br />
|-<br />
|PD9||UART3 RX||In||UART3 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART4 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||UART4 TX||Out||UART4 Serial Output<br />
|-<br />
|PC11||UART4 RX||In||UART4 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART5 (Can NOT be used if SPI_3 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC12||UART5 TX||Out||UART5 Serial Output<br />
|-<br />
|PD2||UART5 RX||In||UART5 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''UART6'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC6||UART6 TX||Out||UART6 Serial Output<br />
|-<br />
|PC7||UART6 RX||In||UART6 Serial Input<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1 (for onboard LIS302DL)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA5||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PA6||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PA7||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB3||SPI1 SCK||I/O||SPI1 Serial clock<br />
|-<br />
|PB4||SPI1 MISO||I/O||SPI1 Master In Slave Out<br />
|-<br />
|PB5||SPI1 MOSI||I/O||SPI1 Master Out Slave In<br />
|-<br />
|PE2||SPI SS0||I/O||SPI1 Select Slave0<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI2 (Can NOT be used if PWM10 & PWM11 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB13||SPI2 SCK||I/O||SPI2 Serial clock<br />
|-<br />
|PB14||SPI2 MISO||I/O||SPI2 Master In Slave Out<br />
|-<br />
|PB15||SPI2 MOSI||I/O||SPI2 Master Out Slave In<br />
|-<br />
|PE7||SPI SS1||I/O||SPI2 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''SPI3 (Can NOT be used if UART4 & UART5 is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC10||SPI3 SCK||I/O||SPI3 Serial clock<br />
|-<br />
|PC11||SPI3 MISO||I/O||SPI3 Master In Slave Out<br />
|-<br />
|PC12||SPI3 MOSI||I/O||SPI3 Master Out Slave In<br />
|-<br />
|PE3||SPI SS2||I/O||SPI3 Select Slave1<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB8||I2C1 SCL||I/O||I2C1 Serial Clock<br />
|-<br />
|PB9||I2C1 SDA||I/O||I2C1 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB10||I2C2 SCL||I/O||I2C2 Serial Clock<br />
|-<br />
|PB11||I2C2 SDA||I/O||I2C2 Serial Data<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''I2C3 (Can NOT be used if Spektrum bind / PPM input is active!)'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||I2C3 SCL||I/O||I2C3 Serial Clock<br />
|-<br />
|PC9||I2C3 SDA||I/O||I2C3 Serial Data<br />
|}<br />
Note: is disabled in header file, PA8 is used as Spektrum bind pin, PC9 is used as PPM (not Spektrum) input<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''ADC'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PB1||AUX1||I/O||ADC_1<br />
|-<br />
|PC5||AUX2||I/O||ADC_2<br />
|-<br />
|PC4||AUX3||I/O||ADC_3<br />
|-<br />
|PA4||BAT||I/O||ADC_4, is used for BAT voltage<br />
|-<br />
|PC1||AUX5||I/O||ADC_5<br />
|-<br />
|PC2||AUX6||I/O||ADC_6<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PWM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PE9||PWM0||Out||Servo 1<br />
|-<br />
|PE11||PWM1||Out||Servo 2<br />
|-<br />
|PE13||PWM2||Out||Servo 3<br />
|-<br />
|PE14||PWM3||Out||Servo 4<br />
|-<br />
|PE5||PWM4||Out||Servo 5<br />
|-<br />
|PE6||PWM5||Out||Servo 6<br />
|-<br />
|PA3||PWM6||Out||Servo 7<br />
|-<br />
|PA2||PWM7||Out||Servo 8<br />
|-<br />
|PA1||PWM8||Out||Servo 9<br />
|-<br />
|PA0||PWM9||Out||Servo 10<br />
|-<br />
|PB14||PWM10||Out||Servo 11, Can not be used if SPI2 is active<br />
|-<br />
|PB15||PWM11||Out||Servo 12, Can not be used if SPI2 is active<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''PPM'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PC9||PPM||In||PPM input (remember, you need 100 Ohm serial termination in order to use this) <br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Spektrum'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|PA8||Bind||Out||Spektrum bind pin<br />
|-<br />
|PA10||PPM||IN||Spektrum PPM in<br />
|}<br />
<br />
<br />
=== Jumper ===<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|JP1||JP1||Switch||MCU Current can be measured here<br />
|-<br />
|CN3||CN3||Switch||closed: STLinkV2 is connected to onboard MCU, open: is not connectec to onboard, only external header<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="60%"<br />
|+'''Soolder Jumper'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|SB17||SB17||Switch||Bypass for JP1, close this for security ! (if JP1 gets loose)<br />
|}<br />
<br />
==Daughterboard==<br />
<br />
comming soon :) [https://github.com/NeoFromMatrix/stm32f4discovery_daughterboard git repo]<br />
<br />
Components:<br />
<br />
Diode: Standard types (like 1N4007) will work<br/><br />
Resistors: 2k2 and 22k, 0,1%<br/><br />
Caps: Low ESR type, 10-50µF<br/><br />
<br />
==Firmware Flashing==<br />
<br />
'''FLASH_MODE=STLINK''' is set as default<br />
<br />
STM32F4 Discovery can mainly be programmed in two different ways:<br />
<br />
===STLINK===<br />
<br />
* with onboard STLinkV2 over SWD<br />
* required hardware: usb to mini USB cable<br />
* required software: st_flash and st_util from [https://github.com/texane/stlink Texane]<br />
* more information: [[STLink]] page<br />
<br />
===DFU-UTIL===<br />
<br />
* with the MCU native (embedded in rom) DFU USB bootloader over the micro USB AB connector<br />
* required hardware: USB to micro and USB to mini usb cable <br />
* required external software: dfu-util <br />
* push MCU in DFU mode: connect mini(for power) and micro USB to PC, connect pin BOOT0 with 3V, press reset button(LED LD7 should light up now), disconnect BOOT0<br />
* more information: [[DFU]] page<br />
<br />
[[Category:Autopilots]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Linux&diff=18456Installation/Linux2014-04-10T20:45:43Z<p>Christoph: /* Troubleshooting */</p>
<hr />
<div><categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Installation</categorytree><br />
__TOC__<br />
<br />
'''<span style="color:red">This page only describes the installation of the prerequisite tools and dependencies on Debian/Ubuntu needed for Paparazzi.</span>'''<br />
<br />
'''See the general [[Installation]] page for how to [[Installation#Getting_the_Source_Code|download Paparazzi]] and [[Installation#Launching_the_Software|launching it]] after you followed the instructions here.'''<br />
<br />
== Introduction ==<br />
<br />
Paparazzi is very easily installed on any laptop or workstation running [http://www.ubuntu.com/ Ubuntu], [http://www.debian.org/ Debian] (or any of their derivatives).<br />
<br />
The steps required to install the software needed to be able to let your UAS fly <br />
<ul><br />
<li>Install the basic Paparazzi dependencies and the ARM cross compiling toolchain.<br />
<li>[[Installation#Getting_the_Source_Code|Download the source code from the source repository]].<br />
<li>Allow access to your PC hardware connection by adding appropriate [[Udev]] rules.<br />
<li>Compile the binaries from the sources (cd paparazzi && make)<br />
</ul><br />
<br />
Users of other Linux flavors than a recent Ubuntu or Debian and anyone needing manual control of each individual package can [[Installation/Manual|install them independently]].<br />
<br />
===For the impatient===<br />
For Ubuntu add the [https://launchpad.net/~paparazzi-uav/+archive/ppa paparazzi-uav ppa] <tt>sudo add-apt-repository ppa:paparazzi-uav/ppa</tt> and install the <tt>paparazzi-dev</tt> package.<br />
<br />
Since Paparazzi v5.0 the [https://launchpad.net/gcc-arm-embedded/ gcc-arm-embedded toolchain] is recommended.<br />
You can just unpack the tarball and add the bin directory to your PATH.<br />
<br />
== Installation video Tutorials ==<br />
<br />
{{#ev:youtubehd|SshFJrBuku8}} {{#ev:youtubehd|eW0PCSjrP78}}<br />
<br />
== Installation of dependencies ==<br />
<br />
=== Ubuntu ===<br />
<br />
Add the installation sources for the Paparazzi software packages. Run from a terminal:<br />
sudo add-apt-repository ppa:paparazzi-uav/ppa<br />
<br />
Then update the systems package inventory and install the main Paparazzi software dependencies. This will take some time.<br />
sudo apt-get update <br />
sudo apt-get install paparazzi-dev<br />
<br />
=== Debian ===<br />
<br />
For Debian Squeeze (6.0) and Wheezy (7.0) packages are built using the [http://openbuildservice.org/ Open Build Service (OBS)] on [https://build.opensuse.org/project/show?project=home%3Aflixr%3Apaparazzi-uav OpenSUSE Build Service project home:flixr:paparazzi-uav]<br />
<br />
First add the key:<br />
wget -q "http://download.opensuse.org/repositories/home:/flixr:/paparazzi-uav/Debian_7.0/Release.key" -O- | sudo apt-key add -<br />
<br />
Add the appropriate repo, depending on your Debian version to sources.list<br />
echo "deb http://download.opensuse.org/repositories/home:/flixr:/paparazzi-uav/Debian_6.0/ ./" | sudo tee -a /etc/apt/sources.list<br />
echo "deb http://download.opensuse.org/repositories/home:/flixr:/paparazzi-uav/Debian_7.0/ ./" | sudo tee -a /etc/apt/sources.list<br />
<br />
Update the systems package inventory and install the main Paparazzi software dependencies.<br />
sudo apt-get update <br />
sudo apt-get install paparazzi-dev<br />
<br />
== ARM embedded toolchain ==<br />
For current Paparazzi versions (v5.0 and above) the [https://launchpad.net/gcc-arm-embedded/ gcc-arm-embedded toolchain] is recommended, which also supports the STM32F4 with FPU (hardware floating point).<br />
<br />
The most common way is to download and unpack the tarball and add it to your PATH:<br />
<br />
cd ~<br />
wget https://launchpad.net/gcc-arm-embedded/4.8/4.8-2013-q4-major/+download/gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar.bz2<br />
tar -vjxf gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar.bz2<br />
rm -rf gcc-arm-none-eabi-4_8-2013q4-20131204-linux.tar.bz2<br />
sudo mv gcc-arm-none-eabi-4_8-2013q4 /opt<br />
exportline="PATH=$PATH:/opt/gcc-arm-none-eabi-4_8-2013q4/bin"<br />
if grep -Fxq "$exportline" ~/.profile; then echo nothing to do ; else echo $exportline >> ~/.profile; fi<br />
source ~/.profile<br />
<br />
The file .profile will be sourced in every bash after logging out and in again. Until then,<br />
source ~/.profile<br />
can be used for every bash individually.<br />
<br />
If you can not access your toolchain with PATH working, look a the [[Installation/Linux#Troubleshooting]].<br />
<br />
=== gcc-arm-none-eabi as Ubuntu package ===<br />
<br />
From Ubuntu 14.04 ('''trusty'''), gcc-arm-none-eabi is a part of the official ubuntu repository ('''universe''') and can be installed with:<br />
sudo apt-get update<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
On ''some'' Ubuntu versions ('''currently only lucid, precise and raring''') the [https://launchpad.net/gcc-arm-embedded/ gcc-arm-embedded toolchain] can be installed as a debian package from the [https://launchpad.net/~terry.guo/+archive/gcc-arm-embedded ppa]:<br />
sudo add-apt-repository ppa:terry.guo/gcc-arm-embedded<br />
sudo apt-get update<br />
sudo apt-get install gcc-arm-none-eabi<br />
<br />
NOTE: For newer Debian (Ubuntu saucy 13.10 and Mint 16) there are no binary debian packages available. Although it's recommended to use the tarballs as described above, you can also try to use the binary packages meant for Ubuntu raring 13.04. For that edit the sources list before you do the apt-get update. Details why [https://bugs.launchpad.net/gcc-arm-embedded/+bug/1244060 here]<br />
<br />
nano /etc/apt/sources.list.d/terry_guo-gcc-arm-embedded-saucy.list<br />
<br />
The contents should read 1 line like this after the edit:<br />
deb http://ppa.launchpad.net/terry.guo/gcc-arm-embedded/ubuntu raring main<br />
<br />
=== Old toolchain for Paparazzi v4.x and earlier ===<br />
<br />
'''For Paparazzi v4.x''' and earlier you need to install the <tt>paparazzi-arm-multilib</tt> package. It has support for both ARM7 (i.e. Tiny,TWOG,YAPA autopilot boards) as well as STM32F1 (i.e. LISA boards).<br><br />
'''This toolchain does not properly support STM32F4 based autopilots!!'''<br />
<br />
You can install it explicitly with:<br />
sudo apt-get install paparazzi-arm-multilib<br />
<br />
== Optional Packages ==<br />
<br />
The packages <b>lpc21isp</b> and <b>openocd</b> are normally '''automatically installed''' as they are recommended packages of paparazzi-dev, '''if not''' you can manually install them via:<br />
<br />
sudo apt-get install lpc21isp openocd<br />
<br />
<tt>lpc21isp</tt> is needed to serially flash the LPC2148 based autopilots (e.g. bootloader for tiny, twog, umarim), <tt>openocd</tt> is for flashing via JTAG (e.g. for Lisa boards) and debugging.<br />
<br />
== Installing and running Paparazzi ==<br />
Please see [[Installation#Getting_the_Source_Code|Getting the Source Code on the general Installation page]] for details on downloading the Paparazzi source code, compiling and running it.<br />
<br />
== Udev rules ==<br />
Add the appropriate [[Udev]] rule (available in fhe file ''50-paparazzi.rules'') to the USB handler. Simply copy as root <tt>conf/system/udev/rules/50-paparazzi.rules</tt> to <tt>/etc/udev/rules.d/</tt>, e.g in a terminal:<br />
<br />
cd <your paparazzi directory><br />
sudo cp conf/system/udev/rules/50-paparazzi.rules /etc/udev/rules.d/<br />
<br />
See the [[Udev]] page for more details.<br />
<br />
== Troubleshooting ==<br />
<br />
=== No access rights for USB devices ===<br />
<br />
Some Linux distributions, don't allow standard (non admin) users to directly access the USB bus by default. On recent Ubuntu/Debian versions the first/main user is already a member of the ''plugdev'' group which should be sufficient for most cases.<br><br />
If you have problems, make yourself a member of the ''plugdev'' and ''dialout'' groups:<br />
<br />
sudo adduser <your login> plugdev<br />
sudo adduser <your login> dialout<br />
<br />
Logout and login again.<br />
<br />
=== arm-none-eabi-gcc: Command not found ===<br />
Appeared on Debian<br/><br />
This error occurs, the [https://packages.debian.org/de/wheezy/ia32-libs ia32-libs] are missing.<br />
<br />
Enable multiarch and install ia32-libs:<br />
dpkg --add-architecture i386<br />
apt-get update<br />
apt-get install ia32-libs<br />
<br />
=== FTDI serial adapter not working on old Ubuntu version ===<br />
<br />
On older Linux distributions (not needed for lucid and later), the Braille TTY driver interferes with FTDI USB Serial adapters. If somehow your FTDI serial adapter does not work, remove the package via:<br />
<br />
sudo apt-get remove brltty<br />
<br />
=== Code not starting on autopilot after changing gcc ===<br />
<br />
If you changed the toolchain (e.g. installed a new one for having FPU-Support for the F4), you need to run<br />
<br />
make clean && make<br />
<br />
in sw/ext in order to rebuild the libs. Otherwise the embedded code can behave strange (most likely not start)<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=16448Users2013-12-30T02:00:30Z<p>Christoph: /* Europe */</p>
<hr />
<div>Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi<br />
<br />
== Wiki User Pages ==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ User Pages<br />
|-<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]<br />
|[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]<br />
|[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]<br />
|[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]<br />
|[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]<br />
|[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]<br />
|[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]<br />
|[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]<br />
|[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]<br />
|[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]<br />
|[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]<br />
|[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]<br />
|[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Marc Marc]<br />
|[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]<br />
|[http://paparazzi.enac.fr/wiki/User:HWal HWal]<br />
|[http://paparazzi.enac.fr/wiki/User:Aerodolphin Rui Costa]<br />
|[http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:PaulCox Paul Cox]<br />
|[http://paparazzi.enac.fr/wiki/User:Bruzzlee Bruzzlee]<br />
|[http://paparazzi.enac.fr/wiki/User:Stspies Stspies]<br />
|[http://paparazzi.enac.fr/wiki/User:Mzr Mzr]<br />
|[http://brquad.blogspot.com AGRESSiVA]<br />
|- style="background:bisque; color:black"<br />
|add yourself here<br />
|[http://paparazzi.enac.fr/wiki/User:Martial Martial Châteauvieux]<br />
|[http://paparazzi.enac.fr/wiki/User:Christoph Christoph]<br />
|<br />
|<br />
|}<br />
<br />
== Developers ==<br />
See [[Developers]]<br />
<br />
== Paparazzi Users sorted geographically ==<br />
<br />
===Asia===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ Asia<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
|- style="background:bisque; color:black"<br />
| [mailto:wzxwyvippt@126.com WANGYAO]|| China || UMARIM,twog,tiny2.11 lisa/m2.0 ||| 2008|| fly with lisa/m2.0 now, fully auto takeoff and landing <br />
|- style="background:bisque; color:black"<br />
| [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中文)<br />
|- style="background:bisque; color:black"<br />
| [mailto:laizzb@126.com dianzhichong]|| China || Umarim ||| 2011|| Fixed-wing autonomous flight. Establish QQ group (group No. 5436583) and technology sharing<br />
|- style="background:bisque; color:black"<br />
| [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!<br />
|- style="background:bisque; color:black"<br />
<br />
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.<br />
|- style="background:bisque; color:black"<br />
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe<br />
|- style="background:bisque; color:black"<br />
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe <br />
|- style="background:bisque; color:black"<br />
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!<br />
|- style="background:bisque; color:black"<br />
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet <br />
|- style="background:bisque; color:black"<br />
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon<br />
|- style="background:bisque; color:black"<br />
| [mailto:benybeejz@gmail.com benybee] || Bandar Lampung, Indonesia || Tiny13 1.1 ||| 2010 || trying to get wing dragon fully autonomous, for aireal photograph and research<br />
|- style="background:bisque; color:black"<br />
| [mailto:iman.shirdareh@gmail.com Iman Shirdareh]|| Iran || YAPA V2,TWOG ||| 2010 || Many flight in AUTO2 by different aircraft(1.7-21Kg)<br />
|- style="background:bisque; color:black" <br />
| [mailto:anilvanjare83@gmail.com Anil vanjare] || India || TWOG, Tiny v2.1,Umarim v10 ||| 2011 || ,Umarim board assembled and tested all are ok on ground, now building a MAV to do test flight using UMARIM, with prashant<br />
|}<br />
<br />
===Europe===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:lightgreen; color:black"<br />
|Austria<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:NeoFromMatrix NeoFromMatrix] || Lower Austria/Vienna, Austria || STM32F4-discovery, LisaMV2 || 2013 || wiki doc, testing with low cost/high performance hardware<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mbina Markus Bina] || Lower Austria/Vienna, Austria || LisaMV2 || 2013 || wiki doc, testing with low/medium cost hardware<br />
<br />
|- style="background:lightgreen; color:black"<br />
|France<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:limaiem@gmail.com Imed Limaiem] || Paris, France || TWOG 2.11, EPP-CF FPV ||| January 2010 || flight test; Town pollution measurement; <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox] <br />
| Toulouse <br />
| Tiny v2.11 || Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:charles-edmond.bichot@ec-lyon.fr Charles-Edmond Bichot] || Lyon, France || Tiny/YAPA, IR+GPS, XBee/smartphone ||| September 2009 || Teaching projects, solar cells, object detection in video / image<br />
<br />
|- style="background:lightgreen; color:black"<br />
|Germany<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.<br />
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Lisa/M, Lisa/L, Booz, Twog ||| 2008 || coding more than flying.... unfortunately<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Christoph|Christoph Niemann]] || Hamburg, Germany || Mini-Quadrotor with HBMini ||| 2010 || Several successful AUTO2-Flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Martial|Martial Châteauvieux]] || Munich, Germany || Bormatec/Maja with TWOG and IR ||| 2011 || Next test in January 2012, as soon as the weather permits. Hopefully I can switch in AUTO2.<br />
|- style="background:bisque; color:black"<br />
| [[User:Stspies|Steffen Spies]] || Wolfsburg, Germany || Multiplex TwinStar with Tiny V2.11 and IR ||| 2010 || Awaiting first flight. <br />
<br />
|- style="background:bisque; color:black"<br />
| [[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<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:RoN|Rolf N]] || Bremen, Germany || TWOG, YAPA2, analog airspeed, imu ||| 2010 || many AUTO2 flights<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:rijo1011_at_gmail.com Jochen Rieger] || Karlsruhe, Germany || Bormatec Maja, Lisa/L ||| 2011 || I hope the first flight is coming soon.<br />
<br />
|- style="background:lightgreen; color:black"<br />
| Portugal<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting<br />
<br />
<br />
|- style="background:lightgreen; color:black"<br />
|Switzerland<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny v2.11, TWOG v1, EeePC as GCS, Multiplex FunJet & EasyStar ||| 2008 || Many successful flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:samuelbryner_gmx.ch Samuel B.] || Winterthur, Switzerland || Tiny 2.11, Multiplex Easyglider ||| 2010 || Just starting. No flight so far :/<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:sjwilks_at_gmail.com Simon W.] || Aarau, Switzerland || TWOG with ArduIMU in Jamara Roo, TWOG on a Telink Tempest flying wing, YAPA2 on a Bormatec Maja, Lisa/L on a Droidworx AD-8 HL ||| 2010 || Many successful flights. See [http://sites.google.com/site/paparazziuav/ http://sites.google.com/site/paparazziuav/].<br />
<br />
|- style="background:lightgreen; color:black"<br />
| UK<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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!).<br />
<br />
<br />
|- style="background:lightgreen; color:black"<br />
| Other<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:hendrix@gmail.gr| Chris Efstathiou] || Piraeus Hellas || tiny 2.11 on a Mpx EasyGlider, TWOG 1.3 on a Boomerang turbine jet, and my newest toy a X8 with a on camera ||| 2008 || The Easyglider is fully operational, still working on the jet which had his first flight with the TWOG at 25/1/2009 <br />
<br />
|- style="background:bisque; color:black"<br />
| [[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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor <br />
|<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:helgewal@gmail.com Helge] || Bergen, Norway || TWOG ||| 2009 || First Auto2 flight with Twinstar2 in October 2010 <br />
|}<br />
<br />
===North America===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York, New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 || <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. <br />
<br />
|- style="background:bisque; color:black"<br />
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project<br />
<br />
|- style="background:bisque; color:black"<br />
| 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. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer] || Edmonton, AB, CAN || Nothing Yet ||| Jan 2011 || Obtaining Hardware <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muratagenc@yahoo.com Murat A. Genc] || New York, NY || not decided yet ||| May 2011 || just started<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:piotr@esden.net Piotr Esden-Tempski] || Santa Cruz, CA || Lisa/L, Lisa/M, Aspirin, Quadshot, Rotorcraft ||| 2009 || Software and Hardware development as well as [http://thequadshot.com The Quadshot]<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://clubs.asua.arizona.edu/~mavclub University of Arizona MAV] || Tucson, AZ || Lisa/M 2.0, Aspirin v2.0, uBlox MAX-6Q, XBee 900 Pro/868LP, Mini-Vertigo ||| 2005 || University of Arizona Micro Air Vehicle Club (competing in IMAVs with Paparazzi since 2003.)<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Cwozny Chris Wozny] || Nashua, New Hampshire || Lisa/M, Aspirin ||| 2008 || Currently building quadcopter around Lisa/M 2.0 platform.<br />
<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
===Central America===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
===South America===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:agressiva@hotmail.com Eduardo Lavratti] || Porto Alegre - RS, Brasil || TWOG / BOOZ / LISA-M, UBLOX, Xbee900 60mw||| 2011 || Working with geoprocessing - developping new modules and sensors to paparazzi. [http://brquad.blogspot.com ACCENT AERiALS]<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
===Australia===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|}<br />
<br />
===Africa===<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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 ...<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
|}<br />
<br />
==Need help adding your information?==<br />
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 <br />
following:<br />
<br />
*Name<br />
*Email<br />
*Location<br />
*Hardware<br />
*Join date<br />
*Current activities / project status<br />
<br />
[[Category:Community]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Talk:Modems&diff=16120Talk:Modems2013-10-07T09:32:32Z<p>Christoph: /* Radiotronix Modem: */</p>
<hr />
<div><br />
== Radiotronix Modem: ==<br />
<br />
The picture of the "WI232EUR Modem" is a bit misleading because on the 8 Pin Molex the red cable (+ Pole) connects to 5 V on the Tiny. But the Modem is driven via 3.3V (one pin to the left).<br />
<br />
Furthermore i do not have to disconnect the two Pins RTS and CTS on the ground station as writen in note 1 and 2.<br />
<br />
The Radiotronix Modems are still available. But the company has a new name and the part a new description: It is now named TRM-868-EUR and the Company is Linx - so move it from deprecated to active - its working perfect :-)</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Talk:Modems&diff=16119Talk:Modems2013-10-07T09:32:22Z<p>Christoph: /* Radiotronix Modem: */</p>
<hr />
<div><br />
== Radiotronix Modem: ==<br />
<br />
The picture of the "WI232EUR Modem" is a bit misleading because on the 8 Pin Molex the red cable (+ Pole) connects to 5 V on the Tiny. But the Modem is driven via 3.3V (one pin to the left).<br />
<br />
Furthermore i do not have to disconnect the two Pins RTS and CTS on the ground station as writen in note 1 and 2.<br />
<br />
The Radiotronix Modems are still available. But the company has a new name and the part a new description: It is now named TRM-868-EUR and the Company is Linx - so move it from deprecated to active - it working perfect :-)</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12781Openlog2012-06-26T15:54:11Z<p>Christoph: </p>
<hr />
<div>== Openlog ==<br />
In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).<br />
The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.<br />
Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log. <br />
There is a helper-script that does this job.<br />
=== Hardware ===<br />
<br />
[[File:openlog.jpg|300px]]<br />
<br />
The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.<br />
In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbritary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed. <br />
<br />
First you need to checkout the modified OpenLog firmware on github:<br />
<br />
git clone https://github.com/chni/OpenLog.git -b OpenLog_V1_noescape<br />
<br />
then change to the directory where the hexfile is:<br />
<br />
cd OpenLog/Code<br />
<br />
The hexfile is contained by the directory, so you can flash it. <br />
<br />
You should power the OpenLog with the Programmer, not by the LPC in the same time. The programming is done by running<br />
<br />
avrdude -c usbasp -pm328p -U flash:w:openlog_noescape.hex -Ulfuse:w:0xff:m -Uhfuse:w:0xda:m -Uefuse:w:0x0:m<br />
<br />
After running this, the OpenLog has a custom firmware making it ignore the escape-characters.<br />
<br />
=== Software ===<br />
<br />
First of all the OpenLog needs to be configured. If it was powered one time without being configured, but with SD-Card plugged, it creates a file named CONFIG.txt or CONFIG.TXT (depends on the version of the firmware). You need to configure the Baudrate, it defaults to 9600-8-N1. In case you use 57600 Baud it should look like:<br />
{{Box Code|CONFIG.TXT|<br />
<source lang="xml"><br />
57600,26,3,0<br />
</source><br />
}}<br />
Furthermore you need to add the OpenLog-module to your airframe.<br />
{{Box Code|conf/airframes/yourairframe.xml|<br />
<source lang="xml"><br />
[...]<br />
<modules><br />
<load name="openlog.xml"/><br />
[...]<br />
</modules><br />
[...]<br />
</source><br />
}}<br />
Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog LOG00003.TXT <br />
now converting LOG00003.TXT to LOG00003.TXT.tlm<br />
The conversion from the logfile from the SD to TLM seems to be successful, 567 have been converted, 2 packages have been broken<br />
Renaming produced file ...<br />
12_06_17__01_59_45_SD.data file produced<br />
Looking for 4ae62580cb19d37d2b30aa8d31cc20dc conf...<br />
12_06_17__01_59_45_SD.log file produced<br />
12_06_17__01_59_45_SD.tlm file saved<br />
<br />
You can also do batch processing like:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog /media/disk-1/LOG*<br />
<br />
In this case all logs will be imported.<br />
Afterwards you can find the logs as usual in var/logs/*_SD.log<br />
<br />
If someting goes wrong during the import have a close look to the error messages, since openlog2tlm tries to identify the most common problems.<br />
<br />
<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12780Openlog2012-06-26T15:30:53Z<p>Christoph: /* Hardware */</p>
<hr />
<div>== Openlog ==<br />
In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).<br />
The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.<br />
Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log. <br />
There is a helper-script that does this job.<br />
=== Hardware ===<br />
<br />
[[File:openlog.jpg|300px]]<br />
<br />
The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.<br />
In general there is one Problem with the stock-firmware of the OpenLog. If it gets an escape-character (CTRL+Z) it switches into command-mode and stops logging. But the telemetry stream is nearly arbritary. So we have to deactivate this feature, it isn't needed for our application at all. Therefore we have to reprogram the OpenLog. You need an AVR-programmer like the i.e. [http://www.hobbyking.com/hobbycity/store/uh_viewItem.asp?idProduct=21321 usbasp]. You have to wire the ISP to the accoring pins of the OpenLog. You need the avrdude package installed. <br />
<br />
First you need to download the ''[[Media:Booz_gps_brd.zip|modified .hex-file for OpenLog]]''<br />
<br />
You should power the OpenLog with the Programmer, not by the LPC in the same time. The programming is done by running<br />
<br />
avrdude -c usbasp -pm328p -U flash:w:openlog_noescape.hex -Ulfuse:w:0xff:m -Uhfuse:w:0xda:m -Uefuse:w:0x0:m<br />
<br />
After running this, the OpenLog has a custom firmware making it ignore the escape-characters.<br />
<br />
=== Software ===<br />
<br />
First of all the OpenLog needs to be configured. If it was powered one time without being configured, but with SD-Card plugged, it creates a file named CONFIG.txt or CONFIG.TXT (depends on the version of the firmware). You need to configure the Baudrate, it defaults to 9600-8-N1. In case you use 57600 Baud it should look like:<br />
{{Box Code|CONFIG.TXT|<br />
<source lang="xml"><br />
57600,26,3,0<br />
</source><br />
}}<br />
Furthermore you need to add the OpenLog-module to your airframe.<br />
{{Box Code|conf/airframes/yourairframe.xml|<br />
<source lang="xml"><br />
[...]<br />
<modules><br />
<load name="openlog.xml"/><br />
[...]<br />
</modules><br />
[...]<br />
</source><br />
}}<br />
Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog LOG00003.TXT <br />
now converting LOG00003.TXT to LOG00003.TXT.tlm<br />
The conversion from the logfile from the SD to TLM seems to be successful, 567 have been converted, 2 packages have been broken<br />
Renaming produced file ...<br />
12_06_17__01_59_45_SD.data file produced<br />
Looking for 4ae62580cb19d37d2b30aa8d31cc20dc conf...<br />
12_06_17__01_59_45_SD.log file produced<br />
12_06_17__01_59_45_SD.tlm file saved<br />
<br />
You can also do batch processing like:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog /media/disk-1/LOG*<br />
<br />
In this case all logs will be imported.<br />
Afterwards you can find the logs as usual in var/logs/*_SD.log<br />
<br />
If someting goes wrong during the import have a close look to the error messages, since openlog2tlm tries to identify the most common problems.<br />
<br />
<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Data_Logger&diff=12770Data Logger2012-06-24T11:29:23Z<p>Christoph: </p>
<hr />
<div>[[Image:sd_spi.jpg|thumb|micro SD card connected to SPI]]<br />
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.<br />
<br />
== Mode of operation ==<br />
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.<br />
<br />
== Hardware ==<br />
<br />
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.<br />
<br />
LED2 on: logging enabled, press button to stop<br />
LED3 flashing: writing message to SD<br />
<br />
LED2 flashing: logging stopped, connect USB to read out data or press button long to restart logging<br />
<br />
LED1 on: USB mass storage enabled<br />
<br />
=== Option 1: Paparazzi Logger HW ===<br />
<br />
https://github.com/paparazzi/paparazzi-hardware/tree/master/controller/logger/v1.0<br />
<br />
=== Option 2: TWOG ===<br />
<br />
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:<br />
<br />
microSD TinyV2 SPI J3 <br />
<br />
8 nc<br />
7 DO 5 MISO<br />
6 GND 1 GND<br />
5 CLK 7 SCK<br />
4 Vcc 2 +3V3<br />
3 DI 4 MOSI<br />
2 CS 3 SSEL<br />
1 nc<br />
<br />
Looking onto the gold plated connector side of the microSD card:<br />
<br />
###############<br />
I 8 <br />
I 7<br />
I 6<br />
I 5<br />
I 4<br />
I 3<br />
I 2<br />
I 1<br />
###### ##<br />
\ I \<br />
## ##<br />
<br />
The start/stop button is connected to the BUTTON (P0.7) pin of the USB connector (J9). It is activated by pulling it low.<br />
<br />
=== Option 3: Logomatic ===<br />
<br />
There is also direct support for the Sparkfun [http://www.sparkfun.com/products/10216 Logomatic V2.6] board, just use<br />
<br />
conf/airframes/logomatic.xml<br />
<br />
=== Option 4: OpenLog ===<br />
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.<br />
Take a look at [[Openlog|Openlog]].<br />
<br />
== UART Connection ==<br />
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.<br />
<br />
== I2C Connection ==<br />
tbd<br />
<br />
== SPI Connection ==<br />
tbd<br />
<br />
== Configuration ==<br />
The logger is defined just like an aircraft. Take the <br />
<br />
conf/airframes/logger_sd.xml<br />
<br />
as example. You can enable one or both UARTs for logging and have to set the serial speed<br />
<br />
<configure name="UART0_BAUD" value="B9600" /><br />
<configure name="UART1_BAUD" value="B9600" /><br />
<br />
The message type can be switched between the PPRZ and the XBEE format<br />
<br />
<configure name="LOG_MSG_FMT" value="LOG_PPRZ"/><br />
''or''<br />
<configure name="LOG_MSG_FMT" value="LOG_XBEE"/><br />
<br />
The SD card can either be connected to SPI0 or SPI1<br />
<br />
<configure name="SPI_CHANNEL" value="0" /><br />
''or''<br />
<configure name="SPI_CHANNEL" value="1" /><br />
<br />
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.<br />
<br />
== Decoding ==<br />
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<br />
<br />
me@home:~/media/usbstick$ ~/paparazzi3/sw/logalizer/sd2log 00000002.TLM<br />
Renaming produced file ...<br />
09_08_13__20_55_03_SD.data file produced<br />
09_08_13__20_55_03_SD.log file produced<br />
09_08_13__20_55_03_SD.tlm file saved<br />
<br />
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.<br />
<br />
[[Category:Hardware]] [[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12769Openlog2012-06-24T11:21:43Z<p>Christoph: </p>
<hr />
<div>== Openlog ==<br />
In general [http://www.sparkfun.com/products/9530 OpenLog] is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).<br />
The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.<br />
Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log. <br />
There is a helper-script that does this job.<br />
=== Hardware ===<br />
<br />
[[File:openlog.jpg|300px]]<br />
<br />
The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.<br />
<br />
=== Software ===<br />
<br />
First of all the OpenLog needs to be configured. If it was powered one time without being configured, but with SD-Card plugged, it creates a file named CONFIG.txt or CONFIG.TXT (depends on the version of the firmware). You need to configure the Baudrate, it defaults to 9600-8-N1. In case you use 57600 Baud it should look like:<br />
{{Box Code|CONFIG.TXT|<br />
<source lang="xml"><br />
57600,26,3,0<br />
</source><br />
}}<br />
Furthermore you need to add the OpenLog-module to your airframe.<br />
{{Box Code|conf/airframes/yourairframe.xml|<br />
<source lang="xml"><br />
[...]<br />
<modules><br />
<load name="openlog.xml"/><br />
[...]<br />
</modules><br />
[...]<br />
</source><br />
}}<br />
Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog LOG00003.TXT <br />
now converting LOG00003.TXT to LOG00003.TXT.tlm<br />
The conversion from the logfile from the SD to TLM seems to be successful, 567 have been converted, 2 packages have been broken<br />
Renaming produced file ...<br />
12_06_17__01_59_45_SD.data file produced<br />
Looking for 4ae62580cb19d37d2b30aa8d31cc20dc conf...<br />
12_06_17__01_59_45_SD.log file produced<br />
12_06_17__01_59_45_SD.tlm file saved<br />
<br />
You can also do batch processing like:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog /media/disk-1/LOG*<br />
<br />
In this case all logs will be imported.<br />
Afterwards you can find the logs as usual in var/logs/*_SD.log<br />
<br />
If someting goes wrong during the import have a close look to the error messages, since openlog2tlm tries to identify the most common problems.<br />
<br />
<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12768Openlog2012-06-24T11:16:16Z<p>Christoph: </p>
<hr />
<div>== Openlog ==<br />
In general OpenLog is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).<br />
The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.<br />
Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log. <br />
There is a helper-script that does this job.<br />
=== Hardware ===<br />
<br />
[[File:openlog.jpg|300px]]<br />
<br />
The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.<br />
<br />
=== Software ===<br />
<br />
First of all the OpenLog needs to be configured. If it was powered one time without being configured, but with SD-Card plugged, it creates a file named CONFIG.txt or CONFIG.TXT (depends on the version of the firmware). You need to configure the Baudrate, it defaults to 9600-8-N1. In case you use 57600 Baud it should look like:<br />
{{Box Code|CONFIG.TXT|<br />
<source lang="xml"><br />
57600,26,3,0<br />
</source><br />
}}<br />
Furthermore you need to add the OpenLog-module to your airframe.<br />
{{Box Code|conf/airframes/yourairframe.xml|<br />
<source lang="xml"><br />
[...]<br />
<modules><br />
<load name="openlog.xml"/><br />
[...]<br />
</modules><br />
[...]<br />
</source><br />
}}<br />
Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog LOG00003.TXT <br />
now converting LOG00003.TXT to LOG00003.TXT.tlm<br />
The conversion from the logfile from the SD to TLM seems to be successful, 567 have been converted, 2 packages have been broken<br />
Renaming produced file ...<br />
12_06_17__01_59_45_SD.data file produced<br />
Looking for 4ae62580cb19d37d2b30aa8d31cc20dc conf...<br />
12_06_17__01_59_45_SD.log file produced<br />
12_06_17__01_59_45_SD.tlm file saved<br />
<br />
You can also do batch processing like:<br />
<br />
christoph@christoph:~/paparazzi/aktueller$ sw/logalizer/getopenlog /media/disk-1/LOG*<br />
<br />
In this case all logs will be imported.<br />
Afterwards you can find the logs as usual in var/logs/*_SD.log<br />
<br />
If someting goes wrong during the import have a close look to the error messages, since openlog2tlm tries to identify the most common problems.<br />
<br />
<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12767Openlog2012-06-24T11:07:33Z<p>Christoph: </p>
<hr />
<div>== Openlog ==<br />
In general OpenLog is a Module from Sparkfun that contains an Atmega324 and a Micro-SD-Slot. It can handle FAT-formated files-systems up to 2GB. Once installed into the wiring (parallel to the dataradio) it records every message the UAS sends. That is very handy for using it as some kind of blackbox or for data-logging purposes if no Modem was involved. It is also nice for reconstructing what happened after a crash, since the radio-communication is gone, once the plane is near the ground. 2GB is enough to log a comlete season (several hundred flights).<br />
The general logging is done in two steps: First you record your log using the telemtry in transparent mode, with the openlog-module loaded. the normal paparazzi-protocal does not contain timestamps and the openlog-module adds timestamps to the datastream to have a reference for the time.<br />
Second the recorded logs are extracted from the SD-Card to the normal logfiles. For doing so, there is a tool calles openlog2tlm to convert the recorded files to the TLM-format of the SD-logger. Next the created TLM-file is added to the logs by sd2log. <br />
There is a helper-script that does this job.<br />
=== Hardware ===<br />
<br />
[[File:openlog.jpg|300px]]<br />
<br />
The OpenLog is simply connected to the TX-Line of the AP. Once the AP is powered, it starts to record.<br />
<br />
=== Software ===<br />
<br />
First of all the OpenLog needs to be configured. If it was powered one time without being configured, but with SD-Card plugged, it creates a file named CONFIG.txt or CONFIG.TXT (depends on the version of the firmware). You need to configure the Baudrate, it defaults to 9600-8-N1. In case you use 57600 Baud it should look like:<br />
{{Box Code|CONFIG.TXT|<br />
<source lang="xml"><br />
57600,26,3,0<br />
</source><br />
}}<br />
Furthermore you need to add the OpenLog-module to your airframe.<br />
{{Box Code|conf/airframes/yourairframe.xml|<br />
<source lang="xml"><br />
[...]<br />
<modules><br />
<load name="openlog.xml"/><br />
[...]<br />
</modules><br />
[...]<br />
</source><br />
}}<br />
Then compile, flash your AP and do your flight. Afterwards take the SD-Card from the logger and import the logs:<br />
<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:Openlog.jpg&diff=12766File:Openlog.jpg2012-06-24T10:41:44Z<p>Christoph: Picture of OpenLog and wiring</p>
<hr />
<div>Picture of OpenLog and wiring</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Openlog&diff=12762Openlog2012-06-22T22:40:21Z<p>Christoph: Created page with "== Openlog == === Hardware === === Software === Category:Software Category:User_Documentation"</p>
<hr />
<div>== Openlog ==<br />
<br />
=== Hardware ===<br />
<br />
=== Software ===<br />
<br />
[[Category:Software]] [[Category:User_Documentation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Linux&diff=12108Installation/Linux2012-04-18T13:22:53Z<p>Christoph: /* Installation of Compilers and Handlers */</p>
<hr />
<div><categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Installation</categorytree><br />
__TOC__<br />
<br />
== Introduction ==<br />
<br />
Paparazzi is very easily installed on any laptop or workstation running the [http://www.ubuntu.com/ Ubuntu Linux OS] or virtually any [http://www.debian.org/ Debian] based [http://en.wikipedia.org/wiki/Linux Linux].<br />
<br />
The steps required to install the software needed to be able to let your UAS fly <br />
<ul><br />
<li>Install a recent Ubuntu Linux operating system<br />
<li>The basic Paparazzi tools installed via Synaptic Package Manager.<br />
<li>Download the source code from the source repository.<br />
<li>Allow access to your PC hardware connection by copying the [http://www.openuas.org/pub/writing_udev_rules.html rules file]<br />
<li>Compile the binaries from the sources (cd paparazzi && make)<br />
</ul><br />
<br />
That's all.<br />
<br />
=== Operating System ===<br />
<br />
Paparazzi is very easily installed on any laptop or workstation running the [http://www.ubuntu.com/ Ubuntu Linux OS] or virtually any [http://www.debian.org/ Debian] based [http://en.wikipedia.org/wiki/Linux Linux]. Paparazzi is packaged for Debian as well as all of it's dependencies. The [http://paparazzi.enac.fr/debian repository] hosted at ENAC holds their latest version.<br />
<br />
If you are new and this is your first time installing it is suggested you keep it simple. Select a system you can dedicate to the Linux installation. No [[Installation#Virtual_Machines|virtual machines]] or dual boot configurations. The idea is do a very simple generic installation that is certain to have no issues. This reassures you that the installation process works and you can see and use a working Paparazzi install for some time before you try a more complicated install. The install is well documented below and certain to succeed if followed exactly. Most issues arise when someone unfamiliar with Linux tries a non-standard install that requires special steps not documented here.<br />
<br />
=== Compilers and Handlers ===<br />
<br />
The typical installation contains all of the necessary C and OCaml compilers as well as some XML and [http://www.tls.cena.fr/products/ivy/ Ivy] handlers. These tools are provided by the ''paparazzi-dev'' package. Have no fear, this is all taken care of for you so all you must do is type a few simple commands. Below are those commands and helpful information. Commands can be copied and pasted from these pages to make it as easy as possible. <br />
<br />
=== Source Code ===<br />
<br />
The Paparazzi source code is hosted by [https://github.com/paparazzi/paparazzi Github]. It is downloaded using [http://en.wikipedia.org/wiki/Git_%28software%29 Git].<br />
<br />
== Installation of Compilers and Handlers ==<br />
For the impatient:<br />
* Add paparazzi the [https://launchpad.net/~paparazzi-uav/+archive/ppa paparazzi-uav ppa] for Ubuntu for Ubuntu: <tt>ppa:paparazzi-uav/ppa</tt><br/>or for Debian: <tt>deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> squeeze main</tt><br><br />
* Install: <tt>paparazzi-dev</tt> and <tt>paparazzi-arm-multilib</tt><br />
<br />
=== Adding the APT repository ===<br />
For any Ubuntu version run from the command line:<br />
sudo add-apt-repository ppa:paparazzi-uav/ppa<br />
<br />
==== Alternate Ubuntu repository and Debian ====<br />
The ubuntu repository at <tt>paparazzi.enac.fr/ubuntu</tt> contains some older packages and can be used instead of the ppa.<br />
<br />
For the sources file (sources.list) you only add the line required for your version. Linux names their versions. <br />
<br />
Just add the following lines to your repository list (<b>/etc/apt/sources.list</b>) and then<br />
uncomment the line relevant to your operating system (e.g. squeeze or natty):<br />
<br />
Note: Because of the sources.list file permissions maybe you will need to edit it with root access. In Terminal write this:<br />
<br />
gksudo gedit /etc/apt/sources.list<br />
{{Box Code|/etc/apt/sources.list|<br />
# Uncomment just _one_ of the following lines - depending on your OS version<br />
# deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> etch main<br />
# deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> lenny main<br />
# deb <nowiki>http://paparazzi.enac.fr/debian</nowiki> squeeze main<br />
# deb <nowiki>http://paparazzi.enac.fr/ubuntu</nowiki> lucid main<br />
# deb <nowiki>http://paparazzi.enac.fr/ubuntu</nowiki> maverick main<br />
# deb <nowiki>http://paparazzi.enac.fr/ubuntu</nowiki> natty main<br />
# deb <nowiki>http://paparazzi.enac.fr/ubuntu</nowiki> oneiric main<br />
}}<br />
<br />
=== Installing the packages ===<br />
<br />
Update your sources and install the dependencies needed for recompiling from the source (<b>dev</b>), and the cross-compiler toolchain <b>arm-multilib</b>:<br />
<br />
sudo apt-get update<br />
sudo apt-get install paparazzi-dev paparazzi-arm-multilib<br />
<br />
The <b>paparazzi-arm-multilib</b> package provides support for both ARM7 (i.e. Tiny or TWOG boards) as well as STM32 (i.e. Lisa boards). <br/><br />
<br />
==== Using Ubuntu Software Center ====<br />
For Ubuntu Oneiric (11.10)<br />
* Launch ''Software Sources'' (Red '''Wrench and gear''' icon -> '''System''' section)<br />
* Search for <tt>paparazzi-dev</tt> and <tt>paparazzi-arm-multilib</tt> packages and click on install.<br />
<br />
==== Using Synaptic Package Manager ====<br />
Note: The Synaptic Package Manager is not installed by default anymore under Ubuntu Oneiric (11.10). Either use the Software Center, command line or install Synaptic again.<br />
* Launch ''Synaptic Package Manager'' (Menu '''System/Administration''')<br />
* Click ''Reload'' to update your sources.<br />
* Search for <tt>paparazzi-dev</tt> and <tt>paparazzi-arm-multilib</tt> packages (use the ''Search'' button)<br />
* Mark them for installation (right-click on package names)<br />
* Left-click on ''Apply''<br />
<br />
=== Optional Packages ===<br />
sudo apt-get install lpc21isp openocd<br />
<br />
The packages <b>lpc21isp</b> and <b>openocd</b> are normally automatically installed as they are recommended packages of paparazzi-dev, if not you can manually install them. <tt>lpc21isp</tt> is needed to serially flash the LPC2148 based autopilots (e.g. bootloader for tiny, twog, umarim), <tt>openocd</tt> is for flashing via JTAG (e.g. for Lisa boards) and debugging.<br />
<br />
==== Obsolete Packages ====<br />
These packages are in the <tt>paparazzi.enac.fr/ubuntu (or debian)</tt> repository and unmaintained, but still might be of some use...<br />
<br />
* <b>paparazzi-avr</b> Users of the older AVR based boards will need this.<br />
* <b>paparazzi-arm7</b> To use the old gcc 3.4.4 for ARM7, superseded by <b>paparazzi-arm-multilib</b>. To use ''paparazzi-arm7'' remove ''paparazzi-arm-multilib''.<br />
* <b>paparazzi-stm32</b> Can be used for the Lisa autopilots, superseded by <b>paparazzi-arm-multilib</b>. To use ''paparazzi-stm32'' remove ''paparazzi-arm-multilib''.<br />
<br />
==== Older Ubuntu Versions ====<br />
<br />
On older Linux distributions (not needed for lucid and later), the Braille TTY driver interferes with FTDI USB Serial adapters. If somehow your FTDI serial adapter does not work, remove the package via:<br />
<br />
sudo apt-get remove brltty<br />
<br />
=== Manual Installation of Individual Packages ===<br />
Users of other Linux flavors than a recent Ubuntu or Debian and anyone needing manual control of each individual package can [[Manual_Installation|install them independently]].<br />
<br />
== Downloading the Source Code ==<br />
The complete source code should be downloaded from the paparazzi software repository on Github. Make sure you have installed the <tt>paparazzi-dev</tt> package as described above. Without these you will not be able to compile the sourcecode.<br />
<br />
Please see [[Installation#Downloading_the_Source_Code]] for details.<br />
<br />
== Launching the Software ==<br />
<br />
Please see [[Installation#Launching_the_Software]] for details.<br />
<br />
=== Quick Launch Icon ===<br />
<br />
To create an icon on the desktop so you don’t have to manually type codes into the Terminal each time you want to start the Paparazzi Center follow these steps:<br />
<br />
#Save [[Media:Paparazzi_logo.png|this image file]] to your /paparazzi folder<br />
#Right click anywhere on the Ubuntu desktop and click Create Launcher.<br />
#Enter the following in the fields provided:<br />
#*Name: Paparazzi Center<br />
#*Command: /home/YOUR_USER_NAME/paparazzi/paparazzi<br />
#*Comment: Runs the Paparazzi Center<br />
#*Then click the icon image in the top left on the dialog box and select the Paparazzi logo you just downloaded.<br />
#Click the OK button and that’s it! Your icon should appear on the desktop and you are ready to go.<br />
<br />
=== Agents ===<br />
<br />
Please see [[Installation#Agents]] for details.<br />
<br />
=== env Variables ===<br />
<br />
Please see [[Installation#env_Variables]] for details.<br />
<br />
== Udev rules ==<br />
Add the appropriate rule (available in fhe file ''50-paparazzi.rules'') to the USB handler. Simply copy as root <tt>conf/system/udev/rules/50-paparazzi.rules</tt> to <tt>/etc/udev/rules.d/</tt>, e.g in a terminal:<br />
<br />
cd <your paparazzi directory><br />
sudo cp conf/system/udev/rules/50-paparazzi.rules /etc/udev/rules.d/<br />
<br />
See the [[Udev]] page for more details.<br />
<br />
== Setting access rights for USB download ==<br />
<br />
On recent Ubuntu releases this is not necessary. For other distributions/releases this may be required to flash the Paparazzi-boards directly through USB. For flashing details, see [[Compiling]].<br />
<br />
Some Linux distributions, don't allow standard (non root) users to directly access the USB bus by default. You will need to make yourself a member of the plugdev "group" and then create a "rule", associated with that "group". <br><br />
Make yourself a member of the ''plugdev'' group:<br />
<br />
sudo adduser <your login> plugdev<br />
<br />
Logout and login again.<br />
<br />
== Software Updates ==<br />
<br />
Please see [[Installation#Software_Updates]] for details.<br />
<br />
== Using 32Bit on 64Bit ==<br />
<br />
As there are now 64bit packages available this should not be needed anymore, nevertheless...<br />
<br />
An temporary solution is to use an i386 installation instead. In rare circumstances however, this may be problematic (certain engineering software for example requires 64 bit kernels).<br />
In these cases, a chroot is a good compromise, while avoiding the overhead of a virtual machine (and USB device problems which may occur).<br />
Initial instructions are here for now: https://help.ubuntu.com/community/DebootstrapChroot<br />
The command you use for the bootstrap needs to reflect your architecture - I used<br />
<br />
sudo debootstrap --variant=buildd --arch i386 lucid /var/chroot/lucid http://gb.archive.ubuntu.com/ubuntu/<br />
<br />
The format for schroot config files has changed as of lucid however - here is mine:<br />
<br />
$ cat /etc/schroot/chroot.d/lucid-i386 <br />
[lucid]<br />
description=Ubuntu 10.04 Lucid for i386<br />
directory=/var/chroot/lucid<br />
personality=linux32<br />
root-users=my_user<br />
type=directory<br />
users=my_user<br />
<br />
Once you've installed the ubuntu minimal package, make sure you also enable the uni- and multiverse repos (the easiest way for me is to simply copy my host's /etc/apt/sources.lst to /var/chroot/lucid/etc/apt/sources.lst).<br />
Then follow the standard instructions above. You may need to manually set the PAPARAZZI_HOME and PAPARAZZI_SRC environment variables. You will also have to set the DISPLAY environment variable to :0.0 like so:<br />
<br />
export DISPLAY=:0.0<br />
<br />
Please note, this is more advanced than the standard paparazzi installation and therefore you may encounter strange problems.<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Modules_list&diff=11848Modules list2012-03-06T12:29:07Z<p>Christoph: /* Available modules */</p>
<hr />
<div><categorytree style="float:right; clear:right; margin-left:1ex; border: 1px solid gray; padding: 0.7ex;" mode=pages>Modules</categorytree><br />
Some part of the code is already available as [[Modules|modules]]. Some other parts could be easily adapted. A module may have several configuration files for the most common uses. The code of the modules is placed in sw/modules/<directory name>.<br />
<br />
=== Available modules ===<br />
<br />
{| class="wikitable" style="text-align:center" border="1"<br />
! Name !! directory !! configuration files !! airframe(s) !! description<br />
|-<br />
|Demo || demo_module || demo_module.xml || FW || basic example with blinking leds<br />
|-<br />
|max11040 || adcs || max11040.xml || FW || 24 bit 16 channel AD converter<br />
|-<br />
|[[Module/ADC_generic|ADC generic]] || adcs || adc_generic.xml || FW || autopilot internal 10 bit AD converter<br />
|-<br />
|Enose || enose || enose.xml || FW || chemical sensor<br />
|-<br />
|Booz cam || cam_control || booz_cam.xml || Booz || pointing of a simple camera on booz (servo for tilt, heading for pan<br />
|-<br />
|Cam point || cam_control || cam_point.xml || FW || pointing of a camera<br />
|-<br />
|Cam roll || cam_control || cam_roll.xml || FW || roll camera<br />
|-<br />
|Booz drop || drop || booz_drop.xml || Booz || drop mechanism on booz<br />
|-<br />
|light || light || light.xml || FW || control blinking speed of the LEDs for night flights<br />
|-<br />
|[[Module/Servo_switch|servo switch]] || servo_switch || servo_switch.xml || FW || simply switch a servo to "on" or "off" position, e.g. trigger camera or open hatch<br />
|-<br />
|Formation flight || multi || formation_flight.xml || FW || formation flight control for fixed-wing aircraft<br />
|-<br />
|Gps i2c || gps_i2c || gps_i2c.xml || FW || i2c driver for Ubx GPS modules<br />
|-<br />
|[[Module/GPS_UBlox_UCenter|GPS UBX µcenter]] || gps || gps_ubx_ucenter.xml || FW/Rotor || Module to initialise µ-blox GPS at every power on<br />
|-<br />
|Xsens || ins || ins_xsens.xml<br>ins_xsens_MTi_Uart0.xml<br>ins_xsens_MTiG_Uart0.xml || || driver for the Xsens AHRS/INS (for fixedwing it provides a full navigation solution, for rotorcraft it is a bit slow)<br />
|-<br />
|[[ArduIMU|ins_ArduIMU]] || ins || ins_arduimu.xml || FW || ArduIMU V2+ (Flat) INS (should probably be renamed to AHRS and adhere to the ahrs interface)<br />
|-<br />
|imu_ppzauv || sensors || imu_ppzuav.xml || FW/rotor || module to read the PPZIMU<br />
|-<br />
|imu_aspirin_i2c || sensors || imu_aspirin_i2c.xml || FW/rotor || module to read the aspirin IMU via I2C<br />
|-<br />
|VN-100 || ins || ins_vn100.xml || FW RW? || VectorNav VN-100 AHRS (should probably be renamed to AHRS and adhere to the ahrs interface)<br />
|-<br />
|Max 3100 || max3100 || max3100.xml || FW || max3100 driver (spi<->uart converter)<br />
|-<br />
|MPPT || MPPT || MPPT.xml || FW || maximum power point tracker (control board for solar cells, i2C interface)<br />
|-<br />
|Poles || poles || poles.xml || FW || special navigation functions to fly around poles and counting loops<br />
|-<br />
|Potential || multi || potential.xml || FW || use potential fields for collision avoidance<br />
|-<br />
|Sonar || sonar || sonar_maxbotix_booz.xml || Booz || driver for a Maxbotix ultrasonic sensor<br />
|-<br />
|dust_gp2y || meteo || dust_gp2y.xml || FW || driver for Sharp GP2Y1010AU0F dust sensor<br />
|-<br />
|humid_dpicco || meteo || humid_dpicco.xml || FW || driver for IST DigiPicco humidity sensor<br />
|-<br />
|humid_hih || meteo || humid_hih.xml || FW || driver for Honeywell HIH-4030 humidity sensor<br />
|-<br />
|humid_htm_b71 || meteo || humid_htm_b71.xml || FW || driver for TronSens HTM-B71 humidity sensor<br />
|-<br />
|humid_sht || meteo || humid_sht.xml || FW || driver for Sensirion SHT75 humidity sensor<br />
|-<br />
|humid_sht_i2c || meteo || humid_sht_i2c.xml || FW || driver for Sensirion SHT25 humidity sensor (I2C)<br />
|-<br />
|ir_mlx || meteo || ir_mlx.xml || FW || driver for Melexis 90614 IR sensor<br />
|-<br />
|light_temt || meteo || light_temt.xml || FW || driver for Vishay TEMT6000 ambient light sensor<br />
|-<br />
|temp_lm75 || meteo || temp_lm75.xml || FW || driver for National LM75 temperature sensor<br />
|-<br />
|temp_temod || meteo || temp_temod.xml || FW || Hygrosens TEMOD-I2C-Rx temperature sensor for PT1000<br />
|-<br />
|temp_tmp102 || meteo || temp_tmp102.xml || FW || driver for TI TMP102 temperature sensor<br />
|-<br />
|[[Module/infrared|infrared_adc]] || sensors || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/infrared_adc.xml infrared_adc.xml] || FW || driver for infrared sensors based on analog voltage<br />
|-<br />
|[[Module/infrared|infrared_i2c]] || sensors || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/infrared_i2c.xml infrared_i2c.xml] || FW || driver for infrared sensors with i2c connection<br />
|-<br />
|airspeed_adc || sensors || airspeed_adc.xml || FW || driver for airspeed sensor based on analog voltage<br />
|-<br />
|[[Airspeed_sensor#Connecting_an_EagleTree_Airspeed_Sensor|airspeed_ets]] || sensors || airspeed_ets.xml || FW || Eagle Tree Systems airspeed sensor<br />
|-<br />
|alt_srf08 || sensors || alt_srf08.xml || FW || driver for Devantech Ultrasonic Range Finder SRF08<br />
|-<br />
|baro_bmp || sensors || baro_bmp.xml || FW || driver for Bosch BMP085 pressure sensor<br />
|-<br />
|baro_ets || sensors || baro_ets.xml || FW || Eagle Tree Systems pressure sensor<br />
|-<br />
|baro_MS5534A || sensors || baro_MS5334A.xml || FW || driver for Intersema MS5534A pressure sensor<br />
|-<br />
|baro_ms5611_i2c || sensors || baro_ms5611_i2c.xml || FW || driver for Measurement Specialties MS5611-01BA pressure sensor<br />
|-<br />
|baro_scp || sensors || baro_scp.xml || FW || driver for VTI SCP1000 (SPI) pressure sensor<br />
|-<br />
|baro_scp_i2c || sensors || baro_scp_i2c.xml || FW || driver for VTI SCP1000 (I2C) pressure sensor<br />
|-<br />
|mag_micromag_fw || sensors || mag_micromag_fw.xml || FW || driver for PNI Micromag magnetic sensor<br />
|-<br />
|trigger_ext || sensors || trigger_ext.xml || FW || driver to measure external events/durations<br />
|-<br />
|[[Module/Xtend_rssi|xtend_rssi]] || datalink || xtend_rssi.xml || FW || driver to measure and report rssi from Digi 9Xtend radio with pwm input, currently only LPC21xx arch<br />
|-<br />
|[[Module/Pwm_meas|pwm_meas]] || core || pwm_meas.xml || FW || driver wrapper to measure duty and period of pwm input, currently only LPC21xx arch<br />
|-<br />
|Sys mon || core || sys_mon.xml || FW & Booz || measures CPU load & activity<br />
|-<br />
|DC || digital_cam || digital_cam.xml<br>digital_cam_i2c.xml || FW & RW || Controls Digital Camera Functions (buttons) like shoot/zoom/onoff/take pictures at regular intervals<br />
|-<br />
|[[Module/AOA_adc|AOA adc]] || sensors || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/AOA_adc.xml AOA_adc.xml] || FW || Reads the value of an US DIGITAL MA3-A10-236-N AoA Sensor and controls the elevator with its value<br />
|-<br />
|[[Module/FlightBenchmark|flight_benchmark]] || benchmark || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/flight_benchmark.xml flight_benchmark.xml] || FW || quantitative assessments of flights<br />
|-<br />
|[[AMSYS|airspeed_amsys]] || sensors || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/airspeed_amsys.xml airspeed_amsys.xml] || FW || driver for AMS 5812-0003-D (Airspeed) pressure sensors<br />
|-<br />
|[[AMSYS|baro_amsys]] || sensors || [https://github.com/paparazzi/paparazzi/blob/master/conf/modules/baro_amsys.xml baro_amsys.xml] || FW || driver for AMS 5812-0150-A (Baro) pressure sensors<br />
|-<br />
|[[Openlog|openlog]] || openlog || [https://github.com/chni/paparazzi/blob/master/conf/modules/openlog.xml openlog.xml] || FW & RW || Module for logging with a [http://www.sparkfun.com/products/9530 Sparkfun OpenLog]<br />
|}<br />
<br />
=== Possible modules ===<br />
<br />
A list of the parts of the FW airborne code that could be changed to modules.<br />
<br />
{| class="wikitable" style="text-align:center" border="1"<br />
! Name !! header !! init !! periodic !! event !! datalink !! description<br />
|-<br />
|Led || X || X || || || || control leds and GPIO<br />
|-<br />
|I2C || X || X || || || ||<br />
|-<br />
|SPI || X || X || || || ||<br />
|-<br />
|Traffic || X || || || || X || update traffic information from datalink<br />
|-<br />
|TCAS || X || X || 1Hz - 4Hz || || ? || vertical collision avoidance<br />
|-<br />
|GPS || X || X || || X || ||<br />
|-<br />
|Joystick || X || X || || X || X|| control a plane from telemetry<br />
|}<br />
<br />
[[Category:User_Documentation]] [[Category:Modules]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=11335Users2012-01-09T19:49:37Z<p>Christoph: /* Wiki User Pages */</p>
<hr />
<div>Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi<br />
<br />
== Wiki User Pages ==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ User Pages<br />
|-<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]<br />
|[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]<br />
|[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]<br />
|[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]<br />
|[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]<br />
|[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]<br />
|[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]<br />
|[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]<br />
|[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]<br />
|[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]<br />
|[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]<br />
|[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]<br />
|[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:Marc Marc]<br />
|[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]<br />
|[http://paparazzi.enac.fr/wiki/User:HWal HWal]<br />
|[http://paparazzi.enac.fr/wiki/User:Aerodolphin Rui Costa]<br />
|[http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer]<br />
|- style="background:bisque; color:black"<br />
|[http://paparazzi.enac.fr/wiki/User:PaulCox Paul Cox]<br />
|[http://paparazzi.enac.fr/wiki/User:Bruzzlee Bruzzlee]<br />
|[http://paparazzi.enac.fr/wiki/User:Stspies Stspies]<br />
|[http://paparazzi.enac.fr/wiki/User:Mzr Mzr]<br />
|[http://brquad.blogspot.com AGRESSiVA]<br />
|- style="background:bisque; color:black"<br />
|add yourself here<br />
|[http://paparazzi.enac.fr/wiki/User:Martial Martial Châteauvieux]<br />
|[http://paparazzi.enac.fr/wiki/User:Christoph Christoph]<br />
|<br />
|<br />
|}<br />
<br />
= Paparazzi Users sorted geographically =<br />
<br />
==Asia==<br />
<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ Asia<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
|- style="background:bisque; color:black"<br />
| [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中文)<br />
|- style="background:bisque; color:black"<br />
| [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!<br />
|- style="background:bisque; color:black"<br />
<br />
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.<br />
|- style="background:bisque; color:black"<br />
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe<br />
|- style="background:bisque; color:black"<br />
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe <br />
|- style="background:bisque; color:black"<br />
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!<br />
|- style="background:bisque; color:black"<br />
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet <br />
|- style="background:bisque; color:black"<br />
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon<br />
|- style="background:bisque; color:black"<br />
| [mailto:benybeejz@gmail.com benybee] || Bandar Lampung, Indonesia || Tiny13 1.1 ||| 2010 || trying to get wing dragon fully autonomus, for aireal photograph and research<br />
|- style="background:bisque; color:black" <br />
| [mailto:anilvanjare83@gmail.com Anil vanjare] || India || TWOG, Tiny v2.1,Umarim v10 ||| 2011 || ,working on Umarim board assembly with prashant<br />
|}<br />
<br />
==Europe==<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:lightgreen; color:black"<br />
|Austria<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:lightgreen; color:black"<br />
|France<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:limaiem@gmail.com Imed Limaiem] || Paris, France || TWOG 2.11, EPP-CF FPV ||| January 2010 || flight test; Town pollution measurement; <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox] <br />
| Toulouse <br />
| Tiny v2.11 || Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] <br />
<br />
|- style="background:lightgreen; color:black"<br />
|Germany<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.<br />
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz and Lisa/L ||| 2008 || coding more than flying.... unfortunately<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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])<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successful AUTO2-Flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Martial|Martial Châteauvieux]] || Munich, Germany || Bormatec/Maja with TWOG and IR ||| 2011 || Next test in January 2012, as soon as the weather permits. Hopefully I can switch in AUTO2.<br />
|- style="background:bisque; color:black"<br />
| [[User:Stspies|Steffen Spies]] || Wolfsburg, Germany || Multiplex TwinStar with Tiny V2.11 and IR ||| 2010 || Awaiting first flight. <br />
<br />
|- style="background:bisque; color:black"<br />
| [[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<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:RoN|Rolf N]] || Bremen, Germany || Multiplex Acromaster with TWOG, airspeed and imu ||| 2010 || Several successful AUTO2 flights<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:rijo1011_at_gmail.com Jochen Rieger] || Karlsruhe, Germany || Bormatec Maja, Lisa/L ||| 2011 || I hope the first flight is coming soon.<br />
<br />
|- style="background:lightgreen; color:black"<br />
| Portugal<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting<br />
<br />
<br />
|- style="background:lightgreen; color:black"<br />
|Switzerland<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny v2.11, TWOG v1, EeePC as GCS, Multiplex FunJet & EasyStar ||| 2008 || Many successful flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:samuelbryner_gmx.ch Samuel B.] || Winterthur, Switzerland || Tiny 2.11, Multiplex Easyglider ||| 2010 || Just starting. No flight so far :/<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:rmaurer@sunrise.ch RetoM] || Bottighofen, Switzerland || Tiny 2.11/YAPA2/ArduIMU, Multiplex Mentor, SebArt Wind S 50E ||| 2010 || Many flights successfully performed, including auto-landing, more to go ...<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:sjwilks_at_gmail.com Simon W.] || Aarau, Switzerland || TWOG with ArduIMU in Jamara Roo, TWOG on a Telink Tempest flying wing, YAPA2 on a Bormatec Maja, Lisa/L on a Droidworx AD-8 HL ||| 2010 || Many successful flights. See [http://sites.google.com/site/paparazziuav/ http://sites.google.com/site/paparazziuav/].<br />
<br />
|- style="background:lightgreen; color:black"<br />
| UK<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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!).<br />
<br />
<br />
|- style="background:lightgreen; color:black"<br />
| Other<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[ 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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [[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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor <br />
|<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:helgewal@gmail.com Helge] || Bergen, Norway || TWOG ||| 2009 || First Auto2 flight with Twinstar2 in October 2010 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|}<br />
<br />
==North America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 || <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. <br />
<br />
|- style="background:bisque; color:black"<br />
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project<br />
<br />
|- style="background:bisque; color:black"<br />
| 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. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Scdwyer Stephen Dwyer] || Edmonton, AB, CAN || Nothing Yet ||| Jan 2011 || Obtaining Hardware <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muratagenc@yahoo.com Murat A. Genc] || New York, NY || not decided yet ||| May 2011 || just started<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Central America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==South America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Australia==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|}<br />
<br />
==Africa==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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 ...<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
|}<br />
<br />
=Need help adding your information?=<br />
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 <br />
following:<br />
<br />
*Name<br />
*Email<br />
*Location<br />
*Hardware<br />
*Join date<br />
*Current activities / project status<br />
<br />
[[Category:Community]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8226User:Christoph2010-12-23T13:57:16Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap one from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch I will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view only, perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8225User:Christoph2010-12-23T13:53:02Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch I will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view only, perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8224User:Christoph2010-12-23T13:51:51Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view only, perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8223User:Christoph2010-12-23T13:51:09Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view only, perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8222User:Christoph2010-12-23T13:48:20Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view, only perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8221User:Christoph2010-12-23T13:47:50Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view, only perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own Attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8220User:Christoph2010-12-23T13:47:30Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view, only perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own Attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]<br />
<br />
Cheers <br />
<br />
Christoph</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8219User:Christoph2010-12-23T13:46:07Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]<br />
<br />
There is also a YouTube-Video showing the plane to fly circles (GCS view, only perhaps boring): [http://www.youtube.com/watch?v=aqzqhyAQs38]<br />
<br />
For the ones that might be interrested in the Data-File of the Flight (for having fixed wing IMU-Data for developing own Attitude estimation SW), the Logfile can be found here: [http://www.christoph-niemann.net/pprz]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:Gcschni.jpg&diff=8218File:Gcschni.jpg2010-12-23T13:41:52Z<p>Christoph: </p>
<hr />
<div></div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8217User:Christoph2010-12-23T13:41:01Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcschni.jpg|600px|x]]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8216User:Christoph2010-12-23T13:40:38Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
In the mechanical point of view, I had to change some things on the Plane:<br />
<br />
- change the Prop-Saver, since the delivered one was rubbish<br />
- mount the IMU on the LiPo wich was suspended in foam to reduce vibrations<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]<br />
<br />
And what is on the Screen, while in flight :-)<br />
<br />
[[Image:gcs.jpg|600px|x]]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:Ground.jpg&diff=8215File:Ground.jpg2010-12-23T13:37:36Z<p>Christoph: </p>
<hr />
<div></div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8214User:Christoph2010-12-23T13:36:42Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]<br />
<br />
A Picture of the entire Groundstation:<br />
<br />
[[Image:ground.jpg|600px|x]]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8213User:Christoph2010-12-23T13:35:44Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|600px|x]]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8212User:Christoph2010-12-23T13:35:18Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg|800px|x]]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=File:Condor.jpg&diff=8211File:Condor.jpg2010-12-23T13:33:11Z<p>Christoph: </p>
<hr />
<div></div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8210User:Christoph2010-12-23T13:32:23Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:condor.jpg]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8209User:Christoph2010-12-23T13:31:12Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.<br />
<br />
Currently my plane looks like this:<br />
<br />
[[Image:http://farm5.static.flickr.com/4149/5222720261_be8a6dcec6_b.jpg]]</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8208User:Christoph2010-12-23T13:29:45Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters, that might not be nescessary for the new one.<br />
<br />
So the system was really cheap, what was improtant for me as a student :-) <br />
<br />
On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8207User:Christoph2010-12-23T13:27:30Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''<br />
<br />
The plane is a cheap on from Conrad Electronic (50€ incl. RC).<br />
The Paparazzi-System consists of a TWOG, some wi.232-Modules for Telemetry a cheap Navilock-GPS NL-507TTL (30€) and instead of using IR-Sensors for attitude estimation, I have used a Sparkfun Razor IMU (http://www.sparkfun.com/products/9431). That one is deprecated and I had to remove some frequency-filters. On the TWOG side I have bridged the Resistors for scaling to Something else than 3.3V for the ADC.<br />
The current working version of the Software is checked into GitHub: https://github.com/chni/paparazzi<br />
Since Felix and Christophe started the integration of the analogimu stuff into the main-branch i will switch to this soon, but yet the github-version works for me.</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=User:Christoph&diff=8206User:Christoph2010-12-23T13:19:46Z<p>Christoph: </p>
<hr />
<div>'''Reely Condor with Sparkfun Razor IMU'''</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=8205Users2010-12-23T13:18:49Z<p>Christoph: /* Europe */</p>
<hr />
<div>Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi<br />
<br />
==Need help adding your information?==<br />
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 <br />
following:<br />
<br />
*Name<br />
*Email<br />
*Location<br />
*Hardware<br />
*Join date<br />
*Current activities / project status<br />
<br />
== Wiki pages ==<br />
add a link to your users wiki page.<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Marc Marc]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:HWal HWal]<br />
<br />
==Asia==<br />
<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ Asia<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
|- style="background:bisque; color:black"<br />
<br />
| [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!<br />
|- style="background:bisque; color:black"<br />
<br />
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.<br />
|- style="background:bisque; color:black"<br />
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe<br />
|- style="background:bisque; color:black"<br />
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe <br />
|- style="background:bisque; color:black"<br />
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!<br />
|- style="background:bisque; color:black"<br />
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet <br />
|- style="background:bisque; color:black"<br />
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon<br />
|}<br />
<br />
==Europe==<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
|Austria<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|France<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:limaiem@gmail.com Imed Limaiem] || Paris, France || TWOG 2.11, EPP-CF FPV ||| January 2010 || flight test; Town pollution measurement; <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox] <br />
| Toulouse <br />
| Tiny v2.11 || Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] <br />
<br />
|- style="background:bisque; color:black"<br />
|Germany<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.<br />
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz2 quadrotor ||| 2008 || flying, but a lot to improve ;-)<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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])<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successful AUTO2-Flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| Portugal<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|Switzerland<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny v2.11, TWOG v1, EeePC as GCS, Multiplex FunJet & EasyStar ||| 2008 || Many successful flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:reto.buettner_at_gmail.com RetoB] || Meilen, Switzerland || TWOG, Tiny 2.11, AeroMaster, E-Hawk, 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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:enso@zhaw.ch Oliver Ensslin] || Winterthur, Switzerland || Tiny 2.11 incl. ArduIMU, Kyosho Calmato, UMARS||| 2010 || Still struggling to get in the air with Calmato. Successful flights with Maya. Now with the new reorganized code. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:samuelbryner_gmx.ch Samuel B.] || Winterthur, Switzerland || Tiny 2.11, Multiplex Easyglider ||| 2010 || Just starting. No flight so far :/<br />
<br />
|- style="background:bisque; color:black"<br />
| UK<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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!).<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| Other<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[ 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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:openuas|OpenUAS]] || Amsterdam, The Netherlands || TWOG, Tiny and various airframes || 2007 || Quite a few AUTO2 flights. Improving airspeed integration<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor <br />
|<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:helgewal@gmail.com Helge] || Bergen, Norway || TWOG ||| 2009 || First Auto2 flight with Twinstar2 in October 2010 <br />
|}<br />
<br />
==North America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 || <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. <br />
<br />
|- style="background:bisque; color:black"<br />
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project<br />
<br />
|- style="background:bisque; color:black"<br />
| 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. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Central America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==South America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Australia==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|}<br />
<br />
==Africa==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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 ...<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
|}</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Downloads&diff=8045Downloads2010-11-09T16:18:18Z<p>Christoph: /* Paparazzi Source Code */</p>
<hr />
<div>== Paparazzi Boot CD ==<br />
* Burn this to a CD and boot from it to try Paparazzi without any software changes to your PC! Includes Debian, Paparazzi, and all required libraries.<br />
*: [http://www.recherche.enac.fr/paparazzi/paparazzix/ Download Page]<br />
* Boot the CD, sit back, relax and enjoy the scenery.<br />
*: [[Using the Boot CD]] step by step - howto<br />
<br />
(Note: The image file [http://www.recherche.enac.fr/paparazzi/paparazzix/paparazziX_Mas2008.iso paparazziX_Mas2008.iso] is the latest and greatest version of the boot-CD)<br />
<br />
== Paparazzi Binary Package ==<br />
* Install this package to your Debian system<br />
*: [http://www.recherche.enac.fr/paparazzi/debian/ Http Download Page].<br />
<br />
== Paparazzi Source Code ==<br />
* Browse the current code tree here:<br />
*: http://svn.savannah.gnu.org/viewvc/paparazzi/paparazzi3/<br />
* If you want to update your exiting paparazzi code, follow these [[Installation#Software_Updates|instructions]]. It is advised to first backup your personal modifications. Either by renaming the files (e.g. easystar_myname.xml) or by saving in another directory. You might need the backup if something gets overwritten by the current source.<br />
* Download the current source tree using our anonymous SVN server by running this command from your home directory<br />
svn co svn://svn.savannah.nongnu.org/paparazzi/paparazzi3/trunk paparazzi3<br />
or through <tt>http</tt> (proxy configuration is <tt>~/.subversion/servers</tt>)<br />
svn co http://svn.savannah.gnu.org/svn/paparazzi/paparazzi3/trunk paparazzi3<br />
You should only need to do this once. For updates follow these [[Installation#Software_Updates|instructions]].<br />
<br />
== Paparazzi Hardware Plans ==<br />
* Download Eagle files for all current and past autopilot, sensor, and miscellaneous hardware.<br />
*: http://svn.savannah.gnu.org/viewvc/paparazzi/paparazzi3/hw/<br />
* Be sure to download both *.brd and *.sch files and use Cadsoft Eagle to view them. [http://www.cadsoft.de/freeware.htm Eagle (free version)]<br />
<br />
== User Submitted Files ==<br />
* Upload your patches, scripts, etc. here. Please sign your entry!<br />
<br />
=== Matlab Files ===<br />
<br />
=== Other Files ===</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Downloads&diff=8044Downloads2010-11-09T16:17:18Z<p>Christoph: /* Paparazzi Hardware Plans */</p>
<hr />
<div>== Paparazzi Boot CD ==<br />
* Burn this to a CD and boot from it to try Paparazzi without any software changes to your PC! Includes Debian, Paparazzi, and all required libraries.<br />
*: [http://www.recherche.enac.fr/paparazzi/paparazzix/ Download Page]<br />
* Boot the CD, sit back, relax and enjoy the scenery.<br />
*: [[Using the Boot CD]] step by step - howto<br />
<br />
(Note: The image file [http://www.recherche.enac.fr/paparazzi/paparazzix/paparazziX_Mas2008.iso paparazziX_Mas2008.iso] is the latest and greatest version of the boot-CD)<br />
<br />
== Paparazzi Binary Package ==<br />
* Install this package to your Debian system<br />
*: [http://www.recherche.enac.fr/paparazzi/debian/ Http Download Page].<br />
<br />
== Paparazzi Source Code ==<br />
* Browse the current code tree here:<br />
*: http://svn.savannah.gnu.org/viewvc/paparazzi3/trunk/?root=paparazzi<br />
* If you want to update your exiting paparazzi code, follow these [[Installation#Software_Updates|instructions]]. It is advised to first backup your personal modifications. Either by renaming the files (e.g. easystar_myname.xml) or by saving in another directory. You might need the backup if something gets overwritten by the current source.<br />
* Download the current source tree using our anonymous SVN server by running this command from your home directory<br />
svn co svn://svn.savannah.nongnu.org/paparazzi/paparazzi3/trunk paparazzi3<br />
or through <tt>http</tt> (proxy configuration is <tt>~/.subversion/servers</tt>)<br />
svn co http://svn.savannah.gnu.org/svn/paparazzi/paparazzi3/trunk paparazzi3<br />
You should only need to do this once. For updates follow these [[Installation#Software_Updates|instructions]].<br />
<br />
== Paparazzi Hardware Plans ==<br />
* Download Eagle files for all current and past autopilot, sensor, and miscellaneous hardware.<br />
*: http://svn.savannah.gnu.org/viewvc/paparazzi/paparazzi3/hw/<br />
* Be sure to download both *.brd and *.sch files and use Cadsoft Eagle to view them. [http://www.cadsoft.de/freeware.htm Eagle (free version)]<br />
<br />
== User Submitted Files ==<br />
* Upload your patches, scripts, etc. here. Please sign your entry!<br />
<br />
=== Matlab Files ===<br />
<br />
=== Other Files ===</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=6991Users2010-07-23T14:51:48Z<p>Christoph: /* Europe */</p>
<hr />
<div>Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi<br />
<br />
==Need help adding your information?==<br />
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 <br />
following:<br />
<br />
*Name<br />
*Email<br />
*Location<br />
*Hardware<br />
*Join date<br />
*Current activities / project status<br />
<br />
== Wiki pages ==<br />
add a link to your users wiki page.<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Marc Marc]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]<br />
<br />
==Asia==<br />
<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ Asia<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
|- style="background:bisque; color:black"<br />
<br />
| [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!<br />
|- style="background:bisque; color:black"<br />
<br />
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.<br />
|- style="background:bisque; color:black"<br />
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe<br />
|- style="background:bisque; color:black"<br />
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe <br />
|- style="background:bisque; color:black"<br />
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!<br />
|- style="background:bisque; color:black"<br />
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet <br />
|- style="background:bisque; color:black"<br />
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon<br />
|}<br />
<br />
==Europe==<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
|Austria<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|France<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox] <br />
| Toulouse <br />
| Tiny v2.11 || Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] <br />
<br />
|- style="background:bisque; color:black"<br />
|Germany<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.<br />
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz2 quadrotor ||| 2008 || flying, but a lot to improve ;-)<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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])<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successful AUTO2-Flights but still need to improve the Configuration<br />
<br />
|- style="background:bisque; color:black"<br />
| Portugal<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|Switzerland<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny v2.11, TWOG v1, EeePC as GCS, Multiplex FunJet & EasyStar ||| 2008 || Many successful flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:reto.buettner_at_gmail.com RetoB] || Meilen, Switzerland || TWOG, Borjet Maja, 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.<br />
<br />
|- style="background:bisque; color:black"<br />
| UK<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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!).<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| Other<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[ 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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor <br />
|}<br />
<br />
==North America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 || <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. <br />
<br />
|- style="background:bisque; color:black"<br />
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project<br />
<br />
|- style="background:bisque; color:black"<br />
| 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. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Central America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
<br />
==Australia==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|}<br />
<br />
==Africa==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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 ...<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
|}</div>Christophhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=6989Users2010-07-23T14:47:32Z<p>Christoph: /* Europe */</p>
<hr />
<div>Please add yourself to this list if you wish to share who you are and what you are doing with Paparazzi<br />
<br />
==Need help adding your information?==<br />
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 <br />
following:<br />
<br />
*Name<br />
*Email<br />
*Location<br />
*Hardware<br />
*Join date<br />
*Current activities / project status<br />
<br />
== Wiki pages ==<br />
add a link to your users wiki page.<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Dconger Dconger]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:MarcusWolschon MarcusWolschon]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Alfamyke Alfamyke]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Danstah Danstah]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinmm Martinmm]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:John_Burt John Burt]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:SilaS SilaS]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Mecevans Mecevans]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:CSU-FCUAV CSU-FCUAV]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:GPH Pierre-Selim]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Martinpi martinpi]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:VAMK VAMK]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:EldenC Elden_Crom]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Rbdavison Bernard Davison]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:jvs84 U of Arizona Autonomous Glider]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Marc Marc]<br />
<br />
[http://paparazzi.enac.fr/wiki/User:Bu5hm4nn Bu5hm4nn]<br />
<br />
==Asia==<br />
<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|+ Asia<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
|- style="background:bisque; color:black"<br />
<br />
| [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!<br />
|- style="background:bisque; color:black"<br />
<br />
| [mailto:mnwxiaobao@gmail.com MNW]|| China || Tiny2.11 ||| 2009 || Just starting,having troubles with parts.<br />
|- style="background:bisque; color:black"<br />
| [mailto:shubhamearly@gmail.com Shubham]|| India || Tiny2.11 ||| 2009 || Writing the configuration code for airframe<br />
|- style="background:bisque; color:black"<br />
| [mailto:mundhra@gmail.com M Mundhra] || India || Tiny 1.3 ||| 2007 || Gain tuning on a flying wing configuration airframe <br />
|- style="background:bisque; color:black"<br />
| [mailto:ngkiangloong_at_hopetechnik.com Jianlun]|| Singapore || TWOG V1 ||| 2008 || trying to get TWOG onto an EasyStar. very much a newbie!<br />
|- style="background:bisque; color:black"<br />
| [mailto:praxmail@gmail.com prashanth] || India || Tiny 2.11 ||| 2008 || 6 autonomous flights till now, currently build a new wing like funjet <br />
|- style="background:bisque; color:black"<br />
| [mailto:spencerpangborn@gmail.com spencer] || Taipei, Taiwan || none ||| 2009 || research for now, hope to take aerial photos of Taipei City soon<br />
|}<br />
<br />
==Europe==<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
|Austria<br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Martinpi Martin Piehslinger] || Vienna, Austria || Tiny 2.11 || 2008 || just starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|France<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pvol_at_club.fr Philippe Volivert] || Paris, France || TWOG 2.12, EasyGlider, MPX3030 ||| July 2009 || Working on pan/tilt/roll camera<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:thibaut.bergal@estaca.eu ESTACA Modélisme] || Paris, France || TWOG 2.11, Swift 2, MC22 ||| January 2010 || Starting<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:pauldanielcox_at_gmail_dot_com Paul Cox] <br />
| Toulouse <br />
| Tiny v2.11 || Nov. 2008 || GWS Slow Stick flying in AUTO2 reliably. Starting on stabilized video and payload drops Skype: pauldanielcox Gtalk: [use email] <br />
<br />
|- style="background:bisque; color:black"<br />
|Germany<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:MarcusWolschon|Marcus Wolschon]] || Freiburg, Germany || Gumstix, Paraplane ||| 2008 || Porting Paparazzi to Linux-Userland with UDP-communication using mesh-networking.<br />
UDP-Downlink working, GPS via GPSD working, Pararazzi in Linux working, Hardware still RC-only due to sensor-soldering-issues<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Flixr|Felix Ruess]] || Munich, Germany || Booz2 quadrotor ||| 2008 || flying, but a lot to improve ;-)<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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])<br />
<br />
|- style="background:bisque; color:black"<br />
| [[User:Christoph|Christoph Niemann]] || Bremen, Germany || Reely Condor with TWOG and Sparkfun Razor-IMU ||| 2010 || Several successfull AUTO2-Flights but still need to improve the Configuration)<br />
<br />
|- style="background:bisque; color:black"<br />
| Portugal<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:muralha_at_gmail.com Nuno Guedes] || Lamego, Portugal || Tiny 2.11 || 2008 || Starting<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
|Switzerland<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:markggriffin_at_gmail.com MarkG] || Geneva, Switzerland || Modified Tiny v2.11, TWOG v1, EeePC as GCS, Multiplex FunJet & EasyStar ||| 2008 || Many successful flights. <br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:reto.buettner_at_gmail.com RetoB] || Meilen, Switzerland || TWOG, Borjet Maja, 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.<br />
<br />
|- style="background:bisque; color:black"<br />
| UK<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:et@onyxnet.co.uk Alan K] || Middlesbrough, England || Tiny 2.11 & MaxStream ||| 2008 || Just starting.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[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!).<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| Other<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [[ 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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:sanarlab@yandex.ru Andrew Saenko] || Russia, St-Petersburg || Tiny 1.13, Tiny 2.11, 2.5 kg motorised glider, 800 g plane ||| 2007 || Automatic flight, adding own code.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:alexandru.panait@ral.ro Phineas] || Bucharest, Romania || Tiny2.11 (PPZUAV) ||| November 2009 || Just started to set-up <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:lukeiron@hotmail.com Luke] || Torino, Italy || TWOG ||| December 2009 || Close to mount the AP on my Mentor <br />
|}<br />
<br />
==North America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status <br />
<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Mcurrie Matthew Currie] || Nanaimo, BC Canada || Tiny 13 v1.1 (Self-built) ||| November 2006 || Funjet + XBee<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:kochesj@gvsu.edu John Koches] || Muskegon, Michigan || Tiny 2.11 (PPZUAV) ||| 2007 || currently flying a 48 inch zagi, 80 inch under construction.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:Stdeguir@gmail.com Steve Deguir] || New York,New York || Tiny2.11+LEA-5H (PPZUAV), XbeePro 2.4, Berg4L, JR FMA ||| Feb 2009 || <br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [mailto:mecevans@gmail.com Michael Evans] || Seaside(Monterey Bay), California || Tiny2.11 (PPZUAV) ||| Feb 2009 ||http://www.rcgroups.com/forums/showthread.php?t=1000937. <br />
<br />
|- style="background:bisque; color:black"<br />
| USU AggieAir Remote Sensing || Logan, UT || TWOG (PPZUAV) ||| January 2009 || Building 72" Flying Wings which will be used for remote sensing. Routine autonomous flight.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [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 <br />
<br />
|- style="background:bisque; color:black"<br />
| [Reegan] || Lubbock, TX || Planning on Tiny 2.11 (PPZUAV), 900mhz XBPro |||Dec. 2009 || Gaining info to begin a collegiate project<br />
<br />
|- style="background:bisque; color:black"<br />
| 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. <br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
<br />
<br />
<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
==Central America==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
| New User || 1 || 2 ||| 3 || 4 <br />
|}<br />
<br />
<br />
==Australia==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
|-<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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. <br />
|- style="background:bisque; color:black"<br />
| [mailto:reubenb87@gmail.com Reuben Brown]|| Gawler, SA || Tiny v2.11 ||| May 2009 || Getting the autopilot set up <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|- style="background:bisque; color:black"<br />
| [http://paparazzi.enac.fr/wiki/User:Rufus Chris Gough] || Canberra || TWOG v2.11, EZ* || September 09 || not yet airborn <br />
|- style="background:bisque; color:black"<br />
| [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<br />
|}<br />
<br />
==Africa==<br />
<br />
{| class="wikitable" style="text-align:center;background:black; color:blue"<br />
! Name !! Location !! Hardware !! Joined !! Current activities / project status<br />
|- style="background:bisque; color:black"<br />
| [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 ...<br />
|- style="background:bisque; color:black"<br />
| [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.<br />
|- style="background:bisque; color:black"<br />
|}</div>Christoph