MagTek USB MagneSafe Swipe and Insert Reader V5 - Manual (Page 20)

USB MagneSafe V5 Swipe and Insert Reader
12
For the wireless reader, after a card swipe but prior to indicating the status of decoding the card
data when data should be transmitted wirelessly, if the the reader is out of range the green LED
will blink rapidly (~10 times a second) until the reader is back in range (when data is
transmitted). The LED will go off if the user holds the user switch down for three seconds, if the
reader times out, or if the battery power is too low. If the reader is within range, it attempts to
transmit the data during which time the LED goes off. If the transmit attempt fails, the reader
will blink the red LED rapidly (~10 times a second) for two seconds. After which, regardless of
the outcome of the transmit attempt, the LED goes green or red to indicate the status of decoding
the card data.
Anytime the host puts the wired reader or dongle into suspend mode, the LED will turn off.
Once the host takes the reader or dongle out of suspend mode, the respective LED will return to
solid green. For the wired reader, authenticated mode is always ended by a USB suspend. For
the wireless reader it is not.
CARD READ
A card may be swiped through the reader slot when the LED is solid green or flashing green.
The magnetic stripe must face toward the head (as indicated by a line on the top of the reader)
and may be swiped in either direction. If there is data encoded on the card, the reader will
attempt to read the data, encrypt it, and then send the results to the host via a USB HID input
report or, if in Keyboard Emulation mode, as if the data was being typed on a keyboard. After
the results are sent to the host, the reader will be ready to read the next card. For the wireless
reader, if no errors were found while decoding the card data, the reader will automatically turn
off after attempting to transmit the data to the host.
READER STATES
This reader may be operated so that it requires Mutual Authentication with a Host in order to
transmit card data to the Host. When this mode of operation is required, the application (not
necessarily the Authenticating Host) may need to know the state of the reader at any given
moment. This can be done using the Get Reader State Command. The application may retrieve
this state at any time to get a clear definition of where the reader is any given moment.
For convenience, this manual refers to states with the notation State:Antecedent (e.g.,
WaitActAuth:BadSwipe). State definitions can be found at the definition of the Get Reader
State Command.
In most cases, the application could also track the state by inference. As the application interacts
with a reader, most state transitions are marked by the commands and responses exchanged with
the reader. The exception to this concept is the transition from WaitActRply:x to
WaitActAuth:TOAuth. This state transition occurs as the result of a timeout and the transition is
not reported to the Host. As the reader was waiting for the Host to send the Activation
Challenge Reply command and the Host set the time limit the reader should wait, the Host
should be aware that a timeout could occur. If the reader does time out and the Host sends the
Activation Challenge Reply command, the reader will return RC = 07 (Sequence error).
Examples of Host/Application/Reader interaction and state transitions: