|
Re: Kinect, cRIO crashes, and RetVal 3
IIRC, in 2012 teams solved these kinect problems by plugging in a cypress i/o board and setting it to advanced mode.
The kinect code (and way over complicated driver station communication code) is somewhat of a disaster. We've seen our fair share of random communication issues with even the sample software. Looking through the WPI source, they've left a few interesting comments, like "//temporary hack for 241", which I'm sure made sense to the person writing the software at the time, but doesn't really help.
The issue is with the mystery method "getDynamicControlDataFn.call4() , which returns a mystery value of three (not 0, 1, 2 that is shown in the comment).
|