Difference between revisions of "S16: Simpsons"
Proj user1 (talk | contribs) (→Design & Implementation) |
Proj user1 (talk | contribs) (→Design & Implementation) |
||
| Line 112: | Line 112: | ||
==== Software Design ==== | ==== 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. | + | 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. |
| + | |||
| + | The software design is divided into two parts: | ||
| + | 1) Key Transmitter : A Free-RTOS task is used to detect key press by the user. | ||
| + | 2) Key Receiver : A Free-RTOS task is used to detect signal received on the Cane | ||
==== Implementation ==== | ==== Implementation ==== | ||
Revision as of 20:00, 1 May 2016
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.
Smart Walking Cane for Blind
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
- Gaurao Chaudhari
- Akshay Kanchar
- Key Locator
- Keerthana Alugudurai
- Bhushan Muthiyan
- Arvind Allawadi
- GSM module
Schedule
| Sl. No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 04/05/2016 | 04/12/2016 | 1) Buying of blind stick and other important components 2) Development and Design of Software and Hardware Architecture |
Completed | 04/11/2016 |
| 2 | 04/12/2016 | 04/19/2016 | 1) Interfacing Sensors,Vibrators,Buttons and GSM with SJ One Board 2)Developing basic functionalities for Sensors and Vibrators |
Completed | 04/20/2016 |
| 3 | 04/19/2016 | 04/26/2016 | 1) Interfacing,implementation and integration of GSM module 2) Implementation of Key Locator functionality |
In Progress | |
| 4 | 04/26/2016 | 05/03/2016 | Completing Integration of all modules and testing basic obstacle avoidance and haptic feedback | ||
| 5 | 05/03/2016 | 05/10/2016 | Testing and resolution of Problems | ||
| 6 | 05/10/2016 | 05/17/2016 | Final testing |
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
Key Locator
Hardware Design
A in-built Nordic wireless is used for board to board communication.The transceiver used is nRF24L01+ Single Chip 2.4GHz Transceiver. Figure() shows the connection of the transceiver with the SJ One controller.
<Figure should appear here>
The boards communicate via 2.4 GHz RP-SMA Duck antennas. Figure() shows the connections of these antennas.
<Figure should appear here>
Hardware Interface
The hardware interface is fairly simple. A small 5V battery powers key via its on board 5V pins.The antenna is connected to the SJ One board via its SMA connector.The Nordic wireless has the following connections with the controller. SPI bus is used for communication between them.
< table should appear here>
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.
The software design is divided into two parts: 1) Key Transmitter : A Free-RTOS task is used to detect key press by the user. 2) Key Receiver : A Free-RTOS task is used to detect signal received on the Cane
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.
