S14: Wireless Control Car
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
Wireless Control Car
Abstract
This project is about the development of a robotic car which can be controlled wirelessly. A robotic car has two front and back motors which are controlled independently. Both the motors are attached to a wireless module in built in the microcontroller so that it can be controlled wirelessly. This car also has three ultrasonic sensors which are attached to front, left and right side of the car. These three sensors help in avoiding any collision with the obstacle. This car also has an auto mode which enables the car to run without the user's help.
Objectives & Introduction
The objective of this project is to build a wireless robotic car. This car is designed so that it can be controlled wirelessly. This car has two DC motors to control front and back tires, an H bridge dual motor controller to control the speed and direction of the motor, three ultrasonic sensors for obstacle avoidance, an Accelerometer sensor to detect the direction of board rotation and a wireless module to control the car wirelessly.
The project is divided into following objectives:
- Design the circuit and algorithm for motor controller to control both front and back motor independently.
- Write the driver to control in build accelerometer sensor on the microcontroller.
- Write the wireless driver to send and receive commands between two microcontroller boards.
Team Members & Responsibilities
- Deepak Yadav
- Project Design and Testing
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# | Date | Task | Actual |
|---|---|---|---|
| 1 | 02/24 | Project Planning | Completed |
| 1 | 03/06 | Order Parts | Completed |
| 1 | 03/10 | Reviewing part's user manual and datasheet | Completed |
| 3 | 03/24 | PWM Driver | Completed (04/6) |
| 3 | 03/24 | Wireless Driver | Partially Completed (Need to add Ack bit/error checking) |
| 3 | 04/1 | Acceloremoter Driver | Partially Completed |
| 3 | 04/12 | Design Integration | Pending |
| 2 | 04/14 | Testing and Debug-Phase 1 | Pending |
| 2 | 04/21 | Testing and Debug-Phase 2 | Pending |
| 1 | 05/08 | Project Demo | Pending |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | SJOne Board (LPC1758) | One board from SJSU CmpE and one board by Preet(FREE) | 2 | $80.00 |
| 2 | Toy car(including two DC Motors) | Grocery Outlet (Any toy store/grocery store such as Walmart) | 1 | $15.00 |
| 3 | Ultrasonic Sensor | Amazone | 1 | $5:00 |
| 4 | 9V Battery | Frys | 1 | $12:00 |
| 5 | Accessories (Jumper Wires, prototype board and battery charger) | Frys | 1 | $20:00 |
| Total Cost | $132:00 |
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
Send me your zipped source code and I will upload this to SourceForge and link it for you.
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.
