ECE497 Project Remote Web Cam Viewer - Revision history

Yoder: Removed grade. Moved to Fall2012

2013-05-18T16:18:41Z

Removed grade. Moved to Fall2012

Yoder: /* Grading Template */

2012-11-14T22:58:57Z

‎Grading Template

Yoder: /* Grading Template */

2012-11-14T22:53:48Z

‎Grading Template

Yoder: /* Installation Instructions */

2012-11-14T22:44:44Z

‎Installation Instructions

Yoder: /* Installation Instructions */

2012-11-14T22:43:41Z

‎Installation Instructions

Yoder: /* Executive Summary */

2012-11-14T22:40:31Z

‎Executive Summary

Yoder at 21:59, 14 November 2012

2012-11-14T21:59:19Z

Yoder at 21:58, 14 November 2012

2012-11-14T21:58:43Z

Yoder: Yoder moved page ECE497: Remote Web Cam Viewer Final Project to ECE497 Project Remote Web Cam Viewer

2012-11-14T21:57:30Z

Yoder moved page ECE497: Remote Web Cam Viewer Final Project to ECE497 Project Remote Web Cam Viewer

Lobdeljt: /* Future Work */

2012-11-14T06:58:59Z

‎Future Work

@@ Line 1: / Line 1: @@
-[[Category:ECE497 |Project]]
+[[Category:ECE497Fall2012 |Project]]
 {{YoderHead}}
 Team members: [[user:Draneaw|Alexander W. Drane]], [[user:Lobdeljt|John Lobdell]]
 == Executive Summary ==

@@ Line 11: / Line 11: @@
 Executive Summary (No conclusion sentence.)
 Installation Instructions
-User Instructions
+User Instructions (git has no README.md file)
 Highlights (Text was too small to read.  No audio. Embed video.)
 Theory of Operation (Nice diagrams. Some comments in your source code would help.)
@@ Line 21: / Line 21: @@
 Comments: You pulled it together.  It would be nice if the switching didn't hang.
-Score:  87/100
+Score:  85/100
 </pre>

@@ Line 9: / Line 9: @@
 <pre style="color:red">
-Executive Summary
+Executive Summary (No conclusion sentence.)
 Installation Instructions
 User Instructions
-Highlights
+Highlights (Text was too small to read.  No audio. Embed video.)
-Theory of Operation
+Theory of Operation (Nice diagrams. Some comments in your source code would help.)
 Work Breakdown
 Future Work
 Conclusions
 Demo
-Late
+On time
-Comments: I'm looking forward to seeing this.
+Comments: You pulled it together.  It would be nice if the switching didn't hang.
-Score:  10/100
+Score:  87/100
 </pre>
 == Executive Summary ==

@@ Line 45: / Line 45: @@
   xm$ '''mkdir WebcamFeed'''
-  xm$ '''git clone https://github.com/jtlobdell/bbWebcamFeed.git WebcamFeed'''
+  xm$ '''git clone git://github.com/jtlobdell/bbWebcamFeed.git WebcamFeed'''
   xm$ '''cd WebcamFeed'''

