Kinect saying vertices are not tracking

[RahatAhmed]

After coping the code from the Kinect tutorial, checking the state of any vertex always comes out as Not Tracking. We can see the kinect skeleton on the DS. Also for some reason running robot main.vi and choosing autonomous doesn't run the autonomous independent.vi, instead we have to run the autonomous.vi itself. Anyone know how to fix it?

[Mark McLeod]

Is your Kinect problem similar to this one?http://www.chiefdelphi.com/forums/sh...d.php?t=100557


To run autonomous you need to choose it on the Driver Station application Operations tab.

[RahatAhmed]

Okay, after further research, I found out there is some Kinect Joystick that has some pre-written code to better interface with. Do you know where in the functions palette I can get the joystick from?

Also, the kinect skeleton in the DS moves and updates fine, so I don't think it's a driver issue. The status LED for the Kinect is green.

EDIT: Nevermind, I figured it out. I haven't been able to test it yet. How are we supposed to structure the code in the Autonomous.vi? I have added to the default code a part where the kinect joysticks(I made two, assuming they are one for each arm) and the motors wire into a while loop, and in the loop the joysticks wire their y axes to a Tank Drive.vi. Is this the correct way to do it?

EDIT 2: I checked the values from Kinect Header, and this is what I got:
Version = "" blank
Num Players = 0
Success = false

So for some reason the DS recognizes the Kinect, but not the code.

[Mark McLeod]

Try installing Visual Studio C#, there may be a dependency on that for getting the Kinect data properly.

[RahatAhmed]

Doesn't the classmate come with visual studio?

EDIT: It does seem to have Visual Studio C# installed on it already. I tried to install .NET 4.0 just to be safe, but it seemed to have it installed already and only gave me a repair or remove option(i repaired it).

EDIT 2: My hypothesis is that the Kinect is installed fine but the robot is not receiving any information over the network, since the DS is receiving the kinect values, but the robot receives 0's and blank strings for everything. I checked my firewall and it was disabled. I have no idea what could be wrong.

[RahatAhmed]

Here are some screenshots of the code. They're kinda big because I didn't have the time to crop them, so sorry about that.

Begin.vi: http://i.imgur.com/BFSqB.png
Finish.vi: http://i.imgur.com/a45vq.png
Autonomous Independent.vi: http://i.imgur.com/leoMF.png

[SuperS_5]

Originally Posted by RahatAhmed

Here are some screenshots of the code. They're kinda big because I didn't have the time to crop them, so sorry about that.

Begin.vi: http://i.imgur.com/BFSqB.png
Finish.vi: http://i.imgur.com/a45vq.png
Autonomous Independent.vi: http://i.imgur.com/leoMF.png

You can make code snippets, might make life easier. To do so, select the desired code, click on edit>"create VI snippet from selection". The result is a compressed PNG, that has VI code attached. It can be dragged and dropped onto a block diagram.

[Mark McLeod]

There seems to be an odd issue with getting the Kinect data from some PCs.
FIRST is looking at it.

[Mark McLeod]

Okay, FIRST thinks that the issue seems to be due to a conflict with the missing Cypress IO board.

Here are some temporary solutions to try.
Please, report back if this helps or fails.

• See if plugging your Cypress board USB in makes it all better.

or

• Go to the Driver station I/O tab, click Configure and change it to Compatible mode to see if that makes the Kinect data work.

[RahatAhmed]

Originally Posted by Mark McLeod

Okay, FIRST thinks that the issue seems to be due to a conflict with the missing Cypress IO board.

Here are some temporary solutions to try.
Please, report back if this helps or fails.

• See if plugging your Cypress board USB in makes it all better.

or

• Go to the Driver station I/O tab, click Configure and change it to Compatible mode to see if that makes the Kinect data work.

I set the DS I/O tab to Configure and it didn't work. Then I installed the update that came out a few days ago (found it on the Team Updates section on usfirst.org), and suddenly the robot started recognizing the Kinect! Thanks for the help, though!