Sending a vendor-specific setup packet read request (0xC2) with zeros for the request, value, and index and 0x02 for the length returns 0x80. The Motor has only a single control endpoint on 0x00.
After the driver for the Motor is installed/activated, Kinect displays a flashing green light and the other devices connect to the internal USB hub.
It also seems to control power to the rest of the Kinect devices. The Motor device controls the actual motor for tilting/panning the Kinect. Until analysis is done on the USB protocol exchange between the Xbox and Kinect, controlling or getting data from Kinect is likely not possible. There were a few interesting bits, documented below. He attempted to send vendor-type setup packets with various values for other parameters but it was mostly non-productive. Josh was able to send standard USB requests and get appropriate responses from all three devices. It appears that starting the Motor device also controls power to the rest of Kinect.Īfter the Audio and Camera devices were powered on, Josh also generated boilerplate drivers for them. At this point it is waiting for the Xbox to boot up and probably for a handshake protocol or other command to activate the devices. The flashing green light is consistent with the standard Kinect startup process.
The Kinect device started flashing green on the indicator light.When he generated and installed the driver for the Xbox NUI Motor, the following happened: Josh Blake tested creating boilerplate drivers using a Jungo WinDriver USB trial. At this point, the Kinect still looks to be powered off. The Motor obviously does not have drivers, so the PnP configuration fails and the device is not started.
When you plug the Kinect to a PC running Windows, it finds the Generic USB Hub and the Xbox NUI Motor. This indicates that using it as a plug-and-play webcam or microphone is probably not possible. The devices do not conform to any standard USB class such as HID, camera, or audio devices.
Try installing the program again using the original installation media or contact your system administrator or the software vendor for support.Kinect has the following USB devices connected through its USB cable: (Code 39) %hs is either not designed to run on Windows or it contains an error. (R) click and then clicking Properties gives me the following message "Windows cannot load the device driver for this hardware. In Device Manager, there is a yellow warning triangle against Kinect for Windows Camera. Skanect says it is detecting sensor, but when I close the message from Kinect, Skanect that the sensor is unavailable. Firstly I get a message from Kinect saying failed to initialise the sensor. When I start Kinect Studio v 1.8, I am told that I need to be connected to a Kinect-enabled app. I have followed your instructions for SDK v 1.7 and v 1.8 using the correct drivers.
Hi Pieter I have a Win 10 64 bit O/S, 16 Gb Memory, Gigabyte Aorus Geforce GTX 1080 ti Xtreme edition 11gb and a Kinect Xbox 360 sensor model # 1414. And that, surprisingly, is sometimes a frustrating exercise. The plethora of new functions requires a lot of exploring and experimenting which can start as soon as your Kinect has been connected to your Windows computer. That is very interesting for a device with a second hand street price of USD 25! The most striking one is 3D scanning in a user friendly way. The Kinect happened to be a versatile device that, connected to your Windows computer, offers an array of new functions. Instead they used a dedicated camera system, called Kinect, that could do the job without remotes. Later Microsoft added motion control to its XBox360 game console as well. Nintendo's Wii game console introduced motion control to games via wireless remote controls.
We describe how to connect a Kinect to your Windows PC. Originally it was launched as an extension to the Xbox game console. Microsoft's Kinect is a versatile multimedia input device that can be used as a 3D scanner.