CSE 466 Midterm (Lab 6) Project

Introduction

For the Midterm, each of you will build and program a project with a specific design and goal. This project must be individual work, not done with a partner.

You can re-use some previously developed code from the labs, like display and motion sensor code.

Try to work systematically, outlining and planning program flow and user activity in advance. You may need to do some research into methods.

You will be graded on how well your project works, its ease of use, and the clarity of documentation and code comments.

Bonus Points: We will take complexity and originality into account for bonus points. Wonderful failures are better than boring successes, but your project should actually work.

Objective

In this lab, you will build something to demonstrate what you have learned so far in this course.

Available Resources

You should pick one of the following projects

  1. Video Game— using LCD, NeoPixels and motion sensor. Pong? Tilt-table? Etch-a-Sketch? Simon? Battleship? Be creative…Make it simple.
    Option: add audio sound effects through the DAC or PWM using a small speaker or piezo transducer.
    See PlayScale.ino for information on sharing the SPI bus, and use of the SD reader. It also plays a chromatic scale through the A14 DAC output.
    There are several small speakers in the cabinet that work when connected to A14 and ground.

  2. Respiration Monitor— a device that sits on your chest and measures and logs respiration in breaths per minute as you lie on your back.
    Store the data as an ASCII text file on the SD card.
    Uses battery pack, and needs low-power considerations in programming.
    Android example: https://play.google.com/store/apps/details?id=com.sciencewithandroid.crmonitorfree&hl=en

  3. Activity Logger— use the motion sensor to detect activity, (such as walking, jogging, sitting, going up or down stairs) and log it as ASCII to the SD card.
    Think FitBit, or any of the other myriad fitness trackers.
    Uses battery pack, and needs low-power considerations in programming.

  4. Any other project idea of your own devising-- just get my approval in advance.

    Here are some project descriptions from last year.

Deliverables

  1. Short (1-3 pages) project report, with the following:
  2. Fully-annotated and clearly commented sketch, with each code block explained

  3. files with example logging data (if applicable)

  4. Demo of your working hardware sometime on Wednesday Nov. 18 afternoon, in the lab. I'll be there until 2 pm. Late demos at the start of Thursday's lab or email me for a time.

1, 2, and 3 should be turned in to your Catalyst drop box in the Lab 6 drop bin by Wednesday, Nov. 18 at 11:45 pm.