USB HID Usage Tables v1.12: Universal Serial Bus Human Interface Device标准

需积分: 12 88 浏览量更新于2024-07-10 收藏 2.05MB PDF 举报

"这是USB开发手册中的HID（Human Interface Device，人机接口设备）Usage Tables，版本1.12，发布于2004年10月28日。该文档由USB Implementers’ Forum发布，并由多个公司的专家共同编写和修订。手册详细列出了USB HID设备的各种使用表，包括各种输入、输出和控制设备的定义，如键盘、鼠标、游戏控制器、扫描仪等。此外，还包含了历史修订记录，例如1.11和1.11rc1的更新内容。" USB HID Usage Tables是定义和标准化USB设备与操作系统交互的一种规范。在USB设备中，HID类设备是最常见的，它们是用户直接与计算机进行交互的设备，如键盘、鼠标、游戏控制器、触摸屏等。这个手册提供了这些设备在USB协议下的具体使用方式和识别码，使得不同的硬件厂商可以按照统一的标准来设计和制造HID设备，确保其能在各种操作系统上正常工作。手册中的Usage Tables详细描述了每个HID设备类型的编码和用法，包括主控项（如按钮、滑块、转盘）、轴（如鼠标滚轮、摇杆）、以及其他特殊功能。例如，一个键盘的Usage可能包括字母键、数字键、功能键等，而鼠标则可能包括左键、右键、滚轮和移动轴。版本1.12的发布意味着对之前的版本进行了更新和改进，可能涉及了错误修复、新设备类型的添加或者对现有设备定义的细化。例如，修订记录中提到的HUT Review Request编号可能对应着特定的反馈或建议，这些改动旨在提高设备兼容性和用户体验。 USB HID Usage Tables的重要性在于，它不仅是硬件开发者设计USB HID设备时的重要参考，也是软件开发者实现驱动程序和应用支持的基础。通过遵循这些标准，设备可以被广泛支持，减少了用户在不同系统上的兼容性问题。同时，这个文档也为系统和应用开发者提供了一个统一的接口，使他们能够方便地处理来自各种HID设备的输入信号。 USB开发手册中的HID Usage Tables是理解和开发USB HID设备的核心参考资料，对于理解USB设备的工作原理、确保设备兼容性以及构建相关软件有着至关重要的作用。

Universal Serial Bus HID Usage Tables

Version 1.12

October 28, 2004

3.3

Usages and Units

For usages that declare data items as a measurement of time, distance, force, and so forth, an application

must look at the units to properly interpret the value defined by a usage, unless:

1. The usage specifically declares Units as optional.

2. The usage description defines the units in which the value will be presented.

If Units are set to Optional or set to None (have not been declared) then an application can assume the usage

represents a dimensionless value. Any application that ignores Units does so at its own risk.

A usage that declares itself to be a measurement of time would specify whether it was seconds or

milliseconds by declaring Units and Unit Exponent prior to the respective Main item declaration. An

example of this is the Flash On Time usage on the LED page, which is described as the duration that the

indicator is illuminated in flash mode. The duration would be qualified by the values of Units and Unit

Exponent.

When declaring Units for a main item, the Logical Minimum, Logical Maximum, Physical Minimum,

Physical Maximum, and Unit Exponent items must also be declared.

Note In many cases the coordinate system assumes that the values can vary both positively and

negatively from zero (0).

3.4

Usage Types

Usages define a wide variety of device features. However, the way an application treats the data that they

generate falls into a relatively small set of categories. This section provides descriptions of frequently used

types of usages, primarily to save redundant text throughout this document. This list is not an exhaustive list

of the possible usage types. Individual usage pages can declare their own usage types.

Each usage type describes how an application should treat the data generated by the Main item that the

usage is attached to.

Usage type names are followed by an abbreviation that is used in the detailed usage description to identify

the default type of a usage. In some cases usage types do not apply and the detailed description will identify

