S17: Halo
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.
Halo: The Smart Helmet
Abstract
This section should be a couple lines to describe what your project does.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Abhay Prasad
- Revathy
- Unnikrishnan
- Vishalkumar
- Kripanand Jha
Schedule
This section of the report provides the team schedule for the Halo Smart Helmet project, indicating the milestones to be achieved during the course of the project.
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 03/21 | Team Discussion on understanding and finalizing requirements; Identify extra hardware requirements | Completed |
| 2 | 03/28 | Design Hardware and Software modules;Finalize on schematic; Purchase h/w components. | Completed |
| 3 | 04/04 | Interface Accelerometer & Ultrasound sensors; Finalise API layer for individual modules | Completed |
| 4 | 04/11 | Implement modules - start/stop detect algo,distance detect algo,Wireless comm,LED-Display Pane | Completed |
| 5 | 04/18 | Interface system with wireless modules; PCB design | Completed |
| 6 | 04/25 | SW & HW unit testing | Completed |
| 7 | 05/02 | System level Integration & testing | Planned |
| 8 | 05/09 | OnRoad testing /Blackbox testing | Planned |
| 9 | 05/16 | Project Demo | Planned |
Parts List & Cost
Schedule
This section of the report provides the team schedule for the Halo Smart Helmet project, indicating the milestones to be achieved during the course of the project.
| Parts# | Part Name | Quantity | Cost Unit Item |
|---|---|---|---|
| 1 | Bike | 1 | Free |
| 2 | Helmet | 1 | Free |
| 3 | 9 V DC battery | 4 | 3.00 $ |
| 4 | Wireless Antenna | 2 | 2.20 $ |
| 5 | SJOne Board | 2 | 80 $ |
| 6 | PCB fabrication | 10 | 2.8 $ |
Design & Implementation
Printed Circuit Board
Design
We designed custom 28.2 x 48.8 mm board for our project. The goal of the PCB design was to learn the basics of PCB designing using EAGLE software as it is one of the part of embedded systems. We have added two switches along with two leds for showing left right direction while turning the bike. We added connectors on the board to further connect the switch to external board and also connect the power and ground to the external circuit.
EAGLE Software
To design our board we used AUTODESK EAGLE application. We mainly designed schematics and PCB for our board. This board will be interfaced with SJOne board's gpio, power and gnd pin. For the schematic design we used SparkFun library components like switches, leds, connector, resistors. After done with schematics move to board design EAGLE generates board design based on schematics we create. After moving to board design we have to minimize the space used in board and further arrange the components based on your choice. after done with proper design we can either opt for auto-routing or manual routing thing to route the components on the board. While routing use proper values of width and drill size for the route. After done with routing check for any error on the board connections using ERC and DRC tools. We designed dual layer pcb just for the sake of testing. for the commong ground we used ground plane that makes circuit design simple.
EAGLE components used
Algorithm Design
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.
