saogden
commented
5 years ago When this happens in windows, the device will still enumerate in device manager, 1354 warnings will also show in the event log for applications.
Open Brent-A opened 5 years ago
saogden
commented
5 years ago When this happens in windows, the device will still enumerate in device manager, 1354 warnings will also show in the event log for applications.
Example output with power cable disconnected
C:\Program Files\Azure Kinect SDK\tools\amd64\release>AzureKinectFirmwareTool.exe -l == Azure Kinect DK Firmware Tool == Found 1 connected devices: [2019-03-02 08:09:58.645] [error] [t=23232] [K4A] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\usbcommand\usbcommand.c (306): find_libusb_device(). Unable to open LIBUSB at index 0 [2019-03-02 08:09:58.647] [error] [t=23232] [K4A] 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() ERROR: 0: Failed to open device [2019-03-02 08:09:58.647] [error] [t=23232] [K4A] Invalid depthmcu_t 0000000000000000 [2019-03-02 08:09:58.647] [error] [t=23232] [K4A] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (101): Invalid argument to depthmcu_get_serialnum(). depthmcu_handle (0000000000000000) is not a valid handle of type depthmcu_t ERROR: 0: Failed to get serial number length [2019-03-02 08:09:58.648] [error] [t=23232] [K4A] Invalid depthmcu_t 0000000000000000 [2019-03-02 08:09:58.648] [error] [t=23232] [K4A] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\depth_mcu\depth_mcu.c (87): Invalid argument to depthmcu_destroy(). depthmcu_handle (0000000000000000) is not a valid handle of type depthmcu_t