Difference between revisions of "S17: Interactive Snake and ladder"
Proj user2 (talk | contribs) (→Project Title) |
Proj user2 (talk | contribs) (→Abstract) |
||
Line 15: | Line 15: | ||
== Abstract == | == Abstract == | ||
− | + | Interactive Snake and Ladder is a simulation of traditional snake and ladder game using SJONE board,LCD and 2 wireless remotes. LCD display is connected to the SJONE board will display the game board. 2 wireless remotes will be interfaced with SJONE board to simulate dice functionality for two users. | |
== Objectives & Introduction == | == Objectives & Introduction == |
Revision as of 19:13, 26 March 2017
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
Interactive Snake and Ladder
Abstract
Interactive Snake and Ladder is a simulation of traditional snake and ladder game using SJONE board,LCD and 2 wireless remotes. LCD display is connected to the SJONE board will display the game board. 2 wireless remotes will be interfaced with SJONE board to simulate dice functionality for two users.
Objectives & Introduction
The project explores the GPIO and UART drivers in LPC1758 platform. CamBot is driven with the help of DC Motors whose PWM Signals are given by LPC1758. Since stepper motor moves in precise repeatable steps, it is best suited for applications requiring precise positioning. Precise increments of movement also allow for excellent control of rotational speed for process automation and robotics. Normal DC motors do not have much torque at low speeds. The sequence of directions for the CamBot is provided by a Bluetooth Application which sends the commands for specific movements.
Team Members & Responsibilities
- Spoorthi Mysore Shivakumar
- Goutam Madhukeshwar Hegde
- Chethan Palangotu Keshava
- Aajna Karki
Schedule
Team Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 03/14/2017 | 03/21/2017 |
|
Completed | 03/21/2017 |
2 | 03/21/2017 | 03/28/2017 |
|
In Progress | |
3 | 03/29/2017 | 04/04/2017 |
|
Not Started | |
4 | 04/05/2017 | 04/11/2017 |
|
Not Started | |
5 | 04/12/2017 | 04/18/2017 |
|
Not Started | |
6 | 04/19/2017 | 04/25/2017 |
|
Not Started | |
7 | 04/26/2017 | 05/02/2017 |
|
Not Started | |
8 | 03/05/2017 | 10/05/2017 |
|
Not Started |
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.
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.