Magtek DynaPro Mini, Руководство программиста

Страница: 14 / 128

2 - Connection Types
DynaPro Mini| PIN Encryption Device | Programmer’s Manual (Commands)
Page 14 of 128 ( D99875629-43 )
2 Connection Types
Table 1-1 in section 1.4 includes a list of connection types available for each device. The following
subsections provide details developers will need to communicate with the device using each connection
type.
2.1 How to Use USB Connections (USB Only)
The device conforms to the USB specification revision 2.0, and are compatible with revision 1.1. It also
conforms to the Human Interface Device (HID) class specification version 1.1, and communicates as a
vendor-defined HID device. This document assumes the reader is familiar with USB HID class
specifications, which are available at
www.usb.org .
Developers can easily create custom software to communicate with the device using any framework that
can make API calls to the standard Windows USB HID driver, such as Visual Basic or Visual C++.
MagTek has developed demonstration software that communicates with the device via this method, and
developers can use it to test the device and to provide a starting point for developing other software. For
more information, see the MagTek web site, or contact your reseller or MagTek Support Services.
The devices is a full speed high-powered USB device that, when connected, draws power from the USB
bus. It identifies itself with vendor
ID 0x0801 and product ID 0x3009 . The device will enter and wake
up from Suspend mode when directed to do so by the USB host. It does not support remote wakeup.
This device has programmable configuration properties stored in non-volatile memory. The properties
are configured via the USB port and can be configured at the factory, by the key loader, or by the end
user. More details can be found in section
3 Command Set in this document, and in a separate document
which provides details about key loading.
2.1.1 About HID Usages
2.1.1.1 About Reports
USB HID devices send and receive data using reports . Each report can contain several sections, called
usages , each of which has its own unique four-byte identifier. The two most significant bytes of a usage
are called the usage page , and the least two significant bytes are called the usage ID . Vendor-defined
usages must have a usage page in the range 0xFF00 - 0xFFFF , and it is common practice for related
usage IDs to share the same usage page. For these reasons, all usages for this device uses vendor-defined
usage page
0xFF20 .
HID reports used by the host can be divided into three types:

Feature Reports (documented in section 3.4 General Commands ). Feature reports can be further
divided into Get types and Set types. The host exclusively uses this type of report to send commands
to the device and to receive synchronous responses from the device.

Input Reports (documented in section 3.5 General Input Reports ) are used by the device to send
asynchronous responses or notifications to the host when a related feature report completes, or
automatically when the device’s state changes. This is common when a command depends on
cardholder action (for example,
Command 0x03 - Request Swipe Card or Command 0x04 -
Request PIN Entry ) or otherwise takes more time to run.

Output Reports . Output reports are part of the HID standard, but are not used by this device.