Main Page
Course Admin
Contest Rules
Project Resources
Team Info
Picture Gallery
Contact Info
  You are here: RoboTag Main Page > Course Administration > Basic Demonstration


The basic demonstration is where you show that you have physically implemented the main components of the robot design: the motors, the sensors, the beacon, the tagging device and the radio communication. Not only do these hardware devices need to be interfaced to your main processor, but they must be accompanied by the appropriate software control.

The demo is also an extention of the design review; you must have implemented the main components of your design and accounted for any changes since the design review. This is a very important aspect of the demo and is outlined under the "managerial" section below.

Note that the formal design review is worth 10% of your final grade.

Read the milestone-style short explanation here.

The Basic Demonstration:

The basic demo will consist of your three team members and the project course coordinator. The review will be informal - no slides or suits are required - and very technical. The entire demonstration will take place in the lab; you MUST be prepared to demonstrate the requirements outlined below, and answer detailed technical questions.

Note that for every component of the demo I will want to see code and hear an explanation of how the hardware and software interface. Please take care to make sure that you're presenting technically valid information.

If you have drawings or schematics to present, sketch them on a piece of paper and pass them around. If you design circuits or use drawings that are more complicated, print them out. There will be no portion of your mark associated with the presentation - as long as I can understand what you're talking about.

The following list of guidelines detail the required level of assembly for the basic demo:

  • an umbilical cord (from the PC to the handyboard) is allowed
  • only one robot will be required for the movement demonstration
  • the following should be attached to the chassis (as a minimum):
    • motors, gears and wheels
    • additional battery packs
    • the handyboard and AM receive/transmit boards
  • sensors and tagging can be demonstrated from the 2nd handyboard
  • communications must be demonstrated between both handyboards
  • code must be shown and explained for all portions of the demo

Movement Demo:

Your team will be expected to demonstrate the basics of movement, as follows:

  • move 12" forward (in a straight line)
  • turn 90 degrees to the right
  • move 12" backward (in a straight line)
  • turn 315 degrees to the left
  • move back to the starting point (in a straight line)
Other required tasks are:
  • moving in a circle with approx. 12" diameter
  • high speed forward movement with an abrupt stop
  • 720-degree spin (two full rotations) w/ abrupt stop
Additional (optional) tasks are:
  • spinning the wheels during acceleration (or skidding while stopping)
  • exhibiting some form of motor feedback:
    • moving in perfectly straight lines (without using a stepper motor)
    • wall following or turning around a corner
    • high-speed stop before running into an obstacle
Feel free to suprise me with the movement demonstration. As with all of the components of the demo, I'll want to see a printout and explanation of the code.

Sensors Demo:

You must demonstrate each of the sensors you specified in the design review, as well as all the ones you added due to excessive feedback from myself. You are not required to interface the total number of sensors you plan to have, you don't have to integrate any additional processors, and it isn't a requirement that you implement ISRs.

It is important that you interface the sensors in the manner in which you presented for your design review. ie: If you propose to have all five tag-detect sensors connected to a PIC, then connected to the HandyBoard via one digital port, aim to do that! Connecting all five sensors to one HandyBoard port would be acceptable as well.

As a minimum, you must demonstrate:

  • (minimum) 5x tag detector sensors, which must:
    • make an average 'ambient' light measurement
    • correctly identify a tag & communicate with the handyboard
  • (minimum) 1x beacon detect sensor, which must:
    • correctly detect the common prey beacon (200Hz modulated tone)
    • correctly detect a predator beacon (300Hz+ modulated tone)
    • ignore the predator modulation frequency for THAT robot
Other sensors you might have specified include:
  • bump or bend sensors
  • IR navigation sensors
  • shaft encoders or positional feedback
Additional (optional) tasks are:
  • implementing any additional processors (if req'd)
  • having the sensors interrupt the HB (if req'd)
  • implement the correct number of beacon detectors
  • implementing the sensors on the robot chassis
  • sensor feedback to motors to complete a complex task
Again, feel free to surprise/impress me. I'll want to see a printout and explanation of the code.

Beacon Demo:

You must demonstrate a fully-working beacon that complies with the specifications from the Rules and Regulations page. The requirements of the demo include:

  • 360-degree projection of the modulated IR light
  • detectable from 12'+ in any direction (w/ suggested detectors)
As detailed in the specifications, each robot will be assigned two modulation frequencies (one common frequency for the prey state, one for the predator state) which will be combined with the 56.8kHz carrier frequency. Your beacon must therefore be able to:

  • emit infrared light (approx. 900nm) on a 56.8kHz square-wave carrier
  • modulate the carrier with the prey modulation frequency (200Hz)
  • modulate the carrier with the individual predator modulation frequency
    • this is the specific frequency detailed in the specs

You may use a hardware switch to select the modulation frequency; an optional extention (read: bonus marks) of this demonstration would be to select the modulation frequency from the handyboard.

I'll want to see circuit schematics for any hardware, and a software listing for any software required. Show me the details, baby!

Tagger Demo:

You must demonstrate a fully-functional tagging implement that meets the specifications on the Rules and Regulations page. The requirements of the tagger demo include:

  • one light that MUST conform to the beam-width specifications
  • a demonstration of your moving turret (if req'd)
    • ie: your servo or stepper motor must be working!
  • a demonstration of the correct timing, (500ms on, 3000ms off)
Additional (optional) demonstrations include:
  • looking for a prey beacon (w/ beacon detector) and activing the tagger
    • hitting the handheld beacon
  • tracking the prey beacon as I move it
    • hitting the handheld beacon

Again: show me the schematics and code.

Communications Demo:

You must demonstrate a fully-working radio communications link between your two HandyBoards. This includes:

  • transmitting data at 1200bps between the two HBs
  • relatively asynchronous data transfer
  • presenting a demo of the data transfer
    • ie: pressing start on one HB causes the other to beep

Once again, schematics and code are required.

Management Stuff:

The member of your group responsible for the management will also cover the following:

  • the availability and cost of all the sensors, processors, motors, etc
  • how resources (time, money, effort, etc) have been allocated
  • any changes in the timeline
  • any management problems
This is a follow-up to the design review, so I expect that you will include a list of all the information that has changed since the review.

I don't need schematics or code for the management portion of the dmeo.


Main Page
Course Admin
Contest Rules
Project Resources
Team Info
Picture Gallery
Contact Info