Difference between revisions of "F16: Spartan and Furious"
Proj user10 (talk | contribs) (→Geographical Controller) |
Proj user10 (talk | contribs) (→Sensor and I/O) |
||
| Line 412: | Line 412: | ||
==Sensor and I/O == | ==Sensor and I/O == | ||
| − | '' | + | ==== Group Members ==== |
| − | + | *'''''[http://linkedin.com/in/sreeharshagorantla Harsha Gorantla]<br> ''''' | |
| − | + | *'''''[http://www.linkedin.com/in/shauryajai Shaurya Jain]<br> ''''' | |
| − | + | === Schedule === | |
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Revision as of 21:09, 8 October 2016
Contents
Project Title
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
- Android and Communication Bridge:
- Geographical Controller:
- Master Controller:
- Motor Controller
- Sensor and I/O Controller:
Schedule
| Week# | Date | Task | Actual | Status |
|---|---|---|---|---|
| 1 | 9/17/2016 |
|
|
Complete |
| 2 | 9/24/2016 |
|
|
Complete |
| 3 | 10/01/2016 |
|
|
Complete |
| 4 | 10/08/2016 |
|
|
Complete |
| 5 | 10/15/2016 | |||
| 6 | 10/22/2016 | |||
| 7 | 10/29/2016 | |||
| 8 | 11/05/2016 |
|
||
| 8 | 11/12/2016 | |||
| 8 | 11/19/2016 | |||
| 8 | 11/26/2016 | |||
| 8 | 12/03/2016 | |||
| 8 | 12/10/2016 | |||
| 8 | 12/17/2016 |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
ECUs
Motor Controller
Group Members
Schedule
| Week# | Date | Task | Actual | Status |
|---|---|---|---|---|
| 1 | 10/01/2016 |
|
|
Complete |
| 2 | 10/08/2016 |
|
|
Complete |
| 3 | 10/15/2016 |
|
|
|
| 4 | 10/22/2016 |
|
|
|
| 5 | 10/29/2016 |
|
|
|
| 6 | 11/05/2016 |
|
|
|
| 7 | 11/12/2016 |
|
|
|
| 8 | 11/19/2016 |
|
|
|
| 9 | 11/26/2016 |
|
|
|
| 10 | 12/03/2016 |
|
|
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.
Android and Communication Bridge
Group Members
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.
Geographical Controller
Group Members
Schedule
| Week# | Date | Task | Actual | Status |
|---|---|---|---|---|
| 1 | 10/01/2016 |
|
|
Complete |
| 2 | 10/08/2016 |
|
|
Complete |
| 3 | 10/15/2016 |
|
|
|
| 4 | 10/22/2016 |
|
|
|
| 5 | 10/29/2016 |
|
|
|
| 6 | 11/05/2016 |
|
|
|
| 7 | 11/12/2016 |
|
|
|
| 8 | 11/19/2016 |
|
|
|
| 9 | 11/26/2016 |
|
|
|
| 10 | 12/03/2016 |
|
|
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.
Sensor and I/O
Group Members
Schedule
| Week# | Date | Task | Actual | Status |
|---|---|---|---|---|
| 1 | 10/01/2016 |
|
|
Complete |
| 2 | 10/05/2016 |
|
|
Complete |
| 3 | 10/14/2016 |
|
|
|
| 4 | 10/21/2016 |
|
|
|
| 5 | 10/28/2016 |
|
|
|
| 6 | 11/04/2016 |
|
|
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.
Master 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.
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.
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.
