Kinect Kiosk will not connect to DriverStation

So last night I was attempting to test a Hybrid mode program using our team’s Kinect and I can’t seem to get it to connect to the DS. I followed the PDF’s instructions to the letter, and I still cannot produce a result.

I have an HP Latop set to ip 10.0.100.15 <–Blue I think. subnet 255.0.0.0
Connected to my Robot network 1102
My DS laptop is ip 10.11.2.9 subnet 255.0.0.0
All of my DS and Kiosk images are up to date.

I do wonder does the Kiosk require a FULL labview installation from the flash disk to work. It shows up on the screen just fine on my PC with only the FRC tools. I code in Java so I thought having all of the LabView files was completely unnecessary as the installation instructions state.

All of your IP addresses should fall under the format 10.11.2.*; your DS laptop should be 10.11.2.6.

You do need the full Labview installation as it contains numerous dependencies that the DS requires to function.

The DS does not need the full LabVIEW program. There is an option on the LabVIEW flash disk to install a DS only LabVIEW option. My issue is not the operation of the DS my DS functions normally.

My issue again is the operation of the Kinect Kiosk connecting to the DS.

IP configuration can be set 10.11.2.*

  • being any number between 0 - 9. Not currently being used by the robot, bridge, or router.

Please read the getting started manuals/guides before posting.

The Kinect Kiosk isn’t provided as source and the only machines I’ve tried it on have LabVIEW, but if you’re not seeing any error messages I doubt that’s the source of the issue. I would check that the “Station” setting in the Driver Station matches the alliance of the IP you are setting on the Kinect Kiosk. The Kiosk should show which color it is in the center bar.

I would also check the firewall on the machine you are using as the Kiosk.

It may also be worth noting that the Kiosk is just a display and you don’t necessarily need it for testing. The Kinect display on the Dashboard has worked just fine for most of our hybrid mode testing.

what OS is the computer running?

All computers are running windows 7 Ultimate.
The DS computer is 64x
The Kiosk computer is 84x

I tried plugging the Kinect into my DS computer as Rufflesridge suggested and I did get a change, now the Dianostics window in the DriverStation says
“no Kinect”

YET, I can open the Microsoft Skeletal Viewer and it see the Kinect just fine.

I have the SDK Beta 2 and the Kinect Server installed.

If the skeletal viewer recognizes it, then Windows in OK. It must be something with the FRC tools for Kinect. I think there is a Kinect FRC server. Maybe try re-installing according to the FRC Kinect guide. I don’ know if the USB device order makes a difference. In the DS, I believe there is a diagnostics tab, where you can change the order of the USB devices for the DS. Maybe the DS software expects it in a specific spot.

what is the IP of the server? it must be 10.0.100.15 for a Blue kiosk or 10.0.100.16 for a Red kiosk.
http://www.wbrobotics.com/attachments/article/12/Using%20the%20Kinect%20Kiosk.pdf

i’ve tested exactly as you’ve described myself and it worked just fine for me, if your driver station is seeing the Kinect (on the operation tab your kinect is green and you show one skeleton lit up) then it shoudl be good to go. When you said you ran the microsoft skeletal viewer you were speaking of the standalone program from microsoft, not the skeletal tab within the FRC dashboard, correct?

if you are not getting the green light and skeletal within the FRC driver station and dashboard, then the issue must be related to the Kinect server, on the diagnostics tab of the driver station next to the kinect there is a little refresh button, that will attempt to restart the FRC kinect server to gain a connection to the kinect. if that’s not working you have an issue - either the kinect server isn’t working right or perhaps you are running something else that has grabbed control of the kinect drivers already?

if you are still having issues - check your task manager - make sure KinectServer.EXE is running, if you hit the restart button in the driver station that process should get killed and restarted and you should see a new process id (PID) if you are displaying that column in the task manager.

Lastly if it’s still not working you can attempt to run the kinect server in debug mode, there is a shortcut for that within the kinect server directory (either C:\Program Files (x86)\FRC Kinect Server or C:\Program Files\FRC Kinect Server ) called “KinectServer Debug Mode” the debug mode will simply show you the window with all the streams and connection info - start with a kinect not plugged in, run the debug mode and you should see a small window asking you to plug in a kinect and take it from there…

once you have the kinect seen within the driver station you simply need to assign yourself to red or blue in the driver station operation tab Team station selection, in your case your kinect station is configured as 10.0.100.15 which IS BLUE TEAM not red as you thought, Red is .16

if everything is connected on the same network and you have the right team and a green kinect light - your kiosk should come to life with a skeletal view and a team number…

let me know if you get it working or have addiitonal problems :wink: