ECE497 Project Electric Car

Revision as of 15:04, 17 November 2013 by Zhenw (talk | contribs)
Jump to: navigation, search

thumb‎ Embedded Linux Class by Mark A. Yoder

Team members: Junxuan Hou, Zhen Wei

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 Late
Comments: I'm looking forward to seeing this.

Score:  10/100

(Inline Comment)

Executive Summary

This project interfaces the Beaglebone with motor-based electronic mini-car. The gpio pins are used to control the motor on the car to remote it. Some additional interfaces, such as a IR sensor to control the moving direction of the car, and an analog input to control the speed of the car, are considered to be done based on the progress of the project.

Currently we have the small car which can be controlled by keyboard, or IR sensor. With the keyboard controlling, the car can go foreword and backward, make a turn to both right and left. With the IR sensor controlling, the car can keep space before the barrier in front of item.

At first, we use the H-bridge to control four motors which connect to four wheels for the car. And use the GPIO pins to control this H-bridge. And then use a analog input pin to get the signal feedback from the IR sensor.

Depending on the time, in the feature time, there are lots of works can be done for this robot car.


If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.

Parts List:

  1. sharp 2d120x f IR sensor X1
  2. L293 H-Bridge Chip X1
  3. 1N4004 Diodes X8
  4. 100 ohm Resistors X2
  5. DC Brush motor X4
  6. On/Off Switch X1
  7. Robot Kits X1
  8. Beaglebone X1

Installation Instructions

The Github Link for this project is

Give step by step instructions on how to install your project.

  • Be sure your 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 Makefile for you code.
  • Include any additional packages installed via opkg.
  • 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.


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

Suggest addition things that could be done with this project.


Give some concluding thoughts about the project. Suggest some future additions that could make it even more interesting.

thumb‎ Embedded Linux Class by Mark A. Yoder