20
P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Embed Size (px)

Citation preview

Page 1: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

P13036 Notification Alert

System Design ReviewDate: December 21, 2012

Meeting Location: 17-1545Meeting Time: 2:00 – 3:30 pm

Page 2: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Technical Review Agenda P13036: Notification Alert------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

MembersPatrick Ganson, CE Stephen Moskal, CE Umer Usman, EEElizabeth Phillips, EE Thomas Adcock, ME William Johnson, ME

Meeting Purpose:1. Overview of Project2. Discuss Customer Needs and Specifications3. Concept Development4. Initial design approach5. Schedule for further development.

Materials to be Reviewed:1. Project Description2. Customer Needs and Specifications3. Functional Decomposition4. Initial Casing Drawings/Material & Shaker Design Concept5. Software Flowchart/Microcontroller Concept Selection6. Electrical Block Diagram/Wireless Communication Concept Selection7. Risk Assessment8. Team Schedules9. Questions/Concerns

Page 3: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Meeting TimelineStart Time Topic of Review Require Attendees

2:00 Introduction to Project Dr. Slack, Dr. Behm

2:10 Customer Needs and Specifications Dr. Slack, Dr. Behm

2:20 Functional Decomposition Dr. Slack, Dr. Behm

2:25 Initial Housing Designs Dr. Slack, Dr. Behm

2:30 Concept Development – Housing and Shaker Dr. Slack, Dr. Behm

2:35 Initial Software Development Flow Chart Dr. Slack, Dr. Behm

2:40 Concept Development – Microcontroller Selection

Dr. Slack, Dr. Behm

2:45 Initial Electrical Hardware Diagram Dr. Slack, Dr. Behm

2:50 Concept Development – Wireless Communications

Dr. Slack, Dr. Behm

2:55 Risk Assessment Dr. Slack, Dr. Behm

3:05 Schedule Overview Dr. Slack, Dr. Behm

3:15 Questions, Comments, Concerns Dr. Slack, Dr. Behm

Page 4: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Product DescriptionProject Background:

For deaf and hard of hearing users, to wake up via an alarm would require a bed shaker and/or flashing light source. Many devices in the market now are very limited on additional functionalities. The product to be designed would combine the bed shaker and light source alarm system but also implement the use of a Bluetooth device to expand the ability to receive alert and alarms from a mobile device wirelessly.

Problem Statement:Provide a useful system for notification that will be both flexible and versatile, allowing for better utilization of many smart phone features that rely on notifying the user. Overall the goal on this iteration of the project is to reduce size and improve features and functionality all while maintaining a reasonable product cost.

Objectives/Scope: Make a competitive device for the market. Reduce the size of the final product to allow for travel applications. Improve the Bluetooth technology to expand the range of performance for alert notifications.

Deliverables: Provide a complete product that can be marketed for future use. A user friendly GUI/Mobile Application. Manufacturing Guide for production. Schematics of electrical and mechanical designs. Provide a product that can be used for further development.

Expected Project Benefits:The motivation for this project is to improve the quality of life of deaf and hard of hearing users. This includes providing more independence for the users of the deaf community by using their mobile devices as a means receiving alerts and alarms.

Assumptions & Constraints: Use of Bluetooth technologies in order to interface with user’s mobile devices. Device must be portable; a reasonable weight and size for travel purposes. Finished project with the assumption of being manufactured

Risks/Issues: Due to additional features (LCD/LED screen) and the microcontroller, target size and weight of the product may

not reach specifications. Including extra features can increase the time it takes to build the product by hand/machine. Materials and devices used in the product may not be readily available for mass production. Final cost of the product may exceed initial expectations depending on final concept selection.

Page 5: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Customer NeedsCustomer Need # Importance Description Comments/Status

CN1 2 Lightweight

CN2 2 Small size for travel and easy to carry

CN3 3 Power LED Indicator

CN4 2 Alarm LED Indicator

CN5 2 Bluetooth LED Indicator

CN6 1 Plug in bed shaker and/or light to activate via alarm

CN7 1 Blinking High Intensity LEDs

CN8 3 Variable blinking patterns for LEDs

CN9 3 Control varying shaking intensities

CN10 2 Quality product

CN11 2 Rechargeable batteries.

CN12 1 External power connection/charge batteries

CN13 3 24 hour battery life for travel

CN14 1 Deliver a functional prototype

CN15 2 Keep the product inexpensive (20-40$) Could between $80-$100

CN16 2 Stand alone alarm when PDA is not synced

CN17 2 Quality/attractive shell/external design

CN18 2 Long Lifetime (roughly 10 years)

CN19 2 User-friendly Product

CN20 2 LCD Display to show clock/alarm

