Magtek ExpressCard 1000 Owner's manual

Magtek
Brand
Magtek
Model
ExpressCard 1000
Type
Owner's manual

Magtek ExpressCard 1000 is a versatile device that allows its users to easily process card data in various ways. With the ExpressCard 1000, you can:

  • Process card data using a web browser interface or the ExpressCard 1000 API.
  • Get device status and information, such as the firmware version and serial number.
  • Process cards with various options, such as reading the cardholder's name, account number, and expiration date.
  • Receive error messages if the card processing fails.

Magtek ExpressCard 1000 is a versatile device that allows its users to easily process card data in various ways. With the ExpressCard 1000, you can:

  • Process card data using a web browser interface or the ExpressCard 1000 API.
  • Get device status and information, such as the firmware version and serial number.
  • Process cards with various options, such as reading the cardholder's name, account number, and expiration date.
  • Receive error messages if the card processing fails.
ExpressCard 1000
PROGRAMMING REFERENCE MANUAL
WINDOWS API SPECIFICATIONS
MANUAL PART NUMBER 99875367-1
SEPTEMBER 2007
REGISTERED TO ISO 9001:2000
1710 Apollo Court
Seal Beach, CA 90740
Phone: (562) 546-6400
FAX: (562) 546-6301
Technical Support: (651) 415-6800
www.magtek.com
Copyright
©
2004 – 2007
MagTek
®
, Inc.
Printed in the United States of America
Information in this document is subject to change without notice. No part of this document may be
reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose,
without the express written permission of MagTek, Inc.
MagTek is a registered trademark of MagTek, Inc.
ExpressCard 1000
TM
is a trademark of MagTek, Inc.
Microsoft
®
is a trademark of Microsoft, Inc.
REVISIONS
Rev Number Date Notes
1 Sept 9, 07 Initial Release
ii
REGISTERED TO ISO 9001:2000
1710 Apollo Court, Seal Beach, CA 90740 MagTek Part Number 99875367-1
Voice: 310-631-8602 Fax: 310-631-3956 06 Sept 2007
SOFTWARE LICENSE AGREEMENT
IMPORTANT: YOU SHOULD CAREFULLY READ ALL THE TERMS, CONDITIONS AND RESTRICTIONS OF THIS LICENSE AGREEMENT
BEFORE INSTALLING THE SOFTWARE PACKAGE. YOUR INSTALLATION OF THE SOFTWARE PACKAGE PRESUMES YOUR ACCEPTANCE
OF THE TERMS, CONDITIONS, AND RESTRICTIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE WITH THESE TERMS,
CONDITIONS, AND RESTRICTIONS, PROMPTLY RETURN THE SOFTWARE PACKAGE AND ASSOCIATED DOCUMENTATION TO ABOVE
ADDRESS ATTENTION: CUSTOMER SUPPORT.
TERMS, CONDITIONS AND RESTRICTIONS
MagTek, Incorporated (the "Licensor") owns and has the right to distribute the described software and documentation, collectively referred to as the
"Software".
LICENSE: Licensor grants you (the "Licensee") the right to use the Software in conjunction with MagTek products.
LICENSEE MAY NOT COPY, MODIFY OR TRANSFER THE SOFTWARE IN WHOLE OR IN PART EXCEPT AS EXPRESSLY PROVIDED IN THIS
AGREEMENT. Licensee may not decompile, disassemble or in any other manner attempt to reverse engineer the Software. Licensee shall not tamper with,
bypass or alter any security features of the software or attempt to do so.
TRANSFER: Licensee may not transfer the Software or license to the Software to another party without prior written authorization of the Licensor. If
Licensee transfers the Software without authorization, all rights granted under this Agreement are automatically terminated.
COPYRIGHT:
The Software is copyrighted. Licensee may not copy the Software except for archival purposes or to load for execution purposes. All other
copies of the Software are in violation of this Agreement.
TERM:
This Agreement is in effect as long as Licensee continues the use of the Software. The Licensor also reserves the right to terminate this Agreement if
Licensee fails to comply with any of the terms, conditions or restrictions contained herein. Should Licensor terminate this Agreement due to Licensee's failure
to comply, Licensee agrees to return the Software to Licensor. Receipt of returned Software by the Licensor shall mark the termination.
LIMITED WARRANTY:
Licensor warrants to the Licensee that the disk(s) or other media on which the Software is recorded to be free from defects in
material or workmanship under normal use. THE SOFTWARE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. Because of the diversity of conditions and PC hardware under which the Software may be used, Licensor does not warrant that the Software will
meet Licensee specifications or that the operation of the Software will be uninterrupted or free of errors.
IN NO EVENT WILL LICENSOR BE LIABLE FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR OTHER INCIDENTAL
OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE. Licensee's sole remedy in the event of a
defect in material or workmanship is expressly limited to replacement of the Software disk(s) if applicable.
GOVERNING LAW: If any provision of this Agreement is found to be unlawful, void or unenforceable, that provision shall be removed from
consideration under this Agreement and will not affect the enforceability of any of the remaining provisions. This Agreement shall be governed by the laws of
the State of California and shall insure to the benefit of MagTek, Incorpor
ated, its successors or assigns.
ACKNOWLEDGMENT:
LICENSEE ACKNOWLEDGES THAT HE HAS READ THIS AGREEMENT, UNDERSTANDS ALL OF ITS TERMS,
CONDITIONS AND RESTRICTIONS AND AGREES TO BE BOUND BY THEM. LICENSEE ALSO AGREES THAT THIS AGREEMENT
SUPERSEDES ANY AND ALL, VERBAL AND WRITTEN, COMMUNICATIONS BETWEEN LICENSOR AND LICENSEE OR THEIR ASSIGNS
RELATING TO THE SUBJECT MATTER OF THIS AGREEMENT.
QUESTIONS REGARDING THIS AGREEMENT SHOULD BE ADDRESSED IN WRITING TO MAGTEK, INCORPORATED, ATTENTION:
CUSTOMER SUPPORT, AT THE ABOVE ADDRESS OR E-MAILED TO [email protected]om
.
iii
TABLE OF CONTENTS
SECTION 1. OVERVIEW .............................................................................................................................................1
Requirements............................................................................................................................................................1
Introduction................................................................................................................................................................1
SECTION 2. EXPRESSCARD 1000 SOFTWARE ARCHITECTURE.........................................................................3
Term Description.......................................................................................................................................................4
How To Communicate With Expresscard 1000 Using Web Browser.......................................................................5
Get Device Status .....................................................................................................................................................6
Get Device Information..............................................................................................................................................7
How To Communicate With Expresscard 1000 Using Expresscard 1000 API.........................................................8
API Functions............................................................................................................................................................9
Software Flow For Document Processing...............................................................................................................10
How To Process Card Using Expresscard 1000 API..............................................................................................11
Process Options......................................................................................................................................................11
Error Reporting........................................................................................................................................................12
Debugging API........................................................................................................................................................12
SECTION 3. EXPRESSCARD 1000 API...................................................................................................................13
MTECSDK_GetDevice............................................................................................................................................13
Parameters..........................................................................................................................................................13
Return Values .....................................................................................................................................................13
Remarks..............................................................................................................................................................13
Example..............................................................................................................................................................13
MTECSDK_OpenDevice.........................................................................................................................................14
Parameters..........................................................................................................................................................14
Return Values .....................................................................................................................................................14
Remarks..............................................................................................................................................................14
Example..............................................................................................................................................................14
MTECSDK_CloseDevice.........................................................................................................................................15
Parameters..........................................................................................................................................................15
Return Values .....................................................................................................................................................15
Remarks..............................................................................................................................................................15
Example..............................................................................................................................................................15
MTECSDK_ProcessDoc .........................................................................................................................................16
Parameters..........................................................................................................................................................16
Return Values .....................................................................................................................................................16
Remarks..............................................................................................................................................................17
Example..............................................................................................................................................................17
MTECSDK_QueryInfo.............................................................................................................................................18
Parameters..........................................................................................................................................................18
Return Values .....................................................................................................................................................18
Remarks..............................................................................................................................................................19
Example..............................................................................................................................................................19
MTECSDK_SendCommand....................................................................................................................................19
MTECSDK_SetValue..............................................................................................................................................20
Parameters..........................................................................................................................................................20
Return Values .....................................................................................................................................................20
Remarks..............................................................................................................................................................20
Example..............................................................................................................................................................21
MTECSDK_GetValue..............................................................................................................................................21
Parameters..........................................................................................................................................................21
Return Values .....................................................................................................................................................21
Remarks..............................................................................................................................................................22
Example..............................................................................................................................................................22
MTECSDK_SetAttribute..........................................................................................................................................23
iv
v
Parameters..........................................................................................................................................................23
Return Values .....................................................................................................................................................23
Remarks..............................................................................................................................................................23
Example..............................................................................................................................................................23
MTECSDK_GetAttribute..........................................................................................................................................24
Parameters..........................................................................................................................................................24
Return Values .....................................................................................................................................................24
Remarks..............................................................................................................................................................24
Example..............................................................................................................................................................25
MTECSDK_LogEnable............................................................................................................................................26
Parameters..........................................................................................................................................................26
Return Values .....................................................................................................................................................26
Remarks..............................................................................................................................................................26
Example..............................................................................................................................................................26
MTECSDK_SetLogFileHandle................................................................................................................................27
Parameters..........................................................................................................................................................27
Return Values .....................................................................................................................................................27
Remarks..............................................................................................................................................................27
Example..............................................................................................................................................................27
1
SECTION 1. OVERVIEW
The sections of this manual are as follows:
Section 1. Overview
Section 2. Architecture and Operation
Section 3. Functions – describes ExpressCard 1000 API functions and return codes.
REQUIREMENTS
The following item is required for software installation:
P/N 33090060 ExpressCard Software Development Kit (This CD installs ExpressCard 1000 Demo
Program and MTECSDK.dll)
INTRODUCTION
The ExpressCard 1000 (EC1000) is a desktop card production/personalization system that has
the capability to instantly issue financial or ID cards in approximately 2 to 3 minutes per card.
The primary functions and features of the EC1000 are as follows:
• Dual card-input hoppers (100 cards per hopper)
• Manual Insertion Slot (Single card entry)
• Encoder module (Magstripe/smartcard/contactless-card/MagnePrint)
• Thermal/Dye-Sublimation Printer (Print on dual sides of card)
• Embosser/Rear-Indent module (Mechanically embosses/indents characters on card surface)
• Exit module (Exits completed card, or stores rejected card in internal hopper)
• Secure enclosure that can logically detect/permit access to the device
• Touchscreen LCD display that provides for primary user interface.
• Ethernet interface
• XML protocol, using MagTek defined key-value pairs.
This manual is intended for use by Application Programmers who want to develop custom application
code to directly control and interface to the EC1000 device.
In regard to interface options, programmers can choose from 2 approaches to facilitate an interface to the
device:
1. Directly utilize XML protocol and MagTek defined key-value pairs.
2. Utilize a MagTek API DLL.
Both options are effective in facilitating an interface to the device.
However, there is probably an advantage in utilizing the MagTek API, as it will ensure that if any changes
occur to the underlying hardware interface of the device (e.g. USB, RS-232, Firewire, etc…), the
Application layer will be abstracted from these changes, and will not have to make any code changes.
ExpressCard 1000 Programming Reference
2
This Programmer’s reference manual provides definitions for the API DLL interface. It is recommended
that the application programmer review all of this information, so as to gain a broad perspective of the
command, status, and functional aspects the device interface.
Of primary importance, is to review the code samples contained in the appendices of this document. The
code samples provide clear instructions regarding the operational sequence of events, as well as the code
formatting that is typically used during interface to the device.
By starting with these samples, the application programmer can build more complex functionality into
their overall application.
SECTION 2. EXPRESSCARD 1000 SOFTWARE ARCHITECTURE
The architecture of the system is shown in Figure 2-1. Descriptions of the terms and operations used
follow the illustration.
A
pp
lication
Figure 2-1. ExpressCard 1000 Software Architecture
COMPUTER
EXPRESSCARD 1000
DEVICE
Wininet.dll
‘C’ API to xfer data to a web
XML to Key/Value and vice versa
ExpressCard 1000
‘C’ API
MSXML
HTTP: XML
Microsoft Network Stack
Ethernet XML
Ethernet XML
Network Layer TCP/IP
WEB Server
HTTP & XML Parser)
ExpressCard 1000 Programming Reference
TERM DESCRIPTION
MTECSDK.dll.
Provides API to upper level application to talk to the device. The application does not have any
knowledge of how the device is connected to the computer. Thus it does not expose the transport protocol
to the application. We are using HTTP protocol with XML to communicate with the device. The
MTECSDK.dll uses wininet.dll to talk to internet protocols. The MTECSDK.dll. provides functions to
convert the print request into XML format using msxml4.dll and then send it to the device using
wininet.dll. It also provides functions to convert the response from the device (XML format) to key/value
pairs.
msxml4.dll: Microsoft XML Parser.
MTECSDK.dll. uses msxml4.dll to convert the key/value pair to XML language.
MTECSDK.dll also uses the msxml4.dll to convert the XML data back to key/ value pair.
wininet.dll: MFC Win32 Internet Extension. wininet.dll, provide access to common Internet protocols,
including Gopher, FTP, and HTTP. MTECSDK.dl uses wininet.dll to establish an Internet connection
with ExpressCard 1000 device. It then communicates with ExpressCard 1000 using GET and POST
requests provide by wininet.dll.
4
Section 2 - Architecture
HOW TO COMMUNICATE WITH EXPRESSCARD 1000 USING WEB BROWSER
ExpressCard 1000 can be accessed from an Internet Web browser using the IP address of the device. An
example in using the IP address of the ExpressCard 1000 device to obtain device capabilities information
is followed.
Assuming the ExpressCard 1000 device has IP address 192.168.10.100, type the following line in the
address box of the Web browser. Internet Explorer is used in this example:
https:// 192.168.10.100/Index.aspx?DeviceInformation=DeviceCapabilities
Press the Enter key, and the ExpressCard 1000 responds with the results shown below:
5
ExpressCard 1000 Programming Reference
GET DEVICE STATUS
The following is an example in using the IP address of the ExpressCard 1000 device to obtain device
status information. Assuming the ExpressCard 1000 device has IP address 192.168.10.100, type the
following line in the address box of the Web browser. Internet Explorer is used in this example:
https:// 192.168.10.100/Index.aspx?DeviceInformation=DeviceStatus
Press the Enter key, and the ExpressCard 1000 responds with the results shown below:
6
Section 2 - Architecture
GET DEVICE INFORMATION
The following is an example in using the IP address of the ExpressCard 1000 device to obtain device -
usage information. Assuming the ExpressCard 1000 device has IP address 192.168.10.100, type the
following line in the address box of the Web browser. Internet Explorer is used in this example:
https:// 192.168.10.100/Index.aspx?DeviceInformation=DeviceInformation
Press the Enter key, and the ExpressCard 1000 responds with the results shown below:
7
ExpressCard 1000 Programming Reference
HOW TO COMMUNICATE WITH EXPRESSCARD 1000 USING EXPRESSCARD 1000 API
The following table lists required files in order to use ExpressCard 1000 API:
Files Location Description
MTECSDK.ini
Windows folder This file contains a list of default
ExpressCard 1000 connections
and IP addresses. This file is
required by the MTECSDK.dll
MTECSDK.dll
Windows System32 folder ExpressCard 1000 API
wininet.dll
Windows System32 folder.
Win32 API for Internet Protocols.
This file is provided by Microsoft
msxml4.dll
Windows System32 folder.
MSXML XML parser. ActiveX
Object for XML API . This file is
installed with the installation of
ExpressCard 1000 API
8
Section 2 - Architecture
API FUNCTIONS
Table 2-1 lists functions provided by MTECSDK.dll. Please refer to Section 3 for a complete description
of these functions.
Table 2-1. Functions
NAME DESCRIPTION PAGE
MTECSDK_GetDevice
Get device name of all devices present in
the system.
13
MTECSDK_OpenDevice
Opens device with the given device
name.
14
MTECSDK_CloseDevice
Closes device with the given device
name.
15
MTECSDK_ProcessDoc
Sends a process request to a given
device to process card with given options
16
MTECSDK_QueryInfo
Sends a request to a given device name
to query for info on a given query
parameter.
18
MTECSDK_SendCommand
Sends a single command to a given
device name.
19
MTECSDK_SetValue
Sends a request to a given device to
process with given options.
20
MTECSDK_GetValue
Get process options from a given device
21
MTECSDK_SetAttribute
Set a specific attribute within a key
23
MTECSDK_GetAttribute
Get all attributes within a key
24
MTECSDK_LogEnable
Enable the logging.
26
MTECSDK_SetLogFileHandle
Logs errors to the given file handle.
27
9
ExpressCard 1000 Programming Reference
SOFTWARE FLOW FOR DOCUMENT PROCESSING
Figure 2-4 illustrates the sequence of document processing.
Ex
p
ressCard 1000 Presen
t
Successful Open Device
Select desired options for
document processing
Yes
Yes
Send O
p
tions to Device
Check Completion Status
Close Device
Yes
Yes
Figure 2-4. Software Flow for Card Processing
10
Section 2 - Architecture
HOW TO PROCESS CARD USING EXPRESSCARD 1000 API
To process card, follow these steps:
1. Find the attached ExpressCard 1000 device by calling function MTECSDK_GetDevice.
2. Use function MTECSDK_OpenDevice to open the device.
3. ExpressCard 1000 is now ready to accept the XML options using function
MTECSDK_ProcessDoc. For every document that is processed, a set of options must be sent to the
device. These options define how the document will be processed, i.e., image file, image type, text
line, text font, magstripe encode data, emboss data, etc. The options are stored as key/value pairs
in a buffer. The memory for this buffer must be allocated big enough to store all selected options.
These options must be sent to ExpressCard 1000 device using function
MTECSDK_ProcessDoc.
Use function
MTECSDK_SetValue to store the key/value pairs in the option buffer. The options
can be set in the buffer only once.
4. Use function MTECSDK_ProcessDoc to send the process options to the ExpressCard 1000 device.
5. ExpressCard 1000 processes the document with the given process options and returns the result of
the process operation. The result is stored in the third parameter of the function
MTECSDK_ProcessDoc. The result contains only the information of the operation and information
of the device. It does not contain scanned data. Information such as the size of the scanned images
and the image identifier are included. The image information can be found under ImageInfo
section. Use function MTECSDK_GetValue to retrieve key/value pair for image information. If
there is no error returned in the document information, use function MTECSDKGetImage or
function MTECSDKGetImages to get image data.
6. Go to step 4 to process the next card.
PROCESS OPTIONS
Process options are stored as key/value pairs in a buffer. The structure of the options follows XML
format. Use function
MTECSDK_SetValue to add an option to this structure. Options are string-based
key/value pairs. Each option is stored only once in the buffer. Function MTECSDK_GetValue can be used
to retrieve a key/value pair from this buffer.
11
ExpressCard 1000 Programming Reference
12
ERROR REPORTING
When a document is processed, if there is an error in the ExpressCard 1000 device or in the processing
operation, the error is returned in the function
MTECSDK_ProcessDoc. Use function MTECSDK_GetValue
to retrieve the error information. The Windows XML Specification manual (PN 99875368) has a list of
return codes and return messages from the ExpressCard 1000.
If an error occurs due to the failure of API function, the error is returned as the return code of the API
provided by MTECSDK.dll. The Windows XML Specification manual (PN 99875368) contains a list of
return codes from MTECSDK.dll
DEBUGGING API
On the ExpressCard 1000 Demo GUI program, there is an option to enable the error logging function. If
this option is enabled, all errors returned from the device are logged into log file named “Demo.log”. This
file is resided in the ExpressCard 1000 Demo program installation directory.
SECTION 3. EXPRESSCARD 1000 API
MTECSDK_GetDevice
MTECSDK_GetDevice function returns the device name of the device present in the system.
ULONG MTECSDK_GetDevice (
DWORD dwDeviceContext,
char *pcDevName
);
Parameters
dwDeviceContext
This is the device number of the device. This must be set to 1 to get the first device in the system. Increment it by 1 to get
the next device name.
pcDevName
Pointer to the buffer where the device name will be stored.
Return Values
EC_ST_OK
EC_ST_DEVICE_NOT_FOUND
EC_ST_BAD_PARAMETER
Remarks
If the function succeeds, the return value is EC_ST_OK. The device name of the device is filled in the buffer pointed by the
parameter pcDevName.
If there is no device present or there is no device that is associated with the given dwDeviceContext, then the function fails and
EC_ST_DEVICE_NOT_FOUND is returned.
If there is no memory allocated for the pcDevName parameter, then EC_ST_BAD_PARAMETER is returned.
Example
#define DEVICE_NAME_LEN 128
int i=1;
DWORD dwResult;
char pcDevName[DEVICE_NAME_LEN]="";
while ((dwResult = MTECSDK_GetDevice(i,(char*) pcDevName)) != EC_ST_DEVICE_NOT_FOUND)
{
// Device found, increment the device number
i++;
}
ExpressCard 1000 Programming Reference
MTECSDK_OpenDevice
MTECSDK_OpenDevice function opens the device with the given device name.
ULONG MTECSDK_OpenDevice (
char *pcDevName
);
Parameters
pcDevNam
e
Pointer to null terminated string that specifies the name of the device to open. Use function MTECSDK_GetDevice to
obtain the device name.
Return Values
If the function succeeds, the return value is EC_ST_OK.
EC_ST_OK
EC_ST_BAD_DEVICE_NAME
EC_ST_DEVICE_NOT_FOUND
EC_ST_DEVICE_NOT_RESPONDING
EC_ST_MSXML_NOT_FOUND
Remarks
If the pcDevName is NULL, the return value is EC_ST_BAD_DEVICE_NAME.
If no device is found, the return value is EC_ST_DEVICE_NOT_FOUND.
If MSXML is not installed, return value is EC_ST_MSXML_NOT_FOUND
If device is found but cannot connect, return value is EC_ST_DEVICE_NOT_RESPONDING
Example
#define DEVICE_NAME_LEN 128
int i=1;
DWORD dwResult;
char pcDevName[DEVICE_NAME_LEN]="";
while ((dwResult = MTECSDK_GetDevice(i,(char*) pcDevName)) != EC_ST_DEVICE_NOT_FOUND)
{
if (MTECSDK_OpenDevice (pcDevName) == EC_ST_OK)
{
///close the device
MTECSDK_CloseDevice (pcDevName);
}
i++;
}
14
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
  • Page 1 1
  • Page 2 2
  • Page 3 3
  • Page 4 4
  • Page 5 5
  • Page 6 6
  • Page 7 7
  • Page 8 8
  • Page 9 9
  • Page 10 10
  • Page 11 11
  • Page 12 12
  • Page 13 13
  • Page 14 14
  • Page 15 15
  • Page 16 16
  • Page 17 17
  • Page 18 18
  • Page 19 19
  • Page 20 20
  • Page 21 21
  • Page 22 22
  • Page 23 23
  • Page 24 24
  • Page 25 25
  • Page 26 26
  • Page 27 27
  • Page 28 28
  • Page 29 29
  • Page 30 30
  • Page 31 31
  • Page 32 32
  • Page 33 33

Magtek ExpressCard 1000 Owner's manual

Magtek
Brand
Magtek
Model
ExpressCard 1000
Type
Owner's manual

Magtek ExpressCard 1000 is a versatile device that allows its users to easily process card data in various ways. With the ExpressCard 1000, you can:

  • Process card data using a web browser interface or the ExpressCard 1000 API.
  • Get device status and information, such as the firmware version and serial number.
  • Process cards with various options, such as reading the cardholder's name, account number, and expiration date.
  • Receive error messages if the card processing fails.
Download PDF
report

Ask a question and I''ll find the answer in the document

Finding information in a document is now easier with AI

Related papers

Other documents