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
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,9 @@ No. It's a pure USB3 device due to the high bandwidth requirements.
24
24
25
25
### Protonect complains about "no device connected" or "failure opening device".
26
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.
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 `rules/90-kinect2.rules` into `/etc/udev/rules.d/` and re-plug the device.
28
+
29
+
On Mac OS X, open "System Information" from Spotlight, go to the USB section, and verify "Xbox NUI Sensor" is under "USB 3.0 SuperSpeed Bus" not "High-Speed Bus". If this is not the case, try unplugging the Kinect from power source with the USB cable connected, and plug the power again, then verify.
28
30
29
31
### I'm getting lots of USB transfer errors, and/or only blank windows.
30
32
@@ -36,7 +38,7 @@ USB3 as a whole is a flaky thing. If you're running Linux, try upgrading to a re
36
38
Probably not working:
37
39
* ASMedia Technology Inc. Device 1142
38
40
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.
41
+
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 | grep libusb` (shows libusb-1.0 under `depends/`), and adjust your `LD_LIBRARY_PATH` if necessary.
40
42
41
43
### I'm seeing the color camera stream, but no depth/IR (black windows).
42
44
@@ -87,7 +89,7 @@ You can go back and forth between the SDK driver and the libusbK driver very qui
0 commit comments