ECE497 Project Smart Glass

Team members: Hazen Hamather and Luke Kuza

Draft Feedback
Good start, but much is missing. Add pictures of your Smart Glass.

I look forward to seeing your finished report.

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
Smart Glass will be a spin off of the original Magic Mirror developed by Michael Teeuw. The team plans to build a setup that is very similar to his but take it a step further and implement motion control by using an Xbox Kinect. We currently have found a way to access some of the functionality associated with the Kinect such as IR distance and the camera itself. We were able to implement OpenKinect in order to reach these features. The problem we are running into right now is the image recognition aspect. We are attempting to install OpenCV but have run into multiple problems, causing us to search in other places for our solution.

The hardware aspect of this project is 95% complete. The frame and housing has been constructed and the mirror film applied to the glass and installed in the frame. The monitor that rests behind the glass has been securely fastened into place and an external button has been soldered to it to turn the monitor on and off as desired by the user. At this time, we have a basic user interface setup but are exploring other options (freeboard) to give a clean, fresh look.

TODO: Keep this updated

Give two sentences for a brief introduction of the project.

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.

The BeagleBone is running a simple webpage that is constantly making JSON requests to various APIs to keep the interface current. The Bone will also be doing image processing in order to alter the contents of what the user is experiencing.

Work Breakdown
List the major tasks in your project and who did what. The large milestones we have encountered have been designing the frame, constructing the frame, and setting up our interface combined with motion detection controls. Luke originally had the idea of how to mount the glass into a frame and Hazen took that idea and created a SolidWorks model of what the final product should look like. The provided the group with a Bill of Materials (BOM) that we were able to take to the department in order to get funding. Using that BOM, we gathered the right construction materials and began the building process. Hazen took control of the building process and Luke handled the electrical part of altering our monitor to suit our needs. Currently at this time, Hazen is finishing up the User Interface and Luke is attempting to access the Kinect, hoping to implement simple skeleton tracking for gesture recognition. The Kinect is not working as expected right now and we aim to have that ironed out by Wednesday night (11/9).

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. One neat thing we would like to see done at some point is create this same project but run Windows instead. Using Windows for development opens up most (if not all) of the capabilities of the Kinect granted to it by Microsoft. It would make for an easier gesture recognition and also give the ability to do some very complex motion tracking or even facial recognition. Advanced techniques such as the previous could allow the same mirror to be customized for multiple users.

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