A3 Project Plan

A3

Framework

Arduino

Hardware

• Arduino 328
• Data shield (http://www.adafruit.com/index.php?main_page=product_info&cPath=17_21&products_id=243)
• 3 analog temp sensors (http://www.sparkfun.com/commerce/product_info.php?products_id=9438)
• Analog 3 axis accelerometer (http://www.sparkfun.com/commerce/product_info.php?products_id=9269)
• GPS (http://www.argentdata.com/catalog/product_info.php?products_id=144)
• Analog mux (http://www.sparkfun.com/commerce/product_info.php?products_id=9056)
• Cell phone (http://code.google.com/p/sserial2mobile/wiki/MotorolaC168i)

Sensor Process

All sensors are connected to the mux which is connected to the Arduino. A string is created reading all temp sensors and accelerometer data along with the GPS lat, lon, alt, and time. The string is written to the SD card on the shield every X seconds.

Every Y minutes the position data is sent to the cell phone using AT commands to send a text message for back up tracking. This system could use something like Gumbands to process the incoming text messages and plot them. If that is used we need a webpage to handle the incoming messages and show the data, possibly with Google Maps integration.

Software Tasks

1 Code for writing to the data shield - Ed P

2 Temp Sensor code (averaging?) - Matt S

3 Accelerometer code (averaging?) - Matt B

4 GPS reading code - Chris

5 Code to use the MUX Completed - Wed Oct 20 2010 - Jon (http://github.com/jonspeicher/AnalogMux)

6 Cell phone code (altitude/time dependent?) Completed - Mon Oct 12 2010 - Sayan

7 Gumbands setup and PHP page Completed - Mon Oct 12 2010 - Sayan

8 Google Maps integration for cell data Completed - Mon Oct 12 2010 - Sayan

9 Integrate all code segments together - All, targeted for Mon Oct 25 2010 at the shop

Construction Tasks

1 Build logging sheild - Ed P

2 Connect all sensors to the mux

3 GPS and mux to arduino

4 Prepping the payload for the sensors and arduino

5 Build a radar reflector

6 Prep the payload for video camera

Coding Standards

All tasks should be written as functions.

Pin assignments should be sent in the arguments of the function not hard coded. If possible, a separate "init" function should be used to set the pins once so that it is not necessary to pass the pin values to the "read" function with every call.

Functions should return either a string or numeric value.