Elo TouchSystems Entuitive 1525L Series User Manual
  1. Manuals
  2. Brands
  3. Elo TouchSystems Manuals
  4. Monitor
  5. Entuitive 1525L Series
  6. User manual

Elo TouchSystems Entuitive 1525L Series User Manual

Elo touchsystems 15" lcd desktop touchmonitors with magnetic swipe reader (usb) user guide 1525l
Hide thumbs Also See for Entuitive 1525L Series:
Table of Contents

Advertisement

Quick Links

Download this manual
Elo Entuitive Touchmonitor User Guide
15" LCD Desktop Touchmonitor with Magnetic Swipe Reader (USB)
1525L Series
Revision A
P/N 008569
Elo TouchSystems, Inc.
1-800-ELOTOUCH
www.elotouch.com

Advertisement

Table of Contents
loading

Related Manuals for Elo TouchSystems Entuitive 1525L Series

Summary of Contents for Elo TouchSystems Entuitive 1525L Series

  • Page 1 Elo Entuitive Touchmonitor User Guide 15" LCD Desktop Touchmonitor with Magnetic Swipe Reader (USB) 1525L Series Revision A P/N 008569 Elo TouchSystems, Inc. 1-800-ELOTOUCH www.elotouch.com...
  • Page 2 Elo TouchSystems. Disclaimer The information in this document is subject to change without notice. Elo TouchSystems makes no representations or warranties with respect to the contents hereof, and specifically disclaims any implied warranties of merchantability or fitness for a particular purpose. Elo TouchSystems reserves the right to revise this publication and to make changes from time to time in the content hereof without obligation of Elo TouchSystems to notify any person of such revisions or changes.

  • Page 3: Table Of Contents

    Table of Contents Chapter 1 Introduction Precautions ....1 Chapter 2 Installation and Setup Unpacking Your Touchmonitor... 3 Product Overview .

  • Page 4: Introduction

    Congratulations on your purchase of an Elo TouchSystems Entuitive touchmonitor. Your new touchmonitor combines the reliable performance of Elo’s touch technology with the latest advances in LCD display design. This combination of features creates a natural flow of information between a user and your touchmonitor.
  • Page 5 • Serial or USB touch interface (USB requires Windows 98, 2000, Me and XP.) • Built in speakers • Patented touch technology of Elo TouchSystems • VESA DDC 1/2B data communication • VESA DPMS power saving • Stand with minimum 45° angle of tilt.

  • Page 6: Installation And Setup

    This chapter discusses how to install your LCD touchmonitor and how to install Elo TouchSystems driver software. Unpacking Your Touchmonitor Check that the following 8 items are present and in good condition: LCD Display Software User Guide-on CD, Quick Install Guide and software CD...

  • Page 7: Product Overview

    Product Overview Main Unit Rear View E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e LCD Display Stand...

  • Page 8: Side View

    Side View User Controls Base Bottom View...

  • Page 9: Touch Interface Connection

    Touch Interface Connection Your interface cables may have been pre-connected to your monitor at the factory. Your touchmonitor comes with one of the following touchscreen connector cables: Serial (RS-232) cable or USB cable. (For Windows 98, 2000, Me and XP systems only.) To set up this display, please refer to the following figures and procedures: Serial Connection The following illustrations guide you step by step in connecting your...

  • Page 10: Step 1-Removing The Back Cover

    STEP 1-Removing the Back Cover • The cables are routed through the back of the stand. • To remove the back cover, place one hand at the top of the stand and your other hand on the bottom cut-out. • Pull forward from the bottom cut-out and twist the cover until it snaps off. The cable ports are located on the underside of your touchmonitor.

  • Page 11: Step 2-Connecting The Video Cable

    STEP 2-Connecting the Video Cable Cable management clip • Tilt the screen up and back to access the connection ports. • Connect the 15-pin video cable (the ferrite bead end) to the video port on your PC. • Connect the other end of the video cable to the video connector on your touchmonitor by routing the cable through the hole in the stand.

  • Page 12: Step 3-Connecting The Serial Touchscreen Cable

    STEP 3-Connecting the Serial Touchscreen Cable • Connect the female end of the serial (RS-232) cable to the serial port on the back of your PC. • Connect the male end of the cable to the serial touchscreen connector on your touchmonitor.

  • Page 13: Step 4-Connecting The Speaker Cable

    STEP 4-Connecting the Speaker Cable If you do not wish to connect the speaker cable, go to step 5. • To use the built in speakers, you need to connect the speaker cable. Connect the speaker cable to the speaker port inside the back of your touchmonitor. •...

  • Page 14: Step 5-Connecting The Power Cable

    STEP 5-Connecting the Power Cable Cable management clip Depending on where you live, you will use either the European or US/Canadian power cable. • Connect the female end of the power cable to the power port on the touchmonitor. • Route the cable through the cable management clip. To protect your equipment against risk of damage from electrical surges in the power line, plug the touchmonitor’s power cord into a surge protector, and then connect the surge protector to a grounded AC electrical outlet.

  • Page 15: Usb Connection

    USB Connection A USB connection can only be used if your PC is running Windows 98, 2000, Me or XP. The following illustrations guide you step by step in connecting your touchmonitor using a USB cable connection. CAUTION Before connecting the cables to your touchmonitor and PC, be sure that the computer and the touchmonitor are turned off.

  • Page 16: Step 1-Removing The Back Cover

    STEP 1-Removing the Back Cover • The cables are routed through the back of the stand. • To remove the back cover, place one hand at the top of the stand and your other hand on the bottom cut-out. • Pull forward from the bottom cut-out and twist the cover until it snaps off. The cable ports are located on the underside of your touchmonitor.

  • Page 17: Step 2-Connecting The Video Cable

    STEP 2-Connecting the Video Cable Cable management clip • Tilt the screen up and back to access the connection ports. • Connect the 15-pin video cable (the ferrite bead end) to the video port on your PC. • Connect the other end of the video cable to the video connector on your touchmonitor by routing the cable through the hole in the stand.

  • Page 18: Step 3-Connecting The Usb Touchscreen Cable

    STEP 3-Connecting the USB Touchscreen Cable Cable management clip • Connect the USB touchscreen cable to the USB touchscreen connector on the touchmonitor. • Connect the other end of the USB touchscreen cable to your PC. • The touchscreen cable connectors should fit snugly into the connectors on your touchmonitor and PC.

  • Page 19: Step 4-Connecting The Speaker Cable

    STEP 4-Connecting the Speaker Cable If you do not wish to connect the speaker cable, go to step 5. • To use the built in speakers, you need to connect the speaker cable. Both ends of the speaker cable are identical, so you can connect either end of the speaker cable to the speaker port inside the stand of your touchmonitor.

  • Page 20: Step 5-Connecting The Power Cable

    STEP 5-Connecting the Power Cable Depending on where you live, you will use either the European or US/Canadian power cable. • Connect the female end of the power cable into the power port on the touchmonitor. • Route the cable through the cable management clip. To protect your equipment against risk of damage from electrical surges in the power line, plug the touchmonitor’s power cord into a surge protector, and then connect the surge protector to a grounded AC electrical outlet.

  • Page 21: Optimizing The Lcd Display

    Optimizing the LCD Display To ensure the LCD display works well with your computer, configure the display mode of your graphic card to make it less than or equal to 1024 x 768 resolution, and make sure the timing of the display mode is compatible with the LCD display.

  • Page 22: Accessing The Vesa Mounting Interface

    Accessing the VESA Mounting Interface If you want to convert your desktop monitor to a wall mount or kiosk monitor, follow the steps below to access the VESA mounting interface. You will need a screwdriver for the following steps. Remove the back cover of the stand by pulling forward on the bottom cut-out.

  • Page 23: Installing The Driver Software

    Installing the Driver Software Elo TouchSystems provides driver software that allows your touchmonitor to work with your computer. Drivers are located on the enclosed CD-ROM for the following operating systems: • Windows XP • Windows 2000 • Windows Me • Windows 98 •...

  • Page 24: Installing The Serial Touch Driver

    Installing the Serial Touch Driver for Windows XP, Windows 2000 , Me, 95/98 and NT 4.0 For Windows 2000 and NT 4.0 you must have administrator access rights to install the driver. Insert the Elo CD-ROM in your computer’s CD-ROM drive. If the AutoStart feature for your CD-ROM drive is active, the system automatically detects the CD and starts the setup program.

  • Page 25: Installing The Serial Touch Driver For Ms-Dos And Windows 3.1

    Installing the Serial Touch Driver for MS-DOS and Windows 3.1 You must have a DOS mouse driver (MOUSE.COM) installed for your mouse if you wish to continue using your mouse along with your touchmonitor in DOS. To install Windows 3.x and MS-DOS from Windows 95/98, follow the directions below: Insert the Elo CD-ROM in your computer’s CD-ROM drive.

  • Page 26: Installing The Usb Touch Driver

    Browse to select the \EloUSB directory on the Elo CD-ROM. Choose Next. Once the Elo TouchSystems USB touchscreen driver has been detected, choose Next again. You will see several files being copied. Insert your Windows 98 CD if prompted.
  • Page 27 2-24 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e...

  • Page 28: Operation

    About Touchmonitor Adjustments Your touchmonitor will unlikely require adjustment. Variations in video output and application may require adjustments to your touchmonitor to optimize the quality of the display. For best performance, your touchmonitor should be operating in native resolution, that is 1024 x 768 at 60-75 Hz. Use the Display control panel in Windows to choose 1024 x 768 resolution.

  • Page 29: Side Bezel Buttons

    Side Bezel Buttons MENU SELECT 3-26 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e Control Function Menu Display on exit the OSD menus.

  • Page 30: Osd Menu Function

    OSD Menu Function Contrast Controls the picture contrast Brightness Controls the picture brightness V-Position Controls the vertical position H-Position Controls the horizontal position Recall Defaults Recalls factory settings of the image parameters C1/C2/USER (Color) Using these icons, you can select one of the preset color temperatures (9300°K or 6500°K).
  • Page 31 3-28 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e...

  • Page 32: Troubleshooting

    If you are experiencing trouble with your touchmonitor, refer to the following table. If the problem persists, please contact your local dealer or our service center. Solutions to Common Problems Problem No image appears on screen. “Out of Range” display ROUBLESHOOTING HAPTER Suggestion(s)
  • Page 33 Image has vertical flickering line bars. Image is unstable and flickering Image is scrolling Touch doesn’t work 4-30 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e Use “PHASE”...

  • Page 34: Appendix A Native Resolution

    The native resolution of a monitor is the resolution level at which the LCD panel is designed to perform best. For the Elo LCD touchmonitor, the native resolution is 1024 x 768 for the XGA-15 inch size. In almost all cases, screen images look best when viewed at their native resolution.
  • Page 35 As an example, a SVGA resolution LCD panel has 800 pixels horizontally by 600 pixels vertically. Input video is also represented by the same terms. XGA input video has a format of 1024 pixels horizontally by 768 pixels vertically. When the input pixels contained in the video input format match the native resolution of the panel, there is a one to one correspondence of mapping of input video pixels to LCD pixels.

  • Page 36: Touchmonitor Safety

    Do not use a damaged power cord. Use only the power cord that comes with your Elo TouchSystems Touchmonitor. Use of an unauthorized power cord may invalidate your warranty.

  • Page 37: Care And Handling Of Your Touchmonitor

    Care and Handling of Your Touchmonitor The following tips will help keep your Elo Entuitive touchmonitor functioning at the optimal level. • To avoid risk of electric shock, do not disassemble the brick supply or display unit cabinet. The unit is not user serviceable. Remember to unplug the display unit from the power outlet before cleaning.

  • Page 38: Technical Specifications

    Compatible Video Modes Your Elo Entuitive touchmonitor is compatible with the following standard video modes: Mode Resolution IBM & VESA VGA 640 x 350 IBM & VESA VGA 640 x 400 IBM & VESA VGA 720 x 400 IBM & VESA VGA 640 x 480 IBM &...

  • Page 39: Touchmonitor Specifications

    Touchmonitor Specifications Table C.1 15" LCD Touchmonitor (ET15-XXWA-1) Specifications Active matrix, thin film transistor Display Type (TFT), liquid crystal display 15-inch diagonal Size 304.1 x 228.1 mm useful screen area 1024 x 768 Pixel Format 0.125-inch IntelliTouch and Touchscreen AccuTouch, anti-glare IntelliTouch or AccuTouch 16 million with dithering Colors...
  • Page 40 Table C.2 IntelliTouch Touchmonitor Specifications Mechanical Positional Accuracy Touchpoint Density Touch Activation Force Surface Durability Expected Life Performance Sealing Optical Light Transmission (per ASTM D1003) Visual Resolution Gloss (per ASTM D2457 using a 60- degree gloss meter) Standard deviation of error is less than 0.080 in. (2.03 mm). Equates to less than ±1%.
  • Page 41 Environmental Chemical Resistance Electrostatic Protection (per EN 61 000-4-2, 1995) C-38 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e The active area of the touchscreen is resistant to all chemicals that do not affect glass, such as: Acetone...
  • Page 42 Table C.3 AccuTouch Touchmonitor Specifications Mechanical Construction Positional Accuracy Touchpoint Density Touch Activation Force Surface Durability Expected Life Performance Optical Light Transmission (per ASTM D1003) Visual Resolution Haze (per ASTM D1003) Gloss (per ASTM D2457) Top: Polyester with outside hard-surface coating with clear or antiglare finish.

  • Page 43: 15" Lcd Touchmonitor (Et15-Xxwa-1) Dimensions

    15" LCD Touchmonitor (ET15-XXWA-1) Dimensions C-40 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e...
  • Page 44 See Detail A Detail A C-41...
  • Page 45 C-42 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e...

  • Page 46: Regulatory Information

    EGULATORY HAPTER I. Electrical Safety Information: A) Compliance is required with respect to the voltage, frequency, and current requirements indicated on the manufacturer’s label. Connection to a different power source than those specified herein will likely result in improper operation, damage to the equipment or pose a fire hazard if the limitations are not followed.
  • Page 47 D) General Information to all Users: This equipment generates, uses and can radi- ate radio frequency energy. If not installed and used according to this manual the equipment may cause interference with radio and television communications. There is, however, no guarantee that interference will not occur in any particular installation due to site-specific factors.
  • Page 48 N10051...
  • Page 49 E l o E n t u i t i v e T o u c h m o n i t o r U s e r G u i d e...

  • Page 50: Warranty

    ARRANTY HAPTER Except as otherwise stated herein or in an order acknowledgment delivered to Buyer, Seller warrants to Buyer that the Product shall be free of defects in materials and workmanship. The warranty for the touchmonitors and components of the product is 1 year. Seller makes no warranty regarding the model life of components.
  • Page 51 THESE REMEDIES SHALL BE THE BUYER’S EXCLUSIVE REMEDIES FOR BREACH OF WARRANTY. EXCEPT FOR THE EXPRESS WARRANTY SET FORTH ABOVE, SELLER GRANTS NO OTHER WARRANTIES, EXPRESS OR IMPLIED BY STATUTE OR OTHERWISE, REGARDING THE PRODUCTS, THEIR FITNESS FOR ANY PURPOSE, THEIR QUALITY, THEIR MERCHANTABILITY, THEIR NONINFRINGEMENT, OR OTHERWISE.

  • Page 52: Chapter 2 Installation And Setup

    Numerics 15" LCD Touchmonitor (ET15-XXWA-1) Dimensions, 40 15” LCD Touchmonitor (ET15-XXWA-1) Specifications, 36 About the Product, 1 About Touchmonitor Adjustments, 25 Accessing the VESA Mounting Interface, 19 AccuTouch Touchmonitor Specifications, 39 Agencies, 36 Auto Adjust, 27 Back-light Lamp Life, 36 Base Bottom View, 5 Brightness, 27 C1/C2/USER (Color), 27...
  • Page 53 Operation, 25 Optical, AccuTouch, 39 Optical, IntelliTouch, 37 Optimizing the LCD Display, 18 OSD H-Position, 27 OSD Language, 27 OSD Menu Function, 27 OSD Time, 27 OSD V-Position, 27 Out of Range display, 29 Phase, 27 Pixel Format, 36 Plus/Clockwise, 26 Positional Accuracy, AccuTouch, 39 Positional Accuracy, IntelliTouch, 37 Power Switch, 26...

  • Page 54: Msr Reference Manual

    USB (UNIVERSAL SERIAL BUS) SWIPE READER TECHNICAL REFERENCE MANUAL Manual Part Number 99875191 Rev 4 AUGUST 2001 20725 South Annalee Avenue Carson, CA 90746 Phone: (310) 631-8602 FAX: (310) 631-3956 Technical Support: (888) 624-8350 www.magtek.com...
  • Page 55 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 Mag-Tek, Inc. Mag-Tek is a registered trademark of Mag-Tek, Inc.
  • Page 56 Limited Warranty Mag-Tek, Inc. (hereinafter “Mag-Tek”) warrants this Mag-Tek product IN ITS ENTIRETY, to be in good working order for a period of one year from the date of purchase from Mag-Tek. Should this product fail to be in good working order at any time during this warranty period, Mag-Tek will, at its option, repair or replace this product at no additional charge except as set forth below.
  • Page 57 FCC WARNING STATEMENT This equipment has been tested and found to comply with the limits for Class B digital device, pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a residential environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications.
  • Page 58 SECTION 1. FEATURES AND SPECIFICATIONS...57 FEATURES ...57 CONFIGURATIONS...58 ACCESSORIES ...58 REFERENCE DOCUMENTS...58 SPECIFICATIONS ...58 SECTION 2. INSTALLATION ...61 USB CONNECTION...61 WINDOWS PLUG AND PLAY SETUP ...62 MOUNTING...62 SECTION 3. OPERATION ...65 LED INDICATOR ...65 CARD READ ...65 SECTION 4. USB COMMUNICATIONS ...67 HID USAGES ...67 REPORT DESCRIPTOR...68 CARD DATA ...69...

  • Page 59: Figure 1-1. Usb Swipe Reader

    Figure 1-1. USB Swipe Reader...

  • Page 60: Section 1. Features And Specifications

    SECTION 1. FEATURES AND SPECIFICATIONS The USB (Universal Serial Bus) Swipe Reader is a compact magnetic stripe card reader which conforms to ISO standards. The Reader is compatible with the PC series of personal computers or any device with a USB interface. A card is read by sliding it, stripe down and facing the LED side, through the slot either forward or backward.

  • Page 61: Configurations

    USB Swipe Reader CONFIGURATIONS The Configurations are as follows: Part Number P/N 21040101 P/N 21040102 P/N 21040103 P/N 21040104 P/N 21040105 P/N 21040106 ACCESSORIES The accessories are as follows: Part Number 21042806 99510026 REFERENCE DOCUMENTS Axelson, Jan. USB Complete, Everything You Need to Develop Custom USB Peripherals, 1999. Lakeview Research, 2209 Winnebago St., Madison WI 53704, 396pp., http://www.lvr.com.

  • Page 62: Figure 1-2. Dimensions

    Reference Standards Power Input Recording Method Message Format Card Speed MTBF Current Normal Mode Suspend Mode MECHANICAL (STANDARD PRODUCT) Weight Cable length Connector Temperature Operating Storage Humidity Operating Storage Altitude Operating Storage * ISO (International Standards Organization), CDL (California Drivers License), and AAMVA (American Association of Motor Vehicle Administrators).
  • Page 63 USB Swipe Reader...

  • Page 64: Section 2. Installation

    SECTION 2. INSTALLATION This section describes the cable connection, the Windows Plug and Play Setup, and the physical mounting of the unit. USB CONNECTION Connect the USB cable to a USB port on the host. The Reader, LED Indicator, and pin numbers for the 4-pin connector are shown in Figure 2-1.

  • Page 65: Windows Plug And Play Setup

    USB Swipe Reader WINDOWS PLUG AND PLAY SETUP On hosts with the Windows operating system, the first time the device is plugged into a specific USB port, Windows will pop up a dialog box, which will guide you through the process of installing a device driver for the device.

  • Page 66: Figure 2-2. Mounting Hole Dimensions For Surface

    Figure 2-2. Mounting Hole Dimensions For Surface Ensure the Reader is positioned on a flat, accessible surface with at least 4 inches clearance on either end for room to swipe a card. Orient the Reader so the side with the LED is facing the direction of intended use.
  • Page 67 USB Swipe Reader...

  • Page 68: Section 3. Operation

    SECTION 3. OPERATION This section describes the LED Indicator and Card Read. LED INDICATOR The LED indicator will be either off, red, or green. When the device is not powered, the LED will be off. When the device is first plugged in, the LED will be red. As soon as the device is plugged in, the host will try to enumerate the device.
  • Page 69 USB Swipe Reader...

  • Page 70: Section 4. Usb Communications

    SECTION 4. USB COMMUNICATIONS This device conforms to the USB specification revision 1.1. This device also conforms with the Human Interface Device (HID) class specification version 1.1. The device communicates to the host as a vendor defined HID device. The details about how the card data and commands are structured into HID reports follow later in this section.

  • Page 71: Report Descriptor

    USB Swipe Reader following table. The usage types are also listed. These usage types are defined in the HID Usage Tables document. Magnetic Stripe Reader usage page 0xff00: Usage ID Usage Name (Hex) Decoding reader device Track 1 decode status Track 2 decode status Track 3 decode status Track 1 data length...

  • Page 72: Card Data

    Item Usage (Card encode type) Report Count (7) Input (Data, Variable, Absolute, Bit Field) Usage (Track 1 data) Report Count (110) Input (Data, Variable, Absolute, Buffered Bytes) Usage (Track 2 data) Report Count (110) Input (Data, Variable, Absolute, Buffered Bytes) Usage (Track 3 data) Report Count (110) Input (Data, Variable, Absolute,...

  • Page 73: Track 1 Decode Status

    USB Swipe Reader TRACK 1 DECODE STATUS Bits Value Reserved Error This is a one-byte value, which indicates the status of decoding track 1. Bit position zero indicates there was an error decoding track 1 if the bit is set to 1. If it is zero, then no error occurred.

  • Page 74: Card Encode Type

    CARD ENCODE TYPE This one byte value indicates the type of encoding that was found on the card. The following table defines the possible values. Value Encode Type ISO/ABA AAMVA CADL Blank Other Undetermined None TRACK DATA If decodable track data exits for a given track, it is located in the track data field that corresponds to the track number.

  • Page 75: Commands

    USB Swipe Reader COMMANDS Most host applications do not need to send commands to the device. Most host applications only need to obtain card data from the device as described previously in this section. This section of the manual can be ignored by anyone who does not need to send commands to the device.

  • Page 76: Result Code

    RESULT CODE This one byte field contains the value of the result code. There are two types of result codes: generic result codes and command specific result codes. Generic result codes always have the most significant bit set to zero. Generic result codes have the same meaning for all commands and can be used by any command.

  • Page 77: Software_Id Property

    USB Swipe Reader Property ID is a one byte field that contains a value that identifies the property. The following table lists all the current property ID values: Value Property ID SOFTWARE_ID SERIAL_NUM POLLING_INTERVAL The Property Value is a multiple byte field that contains the value of the property. The number of bytes in this field depends on the type of property and the length of the property.

  • Page 78: Serial_Num Property

    SERIAL_NUM PROPERTY Property ID: Property Type: String Length: 0 – 15 bytes Get Property: Set Property: Default Value: The default value is no string with a length of zero. Description: The value is an ASCII string that represents the device’s serial number. This string can be 0 –...
  • Page 79 USB Swipe Reader will be sent to the host when the host requests the device’s USB endpoint descriptor. When this property is changed, the unit must be power cycled to have these changes take effect for the USB descriptor. If a value other than the default value is desired, it can be set by the factory upon request.

  • Page 80: Section 5. Demo Program

    SECTION 5. DEMO PROGRAM The demo program, which is written in Visual Basic, can be used to do the following: • Read cards from the device and view the card data • Send command requests to the device and view the command responses •...

  • Page 81: Source Code

    USB Swipe Reader SOURCE CODE Source code is included with the demo program. It can be used as a guide for application development. It is described in detail, with comments, to assist developers. The book USB Complete by Jan Axelson is also a good guide for application developers, especially the chapter on Human Interface Device Host Applications (see “Reference Documents”...

  • Page 82: Programming Reference Manual

    MAGTEK DEVICE DRIVERS FOR WINDOWS PROGRAMMING REFERENCE MANUAL Manual Part Number: 99875125 Rev 6 NOVEMBER 2001 20725 South Annalee Avenue Carson, CA 90746 Phone: (310) 631-8602 FAX: (310) 631-3956 Technical Support: (888) 624-8350 www.MagTek.com...
  • Page 83 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 Mag-Tek, Inc. MagTek is a registered trademark of Mag-Tek, Inc.

  • Page 84: Limited Warranty

    Limited Warranty Mag-Tek, Inc. (hereinafter “Mag-Tek”) warrants this Mag-Tek product IN ITS ENTIRETY, to be in good working order for a period of 90 days from the date of purchase from Mag-Tek. Should this product fail to be in good working order at any time during this warranty period, Mag-Tek will, at its option, repair or replace this product at no additional charge except as set forth below.

  • Page 85: Table Of Contents

    SECTION 1. OVERVIEW ...87 PROBLEMS WITH CONTROLLING DEVICES ...87 BENEFITS OF A CONTROL LANGUAGE AND DRIVER ...88 LANGUAGE OVERVIEW ...89 Properties...89 COMMANDS ...90 TYPICAL OPERATION ...91 Open a device...91 Query the device’s capabilities ...91 Prepare the device for work ...91 Use the device ...91 Close the device ...92 METHODS OF ACCESSING THE DEVICE ...92...
  • Page 86 enc_key...99 enc_key_sn...99 enc_mode ...99 entry_echo ...99 entry_len ...99 entry_tout ...99 events_on ...99 invalcmdrsp...99 key_parity...99 lasterr ...99 max_pin_len...99 msg1 - msg4 ...99 oper_tout ...100 pin_blk_fmt...100 pinfilldig ...100 port_name...100 pwroffdelay...100 s_down_tout...100 track1ss...100 trivpinchk ...100 trk_enable ...100 trk1data ...100 trk2data ...100 trk3data ...100 visa_mac1...100 visa_mac2...100 visa_mac3...100...
  • Page 87 DESCRIPTION...116 LANGUAGE FORMAT ...117 Format Name ...117 Format Template...117 Format Rules ...117 DEFAULT FORMATS ...121 EXAMPLE ...122 Retrieving properties from a magnetic card...122 SECTION 5. EXAMPLE APPLICATIONS ...125 PROGRAMMING HINTS ...125 VISUAL BASIC EXAMPLE...125 C++ EXAMPLE ...131 POWER BUILDER EXAMPLE ...136 APPENDIX A.
  • Page 88 MT-95 HICO ENCODER...174 INDEX...175 FIGURES Figure 1-1. MagTek Devices and Device Drivers for Windows...86 Figure A-1. Properties Settings, Windows 95 ...144 Figure A-2. Advanced Settings, Windows 95 ...144...
  • Page 89 MagTek Device Drivers for Windows Figure 1-1. MagTek Devices and Device Drivers for Windows...

  • Page 90: Section 1. Overview

    SECTION 1. OVERVIEW The MagTek Device (MTD) Drivers for Windows is a collection of individual drivers that support a number of MagTek products. These drivers provide a uniform application interface for controlling a wide range of MagTek devices. The drivers, combined with a device control language, solve many of the difficulties application developers face when attempting to control hardware devices.
  • Page 91 MagTek Device Drivers for Windows • MagTek devices are attached to the host in different ways. MagTek devices may be attached to a serial port, parallel port, to another device or even to the keyboard port. All these ports differ greatly in nature and would all have to be accessed by the application. Additionally, meaningful communication with a device attached to the keyboard port would be tricky at best.

  • Page 92: Language Overview

    usually remain unchanged, even though the new device may be very different from the old one. The features of a driver that implement a device control language completely shield an application developer from the complexities of device-specific functionality. LANGUAGE OVERVIEW The device control language is text based and designed to utilize the read and write file I/O facilities of the underlying operating system.
  • Page 93 MagTek Device Drivers for Windows COMMANDS Like properties, commands are identified by a string name and have string arguments. All commands are terminated by line feed <LF> or a carriage return. To invoke a command, an application simply writes it to the driver in the same manner as writing to a file or serial port. If the command has a response defined for it, the application reads it from the driver using the same I/O handle as in the write.

  • Page 94: Typical Operation

    Section 1. Overview TYPICAL OPERATION This section describes a typical pattern that an application developer may use to operate a device. Although it is the most typical pattern, it is by no means the only viable one. Refer to Section 5, Example Applications, to see how to use the drivers in various applications.

  • Page 95: Close The Device

    MagTek Device Drivers for Windows instruct the device to return the card data when swiped. All the facilities of the driver are utilized during this stage of operation. Close the device When the application is finished with the device, it simply closes the port using the handle obtained when it opened it.

  • Page 96: Interacting With The Device

    Settings tab. This gives both the Friendly Name and the port name ( identifies the physical port that will be used to communicate with the device. Open the device using either of the previous names. Use whatever facility is provided by your development environment for opening files.

  • Page 97: Releasing Access To The Device

    MagTek Device Drivers for Windows ‘set up error handling On Error Resume Next ‘submit echo command Put #1, , "/echo Hello" + Chr$(10) ‘declare an input buffer a$ = String(2000, Chr$(0)) ‘read echo response from device Get #1, , a$ If Err.Number <>...

  • Page 98: Handling Special Commands

    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. It can reset the device and prompt the user to repeat the action.

  • Page 99: Micr Format Numbers

    MagTek Device Drivers for Windows Installation And Setup) and select Properties. Click on the Version tab. Note the File Version, Part Number, and Description. INSTALLATION The drivers are installed by means of the Windows “Add New Hardware” facility in Windows 95/98/ME and the "INF"...

  • Page 100: Section 2. Properties

    SECTION 2. PROPERTIES This section lists the properties that are used in the MagTek Drivers. Properties can be interrogated by issuing a Commands for complete description and examples of all commands. properties are set by the driver and reflect the device’s capabilities. However, the c_xxx properties do not indicate the configuration of the device.
  • Page 101 MagTek Device Drivers for Windows Property Access c_write indicated in c_wr_secure (see Set this to capitalize read Current card sensor status: card_stat Check account number from check (MICR). chk_account Check amount from check (MICR). chk_amount Bank ID number from the transit field (MICR). chk_bankid Output data string as received from MICR reader (MICR).
  • Page 102 Property Access Encryption key to use for the next encryption process (IntelliPIN): enc_key Serial number of encryption key. Used to specify key serial enc_key_sn number for activating/deactivating PIN encryption in MSK mode and to return the key serial number in DUKPT mode. The key serial number is specified in clear text (IntelliPIN).
  • Page 103 MagTek Device Drivers for Windows Property Access Set to offline_enc keyboard; Operational timeout in seconds (15-255). (IntelliPIN) oper_tout PIN block format (IntelliPIN): pin_blk_fmt PIN fill digit (0..9, A..F) when pinfilldig Indicates the virtual port number (e.g., COM6) derived from the port_name friendly port name.
  • Page 104 SECTION 3. COMMANDS This section describes all of the commands that can be used with the MagTek Windows Device Drivers. Some commands require parameters to indicate to the driver exactly what function is to be performed. While there are a few device-specific commands, most commands can be used with any device.

  • Page 105: Notation Conventions

    MagTek Device Drivers for Windows Examples: 000000000011111111112222222222 012345678901234567890123456789 /read /get trk_enable NOTATION CONVENTIONS The following conventions are used in the tables that follow. Used to represent literals (symbols, exactly as sent or received Fixed Size (Bold) from driver) Italic Used to represent placeholders (variable fields) Expression parts in brackets are optional.
  • Page 106 display Function Show a single message or two alternating messages on the device’s display. Syntax /display The optional argument x indicates the message to be displayed. Errors none Remarks If the optional argument x is provided, this command displays it as a single message. If x is , the driver sends a command to the device to display the idle message (“Welcome”).
  • Page 107 MagTek Device Drivers for Windows event Function Response to an unsolicited event notification. Syntax none Errors none Remarks This response can occur when an unsolicited event, such as card inserted, occurs. The format of the response is: n is a numeric event code: –...
  • Page 108 load_key Function Load an encryption key into the device. Syntax n key /load_key n can be one of the following values: – master key (key is in clear text) – session key (key is encrypted under Master Key) – lower working keys (key is encrypted under Session Key) –...
  • Page 109 MagTek Device Drivers for Windows rawrecv Function Receive data from the device. Syntax /rawrecv Errors /rawrecv If a command is already pending. /rawrecv If the command was canceled by the user (e.g., with CLEAR key) Remarks This command overrides the default processing of the next message that comes from the device and returns it to the application as a message from the device will be processed in this manner, after that the driver switches to normal operation.
  • Page 110 rawsend Function Send arbitrary data to the device. Syntax /rawsend x x is an arbitrary string which is transmitted directly to the device. The string x is passed as-is to the device, except for ‘\’ which is used as an ‘escape’ character: •...
  • Page 111 MagTek Device Drivers for Windows read Function Read data from the device. Syntax [[x] y] /read The optional argument x specifies the data source; if x is missing, a card will be read. Refer to the Read Argument table below for a description data sources. The optional argument y is used to specify a message to be displayed on the LCD screen, if supported, before carrying out the command.
  • Page 112 Read Arguments The optional argument x used in the specifies the text to be displayed. The following table describes the recognized x arguments for command: read Read Description Argument Read any type of data. This option is equivalent to Read magnetic stripe card. Display message ( card When the user swipes a card, the response will be in the following format: /read M...
  • Page 113 MagTek Device Drivers for Windows Read Description Argument Read magnetic stripe card or check data. When a card or check is swiped chk_or_card through the device, the driver sends the respective response. Display a message ( key_press key on the keypad to be pressed. The device will wait for seconds for the key press (by default 0 for no timeout).
  • Page 114 Read Description Argument Collect PIN from cardholder and read PIN data from the device. The following properties may be set before issuing this command: • account_no if required • amount required • enc_key S for session, 0-3 for lower working keys, A-J for upper working keys. •...
  • Page 115 reset Function Reset the device. Syntax /reset Errors none Remarks Clear any pending operations and reset the device to initial state (for mechanized card devices this command will also eject the card). This does not affect any of the properties. Example To return a device to its initial state: Command...
  • Page 116 write Function Data encode command. Syntax data /write Errors /write Encode is not supported on this device. /write The data field was in the incorrect format. /write command was canceled. write /write Device in wrong mode (e.g., if /read already issued) /write Error during write operation (e.g., on MT-95) Remarks...
  • Page 117 MagTek Device Drivers for Windows...
  • Page 118 SECTION 4. MAGNETIC CARD DATA PARSING This section describes the flexible data parsing language to be used by the MagTek device drivers to parse specific fields from magnetic card data and expose those fields as properties which may be retrieved by an application using the /get command. The data parsing language is flexible in that it can define both standard and custom formats to be parsed by the driver.

  • Page 119: Description

    MagTek Device Drivers for Windows • Property names specified in format rules are 11 characters or less, consisting of alphabetic characters, digits, and ‘_’. The property name begins with an alphabetic character. • Properties used in format strings do not conflict with properties defined by the driver. If there is a duplicate property (e.g., dev_version) specified in the format strings, the driver will return the value of the parsed property rather than the device version string.

  • Page 120: Language Format

    Section 4. Magnetic Card Data Parsing If the driver is successful in applying one of the rules, the name of the applied format is available in the property applied_fmt. LANGUAGE FORMAT Format Name (fmtx_name) The format name specifies an identifier by which to identify the format template and/or rules being applied.
  • Page 121 MagTek Device Drivers for Windows A format rule describes how the data is to be parsed. Characters that must be matched as literals are placed as is in the string or preceded with a ‘\’ if the character is one of the following: ‘[’, ‘]’, ‘(’, ‘)’, ‘*’, ‘_’, ‘<’, ‘>’, ‘:’, ‘.’, or ‘\’.
  • Page 122 Field Type Example Literal Non-ASCII literal \r, \n, \\, \xhh Optional choice (x|y|…) Optional field Optional track {xy} There can be more than one rule specified for a particular format template. The rules should be placed in a single string enclosed in curly braces (i.e., ‘{’ and ‘}’) and delimited with commas ‘,’.
  • Page 123 MagTek Device Drivers for Windows The property name can also contain a modifier at the end preceded by a ‘:’ which specifies the type of data to store in that property. For example <cust_name:A> specifies that customer name should contain alphabetic characters, spaces, and punctuation. The modifier may also be used with ignore-fields (i.e., <*>).

  • Page 124: Default Formats

    DEFAULT FORMATS The MTD drivers will be assigned parameters with default formats for parsing magnetic stripe data. The formats will be placed in the INF file for the driver and written to the registry when the driver is installed. Some examples are shown below; more are included with the drivers. In these examples, spaces are inserted between fields for readability;...

  • Page 125: Example

    MagTek Device Drivers for Windows 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.
  • Page 126 Section 4. Magnetic Card Data Parsing The application issues /get applied_fmt. The driver responds with /get applied_fmt BankCard. The application issues /get FirstName to the driver. The driver responds with /get FirstName JOHN. The application issues /get LastName to the driver. The driver responds with /get LastName SMITH.
  • Page 127 MagTek Device Drivers for Windows...

  • Page 128: Section 5. Example Applications

    SECTION 5. EXAMPLE APPLICATIONS While each application in this section is oriented toward a specific programming language, different devices are addressed in each example. It may be useful for the reader to look at all examples to understand how the MagTek Windows Drivers can operate with various MagTek devices. PROGRAMMING HINTS When opening a Keyboard Wedge device, the application must wait for any key press to complete, e.g., ALT-0.
  • Page 129 MagTek Device Drivers for Windows ' The form needs to contain: 1) an "MSComm" object named MSComm1 2) a button named btnStart, should be set to Enabled and Visible with the caption "Start" 3) a button named btnRead, should be set to Disabled and Visible with caption "Read"...
  • Page 130 MSComm1.Output = "/read card" & Chr$(10) ' If the device has check reading capability, then the ' following command would be used to read only the check ' data ' MSComm1.Output = "/read check" & Chr$(10) ' If the device can read only one media type (e.g. a ' card reader) then the read command "/read"...
  • Page 131 MagTek Device Drivers for Windows ' will hold the numeric port number Dim PortNumber As Integer ' prevent the Start button from being pressed again btnStart.Enabled = False txtInfo.Text = "Please wait. txtInfo.Refresh ' declare space for an input buffer buf$ = String(2000, Chr$(0)) ' If the virtual serial port number is unknown, it can be ' obtained by opening the driver in "File"...
  • Page 132 If Err.Number <> 0 Then ' Process error using Err.Description ' contains error description for the demo, ' we'll just display it txtInfo.Text = Err.Description ' Reset the error handling On Error GoTo 0 ' exit this sub Exit Sub End If ' reset the error handling On Error GoTo 0...
  • Page 133 MagTek Device Drivers for Windows ' Set the com port number retrieved from the response MSComm1.CommPort = PortNumber ' Open the com port and establish communications with the device MSComm1.PortOpen = True ' enable the read button btnRead.Enabled = True txtInfo.Text = "Click on the Read button to read a”...

  • Page 134: C++ Example

    C++ EXAMPLE The following is an example of C++: /* -------------------------------------------------------------------------- */ MTDTEST.C - Test module for Mag-Tek device drivers /* -------------------------------------------------------------------------- */ /* Version 1.00 /* -------------------------------------------------------------------------- */ #include <windows.h> #include <stdio.h> #include <conio.h> #include <string.h> /* --- Static variables ----------------------------------------------------- */ static volatile BOOL quit = FALSE;...
  • Page 135 MagTek Device Drivers for Windows /** clear overlapped structure */ memset ( &ov_r, 0, sizeof (ov_r) ); memset ( &ov_w, 0, sizeof (ov_w) ); if (argc < 2) drv_h = OPEN_DEVICE ("COM5"); else drv_h = OPEN_DEVICE (argv[1]); if (drv_h == INVALID_HANDLE_VALUE) ws = GetLastError();...
  • Page 136 NULL, (LPTHREAD_START_ROUTINE)input_thread,// addr of thread function NULL, &retdw "Can't Create input thread" ); in_threadh = ret_h; Sleep(100); printf("\nTest Console started. (press <^Z> to terminate).\n"); } while (0); switch ( stage) case 9: WaitForSingleObject (in_threadh, INFINITE); printf ("\n"); case 8: quit = TRUE; ws = WaitForSingleObject ( out_threadh, 300);...
  • Page 137 MagTek Device Drivers for Windows #else gets(str); strcat(str, "\n"); ch = str[0]; #endif switch (ch) case 0x1a: printf("\n---Exit---\n");//@@ quit = TRUE; break; default: if (ch < 0x100) BOOL DWORD #ifdef SINGLE_CHARS rs = WriteFile(drv_h, &ch, 1, &ret_len, &ov_w); #else rs = WriteFile(drv_h, str, strlen(str), &ret_len, &ov_w); #endif if (!rs) ws = GetLastError ();...
  • Page 138 DWORD read_len=0; char wbuff[1]; char* while (!quit) rs = ReadFile(drv_h, wbuff, sizeof(wbuff), &read_len, &ov_r); if ( !rs) rs = GetLastError (); if ( rs != ERROR_IO_PENDING) printf("DeviceIOControl (Read) Error : %i (0x%x)\n", rs, rs ); break; rs = WaitForSingleObject ( ov_r.hEvent, INFINITE); rs = GetOverlappedResult ( drv_h, &ov_r,...

  • Page 139: Power Builder Example

    MagTek Device Drivers for Windows POWER BUILDER EXAMPLE The following example illustrates how to set up PowerBuilder (from Sybase) to read magnetic data from the IntelliPIN device. Since PowerBuilder does not interface to a serial port very easily, a third-party OCX is required.
  • Page 140 8. Close the PowerScript Painter window and answer “Yes” to “Save changes…”. 9. Close the Window Painter window and answer “Yes” to “Save changes…”. At the “Save Window” dialog box, enter “ole_io” then click “OK”. 10. Open the PowerScript window for the main application and integrate the following commands into the application.
  • Page 141 MagTek Device Drivers for Windows...

  • Page 142: Appendix A. Installation And Setup

    APPENDIX A. INSTALLATION AND SETUP The distribution disks contain the MTD Driver files for many of the MagTek products. In addition to the drivers, there are number of files that are required to support the installation and operation of these drivers. The disk contents are listed in the tables below. Some of the Drivers support multiple configurations of the associated product.

  • Page 143: Installing Device Drivers (W95/98/Me)

    MagTek Device Drivers for Windows INSTALLING DEVICE DRIVERS (W95/98/ME) File or Directory Name OEMSETUP.INF README.TXT \W95_DRV Directory DMAPLD.VXD DMVXD.VXD DMVXDD.VXD GENERIC.VXD IntelliPIN RS-232 IPIN.VXD IntelliPIN Wedge IntelliPIN MICR Aux MAGCDFLT.DLL MAGCDFLT.HLP MAG-TEKCL.DLL MAG-TEKCL.VXD Mag-Wedge MAGWEDGE.VXD MICR+ MICRPLUS.VXD Mini MICR RS-232 MINIMICR.VXD Mini MICR Wedge MiniWedge...

  • Page 144: Adding The First Device Driver (W95/98/Me)

    General Notes: The computer and device should be powered off when connecting any devices. Although you do not have to have the device connected to install the driver, it is highly recommended. This allows the device and driver to be tested when the driver is installed. Note which hardware port each device is using on the computer as this information will be used later in the driver installation process.

  • Page 145: Updating An Installed Device Driver (W95/98/Me)

    Select MagTek from the list of Hardware Types, then click the Next button. Select the device to be installed from the displayed list box and click the Next button. Click the Finish button. The computer will take a moment to install the driver. Please be patient.

  • Page 146: Modifying A Device Driver's Settings (W95/98/Me)

    Either accept the default selection for the virtual Port Name or select the desired port (COM5-COM15) to be associated with the device from the Port Name combo box and modify the device’s friendly name if the default is not acceptable. Select the port to which the device is connected (see General Notes in Installing Device Drivers (W95/98/ME) above) from the Connect to combo box.
  • Page 147 MagTek Device Drivers for Windows Figure A-1. Properties Settings, Windows 95/98/ME Figure A-2. Advanced Settings, Windows 95/98/ME...

  • Page 148: Removing The Drivers (W95/98/Me)

    Removing the Drivers (W95/98/ME) The following assumes familiarity with the Registry Editor. Improper use of the Registry Editor can cause Windows to cease to function. Please follow the instructions carefully. Complete removal of the drivers requires two steps: (1) remove the drivers from the system using the Device Manager and (2) remove the driver files manually after all devices have been removed by the Device Manager.
  • Page 149 MagTek Device Drivers for Windows MAGCDFLT.DLL MAGCxxx.HLP MAGCxxx.DLL 7. Find and remove the copy of the Mag-TekOEMSETUP.INF file made by Windows. In release 1 of Windows 95, it is located in C:\Windows\inf\. With the OSR2 release of Windows 95 (Win95B) and Windows 98/ME, the files will be located in C:\Windows\inf\other\.

  • Page 150: Installing Device Drivers (Wnt)

    INSTALLING DEVICE DRIVERS (WNT) File or Directory Name OEMSETUP.INF README.TXT Directory \WNT_DRV DMAPLD.DLL DMNTK.DLL DMNTKD.DLL GENERIC.SYS IntelliPIN RS-232 IPIN.SYS IntelliPIN Wedge IntelliPIN MICR Aux MAG-TEKCL.SYS Mag-Wedge MAGWEDGE.SYS MICR+ MICRPLUS.SYS Mini MICR RS-232 MINIMICR.SYS Mini MICR Wedge MiniWedge MINIWEDG.SYS MT-85 MT85.SYS MT-95 MT95.SYS MTCFG.EXE...

  • Page 151: Installing The Driver Binaries (Wnt)

    MagTek Device Drivers for Windows Wizard. Open the Wizard by double clicking on the Add/Remove Programs icon in the Control Panel. On the Install/Uninstall tab. Find and select the entry that reads MTD preliminary release (uninstall) Mag-Tek Device Drivers (MTD) - uninstall then click on the Add/Remove button.

  • Page 152: Installing Device Drivers (Wnt)

    INSTALLING DEVICE DRIVERS (W2000/XP) File or Directory Name MTD_KBH.INF MTD_KBH.SYS OEMSETUP.INF README.TXT Directory \I386 Directory \W2K_DRV DMNTK.DLL DMNTKD.DLL GENERIC.SYS IntelliPIN RS-232 IPIN.SYS IntelliPIN Wedge IntelliPIN MICR Aux MAGTEKCL.SYS Mag-Wedge MAGWEDGE.SYS MICR+ MICRPLUS.SYS Mini MICR RS-232 MINIMICR.SYS Mini MICR Wedge MiniWedge MINIWEDG.SYS MT-85 MT85.SYS...

  • Page 153: Installing The Driver Binaries (Wnt)

    MagTek Device Drivers for Windows In Windows 2000/XP, only users with Administrator privileges may install system components. Log on as Administrator (or as a user with full administrative privileges) before attempting to install the MTD driver. It is important to uninstall the previous version of MTD and re-boot the system before installing this version of the driver.

  • Page 154: Installing Device Drivers (W2000/Xp)

    Click the “Next” button to advance to the next input screen. Click on "Yes" to the "Digital Signature Not Found". Click "Finish". Click "Close" on the "System" dialog. Answer "Yes" to the "Restart System" prompt. If, during the installation, a strange behavior is observed - failure, or some other unexpected error−a system reboot is necessary before continuing or repeating the failed operation.

  • Page 155: Installing The Driver Binaries (W2000/Xp)

    MagTek Device Drivers for Windows 12. Uncheck all “Optional search locations” check boxes. 13. Click the “Next” button to advance to the next input screen. 14. Click the “Next” button to advance to the next input screen. 15. Answer "Yes" to the "Confirm Driver Install". (Note: This uninstallation procedure may hang at step 15.

  • Page 156: Adding A Serial Device (Wnt/W2000/Xp)

    MTD was successfully re-started. The changes you made are now in effect. Only a single keyboard device can be installed at a time. Adding a Serial Device (WNT/2000/XP) Mini MICR is used in the following example: 1. Select an unused COM port number for the device. Choose any number between 5 and 255 that is not used by other devices (if in doubt, check the Ports Control panel−it displays all COMx names currently used).

  • Page 157: Windows Nt/W2000/Xp Configuration Utility

    MagTek Device Drivers for Windows and MTD device will appear as COM7. The MICR+ device appears to the system as COM12 and has a friendly name : MICR+.) Two examples are shown: mtcfg COM7 "IntelliPIN MICR Aux" "UsePort=AUX port on MICR+" mtcfg COM7 "IntelliPIN MICR Aux"...

  • Page 158: Command Syntax Summary

    Command syntax summary Command Syntax mtcfg mtcfg -? mtcfg -help mtcfg -models mtcfg port-name mtcfg port-name –allmore mtcfg port-name model [settings] mtcfg port-name –delete mtcfg port-name settings * these commands require Administrator privilege. MTCFG will display an error message if the current user is not an Administrator. Displaying Configuration Information (WNT/2000/XP) To display the list of configured MagTek devices, use the following syntax: mtcfg...

  • Page 159: Viewing The List Of Configured Devices (Wnt/W2000/Xp)

    MagTek Device Drivers for Windows model is the full name of the device model to be added. The name should be enclosed in quotes if it contains spaces. Use " list of models. The model names used by MTCFG are the ones specified in the [Models] section of the MTD installation script (OEMSETUP.INF).

  • Page 160: Configuration Examples Of Nt/W2000/Xp

    Configuration Examples for Windows NT/2000/XP These examples are for illustration only. Most of the command line entries will have to be modified to accommodate the actual installation. Device or driver Generic RS-232 MTCFG COM5 "Generic Serial (RS- 232)" FriendlyName=MT-80 UsePort=COM1 baud=4800 parity=0 datasize=7 Generic KB MTCFG COM6 "Generic Wedge...

  • Page 161: Modifying A Device Driver's Settings (Wnt/W2000/Xp)

    MagTek Device Drivers for Windows Modifying a Device Driver's Settings (WNT/2000/XP) Use the following syntax to change settings of a device: mtcfg <port-name> <setting1> [<setting2> [<setting3>...]] each of the settings is specified as name=value if value contains spaces, the whole name=value string should be enclosed in quotes (not just the value), e.g., to specify the string “MT-85 on COM1”...

  • Page 162: Removing A Device (Wnt/W2000/Xp))

    Removing a Device (WNT/2000/XP) To remove a MagTek device use the following command syntax: mtcfg port-name -delete The device is removed and all non-default settings specified for it are lost. This operation does not remove any files from the system. To remove all devices and uninstall the MTD driver, follow the instructions in the next section.
  • Page 163 MagTek Device Drivers for Windows...

  • Page 164: Appendix B. Command List Summary

    APPENDIX B. COMMAND LIST SUMMARY This is a consolidated list of all available commands for the MagTek Windows Drivers. Command Description Cancel a command. cmd can be any of the transaction /cancel commands. Display a message or two alternating messages on the LCD /display screen.
  • Page 165 MagTek Device Drivers for Windows...

  • Page 166: Appendix C. Status Codes

    APPENDIX C. STATUS CODES The following table defines the status codes returned in command responses. Note that it is not meant as a complete list of status codes–new codes may be added as necessary. Value successful operation port already open wrong device ID value, buffer, whatever may overflow value not valid in operation context...
  • Page 167 MagTek Device Drivers for Windows...

  • Page 168: Appendix D. Device Driver Summaries

    APPENDIX D. DEVICE DRIVER SUMMARIES This section contains summaries of Device Drivers for the for the following models: • IntelliPIN and IntelliPIN PLUS • MagWedge Reader • MiniWedge Reader • MICR+ Reader • Mini-MICR Reader • Port Powered RS-232 Swipe Reader •...

  • Page 169: Intellipin Pinpad & Msr

    MagTek Device Drivers for Windows INTELLIPIN PINPAD & MSR File Name IPIN.VXD Friendly Name(s) IntelliPIN RS-232, IntelliPIN Wedge & IntelliPIN MICR+ Aux Remarks The Automatic Settings in the properties sheet are not supported; the communications must be specified manually. When using the IntelliPIN on the MICR+ Aux port, the MICR+ driver must be installed before the IntelliPIN driver;...

  • Page 170: Magwedge Swipe Reader

    MAGWEDGE SWIPE READER File Name MAGWEDGE.VXD MagWedge Friendly Name(s) Remarks The driver cannot determine which tracks are supported on the device, so the indicate /cancel cmd /display [x] /echo string n data /event /get prop Property Default account_no amount ✔ ✔ ✔ ✔ applied_fmt c_card_stat c_cardwpin...

  • Page 171: Miniwedge Msr

    MagTek Device Drivers for Windows MINIWEDGE MSR File Name MINIWEDG.VXD Friendly Name(s) MiniWedge Remarks When operating in the Windows Driver mode, the MiniWedge transmits data as ASCII characters instead of scan codes in order to reduce the transmission time. (A full 3-track card can be transmitted in about 0.5 second whereas in the non-driver mode it would take almost 4 seconds.) If this creates problems in certain hardware implementations, the skip_ascii and dev_char_delay parameters in the registry...

  • Page 172: Micr+ Check Reader & Msr

    MICR+ CHECK READER & MSR File Name MICRPLUS.VXD Friendly Name(s) MICR+ Remarks These devices may or may not have an MSR installed. If not installed, the driver may not properly indicate the capability. /cancel cmd /display [x] /echo string n data /event /get prop Property...

  • Page 173: Mini Micr Check Reader & Msr

    MagTek Device Drivers for Windows MINI MICR CHECK READER & MSR File Name MINIMICR.VXD Friendly Name(s) Mini MICR RS-232 & Mini MICR Wedge Remarks These devices may or may not have an MSR installed. If not installed, the driver may not properly indicate the capability.

  • Page 174: Port-Powered Rs-232 Swipe Reader

    PORT-POWERED RS-232 SWIPE READER File Name MTPPSWIP.VXD Friendly Name(s) Port-powered swipe reader Remarks This driver supports all port-powered swipe readers. /cancel cmd /display [x] /echo string n data /event /get prop Property Default account_no amount ✔ ✔ ✔ ✔ applied_fmt c_card_stat c_cardwpin c_check...

  • Page 175: Port-Powered Rs-232 Insertion Reader

    MagTek Device Drivers for Windows PORT-POWERED RS-232 INSERTION READER File Name MTPPINSR.VXD Friendly Name(s) Port-powered insert reader If events_on is enabled, the driver will send /event 1 M when the card is Remarks inserted. It is suggested that events be disabled (/set events_on 0) before the data is read to prevent the removal event from being included at the end of card data.

  • Page 176: Mt-85 Loco Encoder

    MT-85 LOCO ENCODER MT85.VXD File Name MT-85 Friendly Name(s) Remarks The driver attempts to connect to the device by automatically scanning all connection modes. /cancel cmd /display [x] /echo string n data /event /get prop Property Default account_no amount ✔ ✔ ✔ ✔ applied_fmt c_card_stat c_cardwpin...
  • Page 177 MagTek Device Drivers for Windows MT-95 HICO ENCODER File Name MT95.VXD Friendly Name(s) MT-95 Remarks /cancel cmd /display [x] /echo string n data /event /get prop Property Default account_no amount ✔ ✔ ✔ ✔ applied_fmt c_card_stat c_cardwpin c_check c_events c_keypress c_keystring ✔...
  • Page 178 Access to the device ... 92 account_no ... 97 Action properties ... 89 Adding a Keyboard Device (WNT) ... 152 Adding a Serial Device (WNT)... 153 Adding an ‘IntelliPIN MICR Aux’ Device (WNT) ... 153 Adding Another Device Driver (W95/98) 141 Adding New Devices (WNT)...
  • Page 179 MagTek Device Drivers for Windows Device control language... 88 Device Driver Summaries ... 165 Device, close the ...92 Device, interacting with ... 93 Device, methods of accessing ... 92 Device, obtaining access to ... 92 Device, open... 91 Device, prepare for work... 91 Device, releasing access to...
  • Page 180 MTCFG Utility (WNT), Using ... 154 MTD (Mag-Tek Drivers) ... 87 Non-interactive commands ... 90 Notation Conventions... 102 offline_enc... 100 Open a device ... 91, 93 oper_tout... 100 Operational Timeout (oper_tout) ... 100 Packets communication... 87 Parallel port ... 88 Parity ...
  • Page 181 MagTek Device Drivers for Windows Use Port ... 153, 158 Use the device ... 91 Ver Command ... 112 Version, Driver... 95 Viewing the List of Configured Devices (WNT) ... 154 Virtual device ... 91 visa_mac1-3 ... 100 Visual Basic... 88 Visual Basic Example ...

Table of Contents