S15: Vision RC 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.
Vision RC Car
Abstract
This section should be a couple lines to describe what your project does.
The goal of the Vision RC Car is to be able to roam wherever a WiFi network is present. A user will utilize a web-based GUI to view a video-feed from the platform, and in turn control the vehicle from the GUI. (Eduardo Espericueta, 04/25/2015)
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
- Team Member 1
- Jonathon Hongpananon - Web Server
- Team Member 2
- Eduardo Espericueta - Motor Control
- Team Member 3
- Shangming Wang - IP Camera Support
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# | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 4/14/2015 | 4/20/2015 | Ed: Attach prototyping board to the RC car. Interface the SJSU One and the motor controller. Test the motor tasks, and verify that steering and drive work as expected.
Jon: Research setting up server on Edison. Flash OS onto the Intel Edison. Solder header pins onto the Edison mini breakout board. Eric: Research streaming camera feed. Create system layout diagram. |
Ongoing | N/A |
| 2 | 4/21/2015 | 4/27/2015 | Ed: Modify the Edison’s web page to form a first draft of what UI will look like. Write JavaScript for UI that will detect a user’s keyboard input.
Jon: Setup node.js server from Edison. Attempt first draft webserver implementation. Eric: Setup streaming camera feed to browser - Part 1 |
Ongoing | N/A |
| 3 | 4/28/2015 | 5/4/2015 | Ed: Integrate the Edison and the SJSU One. Write code to transfer command input from UI to the SJSU One.
Jon: Continuation of node.js server. Expand UI aesthetics and functionality. Eric: Setup streaming camera feed to browser - Part 2 |
Ongoing | N/A |
| 4 | 5/5/2015 | 5/11/2015 | Ed: Integration on RC car platform, more specifically wiring layout, color, and verfication of connections.
Jon: Integration on RC car platform (power supply) Eric: Integration on RC car platform (mounting) |
Ongoing | N/A |
| 5 | 5/12/2015 | 5/18/2015 | Ed: Test motor controls from web GUI.
Jon: Test accessibility and physical range. Eric: Test webcam at distance. |
Ongoing | N/A |
| 6 | 5/19/2015 | 5/22/2015 | Ed: Finish details. Work on Wiki.
Jon: Finish details. Work on Wiki. Eric: Finish details. Work on Wiki |
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.
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.
