Difference between revisions of "ECE497 Project Tweet-A-Watt"
| Line 2: | Line 2: | ||
Team members: [[user:Andrewca|Chris Andrews]], (List all the team members here with link to their eLinux User page. Use my format.) | Team members: [[user:Andrewca|Chris Andrews]], (List all the team members here with link to their eLinux User page. Use my format.) | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Executive Summary == | == Executive Summary == | ||
| − | + | This project is based off of two projects and bringing the results to the Beaglebone Black. The first project is [http://www.ladyada.net/make/tweetawatt/index.html Tweet-a-Watt]. This takes a signal from a Kill-A-Watt power meter and reports it to a host computer. The second one is [http://www.element14.com/community/community/raspberry-pi/blog/2013/04/05/raspiwatt-discover-power-consumption-using-a-kill-a-watt-pi#comment-21839 RaspiWatt]. This modified the first project in order to use a Raspberry Pi instead of a general purpose computer. | |
Give two sentences telling what works. | Give two sentences telling what works. | ||
Revision as of 11:19, 1 November 2013
Team members: Chris Andrews, (List all the team members here with link to their eLinux User page. Use my format.)
Contents
Executive Summary
This project is based off of two projects and bringing the results to the Beaglebone Black. The first project is Tweet-a-Watt. This takes a signal from a Kill-A-Watt power meter and reports it to a host computer. The second one is RaspiWatt. This modified the first project in order to use a Raspberry Pi instead of a general purpose computer.
Give two sentences telling what works.
Give two sentences telling what isn't working.
End with a two sentence conclusion.
The sentence count is approximate and only to give an idea of the expected length.
Packaging
If you have hardware, consider Small Build, Big Execuition for ideas on the final packaging.
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.
