http://wiki.paparazziuav.org/w/api.php?action=feedcontributions&feedformat=atom&user=ImanPaparazziUAV - User contributions [en]2026-04-08T07:06:05ZUser contributionsMediaWiki 1.37.1http://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24184Installation/Windows102019-04-16T05:40:30Z<p>Iman: /* Graphical Interface */ add a link to new paparazzi center</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 />
=Intro=<br />
[[File:Win+papa.jpg|250px|thumb|right]]<br />
<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's '''not so efficient''' to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands(it's like usual [[Installation#Quickstart_for_Ubuntu_users|ubuntu installation command]]):<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
You can also install [https://wiki.gnome.org/Apps/Gedit gedit], to be able to edit your aircraft files (airframe, flight plan, etc) from within the center, since it is the default app that Paparazzi center uses.<br />
sudo apt-get install gedit<br />
<br /><br />
After that you can launch Paparazzi. (Or use the [[Paparazzi_Center/Evolutions#New_Paparazzi_Center|new Paparazzi center]] which works seamless on windows) <br />
cd ~/paparazzi && ./paparazzi<br />
<br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft using Paparazzi link application.<br />
sw/ground_segment/tmtc/link -d /dev/ttyS15<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24177Installation/Windows102019-03-09T12:18:38Z<p>Iman: </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 />
=Intro=<br />
[[File:Win+papa.jpg|250px|thumb|right]]<br />
<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's '''not so efficient''' to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands(it's like usual [[Installation#Quickstart_for_Ubuntu_users|ubuntu installation command]]):<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
After that you can launch Paparazzi. <br />
cd ~/paparazzi && ./paparazzi<br />
You can also install [https://wiki.gnome.org/Apps/Gedit gedit], to be able to edit your aircraft files (airframe, flight plan, etc) from within the center, since it is the default app that Paparazzi center uses.<br />
sudo apt-get install gedit<br />
<br /><br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft using Paparazzi link application.<br />
sw/ground_segment/tmtc/link -d /dev/ttyS15<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation&diff=24167Installation2019-02-19T13:37:44Z<p>Iman: Add description for windows version</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] or Apple Macintosh running [http://en.wikipedia.org/wiki/OS_X Mac OS X]. After Microsoft introduced Ubuntu on Windows, now it is possible to run Paparazzi on [https://en.wikipedia.org/wiki/Windows_10 Windows 10]. There is also another work being done to port Paparazzi to Windows with a different approach to work on all versions of Windows.<br />
<br />
The steps required to install the software needed to be able to let your UAS fly are:<br />
<br />
# Install tools and prerequisites needed by Paparazzi.<br />
# Download the source code from the source repository.<br />
# Compile the Paparazzi software from sourcecode<br />
# Complete any final configuration<br />
<br />
== Quickstart for Ubuntu users ==<br />
Love one-liners? To get the latest Paparazzi up and running on your '''Ubuntu 12.04 or higher OS''', make sure you have a working internet connection and the '''universe''' packages activated in 'Software & Updates', then just copy and paste the text below into your terminal and press [enter] ... and wait a while...<br />
<br />
<nowiki><br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
</nowiki><br />
<br />
[[File:Done.jpg|frameless|center|Done!]]<br />
If all went well the Paparazzi Center should now be running... '''skip''' the rest of this page and go fly! <br />
<br />
If you are new you'll need to do some more things before you go fly like configuring your XML definition file detailing your airframe configuration. There is help here for that: [[Airframe_Configuration]]<br />
<br />
In case you have no autopilot hardware yet, no problem, you can get hardware [[Get_Hardware|here]] or just buy a ready to fly aircraft that can run Paparazzi Software like the Parrot Drones [http://www.parrot.com/products/bebop-drone/ Parrot Bebop] and run Paparazzi on your Parrot [[AR_Drone_2|ARDRone2]], [[Bebop|Bebop]] and Bebop2 (soon the Disco drone).<br />
<br />
== OS Specific Instructions ==<br />
<br />
For Linux an instructional video explaining it all in detail can be found here https://www.youtube.com/watch?v=eW0PCSjrP78<br />
<br />
The process of installing the prerequisite tools and dependencies needed by Paparazzi is specific to the operating system you are using. For detailed installation instructions, please see the following pages:<br />
*[[Installation/Linux|Installing prerequisites tools on Linux]]<br />
*[[Installation/MacOSX|Installing prerequisites tools on Mac OS X]]<br />
*[[Installation/RaspberryPi|Installing prerequisites tools on the RaspberryPi (Raspbian)]]<br />
<br />
For more advanced installation information or developers, please see the following pages:<br />
*[[Installation/FromScratch|Installing everything from scratch]] For non Debian based Linux distributions or if one just wants to be able to use all the latest and greatest compilers, or source code of everything to improve something. Then there is no other way than to install from scratch.<br />
*[[Installation/Windows|Installing prerequisite tools on Windows]] Note that this is '''a work in progress, and not finished yet'''. It would be fantastic if you are interested in running Paparazzi on this OS to help out with the porting. Being able to help is one of opensource software main features. If your skill- set is not so good in this area, but you still insist using Windows OS, then it is best to install a VirtualMachine from within Windows where you run the free Ubuntu OS of choice.<br />
<br />
=== Virtual Machines ===<br />
<br />
It is also possible to have your Debian/Ubuntu running in a virtual machine, for instance with [http://www.virtualbox.org/ VirtualBox]. This requires minimal changes to your computer setup, as you can run the VM from all common platforms (Windows, OS X, Linux). The virtual machine image can easily be transferred between different laptops, giving greater flexibility. Unfortunately, the Open-Source Edition of VirtualBox doesn't include the necessary USB support, so you'll need to get the regular version from the website.<br />
<br />
If you are new and this is your first time installing it is suggested you keep it simple. Use the standard Linux or OS X install. Select a system you can dedicate to the Linux installation. No VMs 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 and certain to succeed if followed exactly. Most issues arise when someone unfamiliar with Paparazzi or their OS tries a non-standard install that requires special steps that are not documented. Generally, commands can be copied and pasted for easy, step-by-step installation.<br />
<br />
== Getting the Source Code ==<br />
The Paparazzi source code is hosted on [https://github.com/paparazzi/paparazzi Github]. While you can download it as a tarball from https://github.com/paparazzi/paparazzi/releases, it is recommended to clone the repository with [[git]].<br />
<br />
From the directory of your choice type:<br />
git clone --origin upstream https://github.com/paparazzi/paparazzi.git<br />
Check out the released stable version branch:<br />
cd paparazzi<br />
git checkout v5.14<br />
<br />
'''If this whole "Git" thing is new to you, more options and information can be found on the [[git|Git page]].'''<br />
<br />
== Launching the Software ==<br />
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 />
The first step is to compile. From the <tt>paparazzi</tt> directory (<tt>cd ~/paparazzi</tt>), run<br />
<br />
make<br />
<br />
You will have to run this command after each update of the source (<tt>git pull</tt> command).<br />
Launch the software from the <tt>paparazzi</tt> directory with<br />
<br />
./paparazzi<br />
<br />
From the [[Paparazzi_Center|Paparazzi Center]] interface, select the ''Microjet'' aircraft, select the ''sim'' target and ''Build'' it. Then ''Execute'' the ''Simulation'' session. The procedure is detailed in the [[Simulation]] page.<br />
<br />
=== Environment Variables ===<br />
<br />
If ('''and only if''') you want to directly launch some Paparazzi agents (the ''Tools'' of the [[Paparazzi_Center|Paparazzi Center]]) from the command line, without using the Paparazzi Center, you must have the Paparazzi source and home environment variables set correctly in your shell. These variables can be automatically set in your shell by adding the following lines to your .bashrc file:<br />
{{Box Code|~/.bashrc|<br />
<source lang="bash"><br />
export PAPARAZZI_HOME=''your paparazzi software directory''<br />
export PAPARAZZI_SRC=''your paparazzi software directory''<br />
</source><br />
}}<br />
<br />
Verify that your variables are set correctly with the following command:<br />
:<source lang="bash">env | grep PAPARAZZI</source><br />
which should return the following:<br />
<source lang="bash"><br />
PAPARAZZI_HOME=''your paparazzi software directory''<br />
PAPARAZZI_SRC=''your paparazzi software directory''<br />
</source><br />
<br />
<br />
If you wish to manually set the env variables (i.e. when compiling a backup copy of your code in a different folder) execute the following command from the folder you wish to set as your active paparazzi folder:<br />
:<source lang="bash">export PAPARAZZI_HOME=`pwd`;export PAPARAZZI_SRC=`pwd`</source><br />
<br />
== Software Updates ==<br />
'''We manage the software with the git version control system. Learn it! If you are new to it, see the [[Git|Git wiki page]].'''<br />
<br />
Paparazzi is a very rapidly evolving project and as such you might want to update your software regularly. See the [[RepositoryStructure|branching model and release process page]].<br />
<br />
Any new files you created will not be lost/overwritten when updating (like your own airframe file). Nevertheless, as with all things, backups are advised.<br />
If you modified source code, the best way is of course to use the version control system [[Git]] to commit your changes. Otherwise at least use the brute force method and save everything in another directory.<br />
<br />
Update your software with care and caution, and always test the functionality on the ground and in the air as some updates will affect tuning parameters. You might need to update your airframe file as well. The compiler will usually complain if there is a problem, at which point you can look at the [[Airframe_Configuration|Airframe Configuration wiki page]] again, look on the [[Contact#Mailing_List|mailing list]] or some of the most recent airframe files on git to find the proper syntax.<br />
<br />
'''See also the [[Release Upgrades]] page for information on how to update your configuration from one release to the next.'''<br />
<br />
=== Quick'n dirty description ===<br />
<br />
To download and automatically merge any updated source files, run the following command from your Paparazzi directory<br />
git pull<br />
<br />
After any git update or source code modification the code can be recompiled from ''your paparazzi software directory'' with the following command:<br />
<br />
make<br />
<br />
The ''make'' command will only recompile portions of the software where changed have been detected.<br />
If it does not behave as expected you can delete all compiled files and recompile from scratch with the following commands:<br />
<br />
make clean<br />
make<br />
<br />
If you'd like to check that the code compiles all example airframes then you can run the test suite using the command<br />
<br />
make test<br />
<br />
For more details see the [[Builds/Tests|tests page]].<br />
<br />
== Using the Live CD ==<br />
<br />
There is a [[LiveCD]] available, but it dates back to 2008. It is still an easy way to get a first glimpse of Paparazzi however without installing anything.<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24166Installation/Windows102019-02-15T08:33:51Z<p>Iman: </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 />
=Intro=<br />
[[File:Win+papa.jpg|250px|thumb|right]]<br />
<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's '''not so efficient''' to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands(it's like usual [[Installation#Quickstart_for_Ubuntu_users|ubuntu installation command]]):<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
After that you can launch Paparazzi. <br /><br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft using Paparazzi link application.<br />
sw/ground_segment/tmtc/link -d /dev/ttyS15<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Win%2Bpapa.jpg&diff=24165File:Win+papa.jpg2019-02-15T08:20:15Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24164Installation/Windows102019-02-13T15:37:08Z<p>Iman: /* Using Telemetry */</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 />
=Intro=<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's not so efficient to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
<br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands:<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
After that you can launch Paparazzi. <br /><br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft using Paparazzi link application.<br />
sw/ground_segment/tmtc/link -d /dev/ttyS15<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24161Installation/Windows102019-02-06T12:26:39Z<p>Iman: </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 />
=Intro=<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's not so efficient to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
<br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands:<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
After that you can launch Paparazzi. <br /><br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft.<br />
<br />
[[Category:Software]] [[Category:User_Documentation]] [[Category:Installation]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Installation/Windows10&diff=24160Installation/Windows102019-01-27T18:38:40Z<p>Iman: Installing Paparazzi on windows10</p>
<hr />
<div><br />
=Intro=<br />
This page describes the installation of paparazzi on Microsoft Windows10.<br /><br />
<br />
There are many Windows users who like to use paparazzi on this popular OS. Be-aware it's not so efficient to use paparazzi on Windows OS but it could be helpful in some cases.<br /><br />
<br />
Since Microsoft introduced the possibility of installing Ubuntu on windows 10, you can run Paparazzi on it with some little efforts.<br /><br />
=Installing Ubuntu on windows=<br />
First you need to install Ubuntu on Windows 10. (Ensure you are using a '''64-bit''' version of windows 10, since it cannot be run on a 32-bit version.<br />
Go to “''Control Panel-> Programs-> Turn Windows Feature On or Off''”.<br /><br />
<br />
Enable the “''Windows Subsystem for Linux''” option in the list, and then click OK button. <br />
Click “Restart Now” when you are prompted to restart your computer. The feature won’t work until you reboot.<br /><br />
<br />
'''Or''',Instead of the above steps, you can setup your system by executing the following command in the Administrator PowerShell prompt:<br />
Enable-WindowsOptionalFeature –Online –FeatureName Microsoft-Windows-Subsystem-Linux<br />
After that, Ubuntu can be installed from the Microsoft Store:<br />
# Use the Start menu to launch the Microsoft Store application.<br />
# Search for Ubuntu and select the first result, ‘Ubuntu', published by Canonical Group Limited.<br />
# Click on the Install button.<br />
<br />
Ubuntu will be downloaded and installed automatically. Progress will be reported within the Microsoft Store application.<br />
<br />
[[File:Microsoft store.png|400px]]<br />
<br />
<br />
=First launch=<br />
Ubuntu can now be launched in the same way as any other Windows 10 application, such as searching for and selecting Ubuntu in the Start menu.<br /><br />
<br />
When launched for the first time, Ubuntu will inform you that it's ‘Installing' and you'll need to wait a few moments.<br />
<br />
[[File:Installing.png|450px]]<br />
<br />
When complete, you'll be asked for a username and password specific to your Ubuntu installation. These don't need to be the same as your Windows 10 credentials. <br />
<br />
[[File:New user.png|450px]]<br />
<br />
<br />
With this step complete, you'll find yourself at the Ubuntu bash command line.<br /><br />
<br />
After installing Ubuntu, you need to install Paparazzi. The quickest way is to add the Paparazzi repositories, update, and then install the required software.<br /><br />
<br />
You can add the repository and install with these commands:<br />
<br />
sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi<br />
<br />
This step is a little bit slow. Be patient!<br /><br />
<br />
Ubuntu on windows 10 is only command line and there is no GUI. So after finishing this step, you might get an error like this:<br /><br />
<br />
Fatal error: exception Gtk.Error(“GtkMain.init: initialization failed\nml_gtk_init: initialization falied”)<br />
[[File:Gtk error.png|450px]]<br />
<br />
It is because it wants to run the graphical Paparazzi Center. There is a way to have Graphical interface. <br />
<br />
=Graphical Interface=<br />
* '''Step One: Install an X server'''<br />
<br />
There are several different X servers you could install on Windows, [https://sourceforge.net/projects/xming/ Xming] is recommended. Download it and install it on your Windows 10 PC.<br /><br />
<br />
The installation process is simple, You can just accept the default settings. It will then automatically launch and run in your system tray, waiting for you to run graphical programs.<br /><br />
<br />
[[File:Xming windows.png|300px]]<br /><br />
<br />
<br />
<span style="color:#FF0000">'''Hint:'''</span> Every time you want to run a graphical interface from Ubuntu, make sure that Xming is running. <br /><br />
<br />
<br />
* '''Step Two: Set Your Display Environment Variable'''<br />
Now, you’ll need to set the “DISPLAY” environment variable to point at the X server running on your Windows 10 PC. If you don’t do this, graphical applications will simply fail to launch.<br /><br />
<br />
To do this, run the following command in the Bash environment:<br />
export DISPLAY=:0<br />
<br />
This setting only applies to your current Bash session. If you close the window, Bash will forget it. You’ll have to run this command each time you reopen Bash and want to run a graphical application.<br /><br />
<br />
After that you can launch Paparazzi. <br /><br />
<br />
[[File:Paparazzi on windows.png|700px]]<br /><br />
<br />
<br />
Right now you can use Paparazzi for Simulation.<br /><br />
<br />
[[File:Simulation windows.png|700px]]<br /><br />
<br />
<br />
When you build for an aircraft, the processes will end, but it may not automatically remove the indicator. You may need to press “''Stop/Remove All Processes''” button.<br /><br />
<br />
<br />
[[File:Stop windows.png|700px]]<br /><br />
<br />
<br />
=Programming Autopilot=<br />
Right now, to program the autopilot, you should copy the HEX/BIN file manually to your windows OS, You can find your ubuntu home directory files in the following directory:<br /><br />
<br />
C:\Users\NAME\AppData\Local\Packages\DISTRO_FOLDER\LocalState\rootfs<br />
<br />
'''DISTRO_FOLDER''' for Ubuntu is:<br /><br />
<br />
CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc<br />
<br />
Then use a windows program to upload firmware to the autopilot<br /><br />
(For example [https://www.st.com/en/development-tools/stsw-stm32080.html DfuSe] or STM32 [https://www.st.com/en/development-tools/stsw-link004.html ST-LINK Utility] for ST microcontrollers)<br />
<gallery><br />
DfuSE.PNG|DfuSE <br />
ST-Link Utility.png|ST-Link Utility<br />
</gallery><br />
<br />
=Using Telemetry=<br />
After you connect your telemetry to the PC, usually it's recognized under COMx in windows. Find the port number first.<br /><br />
In the Ubuntu, you can access it by "''/dev/ttySx''". For example, COM15 on windows can be accessed on "''/dev/ttyS15''" on Ubuntu.<br /><br />
<br />
First you need to give it the proper permissions. Run this command<br />
sudo chmod 666 /dev/ttyS15<br />
Replacing 15 with the correct number. Now in the Paparazzi center you can use this port to connect to the aircraft.</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Xming_windows.png&diff=24159File:Xming windows.png2019-01-27T17:45:55Z<p>Iman: importing file</p>
<hr />
<div>importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:ST-Link_Utility.png&diff=24158File:ST-Link Utility.png2019-01-27T17:22:24Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:DfuSE.PNG&diff=24157File:DfuSE.PNG2019-01-27T17:20:52Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Stop_windows.png&diff=24156File:Stop windows.png2019-01-27T17:19:48Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Simulation_windows.png&diff=24155File:Simulation windows.png2019-01-27T17:18:21Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Paparazzi_on_windows.png&diff=24154File:Paparazzi on windows.png2019-01-27T17:16:37Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:New_user.png&diff=24153File:New user.png2019-01-27T17:13:59Z<p>Iman: Iman uploaded a new version of File:New user.png</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Gtk_error.png&diff=24152File:Gtk error.png2019-01-27T17:11:58Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:New_user.png&diff=24151File:New user.png2019-01-27T17:09:57Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Installing.png&diff=24150File:Installing.png2019-01-27T17:08:44Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=File:Microsoft_store.png&diff=24149File:Microsoft store.png2019-01-27T17:06:36Z<p>Iman: Importing file</p>
<hr />
<div>Importing file</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Apogee/v1.00&diff=24105Apogee/v1.002018-07-11T16:39:36Z<p>Iman: fix a typo</p>
<hr />
<div>{| 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 />
<div style="float: right; width: 65%"><br />
[[Image:Apogee_v100_top.jpg|260px|Apogee v1.00 bottom side]]<br />
[[Image:Apogee_v100_bottom_1E.jpg|400px|Apogee v1.00 top side]]<br />
</div><br />
__TOC__<br />
<br />
== Overview ==<br />
<br />
* STMicroelectronics STM32F405RGT6 Cortex M4 168MHz processor featuring a Floating point unit (FPU), up to 192k of RAM and 1024k of FLASH.<br />
* 9(6) DOF integrated IMU MPU-9150(6050) based<br />
* 1 x Barometer/altimeter MPL3115A2 (I2C, MPU slave capability)<br />
* 1 x MicroSD card slot, 4 bit SDIO interface (high speed data logging)<br />
* 1 x USB : DFU mode (download) or USB storage (direct access to MicroSD card) <br />
* 6 x Servo PWM outputs<br />
* 1 x R/C receiver PPM frame input<br />
* 1 x R/C receiver serial input with inverter (Futaba S.BUS, Spektrum, etc.)<br />
* 3 x UART<br />
* 2 x [http://en.wikipedia.org/wiki/I2c I<sup>2</sup>C] bus<br />
* 1 x [http://en.wikipedia.org/wiki/Serial_Peripheral_Interface SPI] bus<br />
* RTC with backup capacitor<br />
* SWD(ARM download/debug interface)<br />
* 4 x Auxiliary I/O (General Purpose and/or ADC and/or servo PWM) <br />
* 5v / 1.5A switching power supply (input voltage range 5.5V min &rarr; 17.0v max)<br />
* 3.3v / 1A linear regulator<br />
* 1 x 5v / 500mA power switch<br />
* 4 x status LEDs<br />
* 10.4 grams (0.37 oz)<br />
* 53 x 25mm (2.1" x 0.98"), shares the same external dimensions and mounting points as UmarimLite<br />
* 4 layers PCB design<br />
<br />
== Hardware Revision History ==<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="6"<br />
!''Version #''!!''Release Date''!!''Release Notes''<br />
|-<br />
|v1.00||07/2013||Initial release of Apogee<br />
|}<br />
<br />
<br />
== Detailed Features ==<br />
<br />
=== SDIO (MicroSD card) ===<br />
<br />
* software support available with '''v5.2''' and above<br />
* hi-cap power designed to give enough time to cleanly save buffer and close file(s) when power outage detected<br />
* USB-storage mode when plugging an USB cable after startup<br />
<br />
=== 6 or 9 DOF IMU ===<br />
<br />
Apogee v1.00 PCB offer two [http://www.invensense.com/ Invensense] IMU chip options:<br />
* [http://www.invensense.com/mems/gyro/mpu6050.html MPU-6050] : 6 DOF, 3 axis Accelerometer + 3 axis Gyroscope<br />
* [http://www.invensense.com/mems/gyro/mpu9150.html MPU-9150] : 9 DOF, 3 axis Accelerometer + 3 axis Gyroscope + 3 axis Magnetometer<br />
<br />
=== USB Modes ===<br />
<br />
* usb plugged before autopilot is powered : enter DFU mode to be flashed<br />
* usb plugged after autopilot is powered : stop ap task, enter usb storage mode to made sdcard content easily avalaible, after the host has mounted;copied;dismounted storage;unplugged usb, ap restart<br />
<br />
=== SWD: Serial Wire Debug ===<br />
permits flash and source level debugging via swd part of cheap discovery card, or via more capable, fastest, more expensive probe like black magic probe<br />
<br />
=== R/C Serial ===<br />
<br />
In addition to the classic PPM input, that mostly require receiver modification, one pin of the R/C connector is routed to the MCU UART2 receive input through a '''controlled inverter'''.<br><br />
This new feature allow '''direct connection''' (3 pin) of several brand off-the-shelf receivers '''without hardware modification''' or external encoder board.<br />
* '''RX2_POL(PB13) = 0''' => R/C serial (Rx2) is '''non-inverted''' : allow use standard polarity serial receivers (Spektrum, FlyElectric...)<br />
* '''RX2_POL(PB13) = 1''' => R/C serial (Rx2) is '''inverted''' : allow use of S.BUS protocol compatible receivers (Futaba, FrSky,...)<br />
(see [[RC_Receivers_and_Radios | R/C Receivers and Radios page]] for serial compatible receiver)<br />
<br />
=== Real Time Clock ===<br />
supercap powered rtc, permit to associate correct time and date on sdcard log files, when ap is unpowered between flights<br />
<br />
=== Power Switch ===<br />
<br />
'''5V''' power output pin on '''AUX connector''' ("5Vaux",#2) '''can be switched ON and OFF''' on demand using APSW (MCU GPIO output PB12).<br />
* APSW = 0 => 5V Aux OFF<br />
* APSW = 1 => 5V Aux ON (default)<br />
The internal switch TPS2051B is designed to withstand 500mA continuous current and is '''short-circuit and thermally protected'''.<br><br />
(see [http://www.ti.com/product/tps2051b TPS2051B] datasheet for recommended operation conditions)<br />
<br />
== Pictures ==<br />
<br />
<gallery><br />
Image:Apogee_v100_3D_bottom.png|Apogee v1.00 3D bottom view<br />
Image:Apogee_v100_3D_top.png|Apogee v1.00 3D top view<br />
Image:Apogee_v100_bottom.JPG|Apogee v1.00 bottom view<br />
Image:Apogee_v100_top_1E.JPG|Apogee v1.00 top view<br />
Image:Apogee&UmarimLitePCBs.JPG|Apogee v1.00 and Umarim-Lite<br>footprint comparison<br />
</gallery><br />
<br />
== Pinout ==<br />
''Pins Name and Type are specified with respect to the Autopilot Board''<br />
<br />
[[Image:Apogee_v100_pinout.png]]<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''SRV0/1/2/3/4/5'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5V||PWR||5V Rail from autopilot<br />
|-<br />
|3||SRVx||OUT||Servo signal (PWM)<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''R/C'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5v||PWR||5V Rail from autopilot<br />
|-<br />
|3||style="background:white; color:black"|PPM in||IN||PPM Stream from R/C Receiver (5V tolerant)<br />
|-<br />
|4||style="background:green; color:white"|RX2||IN||UART2 Serial Input (5V Tolerant) through [[#R/C Serial|controlled inverter]]<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''UART1/4/6'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5V||PWR||5V Rail from autopilot<br />
|-<br />
|3||style="background:Red; color:white"|+3.3V||PWR||3.3V Rail from autopilot<br />
|-<br />
|4||style="background:green; color:white"|RX1/4/6||IN||UART1/4/6 Serial Input (3.3V level, UART1 and UART6 are 5V tolerant, UART4 '''IS *NOT* 5V''' tolerant)<br />
|-<br />
|5||style="background:blue; color:white"|TX1/4/6||OUT||UART1/4/6 Serial Output (3.3V level)<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''I2C1/2'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="12%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5V||PWR||5V Rail from autopilot<br />
|-<br />
|3||style="background:red; color:white"|+3.3V||PWR||3.3V Rail from autopilot<br />
|-<br />
|4||style="background:sienna; color:white"|SDA1/2||Open Drain I/O<br>(1.5k pull-up)||I2C1/2 bus Serial DAta<br />
|-<br />
|5||style="background:blue; color:white"|SCL1/2||Open Drain I/O<br>(1.5k pull-up)||I2C1/2 bus Serial CLock<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''USB'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:green; color:white"|USB+||I/O||USB bidirectional D+ line<br />
|-<br />
|3||style="background:white; color:black"|USB-||I/O||USB bidirectional D- line<br />
|-<br />
|4||style="background:orange; color:white"|VBUS||IN||Indicates the presence of USB bus power (5V level), DFU or USB storage Mode selection<br />
|}<br />
''Note: MiniUSB and Molex USB connectors are in parallel, only one can be connected at a time.''<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''SPI1'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5V||PWR||5V Rail from autopilot<br />
|-<br />
|3||style="background:red; color:white"|+3.3V||PWR||3.3V Rail from autopilot<br />
|-<br />
|4||style="background:sienna; color:white"|CS1||OUT||Slave Select. Selects the SPI slave (PB9)<br />
|-<br />
|5||style="background:Grey; color:white"|MOSI1||I/O||SPI1 Master Out Slave In. Data output from master / data input to slave<br />
|-<br />
|6||style="background:Green; color:white"|MISO1||I/O||SPI1 Master In Slave Out. Data input to master / data output from slave<br />
|-<br />
|7||style="background:Yellow; color:black"|SCK1||I/O||SPI1 Serial clock. Clock output from master or input to slave<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''AUX'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Port!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||||common ground<br />
|-<br />
|2||style="background:Orange; color:white"|+5Vaux||PWR||||5V from autopilot through [[#Power Switch | Power Switch]]<br />
|-<br />
|3||style="background:Red; color:white"|+3.3V||PWR||||3.3V Rail from autopilot<br />
|-<br />
|4||AUX1||I/O||PB1||General Purpose I/O #1 or ADC_1 Input or PWM6<br />
|-<br />
|5||AUX2||I/O||PC5||General Purpose I/O #2 or ADC_2 Input<br />
|-<br />
|6||AUX3||I/O||PC4||General Purpose I/O #3 or ADC_3 Input<br />
|-<br />
|7||AUX4||I/O||PB15||General Purpose I/O #4 (also spektrum bind pin)<br />
|}<br />
<br />
<br />
{|border="1" cellspacing="0" style="text-align:center" cellpadding="2%" width="70%"<br />
|+'''SWD'''<br />
!width="7%"|''Pin #''!!width="10%"|''Name''!!width="10%"|''Type''!!''Description''<br />
|-<br />
|1||style="background:black; color:white"|GND||PWR||common ground<br />
|-<br />
|2||style="background:red; color:white"|+3.3V||PWR||3.3V Rail from autopilot<br />
|-<br />
|3||style="background:white; color:black"|RST||IN||MCU Reset<br />
|-<br />
|4||style="background:blue; color:white"|SWCLK||IN||Serial Wire Clock<br />
|-<br />
|5||style="background:sienna; color:white"|SWDIO||I/O||Serial Wire Data Input/Output<br />
|}<br />
<br />
== Schematic ==<br />
[[Image:Apogee_v100_schematic.png|left|900px|Apogee v1.00 Schematic]]<br />
<br style="clear:both"><br />
<br />
<br />
== PCB ==<br />
<br />
=== Gerber & Drill Files ===<br />
<br />
PCB design [http://www.eurocircuits.com/images/stories/ec09/ec-classification-english-1-2010-v2.pdf Eurocircuits 6-C class] compliant:<br />
<br />
'''''[[Media:Apogee_v100_gerber_files.zip|Download Apogee v1.00 gerber & drill files (zip)]]'''''<br />
<br />
RS274X, units = Inches, format = 2:5<br />
<br />
:*Apogee_v100_Silkscreen_TOP.GBR (Top Component Print Layer)<br />
:*Apogee_v100_Soldermask_Top.GBR (Top Solder Mask)<br />
:*Apogee_v100_Paste_Mask_Top.GBR (Top Paste Mask, stencil)<br />
:*Apogee_v100_Signal_Top.GBR (Top Copper Layer)<br />
:*Apogee_v100_Internal_Plane_1.GBR (Internal Copper Layer GND)<br />
:*Apogee_v100_Internal_Plane_2.GBR (Internal Copper Layer +3.3V)<br />
:*Apogee_v100_Signal_Bottom.GBR (Bottom Copper Layer)<br />
:*Apogee_v100_Paste_Mask_Bottom.GBR (Bottom Paste, stencil)<br />
:*Apogee_v100_Soldermask_Bottom.GBR (Bottom Solder Mask)<br />
:*Apogee_v100_Outline.GBR (Board Outline)<br />
:*Apogee_v100_Drill.GBR (NC XY coordinates & Drill tools sizes)<br />
<br />
<br />
== Assembly ==<br />
<br />
===Components Layout===<br />
<br />
<gallery><br />
Image:Apogee_v100_2D_bottom_components.png|Apogee v1.00 bottom components Layout<br />
Image:Apogee_v100_2D_top_components.png|Apogee v1.00 top components Layout<br />
Image:Apogee_v100_bottom_components.png|Apogee v1.00 bottom components detail<br />
Image:Apogee_v100_top_components.png|Apogee v1.00 top components detail<br />
</gallery><br />
<br />
<br />
=== Bill Of Material ===<br />
<br />
'''''[[Media:Apogee_v100_BoM.zip|Download Apogee v1.00 Bill of Material (zipped .xls file)]]'''''<br />
<br><br />
<br><br />
<br />
=== PCB and assembled boards suppliers ===<br />
<br />
Check availability on [[Get_Hardware|Get Hardware]] page<br />
<br />
== Mechanical Dimensions ==<br />
[[Image:Apogee_v100_top_mechanical_dimensions.png|500px|Apogee v1.00 Top Mechanical Dimensions]]<br />
[[Image:Apogee_v100_side_mechanical_dimensions.png|500px|Apogee v1.00 Side Mechanical Dimensions]]<br />
<br />
== Programming ==<br />
Apogee autopilot can reprogrammed in two different ways:<br />
<br />
* using the MCU native (embedded in rom) DFU USB bootloader over the on-board USB header (so pre-loading an "external" bootloader is useless)<br />
** required hardware : usb cable with usb-mini connector<br />
** required software : dfu_util tool (present in ubuntu repository)<br />
* using the SWD (Serial Wire Debug) connector<br />
** required hardware : usb cable with usb-mini connector, molex to 2.54mm pitch pin cable, swd part of a cheap stm32 evaluation board (any discovery board, start @ 8$)<br />
** required software : st_flash and st_util, have to be compiled from source (https://github.com/texane/stlink)<br />
<br />
==On-board Data Logging==<br />
<br />
It is possible to write data on the embedded SD card from the main autopilot program. In order to cope with a real-time constraints of the autopilot, a light RTOS called [http://http://www.chibios.org ChibiOS] is used to split the logging task from the rest of the system. Two modules are necessary to enable the logging system: the driver of the SD card system that also handle the file system (using FATFS) and a dynamic memory allocation system called TLSF.<br />
In order to enable this features for your apogee board, you need to select the correct board type and add the required modules to the firmware section of your airframe file (logging is currently only available for '''fixedwing''' firmware):<br />
<br />
<firmware name="firmware"><br />
...<br />
<target name="ap" board="apogee_1.0_chibios"><br />
...<br />
</target><br />
...<br />
<module name="tlsf"/><br />
<module name="logger" type="sd_chibios"/><br />
</firmware><br />
<br />
This will active the automatic opening of a new log file (30 seconds) after each startup of the autopilot. Then you can freely write ASCII or binary data into this file (see a simple example logging for [https://github.com/paparazzi/paparazzi/blob/master/sw/airborne/modules/meteo/mf_ptu.c meteorological data logging]).<br />
The file is '''automatically''' closed upon battery disconnection, no need to press any button to stop the logging.<br />
<br />
To recover the data on the SD card, just power up the board '''without''' the USB plugged (otherwise it will enter in DFU boot mode), then plus the USB cable to the board and to your computer. This will stop the main autopilot program and will mount the SD card as a regular mass storage with a FAT file system. The log files are placed in a PPRZ folder. Unplugging the USB will reset the autopilot.<br />
<br />
In addition to this, you can also load a [http://docs.paparazziuav.org/latest/module__flight_recorder.html '''flight recorder''' module] (it also needs the '''pprzlog''' module for supporting the specific paparazzi binary log format).<br />
<br />
<firmware><br />
...<br />
<module name="pprzlog"/><br />
<module name="flight_recorder"/><br />
...<br />
</firmware><br />
<br />
with the appropriate telemetry file (conf/telemetry/fixedwing_flight_recorder.xml). This will automatically open a second file where telemetry messages described in the FlightRecorder section of the telemetry file will be logged in [[Data_Logger#Storage_format|binary format]]. The files are store in a separated FR folder on the SD card. The decoding procedure is the same than [[Openlog#Decoding|OpenLog]] and is using the '''sd2log''' tool:<br />
<br />
~/paparazzi/sw/logalizer/sd2log [log_file] [optinal_output_dir]<br />
<br />
This will produce 3 files: a ''.log'' and a ''.data'' files similar to the normal [[Logs|ground station log]] and ''.tlm'' file that is a simple copy of the binary file (but rename with the same base name than the two others).<br />
<br />
==Debugging==<br />
<br />
===Debugging with STM Discovery ST-LINK/V2 embedded debug tool===<br />
<br />
[[Image:SWD_Discovery_to_Apogee.png|Apogee debugging with Discovery dev board]]<br />
<br />
<br />
<br />
===Debugging with [[CricketProbe/v1.00 | CricketProbe]]===<br />
<br />
[[Image:SWD_CricketProbe_to_Apogee.png|800px|Apogee debugging with CricketProbe]]<br />
<br />
===Debugging with Black Magic Probe===<br />
<br />
[[Image:SWD_BlackMagicProbe_to_Apogee.png|700px|Apogee debugging with Black Magic Probe]]<br />
<br />
== Source Files ==<br />
<br />
''[[Media:Apogee_v100_Protel_Design.zip|Apogee v1.00 hardware design (zipped Protel99SE SP6 database file)]]''<br />
<br />
== Source code ==<br />
<br />
Available in latest git master branch<br />
<br />
== Where to Buy ==<br />
<br />
You can purchase Apogee V1.00 from one of the following stores:<br />
* [http://www.drotek.com/shop/en/home/739-apogee-paparazzi-flight-controller.html Drotek]<br />
* [http://www.droneasy.com/index.php/electronics/flight-controllers-2/paparazzi-apogee.html EasyDrone]<br />
* [http://www.goodluckbuy.com/ppz-paparazzi-apogee-uav-stm32f405-flight-control-for-fpv-quadcopter.html GoodluckBuy (xD)]<br />
* [https://www.alibaba.com/product-detail/paparazzi-apogee-UAV-Flight-Control-ppz_60277228722.html Alibaba]<br />
<br />
[[Category:Autopilots]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Advanced_Navigation_Routines&diff=23848Advanced Navigation Routines2017-09-17T06:40:35Z<p>Iman: </p>
<hr />
<div>= Introduction =<br />
<br />
The flight plan standard navigation functions are very flexible. However sometimes one needs to perform a very specific task, and the basic functions are not enough to accomplish a special mission. In that case you can use additional modules functions in the flight plan. By adding a navigation capability to your airframe. The flight plan now has extra functionality that can be used.<br />
<br />
= Available navigation modules =<br />
<br />
== Navigation Routines (Prev.OSAM) ==<br />
<br />
Thanks to Team OSAM's contribution these navigation capabilities have been added.<br />
<br />
To use these navigation routines, you need to change the navigation subsystem type to extra in your airframe file. The navigation extra subsystem includes extra navigation routines like OSAMnav, spiral, poly_survey_advanced, nav_cube, etc.<br />
<br />
<source lang="xml"><br />
<subsystem name="navigation" type="extra"/><br />
</source><br />
<br />
Also include OSAMNav.h in your flight plan:<br />
<br />
<source lang="xml"><br />
#include "subsystems/navigation/OSAMNav.h"<br />
</source><br />
<br />
'''NOTE''' The latest version of PaparazziUAV (v5.10 is the one I am using at the moment) does not have the OSAM navigation contributions as a subsystem but a module. It can be found in the link mentioned below. Not sure from which version the changes apply, but if you cannot find the header file in the subsystems folder, it is most probably in the modules folder.<br />
<br />
sw/airborne/modules/nav<br />
<br />
== Flower ==<br />
[[Image:FlowerScreenShot.png|thumb|Screen shot of flower routine]]<br />
The flower navigation routine flies the aircraft in a flower pattern defined by two waypoints. The center waypoint defines the center of the flower and the altitude the plane flies at. The edge waypoint defines the radius of the flower.<br />
<br />
In our example the waypoints are called "Center" and "Edge":<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<waypoint name="Center" x="-20.0" y="-160.0"/><br />
<waypoint name="Edge" x="-10.0" y="-60.0"/><br />
</source><br />
}}<br />
<br />
Then you can add flower to your flight plan:<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Flower"><br />
<call fun="InitializeFlower(WP_Center,WP_Edge)"/><br />
<call fun="FlowerNav()"/><br />
</block><br />
</source><br />
}}<br />
<br />
Note that in the function InitializeFlower the waypoints need the prefix "WP_".<br />
<br />
== Bungee Takeoff ==<br />
<br />
The bungee takeoff routine helps to automate takeoff by turning the throttle on after the bungee has been release from the hook. The only waypoint you need for this routine is the position of where the bungee is pegged to the ground. Using this waypoint, a line is drawn from the position of the aircraft to the bungee waypoint. This line is called the launch line and will stop updating once the speed of the plane exceeds the MinSpeed. This allows the user to initialize the routine, move the plane and launch it without having to reinitialize. Once the plane is launched, it will follow the launch line until it crosses the throttle line. The throttle line is a line perpendicular to the launch line at a distance d from the bungee waypoint (see the diagram below). When the plane crosses the throttle line and the speed of the aircraft is greater than MinSpeed, the throttle comes on. After the throttle comes on, the plane keeps going straight until it reaches a specified speed and altitude above the bungee waypoint altitude. When it reaches the takeoff speed and takeoff altitude, the next block in the flight plan is executed. The takeoff speed, takeoff altitude, MinSpeed and the distance d from the bungee waypoint are specified in the airframe file. You will need to add those values to your airframe file like this...<br />
<br />
{{Box Code|conf/airframes/myAircraft.xml|<br />
<source lang="xml"><br />
<section name="Takeoff" prefix="Takeoff_"><br />
<define name="Height" value="30" unit="m"/><br />
<define name="Speed" value="15" unit="m/s"/><br />
<define name="Distance" value="3" unit="m"/><br />
<define name="MinSpeed" value="5" unit="m/s"/> <br />
</section><br />
</source><br />
}}<br />
<br />
You can add the bungee takeoff routine to your flight plan like so...<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Takeoff" strip_button="Takeoff (wp CLIMB)" strip_icon="takeoff.png"><br />
<call fun="InitializeBungeeTakeoff(WP_Bungee)"/><br />
<call fun="BungeeTakeoff()"/><br />
</block><br />
</source><br />
}}<br />
<br />
To get this routine to work consistently, you will need to tune the values in the airframe config file. If the prop doesn't automatically turn on when it crosses the throttle line, it could be because the Distance and/or the MinSpeed are too big. If it turns on too early, it could be because the Distance and/or MinSpeed are too small. <br />
<br />
<span style="color:#ff0000"> ***Precaution should be taken while tuning the auto takeoff with electrical plane. If the MinSpeed is too low, the prop could turn on while holding the aircraft!***</span> <br />
<br />
<gallery><br />
Image:BungeeTakeoffDiagram.png|Bungee takeoff diagram<br />
Image:BungeeTakeoffInit.png|After bungee takeoff initialization<br />
Image:BungeeTakeoffThrottleOn.png|After crossing the throttle line<br />
</gallery><br />
<br />
== Polygon Survey ==<br />
=== Explanation ===<br />
With this navigation routine, an aircraft can survey the area of any [http://en.wikipedia.org/wiki/Convex_polygon convex polygon] given an entry point, the number of waypoints which define the polygon, the sweep width and the desired orientation of the sweeps.<br />
<br />
The entry point is the first corner of the polygon and the point at which the aircraft will begin surveying the area. When in the entry state, the aircraft will circle around the entry point in order to smoothly transition into the first sweep. The aircraft will also keep circling around the entry point until it gets to the waypoint altitude. After the first sweep is made, the direction of the next sweep is determined by the distance of the entry point to the edges of the polygon. If there is more area above the first sweep, the aircraft will sweep up. If there is more area below the first sweep, the aircraft will sweep down.<br />
<br />
The aircraft will keep sweeping back and forth until it reaches the end of the polygon. At this point, the aircraft will sweep back up/down the polygon halfway in between the sweeps previously made by the aircraft (just like the rectangle survey function). The aircraft will keep sweeping up and down the polygon unless the user manually exits the block or unless an exception is used ([[#Exceptions|see below]]).<br />
<br />
The orientation of the sweeps can ranges from north south to east west and any where in between (-90 <-> 90 degrees respectively). The side of the polygon the aircraft starts on (ex. north or south) is determined by the side of the polygon the entry point is located.<br />
<br />
<gallery><br />
Image:PolySurveySweepDef.png|Sweep Definition<br />
Image:PolySurveyEntryPic.png|Entry Point<br />
Image:PolySurveySweepBack.png|Sweeping Back<br />
</gallery><br />
<br />
==== Implementation ====<br />
<br />
You can add this navigation routine in your flight plan like so... <br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Poly Survey"><br />
<call fun="InitializePolygonSurvey(WP_S1, NumOfCorners, SweepWidth, Orientation)"/><br />
<call fun="PolygonSurvey()"/><br />
</block><br />
</source><br />
}}<br />
<br />
The parameters are the entry waypoint, the number of waypoints in the polygon, the sweep width (meters), and the desired orientation of the sweeps (degrees). The maximum number of waypoints a polygon can have is currently ten (can be changed in the code). If the number of waypoints in the polygon exceeds the maximum number, the routine will exit and move to the next block in the flight plan. The routine will also exit if the orientation is not between -90 and 90 degrees.<br />
<br />
Here is an example of how you should declare each of the corners of the polygon.<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<waypoint alt="1453.0" name="S1" x="-546.2" y="297.4"/><br />
<waypoint alt="1453.0" name="S2" x="-129.8" y="744.1"/><br />
<waypoint alt="1553.0" name="S3" x="1030.5" y="535.5"/><br />
<waypoint alt="1453.0" name="S4" x="523.0" y="-236.7"/><br />
<waypoint alt="1453.0" name="S5" x="-285.9" y="-255.7"/><br />
</source><br />
}}<br />
<br />
S1 is the entry waypoint and the first corner. The other corners should be in order clockwise or counter clockwise around the polygon. Even though this group of waypoints must be declared together, where the group appears in the list of waypoints doesn't matter.<br />
<br />
If you want the edges of the polygon to show up on the GCS, you can also declare the polygon as a sector. This is not required to run the routine.<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<sectors><br />
<sector name="PolySector"><br />
<corner name="S1"/><br />
<corner name="S2"/><br />
<corner name="S3"/><br />
<corner name="S4"/><br />
<corner name="S5"/><br />
</sector><br />
</sectors><br />
</source><br />
}}<br />
<br />
<gallery caption="A Range of Different Sweep Orientations"><br />
Image:PolySurvey0DegreeEx.png|0 Degrees<br />
Image:PolySurvey30DegreeEx.png|30 Degrees<br />
Image:PolySurvey65DegreeEx.png|65 Degrees<br />
Image:PolySurvey90DegreeEx.png|90 Degrees<br />
</gallery><br />
<br />
<br />
==== Alternative configurations ====<br />
<br />
If you are wanting to start and stop the Poly Survey this is possible by splitting the Poly Survey code above into the initialization routine and the execution routine. You might want to do this if you are searching for something inside the Poly Survey, think you have found it and then realized you haven't, so you want to continue the survey (not restart it). Using the example above, but with the initialisation and execution code separate:<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Init Poly Survey"><br />
<call fun="InitializePolygonSurvey(WP_S1, NumOfCorners, SweepWidth, Orientation)"/><br />
</block><br />
<br />
<block name="Execute Poly Survey"><br />
<call fun="PolygonSurvey()"/><br />
</block><br />
</source><br />
}}<br />
<br />
==== Exceptions ====<br />
There are a couple of built in variables which can be used to exit the routine with an exception. PolySurveySweepNum gives the number of sweeps the aircraft has made and PolySurveySweepBackNum gives the number of times the aircraft has gotten to the bottom of the polygon and swept back. The first example would deroute the aircraft to standby after the aircraft made it's second sweep. The second example would deroute the aircraft to standby before it starts to sweep back up the polygon for the first time.<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Poly Survey"><br />
<exception cond="PolySurveySweepNum >= 2" deroute="Standby"/><br />
<call fun="InitializePolygonSurvey(WP_S1, 5, 200, 45)"/><br />
<call fun="PolygonSurvey()"/><br />
</block><br />
<br />
<block name="Poly Survey"><br />
<exception cond="PolySurveySweepBackNum >= 1" deroute="Standby"/><br />
<call fun="InitializePolygonSurvey(WP_S1, 5, 200, 45)"/><br />
<call fun="PolygonSurvey()"/><br />
</block><br />
</source><br />
}}<br />
<br />
=== Flight Line ===<br />
The Flight Line Routine allows the user to map/follow one dimensional areas of interest like roads and rivers. Given two waypoints, the routine will automatically transition into the flight line to ensure full coverage between the waypoints. In addition, distances before and after the flight line can be used to add extra security to the coverage.<br />
<br />
[[Image:OSAMFlightLineDiagram.png|Flight Line Diagram]]<br />
<br />
To use this navigation routine, you need to include OSAMNav.h in your flight plan and OSAMNav.c to your airframe file. Then add this navigation routine in your flight plan like so... <br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Map River"><br />
<call fun="FlightLine(WP_R1,WP_R2,nav_radius,distance_before,distance_after)"/><br />
</block><br />
</source><br />
}}<br />
<br />
Multiple flight lines can be daisy chained by reusing waypoints as shown below...<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Map River"><br />
<call fun="FlightLine(WP_R1,WP_R2,nav_radius,100,100)"/><br />
<call fun="FlightLine(WP_R2,WP_R3,nav_radius,100,100)"/><br />
<call fun="FlightLine(WP_R3,WP_R4,nav_radius,100,100)"/><br />
<call fun="FlightLine(WP_R5,WP_R6,nav_radius,100,100)"/><br />
<deroute block="Standby"/><br />
</block><br />
</source><br />
}}<br />
<br />
However, the previous block can also be implemented using the FlightLineBlock function. The FlightLineBlock function works the same as the FlightLine function except it automatically steps through the waypoints between the given waypoints. Make sure the waypoints are declared in order or else it won't work!<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block name="Map River"><br />
<call fun="FlightLineBlock(WP_R1,WP_R6,nav_radius,100,100)"/><br />
<deroute block="Standby"/><br />
</block><br />
</source><br />
}}<br />
<br />
<gallery><br />
Image:OSAMFlightLineExample.jpg |Multiple Flight Line Example<br />
</gallery><br />
<br />
== misc ==<br />
<br />
=== Border line ===<br />
<br />
border_line is a nav-routine pretty similar to the nav-line-routine. You can use this nav-routine whenever you want to take care your plane stays on a defined site of a border.<br />
For example you can use this routine to fly along a mountain and always turn away from the mountain ridge wall. Or use it fly along a border road without penetrating the other side of the border.<br />
<br />
Use "extra" navigation subsystem with:<br />
<source lang="xml"><br />
<subsystem name="navigation" type="extra"/><br />
</source><br />
<br />
If you want to use waypoint 1 and 2 you can add border_line in your flight plan like this:<br />
* Include header in "header" section at the beginning<br />
#include "subsystems/navigation/border_line.h"<br />
* Add function in a flight plan block:<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<block group="extra_pattern" name="border line"><br />
<call fun="border_line_init()"/><br />
<call fun="border_line(WP_1, WP_2, -nav_radius)"/><br />
</block><br />
</source><br />
}}<br />
<br />
<br />
<gallery caption="example"><br />
Image:border_line.png|Screen shot of border_line<br />
Image:border_line2.png|Screen shot of border_line2<br />
Image:border_line3.png|Screen shot of border_line3<br />
</gallery><br />
<br />
<br />
=== GLS ===<br />
<br />
GLS or '''G'''lobal Navigation Satellite System (GNSS) '''L'''anding '''S'''ystem adds advanced landing functions to your flightplan<br />
<br />
It add the following capabilities:<br />
<br />
# Fly via defined glide path angle<br />
# In flight changeable landing direction without loosing the glide path angle!<br />
# Smooth intercept, independent of approach angle or wind<br />
# Separation of '''a'''pproach '''f'''ix, '''s'''tart '''d'''ecent and '''t'''op '''o'''f '''d'''ecent<br />
# With fixed target speed (in airspeed mode only)<br />
<br />
====GLS related abbreviations====<br />
<br />
* GLS = '''G'''lobal Navigation Satellite System (GNSS) '''L'''anding '''S'''ystem<br />
* TOD = '''t'''op '''o'''f '''d'''ecent<br />
* AF = '''A'''pproach '''Fix'''<br />
* SD = '''S'''tart '''D'''ecend<br />
* TD = '''T'''ouch '''D'''own point, The spot where the plane should touch the ground for landing<br />
<br />
====Configure====<br />
<br />
What to add to your airframe.<br />
<br />
{{Box Code|conf/flight_plans/myflightplan.xml|<br />
<source lang="xml"><br />
<section name="GLS_APPROACH" prefix="APP_"><br />
<define name="ANGLE" value="5" unit="deg"/><br />
<define name="INTERCEPT_RATE" value="0.624" unit="m/s/s"/><br />
<define name="DISTANCE_AF_SD" value="20" unit="m"/><br />
<define name="TARGET_SPEED" value="14" unit="m/s"/><br />
</section><br />
</source><br />
}}<br />
<br />
<br />
ANGLE - angle from TOD to TD<br />
<br />
DISTANCE_AF_SD - minimum distance (meter) between AF and SD to allow the plane to self stabilize before the intercept starts (e.g. for speed reduction)<br />
<br />
You can set the landing direction by moving the approach fix (AF) in relation to the touch down point (TD).<br />
If you try to set the AF close to the TD you will see how the top of decent (TOD) and start decent (SD) is calculated and if necessary the AF is moved backwards.<br />
(please try in simulation)<br />
<br />
TARGET_SPEED - desired airspeed from AF to TD <br />
<br />
INTERCEPT_RATE -<br />
<br />
e.g. no wind: TARGET_SPEED = 14m/s and ANGLE = 10 --> desired decent rate 2.5 m/s (speed * tan(ANGLE))<br />
<br />
with an INTERCEPT_RATE of 0.624 m/s/s it will take 4s to intercept the final approach path (desired decent rate / intercept_rate)<br />
<br />
the idea is that the INTERCEPT_RATE is unique to each plane and will not change with different approach angles<br />
<br />
to find an appropriate value you can start with a lower (to match 8s for example) and increase it until the intercept will be made from above<br />
<br />
in general: bigger plane - smaller value!<br />
<br />
<br />
how to setup your flightplan.xml:<br />
<br />
<br />
<source lang="xml"><br />
<waypoints><br />
<waypoint height="150" name="AF" x="-260.6" y="-344.6"/><br />
<waypoint name="SD" x="-1600." y="-36."/><br />
<waypoint name="TOD" x="-1600." y="-36."/><br />
<waypoint height="0.0" name="TD" x="-27.2" y="-243.5"/><br />
<waypoint height="266.0" name="_BASELEG" x="-1652.1" y="-113.5"/><br />
</waypoints><br />
<br />
<br />
<br />
<block name="land"><br />
<call fun="gls_init(WP_AF,WP_SD, WP_TOD, WP_TD)"/><br />
<call fun="nav_compute_baseleg(WP_AF, WP_TD, WP__BASELEG, nav_radius)"/><br />
<circle radius="nav_radius" until="NavCircleCount() > 0.5" wp="_BASELEG"/><br />
<circle radius="nav_radius" until="And(NavQdrCloseTo(DegOfRad(baseleg_out_qdr)-(nav_radius/fabs(nav_radius))*10),<br />
10 > fabs(GetPosAlt() - WaypointAlt(WP__BASELEG)))" wp="_BASELEG"/><br />
</block><br />
<br />
<block name="final"><br />
<exception cond="ground_alt + 10 > estimator_z" deroute="flare"/><br />
<call fun="gls(WP_AF,WP_SD, WP_TOD, WP_TD)"/><br />
</block><br />
</source><br />
<br />
<br />
those pictures match the old gls routine! anyway - the new one is not much different... (POS I = SD)<br />
<gallery caption="theory"><br />
Image:gls1.png|side view<br />
Image:gls2.png|from above<br />
Image:gls3.png|screen shot of flight test<br />
</gallery><br />
<br />
== Multi-UAV ==<br />
For TCAS (Traffic Collision Avoidance System) see the [[MultiUAV]] page.<br />
<br />
[[Category:Software]] [[Category:Navigation]] [[Category:User_Documentation]]<br />
<br />
= Create a navigation module =<br />
<br />
Creating a navigation module is not to complex. Have said that, it is not very likely to need to create one module oneself. The already available functions are very flexible and powerful. Before you set of to create and additional navigation module, make sure you understand all current modules and their capabilities. After you investigated current modules and came to the conclusion, there is no way to solve you flightplan mission by creating a new module, go ahead and plz share your work with the community. The more people test the new module, the faster it will reach a stable state.</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=User:Iman/Books/Paparazzi_Main_pages&diff=15698User:Iman/Books/Paparazzi Main pages2013-08-13T15:12:00Z<p>Iman: Created page with "{{saved_book}} == Paparazzi Main Pages == === Collect by RAHA === :Overview :Theory of Operation :Control Loops :ControlTheory :Getting Started :[[Umarim v1.…"</p>
<hr />
<div>{{saved_book}}<br />
<br />
== Paparazzi Main Pages ==<br />
=== Collect by RAHA ===<br />
:[[Overview]]<br />
:[[Theory of Operation]]<br />
:[[Control Loops]]<br />
:[[ControlTheory]]<br />
:[[Getting Started]]<br />
:[[Umarim v1.0]]<br />
:[[Umarim Lite v2]]<br />
:[[Sensors/IMU]]<br />
:[[Modems]]<br />
:[[Modems/xbee]]<br />
:[[Sensors/GPS]]<br />
:[[Tunnel]]<br />
:[[Sensors/IR]]<br />
:[[Other Infrared Sensors]]<br />
:[[ATmega PPM Encoder Board]]<br />
:[[RC Receivers and Radios]]<br />
:[[Paparazzi Center]]<br />
:[[Airframe Configuration]]<br />
:[[Fixedwing Configuration]]<br />
:[[Subsystem/imu]]<br />
:[[ImuCalibration]]<br />
:[[Subsystem/ahrs]]<br />
:[[Subsystem/radio control]]<br />
:[[Subsystem/telemetry]]<br />
:[[Subsystem/gps]]<br />
:[[Modules]]<br />
:[[GCS]]<br />
:[[Simulation]]<br />
:[[FirmwareFlashing]]<br />
:[[Tuning]]<br />
:[[Logs]]<br />
:[[Users]]<br />
:[[Module/infrared]]<br />
<br />
[[Category:Books|Paparazzi Main pages]]</div>Imanhttp://wiki.paparazziuav.org/w/index.php?title=Users&diff=14823Users2013-04-14T04:12:30Z<p>Iman: /* Asia */</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: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: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: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 || 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 />
|- 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 />
{| 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>Iman