Why doesn't my Kinect for Xbox 360 work?


#1

First checks

  1. Is the Kinect power plug connected? (there is a steady green light on the Kinect USB cable if this is true)

  2. Make sure that the Kinect is connected to a USB 2 port (the plastic part in the USB port is black, not blue)

  3. Does the Kinect blink a green light when connected?

  4. On Windows check the Device Manager to see if the sensor is detected as:

    • PrimeSense
      • Kinect Motor
      • Kinect Camera
  5. On OS X, the XBox 360 Kinect model 1473 may not work at all due to firmware issues that aren’t yet solved. If this is the case, you can try using our alternative driver alpha build here. You can see this model number at the bottom of your sensor device.

If you don’t see the Kinect Camera device in the Device Manager and you are on Windows 8 or later the sensor driver installation could have failed. By default Windows releases after Windows 8 require that all installed device drivers are signed and don’t allow installation of non-signed drivers. The Kinect driver that NI mate uses with OpenNI 1 is not signed so some extra steps are required to enable trouble free installation:

  1. Press “Win+R” to open up the run prompt and enter “shutdown.exe /r /o”.

  2. Press “OK” to restart to the “Choose an option” screen.

  3. Select “Troubleshoot” (icon with tools).

  4. Select “Advanced options” (Icon with checkmarks).

  5. Select “Windows Startup Settings” (Icon with gearwheel).

  6. Press “Restart” to restart the computer to the “Advanced Boot Options” screen.

  7. Select “Disable Driver Signature Enforcement”.

  8. Once the computer starts install NI mate.

  9. Once the NI mate installation is complete plug in the Kinect and start NI mate.

Additional things to try out

If all of the previous things check out proceed with the following:

  1. Try connecting the Kinect to a different USB port.

  2. Unplug any other “big” USB devices from the computer. The Kinect requires most of the bandwidth a USB 2 controller can provide, so all other devices requiring significant bandwidth (for example a web camera) should be disconnected.

  3. Uninstall any of the following software if it’s currently installed:

    • OpenNI
    • PrimeSense - Nite
    • PrimeSense Sensor KinectMod, or any other sensor device driver.
  4. On Windows: Uninstall NI mate and the sensor device driver:
    Windows Driver Package - PrimeSense (psdrv3) PrimeSense/PrimeSensor

  5. On Windows: Reinstall NI mate and make sure to enabled the driver installation if it’s unchecked at the installation screen for some reason.

Ensure correct drivers are selected on Windows

On Windows even after uninstalling any other sensor device related things it could be that for some reason the drivers installed by NI mate have been overridden by some other sensor drivers. You can change the drivers manually by following these steps:

  1. Go to the Windows Device Manager and locate the Kinect camera and Kinect Motor devices.

  2. Right click on the Kinect Motor and select “Properties”.

  3. From the driver tab select “Update Driver…”.

  4. Select “Browse my computer for driver software”.

  5. Select “Let me pick from a list of device drivers on my computer”.

  6. To use NI mate you should choose the “Kinect Motor” driver without the signature logo.

  7. Clicking “Next” will make the selected driver the active one.

  8. Repeat the above steps for the “Kinect camera” device.


Documentation: Kinect for Windows 1 / Kinect for Xbox 360 (models 1414 & 1473)
Problems with getting Kinect to work with NI mate V2
NI mate 2.11 released!
Documentation: Kinect for Windows 1 / Kinect for Xbox 360 (models 1414 & 1473)
Il se passe rien,
Problems with getting Kinect to work with NI mate V2
Problems with getting Kinect to work with NI mate V2
#2

So far I checked every above listed suggestion. Actually my kinect xbox 360 is connected to nimate and it is on the list. it is blinking yellow and even the infrared camera red light is on. unfortunately I dont get any depth or rgb image to the program. I had before a similar problem with nimate 1.2 on this computer, where I couldnt get any data to Blender. I am confused where the problem might be.


#3

Could you check if there’s anything outputted in the log? NI mate V2.0 defaults to GPU transfer on both OS X (Syphon) and Windows (Spout), which might cause problems if your GPU isn’t up to the task. You could try disabling the GPU transfer by going to your Preferences and unchecking “Use GPU transfer”. While you’re at it, also try disabling “Live Feeds” for now.


