Difference between revisions of "ECE497 Project Programmable Light Show"

From eLinux.org
Jump to: navigation, search
(Executive Summary)
(Packaging)
Line 10: Line 10:
  
 
Most of the effort of the project is now focused on changing the interface so that multiple light changes can be bundled in messages, making fewer messages and (hopefully) faster update times.
 
Most of the effort of the project is now focused on changing the interface so that multiple light changes can be bundled in messages, making fewer messages and (hopefully) faster update times.
 
== Packaging ==
 
 
If you have hardware, consider [http://cpprojects.blogspot.com/2013/07/small-build-big-execuition.html Small Build, Big Execuition] for ideas on the final packaging.
 
  
 
== Installation Instructions ==
 
== Installation Instructions ==

Revision as of 21:38, 17 November 2013


Team members: Taylor Purviance

Executive Summary

The idea of this project is to have a bone controlling a chain of LEDs and drive the LEDs to flash different colors and patterns. The patterns and colors being displayed will be programmed via a web interface that is accessible to the public, allowing anyone to program the lights.

At the moment, the project is up and running, allowing individual LEDs to be changed via a drag-and drop programming interface accessible via browser. However, the speed of communications / light changes is still a bit of a problem. Using the slow way, it would take 2 or 3 seconds to change all the lights.

Most of the effort of the project is now focused on changing the interface so that multiple light changes can be bundled in messages, making fewer messages and (hopefully) faster update times.

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 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.

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

Suggest addition things that could be done with this project.

Conclusions

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