User:Pghsound/ENES-100/project 3

=Week 1 Narrative= I tried to fix the previous problem of the Kinect depth cam not working. Here is the working Kinect example LabVIEW program. Next step is to create my own program for a different Kinect function in LabVIEW.
 * wow ... great job ... love the video ... 10/10/40 --1sfoerster (discuss • contribs) 17:03, 21 April 2014 (UTC)

=Week 2 Narrative= This week I made a program in LabVIEW for the Kinect. It uses the Kinect's depth capture and color video. I also was having trouble with messy VI's. Figured out how to clean up the block diagram.
 * 10/10/40 .. wow --1sfoerster (discuss • contribs) 15:54, 22 April 2014 (UTC)

=Week 3 Narrative= I tested HCC's Kinects to see if they were working correctly. One was working properly, while the other was not displaying the correct skeletal capture.

Next steps are to do something like these links:
 * 
 * 
 * 
 * 
 * 


 * 10/10/40 ... good video, but I had to go to it to figure out it was not working in windows ... did the problem also appear in LabView? What did you do to isolate the problem? --1sfoerster (discuss • contribs) 15:49, 29 April 2014 (UTC)

=Week 4 Narrative= Couldn't find anything related to the serial number of the Kinects online. The working Kinect has a mirrored tilt stand. The one that doesn't work correctly has a black tilt stand.


 * 10/10/20 ... excellent .. the tilt function is called a "ball joint" or "ball and socket joint" ... you will learn these names in statics or dynamics ... --1sfoerster (discuss • contribs) 13:33, 6 May 2014 (UTC)