Wincor Document PDF

ProCash/NDC V1.
3/00
ProConsult/NDC V1.1/00
User Guide
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
Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\User1TOC.fm
Contents
Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What’s new . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
© Siemens Nixdorf Informationssysteme AG 1995
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Wincor Nixdorf Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Function Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Multi Vendor capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Software Products of ProCash/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software Products of ProConsult/NDC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Software Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Dynamic Link Libraries (DLL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Parameter / Data Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Types of Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Compatible Customization Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Extended Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Global Screen Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Error Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Font Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Standard Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
System Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Software Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Directory Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Modes of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Exiting power-up mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Out-of-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
In-service mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Offline mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Suspend mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Service and Operating(SOP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
October 2004
Contents
Automatic return . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
In-service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Start Rear Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Customize Rear Balancing functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Dispense Below Zero . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

FDK Information Entry State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Extension to State (X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Eight FDK Selection State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Multi Language Extension to State (Y) . . . . . . . . . . . . . . . . . . . . . . . . . 136
Audio Control State (i) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Hardware Fitness State (‘h’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Extension to State (‘h’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Smart FIT Check State (‘k’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Skip State step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Screen Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Displaying Graphics as Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Full Screen graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
– Display resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Displaying MacroMedia Flash executables . . . . . . . . . . . . . . . . . . . . . 159
Displaying Video files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Voice Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
– Auto Voice Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
– Audible Echo on Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Reserved Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Language Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Miscellaneous Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Terminal Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Logical Unit Number (LUNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Timer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Local download feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Configure local download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
PIN and PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Personal Identification Number (PIN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Variable length PIN Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
PIN Offset Number (DES verification) . . . . . . . . . . . . . . . . . . . . . . . . . 178
PIN Verification Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
October 2004
Contents
Local PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Network PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
– ANSI PIN/PAN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
– Diebold PIN Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
ID Card and FIT Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
ID Card Data Tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
FIT (Financial Institution Table) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
FIT Library Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Multi Card, Multi Institution Capability . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Alternate Transaction Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
FIT Data Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Institution Index (PIDDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Institution Identification (PFIID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
FIT Switch Index (PSTDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Maximum PIN Entry Digits (PMXPN) . . . . . . . . . . . . . . . . . . . . . . . . . . 191
PIN Check Length (PCKLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
PIN Pad Character (PINPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
PAN Index (PANDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
PAN Length (PANLN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
PAN Pad Character (PANPD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
PIN Retry Count Index (PRCNT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Offset Number Index (POFDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Decimalization Table (PDCTB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Encrypted PIN Key (PEKEY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Data Track Locator (PINDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Language Code Index (PLNDX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Message Authentication (MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
MAC flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Security Terminal Number (Machine Number) . . . . . . . . . . . . . . . . . . . 201
MAC data field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Time variant number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Typical Message Authentication Procedure . . . . . . . . . . . . . . . . . . . . . 202
MACing for State and FIT Table Load commands . . . . . . . . . . . . . . . . . 203
Triple DES operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
EMV capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Remote Key Loading (RKL) capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
October 2004
Contents
Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Messages from Terminal to Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Transaction Request message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Solicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Unsolicited Status messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Network to Terminal messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Transaction Reply command (message ID ‘4’) . . . . . . . . . . . . . . . . . . . 226
Terminal Command message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

State Tables Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Screen Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Enhanced Configuration Parameters Load . . . . . . . . . . . . . . . . . . . . . 249
Interactive Transaction Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
FIT Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Extended Encryption Key Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
Dispenser Currency Mapping Table Load . . . . . . . . . . . . . . . . . . . . . . 267
Configuration ID Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Date And Time Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Message Authentication Field Selection Load . . . . . . . . . . . . . . . . . . . 275
Specific Command Reject Conditions . . . . . . . . . . . . . . . . . . . . . . . . . 280
Terminal operations in Transaction Replies . . . . . . . . . . . . . . . . . . . . . . . . 287
Print Immediate (‘4’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Set Next State and Print (‘5’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Night Safe Deposit and Print (‘6’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Deposit and Print (‘1’ or ‘7’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Dispense, Deliver and Print (‘2’ or ‘8’) . . . . . . . . . . . . . . . . . . . . . . . . . 291
Display and Print (‘3’ or ‘9’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Eject Card, Dispense and Print (‘A’) (Card before Cash) . . . . . . . . . . . 292
Eject Card, Dispense and Print (‘F’) (Parallel CBC) . . . . . . . . . . . . . . . 293
Parallel Eject/Dispense and Print (Fast Cash) (‘B’ or ‘C’) . . . . . . . . . . . 294
Print Data and Stay in Present State (‘P’) . . . . . . . . . . . . . . . . . . . . . . . 294
Print Statement and Set Next State (‘Q’) . . . . . . . . . . . . . . . . . . . . . . . 295
Electronic Journal Upload (EJU) commands . . . . . . . . . . . . . . . . . . . . . . . 295
Send Options And Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Acknowledge And Continue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Acknowledge And Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
NDC Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Solicited Status (terminal state) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
October 2004
Contents
– Send Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

– Send Supply Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
– Send Error Log Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
– Send date/time information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
– Hardware Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
– Supplies Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
– Fitness Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
– Tamper and Sensor Status Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
– Software ID and Release Number . . . . . . . . . . . . . . . . . . . . . . . . . . 328
– Local Configuration Option Digits . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Solicited Status (device fault) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Unsolicited Device Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
– Power Up (unsolicited) (DID ‘B’) . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
– Card Reader (sol./unsol.) (DID ‘D’) . . . . . . . . . . . . . . . . . . . . . . . . . 338
– Dispenser (sol./unsol.) (DID ‘E’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
– Depository (sol./unsol.) (DID ‘F’) . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
– Envelope Dispenser (unsolicited) (DID ‘\’ . . . . . . . . . . . . . . . . . . . . 348
– Receipt Printer (unsolicited) (DID ‘G’) . . . . . . . . . . . . . . . . . . . . . . . 349
– Journal Printer (unsolicited) (DID ‘H’) . . . . . . . . . . . . . . . . . . . . . . . 351
– Statement Printer (sol./unsol.) (DID ‘V’) . . . . . . . . . . . . . . . . . . . . . . 353
– Vandal Guard (unsolicited) (DID ‘J’) . . . . . . . . . . . . . . . . . . . . . . . . . 356
– EDM - Module (unsolicited) (DID ‘L’) . . . . . . . . . . . . . . . . . . . . . . . . 357
– Door Access (unsolicited) (DID ‘N’) . . . . . . . . . . . . . . . . . . . . . . . . . 361
– Sensor Status (unsolicited) (DID ‘P’) . . . . . . . . . . . . . . . . . . . . . . . . 361
– Supervisor Key Messages (unsolicited) (DID ‘R’) . . . . . . . . . . . . . . 363
Electronic Journal Upload (EJU) Message . . . . . . . . . . . . . . . . . . . . . . 364
Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Printer Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Printer Control Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Electronic journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Electronic journal storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Types of journal information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Printing with the Windows GDI Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Additional Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

NDC Standard Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
ASCII to EBCDIC Code Conversion Table . . . . . . . . . . . . . . . . . . . . . . . . . 376
Screen Design Worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
October 2004
Contents
M-Status & M-Data Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

CSC-W32 Error Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
Cash Dispenser V1 (old series) (Class: 0007) . . . . . . . . . . . . . . . . . . . 379
Cash Dispenser NG (Classes: 0018/AA18/001D) . . . . . . . . . . . . . . . . 383
Cash Cheque Deposit Module (Classes: 001A/XX1A) . . . . . . . . . . . . . 392
Encryption Decryption Module (Class: 000F) . . . . . . . . . . . . . . . . . . . . 405
Encryption Decryption Software (Class: 0011) . . . . . . . . . . . . . . . . . . . 406
Card Reader (Class: 0008/AA08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Deposit Module (Class: 0017/AA17) . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Vandal Guard (Class: 0015) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
Motorized Door (Class: 000E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Printer (Class: 0032) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Printer ND71/74/98/9A/9C/9E/TH30 (Class: 0033) . . . . . . . . . . . . . . . 417
Printer ND75/75S/94 (Class: 0034) . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Printer ND79 (Class: 0035) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
Printer ND99 (Class: 0038) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Printer ND97/TH97/TP01/NP01/TP05/NP05 (Class: 0039) . . . . . . . . . 420
Printer TH21 (Class: 003E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
Printer Extensions (Class: 003F) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Printer Monitor ND9G (Class: 0040) . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Printer Monitor TH21 (Class: 0041) . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Printer System Framework (Class: 0042) . . . . . . . . . . . . . . . . . . . . . . . 424
Printer TP07 GDI (Class: 0044) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Printer TP07 (Class: 0045) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Printer USB/TP07 (Class: AA45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
Printer TP06 (Class: 0048) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Printer USB/TP06 (Class: AA48) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Application Error Classes (LYNX errors) . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Transaction (Class: 6434) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Cash Dispenser (Class: 643A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Security Module (Class: 643C) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
CashIn transaction (Class: 6446) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
EMV transaction (Class: 6459) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Cheque transaction (Class: 645A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Electronic Journal (Class: 0091) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
WOSA Error Classes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
WOSA Cash Dispenser (Class: 00B9) . . . . . . . . . . . . . . . . . . . . . . . . . 438
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
October 2004
Contents
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
October 2004
Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\user1.fm
What’s new
This section lists a summery of documentation changes and enhancements of
the ProCash/NDC User Guide.
Since November 2003 until October 2004:
© Siemens Nixdorf Informationssystem e AG 1995
● 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:

● 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
What’s new
Since October 2001 until May 2002:

● 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, FIT’s,
Screens and Parameters controls the terminal, thus defining the available
functions. Those are typically (but not exclusively):
● Withdrawal (ProCash/NDC only)
● Fast cash (ProCash/NDC only)
● Deposit (ProCash/NDC only)
● Balance inquiry
● Transfer
● Payment
● PIN change
● Rear Balancing
● Multi language
● Statement print
● MACing
● Triple DES security
● EMV support
● Cheque deposit
● E-Journal Upload (EJU)
October 2004 17
Supported hardware Introduction
Supported hardware
Currently following systems and hardware components are supported:
ATM’s:
● CSC4xx Rear/Frontload
● CSC400 Frontload
● ProCash-Compact
● ProCash 2000
● CSC21xx, CSC1500
● Cash Recycling System (CRS), 3100xe
Info Terminals:
● ProPrint 200
● ProPrint 2000
● ProConsult, Certo
Dispenser modules:
● CDM-V1, CDM-NG, CMD-V4, CDM-NG (6 cassettes)
Needle printers:
● Journal: ND98D, ND98, ND71, NP06
● Receipt: ND9E, ND71, ND9A, NP07
● Statement: ND97, ND94, ND97
Thermal printers:
● Receipt: ND9C, ND99, ND9G, TH21, TH22, TP07
● Journal: TH30, TP06
● Statement: TH97/G, TP01, TH23
Card readers:
● ID14 (Sankyo Seiki), ID15 (Wincor Nixdorf), ID18 (OMRON), V2X,
ID24 (DIP reader), ICM300 (manual smart card reader)
Encryption modules:
● EDM module (restricted security), EPP’s V4, V4+, V5 (international)
Deposit modules:
● Papalakko, Wincor Nixdorf
● Cheque Deposit Module (CCDM)
continued on next page ...
18 October 2004
Introduction Multi Vendor capability
Miscellaneous:
● Operator Panel (Low- or high end)
● Touch screen support
● Power Supply box
● Sound card
● USB support
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:
● 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:
● 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 current Systems

Release
Operating system
Windows XP Professional see Note2
Windows NT 4.00 Srv. 6 all
CSC-W32 2.0/53 all
ProCash/Topas 4.1/00 all
ProSop 3.1/13 all
WOSA/XFS-SSP (2.0) 3.1/72 all
WOSA/XFS-SSP/MV 3.1/71 all
PARAC-NT 3.2/02 all
ProView 3.7/01 all
ProCash/NDC 1.3/00 all
ProCash/NDC-SOP
Communication software
SNA-Workstation 4.0 optional
Eicon software components 3.0 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 PC’s only.
20 October 2004
Introduction Software Products of ProConsult/NDC
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 current Systems

Release
Operating systems
Windows XP Professional see Note2
Windows NT 4.00 Srv. 6 all
CSC-W32 2.0/53 all
ProCash/Topas 4.1/00 all
ProSop 3.1/13 all
WOSA/XFS-SSP/MV 3.1/71 all
PARAC-NT 3.2/02 all
ProView 3.7/01 all
ProConsult/NDC 1.1/00 all
ProConsult/NDC-SOP
Communication software
SNA-Workstation 4.0 optional
Eicon software components 3.0 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 PC’s only.
October 2004 21
Software Products of ProConsult/NDC Introduction
22 October 2004
Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User2.fm
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:
● 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
Dynamic Link Libraries (DLL) 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 Dynamic Link Libraries (DLL)
● 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
Parameter / Data Files
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 ATM’s. 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 Parameter / Data Files
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.

● 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 ATM’s 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
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
● 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 Parameter / Data Files
● Function ID mapping (LYNXPAR\FUNC_ID_MAP)

This section contain the assignment to the ProCash/NDC or
ProConsult/NDC step functions and function ID’s 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 ID’s 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
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 File name Designation 640x480 800x600 1024x768

(W * H) [1] (W * H) [1] (W * H) [1]
1 NDC-SA1.FON Single Size Alpha 1 20x30 25x37 32x48
2 NDC-SA2.FON Single Size Alpha 2 20x30 25x37 32x48
> NDC-DA1.FON Double Size Alpha 1 40x30 50x37 64x48
? NDC-DA2.FON Double Size Alpha 2 40x30 50x37 64x48
3 NDC-GA1.FON Standard Graphic 1 20x30 25x37 32x48
9 NDC-SARA.FON Single Size Arabic 20x21 25x26 32x33
B NDC-DARA.FON Double Size Arabic 40x42 50x52 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 (DLL’s) makes it difficult to assign
configuration files and DLL’s to the right software sub product.
Protopas based DLL’s and ProCash/NDC or ProConsult/NDC specific DLL’s 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 Description

\CSCW32 modules of CSC-W32 operating system
\WOSASSP modules of ProDevice (WOSA)
\PROSOP modules of ProSop
\PROTOPAS
fwstrt.bat Starts ProCash/NDC or ProConsult/NDC
fwkill.bat Stops ProCash/NDC or ProConsult/NDC
ccprot.log Log file of Host and ATM messages
\PROTOPAS\BIN
dcApplFW.dll Application Framework
dcSttFW.dll Transaction Framework
dcMsgcFW.dll Message Control Framework
dcConvFW.dll Converter Framework
dcCdmFW.dll Cash Dispenser Framework
dcSueFW.dll Sop User Exit Framework
dcSecure.dll Security Overlay Framework
3DesEppF.dll Triple DES EPP Overlay Framework
dcDevSta.dll Device Status Framework
dcServic.dll ProCash/NDC-SOP, ProConsult/NDC-SOP
Service Framework
dcSopDia.dll ProCash/NDC-SOP, ProConsult/NDC-SOP
Dialog Framework
ndcDiaFW.dll NDC Dialog Framework
ndcPrtFW.dll NDC Printer Framework
34 October 2004
System Setup Directory Structure

dcPrtGdi.dll GDI Printer Overlay Framework
dcEmvTa.dll EMV Transaction Overlay Framework
dcEmvCv.dll EMV Converter Overlay Framework
dcEmvMc.dll EMV Message Control Overlay Framework
dcTcp2h.dll TcpIP converter for 2 bytes binary headers

(header length excluded)
dcTcp2hi.dll TcpIP converter for 2 bytes binary headers
(header length included)
dcTcp4a.dll TcpIP converter for 4 bytes ASCII headers
dcTcp4ai.dll TcpIP converter for 4 bytes ASCII headers
(header length included)
dcTcp3a.dll TcpIP converter for 3 bytes ASCII headers
dcTcpSTX.dll TcpIP converter for STX and ETX message
length calculation
dcSimCom.dll Host Simulator Framework
ccrcconv.exe Updates the Windows registry with contents
of *.RCK files
\PROTOPAS\CONF
Kconf.exe Converts *.INA files to *.RCK format
Kconf.txt Describes functionality of Kconf.exe
conv.bat Update job for *.INA files to update existing
and store new parameters in the Registry
conv-all.ok (conv-all.bat) 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).
prtmakro.bat Batch job to store additional parameters for
the journal and receipt printer to enable ’INIT’
sequences via makros.
prtmakro.ina Parameter source file of printer parameters
used by Kconf.exe
prosop.bat Batch job to set SOP User Exit and Trace
menu items for ProSop (Single DES).
October 2004 35

prosop.ina Parameter source file of SOP User Exit and
Trace (Single DES) used by Kconf.exe
sop3des.bat Batch job to set SOP User Exit and Trace
menu items for ProSop (Triple DES).
sop3des.ina Parameter source file of SOP User Exit and
Trace (Triple DES) used by Kconf.exe
gdi_prt.bat Batch job to set GDI printer parameters.
gdi_prt.ina Parameter source file of GDI printer
parameters used by Kconf.exe
logon.bat Batch job to set parameters in the Registry to
activate automatic logon.
logon.ina Parameter source file for automatic logon
parameters
autostrt.bat Batch job to set one parameter which
activates an automatic call of
’C:\STARTUP.BAT’ after restart.
autostrt.ina Parameter source file for the automatic
’startup.bat’ call.
ccerrmap.ina Parameter source file of all application and
CSC-W32 error codes and mapping
definitions which is used during ’conv-all.bat’
process is running.
lynxsop.ina Parameter source file of Rear Balancing step
table parameters which is used during
’conv-all.bat’ process is running.
ccvtable.fil (asc, ebc) Line convertion tables: EBCDIC - ASCII and
ASCII - ASCII (default is ASCII - ASCII)
cfgmanag.lnk Link of the Configuration Manager for the
start bar of Windows.
\PROTOPAS\CONF\ Contains configuration files needed to
TUNING.XP optimize Windows XP
tune_xp.bat Batch routine that installs the *.INF files and
contents of *.REG files.
tune_xp.reg Windows XP general optimations
explorer.inf Windows XP Explorer optimations
36 October 2004

perform.inf Windows XP settings for enhanced
performance
bootload.inf Windows XP reduced boot delay time
autorun.inf Windows XP autorun settings
nowelc.inf Windows XP switch off welcome screen

\PROTOPAS\WORK
cccmos.bin CMOS file - stores transaction oriented
counters and device statuses (e.g. Last
Transaction Status information)
\PROTOPAS\BITMAPS
\PROTOPAS\BITMAPS\640x480 Resolution depended sub directories where
\PROTOPAS\BITMAPS\800x600
\PROTOPAS\BITMAPS\1024x768 the default graphics are stored during the
installation.
*.PCX, *.BMP, *.ICN, *.JPG 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.
dctmpoos.bmp Bitmap which is displayed during the system
shutdown initiated by the restart handler in a
fatal error condition.
dcoos.bmp Bitmap which is permanently displayed if the
maximum system reboots has been initiated
by the restart handler.
*.AVI, *.MPG, *.MPEG Video animation file which can be configured
instead of a ’normal’ graphic in the registry
section “..\LYNXCI\SCREEN”.
\PROTOPAS\FONTS
\PROTOPAS\FONTS\640x480 Resolution depended sub directories where
\PROTOPAS\FONTS\800x600
\PROTOPAS\FONTS\1024x768 the default fonts are stored during the
installation.
\PROTOPAS\FONTS\ Contains Windows fonts that are used if GDI
GDI_PRT printing is enabled (e.g. ND9G, TP07).
\PROTOPAS\TOOLS
HostSim.exe Dialog oriented host simulator simulates host
to terminal messages.
October 2004 37

MfcDlg.exe Dialog window where you can enter specific
screens to display during runtime.
MfcVar.exe Displays variables (e.g. Opcodes) during the
transaction flow.
protlog.exe Message analyzer of log file ’CCPROT.LOG’
reboot.exe Initiates a system shutdown or relogon
write-id.exe Utility to write track 1,2 or/and 3 data on ID
cards via ID Card Unit.
write-id.cmd Batch file which can be modified for calling
write-id.exe to write tracks on ID cards.
fontedit.exe Modifies and view Windows font contents
asc2fon.exe Converts ASCII font files to Windows fonts
fon2asc.exe Extracts Windows fonts to ASCII text files
prt-dof.exe Sends control sequences (in *.DOF format)
to the receipt or journal printer.
asc2dof.exe Converts ASCII printer fonts to *.DOF format.
dof2asc.exe Extracts DOF files to ASCII printer font files
asc-nd99.exe Converts ASCII printer font files to *.SWF
format for ND99 printer.
nd99-asc.exe Extracts binary *.SWF font files of ND99 to
ASCII matrix font files.
ldnd99.exe Font and Logo loader for ND99
nd99logo.exe Extracts ND99 logo files to ASCII matrix file
asc2logo.exe Converts ASCII logo files to binary logo files
for ND99.
nd9e-dof.exe Converts an ASCII logo file to DOF format for
ND9E printer.
pcx2asc.exe Extracts 2 or 16 color PCX graphics to ASCII
matrix text file.
cfgmanag.exe Configuration Manager. Easy access to
analyzing tools and configuration data via
pull down menus.
38 October 2004

cfgmanag.mnu Menu definition file for the Configuration
Manager that allows menu configuration.
(Will not be installed, but can be ordered from
WCN support).
cfgmanag.hlp Help text file for the Configuration Manager.

ina2def.exe Converts INA files to PARAC definition RC
source files.
compregf.exe Compares an extracted registry text file with
the contents of the Windows registry.
cpyntfnt.exe Installes and registers Windows font files.
asc2pcc.exe Converts ASCII files to PCC/PCX files.
icn2asc.exe Extracts ICN icon files to ASCII matrix files.
asc2icn.exe Converts ASCII files to ICN files.
sethwppf.exe Sets hardware depended menu for Status
Overview in ProSop and deconfigures paper
journal of no journal printer is installed.
(used during installation).
prt-raw.exe Test utility that can print a text file with ASCII
printer data and macros via printer interface
of CSC-W32.
printraw.exe 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).
dcsopmgr.exe ProCash/NDC-SOP, ProConsult/NDC-SOP
User Manager.
initepp.exe Deletes keys from EPP and gives detailed
information about the EPP hardware.
dof-rj03.exe Converts ASCII printer fonts to *.DOF format
for NP06/TP06 and NP07/TP07.
rj03-dof.exe Converts hex *.DOF files of NP06/TP06 and
NP07/TP07 font definitions to ASCII files.
confchck.exe Configuration Utility. It is called during
installation and by the Config. Manager
October 2004 39

addonchk.exe Installation Utility that is called during
installation only.
cfgmedit.exe 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:
● 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
SUPERVISOR
SUPERVISOR
OFFLINE
OFFLINE MODE
MODE
SUSPEND
SUSPEND
MODE
MODE
OUT
OUT OF
OF IN
IN SERVICE
SERVICE
SERVICE
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:
● 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:
● 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)
While in-service, the terminal uses the configuration data to make transaction
sequence decisions.
The terminal exits in-service mode under the following conditions:
● 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:
● 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:
● 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:
● 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:
● 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 doesn’t accept customer cards.
44 October 2004 U25604-J-Z745-1-7600

Modes of Operation Service and Operating(SOP)
The terminal exits this mode under the following conditions:

● 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)
Service and Operating(SOP)

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:
● 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 start-
up 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

Service and Operating(SOP) 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:
● 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)
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:
● on rear load terminals on the operator panel
● on front load terminals on the screen
Start Rear Balancing
● 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:
● 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 Modes of Operation
Changes of cash counter behaviour:

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:
● Cash Dispenser Module
Checks shutter and transport way status, performs retract or close shutter commands,
sends status message to the host
● 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:
● 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 consumer’s
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 States
A summary of all the state types is shown in the following tables.
Table 5: State summary
State Name State Description

Type
Card Read A Reads the magnetic stripe from the ID card and then
usually indicates a PIN entry state as the next state.

PIN Entry B Reads the PIN number entered by the customer and
verifies that the PIN entered is valid.
Unlock C After this state the terminal immediately goes to the
Envelope next state.
Dispenser
Preset D Clears and sets any or all 8 bytes of the operation code
Operation buffer.
Code Buffer
FDK E Reads the code of each operation key pressed by the
Selection customer. The key codes are stored in the operation
code buffer. The next state varies depending on the
customer’s selection.
Amount F Reads the entered amount, displays that amount on the
Entry 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.
Amount G Verifies that the amount entered is a whole amount
Check (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.
Information H Reads in a variable-length string of numerical keys and
Entry 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 customer’s
input.
U25604-J-Z745-1-7600 October 2004 55


Type
Transaction I Sends a Transaction Request message to the network
Request and executes the Transaction Reply commands
received from the network. The next state depends on
the network response.
Close J Returns or retains the customer’s 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).
FIT Switch K 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 customer’s institution.
Card Write L During this state, the terminal writes the contents of the
track 3 data buffer onto the magnetic stripe of a card
Enhanced M Same functions as B state, but including updating track
PIN Entry data on the ID card.
Card read T This card read state is used, if the application requires
(Non-000 that the number of the card read state be something
state other than 000.
applications)
Hardware h The Hardware Fitness state checks for fatal error
Fitness 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.
Smart FIT k The Smart FIT Check state performs a FIT check with
Check the chip data that is read from the chip of a smart card.
Skip Step The Skip Step is used to skip states which are not
supported by ProCash/NDC or ProConsult/NDC.
Enhanced R Reads the entered amount, displays it on the screen,
Amount and stores it in the Amount buffer, General Purpose
Entry buffer B or C buffer.
56 October 2004 U25604-J-Z745-1-7600


Type
Language S In this state the flow of a transaction is switched on
Code Switch whether a language code is present in the card data or
not.
Language V In this state one set of state tables can be used to

Select from display screens in different languages within the same
Card transaction. This is determined by a code on the
cardholder’s card.
FDK Switch W This state reads the data buffer from the 8 FDK
selection state to identify which next state the terminal
should go.
FDK X This state translates the FDK selected by the
Information cardholder into a value that is placed in the specified
buffer for use by an FDK switch state.
8 FDK Y This state reads the FDK selected by the cardholder,
Selection stores the key code in an FDK buffer for use by an FDK
switch state, and updates the operation code buffer.
Customer b This state allows the consumer to change the PIN.
Selected PIN
Audio i This state allows the consumer to set the audio volume
Control for the played message and to switch audio channels.
Expanded ’_’ FIT switch state with enhanced number of next states
FIT Switch depending on the specified switch index in the FIT
table.
Extension Z 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.
U25604-J-Z745-1-7600 October 2004 57

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 Step State Step

Type Type
A DC_CARD_READ S NDC_LANGUAGE_SWITCH
B DC_PIN_ENTRY T NDC_CARD_PIN
C DC_DISPENSE_ENVELOPE V NDC_CARD_LANGUAGE
D DC_PRESET_OP_CODE W NDC_FDK_SWITCH
E DC_FDK_SELECT4 X NDC_FDK_INFO_ENTRY
F DC_AMOUNT_ENTRY Y NDC_FDK_SELECT
G DC_WHOLE_DOLLAR_CHECK Z NDC_EXT
H DC_INFORMATION_ENTRY ’_’ NDC_EXP_FIT_SWITCH
I DC_TRAN_REQUEST b NDC_CUST_SEL_PIN
J DC_CLOSE_TRAN i NDC_AUDIO_CONTROL
K DC_FIT_SWITCH P NDC_EXP_FIT_SWITCH
L DC_WRITE_CARD R NDC_ENH_AMOUNT_ENTRY
M DC_ENH_PIN_ENTRY k DC_HARDWARE_FITNESS [1]
N DC_CAMERA_CONTROL all DC_NEXT_X (X = 1-8) [1]
states
[1] - Wincor Nixdorf specific state
58 October 2004 U25604-J-Z745-1-7600

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:
● 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
Table 7: Card Read state entries
Entry Definition
1 state type
2 screen number
3 correct read next state number
4 error (misread) screen number
5 read condition 1
6 read condition 2
7 read condition 3
8 card return flag
9 no FIT match next state number
U25604-J-Z745-1-7600 October 2004 59

The card read (A) state entries are defined as follows:
State type
Entry number: 1
Valid range: A
Description: This state ID identifies this state table as a Card Read state
table.
Screen number
Entry number: 2
Valid range: 000-999
Description: 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: 000-254, 256-999
Description: The number of the state the terminal enters after the customer’s
card is read properly. Normally the next state is a PIN entry
state type.
Error (misread) screen number

Entry number: 4
Description: 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

Read condition 1
Entry number: 5
Description: 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
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
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
Card return flag

Entry number: 8
Description: 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

No FIT match next state number

Entry number: 9
Valid range: 000-254, 256-999
Description: 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 Card read table Card read table
Entry 5 (read Entry 6 (read Entry 7 (read
condition 1) condition 2) condition 3)
1 only 004 004 004
2 only 002 002 002
3 only 001 001 001
1 and 2 006 006 006
1 and 3 005 005 005
2 and 3 003 003 003
1 and 2 and 3 007 007 007
2 or 3 002 001 001
1 or 3 004 001 001
1 or 2 004 002 002
1 or2or3 004 002 001
(1 and 2) or (1 and 3) 006 005 005
(2 and 1) or (2 and 3) 006 003 003
(3 and 1) or (3 and 2) 005 003 003
1 or (2 and 3) 004 003 003
2 or (1 and 3) 002 005 005
3 or (1 and 2) 001 006 006
Chip connect only 008 008 008
3 and chip connect 009 009 009
2, 3 and chip connect 011 011 011
1, 2, 3 and chip connect 015 015 015
62 October 2004 U25604-J-Z745-1-7600

Short desciption to Table 8:

If read condition 1 is satisfied, the good read next state number entry (table entry 3)
is taken. Otherwise, read condition 2 is attempted.
is taken. Otherwise, read condition 3 is attempted.
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

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 Definition
1 state type
2 screen number
3 time-out next state number
4 cancel next state number
5 local PIN check, correct PIN next state number
6 local PIN check, maximum bad PIN’s next state number
7 local PIN check, error screen number
8 remote PIN check, next state number
9 local PIN check, maximum PIN attempts
The PIN Entry (B) state entries are defined as follows:
State type
Entry number: 1
Valid range: B
Description: This state ID identifies this state table as a PIN Entry state table.
64 October 2004 U25604-J-Z745-1-7600

Screen number
Entry number: 2
Description: 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: 000-254, 256-999
Description: 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: 000-254, 256-999
Description: 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: 000-254, 256-999
Description: 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

Local PIN check, maximum bad PIN’s 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
Description: 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: 000-254, 256-999
Description: 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
Description: 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

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 PIN’s have been built
into the PIN blocks for transmitting. If checking is enabled and the two PIN’s
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 PIN’s 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 Definition
1 state type
2 first entry screen number
5 good next state number
6 CSP fail next state number
7 second entry screen number
8 mismatch first entry screen number
9 extension state number
U25604-J-Z745-1-7600 October 2004 67

The Customer Selectable PIN (b) state entries are defined as follows:
State type
Entry number: 1
Valid range: b
Description: This state ID identifies this state table is a Customer Selectable
PIN state table.
First entry screen number

Entry number: 2
Description: Display screen that prompts the cardholder to enter the PIN the
first time.

Entry number: 3
Valid range: 000-254, 256-999
Description: 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.

Entry number: 4
Valid range: 000-254, 256-999
Description: 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: 000-254, 256-999
Description: 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

CSP fail next state number

Entry number: 6
Valid range: 000-254, 256-999
Description: 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
Description: Display screen used to ask for confirmation of the CSP.
Mismatch first entry screen number

Entry number: 8
Description: 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: 000-254, 256-999
Description: State number of the extension state.
U25604-J-Z745-1-7600 October 2004 69

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 Definition
1 state type
2 number of attempts allowed to enter a matching CSP pair
3 use local verification of new PIN pair attempts
4-9 reserved, must be ’000’
The Extension state entries are defined as follows:
State type
Entry number: 1
Valid range: Z
Description: 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
Description: 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
Description: 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

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 Definition
1 state type
2 next state number
3-9 reserved, must be ’000’
The Envelope Deposit (C) state entries are defined as follows:
State type
Entry number: 1
Valid range: C
Description: This state ID identifies this state table as an Envelope Deposit
state.
Next state number

Entry number: 2
Description: The number of the state to which the terminal proceeds after
entering state C.
U25604-J-Z745-1-7600 October 2004 71

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:
● 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 Definition
1 state type
2 next state number
3 clear mask
4 A preset mask
5 B preset mask
6 C preset mask
7 D preset mask
8 reserved
The Pre-Set Operation Code Buffer (D) state entries are defined as follows:
State type
Entry number: 1
Valid range: D
Description: This state ID identifies this state table as a Pre-Set Operation
Code Buffer state table.
72 October 2004 U25604-J-Z745-1-7600

Next state number

Entry number: 2
Valid range: 000-254, 256-999
Description: The number of the state to which the terminal proceeds after
clearing or presetting the operation code buffer.
Clear mask
Entry number: 3
Description: 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
Description: 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
Description: 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

C Preset mask
Entry number: 6
Description: Specifies bytes of operation code buffer to be set to C. Each bit
(one), the corresponding entry is set to C. If a bit is disabled
D Preset mask
Entry number: 7
Description: Specifies bytes of operation code buffer to be set to D. Each bit
(one), the corresponding entry is set to D. If a bit is disabled
Reserved
Entry number: 8
Valid range: 000
Description: Entry 8 is reserved and must be 000.
Extension State number

Entry number: 9
Valid range: 000-254 or 256-999
Description: State number of the extension state containing information on
how the other operation codes are preset.
74 October 2004 U25604-J-Z745-1-7600

Clear mask (entry 3) example
Start with an operation code buffer that looks like the following:
Buffer B _ _ C _ _ D _
Bit Pos 0 1 2 3 4 5 6 7
Weight 1 2 4 8 16 32 64 128
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 B _ _ C _ _ D _
Bit pos 0 1 2 3 4 5 6 7
Positions not cleared X X X X X X X
Weights not cleared 1 + 2 + 4 + 8 + 16 + 32 + 128 = 191
With 191 entered in entry 3, the resultant operation code buffer would appear
as follows:
Buffer B _ _ C _ _ _ _
Bit pos 0 1 2 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:
● 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 A B A C D B _ D
Bit pos 0 1 2 3 4 5 6 7
Weight 1 2 4 8 16 32 64 128
The entries would have to be set as follows:
● entry 4 (A preset mask) - 1+4 = 005
● entry 5 (B preset mask) - 2 + 32 = 034
● entry 6 (C preset mask) - 8 = 008
● entry 7 (D preset mask) - 16 + 128 = 144
U25604-J-Z745-1-7600 October 2004 75

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 Definition
1 state type
2 F preset mask
3 G preset mask
4 H preset mask
5 I preset mask
6-9 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: Z
Description: This state ID identifies this state table as an Pre-Set Operation
Code Buffer Extension state.
F Preset mask
Entry number: 2
Description: Specifies bytes of operation code buffer to be set to F. Each bit
(one), the corresponding entry is set to F. If a bit is disabled
76 October 2004 U25604-J-Z745-1-7600

G Preset mask
Entry number: 3
Description: Specifies bytes of operation code buffer to be set to G. Each bit

(one), the corresponding entry is set to G. If a bit is disabled
H Preset mask
Entry number: 4
Description: Specifies bytes of operation code buffer to be set to H. Each bit
(one), the corresponding entry is set to H. If a bit is disabled
I Preset mask
Entry number: 5
Description: Specifies bytes of operation code buffer to be set to I. Each bit
(one), the corresponding entry is set to I. If a bit is disabled
U25604-J-Z745-1-7600 October 2004 77

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 Definition
1 state type
2 screen number
5 operation key A next state number
6 operation key B next state number
7 operation key C next state number
8 operation key D next state number
9 operation code buffer location
The Four FDK Selection Function (E) state entries are defined as follows:
State type
Entry number: 1
Valid range: E
Description: This state ID identifies this state table as a Function Selection
state table.
78 October 2004 U25604-J-Z745-1-7600

Screen number
Entry number: 2
Description: 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.

Entry number: 3
Valid range: 000-254, 256-999
Description: 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).

Entry number: 4
Valid range: 000-254, 256-999
customer presses the cancel key instead of an operation key.
Operation key A next state number

Entry number: 5
Valid range: 000-254, 256-999
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: 000-254, 256-999
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

Operation key C next state number

Entry number: 7
Valid range: 000-254, 256-999
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
customer presses the D operation key (specify "255" to
deactivate the D operation key during this state).
Operation code buffer location

Entry number: 9
Description: 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 position 0 Buffer positions are as follows:
001 = buffer position 1
002 = buffer position 2 ________
003 = buffer position 3 01234567
80 October 2004 U25604-J-Z745-1-7600

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 Definition
1 state type
2 screen number
9 display amount screen number
The Amount Entry (F) state entries are defined as follows:
State type
Entry number: 1
Valid range: F
Description: This state ID identifies this state table as an Amount Entry state
table.
Screen number
Entry number: 2
Description: 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


Entry number: 3
Valid range: 000-254, 256-999
customer fails to enter the amount within the specified time limit
(specify "255" if the time-out function is not used).

Entry number: 4
Valid range: 000-254, 256-999
customer presses the cancel key before pressing an operation
key. Value "255" deactivates the CANCEL key during this state.

Entry number: 5
Valid range: 000-254, 256-999
customer presses the A operation key. Value "255" deactivates
the A operation key during this state.

Entry number: 6
Valid range: 000-254, 256-999
customer presses the B operation key. Value "255" deactivates
the B operation key during this state.

Entry number: 7
Valid range: 000-254, 256-999
customer presses the C operation key. Value "255" deactivates
the C operation key during this state.
82 October 2004 U25604-J-Z745-1-7600


Entry number: 8
Valid range: 000-254, 256-999
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
Description: 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 left-
hand 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

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 Definition
1 state type
2 whole amount entry next state number
3 non-whole amount entry next state number
4 buffer to be checked
5 zero entry next state number (if table entry 8 is zero) or
integer multiple value (if table entry 8 is non zero)
6 number of decimal places
7 currency type
8 amount check condition
9 reserved must be zero
The Amount Check (G) state entries are defined as follows:
State type
Entry number: 1
Valid range: G
Description: This state ID identifies this state table as a amount check state
table.
84 October 2004 U25604-J-Z745-1-7600

Whole amount entry next state number

Entry number: 2
Description: 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
Description: 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
Description: 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
Description: 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

Number of decimal places

Entry number: 6
Description: 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
Description: 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
Description: 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: 000
86 October 2004 U25604-J-Z745-1-7600

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 Definition
1 state type
2 screen number
9 buffer and display parameters
The Information Entry (H) state entries are defined as follows:
State type
Entry number: 1
Valid range: H
Description: This state ID identifies this state table as an information entry
state table.
U25604-J-Z745-1-7600 October 2004 87

Screen number
Entry number: 2
Description: 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.

Entry number: 3
Valid range: 000-254, 256-999
customer fails to respond to the CRT message within a
specified time limit. Value "255" disables the time-out function.

Entry number: 4
Valid range: 000-254, 256-999
customer presses the cancel key before pressing an operation
key.

Entry number: 5
Valid range: 000-254, 256-999

Entry number: 6
Valid range: 000-254, 256-999
customer presses the B operation key. Value "255’ deactivates
88 October 2004 U25604-J-Z745-1-7600


Entry number: 7
Valid range: 000-254, 256-999

Entry number: 8
Valid range: 000-254, 256-999
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 = display X for each numeric key pressed; store keys
in general purpose buffer C (max. 32 digits).
xx1 = display data as entered; store keys in general
purpose buffer C (max. 32 digits).
xx2 = display X for each numeric key pressed; store keys
in general purpose buffer B (max. 32 digits).
xx3 = 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

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 Definition
1 state type
2 screen number
3 network response time out next state number
4 send track 2 data
5 send track 1, track 3
6 send operation code buffer
7 send amount buffer
8 send PIN buffer (Buffer A) data / Select Extended format
9 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: I
Description: This state ID identifies this state table as a transaction request
state table.
90 October 2004 U25604-J-Z745-1-7600

Screen number
Entry number: 2
Description: 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: 000-254, 256-999
Description: 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
Description: 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
Description: The track 1, 3 data entry specifies whether track 1 and/or track
3 data is sent to the network.
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

Send operation key data

Entry number: 6
Description: This field indicates whether the operation key data should be
sent in the transaction request message.
001 - send data
Send amount buffer data

Entry number: 7
Description: This field indicates whether the amount buffer data should be
sent in the transaction request message.
001 - send data
Send PIN buffer data

Entry number: 8
Valid range: 000-001, 128
Description: 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:
001 - send data
128 - use extension state specified in table entry 9
92 October 2004 U25604-J-Z745-1-7600

Send general purpose buffers B and/or C data

Entry number: 9
Valid range: 000-003, Extension state range: 000-254, 256-999
Description: 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.
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 Definition
1 state type
2 send general purpose buffers B and/or C
3 send optional date fields ’A’ - ’H’
4 send optional data fields ’I’ - ’L’
5 send optional data fields ’Q’ - ’V’
6-9 reserved
State type
Entry number: 1
Valid range: Z
Description: This state ID identifies this state table as an Extension state
table.
U25604-J-Z745-1-7600 October 2004 93

Send general purpose buffers B and/or C data

Entry number: 2
Description: This field indicates whether the data from the general purpose
buffers B and/or C should be sent in the transaction request
message.
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
Description: 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 Field ID
1 ’A’ reserved
2 ’B’ reserved
3 ’C’
4 ’D’
5 ’E’
6 ’F’
7 ’G’
8 ’H’
94 October 2004 U25604-J-Z745-1-7600

Optional data fields ’I’ - ’L’

Entry number: 4
Description: This entry is as for entry 3 but with following values:
BIT Field ID
1 ’I’
2 ’J’
3 ’K’
4 ’L’
5 ’M’ reserved
6 ’N’ reserved
7 ’O’ reserved
8 ’P’ reserved
Optional data fields ’Q’ - ’V’

Entry number: 5
Description: This entry is as for entry 3 but with following values:
BIT Field ID
1 ’Q’
2 ’R’
3 ’S’
4 ’T’ reserved
5 ’U’
6 ’V’
7 reserved
8 reserved
U25604-J-Z745-1-7600 October 2004 95

Close State (J)
The Close state should terminate the customer’s current terminal interface. This
state performs the following functions:
● 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 Definition
1 state type
2 transaction record form delivered screen number
3 next state number
4 no transaction record form delivered screen number
5 card retained screen number
6 Statement delivered screen
7 reserved
8-9 not used
The Close (J) state entries are defined as follows:
State type
Entry number: 1
Valid range: J
Description: This state ID identifies this state table as a Close state table.
96 October 2004 U25604-J-Z745-1-7600

Transaction record form delivered screen number

Entry number: 2
Description: 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

customer’s card is returned and a transaction record form was
printed.
Next state number

Entry number: 3
Valid range: 000-254, 256-999
Description: The state number to which the terminal proceeds after the close
state is completed.
No transaction record form delivered screen number

Entry number: 4
Description: 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 customer’s card is returned and no
transaction record form was printed.
Card retained screen number

Entry number: 5
Description: 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 customer’s card has been retained by
the terminal as instructed by the network. If the customer times-
out, this screen is not displayed.
U25604-J-Z745-1-7600 October 2004 97

Statement delivered screen

Entry number: 6
Description: 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: 000
Not used
Entry number: 8-9
Valid range:
Description: Entries 8 and 9 are not used by ProCash/NDC or
ProConsult/NDC.
98 October 2004 U25604-J-Z745-1-7600

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 Definition
1 state type
2-9 next state number
The FIT Switch (K) state entries are defined as follows:
State type
Entry number: 1
Valid range: K
Description: This state ID identifies this state table as an FIT Switch state
table.
U25604-J-Z745-1-7600 October 2004 99

Next state number

Entry number: 2-9
Valid range: 000-254, 256-999
Description: 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 Description
2 next state number if PSTDX = 0
100 October 2004 U25604-J-Z745-1-7600

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 terminal‘s 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:
● 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.
U25604-J-Z745-1-7600 October 2004 101

Table 23: Card Write state entries
Entry Definition
1 state type
2 screen number
3 good write next state
4 bad write next state
5 no write attempted
6 reserved
7 reserved
8 reserved
9 reserved
The Card Write state entries are defined as follows:
State type
Entry number: 1
Valid range: L
Description: This state ID identifies this state table as the Card Write state.
Screen number
Entry number: 2
Description: Screen displayed during card write operation.
Good Write next state

Entry number: 3
Valid range: 000-254, 256-999
Description: State number goes to after a satisfactory track write operation.
102 October 2004 U25604-J-Z745-1-7600

Bad Write next state

Entry number: 4
Valid range: 000-254, 256-999
Description: State number goes to if the track write is unsuccessful.
No Write attempted
Entry number: 5
Valid range: 000-254, 256-999
Description: 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: 000
Description: Must be 000 for each table entry.
U25604-J-Z745-1-7600 October 2004 103

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 PIN’s 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 Definition
1 state type
2 screen number
5 local PIN check, correct PIN next state number
6 local PIN check, maximum bad PIN’s next state number
7 local PIN check, error screen number
8 remote PIN check, next state number
9 local PIN check, maximum PIN attempts
104 October 2004 U25604-J-Z745-1-7600

The Enhanced PIN Entry (M) state entries are defined as follows:
State type
Entry number: 1
Valid range: M
Description: This state ID identifies this state table as an Enhanced PIN

Entry state table.
Screen number
Entry number: 2
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.

Entry number: 3
Valid range: 000-254, 256-999
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.

Entry number: 4
Valid range: 000-254, 256-999
the customer presses the cancel key.
U25604-J-Z745-1-7600 October 2004 105

Local PIN check, good PIN next state number

Entry number: 5
Valid range: 000-254, 256-999
Description: 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 PIN’s 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
Description: 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: 000-254, 256-999
Description: 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

Local PIN check, maximum PIN attempts

Entry number: 9
Description: 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 Definition
1 state type
2 screen number
U25604-J-Z745-1-7600 October 2004 107

The Enhanced Amount Entry (R) state entries are defined as follows:
State type
Entry number: 1
Valid range: R
Description: This state ID identifies this state table as an Enhanced Amount
Entry state table.
Screen number
Entry number: 2
consumer to enter an amount.

Entry number: 3
Valid range: 000-254, 256-999
consumer fails to enter the amount within the specified time
limit. Enter 255 if the time-out function is not required.

Entry number: 4
Valid range: 000-254, 256-999
the consumer presses the Cancel key.

Entry number: 5
Valid range: 000-254, 256-999
108 October 2004 U25604-J-Z745-1-7600


Entry number: 6
Valid range: 000-254, 256-999
customer presses the B operation key. Value "255" deactivates

Entry number: 7
Valid range: 000-254, 256-999

Entry number: 8
Valid range: 000-254, 256-999
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.

Entry number: 9
Valid range: 000-254; 256-999
Description: State number of the extension state.
U25604-J-Z745-1-7600 October 2004 109

Extension to State (R)
This state is the Extension state for the Enhanced Amount Entry state (R).
Entry Definition
1 state type
2 document amount buffer
3 display amount screen number
4 start CAV command
5-9 reserved
The Extension State entries are defined as follows:
State type
Entry number: 1
Valid range: Z
Description: This state ID identifies this state table as the Extension state to
the Enhanced Amount Entry state table.
Document amount buffer

Entry number: 2
Description: 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

Display amount screen number

Entry number: 3
Description: 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 left-

hand 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
Description: 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

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 Definition
1 state type
2 no language code, next state no.
3 language code = 0, next state
112 October 2004 U25604-J-Z745-1-7600

The Language Code Switch state entries are defined as follows:
State type
Entry number: 1
Valid range: S
Description: 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: 000-254, 256-999
Description: 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: 000-254, 256-999
Description: State number the terminal goes to, if the language code is 0.

Entry number: 4
Valid range: 000-254, 256-999

Entry number: 5
Valid range: 000-254, 256-999

Entry number: 6
Valid range: 000-254, 256-999
U25604-J-Z745-1-7600 October 2004 113


Entry number: 7
Valid range: 000-254, 256-999

Entry number: 8
Valid range: 000-254, 256-999

Entry number: 9
Description: 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 Definition
1 state type
6 reserved
7 reserved
8 reserved
9 reserved
114 October 2004 U25604-J-Z745-1-7600

The Extension state entries of the Language Code Switch state are defined as
follows:
State type
Entry number: 1
Valid range: Z
the Language Code Switch state.

Entry number: 2
Valid range: 000-254, 256-999

Entry number: 3
Valid range: 000-254, 256-999

Entry number: 4
Valid range: 000-254, 256-999

Entry number: 5
Valid range: 000-254, 256-999
Reserved
Entry number: 6-9
Valid range: 000
Description: Must be 000.
U25604-J-Z745-1-7600 October 2004 115

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 Definition
1 state type
2 screen number
3 good read next state number
5 read condition 1
6 read condition 2
7 read condition 3
8 reserved
The Card Read - PIN Entry Initiation (T) state entries are defined as follows:
State type
Entry number: 1
Valid range: T
Description: 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

Screen number
Entry number: 2
Description: 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.

Entry number: 3
Valid range: 000-254, 256-999
Description: The state number the terminal enters after the customer’s card
is read properly:
Following a good read of the card if FIT’s 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.

Entry number: 4
Description: 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
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
U25604-J-Z745-1-7600 October 2004 117

Read condition 2
Entry number: 6
Description: 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
Description: 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
Description: 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.

Entry number: 9
Valid range: 000-254, 256-999
Description: State number of the extension state containing information for
parallel PIN entry.
118 October 2004 U25604-J-Z745-1-7600

Extension to State (T)
This state is the Extension state to the card read state (T).
Entry Definition
1 state type
2 screen number
3 no fit match next state number
4 clear key mask (not supported)
5 accept key mask (not supported)
6 reserved, must be 000
The card read extension state entries are defined as follows:
State type
Entry number: 1
Valid range: Z
Description: This state ID identifies this state table as the extension state to
the card read state (T).
Screen number
Entry number: 2
Description: 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

No FIT match Next state number

Entry number: 3
Valid range: 000-254, 256-999
Description: State number terminal goes to if the financial institution number
on the card does not match any FIT. If FIT’s 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 cardholder’s 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 Definition
1 state type
2 next state number
3 language code for group 1
9 screen group size (range 000-400)
120 October 2004 U25604-J-Z745-1-7600

The Language Select From Card (V) state entries are defined as follows:
State type
Entry number: 1
Valid range: V
Description: This state ID identifies this state table as a Language Select

From Card state table.
Next state number

Entry number: 2
Valid range: 0-9
Description: State number terminal goes to after selecting the screen group.
Language Code
Entry number: 3
Valid range: 0-9
Description: Decimal number in range 0-9 identifying code for screen group
1.
Language Code
Entry number: 4
Valid range: 0-9
2.
Language Code
Entry number: 5
Valid range: 0-9
3.
U25604-J-Z745-1-7600 October 2004 121

Language Code
Entry number: 6
Valid range: 0-9
4.
Language Code
Entry number: 7
Valid range: 0-9
5.
Code
Entry number: 8
Valid range: 0-9
6.
Screen Group Size

Entry number: 9
Description: State number of the extension state containing information for
parallel PIN entry.
122 October 2004 U25604-J-Z745-1-7600

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 Definition
1 state type
2 FDK A next state no.
3 FDK B next state no.
4 FDK C next state no.
5 FDK D next state no.
6 FDK F next state no.
7 FDK G next state no.
8 FDK H next state no.
9 FDK I next state no.
The FDK Switch (W) state entries are defined as follows:
State type
Entry number: 1
Valid range: W
Description: This state ID identifies this state table as a FDK Switch state
table.
FDK A Next state No.

Entry number: 2
Valid range: 000-254, 256-999
Description: State number terminal goes to depending on key code stored in
FDK buffer.
U25604-J-Z745-1-7600 October 2004 123

FDK B Next state No.

Entry number: 3
Valid range: 000-254, 256-999
FDK buffer.
FDK C Next state No.

Entry number: 4
Valid range: 000-254, 256-999
FDK buffer.
FDK D Next state No.

Entry number: 5
Valid range: 000-254, 256-999
FDK buffer.
FDK F Next state No.

Entry number: 6
Valid range: 000-254, 256-999
FDK buffer.
FDK G Next state No.

Entry number: 7
Valid range: 000-254, 256-999
FDK buffer.
124 October 2004 U25604-J-Z745-1-7600

FDK H Next state No.

Entry number: 8
Valid range: 000-254, 256-999
FDK buffer.
FDK I Next state No.

Entry number: 9
Valid range: 000-254, 256-999
FDK buffer.
U25604-J-Z745-1-7600 October 2004 125

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 FDK’s.
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 Definition
1 state type
2 screen number
3 time-out next state number.
5 FDK next state number
7 buffer ID
8 FDK’s active mask
9 reserved
The FDK Information Entry (X) state entries are defined as follows:
State type
Entry number: 1
Valid range: X
Description: This state ID identifies this state table as the FDK Information
Entry state.
126 October 2004 U25604-J-Z745-1-7600

Screen number
Entry number: 2
Description: Display screen that prompts key selection by the consumer.
Time-out Next state number

Entry number: 3
Valid range: 000-254, 256-999
Description: State number the terminal goes to if the consumer fails to
respond to the message on screen within the permitted time
Cancel Next state number

Entry number: 4
Valid range: 000-254, 256-999
Description: State number the terminal goes to if the cancel key is pressed.
FDK Next state

Entry number: 5
Valid range: 000-254, 256-999
Description: State number the terminal goes to if an FDK is pressed.
Extension State Number

Entry number: 6
Valid range: 000-254, 256-999
Description: State number of the extension state containing assigned values
for the 8 FDK’s.
U25604-J-Z745-1-7600 October 2004 127

Buffer ID
Entry number: 7
Description: 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
Description: Specifies the FDK’s 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 b6 b5 b4 b3 b2 b1 b0
0 1 0 1 1 1 0 1
the three decimal characters in table entry 8 are 093 and the
active FDK’s are A, C, D, F and H.
Reserved
Entry number: 9
Valid range: 000
Description: Must be 000.
128 October 2004 U25604-J-Z745-1-7600

Extension to State (X)
This state is the Extension state to the FDK Information Entry state (X).
Entry Definition
1 state type
2 value stored if FDK A is pressed
3 value stored if FDK B is pressed
4 value stored if FDK C is pressed
5 value stored if FDK D is pressed
6 value stored if FDK F is pressed
7 value stored if FDK G is pressed
8 value stored if FDK H is pressed
9 value stored if FDK I is pressed
State type
Entry number: 1
Valid range: Z
the FDK Information Entry state.
Value stored if FDK A is pressed

Entry number: 2
Description: 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

Value stored if FDK B is pressed

Entry number: 3
is pressed.
Value stored if FDK C is pressed

Entry number: 4
is pressed.
Value stored if FDK D is pressed

Entry number: 5
is pressed.
Value stored if FDK F is pressed

Entry number: 6
FDk Information Entry state (table entry 7) if the specified FDK
is pressed.
Value stored if FDK G is pressed

Entry number: 7
is pressed.
130 October 2004 U25604-J-Z745-1-7600

Value stored if FDK H is pressed

Entry number: 8
is pressed.
Value stored if FDK I is pressed

Entry number: 9
is pressed.
U25604-J-Z745-1-7600 October 2004 131

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 Definition
1 state type
2 screen number
5 FDK next state number
7 buffer positions
8 FDK’s active mask
9 multi language extension state number
The Eight FDK Selection state (Y) state entries are defined as follows:
State type
Entry number: 1
Valid range: Y
Description: The state type entry identifies this state table as the Eight FDK
Selection state table.
132 October 2004 U25604-J-Z745-1-7600

Screen number
Entry number: 2
Description: Display screen which prompts key selection by the cardholder.

Entry number: 3
Valid range: 000-254, 256-999
Description: State number the terminal goes to if the cardholder does not
respond to the message on screen within the specified time

Entry number: 4
Valid range: 000-254, 256-999
Description: State number the terminal goes to if the cardholder presses the
cancel key.
FDK next state number

Entry number: 5
Valid range: 000-254, 256-999
Description: State number the terminal goes to if the cardholder presses an
FDK.

Entry number: 6
Valid range: 000-254, 256-999
Description: State number of extension state containing assigned operation
codes for the 8 FDK’s. If there is no extension state enter 255.
U25604-J-Z745-1-7600 October 2004 133

Buffer positions
Entry number: 7
Description: 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.
FDK’s active Mask

Entry number: 8
Description: Specifies the FDK’s 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 b5 b4 b3 b2 b1 b0
1 0 1 1 0 1 1 1
Multi language Extension state number

Entry number: 9
Valid range: 000-254, 256-999
Description: 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

Extension to State (Y)
This state is the Extension state to the Eight FDK Selection state (Y).
Entry Definition
1 state type
2 operation code stored if FDK A pressed
3 operation code stored if FDK B pressed
4 operation code stored if FDK C pressed
5 operation code stored if FDK D pressed
6 operation code stored if FDK F pressed
7 operation code stored if FDK G pressed
8 operation code stored if FDK H pressed
9 operation code stored if FDK I pressed
State type
Entry number: 1
Valid range: Z
Description: Identifies this state table as the Extension state for the Eight
FDK Selection state table.
U25604-J-Z745-1-7600 October 2004 135

Operation Code stored if FDK pressed

Entry number: 2-9
Valid range: ‘A’ - ‘I’, ’@’ or 1 - 9, 0
Description: 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 Definition
1 state type
2 screen language offset if FDK A is pressed
3 screen language offset if FDK B is pressed
4 screen language offset if FDK C is pressed
5 screen language offset if FDK D is pressed
6 screen language offset if FDK F is pressed
7 screen language offset if FDK G is pressed
8 screen language offset if FDK H is pressed
9 screen language offset if FDK I is pressed
136 October 2004 U25604-J-Z745-1-7600

The Multi Language Extension state entries are defined as follows:
State type
Entry number: 1
Valid range: Z
Description: 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
Description: 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

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:
● 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

Table 38: Audio Control state entries
Entry Definition
1 state type
2 Prompt screen
3 Timeout next state
4 Function complete next state

5 Increase Volume FDK mask
6 Decrease Volume FDK mask
7 Audio control
8 Audio message
9 Reserved
The Audio Control (‘i’) state entries are defined as follows:
State type
Entry number: 1
Valid range: ’i’
Description: This state ID identifies this state table as an Audio Control state.
Prompt screen
Entry number: 2
Description: 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: 000-254; 256-999
Description: 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

Function complete next state

Entry number: 4
Valid range: 000-254; 256-999
Description: 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
Description: 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
Description: 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

Audio control
Entry number: 7
Description: This entry is bitmapped:
Bit Definition
0 0 - volume adjust off
1 - volume adjust on
1 0 - disables effect of bits 2 and 3
1 - enables effect of bits 2 and 3
2 0 - disables loudspeaker (left channel)
1 - enables loudspeaker (left channel)
3 0 - disables audio jack (right channel)
1 - enables audio jack (right channel)
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: 000 or 999
Description: 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

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 Definition
1 state type
2 no error next state
3 next state if reboot requested (defined in CCERRMAP)
4 next state if CDM fatal error
5 next state if journal fatal error
6 next state if receipt fatal error
7 next state if deposit fatal error
8 reserved for future use
The Hardware Fitness (‘h’) state entries are defined as follows:
State type
Entry number: 1
Valid range: ‘h’
Description: This state ID identifies this state table as a Hardware Fitness
state.
142 October 2004 U25604-J-Z745-1-7600

No error next state

Entry number: 2
Description: 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
Description: 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
cash dispenser is fatal.
Next state if Journal fatal error

Entry number: 5
journal printer is fatal.
Next state if Receipt fatal error

Entry number: 6
receipt printer is fatal.
U25604-J-Z745-1-7600 October 2004 143

Next state if Deposit fatal error

Entry number: 7
deposit module is fatal.
Reserved for future use

Entry number: 8
Description: Entry 8 is reserved and must be 000 or 255.

Entry number: 9
Description: State number of the extension state (Z) containing additional
device conditions.
144 October 2004 U25604-J-Z745-1-7600

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 Definition
1 state type
2 denomination type
3 next state if denomination not available
4 next state if journal warning
5 next state if receipt warning
6 next state if deposit warning
The Hardware Fitness Extension (Z) state entries are defined as follows:
State type
Entry number: 1
Valid range: Z
Description: This state ID identifies this state table as a Hardware Fitness
Extension state.
U25604-J-Z745-1-7600 October 2004 145

Denomination Type
Entry number: 2
Description: The data field is divided in three digits:
First digit: Reserved, always zero.

Second Specifies the denomination type of cash cassettes which should
digit: 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
Description: The number of state to which the terminal proceeds if the
Denomination is not available.
Next state if Journal warning

Entry number: 4
journal printer has a warning status.
Next state if Receipt warning

Entry number: 5
receipt printer has a warning status.
146 October 2004 U25604-J-Z745-1-7600

Next state if Deposit warning

Entry number: 6
deposit module has a warning status.
Reserved
Entry number: 7-9
Description: Entries 6-9 are reserved and must be 000 or 255.
U25604-J-Z745-1-7600 October 2004 147

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 Definition
1 state type
2 reserved
3 good read next state number
5 read Condition 1
6 read Condition 2
7 read Condition 3
8 card return flag
9 no FIT match next state
The Smart FIT Check (’k’) state entries are defined as follows:
State type
Entry number: 1
Valid range: ’k’
Description: This state ID identifies this state table as a Smart FIT Check
state.
148 October 2004 U25604-J-Z745-1-7600

Reserved
Entry number: 2
Valid range: 0
Description: 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.

Entry number: 3
Description: State number to which the terminal goes if the Financial
Institution number on the card matches a Financial Institution
number in the FIT.

Entry number: 4
Description: 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: see description
Description: First of three entries indicating which card track buffer(s) will be
read.
Bit Description
0 Read track 3
1 Read track 2
2 Read track 1
3-7 Reserved
U25604-J-Z745-1-7600 October 2004 149

Read condition 2
Entry number: 6
Description: Second of three entries indicating which card track buffer(s) will
be read.
Bit Description
0 Read track 3
1 Read track 2
2 Read track 1
3-7 Reserved
Read condition 3
Entry number: 7
Description: Third of three entries indicating which card track buffer(s) will be
read.
Bit Description
0 Read track 3
1 Read track 2
2 Read track 1
3-7 Reserved
Card return flag

Entry number: 8
Description: 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.
150 October 2004 U25604-J-Z745-1-7600

No FIT match next state number

Entry number: 9
Description: 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

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 Definition

DC_NEXT_1 uses field 1 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:
● 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 Configuration Data
Screen delimiters
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 ASCII HEX Equivalent EBCDIC HEX Equivalent

CR 0D 0D
FF 0C 0C
HT 09 05
SI 0F 0F
SO 0E 0E
VT 0B 0B
Table 44: Screen control characters
Control Description
Code
CR moves the cursor to the first position in the current row
FF clears the screen and positions the cursor to position @,@ on
the display grid
HT causes the customer’s name, encoded on track 1 of the
customer’s card, to be shown on the customer display, starting
at the current customer display cursor position
SI 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.
SO 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.
VT shows an alternate character on the customer display. the
alternate character is specified by the byte following VT
154 October 2004 U25604-J-Z745-1-7600

CR control character
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 customer’s
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

SO control character
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:
● 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

Table 45: Screen escape sequences cross-reference
Escape Sequence ASCII HEX Equivalent EBCDIC HEX Equivalent

ESC P 1B 50 27 D7
ESC [ 1B 5B 27 63
ESC ( 1B 28 27 4D
ESC ) 1B 29 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

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 animation’s 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, PCX’s, BMP’s with/without overlaid text.
Display resolutions
ProCash/NDC and ProConsult/NDC support following display resolutions and
color depths:
Mode Resolution color depths [1]

VGA 640x480 16
SVGA 640x480 256, 65535 (16 bit)
SVGA 800x600 256, 65535 (16 bit)
SVGA 1024x768 256, 65535 (16 bit)
[1] - PCX graphics are supported in 16 or 256 colors only.
158 October 2004 U25604-J-Z745-1-7600

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
doesn’t 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

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.
● 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 Trans-
action 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 Message Message

(*.WAV) file Number
1.WAV 1 “your transaction is being processed”
7.WAV 7 “please enter your personal identification number”
8.WAV 8 “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

Audible Echo on Keyboard
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 Phrase

ZERO.WAV “zero”
ONE.WAV “one”
TWO.WAV “two”
THREE.WAV “three”
FOUR.WAV “four”
FIVE.WAV “five”
SIX.WAV “six”
SEVEN.WAV “seven”
EIGHT.WAV “eight”
NINE.WAV “nine”
NOTE: The WAVE files are recorded as female voice
U25604-J-Z745-1-7600 October 2004 161

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 Function
No.
C00 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.
C01 Offline screen; This screen appears on the customer display
when the terminal is offline. The screen’s characters default to
offline at terminal power up or reset.
C02 Out of Service screen; This screen appears on the customer
display when the terminal is in out-of-service mode. The screen’s
characters default to out-of-service at terminal power-up or reset.
C03 Supply screen. This screen is displayed while the terminal is in
supervisor mode.
C04 Card capture screen; This screen is displayed when the terminal
captures a card as a result of a card reader failure
C05 Cardholder tampering screen; This screen is displayed when
cardholder tampering is suspected and the terminal enters
suspend mode.
C06 Temporarily Out of Service screen
162 October 2004 U25604-J-Z745-1-7600

General use of default reserved C 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 Downloaded screen

C00 000
C01 001
C02 002
C03 003
C04 none
C05 C02 / 002
C06 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 configu-
ration 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:
● 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 time-
out 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

Screen C02
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:
● 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

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

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:
● 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 Miscellaneous 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, speci-

fying 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
Timer Default value in PPF Timer Default value in PPF

number (seconds / ticks) number (seconds / ticks)
00 030 / 038 86 018 / 023 (not used)
01 015 / 019 87 030 / 038 (not used)
02 005 / 006 94 030 / 038 (not used)
03 030 / 038 95 030 / 038
04 040 / 050 96 000 / 000
05 040 / 050 97 010 / 013 (not used)
06 030 / 038 98 030 / 038 (not used)
07 001 / 001 99 030 / 038
08 040 / 050
09 020 / 025
10 001 / 001
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.
168 October 2004 U25604-J-Z745-1-7600

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 customer’s 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

● 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.
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

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

Timer 15
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
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:

● 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 Directory Called when

dcCfgId.cmd C:\PROTOPAS\CONF after Config ID received
dcInServ.cmd C:\PROTOPAS\CONF 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

Local download feature 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
Data The Data Encryption Standard (DES) specifies an algorithm
Encryption to be used in electronic hardware devices for the purpose of
Standard cryptographic protection of computer data.
[DES]
Encryption Encryption keys are numbers that are used as part of the PIN
keys 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.
Personal The Personal Identification Number (PIN) is the customer’s
Identification way of verifying his or her identity as established by an
Number [PIN] activator card. By entering this PIN, the customer is identified
and can access the relevant accounts.
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 The Financial Institution Table (FIT) provides the following

Institution items to the network:
Table [FIT]
– capacity of using multiple card formats and multiple insti-
tutions
– 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 institu-
tions to define the exact operation flow of the terminal.
This is done by supplying state flow through the FIT.
Message Message Authentication Code (MAC) provides a method of
Authentication ensuring that messages sent between the terminal and the
Code network are authentic and have not been modified.
[MAC]
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)
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 customer’s PIN also verifies that PIN.
A particular key and a set of PAN’s correspond to a set of PIN’s. Some of the
PIN’s may be duplicated; that is, one PIN may be derived from several PAN’s,
but any given PAN has only one possible PIN.
PIN Entry
The first step in the PIN verification process is the customer’s 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

Personal Identification Number (PIN) 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 PIN’s shorter than the maximum PIN length defined in
a FIT. Customers receiving shorter PIN’s 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 five-
digit 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 customer’s 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 2716
+ 3329 + 3329
5035 (modulo 10) 6045 (regular addition)
Note: 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 Personal Identification Number (PIN)
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 GPIN
+ 1507 OFFSET
6143 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:

● 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:
● 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.
EDM 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:
● 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:
● 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 Security Features
ANSI PIN/PAN Block
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 Filled with

PIN digits or hex F depending
hex digit F
on length of PIN
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 0’s 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 PIN Verification
Diebold PIN Block
The Diebold PIN block is 16 hex digits and appears as follows:

PIN digits PIN or PAD digits PAD digits

depending on PIN length
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 ASCII (HEX) GRAPHIC DIGIT EBCDIC (HEX)
0 30 0 F0
1 31 1 F1
2 32 2 F2
3 33 3 F3
4 34 4 F4
5 35 5 F5
6 36 6 F6
7 37 7 F7
8 38 8 F8
9 39 9 F9
A 3A : 7A
B 3B ; 5E
C 3C < 4C
D 3D = 7E
E 3E > 6E
F 3F ? 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
ID Card and FIT Definitions

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 and FIT Definitions
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
FIT (Financial Institution Table)

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:
● 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:
● the terminal matches a FIT institution ID
● the terminal finds a null FIT (a FIT which is not completed during a configu-
ration down-line load)
● the terminal reaches the end of the FIT library
186 October 2004 U25604-J-Z745-1-7600

Security Features FIT (Financial Institution Table)
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
FIT’s between filled FIT’s. 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 financial institution can modify the FIT configuration data. For
the example, institution E has FIT’s 006 through 010. If, for some
FIT library reason, institution E wishes to add another FIT, for example,
between 008 and 009, the current FIT’s 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, FIT’s 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 FIT’s or groups of zero

FIT’s within the down-line load. These zero FIT’s may be given
values at a later date.
Switch FIT’s 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:
● 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.
FIT Data Definitions

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:
● 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 FIT Data Definitions
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 Description Length Byte

Mnemonic Position
PAGDX ALGO number index (not used) 1 8
PANDX PAN index 1 12
PANLN PAN length 1 13
PANPD PAN pad character 1 14
PCKLN PIN check length 1 10
PDCTB decimalization table 8 17-24
PEKEY encrypted PIN key 8 25-32
PFIID institution identification 5 2-06
PIDDX institution index 1 1
PINDX data track locator 3 33-35
PINPD PIN pad character 1 11
PLNDX language code index 1 36
PMXPN maximum PIN entry digits 1 9
POFDX offset number index 1 16
PRCNT PIN retry count index 1 15
PSTDX indirect next state index 1 7
reserved (not used) 2 37-38
U25604-J-Z745-1-7600 October 2004 189

Table 52: FIT fields listed by data track position
Byte Length Field Description

Position Mnemonic
1 1 PIDDX institution index
2-06 5 PFIID institution identification
7 1 PSTDX indirect next state index
8 1 PAGDX ALGO number index (not used)
9 1 PMXPN maximum PIN entry digits
10 1 PCKLN PIN check length
11 1 PINPD PIN pad character
12 1 PANDX PAN index
13 1 PANLN PAN length
14 1 PANPD PAN pad character
15 1 PRCNT PIN retry count index
16 1 POFDX offset number index
17-24 8 PDCTB decimalization table
25-32 8 PEKEY encrypted PIN key
33-35 3 PINDX data track locator
36 1 PLNDX language code index
37-38 2 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

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

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 ALGORITHM
000 DES
001 not supported
010 Diebold (not supported)
011 reserved
100 not supported
101 reserved
110 reserved
111 reserved
192 October 2004 U25604-J-Z745-1-7600

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 HEX VALUE RANGE

none 00
DES 04-10
DES (EDM) 04-0F
Diebold 40, 44
U25604-J-Z745-1-7600 October 2004 193

PIN Pad Character (PINPD)
PINPD is only used for DES encryption of PIN’s 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 HEX TYPE OF USE AS USE AS USE

BITS ENCRYPTION KEY 1 KEY 2 COORD.NO.
0000 0 single COM none no

0010 2 double MASTER COM no
0011 3 double PIN* COM no
0100 4 none none none no
1000** 8 single COM none yes
1010** A double MASTER COM yes
1011** B double PIN* COM yes
1100 C none none none 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

PAN Index (PANDX)
PANDX is the displacement from the delimiter specified by PINDX (byte 1, low-
order 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:
● 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

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 CARD RETRY COUNT CONDITION

BIT FORMAT
1 ISO Count down on each retry; stop at zero.
0 MINTS 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

Offset Number Index (POFDX)
POFDX is the displacement from the delimiter specified by PINDX (byte 2, low-
order 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 23 45 67 89 AB CD EF (standard hex digits)
01 23 45 67 89 01 23 45 (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

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 Hi-Order HEX digit LO-Order HEX digit

FIT byte 33 PAGDX (ALGO) PIDDX (ID)
FIT byte 34 PRCNT (RETRY) PANDX (PAN)
FIT byte 35 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 Bit Pair Definition

00XX Start sentinel, count forward
01XX First field separator, count forward
10XX End sentinel, count backward
11XX Reserved
XX00 Track 2
XX01 Track 3
XX10 Track 1
XX11 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)
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:
● 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

Message Authentication (MAC) 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 VALUE DESCRIPTION

FLAG CUSTOM.PPF
1 CHECK_TVN_MAC 0 Do not check TVN in Transaction reply messages, or
MAC in Transaction reply, State Table or FIT Load
messages.
1 Check TVN in Transaction reply messages, or MAC in

Transaction reply, State Table or FIT Load messages.
2 SEND_TVN_MAC 0 Do not send the TVN and MAC data in Transaction
Request messages
1 Send the TVN and MAC data in Transaction Request

messages
8 CHECK_MACHINE_NO 0 Do not check the Security Terminal Number in Tran.
Reply messages
1 Check the Security Terminal Number in Tran. Reply

messages
9 MAC_FLD_SELECTED 0 The MAC calculation is performed on the whole message
1 The MAC calculation is performed on the fields that are

specified in the MAC field selection table downloaded
from host.
10 SEND_TVN_MAC_SOL 0 Do not send the TVN and MAC on solicited device status
messages
1 Send the TVN and MAC on solicited device status

messages
SEND_MACHINE_NO 0 Do not include the Security Terminal Number in terminal
(not configurable via to host messages
ProCash/NDC-SOP or 1 Include the Security Terminal Number in terminal to host
ProConsult/NDC-SOP) messages
MAC_ASCII 0 Calculate the MAC in EBCDIC
(not configurable via
ProCash/NDC-SOP or 1 Calculate the MAC in ASCII
ProConsult/NDC-SOP)
200 October 2004 U25604-J-Z745-1-7600

Security Features Message Authentication (MAC)
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

Message Authentication (MAC) Security Features
Typical Message Authentication Procedure
The following steps describe a typical message authentication procedure.

● 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:
● 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

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\USER7.FM
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:
● 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.
● Solicited Status messages
● Unsolicited Status messages
● Transaction Request messages
U25604-J-Z745-1-7600 October 2004 205

Messages from Terminal to Network Messages
Figure 2: Transaction message flow
TERMINAL NETWORK
Consumer enters
card and PIN
Consumer enters Transaction Request message Make decision to allow

request data; terminal or disallow transaction
formats request
Complete transaction Transaction Reply message

as directed; format
status 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 Description
Symbols
X 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 Messages from Terminal to Network
[ ] 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 VAR indicates that the length of the field is variable. Numeric
(Numeric) parenthetic expressions following VAR show the maximum
number of characters allowed in the field.
U25604-J-Z745-1-7600 October 2004 207

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

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 Code No. of Characters

solicited/unsolicited ID ’1’ 1
message identifier ’1’ 1
field separator (FS) :1C 1
logical unit number (LUNO) --- 3 or 9
time variant number [---] 8
top-of-form flag --- 1
message coordination number --- 1
track 2 data [VAR] Var (40 max)
track 3 data [VAR] Var (106 max)
operation code buffer [---] 0 or 8
whole-amount/cents keyboard entry [---] 0, 8 or 12
PIN buffer (Buffer A) [VAR] Var (16 max)
general purpose buffer B [VAR] Var (32 max)
U25604-J-Z745-1-7600 October 2004 209


general purpose buffer C [VAR] Var (32 max)
field separator (FS) [:1C] 1
track 1 data buffer (1) identifier [1] 1
track 1 data buffer [VAR] Var (79 max)
field separator (FS) [:1C] 1 [1]
Transaction status identifier [2] 1 [1]
[1]
Last transaction status data [VAR] 25
CSP data ID ’U’ [:1C] 1
CSP data [VAR] Var (16 max)
confirmation CSP data ID ’V’ [:1C] 1
confirmation CSP data [VAR] Var (16 max)
MAC data [---] 8 [2]
[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

Message identifier field

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
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

Top-of-form (TOF) flag

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

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
Description: This variable length data field contains up to 40 characters of data
from track 2 of the magnetic stripe on the customer’s account
card. This field includes the data from the start sentinel to the end
sentinel inclusive.
212 October 2004 U25604-J-Z745-1-7600

Track 3 data field

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

Description: The operation code buffer field contains the data collected in the
operation code buffer as a result of function display keys (FDK’s)
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

Whole-amount and Cents keyboard entry field

Field size: 0 or 8, 0 or 12
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
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
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

General purpose buffer C

Field size: Up to 32 characters
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)

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)
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

Last transaction status data

Field size: 25
Description: Contains status data relating to the previous transaction
performed by the terminal.
It contains the following data:

● 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’

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
Description: This field contains an encrypted 16 character PIN.
216 October 2004 U25604-J-Z745-1-7600

Confirm CSP data ID ’V’

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 CSP’s is to be carried
out only the identifier will be sent if requested by the transaction
request state.
Confirmation CSP data

Description: Confirmation CSP data. This field contains an encrypted 16
character PIN.
MAC data field

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

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

solicited/unsolicited ID ‘2’ 1
message identifier ‘2’ 1
status descriptor --- 1
status information [---] VAR
MAC data field [---] 8 [1]
[1] These bytes are only sent if MACing is activated for the solicited message.
218 October 2004 U25604-J-Z745-1-7600

The following paragraphs describe the fields for the solicited status message.

Valid range: 1-2
In the case of the solicited status message, this field will be 2.

Valid range: 2
transmitted. The only valid value for the Solicited Status message
is 2.

Description: This three character data field is defined in the configuration data
field being the terminal number. See chapter ”Security Features”
from page 175 for additional details.
U25604-J-Z745-1-7600 October 2004 219

Status descriptor
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

Status information (status descriptor ‘F’ - Terminal State)

Field size: VAR
Description: The status information will vary according to which of the following
terminal commands has been received by the terminal:
● send configuration information
● 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

Status information (status descriptor ‘8’ - Device Fault)

Description: If the status descriptor = ’8’, this field identifies device reporting
abnormal status of following devices:
‘D’ - card reader/writer
‘E’ - cash dispenser
‘F’ - deposit
’G’ - receipt printer
’H’ - journal printer
‘V’ - statement printer
’\’ - envelope dispenser
See section ”Solicited Status (device fault)” on page 331 for

detailed description of status information.
MAC data field

message. See the section ”Message Authentication (MAC)” on
222 October 2004 U25604-J-Z745-1-7600

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

solicited/unsolicited ID ‘1’ 1
status information --- VAR
The following paragraphs describe the fields in the unsolicited status message.

Valid range: 1-2
In the case of the Unsolicited Status message, this field will be 1.
U25604-J-Z745-1-7600 October 2004 223


Valid range: 2
transmitted. The only valid value for the unsolicited status
message is 2.

Status information
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
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, FIT’s, 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
Transaction Reply commands

TERMINAL HOST
Terminal commands
U25604-J-Z745-1-7600 October 2004 225

Network to Terminal messages 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.
● 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: “Trans-
action 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

Transaction Reply command identifier ‘4’ 1
response flag [X] 1
logical unit number (LUNO) [X] 3
message sequence number [X] 3[1]
next state ID (000-254, 256-999) [---] 3
number of bills to dispense [---] VAR
group separator (GS) [:1D] not used
number of coins to dispense [---] not used
transaction serial number --- 4
function identifier --- 1
screen number (010-999) [---] 3
226 October 2004 U25604-J-Z745-1-7600


screen display update data [---] VAR
message coordination number --- 1
card return/retain flag --- 1
printer flag (0 - 4) (8) --- 1

printer data --- VAR (580 max)
group separator (GS) [:1D] 1
printer flag (0 - 4) [---] 1
printer data [---] VAR
printer flag (0 - 4) [---] 1
printer data [---] VAR
group separator (GS) [2] [:1D] 1
[2]
printer flag (0 - 4) [---] 1
printer data [2] [---] VAR
buffer identifier (4) [‘4’] 1
track 3 data [---] VAR (106 max)
buffer identifier (E) [‘E’] not supported
document destination [---] not supported
lift front/rear image(s) [---] not supported
archive lifted front/rear image(s) [---] not supported
lift zones in image list [---] not supported
archive lifted image list zones [---] not supported
check magnetism [---] not supported
check zone verification [---] not supported
report candidates/identify [---] not supported
document entry retries [---] not supported
U25604-J-Z745-1-7600 October 2004 227


buffer identifier (F) [‘F’] not supported
document enable code [---] not supported
group separator (GS) [:1D] not supported
document name [---] not supported
track 1 buffer identifier (K) ’K’ 1
track 1 data [---] VAR (max 78)
track 2 buffer identifier (L) ’L’ 1
track 2 data [---] VAR (max 39)
MAC data [---] 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.

Valid range: 4
transmitted. The only valid value for the Transaction Reply
command message is 4.
228 October 2004 U25604-J-Z745-1-7600

Message sequence number

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.

Next state ID data field

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

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

Transaction serial number

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

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 Short description of the function

’1’ or ‘7’ instructs a deposit + print
’2’ or ‘8’ instructs a dispense + print
’3’ or ‘9’ instructs a display + print
‘4’ 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.
‘5’ 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.
‘6’ Night safe deposit and print
‘A’ eject card and dispense and print (card before cash)
‘F’ card before parallel dispense and print
‘P’ instructs a print statement and wait
‘B’ or ‘C’ parallel dispense and print and card eject
‘Q’ Print statement and next state
230 October 2004 U25604-J-Z745-1-7600

Screen number
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

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 Content

3 screen number
VAR screen data
[1]
1 group separator
[1]
3 screen number
[1]
VAR screen data
[1] These fields are repeated if multiple screens are updated within one reply message.
U25604-J-Z745-1-7600 October 2004 231

Message coordination number

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

Valid range: 0-1
Description: This one-character field instructs the terminal to either return or
retain the customer’s 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

Printer flag field

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)
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

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
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


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
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.

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
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

message. See chapter ”Security Features” from page 175 for
additional details.
234 October 2004 U25604-J-Z745-1-7600

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 proce-
dures 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

The following table shows the fields of the Terminal Command message:
Table 59: Terminal Command message

Terminal Command identifier ‘1’ 1
response flag [X] 1
logical unit number (LUNO) [X] 3
message sequence number [X] 3
command code --- 1
The following paragraphs describe the fields in the Terminal Command

message.
Message identifier
Valid range: 1
transmitted. The only valid value for Terminal Command
messages is 1.

field being the terminal number. See section ”Message
Authentication (MAC)” on page 199 for additional details.
236 October 2004 U25604-J-Z745-1-7600


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
The Message sequence number is ignored by ProCash/NDC and
ProConsult/NDC.
Command code
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

‘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
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 Description
’A’ Processor and system
’B’ High order communications
’C’ SST devices
NOTE: 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 Description
’1’ Send hardware configuration only
’2’ Send supplies data only
’3’ Send fitness data only
’4’ Send tamper and sensor status data only
’5’ Send software ID and release number data only
’6’ Send enhanced configuration data
’7’ Send local configuration option digits
238 October 2004 U25604-J-Z745-1-7600

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

Load command identifier ‘3’ 1
Response flag [X] 1
Field separator (FS) :1C 1
Logical unit number (LUNO) [X] 3
Message sequence number [X] 3
Load identifier (configuration) ‘1’ 1
Modifier (states) ‘2’ 1
Field separator (FS) [:1C] 1
State number --- 3
State data --- 25
Field separator (FS) [:1C] 1 [1]
State number [---] 3 [1]
State data [---] 25 [1]
MAC data 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

The following paragraphs describe the fields in the State Tables Load command
message.
Load command identifier field

Valid range: 3
transmitted. The only valid value for a download command
message is 3.

field being the terminal number.

Load identifier
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

Modifier field
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
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
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

message. See section ”Message Authentication (MAC)” on page
199 for additional details.
U25604-J-Z745-1-7600 October 2004 241

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

Response flag [X] 1
Load identifier (configuration) ’1’ 1
Modifier (screens) ‘1’ 1
Field separator (FS) :1C 1[1]
Screen number --- 3[1]
Screen data --- 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

The following paragraphs describe the fields in the Screen Data Load command
message.
Load Command identifier field

Valid range: 3
transmitted. The only valid value for the Screen Data Load

field being the terminal number. See section for additional details.

Load identifier
Valid range: 1
U25604-J-Z745-1-7600 October 2004 243

Modifier field
Valid range: 1
as screen data. The valid value is ‘1’.
Screen number
Description: This is a three-character field that identifies the screen number for
the screen data that follows.
Screen data
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

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

Load Command Identifier ‘3’ 1
Response Flag [X] 1
Modifier (parameters+LUNO+timers) ‘3’ 1
Camera control X 1 (not supported)
Card reader error threshold --- 3
Reserved ’000’ 3
Track 3 write error threshold X 3 (not supported)
Optional parameters --- 3
Reserved ‘000’ 3
U25604-J-Z745-1-7600 October 2004 245


Timer number --- 2
Number of ticks --- 3
Timer number [---] 2[1]
Number of ticks [---] 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.

Valid range: 3
transmitted. The only valid value for the Configuration Parameters
Load command message is 3.

246 October 2004 U25604-J-Z745-1-7600


Load identifier
Valid range: 1
Modifier field
Valid range: 3
as LUNO, parameters and timer data. The valid value is ‘3’.
Optional Parameters
Description: The value in the optional parameters field is the sum of the
weights of the selected features.
Weight Features
’008’ 12 digit amount buffer size
’002’ automatic return to previous mode
’001’ separate ready (’B’) response to transaction reply
U25604-J-Z745-1-7600 October 2004 247

Timer number
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
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, down-
line loaded.
248 October 2004 U25604-J-Z745-1-7600

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


Load Command Identifier ‘3’ 1
Response Flag [X] 1
Modifier (parameters+LUNO+timers) ‘A’ 1
Logical unit number (LUNO) --- 3
Option number --- 2
Option code --- 3
Option number [---] 2
Option code [---] 3
Timer number --- 2
Number of seconds --- 3
Timer number [---] 2[1]
Number of seconds [---] 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

The following paragraphs describe the fields in the Enhanced Configuration

Parameters Load command message.

Valid range: 3
transmitted. The only valid value for the Enhanced Configuration
Parameters Load command message is 3.


Load identifier
Valid range: 1
250 October 2004 U25604-J-Z745-1-7600

Modifier field
Valid range: A
as LUNO, parameters and timer data. The valid value is ‘A’.
Logical Unit Number (LUNO)

Description: This three-character field defines the three-character LUNO
number.
Option number
Valid range: 00-99
Description: This two-character field defines the option number of the three-
character option code. See Table 64 “Option codes” for detailed
description of these codes.
Table 64: Option codes
Option Option Description

number code
00 Camera Control (not supported)
01 Ready/Supply options
000 No options selected (not supported)
001 Separate READY (B) status sent in response to Transaction Reply
002 Auto return to previous mode from supply mode (not supported)
008 12 digit amount buffer
02 001 Auto Voice on (default)
002 Auto Voice off
03 Date format for supervisor/journal messages
001 MMDD(YY)
002 DDMM(YY)
04 001-040 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

05 001-040 Left print column (Defines the leftmost print column for receipt and journal
messages. Default is ’008’)
06 Vandal Guard Open Condition
000 Open vandal guard when card detected (default condition)
001 Open vandal guard when keyboard is enabled
07 Track 1 format
001 ISO format (default condition)
002 VISA format
08 Reserved for future use
09 Diebold status reporting for vandal guard (not supported)
10 Tamper Indicator Control option (not supported)
11 Extended status control (not supported)
12 Specific Command Reject option
000 Do not transmit Specific Command Reject (default condition)
001 Transmit Specific Command Reject
13 001-255 Card reader error thresholds (Default value is 010)
14 Track 3 write error thresholds
15 Last Transaction Status information
000 Do not append information (default condition)
001 Append information
16-17 Not supported by ProCash/NDC
18-20 Codes reserved for future use
21-22 Not supported by ProCash/NDC
23 Envelope dispenser status option
000 Do not send unsolicited envelope dispenser messages (default)
001 Send unsolicited envelope dispenser messages
24-28, 30 Not supported by ProCash/NDC
31 Enable Audio Echo on Keyboard
000 Do not echo the keyboard (default condition)
001 Echo the keyboard,except in PIN states or/and when ’*’ is pressed
34 Message Coordination Number range. Default range is 31(Hex) - 3F(Hex). This
parameter allows to extend the MCN range up to 7E(Hex).
000 31H - 3FH (default condition)
001 31H - 7EH
50-99 Codes reserved for private use
252 October 2004 U25604-J-Z745-1-7600

Timer number
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
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

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

Response flag [X] 1
Load identifier (ITR) ‘2’ 1
Display flag --- 1
Active keys --- 6, 10
Screen timer --- 3
Screen data --- VAR
The following paragraphs describe the fields in the Interactive Transaction

Response command message.
254 October 2004 U25604-J-Z745-1-7600


Valid range: 3
transmitted. The only valid value for the Interactive Transaction
Response command message is 3.


Load identifier
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

Display flag
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
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 Declaration
first selects all numeric keys
second selects FDK ’A’
third selects FDK ’B’
fourth selects FDK ’C’
fifth selects FDK ’D’
sixth selects the Cancel key
seventh selects FDK ’F’
eighth selects FDK ’G’
ninth selects FDK ’H’
tenth selects FDK ’I’
256 October 2004 U25604-J-Z745-1-7600

Screen timer
Description: This three-character field determines time-out intervals for the
CRT display. Graphic characters represent 001 to 255 800-
millisecond 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
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

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

Response flag [X] 1
Modifier (FIT) ‘5’ 1
FIT number --- 3
FIT data (38 bytes) --- 114
FIT number [---] 3 [1]
FIT data (38 bytes) [---] 114 [1]
MAC data [---] 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


Valid range: 3
transmitted. The only valid value for the FIT Data Load command
message is 3.


Load identifier
Valid range: 1
Modifier field
Valid range: 5
as FIT data. The valid value is ‘5’.
U25604-J-Z745-1-7600 October 2004 259

FIT number
Description: This three-character field designates the number assigned to the
FIT in the following field.
FIT data
Field size: 38 bytes
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
represent the MAC calculation of the FIT Data Load command
message. Refer to section ”Message Authentication (MAC)” on
260 October 2004 U25604-J-Z745-1-7600

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

Response flag [X] 1
Load identifier (encryption key change) ‘3’ 1
Key change [---] 1
New key data [---] 24
U25604-J-Z745-1-7600 October 2004 261

The following paragraphs describe the fields in the Encryption Key Load
message.

Valid range: 3
transmitted. The only valid value for the Encrypion Key Load
command message is ‘3’.


Load identifier
Valid range: 3
Description: This one-character data field tells the terminal that encryption key
262 October 2004 U25604-J-Z745-1-7600

Key change
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

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

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

Response flag [X] 1
Load identifier (encryption key change) ‘4’ 1
Key change [---] 1
Key data size [---] 3
New key data [---] 24 or 48
264 October 2004 U25604-J-Z745-1-7600

The following paragraphs describe the fields in the Extended Encryption Key
Load message.

Valid range: 3
transmitted. The only valid value for the Extended Encrypion Key
Load command message is ‘3’.


Load identifier
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

Key change
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)
Key data size

Field size: 3
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

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

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

Response flag [X] 1
Modifier (Dispenser Currency Mapping ‘E’ 1
Table)
Dispenser Currency Mapping Table --- VAR
data
Number of Mapping Entries --- 2[1]
(range 01-FF)
Currency Type (range 01-FF) --- 2[1]
used for mapping to state ’G’
table entry 7
Cassette Type. Single digit ASCII hex --- 1[1]
value (range 0-F)
Denomination for Cassette. Five-digit --- 5[1]
ASCII numeric value
(e.g. 00010 for $10)
[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

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

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 configu-
ration. 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 recon-
figured, 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

Response flag [X] 1
Load identifier (configuration data) ‘1’ 1
Modifier (configuration ID number) ‘6’ 1
Configuration ID number --- 4
The following paragraphs describe the fields in the Configuration ID Load

command message.

Valid range: 3
transmitted. The only valid value for the Configuration ID Load

270 October 2004 U25604-J-Z745-1-7600


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
Valid range: 1
Modifier
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
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

Date And Time Load
This message is used to set the date and time in the terminal.
Table 71: Date And Time Load

Response flag [X] 1
Modifier (configuration ID number) ‘C’ 1
Date/Time data VAR 10
The following paragraphs describe the fields in the Date And Time Load
command message.

Valid range: 3
transmitted. The only valid value for the Date And Time Load
272 October 2004 U25604-J-Z745-1-7600




Load identifier
Valid range: 1
Modifier
Valid range: C
data that follows is the configuration ID. The only valid value is ‘C’.
U25604-J-Z745-1-7600 October 2004 273

Date and time data

Description: The date and time specified by the is formatted as follows:
„YYMMDDHHMM“.
Description Range
YY = Year ‘00’ - ‘99’
MM = Month ‘01’ - ‘12’
DD = Day ‘01’ - ‘31’
HH = Hour ‘00’ - ‘23’
MM = Minute ‘00’ - ‘59’
274 October 2004 U25604-J-Z745-1-7600

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


Response flag [X] 1
Modifier (configuration ID number) ‘B’ 1
Transaction request field VAR 37 (only 17 supported)
Transaction reply field VAR 23 (only 17 supported)
Solicited status field --- 11 (not supported)
Other messages field VAR 4
Track 1 field VAR 6
Track 2 field VAR 6
Track 3 field VAR 11
MAC data [---] 8
U25604-J-Z745-1-7600 October 2004 275

The following paragraphs describe the fields in the Message Authentication

Field Selection Load command message.

Valid range: 3
transmitted. The only valid value for the Message Authentication
Field Selection Load command message is 3.


Load identifier
Valid range: 1
276 October 2004 U25604-J-Z745-1-7600

Modifier
Valid range: B
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 Description
Position
0 0 - MAC complete message; 1 - Selective MACing
1 Solicited/Unsolicited ID and Message identifier
2 Logical unit number
3 Reserved
4 Time variant number
5 top-of-form flag
6 Message coordination number
7 Track 2 data
8 Track 3 data
9 Operation code data
10 Amount entry field
11 PIN buffer
12 General Purpose Buffer B
13 General Purpose Buffer C
14 Track 1 data buffer identifier
15 Track 1 data
16 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

Field Description
Position
0 0 - MAC complete message; 1 - Selective MACing
1 Transaction Reply command identifier and response flag
2 Logical unit number
3 Message sequence number / Time variant number
4 Next state ID
5 Number of bills to dispense from denomination 1-4
6 Transaction serial number
7 Function identifier
8 Screen number
9 Screen display update data
10 Message coordination number
11 Card return / retain flag
12 Printer flag field and Printer data
13 Printer flag field and Printer data after the first group separator
14 Printer flag field and Printer data within the next group separators
15 Track 3 buffer identifier
16 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

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
Offset Description
Track 3 field
Field size: 11
Valid range: 0 or 1
Offset Description
MAC data field

represent the MAC calculation of the Message Authentication
Field Selection Load message. See the section ”Message
U25604-J-Z745-1-7600 October 2004 279

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:
● 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
Default operations include the following:

● 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

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.
03 Too many print groups in the Transaction Reply message.
More than 13 print groups are present in a Transaction
Reply message.
04 A group separator is missing or found unexpectedly.
U25604-J-Z745-1-7600 October 2004 281

B Field value errors

01 Illegal Message Class. Message class was not 1, 2, 3, 4
or 7, or message class was 7 and exit support was not
detected.
02 Illegal Message Sub-Class or Identifier on a Configu-
ration Load message with class '3' . The following will
cause this report:
– Message sub-class outside the range '1' - '4'
– Message identifier outside the range '1' - '6' or 'A' -'C'.
03 Illegal Load Key Message Identifier. Within a load
encryption key data message:
– The modifier field is outside the range '1' - '9'
04 Illegal Terminal Command Code:
– Returned if the command code is outside the
range '1' - '?'.
05 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.
– The command code is '?' but the modifier is not 0 or 1.
06 Illegal Function ID in Transaction Reply command:
– Function ID outside the range 'l'- '9', 'A', 'B', 'C', 'F', 'P',
'Q', 'S' or 'T'
07 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.
282 October 2004 U25604-J-Z745-1-7600

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 Trans-
action Reply message is out of range.

09 Invalid Message Co-Ordination Number. In a Transaction
Reply message, the co-ordination number is not zero and
does not match the transmitted value.
10 Illegal FIT number. A FIT in a FIT load message is not in
the range of the reserved pool size.
11 Too many notes in Transaction Reply command. The total
number of notes requested exceeds the limit of 40 or 20.
13 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.
14 Too many coins in Transaction Reply command. Total
number of coins requested exceeds the limit of 25.
15 Unrecognised buffer identifier. Returned if the Trans-
action Reply contains a buffer identifier not currently
supported.
16 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.
17 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.
18 The screen identifier in an Override Reserved Screen
Command is not in the range 'D0000' to 'D0010'.
C Illegal Message Type for Current Mode.
01 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.
U25604-J-Z745-1-7600 October 2004 283

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.
– Transaction Replies (not Print Immediate).
03 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).
– Interactive Transaction Response.
04 Message unacceptable in current mode.
The following messages cannot be accepted while in In-
Service mode:
– Terminal commands '4', '5', '6', '9'.
– Interactive Transaction Response when not in Trans-
action Request State.
– Also applies to terminal command when attempting to
enable Supervisor 'Dump Images' but terminal is
performing a transaction.
05 Reserved
06 Reserved
07 Reserved
08 Security key initialise message rejected. The key is
already in a legal state.
09 Reserved
10 Message not accepted while processing a Transaction
Reply.
11 not used
12 Cannot process a document while a statement print
function is being carried out.
13 Cannot perform a statement print function while
processing a document.
14 not used
284 October 2004 U25604-J-Z745-1-7600

D Hardware failure
01 Encryption failure during key change message.
02 Time of day clock failure during data/time set command or
invalid data sent.
03 Reserved
04 Key initialisation command not accepted, due to encryption
failure during initialisation.

05 Reserved
06 Insufficient disk space.
E Not supported
01 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.
03 Reserved
04 Reserved
05 Journal printer backup is inactive
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
Terminal
Terminalinin No
inservice
service
mode
mode??
Yes
Terminal
Terminal in in No
No Is
Is message
message
transaction
transaction aaprint
print
request
request immediate
immediate??
state
state??
Yes Yes
Yes Terminal
Terminal in in
Process message out
out--of
of--service
service
mode
mode ? ?
No
Terminal in
Yes Terminalmode
supervisor in
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
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 ID’s and the assignment to the internal
ProCash/NDC or ProConsult/NDC step function:
Table 74: NDC function ID’s assigned to step functions
Function description ID Step function

Print Immediate ‘4’ DC_F_PRINT_IMMEDIATE
Set Next State and Print ‘5’ DC_F_SET_NEXT_STATE
Night Safe Deposit and Print ’6’ DC_F_NIGHT_SAFE_DEPOSIT
Deposit and Print ’1’ or ’7’ DC_F_DEPOSIT
Dispense, Deliver and Print ‘2’ or ‘8’ DC_F_DISPENSE
Display and Print ‘3’ or ‘9’ NDC_F_DISPLAY
Eject Card Dispense and Print ‘A’ NDC_F_CBC_DISPENSE
(Card Before Cash)
Parallel Eject/Dispense and ‘B’ or ‘C’ NDC_F_PARALLEL_DISPENSE
Print (Fast Cash)
Eject Card Dispense and Print ‘F’ NDC_F_CBC_PARALLEL
Parallel
Print Statement and Set Next ’Q’ NDC_F_PRINT_STM_NEXT
State
Print Data and Stay in Present ’P’ NDC_F_PRINT_STM_WAIT
State
Ignore Reply Function DC_F_IGNORE
U25604-J-Z745-1-7600 October 2004 287

Terminal operations in Transaction Replies 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:
3. If a fault occurs while the printer is printing, the terminal sends a printer
288 October 2004 U25604-J-Z745-1-7600

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.

● 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
unsolicited message indicating a fault.
Deposit and Print (‘1’ or ‘7’)
The terminal handles the Deposit and Print function ID as follows:

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.
● 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

● 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.
● 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.
● 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.
12. If a fault occurs while the printer is printing the terminal returns a printer
290 October 2004 U25604-J-Z745-1-7600

Dispense, Deliver and Print (‘2’ or ‘8’)
The terminal handles the Dispense, Deliver and Print function ID as follows:
2. Initializes for the dispense function.
3. Starts dispensing.
4. If a fault occurs during dispense, the terminal proceeds as follows.
● 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:
● 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
7. If a fault occurs while either printer is printing, the terminal proceeds as
follows:
● Returns a printer unsolicited status message indicating a fault.
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
Display and Print (‘3’ or ‘9’)
The terminal handles the Display and Print function ID as follows:

2. After the screen is displayed the terminal does the following:
● 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
U25604-J-Z745-1-7600 October 2004 291

4. If a fault occurs while the printer is printing, the terminal proceeds as follows:
● Sends a printer unsolicited status message indicating a fault.
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
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

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
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

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
If the notes are taken within the time frame of Timer 05 and Timer 07
the timer is cancelled.
● 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.
Electronic Journal Upload (EJU) commands

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:
● 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

Electronic Journal Upload (EJU) commands 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 Mandatory Code No. of Characters

Optional
Message Identifier M 6 1
Field Separator (FS) M :1C 1
Command Type M 3 1
Option Number Block Size O 60 2[1]
Option Value Block Size O VAR 3[1]
Option Number Retry O 61 2[1]
Threshold
Option Value Retry O VAR 3[1]
Threshold
Acknowledge Timer O 60 2
Number
AcknowledgeTimer Value O VAR 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
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

Command Type
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

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

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

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

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

Acknowledge Timer Number

Valid range: 60
Description: This field indicates the Acknowledge Timer Number with the
following Acknowledge Timer Value.
Acknowledge Timer Value

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

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

Optional
Command Type M 1 1
Last Character Received O VAR 6
Message Identifier
Valid range: 6
Command Type
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

Last Character Received

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

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

Optional
Command Type M 2 1
Last Character Received M VAR 6
Message Identifier
Valid range: 6
Command Type
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

Last Character Received

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 Message Identifier

Send Configuration Information 1
Send Supply Counters 2
Send Error Log Information 4
Send Date/Time Information 5
Send Configuration ID 6
Hardware Configuration Data H
Supplies Data I
Fitness Data J
Tamper and Sensor Status Data K
Software ID and Release Number L
Local Configuration Option Digits M
U25604-J-Z745-1-7600 October 2004 303

NDC Status Messages Messages
Send Configuration Information
This solicited status message is sent to central in response to a Send Configu-

ration Information terminal command message.
Table 78: Send Configuration Information

configuration ID --- 4
hardware fitness --- 22 or 38
hardware configuration --- 44 or 76
supply status --- 23 or 26
sensor status --- 12
NDC+ release number --- 6
NDC+ software ID --- 9
Message identifier
Field size: 1
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
Description: Contains the last four digit configuration ID numbers sent to the
terminal from host.
304 October 2004 U25604-J-Z745-1-7600

Hardware Fitness
Field size: 22 or 38
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 Severity
0 no error
1 routine errors have occurred
2 warning conditions have occurred
3 suspend, terminal is currently in suspend state due to suspected
tampering with this device
4 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 Contents Field Contents

0 time of day clock 11 encryptor
1 high order communications 12 security camera
2 system disk 13 door access
3 card reader 14 flex disk
4 cash handler 15 cassette type 1
5 depository 16 cassette type 2
6 receipt printer 17 cassette type 3
7 journal printer 18 cassette type 4
8 reserved 19-20 reserved
9 reserved 21 statement printer
10 night safe depository
U25604-J-Z745-1-7600 October 2004 305

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

22 Signage Display 31 Reserved
23 Reserved 32 Digital Audio Service
24 Coin Dispenser 33 Reserved
25 System Display 34 Reserved
26 Media Entry Indicators 35 Reserved
27 Envelope Dispenser 36 Reserved
28 Document Processing Module 37 Reserved
29 Coin Dispensing Module
Tamper Indication
30 Document Processing Module
Tamper Indication Module
Hardware configuration
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

Table 81: Device Configuration Table
Byte Device Description

0 Product Class
0E 5663
0F 5674
10 5675
11 5684
12 5685
13 5688
14 5665
15 5670
16 personaS75
17 personaS88
18 personaS40
19 personaS70
1A personaS74
1B personaS84
1C personaS85
1E 5305
1F 5886
1 7F No Configuration
2 System Disk
00 Hard Disk present
02 Reserved
3 Magnetic Card Reader/Writer
01 Track 2 (read only)
03 Track 1/2/3 MCRW (write track3 only)
05 Low cost DIP reader
07 3 Track Write MCRW
08 Track 2 Smart Card Reader
09 Track 1/2/3 Smart Card Reader
0A 3 Track Write Smart Card Reader
0B Track 2/3 DIP MSR
0C Track 1/2/3 CIM 86 MCRW
10 Track 1/2 DIP MSR
11 Track 1/2 Swipe Card DIP Reader
1D MIMIC Smart Card DIPReader
4 Cash Handler
00 Standard cash handler not configured
01 Standard cash handler configured
02 Angel spray dispenser configured
5 Depository
00 Not configured
01 Reserved
02 PPD
03 Reserved (third generation ADM)
04 DPM envelope depository (non-5665 SSTs only)
U25604-J-Z745-1-7600 October 2004 307

6 Receipt Printer
00 Not configured
01 Plain paper
02 Black dot paper (TOF)
03 Sideways printing, no black mark
04 Sideways printing, black mark
05 Thermal printer - no black mark
06 Thermal printer - black mark
07 Thermal printer - sideways printing, no black mark
08 Thermal printer - sideways printing, black mark
7 Journal Printer
00 Not configured
01 Integral journal printer
02 Reserved
03 Thermal printer
80 Electronic journal
81 Electronic journal and integral journal printer
82 Reserved
83 Electronic journal and thermal printer
8 Reserved
00 Not configured
01 Configured
9 Reserved
00 Not configured
01 Configured
10 Night Safe Depository
00 Not configured
01 Configured
02 Reserved
11 Encryptor
?0 Not configured
?1 NBS encyptor
02 Reserved
03 Reserved
04 Reserved
?5 EKC encryptor
06 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
12 Security Camera
00 Not configured
01 Fixed format (for instance, 3M)
02 Variable format (for instance, D/A)
03 Reserved
04 Digital
13 Door Access
00 Not configured
01 Configured
308 October 2004 U25604-J-Z745-1-7600

14 Flex Disk
00 Not configured
01 1.44 MB flex disk connected
02 2.88 MB flex disk connected
15 Tamper Indicat. Bins not DPM or CDM
00 No TI bins present
01 Secure cash, insecure cards, PPD or no PPD
02 Secure cash, insecure cards, secure PPD
03 Secure cash, cards, and PPD or no PPD

16 Cardholder Keyboard
00 Reserved
01 Standard (BAPE) Keyboard
02 EKC Keyboard
17 Operator Keyboard
00 Not configured
01 Standard keyboard (Basic)
02 Keyboard plus FDK’s (Enhanced)
18 Cardholder Display / Voice
BIT 0 0 - (always)
BIT 1 0 - (always)
BIT 2 0 - Voice not supported
BIT 2 1 - Voice supported if digital audio present
BIT 3 0 - Standard FDK’s
BIT 3 1 - Touch screen
BIT 4 0 - VGA
BIT 4 1 - VGM Translator
BIT 5 0 - (always)
BIT 6 0 - (always)
BIT 7 0 - (always)
19 7F No configuration
20 7F No configuration
21 Statement printer
00 Not configured
01 Configured
02 Reserved
03 Reserved
05 5665 DPM statement printer
09 Enhanced thermal statement printer (SDC+)
22 Signage Display [1]
00 Not configured
01 Configured
23 --- Reserved
24 Coin Dispenser [1]
00 None
01 RMX
02 S4
25 System Display [1]
00 Not configured
01 20 x 40 Display
02 Enhanced Display (16 x 32)
U25604-J-Z745-1-7600 October 2004 309

26 Media Entry Indicators [1]

00 Not configured
01 Configured
27 Envelope Dispenser [1]
00 Not configured
01 Configured
02 Reserved
03 Reserved
28 Document Processing Module [1]
00 Not configured
01 5665 DPM configured
02 DP-ATM configured
29 Coin Dispensing Module Tamper
Indication [1]
00 Not configured
01 Present
30 Document Processing Module Tamper
Indication [1]
00 Not configured
01 Present
31 --- Reserved
[1]
32 Digital Audio Service
00 Not configured
01 Present
33-37 --- [1] Reserved
[1] These devices are only appended in the message if command modifier
’6’ is used.
310 October 2004 U25604-J-Z745-1-7600

Supply Status
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

0 reserved 11 - 14 not used = 0
1 reserved 15 cassette type 1
2 not used = 0 16 cassette type 2
3 card capture bin 17 cassette type 3
4 cash handler reject bin 18 cassette type 4
5 deposit bin 19-20 not used = 0
6 receipt paper 21 statement printer
7 journal paper 22 statement ribbon
8 not used = 0 23 reserved [1]
9 not used = 0 24 reserved [1]
10 night safe depository 25 envelope dispenser [1]
[1] These devices are only appended in the message if command modifier
’6’ is used.
Sensor Status
Field size: 12
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
U25604-J-Z745-1-7600 October 2004 311

NDC+ Release Number

Field size: 6
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
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

Send Supply Counters
This solicited status message is sent to the host in response to a “Send Supply
Counters” terminal command message.
Table 83: Supply Counters


transaction serial number --- 4
accumulated transaction count --- 7
notes in cassette --- 20
notes rejected --- 20
notes dispensed --- 20
last transaction notes dispensed --- 20
cards captured --- 5
envelopes deposited --- 5
camera film remaining --- 5 (not supported)
last envelope serial number --- 5
Message identifier
Field size: 1
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
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

Accumulated transaction count

Field size: 7
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
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
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

Last transaction notes dispensed

Field size: 20
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
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
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

Send Error Log Information
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

group number C 1
new entries --- 2
date last cleared --- 12
month --- 2 [1]
day --- 2 [1]
hour --- 2 [1]
minute --- 2 [1]
device identification (DID) --- 1 [1]
maintenance status (M-Status) --- 2 [1]
severity --- 1 [1]
part number --- 1 [1]
maintenance data (M-Data) VAR 23 [1]
field separator :1C 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

Group number
Field size: 1
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
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
Description: The date and time the log was last cleared in the following format:
YY = Year 00-99
MM = Month 01-12
DD = Day 01-31
HH = Hour 00-23
MM = Minute 00-59
SS = Second 00-59
Month
Field size: 2
Valid range: 01-12
Description: Month log entry
U25604-J-Z745-1-7600 October 2004 317

Day
Field size: 2
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’ Processor system (not supported by Wincor Nixdorf
terminals)
‘B’ Communications (not supported by Wincor Nixdorf

terminals)
‘C’ or greater- ATM device log
‘?’ - Repeat log
318 October 2004 U25604-J-Z745-1-7600

Maintenance status (M-status)

Field size: 2
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

Send date/time information
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

TOD clock status 0-2 1
terminal date/time --- 12
Message identifier
Field size: 1
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
Description: The actual date and time returned by the terminal clock in format:
YY = Year 00-99
MM = Month 01-12
DD = Day 01-31
HH = Hour 00-23
MM = Minute 00-59
SS = Second 00-59
320 October 2004 U25604-J-Z745-1-7600

Hardware Configuration 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 ’1’.
Table 86: Hardware Configuration Data


message identifier ‘H’ 1
configuration ID identifier ’A’ 1
configuration ID --- 4
product class identifier ’B’ 1
product class --- 2
hardware configuration identifier ’C’ 1
device identifier --- 1
hardware configuration data --- 2
[1]
device identifier [1] [---] 1
hardware configuration data [1] [---] 2
[1] These fields, devided through group separators, are repeated for each of the devices
present in the ATM.
Message identifier
Field size: 1
Valid range: ’H’
configuration information terminal command message (command
code ’7’ inclusive command modifier ’1’).
U25604-J-Z745-1-7600 October 2004 321

Configuration ID Identifier (’A’)

Field size: 1
Valid range: ’A’
Description: Identifier of the four digit configuration ID number that follows.
Configuration ID
Field size: 4
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
Description: This two character field contains the product class of the terminal.
The following entries are possible:
Product class Sytem Type

0E 5663
0F 5674
10 5675
11 5684
12 5685
13 5688
14 5665
15 5670
16 personaS75
17 personaS88
18 personaS40
19 personaS70
1A personaS74
1B personaS84
1C personaS85
322 October 2004 U25604-J-Z745-1-7600

Hardware configuration identifier (’C’)

Field size: 1
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: 1
Valid range:
Description: This field contains the Device Identifier of each present device.
Hardware configuration data

Field size: 2
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

Supplies Data

Table 87: Supplies Data

message identifier ‘I’ 1
supply status identifier ’A’ 1
supply status data --- VAR
[1]
device identifier [---] 1
[1]
supply status data [---] VAR
present in the ATM.
Message identifier
Field size: 1
Valid range: ’I’
Supply status identifier (’A’)

Field size: 1
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.
324 October 2004 U25604-J-Z745-1-7600

Supply status data

Field size: VAR
Valid range: each element of the supplies status data will take one of the
following values:
’0’ Not configured/reserved
’1’ Good state
’2’ Media low

’3’ Media out
’4’ Overfill
Description: This field contains information for each present device indicating
the condition of the parts of the device that are replenishable.
Fitness Data

Table 88: Fitness Data

message identifier ‘J’ 1
hardware fitness identifier ’A’ 1
fitness --- 1
[1]
device identifier [---] 1
[1]
fitness [---] 1
present in the ATM.
Message identifier
Field size: 1
Valid range: ’J’
U25604-J-Z745-1-7600 October 2004 325

Hardware fitness identifier (’A’)

Field size: 1
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.
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’ No error/ not supported
’1’ Routine errors have occurred
’2’ Warning conditions have occurred, investigation required
’3’ Suspend Mode. The terminal is currently in the suspend
mode due to suspected tampering with this device
’4’ 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

Tamper and Sensor Status Data

Table 89: Tamper and Sensor Status Data


message identifier ‘K’ 1
sensor status identifier ’A’ 1
sensor status --- 5
field separator :1C 1
tamper indicator identifier ’B’ 1
tamper status --- VAR
Message identifier
Field size: 1
Valid range: ’K’
Sensor status identifier (’A’)

Field size: 1
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

Tamper status identifier (’A’)

Field size: 1
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

Table 90: Software ID and Release Number

message identifier ‘L’ 1
release number identifier ’A’ 1
NDC release number --- VAR (6)
software ID identifier ’B’ 1
NDC software ID --- VAR (9)
See description of the fields on the following page.
328 October 2004 U25604-J-Z745-1-7600

Message identifier
Field size: 1
Valid range: ’L’
Release number identifier (’A’)

Field size: 1
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

Local Configuration Option Digits

Table 91: Local Configuration Option Digits

message identifier ‘M’ 1
local options identifier ’A’ 1
local option digits --- VAR (16)
Message identifier
Field size: 1
Valid range: ’M’
Local options identifier (’A’)

Field size: 1
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

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)


transaction status VAR 17
field separator [:1C] 1
error severity VAR 5
diagnostic M-status --- VAR
diagnostic M-data [---] VAR
supplies status VAR 5
Device Identifier
Field size: 1
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 Device
D card reader/writer
E cash handler
F depository
U25604-J-Z745-1-7600 October 2004 331

Transaction Status
Field size: 17
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 Short Description Detailed Description

0 no error Continue to use. No error has occurred.
Diagnostic information follows.
1 routine error Continue to use. A routine error has occurred
and diagnostic information follows.
2 warning Continue to use but it is recommended that the
network operator is informed of the error or
exception condition. Diagnostic information
follows.
3 suspend The terminal will suspend transaction
processing on completion of the current trans-
action (state 000 entered). This is sent if
cardholder tampering is suspected.
4 fatal Device is out of service and will continue to
report intervention at the terminal. It is recom-
mended that the terminal is put out of service or
transactions involving the faulty device are not
allowed.
332 October 2004 U25604-J-Z745-1-7600

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
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

Each character is always coded in the same way:
Table 94: Supplies Status Table
Code Short Description Detailed Description

0 no-new-state The state of the container can be assumed as
unchanged
1 good state The state of the container is known to be good
(not low empty or overfilled).
2 media low The container has reached the low condition.
3 media out The container is empty.
4 overfill 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

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


device identifier (DID) --- 1
device status VAR 13
error severity VAR 5
diagnostic M-status --- VAR
diagnostic M-data [---] VAR
supplies status VAR 5
Device Identifier (DID)

Field size: 1
Description: This field identifies the device by means of a device identification
(DID).
Device Status
Field size: 13
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

Error Severity
Field size: 2
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
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

Power Up (unsolicited) (DID ‘B’)
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 No. of Sol./ Code Detailed Definition

Characters Unsol.
Device Identifier 1 B Indicates a power failure.
Device Status 4 U VAR 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

Card Reader (sol./unsol.) (DID ‘D’)

Characters Unsol.
Device Identifier 1 D Indicates a card reader
unit message
Transaction 1 U 0 No transaction exception
Device Status; condition occurred but
gives details of any consult other fields for
transaction related error severity, diagnostic
exception status or supplies status
condition detected changes.
while processing a S/U 1 Cardholder did not take
card at the his card within the
terminal. allowed time and it was
captured or jammed.
S/U 2 The mechanism failed to
eject the card and it was
captured or jammed.
S/U 3 The mechanism failed to
update Track 3 on the
card.
S/U 4 Invalid Track 3 data
received from Central
Error Severity 1 0-4 This is a single character
field coded in the
standard way to be used
to make a shutdown
decision.
Diagnostic 2-10 00 Operation successful
M-status and 01 Blank track
M-Data 02 Track not supported
03 Read error
04 Write error
05 No card in reader at start
of command
06 Card removed during
capture
07 Shutter jammed open
338 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
08 Shutter switch failure
detected
09 Error recovery successful
10 shutter jammed closed
11 Card jam (not during

capture)
12 Card captured after
unsuccessful eject
13 Possible cardholder
tampering
14 Too many consecutive
read errors
write errors
card jams
shutter jammed closed
18 Card jam during capture
invalid cards
20 Device still inoperative
21 No card during clean test
22 Speed out of spec. (fast)
23 Speed within +3%
24 Speed within +-1%
25 Speed within -3%
26 Speed out of spec. (slow)
27 Invalid card detected
33 CIM service test failed
35 Error in track 3 data
37 CROPF feature not supp.
38 LFCC bin full soon/full
40 LFCC bin removed
U25604-J-Z745-1-7600 October 2004 339


Characters Unsol.
41 CROPF feature failure
50 Card not in SCRW stage
position
51 Smart card stopper pin or
contacts lowered, unable
to capture
52 Invalid smart card
command code error
command data error
54 SCIF not configured/not
responsing
55 SCIF response timeout
exeeded
56 Card reader is in SCRW
mode (diagnostics only)
response length
64 Invalid SCIF command
code
65 Invalid SCIF command
format
66 No smart card encryptor
response error
67 Invalid key ID
68 Invalid key type
69 Invalid parent key type
70 Invalid key - doesn’t exist
71 Password not decimal
72 Password no match
73 Key integrity error
74 Key parity error
75 Invalid data format
76 Stopper PIN failure
77 Contact unit failure
78 Card movement failure
340 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
79 Smart card switch off
failure
80 Smart card removed error
81 No smart card response
82 Smart card transmission

error
83 Smart card switched off
84 Illegal card type/param.
85 Power up ime exceeded
86 ANSI PIN block error
87 CIM self test failed
88 CIM security module
defective
89 CIM security module
communication failure
90 CIM interface board
defective
91 CIM interface board
communication failure
Supplies Status 1 0 No new state
1 No overfill condition
4 Overfill condition
U25604-J-Z745-1-7600 October 2004 341

Dispenser (sol./unsol.) (DID ‘E’)

Characters Unsol.
Device Identifier 1 E Indicates a dispenser
solicited or unsolicited
message.
Transaction Status 1 U 0 Successful operation, but
(T-code plus an exception condition
T-data); gives occurred which is detailed
details of a in later fields.
dispense S 1 Short dispense
operation in S 2 No notes dispensed
response to a S 3 Faulty dispense. Notes
transaction reply dispensed unknown. The
command following counts contain
message. requested dispense
values.
S 4 No notes dispensed or
card not ejected. This
status is returned on a
card before cash trans-
action if the stack
operation fails and the
notes are purged prior to
card eject.
U 5 Some notes have been
retracted following a
Present and Notes not
taken time-out. The
number of notes retracted
is unknown.
Characters 2-9 Characters Cass Types
(T-Data) contain
notes dispensed 2-3 logical cassette 1
counts. Each pair 4-5 logical cassette 2
of characters 6-7 logical cassette 3
represents a two- 8-9 logical cassette 4
digit decimal value
in range 00-99 per
cassette type
342 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
Error Severity 5 0-4
Character ’0’ Severity info related to

complete device.
Character ’1’ Severity related to

cassette type 1.
cassette type 2.
cassette type 3.
cassette type 4.
Diagnostic 2-32 00 No error
M-status and 01 Pick requested from non-
M-data installed cassette
02 Too many bills being
rejected
03 Pick failure
04 Pick failure and low (out
of bills)
05 Sensor failure or currency
jam
06 Divert gate fault
07 Reject bin inoperative
08 Reject bin overfill
09 Comm failure between
dispenser and terminal
10 Fatal previous error
11 Unrecovered previous
error
U25604-J-Z745-1-7600 October 2004 343


Characters Unsol.
12 Present mechanism
failed or jammed
13 Exit shutter jammed open
14 Exit shutter jammed
closed
15 Bills passing overfill
sensor on present
operation
16 Timing disk did not
operate correctly
17 Exit sensor failed to clear
18 Timing disk did not
operate correctly
19 Exit sensor blocked
initially on next operation
20 Not configured
21 Security violation
22 Security inhibition
23-27 Reserved
28 An area of NVRAM
cannot be accessed
29 Presenter transport
timing disk did not
operate correctly or motor
failed
30 One of the presenter
transport sensors failed
clear or blocked
31 Reserved
32 Heartbeat on execution
processor failed (80652)
33 Communications failure
on the I2C bus of the
execution processor
344 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
34 A present bills operation
has been attempted
without any bills being
stacked or a retract
operation has been

attempted with no bills
presented.
35 Operation incomplete due
to ac and 24V dc power
disconnection through
interlock.
36 Pick valve test not
attempted because
cassettes were installed
37 TI service switched ON
38 TI service switched OFF
39 LVDT or associated
circuitry malfunctioning
40 Bill parameters not

configured
41 An attempt to pick from a
cassette which has been
disabled for In Service
Replenishment
Supplies Status. 5
Indicates the state
of the reject bin
and currency
cassettes.
Codes for the 0 no new state

reject cassette 1 no overfill condition
(character ’0’) 4 overfill condition
Codes for disp. 0 no new state

cass. types 1-4 1 Sufficient notes
(character ’1’ - ’4’) 2 Low on notes
3 Out of notes
U25604-J-Z745-1-7600 October 2004 345

Depository (sol./unsol.) (DID ‘F’)

Characters Unsol.
Device Identifier 1 F Indicates a depository
message.
Transaction Status 1 U 0 Successful operation, but
(T-code plus an exception condition
T-data); gives occurred which is detailed
details of a deposit in the following field.
operation in S 1 Time-out on cardholder
response to a deposit.
transaction reply S 2 Failure to enable
command mechanism for a deposit
message S 3 Deposit failed, cardholder
has access to envelope.
This status is also
returned if there is any
doubt about cardholder
access.
S 4 Deposit failed, cardholder
does not have access to
envelope
field coded in the
to make a shutdown
decision.
346 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
M-status and 01 Transport jam
M-data 02 Transport jam and shutter
jammed open
03 Transport jam and shutter

jammed closed
04 Shutter jammed open
05 Shutter jammed closed
06 Transport sensor failure
07 Communication failure
within the atm
08 Invalid device print head
status
09 Invalid device module
status
10 Deposit not done, error
count exceeded
11 Deposit bin overfill
13 Timing disk failure
15 Transport motor failure
50 Anti fishing sensor error
51 Motor speed too fast
52 Print head removed
55 Interlock failed
Supplies Status 1 0 no envelope deposited
1 no overfill condition
4 overfill detected
U25604-J-Z745-1-7600 October 2004 347

Envelope Dispenser (unsolicited) (DID ‘\’
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.

Characters Unsol.
Device Identifier 1 \ indicates a depository
message.
Device Status. 1 U 0 Envelope presentation
Indicates whether successful
the last transaction
was successful 1 Failure - envelope not
presented or retracted
field coded in the
to make a shutdown
decision.
M-status and 01 Transport jam before exit
M-data sensor
02 Transport jam at exit
sensor
03 Exit sensor failure
shutter jammed open
04 Bin low sensor failure
05 Timing disk sensor failure
06 Bin is low and failed to
present, EMPTY.
Supplies Status 1 1 Sufficient envelopes
2 Envelopes low
3 Envelopes exhausted
348 October 2004 U25604-J-Z745-1-7600

Receipt Printer (unsolicited) (DID ‘G’)

Characters Unsol.
Device Identifier 1 G Indicates a receipt printer
unsolicited message.
Transaction/ 1 U 0 Successful print

Device Status.
Indicates whether S 1 Print operation not
or not the print was successfully completed
successfully
completed. S 2 Device not configured
error severity 1 0-4 This is a single character
field coded in the
to make a shutdown
decision. See table “Error
severity table” for details.
M-status and 01 Head jam/ Knife jam
M-data 02 Failed to go not busy
03 Black mark error
04 Always saw the black
mark
05 Paper out
07 Paper not loaded or
Paper jam before
transport
08 Communication error
09 Printer open
10 Ribbon needs replaced
soon
11 Printhead needs replaced
soon
12 Knife needs replaced
soon
U25604-J-Z745-1-7600 October 2004 349


Characters Unsol.
now
now
15 Sideways communication
error
16 Eject jam
Supplies Status 1 CHAR CODE
0 1 Sufficient paper
2 Paper low
3 Paper exhausted
1 1 Ribbon o.k.
2 Ribbon replacement
recommended
mandatory
2 1 Printhead o.k.
2 Printhead replacement
recommended
mandatory
3 1 Knife o.k.
2 Knife replacement recom-
mended
350 October 2004 U25604-J-Z745-1-7600

Journal Printer (unsolicited) (DID ‘H’)

Characters Unsol.
Device Identifier 1 H Indicates a journal printer
Transaction/ 1 U 0 Successful print.

Device Status. S 1 Print operation not
Indicates whether successfully completed
or not the print was S 2 Device not configured
successfully
completed.
field coded in the
to make a shutdown
M-status and 01 Head jam/ Knife jam
M-data 02 Failed to go not busy
03 Black mark error
04 Always saw the black
mark
05 Paper out
07 Paper not loaded or
paper jam before
transport
08 Communication error
09 Printer open
soon
soon
12 Knife needs replaced
soon
U25604-J-Z745-1-7600 October 2004 351


Characters Unsol.
now
now
15 Sideways communication
error
16 Eject jam
2 Paper low
3 Paper exhausted
1 1 Ribbon o.k.
recommended
mandatory
2 1 Printhead o.k.
recommended
mandatory
352 October 2004 U25604-J-Z745-1-7600

Statement Printer (sol./unsol.) (DID ‘V’)

Characters Unsol.
Device Identifier 1 V Indicates a statement
printer sol./unsolicited
message.
Transaction/ 1 U 0 Successful print, but
Device Status. consult other fields for
In a solicited status Error Severity, diagnostic
it gives details of status or supplies status
any transaction change.
oriented faults. In S/U 1 Print / cut not successful
an unsolicited S 2 Device not configured
status it indicates a U 3 Statement present in
transport error or a transport
cut and deliver U 4 Cardholder pressed
error in the close cancel during a “print
state. statement and wait”
function
field coded in the
to make a shutdown
M-status and 01 Mechanical jam
M-data 02 Communication error
04 Black mark error
05 Media jam (fatal), or exit
sensor error (warning)
07 Paper out
now (Fatal)
soon (Warning)
U25604-J-Z745-1-7600 October 2004 353


Characters Unsol.
Diagnostic 2-16 09 Knife needs replaced
M-status and soon
M-data 10 Printhead needs replaced
now (Fatal)
soon (Warning)
11 Printer left open
16 Capture jam
17 Media removed by
customer during capture
18 Media stuck in throat,
unable to pull into printer -
possible customer
tampering
19 No paper present at start
of command
20 Printer malfunction -
paper present
21 Bin overfill
22 Print attempted beyond
end of media
23 Printer fatal
33 Buncher communica-
tions failure
34 Clamp drive jammed
open
35 Clamp drive jammed
open
36 Capture bin full
354 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
2 Paper low
3 Paper exhausted
1 1 Ribbon o.k.
recommended
mandatory
2 1 Printhead o.k.
recommended
mandatory
3 1 Knife o.k.
2 Knife replacement recom-
mended
3 Knife replacement
mandatory
4 1 Capture bin o.k.
4 Capture bin overfill
U25604-J-Z745-1-7600 October 2004 355

Vandal Guard (unsolicited) (DID ‘J’)

Characters Unsol.
Device Identifier 1 J Indicates a vandal guard
Device Status 1 U 1 Always ‘0’ for the vandal
guard.
field coded in the
to make a shutdown
M-status and 01 Failed to close
M-data 02 Failed to open
03 Jammed, position
undefined
356 October 2004 U25604-J-Z745-1-7600

EDM - Module (unsolicited) (DID ‘L’)

Characters Unsol.
Device Identifier 1 L Indicates an EDM -
module unsolicited
message.
Device Status 1 U 1 EDM error

2 EDM not configured
field coded in the
to make a shutdown
M-status and 01 Parity error
M-data 02 Hardware error
03 Key transport error
04 No key
05 Invalid command as
keyboard is currently
enabled
07 Communication failure
08 Security module reset
was successful
11 Invalid command data
12 data mismatch
13 No key loaded in DEU
prior to requesting an
encr. or decr. operation
U25604-J-Z745-1-7600 October 2004 357


Characters Unsol.
15 Set up failure - key space
ID1 already exists and is
not a programmer parent
with E/D attribute and 17
keys
16 Invalid keyspace ID
format, outside 0 -15.
17 Keyspace already exists.
18 Keyspace does not exist
19 Keyspace ID1 has wrong
attribute or class.
20 Keyspace ID2 has wrong
attribute or class.
22 Invalid keyspace, wrong
access right
23 Only two RAR access
spaces allowed,
keyspace not created
24 Secret keyspace creation

disabled.
25 Keyspace is not a parent.
26 Key ID2 not a keyspace
specified or keyspace
specified not a child of
key ID2 keyspace.
27 Invalid parent format.
28 Invalid parent ID,
keyspace not a parent or
keyspace does not exist.
29 Parent keyspace is a
programmer, can not
have secret child.
30 Key spaces do not match.
32 Key ID outside maximum
range of keys.
358 October 2004 U25604-J-Z745-1-7600


Characters Unsol.
33 Key ID1 has wrong
attribute.
34 Key ID2 has wrong
attribute.
37 Invalid key ID, no PIN

encryption allowed.
38 Invalid key, key does not
exist.
39 Key ID2 does not specify
an IV.
40 Invalid key ID, no key
41 Invalid key ID, key may
not be exclusively ORed
with key from different
keyspace.
48 Invalid attribute field.
49 Attribute already in family.
50 Invalid parameter field.
51 Undefined parameter for
keyspace class.
52 Variation index outside
range 01-7F hex.
53 Variation index already in
family.
54 Invalid mode for this
function.
55 Invalid left shift, value out
of range.
56 Invalid length, or length
and offset outside range.
57 Invalid access right.
58 Invalid POST PIN PAD
digit (> 0F hex).
59 Invalid PRE PIN PAD
data length (> 0C hex).
60 Modulus bit length > 576
or Exponent bit length >
576 or Modulus bit length
<= exonent bit length.
U25604-J-Z745-1-7600 October 2004 359


Characters Unsol.
64 Password does not
contain decimal digits
65 Invalid password, no
match.
66 Keyspace inaccessible,
password error count
exceeded.
70 PIN verification failed.
74 Invalid PIN encrypt type
function (encryption
mode changed).
75 Key integrity error.
76 Invalid PIN, no encryption
allowed (truncated PIN
does not contain decimal
digits).
97 Timeout error.
98 Communication error.
99 TC<>41, or TRS<>00 00
00 00, when decrypted.
360 October 2004 U25604-J-Z745-1-7600

Door Access (unsolicited) (DID ‘N’)

Characters Unsol.
Device Identifier 1 N Indicates a door access
Device Status 1 U 1 Always ‘1’ indicating that

access is possibly
inhibited.
Error Severity 1 2 Always ‘2’ indicating a
warning. Local inter-
vention required.
M-status and 01 Bad read error
M-data 02 Time-out error
03 Comms error
05 Not configured
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 No. of Char Code Detailed Definition

Characters
Device Identifier 1 P Indicates a Sensor status
message.
Device Status 13 1 ‘1’ ’TI’ sensor change
(characters 2-13 give
complete definition of all
sensors)
‘2’ Mode change (characters
3-13 are omitted)
‘3’ Alarm state change
If byte 1 = ’2’ 2 ‘0’ Supervisor mode exit
‘1’ Supervisor mode entry
If byte 1 = ’1’ 2 Not applicable
U25604-J-Z745-1-7600 October 2004 361


Characters
3 ‘0’ Vibration and/or heat
sensor inactive
‘1’ Vibration and/or heat
sensor active
4 ‘0’ Door has been closed
‘1’ Door has been opened
5 ‘0’ Silent signal sensor
inactive
Silent signal sensor
‘1’ active
6 ‘0’ Electronics enclosure
sensor inactive
‘1’ Electronics enclosure
sensor active
7 ‘0’ Deposit bin out
‘1’ Deposit bin in
8 ‘0’ Card bin out
‘1’ Card bin in
9 ‘0’ Currency reject bin out
‘1’ Currency reject bin in
10 ‘0’ Cassette in position 1 out
‘1’ Cassette in position 1 in
362 October 2004 U25604-J-Z745-1-7600

Supervisor Key Messages (unsolicited) (DID ‘R’)
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.

Chars
device identifier 1 R Indicates a Sensor status
message.
device status VAR 1-2 ’00’ - ’98’ Key selection from Select menu
(4 max)
or
1 ’0’ Select menu

’1’ Replenishment menu
’2’ Configure menu
’3’ Access menu
’4’ In Service Supervisor menu
’7’ Exit menu
’8’ Exit menu
2-3 ’00’ - ’98’ Menu item selected
or
1-2 ’00’ - ’98’ Host menu

3-4 Host function
U25604-J-Z745-1-7600 October 2004 363

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

Message Identifier 6 1
Message Modifier 1 1
Machine Number VAR 6
Date VAR 6
Time VAR 6
Last Char Previous Block VAR 6
Last Char This Block VAR 6
Block Length [:1C] 3
Response Data VAR 0-350
Message Identifier
Valid range: 6
of the Electronic Journal Upload message is 6.
364 October 2004 U25604-J-Z745-1-7600

Message Modifier
Valid range: 1
Description: This field specifies the message modifier.
The Message Modifier 1 indicates this message as Electronic
Journal Upload data.
Machine Number
Valid range: 000000-999999
Description: This field contains the machine number from the terminal.
Date
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
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

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

Last Char This Block

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 Printer Description

ND71 RECEIPT/JOURNAL dot matrix printer (obsolete)
ND99 THERMO RECEIPT printer (obsolete)
ND98 JOURNAL dot matrix printer
ND9A RECEIPT dot matrix printer
ND9E RECEIPT dot matrix printer
ND9C RECEIPT Thermal printer
ND9D JOURNAL Thermal printer
ND9G RECEIPT Thermal printer (only GDI interface)
TH30 JOURNAL Thermal printer
TH21 RECEIPT Thermal printer (optional with GDI interface)
TH23 STATEMENT Thermal printer (optional with GDI interface)
TH97 STATEMENT dot matrix printer
TH97/G STATEMENT Thermal printer (optional with GDI interface)
TP01 STATEMENT Thermal printer (optional with GDI interface)
TP07 RECEIPT Thermal printer (optional with GDI interface)
TP06 JOURNAL dot matrix printer (optional with GDI interface)
NP07 RECEIPT dot matrix printer
NP06 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 ASCII Short Description

Character Code
LF 0AH Line Feed, causes the next graphic character to be
printed on the next line.
FF 0CH Causes a feed to the next TOF mark or feed to the
maximum receipt length, cut and deliver to
customer.
SO 0EH 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 No. of spaces

1-9 1-9
: 10
; 11
< 12
= 13
> 14
? 15
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.
ESC (1 1B (1 sets Single Alpha 1 char set size (10 CPI)
ESC (2 1B (2 sets Single Alpha 2 char set size (10 CPI) see Note
ESC (7 1B (7 sets Single Alpha 3 char set size (10 CPI) see Note
ESC (> 1B (> sets Double Alpha 1 char set (5 CPI)
ESC (? 1B (? sets Double Alpha 2 char set size (5 CPI)
ESC (B 1B (B sets Double Alpha 3 char set size (5 CPI)
ESC (C 1B (C sets Condensed Alpha 1 char set size (17 CPI)
368 October 2004 U25604-J-Z745-1-7600

Printers Electronic journal
Control ASCII Short Description

Character Code
ESC (D 1B (D sets Condensed Alpha 2 char set size (17 CPI)
ESC (E 1B (E sets Condensed Alpha 3 char set size (17 CPI)
ESC [pxxx 1B [pxxx left margin control
ESC [qxxx 1B [qxxx right margin control

ESC [rxx 1B [rxx lines per inch control
ESC %xxx 1B %xxx 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 - represents the current 4 digit year
MM - represents the current 2 digit month
DD - represents the current 2 digit day
.JRN - 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:

● 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 Additional Useful Information
Single Graphic 1
Single Graphic 2
Single Graphic 3
372 October 2004 U25604-J-Z745-1-7600

Additional Useful Information NDC Standard Character Sets
Single Alpha 1
Single Alpha 2
U25604-J-Z745-1-7600 October 2004 373

NDC Standard Character Sets Additional Useful Information
Double Arabic
Double Alpha 1
374 October 2004 U25604-J-Z745-1-7600

Additional Useful Information NDC Standard Character Sets
Double Alpha 2
Chinese 1
Chinese 2
U25604-J-Z745-1-7600 October 2004 375

ASCII to EBCDIC Code Conversion Table Additional Useful Information
ASCII to EBCDIC Code Conversion Table

GRAPHIC ASCII (HEX) EBCDIC (HEX) GRAPHIC ASCII (HEX) EBCDIC (HEX)
NUL 00 00 SPACE 20 40
SOH 01 01 ! 21 4F
STX 02 02 " 22 7F
ETX 03 03 # 23 7B
EOT 04 37 $ 24 5B
ENQ 05 2D % 25 6C
ACK 06 2E & 26 50
BEL 07 2F 27 7D
BS 08 16 ( 28 4D
HT 09 05 ) 29 5D
LF 0A 15 * 2A 5C
VT 0B 0B + 2B 4E
FF 0C 0C , 2C 6B
CR 0D 0D - 2D 60
SO 0E 0E . 2E 4B
SI 0F 0F / 2F 61
DLE 10 10 0 30 F0
DC1 11 11 1 31 F1
DC2 12 12 2 32 F2
DC3 13 13 3 33 F3
DC4 14 3C 4 34 F4
NAK 15 3D 5 35 F5
SYN 16 32 6 36 F6
ETB 17 26 7 37 F7
CAN 18 18 8 38 F8
EM 19 19 9 39 F9
SUB 1A 3F : 3A 7A
ESC 1B 27 ; 3B 5E
376 October 2004 U25604-J-Z745-1-7600

Additional Useful Information ASCII to EBCDIC Code Conversion Table
FS 1C 1C < 3C 4C
GS 1D 1D = 3D 7E
RS 1E 1E > 3E 6E
US 1F 1F ? 3F 6F
@ 40 7C ' 60 Undefined
A 41 C1 a 61 81
B 42 C2 b 62 82
C 43 C3 c 63 83
D 44 C4 d 64 84
E 45 C5 e 65 85
F 46 C6 f 66 86
G 47 C7 g 67 87
H 48 C8 h 68 88
I 49 C9 i 69 89
J 4A D1 j 6A 91
K 4B D2 k 6B 92
L 4C D3 l 6C 93
M 4D D4 m 6D 94
N 4E D5 n 6E 95
O 4F D6 o 6F 96
P 50 D7 p 70 97
Q 51 D8 q 71 98
R 52 D9 r 72 99
S 53 E2 s 73 A2
T 54 E3 t 74 A3
U 55 E4 u 75 A4
V 56 E5 v 76 A5
W 57 E6 w 77 A6
X 58 E7 x 78 A7
Y 59 E8 y 79 A8
U25604-J-Z745-1-7600 October 2004 377

Screen Design Worksheet Additional Useful Information
Z 5A E9 z 7A A9
[ 5B 4A { 7B C0
\ 5C E0 | 7C 6A
] 5D 5A } 7D D0
^ 5E 5F - 7E A1
_ 5F 6D DEL 7F 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 : ; < = > ? P Q R S T U V W
@
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
0
1
2
3
4
5
6
7
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 Sev. M- M- Status desription
Class Code Status Data INFO
0007 DEFA_W 2 09 00000000000000000000 ”DISPENSER V1: Default warning if no CSCW32 error found”
0007 DEFA_E 4 09 00000000000000000000 ”DISPENSER V1: Default error if no CSCW32 error found”
0007 0100_E 2 03 00002727272700000000 ”DISPENSER V1: No cash in collecting tray”
0007 0200_E 2 09 00000000000000000000 ”DISPENSER V1: Transport direction illegal”
0007 0300_E 2 08 00000000000000000000 ”DISPENSER V1: Remaining capacity of reject bin to small”
0007 0400_E 2 09 00000000000000000000 ”DISPENSER V1: Syntax error in job”
0007 1000_E 2 09 00000000000000000000 ”DISPENSER V1: Incorrect block length, error in job”
0007 1100_E 2 09 00000000000000000000 ”DISPENSER V1: Incorrect device specification, error in job”
0007 1200_E 2 09 00000000000000000000 ”DISPENSER V1: Wrong job specification”
0007 1300_E 2 09 00000000000000000000 ”DISPENSER V1: Incorrect job length”
0007 1400_E 2 09 00000000000000000000 ”DISPENSER V1: Addressed cassette does not exist”
0007 1500_E 2 09 00000000000000000000 ”DISPENSER V1: Attempt to read from an unknown area”
0007 1600_E 2 09 00000000000000000000 ”DISPENSER V1: Field name in job unknown”
0007 1700_E 2 09 00000000000000000000 ”DISPENSER V1: Syntax error in job”
0007 1800_E 2 09 00000000000000000000 ”DISPENSER V1: Invalid transport destination”
0007 1900_E 2 09 00000000000000000000 ”DISPENSER V1: Illegal separator used in the job”
0007 1A00_E 2 09 00000000000000000000 ”DISPENSER V1: A job was previously issued and is still busy”
0007 1B00_E 2 09 00000000000000000000 ”DISPENSER V1: Attempt to write to protected cass. EEPROM”
0007 1C00_E 2 09 00000000000000000000 ”DISPENSER V1: There is no PUT PROM in the cash-out controller”
U25604-J-Z745-1-7600 October 2004 379

CSC-W32 Error Classes M-Status & M-Data Reference Tables

0007 1D00_E 2 09 00000000000000000000 ”DISPENSER V1: Illegal specification transferred in SV job”
0007 2000_E 2 03 00000303030300000000 ”DISPENSER V1: Amount demanded cannot be dispensed”
0007 2100_E 2 05 00000000000000000000 ”DISPENSER V1: Time-out in photosensor of measuring station”
0007 2200_E 2 05 00000000000000000000 ”DISPENSER V1: Time-out photosensor L1”
0007 2300_E 2 05 00000000000000000000 ”DISPENSER V1: Time-out for collecting tray photosensor L19”
0007 2400_E 2 05 00000000000000000000 ”DISPENSER V1: Time-out in photosensor L20 for reject cassette”
0007 2500_E 2 07 00000000000000000000 ”DISPENSER V1: Single reject switch defective”
0007 2600_E 2 02 00000000000000000000 ”DISPENSER V1: All banknotes were identified as multiple dispenses”
0007 2700_E 2 03 00000000000000000000 ”DISPENSER V1: The dispenser module is defective”
0007 2800_E 2 04 00000000000000000000 ”DISPENSER V1: Requested amount cannot be dispensed”
0007 2900_E 2 01 00000000000000000000 ”DISPENSER V1: no cassette for the requested currency”
0007 2A00_E 2 00 00000000000000000000 ”DISPENSER V1: parameter is larger than 40 banknotes”
0007 2B00_E 2 05 00000000000000000000 ”DISPENSER V1: Electronics of the photosensor amplifier defect”
0007 2C00_E 2 20 00000000000000000000 ”DISPENSER V1: Unknow device configuration”
0007 2D00_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L1,L17,L25”
0007 3100_E 2 05 00000000000000000000 ”DISPENSER V1: Times-out of path monitor in 1. dispenser module”
0007 3200_E 2 05 00000000000000000000 ”DISPENSER V1: Time-out of path monitor in 2. dispenser module”
0007 5000_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L17 blocked”
0007 5100_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L18 or L22 blocked”
0007 5110_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L18 does not become free”
0007 5118_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L18 is not reached”
0007 5700_E 2 05 00000000000000000000 ”DISPENSER V1: Does not reach the bottom Collecting tray swivel arm”
0007 5710_E 2 05 00000000000000000000 ”DISPENSER V1: Swivel arm does not reach the bottom”
0007 5800_E 2 05 00000000000000000000 ”DISPENSER V1: Collecting tray swivel arm does not reach the top”
0007 5810_E 2 05 00000000000000000000 ”DISPENSER V1: Swivel arm does not reach the top position”
0007 5B00_E 2 05 00000000000000000000 ”DISPENSER V1: Money slot/shutter does not close completely”
0007 5B10_E 2 05 00000000000000000000 ”DISPENSER V1: Shutter was not closed completely”
0007 5C00_E 2 05 00000000000000000000 ”DISPENSER V1: Money slot/shutter does not open completely”
0007 5C10_E 2 05 00000000000000000000 ”DISPENSER V1: Shutter was not open completely”
0007 5C11_E 2 05 00000000000000000000 ”DISPENSER V1: Shutter was not completely open”
0007 5D00_E 2 05 00000000000000000000 ”DISPENSER V1: Money does not reach L17”
0007 5D10_E 2 05 00000000000000000000 ”DISPENSER V1: Transport motor M2 does not return timing pulses”
0007 5D11_E 2 05 00000000000000000000 ”DISPENSER V1: Transport motor M2 does not return timing pulses”
0007 5F10_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L25 blocked”
380 October 2004 U25604-J-Z745-1-7600

M-Status & M-Data Reference Tables CSC-W32 Error Classes

0007 5F11_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L25 does not become free”
0007 5F18_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L25 is not reached”
0007 5F19_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L25 is not reached”
0007 6300_E 2 05 00000000000000000000 ”DISPENSER V1: Money does not reach L21”
0007 6318_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L21 not reached”

0007 7010_E 2 05 00000000000000000000 ”DISPENSER V1: Correct performed retract after TIMEOUT”
0007 7012_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L26 unexpectedly covered”
0007 7019_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L26 already free before retract”
0007 7110_E 2 05 00000000000000000000 ”DISPENSER V1: Correct retract performed after TIMEOUT”
0007 7119_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor L27 becomes free nevertheless”
0007 7B10_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor G9 is not reached”
0007 7B11_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor G9 is not reached”
0007 7C10_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor G8 is not reached”
0007 7C11_E 2 05 00000000000000000000 ”DISPENSER V1: Photosensor G8 is not reached”
0007 8000_E 2 41 00000000000000000000 ”DISPENSER V1: Invalid cassette slot”
0007 8001_E 2 09 00000000000000000000 ”DISPENSER V1: Error in self-test”
0007 8002_E 2 09 00000000000000000000 ”DISPENSER V1: Internal error Possible hardware error”
0007 8004_E 2 09 00000000000000000000 ”DISPENSER V1: Error occurs only with coded V24 line to the CDM”
0007 8005_E 2 09 00000000000000000000 ”DISPENSER V1: DLL for SW encording, CSCEDSDLL, could not be
opened”
0007 8006_E 2 09 00000000000000000000 ”DISPENSER V1: Invalid CRC received with encoded line”
0007 8007_E 2 09 00000000000000000000 ”DISPENSER V1: Keyword specified in parameter block has invalid
length”
0007 8009_E 2 09 00000000000000000000 ”DISPENSER V1: The segment selector is invalid”
U25604-J-Z745-1-7600 October 2004 381


0007 9000_E 2 09 00000000000000000000 ”DISPENSER V1: Time-out during comm. with measuring station”
0007 9100_E 2 09 00000000000000000000 ”DISPENSER V1: Time-out during comm. with photosensor amplifier”
0007 9200_E 2 09 00000000000000000000 ”DISPENSER V1: Customer relay not connected”
0007 B000_E 2 09 00000000000000000000 ”DISPENSER V1: Error when releasing the cassette”
0007 B100_E 2 09 00000000000000000000 ”DISPENSER V1: Error when initiating the cassette”
0007 B200_E 2 09 00000000000000000000 ”DISPENSER V1: No reject cassette”
0007 B300_E 2 07 00000000000000000000 ”DISPENSER V1: There is no dispensing cassette”
0007 B400_E 2 09 00000000000000000000 ”DISPENSER V1: Time-out at cassette initialization/release”
0007 B510_E 2 09 00000000000000000000 ”DISPENSER V1: EE-PROM defect”
0007 B511_E 2 09 00000000000000000000 ”DISPENSER V1: Main motor is not working”
0007 B512_E 2 09 00000000000000000000 ”DISPENSER V1: Incorrect motor speed”
0007 B513_E 2 09 00000000000000000000 ”DISPENSER V1: Hardware error (processor)”
0007 B514_E 2 09 00000000000000000000 ”DISPENSER V1: Hardware error (E-PROM)”
0007 B523_E 2 09 00000000000000000000 ”DISPENSER V1: Cassette busy (pressure being accumulated)”
0007 B530_E 2 09 00000000000000000000 ”DISPENSER V1: Reject position cannot be reached”
0007 B531_E 2 09 00000000000000000000 ”DISPENSER V1: Reject position cannot be reached”
0007 B534_E 2 09 00000000000000000000 ”DISPENSER V1: Processor defect”
0007 B535_E 2 09 00000000000000000000 ”DISPENSER V1: RAM defect”
0007 B536_E 2 09 00000000000000000000 ”DISPENSER V1: Checksum error, E-PROM”
0007 B537_E 2 09 00000000000000000000 ”DISPENSER V1: Checksum error, EE-PROM”
0007 B538_E 2 09 00000000000000000000 ”DISPENSER V1: Clutch signal error”
0007 B539_E 2 09 00000000000000000000 ”DISPENSER V1: Dispensing sensor error”
0007 B544_E 2 09 00000000000000000000 ”DISPENSER V1: Evaluation electronics defect”
0007 B545_E 2 09 00000000000000000000 ”DISPENSER V1: Card is not in a device”
0007 B546_E 2 09 00000000000000000000 ”DISPENSER V1: Device could not be identified”
0007 B547_E 2 09 00000000000000000000 ”DISPENSER V1: Job currently not allowed”
0007 B548_E 2 09 00000000000000000000 ”DISPENSER V1: Job unknown”
0007 B600_E 2 09 00000000000000000000 ”DISPENSER V1: Area/subarea selected does not exist”
0007 B700_E 2 09 00000000000000000000 ”DISPENSER V1: No free block”
0007 B800_E 2 09 00000000000000000000 ”DISPENSER V1: Area selected already exists”
0007 B900_E 2 09 00000000000000000000 ”DISPENSER V1: Character cannot be written”
0007 BA00_E 2 09 00000000000000000000 ”DISPENSER V1: Attempt to write to a write-protected area”
0007 BB00_E 2 09 00000000000000000000 ”DISPENSER V1: Error during processing of the cassette EE-PROM”
0007 BC00_E 2 09 00000000000000000000 ”DISPENSER V1: Required area cannot be dissolved”
0007 BD00_E 2 09 00000000000000000000 ”DISPENSER V1: Old password incorrect”
0007 BE00_E 2 09 00000000000000000000 ”DISPENSER V1: Syntax error in job”
0007 C000_E 2 09 00000000000000000000 ”DISPENSER V1: Cash cannot be dispensed from the selected cassette”
0007 C100_E 2 09 00000000000000000000 ”DISPENSER V1: Cash cannot dispensed from cassette”
0007 C200_E 2 09 00000000000000000000 ”DISPENSER V1: Hardware lock”
0007 C300_E 2 09 00000000000000000000 ”DISPENSER V1: Cannot determine reference value”
0007 C400_E 2 09 00000000000000000000 ”DISPENSER V1: Number of banknotes too high for reference value”
0007 C500_E 2 09 00000000000000000000 ”DISPENSER V1: Not possible to determine the reference value”
0007 C600_E 2 09 00000000000000000000 ”DISPENSER V1: Not possible to accumulate the data-specific pressure”
0007 D000_E 2 09 00000000000000000000 ”DISPENSER V1: The transport key is missing”
0007 D100_E 2 09 00000000000000000000 ”DISPENSER V1: The line key is missing”
0007 D200_E 2 09 00000000000000000000 ”DISPENSER V1: The safe door is not open”
0007 D300_E 2 09 00000000000000000000 ”DISPENSER V1: CODE TEST application command not possible”
0007 D400_E 2 09 00000000000000000000 ”DISPENSER V1: Key test not possible, because encryption is off”
0007 D500_E 2 09 00000000000000000000 ”DISPENSER V1: This message occurs in the dialog”
0007 D600_E 2 09 00000000000000000000 ”DISPENSER V1: This error occurs in the dialog”
382 October 2004 U25604-J-Z745-1-7600

Cash Dispenser NG (Classes: 0018/AA18/001D)
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 DEFA_W 2 00 00000000000000000000 "DISPENSER NG: DEFAULT_WARNING"
0018 DEFA_E 4 00 00000000000000000000 "DISPENSER NG: DEFAULT_ERROR"
0018 E000_W 2 19 00000000000000000000 "DISPENSER NG: No banknotes taken by the customer"
0018 E000_E 2 19 00000000000000000000 "DISPENSER NG: No banknotes taken by the customer"
0018 E001_W 1 34 00000000000000000000 "DISPENSER NG: All banknotes taken by the customer"
0018 E001_E 1 34 00000000000000000000 "DISPENSER NG: All banknotes taken by the customer"
0018 E002_W 1 09 00000000000000000000 "DISPENSER NG: Firmware on disk is newer than SW loaded in CDM-
NG"
0018 E002_E 1 09 00000000000000000000 "DISPENSER NG: Firmware on disk is newer than SW loaded in CDM-
NG"
0018 E003_W 1 09 00000000000000000000 "DISPENSER NG: There is no firmware loaded in the CDM-NG"
0018 E003_E 1 09 00000000000000000000 "DISPENSER NG: There is no firmware loaded in the CDM-NG"
0018 E004_W 1 00 00000000000000000000 "DISPENSER NG: DH configured to switch LEDs"
0018 E004_E 0 00 00000000000000000000 "DISPENSER NG: DH configured to switch LEDs"
0018 E005_W 2 05 00000000000000000000 "DISPENSER NG: Handling error at the filling tray"
0018 E005_E 2 05 00000000000000000000 "DISPENSER NG: Handling error at the filling tray"
0018 EF00_E 4 09 00000000000000000000 "DISPENSER NG: V24 data not in the expected format"
0018 EF01_E 1 09 00000000000000000000 "DISPENSER NG: Invalid CRC received with encrypted line"
0018 EF02_E 1 09 00000000000000000000 "DISPENSER NG: Wrong value for FRM_AUTO_LOAD in CSCCNG
section"
0018 EF03_E 1 09 00000000000000000000 "DISPENSER NG: Wrong value for LED in CSCINI/Registry with CSC-
CNG"
0018 EF04_E 1 09 00000000000000000000 "DISPENSER NG: Firmware loading could not be completed"
0018 F000_E 1 09 00000000000000000000 "DISPENSER NG: Firmware not loaded in CDM-NG"
0018 F001_E 4 09 00000000000000000000 "DISPENSER NG: Wrong syntax"
0018 F002_E 2 09 00000000000000000000 "DISPENSER NG: One of the locks is active"
0018 F003_E 2 09 00000000000000000000 "DISPENSER NG: Error occured during execution of command"
0018 F004_E 2 00 00000000000000000000 "DISPENSER NG: Safe door must be open for this command"
0018 F005_E 4 09 00000000000000000000 "DISPENSER NG: The command cannot be executed at this point of time"
0018 F006_E 2 09 00000000000000000000 "DISPENSER NG: The CDM-NG recognized a problem with the encryp-
tion"
0018 F007_E 2 11 00000000000000000000 "DISPENSER NG: If no error found"
0018 F012_E 4 11 00000000000000000000 "DISPENSER NG: Same error as CNG_FRM_DEVICE_NOT_READY"
0018 F013_E 2 09 00000000000000000000 "DISPENSER NG: The same error as CNG_FRM_ERROR with an excep-
tion"
0018 F015_E 2 09 00000000000000000000 "DISPENSER NG: The same error as CNG_FRM_CONTEXT with an
exception"
0018 FE06_E 4 09 00000000000000000000 "DISPENSER NG: COMM reports invalid spec. for the protocol"
0018 FE07_E 4 09 00000000000000000000 "DISPENSER NG: A COMM WRITE command is cancelled by the user"
0018 FE08_E 4 09 00000000000000000000 "DISPENSER NG: COMM WRITE command could not be executed"
0018 FE09_E 4 09 00000000000000000000 "DISPENSER NG: A COMM READ command could not be executed"
0018 FE0A_E 4 09 00000000000000000000 "DISPENSER NG: A COMM READ command is cancelled by the user"
0018 FE0B_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver reports a parity error"
0018 FE0C_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver reports a general error"
0018 FE0F_E 4 09 00000000000000000000 "DISPENSER NG: Peripheral device did not answer"
0018 FE13_E 4 09 00000000000000000000 "DISPENSER NG: The channel was not initialized"
0018 FE16_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver reports a break"
0018 FE7A_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver reports a overrun error"
0018 FE7B_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver reports a frameing error"
0018 FE85_E 4 09 00000000000000000000 "DISPENSER NG: The COMM driver could not be opened"
U25604-J-Z745-1-7600 October 2004 383


0018 FE89_E 4 09 00000000000000000000 "DISPENSER NG: The pointer pTxData is illegal"
0018 FE8B_E 4 09 00000000000000000000 "DISPENSER NG: Called function is invalid for CscCommOpen"
0018 FE8C_E 4 09 00000000000000000000 "DISPENSER NG: The peripheral device does not return an STX"
0018 FE8D_E 4 09 00000000000000000000 "DISPENSER NG: The peripheral device does not return an ETX"
0018 FE8E_E 4 09 00000000000000000000 "DISPENSER NG: Block length does not agree with the transmitted block
length"
0018 FE8F_E 4 09 00000000000000000000 "DISPENSER NG: The block ID is invalid"
0018 FE90_E 4 09 00000000000000000000 "DISPENSER NG: Received DID does not agree with the transmitted
DID"
0018 FE91_E 4 09 00000000000000000000 "DISPENSER NG: Wrong command specification"
0018 FE92_E 4 09 00000000000000000000 "DISPENSER NG: The received acknowledge type is invalid"
0018 FE93_E 4 09 00000000000000000000 "DISPENSER NG: Max no of repeat transmissions reached"
0018 FE94_E 4 09 00000000000000000000 "DISPENSER NG: Max no of receive repeats has been reached"
0018 FE95_E 4 09 00000000000000000000 "DISPENSER NG: Monitoring time during transmission has been
exceeded"
0018 FE96_E 4 09 00000000000000000000 "DISPENSER NG: Monitoring time during receive has been exceeded"
0018 FE97_E 4 09 00000000000000000000 "DISPENSER NG: Busy time from phys. device excceeded"
0018 FE98_E 4 09 00000000000000000000 "DISPENSER NG: The protocol was cancelled"
0018 FE9C_E 4 09 00000000000000000000 "DISPENSER NG: The length in TxData is 0"
0018 FE9D_E 4 09 00000000000000000000 "DISPENSER NG: CSCWISODLL could not be found in the PATH"
0018 FE9E_E 4 09 00000000000000000000 "DISPENSER NG: The CSCWISODLL could not be opened"
0018 FEE0_E 4 09 00000000000000000000 "DISPENSER NG: The peripheral device did not answer"
0018 FEE1_E 4 09 00000000000000000000 "DISPENSER NG: Peripheral device did not answer as expected"
0018 FEE2_E 4 09 00000000000000000000 "DISPENSER NG: The peripheral device is busy"
0018 FEE3_E 4 09 00000000000000000000 "DISPENSER NG: Peripheral device did not answer as expected"
0018 FEE4_E 4 09 00000000000000000000 "DISPENSER NG: Max no. of repeat transmissions reached"
0018 FEE5_E 4 09 00000000000000000000 "DISPENSER NG: Device asked for termination"
0018 FEE6_E 4 09 00000000000000000000 "DISPENSER NG: Peripheral device did not answer"
0018 FEE7_E 4 09 00000000000000000000 "DISPENSER NG: Response of device not completely received"
0018 FEE8_E 4 09 00000000000000000000 "DISPENSER NG: The header of the response is invalid"
0018 FEE9_E 4 09 00000000000000000000 "DISPENSER NG: DID does not agree with the transmitted DID"
0018 FEEA_E 4 09 00000000000000000000 "DISPENSER NG: DID does not agree with the transmitted device ID"
0018 FEEB_E 4 09 00000000000000000000 "DISPENSER NG: Command spec. does not agree with the transmitted
command spec."
0018 FEEC_E 4 09 00000000000000000000 "DISPENSER NG: The response of the device has not been completely
received"
0018 FEED_E 4 09 00000000000000000000 "DISPENSER NG: A cancel command has been called"
0018 FEEF_E 4 09 00000000000000000000 "DISPENSER NG: A cancel command has been called"
0018 FEF0_E 4 09 00000000000000000000 "DISPENSER NG: The command could not be executed"
0018 FEF1_E 4 09 00000000000000000000 "DISPENSER NG: The command was aborted by the user"
0018 FEF2_E 4 09 00000000000000000000 "DISPENSER NG: The command could not be executed"
0018 FEF3_E 4 09 00000000000000000000 "DISPENSER NG: A cancel command could not be executed"
0018 FEF4_E 4 09 00000000000000000000 "DISPENSER NG: Internal monitoring time exceeded"
0018 FEF5_E 4 09 00000000000000000000 "DISPENSER NG: Internal error within the CSCWISODLL"
AA18 DEFA_W 4 09 00000000000000000000 "USB/CDM: DEFAULT_WARNING"
AA18 DEFA_E 4 09 00000000000000000000 "USB/CDM: DEFAULT_ERROR"
AA18 8000_E 4 09 00000000000000000000 "USB/CDM: Unexpected descriptor was reported from USB device"
AA18 8001_E 4 09 00000000000000000000 "USB/CDM: Device not found"
AA18 8002_E 4 09 00000000000000000000 "USB/CDM: Not enough memory available"
AA18 8003_E 4 09 00000000000000000000 "USB/CDM: It was no endpoint found in the descriptor"
AA18 8004_E 4 09 00000000000000000000 "USB/CDM: The creation of the list of USB devices failed"
AA18 FE09_E 4 09 00000000000000000000 "USB/CDM: USB read command could not be executed in the specified
monitoring time"
AA18 FE0A_E 4 09 00000000000000000000 "USB/CDM: USB READ command is cancelled by the user"
AA18 FE89_E 4 09 00000000000000000000 "USB/CDM: The pointer pData is illegal"
AA18 FE9C_E 4 09 00000000000000000000 "USB/CDM: The length in DataSize is 0 (zero)"
AA18 0001_E 4 09 00000000000000000000 "USB/CDM: CRC error has been detected"
AA18 0002_E 4 09 00000000000000000000 "USB/CDM: Bit stuffing error has been detected"
AA18 0003_E 4 09 00000000000000000000 "USB/CDM: DATA toggle mismatch has been detected"
AA18 0004_E 4 09 00000000000000000000 "USB/CDM: STALLPID has been detected, error is reported by the USB
host controller"
AA18 0005_E 4 09 00000000000000000000 "USB/CDM: USB device is not responding, error is reported by the USB
host"
384 October 2004 U25604-J-Z745-1-7600


AA18 0006_E 4 09 00000000000000000000 "USB/CDM: PID check has failed, error is reported by the USB host con-
troller"
AA18 0007_E 4 09 00000000000000000000 "USB/CDM: Unexpected PID detected, error is reported by the USB host"
AA18 0008_E 4 09 00000000000000000000 "USB/CDM: Data overrun error detected, error is reported by the USB
host"
AA18 0009_E 4 09 00000000000000000000 "USB/CDM: Data underrun error detected, error is reported by the USB
host"
AA18 000A_E 4 09 00000000000000000000 "USB/CDM: Error code is reserved by the USB host controller driver"
AA18 000B_E 4 09 00000000000000000000 "USB/CDM: Error code is reserved by the USB host controller driver"
AA18 000C_E 4 09 00000000000000000000 "USB/CDM: Buffer overrun has been detected, error is reported by the
USB host"
AA18 000D_E 4 09 00000000000000000000 "USB/CDM: Buffer underrun has been detected, error is reported by the
USB host"
AA18 000F_E 4 09 00000000000000000000 "USB/CDM: Buffer was not accessed, error is reported by the USB host"
AA18 0010_E 4 09 00000000000000000000 "USB/CDM: FIFO error has been detected, PCI bus latency was too long"
AA18 0011_E 4 09 00000000000000000000 "USB/CDM: XACT error has been detected, error is reported by the USB
host"
AA18 0012_E 4 09 00000000000000000000 "USB/CDM: Device is babbling, data transfer phase exceeds the USB
frame length"
AA18 0013_E 4 09 00000000000000000000 "USB/CDM: Data buffer error has been detected, error is reported by the
USB host"
AA18 0030_E 4 09 00000000000000000000 "USB/CDM: Endpoint has been halted by the USB bus driver USBD"
AA18 0100_E 4 09 00000000000000000000 "USB/CDM: Memory allocation attempt has failed, error is reported by the
USB bus"
AA18 0200_E 4 09 00000000000000000000 "USB/CDM: Invalid URB function code has been passed, error is reported
by the USB"
AA18 0300_E 4 09 00000000000000000000 "USB/CDM: Invalid parameter has been passed, error is reported by the
USB bus"
AA18 0400_E 4 09 00000000000000000000 "USB/CDM: There are data transfer requests pending for the device"
AA18 0500_E 4 09 00000000000000000000 "USB/CDM: Request has failed, error is reported by the USB bus driver
USBD"
AA18 0600_E 4 09 00000000000000000000 "USB/CDM: Invalid pipe handle has been passed, error is reported by the
USB bus"
AA18 0700_E 4 09 00000000000000000000 "USB/CDM: There is not enough bandwidth available, error is reported by
the USB bus"
AA18 0800_E 4 09 00000000000000000000 "USB/CDM: Internal host controller error has been detected"
AA18 0900_E 4 09 00000000000000000000 "USB/CDM: Short transfer has been detected, error is reported by the USB
bus"
AA18 0A00_E 4 09 00000000000000000000 "USB/CDM: Bad start frame has been specified, error is reported by the
USB bus"
AA18 0B00_E 4 09 00000000000000000000 "USB/CDM: Asynchronous request has failed, error is reported by the
USB bus driver"
AA18 0C00_E 4 09 00000000000000000000 "USB/CDM: USB frame control is currently owned, error is reported by
the USB bus"
AA18 0D00_E 4 09 00000000000000000000 "USB/CDM: USB frame control is currently not owned, error is reported
by the USB"
AA18 0E00_E 4 09 00000000000000000000 "USB/CDM: Operation is not supported, error is reported by the USB bus
driver"
AA18 0F00_E 4 09 00000000000000000000 "USB/CDM: Invalid configuration descriptor was reported by the device"
AA18 1000_E 4 09 00000000000000000000 "USB/CDM: Operation has failed, error is reported by the USBIO driver"
AA18 1001_E 4 09 00000000000000000000 "USB/CDM: Invalid input buffer has been passed to an IOCTL operation"
AA18 1002_E 4 09 00000000000000000000 "USB/CDM: Invalid output buffer has been passed to an IOCTL operation"
AA18 1003_E 4 09 00000000000000000000 "USB/CDM: There is not enough system memory available to complete
the operation"
AA18 1004_E 4 09 00000000000000000000 "USB/CDM: There are read or write requests pending, error is reported by
the USBIO"
AA18 1005_E 4 09 00000000000000000000 "USB/CDM: USB device is already configured, error is reported by the
USBIO"
AA18 1006_E 4 09 00000000000000000000 "USB/CDM: The USB device is not configured, error is reported by the
USBIO driver"
AA18 1007_E 4 09 00000000000000000000 "USB/CDM: There are open pipes, error is reported by the USBIO driver"
AA18 1008_E 4 09 00000000000000000000 "USB/CDM: Either the handle is already bound to a pipe"
AA18 1009_E 4 09 00000000000000000000 "USB/CDM: Handle is not bound to a pipe, error is reported by the USBIO
driver"
AA18 100A_E 4 09 00000000000000000000 "USB/CDM: USB device has been removed from the system"
AA18 100B_E 4 09 00000000000000000000 "USB/CDM: Specified control code is not supported"
U25604-J-Z745-1-7600 October 2004 385


AA18 100C_E 4 09 00000000000000000000 "USB/CDM: Operation has been timed out, error is reported by the USBIO
driver"
AA18 100D_E 4 09 00000000000000000000 "USB/CDM: Invalid recipient has been specified"
AA18 100E_E 4 09 00000000000000000000 "USB/CDM: Either an invalid request type has been specified"
AA18 100F_E 4 09 00000000000000000000 "USB/CDM: Invalid IOCTL code has been specified, error is reported by
the USBIO"
AA18 1010_E 4 09 00000000000000000000 "USB/CDM: Direction of the data transfer request is not supported by that
pipe"
AA18 1011_E 4 09 00000000000000000000 "USB/CDM: Number of asynchronous data packets specified in an asyn-
chronous read"
AA18 1012_E 4 09 00000000000000000000 "USB/CDM: Memory resources are exhausted. This error is reported by
the USBIO driver"
AA18 1013_E 4 09 00000000000000000000 "USB/CDM: The specified pipe was not found in the current configura-
tion"
AA18 1014_E 4 09 00000000000000000000 "USB/CDM: An invalid asynchronous data packet has been specified"
AA18 1015_E 4 09 00000000000000000000 "USB/CDM: There are not enough system resources to complete the oper-
ation"
AA18 1016_E 4 09 00000000000000000000 "USB/CDM: Specified interface was not found in the current configura-
tion"
AA18 1017_E 4 09 00000000000000000000 "USB/CDM: Operation cannot be executed while the USB device is in the
current state"
AA18 1018_E 4 09 00000000000000000000 "USB/CDM: Invalid parameter has been specified with an IOCTL opera-
tion"
AA18 1019_E 4 09 00000000000000000000 "USB/CDM: Evaluation interval of the USBIO DEMO version has
expired"
AA18 101A_E 4 09 00000000000000000000 "USB/CDM: Invalid power state has been specified"
AA18 101B_E 4 09 00000000000000000000 "USB/CDM: Device has entered a power down state"
AA18 101C_E 4 09 00000000000000000000 "USB/CDM: API version reported by the USBIO driver does not match"
AA18 101D_E 4 09 00000000000000000000 "USB/CDM: Set configuration operation has failed, error is reported by the
USBIO"
AA18 1080_E 4 09 00000000000000000000 "USB/CDM: Operation has failed due to a restriction of the USBIO
LIGHT version"
LIGHT version"
LIGHT version"
LIGHT version"
LIGHT version"
LIGHT version"
AA18 1086_E 4 09 00000000000000000000 "USB/CDM: The operation has failed due to a restriction of the USBIO
LIGHT version"
LIGHT version"
AA18 1100_E 4 09 00000000000000000000 "USB/CDM: The specified device object does not exist"
AA18 1102_E 4 09 00000000000000000000 "USB/CDM: Device object was opened, there is no valid handle to execute
the operation"
AA18 1104_E 4 09 00000000000000000000 "USB/CDM: Enumeration of the specified devices has failed"
AA18 1105_E 4 09 00000000000000000000 "USB/CDM: Invalid parameter has been passed to a function"
AA18 1106_E 4 09 00000000000000000000 "USB/CDM: Library setupapi.dll could not be loaded"
AA18 2000_E 4 09 00000000000000000000 "USB/CDM: Set configuration request has failed"
AA18 3000_E 4 09 00000000000000000000 "USB/CDM: Buffer is too small, error is reported by the USB bus driver
USBD"
AA18 4000_E 4 09 00000000000000000000 "USB/CDM: Interface was not found, error is reported by the USB bus
driver USBD"
AA18 5000_E 4 09 00000000000000000000 "USB/CDM: Invalid pipe flags have been specified"
AA18 6000_E 4 09 00000000000000000000 "USB/CDM: Operation has been timed out, error is reported by the USB
bus driver"
AA18 7000_E 4 09 00000000000000000000 "USB/CDM: USB device is gone, error is reported by the USB bus driver
USBD"
001D DEFA_W 2 09 00000000000000000000 "DISPENSER NG: DEFAULT_WARNING"
001D DEFA_E 4 09 00000000000000000000 "DISPENSER NG: DEFAULT_ERROR"
001D 1000_E 2 13 1000000000000000000 "DISPENSER FL: Context error, CDM has received an invalid command"
001D 1001_E 4 09 00000000000000000000 "DISPENSER FL: No response from the CDM"
001D 1010_E 4 09 00000000000000000000 "DISPENSER FL: CDM electronics faulty"
386 October 2004 U25604-J-Z745-1-7600


001D 1011_E 4 09 00000000000000000000 "DISPENSER FL: No firmware in CDM"
001D 1012_E 4 09 00000000000000000000 "DISPENSER FL: CDM not completely inserted"
001D 1013_E 4 00 00000000000000000000 "DISPENSER FL: Max number of retracts reached"
001D 1014_E 4 10 00000000000000000000 "DISPENSER FL: Minimum configuration not reached."
001D 1018_E 2 03 01100000000000000000 "DISPENSER FL: Note jam during dispensing"
001D 1019_E 2 12 00000000000000000000 "DISPENSER FL: Money jam in the output transport"
001D 1020_E 4 18 00000000000000000000 "DISPENSER FL: Single reject switch faulty/blocked"
001D 1021_E 4 05 00000000000000000000 "DISPENSER FL: Measuring station faulty"

001D 1022_E 4 05 00000000000000000000 "DISPENSER FL: Photosensor amplifier faulty"
001D 1023_E 4 11 00000000000000000000 "DISPENSER FL: Bundle reject switch faulty"
001D 1024_E 4 07 00000000000000000000 "DISPENSER FL: Reject/retract drive faulty/blocked"
001D 1025_E 2 09 00000000000000000000 "DISPENSER FL: Dispensing drive faulty"
001D 1026_E 2 05 00000000000000000000 "DISPENSER FL: Collecting tray defect"
001D 1028_E 2 05 00000000000000000000 "DISPENSER FL: Money slot/shutter jammed or cannot be opened"
001D 1029_E 3 13 00000000000000000000 "DISPENSER FL: Manipulation during delivery"
001D 1031_E 2 02 00000000000000000000 "DISPENSER FL: Too many bundle rejects (cassette 1)"
001D 1041_E 2 03 00000000000000000000 "DISPENSER FL: Note extraction impossible (cassette 1)"
001D 1051_E 2 02 00000000000000000000 "DISPENSER FL: Too many bad notes (cassette 1)"
001D 1061_E 2 09 00000000000000000000 "DISPENSER FL: EE-PROM error (cassette 1)"
001D 1070_E 2 05 00000000000000000000 "DISPENSER FL: Photosensor measuring station soiled"
001D 1071_E 2 05 00000000000000000000 "DISPENSER FL: Dispenser sensor soiled (cassette 1)"
001D 1081_E 2 05 00000000000000000000 "DISPENSER FL: Empty sensor soiled (cassette 1)"
001D 1090_E 2 05 00000000000000000000 "DISPENSER FL: Photosensor L1 soiled"
001D 1800_E 2 05 00000000000000000000 "DISPENSER V4: Context error, CDM has received an invalid command"
001D 1801_E 4 05 00000000000000000000 "DISPENSER V4: No response from CDM"
001D 1805_E 4 05 00000000000000000000 "DISPENSER V4: Communication problem with the chip card controller"
001D 1806_E 4 05 00000000000000000000 "DISPENSER V4: Communication problem with the chip card"
001D 1807_E 4 05 00000000000000000000 "DISPENSER V4: Hardware configuration not accepted"
U25604-J-Z745-1-7600 October 2004 387


001D 1808_E 4 05 00000000000000000000 "DISPENSER V4: Communication problem with the EE-PROM collector"
001D 1809_E 4 05 00000000000000000000 "DISPENSER V4: Service switch open, please insert CDM-V4 com-
pletely"
001D 1810_E 4 05 00000000000000000000 "DISPENSER V4: CMD electronics faulty"
001D 1811_E 4 05 00000000000000000000 "DISPENSER V4: Software missing in the CMD"
001D 1812_E 4 05 00000000000000000000 "DISPENSER V4: CMD has not been inserted completely"
001D 1813_E 4 00 00000000000000000000 "DISPENSER V4: The maximal number of retracts has been reached"
001D 1814_E 4 10 00000000000000000000 "DISPENSER V4: Minimum configuration missing"
001D 1817_E 2 09 00000000000000000000 "DISPENSER V4: Gripper belt drive faulty"
001D 1818_E 2 03 01100000000000000000 "DISPENSER V4: Note jam during dispensing"
001D 1819_E 2 09 00000000000000000000 "DISPENSER V4: Gripper transport defective or blocked"
001D 1820_E 4 05 00000000000000000000 "DISPENSER V4: Single reject switch faulty/blocked"
001D 1821_E 4 05 00000000000000000000 "DISPENSER V4: Measuring station faulty"
001D 1822_E 4 05 00000000000000000000 "DISPENSER V4: Photosensor amplifier faulty"
001D 1823_E 4 05 00000000000000000000 "DISPENSER V4: Circle switch faulty/blocked"
001D 1824_E 4 05 00000000000000000000 "DISPENSER V4: Reject/retract drive faulty/blocked"
001D 1825_E 4 05 00000000000000000000 "DISPENSER V4: Dispensing drive faulty/blocked"
001D 1826_E 4 05 00000000000000000000 "DISPENSER V4: Stacker drive faulty /blocked"
001D 1828_E 3 13 00000000000000000000 "DISPENSER V4: Money slot/shutter jammed or cannot be opened"
001D 1829_E 3 13 00000000000000000000 "DISPENSER V4: Manipulation during delivery"
001D 1831_E 2 02 00000000000000000000 "DISPENSER V4: Too many bundle rejects (cassette 1)"
001D 1841_E 2 03 00000000000000000000 "DISPENSER V4: Note extraction impossible (cassette 1)"
001D 1851_E 2 02 00000000000000000000 "DISPENSER V4: Too many bad notes (cassette 1)"
001D 1861_E 2 09 00000000000000000000 "DISPENSER V4: Cassette 1 faulty"
001D 1870_E 2 05 00000000000000000000 "DISPENSER V4: Photosensors measuring station soiled"
001D 1871_E 2 05 00000000000000000000 "DISPENSER V4: Dispenser sensor soiled (cassette 1)"
001D 1881_E 2 05 00000000000000000000 "DISPENSER V4: Empty sensor soiled (cassette 1)"
001D 1890_E 2 05 00000000000000000000 "DISPENSER V4: Photosensor L1 soiled"
001D 1891_E 2 05 00000000000000000000 "DISPENSER V4: Photosensor L18 soiled"
001D 1893_E 2 05 00000000000000000000 "DISPENSER V4: Control tray single reject L2 soiled"
001D 1895_E 2 05 00000000000000000000 "DISPENSER V4: Money taken light barrier L26/L27 soiled"
001D 1898_E 2 05 00000000000000000000 "DISPENSER V4: Withdrawal photosensor L27 soiled"
388 October 2004 U25604-J-Z745-1-7600


001D 1899_E 2 05 00000000000000000000 "DISPENSER V4: Output photosensor L28 soiled"
001D 189A_E 2 05 00000000000000000000 "DISPENSER V4: Light barrier of bundle back edge control (presenter)
soiled"
001D 189D_E 2 05 00000000000000000000 "DISPENSER V4: Light barrier L2 of reject bin soiled"
001D 189E_E 2 05 00000000000000000000 "DISPENSER V4: Light barrier L3 of reject bin soiled"
001D 4001_E 4 09 00000000000000000000 "DISPENSER NG: No response from the CDM"
001D 4010_E 4 09 00000000000000000000 "DISPENSER NG: CDM electronics faulty"
001D 4011_E 4 09 00000000000000000000 "DISPENSER NG: Software missing in the CDM"

001D 4012_E 4 09 00000000000000000000 "DISPENSER NG: CDM has not been inserted completely"
001D 4013_E 4 00 00000000000000000000 "DISPENSER NG: Max number of retracts reached"
001D 4018_E 2 03 01100000000000000000 "DISPENSER NG: Note jam during dispensing"
001D 4020_E 2 05 00000000000000000000 "DISPENSER NG: Single reject switch faulty/blocked"
001D 4021_E 4 05 00000000000000000000 "DISPENSER NG: Measuring station faulty"
001D 4022_E 4 05 00000000000000000000 "DISPENSER NG: Photosensor amplifier faulty"
001D 4025_E 2 03 00000000000000000000 "DISPENSER NG: Dispensing drive faulty/blocked"
001D 4026_E 2 03 00000000000000000000 "DISPENSER NG: Switching dispensing/transport"
001D 4100_E 2 05 00000000000000000000 "DISPENSER NG: Cassette unknown, missing, reinserted"
001D 4114_E 4 07 00000000000000000000 "DISPENSER NG: Reject cassette missing"
001D 4119_E 2 12 00000000000000000000 "DISPENSER NG: Money jam in the output transport"
001D 4123_E 4 12 00000000000000000000 "DISPENSER NG: Bundle reject switch faulty/blocked"
001D 4124_E 4 07 00000000000000000000 "DISPENSER NG: Reject/retract drive faulty/blocked"
001D 4128_E 2 12 00000000000000000000 "DISPENSER NG: Shutter cannot be opened/defect"
001D 4129_E 3 13 00000000000000000000 "DISPENSER NG: Manipulation during delivery"
001D 4200_E 3 14 00000000000000000000 "DISPENSER NG: Shutter has been blocked"
001D 4214_E 4 07 00000000000000000000 "DISPENSER NG: Reject cassette not logged on"
001D 4228_E 2 13 00000000000000000000 "DISPENSER NG: Shutter undefined"
001D 4229_E 3 18 00000000000000000000 "DISPENSER NG: Manipulation in withdrawal position"
001D 4300_E 2 13 00000000000000000000 "DISPENSER NG: Command cannot be executed while Shutter open"
001D 4314_E 2 01 00000000000000000000 "DISPENSER NG: Cash-out cassette(s) missing"
001D 4328_E 2 13 00000000000000000000 "DISPENSER NG: Shutter cannot be closed/undefined"
001D 4329_E 2 30 00000000000000000000 "DISPENSER NG: Manipulation during retract"
001D 4400_E 2 13 00000000000000000000 "DISPENSER NG: Command cannot be executed while Shutter unde-
fined"
001D 4414_E 2 40 00000000000000000000 "DISPENSER NG: No cash-out cassette(s) logged on"
001D 4428_E 2 30 00000000000000000000 "DISPENSER NG: Shutter undefined during retract"
001D 4500_E 2 18 00000000000000000000 "DISPENSER NG: Manipulation at cash-out photosensor"
001D 4600_E 2 05 00000000000000000000 "DISPENSER NG: Note paths blocked"
001D 4629_E 2 13 00000000000000000000 "DISPENSER NG: Manipulation in withdrawal position"
001D 4700_E 2 10 00000000000000000000 "DISPENSER NG: Max number of retracts reached"
001D 4729_E 2 13 00000000000000000000 "DISPENSER NG: Manipulation during retract"
001D 4800_E 2 02 00000000000000000000 "DISPENSER NG: Single reject switch faulty"
001D 4900_E 2 41 00000000000000000000 "DISPENSER NG: Self-test activated"
001D 4919_E 2 18 00000000000000000000 "DISPENSER NG: Photosensor covered during withdrawal"
001D 4A00_E 4 03 00000000000000000000 "DISPENSER NG: The jam was not eliminated effectively"
001D 4A19_E 2 18 00000000000000000000 "DISPENSER NG: Photosensor covered during withdrawal"
001D 4B00_E 2 01 00000000000000000000 "DISPENSER NG: Cash-out cassette missing"
001D 4B19_E 2 19 00000000000000000000 "DISPENSER NG: Photosensor covered during retract"
001D 4C19_E 4 29 00000000000000000000 "DISPENSER NG: Motor defect"
001D 4D00_E 2 04 00000000000000000000 "DISPENSER NG: Cassette is empty"
001D 4E00_E 2 01 00000000000000000000 "DISPENSER NG: Cassette or dispensing sensor defect"
001D 4F00_E 2 04 00000000000000000000 "DISPENSER NG: Cassette becomes empty during dispensing procedure"
U25604-J-Z745-1-7600 October 2004 389


001D 8031_E 2 02 00000000000000000000 "DISPENSER NG: Too many bundle rejects (cassette 1)"
001D 8041_E 2 03 00000000000000000000 "DISPENSER NG: Note extraction impossible (cassette 1)"
001D 8061_E 2 09 00000000000000000000 "DISPENSER NG: Cassette 1 faulty"
001D 8070_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor measuring station soiled"
001D 8071_E 2 05 00000000000000000000 "DISPENSER NG: Dispenser sensor soiled (cassette 1)"
001D 8081_E 2 05 00000000000000000000 "DISPENSER NG: Empty sensor soiled (cassette 1)"
001D 8090_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L1 soiled"
001D 809A_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L29 soiled"
001D 809B_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L36 soiled"
001D 809C_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L37 soiled"
001D 8151_E 2 02 00000000000000000000 "DISPENSER NG: Too many double notes (cassette 1)"
001D 8251_E 2 02 00000000000000000000 "DISPENSER NG: Too many bad notes (cassette 1)"
001D 8300_E 2 11 00000000000000000000 "DISPENSER NG: Bills left in stacker after output to diverter"
001D 8312_E 2 09 00000000000000000000 "DISPENSER NG: CDM has not been inserted completely"
001D 8313_E 2 11 00000000000000000000 "DISPENSER NG: Cash left in diverter after reset/booting"
001D 8314_E 2 11 00000000000000000000 "DISPENSER NG: Dispensing not possible"
001D 8315_E 2 11 00000000000000000000 "DISPENSER NG: Command could not be executed"
001D 8316_E 2 11 00000000000000000000 "DISPENSER NG: Command could not be executed"
390 October 2004 U25604-J-Z745-1-7600


001D 8318_E 2 11 00000000000000000000 "DISPENSER NG: Note jam during dispense operation"
001D 8319_E 2 11 00000000000000000000 "DISPENSER NG: Note jam in the output transport"
001D 8320_E 2 11 00000000000000000000 "DISPENSER NG: Single reject switch faulty/blocked"
001D 8321_E 2 05 00000000000000000000 "DISPENSER NG: Measuring station faulty"
001D 8322_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor amplifier faulty"
001D 8325_E 2 11 00000000000000000000 "DISPENSER NG: Dispensing drive faulty/blocked"

001D 8326_E 2 11 00000000000000000000 "DISPENSER NG: Switching dispensing/transport faulty"
001D 8328_E 2 05 00000000000000000000 "DISPENSER NG: Diverter does not reach the end position"
001D 8329_E 2 05 00000000000000000000 "DISPENSER NG: Bills jammed in stacker, under output photosensor"
001D 8331_E 2 02 00000000000000000000 "DISPENSER NG: Too many bundle rejects (casette 1)"
001D 8370_E 2 05 00000000000000000000 "DISPENSER NG: Photosensors measuring station soiled"
001D 839A_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L29 soiled"
001D 839B_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L36 soiled"
001D 839C_E 2 05 00000000000000000000 "DISPENSER NG: Photosensor L37 soiled"
001D 8400_E 2 05 00000000000000000000 "DISPENSER NG: Banknotes left in the stacker after output"
U25604-J-Z745-1-7600 October 2004 391


001D 8419_E 2 05 00000000000000000000 "DISPENSER NG: Note jam in the output transport"
001D A000_E 2 09 00000000000000000000 "DISPENSER NG: Wrong command"
001D A100_E 2 09 00000000000000000000 "DISPENSER NG: Wrong command"
001D A200_E 2 09 00000000000000000000 "DISPENSER NG: Programming error"
001D FE38_E 4 09 00000000000000000000 "DISPENSER NG: Communication problem"
001D FE50_E 4 09 00000000000000000000 "DISPENSER NG: Communication problem"
001D FFFF_E 2 09 00000000000000000000 "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)

Class Code INFO
Status Data
001A DEFA_E 2 00 0000000000000000000000 "CCDM: DEFAULT ERROR"
001A DEFA_W 2 00 0000000000000000000000 "CCDM: DEFAULT WARNING"
001A 0014_E 2 00 0000000000000000000000 "CCDM: General firmware error"
001A 0015_E 2 00 0000000000000000000000 "CCDM: Battery on controller board empty"
001A 0016_E 2 00 0000000000000000000000 "CCDM: Safety switch active"
001A 0017_E 2 00 0000000000000000000000 "CCDM: System interface does not fetch the data from the CCDM fast
enough"
001A 0018_E 2 00 0000000000000000000000 "CCDM: Invalid or missing configuration"
001A 001E_E 2 00 0000000000000000000000 "CCDM: Error magnetic character reader"
001A 0028_E 2 00 0000000000000000000000 "CCDM: Error cheque/cash reader"
001A 0029_E 2 00 0000000000000000000000 "CCDM: Firmware error cheque/cash reader"
001A 002A_E 2 00 0000000000000000000000 "CCDM: Communication problem cheque/cash reader"
001A 002B_E 2 00 0000000000000000000000 "CCDM: Data error cheque/cash reader"
001A 002C_E 2 00 0000000000000000000000 "CCDM: Note table configuration not Ok"
001A 002D_E 2 00 0000000000000000000000 "CCDM: External light in cheque/cash reader"
001A 002F_E 2 00 0000000000000000000000 "CCDM: Communication problems (time out)"
001A 0030_E 2 00 0000000000000000000000 "CCDM: Communication problems"
001A 0031_E 2 00 0000000000000000000000 "CCDM: Cheque/cash reader firmware and CCDM firmware are incom-
patible"
001A 003D_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS"
001A 003E_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS"
001A 003F_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS"
001A 0040_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS"
001A 0041_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS1"
001A 0042_E 2 00 0000000000000000000000 "CCDM: Error photosensor ALS"
001A 0046_E 2 00 0000000000000000000000 "CCDM: Error photosensor SLS"
001A 0047_E 2 00 0000000000000000000000 "CCDM: Error photosensor SLS"
001A 0048_E 2 00 0000000000000000000000 "CCDM: Error photosensor ELS"
001A 0049_E 2 00 0000000000000000000000 "CCDM: Error photosensor RLS"
001A 004A_E 2 00 0000000000000000000000 "CCDM: Error photosensor RLS"
001A 004B_E 2 00 0000000000000000000000 "CCDM: Error photosensor VLS1"
392 October 2004 U25604-J-Z745-1-7600


Class Code INFO
Status Data
001A 004C_E 2 00 0000000000000000000000 "CCDM: Error photosensor ELS"
001A 0050_E 2 00 0000000000000000000000 "CCDM: Error photosensor KLS"
001A 0053_E 2 00 0000000000000000000000 "CCDM: Error photosensor KLS1"
001A 0064_E 2 00 0000000000000000000000 "CCDM: Transport error detected before dispensing"
001A 0066_E 2 00 0000000000000000000000 "CCDM: VLS6: media too long (media do not pass (VLS6)"
001A 0067_E 2 00 0000000000000000000000 "CCDM: VLS7: medium is expected but no media is coming"
001A 0069_E 2 00 0000000000000000000000 "CCDM: VLS7: media do not leave VLS7"
001A 006A_E 2 00 0000000000000000000000 "CCDM: VLS6: media do not leave VLS6"
001A 006C_E 2 00 0000000000000000000000 "CCDM: Faulty extraction detected during dispensing process"
001A 006E_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media jam in the intermediary trans-
port"
001A 006F_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media jam in the I/O transport"
001A 0070_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media do not reached VLS"
001A 0071_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media jam in the separation area of the
dispense"
001A 0072_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media jam in the intermediary trans-
port"
001A 0073_E 2 00 0000000000000000000000 "CCDM: Clearing error I/O tray. Media jam in the intermediary trans-
port"
001A 0074_E 2 00 0000000000000000000000 "CCDM: Media jam in reject transport area"
001A 0078_E 2 00 0000000000000000000000 "CCDM: Initialization error hinged transport 1 and/or 2"
001A 0079_E 2 00 0000000000000000000000 "CCDM: Position error hingend transport 1. The end position is not
reached"
001A 007A_E 2 00 0000000000000000000000 "CCDM: Position error hinged transport 2. The end position is not
reached"
001A 0082_E 2 00 0000000000000000000000 "CCDM: Initialization error during setting the bundle width"
001A 008C_E 2 00 0000000000000000000000 "CCDM: Error on the cam disk"
001A 008D_E 2 00 0000000000000000000000 "CCDM: Error on the cam disk"
001A 0090_E 2 00 0000000000000000000000 "CCDM: Shutter cannot be opened/closed."
001A 0091_E 2 00 0000000000000000000000 "CCDM: Error on metal detection module"
001A 0096_E 2 00 0000000000000000000000 "CCDM: VHS1: hardware error thickness measuring station"
001A 0097_E 2 00 0000000000000000000000 "CCDM: VHS1: hardware error thickness measuring station"
001A 00AA_E 2 00 0000000000000000000000 "CCDM: Initialization error of reject transport"
001A 00B4_E 2 00 0000000000000000000000 "CCDM: Media jam in reject transport area"
001A 00B5_E 2 00 0000000000000000000000 "CCDM: Clearing error storage transport. Media did not passed VLS2"
001A 00C8_E 2 00 0000000000000000000000 "CCDM: Media in front oaf ALS1 or ALS1 defect"
001A 00C9_E 2 00 0000000000000000000000 "CCDM: ALS1: medium is expected but no media is coming"
001A 00CA_E 2 00 0000000000000000000000 "CCDM: ALS1: media too long (media do not pass the drum)"
001A 00CB_E 2 00 0000000000000000000000 "CCDM: ALS1: media is complete recognized but is too long"
001A 00CC_E 2 00 0000000000000000000000 "CCDM: ALS1: media jam in the drum"
001A 00CD_E 2 00 0000000000000000000000 "CCDM: ALS1: Media end is not detected during entering the drum"
001A 00CE_E 2 00 0000000000000000000000 "CCDM: ALS1: Media end do not detected during leaving the drum"
001A 012D_E 2 00 0000000000000000000000 "CCDM: Media jam in sensor transport at the 3-way deflector"
001A 012E_E 2 00 0000000000000000000000 "CCDM: Media jam in sensor transport at the reject deflector"
001A 0137_E 2 00 0000000000000000000000 "CCDM: SLS3: unexpected media during transport from the alignment
module"
001A 0138_E 2 00 0000000000000000000000 "CCDM: SLS3: unexpected media during transport from the escrow
module"
001A 0139_E 2 00 0000000000000000000000 "CCDM: SLS3: media jam in sensor transport"
001A 0140_E 2 00 0000000000000000000000 "CCDM: SLS1: medium is expected but no media is coming"
001A 0141_E 2 00 0000000000000000000000 "CCDM: SLS1: unexpected document during transport from the align-
ment module"
001A 0142_E 2 00 0000000000000000000000 "CCDM: SLS1: unexpected document during transport from the escrow
module"
001A 0143_E 2 00 0000000000000000000000 "CCDM: Document jam in area -> document deflector -> escrow/reject
module"
001A 0144_E 2 00 0000000000000000000000 "CCDM: Cheque/cash reader: unexpected media during transport from
the alignment module"
001A 014A_E 2 00 0000000000000000000000 "CCDM: Document jam at the escrow module ELS1"
001A 014B_E 2 00 0000000000000000000000 "CCDM: Document jam between sensor module and cassette/reject
module"
001A 014C_E 2 00 0000000000000000000000 "CCDM: Document jam between sensor transport and reject transport"
U25604-J-Z745-1-7600 October 2004 393


Class Code INFO
Status Data
001A 014D_E 2 00 0000000000000000000000 "CCDM: Cheque/cash reader: the gap between two media is too small"
001A 0190_E 2 00 0000000000000000000000 "CCDM: Escrow tape at ELS2 defective"
001A 0191_E 2 00 0000000000000000000000 "CCDM: Escrow tape at ELS3 defective"
001A 0192_E 2 00 0000000000000000000000 "CCDM: Document into escrow not expected"
001A 0193_E 2 00 0000000000000000000000 "CCDM: Failure in ELS1 area"
001A 0194_E 2 00 0000000000000000000000 "CCDM: Document missing or escrow empty"
001A 0195_E 2 00 0000000000000000000000 "CCDM: Gap between two notes too long or jam at escrow unit"
001A 0196_E 2 00 0000000000000000000000 "CCDM: Initialisation not finished in the spezified time"
001A 01F5_E 2 00 0000000000000000000000 "CCDM: Incorrect deflector position"
001A 01F6_E 2 00 0000000000000000000000 "CCDM: Jam between sensor module (paper deflectors) and before
RLS1"
001A 01F7_E 2 00 0000000000000000000000 "CCDM: Document too short"
001A 01F8_E 2 00 0000000000000000000000 "CCDM: Document too long"
001A 0259_E 2 00 0000000000000000000000 "CCDM: RLS1: jam or medium too long"
001A 025A_E 2 00 0000000000000000000000 "CCDM: RLS1: medium missing at KLS2 (module entry)"
001A 025B_E 2 00 0000000000000000000000 "CCDM: KLS2: unexpected medium at module entry"
001A 025C_E 2 00 0000000000000000000000 "CCDM: KLS2: jam or medium too long"
001A 025D_E 2 00 0000000000000000000000 "CCDM: Incorrect position of deflector in cassette module"
001A 025E_E 2 00 0000000000000000000000 "CCDM: KLS2: medium to retract box missing"
001A 025F_E 2 00 0000000000000000000000 "CCDM: Retract cassette: jam or medium too long"
001A 0260_E 2 00 0000000000000000000000 "CCDM: Incorrect position of deflector in cassette module 1"
001A 0261_E 2 00 0000000000000000000000 "CCDM: KLS2: medium to box 1 missing"
001A 0262_E 2 00 0000000000000000000000 "CCDM: Cassette module 1: jam or medium too long"
001A 0263_E 2 00 0000000000000000000000 "CCDM: Incorrect position of deflector in cassette module 2"
001A 0264_E 2 00 0000000000000000000000 "CCDM: KLS2: medium to box 2 missing"
001A 0265_E 2 00 0000000000000000000000 "CCDM: Cassette module 2: jam or medium too long"
001A 0266_E 2 00 0000000000000000000000 "CCDM: Media jam KLS5 - KSM"
001A 0267_E 2 00 0000000000000000000000 "CCDM: Error in cassette 1 during init"
001A 0268_E 2 00 0000000000000000000000 "CCDM: Error in cassette 2 during init"
001A 8000_E 2 00 0000000000000000000000 "CCDM: Invalid parameter in command"
001A 8001_E 2 00 0000000000000000000000 "CCDM: No document inserted"
001A 8002_E 2 00 0000000000000000000000 "CCDM: Function CscPrtRead was called, but no MICR mode via
CscPrtControl selected"
001A 8003_E 2 00 0000000000000000000000 "CCDM: The CCDM device handler presumes MS-Windows 2000 or
MS-Windows XP"
001A 8004_E 2 00 0000000000000000000000 "CCDM: There is still a document in the scanner"
001A 8005_E 2 00 0000000000000000000000 "CCDM: The CCDM-HW send unknown response to a command"
001A 8006_E 2 00 0000000000000000000000 "CCDM: Cannot open raw file (CCDM.RAW)"
001A 8007_E 2 00 0000000000000000000000 "CCDM: Error writing raw file (CCDM.RAW)"
001A 8008_E 2 00 0000000000000000000000 "CCDM: The shutter could not be opened"
001A 8009_E 2 00 0000000000000000000000 "CCDM: The shutter could not be closed"
001A 800A_E 2 00 0000000000000000000000 "CCDM: Invalid CRC (check character) received with encrypted line"
001A 800B_E 2 00 0000000000000000000000 "CCDM: Wrong value for FRM_LOAD in Registry with CSCCCDM"
001A 800C_E 2 00 0000000000000000000000 "CCDM: Firmware loading could not be completed"
001A 800D_E 2 00 0000000000000000000000 "CCDM: Wrong value for LED, LED_FLASH or LED_FREQ"
001A 800E_E 2 00 0000000000000000000000 "CCDM: Wrong value for MAX_HEIGHT_CHEQUE,
MAX_HEIGHT_NOTES, MAX_WIDTH_CHEQUE"
001A 800F_E 2 00 0000000000000000000000 "CCDM: Wrong value for the parameter SCAN_FRONT_RED,
SCAN_FRONT_GREEN"
001A 8010_E 2 00 0000000000000000000000 "CCDM: Wrong value for SHUTTER_BEHAVIOUR in Registry with
CSCCCDM"
001A 8011_E 2 00 0000000000000000000000 "CCDM: The thread which receives the image/signature data could not
started"
001A 8012_E 2 00 0000000000000000000000 "CCDM: The thread which receives the image/signature data could not
stopped"
001A 8013_E 2 00 0000000000000000000000 "CCDM: The pointer "
001A 8014_E 2 00 0000000000000000000000 "CCDM: The transferred cheque data (pointer, length) is illegal"
001A 8015_E 2 00 0000000000000000000000 "CCDM: No cheque number received while dispensing cheques or
sheets"
001A 8016_E 2 00 0000000000000000000000 "CCDM: An error occurred while opening a currency file"
001A 8017_E 2 00 0000000000000000000000 "CCDM: An error occurred while opening a currency file"
001A 8018_E 2 00 0000000000000000000000 "CCDM: The currency file is not dedicated for the installed note sensor"
001A 8019_E 2 00 0000000000000000000000 "CCDM: A wrong keyword inside a currency file has been detected"
001A 801A_E 2 00 0000000000000000000000 "CCDM: The loading of new currency data not possible"
394 October 2004 U25604-J-Z745-1-7600


Class Code INFO
Status Data
001A 801B_E 2 00 0000000000000000000000 "CCDM: New currency file loaded during installation"
001A 801C_E 2 00 0000000000000000000000 "CCDM: Error occurred while opening firmware file"
001A 801D_E 2 00 0000000000000000000000 "CCDM: Error occured while reading sensor firmware file"
001A 801E_E 2 00 0000000000000000000000 "CCDM: Firmware file is not dedicated for the installed sensor"
001A 801F_E 2 00 0000000000000000000000 "CCDM: Wrong value for SENS_FRM_LOAD in Registry with CSC-
CCDM"
001A 8020_E 2 00 0000000000000000000000 "CCDM: Not possible to read the current note table from the note sen-
sor"
001A 8021_E 2 00 0000000000000000000000 "CCDM: Too much notes inserted"

001A 8022_E 2 00 0000000000000000000000 "CCDM: Timeout while waiting for signature ID"
001A 8023_E 2 00 0000000000000000000000 "CCDM: Number of detected cheques on ESCROW and number of
scanned cheques different"
001A 8024_E 2 00 0000000000000000000000 "CCDM: Error in previous transaction"
001A 8025_E 2 00 0000000000000000000000 "CCDM: Error in previous transaction"
001A 8026_E 2 00 0000000000000000000000 "CCDM: Error occurred while opening a sensor firmware file"
001A 8027_E 2 00 0000000000000000000000 "CCDM: Error occured while reading a CCDM firmware file"
001A 8030_E 2 00 0000000000000000000000 "CCDM: The checksum of the signature data of a note is wrong"
001A 9201_E 2 00 0000000000000000000000 "CCDM: Illegal arguments calling IMACON.DLL"
001A 9202_E 2 00 0000000000000000000000 "CCDM: Cannot open input file"
001A 9203_E 2 00 0000000000000000000000 "CCDM: Error reading input"
001A 9204_E 2 00 0000000000000000000000 "CCDM: Cannot open output file"
001A 9205_E 2 00 0000000000000000000000 "CCDM: Error writing output file"
001A 9206_E 2 00 0000000000000000000000 "CCDM: Not enough memory"
001A 9207_E 2 00 0000000000000000000000 "CCDM: Image too long"
001A 9208_E 2 00 0000000000000000000000 "CCDM: Image too large (for TIF)"
001A 9209_E 2 00 0000000000000000000000 "CCDM: Image too small (<1 row)"
001A 920A_E 2 00 0000000000000000000000 "CCDM: Error in final conversion step"
001A 920B_E 2 00 0000000000000000000000 "CCDM: Error in temp file access"
001A 920C_E 2 00 0000000000000000000000 "CCDM: Error loading imareco.dll"
001A 92FF_E 2 00 0000000000000000000000 "CCDM: IMACON.DLL returned undefined error"
001A 9300_E 2 00 0000000000000000000000 "CCDM: Internal error while calling DQF.DLL"
001A 93FF_E 2 00 0000000000000000000000 "CCDM: DQF.DLL returned undefined error"
001A E000_W 2 00 0000000000000000000000 "CCDM: Tray operating error (e.g. banknotes not correct inserted)"
001A E001_W 2 00 0000000000000000000000 "CCDM: Sheets not inserted in the given time period (reported by
CscwCcdmEntry(...))"
001A E002_W 2 00 0000000000000000000000 "CCDM: Some or all notes or checks not taken by the consumer"
001A E003_W 2 00 0000000000000000000000 "CCDM: Some or all notes or checks not taken by the consumer while
retract to IO or box"
001A E004_W 2 00 0000000000000000000000 "CCDM: Sheets available in the IO tray, e.g. rejected notes or cheques
after dispensing"
001A E00A_W 2 00 0000000000000000000000 "CCDM: Loaded firmware older than the firmware found on disk"
001A E00B_W 2 00 0000000000000000000000 "CCDM: There is no firmware loaded in the CCCDM"
001A E00C_W 2 00 0000000000000000000000 "CCDM: Device handler was configured to switch LEDs when cus-
tomer action is neccessary"
001A E010_W 2 00 0000000000000000000000 "CCDM: Return of the function CscCcdmInit() if a new currency file
has been detected"
001A E011_W 2 00 0000000000000000000000 "CCDM: Returned by the function CscCcdmInit() if a new currency file
has been detected"
001A E014_W 2 00 0000000000000000000000 "CCDM: One or more new firmware loaded automatically by the
Device Handler"
001A E015_W 2 00 0000000000000000000000 "CCDM: Current loaded note table inconsistant to sensor Firmware"
001A F000_E 2 00 0000000000000000000000 "CCDM: The firmware is not loaded in the CCDM"
001A F001_E 2 00 0000000000000000000000 "CCDM: The parameters of the command have a wrong syntax"
001A F002_E 2 00 0000000000000000000000 "CCDM: One of the locks is active or an error occurred that requires
correction"
001A F003_E 2 00 0000000000000000000000 "CCDM: An error occurred during the execution of the command"
001A F004_E 2 00 0000000000000000000000 "CCDM: The safe door must be open for the execution of the actual
command"
001A F005_E 2 00 0000000000000000000000 "CCDM: The command cannot be executed at this point of time"
U25604-J-Z745-1-7600 October 2004 395


Class Code INFO
Status Data
001A F006_E 2 00 0000000000000000000000 "CCDM: The application program tried to dispense a bundle, but the
IO-tray is empty"
001A F007_E 2 00 0000000000000000000000 "CCDM: Customer did not remove the bundle until the command has
timed out"
001A F008_E 2 00 0000000000000000000000 "CCDM: Cheques or sheets are not correct inserted"
001A F009_E 2 00 0000000000000000000000 "CCDM: CCDM firmware initiated a boot"
001A F00A_E 2 00 0000000000000000000000 "CCDM: Note sensor module reports hardware error"
001A F00B_E 2 00 0000000000000000000000 "CCDM: Note sensor module reports firmware error"
001A F00C_E 2 00 0000000000000000000000 "CCDM: Comunication error reported by the sensor module"
001A F00D_E 2 00 0000000000000000000000 "CCDM: Note sensor hase detected an error in the data format"
001A F00E_E 2 00 0000000000000000000000 "CCDM: Note sensor has detected an error in the note table"
001A F00F_E 2 00 0000000000000000000000 "CCDM: The assignment of a note is wrong"
001A F010_E 2 00 0000000000000000000000 "CCDM: The sensor couldn't read the document (note or cheque)"
001A F011_E 2 00 0000000000000000000000 "CCDM: An error occured during downloding of firmware or currency
data"
001A F012_E 2 00 0000000000000000000000 "CCDM: The sensor responded with an unknown error code"
001A F0A0_E 2 00 0000000000000000000000 "CCDM: Bundle with detected metal in tray"
001A F0A1_E 2 00 0000000000000000000000 "CCDM: Tray is occupied with not dispensable notes or cheques"
001A F0A2_E 2 00 0000000000000000000000 "CCDM: A not specified tray error occurred"
001A F0A3_E 2 00 0000000000000000000000 "CCDM: Shutter error while command CscCcdmCashIn"
001A F0A4_E 2 00 0000000000000000000000 "CCDM: CscCcdmTransport command received, but the ESCROW is
empty"
001A F0A5_E 2 00 0000000000000000000000 "CCDM: ESCROW full while dispending a bundle"
001A F0A6_E 2 00 0000000000000000000000 "CCDM: Cheques or sheets on ESCROW while performing the next
transaction"
001A F0A7_E 2 00 0000000000000000000000 "CCDM: Cheques or notes jammed on the ESCROW"
001A F0A8_E 2 00 0000000000000000000000 "CCDM: There exists no hardware equipment to perform the requested
command"
AA1A DEFA_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Default error"
AA1A DEFA_W 4 01 00000000 "IEEE1394/CCDM_CHQ: Default warning"
AA1A FE09_E 4 01 00000000 "IEEE1394/CCDM_CHQ: IEEE 1394 read command could not be exe-
cuted in the specified monitoring time"
AA1A FE0A_E 4 01 00000000 "IEEE1394/CCDM_CHQ: A IEEE 1394 read command is cancelled by
the user"
AA1A FE9C_E 4 01 00000000 "IEEE1394/CCDM_CHQ: The length in DataSize is 0 (zero)"
AA1A FE9E_E 4 01 00000000 "IEEE1394/CCDM_CHQ: The I1394_TS.DLL could not be opened"
AA1A FEA0_E 4 01 00000000 "IEEE1394/CCDM_CHQ: The I1394_UB.DLL could not be opened"
AA1A 0100_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Out of memory"
AA1A 0210_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Device is not in work-
ing state"
AA1A 0300_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid parameter"
AA1A 0305_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Size of buffer is
invalid"
AA1A 8001_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Device not found"
AA1A 8010_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: No such device
instance"
AA1A 0100_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The operation was can-
celled/aborted"
AA1A 0200_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: A non-critical error
occurred on the adapter"
AA1A 0250_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The application has
already opened the specified adapter"
celled because more bus resets"
celled because a 1394 bus reset"
AA1A 0350_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The operation could not
be completed because there was a conflict"
AA1A 0370_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error"
AA1A 0400_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: A critical error
occurred on the adapter that caused the request to fail"
AA1A 0500_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The operation
requested failed because the local adapter is busy"
AA1A 0572_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error."
AA1A 0600_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The driver detected a
bug in its execution logic"
396 October 2004 U25604-J-Z745-1-7600


Class Code INFO
Status Data
AA1A 0639_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The isochronous chan-
nel number is already in use"
AA1A 0645_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: An isochronous opera-
tion failed because of a FIFO"
AA1A 0658_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: An isochronous opera-
tion failed because of a FIFO underrun"
AA1A 06B2_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: An outgoing response
packet is not valid"

AA1A 0700_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: An operation failed due
to some lack of resources other"
AA1A 0900_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The operation
requested is not applicable to the channel"
AA1A 0A00_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The operation
requested is not possible at the channel's current state"
AA1A 0C00_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Adapters not identi-
fied"
AA1A 0D00_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: A validation check on a
number of isochronous buffers failed"
AA1A 0D47_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error"
AA1A 0F00_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The request passed to
the miniport was invalid"
AA1A 0F50_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error"
AA1A 0F73_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error"
AA1A 1070_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The requested item was
not found"
AA1A 1100_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The request valid, but
adapter does not support the required functionality"
AA1A 132A_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The request cannot be
transmitted"
AA1A 1350_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: The request cannot be
transmitted"
AA1A 0001_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Operation failed"
AA1A 0010_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Operation not sup-
ported"
AA1A 0030_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Operation rejected"
AA1A 0110_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Packet pool empty"
AA1A 0200_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Device is removed"
AA1A 0220_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Requested power state
transition not allowed"
AA1A 0280_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Operation rejected,
device is powered down"
AA1A 0302_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid IO control
code"
AA1A 0304_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Requested byte count
does not match buffer size"
AA1A 0310_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Input buffer too small"
AA1A 0320_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Output buffer too
small"
AA1A 0340_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Handle already used by
an object of this type"
AA1A 0341_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Handle already used by
an object of another type"
AA1A 0342_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Handle not associated
with required object"
AA1A 0400_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid configuration
info type"
U25604-J-Z745-1-7600 October 2004 397


Class Code INFO
Status Data
AA1A 0401_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid local host info
type"
AA1A 0402_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid local host prop-
erty type"
AA1A 0403_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Unsupported type of
lock operation"
AA1A 0404_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Unsupported speed
selected"
AA1A 8002_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Device not open"
AA1A 8003_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Request timeout inter-
val has expired"
AA1A 8008_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Invalid parameter in
function call"
AA1A 8020_E 4 01 00000000 "IEEE1394/CCDM_CHQ: Internal driver error: Memory allocation
failed"
BB1A DEFA_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Default error"
BB1A DEFA_W 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Default warning"
BB1A FE09_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: IEEE 1394 read command could not be exe-
cuted in the specified monitoring time"
BB1A FE0A_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: A IEEE 1394 read command is cancelled by
the user"
BB1A FE9C_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: The length in DataSize is 0 (zero)"
BB1A FE9E_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: The I1394_TS.DLL could not be opened"
BB1A FEA0_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: The I1394_UB.DLL could not be opened"
BB1A 0100_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Out of memory"
BB1A 0210_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Device is not in working
state"
BB1A 0300_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid parameter"
BB1A 0305_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Size of buffer is invalid"
BB1A 8001_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Device not found"
BB1A 8010_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: No such device
instance"
BB1A 0100_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The operation was can-
celled/aborted"
BB1A 0200_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: A non-critical error
occurred on the adapter"
BB1A 0250_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The application has
already opened the specified adapter"
celled because more bus resets"
celled because a 1394 bus reset"
BB1A 0350_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The operation could not
be completed because there was a conflict"
BB1A 0370_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error"
BB1A 0400_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: A critical error occurred
on the adapter that caused the request to fail"
BB1A 0500_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The operation requested
failed because the local adapter is busy"
BB1A 0572_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error."
BB1A 0600_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The driver detected a
bug in its execution logic"
BB1A 0639_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The isochronous chan-
nel number is already in use"
BB1A 0645_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: An isochronous opera-
tion failed because of a FIFO"
BB1A 0658_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: An isochronous opera-
tion failed because of a FIFO underrun"
BB1A 06B2_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: An outgoing response
packet is not valid"
BB1A 0700_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: An operation failed due
to some lack of resources other"
BB1A 0900_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The operation requested
is not applicable to the channel"
BB1A 0A00_E 4 00 0000000000000000000000 "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


Class Code INFO
Status Data
BB1A 0C00_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Adapters not identified"
BB1A 0D00_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: A validation check on a
number of isochronous buffers failed"
BB1A 0D47_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error"
BB1A 0F00_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The request passed to
the miniport was invalid"
BB1A 0F50_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error"
BB1A 0F73_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error"
BB1A 1070_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The requested item was
not found"
BB1A 1100_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The request valid, but
adapter does not support the required functionality"
BB1A 132A_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The request cannot be
transmitted"
BB1A 1350_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: The request cannot be
transmitted"
BB1A 0001_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Operation failed"
BB1A 0010_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Operation not sup-
ported"
BB1A 0030_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Operation rejected"
BB1A 0110_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Packet pool empty"
BB1A 0200_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Device is removed"
BB1A 0220_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Requested power state
transition not allowed"
BB1A 0280_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Operation rejected,
device is powered down"
BB1A 0302_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid IO control code"
BB1A 0304_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Requested byte count
does not match buffer size"
BB1A 0310_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Input buffer too small"
BB1A 0320_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Output buffer too small"
BB1A 0340_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Handle already used by
an object of this type"
BB1A 0341_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Handle already used by
an object of another type"
BB1A 0342_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Handle not associated
with required object"
BB1A 0400_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid configuration
info type"
BB1A 0401_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid local host info
type"
BB1A 0402_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid local host prop-
erty type"
BB1A 0403_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Unsupported type of
lock operation"
BB1A 0404_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Unsupported speed
selected"
BB1A 8002_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Device not open"
BB1A 8003_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Request timeout interval
has expired"
BB1A 8008_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Invalid parameter in
function call"
BB1A 8020_E 4 00 0000000000000000000000 "IEEE1394/CCDM_CIN: Internal driver error: Memory allocation
failed"
CC1A DEFA_W 4 00 0000000000000000000000 "USB/CCDM_CIN: DEFAULT_WARNING"
CC1A DEFA_E 4 00 0000000000000000000000 "USB/CCDM_CIN: DEFAULT_ERROR"
U25604-J-Z745-1-7600 October 2004 399


Class Code INFO
Status Data
CC1A 8000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Unexpected descriptor was reported from USB
device"
CC1A 8001_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Device not found"
CC1A 8002_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Not enough memory available"
CC1A 8003_E 4 00 0000000000000000000000 "USB/CCDM_CIN: It was no endpoint found in the descriptor"
CC1A 8004_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The creation of the list of USB devices failed"
CC1A FE09_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB read command could not be executed in the
specified monitoring time"
CC1A FE0A_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB READ command is cancelled by the user"
CC1A FE89_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The pointer pData is illegal"
CC1A FE9C_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The length in DataSize is 0 (zero)"
CC1A 0001_E 4 00 0000000000000000000000 "USB/CCDM_CIN: CRC error has been detected"
CC1A 0002_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Bit stuffing error has been detected"
CC1A 0003_E 4 00 0000000000000000000000 "USB/CCDM_CIN: DATA toggle mismatch has been detected"
CC1A 0004_E 4 00 0000000000000000000000 "USB/CCDM_CIN: STALLPID has been detected, error is reported by
the USB host controller"
CC1A 0005_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB device is not responding, error is reported by
the USB host"
CC1A 0006_E 4 00 0000000000000000000000 "USB/CCDM_CIN: PID check has failed, error is reported by the USB
host controller"
CC1A 0007_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Unexpected PID detected, error is reported by the
USB host"
CC1A 0008_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Data overrun error detected, error is reported by the
USB host"
CC1A 0009_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Data underrun error detected, error is reported by
the USB host"
CC1A 000A_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Error code is reserved by the USB host controller
driver"
CC1A 000B_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Error code is reserved by the USB host controller
driver"
CC1A 000C_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Buffer overrun has been detected, error is reported
by the USB host"
CC1A 000D_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Buffer underrun has been detected, error is reported
by the USB host"
CC1A 000F_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Buffer was not accessed, error is reported by the
USB host"
CC1A 0010_E 4 00 0000000000000000000000 "USB/CCDM_CIN: FIFO error has been detected, PCI bus latency was
too long"
CC1A 0011_E 4 00 0000000000000000000000 "USB/CCDM_CIN: XACT error has been detected, error is reported by
the USB host"
CC1A 0012_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Device is babbling, data transfer phase exceeds the
USB frame length"
CC1A 0013_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Data buffer error has been detected, error is
reported by the USB host"
CC1A 0030_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Endpoint has been halted by the USB bus driver
USBD"
CC1A 0100_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Memory allocation attempt has failed, error is
reported by the USB bus"
CC1A 0200_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid URB function code has been passed, error
is reported by the USB"
CC1A 0300_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid parameter has been passed, error is reported
by the USB bus"
CC1A 0400_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There are data transfer requests pending for the
device"
CC1A 0500_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Request has failed, error is reported by the USB
bus driver USBD"
CC1A 0600_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid pipe handle has been passed, error is
CC1A 0700_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There is not enough bandwidth available, error is
CC1A 0800_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Internal host controller error has been detected"
CC1A 0900_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Short transfer has been detected, error is reported
by the USB bus"
CC1A 0A00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Bad start frame has been specified, error is reported
by the USB bus"
CC1A 0B00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Asynchronous request has failed, error is reported
by the USB bus driver"
400 October 2004 U25604-J-Z745-1-7600


Class Code INFO
Status Data
CC1A 0C00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB frame control is currently owned, error is
CC1A 0D00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB frame control is currently not owned, error is
reported by the USB"
CC1A 0E00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation is not supported, error is reported by the
USB bus driver"
CC1A 0F00_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid configuration descriptor was reported by
the device"
CC1A 1000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation has failed, error is reported by the
USBIO driver"
CC1A 1001_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid input buffer has been passed to an IOCTL
operation"
CC1A 1002_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid output buffer has been passed to an IOCTL
operation"
CC1A 1003_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There is not enough system memory available to
complete the operation"
CC1A 1004_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There are read or write requests pending, error is
reported by the USBIO"
CC1A 1005_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB device is already configured, error is reported
by the USBIO"
CC1A 1006_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The USB device is not configured, error is reported
by the USBIO driver"
CC1A 1007_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There are open pipes, error is reported by the
USBIO driver"
CC1A 1008_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Either the handle is already bound to a pipe"
CC1A 1009_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Handle is not bound to a pipe, error is reported by
the USBIO driver"
CC1A 100A_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB device has been removed from the system"
CC1A 100B_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Specified control code is not supported"
CC1A 100C_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation has been timed out, error is reported by
the USBIO driver"
CC1A 100D_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid recipient has been specified"
CC1A 100E_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Either an invalid request type has been specified"
CC1A 100F_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid IOCTL code has been specified, error is
CC1A 1010_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Direction of the data transfer request is not sup-
ported by that pipe"
CC1A 1011_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Number of asynchronous data packets specified in
an asynchronous read"
CC1A 1012_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Memory resources are exhausted. This error is
reported by the USBIO driver"
CC1A 1013_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The specified pipe was not found in the current
configuration"
CC1A 1014_E 4 00 0000000000000000000000 "USB/CCDM_CIN: An invalid asynchronous data packet has been
specified"
CC1A 1015_E 4 00 0000000000000000000000 "USB/CCDM_CIN: There are not enough system resources to complete
the operation"
CC1A 1016_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Specified interface was not found in the current
configuration"
CC1A 1017_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation cannot be executed while the USB
device is in the current state"
CC1A 1018_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid parameter has been specified with an
IOCTL operation"
CC1A 1019_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Evaluation interval of the USBIO DEMO version
has expired"
CC1A 101A_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid power state has been specified"
CC1A 101B_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Device has entered a power down state"
CC1A 101C_E 4 00 0000000000000000000000 "USB/CCDM_CIN: API version reported by the USBIO driver does not
match"
CC1A 101D_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Set configuration operation has failed, error is
CC1A 1080_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation has failed due to a restriction of the
USBIO LIGHT version"
U25604-J-Z745-1-7600 October 2004 401


Class Code INFO
Status Data
CC1A 1086_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The operation has failed due to a restriction of the
CC1A 1100_E 4 00 0000000000000000000000 "USB/CCDM_CIN: The specified device object does not exist"
CC1A 1102_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Device object was opened, there is no valid handle
to execute the operation"
CC1A 1104_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Enumeration of the specified devices has failed"
CC1A 1105_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid parameter has been passed to a function"
CC1A 1106_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Library setupapi.dll could not be loaded"
CC1A 2000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Set configuration request has failed"
CC1A 3000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Buffer is too small, error is reported by the USB
bus driver USBD"
CC1A 4000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Interface was not found, error is reported by the
USB bus driver USBD"
CC1A 5000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Invalid pipe flags have been specified"
CC1A 6000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: Operation has been timed out, error is reported by
the USB bus driver"
CC1A 7000_E 4 00 0000000000000000000000 "USB/CCDM_CIN: USB device is gone, error is reported by the USB
bus driver USBD"
DD1A DEFA_W 2 01 00000000 "USB/CCDM_CHQ: DEFAULT_WARNING"
DD1A DEFA_E 2 01 00000000 "USB/CCDM_CHQ: DEFAULT_ERROR"
DD1A 8000_E 2 01 00000000 "USB/CCDM_CHQ: Unexpected descriptor was reported from USB
device"
DD1A 8001_E 2 01 00000000 "USB/CCDM_CHQ: Device not found"
DD1A 8002_E 2 01 00000000 "USB/CCDM_CHQ: Not enough memory available"
DD1A 8003_E 2 01 00000000 "USB/CCDM_CHQ: It was no endpoint found in the descriptor"
DD1A 8004_E 2 01 00000000 "USB/CCDM_CHQ: The creation of the list of USB devices failed"
DD1A FE09_E 2 01 00000000 "USB/CCDM_CHQ: USB read command could not be executed in the
specified monitoring time"
DD1A FE0A_E 2 01 00000000 "USB/CCDM_CHQ: USB READ command is cancelled by the user"
DD1A FE89_E 2 01 00000000 "USB/CCDM_CHQ: The pointer pData is illegal"
DD1A FE9C_E 2 01 00000000 "USB/CCDM_CHQ: The length in DataSize is 0 (zero)"
DD1A 0001_E 2 01 00000000 "USB/CCDM_CHQ: CRC error has been detected"
DD1A 0002_E 2 01 00000000 "USB/CCDM_CHQ: Bit stuffing error has been detected"
DD1A 0003_E 2 01 00000000 "USB/CCDM_CHQ: DATA toggle mismatch has been detected"
DD1A 0004_E 2 01 00000000 "USB/CCDM_CHQ: STALLPID has been detected, error is reported by
the USB host controller"
DD1A 0005_E 2 01 00000000 "USB/CCDM_CHQ: USB device is not responding, error is reported by
the USB host"
DD1A 0006_E 2 01 00000000 "USB/CCDM_CHQ: PID check has failed, error is reported by the USB
host controller"
DD1A 0007_E 2 01 00000000 "USB/CCDM_CHQ: Unexpected PID detected, error is reported by the
USB host"
DD1A 0008_E 2 01 00000000 "USB/CCDM_CHQ: Data overrun error detected, error is reported by
the USB host"
DD1A 0009_E 2 01 00000000 "USB/CCDM_CHQ: Data underrun error detected, error is reported by
the USB host"
DD1A 000A_E 2 01 00000000 "USB/CCDM_CHQ: Error code is reserved by the USB host controller
driver"
DD1A 000B_E 2 01 00000000 "USB/CCDM_CHQ: Error code is reserved by the USB host controller
driver"
DD1A 000C_E 2 01 00000000 "USB/CCDM_CHQ: Buffer overrun has been detected, error is reported
by the USB host"
DD1A 000D_E 2 01 00000000 "USB/CCDM_CHQ: Buffer underrun has been detected, error is
DD1A 000F_E 2 01 00000000 "USB/CCDM_CHQ: Buffer was not accessed, error is reported by the
USB host"
DD1A 0010_E 2 01 00000000 "USB/CCDM_CHQ: FIFO error has been detected, PCI bus latency was
too long"
402 October 2004 U25604-J-Z745-1-7600


Class Code INFO
Status Data
DD1A 0011_E 2 01 00000000 "USB/CCDM_CHQ: XACT error has been detected, error is reported
by the USB host"
DD1A 0012_E 2 01 00000000 "USB/CCDM_CHQ: Device is babbling, data transfer phase exceeds
the USB frame length"
DD1A 0013_E 2 01 00000000 "USB/CCDM_CHQ: Data buffer error has been detected, error is
DD1A 0030_E 2 01 00000000 "USB/CCDM_CHQ: Endpoint has been halted by the USB bus driver
USBD"
DD1A 0100_E 2 01 00000000 "USB/CCDM_CHQ: Memory allocation attempt has failed, error is
DD1A 0200_E 2 01 00000000 "USB/CCDM_CHQ: Invalid URB function code has been passed, error
is reported by the USB"
DD1A 0300_E 2 01 00000000 "USB/CCDM_CHQ: Invalid parameter has been passed, error is
DD1A 0400_E 2 01 00000000 "USB/CCDM_CHQ: There are data transfer requests pending for the
device"
DD1A 0500_E 2 01 00000000 "USB/CCDM_CHQ: Request has failed, error is reported by the USB
bus driver USBD"
DD1A 0600_E 2 01 00000000 "USB/CCDM_CHQ: Invalid pipe handle has been passed, error is
DD1A 0700_E 2 01 00000000 "USB/CCDM_CHQ: There is not enough bandwidth available, error is
DD1A 0800_E 2 01 00000000 "USB/CCDM_CHQ: Internal host controller error has been detected"
DD1A 0900_E 2 01 00000000 "USB/CCDM_CHQ: Short transfer has been detected, error is reported
by the USB bus"
DD1A 0A00_E 2 01 00000000 "USB/CCDM_CHQ: Bad start frame has been specified, error is
DD1A 0B00_E 2 01 00000000 "USB/CCDM_CHQ: Asynchronous request has failed, error is reported
by the USB bus driver"
DD1A 0C00_E 2 01 00000000 "USB/CCDM_CHQ: USB frame control is currently owned, error is
DD1A 0D00_E 2 01 00000000 "USB/CCDM_CHQ: USB frame control is currently not owned, error is
reported by the USB"
DD1A 0E00_E 2 01 00000000 "USB/CCDM_CHQ: Operation is not supported, error is reported by the
USB bus driver"
DD1A 0F00_E 2 01 00000000 "USB/CCDM_CHQ: Invalid configuration descriptor was reported by
the device"
DD1A 1000_E 2 01 00000000 "USB/CCDM_CHQ: Operation has failed, error is reported by the
USBIO driver"
DD1A 1001_E 2 01 00000000 "USB/CCDM_CHQ: Invalid input buffer has been passed to an IOCTL
operation"
DD1A 1002_E 2 01 00000000 "USB/CCDM_CHQ: Invalid output buffer has been passed to an
IOCTL operation"
DD1A 1003_E 2 01 00000000 "USB/CCDM_CHQ: There is not enough system memory available to
complete the operation"
DD1A 1004_E 2 01 00000000 "USB/CCDM_CHQ: There are read or write requests pending, error is
DD1A 1005_E 2 01 00000000 "USB/CCDM_CHQ: USB device is already configured, error is
DD1A 1006_E 2 01 00000000 "USB/CCDM_CHQ: The USB device is not configured, error is
DD1A 1007_E 2 01 00000000 "USB/CCDM_CHQ: There are open pipes, error is reported by the
USBIO driver"
DD1A 1008_E 2 01 00000000 "USB/CCDM_CHQ: Either the handle is already bound to a pipe"
DD1A 1009_E 2 01 00000000 "USB/CCDM_CHQ: Handle is not bound to a pipe, error is reported by
the USBIO driver"
DD1A 100A_E 2 01 00000000 "USB/CCDM_CHQ: USB device has been removed from the system"
DD1A 100B_E 2 01 00000000 "USB/CCDM_CHQ: Specified control code is not supported"
DD1A 100C_E 2 01 00000000 "USB/CCDM_CHQ: Operation has been timed out, error is reported by
the USBIO driver"
DD1A 100D_E 2 01 00000000 "USB/CCDM_CHQ: Invalid recipient has been specified"
DD1A 100E_E 2 01 00000000 "USB/CCDM_CHQ: Either an invalid request type has been specified"
DD1A 100F_E 2 01 00000000 "USB/CCDM_CHQ: Invalid IOCTL code has been specified, error is
DD1A 1010_E 2 01 00000000 "USB/CCDM_CHQ: Direction of the data transfer request is not sup-
ported by that pipe"
DD1A 1011_E 2 01 00000000 "USB/CCDM_CHQ: Number of asynchronous data packets specified in
an asynchronous read"
U25604-J-Z745-1-7600 October 2004 403


Class Code INFO
Status Data
DD1A 1012_E 2 01 00000000 "USB/CCDM_CHQ: Memory resources are exhausted. This error is
DD1A 1013_E 2 01 00000000 "USB/CCDM_CHQ: The specified pipe was not found in the current
configuration"
DD1A 1014_E 2 01 00000000 "USB/CCDM_CHQ: An invalid asynchronous data packet has been
specified"
DD1A 1015_E 2 01 00000000 "USB/CCDM_CHQ: There are not enough system resources to com-
plete the operation"
DD1A 1016_E 2 01 00000000 "USB/CCDM_CHQ: Specified interface was not found in the current
configuration"
DD1A 1017_E 2 01 00000000 "USB/CCDM_CHQ: Operation cannot be executed while the USB
device is in the current state"
DD1A 1018_E 2 01 00000000 "USB/CCDM_CHQ: Invalid parameter has been specified with an
IOCTL operation"
DD1A 1019_E 2 01 00000000 "USB/CCDM_CHQ: Evaluation interval of the USBIO DEMO version
has expired"
DD1A 101A_E 2 01 00000000 "USB/CCDM_CHQ: Invalid power state has been specified"
DD1A 101B_E 2 01 00000000 "USB/CCDM_CHQ: Device has entered a power down state"
DD1A 101C_E 2 01 00000000 "USB/CCDM_CHQ: API version reported by the USBIO driver does
not match"
DD1A 101D_E 2 01 00000000 "USB/CCDM_CHQ: Set configuration operation has failed, error is
DD1A 1080_E 2 01 00000000 "USB/CCDM_CHQ: Operation has failed due to a restriction of the
DD1A 1086_E 2 01 00000000 "USB/CCDM_CHQ: The operation has failed due to a restriction of the
DD1A 1100_E 2 01 00000000 "USB/CCDM_CHQ: The specified device object does not exist"
DD1A 1102_E 2 01 00000000 "USB/CCDM_CHQ: Device object was opened, there is no valid handle
to execute the operation"
DD1A 1104_E 2 01 00000000 "USB/CCDM_CHQ: Enumeration of the specified devices has failed"
DD1A 1105_E 2 01 00000000 "USB/CCDM_CHQ: Invalid parameter has been passed to a function"
DD1A 1106_E 2 01 00000000 "USB/CCDM_CHQ: Library setupapi.dll could not be loaded"
DD1A 2000_E 2 01 00000000 "USB/CCDM_CHQ: Set configuration request has failed"
DD1A 3000_E 2 01 00000000 "USB/CCDM_CHQ: Buffer is too small, error is reported by the USB
bus driver USBD"
DD1A 4000_E 2 01 00000000 "USB/CCDM_CHQ: Interface was not found, error is reported by the
USB bus driver USBD"
DD1A 5000_E 2 01 00000000 "USB/CCDM_CHQ: Invalid pipe flags have been specified"
DD1A 6000_E 2 01 00000000 "USB/CCDM_CHQ: Operation has been timed out, error is reported by
the USB bus driver"
DD1A 7000_E 2 01 00000000 "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)
class Encryption Decryption Module (EDM).
Table 102: Encryption Decryption Module (EDM) (Class: 000F)


000F DEFA_W 2 00 00000000 "EDM: DEFAULT_WARNING"
000F DEFA_E 4 00 00000000 "EDM: DEFAULT_ERROR"
000F 8000_E 2 98 00000000 "EDM: An undefined internal error has occurred in the firmware"
000F 8001_E 2 98 00000000 "EDM: The firmware cannot execute the command"
000F 8002_E 2 11 00000000 "EDM: Key address not allowed"
000F 8003_E 2 98 00000000 "EDM: EDM RAM error"
000F 8004_E 2 01 00000000 "EDM: Parity error in key"
000F 8005_E 2 02 00000000 "EDM: Internal hardware E-PROM error"
000F 8006_E 2 02 00000000 "EDM: Internal hardware EE-PROM error"
000F 8007_E 2 02 00000000 "EDM: The EDM command does not exist"
000F 8008_E 2 02 00000000 "EDM: The EDM key RAM is defective"
000F 8009_E 2 56 00000000 "EDM: The transferred data length is invalid"
000F 800A_E 2 02 00000000 "EDM: An invalid block ID is in the V24 protocal"
000F 800B_E 2 12 00000000 "EDM: The device ID is invalid"
000F 800C_E 2 00 00000000 "EDM: Command already transferred to the EDM firmware"
000F 800D_E 2 56 00000000 "EDM: Command length and data length invalid"
000F 800E_E 2 12 00000000 "EDM: Output parameters not defined"
000F 800F_E 2 12 00000000 "EDM: Data contains invalid ASCII characters"
000F 8010_E 2 12 00000000 "EDM: Wrong sequence of commands"
000F 8011_E 2 12 00000000 "EDM: Wrong ID"
000F 8040_E 2 00 00000000 "EDM: No transaction active, command cannot be executed"
000F 8041_E 2 11 00000000 "EDM: No or not enough PIN numbers entered"
000F 8050_E 2 02 00000000 "EDM: Key-splitting E-PROM not connected or wrong"
000F 8051_E 2 02 00000000 "EDM: Checksum of key-splitting E-PROM is wrong"
000F 8052_E 2 01 00000000 "EDM: Parity error in key of the key-splitting E-PROM"
000F 8053_E 2 02 00000000 "EDM: Invalid table charater in key-splitting E-PROM"
000F 8060_E 2 07 00000000 "EDM: V24 connection PC to EDM was/is interrupted"
000F 8061_E 2 02 00000000 "EDM: Battery problem of EDM"
000F 8062_E 2 00 00000000 "EDM: EPP detects an error when entering a key"
000F 8101_E 2 13 00000000 "EDM: EDM not initialized"
000F 8102_E 2 56 00000000 "EDM: Length in the parameter cannot be divided by eight"
000F 8103_E 2 00 00000000 "EDM: The DLL command specification is invalid"
000F 8104_E 2 11 00000000 "EDM: The command parameters are incorrect"
000F 8105_E 2 38 00000000 "EDM: Invalid key number"
000F 8107_E 2 07 00000000 "EDM: Error during data transmission"
000F 810B_E 2 56 00000000 "EDM: Initialize vector has wrong length"
000F 810C_E 2 16 00000000 "EDM: No free space in IV array"
000F 810E_E 2 02 00000000 "EDM: System could not provide dynamic memory"
000F 8111_E 2 56 00000000 "EDM: Wrong maximum PIN length with job EdmStartPin"
000F 8112_E 2 70 00000000 "EDM: Wrong minimum PIN length with job EdmStartPin"
000F 8113_E 2 70 00000000 "EDM: Invalid field for leading zeros in the PIN structure"
000F 8114_E 2 70 00000000 "EDM: Invalid field for acknowledge key in the PIN structure"
000F 8115_E 2 70 00000000 "EDM: Invalid mode in the PIN structure"
000F 8116_E 2 70 00000000 "EDM: Wrong PIN position in PIN field"
000F 8118_E 2 70 00000000 "EDM: Wrong structure entry in field TestMode"
000F 8119_E 2 70 00000000 "EDM: Invalid number of PIN digits"
000F 811A_E 2 02 00000000 "EDM: This API is not supported by the device handler"
000F 811B_E 2 02 00000000 "EDM: The API could not be loaded"
000F 811C_E 2 07 00000000 "EDM: This function cannot be accessed with the firmware"
000F 811E_E 2 07 00000000 "EDM: Cannot access full length of data area in a structure"
000F 811F_E 2 07 00000000 "EDM: Invalid encryption mode specified for key reset"
000F 8120_E 2 07 00000000 "EDM: The total protocol monitoring time has been exceeded"
U25604-J-Z745-1-7600 October 2004 405


000F 8121_E 2 00 00000000 "EDM: The maximum number of receive repeats has been reached"
000F 8122_E 2 00 00000000 "EDM: The received acknowledge type is invalid"
000F 8123_E 2 07 00000000 "EDM: Common protocol error in EPP response data"
000F 8124_E 2 12 00000000 "EDM: Key Generating Keys in REGISTRY/CSCINI are not correct"
000F 8125_E 2 12 00000000 "EDM: Invalid character in KGK Keyset in REGISTRY/CSCINI"
000F 8126_E 2 13 00000000 "EDM: Error when encrypting a Masterkey"
000F 8127_E 2 75 00000000 "EDM: The check is negativ"
Encryption Decryption Software (Class: 0011)
class Encryption Decryption Software (EDS).
Table 103: Encryption Decryption Software (EDS) (Class: 0011)

0011 DEFA_W 2 00 00000000 "EDS: DEFAULT_WARNING"
0011 DEFA_E 4 00 00000000 "EDS: DEFAULT_ERROR"
0011 8001_E 2 13 00000000 "EDS: No transport key is loaded"
0011 8002_E 2 22 00000000 "EDS: An invalid transport key is available"
0011 8003_E 2 13 00000000 "EDS: No CBC key is loaded"
0011 8004_E 2 01 00000000 "EDS: An invalid CBC key is available"
0011 8005_E 2 13 00000000 "EDS: No initial vector loaded"
0011 8007_E 2 13 00000000 "EDS: No ECB key is loaded"
0011 8008_E 2 01 00000000 "EDS: An invalid ECB key is available"
0011 800A_E 2 11 00000000 "EDS: The length specified in the parameter block is zero"
0011 800B_E 2 56 00000000 "EDS: Length specified in param. block cannot divided by eight"
0011 800C_E 2 13 00000000 "EDS: Error while accessing the CSCEDSKEY key file"
406 October 2004 U25604-J-Z745-1-7600

Card Reader (Class: 0008/AA08)
class Card Reader. Class AA08 is the USB class assigned to the Card Reader.
Table 104: Card Reader (Class: 0008/AA08)


0008 DEFA_E 2 00 0000000000 "CARD READER: DEFAULT_ERROR"
0008 DEFA_W 2 00 0000000000 "CARD READER: DEFAULT_WARNING"
0008 0000_W 0 00 0000000000 "CARD READER: If no warning found"
0008 0000_E 2 00 0000000000 "CARD READER: If no error found"
0008 1004_E 2 03 0205000000 "CARD READER: Length of input buffer in parameter block invalid"
0008 1005_E 2 03 0205000000 "CARD READER: Length of output buffer in parameter block invalid"
0008 100F_E 4 03 0205000000 "CARD READER: Device handler not initialized (card trap ?)"
0008 1015_E 4 03 0205000000 "CARD READER: Executed command not permitted or possible"
0008 E000_E 2 00 0000000000 "CARD READER: Invalid command (internal error)"
0008 E001_E 2 00 0000000000 "CARD READER: Parameters not correct"
0008 E002_E 2 13 0000000000 "CARD READER: Command cannot be executed"
0008 E004_E 2 00 0000000000 "CARD READER: Invalid data with a command"
0008 E006_E 4 20 0000000000 "CARD READER: Command cannot be executed, device is in maintanance mode "
0008 E009_E 4 20 0000000000 "CARD READER: Internal encountered in firmware of IDCU device"
0008 E00A_E 2 18 0000000000 "CARD READER: Card jammed (possible manipulation)"
0008 E00B_E 3 07 0000000000 "CARD READER: The sensors report an invalid position of the shutter"
0008 E00C_E 2 08 0000000000 "CARD READER: Sensors are defect"
0008 E00D_E 3 13 0000000000 "CARD READER: Card too long"
0008 E00E_E 3 13 0000000000 "CARD READER: Card too short"
0008 E00F_E 4 20 0000000000 "CARD READER: Memory error"
0008 E010_E 3 13 0000000000 "CARD READER: Card has shifted"
0008 E011_E 3 13 0000000000 "CARD READER: The card is jammed"
0008 E012_E 2 08 0000000000 "CARD READER: Shutter switch or width switch defective"
0008 E013_E 2 11 0000000000 "CARD READER: Mechanical error of IDCU device"
0008 E014_E 0 03 0000000000 "CARD READER: The data read from the cards have the wrong parity"
0008 E015_E 2 03 0000000000 "CARD READER: The card data could not be read"
0008 E016_E 2 04 0000000000 "CARD READER: The WRITE data is faulty on the card"
0008 E017_E 2 03 0000000000 "CARD READER: The end character only was found on the track when read"
0008 E01E_E 4 20 0000000000 "CARD READER: Power fail during a command"
0008 E01F_E 4 20 0000000000 "CARD READER: The DSR signal is in OFF status"
0008 E028_E 2 12 0000000000 "CARD READER: The card was removed during transport from the output position to
the reject box"
0008 E070_E 4 20 0000000000 "CARD READER: There is presently no firmware loaded in the device"
0008 E071_E 4 20 0000000000 "CARD READER: There was a problem during the download of the firmware"
0008 E100_E 2 03 0000000000 "CARD READER: The card data could not be read"
0008 E101_E 3 18 0000000000 "CARD READER: Card jammed in optional stacker unit (possible manipulation)"
0008 E102_E 4 18 0000000000 "CARD READER: No card in the dispenser"
0008 E104_E 4 18 0000000000 "CARD READER: Card is clamped by the ID card unit"
0008 E180_E 2 03 0000000000 "CARD READER: The chip card controller in the IDU or the IC card is defect"
0008 E182_E 2 03 0000000000 "CARD READER: The chip card could not be activated"
0008 E183_E 2 03 0000000000 "CARD READER: The chip card could not be deactivated"
0008 E184_E 2 03 0000000000 "CARD READER: An error occurred during communication with the chip card"
0008 E185_E 2 03 0000000000 "CARD READER: A forced interruption command was received from the chip card"
0008 E186_E 2 03 0000000000 "CARD READER: Error detected in response from the chip card"
0008 E187_E 2 03 0000000000 "CARD READER: The ATR information of the card is incorrect"
0008 7FFB_E 2 03 0000000000 "CARD READER: Chip card mode or SAM configuration not supported"
0008 7FFC_E 2 03 0000000000 "CARD READER: Flash memory needs to be reset"
0008 7FFD_E 2 03 0000000000 "CARD READER: Trigger level of transactions has been reached"
0008 7FFE_E 2 03 0000000000 "CARD READER: Error occurred during access of SEL DH to switch LED's"
0008 7FFF_E 2 03 0000000000 "CARD READER: Temporary power failure between last job and current job"
0008 F001_E 2 03 0205000000 "CARD READER: Maximum number of tries per command is reached"
0008 F002_E 2 20 0000000000 "CARD READER: Not enough data received from IDCU"
0008 F003_E 2 20 0000000000 "CARD READER: Error in communication protocal with IDCU"
U25604-J-Z745-1-7600 October 2004 407


0008 F004_E 2 20 0000000000 "CARD READER: V24 line error No ENQ was sent"
0008 F005_E 2 20 0000000000 "CARD READER: Response from IDCU is incorrect"
0008 F006_E 2 20 0000000000 "CARD READER: Invalid status"
0008 F007_E 2 20 0000000000 "CARD READER: Invalid parameters with the command"
0008 F008_E 2 20 0000000000 "CARD READER: Internal RESET not possible (internal error)"
0008 F009_E 2 20 0000000000 "CARD READER: TYPE in Registry/CSCINI with CSCIDU is incorrect"
0008 F00B_E 2 20 0000000000 "CARD READER: False value for ID_PM in Registry/CSCINI with CSCIDU"
0008 F00C_E 2 20 0000000000 "CARD READER: Wrong value for ID_PD in Registry/CSCINI with CSCIDU"
0008 F00D_E 2 20 0000000000 "CARD READER: False value for ID_WV in Registry/CSCINI with CSCIDU"
0008 F00E_E 2 20 0000000000 "CARD READER: False value for ID_SH in Registry/CSCINI with CSCIDU"
0008 F00F_E 2 20 0000000000 "CARD READER: Command is not available in this configuration"
0008 F011_E 2 04 0000000000 "CARD READER: V24 send command not terminated with correct length"
0008 F012_E 2 20 0000000000 "CARD READER: NAK received as a response"
0008 F013_E 2 00 0000000000 "CARD READER: CANCEL not possible"
0008 F014_E 2 00 0000000000 "CARD READER: A CsclduCancel command has already been sent"
0008 F015_E 2 05 0000000000 "CARD READER: No card in the unit to perform the command"
0008 F016_E 2 00 0000000000 "CARD READER: Wrong value for MSS in Registry/CSCINI with CSCIDU"
0008 F017_E 4 20 0000000000 "CARD READER: The device handler MSS could not be loaded"
0008 F018_E 2 00 0000000000 "CARD READER: Wrong value for ID_WT in Registry/CSCINI with CSCIDU"
0008 F019_E 2 00 0000000000 "CARD READER: Wrong value for ID_RJ in Registry/CSCINI with CSCIDU"
0008 F01A_E 2 00 0000000000 "CARD READER: Wrong value for MAN_RECOG in Registry/CSCINI with CSCIDU"
0008 F01B_E 4 20 0000000000 "CARD READER: The device handler CSCWHYBDLL could not be loaded"
0008 F01C_E 2 00 0000000000 "CARD READER: Wrong value for LED in Registry/CSCINI with CSCIDU"
0008 F01D_E 4 20 0000000000 "CARD READER: The device handler CSCWSELDLL could not be loaded"
0008 F01E_E 4 20 0000000000 "CARD READER: The device handler CSCWCITDLL could not be loaded"
0008 F020_E 4 20 0000000000 "CARD READER: The specified firmware file has not the correct format"
0008 F021_E 4 20 0000000000 "CARD READER: The parameter INIT_LOADER_CTL in the Registry/CSCINI is
incorrect"
0008 F022_E 4 20 0000000000 "CARD READER: DH CSCWTRADLL and /or CSCWESTDLL could not be loaded"
0008 F023_E 4 20 0000000000 "CARD READER: TRANSACTION-ACTIVE in the Registry/CSCINI is incorrect"
0008 F024_E 4 20 0000000000 "CARD READER: TRANSACTION-TRIGGER in the Registry/CSCINI is incorrect"
0008 F025_E 4 20 0000000000 "CARD READER: ERROR-MAPPING in the Registry/CSCINI is incorrect"
0008 F026_E 4 20 0000000000 "CARD READER: Parameter CHIPMODE in registry is incorrect"
0008 F027_E 4 20 0000000000 "CARD READER: Wrong value for ENTRY_HANDLING"
0008 F028_E 4 20 0000000000 "CARD READER: Device handler CSCSWI.DLL could not be loaded"
0008 F029_E 4 20 0000000000 "CARD READER: Device handler CSCEDS.DLL could not be loaded"
0008 F02A_E 4 20 0000000000 "CARD READER: Device handler CSCEDM.DLL could not be loaded"
0008 F02B_E 4 20 0000000000 "CARD READER: Device handler CSCWICM.DLL could not be loaded"
0008 F02C_E 4 20 0000000000 "CARD READER: Parameter SAMx_MODE incorrect"
0008 F02D_E 4 20 0000000000 "CARD READER: Parameter SAM incorrect"
0008 F02E_E 4 20 0000000000 "CARD READER: Device handler CSCWV2X.DLL could not be loaded"
0008 F02F_E 4 20 0000000000 "CARD READER: Device handler CSCWHUS.DLL could not be loaded"
0008 FE08_E 4 20 FE08000000 "CARD READER: V24 Communication timeout"
0008 FE09_E 4 20 FE09000000 "CARD READER: V24 Communication timeout"
0008 FE7B_E 4 00 0000000000 "CARD READER: Initialization failed"
AA08 DEFA_W 4 00 0000000000 "USB/IDCU: DEFAULT_WARNING"
AA08 DEFA_E 4 00 0000000000 "USB/IDCU: DEFAULT_ERROR"
AA08 8000_E 4 00 0000000000 "USB/IDCU: Unexpected descriptor was reported from USB device"
AA08 8001_E 4 00 0000000000 "USB/IDCU: Device not found"
AA08 8002_E 4 00 0000000000 "USB/IDCU: Not enough memory available"
AA08 8003_E 4 00 0000000000 "USB/IDCU: It was no endpoint found in the descriptor"
AA08 8004_E 4 00 0000000000 "USB/IDCU: The creation of the list of USB devices failed"
AA08 FE09_E 4 00 0000000000 "USB/IDCU: USB read command could not be executed in the specified monitoring
time"
AA08 FE0A_E 4 00 0000000000 "USB/IDCU: USB READ command is cancelled by the user"
AA08 FE89_E 4 00 0000000000 "USB/IDCU: The pointer pData is illegal"
AA08 FE9C_E 4 00 0000000000 "USB/IDCU: The length in DataSize is 0 (zero)"
AA08 0001_E 4 00 0000000000 "USB/IDCU: CRC error has been detected"
AA08 0002_E 4 00 0000000000 "USB/IDCU: Bit stuffing error has been detected"
AA08 0003_E 4 00 0000000000 "USB/IDCU: DATA toggle mismatch has been detected"
AA08 0004_E 4 00 0000000000 "USB/IDCU: STALLPID has been detected, error is reported by the USB host controller"
AA08 0005_E 4 00 0000000000 "USB/IDCU: USB device is not responding, error is reported by the USB host"
AA08 0006_E 4 00 0000000000 "USB/IDCU: PID check has failed, error is reported by the USB host controller"
408 October 2004 U25604-J-Z745-1-7600


AA08 0007_E 4 00 0000000000 "USB/IDCU: Unexpected PID detected, error is reported by the USB host"
AA08 0008_E 4 00 0000000000 "USB/IDCU: Data overrun error detected, error is reported by the USB host"
AA08 0009_E 4 00 0000000000 "USB/IDCU: Data underrun error detected, error is reported by the USB host"
AA08 000A_E 4 00 0000000000 "USB/IDCU: Error code is reserved by the USB host controller driver"
AA08 000B_E 4 00 0000000000 "USB/IDCU: Error code is reserved by the USB host controller driver"
AA08 000C_E 4 00 0000000000 "USB/IDCU: Buffer overrun has been detected, error is reported by the USB host"
AA08 000D_E 4 00 0000000000 "USB/IDCU: Buffer underrun has been detected, error is reported by the USB host"
AA08 000F_E 4 00 0000000000 "USB/IDCU: Buffer was not accessed, error is reported by the USB host"
AA08 0010_E 4 00 0000000000 "USB/IDCU: FIFO error has been detected, PCI bus latency was too long"
AA08 0011_E 4 00 0000000000 "USB/IDCU: XACT error has been detected, error is reported by the USB host"
AA08 0012_E 4 00 0000000000 "USB/IDCU: Device is babbling, data transfer phase exceeds the USB frame length"
AA08 0013_E 4 00 0000000000 "USB/IDCU: Data buffer error has been detected, error is reported by the USB host"
AA08 0030_E 4 00 0000000000 "USB/IDCU: Endpoint has been halted by the USB bus driver USBD"
AA08 0100_E 4 00 0000000000 "USB/IDCU: Memory allocation attempt has failed, error is reported by the USB bus"
AA08 0200_E 4 00 0000000000 "USB/IDCU: Invalid URB function code has been passed, error is reported by the USB"
AA08 0300_E 4 00 0000000000 "USB/IDCU: Invalid parameter has been passed, error is reported by the USB bus"
AA08 0400_E 4 00 0000000000 "USB/IDCU: There are data transfer requests pending for the device"
AA08 0500_E 4 00 0000000000 "USB/IDCU: Request has failed, error is reported by the USB bus driver USBD"
AA08 0600_E 4 00 0000000000 "USB/IDCU: Invalid pipe handle has been passed, error is reported by the USB bus"
AA08 0700_E 4 00 0000000000 "USB/IDCU: There is not enough bandwidth available, error is reported by the USB bus"
AA08 0800_E 4 00 0000000000 "USB/IDCU: Internal host controller error has been detected"
AA08 0900_E 4 00 0000000000 "USB/IDCU: Short transfer has been detected, error is reported by the USB bus"
AA08 0A00_E 4 00 0000000000 "USB/IDCU: Bad start frame has been specified, error is reported by the USB bus"
AA08 0B00_E 4 00 0000000000 "USB/IDCU: Asynchronous request has failed, error is reported by the USB bus driver"
AA08 0C00_E 4 00 0000000000 "USB/IDCU: USB frame control is currently owned, error is reported by the USB bus"
AA08 0D00_E 4 00 0000000000 "USB/IDCU: USB frame control is currently not owned, error is reported by the USB"
AA08 0E00_E 4 00 0000000000 "USB/IDCU: Operation is not supported, error is reported by the USB bus driver"
AA08 0F00_E 4 00 0000000000 "USB/IDCU: Invalid configuration descriptor was reported by the device"
AA08 1000_E 4 00 0000000000 "USB/IDCU: Operation has failed, error is reported by the USBIO driver"
AA08 1001_E 4 00 0000000000 "USB/IDCU: Invalid input buffer has been passed to an IOCTL operation"
AA08 1002_E 4 00 0000000000 "USB/IDCU: Invalid output buffer has been passed to an IOCTL operation"
AA08 1003_E 4 00 0000000000 "USB/IDCU: There is not enough system memory available to complete the operation"
AA08 1004_E 4 00 0000000000 "USB/IDCU: There are read or write requests pending, error is reported by the USBIO"
AA08 1005_E 4 00 0000000000 "USB/IDCU: USB device is already configured, error is reported by the USBIO"
AA08 1006_E 4 00 0000000000 "USB/IDCU: The USB device is not configured, error is reported by the USBIO driver"
AA08 1007_E 4 00 0000000000 "USB/IDCU: There are open pipes, error is reported by the USBIO driver"
AA08 1008_E 4 00 0000000000 "USB/IDCU: Either the handle is already bound to a pipe"
AA08 1009_E 4 00 0000000000 "USB/IDCU: Handle is not bound to a pipe, error is reported by the USBIO driver"
AA08 100A_E 4 00 0000000000 "USB/IDCU: USB device has been removed from the system"
AA08 100B_E 4 00 0000000000 "USB/IDCU: Specified control code is not supported"
AA08 100C_E 4 00 0000000000 "USB/IDCU: Operation has been timed out, error is reported by the USBIO driver"
AA08 100D_E 4 00 0000000000 "USB/IDCU: Invalid recipient has been specified"
AA08 100E_E 4 00 0000000000 "USB/IDCU: Either an invalid request type has been specified"
AA08 100F_E 4 00 0000000000 "USB/IDCU: Invalid IOCTL code has been specified, error is reported by the USBIO"
AA08 1010_E 4 00 0000000000 "USB/IDCU: Direction of the data transfer request is not supported by that pipe"
AA08 1011_E 4 00 0000000000 "USB/IDCU: Number of asynchronous data packets specified in an asynchronous read"
AA08 1012_E 4 00 0000000000 "USB/IDCU: Memory resources are exhausted. This error is reported by the USBIO
driver"
AA08 1013_E 4 00 0000000000 "USB/IDCU: The specified pipe was not found in the current configuration"
AA08 1014_E 4 00 0000000000 "USB/IDCU: An invalid asynchronous data packet has been specified"
AA08 1015_E 4 00 0000000000 "USB/IDCU: There are not enough system resources to complete the operation"
AA08 1016_E 4 00 0000000000 "USB/IDCU: Specified interface was not found in the current configuration"
AA08 1017_E 4 00 0000000000 "USB/IDCU: Operation cannot be executed while the USB device is in the current state"
AA08 1018_E 4 00 0000000000 "USB/IDCU: Invalid parameter has been specified with an IOCTL operation"
AA08 1019_E 4 00 0000000000 "USB/IDCU: Evaluation interval of the USBIO DEMO version has expired"
AA08 101A_E 4 00 0000000000 "USB/IDCU: Invalid power state has been specified"
AA08 101B_E 4 00 0000000000 "USB/IDCU: Device has entered a power down state"
AA08 101C_E 4 00 0000000000 "USB/IDCU: API version reported by the USBIO driver does not match"
AA08 101D_E 4 00 0000000000 "USB/IDCU: Set configuration operation has failed, error is reported by the USBIO"
AA08 1080_E 4 00 0000000000 "USB/IDCU: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600 October 2004 409


AA08 1086_E 4 00 0000000000 "USB/IDCU: The operation has failed due to a restriction of the USBIO LIGHT version"
AA08 1100_E 4 00 0000000000 "USB/IDCU: The specified device object does not exist"
AA08 1102_E 4 00 0000000000 "USB/IDCU: Device object was opened, there is no valid handle to execute the opera-
tion"
AA08 1104_E 4 00 0000000000 "USB/IDCU: Enumeration of the specified devices has failed"
AA08 1105_E 4 00 0000000000 "USB/IDCU: Invalid parameter has been passed to a function"
AA08 1106_E 4 00 0000000000 "USB/IDCU: Library setupapi.dll could not be loaded"
AA08 2000_E 4 00 0000000000 "USB/IDCU: Set configuration request has failed"
AA08 3000_E 4 00 0000000000 "USB/IDCU: Buffer is too small, error is reported by the USB bus driver USBD"
AA08 4000_E 4 00 0000000000 "USB/IDCU: Interface was not found, error is reported by the USB bus driver USBD"
AA08 5000_E 4 00 0000000000 "USB/IDCU: Invalid pipe flags have been specified"
AA08 6000_E 4 00 0000000000 "USB/IDCU: Operation has been timed out, error is reported by the USB bus driver"
AA08 7000_E 4 00 0000000000 "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)
class Deposit Module. Class AA17 is the USB class assigned to Deposit
Module.
Table 105: Deposit Module (Class: 0017/AA17)

0017 DEFA_W 2 00 0000000000000000000000 "DEPOSIT: DEFAULT_WARNING"
0017 DEFA_E 4 00 0000000000000000000000 "DEPOSIT: DEFAULT_ERROR"
0017 0001_E 2 00 0000000000000000000000 "DEPOSIT: Device handler was configured to switch LEDs"
0017 0002_E 2 07 0000000000000000000000 "DEPOSIT: There is no firmware loaded"
0017 0003_E 2 07 0000000000000000000000 "DEPOSIT: Cannot open or read the firmware file on disk"
0017 0004_E 2 07 0000000000000000000000 "DEPOSIT: API-Function CscDpsOpen check validity of FW on Disk"
0017 1420_E 4 00 0000000000000000000000 "DEPOSIT: Communication problem"
0017 8000_E 2 07 0000000000000000000000 "DEPOSIT: Undefined error code"
0017 8001_E 2 07 0000000000000000000000 "DEPOSIT: The DLL command specification is invalid"
0017 8002_E 2 07 0000000000000000000000 "DEPOSIT: The DLL command specification is invalid"
0017 8003_E 2 00 8000000000000000000000 "DEPOSIT: Deposit cassette not installed correctly"
0017 8004_E 2 01 0000000000000000000000 "DEPOSIT: Job cannot be executed because envelope in transport path"
0017 8005_E 2 01 0000000000000000000000 "DEPOSIT: Envelope jammed in transport path"
0017 8006_E 2 00 0000000000000000000000 "DEPOSIT: Operator did not insert envelope during monitoring period"
0017 8007_E 2 07 0000000000000000000000 "DEPOSIT: The envelope starting the feed operation"
0017 8008_E 2 02 0000000000000000000000 "DEPOSIT: Undefined status Defective sensor"
0017 8009_E 2 02 0000000000000000000000 "DEPOSIT: The dispensed envelope has not been"
0017 800A_E 2 04 0000000000000000000000 "DEPOSIT: Shutter could not be closed"
0017 800B_E 2 00 0000000000000000000000 "DEPOSIT: No envelopes available any longer"
0017 800C_E 2 01 0000000000000000000000 "DEPOSIT: Dispenser sensor could not detect the envelope"
0017 800D_E 2 08 0000000000000000000000 "DEPOSIT: End of the envelope reached before all chars could be printed"
0017 800E_E 2 07 0000000000000000000000 "DEPOSIT: Print unit motor error"
0017 800F_E 2 07 0000000000000000000000 "DEPOSIT: Envelope under print head sensor could not detect envelope"
0017 8010_E 2 01 0000000000000000000000 "DEPOSIT: Envelope in printer conveyor sensor could not detect enve-
lope"
0017 8011_E 2 07 0000000000000000000000 "DEPOSIT: Motor problem of conveyer transport"
0017 8012_E 2 01 0000000000000000000000 "DEPOSIT: Envelope in conveyor transport entry sensor could not detect
envelope"
0017 8013_E 2 01 0000000000000000000000 "DEPOSIT: Envelope in middle of conveyor transport sensor could not
detect envelope"
0017 8014_E 2 01 0000000000000000000000 "DEPOSIT: Envelope in conveyor transport exit sensor could not detect
envelope"
0017 8015_E 2 08 0000000000000000000000 "DEPOSIT: No connection between print unit and conveyor transport"
0017 8016_E 2 07 0000000000000000000000 "DEPOSIT: No envelope dispenser or programming error"
0017 8017_E 2 08 0000000000000000000000 "DEPOSIT: Print head not locked or not available"
0017 8018_E 2 07 0000000000000000000000 "DEPOSIT: The inserted envelope is too long"
0017 8019_E 2 07 0000000000000000000000 "DEPOSIT: No envelope detected after command"
0017 8020_E 2 01 0000000000000000000000 "DEPOSIT: Failure of Envelope in shutter sensor"
0017 8021_E 2 07 0000000000000000000000 "DEPOSIT: Error when opening the bandage"
0017 8022_E 2 07 0000000000000000000000 "DEPOSIT: Error when closing the bandage"
0017 8023_E 2 06 0000000000000000000000 "DEPOSIT: Operator did not remove the offered envelope"
0017 8024_E 2 02 0000000000000000000000 "DEPOSIT: An error has occurred in the shutter"
0017 8025_E 2 01 0000000000000000000000 "DEPOSIT: An error has occurred on the bandage"
0017 80F0_E 2 00 0000000000000000000000 "DEPOSIT: Job cancelled by CANCEL"
0017 8102_E 2 07 0000000000000000000000 "DEPOSIT: Cannot access full length of data area in a structure"
0017 8104_E 2 07 0000000000000000000000 "DEPOSIT: Active function cannot be cancelled"
0017 8105_E 2 07 0000000000000000000000 "DEPOSIT: Cannot open the firmware file"
0017 8106_E 2 07 0000000000000000000000 "DEPOSIT: Cannot read the firmware file to be loaded"
0017 8107_E 2 07 0000000000000000000000 "DEPOSIT: Detect invalid firmware file data"
0017 8108_E 2 07 0000000000000000000000 "DEPOSIT: Detect an invalid checksum of the firmware file data"
0017 8200_E 2 07 0000000000000000000000 "DEPOSIT: A V24 WRITE command could not be executed"
U25604-J-Z745-1-7600 October 2004 411


0017 8201_E 2 07 0000000000000000000000 "DEPOSIT: A V24 READ command could not be executed"
0017 8202_E 2 07 0000000000000000000000 "DEPOSIT: Max no. of repeat transmissions reached"
0017 8203_E 2 07 0000000000000000000000 "DEPOSIT: Max no. of receive repeats has been reached"
0017 8204_E 2 07 0000000000000000000000 "DEPOSIT: Repetition counter expired"
0017 8205_E 2 07 0000000000000000000000 "DEPOSIT: The received acknowledge type is invalid"
0017 8206_E 2 07 0000000000000000000000 "DEPOSIT: Repetition counter expired"
0017 8207_E 2 07 0000000000000000000000 "DEPOSIT: Expected block length does not match transmitted block
length"
0017 8208_E 2 07 0000000000000000000000 "DEPOSIT: Error occurred during the CscDpsEntry job"
0017 8209_E 2 00 0000000000000000000000 "DEPOSIT: The CscDpsEntry job was cancelled by the user"
0017 8300_E 2 00 0000000000000000000000 "DEPOSIT: Wrong value for LED in Registry/CSCINI with CSCDPS"
0017 FE08_E 4 00 0000000000000000000000 "DEPOSIT: V24 Communication timeout"
0017 FE09_E 4 00 0000000000000000000000 "DEPOSIT: V24 Communication timeout"
0017 FE85_E 4 00 0000000000000000000000 "DEPOSIT: Communication problem"
AA17 DEFA_W 4 00 0000000000000000000000 "USB/DEP: DEFAULT_WARNING"
AA17 DEFA_E 4 00 0000000000000000000000 "USB/DEP: DEFAULT_ERROR"
AA17 8000_E 4 00 0000000000000000000000 "USB/DEP: Unexpected descriptor was reported from USB device"
AA17 8001_E 4 00 0000000000000000000000 "USB/DEP: Device not found"
AA17 8002_E 4 00 0000000000000000000000 "USB/DEP: Not enough memory available"
AA17 8003_E 4 00 0000000000000000000000 "USB/DEP: It was no endpoint found in the descriptor"
AA17 8004_E 4 00 0000000000000000000000 "USB/DEP: The creation of the list of USB devices failed"
AA17 FE09_E 4 00 0000000000000000000000 "USB/DEP: USB read command could not be executed in the specified
monitoring time"
AA17 FE0A_E 4 00 0000000000000000000000 "USB/DEP: USB READ command is cancelled by the user"
AA17 FE89_E 4 00 0000000000000000000000 "USB/DEP: The pointer pData is illegal"
AA17 FE9C_E 4 00 0000000000000000000000 "USB/DEP: The length in DataSize is 0 (zero)"
AA17 0001_E 4 00 0000000000000000000000 "USB/DEP: CRC error has been detected"
AA17 0002_E 4 00 0000000000000000000000 "USB/DEP: Bit stuffing error has been detected"
AA17 0003_E 4 00 0000000000000000000000 "USB/DEP: DATA toggle mismatch has been detected"
AA17 0004_E 4 00 0000000000000000000000 "USB/DEP: STALLPID has been detected, error is reported by the USB
host controller"
AA17 0005_E 4 00 0000000000000000000000 "USB/DEP: USB device is not responding, error is reported by the USB
host"
AA17 0006_E 4 00 0000000000000000000000 "USB/DEP: PID check has failed, error is reported by the USB host con-
troller"
AA17 0007_E 4 00 0000000000000000000000 "USB/DEP: Unexpected PID detected, error is reported by the USB host"
AA17 0008_E 4 00 0000000000000000000000 "USB/DEP: Data overrun error detected, error is reported by the USB
host"
AA17 0009_E 4 00 0000000000000000000000 "USB/DEP: Data underrun error detected, error is reported by the USB
host"
AA17 000A_E 4 00 0000000000000000000000 "USB/DEP: Error code is reserved by the USB host controller driver"
AA17 000B_E 4 00 0000000000000000000000 "USB/DEP: Error code is reserved by the USB host controller driver"
AA17 000C_E 4 00 0000000000000000000000 "USB/DEP: Buffer overrun has been detected, error is reported by the
USB host"
AA17 000D_E 4 00 0000000000000000000000 "USB/DEP: Buffer underrun has been detected, error is reported by the
USB host"
AA17 000F_E 4 00 0000000000000000000000 "USB/DEP: Buffer was not accessed, error is reported by the USB host"
AA17 0010_E 4 00 0000000000000000000000 "USB/DEP: FIFO error has been detected, PCI bus latency was too long"
AA17 0011_E 4 00 0000000000000000000000 "USB/DEP: XACT error has been detected, error is reported by the USB
host"
AA17 0012_E 4 00 0000000000000000000000 "USB/DEP: Device is babbling, data transfer phase exceeds the USB
frame length"
AA17 0013_E 4 00 0000000000000000000000 "USB/DEP: Data buffer error has been detected, error is reported by the
USB host"
AA17 0030_E 4 00 0000000000000000000000 "USB/DEP: Endpoint has been halted by the USB bus driver USBD"
AA17 0100_E 4 00 0000000000000000000000 "USB/DEP: Memory allocation attempt has failed, error is reported by the
USB bus"
AA17 0200_E 4 00 0000000000000000000000 "USB/DEP: Invalid URB function code has been passed, error is reported
by the USB"
AA17 0300_E 4 00 0000000000000000000000 "USB/DEP: Invalid parameter has been passed, error is reported by the
USB bus"
AA17 0400_E 4 00 0000000000000000000000 "USB/DEP: There are data transfer requests pending for the device"
AA17 0500_E 4 00 0000000000000000000000 "USB/DEP: Request has failed, error is reported by the USB bus driver
USBD"
412 October 2004 U25604-J-Z745-1-7600


AA17 0600_E 4 00 0000000000000000000000 "USB/DEP: Invalid pipe handle has been passed, error is reported by the
USB bus"
AA17 0700_E 4 00 0000000000000000000000 "USB/DEP: There is not enough bandwidth available, error is reported by
the USB bus"
AA17 0800_E 4 00 0000000000000000000000 "USB/DEP: Internal host controller error has been detected"
AA17 0900_E 4 00 0000000000000000000000 "USB/DEP: Short transfer has been detected, error is reported by the USB
bus"
AA17 0A00_E 4 00 0000000000000000000000 "USB/DEP: Bad start frame has been specified, error is reported by the
USB bus"
AA17 0B00_E 4 00 0000000000000000000000 "USB/DEP: Asynchronous request has failed, error is reported by the
USB bus driver"
AA17 0C00_E 4 00 0000000000000000000000 "USB/DEP: USB frame control is currently owned, error is reported by
the USB bus"
AA17 0D00_E 4 00 0000000000000000000000 "USB/DEP: USB frame control is currently not owned, error is reported
by the USB"
AA17 0E00_E 4 00 0000000000000000000000 "USB/DEP: Operation is not supported, error is reported by the USB bus
driver"
AA17 0F00_E 4 00 0000000000000000000000 "USB/DEP: Invalid configuration descriptor was reported by the device"
AA17 1000_E 4 00 0000000000000000000000 "USB/DEP: Operation has failed, error is reported by the USBIO driver"
AA17 1001_E 4 00 0000000000000000000000 "USB/DEP: Invalid input buffer has been passed to an IOCTL operation"
AA17 1002_E 4 00 0000000000000000000000 "USB/DEP: Invalid output buffer has been passed to an IOCTL operation"
AA17 1003_E 4 00 0000000000000000000000 "USB/DEP: There is not enough system memory available to complete the
operation"
AA17 1004_E 4 00 0000000000000000000000 "USB/DEP: There are read or write requests pending, error is reported by
the USBIO"
AA17 1005_E 4 00 0000000000000000000000 "USB/DEP: USB device is already configured, error is reported by the
USBIO"
AA17 1006_E 4 00 0000000000000000000000 "USB/DEP: The USB device is not configured, error is reported by the
USBIO driver"
AA17 1007_E 4 00 0000000000000000000000 "USB/DEP: There are open pipes, error is reported by the USBIO driver"
AA17 1008_E 4 00 0000000000000000000000 "USB/DEP: Either the handle is already bound to a pipe"
AA17 1009_E 4 00 0000000000000000000000 "USB/DEP: Handle is not bound to a pipe, error is reported by the USBIO
driver"
AA17 100A_E 4 00 0000000000000000000000 "USB/DEP: USB device has been removed from the system"
AA17 100B_E 4 00 0000000000000000000000 "USB/DEP: Specified control code is not supported"
AA17 100C_E 4 00 0000000000000000000000 "USB/DEP: Operation has been timed out, error is reported by the USBIO
driver"
AA17 100D_E 4 00 0000000000000000000000 "USB/DEP: Invalid recipient has been specified"
AA17 100E_E 4 00 0000000000000000000000 "USB/DEP: Either an invalid request type has been specified"
AA17 100F_E 4 00 0000000000000000000000 "USB/DEP: Invalid IOCTL code has been specified, error is reported by
the USBIO"
AA17 1010_E 4 00 0000000000000000000000 "USB/DEP: Direction of the data transfer request is not supported by that
pipe"
AA17 1011_E 4 00 0000000000000000000000 "USB/DEP: Number of asynchronous data packets specified in an asyn-
chronous read"
AA17 1012_E 4 00 0000000000000000000000 "USB/DEP: Memory resources are exhausted. This error is reported by the
USBIO driver"
AA17 1013_E 4 00 0000000000000000000000 "USB/DEP: The specified pipe was not found in the current configura-
tion"
AA17 1014_E 4 00 0000000000000000000000 "USB/DEP: An invalid asynchronous data packet has been specified"
AA17 1015_E 4 00 0000000000000000000000 "USB/DEP: There are not enough system resources to complete the opera-
tion"
AA17 1016_E 4 00 0000000000000000000000 "USB/DEP: Specified interface was not found in the current configura-
tion"
AA17 1017_E 4 00 0000000000000000000000 "USB/DEP: Operation cannot be executed while the USB device is in the
current state"
AA17 1018_E 4 00 0000000000000000000000 "USB/DEP: Invalid parameter has been specified with an IOCTL opera-
tion"
AA17 1019_E 4 00 0000000000000000000000 "USB/DEP: Evaluation interval of the USBIO DEMO version has
expired"
AA17 101A_E 4 00 0000000000000000000000 "USB/DEP: Invalid power state has been specified"
AA17 101B_E 4 00 0000000000000000000000 "USB/DEP: Device has entered a power down state"
AA17 101C_E 4 00 0000000000000000000000 "USB/DEP: API version reported by the USBIO driver does not match"
AA17 101D_E 4 00 0000000000000000000000 "USB/DEP: Set configuration operation has failed, error is reported by the
USBIO"
AA17 1080_E 4 00 0000000000000000000000 "USB/DEP: Operation has failed due to a restriction of the USBIO LIGHT
version"
U25604-J-Z745-1-7600 October 2004 413


version"
version"
version"
version"
version"
AA17 1086_E 4 00 0000000000000000000000 "USB/DEP: The operation has failed due to a restriction of the USBIO
LIGHT version"
version"
AA17 1100_E 4 00 0000000000000000000000 "USB/DEP: The specified device object does not exist"
AA17 1102_E 4 00 0000000000000000000000 "USB/DEP: Device object was opened, there is no valid handle to execute
the operation"
AA17 1104_E 4 00 0000000000000000000000 "USB/DEP: Enumeration of the specified devices has failed"
AA17 1105_E 4 00 0000000000000000000000 "USB/DEP: Invalid parameter has been passed to a function"
AA17 1106_E 4 00 0000000000000000000000 "USB/DEP: Library setupapi.dll could not be loaded"
AA17 2000_E 4 00 0000000000000000000000 "USB/DEP: Set configuration request has failed"
AA17 3000_E 4 00 0000000000000000000000 "USB/DEP: Buffer is too small, error is reported by the USB bus driver
USBD"
AA17 4000_E 4 00 0000000000000000000000 "USB/DEP: Interface was not found, error is reported by the USB bus
driver USBD"
AA17 5000_E 4 00 0000000000000000000000 "USB/DEP: Invalid pipe flags have been specified"
AA17 6000_E 4 00 0000000000000000000000 "USB/DEP: Operation has been timed out, error is reported by the USB
bus driver"
AA17 7000_E 4 00 0000000000000000000000 "USB/DEP: USB device is gone, error is reported by the USB bus driver
USBD"
Vandal Guard (Class: 0015)
class Vandal Guard (Panel Protection Door (PPD)). This device is used in
CSC450 ATM’s only.
Table 106: Vandal Guard (Class: 0015)

0015 DEFA_W 2 00 0000 "VANDAL GUARD: DEFAULT_WARNING"
0015 DEFA_E 4 00 0000 "VANDAL GUARD: DEFAULT_ERROR"
0015 8000_E 2 03 0100 "VANDAL GUARD: Unknown internal error has occurred in FW"
0015 8020_E 2 03 0100 "VANDAL GUARD: Block ID wrong"
0015 8021_E 2 03 0100 "VANDAL GUARD: Device number wrong"
0015 8022_E 2 03 0100 "VANDAL GUARD: Job specification wrong"
0015 8023_E 2 03 0100 "VANDAL GUARD: Job longer than receive buffer"
0015 8024_E 2 03 0100 "VANDAL GUARD: Syntax error in job specification"
0015 8030_E 2 03 0100 "VANDAL GUARD: No motion messages when door is opened"
0015 8040_E 2 03 0100 "VANDAL GUARD: The hardware error cannot be specified closer"
0015 8041_E 2 03 0100 "VANDAL GUARD: E-PROM faulty"
0015 8043_E 2 03 0100 "VANDAL GUARD: Processor faulty"
0015 8044_E 2 03 0100 "VANDAL GUARD: Checksum error in hardware RAM"
0015 8050_E 2 02 0201 "VANDAL GUARD: The door could not be fully opened"
414 October 2004 U25604-J-Z745-1-7600


0015 8051_E 2 01 0100 "VANDAL GUARD: Door cannot be closed completely"
0015 8052_E 2 03 0100 "VANDAL GUARD: Contact bar without function"
0015 8053_E 2 03 0100 "VANDAL GUARD: Light barrier is dirty or faulty"
0015 8054_E 2 03 0100 "VANDAL GUARD: Door is difficult to operate"
0015 8055_E 2 03 0100 "VANDAL GUARD: Firmware not loaded or started"
0015 80E0_E 2 03 0100 "VANDAL GUARD: Charaters 1-3 not equal to decimal digits"
0015 80E1_E 2 03 0100 "VANDAL GUARD: Block length not in valid area (3-250)"
0015 80E2_E 2 03 0100 "VANDAL GUARD: Block length not equal to received block length"
0015 80E3_E 2 03 0100 "VANDAL GUARD: Invalid Block ID (N,E)"
0015 80E4_E 2 03 0100 "VANDAL GUARD: Invalid Device ID"
0015 80E5_E 2 03 0100 "VANDAL GUARD: Invalid Job ID"
0015 80E6_E 2 03 0100 "VANDAL GUARD: Invalid Job parameter"
0015 80E7_E 2 03 0100 "VANDAL GUARD: The last command has not been processed yet"
0015 80E8_E 2 03 0100 "VANDAL GUARD: Firmware not loaded or started"
0015 80E9_E 2 03 0100 "VANDAL GUARD: Wrong file length"
0015 80EA_E 2 03 0100 "VANDAL GUARD: Memory for program module too small"
0015 80EB_E 2 03 0100 "VANDAL GUARD: Invalid file check charater"
0015 80EC_E 2 03 0100 "VANDAL GUARD: Hardware not functioning/faulty"
0015 8101_E 2 03 0100 "VANDAL GUARD: OS/2 reports error during memory request"
0015 8102_E 2 03 0100 "VANDAL GUARD: Wrong/undefined charater job acknowledgment"
0015 8103_E 2 03 0100 "VANDAL GUARD: Invalid data in response from peripheral controller"
0015 8104_E 2 03 0100 "VANDAL GUARD: Invalid MODSEG ID in FRM file on the system"
0015 8105_E 2 03 0100 "VANDAL GUARD: The file *CTF was not found"
0015 8106_E 2 03 0100 "VANDAL GUARD: The file *FRM was not found"
0015 8107_E 2 03 0100 "VANDAL GUARD: Error when opening a *CTF file"
0015 8108_E 2 03 0100 "VANDAL GUARD: Error when opening a *FRM file"
0015 8109_E 2 03 0100 "VANDAL GUARD: Invalid data in teh *CTF file"
Motorized Door (Class: 000E)
class Motorized Door. This device is used in CSC250/550 old series ATM’s only.
Table 107: Motorized Door (Class: 000E)

000E DEFA_W 2 09 00000000000000000000 "DOOR MODULE: DEFAULT_WARNING"
000E DEFA_E 2 09 00000000000000000000 "DOOR MODULE: DEFAULT_ERROR"
000E 8020_E 2 09 00000000000000000000 "DOOR MODULE: Block ID wrong"
000E 8021_E 2 09 00000000000000000000 "DOOR MODULE: Device number wrong"
000E 8022_E 2 09 00000000000000000000 "DOOR MODULE: Job specification wrong"
000E 8023_E 2 09 00000000000000000000 "DOOR MODULE: Return buffer too small"
000E 8024_E 2 09 00000000000000000000 "DOOR MODULE: Syntax error in job specification"
000E 8025_E 2 09 00000000000000000000 "DOOR MODULE: The last command has not been processed yet"
000E 8030_E 2 09 00000000000000000000 "DOOR MODULE: The door could not be fully opened"
000E 8031_E 2 09 00000000000000000000 "DOOR MODULE: Door cannot be closed completely Door is blocked"
000E 8040_E 2 09 00000000000000000000 "DOOR MODULE: The hardware error cannot be specified closer"
000E 8041_E 2 09 00000000000000000000 "DOOR MODULE: E-PROM faulty"
000E 8042_E 2 09 00000000000000000000 "DOOR MODULE: EE-PROM faulty"
000E 8043_E 2 09 00000000000000000000 "DOOR MODULE: Processor faulty"
000E 8045_E 2 09 00000000000000000000 "DOOR MODULE: One or more light barriers are dirty or faulty"
000E 8046_E 2 09 00000000000000000000 "DOOR MODULE: Door open/close issued more than 3 times quickly"
U25604-J-Z745-1-7600 October 2004 415


000E 8050_E 2 09 00000000000000000000 "DOOR MODULE: Values of a number of photosensors are below the min-
imum value"
000E 8051_E 2 09 00000000000000000000 "DOOR MODULE: The light bulb in the cash output tray is defective"
000E 8052_E 2 09 00000000000000000000 "DOOR MODULE: Door does not reach the open end position when
opened"
000E 8100_E 2 09 00000000000000000000 "DOOR MODULE: OS/2 report an error when requesting memory for a
data buffer"
000E 8101_E 2 09 00000000000000000000 "DOOR MODULE: The status of a non-existent light barrier was requested"
000E 8102_E 2 09 00000000000000000000 "DOOR MODULE: The MDM hardware does not respond at OPEN"
000E 8FFF_E 2 09 00000000000000000000 "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 DEFA_W 2 00 00000000 "PRINTER: DEFAULT_WARNING"
0032 DEFA_E 4 00 00000000 "PRINTER: DEFAULT_ERROR"
0032 1420_E 4 00 00000000 "PRINTER: Communication problem"
0032 1424_E 2 00 00000000 "PRINTER: The device is currently locked by another user"
0032 8001_E 2 00 00000000 "PRINTER: If no error found"
0032 8003_E 2 08 40000800 "PRINTER: Printer control code file could not be opened"
0032 8004_E 2 00 00000000 "PRINTER: Bad format of the printer control code file"
0032 8005_E 2 00 00000000 "PRINTER: Invalid format of the macro"
0032 8006_E 2 00 00000000 "PRINTER: The format file is not available"
0032 8007_E 2 08 20000800 "PRINTER: OPEN error of the format file"
0032 8008_E 2 00 00000000 "PRINTER: Bad format of the format file"
0032 8009_E 2 00 00000000 "PRINTER: Error while transmitting the status buffer"
0032 800A_E 2 00 00000000 "PRINTER: The print buffer is too small"
0032 800B_E 2 00 00000000 "PRINTER: No text from the FMT file was found"
0032 800C_E 2 00 00000000 "PRINTER: If no error found"
0032 800D_E 2 00 00000000 "PRINTER: If no error found"
0032 800E_E 2 00 00000000 "PRINTER: If no error found"
0032 800F_E 2 00 00000000 "PRINTER: Formatting error"
0032 8011_E 2 00 00000000 "PRINTER: The printer-specific DLL could not be opened"
0032 8013_E 2 00 00000000 "PRINTER: Unknown string format specification"
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 DEFA_W 2 00 00000000 "JRN/REC: DEFAULT_WARNING"
0033 DEFA_E 4 00 00000000 "JRN/REC: DEFAULT_ERROR"
0033 0001_W 2 00 00000000 "JRN/REC: Communication problem"
0033 0001_E 2 00 02000000 "JRN/REC: Receipt paper low warning"
0033 0002_E 2 00 02000000 "JRN/REC: Journal paper low warning"
0033 0003_E 2 16 00000002 "JRN/REC: Receipt still in output at OPEN on printer"
0033 1017_E 4 00 00000000 "JRN/REC: Communication problem"
0033 1420_E 4 00 00000000 "JRN/REC: Communication problem"
0033 8005_E 2 00 00000000 "JRN/REC: Wrong macro format"
0033 8009_E 2 08 40000800 "JRN/REC: Printer hardware error"
0033 8101_E 2 08 40000800 "JRN/REC: Loss of command after device error"
0033 8102_E 2 08 40000800 "JRN/REC: Hardware error in memory test (RAM and ROM)"
0033 8103_E 2 00 00000000 "JRN/REC: Syntax error in the ESCAPE sequence"
0033 8104_E 2 08 40000800 "JRN/REC: Parity error"
0033 8105_E 2 08 40000800 "JRN/REC: A checksum error is set"
0033 8106_E 2 08 40000800 "JRN/REC: Short-term power failed"
0033 8107_E 2 05 08000000 "JRN/REC: Paper-out condition or paper jam"
0033 8108_E 4 05 08000000 "JRN/REC: Loss of command after receipt paper end"
0033 8109_E 4 07 40000002 "JRN/REC: Receipt paper jam"
0033 810A_E 2 07 40000002 "JRN/REC: Loss of command after paper jam"
0033 810B_E 2 05 08000000 "JRN/REC: Paper-out condition or paper jam"
0033 810C_E 4 05 08000000 "JRN/REC: Loss of command after receipt paper end"
0033 810D_E 2 07 40000000 "JRN/REC: Journal paper tear"
0033 810E_E 2 07 40000000 "JRN/REC: Loss of command after receipt paper end"
0033 810F_E 2 08 40000800 "JRN/REC: The door is not properly closed"
0033 8110_E 2 08 40000800 "JRN/REC: Loss of command because of open CSC door"
0033 8112_E 2 08 40000800 "JRN/REC: Black dot mark not found"
0033 8201_E 2 08 40000800 "JRN/REC: Cannot open control file ND9X.INI"
0033 8202_E 2 08 40000800 "JRN/REC: Cannot read control file ND9X.INI"
0033 8203_E 2 08 40000800 "JRN/REC: Cannot open a file or checksum incorrect"
0033 8204_E 2 08 40000800 "JRN/REC: Cannot read the file to be loaded"
0033 8205_E 2 08 40000800 "JRN/REC: File to be loaded has invalid module id"
0033 8206_E 2 08 40000800 "JRN/REC: Expected response from firmware loader is incorrect"
0033 8207_E 2 08 40000800 "JRN/REC: Invalid logo type for ND9C"
0033 8208_E 2 08 40000800 "JRN/REC: Loaded file does not fit to printer hardware"
0033 FE08_E 4 08 40000800 "JRN/REC: V24 Communication timeout"
0033 FE09_E 4 08 40000800 "JRN/REC: V24 Communication timeout"
U25604-J-Z745-1-7600 October 2004 417

Printer ND75/75S/94 (Class: 0034)
class 0034.

0034 DEFA_W 2 00 0000000000000000 "ND94: DEFAULT_WARNING"
0034 DEFA_E 4 00 0000000000000000 "ND94: DEFAULT_ERROR"
0034 0001_E 2 00 0200000000000000 "ND94: Paper-low condition"
0034 0002_E 2 00 0200000000000000 "ND94: Weekend limit reached"
0034 0003_E 2 00 4000000000000000 "ND94: FF command caused a feed to 1st line of 10th document"
0034 0004_E 2 00 4000000000000000 "ND94: The set limit for the reject box has been exceeded"
0034 8100_E 2 02 4000000000000000 "ND94: Error in the low-voltage power supply"
0034 8101_E 2 02 4000000000000000 "ND94: The carrier was moved manually"
0034 8102_E 2 02 4000000000000000 "ND94: Error in memory test(RAM and ROM)"
0034 8103_E 2 07 0800000000000000 "ND94: The paper is used up completely"
0034 8104_E 2 04 0400000000000000 "ND94: Paper jam, bad/missing mark on paper"
0034 8105_E 2 02 4000080000000000 "ND94: Reset switch on the drum is faulty"
0034 8106_E 2 01 4000000100000000 "ND94: The cutter is binding"
0034 8107_E 2 05 4000010000000000 "ND94: Paper jam in paper path"
0034 8108_E 2 00 4000000000000000 "ND94: FF command caused a feed to 1st line of 10th document"
0034 8109_E 2 05 4000010000000000 "ND94: Receipt(s) not removed before issuing a new print job"
0034 810A_E 2 00 4000000000000000 "ND94: Access to a non-existent font module"
0034 810B_E 2 05 4000010000000000 "ND94: Forms in gripper after 2 reject attempts"
0034 810C_E 2 00 4000000000000000 "ND94: External light when adjusting photosensor"
0034 810D_E 2 01 4000100000000000 "ND94: Rocker does not return to home position after cutting"
0034 810E_E 2 00 4000000000000000 "ND94: Remove stacker door does not open"
0034 810F_E 2 02 4000400000000000 "ND94: Cheque counter in Backup RAM deleted"
0034 8110_E 2 04 4000000000000000 "ND94: Print control mark not found"
0034 8111_E 2 02 4000080000000000 "ND94: Printer hardware error"
0034 8112_E 2 02 4000080000000000 "ND94: If no error found"
Printer ND79 (Class: 0035)
class 0035.

0035 DEFA_W 2 00 0000000000000000 "ND79: DEFAULT_WARNING"
0035 DEFA_E 4 00 0000000000000000 "ND79: DEFAULT_ERROR"
0035 0001_E 2 00 0200000000000000 "ND79: Receipt paper low warning"
0035 0003_E 2 05 4000010000000000 "ND79: Still a receipt in the output chute at an OPEN"
0035 0004_E 2 00 0200000000000000 "ND79: Receipt paper low warning (last receipt printing)"
0035 8101_E 2 02 4000000000000000 "ND79: Loss of command after device error"
0035 8103_E 2 02 4000000000000000 "ND79: Syntax error in the ESCAPE sequence for loading LOGO"
418 October 2004 U25604-J-Z745-1-7600


0035 8104_E 2 02 4000000000000000 "ND79: A parity error is returned from a printer"
0035 8106_E 2 23 4000000000000000 "ND79: Short-term power failed on during operation"
0035 8107_E 2 07 0800000000000000 "ND79: Paper-out condition or paper jam"
0035 8108_E 2 07 0800000000000000 "ND79: Loss of command after receipt paper end"
0035 8109_E 2 05 4000010000000000 "ND79: Receipt paper jam"
0035 810A_E 2 05 4000010000000000 "ND79: Loss of command after paper jam"
0035 8112_E 2 00 4000010000000000 "ND79: The printer is in service position"

0035 8113_E 2 00 4000010000000000 "ND79: Defective control instruction"
0035 8114_E 2 00 4000010000000000 "ND79: Job lost while printer in service position"
Printer ND99 (Class: 0038)
class 0038.

0038 DEFA_W 2 00 00000000 "RECEIPT: DEFAULT_WARNING"
0038 DEFA_E 4 00 00000000 "RECEIPT: DEFAULT_ERROR"
0038 0001_E 2 00 02000000 "RECEIPT: Receipt paper low warning"
0038 0002_E 2 08 40000000 "RECEIPT: API function CscPrtOpen checks FW load file SWC728HEX"
0038 0003_E 2 08 40000000 "RECEIPT: FW on disk different than SW loaded in printer"
0038 0004_E 2 08 40000000 "RECEIPT: There is no firmware loaded"
0038 0005_E 2 08 40000000 "RECEIPT: Loaded PRT FW has a release smaller than 0305"
0038 1420_E 4 00 00000000 "PRINTER: Communication problem"
0038 1424_E 4 00 00000000 "PRINTER: The device is currently locked by another user"
0038 8100_E 2 03 40000004 "RECEIPT: Hardware error receipt presenter module"
0038 8101_E 2 03 40000004 "RECEIPT: Printer cannot recognize a top-of-form mark"
0038 8102_E 4 09 40000000 "RECEIPT: The print head is lifted"
0038 8103_E 2 08 00000000 "RECEIPT: Syntax error in ESCAPE sequence for loading LOGO"
0038 8104_E 2 08 00000000 "RECEIPT: A parity error is returned from a printer"
0038 8105_E 2 08 40000000 "RECEIPT: HW error occured at power ON (self-test)"
0038 8106_E 2 08 40000000 "RECEIPT: Short-term power failed on during operation"
0038 8107_E 2 05 08000000 "RECEIPT: Paper-out, current form still printed"
0038 8108_E 2 00 40000000 "RECEIPT: Non-existing user-defined character font selected"
0038 8109_E 2 08 40000000 "RECEIPT: The printer buffer is overflow"
0038 810A_E 2 08 40000000 "RECEIPT: Loss of command"
0038 810B_E 2 01 40010000 "RECEIPT: Cutter not in home position"
0038 810C_E 2 08 40000000 "RECEIPT: Syntax error in ESCAPE sequence for loading user chars."
0038 810D_E 2 08 40000000 "RECEIPT: Firmware HEX-file SWC728HEX has no valid firmware version"
0038 810E_E 2 08 40000000 "RECEIPT: Recognized a faulty firmware load file SWC728HEX"
0038 810F_E 2 08 00000000 "RECEIPT: No firmware is loaded"
0038 8110_E 2 08 40000000 "RECEIPT: Loaded PRT FW has a release smaller than 0305"
0038 FE08_E 4 08 40000000 "RECEIPT: V24 Communication timeout"
0038 FE09_E 4 08 40000000 "RECEIPT: V24 Communication timeout"
0038 FE0B_E 4 08 40000000 "RECEIPT: V24 Communication timeout"
0038 FE85_E 4 08 40000000 "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 DEFA_W 2 00 00000000 "ND/TH97: Default warning if no CSCW32 error found"
0039 DEFA_E 4 00 00000000 "ND/TH97: Default error if no CSCW32 error found"
0039 1006_E 2 00 00000000 "ND/TH97: Error"
0039 1427_E 1 00 00000000 "ND/TH97: Printer not accessable, occupied by another user"
0039 8100_E 2 00 00000000 "ND/TH97: Printer is not able to print graphices"
0039 8101_E 2 00 00000000 "ND/TH97: Application tries to get a monitor message, but monitor not started yet"
0039 8102_E 2 00 00000000 "ND/TH97: Application tries to start the monitor, but it is already started"
0039 8103_E 2 00 00000000 "ND/TH97: Application tries to stop monitor with wrong process"
0039 8104_E 2 00 00000000 "ND/TH97: Paper jam, paper skew, bad/missing mark on paper, dirty sensor"
0039 8105_E 4 00 00000000 "ND/TH97: "Drum cover not locked, reset switch faulty, drive belt faulty
0039 8106_E 4 00 00000000 "ND/TH97: The cutter is binding"
0039 8107_E 2 00 00000000 "ND/TH97: Paper jam in paper path"
0039 8108_E 1 00 00000000 "ND/TH97: Tray full, transport of more than 10 sheets attempted"
0039 8109_E 1 00 00000000 "ND/TH97: Sheets where not removed before new print job was issued"
0039 810A_E 1 00 00000000 "ND/TH97: Wrong access to a non-existent font module"
0039 810B_E 4 00 00000000 "ND/TH97: Document jam in transport path, 2 reject attempted"
0039 810C_E 1 00 00000000 "ND/TH97: External light when adjusting the photosensor"
0039 810D_E 4 00 00000000 "ND/TH97: Rocker does not return to home position after cutting"
0039 810E_E 2 00 00000000 "ND/TH97: Door is binding, stacker door open failure"
0039 8111_E 4 00 00000000 "ND/TH97: Printer hardware error"
0039 8112_E 4 00 00000000 "ND/TH97: Reject box overfilled"
0039 8113_E 4 00 00000000 "ND/TH97: Printer firmware receives an internal SW error"
0039 8120_E 4 00 00000000 "ND/TH97: Drum cover not closed"
0039 8121_E 2 00 00000000 "ND/TH97: Selected paper lane not available"
0039 8122_E 4 00 00000000 "ND/TH97: Paper empty on lane 2"
0039 8123_E 4 00 00000000 "ND/TH97: Documents not removed before issuing a new print job"
0039 8124_E 2 00 00000000 "ND/TH97: Print job in graphics mode aborted"
0039 8125_E 1 00 00000000 "ND/TH97: Internal software error during graphic print job"
0039 FE08_E 4 00 00000000 "ND/TH97: V24 Communication timeout"
0039 FE09_E 4 00 00000000 "ND/TH97: V24 Communication timeout"
0039 FE85_E 4 00 00000000 "ND/TH97: V24 Communication problem"
AA39 DEFA_W 4 00 00000000 "USB/DOCPRT: DEFAULT_WARNING"
AA39 DEFA_E 4 00 00000000 "USB/DOCPRT: DEFAULT_ERROR"
AA39 8000_E 4 00 00000000 "USB/DOCPRT: Unexpected descriptor was reported from USB device"
AA39 8001_E 4 00 00000000 "USB/DOCPRT: Device not found"
AA39 8002_E 4 00 00000000 "USB/DOCPRT: Not enough memory available"
AA39 8003_E 4 00 00000000 "USB/DOCPRT: It was no endpoint found in the descriptor"
AA39 8004_E 4 00 00000000 "USB/DOCPRT: The creation of the list of USB devices failed"
AA39 FE09_E 4 00 00000000 "USB/DOCPRT: USB read command could not be executed in the specified monitoring
time"
AA39 FE0A_E 4 00 00000000 "USB/DOCPRT: USB READ command is cancelled by the user"
AA39 FE89_E 4 00 00000000 "USB/DOCPRT: The pointer pData is illegal"
AA39 FE9C_E 4 00 00000000 "USB/DOCPRT: The length in DataSize is 0 (zero)"
AA39 0001_E 4 00 00000000 "USB/DOCPRT: CRC error has been detected"
AA39 0002_E 4 00 00000000 "USB/DOCPRT: Bit stuffing error has been detected"
AA39 0003_E 4 00 00000000 "USB/DOCPRT: DATA toggle mismatch has been detected"
AA39 0004_E 4 00 00000000 "USB/DOCPRT: STALLPID has been detected, error is reported by the USB host control-
ler"
AA39 0005_E 4 00 00000000 "USB/DOCPRT: USB device is not responding, error is reported by the USB host"
AA39 0006_E 4 00 00000000 "USB/DOCPRT: PID check has failed, error is reported by the USB host controller"
AA39 0007_E 4 00 00000000 "USB/DOCPRT: Unexpected PID detected, error is reported by the USB host"
AA39 0008_E 4 00 00000000 "USB/DOCPRT: Data overrun error detected, error is reported by the USB host"
AA39 0009_E 4 00 00000000 "USB/DOCPRT: Data underrun error detected, error is reported by the USB host"
420 October 2004 U25604-J-Z745-1-7600


AA39 000A_E 4 00 00000000 "USB/DOCPRT: Error code is reserved by the USB host controller driver"
AA39 000B_E 4 00 00000000 "USB/DOCPRT: Error code is reserved by the USB host controller driver"
AA39 000C_E 4 00 00000000 "USB/DOCPRT: Buffer overrun has been detected, error is reported by the USB host"
AA39 000D_E 4 00 00000000 "USB/DOCPRT: Buffer underrun has been detected, error is reported by the USB host"
AA39 000F_E 4 00 00000000 "USB/DOCPRT: Buffer was not accessed, error is reported by the USB host"
AA39 0010_E 4 00 00000000 "USB/DOCPRT: FIFO error has been detected, PCI bus latency was too long"
AA39 0011_E 4 00 00000000 "USB/DOCPRT: XACT error has been detected, error is reported by the USB host"
AA39 0012_E 4 00 00000000 "USB/DOCPRT: Device is babbling, data transfer phase exceeds the USB frame length"
AA39 0013_E 4 00 00000000 "USB/DOCPRT: Data buffer error has been detected, error is reported by the USB host"
AA39 0030_E 4 00 00000000 "USB/DOCPRT: Endpoint has been halted by the USB bus driver USBD"
AA39 0100_E 4 00 00000000 "USB/DOCPRT: Memory allocation attempt has failed, error is reported by the USB bus"
AA39 0200_E 4 00 00000000 "USB/DOCPRT: Invalid URB function code has been passed, error is reported by the USB"
AA39 0300_E 4 00 00000000 "USB/DOCPRT: Invalid parameter has been passed, error is reported by the USB bus"
AA39 0400_E 4 00 00000000 "USB/DOCPRT: There are data transfer requests pending for the device"
AA39 0500_E 4 00 00000000 "USB/DOCPRT: Request has failed, error is reported by the USB bus driver USBD"
AA39 0600_E 4 00 00000000 "USB/DOCPRT: Invalid pipe handle has been passed, error is reported by the USB bus"
AA39 0700_E 4 00 00000000 "USB/DOCPRT: There is not enough bandwidth available, error is reported by the USB
bus"
AA39 0800_E 4 00 00000000 "USB/DOCPRT: Internal host controller error has been detected"
AA39 0900_E 4 00 00000000 "USB/DOCPRT: Short transfer has been detected, error is reported by the USB bus"
AA39 0A00_E 4 00 00000000 "USB/DOCPRT: Bad start frame has been specified, error is reported by the USB bus"
AA39 0B00_E 4 00 00000000 "USB/DOCPRT: Asynchronous request has failed, error is reported by the USB bus driver"
AA39 0C00_E 4 00 00000000 "USB/DOCPRT: USB frame control is currently owned, error is reported by the USB bus"
AA39 0D00_E 4 00 00000000 "USB/DOCPRT: USB frame control is currently not owned, error is reported by the USB"
AA39 0E00_E 4 00 00000000 "USB/DOCPRT: Operation is not supported, error is reported by the USB bus driver"
AA39 0F00_E 4 00 00000000 "USB/DOCPRT: Invalid configuration descriptor was reported by the device"
AA39 1000_E 4 00 00000000 "USB/DOCPRT: Operation has failed, error is reported by the USBIO driver"
AA39 1001_E 4 00 00000000 "USB/DOCPRT: Invalid input buffer has been passed to an IOCTL operation"
AA39 1002_E 4 00 00000000 "USB/DOCPRT: Invalid output buffer has been passed to an IOCTL operation"
AA39 1003_E 4 00 00000000 "USB/DOCPRT: There is not enough system memory available to complete the operation"
AA39 1004_E 4 00 00000000 "USB/DOCPRT: There are read or write requests pending, error is reported by the USBIO"
AA39 1005_E 4 00 00000000 "USB/DOCPRT: USB device is already configured, error is reported by the USBIO"
AA39 1006_E 4 00 00000000 "USB/DOCPRT: The USB device is not configured, error is reported by the USBIO driver"
AA39 1007_E 4 00 00000000 "USB/DOCPRT: There are open pipes, error is reported by the USBIO driver"
AA39 1008_E 4 00 00000000 "USB/DOCPRT: Either the handle is already bound to a pipe"
AA39 1009_E 4 00 00000000 "USB/DOCPRT: Handle is not bound to a pipe, error is reported by the USBIO driver"
AA39 100A_E 4 00 00000000 "USB/DOCPRT: USB device has been removed from the system"
AA39 100B_E 4 00 00000000 "USB/DOCPRT: Specified control code is not supported"
AA39 100C_E 4 00 00000000 "USB/DOCPRT: Operation has been timed out, error is reported by the USBIO driver"
AA39 100D_E 4 00 00000000 "USB/DOCPRT: Invalid recipient has been specified"
AA39 100E_E 4 00 00000000 "USB/DOCPRT: Either an invalid request type has been specified"
AA39 100F_E 4 00 00000000 "USB/DOCPRT: Invalid IOCTL code has been specified, error is reported by the USBIO"
AA39 1010_E 4 00 00000000 "USB/DOCPRT: Direction of the data transfer request is not supported by that pipe"
AA39 1011_E 4 00 00000000 "USB/DOCPRT: Number of asynchronous data packets specified in an asynchronous read"
AA39 1012_E 4 00 00000000 "USB/DOCPRT: Memory resources are exhausted. This error is reported by the USBIO
driver"
AA39 1013_E 4 00 00000000 "USB/DOCPRT: The specified pipe was not found in the current configuration"
AA39 1014_E 4 00 00000000 "USB/DOCPRT: An invalid asynchronous data packet has been specified"
AA39 1015_E 4 00 00000000 "USB/DOCPRT: There are not enough system resources to complete the operation"
AA39 1016_E 4 00 00000000 "USB/DOCPRT: Specified interface was not found in the current configuration"
AA39 1017_E 4 00 00000000 "USB/DOCPRT: Operation cannot be executed while the USB device is in the current state"
AA39 1018_E 4 00 00000000 "USB/DOCPRT: Invalid parameter has been specified with an IOCTL operation"
AA39 1019_E 4 00 00000000 "USB/DOCPRT: Evaluation interval of the USBIO DEMO version has expired"
AA39 101A_E 4 00 00000000 "USB/DOCPRT: Invalid power state has been specified"
AA39 101B_E 4 00 00000000 "USB/DOCPRT: Device has entered a power down state"
AA39 101C_E 4 00 00000000 "USB/DOCPRT: API version reported by the USBIO driver does not match"
AA39 101D_E 4 00 00000000 "USB/DOCPRT: Set configuration operation has failed, error is reported by the USBIO"
AA39 1080_E 4 00 00000000 "USB/DOCPRT: Operation has failed due to a restriction of the USBIO LIGHT version"
U25604-J-Z745-1-7600 October 2004 421


AA39 1086_E 4 00 00000000 "USB/DOCPRT: The operation has failed due to a restriction of the USBIO LIGHT ver-
sion"
AA39 1100_E 4 00 00000000 "USB/DOCPRT: The specified device object does not exist"
AA39 1102_E 4 00 00000000 "USB/DOCPRT: Device object was opened, there is no valid handle to execute the opera-
tion"
AA39 1104_E 4 00 00000000 "USB/DOCPRT: Enumeration of the specified devices has failed"
AA39 1105_E 4 00 00000000 "USB/DOCPRT: Invalid parameter has been passed to a function"
AA39 1106_E 4 00 00000000 "USB/DOCPRT: Library setupapi.dll could not be loaded"
AA39 2000_E 4 00 00000000 "USB/DOCPRT: Set configuration request has failed"
AA39 3000_E 4 00 00000000 "USB/DOCPRT: Buffer is too small, error is reported by the USB bus driver USBD"
AA39 4000_E 4 00 00000000 "USB/DOCPRT: Interface was not found, error is reported by the USB bus driver USBD"
AA39 5000_E 4 00 00000000 "USB/DOCPRT: Invalid pipe flags have been specified"
AA39 6000_E 4 00 00000000 "USB/DOCPRT: Operation has been timed out, error is reported by the USB bus driver"
AA39 7000_E 4 00 00000000 "USB/DOCPRT: USB device is gone, error is reported by the USB bus driver USBD"
Printer TH21 (Class: 003E)
class 003E.
Table 114: Printer (Class: 003E)

Error Error Sev. M-Status M-Data Status desription
Class Code INFO
003E DEFA_W 2 00 00000000 "TH21: Default warning if no CSC-W32 error found"
003E DEFA_E 2 00 00000000 "TH21: Default error if no CSC-W32 error found"
003E 0001_E 2 00 02000000 "TH21: Receipt paper low warning"
003E 8100_E 2 08 40000800 "TH21: Receipt paper empty"
003E 8101_E 0 00 00000000 "TH21: Cover is properly opened"
003E 8102_E 2 08 40000800 "TH21: Print head temperature is not ok"
003E 8103_E 2 08 40000800 "TH21: Power lost"
003E 8104_E 2 05 80000000 "TH21: Paper jam"
003E 8105_E 2 08 40000800 "TH21: The cutter is binding"
003E 8106_E 2 08 40000800 "TH21: Hardware error, error in memory test"
003E 8120_E 2 08 40000800 "TH21: Communication error with monitoring module if in use"
003E 8121_E 2 08 40000800 "TH21: No GDI driver WN_TH21 found (when monitoring facility is used)"
003E 8122_E 2 08 40000800 "TH21: Invalid COM port entry for GDI driver (when monitoring facility is
used)"
003E 8201_E 2 08 40000800 "TH21: Cannot open control file TH21.INI"
003E 8202_E 2 08 40000800 "TH21: Cannot read control file TH21.INI"
003E 8203_E 2 08 40000800 "TH21: Cannot open a file or invalid file name give up"
003E 8204_E 2 08 40000800 "TH21: Printer hardware error, cannot read the file to be loaded"
003E 8205_E 2 08 40000800 "TH21: File to be loaded has invalid module ID"
003E 8206_E 2 08 40000800 "TH21: The expected response to the FW loader is not correct"
003E 8207_E 2 08 40000800 "TH21: Invalid Logo type or logo file too big"
422 October 2004 U25604-J-Z745-1-7600

Printer Extensions (Class: 003F)
class 003F.
Table 115: Printer (Class: 003F)


003F DEFA_W 2 00 00000000 "PRT GDI: Default warning if no CSC-W32 error found"
003F DEFA_E 2 00 00000000 "PRT GDI: Default error if no CSC-W32 error found"
003F 1017_E 4 00 00000000 "PRT GDI: Communication problem"
003F 1420_E 4 00 00000000 "PRT GDI: Communication problem"
Printer Monitor ND9G (Class: 0040)
class 0040.

0040 DEFA_W 2 00 00000000 "ND9G GDI: Default warning if no CSC-W32 error found"
0040 DEFA_E 2 00 00000000 "ND9G GDI: Default error if no CSC-W32 error found"
0040 0001_E 2 00 00000000 "ND9G GDI: Paper-out condition."
0040 0002_E 2 00 00000000 "ND9G GDI: Terminate applications requiring the printer."
0040 0003_E 2 00 00000000 "ND9G GDI: Receipt paper jam. Receipt could not be correctly processed."
0040 0004_E 4 00 00000000 "ND9G GDI: Hardware error: error in memory test (RAM and ROM), backup RAM
faulty."
0040 0005_E 4 00 00000000 "ND9G GDI: Printer detect unexpected data."
0040 0006_E 4 00 00000000 "ND9G GDI: A parity error is returned from the printer when faulty characters are
received."
0040 0007_E 4 00 00000000 "ND9G GDI: Loss of a command. The command was sent and could not be correctly
executed."
0040 0009_E 2 00 00000000 "ND9G GDI: By activated mark, recognition a mark is not found."
0040 000A_E 4 00 00000000 "ND9G GDI: A checksum error of the RAM is occurred."
0040 000B_E 4 00 00000000 "ND9G GDI: The loaded firmware file does not fit to the printer hardware."
0040 000D_E 4 00 00000000 "ND9G GDI: Unexpected data was received."
0040 000E_E 2 00 00000000 "ND9G GDI: A WRITE command could not be executed in the specified monitoring
time."
0040 000F_E 2 00 00000000 "ND9G GDI: A READ command could not be executed in the specified monitoring
time."
0040 0010_E 2 00 00000000 "ND9G GDI: Further control commands missing (e.g. Eject)"
0040 0011_E 2 00 00000000 "ND9G GDI: An error occurred while the required line parameters were being set."
0040 0012_E 2 00 00000000 "ND9G GDI: An internal SW error occurred."
0040 0020_E 4 00 00000000 "ND9G GDI: Cannot open a file or checksum of a file to be loaded is not correct."
0040 0021_E 4 00 00000000 "ND9G GDI: Cannot read the firmware file to be loaded."
0040 0022_E 4 00 00000000 "ND9G GDI: Cannot read the file to be loaded."
0040 0023_E 4 00 00000000 "ND9G GDI: The expected response of the Firmware Loader is not correct."
0040 0024_E 4 00 00000000 "ND9G GDI: Firmware file data do not reach the firmware controller correctly."
0040 0025_E 4 00 00000000 "ND9G GDI: An error occurred when the print system was started from the CSC ser-
vice."
0040 0001_W 4 00 00000000 "ND9G GDI: Wrong value of entry FILE_CTR"
0040 0002_W 4 00 00000000 "ND9G GDI: No entry FILE1 found in the Registry."
U25604-J-Z745-1-7600 October 2004 423

Printer Monitor TH21 (Class: 0041)
class 0041.

0041 DEFA_W 2 00 00000000 "TH21 GDI: Default warning if no CSC-W32 error found"
0041 DEFA_E 2 00 00000000 "TH21 GDI: Default error if no CSC-W32 error found"
0041 0001_E 4 00 00000000 "TH21 GDI: Paper-out condition."
0041 0002_E 2 00 00000000 "TH21 GDI: The cover is properly opened."
0041 0003_E 2 00 00000000 "TH21 GDI: The print head temperature is not ok."
0041 0004_E 4 00 00000000 "TH21 GDI: Power failure during operation or insufficient power supply."
0041 0005_E 4 00 00000000 "TH21 GDI: Receipt paper jam. Receipt could not be correctly processed."
0041 0006_E 2 00 00000000 "TH21 GDI: The cutter is binding."
0041 0007_E 4 00 00000000 "TH21 GDI: Error in memory test (RAM and ROM)"
0041 0008_E 2 00 00000000 "TH21 GDI: Unexpected data was received."
0041 0009_E 2 00 00000000 "TH21 GDI: A WRITE command could not be executed in the specified monitor-
ing time"
0041 000A_E 2 00 00000000 "TH21 GDI: A READ command could not be executed in the specified monitoring
time"
0041 000B_E 2 00 00000000 "TH21 GDI: Further control commands missing (e.g. Eject)"
0041 000C_E 4 00 00000000 "TH21 GDI: An error occurred while the required line parameters were being set."
Printer System Framework (Class: 0042)
class 0042.

0042 DEFA_W 2 00 00000000 "PRT GDI: Default warning if no CSC-W32 error found"
0042 DEFA_E 2 00 00000000 "PRT GDI: Default error if no CSC-W32 error found"
0042 0001_E 2 00 00000000 "PRT GDI: Data that are passed to print system are to small"
0042 0002_E 2 00 00000000 "PRT GDI: Invalid registry parameter"
0042 0003_E 2 00 00000000 "PRT GDI: Operation not valid or not supported by printer"
0042 0004_E 2 00 00000000 "PRT GDI: Internal software error"
0042 0005_E 2 00 00000000 "PRT GDI: Function not allowed in the current context"
0042 0006_E 4 00 00000000 "PRT GDI: Communication error, write request unsuccessful"
0042 0007_E 4 00 00000000 "PRT GDI: A system error has occurred"
0042 0008_E 2 00 00000000 "PRT GDI: Unexpected parameter in system call"
0042 0009_E 4 00 00000000 "PRT GDI: Open failed"
0042 000A_E 2 00 00000000 "PRT GDI: Start of a print job failed"
0042 000B_E 2 00 00000000 "PRT GDI: A job has been despooled while another job is still in progress"
0042 000D_E 2 00 00000000 "PRT GDI: Invalid parameter used in a server function call"
0042 000E_E 2 00 00000000 "PRT GDI: Client already registered for monitoring"
0042 000F_E 2 00 00000000 "PRT GDI: The client tried to claim the device twice"
0042 0010_E 2 00 00000000 "PRT GDI: Invalid client handle used"
0042 0011_E 2 00 00000000 "PRT GDI: Client not registered for monitoring"
424 October 2004 U25604-J-Z745-1-7600


0042 0012_E 2 00 00000000 "PRT GDI: Start of print system server failed"
0042 0013_E 4 00 00000000 "PRT GDI: Connection failed, the printer is unknown"
0042 0014_E 2 00 00000000 "PRT GDI: Access denied, the client is not allowed to access the requested operation"
0042 0015_E 2 00 00000000 "PRT GDI: Access denied, because another client has claimed the device for exclusive
access"
0042 0016_E 2 00 00000000 "PRT GDI: Unknown property"
0042 0017_E 2 00 00000000 "PRT GDI: The property has an invalid format"
0042 0018_E 2 00 00000000 "PRT GDI: The property value is invalid"

0042 0019_E 2 00 00000000 "PRT GDI: An invalid input string has been supplied"
U25604-J-Z745-1-7600 October 2004 425

Printer TP07 GDI (Class: 0044)
class 0044.

0044 DEFA_W 2 00 00000000 "TP07 GDI: DEFAULT_WARNING"
0044 DEFA_E 4 00 00000000 "TP07 GDI: DEFAULT_ERROR"
0044 0001_E 2 08 40000800 "TP07 GDI: Paper-out condition"
0044 0002_E 2 05 80000000 "TP07 GDI: Paper jam while cutting the paper"
0044 0003_E 2 00 00000000 "TP07 GDI: Black dot mark not found"
0044 0004_E 2 00 00000000 "TP07 GDI: Paper jam after cut receipt in the presenter"
0044 0005_E 2 00 00000000 "TP07 GDI: Paper jam after cut receipt after reject command."
0044 0006_E 2 00 00000000 "TP07 GDI: Receipt paper jam while printing process"
0044 0007_E 4 00 00000000 "TP07 GDI: Internal print job timeout has occurred"
0044 0008_E 4 00 00000000 "TP07 GDI: Power voltage of the printer is too high"
0044 0009_E 4 00 00000000 "TP07 GDI: Power voltage of the printer is too low"
0044 000A_E 4 00 00000000 "TP07 GDI: Temperature of the print head is too high"
0044 000B_E 4 00 00000000 "TP07 GDI: Hardware error"
0044 0010_E 4 00 00000000 "TP07 GDI: Unexpected data was received"
0044 0011_E 4 00 00000000 "TP07 GDI: A WRITE command could not be executed in the specified monitoring time"
0044 0012_E 4 00 00000000 "TP07 GDI: A READ command could not be executed in the specified monitoring time"
0044 0013_E 4 00 00000000 "TP07 GDI: This message may only occur when controlled print jobs are received"
0044 0015_E 2 00 00000000 "TP07 GDI: An internal SW error occurred"
0044 0016_E 4 00 00000000 "TP07 GDI: Printer is in offline state without any specific device error"
426 October 2004 U25604-J-Z745-1-7600

Printer TP07 (Class: 0045)
class 0045.


0045 DEFA_W 4 00 00000000 "RJ03/TP07/NP07: DEFAULT_WARNING"
0045 DEFA_E 4 00 00000000 "RJ03/TP07/NP07: DEFAULT_ERROR"
0045 0001_E 2 00 02000000 "RJ03/TP07/NP07: Receipt paper low"
0045 8100_E 4 00 00000000 "RJ03/TP07/NP07: Unexpected data was received"
0045 8101_E 4 00 00000000 "RJ03/TP07/NP07: Allocation error, not enough resources to allocate internal memory"
0045 8102_E 4 00 00000000 "RJ03/TP07/NP07: A READ command could not be executed in the specified monitoring
time"
0045 8103_E 4 00 00000000 "RJ03/TP07/NP07: Code page not available"
0045 8104_E 4 00 00000000 "RJ03/TP07/NP07: Cannot open image file or invalid file name give up"
0045 8105_E 4 00 00000000 "RJ03/TP07/NP07: Cannot read the file to be loaded"
0045 8106_E 4 00 00000000 "RJ03/TP07/NP07: Invalid logo type"
0045 8107_E 4 00 00000000 "RJ03/TP07/NP07: Printer is in offline state without any specific device error"
0045 8108_E 4 00 00000000 "RJ03/TP07/NP07: No USB devices of the specified type available"
0045 8000_E 4 00 00000000 "RJ03/TP07/NP07: Receipt paper out"
0045 8001_E 4 00 00000000 "RJ03/TP07/NP07: Paper jam while paper cut"
0045 8002_E 4 00 00000000 "RJ03/TP07/NP07: Carrier does not found the home position"
0045 8003_E 4 00 00000000 "RJ03/TP07/NP07: Paper jam before cut"
0045 8004_E 4 00 00000000 "RJ03/TP07/NP07: Black dot mark not found"
0045 8005_E 4 00 00000000 "RJ03/TP07/NP07: Paper jam after cutting the receipt in the presenter"
0045 8006_E 4 00 00000000 "RJ03/TP07/NP07: Paper jam after cut receipt after reject command"
0045 8007_E 4 00 00000000 "RJ03/TP07/NP07: Receipt paper jam while printing"
0045 8008_E 4 00 00000000 "RJ03/TP07/NP07: Power voltage of printer is too high"
0045 8009_E 4 00 00000000 "RJ03/TP07/NP07: Power voltage of printer is too low"
0045 800A_E 4 00 00000000 "RJ03/TP07/NP07: Temperature of print head is too high"
0045 800B_E 4 00 00000000 "RJ03/TP07/NP07: Hardware error"
0045 800C_E 4 00 00000000 "RJ03/TP07/NP07: Paper is not at print starting position"
U25604-J-Z745-1-7600 October 2004 427

Printer USB/TP07 (Class: AA45)
class AA45.
Table 121: Printer (Class: AA45)

AA45 DEFA_W 2 00 00000000 "USB/TP07/NP07: DEFAULT_WARNING"
AA45 DEFA_E 4 00 00000000 "USB/TP07/NP07: DEFAULT_ERROR"
AA45 8000_E 2 00 00000000 "USB/TP07/NP07: Unexpected descriptor was reported from USB device"
AA45 8001_E 2 00 00000000 "USB/TP07/NP07: Device not found"
AA45 8002_E 2 00 00000000 "USB/TP07/NP07: Not enough memory available"
AA45 8003_E 2 00 00000000 "USB/TP07/NP07: It was no endpoint found in the descriptor"
AA45 8004_E 2 00 00000000 "USB/TP07/NP07: The creation of the list of USB devices failed"
AA45 FE09_E 2 00 00000000 "USB/TP07/NP07: USB read command could not be executed in the specified monitoring
time"
AA45 FE0A_E 2 00 00000000 "USB/TP07/NP07: USB READ command is cancelled by the user"
AA45 FE89_E 2 00 00000000 "USB/TP07/NP07: The pointer pData is illegal"
AA45 FE9C_E 2 00 00000000 "USB/TP07/NP07: The length in DataSize is 0 (zero)"
AA45 0001_E 2 00 00000000 "USB/TP07/NP07: CRC error has been detected"
AA45 0002_E 2 00 00000000 "USB/TP07/NP07: Bit stuffing error has been detected"
AA45 0003_E 2 00 00000000 "USB/TP07/NP07: DATA toggle mismatch has been detected"
AA45 0004_E 2 00 00000000 "USB/TP07/NP07: STALLPID has been detected, error is reported by the USB host con-
troller"
AA45 0005_E 2 00 00000000 "USB/TP07/NP07: USB device is not responding, error is reported by the USB host"
AA45 0006_E 2 00 00000000 "USB/TP07/NP07: PID check has failed, error is reported by the USB host controller"
AA45 0007_E 2 00 00000000 "USB/TP07/NP07: Unexpected PID detected, error is reported by the USB host"
AA45 0008_E 2 00 00000000 "USB/TP07/NP07: Data overrun error detected, error is reported by the USB host"
AA45 0009_E 2 00 00000000 "USB/TP07/NP07: Data underrun error detected, error is reported by the USB host"
AA45 000A_E 2 00 00000000 "USB/TP07/NP07: Error code is reserved by the USB host controller driver"
AA45 000B_E 2 00 00000000 "USB/TP07/NP07: Error code is reserved by the USB host controller driver"
AA45 000C_E 2 00 00000000 "USB/TP07/NP07: Buffer overrun has been detected, error is reported by the USB host"
AA45 000D_E 2 00 00000000 "USB/TP07/NP07: Buffer underrun has been detected, error is reported by the USB host"
AA45 000F_E 2 00 00000000 "USB/TP07/NP07: Buffer was not accessed, error is reported by the USB host"
AA45 0010_E 2 00 00000000 "USB/TP07/NP07: FIFO error has been detected, PCI bus latency was too long"
AA45 0011_E 2 00 00000000 "USB/TP07/NP07: XACT error has been detected, error is reported by the USB host"
AA45 0012_E 2 00 00000000 "USB/TP07/NP07: Device is babbling, data transfer phase exceeds the USB frame length"
AA45 0013_E 2 00 00000000 "USB/TP07/NP07: Data buffer error has been detected, error is reported by the USB host"
AA45 0030_E 2 00 00000000 "USB/TP07/NP07: Endpoint has been halted by the USB bus driver USBD"
AA45 0100_E 2 00 00000000 "USB/TP07/NP07: Memory allocation attempt has failed, error is reported by the USB
bus"
AA45 0200_E 2 00 00000000 "USB/TP07/NP07: Invalid URB function code has been passed, error is reported by the
USB"
AA45 0300_E 2 00 00000000 "USB/TP07/NP07: Invalid parameter has been passed, error is reported by the USB bus"
AA45 0400_E 2 00 00000000 "USB/TP07/NP07: There are data transfer requests pending for the device"
AA45 0500_E 2 00 00000000 "USB/TP07/NP07: Request has failed, error is reported by the USB bus driver USBD"
AA45 0600_E 2 00 00000000 "USB/TP07/NP07: Invalid pipe handle has been passed, error is reported by the USB bus"
AA45 0700_E 2 00 00000000 "USB/TP07/NP07: There is not enough bandwidth available, error is reported by the USB
bus"
AA45 0800_E 2 00 00000000 "USB/TP07/NP07: Internal host controller error has been detected"
AA45 0900_E 2 00 00000000 "USB/TP07/NP07: Short transfer has been detected, error is reported by the USB bus"
AA45 0A00_E 2 00 00000000 "USB/TP07/NP07: Bad start frame has been specified, error is reported by the USB bus"
AA45 0B00_E 2 00 00000000 "USB/TP07/NP07: Asynchronous request has failed, error is reported by the USB bus
driver"
AA45 0C00_E 2 00 00000000 "USB/TP07/NP07: USB frame control is currently owned, error is reported by the USB
bus"
AA45 0D00_E 2 00 00000000 "USB/TP07/NP07: USB frame control is currently not owned, error is reported by the
USB"
AA45 0E00_E 2 00 00000000 "USB/TP07/NP07: Operation is not supported, error is reported by the USB bus driver"
AA45 0F00_E 2 00 00000000 "USB/TP07/NP07: Invalid configuration descriptor was reported by the device"
AA45 1000_E 2 00 00000000 "USB/TP07/NP07: Operation has failed, error is reported by the USBIO driver"
428 October 2004 U25604-J-Z745-1-7600


AA45 1001_E 2 00 00000000 "USB/TP07/NP07: Invalid input buffer has been passed to an IOCTL operation"
AA45 1002_E 2 00 00000000 "USB/TP07/NP07: Invalid output buffer has been passed to an IOCTL operation"
AA45 1003_E 2 00 00000000 "USB/TP07/NP07: There is not enough system memory available to complete the opera-
tion"
AA45 1004_E 2 00 00000000 "USB/TP07/NP07: There are read or write requests pending, error is reported by the
USBIO"
AA45 1005_E 2 00 00000000 "USB/TP07/NP07: USB device is already configured, error is reported by the USBIO"
AA45 1006_E 2 00 00000000 "USB/TP07/NP07: The USB device is not configured, error is reported by the USBIO
driver"
AA45 1007_E 2 00 00000000 "USB/TP07/NP07: There are open pipes, error is reported by the USBIO driver"
AA45 1008_E 2 00 00000000 "USB/TP07/NP07: Either the handle is already bound to a pipe"
AA45 1009_E 2 00 00000000 "USB/TP07/NP07: Handle is not bound to a pipe, error is reported by the USBIO driver"
AA45 100A_E 2 00 00000000 "USB/TP07/NP07: USB device has been removed from the system"
AA45 100B_E 2 00 00000000 "USB/TP07/NP07: Specified control code is not supported"
AA45 100C_E 2 00 00000000 "USB/TP07/NP07: Operation has been timed out, error is reported by the USBIO driver"
AA45 100D_E 2 00 00000000 "USB/TP07/NP07: Invalid recipient has been specified"
AA45 100E_E 2 00 00000000 "USB/TP07/NP07: Either an invalid request type has been specified"
AA45 100F_E 2 00 00000000 "USB/TP07/NP07: Invalid IOCTL code has been specified, error is reported by the
USBIO"
AA45 1010_E 2 00 00000000 "USB/TP07/NP07: Direction of the data transfer request is not supported by that pipe"
AA45 1011_E 2 00 00000000 "USB/TP07/NP07: Number of asynchronous data packets specified in an asynchronous
read"
AA45 1012_E 2 00 00000000 "USB/TP07/NP07: Memory resources are exhausted. This error is reported by the USBIO
driver"
AA45 1013_E 2 00 00000000 "USB/TP07/NP07: The specified pipe was not found in the current configuration"
AA45 1014_E 2 00 00000000 "USB/TP07/NP07: An invalid asynchronous data packet has been specified"
AA45 1015_E 2 00 00000000 "USB/TP07/NP07: There are not enough system resources to complete the operation"
AA45 1016_E 2 00 00000000 "USB/TP07/NP07: Specified interface was not found in the current configuration"
AA45 1017_E 2 00 00000000 "USB/TP07/NP07: Operation cannot be executed while the USB device is in the current
state"
AA45 1018_E 2 00 00000000 "USB/TP07/NP07: Invalid parameter has been specified with an IOCTL operation"
AA45 1019_E 2 00 00000000 "USB/TP07/NP07: Evaluation interval of the USBIO DEMO version has expired"
AA45 101A_E 2 00 00000000 "USB/TP07/NP07: Invalid power state has been specified"
AA45 101B_E 2 00 00000000 "USB/TP07/NP07: Device has entered a power down state"
AA45 101C_E 2 00 00000000 "USB/TP07/NP07: API version reported by the USBIO driver does not match"
AA45 101D_E 2 00 00000000 "USB/TP07/NP07: Set configuration operation has failed, error is reported by the USBIO"
AA45 1080_E 2 00 00000000 "USB/TP07/NP07: Operation has failed due to a restriction of the USBIO LIGHT version"
AA45 1086_E 2 00 00000000 "USB/TP07/NP07: The operation has failed due to a restriction of the USBIO LIGHT ver-
sion"
AA45 1100_E 2 00 00000000 "USB/TP07/NP07: The specified device object does not exist"
AA45 1102_E 2 00 00000000 "USB/TP07/NP07: Device object was opened, there is no valid handle to execute the oper-
ation"
AA45 1104_E 2 00 00000000 "USB/TP07/NP07: Enumeration of the specified devices has failed"
AA45 1105_E 2 00 00000000 "USB/TP07/NP07: Invalid parameter has been passed to a function"
AA45 1106_E 2 00 00000000 "USB/TP07/NP07: Library setupapi.dll could not be loaded"
AA45 2000_E 2 00 00000000 "USB/TP07/NP07: Set configuration request has failed"
AA45 3000_E 2 00 00000000 "USB/TP07/NP07: Buffer is too small, error is reported by the USB bus driver USBD"
AA45 4000_E 2 00 00000000 "USB/TP07/NP07: Interface was not found, error is reported by the USB bus driver
USBD"
AA45 5000_E 2 00 00000000 "USB/TP07/NP07: Invalid pipe flags have been specified"
AA45 6000_E 2 00 00000000 "USB/TP07/NP07: Operation has been timed out, error is reported by the USB bus driver"
AA45 7000_E 2 00 00000000 "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)
class 0048.

0048 DEFA_W 4 00 00000000 "RJ03/TP06/NP06: DEFAULT_WARNING"
0048 DEFA_E 4 00 00000000 "RJ03/TP06/NP06: DEFAULT_ERROR"
0048 0001_E 2 00 02000000 "RJ03/TP06/NP06: Journal paper low"
0048 8100_E 4 00 00000000 "RJ03/TP06/NP06: Unexpected data was received"
0048 8101_E 4 00 00000000 "RJ03/TP06/NP06: Allocation error, not enough resources to allocate internal memory"
0048 8102_E 4 00 00000000 "RJ03/TP06/NP06: A READ command could not be executed in the specified monitoring
time"
0048 8103_E 4 00 00000000 "RJ03/TP06/NP06: Code page not available"
0048 8104_E 4 00 00000000 "RJ03/TP06/NP06: Cannot open image file or invalid file name give up"
0048 8105_E 4 00 00000000 "RJ03/TP06/NP06: Cannot read the file to be loaded"
0048 8106_E 4 00 00000000 "RJ03/TP06/NP06: Invalid logo type"
0048 8107_E 4 00 00000000 "RJ03/TP06/NP06: Printer is in offline state without any specific device error"
0048 8108_E 4 00 00000000 "RJ03/TP06/NP06: No USB devices of the specified type available"
0048 8000_E 4 00 00000000 "RJ03/TP06/NP06: Journal paper out"
0048 8001_E 4 00 00000000 "RJ03/TP06/NP06: Paper jam while paper cut"
0048 8002_E 4 00 00000000 "RJ03/TP06/NP06: Carrier does not found the home position"
0048 8003_E 4 00 00000000 "RJ03/TP06/NP06: Paper jam before cut"
0048 8004_E 4 00 00000000 "RJ03/TP06/NP06: Black dot mark not found"
0048 8005_E 4 00 00000000 "RJ03/TP06/NP06: Paper jam after cutting the receipt in the presenter"
0048 8006_E 4 00 00000000 "RJ03/TP06/NP06: Paper jam after cut receipt after reject command"
0048 8007_E 4 00 00000000 "RJ03/TP06/NP06: Receipt paper jam while printing"
0048 8008_E 4 00 00000000 "RJ03/TP06/NP06: Power voltage of printer is too high"
0048 8009_E 4 00 00000000 "RJ03/TP06/NP06: Power voltage of printer is too low"
0048 800A_E 4 00 00000000 "RJ03/TP06/NP06: Temperature of print head is too high"
0048 800B_E 4 00 00000000 "RJ03/TP06/NP06: Hardware error"
0048 800C_E 4 00 00000000 "RJ03/TP06/NP06: Paper is not at print starting position"
430 October 2004 U25604-J-Z745-1-7600

Printer USB/TP06 (Class: AA48)
class AA48.
Table 123: Printer (Class: AA48)


AA48 DEFA_W 2 00 00000000 "USB/TP06/NP06: DEFAULT_WARNING"
AA48 DEFA_E 4 00 00000000 "USB/TP06/NP06: DEFAULT_ERROR"
AA48 8000_E 2 00 00000000 "USB/TP06/NP06: Unexpected descriptor was reported from USB device"
AA48 8001_E 2 00 00000000 "USB/TP06/NP06: Device not found"
AA48 8002_E 2 00 00000000 "USB/TP06/NP06: Not enough memory available"
AA48 8003_E 2 00 00000000 "USB/TP06/NP06: It was no endpoint found in the descriptor"
AA48 8004_E 2 00 00000000 "USB/TP06/NP06: The creation of the list of USB devices failed"
AA48 FE09_E 2 00 00000000 "USB/TP06/NP06: USB read command could not be executed in the specified monitoring
time"
AA48 FE0A_E 2 00 00000000 "USB/TP06/NP06: USB READ command is cancelled by the user"
AA48 FE89_E 2 00 00000000 "USB/TP06/NP06: The pointer pData is illegal"
AA48 FE9C_E 2 00 00000000 "USB/TP06/NP06: The length in DataSize is 0 (zero)"
AA48 0001_E 2 00 00000000 "USB/TP06/NP06: CRC error has been detected"
AA48 0002_E 2 00 00000000 "USB/TP06/NP06: Bit stuffing error has been detected"
AA48 0003_E 2 00 00000000 "USB/TP06/NP06: DATA toggle mismatch has been detected"
AA48 0004_E 2 00 00000000 "USB/TP06/NP06: STALLPID has been detected, error is reported by the USB host con-
troller"
AA48 0005_E 2 00 00000000 "USB/TP06/NP06: USB device is not responding, error is reported by the USB host"
AA48 0006_E 2 00 00000000 "USB/TP06/NP06: PID check has failed, error is reported by the USB host controller"
AA48 0007_E 2 00 00000000 "USB/TP06/NP06: Unexpected PID detected, error is reported by the USB host"
AA48 0008_E 2 00 00000000 "USB/TP06/NP06: Data overrun error detected, error is reported by the USB host"
AA48 0009_E 2 00 00000000 "USB/TP06/NP06: Data underrun error detected, error is reported by the USB host"
AA48 000A_E 2 00 00000000 "USB/TP06/NP06: Error code is reserved by the USB host controller driver"
AA48 000B_E 2 00 00000000 "USB/TP06/NP06: Error code is reserved by the USB host controller driver"
AA48 000C_E 2 00 00000000 "USB/TP06/NP06: Buffer overrun has been detected, error is reported by the USB host"
AA48 000D_E 2 00 00000000 "USB/TP06/NP06: Buffer underrun has been detected, error is reported by the USB host"
AA48 000F_E 2 00 00000000 "USB/TP06/NP06: Buffer was not accessed, error is reported by the USB host"
AA48 0010_E 2 00 00000000 "USB/TP06/NP06: FIFO error has been detected, PCI bus latency was too long"
AA48 0011_E 2 00 00000000 "USB/TP06/NP06: XACT error has been detected, error is reported by the USB host"
AA48 0012_E 2 00 00000000 "USB/TP06/NP06: Device is babbling, data transfer phase exceeds the USB frame length"
AA48 0013_E 2 00 00000000 "USB/TP06/NP06: Data buffer error has been detected, error is reported by the USB host"
AA48 0030_E 2 00 00000000 "USB/TP06/NP06: Endpoint has been halted by the USB bus driver USBD"
AA48 0100_E 2 00 00000000 "USB/TP06/NP06: Memory allocation attempt has failed, error is reported by the USB
bus"
AA48 0200_E 2 00 00000000 "USB/TP06/NP06: Invalid URB function code has been passed, error is reported by the
USB"
AA48 0300_E 2 00 00000000 "USB/TP06/NP06: Invalid parameter has been passed, error is reported by the USB bus"
AA48 0400_E 2 00 00000000 "USB/TP06/NP06: There are data transfer requests pending for the device"
AA48 0500_E 2 00 00000000 "USB/TP06/NP06: Request has failed, error is reported by the USB bus driver USBD"
AA48 0600_E 2 00 00000000 "USB/TP06/NP06: Invalid pipe handle has been passed, error is reported by the USB bus"
AA48 0700_E 2 00 00000000 "USB/TP06/NP06: There is not enough bandwidth available, error is reported by the USB
bus"
AA48 0800_E 2 00 00000000 "USB/TP06/NP06: Internal host controller error has been detected"
AA48 0900_E 2 00 00000000 "USB/TP06/NP06: Short transfer has been detected, error is reported by the USB bus"
AA48 0A00_E 2 00 00000000 "USB/TP06/NP06: Bad start frame has been specified, error is reported by the USB bus"
AA48 0B00_E 2 00 00000000 "USB/TP06/NP06: Asynchronous request has failed, error is reported by the USB bus
driver"
AA48 0C00_E 2 00 00000000 "USB/TP06/NP06: USB frame control is currently owned, error is reported by the USB
bus"
AA48 0D00_E 2 00 00000000 "USB/TP06/NP06: USB frame control is currently not owned, error is reported by the
USB"
AA48 0E00_E 2 00 00000000 "USB/TP06/NP06: Operation is not supported, error is reported by the USB bus driver"
AA48 0F00_E 2 00 00000000 "USB/TP06/NP06: Invalid configuration descriptor was reported by the device"
AA48 1000_E 2 00 00000000 "USB/TP06/NP06: Operation has failed, error is reported by the USBIO driver"
U25604-J-Z745-1-7600 October 2004 431


AA48 1001_E 2 00 00000000 "USB/TP06/NP06: Invalid input buffer has been passed to an IOCTL operation"
AA48 1002_E 2 00 00000000 "USB/TP06/NP06: Invalid output buffer has been passed to an IOCTL operation"
AA48 1003_E 2 00 00000000 "USB/TP06/NP06: There is not enough system memory available to complete the opera-
tion"
AA48 1004_E 2 00 00000000 "USB/TP06/NP06: There are read or write requests pending, error is reported by the
USBIO"
AA48 1005_E 2 00 00000000 "USB/TP06/NP06: USB device is already configured, error is reported by the USBIO"
AA48 1006_E 2 00 00000000 "USB/TP06/NP06: The USB device is not configured, error is reported by the USBIO
driver"
AA48 1007_E 2 00 00000000 "USB/TP06/NP06: There are open pipes, error is reported by the USBIO driver"
AA48 1008_E 2 00 00000000 "USB/TP06/NP06: Either the handle is already bound to a pipe"
AA48 1009_E 2 00 00000000 "USB/TP06/NP06: Handle is not bound to a pipe, error is reported by the USBIO driver"
AA48 100A_E 2 00 00000000 "USB/TP06/NP06: USB device has been removed from the system"
AA48 100B_E 2 00 00000000 "USB/TP06/NP06: Specified control code is not supported"
AA48 100C_E 2 00 00000000 "USB/TP06/NP06: Operation has been timed out, error is reported by the USBIO driver"
AA48 100D_E 2 00 00000000 "USB/TP06/NP06: Invalid recipient has been specified"
AA48 100E_E 2 00 00000000 "USB/TP06/NP06: Either an invalid request type has been specified"
AA48 100F_E 2 00 00000000 "USB/TP06/NP06: Invalid IOCTL code has been specified, error is reported by the
USBIO"
AA48 1010_E 2 00 00000000 "USB/TP06/NP06: Direction of the data transfer request is not supported by that pipe"
AA48 1011_E 2 00 00000000 "USB/TP06/NP06: Number of asynchronous data packets specified in an asynchronous
read"
AA48 1012_E 2 00 00000000 "USB/TP06/NP06: Memory resources are exhausted. This error is reported by the USBIO
driver"
AA48 1013_E 2 00 00000000 "USB/TP06/NP06: The specified pipe was not found in the current configuration"
AA48 1014_E 2 00 00000000 "USB/TP06/NP06: An invalid asynchronous data packet has been specified"
AA48 1015_E 2 00 00000000 "USB/TP06/NP06: There are not enough system resources to complete the operation"
AA48 1016_E 2 00 00000000 "USB/TP06/NP06: Specified interface was not found in the current configuration"
AA48 1017_E 2 00 00000000 "USB/TP06/NP06: Operation cannot be executed while the USB device is in the current
state"
AA48 1018_E 2 00 00000000 "USB/TP06/NP06: Invalid parameter has been specified with an IOCTL operation"
AA48 1019_E 2 00 00000000 "USB/TP06/NP06: Evaluation interval of the USBIO DEMO version has expired"
AA48 101A_E 2 00 00000000 "USB/TP06/NP06: Invalid power state has been specified"
AA48 101B_E 2 00 00000000 "USB/TP06/NP06: Device has entered a power down state"
AA48 101C_E 2 00 00000000 "USB/TP06/NP06: API version reported by the USBIO driver does not match"
AA48 101D_E 2 00 00000000 "USB/TP06/NP06: Set configuration operation has failed, error is reported by the USBIO"
AA48 1086_E 2 00 00000000 "USB/TP06/NP06: The operation has failed due to a restriction of the USBIO LIGHT ver-
sion"
AA48 1100_E 2 00 00000000 "USB/TP06/NP06: The specified device object does not exist"
AA48 1102_E 2 00 00000000 "USB/TP06/NP06: Device object was opened, there is no valid handle to execute the oper-
ation"
AA48 1104_E 2 00 00000000 "USB/TP06/NP06: Enumeration of the specified devices has failed"
AA48 1105_E 2 00 00000000 "USB/TP06/NP06: Invalid parameter has been passed to a function"
AA48 1106_E 2 00 00000000 "USB/TP06/NP06: Library setupapi.dll could not be loaded"
AA48 2000_E 2 00 00000000 "USB/TP06/NP06: Set configuration request has failed"
AA48 3000_E 2 00 00000000 "USB/TP06/NP06: Buffer is too small, error is reported by the USB bus driver USBD"
AA48 4000_E 2 00 00000000 "USB/TP06/NP06: Interface was not found, error is reported by the USB bus driver
USBD"
AA48 5000_E 2 00 00000000 "USB/TP06/NP06: Invalid pipe flags have been specified"
AA48 6000_E 2 00 00000000 "USB/TP06/NP06: Operation has been timed out, error is reported by the USB bus driver"
AA48 7000_E 2 00 00000000 "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 0001_E 0 00 06000000 "LYNX TRX: Card was captured"
6434 0001_W 2 12 06000000 "LYNX TRX: Card was captured"
6434 0002_E 4 07 40000000 "LYNX TRX: Receipt printer not configured"
6434 0003_E 4 08 40000000 "LYNX TRX: Statement printer not configured"
6434 0004_E 2 00 0007000000000000 "LYNX TRX: Statement was retracted"
6434 0004_W 2 00 0007000000000000 "LYNX TRX: Statement was retracted"
6434 0005_W 4 08 0000000000000000000000 "LYNX TRX: Deposit general error"
6434 0006_E 2 00 0000000000000000000000 "LYNX TRX: Deposit was cancelled"
6434 0007_E 2 00 0000000000000000000000 "LYNX TRX: Deposit timeout"
6434 0008_E 4 00 0000000000000000000000 "LYNX TRX: Deposit not configured"
6434 0009_E 4 20 000000000000000000 "LYNX TRX: Cash dispenser not configured"
6434 000A_W 4 00 00000000 "LYNX TRX: Journal printer general error"
6434 000B_W 4 00 00000000 "LYNX TRX: Receipt printer general error"
6434 000C_W 4 00 00000000 "LYNX TRX: Document printer general error"
6434 000D_W 4 20 0000000000 "LYNX TRX: Card reader general HW error"
6434 000E_E 4 00 00000000 "LYNX TRX: Journal printer error, spooler active"
6434 000E_W 2 00 00000000 "LYNX TRX: Journal printer warning, spooler active"
6434 0010_E 2 00 00000000000000000000 "LYNX TRX: Money was retracted error"
6434 0010_W 2 00 00000000000000000000 "LYNX TRX: Money was retracted warning"
6434 0011_W 2 05 0000000000000000000000 "LYNX TRX: Deposit shutter not opened"
6434 0012_W 2 00 0001 "LYNX TRX: Panel Protection door problem"
6434 0013_W 2 12 06000040 "LYNX TRX: Card read threshold"
6434 0014_W 2 00 01000000000000000000 "LYNX TRX: Cassette low"
6434 0015_W 2 00 02000000 "LYNX TRX: Journal paper low, warning"
6434 0015_E 2 00 02000000 "LYNX TRX: Journal paper low, error"
6434 0016_W 2 00 02000000 "LYNX TRX: Receipt paper low"
6434 0017_W 2 00 0200000000000000 "LYNX TRX: Document paper low"
6434 0018_E 2 11 0400000000000000000 "LYNX TRX: Try to dispense with money in transport"
6434 0019_E 2 07 0000000000 "LYNX TRX: Card write attempt but no track data"
6434 0020_W 2 13 1000000000000000000 "LYNX TRX: CDM shutter error"
6434 0021_W 4 09 0000000000000000000000 "LYNX TRX: Deposit bin missing"
6434 0022_W 4 01 0000000000000000000000 "LYNX TRX: Deposit jam"
6434 0023_W 4 01 0000000000000000000000 "LYNX TRX: Deposit envelope jam"
6434 0024_W 4 11 0000000000000000000000 "LYNX TRX: Deposit no envelope"
6434 0025_W 4 08 0000000000000000000000 "LYNX TRX: Deposit printer failure"
6434 0026_W 2 01 0000000000000000000000 "LYNX TRX: Deposit envelope size"
6434 0027_W 2 04 0000000000000000000000 "LYNX TRX: Deposit shutter not close"
6434 0028_W 4 11 0000000000000000000000 "LYNX TRX: Deposit bin full"
6434 0028_E 4 11 0000000000000000000000 "LYNX TRX: Deposit bin full (ADRS)"
6434 0029_W 4 38 0600000000 "LYNX TRX: Card reader bin overfilled"
6434 002A_E 2 00 000000 "LYNX TRX: CAS - CDM: Consumer timeout in screen dialog 907"
6434 002B_E 2 00 000000 "LYNX TRX: CAS - CDM: Consumer has cancelled screen dialog 907"
6434 002C_E 2 00 0000000000000000000000 "LYNX TRX: CAS - DEP: Consumer timeout in screen dialog 906"
6434 002D_E 2 00 0000000000000000000000 "LYNX TRX: CAS - DEP: Consumer has cancelled screen dialog 906"
6434 002E_E 2 00 000000 "LYNX TRX: CAS - DOC: Consumer timeout in Screen dialog 909"
6434 002F_E 2 00 000000 "LYNX TRX: CAS - DOC: Consumer has cancelled screen dialog 909"
6434 0030_E 2 04 000000 "LYNX TRX: Envelope dispenser LOW"
6434 0031_E 4 06 000000 "LYNX TRX: Envelope dispenser EMPTY"
6434 0032_W 2 02 000000 "LYNX TRX: Envelope dispenser error"
6434 0033_W 2 01 000000 "LYNX TRX: Envelope dispenser jam"
6434 0034_W 2 02 000000 "LYNX TRX: Envelope dispenser shutter not close"
6434 0035_W 2 05 000000 "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 0036_E 2 36 0007000000000000 "LYNX TRX: Statement capture bin full"
6434 0037_E 4 05 08000000 "LYNX TRX: Journal paper nearly empty, error"
6434 0037_W 2 05 08000000 "LYNX TRX: Journal paper nearly empty, warning"
6434 0038_E 2 08 40000800 "LYNX TRX: Receipt paper nearly empty"
6434 0039_E 2 12 00000000000000000000 "LYNX TRX: Shutter not close or money jam, dispense operation
declined"
6434 0040_E 4 05 40000800 "LYNX TRX: Receipt paper jam or paper empty"
6434 0041_E 4 05 08000000 "LYNX TRX: Journal paper jam or paper empty"
6434 0042_E 2 12 06000000 "LYNX TRX: Card was captured after jam"
6434 0043_W 2 05 08000000 "LYNX TRX: Hard disk free space becomes low"
6434 0043_E 4 05 08000000 "LYNX TRX: No hard disk free space available"
6434 0044_E 2 02 0000000000 "LYNX TRX: Card write attempted but track not installed"
6434 0045_E 2 04 0000000000 "LYNX TRX: Card write command failed"
6434 0046_E 4 04 0000000000 "LYNX TRX: Card trap active"
6434 0047_E 4 04 0000000000 "LYNX TRX: Mouth piece vandalism"
6434 0048_E 4 04 0000000000 "LYNX TRX: Card reader skimming active"
Cash Dispenser (Class: 643A)

Table 125: Cash Dispenser (Class: 643A)
643A DEFA_W 2 03 01100000000000000000 "LYNX CDM: Warning not found, use default entry"
643A DEFA_E 2 03 01100000000000000000 "LYNX CDM: Error not found, use default entry"
643A 0001_E 4 41 00004000000000000000 "LYNX CDM: Invalid cassette number"
643A 0002_E 2 04 00000303030300000000 "LYNX CDM: Try from empty or low cassette"
643A 0002_W 2 04 00000303030300000000 "LYNX CDM: Not dispenseable"
643A 0003_E 2 00 00000000000000000000 "LYNX CDM: Safe door open during dispense"
643A 0004_E 4 07 00000000000000000000 "LYNX CDM: Reject cassette not operational"
643A 0005_E 4 08 00000000000000000000 "LYNX CDM: Reject cassette full"
643A 0006_E 4 08 00000000000000000000 "LYNX CDM: Max retracts reached"
643A 0007_E 2 07 06000000000000000000 "LYNX CDM: Reject bin missing"
643A 0008_E 4 11 02000000000000000000 "LYNX CDM: Max present errors after dispense"
643A 0009_E 4 10 00000000000000000000 "LYNX CDM: Cash dispenser fatal"
643A FEB5_W 2 00 00000000000000000000 "LYNX WOSA RTC: -331 (Order not allowed)"
643A FEB6_W 2 14 00000000000000000000 "LYNX WOSA RTC: -330 (Shutter not closed)"
643A FEC0_W 2 03 00000000000000000000 "LYNX WOSA RTC: -320 (Denomination error)"
643A FEC3_W 2 03 00000000000000000000 "LYNX WOSA RTC: -317 (No documents, no bills)"
643A FEC4_W 2 01 00000000000000000000 "LYNX WOSA RTC: -316 (Invalid cash unit)"
643A FEC5_W 2 14 00000000000000000000 "LYNX WOSA RTC: -315 (Shutter closed)"
643A FEC6_W 2 13 00000000000000000000 "LYNX WOSA RTC: -314 (Shutter open)"
643A FEC7_W 2 14 00000000000000000000 "LYNX WOSA RTC: -313 (Shutter not open)"
643A FEC8_W 2 34 00000000000000000000 "LYNX WOSA RTC: -312 (Invalid retract)"
643A FEC9_W 2 00 00000000000000000000 "LYNX WOSA RTC: -311 (Safe door open)"
643A FECA_W 2 03 00000000000000000000 "LYNX WOSA RTC: -310 (Position locked)"
643A FECB_W 2 03 00000000000000000000 "LYNX WOSA RTC: -309 (Invalid position)"
643A FECC_W 2 17 00000000000000000000 "LYNX WOSA RTC: -308 (Documents, bills left)"
643A FECD_W 2 03 00000000000000000000 "LYNX WOSA RTC: -307 (Too many documents)"
643A FECE_W 2 04 00000000000000000000 "LYNX WOSA RTC: -306 (Not dispensable)"
643A FECF_W 2 04 00000000000000000000 "LYNX WOSA RTC: -305 (No currency mix)"
643A FED0_W 2 04 00000000000000000000 "LYNX WOSA RTC: -304 (Invalid mix type)"
643A FED1_W 2 04 00000000000000000000 "LYNX WOSA RTC: -303 (Invalid denomination)"
643A FED2_W 2 09 00000000000000000000 "LYNX WOSA RTC: -302 (Cash unit error)"
02DF FED2_E 2 09 00000000000000000000 "LYNX WOSA RTC: -302 return of CheckDispOutput()"
434 October 2004 U25604-J-Z745-1-7600


643A FED3_W 2 09 00000000000000000000 "LYNX WOSA RTC: -301 (Invalid teller ID)"
643A FED4_W 2 01 00000000000000000000 "LYNX WOSA RTC: -300 (Invalid currency)"
643A FFF2_W 2 03 01100000000000000000 "LYNX WOSA RTC: Hardware error, cannot dispense"
643A FFF3_W 2 03 01100000000000000000 "LYNX WOSA RTC: Hardware error, device not ready"
643A FEB5_E 2 00 00000000000000000000 "LYNX WOSA RTC: -331 (Order not allowed)"
643A FEB6_E 2 14 00000000000000000000 "LYNX WOSA RTC: -330 (Shutter not closed)"
643A FEC0_E 2 03 00000000000000000000 "LYNX WOSA RTC: -320 (Denomination error)"
643A FEC3_E 2 03 00000000000000000000 "LYNX WOSA RTC: -317 (No documents, no bills)"
643A FEC4_E 2 01 00000000000000000000 "LYNX WOSA RTC: -316 (Invalid cash unit)"
643A FEC5_E 2 14 00000000000000000000 "LYNX WOSA RTC: -315 (Shutter closed)"
643A FEC6_E 2 13 00000000000000000000 "LYNX WOSA RTC: -314 (Shutter open)"
643A FEC7_E 2 14 00000000000000000000 "LYNX WOSA RTC: -313 (Shutter not open)"
643A FEC8_E 2 34 00000000000000000000 "LYNX WOSA RTC: -312 (Invalid retract)"
643A FEC9_E 2 00 00000000000000000000 "LYNX WOSA RTC: -311 (Safe door open)"
643A FECA_E 2 03 00000000000000000000 "LYNX WOSA RTC: -310 (Position locked)"
643A FECB_E 2 03 00000000000000000000 "LYNX WOSA RTC: -309 (Invalid position)"
643A FECC_E 2 17 00000000000000000000 "LYNX WOSA RTC: -308 (Documents, bills left)"
643A FECD_E 2 03 00000000000000000000 "LYNX WOSA RTC: -307 (Too many documents)"
643A FECE_E 2 04 00000000000000000000 "LYNX WOSA RTC: -306 (Not dispensable)"
643A FECF_E 2 04 00000000000000000000 "LYNX WOSA RTC: -305 (No currency mix)"
643A FED0_E 2 04 00000000000000000000 "LYNX WOSA RTC: -304 (Invalid mix type)"
643A FED1_E 2 04 00000000000000000000 "LYNX WOSA RTC: -303 (Invalid denomination)"
643A FED2_E 2 09 00000000000000000000 "LYNX WOSA RTC: -302 (Cash unit error)"
643A FED3_E 2 09 00000000000000000000 "LYNX WOSA RTC: -301 (Invalid teller ID)"
643A FED4_E 2 01 00000000000000000000 "LYNX WOSA RTC: -300 (Invalid currency)"
643A FFF2_E 2 03 01100000000000000000 "LYNX WOSA RTC: Hardware error, cannot dispense"
Security Module (Class: 643C)

Table 126: Security Module (Class: 643C)
643C 0001_E 4 38 00000000 "LYNX SEC: Set key error, possibly wrong keys"
643C 0002_E 2 70 00000000 "LYNX SEC: PIN check error, possibly wrong keys"
643C 0003_E 2 70 00000000 "LYNX SEC: Error while creating host PIN block"
643C 0004_E 2 38 00000000 "LYNX SEC: Error calculating MAC"
643C 0005_E 2 38 00000000 "LYNX SEC: Error initializing transaction"
CashIn transaction (Class: 6446)

Table 127: CashIn transaction (Class: 6446)
6446 0001_E 4 01 0000000000000000 "LYNX CASHIN: CashIn not operational"
000001
6446 0002_E 2 02 0000000000000000 "LYNX CASHIN: CashIn input shutter jam"
000002
6446 0003_E 3 03 0000000000000000 "LYNX CASHIN: CashIn input tray jam"
000003
6446 0004_E 4 04 0000000000000000 "LYNX CASHIN: CashIn input transport jam"
000004
6446 0005_E 2 05 0000000000000000 "LYNX CASHIN: CashIn output shutter jam"
000005
U25604-J-Z745-1-7600 October 2004 435

Application Error Classes (LYNX errors)M-Status & M-Data Reference Table

6446 0006_E 4 06 0000000000000000 "LYNX CASHIN: CashIn output tray jam"
000006
6446 0007_E 4 07 0000000000000000 "LYNX CASHIN: CashIn output transport jam"
000007
6446 0008_E 2 08 0000000000000000 "LYNX CASHIN: CashIn BIM not operational"
000008
6446 0009_E 2 09 0000000000000000 "LYNX CASHIN: CashIn retracted"
000009
6446 000A_E 3 10 0000000000000000 "LYNX CASHIN: CashIn input stacker jam"
000010
6446 000B_E 4 11 0000000000000000 "LYNX CASHIN: CashIn output stacker jam"
000011
6446 000C_E 2 13 0000000000000000 "LYNX CASHIN: Hardware error on Drum 1"
000013
6446 000D_E 2 14 0000000000000000 "LYNX CASHIN: Hardware error on Drum 2"
000014
6446 000E_E 2 15 0000000000000000 "LYNX CASHIN: Hardware error on Drum 3"
000015
6446 000F_E 2 16 0000000000000000 "LYNX CASHIN: Hardware error on Drum 4"
000016
6446 0010_E 4 17 0000000000000000 "LYNX CASHIN: Jam during transport on Drum"
000017
6446 0011_E 2 18 0000000000000000 "LYNX CASHIN: One CashIn box is now overfilled"
000018
6446 0012_E 2 19 0000000000000000 "LYNX CASHIN: CashIn boxes are overfilled"
000019
6446 0013_E 4 20 0000000000000000 "LYNX CASHIN: Metal in CashIn tray detected"
000020
6446 0014_E 2 21 0000000000000000 "LYNX CASHIN: CashIn reject bin full"
000021
6446 0015_E 2 22 0000000000000000 "LYNX CASHIN: Security stripe sensor defective"
000022
6446 0016_E 2 23 0000000000000000 "LYNX CASHIN: Metal sensor defective"
000023
6446 0017_E 2 24 0000000000000000 "LYNX CASHIN: Escrow empty"
000024
6446 0018_E 2 25 0000000000000000 "LYNX CASHIN: Error TRX reply buffer"
000025
6446 0019_E 2 26 0000000000000000 "LYNX CASHIN: Good Rollback, but L2 notes retracted"
000026
6446 001A_E 2 27 0000000000000000 "LYNX CASHIN: Rollback failed, all notes retracted"
000027
6446 001B_E 2 28 0000000000000000 "LYNX CASHIN: Good Cashin, but L2 notes retracted"
000028
6446 001C_E 2 29 0000000000000000 "LYNX CASHIN: Good Rollback, but all notes retracted after consumer time-
000029 out"
6446 001D_E 2 30 0000000000000000 "LYNX CASHIN: CashIn cancelled by consumer, host reply not yet received"
000030
6446 001E_E 2 31 0000000000000000 "LYNX CASHIN: Good Rollback, but L3 notes not returned"
000031
6446 001F_E 2 32 0000000000000000 "LYNX CASHIN: Good Rollback, but L2+L3 notes not returned"
000032
6446 0020_E 2 33 0000000000000000 "LYNX CASHIN: Good Cashin, but L3 notes not returned"
000033
6446 0021_E 2 34 0000000000000000 "LYNX CASHIN: Good Cashin, but L2+L3 notes not returned"
000034
EMV transaction (Class: 6459)

Table 128: EMV transaction (Class: 6459)
6459 0001_W 2 77 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 DEFA_E 2 01 00000000 "LYNX CHEQUE: Cheque device jammed"
645A 0001_E 2 01 00000000 "LYNX CHEQUE: Cheque acception error"
645A 0002_E 2 02 00000000 "LYNX CHEQUE: Error during cheques storing"

645A 0003_E 2 03 00000000 "LYNX CHEQUE: Error during ejecting cheques"
645A 0004_E 2 04 00000000 "LYNX CHEQUE: Present timeout, cheque will be captured"
645A 0005_E 2 05 00000000 "LYNX CHEQUE: Retract error, cheque may be still in IO path"
645A 0006_E 2 06 00000000 "LYNX CHEQUE: Retract bin full, no more cheques can be captured"
645A 0007_E 2 07 00000000 "LYNX CHEQUE: Cheque flush error"
645A 0008_E 2 08 00000000 "LYNX CHEQUE: Cheque device jammed"
645A 0009_E 2 09 00000000 "LYNX CHEQUE: Cheque archiving failed, check path configuration"
645A 000A_E 2 10 00000000 "LYNX CHEQUE: Shutter jammed or blocked during MediaIn"
645A 000B_E 2 11 00000000 "LYNX CHEQUE: General hardware error of CCDM"
645A 000C_E 2 12 00000000 "LYNX CHEQUE: Safe door open, trx not allowed"
Electronic Journal (Class: 0091)

Table 130: EMV transaction (Class: 0091)
0091 DEFA_E 4 07 40000000 "E-JRN: E-Journal file could not be written"
0091 0001_E 4 07 40000000 "E-JRN: E-Journal file could not be written"
0091 0002_E 4 07 40000000 "E-JRN: E-Journal file could not be written"
0091 0003_E 4 07 40000000 "E-JRN: EJ/SAF-Journal file could not be written"
U25604-J-Z745-1-7600 October 2004 437

WOSA Error Classes) M-Status & M-Data Reference Tables
WOSA Error Classes)
WOSA Cash Dispenser (Class: 00B9)

Table 131: WOSA Cash Dispenser (Class: 00B9)
00B9 D010_E 4 09 00000000000000000000 "WOSA CDM/CRS: Firmware faulty, stopped"
00B9 D016_E 4 09 00000000000000000000 "WOSA CDM/CRS: Booter Firmware faulty, stopped"
00B9 D020_E 4 09 00000000000000000000 "WOSA CDM/CRS: V.24 line problem master <==> slave"
00B9 D025_E 4 09 00000000000000000000 "WOSA CDM/CRS: Slave controller without Firmware"
00B9 D100_E 4 09 00000000000000000000 "WOSA CDM/CRS: Safe controller faulty"
00B9 D101_E 4 09 00000000000000000000 "WOSA CDM/CRS: Safe controller no booter or faulty"
00B9 D105_E 4 09 00000000000000000000 "WOSA CDM/CRS: Counter controller faulty"
00B9 D106_E 4 09 00000000000000000000 "WOSA CDM/CRS: Counter controller no booter or faulty"
00B9 D110_E 4 09 00000000000000000000 "WOSA CDM/CRS: Firmware not loaded"
00B9 D120_E 2 09 00000000000000000000 "WOSA CDM/CRS: Safety switch of safe module open"
00B9 D125_E 2 09 00000000000000000000 "WOSA CDM/CRS: Safety switch of counter module open"
00B9 D135_E 4 10 00000000000000000000 "WOSA CDM/CRS: Device lock after retract & quit"
00B9 D136_E 4 10 00000000000000000000 "WOSA CDM/CRS: Device lock after jam in counter area"
00B9 D140_E 4 09 00000000000000000000 "WOSA CDM/CRS: Hardware requirements not ok"
00B9 D145_E 4 09 00000000000000000000 "WOSA CDM/CRS: Hardware requirements not ok"
00B9 D146_E 4 09 00000000000000000000 "WOSA CDM/CRS: Requirements for BIM missing"
00B9 D170_E 2 01 0000000000000000000000 "WOSA CDM/CRS: Money jam during cash-in"
00B9 D180_E 2 09 00000000000000000000 "WOSA CDM/CRS: Note jam in safe area cassettes"
00B9 D181_E 2 09 00000000000000000000 "WOSA CDM/CRS: Note jam in safe area roller"
00B9 D182_E 2 09 00000000000000000000 "WOSA CDM/CRS: Note jam in safe area cassettes"
00B9 D185_E 2 09 01100000000000000000 "WOSA CDM/CRS: Note jam in counter area (cash out tray)"
00B9 D200_E 2 09 00000000000000000000 "WOSA CDM/CRS: Switch in safe area faulty/blocked"
00B9 D205_E 2 09 00000000000000000000 "WOSA CDM/CRS: Switch in counter area faulty/blocked"
00B9 D210_E 2 09 00000000000000000000 "WOSA CDM/CRS: Measurement station in safe area faulty"
00B9 D214_E 4 05 00000000000000000000 "WOSA CDM/CRS: Tape sensor in BIM module reports error"
00B9 D215_E 2 09 00000000000000000000 "WOSA CDM/CRS: Measurement station in counter area faulty"
00B9 D216_E 2 09 00000000000000000000 "WOSA CDM/CRS: BIM reader line faulty"
00B9 D217_E 2 09 00000000000000000000 "WOSA CDM/CRS: BIM communication faulty"
00B9 D218_E 2 09 00000000000000000000 "WOSA CDM/CRS: BIM note signals missing/inacceptable"
00B9 D219_E 2 09 00000000000000000000 "WOSA CDM/CRS: BIM returns error in call response"
00B9 D220_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor intensifier faulty"
00B9 D230_E 2 09 00000000000000000000 "WOSA CDM/CRS: Switch in safe area faulty / blocked"
00B9 D250_E 2 09 00000000000000000000 "WOSA CDM/CRS: Transport motor in safe area faulty"
00B9 D285_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error during cash out tray handling"
00B9 D286_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error during filling tray handling"
438 October 2004 U25604-J-Z745-1-7600

M-Status & M-Data Reference Tables WOSA Error Classes)

00B9 D287_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error during cash out tray handling"
00B9 D295_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor of cash out tray covered"
00B9 D296_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor of filling tray covered"
00B9 D310_E 2 09 00000000000000000000 "WOSA CDM/CRS: Too many bundle reject cassette 1"
00B9 D405_E 2 09 00000000000000000000 "WOSA CDM/CRS: No separation possible"

00B9 D407_E 2 09 00000000000000000000 "WOSA CDM/CRS: Metal in input tray detected"
00B9 D408_E 2 09 00000000000000000000 "WOSA CDM/CRS: Security stripe sensor defect"
00B9 D510_E 2 09 00000000000000000000 "WOSA CDM/CRS: Too many bad bills cassette 1"
00B9 D605_E 2 09 00000000000000000000 "WOSA CDM/CRS: ESCROW faulty (no signals)"
00B9 D610_E 2 09 00000000000000000000 "WOSA CDM/CRS: Cassette 1 faulty, write error"
00B9 D611_E 2 09 00000000000000000000 "WOSA CDM/CRS: Roller 1 or switch faulty"
00B9 D621_E 2 09 00000000000000000000 "WOSA CDM/CRS: Roller 2 oder switch faulty"
00B9 D700_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor is dirty"
00B9 D710_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photo or pressure sensor faulty"
00B9 D901_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor is dirty (counter area)"
00B9 D911_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor is dirty (safe area)"
U25604-J-Z745-1-7600 October 2004 439


00B9 D931_E 2 09 00000000000000000000 "WOSA CDM/CRS: Photosensor roller1 dirty"
00B9 D941_E 2 09 00000000000000000000 "WOSA CDM/CRS: Wrong position roller1 or 36V missing"
00B9 DF01_E 2 09 00000000000000000000 "WOSA CDM/CRS: Metal or/and Stripe sensor defect"
00B9 DF03_E 2 09 00000000000000000000 "WOSA CDM/CRS: Metal or/and Stripe sensor defect"
00B9 FE71_E 2 09 00000000000000000000 "WOSA CDM/CRS: Wrong height of note in input tray"
00B9 FE9F_E 2 09 00000000000000000000 "WOSA CDM/CRS: Metal in CashIn tray detected"
00B9 FEA0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Safe door must be closed during this command"
00B9 FEA1_E 2 09 00000000000000000000 "WOSA CDM/CRS: CashIn security failure"
00B9 FEA2_E 2 09 00000000000000000000 "WOSA CDM/CRS: Output position is not empty"
00B9 FEB9_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application or configuration error"
00B9 FEBA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FEBB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FEBC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FEBD_E 2 09 00000000000000000000 "WOSA CDM/CRS: Money taken during retract"
00B9 FEBE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error in bills presentation"
00B9 FEBF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error in bills presentation"
00B9 FEC0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Error in bills presentation"
00B9 FEC1_E 2 09 00000000000000000000 "WOSA CDM/CRS: Operator intervention required"
00B9 FEC2_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FEC3_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FEC4_E 2 09 00000000000000000000 "WOSA CDM/CRS: No bills available"
00B9 FEC5_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FECA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Operator intervention required"
00B9 FECB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Position locked"
00B9 FECC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FECD_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FECE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FECF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FED0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FED1_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FED2_E 2 09 00000000000000000000 "WOSA CDM/CRS: Operator intervention required"
00B9 FED3_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FED4_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FFCA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFCB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FFCC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFCD_E 2 09 00000000000000000000 "WOSA CDM/CRS: Installation error"
00B9 FFCE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFCF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFD0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
440 October 2004 U25604-J-Z745-1-7600

M-Status & M-Data Reference Tables WOSA Error Classes)

00B9 FFD1_E 2 09 00000000000000000000 "WOSA CDM/CRS: Installation error"
00B9 FFD5_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"

00B9 FFDA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFDB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFDC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFDD_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFDE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Installation error"
00B9 FFDF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFE0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFEA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFEB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFEC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFED_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFEE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFEF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFF0_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFF2_E 2 09 00000000000000000000 "WOSA CDM/CRS: Hardware error"
00B9 FFF4_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FFFA_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FFFB_E 2 09 00000000000000000000 "WOSA CDM/CRS: Configuration error"
00B9 FFFC_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
00B9 FFFD_E 2 09 00000000000000000000 "WOSA CDM/CRS: Installation error"
00B9 FFFE_E 2 09 00000000000000000000 "WOSA CDM/CRS: Installation error"
00B9 FFFF_E 2 09 00000000000000000000 "WOSA CDM/CRS: Application error"
U25604-J-Z745-1-7600 October 2004 441

442 October 2004 U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User1LOT.fm
Tables
Tables
Table 1: Basic Software of ProCash/NDC . . . . . . . . . . . . . . . 20
Table 2: Basic Software of ProConsult/NDC . . . . . . . . . . . . . 21
Table 3: Standard fonts table . . . . . . . . . . . . . . . . . . . . . 31

Table 4: Software structure . . . . . . . . . . . . . . . . . . . . . . 34
Table 5: State summary . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 6: ProCash/NDC, ProConsult/NDC steps belonging to NDC states 58
Table 7: Card Read state entries . . . . . . . . . . . . . . . . . . . 59
Table 8: Read condition entry definitions . . . . . . . . . . . . . . . 62
Table 9: PIN Entry state entries . . . . . . . . . . . . . . . . . . . . 64
Table 10: Customer Selectable PIN state entries . . . . . . . . . . . . 67
Table 11: Extension state entries . . . . . . . . . . . . . . . . . . . . 70
Table 12: Envelope Deposit (C) state entries . . . . . . . . . . . . . . 71
Table 13: Pre-Set Operation Code Buffer state table . . . . . . . . . . 72
Table 14: Preset operation code buffer Extension state table . . . . . 76
Table 15: Four FDK Select Function state entries . . . . . . . . . . . 78
Table 16: Amount Entry state entries . . . . . . . . . . . . . . . . . . 81
Table 17: Amount Check state entries . . . . . . . . . . . . . . . . . 84
Table 18: Information Entry state entries . . . . . . . . . . . . . . . . 87
Table 19: Transaction Request state entries . . . . . . . . . . . . . . 90
Table 20: Extension state entries . . . . . . . . . . . . . . . . . . . . 93
Table 21: Close state entries . . . . . . . . . . . . . . . . . . . . . . 96
Table 22: FIT Switch state entries . . . . . . . . . . . . . . . . . . . 99
Table 23: Card Write state entries . . . . . . . . . . . . . . . . . . . 102
Table 24: Enhanced PIN Entry state entries . . . . . . . . . . . . . . 104
U25604-J-Z745-1-7600 October 2004 443

Tables
Table 25: Enhanced Amount Entry state entries . . . . . . . . . . . . 107
Table 26: Extension state entries . . . . . . . . . . . . . . . . . . . 110
Table 27: Language Code Switch state entries . . . . . . . . . . . . 112
Table 29: Card Read - PIN Entry Initiation state entries . . . . . . . . 116
Table 31: Language Select From Card state entries . . . . . . . . . . 120
Table 32: FDK Switch state entries . . . . . . . . . . . . . . . . . . 123
Table 33: FDK Information Entry state entries . . . . . . . . . . . . . 126
Table 35: Eight FDK Selection state entries . . . . . . . . . . . . . . 132
Table 38: Audio Control state entries . . . . . . . . . . . . . . . . . 139
Table 39: Hardware Fitness state entries . . . . . . . . . . . . . . . 142
Table 40: Hardware Fitness Extension state entries . . . . . . . . . . 145
Table 41: Smart FIT Check State . . . . . . . . . . . . . . . . . . . 148
Table 42: Skip state step . . . . . . . . . . . . . . . . . . . . . . . . 152
Table 43: Screen control characters cross-reference . . . . . . . . . 154
Table 44: Screen control characters . . . . . . . . . . . . . . . . . . 154
Table 45: Screen escape sequences cross-reference . . . . . . . . . 157
Table 46: Screen escape sequences . . . . . . . . . . . . . . . . . 157
Table 47: Default Voice Message files . . . . . . . . . . . . . . . . . 160
Table 48: Default WAVE files for Audio Echo on Keyboard . . . . . . 161
Table 49: Downloaded reserved screens supported by Wincor Nixdorf

terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
444 October 2004 U25604-J-Z745-1-7600

Tables
Table 50: Timer values . . . . . . . . . . . . . . . . . . . . . . . . . 168
Table 51: Alphabetical FIT references . . . . . . . . . . . . . . . . . 189
Table 52: FIT fields listed by data track position . . . . . . . . . . . . 190
Table 53: MAC flags definition . . . . . . . . . . . . . . . . . . . . . 200

Table 54: Code conventions . . . . . . . . . . . . . . . . . . . . . . 206
Table 55: Transaction Request message . . . . . . . . . . . . . . . . 209
Table 56: Solicited Status message . . . . . . . . . . . . . . . . . . . 218
Table 57: Unsolicited Status message . . . . . . . . . . . . . . . . . 223
Table 58: Transaction Reply command message . . . . . . . . . . . . 226
Table 59: Terminal Command message . . . . . . . . . . . . . . . . 236
Table 60: State Tables Load . . . . . . . . . . . . . . . . . . . . . . 239
Table 61: Screen Data Load . . . . . . . . . . . . . . . . . . . . . . 242
Table 62: Configuration Parameters Load . . . . . . . . . . . . . . . 245
Table 63: Enhanced Configuration Parameters Load . . . . . . . . . . 249
Table 64: Option codes . . . . . . . . . . . . . . . . . . . . . . . . . 251
Table 65: Interactive Transaction Response . . . . . . . . . . . . . . 254
Table 66: FIT Data Load . . . . . . . . . . . . . . . . . . . . . . . . 258
Table 67: Encryption Key Load . . . . . . . . . . . . . . . . . . . . . 261
Table 68: Extended Encryption Key Load . . . . . . . . . . . . . . . 264
Table 69: Dispenser Currency Mapping Table Load . . . . . . . . . . 267
Table 70: Configuration IDLoad . . . . . . . . . . . . . . . . . . . . . 270
Table 71: Date And Time Load . . . . . . . . . . . . . . . . . . . . . 272
Table 72: Message Authentication Field Selection Load . . . . . . . . 275
Table 73: Specific Command Reject Conditions . . . . . . . . . . . . 281
Table 74: NDC function ID’s assigned to step functions . . . . . . . . 287
Table 75: Send Options And Timers message format . . . . . . . . . 296
U25604-J-Z745-1-7600 October 2004 445

Tables
Table 76: Acknowledge And Continue . . . . . . . . . . . . . . . . . 299
Table 77: Acknowledge And Stop . . . . . . . . . . . . . . . . . . . 301
Table 78: Send Configuration Information . . . . . . . . . . . . . . . 304
Table 79: Hardware Fitness Table . . . . . . . . . . . . . . . . . . . 305
Table 80: Hardware Fitness Table Enhanced . . . . . . . . . . . . . 306
Table 81: Device Configuration Table . . . . . . . . . . . . . . . . . 307
Table 82: Supply Status Device Table . . . . . . . . . . . . . . . . . 311
Table 83: Supply Counters . . . . . . . . . . . . . . . . . . . . . . . 313
Table 84: Send Error Log Information . . . . . . . . . . . . . . . . . 316
Table 85: Send Date/Time Info . . . . . . . . . . . . . . . . . . . . . 320
Table 86: Hardware Configuration Data . . . . . . . . . . . . . . . . 321
Table 87: Supplies Data . . . . . . . . . . . . . . . . . . . . . . . . 324
Table 88: Fitness Data . . . . . . . . . . . . . . . . . . . . . . . . . 325
Table 89: Tamper and Sensor Status Data . . . . . . . . . . . . . . . 327
Table 90: Software ID and Release Number . . . . . . . . . . . . . . 328
Table 91: Local Configuration Option Digits . . . . . . . . . . . . . . 330
Table 92: Solicited Status (Device Fault) . . . . . . . . . . . . . . . . 331
Table 93: Error Severity Table . . . . . . . . . . . . . . . . . . . . . 332
Table 94: Supplies Status Table . . . . . . . . . . . . . . . . . . . . 334
Table 95: Unsolicited Device Status . . . . . . . . . . . . . . . . . . 335
Table 96: Electronic Journal Upload message format . . . . . . . . . 364
Table 97: Printer Models . . . . . . . . . . . . . . . . . . . . . . . . 367
Table 98: NDC Printer control characters . . . . . . . . . . . . . . . 368
Table 99: Cash Dispenser V1 (Class: 0007) . . . . . . . . . . . . . . 379
Table 100:Cash Dispenser NG (Classes: 0018/001D)) . . . . . . . . 383
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) . . . . 405
Table 103:Encryption Decryption Software (EDS) (Class: 0011) . . . . 406
Table 104:Card Reader (Class: 0008/AA08) . . . . . . . . . . . . . . 407
Table 105:Deposit Module (Class: 0017/AA17) . . . . . . . . . . . . . 411

Table 106:Vandal Guard (Class: 0015) . . . . . . . . . . . . . . . . . 414
Table 107:Motorized Door (Class: 000E) . . . . . . . . . . . . . . . . 415
Table 108:Printer (Class: 0032) . . . . . . . . . . . . . . . . . . . . . 416
Table 114:Printer (Class: 003E) . . . . . . . . . . . . . . . . . . . . . 422
Table 115:Printer (Class: 003F) . . . . . . . . . . . . . . . . . . . . . 423
Table 121:Printer (Class: AA45) . . . . . . . . . . . . . . . . . . . . . 428
Table 123:Printer (Class: AA48) . . . . . . . . . . . . . . . . . . . . . 431
Table 124:Transaction (Class: 6434) . . . . . . . . . . . . . . . . . . 433
Table 125:Cash Dispenser (Class: 643A) . . . . . . . . . . . . . . . . 434
Table 126:Security Module (Class: 643C) . . . . . . . . . . . . . . . . 435
Table 127:CashIn transaction (Class: 6446) . . . . . . . . . . . . . . 435
U25604-J-Z745-1-7600 October 2004 447

Tables
Table 128:EMV transaction (Class: 6459) . . . . . . . . . . . . . . . 436
Table 129:Cheque transaction (Class: 645A) . . . . . . . . . . . . . 437
Table 130:EMV transaction (Class: 0091) . . . . . . . . . . . . . . . 437
Table 131:WOSA Cash Dispenser (Class: 00B9) . . . . . . . . . . . 438
448 October 2004 U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\User1LOF.fm
Figures
Figures
Figure 1: Terminal operation . . . . . . . . . . . . . . . . . . . . 41
Figure 2: Transaction message flow . . . . . . . . . . . . . . . . 206
Figure 3: Terminal to network messages . . . . . . . . . . . . . . 208

Figure 4: Network to terminal commands . . . . . . . . . . . . . . 225
Figure 5: Transaction Reply message accept/reject flowchart . . . 286
U25604-J-Z745-1-7600 October 2004 449

Figures
450 October 2004 U25604-J-Z745-1-7600

Pfad: E:\FRAMEMAK\NDC_DDC.NT\USER-NDC\userabk.fm
Abbreviations
API Application Program Interface
ARC Application Return Code

ASCII American Standard Code for Information Interchange
ATM Automated Teller Machine
CDM Cash Dispenser Module
CI Customization Image
CRT Cathode Ray Tube
CSC Customer Service Center
CSP Customer Selected PIN
DES Data Encryption Standard
EBCDIC Extended Binary Coded Decimal Interchange Code
FDK Function Display Key
FIT Financial Institution Table
ID IDentification
IDCU ID Card Unit
ITR Interactive Transaction Response
MAC Message Authentication Code
MDS Modular Delivery System
NCR National Cash Register
NDC NCR Direct Connect
U25604-J-Z745-1-7600 October 2004 451

Abbreviations
OAR Open Account Relationship
PAN Primary Account Number
PC Personal Computer
PCCP PC Configurator Package
PIN Personal Identification Number
POS Point of Sales (Cash Registers)
QLLC Qualified Logical Link Control
SDLC Synchronous Data Link Control
SNA System Network Architecture
SOH State Of Health
SST Self Service Terminal
TABS Total Automatic Banking System
452 October 2004 U25604-J-Z745-1-7600

Pfad: E:\FRAM EMAK\NDC_DDC.NT\USER-NDC\Userlit.fm
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 VERSION ORDER NUMBER

ProCash/NDC-DDC Prog. Reference 1.1/03 (PDF file)
ProCash/NDC Installation manual 1.3/00 (PDF file)
ProConsult/NDC Installation manual 1.3/00 (PDF file)
ProCashIn/Online 1.1/00 (PDF file)
Installation & Configuration manual
GDI Printer Overlay Framework 1.3/00 (PDF file)
User Guide
ProCash/NDC-DDC 1.3/00 (PDF file)
ProConsult/NDC-DDC 1.1/00
WEB-Extensions
Installation & Configuration manual
Protopas Module Construction Kit 4.1/00 (PDF file)
Programming Guide
Protopas Framework Documentation 4.1/00 (PDF file)
Programming Guide
Protopas Host Protocol and 4.1/00 (PDF file)
Communication Frameworks
Programming Guide
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

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 API’s 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

Wincor Document PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Wincor Document PDF

Încărcat de

Drepturi de autor:

Formate disponibile

ProCash/NDC V1.

Edition October 2004

Copyright © Wincor Nixdorf GmbH & Co. KG 2004.

Additional useful Information

FDK Switch State (W) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Hardware Fitness State (‘h’) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Security Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Local PIN Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Terminal Command message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

– Send Configuration Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Additional Useful Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

M-Status & M-Data Reference Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 379

Card Reader (Class: 0008/AA08) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453

● New section ”Electronic Journal Upload (EJU) commands” on page 295

Since May 2002 until November 2003:

Since October 2001 until May 2002:

Wincor Nixdorf Solution

Purpose of the Document

Introduction Function Overview

continued on next page ...

Introduction Multi Vendor capability

Multi Vendor capability

Software Products of ProCash/NDC

Table 1: Basic Software of ProCash/NDC

Name current Systems

Introduction Software Products of ProConsult/NDC

Software Products of ProConsult/NDC

Table 2: Basic Software of ProConsult/NDC

Name current Systems

Dynamic Link Libraries (DLL)

● NDC Printer Framework (ndcprtfw.dll)

Software Structure Dynamic Link Libraries (DLL)

● GDI Printer Overlay Framework (dcPrtGdi.dll)

about GDI printing with ProCash/NDC and ProConsult/NDC.

Parameter / Data Files

Every terminal needs many different parameters to operate as expected. The

Software Structure Parameter / Data Files

Compatible Customization Data

All customization data are stored in the Windows registry location:

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

are the predefined display screens provided by the host.

Extended Configuration Data

● Application Parameters (LYNXPAR\APPLICATION )

Software Structure Parameter / Data Files

● Function ID mapping (LYNXPAR\FUNC_ID_MAP)

This section contain the assignment to the ProCash/NDC or

Global Screen Configuration

The global non downloaded screen configuration contains default display

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

Error Mapping Configuration

They are stored in the following location of the Windows registry:

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

Software Structure Font Files

automatically like standard Windows fonts.

Font name File name Designation 640x480 800x600 1024x768

Table 4: Software structure

File Structure Description

System Setup Directory Structure

File Structure Description

dcTcp2h.dll TcpIP converter for 2 bytes binary headers

File Structure Description

System Setup Directory Structure