#4

Great That helped! Thank you Julius!


#5

I’m using the NImate version 1, having bought it a few days before v. 2 appeared (surprise!). So far I have a working depth field 1 out of every 5 attempts. The application either opens quickly, loads and is seen on the live feed tab, and runs fine (very rare) or more typically, loads slowly, runs for a few minutes, and then the live feed disappears. Syphon sources appear invisible as well in other programs. Log shows no errors, the depth feed just disappears. Occasionally the program does open quickly and shows a depth field, but then disappears randomly within 10 minutes. Often, when this happens, closing the program causes the program to crash and freeze and I need to force quit the program.
I have run through the troubleshooting suggestions above. I am using a 2 year old mac. I am not trying to do anything other than just get a depth field to use a mask. Any quick reply would be much appreciated.


#6

Are you running V1 or V2 in this case?


#7

I mentioned above in my first sentence that I am using NImate version 1. After writing my message above, Nimate started working and stayed stable all evening. The next morning it was crashing again for several hours. I took it that afternoon hoping for the best in potentially using it for a video installation and I was very happy- it worked perfectly all day and into the night with no issues. Not sure what changed, but it is now working- going to set-up again in my studio and test again and see if stays stable. So far so good. Thanks.


#8

Sorry,but i am trying all day to connect my kinect with ni mate,i have uninstall and install the drives many many times.I have kinect v1 in the latest ni mate and windows 10,i just run the sensor test in command prompt and it outputs me:

Sensor test started for 200 frames:

progress: initializing device context
progress: USB enumeration
progress: USB open
Error with USB open: USB device not found!.
progress: enumerating connected devices
Error with enumerating connected devices: Can’t create any node of the requested type!.
progress: Preparing led message
Error with Preparing led message: Invalid Xiron USB device handle!.
startlive failed
shutting down sensor

i have installed the kinect for windows 1.8v,

Thank you very much


#9