how the usage is to be interpreted.

There are three basic types of information that are described by usages: controls, collections, and data. In

this context, controls are identified with the state of a device (on/off, enable/disable, and so forth),

collections group related controls and data together, and data comprises the remaining information that is

passed between a device and the host.

Note Usage types are always considered to be the recommended method of handling a usage.

Consult the usage’s definition to determine whether alternative usage types may apply.

Universal Serial Bus HID Usage Tables

Version 1.12

October 21, 2004

3.4.1 Usage Types (Controls)

The following table summarizes the control related usage types.

Table 2: Usage Types (Controls)

Control

Type

Logical

Min

Logical

Max

Flags

Signal

Operation

Linear

Control

(LC)

–1

Relative,

Preferred

State

Edge

1 increments the control’s value.

–1 decrements the control’s value.

–Min

Max

Relative,

Preferred

State

Level

n increments the control’s value. –n

decrements the control’s value.

Min

Max

Absolute,

Preferred

State

N/A

The value reported by the control is

used directly by the host.

On/Off

Control

(OOC)

-1

Relative,

No Preferred

Edge

1 asserts an On condition.

–1 asserts an Off condition.

Relative,

Preferred

State

Edge

A 0 to 1 transition toggles the current

On/Off state.

Absolute,

No Preferred

Level

1 asserts an On condition.

0 asserts an Off condition.

Momentary

Control

(MC)

Absolute,

Preferred

State

Level

1 asserts a condition.

0 deasserts the condition.

One Shot

Control

(OSC)

Relative,

Preferred

State

Edge

A 0 to 1 transition triggers an event.

A 1 to 0 transition must occur before

another event can be triggered.

Re-trigger

Control

(RTC)

Absolute,

Preferred

State

Level

1 triggers an event. When an event

completes, if the value is 1 then the

event will be triggered again.

3.4.1.1 Linear Control (LC)

In many cases, a control of a linear value is implemented as a pair of increment/decrement buttons, a jog

wheel, or a linear control such as a knob or a slide.

When implemented as an increment/decrement control, the two buttons must be translated into a single, 2-bit

signed value and declared as a Relative Main item with a Report Size equal to 2, where –1 decrements the

value, +1 increments it, and no change occurs when 0 is asserted.

A jog wheel is normally implemented as a spring-loaded knob that returns to a fixed center position when

released. This control reports a single value of two or more bits which are reported as a signed value and

declared as a Relative Main item where –n decrements the value, +n increments it, and no change occurs

when 0 is asserted. A jog wheel control is implemented with a resolution of +/–n, where the offset of the

knob from the center position is proportional to the reported value. The Report Size must be declared large

enough to contain the signed value n.

When implemented as a linear knob or slide, the control must be declared as an Absolute Main item. For an

example, see Section A.1, “Volume Control,” in Appendix A, “Usage Examples.”

Universal Serial Bus HID Usage Tables

Version 1.12

October 28, 2004

3.4.1.2 On/Off Control (OOC)

An On/Off Control can be implemented in any of the following ways:

Two buttons, On and Off. The two buttons are encoded into a 2-bit signed value and declared as

a Relative, No Preferred Main item with Logical Minimum and Logical Maximum of –1 and 1,

respectively. The transition from 0 to –1 generates an Off condition and the transition from 0 to +1

generates an On condition. No change occurs when 0 is asserted.

