question

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

Persistent Azure Kinect Crash

I've just migrated to windows specifically for this tech so excuse my ignorance, am not a coder but have been at this 2 days and have reached a real impasse.

Running Azure Kinect on Windows 10 on Razer Blade Stealth 13 (Specs below) and getting a repeated problem that causes the Kinect to fail ( with standard windows message following - the last USB device you connected to windows has malfunctioned AND WINDOWS DOES NOT RECOGNISE IT). This happens in Kinect Viewer and also when I try to open in DepthKit. Both have different faults (Logs below) but always involve LIBUSB_ERROR or references the DepthSensor (moreso in depthkit)

KINECT VIEWER FAULT

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 42ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 41ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 37ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 40ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 42ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 39ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 42ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 42ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 36ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 37ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 40ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 34ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 36ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 41ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 39ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 34ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 37ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 42ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 37ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 41ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 34ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 34ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 41ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 35ms (this may be transient).

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 39ms (this may be transient).

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for imu

[ warning ] : usb_cmd_libusb_cb(). USB timeout on streaming endpoint for depth

2020-07-30 (1)
2020-07-30 (2)
2020-07-30 (4)

DEPTHKIT FAULT

2020-07-30 15:09:40.794 [t=8188] ..\src\usbcommand\usbcommand.c (305): find_libusb_device(). Unable to open LIBUSB at index 0
2020-07-30 15:09:40.797 [t=8188] ..\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
2020-07-30 15:09:40.797 [t=8188] ..\src\sdk\k4a.c (133): depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()
2020-07-30 15:09:40.799 WARN [8188] [Depthkit::IO::DepthSensor::DepthSensorAzureKinect::getConnectedDevices@257] : Failed to open device

From googling the issue I can see that LIBUSB refers to bandwidth of the USB connection, which was never an issue before. It was working earlier today and nothing has changed in terms of hardware etc. I tried updatng drivers of USB to no avail. It does come up under Generic USB Superspeed Hub which I gather is just a standard USB function in windows.

Current Firmware Versions:
RGB camera firmware: 1.6.110
Depth camera firmware: 1.6.79
Depth config file: 6109.7
Audio firmware: 1.6.14
Build Config: Production
Certificate Type: Microsoft

The Firmware was updated last week, and there has been a release since, but now every time I try to update it gives me one of two errors -

EITHER

[2020-07-30 17:47:13.697] [critical] [t=4780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (366): find_libusb_device(). libusb device(s) are all unavalable. Is the device being used by another application?
2020-07-30 17:47:13.698 [t=4780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (68): usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()
2020-07-30 17:47:13.698 [t=4780] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\firmware\firmware.c (128): depthmcu_create(device_index, &firmware->depthmcu) returned failure in firmware_create()

OR...

Please wait, updating device firmware. Don't unplug the device. This operation can take a few minutes...
2020-07-30 17:56:54.666 [t=6892] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (689): usb_cmd_io(). Error calling libusb_bulk_transfer for tx, result:LIBUSB_ERROR_PIPE
2020-07-30 17:56:54.668 [t=6892] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (900): usb_cmd_io(usbcmd_handle, cmd, p_cmd_data, cmd_data_size, NULL, 0, p_data, data_size, NULL, &cmd_status) returned failure in usb_cmd_write()
2020-07-30 17:56:54.668 [t=6892] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (435): usb_cmd_write( depthmcu->usb_cmd, DEV_CMD_DOWNLOAD_FIRMWARE, (uint8_t *)&info, sizeof(info), firmwarePayload, firmwareSize) returned failure in depthmcu_download_firmware()
2020-07-30 17:56:54.668 [t=6892] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\firmware\firmware.c (255): depthmcu_download_firmware(firmware->depthmcu, pFirmwareBuffer, firmwareSize) returned failure in firmware_download()
ERROR: Downloading the firmware failed! 1

I did get past this before last week but cant remember. It should be able to handle the Azure Kinect, and has until now. I havent tried factory reset on azure as i know you are limited to one. Any help please, I have invested so much time and money in this kit only to be stumped now. Thanks in advance!

Computer specs below -

16911-88952656-a2b2bb00-d28f-11ea-9cce-4f0a3f28666e.png



Im now getting these errors

[ warning ] : is_fw_version_compatable(). Firmware version for RGB is 1.6.102. Consider upgrading to 1.6.110 or newer.

[ warning ] : is_fw_version_compatable(). Firmware version for Depth is 1.6.75. Consider upgrading to 1.6.79 or newer.

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 39ms (this may be transient).

[ warning ] : imu_capture_ready(). A streaming IMU transfer failed

[ warning ] : depth_engine_thread(). Depth image processing is too slow at 41ms (this may be transient).

[ warning ] : capturesync_add_capture(). Capture Error Detected, Color

[ warning ] : color_capture_available(). A streaming color transfer failed

[ warning ] : color_capture_available(). A streaming color transfer failed


I do need to update firmware but real chicken and egg, did factory reset and tentatively worked so afraid to do anything - really at wits end. Is there anything i can do about processing or about usb controller ?

azure-kinect-dk
· 1
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 @RobbyGraham-6684

Our setups are similar. Razer + Azure Kinect.
Did you find a solution to this? I am getting similar errors + camera flickering.

None of the mentioned solutions worked so far.

0 Votes 0 ·

1 Answer

asergaz avatar image
0 Votes"
asergaz answered TomihiroOno-4232 commented

Hello @RobbyGraham-6684 , sorry to hear that you are struggling getting things ready with Azure Kinect DK. Let me ask some quick questions and suggest possible solutions to your case:


I havent tried factory reset on azure as i know you are limited to one

Can you share where you read it? Was it from the official documentation here? https://docs.microsoft.com/en-us/azure/kinect-dk/ .

1) Actually the suggestion is exactly that you perform a factory reset if firmware update is interrupted and\or got into bad state and fail to enumerate.
2) Please check the Azure Kinect Troubleshooting doc and confirm if you followed all the steps there?

Thank you! Hope we can get you ready asap.

· 6
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.

@RobbyGraham-6684 Just checking back, could you please let us know if you need further help in this matter.

0 Votes 0 ·

@RobbyGraham-6684 Are you able to follow the suggestions? Do let us know if that helps to resolve the issue?

1) Actually the suggestion is exactly that you perform a factory reset if firmware update is interrupted and\or got into bad state and fail to enumerate.
2) Please check the Azure Kinect Troubleshooting doc and confirm if you followed all the steps there?

0 Votes 0 ·

I am having the same problem, and I have progressed to the 6th step of the factory initialization manual, but I am not able to enter the 7th step (the power indicator turns yellow after 3 seconds).
Currently, I have checked with 2 Azure Kinects and 2 PCs, but both have the same symptoms.


The following is the log in the viewer.


[ error ] : find_libusb_device(). Unable to open LIBUSB at index 0

[ error ] : usb_cmd_create(USB_DEVICE_DEPTH_PROCESSOR, device_index, NULL, &depthmcu->usb_cmd) returned failure in depthmcu_create()

[ error ] : depthmcu_create(index, &device->depthmcu) returned failure in k4a_device_open()

0 Votes 0 ·

I am having the same issue, in which I follow the factory reset steps in the official docs but the LED does not turn amber for step 7. The connection errors remain unresolved, so I am assuming that the factory reset (just like the light turning amber) simply did not happen. What do you recommend when the device itself seems to not be responding to factory reset? Do I need to open the device itself?

1 Vote 1 ·

I am also not getting the amber color ://
Were you able to find something?

Best,

0 Votes 0 ·
Show more comments