Manual de Usuario Procash NDC V 1 3

ProCash/NDC ProConsult/NDC
User Guide
V1.3/00 V1.1/00
Edition October 2004
Copyright and Trademarks

Copyright Wincor Nixdorf GmbH & Co. KG 2004. All rights, including rights of translation by printing, copying or similar methods, even of parts, are reserved. All rights, including rights created by patent grants or registration of a utility model or design, are reserved. Delivery subject to availability; right of technical modifications reserved. All names of hardware and software products mentioned in this manual are trade names and/or trademarks of their respective manufacturers. All hardware and software names used are trademarks of their respective manufacturers. Reliant is a registered trademark of Pyramid Technology Corporation. SINIX is the UNIX System derivative of Wincor Nixdorf GmbH & Co. KG. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Base: OSF/Motif, Copyright Open Software Foundation, Inc. X Window System, Copyright Massachusetts Institute of Technology. OSF/Motif is a trademark of Open Software Foundation, Inc. X Window System is a registered trademark of Massachusetts Institute of Technology. MS-DOS and Windows are registered trademarks of Microsoft Corporation in the United States and other countries.
Introduction
Software Structure
System Setup
Modes of operation
Configuration Data
Security Features
Messages
Printers
Additional useful Information
Abbreviations
Figures
Tables
Related publications
Contents
Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Whats new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Wincor Nixdorf Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Function Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Vendor capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Products of ProCash/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Products of ProConsult/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dynamic Link Libraries (DLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameter / Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Compatible Customization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Global Screen Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Error Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 15 16 17 18 19 20 21 23 23 26 26 27 28 29 30 31 31
System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exiting power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Out-of-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offline mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Suspend mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Service and Operating(SOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 42 42 42 43 44 44 45
October 2004
Contents Automatic return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customize Rear Balancing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispense Below Zero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 47 47 47 48 49
Miscellaneous Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 ADRS operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Steps processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Card Read State (A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 PIN Entry State (B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Customer Selectable PIN State (b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Extension to state (b) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Envelope Dispense (C) State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Pre-Set Operation Code Buffer State (D) . . . . . . . . . . . . . . . . . . . . . . . . 72 Clear mask (entry 3) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 A, B, C, D preset masks (entries 4-7) example . . . . . . . . . . . . . . . . . 75 Extension to State (D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Four FDK Selection Function State (E) . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Amount Entry State (F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Amount Check State (G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Information Entry State (H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Transaction Request State (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Extension to state (I) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Close State (J) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 FIT Switch State (K) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Card Write State (L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Enhanced PIN Entry State (M) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Enhanced Amount Entry State (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Extension to State (R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Language Code Switch State (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Extension to State (S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Card Read - PIN Entry Initiation State (T) . . . . . . . . . . . . . . . . . . . . . . . 116 Extension to State (T) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Language Select From Card State (V) . . . . . . . . . . . . . . . . . . . . . . . . . 120
October 2004
Contents FDK Switch State (W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FDK Information Entry State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eight FDK Selection State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Language Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . Audio Control State (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Fitness State (h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extension to State (h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Smart FIT Check State (k) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Skip State step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screen Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying Graphics as Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Full Screen graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Display resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying MacroMedia Flash executables . . . . . . . . . . . . . . . . . . . . . Displaying Video files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Voice Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto Voice Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audible Echo on Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reserved Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Miscellaneous Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Unit Number (LUNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Local download feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure local download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN and PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Personal Identification Number (PIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Variable length PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Offset Number (DES verification) . . . . . . . . . . . . . . . . . . . . . . . . . PIN Verification Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 126 129 132 135 136 138 142 145 148 152 153 153 158 158 158 159 159 160 160 161 162 165 166 166 166 167 173 173 175 175 176 177 177 178 178 179 180
October 2004
Contents Local PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANSI PIN/PAN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diebold PIN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ID Card and FIT Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ID Card Data Tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT (Financial Institution Table) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Library Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multi Card, Multi Institution Capability . . . . . . . . . . . . . . . . . . . . . . . . . . Alternate Transaction Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Data Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Institution Index (PIDDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Institution Identification (PFIID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Switch Index (PSTDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximum PIN Entry Digits (PMXPN) . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Check Length (PCKLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Pad Character (PINPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Index (PANDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Length (PANLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PAN Pad Character (PANPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PIN Retry Count Index (PRCNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Offset Number Index (POFDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Decimalization Table (PDCTB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encrypted PIN Key (PEKEY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Track Locator (PINDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Language Code Index (PLNDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Authentication (MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAC flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Terminal Number (Machine Number) . . . . . . . . . . . . . . . . . . . MAC data field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Time variant number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Typical Message Authentication Procedure . . . . . . . . . . . . . . . . . . . . . MACing for State and FIT Table Load commands . . . . . . . . . . . . . . . . . Triple DES operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMV capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Key Loading (RKL) capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 181 182 183 184 185 186 186 187 188 188 188 190 191 191 191 192 194 195 195 196 196 197 197 197 198 198 199 199 200 201 201 201 202 203 203 203 204
October 2004
Contents Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Messages from Terminal to Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsolicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network to Terminal messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction Reply command (message ID 4) . . . . . . . . . . . . . . . . . . . Terminal Command message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . State Tables Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Screen Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhanced Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . Interactive Transaction Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . FIT Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispenser Currency Mapping Table Load . . . . . . . . . . . . . . . . . . . . . . Configuration ID Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Date And Time Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Authentication Field Selection Load . . . . . . . . . . . . . . . . . . . Specific Command Reject Conditions . . . . . . . . . . . . . . . . . . . . . . . . . Terminal operations in Transaction Replies . . . . . . . . . . . . . . . . . . . . . . . . Print Immediate (4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Next State and Print (5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Night Safe Deposit and Print (6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deposit and Print (1 or 7) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dispense, Deliver and Print (2 or 8) . . . . . . . . . . . . . . . . . . . . . . . . . Display and Print (3 or 9) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Eject Card, Dispense and Print (A) (Card before Cash) . . . . . . . . . . . Eject Card, Dispense and Print (F) (Parallel CBC) . . . . . . . . . . . . . . . Parallel Eject/Dispense and Print (Fast Cash) (B or C) . . . . . . . . . . . Print Data and Stay in Present State (P) . . . . . . . . . . . . . . . . . . . . . . . Print Statement and Set Next State (Q) . . . . . . . . . . . . . . . . . . . . . . . Electronic Journal Upload (EJU) commands . . . . . . . . . . . . . . . . . . . . . . . Send Options And Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge And Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Acknowledge And Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NDC Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status (terminal state) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . October 2004 205 205 209 218 223 225 226 235 239 242 245 249 254 258 261 264 267 269 272 275 280 287 288 288 289 289 291 291 292 293 294 294 295 295 296 299 301 303 303
Contents Send Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Supply Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send Error Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Send date/time information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supplies Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fitness Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tamper and Sensor Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . Software ID and Release Number . . . . . . . . . . . . . . . . . . . . . . . . . . Local Configuration Option Digits . . . . . . . . . . . . . . . . . . . . . . . . . . Solicited Status (device fault) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsolicited Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Up (unsolicited) (DID B) . . . . . . . . . . . . . . . . . . . . . . . . . . . Card Reader (sol./unsol.) (DID D) . . . . . . . . . . . . . . . . . . . . . . . . . Dispenser (sol./unsol.) (DID E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Depository (sol./unsol.) (DID F) . . . . . . . . . . . . . . . . . . . . . . . . . . . Envelope Dispenser (unsolicited) (DID \ . . . . . . . . . . . . . . . . . . . . Receipt Printer (unsolicited) (DID G) . . . . . . . . . . . . . . . . . . . . . . . Journal Printer (unsolicited) (DID H) . . . . . . . . . . . . . . . . . . . . . . . Statement Printer (sol./unsol.) (DID V) . . . . . . . . . . . . . . . . . . . . . . Vandal Guard (unsolicited) (DID J) . . . . . . . . . . . . . . . . . . . . . . . . . EDM - Module (unsolicited) (DID L) . . . . . . . . . . . . . . . . . . . . . . . . Door Access (unsolicited) (DID N) . . . . . . . . . . . . . . . . . . . . . . . . . Sensor Status (unsolicited) (DID P) . . . . . . . . . . . . . . . . . . . . . . . . Supervisor Key Messages (unsolicited) (DID R) . . . . . . . . . . . . . . Electronic Journal Upload (EJU) Message . . . . . . . . . . . . . . . . . . . . . . Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic journal storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Types of journal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printing with the Windows GDI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NDC Standard Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ASCII to EBCDIC Code Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . Screen Design Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304 313 316 320 321 324 325 327 328 330 331 335 337 338 342 346 348 349 351 353 356 357 361 361 363 364 367 367 368 369 369 370 370 371 371 376 378
October 2004
Contents M-Status & M-Data Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . CSC-W32 Error Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cash Dispenser V1 (old series) (Class: 0007) . . . . . . . . . . . . . . . . . . . Cash Dispenser NG (Classes: 0018/AA18/001D) . . . . . . . . . . . . . . . . Cash Cheque Deposit Module (Classes: 001A/XX1A) . . . . . . . . . . . . . Encryption Decryption Module (Class: 000F) . . . . . . . . . . . . . . . . . . . . Encryption Decryption Software (Class: 0011) . . . . . . . . . . . . . . . . . . . Card Reader (Class: 0008/AA08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deposit Module (Class: 0017/AA17) . . . . . . . . . . . . . . . . . . . . . . . . . . Vandal Guard (Class: 0015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Motorized Door (Class: 000E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer (Class: 0032) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND71/74/98/9A/9C/9E/TH30 (Class: 0033) . . . . . . . . . . . . . . . Printer ND75/75S/94 (Class: 0034) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND79 (Class: 0035) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND99 (Class: 0038) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer ND97/TH97/TP01/NP01/TP05/NP05 (Class: 0039) . . . . . . . . . Printer TH21 (Class: 003E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Extensions (Class: 003F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Monitor ND9G (Class: 0040) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Monitor TH21 (Class: 0041) . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer System Framework (Class: 0042) . . . . . . . . . . . . . . . . . . . . . . . Printer TP07 GDI (Class: 0044) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer TP07 (Class: 0045) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer USB/TP07 (Class: AA45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer TP06 (Class: 0048) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer USB/TP06 (Class: AA48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application Error Classes (LYNX errors) . . . . . . . . . . . . . . . . . . . . . . . . . . Transaction (Class: 6434) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cash Dispenser (Class: 643A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Security Module (Class: 643C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CashIn transaction (Class: 6446) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . EMV transaction (Class: 6459) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cheque transaction (Class: 645A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Electronic Journal (Class: 0091) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WOSA Error Classes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . WOSA Cash Dispenser (Class: 00B9) . . . . . . . . . . . . . . . . . . . . . . . . . 379 379 379 383 392 405 406 407 411 414 415 416 417 418 418 419 420 422 423 423 424 424 426 427 428 430 431 433 433 434 435 435 436 437 437 438 438
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
October 2004
Contents Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451 Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
October 2004
Whats new
This section lists a summery of documentation changes and enhancements of the ProCash/NDC User Guide. Since November 2003 until October 2004:
q q q q q q q q q
New section Electronic Journal Upload (EJU) commands on page 295 New section Electronic Journal Upload (EJU) Message on page 364 New section Remote Key Loading (RKL) capability on page 204 New section EMV capability on page 203 New section Displaying MacroMedia Flash executables on page 159 New section Smart FIT Check State (k) on page 148 Changed section Hardware Fitness State (h) on page 142 Changed section Amount Check State (G) on page 84 New section Dispenser Currency Mapping Table Load on page 267
Since May 2002 until November 2003:

q q q q q q q q q q q
New section Miscellaneous Operations on page 51 Changed section Related publications on page 453 New section M-Status & M-Data Reference Tables on page 379 New section Triple DES operation on page 203 Extended section Solicited Status messages on page 218 Extended section Send Configuration Information on page 304 Changed section Software Products of ProConsult/NDC on page 21 Changed section Software Products of ProCash/NDC on page 20 New section Printing with the Windows GDI Interface on page 370 Changed section Dynamic Link Libraries (DLL) on page 23 Changed section Directory Structure on page 34
October 2004
13
Whats new Since October 2001 until May 2002:

q q q q q q q q q
New section Enhanced Amount Entry State (R) on page 107 New section Audio Control State (i) on page 138 New section Voice Control on page 160 New section Dispense Below Zero on page 49 Enhanced section Unsolicited Device Status on page 335 Enhanced section Printer Models on page 367 Changed section Related publications on page 453 Enhanced section Directory Structure on page 34 Enhanced section Solicited Status (terminal state) on page 303
14
October 2004
Introduction
Preface
Introduction
Preface
In the past NCR and Diebold/Interbold have dominated the international market of automated teller machines (ATM). Both vendors have defined very similar protocols for the network integration of their systems. The existing MS-DOS based NDC-Emulation from Wincor Nixdorf is running in NCR network environments all around the world. New technologies and of course windows oriented platforms provided from Microsoft has forced Wincor Nixdorf to develope the NDC-Emulation running with Windows. The product ProCash/NDC and since October 2002 ProConsult/NDC from Wincor Nixdorf has been developed with all known advantages provided by Windows like Multithreading Processes, using WOSA services, open system environment through the ProTopas architecture from Wincor Nixdorf. The ability to integrate ProCash/NDC in multi vendor projects (ProCash/NDC running on NCR, Olivetti, or Diebold hardware) is another big advantage of this software architecture.
Wincor Nixdorf Solution

ProCash/NDC and ProConsult/NDC have been developed using the C++ object oriented ProTopas architecture. ProTopas is a flexible development platform for self-service device applications in open system environments. Development with ProTopas means using existing Frameworks, modifying and creating new Frameworks for the specific self-service application. The application design allows customers to create easily new Frameworks of customer specific functions using ProTopas/KIT. Wincor Nixdorf provides ProCash/NDC and ProConsult/NDC with function messages of NCR terminals which are described in later sections. Any function restrictions against NCR can be recognized if it is not documented in this manual.
October 2004
15
Purpose of the Document
Introduction
Purpose of the Document

This document will provide the software analyst with the necessary information on the functions which are supported by product ProCash/NDC and ProConsult/NDC. Furthermore all the information needed for the operation of the ATM, as far as it is NDC specific and not covered by other documentation (e.g. CSC-W32, Protopas or ProDevice documents). A detailed description of all the application specific parameters will be found in the ProCash/NDC ProConsult/NDC Installation manual along with information for installation and upgrading the products. NDC specific features like States, Screens, FIT, commands and messages will be described here in detail. Since the list of supported features keeps growing please always use the latest release of this documentation. We will make updated versions available as soon as practical, either by file download or as an online-documentation. Any feature exceeding the described ones may not be supported. In this case please refer to the protocol descriptions of the network (in case of project specific extensions) or to recent releases of the Programmers Reference Manuals of NCR.
16
October 2004
Introduction
Function Overview
Function Overview
ProCash/NDC and ProConsult/NDC written for Wincor Nixdorf terminals contain base functions from the original NCR Direct Connect (NDC) software provided by NCR. The functionality depends on the host Software (BASE24, ON/2, TP/2, etc.). The download of original NCR Customization Tables such as States, FITs, Screens and Parameters controls the terminal, thus defining the available functions. Those are typically (but not exclusively):
q q q q q q q q q q q q q q q
Withdrawal Fast cash Deposit Balance inquiry Transfer Payment PIN change Rear Balancing Multi language Statement print MACing Triple DES security EMV support Cheque deposit
(ProCash/NDC only) (ProCash/NDC only) (ProCash/NDC only)
E-Journal Upload (EJU)
October 2004
17
Supported hardware
Introduction
Supported hardware
Currently following systems and hardware components are supported: ATMs: q CSC4xx Rear/Frontload q CSC400 Frontload q ProCash-Compact q ProCash 2000 q CSC21xx, CSC1500 q Cash Recycling System (CRS), 3100xe Info Terminals: q ProPrint 200 q ProPrint 2000 q ProConsult, Certo Dispenser modules: q CDM-V1, CDM-NG, CMD-V4, CDM-NG (6 cassettes) Needle printers: q Journal: ND98D, ND98, ND71, NP06 q Receipt: ND9E, ND71, ND9A, NP07 q Statement: ND97, ND94, ND97 Thermal printers: q Receipt: ND9C, ND99, ND9G, TH21, TH22, TP07 q Journal: TH30, TP06 q Statement: TH97/G, TP01, TH23 Card readers: q ID14 (Sankyo Seiki), ID15 (Wincor Nixdorf), ID18 (OMRON), V2X, ID24 (DIP reader), ICM300 (manual smart card reader) Encryption modules: q EDM module (restricted security), EPPs V4, V4+, V5 (international) Deposit modules: q Papalakko, Wincor Nixdorf q Cheque Deposit Module (CCDM)
continued on next page ...
18
October 2004
Introduction Miscellaneous: q Operator Panel (Low- or high end) q Touch screen support q Power Supply box q Sound card q USB support
Multi Vendor capability
Multi Vendor capability

Since release 1.3/00 ProCash/NDC supports hardware platforms from other vendors as well. Follwing hardware platforms of other vendors are supported, which can be installed via standard installation procedure via ProInstall:
q q
NCR cash systems Diebold cash systems, (except OPTEVA)
Following vendors are running with ProCash/NDC, but they have to be installed with a special prepared installation set:
q q q
Fujitsu cash systems Olivetti cash systems Delarue cash systems
October 2004
19
Software Products of ProCash/NDC
Introduction
Software Products of ProCash/NDC

In the following table is listed the basic software products that are required to setup a whole ProCash/NDC application:
Table 1: Basic Software of ProCash/NDC
Name Operating system Windows XP Professional Windows NT CSC-W32 ProCash/Topas ProSop WOSA/XFS-SSP (2.0) WOSA/XFS-SSP (3.0) WOSA/XFS-SSP/MV PARAC-NT ProView ProCash/NDC
ProCash/NDC-SOP
current Release
Systems
see Note2 4.00 Srv. 6 2.0/53 4.1/00 3.1/13 3.1/72 4.0/31 3.1/71 3.2/02 3.7/01 1.3/00 all all all all all all all all all all
Communication software SNA-Workstation Eicon software components 4.0 3.0 optional optional
For detailed information about function and configuration of each product refer to ProCash/NDC ProConsult/NDC Installation manual NOTE 1: ProCash/NDC is running on on PC based systems. The Windows NT system needs minimum 128 MB RAM at runtime and one hard disk with the minimum capacity of 500 MB to store the whole software. For Windows XP 256 MB RAM and hard disk space of 4 GB is required. Pure Windows XP needs 1,8 GB hard disk space. NOTE 2: Windows XP is released on Embedded PCs only.
20
October 2004
Introduction
Software Products of ProConsult/NDC

In the following table is listed the basic software products that are required to setup a whole ProConsult/NDC application:
Table 2: Basic Software of ProConsult/NDC
Name Operating systems Windows XP Professional Windows NT CSC-W32 ProCash/Topas ProSop WOSA/XFS-SSP (2.0) WOSA/XFS-SSP (3.0) WOSA/XFS-SSP/MV PARAC-NT ProView ProConsult/NDC
ProConsult/NDC-SOP
current Release
Systems
see Note2 4.00 Srv. 6 2.0/53 4.1/00 3.1/13 3.1/72 4.0/31 3.1/71 3.2/02 3.7/01 1.1/00 all all all all all all all all all all
Communication software SNA-Workstation Eicon software components 4.0 3.0 optional optional
For detailed information about function and configuration of each product refer to ProCash/NDC ProConsult/NDC Installation manual NOTE 1: ProConsult/NDC is running on on PC based systems. The Windows NT system needs minimum 128 MB RAM at runtime and one hard disk with the minimum capacity of 500 MB to store the whole software. For Windows XP 256 MB RAM and hard disk space of 4 GB is required. Pure Windows XP needs 1,8 GB hard disk space. NOTE 2: Windows XP is released on Embedded PCs only.
October 2004
21
Introduction
22
October 2004
Software Structure
Dynamic Link Libraries (DLL)
The following described Dynamic Link libraries are the part of ProCash/NDC or ProConsult/NDC, which have to be installed via ProInstall on the harddisk of the ATM. These modules control the functions of the application. The following software modules build the application part NDC on the ATM:
q
Transaction Framework (dcsttfw.dll) The Transaction Framework maps the downloaded NDC states to the belonging step function defined in the LYNXPAR section of the registry.
Cash Dispenser Framework (dccdmfw.dll) (not ProConsult/NDC) The Cash Dispenser Framework controls the dispensing requests from the consumer. It maps the physical cassettes to logical positions which have to match with the positions configured at the host side. It handles the cassette counters and syncronizes them with WOSA.
Device Status Framework (dcdevsta.dll) The Device Status Framework collects the status of the devices from the different device frameworks. It also offers the supplies of the devices. The actual status will be passed to the Message Control Framework whenever it asks for the device status.
Message Control Framework (dcmsgcfw.dll) The Message Control Framework handles the NDC messages sent from the host to the terminal and builds up the messages which have to be sent from the terminal to the host. It asks the Device Status Framework for the current status of the device to fill the severity and supply status fields of solicited and unsolicited messages to be sent to the host.
SOP User Exit Framework for ProSop (dcsuefw.dll) The ProSop User Exit Framework contains NCR service functions like Display supply status, Clear card capture counter, Rear balancing, etc..
October 2004
23

q
Software Structure
NDC Printer Framework (ndcprtfw.dll) The NDC Printer Framework analyzes the printer data from the host and converts it to printable printer buffers. First it reads the base settings from the registry and set it as default (sets lpi and cpi size, activates the printer font, reads the char convertion table, etc.) after that it fills the printer data with the specific macros depending on which NDC escape sequences are in the printer data from the host. The formatted print buffer will be passed to the base printer framework of ProTopas.
NDC Dialog Framework (ndcdiafw.dll) The NDC Dialog Framework handles the consumer FDK, PIN inputs and controls the screen flow.
Application Framework (dcapplfw.dll) The Application Framework has the control above the other Frameworks. It starts the Protocol Framework, Communication Framework, Step Table Framework and handles the synchronisation with the different Frameworks.
Converter Framework (dcconvfw.dll) The Converter Framework handles the Customisation Image (CI) downloaded from the host. It stores the host configuration (States, Screens, Timers, FIT table , Configuration parameters and Configuration ID) in the LYNXCI path of the Registry.
Protocol Framework (dcprotfw.dll) The Protocol Framework send to or receives messages from the Communication Framework.
Security Overlay Framework (dcsecure.dll) The Security Framework performes local PIN verification with the corresponded FIT data. Performs calls to security functions of Protopas basic framework.
SOP Service Framework (dcServic.dll) The SOP service framework contains Dialog and synchronisation functions of ProCash/NDC-SOP ProConsult/NDC-SOP.
SOP Dialog Framework (dcSopDia.dll) The SOP dialog framework controls the dialog screens on the facia screen or on the operator panel of ProCash/NDC-SOP or ProConsult/NDC-SOP.
24
October 2004
Software Structure
q
GDI Printer Overlay Framework (dcPrtGdi.dll) The GDI Printer Overlay Framework converts PrintRaw data to GDI print data, which are passed to a Windows printer (e.g. ND9G). This Overlay framework has to be configured in between the ProTopas printer framework and the NDC Printer Framework in the Repository Manager. Refer to GDI Printer Overlay Framework - User Guide for detailed descriptions about GDI printing with ProCash/NDC and ProConsult/NDC.
EMV Transaction Overlay Framework (dcEmvTa.dll) The EMV Transaction Overlay Framework is needed to handle transactions with EMV data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.
EMV Message Control Overlay Framework (dcEmvMc.dll) The EMV Message Control Overlay Framework is needed to append messages with EMV data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.
EMV Converter Overlay Framework (dcEmvCv.dll) The EMV Converter Overlay Framework is needed to handle EMV download data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions.
October 2004
25
Parameter / Data Files
Software Structure

Types of Parameters
Every terminal needs many different parameters to operate as expected. The most complex set of parameters is called "Customization" and contains the dialogs and the sequence of functional steps (e.g. card read - PIN Entry Function selection ...) which the system will perform. NCR supports the central customization by files which will be distributed to all connected ATMs. Our ProCash/NDC and ProConsult/NDC emulation fully supports this Customization Download. The parameters will be stored into the Windows registry. Changes to those parameters may be overwritten any time by a new download. Thus permanent changes must be made to the customization files on the Host, not on the ATM. Furthermore each ATM will have a number of extended parameters which are specific to its type or to the particular machine. The Wincor Nixdorf solution, being an emulation, needs several parameters to cover the differences to the original systems and for enhanced services. Existing parameters can be edited in text files (*.ppf or *.ina type). The Registry update with the changed values will be done via PARAC-NT after the next RUN process and with CCRCCONV.EXE. Details will be given in the ProCash/NDC ProConsult/NDC Installation manual.
26
October 2004
Software Structure
Compatible Customization Data

All customization data are stored in the Windows registry location:
HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXCI
Screen Data (LYNXCI\SCREEN\XXX [1])

[1] XXX represents the downloaded screen number
are the predefined display screens provided by the host.

q
State Table (LYNXCI\STATE) is used to define and control the logic flow of the for client transactions.
Financial Institution Table (LYNXCI\FIT) consists of an entry for every institution or group of institutions offering services on the ATM. Client card data are compared to data in this file to determine whether the card holder can receive services.
Customization Parameters (LYNXCI\PARAMETER) contain some terminal specific settings and specific definitions of the message protocol.
Timers (LYNXCI\TIMER) contain downloaded timer values valid for all ATMs in the network.
Receipt Templates (LYNXCI\SCREEN\R00; LYNXCI\SCREEN\R01) As part of the screens download the host can send receipt header data (R00) and predefined receipt data (R01) (data that are mixed together with the host printer data of the transaction reply). Those screens are stored in sub section ..\LYNXCI\R00 and ..\LYNXCI\R01.
EMV Parameters (LYNXCI\EMV) This section contain specific EMV parameters.
October 2004
27
Software Structure
Extended Configuration Data

All non downloaded configuration data are stored in the following location of the Windows registry:
HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXPAR
q
Application Parameters (LYNXPAR\APPLICATION ) This section contain parameters which are not assigned to a specific hardware device. These are global settings of NDC and can be parameters for the protocol or timers etc..
Cash Dispenser Parameters ( LYNXPAR\CASH_DISPENSER) This section contain parameters related to the cash dispenser like cassettes type configuration, dispense algorithm, dispenser status. (This section is missing in the non cash product ProConsult/NDC.)
Card Reader Parameters (LYNXPAR\CARD_READER ) This section contain parameters related to the card reader like track configuration and transport handling of the ID card.
Deposit Parameters (LYNXPAR\DEPOSIT) This section contain parameters related to the deposit module.
Printer Parameters (LYNXPAR\PRINTER) This section contain parameters related to the journal, receipt and document printers.
GDI Printer Parameters ( LYNXPAR\GDI_RINTER) This section contain parameters for printers using GDI.
Operator Screen Parameters ( LYNXPAR\OPERATOR_SCREENS) This section contain the operator screen template parameters that are used to display or print the supply counters within the user exit menu Individual Functions of ProSop.
28
October 2004
Software Structure
q
Function ID mapping (LYNXPAR\FUNC_ID_MAP) This section contain the assignment to the ProCash/NDC or ProConsult/NDC step functions and function IDs that are send in transaction replies.
State mapping (LYNXPAR\STATE_MAP ) This section contain the assignment to the ProCash/NDC or ProConsult/NDC step functions and state IDs that are send in the states table download from host.
Global Screen Configuration

The global non downloaded screen configuration contains default display settings and path for graphic files (*.PCX), Bitmaps (*.BMP) and Videos (*.AVI; *.MPG) etc.. Furthermore for each screen can be configured special display settings or idle rotations which are independend from the host download. Those parameters are stored in the following location of the Windows registry:
HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ LYNXCI\SCREEN LYNXCI\SCREEN\XXX
Details will be given in the ProCash/NDC ProConsult/NDC Installation manual.
October 2004
29
Software Structure
Error Mapping Configuration

All device errors and mapping parameters are devided in error classes. The CLASS section is devided in the CSC-W32 device classes inclusive the ProCash/NDC classes. Each class contains sub sections of error codes which contain the CSC-W32 error and the error mapping definitions for the message protocol. They are stored in the following location of the Windows registry:
HKEY_LOCAL_MACHINE\ SOFTWARE\ Wincor Nixdorf\ ProTopas\ CurrentVersion\ CCERRMAP\CLASS
Details will be given in the ProCash/NDC ProConsult/NDC Installation manual
30
October 2004
Software Structure
Font Files
Font Files
ProCash/NDC uses the Windows font format (*.FON) for displaying text and graphic characters for downloaded NDC screens. The fonts can be created and modified via utility FONTEDIT.EXE. During the installation the default base set of ProCash/NDC or ProConsult/NDC fonts will be installed and activated automatically like standard Windows fonts.
The following section contains a short list of NDC Standard Fonts that are installed during the installation of ProCash/NDC or ProConsult/NDC:
Standard Fonts
Table 3: Standard fonts table
Font name 1 2 > ? 3 4 5 9 B File name NDC-SA1.FON NDC-SA2.FON NDC-DA1.FON NDC-DA2.FON NDC-GA1.FON NDC-GA2.FON NDC-GA3.FON NDC-SARA.FON NDC-DARA.FON Designation Single Size Alpha 1 Single Size Alpha 2 Double Size Alpha 1 Double Size Alpha 2 Standard Graphic 1 Standard Graphic 2 Standard Graphic 3 Single Size Arabic Double Size Arabic 640x480 (W * H) [1] 20x30 20x30 40x30 40x30 20x30 20x30 20x30 20x21 40x42 800x600 (W * H) [1] 25x37 25x37 50x37 50x37 25x37 25x37 25x37 25x26 50x52 1024x768 (W * H) [1] 32x48 32x48 64x48 64x48 32x48 32x48 32x48 32x33 64x64
[1] -
Depending on the display resolution you have to select the belonging font with the correct width and height (W * H). During the installation the standard fonts are automatically installed with the display resolution currently set in the control panel of Windows.
October 2004
31
Font Files
Software Structure
32
October 2004
System Setup
Software Installation
The whole software will be installed via the ProInstall Product CD, Customizing and Update diskettes. The installation process will be started via program SETUP.EXE located in the root of the ProInstall CD. During the installation you will guided via menu dialogs through the installation processes. You can set also specific parameters via a parameter configuration dialog. All details about product installation will be provided in the ProCash/NDC ProConsult/NDC Installation manual.
October 2004
33
Directory Structure
System Setup
Directory Structure
ProCash/NDC or ProConsult/NDC is only one part of a bundle of software packages running on an Windows based ATM. A lot of directories and a large number of Dynamic Link Libraries (DLLs) makes it difficult to assign configuration files and DLLs to the right software sub product. Protopas based DLLs and ProCash/NDC or ProConsult/NDC specific DLLs are stored together in directory C:\PROTOPAS\BIN. The following table gives short overview about the modules and their directories:
Table 4: Software structure
File Structure \CSCW32 \WOSASSP \PROSOP \PROTOPAS fwstrt.bat fwkill.bat ccprot.log \PROTOPAS\BIN dcApplFW.dll dcSttFW.dll dcMsgcFW.dll dcConvFW.dll dcCdmFW.dll dcSueFW.dll dcSecure.dll 3DesEppF.dll dcDevSta.dll dcServic.dll dcSopDia.dll ndcDiaFW.dll ndcPrtFW.dll
Description modules of CSC-W32 operating system modules of ProDevice (WOSA) modules of ProSop Starts ProCash/NDC or ProConsult/NDC Stops ProCash/NDC or ProConsult/NDC Log file of Host and ATM messages Application Framework Transaction Framework Message Control Framework Converter Framework Cash Dispenser Framework Sop User Exit Framework Security Overlay Framework Triple DES EPP Overlay Framework Device Status Framework ProCash/NDC-SOP, ProConsult/NDC-SOP Service Framework ProCash/NDC-SOP, ProConsult/NDC-SOP Dialog Framework NDC Dialog Framework NDC Printer Framework
34
October 2004
System Setup
Directory Structure
File Structure dcPrtGdi.dll dcEmvTa.dll dcEmvCv.dll dcEmvMc.dll dcTcp2h.dll dcTcp2hi.dll dcTcp4a.dll dcTcp4ai.dll dcTcp3a.dll dcTcpSTX.dll dcSimCom.dll ccrcconv.exe \PROTOPAS\CONF Kconf.exe Kconf.txt conv.bat conv-all.ok (conv-all.bat)
Description GDI Printer Overlay Framework EMV Transaction Overlay Framework EMV Converter Overlay Framework EMV Message Control Overlay Framework TcpIP converter for 2 bytes binary headers (header length excluded) TcpIP converter for 2 bytes binary headers (header length included) TcpIP converter for 4 bytes ASCII headers (header length excluded) TcpIP converter for 4 bytes ASCII headers (header length included) TcpIP converter for 3 bytes ASCII headers (header length excluded) TcpIP converter for STX and ETX message length calculation Host Simulator Framework Updates the Windows registry with contents of *.RCK files Converts *.INA files to *.RCK format Describes functionality of Kconf.exe Update job for *.INA files to update existing and store new parameters in the Registry Batch file which is called once immediately after installation to store additional parameters in the registry (will be renamed from *.BAT to *.OK after the call). Batch job to store additional parameters for the journal and receipt printer to enable INIT sequences via makros. Parameter source file of printer parameters used by Kconf.exe Batch job to set SOP User Exit and Trace menu items for ProSop (Single DES).
prtmakro.bat
prtmakro.ina prosop.bat
October 2004
35
Directory Structure
System Setup
File Structure prosop.ina sop3des.bat sop3des.ina gdi_prt.bat gdi_prt.ina logon.bat logon.ina autostrt.bat
Description Parameter source file of SOP User Exit and Trace (Single DES) used by Kconf.exe Batch job to set SOP User Exit and Trace menu items for ProSop (Triple DES). Parameter source file of SOP User Exit and Trace (Triple DES) used by Kconf.exe Batch job to set GDI printer parameters. Parameter source file of GDI printer parameters used by Kconf.exe Batch job to set parameters in the Registry to activate automatic logon. Parameter source file for automatic logon parameters Batch job to set one parameter which activates an automatic call of C:\STARTUP.BAT after restart. Parameter source file for the automatic startup.bat call. Parameter source file of all application and CSC-W32 error codes and mapping definitions which is used during conv-all.bat process is running. Parameter source file of Rear Balancing step table parameters which is used during conv-all.bat process is running. Line convertion tables: EBCDIC - ASCII and ASCII - ASCII (default is ASCII - ASCII) Link of the Configuration Manager for the start bar of Windows. Contains configuration files needed to optimize Windows XP Batch routine that installs the *.INF files and contents of *.REG files. Windows XP general optimations Windows XP Explorer optimations
autostrt.ina ccerrmap.ina
lynxsop.ina
ccvtable.fil (asc, ebc) cfgmanag.lnk \PROTOPAS\CONF\ TUNING.XP tune_xp.bat tune_xp.reg explorer.inf
36
October 2004
System Setup
Directory Structure
File Structure perform.inf bootload.inf autorun.inf nowelc.inf \PROTOPAS\WORK cccmos.bin
Description Windows XP settings for enhanced performance Windows XP reduced boot delay time Windows XP autorun settings Windows XP switch off welcome screen CMOS file - stores transaction oriented counters and device statuses (e.g. Last Transaction Status information) Resolution depended sub directories where the default graphics are stored during the installation. Graphic and Bitmap files which are controlled via screen escape sequences or as a local definition for Background pictures or to replace downloaded NDC text screens. Bitmap which is displayed during the system shutdown initiated by the restart handler in a fatal error condition. Bitmap which is permanently displayed if the maximum system reboots has been initiated by the restart handler. Video animation file which can be configured instead of a normal graphic in the registry section ..\LYNXCI\SCREEN. Resolution depended sub directories where the default fonts are stored during the installation. Contains Windows fonts that are used if GDI printing is enabled (e.g. ND9G, TP07). Dialog oriented host simulator simulates host to terminal messages.
\PROTOPAS\BITMAPS
\PROTOPAS\BITMAPS\640x480 \PROTOPAS\BITMAPS\800x600 \PROTOPAS\BITMAPS\1024x768
*.PCX, *.BMP, *.ICN, *.JPG
dctmpoos.bmp
dcoos.bmp
*.AVI, *.MPG, *.MPEG
\PROTOPAS\FONTS
\PROTOPAS\FONTS\640x480 \PROTOPAS\FONTS\800x600 \PROTOPAS\FONTS\1024x768
\PROTOPAS\FONTS\ GDI_PRT \PROTOPAS\TOOLS HostSim.exe
October 2004
37
Directory Structure
System Setup
File Structure MfcDlg.exe MfcVar.exe protlog.exe reboot.exe write-id.exe write-id.cmd fontedit.exe asc2fon.exe fon2asc.exe prt-dof.exe asc2dof.exe dof2asc.exe asc-nd99.exe nd99-asc.exe ldnd99.exe nd99logo.exe asc2logo.exe nd9e-dof.exe pcx2asc.exe cfgmanag.exe
Description Dialog window where you can enter specific screens to display during runtime. Displays variables (e.g. Opcodes) during the transaction flow. Message analyzer of log file CCPROT.LOG Initiates a system shutdown or relogon Utility to write track 1,2 or/and 3 data on ID cards via ID Card Unit. Batch file which can be modified for calling write-id.exe to write tracks on ID cards. Modifies and view Windows font contents Converts ASCII font files to Windows fonts Extracts Windows fonts to ASCII text files Sends control sequences (in *.DOF format) to the receipt or journal printer. Converts ASCII printer fonts to *.DOF format. Extracts DOF files to ASCII printer font files Converts ASCII printer font files to *.SWF format for ND99 printer. Extracts binary *.SWF font files of ND99 to ASCII matrix font files. Font and Logo loader for ND99 Extracts ND99 logo files to ASCII matrix file Converts ASCII logo files to binary logo files for ND99. Converts an ASCII logo file to DOF format for ND9E printer. Extracts 2 or 16 color PCX graphics to ASCII matrix text file. Configuration Manager. Easy access to analyzing tools and configuration data via pull down menus.
38
October 2004
System Setup
Directory Structure
File Structure cfgmanag.mnu
Description Menu definition file for the Configuration Manager that allows menu configuration. (Will not be installed, but can be ordered from WCN support). Help text file for the Configuration Manager. Converts INA files to PARAC definition RC source files. Compares an extracted registry text file with the contents of the Windows registry. Installes and registers Windows font files. Converts ASCII files to PCC/PCX files. Extracts ICN icon files to ASCII matrix files. Converts ASCII files to ICN files. Sets hardware depended menu for Status Overview in ProSop and deconfigures paper journal of no journal printer is installed. (used during installation). Test utility that can print a text file with ASCII printer data and macros via printer interface of CSC-W32. Test utility that prints raw data via ProTopas API function PrintRaw() from file C:\PROTOPAS\RAWDATA.TXT, or prints the contents of registry parameter MSGxxx via function Print(xxx). ProCash/NDC-SOP, ProConsult/NDC-SOP User Manager. Deletes keys from EPP and gives detailed information about the EPP hardware. Converts ASCII printer fonts to *.DOF format for NP06/TP06 and NP07/TP07. Converts hex *.DOF files of NP06/TP06 and NP07/TP07 font definitions to ASCII files. Configuration Utility. It is called during installation and by the Config. Manager
cfgmanag.hlp ina2def.exe compregf.exe cpyntfnt.exe asc2pcc.exe icn2asc.exe asc2icn.exe sethwppf.exe
prt-raw.exe
printraw.exe
dcsopmgr.exe initepp.exe dof-rj03.exe rj03-dof.exe confchck.exe
October 2004
39
Directory Structure
System Setup
File Structure addonchk.exe cfgmedit.exe
Description Installation Utility that is called during installation only. Editor with restricted file access that can be used via the Configuration Manager.
40
October 2004
Modes of Operation
At any time, Wincor Nixdorf terminals operates in one of the following six modes:
q q q q q q
power-up mode out-of-service mode in-service mode offline mode Service and Operating (supervisor mode) suspend mode
The terminal changes from one mode to another when it encounters a specific event, like the SOP switch is pressed or the terminal discovers that it is no longer communicating with the network. Figure 1 shows how the terminal normally exits one mode and enters another. If the terminal loses power or is reset, the terminal abnormally exits from the mode it was in, when the reset or power failure occurred.
Figure 1: Terminal operation
POWER-UP POWER-UP
OFFLINE OFFLINE
SUPERVISOR SUPERVISOR MODE MODE SUSPEND SUSPEND MODE MODE
OUT OF OUT OF SERVICE SERVICE
IN SERVICE IN SERVICE
The following paragraphs describe how the terminal enters and exits each of the modes and, if applicable, how the terminal functions when it is in that mode.
U25604-J-Z745-1-7600
October 2004
41
Power-up mode
Modes of Operation
Power-up mode
The terminal enters power-up mode when the terminal is switched on. During power-up mode, the restart handler starts the WOSA services, the Protopas environment and at least the ProCash/NDC, ProConsult/NDC frameworks. After all terminal devices are opened the communication framework is waiting for line activity.
Exiting power-up mode

The terminal exits to offline or out-of-service mode when it leaves power-up mode. If line connection is established, the communication framework sends the power up message as configured to the host.
Out-of-service mode
The terminal may enter out-of-service mode from any one of the following modes:
q q q
power-up mode offline mode in-service mode (if the terminal receives an out-of-service command from the network) supervisor mode
The terminal accepts and stores configuration data while it is in out-of-service mode. During this time, the terminal can also receive and execute print immediates, startup and shutdown commands from the network. Depending on what mode the terminal was in before going out-of-service, the terminal may perform other functions.
42
October 2004
U25604-J-Z745-1-7600
Modes of Operation
In-service mode
In-service mode
The terminal enters in-service mode from any of the following modes:
q
out-of-service mode (if the terminal receives a startup command from the network) supervisor mode (if the return to previous mode feature is enabled ) offline mode (if communication with the network is restored)
q q
While in-service, the terminal uses the configuration data to make transaction sequence decisions. The terminal exits in-service mode under the following conditions:
q
The terminal receives a shutdown command from the network; the terminal exits to out-of-service mode after finishing any customer transactions in progress. The terminal looses communication with the network; the terminal exits to offline mode. The terminal exits to supervisor mode when there is an SOP entry on the operator panel, the SOP switch is pressed, or when the safe door is open. An abnormal exit occurs.
Except when an abnormal exit occurs, the in-service mode can only be exited from State 000.
U25604-J-Z745-1-7600
October 2004
43
Offline mode
Modes of Operation
Offline mode
The terminal may enter offline mode from any of the following modes:
q q q q
in-service mode out-of-service mode power-up mode supervisor mode
Offline mode is entered from the in-service mode if communication is lost between the network and the terminal. While in this mode, the terminal operates as follows:
q
The terminal displays the user-defined offline screen (screen C01) on the screen. The terminal enters an idle loop until network communication is restored.
The terminal exits this mode under the following conditions:

q q q
communication with the network is restored the terminal enters supervisor mode an abnormal exit occurs
Suspend mode
The suspend mode feature must be activated in the miscellaneous parameters (see ProCash/NDC ProConsult/NDC Installation manual for details). Suspend mode is entered from the in-service mode if a tampering suspected error has occurred and the specific error of the device class in CCERRMAP is set to Severity 3. While in this mode, the terminal operates as follows:
q
The terminal displays the suspend mode screen C05 or C02 (if screen C05 not exists) on the screen. Green status lights in front and on the Operator Panel will be switched off. The terminal doesnt accept customer cards.
q q
44
October 2004
U25604-J-Z745-1-7600
Modes of Operation
Service and Operating(SOP)
The terminal exits this mode under the following conditions:

q q q
the terminal enters supervisor mode the host sends an in-service or out-of-service command the suspend mode timer has expired (return to previous mode)

For Wincor Nixdorf terminals the operator uses the Service and Operating to replenish supplies, change passwords and change encryption keys. While in the SOP mode, the manager or operator can enable or disable devices or device options for service and maintenance. All service and operator functions are described in the manual ProCash/SOP Service & Operating User Guide. If the manager enters the SOP, the terminal sends an unsolicited status message to the network when it enters the operator mode. Refer to section Unsolicited Status messages on page 223 for further information. While in SOP mode, the terminal responds to network messages as follows:
q
The terminal processes load command messages and replies with solicited status messages indicating either a ready condition or a command reject condition. The terminal responds to all other Transaction Reply command messages with a solicited status message indicating a command reject condition. The terminal responds to an Terminal Command message requesting configuration information with a solicited status message containing configuration information. The terminal accepts Terminal Command messages requesting start-up or shutdown but does not process or reply to them until it exits the supervisor mode. If the terminal receives any Terminal Command messages requesting startup or shutdown while in the SOP, then upon exiting the SOP, the terminal processes the last such message received and sends the network a solicited status message indicating a ready condition.
U25604-J-Z745-1-7600
October 2004
45
Modes of Operation
Service & Operating (operator panel or consumer display) On rearload terminals the operator uses the operator functions via the Operator Panel. On Frontload terminals the operator can enable the Service & Operating on the consumer screen if he presses the SOP button. Service and Operating provides the following features to enhance operations:
q
menu selections that are available without device synchronization, such as viewing counters while the terminal remains in service simplifies diagnostics by providing easy-to-understand entry screens and reports test results in understandable phrases a sequencing capability allowing the terminal to perform each command in the sequence without any operator input except an enter keystroke device self tests and operator messages to be included in sequences a simplified status list that compiles supply, device and fault status on one easy-to-understand report; entries are date stamped and all codes are declared in the manual System Messages of CSC-W32. allows the cash position data (balancing data) to be entered into the terminal help text (extensive, context-sensitive, online help) the Operator Panel has status lights that indicate the terminal status messages can be displayed on the Operator Panel as soon as the situation occurs (in-service, out-of-service, door open, door closed)
q q
q q q q
Each institution can configure the service and operator functions menu structure to fit the specific needs of the institution with a special tool called SOPCONF. With SOPCONF you can create operator groups, limiting which commands each group is authorized to use. With the SOP itself you can specify special groups with own passwords.
Automatic return
The automatic return to previous mode feature configures a terminal to automatically return to service after exiting SOP mode, if the terminal was in-service before entering SOP mode. If the feature is disabled, the terminal remains out-of-service after exiting SOP. This option can be downloaded with the customization table load command (see ProCash/NDC ProConsult/NDC Installation manual Optional Parameters (NDC)).
46
October 2004
U25604-J-Z745-1-7600
Modes of Operation
Rear Balancing
In-service
By default, the terminal accepts load command messages while in-service. It also processes the Terminal Command message requesting configuration information, even if a customer is on the terminal.
Rear Balancing
On Wincor Nixdorf terminals the rear balancing functions can be performed in two ways:
q q
on rear load terminals on the operator panel on front load terminals on the screen
Start Rear Balancing

q
Rear load terminals If the ProSop is in use, the rear balancing function is part of the User Exit interface and can be called within the Individual Functions menu. If the ProCash/NDC-SOP or ProConsult/NDC-SOP is in use, the rear balancing function is integrated in the step table configuration. If the rear balancing function has been entered, the script framework calls step functions as configured in the step configuration file LYNXSOP.INA. Refer to the ProCash/NDC-DDC Programmers Reference manual for details regarded to rear balancing step functions.
Front load terminals On front loads the rear balancing functions will be performed in the same way. The only difference is that supervisor mode is entered on the consumer display. The supervisor mode must be activated using the green SOP button on the right-hand side under the customer console in the front. You have to open the front door of the safe to reach the button. The operator screen will be displayed 2 or 3 seconds after pressing the button. Then you can select the options with the PIN PAD and softkeys.
U25604-J-Z745-1-7600
October 2004
47
Rear Balancing
Modes of Operation
Customize Rear Balancing functions

To build up rear balancing functions for the operator panel or consumer screen, you have to create a step table which is stored in section ..\LYNXSOP\ REAR_BALANCING see ProCash NDC/DDC Programmers Reference for detailed description of step functions and how to create step tables. The parameter file LYNXSOP.INA in C:\PROTOPAS\CONF can be used to enhance or replace the existing steps against your rear balancing steps. Rear Balancing default configuration
[REAR_BALANCING] STEP_START = "START" STEP_ABORT = "ABORT" [REAR_BALANCING\ABORT] STEP_FUNC = "APPL_STOP_REAR_BAL" STEP_PARAM = "" JUMP_ON_RC = "RET_ERROR" [REAR_BALANCING\RET_OK] STEP_FUNC = "RETURN" STEP_PARAM = "0" [REAR_BALANCING\RET_ERROR] STEP_FUNC = "RETURN" STEP_PARAM = "1" [REAR_BALANCING\START] STEP_FUNC = "DISPLAY_CONFIRM_MSG" STEP_PARAM = "No Rear Balancing Configured!,2,1" JUMP_ON_RC = "RET_ERROR,RET_ERROR,RET_ERROR"
48
October 2004
U25604-J-Z745-1-7600
Modes of Operation
Dispense Below Zero
Dispense Below Zero

Since release 1.2 ProCash/NDC is able to perform dispense operations when the physical cassettes counters become negative. Some customers have requested this behavior for host environments where counter actualization is not mandatory after every time when cashout cassettes will be refilled with cash. That means at least, cashout cassettes can be refilled without updating the local cassette counters where dispensing is possible immediately after cassette insertion (and cassette logon via SOP if automatic logon is NOT enabled). How to configure Dispense Below Zero: Dispense Below Zero can be enabled via following parameter in CUSTOM.PPF: SECTION PARAMETER
[CASH_DISPENSER DISPENSE_BELOW_ZERO Please refer to ProCash/NDC ProConsult/NDC Installation manual for detailed description of this parameter. Restrictions:
q
Dispense Below Zero can be used with ProCash/NDC-SOP only. If the ProSop is in use you get counter mismatches between the ProSop counters (received from WOSA) and the recalculated counters in the User Exit function provided by ProCash/NDC. Dispense Below Zero cannot be used together with ProView. Because ProView is requesting for the WOSA counters and does not get the recalculated counters from ProCash/NDC. Dispense Below Zero can be used only for cash out systems when the logical WOSA service (BSATM32.DLL) is configured. It is mandatory to install cashout cassettes with a physical LOW sensor to be able to send a Money Low unsolicited message to the host, because the logical cassettes counters never fall down below the low threshold.
U25604-J-Z745-1-7600
October 2004
49
Dispense Below Zero Changes of cash counter behaviour:
Modes of Operation
If Dispense Below Zero is enabled ProCash/NDC handles the internal counters as follows: As long as the number of notes remaining in the cassette is higher or equal than 500 notes, the counters are calculated in the standard way. If the remaining counter is lesser than 500 notes, the counter maintained in the CashUnitInfo() structure of WOSA will be encreased with 500 notes via SetCuInfo() call from ProCash/NDC framework dcCdmFW. That has the effect that the WOSA counter will not fall down to zero or below zero in any case. WOSA is not able to handle negative counters. (The counters of WOSA would remain zero for all following dispenses. The result is that the counters of rejected and dispensed notes get lost.) Temporarily the number of notes added for each cassette is stored in the CMOS. The CMOS counters are used to recalculate back the original counters for the NDC Supply counter message and SOP Cash supply counters. Send Supply Counters terminal response: If the remaining counter for a cassette becomes negative, the counter number of notes remaining in cassette is set to 65535 (FFFF) in the Supply Counters solicited message. The counters number of notes dispensed and rejected are still maintained with the actual values. Display or Print Cash Supplies in ProCash/NDC-SOP: For cassettes with negative counters only the number of rejected and dispensed notes are displayed or printed in the Cash Counters supply function. All other counter values are blanked out.
50
October 2004
U25604-J-Z745-1-7600
Miscellaneous Operations
ADRS operation
ADRS by ProCash/NDC The ProCash/NDC application periodically checks several devices of a self service terminal and the application tries to repair them if neccessary. This function is called Automatic Device Repair System (ADRS). Especially the shutters and transport ways of input and output devices (Cash Dispenser Module, Deposit Module, CashIn Module, etc.) are checked after each consumer transaction. If status requests to the device are returned with transport jams or device not operational, the application actively tries to repair them via reset, or shutter close commands. During silent service ADRS is called 3 times in a 60 second time cycle. ADRS methods in ProCash/NDC are implemented for the following devices:
q
Cash Dispenser Module

Checks shutter and transport way status, performs retract or close shutter commands, sends status message to the host
q q q q
Deposit Module
Checks shutter status, sends status message to the host, performs retract
Receipt Printer
Checks supply status, sends low/out status message to the host
Journal Printer
Document Printer
ADRS by WOSA WOSA (ProDevice) also uses ADRS for the Cash Dispenser device. In a configurable time cycle the status of the device is checked and if neccessary, a reset command is initiated by the WOSA service (Wincor Nixdorf systems only). ADRS by Firmware In specific conditions the firmware itself performs ADRS through automatic resets (resp. for the cash dispenser so called clearing run). The ADRS behavior can be controlled via configuration parameters. Please refer to ProCash/NDC Installation Manual and ProDevice parameter specification for ADRS configuration parameters.
U25604-J-Z745-1-7600
October 2004
51
ADRS operation
Miscellaneous Operations
52
October 2004
U25604-J-Z745-1-7600
Configuration Data
Configuration data is down-line loaded from the network to each terminal using a series of load command messages. Configuration data is divided into four categories:
q
States The states table directs the terminal to the tasks to be performed during each part of a transaction. Refer to section States on page 54 for details. Screens Screen data contains display, control, and delimiter characters for different screens which must be shown during different parts of a transaction. Refer to section Screens on page 153 for details. Miscellaneous Configuration Data Consists of terminal parameters (capabilities), LUNO (a unique number identifying each terminal), and terminal timer values. Refer to section Miscellaneous Configuration Data on page 166 for details. FIT Financial Institution Tables entries provide information which is used for identifying which institution has issued a particular card, decoding or encoding of data and for electronic fund transfers. Refer to chapter Security Features on page 175 for details.
Downloaded configuration data are stored in the registry location LYNXCI after a "Set Config ID" load command is received. From now on the terminal will be loaded automatically with the configuration data of the registry when the application starts up as long as the terminal has not received any new customization data. When power is restored or the terminal is turned on, the network requests a configuration ID from the terminal. If the configuration ID sent by the terminal does not match the configuration ID at the network, the network will usually send a new configuration load to the terminal. Terminals connected to the network are assigned to distinct groups. A network programmer can create unique configuration data for each group, thereby giving each group of terminals its own "personality", e.g. for systems of different type or purpose.
U25604-J-Z745-1-7600
October 2004
53
States
Configuration Data
States
The states configuration data is down-line loaded using the States Table Load command message (refer to section State Tables Load on page 239). Each state is associated with a specific task. For example, while the terminal is in the select function state the terminal is dedicated to the task of prompting the consumer to select a function and recognizing the key (function) selected. Only those subroutines and hardware components (such as screen and keyboard) that facilitate function selection are used. The terminal requires the repeated use, in different ways, of some states. For instance, the consumers have to select the type of transaction (deposit, withdrawal, inquiry or other) and later they have to select the type of account. Both tasks are performed using different versions of the select function state. Each state type can have one or more state tables associated with it. Each state table of the same state type is a different version of that state providing the same type of functions, but used in a different manner. The different state tables are specified by a three-digit decimal number (000 through 999). This range allows up to 1000 different state tables. Each state table contains nine entries. 1. A state table is 25 characters long (first entry, which is one character long, plus eight three-digit entries). 2. The first entry in a state table is a single character identifying the type of state (ASCII graphic character). 3. The other eight entries are used to specify the actions performed (such as screen displayed, buffers used and next state table) and are three characters long.
State table 000 is the first state table that the terminal is in when it enters in-service mode. State table 000 is usually a card read state. The terminal should always return to a close state after the consumers transaction(s) have been completed. The terminal may use one state type several times while processing a transaction; depending on the transaction that the costumer has requested, other state types might not be used at all. The use of these state types, in any order, defines terminal operation.
54
October 2004
U25604-J-Z745-1-7600
Configuration Data A summary of all the state types is shown in the following tables.
Table 5: State summary
States
State Name Card Read PIN Entry Unlock Envelope Dispenser Preset Operation Code Buffer FDK Selection
State Description Type A B C Reads the magnetic stripe from the ID card and then usually indicates a PIN entry state as the next state. Reads the PIN number entered by the customer and verifies that the PIN entered is valid. After this state the terminal immediately goes to the next state. Clears and sets any or all 8 bytes of the operation code buffer. Reads the code of each operation key pressed by the customer. The key codes are stored in the operation code buffer. The next state varies depending on the customers selection. Reads the entered amount, displays that amount on the screen, and stores it in the amount buffer. If a withdrawal transaction is being processed, an amount check state will normally be the next state. Otherwise, a Preset Operation Code Buffer state will usually be the next state. Verifies that the amount entered is a whole amount (zero cents). If the amount entered by the customer is not a whole amount, the next state is always determined by the network configuration. Otherwise, a Preset Operation Code Buffer state will typically be the next state. Reads in a variable-length string of numerical keys and stores that data in a general purpose buffer. Optionally, the terminal displays the data on the screen. If the customer presses the cancel key, an operation key, or times-out during data entry, the input string is terminated. The next state depends on the customers input.
Amount Entry
Amount Check
Information Entry
U25604-J-Z745-1-7600
October 2004
55
States
Configuration Data
State Name Transaction Request
State Description Type I Sends a Transaction Request message to the network and executes the Transaction Reply commands received from the network. The next state depends on the network response. Returns or retains the customers card and optionally issues a printed acknowledgment form to the customer. Typically, the next state table used is 000 (a card read state preparing the terminal for the next customer). Used to modify selection paths based on FIT table entry and institution type. The terminal can use customized state tables for the customers of a specific institution. The terminal can provide different functions to different customers depending on the customers institution. During this state, the terminal writes the contents of the track 3 data buffer onto the magnetic stripe of a card Same functions as B state, but including updating track data on the ID card. This card read state is used, if the application requires that the number of the card read state be something other than 000. The Hardware Fitness state checks for fatal error condition of the terminal devices. It goes to the specified next state depending on devices which have a fatal condition. The extension of this state checks for warning conditions und uses the specified next state exit. The Smart FIT Check state performs a FIT check with the chip data that is read from the chip of a smart card. The Skip Step is used to skip states which are not supported by ProCash/NDC or ProConsult/NDC. R Reads the entered amount, displays it on the screen, and stores it in the Amount buffer, General Purpose buffer B or C buffer.
Close
FIT Switch
Card Write Enhanced PIN Entry
L M
Card read T (Non-000 state applications) Hardware Fitness h
Smart FIT Check Skip Step Enhanced Amount Entry
56
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
State Name
State Description Type In this state the flow of a transaction is switched on whether a language code is present in the card data or not. In this state one set of state tables can be used to display screens in different languages within the same transaction. This is determined by a code on the cardholders card. This state reads the data buffer from the 8 FDK selection state to identify which next state the terminal should go. This state translates the FDK selected by the cardholder into a value that is placed in the specified buffer for use by an FDK switch state. This state reads the FDK selected by the cardholder, stores the key code in an FDK buffer for use by an FDK switch state, and updates the operation code buffer. This state allows the consumer to change the PIN. This state allows the consumer to set the audio volume for the played message and to switch audio channels. FIT switch state with enhanced number of next states depending on the specified switch index in the FIT table. The Extension state extends the functions of state S, T, X, k and Y. The Extension state can be activated in the extension state number field of the state.
Language S Code Switch Language Select from Card FDK Switch V
FDK Information 8 FDK Selection
Customer b Selected PIN Audio Control Expanded FIT Switch Extension i _
U25604-J-Z745-1-7600
October 2004
57
States
Configuration Data
Steps processing
ProCash/NDC or ProConsult/NDC uses step oriented functions for each state. Every downloaded state is assigned to a specific ProCash/NDC or ProConsult/NDC step. The step assignment is stored in the Windows registry location ..\LYNXPAR\STATE_MAP The following table shows, which NDC state is assigned to a ProCash/NDC or ProConsult/NDC step:
Table 6: ProCash/NDC, ProConsult/NDC steps belonging to NDC states
State Type
A B C D E F G H I J K L M N
Step
DC_CARD_READ DC_PIN_ENTRY DC_DISPENSE_ENVELOPE DC_PRESET_OP_CODE DC_FDK_SELECT4 DC_AMOUNT_ENTRY DC_WHOLE_DOLLAR_CHECK DC_INFORMATION_ENTRY DC_TRAN_REQUEST DC_CLOSE_TRAN DC_FIT_SWITCH DC_WRITE_CARD DC_ENH_PIN_ENTRY DC_CAMERA_CONTROL
State Type
S T V W X Y Z _ b i P R k all states
Step
NDC_LANGUAGE_SWITCH NDC_CARD_PIN NDC_CARD_LANGUAGE NDC_FDK_SWITCH NDC_FDK_INFO_ENTRY NDC_FDK_SELECT NDC_EXT NDC_EXP_FIT_SWITCH NDC_CUST_SEL_PIN NDC_AUDIO_CONTROL NDC_EXP_FIT_SWITCH NDC_ENH_AMOUNT_ENTRY DC_HARDWARE_FITNESS [1] DC_NEXT_X (X = 1-8) [1]
[1] -
Wincor Nixdorf specific state
58
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Card Read State (A)

The Card Read state is usually the first state used during transaction processing. This state table is normally assigned to the state number 000. The terminal enters state number 000 automatically when placed in-service. The Card Read state table performs the following functions:
q q q q
identifies the number of the screen displayed for prompting card entry identifies the screen displayed after a misread defines the card track(s) from which data is read contains a flag for the card return feature (immediately or at the end of the transaction) indicates the next state number for cards that are read properly scans the FIT to obtain a match on the financial institution number tells the terminal the next state to go to if there is no FIT match
q q q
Table 7: Card Read state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number correct read next state number error (misread) screen number read condition 1 read condition 2 read condition 3 card return flag no FIT match next state number
U25604-J-Z745-1-7600
October 2004
59
States The card read (A) state entries are defined as follows: State type Entry number: 1 Valid range: Description: A
Configuration Data
This state ID identifies this state table as a Card Read state table.
Screen number Entry number: 2 Valid range: Description: 000-999 This is the number of the screen which prompts the customer to insert a card. This screen is displayed while the terminal is awaiting card entry.
Good read next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The number of the state the terminal enters after the customers card is read properly. Normally the next state is a PIN entry state type.
Error (misread) screen number Entry number: 4 Valid range: Description: 000-999 This is the number of the screen displayed if the card is not read properly. Normally, this screen will prompt the customer to check that the card is inserted correctly and to reinsert the card.
60
October 2004
U25604-J-Z745-1-7600
Configuration Data Read condition 1 Entry number: 5 Valid range: Description: 001-015
States
This is one of the three entries (used with entry no. 6 and 7) that tell the terminal which card track(s) must be read. This is the first read condition. If this condition cannot be met, read condition 2 is used next. Refer to table Card Read state entries for the definition of the card read conditions.
Read condition 2 Entry number: 6 Valid range: Description: 001-015 This is one of the three entries (used with entry no. 5 and 7) that tell the terminal which card track(s) must be read. This is the second read condition used. This one is used if read condition 1 cannot be done. If read condition 2 cannot be met, read condition 3 is used. Refer to table Card Read state entries for the definition of the card read conditions.
Read condition 3 Entry number: 7 Valid range: Description: 001-015 This is one of the three entries (used with entry no. 5 and 6) that tell the terminal which card track(s) must be read. If neither read condition 1 or read condition 2 can be met, this read condition is used. Refer to table Card Read state entries for the definition of the card read conditions.
Card return flag Entry number: 8 Valid range: Description: 000-001 This entry tells the terminal whether the card should be returned immediately or upon transaction completion. The valid values are as follows: 000 - return card immediately 001 - return card upon transaction completion
U25604-J-Z745-1-7600
October 2004
61
States No FIT match next state number Entry number: 9 Valid range: Description: 000-254, 256-999
Configuration Data
The number of the state the terminal enters if the FIT number on the card does not match that of any member institution.
Table 8: Read condition entry definitions
Required track(s)
Card read table Entry 5 (read condition 1) 1 only 004 2 only 002 3 only 001 1 and 2 006 1 and 3 005 2 and 3 003 1 and 2 and 3 007 2 or 3 002 1 or 3 004 1 or 2 004 1 or2or3 004 (1 and 2) or (1 and 3) 006 (2 and 1) or (2 and 3) 006 (3 and 1) or (3 and 2) 005 1 or (2 and 3) 004 2 or (1 and 3) 002 3 or (1 and 2) 001 Chip connect only 008 3 and chip connect 009 2 and chip connect 010 2, 3 and chip connect 011 1 and chip connect 012 1, 3 and chip connect 013 1, 2 and chip connect 014 1, 2, 3 and chip connect 015
Card read table Entry 6 (read condition 2) 004 002 001 006 005 003 007 001 001 002 002 005 003 003 003 005 006 008 009 010 011 012 013 014 015
Card read table Entry 7 (read condition 3) 004 002 001 006 005 003 007 001 001 002 001 005 003 003 003 005 006 008 009 010 011 012 013 014 015
62
October 2004
U25604-J-Z745-1-7600
Configuration Data
Short desciption to Table 8:
States
If read condition 1 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, read condition 2 is attempted. If read condition 2 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, read condition 3 is attempted. If read condition 3 is satisfied, the good read next state number entry (table entry 3) is taken. Otherwise, the card is ejected and the error screen number (table entry 4) is displayed.
U25604-J-Z745-1-7600
October 2004
63
States
Configuration Data
PIN Entry State (B)

The PIN Entry state prompts the customer to enter the PIN and displays an X for each PIN digit entered. FIT determines whether the terminal performs PIN verification (local PIN verification) or whether this is done by the network (remote PIN verification). If local PIN verification is used, the terminal does not use state entry 8. If remote PIN verification is used, the terminal does not use state entry 5. For details on each PIN verification method, refer to chapter Security Features on page 175.
Table 9: PIN Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number local PIN check, correct PIN next state number local PIN check, maximum bad PINs next state number local PIN check, error screen number remote PIN check, next state number local PIN check, maximum PIN attempts
The PIN Entry (B) state entries are defined as follows: State type Entry number: 1 Valid range: Description: B This state ID identifies this state table as a PIN Entry state table.
64
October 2004
U25604-J-Z745-1-7600
Configuration Data Screen number Entry number: 2 Valid range: Description: 000-999
States
This is the number of the screen display that prompts the customer to enter the PIN. This screen is displayed when the terminal enters the PIN entry state. This screen must position the cursor at the beginning of the area where the Xs are displayed.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds if the customer fails to enter the PIN within the specified time limit. Enter 255 to deactivate the time-out function. Entering 255 keeps the terminal in this state until an operation key is pressed.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 This is the number of the state to which the terminal proceeds if the customer presses the cancel key.
Local PIN check, good PIN next state number Entry number: 5 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds after it verifies that the customer entered the correct PIN (if local PIN check). The number of digits to be checked are specified by FIT field PCKLN. Normally the next state is a Pre-Set Operation Code Buffer state.
U25604-J-Z745-1-7600
October 2004
65
States
Configuration Data
Local PIN check, maximum bad PINs next state number Entry number: 6 Vollud data range:000-254, 256-999 Description: The number of the state to which the terminal proceeds after the customer incorrectly enters the PIN the number of times specified by state entry 9. Normally, the next state is a close state.
Local PIN check, error screen number Entry number: 7 Valid range: Description: 000-999 The number of the screen display that prompts the customer to enter the PIN again. This screen is displayed each time the customer enters an incorrect PIN until the retry value is reached as specified by state entry 9 (or by the card). This screen must position the screen cursor at the beginning of the area in which the Xs are displayed.
Remote PIN check, next state number Entry number: 8 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds if no local PIN check is specified in FIT.
Local PIN check, maximum PIN attempts Entry number: 9 Valid range: Description: 000-009 This entry specifies the maximum number of times that a customer can enter an incorrect PIN before the terminal goes to the state specified by state entry 6. (This can be overridden by an entry on the card if such is specified by the FIT. Typically used in the M state.)
66
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Customer Selectable PIN State (b)

This state allows the cardholder to input a new PIN. It differs from the PIN entry state (B) in the number of retries. The state will prompt for the new PIN twice and will take a good exit if both are the same and local PIN check is enabled. If checking is local, the exit will be taken when the two new PINs have been built into the PIN blocks for transmitting. If checking is enabled and the two PINs entered are not the same the cardholder wil be asked to re-enter the Customer Selectable PIN (CSP) and the state will not exit. If the FIT specifies that short PIN entry is to be tested for, short PINs will be regarded as one try against the limit specified in the state table. The screen association for this state is derived from screen specified in table entry 2. The cardholder PIN is entered on the facia keyboard and consists of four to sixteen digits. If the number of digits entered is less than the value specified in the FIT entry PMXPN the cardholder must press FDK A or ENTER key on the facia keyboard after the last digit entered . The CLEAR key clears all digits.
Table 10: Customer Selectable PIN state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type first entry screen number time-out next state number cancel next state number good next state number CSP fail next state number second entry screen number mismatch first entry screen number extension state number
U25604-J-Z745-1-7600
October 2004
67
States
Configuration Data
The Customer Selectable PIN (b) state entries are defined as follows: State type Entry number: 1 Valid range: Description: b This state ID identifies this state table is a Customer Selectable PIN state table.
First entry screen number Entry number: 2 Valid range: Description: 000-999 Display screen that prompts the cardholder to enter the PIN the first time.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 State number to which the terminal goes if the cardholder does not make a CSP entry within the specified time limit. Enter 255 if the time-out function is not required.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 State number to which the terminal goes if the cardholder presses the CANCEL key to stop the CSP transaction.
Good next state number Entry number: 5 Valid range: Description: 000-254, 256-999 State number to which the terminal goes if the cardholder enters a matching pair of new PIN values.
68
October 2004
U25604-J-Z745-1-7600
Configuration Data CSP fail next state number Entry number: 6 Valid range: Description: 000-254, 256-999
States
State number to which the terminal goes if the cardholder fails to enter a matching pair of new PIN digits or the maximum number of retries for local PIN checking is reached. This state will also be taken if: 1. No FIT match 2. Cardholder tampering is detected. 3. PIN block generation fails.
Second entry screen number Entry number: 7 Valid range: Description: 000-999 Display screen used to ask for confirmation of the CSP.
Mismatch first entry screen number Entry number: 8 Valid range: Description: 000-999 Displays a new screen that replaces the screen for table entry 2 on each attempt after a CSP pair attempt did not match or an error has occurred and there are still further retries allowed.
Extension state number Entry number: 9 Valid range: Description: 000-254, 256-999 State number of the extension state.
U25604-J-Z745-1-7600
October 2004
69
States
Configuration Data
Extension to state (b)

This state extends the Customer selected PIN state regarding number of PIN entry attempts and type of PIN verification.
Table 11: Extension state entries
Entry 1 2 3 4-9
Definition state type number of attempts allowed to enter a matching CSP pair use local verification of new PIN pair attempts reserved, must be 000
The Extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies that this state table is an Extension state.
Number of attempts allowed to enter a matching CSP pair Entry number: 2 Valid range: Description: 000-010 Limits the number of attempts the cardholder may make to select a new PIN. A zero entry means no limit.
Use local verification of new PIN pair attempts Entry number: 3 Valid range: Description: 000-001 Specifies which attempts are to be verified locally: 0 - Do not verify locally 1 - Verify both attempts locally. Result available in transaction request field U.
70
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Envelope Dispense (C) State

The Envelope Dispense (C) state tells the terminal how to process a deposit operation. If there are still enough envelopes in the deposit module and the local parameter DISPENSE_ENVELOPE is enabled, the envelope is dispensed within the envelope dispense (C) state. If the local parameter DISPENSE_ENVELOPE is disabled, the Envelope Dispense (C) state immediately enters the next state exit without an envelope dispense operation. Envelope dispensing takes place in the deposit function of the transaction reply. Refer to ProCash/NDC ProConsult/NDC Installation manual for detailed parameter description.
Table 12: Envelope Deposit (C) state entries
Entry 1 2 3-9
Definition state type next state number reserved, must be 000
The Envelope Deposit (C) state entries are defined as follows: State type Entry number: 1 Valid range: Description: C This state ID identifies this state table as an Envelope Deposit state.
Next state number Entry number: 2 Valid range: Description: 000-511 The number of the state to which the terminal proceeds after entering state C.
U25604-J-Z745-1-7600
October 2004
71
States
Configuration Data
Pre-Set Operation Code Buffer State (D)

The operation code buffer is eight bytes long. The Pre-Set Operation Code Buffer state can do any combination of the following:
q
Clear the operation code buffer or clear selected bytes of the operation code buffer. Pre-set selected bytes of the operation code buffer with A, B, C, or D and F, G, H or I
Each bit of the masks in this state represents a byte (buffer position) in the operation code buffer. Bit 0 of the mask represents the first byte; bit 7 of the mask represents the eighth byte.
Table 13: Pre-Set Operation Code Buffer state table
Entry 1 2 3 4 5 6 7 8 9
Definition state type next state number clear mask A preset mask B preset mask C preset mask D preset mask reserved extension state number
The Pre-Set Operation Code Buffer (D) state entries are defined as follows: State type Entry number: 1 Valid range: Description: D This state ID identifies this state table as a Pre-Set Operation Code Buffer state table.
72
October 2004
U25604-J-Z745-1-7600
Configuration Data Next state number Entry number: 2 Valid range: Description: 000-254, 256-999
States
The number of the state to which the terminal proceeds after clearing or presetting the operation code buffer.
Clear mask Entry number: 3 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be cleared to graphic "space." Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is not set (zero), the corresponding entry is cleared. If a bit is enabled (one), the corresponding entry is unchanged. Set this entry to 255 if none of the operation code buffer positions are to be cleared.
A Preset mask Entry number: 4 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be set to A. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to A. If a bit is disabled (zero), the corresponding entry is unchanged.
B Preset mask Entry number: 5 Valid range: Description: 000-255 Specifies bytes of operation codeoperation code buffer buffer to be set to B. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to B. If a bit is disabled (zero), the corresponding entry is unchanged.
U25604-J-Z745-1-7600
October 2004
73
States C Preset mask Entry number: 6 Valid range: Description: 000-255
Configuration Data
Specifies bytes of operation code buffer to be set to C. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to C. If a bit is disabled (zero), the corresponding entry is unchanged.
D Preset mask Entry number: 7 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be set to D. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to D. If a bit is disabled (zero), the corresponding entry is unchanged.
Reserved Entry number: 8 Valid range: Description: 000 Entry 8 is reserved and must be 000.
Extension State number Entry number: 9 Valid range: Description: 000-254 or 256-999 State number of the extension state containing information on how the other operation codes are preset.
74
October 2004
U25604-J-Z745-1-7600
Configuration Data Clear mask (entry 3) example Start with an operation code buffer that looks like the following:
Buffer Bit Pos Weight B 0 1 _ 1 2 _ 2 4 C 3 8 _ 4 16 _ 5 32 D 6 64 _ 7 128
States
To clear buffer position 6 (byte 6), add the weights of the positions that you do not want to clear and put that result in the clear mask entry (entry 3).
Buffer Bit pos Positions not cleared Weights not cleared B _ 0 1 X X 1 + 2 + 4 _ 2 X + 8 + C 3 X 16 + _ 4 X 32 + _ D 5 6 X 128 = 191 _ 7 X
With 191 entered in entry 3, the resultant operation code buffer would appear as follows:
Buffer Bit pos B 0 _ 1 _ 2 C 3 _ 4 _ 5 _ 6 _ 7
A, B, C, D preset masks (entries 4-7) example Assume that you want to set the operation code buffer positions as follows:
q q q q
positions 0 and 2 to A positions 1 and 5 to B position 3 to C positions 4 and 7 to D
The buffer would appear as follows:

Buffer Bit pos Weight A 0 1 B 1 2 A 2 4 C 3 8 D 4 16 B 5 32 _ 6 64 D 7 128
The entries would have to be set as follows:

q q q q
entry 4 (A preset mask) entry 5 (B preset mask) entry 6 (C preset mask) entry 7 (D preset mask) -
1+4 2 + 32 8 16 + 128
= 005 = 034 = 008 = 144
U25604-J-Z745-1-7600
October 2004
75
States
Configuration Data
Extension to State (D)

The extension to state (D) allows presetting the operation code buffer with F, G, H or I.
Table 14: Preset operation code buffer Extension state table
Entry 1 2 3 4 5 6-9
Definition state type F preset mask G preset mask H preset mask I preset mask reserved must be 000
The Pre-Set Operation Code Buffer Extension (Z) state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as an Pre-Set Operation Code Buffer Extension state.
F Preset mask Entry number: 2 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be set to F. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to F. If a bit is disabled (zero), the corresponding entry is unchanged.
76
October 2004
U25604-J-Z745-1-7600
Configuration Data G Preset mask Entry number: 3 Valid range: Description: 000-255
States
Specifies bytes of operation code buffer to be set to G. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to G. If a bit is disabled (zero), the corresponding entry is unchanged.
H Preset mask Entry number: 4 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be set to H. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to H. If a bit is disabled (zero), the corresponding entry is unchanged.
I Preset mask Entry number: 5 Valid range: Description: 000-255 Specifies bytes of operation code buffer to be set to I. Each bit relates to a byte in the operation code buffer. Bit 0 relates to the first entry; bit 7 relates to the eighth entry. If a bit is enabled (one), the corresponding entry is set to I. If a bit is disabled (zero), the corresponding entry is unchanged.
U25604-J-Z745-1-7600
October 2004
77
States
Configuration Data
Four FDK Selection Function State (E)

This state reads the operation key that has been pressed by the cardholder, stores the key code in the operation code buffer, and then advances to the next state. This state permits the customer to select one function from up to four functions displayed on the screen, by pressing one of the active operation keys. The state table data for this state type defines which of the four operation keys are to be active during this state.
Table 15: Four FDK Select Function state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number operation key A next state number operation key B next state number operation key C next state number operation key D next state number operation code buffer location
The Four FDK Selection Function (E) state entries are defined as follows: State type Entry number: 1 Valid range: Description: E This state ID identifies this state table as a Function Selection state table.
78
October 2004
U25604-J-Z745-1-7600
States
The number of the display screen which prompts the customer to choose between transaction types, account names, etc.. This screen is displayed upon entry into the selection function state and must be aligned with the active operation keys (table entry 5, 6, 7, and 8) for proper operation.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer fails to make the selection within the specified time limit (specify "255" if the time-out function is not used).
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the cancel key instead of an operation key.
Operation key A next state number Entry number: 5 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the A operation key (specify "255" to deactivate the A operation key during this state).
Operation key B next state number Entry number: 6 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the B operation key (specify "255" to deactivate the B operation key during this state).
U25604-J-Z745-1-7600
October 2004
79
States Operation key C next state number Entry number: 7 Valid range: Description: 000-254, 256-999
Configuration Data
The state number to which the terminal proceeds if the customer presses the C operation key (specify "255" to deactivate the C operation key during this state).
Operation key D next state number Entry number: 8 Valid range. 000-254, 256-999 Description: The state number to which the terminal proceeds if the customer presses the D operation key (specify "255" to deactivate the D operation key during this state).
Operation code buffer location Entry number: 9 Valid range: Description: 000-007 Specifies the operation code buffer byte in which the key code for the selected operation key is to be stored. The network down-line loads the following data to select the indicated buffer byte: 000 = buffer 001 = buffer 002 = buffer 003 = buffer 004 = buffer 005 = buffer 006 = buffer 007 = buffer position 0 position 1 position 2 position 3 position 4 position 5 position 6 position 7 Buffer positions are as follows: ________ 01234567
80
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Amount Entry State (F)

This state reads the amount entered by the consumer, displays it on the screen and saves it in the amount buffer. This buffer is 8 or 12 bytes long. In the amount entry state, the operation keys are used by the consumer to indicate whether the displayed amount is either correct or incorrect.
Table 16: Amount Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number operation key A next state number operation key B next state number operation key C next state number operation key D next state number display amount screen number
The Amount Entry (F) state entries are defined as follows: State type Entry number: 1 Valid range: Description: F This state ID identifies this state table as an Amount Entry state table.
Screen number Entry number: 2 Valid range: Description: 000-999 Number of display screen that prompts an amount entry. This screen is displayed upon entry into the amount entry state.
U25604-J-Z745-1-7600
October 2004
81
States Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999
Configuration Data
The state number to which the terminal proceeds if the customer fails to enter the amount within the specified time limit (specify "255" if the time-out function is not used).
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the cancel key before pressing an operation key. Value "255" deactivates the CANCEL key during this state.
Operation key A next state number Entry number: 5 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the A operation key. Value "255" deactivates the A operation key during this state.
Operation key B next state number Entry number: 6 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the B operation key. Value "255" deactivates the B operation key during this state.
Operation key C next state number Entry number: 7 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.
82
October 2004
U25604-J-Z745-1-7600
Configuration Data Operation key D next state number Entry number: 8 Valid range: Description: 000-254, 256-999
States
The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.
Normally one operation key is used to indicate whether the amount entry is correct and another is used to indicate whether it is incorrect. The other operation keys are inactive. Display amount screen number Entry number: 9 Valid range: Description: 000-999 Overlay screen number that sets the screen cursor position. This screen optionally defines the initial display format prior consumer amount entry. The cursor should be set on the lefthand side of the echo field on the screen. This is space filled until the required start position for the currency character is reached. Default echo field for eight digits: bbbbb$ 0.00 (where b = space) Default echo field for twelve digits: bbbbbbbbb$ 0.00 (where b = space)
U25604-J-Z745-1-7600
October 2004
83
States
Configuration Data
Amount Check State (G)

This state checks to see if the amount entered is a whole amount (zero cents). This state should follow the amount entry function state when a withdrawal transaction is being performed. When checking that an amount is dispensable, Central must have downloaded the Dispenser Currency Cassette Mapping Table. If this table has not been downloaded, or a currency type identified in table entry 7 is not present in the table, processing will proceed with non-whole amount entry next state number.
Table 17: Amount Check state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type whole amount entry next state number non-whole amount entry next state number buffer to be checked zero entry next state number (if table entry 8 is zero) or integer multiple value (if table entry 8 is non zero) number of decimal places currency type amount check condition reserved must be zero
The Amount Check (G) state entries are defined as follows: State type Entry number: 1 Valid range: Description: G This state ID identifies this state table as a amount check state table.
84
October 2004
U25604-J-Z745-1-7600
Configuration Data Whole amount entry next state number Entry number: 2 Valid range: Description: 000-999
States
The state number to which the terminal proceeds upon finding 00 (zero cents) value in the amount entry.
Non-whole amount entry next state number Entry number: 3 Valid range: Description: 000-999 The state number to which the terminal proceeds upon finding a cents value other than 00 cents in the amount entry.
Buffer to be checked Entry number: 4 Valid range: Description: 000-002 This field specifies which buffer is to be checked: 000 - amount buffer 001 - general purpose buffer B 002 - general purpose buffer C Zero entry next state number Integer Multiple Value Entry number: 5 Valid range: Description: 000-999 If table entry 8 is zero: The state number to which the terminal proceeds, if the consumer enters zero amount or does not enter any value. If table entry 8 is non-zero: Integer multiple value used in checking specified buffer. For example, to check that the specified buffer contains a multiple of the minimum denomination $5, this field would be set to '005'. This field is ignored if table entry 8 is not 002.
U25604-J-Z745-1-7600
October 2004
85
States Number of decimal places Entry number: 6 Valid range: Description: 000-004
Configuration Data
Number of decimal places used in specified buffer. For example, $5 is sent as 500 cents, so has 002 decimal places.
Currency type Entry number: 7 Valid range: Description: 001-255 Currency type of amount in specified buffer. Used in conjunction with the Dispenser Currency Cassette Mapping Table. This field is ignored if table entry 8 is not '003'.
Amount check condition Entry number: 8 Valid range: Description: 000-003 If the condition being checked evaluates to 'true' then processing will proceed to the next state identified in table entry 2; otherwise processing will proceed to the next state identified in table entry 3. All conditions check the buffer indicated by table entry 4. All conditions except condition 000 take account of the decimal point location via the value in table entry 6. When this entry is set to 000, the state does not use state parameters 5 to 9, to enable backwards compatibility. When this entry is set to 001, the state evaluates whether the value to the right of the decimal point position is zero. When this entry is set to 002, the state evaluates whether the value is a whole number multiple of the value identified in table entry 5. When this entry is set to 003, the state evaluates whether the value is dispensable by the terminal, taking into account the currency type required (table entry 7), currency type denominations available, dispenser status and cassette status.
Reserved Entry number: 9 Valid range: Description: 000 Entry 9 is reserved and must be 000.
86
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Information Entry State (H)

This state reads in a variable-length string of numeric keys, saves the data in one of two general purpose buffers (see table entry 9), and displays either the data or X for each numeric key pressed. The input string is terminated by an operation key, cancel key, or a time-out. General purpose buffers B and C are variable in length. Maximum length is 32 bytes. When the terminal enters this state, the specified buffer contains only the data from the depressed numeric keys. If no keys are depressed, then the buffer contains no data.
Table 18: Information Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number operation key A next state number operation key B next state number operation key C next state number operation key D next state number buffer and display parameters
The Information Entry (H) state entries are defined as follows: State type Entry number: 1 Valid range: Description: H This state ID identifies this state table as an information entry state table.
U25604-J-Z745-1-7600
October 2004
87
States Screen number Entry number: 2 Valid range: Description: 000-999
Configuration Data
The number of the display screen that prompts key entry from the customer. This screen is displayed upon entry into the information entry state and must leave the cursor at the beginning of the data or X display area.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer fails to respond to the CRT message within a specified time limit. Value "255" disables the time-out function.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the cancel key before pressing an operation key.
Operation key B next state number Entry number: 6 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the B operation key. Value "255 deactivates the B operation key during this state.
88
October 2004
U25604-J-Z745-1-7600
Configuration Data Operation key C next state number Entry number: 7 Valid range: Description: 000-254, 256-999
States
The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.
Operation key D next state number Entry number: 8 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.
Buffer and display parameters Entry number: 9 Valid range. 000-323 Description: This entry specifies whether the actual data entered or X is to be displayed, beginning at the current cursor position. This entry also specifies which general purpose buffer (B or C) is used for storing the numeric data input and how many digits can be entered. The default buffer size of 32 digits can be decreased if the first two digits have a non zero value up to the maximum of 32. The valid characters are as follows: xx0 = xx1 = xx2 = xx3 = display X for each numeric key pressed; store keys in general purpose buffer C (max. 32 digits). display data as entered; store keys in general purpose buffer C (max. 32 digits). display X for each numeric key pressed; store keys in general purpose buffer B (max. 32 digits). display data as entered; store keys in general purpose buffer B (max. 32 digits).
Set a buffer limit example: 123 = display data as entered; store keys in general purpose buffer B with max. 12 digits.
U25604-J-Z745-1-7600
October 2004
89
States
Configuration Data
Transaction Request State (I)

The Transaction Request state tells the terminal what information to include in the transaction request message, transmits the transaction request message to the network, and waits for the network response. When the network responds with a Transaction Reply command message, the terminal executes the Transaction Reply command message and goes to the next state specified in the Transaction Reply command message. If the network does not respond with a Transaction Reply command message within the time specified by timer 03 (section Timer Data on page 167), the terminal goes to the state specified in entry 3 of this state.
Table 19: Transaction Request state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number network response time out next state number send track 2 data send track 1, track 3 send operation code buffer send amount buffer send PIN buffer (Buffer A) data / Select Extended format send general purpose buffer(s) B and/or C or Extension State Number (Range 000-254, 256-999)
The Transaction Request (I) state entries are defined as follows: State type Entry number: 1 Valid range: Description: I This state ID identifies this state table as a transaction request state table.
90
October 2004
U25604-J-Z745-1-7600
States
The number of the screen displayed while the terminal transmits a request to the network and waits for the associated Transaction Reply command. This is normally a Please Wait screen.
Network response time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the network does not respond to the transaction request in the time specified by timer 03 (section Timer Data on page 167). This timer checks for receipt of a Transaction Reply command message in response to a transaction request.
Send track 2 data Entry number: 4 Valid range: Description: 000-001 This field indicates whether track 2 data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data Send track 1, 3 Entry number: 5 Valid range: Description: 000-007 The track 1, 3 data entry specifies whether track 1 and/or track 3 data is sent to the network. The valid values are as follows: 000 - no additional tracks 001 - send track 3 only 002 - send track 1 only 003 - send track 1 and 3
U25604-J-Z745-1-7600
October 2004
91
States Send operation key data Entry number: 6 Valid range: Description: 000-001
Configuration Data
This field indicates whether the operation key data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data
Send amount buffer data Entry number: 7 Valid range: Description: 000-001 This field indicates whether the amount buffer data should be sent in the transaction request message. The valid values are as follows: 000 - do not send data 001 - send data Send PIN buffer data Entry number: 8 Valid range: Description: 000-001, 128 This field indicates whether the PIN buffer data should be sent in the transaction request message or when bit 128 is enabled use table entry 9 as an extension state definition. The valid bit values are as follows: 000 - do not send data 001 - send data 128 - use extension state specified in table entry 9
92
October 2004
U25604-J-Z745-1-7600
Configuration Data Send general purpose buffers B and/or C data Entry number: 9 Valid range: Description: 000-003, Extension state range: 000-254, 256-999
States
This field indicates whether the data from the general purpose buffers B and/or C should be sent in the transaction request message. If bit 128 is enabled in table entry 8 its meaning of this table entry changes to an extension state number definition. The valid values are as follows: 000 - do not send data from either buffer 001 - send general purpose buffer B data only 002 - send general purpose buffer C data only 003 - send general purpose buffers B and C data
Extension to state (I)

In the Extension state of the transaction request state additional buffers can be defined to be sent to the network.
Entry 1 2 3 4 5 6-9
Definition state type send general purpose buffers B and/or C send optional date fields A - H send optional data fields I - L send optional data fields Q - V reserved
The Extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as an Extension state table.
U25604-J-Z745-1-7600
October 2004
93
States Send general purpose buffers B and/or C data Entry number: 2 Valid range: Description: 000-003
Configuration Data
This field indicates whether the data from the general purpose buffers B and/or C should be sent in the transaction request message. The valid values are as follows: 000 - do not send data from either buffer 001 - send general purpose buffer B data only 002 - send general purpose buffer C data only 003 - send general purpose buffers B and C data
Optional data fields A - H Entry number: 3 Valid range: Description: 000-255 This entry is bit encoded to control the sending of individual optional data fields in the transaction request message. If a bit is set, the corresponding data field is sent. If a bit is clear, the data field is not sent. BIT 1 2 3 4 5 6 7 8 Field ID A reserved B reserved C D E F G H
94
October 2004
U25604-J-Z745-1-7600
Configuration Data Optional data fields I - L Entry number: 4 Valid range: Description: 000-015 This entry is as for entry 3 but with following values: BIT 1 2 3 4 5 6 7 8 Optional data fields Q - V Entry number: 5 Valid range: Description: 000-063 This entry is as for entry 3 but with following values: BIT 1 2 3 4 5 6 7 8 Field ID Q R S T reserved U V reserved reserved Field ID I J K L M reserved N reserved O reserved P reserved
States
U25604-J-Z745-1-7600
October 2004
95
States
Configuration Data
Close State (J)

The Close state should terminate the customers current terminal interface. This state performs the following functions:
q q
displays a screen completes any printing on the customer or journal printer that was initiated by a Transaction Reply command message. returns or retains the activator card as instructed by the Transaction Reply command message.
In addition, if the terminal returns the ID card and the consumer fails to remove the card within the time period specified by timer 02 (section Timer Data on page 167), the terminal will automatically retain the card.
Table 21: Close state entries
Entry 1 2 3 4 5 6 7 8-9
Definition state type transaction record form delivered screen number next state number no transaction record form delivered screen number card retained screen number Statement delivered screen reserved not used
The Close (J) state entries are defined as follows: State type Entry number: 1 Valid range: Description: J This state ID identifies this state table as a Close state table.
96
October 2004
U25604-J-Z745-1-7600
Configuration Data Transaction record form delivered screen number Entry number: 2 Valid range: Description: 000-999
States
The number of the display screen that asks the customer to please take the card and the transaction record form. This screen is displayed upon entry to the close state only if the customers card is returned and a transaction record form was printed.
Next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds after the close state is completed.
No transaction record form delivered screen number Entry number: 4 Valid range: Description: 000-999 The number of the display screen that asks the customer to please take the card. This screen is displayed upon entry to the close state only if the customers card is returned and no transaction record form was printed.
Card retained screen number Entry number: 5 Valid range: Description: 000-999 The number of the screen that informs the customer that the card has been retained. This screen is displayed upon entry to the close state only if the customers card has been retained by the terminal as instructed by the network. If the customer timesout, this screen is not displayed.
U25604-J-Z745-1-7600
October 2004
97
States Statement delivered screen Entry number: 6 Valid range: Description: 000-999
Configuration Data
Display screen to be overlaid when either the receipt is delivered (entry 2) or there is no receipt delivery (entry 4). This screen is only displayed if the statement is cut and delivered in a close state and the terminal has not been instructed by the last transaction reply message to capture the card
Reserved Entry number: 7 Valid range: Description: Not used Entry number: 8-9 Valid range: Description: Entries 8 and 9 are not used by ProCash/NDC or ProConsult/NDC. 000 Entry 7 is reserved and must be 000.
98
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
FIT Switch State (K)

The FIT Switch state allows the terminal to follow an alternate sequence of states and screens according to the value of the Primary Account Number (PAN) on the activator card. This state examines the PSTDX entry in the FIT to determine the next state number. Refer to section FIT (Financial Institution Table) on page 186 for a detailed explanation of the FIT tables. Each FIT designates a next state according to the institution type to which it applies. The next state executed is indexed in this table. For example, if the FIT identified during the Card Read state contains a PSTDX of 3, state entry 5 contains the next state number.
Table 22: FIT Switch state entries
Entry 1 2-9
Definition state type next state number
The FIT Switch (K) state entries are defined as follows: State type Entry number: 1 Valid range: Description: K This state ID identifies this state table as an FIT Switch state table.
U25604-J-Z745-1-7600
October 2004
99
States Next state number Entry number: 2-9 Valid range: Description: 000-254, 256-999
Configuration Data
Entries 2 through 9 contain the number of the state to which the terminal proceeds depending on the value in the PSTDX value of FIT.
These entries are defined as follows: Entry 2 3 4 5 6 7 8 9 Description next state number if PSTDX = 0 next state number if PSTDX = 1 next state number if PSTDX = 2 next state number if PSTDX = 3 next state number if PSTDX = 4 next state number if PSTDX = 5 next state number if PSTDX = 6 next state number if PSTDX = 7
100
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Card Write State (L)

During a Card Read state the card data buffers are cleared of all previous data. The Card Read state defines the card tracks to be read, and stores the card track data in the corresponding card data buffer. In the transaction request state, the terminal sends a transaction request message to central. You can specify whether or not track 1, 2 or/and track 3 data are included in this message. Central responds to this message by sending a transaction reply command to the terminal. Within this command is a field which contains updated track 1/2 or/and track 3 data. This data replaces any previous data in the terminals track data buffer. During the Card Write state the terminal writes the contents of the track 1/2/3 data buffer onto the magnetic stripe of the card. You specify which screen is to be displayed on the screen while writing takes place. Writing takes place only if the track data buffer contains data obtained from a successful track 3 read during a card read state, or updated track data from a transaction reply command. There are three next state numbers that the terminal can go to once it leaves the Card Write state. One exit is taken if the track write is successful. Another exit taken if the track write is unsuccessful. A third exit is taken if the track buffer is empty or contains invalid data and no writing is attempted. If the terminal is to write more than one track, the order will be first track 1, then track 2 and at least track 3. Before writing , a check is made to ensure that the data are valid. If the data are valid and a track write fails the terminal will not attempt any further requested track writes and the write state will exit. To use the Card Write state, the magnetic stripe card must still be in the reader. The following conditions must apply:
q
If table entry 8 of the Card Read state (Type A) is used, it must not be 000 (return card immediately) A card before cash transaction reply must not have been performed. A parallel eject/dispense and print (Fast Cash) transaction reply must not have been performed.
q q
U25604-J-Z745-1-7600
October 2004
101
States
Table 23: Card Write state entries
Configuration Data
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number good write next state bad write next state no write attempted reserved reserved reserved reserved
The Card Write state entries are defined as follows: State type Entry number: 1 Valid range: Description: L This state ID identifies this state table as the Card Write state.
Screen number Entry number: 2 Valid range: Description: 010-999 Screen displayed during card write operation.
Good Write next state Entry number: 3 Valid range: Description: 000-254, 256-999 State number goes to after a satisfactory track write operation.
102
October 2004
U25604-J-Z745-1-7600
Configuration Data Bad Write next state Entry number: 4 Valid range: Description: 000-254, 256-999 State number goes to if the track write is unsuccessful.
States
No Write attempted Entry number: 5 Valid range: Description: 000-254, 256-999 State number goes to if no data or invalid data is present in the track buffer. This state is also used if a start and/or end sentinel is missing.
Reserved Entry number: 6-9 Valid range: Description: 000 Must be 000 for each table entry.
U25604-J-Z745-1-7600
October 2004
103
States
Configuration Data
Enhanced PIN Entry State (M)

This state performs the same functions as the PIN Entry (B) state. It also supports track 3 retries if the FIT specifies local PIN check and indicates that there is a track 3 retry field on the card. If the FIT specifies track 3 retries but there is no data in the track 3 buffer, the Cancel Next state exit is taken. Before the customer can enter a PIN for a local PIN check with track 3 retries, the PIN retry field on the card is checked. For a Mutual Institutions Transfer System (MINTS) format card, the retry field of the track 3 data buffer must not equal or exceed the limit specified in state table entry 9. If an International Standards Organistation (ISO) format card is used, the retry field must not equal 0. If that is the case, in both situations the terminal exits to the Maximum Bad PINs Next state specified in table entry 6. This check is done before the start of each PIN entry attempt. After the PIN is entered by the customer and compared with the calculated PIN, the PIN retry field in the track 3 data buffer is updated. For MINTS format cards, if the entered PIN is correct, the PIN retry field is set to 0. For ISO format cards, the retry field is set to the value specified in state table entry 9. If the entered PIN is incorrect, the PIN retry field is incremented for MINTS format cards and decremented for ISO format cards. The updated track 3 data buffer is available for transmission through the Transaction Request state.The buffer can also be written on the card using the Card Write state.
Table 24: Enhanced PIN Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number local PIN check, correct PIN next state number local PIN check, maximum bad PINs next state number local PIN check, error screen number remote PIN check, next state number local PIN check, maximum PIN attempts
104
October 2004
U25604-J-Z745-1-7600
Configuration Data The Enhanced PIN Entry (M) state entries are defined as follows: State type Entry number: 1 Valid range: Description: M
States
This state ID identifies this state table as an Enhanced PIN Entry state table.
Screen number Entry number: 2 Valid range: Description: 000-999 This is the number of the screen display that prompts the customer to enter the PIN. This screen is displayed when the terminal enters the PIN entry state. This screen must position the cursor at the beginning of the area where the Xs are displayed.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds if the customer fails to enter the PIN within the specified time limit. Enter 255 to deactivate the time-out function. Entering 255 keeps the terminal in this state until an operation key is pressed.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 This is the number of the state to which the terminal proceeds if the customer presses the cancel key.
U25604-J-Z745-1-7600
October 2004
105
States Local PIN check, good PIN next state number Entry number: 5 Valid range: Description: 000-254, 256-999
Configuration Data
The number of the state to which the terminal proceeds after it verifies that the customer entered the correct PIN (if local PIN check). The number of digits to be checked are specified by FIT field PCKLN. Normally the next state is a Pre-Set Operation Code Buffer state.
Local PIN check, maximum bad PINs next state number Entry number: 6 Vollud data range:000-254, 256-999 Description: The number of the state to which the terminal proceeds after the customer incorrectly enters the PIN the number of times specified by state entry 9. This state could be a Card Write state in order to update the track 3 PIN retry field.
Local PIN check, error screen number Entry number: 7 Valid range: Description: 000-999 The number of the screen display that prompts the customer to enter the PIN again. This screen is displayed each time the customer enters an incorrect PIN until the retry value is reached as specified by state entry 9 (or by the card). This screen must position the screen cursor at the beginning of the area in which the Xs are displayed.
Remote PIN check, next state number Entry number: 8 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds if no local PIN check is specified in FIT.
106
October 2004
U25604-J-Z745-1-7600
Configuration Data Local PIN check, maximum PIN attempts Entry number: 9 Valid range: Description: 000-009
States
This entry specifies the maximum number of times that a customer can enter an incorrect PIN before the terminal goes to the state specified by state entry 6. This entry is used as the PIN retry count if the PIN retry count is not on the card (FIT entry PRCNT = FF).
Enhanced Amount Entry State (R)

This state reads the amount entered by the cardholder, displays it on the screen, and saves it in the buffers specified by the state table. Exit from the Enhanced Amount Entry state occurs when an active FDK is pressed, the Cancel key is pressed or a time-out occurs. The Enter key is equivalent to FDK A. The Clear key is always active and clears the amount entered and the screen echo field to allow data entry retries within the Amount Entry state. The Digital Audio Service can echo the keys pressed on the keyboard.
Table 25: Enhanced Amount Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number operation key A next state number operation key B next state number operation key C next state number operation key D next state number extension state number
U25604-J-Z745-1-7600
October 2004
107
States
Configuration Data
The Enhanced Amount Entry (R) state entries are defined as follows: State type Entry number: 1 Valid range: Description: R This state ID identifies this state table as an Enhanced Amount Entry state table.
Screen number Entry number: 2 Valid range: Description: 000-999 This is the number of the screen display that prompts the consumer to enter an amount.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The number of the state to which the terminal proceeds if the consumer fails to enter the amount within the specified time limit. Enter 255 if the time-out function is not required.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 This is the number of the state to which the terminal proceeds if the consumer presses the Cancel key.
108
October 2004
U25604-J-Z745-1-7600
Configuration Data Operation key B next state number Entry number: 6 Valid range: Description: 000-254, 256-999
States
The state number to which the terminal proceeds if the customer presses the B operation key. Value "255" deactivates the B operation key during this state.
Operation key C next state number Entry number: 7 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the C operation key. Value "255" deactivates the C operation key during this state.
Operation key D next state number Entry number: 8 Valid range: Description: 000-254, 256-999 The state number to which the terminal proceeds if the customer presses the D operation key. Value "255" deactivates the D operation key during this state.
Normally one operation key is used to indicate whether the amount entry is correct and another is used to indicate whether it is incorrect. The other operation keys are inactive. Extension State number Entry number: 9 Valid range: Description: 000-254; 256-999 State number of the extension state.
U25604-J-Z745-1-7600
October 2004
109
States
Configuration Data
Extension to State (R)

This state is the Extension state for the Enhanced Amount Entry state (R).
Entry 1 2 3 4 5-9
Definition state type document amount buffer display amount screen number start CAV command reserved
The Extension State entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as the Extension state to the Enhanced Amount Entry state table.
Document amount buffer Entry number: 2 Valid range: Description: 000-002 This field determines which buffer the amount entered will be stored in: 000 - Amount Buffer 001 - General Purpose buffer B 002 - General Purpose buffer C
110
October 2004
U25604-J-Z745-1-7600
Configuration Data Display amount screen number Entry number: 3 Valid range: Description: 000-999
States
Overlay screen number that sets the screen cursor position. This screen optionally defines the initial display format prior consumer amount entry. The cursor should be set on the lefthand side of the echo field on the screen. This is space filled until the required start position for the currency character is reached. Default echo field for eight digits: bbbbb$ 0.00 (where b = space) Default echo field for twelve digits: bbbbbbbbb$ 0.00 (where b = space)
Start CAV command Entry number: 4 Valid range: Description: 000-001 This field determines whether to start CAV processing or not if a document is available. ProCash/NDC or ProConsult/NDC only supports value 000. If a non-zero value is downloaded, the cancel next state is taken.
U25604-J-Z745-1-7600
October 2004
111
States
Configuration Data
Language Code Switch State (S)

In this state the flow of a transaction is switched depending on whether a language code is present in the card data or not. You can use this state to automatically select the language to be used from the code on the card, or to allow manual selection for cards which either have no language code, or an invalid language code. This state is subject to the same restrictions as the language select state. See section Language Select from Card State (V) for details.
Table 27: Language Code Switch state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type no language code, next state no. language code = 0, next state language code = 1, next state language code = 2, next state language code = 3, next state language code = 4, next state language code = 5, next state extension state number
112
October 2004
U25604-J-Z745-1-7600
Configuration Data The Language Code Switch state entries are defined as follows: State type Entry number: 1 Valid range: Description: S
States
This state ID identifies this state table as a Language Code Switch state table.
No Language Code, Next State No. Entry number: 2 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the language code is illegal or cannot be read.
Language Code = 0, next state Entry number: 3 Valid range: Description: 000-254, 256-999 State number the terminal goes to, if the language code is 0.
U25604-J-Z745-1-7600
October 2004
113
States Language Code = 4, next state Entry number: 7 Valid range: Description: 000-254, 256-999
Configuration Data
State number the terminal goes to, if the language code is 4.
Extension State number Entry number: 9 Valid range: Description: 000-999 State number of the extension state containing next states for language code 6-9. A value of 255 means that there is no extension state, and language code 6-9 cause the no language code next state exit to be taken.
Extension to State (S)

This state is the Extension state for the Language Code Switch state (S).
Entry 1 2 3 4 5 6 7 8 9
Definition state type language code = 6, next state language code = 7, next state language code = 8, next state language code = 9, next state reserved reserved reserved reserved
114
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
The Extension state entries of the Language Code Switch state are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as the Extension state to the Language Code Switch state.
Language Code = 9, next state Entry number: 5 Valid range: Description: Reserved Entry number: 6-9 Valid range: Description: 000 Must be 000. 000-254, 256-999 State number the terminal goes to, if the language code is 9.
U25604-J-Z745-1-7600
October 2004
115
States
Configuration Data
Card Read - PIN Entry Initiation State (T)

You can use this state instead of the Card Read state (A), if you want to initiate PIN entry by the consumer at the same time as the terminal reads the card. This state performs the same functions as the card read state. This state also enables the keyboard for PIN entry while the card is being read, and displays a screen prompting the customer to enter the PIN. One difference between this state and the Card Read state is that in this state the card is always returned according to the instruction in the Transaction Reply command message. See also section Card Read State (A) on page 59.
Table 29: Card Read - PIN Entry Initiation state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number good read next state number error (misread) screen number read condition 1 read condition 2 read condition 3 reserved extension state number
The Card Read - PIN Entry Initiation (T) state entries are defined as follows: State type Entry number: 1 Valid range: Description: T This state ID identifies this state table as a Card Read -PIN Entry Initiation state table with a parallel card read.
116
October 2004
U25604-J-Z745-1-7600
States
This is the number of the screen display which prompts the customer to insert a card. This screen is displayed while the terminal is awaiting card entry. This screen will be displayed on the screen.
Good read next state number Entry number: 3 Valid range: Description: 000-254, 256-999 The state number the terminal enters after the customers card is read properly: Following a good read of the card if FITs are not used. (Table Entry 3 in Extension State = 000), or if the FIT number on the card matches a FIT number in the FIT table. Normally the next state is a PIN entry state type. Error (misread) screen number Entry number: 4 Valid range: Description: 010-800 This is the number of the screen displayed, if the card is not read properly. Normally, this screen will prompt the customer to check that the card is inserted correctly and to reinsert the card.
Read condition 1 Entry number: 5 Valid range: Description: 001-015 This is one of the three entries (used with entry no. 6 and 7) that tell the terminal which card track(s) must be read. This is the first read condition. If this condition cannot be met, read condition 2 is used next. Refer to table Card read state entries for the definition of the card read conditions.
U25604-J-Z745-1-7600
October 2004
117
States Read condition 2 Entry number: 6 Valid range: Description: 001-015
Configuration Data
This is one of the three entries (used with entry numbers 5 and 7) that tell the terminal which card track(s) must be read. This is the second read condition used. This one is used if read condition 1 cannot be done. If read condition 2 cannot be met, read condition 3 is used. Refer to table Card read state entries for the definition of the card read conditions.
Read condition 3 Entry number: 7 Valid range: Description: 001-015 This is one of the three entries (used with entry numbers 5 and 6) that tell the terminal which card track(s) must be read. If neither read condition 1 or read condition 2 can be met, this read condition is used. Refer to table Card read state entries for the definition of the card read conditions.
Card return flag Entry number: 8 Valid range: Description: 000-001 This field is not used. The early card eject feature is not supported by this state. Card is always returned as specified be the Transaction Replay command message.
Extension State number Entry number: 9 Valid range: Description: 000-254, 256-999 State number of the extension state containing information for parallel PIN entry.
118
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Extension to State (T)

This state is the Extension state to the card read state (T).
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number no fit match next state number clear key mask (not supported) accept key mask (not supported) reserved, must be 000 reserved, must be 000 reserved, must be 000 reserved, must be 000
The card read extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as the extension state to the card read state (T).
Screen number Entry number: 2 Valid range: Description: 010-999 Display screen that prompts cardholder to enter PIN. This screen is displayed on card entry. The identified screen must leave the screen cursor positioned at the beginning of the PIN entry display area. An X is displayed for each key pressed. track 1 name cannot be displayed at this time as card has not been read.
U25604-J-Z745-1-7600
October 2004
119
States No FIT match Next state number Entry number: 3 Valid range: Description: 000-254, 256-999
Configuration Data
State number terminal goes to if the financial institution number on the card does not match any FIT. If FITs are not used this entry must be 000.
Language Select From Card State (V)

In this state you can set one of state tables to display screens in different languages within the same transaction. This is determined by one character (byte) on the cardholders card. This code is located using the Language Code Index parameter (PLNDX) in the FIT. See chapter Security Features for more details. You can use up to six screen groups in this state, and you specify which language is to be used in each group. You also specify in table entry 9 how many screens each group will contain.
Table 31: Language Select From Card state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type next state number language code for group 1 language code for group 2 language code for group 3 language code for group 4 language code for group 5 language code for group 6 screen group size (range 000-400)
120
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
The Language Select From Card (V) state entries are defined as follows: State type Entry number: 1 Valid range: Description: V This state ID identifies this state table as a Language Select From Card state table.
Next state number Entry number: 2 Valid range: Description: 0-9 State number terminal goes to after selecting the screen group.
Language Code Entry number: 3 Valid range: Description: 0-9 Decimal number in range 0-9 identifying code for screen group 1.
U25604-J-Z745-1-7600
October 2004
121
States Language Code Entry number: 6 Valid range: Description: 0-9
Configuration Data
Decimal number in range 0-9 identifying code for screen group 4.
Code Entry number: 8 Valid range: Description: 0-9 Decimal number in range 0-9 identifying code for screen group 6.
Screen Group Size Entry number: 9 Valid range: Description: 000-400 State number of the extension state containing information for parallel PIN entry.
122
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
FDK Switch State (W)

Data is placed in the FDK buffer during the FDK Selection state or the FDK Information Entry state. This data is read by the FDK Switch state in order to identify which next state the terminal should go to.
Table 32: FDK Switch state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type FDK A next state no. FDK B next state no. FDK C next state no. FDK D next state no. FDK F next state no. FDK G next state no. FDK H next state no. FDK I next state no.
The FDK Switch (W) state entries are defined as follows: State type Entry number: 1 Valid range: Description: W This state ID identifies this state table as a FDK Switch state table.
FDK A Next state No. Entry number: 2 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
U25604-J-Z745-1-7600
October 2004
123
States FDK B Next state No. Entry number: 3 Valid range: Description: 000-254, 256-999
Configuration Data
State number terminal goes to depending on key code stored in FDK buffer.
FDK C Next state No. Entry number: 4 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
FDK D Next state No. Entry number: 5 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
FDK F Next state No. Entry number: 6 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
FDK G Next state No. Entry number: 7 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
124
October 2004
U25604-J-Z745-1-7600
Configuration Data FDK H Next state No. Entry number: 8 Valid range: Description: 000-254, 256-999
States
State number terminal goes to depending on key code stored in FDK buffer.
FDK I Next state No. Entry number: 9 Valid range: Description: 000-254, 256-999 State number terminal goes to depending on key code stored in FDK buffer.
U25604-J-Z745-1-7600
October 2004
125
States
Configuration Data
FDK Information Entry State (X)

When the cardholder selects an FDK, this state places the corresponding value in the general purpose buffer or amount buffer that you have specified in table entry 7. Table entries 2-9 in the extension to this state contain values relating to the FDKs. You can use this function, for example, where a screen offers a selection of fixed amounts that the cardholder can select by pressing a particular FDK. This state translates the FDK selected by the cardholder into a value that is placed in the specified buffer. The FDK key code is stored in the FDK buffer for use by an FDK Switch state.
Table 33: FDK Information Entry state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number. cancel next state number FDK next state number extension state number buffer ID FDKs active mask reserved
The FDK Information Entry (X) state entries are defined as follows: State type Entry number: 1 Valid range: Description: X This state ID identifies this state table as the FDK Information Entry state.
126
October 2004
U25604-J-Z745-1-7600
States
Display screen that prompts key selection by the consumer.
Time-out Next state number Entry number: 3 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the consumer fails to respond to the message on screen within the permitted time limit. Enter 255 if the time-out function is not required.
Cancel Next state number Entry number: 4 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the cancel key is pressed.
FDK Next state Entry number: 5 Valid range: Description: 000-254, 256-999 State number the terminal goes to if an FDK is pressed.
Extension State Number Entry number: 6 Valid range: Description: 000-254, 256-999 State number of the extension state containing assigned values for the 8 FDKs.
U25604-J-Z745-1-7600
October 2004
127
States Buffer ID Entry number: 7 Valid range: Description: 010-039
Configuration Data
Identifies which buffer is to be edited and the number of zeros to add to the values specified in the extension state. 01X = general purpose buffer B 02X = general purpose buffer C 03X = amount buffer X - specifies the number of zeros in the range 0-9.
If Amount buffer is used, the amount buffer will contain 8 or 12 digits, depending on the option selected. If this state is followed by an amount check state the amount entered is assumed to be a whole amount. FDK Active Mask Entry number: 8 Valid range: Description: 000-255 Specifies the FDKs that are active during this state. Each bit relates to an FDK. Bit 0 relates to FDK A, bit 7 relates to FDK I. If a bit is 1 the relative FDK is active. If a bit is 0 the relative FDK is inactive. The eight bits the binary equivalent of an FDK active mask. For example in the following mask: b7 0 b6 1 b5 0 b4 1 b3 1 b2 1 b1 0 b0 1
the three decimal characters in table entry 8 are 093 and the active FDKs are A, C, D, F and H. Reserved Entry number: 9 Valid range: Description: 000 Must be 000.
128
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Extension to State (X)

This state is the Extension state to the FDK Information Entry state (X).
Entry 1 2 3 4 5 6 7 8 9
Definition state type value stored if FDK A is pressed value stored if FDK B is pressed value stored if FDK C is pressed value stored if FDK D is pressed value stored if FDK F is pressed value stored if FDK G is pressed value stored if FDK H is pressed value stored if FDK I is pressed
The Extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as the Extension state to the FDK Information Entry state.
Value stored if FDK A is pressed Entry number: 2 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
U25604-J-Z745-1-7600
October 2004
129
States Value stored if FDK B is pressed Entry number: 3 Valid range: Description: 000-999
Configuration Data
Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
Value stored if FDK C is pressed Entry number: 4 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
Value stored if FDK D is pressed Entry number: 5 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
Value stored if FDK F is pressed Entry number: 6 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDk Information Entry state (table entry 7) if the specified FDK is pressed.
Value stored if FDK G is pressed Entry number: 7 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
130
October 2004
U25604-J-Z745-1-7600
Configuration Data Value stored if FDK H is pressed Entry number: 8 Valid range: Description: 000-999
States
Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
Value stored if FDK I is pressed Entry number: 9 Valid range: Description: 000-999 Contains a value stored in the buffer specified in the associated FDK Information Entry state (table entry 7) if the specified FDK is pressed.
U25604-J-Z745-1-7600
October 2004
131
States
Configuration Data
Eight FDK Selection State (Y)

This state reads the FDK selected by the cardholder, stores the key code in an FDK buffer for use by an FDK switch state, and updates the operation code buffer. If you do not specify an extension state in table entry 6, the key code of the FDK selected by the cardholder is stored directly in the operation code buffer. If you do specify an extension state, the key code is translated into three pseudo key codes, which are then stored in the operation code buffer. You can specify a second extension state in table entry 9 to identify the screen bases for multi-language screen displays. If you do not specify this extension state, then multi-language is not used.
Table 35: Eight FDK Selection state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen number time-out next state number cancel next state number FDK next state number extension state number buffer positions FDKs active mask multi language extension state number
The Eight FDK Selection state (Y) state entries are defined as follows: State type Entry number: 1 Valid range: Description: Y The state type entry identifies this state table as the Eight FDK Selection state table.
132
October 2004
U25604-J-Z745-1-7600
States
Display screen which prompts key selection by the cardholder.
Time-out next state number Entry number: 3 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the cardholder does not respond to the message on screen within the specified time limit. Enter 255 if the time-out function is not required.
Cancel next state number Entry number: 4 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the cardholder presses the cancel key.
FDK next state number Entry number: 5 Valid range: Description: 000-254, 256-999 State number the terminal goes to if the cardholder presses an FDK.
Extension state number Entry number: 6 Valid range: Description: 000-254, 256-999 State number of extension state containing assigned operation codes for the 8 FDKs. If there is no extension state enter 255.
U25604-J-Z745-1-7600
October 2004
133
States Buffer positions Entry number: 7 Valid range: Description: 000-777
Configuration Data
no extension state: This defines the operation code buffer position to be edited by a value in the range 000 to 007. extension state: This specifies three bytes of the operation code buffer to be set to the values specified in the extension state. Three numeric values, each in the range 0 to 7, are specified to define three positions in the 8 byte operation code buffer to be edited. These three values must be ordered to correspond with the edit characters in the extension state. If no buffer positions or less than three buffer positions are to be edited, this is specified in the extension state.
FDKs active Mask Entry number: 8 Valid range: Description: 000-255 Specifies the FDKs that are active during this state. Each bit relates to an FDK. Bit 0 relates to FDK A, bit 7 relates to FDK I. If a bit is 1 the relative FDK is active. If a bit is 0 the relative FDK is inactive.
The eight bits represent the binary equivalent of an FDK active mask. For example in the following mask, the three decimal characters in the table entry are 183 and the active FDK`s are A, B, C, F, G, and I. BIT mask: b7 b6 1 0
b5 1
b4 1
b3 0
b2 1
b1 1
b0 1
Multi language Extension state number Entry number: 9 Valid range: Description: 000-254, 256-999 If the state selects the multi language screen base, this contains the extension state number. If there is no extension state, enter 000 or 255.
134
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Extension to State (Y)

This state is the Extension state to the Eight FDK Selection state (Y).
Entry 1 2 3 4 5 6 7 8 9
Definition state type operation code stored if FDK A pressed operation code stored if FDK B pressed operation code stored if FDK C pressed operation code stored if FDK D pressed operation code stored if FDK F pressed operation code stored if FDK G pressed operation code stored if FDK H pressed operation code stored if FDK I pressed
The Extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z Identifies this state table as the Extension state for the Eight FDK Selection state table.
U25604-J-Z745-1-7600
October 2004
135
States Operation Code stored if FDK pressed Entry number: 2-9 Valid range: Description: A - I, @ or 1 - 9, 0
Configuration Data
This table entry contains the operation code characters to be written to the operation code buffer if the specified FDK is pressed. Three characters are specified for each code, which must be in the range A - I. They are written in order to the three positions specified in the Eight FDK Selection state table (entry 7). Enter @ if no character is to be written to a specified position in the buffer (fields are unchanged).
The values 1 to 9 and 0 represent the characters A - I, and @.
Multi Language Extension to State (Y)

This state is the Multi Language Extension state to the Eight FDK Selection state (Y).
Entry 1 2 3 4 5 6 7 8 9
Definition state type screen language offset if FDK A is pressed screen language offset if FDK B is pressed screen language offset if FDK C is pressed screen language offset if FDK D is pressed screen language offset if FDK F is pressed screen language offset if FDK G is pressed screen language offset if FDK H is pressed screen language offset if FDK I is pressed
136
October 2004
U25604-J-Z745-1-7600
Configuration Data The Multi Language Extension state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z
States
Identifies this state table as the Multi Language Extension state for the Eight FDK Selection state table.
Screen language offset if FDK pressed Entry number: 2-9 Valid range: Description: 000-999 Each table entry contains the screen number of the first screen for each language group. The initial offset is 000, and all unused fields should contain this value.
U25604-J-Z745-1-7600
October 2004
137
States
Configuration Data
Audio Control State (i)

The Audio Control State allows the consumer to set the volume for the voice message that will be played for the duration of the current transaction. Furthermore the consumer can switch between the audio channels of the sound card. If the terminal has a sound card installed, the left the two channels (left and right channel) can be connected to a loudspeaker and the right channel can be connected to a headphone jack (if physically installed). The state table sets which audio channels are in use on entry to this state, and whether the cardholder will be given the option to adjust the volume. If the cardholder is to be given the option, then a message prompting the cardholder to adjust the volume is played repeatedly. The message is not played if the option is not offered. The cardholder may press:
q
FDKs to increase or decrease the volume This functionality can be disabled by setting entry 7 in the state table. If you map the FDKs to the numeric keyboard, the cardholder can adjust the volume by pressing numeric keys instead of the FDKs ENTER to set the volume at its current level. The state takes the Function Complete Next State exit CANCEL to return the volume to its default level. The state takes the Function Complete Next State exit.
If the cardholder does not press any keys within the time specified by Timer 00, then this state invokes the Time Out State. Make sure that the screen associated with the Time Out State is helpful to cardholders with visual difficulties. For example, you can map FDKs to the PIN pad and play an appropriate message. The Audio Control State's prompt screen must not contain an audio message. The volume returns to its default level on exit from the Close State.
See Table 38 on the following page for state table entry definitions:
138
October 2004
U25604-J-Z745-1-7600
Configuration Data
Table 38: Audio Control state entries
States
Entry 1 2 3 4 5 6 7 8 9
Definition state type Prompt screen Timeout next state Function complete next state Increase Volume FDK mask Decrease Volume FDK mask Audio control Audio message Reserved
The Audio Control (i) state entries are defined as follows: State type Entry number: 1 Valid range: Description: i This state ID identifies this state table as an Audio Control state.
Prompt screen Entry number: 2 Valid range: Description: 000-999 Prompts user to adjust volume. This screen is only displayed if table entry 7 indicates that the volume is to be adjusted.
Timeout next state Entry number: 3 Valid range: Description: 000-254; 256-999 State number to which the terminal proceeds if the cardholder has responded within the time specified by Timer 00. Value 255 disables the time-out feature.
U25604-J-Z745-1-7600
October 2004
139
States Function complete next state Entry number: 4 Valid range: Description: 000-254; 256-999
Configuration Data
State number to which the terminal proceeds if: - the cardholder selects Cancel or Enter - table entry 7 selects a channel but disables volume adjustment - there is no audio file present on the terminal
Increase Volume FDK mask Entry number: 5 Valid range: Description: 000-255 Specifies which FDKs will increase the volume in this state. Bit 0 relates to FDK A, bit 1 to FDK B etc. If a bit is 1 then the FDK referred to is active; otherwise it is inactive. The FDKs are not enabled unless the least significant bit of table entry 7 is 1. A value of 000 disables this entry and is discouraged.
Decrease Volume FDK mask Entry number: 6 Valid range: Description: 000-255 Specifies which FDKs will decrease the volume in this state. Bit 0 relates to FDK A, bit 1 to FDK B etc. If a bit is 1 then the FDK referred to is active; otherwise it is inactive. The FDKs are not enabled unless the least significant bit of table entry 7 is 1. A value of 000 disables this entry and is discouraged. Where the same FDK is specified as having both Increase Volume and Decrease Volume functions, Decrease Volume takes precedence.
140
October 2004
U25604-J-Z745-1-7600
Configuration Data Audio control Entry number: 7 Valid range: Description: 000-015 This entry is bitmapped: Bit Definition 0 1 2 3 0 - volume adjust off 1 - volume adjust on 0 - disables effect of bits 2 and 3 1 - enables effect of bits 2 and 3 0 - disables loudspeaker (left channel) 1 - enables loudspeaker (left channel) 0 - disables audio jack (right channel) 1 - enables audio jack (right channel)
States
EXAMPLE: For instance, a value of 007 enables volume adjustment and directs audio output to the speaker; 015 enables volume adjustment and enables both channels. A value of 003 is discouraged in this entry: this would turn both channels off but enable volume adjustment. If this entry does not instruct a change to the audio channel in use, the current audio channel(s) will remain in use. Audio message Entry number: 8 Valid range: Description: 000 or 999 Specifies which audio message will be played. Provided that table entry 7 indicates that the volume is to be adjusted, the message will be played repeatedly until the state is exited. If there is no audio file present on the terminal, it will take the Function Complete Next State exit.
U25604-J-Z745-1-7600
October 2004
141
States
Configuration Data
Hardware Fitness State (h)

The Hardware Fitness state is a special state designed by Wincor Nixdorf that can be used for specific purposes on Wincor Nixdorf terminals. This state allows to jump into another state flow depending on the actual hardware fitness of the devices defined in the state table. Also an extension state can be defined which allows additional decisions to jump to a defined next state. If multiple conditions apply, the priority is top down; i.e. state h entry 3 (reboot) has the highest priority over all values. The value of the last table entry of the extension state becomes active only if no previous condition was fullfilled. The general order is: reboot, device fatal, device warning.
Table 39: Hardware Fitness state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type no error next state next state if reboot requested (defined in CCERRMAP) next state if CDM fatal error next state if journal fatal error next state if receipt fatal error next state if deposit fatal error reserved for future use extension state number
The Hardware Fitness (h) state entries are defined as follows: State type Entry number: 1 Valid range: Description: h This state ID identifies this state table as a Hardware Fitness state.
142
October 2004
U25604-J-Z745-1-7600
Configuration Data No error next state Entry number: 2 Valid range: Description: 000-999
States
The number of the state to which the terminal proceeds if none of the subsequent hardware conditions apply.
Next state if reboot requested Entry number: 3 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if a system reboot has been requested. This reboot request can be issued by errors of classes which have set the reboot flag. This can be used to prevent offering other functions to the customer after serious malfunctions requiring a system reboot have occurred.
Next state if Cash Dispenser fatal error Entry number: 4 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if the cash dispenser is fatal.
Next state if Journal fatal error Entry number: 5 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if the journal printer is fatal.
Next state if Receipt fatal error Entry number: 6 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if the receipt printer is fatal.
U25604-J-Z745-1-7600
October 2004
143
States Next state if Deposit fatal error Entry number: 7 Valid range: Description: 000-999
Configuration Data
The number of the state to which the terminal proceeds if the deposit module is fatal.
Reserved for future use Entry number: 8 Valid range: Description: 000 or 255 Entry 8 is reserved and must be 000 or 255.
Extension state number Entry number: 9 Valid range: Description: 000-999 State number of the extension state (Z) containing additional device conditions.
144
October 2004
U25604-J-Z745-1-7600
Configuration Data
States
Extension to State (h)

The Extension state to the Hardware Fitness state contains additional conditions to go to the specified next state. Typically for NDC the Hardware Fitness Extension state is a Z state.
Table 40: Hardware Fitness Extension state entries
Entry 1 2 3 4 5 6 7 8 9
Definition state type denomination type next state if denomination not available next state if journal warning next state if receipt warning next state if deposit warning reserved for future use reserved for future use reserved for future use
The Hardware Fitness Extension (Z) state entries are defined as follows: State type Entry number: 1 Valid range: Description: Z This state ID identifies this state table as a Hardware Fitness Extension state.
U25604-J-Z745-1-7600
October 2004
145
States Denomination Type Entry number: 2 Valid range: Description: 000-044 The data field is divided in three digits:
Configuration Data
First digit: Reserved, always zero. Second digit: Specifies the denomination type of cash cassettes which should be verified as out of notes (fatal condition). The entry range 1-4 indicates denomination Type 1 to 4.
Third digit: Specifies which cassette position will be checked for low notes (warning condition). The entry range 1-4 indicates the denomination Type 1 to 4. Next state if Denomination not available Entry number: 3 Valid range: Description: 000-999 The number of state to which the terminal proceeds if the Denomination is not available.
Next state if Journal warning Entry number: 4 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if the journal printer has a warning status.
Next state if Receipt warning Entry number: 5 Valid range: Description: 000-999 The number of the state to which the terminal proceeds if the receipt printer has a warning status.
146
October 2004
U25604-J-Z745-1-7600
Configuration Data Next state if Deposit warning Entry number: 6 Valid range: Description: 000-999
States
The number of the state to which the terminal proceeds if the deposit module has a warning status.
Reserved Entry number: 7-9 Valid range: Description: 000 or 255 Entries 6-9 are reserved and must be 000 or 255.
U25604-J-Z745-1-7600
October 2004
147
States
Configuration Data
Smart FIT Check State (k)

This state is only required when chip data is to be used in a FIT check. The Smart FIT Check state should be entered after the chip data a read from the smart card and stored in the magnetic track buffers of the application. The Smart FIT Check state then performs a FIT check on the contents of the three track buffers. It is possible to create more than one Smart FIT Check state to accomodate multiple FIT checks. This would allow different FIT checks to be performed on data from the same card.
Table 41: Smart FIT Check State
Entry 1 2 3 4 5 6 7 8 9
Definition state type reserved good read next state number error (misread) screen number read Condition 1 read Condition 2 read Condition 3 card return flag no FIT match next state
The Smart FIT Check (k) state entries are defined as follows: State type Entry number: 1 Valid range: Description: k This state ID identifies this state table as a Smart FIT Check state.
148
October 2004
U25604-J-Z745-1-7600
Configuration Data Reserved Entry number: 2 Valid range: Description: 0
States
Not used - set to 0. This is left blank to align the following table entries to the same positions as those in the Card Read State, allowing common FIT check procedures to be used.
Good read next state number Entry number: 3 Valid range: Description: 000-999 State number to which the terminal goes if the Financial Institution number on the card matches a Financial Institution number in the FIT.
Error (misread) screen number Entry number: 4 Valid range: Description: 000-999 If the read conditions are not satisfied due to a bad card or a mechanism error, the card is ejected and this screen is displayed.
Read condition 1 Entry number: 5 Valid range: Description: see description First of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7 Description Read track 3 Read track 2 Read track 1 Reserved
U25604-J-Z745-1-7600
October 2004
149
States Read condition 2 Entry number: 6 Valid range: Description: see description
Configuration Data
Second of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7 Description Read track 3 Read track 2 Read track 1 Reserved
Read condition 3 Entry number: 7 Valid range: Description: see description Third of three entries indicating which card track buffer(s) will be read. Bit 0 1 2 3-7 Card return flag Entry number: 8 Valid range: Description: 000-999 Tells the terminal when the card should be returned to the cardholder: 000 - eject the card immediately 001 - return the card as specified by a transaction reply message. Description Read track 3 Read track 2 Read track 1 Reserved
150
October 2004
U25604-J-Z745-1-7600
Configuration Data No FIT match next state number Entry number: 9 Valid range: Description: 000 or 999
States
This is the state is executed if the FIT check fails. It may be a close state or a return to another Chip exit state which places the chip data in the read buffers before calling a different Smart FIT Check state with different read conditions. If FITs are not used, this entry must be 000.
U25604-J-Z745-1-7600
October 2004
151
States
Configuration Data
Skip State step

The Skip state steps can be used to skip non supported states which can be just ignored through a good next state number definition.
Table 42: Skip state step
Step name DC_NEXT_1 DC_NEXT_2 DC_NEXT_3 DC_NEXT_4 DC_NEXT_5 DC_NEXT_6 DC_NEXT_7 DC_NEXT_8
Definition uses field 1 for good state next operation uses field 2 for good state next operation uses field 3 for good state next operation uses field 4 for good state next operation uses field 5 for good state next operation uses field 6 for good state next operation uses field 7 for good state next operation uses field 8 for good state next operation
152
October 2004
U25604-J-Z745-1-7600
Configuration Data
Screens
Screens
Screen data is also a type of configuration data. All screens are assigned to a decimal number between 000 and 999. Furthermore the NDC+ protocol is using reserved screen numbers like C00 through C06, Axx, Dxx, Exx, and so on that can be used for specific functions. Restrictively ProCash/NDC and ProConsult/NDC just can store the reserved screens in the registry if they are downloaded from host. The only reserved screens supported, are C00 - C06. For detailed descripton see section Reserved Screens on page 162. Normally, the screen number and following data are down-line loaded to the terminal using the Screens Table Load command message. Refer to section Screen Data Load on page 242 for details. However, new screens can be sent by the network in a Transaction Reply command message. Unused screens do not need to be down-line loaded. The terminal stores the screen data in the registry location ..\LYNXCI\SCREEN. Wincor Nixdorf terminals can display screens in the grid of 32 columns by 16 rows. See section Screen Design Worksheet on page 378.
Screen Control Characters

Nearly in all screens serveral control characters are included, like cursor positioning, set an overlay screen, clear screen, display Track 1 information, etc.. A global overview gives Table Screen control characters on page 154. ProCash/NDC and ProConsult/NDC support following major control functions:
q q q q q
Clears a screen Sets the screen cursor Delays then shows a character Shows inverse video characters Allows blinking
U25604-J-Z745-1-7600
October 2004
153
Screens Screen delimiters
Configuration Data
The field separator (FS) or group separator (GS) at the end of the message are screen delimiters. Each screen data field must be terminated by one of these two screen delimiters. Normally, FS separates each screen data field in a Screens Table Load command message. The end of the message terminates the last screen data field in a Screens Table Load command message.
Table 43: Screen control characters cross-reference
Control Code CR FF HT SI SO VT
ASCII HEX Equivalent 0D 0C 09 0F 0E 0B
EBCDIC HEX Equivalent 0D 0C 05 0F 0E 0B
Table 44: Screen control characters
Control Code CR FF HT
Description moves the cursor to the first position in the current row clears the screen and positions the cursor to position @,@ on the display grid causes the customers name, encoded on track 1 of the customers card, to be shown on the customer display, starting at the current customer display cursor position sets the cursor to the position specified by the two bytes following SI. the first byte is the row, and the second byte is the column. data shown on the screen remains unchanged. overlays the screen specified by the three bytes following SO. screen data can be nested or overlaid to five levels using the control character SO. shows an alternate character on the customer display. the alternate character is specified by the byte following VT
SI
SO
VT
154
October 2004
U25604-J-Z745-1-7600
Configuration Data CR control character
Screens
The CR control character moves the cursor to column @ in the following row. FF control character The FF control character clears the screen with the default foreground and background colors. The cursor is set to the top left hand corner (row @, column @) of the screen. Screen blinking will be switched off. HT control character The HT control character inserts the name from track 1 of the customers activator card into the screen data. The terminal displays the name starting at the current cursor position. SI control character The SI control sequence moves the cursor to a specified row and column. The format of the control sequence is as follows: SI 1A The terminal places the cursor at row 1, column A. Any of the 16 rows can be selected by using a row select character from @ through 3. Any of the 32 columns can be selected by using a column select character @ through ?. See also the grid graphic in section Screen Design Worksheet on page 378. VT control character The VT control sequence is used to display characters from secondary character set. ASCII codes in the range 20 - 7F hex, preceded by a VT character, forces displaying characters from the Customer Graphic 1 character set. The format of the control sequence is as follows:
VT C
U25604-J-Z745-1-7600
October 2004
155
Screens SO control character
Configuration Data
The SO control sequence inserts a specified screen into the current screen. The format of the control sequence is as follows: SO nnn The network uses the control character SO to call another screen. This technique is called nesting. Nesting is accomplished by placing control character SO followed by a three-digit screen number within a current screen. The maximum number of nesting levels is five. When using nested screens, the maximum number of characters per screen is as follows:
q q
screen 1: 600 characters screens 2 through 6: 310 characters each
The network can use an SO control sequence along with an ESC [z control sequence to show animated screens. In a typical animation sequence, the last screen calls the first screen again. To prevent infinite nesting when using animation, the ESC [z control sequence must be the last instruction in each animation screen.
156
October 2004
U25604-J-Z745-1-7600
Configuration Data
Table 45: Screen escape sequences cross-reference
Screens
Escape Sequence ESC P ESC [ ESC ( ESC )
ASCII HEX Equivalent 1B 50 1B 5B 1B 28 1B 29
EBCDIC HEX Equivalent 27 D7 27 63 27 4D 27 5D
Table 46: Screen escape sequences
Escape Parameters Description Sequence ESC [...m kk;ff;bb Activates blinking characters and sets foreground and background color. Example: kk = 00 - blinking off; 10 - blinking on (max. 100 ESC characters per screen) [10;67;71m ff = foreground color bb = background color ESC [...z ttt Display idle sequence. Displays the screen in the specified time ttt. ESC ( c Select primary character set; (c = font type) ESC ) c Select secondary character set; (c = font type) ESC P0... nnn Voice control; Defines a voice message number ;0ESC\ that is played when the screen is displayed. Voice files have to be stored in the path locations defined via parameter AUDIOx_PATH for each language group (x = language group) in section ..\LYNXCI\SCREEN. ESC P1.. nn Logo control; displays number nn logo. (e.g. ESC\ ESCP199ESC\) ESC P2... nnn Picture control; diplays number nnn picture. (e.g. ESC\ ESCP2999ESC\) ESC PE... path Picture control; diplays a graphic specified via ESC\ path. (e.g. ESCPEC:\PICT\PICTURE.PCXESC\) The backslash character (\) is stored in hexadecimal format (\5c) in the registry. ESC is stored as \1b. Example entry for ESCPE: CONTENTS = \1bPEC:\5cPICT\5cPICTURE.PCX\1b\5c
U25604-J-Z745-1-7600
October 2004
157
Screens
Configuration Data
Displaying Graphics as Icons

ProCash/NDC and ProConsult/NDC can display *.pcx, or *.bmp files which are smaller than the whole screen as an icon. Therefore a cursor positioning is required to fit the icon in the right place. You can add text above or below the icon without modifying icon data. Also, text can share a row with an icon. However, if text and the icon share a row, one cannot overlap on the other, and one space must separate the text and the icon. Their combined lengths cannot extend beyond the end of the row. Non supported graphic extensions, for example specified in a downloaded screen using the ESCPE control sequence can be mapped to another file extension supported by ProCash/NDC via parameter PICTURE_EXT_XXX. See ProCash/NDC ProConsult/NDC Installation manual section Graphic and Video file extension mapping for detailed descriptions how to map graphic and video files.
Full Screen graphics

Wincor Nixdorf terminals support full screen graphics as *.pcx, or *.bmp formats. With these graphics it is possible to show animations and text together instead of using icons and/or text using WIN-NT font files. Additionally the text from the font files can be overlaid (transparent mode) onto full screen graphics. The possibilities are endless. Mixtures of all kinds of graphics in one customization image are possible, PCXs, BMPs with/without overlaid text. Display resolutions ProCash/NDC and ProConsult/NDC support following display resolutions and color depths: Mode VGA SVGA SVGA SVGA [1] Resolution 640x480 640x480 800x600 1024x768 color depths [1] 16 256, 65535 (16 bit) 256, 65535 (16 bit) 256, 65535 (16 bit)
PCX graphics are supported in 16 or 256 colors only.
158
October 2004
U25604-J-Z745-1-7600
Configuration Data
Screens
Displaying MacroMedia Flash executables

ProCash/NDC and ProConsult/NDC are able to display Flash video animations. Flash files can be created via different utilities like MacroMedia Flash. A Flash animation has to be stored as an executable file like MyFlash.exe. Please refer to ProCash/NDC ProConsult/NDC Installation manual to get detailed information how to configure Flash animations in ProCash/NDC and ProConsult/NDC. Important Note: You have to install Internet Explorer 5.5 or higher to be able to display Flash files.
Displaying Video files

In addition to the graphics, ProCash/NDC and ProConsult/NDC are able to display AVI and MPG video files. They can be configured in the same way as the graphic files. The only difference is the file extension, which has to be *.avi, *.mpg or *.mpeg. If a video file is specified within the screen flow, an external program named ccMciPly.exe located in directory C:\PROTOPAS\BIN is called that performs function calls to the API of the MCI player. If you want to play video files it is necessary to check if the video file can be played with the current installed codec on the ATM. This can be easily tested if you double click the video file. After you have double clicked the file, the Microsoft MCI player should come up automatically to play the video. If you get an error or the MCI player doesnt come up, you have to install the correct Video Compression Codec. Some codecs will be installed together with the Internet Explorer or Media Player installation. The current version of the Video Compression Codecs can be viewed in the Multimedia dialog box in the Control Panel of Windows. IMPORTANT NOTE: Since version $MOD$ 020701 1009 of ccMciPly.exe, videos are running in the topmost window. That means, videos are always played in the foreground window. Other open windows behind (previously accessed via ALT-TAB) cannot be reached any more. The only chance to get access to other open windows is via key combination ALT+F4 on the alpha keyboard. ALT+F4 terminates the program ccMciPly.exe.
U25604-J-Z745-1-7600
October 2004
159
Screens
Configuration Data
Voice Control
If the terminal has installed a sound card and the path of the voice files are configured via AUDIOx_PATH (see ProCash/NDC ProConsult/NDC Installation manual for detailed definition of this parameter), the terminal attempts to play pre-recored messages in some states. Make sure that the pre-recorded message is brief enough to play completely before the state is timed out. The terminal attempts to play messages at following times: Auto Voice Feature The following voice messages are spoken if the Auto Voice Feature option 02 is set to 001 in the Enhanced Configuration Parameters Load message. See also Table 47 for the message description.
q
PIN Entry (Message 7) The message starts during a PIN Entry state or Enhanced PIN Entry state when the card has been read and recognized. Transaction Request (Message 1) The message starts when a Transaction Request message is sent to the host. Card Taken (Message 8) The message starts as soon as a card is taken in the Close state. If the card has already been taken, the message starts on entry to the Close state.
Table 47: Default Voice Message files
Audio (*.WAV) file 1.WAV 7.WAV 8.WAV
Message Number 1 7 8
Message your transaction is being processed please enter your personal identification number thank you for using this atm
NOTE: The three WAVE message files are recorded as male voice
160
October 2004
U25604-J-Z745-1-7600
Configuration Data Audible Echo on Keyboard
Screens
ProCash/NDC and ProConsult/NDC also support Audio Echo on Keyboard if Option 31 is enabled in the Enhanced Configuration Parameters Load message (see Table 48). Table 48 lists the wave files used if Audio Echo on Keyboard is enabled:
Table 48: Default WAVE files for Audio Echo on Keyboard
Audio (*.WAV) file ZERO.WAV ONE.WAV TWO.WAV THREE.WAV FOUR.WAV FIVE.WAV SIX.WAV SEVEN.WAV EIGHT.WAV NINE.WAV
Phrase zero one two three four five six seven eight nine
NOTE: The WAVE files are recorded as female voice
U25604-J-Z745-1-7600
October 2004
161
Screens
Configuration Data
Reserved Screens
Wincor Nixdorf terminals contain reserved screens C00 through C06 stored in the registry location ..\LYNXCI\SCREEN. These screens contain default data which is displayed when no reserved screen is downloaded with its own data.
Table 49: Downloaded reserved screens supported by Wincor Nixdorf terminals
Screen No. C00
Function More time screen; This screen prompts the customer who has failed to respond to a request for keyboard input within the specified keyboard response time. Offline screen; This screen appears on the customer display when the terminal is offline. The screens characters default to offline at terminal power up or reset. Out of Service screen; This screen appears on the customer display when the terminal is in out-of-service mode. The screens characters default to out-of-service at terminal power-up or reset. Supply screen. This screen is displayed while the terminal is in supervisor mode. Card capture screen; This screen is displayed when the terminal captures a card as a result of a card reader failure Cardholder tampering screen; This screen is displayed when cardholder tampering is suspected and the terminal enters suspend mode. Temporarily Out of Service screen
C01
C02
C03 C04 C05
C06
162
October 2004
U25604-J-Z745-1-7600
Configuration Data General use of default reserved C screens
Screens
In addition to Diebold the reserved screens C00-C06 can be downloaded. If one of those screens is not downloaded, the following defaults are used: Default screen C00 C01 C02 C03 C04 C05 C06 Downloaded screen 000 001 002 003 none C02 / 002 C02 / 002 If one or more of the reserved screens are not downloaded by the host you can create your own reserved screens in PARAC configuration file CUSTOM.PPF. In Registry section ..\LYNXCI\SCREEN the new subsections of your new defined C screens will be created and updated if you start the PARAC run. See ProCash/NDC ProConsult/NDC Installation manual for details. Screen C00 Screen C00 prompts customers who fail to respond within a specified time interval. Screen C00 must be defined and must conform to the following operation key A and B requirements:
q
if operation key A is pressed, the terminal returns to the original state in which the time-out occurred. The customer presses this key to request more time. if operation key B is pressed, the terminal returns to the time-out next state entry of the original state in which the time-out occurred. Normally, this timeout next state is a close state.
Screen C01 Screen C01 is displayed when the terminal is in offline mode.
U25604-J-Z745-1-7600
October 2004
163
Screens Screen C02
Configuration Data
Screen 002 is displayed when the terminal is in out-of-service mode. Screen C03 Screen C03 is the supply screen. This screen is displayed when the terminal is in supervisor mode. Screen C04 Screen C04 is displayed when the terminal captures the card in case of a card reader failure. When this occurs, the next state is executed. This screen is displayed as long as in the value of Timer 2 specified. Screen C05 Screen C05 is displayed when cardholder tampering is suspected and the terminal enters Suspend mode. The Suspend mode condition as an error Severity 3 can be configured in CCERRMAP. See ProCash/NDC ProConsult/NDC Installation manual for details. Screen C06 Screen C06 is displayed when the terminal is temporarily in out of service mode. This screen is displayed under following conditions:
q q
When specified in a go out of service comand from host On exit supervisor mode to out of service if supervisor mode was entered from in service and the auto return to previous mode is not set. If supply mode is entered from out of service while displaying screen C06.
164
October 2004
U25604-J-Z745-1-7600
Configuration Data
Screens
Language Selection
You can create multi language customer screens to be displayed as requested from one set of state tables. This can be defined via group definitions for each language, in which the equivalent screen for all languages has the same relative position within the group. Make sure that all the screens for which a choice of languages can be made are in the group. Note that nested screens must have absolute positions. The first group must start at 000, and contain thos screens fro which language selection is not possible. That is, screens displayed from the Card Read state and Language Select from Card state. Screens normally associated with not in service conditions, such out of service, supervisor or offline, should also be in this group if the Cxx default screens are used. You do not need to cahnge the state tables, but you must include an Eight FDK Selection Function state, or Language Select from Card state, in order to select the language.
EXAMPLE: If four languages are required, the screen group bases could be: Language A - 000 Language B - 100 Language C - 200 Language D - 300 If a screen 055 is displayed from a state table, the screen is downloaded as: 055 for Language A 155 for Language B 255 for Language C 355 for Language D
U25604-J-Z745-1-7600
October 2004
165
Miscellaneous Configuration Data
Configuration Data

Miscellaneous configuration data is down-line loaded via (Enhanced) Customisation Table Load command message from network to terminal. Refer to section Configuration Parameters Load on page 245 and to section Enhanced Configuration Parameters Load on page 249 for the message format. The (Enhanced) Customisation Table Load command message has three data fields:
q q q
terminal parameters logical unit number timer data
Each field is preceded by a field separator (FS). The following sections describe the contents of these data fields.
Terminal Parameters
The terminal parameters data fields are described in section Configuration Parameters Load on page 245 and section Enhanced Configuration Parameters Load on page 249.
Logical Unit Number (LUNO)

The second piece of information in the miscellaneous configuration data is called the Logical Unit No. (LUNO). The LUNO is a unique number that indicates which terminal has transmitted a message. If the key-entry person enters a machine number, the terminal places the terminal number at the end of the LUNO in the transaction request, solicited status, and unsolicited status messages (except the power failure unsolicited status message).
166
October 2004
U25604-J-Z745-1-7600
Configuration Data
Timer Data
The third piece of information in the miscellaneous configuration data is called timer data. Some timers must be down-line loaded by the network because they do not have default times. Other timers may be down-line loaded, but they do not have to be as they have default settings. The time-out intervals are specified as a number of 0.8 second segments (ticks). The number of ticks assigned to a timer can be 000 to 255. This gives each timer a time-out range of 0 to 204 seconds. Unless otherwise stated in the timer descriptions that follow, specifying a time-out interval of 000 causes the terminal to never take the time-out next state exit from a state. The data for each timer is down-line loaded in the sequence the timer number (2 bytes) then the number of 800-millisecond ticks (3 bytes). Timers are stored in registry location ..\LYNXCI\TIMER. The timer values are stored in seconds.
U25604-J-Z745-1-7600
October 2004
167

Table 50: Timer values
Configuration Data
Timer Default value in PPF Timer Default value in PPF number (seconds / ticks) number (seconds / ticks) 00 01 02 03 04 05 06 07 08 09 10 11 12-14 15 16-17 18 19 20 Timer 00 Timer 00 sets the keyboard response timeout interval. When a screen is displayed that prompts the customer to make a keyboard entry, the customer must respond within the timeout interval specified for timer 00. Otherwise, the terminal will exit its present state, display screen number 000, and start timer 01. 030 / 038 015 / 019 005 / 006 030 / 038 040 / 050 040 / 050 030 / 038 001 / 001 040 / 050 020 / 025 001 / 001 86 87 94 95 96 97 98 99 018 / 023 (not used) 030 / 038 (not used) 030 / 038 (not used) 030 / 038 000 / 000 010 / 013 (not used) 030 / 038 (not used) 030 / 038
168
October 2004
U25604-J-Z745-1-7600
Configuration Data Timer 01
Timer 01 sets the consumer response extension timeout interval. If the customer exceeds the timeout interval allowed for keyboard entry (timer 00), for deposit envelope insertion (timer 04, 08 or timer 20), or for securomatic insertion (timer 08), screen 000 is displayed. Screen 000 asks if the customer needs more time. Timer 01 is the timeout interval for the customers response to screen 000. The keyboard beeper sounds while this timer is active. If this timer expires for the keyboard, the terminal advances to timeout next state; if the timer expires for the deposit, the terminal sends a solicited status message to the network. Timer 02 Timer 02 sets the close state screen time-out interval. At the end of this interval, the terminal proceeds to the next state number specified in the close state. A timeout interval of 000 is not permitted for timer 02.
Timer 03 Timer 03 sets the communication message timeout interval. When the terminal is ready to transmit a Transaction Request message to the network, the terminal starts Timer 03. If the terminal does not receive a Transaction Reply command before Timer 03 expires, the terminal exits the transaction request state by going to the network response time-out next state number. Timer 04 Timer 04 sets the envelope insertion time-out interval for the depository. When a screen is displayed that prompts the customer to insert an envelope into the depository, the customer must respond within the time-out interval specified by timer 04; otherwise, the terminal exits its present state, displays screen 000 and starts timer 01. The keyboard beeper sounds while this timer is active. Timer 05 Timer 05 sets the withdrawal time-out interval for terminals with a withdrawal door. The maximum amount of time that the terminal waits for a customer to remove the cash is the sum of timers 05 and 07. After the cash has been counted and placed in the delivery mechanism, the terminal unlocks the delivery door and starts timer 05.
U25604-J-Z745-1-7600
October 2004
169

q
Configuration Data
If the customer fails to fully open the withdrawal door and clear the rear withdrawal area sensors before timer 05 expires (or to just fully open the door on terminals with a manual door), the terminal transmits the withdrawal door solicited status to the network indicating a fault and waits for a new Transaction Reply command message from the network. If the customer fully opens the withdrawal door and clears the rear withdrawal area sensors before timer 05 expires (or just fully opens the door on terminals with a manual door), the terminal proceeds to timer 07.
Timer 06 Timer 06 sets the communications offline timeout interval. This timer is started each time the terminal receives a poll or select sequence from the network. If the terminal has not been polled or selected within the interval specified for timer 06, the terminal proceeds to offline mode (out-of-service to customers) and displays screen 001.
A timeout interval of 000 is not permitted for timer 06.
Timer 07 Timer 07 sets the withdrawal door open timeout interval. This timer specifies the amount of time that the terminal waits after the withdrawal door is fully opened before going to the next specified state. On all terminals with a delivery door, this timer starts after the withdrawal door is fully opened and either the sensors are cleared or timer 05 expires. On all terminals without a delivery door, this timer starts after timer 10 expires.
Timer 08 Timer 08 sets the envelope insertion timeout interval for the night safe depository. When a screen is displayed prompting the insertion of a deposit, the customer has to respond within the timeout interval specified by timer 08. Otherwise, the terminal exits its present state, displays screen 000 and starts timer 01.
170
October 2004
U25604-J-Z745-1-7600
Configuration Data Timer 09
Timer 09 sets the customer timeout interval before a card capture attempt. If, during a close state, the card is presented to the customer and not removed within this time period, a card capture attempt is made. This timer starts after the terminal executes the card return function ID and at the beginning of the close state if the card was not returned at the card read state. Timers 02 and 09 start at the same time. When the card is removed, timer 09 stops. The default setting for timer 09 on power-up is 30 seconds (38 ticks).
Timer 10 Timer 10 sets the withdrawal timeout interval for terminals without a withdrawal door. Timer 10 sets the amount of time the beeper beeps while waiting for the customer to take the cash. After the terminal counts and places the cash in the withdrawal area, the terminal displays a Take Cash screen, starts timer 10, and activates the beeper. After timer 10 expires, the terminal stops the beeper and starts timer 07. Therefore, the total amount of time that the terminal waits for a customer to remove the cash is the sum of timers 10 and 07. A value of 000 in timer 10 will result in no beeping and zero time. The default setting for timer 10 on power-up is 006 ticks. Timer 11 (CSC450 with vandal shield only) Timer 11 sets the vandal shield delay time before closing. Timer 11 sets the amount of time the vandal shield delays before it begins to close. The vandal shield uses this timer if a value of 004 is in state entry 3 of the vandal shield state. Timer 11 defaults to 080 ticks on power-up.
U25604-J-Z745-1-7600
October 2004
171
Miscellaneous Configuration Data Timer 15
Configuration Data
Timer 15 is used with the card read T state (not used by Wincor Nixdorf terminals). Timer 18 Timer 18 sets the swipe card reader error screen timer (not used by ProCash/NDC and ProConsult/NDC application). Timer 20 Timer 20 sets the insertion timeout interval for the depository. If timer 20 is configured to a non-zero value, it is used instead of timer 04. Timer 20 allows seven seconds of silent time, after which the beeper starts at a slow rate for the remainder of the specified time. Timer 95 Timer 95 sets the statement retract timeout. This timer is used during the Close State processing. It determines when to retract a statement that has not been taken by the customer. The default value is 30 ticks and the timer is not used if you set a zero value. This timer is also used when Transaction Reply command S is sent in the transaction reply and the statement is laying in the collection tray of the statement printer. The timer will be started when this condition is detected. If the timer expires the statement is retracted and Transaction Reply command S commences. If the statement is taken before the timer expires, Transaction Reply command S commences without retract attempt. Timer 96 Timer 96 sets the statement present timeout. This timer is used only in the statement and continue function and is started regardless of whether or not a statement has been delivered. When the timer expires, the next state specified by the transaction reply command is entered. Timer value zero means no wait. Timer 99 Timer 99 specifies after what time the vandal guard close operation should be started when the consumer transaction has been finished.
172
October 2004
U25604-J-Z745-1-7600
Configuration Data
Local download feature

The local download feature is useful if you want to overload the downloaded customization image (CI) from host with local defined settings. With local downloads you can skip unsupported functions or overwrite non legal values in states or screens and it allows to enhance the host configuration with new functions locally. In addition to the download modifications you can also change local ATM settings (e.g. graphic file locations or printer settings).
Configure local download

Local download procedures can be called after following two situations:
q q
ATM has received Config ID (Set Config ID command) from host ATM has received Go in Service command from host
The local download process can be evaluated via two batch files. Depending on the existing file name the local download is called after the ATM has received the Config ID and/or a Go in Service command. The following table describes the filenames, location and in which situations the files are called: Filename dcCfgId.cmd dcInServ.cmd Directory C:\PROTOPAS\CONF C:\PROTOPAS\CONF Called when after Config ID received after Go in Service received
The contents of the files can be any command which is supported in a Windows command line window. Contents of dcCfgId.cmd or dcInServ.cmd:
regedit -s stt010.reg
Description: Calls regedit silent (no screen appears) to update contents of stt010.reg. The contents of stt010.reg could contain following entries:
REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\ProTopas\CurrentVersion\LYNXCI\STATE\010] "STEP_PARAM"="113217217013211012013003"
overloads values of state 010. Note: The command job must return within 30 seconds.
U25604-J-Z745-1-7600
October 2004
173
Configuration Data
174
October 2004
U25604-J-Z745-1-7600
Security Features
General Overview
To understand and use the information in this section, you should understand some basic terms and concepts, which are defined below.
Algorithm
An algorithm is a structured mathematical procedure for solving a specific problem. The DES algorithm is designed to encrypt and decrypt blocks of data. The DES algorithm is not confidential and can be obtained by the general public. The keys used as part of the algorithm are what provides the confidentially The Data Encryption Standard (DES) specifies an algorithm to be used in electronic hardware devices for the purpose of cryptographic protection of computer data. Encryption keys are numbers that are used as part of the PIN verification process and also for encrypting messages to and from the terminals. As the DES algorithm is available to the general public, the keys must be kept secret to ensure the confidentiality of the data being encrypted. The Personal Identification Number (PIN) is the customers way of verifying his or her identity as established by an activator card. By entering this PIN, the customer is identified and can access the relevant accounts.
Data Encryption Standard [DES] Encryption keys
Personal Identification Number [PIN]
PIN verification PIN verification is the method of ensuring that the PIN entered on the ATM is the proper PIN for the card inserted in the ATM.
U25604-J-Z745-1-7600
October 2004
175
PIN and PIN Verification
Security Features
Financial Institution Table [FIT]
The Financial Institution Table (FIT) provides the following items to the network: capacity of using multiple card formats and multiple institutions the type of PIN verification the encryption key (if PEKEY is used) that is used to encrypt a PIN, which is sent to the network control of the transaction sequence of the terminal via FIT switch indexes. FIT can also be used to allow the institutions to define the exact operation flow of the terminal. This is done by supplying state flow through the FIT.
Message Authentication Code [MAC]
Message Authentication Code (MAC) provides a method of ensuring that messages sent between the terminal and the network are authentic and have not been modified.
PIN and PIN Verification

In order to access a Wincor Nixdorf customer service terminal, the customer must enter a Personal Identification Number (PIN). Typically, a request for PIN entry is made after the customer has inserted an activator card into the terminal. The terminal and/or the network must then verify the PIN before the transaction can continue. The processes for this verification are called PIN verification processes. This section describes both the PIN and the processes required to verify the PIN.
176
October 2004
U25604-J-Z745-1-7600
Security Features
Personal Identification Number (PIN)

The PIN is generally derived from an account number. In most PIN verification methods that account number is the Primary Account Number (PAN). The examples and explanations in this document assume that the PAN is the account number associated with the PIN. It is not necessary to use the entire PAN; it is possible to use only those PAN digits that vary from customer to customer. The local PIN verification process is based on an algorithm, a sequence of mathematical steps. Usually, some type of key governs the algorithm sequence. Generally, the process that generates the customers PIN also verifies that PIN. A particular key and a set of PANs correspond to a set of PINs. Some of the PINs may be duplicated; that is, one PIN may be derived from several PANs, but any given PAN has only one possible PIN.
PIN Entry
The first step in the PIN verification process is the customers PIN entry. This is done through a PIN entry state. If local PIN verification is being used, the terminal verifies the PIN and goes to the next state required. When remote PIN verification is used instead of local PIN verification, one of two transaction request messages is usually sent to the network. In the first method, the terminal can accept any PIN and continue with a transaction selection to the customer. The terminal then sends both the unverified PIN and the transaction request to the network in the same message. Then, the network can authorize or deny either the PIN or transaction. In the second way, the terminal forwards the PIN to the network in one request message, then awaits the go-ahead before giving a transaction selection to the customer. The second request message holds the current transaction information.
U25604-J-Z745-1-7600
October 2004
177
Security Features
Variable length PIN Entry

Using FIT, the terminal can accept a variable-length PIN. The FIT field PMXPN indicates the maximum number of PIN digits that a customer may enter. As soon as the customer enters the maximum number of PIN digits, the terminal automatically completes the PIN entry state. For example, the maximum number of PIN digits may be nine. On entry of the ninth digit, the terminal automatically completes the PIN entry state. The institution may issue PINs shorter than the maximum PIN length defined in a FIT. Customers receiving shorter PINs must press operation key A (which is active on PIN entry) to signal the end of the entry. After the customer presses operation key A, the terminal automatically completes the PIN entry state. For example, if the maximum PIN length is nine digits and the customer has a fivedigit PIN, the customer must press operation key A after the five-digit PIN is entered. If the customer inadvertently presses operation key A before entering all of the required PIN digits, the terminal automatically attempts to verify the digits entered. The PIN verification will fail and a retry or error state occurs (depending on the configuration of the states).
PIN Offset Number (DES verification)

For DES PIN verification, the PIN offset number allows an institution to let customers choose any PIN they wish. To accomplish this, an offset is added to or subtracted from the customers generated PIN to obtain the desired PIN. This is not, however, ordinary addition or subtraction, but modulo 10. In modulo 10, no figures are carried. The following example shows the difference between these two mathematical systems. 2716 + 3329 5035 (modulo 10) Note: 2716 + 3329 6045 (regular addition)
Diebold PIN and VISA/ABA PIN verification is not supported by ProCash/NDC and ProConsult/NDC.
178
October 2004
U25604-J-Z745-1-7600
Security Features
In the DES PIN verification process, the offset is added to the generated PIN to obtain the customer PIN. For example, if the GPIN is 5646 and the offset is 1507, the CPIN would be calculated as follows: 5646 + 1507 6143 GPIN OFFSET CPIN
An activator card data track stores the offset. FIT entry POFDX tells the terminal where to find the offset on the activator card data track. If an institution does not wish to use the offset, it may be set to zero.
PIN Verification Processes

ProCash/NDC and ProConsult/NDC support following types of PIN verification:
q q
DES local DES remote
These PIN verification processes are the steps that either the terminal or the network performs to verify that a customer-entered PIN is valid. The type of terminal you have and the data security equipment installed may dictate the processes that are available to you. For Wincor Nixdorf cash terminals, the following equipment is available to control PIN handling:
q q
DES PIN algorithm Encryption Decryption Module (EDM)
U25604-J-Z745-1-7600
October 2004
179
PIN Verification
Security Features
The following paragraphs describe this equipment and list the PIN verification processes that the equipment supports. DES PIN DES PIN encryption provides for local DES PIN verification and remote network PIN verification. This feature also encrypts the PIN before sending it to the network. This type of encryption provides increased security for the PIN. The Encryption Decryption Module (EDM) (available in all cash out systems) provides all the features of the DES PIN Verification/ Encryption option and the following additional features:
q q
EDM
Message Authentication (MAC) PIN encryption using Diebold or ANSI format
DES PIN requires Financial Institution Table (FIT) entries. These FIT entries tell the terminal what PIN verification process to use and where to find the information that the terminal needs to perform the verification process. Remote PIN Verification The terminal can also send the PIN to the network for verification rather than verifying the PIN at the terminal. The EDM encrypts the PIN before sending it to the network for verification. The following sections describe some of the essentials for PIN verification and each verification process.
PIN Verification
Wincor Nixdorf terminals support local or remote PIN verification. Depending on the FIT entries the terminal determine if the PIN should be checked locally or remote by the host.
180
October 2004
U25604-J-Z745-1-7600
Security Features
PIN Verification
Local PIN Verification

In the DES PIN verification process, the key is the PIN key. This PIN key is stored at the terminal. The PIN key serves the same purpose as the ALGO. The PIN key governs a sequence of operations in the DES ALGO. This algorithm is a standard procedure available to the public. Security is achieved by keeping the PIN key confidential. To obtain greater security, the PIN key is encrypted using the DES algorithm and another secret key. The resulting encrypted PIN key (PEKEY) is put into a FIT entry. During PIN verification, the terminal (or network) decrypts PEKEY to restore the PIN key. Before adding the generated PIN to the offset, DES PIN verification must go through two algorithm procedures. The first procedure decrypts PEKEY from the FIT using the Master key. In the second procedure, the decrypted PEKEY is the PIN key that is used to encrypt the PAN. The encrypted PAN is decimalized using the decimalization table in the FIT. Decimalization ensures that the PIN digits are decimal.
Network PIN Verification

Network PIN verification requires that the PIN be padded to 16 digits and encrypted before sending it to the Network. The terminal can encrypt the customer-entered PIN once or twice, then send it to the Network with unencrypted PAN and offset. The PIN may be send unencrypted, but this is not recommended only for system testing. When the encrypted PIN reaches the verification point in the network, a single (or double) decryption restores the customer entered PIN. Then the generated PIN will be compared with the calculated PIN. If the PIN is correct the transaction can be continued. The institution may choose to verify the encrypted PIN without performing decryption. This can be done by comparing the encrypted PIN to a table of encrypted PIN values. Therefore the PAN is used as a table look-up key. For remote PIN verification, the PIN is sent to the network in two different forms:
q q q
ANSI PIN/PAN Block Diebold PIN Block BANKSYS PIN Block
The terminal encrypts the block and sends it to the network. The network then handles the PIN verification. The FIT field PMXPN tells the terminal which form to use. See section Maximum PIN Entry Digits (PMXPN) on page 191 for more details on PMXPN.
U25604-J-Z745-1-7600
October 2004
181
PIN Verification ANSI PIN/PAN Block
Security Features
The ANSI PIN/PAN block is a 16-hex digit block that contains the result of exclusively ORing the ANSI PIN block and the Primary Account Number (PAN) block. The ANSI PIN block is 16 hex digits and appears as follows:
PIN digits
PIN digits or hex F depending on length of PIN
Filled with hex digit F
Length of PIN (4-12)
Control field (presently 0)
The PAN block is 16 hex digits and appears as follows:
PAD digits
PAN digits
The PAD digits are always hex 0. The PAN digits are the least significant digits of the PAN. The number of digits is determined by the FIT parameters PANLN, PANDX, and PINDX. If the PAN digits are less than 12, hex 0s are used to fill the remaining slots. The PIN block and PAN block are then exclusively ORed together to create the PIN/PAN block. This block is then encrypted according to the FIT field PINPD and sent to the network.
182
October 2004
U25604-J-Z745-1-7600
Security Features Diebold PIN Block
PIN Verification
The Diebold PIN block is 16 hex digits and appears as follows:
PIN digits
PIN or PAD digits depending on PIN length
PAD digits
Refer to section PIN Pad Character (PINPD) on page 194 for more details on the Diebold PIN block. The Diebold implementation of DES uses 16 hex digits, 0-F. The encryption process results in 16 hex digits that are converted to ASCII by prefixing each hex digit with a hex 3 to convert the 16 hex digits to 16 ASCII digits. These 16 ASCII digits are sent to the host if the protocol is ASCII. If the communication protocol is EBCDIC, the 16 ASCII digits are converted prior to transmission. The host must reconvert the received 16 digits to 16 hex digits prior to decrypting PIN buffer A. If the protocol is ASCII, the only conversion required is removing the prefixed hex 3 from each digit and combining the resultant into eight bytes. If the host protocol is EBCDIC, each digit must be converted by using the conversion prior to combining the digits into eight bytes. The following table shows the conversion from ASCII to EBCDIC. HEX DIGIT 0 1 2 3 4 5 6 7 8 9 A B C D E F ASCII (HEX) 30 31 32 33 34 35 36 37 38 39 3A 3B 3C 3D 3E 3F GRAPHIC DIGIT 0 1 2 3 4 5 6 7 8 9 : ; < = > ? EBCDIC (HEX) F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 7A 5E 4C 7E 6E 6F
U25604-J-Z745-1-7600
October 2004
183
ID Card and FIT Definitions
Security Features
For example assume that the PIN is encrypted and F is used to pad the PIN. If the entered PIN is 4512, the 16 hex digits internal to the terminal before encryption are:
45 12 FF FF FF FF FF FF
These 16 hex digits are internal to the terminal after encryption as follows (example only):
7A 4C F2 97 31 6E 51 33
These hex digits are then converted to ASCII by prefixing each hex digit with a hex 3:
373A 343C 3F32 3937 3331 363E 3531 3333
If the host protocol is ASCII, the PIN buffer contains these ASCII digits. If the host protocol is EBCDIC, the PIN buffer will contain the following 16 bytes:
F77A F44C 6FF2 F9F7 F3F1 F66E F5F1 F3F3
The graphic presentation in a line trace of these bytes will be as follows:

7:4<?297316>5133

This section describes each FIT byte and the associated identification card magnetic data tracks.
184
October 2004
U25604-J-Z745-1-7600
Security Features
ID Card Data Tracks

A customer card has one, two or three magnetic data tracks. These tracks retain sufficient information to identify a corresponding customer's account. FIT allows a terminal to find the information on the data tracks. Industry standards designate the three tracks as follows: Track 1, Track 2 and Track 3. Wincor Nixdorf terminals can be equipped to read each track and to write to Track 1/2 and 3. Normally, Track 1 contains the customer's name. Depending on the terminal programming, the name can be shown on the terminal screen during a transaction. Each track has a common set of reference delimiters that are specially encoded digits. The delimiters locate three positions: the start sentinel (SS), the end sentinel (ES), and the field separator (FS). If the track contains more than one separator, the separators are designated as the first field separator, second field separator, and so on. For error checking, there is one other digit on a track. This digit is the longitudinal redundancy digit (LRC). The start sentinel is the first track digit. The end sentinel and LRC are the last two digits. Track 1 can be encoded with up to 79 digits, including the sentinels, separator, and LRC. Track 2 can be encoded with up to 40 digits and track 3 can be encoded with up to 107. The tracks have the same physical length; they differ in capacity because of different encoding densities (bits per inch). The terminal reads the magnetic data digits of each track and stores the information in three data buffers. The data on a track is found by counting forward from the start sentinel or first field separator or backward from the end sentinel.
U25604-J-Z745-1-7600
October 2004
185
FIT (Financial Institution Table)
Security Features

The FIT table contains data that specifies institution IDs, information required for PIN verification, and routing information for multi-institution terminal use. A FIT can also contains card formats and indexes indicating where to find specific information on a card. FIT data is down-line loaded to a terminal. Each of the FIT table bytes falls under following categories:
q q q q
institution identification indexes and lengths related to the ID card format counts, digits, codes and keys for PIN verification and related security reserved for future use
Configuration Data
Before processing transactions, a terminal must receive configuration data from the host. Configuration data is down-line loaded into the Windows registry location ..\LYNXCI\FIT. The Financial Institution Tables are part of the configuration data which are added to the personality of the terminal. FIT data are down-line loaded in a Financial Institution Table Load command message, see section FIT Data Load on page 258 for details. ProCash/NDC or ProConsult/NDC stores FIT data in the Windows registry location ..\LYNXCI\FIT, which represents the FIT library. ProCash/NDC and ProConsult/NDC can store a maximum of 1000 FIT entries (000-999). The highest numbered FIT entry received in a Financial Institution Table Load command message marks the end of the FIT library. After reading an identification card, the terminal scans the FIT library, trying to match the card institution ID field with a particular FIT entry. If the terminal finds a match, it then proceeds to the PIN entry state table. See section PIN Entry State (B) on page 64 in manual part 1 for details. An institution identification scan always begins with FIT 000 and continues until:
q q
the terminal matches a FIT institution ID the terminal finds a null FIT (a FIT which is not completed during a configuration down-line load) the terminal reaches the end of the FIT library
186
October 2004
U25604-J-Z745-1-7600
Security Features
FIT Library Restrictions

A FIT library has four restrictions. Violating these restrictions may cause unpredictable terminal operation. FIT gap A FIT library should not have any gaps. A gap is one or more zero FITs between filled FITs. For example, if any sample application requires 27 FIT entries, they must be consecutively numbered from 000 to 026. The terminal then recognizes only FIT 000 to FIT 026 since any scan will find a zero FIT at FIT 027. The sample application could not use FIT 000 to FIT 013 followed by FIT 020 to FIT 032 because of the gap beginning with FIT 014 through FIT 019.
Modifying the FIT library
The financial institution can modify the FIT configuration data. For example, institution E has FITs 006 through 010. If, for some reason, institution E wishes to add another FIT, for example, between 008 and 009, the current FITs 009 through 011 must shift one position ahead to become 010 through 012. The inserted FIT becomes the new 009. On the other hand, if institution E wishes to drop a card format, for example, FIT 007, FITs 008 through the end of the library must shift back one position. Thus, 008 becomes 007, 009 becomes 008, and so forth. Never delete a FIT by omitting that FIT from a down-line load. This creates a gap in the FIT library at which FIT scanning will stop. Instead of deleting a FIT, renumber them. A FIT may contain all zeros (a zero FIT). The zero FIT must be last, because its PIDDX, PFIID, PSTDX and PINDX fields are not the same as those in the base FIT. An institution may include several zero FITs or groups of zero FITs within the down-line load. These zero FITs may be given values at a later date.
Switch FITs A FIT entry that has a PFIID of all Fs will match any card. This entry must be the last FIT in the table. No FIT entry with a higher number will be checked.
U25604-J-Z745-1-7600
October 2004
187
FIT Data Definitions
Security Features
Multi Card, Multi Institution Capability

An activator card has one to three magnetic data tracks (section ID Card and FIT Definitions on page 184). Several FIT bytes indicate the size and location of the data fields on the tracks. These bytes specify the following:
q q q
on which track the specific data fields can be found the direction of the data field, relative to a track delimiter the number of track positions occupied
Alternate Transaction Sequences

A FIT may contain information that causes the terminal to follow alternate sequences of states and screens. This allows the use of transaction sets specifically designed for different activator card formats. This method uses the FIT switch state table. Refer to section FIT Switch State (K) on page 99 for detailed description of this state.

The bytes that make up a FIT entry are divided into 16 fields. Many of the fields contain only one byte. A FIT byte represents one of the following:
q q q
two hex digits with hex values 0 to F for each digit two hex digits with each digit restricted to the decimal values 0 to 9 eight bits possibly divided into bit fields one to seven bits wide
Table 51 shows the 16 fields listed by mnemonic, in alphabetical order; Table 52 shows these fields listed according to their positions in the FIT.
188
October 2004
U25604-J-Z745-1-7600
Security Features
An index indicates how many digit positions should be skipped over between a track delimiter and the first data digit. Throughout this section, the term displacement means the number of digits to be skipped. A displacement equal to zero means skip no positions; the first data position is adjacent to the track delimiter. A displacement equal to three means skip three positions; the data begins in the fourth position. The following two tables give a short description about the FIT fields:
Table 51: Alphabetical FIT references
Field Mnemonic PAGDX PANDX PANLN PANPD PCKLN PDCTB PEKEY PFIID PIDDX PINDX PINPD PLNDX PMXPN POFDX PRCNT PSTDX
Description ALGO number index (not used) PAN index PAN length PAN pad character PIN check length decimalization table encrypted PIN key institution identification institution index data track locator PIN pad character language code index maximum PIN entry digits offset number index PIN retry count index indirect next state index reserved (not used)
Length 1 1 1 1 1 8 8 5 1 3 1 1 1 1 1 1 2
Byte Position 8 12 13 14 10 17-24 25-32 2-06 1 33-35 11 36 9 16 15 7 37-38
U25604-J-Z745-1-7600
October 2004
189

Table 52: FIT fields listed by data track position
Security Features
Byte Position 1 2-06 7 8 9 10 11 12 13 14 15 16 17-24 25-32 33-35 36 37-38
Length 1 5 1 1 1 1 1 1 1 1 1 1 8 8 3 1 2
Field Mnemonic PIDDX PFIID PSTDX PAGDX PMXPN PCKLN PINPD PANDX PANLN PANPD PRCNT POFDX PDCTB PEKEY PINDX PLNDX
Description institution index institution identification indirect next state index ALGO number index (not used) maximum PIN entry digits PIN check length PIN pad character PAN index PAN length PAN pad character PIN retry count index offset number index decimalization table encrypted PIN key data track locator language code index reserved (not used)
Institution Index (PIDDX)

PIDDX is the displacement from the delimiter specified by PINDX (byte 0, low-order digit) to the start of the activator card institution identification field. PIDDX comprises two hex digits with values 00 to 7F.
190
October 2004
U25604-J-Z745-1-7600
Security Features
Institution Identification (PFIID)

PFIID is the institution identification number. After reading an activator card, the terminal scans its FIT library for a PFIID that matches the institution identification number on the activator card. PFIID contains ten hex digits (two per byte). Each digit must have a hex value of 0 to 9 or F (A, B, C, D and E are not permitted). An F in any position means match all; that is, any value on the activator card at that position matches. FIT's that have Fs in PFIID should be at the higher numbered positions in the FIT library. For example, a PFIID that is all Fs should be the last FIT in the library because all activator cards match the PFIID.
FIT Switch Index (PSTDX)

PSTDX indicates the next state location in the FIT Switch state table. See section FIT Switch State (K) on page 99 for details. PSTDX comprises two hex digits with values 00 to 06 and . (PSTDX is not a displacement on the ID card.)
Maximum PIN Entry Digits (PMXPN)

PMXPN is the maximum number of PIN digits that the terminal accepts from a customer on any one PIN entry. PMXPN must be greater than or equal to the value of the five low-order bits of PCKLN. PMXPN comprises two hex digits with values of 04 to 10 for Diebold PIN block or 84 to 8C for ANSI PIN block. With the data security module installed, the PMXPN values are 04 to 0F. ProCash/NDC or ProConsult/NDC identifies a null FIT if PMXPN = 0. The highest order bit of PMXPN indicates whether Diebold or ANSI PIN block is used. The bit definitions are as follows: 0 - Diebold PIN block 1 - ANSI PIN block An institution may issue PIN's shorter than PMXPN. These are variable-length PIN's. Customers with variable-length PIN's enter their PIN digits, then press operation key A to signal the end of the PIN entry.
U25604-J-Z745-1-7600
October 2004
191
Security Features
PIN Check Length (PCKLN)

PCKLN provides the following information to the terminal: The number of PIN digits to be verified. This number must be less than or equal to the maximum PIN length (PMXPN). If this number is less than PMXPN, the Diebold PIN verification process checks the last digits entered up to the number indicated by the PCKLN field. For example, if the customer has a PIN of 1346875 and the PCKLN is 4, the process will check the last four digits entered, 6875. The number of digits in the offset number. This number is always equal to the number of PIN digits verified. The PIN verification algorithm to be used for terminal PIN verification. This information is in two bit fields:
3 BITS
5 BITS
The high-order three-bit field indicates the type of local terminal PIN verification to be used. BITS 000 001 010 011 100 101 110 111 ALGORITHM DES not supported Diebold (not supported) reserved not supported reserved reserved reserved
192
October 2004
U25604-J-Z745-1-7600
Security Features
DES and Diebold - The low order five-bit field is the number of PIN digits verified and the number of digits in the offset. The value must be less than or equal to PMXPN. If the entire PCKLN byte is zero, the terminal does not perform local PIN verification. TERMINAL VERIFICATION none DES DES (EDM) Diebold HEX VALUE RANGE 00 04-10 04-0F 40, 44
U25604-J-Z745-1-7600
October 2004
193
Security Features
PIN Pad Character (PINPD)

PINPD is only used for DES encryption of PINs in messages sent to the network. PINPD is reserved and equal to zero for other PIN verifications. PINPD comprises two hex digits. The high-order digit indicates the message encryption type, the key(s), and the use of the message coordination number.
HIGH-ORDER BITS HEX TYPE OF ENCRYPTION USE AS KEY 1 USE AS KEY 2 USE COORD.NO.
0000 0010 0011 0100 1000** 1010** 1011** 1100
0 2 3 4 8 A B C
single double double none single double double none
COM MASTER PIN* none COM MASTER PIN* none
none COM COM none none COM COM none
no no no no yes yes yes yes
* PIN key is PEKEY decrypted by master key ** Not applicable with ANSI PIN block
The low-order digit pads the PIN to the right in the PIN buffer of the terminal. When ANSI PIN block has been selected, PINPD is not used to pad the PIN. PINPD must be used to select the type of ANSI PIN block encryption. The PIN buffer stores the customer-entered PIN digits in an equal number of positions. Then, the pad digits concatenate to the PIN digits to yield 16 PIN buffer positions. When the message coordination number is not in the message sent to the network, the terminal encrypts (either single or double) these 16 PIN buffer digits before transmission. The 16 PIN buffer digits can also be sent without encryption, but this is not recommended. When the message coordination number is in the message to the network, the message coordination number is inserted in the PIN buffer before encryption. In effect, the PIN and pad shift right one position, loosing one pad digit. The valid range of hex values for PINPD includes 00 to 0F, 20 to 4F, 80 to 8F, and A0 to CF. 194 October 2004
U25604-J-Z745-1-7600
Security Features
PAN Index (PANDX)

PANDX is the displacement from the delimiter specified by PINDX (byte 1, loworder digit) to the start of the ID card PAN field (those PAN digits used for PIN verification). PANDX comprises two hex digits with values 00 to 7F.
PAN Length (PANLN)

PANLN is the number of PAN digits to be used for terminal PIN verification. Depending on PIN verification, PANLN has the following value limits:
q q
DES - PANLN comprises two hex digits with values 00 to 10. Diebold - PANLN comprises two hex digits with values 04 to 13 or 1F. PANLN must be greater than or equal to the value of the five low-order bits in PCKLN. When PANLN equals 1F, the terminal uses all PAN digits from the PANDX starting position to the field separator that follows. ANSI PIN block - PANLN comprises two hex digits with values from 00 to 0C or 1F. When PANLN equals 1F, the PAN is obtained as follows: locate the first field separator on the specified track. count back 13 digits or to the first digit before the start sentinel, whichever count is the least. the PAN will include all the digits from this point up to but not including the last digit before the first field separator. the delimiter and direction specified in PINDX and PANDX do not apply.
U25604-J-Z745-1-7600
October 2004
195
Security Features
PAN Pad Character (PANPD)

PANPD has three definitions (depending on the PIN verification scheme used): DES - PANPD comprises two hex digits. The low-order digit pads those PAN digits specified by PANLN (to 16 positions). The 16-position padded PAN is then encrypted to produce a generated (natural) PIN. The high-order PANPD hex digit specifies which of the following encryption keys is used: 0 = use the PIN key (decrypted PEKEY) 8 = use the master key Other hex values of either 00 to 0F or 80 to 8F. DIEBOLD - PANPD is the algorithm number (ALGO) when PAGDX equals hex FF. When PAGDX does not equal FF, PANPD is not used and is, thus, equal to zero. PANPD comprises two hex digits with each digit restricted to values 0 to 9 (hex values A to F not permitted). The PANPD values are 00 to 99.
PIN Retry Count Index (PRCNT)

The low-order seven bits of PRCNT are the displacement from the delimiter specified by PINDX (byte 1, high-order digit) to the ID card PIN entry count field. The high-order bit of PRCNT indicates the retry count conditions. HI-ORDER BIT 1 0 CARD RETRY COUNT CONDITION FORMAT ISO MINTS Count down on each retry; stop at zero. Count up on each retry; stop at the retry value in PIN entry state table.
PRCNT comprises two hex digits with values 00 to 7F (MINTS) or 80 to FE (ISO) or FF. When PRCNT is hex FF, the PIN entry count is not on the ID card, but in the PIN entry state table.
196
October 2004
U25604-J-Z745-1-7600
Security Features
Offset Number Index (POFDX)

POFDX is the displacement from the delimiter specified by PINDX (byte 2, loworder digit) to the start of the ID card offset field. POFDX comprises two hex digits with values 00 to 7F or FF. When the value of POFDX equals hex FF, the offset is not used.
Decimalization Table (PDCTB)

PDCTB is the DES decimalization table containing a pattern of decimal digits (two per byte, hex values A to F not permitted). The institution is responsible for producing values for PDCTB. A sample value follows:
01 01 23 23 45 45 67 67 89 89 AB 01 CD 23 EF 45 (standard hex digits) (decimalized digits)
The digit positions map the corresponding hex digits from the DES process to ensure that only decimal digits result. Each decimal digit (0 to 9) should appear at least once, but not more than twice.
Encrypted PIN Key (PEKEY)

PEKEY is the encrypted PIN key. The master key encrypts the PIN key. The PIN key encrypts the PAN digits specified by PANDX and PANLN to yield a generated PIN for DES terminal PIN verification. PEKEY comprises 16 hex digits (two per byte), with each digit having a hex value of 0 to F. For non-DES operation PEKEY is reserved and all bytes must be hex 00. The institution is responsible for providing PEKEY values.
U25604-J-Z745-1-7600
October 2004
197
Security Features
Data Track Locator (PINDX)

PINDX comprises six hex digits (two per byte). Five of the six PINDX digits specify the ID card data track delimiter to be used in conjunction with five corresponding indexes (PAGDX, PIDDX, PRCNT, PANDX, PLNDX and POFDX). PINDX Byte FIT byte 33 FIT byte 34 FIT byte 35 Hi-Order HEX digit PAGDX (ALGO) PRCNT (RETRY) LO-Order HEX digit PIDDX (ID) PANDX (PAN)
PLNDX (LANGUAGE) POFDX (OFFSET)
The four bits of each non-reserved digit define a track, a delimiter and a direction from that delimiter. Digit Bits 00XX 01XX 10XX 11XX XX00 XX01 XX10 XX11 Bit Pair Definition Start sentinel, count forward First field separator, count forward End sentinel, count backward Reserved Track 2 Track 3 Track 1 Reserved
Language Code Index (PLNDX)

The Language Code Index specifies the offset for the language code on the ID card. This field can be used in conjunction with state V (Language Select from Card state). The V state sets the screen group of multi language screens that should be displayed during transactions. PLNDX is in range of 01-7F hex. The value of 00 hex is not allowed if the language code is used. The value 7F hex means zero if the language code is used and the search is backwards from an end sentinel only.
198
October 2004
U25604-J-Z745-1-7600
Security Features
Message Authentication (MAC)

Overview
Message authentication minimizes the risk of unauthorized tampering with the messages sent between the terminal and the network. Message modification and message replay are two methods of message tampering. Message modification is where the data communication lines between the terminal and next node are tampered with so that values in a message can be changed for fraudulent purposes. Message replay is where entire messages are copied from a previous transaction and retransmitted later for fraudulent purposes. To help minimize the risk of message tampering, two fields are added to the messages, a time variant number and a Message Authentication Code (MAC). The time variant number is a randomly-generated eight-digit hex number. This number is generated by the terminal for each transaction request message. The MAC is an eight-digit hex number containing the result of a MAC calculation on the message. For example, the transaction request message is formed and includes a time variant number. Once this is done, a DES operation is performed on the message using the master key and the DES algorithm. The result of this operation is the MAC. The MAC is placed in the MAC data field at the end of the message. Upon receiving the message, the network performs the same DES operation on it. The network then compares the result of this DES operation with the MAC contained in the MAC data field. If the two match, the network is assured that the message is from a valid terminal and that it has not been tampered with. The network then returns the time variant number with its Transaction Reply command. The ATM can check that this is the same time variant number sent in the transaction request. This ensures that the entire process is authentic. Messages that can be authenticated are as follows:
q q q q q q
Transaction Request command Transactioen Reply command State Table Load command FIT Table Load command MAC Field Selection Load command Solicited Status messages
U25604-J-Z745-1-7600
October 2004
199
Security Features
The ANSI standard X9.9 describes the procedures and provides the algorithm used to calculate the MAC data. A MAC master key is used with this algorithm to perform the MAC calculation. This master key is down-line loaded from the network in an Encryption Key Load command message.
MAC flags
Message Authentication is controlled by some configuration parameters which have to be set in PARAC configuration file CUSTOM.PPF. The following table shows the MAC flags to be activated:
Table 53: MAC flags definition
NDC PARAMETER in FLAG CUSTOM.PPF 1 CHECK_TVN_MAC VALUE 0 DESCRIPTION Do not check TVN in Transaction reply messages, or MAC in Transaction reply, State Table or FIT Load messages. Check TVN in Transaction reply messages, or MAC in Transaction reply, State Table or FIT Load messages. Do not send the TVN and MAC data in Transaction Request messages Send the TVN and MAC data in Transaction Request messages Do not check the Security Terminal Number in Tran. Reply messages Check the Security Terminal Number in Tran. Reply messages The MAC calculation is performed on the whole message The MAC calculation is performed on the fields that are specified in the MAC field selection table downloaded from host. Do not send the TVN and MAC on solicited device status messages Send the TVN and MAC on solicited device status messages Do not include the Security Terminal Number in terminal to host messages Include the Security Terminal Number in terminal to host messages Calculate the MAC in EBCDIC Calculate the MAC in ASCII
1 2 SEND_TVN_MAC 0
1 8 CHECK_MACHINE_NO 0
1 9 MAC_FLD_SELECTED 0 1
10
SEND_TVN_MAC_SOL
1 SEND_MACHINE_NO (not configurable via ProCash/NDC-SOP or ProConsult/NDC-SOP) MAC_ASCII (not configurable via ProCash/NDC-SOP or ProConsult/NDC-SOP) 0 1 0 1
200
October 2004
U25604-J-Z745-1-7600
Security Features
Security Terminal Number (Machine Number)

Message Authentication uses a six digit Security Terminal Number in the messages which has to be included to build the MAC field. The Security Terminal Number can be entered in the User Exit functions item Enter Machine no. of ProSop. If you have configured the ProCash/NDC-SOP, refer to the ProCash/SOP Service & Operating User Guide for details. See also ProCash/NDC ProConsult/NDC Installation manual section [HARDWARE_CONFIGURATION] about MACing activation.
MAC data field

There are two additional fields in the messages for message authentication. The first field, the MAC data field, contains the result of a MAC calculation performed on the message. This MAC calculation uses the MAC master key and the DES algorithm to obtain its result. The MAC data field is calculated by performing a MAC calculation on the message from the first field after the protocol-dependent header (on a Transaction Reply command this is the Transaction Reply command identifier) up to but not including the field separator preceding the MAC data field. The MAC data field is always the last field of the message preceding the end of text (ETX). The digits on which the MAC calculation is performed are the same digits that appear on the communications line. For example, if the protocol is IBM 3275 EBCDIC, the digits that are authenticated will be EBCDIC; if the protocol is IBM 2265 ASCII, the digits will be ASCII.
Time variant number

If the message is a transaction request or Transaction Reply command, another field, the time variant number, is also included in the message. The time variant numbers are generated randomly by the terminal. If a terminal expects a MAC in a message and does not receive it, the terminal will reject the message. On the other hand, if a terminal does not expect a MAC but receives it, the terminal operation is not guaranteed. Refer to your terminal programming manual for more details on the messages.
U25604-J-Z745-1-7600
October 2004
201
Security Features
Typical Message Authentication Procedure

The following steps describe a typical message authentication procedure.
q
If the terminal is sending a transaction request message, it first generates a time variant number and inserts the number after the third field separator of the message. The terminal performs a MAC calculation on the transaction request message. The result of this calculation is placed at the end of the message in the MAC data field. When the network receives the transaction request message, it performs a MAC calculation on the message. The network compares the result of the MAC calculation with the data in the MAC data field. If the two are the same, the network generates a Transaction Reply command message instructing the terminal to perform the desired transaction. If not, a Transaction Reply command message is sent directing the customer to try another transaction. The network inserts the time variant number received in the transaction request message into the Transaction Reply command message. The network performs a MAC calculation on the Transaction Reply command message. The result of this calculation is placed at the end of the message in the MAC data field. When the terminal receives the Transaction Reply command message, it performs a MAC calculation on the message. The terminal compares the result of the MAC calculation with the data in the MAC data field of the Transaction Reply command message. If the two are the same, the terminal then continues to step 9. If not, the terminal sends a command reject in a solicited status message. The terminal then compares the time variant number sent in the transaction request message to the time variant number received in the Transaction Reply command message. If the two are the same, the terminal services the Transaction Reply command. If not, the terminal sends a command reject in a solicited status message.
202
October 2004
U25604-J-Z745-1-7600
Security Features
Triple DES operation
MACing for State and FIT Table Load commands

For the State Table Load and FIT Table Load command messages, only the MAC data field is used for message authentication. The network performs a MAC calculation on the Load command message being sent and puts the result in the MAC data field. When the terminal receives the message, it performs a MAC calculation on the message. The terminal then compares the result of the MAC calculation with the MAC data field. If the two are the same, the terminal accepts the Load command message. If not, the terminal transmits a command reject in the solicited status message.
Triple DES operation

Since release 1.2/10 ProCash/NDC is able to operate in triple DES mode. For triple DES operation, following minimum conditions are required:
q
The EPP hardware of the system must be able to operate with double length triple DES keys (minimum firmware version 4.23). Triple DES mode has to be enabled in the installation dialog of ProCash/NDC at the beginning of the installation process. Refer to ProCash/NDC Installation manual for details about Triple DES configuration. The host system must be able to download double length triple DES keys to the terminal. Local security keys (Master-Key , COM-Key) have to be entered via Triple DES key entering method.
EMV capability
Since release 1.3/00 ProCash/NDC supports transactions with EMV data. Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for EMV for detailed descriptions how to integrate EMV support.
U25604-J-Z745-1-7600
October 2004
203
Remote Key Loading (RKL) capability
Security Features
Remote Key Loading (RKL) capability

Since release 1.3/00 ProCash/NDC supports Remote Key Loading (RKL). Please refer to Wincor Nixdorf / Diebold D91x Message Format Extension for RKL for detailed descriptions how to integrate RKL.
204
October 2004
U25604-J-Z745-1-7600
Messages
This section describes the messages that make up the communications interface between the Wincor Nixdorf terminals and the controlling network. Unless otherwise indicated, information refers to all versions. The terminal gathers all the necessary information for a transaction request. Typically this information consists of the following:
q q q
account card data including the Primary Account Number (PAN) the Personal Identification Number (PIN) various terminal keyboard inputs
Figure 2: Transaction message flow on page 206 is an example of a typical message exchange sequence. The Transaction Request message is sent to the network. The network responds to a Transaction Request message with a Transaction Reply command message. The Transaction Reply command message tells the terminal how to accomplish the requested transaction. After the terminal completes the transaction with the customer, it sends a solicited status message to the network. The basic message formats used in the system are fixed. These formats contain the necessary control characters to conform with most protocol formats. This section shows the format for each message type used in the system. Messages can travel either from the terminal to the network, or from the network to the terminal.
Messages from Terminal to Network

The terminal transmits three message types.
q q q
Solicited Status messages Unsolicited Status messages Transaction Request messages
U25604-J-Z745-1-7600
October 2004
205

Figure 2: Transaction message flow
Messages
TERMINAL
Consumer enters card and PIN
NETWORK
Consumer enters request data; terminal formats request
Transaction Request message
Make decision to allow or disallow transaction
Complete transaction as directed; format status message
Transaction Reply message
Solicited Status message
Record completed transaction
The following subsections illustrate these messages in tabular form. The notes in the following table apply to all tables.
Table 54: Code conventions
Code Symbols X
Description This symbol indicates that the terminal ignores the data. The data for this code must be a valid character as described in this manual. An example of an invalid Wincor Nixdorf terminal character for this code is a zero (hex 00). Three dashes indicate that the field data is dependent on the specific transaction performed and the valid entries for the field. Refer to the field descriptions in this manual. The colon symbol indicates that the following two digits are a hexadecimal number. Single quotation marks indicate that the characters enclosed within them are graphic characters from an ASCII or EBCDIC code set.
---
206
October 2004
U25604-J-Z745-1-7600
Messages
[ ]
Brackets indicate that the field is optional. The field can be deleted completely from the message without affecting the format or meaning of the message. The data for this code must be a valid character as described in this manual. An example of an invalid Wincor Nixdorf terminal character for this code is a zero (hex 00). It will be skipped by the emulation. VAR indicates that the length of the field is variable. Numeric parenthetic expressions following VAR show the maximum number of characters allowed in the field.
VAR (Numeric)
U25604-J-Z745-1-7600
October 2004
207

Figure 3: Terminal to network messages
Messages
Terminal to network messages
Solicited Status
TERMINAL
Unsolicited Status
HOST
Transaction Request
208
October 2004
U25604-J-Z745-1-7600
Messages
Transaction Request message

This message contains data which the network needs to authorize a customer transaction at the terminal. The maximum length of this message is 2000 characters (bytes). The network answers a Transaction Request with a Transaction Reply command to the terminal. The following table shows the data fields and sequence of fields for a Transaction Request message.
Table 55: Transaction Request message
Description solicited/unsolicited ID message identifier field separator (FS) logical unit number (LUNO) field separator (FS) field separator (FS) time variant number field separator (FS) top-of-form flag message coordination number field separator (FS) track 2 data field separator (FS) track 3 data field separator (FS) operation code buffer field separator (FS) whole-amount/cents keyboard entry field separator (FS) PIN buffer (Buffer A) field separator (FS) general purpose buffer B field separator (FS)
Code 1 1 :1C --:1C :1C [---] :1C ----:1C [VAR] :1C [VAR] :1C [---] :1C [---] :1C [VAR] :1C [VAR] :1C
No. of Characters 1 1 1 3 or 9 1 1 8 1 1 1 1 Var (40 max) 1 Var (106 max) 1 0 or 8 1 0, 8 or 12 1 Var (16 max) 1 Var (32 max) 1
U25604-J-Z745-1-7600
October 2004
209
Messages
Description general purpose buffer C field separator (FS) track 1 data buffer (1) identifier track 1 data buffer field separator (FS) Transaction status identifier Last transaction status data field separator (FS) CSP data ID U CSP data field separator (FS) confirmation CSP data ID V confirmation CSP data field separator (FS) MAC data
Code [VAR] [:1C] [1] [VAR] [:1C] [2] [VAR] [:1C] [:1C] [VAR] [:1C] [:1C] [VAR] [:1C] [---]
No. of Characters Var (32 max) 1 1 Var (79 max) 1 [1] 1 [1] 25 1 1 Var (16 max) 1 1 Var (16 max) 1 [2] 8 [2]
[1]
[1] These bytes are only sent if the download option is selected in the Enhanced Configuration Parameters load message. [2] These bytes are only sent if MACing is used
The following paragraphs describe the fields in the Transaction Request message. Solicited/unsolicited message field Field size: 1 character
Valid range: 1-2 Description: This field tells the network whether the message is solicited or unsolicited. The valid entries for this field are as follows: 1 - unsolicited message 2 - solicited message In case of a Transaction Request message, this field will be 1.
210
October 2004
U25604-J-Z745-1-7600
Messages Message identifier field Field size: 1 character
Valid range: 1 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Transaction Request message is 1. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number used for MACing. See section Message Authentication (MAC) on page 199 for further information. Time variant number Field size: 8 characters
Valid range: See description Description: This is an eight-character field, containing hexadecimal characters, randomly generated by the ATM. See chapter Security Features from page 175 for further information.
U25604-J-Z745-1-7600
October 2004
211
Messages from Terminal to Network Top-of-form (TOF) flag Field size: 1 character
Messages
Valid range: 0-1 Description: This data field informs the network if this transaction is printing at the top of the transaction record form. The valid values are as follows: 0 - not printing this transaction at the top of the transaction record form. 1 - printing transaction at the top of the transaction record form. Message coordination number Field size: 1 character
Valid range: ASCII 31-3F (or extended range 31-7E) Description: This is a character assigned by the terminal to each transaction request message. The terminal assigns a different coordination number to each successive transaction request on a rotating basis. The valid range for the coordination numbers is graphic 1 through 9, :, I ;, <" =, , >, and ? (ASCII 31 through 3F). If the extended range for the message coordination number field is enabled (Enhanced Configuration Parameters Load message), the valid range is ASCII 31 trough 7E. The host or controller must include the corresponding coordination number when responding with a transaction reply message. If the coordination numbers do not match, the terminal sends a solicited status message with a command reject status. Track 2 data field Field size: Variable
Valid range: See description Description: This variable length data field contains up to 40 characters of data from track 2 of the magnetic stripe on the customers account card. This field includes the data from the start sentinel to the end sentinel inclusive.
212
October 2004
U25604-J-Z745-1-7600
Messages Track 3 data field Field size: Variable
Valid range: See description Description: This is variable length field contains up to 106 characters of data from track 3 of the magnetic stripe. This field includes the data from the start sentinel to the end sentinel inclusive. Operation code buffer Field size: 0 or 8 characters
Valid range: See description Description: The operation code buffer field contains the data collected in the operation code buffer as a result of function display keys (FDKs) pressed. States D, E and Y determines the contents of this field, which identifies the transaction selected by the consumer. The field can be either zero or eight characters long. The Preset Operation Code state can clear and preset any of the positions in the operation code buffer. State E or Y determine in which position and how many graphics are stored in the operation code buffer when an FDK is pressed. For detailed descriptions refer to following sections: Pre-Set Operation Code Buffer State (D) on page 72 Four FDK Selection Function State (E) on page 78 Eight FDK Selection State (Y) on page 132
U25604-J-Z745-1-7600
October 2004
213
Messages from Terminal to Network Whole-amount and Cents keyboard entry field Field size: 0 or 8, 0 or 12
Messages
Valid range: See description Description: If the amount buffer size feature is not selected, the whole-amount and Cents keyboard entries field can be either zero or eight characters long. If the amount buffer size feature is selected, this field can be either zero or twelve characters long. This field identifies the whole-amount and cent amount entered at the keyboard. The content of this field is determined by the Amount Entry state. The data is right-aligned with zeros to fill unused positions on the left. PIN buffer Field size: 0 or up to 16 characters
Valid range: See description Description: The variable-length PIN buffer field will contain either no characters (if local PIN check is used) or the 16-character encrypted or decrypted PIN (if remote PIN check is used). The PIN buffer is also known as general purpose buffer A. General purpose buffer B Field size: Up to 32 characters
Valid range: See description Description: The contents of the variable-length general purpose buffer B field depend on whether the consumer message is being sent in response to an interactive transaction screen. If it is not being sent in response to an interactive transaction screen, this field only contains up to 32 digits that were entered by the customer. If it is being sent in response to an interactive transaction screen, this field contains up to 32 digits that were entered by the customer, and, if less than 32 digits were entered, this field also contains the character representing the operation key pressed or a time-out (A, B, C, D, E (cancel) or T (time-out)).
214
October 2004
U25604-J-Z745-1-7600
Messages General purpose buffer C Field size: Up to 32 characters
Valid range: See description Description: The variable-length general purpose buffer C field contains up to 32 digits that were entered by the customer, if so selected by the information entry state. Track 1 data buffer identifier (1) Field size: 1 character
Valid range: 1 Description: This one-character field identifies the data that follows in the next field as track 1 data. Track 1 data field Field size: Variable (79 maximum)
Valid range: See description Description: This variable-length field contains up to 79 characters of data from the track 1 magnetic stripe. This field includes the data from the start sentinel to the end sentinel inclusive. Transaction status data identifier Field size: 1
Valid range: 2 Description: Identifies the following data in the next fields as Transaction status data of the previous transaction.
U25604-J-Z745-1-7600
October 2004
215
Messages from Terminal to Network Last transaction status data Field size: 25
Messages
Valid range: See description Description: Contains status data relating to the previous transaction performed by the terminal. It contains the following data:
q
Last transaction serial number - 4 bytes Contains the four-digit serial number of the last transaction processed by the terminal. Last status issued - 1 byte Contains one byte identifying what the last known status message sent from the terminal was. The field can contain the following values: 0 - none sent 1 - good termination sent 2 - error status sent 3 - transaction reply rejected
Last transaction notes dispensed - 20 bytes Contains four five-digit decimal counts defining the notes dispensed on the last transaction.
CSP data ID U Field size: 1 character
Valid range: U Description: The value U in this field identifies the following field as the first Customer selected PIN data. If this field is selected in the transaction request state table and no CSP has been requested only this field will be present. CSP data Field size: 16 characters
Valid range: See description Description: This field contains an encrypted 16 character PIN.
216
October 2004
U25604-J-Z745-1-7600
Messages Confirm CSP data ID V Field size: 1 character
Valid range: V Description: Confirmation CSP data ID V is the field that identifies the following field as the second Customer selected PIN data. If this field is selected in the transaction request state table and no CSP has been requested only this field will be present. If the CSP state indicates that loacal verification of the two CSPs is to be carried out only the identifier will be sent if requested by the transaction request state. Confirmation CSP data Field size: 16 characters
Valid range: See description Description: Confirmation CSP data. This field contains an encrypted 16 character PIN. MAC data field Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the transaction request message. See the section Message Authentication (MAC) on page 199 for additional details.
U25604-J-Z745-1-7600
October 2004
217
Messages
Solicited Status messages

Solicited Status messages are sent from the terminal as the response to command messages received from the network. The maximum length of this message is 256 characters. The network expects a reply concerning the results of the last function performed through a Solicited Status message. If an error is detected during the last function performed, error status data pertaining to the terminal is inserted into the status message. If the functions are performed as commanded, a ready status indicator is inserted into the status message. The following tables list the data field associated with the Solicited Status message and shows field positions. The following table contains the fields of the solicited status message:
Table 56: Solicited Status message
Description solicited/unsolicited ID message identifier field separator (FS) logical unit number (LUNO) field separator (FS) field separator (FS) status descriptor field separator (FS) status information field separator (FS) MAC data field
Code 2 2 :1C --:1C :1C --[:1C] [---] [:1C] [---]
No. of Characters 1 1 1 3 or 9 1 1 1 1 VAR 1 [1] 8 [1]
[1] These bytes are only sent if MACing is activated for the solicited message.
218
October 2004
U25604-J-Z745-1-7600
Messages
The following paragraphs describe the fields for the solicited status message. Solicited/unsolicited message field Field size: 1 character
Valid range: 1-2 Description: This field tells the network whether the message is solicited or unsolicited. The valid entries for this field are as follows: 1 - unsolicited message 2 - solicited message In the case of the solicited status message, this field will be 2. Message identifier field Field size: 1 character
Valid range: 2 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Solicited Status message is 2. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See chapter Security Features from page 175 for additional details.
U25604-J-Z745-1-7600
October 2004
219
Messages from Terminal to Network Status descriptor Field size: 1 character
Messages
Valid range: See description Description: This one-character field describes the terminal status as it responded to the command. The valid values are as follows: 8 - device fault or configuration information. This character indicates a terminal device is reporting an abnormal status or that configuration information follows. 9 - ready. This character indicates the successful completion of either a terminal command or a Transaction Reply command when the separate ready for Transaction Reply command is not selected. A - general command reject. This character indicates the unsuccessful completion of either an terminal command or a Transaction Reply command. For example, a graphic A can be inserted into the status descriptor if the terminal receives any of the following: - an illegal command - illegal data from the network - configuration data while In Service mode Some additional general command reject conditions are listed in section Specific Command Reject Conditions on page 280. B - ready. When separate ready for Transaction Reply commands is selected, this character indicates successful completion of the Transaction Reply command. C - specific MAC command reject. The terminal can send this character only if MAC is enabled. This character indicates the unsuccessful completion of a message because of a message authentication code (MAC) failure or a time variant number failure. The terminal can send this character in response to any of the following messages: - a Transaction Reply command message - a State Tables Load command message - a FIT Data Load command message F - Terminal State. This is sent in response to terminal commands requesting Tallies, Logs, Supply Counters or terminal configuration information.
220
October 2004
U25604-J-Z745-1-7600
Messages
Status information (status descriptor F - Terminal State) Field size: VAR
Valid range: See description Description: The status information will vary according to which of the following terminal commands has been received by the terminal: q send configuration information
q q q q q
send supply counters send error log information send date/time information send configuration ID send Software ID and release number
See section Solicited Status (terminal state) on page 303 for detailed description of status information.
U25604-J-Z745-1-7600
October 2004
221
Messages from Terminal to Network Status information (status descriptor 8 - Device Fault) Field size: 1 character
Messages
Valid range: See description Description: If the status descriptor = 8, this field identifies device reporting abnormal status of following devices: D E F G H V \ - card reader/writer - cash dispenser - deposit - receipt printer - journal printer - statement printer - envelope dispenser
See section Solicited Status (device fault) on page 331 for detailed description of status information. MAC data field Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the transaction request message. See the section Message Authentication (MAC) on page 199 for additional details.
222
October 2004
U25604-J-Z745-1-7600
Messages
Unsolicited Status messages

This message is transmitted to the network when a change of status occurs at the terminal. Maximum length is 256 characters. The following table contains the status fields of unsolicited messages:
Table 57: Unsolicited Status message
Description solicited/unsolicited ID message identifier field separator (FS) logical unit number (LUNO) field separator (FS) field separator (FS) status information
Code 1 2 :1C --:1C :1C ---
No. of Characters 1 1 1 3 or 9 1 1 VAR
The following paragraphs describe the fields in the unsolicited status message. Solicited/unsolicited message field Field size: 1 character
Valid range: 1-2 Description: This field tells the network whether the message is solicited or unsolicited. The valid entries for this field are as follows: 1 - unsolicited message 2 - solicited message In the case of the Unsolicited Status message, this field will be 1.
U25604-J-Z745-1-7600
October 2004
223
Messages from Terminal to Network Message identifier field Field size: 1 character
Messages
Valid range: 2 Description: This one-character data field defines the type of message being transmitted. The only valid value for the unsolicited status message is 2. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See chapter Security Features from page 175 for additional details. Status information Field size: Variable
Valid range: See description Description: This field contains the device identifier and device status information. For details of this field, refer to section Unsolicited Device Status on page 335 of NDC device status.
224
October 2004
U25604-J-Z745-1-7600
Messages
Network to Terminal messages

There are three basic message types transmitted from the network to the terminal. 1. Transaction Reply command (message ID 4) 2. Terminal command (message ID 1) 3. Load command (message ID 3)
See the following figure for an overview. There are several download commands used in communications between network and terminal. States, Screens, FITs, and terminal configuration data download commands are part of configuration data during terminal startup. Load commands can be sent as interactive transaction responses that are used during system operation to satisfy transaction requests. Encryption Key Load commands are used during terminal startup (or for dynamic key exchange used by some customers) to load new encryption keys. The Configuration ID Number Load command is used to change the configuration ID after terminal startup and whenever new configuration data is sent to the terminal.
Figure 4: Network to terminal commands
Network to terminal messages
Load commands
TERMINAL
Transaction Reply commands
HOST
Terminal commands
U25604-J-Z745-1-7600
October 2004
225
Messages
Transaction Reply command (message ID 4)

The Transaction Reply command message is sent to the terminal in response to a Transaction Request message. Two conditions must be fullfilled for the transmission of the Transaction Reply command message to the terminal.
q
The customer has entered all the required data for a specific transaction request. The request has been sent to the network.
The Transaction Reply command acts as an authorization to the terminal to complete the transaction. The Transaction Reply command message is restricted to a length of 600 characters. It is prohibited to transmit a Transaction Reply command message without the end of text character. Table 58: Transaction Reply command message on page 226 lists the fields of the Transaction Reply command message. The paragraphs following the tables describe the fields in the Transaction Reply command message.
Table 58: Transaction Reply command message
Description Transaction Reply command identifier response flag field separator (FS) logical unit number (LUNO) field separator (FS) message sequence number field separator (FS) next state ID (000-254, 256-999) field separator (FS) number of bills to dispense group separator (GS) number of coins to dispense field separator (FS) transaction serial number function identifier screen number (010-999)
Code 4 [X] :1C [X] :1C [X] :1C [---] :1C [---] [:1D] [---] :1C ----[---]
No. of Characters 1 1 1 3 1 3[1] 1 3 1 VAR not used not used 1 4 1 3
226
October 2004
U25604-J-Z745-1-7600
Messages
Description screen display update data field separator (FS) message coordination number card return/retain flag printer flag (0 - 4) (8) printer data group separator (GS) printer flag (0 - 4) printer data group separator (GS) printer flag (0 - 4) printer data group separator (GS) [2] printer flag (0 - 4) printer data
[2] [2]
Code [---] :1C --------[:1D] [---] [---] [:1D] [---] [---] [:1D] [---] [---] :1C [4] [---] :1C [E] [---] [---] [---] [---] [---] [---] [---] [---] [---]
No. of Characters VAR 1 1 1 1 VAR (580 max) 1 1 VAR 1 1 VAR 1 1 VAR 1 1 VAR (106 max) 1 not supported not supported not supported not supported not supported not supported not supported not supported not supported not supported
field separator (FS) buffer identifier (4) track 3 data field separator (FS) buffer identifier (E) document destination lift front/rear image(s) archive lifted front/rear image(s) lift zones in image list archive lifted image list zones check magnetism check zone verification report candidates/identify document entry retries
U25604-J-Z745-1-7600
October 2004
227
Messages
Description field separator (FS) buffer identifier (F) document enable code group separator (GS) document name track 1 buffer identifier (K) track 1 data track 2 buffer identifier (L) track 2 data field separator (FS) MAC data
Code [:1C] [F] [---] [:1D] [---] K [---] L [---] [:1C] [---]
No. of Characters 1 [3] not supported not supported not supported not supported 1 VAR (max 78) 1 VAR (max 39) 1 [3] 8 [3]
[1] If message authentication is used, the three-byte message sequence number is replaced by an eight-byte time variant number, and the optional field separator and MAC data are included in the message. [2] This fields can be repeated up to nine further times. [3] This group of fields (FS/MAC Data) is used only when MAC is configured. The following paragraphs describe the fields in the State Table Load command message.
The following paragraphs describe the fields in the Transaction Reply command message. Message identifier field Field size: 1 character
Valid range: 4 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Transaction Reply command message is 4.
228
October 2004
U25604-J-Z745-1-7600
Messages Message sequence number Field size: 3 characters
Valid range: 000-999 Description: The message sequence number field is part of the logical protocol in a network message. It is a reserved entry and contain any three-digit decimal number (000-999). If the terminal uses MACing, this field is replaced by an eight-byte Time Variant Number. See chapter Security Features from page 175 for details. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See chapter Security Features from page 175 for additional details. Next state ID data field Field size: 3 characters
Valid range: 000-511 Description: This three-character data field contains a decimal number from 000 to 511 in three bytes of graphic code. This field defines the state number which the terminal should execute after the normal completion of the specified Transaction Reply command. Number of bills to dispense Field size: Variable
Valid range: See description Description: This field contains the two digit number of bills to dispense for logical cassette type 1 through 4. If the number of bills requested by the host are higher than the cash dispenser is able to dispense in one bundle, the terminal responds with a command reject or a specific command reject.
U25604-J-Z745-1-7600
October 2004
229
Network to Terminal messages Transaction serial number Field size: 4 characters
Messages
Valid range: 0000-9999 Description: The transaction serial number data is four characters of graphic code which identify the transaction to the network. This number originates at the network when a transaction request message is received. The depository printer prints this number on the deposit envelope. Function identifier field Field size: 1 character
Valid range: See description Description: The contents of this one-character data field instruct the terminal as to what functions it is to perform. The valid characters are listed as follows: Function ID 1 or 7 2 or 8 3 or 9 4 Short description of the function instructs a deposit + print instructs a dispense + print instructs a display + print instructs a print immediate. A graphic 4 instructs the terminal to print the information sent down-line to the terminal. This function ID is often used when the operator requests to balance the terminal. instructs a set next state + print. A graphic 5 instructs the terminal to print the information sent down-line to the terminal; the terminal proceeds to the next state defined in the Transaction Reply command. This function ID is often used when the consumer requests an inquiry, when a transaction is disallowed, or for any print operation. Night safe deposit and print eject card and dispense and print (card before cash) card before parallel dispense and print instructs a print statement and wait parallel dispense and print and card eject Print statement and next state
6 A F P B or C Q
230
October 2004
U25604-J-Z745-1-7600
Messages Screen number Field size: 3 characters
Valid range: 000-999 Description: This field contains three decimal digits of graphic code which represent numbers from 010 to 999. This number indicates one of 989 screens to be displayed on the screen during execution of the Transaction Reply command. This field is used for dispense, deposit and deliver instructions. Screen display update Field size: Variable
Valid range: See description Description: This variable-length field contains screen numbers and new screen data which can replace existing screen data. The new screen data can be displayed when this screen number is referenced during transaction processing. The screen update data have the following format: No. of Bytes 3 VAR 1 3
[1] [1] [1]
Content screen number screen data group separator screen number screen data
VAR
[1] These fields are repeated if multiple screens are updated within one reply message.
U25604-J-Z745-1-7600
October 2004
231
Network to Terminal messages Message coordination number Field size: 1 character
Messages
Valid range: ASCII 31-3F (or extended range 31-7E) Description: This is a character assigned by the terminal to each transaction request message. The terminal assigns a different coordination number to each successive transaction request on a rotating basis. The valid range for the coordination numbers is graphic 1 through 9, :, I ;, <" =, , >, and ? (ASCII 31 through 3F). If the extended range for the message coordination number field is enabled (Enhanced Configuration Parameters Load message), the valid range is ASCII 31 trough 7E. The host or controller must include the corresponding coordination number when responding with a transaction reply message. If the coordination numbers do not match, the terminal sends a solicited status message with a command reject status. A graphic 0 overrides the message coordination number. As a result, the terminal cannot verify that the transaction authorization corresponds to the last consumer message. Card return/retain flag field Field size: 1 character
Valid range: 0-1 Description: This one-character field instructs the terminal to either return or retain the customers account card during the close state. The valid values are as follows: 0 - return card 1 - retain card
232
October 2004
U25604-J-Z745-1-7600
Messages Printer flag field Field size: 1 character
Valid range: 0-3 Description: This one-character field tells the terminal which printer or printers to use. The valid graphic characters for this field are as follows: 0 - do not print 1 - print on journal printer only 2 - print on customer printer only 3 - print on both printers 4 - print on deposit if function ID is 1 or 7. 8 - print on statement printer only
Printer data field Field size: Variable (580 characters maximum)
Valid range: See description Description: This is a variable-length data field with a maximum of 580 characters. Inserted data is printed by the printer indicated in the printer flag field. Track 3 buffer identifier Field size: 1 character
Valid range: 4 Description: This one-character track 3 buffer identifier field tells the terminal that track 3 data follows in the buffer data field. Track 3 data Field size: Variable (106 characters maximum)
Valid range: See description Description: This field contains the data to be written onto track 3 as instructed by a Transaction Reply command. This data replaces any data previously located in the track 3 buffer of the terminal. The track 3 data consists of up to 106 characters including the start and end sentinels.
U25604-J-Z745-1-7600
October 2004
233
Network to Terminal messages Track 1 buffer identifier Field size: 1 character
Messages
Valid range: K Description: This one-character buffer identifier field tells the terminal that track 1 data follows in the buffer data field. Track 1 data Field size: Variable (78 characters maximum)
Valid range: See description Description: This field contains the data to be written to track 1. This data replaces any data previously located in the track 1 buffer of the terminal. The track 1 data consists of up to 78 characters including the start and end sentinels. Track 2 buffer identifier Field size: 1 character
Valid range: L Description: This one-character buffer identifier field tells the terminal that track 2 data follows in the buffer data field. Track 2 data Field size: Variable (39 characters maximum)
Valid range: See description Description: This field contains the data to be written to track 2. This data replaces any data previously located in the track 2 buffer of the terminal. The track 2 data consists of up to 39 characters including the start and end sentinels. MAC data field Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the transaction request message. See chapter Security Features from page 175 for additional details.
234
October 2004
U25604-J-Z745-1-7600
Messages
Terminal Command message

This message is transmitted by the network to startup or shutdown the terminal, or to request a configuration ID. Table 59: Terminal Command message on page 236 shows the format of the Terminal Command message. The following paragraphs describe each Terminal Command message type. Startup When the terminal is powered on the first time, all configuration data from the host must be downloaded to the terminal. This requires a startup sequence that loads the ProCash/NDC or ProConsult/NDC frameworks with a predefined configuration from the WIN-NT Registry. In the next step the terminal is ready to receive download commands from the host. The startup command can also put the terminal into service after shutdown or exit from maintenance mode. Shutdown This is an Terminal Command message from the network that places the terminal temporarily out-of-service. All pending messages are sent and current transactions completed, before the terminal executes the shutdown. The terminal then indicates that it has successfully completed the shutdown procedures by sending a ready status in a solicited status message. Configuration information request This Terminal Command message requests the terminal to send a solicited status message containing configuration information.
U25604-J-Z745-1-7600
October 2004
235
Messages
The following table shows the fields of the Terminal Command message:
Table 59: Terminal Command message
Description Terminal Command identifier response flag field separator (FS) logical unit number (LUNO) field separator (FS) message sequence number field separator (FS) command code
Code 1 [X] :1C [X] :1C [X] :1C ---
No. of Characters 1 1 1 3 1 3 1 1
The following paragraphs describe the fields in the Terminal Command message. Message identifier Field size: 1 character
Valid range: 1 Description: This one-character data field defines the type of message being transmitted. The only valid value for Terminal Command messages is 1. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See section Message Authentication (MAC) on page 199 for additional details.
236
October 2004
U25604-J-Z745-1-7600
Valid range: 000-999 Description: The Message Sequence Number field is part of the logical protocol in a network message. It is a reserved entry and contain any three-digit decimal number (000-999). If the terminal uses MACing, this field is replaced by an eight-byte Time Variant Number. See chapter Security Features from page 175 for details. The Message sequence number is ignored by ProCash/NDC and ProConsult/NDC. Command code Field size: 1 character
Valid range: See description Description: This one-character field is used to identify the type of command. The valid values for this field are as follows: 1 - Go in service to customers (startup). 2 - Go out-of-service to customers (shutdown). This code includes a modifier. This modifier is the number of the screen to be displayed when the terminal goes out of service. If no modifier is included, the default out-of-service screen is displayed. The defined values for the modifier are: 0 - display Out of Service screen (C02) 1 - display Temporary Out of Service screen (C06) 4 - Send Supply Counters. The host requests the Supply counters. The ATM responds with a Terminal State message (Status Descriptor F, Message Identifier 2). See also section Solicited Status (terminal state) on page 303. 5 - Send Tally Information (not supported) 6 - Send Error Log Information. The Send Error Log command asks the terminal to send the error log information for the device groups specified by the Device Identifier. (Status Descriptor F, Message Identifier 4). See also section Solicited Status (terminal state) on page 303.
U25604-J-Z745-1-7600
October 2004
237
Messages
7 - Send Configuration Information. The host requests Configuration ID, Hardware Status, and Sensor Status. The ATM responds with a Terminal State message (Status Descriptor F, Message Identifier 1). See also section Solicited Status (terminal state) on page 303. 8 - Send Date and Time information (Status Descriptor F, Message Identifier 5), see section Solicited Status (terminal state) on page 303. Command modifier Field size: 1 character
Valid range: See description Description: This field must be present for command code 6. For command code 7 this field is optional.
Error Log Information (Command code 6) Modifier A B C NOTE: Description Processor and system High order communications SST devices
In ProCash/NDC or ProConsult/NDC the solicited status response for modifier A and B is the same as for modifier C.
Configuration Information (Command code 7) Modifier 1 2 3 4 5 6 7 Description Send hardware configuration only Send supplies data only Send fitness data only Send tamper and sensor status data only Send software ID and release number data only Send enhanced configuration data Send local configuration option digits
238
October 2004
U25604-J-Z745-1-7600
Messages
State Tables Load

This type of message is used to load state tables to the terminal. The maximum message length for this command is 2000 characters. Each message contains a portion of the state tables. The following paragraphs describe the fields that can be included in the State Tables Load command message.
Table 60: State Tables Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration) Modifier (states) Field separator (FS) State number State data Field separator (FS) State number State data Field separator (FS) MAC data
Code 3 [X] :1C [X] :1C [X] :1C 1 2 [:1C] ----[:1C] [---] [---] [:1C]
No. of Characters 1 1 1 3 1 3 1 1 1 1 3 25 1 [1] 3 [1] 25 [1] 1 [2] 8 [2]
[1] This group of fields (FS/state number/state data) can be repeated, as necessary, to a maximum of 600 bytes per State Tables Load command message. [2] This group of fields (FS/MAC Data) is used only when MAC is configured. The following paragraphs describe the fields in the State Tables Load command message.
U25604-J-Z745-1-7600
October 2004
239
Messages
The following paragraphs describe the fields in the State Tables Load command message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for a download command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. Message sequence number Field size: 3 characters
Valid range: 000-999 Description: The message sequence number field is part of the logical protocol in a network message. It is a reserved entry and contain any three-digit decimal number (000-999). Load identifier Field size: 1 character
Valid range: 1 Description: This one-character data field tells the terminal that configuration data follows. The valid value is 1.
240
October 2004
U25604-J-Z745-1-7600
Messages Modifier field Field size: 1 character
Valid range: 2 Description: This one-character field identifies the configuration data to follow as state table data. The valid value is 2. State number Field size: 3 characters
Valid range: 000-254, 255-999 Description: This is a three-character field from 000 to 254 and 255-511. It identifies the state number for the state data that follows. State data Field size: Variable
Valid range: See description Description: The first entry identifies the state type. The rest of the characters are associated state data.
State number, state data, and field separator fields can be repeated as required to a maximum of 2000 bytes (total message length). MAC data field Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the transaction request message. See section Message Authentication (MAC) on page 199 for additional details.
U25604-J-Z745-1-7600
October 2004
241
Messages
Screen Data Load

This type of message is used to download screen configuration data to the terminal where the data are stored in the WIN-NT registry sub section ..\LYNXCI\SCREEN.
Table 61: Screen Data Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration) Modifier (screens) Field separator (FS) Screen number Screen data
Code 3 [X] :1C [X] :1C [X] :1C 1 1 :1C -----
No. of Characters 1 1 1 3 1 3 1 1 1 1[1] 3[1] VAR[1]
[1] This group of fields can be repeated, as required, to a maximum of 2000 bytes per Screen Data Load command message.
242
October 2004
U25604-J-Z745-1-7600
Messages
The following paragraphs describe the fields in the Screen Data Load command message. Load Command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Screen Data Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See section for additional details. Message sequence number Field size: 3 characters
U25604-J-Z745-1-7600
October 2004
243
Network to Terminal messages Modifier field Field size: 1 character
Messages
Valid range: 1 Description: This one-character field identifies the configuration data to follow as screen data. The valid value is 1. Screen number Field size: 3 characters
Valid range: 000-999 Description: This is a three-character field that identifies the screen number for the screen data that follows. Screen data Field size: Variable
Valid range: See description Description: The variable-length screen data field represents the data to be shown on the screen. This field always follows a screen number entry. Screen numbers, screen data, and field separator fields can be repeated as required to a maximum of 2000 bytes (total message length).
244
October 2004
U25604-J-Z745-1-7600
Messages
Configuration Parameters Load

The Configuration Parameters Load command message configures terminal parameters, the LUNO and terminal timers. The format of the Configuration Parameters Load message is shown in Table 62: Configuration Parameters Load on page 245. This message down-line loads the logical unit number (LUNO), parameters and timers into the WIN-NT Registry. This configuration message should be used first after a power-up because it defines the LUNO and communications timers. The following table contains field definitions of the Configuration Parameters Load command message:
Table 62: Configuration Parameters Load
Description Load Command Identifier Response Flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration) Modifier (parameters+LUNO+timers) Field separator (FS) Camera control Card reader error threshold Reserved Reserved Track 3 write error threshold Optional parameters Reserved Reserved Reserved
Code 3 [X] :1C [X] :1C [X] :1C 1 3 :1C X --000 000 X --000 000 000
No. of Characters 1 1 1 3 1 3 1 1 1 1 1 (not supported) 3 3 3 3 (not supported) 3 3 3 3
U25604-J-Z745-1-7600
October 2004
245
Messages
Description Field separator (FS) Logical unit number (LUNO) Field separator (FS) Timer number Number of ticks Timer number Number of ticks
Code :1C [X] :1C ----[---] [---]
No. of Characters 1 3 1 2 3 2[1] 3[1]
[1] This field can be repeated with the number of timers that are requested to be loaded.
The following paragraphs describe the fields in the Configuration Parameters Load message. Load Command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Configuration Parameters Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
246
October 2004
U25604-J-Z745-1-7600
Valid range: 1 Description: This one-character data field tells the terminal that configuration data follows. The valid value is 1. Modifier field Field size: 1 character
Valid range: 3 Description: This one-character field identifies the configuration data to follow as LUNO, parameters and timer data. The valid value is 3. Optional Parameters Field size: 3 characters
Valid range: 000-255 Description: The value in the optional parameters field is the sum of the weights of the selected features. Weight 008 002 001 Features 12 digit amount buffer size automatic return to previous mode separate ready (B) response to transaction reply
U25604-J-Z745-1-7600
October 2004
247
Network to Terminal messages Timer number Field size: 2 characters
Messages
Valid range: 00-20 Description: This two character field contains the timer number. See section Timer Data on page 167 for details on timers. The valid values are as follows: 00 keyboard response time-out interval 01 consumer response extension time-out interval 02 close state screen time-out interval 03 communication message time-out interval 04 envelope insertion time-out interval (depositor) 05 withdrawal time-out interval 06 communications off-line time-out interval 07 withdrawal shutter open time-out interval 08 not used 09 consumer time-out interval before card capture attempt 10 additional cash present time-out interval 11 vandal shield timer 82-83 not used 86 rear settlement time-out interval 87 not used 88-90 reserved 91-93 not used 94 envelope eject time-out interval 95 Statement retract time-out interval 96 Statement present time-out interval 97 vestibule door open time-out interval 98 reserved 99 vandal close timer Number of ticks Field size: 3 characters
Valid range: 000-255 Description: This three-character decimal data field determines the time-out intervals for the timers in 800 millisecond ticks. The number of ticks can be 000-255; this gives a time-out range from 0 - 204 seconds. Timer number and number of ticks fields can be repeated as required. Any timers with default values may be, but do not have to be, downline loaded.
248
October 2004
U25604-J-Z745-1-7600
Messages
Enhanced Configuration Parameters Load

The Enhanced Configuration Parameters Load command message (modifier A) contains additional options and parameters which are not included in the Configuration Parameters Load command message (modifier 3).
Table 63: Enhanced Configuration Parameters Load
Description Load Command Identifier Response Flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration) Modifier (parameters+LUNO+timers) Field separator (FS) Logical unit number (LUNO) Field separator (FS) Option number Option code Option number Option code Field separator (FS) Timer number Number of seconds Timer number Number of seconds
Code 3 [X] :1C [X] :1C [X] :1C 1 A :1C --:1C ----[---] [---] :1C ----[---] [---]
No. of Characters 1 1 1 3 1 3 1 1 1 1 3 1 2 3 2 3 1 2 3 2[1] 3[1]
[1] This field can be repeated with the number of timers that are requested to be loaded.
U25604-J-Z745-1-7600
October 2004
249
Messages
The following paragraphs describe the fields in the Enhanced Configuration Parameters Load command message. Load Command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Enhanced Configuration Parameters Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See section Message Authentication (MAC) on page 199 for additional details. Message sequence number Field size: 3 characters
250
October 2004
U25604-J-Z745-1-7600
Messages Modifier field Field size: 1 character
Valid range: A Description: This one-character field identifies the configuration data to follow as LUNO, parameters and timer data. The valid value is A. Logical Unit Number (LUNO) Field size: 3 characters
Valid range: 000-999 Description: This three-character field defines the three-character LUNO number. Option number Field size: 2 characters
Valid range: 00-99 Description: This two-character field defines the option number of the threecharacter option code. See Table 64 Option codes for detailed description of these codes.
Table 64: Option codes
Option number Option code Description
00 01 000 001 002 008 02 001 002 03 001 002 04 001-040
Camera Control (not supported) Ready/Supply options

No options selected (not supported) Separate READY (B) status sent in response to Transaction Reply Auto return to previous mode from supply mode (not supported) 12 digit amount buffer
Auto Voice on (default) Auto Voice off Date format for supervisor/journal messages
MMDD(YY) DDMM(YY)
Roll width. Defines the number of receipt and journal columns used to print messages from the host. (Default is 025)
U25604-J-Z745-1-7600
October 2004
251
Messages
05 06
001-040
Left print column (Defines the leftmost print column for receipt and journal messages. Default is 008) Vandal Guard Open Condition
000 001 07 001 002 08 09 10 11 12 000 001 13 14 15 000 001 16-17 18-20 21-22 23 000 001 24-28, 30 31 000 001 32-33 34 000 001 35-49 50-99 001-255
Open vandal guard when card detected (default condition) Open vandal guard when keyboard is enabled
Track 1 format
ISO format (default condition) VISA format
Reserved for future use Diebold status reporting for vandal guard (not supported) Tamper Indicator Control option (not supported) Extended status control (not supported) Specific Command Reject option
Do not transmit Specific Command Reject (default condition) Transmit Specific Command Reject
Card reader error thresholds (Default value is 010) Track 3 write error thresholds Last Transaction Status information
Do not append information (default condition) Append information
Not supported by ProCash/NDC Codes reserved for future use Not supported by ProCash/NDC Envelope dispenser status option
Do not send unsolicited envelope dispenser messages (default) Send unsolicited envelope dispenser messages
Not supported by ProCash/NDC Enable Audio Echo on Keyboard

Do not echo the keyboard (default condition) Echo the keyboard,except in PIN states or/and when * is pressed
Codes reserved for future use Message Coordination Number range. Default range is 31(Hex) - 3F(Hex). This parameter allows to extend the MCN range up to 7E(Hex).
31H - 3FH (default condition) 31H - 7EH
Codes reserved for future use Codes reserved for private use
252
October 2004
U25604-J-Z745-1-7600
Messages Timer number Field size: 2 characters
Valid range: 00-20 Description: This two character field contains the timer number. See section Timer Data on page 167 for details on timers. The valid values are as follows: 00 keyboard response time-out interval 01 consumer response extension time-out interval 02 close state screen time-out interval 03 communication message time-out interval 04 envelope insertion time-out interval (depositor) 05 withdrawal time-out interval 06 communications off-line time-out interval 07 withdrawal shutter open time-out interval 08 not used 09 consumer time-out interval before card capture attempt 10 additional cash present time-out interval 11 vandal shield timer 82-83 not used 86 rear settlement time-out interval 87 not used 88-90 reserved 91-93 not used 94 envelope eject time-out interval 95 Statement retract time-out interval 96 Statement present time-out interval 97 vestibule door open time-out interval 98 reserved 99 vandal close timer Number of seconds Field size: 3 characters
Valid range: 000-255 Description: This three-character decimal data field determines the time-out intervals for the timers in seconds. The number of seconds can be 000-255. Timer number and number of seconds fields can be repeated as required. Any timers with default values may be, but do not have to be, down-line loaded.
U25604-J-Z745-1-7600
October 2004
253
Messages
Interactive Transaction Response

This message may be sent in response to a Transaction Request in order to obtain more information from the cardholder. This facility allows Central to communicate directly with the keyboard and display in those situations where state table sequencing is inappropiate. For example, a cardholder account selection can be handled in this way. Central can establish which accounts are available to the cardholder and build the screen accordingly. The message defines screen data and active keys. Key data is returned in a Transaction Request message. After the Interactive Transaction Response message, the terminal waits for a consumer response or time-out. When an FDK or cancel key is pressed or the screen timer expires, the terminal responds with a Transaction Request message containing key data usually in general purpose buffer B.
Table 65: Interactive Transaction Response
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (ITR) Display flag Active keys Field separator (FS) Screen timer Field separator (FS) Screen data
Code 3 [X] :1C [X] :1C [X] :1C 2 ----:1C --:1C ---
No. of Characters 1 1 1 3 1 3 1 1 1 6, 10 1 3 1 VAR
The following paragraphs describe the fields in the Interactive Transaction Response command message.
254
October 2004
U25604-J-Z745-1-7600
Messages Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Interactive Transaction Response command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: See description Description: This three-character data field is defined in the configuration data transmitted to the terminal. If a machine number is entered, this field will contain nine characters with the last six characters of this field being the terminal number. See chapter Security Features from page 175 for additional details. Message sequence number Field size: 3 characters
Valid range: 2 Description: This one-character data field tells the terminal that screen data of an ITR follows. The valid value is 2.
U25604-J-Z745-1-7600
October 2004
255
Network to Terminal messages Display flag Field size: 1 character
Messages
Valid range: 0-2 Description: This one-character field instructs the terminal display as follows: 0 - display Xs as consumer response 1 - display consumer response 2 - display Xs as consumer response. (NCR displays *) The keyed response is stored in general purpose buffer B for later transmission in a Transaction Request message. Active keys Field size: 6 or 10 characters
Valid range: 0-1 Description: This 10-character field either activates or deactivates keyboard keys for consumer responses. A graphic 0 will deactivate, while a graphic 1 will activate, the selected key(s) as follows:
Character first second third fourth fifth sixth seventh eighth ninth tenth
Declaration selects all numeric keys selects FDK A selects FDK B selects FDK C selects FDK D selects the Cancel key selects FDK F selects FDK G selects FDK H selects FDK I
256
October 2004
U25604-J-Z745-1-7600
Messages Screen timer Field size: 3 characters
Valid range: 000-255 Description: This three-character field determines time-out intervals for the CRT display. Graphic characters represent 001 to 255 800millisecond ticks to give a time-out range from 0.8 to 204 seconds. If the terminal "timed out" waiting for the consumer to respond (via keyboard entry) to a screen command, the last character in general purpose buffer B is T. Entering 000 gives an infinite display time. Screen data Field size: Variable
Valid range: See description Description: This is a variable-length field which represents data to be displayed on the consumer screen.
U25604-J-Z745-1-7600
October 2004
257
Messages
FIT Data Load

This type of message down-line loads Financial Institution Tables (FIT's) to the terminal. Each message can include up to four tables. The terminal can store up to 1000 FIT's. One FIT is required for each member financial institution. Refer to chapter Security Features from page 175 for details on FIT. Table 66: FIT Data Load on page 258 illustrates the message format. The following paragraphs describe the message fields.
Table 66: FIT Data Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration) Modifier (FIT) Field separator (FS) FIT number FIT data (38 bytes) Field separator (FS) FIT number FIT data (38 bytes) Field separator (FS) MAC data
Code 3 [X] :1C [X] :1C [X] :1C 1 5 :1C ----[:1C] [---] [---] [:1C] [---]
No. of Characters 1 1 1 3 1 3 1 1 1 1 3 114 1 [1] 3 [1] 114 [1] 1 8
[1] This group of fields (FS/FIT number/FIT data) can be repeated, as required, to a maximum of four FIT's per FIT Data Load command message.
The following paragraphs describe the fields in the FIT Data Load command message.
258
October 2004
U25604-J-Z745-1-7600
Messages Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the FIT Data Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: 1 Description: This one-character data field tells the terminal that configuration data follows. The valid value is 1. Modifier field Field size: 1 character
Valid range: 5 Description: This one-character field identifies the configuration data to follow as FIT data. The valid value is 5.
U25604-J-Z745-1-7600
October 2004
259
Network to Terminal messages FIT number Field size: 3 characters
Messages
Valid range: 000-509 Description: This three-character field designates the number assigned to the FIT in the following field. FIT data Field size: 38 bytes
Valid range: See description Description: The FIT data specifies control words for processing the PIN. FIT is also used for indirect next state and remote PIN encryption. FIT is down-line loaded to the terminal. MAC data Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the FIT Data Load command message. Refer to section Message Authentication (MAC) on page 199 for additional details.
260
October 2004
U25604-J-Z745-1-7600
Messages
Encryption Key Load

The Encryption Key Load message carries encrypted encryption keys to replace the current keys. This message also includes a control word (in the modifier field) that identifies the key in the message and the means of decrypting it (see chapter Security Features from page 175 for a detailed description of data encryption). The Encryption Key Load message can be used only for single lengths keys (24 characters). For double lengths keys (48 characters), the Extended Encryption Key Load message has to be used. Table 67: Encryption Key Load on page 261 illustrates the message format.
Table 67: Encryption Key Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Key change Field separator (FS) New key data
Code 3 [X] :1C [X] :1C [X] :1C [---] :1C [---]
No. of Characters 1 1 1 3 1 3 1 1 1 1 24
Load identifier (encryption key change) 3
U25604-J-Z745-1-7600
October 2004
261
Messages
The following paragraphs describe the fields in the Encryption Key Load message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Encrypion Key Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: 3 Description: This one-character data field tells the terminal that encryption key data follows. The valid value is 3.
262
October 2004
U25604-J-Z745-1-7600
Messages Key change Field size: 1 character
Valid range: 1-9 Description: This one-character field tells the terminal what key(s) to use for encryption and message authentication. The valid values for this field are as follows: 1 - decrypt new master key with current master key 2 - decrypt new COMM key with current master key 3 - decrypt new COMM key with current COMM key 4 - use power-up COMM key (B key) as current COMM key 5 - decrypt MAC key with current master key 6 - decrypt MAC key with current COMM key 7 - use power-up COMM key (B key) as current MAC key 8 - decrypt new VISA master key with current VISA master key (not supported by Wincor Nixdorf terminals) 9 - send VISA key table to terminal (not supported by Wincor Nixdorf terminals) New key data Field size: Variable
Valid range: See description Description: The terminal receives, decrypts and stores new key data inputs for future use. The size of this field varies, depending on the key change field. The field sizes are as follows: If the key change field is 4 or 7, there is no new key data; this field is not included in the message. If the key change field is 1, 2, 3, 5, 6 or 8, the new key data field is 24 characters. It is eight hex bytes transmitted as eight 3 decimal characters with a range of 000-255.
U25604-J-Z745-1-7600
October 2004
263
Messages
Extended Encryption Key Load

The Extended Encryption Key Load message allows to carry encrypted encryption keys in double length (48 characters) or single length (24 characters) to replace the current keys. Double lengths keys usually are used if triple DES verification is enabled. This message also includes a control word (in the modifier field) that identifies the key in the message and the means of decrypting it (see chapter Security Features from page 175 for a detailed description of data encryption). If this message is sent with a single length key and the terminal is configured to work with double length keys, a command reject is issued indicating an Encryption Key Change message of the wrong length has been issued. Table 68 Extended Encryption Key Load illustrates the message format.
Table 68: Extended Encryption Key Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Key change Field separator (FS) Key data size New key data
Code 3 [X] :1C [X] :1C [X] :1C [---] :1C [---] [---]
No. of Characters 1 1 1 3 1 3 1 1 1 1 3 24 or 48
Load identifier (encryption key change) 4
264
October 2004
U25604-J-Z745-1-7600
Messages
The following paragraphs describe the fields in the Extended Encryption Key Load message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Extended Encrypion Key Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: 4 Description: This one-character data field tells the terminal that encryption key data in single length or double length follows. The valid value is 4.
U25604-J-Z745-1-7600
October 2004
265
Network to Terminal messages Key change Field size: 1 character
Messages
Valid range: 1-9 Description: This one-character field tells the terminal what key(s) to use for encryption and message authentication. The valid values for this field are as follows: decrypt new master key with current master key decrypt new COMM key with current master key decrypt new COMM key with current COMM key use power-up COMM key (B key) as current COMM key decrypt MAC key with current master key decrypt MAC key with current COMM key use power-up COMM key (B key) as current MAC key decrypt new VISA master key with current VISA master key (not supported by Wincor Nixdorf terminals) 9 - send VISA key table to terminal (not supported by Wincor Nixdorf terminals) Key data size Field size: 3 1 2 3 4 5 6 7 8 -
Valid range: 018 or 030 Description: The key data size specifies the size of the following key data field. For a single length key the size is 018 (24 characters). For a double length key the size is 030 (48 characters). New key data Field size: Variable
Valid range: See description Description: The terminal receives, decrypts and stores new key data inputs for future use. The size of this field varies, depending on the key change field. The field sizes are as follows: If the key change field is 4 or 7, there is no new key data; this field is not included in the message. If the key change field is 1, 2, 3, 5, 6 or 8, the new key data field is 24 characters for single length keys or 48 characters for double length keys (Triple DES mode). It is eight or sixteen hex bytes transmitted where the terminal receives each byte as a 3 digit decimal value in range of 000-255.
266
October 2004
U25604-J-Z745-1-7600
Messages
Dispenser Currency Mapping Table Load

This message contains a table that is used to define currency types, which is mapped to the configuration settings in table entry 7 of the Amount Check State defined in the Amount Check State Table. Table 69 Dispenser Currency Mapping Table Load illustrates the message format.
Table 69: Dispenser Currency Mapping Table Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration)
Code 3 [X] :1C [X] :1C [X] :1C 1
No. of Characters 1 1 1 3 1 3 1 1 1 1 VAR 2[1] 2[1]
Modifier (Dispenser Currency Mapping E Table) Field separator (FS) Dispenser Currency Mapping Table data Number of Mapping Entries (range 01-FF) Currency Type (range 01-FF) used for mapping to state G table entry 7 Cassette Type. Single digit ASCII hex value (range 0-F) Denomination for Cassette. Five-digit ASCII numeric value (e.g. 00010 for $10) :1C -------
-----
1[1] 5[1]
[1] If the Number of Mapping Entries a greater than 01, the following fields are repeated with the specified number of Mapping Entries
U25604-J-Z745-1-7600
October 2004
267
Messages
The Dispenser Currency mapping Table Load is expected at the terminal only when the terminal is in out-of-service mode or supply/supervisor mode. If Central transmits a Dispenser Currency mapping Table Load message and it does not conform to the format above, or is sent at a time when it is not expected, a solicited error message is generated, identifying a specific command reject value for the failure reason (or simply 'A' if specific command reject processing is not activated). If a specific command reject value is generated then the message content will be ignored.
See also section Amount Check State (G) on page 84 for detailed configuration description.
268
October 2004
U25604-J-Z745-1-7600
Messages
Configuration ID Load
This message contains an identifier for the configuration data sent to the terminal, i.e. the configuration data in a given terminal. At terminal startup, or any time that configuration data is sent to the terminal, the configuration ID is set to 0000. The Configuration ID Load command message must be included as the last of the down-line loaded configuration data to set the configuration ID to the desired number. Thus, the Configuration ID Load command message acts as an authorization signature for the preceding data. The configuration ID number can be any number from 0000 to 9999. After the terminal has received a new configuration ID all downloaded parameters are stored into the WIN-NT Registry. The Configuration ID can be used to verify configuration data. When properly configured, the WIN-NT Registry contains the configuration ID number assigned by the Configuration ID Load command message during configuration. To verify the configuration data, the network sends a configuration ID request terminal command (section Terminal Command message on page 235). The terminal responds by sending the configuration ID number to the network. If the configuration data has been changed without the authorization signature, the terminal had been powered down and has not been reconfigured, or if the encryption keys have been changed, the terminal sends 0000 to the network. The terminal can respond, as described above to the configuration ID request message only when it is in supply mode or out-of-service mode. When not in one of these conditions, the terminal responds with a command reject (section Specific Command Reject Conditions on page 280).
U25604-J-Z745-1-7600
October 2004
269

Table 70: Configuration IDLoad
Messages
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration data) Modifier (configuration ID number) Field separator (FS) Configuration ID number
Code 3 [X] :1C [X] :1C [X] :1C 1 6 :1C ---
No. of Characters 1 1 1 3 1 3 1 1 1 1 4
The following paragraphs describe the fields in the Configuration ID Load command message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Configuration ID Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
270
October 2004
U25604-J-Z745-1-7600
Valid range: 000-999 Description: The message sequence number field is part of the logical protocol in a network message. It is a reserved entry and contain any three-digit decimal number (000-999). If the terminal uses MACing, this field is replaced by an eight-byte time variant number. See chapter Security Features from page 175 for details. Load identifier Field size: 1 character
Valid range: 1 Description: This one-character data field tells the terminal that configuration data follows. The valid value is 1. Modifier Field size: 1 character
Valid range: 6 Description: This one-character field tells the terminal that the configuration data that follows is the configuration ID. The only valid value is 6. Configuration ID number Field size: 4 characters
Valid range: 0001-9999 Description: This four-character field contains the configuration ID Number. The configuration ID number must be in the range of 0001 to 9999. 0000 indicates that the terminal is not configured.
U25604-J-Z745-1-7600
October 2004
271
Messages
Date And Time Load

This message is used to set the date and time in the terminal.
Table 71: Date And Time Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration data) Modifier (configuration ID number) Field separator (FS) Date/Time data
Code 3 [X] :1C [X] :1C [X] :1C 1 C :1C VAR
No. of Characters 1 1 1 3 1 3 1 1 1 1 10
The following paragraphs describe the fields in the Date And Time Load command message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Date And Time Load command message is 3.
272
October 2004
U25604-J-Z745-1-7600
Messages Logical unit number (LUNO) Field size: 3 or 9 characters
Valid range: 1 Description: This one-character data field tells the terminal that configuration data follows. The valid value is 1. Modifier Field size: 1 character
Valid range: C Description: This one-character field tells the terminal that the configuration data that follows is the configuration ID. The only valid value is C.
U25604-J-Z745-1-7600
October 2004
273
Network to Terminal messages Date and time data Field size: 10 characters
Messages
Valid range: See description Description: The date and time specified by the is formatted as follows: YYMMDDHHMM. Description YY = Year MM = Month DD = Day HH = Hour MM = Minute Range 00 - 99 01 - 12 01 - 31 00 - 23 00 - 59
274
October 2004
U25604-J-Z745-1-7600
Messages
Message Authentication Field Selection Load

This type of message is used to set the messages and fields specified for full or selective MAC verification. The following paragraphs describe the message fields.
Table 72: Message Authentication Field Selection Load
Description Load command identifier Response flag Field separator (FS) Logical unit number (LUNO) Field separator (FS) Message sequence number Field separator (FS) Load identifier (configuration data) Modifier (configuration ID number) Field separator (FS) Transaction request field Field separator (FS) Transaction reply field Field separator (FS) Solicited status field Field separator (FS) Other messages field Field separator (FS) Track 1 field Field separator (FS) Track 2 field Field separator (FS) Track 3 field Field separator (FS) MAC data
Code 3 [X] :1C [X] :1C [X] :1C 1 B :1C VAR :1C VAR :1C --:1C VAR :1C VAR :1C VAR :1C VAR [:1C] [---]
No. of Characters 1 1 1 3 1 3 1 1 1 1 37 (only 17 supported) 1 23 (only 17 supported) 1 11 (not supported) 1 4 1 6 1 6 1 11 1 8
U25604-J-Z745-1-7600
October 2004
275
Messages
The following paragraphs describe the fields in the Message Authentication Field Selection Load command message. Load command identifier field Field size: 1 character
Valid range: 3 Description: This one-character data field defines the type of message being transmitted. The only valid value for the Message Authentication Field Selection Load command message is 3. Logical unit number (LUNO) Field size: 3 or 9 characters
276
October 2004
U25604-J-Z745-1-7600
Messages Modifier Field size: 1 character
Valid range: B Description: This one-character field tells the terminal that the configuration data that follows is the configuration ID. The only valid value is B. Transaction request field Field size: 0-37 (17 fields supported only)
Valid range: 0 or 1 (for each field) Description: The following table shows the fields which can be verified:
Field Position
Description
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
0 - MAC complete message; 1 - Selective MACing Solicited/Unsolicited ID and Message identifier Logical unit number Reserved Time variant number top-of-form flag Message coordination number Track 2 data Track 3 data Operation code data Amount entry field PIN buffer General Purpose Buffer B General Purpose Buffer C Track 1 data buffer identifier Track 1 data Transcation status Data identifier and Last transaction status
Transaction reply field Field size: 0-23 (17 supported only)
Valid range: 0 or 1 (for each field) Description: The following table shows the fields which can be verified:
U25604-J-Z745-1-7600
October 2004
277
Messages
Field Position
Description
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
0 - MAC complete message; 1 - Selective MACing Transaction Reply command identifier and response flag Logical unit number Message sequence number / Time variant number Next state ID Number of bills to dispense from denomination 1-4 Transaction serial number Function identifier Screen number Screen display update data Message coordination number Card return / retain flag Printer flag field and Printer data Printer flag field and Printer data after the first group separator Printer flag field and Printer data within the next group separators Track 3 buffer identifier Track 3 data field
Solicited status field Field size: 11
Valid range: 0 or 1 Description: This field contains the MAC selection data for the solicited status message. This field is ignored by the application. ProCash/NDC and ProConsult/NDC always performs a full MAC for solicited status messages. Other messages field Field size: 4
Valid range: 0 or 1 Description: This field conains the MAC selection data for FIT load, State Table load, Terminal State status and Dispenser Currency Mapping Table messages. MAC verification of Terminal State and Dispenser Currency Mapping Table messages are not supported.
278
October 2004
U25604-J-Z745-1-7600
Messages Track 1 field Field size: 6
Valid range: 0 or 1 Description: This field contains the MAC selection data for Track 1 data. Offset Description 0 0 - MAC full track. Ignore bytes 1-5 1 - Selectively MAC the fields below 1 Sub field 1 until = (including start sentinel) 2-5 Sub field 2-5 that should be MACed Track 2 field Field size: 6
Valid range: 0 or 1 Description: This field contains the MAC selection data for Track 2 data. Description Offset 0 0 - MAC full track. Ignore bytes 1-5 1 - Selectively MAC the fields below 1 Sub field 1 until = (including start sentinel) 2-5 Sub field 2-5 that should be MACed Track 3 field Field size: 11
Valid range: 0 or 1 Description: This field contains the MAC selection data for Track 3 data. Offset Description 0 0 - MAC full track. Ignore bytes 1-10 1 - Selectively MAC the fields below 1 Sub field 1 until = (including start sentinel) 2-10 Sub field 2-10 that should be MACed MAC data field Field size: 8 characters
Valid range: See description Description: This eight-character field contains hexadecimal characters that represent the MAC calculation of the Message Authentication Field Selection Load message. See the section Message Authentication (MAC) on page 199 for additional details.
U25604-J-Z745-1-7600
October 2004
279
Messages
Specific Command Reject Conditions

The terminal will return a specific command reject status if an error is detected in any command sent from the network to the terminal. The situations which cause a command reject are as follows:
q q q q q q q q q q
Illegal message class (legal classes are 1, 2, 3 or 4) Illegal message sub class Illegal message identifier Illegal terminal command code Illegal terminal command modifier Field separator in illegal position Insufficient fields in the message Insufficient Registry space to store configuration data The dispense amount request is to large The message coordination number in a Transaction Reply message does not match the number in the Transaction Request, and is not 0. Illegal function ID in Transaction Reply command. An illegal function ID is a non supported ID by ProCash/NDC or ProConsult/NDC. An encryption key change message is received before the original key has been entered at the terminal. More than 13 print fields in aTransaction Reply command Date and Time data are invalid in a date and time load command
q q
Default operations include the following:

q q q
Entry to default close state. For example , non existent state number Illegal characters for data convertion received Default display, for example if a screen does not exist the screen number is displayed on the consumer screen
280
October 2004
U25604-J-Z745-1-7600
Messages
The following table shows under which conditions the specific command reject value/qualifier combinations are produced:
Table 73: Specific Command Reject Conditions
Value Qualifier Description A Message format errors 01 Message length error. An incomplete message is found
under the following conditions: Report logs missing the group number Load of configuration ID incomplete or missing ID field. Diebold PIN mode message - missing or incomplete data. Option /timer - incomplete number/value field in configuration message Truncated MAC field selection load, with expected MAC data missing.
02 Field separator not found or found unexpectedly in the following circumstances:
Found in the middle of an option / timer number and value field in configuration message. Not found when skipping the first three field separators in a Transaction Reply message. Not found at the end of the coinage field. Not found in MAC Field Selection Load Data. Mandatory last field separator not found or found unexpectedly in a Transaction Reply message. Found unexpectedly in the Override Reserved Screen command. Too many print groups in the Transaction Reply message. More than 13 print groups are present in a Transaction Reply message. A group separator is missing or found unexpectedly.
03
04
U25604-J-Z745-1-7600
October 2004
281
Messages
B 01
Field value errors
02
Illegal Message Class. Message class was not 1, 2, 3, 4 or 7, or message class was 7 and exit support was not detected. Illegal Message Sub-Class or Identifier on a Configuration Load message with class '3' . The following will cause this report: Message sub-class outside the range '1' - '4'
03
Message identifier outside the range '1' - '6' or 'A' -'C'. Illegal Load Key Message Identifier. Within a load encryption key data message: The modifier field is outside the range '1' - '9' Illegal Terminal Command Code: Returned if the command code is outside the range '1' - '?'. Illegal Terminal Command Modifier. Within a legal terminal command, if a modifier is required: Report tallies modifier outside the range 'A' - 'N' or 'V' or 'Y' or '\' or'[' . Report error log modifier outside the range 'A'' - 'C' The terminal command code is 7 and the command modifier is outside the range 0-7.
04
05
06
The command code is '?' but the modifier is not 0 or 1. Illegal Function ID in Transaction Reply command: Function ID outside the range 'l'- '9', 'A', 'B', 'C', 'F', 'P', 'Q', 'S' or 'T' Data Field contains non-numeric data. This is found in the following circumstances: Encryption key change message key data. Coinage field has at least one non-numeric character present. Option/Timer number or value in configuration message.
07
282
October 2004
U25604-J-Z745-1-7600
Messages
08
Numeric value out of range. In a FIT message, FIT data value is greater than 255 message contain a value exceeding their maximum values. The zone name length in the printer fields of a Transaction Reply message is out of range. Invalid Message Co-Ordination Number. In a Transaction Reply message, the co-ordination number is not zero and does not match the transmitted value. Illegal FIT number. A FIT in a FIT load message is not in the range of the reserved pool size. Too many notes in Transaction Reply command. The total number of notes requested exceeds the limit of 40 or 20. Unrecognised document destination. Returned if the document destination (field in the the Transaction Reply) is not one of the allowed values or if the field is null. Too many coins in Transaction Reply command. Total number of coins requested exceeds the limit of 25. Unrecognised buffer identifier. Returned if the Transaction Reply contains a buffer identifier not currently supported. Buffer identifier 'E' missing. Returned if the Transaction Reply command ID is 'S' (Process Document with Cash) but there is no mandatory field 'ae' in the Transaction Reply message. Document name error. Returned if the data present in a printer field in the Transaction Reply message is shorter than the zone name length given. The screen identifier in an Override Reserved Screen Command is not in the range 'D0000' to 'D0010'. Illegal Message Type for Current Mode. Message type only accepted while terminal Is in In Service mode and is expecting a Transaction Reply. The reject is caused by receipt of a Transaction Reply at other times while the terminal is in service.
09
10 11 13
14 15
16
17
18 C 01
U25604-J-Z745-1-7600
October 2004
283
Messages
02
Message cannot be accepted while diagnostics and clear SOH programs for Level 2 and Level 3 are in progress. This reply is designed to draw attention to the fact that these programs are being executed. It applies to the following messages: Download messages for customisation.
03
Transaction Replies (not Print Immediate). Message cannot be accepted while in Out-of-Service or Supply modes. The following messages cannot be accepted in these modes: Transaction Replies (not Print Immediate).
04
Interactive Transaction Response. Message unacceptable in current mode. The following messages cannot be accepted while in InService mode: Terminal commands '4', '5', '6', '9'. Interactive Transaction Response when not in Transaction Request State. Also applies to terminal command when attempting to enable Supervisor 'Dump Images' but terminal is performing a transaction.
05 06 07 08 09 10 11 12 13 14
Reserved Reserved
Reserved Security key initialise message rejected. The key is already in a legal state.
Reserved
Message not accepted while processing a Transaction Reply.

not used
Cannot process a document while a statement print function is being carried out. Cannot perform a statement print function while processing a document.
not used
284
October 2004
U25604-J-Z745-1-7600
Messages
D 01 02 03 04 05 06 E 01
Hardware failure Encryption failure during key change message. Time of day clock failure during data/time set command or invalid data sent. Reserved Key initialisation command not accepted, due to encryption failure during initialisation. Reserved Insufficient disk space. Not supported Not supported by software:
The requested function is not supported by current ProCash/NDC or ProConsult/NDC release. VISA PIN verfication key table load via encryption key load message. MAC field selection load.
02 Not supported by hardware: A dispense function has been issued which requests coins but there is no Coin dispenser present. Sideways printing on receipt is requested and the option is not available. Reserved Reserved Journal printer backup is inactive
03 04 05
U25604-J-Z745-1-7600
October 2004
285

Figure 5: Transaction Reply message accept/reject flowchart
Network sends a Transaction Reply message or host generated screen to the terminal
Messages
Terminal in Terminal in inservice service mode? mode?
No
Yes
No
Terminal in Terminal in transaction transaction request request state? state?
Is message Is message a print a print immediate ? immediate ?
No
Yes
Yes
Process message
Yes
Terminal in Terminal in out--of--service out of service mode ? mode ?
No
Yes
Terminal in Terminal in supervisor mode and MISC_PRINT supervisor mode Flag is set to 8 ?
No
Reject message
286
October 2004
U25604-J-Z745-1-7600
Messages
Terminal operations in Transaction Replies

This section describes the operation of the terminal in response to Transaction Reply command messages. Each Transaction Reply command message identifies a particular function for the terminal to perform. How the terminal responds to each of these function identifiers is the subject of this section. The following table lists NDC function IDs and the assignment to the internal ProCash/NDC or ProConsult/NDC step function:
Table 74: NDC function IDs assigned to step functions
Function description Print Immediate Set Next State and Print Night Safe Deposit and Print Deposit and Print Dispense, Deliver and Print Display and Print
ID 4 5 6 1 or 7 2 or 8 3 or 9
Step function DC_F_PRINT_IMMEDIATE DC_F_SET_NEXT_STATE DC_F_NIGHT_SAFE_DEPOSIT DC_F_DEPOSIT DC_F_DISPENSE NDC_F_DISPLAY NDC_F_CBC_DISPENSE
Eject Card Dispense and Print A (Card Before Cash) Parallel Eject/Dispense and Print (Fast Cash)
B or C NDC_F_PARALLEL_DISPENSE NDC_F_CBC_PARALLEL NDC_F_PRINT_STM_NEXT NDC_F_PRINT_STM_WAIT DC_F_IGNORE
Eject Card Dispense and Print F Parallel Print Statement and Set Next State Q
Print Data and Stay in Present P State Ignore Reply Function
U25604-J-Z745-1-7600
October 2004
287
Messages
Print Immediate (4)

The terminal handles the Print Immediate function ID as follows: 1. Shows the screen specified in the Transaction Reply command message. 2. Initializes for printing. 3. Tells the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print. 4. If a fault occurs while the printer is printing the terminal sends a printer unsolicited status message indicating a fault.
Set Next State and Print (5)

The terminal handles the Set Next State and Print function ID as follows: 1. Initializes for printing. 2. Tells the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print. 3. If a fault occurs while the printer is printing, the terminal sends a printer unsolicited status message indicating a fault. 4. Initializes for printing. 5. Tells the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print. 6. If a fault occurs while the printer is printing, the terminal sends a printer unsolicited status message indicating a fault.
288
October 2004
U25604-J-Z745-1-7600
Messages
Night Safe Deposit and Print (6)

The terminal handles the Night Safe Deposit and Print function as follows: 1. Shows the screen specified in the Transaction Reply command message 2. Starts the Timer 08 and waits for the deposit to be completed. The deposit is completed when the deposit shutter has been safety closed.
q
If Timer 08 expires before the deposit is completed, the terminal starts timer 1 and shows screen 000. If timer 1 expires before the deposit is completed, the terminal sends a deposit solicited status message indicating a fault and waits for a new Transaction Reply command. If the cancel key is pressed while Timers 01 or 08 are active, the terminal sends a deposit solicited status message indicating a fault and waits for a new Transaction Reply command. If Timer 08 does not expire and the cancel key is not pressed while Timer 01 or 08 is active, the terminal goes to step 3.
3. Tells the journal and/or receipt printers defined in the printer flag field of the Transaction Reply command message to print. 4. If a fault occurs while the printer is printing, the terminal sends a printer unsolicited message indicating a fault.
Deposit and Print (1 or 7)

The terminal handles the Deposit and Print function ID as follows: 1. Shows the screen specified in the Transaction Reply command message. If the envelope should be given in the host replay, the screen please take the envelope will be displayed. 2. Starts Timer 04 (envelope insertion timer). 3. Checks for envelope insertion.
q
If Timer 04 expires before the customer inserts the envelope, the terminal starts timer 01 (consumer time-out response) and shows screen 000. If Timer 01 expires before the customer inserts the envelope, the terminal returns a depository solicited status message indicating a fault and waits for a new Transaction Reply command message.
U25604-J-Z745-1-7600
October 2004
289

q
Messages
If the cancel key is pressed while the terminal is checking for the insertion of the envelope, the terminal returns a depository solicited status message indicating a fault and waits for a new Transaction Reply command message. If an envelope is inserted, the terminal goes to step 5.
4. Initializes for envelope entry. 5. Transports the deposit envelope.

q
If a fault occurs during transport, the terminal returns a depository solicited status message indicating a fault and waits for a new Transaction Reply command message. If a fault does not occur, the terminal goes to step 7.
6. Increases the deposit envelope count by one. 7. Prints the transaction serial number, the contents of the amount buffer, and the first 20 characters of track 2 data on the envelope. 8. Initializes for finishing the deposit. 9. Waits for the deposit to finish.
q
If a fault occurs while the terminal is waiting for the deposit to finish, the terminal returns a depository solicited status message indicating a fault and waits for a new Transaction Reply command message. If a fault does not occur, the terminal checks for an additional function identifier in the Transaction Reply command message.
10. Initializes for printing. 11. Tells the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print. 12. If a fault occurs while the printer is printing the terminal returns a printer unsolicited status message indicating a fault.
290
October 2004
U25604-J-Z745-1-7600
Messages
Dispense, Deliver and Print (2 or 8)

The terminal handles the Dispense, Deliver and Print function ID as follows: 1. Shows the screen specified in the Transaction Reply command message. 2. Initializes for the dispense function. 3. Starts dispensing. 4. If a fault occurs during dispense, the terminal proceeds as follows.
q q
Returns a dispenser solicited status message indicating a fault . Waits for a new Transaction Reply command message.
5. Wincor Nixdorf retract able terminals proceeds as follows:

q q
Starts Timer 10 (doorless terminal withdrawal time-out interval). Turns on the beeper.
6. Informs the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print. 7. If a fault occurs while either printer is printing, the terminal proceeds as follows:
q q
Returns a printer unsolicited status message indicating a fault. Waits for a new Transaction Reply command message.
8. If a fault does not occur while the printer is printing, the terminal waits for printing to finish and then checks for an additional function identifier in the Transaction Reply command message.
Display and Print (3 or 9)

The terminal handles the Display and Print function ID as follows: 1. Shows the screen specified in the Transaction Reply command message. 2. After the screen is displayed the terminal does the following:
q q
Starts Timer 10 (withdrawal time-out interval). Turns on the beeper.
3. Informs the printer(s) (receipt or journal) defined in the printer flag field of the Transaction Reply command message to print.
U25604-J-Z745-1-7600
October 2004
291
Messages
4. If a fault occurs while the printer is printing, the terminal proceeds as follows:
q q
Sends a printer unsolicited status message indicating a fault. Waits for a new Transaction Reply command message.
5. If a fault does not occur while the printer is printing, the terminal waits for printing to finish and then checks for an additional function identifier in the Transaction Reply command message.
Eject Card, Dispense and Print (A) (Card before Cash)

The terminal handles the Eject Card, Dispense and Print function ID as follows: 1. Dispense the money and ejects the card. 2. Shows the Please take your card screen specified in the Transaction Reply command message as long as the customer takes the card or it will be captured after the Timer 09 has expired. 3. If card was taken, cash will be delivered and the screen Please wait for Cash and receipt is shown. If card was not taken, card will be retained, the dispensed money will be rejected and the terminal enters the next state specified in the Transaction Reply. 4. Prints the receipt and journal data. 5. Cut and deliver receipt if necessary. 6. Shows the Take receipt and Cash or Take Cash screen as long as Timer 02 is active. Timer 02 is in use to determine the length of time that the Close screen is displayed.
For retract terminals Timer 05 is started the cash has been dispensed. Also the beeper is active during Timer 05 is running. If the notes have not been taken when the timer expires, a retract is attempted. If some notes are retracted, the message Cash retracted is logged to the journal and an unsolicited error is reported to the host. If the notes are taken within the time frame of Timer 05 the timer is canceled. In both cases, Timer 07 is started, and the next state is entered on expiry.
292
October 2004
U25604-J-Z745-1-7600
Messages
Eject Card, Dispense and Print (F) (Parallel CBC)

The terminal handles the Parallel Eject Card, Dispense and Print function ID (Card before Cash) as follows: 1. Ejects the card. 2. Shows the Please take your card screen specified in the Transaction Reply command message as long as the customer takes the card or it will be captured after the Timer 09 has expired. 3. If card was taken, dispense the cash and shows the screen Please wait for Cash and receipt. If card was not taken, card will be retained, the dispensed money will be rejected and the terminal enters the next state specified in the Transaction Reply. 4. Prints the receipt and journal data. 5. Cut and deliver receipt if necessary. 6. Shows the Take receipt and Cash or Take Cash screen as long as Timer 02 is active. Timer 02 is in use to determine the length of time that the Close screen is displayed.
For retract terminals Timer 05 is started the cash has been dispensed. Also the beeper is active during Timer 05 is running. If the notes have not been taken when the timer expires, a retract is attempted. If some notes are retracted, the message Cash retracted is logged to the journal and an unsolicited error is reported to the host. If the notes are taken within the time frame of Timer 05 the timer is canceled. In both cases, Timer 07 is started, and the next state is entered on expiry.
U25604-J-Z745-1-7600
October 2004
293
Messages
Parallel Eject/Dispense and Print (Fast Cash) (B or C)

The terminal handles the Parallel Eject/Dispense and Print function ID as follows: 1. Parallel Eject/Dispense and Print. Shows the Please wait screen specified in the transaction request state. 2. Cut and deliver receipt if necessary and shows the screen Take Card and Cash. 3. Wait for card to be taken or captured, if not already taken. Displays the screen ...and receipt specified in the close state. Timer 02 is in use to determine the length of time that the Close screen is displayed.
For retract terminals Timer 05 and Timer 07 is started the cash has been dispensed. Also the beeper is active during Timer 05 is running. If the notes have not been taken when the timer expires, a retract is attempted. If some notes are retracted, the message Cash retracted is logged to the journal and an unsolicited error is reported to the host. If the notes are taken within the time frame of Timer 05 and Timer 07 the timer is cancelled.
q
If a fault does occur after five attempts to write to the card, the terminal goes to step 5.
4. Retains the card if the terminal cannot advance the card to write on it. 5. Returns a card writer solicited status message indicating a fault and waits for a new Transaction Reply command message
Print Data and Stay in Present State (P)

The Print Data and Stay in Present Mode function tells the terminal to print data and stay in present state. This allows the terminal to print large amounts of data without continually sending request messages to the network. After printing has been finished, the terminal sends a READY to the network. Then the network sends the next part of the printer data. This can be repeated until the network sends a new function reply containing a next state.
294
October 2004
U25604-J-Z745-1-7600
Messages
Electronic Journal Upload (EJU) commands
Print Statement and Set Next State (Q)

The Print Statement and Set Next State function is used to print statement data on receipts. During printing on receipt the terminal displays the transaction request screen (Please Wait). Depending on the print flag logging data are printed on journal. Then the terminal displays the transaction reply screen (Take Statement). If the printing has been finished, the terminal sends a READY to the network.

This section describes the commands that will be sent by the host to enable, continue und stop Electronic Journal Upload (EJU). EJU consists of following three terminal commands:
q q q
Send Options And Timers Acknowledge And Continue Acknowledge And Stop
see description of the commands on the following pages ...
U25604-J-Z745-1-7600
October 2004
295
Messages
Send Options And Timers

This command can be sent at any time to enable the Electronic Journal Upload. See also ProCash/NDC ProConsult/NDC Installation manual for EJU configuration. The following table describes the message format and its fields:
Table 75: Send Options And Timers message format
Description Message Identifier Field Separator (FS) Field Separator (FS) Field Separator (FS) Command Type Option Number Block Size Option Value Block Size Option Number Retry Threshold Option Value Retry Threshold Field Separator (FS) Acknowledge Timer Number AcknowledgeTimer Value
Mandatory Optional M M M M M O O O O M O O
Code 6 :1C :1C :1C 3 60 VAR 61 VAR :1C 60 VAR
No. of Characters 1 1 1 1 1 2[1] 3[1] 2[1] 3[1] 1 2 3
[1] If one or both Option Number(s) (60 or/and 61) are inserted, the 3 digit Option Value has to follow after each option.
Message Identifier Field size: 1 character
Valid range: 6 Description: This field specifies the message identifier. The message identifier for Electronic Journal is 6.
296
October 2004
U25604-J-Z745-1-7600
Messages Command Type Field size: 1 character
Valid range: 3 Description: This field specifies the command type for message identifier 6. The command type for Send Options and Timers is 3. Option Number Block Size Field size: 2 characters
Valid range: 60 Description: This field specifies the option number indicating the block size following the three digit Option Value Block Size. Option Value Block Size Field size: 3 characters
Valid range: 010-350; default is 200 Description: This field specifies the option value for the maximum size of electronic journal data that has to be sent to the host. Option Number Retry Threshold Field size: 2 characters
Valid range: 61 Description: This field specifies the option number indicating the retry threshold following the three digit Option Value Retry Threshold. Option Value Retry Threshold Field size: 3 characters
Valid range: 000-999; default is 000 (infinite retries) Description: This field specifies the option value for the number attempts to successfully send an Electronic Journal Upload block. The send attempt will be marked as successfull as soon as the terminal has received an Acknowledge command.
U25604-J-Z745-1-7600
October 2004
297
Electronic Journal Upload (EJU) commands Acknowledge Timer Number Field size: 2 characters
Messages
Valid range: 60 Description: This field indicates the Acknowledge Timer Number with the following Acknowledge Timer Value. Acknowledge Timer Value Field size: 3 characters
Valid range: 000-255; default is 000 (infinite) Description: This field specifies the Acknowledge Timer Value for the timer that indicates the maximum time in seconds to wait for an acknowledgement message from host before the same block will be resent.
298
October 2004
U25604-J-Z745-1-7600
Messages
Acknowledge And Continue

This command should be sent by the host each time a block of electronic journal data is received from the terminal. It can also be sent unsolicited at any time to enable EJU instead of sending the Options And Timers command. Then the default option and timer values will be used. If after sending an EJ block to the host, the terminal does not receive an acknowledgement within the specified time, the terminal will send the same block again. If the terminal has received the acknowledgement for the last electronic journal data block, the contents of the shared mapping where all EJ data are stored will be erased. See also ProCash/NDC ProConsult/NDC Installation manual for EJU configuration. The following table describes the Acknowledge And Continue message format and its fields:
Table 76: Acknowledge And Continue
Description Message Identifier Field Separator (FS) Field Separator (FS) Field Separator (FS) Command Type Last Character Received Message Identifier Field size: 1 character
Mandatory Optional M M M M M O
Code 6 :1C :1C :1C 1 VAR
No. of Characters 1 1 1 1 1 6
Valid range: 6 Description: This field specifies the message identifier. The message identifier for Electronic Journal is 6. Command Type Field size: 1 character
Valid range: 1 Description: This field specifies the command type for the Acknowledge And Continue of message identifier 6.
U25604-J-Z745-1-7600
October 2004
299
Electronic Journal Upload (EJU) commands Last Character Received Field size: 6 characters
Messages
Valid range: 000000-999999 Description: The value in this field should be the same as the value in the Last Character This Block field in the last EJU data message sent by the terminal. If the value is different, the terminal will not count this message as an acknowledgement. The last Char Previous Block and Last Char This Block values are based on a modulus 1,000.000 character count which starts at zero when the application will be started and EJU has been activated.
300
October 2004
U25604-J-Z745-1-7600
Messages
Acknowledge And Stop

This command acknowledges the last EJU block received by the host, and in addition indicates that EJU has to be stopped. This will disable the EJU function until the host sends a new Acknowledge And Continue command or Options And Timers command. See also ProCash/NDC ProConsult/NDC Installation manual for EJU configuration. The following table describes the Acknowledge And Stop message format and its fields:
Table 77: Acknowledge And Stop
Description Message Identifier Field Separator (FS) Field Separator (FS) Field Separator (FS) Command Type Last Character Received Message Identifier Field size: 1 character
Mandatory Optional M M M M M M
Code 6 :1C :1C :1C 2 VAR
No. of Characters 1 1 1 1 1 6
Valid range: 6 Description: This field specifies the message identifier. The message identifier for Electronic Journal is 6. Command Type Field size: 1 character
Valid range: 2 Description: This field specifies the command type for the Acknowledge And Stop of message identifier 6.
U25604-J-Z745-1-7600
October 2004
301
Electronic Journal Upload (EJU) commands Last Character Received Field size: 6 characters
Messages
Valid range: 000000-999999 Description: The value in this field should be the same as the value in the Last Character This Block field in the last EJU data message sent by the terminal. The last Char Previous Block and Last Char This Block values are based on a modulus 1,000.000 character count which starts at zero when the application will be started and EJU has been activated.
302
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
NDC Status Messages

Solicited Status (terminal state)
If the status descriptor field contains an F in the solicited status message, the status information will vary according to which of the following terminal commands has been received by the terminal. Terminal Command Send Configuration Information Send Supply Counters Send Error Log Information Send Date/Time Information Send Configuration ID Hardware Configuration Data Supplies Data Fitness Data Tamper and Sensor Status Data Software ID and Release Number Local Configuration Option Digits Message Identifier 1 2 4 5 6 H I J K L M
U25604-J-Z745-1-7600
October 2004
303
NDC Status Messages Send Configuration Information
Messages
This solicited status message is sent to central in response to a Send Configuration Information terminal command message.
Table 78: Send Configuration Information
Description message identifier configuration ID field separator (FS) hardware fitness field separator (FS) hardware configuration field separator (FS) supply status field separator (FS) sensor status field separator (FS) NDC+ release number field separator (FS) NDC+ software ID Message identifier Field size: 1
Code 1 --:1C --:1C --:1C --:1C --:1C --:1C ---
No. of Characters 1 4 1 22 or 38 1 44 or 76 1 23 or 26 1 12 1 6 1 9
Valid range: 1 Description: This message is sent to central in response to a send configuration information terminal command message. Configuration ID Field size: 4
Valid range: 0000-9999 Description: Contains the last four digit configuration ID numbers sent to the terminal from host.
304
October 2004
U25604-J-Z745-1-7600
Messages Hardware Fitness Field size: 22 or 38
NDC Status Messages
Valid range: 0-4 Description: Contains one byte per device or major device resource. Each byte is encoded with an error severity value indicating the current fitness of the device. The following table describes the meaning of the severity codes: Code 0 1 2 3 4 Severity no error routine errors have occurred warning conditions have occurred suspend, terminal is currently in suspend state due to suspected tampering with this device fatal error condition exists Routine, warning and fatal conditions can only be cleared by local supervisor transactions or through an system reboot for some devices if the reboot flag is set. The following table gives an overview about the devices of the hardware fitness:
Table 79: Hardware Fitness Table
Field 0 1 2 3 4 5 6 7 8 9 10
Contents time of day clock high order communications system disk card reader cash handler depository receipt printer journal printer reserved reserved night safe depository
Field 11 12 13 14 15 16 17 18 19-20 21
Contents encryptor security camera door access flex disk cassette type 1 cassette type 2 cassette type 3 cassette type 4 reserved statement printer
U25604-J-Z745-1-7600
October 2004
305
NDC Status Messages
Messages
The following table lists devices that are additionally appended in the Hardware Configuration Status message if command modifier 6 for command code 7 is used:
Table 80: Hardware Fitness Table Enhanced
Field 22 23 24 25 26 27 28 29 30
Contents Signage Display Reserved Coin Dispenser System Display Media Entry Indicators Envelope Dispenser Document Processing Module Coin Dispensing Module Tamper Indication Document Processing Module Tamper Indication Module
Field 31 32 33 34 35 36 37
Contents Reserved Digital Audio Service Reserved Reserved Reserved Reserved Reserved
Hardware configuration Field size: 44 or 76
Valid range: see detailed value description Description: Contains one byte per device or major device resource. Each byte is encoded with an error severity value indicating the current fitness of the device. See Table 81: Device Configuration Table on page 307 for the definition of ech byte.
Table 81: Device Configuration Table on page 307 mainly contains expressions of NCR specific hardware. For ProCash/NDC and ProConsult/NDC this table is just a reference table where the option bits of each hardware device can be taken and be set in section [HARDWARE_CONFIGURATION] of configuration file CUSTOM.PPF, to send the expected values for the host in the Hardware Configuration Information message.
306
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Table 81: Device Configuration Table
Byte Device
0
Product 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1E 1F
Description
Class 5663 5674 5675 5684 5685 5688 5665 5670 personaS75 personaS88 personaS40 personaS70 personaS74 personaS84 personaS85 5305 5886
1 2
7F
System Disk 00 02 Magnetic Card Reader/Writer 01 03 05 07 08 09 0A 0B 0C 10 11 1D Cash Handler 00 01 02 Depository 00 01 02 03 04
No Configuration Hard Disk present Reserved Track 2 (read only) Track 1/2/3 MCRW (write track3 only) Low cost DIP reader 3 Track Write MCRW Track 2 Smart Card Reader Track 1/2/3 Smart Card Reader 3 Track Write Smart Card Reader Track 2/3 DIP MSR Track 1/2/3 CIM 86 MCRW Track 1/2 DIP MSR Track 1/2 Swipe Card DIP Reader MIMIC Smart Card DIPReader Standard cash handler not configured Standard cash handler configured Angel spray dispenser configured Not configured Reserved PPD Reserved (third generation ADM) DPM envelope depository (non-5665 SSTs only)
U25604-J-Z745-1-7600
October 2004
307
NDC Status Messages
Messages
Receipt Printer 00 01 02 03 04 05 06 07 08 Journal Printer 00 01 02 03 80 81 82 83 Reserved 00 01 Reserved 00 01 Night Safe Depository 00 01 02 Encryptor ?0 ?1 02 03 04 ?5 06
Not configured Plain paper Black dot paper (TOF) Sideways printing, no black mark Sideways printing, black mark Thermal printer - no black mark Thermal printer - black mark Thermal printer - sideways printing, no black mark Thermal printer - sideways printing, black mark Not configured Integral journal printer Reserved Thermal printer Electronic journal Electronic journal and integral journal printer Reserved Electronic journal and thermal printer Not configured Configured Not configured Configured Not configured Configured Reserved Not configured NBS encyptor Reserved Reserved Reserved EKC encryptor Reserved ? = SST key entry mode (0, B, or C) where: 0 = single length keys without XOR key entry B = single length keys using XOR key entry C = double length keys
10
11
12
Security Camera 00 01 02 03 04 Door Access 00 01
Not configured Fixed format (for instance, 3M) Variable format (for instance, D/A) Reserved Digital Not configured Configured
13
308
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
14
Flex Disk 00 01 02 Tamper Indicat. Bins not DPM or CDM 00 01 02 03 Cardholder Keyboard 00 01 02 Operator Keyboard 00 01 02 Cardholder Display / Voice BIT 0 BIT 1 BIT 2 BIT 2 BIT 3 BIT 3 BIT 4 BIT 4 BIT 5 BIT 6 BIT 7
Not configured 1.44 MB flex disk connected 2.88 MB flex disk connected No TI bins present Secure cash, insecure cards, PPD or no PPD Secure cash, insecure cards, secure PPD Secure cash, cards, and PPD or no PPD Reserved Standard (BAPE) Keyboard EKC Keyboard Not configured Standard keyboard (Basic) Keyboard plus FDKs (Enhanced) 0 - (always) 0 - (always) 0 - Voice not supported 1 - Voice supported if digital audio present 0 - Standard FDKs 1 - Touch screen 0 - VGA 1 - VGM Translator 0 - (always) 0 - (always) 0 - (always) No configuration No configuration Not configured Configured Reserved Reserved 5665 DPM statement printer Enhanced thermal statement printer (SDC+) Not configured Configured Reserved None RMX S4 Not configured 20 x 40 Display Enhanced Display (16 x 32)
15
16
17
18
19 20 21
7F 7F
Statement printer 00 01 02 03 05 09 Signage Display [1] 00 01
22
23 24
--Coin Dispenser [1] 00 01 02 System Display [1] 00 01 02
25
U25604-J-Z745-1-7600
October 2004
309
NDC Status Messages
Messages
26
Media Entry Indicators [1] 00 01 Envelope Dispenser [1] 00 01 02 03 Document Processing Module [1] 00 01 02 Coin Dispensing Module Tamper Indication [1] 00 01 Document Processing Module Tamper Indication [1] 00 01
Not configured Configured Not configured Configured Reserved Reserved Not configured 5665 DPM configured DP-ATM configured
27
28
29
Not configured Present
30
Not configured Present Reserved
31 32
--Digital Audio Service 00 01

[1]
Not configured Present Reserved
33-37
--- [1]
[1]
These devices are only appended in the message if command modifier 6 is used.
310
October 2004
U25604-J-Z745-1-7600
Messages Supply Status Field size: 23 or 26
NDC Status Messages
Valid range: 0 - Not Configured 1 - Good State 2 - Media Low 3 - Media Out 4 - Overfilled Description: Contains one byte of following devices:
Table 82: Supply Status Device Table
Field 0 1 2 3 4 5 6 7 8 9 10 [1]
Contents reserved reserved not used = 0 card capture bin cash handler reject bin deposit bin receipt paper journal paper not used = 0 not used = 0 night safe depository
Field 11 - 14 15 16 17 18 19-20 21 22 23 24 25
Contents not used = 0 cassette type 1 cassette type 2 cassette type 3 cassette type 4 not used = 0 statement printer statement ribbon reserved [1] reserved [1] envelope dispenser [1]
These devices are only appended in the message if command modifier 6 is used.
Sensor Status Field size: 12
Valid range: see description Description: Contains one character per sensor and is identical to the information reported in character 2-13 of the Sensors status message. See section Sensor Status (unsolicited) (DID P) on page 361 for details.
U25604-J-Z745-1-7600
October 2004
311
NDC Status Messages NDC+ Release Number Field size: 6
Messages
Valid range: see description Description: Contains a six digit decimal number. The first pair of digits represents the release number. The second pair of digits represents the point release number. The third pair of digits represents the patch release number. Example: 060400 is release 06.04.00 NDC+ Software ID Field size: 9
Valid range: see description Description: Contains the NDC+ Software ID. Following values are valid: G530-0205 (NDC+ Native mode) G530-0206 (NDC+ Diebold Emulation mode) ProCash/NDC reports G530-0205 (NDC+ Native mode)
312
October 2004
U25604-J-Z745-1-7600
Messages Send Supply Counters
NDC Status Messages
This solicited status message is sent to the host in response to a Send Supply Counters terminal command message.
Table 83: Supply Counters
Description message identifier transaction serial number accumulated transaction count notes in cassette notes rejected notes dispensed last transaction notes dispensed cards captured envelopes deposited camera film remaining last envelope serial number Message identifier Field size: 1
Code 2 ---------------------
No. of Characters 1 4 7 20 20 20 20 5 5 5 (not supported) 5
Valid range: 2 Description: This message is sent to the host in response to a Send Configuration Information terminal command message. Transaction serial number Field size: 4
Valid range: 0000-9999 Description: Contains the TSN of the last transaction processed by the terminal. If this does not correspond to the last TSN sent by host, the transaction has not been initiated and terminal counters have not been updated.
U25604-J-Z745-1-7600
October 2004
313
NDC Status Messages Accumulated transaction count Field size: 7
Messages
Valid range: 0000000-9999999 Description: Defines the total number of transactions completed since the terminal was installed, or the non-volatile terminal memory was last corrupted. The count is reset to 0 after 9,999,999 transactions. Notes in cassette Field size: 20
Valid range: 00000-09999; 65535 Description: Consists of four 5 digit decimal counts of the total number of notes remaining in cassette types 1, 2, 3 and 4. The counts are set by supervisor functions and are decremented on each dispense transaction. These counts are zero if not set by the Standard Cassette Change or Set Cassette Counters SOP function. If physically more notes are dispensed (dispense below zero) than initially set (number of notes loaded) via one of the SOP function, ProCash/NDC sets this counter to value 65535 if the dispense below zero option is enabled. Notes rejected Field size: 20
Valid range: 00000-99999 Description: Consists of four 5 digit decimal counts of the total number of notes moved to the reject bin from cassettes 1, 2, 3 and 4. Although the fields Notes in Cassettes and Notes rejected may not be totally accurate, the sum of these counters for a particular cassette does accurately represent the difference between the original number of notes added and the number of notes dispensed. Notes dispensed Field size: 20
Valid range: 00000-99999 Description: Consists of four 5 digit decimal counts of the total number of notes dispensed from cassettes 1, 2, 3 and 4. These counts are consistent with note counts reported since the counts were last cleared by a SOP function. 314 October 2004
U25604-J-Z745-1-7600
Messages Last transaction notes dispensed Field size: 20
NDC Status Messages
Valid range: 00000-99999 Description: Consists of four 5 digit decimal counts of the total number of notes dispensed on the last transaction processed by the terminal. These field allows the host to recover note counts after power failure, even if the power failure occurred in the middle of a dispense operation. Card captured Field size: 5
Valid range: 00000-99999 Description: Consists of one 5 digit decimal count of the number of cards captured since the count was cleared by a SOP function. The count includes cards captured up to and including the transaction defined in the transaction serial number. Envelopes deposited Field size: 5
Valid range: 00000-99999 Description: Consists of one 5 digit decimal count of the number of envelopes deposited since the count was last cleared by a SOP function. The count includes envelopes deposited up to and including the transaction defined in the transaction serial number. Camera film remaining Field size: 5
Valid range: 00000 Description: Not supported by Wincor Nixdorf terminals. Always returned as zeros. Last envelope serial number Field size: 5
Valid range: 00000 Description: The last envelope serial number is always set to 00000.
U25604-J-Z745-1-7600
October 2004
315
NDC Status Messages Send Error Log Information
Messages
This solicited status message is sent to the host in response to a Send Error Log Information terminal command message. All error log information are stored in the CMOS file C:\PROTOPAS\WORK\CCCMOS.BIN. If the error log information request (6C) is sent from the host, the terminal reads the contents from the CMOS and send it to the network. The error log file can be cleared via the User Exit function. Enter Individual Functions from the main menu and select Clear Error Log.
Table 84: Send Error Log Information
Description message identifier group number new entries date last cleared month day hour minute device identification (DID) maintenance status (M-Status) severity part number maintenance data (M-Data) field separator
Code 4 C --------------------VAR :1C
No. of Characters 1 1 2 12 2 [1] 2 [1] 2 [1] 2 [1] 1 [1] 2 [1] 1 [1] 1 [1] 23 [1] 1 [1]
[1] These fields are repeated for each log entry present. The field separator is not present after the last log entry. In case of a repeated log there are two entries. The first acts as a header indicating the time of the most recent entry and the number of times repeated. The following log entry contains the information which has been repeatedly logged by the system, with the time of the first entry.
Message identifier Field size: 1
Valid range: 4 Description: This message is sent to central in response to a send error log group terminal command message.
316
October 2004
U25604-J-Z745-1-7600
Messages Group number Field size: 1
NDC Status Messages
Valid range: C Description: This field indicates the group number of the requested group. A = Processor system (not supported by Wincor Nixdorf terminals) B = Communications (not supported by Wincor Nixdorf terminals) C = ATM devices New entries Field size: 2
Valid range: See description Description: The number of new entries on the log since last read. If this is greater than log entries reported it indicates that log entries have been missed. Date last cleared Field size: 12
Valid range: See description Description: The date and time the log was last cleared in the following format: YY = Year MM = Month DD = Day HH = Hour MM = Minute SS = Second Month Field size: 2 00-99 01-12 01-31 00-23 00-59 00-59
Valid range: 01-12 Description: Month log entry
U25604-J-Z745-1-7600
October 2004
317
NDC Status Messages Day Field size: 2
Messages
Valid range: 01-31 Description: Day log entry Hour Field size: 2
Valid range: 00-23 Description: Hour log entry Minute Field size: 2
Valid range: 00-59 Description: Minute log entry Device identification Field size: 1
Valid range: C Description: This field identifies the device for which the log entry was made. This is the device identification used in all Wincor Nixdorf terminals reporting. A B C ? Processor system (not supported by Wincor Nixdorf terminals) Communications (not supported by Wincor Nixdorf terminals) or greater- ATM device log - Repeat log
318
October 2004
U25604-J-Z745-1-7600
Messages Maintenance status (M-status) Field size: 2
NDC Status Messages
Valid range: 00-99 Description: For a repeat log entry (?) this is field contains the number of times the log entry is repeated. Severity Field size: 1
Valid range: 1-4 Description: Severity of the log entry. Part number Field size: 1
Valid range: always zero Description: Part number of the component of the device. Maintenance data (M-data) Field size: 2
Valid range: 0-9; A-F Description: Maintenance data consisting of a string of hexadecimal characters. Each pair of characters represents the binary value of a single byte of detailed maintenance data. For a repeat log entry this data field is empty.
U25604-J-Z745-1-7600
October 2004
319
NDC Status Messages Send date/time information
Messages
This solicited status message is sent to the host in response to a send date and time terminal command message.
Table 85: Send Date/Time Info
Description message identifier TOD clock status terminal date/time Message identifier Field size: 1
Code 5 0-2 ---
No. of Characters 1 1 12
Valid range: 5 Description:This message is sent to central in response to a send date and time information terminal command message. TOD clock status Field size: 1
Valid range: 0-2 Description: 0 = Time is actual; 1 = Time is default; 2 = TOD malfunction Terminal date/time Field size: 12
Valid range: See description Description: The actual date and time returned by the terminal clock in format: YY = Year MM = Month DD = Day HH = Hour MM = Minute SS = Second 00-99 01-12 01-31 00-23 00-59 00-59
320
October 2004
U25604-J-Z745-1-7600
Messages Hardware Configuration Data
NDC Status Messages
This solicited status message is sent to central in response to a Send Configuration Information terminal command message with command code 7 and command modifier 1.
Table 86: Hardware Configuration Data
Description message identifier configuration ID identifier configuration ID field separator (FS) product class identifier product class field separator (FS) hardware configuration identifier device identifier hardware configuration data group separator (GS) device identifier [1] hardware configuration data [1]
[1]
Code H A --:1C B --:1C C ----[:1D] [---] [---]
No. of Characters 1 1 4 1 1 2 1 1 1 2 1 1 2
[1] These fields, devided through group separators, are repeated for each of the devices present in the ATM.
Valid range: H Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 1).
U25604-J-Z745-1-7600
October 2004
321
NDC Status Messages Configuration ID Identifier (A) Field size: 1
Messages
Valid range: A Description: Identifier of the four digit configuration ID number that follows. Configuration ID Field size: 4
Valid range: 0000-9999 Description: Contains the last four digit configuration ID number sent to the terminal from host. Product class ID Identifier (B) Field size: 1
Valid range: B Description: Identifier of the two digit product class that is included in the following two fields of the message. Product class Field size: 2
Valid range: 0000-9999 Description: This two character field contains the product class of the terminal. The following entries are possible:
Product class
0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C
Sytem Type
5663 5674 5675 5684 5685 5688 5665 5670 personaS75 personaS88 personaS40 personaS70 personaS74 personaS84 personaS85
322
October 2004
U25604-J-Z745-1-7600
Messages Hardware configuration identifier (C) Field size: 1
NDC Status Messages
Valid range: C Description: This field indicates that hardware configuration information of each present device follows. It is devided into a series of subfields separated by group separators. One subfield consists of Device Identifier and Hardware Configuration Data. If a device is not present, there will be no corresponding Device Identifier subgroup in the field. Device identifier Field size: Valid range: Description: This field contains the Device Identifier of each present device. Hardware configuration data Field size: 2 1
Valid range: see Table 81: Device Configuration Table on page 307. Description: This field contains the two digit hardware configuration information of each present device. It contains information for each device indicating which variant of the device is configured and if any other configuration data is available.
U25604-J-Z745-1-7600
October 2004
323
NDC Status Messages Supplies Data
Messages
Table 87: Supplies Data
Description message identifier supply status identifier device identifier supply status data group separator (GS) [1] device identifier
[1] [1]
Code I A ----[:1D] [---] [---]
No. of Characters 1 1 1 VAR 1 1 VAR
supply status data
Valid range: I Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 2). Supply status identifier (A) Field size: 1
Valid range: A Description: This field indicates that supply data of each present device follows. It is devided into a series of subfields separated by group separators. One subfield consists of Device Identifier and following supply data. If a device is not present, there will be no corresponding Device Identifier subgroup in the field.
324
October 2004
U25604-J-Z745-1-7600
Messages Supply status data Field size: VAR
NDC Status Messages
Valid range: each element of the supplies status data will take one of the following values: 0 1 2 3 4 Not configured/reserved Good state Media low Media out Overfill
Description: This field contains information for each present device indicating the condition of the parts of the device that are replenishable. Fitness Data This solicited status message is sent to central in response to a Send Configuration Information terminal command message with command code 7 and command modifier 3.
Table 88: Fitness Data
Description message identifier hardware fitness identifier device identifier fitness group separator (GS) [1] device identifier fitness
[1] [1]
Code J A ----[:1D] [---] [---]
No. of Characters 1 1 1 1 1 1 1
Valid range: J Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 3).
U25604-J-Z745-1-7600
October 2004
325
NDC Status Messages Hardware fitness identifier (A) Field size: 1
Messages
Valid range: A Description: This field indicates that the hardware fitness of each present device follows. It is devided into a series of subfields separated by group separators. One subfield consists of Device Identifier and following hardware fitness. If a device is not present, there will be no corresponding Device Identifier subgroup in the field. Fitness Field size: 1
Valid range: each fitness character is encoded with one of the following error severity values, indicating the current fitness of the device: 0 1 2 3 4 No error/ not supported Routine errors have occurred Warning conditions have occurred, investigation required Suspend Mode. The terminal is currently in the suspend mode due to suspected tampering with this device Fatal error condition exists on this device
Routine, Warning and fatal errors can only be cleared by entering Supervisor Mode or local Supervisor function Clear Fitness. Description: This field contains information for each present device indicating the current fitness the device present.
326
October 2004
U25604-J-Z745-1-7600
Messages Tamper and Sensor Status Data
NDC Status Messages
Table 89: Tamper and Sensor Status Data
Description message identifier sensor status identifier sensor status field separator tamper indicator identifier tamper status Message identifier Field size: 1
Code K A --:1C B ---
No. of Characters 1 1 5 1 1 VAR
Valid range: K Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 4). Sensor status identifier (A) Field size: 1
Valid range: A Description: This field indicates that a five bytes sensor status follows. These sensor status bytes are identical to the information reported in bytes 2-6 of the Sensor Status message. See section Sensor Status (unsolicited) (DID P) on page 361. Sensor Status Field size: 5
Valid range: 0 - 1 Description: These 5 bytes represents the same sensor status as reported in the unsolicited Sensor Status message (DID P).
U25604-J-Z745-1-7600
October 2004
327
NDC Status Messages Tamper status identifier (A) Field size: 1
Messages
Valid range: A Description: This field indicates that TI sensor status information follows. Tamper Status Field size: VAR
Valid range: 0 - 1 Description: Character 1-7 of the tamper status data are identical to the information reported in bytes 7-13 of the Sensor Status message. See section Sensor Status (unsolicited) (DID P) on page 361. The characters 8-13 are devices that are not supported by ProCash/NDC and appended as zeros in this message. If a device is not configured, any associated TI byte will take the value 0. Software ID and Release Number This solicited status message is sent to central in response to a Send Configuration Information terminal command message with command code 7 and command modifier 5.
Table 90: Software ID and Release Number
Description message identifier release number identifier NDC release number field separator software ID identifier NDC software ID
Code L A --:1C B ---
No. of Characters 1 1 VAR (6) 1 1 VAR (9)
See description of the fields on the following page.
328
October 2004
U25604-J-Z745-1-7600
Messages Message identifier Field size: 1
NDC Status Messages
Valid range: L Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 5). Release number identifier (A) Field size: 1
Valid range: A Description: This field indicates that a six digit release number follows. NDC release number Field size: 6
Valid range: VAR Description: Contains a six digit decimal number. The first pair of digits represent the release number. The second pair of digits represent the point release number. The third pair of digits represent the patch number (Example : 060000 is release 06.00.00). Software ID identifier (B) Field size: 1
Valid range: B Description: This field indicates that the sftware ID follows. NDC Software ID Field size: 9
Valid range: VAR Description: Contains the NDC+ software ID. For this release the field is set to following value: G530-0205 (NDC+ Native mode).
U25604-J-Z745-1-7600
October 2004
329
NDC Status Messages Local Configuration Option Digits
Messages
Table 91: Local Configuration Option Digits
Description message identifier local options identifier local option digits Message identifier Field size: 1
Code M A ---
No. of Characters 1 1 VAR (16)
Valid range: M Description: This message is sent to central in response to a send configuration information terminal command message (command code 7 inclusive command modifier 7). Local options identifier (A) Field size: 1
Valid range: A Description: This field indicates that local option digits follows. Local option digits Field size: 16
Valid range: VAR Description: These characters represent the values of the Local Option Digits. You can enable specific options via parameter LOCAL_MODE_ OPTIONS in configuration file CUSTOM.PPF.
330
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Solicited Status (device fault)

When the status descriptor is 8 - device fault, the following information is present in the status information field.
Table 92: Solicited Status (Device Fault)
Description device identifier transaction status field separator error severity field separator diagnostic M-status diagnostic M-data field separator supplies status Device Identifier Field size: 1
Code --VAR [:1C] VAR [:1C] --[---] [:1C] VAR
No. of Characters 1 17 1 5 1 VAR VAR 1 5
Valid range: See description Description: This field identifies the device by means of a device identification (DID). The following table shows DID entries of solicited status messages which Wincor Nixdorf terminals may send in response for transaction reply commands: DID D E F Device card reader/writer cash handler depository
U25604-J-Z745-1-7600
October 2004
331
NDC Status Messages Transaction Status Field size: 17
Messages
Valid range: See description Description: Contains information required to make a transaction completion decision. The length of the field is different for each device but each device will always send the same number of characters. See next section for detailed descriptions for each device. Error Severity Field size: 2
Valid range: 0-99 Description: Contains information required to decide locking the device or continue to use. The length of the filed is one character with the exception of currency handler which sends five characters. Each character is always coded in the same way:
Table 93: Error Severity Table
Code 0 1 2
Short Description Detailed Description no error routine error warning Continue to use. No error has occurred. Diagnostic information follows. Continue to use. A routine error has occurred and diagnostic information follows. Continue to use but it is recommended that the network operator is informed of the error or exception condition. Diagnostic information follows. The terminal will suspend transaction processing on completion of the current transaction (state 000 entered). This is sent if cardholder tampering is suspected. Device is out of service and will continue to report intervention at the terminal. It is recommended that the terminal is put out of service or transactions involving the faulty device are not allowed.
suspend
fatal
332
October 2004
U25604-J-Z745-1-7600
Messages Diagnostic M-Status Field size: 2
NDC Status Messages
Valid range: 0-99 Description: The two digit M-Status contain the NDC specific main error status which gives a global information of the error situation. The M-Status values can be configured (mapped) for each error CLASS and error CODE of vendor specific errors (on Wincor Nixdorf systems CSC-W32 errors) via parameter M_STATUS in configuration file CCERRMAP.INA. Please refer to the ProCash/NDC ProConsult/NDC Installation manual section Customize Error Mapping Table CCERRMAP how to configure M-Status. Diagnostic M-Data Field size: 0-30
Valid range: 0-9; A-F Description: This field is used to log additional M-Data status information. It can be variable depending on the device. M-Data are appended to the M-Status without separator. M-Data contain additional hardware status information of NCR hardware. On Wincor Nixdorf systems this hardware status information can be configured (mapped) via parameter M_DATA in configuration file CCERRMAP.INA to the vendor specific error code with the closest match to the meaning of the NCR specifc M-Data code. A cross reference of the M-Data descriptions can be taken from the original Diagnostic Status Code Note Book that can be ordered from NCR. (See also M-Status description). Supplies Status Field size: 5
Valid range: 0-99 Description: Contains information related to the state of supplies (paper, currency, magnetic cards, envelopes) in the terminal. This field contains one character for each supplies container managed by the device.
U25604-J-Z745-1-7600
October 2004
333
NDC Status Messages Each character is always coded in the same way:
Table 94: Supplies Status Table
Messages
Code 0 1 2 3 4
Short Description Detailed Description no-new-state good state media low media out overfill The state of the container can be assumed as unchanged The state of the container is known to be good (not low empty or overfilled). The container has reached the low condition. The container is empty. The container has sensed a full condition and should be emptied.
If this field is omitted it can be assumed that there is no new state on any container.
334
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Unsolicited Device Status

The following table shows the structure of the status information field in unsolicited status messages of NDC.
Table 95: Unsolicited Device Status
Description device identifier (DID) device status field separator error severity field separator diagnostic M-status diagnostic M-data field separator supplies status Device Identifier (DID) Field size: 1
Code --VAR [:1C] VAR [:1C] --[---] [:1C] VAR
No. of Characters 1 13 1 5 1 VAR VAR 1 5
Valid range: See description Description: This field identifies the device by means of a device identification (DID). Device Status Field size: 13
Valid range: See description Description: Used for recording any transaction exceptions of device state changes. For devices which report both solicited and unsolicited status messages a common set of transaction device status codes are defined for use in either type of message. When processing a transaction reply command any unsolicited transaction exceptions are reported prior to the solicited device fault or ready status.
U25604-J-Z745-1-7600
October 2004
335
NDC Status Messages Error Severity Field size: 2
Messages
Valid range: 0-99 Description: See section Solicited Status (device fault) on page 331 Diagnostic M-Status Field size: 2
Valid range: 0-99 Description: The two digit M-Status contain the NDC specific main error status which gives a global information of the error situation. The M-Status values can be configured (mapped) for each error CLASS and error CODE of vendor specific errors (on Wincor Nixdorf systems CSC-W32 errors) via parameter M_STATUS in configuration file CCERRMAP.INA. Please refer to the ProCash/NDC ProConsult/NDC Installation manual section Customize Error Mapping Table CCERRMAP how to configure M-Status. Diagnostic M-Data Field size: 0-30
Valid range: 0-9; A-F Description: This field is used to log additional M-Data status information. It can be variable depending on the device. M-Data are appended to the M-Status without separator. M-Data contain additional hardware status information of NCR hardware. On Wincor Nixdorf systems this hardware status information can be configured (mapped) via parameter M_DATA in configuration file CCERRMAP.INA to the vendor specific error code with the closest match to the meaning of the NCR specifc M-Data code. A cross reference of the M-Data descriptions can be taken from the original Diagnostic Status Code Note Book that can be ordered from NCR. (See also M-Status description). Supplies Status Field size: 5
Valid range: 0-99 Description: See section Solicited Status (device fault) on page 331
336
October 2004
U25604-J-Z745-1-7600
Messages Power Up (unsolicited) (DID B)
NDC Status Messages
This message is used to inform the host that a power interruption or system reboot has occurred. Under such circumstances, the message cannot be sent until the communication with the host has been reestablished. The status field for this type message is composed of the following sub fields: Description Device Identifier Device Status No. of Sol./ Code Characters Unsol. 1 4 U B VAR Detailed Definition Indicates a power failure. Four characters (0000 9999) defining the configuration number of the customization data. The host ensures that the terminal has the correct CI before sending a go in service command.
U25604-J-Z745-1-7600
October 2004
337
NDC Status Messages Card Reader (sol./unsol.) (DID D) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 U D 0
Messages
Detailed Definition Indicates a card reader unit message No transaction exception condition occurred but consult other fields for error severity, diagnostic status or supplies status changes. Cardholder did not take his card within the allowed time and it was captured or jammed. The mechanism failed to eject the card and it was captured or jammed. The mechanism failed to update Track 3 on the card. Invalid Track 3 data received from Central This is a single character field coded in the standard way to be used to make a shutdown decision. Operation successful Blank track Track not supported Read error Write error No card in reader at start of command Card removed during capture Shutter jammed open
Transaction 1 Device Status; gives details of any transaction related exception condition detected while processing a card at the terminal.
S/U
S/U
S/U
S/U Error Severity 1
4 0-4
Diagnostic M-status and M-Data
2-10
00 01 02 03 04 05 06 07
338
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description
No. of Sol./ Code Characters Unsol. 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 33 35 37 38 40
Detailed Definition Shutter switch failure detected Error recovery successful shutter jammed closed Card jam (not during capture) Card captured after unsuccessful eject Possible cardholder tampering Too many consecutive read errors Too many consecutive write errors Too many consecutive card jams Too many consecutive shutter jammed closed Card jam during capture Too many consecutive invalid cards Device still inoperative No card during clean test Speed out of spec. (fast) Speed within +3% Speed within +-1% Speed within -3% Speed out of spec. (slow) Invalid card detected CIM service test failed Error in track 3 data CROPF feature not supp. LFCC bin full soon/full LFCC bin removed
U25604-J-Z745-1-7600
October 2004
339
NDC Status Messages
Messages
Description
No. of Sol./ Code Characters Unsol. 41 50 51
Detailed Definition CROPF feature failure Card not in SCRW stage position Smart card stopper pin or contacts lowered, unable to capture Invalid smart card command code error Invalid smart card command data error SCIF not configured/not responsing SCIF response timeout exeeded Card reader is in SCRW mode (diagnostics only) Invalid smart card response length Invalid SCIF command code Invalid SCIF command format No smart card encryptor response error Invalid key ID Invalid key type Invalid parent key type Invalid key - doesnt exist Password not decimal Password no match Key integrity error Key parity error Invalid data format Stopper PIN failure Contact unit failure Card movement failure
52 53 54 55 56 57 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78
340
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description
No. of Sol./ Code Characters Unsol. 79 80 81 82 83 84 85 86 87 88 89 90 91
Detailed Definition Smart card switch off failure Smart card removed error No smart card response Smart card transmission error Smart card switched off Illegal card type/param. Power up ime exceeded ANSI PIN block error CIM self test failed CIM security module defective CIM security module communication failure CIM interface board defective CIM interface board communication failure No new state No overfill condition Overfill condition
Supplies Status
0 1 4
U25604-J-Z745-1-7600
October 2004
341
NDC Status Messages Dispenser (sol./unsol.) (DID E) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 E
Messages
Detailed Definition Indicates a dispenser solicited or unsolicited message. Successful operation, but an exception condition occurred which is detailed in later fields. Short dispense No notes dispensed Faulty dispense. Notes dispensed unknown. The following counts contain requested dispense values. No notes dispensed or card not ejected. This status is returned on a card before cash transaction if the stack operation fails and the notes are purged prior to card eject. Some notes have been retracted following a Present and Notes not taken time-out. The number of notes retracted is unknown. Cass Types logical cassette 1 logical cassette 2 logical cassette 3 logical cassette 4
Transaction Status 1 (T-code plus T-data); gives details of a dispense operation in response to a transaction reply command message.
S S S
1 2 3
Characters 2-9 (T-Data) contain notes dispensed counts. Each pair of characters represents a twodigit decimal value in range 00-99 per cassette type
Characters 2-3 4-5 6-7 8-9
342
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description Error Severity Character 0 Character 1 Character 2 Character 3 Character 4 Diagnostic M-status and M-data
No. of Sol./ Code Characters Unsol. 5 0-4
Detailed Definition
Severity info related to complete device. Severity related to cassette type 1. Severity related to cassette type 2. Severity related to cassette type 3. Severity related to cassette type 4. 2-32 00 01 02 03 04 05 06 07 08 09 10 11 No error Pick requested from noninstalled cassette Too many bills being rejected Pick failure Pick failure and low (out of bills) Sensor failure or currency jam Divert gate fault Reject bin inoperative Reject bin overfill Comm failure between dispenser and terminal Fatal previous error Unrecovered previous error
U25604-J-Z745-1-7600
October 2004
343
NDC Status Messages
Messages
Description
No. of Sol./ Code Characters Unsol. 12 13 14 15
Detailed Definition Present mechanism failed or jammed Exit shutter jammed open Exit shutter jammed closed Bills passing overfill sensor on present operation Timing disk did not operate correctly Exit sensor failed to clear Timing disk did not operate correctly Exit sensor blocked initially on next operation Not configured Security violation Security inhibition Reserved An area of NVRAM cannot be accessed Presenter transport timing disk did not operate correctly or motor failed One of the presenter transport sensors failed clear or blocked Reserved Heartbeat on execution processor failed (80652) Communications failure on the I2C bus of the execution processor
16 17 18 19 20 21 22 23-27 28 29
30
31 32 33
344
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description
No. of Sol./ Code Characters Unsol. 34
Detailed Definition A present bills operation has been attempted without any bills being stacked or a retract operation has been attempted with no bills presented. Operation incomplete due to ac and 24V dc power disconnection through interlock. Pick valve test not attempted because cassettes were installed TI service switched ON TI service switched OFF LVDT or associated circuitry malfunctioning Bill parameters not configured An attempt to pick from a cassette which has been disabled for In Service Replenishment
35
36
37 38 39
40 41
Supplies Status. 5 Indicates the state of the reject bin and currency cassettes. Codes for the reject cassette (character 0) Codes for disp. cass. types 1-4 (character 1 - 4) 0 1 4 0 1 2 3 no new state no overfill condition overfill condition no new state Sufficient notes Low on notes Out of notes
U25604-J-Z745-1-7600
October 2004
345
NDC Status Messages Depository (sol./unsol.) (DID F) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 F
Messages
Detailed Definition Indicates a depository solicited or unsolicited message. Successful operation, but an exception condition occurred which is detailed in the following field. Time-out on cardholder deposit. Failure to enable mechanism for a deposit Deposit failed, cardholder has access to envelope. This status is also returned if there is any doubt about cardholder access. Deposit failed, cardholder does not have access to envelope This is a single character field coded in the standard way to be used to make a shutdown decision.
Transaction Status 1 (T-code plus T-data); gives details of a deposit operation in response to a transaction reply command message
S S S
1 2 3
Error Severity
0-4
346
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description Diagnostic M-status and M-data
No. of Sol./ Code Characters Unsol. 2-22 00 01 02 03 04 05 06 07 08 09 10 11 13 15 50 51 52 55
Detailed Definition No error Transport jam Transport jam and shutter jammed open Transport jam and shutter jammed closed Shutter jammed open Shutter jammed closed Transport sensor failure Communication failure within the atm Invalid device print head status Invalid device module status Deposit not done, error count exceeded Deposit bin overfill Timing disk failure Transport motor failure Anti fishing sensor error Motor speed too fast Print head removed Interlock failed no envelope deposited no overfill condition overfill detected
Supplies Status
0 1 4
U25604-J-Z745-1-7600
October 2004
347
NDC Status Messages Envelope Dispenser (unsolicited) (DID \
Messages
ProCash/NDC sends unsolicited envelope dispenser messages depending on the value of the enhanced configuration option 23. See section Enhanced Configuration Parameters Load on page 249 for details.
Description Device Identifier
No. of Sol./ Code Characters Unsol. 1 \
Detailed Definition indicates a depository solicited or unsolicited message. Envelope presentation successful Failure - envelope not presented or retracted This is a single character field coded in the standard way to be used to make a shutdown decision. No error Transport jam before exit sensor Transport jam at exit sensor Exit sensor failure shutter jammed open Bin low sensor failure Timing disk sensor failure Bin is low and failed to present, EMPTY. Sufficient envelopes Envelopes low Envelopes exhausted
Device Status. 1 Indicates whether the last transaction was successful Error Severity 1
1 0-4
Diagnostic M-status and M-data
2-8
00 01 02 03 04 05 06
Supplies Status
1 2 3
348
October 2004
U25604-J-Z745-1-7600
Messages Receipt Printer (unsolicited) (DID G) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 U S G 0 1
NDC Status Messages
Detailed Definition Indicates a receipt printer unsolicited message. Successful print Print operation not successfully completed Device not configured This is a single character field coded in the standard way to be used to make a shutdown decision. See table Error severity table for details. No error Head jam/ Knife jam Failed to go not busy Black mark error Always saw the black mark Paper out Paper not loaded or Paper jam before transport Communication error Printer open Ribbon needs replaced soon Printhead needs replaced soon Knife needs replaced soon
Transaction/ 1 Device Status. Indicates whether or not the print was successfully completed. error severity 1
2 0-4
2-10
00 01 02 03 04 05 07
08 09 10 11 12
U25604-J-Z745-1-7600
October 2004
349
NDC Status Messages
Messages
Description
Detailed Definition Ribbon needs replaced now Printhead needs replaced now Sideways communication error Eject jam Sufficient paper Paper low Paper exhausted Ribbon o.k. Ribbon replacement recommended Ribbon replacement mandatory Printhead o.k. Printhead replacement recommended Printhead replacement mandatory Knife o.k. Knife replacement recommended
Supplies Status
CHAR 0
CODE 1 2 3 1 2 3
1 2 3
1 2
350
October 2004
U25604-J-Z745-1-7600
Messages Journal Printer (unsolicited) (DID H) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 U S S H 0 1 2
NDC Status Messages
Detailed Definition Indicates a journal printer unsolicited message. Successful print. Print operation not successfully completed Device not configured
Transaction/ 1 Device Status. Indicates whether or not the print was successfully completed. Error Severity 1
0-4
This is a single character field coded in the standard way to be used to make a shutdown decision. See table Error severity table for details. No error Head jam/ Knife jam Failed to go not busy Black mark error Always saw the black mark Paper out Paper not loaded or paper jam before transport Communication error Printer open Ribbon needs replaced soon Printhead needs replaced soon Knife needs replaced soon
2-10
00 01 02 03 04 05 07
08 09 10 11 12
U25604-J-Z745-1-7600
October 2004
351
NDC Status Messages
Messages
Description
Detailed Definition Ribbon needs replaced now Printhead needs replaced now Sideways communication error Eject jam Sufficient paper Paper low Paper exhausted Ribbon o.k. Ribbon replacement recommended Ribbon replacement mandatory Printhead o.k. Printhead replacement recommended Printhead replacement mandatory
Supplies Status
CHAR 0
CODE 1 2 3 1 2 3
1 2 3
352
October 2004
U25604-J-Z745-1-7600
Messages Statement Printer (sol./unsol.) (DID V) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 V
NDC Status Messages
Detailed Definition Indicates a statement printer sol./unsolicited message. Successful print, but consult other fields for Error Severity, diagnostic status or supplies status change. Print / cut not successful Device not configured Statement present in transport Cardholder pressed cancel during a print statement and wait function This is a single character field coded in the standard way to be used to make a shutdown decision. See table Error severity table for details. No error Mechanical jam Communication error Black mark error Media jam (fatal), or exit sensor error (warning) Paper out Ribbon needs replaced now (Fatal) Ribbon needs replaced soon (Warning)
Transaction/ 1 Device Status. In a solicited status it gives details of any transaction oriented faults. In an unsolicited status it indicates a transport error or a cut and deliver error in the close state. Error Severity 1
S/U S U U
1 2 3 4
0-4
2-32
00 01 02 04 05 07 08 08
U25604-J-Z745-1-7600
October 2004
353
NDC Status Messages
Messages
Description Diagnostic M-status and M-data
No. of Sol./ Code Characters Unsol. 2-16 09 10 10 11 16 17 18
Detailed Definition Knife needs replaced soon Printhead needs replaced now (Fatal) Printhead needs replaced soon (Warning) Printer left open Capture jam Media removed by customer during capture Media stuck in throat, unable to pull into printer possible customer tampering No paper present at start of command Printer malfunction paper present Bin overfill Print attempted beyond end of media Printer fatal Buncher communications failure Clamp drive jammed open Clamp drive jammed open Capture bin full
19 20 21 22 23 33 34 35 36
354
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description Supplies Status
No. of Sol./ Code Characters Unsol. 1 CHAR CODE 0 1 2 3 1 1 2 3 2 1 2 3 3 1 2 3 4 1 4
Detailed Definition
Sufficient paper Paper low Paper exhausted Ribbon o.k. Ribbon replacement recommended Ribbon replacement mandatory Printhead o.k. Printhead replacement recommended Printhead replacement mandatory Knife o.k. Knife replacement recommended Knife replacement mandatory Capture bin o.k. Capture bin overfill
U25604-J-Z745-1-7600
October 2004
355
NDC Status Messages Vandal Guard (unsolicited) (DID J) Description Device Identifier Device Status Error Severity No. of Sol./ Code Characters Unsol. 1 1 1 U J 1 0-4
Messages
Detailed Definition Indicates a vandal guard unsolicited message. Always 0 for the vandal guard. This is a single character field coded in the standard way to be used to make a shutdown decision. See table Error severity table for details. No error Failed to close Failed to open Jammed, position undefined
2-6
00 01 02 03
356
October 2004
U25604-J-Z745-1-7600
Messages EDM - Module (unsolicited) (DID L) Description Device Identifier No. of Sol./ Code Characters Unsol. 1 L
NDC Status Messages
Detailed Definition Indicates an EDM module unsolicited message. EDM error EDM not configured This is a single character field coded in the standard way to be used to make a shutdown decision. See table Error severity table for details. No error Parity error Hardware error Key transport error No key Invalid command as keyboard is currently enabled Communication failure Security module reset was successful Invalid command data data mismatch No key loaded in DEU prior to requesting an encr. or decr. operation
Device Status Error Severity
1 1
1 2 0-4
2-10
00 01 02 03 04 05
07 08 11 12 13
U25604-J-Z745-1-7600
October 2004
357
NDC Status Messages
Messages
Description
No. of Sol./ Code Characters Unsol. 15
Detailed Definition Set up failure - key space ID1 already exists and is not a programmer parent with E/D attribute and 17 keys Invalid keyspace ID format, outside 0 -15. Keyspace already exists. Keyspace does not exist Keyspace ID1 has wrong attribute or class. Keyspace ID2 has wrong attribute or class. Invalid keyspace, wrong access right Only two RAR access spaces allowed, keyspace not created Secret keyspace creation disabled. Keyspace is not a parent. Key ID2 not a keyspace specified or keyspace specified not a child of key ID2 keyspace. Invalid parent format. Invalid parent ID, keyspace not a parent or keyspace does not exist. Parent keyspace is a programmer, can not have secret child. Key spaces do not match. Key ID outside maximum range of keys.
16 17 18 19 20 22 23
24 25 26
27 28
29
30 32
358
October 2004
U25604-J-Z745-1-7600
Messages
NDC Status Messages
Description
No. of Sol./ Code Characters Unsol. 33 34 37 38 39 40 41
Detailed Definition Key ID1 has wrong attribute. Key ID2 has wrong attribute. Invalid key ID, no PIN encryption allowed. Invalid key, key does not exist. Key ID2 does not specify an IV. Invalid key ID, no key Invalid key ID, key may not be exclusively ORed with key from different keyspace. Invalid attribute field. Attribute already in family. Invalid parameter field. Undefined parameter for keyspace class. Variation index outside range 01-7F hex. Variation index already in family. Invalid mode for this function. Invalid left shift, value out of range. Invalid length, or length and offset outside range. Invalid access right. Invalid POST PIN PAD digit (> 0F hex). Invalid PRE PIN PAD data length (> 0C hex). Modulus bit length > 576 or Exponent bit length > 576 or Modulus bit length <= exonent bit length.
48 49 50 51 52 53 54 55 56 57 58 59 60
U25604-J-Z745-1-7600
October 2004
359
NDC Status Messages
Messages
Description
No. of Sol./ Code Characters Unsol. 64 65 66
Detailed Definition Password does not contain decimal digits Invalid password, no match. Keyspace inaccessible, password error count exceeded. PIN verification failed. Invalid PIN encrypt type function (encryption mode changed). Key integrity error. Invalid PIN, no encryption allowed (truncated PIN does not contain decimal digits). Timeout error. Communication error. TC<>41, or TRS<>00 00 00 00, when decrypted.
70 74
75 76
97 98 99
360
October 2004
U25604-J-Z745-1-7600
Messages Door Access (unsolicited) (DID N) Description Device Identifier Device Status No. of Sol./ Code Characters Unsol. 1 1 U N 1
NDC Status Messages
Detailed Definition Indicates a door access unsolicited message. Always 1 indicating that access is possibly inhibited. Always 2 indicating a warning. Local intervention required. No error Bad read error Time-out error Comms error Not configured
Error Severity
2-4
00 01 02 03 05
Sensor Status (unsolicited) (DID P) This message is sent on Supervisor mode entry and exit, tamper indicating bin in/out conditions and alarm conditions. See also ProCash/NDC ProConsult/NDC Installation manual section [APPLICATION_XXX].. Description Device Identifier Device Status No. of Char Characters 1 13 1 Code P 1 Detailed Definition Indicates a Sensor status message. TI sensor change (characters 2-13 give complete definition of all sensors) Mode change (characters 3-13 are omitted) Alarm state change Supervisor mode exit Supervisor mode entry Not applicable
2 3 If byte 1 = 2 If byte 1 = 1 2 2 0 1
U25604-J-Z745-1-7600
October 2004
361
NDC Status Messages
Messages
Description
No. of Char Characters 3
Code 0 1
Detailed Definition Vibration and/or heat sensor inactive Vibration and/or heat sensor active Door has been closed Door has been opened Silent signal sensor inactive Silent signal sensor active Electronics enclosure sensor inactive Electronics enclosure sensor active Deposit bin out Deposit bin in Card bin out Card bin in Currency reject bin out Currency reject bin in Cassette in position 1 out Cassette in position 1 in Cassette in position 2 out Cassette in position 2 in Cassette in position 3 out Cassette in position 3 in Cassette in position 4 out Cassette in position 4 in
4 5
0 1 0
1 6 0 1 7 8 9 10 11 12 13 0 1 0 1 0 1 0 1 0 1 0 1 0 1
362
October 2004
U25604-J-Z745-1-7600
Messages Supervisor Key Messages (unsolicited) (DID R)
NDC Status Messages
This message sends supervisor key messages from the terminal to inform the host of the functions selected by the operator after entry to supervisor mode. Supervisor key messages are supported in ProCash/NDC-SOP only. They can be configured via parameter MESSAGE_MODE. See also ProCash/NDC SOP Programmers Reference manual for detailed descriptions. Description No. of Char Chars Code R 1-2 or 1 0 1 2 3 4 7 8 00 - 98 Select menu Replenishment menu Configure menu Access menu In Service Supervisor menu Exit menu Exit menu Menu item selected Detailed Definition Indicates a Sensor status message.
device identifier 1 device status VAR

(4 max)
00 - 98 Key selection from Select menu
2-3 or 1-2 3-4
00 - 98 Host menu Host function
U25604-J-Z745-1-7600
October 2004
363
NDC Status Messages
Messages
Electronic Journal Upload (EJU) Message

This section describes the message format of the Electronic Journal Upload (EJU) message that will be sent in response to an Options And Timers or Acknowledge And Continue command. Please refer to section Electronic Journal Upload (EJU) commands on page 295 for detailed descriptions about EJU command messages. The following table describes the message format of the EJU message.
Table 96: Electronic Journal Upload message format
Description Message Identifier Message Modifier field separator field separator field separator field separator Machine Number Date Time Last Char Previous Block Last Char This Block Block Length Response Data Message Identifier Field size: 1 character
Code 6 1 :1C :1C :1C :1C VAR VAR VAR VAR VAR [:1C] VAR
No. of Characters 1 1 1 1 1 1 6 6 6 6 6 3 0-350
Valid range: 6 Description: This field specifies the message identifier. The message identifier of the Electronic Journal Upload message is 6.
364
October 2004
U25604-J-Z745-1-7600
Messages Message Modifier Field size: 1 character
NDC Status Messages
Valid range: 1 Description: This field specifies the message modifier. The Message Modifier 1 indicates this message as Electronic Journal Upload data. Machine Number Field size: 6 characters
Valid range: 000000-999999 Description: This field contains the machine number from the terminal. Date Field size: 6 characters
Valid range: 000000-999999 in format YYMMDD Description: This field contains the date (from internal system clock of the terminal) when the EJ block was sent to the host. Time Field size: 6 characters
Valid range: 000000-999999 in format HHMMSS Description: This field contains the time (from internal system clock of the terminal) when the EJ block was sent to the host. Last Char Previous Block Field size: 6 characters
Valid range: 000000-999999 Description: The last Char Previous Block and Last Char This Block values are based on modulus 1,000.000 character count which starts at zero when the EJU is conffollowing a restart start of the terminal. The count is incremented for each character written to the electronic journal.
U25604-J-Z745-1-7600
October 2004
365
NDC Status Messages Last Char This Block Field size: 6 characters
Messages
Valid range: 000000-999999 Description: The terminal compares the last Character Received field in the acknowledgement message sent from the host with the Last Character This Block field of the last EJU data message that is sent to the host. If these two values are not the same, the acknowledgement message is ignored. The Last Character Previous Block field can be used by the host for checks on message received. Response Data Field size: up to 350 bytes
Valid range: 0-350 Description: Electronic Upload Data consists of ASCII text with carriage return (CR) at the end of each line. If no electronic data available to sent, the response data size is zero.
366
October 2004
U25604-J-Z745-1-7600
Printers
Printer Models
ProCash/NDC and ProConsult/NDC support all models of printers that are listed in Table 97. All printer control characters of ProCash/NDC or ProConsult/NDC will be initiated via macros. Then the macros are transfered to the WOSA service. WOSA passes the data to CSC-W32. See also CSC-W32 Programmers Reference. The current ProCash/NDC and ProConsult/NDC releases support following printer models as listed in the following table:
Table 97: Printer Models
Models
ND71 ND99 ND98 ND9A ND9E ND9C ND9D ND9G TH30 TH21 TH23 TH97 TH97/G TP01 TP07 TP06 NP07 NP06
Printer Description
RECEIPT/JOURNAL dot matrix printer (obsolete) THERMO RECEIPT printer (obsolete) JOURNAL dot matrix printer RECEIPT dot matrix printer RECEIPT dot matrix printer RECEIPT Thermal printer JOURNAL Thermal printer RECEIPT Thermal printer (only GDI interface) JOURNAL Thermal printer RECEIPT Thermal printer (optional with GDI interface) STATEMENT Thermal printer (optional with GDI interface) STATEMENT dot matrix printer STATEMENT Thermal printer (optional with GDI interface) STATEMENT Thermal printer (optional with GDI interface) RECEIPT Thermal printer (optional with GDI interface) JOURNAL dot matrix printer (optional with GDI interface) RECEIPT dot matrix printer JOURNAL dot matrix printer
Detailed descriptions can be taken from the hardware specification manuals. Please refer also to the ProCash/NDC ProConsult/NDC Installation manual for detailed descriptions about printer utilities.
U25604-J-Z745-1-7600
October 2004
367
Printer Control Characters
Printers
Printer Control Characters

The following tables gives a short description about control sequences used in the NDC+ message protocol, which are supported by ProCash/NDC and ProConsult/NDC.
Table 98: NDC Printer control characters
Control Character LF FF
ASCII Code 0AH 0CH
Short Description Line Feed, causes the next graphic character to be printed on the next line. Causes a feed to the next TOF mark or feed to the maximum receipt length, cut and deliver to customer. Fills an area of the printer form with spaces. This 'SO' character is followed by a single graphic character indicating the desired number of spaces: Character 1-9 : ; < = > ? No. of spaces 1-9 10 11 12 13 14 15
SO
0EH
HT
09H
Horizontal tabulators; positions the next graphic character in the next tab column. Tabs are defined to be in every eighth column from the left margin. sets Single Alpha 1 char set size (10 CPI) sets Single Alpha 2 char set size (10 CPI) see Note sets Single Alpha 3 char set size (10 CPI) see Note sets Double Alpha 1 char set (5 CPI) sets Double Alpha 2 char set size (5 CPI) sets Double Alpha 3 char set size (5 CPI) sets Condensed Alpha 1 char set size (17 CPI)
ESC (1 ESC (2 ESC (7 ESC (> ESC (? ESC (B ESC (C
1B (1 1B (2 1B (7 1B (> 1B (? 1B (B 1B (C
368
October 2004
U25604-J-Z745-1-7600
Printers
Electronic journal
Control Character ESC (D ESC (E ESC [pxxx ESC [qxxx ESC [rxx ESC %xxx
ASCII Code 1B (D 1B (E 1B [pxxx 1B [qxxx 1B [rxx 1B %xxx
Short Description sets Condensed Alpha 2 char set size (17 CPI) sets Condensed Alpha 3 char set size (17 CPI) left margin control right margin control lines per inch control sets printer code page xxx. 000 = set user charset
If character set Alpha 2 or Alpha 3 is sent from host, the printer switches to the user defined character set. See also ProCash/NDC ProConsult/NDC Installation manual section Printer Fonts for details.
Electronic journal
Wincor Nixdorf terminals are able to log all journal printer messages into journal files which are stored on the PC hard disk. The predefined path of the journal files on the harddisk is C:\JOURNAL and C:\CUSTUMER. See also section [TOPMSG] and [CUSTMSG] in configuration file CUSTOM.PPF.
Electronic journal storage

The journal file will be created daily and have the following format: YYYYMMDD.JRN YYYY MM DD .JRN represents the current 4 digit year represents the current 2 digit month represents the current 2 digit day is the file extension
EXAMPLE:
19990701.JRN
U25604-J-Z745-1-7600
October 2004
369
Printing with the Windows GDI Interface
Printers
Types of journal information

Following information can be stored into the electronic journal files:
q q q q q q q q q
date and time device errors transaction reply printer data operation code buffer and requested amount ID-card track 2 data ID-card track 3 data Transaction Reply command of reply dispense data ATM modes (in-service, out-of-service, offline, supervisor mode)
See also section [TOPMSG] and [CUSTMSG] of configuration file CUSTOM.PPF where you can see the default journal output definitions
Printing with the Windows GDI Interface

ProCash/NDC and ProConsult/NDC supports raw printing via the Windows GDI Interface. Printing via GDI requires graphic able printers, which support Windows printing via a Windows printer driver. The printer has to be installed as a Windows printer. In addition an associated port monitor has to be installed to get status information about printed jobs, paper supply status and status of the printer hardware. In Table Printer Models on page 367 you can see what type of printer can or must be installed as a Windows printer. All detailes about configuration and GDI print technology in ProCash/NDC or ProConsult/NDC are described in the GDI Printer Overlay Framework User Guide and ProCash/DDC ProConsult/DDC Installation manual.
370
October 2004
U25604-J-Z745-1-7600
Additional Useful Information

NDC Standard Character Sets
Single Pixel
Single Arabic
U25604-J-Z745-1-7600
October 2004
371
NDC Standard Character Sets Single Graphic 1
Single Graphic 2
Single Graphic 3
372
October 2004
U25604-J-Z745-1-7600
Additional Useful Information Single Alpha 1
Single Alpha 2
U25604-J-Z745-1-7600
October 2004
373
NDC Standard Character Sets Double Arabic
Double Alpha 1
374
October 2004
U25604-J-Z745-1-7600
Additional Useful Information Double Alpha 2
Chinese 1
Chinese 2
U25604-J-Z745-1-7600
October 2004
375
ASCII to EBCDIC Code Conversion Table

GRAPHIC ASCII (HEX) EBCDIC (HEX) GRAPHIC ASCII (HEX) EBCDIC (HEX)
NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CR SO SI DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC
00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B
00 01 02 03 37 2D 2E 2F 16 05 15 0B 0C 0D 0E 0F 10 11 12 13 3C 3D 32 26 18 19 3F 27
SPACE ! " # $ % & ( ) * + , . / 0 1 2 3 4 5 6 7 8 9 : ;
20 21 22 23 24 25 26 27 28 29 2A 2B 2C 2D 2E 2F 30 31 32 33 34 35 36 37 38 39 3A 3B
40 4F 7F 7B 5B 6C 50 7D 4D 5D 5C 4E 6B 60 4B 61 F0 F1 F2 F3 F4 F5 F6 F7 F8 F9 7A 5E
376
October 2004
U25604-J-Z745-1-7600
GRAPHIC
ASCII (HEX)
EBCDIC (HEX)
GRAPHIC
ASCII (HEX)
EBCDIC (HEX)
FS GS RS US @ A B C D E F G H I J K L M N O P Q R S T U V W X Y
1C 1D 1E 1F 40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F 50 51 52 53 54 55 56 57 58 59
1C 1D 1E 1F 7C C1 C2 C3 C4 C5 C6 C7 C8 C9 D1 D2 D3 D4 D5 D6 D7 D8 D9 E2 E3 E4 E5 E6 E7 E8
< = > ? ' a b c d e f g h i j k l m n o p q r s t u v w x y
3C 3D 3E 3F 60 61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 71 72 73 74 75 76 77 78 79
4C 7E 6E 6F Undefined 81 82 83 84 85 86 87 88 89 91 92 93 94 95 96 97 98 99 A2 A3 A4 A5 A6 A7 A8
U25604-J-Z745-1-7600
October 2004
377
Screen Design Worksheet
GRAPHIC
ASCII (HEX)
EBCDIC (HEX)
GRAPHIC
ASCII (HEX)
EBCDIC (HEX)
Z [ \ ] ^ _
5A 5B 5C 5D 5E 5F
E9 4A E0 5A 5F 6D
z { | } DEL
7A 7B 7C 7D 7E 7F
A9 C0 6A D0 A1 07
Screen Design Worksheet

@ A B C D E F G H I J K L M N O 0 1 2 3 4 5 6 7 8 9 : @ A B C D E F G H I J K L M N O 0 1 2 3 4 5 6 7 ; < = > ? P Q R S T U V W
378
October 2004
U25604-J-Z745-1-7600
M-Status & M-Data Reference Tables

The following tables show the CSC-W32 device error classes that are mapped to the NDC Maintenance M-Status and M-Data error codes. The registry path ..\ProTopas\CurrentVersion\CCERRMAP\ is devided in error sub sections where in each section the M-Status and M-Data status code is mapped. In addition you will find reference tables of application error codes (so called LYNX errors as nick name, which can be identified by the class numbers 64xx). The error mapping can be customized in configuration file "CCERRMAP.INA". See ProCash/DDC ProConsult/DDC Installation manual section "Parameter Management" for details about setting up the error mapping table (CCERRMAP.INA) and how to update the contents into the Windows registry. Detailed descriptions about CSC-W32 error codes of each device class are described in the manual CSC-W32 System Messages (available on the Wincor Nixdorf Intranet server).
CSC-W32 Error Classes

Cash Dispenser V1 (old series) (Class: 0007)
The following table lists the M-Status and M-Data codes assigned to the device class Cash Dispenser V1 (old series, will not produced any more).
Table 99: Cash Dispenser V1 (Class: 0007)
Error Error Class Code
0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 DEFA_W DEFA_E 0100_E 0200_E 0300_E 0400_E 1000_E 1100_E 1200_E 1300_E 1400_E 1500_E 1600_E 1700_E 1800_E 1900_E 1A00_E 1B00_E 1C00_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 03 09 08 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00002727272700000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000
Status desription INFO

DISPENSER V1: Default warning if no CSCW32 error found DISPENSER V1: Default error if no CSCW32 error found DISPENSER V1: No cash in collecting tray DISPENSER V1: Transport direction illegal DISPENSER V1: Remaining capacity of reject bin to small DISPENSER V1: Syntax error in job DISPENSER V1: Incorrect block length, error in job DISPENSER V1: Incorrect device specification, error in job DISPENSER V1: Wrong job specification DISPENSER V1: Incorrect job length DISPENSER V1: Addressed cassette does not exist DISPENSER V1: Attempt to read from an unknown area DISPENSER V1: Field name in job unknown DISPENSER V1: Syntax error in job DISPENSER V1: Invalid transport destination DISPENSER V1: Illegal separator used in the job DISPENSER V1: A job was previously issued and is still busy DISPENSER V1: Attempt to write to protected cass. EEPROM DISPENSER V1: There is no PUT PROM in the cash-out controller
U25604-J-Z745-1-7600
October 2004
379

0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 1D00_E 2000_E 2100_E 2200_E 2300_E 2400_E 2500_E 2600_E 2700_E 2800_E 2900_E 2A00_E 2B00_E 2C00_E 2D00_E 3100_E 3200_E 3300_E 3400_E 3500_E 5000_E 5100_E 5110_E 5111_E 5118_E 5119_E 5200_E 5210_E 5211_E 5218_E 5219_E 5300_E 5400_E 5410_E 5418_E 5500_E 5510_E 5511_E 5518_E 5519_E 5610_E 5611_E 5618_E 5619_E 5700_E 5710_E 5800_E 5810_E 5B00_E 5B10_E 5B11_E 5B12_E 5B13_E 5C00_E 5C10_E 5C11_E 5C12_E 5C13_E 5D00_E 5D10_E 5D11_E 5F10_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 03 05 05 05 05 07 02 03 04 01 00 05 20 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05
MData
00000000000000000000 00000303030300000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

DISPENSER V1: Illegal specification transferred in SV job DISPENSER V1: Amount demanded cannot be dispensed DISPENSER V1: Time-out in photosensor of measuring station DISPENSER V1: Time-out photosensor L1 DISPENSER V1: Time-out for collecting tray photosensor L19 DISPENSER V1: Time-out in photosensor L20 for reject cassette DISPENSER V1: Single reject switch defective DISPENSER V1: All banknotes were identified as multiple dispenses DISPENSER V1: The dispenser module is defective DISPENSER V1: Requested amount cannot be dispensed DISPENSER V1: no cassette for the requested currency DISPENSER V1: parameter is larger than 40 banknotes DISPENSER V1: Electronics of the photosensor amplifier defect DISPENSER V1: Unknow device configuration DISPENSER V1: Photosensor L1,L17,L25 DISPENSER V1: Times-out of path monitor in 1. dispenser module DISPENSER V1: Time-out of path monitor in 2. dispenser module DISPENSER V1: Time-out of path monitor in 3. dispenser module DISPENSER V1: Time-out of path monitor in 4. dispenser module DISPENSER V1: Time-out of path monitor in 5. dispenser module DISPENSER V1: Photosensor L17 blocked DISPENSER V1: Photosensor L18 or L22 blocked DISPENSER V1: Photosensor L18 does not become free DISPENSER V1: Photosensor L18 does not become free DISPENSER V1: Photosensor L18 is not reached DISPENSER V1: Photosensor L18 is not reached DISPENSER V1: Photosensor L19 blocked DISPENSER V1: Photosensor L19 does not become free DISPENSER V1: Photosensor L19 does not become free DISPENSER V1: Photosensor L19 is not reached DISPENSER V1: Photosensor L19 is not reached DISPENSER V1: Photosensor L20 blocked DISPENSER V1: Photosensor L21 blocked DISPENSER V1: Photosensor L21 does not become free DISPENSER V1: Photosensor L21 is not reached DISPENSER V1: Photosensor L22 does not become free DISPENSER V1: Photosensor L22 does not become free DISPENSER V1: Photosensor L22 does not become free DISPENSER V1: Photosensor L22 is not reached DISPENSER V1: Photosensor L22 is not reached DISPENSER V1: Photosensor L23 does not become free DISPENSER V1: Photosensor L23 does not become free DISPENSER V1: Photosensor L23 is not reached DISPENSER V1: Photosensor L23 is not reached DISPENSER V1: Does not reach the bottom Collecting tray swivel arm DISPENSER V1: Swivel arm does not reach the bottom DISPENSER V1: Collecting tray swivel arm does not reach the top DISPENSER V1: Swivel arm does not reach the top position DISPENSER V1: Money slot/shutter does not close completely DISPENSER V1: Shutter was not closed completely DISPENSER V1: Shutter was not closed completely DISPENSER V1: Shutter was not closed completely DISPENSER V1: Shutter was not closed completely DISPENSER V1: Money slot/shutter does not open completely DISPENSER V1: Shutter was not open completely DISPENSER V1: Shutter was not completely open DISPENSER V1: Shutter was not completely open DISPENSER V1: Shutter was not completely open DISPENSER V1: Money does not reach L17 DISPENSER V1: Transport motor M2 does not return timing pulses DISPENSER V1: Transport motor M2 does not return timing pulses DISPENSER V1: Photosensor L25 blocked
380
October 2004
U25604-J-Z745-1-7600

0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 5F11_E 5F18_E 5F19_E 6300_E 6310_E 6311_E 6318_E 6319_E 7010_E 7011_E 7012_E 7013_E 7018_E 7019_E 7110_E 7111_E 7112_E 7113_E 7118_E 7119_E 7210_E 7211_E 7218_E 7219_E 7310_E 7311_E 7318_E 7319_E 7410_E 7411_E 7418_E 7419_E 7510_E 7511_E 7518_E 7519_E 7610_E 7611_E 7618_E 7619_E 7710_E 7711_E 7718_E 7719_E 7910_E 7911_E 7918_E 7919_E 7B10_E 7B11_E 7C10_E 7C11_E 8000_E 8001_E 8002_E 8004_E 8005_E 8006_E 8007_E 8009_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 41 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

DISPENSER V1: Photosensor L25 does not become free DISPENSER V1: Photosensor L25 is not reached DISPENSER V1: Photosensor L25 is not reached DISPENSER V1: Money does not reach L21 DISPENSER V1: Photosensor L21 does not become free DISPENSER V1: Photosensor L21 does not become free DISPENSER V1: Photosensor L21 not reached DISPENSER V1: Photosensor L21 is not reached DISPENSER V1: Correct performed retract after TIMEOUT DISPENSER V1: Photosensor L26 does not become free DISPENSER V1: Photosensor L26 unexpectedly covered DISPENSER V1: Photosensor L26 unexpectedly covered DISPENSER V1: Photosensor L26 is not reached DISPENSER V1: Photosensor L26 already free before retract DISPENSER V1: Correct retract performed after TIMEOUT DISPENSER V1: Photosensor L27 does not become free DISPENSER V1: Photosensor L27 unexpectedly covered DISPENSER V1: Photosensor L26 unexpectedly covered DISPENSER V1: Photosensor L27 is not reached DISPENSER V1: Photosensor L27 becomes free nevertheless DISPENSER V1: Photosensor L28 does not become free DISPENSER V1: Photosensor L28 does not become free DISPENSER V1: Photosensor L28 is not reached DISPENSER V1: Photosensor L28 is not reached DISPENSER V1: Photosensor L29 does not become free DISPENSER V1: Photosensor L29 does not become free DISPENSER V1: Photosensor L29 is not reached DISPENSER V1: Photosensor L29 is not reached DISPENSER V1: Photosensor L30 does not become free DISPENSER V1: Photosensor L30 does not become free DISPENSER V1: Photosensor L30 is not reached DISPENSER V1: Photosensor L30 is not reached DISPENSER V1: Photosensor L31 does not become free DISPENSER V1: Photosensor L31 does not become free DISPENSER V1: Photosensor L31 is not reached DISPENSER V1: Photosensor L31 is not reached DISPENSER V1: Photosensor L32 does not become free DISPENSER V1: Photosensor L32 does not become free DISPENSER V1: Photosensor L32 is not reached DISPENSER V1: Photosensor L32 is not reached DISPENSER V1: Photosensor L33 does not become free DISPENSER V1: Photosensor L33 does not become free DISPENSER V1: Photosensor L33 is not reached DISPENSER V1: Photosensor L33 is not reached DISPENSER V1: Photosensor L35 does not become free DISPENSER V1: Photosensor L35 does not become free DISPENSER V1: Photosensor L35 is not reached DISPENSER V1: Photosensor L35 is not reached DISPENSER V1: Photosensor G9 is not reached DISPENSER V1: Photosensor G9 is not reached DISPENSER V1: Photosensor G8 is not reached DISPENSER V1: Photosensor G8 is not reached DISPENSER V1: Invalid cassette slot DISPENSER V1: Error in self-test DISPENSER V1: Internal error Possible hardware error DISPENSER V1: Error occurs only with coded V24 line to the CDM DISPENSER V1: DLL for SW encording, CSCEDSDLL, could not be opened DISPENSER V1: Invalid CRC received with encoded line DISPENSER V1: Keyword specified in parameter block has invalid length DISPENSER V1: The segment selector is invalid
U25604-J-Z745-1-7600
October 2004
381

0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 0007 9000_E 9100_E 9200_E B000_E B100_E B200_E B300_E B400_E B510_E B511_E B512_E B513_E B514_E B523_E B530_E B531_E B534_E B535_E B536_E B537_E B538_E B539_E B544_E B545_E B546_E B547_E B548_E B600_E B700_E B800_E B900_E BA00_E BB00_E BC00_E BD00_E BE00_E C000_E C100_E C200_E C300_E C400_E C500_E C600_E D000_E D100_E D200_E D300_E D400_E D500_E D600_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 07 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

DISPENSER V1: Time-out during comm. with measuring station DISPENSER V1: Time-out during comm. with photosensor amplifier DISPENSER V1: Customer relay not connected DISPENSER V1: Error when releasing the cassette DISPENSER V1: Error when initiating the cassette DISPENSER V1: No reject cassette DISPENSER V1: There is no dispensing cassette DISPENSER V1: Time-out at cassette initialization/release DISPENSER V1: EE-PROM defect DISPENSER V1: Main motor is not working DISPENSER V1: Incorrect motor speed DISPENSER V1: Hardware error (processor) DISPENSER V1: Hardware error (E-PROM) DISPENSER V1: Cassette busy (pressure being accumulated) DISPENSER V1: Reject position cannot be reached DISPENSER V1: Reject position cannot be reached DISPENSER V1: Processor defect DISPENSER V1: RAM defect DISPENSER V1: Checksum error, E-PROM DISPENSER V1: Checksum error, EE-PROM DISPENSER V1: Clutch signal error DISPENSER V1: Dispensing sensor error DISPENSER V1: Evaluation electronics defect DISPENSER V1: Card is not in a device DISPENSER V1: Device could not be identified DISPENSER V1: Job currently not allowed DISPENSER V1: Job unknown DISPENSER V1: Area/subarea selected does not exist DISPENSER V1: No free block DISPENSER V1: Area selected already exists DISPENSER V1: Character cannot be written DISPENSER V1: Attempt to write to a write-protected area DISPENSER V1: Error during processing of the cassette EE-PROM DISPENSER V1: Required area cannot be dissolved DISPENSER V1: Old password incorrect DISPENSER V1: Syntax error in job DISPENSER V1: Cash cannot be dispensed from the selected cassette DISPENSER V1: Cash cannot dispensed from cassette DISPENSER V1: Hardware lock DISPENSER V1: Cannot determine reference value DISPENSER V1: Number of banknotes too high for reference value DISPENSER V1: Not possible to determine the reference value DISPENSER V1: Not possible to accumulate the data-specific pressure DISPENSER V1: The transport key is missing DISPENSER V1: The line key is missing DISPENSER V1: The safe door is not open DISPENSER V1: CODE TEST application command not possible DISPENSER V1: Key test not possible, because encryption is off DISPENSER V1: This message occurs in the dialog DISPENSER V1: This error occurs in the dialog
382
October 2004
U25604-J-Z745-1-7600
Cash Dispenser NG (Classes: 0018/AA18/001D)

The following table lists the M-Status and M-Data codes assigned to the device classes Cash Dispenser NG. Error codes of class "0018" are basic errors. Class AA18 is the USB class assigned to the Cash Dispenser device. Error codes of class "001D" are extended errors.
Table 100: Cash Dispenser NG (Classes: 0018/001D))
0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 DEFA_W DEFA_E E000_W E000_E E001_W E001_E E002_W E002_E E003_W E003_E E004_W E004_E E005_W E005_E EF00_E EF01_E EF02_E EF03_E EF04_E F000_E F001_E F002_E F003_E F004_E F005_E F006_E F007_E F012_E F013_E F015_E FE06_E FE07_E FE08_E FE09_E FE0A_E FE0B_E FE0C_E FE0F_E FE13_E FE16_E FE7A_E FE7B_E FE85_E
Sev.
2 4 2 2 1 1 1 1 1 1 1 0 2 2 4 1 1 1 1 1 4 2 2 2 4 2 2 4 2 2 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 19 19 34 34 09 09 09 09 00 00 05 05 09 09 09 09 09 09 09 09 09 00 09 09 11 11 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER NG: DEFAULT_WARNING" "DISPENSER NG: DEFAULT_ERROR" "DISPENSER NG: No banknotes taken by the customer" "DISPENSER NG: No banknotes taken by the customer" "DISPENSER NG: All banknotes taken by the customer" "DISPENSER NG: All banknotes taken by the customer" "DISPENSER NG: Firmware on disk is newer than SW loaded in CDMNG" "DISPENSER NG: Firmware on disk is newer than SW loaded in CDMNG" "DISPENSER NG: There is no firmware loaded in the CDM-NG" "DISPENSER NG: There is no firmware loaded in the CDM-NG" "DISPENSER NG: DH configured to switch LEDs" "DISPENSER NG: DH configured to switch LEDs" "DISPENSER NG: Handling error at the filling tray" "DISPENSER NG: Handling error at the filling tray" "DISPENSER NG: V24 data not in the expected format" "DISPENSER NG: Invalid CRC received with encrypted line" "DISPENSER NG: Wrong value for FRM_AUTO_LOAD in CSCCNG section" "DISPENSER NG: Wrong value for LED in CSCINI/Registry with CSCCNG" "DISPENSER NG: Firmware loading could not be completed" "DISPENSER NG: Firmware not loaded in CDM-NG" "DISPENSER NG: Wrong syntax" "DISPENSER NG: One of the locks is active" "DISPENSER NG: Error occured during execution of command" "DISPENSER NG: Safe door must be open for this command" "DISPENSER NG: The command cannot be executed at this point of time" "DISPENSER NG: The CDM-NG recognized a problem with the encryption" "DISPENSER NG: If no error found" "DISPENSER NG: Same error as CNG_FRM_DEVICE_NOT_READY" "DISPENSER NG: The same error as CNG_FRM_ERROR with an exception" "DISPENSER NG: The same error as CNG_FRM_CONTEXT with an exception" "DISPENSER NG: COMM reports invalid spec. for the protocol" "DISPENSER NG: A COMM WRITE command is cancelled by the user" "DISPENSER NG: COMM WRITE command could not be executed" "DISPENSER NG: A COMM READ command could not be executed" "DISPENSER NG: A COMM READ command is cancelled by the user" "DISPENSER NG: The COMM driver reports a parity error" "DISPENSER NG: The COMM driver reports a general error" "DISPENSER NG: Peripheral device did not answer" "DISPENSER NG: The channel was not initialized" "DISPENSER NG: The COMM driver reports a break" "DISPENSER NG: The COMM driver reports a overrun error" "DISPENSER NG: The COMM driver reports a frameing error" "DISPENSER NG: The COMM driver could not be opened"
U25604-J-Z745-1-7600
October 2004
383

0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 0018 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 FE89_E FE8B_E FE8C_E FE8D_E FE8E_E FE8F_E FE90_E FE91_E FE92_E FE93_E FE94_E FE95_E FE96_E FE97_E FE98_E FE9C_E FE9D_E FE9E_E FEE0_E FEE1_E FEE2_E FEE3_E FEE4_E FEE5_E FEE6_E FEE7_E FEE8_E FEE9_E FEEA_E FEEB_E FEEC_E FEED_E FEEF_E FEF0_E FEF1_E FEF2_E FEF3_E FEF4_E FEF5_E DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER NG: The pointer pTxData is illegal" "DISPENSER NG: Called function is invalid for CscCommOpen" "DISPENSER NG: The peripheral device does not return an STX" "DISPENSER NG: The peripheral device does not return an ETX" "DISPENSER NG: Block length does not agree with the transmitted block length" "DISPENSER NG: The block ID is invalid" "DISPENSER NG: Received DID does not agree with the transmitted DID" "DISPENSER NG: Wrong command specification" "DISPENSER NG: The received acknowledge type is invalid" "DISPENSER NG: Max no of repeat transmissions reached" "DISPENSER NG: Max no of receive repeats has been reached" "DISPENSER NG: Monitoring time during transmission has been exceeded" "DISPENSER NG: Monitoring time during receive has been exceeded" "DISPENSER NG: Busy time from phys. device excceeded" "DISPENSER NG: The protocol was cancelled" "DISPENSER NG: The length in TxData is 0" "DISPENSER NG: CSCWISODLL could not be found in the PATH" "DISPENSER NG: The CSCWISODLL could not be opened" "DISPENSER NG: The peripheral device did not answer" "DISPENSER NG: Peripheral device did not answer as expected" "DISPENSER NG: The peripheral device is busy" "DISPENSER NG: Peripheral device did not answer as expected" "DISPENSER NG: Max no. of repeat transmissions reached" "DISPENSER NG: Device asked for termination" "DISPENSER NG: Peripheral device did not answer" "DISPENSER NG: Response of device not completely received" "DISPENSER NG: The header of the response is invalid" "DISPENSER NG: DID does not agree with the transmitted DID" "DISPENSER NG: DID does not agree with the transmitted device ID" "DISPENSER NG: Command spec. does not agree with the transmitted command spec." "DISPENSER NG: The response of the device has not been completely received" "DISPENSER NG: A cancel command has been called" "DISPENSER NG: A cancel command has been called" "DISPENSER NG: The command could not be executed" "DISPENSER NG: The command was aborted by the user" "DISPENSER NG: The command could not be executed" "DISPENSER NG: A cancel command could not be executed" "DISPENSER NG: Internal monitoring time exceeded" "DISPENSER NG: Internal error within the CSCWISODLL" "USB/CDM: DEFAULT_WARNING" "USB/CDM: DEFAULT_ERROR" "USB/CDM: Unexpected descriptor was reported from USB device" "USB/CDM: Device not found" "USB/CDM: Not enough memory available" "USB/CDM: It was no endpoint found in the descriptor" "USB/CDM: The creation of the list of USB devices failed" "USB/CDM: USB read command could not be executed in the specified monitoring time" "USB/CDM: USB READ command is cancelled by the user" "USB/CDM: The pointer pData is illegal" "USB/CDM: The length in DataSize is 0 (zero)" "USB/CDM: CRC error has been detected" "USB/CDM: Bit stuffing error has been detected" "USB/CDM: DATA toggle mismatch has been detected" "USB/CDM: STALLPID has been detected, error is reported by the USB host controller" "USB/CDM: USB device is not responding, error is reported by the USB host"
384
October 2004
U25604-J-Z745-1-7600

AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"USB/CDM: PID check has failed, error is reported by the USB host controller" "USB/CDM: Unexpected PID detected, error is reported by the USB host" "USB/CDM: Data overrun error detected, error is reported by the USB host" "USB/CDM: Data underrun error detected, error is reported by the USB host" "USB/CDM: Error code is reserved by the USB host controller driver" "USB/CDM: Error code is reserved by the USB host controller driver" "USB/CDM: Buffer overrun has been detected, error is reported by the USB host" "USB/CDM: Buffer underrun has been detected, error is reported by the USB host" "USB/CDM: Buffer was not accessed, error is reported by the USB host" "USB/CDM: FIFO error has been detected, PCI bus latency was too long" "USB/CDM: XACT error has been detected, error is reported by the USB host" "USB/CDM: Device is babbling, data transfer phase exceeds the USB frame length" "USB/CDM: Data buffer error has been detected, error is reported by the USB host" "USB/CDM: Endpoint has been halted by the USB bus driver USBD" "USB/CDM: Memory allocation attempt has failed, error is reported by the USB bus" "USB/CDM: Invalid URB function code has been passed, error is reported by the USB" "USB/CDM: Invalid parameter has been passed, error is reported by the USB bus" "USB/CDM: There are data transfer requests pending for the device" "USB/CDM: Request has failed, error is reported by the USB bus driver USBD" "USB/CDM: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/CDM: There is not enough bandwidth available, error is reported by the USB bus" "USB/CDM: Internal host controller error has been detected" "USB/CDM: Short transfer has been detected, error is reported by the USB bus" "USB/CDM: Bad start frame has been specified, error is reported by the USB bus" "USB/CDM: Asynchronous request has failed, error is reported by the USB bus driver" "USB/CDM: USB frame control is currently owned, error is reported by the USB bus" "USB/CDM: USB frame control is currently not owned, error is reported by the USB" "USB/CDM: Operation is not supported, error is reported by the USB bus driver" "USB/CDM: Invalid configuration descriptor was reported by the device" "USB/CDM: Operation has failed, error is reported by the USBIO driver" "USB/CDM: Invalid input buffer has been passed to an IOCTL operation" "USB/CDM: Invalid output buffer has been passed to an IOCTL operation" "USB/CDM: There is not enough system memory available to complete the operation" "USB/CDM: There are read or write requests pending, error is reported by the USBIO" "USB/CDM: USB device is already configured, error is reported by the USBIO" "USB/CDM: The USB device is not configured, error is reported by the USBIO driver" "USB/CDM: There are open pipes, error is reported by the USBIO driver" "USB/CDM: Either the handle is already bound to a pipe" "USB/CDM: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/CDM: USB device has been removed from the system" "USB/CDM: Specified control code is not supported"
U25604-J-Z745-1-7600
October 2004
385

AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 AA18 001D 001D 001D 001D 001D 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E DEFA_W DEFA_E 1000_E 1001_E 1010_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 2 4 2 4 4
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 13 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 1000000000000000000 00000000000000000000 00000000000000000000

"USB/CDM: Operation has been timed out, error is reported by the USBIO driver" "USB/CDM: Invalid recipient has been specified" "USB/CDM: Either an invalid request type has been specified" "USB/CDM: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/CDM: Direction of the data transfer request is not supported by that pipe" "USB/CDM: Number of asynchronous data packets specified in an asynchronous read" "USB/CDM: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/CDM: The specified pipe was not found in the current configuration" "USB/CDM: An invalid asynchronous data packet has been specified" "USB/CDM: There are not enough system resources to complete the operation" "USB/CDM: Specified interface was not found in the current configuration" "USB/CDM: Operation cannot be executed while the USB device is in the current state" "USB/CDM: Invalid parameter has been specified with an IOCTL operation" "USB/CDM: Evaluation interval of the USBIO DEMO version has expired" "USB/CDM: Invalid power state has been specified" "USB/CDM: Device has entered a power down state" "USB/CDM: API version reported by the USBIO driver does not match" "USB/CDM: Set configuration operation has failed, error is reported by the USBIO" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CDM: The specified device object does not exist" "USB/CDM: Device object was opened, there is no valid handle to execute the operation" "USB/CDM: Enumeration of the specified devices has failed" "USB/CDM: Invalid parameter has been passed to a function" "USB/CDM: Library setupapi.dll could not be loaded" "USB/CDM: Set configuration request has failed" "USB/CDM: Buffer is too small, error is reported by the USB bus driver USBD" "USB/CDM: Interface was not found, error is reported by the USB bus driver USBD" "USB/CDM: Invalid pipe flags have been specified" "USB/CDM: Operation has been timed out, error is reported by the USB bus driver" "USB/CDM: USB device is gone, error is reported by the USB bus driver USBD" "DISPENSER NG: DEFAULT_WARNING" "DISPENSER NG: DEFAULT_ERROR" "DISPENSER FL: Context error, CDM has received an invalid command" "DISPENSER FL: No response from the CDM" "DISPENSER FL: CDM electronics faulty"
386
October 2004
U25604-J-Z745-1-7600

001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 1011_E 1012_E 1013_E 1014_E 1018_E 1019_E 1020_E 1021_E 1022_E 1023_E 1024_E 1025_E 1026_E 1028_E 1029_E 1031_E 1032_E 1033_E 1034_E 1035_E 1036_E 1041_E 1042_E 1043_E 1044_E 1045_E 1046_E 1051_E 1052_E 1053_E 1054_E 1055_E 1056_E 1061_E 1062_E 1063_E 1064_E 1065_E 1066_E 1070_E 1071_E 1072_E 1073_E 1074_E 1075_E 1076_E 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1090_E 1091_E 1093_E 1098_E 1099_E 1800_E 1801_E 1805_E 1806_E 1807_E
Sev.
4 4 4 4 2 2 4 4 4 4 4 2 2 2 3 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4
MStatus
09 09 00 10 03 12 18 05 05 11 07 09 05 05 13 02 02 02 02 02 02 03 03 03 03 03 03 02 02 02 02 02 02 09 09 09 09 09 09 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 01100000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER FL: No firmware in CDM" "DISPENSER FL: CDM not completely inserted" "DISPENSER FL: Max number of retracts reached" "DISPENSER FL: Minimum configuration not reached." "DISPENSER FL: Note jam during dispensing" "DISPENSER FL: Money jam in the output transport" "DISPENSER FL: Single reject switch faulty/blocked" "DISPENSER FL: Measuring station faulty" "DISPENSER FL: Photosensor amplifier faulty" "DISPENSER FL: Bundle reject switch faulty" "DISPENSER FL: Reject/retract drive faulty/blocked" "DISPENSER FL: Dispensing drive faulty" "DISPENSER FL: Collecting tray defect" "DISPENSER FL: Money slot/shutter jammed or cannot be opened" "DISPENSER FL: Manipulation during delivery" "DISPENSER FL: Too many bundle rejects (cassette 1)" "DISPENSER FL: Too many bundle rejects (cassette 2)" "DISPENSER FL: Too many bundle rejects (cassette 3)" "DISPENSER FL: Too many bundle rejects (cassette 4)" "DISPENSER FL: Too many bundle rejects (cassette 5)" "DISPENSER FL: Too many bundle rejects (cassette 6)" "DISPENSER FL: Note extraction impossible (cassette 1)" "DISPENSER FL: Note extraction impossible (cassette 2)" "DISPENSER FL: Note extraction impossible (cassette 3)" "DISPENSER FL: Note extraction impossible (cassette 4)" "DISPENSER FL: Note extraction impossible (cassette 5)" "DISPENSER FL: Note extraction impossible (cassette 6)" "DISPENSER FL: Too many bad notes (cassette 1)" "DISPENSER FL: Too many bad notes (cassette 2)" "DISPENSER FL: Too many bad notes (cassette 3)" "DISPENSER FL: Too many bad notes (cassette 4)" "DISPENSER FL: Too many bad notes (cassette 5)" "DISPENSER FL: Too many bad notes (cassette 6)" "DISPENSER FL: EE-PROM error (cassette 1)" "DISPENSER FL: EE-PROM error (cassette 2)" "DISPENSER FL: EE-PROM error (cassette 3)" "DISPENSER FL: EE-PROM error (cassette 4)" "DISPENSER FL: EE-PROM error (cassette 5)" "DISPENSER FL: EE-PROM error (cassette 6)" "DISPENSER FL: Photosensor measuring station soiled" "DISPENSER FL: Dispenser sensor soiled (cassette 1)" "DISPENSER FL: Dispenser sensor soiled (cassette 2)" "DISPENSER FL: Dispenser sensor soiled (cassette 3)" "DISPENSER FL: Dispenser sensor soiled (cassette 4)" "DISPENSER FL: Dispenser sensor soiled (cassette 5)" "DISPENSER FL: Dispenser sensor soiled (cassette 6)" "DISPENSER FL: Empty sensor soiled (cassette 1)" "DISPENSER FL: Empty sensor soiled (cassette 2)" "DISPENSER FL: Empty sensor soiled (cassette 3)" "DISPENSER FL: Empty sensor soiled (cassette 4)" "DISPENSER FL: Empty sensor soiled (cassette 5)" "DISPENSER FL: Empty sensor soiled (cassette 6)" "DISPENSER FL: Photosensor L1 soiled" "DISPENSER FL: Photosensor L18 soiled" "DISPENSER FL: Photosensor L21 soiled" "DISPENSER FL: Photosensor L27 soiled" "DISPENSER FL: Photosensor L28 soiled" "DISPENSER V4: Context error, CDM has received an invalid command" "DISPENSER V4: No response from CDM" "DISPENSER V4: Communication problem with the chip card controller" "DISPENSER V4: Communication problem with the chip card" "DISPENSER V4: Hardware configuration not accepted"
U25604-J-Z745-1-7600
October 2004
387

001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 1808_E 1809_E 1810_E 1811_E 1812_E 1813_E 1814_E 1817_E 1818_E 1819_E 1820_E 1821_E 1822_E 1823_E 1824_E 1825_E 1826_E 1828_E 1829_E 1831_E 1832_E 1833_E 1834_E 1835_E 1836_E 1841_E 1842_E 1843_E 1844_E 1845_E 1846_E 1851_E 1852_E 1853_E 1854_E 1855_E 1856_E 1861_E 1862_E 1863_E 1864_E 1865_E 1866_E 1870_E 1871_E 1872_E 1873_E 1874_E 1875_E 1876_E 1881_E 1882_E 1883_E 1884_E 1885_E 1886_E 1890_E 1891_E 1893_E 1895_E 1898_E
Sev.
4 4 4 4 4 4 4 2 2 2 4 4 4 4 4 4 4 3 3 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
05 05 05 05 05 00 10 09 03 09 05 05 05 05 05 05 05 13 13 02 02 02 02 02 02 03 03 03 03 03 03 02 02 02 02 02 02 09 09 09 09 09 09 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 01100000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER V4: Communication problem with the EE-PROM collector" "DISPENSER V4: Service switch open, please insert CDM-V4 completely" "DISPENSER V4: CMD electronics faulty" "DISPENSER V4: Software missing in the CMD" "DISPENSER V4: CMD has not been inserted completely" "DISPENSER V4: The maximal number of retracts has been reached" "DISPENSER V4: Minimum configuration missing" "DISPENSER V4: Gripper belt drive faulty" "DISPENSER V4: Note jam during dispensing" "DISPENSER V4: Gripper transport defective or blocked" "DISPENSER V4: Single reject switch faulty/blocked" "DISPENSER V4: Measuring station faulty" "DISPENSER V4: Photosensor amplifier faulty" "DISPENSER V4: Circle switch faulty/blocked" "DISPENSER V4: Reject/retract drive faulty/blocked" "DISPENSER V4: Dispensing drive faulty/blocked" "DISPENSER V4: Stacker drive faulty /blocked" "DISPENSER V4: Money slot/shutter jammed or cannot be opened" "DISPENSER V4: Manipulation during delivery" "DISPENSER V4: Too many bundle rejects (cassette 1)" "DISPENSER V4: Too many bundle rejects (cassette 2)" "DISPENSER V4: Too many bundle rejects (cassette 3)" "DISPENSER V4: Too many bundle rejects (cassette 4)" "DISPENSER V4: Too many bundle rejects (cassette 5)" "DISPENSER V4: Too many bundle rejects (cassette 6)" "DISPENSER V4: Note extraction impossible (cassette 1)" "DISPENSER V4: Note extraction impossible (cassette 2)" "DISPENSER V4: Note extraction impossible (cassette 3)" "DISPENSER V4: Note extraction impossible (cassette 4)" "DISPENSER V4: Note extraction impossible (cassette 5)" "DISPENSER V4: Note extraction impossible (cassette 6)" "DISPENSER V4: Too many bad notes (cassette 1)" "DISPENSER V4: Too many bad notes (cassette 2)" "DISPENSER V4: Too many bad notes (cassette 3)" "DISPENSER V4: Too many bad notes (cassette 4)" "DISPENSER V4: Too many bad notes (cassette 5)" "DISPENSER V4: Too many bad notes (cassette 6)" "DISPENSER V4: Cassette 1 faulty" "DISPENSER V4: Cassette 2 faulty" "DISPENSER V4: Cassette 3 faulty" "DISPENSER V4: Cassette 4 faulty" "DISPENSER V4: Cassette 5 faulty" "DISPENSER V4: Cassette 6 faulty" "DISPENSER V4: Photosensors measuring station soiled" "DISPENSER V4: Dispenser sensor soiled (cassette 1)" "DISPENSER V4: Dispenser sensor soiled (cassette 2)" "DISPENSER V4: Dispenser sensor soiled (cassette 3)" "DISPENSER V4: Dispenser sensor soiled (cassette 4)" "DISPENSER V4: Dispenser sensor soiled (cassette 5)" "DISPENSER V4: Dispenser sensor soiled (cassette 6)" "DISPENSER V4: Empty sensor soiled (cassette 1)" "DISPENSER V4: Empty sensor soiled (cassette 2)" "DISPENSER V4: Empty sensor soiled (cassette 3)" "DISPENSER V4: Empty sensor soiled (cassette 4)" "DISPENSER V4: Empty sensor soiled (cassette 5)" "DISPENSER V4: Empty sensor soiled (cassette 6)" "DISPENSER V4: Photosensor L1 soiled" "DISPENSER V4: Photosensor L18 soiled" "DISPENSER V4: Control tray single reject L2 soiled" "DISPENSER V4: Money taken light barrier L26/L27 soiled" "DISPENSER V4: Withdrawal photosensor L27 soiled"
388
October 2004
U25604-J-Z745-1-7600

001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 1899_E 189A_E 189D_E 189E_E 4001_E 4010_E 4011_E 4012_E 4013_E 4018_E 4020_E 4021_E 4022_E 4025_E 4026_E 4100_E 4114_E 4119_E 4123_E 4124_E 4128_E 4129_E 4200_E 4214_E 4219_E 4223_E 4224_E 4228_E 4229_E 4300_E 4314_E 4319_E 4328_E 4329_E 4400_E 4414_E 4419_E 4428_E 4429_E 4500_E 4519_E 4529_E 4600_E 4619_E 4629_E 4700_E 4719_E 4729_E 4800_E 4829_E 4900_E 4919_E 4A00_E 4A19_E 4B00_E 4B19_E 4C19_E 4D00_E 4E00_E 4F00_E
Sev.
2 2 2 2 4 4 4 4 4 2 2 4 4 2 2 2 4 2 4 4 2 3 3 4 2 2 2 2 3 2 2 2 2 2 2 2 2 2 3 2 2 2 2 2 2 2 2 2 2 2 2 2 4 2 2 2 4 2 2 2
MStatus
05 05 05 05 09 09 09 09 00 03 05 05 05 03 03 05 07 12 12 07 12 13 14 07 18 18 18 13 18 13 01 04 13 30 13 40 18 30 18 18 18 18 05 18 13 10 18 13 02 14 41 18 03 18 01 19 29 04 01 04
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 01100000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER V4: Output photosensor L28 soiled" "DISPENSER V4: Light barrier of bundle back edge control (presenter) soiled" "DISPENSER V4: Light barrier L2 of reject bin soiled" "DISPENSER V4: Light barrier L3 of reject bin soiled" "DISPENSER NG: No response from the CDM" "DISPENSER NG: CDM electronics faulty" "DISPENSER NG: Software missing in the CDM" "DISPENSER NG: CDM has not been inserted completely" "DISPENSER NG: Max number of retracts reached" "DISPENSER NG: Note jam during dispensing" "DISPENSER NG: Single reject switch faulty/blocked" "DISPENSER NG: Measuring station faulty" "DISPENSER NG: Photosensor amplifier faulty" "DISPENSER NG: Dispensing drive faulty/blocked" "DISPENSER NG: Switching dispensing/transport" "DISPENSER NG: Cassette unknown, missing, reinserted" "DISPENSER NG: Reject cassette missing" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Bundle reject switch faulty/blocked" "DISPENSER NG: Reject/retract drive faulty/blocked" "DISPENSER NG: Shutter cannot be opened/defect" "DISPENSER NG: Manipulation during delivery" "DISPENSER NG: Shutter has been blocked" "DISPENSER NG: Reject cassette not logged on" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Bundle reject switch faulty/blocked" "DISPENSER NG: Reject/retract drive faulty/blocked" "DISPENSER NG: Shutter undefined" "DISPENSER NG: Manipulation in withdrawal position" "DISPENSER NG: Command cannot be executed while Shutter open" "DISPENSER NG: Cash-out cassette(s) missing" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Shutter cannot be closed/undefined" "DISPENSER NG: Manipulation during retract" "DISPENSER NG: Command cannot be executed while Shutter undefined" "DISPENSER NG: No cash-out cassette(s) logged on" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Shutter undefined during retract" "DISPENSER NG: Manipulation during delivery" "DISPENSER NG: Manipulation at cash-out photosensor" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Manipulation during delivery" "DISPENSER NG: Note paths blocked" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Manipulation in withdrawal position" "DISPENSER NG: Max number of retracts reached" "DISPENSER NG: Money jam in the output transport" "DISPENSER NG: Manipulation during retract" "DISPENSER NG: Single reject switch faulty" "DISPENSER NG: Manipulation during delivery" "DISPENSER NG: Self-test activated" "DISPENSER NG: Photosensor covered during withdrawal" "DISPENSER NG: The jam was not eliminated effectively" "DISPENSER NG: Photosensor covered during withdrawal" "DISPENSER NG: Cash-out cassette missing" "DISPENSER NG: Photosensor covered during retract" "DISPENSER NG: Motor defect" "DISPENSER NG: Cassette is empty" "DISPENSER NG: Cassette or dispensing sensor defect" "DISPENSER NG: Cassette becomes empty during dispensing procedure"
U25604-J-Z745-1-7600
October 2004
389

001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 8031_E 8032_E 8033_E 8034_E 8035_E 8036_E 8041_E 8042_E 8043_E 8044_E 8045_E 8046_E 8061_E 8062_E 8063_E 8064_E 8065_E 8066_E 8070_E 8071_E 8072_E 8073_E 8074_E 8075_E 8076_E 8081_E 8082_E 8083_E 8084_E 8085_E 8086_E 8090_E 8091_E 8092_E 8093_E 8094_E 8095_E 8096_E 8097_E 8098_E 8099_E 809A_E 809B_E 809C_E 8151_E 8152_E 8153_E 8154_E 8155_E 8156_E 8251_E 8252_E 8253_E 8254_E 8255_E 8256_E 8300_E 8312_E 8313_E 8314_E 8315_E 8316_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
02 02 02 02 02 02 03 10 10 10 10 10 09 09 09 09 09 09 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 02 02 02 02 02 02 02 02 02 02 02 02 11 09 11 11 11 11
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER NG: Too many bundle rejects (cassette 1)" "DISPENSER NG: Too many bundle rejects (cassette 2)" "DISPENSER NG: Too many bundle rejects (cassette 3)" "DISPENSER NG: Too many bundle rejects (cassette 4)" "DISPENSER NG: Too many bundle rejects (cassette 5)" "DISPENSER NG: Too many bundle rejects (cassette 6)" "DISPENSER NG: Note extraction impossible (cassette 1)" "DISPENSER NG: Note extraction impossible (cassette 2)" "DISPENSER NG: Note extraction impossible (cassette 3)" "DISPENSER NG: Note extraction impossible (cassette 4)" "DISPENSER NG: Note extraction impossible (cassette 5)" "DISPENSER NG: Note extraction impossible (cassette 6)" "DISPENSER NG: Cassette 1 faulty" "DISPENSER NG: Cassette 2 faulty" "DISPENSER NG: Cassette 3 faulty" "DISPENSER NG: Cassette 4 faulty" "DISPENSER NG: Cassette 5 faulty" "DISPENSER NG: Cassette 6 faulty" "DISPENSER NG: Photosensor measuring station soiled" "DISPENSER NG: Dispenser sensor soiled (cassette 1)" "DISPENSER NG: Dispenser sensor soiled (cassette 2)" "DISPENSER NG: Dispenser sensor soiled (cassette 3)" "DISPENSER NG: Dispenser sensor soiled (cassette 4)" "DISPENSER NG: Dispenser sensor soiled (cassette 5)" "DISPENSER NG: Dispenser sensor soiled (cassette 6)" "DISPENSER NG: Empty sensor soiled (cassette 1)" "DISPENSER NG: Empty sensor soiled (cassette 2)" "DISPENSER NG: Empty sensor soiled (cassette 3)" "DISPENSER NG: Empty sensor soiled (cassette 4)" "DISPENSER NG: Empty sensor soiled (cassette 5)" "DISPENSER NG: Empty sensor soiled (cassette 6)" "DISPENSER NG: Photosensor L1 soiled" "DISPENSER NG: Photosensor L18 soiled" "DISPENSER NG: Photosensor L19 soiled" "DISPENSER NG: Photosensor L21 soiled" "DISPENSER NG: Photosensor L22 soiled" "DISPENSER NG: Photosensor L26 soiled" "DISPENSER NG: Photosensor L33 soiled" "DISPENSER NG: Photosensor L35 soiled" "DISPENSER NG: Photosensor L27 soiled" "DISPENSER NG: Photosensor L28 soiled" "DISPENSER NG: Photosensor L29 soiled" "DISPENSER NG: Photosensor L36 soiled" "DISPENSER NG: Photosensor L37 soiled" "DISPENSER NG: Too many double notes (cassette 1)" "DISPENSER NG: Too many double notes (cassette 2)" "DISPENSER NG: Too many double notes (cassette 3)" "DISPENSER NG: Too many double notes (cassette 4)" "DISPENSER NG: Too many double notes (cassette 5)" "DISPENSER NG: Too many double notes (cassette 6)" "DISPENSER NG: Too many bad notes (cassette 1)" "DISPENSER NG: Too many bad notes (cassette 2)" "DISPENSER NG: Too many bad notes (cassette 3)" "DISPENSER NG: Too many bad notes (cassette 4)" "DISPENSER NG: Too many bad notes (cassette 5)" "DISPENSER NG: Too many bad notes (cassette 6)" "DISPENSER NG: Bills left in stacker after output to diverter" "DISPENSER NG: CDM has not been inserted completely" "DISPENSER NG: Cash left in diverter after reset/booting" "DISPENSER NG: Dispensing not possible" "DISPENSER NG: Command could not be executed" "DISPENSER NG: Command could not be executed"
390
October 2004
U25604-J-Z745-1-7600

001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 001D 8318_E 8319_E 8320_E 8321_E 8322_E 8323_E 8324_E 8325_E 8326_E 8328_E 8329_E 8331_E 8332_E 8333_E 8334_E 8335_E 8336_E 8341_E 8342_E 8343_E 8344_E 8345_E 8346_E 8351_E 8352_E 8353_E 8354_E 8355_E 8356_E 8361_E 8362_E 8363_E 8364_E 8365_E 8366_E 8370_E 8371_E 8372_E 8373_E 8374_E 8375_E 8376_E 8381_E 8382_E 8383_E 8384_E 8385_E 8386_E 8390_E 8391_E 8392_E 8393_E 8394_E 8395_E 8396_E 8397_E 8398_E 8399_E 839A_E 839B_E 839C_E 8400_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
11 11 11 05 05 11 11 11 11 05 05 02 02 02 02 02 02 11 11 11 11 11 11 02 02 02 02 02 02 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05 05
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER NG: Note jam during dispense operation" "DISPENSER NG: Note jam in the output transport" "DISPENSER NG: Single reject switch faulty/blocked" "DISPENSER NG: Measuring station faulty" "DISPENSER NG: Photosensor amplifier faulty" "DISPENSER NG: Bundle reject switch faulty/blocked" "DISPENSER NG: Reject/retract drive faulty/blocked" "DISPENSER NG: Dispensing drive faulty/blocked" "DISPENSER NG: Switching dispensing/transport faulty" "DISPENSER NG: Diverter does not reach the end position" "DISPENSER NG: Bills jammed in stacker, under output photosensor" "DISPENSER NG: Too many bundle rejects (casette 1)" "DISPENSER NG: Too many bundle rejects (casette 2)" "DISPENSER NG: Too many bundle rejects (casette 3)" "DISPENSER NG: Too many bundle rejects (casette 4)" "DISPENSER NG: Too many bundle rejects (casette 5)" "DISPENSER NG: Too many bundle rejects (casette 6)" "DISPENSER NG: Note extraction impossible (cassette 1)" "DISPENSER NG: Note extraction impossible (cassette 2)" "DISPENSER NG: Note extraction impossible (cassette 3)" "DISPENSER NG: Note extraction impossible (cassette 4)" "DISPENSER NG: Note extraction impossible (cassette 5)" "DISPENSER NG: Note extraction impossible (cassette 6)" "DISPENSER NG: Too many double notes (cassette 1)" "DISPENSER NG: Too many double notes (cassette 2)" "DISPENSER NG: Too many double notes (cassette 3)" "DISPENSER NG: Too many double notes (cassette 4)" "DISPENSER NG: Too many double notes (cassette 5)" "DISPENSER NG: Too many double notes (cassette 6)" "DISPENSER NG: Cassette 1 faulty" "DISPENSER NG: Cassette 2 faulty" "DISPENSER NG: Cassette 3 faulty" "DISPENSER NG: Cassette 4 faulty" "DISPENSER NG: Cassette 5 faulty" "DISPENSER NG: Cassette 6 faulty" "DISPENSER NG: Photosensors measuring station soiled" "DISPENSER NG: Dispenser sensor soiled (cassette 1)" "DISPENSER NG: Dispenser sensor soiled (cassette 2)" "DISPENSER NG: Dispenser sensor soiled (cassette 3)" "DISPENSER NG: Dispenser sensor soiled (cassette 4)" "DISPENSER NG: Dispenser sensor soiled (cassette 5)" "DISPENSER NG: Dispenser sensor soiled (cassette 6)" "DISPENSER NG: Empty sensor soiled (cassette 1)" "DISPENSER NG: Empty sensor soiled (cassette 2)" "DISPENSER NG: Empty sensor soiled (cassette 3)" "DISPENSER NG: Empty sensor soiled (cassette 4)" "DISPENSER NG: Empty sensor soiled (cassette 5)" "DISPENSER NG: Empty sensor soiled (cassette 6)" "DISPENSER NG: Photosensor L1 soiled" "DISPENSER NG: Photosensor L18 soiled" "DISPENSER NG: Photosensor L19 soiled" "DISPENSER NG: Photosensor L21 soiled" "DISPENSER NG: Photosensor L22 soiled" "DISPENSER NG: Photosensor L26 soiled" "DISPENSER NG: Photosensor L33 soiled" "DISPENSER NG: Photosensor L35 soiled" "DISPENSER NG: Photosensor L27 soiled" "DISPENSER NG: Photosensor L28 soiled" "DISPENSER NG: Photosensor L29 soiled" "DISPENSER NG: Photosensor L36 soiled" "DISPENSER NG: Photosensor L37 soiled" "DISPENSER NG: Banknotes left in the stacker after output"
U25604-J-Z745-1-7600
October 2004
391

001D 001D 001D 001D 001D 001D 001D 8419_E A000_E A100_E A200_E FE38_E FE50_E FFFF_E
Sev.
2 2 2 2 4 4 2
MStatus
05 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DISPENSER NG: Note jam in the output transport" "DISPENSER NG: Wrong command" "DISPENSER NG: Wrong command" "DISPENSER NG: Programming error" "DISPENSER NG: Communication problem" "DISPENSER NG: Communication problem" "DISPENSER NG: Extended error code not computed"
Cash Cheque Deposit Module (Classes: 001A/XX1A)

The following table lists the MDS Status codes assigned to the device classes Cash Cheque Deposit Module (CCDM). Class AA1A is the class IEEE 1394 assigned to device class ChequeInFW. Class BB1A is class IEEE 1394 assigned to device class CashInFW. Class CC1A is class USB assigned to device class CashInFW. Class DDA is class USB assigned to device class ChequeInFW.
Table 101: Cash Cheque Deposit Module (CCDM) (Classes: 001A/XX1A)
Error Class 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A Error Code DEFA_E DEFA_W 0014_E 0015_E 0016_E 0017_E 0018_E 001E_E 0028_E 0029_E 002A_E 002B_E 002C_E 002D_E 002F_E 0030_E 0031_E 003D_E 003E_E 003F_E 0040_E 0041_E 0042_E 0043_E 0044_E 0045_E 0046_E 0047_E 0048_E 0049_E 004A_E 004B_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "CCDM: DEFAULT ERROR" "CCDM: DEFAULT WARNING" "CCDM: General firmware error" "CCDM: Battery on controller board empty" "CCDM: Safety switch active" "CCDM: System interface does not fetch the data from the CCDM fast enough" "CCDM: Invalid or missing configuration" "CCDM: Error magnetic character reader" "CCDM: Error cheque/cash reader" "CCDM: Firmware error cheque/cash reader" "CCDM: Communication problem cheque/cash reader" "CCDM: Data error cheque/cash reader" "CCDM: Note table configuration not Ok" "CCDM: External light in cheque/cash reader" "CCDM: Communication problems (time out)" "CCDM: Communication problems" "CCDM: Cheque/cash reader firmware and CCDM firmware are incompatible" "CCDM: Error photosensor VLS" "CCDM: Error photosensor VLS" "CCDM: Error photosensor VLS" "CCDM: Error photosensor VLS" "CCDM: Error photosensor VLS1" "CCDM: Error photosensor ALS" "CCDM: Error photosensor ALS" "CCDM: Error photosensor ALS" "CCDM: Error photosensor ALS" "CCDM: Error photosensor SLS" "CCDM: Error photosensor SLS" "CCDM: Error photosensor ELS" "CCDM: Error photosensor RLS" "CCDM: Error photosensor RLS" "CCDM: Error photosensor VLS1"
392
October 2004
U25604-J-Z745-1-7600
Error Class 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A
Error Code 004C_E 0050_E 0051_E 0052_E 0053_E 0064_E 0066_E 0067_E 0069_E 006A_E 006C_E 006E_E 006F_E 0070_E 0071_E 0072_E 0073_E 0074_E 0078_E 0079_E 007A_E 0082_E 008C_E 008D_E 0090_E 0091_E 0096_E 0097_E 00AA_E 00B4_E 00B5_E 00C8_E 00C9_E 00CA_E 00CB_E 00CC_E 00CD_E 00CE_E 012D_E 012E_E 0137_E 0138_E 0139_E 0140_E 0141_E 0142_E 0143_E 0144_E 014A_E 014B_E 014C_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "CCDM: Error photosensor ELS" "CCDM: Error photosensor KLS" "CCDM: Error photosensor KLS" "CCDM: Error photosensor KLS" "CCDM: Error photosensor KLS1" "CCDM: Transport error detected before dispensing" "CCDM: VLS6: media too long (media do not pass (VLS6)" "CCDM: VLS7: medium is expected but no media is coming" "CCDM: VLS7: media do not leave VLS7" "CCDM: VLS6: media do not leave VLS6" "CCDM: Faulty extraction detected during dispensing process" "CCDM: Clearing error I/O tray. Media jam in the intermediary transport" "CCDM: Clearing error I/O tray. Media jam in the I/O transport" "CCDM: Clearing error I/O tray. Media do not reached VLS" "CCDM: Clearing error I/O tray. Media jam in the separation area of the dispense" "CCDM: Clearing error I/O tray. Media jam in the intermediary transport" "CCDM: Clearing error I/O tray. Media jam in the intermediary transport" "CCDM: Media jam in reject transport area" "CCDM: Initialization error hinged transport 1 and/or 2" "CCDM: Position error hingend transport 1. The end position is not reached" "CCDM: Position error hinged transport 2. The end position is not reached" "CCDM: Initialization error during setting the bundle width" "CCDM: Error on the cam disk" "CCDM: Error on the cam disk" "CCDM: Shutter cannot be opened/closed." "CCDM: Error on metal detection module" "CCDM: VHS1: hardware error thickness measuring station" "CCDM: VHS1: hardware error thickness measuring station" "CCDM: Initialization error of reject transport" "CCDM: Media jam in reject transport area" "CCDM: Clearing error storage transport. Media did not passed VLS2" "CCDM: Media in front oaf ALS1 or ALS1 defect" "CCDM: ALS1: medium is expected but no media is coming" "CCDM: ALS1: media too long (media do not pass the drum)" "CCDM: ALS1: media is complete recognized but is too long" "CCDM: ALS1: media jam in the drum" "CCDM: ALS1: Media end is not detected during entering the drum" "CCDM: ALS1: Media end do not detected during leaving the drum" "CCDM: Media jam in sensor transport at the 3-way deflector" "CCDM: Media jam in sensor transport at the reject deflector" "CCDM: SLS3: unexpected media during transport from the alignment module" "CCDM: SLS3: unexpected media during transport from the escrow module" "CCDM: SLS3: media jam in sensor transport" "CCDM: SLS1: medium is expected but no media is coming" "CCDM: SLS1: unexpected document during transport from the alignment module" "CCDM: SLS1: unexpected document during transport from the escrow module" "CCDM: Document jam in area -> document deflector -> escrow/reject module" "CCDM: Cheque/cash reader: unexpected media during transport from the alignment module" "CCDM: Document jam at the escrow module ELS1" "CCDM: Document jam between sensor module and cassette/reject module" "CCDM: Document jam between sensor transport and reject transport"
U25604-J-Z745-1-7600
October 2004
393
Error Class 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A
Error Code 014D_E 0190_E 0191_E 0192_E 0193_E 0194_E 0195_E 0196_E 01F5_E 01F6_E 01F7_E 01F8_E 0259_E 025A_E 025B_E 025C_E 025D_E 025E_E 025F_E 0260_E 0261_E 0262_E 0263_E 0264_E 0265_E 0266_E 0267_E 0268_E 8000_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E 800D_E 800E_E 800F_E 8010_E 8011_E 8012_E 8013_E 8014_E 8015_E 8016_E 8017_E 8018_E 8019_E 801A_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "CCDM: Cheque/cash reader: the gap between two media is too small" "CCDM: Escrow tape at ELS2 defective" "CCDM: Escrow tape at ELS3 defective" "CCDM: Document into escrow not expected" "CCDM: Failure in ELS1 area" "CCDM: Document missing or escrow empty" "CCDM: Gap between two notes too long or jam at escrow unit" "CCDM: Initialisation not finished in the spezified time" "CCDM: Incorrect deflector position" "CCDM: Jam between sensor module (paper deflectors) and before RLS1" "CCDM: Document too short" "CCDM: Document too long" "CCDM: RLS1: jam or medium too long" "CCDM: RLS1: medium missing at KLS2 (module entry)" "CCDM: KLS2: unexpected medium at module entry" "CCDM: KLS2: jam or medium too long" "CCDM: Incorrect position of deflector in cassette module" "CCDM: KLS2: medium to retract box missing" "CCDM: Retract cassette: jam or medium too long" "CCDM: Incorrect position of deflector in cassette module 1" "CCDM: KLS2: medium to box 1 missing" "CCDM: Cassette module 1: jam or medium too long" "CCDM: Incorrect position of deflector in cassette module 2" "CCDM: KLS2: medium to box 2 missing" "CCDM: Cassette module 2: jam or medium too long" "CCDM: Media jam KLS5 - KSM" "CCDM: Error in cassette 1 during init" "CCDM: Error in cassette 2 during init" "CCDM: Invalid parameter in command" "CCDM: No document inserted" "CCDM: Function CscPrtRead was called, but no MICR mode via CscPrtControl selected" "CCDM: The CCDM device handler presumes MS-Windows 2000 or MS-Windows XP" "CCDM: There is still a document in the scanner" "CCDM: The CCDM-HW send unknown response to a command" "CCDM: Cannot open raw file (CCDM.RAW)" "CCDM: Error writing raw file (CCDM.RAW)" "CCDM: The shutter could not be opened" "CCDM: The shutter could not be closed" "CCDM: Invalid CRC (check character) received with encrypted line" "CCDM: Wrong value for FRM_LOAD in Registry with CSCCCDM" "CCDM: Firmware loading could not be completed" "CCDM: Wrong value for LED, LED_FLASH or LED_FREQ" "CCDM: Wrong value for MAX_HEIGHT_CHEQUE, MAX_HEIGHT_NOTES, MAX_WIDTH_CHEQUE" "CCDM: Wrong value for the parameter SCAN_FRONT_RED, SCAN_FRONT_GREEN" "CCDM: Wrong value for SHUTTER_BEHAVIOUR in Registry with CSCCCDM" "CCDM: The thread which receives the image/signature data could not started" "CCDM: The thread which receives the image/signature data could not stopped" "CCDM: The pointer " "CCDM: The transferred cheque data (pointer, length) is illegal" "CCDM: No cheque number received while dispensing cheques or sheets" "CCDM: An error occurred while opening a currency file" "CCDM: An error occurred while opening a currency file" "CCDM: The currency file is not dedicated for the installed note sensor" "CCDM: A wrong keyword inside a currency file has been detected" "CCDM: The loading of new currency data not possible"
394
October 2004
U25604-J-Z745-1-7600
Error Class 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A
Error Code 801B_E 801C_E 801D_E 801E_E 801F_E 8020_E 8021_E 8022_E 8023_E 8024_E 8025_E 8026_E 8027_E 8030_E 9201_E 9202_E 9203_E 9204_E 9205_E 9206_E 9207_E 9208_E 9209_E 920A_E 920B_E 920C_E 92FF_E 9300_E 9301_E 9302_E 9303_E 9304_E 9305_E 93FF_E E000_W E001_W E002_W E003_W E004_W E00A_W E00B_W E00C_W E010_W E011_W E014_W E015_W F000_E F001_E F002_E F003_E F004_E F005_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "CCDM: New currency file loaded during installation" "CCDM: Error occurred while opening firmware file" "CCDM: Error occured while reading sensor firmware file" "CCDM: Firmware file is not dedicated for the installed sensor" "CCDM: Wrong value for SENS_FRM_LOAD in Registry with CSCCCDM" "CCDM: Not possible to read the current note table from the note sensor" "CCDM: Too much notes inserted" "CCDM: Timeout while waiting for signature ID" "CCDM: Number of detected cheques on ESCROW and number of scanned cheques different" "CCDM: Error in previous transaction" "CCDM: Error in previous transaction" "CCDM: Error occurred while opening a sensor firmware file" "CCDM: Error occured while reading a CCDM firmware file" "CCDM: The checksum of the signature data of a note is wrong" "CCDM: Illegal arguments calling IMACON.DLL" "CCDM: Cannot open input file" "CCDM: Error reading input" "CCDM: Cannot open output file" "CCDM: Error writing output file" "CCDM: Not enough memory" "CCDM: Image too long" "CCDM: Image too large (for TIF)" "CCDM: Image too small (<1 row)" "CCDM: Error in final conversion step" "CCDM: Error in temp file access" "CCDM: Error loading imareco.dll" "CCDM: IMACON.DLL returned undefined error" "CCDM: Internal error while calling DQF.DLL" "CCDM: Internal error while calling DQF.DLL" "CCDM: Internal error while calling DQF.DLL" "CCDM: Internal error while calling DQF.DLL" "CCDM: Internal error while calling DQF.DLL" "CCDM: Internal error while calling DQF.DLL" "CCDM: DQF.DLL returned undefined error" "CCDM: Tray operating error (e.g. banknotes not correct inserted)" "CCDM: Sheets not inserted in the given time period (reported by CscwCcdmEntry(...))" "CCDM: Some or all notes or checks not taken by the consumer" "CCDM: Some or all notes or checks not taken by the consumer while retract to IO or box" "CCDM: Sheets available in the IO tray, e.g. rejected notes or cheques after dispensing" "CCDM: Loaded firmware older than the firmware found on disk" "CCDM: There is no firmware loaded in the CCCDM" "CCDM: Device handler was configured to switch LEDs when customer action is neccessary" "CCDM: Return of the function CscCcdmInit() if a new currency file has been detected" "CCDM: Returned by the function CscCcdmInit() if a new currency file has been detected" "CCDM: One or more new firmware loaded automatically by the Device Handler" "CCDM: Current loaded note table inconsistant to sensor Firmware" "CCDM: The firmware is not loaded in the CCDM" "CCDM: The parameters of the command have a wrong syntax" "CCDM: One of the locks is active or an error occurred that requires correction" "CCDM: An error occurred during the execution of the command" "CCDM: The safe door must be open for the execution of the actual command" "CCDM: The command cannot be executed at this point of time"
U25604-J-Z745-1-7600
October 2004
395
Error Class 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A 001A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A
Error Code F006_E F007_E F008_E F009_E F00A_E F00B_E F00C_E F00D_E F00E_E F00F_E F010_E F011_E F012_E F0A0_E F0A1_E F0A2_E F0A3_E F0A4_E F0A5_E F0A6_E F0A7_E F0A8_E DEFA_E DEFA_W FE09_E FE0A_E FE9C_E FE9E_E FEA0_E 0100_E 0210_E 0300_E 0305_E 8001_E 8010_E 0100_E 0200_E 0250_E 0270_E 0300_E 0350_E 0370_E 0400_E 0500_E 0572_E 0600_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Status desription INFO "CCDM: The application program tried to dispense a bundle, but the IO-tray is empty" "CCDM: Customer did not remove the bundle until the command has timed out" "CCDM: Cheques or sheets are not correct inserted" "CCDM: CCDM firmware initiated a boot" "CCDM: Note sensor module reports hardware error" "CCDM: Note sensor module reports firmware error" "CCDM: Comunication error reported by the sensor module" "CCDM: Note sensor hase detected an error in the data format" "CCDM: Note sensor has detected an error in the note table" "CCDM: The assignment of a note is wrong" "CCDM: The sensor couldn't read the document (note or cheque)" "CCDM: An error occured during downloding of firmware or currency data" "CCDM: The sensor responded with an unknown error code" "CCDM: Bundle with detected metal in tray" "CCDM: Tray is occupied with not dispensable notes or cheques" "CCDM: A not specified tray error occurred" "CCDM: Shutter error while command CscCcdmCashIn" "CCDM: CscCcdmTransport command received, but the ESCROW is empty" "CCDM: ESCROW full while dispending a bundle" "CCDM: Cheques or sheets on ESCROW while performing the next transaction" "CCDM: Cheques or notes jammed on the ESCROW" "CCDM: There exists no hardware equipment to perform the requested command" "IEEE1394/CCDM_CHQ: Default error" "IEEE1394/CCDM_CHQ: Default warning" "IEEE1394/CCDM_CHQ: IEEE 1394 read command could not be executed in the specified monitoring time" "IEEE1394/CCDM_CHQ: A IEEE 1394 read command is cancelled by the user" "IEEE1394/CCDM_CHQ: The length in DataSize is 0 (zero)" "IEEE1394/CCDM_CHQ: The I1394_TS.DLL could not be opened" "IEEE1394/CCDM_CHQ: The I1394_UB.DLL could not be opened" "IEEE1394/CCDM_CHQ: Internal driver error: Out of memory" "IEEE1394/CCDM_CHQ: Internal driver error: Device is not in working state" "IEEE1394/CCDM_CHQ: Internal driver error: Invalid parameter" "IEEE1394/CCDM_CHQ: Internal driver error: Size of buffer is invalid" "IEEE1394/CCDM_CHQ: Internal driver error: Device not found" "IEEE1394/CCDM_CHQ: Internal driver error: No such device instance" "IEEE1394/CCDM_CHQ: Internal driver error: The operation was cancelled/aborted" "IEEE1394/CCDM_CHQ: Internal driver error: A non-critical error occurred on the adapter" "IEEE1394/CCDM_CHQ: Internal driver error: The application has already opened the specified adapter" "IEEE1394/CCDM_CHQ: Internal driver error: The operation was cancelled because more bus resets" "IEEE1394/CCDM_CHQ: Internal driver error: The operation was cancelled because a 1394 bus reset" "IEEE1394/CCDM_CHQ: Internal driver error: The operation could not be completed because there was a conflict" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: A critical error occurred on the adapter that caused the request to fail" "IEEE1394/CCDM_CHQ: Internal driver error: The operation requested failed because the local adapter is busy" "IEEE1394/CCDM_CHQ: Internal driver error." "IEEE1394/CCDM_CHQ: Internal driver error: The driver detected a bug in its execution logic"
396
October 2004
U25604-J-Z745-1-7600
Error Class AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A
Error Code 0639_E 0645_E 0658_E 0671_E 06B2_E 0700_E 0900_E 0A00_E 0C00_E 0D00_E 0D47_E 0F00_E 0F50_E 0F73_E 1070_E 1100_E 1200_E 1300_E 1313_E 132A_E 1350_E 1409_E 1433_E 1450_E 1500_E 0001_E 0010_E 0030_E 0110_E 0200_E 0220_E 0280_E 0302_E 0304_E 0310_E 0320_E 0340_E 0341_E 0342_E 0350_E 0351_E 0400_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Status desription INFO "IEEE1394/CCDM_CHQ: Internal driver error: The isochronous channel number is already in use" "IEEE1394/CCDM_CHQ: Internal driver error: An isochronous operation failed because of a FIFO" "IEEE1394/CCDM_CHQ: Internal driver error: An isochronous operation failed because of a FIFO underrun" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: An outgoing response packet is not valid" "IEEE1394/CCDM_CHQ: Internal driver error: An operation failed due to some lack of resources other" "IEEE1394/CCDM_CHQ: Internal driver error: The operation requested is not applicable to the channel" "IEEE1394/CCDM_CHQ: Internal driver error: The operation requested is not possible at the channel's current state" "IEEE1394/CCDM_CHQ: Internal driver error: Adapters not identified" "IEEE1394/CCDM_CHQ: Internal driver error: A validation check on a number of isochronous buffers failed" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: The request passed to the miniport was invalid" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: The requested item was not found" "IEEE1394/CCDM_CHQ: Internal driver error: The request valid, but adapter does not support the required functionality" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: The request cannot be transmitted" "IEEE1394/CCDM_CHQ: Internal driver error: The request cannot be transmitted" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: Operation failed" "IEEE1394/CCDM_CHQ: Internal driver error: Operation not supported" "IEEE1394/CCDM_CHQ: Internal driver error: Operation rejected" "IEEE1394/CCDM_CHQ: Internal driver error: Packet pool empty" "IEEE1394/CCDM_CHQ: Internal driver error: Device is removed" "IEEE1394/CCDM_CHQ: Internal driver error: Requested power state transition not allowed" "IEEE1394/CCDM_CHQ: Internal driver error: Operation rejected, device is powered down" "IEEE1394/CCDM_CHQ: Internal driver error: Invalid IO control code" "IEEE1394/CCDM_CHQ: Internal driver error: Requested byte count does not match buffer size" "IEEE1394/CCDM_CHQ: Internal driver error: Input buffer too small" "IEEE1394/CCDM_CHQ: Internal driver error: Output buffer too small" "IEEE1394/CCDM_CHQ: Internal driver error: Handle already used by an object of this type" "IEEE1394/CCDM_CHQ: Internal driver error: Handle already used by an object of another type" "IEEE1394/CCDM_CHQ: Internal driver error: Handle not associated with required object" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error" "IEEE1394/CCDM_CHQ: Internal driver error: Invalid configuration info type"
U25604-J-Z745-1-7600
October 2004
397
Error Class AA1A AA1A AA1A AA1A AA1A AA1A AA1A AA1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A
Error Code 0401_E 0402_E 0403_E 0404_E 8002_E 8003_E 8008_E 8020_E DEFA_E DEFA_W FE09_E FE0A_E FE9C_E FE9E_E FEA0_E 0100_E 0210_E 0300_E 0305_E 8001_E 8010_E 0100_E 0200_E 0250_E 0270_E 0300_E 0350_E 0370_E 0400_E 0500_E 0572_E 0600_E 0639_E 0645_E 0658_E 0671_E 06B2_E 0700_E 0900_E 0A00_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
01 01 01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "IEEE1394/CCDM_CHQ: Internal driver error: Invalid local host info type" "IEEE1394/CCDM_CHQ: Internal driver error: Invalid local host property type" "IEEE1394/CCDM_CHQ: Internal driver error: Unsupported type of lock operation" "IEEE1394/CCDM_CHQ: Internal driver error: Unsupported speed selected" "IEEE1394/CCDM_CHQ: Internal driver error: Device not open" "IEEE1394/CCDM_CHQ: Internal driver error: Request timeout interval has expired" "IEEE1394/CCDM_CHQ: Internal driver error: Invalid parameter in function call" "IEEE1394/CCDM_CHQ: Internal driver error: Memory allocation failed" "IEEE1394/CCDM_CIN: Default error" "IEEE1394/CCDM_CIN: Default warning" "IEEE1394/CCDM_CIN: IEEE 1394 read command could not be executed in the specified monitoring time" "IEEE1394/CCDM_CIN: A IEEE 1394 read command is cancelled by the user" "IEEE1394/CCDM_CIN: The length in DataSize is 0 (zero)" "IEEE1394/CCDM_CIN: The I1394_TS.DLL could not be opened" "IEEE1394/CCDM_CIN: The I1394_UB.DLL could not be opened" "IEEE1394/CCDM_CIN: Internal driver error: Out of memory" "IEEE1394/CCDM_CIN: Internal driver error: Device is not in working state" "IEEE1394/CCDM_CIN: Internal driver error: Invalid parameter" "IEEE1394/CCDM_CIN: Internal driver error: Size of buffer is invalid" "IEEE1394/CCDM_CIN: Internal driver error: Device not found" "IEEE1394/CCDM_CIN: Internal driver error: No such device instance" "IEEE1394/CCDM_CIN: Internal driver error: The operation was cancelled/aborted" "IEEE1394/CCDM_CIN: Internal driver error: A non-critical error occurred on the adapter" "IEEE1394/CCDM_CIN: Internal driver error: The application has already opened the specified adapter" "IEEE1394/CCDM_CIN: Internal driver error: The operation was cancelled because more bus resets" "IEEE1394/CCDM_CIN: Internal driver error: The operation was cancelled because a 1394 bus reset" "IEEE1394/CCDM_CIN: Internal driver error: The operation could not be completed because there was a conflict" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: A critical error occurred on the adapter that caused the request to fail" "IEEE1394/CCDM_CIN: Internal driver error: The operation requested failed because the local adapter is busy" "IEEE1394/CCDM_CIN: Internal driver error." "IEEE1394/CCDM_CIN: Internal driver error: The driver detected a bug in its execution logic" "IEEE1394/CCDM_CIN: Internal driver error: The isochronous channel number is already in use" "IEEE1394/CCDM_CIN: Internal driver error: An isochronous operation failed because of a FIFO" "IEEE1394/CCDM_CIN: Internal driver error: An isochronous operation failed because of a FIFO underrun" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: An outgoing response packet is not valid" "IEEE1394/CCDM_CIN: Internal driver error: An operation failed due to some lack of resources other" "IEEE1394/CCDM_CIN: Internal driver error: The operation requested is not applicable to the channel" "IEEE1394/CCDM_CIN: Internal driver error: The operation requested is not possible at the channel's current state"
398
October 2004
U25604-J-Z745-1-7600
Error Class BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A BB1A CC1A CC1A
Error Code 0C00_E 0D00_E 0D47_E 0F00_E 0F50_E 0F73_E 1070_E 1100_E 1200_E 1300_E 1313_E 132A_E 1350_E 1409_E 1433_E 1450_E 1500_E 0001_E 0010_E 0030_E 0110_E 0200_E 0220_E 0280_E 0302_E 0304_E 0310_E 0320_E 0340_E 0341_E 0342_E 0350_E 0351_E 0400_E 0401_E 0402_E 0403_E 0404_E 8002_E 8003_E 8008_E 8020_E DEFA_W DEFA_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "IEEE1394/CCDM_CIN: Internal driver error: Adapters not identified" "IEEE1394/CCDM_CIN: Internal driver error: A validation check on a number of isochronous buffers failed" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: The request passed to the miniport was invalid" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: The requested item was not found" "IEEE1394/CCDM_CIN: Internal driver error: The request valid, but adapter does not support the required functionality" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: The request cannot be transmitted" "IEEE1394/CCDM_CIN: Internal driver error: The request cannot be transmitted" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: Operation failed" "IEEE1394/CCDM_CIN: Internal driver error: Operation not supported" "IEEE1394/CCDM_CIN: Internal driver error: Operation rejected" "IEEE1394/CCDM_CIN: Internal driver error: Packet pool empty" "IEEE1394/CCDM_CIN: Internal driver error: Device is removed" "IEEE1394/CCDM_CIN: Internal driver error: Requested power state transition not allowed" "IEEE1394/CCDM_CIN: Internal driver error: Operation rejected, device is powered down" "IEEE1394/CCDM_CIN: Internal driver error: Invalid IO control code" "IEEE1394/CCDM_CIN: Internal driver error: Requested byte count does not match buffer size" "IEEE1394/CCDM_CIN: Internal driver error: Input buffer too small" "IEEE1394/CCDM_CIN: Internal driver error: Output buffer too small" "IEEE1394/CCDM_CIN: Internal driver error: Handle already used by an object of this type" "IEEE1394/CCDM_CIN: Internal driver error: Handle already used by an object of another type" "IEEE1394/CCDM_CIN: Internal driver error: Handle not associated with required object" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error" "IEEE1394/CCDM_CIN: Internal driver error: Invalid configuration info type" "IEEE1394/CCDM_CIN: Internal driver error: Invalid local host info type" "IEEE1394/CCDM_CIN: Internal driver error: Invalid local host property type" "IEEE1394/CCDM_CIN: Internal driver error: Unsupported type of lock operation" "IEEE1394/CCDM_CIN: Internal driver error: Unsupported speed selected" "IEEE1394/CCDM_CIN: Internal driver error: Device not open" "IEEE1394/CCDM_CIN: Internal driver error: Request timeout interval has expired" "IEEE1394/CCDM_CIN: Internal driver error: Invalid parameter in function call" "IEEE1394/CCDM_CIN: Internal driver error: Memory allocation failed" "USB/CCDM_CIN: DEFAULT_WARNING" "USB/CCDM_CIN: DEFAULT_ERROR"
U25604-J-Z745-1-7600
October 2004
399
Error Class CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A
Error Code 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "USB/CCDM_CIN: Unexpected descriptor was reported from USB device" "USB/CCDM_CIN: Device not found" "USB/CCDM_CIN: Not enough memory available" "USB/CCDM_CIN: It was no endpoint found in the descriptor" "USB/CCDM_CIN: The creation of the list of USB devices failed" "USB/CCDM_CIN: USB read command could not be executed in the specified monitoring time" "USB/CCDM_CIN: USB READ command is cancelled by the user" "USB/CCDM_CIN: The pointer pData is illegal" "USB/CCDM_CIN: The length in DataSize is 0 (zero)" "USB/CCDM_CIN: CRC error has been detected" "USB/CCDM_CIN: Bit stuffing error has been detected" "USB/CCDM_CIN: DATA toggle mismatch has been detected" "USB/CCDM_CIN: STALLPID has been detected, error is reported by the USB host controller" "USB/CCDM_CIN: USB device is not responding, error is reported by the USB host" "USB/CCDM_CIN: PID check has failed, error is reported by the USB host controller" "USB/CCDM_CIN: Unexpected PID detected, error is reported by the USB host" "USB/CCDM_CIN: Data overrun error detected, error is reported by the USB host" "USB/CCDM_CIN: Data underrun error detected, error is reported by the USB host" "USB/CCDM_CIN: Error code is reserved by the USB host controller driver" "USB/CCDM_CIN: Error code is reserved by the USB host controller driver" "USB/CCDM_CIN: Buffer overrun has been detected, error is reported by the USB host" "USB/CCDM_CIN: Buffer underrun has been detected, error is reported by the USB host" "USB/CCDM_CIN: Buffer was not accessed, error is reported by the USB host" "USB/CCDM_CIN: FIFO error has been detected, PCI bus latency was too long" "USB/CCDM_CIN: XACT error has been detected, error is reported by the USB host" "USB/CCDM_CIN: Device is babbling, data transfer phase exceeds the USB frame length" "USB/CCDM_CIN: Data buffer error has been detected, error is reported by the USB host" "USB/CCDM_CIN: Endpoint has been halted by the USB bus driver USBD" "USB/CCDM_CIN: Memory allocation attempt has failed, error is reported by the USB bus" "USB/CCDM_CIN: Invalid URB function code has been passed, error is reported by the USB" "USB/CCDM_CIN: Invalid parameter has been passed, error is reported by the USB bus" "USB/CCDM_CIN: There are data transfer requests pending for the device" "USB/CCDM_CIN: Request has failed, error is reported by the USB bus driver USBD" "USB/CCDM_CIN: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/CCDM_CIN: There is not enough bandwidth available, error is reported by the USB bus" "USB/CCDM_CIN: Internal host controller error has been detected" "USB/CCDM_CIN: Short transfer has been detected, error is reported by the USB bus" "USB/CCDM_CIN: Bad start frame has been specified, error is reported by the USB bus" "USB/CCDM_CIN: Asynchronous request has failed, error is reported by the USB bus driver"
400
October 2004
U25604-J-Z745-1-7600
Error Class CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A
Error Code 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000
Status desription INFO "USB/CCDM_CIN: USB frame control is currently owned, error is reported by the USB bus" "USB/CCDM_CIN: USB frame control is currently not owned, error is reported by the USB" "USB/CCDM_CIN: Operation is not supported, error is reported by the USB bus driver" "USB/CCDM_CIN: Invalid configuration descriptor was reported by the device" "USB/CCDM_CIN: Operation has failed, error is reported by the USBIO driver" "USB/CCDM_CIN: Invalid input buffer has been passed to an IOCTL operation" "USB/CCDM_CIN: Invalid output buffer has been passed to an IOCTL operation" "USB/CCDM_CIN: There is not enough system memory available to complete the operation" "USB/CCDM_CIN: There are read or write requests pending, error is reported by the USBIO" "USB/CCDM_CIN: USB device is already configured, error is reported by the USBIO" "USB/CCDM_CIN: The USB device is not configured, error is reported by the USBIO driver" "USB/CCDM_CIN: There are open pipes, error is reported by the USBIO driver" "USB/CCDM_CIN: Either the handle is already bound to a pipe" "USB/CCDM_CIN: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/CCDM_CIN: USB device has been removed from the system" "USB/CCDM_CIN: Specified control code is not supported" "USB/CCDM_CIN: Operation has been timed out, error is reported by the USBIO driver" "USB/CCDM_CIN: Invalid recipient has been specified" "USB/CCDM_CIN: Either an invalid request type has been specified" "USB/CCDM_CIN: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/CCDM_CIN: Direction of the data transfer request is not supported by that pipe" "USB/CCDM_CIN: Number of asynchronous data packets specified in an asynchronous read" "USB/CCDM_CIN: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/CCDM_CIN: The specified pipe was not found in the current configuration" "USB/CCDM_CIN: An invalid asynchronous data packet has been specified" "USB/CCDM_CIN: There are not enough system resources to complete the operation" "USB/CCDM_CIN: Specified interface was not found in the current configuration" "USB/CCDM_CIN: Operation cannot be executed while the USB device is in the current state" "USB/CCDM_CIN: Invalid parameter has been specified with an IOCTL operation" "USB/CCDM_CIN: Evaluation interval of the USBIO DEMO version has expired" "USB/CCDM_CIN: Invalid power state has been specified" "USB/CCDM_CIN: Device has entered a power down state" "USB/CCDM_CIN: API version reported by the USBIO driver does not match" "USB/CCDM_CIN: Set configuration operation has failed, error is reported by the USBIO" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600
October 2004
401
Error Class CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A CC1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A
Error Code 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Status desription INFO "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CIN: The specified device object does not exist" "USB/CCDM_CIN: Device object was opened, there is no valid handle to execute the operation" "USB/CCDM_CIN: Enumeration of the specified devices has failed" "USB/CCDM_CIN: Invalid parameter has been passed to a function" "USB/CCDM_CIN: Library setupapi.dll could not be loaded" "USB/CCDM_CIN: Set configuration request has failed" "USB/CCDM_CIN: Buffer is too small, error is reported by the USB bus driver USBD" "USB/CCDM_CIN: Interface was not found, error is reported by the USB bus driver USBD" "USB/CCDM_CIN: Invalid pipe flags have been specified" "USB/CCDM_CIN: Operation has been timed out, error is reported by the USB bus driver" "USB/CCDM_CIN: USB device is gone, error is reported by the USB bus driver USBD" "USB/CCDM_CHQ: DEFAULT_WARNING" "USB/CCDM_CHQ: DEFAULT_ERROR" "USB/CCDM_CHQ: Unexpected descriptor was reported from USB device" "USB/CCDM_CHQ: Device not found" "USB/CCDM_CHQ: Not enough memory available" "USB/CCDM_CHQ: It was no endpoint found in the descriptor" "USB/CCDM_CHQ: The creation of the list of USB devices failed" "USB/CCDM_CHQ: USB read command could not be executed in the specified monitoring time" "USB/CCDM_CHQ: USB READ command is cancelled by the user" "USB/CCDM_CHQ: The pointer pData is illegal" "USB/CCDM_CHQ: The length in DataSize is 0 (zero)" "USB/CCDM_CHQ: CRC error has been detected" "USB/CCDM_CHQ: Bit stuffing error has been detected" "USB/CCDM_CHQ: DATA toggle mismatch has been detected" "USB/CCDM_CHQ: STALLPID has been detected, error is reported by the USB host controller" "USB/CCDM_CHQ: USB device is not responding, error is reported by the USB host" "USB/CCDM_CHQ: PID check has failed, error is reported by the USB host controller" "USB/CCDM_CHQ: Unexpected PID detected, error is reported by the USB host" "USB/CCDM_CHQ: Data overrun error detected, error is reported by the USB host" "USB/CCDM_CHQ: Data underrun error detected, error is reported by the USB host" "USB/CCDM_CHQ: Error code is reserved by the USB host controller driver" "USB/CCDM_CHQ: Error code is reserved by the USB host controller driver" "USB/CCDM_CHQ: Buffer overrun has been detected, error is reported by the USB host" "USB/CCDM_CHQ: Buffer underrun has been detected, error is reported by the USB host" "USB/CCDM_CHQ: Buffer was not accessed, error is reported by the USB host" "USB/CCDM_CHQ: FIFO error has been detected, PCI bus latency was too long"
402
October 2004
U25604-J-Z745-1-7600
Error Class DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A
Error Code 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Status desription INFO "USB/CCDM_CHQ: XACT error has been detected, error is reported by the USB host" "USB/CCDM_CHQ: Device is babbling, data transfer phase exceeds the USB frame length" "USB/CCDM_CHQ: Data buffer error has been detected, error is reported by the USB host" "USB/CCDM_CHQ: Endpoint has been halted by the USB bus driver USBD" "USB/CCDM_CHQ: Memory allocation attempt has failed, error is reported by the USB bus" "USB/CCDM_CHQ: Invalid URB function code has been passed, error is reported by the USB" "USB/CCDM_CHQ: Invalid parameter has been passed, error is reported by the USB bus" "USB/CCDM_CHQ: There are data transfer requests pending for the device" "USB/CCDM_CHQ: Request has failed, error is reported by the USB bus driver USBD" "USB/CCDM_CHQ: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/CCDM_CHQ: There is not enough bandwidth available, error is reported by the USB bus" "USB/CCDM_CHQ: Internal host controller error has been detected" "USB/CCDM_CHQ: Short transfer has been detected, error is reported by the USB bus" "USB/CCDM_CHQ: Bad start frame has been specified, error is reported by the USB bus" "USB/CCDM_CHQ: Asynchronous request has failed, error is reported by the USB bus driver" "USB/CCDM_CHQ: USB frame control is currently owned, error is reported by the USB bus" "USB/CCDM_CHQ: USB frame control is currently not owned, error is reported by the USB" "USB/CCDM_CHQ: Operation is not supported, error is reported by the USB bus driver" "USB/CCDM_CHQ: Invalid configuration descriptor was reported by the device" "USB/CCDM_CHQ: Operation has failed, error is reported by the USBIO driver" "USB/CCDM_CHQ: Invalid input buffer has been passed to an IOCTL operation" "USB/CCDM_CHQ: Invalid output buffer has been passed to an IOCTL operation" "USB/CCDM_CHQ: There is not enough system memory available to complete the operation" "USB/CCDM_CHQ: There are read or write requests pending, error is reported by the USBIO" "USB/CCDM_CHQ: USB device is already configured, error is reported by the USBIO" "USB/CCDM_CHQ: The USB device is not configured, error is reported by the USBIO driver" "USB/CCDM_CHQ: There are open pipes, error is reported by the USBIO driver" "USB/CCDM_CHQ: Either the handle is already bound to a pipe" "USB/CCDM_CHQ: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/CCDM_CHQ: USB device has been removed from the system" "USB/CCDM_CHQ: Specified control code is not supported" "USB/CCDM_CHQ: Operation has been timed out, error is reported by the USBIO driver" "USB/CCDM_CHQ: Invalid recipient has been specified" "USB/CCDM_CHQ: Either an invalid request type has been specified" "USB/CCDM_CHQ: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/CCDM_CHQ: Direction of the data transfer request is not supported by that pipe" "USB/CCDM_CHQ: Number of asynchronous data packets specified in an asynchronous read"
U25604-J-Z745-1-7600
October 2004
403
Error Class DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A DD1A
Error Code 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Status desription INFO "USB/CCDM_CHQ: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/CCDM_CHQ: The specified pipe was not found in the current configuration" "USB/CCDM_CHQ: An invalid asynchronous data packet has been specified" "USB/CCDM_CHQ: There are not enough system resources to complete the operation" "USB/CCDM_CHQ: Specified interface was not found in the current configuration" "USB/CCDM_CHQ: Operation cannot be executed while the USB device is in the current state" "USB/CCDM_CHQ: Invalid parameter has been specified with an IOCTL operation" "USB/CCDM_CHQ: Evaluation interval of the USBIO DEMO version has expired" "USB/CCDM_CHQ: Invalid power state has been specified" "USB/CCDM_CHQ: Device has entered a power down state" "USB/CCDM_CHQ: API version reported by the USBIO driver does not match" "USB/CCDM_CHQ: Set configuration operation has failed, error is reported by the USBIO" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/CCDM_CHQ: The specified device object does not exist" "USB/CCDM_CHQ: Device object was opened, there is no valid handle to execute the operation" "USB/CCDM_CHQ: Enumeration of the specified devices has failed" "USB/CCDM_CHQ: Invalid parameter has been passed to a function" "USB/CCDM_CHQ: Library setupapi.dll could not be loaded" "USB/CCDM_CHQ: Set configuration request has failed" "USB/CCDM_CHQ: Buffer is too small, error is reported by the USB bus driver USBD" "USB/CCDM_CHQ: Interface was not found, error is reported by the USB bus driver USBD" "USB/CCDM_CHQ: Invalid pipe flags have been specified" "USB/CCDM_CHQ: Operation has been timed out, error is reported by the USB bus driver" "USB/CCDM_CHQ: USB device is gone, error is reported by the USB bus driver USBD"
404
October 2004
U25604-J-Z745-1-7600
Encryption Decryption Module (Class: 000F)

The following table lists the M-Status and M-Data codes assigned to the device class Encryption Decryption Module (EDM).
Table 102: Encryption Decryption Module (EDM) (Class: 000F)
000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F 000F DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E 800D_E 800E_E 800F_E 8010_E 8011_E 8040_E 8041_E 8050_E 8051_E 8052_E 8053_E 8060_E 8061_E 8062_E 8101_E 8102_E 8103_E 8104_E 8105_E 8107_E 810B_E 810C_E 810E_E 8111_E 8112_E 8113_E 8114_E 8115_E 8116_E 8118_E 8119_E 811A_E 811B_E 811C_E 811E_E 811F_E 8120_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 98 98 11 98 01 02 02 02 02 56 02 12 00 56 12 12 12 12 00 11 02 02 01 02 07 02 00 13 56 00 11 38 07 56 16 02 56 70 70 70 70 70 70 70 02 02 07 07 07 07
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"EDM: DEFAULT_WARNING" "EDM: DEFAULT_ERROR" "EDM: An undefined internal error has occurred in the firmware" "EDM: The firmware cannot execute the command" "EDM: Key address not allowed" "EDM: EDM RAM error" "EDM: Parity error in key" "EDM: Internal hardware E-PROM error" "EDM: Internal hardware EE-PROM error" "EDM: The EDM command does not exist" "EDM: The EDM key RAM is defective" "EDM: The transferred data length is invalid" "EDM: An invalid block ID is in the V24 protocal" "EDM: The device ID is invalid" "EDM: Command already transferred to the EDM firmware" "EDM: Command length and data length invalid" "EDM: Output parameters not defined" "EDM: Data contains invalid ASCII characters" "EDM: Wrong sequence of commands" "EDM: Wrong ID" "EDM: No transaction active, command cannot be executed" "EDM: No or not enough PIN numbers entered" "EDM: Key-splitting E-PROM not connected or wrong" "EDM: Checksum of key-splitting E-PROM is wrong" "EDM: Parity error in key of the key-splitting E-PROM" "EDM: Invalid table charater in key-splitting E-PROM" "EDM: V24 connection PC to EDM was/is interrupted" "EDM: Battery problem of EDM" "EDM: EPP detects an error when entering a key" "EDM: EDM not initialized" "EDM: Length in the parameter cannot be divided by eight" "EDM: The DLL command specification is invalid" "EDM: The command parameters are incorrect" "EDM: Invalid key number" "EDM: Error during data transmission" "EDM: Initialize vector has wrong length" "EDM: No free space in IV array" "EDM: System could not provide dynamic memory" "EDM: Wrong maximum PIN length with job EdmStartPin" "EDM: Wrong minimum PIN length with job EdmStartPin" "EDM: Invalid field for leading zeros in the PIN structure" "EDM: Invalid field for acknowledge key in the PIN structure" "EDM: Invalid mode in the PIN structure" "EDM: Wrong PIN position in PIN field" "EDM: Wrong structure entry in field TestMode" "EDM: Invalid number of PIN digits" "EDM: This API is not supported by the device handler" "EDM: The API could not be loaded" "EDM: This function cannot be accessed with the firmware" "EDM: Cannot access full length of data area in a structure" "EDM: Invalid encryption mode specified for key reset" "EDM: The total protocol monitoring time has been exceeded"
U25604-J-Z745-1-7600
October 2004
405

000F 000F 000F 000F 000F 000F 000F 8121_E 8122_E 8123_E 8124_E 8125_E 8126_E 8127_E
Sev.
2 2 2 2 2 2 2
MStatus
00 00 07 12 12 13 75
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000

"EDM: The maximum number of receive repeats has been reached" "EDM: The received acknowledge type is invalid" "EDM: Common protocol error in EPP response data" "EDM: Key Generating Keys in REGISTRY/CSCINI are not correct" "EDM: Invalid character in KGK Keyset in REGISTRY/CSCINI" "EDM: Error when encrypting a Masterkey" "EDM: The check is negativ"
Encryption Decryption Software (Class: 0011)

The following table lists the M-Status and M-Data codes assigned to the device class Encryption Decryption Software (EDS).
Table 103: Encryption Decryption Software (EDS) (Class: 0011)
0011 0011 0011 0011 0011 0011 0011 0011 0011 0011 0011 0011 DEFA_W DEFA_E 8001_E 8002_E 8003_E 8004_E 8005_E 8007_E 8008_E 800A_E 800B_E 800C_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 13 22 13 01 13 13 01 11 56 13
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"EDS: DEFAULT_WARNING" "EDS: DEFAULT_ERROR" "EDS: No transport key is loaded" "EDS: An invalid transport key is available" "EDS: No CBC key is loaded" "EDS: An invalid CBC key is available" "EDS: No initial vector loaded" "EDS: No ECB key is loaded" "EDS: An invalid ECB key is available" "EDS: The length specified in the parameter block is zero" "EDS: Length specified in param. block cannot divided by eight" "EDS: Error while accessing the CSCEDSKEY key file"
406
October 2004
U25604-J-Z745-1-7600
Card Reader (Class: 0008/AA08)

The following table lists the M-Status and M-Data codes assigned to the device class Card Reader. Class AA08 is the USB class assigned to the Card Reader.
Table 104: Card Reader (Class: 0008/AA08)
Error Class 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 Error Code DEFA_E DEFA_W 0000_W 0000_E 1004_E 1005_E 100F_E 1015_E E000_E E001_E E002_E E004_E E006_E E009_E E00A_E E00B_E E00C_E E00D_E E00E_E E00F_E E010_E E011_E E012_E E013_E E014_E E015_E E016_E E017_E E01E_E E01F_E E028_E E070_E E071_E E100_E E101_E E102_E E104_E E180_E E182_E E183_E E184_E E185_E E186_E E187_E 7FFB_E 7FFC_E 7FFD_E 7FFE_E 7FFF_E F001_E F002_E F003_E Sev. 2 2 0 2 2 2 4 4 2 2 2 2 4 4 2 3 2 3 3 4 3 3 2 2 0 2 2 2 4 4 2 4 4 2 3 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 MStatus 00 00 00 00 03 03 03 03 00 00 13 00 20 20 18 07 08 13 13 20 13 13 08 11 03 03 04 03 20 20 12 20 20 03 18 18 18 03 03 03 03 03 03 03 03 03 03 03 03 03 20 20 MData 0000000000 0000000000 0000000000 0000000000 0205000000 0205000000 0205000000 0205000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0205000000 0000000000 0000000000 Status desription INFO "CARD READER: DEFAULT_ERROR" "CARD READER: DEFAULT_WARNING" "CARD READER: If no warning found" "CARD READER: If no error found" "CARD READER: Length of input buffer in parameter block invalid" "CARD READER: Length of output buffer in parameter block invalid" "CARD READER: Device handler not initialized (card trap ?)" "CARD READER: Executed command not permitted or possible" "CARD READER: Invalid command (internal error)" "CARD READER: Parameters not correct" "CARD READER: Command cannot be executed" "CARD READER: Invalid data with a command" "CARD READER: Command cannot be executed, device is in maintanance mode " "CARD READER: Internal encountered in firmware of IDCU device" "CARD READER: Card jammed (possible manipulation)" "CARD READER: The sensors report an invalid position of the shutter" "CARD READER: Sensors are defect" "CARD READER: Card too long" "CARD READER: Card too short" "CARD READER: Memory error" "CARD READER: Card has shifted" "CARD READER: The card is jammed" "CARD READER: Shutter switch or width switch defective" "CARD READER: Mechanical error of IDCU device" "CARD READER: The data read from the cards have the wrong parity" "CARD READER: The card data could not be read" "CARD READER: The WRITE data is faulty on the card" "CARD READER: The end character only was found on the track when read" "CARD READER: Power fail during a command" "CARD READER: The DSR signal is in OFF status" "CARD READER: The card was removed during transport from the output position to the reject box" "CARD READER: There is presently no firmware loaded in the device" "CARD READER: There was a problem during the download of the firmware" "CARD READER: The card data could not be read" "CARD READER: Card jammed in optional stacker unit (possible manipulation)" "CARD READER: No card in the dispenser" "CARD READER: Card is clamped by the ID card unit" "CARD READER: The chip card controller in the IDU or the IC card is defect" "CARD READER: The chip card could not be activated" "CARD READER: The chip card could not be deactivated" "CARD READER: An error occurred during communication with the chip card" "CARD READER: A forced interruption command was received from the chip card" "CARD READER: Error detected in response from the chip card" "CARD READER: The ATR information of the card is incorrect" "CARD READER: Chip card mode or SAM configuration not supported" "CARD READER: Flash memory needs to be reset" "CARD READER: Trigger level of transactions has been reached" "CARD READER: Error occurred during access of SEL DH to switch LED's" "CARD READER: Temporary power failure between last job and current job" "CARD READER: Maximum number of tries per command is reached" "CARD READER: Not enough data received from IDCU" "CARD READER: Error in communication protocal with IDCU"
U25604-J-Z745-1-7600
October 2004
407
Error Class 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 0008 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08
Error Code F004_E F005_E F006_E F007_E F008_E F009_E F00B_E F00C_E F00D_E F00E_E F00F_E F011_E F012_E F013_E F014_E F015_E F016_E F017_E F018_E F019_E F01A_E F01B_E F01C_E F01D_E F01E_E F020_E F021_E F022_E F023_E F024_E F025_E F026_E F027_E F028_E F029_E F02A_E F02B_E F02C_E F02D_E F02E_E F02F_E FE08_E FE09_E FE7B_E DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E
Sev. 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 2 2 2 4 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus 20 20 20 20 20 20 20 20 20 20 20 04 20 00 00 05 00 20 00 00 00 20 00 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 FE08000000 FE09000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000
Status desription INFO "CARD READER: V24 line error No ENQ was sent" "CARD READER: Response from IDCU is incorrect" "CARD READER: Invalid status" "CARD READER: Invalid parameters with the command" "CARD READER: Internal RESET not possible (internal error)" "CARD READER: TYPE in Registry/CSCINI with CSCIDU is incorrect" "CARD READER: False value for ID_PM in Registry/CSCINI with CSCIDU" "CARD READER: Wrong value for ID_PD in Registry/CSCINI with CSCIDU" "CARD READER: False value for ID_WV in Registry/CSCINI with CSCIDU" "CARD READER: False value for ID_SH in Registry/CSCINI with CSCIDU" "CARD READER: Command is not available in this configuration" "CARD READER: V24 send command not terminated with correct length" "CARD READER: NAK received as a response" "CARD READER: CANCEL not possible" "CARD READER: A CsclduCancel command has already been sent" "CARD READER: No card in the unit to perform the command" "CARD READER: Wrong value for MSS in Registry/CSCINI with CSCIDU" "CARD READER: The device handler MSS could not be loaded" "CARD READER: Wrong value for ID_WT in Registry/CSCINI with CSCIDU" "CARD READER: Wrong value for ID_RJ in Registry/CSCINI with CSCIDU" "CARD READER: Wrong value for MAN_RECOG in Registry/CSCINI with CSCIDU" "CARD READER: The device handler CSCWHYBDLL could not be loaded" "CARD READER: Wrong value for LED in Registry/CSCINI with CSCIDU" "CARD READER: The device handler CSCWSELDLL could not be loaded" "CARD READER: The device handler CSCWCITDLL could not be loaded" "CARD READER: The specified firmware file has not the correct format" "CARD READER: The parameter INIT_LOADER_CTL in the Registry/CSCINI is incorrect" "CARD READER: DH CSCWTRADLL and /or CSCWESTDLL could not be loaded" "CARD READER: TRANSACTION-ACTIVE in the Registry/CSCINI is incorrect" "CARD READER: TRANSACTION-TRIGGER in the Registry/CSCINI is incorrect" "CARD READER: ERROR-MAPPING in the Registry/CSCINI is incorrect" "CARD READER: Parameter CHIPMODE in registry is incorrect" "CARD READER: Wrong value for ENTRY_HANDLING" "CARD READER: Device handler CSCSWI.DLL could not be loaded" "CARD READER: Device handler CSCEDS.DLL could not be loaded" "CARD READER: Device handler CSCEDM.DLL could not be loaded" "CARD READER: Device handler CSCWICM.DLL could not be loaded" "CARD READER: Parameter SAMx_MODE incorrect" "CARD READER: Parameter SAM incorrect" "CARD READER: Device handler CSCWV2X.DLL could not be loaded" "CARD READER: Device handler CSCWHUS.DLL could not be loaded" "CARD READER: V24 Communication timeout" "CARD READER: V24 Communication timeout" "CARD READER: Initialization failed" "USB/IDCU: DEFAULT_WARNING" "USB/IDCU: DEFAULT_ERROR" "USB/IDCU: Unexpected descriptor was reported from USB device" "USB/IDCU: Device not found" "USB/IDCU: Not enough memory available" "USB/IDCU: It was no endpoint found in the descriptor" "USB/IDCU: The creation of the list of USB devices failed" "USB/IDCU: USB read command could not be executed in the specified monitoring time" "USB/IDCU: USB READ command is cancelled by the user" "USB/IDCU: The pointer pData is illegal" "USB/IDCU: The length in DataSize is 0 (zero)" "USB/IDCU: CRC error has been detected" "USB/IDCU: Bit stuffing error has been detected" "USB/IDCU: DATA toggle mismatch has been detected" "USB/IDCU: STALLPID has been detected, error is reported by the USB host controller" "USB/IDCU: USB device is not responding, error is reported by the USB host" "USB/IDCU: PID check has failed, error is reported by the USB host controller"
408
October 2004
U25604-J-Z745-1-7600
Error Class AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08
Error Code 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E
Sev. 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000
Status desription INFO "USB/IDCU: Unexpected PID detected, error is reported by the USB host" "USB/IDCU: Data overrun error detected, error is reported by the USB host" "USB/IDCU: Data underrun error detected, error is reported by the USB host" "USB/IDCU: Error code is reserved by the USB host controller driver" "USB/IDCU: Error code is reserved by the USB host controller driver" "USB/IDCU: Buffer overrun has been detected, error is reported by the USB host" "USB/IDCU: Buffer underrun has been detected, error is reported by the USB host" "USB/IDCU: Buffer was not accessed, error is reported by the USB host" "USB/IDCU: FIFO error has been detected, PCI bus latency was too long" "USB/IDCU: XACT error has been detected, error is reported by the USB host" "USB/IDCU: Device is babbling, data transfer phase exceeds the USB frame length" "USB/IDCU: Data buffer error has been detected, error is reported by the USB host" "USB/IDCU: Endpoint has been halted by the USB bus driver USBD" "USB/IDCU: Memory allocation attempt has failed, error is reported by the USB bus" "USB/IDCU: Invalid URB function code has been passed, error is reported by the USB" "USB/IDCU: Invalid parameter has been passed, error is reported by the USB bus" "USB/IDCU: There are data transfer requests pending for the device" "USB/IDCU: Request has failed, error is reported by the USB bus driver USBD" "USB/IDCU: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/IDCU: There is not enough bandwidth available, error is reported by the USB bus" "USB/IDCU: Internal host controller error has been detected" "USB/IDCU: Short transfer has been detected, error is reported by the USB bus" "USB/IDCU: Bad start frame has been specified, error is reported by the USB bus" "USB/IDCU: Asynchronous request has failed, error is reported by the USB bus driver" "USB/IDCU: USB frame control is currently owned, error is reported by the USB bus" "USB/IDCU: USB frame control is currently not owned, error is reported by the USB" "USB/IDCU: Operation is not supported, error is reported by the USB bus driver" "USB/IDCU: Invalid configuration descriptor was reported by the device" "USB/IDCU: Operation has failed, error is reported by the USBIO driver" "USB/IDCU: Invalid input buffer has been passed to an IOCTL operation" "USB/IDCU: Invalid output buffer has been passed to an IOCTL operation" "USB/IDCU: There is not enough system memory available to complete the operation" "USB/IDCU: There are read or write requests pending, error is reported by the USBIO" "USB/IDCU: USB device is already configured, error is reported by the USBIO" "USB/IDCU: The USB device is not configured, error is reported by the USBIO driver" "USB/IDCU: There are open pipes, error is reported by the USBIO driver" "USB/IDCU: Either the handle is already bound to a pipe" "USB/IDCU: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/IDCU: USB device has been removed from the system" "USB/IDCU: Specified control code is not supported" "USB/IDCU: Operation has been timed out, error is reported by the USBIO driver" "USB/IDCU: Invalid recipient has been specified" "USB/IDCU: Either an invalid request type has been specified" "USB/IDCU: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/IDCU: Direction of the data transfer request is not supported by that pipe" "USB/IDCU: Number of asynchronous data packets specified in an asynchronous read" "USB/IDCU: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/IDCU: The specified pipe was not found in the current configuration" "USB/IDCU: An invalid asynchronous data packet has been specified" "USB/IDCU: There are not enough system resources to complete the operation" "USB/IDCU: Specified interface was not found in the current configuration" "USB/IDCU: Operation cannot be executed while the USB device is in the current state" "USB/IDCU: Invalid parameter has been specified with an IOCTL operation" "USB/IDCU: Evaluation interval of the USBIO DEMO version has expired" "USB/IDCU: Invalid power state has been specified" "USB/IDCU: Device has entered a power down state" "USB/IDCU: API version reported by the USBIO driver does not match" "USB/IDCU: Set configuration operation has failed, error is reported by the USBIO" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600
October 2004
409
Error Class AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08 AA08
Error Code 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev. 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000
Status desription INFO "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/IDCU: The specified device object does not exist" "USB/IDCU: Device object was opened, there is no valid handle to execute the operation" "USB/IDCU: Enumeration of the specified devices has failed" "USB/IDCU: Invalid parameter has been passed to a function" "USB/IDCU: Library setupapi.dll could not be loaded" "USB/IDCU: Set configuration request has failed" "USB/IDCU: Buffer is too small, error is reported by the USB bus driver USBD" "USB/IDCU: Interface was not found, error is reported by the USB bus driver USBD" "USB/IDCU: Invalid pipe flags have been specified" "USB/IDCU: Operation has been timed out, error is reported by the USB bus driver" "USB/IDCU: USB device is gone, error is reported by the USB bus driver USBD"
410
October 2004
U25604-J-Z745-1-7600
Deposit Module (Class: 0017/AA17)

The following table lists the M-Status and M-Data codes assigned to the device class Deposit Module. Class AA17 is the USB class assigned to Deposit Module.
Table 105: Deposit Module (Class: 0017/AA17)
0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 1420_E 8000_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E 800D_E 800E_E 800F_E 8010_E 8011_E 8012_E 8013_E 8014_E 8015_E 8016_E 8017_E 8018_E 8019_E 8020_E 8021_E 8022_E 8023_E 8024_E 8025_E 80F0_E 8102_E 8104_E 8105_E 8106_E 8107_E 8108_E 8200_E
Sev.
2 4 2 2 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 07 07 07 00 07 07 07 00 01 01 00 07 02 02 04 00 01 08 07 07 01 07 01 01 01 08 07 08 07 07 01 07 07 06 02 01 00 07 07 07 07 07 07 07
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 8000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000

"DEPOSIT: DEFAULT_WARNING" "DEPOSIT: DEFAULT_ERROR" "DEPOSIT: Device handler was configured to switch LEDs" "DEPOSIT: There is no firmware loaded" "DEPOSIT: Cannot open or read the firmware file on disk" "DEPOSIT: API-Function CscDpsOpen check validity of FW on Disk" "DEPOSIT: Communication problem" "DEPOSIT: Undefined error code" "DEPOSIT: The DLL command specification is invalid" "DEPOSIT: The DLL command specification is invalid" "DEPOSIT: Deposit cassette not installed correctly" "DEPOSIT: Job cannot be executed because envelope in transport path" "DEPOSIT: Envelope jammed in transport path" "DEPOSIT: Operator did not insert envelope during monitoring period" "DEPOSIT: The envelope starting the feed operation" "DEPOSIT: Undefined status Defective sensor" "DEPOSIT: The dispensed envelope has not been" "DEPOSIT: Shutter could not be closed" "DEPOSIT: No envelopes available any longer" "DEPOSIT: Dispenser sensor could not detect the envelope" "DEPOSIT: End of the envelope reached before all chars could be printed" "DEPOSIT: Print unit motor error" "DEPOSIT: Envelope under print head sensor could not detect envelope" "DEPOSIT: Envelope in printer conveyor sensor could not detect envelope" "DEPOSIT: Motor problem of conveyer transport" "DEPOSIT: Envelope in conveyor transport entry sensor could not detect envelope" "DEPOSIT: Envelope in middle of conveyor transport sensor could not detect envelope" "DEPOSIT: Envelope in conveyor transport exit sensor could not detect envelope" "DEPOSIT: No connection between print unit and conveyor transport" "DEPOSIT: No envelope dispenser or programming error" "DEPOSIT: Print head not locked or not available" "DEPOSIT: The inserted envelope is too long" "DEPOSIT: No envelope detected after command" "DEPOSIT: Failure of Envelope in shutter sensor" "DEPOSIT: Error when opening the bandage" "DEPOSIT: Error when closing the bandage" "DEPOSIT: Operator did not remove the offered envelope" "DEPOSIT: An error has occurred in the shutter" "DEPOSIT: An error has occurred on the bandage" "DEPOSIT: Job cancelled by CANCEL" "DEPOSIT: Cannot access full length of data area in a structure" "DEPOSIT: Active function cannot be cancelled" "DEPOSIT: Cannot open the firmware file" "DEPOSIT: Cannot read the firmware file to be loaded" "DEPOSIT: Detect invalid firmware file data" "DEPOSIT: Detect an invalid checksum of the firmware file data" "DEPOSIT: A V24 WRITE command could not be executed"
U25604-J-Z745-1-7600
October 2004
411

0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 0017 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 8201_E 8202_E 8203_E 8204_E 8205_E 8206_E 8207_E 8208_E 8209_E 8300_E FE08_E FE09_E FE85_E DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E
Sev.
2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
07 07 07 07 07 07 07 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000

"DEPOSIT: A V24 READ command could not be executed" "DEPOSIT: Max no. of repeat transmissions reached" "DEPOSIT: Max no. of receive repeats has been reached" "DEPOSIT: Repetition counter expired" "DEPOSIT: The received acknowledge type is invalid" "DEPOSIT: Repetition counter expired" "DEPOSIT: Expected block length does not match transmitted block length" "DEPOSIT: Error occurred during the CscDpsEntry job" "DEPOSIT: The CscDpsEntry job was cancelled by the user" "DEPOSIT: Wrong value for LED in Registry/CSCINI with CSCDPS" "DEPOSIT: V24 Communication timeout" "DEPOSIT: V24 Communication timeout" "DEPOSIT: Communication problem" "USB/DEP: DEFAULT_WARNING" "USB/DEP: DEFAULT_ERROR" "USB/DEP: Unexpected descriptor was reported from USB device" "USB/DEP: Device not found" "USB/DEP: Not enough memory available" "USB/DEP: It was no endpoint found in the descriptor" "USB/DEP: The creation of the list of USB devices failed" "USB/DEP: USB read command could not be executed in the specified monitoring time" "USB/DEP: USB READ command is cancelled by the user" "USB/DEP: The pointer pData is illegal" "USB/DEP: The length in DataSize is 0 (zero)" "USB/DEP: CRC error has been detected" "USB/DEP: Bit stuffing error has been detected" "USB/DEP: DATA toggle mismatch has been detected" "USB/DEP: STALLPID has been detected, error is reported by the USB host controller" "USB/DEP: USB device is not responding, error is reported by the USB host" "USB/DEP: PID check has failed, error is reported by the USB host controller" "USB/DEP: Unexpected PID detected, error is reported by the USB host" "USB/DEP: Data overrun error detected, error is reported by the USB host" "USB/DEP: Data underrun error detected, error is reported by the USB host" "USB/DEP: Error code is reserved by the USB host controller driver" "USB/DEP: Error code is reserved by the USB host controller driver" "USB/DEP: Buffer overrun has been detected, error is reported by the USB host" "USB/DEP: Buffer underrun has been detected, error is reported by the USB host" "USB/DEP: Buffer was not accessed, error is reported by the USB host" "USB/DEP: FIFO error has been detected, PCI bus latency was too long" "USB/DEP: XACT error has been detected, error is reported by the USB host" "USB/DEP: Device is babbling, data transfer phase exceeds the USB frame length" "USB/DEP: Data buffer error has been detected, error is reported by the USB host" "USB/DEP: Endpoint has been halted by the USB bus driver USBD" "USB/DEP: Memory allocation attempt has failed, error is reported by the USB bus" "USB/DEP: Invalid URB function code has been passed, error is reported by the USB" "USB/DEP: Invalid parameter has been passed, error is reported by the USB bus" "USB/DEP: There are data transfer requests pending for the device" "USB/DEP: Request has failed, error is reported by the USB bus driver USBD"
412
October 2004
U25604-J-Z745-1-7600

AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000

"USB/DEP: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/DEP: There is not enough bandwidth available, error is reported by the USB bus" "USB/DEP: Internal host controller error has been detected" "USB/DEP: Short transfer has been detected, error is reported by the USB bus" "USB/DEP: Bad start frame has been specified, error is reported by the USB bus" "USB/DEP: Asynchronous request has failed, error is reported by the USB bus driver" "USB/DEP: USB frame control is currently owned, error is reported by the USB bus" "USB/DEP: USB frame control is currently not owned, error is reported by the USB" "USB/DEP: Operation is not supported, error is reported by the USB bus driver" "USB/DEP: Invalid configuration descriptor was reported by the device" "USB/DEP: Operation has failed, error is reported by the USBIO driver" "USB/DEP: Invalid input buffer has been passed to an IOCTL operation" "USB/DEP: Invalid output buffer has been passed to an IOCTL operation" "USB/DEP: There is not enough system memory available to complete the operation" "USB/DEP: There are read or write requests pending, error is reported by the USBIO" "USB/DEP: USB device is already configured, error is reported by the USBIO" "USB/DEP: The USB device is not configured, error is reported by the USBIO driver" "USB/DEP: There are open pipes, error is reported by the USBIO driver" "USB/DEP: Either the handle is already bound to a pipe" "USB/DEP: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/DEP: USB device has been removed from the system" "USB/DEP: Specified control code is not supported" "USB/DEP: Operation has been timed out, error is reported by the USBIO driver" "USB/DEP: Invalid recipient has been specified" "USB/DEP: Either an invalid request type has been specified" "USB/DEP: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/DEP: Direction of the data transfer request is not supported by that pipe" "USB/DEP: Number of asynchronous data packets specified in an asynchronous read" "USB/DEP: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/DEP: The specified pipe was not found in the current configuration" "USB/DEP: An invalid asynchronous data packet has been specified" "USB/DEP: There are not enough system resources to complete the operation" "USB/DEP: Specified interface was not found in the current configuration" "USB/DEP: Operation cannot be executed while the USB device is in the current state" "USB/DEP: Invalid parameter has been specified with an IOCTL operation" "USB/DEP: Evaluation interval of the USBIO DEMO version has expired" "USB/DEP: Invalid power state has been specified" "USB/DEP: Device has entered a power down state" "USB/DEP: API version reported by the USBIO driver does not match" "USB/DEP: Set configuration operation has failed, error is reported by the USBIO" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600
October 2004
413

AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 AA17 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000

"USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DEP: The specified device object does not exist" "USB/DEP: Device object was opened, there is no valid handle to execute the operation" "USB/DEP: Enumeration of the specified devices has failed" "USB/DEP: Invalid parameter has been passed to a function" "USB/DEP: Library setupapi.dll could not be loaded" "USB/DEP: Set configuration request has failed" "USB/DEP: Buffer is too small, error is reported by the USB bus driver USBD" "USB/DEP: Interface was not found, error is reported by the USB bus driver USBD" "USB/DEP: Invalid pipe flags have been specified" "USB/DEP: Operation has been timed out, error is reported by the USB bus driver" "USB/DEP: USB device is gone, error is reported by the USB bus driver USBD"
Vandal Guard (Class: 0015)

The following table lists the M-Status and M-Data codes assigned to the device class Vandal Guard (Panel Protection Door (PPD)). This device is used in CSC450 ATMs only.
Table 106: Vandal Guard (Class: 0015)
0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 DEFA_W DEFA_E 8000_E 8020_E 8021_E 8022_E 8023_E 8024_E 8030_E 8040_E 8041_E 8043_E 8044_E 8050_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 03 03 03 03 03 03 03 03 03 03 03 02
MData
0000 0000 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0201

"VANDAL GUARD: DEFAULT_WARNING" "VANDAL GUARD: DEFAULT_ERROR" "VANDAL GUARD: Unknown internal error has occurred in FW" "VANDAL GUARD: Block ID wrong" "VANDAL GUARD: Device number wrong" "VANDAL GUARD: Job specification wrong" "VANDAL GUARD: Job longer than receive buffer" "VANDAL GUARD: Syntax error in job specification" "VANDAL GUARD: No motion messages when door is opened" "VANDAL GUARD: The hardware error cannot be specified closer" "VANDAL GUARD: E-PROM faulty" "VANDAL GUARD: Processor faulty" "VANDAL GUARD: Checksum error in hardware RAM" "VANDAL GUARD: The door could not be fully opened"
414
October 2004
U25604-J-Z745-1-7600

0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 8051_E 8052_E 8053_E 8054_E 8055_E 80E0_E 80E1_E 80E2_E 80E3_E 80E4_E 80E5_E 80E6_E 80E7_E 80E8_E 80E9_E 80EA_E 80EB_E 80EC_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8109_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
01 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03 03
MData
0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100 0100

"VANDAL GUARD: Door cannot be closed completely" "VANDAL GUARD: Contact bar without function" "VANDAL GUARD: Light barrier is dirty or faulty" "VANDAL GUARD: Door is difficult to operate" "VANDAL GUARD: Firmware not loaded or started" "VANDAL GUARD: Charaters 1-3 not equal to decimal digits" "VANDAL GUARD: Block length not in valid area (3-250)" "VANDAL GUARD: Block length not equal to received block length" "VANDAL GUARD: Invalid Block ID (N,E)" "VANDAL GUARD: Invalid Device ID" "VANDAL GUARD: Invalid Job ID" "VANDAL GUARD: Invalid Job parameter" "VANDAL GUARD: The last command has not been processed yet" "VANDAL GUARD: Firmware not loaded or started" "VANDAL GUARD: Wrong file length" "VANDAL GUARD: Memory for program module too small" "VANDAL GUARD: Invalid file check charater" "VANDAL GUARD: Hardware not functioning/faulty" "VANDAL GUARD: OS/2 reports error during memory request" "VANDAL GUARD: Wrong/undefined charater job acknowledgment" "VANDAL GUARD: Invalid data in response from peripheral controller" "VANDAL GUARD: Invalid MODSEG ID in FRM file on the system" "VANDAL GUARD: The file *CTF was not found" "VANDAL GUARD: The file *FRM was not found" "VANDAL GUARD: Error when opening a *CTF file" "VANDAL GUARD: Error when opening a *FRM file" "VANDAL GUARD: Invalid data in teh *CTF file"
Motorized Door (Class: 000E)

The following table lists the M-Status and M-Data codes assigned to the device class Motorized Door. This device is used in CSC250/550 old series ATMs only.
Table 107: Motorized Door (Class: 000E)
000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E 000E DEFA_W DEFA_E 8020_E 8021_E 8022_E 8023_E 8024_E 8025_E 8030_E 8031_E 8040_E 8041_E 8042_E 8043_E 8045_E 8046_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DOOR MODULE: DEFAULT_WARNING" "DOOR MODULE: DEFAULT_ERROR" "DOOR MODULE: Block ID wrong" "DOOR MODULE: Device number wrong" "DOOR MODULE: Job specification wrong" "DOOR MODULE: Return buffer too small" "DOOR MODULE: Syntax error in job specification" "DOOR MODULE: The last command has not been processed yet" "DOOR MODULE: The door could not be fully opened" "DOOR MODULE: Door cannot be closed completely Door is blocked" "DOOR MODULE: The hardware error cannot be specified closer" "DOOR MODULE: E-PROM faulty" "DOOR MODULE: EE-PROM faulty" "DOOR MODULE: Processor faulty" "DOOR MODULE: One or more light barriers are dirty or faulty" "DOOR MODULE: Door open/close issued more than 3 times quickly"
U25604-J-Z745-1-7600
October 2004
415

000E 000E 000E 000E 000E 000E 000E 8050_E 8051_E 8052_E 8100_E 8101_E 8102_E 8FFF_E
Sev.
2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"DOOR MODULE: Values of a number of photosensors are below the minimum value" "DOOR MODULE: The light bulb in the cash output tray is defective" "DOOR MODULE: Door does not reach the open end position when opened" "DOOR MODULE: OS/2 report an error when requesting memory for a data buffer" "DOOR MODULE: The status of a non-existent light barrier was requested" "DOOR MODULE: The MDM hardware does not respond at OPEN" "DOOR MODULE: Internal error"
Printer (Class: 0032)

The following table lists the M-Status and M-Data codes assigned to printer class 0032.
Table 108: Printer (Class: 0032)
0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 0032 DEFA_W DEFA_E 1420_E 1424_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E 800D_E 800E_E 800F_E 8010_E 8011_E 8012_E 8013_E 8014_E 8015_E
Sev.
2 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 08 00 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 40000800 00000000 00000000 00000000 20000800 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"PRINTER: DEFAULT_WARNING" "PRINTER: DEFAULT_ERROR" "PRINTER: Communication problem" "PRINTER: The device is currently locked by another user" "PRINTER: If no error found" "PRINTER: If no error found" "PRINTER: Printer control code file could not be opened" "PRINTER: Bad format of the printer control code file" "PRINTER: Invalid format of the macro" "PRINTER: The format file is not available" "PRINTER: OPEN error of the format file" "PRINTER: Bad format of the format file" "PRINTER: Error while transmitting the status buffer" "PRINTER: The print buffer is too small" "PRINTER: No text from the FMT file was found" "PRINTER: If no error found" "PRINTER: If no error found" "PRINTER: If no error found" "PRINTER: Formatting error" "PRINTER: If no error found" "PRINTER: The printer-specific DLL could not be opened" "PRINTER: If no error found" "PRINTER: Unknown string format specification" "PRINTER: If no error found" "PRINTER: If no error found"
416
October 2004
U25604-J-Z745-1-7600
Printer ND71/74/98/9A/9C/9E/TH30 (Class: 0033)

The following table lists the M-Status and M-Data assigned to printer class 0033.
0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 0033 DEFA_W DEFA_E 0001_W 0001_E 0002_E 0003_E 1017_E 1420_E 8005_E 8009_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8109_E 810A_E 810B_E 810C_E 810D_E 810E_E 810F_E 8110_E 8111_E 8112_E 8201_E 8202_E 8203_E 8204_E 8205_E 8206_E 8207_E 8208_E FE08_E FE09_E
Sev.
2 4 2 2 2 2 4 4 2 2 2 2 2 2 2 2 2 2 4 4 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4
MStatus
00 00 00 00 00 16 00 00 00 08 08 08 08 00 08 08 08 05 05 07 07 05 05 07 07 08 08 08 08 08 08 08 08 08 08 08 08 08 08
MData
00000000 00000000 00000000 02000000 02000000 00000002 00000000 00000000 00000000 40000800 40000800 40000800 40000800 00000000 40000800 40000800 40000800 08000000 08000000 40000002 40000002 08000000 08000000 40000000 40000000 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800

"JRN/REC: DEFAULT_WARNING" "JRN/REC: DEFAULT_ERROR" "JRN/REC: Communication problem" "JRN/REC: Receipt paper low warning" "JRN/REC: Journal paper low warning" "JRN/REC: Receipt still in output at OPEN on printer" "JRN/REC: Communication problem" "JRN/REC: Communication problem" "JRN/REC: Wrong macro format" "JRN/REC: Printer hardware error" "JRN/REC: Printer hardware error" "JRN/REC: Loss of command after device error" "JRN/REC: Hardware error in memory test (RAM and ROM)" "JRN/REC: Syntax error in the ESCAPE sequence" "JRN/REC: Parity error" "JRN/REC: A checksum error is set" "JRN/REC: Short-term power failed" "JRN/REC: Paper-out condition or paper jam" "JRN/REC: Loss of command after receipt paper end" "JRN/REC: Receipt paper jam" "JRN/REC: Loss of command after paper jam" "JRN/REC: Paper-out condition or paper jam" "JRN/REC: Loss of command after receipt paper end" "JRN/REC: Journal paper tear" "JRN/REC: Loss of command after receipt paper end" "JRN/REC: The door is not properly closed" "JRN/REC: Loss of command because of open CSC door" "JRN/REC: Printer hardware error" "JRN/REC: Black dot mark not found" "JRN/REC: Cannot open control file ND9X.INI" "JRN/REC: Cannot read control file ND9X.INI" "JRN/REC: Cannot open a file or checksum incorrect" "JRN/REC: Cannot read the file to be loaded" "JRN/REC: File to be loaded has invalid module id" "JRN/REC: Expected response from firmware loader is incorrect" "JRN/REC: Invalid logo type for ND9C" "JRN/REC: Loaded file does not fit to printer hardware" "JRN/REC: V24 Communication timeout" "JRN/REC: V24 Communication timeout"
U25604-J-Z745-1-7600
October 2004
417
Printer ND75/75S/94 (Class: 0034)

0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 0034 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8109_E 810A_E 810B_E 810C_E 810D_E 810E_E 810F_E 8110_E 8111_E 8112_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 02 02 02 07 04 02 01 05 00 05 00 05 00 01 00 02 04 02 02
MData
0000000000000000 0000000000000000 0200000000000000 0200000000000000 4000000000000000 4000000000000000 4000000000000000 4000000000000000 4000000000000000 0800000000000000 0400000000000000 4000080000000000 4000000100000000 4000010000000000 4000000000000000 4000010000000000 4000000000000000 4000010000000000 4000000000000000 4000100000000000 4000000000000000 4000400000000000 4000000000000000 4000080000000000 4000080000000000

"ND94: DEFAULT_WARNING" "ND94: DEFAULT_ERROR" "ND94: Paper-low condition" "ND94: Weekend limit reached" "ND94: FF command caused a feed to 1st line of 10th document" "ND94: The set limit for the reject box has been exceeded" "ND94: Error in the low-voltage power supply" "ND94: The carrier was moved manually" "ND94: Error in memory test(RAM and ROM)" "ND94: The paper is used up completely" "ND94: Paper jam, bad/missing mark on paper" "ND94: Reset switch on the drum is faulty" "ND94: The cutter is binding" "ND94: Paper jam in paper path" "ND94: FF command caused a feed to 1st line of 10th document" "ND94: Receipt(s) not removed before issuing a new print job" "ND94: Access to a non-existent font module" "ND94: Forms in gripper after 2 reject attempts" "ND94: External light when adjusting photosensor" "ND94: Rocker does not return to home position after cutting" "ND94: Remove stacker door does not open" "ND94: Cheque counter in Backup RAM deleted" "ND94: Print control mark not found" "ND94: Printer hardware error" "ND94: If no error found"
Printer ND79 (Class: 0035)

0035 0035 0035 0035 0035 0035 0035 0035 DEFA_W DEFA_E 0001_E 0003_E 0004_E 8100_E 8101_E 8103_E
Sev.
2 4 2 2 2 2 2 2
MStatus
00 00 00 05 00 23 02 02
MData
0000000000000000 0000000000000000 0200000000000000 4000010000000000 0200000000000000 4000000000000000 4000000000000000 4000000000000000

"ND79: DEFAULT_WARNING" "ND79: DEFAULT_ERROR" "ND79: Receipt paper low warning" "ND79: Still a receipt in the output chute at an OPEN" "ND79: Receipt paper low warning (last receipt printing)" "ND79: Printer hardware error" "ND79: Loss of command after device error" "ND79: Syntax error in the ESCAPE sequence for loading LOGO"
418
October 2004
U25604-J-Z745-1-7600

0035 0035 0035 0035 0035 0035 0035 0035 0035 0035 8104_E 8106_E 8107_E 8108_E 8109_E 810A_E 8111_E 8112_E 8113_E 8114_E
Sev.
2 2 2 2 2 2 2 2 2 2
MStatus
02 23 07 07 05 05 00 00 00 00
MData
4000000000000000 4000000000000000 0800000000000000 0800000000000000 4000010000000000 4000010000000000 4000010000000000 4000010000000000 4000010000000000 4000010000000000

"ND79: A parity error is returned from a printer" "ND79: Short-term power failed on during operation" "ND79: Paper-out condition or paper jam" "ND79: Loss of command after receipt paper end" "ND79: Receipt paper jam" "ND79: Loss of command after paper jam" "ND79: Printer hardware error" "ND79: The printer is in service position" "ND79: Defective control instruction" "ND79: Job lost while printer in service position"
Printer ND99 (Class: 0038)

0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 0038 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 1005_E 1420_E 1424_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8109_E 810A_E 810B_E 810C_E 810D_E 810E_E 810F_E 8110_E FE08_E FE09_E FE0B_E FE85_E
Sev.
2 4 2 2 2 2 2 2 4 4 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4
MStatus
00 00 00 08 08 08 08 08 00 00 03 03 09 08 08 08 08 05 00 08 08 01 08 08 08 08 08 08 08 08 08
MData
00000000 00000000 02000000 40000000 40000000 40000000 40000000 40000800 00000000 00000000 40000004 40000004 40000000 00000000 00000000 40000000 40000000 08000000 40000000 40000000 40000000 40010000 40000000 40000000 40000000 00000000 40000000 40000000 40000000 40000000 40000000

"RECEIPT: DEFAULT_WARNING" "RECEIPT: DEFAULT_ERROR" "RECEIPT: Receipt paper low warning" "RECEIPT: API function CscPrtOpen checks FW load file SWC728HEX" "RECEIPT: FW on disk different than SW loaded in printer" "RECEIPT: There is no firmware loaded" "RECEIPT: Loaded PRT FW has a release smaller than 0305" "JRN/REC: Printer hardware error" "PRINTER: Communication problem" "PRINTER: The device is currently locked by another user" "RECEIPT: Hardware error receipt presenter module" "RECEIPT: Printer cannot recognize a top-of-form mark" "RECEIPT: The print head is lifted" "RECEIPT: Syntax error in ESCAPE sequence for loading LOGO" "RECEIPT: A parity error is returned from a printer" "RECEIPT: HW error occured at power ON (self-test)" "RECEIPT: Short-term power failed on during operation" "RECEIPT: Paper-out, current form still printed" "RECEIPT: Non-existing user-defined character font selected" "RECEIPT: The printer buffer is overflow" "RECEIPT: Loss of command" "RECEIPT: Cutter not in home position" "RECEIPT: Syntax error in ESCAPE sequence for loading user chars." "RECEIPT: Firmware HEX-file SWC728HEX has no valid firmware version" "RECEIPT: Recognized a faulty firmware load file SWC728HEX" "RECEIPT: No firmware is loaded" "RECEIPT: Loaded PRT FW has a release smaller than 0305" "RECEIPT: V24 Communication timeout" "RECEIPT: V24 Communication timeout" "RECEIPT: V24 Communication timeout" "RECEIPT: V24 Communication problem"
U25604-J-Z745-1-7600
October 2004
419
Printer ND97/TH97/TP01/NP01/TP05/NP05 (Class: 0039)

The following table lists the M-Status and M-Data codes assigned to class 0039. Class AA39 is the USB class assigned to the Statement printer device.
0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 0039 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 DEFA_W DEFA_E 1006_E 1427_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8109_E 810A_E 810B_E 810C_E 810D_E 810E_E 8111_E 8112_E 8113_E 8120_E 8121_E 8122_E 8123_E 8124_E 8125_E FE08_E FE09_E FE85_E DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E
Sev.
2 4 2 1 2 2 2 2 2 4 4 2 1 1 1 4 1 4 2 4 4 4 4 2 4 4 2 1 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"ND/TH97: Default warning if no CSCW32 error found" "ND/TH97: Default error if no CSCW32 error found" "ND/TH97: Error" "ND/TH97: Printer not accessable, occupied by another user" "ND/TH97: Printer is not able to print graphices" "ND/TH97: Application tries to get a monitor message, but monitor not started yet" "ND/TH97: Application tries to start the monitor, but it is already started" "ND/TH97: Application tries to stop monitor with wrong process" "ND/TH97: Paper jam, paper skew, bad/missing mark on paper, dirty sensor" "ND/TH97: "Drum cover not locked, reset switch faulty, drive belt faulty "ND/TH97: The cutter is binding" "ND/TH97: Paper jam in paper path" "ND/TH97: Tray full, transport of more than 10 sheets attempted" "ND/TH97: Sheets where not removed before new print job was issued" "ND/TH97: Wrong access to a non-existent font module" "ND/TH97: Document jam in transport path, 2 reject attempted" "ND/TH97: External light when adjusting the photosensor" "ND/TH97: Rocker does not return to home position after cutting" "ND/TH97: Door is binding, stacker door open failure" "ND/TH97: Printer hardware error" "ND/TH97: Reject box overfilled" "ND/TH97: Printer firmware receives an internal SW error" "ND/TH97: Drum cover not closed" "ND/TH97: Selected paper lane not available" "ND/TH97: Paper empty on lane 2" "ND/TH97: Documents not removed before issuing a new print job" "ND/TH97: Print job in graphics mode aborted" "ND/TH97: Internal software error during graphic print job" "ND/TH97: V24 Communication timeout" "ND/TH97: V24 Communication timeout" "ND/TH97: V24 Communication problem" "USB/DOCPRT: DEFAULT_WARNING" "USB/DOCPRT: DEFAULT_ERROR" "USB/DOCPRT: Unexpected descriptor was reported from USB device" "USB/DOCPRT: Device not found" "USB/DOCPRT: Not enough memory available" "USB/DOCPRT: It was no endpoint found in the descriptor" "USB/DOCPRT: The creation of the list of USB devices failed" "USB/DOCPRT: USB read command could not be executed in the specified monitoring time" "USB/DOCPRT: USB READ command is cancelled by the user" "USB/DOCPRT: The pointer pData is illegal" "USB/DOCPRT: The length in DataSize is 0 (zero)" "USB/DOCPRT: CRC error has been detected" "USB/DOCPRT: Bit stuffing error has been detected" "USB/DOCPRT: DATA toggle mismatch has been detected" "USB/DOCPRT: STALLPID has been detected, error is reported by the USB host controller" "USB/DOCPRT: USB device is not responding, error is reported by the USB host" "USB/DOCPRT: PID check has failed, error is reported by the USB host controller" "USB/DOCPRT: Unexpected PID detected, error is reported by the USB host" "USB/DOCPRT: Data overrun error detected, error is reported by the USB host" "USB/DOCPRT: Data underrun error detected, error is reported by the USB host"
420
October 2004
U25604-J-Z745-1-7600

AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E 1084_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/DOCPRT: Error code is reserved by the USB host controller driver" "USB/DOCPRT: Error code is reserved by the USB host controller driver" "USB/DOCPRT: Buffer overrun has been detected, error is reported by the USB host" "USB/DOCPRT: Buffer underrun has been detected, error is reported by the USB host" "USB/DOCPRT: Buffer was not accessed, error is reported by the USB host" "USB/DOCPRT: FIFO error has been detected, PCI bus latency was too long" "USB/DOCPRT: XACT error has been detected, error is reported by the USB host" "USB/DOCPRT: Device is babbling, data transfer phase exceeds the USB frame length" "USB/DOCPRT: Data buffer error has been detected, error is reported by the USB host" "USB/DOCPRT: Endpoint has been halted by the USB bus driver USBD" "USB/DOCPRT: Memory allocation attempt has failed, error is reported by the USB bus" "USB/DOCPRT: Invalid URB function code has been passed, error is reported by the USB" "USB/DOCPRT: Invalid parameter has been passed, error is reported by the USB bus" "USB/DOCPRT: There are data transfer requests pending for the device" "USB/DOCPRT: Request has failed, error is reported by the USB bus driver USBD" "USB/DOCPRT: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/DOCPRT: There is not enough bandwidth available, error is reported by the USB bus" "USB/DOCPRT: Internal host controller error has been detected" "USB/DOCPRT: Short transfer has been detected, error is reported by the USB bus" "USB/DOCPRT: Bad start frame has been specified, error is reported by the USB bus" "USB/DOCPRT: Asynchronous request has failed, error is reported by the USB bus driver" "USB/DOCPRT: USB frame control is currently owned, error is reported by the USB bus" "USB/DOCPRT: USB frame control is currently not owned, error is reported by the USB" "USB/DOCPRT: Operation is not supported, error is reported by the USB bus driver" "USB/DOCPRT: Invalid configuration descriptor was reported by the device" "USB/DOCPRT: Operation has failed, error is reported by the USBIO driver" "USB/DOCPRT: Invalid input buffer has been passed to an IOCTL operation" "USB/DOCPRT: Invalid output buffer has been passed to an IOCTL operation" "USB/DOCPRT: There is not enough system memory available to complete the operation" "USB/DOCPRT: There are read or write requests pending, error is reported by the USBIO" "USB/DOCPRT: USB device is already configured, error is reported by the USBIO" "USB/DOCPRT: The USB device is not configured, error is reported by the USBIO driver" "USB/DOCPRT: There are open pipes, error is reported by the USBIO driver" "USB/DOCPRT: Either the handle is already bound to a pipe" "USB/DOCPRT: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/DOCPRT: USB device has been removed from the system" "USB/DOCPRT: Specified control code is not supported" "USB/DOCPRT: Operation has been timed out, error is reported by the USBIO driver" "USB/DOCPRT: Invalid recipient has been specified" "USB/DOCPRT: Either an invalid request type has been specified" "USB/DOCPRT: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/DOCPRT: Direction of the data transfer request is not supported by that pipe" "USB/DOCPRT: Number of asynchronous data packets specified in an asynchronous read" "USB/DOCPRT: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/DOCPRT: The specified pipe was not found in the current configuration" "USB/DOCPRT: An invalid asynchronous data packet has been specified" "USB/DOCPRT: There are not enough system resources to complete the operation" "USB/DOCPRT: Specified interface was not found in the current configuration" "USB/DOCPRT: Operation cannot be executed while the USB device is in the current state" "USB/DOCPRT: Invalid parameter has been specified with an IOCTL operation" "USB/DOCPRT: Evaluation interval of the USBIO DEMO version has expired" "USB/DOCPRT: Invalid power state has been specified" "USB/DOCPRT: Device has entered a power down state" "USB/DOCPRT: API version reported by the USBIO driver does not match" "USB/DOCPRT: Set configuration operation has failed, error is reported by the USBIO" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600
October 2004
421

AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 AA39 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev.
4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/DOCPRT: The specified device object does not exist" "USB/DOCPRT: Device object was opened, there is no valid handle to execute the operation" "USB/DOCPRT: Enumeration of the specified devices has failed" "USB/DOCPRT: Invalid parameter has been passed to a function" "USB/DOCPRT: Library setupapi.dll could not be loaded" "USB/DOCPRT: Set configuration request has failed" "USB/DOCPRT: Buffer is too small, error is reported by the USB bus driver USBD" "USB/DOCPRT: Interface was not found, error is reported by the USB bus driver USBD" "USB/DOCPRT: Invalid pipe flags have been specified" "USB/DOCPRT: Operation has been timed out, error is reported by the USB bus driver" "USB/DOCPRT: USB device is gone, error is reported by the USB bus driver USBD"
Printer TH21 (Class: 003E)

The following table lists the M-Status and M-Data codes assigned to printer class 003E.
Table 114: Printer (Class: 003E)
003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E 003E DEFA_W DEFA_E 0001_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8120_E 8121_E 8122_E 8201_E 8202_E 8203_E 8204_E 8205_E 8206_E 8207_E
Sev.
2 2 2 2 0 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
M-Status
00 00 00 08 00 08 08 05 08 08 08 08 08 08 08 08 08 08 08 08
M-Data
00000000 00000000 02000000 40000800 00000000 40000800 40000800 80000000 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800 40000800

"TH21: Default warning if no CSC-W32 error found" "TH21: Default error if no CSC-W32 error found" "TH21: Receipt paper low warning" "TH21: Receipt paper empty" "TH21: Cover is properly opened" "TH21: Print head temperature is not ok" "TH21: Power lost" "TH21: Paper jam" "TH21: The cutter is binding" "TH21: Hardware error, error in memory test" "TH21: Communication error with monitoring module if in use" "TH21: No GDI driver WN_TH21 found (when monitoring facility is used)" "TH21: Invalid COM port entry for GDI driver (when monitoring facility is used)" "TH21: Cannot open control file TH21.INI" "TH21: Cannot read control file TH21.INI" "TH21: Cannot open a file or invalid file name give up" "TH21: Printer hardware error, cannot read the file to be loaded" "TH21: File to be loaded has invalid module ID" "TH21: The expected response to the FW loader is not correct" "TH21: Invalid Logo type or logo file too big"
422
October 2004
U25604-J-Z745-1-7600
Printer Extensions (Class: 003F)

The following table lists the M-Status and M-Data codes assigned to printer class 003F.
Table 115: Printer (Class: 003F)
003F 003F 003F 003F DEFA_W DEFA_E 1017_E 1420_E
Sev.
2 2 4 4
MMStatus Data
00 00 00 00 00000000 00000000 00000000 00000000

"PRT GDI: Default warning if no CSC-W32 error found" "PRT GDI: Default error if no CSC-W32 error found" "PRT GDI: Communication problem" "PRT GDI: Communication problem"
Printer Monitor ND9G (Class: 0040)

0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 0040 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0009_E 000A_E 000B_E 000D_E 000E_E 000F_E 0010_E 0011_E 0012_E 0020_E 0021_E 0022_E 0023_E 0024_E 0025_E 0001_W 0002_W
Sev.
2 2 2 2 2 4 4 4 4 2 4 4 4 2 2 2 2 2 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"ND9G GDI: Default warning if no CSC-W32 error found" "ND9G GDI: Default error if no CSC-W32 error found" "ND9G GDI: Paper-out condition." "ND9G GDI: Terminate applications requiring the printer." "ND9G GDI: Receipt paper jam. Receipt could not be correctly processed." "ND9G GDI: Hardware error: error in memory test (RAM and ROM), backup RAM faulty." "ND9G GDI: Printer detect unexpected data." "ND9G GDI: A parity error is returned from the printer when faulty characters are received." "ND9G GDI: Loss of a command. The command was sent and could not be correctly executed." "ND9G GDI: By activated mark, recognition a mark is not found." "ND9G GDI: A checksum error of the RAM is occurred." "ND9G GDI: The loaded firmware file does not fit to the printer hardware." "ND9G GDI: Unexpected data was received." "ND9G GDI: A WRITE command could not be executed in the specified monitoring time." "ND9G GDI: A READ command could not be executed in the specified monitoring time." "ND9G GDI: Further control commands missing (e.g. Eject)" "ND9G GDI: An error occurred while the required line parameters were being set." "ND9G GDI: An internal SW error occurred." "ND9G GDI: Cannot open a file or checksum of a file to be loaded is not correct." "ND9G GDI: Cannot read the firmware file to be loaded." "ND9G GDI: Cannot read the file to be loaded." "ND9G GDI: The expected response of the Firmware Loader is not correct." "ND9G GDI: Firmware file data do not reach the firmware controller correctly." "ND9G GDI: An error occurred when the print system was started from the CSC service." "ND9G GDI: Wrong value of entry FILE_CTR" "ND9G GDI: No entry FILE1 found in the Registry."
U25604-J-Z745-1-7600
October 2004
423
Printer Monitor TH21 (Class: 0041)

0041 0041 0041 0041 0041 0041 0041 0041 0041 0041 0041 0041 0041 0041 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E
Sev.
2 2 4 2 2 4 4 2 4 2 2 2 2 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"TH21 GDI: Default warning if no CSC-W32 error found" "TH21 GDI: Default error if no CSC-W32 error found" "TH21 GDI: Paper-out condition." "TH21 GDI: The cover is properly opened." "TH21 GDI: The print head temperature is not ok." "TH21 GDI: Power failure during operation or insufficient power supply." "TH21 GDI: Receipt paper jam. Receipt could not be correctly processed." "TH21 GDI: The cutter is binding." "TH21 GDI: Error in memory test (RAM and ROM)" "TH21 GDI: Unexpected data was received." "TH21 GDI: A WRITE command could not be executed in the specified monitoring time" "TH21 GDI: A READ command could not be executed in the specified monitoring time" "TH21 GDI: Further control commands missing (e.g. Eject)" "TH21 GDI: An error occurred while the required line parameters were being set."
Printer System Framework (Class: 0042)

0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 0042 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000D_E 000E_E 000F_E 0010_E 0011_E
Sev.
2 2 2 2 2 2 2 4 4 2 4 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"PRT GDI: Default warning if no CSC-W32 error found" "PRT GDI: Default error if no CSC-W32 error found" "PRT GDI: Data that are passed to print system are to small" "PRT GDI: Invalid registry parameter" "PRT GDI: Operation not valid or not supported by printer" "PRT GDI: Internal software error" "PRT GDI: Function not allowed in the current context" "PRT GDI: Communication error, write request unsuccessful" "PRT GDI: A system error has occurred" "PRT GDI: Unexpected parameter in system call" "PRT GDI: Open failed" "PRT GDI: Start of a print job failed" "PRT GDI: A job has been despooled while another job is still in progress" "PRT GDI: Invalid parameter used in a server function call" "PRT GDI: Client already registered for monitoring" "PRT GDI: The client tried to claim the device twice" "PRT GDI: Invalid client handle used" "PRT GDI: Client not registered for monitoring"
424
October 2004
U25604-J-Z745-1-7600

0042 0042 0042 0042 0042 0042 0042 0042 0012_E 0013_E 0014_E 0015_E 0016_E 0017_E 0018_E 0019_E
Sev.
2 4 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"PRT GDI: Start of print system server failed" "PRT GDI: Connection failed, the printer is unknown" "PRT GDI: Access denied, the client is not allowed to access the requested operation" "PRT GDI: Access denied, because another client has claimed the device for exclusive access" "PRT GDI: Unknown property" "PRT GDI: The property has an invalid format" "PRT GDI: The property value is invalid" "PRT GDI: An invalid input string has been supplied"
U25604-J-Z745-1-7600
October 2004
425
Printer TP07 GDI (Class: 0044)

0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 0044 DEFA_W DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 0010_E 0011_E 0012_E 0013_E 0015_E 0016_E
Sev.
2 4 2 2 2 2 2 2 4 4 4 4 4 4 4 4 4 2 4
MStatus
00 00 08 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 40000800 80000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"TP07 GDI: DEFAULT_WARNING" "TP07 GDI: DEFAULT_ERROR" "TP07 GDI: Paper-out condition" "TP07 GDI: Paper jam while cutting the paper" "TP07 GDI: Black dot mark not found" "TP07 GDI: Paper jam after cut receipt in the presenter" "TP07 GDI: Paper jam after cut receipt after reject command." "TP07 GDI: Receipt paper jam while printing process" "TP07 GDI: Internal print job timeout has occurred" "TP07 GDI: Power voltage of the printer is too high" "TP07 GDI: Power voltage of the printer is too low" "TP07 GDI: Temperature of the print head is too high" "TP07 GDI: Hardware error" "TP07 GDI: Unexpected data was received" "TP07 GDI: A WRITE command could not be executed in the specified monitoring time" "TP07 GDI: A READ command could not be executed in the specified monitoring time" "TP07 GDI: This message may only occur when controlled print jobs are received" "TP07 GDI: An internal SW error occurred" "TP07 GDI: Printer is in offline state without any specific device error"
426
October 2004
U25604-J-Z745-1-7600
Printer TP07 (Class: 0045)

0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 0045 DEFA_W DEFA_E 0001_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8000_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E
Sev.
4 4 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 02000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"RJ03/TP07/NP07: DEFAULT_WARNING" "RJ03/TP07/NP07: DEFAULT_ERROR" "RJ03/TP07/NP07: Receipt paper low" "RJ03/TP07/NP07: Unexpected data was received" "RJ03/TP07/NP07: Allocation error, not enough resources to allocate internal memory" "RJ03/TP07/NP07: A READ command could not be executed in the specified monitoring time" "RJ03/TP07/NP07: Code page not available" "RJ03/TP07/NP07: Cannot open image file or invalid file name give up" "RJ03/TP07/NP07: Cannot read the file to be loaded" "RJ03/TP07/NP07: Invalid logo type" "RJ03/TP07/NP07: Printer is in offline state without any specific device error" "RJ03/TP07/NP07: No USB devices of the specified type available" "RJ03/TP07/NP07: Receipt paper out" "RJ03/TP07/NP07: Paper jam while paper cut" "RJ03/TP07/NP07: Carrier does not found the home position" "RJ03/TP07/NP07: Paper jam before cut" "RJ03/TP07/NP07: Black dot mark not found" "RJ03/TP07/NP07: Paper jam after cutting the receipt in the presenter" "RJ03/TP07/NP07: Paper jam after cut receipt after reject command" "RJ03/TP07/NP07: Receipt paper jam while printing" "RJ03/TP07/NP07: Power voltage of printer is too high" "RJ03/TP07/NP07: Power voltage of printer is too low" "RJ03/TP07/NP07: Temperature of print head is too high" "RJ03/TP07/NP07: Hardware error" "RJ03/TP07/NP07: Paper is not at print starting position"
U25604-J-Z745-1-7600
October 2004
427
Printer USB/TP07 (Class: AA45)

The following table lists the M-Status and M-Data codes assigned to printer class AA45.
Table 121: Printer (Class: AA45)
AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/TP07/NP07: DEFAULT_WARNING" "USB/TP07/NP07: DEFAULT_ERROR" "USB/TP07/NP07: Unexpected descriptor was reported from USB device" "USB/TP07/NP07: Device not found" "USB/TP07/NP07: Not enough memory available" "USB/TP07/NP07: It was no endpoint found in the descriptor" "USB/TP07/NP07: The creation of the list of USB devices failed" "USB/TP07/NP07: USB read command could not be executed in the specified monitoring time" "USB/TP07/NP07: USB READ command is cancelled by the user" "USB/TP07/NP07: The pointer pData is illegal" "USB/TP07/NP07: The length in DataSize is 0 (zero)" "USB/TP07/NP07: CRC error has been detected" "USB/TP07/NP07: Bit stuffing error has been detected" "USB/TP07/NP07: DATA toggle mismatch has been detected" "USB/TP07/NP07: STALLPID has been detected, error is reported by the USB host controller" "USB/TP07/NP07: USB device is not responding, error is reported by the USB host" "USB/TP07/NP07: PID check has failed, error is reported by the USB host controller" "USB/TP07/NP07: Unexpected PID detected, error is reported by the USB host" "USB/TP07/NP07: Data overrun error detected, error is reported by the USB host" "USB/TP07/NP07: Data underrun error detected, error is reported by the USB host" "USB/TP07/NP07: Error code is reserved by the USB host controller driver" "USB/TP07/NP07: Error code is reserved by the USB host controller driver" "USB/TP07/NP07: Buffer overrun has been detected, error is reported by the USB host" "USB/TP07/NP07: Buffer underrun has been detected, error is reported by the USB host" "USB/TP07/NP07: Buffer was not accessed, error is reported by the USB host" "USB/TP07/NP07: FIFO error has been detected, PCI bus latency was too long" "USB/TP07/NP07: XACT error has been detected, error is reported by the USB host" "USB/TP07/NP07: Device is babbling, data transfer phase exceeds the USB frame length" "USB/TP07/NP07: Data buffer error has been detected, error is reported by the USB host" "USB/TP07/NP07: Endpoint has been halted by the USB bus driver USBD" "USB/TP07/NP07: Memory allocation attempt has failed, error is reported by the USB bus" "USB/TP07/NP07: Invalid URB function code has been passed, error is reported by the USB" "USB/TP07/NP07: Invalid parameter has been passed, error is reported by the USB bus" "USB/TP07/NP07: There are data transfer requests pending for the device" "USB/TP07/NP07: Request has failed, error is reported by the USB bus driver USBD" "USB/TP07/NP07: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/TP07/NP07: There is not enough bandwidth available, error is reported by the USB bus" "USB/TP07/NP07: Internal host controller error has been detected" "USB/TP07/NP07: Short transfer has been detected, error is reported by the USB bus" "USB/TP07/NP07: Bad start frame has been specified, error is reported by the USB bus" "USB/TP07/NP07: Asynchronous request has failed, error is reported by the USB bus driver" "USB/TP07/NP07: USB frame control is currently owned, error is reported by the USB bus" "USB/TP07/NP07: USB frame control is currently not owned, error is reported by the USB" "USB/TP07/NP07: Operation is not supported, error is reported by the USB bus driver" "USB/TP07/NP07: Invalid configuration descriptor was reported by the device" "USB/TP07/NP07: Operation has failed, error is reported by the USBIO driver"
428
October 2004
U25604-J-Z745-1-7600

AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 AA45 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/TP07/NP07: Invalid input buffer has been passed to an IOCTL operation" "USB/TP07/NP07: Invalid output buffer has been passed to an IOCTL operation" "USB/TP07/NP07: There is not enough system memory available to complete the operation" "USB/TP07/NP07: There are read or write requests pending, error is reported by the USBIO" "USB/TP07/NP07: USB device is already configured, error is reported by the USBIO" "USB/TP07/NP07: The USB device is not configured, error is reported by the USBIO driver" "USB/TP07/NP07: There are open pipes, error is reported by the USBIO driver" "USB/TP07/NP07: Either the handle is already bound to a pipe" "USB/TP07/NP07: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/TP07/NP07: USB device has been removed from the system" "USB/TP07/NP07: Specified control code is not supported" "USB/TP07/NP07: Operation has been timed out, error is reported by the USBIO driver" "USB/TP07/NP07: Invalid recipient has been specified" "USB/TP07/NP07: Either an invalid request type has been specified" "USB/TP07/NP07: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/TP07/NP07: Direction of the data transfer request is not supported by that pipe" "USB/TP07/NP07: Number of asynchronous data packets specified in an asynchronous read" "USB/TP07/NP07: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/TP07/NP07: The specified pipe was not found in the current configuration" "USB/TP07/NP07: An invalid asynchronous data packet has been specified" "USB/TP07/NP07: There are not enough system resources to complete the operation" "USB/TP07/NP07: Specified interface was not found in the current configuration" "USB/TP07/NP07: Operation cannot be executed while the USB device is in the current state" "USB/TP07/NP07: Invalid parameter has been specified with an IOCTL operation" "USB/TP07/NP07: Evaluation interval of the USBIO DEMO version has expired" "USB/TP07/NP07: Invalid power state has been specified" "USB/TP07/NP07: Device has entered a power down state" "USB/TP07/NP07: API version reported by the USBIO driver does not match" "USB/TP07/NP07: Set configuration operation has failed, error is reported by the USBIO" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP07/NP07: The specified device object does not exist" "USB/TP07/NP07: Device object was opened, there is no valid handle to execute the operation" "USB/TP07/NP07: Enumeration of the specified devices has failed" "USB/TP07/NP07: Invalid parameter has been passed to a function" "USB/TP07/NP07: Library setupapi.dll could not be loaded" "USB/TP07/NP07: Set configuration request has failed" "USB/TP07/NP07: Buffer is too small, error is reported by the USB bus driver USBD" "USB/TP07/NP07: Interface was not found, error is reported by the USB bus driver USBD" "USB/TP07/NP07: Invalid pipe flags have been specified" "USB/TP07/NP07: Operation has been timed out, error is reported by the USB bus driver" "USB/TP07/NP07: USB device is gone, error is reported by the USB bus driver USBD"
U25604-J-Z745-1-7600
October 2004
429
Printer TP06 (Class: 0048)

0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 0048 DEFA_W DEFA_E 0001_E 8100_E 8101_E 8102_E 8103_E 8104_E 8105_E 8106_E 8107_E 8108_E 8000_E 8001_E 8002_E 8003_E 8004_E 8005_E 8006_E 8007_E 8008_E 8009_E 800A_E 800B_E 800C_E
Sev.
4 4 2 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 02000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"RJ03/TP06/NP06: DEFAULT_WARNING" "RJ03/TP06/NP06: DEFAULT_ERROR" "RJ03/TP06/NP06: Journal paper low" "RJ03/TP06/NP06: Unexpected data was received" "RJ03/TP06/NP06: Allocation error, not enough resources to allocate internal memory" "RJ03/TP06/NP06: A READ command could not be executed in the specified monitoring time" "RJ03/TP06/NP06: Code page not available" "RJ03/TP06/NP06: Cannot open image file or invalid file name give up" "RJ03/TP06/NP06: Cannot read the file to be loaded" "RJ03/TP06/NP06: Invalid logo type" "RJ03/TP06/NP06: Printer is in offline state without any specific device error" "RJ03/TP06/NP06: No USB devices of the specified type available" "RJ03/TP06/NP06: Journal paper out" "RJ03/TP06/NP06: Paper jam while paper cut" "RJ03/TP06/NP06: Carrier does not found the home position" "RJ03/TP06/NP06: Paper jam before cut" "RJ03/TP06/NP06: Black dot mark not found" "RJ03/TP06/NP06: Paper jam after cutting the receipt in the presenter" "RJ03/TP06/NP06: Paper jam after cut receipt after reject command" "RJ03/TP06/NP06: Receipt paper jam while printing" "RJ03/TP06/NP06: Power voltage of printer is too high" "RJ03/TP06/NP06: Power voltage of printer is too low" "RJ03/TP06/NP06: Temperature of print head is too high" "RJ03/TP06/NP06: Hardware error" "RJ03/TP06/NP06: Paper is not at print starting position"
430
October 2004
U25604-J-Z745-1-7600
Printer USB/TP06 (Class: AA48)

The following table lists the M-Status and M-Data codes assigned to printer class AA48.
Table 123: Printer (Class: AA48)
AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 DEFA_W DEFA_E 8000_E 8001_E 8002_E 8003_E 8004_E FE09_E FE0A_E FE89_E FE9C_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000F_E 0010_E 0011_E 0012_E 0013_E 0030_E 0100_E 0200_E 0300_E 0400_E 0500_E 0600_E 0700_E 0800_E 0900_E 0A00_E 0B00_E 0C00_E 0D00_E 0E00_E 0F00_E 1000_E
Sev.
2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/TP06/NP06: DEFAULT_WARNING" "USB/TP06/NP06: DEFAULT_ERROR" "USB/TP06/NP06: Unexpected descriptor was reported from USB device" "USB/TP06/NP06: Device not found" "USB/TP06/NP06: Not enough memory available" "USB/TP06/NP06: It was no endpoint found in the descriptor" "USB/TP06/NP06: The creation of the list of USB devices failed" "USB/TP06/NP06: USB read command could not be executed in the specified monitoring time" "USB/TP06/NP06: USB READ command is cancelled by the user" "USB/TP06/NP06: The pointer pData is illegal" "USB/TP06/NP06: The length in DataSize is 0 (zero)" "USB/TP06/NP06: CRC error has been detected" "USB/TP06/NP06: Bit stuffing error has been detected" "USB/TP06/NP06: DATA toggle mismatch has been detected" "USB/TP06/NP06: STALLPID has been detected, error is reported by the USB host controller" "USB/TP06/NP06: USB device is not responding, error is reported by the USB host" "USB/TP06/NP06: PID check has failed, error is reported by the USB host controller" "USB/TP06/NP06: Unexpected PID detected, error is reported by the USB host" "USB/TP06/NP06: Data overrun error detected, error is reported by the USB host" "USB/TP06/NP06: Data underrun error detected, error is reported by the USB host" "USB/TP06/NP06: Error code is reserved by the USB host controller driver" "USB/TP06/NP06: Error code is reserved by the USB host controller driver" "USB/TP06/NP06: Buffer overrun has been detected, error is reported by the USB host" "USB/TP06/NP06: Buffer underrun has been detected, error is reported by the USB host" "USB/TP06/NP06: Buffer was not accessed, error is reported by the USB host" "USB/TP06/NP06: FIFO error has been detected, PCI bus latency was too long" "USB/TP06/NP06: XACT error has been detected, error is reported by the USB host" "USB/TP06/NP06: Device is babbling, data transfer phase exceeds the USB frame length" "USB/TP06/NP06: Data buffer error has been detected, error is reported by the USB host" "USB/TP06/NP06: Endpoint has been halted by the USB bus driver USBD" "USB/TP06/NP06: Memory allocation attempt has failed, error is reported by the USB bus" "USB/TP06/NP06: Invalid URB function code has been passed, error is reported by the USB" "USB/TP06/NP06: Invalid parameter has been passed, error is reported by the USB bus" "USB/TP06/NP06: There are data transfer requests pending for the device" "USB/TP06/NP06: Request has failed, error is reported by the USB bus driver USBD" "USB/TP06/NP06: Invalid pipe handle has been passed, error is reported by the USB bus" "USB/TP06/NP06: There is not enough bandwidth available, error is reported by the USB bus" "USB/TP06/NP06: Internal host controller error has been detected" "USB/TP06/NP06: Short transfer has been detected, error is reported by the USB bus" "USB/TP06/NP06: Bad start frame has been specified, error is reported by the USB bus" "USB/TP06/NP06: Asynchronous request has failed, error is reported by the USB bus driver" "USB/TP06/NP06: USB frame control is currently owned, error is reported by the USB bus" "USB/TP06/NP06: USB frame control is currently not owned, error is reported by the USB" "USB/TP06/NP06: Operation is not supported, error is reported by the USB bus driver" "USB/TP06/NP06: Invalid configuration descriptor was reported by the device" "USB/TP06/NP06: Operation has failed, error is reported by the USBIO driver"
U25604-J-Z745-1-7600
October 2004
431

AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 AA48 1001_E 1002_E 1003_E 1004_E 1005_E 1006_E 1007_E 1008_E 1009_E 100A_E 100B_E 100C_E 100D_E 100E_E 100F_E 1010_E 1011_E 1012_E 1013_E 1014_E 1015_E 1016_E 1017_E 1018_E 1019_E 101A_E 101B_E 101C_E 101D_E 1080_E 1081_E 1082_E 1083_E 1084_E 1085_E 1086_E 1087_E 1100_E 1102_E 1104_E 1105_E 1106_E 2000_E 3000_E 4000_E 5000_E 6000_E 7000_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"USB/TP06/NP06: Invalid input buffer has been passed to an IOCTL operation" "USB/TP06/NP06: Invalid output buffer has been passed to an IOCTL operation" "USB/TP06/NP06: There is not enough system memory available to complete the operation" "USB/TP06/NP06: There are read or write requests pending, error is reported by the USBIO" "USB/TP06/NP06: USB device is already configured, error is reported by the USBIO" "USB/TP06/NP06: The USB device is not configured, error is reported by the USBIO driver" "USB/TP06/NP06: There are open pipes, error is reported by the USBIO driver" "USB/TP06/NP06: Either the handle is already bound to a pipe" "USB/TP06/NP06: Handle is not bound to a pipe, error is reported by the USBIO driver" "USB/TP06/NP06: USB device has been removed from the system" "USB/TP06/NP06: Specified control code is not supported" "USB/TP06/NP06: Operation has been timed out, error is reported by the USBIO driver" "USB/TP06/NP06: Invalid recipient has been specified" "USB/TP06/NP06: Either an invalid request type has been specified" "USB/TP06/NP06: Invalid IOCTL code has been specified, error is reported by the USBIO" "USB/TP06/NP06: Direction of the data transfer request is not supported by that pipe" "USB/TP06/NP06: Number of asynchronous data packets specified in an asynchronous read" "USB/TP06/NP06: Memory resources are exhausted. This error is reported by the USBIO driver" "USB/TP06/NP06: The specified pipe was not found in the current configuration" "USB/TP06/NP06: An invalid asynchronous data packet has been specified" "USB/TP06/NP06: There are not enough system resources to complete the operation" "USB/TP06/NP06: Specified interface was not found in the current configuration" "USB/TP06/NP06: Operation cannot be executed while the USB device is in the current state" "USB/TP06/NP06: Invalid parameter has been specified with an IOCTL operation" "USB/TP06/NP06: Evaluation interval of the USBIO DEMO version has expired" "USB/TP06/NP06: Invalid power state has been specified" "USB/TP06/NP06: Device has entered a power down state" "USB/TP06/NP06: API version reported by the USBIO driver does not match" "USB/TP06/NP06: Set configuration operation has failed, error is reported by the USBIO" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: The operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: Operation has failed due to a restriction of the USBIO LIGHT version" "USB/TP06/NP06: The specified device object does not exist" "USB/TP06/NP06: Device object was opened, there is no valid handle to execute the operation" "USB/TP06/NP06: Enumeration of the specified devices has failed" "USB/TP06/NP06: Invalid parameter has been passed to a function" "USB/TP06/NP06: Library setupapi.dll could not be loaded" "USB/TP06/NP06: Set configuration request has failed" "USB/TP06/NP06: Buffer is too small, error is reported by the USB bus driver USBD" "USB/TP06/NP06: Interface was not found, error is reported by the USB bus driver USBD" "USB/TP06/NP06: Invalid pipe flags have been specified" "USB/TP06/NP06: Operation has been timed out, error is reported by the USB bus driver" "USB/TP06/NP06: USB device is gone, error is reported by the USB bus driver USBD"
432
October 2004
U25604-J-Z745-1-7600
M-Status & M-Data Reference TablesApplication Error Classes (LYNX error
Application Error Classes (LYNX errors)

Transaction (Class: 6434)
Table 124: Transaction (Class: 6434)
6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 0001_E 0001_W 0002_E 0003_E 0004_E 0004_W 0005_W 0006_E 0007_E 0008_E 0009_E 000A_W 000B_W 000C_W 000D_W 000E_E 000E_W 0010_E 0010_W 0011_W 0012_W 0013_W 0014_W 0015_W 0015_E 0016_W 0017_W 0018_E 0019_E 0020_W 0021_W 0022_W 0023_W 0024_W 0025_W 0026_W 0027_W 0028_W 0028_E 0029_W 002A_E 002B_E 002C_E 002D_E 002E_E 002F_E 0030_E 0031_E 0032_W 0033_W 0034_W 0035_W
Sev.
0 2 4 4 2 2 4 2 2 4 4 4 4 4 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 4 4 4 4 2 2 4 4 4 2 2 2 2 2 2 2 4 2 2 2 2
MStatus
00 12 07 08 00 00 08 00 00 00 20 00 00 00 20 00 00 00 00 05 00 12 00 00 00 00 00 11 07 13 09 01 01 11 08 01 04 11 11 38 00 00 00 00 00 00 04 06 02 01 02 05
MData
06000000 06000000 40000000 40000000 0007000000000000 0007000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 000000000000000000 00000000 00000000 00000000 0000000000 00000000 00000000 00000000000000000000 00000000000000000000 0000000000000000000000 0001 06000040 01000000000000000000 02000000 02000000 02000000 0200000000000000 0400000000000000000 0000000000 1000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0600000000 000000 000000 0000000000000000000000 0000000000000000000000 000000 000000 000000 000000 000000 000000 000000 000000

"LYNX TRX: Card was captured" "LYNX TRX: Card was captured" "LYNX TRX: Receipt printer not configured" "LYNX TRX: Statement printer not configured" "LYNX TRX: Statement was retracted" "LYNX TRX: Statement was retracted" "LYNX TRX: Deposit general error" "LYNX TRX: Deposit was cancelled" "LYNX TRX: Deposit timeout" "LYNX TRX: Deposit not configured" "LYNX TRX: Cash dispenser not configured" "LYNX TRX: Journal printer general error" "LYNX TRX: Receipt printer general error" "LYNX TRX: Document printer general error" "LYNX TRX: Card reader general HW error" "LYNX TRX: Journal printer error, spooler active" "LYNX TRX: Journal printer warning, spooler active" "LYNX TRX: Money was retracted error" "LYNX TRX: Money was retracted warning" "LYNX TRX: Deposit shutter not opened" "LYNX TRX: Panel Protection door problem" "LYNX TRX: Card read threshold" "LYNX TRX: Cassette low" "LYNX TRX: Journal paper low, warning" "LYNX TRX: Journal paper low, error" "LYNX TRX: Receipt paper low" "LYNX TRX: Document paper low" "LYNX TRX: Try to dispense with money in transport" "LYNX TRX: Card write attempt but no track data" "LYNX TRX: CDM shutter error" "LYNX TRX: Deposit bin missing" "LYNX TRX: Deposit jam" "LYNX TRX: Deposit envelope jam" "LYNX TRX: Deposit no envelope" "LYNX TRX: Deposit printer failure" "LYNX TRX: Deposit envelope size" "LYNX TRX: Deposit shutter not close" "LYNX TRX: Deposit bin full" "LYNX TRX: Deposit bin full (ADRS)" "LYNX TRX: Card reader bin overfilled" "LYNX TRX: CAS - CDM: Consumer timeout in screen dialog 907" "LYNX TRX: CAS - CDM: Consumer has cancelled screen dialog 907" "LYNX TRX: CAS - DEP: Consumer timeout in screen dialog 906" "LYNX TRX: CAS - DEP: Consumer has cancelled screen dialog 906" "LYNX TRX: CAS - DOC: Consumer timeout in Screen dialog 909" "LYNX TRX: CAS - DOC: Consumer has cancelled screen dialog 909" "LYNX TRX: Envelope dispenser LOW" "LYNX TRX: Envelope dispenser EMPTY" "LYNX TRX: Envelope dispenser error" "LYNX TRX: Envelope dispenser jam" "LYNX TRX: Envelope dispenser shutter not close" "LYNX TRX: Envelope dispenser shutter not open"
U25604-J-Z745-1-7600
October 2004
433
Application Error Classes (LYNX errors)M-Status & M-Data Reference Table

6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 6434 0036_E 0037_E 0037_W 0038_E 0039_E 0040_E 0041_E 0042_E 0043_W 0043_E 0044_E 0045_E 0046_E 0047_E 0048_E
Sev.
2 4 2 2 2 4 4 2 2 4 2 2 4 4 4
MStatus
36 05 05 08 12 05 05 12 05 05 02 04 04 04 04
MData
0007000000000000 08000000 08000000 40000800 00000000000000000000 40000800 08000000 06000000 08000000 08000000 0000000000 0000000000 0000000000 0000000000 0000000000

"LYNX TRX: Statement capture bin full" "LYNX TRX: Journal paper nearly empty, error" "LYNX TRX: Journal paper nearly empty, warning" "LYNX TRX: Receipt paper nearly empty" "LYNX TRX: Shutter not close or money jam, dispense operation declined" "LYNX TRX: Receipt paper jam or paper empty" "LYNX TRX: Journal paper jam or paper empty" "LYNX TRX: Card was captured after jam" "LYNX TRX: Hard disk free space becomes low" "LYNX TRX: No hard disk free space available" "LYNX TRX: Card write attempted but track not installed" "LYNX TRX: Card write command failed" "LYNX TRX: Card trap active" "LYNX TRX: Mouth piece vandalism" "LYNX TRX: Card reader skimming active"
Cash Dispenser (Class: 643A)

Table 125: Cash Dispenser (Class: 643A)
643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 02DF DEFA_W DEFA_E 0001_E 0002_E 0002_W 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E FEB5_W FEB6_W FEC0_W FEC3_W FEC4_W FEC5_W FEC6_W FEC7_W FEC8_W FEC9_W FECA_W FECB_W FECC_W FECD_W FECE_W FECF_W FED0_W FED1_W FED2_W FED2_E
Sev.
2 2 4 2 2 2 4 4 4 2 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
03 03 41 04 04 00 07 08 08 07 11 10 00 14 03 03 01 14 13 14 34 00 03 03 17 03 04 04 04 04 09 09
MData
01100000000000000000 01100000000000000000 00004000000000000000 00000303030300000000 00000303030300000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 06000000000000000000 02000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"LYNX CDM: Warning not found, use default entry" "LYNX CDM: Error not found, use default entry" "LYNX CDM: Invalid cassette number" "LYNX CDM: Try from empty or low cassette" "LYNX CDM: Not dispenseable" "LYNX CDM: Safe door open during dispense" "LYNX CDM: Reject cassette not operational" "LYNX CDM: Reject cassette full" "LYNX CDM: Max retracts reached" "LYNX CDM: Reject bin missing" "LYNX CDM: Max present errors after dispense" "LYNX CDM: Cash dispenser fatal" "LYNX WOSA RTC: -331 (Order not allowed)" "LYNX WOSA RTC: -330 (Shutter not closed)" "LYNX WOSA RTC: -320 (Denomination error)" "LYNX WOSA RTC: -317 (No documents, no bills)" "LYNX WOSA RTC: -316 (Invalid cash unit)" "LYNX WOSA RTC: -315 (Shutter closed)" "LYNX WOSA RTC: -314 (Shutter open)" "LYNX WOSA RTC: -313 (Shutter not open)" "LYNX WOSA RTC: -312 (Invalid retract)" "LYNX WOSA RTC: -311 (Safe door open)" "LYNX WOSA RTC: -310 (Position locked)" "LYNX WOSA RTC: -309 (Invalid position)" "LYNX WOSA RTC: -308 (Documents, bills left)" "LYNX WOSA RTC: -307 (Too many documents)" "LYNX WOSA RTC: -306 (Not dispensable)" "LYNX WOSA RTC: -305 (No currency mix)" "LYNX WOSA RTC: -304 (Invalid mix type)" "LYNX WOSA RTC: -303 (Invalid denomination)" "LYNX WOSA RTC: -302 (Cash unit error)" "LYNX WOSA RTC: -302 return of CheckDispOutput()"
434
October 2004
U25604-J-Z745-1-7600

643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A 643A FED3_W FED4_W FFF2_W FFF3_W FEB5_E FEB6_E FEC0_E FEC3_E FEC4_E FEC5_E FEC6_E FEC7_E FEC8_E FEC9_E FECA_E FECB_E FECC_E FECD_E FECE_E FECF_E FED0_E FED1_E FED2_E FED3_E FED4_E FFF2_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 01 03 03 00 14 03 03 01 14 13 14 34 00 03 03 17 03 04 04 04 04 09 09 01 03
MData
00000000000000000000 00000000000000000000 01100000000000000000 01100000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 01100000000000000000

"LYNX WOSA RTC: -301 (Invalid teller ID)" "LYNX WOSA RTC: -300 (Invalid currency)" "LYNX WOSA RTC: Hardware error, cannot dispense" "LYNX WOSA RTC: Hardware error, device not ready" "LYNX WOSA RTC: -331 (Order not allowed)" "LYNX WOSA RTC: -330 (Shutter not closed)" "LYNX WOSA RTC: -320 (Denomination error)" "LYNX WOSA RTC: -317 (No documents, no bills)" "LYNX WOSA RTC: -316 (Invalid cash unit)" "LYNX WOSA RTC: -315 (Shutter closed)" "LYNX WOSA RTC: -314 (Shutter open)" "LYNX WOSA RTC: -313 (Shutter not open)" "LYNX WOSA RTC: -312 (Invalid retract)" "LYNX WOSA RTC: -311 (Safe door open)" "LYNX WOSA RTC: -310 (Position locked)" "LYNX WOSA RTC: -309 (Invalid position)" "LYNX WOSA RTC: -308 (Documents, bills left)" "LYNX WOSA RTC: -307 (Too many documents)" "LYNX WOSA RTC: -306 (Not dispensable)" "LYNX WOSA RTC: -305 (No currency mix)" "LYNX WOSA RTC: -304 (Invalid mix type)" "LYNX WOSA RTC: -303 (Invalid denomination)" "LYNX WOSA RTC: -302 (Cash unit error)" "LYNX WOSA RTC: -301 (Invalid teller ID)" "LYNX WOSA RTC: -300 (Invalid currency)" "LYNX WOSA RTC: Hardware error, cannot dispense"
Security Module (Class: 643C)

Table 126: Security Module (Class: 643C)
643C 643C 643C 643C 643C 0001_E 0002_E 0003_E 0004_E 0005_E
Sev.
4 2 2 2 2
MStatus
38 70 70 38 38
MData
00000000 00000000 00000000 00000000 00000000

"LYNX SEC: Set key error, possibly wrong keys" "LYNX SEC: PIN check error, possibly wrong keys" "LYNX SEC: Error while creating host PIN block" "LYNX SEC: Error calculating MAC" "LYNX SEC: Error initializing transaction"
CashIn transaction (Class: 6446)

Table 127: CashIn transaction (Class: 6446)
6446 6446 6446 6446 6446 0001_E 0002_E 0003_E 0004_E 0005_E
Sev.
4 2 3 4 2
MStatus
01 02 03 04 05
MData
0000000000000000 000001 0000000000000000 000002 0000000000000000 000003 0000000000000000 000004 0000000000000000 000005

"LYNX CASHIN: CashIn not operational" "LYNX CASHIN: CashIn input shutter jam" "LYNX CASHIN: CashIn input tray jam" "LYNX CASHIN: CashIn input transport jam" "LYNX CASHIN: CashIn output shutter jam"
U25604-J-Z745-1-7600
October 2004
435
Application Error Classes (LYNX errors)M-Status & M-Data Reference Table

6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 6446 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E 000D_E 000E_E 000F_E 0010_E 0011_E 0012_E 0013_E 0014_E 0015_E 0016_E 0017_E 0018_E 0019_E 001A_E 001B_E 001C_E 001D_E 001E_E 001F_E 0020_E 0021_E
Sev.
4 4 2 2 3 4 2 2 2 2 4 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
06 07 08 09 10 11 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34
MData
0000000000000000 000006 0000000000000000 000007 0000000000000000 000008 0000000000000000 000009 0000000000000000 000010 0000000000000000 000011 0000000000000000 000013 0000000000000000 000014 0000000000000000 000015 0000000000000000 000016 0000000000000000 000017 0000000000000000 000018 0000000000000000 000019 0000000000000000 000020 0000000000000000 000021 0000000000000000 000022 0000000000000000 000023 0000000000000000 000024 0000000000000000 000025 0000000000000000 000026 0000000000000000 000027 0000000000000000 000028 0000000000000000 000029 0000000000000000 000030 0000000000000000 000031 0000000000000000 000032 0000000000000000 000033 0000000000000000 000034

"LYNX CASHIN: CashIn output tray jam" "LYNX CASHIN: CashIn output transport jam" "LYNX CASHIN: CashIn BIM not operational" "LYNX CASHIN: CashIn retracted" "LYNX CASHIN: CashIn input stacker jam" "LYNX CASHIN: CashIn output stacker jam" "LYNX CASHIN: Hardware error on Drum 1" "LYNX CASHIN: Hardware error on Drum 2" "LYNX CASHIN: Hardware error on Drum 3" "LYNX CASHIN: Hardware error on Drum 4" "LYNX CASHIN: Jam during transport on Drum" "LYNX CASHIN: One CashIn box is now overfilled" "LYNX CASHIN: CashIn boxes are overfilled" "LYNX CASHIN: Metal in CashIn tray detected" "LYNX CASHIN: CashIn reject bin full" "LYNX CASHIN: Security stripe sensor defective" "LYNX CASHIN: Metal sensor defective" "LYNX CASHIN: Escrow empty" "LYNX CASHIN: Error TRX reply buffer" "LYNX CASHIN: Good Rollback, but L2 notes retracted" "LYNX CASHIN: Rollback failed, all notes retracted" "LYNX CASHIN: Good Cashin, but L2 notes retracted" "LYNX CASHIN: Good Rollback, but all notes retracted after consumer timeout" "LYNX CASHIN: CashIn cancelled by consumer, host reply not yet received" "LYNX CASHIN: Good Rollback, but L3 notes not returned" "LYNX CASHIN: Good Rollback, but L2+L3 notes not returned" "LYNX CASHIN: Good Cashin, but L3 notes not returned" "LYNX CASHIN: Good Cashin, but L2+L3 notes not returned"
EMV transaction (Class: 6459)

Table 128: EMV transaction (Class: 6459)
6459 0001_W
Sev.
2
MStatus
77
MData
7000000000

"LYNX EMV: Chip contact threshold"
436
October 2004
U25604-J-Z745-1-7600
Cheque transaction (Class: 645A)

Table 129: Cheque transaction (Class: 645A)
645A 645A 645A 645A 645A 645A 645A 645A 645A 645A 645A 645A 645A DEFA_E 0001_E 0002_E 0003_E 0004_E 0005_E 0006_E 0007_E 0008_E 0009_E 000A_E 000B_E 000C_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
01 01 02 03 04 05 06 07 08 09 10 11 12
MData
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

"LYNX CHEQUE: Cheque device jammed" "LYNX CHEQUE: Cheque acception error" "LYNX CHEQUE: Error during cheques storing" "LYNX CHEQUE: Error during ejecting cheques" "LYNX CHEQUE: Present timeout, cheque will be captured" "LYNX CHEQUE: Retract error, cheque may be still in IO path" "LYNX CHEQUE: Retract bin full, no more cheques can be captured" "LYNX CHEQUE: Cheque flush error" "LYNX CHEQUE: Cheque device jammed" "LYNX CHEQUE: Cheque archiving failed, check path configuration" "LYNX CHEQUE: Shutter jammed or blocked during MediaIn" "LYNX CHEQUE: General hardware error of CCDM" "LYNX CHEQUE: Safe door open, trx not allowed"
Electronic Journal (Class: 0091)

Table 130: EMV transaction (Class: 0091)
0091 0091 0091 0091 DEFA_E 0001_E 0002_E 0003_E
Sev.
4 4 4 4
MStatus
07 07 07 07
MData
40000000 40000000 40000000 40000000

"E-JRN: E-Journal file could not be written" "E-JRN: E-Journal file could not be written" "E-JRN: E-Journal file could not be written" "E-JRN: EJ/SAF-Journal file could not be written"
U25604-J-Z745-1-7600
October 2004
437
WOSA Error Classes)
WOSA Error Classes)

WOSA Cash Dispenser (Class: 00B9)
Table 131: WOSA Cash Dispenser (Class: 00B9)
00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 D010_E D016_E D020_E D025_E D100_E D101_E D105_E D106_E D110_E D120_E D125_E D135_E D136_E D140_E D145_E D146_E D170_E D171_E D175_E D176_E D178_E D179_E D180_E D181_E D182_E D185_E D186_E D187_E D200_E D201_E D202_E D203_E D204_E D205_E D206_E D207_E D210_E D214_E D215_E D216_E D217_E D218_E D219_E D220_E D230_E D231_E D232_E D250_E D255_E D256_E D285_E D286_E
Sev.
4 4 4 4 4 4 4 4 4 2 2 4 4 4 4 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09 09 09 09 09 10 10 09 09 09 01 01 01 01 01 01 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 05 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 0000000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 01100000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"WOSA CDM/CRS: Firmware faulty, stopped" "WOSA CDM/CRS: Booter Firmware faulty, stopped" "WOSA CDM/CRS: V.24 line problem master <==> slave" "WOSA CDM/CRS: Slave controller without Firmware" "WOSA CDM/CRS: Safe controller faulty" "WOSA CDM/CRS: Safe controller no booter or faulty" "WOSA CDM/CRS: Counter controller faulty" "WOSA CDM/CRS: Counter controller no booter or faulty" "WOSA CDM/CRS: Firmware not loaded" "WOSA CDM/CRS: Safety switch of safe module open" "WOSA CDM/CRS: Safety switch of counter module open" "WOSA CDM/CRS: Device lock after retract & quit" "WOSA CDM/CRS: Device lock after jam in counter area" "WOSA CDM/CRS: Hardware requirements not ok" "WOSA CDM/CRS: Hardware requirements not ok" "WOSA CDM/CRS: Requirements for BIM missing" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Money jam during cash-in" "WOSA CDM/CRS: Note jam in safe area cassettes" "WOSA CDM/CRS: Note jam in safe area roller" "WOSA CDM/CRS: Note jam in safe area cassettes" "WOSA CDM/CRS: Note jam in counter area (cash out tray)" "WOSA CDM/CRS: Note jam in counter area (cash out tray)" "WOSA CDM/CRS: Note jam in counter area (cash out tray)" "WOSA CDM/CRS: Switch in safe area faulty/blocked" "WOSA CDM/CRS: Switch in safe area faulty/blocked" "WOSA CDM/CRS: Switch in safe area faulty/blocked" "WOSA CDM/CRS: Switch in safe area faulty/blocked" "WOSA CDM/CRS: Switch in safe area faulty/blocked" "WOSA CDM/CRS: Switch in counter area faulty/blocked" "WOSA CDM/CRS: Switch in counter area faulty/blocked" "WOSA CDM/CRS: Switch in counter area faulty/blocked" "WOSA CDM/CRS: Measurement station in safe area faulty" "WOSA CDM/CRS: Tape sensor in BIM module reports error" "WOSA CDM/CRS: Measurement station in counter area faulty" "WOSA CDM/CRS: BIM reader line faulty" "WOSA CDM/CRS: BIM communication faulty" "WOSA CDM/CRS: BIM note signals missing/inacceptable" "WOSA CDM/CRS: BIM returns error in call response" "WOSA CDM/CRS: Photosensor intensifier faulty" "WOSA CDM/CRS: Switch in safe area faulty / blocked" "WOSA CDM/CRS: Switch in safe area faulty / blocked" "WOSA CDM/CRS: Switch in safe area faulty / blocked" "WOSA CDM/CRS: Transport motor in safe area faulty" "WOSA CDM/CRS: Transport motor in safe area faulty" "WOSA CDM/CRS: Transport motor in safe area faulty" "WOSA CDM/CRS: Error during cash out tray handling" "WOSA CDM/CRS: Error during filling tray handling"
438
October 2004
U25604-J-Z745-1-7600
WOSA Error Classes)

00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 D287_E D295_E D296_E D310_E D320_E D330_E D340_E D405_E D406_E D407_E D408_E D410_E D411_E D420_E D421_E D430_E D431_E D440_E D441_E D451_E D461_E D510_E D520_E D530_E D540_E D605_E D610_E D611_E D620_E D621_E D630_E D631_E D640_E D641_E D651_E D661_E D700_E D705_E D710_E D720_E D730_E D740_E D810_E D820_E D830_E D840_E D901_E D902_E D903_E D904_E D905_E D906_E D907_E D908_E D909_E D910_E D911_E D912_E D913_E D914_E D915_E D916_E
Sev.
2 2 2 2 2 2 2 2 4 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"WOSA CDM/CRS: Error during cash out tray handling" "WOSA CDM/CRS: Photosensor of cash out tray covered" "WOSA CDM/CRS: Photosensor of filling tray covered" "WOSA CDM/CRS: Too many bundle reject cassette 1" "WOSA CDM/CRS: Too many bundle reject cassette 2" "WOSA CDM/CRS: Too many bundle reject cassette 3" "WOSA CDM/CRS: Too many bundle reject cassette 4" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: Metal in input tray detected" "WOSA CDM/CRS: Security stripe sensor defect" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: No separation possible" "WOSA CDM/CRS: Too many bad bills cassette 1" "WOSA CDM/CRS: Too many bad bills cassette 2" "WOSA CDM/CRS: Too many bad bills cassette 3" "WOSA CDM/CRS: Too many bad bills cassette 4" "WOSA CDM/CRS: ESCROW faulty (no signals)" "WOSA CDM/CRS: Cassette 1 faulty, write error" "WOSA CDM/CRS: Roller 1 or switch faulty" "WOSA CDM/CRS: Cassette 2 faulty, write error" "WOSA CDM/CRS: Roller 2 oder switch faulty" "WOSA CDM/CRS: Cassette 3 faulty, write error" "WOSA CDM/CRS: Roller 3 oder switch faulty" "WOSA CDM/CRS: Cassette 4 faulty, write error" "WOSA CDM/CRS: Roller 4 oder switch faulty" "WOSA CDM/CRS: Roller 5 oder switch faulty" "WOSA CDM/CRS: Roller 6 oder switch faulty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photo or pressure sensor faulty" "WOSA CDM/CRS: Photo or pressure sensor faulty" "WOSA CDM/CRS: Photo or pressure sensor faulty" "WOSA CDM/CRS: Photo or pressure sensor faulty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photosensor is dirty" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (counter area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)"
U25604-J-Z745-1-7600
October 2004
439
WOSA Error Classes)

00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 D917_E D918_E D919_E D920_E D921_E D922_E D923_E D924_E D931_E D932_E D933_E D934_E D935_E D936_E D941_E D942_E D943_E D944_E D945_E D946_E DF01_E DF03_E FE71_E FE9F_E FEA0_E FEA1_E FEA2_E FEB9_E FEBA_E FEBB_E FEBC_E FEBD_E FEBE_E FEBF_E FEC0_E FEC1_E FEC2_E FEC3_E FEC4_E FEC5_E FEC6_E FEC7_E FEC8_E FEC9_E FECA_E FECB_E FECC_E FECD_E FECE_E FECF_E FED0_E FED1_E FED2_E FED3_E FED4_E FFCA_E FFCB_E FFCC_E FFCD_E FFCE_E FFCF_E FFD0_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor is dirty (safe area)" "WOSA CDM/CRS: Photosensor roller1 dirty" "WOSA CDM/CRS: Photosensor roller2 dirty" "WOSA CDM/CRS: Photosensor roller3 dirty" "WOSA CDM/CRS: Photosensor roller4 dirty" "WOSA CDM/CRS: Photosensor roller5 dirty" "WOSA CDM/CRS: Photosensor roller6 dirty" "WOSA CDM/CRS: Wrong position roller1 or 36V missing" "WOSA CDM/CRS: Wrong position roller2 or 36V missing" "WOSA CDM/CRS: Wrong position roller3 or 36V missing" "WOSA CDM/CRS: Wrong position roller4 or 36V missing" "WOSA CDM/CRS: Wrong position roller5 or 36V missing" "WOSA CDM/CRS: Wrong position roller6 or 36V missing" "WOSA CDM/CRS: Metal or/and Stripe sensor defect" "WOSA CDM/CRS: Metal or/and Stripe sensor defect" "WOSA CDM/CRS: Wrong height of note in input tray" "WOSA CDM/CRS: Metal in CashIn tray detected" "WOSA CDM/CRS: Safe door must be closed during this command" "WOSA CDM/CRS: CashIn security failure" "WOSA CDM/CRS: Output position is not empty" "WOSA CDM/CRS: Application or configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Money taken during retract" "WOSA CDM/CRS: Error in bills presentation" "WOSA CDM/CRS: Error in bills presentation" "WOSA CDM/CRS: Error in bills presentation" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: No bills available" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Position locked" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Operator intervention required" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error"
440
October 2004
U25604-J-Z745-1-7600
WOSA Error Classes)

00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 00B9 FFD1_E FFD2_E FFD3_E FFD4_E FFD5_E FFD6_E FFD7_E FFD8_E FFD9_E FFDA_E FFDB_E FFDC_E FFDD_E FFDE_E FFDF_E FFE0_E FFE1_E FFE2_E FFE3_E FFE4_E FFE5_E FFE6_E FFE7_E FFE8_E FFE9_E FFEA_E FFEB_E FFEC_E FFED_E FFEE_E FFEF_E FFF0_E FFF1_E FFF2_E FFF3_E FFF4_E FFF5_E FFF6_E FFF7_E FFF8_E FFF9_E FFFA_E FFFB_E FFFC_E FFFD_E FFFE_E FFFF_E
Sev.
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
MStatus
09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09 09
MData
00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000 00000000000000000000

"WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Hardware error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Configuration error" "WOSA CDM/CRS: Application error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Installation error" "WOSA CDM/CRS: Application error"
U25604-J-Z745-1-7600
October 2004
441
WOSA Error Classes)
442
October 2004
U25604-J-Z745-1-7600
Tables
Tables
Table 1: Table 2: Table 3: Table 4: Table 5: Table 6: Table 7: Table 8: Table 9: Basic Software of ProCash/NDC . . . . . . . . . . . . . . . Basic Software of ProConsult/NDC Standard fonts table Software structure . . . . . . . . . . . . . 20 21 31 34 55 58 59 62 64 67 70 71 72 76 78 81 84 87 90 93 96 99 102 104
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
State summary . . . . . . . . . . . . . . . . . . . . . . . . ProCash/NDC, ProConsult/NDC steps belonging to NDC states Card Read state entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Read condition entry definitions
PIN Entry state entries . . . . . . . . . . . . . . . . . . . .
Table 10: Customer Selectable PIN state entries . . . . . . . . . . . . Table 11: Extension state entries . . . . . . . . . . . . . . . . . . . . Table 12: Envelope Deposit (C) state entries . . . . . . . . . . . . . . Table 13: Pre-Set Operation Code Buffer state table . . . . . . . . . . Table 14: Preset operation code buffer Extension state table Table 15: Four FDK Select Function state entries . . . . .
. . . . . . . . . . .
Table 16: Amount Entry state entries . . . . . . . . . . . . . . . . . . Table 17: Amount Check state entries . . . . . . . . . . . . . . . . .
Table 18: Information Entry state entries . . . . . . . . . . . . . . . . Table 19: Transaction Request state entries . . . . . . . . . . . . . .
Table 20: Extension state entries . . . . . . . . . . . . . . . . . . . . Table 21: Close state entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 22: FIT Switch state entries Table 23: Card Write state entries
Table 24: Enhanced PIN Entry state entries
U25604-J-Z745-1-7600
October 2004
443
Tables Table 25: Enhanced Amount Entry state entries . . . . . . . . . . . . Table 26: Extension state entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 110 112 114 116 119 120 123 126 129 132 135 136 139 142 145 148 152 154 154 157 157 160 161 162
Table 27: Language Code Switch state entries Table 28: Extension state entries
. . . . . . . . . . . . . . . . . . .
Table 29: Card Read - PIN Entry Initiation state entries . . . . . . . . Table 30: Extension state entries . . . . . . . . . . . . . . . . . . .
Table 31: Language Select From Card state entries . . . . . . . . . . Table 32: FDK Switch state entries . . . . . . . . . . . . . . . . . .
Table 33: FDK Information Entry state entries . . . . . . . . . . . . . Table 34: Extension state entries . . . . . . . . . . . . . . . . . . .
Table 35: Eight FDK Selection state entries . . . . . . . . . . . . . . Table 36: Extension state entries Table 37: Extension state entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 38: Audio Control state entries
Table 39: Hardware Fitness state entries
Table 40: Hardware Fitness Extension state entries . . . . . . . . . . Table 41: Smart FIT Check State . . . . . . . . . . . . . . . . . . .
Table 42: Skip state step . . . . . . . . . . . . . . . . . . . . . . . . Table 43: Screen control characters cross-reference . . . . . . . . .
Table 44: Screen control characters . . . . . . . . . . . . . . . . . . Table 45: Screen escape sequences cross-reference . . . . . . . . . Table 46: Screen escape sequences . . . . . . . . . . . . . . . . .
Table 47: Default Voice Message files . . . . . . . . . . . . . . . . . Table 48: Default WAVE files for Audio Echo on Keyboard . . . . . .
Table 49: Downloaded reserved screens supported by Wincor Nixdorf terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
444
October 2004
U25604-J-Z745-1-7600
Tables Table 50: Timer values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 189 190 200 206 209 218 223 226 236 239 242 245 249 251 254 258 261 264 267 270 272 275 281 287 296 445
Table 51: Alphabetical FIT references
Table 52: FIT fields listed by data track position Table 53: MAC flags definition Table 54: Code conventions
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 55: Transaction Request message . . . . . . . . . . . . . . . . Table 56: Solicited Status message . . . . . . . . . . . . . . . . . . . Table 57: Unsolicited Status message . . . . . . . . . . . . . . . . .
Table 58: Transaction Reply command message . . . . . . . . . . . . Table 59: Terminal Command message Table 60: State Tables Load Table 61: Screen Data Load . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 62: Configuration Parameters Load
Table 63: Enhanced Configuration Parameters Load . . . . . . . . . . Table 64: Option codes . . . . . . . . . . . . . . . . . . . . . . . . . Table 65: Interactive Transaction Response Table 66: FIT Data Load . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
Table 67: Encryption Key Load . . . . . . . . . . . . . . . . . . . . . Table 68: Extended Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . .
Table 69: Dispenser Currency Mapping Table Load
Table 70: Configuration IDLoad . . . . . . . . . . . . . . . . . . . . . Table 71: Date And Time Load . . . . . . . . . . . . . . . . . . . . . Table 72: Message Authentication Field Selection Load . . . . . . . . Table 73: Specific Command Reject Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Table 74: NDC function IDs assigned to step functions Table 75: Send Options And Timers message format
U25604-J-Z745-1-7600
October 2004
Tables Table 76: Acknowledge And Continue . . . . . . . . . . . . . . . . . Table 77: Acknowledge And Stop . . . . . . . . . . . . . . . . . . . 299 301 304 305 306 307 311 313 316 320 321 324 325 327 328 330 331 332 334 335 364 367 368 379 383
Table 78: Send Configuration Information . . . . . . . . . . . . . . . Table 79: Hardware Fitness Table . . . . . . . . . . . . . . . . . . . Table 80: Hardware Fitness Table Enhanced Table 81: Device Configuration Table . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . .
Table 82: Supply Status Device Table . . . . . . . . . . . . . . . . . Table 83: Supply Counters . . . . . . . . . . . . . . . . . . . . . . . Table 84: Send Error Log Information . . . . . . . . . . . . . . . . .
Table 85: Send Date/Time Info . . . . . . . . . . . . . . . . . . . . . Table 86: Hardware Configuration Data Table 87: Supplies Data . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
Table 88: Fitness Data . . . . . . . . . . . . . . . . . . . . . . . . . Table 89: Tamper and Sensor Status Data . . . . . . . . . . . . . . . Table 90: Software ID and Release Number . . . . . . . . . . . . . . Table 91: Local Configuration Option Digits . . . . . . . . . . . . . . Table 92: Solicited Status (Device Fault) . . . . . . . . . . . . . . . . Table 93: Error Severity Table . . . . . . . . . . . . . . . . . . . . . Table 94: Supplies Status Table . . . . . . . . . . . . . . . . . . . .
Table 95: Unsolicited Device Status . . . . . . . . . . . . . . . . . . Table 96: Electronic Journal Upload message format . . . . . . . . . Table 97: Printer Models . . . . . . . . . . . . . . . . . . . . . . . . Table 98: NDC Printer control characters . . . . . . . . . . . . . . .
Table 99: Cash Dispenser V1 (Class: 0007) . . . . . . . . . . . . . . Table 100:Cash Dispenser NG (Classes: 0018/001D)) . . . . . . . .
Table 101:Cash Cheque Deposit Module (CCDM) (Classes: 001A/XX1A) 392 446 October 2004
U25604-J-Z745-1-7600
Tables Table 102:Encryption Decryption Module (EDM) (Class: 000F) Table 103:Encryption Decryption Software (EDS) (Class: 0011) Table 104:Card Reader (Class: 0008/AA08) . . . . . . . . 405 406 407 411 414 415 416 417 418 418 419 420 422 423 423 424 424 426 427 428 430 431 433 434 435 435 447
. . . . . . . . . . . . . .
Table 105:Deposit Module (Class: 0017/AA17) . . . . . . . . . . . . . Table 106:Vandal Guard (Class: 0015) . . . . . . . . . . . . . . . . .
Table 107:Motorized Door (Class: 000E) . . . . . . . . . . . . . . . . Table 108:Printer (Class: 0032) . . . . . . . . . . . . . . . . . . . . . Table 109:Printer (Class: 0033) . . . . . . . . . . . . . . . . . . . . . Table 110:Printer (Class: 0034) . . . . . . . . . . . . . . . . . . . . . Table 111:Printer (Class: 0035) . . . . . . . . . . . . . . . . . . . . . Table 112:Printer (Class: 0038) . . . . . . . . . . . . . . . . . . . . . Table 113:Printer (Class: 0039) . . . . . . . . . . . . . . . . . . . . . Table 114:Printer (Class: 003E) . . . . . . . . . . . . . . . . . . . . . Table 115:Printer (Class: 003F) . . . . . . . . . . . . . . . . . . . . . Table 116:Printer (Class: 0040) . . . . . . . . . . . . . . . . . . . . . Table 117:Printer (Class: 0041) . . . . . . . . . . . . . . . . . . . . . Table 118:Printer (Class: 0042) . . . . . . . . . . . . . . . . . . . . . Table 119:Printer (Class: 0044) . . . . . . . . . . . . . . . . . . . . . Table 120:Printer (Class: 0045) . . . . . . . . . . . . . . . . . . . . . Table 121:Printer (Class: AA45) . . . . . . . . . . . . . . . . . . . . . Table 122:Printer (Class: 0048) . . . . . . . . . . . . . . . . . . . . . Table 123:Printer (Class: AA48) . . . . . . . . . . . . . . . . . . . . . Table 124:Transaction (Class: 6434) . . . . . . . . . . . . . . . . . .
Table 125:Cash Dispenser (Class: 643A) . . . . . . . . . . . . . . . . Table 126:Security Module (Class: 643C) . . . . . . . . . . . . . . . . Table 127:CashIn transaction (Class: 6446)
U25604-J-Z745-1-7600
. . . . . . . . . . . . . .
October 2004
Tables Table 128:EMV transaction (Class: 6459) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436 437 437 438
Table 129:Cheque transaction (Class: 645A) Table 130:EMV transaction (Class: 0091)
. . . . . . . . . . . . . . . . . . . . . . . . . .
Table 131:WOSA Cash Dispenser (Class: 00B9)
448
October 2004
U25604-J-Z745-1-7600
Figures
Figures
Figure 1: Figure 2: Figure 3: Figure 4: Figure 5: Terminal operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 206 208 225 286 Transaction message flow
Terminal to network messages . . . . . . . . . . . . . . Network to terminal commands . . . . . . . . . . . . . . Transaction Reply message accept/reject flowchart . . .
U25604-J-Z745-1-7600
October 2004
449
Figures
450
October 2004
U25604-J-Z745-1-7600
Abbreviations
API ARC ASCII ATM CDM CI CRT CSC CSP DES EBCDIC FDK FIT ID IDCU ITR MAC MDS NCR NDC Application Program Interface Application Return Code American Standard Code for Information Interchange Automated Teller Machine Cash Dispenser Module Customization Image Cathode Ray Tube Customer Service Center Customer Selected PIN Data Encryption Standard Extended Binary Coded Decimal Interchange Code Function Display Key Financial Institution Table IDentification ID Card Unit Interactive Transaction Response Message Authentication Code Modular Delivery System National Cash Register NCR Direct Connect
U25604-J-Z745-1-7600
October 2004
451
Abbreviations OAR PAN PC PCCP PIN POS QLLC SDLC SNA SOH SST TABS Open Account Relationship Primary Account Number Personal Computer PC Configurator Package Personal Identification Number Point of Sales (Cash Registers) Qualified Logical Link Control Synchronous Data Link Control System Network Architecture State Of Health Self Service Terminal Total Automatic Banking System
452
October 2004
U25604-J-Z745-1-7600
Related publications
Available manuals
Basically all the manuals you need to get information about configurations and functionality of ProCash/NDC, ProConsult/NDC, ProDevice (WOSA), CSC-W32 and AddOn products can be downloaded from the Wincor Nixdorf intranet server. Link: http://ssp-asw
ProCash/NDC and ProConsult/NDC Manuals

DESIGNATION ProCash/NDC-DDC Prog. Reference ProCash/NDC Installation manual ProConsult/NDC Installation manual ProCashIn/Online Installation & Configuration manual GDI Printer Overlay Framework User Guide ProCash/NDC-DDC ProConsult/NDC-DDC WEB-Extensions Installation & Configuration manual Protopas Module Construction Kit Programming Guide Protopas Framework Documentation Programming Guide Protopas Host Protocol and Communication Frameworks Programming Guide VERSION ORDER NUMBER 1.1/03 1.3/00 1.3/00 1.1/00 1.3/00 1.3/00 1.1/00 (PDF file) (PDF file) (PDF file) (PDF file) (PDF file) (PDF file)
4.1/00 4.1/00 4.1/00
(PDF file) (PDF file) (PDF file)
ProCash/NDC ProConsult/NDC Installation manuals These two Installation manuals contain detailed descriptions of configuration parameters of ProCash/NDC, ProCash/DDC and ProConsult/NDC, ProConsult/DDC, which are stored in the Windows registry. Further contents are descriptions about several Utilities which are additionally delivered.
U25604-J-Z745-1-7600
October 2004
453
Related publications ProCash/NDC-DDC Programmers Reference This manual gives detailed descriptions about Steps, Prep functions and variables used by ProCash/NDC and ProConsult/NDC. Furthermore it gives information about the ProCash/NDC ProConsult/NDC architecture and the connection with Protopas basic frameworks. ProTopas Module Konstruction Kit Programming Guide Describes the Frameworks of the ProTopas Manager and gives detailed API descriptions for the programmer. With this manual a programmer is able to build up Protopas applications. ProTopas Framework Documentation Programming Guide Gives a global overview about the ProTopas Framework architecture and describes the interaction between the different frameworks. ProTopas Host Protocol and Communication Frameworks ProGramming Guide Describes the APIs of the Communication Frameworks from ProTopas Manager and gives detailed descriptions for the programmer. ProCash/NDC ProConsult/NDC WEB-Extension Inst. & Conf. manual The Installation & Configuration manual contains detailed descriptions how the add on product WEB-Extensions is integrated in ProCash/NDC and ProConsult/NDC. It also gives detailed descriptions about additional configuration parameters, which are needed to enable the WEB-Extensions. ProCashIn/Online Inst. & Conf. manual The Installation & Configuration manual contains detailed descriptions how the add on product ProCashIn/Online is integrated in ProCashIn/NDC and ProCashIn/DDC. It also gives detailed descriptions about additional configuration parameters, which are needed to enable ProCashIn/Online. GDI Printer Overlay Framework User Guide The User Guide describes how GDI print is realised in ProCash/NDC, ProCash/DDC, ProConsult/NDC and ProConsult/DDC. It contains detailed parameter descriptions that are required (mandatory or optional) to enable Windows GDI printing.
454
October 2004
U25604-J-Z745-1-7600

Manual de Usuario Procash NDC V 1 3

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual de Usuario Procash NDC V 1 3

Uploaded by

Copyright:

Available Formats

ProCash/NDC ProConsult/NDC

Edition October 2004

Copyright and Trademarks

Additional useful Information

Since May 2002 until November 2003:

Whats new Since October 2001 until May 2002:

Wincor Nixdorf Solution

Purpose of the Document

Purpose of the Document

(ProCash/NDC only) (ProCash/NDC only) (ProCash/NDC only)

E-Journal Upload (EJU)

continued on next page ...

Multi Vendor capability

Multi Vendor capability

NCR cash systems Diebold cash systems, (except OPTEVA)

Fujitsu cash systems Olivetti cash systems Delarue cash systems

Software Products of ProCash/NDC

Software Products of ProCash/NDC

Software Products of ProConsult/NDC

Software Products of ProConsult/NDC

Software Products of ProConsult/NDC

Dynamic Link Libraries (DLL)

Dynamic Link Libraries (DLL)

Parameter / Data Files

Parameter / Data Files

Parameter / Data Files

Compatible Customization Data

Screen Data (LYNXCI\SCREEN\XXX [1])

are the predefined display screens provided by the host.

EMV Parameters (LYNXCI\EMV) This section contain specific EMV parameters.

Parameter / Data Files

Extended Configuration Data

Parameter / Data Files

Global Screen Configuration

Details will be given in the ProCash/NDC ProConsult/NDC Installation manual.

Parameter / Data Files

Error Mapping Configuration

Details will be given in the ProCash/NDC ProConsult/NDC Installation manual

ccvtable.fil (asc, ebc) cfgmanag.lnk \PROTOPAS\CONF\ TUNING.XP tune_xp.bat tune_xp.reg explorer.inf

File Structure perform.inf bootload.inf autorun.inf nowelc.inf \PROTOPAS\WORK cccmos.bin

*.PCX, *.BMP, *.ICN, *.JPG

*.AVI, *.MPG, *.MPEG

\PROTOPAS\FONTS\ GDI_PRT \PROTOPAS\TOOLS HostSim.exe

File Structure cfgmanag.mnu

cfgmanag.hlp ina2def.exe compregf.exe cpyntfnt.exe asc2pcc.exe icn2asc.exe asc2icn.exe sethwppf.exe

dcsopmgr.exe initepp.exe dof-rj03.exe rj03-dof.exe confchck.exe

File Structure addonchk.exe cfgmedit.exe

SUPERVISOR SUPERVISOR MODE MODE SUSPEND SUSPEND MODE MODE

OUT OF OUT OF SERVICE SERVICE

Exiting power-up mode

in-service mode out-of-service mode power-up mode supervisor mode

The terminal exits this mode under the following conditions:

Service and Operating(SOP)

The terminal exits this mode under the following conditions:

Service and Operating(SOP)

Service and Operating(SOP)

Start Rear Balancing

Customize Rear Balancing functions

Dispense Below Zero

Dispense Below Zero

Dispense Below Zero Changes of cash counter behaviour:

Cash Dispenser Module

.PCX, .BMP, .ICN, .JPG

.AVI, .MPG, *.MPEG