Elo TouchSystems ET1229L Series

MagTek Device Drivers for Windows
36
fmt5_name "AAMVA"
fmt5_template"%<*>?;<*>?{(+|%|#|!)<*>?}"
fmt5_rules "{%<State[2]><City>^<LastName>$<FirstName>$<MidName>^<Adr>^<*>?
;<*[6]><DLID>=<ExpDate[4]><DateOfBirth[8]><*>?
{(+|!|#|%)<*[2]><ZIP[11]><*[16]><Sex[1]><Hgt[3]><Wgt[3]><Hair[3]>
<Eye[3]><*>?}},
{%<State[2]><City>^<LastName>$<FirstName>^<Adr>^<*>?
;<*[6]><DLID>=<ExpDate[4]><DateOfBirth[8]><*>?
{(+|!|#|%)<*[2]><ZIP[11]><*[16]><Sex[1]><Hgt[3]><Wgt[3]><Hair[3]>
<Eye[3]><*>?}}"
In the examples for CADL (California Drivers License) and AAMVA (all other drivers licenses),
the braces around the rules for track 3 indicate that track 3 is optional.
EXAMPLE
Retrieving properties from a magnetic card
In this example, the rules above have been stored in the registry by the installation script.
The following data is received from the device:
%B1234567890074589^SMITH/JOHN Q.MR^9912101254700000000000123?
;1234567890074589=991210112547?
Format 1 (ISO59) would not be applied because the first two digits of track 2 are not 59. Format
2 (BankCardA) would not be applied since there is not an ‘A’ following the start sentinel.
However, the data fits the template for format 2 (BankCard).
The following properties and their corresponding values will be exposed:
LastName Æ “SMITH”
FirstName Æ “JOHN”
MidName Æ “Q”
Title Æ “SMITH”
DiscData1 Æ “254700000000000123”
PAN Æ “1234567890074589”
ExpDate Æ “9912”
SrvCode Æ “101”
DiscData2 Æ “12547”
The application receives the successful read response /read M00900 <card data>.