Section 2. Communications
5
REPORT DESCRIPTOR (HID)
The Report Descriptor is made available to the hosting system during USB enumeration. The
descriptor is shown here for completeness. Typically the hosting operating system will provide
the ability to parse HID Reports based on the actual Report Descriptor, using the assigned Usage
IDs. We strongly CAUTION the programmer to avoid depending on this specific structure as it
may change in future versions. The Report Descriptor is structured as follows:
Item
Value
(Hex)
Usage Page (Magnetic Stripe Reader)
06 00 FF
Usage (Decoding reader device)
09 01
Collection (Application)
A1 01
Logical Minimum (0)
15 00
Logical Maximum (255)
26 FF 00
Report Size (8)
75 08
Usage (Track 1 decode status)
09 20
Usage (Track 2 decode status)
09 21
Usage (Track 3 decode status)
09 22
Usage (Track 1 encrypted data length)
09 28
Usage (Track 2 encrypted data length)
09 29
Usage (Track 3 encrypted data length)
09 2A
Usage (Card encode type)
09 38
Report Count (7)
95 07
Input (Data, Variable, Absolute, Bit Field)
81 02
Usage (Track 1 encrypted data)
09 30
Report Count (112)
95 70
Input (Data, Variable, Absolute, Buffered Bytes)
82 02 01
Usage (Track 2 encrypted data)
09 31
Report Count (112)
95 70
Input (Data, Variable, Absolute, Buffered Bytes)
82 02 01
Usage (Track 3 encrypted data)
09 32
Report Count (112)
95 70
Input (Data, Variable, Absolute, Buffered Bytes)
82 02 01
Usage (Card status)
09 39
Report Count (1)
95 01
Input (Data, Variable, Absolute, Bit Field)
81 02
Report Size (32)
75 20
Usage (MagnePrint status)
09 23
Report Count (1)
95 01
Input (Data, Variable, Absolute, Bit Field)
81 02
Summary of Contents for MagneSafe V5
Page 8: ...viii...
Page 84: ...MagneSafe V5 76...
Page 96: ...MagneSafe V5 88...
Page 98: ...MagneSafe V5 90...
Page 132: ...MagneSafe V5 124...
