F15: Fury
Contents
- 1 Grading Criteria
- 2 Project Title
- 3 Abstract
- 4 Schedule
- 5 Parts List & Cost
- 6 Introduction
- 7 Design & Implementation
- 8 Master Controller
- 9 Motor and I/O controller
- 10 Sensor Controller
- 11 Geographical Controller and Compass
- 12 Android & Communication Bridge Controller
- 13 Integration
- 14 Conclusion
- 15 References
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
Abstract
This section should be a couple lines to describe what your project does.
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Sl. No | Start Date | End Date | Task | Actual End date | Problems Encountered |
|---|---|---|---|---|---|
| 1 | 09/20/2015 | 09/27/2015 | Buy RC Car | 09/26/2015 | None |
| 2 | 09/27/2015 | 10/3/2015 | Divide the modules among team members | 10/2/2015 | None |
| 3 | 10/3/2015 | 10/10/2015 | Decide the pins used by each module | ||
| 4 | 10/10/2015 | 10/25/2015 | Get the main board ready which connects all SJOne boards | ||
| 5 | 10/3/2015 | 10/30/2015 | Work on individual modules | ||
| 6 | 10/31/2015 | 11/13/2015 | Sensors, motors and master controller are integrated and tested.
GPS, android and master are integrated and tested |
||
| 7 | 11/14/2015 | 12/10/2015 | Integration, testing and tweaking | ||
| 8 | 12/16/2015 | 12/16/2015 | 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.
Introduction
The Controllers
- Master Controller
- Motor and I/O controller
- Sensor Controller
- Geographical Controller and Compass
- Android & Communication Bridge Controller
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.
Master Controller
Group Members
Schedule
| Sl.No | Start Date | End Date | Task | Status | Actual Completion date | Problems Encountered |
|---|---|---|---|---|---|---|
| 1 | 9/23/2015 | 10/2/2015 | Task list | Completed/ongoing | 10/1/2015 | problems? |
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.
Motor and I/O controller
Group Members
- Sin Yu Ho
- Nimmi Bhatt
Schedule
| Sl.No | Start Date | End Date | Task | Status | Actual Completion date | Problems Encountered |
|---|---|---|---|---|---|---|
| 1 | 9/27/2015 | 10/4/2015 | Decide and purchase rpm sensor and LCD screen module | Completed | 10/1/2015 | |
| 2 | 10/4/2015 | 10/11/2015 | Research and understand servo/throttle motor and issue command from terminal to control it. | In Progress | ||
| 3 | 10/11/2015 | 10/18/2015 | Research and implement on RPM sensor to monitor the speed.
Research and understand how to program LCD module, and provide speed monitoring on LCD module |
|||
| 4 | 10/18/2015 | 10/28/2015 | Design CAN message and implement CAN infrastructure. | |||
| 5 | 10/25/2015 | 10/30/2015 | Design and create graphic interface for monitoring sensor, gps, connection bridge, and master on LCD module | |||
| 6 | 10/31/2015 | 11/13/2015 | Integrate with master, testing and debug | |||
| 7 | 11/14/2015 | 12/10/2015 | Integrate with the whole system, testing and debug |
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
- LCD: : 4D Systems- uLCD-35DT-AR
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.
Sensor Controller
Group Members
Schedule
| Sl.No | Start Date | End Date | Task | Status | Actual Completion date | Problems Encountered |
|---|---|---|---|---|---|---|
| 1 | 9/27/2015 | 10/3/2015 | Order ultra sonic sensors and read data sheets | Completed | 10/2/2015 | N/A |
| 2 | 10/4/2015 | 10/10/2015 | Connect ultra sonic sensor to LPC board & see if LDAR is an option | In Progress | ??/??/???? | N/A |
| 3 | 10/11/2015 | 10/17/2015 | Read data value from sensor and send in CAN bus | Incomplete | ??/??/???? | N/A |
| 4 | 10/18/2015 | 10/24/2015 | Integrate and test proximity sensors | Incomplete | ??/??/???? | N/A |
| 5 | 10/25/2015 | 10/31/2015 | Develop light sensor code | Incomplete | ??/??/???? | N/A |
| 6 | 11/01/2015 | 11/07/2015 | Integrate and test light sensor | Incomplete | ??/??/???? | N/A |
| 7 | 11/08/2015 | 11/21/2015 | Complete hardware testing | Incomplete | ??/??/???? | N/A |
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.
Geographical Controller and Compass
Group Members
- Abhishek Gurudutt
- Tejeshwar Chandra Kamaal
Schedule
| Sl.No | Start Date | End Date | Task | Status | Actual Completion date | Problems Encountered |
|---|---|---|---|---|---|---|
| 1 | 9/23/2015 | 10/2/2015 | Researched and decided upon the GPS module and Compass module. | Completed | 10/1/2015 | None |
| 2 | 10/3/2015 | 10/3/2015 | Ordered GPS module and compass module. | Completed | 10/2/2015 | None |
| 3 | 10/5/2015 | 10/14/2015 | Interface GPS module and
compass module to SJOne board. |
In-progress | - | - |
| 4 | 10/15/2015 | 10/25/2015 | Designing GPS driver
Test code to get compass reading information |
- | - | - |
| 5 | 10/26/2015 | 10/30/2015 | Integration with Android module,
testing and fine tuning. |
- | - | - |
| 6 | 11/1/2015 | 11/13/2015 | Integration with Master through CAN bus. | - | - | - |
| 7 | 11/15/2015 | 12/10/2015 | Testing and calibrating with other modules. | - | - | - |
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.
Android & Communication Bridge Controller
Group Members
- Chinmayi Divakara
- Praveen Prabhakaran
Schedule
| Sl.No | Start Date | Planned End Date | Task | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/30/2015 | 9/30/2015 | Decide and purchase Bluetooth Module | Completed | 9/30/2015 |
| 2 | 9/30/2015 | 10/14/2015 | Develop Basic Android App with Bluetooth Sensor Communication | ||
| 3 | 10/11/2015 | 10/14/2015 | Interface Bluetooth Module with SJSU Dev Board | ||
| 4 | 10/12/2015 | 10/26/2015 | Be able to send bi-directional arbitrary messages between Android App and Dev Board via Bluetooth | ||
| 5 | 10/14/2015 | 11/21/2015 | Interface Bluetooth Module with CAN | ||
| 6 | 10/26/2014 | 11/30/2014 | Integration with GPS module testing and fine tuning. | ||
| 7 | 11/01/2014 | 11/13/2014 | Integration with Master through CAN bus | ||
| 8 | 11/15/2014 | 12/10/2014 | Android App GUI enhancements (Google Maps, Google Drive) |
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.
Integration
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.
