Difference between revisions of "Roadmap"

From PaparazziUAV
Jump to: navigation, search
(Blanked the page)
Line 1: Line 1:
This is complete roadmap for paparazzi "go to fly" procedure with proper sequence.
 
  
= Hardware considerations =
 
== Choosing main board ==
 
There are [[Autopilots | a lot of autopilots]] that run paparazzi software. Some of them [[Tiny | have inbuilt GPS]], others have [[Lisa | inbuilt baro sensor and even IMU]] and some are [[Booz | designed to run on copters]] (although nobody says other's can't ;) ). Depending on what you choose and what you want to get, you'll need or need not add external components.
 
 
== Adding proper external components. ==
 
Basically there are three types of components you can add:
 
* [[Sensors]] - used for orientation, proximity, leveling, etc. purposes.
 
* [[GPS]] - sensors that allow accurate positioning. There are lots of such sensors.
 
* [[OMAP]] - which is portable computer used for on-board data processing.
 
* There are lot of [[Other_Hardware | other hardware]] types possible.
 
 
== Choosing interaction interface. ==
 
=== Wired ===
 
* USB - stands for boards that have low level firmware that allow to connect and flash board via USB.
 
* [[JTAG]] - debugging interface that allow direct chip programming (usually for development purposes). Has two channels: JTAG and RS232, which allows to use this interface for ground telemetry messages as well.
 
=== Wireless (RF modem) ===
 
* [[Modems | RF modems]] - communicate with aircraft while it's in flight and to send various data both ways up and down.
 
 
= GCS install =
 
== Preparing OS ==
 
* For ubuntu a [[Installation/Linux#Adding_the_APT_repository | repository should be added]].
 
* Some [[Installation/Linux#Udev_rules | UDEV rules should be created]] if you want to run paparazzi as regular user. If you run as root, nevermind. :)
 
== Installing paparazzi libraries ==
 
* For paparazzi to work correctly, we should [[Installation/Linux#Using_Ubuntu_Software_Center | install required libraries]].
 
== Installing and compiling source code ==
 
* First change to (create?) folder where you want paparazzi to be.
 
 
Keep in mind, that if you want to run as regular user it is better to place source under your home directory (for example: /home/mr_pilot/'''paparazzi'''). I myself use /opt directory, but first install is a bit tricky there because paparazzi libraries are already installed to that folder (/opt/paparazzi). In order to install, you should rename existing folder (/opt/paparazzi->/opt/pp), install source (/opt/paparazzi) and then move contents of renamed folder to new folder (mv /opt/pp/. /opt/paparazzi/.). In other words I'd not recommend to use it.
 
* Now we can [[Installation#Getting_the_Source_Code | get paparazzi source code and make it]].
 
* Don't forget to [[Installation#Environment_Variables | set environment variables]].
 
 
== Assuring proper installation ==
 
* After binary assembly is done, [[Installation#Launching_the_Software | run binary]] to make sure it is working.
 
 
= Airframe configuration =
 
== Planning airframe purpose and capabilities ==
 
There are two global classes of aircraft: Fixed wing and Rotorcraft
 
=== Fixed wing ===
 
* Airplanes - here we have all standard airplanes: aerobatic, slowflying and so on.
 
* Gliders - almost the same thing as airplane but with different flight concept. Unlike airplane, glider mostly relies on motor-less flight, which results in slighter turns and less throttle usage.
 
[[Fixedwing_Configuration | Configuration option sets]] are pretty the same with only difference in variables.
 
=== Rotorcraft ===
 
* Helicopters - mere helicopters that have main and tail rotor.
 
* Tri,Quad,Hexa,Octo-Copters - multirotor platfroms.
 
Unfortunately there are mostly [[Rotorcraft_Configuration | multirotor config file]] examples.
 
 
== Choosing all necessary modules for airframe ==
 
 
== Putting whole config file together ==
 
 
== Testing in SIM mode ==
 
 
== Testing with a real hardware ==
 
 
= Debug =
 

Revision as of 05:27, 10 June 2012