LG USB Drivers Ver. 4.5.0 and LG USB Drivers Ver 4.4.2 In this post, you can download and install the latest LG USB Drivers Ver 4.5.0 for your LG Phones or tablets. In order to establish communications between your LG devices and computer, you need to install the latest LG Drivers properly onto your computer. .Device must be using Android 4.4 or higher and support USB host mode. A USB OTG (“On the Go”) cable is required to connect OBDLink EX (not included with purchase). Before purchasing EX for use with an Android, make sure phone or tablet meets these requirements. Usb driver download - Best answers Download usb driver - Best answers Spvd-012.1 usb driver for windows 10 - Forum - Drivers.

Important

This topic is for programmers. If you are a customer experiencing USB problems, see Troubleshoot common USB problems

This topic lists the Microsoft-provided drivers for the supported USB device classes.

Gfm Usb Devices Drivers

• Microsoft-provided drivers for USB-IF approved device classes.
• For composite devices, use USB Generic Parent Driver (Usbccgp.sys) that creates physical device objects (PDOs) for each function.
• For non-composite devices or a function of a composite device, use WinUSB (Winusb.sys).

If you are installing USB drivers: You do not need to download USB device class drivers. They are installed automatically. These drivers and their installation files are included in Windows. They are available in the WindowsSystem32DriverStoreFileRepository folder. The drivers are updated through Windows Update.

If you are writing a custom driver: Before writing a driver for your USB device, determine whether a Microsoft-provided driver meets the device requirements. If a Microsoft-provided driver is not available for the USB device class to which your device belongs, then consider using generic drivers, Winusb.sys or Usbccgp.sys. Write a driver only when necessary. More guidelines are included in Choosing a driver model for developing a USB client driver.

USB Device classes

USB Device classes are categories of devices with similar characteristics and that perform common functions. Those classes and their specifications are defined by the USB-IF. Each device class is identified by USB-IF approved class, subclass, and protocol codes, all of which are provided by the IHV in device descriptors in the firmware. Microsoft provides in-box drivers for several of those device classes, called USB device class drivers. If a device that belongs to a supported device class is connected to a system, Windows automatically loads the class driver, and the device functions with no additional driver required.

Hardware vendors should not write drivers for the supported device classes. Windows class drivers might not support all of the features that are described in a class specification. If some of the device's capabilities are not implemented by the class driver, vendors should provide supplementary drivers that work in conjunction with the class driver to support the entire range of functionality provided by the device.

For general information about USB-IF approved device classes see the USB Common Class Specification

The current list of USB class specifications and class codes is documented in the USB-IF Defined Class Code List.

Device setup classes

Windows categorizes devices by device setup classes, which indicate the functionality of the device.

Microsoft defines setup classes for most devices. IHVs and OEMs can define new device setup classes, but only if none of the existing classes apply. For more information, see System-Defined Device Setup Classes.

Two important device setup classes for USB devices are as follows:

• USBDevice {88BAE032-5A81-49f0-BC3D-A4FF138216D6}: IHVs must use this class for custom devices that do not belong to another class. This class is not used for USB host controllers and hubs.

• USB {36fc9e60-c465-11cf-8056-444553540000}: IHVs must not use this class for their custom devices. This is reserved for USB host controllers and USB hubs.

The device setup classes are different from USB device classes discussed earlier. For example, an audio device has a USB device class code of 01h in its descriptor. When connected to a system, Windows loads the Microsoft-provided class driver, Usbaudio.sys. In Device Manager, the device is shown under is Sound, video and game controllers, which indicates that the device setup class is Media.

Microsoft-provided USB device class drivers

Related topics

Notice: MediaWiki has been updated. Report any rough edges to marcan@marcan.st

Here's what we know about the USB devices.

• 4Xbox NUI Motor
  • 4.3Confirmed Information
• 5Xbox NUI Audio
• 6Xbox NUI Camera

Devices

Kinect has the following USB devices connected through its USB cable:

• Generic USB Hub
  • Xbox NUI Audio
  • Xbox NUI Motor
  • Xbox NUI Camera

The devices do not conform to any standard USB class such as HID, camera, or audio devices. This indicates that using it as a plug-and-play webcam or microphone is probably not possible.

Plugging in Kinect

When you plug the Kinect to a PC running Windows, it finds the Generic USB Hub and the Xbox NUI Motor. The Motor obviously does not have drivers, so the PnP configuration fails and the device is not started. At this point, the Kinect still looks to be powered off.