We haven’t tested the old Kinect for WIndows (Kinect model 1517) on Windows 10 yet, and it seems the runtime download page (http://www.microsoft.com/en-us/download/details.aspx?id=40277) does not list Windows 10 as a supported platform. This does not necessarily mean that you can’t use the sensor on WIndows 10, but it’s one possible cause. We don’t yet have a Windows 10 machine at our office, but we’re going to test this as soon as we get one.

You could try installing the Kinect for Windows 1.8 SDK and see if the included samples work: http://www.microsoft.com/en-us/download/details.aspx?id=40278. During the installer, make sure to download the Developer Toolkit that gives you the actual samples. The samples will be located in C:/Program Files/Microsoft SDKs/Kinect/Developer Toolkit v1.8.0/tools/ToolkitBrowser/ToolkitBrowser.exe. These are the official releases by Microsoft and should work as a good benchmark. Try the “Infrared Basics -D2D”.


Crashes NI Mate
#10

I test it,i have the kinect (model 1414),it works with nimate but it wants the same procedure as windows 8.I deleted all the kinect drivers ,i disabled the signature drive ,and then i install the ni mate.After that,and because some programms want the windows sdk 1.8v drives(such as Scanect),i installed the kinect sdk 1.8v and now i just switch drivers.whenever i use blender or skanect.

Thanks a lot,ni mate is an excellent application.


Can I use multiple sensors of the same type concurrently?
#11

Hello,

've problems with a kinect 360 “1414”, as soon as i plug it in the led turns red, and doesn’t show in device manager(win) or sys info (osx). is it the USB hub inside kinect ?
is there somebody with similar problems ?

thank, any help appreciated


#12

Hello!

The fact that you don’t see it on OS X could be an issue with the USB port you’re using. The 1414 should be plugged in a USB 2 port (the port is not blue).

Did you successfully install the unsigned driver which the 1414 needs on Windows 8+? There should be instructions for this when you run the sensor installer from NI mate, but the steps are:

  • Press “Win+R” and enter “shutdown /r /o”
  • Press “OK” to restart to the “Choose an option” screen
  • Select “Troubleshoot” (icon with tools)
  • Select “Advanced Options” (icon with checkmarks)
  • Select “Windows Startup Settings” (icon with gearwheel)
  • Press “Restart” to restart the computer to the “Advanced Boot Options” screen
  • Select “Disable Driver Signature Enforcement”
  • Once the computer starts run the installer again

#13

Bonjour,
Enfin j’ai réussis à faire des enregistrement BVH.
Tout fonctionne très bien sous Kinect Windows 2.
Pour ce qui est d’Openi 1, Openi 2, ma fois je cherche à comprendre.
Il semblerais que les fichiers Drivers ne veulent pas ce télécharger.
Mais bon cela est un début.

Bonne journée.

Hello,
Finally I managed to make BVH recording.
Everything works fine under Windows Kinect 2.
In terms of Openi 1, 2 Openi my time I try to understand.
It semblerais Drivers that files will not download it.
But hey it’s a start.
Good day.


#14

We are having similar issues with the Kinect v2, where the “use GPU transfer” setting causes NI Mate to crash. Spout doesn’t output, which I assume to be a consequence of the GPU transfer crash. The crash log doesn’t run, so we can’t provide any script on what might be causing this.

We are on Windows 10 64-bit with a Kinect v2 (i.e. Kinect for Xbox One). The system has 8Gb RAM and a 2.7GHz (turbo) Intel i5 chip. The GPUs are an AMD Radeon R5 M330 and an Intel HD Graphics 5500. Has anyone experienced any conflicts with graphics switching?

We have tried removing all the drivers and reinstalling. The problem unfortunately persists. Any suggestions?


Why does GPU texture transfer not work on my computer?
#15

Created a new topic for this here Why does GPU texture transfer not work on my computer?


#16

Hi,

I also have the problem that I cant get my Kinect to work with NI mate.
The software recognises the sensor when I connect it (as Open Ni 1) but it it will not start.

I am using a kinect 1414 which works well on this computer with other software such as Skanect, OSCeleton etc.

My system Specs:

I think I only have USB 3 ports.

I am currently using the free version but would buy the pro version if I get this working.
Any help would be much appriciated.

Here is the log from NI mate:

18:34:12: Starting input 1: Kinect for Xbox
18:34:12: Input 1: Live sensor not found.
18:34:12: Input 1: startlive failed
18:34:12: Input 1: shutting down sensor
18:34:12: Input 1 quit normally.

Here is the terminal log from the./Delicode_Sensor_OpenNI sensor_test

Sensor test started for 200 frames:

progress: initializing device context
progress: USB enumeration
progress: USB open
progress: enumerating connected devices
Starting live sensor: PrimeSense SensorKinect
progress: creating sensor device
progress: accessing depth stream
progress: setting depth format
progress: setting depth mirror
progress: accessing RGB stream
progress: setting RGB format
progress: setting RGB mirror
progress: creating user generator
progress: starting live streams
Using GPU (Syphon) for shared textures.
Sensor started
1: progress: updating all sensor data
2: progress: updating all sensor data
3: progress: updating all sensor data
4: progress: updating all sensor data
5: progress: updating all sensor data
6: progress: updating all sensor data
7: progress: updating all sensor data
8: progress: updating all sensor data
9: progress: updating all sensor data
10: progress: updating all sensor data
11: progress: updating all sensor data
12: progress: updating all sensor data
13: progress: updating all sensor data
14: progress: updating all sensor data
15: progress: updating all sensor data
16: progress: updating all sensor data
17: progress: updating all sensor data
18: progress: updating all sensor data
19: progress: updating all sensor data
20: progress: updating all sensor data
21: progress: updating all sensor data
22: progress: updating all sensor data
23: progress: updating all sensor data
24: progress: updating all sensor data
25: progress: updating all sensor data
26: progress: updating all sensor data
27: progress: updating all sensor data
28: progress: updating all sensor data
29: progress: updating all sensor data
30: progress: updating all sensor data
31: progress: updating all sensor data
32: progress: updating all sensor data
33: progress: updating all sensor data
34: progress: updating all sensor data
35: progress: updating all sensor data
36: progress: updating all sensor data
37: progress: updating all sensor data
38: progress: updating all sensor data
39: progress: updating all sensor data
40: progress: updating all sensor data
41: progress: updating all sensor data
42: progress: updating all sensor data
43: progress: updating all sensor data
44: progress: updating all sensor data
45: progress: updating all sensor data
46: progress: updating all sensor data
47: progress: updating all sensor data
48: progress: updating all sensor data
49: progress: updating all sensor data
50: progress: updating all sensor data
51: progress: updating all sensor data
52: progress: updating all sensor data
53: progress: updating all sensor data
54: progress: updating all sensor data
55: progress: updating all sensor data
56: progress: updating all sensor data
57: progress: updating all sensor data
58: progress: updating all sensor data
59: progress: updating all sensor data
60: progress: updating all sensor data
61: progress: updating all sensor data
62: progress: updating all sensor data
63: progress: updating all sensor data
64: progress: updating all sensor data
65: progress: updating all sensor data
66: progress: updating all sensor data
67: progress: updating all sensor data
68: progress: updating all sensor data
69: progress: updating all sensor data
70: progress: updating all sensor data
71: progress: updating all sensor data
72: progress: updating all sensor data
73: progress: updating all sensor data
74: progress: updating all sensor data
75: progress: updating all sensor data
76: progress: updating all sensor data
77: progress: updating all sensor data
78: progress: updating all sensor data
79: progress: updating all sensor data
80: progress: updating all sensor data
81: progress: updating all sensor data
82: progress: updating all sensor data
83: progress: updating all sensor data
84: progress: updating all sensor data
85: progress: updating all sensor data
86: progress: updating all sensor data
87: progress: updating all sensor data
88: progress: updating all sensor data
89: progress: updating all sensor data
90: progress: updating all sensor data
91: progress: updating all sensor data
92: progress: updating all sensor data
93: progress: updating all sensor data
94: progress: updating all sensor data
95: progress: updating all sensor data
96: progress: updating all sensor data
97: progress: updating all sensor data
98: progress: updating all sensor data
99: progress: updating all sensor data
100: progress: updating all sensor data
101: progress: updating all sensor data
102: progress: updating all sensor data
103: progress: updating all sensor data
104: progress: updating all sensor data
105: progress: updating all sensor data
106: progress: updating all sensor data
107: progress: updating all sensor data
108: progress: updating all sensor data
109: progress: updating all sensor data
110: progress: updating all sensor data
111: progress: updating all sensor data
112: progress: updating all sensor data
113: progress: updating all sensor data
114: progress: updating all sensor data
115: progress: updating all sensor data
116: progress: updating all sensor data
117: progress: updating all sensor data
118: progress: updating all sensor data
119: progress: updating all sensor data
120: progress: updating all sensor data
121: progress: updating all sensor data
122: progress: updating all sensor data
123: progress: updating all sensor data
124: progress: updating all sensor data
125: progress: updating all sensor data
126: progress: updating all sensor data
127: progress: updating all sensor data
128: progress: updating all sensor data
129: progress: updating all sensor data
130: progress: updating all sensor data
131: progress: updating all sensor data
132: progress: updating all sensor data
133: progress: updating all sensor data
134: progress: updating all sensor data
135: progress: updating all sensor data
136: progress: updating all sensor data
137: progress: updating all sensor data
138: progress: updating all sensor data
139: progress: updating all sensor data
140: progress: updating all sensor data
141: progress: updating all sensor data
142: progress: updating all sensor data
143: progress: updating all sensor data
144: progress: updating all sensor data
145: progress: updating all sensor data
146: progress: updating all sensor data
147: progress: updating all sensor data
148: progress: updating all sensor data
149: progress: updating all sensor data
150: progress: updating all sensor data
151: progress: updating all sensor data
152: progress: updating all sensor data
153: progress: updating all sensor data
154: progress: updating all sensor data
155: progress: updating all sensor data
156: progress: updating all sensor data
157: progress: updating all sensor data
158: progress: updating all sensor data
159: progress: updating all sensor data
160: progress: updating all sensor data
161: progress: updating all sensor data
162: progress: updating all sensor data
163: progress: updating all sensor data
164: progress: updating all sensor data
165: progress: updating all sensor data
166: progress: updating all sensor data
167: progress: updating all sensor data
168: progress: updating all sensor data
169: progress: updating all sensor data
170: progress: updating all sensor data
171: progress: updating all sensor data
172: progress: updating all sensor data
173: progress: updating all sensor data
174: progress: updating all sensor data
175: progress: updating all sensor data
176: progress: updating all sensor data
177: progress: updating all sensor data
178: progress: updating all sensor data
179: progress: updating all sensor data
180: progress: updating all sensor data
181: progress: updating all sensor data
182: progress: updating all sensor data
183: progress: updating all sensor data
184: progress: updating all sensor data
185: progress: updating all sensor data
186: progress: updating all sensor data
187: progress: updating all sensor data
188: progress: updating all sensor data
189: progress: updating all sensor data
190: progress: updating all sensor data
191: progress: updating all sensor data
192: progress: updating all sensor data
193: progress: updating all sensor data
194: progress: updating all sensor data
195: progress: updating all sensor data
196: progress: updating all sensor data
197: progress: updating all sensor data
198: progress: updating all sensor data
199: progress: updating all sensor data
200: progress: updating all sensor data
shutting down sensor
progress: Preparing led message
progress: Sending led message
donuan:MacOS donuan$

Thanks!


#17

Hello, and welcome to the forums.

It’s quite weird that the sensor does not work via NI mate as the sensor test seems to run correctly. Did you perhaps unplug / replug the sensor between trying NI mate and the direct sensor test? Maybe the sensor will simply start working if you now start NI mate and try again? Sometimes these devices take a while to be detected or require themselves to be re-plugged for them to be properly noticed.

If the sensor does not work while NI mate is running, unplug the sensor, connect it to a different USB port, wait around half a minute and hit rescan on the setup page. Does this help?


#18

Hi Jesse and thanks for the reply.

I don’t know what was the problem but today it just works for some reason so I just bought it (I didn’t do anything different from what I tried yesterday), I guess some days are just like that :slight_smile:
Thanks!


#19

Hello, I am new to the ni mate world and I am having some problems…I own a mac pro late 2104 model/trash can model with two kinect sensors, both are v1414…I am running el capitan, and connected my sensors via usb, and they appear when I scan for sensors, but when I go to “use”, in the log I get an error:

Input 1: Error with USB open: Failed to open the USB device!.
21:17:16: Input 1: Starting live sensor: PrimeSense SensorKinect
21:17:16: Input 1: Error with creating sensor device: Failed to open the USB device!.
21:17:16: Input 1: startlive failed
21:17:16: Input 1: shutting down sensor
21:17:16: Input 1 quit normally.
21:18:04: Starting input 2: Kinect for Xbox
21:18:05: No MIDI ports available for output.
21:18:07: Input 1: Error with USB open: Failed to open the USB device!.

Read the faq’s and I’m totally lost…anyone run into this problem and can help fix it? I also have two sensors I’m trying to run in tandem, but even with only one plugged in it will not work…let me know, thanks!


#20

Hello!

We’ve heard some similar reports from other El Capitan users. A few quick reads online suggest that something has changed in how El Capitan detects USB devices and this might be related to the problem. Something you could try is to change the used libusb version:

  • Open the terminal
  • cd /Applications/Delicode_NI_mate.app/Contents/Frameworks
  • sh select_usb.sh -stable
  • Try running the sensor test:
  • cd /Applications/Delicode_NI_mate.app/Contents/MacOS/Delicode_Sensor_OpenNI
  • ./Delicode_Sensor_OpenNI sensor_test
  • If this does not work, revert back to the fast version of libusb:
  • cd /Applications/Delicode_NI_mate.app/Contents/Frameworks
  • sh select_usb.sh -fast

We’ll have to do some research into what exactly it is that’s broken with El Capitan. Meanwhile, we recommend that users remain in Yosemite.