Difference between revisions of "Team-08 Wireless Controlled Car Project"
m (Updated category) |
|||
Line 1: | Line 1: | ||
− | [[Category:ECE597| | + | [[Category:ECE597 |P8]] |
{{YoderHead}} | {{YoderHead}} | ||
Team members: | Team members: |
Revision as of 02:49, 29 October 2015
Embedded Linux Class by Mark A. Yoder
Team members:
Divakar Maurya
Himanshu Kamboj
Vinod Kumar
Contents
Grading Template
I'm using the following template to grade. Each slot is 10 points. 0 = Missing, 5=OK, 10=Wow!
00 Executive Summary 00 Installation Instructions 00 User Instructions 00 Highlights 00 Theory of Operation 00 Work Breakdown 00 Future Work 00 Conclusions 00 Demo 00 Not Late Comments: I'm looking forward to seeing this. Score: 00/100
(Inline Comment)
Executive Summary
Introduction to Project: The goal of this project is to create a Wirelessly Controlled Car using DC motors interfaced with beaglebone/pi/.. It will be controlled from any Input device (for our demonstration, let it be a keyboard). The Control signals will be sent over WiFi.
Working parts: We have bought the chassis and mounted the wheels and motors. It will be a two wheel drive.
Not Working Parts: Since, we have just initiated our project, due to unavailability of electronic components, we have not been able to accomplish much. The motors are connected to the battery via a Motor Driver module but it can only be operated when we have a Raspberry Pi and a Wifi Module.
Conclusion: It has been a great experience to assemble all the required parts (whatever we have till now) and then to decide over the parts which we may be needing immediately or when if something goes wrong.
Instalment Instructions
If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.
If you have wiring, include Frizing diagrams.
Packaging
Future packaging of product something look this:
Above_Samplephotos_of_process_can_be_found_here source :[[Source]]
If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.
If you have wiring, include Frizing diagrams.
Installation Instructions
Give step by step instructions on how to install your project.
- Include your github path as a link like this to the read-only git site: https://github.com/MarkAYoder/gitLearn.
- Be sure your README.md is includes an up-to-date and clear description of your project so that someone who comes across you git repository can quickly learn what you did and how they can reproduce it.
- Include a file called install.sh which installs all the files/packages needed. These are the things that only need to be done one.
- Include a file called setup.sh which initializes everything. These are the things that need to be done every time you reboot the Bone.
- Include a Makefile for your code if you use a compiled language.
- Include any additional packages installed via apt-get.
- Include kernel mods.
- If there is extra hardware needed, include links to where it can be obtained.
User Instructions
Once everything is installed, how do you use the program? Give details here, so if you have a long user manual, link to it here.
Highlights
Here is where you brag about what your project can do.
Include a YouTube demo.
Theory of Operation
Give a high level overview of the structure of your software. Are you using GStreamer? Show a diagram of the pipeline. Are you running multiple tasks? Show what they do and how they interact.
Work Breakdown
List the major tasks in your project and who did what.
Also list here what doesn't work yet and when you think it will be finished and who is finishing it.
Future Work
For now, we will try to operate the car sending directions over WiFi signals. Once it is completed, we may use IR sensors to avoid collisions, different coloured LEDs to tell about different ongoing processes.
Conclusions
If we are left with some time after completion of all the aforementioned processes, we will try to regulate the speed of motors in a stepped way (like gear system in Car). We are very excited about that part of project.
Embedded Linux Class by Mark A. Yoder