A single button that toggles the On/Off state each time it is pressed. (single throw momentary

switch The single button is encoded into a 1-bit unsigned value and declared as an Relative,

Preferred Main item with a Logical Minimum and Logical Maximum of 0 and 1, respectively.

The transition from 0 to 1 toggles the current On/Off state. No change occurs on the 1 to 0

transition.

A toggle switch that maintains the On/Off state mechanically. (toggle switch) This control is

encoded into a 1-bit unsigned value and declared as an Absolute, No Preferred Main item with a

Logical Minimum and Logical Maximum of 0 and 1, respectively. The assertion of 1 generates an

On condition and the assertion of 0 generates an Off condition.

3.4.1.3 Momentary Control (MC)

A Momentary Control is a basic push button. A Momentary Control is encoded into a 1-bit value and

declared as an Absolute, Preferred Main item with a Logical Minimum and Logical Maximum of 0 and 1,

respectively. A value of 1 generates an asserted condition and 0 generates a non-asserted condition. An

example is a mouse button.

3.4.1.4 One Shot Control (OSC)

A One Shot Control is a push button that triggers a single event or action. A One Shot Control is encoded

into a 1-bit value and declared as a Relative, Preferred Main item with a Logical Minimum and Logical

Maximum of 0 and 1, respectively. A 0 to 1 transition initiates an event. Nothing occurs on a 1 to 0

transition but it is required before another event can occur. An example is degauss.

3.4.1.5 Re-Trigger Control (RTC)

A Re-Trigger Control is a push button that triggers a repeating event as long as it is asserted. A Re-Trigger

Control is encoded into a 1-bit value and declared as an Absolute, Preferred Main item with a Logical

Minimum and Logical Maximum of 0 and 1, respectively. A 0 to 1 transition initiates the first event. When

each event terminates, if the control is still asserted (1) then another event will occur. An example is an auto-

repeat fire button.

3.4.2 Usage Types (Data)

The following table summarizes the data-related usage types.

Table 3: Usage Types (Data)

Type

Flags

Description

Selector (Sel)

Array

Contained in a Named Array (NAry).

Static Value (SV)

Constant, Variable, Absolute

A read-only multiple-bit value.

Static Flag (SF)

Constant, Variable, Absolute

A read-only single-bit value.

Dynamic Value (DV)

Data, Variable, Absolute

A read/write multiple-bit value.

Dynamic Flag (DF)

Data, Variable, Absolute

A read/write single-bit value.

Universal Serial Bus HID Usage Tables

Version 1.12

October 21, 2004

3.4.2.1 Selector (Sel)

Selectors come in three forms:

One selection of a set. Radio buttons are a mechanically linked set of buttons where one selection

is always valid. This is a perfect example of the “one selection of a set” form. A radio button set is

defined by a Main item with the Array flag set and the Report Count set to 1. The index returned

in the array field corresponds to the pressed button (or selection). A usage must be declared for

each selection. The array field never returns an index of NULL because one usage is always valid.

An example is Stat Not Ready on the Alphanumeric Display page.

N selections of a set. More than one selection (button) can be valid at a time. Multiple selections

can be returned to the system at one time in a multi-byte array. The “n selections of a set” form is

defined by a Main item with the Array flag set and the Report Count set to n, where n is the

number of selections that can be reported in a single report. An example is a keyboard.

Any selection of a set. The control is implemented as a set of bit fields in which each bit represents

a single selection. This control is defined by a Main item with the Variable flag set and the Report

Size equal to 1. The Report Count will be equal to the number of selections in the set.

Selectors therefore can be implemented in a number of ways: Array[1] (one selection of a set), Array[n] (n

selections of a set), or bitmap (any selection of a set).

Optionally, the array field or set can be named by wrapping a set of Selectors in a logical collection with a

usage attached to it. For details, see Section 3.4.3.1, “Named Array (NAry).”

3.4.2.2 Static Value (SV)

Static values are used to declare a fixed features in a device. They are defined as Constant and treated as

read-only information. Therefore, asserting this field in a Set_Report command has no defined effect.

3.4.2.3 Static Flag (SF)

Static flags are used to declare the existence of a fixed feature in a device. If a Static Flag usage is found in a

Report descriptor then the field must be read to determine whether the feature identified by the flag exists.

A value of 1 indicates existence and a value of 0 indicates non-existence. The absence of a Static Flag usage

implies that the flag is false or the feature defined by the flag is not supported by the device. A Static Flag

must be declared as a Constant. To be accessible by applications, a Static Flag must have a usage assigned to

it.

Static Flags are typically declared in a Feature report as a single-bit field where the value is always read as

1. Attempting to modify this field in a Set_Report command has no effect on a Static Flag.

3.4.2.4 Dynamic Flag (DF)

Dynamic Flags are used to declare the existence of a host-controllable feature in a device. The absence of a

Dynamic Flag usage implies that the flag is false or the feature defined by the flag is not supported by the

device.

Dynamic Flags are typically declared in a report as a single-bit field, where a value of 1 returned by the

device indicates that the feature is enabled. The assertion of 1 by the host will cause the feature to be evoked

and the assertion of 0 indicates that the feature is to be disabled or ignored if the feature is a one-time event

(such as Degauss or Clear Display). A Dynamic Flag Main item must be declared as Data.

Universal Serial Bus HID Usage Tables

Version 1.12

October 28, 2004

3.4.2.5 Dynamic Value (DV)

A Dynamic Value is an n-bit field that contains a value associated with a control. The associated Main item

will have the Data and Variable flags set. A Dynamic Value Main item must be declared as Data.

Note

More advanced devices may allow a usage declared as a Static type to be Dynamic. Always

check the Constant/Data flag in an Input, Output or Feature Main item.

3.4.3 Usage Types (Collection)

The following table summarizes the collection-related usage types.

Table 4: Usage Types (Collection)

Type

Collection Type

Definition

Named Array

(NAry)

Logical

A collection that encompasses an array

definition, naming the array set or the field

created by the array.

Application Collection

(CA)

Application

Applies a name to a top level collection

which the operating system uses to identify

a device and possibly remap to a legacy

API.

Logical Collection

(CL)

Logical

A logical collection of items.

Physical Collection

(CP)

Physical

A physical collection of items.

Usage Switch

(US)

Logical

Modifies the purpose or function of the

usages (controls) that it contains.

Usage Modifier

(UM)

Logical

Modifies the purpose or function of the

usages (controls) that contains it.

3.4.3.1 Named Array (NAry)

To simplify for an application the process of finding a set of selectors, whether defined as an Array Field or

a bitmap, the set of selectors can be named by wrapping them in a logical collection and applying a usage to

the collection. Usages applied in this way are called Named Array usages. For an example, see Section A.4,

“Named Array Field,” in Appendix A, “Usage Examples.”

3.4.3.2 Collection Application (CA)

The Collection Application usage type identifies usages that are used only in application-level collections.

An application collection identifies a HID device or a functional subset of a complex device. An operating

system uses the usage associated with this collection to link the device to its controlling application or

driver. Common examples are a keyboard or mouse. A keyboard with an integrated pointing device could

contain two different application collections.

Note Data reports cannot span application collections.

3.4.3.3 Collection Logical (CL)

The Collection Logical usage type identifies a usage applied to a logical collection. Logical collections can

be used to further define the purpose of the items or controls that they contain.

剩余169页未读，继续阅读

站长漫谈

粉丝: 114
资源: 56

USB HID Usage Tables v1.12: Universal Serial Bus Human Interface...

最新资源

USB HID Usage Tables v1.12: Universal Serial Bus Human Interface...

Hut1_12v2 (1).zip_Hut1_12v2.pdf_hut1_modulation_theusualstuff

T细胞淋巴瘤Hut-78细胞株细胞周期细胞凋亡PMLhTERT三氧化二砷RT-PCR.pdf

N-body实验.pdf

USB HID USAGE TABLE.pdf

沈阳连锁餐饮分布借鉴.pdf

5月30号现代控制理论A-自动化17级-试卷A(1).pdf

XXX家居广场]招商策划方案.pdf

百胜中国-S：2020年度报告.PDF

使用CUDA进行快速N-body模拟.pdf

python核心编程第15章学习笔记.pdf

最新资源