Difference between revisions of "F15: TopGun"
(→Team Members & Responsibilities) |
(→Team Members & Responsibilities) |
||
| Line 29: | Line 29: | ||
| Motor and LCD Controller | | Motor and LCD Controller | ||
| *Dhruv Kakadiya | | *Dhruv Kakadiya | ||
| − | + | | *Anuj Korat | |
|- | |- | ||
! scope="row"|2 | ! scope="row"|2 | ||
Revision as of 06:49, 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
| No. | Tasks | Members | |
|---|---|---|---|
| 1 | Motor and LCD Controller | *Dhruv Kakadiya | *Anuj Korat |
| 2 | GPS and Compass Controller | Chitrang Talaviya, Navjot Singh | |
| 3 | Android Controller and communication bridge | Anush Shankar, Aditya Devaguptapu | |
| 4 | Sensor Controller | Hemanth Konanur Nagendra, Akshay Vijaykumar | |
| 5 | Master Controller | Divya Dodda |
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.
| Week# | Scheduled
Completion Date |
Task | Concerned Team | Status |
|---|---|---|---|---|
| 1 | 9/20 | Understanding flow of whole project
|
Completed | |
| 2 | 9/27 |
|
|
Completed |
| 3 | 10/4 | Testing of individual modules and their components
|
|
Completed |
| 4 | 10/6 | Basic Hardware layout on RC Car |
|
Completed |
| 5 | 10/13 | Obstacle avoidance on RC Car |
|
Completed |
| 6 | 10/20 | CAN bus setup between all 5 controllers
|
|
In progress |
| 7 | 10/27 |
|
|
In Progress |
| 8 | 11/14 |
|
|
In progress |
| 9 | 11/27 | Driving algorithm deployment and testing | Not completed | |
| 10 | 12/1 | Debugging | Not Completed |
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.
