1. Wiimote/Kinect Lab Design Senior Design December 2011, Group 16 Adviser: Dr. Tom Daniels Brenton Hankins Rick Hanton Harsh Goel Jeff Kramer

2. Outline Problem/Solution Requirements Risks, Costs, and Schedule Wii Hardware WiiWrap and Software Kinect Hardware Software Test Plan Project Status Work Distribution Future Plans

3. Problem Statement The Wii Wrap software used by freshmen Computer Engineering students is simple but needs improvement for installation and use by novice users such as a high school science teachers. In addition, similar software should be developed that uses the Microsoft Kinect sensor as input to student- written programs.

4. Solution

7. Functional Requirements Develop an installer for the Wiimote project. Identify and Remove errors from the Wiimote lab software Correct buffering problems and synchronize user program with the incoming data stream. Make Kinect sensor data streams available to the user in an efficient and real-time manner Provide an interactive application that students can program using the Kinect data. Have an interface to write programs on the received Kinect data and run them.

8. Non-Functional Requirements Reliability: We will refine and package the software that is designed. This pertains to optimization of real-time processes such as data processing. A testing plan shall be developed for this purpose. Portability: The project shall be portable between computers. We will cater mainly to windows, but will ensure that our libraries are extendable in case there is a need to adapt it to another system. Additionally, the software shall be easy to install and remove. Usability: The project shall be easy to use, both for instructors and students. It shall simplify tasks to set up and run projects by means of intuitive GUIs so that students can focus on problem solving aspects as much as possible.

9. Assumptions The software is designed to be used in a Windows computer lab that has both a bluetooth dongle and a Wiimote or a Kinect sensor at each computer terminal. We are currently assuming that the Microsoft SDK will be released in the coming months, otherwise development will continue based on the OpenKinect software on the Windows platform

10. What makes us unique? Using video game hardware for to teach programming in an educational setting Designing software for students with little programming experience to work with 3D video capture & processing functions Interactive API and GUI that makes it easy for students to program without worry about OO programming or managing system/hardware issues.

11. Existing Developed Software The Wii Wrap software was previously developed by a student at Iowa State Similar software for the Wii Remote exists such as Wiimote Whiteboard, WiinRemote, or GlovePie OpenKinect is a package of software created by enthusiasts to run Kinect programs on Linux, Mac, and Windows using a variety of languages Within a few weeks Microsoft will release a Kinect SDK specifically for Windows

12. Risks Risk 1: Temporarily lose a developer from our team for unforeseen reasons. Mitigation 1: The team will do our best to continue work without the developer while they are gone and rely on a detailed documentation trail. We will use technologies like Skype and email to keep in touch with the developer during their absence. Risk 2: Unable to keep tasks fully on schedule due to other projects and schoolwork. Mitigation 2: Set up minor deadlines to make progress on larger tasks. Risk 3: Important equipment becomes lost or nonfunctional (Wiimote, Kinects) Mitigation 3: Jeff has several personal Wiimotes available to him for use and there are one or two extra department-owned Kinects Dr. Daniels has for use. Risk 4: No individuals on the project team have experience programming with graphics APIs. Mitigation 4: We have built periods of time into our schedule for us to work on developing the necessary experience with OpenGL and SDL environments to allow us to design and develop software for the Kinect efficiently.

13. Cost Estimates ItemCost Microsoft Kinect (1) for development$150 Wiimotes and Bluetooth adapters$0 (owned by dept.) Total:$150

14. Cost Estimates TaskEstimated Hours # People per Task Estimated Cost @ $20/hrs Define Customer Requirements204$400 Refine Customer Requirements204$400 Project Plan404$800 Set Up Website202$400 Final Design Document804$1,600 Design Review84$160 Remove Known Bugs from Wii Wrap201$400 Develop Installer for Wii Project201$400 Write Documentation for Wii Project202$400 Research Software for Kinect Package1002$2,000 Development on Kinect Package6004$12,000 Document Kinect Package202$400 Testing of Kinect Package3504$7,000 Total1318$26,360

