P19043: Essential Tremor Evaluation
/public/

Systems Design

Table of Contents

Team Vision for System-Level Design Phase

During the System Level Design phase, our team broke down the two major sensor systems, the major communications systems, possible power systems, and the possible data manipulation procedures. Through our analysis of these subsystems, team Magna Modus determined that the best way to approach design was by conceptualizing a main model that the team feels best fit engineering requirements feasibly while also compiling a list of possible alternate parts to modify that main design. In addition to hardware data acquisition, we must transmit that data wireless to be displayed in real time on some readable monitor. We began with a morphological chart and considered which possible solutions best fit our needs. We then selected which combinations of these concepts fulfilled each requirement. From there, we further narrowed solutions to come to our model design as well as several alternate possibilities. If such a time comes where our design must be altered due to any restrictions, we will keep the alternate systems in mind.

Functional Decomposition

Functional Decomposition

Transformation Diagram

Transformation Diagram

Benchmarking

Benchmarking

Concept Development

In developing our system level concept, team Magna Modus began with a functional decomposition of our device. Which had 7 steps. Each of these steps correlated with a system, and at the lowest level two systems were needed. We would need to capture two data types, collect that data, transmit data, filter data, correlate data, and display that data in real time and store that data. We then created a morphological chart with 8 sub functions as housing was included in this chart. We developed our solution, and then assessed it for feasibility and requirement fulfillment.

Feasibility: Prototyping, Analysis, Simulation

The system architecture we plan to use is a sleeve housing an Arduino Uno with HC-15 Bluetooth reciever/transmitter, battery system, EMG electrodes, and two IMU motion sensors. These systems are all compatable with one another, and when data is collected from the sensors the bluetooth header on the microcontroller will transmit data to a computer set up to recieve that data. The data will then be filtered and correlated using software, then that software will display the output in real time. The most sensitive design criteria include the limited battery life this system will have in its worst case, and the sheer amount of data that we are to analyze with this device.

We believe that it is feasible to reach each engineering requirement, but feel there must be modifications to the Battery Life and Real Time Display requirements. Operating this device for 8 hours straight on max load would require quite a heavy battery system, and to display each of the 16 strings of data simultaneously would require serious computing power that would break our budget.

Design Parameters

Control Testing will be required to determine many parameters and targets, but the few we know now are:

Morphological Chart and Concept Selection

Morphological Chart

Concept Selection

Our concept development sessions lead to our design of a sleeve powered by a lithium notebook battery with a switching power buffer to feed into an Arduino Uno powering four Myoware Electrodes, and two IMUs. The data collected on these devices will then be communicated via Bluetooth to a PC running our filtering and correlation software displaying in real time on it's monitor.

We decided on this based on the design's:

Concept Selection

Systems Architecture

The data architecture of our system will flow from sensors to the Microcontroller. This will transmit to a computer via Bluetooth. This computer will run our software and display our data while saving to a .csv file.

Data Architecture

The hardware architecture will be separated into two main components. this will consist of the wearable device and the PC with our software.

Designs and Flowcharts

To ensure that our device can be feasibly built, we need to analyze the power consumption of the microcontroller circuit. This can then be compared to battery specifications to determine if our design can run off of each specific battery. Seen in the Microcontroller Circuit Current Analysis block diagram, we analyze the flow of current throughout this subsystem.

Microcontroller Circuit Current Analysis

Test Design

We intend to test our device in compliance with ISO Medical Device standards. Our test will first require several control tests to determine trace profiles when conducted on someone without the essential tremor. We will then use the same conditions to capture data of someone with the essential tremor. We plan to see significant variation from person to person, but there should also be unique patterns to people with and without the essential tremor. This will allow us to set certain testing standards based on the data we collect.

Risk Assessment

In light of the new ideas for our product, several more risks must be considered.

Risk Assessment Table

Design Review Materials

Included are links to our system level design pre-read and presentation.

System Level Design Pre-read

System Level Design Presentation

Plans for next phase

By our next review we would like to be in the simulation and prototyping phase of some subsystems in our device. We would like to know some baseline information when it comes to the specifics of the systems of our device.

Home | Planning & Execution | Imagine RIT

Problem Definition | Systems Design | Preliminary Detailed Design | Detailed Design

Build & Test Prep | Subsystem Build & Test | Integrated System Build & Test | Customer Handoff & Final Project Documentation