Difference between revisions of "TU Delft - Autonomous Quadrotor"

From PaparazziUAV
Jump to navigation Jump to search
 
(28 intermediate revisions by 5 users not shown)
Line 1: Line 1:
[[File:tudelft_logo.jpg|link=http://tudelft.nl/en/]]
[[File:tudelft_logo.jpg|right|150px|link=http://tudelft.nl/en/]]


== TU Delft - Autonomous Quadrotor ==
== TU Delft - Autonomous Quadrotor ==


On 3 September 2012 two student teams of the Delft University of Technology started with a UAV robotics project, under guidance of dr. ir. M. Wisse and ir. B. D. W. Remes. Each team would have a slightly different initial objective. After completing this objective each team will be free to set its own objectives for the next phase of this project.
On 3 September 2012 two student teams of the Delft University of Technology started with a UAV robotics project, under guidance of [https://phonebook.tudelft.nl/detail.html?uid=ec55934d3f8645c2217f47f46ba795b5|ing. ir. B. D. W. Remes.] The initial objective of both teams is similar, namely getting the AR Drone v2.0 to fly using the Paparazzi Software. However the path taken by each group to reach this objective will be different. In the second part of the project each group is then free to develop a cool or useful application for the AR Drone v2.0, now flying on the paparazzi software.


=== Objectives ===
=== Objectives ===
Our first objective is to enable the Parrot AR Drone v2.0 (from now on referred to as the AR Drone 2) to fly autonomously on the Paparazzi Software.
So our first objective is to enable the Parrot AR Drone v2.0 (from now on referred to as the AR Drone 2) to fly autonomously on the Paparazzi Software. However each group will obtain this goal following a different path:
* Team one will work with the raw navigation data, creating their own software to retrieve and interpret the date. They will need to describe a new board configuration within for Paparazzi to work with.
* '''Team 1''' has the heavy task to make it all work smoothly by using the raw data, creating their own software drivers to retrieve and interpret and steer the data. They will need to describe a new board configuration within for Paparazzi to work with.
* Team two will work with the programming as developed by Parrot. They will need to interpret the data as provided by the program and determine what data to send back.
* '''Team 2''' challenging task is to let the AP work with via on-board SDK as developed by Parrot. They will need to interpret the data as provided by the program and determine what data to send back.


The second objective is that each team has to add a GPS sensor to the AR Drone 2. We will use the US Globalsat BU-353 GPS receiver for this purpose and mount it to the AR Drone 2 using the USB connection on the board.
As mentioned, the second objective or part of the project was to come up with a cool or useful application for the AR Drone 2. '''Team 1''' further developed the AR Drone 2 to include search and rescue applications. '''Team 2''' decided to further develop the AR Drone 2 to be applicable is laser shooting games.  Also each team had to add a GPS sensor to the AR Drone 2. We will use the US Globalsat BU-353 GPS receiver for this purpose and mount it to the AR Drone 2 using the USB connection on the board. More information on each project can be found following the links in the next section.


=== Project Contents ===
=== Teams ===
* [[AR.Drone 2 - Specifications]]
** [[Motor specifcations]]
** [[Sensor specifications]]
** [[GPS specifications]]


=== Teams ===
More information on each project can be found here:
* Team 1: [[TU Delft - Search and Rescue with AR Drone 2]]
 
* Team 2: [[TU Delft - Lasergame with Autonomous AR Drone]]
* '''Team 1''': [[TU Delft - Search and Rescue with AR Drone 2]]
* '''Team 2''': [[TU Delft - Lasergame with Autonomous AR Drone]]


== Development ==
== Newsflash ==
To try and keep you up to date with the most recent developments in this project we have created the [[Talk: TU Delft: AR Drone 2 - News|TU Delft: AR Drone 2 - News]] page. Here we will post breakthroughs, summaries of a page update and small facts that might be nice to know.


=== Installing Paparazzi on AR.Drone 2 ===
To keep you up to date with the most recent developments in this project we have created the [[Talk: TU Delft: AR Drone 2 - News|TU Delft: AR Drone 2 - News]] page. Here we will post breakthroughs, summaries of a page update and small facts that might be nice to know.  
Installing Paparazzi on the AR Drone 2 is taking more effort than we initially expected. To make life easier on both Paparazzi users and developers we are setting up two separate pages. The [[Beginners Page]] is meant for everyone that wants to use Paparazzi as the control system on their UAV. It will guide them through all the choices they will have to make, from selecting the correct hardware modules in Paparazzi to how to use the Paparazzi GCS.


The [[Developers Page]] is meant for anyone that wants help develop Paparazzi into a more all-round platform that can be used on any and all UAVs. It will describe in depth what is needed in order to add a new modules to Paparazzi without ruining the rest of the architecture.
== Installing Paparazzi on AR.Drone 2 ==


''Editors note: Both these pages are not complete yet. We will let you know when they near completion''
To make life easier for everyone that wants to use the AR Drone 2 controlled by Paparazzi, there is a [[AR_Drone_2/getting_started|AR-Drone 2 getting started]] Page. This page will guide you through that process step by step.


* [[Beginners Page]]
* [[Developers Page]]


[[Category: TU Delft - Automonous Quadrotor]]
[[Category: TU Delft - Autonomous Quadrotor]]

Latest revision as of 14:03, 16 June 2013

Tudelft logo.jpg

TU Delft - Autonomous Quadrotor

On 3 September 2012 two student teams of the Delft University of Technology started with a UAV robotics project, under guidance of ir. B. D. W. Remes. The initial objective of both teams is similar, namely getting the AR Drone v2.0 to fly using the Paparazzi Software. However the path taken by each group to reach this objective will be different. In the second part of the project each group is then free to develop a cool or useful application for the AR Drone v2.0, now flying on the paparazzi software.

Objectives

So our first objective is to enable the Parrot AR Drone v2.0 (from now on referred to as the AR Drone 2) to fly autonomously on the Paparazzi Software. However each group will obtain this goal following a different path:

  • Team 1 has the heavy task to make it all work smoothly by using the raw data, creating their own software drivers to retrieve and interpret and steer the data. They will need to describe a new board configuration within for Paparazzi to work with.
  • Team 2 challenging task is to let the AP work with via on-board SDK as developed by Parrot. They will need to interpret the data as provided by the program and determine what data to send back.

As mentioned, the second objective or part of the project was to come up with a cool or useful application for the AR Drone 2. Team 1 further developed the AR Drone 2 to include search and rescue applications. Team 2 decided to further develop the AR Drone 2 to be applicable is laser shooting games. Also each team had to add a GPS sensor to the AR Drone 2. We will use the US Globalsat BU-353 GPS receiver for this purpose and mount it to the AR Drone 2 using the USB connection on the board. More information on each project can be found following the links in the next section.

Teams

More information on each project can be found here:

Newsflash

To keep you up to date with the most recent developments in this project we have created the TU Delft: AR Drone 2 - News page. Here we will post breakthroughs, summaries of a page update and small facts that might be nice to know.

Installing Paparazzi on AR.Drone 2

To make life easier for everyone that wants to use the AR Drone 2 controlled by Paparazzi, there is a AR-Drone 2 getting started Page. This page will guide you through that process step by step.