View Single Post
  #12   Spotlight this post!  
Unread 15-01-2011, 10:45
davidthefat davidthefat is offline
Alumni
AKA: David Yoon
FRC #0589 (Falkons)
Team Role: Alumni
 
Join Date: Jan 2011
Rookie Year: 2010
Location: California
Posts: 792
davidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud of
Re: Kinect is Legal for Both Drive Station and Field Use (Here’s why)

Quote:
Originally Posted by MaxKinect View Post
This is a very good question.

We will program our drive station to use both a XBOX controller and the Kinect. (Not at the same time) Based on years of using a joystick (Xbox controller) we know how it works. The Kinect interface will be a totally new adventure. Our goal will be to make a natural interface in which anyone can walk up and drive our robot. This may not be possible in 5 weeks, it may never be possible.



The kinect on the field may not be a good choice for this game. We will find out by trying both a standard camera and the Kinect (depth sensor).

As for the cRio precious clock cycle, if we off load the visual processing to a laptop and use C++ in the cRio there will be lots of unused cRio cycles.
Yes, the laptop would get the image input and process it, but you would then have to transfer that data to the cRio and then the cRio has to move the motors and ect. I honestly do not think one has to invest a $100 for a kinect but rather just invest $20 on a pair of low end webcams.
__________________
Do not say what can or cannot be done, but, instead, say what must be done for the task at hand must be accomplished.