Thread: Kinect Issues
View Single Post
  #2   Spotlight this post!  
Unread 18-02-2012, 21:34
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Kinect Issues

Actually, there were two changes. The code you attached was intended to be part of the robot code. It was moved to run on the PC, where it will not run due to a missing library called FRC_NetworkCommunication.out. Since that didn't work, it was changed to not call any library at all.

Anyway, the Kinect VIs in WPILib can be used on the cRIO in a location such as autonomous or periodic. The basic Kinect joystick data is available using just the Joystick opening a Kinect 1 or Kinect 2 edition. The other data such as the Kinect Header can be used to get at the advanced data fields. I uploaded some examples to CD and FIRSTForge showing how to map various arm movements from the low level vertices and make your own joystick on the robot. The FIRSTForge URL is http://firstforge.wpi.edu/sf/frs/do/...inect_examples

Greg McKaskle
Reply With Quote