View Single Post
  #9   Spotlight this post!  
Unread 12-11-2010, 09:51
JesseK's Avatar
JesseK JesseK is offline
Expert Flybot Crasher
FRC #1885 (ILITE)
Team Role: Mentor
 
Join Date: Mar 2007
Rookie Year: 2005
Location: Reston, VA
Posts: 3,632
JesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond reputeJesseK has a reputation beyond repute
Re: M$ Kinect controlling robots!

Quote:
Originally Posted by biojae View Post
Who says it has to be on the robot?
Why not use it as it was designed, and have your drivers be the controllers?
Quote:
Originally Posted by basicxman View Post
That's exactly what I was saying; I realize that it is probably not FIRST-competition reliable but would still be cool in other environments.
Quote:
Originally Posted by Wikipedia
The Kinect sense has a practical ranging limit of 1.2–3.5 metres (3.9–11 ft) distance
Standing far enough back from the controls for Kinect to properly sensor a driver means that driver has to stand at the very rear of the driver's station. Additionally, both the Driver Coach and the other Driver have to make sure they do not interfere with Kinect's imaging. Finally, every couple of years the human players are also confined to the driver's station; thus any of the HP's movement would have to keep from interfering with the Kinect as well.

By all means file it under 'neat' and 'innovative' -- so long as it's not within a competition robot driver controls context.
__________________

Drive Coach, 1885 (2007-present)
CAD Library Updated 5/1/16 - 2016 Curie/Carver Industrial Design Winner
GitHub

Last edited by JesseK : 12-11-2010 at 09:55. Reason: Communication is iterative...
Reply With Quote