I'm working for an University of Applied Sciences and we want to buy some Kinects together with some PCs for future research as well as student projects and we are currently in a stage where we want to define which hardware to use.
We have a Kinect for Windows sensor and we are testing it with a Dell PC (Inspiron 15r 7520; Windows7 64bit, Intel i5-3210M #2.5GHz; 6GB RAM; USB 3.0).
We installed all the drivers for the 1.6 Version of the Kinect SDK but the PC only detects the Kinect camera once in a while.
In the device manger the "Kinect for windows Audio Array Control" and the "Kinect for Windows Security Control" show up but the "Kinect for Windows" Camera only shows up once in a while. If we plug and unplug the Kinect 10 (or 20 or 30 or 5) times the Camera is not detected 9 times. Then suddenly the camera is detected once and we are able to use it.
The next time we have to plug and unplug the camera 20 or 30 (or 2 or 5 or 10) times until the Camera is detected again. Then, we can plug and unplug the Camera 5 or 6 times and it is detected every single time.
Every time the camera is not detected a Windows USB Information (yellow triangle) pops up stating that a USB device was not detected.
We are quite sure that the Kinect sensor is not the problem because it works on 5 other PC without any problems. Then we thought about an USB Controller problem but after replacing the Mainboard and the USB Controller of the PC the error persists.
Are there any known PC - Kinect incompatibilities or can anybody think of a reason for this strange behavior?
Any help is greatly appreciated.
I'm not sure whether this includes recognising the camera, but there are known issues with certain USB host controllers and version 1.6. If you haven't already, take a look at this MSDN page under the "USB host controller compatibility" subheading.
It does mention two USB 3.0 controllers which are known to have issues. If you are using either the "Etron USB 3.0 Extensible Host Controller" or the "Renesas Electronics USB 3.0 Controller" you might have your answer.
Related
I am trying to connect Kinect 360 with Windows.
What I try:
I try to connect it with Windows 10 (64-bit) and Windows 8.1 (64-bit) (both ware host OS).
I downloaded and Installed the Software Development Kit (SDK).
I downloaded and installed the Kinect for Windows SDK v1.8.
I downloaded and installed the Kinect for Windows Developer Toolkit v1.8.
Then, I plug the Kinect 360 in the electric power and connect it with my Lap Top using the USB 3. I am using a power supply adapter cable for Xbox 360 Kinect Sensor (see the picture below).
As a result, no new hardware ware listed in the Device Manager like no new microphone, no new camera, no new unknown devices.
BTW I am not sure if the Kinect hardware is working at all. I don't know how to check it - there aren't any lighting lights on it. I did some research, but I didn't see any lights on working Kinect 360 on youtube videos. So I don't know how to test whether the Kinect is working (without connecting it with XBOX).
I want to connect the Kinect sensor with the PC machine because I need to do some tests. If there are other solutions with another OS (like Linux-based or MAC OS), I can try it too.
there was the same problem, it shows up as a microphone, I thought the problem was in the kinect itself (I thought it was broken) so it lay on the shelf for 2 years. I updated my PC 4 months ago and it turned out that there is usb 3.0 on my old motherboard, but it is not supported (perhaps 3.2 is needed for it). Now kinect works fine and is being determined
I am trying to get my Kinect running with my PC and therefore installed and updated all the drivers and the latest SDK.
Now when I connect the Kinect it is registered but only as an audio device. When the dialog on what to do with the device opens, the only option is "Kinect" which keeps "downloading" forever.
I have plugged it into the ss USB3 port and checked back every piece of hardware with a replacement.
My PC is rather new and running Windows 10 and both Kinects are around 3 years old
What could have gone wrong?
I am developing on an ARM Mbed board which connects to my Windows laptop over USB. I've just moved to a new Dell laptop running Win 10 [from a Dell laptop running Win 7] and I find that the laptop resets my development board every 15 minutes.
There are two things that will cause the ARM Mbed board to reset:
powering down/up the USB connection
sending "break" via the USB serial driver.
When the reset occurs there is nothing of note in the Windows event logs. I have all of the "allow Windows to power me down" boxes unticked on the USB hubs in System devices and in the Control Panel power management options.
Does anyone have any suggestions on how I (a) debug what's going on or (b) fix/workaround the problem? I've not yet tried connecting via a powered USB hub, will do that next...
I had the same issue using a FRDM-K64F running mBed and communicating over a USB COM port to a Windows 7 Dell machine. The communication would sometimes drop out. As #Rob suggested, uninstalling the Dell Support Assist Agent completely fixed the issue.
Just adding this answer as it was very difficult to find any information using google.
Another note in support of this solution for google...
I have a Dell 5480 running Windows 10, and started using from ST Nucleo boards on it. I've used the exact same boards at work, with no problems. Every 15minutes or so the board was reset.
I tried disabling the Dell Support Assist services but this did not seem to fix the problem.
Removing the programs did make the Nucleo work.
I'm working on a Kinect app, using a Kinect 2.0 for Xbox One on a Windows 10 PC. Now I have a problem using a new computer. Testing the Kinect with KinectStudio or any of the example programms, the Kinect keeps reconnecting frequently, as if you would pull out the usb cable and plug it in again.
If the Kinect is running I get the full 30 fps but mostly only for about 10 seconds before the connection is interrupted.
There is no other device plugged in at the usb 3 ports and I tried all of the ports. The computer has an Intel 8 Series/C220 Series USB Chipset and I updated and reinstalled all the drivers. The Kinect Configuration Verifier showes a problem with the usb Controller: "Supported USB 3.0 port detected with unknown bandwidth. Kinect may or may not be compatible with your hardware."
Did anyone experienced something similarly or do you have any idea how to fix it?
Your Kinect has to be attached to a 3.0 port that has its own pcie channel.
If the usb isn't built into the motherboard and you don't have a 3.0 without anything else on the channel, then you'll need to get a pcie to usb 3.0 addition for your motherboard.
When i go to my device manager i can't see my kinect device. I
downloaded the kinect SDK 1.6.
The "Kinect for Windows Device" that is supposed to show up there is the motor in the base of the Kinect, used for tilting the device up and down. While theoretically you don't need it, its absence in the Device Manager may be a curiosity that heralds trouble.
On two occasions where I and a friend have had similar problems (I was missing the Camera, and he was missing the Audio Array), we found the power plug to be the culprit. Make sure everything is connected properly. Try moving to a different the USB port and/or restarting the computer.
That said, what appears in the Device Manager does depend on your specific configuration. My Device Manager, on Win 8 x64 with the SDK 1.6 and an X-box Kinect, shows 4 nodes: the three that you have, plus the "Kinect for Windows Device." 'Meet the Kinect' by Kean, Hall and Kerry says you would have a "Microsoft Kinect Device", a "Microsoft Kinect Camera" and a "Microsoft Kinect Audio Array Control;" no "Security Control." Webb and Ashley's 'Beginning Kinect Programming...' shows the three nodes that you have as the correct ones, plus a "Kinect USB Audio" node under "Sound, video and game controllers."
So really, if your device works, don't worry.
Your screenshot is as it should be. You have the audio array listed and the cameras, which is all the Kinect is... a microphone and a pair of cameras. All the other "magic" is done on the software end, within the SDK.
You are not missing anything and should be able to develop applications with the Kinect.