Jordan Kuehn Posted December 22, 2011 Report Share Posted December 22, 2011 NI has released an API for using the Microsoft Kinect SDK and I've been tasked with a research project involving this device. See the links below: http://zone.ni.com/d...a/epd/p/id/6504 http://www.xbox.com/en-US/kinect http://kinectforwindows.org/ I've followed the instructions on the SDK website, installed the drivers and Visual Studio Express, and everything works fine in the MS demos. The labview config file to allow it to use .NET 4.0 is in place and it sees the .dll included in the API as well as the one installed by the SDK. I've tried mapping the constructor to both. When trying to run the demo I encounter the error screen below in LV2011 x86, LV2011 x64, and LV2010 x86. LV subsequently crashes on all versions, but that's nothing new Thoughts? I've posted to the API page and will post to the dark side if needed. .NET isn't really my cup of tea... //Edit. Google searches have suggested that people who encounter this when doing *shiver* text based programming have corrected the issue by modifying a parameter of their build environment from 'Any CPU' to only x86 CPU. I'm not sure how this would correlate with LabVIEW though. Quote Link to comment
Jordan Kuehn Posted December 22, 2011 Author Report Share Posted December 22, 2011 For those interested, I have a reply from labviewhacker.com (operated by NI employees). "Sorry, but due to Microsoft's recent update of the Kinect SDK, the current version of the hack may not be functional. We are working on getting a new version up. Thanks! Jimmy" Quote Link to comment
vugie Posted December 23, 2011 Report Share Posted December 23, 2011 There are alternative drivers for Kinect - OpenKinect. DLLs, are pure C style, so easy accessible from LabVIEW. There is also some work done on LV wrappers for OenKinect. Quote Link to comment
Jordan Kuehn Posted December 23, 2011 Author Report Share Posted December 23, 2011 There are alternative drivers for Kinect - OpenKinect. DLLs, are pure C style, so easy accessible from LabVIEW. There is also some work done on LV wrappers for OenKinect. Vugie, thanks for pointing those drivers out as well. I had looked into them some prior to the release of the SDK and felt they had promise, but I feel that it is better to build an approach around the official supported SDK now that it's available. Of course, the attractiveness of homebrew drivers is inversely proportional to the level of success I have with the official ones Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.