Josh Blake tested creating boilerplate drivers using a Jungo WinDriver USB trial. When he generated and installed the driver for the Xbox NUI Motor, the following happened:

• The Kinect device started flashing green on the indicator light.
• The Xbox NUI Audio and Xbox NUI Camera devices became available on the USB hub (also with no drivers initially)

The flashing green light is consistent with the standard Kinect startup process. 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.

It appears that starting the Motor device also controls power to the rest of Kinect.

After the Audio and Camera devices were powered on, Josh also generated boilerplate drivers for them.

Talking to Kinect

Josh was able to send standard USB requests and get appropriate responses from all three devices.

He attempted to send vendor-type setup packets with various values for other parameters but it was mostly non-productive. There were a few interesting bits, documented below.

Until analysis is done on the USB protocol exchange between the Xbox and Kinect, controlling or getting data from Kinect is likely not possible.

Gfm Usb Devices Driver Vga

Xbox NUI Motor

The Motor device controls the actual motor for tilting/panning the Kinect. It also seems to control power to the rest of the Kinect devices. 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.

Endpoints

The Motor has only a single control endpoint on 0x00.

Data Experiments

Sending a vendor-specific setup packet read request (0xC2) with zeros for the request, value, and index and 0x02 for the length returns 0x80. This might indicate the current position of the motor as 0x80 is the middle of possible values (0x00 to 0xFF) and would be a good initial position for the motor.

Sending a vendor-specific setup packet write request (0x02) with a request of 0x00 and zeros for the value, index, and length resulted in (need to double check but it was a no-op, as opposed to an error)

Sending a vendor-specific setup packet write request (0x02) with a request of 0x01 and zeros for the value, index, and length resulted in the Motor device immediately disconnecting from the USB port, effectively resetting it.

Confirmed Information

The joint range of the Kinect motor is +31 degrees (up) and -31 degrees (down).

Setting Joint Position

The joint position can be set by sending:

Setting LED

The led can be set by sending:

where the led_options are enumerated as follows:

Reading Joint State

The joint state information is grouped in with the accelerometer data and is stored in the 1st, 8th and 9th byte of the return from:

the 1st byte (buf[1]) yields:

the 8th byte (buf[8]) yields:

the 9th byte (buf[9]) yields the following status codes:

Reading Accelerometer

The accelerometer data is stored in two byte pairs for x,y, and z:

The Accelerometer documentation (http://www.kionix.com/Product%20Sheets/KXSD9%20Product%20Brief.pdf) states there are 819 counts/g

Xbox NUI Audio

The Audio device provides combined audio from Kinect's four microphones. It also provides hardware noise cancellation by subtracting the TV's game audio and accounting for the 3D layout of the room.

Endpoints

The Audio device has several endpoints, the purpose of which is not yet clear. They provide enough bandwidth for full audio both in and out of the device. This supports the hardware noise processor and feeding game audio to Kinect for processing purposes only.

In addition to the default 0x00 control endpoint, the Audio device has:

• Endpoint 0x81 - IN, Bulk, 512 bytes
• Endpoint 0x01 - OUT, Bulk, 512 bytes
• Endpoint 0x82 - IN, Isochronous, 524 bytes
• Endpoint 0x02 - OUT, Isochronous, 72 bytes

Note that IN and OUT are relative to the USB host. OUT means sending data from the Xbox (or your computer) to Kinect.

Xbox NUI Camera

The most interesting and useful device, the Camera provides both an RGB and a depth map image.

Endpoints

The Camera device has two endpoints. Presumably, one of these provide the RGB image data and the other provides depth map data.

In addition to the default 0x00 control endpoint, the Camera device has:

• Endpoint 0x81 - IN, Isochronous, 1920 bytes (color camera)
• Endpoint 0x82 - IN, Isochronous, 1760 bytes (depth camera)

Note that the packet size is not large enough to fit an entire image at either 320x240 or 640x480, so a single frame will have to be transmitted and reconstituted from multiple frames. This also implies there may be some packet headers to help combine the image.

Interestingly, 1920 divided by 320 is 6, so without a header a single packet could contain 3 16-bit rows, and 80 packets would be required for a single 320x240 16-bit frame.

Data Experiments

Sending any vendor-specific setup packets, both read (0xC2) or write (0x02) results in a timeout, requiring resetting the device.

Josh suspects that a handshake protocol has to occur, possibly with the Motor device, before the other devices will respond. Alternately, the camera might respond to a class setup packet or a non-standard setup packet type.