- This topic has 40 replies, 30 voices, and was last updated 6 months, 4 weeks ago by
.
-
If you have trouble connecting to your Kinect device, for example, if KinectUtil or RawKinectViewer keep terminating with an error similar to the following one:
terminate called after throwing an instance of ‘std::runtime_error’ what(): Kinect::Camera::Camera: Less than 0 Kinect camera devices detected Abortedthen your PC might have a bad USB host controller.
First, check if your Kinect is plugged into a USB 3.0 or a USB 2.0 port. From a terminal, run
lsusband look for a line like the following:Bus 001 Device 014: ID 045e:02ae Microsoft Corp. Xbox NUI CameraInstead of “NUI Camera,” you might get “NUI Audio” or “NUI Motor,” and the bus and device numbers depend on your local setup. Note down the bus number you see, and then look for a line indicating a root hub with the same bus number, and device number 1, in the output from
lsusb. In my case:Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubThis indicates that my Kinect is plugged into a USB 2.0 bus. For USB 3.0, you would see:
Bus 001 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubIf your Kinect is on USB 3.0, try plugging it into a USB 2.0 port. Confirm via the above method that the port you found really is USB 2.0.
If your PC does not have USB 2.0 ports, of if the problem persists even on USB 2.0, you will have to buy and install a PCI express USB 3.0 extension card. I have successfully been using this no-name card, for USD 11.30 plus shipping, to run multiple Kinects at the same time.
The important thing to look out for is that the USB extension card is based on a USB controller chip from NEC or Renesas Technology Corp., chip models “uDP720200″ or “uDP720202” or similar. When installing the card, you must connect the power plug on the back of the card to your PC’s power supply unit.
If you want to find out the chip type of your current USB 3.0 host controller, run the following from a terminal:
lspci | grep "USB 3.0"In my case, the output is:
06:00.0 USB controller: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)Hi, having a big problem getting the Kinect to be recognized. The light comes on and flashes briefly when the Kinect is first plugged in then goes off. I’ve tried it in USB 2 and 3 ports and have the same outcome:
terminate called after throwing an instance of 'std::runtime_error' what(): Kinect::Camera::Camera: Less than 0 Kinect camera devices detectedI then bought a PCIe USB3 card with an NEC chip as recommended, plugged in the extra power connector and still get the same error. The Kinect is model 1414 and has an original power supply. the Kinect works fine under Windows with the official SDK. The output of lsusb is as follows when connected to the PCIe card:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 009: ID 045e:02b0 Microsoft Corp. Xbox NUI Motor Bus 003 Device 008: ID 0409:005a NEC Corp. HighSpeed Hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04d9:2519 Holtek Semiconductor, Inc. Shenzhen LogoTech 2.4GHz receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubThe lspci output:
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 03:00.0 USB controller: Renesas Technology Corp. uPD720201 USB 3.0 Host Controller (rev 03)Anyone have any other ideas on what else I could try? Thanks.
- You must be logged in to reply to this topic.
