OK so back to our motor. We are ready to start sending data to it via the Control endpoint. For Mac and Linux type computers, a driver isn't necessary to send or receive data directly via USB.

For windows, however, there must be some sort of driver to 'grab' the device for us. Usually drivers are complex and have like, interfaces that plug into the operating system. Like the cameras would show up as a camera device, the microphones as an audio device. We're not quite ready for a detailed driver, what we'll do is make a 'shell driver' which has no operating system capabilities but does let us send commands to it from software.

Again, Mac/Linux people have this built into the OS kernel so skip this part if you don't use windows.

For our shell, we'll use libusb a USB library, which is available for windows as libusb-win32 go there and download it.

We'll run the inf-wizard (which will make our driver shell)

The important part is entering in the matching VID and PID we found before.
Now when you plug in the Kinect, it will attach itself the the LibUSB-win32 device driver.
We didn't make matching drivers for the audio or camera so those are still driver-less.

This guide was first published on Jul 29, 2012. It was last updated on Jun 13, 2012.

This page (Making a Driver) was last updated on Jun 13, 2012.

Text editor powered by tinymce.