F16: Seismograph
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Project Title
Seismograph
Abstract
In recent years, news of an upcoming large scale earthquake in California has been increasing. Having a seismograph would allow us to directly see any seismic activity. In addition, by adding an LCD screen, we would be able to add plots of the data in a time series manner for any research purposes. Most importantly, the seismograph device would allow to help with search and rescue efforts. When a large scale earthquake is detected, it would allow a signal to be detected via your cellphone in order to ping your GPS location in case of a building collapse.
Objectives & Introduction
Our seismograph would help bring awareness to the realities of earthquakes in California. In addition, it has the possibility to help save lives by aiding in search and rescue efforts when a large earthquake does come.
- Create a working seismograph and store data onto a microSD card
- Write software to display data onto an LCD screen
- Add to software to send signals to cellphone via Bluetooth
- Write a small mobile application to ping GPS location via cellphone when it receives a signal from the seismograph
Team Members & Responsibilities
Both team members will be working on all areas of development with specific focuses as follows:
- Mina Yi
- Focus on software
- Display data on LCD screen with a working joystick
- Mobile application to recognize signal to ping GPS location
- Focus on software
- Andrew Ahwal
- Focus on hardware portion to build a working seismograph
Schedule
Our tentative schedule for the rest of the semester. Responsibility and leadership of the task is indicated by the Assignee. However, it does not mean that they will be expected to complete the tasks alone. Subtasks will be delegated as seen fit.
| Task# | Start Date | End Date | Task | Assignee | Status | Date Completed | Comments |
|---|---|---|---|---|---|---|---|
| 1 | 10/30 | 11/12 | Order components | Both | Complete | 11/6 | |
| 2 | 10/31 | 11/7 | Read datasheets & research | Both | In Progress | ||
| 3 | 11/6 | 12/1 | Interfacing Bluetooth and app creation | Mina | In Progress | ||
| 4 | 11/6 | 11/17 | Build Seismograph circuit | Andrew | In Progress | Expected circuit completion date: 11/14
Expected testing dates: 11/14 - 11/17 | |
| 5 | 11/18 | 11/18 | Progress update | Both | In class demo of our progress | ||
| 6 | 11/18 | 11/20 | Interface seismograph circuit with SJOne board | Andrew | |||
| 7 | 11/21 | 12/7 | Integrate LCD screen with SJOne board & seismograph | Mina | |||
| 8 | 12/7 | 12/20 | Testing and tweaking finalized product | Both |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Part # | Part Name | Purchase Location | Part Specification | Quantity | Cost |
|---|---|---|---|---|---|
| 1 | Piezoelectric Vibration Sensor With Mass | wwww.sparkfun.com | Sen-09197 | 1 | $2.95 |
| 2 | Example | Example | Example | Example | Example |
| 3 | Example | Example | Example | Example | Example |
| 4 | Example | Example | Example | Example | Example |
| 5 | Example | Example | Example | Example | Example |
| 6 | Example | Example | Example | Example | Example |
| 7 | Example | Example | Example | Example | Example |
| 8 | Example | Example | Example | Example | Example |
| 9 | Example | Example | Example | Example | Example |
| 10 | Example | Example | Example | Example | Example |
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
