You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Driver for Kinect for Windows v2 (K4W2) devices (release and developer preview).
11
5
@@ -14,14 +8,46 @@ Note: libfreenect2 does not do anything for either Kinect for Windows v1 or Kine
14
8
This driver supports:
15
9
* RGB image transfer
16
10
* IR and depth image transfer
11
+
* registration of RGB and depth images
17
12
18
13
Missing features:
19
-
* registration of RGB and depth images
20
14
* audio transfer
21
15
* firmware updates
22
16
23
17
Watch the OpenKinect wiki at www.openkinect.org and the mailing list at https://groups.google.com/forum/#!forum/openkinect for the latest developments and more information about the K4W2 USB protocol.
24
18
19
+
## FAQ
20
+
21
+
### Can I use the Kinect v2 without an USB3 port?
22
+
23
+
No. It's a pure USB3 device due to the high bandwidth requirements.
24
+
25
+
### Protonect complains about "no device connected" or "failure opening device".
26
+
27
+
Either your device is connected to an USB2-only port (see above), or you don't have permissions to access the device. On Linux, try running Protonect as root (e.g. using `sudo`). If that fixes things, place `contrib/90-kinect2.rules` into `/etc/udev/rules.d/` and re-plug the device.
28
+
29
+
### I'm getting lots of USB transfer errors, and/or only blank windows.
30
+
31
+
USB3 as a whole is a flaky thing. If you're running Linux, try upgrading to a recent kernel (>= 3.16) first. If that doesn't work, try a different USB3 controller. The following ones are known to work on a 3.16 kernel:
32
+
* Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI
33
+
* Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI
34
+
* NEC Corporation uPD720200 USB 3.0 Host Controller
35
+
36
+
Probably not working:
37
+
* ASMedia Technology Inc. Device 1142
38
+
39
+
Finally, it's also possible that your executable is not actually using the patched libusb from the depends/ folder which is required at the moment. Check this using `ldd`, and adjust your `LD_LIBRARY_PATH` if necessary.
40
+
41
+
### I'm seeing the color camera stream, but no depth/IR (black windows).
42
+
43
+
The depth packet processor runs on OpenGL by default. You can try alternatives, such as OpenCL (by running `Protonect cl`) or CPU (`Protonect cpu`). At least the CPU DPP should always produce some output, although slow. For OpenCL on Intel/Linux, you can also try to set `/sys/module/i915/parameters/enable_cmd_parser` to 0.
0 commit comments