Difference between revisions of "S16: OpenSJ Bluz"
(→Schedule) |
(→Schedule) |
||
| Line 44: | Line 44: | ||
*Understanding the requirements and having initial team discussions on approach to be followed to carry out project | *Understanding the requirements and having initial team discussions on approach to be followed to carry out project | ||
*Forming sub-teams and assigning individual modules to each sub-team | *Forming sub-teams and assigning individual modules to each sub-team | ||
| − | | | + | | Incomplete |
| 09/27/2015 | | 09/27/2015 | ||
|- | |- | ||
| Line 51: | Line 51: | ||
| 10/30/2015 | | 10/30/2015 | ||
| Following up on RC car and other component procurement through team discussions | | Following up on RC car and other component procurement through team discussions | ||
| − | | | + | | Incomplete |
| 10/30/2015 | | 10/30/2015 | ||
|- | |- | ||
| Line 58: | Line 58: | ||
| 10/06/2015 | | 10/06/2015 | ||
| Hardware design of the car including discussions on component placement, soldering and wiring. | | Hardware design of the car including discussions on component placement, soldering and wiring. | ||
| − | | | + | | Incomplete |
| 10/06/2015 | | 10/06/2015 | ||
|- | |- | ||
| Line 65: | Line 65: | ||
| 10/17/2015 | | 10/17/2015 | ||
| CAN message ID's, priorities, data size and format proposals for all the possible CAN messages on the bus | | CAN message ID's, priorities, data size and format proposals for all the possible CAN messages on the bus | ||
| − | | | + | | Incomplete |
| 10/20/2015 | | 10/20/2015 | ||
|- | |- | ||
| Line 72: | Line 72: | ||
| 11/05/2015 | | 11/05/2015 | ||
| Discussions and proposals on basic obstacle avoidance algorithm with sensor integration, hands on and testing | | Discussions and proposals on basic obstacle avoidance algorithm with sensor integration, hands on and testing | ||
| − | | | + | | Incomplete |
| 11/03/2015 | | 11/03/2015 | ||
|- | |- | ||
| Line 79: | Line 79: | ||
| 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 |
| 12/1/2015 | | 12/1/2015 | ||
|- | |- | ||
| Line 86: | Line 86: | ||
| 12/7/2015 | | 12/7/2015 | ||
| Testing the RC car in real world environments | | Testing the RC car in real world environments | ||
| − | | | + | | Incomplete |
| 12/5/2015 | | 12/5/2015 | ||
|- | |- | ||
Revision as of 09:17, 16 March 2016
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.
OpenSJ Bluz
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
- Dhruv Kakadiya
- Surojit Saingupta
- Gerard Ramos
- Fred Sun
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 |
|
Incomplete | 09/27/2015 |
| 2 | 09/27/2015 | 10/30/2015 | Following up on RC car and other component procurement through team discussions | Incomplete | 10/30/2015 |
| 3 | 10/30/2015 | 10/06/2015 | Hardware design of the car including discussions on component placement, soldering and wiring. | Incomplete | 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 | Incomplete | 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 | Incomplete | 11/03/2015 |
| 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 | 12/1/2015 |
| 7 | 11/25/2015 | 12/7/2015 | Testing the RC car in real world environments | Incomplete | 12/5/2015 |
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.
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.
