ECE497 Project: Kinect Project - Revision history

Yoder: Moved to Winter1112 category

2012-07-16T13:54:30Z

Moved to Winter1112 category

Yoder: /* Grading */

2012-02-24T20:07:58Z

‎Grading

Yoder: /* Executive Summary */

2012-02-24T20:01:09Z

‎Executive Summary

Yoder: /* Executive Summary */

2012-02-24T19:55:20Z

‎Executive Summary

Yoder: /* Grading */

2012-02-24T19:52:24Z

‎Grading

Yoder: /* Grading */

2012-02-24T19:51:01Z

‎Grading

Yifei: user instructions, conclusions and others

2012-02-21T04:31:16Z

user instructions, conclusions and others

Show changes

Yifei: other changes

2012-02-20T17:59:13Z

other changes

Yifei: Theory of Operation

2012-02-20T16:30:52Z

Theory of Operation

Yifei at 15:33, 20 February 2012

2012-02-20T15:33:15Z

← Older revision		Revision as of 13:54, 16 July 2012
Line 1:		Line 1:
−	[[Category:~~ECE497~~]]	+	[[Category:ECE497Winter1112]]

	Team members: [[user:Yifei\|Yifei Li]], [[user:Gemini91\|Guanqun Wang]]		Team members: [[user:Yifei\|Yifei Li]], [[user:Gemini91\|Guanqun Wang]]

@@ Line 5: / Line 5: @@
 == Grading ==
-Update your '''Objectives''' to reflect the current objects.  Presently it captures the history of your thinking rather than the current state.  The '''Executive Summary''' isn't one.  See my template for what should be in the summary.
+Overall your wiki doesn't follow everything from the project template.
 == Objectives ==

@@ Line 30: / Line 30: @@
 After burning the microsd card sucessfully, we can boot from this card and see a simplified Angstrom without GUI. All demos ran almost as expected but,
-(1).the program froze sometimes. It even happened sometimes when we were just typing some command. We think maybe it's because of the speed of microsd card. We will get a faster card and have a try.
+# The program (<span style="color:red"> which program? You need more context here.  If I hadn't seen this before I wouldn't know what you are doing</span>) froze sometimes. It even happened sometimes when we were just typing some command. We think maybe it's because of the speed of microsd card. We will get a faster card and have a try.
+# The tracking for legs doesn't work very well, we think maybe it's because we didn't have enough space for the kinect.(When you played kinect game in xbox, it will tell you a large space is required for tracking).
-(2).the tracking for legs doesn't work very well, we think maybe it's because we didn't have enough space for the kinect.(When you played kinect game in xbox, it will tell you a large space is required for tracking).
 . '''Compile the Sample Code on Host'''
@@ Line 43: / Line 42: @@
 The instruction also asked us to install two different versions of QtCreater in the pdf file and in blog, we prefered the version in pdf file since the instruction should be written based on this version.
-After struggling for a very long time, I decided to clean everything up and start over. I followed the instruction one step by step but '''skipped one step''' and it turned out everything works perfectly now.
+After struggling for a very long time, I decided to clean everything up and start over. I followed the instructions (<span style="color:red"> which instructions? Can you give a pointer?</span>) one step by step but '''skipped one step''' and it turned out everything works perfectly now.
 Link [http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=68&sid=6c151b2898f1e8f53039adc335781c9e Omek Forum] may help you with the version problem.

@@ Line 13: / Line 13: @@
 == Executive Summary ==
 . '''Burn the Image Package and Boot the System'''
-The detailed instruction is shown in page7 of developer's guide from omek.
+The detailed instruction is shown in page7 of developer's guide from omek. (<span style="color:red">Give a link to this so it's easy to find.</span>)
 When I tried to run mkcard.sh to create new partitions, I got some errors.

@@ Line 5: / Line 5: @@
 == Grading ==
-Update your '''Objectives''' to reflect the current objects.  Presently it captures the history of your thinking rather than the current state.
+Update your '''Objectives''' to reflect the current objects.  Presently it captures the history of your thinking rather than the current state.  The '''Executive Summary''' isn't one.  See my template for what should be in the summary.
 == Objectives ==

← Older revision		Revision as of 19:51, 24 February 2012
Line 2:		Line 2:

	Team members: [[user:Yifei\|Yifei Li]], [[user:Gemini91\|Guanqun Wang]]		Team members: [[user:Yifei\|Yifei Li]], [[user:Gemini91\|Guanqun Wang]]
		+
		+	== Grading ==
		+
		+	Update your '''Objectives''' to reflect the current objects. Presently it captures the history of your thinking rather than the current state.

	== Objectives ==		== Objectives ==

