This section describes the enumeration process on the Universal Serial Bus.
When a device is plugged in to a Windows-based computer, the Windows USB stack enumerates the device, extracting details from the device including the interface descriptor (or descriptors) of the device, and then generates a set of hardware IDs and compatible IDs for the device.
DPC-11 Universal Programming Interface for Hitec Programmable Servos Installation Instructions & Software Download. Driver Installation Troubleshooting. DPC-10 Brushless Servo PC Programming Interface Windows® XP and 32bit Versions of Windows® 7, 8 or 8.1 - Installation instructions Software. Like wired and wireless networking drivers, USB 3.0 drivers are a staple of any Windows 10 installation and should be present and correct when you switch to the operating system for the first time. However, upgrades to Windows 10 from Windows 7 or Windows 8.1, as well as updates to the latest version of Windows, can sometimes cause conflicts. USB IDs for a multi-interface (composite) USB device; Example 1: Single Interface HID USB Device. This example shows how the hardware IDs and compatible IDs are generated for a single-interface USB device on a system running Windows 2000 or Windows XP. When the device is originally enumerated by the USB stack, the USBHUB driver extracts. It's not a new driver for Windows 8, it's just that Hitec found this driver worked with Windows 8. If you use it you have to follow the instructions on its use (2nd link on FLO) otherwise, once installed, Windows will try to update it to a driver that doesn't work. This high speed, opto-isolated, PC USB interface module is designed to provide safe, 2-way communication between Revolectrix products and a PC USB port. For use with free PC software, supports firmware updates, and PC compatible GUI software for Revolectrix Chargers and Battery Management Systems, Co-Pilot II Flight Stabilization systems.
For a complete list of USB hardware IDs, see the 'Device Identification Strings' section under Device Installation.
The examples in the following sections illustrate two scenarios:
Example 1: Single Interface HID USB Device
This example shows how the hardware IDs and compatible IDs are generated for a single-interface USB device on a system running Windows 2000 or Windows XP.
When the device is originally enumerated by the USB stack, the USBHUB driver extracts idVendor, idProduct, and bcdDevice from the device descriptor. These three fields are incorporated to generate a USB hardware ID. Note that the vendor, device, and revision numbers are always stored in hexadecimal format.
The generation of the compatible ID for the device is more complicated. The class code, subclass code, and protocol code are determined by the interface descriptor's bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol. These values are in two-digit hexadecimal format.
Note If you are providing an INF, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)
Hitec Usb Interface Drivers
Hardware Identifiers: Compatible Identifiers
USBVid_xxxx&Pid_yyyy&Rev_zzzz: USBClass_aa&SubClass_bb&Prot_cc
USBVid_xxxx&Pid_yyyy: USBClass_aa&SubClass_bb
****: USBClass_aa
Example 2: Multiple Interface/Function HID USB Device (Composite Device)
USB devices with multiple functions are called composite devices. This example shows how the hardware IDs and compatible IDs are generated for composite USB devices on Windows. When a new USB composite device is plugged into a computer system running Windows, the USBHUB driver creates a physical device object (PDO) and notifies the operating system that its set of child devices has changed. After querying the hub driver for the hardware IDs associated with the new PDO, the system searches the appropriate INF files to find a match for the identifiers. If a vendor chooses to load just one driver for the entire device (that is, not using the composite device driver) and multiplex all interfaces in software with that driver, the vendor should specify a hardware ID match to prevent the operating system from picking up the lower-ranking match (USBCOMPOSITE).
Note If you are providing an INF, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)
Hardware Identifiers: Compatible Identifiers
USBVid_xxxx&Pid_yyyy&Rev_zzzz: USBClass_aa&SubClass_bb&Prot_cc
USBVid_xxxx&Pid_yyyy: USBClass_aa&SubClass_bb
****: USBClass_aa
****: USBCOMPOSITE
If, however, no hardware match is found, Windows Plug and Play makes use of the USBCOMPOSITE identifier to load the USB Generic Parent driver (USBCCGP). The Generic Parent driver then creates a separate set of PDOs (one for every interface) with a separate set of hardware IDs for each interface of the composite device. The following section displays the format of hardware IDs for child PDOs.
To build the set of hardware IDs for each interface’s PDO, the USBCCGP driver appends the interface number (which is a zero-based hexadecimal value) to the end of the hardware ID.
The class code, subclass code, and protocol code are determined by the bInterfaceClass, bInterfaceSubClass, and bInterfaceProtocol fields of the interface descriptor, respectively. These values are in two-digit hexadecimal format.
Note If you are providing an INF, either to load your driver or to provide a friendly device name, your hardware identifiers should match the bold identifiers in the left column of the following table. (You should avoid using the compatible identifiers listed in the right column.)
Hardware Identifiers: Compatible Identifiers
USBVid_xxxx&Pid_yyyy&Rev_zzzz&MI_ww: USBClass_aa&SubClass_bb&Prot_cc
Hitec Usb Interface Driver Installer
USBVid_xxxx&Pid_yyyy&MI_ww: USBClass_aa&SubClass_bb
****: USBClass_aa
Overview
The S2USB485 is a USB to full-duplex RS-232 and half-duplex RS-485 serial converter integrated into a single device. In essence the S2USB485 is a single USB serial port that has two electrical interfaces available to it (RS-232 and RS-485). Either interface can be used without the need to set jumpers or change dip switch settings. Details
The S2USB485 can be used as a replacement to the Johnson Controls MM-CVT101 (RS-232 to N2 Bus) / CVTPro100 converter for those computers or laptops that have a USB interface. In addition to direct support for Johnson Controls software (Metasys, HVAC Pro, etc), the S2USB485 provides the following improved features and functionality:
Dead rising 2 pc product key generator.
Specifications
Hitec Usb Interface Driver Updater
Hitec Usb Interface Driver SoftwareComments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |