08-12-2012 04:17 PM
Attempting to use Kinesthesia vi's in an FRC cRIO project yields many of these wire errors. The errors occur in sub-vi's being called by Kinesthesia and are caused by data type wires specific to the Kinect library. These wires carry properties, functions, and methods loaded from the DLL Microsoft.Kinect. Below is context help for one of the many wires invoking these errors.
I know that the problem is specific to the FRC framework because the library works perfectly in a blank vi or project. Does the framework not allow third party libraries? Is there a way to change the properties of the project and allow the use of Kinesthesia? Any help is greatly appreciated.
08-13-2012 09:27 AM
I'm not sure about kinesthesia but I am pretty sure that FRC works with Kinect.
I've used this before: https://decibel.ni.com/content/docs/DOC-20154
08-13-2012 08:08 PM
That method stopped working for us after the new SDK came out and installed new drivers. The driver station no longer recognizes the Kinect, which is why we were looking for alternative libraries that might let us keep experimenting with the Kinect.
05-22-2013 07:54 PM
to solve the problem of compatibilaidad between LabVIEW and. NET 4.0 framework follow signs for this publication
attached to the configuration file