Does anyone have this working successfully? We like to use
the kinect kiosk for demonstrations. I didn’t keep last year’s labview
environment around. The kiosk worked great last year.
This year the drivers’s station skeleton view
works, just nothing it showing up in the kiosk. I’ve
tried both 10.0.100.15 and .16 and switching blue/red.
The kiosk reacts appropriately to the team color but doesn’t
display the team number,
I tried using the 2012 default driver’s station when installed
on an FRC2013 labview system. That also sees the kinect and I
get the skeleton on the DS but also not on the kiosk.
One and one time only I got output on the kiosk and the team
number displayed as 16xxx (my team number is 2590 :-))
I can’t reproduce this easily. I’m curious if this is working for other teams.
Instead of the kiosk and driver station, why don’t you use some of the examples provided by Microsoft in the SDK?
We used the kiosk one time last year and had troubles in getting everything working. So the next time we had an open house we used some of the examples provided by Microsoft in the SDK. There are plenty of different things, a face tracking, a skeleton tool, our personal favorite is a shape game where you have to pop the shapes with your skeleton- this supports 2 players.
Is your Driver Station netmask 255.0.0.0 ?
Did you install this year’s Kinect SDK software - that may not be compatible with last year’s Beta SDK.
We hooked it up this year to let some elementary school kids drive around the machine. We hooked it directly to the driver station computer using an old test code without updating any of the kinect software and it worked fine. I can ask the programming folks more details for you but I don’t remember there being any major headaches.
>Instead of the kiosk and driver station, why don’t you use some of the
>examples provided by Microsoft in the SD
In our case the point was not to show off kinect itself but to
show off the robot via kinect. Exactly like bgg said - we
let folks drive the robot around and shoot via kinect.
Fun and engaging demonstration.
>Is your Driver Station netmask 255.0.0.0 ?
Hmm… Not 100% sure. Not in front of the system
at the moment so I’ll have to double check.
>Did you install this year’s Kinect SDK software - that may not be compatible
>with last year’s Beta SDK.
Yes, I ended up deleting the Microsoft V1 SDK and had to revert
to the beta SDK since the FRC kinect server install had a hardcoded
check for the beta SDK (and I didn’t feel like trying to hack
that dependency). So I was trying FRC 2013 labview
with last year’s Kinect software (kinect beta SDK and FRC Kinect Server
the FRC kinect kiosk). That’s the gist of this post - should that
be expected to work?
>We hooked it directly to the driver station computer using an old test code
>without updating any of the kinect software and it worked fine
That works fine for me as well. It’s just the remote kiosk
that I can’t get to work.
Mark nailed it. It was the subnet mask. I had it 255.0.0.0 on
one system but not the other… Works just dandy after that.
Thanks.