15. Schedule

16. Hardware - Wii Wii Remote / Wiimote 11 buttons + Power Roll/Pitch/Yaw Gyro Infrared Sensor Speaker (unsupported) Optional Nunchuck (unsupported)

17. Software Dataflow Wii Lab

18. Development Software Selection Wii Wrap Written in C GUI written in Java Kinect SDK Written in C++ Wii Wrap installer MSI

19. How Wii Wrap Works

20. Wii Wrap GUI

21. Fix Run/Stopped Errors in GUI when the Wii Wrap software doesn’t execute as planned. Discover where the lag in display output is (Java Buffers, Windows I/O) Integrate GUI into Wii Wrap installer

22. Hardware - Kinect RGB Webcam Camera 640x480 @ 30 Hz (center) IR Projector Projects Grid for Depth Mapping IR Camera at 640x480 @ 30 Hz collects depth data (right) Microphones give room audio Small Panning motor turns sensor bar from side to side Onboard image preprocessing Projector power draw requires extra AC power Thanks to iFixit for some specs data

23. Kinect - Approaches Naïve Approach Develop similar text output program that is based on OpenKinect, using OpenGL, pthreads, and the Windows port of the Linux USB library functions Allow students to generate a spreadsheet of data that they can work on before developing real-time software. Con: Slow, lots of text processing and possibly storage

24. Kinect - Approaches What we need Provide a GUI environment that would use OpenGL (or an alternative) to show basic output of the Kinect (depth on video) as well as user modifications to the video data (head replacement, skeleton tracking, etc). Want to make use as painless as possible (no pthreads etc to deal with) Colored image to visualize depth

25. Kinect - Design Need to evaluate how to best integrate student code Concept A : Process-Update Model Provide a framework of classes that students modify without needing to know how OO programming works Process* Update* API for the Student Called when new frame data is available Called to update the screen after processing User Models * -> function pointers

26. Kinect Backend: High-Level Sketch Acquire Moving Average of Frames Apply User-Defined Process* Function Apply User-Defined Update* Function Apply Changes to Output Screen Anticipated User View Input ScreenOutput Screen

27. Test Plan We will use similar test plans for both the Wii and Kinect. Initially we will use black box testing methods on individual modules of the program. Testing boundary input values such as null, negative values, etc. Randomizing input values in case edge case is missed The second phase of testing will be integration testing. Testing the entire system as a whole single unit Making sure all the individual modules function when combined GUI testing can be done alongside integration phase of the testing plan. Consists of making sure GUI is responsive, functions properly (buttons do the correct actions)

28. Test Plan (Part 2) Once the functionality is tested, we will need to do performance testing especially on the GUI. Use Eclipse TPTP to test performance. Test GUI input buffering, load tests, etc. Will have Dr. Daniels use the programs to see if they are satisfactory and what changes need to be made. Make revisions to code based on Daniels’ feedback

29. Current Project Status Have been working on developing a software update for Wii Wrap Finishing installer for Wii Wrap Still need to write documentation for Wii Wrap and provide a distribution setup Started experimenting with the OpenKinect software and communicating with OpenKinect founder about release of Microsoft SDK Currently preparing a test plan for the Kinect

30. Work Distribution / Fall ‘11 Plans Now – May 6: Complete Wii Wrap Installer (Brenton) Now – Sept. 1: Identify data stream from Kinect (Rick/Brenton) Now – Sept. 1: Make the data streams accessible to user (Rick/Brenton) Now – Sept. 1: Developer user engine/API, investigate graphics (Harsh/Jeff) Sept. 1 – 7: Document Kinect package (Rick – Lead) Sept. 7- 21: Testing of Kinect Software (Jeff – Lead) Sept. 22-Dec: Fix Kinect Software Issues, Complete Documentation (All)

31. Questions?