@@ Line 6: / Line 6: @@
 Our goal is to implant a specific game application into Beagleboard and using Microsoft's Kinect to play with it. We would firstly make the Kinect recognizable to the Beagleboard. And then try to adapt the application to the Beagleboard. We haven't decided which game to play with, because the performance may be greatly influenced by what kind of operating system we want to use, or the size of this game. So the second part would be to test what is the best option for us. Finally, we would try everything to make it work.
-Update: We finally decided to use Omek Beckon 2.4 SDK on BeagleBoard as interface of Kinect to develop our application and we chose Qt creator as cross-compiler tool to program and debug. As the limitation of the image(we could only use the image Omek provided with us, see [http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=58&sid=2ac0c7615fd5accfaf0458ed662ec5bb Omek Forum] for details, you may need to register first), we can't transfer all the drivers and data to the image we used to use and also we can't develop programs with GUI using Qt, because the Omek image only support command-line mode, so we chose to develop the GUI itself within the source code. We searched on line and found the open source code for a game called Q-ball. We are going to use kinect to play with it.
+Update: We previously want to build our own driver for Kinect, and develop our game on Android. For there are many open-source code that we can reference. We got a sample game that run on Android and successfully tested it on BeagleBoard with Kinect. But it seemed that it was quite difficult to develop our own kinect driver. So with the suggestion of Prof.Yoder, we finally decided to use Omek Beckon 2.4 SDK on BeagleBoard as interface of Kinect to develop our application and we chose Qt creator as cross-compiler tool to program and debug. As the limitation of the image(we could only use the image Omek provided with us, see [http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=58&sid=2ac0c7615fd5accfaf0458ed662ec5bb Omek Forum] for details, you may need to register first), we can't transfer all the drivers and data to the image we used to use and also we can't develop programs with GUI using Qt, because the Omek image only support command-line mode, so we chose to develop the GUI itself within the source code. We searched on line and found the open source code for a game called Q-ball. We are going to use kinect to play with it.
 == Executive Summary ==
@@ Line 118: / Line 118: @@
 . Now we are moving to the host side, and install the toolchain and Qtcreator we need.
 == User Instructions ==
@@ Line 124: / Line 126: @@
 == Highlights ==
@@ Line 212: / Line 220: @@
+}
 </pre>
 == Work Breakdown ==
 . Installed the Beckon SDK Development tools on both Linux PC host and BeagleBoard; Successfully tested the sample code and discussed the interface functions. ---completed on February 5th by Yifei Li and Guanqun Wang
 == Conclusions ==

