1 / 20

P13036 Notification Alert

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

emonk
Download Presentation

P13036 Notification Alert

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Technical Review Agenda P13036: Notification Alert ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Members Patrick Ganson, CE Stephen Moskal, CE Umer Usman, EE Elizabeth Phillips, EE Thomas Adcock, ME William Johnson, ME Meeting Purpose: 1. Overview of Project 2. Discuss Customer Needs and Specifications 3. Concept Development 4. Initial design approach 5. Schedule for further development. Materials to be Reviewed: 1. Project Description 2. Customer Needs and Specifications 3. Functional Decomposition 4. Initial Casing Drawings/Material & Shaker Design Concept 5. Software Flowchart/Microcontroller Concept Selection 6. Electrical Block Diagram/Wireless Communication Concept Selection 7. Risk Assessment 8. Team Schedules 9. Questions/Concerns

  3. Meeting Timeline

  4. Product Description Project 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.

  5. Customer Needs

  6. Product Specifications

  7. Functional Decomposition

  8. Mechanical Design

  9. Mechanical Design (contd.)

  10. 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.

  11. 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.

  12. Software Flowchart S3 = Indication System S4 = Activation System S5 = Variable Flashing Frequencies S6 = Variable Shaking Frequencies S10 = Alarm Activation S17 = Alarm Self Activate/Deactivate

  13. 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.

  14. Electrical Block Diagram S1 = Weight S7 = Compatible Recharger Plugs S2 = Size S8 = Robust Rechargeable Batteries S3 = Indication System S15 = Distance Bluetooth Works S4 = Activation System S16 = Percent Reliability S5 = Variable Flashing Frequencies S17 = Alarm Self Activate/Deactivate S6 = Variable Shaking Frequencies S19 = Device Temperature

  15. 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.

  16. Risk Assessment

  17. ME Schedules

  18. CE Schedules

  19. EE Schedules

  20. The End! • Questions? Comments?

More Related