TEAM 8: JSM Hammer
Spring 2007



@Badwater @Death Valley @winter2006:
left to right - junwei, mingyang, shihong, and one other friend(stone)

MEMBERS

PROJECT CONCEPT

MOTIVATION

COMPETITIVE ANALYSIS

TECHNICAL SPECIFICATIONS

Hardware:

Software: Protocols:

REQUIREMENTS

ARCHITECTURE

USE CASES (INTERACTION DIAGRAMS)

SYSTEM STATES & TRANSITIONS

State Transition Diagram for the laptop software:


State Transition Diagram for the microcontroller:

RISKS AND MITIGATION STRATEGIES

Risks:

Mitigation:

ERROR HANDLING

IMPLEMENTATION DETAILS

TEST CASES

  1. Startup (Devices start up without errors)
  2. User moves laptop (Nothing should happen)
  3. User leaves laptop (Arming of device)
  4. Thief moves laptop (Alarm rings)
  5. User returns to laptop (Disarming of device)
  6. Shutdown (Devices shutdown properly)

EXPERIMENTAL EVALUATION

LESSONS LEARNED

  1. Subtleties in tinyOS: Deluge library prevented buttons from working
  2. Subtleties in tinyOS: Using genericComm instead of which hpluart to send packets
  3. Subtleties in tinyOS: Using Tosmsg->strength instead of Tosmsg->lqi
  4. RFID voltage incompatibility: Leads to complications when using it with tmote
  5. Accelerometer detects only acceleration, slow movement escapes detection
  6. Tmote to tmote communication strength varies greatly

FUN STUFF

REFERENCES


Back to the top of this page
18-549 course home page