S17: Smart collision alert system
- 1 Grading Criteria
- 2 Project Title
- 3 Abstract
- 4 Objectives & Introduction
- 5 Schedule
- 6 Parts List & Cost
- 7 Design & Implementation
- 8 Testing & Technical Challenges
- 9 Conclusion
- 10 References
- 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.
Interactive Snake and ladder
Interactive Snake and Ladder game is the simulation of traditional snake and ladder game using SJONE board, LCD display and 2 wireless remotes. In this, LCD display is connected to the SJONE board that will display the snake and ladder grid. Also, 2 wireless remotes are interfaced with the same SJONE board for the 2 users.
Objectives & Introduction
1. Simulation of snake and ladder game. 2. Wireless module to simulate dice functionality. 3. Speech output for events.
1. PCB designing to avoid electrical interference. 2. Algorithm development for snake and ladder game. 3. Achieving high refresh rate on LCD to get real time display effect. 4. Figuring out communication protocol for wireless.
Team Members & Responsibilities
- Abhishek Singh
- Aniket Achyut Bapat
- Bhupendra Naphade
- Jerry John
- Saurabh Ravindra Deshmukh
|Week||Start Date||End Date||Task||Status||Actual Completion Date|
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
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.
Discuss your hardware design here. Show detailed schematics, and the interface here.
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.
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.
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.
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?
Upload a video of your project and post the link here.
Project Source Code
Any acknowledgement that you may wish to provide can be included here.
List any references used in project.
You can list the references you used.