MagTek 99875125 - Manual (Page 17)

Section 1. Overview
1. It can prompt the user to repeat the action and re-submit the command. This is typical if
the status does not indicate a failure, per se, but that the device may not be ready yet or
first needs some other interaction by the user.
2.
It can reset the device and prompt the user to repeat the action. Typically, this action is
necessary if the device’s state or configuration has been corrupted, but is otherwise
functioning correctly.
3.
Finally, the application can refuse to continue operation of the device. An application
should do this only if the returned status indicates that the device is malfunctioning.
HANDLING SPECIAL COMMANDS
Generic Devices
Some devices such as the IntelliPIN support a set of commands that are not standard and/or do
not follow the usual protocol. The Generic Driver can be used to support these commands. It
does not know how to communicate with any device and does not support any protocol. The
Generic Driver allows the application to send any string to a device. When the Generic Driver is
used, the application must form the command, insert packet characters, and compute a check
character where required. The Generic Driver only supports the “raw” commands.
The Generic Driver can be used whenever a deviation from the standard protocol is required or
when no protocol exists at all. However, the Generic Driver, unlike all of the other drivers, does
not support any properties. It is only available to support those cases that cannot be handled with
the standard drivers.
IntelliPIN Driver
With release MTD 1.12, the IntelliPIN driver has been updated to support the special set of
commands that require <si> and <so> instead of the usual <stx> and <etx> characters. These
special commands that support the multi-master keys (e.g., 02, 04, 08, etc.) are not supported
with the standard IntelliPIN commands. However, if these commands are used in the
/rawsend
or /rawxmit commands, the <si> and <so> will automatically be inserted.
MICR Format Numbers
In order to retrieve the built-in check properties (chk_***), the driver automatically configures
the MICR units to format number 6500. However, there are some cases, especially outside the
United States, where the check information is not consistent with format number 6500. In these
cases, the installer has the option of modifying the format number string in the OEMSETUP.INF
file.
9