Author: Alex Cater Email: [email protected]
Date: Last modified on 12/19/2016
Keywords: Ollobot Tutorial, IFTTT app, Ollobot Android sample app

The photo above depicts the Ollobot as seen from the front. The big picture problem is to learn how to control the Ollobot using the IFTTT app in conjunction with the Android sample app. Solving this partially or completely is important because it will bring the user a step closer to implementing their own actions and uses on the Ollobot. This tutorial shows you how to set up the Ollobot and the apps mentioned above and takes approximately one hour to complete.

Readers of this tutorial assumes the reader has the following background and interests:

* Know simple programing concepts
* Interests in automation and vehicle control

The rest of this tutorial is presented as follows:

• Parts List and Sources
• Construction
• Programming <!- delete this line if not applicable →
• Final Words

To obtain an Ollobot you will need to directly contact Robotis either by phone, 949-377-0377, or by email at [email protected]. Ollobot is not available to purchase on their site therefor direct contact will be best.
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