question

TomihiroOno-4232 avatar image
0 Votes"
TomihiroOno-4232 asked TomihiroOno-4232 commented

How can I refresh Azure Kinect configurations when the factory reset button is not working?

Hi,

My main question is this:

What can I do to reset the Azure Kinect device when the LED seems to not be responding to the factory reset button? What does it even mean when the orange LED seems to never turn on?

I bought an Azure Kinect device and for a while was able to get it to work and do things via Unity. I am trying to put together something for a classroom teacher friend of mine to be used educationally. At some point, the device stopped being recognized by all three of my Windows computers ("Invalid Configuration Descriptor") while the device LED just blinks white. The Azure Kinect Microphone Array is read, but the Azure Kinect 4K Camera and Azure Kinect Depth Camera are not. I tried following the standard procedures, but when I tried to do a factory reset as recommended on the troubleshooting docs (https://docs.microsoft.com/en-us/azure/kinect-dk/troubleshooting#usb3-host-controller-compatibility), when I got to step 7 (https://docs.microsoft.com/en-us/azure/kinect-dk/reset-azure-kinect-dk) I saw that the LED on the back of the device did not change to orange. As it was not changing no matter how long I held the reset button, I released it, but the process did not solve the recognition issue.

Of note, I have tried using different USB ports, restarting the host PCs, uninstalling and updating devices from device driver, and changing the "Allow the computer to turn off this device to save power" settings for the USB root hubs. When I plug the kinect into a mac computer, both "Azure Kinect 4K Camera" and "Azure Kinect Depth Camera" are recognized (though I can't read from them), so it doesn't seem to be that the device is completely gone.

My USB 3.0 host controller is the Intel USB 3.0 eXtensible Host Controller 1.0, which as far as I can tell is one of the supported controllers. My main OS is Windows 10 Pro 64-bit 21H1 build 19043.1052. It runs an Intel (R) Core i3-3220 CPU @ 3.30 GHz with 16.0GB of RAM. My graphics card is a NVIDIA GeForce GTX 650 Ti, which is an older model but was working fine for a while until it stopped working. I don't know if it's relevant, but I have the Azure Kinect SDK v.1.4.1 installed right now.

Thanks in advance for your time.

azure-kinect-dk
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

SatishBoddu-MSFT avatar image
0 Votes"
SatishBoddu-MSFT answered TomihiroOno-4232 commented

Hello @TomihiroOno-4232,

As the device setup worked earlier, it is now strange that the device blinks white. As per the documentation, it states as below.

The flashing white===> Device is on but doesn't have a USB 3.0 data connection.

Reference: Doc link

109231-image.png


Was anything changed about the USB cable?

Flashing white means that the camera does not have a data connection to the host PC. Is the cable you are using a power+data capable or just power. Some USB-C cables are power only.
The blinking white LED indicates that the device is connected to a USB2 interface. It requires USB3. Can you please verify that you are connecting it to a USB3 interface? Please use the supplied cables. If can confirm you are using a USB3 interface and it still does not work then please test with an alternative USBA - USBC power+data cable or a USBC-USBC power+data cable.

Please also check the page on USB3 host controller compatibility

Please comment in the below section if you need further help in this regard.




image.png (24.5 KiB)
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @SatishBoddu-MSFT ,

Thank you for a detailed answer!

I have tried to connect the kinect setup (with the cable as-is from the original packaging) to other Windows computers and laptops, all to ostensibly valid USB 3.0 ports. In all of the computers I have tried, I get the same Invalid Configuration Descriptor warning and an Unknown kinect device. Thus, the issue does not seem to be that I am not accessing USB 3.0 ports.

As for the USB3 host controller compatibility, all of the devices I tried to get the kinect to work on had the same Intel USB 3.0 eXtensible Host Controller 1.0, which seems to be the same controller as the one shown in the page you provided. Thus, I am guessing the issue is not the host controller being incompatible.

I do not think I have changed anything about the cable, but that is one thing I have not tried. Do you have recommendations as to where I can procure a new data transfer cable, or could you provide me with the required specs for said new cable, if Microsoft has such cable specs outlined? Thank you.

0 Votes 0 ·

Hello @TomihiroOno-4232,
Please make sure to go through this Thread to get more info on the USB-Data cable importance.

Please make sure to use an Active USB Cable. Always be careful with USB cables and test your USB cables before you proceed to make use of them.

active USB - A cable that buffers the cable signal to provide signal quality.


We recommend this cable from B&H.

If the response is helpful, please click "Accept Answer" and upvote it so that it is helpful to other members as well.

0 Votes 0 ·

Hi @SatishBoddu-MSFT ,

Thanks for the recommendation! I will try to get my hands on the specified cable. In the meantime, I have tried swapping out the cable from the one that came with the original package to one that I had around, a USB-C 480mbps 3A to USB-A threaded nylon cable (Amazon link). It gives the same error on connection, which is to say that Windows cannot recognize the device (Invalid Configuration Descriptor). I would imagine the data transfer speed matters when streaming video, but in the enumeration of the device the data speed should not matter. Since swapping the cable did not change the identification error, I am beginning to wonder if it's more of an issue within the Kinect device.



0 Votes 0 ·
Show more comments