Quote:
Originally Posted by alectronic
It has also been officially tested by microsoft to insure proper response time over a "long" cable, so hopefully there won't be any response delays at competition.
|
Why is it implemented this way?
Wouldn't it make more sense for the kinect data to be processed by the computer that is running kinect kiosk?
Then that computer would send the skeleton data to the team's kinect server which would interpret the joints and convert that to joystick commands.
Code:
kinect -> kinect Kiosk <=> kinect server -> robot
currently it is:
kinect -> kinect server -> robot
|-> kinect Kiosk
This way:
* the USB cord is acting within normal USB specs (it uses the cord that comes with the kinect);
* the skeleton data is sent at the same rate to all teams (with the classmate PC, I have seen lag of up to 2 seconds. Not very safe).