Thread: Programming Kinect
View Single Post
  #11   Spotlight this post!  
Unread 22-01-2012, 12:51
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
  
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,795
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Programming Kinect
I see what you mean.
Retrieving data from the Kinect isn't straight-forward for me either on a particular PC.
The network communication task does not appear to be supplying the Kinect data to the cRIO.

I'll see what I can discover.

P.S.
It seems to be due to the Driver Station PC, possibly when some of the required Kinect software is missing from it.
Symptoms are: the DS/Dashboard Kinect skeleton feedback works fine, but the cRIO never receives the data.
The good news is that your software works if I run it with a properly built Driver Station PC, such as the Classmate.
I'll experiment some more to see what you're likely to be missing, or what's messing things up.

P.P.S.
I assume it was not something really simple like failing to enabled from the Driver Station?
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle
Last edited by Mark McLeod : 22-01-2012 at 19:59.
Reply With Quote