← Older revision		Revision as of 16:30, 20 February 2012
Line 128:		Line 128:

	== Theory of Operation ==		== Theory of Operation ==
		+	The whole point is to use Kinect interface provided by Omek to control the movement of the bar. The original control is achieved by calling Qt key event "Qt::Key_Left", which would get back a value that is used in PlayGameState::updateScene as shown followings:
		+	<pre>
		+	// move
		+	if( mainWindow->isKeyDownLeft() ) {
		+	bat_has_target = false;
		+	itemBat->moveBy(-bat_sp_x_c, 0);
		+	if( itemBat->pos().x() < 0 ) {
		+	itemBat->setPos(0, itemBat->pos().y());
		+	}
		+	}
		+	else if( mainWindow->isKeyDownRight() ) {
		+	bat_has_target = false;
		+	itemBat->moveBy(bat_sp_x_c, 0);
		+	if( itemBat->pos().x() > scene->width() - bat_w_c ) {
		+	itemBat->setPos(scene->width() - bat_w_c, itemBat->pos().y());
		+	}
		+	}
		+	else if( bat_has_target ) {
		+	int bat_centre_x = itemBat->pos().x() + bat_w_c/2;
		+	int dist = abs(bat_centre_x - bat_target_x);
		+	if( dist <= bat_sp_x_c ) {
		+	itemBat->setPos(bat_target_x - bat_w_c/2, itemBat->pos().y());
		+	bat_has_target = false;
		+	}
		+	else {
		+	int dir = bat_target_x > bat_centre_x ? 1 : -1;
		+	itemBat->moveBy(dir * bat_sp_x_c, 0);
		+	}
		+	}
		+	</pre>
		+
		+	In order to replace the condition judgement in if() shown above, we need to first initialize Omek Kinect sensors ready. The Omek give us a good example on how to register and enable Gestures, we would use that directly. The problem is whether we should initialize them in main(), or in class. We need the init to get the value of pGesture in order to get gestureName that used to determine which gesture is detected, so we can't seperate them! If we put them in main(), then we won't be able to process them repeatly. The best way is to put them in class, and use the following code to call the class from period to period.

		+	<pre>
		+	QTimer timer;
		+	QObject::connect(&timer, SIGNAL(timeout()), &w, SLOT(updateScene()));
		+	timer.start(time_per_frame_c);
		+	</pre>
		+	Note: We found a good explanation of this code. See here:[http://developer.qt.nokia.com/doc/qt-4.8/graphicsview-collidingmice.html]

		+	At this point, we have two different ways of coding. Guanqun defined the init function of kinect in a headerfile called GestureDemo.h, and call it within PlayGameState::updateScene. So every period of time_per_frame_c, it would go into the init function, and detect which gestures we make. While, Yifei put the init function into a new class, called PlayGameState::updateKinect, and add another signal called timer1_per_frame_c so that updateKinect and updateScene would be both processed repeatly. The first one worked!
		+
		+	We still want to use the keyboard while playing with it. So we didn't change anything in MainWindow::KeyPressEvent and MainWindow::KeyReleaseEvent.
		+	<pre>
		+	void MainWindow::keyPressEvent(QKeyEvent *event) {
		+	//qDebug("keyPressEvent");
		+	if( event->key() == Qt::Key_Left ) {
		+	this->keydown_left = true;
		+	//qDebug("left");
		+	}
		+	else if( event->key() == Qt::Key_Right ) {
		+	this->keydown_right = true;
		+	//qDebug("right");
		+	}
		+	else if( event->key() == Qt::Key_Escape ) {
		+	gamestate->userQuit();
		+	}
		+	else if( event->key() == Qt::Key_P ) {
		+	gamestate->userPause();
		+	}
		+	else if( event->key() == Qt::Key_Return ) {
		+	QPushButton button = qobject_cast< QPushButton >(qApp->focusWidget());
		+	if (button) {
		+	button->click();
		+	}
		+	}
		+	else {
		+	QMainWindow::keyPressEvent(event);
		+	}
		+	}
		+
		+	void MainWindow::keyReleaseEvent(QKeyEvent *event) {
		+	//qDebug("keyReleaseEvent");
		+	if( event->key() == Qt::Key_Left ) {
		+	this->keydown_left = false;
		+	}
		+	else if( event->key() == Qt::Key_Right ) {
		+	this->keydown_right = false;
		+	}
		+	else {
		+	QMainWindow::keyReleaseEvent(event);
		+	}
		+	}
		+	</pre>

	== Work Breakdown ==		== Work Breakdown ==

@@ Line 5: / Line 5: @@
 == Objectives ==
 Our goal is to implant a specific game application into Beagleboard and using Microsoft's Kinect to play with it. We would firstly make the Kinect recognizable to the Beagleboard. And then try to adapt the application to the Beagleboard. We haven't decided which game to play with, because the performance may be greatly influenced by what kind of operating system we want to use, or the size of this game. So the second part would be to test what is the best option for us. Finally, we would try everything to make it work.
 Update: We finally decided to use Omek Beckon 2.4 SDK on BeagleBoard as interface of Kinect to develop our application and we chose Qt creator as cross-compiler tool to program and debug. As the limitation of the image(we could only use the image Omek provided with us, see http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=58&sid=2ac0c7615fd5accfaf0458ed662ec5bb for details, you may need to register first), we can't transfer all the drivers and data to the image we used to use and also we can't develop programs with GUI using Qt, because the Omek image only support command-line mode, so we chose to develop the GUI itself within the source code. We searched on line and found the open source code for a game called Q-ball. We are going to use kinect to play with it.
 == Executive Summary ==
@@ Line 37: / Line 38: @@
 After struggling for a very long time, I decided to clean everything up and start over. I followed the instruction one step by step but '''skipped one step''' and it turned out everything works perfectly now.
-Link http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=68&sid=6c151b2898f1e8f53039adc335781c9e may help you with the version problem.
+Link [http://support.omekinteractive.com/forums/viewtopic.php?f=21&t=68&sid=6c151b2898f1e8f53039adc335781c9e Omek Forum] may help you with the version problem.
 '''Some conclusion for compiling Qt:'''
@@ Line 65: / Line 66: @@
 == Installation Instructions ==
-* Github links: http://github.com/wangg/ECE497, including Omek image, developer guide, Omek sample code, and Kinect supported Q-ball source code
+* Github links: [http://github.com/wangg/ECE497 Github], including Omek image, developer guide, Omek sample code, and Kinect supported Q-ball source code
 * Omek Beckon SDK Development tools
 == User Instructions ==