CN21 2 Output will deactivate after a reasonable amount of time

CN22 2 Acceptable range Bluetooth device (50 m)

CN23 2 Alarm turn off switch when activated

CN24 2 Switch to disable alarm anytime

Page 6: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Product SpecificationsSpec.

# Importance Source Specification Unit of Measure Marginal Value Ideal Value

S1 2 CN1, CN11, CN17, CN20 Weight Poundsless than

the prototypeless than

1/2 prototype

S2 2CN2, CN11,CN17, CN20 Size in^3

less than the 22.56 in^3

less than11.28 in^3

S3 2 CN3, CN4, CN5, CN20 Indication System requirement n/a n/a

S4 1 CN7Activation System (Light source,

Bed Shaker) requirement n/a n/a

S5 2 CN8 Variable flashing frequencies frequency 2 settings 3 settings

S6 2 CN9 Variable shaking frequencies frequency 2 settings 3 settings

S7 1 CN6, CN12, CN21Compatible recharger plugs for Light

source and Bed Shaker binary n/a n/a

S8 2 CN11, CN13 Robust Rechargeable Batteries hours 8 24

S9 2 CN15 Low CostUnit Manufacturing Cost (US dollars) per 500 units 100 20

S10 1 CN20Alarm Activation

(self-sustaining clock) accuracy± 5 minutes actual time

± 1 minute actual time

S11 2 CN18 Lifetime of Product years 1 years 5 years

S12 3 CN17 Drop Standard (design range) G's 20 25

S13 2 CN1, CN17 Housing Material Selection TBD TBD TBD

S14 3 CN17 Shock Resistance TBD TBD TBD

S15 2 CN22 Distance that Bluetooth works meters 50 100

S16 2 CN10, CN14, CN22 Percent Reliability % Successful trials 90/100 100/100

S17 2 CN16, CN19, CN23, CN24 Alarm self-deactivate/self-reactivate requirement n/a n/a

S18 3 CN19, CN23, CN24 Time it takes to deactivate system seconds 5 2

S19 2 CN17 Device temperature Fahrenheit 72 32 – 140

Page 7: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Functional Decomposition

Page 8: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Mechanical Design

Page 9: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Mechanical Design (contd.)

Page 10: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Material Concept Selection

For the housing material selection ABS plastic was chosen due to ease of manufacture and low cost. While having a lower tensile strength than alternatives such as aluminum, the reduction in strength is not crucial in this application due to the housing not supporting a significant structural load. One disadvantage is the lack of conductivity thermally, meaning further thermal analysis will be required.

Page 11: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Shaker Concept Selection

For the shaker selection the 12V and 5V shakers are both feasible. The choice between them hinges on the electrical system. While the 12V shaker is more powerful and may already be owned by the end user, but the 5V shaker will interface better with the power system. The initial selection is the 12V shaker and depending on the challenges experienced by the team members working with the electrical system may be switched to 5V.

Page 12: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Software Flowchart

S3 = Indication SystemS4 = Activation SystemS5 = Variable Flashing FrequenciesS6 = Variable Shaking FrequenciesS10 = Alarm ActivationS17 = Alarm Self Activate/Deactivate

Page 13: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Microcontroller Concept Selection

The Raspberry Pi was selected because of it's robustness, versatility, and popularity. The rPi uses a ARM11 system on a chip microprocessor that allows for a Linux-based operating system to run. This allows for a vast amount of different programming languages and interfaces that normally are not available in other embedded systems. The rPi opens the door for a more modular software design because of the strong developer's following and ease of coding. Other similar boards have more IO pins and are more powerful than the rPi however, the major downfall is the price is significantly higher. The rPi provides a strong base and potential in a small and inexpensive package at the expense of IO's and having too many unneeded features.

Page 14: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Electrical Block Diagram

S1 = Weight S7 = Compatible Recharger PlugsS2 = Size S8 = Robust Rechargeable BatteriesS3 = Indication System S15 = Distance Bluetooth WorksS4 = Activation System S16 = Percent ReliabilityS5 = Variable Flashing Frequencies S17 = Alarm Self Activate/DeactivateS6 = Variable Shaking Frequencies S19 = Device Temperature

Page 15: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Wireless Communications Concept Selection

Based on current research, Bluetooth seems to be the likely technology to be chosen. The BlueGiga recommendation from the customer was taken into consideration. However, final recommendation can not be made until research is complete.

Page 16: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

Risk Assessment

Page 17: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

ME Schedules

Page 18: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

CE Schedules

Page 19: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

EE Schedules

Page 20: P13036 Notification Alert System Design Review Date: December 21, 2012 Meeting Location: 17-1545 Meeting Time: 2:00 – 3:30 pm

The End!

Questions? Comments?