Difference between revisions of "F15: TopGun"
(→Schedule) |
(→Schedule) |
||
Line 97: | Line 97: | ||
| 11/25/2015 | | 11/25/2015 | ||
| Integrating other modules and components to the RC car, development of autonomous driving algorithm and finalize on hardware layout of the car | | Integrating other modules and components to the RC car, development of autonomous driving algorithm and finalize on hardware layout of the car | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
Line 104: | Line 104: | ||
| 12/15/2015 | | 12/15/2015 | ||
| Testing the RC car in real world environments | | Testing the RC car in real world environments | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
|} | |} | ||
+ | |||
+ | '''Motor & I/O Controller Schedule''' | ||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! scope="col"| SI No. | ||
+ | ! scope="col"| Start Date | ||
+ | ! scope="col"| End Date | ||
+ | ! scope="col"| Task | ||
+ | ! scope="col"| Status | ||
+ | ! scope="col"| Actual Completion Date | ||
+ | |- | ||
+ | ! scope="row"| 1 | ||
+ | | 09/20/2015 | ||
+ | | 09/27/2015 | ||
+ | | Researching and ordering the LCD module to be used in the project | ||
+ | | Completed | ||
+ | | 9/27/2015 | ||
+ | |- | ||
+ | ! scope="row"| 2 | ||
+ | | 09/27/2015 | ||
+ | | 10/05/2015 | ||
+ | | | ||
+ | *Studying data sheets(LCD and motor) to get understanding of basic concepts and working of components | ||
+ | *Understanding and proposing driving mechanisms for LCD and motors(DC and servo) | ||
+ | | Completed | ||
+ | | 10/05/2015 | ||
+ | |- | ||
+ | ! scope="row"| 3 | ||
+ | | 10/05/2015 | ||
+ | | 10/12/2015 | ||
+ | | | ||
+ | *Interfacing motors to SJOne board and developing drivers for the same | ||
+ | *Interfacing LCD module to SJOne board and developing drivers to display basic texts and symbols | ||
+ | | Completed | ||
+ | | 10/12/2015 | ||
+ | |- | ||
+ | ! scope="row"| 4 | ||
+ | | 10/12/2015 | ||
+ | | 10/30/2015 | ||
+ | | | ||
+ | *Implementation of basic power on RC car run with motors(DC and servo) interfaced to SJOne board | ||
+ | *Collaborating with other teams to develop basic obstacle avoidance and testing it | ||
+ | | In progress | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 5 | ||
+ | | 10/30/2015 | ||
+ | | 11/12/2015 | ||
+ | | Proposals related to speed controls and sensors for the same and integration of LCD module(with data display) | ||
+ | | Incomplete | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 6 | ||
+ | | 11/12/2015 | ||
+ | | 11/25/2015 | ||
+ | | CAN bus communication from motor and I/O controller to other boards | ||
+ | | Incomplete | ||
+ | | | ||
+ | |- | ||
+ | ! scope="row"| 7 | ||
+ | | 11/25/2015 | ||
+ | | 12/15/2015 | ||
+ | | Debugging issues during trial runs and testing out fault cases | ||
+ | | Incomplete | ||
+ | | | ||
+ | |- | ||
+ | |} | ||
'''Communication bridge & Android Controller Schedule''' | '''Communication bridge & Android Controller Schedule''' | ||
Line 156: | Line 223: | ||
| 11/10/2015 | | 11/10/2015 | ||
| Relay commands and CAN messages from SJOne to android application and test correctness of data | | Relay commands and CAN messages from SJOne to android application and test correctness of data | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
Line 163: | Line 230: | ||
| 11/22/2015 | | 11/22/2015 | ||
| Performing correct routing between source and destination, have a complete working application, basic testing of application and bridge interface | | Performing correct routing between source and destination, have a complete working application, basic testing of application and bridge interface | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
Line 170: | Line 237: | ||
| 12/15/2015 | | 12/15/2015 | ||
| Extensive Testing of application during final phases, modifying code in cooperation with other teams and optimization of android application | | Extensive Testing of application during final phases, modifying code in cooperation with other teams and optimization of android application | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
Line 227: | Line 294: | ||
| 11/25/2015 | | 11/25/2015 | ||
| Preparing sensor values to be sent over CAN bus and testing out the correctness of sensor can messages | | Preparing sensor values to be sent over CAN bus and testing out the correctness of sensor can messages | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- | ||
Line 234: | Line 301: | ||
| 12/15/2015 | | 12/15/2015 | ||
| Testing of code during final phases, modifying code in cooperation with other teams and optimization of code | | Testing of code during final phases, modifying code in cooperation with other teams and optimization of code | ||
− | | | + | | Incomplete |
| | | | ||
|- | |- |
Revision as of 20:02, 23 October 2015
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
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.
Team Members & Responsibilities
Motor & I/0 Controller:
- Anuj Korat
- Dhruv Kakadiya
Communication Bridge & Android Controller:
- Anush Shankar
- Aditya Devaguptapu
Geographical Controller:
- Chitrang Talaviya
- Navjot Singh
Master Controller:
- Divya Dodda
Sensor Controller:
- Hemanth Konanur Nagendra
- Akshay Vijaykumar
Treasurer:
- Anuj Korat
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/15/2015 | 09/27/2015 |
|
Completed | 09/27/2015 |
2 | 09/27/2015 | 10/30/2015 | Following up on RC car and other component procurement through team discussions | Completed | 10/30/2015 |
3 | 10/30/2015 | 10/06/2015 | Hardware design of the car including discussions on component placement, soldering and wiring. | Completed | 10/06/2015 |
4 | 10/06/2015 | 10/17/2015 | CAN message ID's, priorities, data size and format proposals for all the possible CAN messages on the bus | Completed | 10/20/2015 |
5 | 10/20/2015 | 11/05/2015 | Discussions and proposals on basic obstacle avoidance algorithm with sensor integration, hands on and testing | In Progress | |
6 | 11/05/2015 | 11/25/2015 | Integrating other modules and components to the RC car, development of autonomous driving algorithm and finalize on hardware layout of the car | Incomplete | |
7 | 11/25/2015 | 12/15/2015 | Testing the RC car in real world environments | Incomplete |
Motor & I/O Controller Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/20/2015 | 09/27/2015 | Researching and ordering the LCD module to be used in the project | Completed | 9/27/2015 |
2 | 09/27/2015 | 10/05/2015 |
|
Completed | 10/05/2015 |
3 | 10/05/2015 | 10/12/2015 |
|
Completed | 10/12/2015 |
4 | 10/12/2015 | 10/30/2015 |
|
In progress | |
5 | 10/30/2015 | 11/12/2015 | Proposals related to speed controls and sensors for the same and integration of LCD module(with data display) | Incomplete | |
6 | 11/12/2015 | 11/25/2015 | CAN bus communication from motor and I/O controller to other boards | Incomplete | |
7 | 11/25/2015 | 12/15/2015 | Debugging issues during trial runs and testing out fault cases | Incomplete |
Communication bridge & Android Controller Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/20/2015 | 09/30/2015 | Getting familiarized with Android SDK, Java, Bluetooth API and Google Maps API | Completed | 09/30/2015 |
2 | 09/31/2015 | 10/10/2015 |
|
Completed | 10/10/2015 |
3 | 10/10/2015 | 10/22/2015 |
|
Completed | 10/22/2015 |
4 | 10/22/2015 | 10/30/2015 | Interfacing bluetooth module to SJOne board through UART and receive data on SJOne board sent by the bluetooth application | In Progress | |
5 | 10/30/2015 | 11/10/2015 | Relay commands and CAN messages from SJOne to android application and test correctness of data | Incomplete | |
6 | 11/10/2015 | 11/22/2015 | Performing correct routing between source and destination, have a complete working application, basic testing of application and bridge interface | Incomplete | |
7 | 11/22/2015 | 12/15/2015 | Extensive Testing of application during final phases, modifying code in cooperation with other teams and optimization of android application | Incomplete |
Sensor Controller Schedule
SI No. | Start Date | End Date | Task | Status | Actual Completion Date |
---|---|---|---|---|---|
1 | 09/20/2015 | 09/27/2015 | Researching and ordering the sensors to be used in the project | Completed | 9/27/2015 |
2 | 09/27/2015 | 10/03/2015 |
|
Completed | 10/03/2015 |
3 | 10/03/2015 | 10/10/2015 | Interfacing ADC ultrasonic sensor to SJOne board, reading sensor values and filter the readings | Completed | 10/10/2015 |
4 | 10/10/2015 | 10/20/2015 | Understanding inertial measurement unit sensor, interfacing it to SJOne board to get filtered readings | Completed | 10/20/2015 |
5 | 10/20/2015 | 11/05/2015 | Integrating multiple sensors to the SJOne board, testing the sensors and debugging issues | In Progress | |
6 | 11/05/2015 | 11/25/2015 | Preparing sensor values to be sent over CAN bus and testing out the correctness of sensor can messages | Incomplete | |
7 | 11/25/2015 | 12/15/2015 | Testing of code during final phases, modifying code in cooperation with other teams and optimization of code | Incomplete |
Parts List & Cost
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.
CAN Message ID Table
Message ID | Task associated with it | Data bytes | Data values |
---|---|---|---|
0x00 | Kill switch | 1 | Data 0/1 |
0x01 | Reset Message | 1 | Data 0/1 |
0x02 | PowerUp Message Sync | 1 | Data 0/1 |
0x03 | PowerUp Message Sync Ack | 1 | Data values(1-5) |
0x04 | PowerUp Message Ack | 1 | Data values(1-5) |
0x05 | Heartbeat Message | 1 | Data 0/1 |
0x06 | Heartbeat Message Ack | 1 | Data values(1-5) |
0x07 | Distance sensor data message | 6 | Front three sensor, One left, One right and One back (each byte for each sensor) |
0x08 | Light/Battery sensor data message | 2 | one for Light and one for Battery status |
0x09 | Geo data message | 8 | 4 bytes for longitude and 4 bytes for lattitude |
0x0A | Car pause message | 1 | Data 0/1 |
0x0B | Car resume message | 1 | Data 0/1 |
0x0C | Checkpoint message request | 1 | Data 0/1 |
0x0D | Checkpoint data message | 8 | Still working with JSON data in Android application |
0x0E | Driving mode message | 1 | SLOW / NORMAL / FAST / TURBO |
0x0F | Speed message from GPS | 1 | Speed value (in mph) |
0x10 | Free run car message | 1 | Data 0/1 -> Just run car with obstacle avoidance |
0x11 | Error Message | 1 | Different types of error messages |
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.