F16: Kasper
Contents
Project Title
Self Driving Car
Abstract
This project implements a self-driving car.
Objectives & Introduction
Objective of this project is to create a self driving car
Team Members & Responsibilities
We have used five controllers
- Sensor Controller
- Shruthi Narayan
- Rimjhim Ghosh
- Motor & I/O Controller
- Prashant Aithal
- Chethan Keshava
- Geographical Controller
- Ankit Gandhi
- Bharat Khanna
- Central Controller
- Aajna Karki
- Spoorthi Shivakumar
- Communication Bridge Controller
- Bharat Khanna
- Shantanu Vasishtha
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.
Team Schedule
| SI No. | Start Date | End Date | Task | Status | Actual Completion Date | |
|---|---|---|---|---|---|---|
| 1 | 09/20/2016 | 09/27/2016 |
|
Completed | 09/27/2016 | |
| 2 | 09/28/2016 | 10/4/2016 | Reading previous reports and plan accordingly for each task. | Ordering components based on
|
In Progress | |
| 3 | 10/5/2016 | 10/11/2016 | Understanding Hardware design and requirements of each task. | In Progress | ||
| 4 | 10/12/2016 | 10/18/2016 | Designing project architecture based on the protocol for communication, power requirement and the number of special purpose GPIO on the SjOne board. | CAN message ID's, priorities, data size and format proposals for all the possible CAN messages on the bus | Upcoming Task | |
| 5 | 10/19/2016 | 10/25/2016 | Planning methods of testing individual modules based on communication protocols used. | Upcoming Task | ||
| 6 | 10/26/2016 | 11/08/2016
|
Upcoming Task | |||
| 7 | 11/9/2016 | 11/20/2016 | Testing Individual sensor with Master controller using CAN communication | Upcoming Task | ||
| 8 | 11/21/2016 | 12/05/2016 | Integrating & Testing after connecting all sensors to the controller | Upcoming Task |
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost $ |
|---|---|---|---|---|
| 1 | RC Car | From Preet | 1 | 0 |
| 2 | SJOne board | Preet | 5 | 80 |
| 3 | GPS Module | From Preet | 1 | 40 |
| 4 | Triple Axis Magnetometer (Compass) | Sparkfun | 1 | 15 |
| 5 | Bluetooth Module | Sparkfun | 1 | 24.95 |
Sensor Controller
Team Members & Responsibilities
- Shruthi Narayan
- Rimjhim Ghosh
Schedule
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
Schedule
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
Schedule
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
Schedule
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
Schedule
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.
