Author: <Dongbin> Kim Email: akdba0207@gmail.com
Date: Last modified on <05/25/16>
Keywords: <Mobile, Manipulation, MM-UAV, Robot, Arms, Drones>

The photo above depicts MM-UAV Arms Assembly which allows drones to do missions. The big picture problem is that Drone doesn't have a particular arms to carry some stuff or do missions. Solving this partially or completely is important because it will probably lead you to the further research with wider knowledge. This tutorial shows you how to make MM-UAV Arms and takes approximately 40 hours to complete.

This tutorial's motivation is to manipulate drone to do various missions. Readers of this tutorial assumes the reader has the following background and interests:

* Know how to assemble simple robot
* Perhaps also know how to run Arduino/C++
* Perhaps additional background needed may include Servo Motor Control
* This tutorial may also attract readers who interested in advanced UAV research

US-based vendors to obtain material to complete this tutorial include Mcmaster.com
To complete this tutorial, you'll need the following items.

Here is the list as a Google XLS document
Here is the list as a PDF file

This section gives step-by-step instructions along with photos to <fill in the blank>. (If a circuit-building tutorial:) A schematic to construct <fill in the blank> is shown here <add image>. <Add hyperlink to PDF of schematic> is the Acrobat file of the same schematic.

Step 1

<Add photos to make step easier to understand>

Step 2

<Additional steps like Step 3, Step 4, etc>

A link to the source code can be found <provide URL to your code, probably saved in this DASL Wiki>.
The goal of the code is <brief explanation>. It works in the following way

<!- Insert a snippet of your code here. Try to keep to less than 0.5 page long –>

The snippet above serves to <fill in the blank>. It does this by <fill in the blank>.

<!- Insert another snippet of your code here. Try to keep to less than 0.5 page long –>

Next, the code does <fill in the blank>. It does this by <fill in the blank>.

This tutorial's objective was to <fill in the blank>. Complete <choose: construction details, source code and program descriptions> for <fill in the blank>. Once the concepts were conveyed the reader could <fill in the blank>.

Speculating future work derived from this tutorial, includes <fill in the blank>. In the big picture, the problem of <fill in the blank> can be solved with this tutorial.

For questions, clarifications, etc, Email: paul.oh@unlv.edu