Устройства HID Human Interface Devices Windows 10
Привет ! Мы продолжаем разбирать операционную систему Windows 10 ! Сегодня вы узнаете как настроить на своём компьютере устройства HID (Human Interface Devices). Вы сможете узнать тип и состояние устройства, сможете обновить драйвера, узнать характеристики и свойства и т.д.
Чтобы открыть параметры устройства, внизу экрана слева откройте меню “Пуск”. В открывшемся окне нажмите на вкладку или значок – Параметры .
Далее, на странице “Параметры” нажмите на вкладку – Устройства .
Далее, на странице “Устройства”, внизу страницы, нажмите на вкладку – Диспетчер устройств .
Далее, на странице устройств нажмите два раза на вкладку – Устройства HID (Human Interface Devices) . У вас откроются вложения. Нажмите два раза по вкладке устройства, чтобы открыть его параметры. Вам могут быть доступны следующие устройства:
– HID-совместимая сенсорная панель.
– Microsoft Input Configuration Device.
– Устройство HID на шине I2C.
Далее, в свойствах устройства вы можете узнать и настроить:
Общие:
– Вы можете узнать тип устройства.
Драйвер:
– Вы можете узнать поставщика драйвера.
– Сведения о файлах драйвера.
– Вы можете обновить драйвер.
– Вы можете откатить драйвер к предыдущему.
– Можно отключить устройство.
– Можно удалить драйвер.
Сведения:
– Вы можете узнать значения свойств устройства.
– Выберите свойство и вам автоматически покажут его значение.
– Вы можете узнать характеристики, класс, код ошибки устройства и т.д.
События:
– Вы можете узнать события, которые происходили с устройством.
– Вы можете узнать дату и время события.
– Можно узнать описания и сведения событий.
– В конце нажмите на кнопку OK, чтобы сохранить сделанные изменения.
Остались вопросы ? Напиши комментарий ! Удачи !
Human Interface Devices (HID)
Overview of the Human Interface Devices (HID) technology.
To develop Human Interface Devices (HID), you need these headers:
This section contains the programming interfaces related to Human Interface Devices (or HID). Typically, these are devices that humans use to directly control the operation of computer systems.
HIDClass Support Routines
There are system-supplied routines that user-mode applications, kernel-mode drivers, and HID minidrivers use to operate devices in the HIDClass device setup class.
As a general rule, user-mode applications can use the HidD_Xxx and HidP_Xxx routines. However, kernel-mode drivers can only call HidP_Xxx routines.
HID minidrivers use only the HidRegisterMinidriver routine.
For Windows 8.1 Microsoft introduced the new Windows.Devices.HumanInterfaceDevice API which lets you write Windows apps that access HID devices.
The header defines IOCTLs that a HID minidriver must support. Only the HID class driver sends these IOCTLs to a HID minidriver. User-mode applications and other kernel-mode drivers can only communicate with HID collections by using the HIDClass support routines and HID class driver ioctls.
HID Minidriver IOCTLs
A HID minidriver must handle a set of IOCTLs. Only the HID class driver sends these IOCTLs to a HID minidriver. User-mode applications and other kernel-mode drivers can only communicate with HID collections by using the HIDClass support routines and HID class driver ioctls.
| Topic | Description |
|---|---|
| IOCTL_HID_ACTIVATE_DEVICE | The IOCTL_HID_ACTIVATE_DEVICE request activates a HIDClass device, which makes it ready for I/O operations. |
| IOCTL_HID_DEACTIVATE_DEVICE | The IOCTL_HID_DEACTIVATE_DEVICE request deactivates a HIDClass device, which causes it to stop operations and terminate all outstanding I/O requests. |
| IOCTL_HID_GET_DEVICE_ATTRIBUTES | The IOCTL_HID_GET_DEVICE_ATTRIBUTES request obtains a HIDClass device’s attributes in a HID_DEVICE_ATTRIBUTES structure. |
| IOCTL_HID_GET_DEVICE_DESCRIPTOR | The IOCTL_HID_GET_DEVICE_DESCRIPTOR request obtains a HIDClass device’s HID descriptor. |
| IOCTL_HID_GET_REPORT_DESCRIPTOR | The IOCTL_HID_GET_REPORT_DESCRIPTOR request obtains the report descriptor for a HIDClass device. |
| IOCTL_HID_GET_STRING | The IOCTL_HID_GET_STRING request obtains a manufacturer ID, product ID, or serial number for a top-level collection. The retrieved string is a NULL-terminated wide character string in a human-readable format. |
| IOCTL_HID_READ_REPORT | The IOCTL_HID_READ_REPORT request transfers an input report from a HIDClass device into the HID class driver’s buffer. |
| IOCTL_HID_WRITE_REPORT | The IOCTL_HID_WRITE_REPORT request sends a HID report to a HIDClass device. |
| IOCTL_UMDF_GET_PHYSICAL_DESCRIPTOR | The IOCTL_UMDF_GET_PHYSICAL_DESCRIPTOR control code obtains the physical descriptor of a HIDClass device. |
| IOCTL_UMDF_HID_GET_FEATURE | The IOCTL_UMDF_HID_GET_FEATURE control code obtains a feature report from a HIDClass device. |
| IOCTL_UMDF_HID_GET_INPUT_REPORT | The IOCTL_UMDF_HID_GET_INPUT_REPORT control code returns an input report from a HIDClass device. |
| IOCTL_UMDF_HID_SET_FEATURE | The IOCTL_UMDF_HID_GET_FEATURE control code sends a feature report to a HIDClass device. |
| IOCTL_UMDF_HID_SET_OUTPUT_REPORT | The IOCTL_UMDF_HID_SET_OUTPUT_REPORT control code sends an output report to a top-level collection. |
HID Class Driver IOCTLs
The HID class driver handles IOCTLs to support for top-level collections.
Although user applications can communicate with the HID class driver by using HidD_Xxx HIDClass support routines, kernel-mode drivers must send the corresponding device control requests described in this section.
The input and output parameters are request-specific.
Upon completion of a request, the I/O status block members are set as follows:
The Status member is set by the HID class driver for all requests that it handles.
As described for each IOCTL, the Information member is set either by the class driver or a lower-level driver. Normally, when a lower-level driver transfers data from or to a device, the lower-level driver sets Information to the number of bytes transferred. However, the HID class driver might return a different value.
Introduction to Human Interface Devices (HID)
Human Interface Devices (HID) is a device class definition to replace PS/2-style connectors with a generic USB driver to support HID devices such as keyboards, mice, game controllers, etc. Prior to HID, devices could only utilize strictly-defined protocols for mice and keyboards. Hardware innovation required either overloading data in an existing protocol or creating non-standard hardware with its own specialized driver. HID provided support for these “boot mode” devices while adding support for hardware innovation through extensible, standardized and easily-programmable interfaces.
HID devices today include a broad range of devices such as alphanumeric displays, bar code readers, volume controls on speakers/headsets, auxiliary displays, sensors and many others. Many hardware vendors also use HID for their proprietary devices.
HID began with USB but was designed to be bus-agnostic. It was designed for low latency, low bandwidth devices but with flexibility to specify the rate in the underlying transport. The specification for HID over USB was ratified by the USB-IF in 1996 and support over additional transports followed soon after. Details on currently supported transports can be found in HID Transports Supported in Windows. 3rd-party, vendor-specific transports are also allowed via custom transport drivers.
HID Concepts
HID consists of two fundamental concepts, a Report Descriptor, and Reports. Reports are the actual data that is exchanged between a device and a software client. The Report Descriptor describes the format and meaning the data that the device supports.
Reports
Applications and HID devices exchange data through Reports. There are three Report types: Input Reports, Output Reports, and Feature Reports.
| Report Type | Description |
|---|---|
| Input Report | Data sent from the HID device to the application, typically when the state of a control changes. |
| Output Report | Data sent from the application to the HID device, for example to the LEDs on a keyboard. |
| Feature Report | Data that can be manually read and/or written, and are typically related to configuration information. |
Each Top Level Collection defined in a Report Descriptor can contain zero (0) or more reports of each type.
Usage Tables
The USB-IF working group publishes HID Usage Tables that are part of the Report Descriptors that describe what HID devices are allowed to do. These HID Usage Tables contain a list with descriptions of Usages, which describe the intended meaning and use of a particular item described in the Report Descriptor. For example, a Usage is defined for the left button of a mouse. The Report Descriptor can define where in a Report an application can find the current state of the mouse’s left button. The Usage Tables are broken up into several name spaces, called Usage Pages. Each Usage Page describes a set of related Usages to help organize the document. The combination of a Usage Page and Usage define the Usage ID that uniquely identifies a specific Usage in the Usage Tables.