Difference between revisions of "S15: Multi-media Car"
Proj user16 (talk | contribs) (→Schedule) |
Proj user16 (talk | contribs) (→Design & Implementation) |
||
| Line 156: | Line 156: | ||
=== Hardware Interface === | === 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. | 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. | ||
| + | |||
| + | We have used the GPIO pins to control the DC Motors using the SJ One Board. For the Motor Control circuit we utilized a device called the H-bridge, an electronic circuit used to control the motion of the motors, ie., forward or backward. We utilise the GPIO pins to deliver a HIGH signal, which in turn runs the motors. | ||
| + | |||
=== Software Design === | === 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 | + | 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 pseudocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it. |
=== Implementation === | === Implementation === | ||
Revision as of 00:49, 3 May 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.
Multi-media Car
Abstract
The aim of this project is to build a self-driving car which can automatically avoid big barriers and obstacles in its path.
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
- Zan Zhan
- <role>
- Rohit Teja Maddula
- <role>
- Mengchi Cheng
- <role>
- Taowu Wen
- <role>
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 No. | Start Date | Planned End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 04/06/2015 | 04/12/2015 | Interfacing motors with SJone board, building the power circuit design | Completed | N/A |
| 2 | 04/13/2015 | 04/19/2015 | Interfacing infrared sensor and ultrasonic sensor, using the feedbacks to control the motors. | Completed | N/A |
| 3 | 04/20/2015 | 04/26/2015 | Writing functions of motors(including turn left&right&forward&revesre), verify the accuracies of those functions. | Completed | N/A |
| 4 | 04/27/2015 | 05/03/2015 | Implementing three ultrasonic sensors, and using the feedbacks to achieve the car can automatically find its own path when counter obstacles. | Ongoing | N/A |
| 5 | 05/04/2015 | 05/10/2015 | Depending on the previous function, adjusting the motors control module to ensure the car keep going straight in the case of no obstacles. | Ongoing | N/A |
| 6 | 05/11/2015 | 05/17/2015 | Assemble all the features together, use multi-tasking to connect all equipment as a unity. | Ongoing | N/A |
| 7 | 05/18/2015 | 05/23/2015 | Check all the details and prepare to demo. | Ongoing | N/A |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Part No. | Part Type | Part Description | Quantity | Cost for each | Total |
|---|---|---|---|---|---|
| 1 | 28015-ND | Ultrasonic Distance Sensor | 2 | $ 2.20 | $ 4.40 |
| 2 | WTV020-SD-16P | Sound Module with Mini SD Card | 1 | $ 3.60 | $ 3.60 |
| 3 | LTYKC-01 | DIY Toy Car (Including 2 DC motors) | 1 | $ 7.00 | $ 7.00 |
| 4 | 18650*2 | 7.4V-2200mAh Rechargeable Battery | 1 | $ 8.50 | $ 8.50 |
| 5 | SJOne Board | Board including LPC1758 from SJSU CmpE | 1 | $ 80.00 | $ 80.00 |
| Total Cost | $ 103.50 |
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.
We have used the GPIO pins to control the DC Motors using the SJ One Board. For the Motor Control circuit we utilized a device called the H-bridge, an electronic circuit used to control the motion of the motors, ie., forward or backward. We utilise the GPIO pins to deliver a HIGH signal, which in turn runs the motors.
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 pseudocode 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.
