-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to set the LED of K4W or 1473 device: LIBUSB_ERROR_IO #580
Comments
I have this problem too. Do you have any answers? |
I have this problem as well:
|
Mine works after trying this solution from another answer (#543): "Please try freenect-camtest, which uses only the camera. |
So, Can't we open Kinect 1473 through OpenCV? |
Me too! |
What did it for me, was running |
This worked for me! thanks a lot! |
When I run
any help is appreciated. |
The file
This will download the audio.bin to the libfreenect folder, then simply move it to the location of the installed libfreenect library
|
This worked for me! thanks a lot! |
I have also the model 1473 (I did not know where to get this info: it's depicted in the sticker on the foot of the device) and I had the same error
EDIT: today I wanted to retry tests but I got this error similar to #650:
I tried to call back
I did not understood but my hypothesis is that I shall be |
Update. On my Ubuntu I got this error again. This is because I was inside the build folder. After doing |
If anyone is still checking this thread... I am attempting to run Would anyone know where I can manually download the files or update.zip that |
please help me i am very urgent
i am trying to connect my kinect 1517 to ubuntu 18.04
i downloaded libfreenect and everything, and if i try to execute freenect-glview
i keep getting this error.
freenect-glview Kinect camera test Number of devices found: 1 Found sibling device [same parent] Failed to set the LED of K4W or 1473 device: LIBUSB_ERROR_IO Found sibling device [same parent] Could not open device: LIBUSB_ERROR_NO_DEVICE Could not open device
maybe it's because of the usb problem?
because i don't have any usb bus 003 when i execute lsusb -t
anyways please help me
i searched everywhere, but i wasn't able to find the answer...
please help me..
The text was updated successfully, but these errors were encountered: