Difference between revisions of "F16: AutoNav"
Proj user16 (talk | contribs) (→Motor & I/O Controller) |
Proj user16 (talk | contribs) (→Geographical Controller) |
||
| Line 374: | Line 374: | ||
| 10/12/2016 | | 10/12/2016 | ||
| Get familiar with data sheets of both modules. | | Get familiar with data sheets of both modules. | ||
| − | | | + | | Completed |
| + | | 10/12/2016 | ||
| | | | ||
|- | |- | ||
| Line 381: | Line 382: | ||
| 10/21/2016 | | 10/21/2016 | ||
| Interface GPS and Compass modules to SJOne board. | | Interface GPS and Compass modules to SJOne board. | ||
| − | | | + | | In Progress |
| | | | ||
|- | |- | ||
Revision as of 03:33, 16 October 2016
Contents
- 1 Project Title
- 2 Abstract
- 3 Objectives & Introduction
- 4 Team Members & Responsibilities
- 5 Schedule
- 6 Parts List & Cost
- 7 Design & Implementation
- 8 Sensor Controller
- 9 Motor & I/O Controller
- 10 Bluetooth and Bridge(Android) Connections
- 11 Geographical Controller
- 12 Master Controller
- 13 Testing & Technical Challenges
- 14 Conclusion
- 15 References
Project Title
- Autonomous 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 Members & Responsibilities
Sensor Controller:
- Vishwanath Balakuntla Ramesh
Motor & I/O Controller:
- Sameer Saran
- Jaswanth Bhimanapalli
Bluetooth (Communication Bridge) & Android Controller:
- Sucharitha
- Karthikeya Rao G V
Geographical Controller:
- Arpita Ramanath
- Veena Manasa Kanakamalla
Master Controller:
- Ajai Krishna Velayutham
- Goutam Madhukeshwar Hegde
Schedule
Team Schedule
| SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 09/13/2016 | 09/27/2016 |
|
Completed | 09/26/2016 |
| 2 | 09/27/2016 | 10/11/2016 |
|
Completed | 10/11/2016 |
| 3 | 10/12/2016 | 10/18/2016 |
Discussions on hardware design of the car including placements of sensor components, controllers etc. |
In Progress | |
| 4 | 10/19/2016 | 10/25/2016 |
Discussion on proposals of developing CAN messages using DBC file. |
Not Started | |
| 5 | 10/26/2016 | 11/08/2016 |
Discussions and proposals on basic obstacle avoidance algorithm with sensor integration, hands on and testing. |
Not Started | |
| 6 | 11/09/2016 | 11/27/2016 |
Integration of other modules and components to the RC car. Navigational algorithm implemented and tested to form a complete autonomous driving algorithm. |
Not Started | |
| 7 | 11/27/2016 | 12/15/2016 |
Testing the RC car in real world environments. |
Not Started |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
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.
Sensor Controller
Team Members:
Vishwanath Balakuntla Ramesh
Sensor Interface schedule
| SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/04/2016 | 10/11/2016 | Reading datasheets of multiple sensors, Understand pros and cons of each sensor. Make an Order. | Completed | 10/10/2016 |
| 2 | 10/12/2016 | 10/18/2016 | Write sample code for sensors and experiment with sensor output(filtering). | ||
| 3 | 10/19/2016 | 10/25/2016 |
|
||
| 4 | 10/26/2016 | 11/7/2016 | Add multiple sensors to the car and work on synchronization between them. | ||
| 5 | 11/8/2016 | 11/22/2016 | Integration testing with Master Controller and other boards. | ||
| 6 | 11/23/2016 | 12/5/2016 | Optimize the code, Finalize the operation (validate correctness) & Documentation |
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.
Motor & I/O Controller
Team Members:
Sameer Saran Jaswanth Bhimanapalli
Motor & I/O Controller Schedule
| S.No. | Start Date | Projected End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/04/2016 | 10/11/2016 |
|
In Progress | |
| 2 | 10/11/2016 | 10/20/2016 |
|
In Progress | |
| 3 | 10/20/2016 | 11/05/2016 |
|
Not yet started | |
| 4 | 11/05/2016 | 11/15/2016 |
|
Not yet started | |
| 5 | 11/15/2016 | 11/25/2016 |
|
Not yet started | |
| 6 | 11/25/2016 | 12/17/2016 |
|
Not yet started |
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.
Bluetooth and Bridge(Android) Connections
Team Members:
Sucharitha Sirigreddy Karthikeya Rao GV
This section includes high level implementation details regarding the Android app connectivity with the Bluetooth module of the RC car. It gives a overview of building the android app, communication between the Bluetooth and Android app on a mobile device, routing mechanisms during the navigation.
Bluetooth and Bridge Connections Schedule
| SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 09/25/2016 | 10/05/2016 | Learning and Getting familiarized with Android SDK, Java, Bluetooth API and Google Maps API | Completed | 10/05/2016 |
| 2 | 10/05/2016 | 10/20/2016 |
|
||
| 3 | 10/20/2016 | 10/31/2016 |
|
||
| 4 | 10/22/2016 | 10/30/2016 | Interfacing Bluetooth module to SJ One board through UART and sending and receiving data between them. | ||
| 5 | 10/30/2016 | 11/10/2016 | Receive commands from SJ One to android application and test if right data is being sent | ||
| 6 | 11/10/2016 | 11/22/2016 | Testing the routing path and the basic testing of the application | ||
| 7 | 11/22/2016 | 12/15/2016 | Integration Testing and Final testing after integration of all the modules on the car. |
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.
Geographical Controller
Geographic Controller Schedule Team Members:
Veena Manasa Kanakamalla Arpita Ramanath
| Sl No. | Start Date | End Date | Task | Status | Actual Completion Date | |
|---|---|---|---|---|---|---|
| 1 | 10/04/2016 | 10/10/2016 | Research and order GPS and Compass module. | Completed | 10/08/2016 | |
| 2 | 10/09/2016 | 10/12/2016 | Get familiar with data sheets of both modules. | Completed | 10/12/2016 | |
| 3 | 10/12/2016 | 10/21/2016 | Interface GPS and Compass modules to SJOne board. | In Progress | ||
| 4 | 10/21/2016 | 10/30/2016 | Calibrate the modules and code to parse raw compass and GPS readings. | |||
| 5 | 10/30/2016 | 11/10/2016 | Establish CAN communication from Geo controller to Master controller. | |||
| 6 | 11/10/2016 | 11/25/2016 | Test functionality and synchronization with Android app. | |||
| 7 | 11/25/2016 | 12/15/2016 | Integrate with the entire system and test, debug and optimize. |
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.
Master Controller
Team Members:
Ajai Krishna Velayutham Goutam Madhukeshwar Hegde
Master Controller Schedule
| SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/10/2016 | 10/20/2016 |
|
Not Started | |
| 2 | 10/21/2016 | 10/31/2016 |
|
Not Started | |
| 3 | 10/26/2016 | 11/05/2016 |
Device and implement a simple obstacle avoidance algorithm on to the Master controller. |
Not Started | |
| 4 | 11/06/2016 | 11/17/2016 |
|
Not Started | |
| 5 | 10/18/2016 | 11/29/2016 |
|
Not Started | |
| 6 | 11/30/2016 | 12/07/2016 |
Integrate navigation and avoidance algorithm. |
Not Started | |
| 7 | 12/08/2016 | 12/15/2016 |
Final testing. |
Not Started |
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.
Include sub-sections that list out a problem and solution, such as:
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.