@@ Line 44: / Line 44: @@
 First Download the git Repository, it is located here:[https://github.com/jtlobdell/bbWebcamFeed.git WebcamFeed]
-<source lang="text">
+ xm$ '''mkdir WebcamFeed'''
-xm$ mkdir WebcamFeed
+ xm$ '''git clone https://github.com/jtlobdell/bbWebcamFeed.git WebcamFeed'''
-xm$ git clone https://github.com/jtlobdell/bbWebcamFeed.git WebcamFeed
+ xm$ '''cd WebcamFeed'''
 xm$ cd WebcamFeed
-</source>
 Install Node.js
-  <source lang="text">
+  xm$ '''opkg update'''
-xm$ opkg update
+ xm$ '''opkg install nodejs'''
 xm$ opkg install nodejs
- </source>
 Verify gstreamer is available and up to date
- <source lang="text">
-xm$ opkg update
+ xm$ '''opkg update'''
-xm$ opkg install gstreamer
+ xm$ '''opkg install gstreamer'''
- </source>
 One last thing must be done on the user computer. VLC Media Player Plugin must be available in your browser of choice. This can be done by downloading the software here: [[http://www.videolan.org/vlc/index.html]]  and making sure during installation to install the browser plugin. Many modern browsers will guide you through this if you run into a page that requires a missing plugin.
 Now for reference type the following to get the xM's IP address. It is needed quite soon
-  <source lang="text">
-xm$ ifconfig
+  xm$ '''ifconfig'''
- </source>
 == User Instructions ==

@@ Line 27: / Line 27: @@
 == Executive Summary ==
-The goal of this project is to create a simple webcam based security system that allows a user to remotely view the devices web cam by navigating to a webpage. Then using buttons the user can change what camera they are viewing.
+The goal of this project is to create a simple webcam based security system that allows a user to remotely view the device's web cam by navigating to a webpage. Then using buttons the user can change what camera they are viewing.
 Currently we have the ability to select a camera and view the stream in a remote webpage. This view uses the browser's VLC Plugin. We have tested this with 4 webcams on the xM board.

← Older revision		Revision as of 21:59, 14 November 2012
Line 1:		Line 1:
−	[[Category:ECE497 \|P]]	+	[[Category:ECE497 \|Project]]
	{{YoderHead}}		{{YoderHead}}

← Older revision		Revision as of 21:58, 14 November 2012
Line 1:		Line 1:
−	[[Category:ECE497]]	+	[[Category:ECE497 \|P]]
	{{YoderHead}}		{{YoderHead}}

@@ Line 135: / Line 135: @@
 == Future Work ==
-Adding video capture would add true security camera capabilities to this system. In addition adding motion detection into the video selection stream would be interesting. Though this might be too much for the XM's hardware.
+Adding video capture would add true security camera capabilities to this system. In addition adding motion detection into the video selection stream would be interesting. Though this might be too much for the xM's hardware.
 Having a webpage that displayed all of the video feeds at once would also be an interesting feature but this could over tax the XM's hardware or internet connection.
-Figuring out how to implement this project with only HTML5 and make it so that no plugin is required by the end user was Alex's original plan but the maturity of the knowledge base for HTML5 is not adequate to accomplish this task at this time. But in the future when many of the draft standards are finished this project could be implemented without the vlc-plugin.
+Figuring out how to implement this project with only HTML5 and make it so that no plugin is required by the end user was Alex's original plan but the maturity of the knowledge base for HTML5 is not adequate to accomplish this task at this time. But in the future when many of the draft standards are finished this project could be implemented without the VLC plugin.
-Solving the interesting problem with the random stream failure. This issue arises when switching between streams. Occasionally the video receiver does not receive the stream even though the stream is playing across the network. From experimentation we found that as cameras were added the performance of the entire program greatly decreased. Since we only access one camera at a time the only explanation we could find was that the OS was devoting resources to the devices when they were connected thus creating a much greater overhead as cameras were added. When the cameras were disconnected the performance returned to their previous levels. With four cameras operating a noticeable increase in stream failures was observed. With only two cameras operating about 1/5 of attempts would be unsuccessful. With four cameras the failure rate was significantly higher (as much as 1/3 of attempts would fail). One possible explanation of this is the overhead causing a slow down in setup time for the video out thread compared to the load up time of the browser. While this is set up to go first if the system hanged due to lack of resources this could cause the video stream to start after the html file stopped looking for it. Occasionally the camera just won't turn on. We have found that signaling it again usually fixes the problem without much effort. After trying to figure out what was causing the problem we could not definitively pin down the root cause of the problem and we found no simple or effective solution for it but would like to see it fixed.
+Solving the interesting problem with the random stream failure. This issue arises when switching between streams. Occasionally the video receiver does not receive the stream even though the stream is playing across the network. From experimentation we found that as cameras were added the performance of the entire program greatly decreased. Since we only access one camera at a time the only explanation we could find was that the OS was devoting resources to the devices when they were connected thus creating a much greater overhead as cameras were added. When the cameras were disconnected the performance returned to their previous levels. With four cameras operating a noticeable increase in stream failures was observed. With only two cameras operating about 1/5 of attempts would be unsuccessful. With four cameras the failure rate was significantly higher (as much as 1/3 of attempts would fail). One possible explanation of this is the overhead causing a slow down in setup time for the video out thread compared to the load up time of the browser. While this is set up to go first if the system hanged due to lack of resources this could cause the video stream to start after the HTML file stopped looking for it. Occasionally the camera just won't turn on. We have found that signaling it again usually fixes the problem without much effort. After trying to figure out what was causing the problem we could not definitively pin down the root cause of the problem and we found no simple or effective solution for it but would like to see it fixed.
 == Conclusions ==