F16: Thunderbolt
Contents
Project Title
Thunderbolt - a self driving RC car
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
| Sr No | Start Date | End Date | Task | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 09/14/2016 | 09/20/2016 | Read previous reports and module distribution | Completed | |
| 2 | 09/21/2016 | 09/27/2016 | Set up git and wiki page | Completed | |
| 3 | 09/28/2016 | 10/04/2016 | Read previous reports and order parts | In Progress | |
| 4 | 10/05/2016 | 10/25/2016 | Work on individual modules | In Progress | |
| 5 | 10/26/2016 | 11/01/2016 | Interface Motor, Sensor, GPS, Bluetooth module with the Master Controller over CAN bus | ||
| 6 | 11/02/2016 | 12/06/2016 | Testing, Modifications and error correction | ||
| 7 | 12/07/2016 | 12/13/2016 | Final testing |
Team members and Responsibilities
- Master Controller
- Abhishek Singh
- Saurabh Ravindra Deshmukh
- Neha Biradar
- Motor Controller
- Krishank Mehta
- Virginia Menezes
- Saurabh Ravindra Deshmukh
- GPS/Compass Module
- Samiksha Ambekar
- Krishank Mehta
- Neha Biradar
- Virginia Menezes
- Sensors
- Arthur Nguyen
- Rajeev Sawant
- Samiksha Ambekar
- Bluetooth
- Abhishek Singh
- Nikhil Namjoshi
- Android Application
- Nikhil Namjoshi
- Saurabh Ravindra Deshmukh
Parts List & Cost
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | RC Car | given by Preet | ||
| 2 | Bluetooth hc 05 | Amazon | 1 | $3.21 |
| 3 | Sonar Sensor | Maxbotix EZ1 MB 1010 | ||
| 4 |
Master Controller
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completed Date |
|---|---|---|---|---|---|
| 1 | 10/11/2016 | 10/18/2016 |
|
In Progress | |
| 2 | 10/18/2016 | 10/25/2016 |
|
||
| 3 | 10/25/2016 | 11/01/2016 |
|
||
| 4 | 11/01/2016 | 11/08/2016 |
|
||
| 5 | 11/08/2016 | 11/15/2016 |
|
||
| 6 | 11/15/2016 | 11/22/2016 |
|
||
| 7 | 11/23/2016 | 11/29/2016 |
|
||
| 8 | 11/30/2016 | 12/06/2016 |
|
||
| 9 | 12/07/2016 | 12/13/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 Controller
Group Members
- Arthur Nguyen
- Rajeev Sawant
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/04/2016 | 10/10/2016 |
|
Complete | |
| 2 | 10/11/2016 | 10/17/2016 |
|
Complete | |
| 3 | 10/18/2016 | 10/24/2016 |
|
||
| 4 | 10/25/2016 | 10/31/2016 |
|
||
| 5 | 11/01/2016 | 11/07/2016 |
|
||
| 6 | 11/08/2016 | 11/14/2016 |
|
||
| 7 | 11/15/2016 | 11/21/2016 |
|
||
| 8 | 11/22/2016 | 11/29/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.
Motor & I/O Controller
Group Members
- Krishank Mehta
- Virginia Menezes
- Saurabh Deshmukh
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completed Date |
|---|---|---|---|---|---|
| 1 | 9/19/2016 | 9/24/2016 | Understanding the motor and PWM concept. | Completed | 9/25/2016 |
| 2 | 10/4/2016 | 10/5/2016 | Testing Servo and DC motor using RC Transmitter and Receiver. | Completed | 10/5/2016 |
| 3 | 10/7/2016 | 10/10/2016 | Testing and interfacing of servo and DC motor with SJOne Board | In Progress | |
| 4 | 10/11/2016 | 10/18/2016 | Design of CAN message ID for motor controller. | ||
| 5 | 10/20/2016 | 10/24/2016 | Design a power circuit on RC car with motors interfaced to SJOne board. | ||
| 6 | 11/01/2016 | 11/08/2016 | Establishing reliable CAN communication for motors with master controller. | ||
| 7 | 11/15/2016 | 11/18/2016 | Interfacing of sensors with motors and testing obstacle avoidance . | ||
| 8 | 11/18/2016 | 11/22/2016 | Integrating it with the master controller, testing and debugging |
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
- Samiksha Ambekar
- Neha Biradar
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completed Date |
|---|---|---|---|---|---|
| 1 | 09/28/2016 | 10/04/2016 | Read previous reports and order GPS , compass module and antenna | Completed | 10/04/2016 |
| 2 | 10/05/2016 | 10/16/2016 | Interface GPS module and compass module to SJOne board. | In Progress | |
| 3 | 10/17/2016 | 10/25/2016 | Parse GPS data and format the data to be transmitted. Test code to get compass reading information. | ||
| 4 | 10/26/2016 | 11/05/2016 | Algorithm development of GPS module for distance calculation. | ||
| 5 | 11/06/2016 | 11/14/2016 | Calibrating the compass module.Integration of GPS and compass module. Interfacing of GPS and compass module to Android | ||
| 6 | 11/15/2016 | 11/22/2016 | Integration with Master through CAN bus and unit testing. | ||
| 7 | 11/22/2016 | 11/29/2016 | Complete System Testing. |
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.
|
GPS Module: Readytosky Ublox NEO-M8N This GPS module uses UART serial communication interface. The refresh rate ranges from 1Hz up to 10Hz with a default baud rate of 9600bps. This module is an updated version to the Ublox NEO-M7N which brings improved accuracy of up to 0.9 meters using its build in antenna. Specifications:
|
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
Group Members
- Nikhil Namjoshi
- Abhishek Singh
- Saurabh Deshmukh
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completed Date |
|---|---|---|---|---|---|
| 1 | 9/27/2016 | 10/4/2016 |
|
Complete | 10/4/2016 |
| 2 | 10/6/2016 | 10/8/2016 |
|
Complete | 10/8/2016 |
| 3 | 9/30/2016 | 10/2/2016 |
|
Complete | 10/2/2016 |
| 4 | 10/2/2016 | 10/6/2016 |
|
Complete | 10/6/2016 |
| 5 | 10/10/2016 | 10/25/2016 |
|
In Progress | |
| 6 | 10/25/2016 | 11/2/2016 |
|
||
| 7 | 11/3/2016 | 11/8/2016 |
|
||
| 8 | 11/9/2016 | 11/23/2016 |
|
||
| 9 | 11/26/2016 | 12/5/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.
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.
