Remote Data Acquisition System for Materials Lab Stephen Cauterucio and Corey Simoncic SCHOOL OF ENGINEERING

The Problem  Materials lab is cluttered  Need for constant recalibration  Outdated hardware and software – Slow – Inconvenient

Our Solution

 One device – less wires  Multiple users  Mobility  Cleaner – Sleek user interface – Separate tool for calibration

Requirements  Functional – Transfer sensor data to phone – Phone must display data graphically – Must be able to save sensor data using the phone  Nonfunctional – Device must provide 0-30V of power – Data transfer must be done wirelessly – Only 1 user may have privileges

Use Cases  Anyone – Initial device setup  Professor – Starting data acquisition – Viewing data acquisition – End data acquisition – Saving data

Use Cases  Student – Viewing data acquisition – Saving data  Anyone – Viewing previously saved data plot

Professor Flow Chart

Student Flow Chart

Architectural Design

Technologies Used  Android Software Development Kit (SDK)  Java Development Kit (JDK)  Eclipse with ADT plugin  Bluetooth

Design Rationale  Major Decisions – Android or iPhone? – Bluetooth or Wifi?

Test Plan  Alpha Testing (5 phases) – Android application – Making Bluetooth work – Interacting with physical device – Plotting data – Saving data  Beta Testing – Dr. Aschheim and his students

Project Risks DescriptionPSTIRisk Mitigation Strategy Lack of Technical Knowledge Android Development website -Android programming books -Online Android programming tutorial videos Lack of Time (Falling behind schedule) Cut features -Put more hours into working on the project Professor Aschheim is too busy to meet with us We have set up a standing weekly appointment with him -We can visit during his office hours Android phones come in many shapes and sizes We will need to pick a good average screen size and develop for that. -If there is time, we may develop app for multiple screen sizes.

Timeline

Questions?