Remote Data Acquisition Systemfor Materials Lab

Stephen Cauterucio and Corey Simoncic

SCHOOL OF ENGINEERINGwww.scu.edu

The Problem

Materials lab is cluttered

Need for constant recalibration

Outdated hardware and software

– Slow

– Inconvenient

Our Solution

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

Description P S TI Risk Mitigation Strategy

Lack of Technical Knowledge

.70 .60 .42 -Android Development website -Android programming books-Online Android programming tutorial videos

Lack of Time (Falling behind schedule)

0.5 0.5 0.25 -Cut features-Put more hours into working on the project

Professor Aschheim is too busy to meet with us

0.5 0.4 0.2 -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

1 0.2 0.2 -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.

TimelineFall Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10

Requirement ElicitationRequirement AnalysisProblem Statement

Researching OptionsDesign Document

Winter Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10Prepare for Design Review

Revised Design ReportCoding (create a user interface)

Test operational system

Spring Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10

Prepare for Design Conference

Ensure report/thesis is finished

Coding (Android user interface can interact with device)

Coding (user interface functions and looks nice)

Ensure implementation is complete (consider adding features)

Questions?