Difference between revisions of "F16: Thunderbolt"
Proj user14 (talk | contribs) (→Team Schedule) |
Proj user14 (talk | contribs) (→Team Schedule) |
||
| Line 70: | Line 70: | ||
* <font color="green"> Testing and interfacing of servo and DC motor with SJOne Board | * <font color="green"> Testing and interfacing of servo and DC motor with SJOne Board | ||
* <font color="red"> Sensor Data Sheet Review with team | * <font color="red"> Sensor Data Sheet Review with team | ||
| − | |||
| − | |||
| − | |||
| In Progress | | In Progress | ||
| | | | ||
| Line 89: | Line 86: | ||
* <font color="red"> Determine pins and architecture of board for sensor controller | * <font color="red"> Determine pins and architecture of board for sensor controller | ||
* <font color="clouds"> Design the algorithm for navigation and obstacle avoidance in Master controller | * <font color="clouds"> Design the algorithm for navigation and obstacle avoidance in Master controller | ||
| − | |||
| − | |||
* <font color="blue"> Interface the compass module to SJOne board using I2C communication | * <font color="blue"> Interface the compass module to SJOne board using I2C communication | ||
* <font color="carrot"> Bi-directional communication between SJ-ONE Board and Android App | * <font color="carrot"> Bi-directional communication between SJ-ONE Board and Android App | ||
| Line 103: | Line 98: | ||
* <font color="red"> Develop entire board algorithm for all sensors | * <font color="red"> Develop entire board algorithm for all sensors | ||
* <font color="blue"> Develop the algorithms for distance and turn angle calculation | * <font color="blue"> Develop the algorithms for distance and turn angle calculation | ||
| − | * <font color="blue"> | + | * <font color="blue"> Interfacing of GEO controller with Master |
* <font color="carrot"> Interface Android and Bluetooth module with CAN | * <font color="carrot"> Interface Android and Bluetooth module with CAN | ||
| | | | ||
| Line 116: | Line 111: | ||
* <font color="red"> Mount all ultrasonic sensors on car and test it | * <font color="red"> Mount all ultrasonic sensors on car and test it | ||
* <font color="red"> Start implementation of CAN bus by testing sending and receiving of messages | * <font color="red"> Start implementation of CAN bus by testing sending and receiving of messages | ||
| − | * <font color="blue"> | + | * <font color="blue"> Calibrate the compass module and testing |
| − | |||
| | | | ||
| | | | ||
| Line 128: | Line 122: | ||
* <font color="red"> Complete implementation of the sensor controller with the Master controller over CAN bus | * <font color="red"> Complete implementation of the sensor controller with the Master controller over CAN bus | ||
* <font color="red"> Fine-tune algorithms for sensor | * <font color="red"> Fine-tune algorithms for sensor | ||
| − | |||
| − | |||
* <font color="carrot"> Interfacing with GPS module using CAN bus for receiving current location | * <font color="carrot"> Interfacing with GPS module using CAN bus for receiving current location | ||
| + | * <font color="blue"> Interface GPS module to SJOne board using UART communication | ||
| + | * <font color="blue"> Calibrating the GPS and testing | ||
| | | | ||
| | | | ||
| Line 142: | Line 136: | ||
* <font color="red"> Test the implementation for multiple sensors and debugging the issue | * <font color="red"> Test the implementation for multiple sensors and debugging the issue | ||
* <font color="red"> Decide upon additional I/O such as lights | * <font color="red"> Decide upon additional I/O such as lights | ||
| − | * <font color="blue"> | + | * <font color="blue"> Integrating of GPS and compass module |
| − | * <font color="blue"> Interfacing of GEO controller with | + | * <font color="blue"> Interfacing of GEO controller with Android |
* <font color="carrot"> Integrating com_bridge with entire system | * <font color="carrot"> Integrating com_bridge with entire system | ||
| | | | ||
| Line 153: | Line 147: | ||
| | | | ||
* <font color="red"> Optimize the code and testing for stability and report | * <font color="red"> Optimize the code and testing for stability and report | ||
| − | * <font color="blue"> Unit Testing of GEO controller and bug fixes | + | * <font color="blue"> Interfacing of GEO controller with LCD |
| + | * <font color="blue"> Unit Testing of GEO controller and bug fixes and re-calibrate if needed. | ||
* <font color="carrot"> Testing and bug fixes | * <font color="carrot"> Testing and bug fixes | ||
| | | | ||
| Line 162: | Line 157: | ||
| | | | ||
* <font color="red"> Testing and debugging | * <font color="red"> Testing and debugging | ||
| − | |||
* <font color="carrot"> Android App GUI enhancements and bug fixes | * <font color="carrot"> Android App GUI enhancements and bug fixes | ||
| | | | ||
Revision as of 00:37, 1 November 2016
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.
Team Schedule
| Sr No | Start Date | End Date | Task | Status | Problems/Delays if any |
|---|---|---|---|---|---|
| 1 | 09/14/2016 | 09/20/2016 |
|
Completed | |
| 2 | 09/21/2016 | 09/27/2016 |
|
Completed | |
| 3 | 09/28/2016 | 10/04/2016 |
|
Completed | |
| 4 | 10/05/2016 | 10/11/2016 |
|
Completed | |
| 5 | 10/12/2016 | 10/18/2016 |
|
In Progress | |
| 6 | 10/19/2016 | 10/25/2016 |
|
In Progress | |
| 7 | 10/26/2016 | 11/01/2016 |
|
||
| 8 | 11/02/2016 | 11/08/2016 |
|
||
| 9 | 11/09/2016 | 11/15/2016 |
|
||
| 10 | 11/16/2016 | 11/22/2016 |
|
||
| 11 | 11/23/2016 | 11/29/2016 |
|
||
| 12 | 11/30/2016 | 12/06/2016 |
|
||
| 13 | 12/07/2016 | 12/13/2016 |
|
Team members and Responsibilities
- Master Controller
- Abhishek Singh
- Saurabh Ravindra Deshmukh
- Neha Biradar
- Motor Controller
- Krishank Mehta
- Neha Biradar
- Saurabh Ravindra Deshmukh
- GPS/Compass Module
- Samiksha Ambekar
- Virginia Menezes
- Neha Biradar
- 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
- Saurabh Deshmukh
Schedule
| Sr No | Start Date | End Date | Task | Status | Actual Completed Date |
|---|---|---|---|---|---|
| 1 | 9/19/2016 | 9/24/2016 |
|
Completed | 9/25/2016 |
| 2 | 10/4/2016 | 10/5/2016 |
|
Completed | 10/5/2016 |
| 3 | 10/7/2016 | 10/10/2016 |
|
In Progress | |
| 4 | 10/11/2016 | 10/18/2016 |
|
||
| 5 | 10/20/2016 | 10/24/2016 |
|
||
| 6 | 10/26/2016 | 10/28/2016 |
|
||
| 7 | 11/01/2016 | 11/08/2016 |
|
||
| 8 | 11/15/2016 | 11/18/2016 |
|
||
| 9 | 11/18/2016 | 11/22/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.
Geographical Controller
Group Members
- Samiksha Ambekar
- Virginia Menezes
Schedule
| Sr No | Start Date | End Date | Task | Status | Problems/Delay if any |
|---|---|---|---|---|---|
| 1 | 09/14/2016 | 09/20/2016 |
|
Completed | |
| 2 | 09/21/2016 | 09/27/2016 |
|
Completed | |
| 3 | 09/28/2016 | 10/04/2016 |
|
Completed | |
| 4 | 10/05/2016 | 10/11/2016 |
|
Completed | |
| 5 | 10/12/2016 | 10/18/2016 |
|
In Progress | |
| 6 | 10/19/2016 | 10/25/2016 |
|
In Progress | |
| 7 | 10/26/2016 | 11/01/2016 |
|
||
| 8 | 11/02/2016 | 11/08/2016 |
|
||
| 9 | 11/09/2016 | 11/15/2016 |
|
||
| 10 | 11/16/2016 | 11/22/2016 |
|
||
| 11 | 11/23/2016 | 11/29/2016 |
|
||
| 12 | 11/30/2016 | 12/06/2016 |
|
||
| 13 | 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.
|
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
- 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.
