91.450 home
final project writeup template doc
demos Fri Dec 17, 10 am
writeup due Mon Dec 20
contest writeup html
due Mon Nov 22
servo jitter fix html
egg hunt html
due Mon Nov 1
lab 4 html
babblebot html
due Fri Oct 15
lab 3 html
due Mon Oct 4
lab 2 html
due Mon Sep 27
lab 1 html
art of lego design pdf
due Mon Sep 20
resources ikonboard links

91.450 Lab 4: Behavior-Based Control and Speech Output


Reading Assignment


This lab is more open-ended than previous. You have to accomplish all of the following three:
  • Use a sensor that you haven't used before. This might be the optical rangefinder sensor (aka the “ET sensor” because it looks like a pair of big innocent eyes), which is good for doing wall-following; or, the sonar rangefinder, which is good for searching out and moving toward open space.

    Pick one of these two sensors (or another, like the CMUcam) and implement some new robotic behavior on your vehicle.

  • Develop some kind of prioritization/sensor fusion/layered behavior scheme whereby multiple sensors are combined and coordinated with one another.

    Read Section 5.4, “Reactive Control,” in Robotic Explorations for background. It has a particular implementation of a prioritization scheme, which you should feel free to copy or ignore. You might also want to take inspiration from Braitenberg's work or the ideas presented in Arkin's Behavior-Based Robotics.

    But do something along these lines, so that your robot is capable of demonstrating a primary behavior and then a secondary behavior which interrupts the first.

  • Get the Babblebot speech board working so that your robot can talk. Instructions for using it are here. You'll have to build it and then connect it to the Handy Board. Then insert talk commands so that it talks about what state it’s in and what it’s up to.

Invention Database

Update your entry for your robot in the Invention Database. Include:

  • Specifically describe the behavior coordination scheme.
  • Include the code for this. Use the <pre> (preformatted) HTML tag to make the code be presentable.

In your lab write-up, provide the URL to your robot's entry.

Lab Report

Print out your code for the different parts and attach answers to each of the questions raised above. Each team only needs to submit one lab report; however, I strongly encourage you to write the report together so that both members of the team participate in all aspects of the lab.

Include the URL to your Invention Database robot in the lab report.

Your lab report is due at the beginning of class (1:30 pm) on Friday, 15 October 2004.


The lab report should clearly present your work in the three areas that are the topic for this lab (new sensor, behavior-based control, speech output).

It should read like a short paper—in other words, with clearly labeled sections and prose that flows from section to section. You probably want 5 main sections, corresponding to an introduction, the three lab areas, and conclusion.

Sections should contain a combination of descriptive text, relevant code excerpts, photographs, and/or diagrams, as appropriate for explaining your ideas.

  • Quality of work itself, 10 points.
  • Technical clarity (diagrams/figures), 5 points.
  • Writing/grammar correctness, 5 points.
  • Overall presentation, 5 points.
  • InventionDB entry, 5 points.

Last modified: Friday, 08-Oct-2004 12:17:02 EDT by fred_martin@uml.edu