Difference between revisions of "S15: Bug Rider"
Proj user14 (talk | contribs) (→Hardware Design) |
Proj user14 (talk | contribs) (→Hardware Design) |
||
| Line 115: | Line 115: | ||
=== Hardware Design === | === Hardware Design === | ||
The main components required for this project are : | The main components required for this project are : | ||
| + | |||
(1) A Toy Car of dimensions approximately 25*12 inches which we bought from WALMART. | (1) A Toy Car of dimensions approximately 25*12 inches which we bought from WALMART. | ||
Revision as of 04:37, 8 May 2015
Contents
Bug Rider
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
- [Vishnuram Venkataswamy Sampathkumar]
- <role>
- [Krishna Sai Sevilimedu Veeravalli]
- <role>
- [Saketh Ram Bhamidimarri]
- <role>
- [Prakash Kurup]
- <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.
| Sl. No | Start Date | End Date | Task | Status |
|---|---|---|---|---|
| 1 | 03/31/2015 | 04/07/2015 | Order required components | *Completed* |
| 2 | 04/08/2015 | 04/14/2015 | Image processing for object tracking | *Completed* |
| 3 | 04/15/2015 | 04/21/2015 | PWM driver and motor calibration | *Completed* |
| 4 | 04/22/2015 | 04/28/2015 | Serial communication & Nordic wireless communication | Scheduled |
| 5 | 05/29/2015 | 05/05/2015 | Platform design for the hexbug and building the framework to hold the camera on top | *Completed* |
| 6 | 05/06/2015 | 05/12/2015 | Ultrasonic sensor for obstacle avoidance | Scheduled |
| 7 | 05/13/2015 | 05/19/2015 | Integration of complete system and testing | Scheduled |
| 8 | 05/20/2015 | 05/26/2015 | Final Testing and demo | Scheduled |
Parts List & Cost
| Item# | Qty | Description | Manufacturer | Part Number | Total Cost |
|---|---|---|---|---|---|
| 1 | 1 | RC Car | New Bright | Jeep 9.6V | $60.00 |
| 2 | 1 | Bluetooth Camera | Adesso | CyberTrack V10 | $40.00 |
| 3 | 2 | SJ-One Board | NXP LPC1758 | SJSU development board, LPC1758 | $160.00 |
| 4 | 1 | HexBug | Innovation First | HexBug Larva - Green color | $8.96 |
| 5 | 1 | Dual H-Bridge Motor Drive | Drok | L298N | $8.48 |
| Total Cost | $277.44 |
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
The main components required for this project are :
(1) A Toy Car of dimensions approximately 25*12 inches which we bought from WALMART.
(2) An Acrylic sheet of dimensions 30*15 milky white color with highest opaqueness for light bought at TAP-PLASTICS.
(3) A framework consisting of vertical rods attached to the front and back of the car and a horizontal rod which can be movable on the vertical rods.The camera will be attached right at the middle of the horizontal rod. The intention of the horizontal rod sliding on the vertical rods is to adjust the height of the camera position relative to the platform.
(4) Ultra-sonic sensors attached at the front portion of the car to provide the obstacle avoidance feature to the car.
(5) The "SJ-ONE" board will be placed underneath the platform,in the slot provided for the batteries of the car.
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.
