Difference between revisions of "F16: Kepler"
Proj user18 (talk | contribs) (Created page with " == Project Title == == Abstract == This section should be a couple lines to describe what your project does. == Objectives & Introduction == Show list of your objectives. ...") |
Proj user18 (talk | contribs) (→Parts List & Cost) |
||
| (16 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
== Objectives & Introduction == | == 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. | 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. | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Schedule == | == Schedule == | ||
| Line 35: | Line 26: | ||
== Parts List & Cost == | == Parts List & Cost == | ||
| − | + | {| class="wikitable" | |
| + | |- | ||
| + | ! scope="col"| Item# | ||
| + | ! scope="col"| Part Desciption | ||
| + | ! scope="col"| Vendor | ||
| + | ! scope="col"| Qty | ||
| + | ! scope="col"| Cost $ | ||
| + | |- | ||
| + | ! scope="row"| 1 | ||
| + | | RC Car | ||
| + | | [http://www.rchobbyexplosion.com/DHK_Hunter_4WD_Short_Course_Truck_with_2_4Ghz_p/dhk8135.htm From Preet] | ||
| + | | 1 | ||
| + | | Free | ||
| + | |- | ||
| + | ! scope="row"| 2 | ||
| + | | SJOne board | ||
| + | | [http://www.socialledge.com/sjsu/index.php?title=Main_Paget Preet] | ||
| + | | 5 | ||
| + | | 80 | ||
| + | |} | ||
| + | |||
| + | == Sensor Controller == | ||
| + | === Team Members & Responsibilities === | ||
| + | *''''' Shruthi Narayan ''''' | ||
| + | *''''' Rimjhim Ghosh ''''' | ||
| + | |||
| + | === 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. | ||
| + | |||
| + | == Motor & I/O Controller == | ||
| + | === Team Members & Responsibilities === | ||
| + | *''''' Chethan Keshava''''' | ||
| + | *''''' Prashant Aithal ''''' | ||
| + | |||
| + | === 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 == | ||
| + | === Team Members & Responsibilities === | ||
| + | *''''' Ankit Gandhi ''''' | ||
| + | *''''' Bharat Khanna ''''' | ||
| + | |||
| + | === 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. | ||
| + | |||
| + | == Communication Bridge Controller == | ||
| + | === Team Members & Responsibilities === | ||
| + | *''''' Bharat Khanna''''' | ||
| + | *''''' Shantanu Vashishtha ''''' | ||
| + | |||
| + | === 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. | ||
| + | |||
| + | == Central Controller == | ||
| + | === Team Members & Responsibilities === | ||
| + | |||
| + | *''''' Aajna Karki ''''' | ||
| + | *''''' Spoorthi Shivakumar ''''' | ||
| − | == Design & Implementation == | + | === 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. | The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation. | ||
| Line 52: | Line 164: | ||
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. | 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 == | + | === 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? | 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. | Make a smooth transition to testing section and described what it took to test your project. | ||
| − | |||
=== My Issue #1 === | === My Issue #1 === | ||
| Line 68: | Line 179: | ||
=== Project Source Code === | === Project Source Code === | ||
| − | * [https:// | + | * [https://gitlab.com/cmpe243_kepler/self_driving_car/tree/master/ Sourceforge Source Code Link] |
== References == | == References == | ||
Latest revision as of 20:13, 26 September 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.
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.
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 10/8 | Task list | Completed? Problems Encountered? |
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost $ |
|---|---|---|---|---|
| 1 | RC Car | From Preet | 1 | Free |
| 2 | SJOne board | Preet | 5 | 80 |
Sensor Controller
Team Members & Responsibilities
- Shruthi Narayan
- Rimjhim Ghosh
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.
Motor & I/O Controller
Team Members & Responsibilities
- Chethan Keshava
- Prashant Aithal
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
Team Members & Responsibilities
- Ankit Gandhi
- Bharat Khanna
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.
Communication Bridge Controller
Team Members & Responsibilities
- Bharat Khanna
- Shantanu Vashishtha
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.
Central Controller
Team Members & Responsibilities
- Aajna Karki
- Spoorthi Shivakumar
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.
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.
