ProCash NDC-DDC InstallationManual

Installation Guide
ProCash/NDC V3.1/20
ProCash/DDC V3.1/20
Document version: 001

Edition date: September 11, 2018
Protection Class: Public
copyright © Wincor Nixdorf International GmbH, 2018 1

Trademark Rights
As long as hardware and software names are contained in this document, they
may have been also registered as trademarks of their respective product owners
and shall be treated as such. Diebold Nixdorf has, in the main, followed the
manufacturers' spelling for product names.
Confidentiality Undertaking
Copyright © Wincor Nixdorf International GmbH September 2018.
The contents of this document may not be reproduced, exploited or published,
whether in whole or in part, without the prior written permission of
Wincor Nixdorf International GmbH.
The copyright applies to all forms of storage and reproduction in which this
information is incorporated including, but not limited to, magnetic memory,
computer printouts and visual displays. Offenders will be prosecuted and liable for
all cost and damages incurred by the breach. All rights, including rights created by
patent grant or registration of a utility model or design, are reserved. Right of any
technical modifications reserved.
Names and Other Data

The names, e-mail addresses, telephone numbers and other data used in this doc-
ument are purely fictional (except the e-Mail addresses listed below to return
feedback to this document). Any resemblance to actual persons, living or dead, is
coincidental.
Comments, Findings
In case there is something you want to tell us about this document please inform
us via our iSupport interface. There you can open an incident to inform us
regarding comments or findings related to this document:
External: https://www.dieboldnixdorf.com/de-de/support/egate
Internal: https://ebusiness.wincor-nixdorf.com/OA_HTML/iSupportLogin.jsp
If you do not have access to iSupport and there is nobody known having an
account, please login to the Diebold Nixdorf Learning Suite
(https://training.wincor-nixdorf.com) and complete the iSupport Web-based
training (WBT) to receive access to iSupport.

Contents
Contents
Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What’s new ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Software Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Product short description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Open/JVM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ProBase/C Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Hardware Configuration Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Customization File for ProBase/C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
PROBASE.CUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Customization of ProBase/C 1.4/xx with ACU . . . . . . . . . . . . . . . . . . . . . . . 37
Import ACU (XML) configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Customization Files for ProSetup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
PROSETUP.CUS and PROSETUP.PAR . . . . . . . . . . . . . . . . . . . . . . . . 38
J/Install Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Registration Key Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Product Updates via J/Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Customizing Media for J/Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Enable ProAgent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Rich Client Manager Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Creation of Installation Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Multi Vendor Installation capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Installation subfolders of custom/update files . . . . . . . . . . . . . . . . . . . . . 45
The Installation Disk Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Installation of Terminal Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Run application as "Non Administrator" user . . . . . . . . . . . . . . . . . . . . . . . . 48
Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 1 - Windows Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Windows 7 + SP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Windows 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Step 2 - Communication Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Step 3 - J/Install Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Contents
PROEINFO installation log folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Parameter Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Dialog main and sub menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Parameters in “CUSTOM.PPF” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
[START_APPLICATION] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Program list called by the Restart Manager . . . . . . . . . . . . . . . . . . . . . . 60
[STARTUP] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Communication framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Operator panel framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
EPP framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Special Electronics framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Cash Dispenser framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Cash Dispenser framework Instance 2 . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Cash Dispenser framework Instance 3 . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Coin Dispenser framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Card Reader framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Camera framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Journal framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Service Handler framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Dialog framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Application framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Data framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Variable framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Converter framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Presentation framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Protocol framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Message Control framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Receipt Printer framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Journal Printer framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Document Printer framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Device Status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Deposit framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Transaction framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Script framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Utility framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Security framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
ProCash/XDC-SOP dialog framework . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Contents
Barcode Reader framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

System Restart settings of the Restart Manager . . . . . . . . . . . . . . . . . . . . . 75
Automatic System shut down & restart . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Maximum system reboots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Power up period timer to clear actual reboot counter . . . . . . . . . . . . . . . 76
Configurable screen during system shut down . . . . . . . . . . . . . . . . . . . . 76
[CCPROTFW1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Message Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Character Conversion Table location . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Messages log file location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Size of Messages log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Append ETX character to the end of a message . . . . . . . . . . . . . . . . . . 78
Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
[SNA] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
– SNA Communication Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
– Strip Function Management Header (FMH) . . . . . . . . . . . . . . . . . . . 79
– SNA open timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
– NAUTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
– Logical Unit Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
– Communication response timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
– Receive buffer size of project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
– OPMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
– Destination Logical Unit Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
– OPUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
– OPPASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
– OPLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
[X25] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
– X.25 Communication Framework . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
– Number of Virtual Circuits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
– Short hold mode time delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
– Waiting time for “Call Accept” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
– Waiting time for “Call Request” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
– Waiting time for “Clear Request” . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
– Number of calling retries to open X.25 connection . . . . . . . . . . . . . . 87
– Calling delay timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
– Receive buffer size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
– X.25 connection index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
– Type of Virtual Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
– Suppress TLS trace output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Contents
– Buffer size in send direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

– Buffer size in receive direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
– Permanent Virtual Circuit (PVC) number . . . . . . . . . . . . . . . . . . . . . 90
– Delivery control for send and receive direction . . . . . . . . . . . . . . . . . 90
– Activate Short Hold Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
– Short Hold Mode passive configuration . . . . . . . . . . . . . . . . . . . . . . 91
– Start Short Hold Mode passive connection . . . . . . . . . . . . . . . . . . . . 92
– Connection reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
– Diagnostic code setting for SHM clear cause . . . . . . . . . . . . . . . . . . 93
– Closed user group selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
– Closed user group outgoing call assignment . . . . . . . . . . . . . . . . . . 94
– Add Reversed Charging Facility to “Call Request” packets . . . . . . . 94
– Accept Reversed Charging Facility of incoming calls . . . . . . . . . . . . 95
– Add Call User Data to “Call Request” packets . . . . . . . . . . . . . . . . . 95
– Check Call User Data of incoming calls . . . . . . . . . . . . . . . . . . . . . . 96
– Local station address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
– Remote station (host) address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
[TCPIP] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
– TCP/IP Communication Framework . . . . . . . . . . . . . . . . . . . . . . . . . 98
– Remote station (host) address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
– TCP port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
– Keep Alive mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
– TCP/IP open timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
– Connection retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
– Send timeout timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
– Close timeout timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
– Local port address configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
– Coding DLL location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
– Size of memory blocks need to allocate . . . . . . . . . . . . . . . . . . . . . 103
TCP/IP parameters used by Windows . . . . . . . . . . . . . . . . . . . . . . . . . 104
– KeepAliveTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
– TcpKeepTries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
– TcpKeepCnt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
– KeepAliveInterval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
– TcpMaxDataRetransmissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
[SSL_PROJECT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
– Remote station (host) address . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
– SSL port number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
– SSL Coding DLL location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Contents
– SSL Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

– SSL Message length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
[LYNXCI_PARAMETER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Optional Parameters (NDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Miscellaneous Features I (DDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Miscellaneous Features II (DDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Miscellaneous Features III (DDC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Logical Unit Number (LUNO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Configuration Identification (Config ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
[LYNXCI_TIMER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Keyboard response time (Timer 00) . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Additional time (Timer 01) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Close state time delay (Timer 02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Communication response time (Timer 03) . . . . . . . . . . . . . . . . . . . . . . 118
Envelope insertion time (Timer 04) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Cash retract time-out ( Timer 05) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Poll/select time (Timer 06) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Take cash time (Timer 07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Card capture time (Timer 09) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Additional cash present time (Timer 10) . . . . . . . . . . . . . . . . . . . . . . . . 120
Document/Envelope present timeout (Timer 94) . . . . . . . . . . . . . . . . . 120
Statement retract (Timer 95) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Statement present (Timer 96) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Vandal guard close (Timer 98) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Vandal guard close time (Timer 99) . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Unsupported timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
[LYNXCI_SCREEN] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Screen default foreground color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Screen default background color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Screen transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Blink rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Graphic file location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Configure MacroMedia Flash Animations . . . . . . . . . . . . . . . . . . . . . . . 127
Palette file location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Character Width screen global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Character Height screen global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Screen horizontal offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Screen vertical offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Screen background picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Contents
Play videos in full screen mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

ESC substitution character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Graphic and Video file extension mapping . . . . . . . . . . . . . . . . . . . . . . 133
Stop Video after screen delay sequence (NDC only) . . . . . . . . . . . . . . 134
Touch zone support in PIN entry dialogs (EPP only) . . . . . . . . . . . . . . 134
Assign "Confirm" FDK in PIN entry dialogs (EDM only) . . . . . . . . . . . . 135
Configure default Audio path for NDC . . . . . . . . . . . . . . . . . . . . . . . . . 135
Configure default Audio path for DDC . . . . . . . . . . . . . . . . . . . . . . . . . 136
Configurable substitution character on display . . . . . . . . . . . . . . . . . . . 136
Specific supervisor mode screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Configure number of PIN digits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
[SCREEN_XXX] [1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Foreground Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Background Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Screen idle next screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Screen idle time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Character Width screen specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Character Height screen specific . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Screen contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Screen horizontal offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Screen vertical offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Screen transparent mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Screen background picture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Screen display contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Set Curser position for consumer inputs locally . . . . . . . . . . . . . . . . . . 143
– Upper left offset of the input rectangle . . . . . . . . . . . . . . . . . . . . . . 143
– Upper top offset of the input rectangle . . . . . . . . . . . . . . . . . . . . . . 144
– Lower right offset of the input rectangle . . . . . . . . . . . . . . . . . . . . . 144
– Lower bottom offset of the input rectangle . . . . . . . . . . . . . . . . . . . 144
– Input adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Language bank screen parameters (DDC only) . . . . . . . . . . . . . . . . . . . . 146
[TOP_MSG] and [CUST_MSG] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Event and Error message definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 147
– Format Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Event and Error message destination . . . . . . . . . . . . . . . . . . . . . . . . . 149
[HARDWARE_CONFIGURATION] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Hardware Configuration Parameters (NDC) . . . . . . . . . . . . . . . . . . . . . 150
Unsol./Sol. message logging on journal . . . . . . . . . . . . . . . . . . . . . . . . 151
Expanded Hardware Configuration Parameters (DDC) . . . . . . . . . . . . 152

Contents
MACing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

– Send TVN and MAC in Transaction Request messages . . . . . . . . 153
– Check TVN and MAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
– Send Machine Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
– Check Machine Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
– Send TVN and MAC in solicited status . . . . . . . . . . . . . . . . . . . . . . 154
– Field selected MACing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
– ASCII MACing activation in EBCDIC line environments . . . . . . . . . 155
M-Data and MDS i series status code handling . . . . . . . . . . . . . . . . . . 155
Go offline after host reply timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
RKL message encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
SAF Machine Number (DDC only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
[APPLICATION_XXX][1] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Hardware Fitness Fitness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Resend Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Suspend Mode timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Resend Power up message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Sensor messages for terminal doors . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Force Supervisor Mode when door open . . . . . . . . . . . . . . . . . . . . . . . 160
Solicited and Unsolicited message queuing . . . . . . . . . . . . . . . . . . . . . 161
Default Miscellaneous Features (DDC only) . . . . . . . . . . . . . . . . . . . . 162
Switch on/off logo light together with ready indicator . . . . . . . . . . . . . . 162
Ready/Supply/Amount option defaults (NDC) . . . . . . . . . . . . . . . . . . . 163
Card Read/Write error threshold defaults . . . . . . . . . . . . . . . . . . . . . . . 164
Enter "Out of service" mode after line reconnect . . . . . . . . . . . . . . . . . 164
Rear Balancing host timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Configure Customer Relays 1 - 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
– LED_IN_SERVICE (ATM is in service mode) . . . . . . . . . . . . . . . . . 167
– LED_CUSTOMER (transaction active) . . . . . . . . . . . . . . . . . . . . . . 167
– LED_CASH (cash cassette(s) has/have low or out status) . . . . . . . 167
– LED_PAPER (printer paper low) . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
– LED_SERVICE (technical service required) . . . . . . . . . . . . . . . . . . 168
– LED_SVR_MODE (ATM in supervisor mode) . . . . . . . . . . . . . . . . . 168
Configure Remote Sensor Indicators (RSI) . . . . . . . . . . . . . . . . . . . . . 169
– RSI Status GREEN (RELAY3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
– RSI Status YELLOW (RELAY2) . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
– RSI Status RED (RELAY1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Configure Remote Status Monitor (RSM) . . . . . . . . . . . . . . . . . . . . . . . 172
LED Mapping for systems of other vendors . . . . . . . . . . . . . . . . . . . . . 173

Contents
Guide Light flash rate control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Offline Reboot timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Enable double length keys for triple DES . . . . . . . . . . . . . . . . . . . . . . . 176
Zero filled General Purpose Buffer B and C . . . . . . . . . . . . . . . . . . . . . 176
Configurable cassette names on journal . . . . . . . . . . . . . . . . . . . . . . . 178
Configurable text for reject/retract counter on journal . . . . . . . . . . . . . 179
ADRS options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
ADRS max retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Store downloaded COM key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Force displaying "Card captured" screen in close state . . . . . . . . . . . . 182
Print immediate processing options . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Configure anti skimming, mouthpiece and alarm sensors . . . . . . . . . . 183
– Initial Status after application start . . . . . . . . . . . . . . . . . . . . . . . . . 187
Display receipt delivered screen in close state . . . . . . . . . . . . . . . . . . . 188
Use Close (J) state Timer 02 always . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Delay after Transaction Request processing . . . . . . . . . . . . . . . . . . . . 189
Screen delay time for FID ’Z’ (DDC only) . . . . . . . . . . . . . . . . . . . . . . . 189
Options for PAN handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Monitor SEL boot switch (Wincor only) . . . . . . . . . . . . . . . . . . . . . . . . . 190
Monitor Safe door . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Reconnection delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Power Save Mode delay time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
NDC LTS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Host Protocol (HP) Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
D91x compatible options parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
CAS dialog timer parameters (DDC only) . . . . . . . . . . . . . . . . . . . . . . . . . 194
Time-out for CAS of cash dispenser . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Time-out for CAS of deposit module . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Time-out for CAS of receipt printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Time-out for CAS of document printer . . . . . . . . . . . . . . . . . . . . . . . . . 197
Check CAS of deposit module during dispense . . . . . . . . . . . . . . . . . . 198
[CASH_DISPENSER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Number of logical cassettes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Set cassettes currencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Set cassettes values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Default number of notes loaded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Automatic cassettes logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Automatic cassettes logon in SOP session . . . . . . . . . . . . . . . . . . . . . 201
Set initial number of notes for auto logon cassettes . . . . . . . . . . . . . . . 202

Contents
Send cash low message only if whole denomination low . . . . . . . . . . . 203

Set dispense algorithm (ATM’s only) . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Ignore cash counters for removed cassettes . . . . . . . . . . . . . . . . . . . . 204
Send unsol. Cash low message not only once . . . . . . . . . . . . . . . . . . . 205
Stop dispensing after max. number of present errors . . . . . . . . . . . . . 206
Set fatal after max. number of failed dispenses . . . . . . . . . . . . . . . . . . 207
Send sol. message on Cash present time-out (NDC only) . . . . . . . . . . 208
Cash retract through Presenter Dump ’Q’ (DDC only) . . . . . . . . . . . . . 208
Send missing (’@’) for fatal cassettes (DDC only) . . . . . . . . . . . . . . . . 209
Allow dispense if cassettes counter < 0 (NDC only) . . . . . . . . . . . . . . . 210
Security timer between dispense and presenting money . . . . . . . . . . . 210
Logical cassettes mapping for ATM’s with more than 4 cassettes . . . . 211
Check cash dispenser shutter status after money taken . . . . . . . . . . . 213
Upper case Denomination ID for cassettes (DDC only) . . . . . . . . . . . . 213
Present failure screen and synchronous retract . . . . . . . . . . . . . . . . . . 214
Screen display options during cash present . . . . . . . . . . . . . . . . . . . . . 214
Cash Dispenser fatal if reject bin not operational . . . . . . . . . . . . . . . . . 215
Dispense retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Dispense retries after hardware error . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Currency Exponent correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Maximum cash retracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Guide Light Control on AFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Low threshold for physical cassettes . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Maximum dispense time (watch dog) . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Withdrawal Retract logging and recycling on RM3 . . . . . . . . . . . . . . . . 220
WOSA XFS30 Parameters (Wincor Nixdorf only) . . . . . . . . . . . . . . . . . 221
– Number of minimum bills („money low“ limit) . . . . . . . . . . . . . . . . . 221
– Number of maximum bills to be rejected . . . . . . . . . . . . . . . . . . . . . 221
[COIN_DISPENSER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Number of coin hoppers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Set coin hopper currency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Set coin hopper values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Set coin dispense flags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Number of coin hoppers reported to the host . . . . . . . . . . . . . . . . . . . . 224
[DEPOSIT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Options to dispense envelopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Screen to be displayed during envelope dispense . . . . . . . . . . . . . . . . 226
Screen "Please wait for an envelope" . . . . . . . . . . . . . . . . . . . . . . . . . 227
Allow to cancel deposit transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

Contents
Disable printing on retracted envelopes . . . . . . . . . . . . . . . . . . . . . . . . 228

Deposit print character mapping table . . . . . . . . . . . . . . . . . . . . . . . . . 228
Deposit entry splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Prepare envelope dispense . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
[CARD_READER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Default track read definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Default chip data read on Smart Cards . . . . . . . . . . . . . . . . . . . . . . . . 230
Card insert/eject wake up time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
"Remove Card" screen for left cards in DIP reader . . . . . . . . . . . . . . . 231
Read tracks during insert or remove direction (SWIPE) . . . . . . . . . . . . 232
Card manipulation threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Card jam threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
DIP eject screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Contactless Reader Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
[BARCODE] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Configure barcode type formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
[OPERATOR_SCREENS] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Printer header for Operator screens . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
[JOURNALPRINTER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Set journal destination on paper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Journal printer CPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Journal printer LPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Double Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Condensed Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Electronic journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Send Spooler active or journal printer error message . . . . . . . . . . . . . 240
Keep original printer status if Spooler is configured . . . . . . . . . . . . . . . 241
Force to send "Paper Out" message on paper out supply . . . . . . . . . . 241
Assign codepage control sequence to NDC font type . . . . . . . . . . . . . 242
Print journal host data always prior function ID’s . . . . . . . . . . . . . . . . . 242
Hard disk free space low threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Enable journal file writing error messages . . . . . . . . . . . . . . . . . . . . . . 243
Configure EJU or SAF shared mapping file . . . . . . . . . . . . . . . . . . . . . 244
Configure EJU or SAF maximum file size . . . . . . . . . . . . . . . . . . . . . . 244
EJU journal NCR compatible mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
Extended range of characters in file journal . . . . . . . . . . . . . . . . . . . . . 245
Print unicode (GDI only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
[ELECTRONIC_JOURNAL] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Maximum journal files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Contents
Journal Spooler reset sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Journal Spooler check timer for Spooler data . . . . . . . . . . . . . . . . . . . 248
Journal Spooler threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Maximum spool file size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Maximum unprinted spool data size . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
[RECEIPTPRINTER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Receipt printer CPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Receipt printer LPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Receipt printer character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Double Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Condensed Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Receipt printer page header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Receipt printer page footer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Receipt footer line position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
LED timer during receipt delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Enable R01 print data merging (NDC only) . . . . . . . . . . . . . . . . . . . . . 254
Assign codepage control sequence to NDC font type . . . . . . . . . . . . . 254
Force receipt delivery after each host reply . . . . . . . . . . . . . . . . . . . . . 255
Force to send "Paper Out" message on paper out supply . . . . . . . . . . 255
Options during Rear Balancing print . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
[DOCUMENTPRINTER] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Document printer CPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Document printer LPI setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Document printer character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Double Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Condensed Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Document printer page header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Document printer page footer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Document footer line position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Maximum documents to be collected before delivery . . . . . . . . . . . . . . 261
Cancel document processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Printer Font parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Font type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Double Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Condensed Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
User defined Character set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Printer initialization macros or characters . . . . . . . . . . . . . . . . . . . . . . . 266

Contents
Printer character mapping table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Print unicode font specific (GDI only) . . . . . . . . . . . . . . . . . . . . . . . . . . 268
GDI Windows name for receipt printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
GDI Windows name for document printer . . . . . . . . . . . . . . . . . . . . . . . . . 269
Screen Font configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
[VIEWER_FONT] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Number of screen fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Font name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Font size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Font height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
Font Resolution tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
NDC font identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
NDC double size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Display characters in proportional mode . . . . . . . . . . . . . . . . . . . . . . . 277
Resolution dependent WINNT Font installation . . . . . . . . . . . . . . . . . . . . . 278
Resolution dependent Bitmap/Icon installation . . . . . . . . . . . . . . . . . . . . . 278
User defined WINNT fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Enable and preconfigure ProAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Set Primary/Secondary Server and Port . . . . . . . . . . . . . . . . . . . . . . . 280
Terminal ID of ATM client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Enable Application Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
– Error description for ProAgent Server log window . . . . . . . . . . . . . 281
VDM Activation for ProAgent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
EMV parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Completion Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Contact Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
EMV Protocol Vendor Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Force decline AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Force decline AIDs for Transaction Type nn . . . . . . . . . . . . . . . . . . . . . 284
Force script error AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
Force script error AIDs for Transaction Type nn . . . . . . . . . . . . . . . . . . 285
Code Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Candidate list selection method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Ignore issuer script failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Transaction processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Preferred AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
EMV error conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
Ignore extended authorize failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

Contents
Supported US common AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

TLV data for contactless EMV initial transaction . . . . . . . . . . . . . . . . . 289
Contactless EMV TAG extraction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Contactless EMV TAG removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Contactless EMV error screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Contactless EMV offline error checking . . . . . . . . . . . . . . . . . . . . . . . . 292
Transaction Objects (DDC only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Acquirer Identifier 9F01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Merchant Category Code 9F15 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Terminal Country Code 9F1A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Terminal Capabilities 9F33 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Terminal Type 9F35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
Additional Terminal Capabilities 9F40 . . . . . . . . . . . . . . . . . . . . . . . . . 295
Vendor specific parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Number of physical cassettes names . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Configure physical names of cassettes units . . . . . . . . . . . . . . . . . . . . 296
Set number of maximum rejected notes . . . . . . . . . . . . . . . . . . . . . . . . 297
Set number of maximum retracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Enable test dispense function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Divide remaining notes equally to physical cassettes . . . . . . . . . . . . . 298
DDC Deposit Emulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Enable DDC Deposit Emulation feature . . . . . . . . . . . . . . . . . . . . . . . . 299
Operation Key Buffer Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
– Standard Deposit Op Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Operation Key Buffer Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
– Deposit Op Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Suppress Unsolicited Cash Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Redirect Function for host FID and Screen . . . . . . . . . . . . . . . . . . . . . 302
Redirect Next Function processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Print Form Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Print Tag and Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
Suppress sending Buffer IDs from ’@I ’ state . . . . . . . . . . . . . . . . . . . . 307
Suppress Cash In Buffer in Consumer Request message . . . . . . . . . . 308
Suppress Cheque Buffer in Consumer Request message . . . . . . . . . . 308
Parameter Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

The PARAC run . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Parameter update process via PARAC . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

Contents
PCEDT - PARAC Parameter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

Vendor and AddOn depended configuration . . . . . . . . . . . . . . . . . . . . . . . 312
ProCash/NDC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
ProCash/DDC parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Customize Error Mapping Table CCERRMAP . . . . . . . . . . . . . . . . . . . . . . 324
Configure multiple CDM Error Reasons for DDC . . . . . . . . . . . . . . . . . 325
Variables in MDS i series status: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Cassette specific variable in DDC912 status: . . . . . . . . . . . . . . . . . . . . 327
Variables in M-Data status field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Error Class mapping of CSC-W32 and XFS classes . . . . . . . . . . . . . . 328
Error mapping of XFS30 (WOSA) error events . . . . . . . . . . . . . . . . . . 329
Error Suppression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Configure DDC 911 protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Use ’CCERRMAP.INA’ for 911 mode . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Setup hardware configuration status fields for 911 mode . . . . . . . . . . . 330
Dispenser configuration for HI and LO denomination bills . . . . . . . . . . 331
Diebold 911 compatible HI and LO denomination mode . . . . . . . . . . . 332
Specific Step for dispense FID ’8’ in 911 Mode . . . . . . . . . . . . . . . . . . 333
Printer initialisation via macro tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
Macro parameters for Journal and Receipt printer . . . . . . . . . . . . . . . . 334
User defined Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Configurable ESC xx mapping to Macros . . . . . . . . . . . . . . . . . . . . . . . 337
Enable/Disable Secure Key Entry (SKE) mode . . . . . . . . . . . . . . . . . . . . . 338
Enable Triple DES operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Triple DES enabled via J/Install installation . . . . . . . . . . . . . . . . . . . . . 338
Switch to triple or single DES via SOP . . . . . . . . . . . . . . . . . . . . . . . . . 338
Enable GDI Windows print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
Automatic Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
GDI operation and configuration parameters . . . . . . . . . . . . . . . . . . . . 339
Configuration settings for TH23 on Cineo 4090 . . . . . . . . . . . . . . . . . . 340
Enable card less transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Repository configuration of CLTSTTFW.DLL . . . . . . . . . . . . . . . . . . . . 341
Dialog configuration parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Parameter fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Timeout parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
Screen display and exit for parallel FDK press . . . . . . . . . . . . . . . . . . . 343
Alpha numeric SMS key input style on EPP . . . . . . . . . . . . . . . . . . . . . . . 344
Assign values for Left/Right keys of the ’0’ key . . . . . . . . . . . . . . . . . . . . . 344
Dependent parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Contents
Specify cursor character for input position . . . . . . . . . . . . . . . . . . . . . . . . . 345

Specify cursor character for input position . . . . . . . . . . . . . . . . . . . . . . . . . 346
Set up character sequences for single EPP keys . . . . . . . . . . . . . . . . . . . 346
Input options for SMS input (NDC only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
Dialog options for SMS input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Allowed alpha numeric characters for SMS input . . . . . . . . . . . . . . . . . . . 349
Enable timer restart for input dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Encrypting Touch Screen (ETS) Systems . . . . . . . . . . . . . . . . . . . . . . . . . 351
Configure Dial Up communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Repository section [STARTUP] . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
– Protocol Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
– Modem Interface DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
– Serial Interface DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
– Communication Yield DLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Restart Manager section [START_APPLICATION] . . . . . . . . . . . . . . . 357
– Load dial up frameworks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Specific communication settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
– Modem automatic dial up number . . . . . . . . . . . . . . . . . . . . . . . . . . 358
– Modem initialisation command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
– Serial interface line attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
– Serial interface port name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Project settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
– COM channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
– Protocol channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
– Protocol type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
– Route ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
– Terminal ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Changing Network settings under restricted User . . . . . . . . . . . . . . . . . . . 362
Parameters for Forms printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Rich Client Manager (RCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Journal Event handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
– Free Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
– Joker Journal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Client Settlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Software updates via SOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

Update diskette creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Automatic update process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

Contents
Start and Stop Application services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Start application services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Stop application services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
Application Error Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Transaction Framework (Class 6434) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Cash Dispenser Framework (class 643A) . . . . . . . . . . . . . . . . . . . . . . . . . 371
Security Overlay Framework (Class 643C) . . . . . . . . . . . . . . . . . . . . . . . . 373
Registry Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Installation and Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

ProCash/NDC-DDC Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . 399
Font and Graphic utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
Analyzing utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Font tools for journal and receipt printers . . . . . . . . . . . . . . . . . . . . . . . . . 406
Font and Logo tools for printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
Logo print with ND9E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Font utilities for RJ03 series printers . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Miscellaneous tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Simulation utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Installation of communication SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Installation of Eicon Wan Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

Introduction
This manual provides a detailed description for service technicians how to
install the necessary software components needed to get ProCash/NDC or
ProCash/DDC running. It gives instructions in which order each product has to
be installed and which parameters you have to keep an eye on. Furthermore
this manual provides function descriptions about customizable parameters and
how to create a branch specific installation set.

What’s new ?
What’s new ?
This section lists a summary of documentation changes and extensions of the
ProCash/NDC - ProCash/DDC Installation Manual.
Since May 2017 until August 2018:
• New section ”Customization of ProBase/C 1.4/xx with ACU” on page 37
• New section ”D91x compatible options parameter” on page 193
• New section ”Guide Light Control on AFD” on page 218
• New section ”Open/JVM” on page 33
• New section ”DDC Deposit Emulation Parameters” on page 299
• Parameter DOUBLE_LENGTH_KEYS default changed to 10 to be PCI
compliant.
Additionally Secure Key Entry is enabled per default
(see section ”Enable/Disable Secure Key Entry (SKE) mode” on page 338)
• New section ”Encrypting Touch Screen (ETS) Systems” on page 351
Since February 2016 until May 2017:
• Windows 10 support
• New EMV contactless parameters added
• Version update, installation dialogs updated
• changed section ”Logical cassettes mapping for ATM’s with more than 4
cassettes” on page 211
Since June 2015 until February 2016:
• Set of EMV parameters added
• TP27 description added
• New section ”Cash Dispenser framework Instance 2” on page 64
• New section ”Cash Dispenser framework Instance 3” on page 64
• New section ”Camera framework” on page 65
Since November 2014 until June 2015:
• New section ”Client Settlement” on page 364
Since October 2013 until November 2014:

What’s new ?
• New section ”Configuration settings for TH23 on Cineo 4090” on page 340
• New section ”Rich Client Manager (RCM)” on page 363
• New section “Host Protocol (HP) Handling” on page 193
• New section ”Rich Client Manager Installation” on page 44
• New section ”Contactless Reader Handling” on page 234
• New section ”NDC LTS Options” on page 192
• Parameter PRINT_UNICODE documented
Since December 2012 until October 2013:

• New section ”Configurable ESC xx mapping to Macros” on page 337
• Description for obsolete FOnet configuration removed
• 2D Barcode types documented
• New section ”Parameters for Forms printing” on page 362
Since June 2012 until December 2012:

• SSL description updated
• Windows 7 support
• product version update
Since May 2011 until June 2012:

• New section ”SAF Machine Number (DDC only)” on page 157
• New section ”EMV Protocol Vendor Specification” on page 283
• New section ”Reconnection delay time” on page 191
Since March 2011 until May 2011:

• New section ”Reconnection delay time” on page 191
• New section ”Withdrawal Retract logging and recycling on RM3” on
page 220

What’s new ?
• New section ”Changing Network settings under restricted User” on

page 362
• New section ”Power Save Mode delay time” on page 192
Since November 2010 until March 2011:

• Changed section ”ProBase/C Installation” on page 34
• Changed section ”J/Install Installation” on page 39
Since October 2010 until November 2010:

• Changed section ”RKL message encoding” on page 156
Since April 2010 until October 2010:

• J/Install name introduced
• New section ”Guide Light flash rate control” on page 174
• New section ”Installation of Terminal Protection” on page 48
Since January 2010 until April 2010:

• Update process description extended and corrected
Since June 2009 until January 2010:

• New section ”[SSL_PROJECT]” on page 107
• New section ”Alpha numeric SMS key input style on EPP” on page 344
• New section ”Monitor Safe door” on page 191
• New section ”DIP eject screen” on page 233
Since August 2008 until June 2009:

• New section ”Monitor SEL boot switch (Wincor only)” on page 190
• New section ”RKL message encoding” on page 156

What’s new ?
• New section ”Enable/Disable Secure Key Entry (SKE) mode” on page 338
Since May 2007 until August 2008:

• New section ”Default number of notes loaded” on page 200
• New section ”ProBase/C Installation” on page 34
• Extended section ”Configure anti skimming, mouthpiece and alarm sensors”
on page 183
• New section ”Maximum dispense time (watch dog)” on page 219

What’s new ?
Since July 2006 until May 2007:

• New section ”Installation of Terminal Protection” on page 48
• New section ”Run application as "Non Administrator" user” on page 48
• New section ”Low threshold for physical cassettes” on page 218
• New section ”Card manipulation threshold” on page 232
• New section ”Card jam threshold” on page 233
• New section ”Delay after Transaction Request processing” on page 189
• New section ”Screen delay time for FID ’Z’ (DDC only)” on page 189
• New section ”Options for PAN handling” on page 190
Since September 2005 until July 2006:

• Extended section ”Font and Graphic utilities” on page 400
• New section ”Extended range of characters in file journal” on page 245
• New section ”EJU journal NCR compatible mode” on page 245
• New section ”Screen display options during cash present” on page 214
• New section ”Error mapping of XFS30 (WOSA) error events” on page 329
• New section ”PROEINFO installation log folder” on page 57
• New section ”Configure Remote Status Monitor (RSM)” on page 172
• New section ”[COIN_DISPENSER]” on page 222
• New section ”[BARCODE]” on page 235
• Extended section ”Miscellaneous tools” on page 424
• New section ”Configure Dial Up communication” on page 355
Since October 2004 until September 2005:

• Extended section ”Parameter Management” on page 309
• New section ”EMV parameters” on page 282
• New section ”Currency Exponent correction” on page 217
• New section ”Enable card less transactions” on page 341

What’s new ?
Since March 2004 until October 2004:

• Extended section ”Automatic cassettes logon” on page 201
• New section ”Deposit entry splitting” on page 229
• New section ”Prepare envelope dispense” on page 229
• Changed section ”Parameter Management” on page 309
• New section ”Use Close (J) state Timer 02 always” on page 188
• New section ”Vendor specific parameters” on page 296
• New section ”Display receipt delivered screen in close state” on page 188
• Extended section ”Font utilities for RJ03 series printers” on page 421
• New section “Go offline after host reply timeout” on page 156
• New section “The Installation Disk Manager” on page 46
• Changed section “Creation of Installation Media” on page 45
• New section ”Configure EJU or SAF shared mapping file” on page 244
• New section ”Configure EJU or SAF maximum file size” on page 244
• New section ”Print immediate processing options” on page 182
• New section ”Configure anti skimming, mouthpiece and alarm sensors” on
page 183
• New section ”Enable journal file writing error messages” on page 243
• New section ”Force displaying "Card captured" screen in close state” on
page 182
• New section ”Present failure screen and synchronous retract” on page 214
• Extended section ”ADRS options” on page 180
• Changed section ”ADRS max retries” on page 181
Since November 2003 until March 2004:

• New section ”Configure MacroMedia Flash Animations” on page 127
• New section ”Font utilities for RJ03 series printers” on page 421

What’s new ?
• New section ”Configure number of PIN digits” on page 137

• New section ”Deposit print character mapping table” on page 228
Since March 2003 until November 2003:

• New section ”Store downloaded COM key” on page 181
• New section ”Enable R01 print data merging (NDC only)” on page 254
• New section ”Screen "Please wait for an envelope"” on page 227
• New section ”ESC substitution character” on page 132
• New section ”Options during Rear Balancing print” on page 256
• Changed section ”Options to dispense envelopes” on page 225
• Changed section ”Screen to be displayed during envelope dispense” on
page 226
• New section ”Receipt printer page footer” on page 252
• New section ”Receipt footer line position” on page 253
• New section ”Document printer page footer” on page 260
• New section ”Document footer line position” on page 260
• New section ”Hard disk free space low threshold” on page 243
• New section ”Configure multiple CDM Error Reasons for DDC” on page 325
• New section ”Check cash dispenser shutter status after money taken” on
page 213
• New section ”Specific supervisor mode screen” on page 137
• New section ”Print journal host data always prior function ID’s” on page 242
• New section ”ADRS options” on page 180
• New section ”ADRS max retries” on page 181
• New section ”Upper case Denomination ID for cassettes (DDC only)” on
page 213
• New section ”Assign codepage control sequence to NDC font type” on
page 242 and 254.

What’s new ?
Since April 2002 until March 2003:

• Changed section ”[TOP_MSG] and [CUST_MSG]” on page 147
• New section ”Maximum unprinted spool data size” on page 249
• New section ”Maximum spool file size” on page 248
• New section “Printer initialization macros or characters” on page 266
• New section “Configurable text for reject/retract counter on journal” on
page 179
• New section “Configurable cassette names on journal” on page 178
• New section ”Enable GDI Windows print” on page 339
• New section ”GDI Windows name for document printer” on page 269
• New section ”GDI Windows name for receipt printer” on page 269
• New section ”Security timer between dispense and presenting money” on
page 210
• New section ”Default chip data read on Smart Cards” on page 230
• New section ”Logical cassettes mapping for ATM’s with more than 4
cassettes” on page 211
• New section ”Configurable substitution character on display” on page 136
• Extended section ”Options to dispense envelopes” on page 225
• New section ”Disable printing on retracted envelopes” on page 228
• New section ”Force to send "Paper Out" message on paper out supply” on
page 241 and 255.
• New section ”Zero filled General Purpose Buffer B and C” on page 176
• New section ”Enable Triple DES operation” on page 338
• Description of section ”Font and Logo tools for printers” on page 412
extended for TH30 and TH21/TH22.
• Extended section ”Miscellaneous tools” on page 424. Extensions for
SetHwPPF.EXE and CpyNtFnt.EXE

What’s new ?
Since October 2001 until April 2002:

• Changed section “Creation of Installation Media” on page 45
• New section “Send missing (’@’) for fatal cassettes (DDC only)” on
page 209
• Changed section “Automatic System shut down & restart” on page 75
• New section “CAS dialog timer parameters (DDC only)” on page 194
• New section “Configure Customer Relays 1 - 4” on page 165
• New section “Configure Remote Sensor Indicators (RSI)” on page 169
• New section “Offline Reboot timer” on page 175
• New section “Cash retract through Presenter Dump ’Q’ (DDC only)” on
page 208
• Enhanced section “Miscellaneous tools” on page 424.
New tool PRINTRAW.EXE
• New section “Keep original printer status if Spooler is configured” on
page 241
• New section “Configure default Audio path for NDC” on page 135
• New section “Configure default Audio path for DDC” on page 136
• New section “Logo print with ND9E” on page 420
• New section “Enable double length keys for triple DES” on page 176

What’s new ?
Since March 2001 until October 2001:

• Enhanced section ”Printer Font parameters” on page 263
• New section “Graphic and Video file extension mapping” on page 133
• New section “Touch zone support in PIN entry dialogs (EPP only)” on
page 134
• section “Assign "Confirm" FDK in PIN entry dialogs (EDM only)” on
page 135
• New section ”Send sol. message on Cash present time-out (NDC only)” on
page 208
• section ”Miscellaneous tools” on page 424 enhanced.
New tool PRT-RAW.EXE
Since December 2000 until March 2001:

• New section “Local port address configuration” on page 101
• New section “Printer initialisation via macro tables” on page 334
• New section “TCP/IP parameters used by Windows” on page 104
• New section “Stop dispensing after max. number of present errors” on
page 206
Since September until December 2000:

• New section “Creation of Installation Media” on page 45
• New section “System Restart settings of the Restart Manager” on page 75
• New section “Rear Balancing host timeout” on page 165
• Changed section “Force Supervisor Mode when door open” on page 160
• Changed section “Product short description” on page 31
• Changed section “Cash Dispenser framework” on page 63

Software Product Overview
Software Product Overview

ProCash/NDC and ProCash/DDC itself need a couple of external software
components which are assembled during the installation. The following figure
shows the software products which are necessary to build up the whole
ProCash/NDC or ProCash/DDC application.
Figure 1: Product Overview
CD Windows 7 or 10 CD
Communication Packets
CD EICON SNA CD
Software Workstation
ProBase/C 1.2 or 1.3 or 1.4

CD Device Drivers CD
Firmware CSC-W32
ProDevice (XFS)
3.1/20 NDC/DDC J
J
/
/
I
ProCash/NDC I
CD
N ProCash/DDC N
S
S
T
CD
T
A ProTopas Manager A
L L
L
AddOn Products L
ProAgent

Software Product Overview Product short description
Product short description

The following two tables give a short description about the software compo-
nents shown in Figure 1: Product Overview. Table “External Products”
describes external products delivered on separate CD’s.
Since introduction of release 2.0/00, The CSC-W32 operating system,
ProDevice (XFS) and Firmware are delivered separately as own installation CD
that has to be ordered as product ProBase/C.
Table “Components on "ProBase/C CD"” describes the company’s proprietary
product components up to XFS available on the ProBase/C CD.
Table “Core products and AddOns on "J/Install CD"” describes the company’s
application products available on the J/Install CD.
Table 1: External Products
NAME VERSION DESCRIPTION MEDIAS

Windows 7 or SP1 MS Windows 7 CD
Windows 10 MS Windows 10 CD
SNA SNA Workstation needs to be CD
Workstation installed if the ATM has to
communicate via SNA-SDLC
or SNA-QLLC with the host.
Table 2: Components on "ProBase/C CD"

CSC-W32 --- CSC Operating System CD
communicates directly with
the firmware of the hardware
devices.
ProDevice --- This component contains the CD
(WOSA) WOSA services used by
XFS 3.x ProTopas.
Firmware --- Service and Operating CD
functions for CSC applica-
tions on Windows.

Software Product Overview Product short description
Table 3: Core products and AddOns on "J/Install CD"
ProCash/NDC 3.1/20 Contains the specific frameworks CD

ProTopas/SOP-NDC and necessary accessories
which completes the
ProCash/DDC 3.1/20 ProCash/NDC-DDC products.
ProTopas/SOP-DDC
ProAgent 1.2/70 ProAgent CD

PARAC NT 3.2/40 PARAC is a parameter custom- CD
ization utility which provides the
Windows registry with
parameters of the products.
All defined parameters of each
product are merged together and
will be set into the registry in a
predefined sequence.
ProTopas 5.2/20 Contains ProTopas device frame- CD
Manager works and core components
required for the application
AddOn --- The AddOn Products are optional CD
Products components (exp. ProChip/EMV)
that can be installed with
additional Registration Keys

Software Product Overview Open/JVM
Open/JVM
With ProCash/NDC and ProCash/DDC 3.1/20 or higher versions the Open/JVM
will be installed and used as default. The Open/JVM is included on the product
CD and has replaced the Oracle/JVM.
Example entry in jinstall.cus: product.JRE.VERSION = 8u171dn.0
If required, it is still possible to install the Oracle/JVM via customizing.

Therefore following steps are needed:
• Put the Oracle Java installer into the root of your customizing folder just
next to the jinstall.cus file
• Customize the product.JRE.VERSION entry in your jinstall.cus to
reflect the version number of your Java installer
Example:
If the ORACLE JRE installer package is jre-8u151-windows-i586.exe,
following entry in jinstall.cus has to be set:
product.JRE.VERSION = 8u151

ProBase/C Installation Open/JVM
ProBase/C Installation
Since ProCash/NDC 2.0/00 the installation concept has been redesigned. As it
is shown in table “Product Overview” on page 30,
the CSC-W32 Operating System, T-SOP, Firmware, ProDevice (XFS) and
drivers are separated in a new Product CD named ProBase/C.
ProBase/C needs to be installed on Wincor hardware systems only.

ProBase/C should be installed in folder C:\ProBase only. Please do
not change the destination folder in the input selection dialog of
ProBase.
ProBase/C CD 1.3/00 is a non boot able medium and requires a ready installed
Windows operating system on the hard disk. Additional Windows device drivers
have to be installed from the Driver Utility CD that is delivered together with the
hardware system.
To install Windows, ProBase/C and the application layer on a clean formatted
hard disk, you have to use ProSetup for the installation.
Installation on existing Windows:

ProBase/C can also be installed on an existing Windows operating system.
The installation window automatically appear if you insert the ProBase/C or if
you call AUTORUN.BAT from the CD root folder.
For the ProBase/C installation you need the Hardware Configuration Media
(HW_CONF.INI) and minimum one Customizing Media where the customizing
file PROBASE.CUS has to be included. You can use "Installation Disk Manager"
for automatic creation of the Customizing Media. Refer to section ”Creation of
Installation Media” on page 45 for detailed description.
Important Note: With ProBase/C 1.3 or higher it is mandatory to copy manually
the parameter file PROBASE.CUS into a new folder \CusControl\CONF of the
installation media. Therefore you need to prepare your own ProBase/C media
(exp. USB memory stick) to be able to create folders and to add additional
custom files. You can also add the HW_CONF.INI into \CusControl\CONF.

ProBase/C Installation Open/JVM
Figure 2: ProBase/C Installation Medias
CD CD
ProBase/C
1. 2.
Hardware Customization
Media Media
Note: Instead of floppy diskettes you can use CD’s, USB or HDD medias
Please refer to ProBase Installation 1.3/00 User manual for detailed descriptions
how to install and customize the ProBase/C product.
Detailed descriptions about ProSetup configuration are described in
ProSetup User Manual.

ProBase/C Installation Hardware Configuration Media
Hardware Configuration Media

The Hardware Configuration Media contains the hardware configuration for the
self service system that you need to set up. The hardware configuration file
HW_CONF.INI“ contains device specific settings like specific hardware compo-
nents, driver settings, type of device communication (V.24, USB, COM) and that
has to be configured in the Windows registry for the present devices.
With each new ordered hardware system the specific Hardware Configuration
Media will be delivered automatically from the factory. Service technicians have
the possibility to create their own „HW_CONF.INI“ with the utility HW_CREATE
on the original J/Install CD. With HW_CREATE you can select the requested
hardware system, printers, card reader and additional devices that differ from
the standard configuration.
Customization File for ProBase/C
PROBASE.CUS
The Customization File PROBASE.CUS contains the parameter configuration

settings for the ProBase/C Operating system and XFS services.
The Customizing File will be automatically copied to the Customizing Media via
the "Installation Disk Manager". Refer to section ”Creation of Installation Media”
on page 45 for detailed description.
With ProBase/C 1.3/00 it is mandatory to copy PROBASE.CUS manually to
folder \CusControl\CONF of the ProBase/C installation media.

ProBase/C Installation Customization of ProBase/C 1.4/xx with ACU
Customization of ProBase/C 1.4/xx with ACU

With ProBase/C 1.4 the customization within Probase/C have to be done via the
ACU Configuration Utility after the ProBase/C installation. The customization
ACU also offers an export function where the customization can be extracted in
a set of XML configuration files.
Import ACU (XML) configuration files
ProCash/NDC & ProCash/DDC 3.1/20 has included a predefined ACU

configuration set, which is automatically copied into your customizing folder via
the Installation Disk Manager ("Diebold Nixdorf System" selection only). Refer
to section ”The Installation Disk Manager” on page 46 for details.
The ACU (XML) configuration files are stored under sub folder:
\CUSTOM\vendors\WN\ACU
These XML files have to be imported during the ProBase/C installation.
Therefore you have to copy all the XML files to sub folder <CCF>/ACU which is
used during the ProBase/C installation when the <CCF> folder is selected in the
ProBase/C installation dialog.
Please refer to ProBase/C 1.4 User Manual for detailed description how to handle
ACU configuration.

ProBase/C Installation Customization Files for ProSetup
Customization Files for ProSetup
PROSETUP.CUS and PROSETUP.PAR
The files PROSETUP.CUS and PROSETUP.PAR are configuration files used by

ProSetup. They will be automatically copied to the Customizing Media via the
"Installation Disk Manager". Refer to section ”Creation of Installation Media” on
page 45 for detailed description.
The new installation logic of ProBase/C 1.3/00 requires to have the customized
PROBASE.CUS available in folder \CusControl\CONF of the ProBase/C
installation media (exp. USB memory stick).
Please refer to ProSetup Version 3.3/00 User Manual for details how to prepare a
ProSetup installation package.

J/Install Installation Customization Files for ProSetup
J/Install Installation
The J/Install CD contains the application product components that will be
installed above ProBase/C on Wincor hardware systems. The core product and
AddOn products can be installed only with a valid security key (REG_KEY.INI).
This registration mechanism allows the installation of licensed software only.
Different hardware systems and their customer specific variations presuppose
specific configuration settings. Each customer has the possibility to create a
customized configuration for different branches. Furthermore the product
contents of the CD can be overloaded via an update configuration. The next
figure clarifies the combination of CD, registration, customization and update.
Please refer to J/Install User Guide to get detailed information about the instal-
lation concept and configuration possibilities.
Figure 3: J/Install Installation medias
CD CD
J/Install
1. 2.
Registration Key Customization
Medias Media
3.
Update
Medias
Note: Instead of floppy diskettes you can use CD’s, USB or HDD medias

J/Install Installation Registration Key Media
Registration Key Media

In the Registration Key Media the key file „REG_KEY.INI“ is included. This file
contains the registered products and release versions which are automatically
set with each new order of ProCash/DDC or ProCash/NDC. J/Install verifies the
contents of the file „REG_KEY.INI“ compares it with the contents of the CD and
installs those products only that are defined in this file.
The Registration Key Media is delivered from the factory and it is

strictly prohibited to change it contents. The file „REG_KEY.INI“ will
be created with a generated random security key. Even if anybody
modifies this file after the key generation from factory side, J/Install
cannot install the products any more.
In case of questions or problems related to all Wincor Nixdorf

Software products you should open a ticket via:
https://ebusiness.wincor-nixdorf.com/
OA_HTML/iSupportLogin.jsp
The registration key file "REG_KEY.INI" on the Registration Key Media contains
the product name and major version of the main product you have ordered. All
sub products like, ProTopas Manager, XFSAddOn, PARAC, ..., etc. are defined
in the component file "PRODUCT.INI". This file also is key generated as the
REG_KEY.INI file on the registration key diskette or CD.
You will find the file "PRODUCT.INI" on the J/Install CD in sub folder
"INSTALL\PRODUCTS" separated for each product and release version.
Product Updates via J/Install
Please refer to J/Install User Guide to get detailed information how to update
application software.

J/Install Installation Customizing Media for J/Install
Customizing Media for J/Install

The Customizing Media is used to perform customer specific installations. With
this media the operator can specify the products and update versions and what
parameter settings should be installed.
The Customizing Media will be automatically prepared via the "Installation Disk
Manager". Refer to section ”Creation of Installation Media” on page 45 for
detailed description.
The following table shows the structure of the Customizing Media:
Table 4: Structure of the Customizing Media
File Structure Description

\ BMP\prondc.bmp Customer specific bitmap which is displayed when
or the part ProCash/NDC or ProCash/DDC is
\ BMP\proddc.bmp installed during the J/Install run.
\ VENDORS\ Vendor specific parameters:
WN\XFS30\custom.wn specific parameters for Wincor systems
or
NCR\XFS30\custom.ncr specific parameters for NCR systems
or
DIEBOLD\XFS30\
custom.dib specific parameters for Diebold systems
or
DELARUE\XFS30\
custom.dlr specific parameters for DeLaRue systems
or
GRG\XFS30\
custom.grg specific parameters for GRG systems
or
NAUTILUS\XFS30\
custom.nhy specific parameters for Nautilus Hyosung systems
The vendor specific files are automatically copied
from the vendor specific sub folder to the root
folder of the Customizing Disk.


\ ADDON.PPF\ Specific parameters for AddOn products:
custom.emv ProChip/EMV
custom.ccd ProCashIn/Online with CCDM
custom.crs ProCashIn/Online with CRS
custom.rm2 Recycling Module 2 (PC4000)
custom.chq ProChequeIn
custom.p36 CashIn/Signature
custom.web Web-Extensions
custom.rxe Specific for CRSxe
custom.rkl ProRKL
custom.coi CoinIn
custom.coo CoinOut
custom.snd Specific for SlimCash (obsolete)
custom.flx Parameter settings for ProTopas/Flow-Extensions
custom.rcc Rich Client Manager parameters
custom.fui Flex UI parameters
\ custom.ppf customer parac parameter file - contains basic
parameters that are set during the PARAC run. All
parameters defined in this file must be known by
PARAC. The „PCEDT“ (PARAC PARAMETER
EDITOR) utility should be used to modify the file
custom.ppf.
\ jinstall.cus customizing control file - contains sections of
product names, versions and definitions for update
diskettes. This file is automatically copied from the
vendor specific sub folder from the J/Install CD to
the root folder of the Customizing Disk.
\ dialog.ctl dialog control file - contains the dialog definition of
the installation dialog for the purpose of presetting
parameters during the J/Install run. This file is
automatically copied from the vendor specific sub
folder from the J/Install CD to the root folder of the
Customizing Disk.
\ probase.cus customizing file for ProBase/C - contains
parameters for CSCW32 and XFS services. This
file is automatically copied from the J/Install CD to
the root folder of the Customizing Disk.


\ prosetup.cus customizing file for ProSetup - contains global
parameters and network settings. This file is
automatically copied from the J/Install CD to the
root folder of the Customizing Disk.
\ prosetup.par parameter definition file for ProSetup - contains
some environment variables and the link to the
JInstall.xml script.
\ POST\ Sub folder for UPDATE file(s)
update.zip update file with additional parameter configuration
files (INA files) and batch routines which are called
during the installation process. The update.zip will
be automatically extracted by during the JInstall
installation process.
Note: If you need to add additional customizing,
you can add additional ZIP files to the POST folder.
They will be extracted in alphabetical order.
Please refer to the J/Install reference manual for detailed descriptions

how to create customizing disks.
Enable ProAgent Installation
The installation of ProAgent needs to be manually activated in

JINSTALL.CUS.
Following parameter must be modified in JINSTALL.CUS:
product.PROAGENT.VERSION
Default setting: NONE - ProAgent will not be installed
To enable the ProAgent installation, the parameter value has to be
configured with the two digit minor version of ProAgent as stored on
the product CD.
Example entry in JINSTALL.CUS for ProAgent\R12.60:
product.PROAGENT.VERSION = 60

Rich Client Manager Installation
The Rich Client Manager (RCM) can be used to perform transactions to a PC/E
WEB-Server via SOAP WEB Service communication.
This AddOn Product has to be installed with a separate Registration Key
together with the NDC or DDC core product.
The Rich Client Manager is supported with ProFlex only.
Please refer to ProFlex4 RichClientManager 1.3/20 User Manual for detailed

description.

J/Install Installation Creation of Installation Media
Creation of Installation Media

The Customizing Media has to be created via the "Installation Disk Manager".
The "Installation Disk Manager" automatically assembles all required files from
the product sub folder \PRONDC\R31.20 for ProCash/NDC and
\PRODDC\R31.20 for ProCash/DDC and copies them to the Customizing
Media destination. The destination can be either USB, HDD, or floppy drive. The
"Installation Disk Manager" guarantees that all necessary files are stored on the
right place on the selected destination.
Multi Vendor Installation capability
ProCash/NDC and ProCash/DDC V3.1/20 can also be installed on other

hardware vendors than Wincor Nixdorf.
The Installation of ProCash/NDC and ProCash/DDC is supported on following

hardware vendors:
• Wincor Nixdorf
• NCR
• Diebold
• DeLaRue
• Nautilus Hyosung
• GRG
Installation subfolders of custom/update files
The relevant files for the Customizing Media are stored in sub folder
\INSTALL\PRONDC\R31.20\CUSTOM
or
\INSTALL\PRODDC\R31.20\CUSTOM

The Installation Disk Manager
The Installation Disk Manager (dskmanag.exe) is used to create the

Customizing media for the installation needed by J/Install. Within the main
dialog window you have to select one of the requested hardware vendor
(Wincor Nixdorf, NCR, Diebold, or others), where you want to install the
software. If no removable drives are available you can use the "Browse" button
(see description on the next page) to specify a hard disk or network directory,
where the customizing files and update file are copied to sub folder \CUSTOM
of the folder you have specified via the Installation Disk Manager.
Installation Disk Manager dialog:
Main dialog display after program start:
F1 short help infos

product depended dynamic text.
Program was called from folder
INSTALL\PRONDC\R31.20
Vendor selection
The Installation Disk Manager has to be called directly from the J/Install CD. For
the ProCash/DDC installation you have to start the executable program
"DSKMANAG.EXE" from folder \INSTALL\PRODDC\R31.20. For ProCash/NDC
you have to start it from \INSTALL\PRONDC\R31.20.
See further steps on the next page ...

The "Browse" button:

After pressing the "Browse" button the following dialog appears where you can
specify a hard disk or network directory where the customizing files will be
copied. These folders can be used during installation when J/Install is
requesting the Customizing Media.
If you have selected a floppy drive destination (A:) and you press the "OK"
button after the vendor selection, you will be advised to get an empty formatted
1,44 MB floppy diskette.
If you have inserted the diskette correctly, the required files for the Customizing
Media will be copied from the J/Install CD onto the floppy disk. If the copy
process is completed, you are ready for the product installation with J/Install.

J/Install Installation Installation of Terminal Protection
Installation of Terminal Protection

Since release 2.1/20 ProTect/One is not longer part of the installation CD.
Please refer to the documentation for the Vynamic Security Suite CD how to
install the Vynamic Security Suite components.
Run application as "Non Administrator" user

J/Install automatically installs ProCash/NDC on a specific Windows user and
group that has restricted file and registry access.
The configuration of the application user is configurable in customizing file
JINSTALL.CUS. By default J/Install creates a new group Users00 (if the group
does not exist already ), and a new user OperateSystem. The password for the
user OperateSystem has to be entered during the installation. For unattended
installations the password has to be set encrypted in JINSTALL.CUS.
IMPORTANT NOTE:
For security reasons we strongly advise against using default user
OperateSystem and password for running ProCash/NDC and ProCash/DDC.
Please follow the PCI recommended security rules for user and password
settings.
Please refer to manual J/Install User Guide section

"Operation without administrative rights (PRC section)" to get
detailed information about relevant parameters for non administrator
installations.

Installation Steps Step 1 - Windows Installation
Installation Steps
Wincor Nixdorf hardware systems
On Wincor hardware systems the J/Install installation can be performed as
follows:
Install Windows and additional drivers manually. Install from ProBase/C CD via
call AUTORUN.BAT, but do NOT boot from CD. Install from J/Install CD. See
brief description of Step 1 to Step 3.
Hardware systems of other vendors

If you want to install the application on hardware of other vendors
(NCR, DIEBOLD, DELARUE, NAUTILUS, GRG), it is mandatory to install first
the vendor specific software (exp. Aptra, Agilis, etc.) before you start the
J/Install installation.
Step 1 - Windows Installation
Windows 7 + SP1
If you like to install Microsoft Windows, you have to use the installation CD
provided by Wincor Nixdorf. Please refer to the installation description for
details on how to install Windows. It is highly recommended to install the latest
Microsoft security patches after the Windows installation.
Windows 10
Microsoft Windows 10 is allowed to be installed only on specific embedded PC’s

provided by Wincor Nixdorf.

Installation Steps Step 2 - Communication Installation
Step 2 - Communication Installation

Depending on the requested communication type you have to install the
physical drivers of the communication board and the protocol specific drivers.
Wincor Nixdorf uses communication boards from EICON. Please refer to the
online help on the CD’s and additional handouts for detailed descriptions of the
installation and configuration settings.
For all communication types you need to install:
• WAN Services for Windows (V4R2S1) (CD media)
(This CD installs the physical drivers for the EICON board)
If SNA-SDLC (SNA_LU0) or SNA-QLLC is requested you need in addition:

• SNA Workstation 3.0 (CD media)
For X.25 Native and TCP/IP all drivers are included on the J/Install CD.

Installation Steps Step 3 - J/Install Installation
Step 3 - J/Install Installation

With the J/Install CD you will install all necessary self service products which are
defined on the Customization Disk and Registration Disk.
1. After you have inserted the CD into the CDROM drive, you have to call:
AUTORUN.BAT
2. Please select ProCash/NDC-DDC Applications, Vx.x/xx to install the
requested product. Depending on the used Registration Key it will be
installed either ProCash (NDC or DDC) or ProConsult (NDC or DDC).
Please select one of the offered products. On the bottom a SETUP
button will appear after selection. The installation will be started if you hit
SETUP.

3. After product selection the next J/Install Dialog asks for the
Customizing Disk or Customizing folder:
Note: You have to select the proper CUSTOM folder where your
customizing files are located.

4. This Dialog can be used to set specific device configurations or options

for the line communication during the installation phase. If you already
have set all required values in CUSTOM.PPF, you can ignore this dialog
where you can enable "Configuration is already prepared":
If you select the item “Configuration is already prepared” or after you have
finished specific configurations and you select “All settings done”
("Configuration is already prepared" will be replaced), the J/Install installation is
processing the next dialog window.
This Parameter Configuration Dialog is build via a step table stored in

file DIALOG.CTL located in the customization disk. This step table
can be tested separately with PCDialog. Refer to the J/Install user
manual for detailed descriptions how to create your own installation
dialog.

5. The following dialog is used to enter a password for the application user.
6. When J/Install has finished reading the Customizing Disk or

Customizing folder, the following dialog asks for the Registration Key
Disk(s):
Note: You have to select the proper folder where your Registration Key files
are located.

7. This dialog asks for additional Registration Key Disk(s):
8. If processing of Update disks is specified in JINSTALL.CUS, additional

dialogs can appear with the instruction to insert one or more Update
disks. As another option you can select a sub folder on the hard disk or
another medium where the ZIP compressed data can be located. Make
sure that the ZIP file is stored under sub folder POST of the selected
Update folder. You can have multiple Update disks that you can insert
sequentially after each Update Disk that has been processed. You will be
asked after insertion of each Update Disk if you want to process more
Update Disks. The default configuration in JINSTALL.CUS is Update disk
processing OFF.

9. At least a summary dialog is displayed where it can be verified if the right

product components are selected and valid.
When it is completed successfully, J/Install will pop up the last window to

ask you to restart the Windows system. Click the "Yes" button to confirm
it.

Installation Steps PROEINFO installation log folder
PROEINFO installation log folder

During the J/Install installation process all installation steps are stored in log file
PROEINFO.LOG, error situations are stored in PROEINFO.ERR located in sub
folder C:\PROEINFO. For detailed information about PROEINFO, please refer
to document J/Install User Guide.
If the J/Install installation fails, it is useful to provide the international

support with all files from sub folder C:\PROEINFO in addition to
SUPPORT.ZIP.

Parameter Configuration Dialog Dialog main and sub menus
Parameter Configuration Dialog

As shortly described in the previous section you can set specific parameter
values in the Parameter Configuration Dialog during the J/Install installation.
This chapter describes the main and sub submenus which can be selected
during the installation with J/Install. Refer to Abschnitt ”Parameters in
“CUSTOM.PPF”” on page 59 for detailed parameter descriptions.
Dialog main and sub menus

The main menu has the following menu items:
• Communication
SNA
X.25
TCPIP
Back to Main Menu
• Screen display
• Printers
Journal Printer
Electronic Journal settings
Receipt Printer
Document printer
• Cash Dispenser
• Deposit module
• ProAgent
• Encryption Security
• Configuration already prepared (All settings done)

Parameters in “CUSTOM.PPF”
Parameters in “CUSTOM.PPF”
This chapter describes parameters which are customizable in the Parac
Parameter File (PPF) “CUSTOM.PPF”. Parameters in "CUSTOM.PPF can be
modified with the Parameter Configuration Editor PCEDT.EXE. All parameters
which are not described in this section but exist in "CUSTOM.PPF" should not
be modified or removed.
On the customizing disk, the major CUSTOM.PPF file is located in the root of
the diskette. Vendor specific parameters will be found in the vendor sub folder,
where XFS settings are defined in XFS30 under the "VENDORS" folder.
Parameters that are used by the ADDON products are found in sub folder
"ADDON.PPF". Configuration files in these sub folders do NOT have the file
extension *.PPF.
The parameters of the configuration files, which have another extension than
*.PPF, are added and merged together to one single CUSTOM.PPF file that
finally can be found in folder "C:\INSTALL\CUSTOM" on the harddisk after
installation.

Parameters in “CUSTOM.PPF” [START_APPLICATION]
[START_APPLICATION]
This section describes the parameters which are used to specify the
programs and framework list which are called by the restart manager of
Protopas.
Program list called by the Restart Manager
This parameter specifies the programs and in which order they are loaded.
Each parameter value comma separated is a separate parameter which
contains a programm with execution parameters.
Parameter name: PROGRAMLIST
Section in *.PPF: [START_APPLICATION]
Valid range: Parameter,Parameter,Parameter,...,...,...
Value description: Each Parameter contains a program with execution
parameters which are loaded in the specified order from left
to right.
Default value: “CCBase,WosaCtrl,ApplPM,ProSop,ApplStart”
Enable ProAgent:
“ProViewAgent,CCBase,WosaCtrl,ApplPM,ProSop,ApplStart”

Parameters in “CUSTOM.PPF” [STARTUP]
[STARTUP]
This section describes the parameters which are used to specify the
frameworks path definition for the Repository Manager of Protopas.
See Protopas Programmers Reference manual for detailed descriptions about
Repository- and Restart Manager.
Communication framework
This parameter specifies which communication framework should be started.

Parameter name: COM_FRAME
Section in *.PPF: [STARTUP]
Valid range: character string (path)
Value description: path location
Default value: “C:\PROTOPAS\BIN\dcSimCom.dll” [1]
[1] The default setting is the host simulator framework
Protopas provides following communication frameworks:

• ComSnaSr.dll - SNA Server with EICON Card.
• ComTcpIP.dll - TCP/IP via Ethernet card.
• ComX25Ei.dll - X.25 Native with Eicon card.
Operator panel framework
This parameter specifies the location of the operator panel framework which
has to be started.
Parameter name: OPL_FRAME
Default value: “C:\PROTOPAS\BIN\CCOpl30.DLL”

EPP framework
This parameter specifies the location of the EPP framework which has to be
started. The EPP framework is the direct interface to the encryption services of
WOSA for the EPP or EDM. Refer to section ”Enable Triple DES operation” on
page 338 for detailed description about Triple DES activation.
Parameter name: EPP_FRAME
Default value: “C:\PROTOPAS\BIN\CCEpp30.DLL”

Special Electronics framework
This parameter specifies the location of the Special Electronics framework

which has to be started.
Parameter name: SEL_FRAME
Default value: “C:\PROTOPAS\BIN\CCSel30.DLL”
Cash Dispenser framework
This parameter specifies the location of the Cash Dispenser framework which
has to be started.
Parameter name: CDM_FRAME
Default value: “C:\PROTOPAS\BIN\CCCdm30.DLL;
C:\PROTOPAS\BIN\dcCdmFw.DLL”

Cash Dispenser framework Instance 2
has to be started for Instance 2 which is used for the second tower of the NCR
Dual Tower dispenser.
Parameter name: CDM2_2_FRAME
Default value: “C:\PROTOPAS\BIN\CCCdm30.DLL“
Cash Dispenser framework Instance 3
has to be started for Instance 3 which is used for the Cash Recycle tower of the
NCR Dual Tower dispenser.
Parameter name: CDM3_FRAME
Default value: “C:\PROTOPAS\BIN\CCCdm30.DLL“

Coin Dispenser framework
This parameter specifies the location of the Coin Dispenser framework that has
to be started.
Parameter name: COINOUT_FRAME
Default value: “C:\PROTOPAS\BIN\CCCoinOutFW”
Card Reader framework
This parameter specifies the location of the Card Reader framework which has
to be started.
Parameter name: CARD_FRAME
Default value: “C:\PROTOPAS\BIN\CCCard30.DLL”
Camera framework
This parameter specifies the location of the Camera framework which has to be
started.
Parameter name: CAMERA_FRAME
Default value: “C:\PROTOPAS\BIN\CCCam30.DLL”

Journal framework
This parameter specifies the location of the Journal framework which has to be
started.
Parameter name: JOURNAL_FRAME
Default value: “C:\PROTOPAS\BIN\CCJOUREX.DLL”
Service Handler framework
This parameter specifies the location of the Service Handler framework which
has to be started.
Parameter name: SERVICE_FRAME
Default value: “C:\PROTOPAS\BIN\dcServic.DLL”

Dialog framework
This parameter specifies the location of the Dialog framework which has to be
started.
Parameter name: DLG_FRAME
Default value (NDC):“C:\PROTOPAS\BIN\ndcDiaFw.DLL”
Default value (DDC):“C:\PROTOPAS\BIN\ddcDiaFw.DLL”
Application framework
This parameter specifies the location of the Application framework which has to
be started.
Parameter name: APPLICATION_FRAME
Default value: “C:\PROTOPAS\BIN\dcApplFw.DLL”
Data framework
This parameter specifies the location of the Data framework which has to be
started.
Parameter name: APPL_DATA_FRAME
Default value: “C:\PROTOPAS\BIN\CCDATAFW.DLL”

Variable framework
This parameter specifies the location of the Variable framework which has to be
started.
Parameter name: VARIABLE_FRAME
Default value: “C:\PROTOPAS\BIN\CCVarFw.DLL”
Converter framework
This parameter specifies the location of the Converter framework which has to
be started.
Parameter name: CONVERTER_FRAME
Default value: “C:\PROTOPAS\BIN\dcConvFw.DLL”
Presentation framework
This parameter specifies the location of the Presentation framework which has
to be started.
Parameter name: PRESS_FRAME
Default value: “C:\PROTOPAS\BIN\CCNtPres.DLL”

Protocol framework
This parameter specifies the location of the Protocol framework which has to be
started.
Parameter name: PROT1_FRAME
Default value: “C:\PROTOPAS\BIN\CCProtFw.DLL”
Message Control framework
This parameter specifies the location of the Message Control framework which
has to be started.
Parameter name: MSGCTRL1_FRAME
Default value: “C:\PROTOPAS\BIN\dcMsgCFw.DLL”

Receipt Printer framework
This parameter specifies the location of the Receipt Printer framework which
has to be started.
Parameter name: RECPRT_FRAME
Default value (NDC):“C:\PROTOPAS\BIN\CCPrt30.DLL;
C:\PROTOPAS\BIN\ndcPrtFw.DLL”
Default value (DDC):“C:\PROTOPAS\BIN\CCPrt30.DLL;
C:\PROTOPAS\BIN\ddcPrtFw.DLL”
Journal Printer framework
This parameter specifies the location of the Journal Printer frameworks which
have to be started.
Parameter name: JRNPRT_FRAME
Journal Spooler activation:

To enable the Journal Spooler you have to insert the overlay framework
between the Protopas basic framework and the NDC or DDC specific printer
framework. See example entry for NDC in the following lines:
C:\PROTOPAS\BIN\CCPrt30.DLL;C:\PROTOPAS\BIN\CCJSpool.DLL;

Document Printer framework
This parameter specifies the location of the Document Printer framework which
has to be started.
Parameter name: DOCPRT_FRAME
Device Status framework
This parameter specifies the location of the Device Status framework which has
to be started.
Parameter name: DEVSTA_FRAME
Default value: “C:\PROTOPAS\BIN\dcDevSta.DLL”

Deposit framework
This parameter specifies the location of the Deposit framework which has to be
started.
Parameter name: DEPOSIT_FRAME
Default value: “C:\PROTOPAS\BIN\CCDepo30.DLL”
Transaction framework
This parameter specifies the location of the Transaction framework which has
to be started.
Parameter name: TRANSACT_FRAME
Default value: “C:\PROTOPAS\BIN\dcSttFW.DLL”
Script framework
This parameter specifies the location of the Script framework which has to be
started.
Parameter name: SCRIPT_FRAME
Default value: “C:\PROTOPAS\BIN\CCScript.DLL”

Utility framework
This parameter specifies the location of the ProTopas Utility framework which
has to be started.
Parameter name: UTILFW_FRAME
Default value: “C:\PROTOPAS\BIN\CCUtilFW.DLL”
Security framework
This parameter specifies the location of the Security framework which has to be
started.
Parameter name: SECURE_FRAME
Default value: “C:\PROTOPAS\BIN\CCSecure.DLL;
C:\PROTOPAS\BIN\dcSecure.DLL”
ProCash/XDC-SOP dialog framework
This parameter specifies the location of the SOP dialog framework for
ProTopas/SOP-NDC or ProTopas/SOP-DDC.
Parameter name: CCSOP_DIALOG
Default value: “CCSopDiaJFW@C:\Protopas\java\lib\
JVMPROPERTIES.TXT;C:\ProTopas\bin\ccsopdia.DLL

Barcode Reader framework
This parameter specifies the location of the Barcode Reader framework which
has to be started.
Parameter name: BARCODE_FRAME
Default value: “C:\PROTOPAS\BIN\CCBcr30.DLL"

Parameters in “CUSTOM.PPF”System Restart settings of the Restart Mana
System Restart settings of the Restart Manager
Automatic System shut down & restart
This parameter specifies if the Restart Manager (RM) should initiate an

automatic system reboot if the application has run in a trapp situation. If the
terminal is connected to a ProAgent server this parameter needs to be enabled
if the system should be restarted via the reboot command from the ProAgent
server. If the parameter is zero (disabled), the application is just stopped (killed)
and no automatic reboot takes place.
Parameter name: SHUTDOWN_ACTIVE
Section in *.PPF: [DEFAULT]
Valid range: 0-1
Value description: disables or enables an automatic system restart
Default value: “1" - automatic system restart option enabled
Maximum system reboots
This parameter specifies how many reboots the Restart Manager performs if the
application has run in a trapp situation.
Parameter name: MAXREBOOT
Valid range: 0-99
Value description: specifies the number of reboots the Restart Manager is
allowed to perform
Default value: “3"

Parameters in “CUSTOM.PPF”System Restart settings of the Restart Mana
Power up period timer to clear actual reboot counter
This parameter specifies after what time (in minutes) the number of actual
reboots should be cleared after system has been restarted.
Parameter name: POWER_UP_PERIOD
Valid range: -1; 0-999
Value description: -1 parameter ignored
0 - 999 number of minutes the system must run properly
before the actual reboot counter is set to zero
Default value: “20" - cleares the actual reboot counter if the application
longer than 20 minutes is up.
Configurable screen during system shut down
This parameter can be used to configure a specific bitmap (BMP format) that is
displayed via call of utility "SHOWBMP.EXE" during a system shut down
initiated by the Restart Manager (RM).
Parameter name: SHUTDOWN_EXE
Valid range: C:\PROTOPAS\BIN\SHOWBMP.EXE,path of the bitmap
Value description: program path of SHOWBMP.EXE and path of the bitmap
separated by a comma.
Default value: C:\PROTOPAS\BIN\SHOWBMP.EXE,
C:\PROTOPAS\BITMAPS\DCTMPOOS.BMP

Parameters in “CUSTOM.PPF” [CCPROTFW1]
[CCPROTFW1]
Message Protocol
This parameter defines whether the NCR Direct Connect (NDC) or Diebold
Direct Connect (DDC) message protocol is in use.
Parameter name: PROTOCOL
Section in *.PPF: [CCPROTFW1]
Valid range: NDC, DDC
Value description: NDC - defines the NCR protocol;
DDC - defines the Diebold protocol
Default value: depends on which protocol has to be used
Character Conversion Table location
This parameter specifies the path location of the Character Conversion Table.
The Character Convertion Table handles the ASCII-EBCDIC conversion for
NDC and DDC messages.
Parameter name: CCVTABLE
Valid range: path of character convertion table
Value description: path of char conversion table
Default value: “C:\PROTOPAS\CONF\CCVTABLE.FIL”
Following Character Conversion tables are available:

C:\PROTOPAS\CONF\CCVTABLE.FIL (ASCII-ASCII conversion default table)
C:\PROTOPAS\CONF\CCVTABLE.ASC (ASCII-ASCII conversion table)
C:\PROTOPAS\CONF\CCVTABLE.EBC (ASCII-EBCDICI conversion)

Parameters in “CUSTOM.PPF” [CCPROTFW1]
Messages log file location
This parameter specifies the path location of the Messages log file. All host to
terminal and terminal to host messages will be stored in this file.
Parameter name: LOG_FILE
Valid range: character string
Value description: path of log file
Default value: “C:\PROTOPAS\CCPROT.LOG”
Size of Messages log file
This parameter specifies the size of the Messages log file in KB.
Parameter name: LOG_FILE_SIZE
Valid range: 50-2000
Value description: log file size in kilo bytes
Default value: 200
Append ETX character to the end of a message
This parameter is used to append/remove an ETX (03H) character for each

terminal to host and host to terminal message. Some host environments using
SNA line communication needs an ETX character at the end of the message.
Parameter name: HANDLE_ETX
Valid range: 0, 1
Value description: 0 - do not append/remove ETX
1 - append/remove ETX
Default value: 0

Parameters in “CUSTOM.PPF” Communication
Communication
[SNA]
SNA Communication Framework
This parameter is used to specify the SNA communication framework including

the path location. This setting is stored in the Repository section of the Registry.
Valid range: 256 characters
Value description: specifies the location of the framework for the Repository
manager
Default value: C:\PROTOPAS\BIN\ComSnaSr.dll
Strip Function Management Header (FMH)
This parameter is evaluated for a LU-LU session and can have the values either
YES or NO. If it is YES a Function Management Header (FMH) which is a SNA
specific prefix in a received message is stripped before it is passed to the
communication framework user for further processing. If the value is NO a
received FMH is not stripped.
Parameter name: STRIPFMH
Section in *.PPF: [SNA_PROJECT]
Valid range: NO, YES
Value description: NO - not stripped, YES - Received FMH is stripped
Default value: NO

SNA open timer
This parameter is a duration time in seconds. In case of a LU-LU session the

meaning of this parameter depends on the setting of parameter
SENDINITSELF. If this parameter has the value YES or OTHER, parameter
OPENTIME means the maximum time within the LU-LU session must have
been opened for data exchange after the communication framework Open()
method was called. If INITSELF has the value NO, the parameter OPENTIME
means the maximum time where the SSCP-LU session has to be opened after
the Communication framework Open() method was called. The LU-LU session
for data exchange may be established sometime after termination of the Open()
method in this case. In PU case OPENTIME means the maximum waiting time
where the SSCP-PU session has to be attached from the communication
framework. The attachment succeeds if the SSCP-PU session was established.
If the OPENTIME timer expires without the establishment of the corresponding
SNA session, the Open() method returns with an error.
Parameter name: OPENTIME
Section in *.PPF: [SNA]
Valid range: 0-255
Value description: integer value in seconds
Default value: 60
NAUTYPE
This parameter can have the value either PU for a SSCP-PU session or LU for
a LU-LU session.
Parameter name: NAUTYPE
Valid range: LU, PU
Value description: LU - logical unit, PU - physical unit
Default value: LU

Logical Unit Name
This parameter is only evaluated for a LU-LU session. It is the name of the LU
that is configurated in the IBM CM/2 respectively in the MS SNA Server.
Parameter name: LUNAME
Valid range: char string
Value description: represents the LU name of the SNA Server
Default value: XXXLU
Communication response timer
This is the waiting time in seconds for completion of a send request that is
initiated by the Send() method of the communication framework. For a LU-LU
session a Request Unit (RU) that contains the send data is sent to the PLU in
the SNA host. If this RU requires a SNA acknowledgement (that depends on the
parametrization of the BIND command from the PLU that opened the session),
the PLU sends a SNA response for this RU to the SLU that is used by the
communication framework. In the SSCP-PU session a response is always
required for a RU that is sent from the PU to the SSCP. If sending of the RU and
the optional receiving of a SNA response takes more time then the parameter
value indicates then an error is returned by the Send() method.
Parameter name: RSPTIMER
Valid range: 0-255
Value description: integer value
Default value: 20

Receive buffer size of project
This parameter is used to set the size of the receivebuffer within the SNA
communication framework in bytes. It should not be smaller than the largest
size of a message from the application protocol.
Parameter name: PROJECT_RECEIVE_BUFFER_SIZE
Valid range: 0-4096
Default value: 2048
OPMODE
This parameter can be used to set a symbolic name that is used by the host for
an internal configuration of the SNA connection. If the host does not require this
parameter, its value has to consist of 8 blanks.
Parameter name: OPMODE
Section in *.PPF: [SNA_PROJECT_INITSELF]
Valid range: maximum 8 digit character string
Value description:
Default value: “ ”
Destination Logical Unit Name
This parameter can be used to set a symbolic name of the Destination LU (DLU)
that has to be known on the host side. The DLU name specifies the PLU on the
host side that has to open the LU-LU session after the INITSELF command was
sent. If the host does not require this parameter, its value has to consist of 8
blanks.
Parameter name: DLUNAME
Valid range: 8 digit character string
Value description:

OPUID
This parameter can be used to enter a symbolic name that represents a user
identification of the SLU that sends the INITSELF command. If the host does
not require this parameter, its value has to consist of 8 blanks.
Parameter name: OPUID
Value description:
OPPASS
This parameter can be used to enter a symbolic name that represents the SNA
host password for the SLU that sends the INITSELF command. If the host does
Parameter name: OPPASS
Valid range: 4 digit charcater string
Value description: SNA host password
OPLIB
This parameter can be used to enter a symbolic name that represents user
specific data of the SLU that sends the INITSELF command. The SNA host
passes this data to the PLU that has to open the LU-LU session. If the host does
Parameter name: OPLIB
Value description: user specific data of SLU

[X25]
X.25 Communication Framework
This parameter is used to specify the X.25 communication framework including

the path location. This setting is stored in the Repository section of the Registry.
Value description: specifies the location of the framework
Default value: C:\PROTOPAS\BIN\ComX25Ei.dll
Number of Virtual Circuits
This parameter is used to set the maximum number of simultaneously usable

VC’s. If it is omitted an internal default value of 1 is assumed. This number
should not be larger than the number of VC’s that is configured by the X.25
network for this line.
Parameter name: CONTABSIZE
Section in *.PPF: [X25]
Valid range: 1 - 255
Value description: number of usable VC’s
Default value: 1

Short hold mode time delay
This parameter is used to set a timer value in seconds for those X.25 commu-
nication frameworks that have configured the Short Hold Mode. If a X.25
connection is established by such a communication framework and there was
no data traffic for the duration of this value, the VC is closed internally but the
upper communication layers on both the local and the remote DTE are not
informed about this event. Internally both communication partners change to
listen mode and wait for a connection setup from the other side. If one of the
both has to send something, it leaves its listen state and makes an active call to
reestablish the connection. For the user of the X.25 communication framework,
the connection is in online state the whole time although the VC may be offline
internally after the Short Hold Mode timer had expired. If the value of this
parameter is greater then 999, it is reset to 999.
Parameter name: SHMDELAY
Valid range: 0-999
Value description: integer timer value
Default value: 15
Waiting time for “Call Accept”
This parameter is used to specify the waiting time for the processing of a X.25
CALL ACCEPT packet by the EICON card during the connection setup. If there
was no reaction from the network within this time, an error is reported. The value
can be set from 4 up to 999 seconds.
Parameter name: NETTIME
Value description: integer time value
Default value: 20

Waiting time for “Call Request”
This parameter is used to set the waiting time for processing of a X.25 CALL
REQUEST packet by the EICON card during the connection setup. If there was
no reaction from the network within this time, an error is reported. The value can
be set from 5 up to 180 seconds.
Parameter name: OPENTIME
Default value: 30
Waiting time for “Clear Request”
This parameter is used to set the waiting time for processing of a X.25 CLEAR
REQUEST packet by the EICON card during the connection release. If there
was no reaction from the network within this time, an error is reported. The value
can be set from 5 up to 180 seconds.
Parameter name: CLOSETIME
Default value: 30

Number of calling retries to open X.25 connection
The Open method of the communication framework tries at maximum many

times to open the X.25 connection than the value of CALLRETRY indicates. If
there was no connection established on all tries an error is reported. The value
can be a maximum of 5 times. If the value is greater, it is reset to 5.
Parameter name: CALLRETRY
Valid range: 0-5
Default value: 3
Calling delay timer
This is the waiting time between two connection tries in seconds. The value can
be set up to 300. If the value is greater, it is reset to 300.
Parameter name: CALLDELAY
Valid range: 0-300
Value description: integer time value in seconds
Default value: 20
Receive buffer size
This parameter is used to set the size of the receivebuffer in bytes within the
X.25 communication framework. It should not be smaller then the value of
parameter MAXRECVSIZE.
Parameter name: PROJECT_RECEIVE_BUFFER_SIZE
Section in *.PPF: [X25_PROJECT]
Valid range: 0-2048
Default value: 2048

X.25 connection index
This parameter is used to set the index for the specified X.25 connection. The
index points to an entry in the X.25 connection table that is administrated by the
X.25 support DLL x25corei.dll. This entry contains all necessary administration
data for the specified X.25 connection. The value can be omitted. In this case a
default value of 1 is assumed. 1 is the lowest entry number and there can not
be more entries in the X.25 connection table than the global parameter
CONTABSIZE indicates.
Parameter name: INDEX
Valid range: 0-99
Default value: 0
Type of Virtual Circuit
This parameter can have one of the values 0, 1 or 2. If the value is 0, the
connection is opened actively by sending a X.25 CALL REQUEST packet to the
remote DTE. If the value is 1, the connection is opened passively by changing
to the listen mode and waiting for an INCOMING CALL packet from the remote
DTE. If the value is 2, the connection is used as a PVC (Permanent Virtual
Circuit). Since such a connection is permanent, there is no special need for
opening a connection. Nevertheless a X.25 RESET packet is sent. This packet
reinitialises counters and buffers of the existing VC and indicates to the remote
DTE that the local DTE is operational.
Parameter name: VCTYPE
Valid range: 0-2
Value description: 0 - active SVC, 1 - passive SVC, 2 - PVC
Default value: 0 - active SVC

Suppress TLS trace output
This parameter is used to suppress the TLS trace.

Parameter name: NOTRACE
Valid range: 0, 1
Value description: 0 - trace output is on, 1 - trace output is off
Default value: 0
Buffer size in send direction
This parameter is used to set the internal VC send buffer size in bytes that is
evaluated by the X.25 support DLL x25corei.dll. The value can be up to 4096
bytes large.
Parameter name: MAXSENDSIZE
Valid range: 0-2048
Default value: 2048
Buffer size in receive direction
This parameter is used to set the internal VC receive buffer size in bytes that is
evaluated by the X.25 support DLL x25corei.dll. The value can be up to 4096
bytes large.
Parameter name: MAXRECVSIZE
Valid range: 0-2048
Default value: 2048

Permanent Virtual Circuit (PVC) number
This parameter is used to set the PVC number if a PVC connection is

configured. The number has to concur with the PVC number setting on the
EICON card. The EICON card settings can be viewed with the EICON card
support software.
Parameter name: PVCNO
Valid range: 0-255
Default value: 1
Delivery control for send and receive direction
This parameter can be used to activate a so called Delivery Procedure. If the

X.25 network supports this procedure, every X.25 data packet is acknowledged
by the remote DCE (that is the X.25 network node where the remote DTE is
connected to) instead of the local DCE (that is the X.25 network node where the
local DTE is connected to). This guarantees, that the data was transported
correctly through the X.25 network but not (!) that it was processed correctly by
the remote DTE.
Parameter name: D_BIT_PROC
Valid range: 0, 1
Value description: 0 - no delivery control, 1 - delivery control active
Default value: 0

Activate Short Hold Mode
This parameter is used to activate Short Hold Mode for the local DTE. This
parameter can be used only in SVC connections.
Parameter name: SHMDELAY_FLAG
Valid range: 0, 1
Value description: 0 - no short hold mode, 1 - short hold mode is active
Default value: 0
Short Hold Mode passive configuration
This parameter is used to refine the behaviour of Short Hold Mode. It can take
the value 0, 1 or 2. If the value is 0, every CALL CLEAR packet received from
the EICON card is regarded as a Short Hold Mode CALL CLEAR. The commu-
nication framework changes into the listen mode and waits for an INCOMING
CALL packet from the remote DTE. If the value is 1, during listen mode it is
additionally checked whether the physical connection with the modem is active.
If this connection is lost, an error is reported. If the value is 2 every CALL
CLEAR is regarded as error and is reported to the communication framework
user. This parameter is used only in SVC connections.
Parameter name: SHM_PASSIVE
Valid range: 0-2
Value description: 0 - CALL CLEAR packets are handled as a Short Hold
Mode CALL CLEAR. The communication framework
changes to listen mode and waits for an INCOMING
CALL from the remote DTE.
1 - Check physical line during listen mode.
2 - Every CALL CLEAR is reported as an error to the
communication framework (SVC connections only).
Default value: 1

Start Short Hold Mode passive connection
This parameter is used to set how the SVC or PVC Open() should be returned.
If the value is 0, the Open() method returns immediately. If the value is 1, it
blocks infinitely until the connection is established. For a SVC this means that
an INCOMING CALL packet has arrived and for a PVC, that a RESET packet
has arrived from the remote DTE. If the value is greater then 1 it indicates the
number of seconds the Open() method waits for a connection establishment
Parameter name: PASSIVE_START
Valid range: 0, 1, >1
Default value: 1
Connection reconnect
This parameter can be used to define how the communication framework

behaves if a CALL CLEAR packet is received while data is sent. If the value is
0, an error is returned in the Send() method. If the value is 1, it is tried to
reestablish the VC without error reporting to the communication framework user
by the return code of the Send() method. This parameter is used only in SVC
connections.
Parameter name: SEND_RECONNECT
Valid range: 0, 1
Value description: 0 - reconnect is on, 1 - no reconnect
Default value: 1

Diagnostic code setting for SHM clear cause
This parameter is used to specify a diagnostic code for the SHM clear cause.
The value of this parameter is a four characters long string of hexdigits. The first
two digits from the left are the Cause Code, the last two digits are the Diagnostic
Code that is sent in a CALL CLEAR packet for a Short Hold Mode VC for closing
the line. Usually the user defined Cause Code is set to 80h. This parameter is
used only in SVC connections.
Parameter name: SHMCLRCAUSEDIAG
Valid range: 0000-FFFF
Value description: 4 digit hex value
Default value: 0000
Closed user group selection
This parameter is used to specify a closed user group number. It can have a
value between 0 and 100. If it is between 0 and 99 it indicates the Closed User
Group that the X.25 DTE is assigned to. A Closed User Group is a strictly
isolated subnet from the X.25 net. Only users within the group can communicate
with each other. If the value is 100, no Closed User Group is defined. The
Closed User Group is a X.25 facility that is added to the facility field in the X.25
CALL REQUEST packet to the remote DTE to open the connection. This
parameter is used only in SVC connections.
Parameter name: CUGSELECTION
Valid range: 0-99, 100
Value description: 0 - 99 specifies a closed user group number
100 - no closed user group defined
Default value: 100 - no closed user group defined

Closed user group outgoing call assignment
This parameter is used to specify a Closed User Group with Outgoing Call that
X.25 DTE is assigned to. The parameter can have a value between 0 and 100.
If it is between 0 and 99 it indicates the Closed User Group with Outgoing Call
that X.25 DTE is assigned to. A Closed User Group with Outgoing Call is a
restricted subnet of a X.25 net. Users within the group can communicate with
each other and can connect to addresses outside of this group. It is not possible
to connect to a member of this group from outside of the group. If the value is
100, no Closed User Group with Outgoing Call is defined. The Closed User
Group with Outgoing Call is a X.25 facility that is added to the facility field in the
X.25 CALL REQUEST packet that is sent from the communication framework
to the remote DTE to open the connection. This parameter is used only in SVC
connections.
Parameter name: CUGOUTSELECT
Valid range: 0 - 99, 100
Value description: 0 - 99 specifies the closed user group number
100 - no closed user group defined
Default value: 100 - no closed user group defined
Add Reversed Charging Facility to “Call Request” packets
This parameter is used to add reversed charging facilities for SVC active
connections. The value be 0 or 1. If it is 1 the Reversed Charging Facility is
added to the facility field of a X.25 CALL REQUEST packet that is sent from the
communication framework to open the connection. The communication costs
are burdened to the communication partner, if it accepts this facility. This
parameter is used only in SVC connections.
Parameter name: REVERSECHRG_ACT
Valid range: 0, 1
Value description: 0 - no facilities, 1 - add facilities
Default value: 0 - no facilities

Accept Reversed Charging Facility of incoming calls
This parameter is used to add reversed charging facilities for SVC active
connections. The value can be 0 or 1. If it is 1 the Reversed Charging Facility is
accepted if it is set in the reversed charging facility field of a X.25 INCOMING
CALL packet that was received from the remote DTE to open the connection.
The communication costs are burdened to the local DTE account in this case.
The parameter is used only in SVC connections.
Parameter name: REVERSECHRG_PAS
Valid range: 0, 1
Value description: 0 - accept reversed charging facility
1 - ignore reversed charging facility
Default value: 0 - ignore reversed charging facility
Add Call User Data to “Call Request” packets
The parameter is used to add Call User Data in call request packets. The value
of this parameter is a string of maximum 16 two-figured hexadecimal numbers
separated by blanks. The data of this string defines the Call User Data to be
added to a X.25 CALL REQUEST packet that is sent to the remote DTE. This
parameter is used only in SVC connections. If no call user data is used, the
value of this parameter is an empty string.
Parameter name: CALLUSERDATA_A
Valid range: 00 00 00 00 - FF FF FF FF
Value description: call user data in hex notation
Default value: 00 00 00 00 - no user data

Check Call User Data of incoming calls
This parameter is used to define call user data to be checked for incoming calls.
The value of this parameter is a string of maximum 16 two-figured hexadecimal
numbers separated by blanks. The data of this string defines the Call User Data
which are checked against the Call User Data in a X.25 INCOMING CALL
packet that was received from the remote DTE. The VC is established only if the
incoming Call User Data is equal to the parameter value. This parameter is used
only in SVC connections. If no call user data is used, the value of this parameter
is an empty string.
Parameter name: CALLUSERDATA_P
Valid range: 00 00 00 00 - FF FF FF FF
Value description: call user data in hex notation
Default value: 00 00 00 00 - no user data
Local station address
This parameter is used to set the X.25 address of the local DTE. It can contain
a maximum of 15 digits and a possible address extension of maximum 40 digits.
This extension has to be separated from the address prefix by a period.
Characters other than digits and the period are ignored. This value is used only
for SVC connections.
Parameter name: LOCALADR
Valid range: integer values max. 15 digits, inclusive address extension
40 digits
Value description: local address
Default value: ““

Remote station (host) address
There are a maximum of five alternative X.25 addresses of the remote DTE. An
address not defined is indicated by an empty string for the corresponding
parameter. Each address can contain a maximum of 15 digits and a maximum
possible address extension of 40 digits. This extension has to be separated
from the address prefix by a period. Characters other than digits, the period and
asterisks are ignored. If the connection is opened actively, the remote
addresses are checked in order from REMOTEDAR1 to REMOTEADR5 for a
connection setup. In each probe the remote DTE address is added to the CALL
REQUEST packet that is sent to the remote DTE. If the connection is opened
passively, the remote address in the INCOMING CALL packet is checked
against the alternative addresses in order from REMOTEADR1 to
REMOTEADR5.
Parameter names: REMOTEADRx [1]
Valid range: integer values max. 15 digits, inclusive address extension
40 digits
Value description: local address
[1] ’x’ represents the remote address number from 1 up to 5.

[TCPIP]
TCP/IP Communication Framework
This parameter is used to specify the TCP/IP communication framework

inclusive of the path location.
Value description: specifies the location of the framework
Default value: C:\PROTOPAS\BIN\ComTcpIp.dll
This parameter is used to set the IP address of the remote station that it tries to
connect to.
Parameter names: REMOTEPEER
REMOTEPEER_X[1]
Section in *.PPF: [TCPIP_PROJECT]
Valid range: integer values in format xxx.xxx.xxx
Value description: remote station IP address. If DNS is configured you can
also enter a name instead of the adress number.
[1] - X = placeholder for values in range 1 to 32

TCP port number
This parameter is needed to specify the remote destination TCP port.

Applications above the TCP/IP protocol stack that use TCP communication are
identified by their TCP port. This is a WORD sized number that has to be unique
for every application using the TCP layer. For a successful communication both
client and server have to use the same port number. The port value should be
greater than 1024 because ports below could be reserved for the so-called “well
known ports” that are assigned to specific protocols for applications like telnet,
ftp or smtp.
Parameter name: PORTNUMBER
Valid range: 00000 - 99999
Value description: 5 digit port number
Default value: 99999
Keep Alive mode
This parameter is used to activate keep alive mode. To improve the offline
recognition, so-called KEEPALIVE packets can be exchanged over a TCP
connection. By using KEEPALIVE packets, one communication partner signals
the other that it is still operable. The value of this parameter can be either YES
if the local socket sends KEEPALIVE packets to the remote socket or NO if the
local socket does not send KEEPALIVE messages. This parameter can be
omitted. In this case the default value NO is assumed internally.
Parameter name: KEEPALIVES
Valid range: NO, YES
Value description: NO - keep alive mode off, YES - keep alive mode on
Default value: YES

TCP/IP open timer
This parameter is used to specify how long the Open() method waits for a
successful connect. If there was no connection established within this time, the
Open() method returns with an error code unequal to zero. In the client case the
Open() method implicitly retries to establish the connection as many times as
the value of the parameter CLIENTOPENRETRY indicates. Every try waits at
most OPENTIMEOUT seconds. If no try could open the connection, an error
code unequal to zero is returned.
Parameter name: OPENTIMEOUT
Value description: timer value in seconds
Default value: 20
Connection retries
This parameter specifies the maximum number of times the ATM tries to
connect to the server.
Parameter name: CLIENTOPENRETRY
Value description: number of retries
Default value: 0

Send timeout timer
This parameter sets the maximum waiting time the Send() Method waits for
processing of the send data by the connected socket. If the data was not
processed within this time, a code unequal to zero is returned. This value is
necessary because the stream oriented socket can process send data in
several send calls where in each call only a part of the message is sent.
Parameter name: SENDTIMEOUT
Default value: 20
Close timeout timer
This parameter sets the waiting time in seconds the Open() Method waits for
closing of the TCP/IP connection. If the connection was not closed within this
time, a value unequal to zero is returned. In the client case only the connected
socket is invalidated.
Parameter name: CLOSETIMEOUT
Default value: 20
Local port address configuration
This parameter can be used to specify a specific local port adress used by
TCPIP. If this parameter is set the ATM always is using this local port number.
Parameter name: LOCALPORT
Value description: local port number used by TCPIP
Default value: not set in registry and CUSTOM.PPF

Coding DLL location
This parameter contains the absolute pathname of the DLL that processes the
conversion between the byte stream delivered by the socket and the messages
of the application protocol and vice versa. To identify message boundaries in a
bytestream in most cases it is necessary to enhance the application protocol by
a special intermediate protocol. The DLL identified by this parameter will be
implemented in such a protocol specific enhancement.
Parameter name: CODINGDLL
Value description: absolute path of the com dll
ProCash/NDC-DDC provides following coding DLL’s:

• dcTcp2H.dll - to be used if the TCP/IP stream has a 2 Bytes binary
header to specify the length of the packet excluding the header length.
• dcTcp4A.dll - to be used if the TCP/IP stream has a 4 Bytes ASCII header
to specify the length of the packet excluding the header length.
• dcTcp4AI.dll - to be used if the TCP/IP stream has a 4 Bytes ASCII
header to specify the length of the packet including the header length.
• dcTcp2HI.dll - to be used if the TCP/IP stream has a 2 Bytes binary
header to specify the length of the packet including the header length.
• ccTcpEds.dll - to be used if no header is required in both directions.

Size of memory blocks need to allocate
This parameter gives the size of a memory block that will be allocated within the
Open() method. A pointer to this block is passed as a parameter to every public
function of the DLL that is concerned with the protocol conversion between the
bytestream and application message protocol. Since the memory block is local
to the communication framework, it allows individual message processing, even
if two TCP/IP communication framework objects have been created in the same
address space.
Parameter name: ADMINSIZE
Value description: size of allocated memory blocks
Default value: 8200

TCP/IP parameters used by Windows
The following parameters are needed for the TCP/IP service of Windows. Those
parameters have influence for online and offline recognition and they have to be
set if you need an immediate response (timer controlled) from the TCP/IP
service where the ProCash/NDC or ProCash/DDC application can react on
offline and online situations.
NOTE: The following parameters are NOT included in CUSTOM.PPF.
You have to create a REG file using REGEDIT to add that parameters.
All parameters described in this section are located in the follwing Windows
registry tree:
[HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
KeepAliveTime
Parameter name: KeepAliveTime

Valid range: 00000000-FFFFFFFF in milliseconds (REG_DWORD)
Value description: This parameter controls how often TCP attempts to verify
that an idle connection is still intact by sending a keep alive
packet. If the remote system is still reachable and
functioning, it will acknowledge the keep alive transmission.
Default value: This parameter is not set in the registry by default.
The default value used by Windows is set to:
7200000 (two hours)
TcpKeepTries
Parameter name: TcpKeepTries

Valid range: Number (REG_DWORD)
Value description: Specifies the maximum number of times that TCP/IP will
attempt to deliver keep-alive traffic before marking a
connection as down.
The default value used by Windows is set to 20 tries.

TcpKeepCnt
Parameter name: TcpKeepCnt

Valid range: Number in seconds (REG_DWORD)
Value description: Specifies how often TCP/IP will generate keep-alive traffic.
When TCP/IP determines that no activity has occurred on
the connection within the specified time, it generates
keep-alive traffic to probe the connection.
After trying TcpKeepTries number of times to deliver the
keep-alive traffic without success, it marks the connection
as down.
The default value used by Windows is 20 attempts.
KeepAliveInterval
Parameter name: KeepAliveInterval

Valid range: Number in milliseconds (REG_DWORD)
Value description: This parameter determines the interval separating keep
alive retransmissions until a response is received. Once a
response has been received, the delay until the next keep
alive transmission is again controlled by the value of
KeepAliveTime. The connection will be end after the
number of retransmissions specified by
TcpMaxDataRetransmissions were unanswered.
The default value used by Windows is 1 second.
Please see description for parameter "TcpMaxDataRetransmissions"

on the following page.

TcpMaxDataRetransmissions
Parameter name: TcpMaxDataRetransmissions

Valid range: Number in milliseconds (REG_DWORD)
Value description: This parameter controls the number of times TCP will
retransmit an individual data segment (non connect
segment) before ending the connection. The retransmission
timeout is doubled with each successive retransmission on
a connection. It is reset when responses resume. The base
timeout value is dynamically determined by the measured
round-trip time on the connection.
The default value used by Windows is 5 times.
Example configuration in Windows registry:

[HKEY_LOCAL_MACHINE\
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime"=dword:00003a98
"TcpKeepTries"=dword:0000000a
"TcpKeepCnt"=dword:0000000a
"TcpMaxDataRetransmissions"=dword:0000000a
"KeepAliveInterval"=dword:00003a98
Description:
Parameter "KeepAliveTime" is set to 15000 milliseconds.
Parameter "TcpKeepTries" and "TcpKeepCnt" is set to 10.
Parameter "KeepAliveInterval" is set to 15000 milliseconds.
Parameter "TcpMaxDataRetransmissions" is set to 10.

[SSL_PROJECT]
The following parameters can be set in CUSTOM.PFF under section

[SSL_PROJECT].
For detailed descriptions of SSL configuration and additional parameters which

are not defined via PARAC, refer to manual:
ProTopas Host Protocol and Communication Frameworks Programming Guide
Version 5.0/00
For a Client this parameter is a comma separated list with values, which the
client tries to connect itself to. For a Server it is the address of the client which
tries to connect. If the value is ’*’ any client will be accepted. The values can be
represented as a legal IP address in format d1.d2.d3.d4. D1, d2, d3 and d4 can
be configured from 0 up to 255. An alternative representation of these values is
as a host name. It is passed to the DNS resolution.
Parameter name: REMOTEPEER
Section in *.PPF: [SSL_PROJECT]
Valid range: comma separated list
Value description: ip address or DNS name
Example: "172.18.10.30,172.18.11.11,host.bank.com"

SSL port number
This parameter defines the remote endpoint at host site for the logical
connection. Applications above the TCP/IP protocol stack which use TCP
communication are identified by their ports. For a successful communication
both client and server have to use the same port number.
Parameter name: PORTNUMBER
Valid range: 00000 - 99999
Value description: 5 digit port number
Default value: 99999
SSL Coding DLL location
This is the absolute pathname of the DLL that processes the conversion
between the bytestream delivered by the socket and the messages of the appli-
cation protocol and vice versa. To identify message boundaries in a bytestream
in most cases it is necessary to enhance the application protocol by a special
intermediate protocol. The DLL identified by this parameter will implement such
a protocol. The following chapter describes the DLL in detail.
Parameter name: CODINGDLL
Value description: absolute path of the com dll

SSL Protocols
This optional comma separated parameter specifies the protocol versions in

order to enable them for the use of the connection. The default value is
"Default". If this parameter does not exist or you use the default value, the client
and the host will negotiate a protocol for the connection.
Parameter name: PROTOCOLS
Valid range:
Value description: The following table lists the valid protocol values:
SSLv3 SSL version 3 protocol
TLSv1 TLS version 1 protocol
TLSv1.1 TLS version 1.1 protocol
TLSv1.2 TLS version 1.2 protocol
TCPIP pure TCPIP connection (no encryption!)
Default value: “Default“
It is strongly advised to use at least strong encryption with TLSv1.2 or

higher.
SSL Message length
This parameter gives the size of a memory block which will be allocated within
the Open() method. It is the number of bytes read at once from the TCP input
stream.
Parameter name: MAX_MESSAGE_LENGTH
Valid range:
Value description:
Default value: “8000“

Parameters in “CUSTOM.PPF” [LYNXCI_PARAMETER]
[LYNXCI_PARAMETER]
This section contains the NDC specific optional parameters which are
downloaded from the host with the “Enhanced Customization Table” load
command. Furthermore this section contains parameters where the Logical Unit
Number (LUNO) and the four digit Configuration ID is set.
Optional Parameters (NDC)

These parameters contain NDC specific customization parameters which can
be downloaded from the host through the “Enhanced Customization Table” load
command.
Parameter names: PARAMETER_XX [1]
Section in *.PPF: [LYNXCI_PARAMETER]
Value description: Option Code bits for each Option Number
Default value: see table 5 on the next page.
[1] ’XX’ represents the two digit Option Number in table 5.

Parameters in “CUSTOM.PPF” Optional Parameters (NDC)
Table 5: Optional Parameters (NDC)
Option Option Description

number code
00 Camera Control (not supported)
01 Ready/Supply options
000 No options selected
001 Separate READY (B) status sent in response to Transaction Reply
002 Auto return to previous mode from supply mode
008 12 digit amount buffer
02 002 Auto voice (not supported) default off
03 Date format for supervisor/journal messages
001 MMDD(YY) (default condition)
002 DDMM(YY)
003 (YY)MMDD
004 (YY)DDMM
04 001-040 Roll width (Defines the number of receipt and journal columns used to print
messages from the host. Default for NDC = ’040’ and for DDC = ’099’)
05 001-040 Left print column (Defines the leftmost print column for receipt and journal
messages. Default is ’001’)
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
003 ????
004 ????
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-22 Codes reserved for future use
23 Envelope dispener status option
000 Do not send unsolicited dispenser messages (default condition)
001 Send unsolicited envelope dispenser messages
31 Enable Audio Echo on Keyboard
000 Do not echo the keyboard (default condition)
001 Echo the keyboard, except in PIN states or ’* is pressed

Parameters in “CUSTOM.PPF” Optional Parameters (NDC)

34 Message Coordination Number range
000 31H-3FH (default condition)
001 31H-7EH
50-99 Codes reserved for ATM/E private use

Parameters in “CUSTOM.PPF” Miscellaneous Features I (DDC)
Miscellaneous Features I (DDC)

This parameter contains DDC specific customization options which can be
downloaded from the host through “Write Command III” (Customization Table
load).
Parameter names: PARAMETER_01
Value description: The value of this parameter represents the activated bits of
the Miscellaneous Features I. (See table 6 for available
options).
Default value: 0
Table 6: Miscellaneous Features I (DDC)
BIT Description
128 Append rollover counts
64 Decimal Style
32 Deposit cancel status bit [1]
16 Dollar decimal places
8 Dollar buffer size ( if enabled 12 digits instead of 8 )
4 Fault status bit [1]
2 Automatic return to previous mode
1 Separate ready response
[1] These options are not supported or neccessary to set by ProCash/DDC.

Parameters in “CUSTOM.PPF” Miscellaneous Features II (DDC)
Miscellaneous Features II (DDC)

This parameter contains the second part of DDC specific customization options
which can be downloaded from the host through “Write Command III”.
the Miscellaneous Features II. (See table 7 for available
options).
Default value: 0
Table 7: Miscellaneous Features II (DDC)
BIT Description
128 Reserved
64 Reject Reason codes to network
32 Send MDS status to network
16 Send Maintanance Mode log to network [1]
8 Change MMD mispick timer from 2 minutes to 30 seconds [1]
4 Send Expanded Hardware Configuration status [1]
2 Reserved
1 Reserved
[1] These options are not supported or neccessary to set by ProCash/DDC.

Parameters in “CUSTOM.PPF” Miscellaneous Features III (DDC)
Miscellaneous Features III (DDC)

This parameter contains the third part of DDC specific customization options
which can be downloaded from the host through “Write Command III”.
the Miscellaneous Features II. (See table 8 for available
options).
Default value: 0
Table 8: Miscellaneous Features III (DDC)
BIT Description
128 Reserved [1]
64 Transaction verification status
32 No retract [1]
16 Send all status [1]
8 Message sequence number in solicited status [1]
4 Extended range for message coordination number field [1]
2 Doubling timer 03 feature [1]
1 Double Expanded hardware configuration status [1]
[1] These options are not supported or necessary to set by ProCash/DDC.

Parameters in “CUSTOM.PPF” Logical Unit Number (LUNO)
Logical Unit Number (LUNO)

This parameter contains the three digit Logical Unit Number which is included
in host and terminal messages.
Parameter name: LUNO
Value description: three digit LUNO
Default value: 000
Configuration Identification (Config ID)

This parameter contains the four digit Config ID. Typically the Config ID will be
set through the Config ID load command from the host after a successful
Customization Image (CI) download. At the first connection between the ATM
and the host the Config ID is ’0000’ which indicates an empty configuration. In
general a ’0000’ Config ID forces a CI download from the host.
Parameter name: CONFIG_ID
Value description: four digit Config ID
Default value: 0000 - No CI present

Parameters in “CUSTOM.PPF” [LYNXCI_TIMER]
[LYNXCI_TIMER]
This section contains timer parameters which are downloaded through the
“Configuration Parameters” load or “Enhanced Configuration Parameters” load
command. All settings provided in “CUSTOM.PPF” are default settings. They
can be modified if the values will not be modified via the host download. Timer
values of the "Configuration Parameters" load command are downloaded in
ticks (1 tick = 0,8s). The timer values of the enhanced load are seconds.
ProCash/NDC-DDC stores all timer values as seconds into the registry.
Keyboard response time (Timer 00)
Number of seconds allowed for the client to make a keyboard entry.

Parameter name: TIMER_00
Section in *.PPF: [LYNXCI_TIMER]
Valid range: 0-255
Value description: number of seconds, 0 - infinity
Default value: 30
Additional time (Timer 01)
Number of extra seconds allowed for keyboard input and form or envelope
insertion.
Valid range: 0-255
Value description: number of seconds, 0 - no additional time
Default value: 30

Close state time delay (Timer 02)
Number of seconds the ATM will remain in the close state after the card has
been ejected or if the card cannot be ejected.
Valid range: 0-255
Value description: number of seconds, 0 - no delay
Default value: 5
Communication response time (Timer 03)
Number of seconds allowed for the terminal to receive a transaction reply from
the host.
Valid range: 0-255
Value description: number of seconds, 0 - no time checking
Default value: 60
Envelope insertion time (Timer 04)
Number of seconds allowed for the client to insert an envelope.

Valid range: 0-255
Value description: number of seconds, 0 - infinity
Default value: 50

Cash retract time-out ( Timer 05)
Number of seconds allowed for the client to take the cash before a retract is
attempted.
Valid range: 0-255
Value description: number of seconds
Default value: 60
Poll/select time (Timer 06)
Number of seconds allowed for the terminal to respond to a poll or select

sequence received from the host.
Valid range: 0-255
Value description: not used by ProCash/NDC-DDC
Default value: 60
Take cash time (Timer 07)
Number of seconds allowed for the client to take the cash that has been
dispensed.
Valid range: 0-255
Default value: 1

Card capture time (Timer 09)
Number of seconds allowed for the client to remove a card that has been
ejected. This card will be retained by the ATM when this timer has expired.
Valid range: 0-255
Default value: 40
Additional cash present time (Timer 10)
This indicates the numbers of additional seconds the CSC will wait for the
customer to take the cash.
Valid range: 0-255
Default value: 2
Document/Envelope present timeout (Timer 94)
This timer specifies the time how long the Document/Envelope is presented
before it will be retracted.
Valid range: 0-255
Default value: 30

Statement retract (Timer 95)
This timer determines when to retract a statement that has not been taken by
the cardholder.
Valid range: 0-255
Default value: 30
Statement present (Timer 96)
This timer is started when a statement has been cut and delivered in a “print
statement and set next state” function command. When the timer expires the
next state specified in the transaction reply is entered. The value of ’000’ means
’do not wait’.
Valid range: 0-255
Default value: 1
Vandal guard close (Timer 98)
This timer is started when a card read state is entered. The vandal guard closes
when the timer expires. The value of ’000’ means the vandal guard will remain
permanently open when the terminal goes in service.
Valid range: 0-255
Default value: 10

Vandal guard close time (Timer 99)
Number of seconds the vandal guard remains open after the last customer left
the ATM.
Valid range: 0-255
Value description: number of seconds; 0 - permanently open
Default value: 10
Unsupported timers
The following table lists downloadable timers which are not supported by
ProCash/NDC-DDC:
Table 9: SUnsupported timers by ProCash/NDC-DDC
Timer Description Protocol

06 Communication message timeout (Poll select timeout) NDC/DDC
15 Card Reader enabled timer DDC
18 Swipe or DIP Card Reader error screen timer DDC
22 Not used DDC
23 Dip Card Reader prompt for removal timer DDC
86 Rear Settlement timeout NDC
87 DPM document captured screen timeout NDC
88 Reserved NDC
89 Reserved NDC
90 Reserved NDC
91 EJ inspection timeout NDC
92 SOH/TM-Alert cyclial display timeout NDC
93 SOH/TM-Alert next/previous timeout NDC
97 Door access open timeout NDC

Parameters in “CUSTOM.PPF” [LYNXCI_SCREEN]
[LYNXCI_SCREEN]
Screen default foreground color
This parameter is used to set the default foreground color of the screens to be
displayed. The parameter consists of the three RGB (Red, Green, Blue) compo-
nents used in creating the specified color.
Parameter name: SCREEN_FOREGROUND_COLOR
Section in *.PPF: [LYNXCI_SCREEN]
Valid range: 0-255, 0-255, 0-255
Value description: three integer values which contain the RGB components of
the color.
Default value: 255,255,255
The following table shows the RGB values for the 16 standard colors:
Table 10: RGB values for 16 standard colors
RED GREEN BLUE COLOR

0 0 0 black
0 0 170 dark blue
0 170 0 dark green
0 170 170 dark cyan
170 0 0 dark red
170 0 170 dark magenta
170 85 0 dark yellow
170 170 170 light grey
85 85 85 dark grey
85 85 255 light blue
85 255 85 light green
85 255 255 light cyan
255 85 85 light red
255 85 255 light magenta
255 255 85 light yellow
255 255 255 white

Screen default background color
This parameter is used to set the default background color of the screens to be
displayed. The parameter consists of the three RGB (Red, Green, Blue) compo-
nents used in creating the specified color.
Parameter name: SCREEN_BACKGROUND_COLOR
Valid range: 0-255, 0-255, 0-255
the color.
Default value: 0,0,0
Screen transparent mode
This parameter activates transparent mode for every screen by default. Trans-
parent mode configuration should be used only if all screens are cleared via the
clear screen sequence (FF) before the next screen is displayed. This setting is
useful if you want to display a full screen background picture and you want to
overlay the downloaded text. The downloaded screens should not contain color
sequences if you want to use transparent mode.
Parameter name: SCREEN_TRANSPARENT_MODE
Valid range: 0, 1
Value description: 0 - No, 1- Yes
Default value: 0

Blink rate
This parameter can be used to modify the default blink rate which is used for the
blinking sequence defined in a downloaded screen.
Parameter name: BLINK_RATE
Value description: number of milli seconds
Default value: 1000 - 1 second

Graphic file location
This parameter is needed to specify in which directory the graphic files are
stored on the harddisk. Graphic file types can be BMP, DDU, PCX, ICN or AVI.
Parameter name: PICTURE_XXXX [1]
Value description: path of the graphic file including the file name
Default value: “”
Example: "C:\PROTOPAS\BITMAPS\PICTURE.PCX"
[1] XXXX represents the graphic number which is defined in the downloaded
screen. The number can represent icons, logos, or picture sequences.
The following table describes which kind of picture controls can be

configured via parameter ’PICTURE_XXXX’:
Table 11: Screen parameters reference table
Protocol Description Screen Parameter Name

Sequence
NDC Picture Control \1bP2999\1b\ PICTURE_2999
NDC Logo Control \1bP199\1b\ PICTURE_199
DDC Animation \1bA1002004 PICTURE_100; (101, 102)
DDC Display Icon \1bP9990 PICTURE_999
DDC Select DAC \1bO999 PALETTE_999

Configure MacroMedia Flash Animations
If you want to display Flash animation files, you have to use parameter
"PICTURE_XXXX" to specify the path and additional options of a Flash
animation file. The Flash animation file has to be stored as an executable file.
Parameter name: PICTURE_XXXX [1]
Value description: the parameter value consists of a list of 6 comma separated
parameters:
Position Description
0 path location of the Flash file
1 delay time in milli seconds. Specifies how long the Flash
animation remain displayed after the process has been
terminated. This is useful to prevent screen flickery when after a
Flash movie is following a JPG or BMP picture.
Default if not specified: 0
2 Display priority of the running Flash process. This option can be
used to specify the process priority. If you specify 1, the process
has a lower priority as other processes.
0 - normal
1 - IDLE
2 - HIGH
Default if not specified: 0
3 Specifies the window name (case sensitive) of the Flash movie.
Default if not specified: ShockwaveFlash
4 Display Options (bits):
1 - show Flash in normal mode (no Fullscreen stretch)
2 - display Background screen if configured via parameter
PICTURE_BACKGROUND after Flash is displayed
5 reserved
6 file name of the Flash movie inclusive .EXE extension
Default value: not specified

Example: "C:\PROTOPAS\BITMAPS,650,,,,,010.exe
[1] XXXX represents the graphic number which is defined in the downloaded screen. The number can
represent icons, logos, or picture sequences. See also section ”Graphic file location” on page 126.

Note: If you stop the application without rebooting the system,

you have to kill a running flash movie separately.
Please add following lines in FWKILL.BAT:
c:\protopas\tools\kilflash.exe > c:\protopas\kilflash.bat
call kilflash.bat

Palette file location
This parameter is needed to specify in which directory the palette files are
stored on the harddisk. Palette files are used to set the color table for the
relevant graphic file.
Parameter names: PALETTE_XXX [1] ; PALETTE_DEFAULT [2]
Value description: path of the palette file including the file name
Example: "C:\PROTOPAS\BITMAPS\DAC000.DAT"
[1] XXX represents the palette file number which is appended to the graphic
file name.
[2] PALETTE_DEFAULT can be used to set a basic color palette for all
graphic files if you do not have specific palette files for each graphic.
ProCash/DDC provides following default DAC files:

• DAC000.DAT - contains the default color palette
• DAC001.DAT - contains color black.

Character Width screen global
This parameter can be used to set a basic character width for all screens.
Parameter name: CHARACTER_WIDTH
Valid range: 0 - 99
Value description: number of pixels for one character
Default value: 16
Character Height screen global
This parameter can be used to set a basic character height for all screens.
Parameter name: CHARACTER_HEIGHT
Valid range: 0 - 99
Value description: number of pixels for one character
Default value: 24
Screen horizontal offset
This parameter can be used to set a horizontal offset default setting for all
screens.
Parameter name: HORIZONTAL_OFFSET
Valid range: 0-999
Value description: number of pixels the window is moved down from the top
most position.
Default value: 0

Screen vertical offset
This parameter can be used to set a horizontal offset default setting for all
screens.
Parameter name: VERTICAL_OFFSET
Valid range: 0-999
Value description: number of pixels the window is moved from the left most
position to the right.
Default value: 0
Screen background picture
This parameter can be used to specify a full screen graphic as a background

picture with the mixture of screen contents which is displayed in all screens. If
the background picture is smaller than the screen size, the picture is stretched
to full screen.
Parameter name: PICTURE_BACKGROUND
Valid range: character string (valid path)
Value description: path location of the graphic file
Default value: ""
Example: "C:\PROTOPAS\BITMAPS\EXAMPLE.PCX"

Play videos in full screen mode
This parameter can be used to force playing video files in full screen mode. If
you have enabled this option all video files are stretched to full screen videos.
Parameter name: SCREEN_FULL_SCREEN_VIDEO
Valid range: 0, 1
Value description: 0 - play videos in original size
1 - play videos stretched in full screen mode
Default value: not configured in Registry
ESC substitution character
This parameter can be set if you need the configure a specific substitution
character that is replaced for the ESC (1BH) character in the downloaded
screen data that is downloaded by the host.
Parameter name: ESC_SUB
Valid range: One ASCII character in range (20H-7FH)
Value description: specifies the substitution character
Default value: not configured

Graphic and Video file extension mapping
The following parameters can be used to assign a different file extension for
graphics and video files that are included in screen downloades or for local
configured background pictures. If a file extension is downloaded that is not
supported by ProCash/NDC (e.g. "ESCPEfilepath") or ProCash/DDC (e.g.
"ESCPxxxx" xxxx = picture number) or you like to use a different extension thus
the downloaded one is supported, you have here the possibility to specify a file
extension that replaces the downloaded extension, or the file extension
specified via parameter PICTURE_BACKGROUND or PICTURE_XXXX.
In addition you can specify in the second parameter in which display method,
the file with the specified extension should be displayed.
Parameter names: PICTURE_EXT_ICN PICTURE_EXT_DAT
PICTURE_EXT_PCX PICTURE_EXT_PCC
PICTURE_EXT_DDU PICTURE_EXT_AVI
PICTURE_EXT_MOV PICTURE_EXT_FLC
PICTURE_EXT_FLI PICTURE_EXT_GIF
PICTURE_EXT_TIF PICTURE_EXT_MPEG
PICTURE_EXT_JPG PICTURE_EXT_MPG
PICTURE_EXT_BMP

Parameters: character string (valid file extension),display method
Value description: The first parameter specifies a graphic or video file
extension that should be processed instead of the
extension specified in the host download or specified via
param. PICTURE_BACKGROUND or PICTURE_XXXX.
The second parameter specifies the display method:
0 - use Presentation Framework of Protopas for Bitmaps
1 - use CCMCIPLY.EXE to play Videos repeatedly
3 - use CCMCIPLY.EXE to play Videos once

Example: The following parameter setting assigns a FLC extension to
an AVI extension using display method of CCMCIPLY.EXE
to play videos repeatedly:
PICTURE_EXT_FLC = "AVI,1"

Stop Video after screen delay sequence (NDC only)
This parameter can be used to configure whether videos (AVI’s or MPG’s)

should be terminated after the elapsed delay time specified via a screen delay
control sequence (ESC[dddz) or if the AVi should play further as long as no new
screen is called.
Parameter name: STOP_VIDEO_AFTER_DELAY
Valid range: 0, 1
Value description: 0 - Play AVI infinite
1 - Stop AVI after delay as specified in the screen
Touch zone support in PIN entry dialogs (EPP only)
The following parameter is neccessary to enable touch zone support for the PIN
entry state. If the entered PIN has to be confirmed via a touch key and not via a
Function Display Key (FDK), this parameter has to be enabled otherwise the
presentation framework of Protopas returns with an error if a touch zone has
been touched.
Parameter name: PIN_TOUCH_ENABLE
Valid range: 0, 1
Value description: 0 - No touch zone support in PIN entry states
1 - Enable touch zone support in PIN entry dialogs
On Wincor Nixdorf ATM’s this parameter works only if EPP hardware

is installed or EDS is in use.

Assign "Confirm" FDK in PIN entry dialogs (EDM only)
This parameter is needed if you have to assign the confirmation key in a PIN
entry dialog to an FDK other than A, and the hardware configuration consists of
PINPAD and EDM. In PIN entry dialogs the FDK confirmation key is assigned
to FDK A (defined in CSCW32 PIN Key File (PKF) by default). It is also
neccessary that you assign the new termination key to the new FDK position in
the PKF file.
Parameter name: PIN_CONFIRM_KEY
Valid range: A, B, C, D, F, G, H, I
Value description: specifies the FDK where the confirm key is assigned to.
Configure default Audio path for NDC
This parameter is used to configure the path location of audio (*.WAV) files for
ProCash/NDC. Those wave files are called if digital audio messages are
configured in the screen download (via ESCP0...ESC\) or/and automatic voice
support is enabled in the Enhanced Configuration Parameters Load message.
See ProCash/NDC User Guide for detailed description about voice support and
configuration.
Parameter name: AUDIOX_PATH [1]
Valid range: ASCII string (max. 128 digits)
Value description: full path definition of the wave file.
Default value: not configured in registry
[1] - ’X’ represents the language group number 0-7.

Configure default Audio path for DDC
This parameter is used to configure the path location of audio (*.WAV) files for
ProCash/DDC. Those wave files are called if voice prompting commands are
configured in the screen download (via ESC;...) or/and voice states are
downloaded from host. See ProCash/DDC User Guide for detailed description
about voice support and configuration.
Parameter name: AUDIOXXX_PATH [1]
Valid range: ASCII string (max. 128 digits)
Value description: full path definition of the wave file.
[1] - ’XXX’ represents the language bank number number 000-255.
Configurable substitution character on display
This parameter can be used to exchange the substitution character of customer

input characters in the PIN entry and Information Entry states. By default the
customer input on the screen appears as ’X’ characters in the PIN entry state.
If you like to exchange the ’X’ against a * (star) character, you can specify a star
character in the following parameter.
Parameter name: SUBST_CHAR_SCREEN
Valid range: one character input in range 0x20H - 0x7FH
Value description: specifies the substitution character in PIN entry and
Information Entry states
Default value: not configured in Registry, use ’X’ as substitution character
Example entry: SUBST_CHAR_SCREEN = *

Specific supervisor mode screen
This parameter can be used to specify a specific screen number that should be
displayed during supervisor mode instead of the standard screen 003 (DDC) or
C03 (NDC).
Parameter name: SPECIFIC_SV_MODE_SCREEN
Valid range: 3 or 4 ASCII characters
Value description: specifies the screen number that is displayed instead of
screen 003 or C03.
Note: If you have to emulate a Diebold MDS i series system, you need to
specify value 002.
Configure number of PIN digits
This parameter can be used to define how many PIN digits the consumer has
to enter before the next state can be entered. If the parameter is configured, the
minimum PIN digit definition of the FIT table is ignored.
Parameter name: SCREEN_MIN_PIN_LEN
Valid range: 0-64
Value description: specifies the minimum PIN digits the consumer has to enter
on the PIN pad.

Parameters in “CUSTOM.PPF” [SCREEN_XXX] [1]
[SCREEN_XXX] [1]
[1] ’XXX’ represents the screen number which is downloaded from host.
Foreground Color
This parameter can be used to set a specific foreground color for a downloaded
screen.
Parameter name: FOREGROUND_COLOR
Section in *.PPF: [SCREEN_XXX]
Valid range: 0-255, 0-255, 0-255
the color.
Default value: if the parameter is not set, the values in Registry section
"SCREEN" are used.
Background Color
This parameter can be used to set a specific background color for a downloaded
screen.
Parameter name: BACKGROUND_COLOR
Valid range: 0-255, 0-255, 0-255
the color.
Default value: if the parameter is not set, the values in Registry section
"SCREEN" are used.

Screen idle next screen
This parameter can be used to specify a next screen where it goes to after the
current screen has been displayed. This parameter can be independently set
from the screen download. With this parameter you can insert local screen idle
rotations in combination with, or separately to the screen download. See also
the next parameter for the display time definition of the screen.
Parameter name: IDLE_NEXT_SCREEN
Valid range: -1; 0-999
Value description: -1 - no next screen; next screen number
Default value: -1 - no next screen
Screen idle time
This parameter can be used to specify an idle time how long the current screen
appears before it changes to the next screen which can be specified via
parameter IDLE_NEXT_SCREEN.
Parameter name: IDLE_TIME
Valid range: -1; 0-3600000
Value description: -1 - no time; timer value in milli seconds
Default value: -1 - no time

Character Width screen specific
This parameter can be used to specify a char width for a specific downloaded
screen.
Parameter name: CHARACTER_WIDTH
Valid range: 0-99
Value description: number of pixels in horizontal direction
Default value: If the parameter is not set, the values of Registry section
"SCREEN" are used.
Character Height screen specific
This parameter can be used to specify a char height for a specific downloaded
screen.
Parameter name: CHARACTER_HEIGHT
Valid range: 0-99
Value description: number of pixels in vertical direction
Default value: If the parameter is not set, the values of Registry section
"SCREEN" are used.
Screen contents
This parameter should be set in CUSTOM.PPF only if no screen contents are

downloaded from host. You can use this parameter just in case if you like to
configure a screen locally that is not downloaded from host.
Parameter name: SCREEN_CONTENTS
Valid range: valid ASCII screen sequences (NDC or DDC specific)
Value description: contains screen contents to be displayed
Default value: not set in Registry

Screen horizontal offset
This parameter can be used to set a horizontal offset for a specific downloaded
screen.
Parameter name: HORIZONTAL_OFFSET
Valid range: 0-999
Value description: number of pixels the window is moved down from the top
most position.
Default value: 0
Screen vertical offset
This parameter can be used to set a horizontal offset for a specific downloaded
screen.
Parameter name: VERTICAL_OFFSET
Valid range: 0-999
Value description: number of pixels the window is moved from the left most
position to the right.
Default value: 0

Screen transparent mode
This parameter is used to set transparent mode for a specific downloaded

screen.
Parameter name: TRANSPARENT_MODE
Valid range: 0-1
Value description: 0 - no; 1 - yes
Default value: 0 - no
Screen background picture
This parameter can be used to specify a full screen graphic as a background

picture with the mixture of screen contents of a specific downloaded screen or
as a picture instead of screen contents which are downloaded from host.
Parameter name: PICTURE_BACKGROUND
Valid range: character string (valid path)
Value description: path location of the graphic file
Default value: ""
Example: "C:\PROTOPAS\BITMAPS\EXAMPLE.PCX"

Screen display contents
This parameter is used to switch off displaying the screen contents of a specific
downloaded screen.
Parameter name: DISPLAY_CONTENTS
Valid range: 0-1
Value description: 0 - suppress displaying downloaded screen contents
1 - yes, display contents
Default value: 1 - yes, display contents
Set Curser position for consumer inputs locally
The following parameters are used to set if you need to configure the cursor
position and cursor adjustment of consumer inputs locally. Sometimes it is
neccessary to place the curser exactly to the input field of a background picture.
Often the cursor positioning downloaded from host does not match with the
coordinates of the input rectangle from the background graphic. The following
parameters should solve that problem.
Upper left offset of the input rectangle
Parameter name: INPUT_FIELD_LEFT

Valid range: 0-9999 (pixel)
Value description: Specifies the left offset of the upper left corner of the
input rectangle.
Default value: not used (remarked)

Upper top offset of the input rectangle
Parameter name: INPUT_FIELD_TOP

Value description: Specifies the top offset of the upper left corner of the
input rectangle.
Lower right offset of the input rectangle
Parameter name: INPUT_FIELD_RIGHT

Value description: Specifies the right offset of the lower right corner of the
input rectangle.
Lower bottom offset of the input rectangle
Parameter name: INPUT_FIELD_BOTTOM

Value description: Specifies the bottom offset of the lower right corner of the
input rectangle.

Input adjustment
This parameter controls the character adjustment of the consumer input.

Parameter name: INPUT_FIELD_ADJUST
Valid range: 0, 1, 2
Value description: 0 - character input from left to right
1 - character input from right to left
3 - character input centered, characters are moving to right
and to left
It is very important that for the cursor configuration all five parameters
as described above are set in the [SCREEN_XXX] section.
Configuration Example:
You have set following values:
INPUT_FIELD_LEFT = 0;
INPUT_FIELD_TOP = 24;
INPUT_FIELD_RIGHT = 32;
INPUT_FIELD_BOTTOM = 456;
INPUT_FIELD_ADJUST = 0;
Description: The input rectangle is definded on the left side starting with the first
character at the left border on the second line. The input size is exactly two
characters.
The offset values are dependent from the display resolution and the
font size. If you have a display resolution of 640x480 and your font
has the size and height of 16x24, (value / 16) = 1 character adjust for
parameter xxx_LEFT or xxx_RIGHT, (value / 24) = 1 character adjust
for parameter xxx_TOP or xxx_BOTTOM.

Parameters in “CUSTOM.PPF”Language bank screen parameters (DDC onl
Language bank screen parameters (DDC only)

The following table lists all local parameters that can be used in language
specific screen bank sub sections (BANK_001, BANK_002, etc.). Those screen
sub sections are created if in the screen download the ESCLxxx (set language
bank) sequence is downloaded by the host.
Table 12: Parameters supported in language banks (DDC only)
Parameters Parameters
FOREGROUND_COLOR INPUT_FIELD_RIGHT
BACKGROUND_COLOR INPUT_FIELD_TOP
TRANSPARENT_MODE INPUT_FIELD_BOTTOM
PICTURE_BACKGROUND INPUT_FIELD_ADJUST
CHARACTER_WIDTH PICTURE_BACKGROUND
CHARACTER_HEIGHT PICTURE_XXX
VERTICAL_OFFSET
HORIZONTAL_OFFSET
INPUT_FIELD_LEFT
Example:
If the host downloads screen 011 that contains "ESCL002", the screen contents
are stored in registry section "..\LYNXCI\SCREEN\BANK_002\011".
Parameters needed in language bank sub sections can not be

configured in CUSTOM.PPF used by PARAC.
Please use the way via creating an *.INA file. See also
section “Vendor and AddOn depended configuration” on page 312.

Parameters in “CUSTOM.PPF” [TOP_MSG] and [CUST_MSG]
[TOP_MSG] and [CUST_MSG]
Event and Error message definitions
Parameters of section [TOP_MSG] contain formats, variables and text

messages which are transferred to the destinations defined in parameter
DESTXXXX. Electronic journal files are stored by default in directory
C:\JOURNAL as defined with parameter TOP_JOURNAL_PATH. Electronic
journal files defined in section [CUST_MSG] are stored by default in directory
C:\CUSTOMER as defined with parameter CUST_JOURNAL_PATH. The
advantage of this two parallel journal sections is that you can filter the journal
messages. You can decide which message should be stored to the JOURNAL,
and which message should be stored to the CUSTOMER path.
Parameter name: MSGXXXX [1]
Sections in *.PPF: [TOP_MSG] and [CUST_MSG]
Valid range: ASCII string (max. 128 characters)
Value description: Defines the message string for the journal printer
Default value: see definitions in CUSTOM.PPF
[1] ’XXXX’ represents a fixed four digit definition number which is related to
the error map table (CCErrMap) together with DESTXXXX.

Format Variables
The event and error message text can be prepared with some variables. Here
is a short overview of some variables and their meaning:
Table 13: Variables and formats for event and error messages
Variable Description Output format

@2 prints the current day in two integer digits dd
@3 prints the current month in two integer digits mm
@4 prints the current year in four integer digits yyyy
@5 prints the current time hh:mm:ss
@6 Inserts a three digit security number (000-999) ddd
#NL# macro - initiates a new line
$XXX$ defines a variable name from the variable variable
framework (ccvarfw.dll)
%XXX% defines a variable name from the data variable
dictonary framework (ccdatdic.dll) if it is
loaded via FwLoadPM.exe

Event and Error message destination
This parameter defines the output destinations of the event or error messages.
The destination values can be combinated via enabling the requested bits
(see value description).
Parameter name: DESTXXXX [1]
Section in *.PPF: [TOP_MSG] and [CUST_MSG]
Valid range: 0-39
Value description:
Bit Value Description

0 0 none
1 1 journal file
2 2 journal printer
3 4 journal event with journal data
4 - reserved
5 32 journal events for data monitoring (ProAgent)
Default value: see entries in CUSTOM.PPF

[1] ’XXXX’ represents a fixed four digit definition number which is related to
the error map table (CCERRMAP) together with MSGXXXX.

Parameters in “CUSTOM.PPF” [HARDWARE_CONFIGURATION]
[HARDWARE_CONFIGURATION]
Hardware Configuration Parameters (NDC)
The following table describes the hardware device configuration which is sent
in the NDC solicited status message “Send Configuration Information”.
Table 14: Hardware Configuration Parameters (NDC)
Parameter Description Default Value

HW_CONF_0_PROD_CLASS Product Class 11
HW_CONF_1_NOCONFIG No Configuration 7F
HW_CONF_2_DISK System Disk 00
HW_CONF_3_CARD_READER Card Reader/Writer 03
HW_CONF_4_CASH_HANDLER Cash Handler 01
HW_CONF_5_DEPOSIT Depository 02 [1]
HW_CONF_6_REC_PRINTER Receipt Printer 01 [1]
HW_CONF_7_JRN_PRINTER Journal Printer 01 [1]
HW_CONF_8_RESERVED Reserved 00
HW_CONF_9_RESERVED Reserved 00
HW_CONF_10_NIGHT_DEPOSIT Night Safe Depository 00
HW_CONF_11_ENCRYPTOR Encryptor 01
HW_CONF_12_CAMERA Security Camera 00
HW_CONF_13_DOOR_ACCESS Door Access 00
HW_CONF_14_FLEX_DISK Flex Disk 00
HW_CONF_15_TAMPER_BINS Tamper Indicating Bins 00
HW_CONF_16_CARDHOLDER_KEYB Cardholder Keyboard 00
HW_CONF_17_OPERATOR_KEYB Operator Keyboard 00
HW_CONF_18_DISPLAY_VOICE Cardholder Display/Voice 02
HW_CONF_21_STATEMENT_PRT Statement Printer 7F [1]
HW_CONF_22_SIG_DISPLAY Signage Display ““
HW_CONF_23_RESERVED Reserved ““
HW_CONF_24_COIN_DISP Coin Dispenser ““
HW_CONF_25_SYSTEM_DISPLAY System Display ““
HW_CONF_26_MED_ENT_IND Media Entry Indicators ““

HW_CONF_27_ENV_DISP Envelope Dispenser ““

HW_CONF_28_DOC_PROC_MOD Document Processing Module ““
HW_CONF_29_COIN_TAMP_IND Coin Tamper Indication ““
HW_CONF_30_DOC_TAMP_IND Document Tamper Indication ““
HW_CONF_32_DIG_AUDIO_SERV Digital Audio Service ““
HW_CONF_34_BNA_CASH Bunch Note Acceptor ““
HW_CONF_35_CPM_CHEQUE Cheque Processing Module ““
[1] - Depending on the available hardware, this value will be modified by utility
"SETHWPPF.EXE" during installation.
Unsol./Sol. message logging on journal
This parameter activates NCR compatible logging or DDC MDS status logging
of unsolicited and solicited messages on journal destination.
Parameter name: MESSAGE_LOGGING
Section in *.PPF: [HARDWARE_CONFIGURATION]
Value description: 0 - logging off; 1 - NDC logging on; 2 - DDC logging on
Default value: 0

Expanded Hardware Configuration Parameters (DDC)
The following table describes the hardware device configuration which is sent
in the DDC solicited status message “Send Configuration Information”.
See ProCash/DDC User Guide section “Expanded Hardware Configuration”

and “Double Expanded Hardware Configuration” for detailed description of the
optional bits for each parameter.
Table 15: Hardware Configuration Parameters (DDC)
Parameter Default Parameter Default

Value Value
EXPANDED_HW_CONF_BYTE_0 02 EXPANDED_HW_CONF_BYTE_10 see Note1
EXPANDED_HW_CONF_BYTE_1 00 EXPANDED_HW_CONF_BYTE_11 00
EXPANDED_HW_CONF_BYTE_2 00 [1] EXPANDED_HW_CONF_BYTE_12 00
EXPANDED_HW_CONF_BYTE_6 00 DOUBLE_EXPANDED_HW_CONF_BYTE_16 00
EXPANDED_HW_CONF_BYTE_7 00 [1] DOUBLE_EXPANDED_HW_CONF_BYTE_17 00
EXPANDED_HW_CONF_BYTE_8 00 DOUBLE_EXPANDED_HW_CONF_BYTE_18 00
EXPANDED_HW_CONF_BYTE_9 28
[1] - Depending on the available hardware, this value will be modified by utility
"SETHWPPF.EXE" during installation.
Note1: This field will be filled dynamically by application
Note2: The two digit value represents one Byte where the left digit is the high
part and the right digit the low part. The range of each digit is 30H to
3FH. The value itself has to be entered as an ASCII character value
for the high part and the low part of the byte (see reference table).
HEX Value ASCII char HEX Value ASCII char HEX Value ASCII char
30H 0 36H 6 3CH <
31H 1 37H 7 3DH =
32H 2 38H 8 3EH >
33H 3 39H 9 3FH ?
34H 4 3AH :
35H 5 3BH ;

MACing configuration
Send TVN and MAC in Transaction Request messages
This parameter is used to set if the TVN (Time Variant Number) and MAC have
to be sent in Transation Request messages.
Parameter name: SEND_TVN_MAC
Valid range: 0-1
Value description: 0 - do not send TVN and MAC
1 - TVN and MAC will be sent
Default value: 0 - do not send TVN and MAC
Check TVN and MAC
This parameter is used to set if the TVN (Time Variant Number) and the MAC
have to be checked in Transaction Reply, State table or FIT Load messages.
Parameter name: CHECK_TVN_MAC
Valid range: 0-1
Value description: 0 - do not check TVN and MAC
1 - TVN and MAC will be checked
Default value: 0 - do not check TVN and MAC
Send Machine Number
This parameter is used to set if the Machine Number (Security Terminal

Number) has to be sent in terminal to host messages.
Parameter name: SEND_MACHINE_NO
Valid range: 0-1
Value description: 0 - do not send the Machine number
1 - include the Machine number in the messages
Default value: 0 - do not send the Machine Number

Check Machine Number
This parameter is used to set if the Machine Number (Security Terminal

Number) has to be checked in Transaction Reply messages.
Parameter name: CHECK_MACHINE_NO
Valid range: 0-1
Value description: 0 - do not check the Machine number
1 - check the Machine number
Default value: 0 - do not check the Machine Number
Send TVN and MAC in solicited status
This parameter is used to set if the Time Variant Number and MAC have to be
sent in solicited device status messages.
Parameter name: SEND_TVN_MAC_SOL
Valid range: 0-1
Value description: 0 - do not send TVN and MAC
1 - TVN and MAC will be sent
Default value: 0 - do not send TVN and MAC
Field selected MACing
This parameter is used to activate field selected MACing. The fields to MACed
are defined in the Message Authentication Field Selection Load command.
Parameter name: MAC_FLD_SELECTED
Valid range: 0-1
Value description: 0 - Field selected MACing OFF
1 - Filed selected MACing ON
Default value: 0 - Field selected MACing OFF (DDC)
1 - Field selected MACing ON (NDC)

ASCII MACing activation in EBCDIC line environments
This parameter is used to force MACing calculation in ASCII. This parameter is

only needed if the line communication is EBCDIC and the MAC has to be calcu-
lated in ASCII.
Parameter name: MAC_ASCII
Valid range: 0-1
Value description: 0 - MAC calculation as received from line
1 - MAC calculation always in ASCII
Default value: 0 - MAC calculation as received from line
M-Data and MDS i series status code handling
This parameter is used to specify how the CCERRMAP entries for M_DATA and
DDC_MDS_STATUS have to be modified in the unsolicited or solicited
message by the application at runtime before it be sent to the host. How the
values should be set by the application depends on how the host verifies those
status fields.
Parameter name: STATUS_CODE_HANDLING
Value description: 0 - Status codes entered in CCERRMAP.INA are modified
by the application for solicited and unsolicited messages.
1 - M-Data or MDS i series status codes are replaced
through STCLASS, STCODE, STWARN for solicited or
unsolicited messages. (3 x 4 Bytes = 12 characters)
2 - Status codes entered in CCERRMAP.INA remain
unchanged in solicited and unsolicited messages.
Default value: 0 - Status codes entered in CCERRMAP.INA are modified
by the application for solicited and unsolicited messages.
See also section “Miscellaneous tools” on page 424 utility

MDS2WNC.EXE.

Go offline after host reply timeout
This parameter can be used to set if the terminal should change the ATM mode
to Offline (Communication framework receives offline event), when the host
does not sent the transaction reply message within the time specified by
TIMER_03 (Host Response Timer). This parameter should prevent processing
of host reply commands that are not related to the customer that has initiated
the transaction request.
Parameter name: GO_OFFLINE_AFTER_TIMEOUT
Valid range: 0, 1
Value description: 0 - stay online; 1 - go offline after reply timeout
Default value: 0 - stay online
RKL message encoding
This parameter is used to specify the type of encoding for RKL

(Remote Key Loading) message fields. RKL message fields can be
send/received in hexa decimal, BASE64 or BASE94 encoded format.
Base94 encoding is used automatically if NCR native RKL messages are used.
The parameter specifies how RKL fields have to be handled in receive and send
direction. The format has to be agreed with the switch provider.
Parameter name: RKL_ENCODING
Valid range: 0, 1
Value description: 0 - encoding off, hexa decimal field values
1 - BASE64 encoding enabled
Default value: 0 - encoding off

SAF Machine Number (DDC only)
This parameter needs to be configured with the local machine number if it

should be sent in the SAF response message.
Parameter name: SAF_MACH_NO
Valid range: 6 alpha numeric digits
Value description: valid machine number

Parameters in “CUSTOM.PPF” [APPLICATION_XXX][1]
[APPLICATION_XXX][1]
[1] ’XXX’ represents the protocol type which can be NDC or DDC.
Hardware Fitness Fitness
This parameter can be used to set whether the hardware fitness should be
cleared or remain as before after leaving the SOP session. If you have
ProCash/NDC installed, the Hardware Fitness will allways be cleared if SOP
function "Display Supplies Status" is called.
Parameter name: CLEAR_HWFITNESS
Section in *.PPF: [APPLICATION_XXX]
Valid range: 0-1
Value description: 0 - use current fitness after exiting supervisor mode;
1 - clear fitness after exiting supervisor mode
Default value: 1 - clear fitness after exiting supervisor mode
If the parameter is not set in the Registry, the hardware

fitness is cleared after exiting supervisor mode (like value 1).
Resend Power Up
This parameter is used to set what time cycle the power up message should be
repeated to the host.
Parameter name: RESEND_POWER_UP
Value description: time value in seconds
Default value: 0 - no power up repetition

Suspend Mode timeout
This parameter can be used to set the time in seconds how long the suspend
mode stays active if an error with the suspend mode severity 3 has occurred. If
the parameter is configured with time value zero, the suspend mode option is
switched off.
Parameter name: SUSPEND_TIMEOUT
Value description: time value in seconds. (0 = suspend mode is switched off)
Default value: 30 - suspend mode timeout after 30 seconds
Resend Power up message
This parameter is used to specify in which ATM mode the power up message
should be sent.
Parameter name: SEND_POWER_UP
Valid range: NEVER, ONCE, ALWAYS
Value description: NEVER no power up message.
ONCE send power up message during startup only.
ALWAYS send power up after every online
Default value: ONCE

Sensor messages for terminal doors
This parameter is used to specify for which terminal doors (Cash and Operator
door) an alarm or sensor change message has to be sent. This parameter also
influences the parameter "SVRMODE_WHEN_DOOR_OPEN".
Parameter name: SEND_DOOR_CHANGE
Valid range: GENERAL, SAFE, OPERATOR
Value description: GENERAL - Send door open message if one of the doors
has been opened, and send close message if both doors
are closed.
SAFE - Send open/closed message if safe door has been
opened/closed.
OPERATOR - Send open/closed message if operator door
has been opened/closed.
Default value: GENERAL
Force Supervisor Mode when door open
This parameter can be used to specify if the terminal should go into supervisor
mode after the time specified when the safe or operator door has been opened.
Supervisor mode will be automatically exited (without time delay) when the door
is closed and you have not entered the supervior mode via the SOP menu.
See also section “Sensor messages for terminal doors” on page 160 for door
configuration options.
Parameter name: SVRMODE_WHEN_DOOR_OPEN
Valid range: 0, 999 seconds delay time
Value description: 0 - do not enter SV mode
>0 - enter SV mode after the specified time delay.
Default value: 0 - option disabled

Solicited and Unsolicited message queuing
The parameters in this section are used to configure message queuing for
events within transactions or for during offline which generates a message to
the host. The message will be queued until a transaction has been finished or
the line status changes from offline to online.
The following parameter activates queuing for unsolicited messages within

transactions. If a transaction request message has been sent to the host,
unsolicited messages will be queued until the ready response is sent after the
host reply. Unsolicited sensor messages (doors, cassettes change) or device
fault messages are sent to the host after the transaction ready message.
Parameter name: Q_UNSOL_IN_TRAN_REQ
Valid range: 0, 1
Value description: 0 - message immediately sent to host.
1 - queue message within transactions and send it after
transaction ready.
Default value: 0 - NDC; 1 - DDC
The next parameter activates queuing of solicited messages during offline

mode. Solicited messages unable to be sent to the host during offline mode are
queued until the terminal is again online.
Parameter name: Q_OFFLINE_TRAN_READY
Valid range: 0, 1
Value description: 0 - ignore solicited messages during offline.
1 - queue message during offline and sent it when online.
Default value: 0 - NDC; 1 - DDC

Default Miscellaneous Features (DDC only)
These parameters can be used to set default values for the Miscellaneous
Features 1, 2 and 3. Those default values will be ORed together with the values
of Write Command III (Configuration download). If there is a configuration
download from the host, where the values are less than the default setting, the
bits which are set locally in the default parameters remain active.
Parameter names: DEFAULT_MISC_FEATURE_1
DEFAULT_MISC_FEATURE_2
DEFAULT_MISC_FEATURE_3
Section in *.PPF: [APPLICATION_DDC]

Valid range: 0-255
Value description: see table 6, table 7 and table 8 for detailed value
description.
Switch on/off logo light together with ready indicator
This parameter can be used to set if the logo light should be switched on/off
together with the ready indicator.
Parameter name: SWITCH_LOGO
Valid range: 0, 1
Value description: 0 - switch on/off ready indicator only
1- switch on/off logo light together with the ready indicator
Default value: 0

Ready/Supply/Amount option defaults (NDC)
With this parameter you can switch on bits for the Ready/Supply/Amount Buffer
Options if the Configuration Parameters Load message is downloaded from
host and the bits are switched off. Bits which are set in this parameter will be
AND with the downloaded bits from the host. This could be useful if you want to
set locally required bits which are not downloaded by the network.
Parameter name: DEFAULT_SUPPLY_READY_AMOUNT_OPTIONS
Valid range:
VALUES DESCRIPTION
0 No options selected
1 Separate READY (B) status sent in response to Transaction Reply
2 Auto return to previous mode from supply mode
8 12 digit amount buffer (if not set 8 digit amount buffer)
Value description: The values of each option can be added together if you
want to set more than one option.
Example: Value 3 sets "Separate Ready (B)" and
"Auto return to previos mode from supply mode".
Default value: 0 - No option is set
Refer to ProCash/NDC User Guide for detailed field description of the

Configuration Parameters Load message (13). See also
section ”Optional Parameters (NDC)” on page 110 of this manual.

Card Read/Write error threshold defaults
This parameter can be used to overwrite the threshold values for card read/write
errors from the NDC Enhanced Configuration Parameters load (1A) message.
Parameter name: DEFAULT_CARD_READ_TRESHOLD
DEFAULT_CARD_WRITE_TRESHOLD
Valid range: 0, 99
Value description: Sets the number of allowed read/write errors before
a device error message is sent to the network.
Default values: 10 - for read errors; 3 - for write errors
Refer to ProCash/NDC User Guide for detailed description of

parameter option "13" and "14" in the Enhanced Configuration
Parameters Load (1A) message.
If the card read /write threshold values are not downloaded from the
network, the default values (also valid for ProCash/DDC) can be set
in CUSTOM.PPF exp. thresholds (read) 10, (write) 3:
[LYNXCI_PARAMETER]
PARAMETER_13 = 10
PARAMETER_14 = 3
Enter "Out of service" mode after line reconnect
This parameter can be used to specify if the terminal should enter "Out of
Service" mode after reestablishing the line if the previous mode before offline
was "In Service" mode.
Parameter name: OOS_AFTER_ONLINE
Valid range: 0, 1
Value description: 0 - return to "In Service" mode if previous mode was
"In Service" before offline.
1 - enter "Out of Service" mode after reconnection
Default value: 0

Rear Balancing host timeout
This parameter can be used to specify the time the application waits for the "Go
in Service" command after the Rear Balancing function has been executed and
the terminal has exited supervisor mode. If the terminal does not receive the
"Go in Service" command within the specified time, the rear balancing function
will not performed.
Parameter name: REAR_BALANCE_TIMEOUT
Valid range: 10, 9999
Value description: specifies the time in seconds the application waits for the
"Go in service" command from host.
Default value: 30
Configure Customer Relays 1 - 4
The following parameters are used to configure Customer Relays (1-4) control
of the Special Electronic (SEL) and the Status Indicators of the Operator Panel.
You can configure which status lights should be switched on/off during following
ATM modes or device status:
• ATM is in service mode
• Customer transaction active (card inserted by consumer)
• ATM is in Supervisor Mode
• ATM requires technical service or maintanance
• Low or out status on cash cassettes
• Printer paper low
See detailed description of the parameters on the following pages.

All parameters can be configured in the same parameter syntax as follows:

IndicatorType:Number,IndicatorType:Number,IndicatorType:Number, ...
For the Customer Relays you have to enter keyword REL for IndicatorType.
A positive value in range 1-4 of Number indicates to switch ON the specified
Relay number.
A negative value (preceding minus character) in range 1-4 of Number indicates
to switch OFF (inverted logik) the specified Relay number.
For Status Indicators of the Operator Panel you have to enter OPL for
IndicatorType. Range 0-4 of Number (ON/OFF behaviour see Relay
description) represents the control of the Status Indicators in following order:
OPL Status Indicators Color Number

In Service Indicator green 0
Customer Indicator yellow 1
Cash Indicator yellow 2
Paper Indicator red 3
tech. Service Indicator red 4
EXAMPLE 1:
Assume you like to switch ON the Customer Relay 2 and the Customer Indicator
of the Operator Panel when the ATM mode is in service. In addition you like to
configure to switch OFF the tech. Service Indicator of Operator Panel:
Following parameter setting in CUSTOM.PPF is required:
LED_IN_SERVICE = REL:2,OPL:0,OPL:-4
EXAMPLE 2:
Assume you like to configure Customer Relay 3 and 4 and the tech. Service
Indicator on the Operator Panel when the ATM mode is in Supervisor Mode.
Following parameter setting in CUSTOM.PPF is required:
LED_SVR_MODE = REL:3,REL:4,OPL:4
NOTE: REL configuration requires OPL configuration too.

LED_IN_SERVICE (ATM is in service mode)
Parameter name: LED_IN_SERVICE

Valid range: IndicatorType:Number,IndicatorType:Number, ...
Value description: specifies which Relay Indicator(s) and Operator
Panel Indicator(s) should be switched on/off during in
service mode.
Default value: not configured in registry (internal default handling of
transaction framework is used)
LED_CUSTOMER (transaction active)
Parameter name: LED_CUSTOMER

Panel Indicator(s) should be switched on/off if a consumer
transaction is active.
LED_CASH (cash cassette(s) has/have low or out status)
Parameter name: LED_CASH

Panel Indicator(s) should be switched on/off when the cash
cassette(s) has/have a low or out status.

LED_PAPER (printer paper low)
Parameter name: LED_PAPER

Panel Indicator(s) should be switched on/off if the printers
has/have paper low status.
LED_SERVICE (technical service required)
Parameter name: LED_SERVICE

Panel Indicator(s) should be switched on/off if technical
service or maintanance is required for one or more ATM
devices.
LED_SVR_MODE (ATM in supervisor mode)
Parameter name: LED_SVR_MODE

Panel Indicator(s) should be switched on/off when the ATM
is in supervisor mode

The LED configuration parameters are preset with following defaults if the
parameters are not set in the registry:
Parameter Relay Number

LED_IN_SERVICE OPL 0
LED_CUSTOMER OPL 1
LED_CASH OPL 2
LED_PAPER OPL 3
LED_SERVICE OPL 4
LED_SVR_MODE - -
Configure Remote Sensor Indicators (RSI)
The Remote Sensor Indicators (RSI) consist of three different status lights of
following colors:
GREEN (Relay 3): ATM is In Service and all devices are ok.
YELLOW (Relay 2):ATM is In Service but one or more devices need(s) to

be serviced.
RED (Relay 1): ATM is currently in Supervisor mode or

ATM is in Offline mode or
ATM is Out of Service mode.
On Wincor Systems the RSI status can only be GREEN or YELLOW or RED.
Multiple lights cannot be enabled.
RSI is connected to the Relay output 1-3 of the Special Electronic. The colors
Red, Yellow and Green are assigned to fixed Relay positions, RELAY1 = Red,
RELAY2 = Yellow, RELAY3 = Green. To configure RSI you can use the same
parameters (but with some restrictions), as used to configure Customer Relays
(see also section ”Configure Customer Relays 1 - 4” on page 165).

All parameters can be configured in the same parameter syntax as follows:

IndicatorType:Number,IndicatorType:Number,IndicatorType:Number, ...
For RSI you have to enter keyword REL for IndicatorType.
The value of Number has to be zero which enables the RSI processing.
You have to set Status Indicators of the Operator Panel together with RSI lights.
See section ”Configure Customer Relays 1 - 4” on page 165 for detailed
description about Status Indicator configuration of Operator Panel.
EXAMPLE:
The following parameters in CUSTOM.PPF configure RSI and the belonging
Status Indicators of the Operator Panel.
LED_IN_SERVICE = REL:0,OPL:0
LED_CASH = REL:0,OPL:2
LED_PAPER = REL:0,OPL:3
LED_SERVICE = REL:0,OPL:4
RSI Status GREEN (RELAY3)
Parameter name: LED_IN_SERVICE

Valid range: REL:0,IndicatorType:Number, ...
Value description: enables green RSI for In Service mode and as an option
Operator Panel Indicator(s).

RSI Status YELLOW (RELAY2)
Parameter name: LED_CASH

LED_PAPER
Value description: enables yellow RSI for cash low/out and paper low
status and as an option Operator Panel Indicator(s).
RSI Status RED (RELAY1)
Parameter name: LED_SERVICE

Value description: enables red RSI if the ATM is offline, out of service or in
supervisor mode and as an option Operator Panel
Indicator(s).

Configure Remote Status Monitor (RSM)
On Wincor Nixdorf systems the Remote Status Monitor handling can be enabled
via IndicatorType RSM. As described in section ”Configure Remote Sensor
Indicators (RSI)” on page 169, you can configure multiple parameters and
multiple Indicator Types in a comma separated list.
Example: LED_CASH = RSM,OPL:2
For Multivendor environments on NCR Systems the Indicator Type has to be set
to IndicatorType RSMNCR.
Example: LED_CASH = RSMNCR

LED Mapping for systems of other vendors
The LED control for the Operator Panel (OPL) is slightly different on for
hardware systems other than Wincor Nixdorf. Some LED’s do not exist or the
LED numbers are in a different order. This section describe how the Operator
Panel LED’s can be mapped (as an example) for NCR, Diebold and DeLaRue
systems.
The following table shows the difference of the Operator Panel LED’s between
Wincor Nixdorf and NCR:
Parameter LED Wincor NCR DeLaRue Diebold
No. Nixdorf
LED_IN_SERVICE 0 In Service Supervisor
LED_CUSTOMER 1 Customer Ready
LED_CASH 2 Cash Error
LED_PAPER 3 Paper Not available
LED_SERVICE 4 Service Not available
LED_SVR_MODE - Supervisor - - -
Parameter entries in CUSTOM.PPF for NCR systems:

LED_IN_SERVICE = "OPL:1"
LED_SERVICE = "OPL:2"
LED_SVR_MODE = "OPL:0"

Guide Light flash rate control
This parameter can be optionally used to individually specify the flash intervall
for the guideance light of a device. The flash rate can be configured in multiple
ways as described later on.
Parameter name: GUIDE_FLASH_RATE
Valid range: 1. single value in range of: 0-4
2. comma spearated list of values: 0-4
Value description: The flash rate can be configured in multiple ways:
The 1st way is to specify the flash rate equally for all
devices.
Example 1: GUIDE_FLASH_RATE = "3" specifies quick flash for all devices.
The 2nd way specifies the flash rate individually for a

specific device. The value position in the comma separated
list automatically specifies the device where the flash value
is assigned to.
The positions are assigned to the devices as follows:
0 - Card Reader 1 - Pin Pad
2 - Notes Dispenser 3 - Coin Dispenser
4 - Receipt Printer 5 - Passbook Printer
6 - Deposit Module 7 - Cheque Module[2]
8 - Bill Acceptor[2] 9 - Envelope Dispenser
10 - Document Printer 11 - Coin Acceptor
12 - Scanner Module[2] 13 - Coin Acceptor Reject[1]
14 - Coin Acceptor Out[1]
[1]
-Wincor only
[2]
- Parameter GUIDE_LIGHT_CONTROL needs to be configured.
Refer to CashIn and ChequeIn Inst. & Conf. manuals.
Example 2: GUIDE_FLASH_RATE = "3,0,0,1,0,0,0,0,0,0,0,0,2,0,0"

Configures quick flash for the Card Reader, slow flash for
the Coin Dispenser and medium flash for the Scanner Module.
The flash rate values 0 - 4 are defined are follows:

0 = off; 1 = slow flash; 2 = medium flash; 3 = quick flash; 4 = continueous
Important Note: Please make sure that the guide light control of all other
software layers like XFS or the driver layer underneath are
being switched off to prevent concurrent calls of these
layers.

Offline Reboot timer
This parameter can be used to initiate a system reboot if the ATM mode
changes from online to offline and remain offline longer than the time configured
via this parameter. In addition you can specify the time the ATM is waiting for
line connection after restart before a system reboot is initiated after timer expiry.
This parameter can be useful if host and terminal have reconnect problems in a
non-stable network or because of hardware problems with network cards.
Parameter name: OFFLINE_REBOOT_TIMER
Valid range: -545, 545 minutes (max. 9 hours)
Value description: Positive value: If the ATM has been started and the line
connection is online up to know the ATM mode is triggered.
If the ATM mode changes to offline, the timer is started.
If the ATM remains offline and the timer expires, the reboot
flag is set.
Dependency Restart Manager:
- If parameter SHUTDOWN_ACTIVE is set to "1",
a system reboot takes place.
- If the value is "0" the application will be just killed.
Negative value: Immediately if the ATM has been started,
the connection is checked for online. The timer starts when
the application is in offline mode. If the ATM mode does not
change from offline to online within the specified time, the
reboot flag is set. If ATM gets line connection after
restart. The behavior is the same as described in the
section above (Positive value).
Dependency Restart Manager:
- If parameter SHUTDOWN_ACTIVE is set to "1",
a system reboot takes place. This cycle will be repeated
until we get line connection and number of times
configured in MAXREBOOT.
- If the value of SHUTDOWN_ACTIVE is "0" the application
will be just killed.

Enable double length keys for triple DES
This parameter has to be set if ProCash/NDC or ProCash/DDC has to work with

triple DES keys and has to accept encryption key loads from host that contain
double length keys (48 digits), which are needed to perform triple DES
encryption.
Parameter name: DOUBLE_LENGTH_KEYS
Valid range: 0, 1, 10, 11,12, 20[1]
Value description: 0 - Single DES.
Key load with double length keys is rejected.
Send command reject message to the host.
1 - Key load with double length keys is accepted.
Send ready message to the host.
10, 11, 12 - Key load with double length keys is
accepted (PCI compliant).
Send ready message to the host.
20 - X9 TR-31 key blocks are supported,
normal key load messages are rejected.

[1] - Please refer to document pci-pts-ndc-ddc_v3100.pdf for detailed
descriptions of parameter values 10, 11, 12 and 20.
Zero filled General Purpose Buffer B and C
This parameter can be used to specify if the General Purpose Buffer B and C
should be preset with zeros as it is already done for the Amount Buffer.
This option effects for the Enhanced Amount Entry state for NDC, the Copy
Buffer state and the Enhanced Copy Buffer state for DDC.
Parameter name: ADJ_GEN_BUF_FROM_AMT
Valid range: 0, 1
Value description: 0 - General Purpose buffers are NOT zero filled.
1 - Preset General Purpose buffers with leading zeros.


Configurable cassette names on journal
With the following parameters you can define your own cassette names for the
journal logging when a cassette has been inserted or removed.
You can overwrite following default names:
REJECT CASSETTE
TOP CASSETTE SECOND CASSETTE
THIRD CASSETTE BOTTOM CASSETTE
Configuration Option 1:
Parameter names: JOU_NAME_REJECT
JOU_NAME_CASSx [1]
Valid range: character string (max. 40 characters)
Value description: specifies the cassette names for the reject cassette and for
each single cash out cassette.
[1] - x = physical cassette number beginning with 1 for the first
dispense cassette. The parameters JOU_NAME_CASS1,
JOU_NAME_CASS2, JOU_NAME_CASS3 and
JOU_NAME_CASS4 define the names of 4 cassettes.
Configuration Option 2:
Parameter names: JOU_NAME_REJECT
JOU_NAME_CASSN
Valid range: For parameter JOU_NAME_CASSN you have to include
in addition to a unique cassette name the characters $N$
that are replaced with the physical cassette number.
Range for parameter JOU_NAME_REJECT as defined in
Configuration Option 1.
Value description: specifies the cassette names for the reject cassette and
cash out cassettes.

Configurable text for reject/retract counter on journal
With the following two parameters you can define your own journal text for
number of rejects and retracts for the counter changed messages
"Cash Counters before SOP" and "Cash Counters after SOP".
You can overwrite following default text:
RETRACTS: (represents the retract counter)
REJECTS: (represents the reject counter sum of all dispense cassettes)
Parameter names: JOU_TXT_REJECTS

JOU_TXT_RETRACTS
Value description: specifies the journal text that is logged on journal for the
number of cash retracts and rejects. The counter with the
size of 4 digits for each parameter will be appended to the
new defined text separated with one space to the right.

ADRS options
This parameter can be used to set specific ADRS options to optimize the ADRS
behaviour. By default ProCash/NDC and ProCash/DDC starts the ADRS run
after each consumer transaction. If a consumer inserts his card, the application
waits as long as a previous ADRS run has been finished. In error situations
(cash dispenser time-outs, or shutter jams, dispenser resets, etc.) the waiting
time to finish the ADRS run can cause a long delay time to the next FDK
selection or PIN entry screen for a customer that has already inserted his card.
Parameter names: ADRS_OPTIONS
Valid range: 0 - 15
Value description: 0 - wait until previous ADRS run has been finsihed after a
consumer has inserted a card (can cause a delay during
consumer input)
1 - Do NOT wait for a previous ADRS run. Proceed with the
consumer transaction with the risk that the delay
happens (through a dispenser problem) after the
transaction reply has been received and a dispense
function has been initiated.
2 - Do NOT allow a consumer transaction if after a previous
ADRS run a cash dispenser error has not been repaired.
Display OOS screen in this phase if the dispenser is still
not operational.
Repeat the ADRS run as long as the dispenser is not
repaired. If the dispenser is again operational, stop
ADRS run and allow further consumer transactions.
4 - Run ADRS additionally in Out of Service mode. This
option can be ORed together with one of the other
options.
8 - Run ADRS in OpenCustomerService() to force ADRS
after SOP exit or if the ATM mode changes from offline
to online and previous mode was In Service or the host
sends a Go In Service command. This option can be
ORed together with one of the other options.

ADRS max retries
This parameter can be used to set the maximum repetitions the ADRS should
be repeated.
Parameter name: ADRS_MAX_RETRIES
Value description: 0 - 3 retries during in service mode (1 minute delay).
>0 - number of repetitions the ADRS is repeated until the
device is repaired.
Store downloaded COM key
This parameter is needed if you have to configure whether the downloaded

COM key should be still available after system reboot or if it should be lost after
power failure. The parameter can be used to simulate the behavior of Diebold
systems. They lose the downloaded COM key after power failure.
Parameter name: STORE_COM_KEY
Valid range: 0, 1
Value description: 0 - Downloaded COM key is lost after system reboot.
1 - COM key is stored and available after system reboot.
Default value: not configured - COM key is stored power secure

Force displaying "Card captured" screen in close state
This parameter activates displaying the "Your card has been captured" screen
defined in the Close State (J), if the card was retained by the application (but
retain flag not set in host reply) in case of a jam or a consumer timeout.
Parameter name: CARD_RETAIN_DISPLAY
Valid range: 0-1
Value description: 0 - display also card retain screen if card was already
retained outside the Close State but only if card retain
flag is set in host reply.
1 - display also card retain screen, if card was already
retained outside the Close State but only if the card retain
flag is NOT set in host reply.
Default value: not configured in registry (default = 1)
Print immediate processing options
This parameter can be used to specify in which ATM mode a print immediate
host reply command (FID ’4’) is accepted by the ATM.
Parameter name: PRINT_IMMEDIATE_OPTIONS
Valid range: 0-3
Value description: Bit order
0x01 -Allow print immediate in Supervisor mode
0x02 -Allow print immediate in In Service mode

Configure anti skimming, mouthpiece and alarm sensors
The following parameter is used to configure anti skimming, mouthpiece or/and

alarm sensor recognition. This parameter consists of a comma (,) separated list
for each sensor that you like to define. The single options of each sensor in the
list are grouped through a colon (:), where it can be defined a journal message,
error code, and unsolicited message name.
Parameter name: ALARM_SENSORS
Valid range: SensorValue1:..:..:..:,SensorValue2:..:..:..:,...
Value description: the parameter value consists of one or more Sensor
definitions, where each Sensor definition is separated
through a comma (,). Within each sensor definition, the
mandatory and optional fields are separated through a
colon (:):
POS Optional Description
0 Sensor number that represents the WOSA sensor type:
Value Sensor Type
1 SIU_TAMPER
2 SIU_INTTAMPER
3 SIU_SEISMIC
10 SIU_INPUT1
11 SIU_INPUT2
12 SIU_INPUT3
13 SIU_INPUT4
1 X Device name that represents the device class that will be created in the
Device Status Framework (dcDevsta.dll)
Example: If you enter the name TAMPER_SENSOR, all device state
changes will be assigned to this device name.
The current sensor state can be received in method
PREP_SENSOR_STATUS of the Message Control
Framework (value: 1 = ON (alarm), 0 = OFF).
Set opposite logic:

If you append .1 after the device name the sensor status value is
reported in the opposite way (value: 0 = ON (alarm), 1 = OFF).
Example: TAMPER_SENSOR.1
Sensor State changes from OFF to ON (alarm active) and skimming
device is connected (operational)
2 X 4 digit Journal (TOPMSG/CUSTMSG) message number. If configured
the status change can be journalled to file or/and printer.

3 X 1. Specify StClass/StCodeDevStaDeviceName
This field can be used to set a specific class and error code that can
be set for a specific device name. If DeviceName is not specified,
the device name of parameter position 1 is used.
Example entry 1: 64340050
Example entry 2: 643A0060CCCdmFW
Note: Please make sure that the error section exist in registry
location:
..\Wincor Nixdorf\ProTopas\CurrentVersion\CCERRMAP
2. Specify DevstaDeviceName and Status

The second option how to set this filed is to specify the device name
and the the Status (Severity) that should be set for the current alarm
state. The field consists of 3 dot separated fields. The first field is
reserved and has to contain a bar (’-’), the second field specifies the
device name and the third field specifies the status value.
Example: -.CCCardFW.4
4 X Name of the unsolicited message that should be sent in case if the
sensor status has changed from OFF to ON
Example: T2HUnsolicitedAlarmStateChange
Sensor State changes from OFF to ON (alarm active) and the
skimming device is disconnected or defective
(ASKIM_STATE keyword is set in szExtras of XFS SIU30 service)
the status change can be journalled to file or/and printer.
location:

sensor status has changed from OFF to ON and the skimming device
is disconnected or defective

Sensor State changes from ON to OFF (alarm inactive)

the status change can be journalled to file or/and printer
location:

sensor status has changed from ON to OFF
Default value:not configured in registry
See the following configurations:

Example1:
"1:TAMPER_SENSOR:2000::T2HUnsolicitedAlarmStateChange,
10:INPUT_SENSOR1:2001::T2HUnsolicitedMyOwnDefinedMessage"
This configuration example sets WOSA sensor device SIU_TAMPER, device name TAMPER_SENSOR
for dcDevSta.dll, journal message 2000, no StClass and StCode, and message
T2HUnsolicitedAlarmStateChange if the sensor state changes from OFF to ON (alarm).
The second field (after the comma separator) configures SIU_INPUT1, device name INPUT_SENSOR1
for dcDevsta.dll, journal message 2001, , no StClass and StCode, and message
T2HUnsolicitedMyOwnDefinedMessage if the sensor state changes from OFF to ON (alarm).
Please note that own defined messages have to be configured in registry section
..\CCOPEN\PROTOCOL\NDC\.. or ..\CCOPEN\PROTOCOL\DDC\..
See next examples on the next page ...

Example2:
"1:TAMPER_SENSOR:2000:-.CCCardFW.4:T2HUnsolicitedAlarmStateChange,
10:INPUT_SENSOR1:2001:-.CCCardFW.0:T2HUnsolicitedMyOwnDefinedMessage"
Example3:
"1:TAMPER_SENSOR:2000:64340050:T2HUnsolicitedAlarmStateChange,
10:INPUT_SENSOR1:2001:64340051:T2HUnsolicitedMyOwnDefinedMessage"
Example4:
"1:TAMPER_SENSOR:2000:643A0060CCCdmFW:T2HUnsolicitedAlarmStateChange,
10:INPUT_SENSOR1:2001:643A0061CCCdmFW:T2HUnsolicitedMyOwnDefinedMessage"
Anti Skimming module connection on Wincor ATM’s:

The Anti Skimming module is connected to contact "Reserve In 2" of the special electronic.
For activation of this sensor, following registry parameter settings are required:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\CSC-W32\CurrentVersion\CSCSEL]
"RSRVI2"="ANTI_SKIMMING"
"MAGDOOR3"="ANTI_SKIMMING"
Alternatively: Card reader mouthpiece connection on Wincor ATM’s:
As an alternative solution to the anti skimming module, a specific mouthpiece can be connected to the
"Reserve In 2" contact of the special electronic.
For activation of this sensor, following registry parameter settings are required:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\CSC-W32\CurrentVersion\CSCSEL]
"RSRVI2"="ID_ENTRY"
ProDevice (WOSA) uses sensor type WFS_SIU_TAMPER (1) for status indication.
Please refer to ProBase/C 1.1/30 User Guide "Generation Tools" for detailed information.
Refer also to ProDevice CEN document "Part 10: Sensors and Indicators Unit Device Class Interface" and
"Part4: Identification Card Device Class Interface".
Note: If WOSA parameter "CheckSkimming" is configured in section

HKEY_CLASSES_ROOT\WOSA/ XFS_ROOT\PHYSICAL_SERVICES\SSI
and skimming is active, a running card insert job will be cancelled. The card reader state is set to
not operational and an unsolicited card reader message with a fatal status is sent to the host.
Anti Skimming module defective detection on Wincor ATM’s:

Since release 2.1/10 the ALARM_SENSORS parameter can be configured with POS 8-10. Refer to the table
of the Value description. POS 8-10 can be used if the application should react on disconnect conditions of
the Skimming Module. The disconnect condition will be detected through the next alarm ON event.
This feature is supported for XFS sensor type SIU_TAMPER only.
Dependency on XFS: $MOD$ 110401 5112 PSSIU30.DLL 3.10 or higher

The PSSIU30 service sets keyword ASKIM_STATE with an 8 digit hex value that reflects the status bits of
the skimming interface. Example: ASKIM_STATE = 0x01000051
Example4:
The following just configures the applicationn reactions on disconnect:
"ALARM_SENSORS"="1:MY_SENSOR:::::::2011:64340048.CCCardFW.4:T2HUnsolicitedMySkimming"
Note: For the journal log entry, variable expression $DCVAR_APPL_ASKIM_STATE$ can be used, if the
ASKIM_STATE value should be logged.

Initial Status after application start
The following table describes the "Active" and "Inactive" status that is set as
initial status after application start, depending on how the current status of the
XFS sensor device is set. Depending on the "ALARM_SENSORS" parameter
configuration, an unsolicited alarm message can be sent under following
conditions described in the table.
WOSA XFS WOSA XFS dcDevSta dcDevSta

Sensor Type Status Sensor Status Sensor Status (negative)
SIU_TAMPER ( 1) ON INACTIVE (0) ACTIVE (1)
SIU_INTTAMPER (2) ON INACTIVE (0) ACTIVE (1)
SIU_SEISMIC (3) ON INACTIVE (0) ACTIVE (1)
SIU_INPUT1 (10) OFF INACTIVE (0) ACTIVE (1)
Example1: SIU_INPUT1
ALARM_SENSORS =
"10:INPUT_SENSOR1:2000::T2HUnsolicitedOnMessage:2001::T2HUnsolicitedOffMessage"
Description: In case the SIU_INPUT status has status OFF, the journal message 2001 is generated and
the unsolicited message "T2HUnsolicitedOffMessage" is sent to the host.
If this message contains a device definition of a dcDevSta device, the Sensor Status is
set depending on the configuration in POS 1 of the parameter.
Example2: SIU_TAMPER
ALARM_SENSORS =
"1:INPUT_SENSOR1:2000::T2HUnsolicitedOnMessage:2001::T2HUnsolicitedOffMessage"
Description: In case the SIU_TAMPER status has status ON, the journal message 2000 is generated
and the unsolicited message "T2HUnsolicitedOnMessage" is sent to the host.
If this message contains a device definition of a dcDevSta device, the Sensor Status is
set depending on the configuration in POS 1 of the parameter.
Note: If the negative option is configured, only the sensor status of the
dcDevSta device is changed to the opposite status.

Display receipt delivered screen in close state
With this parameter can be configured which screen should be displayed in the
close state when a receipt was printed or not printed. If the parameter is
enabled, always state index 0 (transaction record form delivered screen) of the
close state (J) is used if the printer has successfully printed and delivered a
receipt. If a receipt was not printed, always state index 2 (no transaction record
form delivered screen) is displayed. If DDC FID ’H’ or ’D’ is used in the host
reply, always state index 2 is used.
Parameter name: RECEIPT_DELIVERED
Valid range: 0, 1
Value description: 0 - use state index 0 if receipt already delivered in the reply
function (form feed (FF) included in printer data).
Use state index 2 if receipt will be deliverd in the close
state.
1 - use state index 0 only if receipt could be printed and
delivered but not if reply DDC FID ’H’ or ’D’ is used in
host reply.
Use Close (J) state Timer 02 always
If this parameter is enabled the close Timer 02 is always used. By default when
the parameter is not set, the close Timer 02 is used only if the next state is a
000 state.
Parameter name: USE_CLOSE_TIMER_ALWAYS
Valid range: 0, 1
Value description: 0 - use close timer only if the next state is a 000 state
specified in the close state (J).
1 - use close timer always
Default value: not configured in registry, default is 0

Delay after Transaction Request processing
This parameter is used to sepecify a delay time how long the application should
wait for the Transaction Reply procesing after the Transaction Request
message has been sent to the host.
Parameter name: TRAN_DELAY_TIME
Valid range: -999-999
Value description: Positive value: delay as long as the Transaction Request
dialog returns, but maximum deleay as specified.
Negative value: delay the specified time in any case
Default value: not configured, default is 0
Screen delay time for FID ’Z’ (DDC only)
This parameter can be used to specify a screen delay time (in seconds) for the
screen that is sent via function identifier ’Z’ (do nothing) of a DDC Function
Command message.
Parameter name: FID_Z_WAIT_TIME
Valid range: 0-5
Value description: the value specifies the time in seconds how long the screen
of FID ’Z’ should be displayed.
Default value: not configured, delay time is 0

Options for PAN handling
This parameter can be used to set special PAN handling that is required in
some project environments.
Parameter name: PAN_HANDLING
Valid range: 0, 1
Value description: 0 - standard PAN handling
1 - specific PAN handling for ANSI PIN block. Use PANLN
and PANDX. Skip field separator und take next PAN
digits up to the number of digits specified by PANLN.
Default value: not configured, use standard PAN handling
Monitor SEL boot switch (Wincor only)
This parameter can be used to disable monitoring of the boot switch

(ON/OFF button) from the operator panel or special electronics panel (the black
boot button of the old special electronic is not involved). That means, if
monitoring is disabled, a button press through an operator has no effect.
Parameter name: MONITOR_BOOT_SWITCH
Valid range: 0, 1
Value description: 0 - disable boot switch monitoring
1 - boot switch monitoring enabled
Default value: not configured, (default = 1)

Monitor Safe door
This parameter can be used to disable safe door monitoring. This parameter is
useful in case the XFS layer returns an undefined door open status because the
physical door sensor connection is missing.
Parameter name: MONITOR_SAFE_DOOR
Valid range: 0, 1
Value description: 0 - disable safe door monitoring
1 - enable safe door monitoring
Reconnection delay time
This parameter can be used to specify the delay time between the connection
attempts when the application tries to establish the line connection in offline
conditions.
Parameter name: RECONNECT_DELAY
Value description: 0 - connection attempts without delay
1 - 9999 delay time between each connection attempt

Power Save Mode delay time
This parameter can be used to specify the delay time when the Power Save
Mode should be activated after a consumer transaction has been finished.
Parameter name: POWER_SAVE_DELAY
Value description: 0 - not configured
1 - 65535 delay time in seconds
Important Note: Power Save Mode is supported only on CMD-V4 with
firmware that supports ECO mode.
NDC LTS Options
This parameter can be used to specify options for the Last Transaction Status
(LTS) of the Transaction Request message.
Parameter name: NDC_LTS_OPTIONS
Valid range: 0, 1
Value description: 0 - not configured
1 - Append always status of five coin out hoppers in LTS
even a coin out module is not configured.
Important Note: This parameter might be required to set if NDC BNA mode
is enabled and BNA LTS is also appended.

Host Protocol (HP) Handling
This parameter is needed to specify how the Application Framework handles

the Start behavior of the Host Protocol Framework. If the Rich Client Manager
(RCM) is in use, this parameter has to be zero and should never be changed or
removed.
Parameter name: HP_HANDLING
Valid range: 0, 1
Value description: 0 - sets HP start behavior for RCM (mandatory for RCM)
1 - Standard behavior for non RCM applications
D91x compatible options parameter
The following parameter can be used to activate specific D91x compatible

handling of states. Please refer to ProCash/DDC V3.1/20 Message Protocol
Extensions for detailed function description.
Parameter name: D91X_OPTIONS
Valid range: 0-3
Value description: 0 - DDC 91X options disabled
1 - Activate D91x compatible state handling for Enhanced
Card Reader State (CRb) and Multi-tasking State (@Xb).
2 - Activate screen blanking feature with reserved screen
943 in Card Read State (A), Enhanced Card Reader
State (CRb) and Multi-tasking State (@Xb).
Default value: 0

Parameters in “CUSTOM.PPF” CAS dialog timer parameters (DDC only)
CAS dialog timer parameters (DDC only)

If the terminal uses Continuous Availability Services (CAS), you have to specify
timeout values for each CAS screen dialog that is displayed when the operator
has selected one of the Continuous Availablity Service. These timeout values
specify how long the CAS specific function selection screen is displayed where
the consumer can select to continue or to abort the transaction if CAS is active.
CAS is supported with ProTopas/SOP-DDC. To use CAS, parameter

SYNCHRONIZE_IMMEDIATE has to be set to "N" in configuration file
CCSOPSTEP.INA. To set the default CAS screens in registry you
have to call the batch routine CAS_SCR.BAT located in
"C:\PROTOPAS\CONF".
Time-out for CAS of cash dispenser
This parameter specifies the timeout value for the screen that is displayed if
CAS for the cash dispenser is active. If the consumer performs a withdrawal
transaction, screen 907 is displayed after the terminal has received the
transaction reply and CAS is active. The consumer has the choice to wait until
CAS is finished or to press CANCEL to abort the transaction. If the consumer
does not press CANCEL and CAS is still active after the timer has expired, the
transaction will be aborted and the terminal responds to the host with a solicited
timeout message. If the consumer press CANCEL, the terminal responds to the
host with a solicited CANCEL message. If CAS will be finished within the time
specified via this parameter, the withdrawal transaction will be processed.
Parameter name: CAS_WAIT_TIME
Section in *.PPF: [CASH_DISPENSER]
Valid range: Tnn, 0, 1-999, ""
Value description: 0 - infinite
1-999 - Number of seconds the screen remain.
Tnn - Use timer value that is downloaded from host.
nn = downloaded timer number stored in
..\LYNXCI\TIMER section.
"" - Timer 04 is used (Diebold compatible)
Default value: not configured - 120 seconds (Diebold compatible)

Time-out for CAS of deposit module
CAS for the deposit module is active. If the consumer performs a deposit
transaction, screen 906 is displayed after the terminal has received the
transaction reply and CAS is active. The consumer has the choice to wait until
CAS is finished or to press CANCEL to abort the transaction. If the consumer
does not press CANCEL and CAS is still active after the timer has expired, the
specified via this parameter, the deposit transaction will be processed.
Section in *.PPF: [DEPOSIT]
Valid range: Tnn, 0, 1-999, ""
Tnn - Use timer value that is downloaded from host.
nn = downloaded timer number stored in
..\LYNXCI\TIMER section.
"" - Timer 04 is used (Diebold compatible)
Default value: not configured - Timer 04 is used (Diebold compatible)

Time-out for CAS of receipt printer
CAS for the receipt printer is active. After the consumer has inserted the card it
will be checked if CAS for the receipt printer is active. If CAS is active, screen
903 is displayed. Within this screen (FDK selection screen) the consumer has
the choice whether to continue or to abort the transaction. If the consumer press
CONTINUE, the transaction will be processed without getting a receipt. If the
consumer press CANCEL or after consumer timeout, the card will be returned
and screen 904 is displayed.
Section in *.PPF: [RECEIPTPRINTER]
Valid range: 0, 1-999
Default value: not configured - infinite

Time-out for CAS of document printer
CAS for the document printer is active. If the consumer performs a
transaction and the transaction reply contains statement print data, screen 906
is displayed if CAS is active. The consumer has the choice to wait until CAS is
finished or to press CANCEL to abort the transaction. If the consumer does not
press CANCEL and CAS is still active after the timer has expired, the
specified via this parameter, statement printer data will be processed as
received in the transaction reply.
Section in *.PPF: [DOCUMENTPRINTER]
Valid range: 0, 1-999
Default value: not configured - infinite

Check CAS of deposit module during dispense
This parameter can be set to inform the consumer that CAS for the deposit
module is active when a withdrawal transaction has been selected by the
consumer. This parameter prevents that dispense operations fail because of an
open safe door while CAS of the deposit module is processed. This parameter
is not needed on terminals which accept dispense operations with an open safe
door.
Parameter name: CAS_WAIT_DEPOSIT
Valid range: 0, 1
Value description: 0 - Do not check CAS for deposit module within a
withdrawal transaction.
1 - Check CAS for deposit module within a
Default value: not configured - Check CAS for deposit module within a

Parameters in “CUSTOM.PPF” [CASH_DISPENSER]
[CASH_DISPENSER]
Number of logical cassettes
This parameter specifies the number of logical cassettes.

Parameter name: NUM_LOG_CASS
Valid range: 0-7 (for NDC); 0-8 (for DDC)
Value description: integer value sets the number of logical cassettes.
Default value: 0
For NDC values above 4 are used only if up to 7 denomination

support is enabled on the host side.
Set cassettes currencies
This parameter sets the currency of the cassettes.

Parameter name: CURRENCY_X [1]
Valid range: 3 digit char string (uppercase)
Value description: represents the cassette currency.
[1] ’X’ represents the logical cassette position from 1 to 7 for NDC and up to 8
for DDC, where 1 - 8 are assigned to denomination ’A’ - ’H’.
For NDC parameters configured above ’X’ > 4 are used only if up to
7 denomination support is enabled on the host side.

Set cassettes values
This parameter sets the bill values of the cassettes.

Parameter name: VALUE_X [1]
Value description: represents the cassette values.
Default value: 0
Default number of notes loaded
This parameter can be used to specify the number of notes loaded count for
each cassettes denomination. This parameter will also be used by SOP function
"STD CASH".
Parameter name: DEFAULT_NUM_NOTES_X [1]
Valid range: 0-9999
Value description: represents the number of notes loaded count.

Automatic cassettes logon
This parameter can be used to configure automatic logon features for cash
cassettes and also for the reject and retract cassette. This allows cassettes
exchange without entering the SOP session. The cassettes are set to
operational automatically after reinsertion. In addition you can specify the
counter behavior of the cassettes. This parameter can also be used to logon
cash in cassettes and retract cassette on CCDM.
Parameter name: AUTO_LOGON_CASSETTES
Valid range: 0 - 31
Value description:
Bit value Description
1 Logon the cassettes if they are inserted and the safe door has
been closed after cassettes insertion
2 Only if parameter AUTO_LOGON_NOTES is non zero:
- Sets the dispensed to customer counter to zero
- Sets the dispensed counter to zero
4 Sets the counter of the reject cassette to zero
8 Sets the counter of the retract cassette to zero
16 Logon cassettes during safe door open. (Dangerous if
cassettes are qickly shuffled; could cause counter mismatch)
Default value: 1 - logon the cassettes
Automatic cassettes logon in SOP session
This parameter activates the automatic logon feature for cash out cassettes and
also for the reject cassette within supervisor mode and without entering the
cassette exchange function. The cassettes will be automatically logged on just
before SOP exit.
Parameter name: AUTO_LOGON_IN_SOP
Valid range: 0, 1
Value description: 0 - logon in SOP off; 1 - logon in SOP on
Default value: 0

Set initial number of notes for auto logon cassettes
This parameter can be used to set initial number of notes for cassettes which
are logged on via the automatic logon feature. This makes the cassettes
immediately operational without entering any counters via the SOP "Set cash
counters" menu.
Parameter name: AUTO_LOGON_NOTES
Value description: initial number of notes for each cassette which is logged on
Default value: 0
The initial configured counter is ignored if the actual counter of the

cassette has a higher value.
This parameter should be used only if the host and operators do not
care about the local calculated cash counters. If a host or other ATM
monitoring programs like ProAgent ask for the local counters they will
get wrong cash counters.

Send cash low message only if whole denomination low
This parameter can be set if the solicited low message should be sent only if the
whole denomination gets low. This is useful if you have configured multiple
cassettes with the same cash type and the solicited low message should be
sent only once for each denomination. If this parameter is not set, the solicited
low message will be sent for each physical cassette.
Parameter name: DENOMINATION_LOW_MSG
Valid range: 0, 1
Value description: 0 - send message for each physical inserted cassette
1 - send low message only if the whole denomination
becomes low [1].
Default value: DDC: 0, NDC: not configured
[1] - If in a DDC environment parameter SEND_CASSETTE_LOW_ALWAYS is not configured, the low
message is sent after each transaction. If you like to send the low message only once, you have to
configure SEND_CASSETTE_LOW_ALWAYS = 0.
Set dispense algorithm (ATM’s only)
This parameter can be used to set how the cassettes should be emptied. You
can specify if the cassettes should be emptied equally or from top to bottom. If
you have for example four cassettes with the same denomination, it might be
useful to set empty cassettes equally, because a cassettes low message is sent
not until the last cassette gets empty. This parameter can also be combined with
parameter "DENOMINATION_LOW_MSG". If the value is zero, the cassettes
low message is immediately sent if the first cassette gets empty. If the value is
one, the low message is sent not until the last cassette gets empty. On Cash
Recycling Systems (CRS) is supported only value "0" (top to bottom algorithm).
Parameter name: DISPENSE_ALGO
Valid range: 0, 1
Value description: 0 - top to bottom algorithm
1 - empty cassettes equally
Default value: 0

Ignore cash counters for removed cassettes
This parameter can be used to configure that the cash counters of removed
cassettes are reported as zero counters to the host. Additionally the counters
are set to zero in the SOP "Display/Print Supply Counters" functions. Also after
cassettes exchange the cassettes counters for removed cassettes are printed
as zero counters on journal after supervisor exit.
Parameter name: CLEAR_MISS_COUNTER
Valid range: 0, 1
Value description: 0 - cash counters remain after cassettes removal
1 - cash counters are set to zero after cassettes removal
Default value: 0
The cash counters for removed cassettes in the SOP functions are
still available !!

Send unsol. Cash low message not only once
This parameter can be used to force sending an unsolicited cash low message
after each consumer transaction if the supply status of one or more cassettes is
low. That is usually used in the NDC environment.
In DDC you can additionally combine bit 0x04 and bit 0x08 if these options are
required by the host. In this case bit 0x01 and bit 0x02 should be switched off.
Parameter name: SEND_CASSETTE_LOW_ALWAYS
Valid range: 0, 1, 2, 4, 8, 12
Value description: 0 - low message is sent only once after supply status
change from "good" to "low".
1- send low message after each transaction only if
current cassettes supply status of a used cassette is
low.
2- send low message after each transaction if one or
more cassettes have low supply status also if a low
cassette is not used in current cash transaction.
4 - send low message only for used cassettes that have
the low status and set the MDS low status bit only for
the used ones (not the accumulated value).
8 - send low message after first consumer transaction if
one or more cassettes have a low status after exit
supervisor mode. In this case the MDS low status
bits are accumulated.
12 - enables above options 4 and 8.
Default value: DDC: not configured

NDC: 1 - send low message after each transaction

Stop dispensing after max. number of present errors
This parameter can be used to specify after how many cash transactions the
application should stop the dispense operation if the application has received
the same error multiple times in the money present operation from the cash
dispenser module. In addition the application is generating a different device
error message for the host where at least the host can decide to not send any
cash out transaction replies any more until the error is fixed (after exit superviser
mode).
Parameter name: MAX_PRESENT_ERRORS
Valid range: 0, 999
Value description: 0 - Counting of money present errors disabled
>0 - After how many times the application should stop the
dispense operation if it has received the same error
in the money present operation of previous cash out
transactions.
Default value: 0 - Counting of money present errors disabled

Set fatal after max. number of failed dispenses
This parameter can be used to specify after how many consecutive dispense
errors the cash dispenser device should be set to severity 4 (fatal).
Parameter name: MAX_DISPENSE_ERRORS
Valid range: 1, 99
Value description: number of dispense errors after the cash dispenser will be
set to fatal (severity 4)
Default value: not configured in registry, internal default is 10

Send sol. message on Cash present time-out (NDC only)
If this parameter is enabled the transaction ready message is sent after the
consumer has successfully taken the money. If the money has not been taken
by the customer during the time-out period, the terminal sends a solicited status
message to the host after the retract operation has been initiated by the
application (only on retract systems if retract operation is enabled).
Parameter name: SEND_SOL_RETRACT
Valid range: 0, 1
Value description: 0 - Send transaction ready immediately when presenting
the cash. Send unsolicited status message after cash
retract if the money was not taken by the consumer
during the time-out period.
1 - Send ready after money has been taken. Send solicited
message after cash present consumer time-out.
Default value: not set in registry
Cash retract through Presenter Dump ’Q’ (DDC only)
This parameter can be set if presented cash should be retracted by the host
through function command ’Q’ and not by the cash terminal if the cash present
timer has expired. If the cash retract time-out timer (Timer 05) has expired, a
solicited message is sent to the host. Then the host can respond with the
Presenter Dump function command ’Q’, which initiates a cash retract operation.
Parameter MAXRETRACT has to be non-zero.
Parameter name: SOLICITED_IF_RETRACT_INHIBIT
Valid range: 0, 1
Value description: 0 - Retract is initiated by the terminal after present timeout.
After retract the terminal generates a solicited message.
1 - Retract is NOT initiated by the terminal, but a solicited
message is sent to the host and the terminal waits for a
new host function command message.

Send missing (’@’) for fatal cassettes (DDC only)
This parameter can be used to set the denomination ID to missing (’@’) in

solicited status messages for those cassettes, which have status fatal. Fatal
conditions can be physically or logically empty, no reference value, note jams,
pick failures or the cassette is not initialized.
This option enabled prevents repeated dispense commands from host for
cassettes, which are reported to the host as a lower case denomination ID
status but the cassette cannot be used anymore because of a fatal status.
In the Diebold protocol the lower case denomination ID ’a’, ’b’, ’c’, ’d’, ’e’, ’f’, ’g’,
or ’h’ can be fatal, empty or low. The disadvantage of this option is, that missing
and fatal cassettes cannot be found out on the host side, because they are
reported as the same status ’@’.
The denomination ID status in the SOP User Exit function display or print
Supply Counters remain unchanged.
Parameter name: FATAL_CASS_AS_MISSING
Valid range: 0, 1
Value description: 0 - Disabled, send lower case denomination ID in solicited
cash dispenser status message for fatal cassettes.
1 - Enabled, send missing denomination ID ’@’ in solicited
cash dispenser status message for fatal cassettes.
Missing status also effects to Hardware Configuration
status and Enhanced Supply Counters status message.
Default value: Disabled, not configured in registry.

Allow dispense if cassettes counter < 0 (NDC only)
This parameter can be used to allow dispense operations for those cassettes,
which have still notes physically available, but the logical counter "number of
notes remaining" in cassette has reached a value below zero. If the counter
"Number of notes remaining" is below zero, the value is set fix to 65535 and
remain unchanged until you have entered SOP to set or add new cash counters
via the SOP function.
Parameter name: DISPENSE_BELOW_ZERO
Valid range: 0, 1
Value description: 0 - Dispense below zero disabled. Do not use any more
those cassettes where the counter "Number of notes
remaining in cassette" has reached zero.
1 - Dispense below zero enabled. Allow dispensing for
those cassettes which have still money available in the
cassette, but cash counter is < 0.
Default value: 0 - Dispense below zero disabled.
Security timer between dispense and presenting money
This parameter can be used to set a time interval that specifies within what time
a present money operation is allowed after a dispense operation. If a present
money operation is not initiated within the specified time, the present money
function returns with "Order not allowed". This option prevents unexpected
money delivery after possible hanging situations or if an outstanding job does
not return.
Parameter name: PRESENT_TIMER
Valid range: 0 - 999 (time in seconds)
Value description: 0 - Money present security timer off
1 - 999 - Money present security time. Sets the time
within what time a present money operation has
to be initiated after a dispense operation.
Default value: not configured, default time used by application is 180 sec.

Logical cassettes mapping for ATM’s with more than 4

cassettes
This parameter is needed to be set if the application has to run on an ATM that
has a dispenser with more than 4 dispense cassettes. If this parameter is
enabled the 4 physical positions are reported from the logical type / denomi-
nation information.
There are two different kinds of reporting the physical ordering supported:
• Logically: The order of reporting the positions is taken from cassette config-
uration in ..\LYNXPAR\CASH_DISPENSER. The available cassettes, which
will be assigned to a logical type are searched from top to bottom. Physical
cassettes that are not configured as a logical type are skipped. Only the first
4 physical cassette types (top to bottom search) that match with the
configured logical types are taken. Remaining physical cassettes are
ignored. The 912 cassette specific dispense error code will be calculated in
logical order.
• Physically: The order of reporting keeps the physically inserted order, but the
information is compressed for identical logical cassettes as above. This is
mainly relevant for ProCash/DDC.
As an example assume the following 6 cassettes (DDC denominations) are
inserted: CBBADD
Logical ordering would result in reporting positions ABCD
Physical ordering would result in reporting positions CBAD
Parameter name:LOGICAL_MAPPING
Valid range: 0, 1, 2, 3
Value description: 0 - Automatic logical mapping on recycler
Off if at most 4 cassettes are found
On if more than 4 cassettes are found (logical ordering)
1 - Logical mapping on with logical ordering
2 - Logical mapping forced off
Only the first four physical cassettes will be reported
Can lead to major issues with more than 4 cassettes!
3 - Logical mapping on with physical ordering
Default value: not configured - Automatic (0)

ProCash/DDC
If this parameter is enabled, following standard protocol characteristics of
ProCash/DDC are changed:
• Cassettes (physical cassette positions) in sol./unsol. cash dispenser device
fault messages are reported from the logical denomination information.
This also applies to the Hardware Configuration message and (Enhanced)
Supply Counter messages.
ProCash/NDC
For ProCash/NDC following characteristics are changed:
• TI Sensor messages of the cassettes are reported logically and NOT as
physically inserted. If multiple physical cassette types are assigned to one
logical type, the sensor status changes only from IN to OUT if all physical
cassettes of the same type are removed.

Check cash dispenser shutter status after money taken
This parameter can be used to specify whether the shutter status of the cash
dispenser should be checked or not after the money has been taken by the
consumer.
Parameter name: CHECK_STATUS_AFTER_MONEY_TAKEN
Valid range: 0, 1
Value description: 0 - shutter status check is OFF after money was taken
1 - shutter status check is ON after money was taken
Default value: not configured, shutter status check is ON
Upper case Denomination ID for cassettes (DDC only)
This parameter can be used to specify if the denomination ID’s for dispense
cassettes should be sent as upper case letters in solicited status messages, if
the supply status of a cassette is still GOOD, but the cassette has other errors
that prevents dispensing from it, like (pick failure, fatal status, no reference
value, double picks, etc.).
Parameter name: DENOM_ID_UPPERCASE
Valid range: 0, 1
Value description: 0 - send always lower case letters for cassettes it cannot be
dispensed from, even the supply is GOOD.
1 - send lower case letters only if the supply status of a
cassette is LOW or OUT.
Default value: not configured, send always lower case letters for cassettes
that have dispense problems.

Present failure screen and synchronous retract
With the following parameter you can configure a specific screen that will be
displayed if the cash present function has failed (note jams, blocked shutter,
consumer manipulations). Additionally this parameter enables to perform the
following retract operation synchronously. For NDC this parameter activates
also sending a solicited device error message instead of sending an unsolicited
message.
Parameter name: PRESENT_FAILURE_SCREEN
Value description: 0 - perform synchrous retract and send solicited
message, but do NOT display an additional screen.
010 - 999 - behaviour as value 0 and display the
configured screen.
Default value: not configured, perform the retract operation
asynchronously without sending a device status
message.
Screen display options during cash present
This parameter can be used to configure, whether the screen of the host
function reply should be displayed before the present cash function or after the
present cash function.
Parameter name: DISPLAY_PRESENT_SCREEN
Valid range: 0, 1
Value description: 0 - "TAKE CASH" screen is displayed when money is
accessible after present.
1 - "TAKE CASH" screen is shown before the present is
issued
Default value: not configured, default is 0

Cash Dispenser fatal if reject bin not operational
This parameter can be used to force setting the severity 4 (fatal) for the device
Cash Dispenser, if the reject bin status from the cash dispenser framework is
not operational. Severity 4 is also set if the reject bin is removed.
Parameter name: REJECT_FATAL_STATUS
Valid range: 0-1
Value description: 0 - leave status of device Cash dispenser unchanged
1 - set device Cash dispenser to severity 4 (fatal)

Dispense retries
This parameter can be used to specify how many dispense retries should be
performed if the dispense function returns with an error.
Parameter name: DISPENSE_RETRIES
Valid range: 0 - 99
Value description: 0 - no retries, one dispense call only
>0 - set number of dispense retries
Default value: not configured, 4 dispense tries is done by default
Dispense retries after hardware error
This parameter can be used to specify how many dispense retries should be
performed if the dispense function returns HARDWARE_ERROR (-14). This
parameter has to be combined with parameter DISPENSE_RETRIES (see
previous section). The value of this parameter should be less or equal as
parameter DISPENSE_RETRIES.
Parameter name: HWERR_DISPENSE_RETRIES
Valid range: 0 - 99
Value description: 0 - no retries, one dispense call only
>0 - set number of dispense retries
Default value: not configured, 3 retries is done by default
Example: Assume parameter DISPENSE_RETRIES is set to 5 and

HWERR_DISPENSE_RETRIES is set to 1. In case the dispense
operation returns with HARDWARE_ERROR (-14) the dispense
operation stops after the first retry. If HWERR_DISPENSE_RETRIES
is not set, 5 dispense retries would be done.

Currency Exponent correction
If this parameter is enabled, the WOSA exponent value will be adjusted to the
exponent value that is needed for dispense operations and status messages in
the NDC or DDC environment.
Parameter name: EXPONENT_CORRECTION
Valid range: 0, 1
Value description: 0 - no exponent correction, the value from WOSA is used
1 - exponent value will be adjusted for NDC and DDC
Default value: 1
Maximum cash retracts
This parameter specifies how many cash retracts can be performed by the cash
dispenser. If the specified limit has been reached the dispenser will be locked.
Parameter name: MAXRETRACT
Section in *.PPF: [CCCDMFW]
Valid range: -1; 0 - 99
Value description: -1 sets defined number of retracts (hardware
dependent). The money of the second retract
remain on the stacker. On ProCash Compact
ATM’s without a retract tray the number of
allowed retracts is one. The money remains on
the stacker area and has to be removed manually
by the operator.
0 no retract operations
1 - 99 number of retracts allowed
Default value: -1

Guide Light Control on AFD
The following vendor specific parameter is used to enable the guide light control
on the Advanced Function Dispenser (AFD) series.
Parameter name: AUTO_SWITCH_GUIDLIGHT
Section in *.WN: [CCCDMFW]
Value description: 0 disabled
4 slow flashing enabled
8 medium flashing enabled
Low threshold for physical cassettes
This parameter can be used to specify a low threshold for physical cassettes. If
the physical number of notes become lesser than the specified value, the
physical cassette status changes from GOOD to LOW. This parameter can be
useful to over control the physical status of recycling cassettes in cases when
the LOW status is set too early.
Parameter name: PHYS_GOOD_NOTES
Valid range: 0-9999
Value description: number of notes threshold.

Maximum dispense time (watch dog)
This parameter can be used to specify a time frame in seconds at what time a
single dispense operation should return. This configuration secures the
dispense operation where in case, the dispenser has a connection problem, the
application stops dispense retries to avoid long delays of communication
time-outs at this time (application would hang for a while). The maximum
dispense time can differ between each dispenser type (RM2, CRS, NG, V4) and
the number of notes.
Parameter name: MAX_DISPENSE_TIME
Valid range: n-999
Value description: time in seconds at what time a single dispense operation
should return. The value ’n’ should be greater than the line
communication time-out timer specified in the CSC-W32
layer.

Withdrawal Retract logging and recycling on RM3
If this parameter is enabled, the CCCdmFW uses the CCCashInFW to perform

retract operations for cash withdrawal transactions. On RM3 (Cineo) systems
the retract recycling feature has to be enabled in the XFS layer.
Parameter name: DO_CIN_RETRACT
Section in *.RM2: [CASH_DISPENSER]
Valid range: 0, 1
Value description: 0 - retract logging off
1 - retract logging on, optionally recycling on RM3
Default value: 1
Enable Retract Recycling on RM3:

The following parameter has to be set in PROBASE.CUS:
prodevice.spec30.CRS30.retractRecycleModeCashOut = ALL_OR_NOTHING
Dependency:
If retract recycling is enabled on ProCash/NDC you have to set parameter
SEND_SOL_RETRACT = 1 in CUSTOM.PPF.

WOSA XFS30 Parameters (Wincor Nixdorf only)
Number of minimum bills („money low“ limit)
This parameter is used to set the low condition of the cassettes. It has no effect
if cassettes with a low switch sensor are installed. The value is just an initial
value which is set during the first application start.
Parameter name: prodevice.spec30.CDM30.MINIMUMITEMS
Parameter file: PROBASE.CUS
Value description: integer value sets the „money low“ limit.
Default value: 50
Number of maximum bills to be rejected
This XFS parameter specifies how many bills are allowed to be stored in the
rejected cassette. If the limit has been reached, the XFS status of the reject
cassette changes to WFS_CDM_STATCUFULL (overfilled).
Parameter name: prodevice.spec30.CDM30.REJECTCASSFULL
Parameter file: PROBASE.CUS
Value description: specifies how many bills are allowed to be rejected
Default value: 0 - value not checked, rejects allowed up to physical limit

Parameters in “CUSTOM.PPF” [COIN_DISPENSER]
[COIN_DISPENSER]
Number of coin hoppers
This parameter specifies the maximum number of coin hoppers available for the
application to use, when the host requests for a coin dispense.
Parameter name: NUM_LOG_HOPPERS
Section in *.PPF: [COIN_DISPENSER]
Valid range: 0-4 (for NDC); 0-8 (for DDC)
Value description: integer value sets the number of logical coin hoppers.
Default value: 0
Set coin hopper currency
This parameter specifies the currency for each coin hopper.

Parameter name: CURRENCY_X [1]
Valid range: 3 digit char string (uppercase)
Value description: represents the currency of one coin hopper in the specified
position.
[1] ’X’ represents the coin hopper position from 1 to 4 for NDC and up to 8
.

Set coin hopper values
This parameter sets the coin values of each coin hopper.

Parameter name: VALUE_X [1]
Value description: represents the cassette values.
Default value: 0
Set coin dispense flags
This parameter can be used to set specific conditions how the coin dispense
should be performed if a coin dispense is requested by the host.
Parameter name: DISPENSE_FLAGS
Valid range: 0-7
Value description: 0 - no option set
1 - always try to dispense coins even if only partial dispense
is possible
2 - Dispense from coin hoppers with status LOW.
4 - Dispense from coin hoppers where the minimum coin
threshold is not specified. This threshold can be
configured via XFS parameter:
prodevice.spec30.COUT30.MINIMUMITEMS
defined in PROBASE.CUS
The values are optional bits and can be set in any combination as required
Default value: 2 - Dispense from coin hoppers with status LOW

Number of coin hoppers reported to the host
This parameter can be used to configure how many logical coin hopper types
should be reported to the host. In the standard protocol definition of NDC and
DDC only 4 different logical hopper types are allowed to be reported. If the host
is able to handle more than 4 logical types, this parameter can be used to report
up to 8 different hopper types.
Parameter name: NUM_HOST_HOPPERS
Valid range: 4 or up to 8 if the NDC or DDC protocol has been extended
on the host side.
Value description: integer value sets the number of logical coin hoppers.
Default value: not configured (use 4 by default)

Parameters in “CUSTOM.PPF” [DEPOSIT]
[DEPOSIT]
Options to dispense envelopes
This parameter is used to specify when an envelope should be dispensed to the

customer. Envelopes can be either dispensed during the envelope "C" state or
later when the terminal has received the deposit transaction reply function.
In combination to the dispense options you can configure specific screens via
parameter DISPENSE_SCREEN (see description on the next page) that can be
displayed during the envelope dispense operation. In addition this parameter
can be used to disable the envelope dispenser device.
Parameter name: DISPENSE_ENVELOPE
Valid range: 0, 1, 2, 3
Value description: 0 - Dispense envelope in deposit host reply
function.
1- Dispense envelope in "C" state.
2- dispense envelope in "C" state but not in reply
function.
3- Disable envelope dispenser device.
Envelopes will not be dispensed and
envelope dispenser status messages are not
sent.
Default value: 1
Refer to parameter description of parameter DISPENSE_SCREEN

section ”Screen to be displayed during envelope dispense” on
page 226.

Screen to be displayed during envelope dispense
This parameter is used to specify which screen is displayed during envelope

dispense when the customer is waiting for an envelope that has to be taken
during processing the "C" state or in the deposit host reply function.
Parameter name: DISPENSE_SCREEN
Valid range: "", 010 - 999, HOST
Value description: The following table illustrates the behavior of dispensing
envelopes in combination with parameter
DISPENSE_ENVELOPE and parameter
DISPENSE_SCREEN.
O[1] S[2] DESCRIPTION
0 "" Envelope will be dispensed in deposit reply function. No specifc screen will be
displayed. Typically the "Please Wait" screen of the transaction request state
remains displayed.
0 HOST Envelope will be dispensed in deposit reply function. Screen of host reply function
is displayed
0 nnn Envelope will be dispensed in deposit reply function. Displays specific screen "nnn"
instead of downloaded screen defined in the deposit transaction reply function.
1 "" Envelope is dispensed asynchronously during processing the "C" state, no specifc
screen is displayed but state flow continues.
1 HOST Envelope is dispensed during processing the "C" state but state flow continues and
screen of host reply function will be displayed if the envelope was not already taken.
1 nnn Envelope is dispensed during processing the "C" state, but state flow continues.
Displays a specific screen "nnn" in deposit reply function if the envelope was not
already taken by the customer.
2 "" Envelope is dispensed asynchronously during processing the "C" state, no specifc
screen is displayed but state flow continues (behaviour as option 1).
2 HOST Envelope is dispensed during processing the "C" state but state flow continues and
screen of host reply function is displayed (behaviour as option 1).
2 nnn Envelope is dispensed during processing the "C" state, displays specific screen
"nnn" and waits until the envelope has been taken during processing the "C" state.
State flow continues when the envelope has been taken or captured after timeout.
3 --- Envelopes will not be dispensed and no screen is displayed
[1] = value of parameter DISPENSE_ENVELOPE

[2] = value of parameter DISPENSE_SCREEN
Default value: ""

Screen "Please wait for an envelope"
This parameter can be used to enable displaying a specific screen while the
consumer is waiting for an envelope.
Parameter name: DISPENSE_WAIT_SCREEN
Valid range: "", 010 - 999
Value description: specifies the screen number of the screen that should be
displayed during an envelope dispense.
Allow to cancel deposit transaction
This parameter can be set so that a deposit transaction can be canceled within
the envelope dispense.
Parameter name: CANCEL_ACTIVE
Valid range: 0, 1
Value description: 0 - no, deposit transaction cannot be canceled
1 - yes, deposit transaction can be canceled
Default value: 1
This parameter is currently not used by ProCash/NDC or

ProCash/DDC

Disable printing on retracted envelopes
This parameter can be used to disable printing on retracted envelopes. If the

parameter will be configured and set to "0", dispensed envelopes are left blank
in the retract operation when the consumer has not taken the envelope after the
envelope dispense timeout.
Parameter name: PRINT_ON_ENVELOPE
Valid range: 0, 1
Value description: 0 - do not print on retracted envelopes
1 - print data on retracted envelopes
Default value: not configured, data on retracted envelopes will be printed.
Deposit print character mapping table
These parameters can be used to map print characters to another hexadecimal

postion as the default print position. This can be useful if the print characters
from host need to be mapped to another hex code. For example if the host
sends the character 60H (’) to print the pound character (£), the value 60H in
the hex position 60 has to be replaced with value 9CH.
Parameter names: DEPOSIT_CHARTABLE_LOW
DEPOSIT_CHARTABLE_HIGH
Valid range: see description
Value description: you can use the same character definition as for receipt,
journal or document printers (defined in CUSTOM.PPF).

Deposit entry splitting
This WOSA parameter can be used to control when the Envelope Entry job
should be returned. If the parameter is enabled the Entry job returns
immediately when the envelope has been inserted. If the parameter is disabled,
the Entry job returns when the envelope was fully transported into the safe. The
activation of this parameter speeds up the transaction time of envelope deposits
up to approx. 4 seconds.
Parameter names: ENTRYSPLIT
Section in *.PPF: [DEP]
Valid range: 0, 1
Value description: 0 - no entry splitting, job returns when envelope is in safe
1 - entry splitting enabled, job returns immediately when the
envelope has been inserted.
Default value: 0 - no entry splitting
Prepare envelope dispense
If this WOSA parameter is enabled, empty envelopes from the envelope

dispenser will be automatically transported in the near of the input shutter. The
transport operation will be initiated directly at the end of a previous deposit
transaction or after application start if no envelope is found in the transport
position. This feature has the advantage that the consumer does not need to
wait the long time (approx. 4 seconds) while the envelope is transported the
long distance from the safe to the input shutter.
Parameter names: PREPAREDISPENSE
Section in *.PPF: [DEP]
Valid range: 0, 1
Value description: 0 - prepare dispense OFF
1 - prepare dispense ON
Default value: 0 - prepare dispense OFF

Parameters in “CUSTOM.PPF” [CARD_READER]
[CARD_READER]
Default track read definitions
The following parameters are used to set which ID card tracks should be pre-
read after the card has been inserted independent of settings defined in the
Card Read State (A or T).
Parameter names: DEFAULT_READ_TRACK1
DEFAULT_READ_TRACK2
DEFAULT_READ_TRACK3
Section in *.PPF: [CARD_READER]

Valid range: 0, 1
Value description: 0 - pre-read off; 1 - pre-read on
Default values: DEFAULT_READ_TRACK1 = 0
DEFAULT_READ_TRACK2 = 0
DEFAULT_READ_TRACK3 = 0
Default chip data read on Smart Cards
The following parameter can be used to force reading the chip data in any case
before reading the ID card tracks (if needed to read).
Parameter name: DEFAULT_READ_CHIP
Valid range: 0-2
Value description: 0 - read chip data only if specified in the read conditions of
the Card Read State.
1 - after card insertion read chip data in any case.
(not supported for NCR smart DIP readers)
2 - contact chip, but do not read magnetic track data on
insertion.
Default values: not configured - read chip data only if specified in the
read conditions of the Card Read State.

Card insert/eject wake up time
This parameter is used to set the time after which the card is briefly moved back
and forth to get the consumer attention. This occurs while the card eject timer
is running (card is returned to the customer). For the activation of wake up, the
time range should be within the time of the card eject timeout timer. If you set a
higher value, the wake up procedure is switched off.
Parameter name: EJECT_IN_OUT_TIMER
Valid range: 0, -999 - 9999
Value description: zero value - wake up after half eject time
positive values - time after eject timer start
negative values - time before eject timer end
Default value: 0
For DIP readers this wake up function has to be switched off (value
9999), because insert/eject operations with a remaining card in a DIP
reader will cause undefined error situations
"Remove Card" screen for left cards in DIP reader
This parameter is used to specify a screen to be displayed when the card has
not been removed during the previous transaction. Here you can configure a
screen that can be displayed after the close state. This screen is displayed as
long as the card is still in the DIP reader.
Parameter name: IDLE_REMOVE_SCREEN
Value description: screen number of screen to be displayed
Default value: "" - no separate screen is not displayed

Read tracks during insert or remove direction (SWIPE)
The following (WOSA) parameter is used to specify if the tracks should be read
during card insertion or card removal. This parameter is useful to set especially
for SWIPE card readers(ID24), to minimize read errors. For motorized readers
this parameter must be always zero.
Parameter name: WAITFORREMOVE
Valid range: 0, 1
Value description: 0 - tracks are read during insert (motorized readers)
1 - tracks are read during removal (SWIPE readers)
Card manipulation threshold
This parameter can be used to set a threshold how often the application should
call a card reader reset command to move an ID card or/and repair the card
reader device before the application goes out of service.
Parameter name: MANIP_THRESHOLD
Valid range: 0-99
Value description: 0 - application goes immediately OOS if the card reader is
not operational.
>0 - sets the number of reset retries before the application
goes OOS
Default: 0 - not configured

Card jam threshold
This parameter can be used to configure a threshold for the number of

consecutive card insert jams. If the jam threshold is exceeded, the application
sends an unsolicited card reader status message (StClass\StCode 6434\0049)
to the host.
Parameter name: JAM_THRESHOLD
Valid range: 0-99
Value description: sets a jam threshold, an unsol. message will be sent when
the threshold is exceeded.
Default: 0 - not configured, unsolicited message will never be sent
DIP eject screen
This parameter is required for DIP readers with chip card capability. It configures
a screen that is shown when a latched DIP card could not be contacted and is
now unlatched so that the track data is read on card removal. It must be set on
Wincor systems when XFS parameter USELATCH is set to 2.
Parameter name: DIP_EJECT_SCREEN
Valid range: three digit screen number
Value description: specifies the screen that is displayed in the described
situation
Default: "" - not configured

Contactless Reader Handling
This parameter is used to enable contactless reader support. If this parameter

is enabled and a contactless reader is installed, the application is starting the
Insert job with track or EMV access.
Parameter name: CONTACTLESS_HANDLING
Valid range: 0,1,4
Value description: 0 - contactless reader support off
1 - contactless reader track, starts the insert job with Track1
and Track2 access (but no chip and Track3 access)
4 - contactless reader EMV, starts a job which performs a
configurable EMV dummy transaction.
Default: 0 - contactless reader support off

Parameters in “CUSTOM.PPF” [BARCODE]
[BARCODE]
The following parameters are used to set up the barcode reader.
Configure barcode type formats
The following parameter configures the barcode types that should be accepted
by the barcode reader.
Parameter name: ACCEPT_CODE_FORMAT
Section in *.PPF: [BARCODE]
Valid range: comma separated list; Syntax: n1,n2,n3,n4,..
Each value in the list indicates the type of barcode that
should be accepted by the barcode reader.
Value description:
1D Barcode types:
1 - EAN 128
2 - EAN-8/13
3 - JAN-8/13
4 - EAN-8/13 with 2 digit add-on
5 - EAN-8/13 with 5 digit add-on
6 - UPC-A/E
7 - UPC-A/E with 2 digit add-on
8 - UPC-A/E with 5 digit add-on
9 - NW-7 (CODABAR)
10 - Interleaved 2 of 5 (ITF)
11 - CODE 11 (USD-8)
12 - CODE 39
13 - CODE 49 (NS with BR02)
14 - CODE 93
15 - MSI/PLESSEY (NS with BR02)
16 - STANDARD 2 of 5 (NS with BR02)
17 - INDUSTRIAL 2 of 5 (NS with BR02)
18 - POSNET (NS with BR02)
19 - PDF-417 (NS with BR02)
20 - DATAMATRIX (NS with BR02)
21 - MAXICODE (NS with BR02)
22 - CODE ONE (NS with BR02)
23 - CHANNEL CODE (NS with BR02)
2D Barcode types are listed on the next page ...

Parameters in “CUSTOM.PPF” [BARCODE]
2D Barcode types:
113 - UPCE1
114 - UPCE1/2
115 - UPCE1/5
124 - 128
126 - PLESSEY
128 - STD2 OF 5IATA
130 - MICRO PDF 417
135 - TELEPEN ORIGINAL
136 - TELEPEN AIM
137 - RSS
138 - RSS EXPANDED
139 - RSS RESTRICTED
140 - COMPOSITE CODE A
141 - COMPOSITE CODE B
142 - COMPOSITE CODE C
143 - POSICODE A
144 - POSICODE B
145 - TRIOPTIC CODE 39
146 - CODABLOCK F
147 - CODE 16K
148 - QR CODE
149 - AZTEC
150 - UK POST
151 - PLANET
152 - POST NET
153 - CANADIAN POST
154 - NETHERLANDS POST
155 - AUSTRALIAN POST
156 - JAPANESE POST
157 - CHINESE POST
158 - KOREAN POST
Default values: not configured

Example entry: "1,2,4,5,12,14,20"

Parameters in “CUSTOM.PPF” [OPERATOR_SCREENS]
[OPERATOR_SCREENS]
Printer header for Operator screens
These parameters can be used to set predefined macro sequences as a header

for operator screens of the SOP user exit functions to be printed on the journal
or/and receipt printer. This permits the setting of a special CPI or/and LPI size
and additional presettings for the operator screens
Parameter names: PRINTER_HEADER_RECEIPT
PRINTER_HEADER_JOURNAL
PRINTER_HEADER_DOCUMENT
Section in *.PPF: [OPERATOR_SCREENS]

Valid range: valid macro sequences or/and text
Value description: the macro sequences must be available by CSCW32 and
be supported by the printer.
Default value: #NCT##CPI15##LPI6#
(Sets standard character set, CPI15 and LPI6)
If the parameter(s) does/do not exist in the registry, the default setting
is CPI15 and LPI6. If the parameter(s) is/are empty the last actual
setting is used.

Parameters in “CUSTOM.PPF” [JOURNALPRINTER]
[JOURNALPRINTER]
Set journal destination on paper
This parameter is used to set the journal output on paper of the journal printer.
This parameter has to be set to zero if no journal printer is physically connected
and not configured in the registry.
Parameter name: PAPER_JOURNAL
Section in *.PPF: [JOURNALPRINTER]
Valid range: 0, 1
Value description: 0 - Printing on journal printer disabled
1 - Printing on journal printer enabled
Default value: 1 - Printing on journal printer enabled
Journal printer CPI setting
This parameter is used to set the CPI size for the journal printer.
Parameter name: CPI
Valid range: 8, 10, 12, 15, 17, 25
Value description: integer value sets number of characters per inch
Default value: 15
Journal printer LPI setting
This parameter is used to set the LPI size for the journal printer.
Parameter name: LPI
Value description: integer value sets number of lines per inch
Default value: 6

Double Width
This parameter is used to specify if the printer should print the characters in
double width by default.
Parameter names: DOUBLE_WIDTH
Valid range: 0, 1
Value description: 0 - Double Width off, 1 - Double width on
Condensed Print
condensed mode by default.
Parameter names: CONDENSED
Valid range: 0, 1
Value description: 0 - Condensed off, 1 - Condensed on

Electronic journal
This parameter is used to set the electronic journal log destination for host print
data. Depending on the setting of the parameters TOP_JOURNAL_PATH and
CUST_JOURNAL_PATH in section [ELECTRONIC_JOURNAL], the host print
data can be stored optional into the journal files of the specified path locations.
Parameter name: ELECTRONIC_JOURNAL
Valid range: 0-3
Value description: 0 - no logging of host print data
1 - log host print data to TOPMSG destination
2 - log host print data to CUSTMSG destination
3 - log host print data to both destinations
Default value: 0 - no electronic journal log
Send Spooler active or journal printer error message
This parameter can be used if the host should receive the original journal printer
error in the unsolicited status message instead of spooler active message
(StClass: 6434, Stcode: 000E).
Parameter name: SEND_SPOOLER_ERROR
Valid range: 0, 1
Value description: 0 - send original journal printer error message
1 - send spooler active message
Default value: not configured - send spooler active message

Keep original printer status if Spooler is configured
This parameter can be set if the host should receive the original hardware and
supply status of the journal printer when the journal spooler is configured. If this
parameter is NOT configured or the value is ZERO, the journal printer severity
never reaches fatal (4) and the supply status never is set to empty (3), thus the
journal printer is out of paper or/and not operational. This behavior can prevent
that the host takes the ATM out of service.
Parameter name: SPOOLER_KEEP_PRINTER_STATUS
Valid range: 0, 1
Value description: 0 - The printer highest severity condition is WARNING (2)
and highest supply condition is LOW (2).
1 - use original journal printer severity and supply status.
Fall down to FATAL (4) and supply OUT (3)
Force to send "Paper Out" message on paper out supply
If this parameter is enabled, the application always sends a "Paper Out"

message to the host if the Device Status framework reports a paper out status,
even the previous print job could be successfully finished. If this parameter is
disabled, paper out status messages or more likely jam status messages are
sent to the host only if the journal print job fails to print the host data.
Parameter name: FORCE_PAPER_OUT_SUPPLY
Valid range: 0, 1
Value description: 0 - send printer error to the host only if the journal print job
fails.
1 - send paper out message on paper out supply status.
Default value: not configured - send printer error to the host only if the
journal print job fails.

Assign codepage control sequence to NDC font type
This parameter can be used to assign the codepage control sequence

ESC%nnn (nnn = codepage number) to a local defined NDC font type. The
codepage control sequence can be included in the host print data which is sent
from the central to the terminal. See also section ”Font type” on page 263. This
parameter is supported for NDC journal and receipt print.
Parameter name: CP_JOURNAL_FONT_TYPE_NNN [1]
Valid range: one valid NDC font type character
Value description: NDC font type character, which is already, or has to be new
specified via parameter JOURNAL_FONT_TYPE in the
JOURNAL_FONT_XXX [2] section.
Refer to section ”Font type” on page 263.
[1] ’NNN’ represents the codepage number specified via ESC%
[2] ’XXX’ represents the font section number
Example:
Assume ESC%850 is included in the host print data for the journal printer.
If you specify CP_JOURNAL_FONT_TYPE_850 = "2", all font parameters in
the JOURNAL_FONT_XXX section are selected where parameter setting
JOURNAL_FONT_TYPE = "2" is found.
Print journal host data always prior function ID’s
This parameter can be used to specify if the journal print data sent from host
should be printed immediately after the host reply has been received before any
function ID has been processed.
Parameter name: PRINT_JOURNAL_ALWAYS
Valid range: 0, 1
Value description: 0 - print journal host data through function ID
1 - print journal host data prior function ID’s
Default value: not configured, print journal host data through function ID.

Hard disk free space low threshold
This parameter specifies the hard disk low threshold. If lesser bytes on hard disk
are available as it is specified via this parameter, the terminal sends an
unsolicited warning (CCERRMAP: 6434\0043_WARNING) message to the host
after each consumer transaction. If lesser than 1MB is available on hard disk,
the terminal sends an unsolicited error (CCERRMAP: 6434\0043_ERROR)
message to the host. In this case the host should take the terminal out of
service.
Parameter name: HDD_SPACE_LOW_LIMIT
Valid range: 0 - 4000 (MB)
Value description: hard disk free space low threshold.
If the value is zero, the hard disk space is not checked.
Default value: not configured, hard disk free space is not checked.
Enable journal file writing error messages
This parameter activates sending unsolicited journal error messages if journal

information cannot be stored in the journal file. It is related to journal Write() calls
to write the journal data into the dayly journal files initiated by the ProTopas
Journal framework (CCJourna.dll). If file writing fails, the journal framework
sends an error event to the application. If the parameter is enabled and the
journal data could not be stored into the file, the application sends an unsolicited
journal error message to the host in the next ADRS run at the end of the current
consumer transaction. This parameter should also be enabled if for NDC
Electronic Journal Upload (EJU), or for DDC Store And Forward (SAF) is
configured.
Parameter name: CHECK_FILE_JOURNAL
Valid range: 0, 1
Value description: 0 - do not send unsolicted messages if file writing fails
1 - send unsolicited journal message if journal data cannot
be stored into the file.
Default value: not configured - do not send journal error messages

Configure EJU or SAF shared mapping file
This parameter specifys the filename where all the electronic journal data are
stored, which can be sent up to the host via Electronic Journal Upload in NDC
or sent up to the host through Store And Forward message sequences in DDC
Parameter name: EJU_SAF_FILE_NAME
Valid range: file path
Value description: specifies the path and filename for EJU or SAF.
Important Note: Please make sure that all sub directories

exist if the file will be configured in a sub folder of the hard
disk.
Default value: not configured - EJU or SAF disabled

Example entry: C:\JOURNAL\EJU_SAF.JRN
Configure EJU or SAF maximum file size
This parameter specifys the maximum file size (in kilobytes) of the EJU or SAF
share mapping file.
Parameter name: EJU_SAF_MAX_FILE_SIZE
Value description: specifies the file size in kilobytes plus additional 5 KB
header size.
Default value: not configured - size 0, EJU or SAF disabled

EJU journal NCR compatible mode
This parameter can be used to configure the EJU journal log format in NCR
compatible mode. If this parameter is enabled specific control sequences like
SO and LF or converted in the same way how the original NCR system it does.
Parameter name: EJU_CONVERT_HOST_DATA
Valid range: 0, 1
Value description: 0 - NCR conversion off (default)
1 - NCR conversion on
Extended range of characters in file journal
This parameter can be used to enable printing of characters in range

20-FF hex. Be default the journal files are printed in the restricted character
range 20-7F hex.
Parameter name: ALL_CHARS_IN_EJRN
Valid range: 0, 1
Value description: 0 - character range 20-7F hex (default)
1 - extended character range 20-FF hex

Print unicode (GDI only)
This parameter can be used to enable unicode character printing based on a

local configured unicode character table configured via registry parameter
UNICODE_XX (XX = hexadecimal start index for the definition of the next 16
unicode characters). This parameter can be set as global option and individually
for each font section.
Parameter name: PRINT_UNICODE
Valid range: mode:font:width:height
Value description: The value consists of 4 optional parameters:
mode - value range:
UTF8 sets UTF-8 mode
font - valid facia name of a windows font
width - character width in pixel
height - character height in pixel
Example Values: "UTF8" or "UTF8:SimHei" or "UTF8:SimHei:15:30"
[1] ’XXX’ represents the font section number from 001-006

Parameters in “CUSTOM.PPF” [ELECTRONIC_JOURNAL]
[ELECTRONIC_JOURNAL]
Maximum journal files
These two parameters are used to specify the journal file creation cycle for the
TOPMSG and CUSTMSG journal files. It specifies for how many days a new
journal file should be new created. (Note: These parameters replace PPF
parameter MAX_JOURNAL_FILES (registry parameter MAX_JFILES)).
Parameter names: TOP_MAX_FILES
CUST_MAX_FILES
Section in *.PPF: [ELECTRONIC_JOURNAL]
Valid range: 0 - 549 (maximum 1.5 years)
Value description: number of journal files to be created
Default value: 10
Journal Spooler reset sequence
This parameter can be used to send printer macro sequences to the journal
printer when the journal printer framework sends a reset command to the
printer. This is useful if the printer is loosing the default settings after reenabling
the journal printer during hardware error conditions.
Parameter name: SPOOLER_RESET
Valid range: ASCII character string (max. 255 characters)
Value description: The string can contain valid printer macros or single
ASCII characters in range 20H - 7FH.
Default value: ""
The following example entry initialize the journal printer with CPI15 and LPI8
during a printer reset initiated by the journal spooler framework.
Example:
SPOOLER_RESET = "#CPI15##LPI8#"

Journal Spooler check timer for Spooler data
This parameter specifies in which time cycle the spooler checks the spooler file
contents that should be printed out to the journal printer.
Parameter name: SPOOLER_PRINT_CACHE_TIMER
Valid range: 0 - 255 seconds
Value description: time in what cycle the spooler checks if spooler data exist
Default value: 2
Journal Spooler threshold
This parameter specifies the number of print jobs be collected before the
Journal Spooler starts printing.
Parameter name: SPOOLER_PRINT_CACHE_THRESHOLD
Valid range: 0 - 255 seconds
Value description: number of collected print jobs before the spooler starts
printing
Default value: 10
Maximum spool file size
This parameter can be used to encrease or decrease the maximum spool file
size in kilobytes.
Parameter name: SPOOLER_MAX_SPOOL_FILE
Valid range: 0 - 9999 (kilobytes)
Value description: spool file size in kilobytes
Default value: not configured - size of 2000 kilobytes is used

Maximum unprinted spool data size
This parameter can be used to encrease or decrease the maximum unprinted

data size within the spool file in kilobytes.
Parameter name: SPOOLER_MAX_SPOOL_AREA
Valid range: 0 - 9999 (kilobytes)
Value description: unprinted spool data size in kilobytes
Default value: not configured - size of 1000 kilobytes is used

Parameters in “CUSTOM.PPF” [RECEIPTPRINTER]
[RECEIPTPRINTER]
Receipt printer CPI setting
This parameter is used to set the CPI size for the receipt printer.
Parameter name: CPI
Valid range: 8, 10, 12, 15, 17, 25
Default value: 15
Receipt printer LPI setting
This parameter is used to set the LPI size for the receipt printer.
Parameter name: LPI
Default value: 6
Receipt printer character set
This parameter is used to specify which character set should be used by default.
Parameter name: USER_CHARSET
Valid range: 0, 1
Value description: 0 - standard character set; 1 - user defined character set
Default value: 0

Double Width
Valid range: 0, 1
Condensed Print
Valid range: 0, 1

Receipt printer page header
This parameter can be used to initialise the receipt printer with special settings
via printer macros or text which should be printed at the beginning of the receipt.
Parameter name: RECEIPT_PAGE_HEADER
Valid range: ASCII characters in range of 20H - 7FH
Value description: macros and characters can be used as init sequences or to
print header lines in front of the host print data.
Default value: no value
Example:
The following entry sets “Variable Receipt length” (macro #VLM#) and two “Line
Feeds” (macro #LF#) for every receipt.
RECEIPT_PAGE_HEADER = “#VLM##LF##LF#”
Receipt printer page footer
This parameter can be used to append local defined printer data inclusive
macros together with the print data that are sent by the host. If parameter
RECEIPT_FOOTER_LINE (see description on the next page) is configured, the
footer data can be placed at a specific line after the host print data.
If RECEIPT_FOOTER_LINE is not configured or zero, the footer will be directly
appended to the host data print raw data stream.
Parameter name: RECEIPT_PAGE_FOOTER
Value description: appends or inserts print data or macros to the print raw data
stream of host print data.

Receipt footer line position
This parameter can be used to define a specific line where the local defined
footer data should be appended after the host print data. If for example the host
print data consists of 15 lines and the parameter is set to 20, the footer will be
appended at the 20th line. If the host print data consists of 25 lines, the footer
will be directly appended after the host print data.
Parameter name: RECEIPT_FOOTER_LINE
Value description: specifies the line where the footer will be appended.
LED timer during receipt delivery
This parameter is used to set the LED blinking time during the receipt delivery.
Parameter name: LEDTIMER
Value description: number of time in milli seconds the guide light is blinking on
receipt eject.
Default value: 5000 - blinking time of 5 seconds

Enable R01 print data merging (NDC only)
This parameter has to be set if the receipt printer does not support the carriage
return (#CR#) command. Then the R01 line is not correctly mixed together with
the host print line. If this parameter is enabled, the R01 and host print data are
merged together via a software algorithm and not just inserting a #CR# after the
R01 line.
Parameter name: MERGE_R01
Valid range: 0, 1
Value description: enables host and R01 data merging via software algorithm.
Assign codepage control sequence to NDC font type
This parameter can be used to assign the codepage control sequence

ESC%nnn (nnn = codepage number) to a local defined NDC font type. The
codepage control sequence can be included in the host print data which is sent
from the central to the terminal. See also section ”Font type” on page 263. This
parameter is supported for NDC receipt and journal print.
Parameter name: CP_RECEIPT_FONT_TYPE_NNN [1]
Valid range: one valid NDC font type character
Value description: NDC font type character, which is already, or has to be new
specified via parameter RECEIPT_FONT_TYPE in the
RECEIPT_FONT_XXX [2] section.
Refer to section ”Font type” on page 263.
[1] ’NNN’ represents the codepage number specified via ESC%
[2] ’XXX’ represents the font section number
Example:
Assume ESC%850 is included in the host print data for the receipt printer.
If you specify CP_RECEIPT_FONT_TYPE_850 = "2", all font parameters in the RECEIPT_FONT_XXX
section are selected where parameter setting RECEIPT_FONT_TYPE = "2" is found.

Force receipt delivery after each host reply
This parameter can be used to activate the receipt delivery for every trans-
action reply. This might be useful if a consumer can perform multiple transac-
tions (transaction chaining with Balance enquiry, withdrawal, transfer, deposit),
and the print data of each transaction should be printed on single receipts. The
setting of this parameter is always necessary if no formfeed (FF) is sent for each
transaction reply but single receipts are required.
Parameter name: SINGLE_RECEIPT
Valid range: 0, 1
Value description: 0 - do not append formfeed (FF).
1 - append formfeed (FF) to host printer data for each host
reply.
Default value: 0
Force to send "Paper Out" message on paper out supply
If this parameter is enabled, the application always sends a "Paper Out"

message to the host if the Device Status framework reports a paper out status,
even the previous print job could be successfully finished. If this parameter is
disabled, paper out status messages or more likely jam status messages are
sent to the host only if the receipt print job fails to print the host data.
Parameter name: FORCE_PAPER_OUT_SUPPLY
Valid range: 0, 1
Value description: 0 - send printer error to the host only if the receipt print job
fails.
1 - send paper out message on paper out supply status.
Default value: not configured - send printer error to the host only if the
receipt print job fails.

Options during Rear Balancing print
This parameter can be used to set specific print options in a Rear Balancing
transaction regarding Header/Footer and R00/R01 printing. The options can be
enabled or disabled via setting the bit that is assigned to the requested option.
Parameter name: REAR_BAL_OPTIONS
Valid range: Bit order
0x01 - Do not print contents of PAGE_HEADER
0x02 - Do not print contents of PAGE_FOOTER
0x04 - Do not print contents of R00
0x08 - Do not print contents of R01
Value description: The bit options can be set in any combination you like.
Default value: not configured - all options are off


mode - value range:

Parameters in “CUSTOM.PPF” [DOCUMENTPRINTER]
[DOCUMENTPRINTER]
Document printer CPI setting
This parameter is used to set the CPI size for the document printer.
Parameter name: CPI
Valid range: 8, 10, 12, 15, 17, 25
Default value: 15
Document printer LPI setting
This parameter is used to set the LPI size for the document printer.
Parameter name: LPI
Default value: 6
Document printer character set
This parameter is used to specify which character set should be used by default.
Parameter name: USER_CHARSET
Valid range: 0, 1
Value description: 0 - standard character set; 1 - user defined character set
Default value: 0

Double Width
Valid range: 0, 1
Condensed Print
Valid range: 0, 1
Document printer page header
This parameter can be used to initialise the document printer with special
settings via printer macros or text which should be printed at the beginning of
the document.
Parameter name: DOC_PAGE_HEADER
Value description: macros and characters can be used as init sequences or to
print header lines in front of the host print data.
Default value: no value

Document printer page footer
This parameter can be used to insert or append local defined printer data
inclusive macros together with the print data that are sent by the host. If
parameter DOC_FOOTER_LINE (see description) is configured, the footer data
are inserted in the specified line. If DOC_FOOTER_LINE is not configured or
zero, the footer will be appended to the host data print raw data stream.
Parameter name: DOC_PAGE_FOOTER
Value description: appends or inserts print data or macros to the print raw data
stream of host print data.
Document footer line position
This parameter specifies the line position where the footer specified by
DOC_PAGE_FOOTER should be inserted. If the parameter is zero, the footer
data will be appended.
Parameter name: DOC_FOOTER_LINE
Value description: specifies the line where the footer will be inserted.

Maximum documents to be collected before delivery
This parameter is used to set the maximum documents to be collected in the

collection tray before the bundle is delivered to the customer.
Parameter name: NO_OF_DOC_BEFORE_EJECT
Valid range: 1 - 10
Value description: specifies how many documents can be collected in the
collection tray prior to delivery.
Default value: 10
Cancel document processing
This parameter can be used to set the cancel activation within the document
printing process.
Parameter name: CANCEL_ACTIVE
Valid range: 0 - not active; 1 - cancel active
Value description: currently not used by ProCash/NDC-DDC
Default value: 0


mode - value range:

Parameters in “CUSTOM.PPF” Printer Font parameters
Printer Font parameters

ProCash/NDC-DDC can use maximum 8 different fonts for each kind of printer.
All parameters can be set for the receipt, document and journal printer. In
parameter configuration file CUSTOM.PPF you find 6 font sections configured
by default for ProCash/NDC and ProCash/DDC.
The following parameters can be set for each font:
Font type
This parameter is used to specify which NDC or DDC font type should be used
for this font section
Parameter names: JOURNAL_FONT_TYPE
RECEIPT_FONT_TYPE
DOCUMENT_FONT_TYPE
Section in *.PPF: [JOURNAL_FONT_XXX] [1]
[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: 1, 2, >, ?, 7, B (NDC)
1, A, V, X, S, Y (DDC)

The following tables show what Font type is used by ProNDC or ProDDC
depending on which character set is selected by the NDC or DDC protocol:
Font type Character set defined by NDC Sequence

1 Single Alpha 1 ESC(1
> Double Alpha 1 ESC(>
? Double Alpha 2 ESC(?
B Double Alpha 3 ESC(B
Font type Character set defined by DDC Sequence

1 Standard char set ESC5
A Alternate (user) char set ESC4
V VT chars from standard char set ESC5...VT
X VT chars from alternate (user) char set ESC4...VT
S Second alternate (user) char set ESCz1
Y VT chars from second alternate (user) char set ESCz1...VT

Double Width
double width for the selected font.
Parameter names: JOURNAL_DOUBLE_WIDTH
RECEIPT_DOUBLE_WIDTH
DOCUMENT_DOUBLE_WIDTH
[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: 0, 1
Value description: 0 - Double Width off, 1 - Double width on, 2 - unchanged
Condensed Print
condensed mode for the selected font.
Parameter names: JOURNAL_CONDENSED
RECEIPT_CONDENSED
DOCUMENT_CONDENSED
[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: 0, 1
Value description: 0 - Condensed off, 1 - Condensed on, 2 - unchanged

User defined Character set
This parameter is used to specify if the printer should print the characters from
the user defined character set or from the standard character set.
Parameter names: JOURNAL_USER_CHARSET
RECEIPT_USER_CHARSET
DOCUMENT_USER_CHARSET
[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: 0, 1
Value description: 0 - print from standard character set
1 - print from user defined character set
2 - unchanged, stay in current character set
Printer initialization macros or characters
The following parameter can be used to insert additional macros or/and text in
front of the print data.
Parameter names: JOURNAL_MACRO
RECEIPT_MACRO
DOCUMENT_MACRO
[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: character string or macros (e.g. #LOGO1#)
Value description: Character string that will be inserted in front of the print
data. The character string can be one or multiple macros
or/and additional text.

Printer character mapping table
This parameter is used to define a printer character table. This character table
can be used to map characters to another hex position of the printer if
neccessary. The mapping position of each character depends on the printer
data from the host.
The printer character table is divided into a low part which contain positions from
000-127 (00H-7FH) and a high part which contains hex positions from 128 - 255
(80H-FFH).
Parameter names: RECEIPT_USER_CHARSET_LOW
JOURNAL_USER_CHARSET_LOW
DOCUMENT_USER_CHARSET_LOW
RECEIPT_USER_CHARSET_HIGH
JOURNAL_USER_CHARSET_HIGH
DOCUMENT_USER_CHARSET_HIGH
Sections in *.PPF: [JOURNAL_FONT_XXX] [1]

[RECEIPT_FONT_XXX]
[DOCUMENT_FONT_XXX]
Valid range: 0-255
Value description: low and high part of the character table can have a
maximum of 127 hex values which represents 127
characters.
Each character position can be defined in the range from
(00H-FFH)

Print unicode font specific (GDI only)

Parameter names: JOURNAL_PRINT_UNICODE
RECEIPT_PRINT_UNICODE
DOCUMENT_PRINT_UNICODE
Sections in *.PPF: [RECEIPT_FONT_XXX] [1]
[JOURNAL_FONT_XXX]
[DOCUMENT_FONT_XXX]
mode - value range:

Parameters in “CUSTOM.PPF” GDI Windows name for receipt printer
GDI Windows name for receipt printer

This parameter specifies the Windows name of the installed receipt printer. The
Windows printer name (e.g. "Wincor Nixdorf ND9G" which is a pure Windows
printer) is needed if the installed printer should operate as a Windows printer.
During J/Install installation the Windows printer name is automatically set in the
Registry and also CUSTOM.PPF, if CSC-W32 has installed and configured the
receipt printer as a Windows printer.
If the printer TH21, TH22, TP07 or TP27 should operate as a Windows printer,
you have to modify the CSC-W32 configuration file CUSTOM.CUS prior instal-
lation. Parameter TH21_GDI_INTERFACE, TH22_GDI_INTERFACE,
TP07_GDI_INTERFACE or TP27_GDI_INTERFACE has to be set to YES.
Parameter name: REC_PRINTER_NAME
Section in *.PPF: [GDI_REC_PRINTER]
Valid range: character string (max 128 characters)
Value description: specifies the Windows printer name
Default value: ""
GDI Windows name for document printer

This parameter specifies the Windows name of the installed document printer.
The Windows printer name (e.g. "Wincor Nixdorf TH97/G") is needed if the
installed printer should operate as a Windows printer.
During J/Install installation the Windows printer name is automatically set in the
Registry and also CUSTOM.PPF, if CSC-W32 has installed and configured the
receipt printer as a Windows printer. If the printer TH97/G or TP01 should
operate as a Windows printer, you have to modify the configuration file
CUSTOM.CUS of CSC-W32 prior installation. Parameter TH97_GDI_
INTERFACE or TP01_GDI_INTERFACE has to be set to YES.
Parameter name: DOC_PRINTER_NAME
Section in *.PPF: [GDI_DOC_PRINTER]
Value description: specifies the Windows printer name
Default value: ""

Parameters in “CUSTOM.PPF” Screen Font configuration
Screen Font configuration

The following parameters are used to set the font types which are used in the
screen download from the host.
[VIEWER_FONT]
Number of screen fonts
This parameter specifies the number of fonts to be used by ProCash/NDC.

Parameter name: TABLE_ENTRIES
Section in *.PPF: [VIEWER_FONT]
Valid range: 0, 9
Value description: number of used fonts
Default value: 9
Font name
The following parameter is used to specify the NDC or DDC font name which is
used by ProCash/NDC or ProCash/DDC.
Parameter name: NAME
Section in *.PPF: [VIEWER_FONT_XXX] [1]
Valid range: char value eight digits maximum in uppercase letters. This
name has to match exactly with the name specified within
the Windows font file (*.FON).
Value description: NDC or DDC font name
Default values: See table “Default NDC font names” and
table “Default DDC font names”
[1] ’XXX’ represents the section number from 001 - 009.
See default settings of table “Default NDC font names” and table “Default DDC
font names” on the next page.

Parameters in “CUSTOM.PPF” [VIEWER_FONT]
Table 16: Default NDC font names
SECTION NAME FONT FILE NAME NDC font description

[VIEWER_FONT_001] NDC-SA1 NDC-SA1.FON Single Alpha 1
[VIEWER_FONT_002] NDC-DA1 NDC-DA1.FON Double Alpha 1
[VIEWER_FONT_003] NDC-SA2 NDC-SA2.FON Single Alpha 2
[VIEWER_FONT_004] NDC-DA1 NDC-DA1.FON Double Alpha 2
[VIEWER_FONT_005] NDC-G1 NDC-G1.FON Graphic 1
[VIEWER_FONT_008] NDC-SARA NDC-SARA.FON Single Arabic
[VIEWER_FONT_009] NDC-DARA NDC-DARA.FON Double Arabic
Table 17: Default DDC font names
SECTION NAME FONT FILE NAME DDC font description

[VIEWER_FONT_001] DDC-NORM DDC-NORM.FON Standard Font
[VIEWER_FONT_002] DDC-HELV DDC-HELV.FON Helvetica
[VIEWER_FONT_003] DDC-ROLL DDC-ROLL.FON Rollíng
[VIEWER_FONT_004] DDC-ENGL DDC-ENGL.FON English
[VIEWER_FONT_005] DDC-CENT DDC-CENT.FON Century
[VIEWER_FONT_006] DDC-8X12 DDC-8X12.FON Border 8x12
[VIEWER_FONT_007] DDC-8X16 DDC-8X16.FON Border 8x16
[VIEWER_FONT_008] DDC-RUSS DDC-RUSS.FON Russisch
[VIEWER_FONT_009] DDC-ARAB DDC-ARAB.FON Arabic

Parameters in “CUSTOM.PPF” [VIEWER_FONT]
Font size
The following parameter is used to specify the font size for NDC and DDC fonts
in pixels.
Parameter name: SIZE
Valid range: See table 18 and table 19 on page 273
Value description: font size in pixels. The value depends on the created font.
The value for fixed size fonts has to match exactly with the
size of the Windows font.
Default values: See table 18 and table 19 on page 274
Font height
The following parameter is used to specify the font size for NDC and DDC in
pixels.
Parameter name: HEIGHT
Valid range: See table 18 and table 19 on page 274
Value description: font height in pixels. The value depends on the created font.
The value for fixed size fonts has to match exactly with the
size of the Windows font.
Default values: See and on

Parameters in “CUSTOM.PPF” Font Resolution tables
Font Resolution tables

Since Release 1.0/05 ProCash/NDC and ProCash/DDC delivers fonts in the
resolution 640x480, 800x600 and 1024x768. Therefore parameters "SIZE" and
"HEIGHT" in the [VIEWER_FONT_XXX] sections needs to be changed
depending in which display resolution the application should run.
The following tables show the values of "SIZE" and "HEIGHT" in the dependent
resolution to be set for ProCash/DDC and ProCash/NDC:
Table 18: DDC resolution dependent values for "SIZE" and "HEIGHT"
NAME 640x480 800x600 1024x768

SIZE x HEIGHT SIZE x HEIGHT SIZE X HEIGHT
DDC-NORM 16 x 24 20 x 30 25 x 38
DDC-HELV 32 x 48 40 x 60 51 x 76
DDC-ROLL 32 x 48 40 x 60 51 x 76
DDC-ENGL 32 x 32 40 x 40 52 x 51
DDC-CENT 32 x 48 40 x 60 51 x 76
DDC-CHN4 32 x 32 40 x 40 51 x 51
DDC-CHN5 32 x 32 40 x 40 51 x 51
DDC-CHN6 32 x 32 40 x 40 51 x 51
DDC-CHN7 32 x 32 40 x 40 51 x 51
DDC-8X12 16 x 24 20 x 30 25 x 38
DDC-8X16 16 x 32 20 x 40 25 x 51
DDC-RUSS 16 x 24 20 x 30 25 x 38
DDC-RUS4 32 x 32 40 x 40 51 x 51
DDC-THAI 16 x 24 20 x 30 25 x 38
DDC-ARAB 16 x 24 20 x 30 25 x 38

Table 19: NDC resolution dependent values for "SIZE" and "HEIGHT"
NAME 640x480 800x600 1024x768

SIZE x HEIGHT SIZE x HEIGHT SIZE X HEIGHT
NDC-SA1 20 x 30 25 x 37 32 x 48
NDC-DA1 40 x 30 50 x 37 64 x 48
NDC-SA2 20 x 30 25 x 37 32 x 48
NDC-DA1 40 x 30 50 x 37 64 x 48
NDC-G1 20 x 30 25 x 37 32 x 48
NDC-G2 20 x 30 25 x 37 32 x 48
NDC-G3 20 x 30 25 x 37 32 x 48
NDC-SARA 20 x 21 25 x 26 32 x 33
NDC-DARA 40 x 42 50 x 52 64 x 67
The values of "SIZE" and "HEIGHT" will be automatically set during

J/Install installation or if you register NT fonts via the "Configuration
Manager". Refer to section ”Resolution dependent WINNT Font
installation” on page 278.

NDC font identifier
The following parameter identifies the NDC or DDC font type. The font identifier
is the specification which type of font is selected in the ’ESC(’ sequence for NDC
or ’ESC’ for DDC.
Parameter name: NDC_FONT
Valid range: single character
Value description: one character for NDC or two characters for DDC
Default values: See table “Standard NDC and DDC font identifiers”
Table 20: Standard NDC and DDC font identifiers
SECTION NDC NDC FONT DDC NDC FONT

DEFAULT NAME DEFAULT NAME
IDENTIFIER IDENTIFIER
[VIEWER_FONT_001] 1 NDC-SA1 F0 DDC-NORM
[VIEWER_FONT_002] > NDC-DA1 F1 DDC-HELV
[VIEWER_FONT_003] 2 NDC-SA2 F3 DDC-ROLL
[VIEWER_FONT_004] ? NDC-DA1 FF DDC-ENGL
[VIEWER_FONT_005] 3 NDC-G1 F2 DDC-CENT
[VIEWER_FONT_006] 4 NDC-G2 F@ DDC-8X12
[VIEWER_FONT_007] 5 NDC-G3 FG DDC-8X16
[VIEWER_FONT_008] 7 NDC-SARA FI DDC-RUSS
[VIEWER_FONT_009] B NDC-DARA FE DDC-ARAB
See also ProCash/NDC and ProCash/DDC User Guide section

Screens for detailed descriptions about screen control sequences.

NDC double size
This parameter has to be set for double size fonts.

Parameter name: NDC_DOUBLE
Valid range: 0, 1
Value description: 0 - single, 1 - double
Default values: See table “Default settings for NDC and DDC fonts”
Table 21: Default settings for NDC and DDC fonts
SECTION DEFAULT NDC FONT DEFAULT DDC FONT

VALUE NAME VALUE NAME
[VIEWER_FONT_001] 0 NDC-SA1 0 DDC-NORM
[VIEWER_FONT_002] 1 NDC-DA1 1 DDC-HELV
[VIEWER_FONT_003] 0 NDC-SA2 1 DDC-ROLL
[VIEWER_FONT_004] 1 NDC-DA1 1 DDC-ENGL
[VIEWER_FONT_005] 0 NDC-G1 1 DDC-CENT
[VIEWER_FONT_006] 0 NDC-G2 0 DDC-8X12
[VIEWER_FONT_007] 0 NDC-G3 0 DDC-8X16
[VIEWER_FONT_008] 0 NDC-SARA 0 DDC-RUSS
[VIEWER_FONT_009] 1 NDC-DARA 0 DDC-ARAB

Display characters in proportional mode
This parameter can be used to display characters in proportional mode. In

proportional mode the distance between each character will be calculated by
the size of each character. This has the effect, that lines become shorter than in
normal mode depending on the characters to be displayed. In this mode
characters from a downloaded screen are read line by line and not character by
character. This speeds up the display time for screens which contain escape
sequences to fill a screen via ’ESC R’ or ’ESC U’ in DDC mode. This mode is
also useful to set if you like to display WINNT proportional fonts instead of the
standard NDC or DDC fonts.
Parameter name: PROPORTIONAL
Valid range: 0, 1
Value description: 0 - proportional off, 1 - proportional on
Default values: 0 - proportional off

Parameters in “CUSTOM.PPF”Resolution dependent WINNT Font installatio
Resolution dependent WINNT Font installation

Since Release 1.0/05 ProCash/NDC and ProCash/DDC are able to register
automatically Windows Fonts (*.FON) with the Display Resolution which is
currently set during the installation. ProCash/NDC and ProCash/DDC delivers
a set of default Fonts which are extracted from the J/Install CD and copied to
the C:\PROTOPAS\FONTS\XXX directory (the ’XXX’ placeholder stands for
640X480, 800X600 and 1024X768). Within batch program
"C:\PROTOPAS\UPDCONF.CMD" at the end of the batch routines the font
registration utility "CPYNTFNT.EXE" is called that analyzes first the current
Windows display resolution. Than all files are copied from the
C:\PROTOPAS\FONTS\ subfolder of the detected resolution to the
\WINNT\FONTS directory. In addition the utility registers all standard fonts in the
Windows environment for immediate access by ProCash/NDC or
ProCash/DDC. At least the utility updates the values of parameter "SIZE" and
"HEIGHT" in the [VIEWER_FONT_XXX] section of configuration file
"CUSTOM.PPF". The last step is a call to PARAC to set the new values for SIZE
and HEIGHT from "CUSTOM.PPF" into the registry.
Later after the installation if you have decided to change the Windows display
resolution you can use the "Configuration Manager" to register default fonts in
a different resolution. See menu "Update" ->"Install Fonts and Bitmaps" of
"Configuration Manager".
Refer to section “Font and Graphic utilities” on page 400 for detailed
description CPYNTFNT.EXE.
Resolution dependent Bitmap/Icon installation

Since Release 1.0/05 during the installation all default Bitmaps and Icons are
copied with the currently detected resolution from the resolution dependent
subfolder C:\PROTOPAS\BITMAPS\XXX (the ’XXX’ placeholder stands for
640X480, 800X600 and 1024X768) to C:\PROTOPAS\BITMAPS. The Bitmaps
and Icon copy process will be initiated via utility "CPYNTFNT.EXE" in a second
step after the automatic NT font registration during the "UPDCONF.CMD" run.
You are also able to exchange Bitmaps and Icons later after the installation with
the "Configuration Manager". See also section ”Resolution dependent WINNT
Font installation” on page 278.

Parameters in “CUSTOM.PPF” User defined WINNT fonts
User defined WINNT fonts

If you like to create your own Windows fonts (*.FON), you can use utility
"FONTEDIT.EXE" or the procedures as described in section ”Font and Graphic
utilities” on page 400. Very important is that the name of the font you create has
to match with the filename (without extension). This fontname has to be entered
in uppercase letters in section [VIEWER_FONTS_XXX] for parameter "NAME"
in configuration file "CUSTOM.PPF" in directory C:\INSTALL\CUSTOM. The
new created font has to be copied in one of the resolution sub directories of
C:\PROTOPAS\FONTS\XXX. Than you can use function "Install Fonts and
Bitmaps" in menu "Update" of the "Configuration Manager" to register the new
font in the requested resolution. At least you have to make a CUSTOM.PPF
update via the PARAC call (CfgM "Call PARAC for Update" in menu "Update").
The second option is using utility "CPYNTFNT.EXE" via parameter options to
register a new Windows font. The PARAC call after the Windows registration is
needed too. See section ”Font and Graphic utilities” on page 400 the detailed
description of utility "CPYNTFNT.EXE".
IMPORTANT: Depending on the selected Display Resolution you

have to set the correct SIZE and HEIGHT within the Windows fonts.
See table “DDC resolution dependent values for "SIZE" and
"HEIGHT"” on page 273 and table “NDC resolution dependent values
for "SIZE" and "HEIGHT"” on page 274. The values of "SIZE" and
"HEIGHT" in configuration file "CUSTOM.PPF" are set
automatically via utility "CPYNTFNT.EXE".
If you are using "FONTEDIT.EXE" you have to check the value of
"Nominal Vert. Resolution" and "Nominal Horiz. Resolution" in menu
"Fonts" function "Header". The value must be 96 for all resolutions.

Parameters in “CUSTOM.PPF” Enable and preconfigure ProAgent
Enable and preconfigure ProAgent

The following parameters are needed to enable and preconfigure the ProAgent.
If you need details of all configuration parameters refer to the ProAgent
(Windows) V1.0 Administration & Management System Manual Version 1.0/30.
A sub set of parameters needed by ProAgent are stored in configuration file
"PROVIEW.INA" located in directory C:\PROTOPAS\CONF. The basic
parameter set will be configured during ProAgent installation.
Set Primary/Secondary Server and Port
The following parameters are used to specify the primary and secondary Server
name and Port number. The Server name and Port number has to match with
the settings on the ProAgent Server station. If the primary server cannot pe
reached, the secondary server is taken to establish the connection.
Parameter name: NAME
Sections in *.PPF: [PRIMARYSERVER]
[SECONDARYSERVER]
Valid range: character string (any TCP/IP host name or IP address)
Value description: specifies the ProAgent Server station name (usually the
computer name) or the TCP/IP address of the server.
Default value: ""
Parameter name: PORT

Sections in *.PPF: [PRIMARYSERVER]
[SECONDARYSERVER]
Valid range: 00000 - 99999 (any valid port number)
Value description: specifies the ProAgent Server port number the Agent tries
to connect to.
Default values: 18988

Parameters in “CUSTOM.PPF” Enable and preconfigure ProAgent
Terminal ID of ATM client
The following parameter is used to specify the terminal ID from the ATM. The
terminal name can be any name you like to set. Usually the computer name
should be used. The computer name is default is the parameter value is an
empty string.
Parameter name: TERMINALID
Sections in *.PPF: [PROVIEW_SSTPAGENT]
Valid range: any string without blanks
Value description: This entry is the name which displayed on the ProAgent
Server desktop window if the Agent is connected with the
server.
Default value: ""
Enable Application Events
To enable displaying the application specific event messages in the event

window of ProAgent Server, you have to activate Bit 32 of parameter DESTxxx
in section [CUSTMSG]. Refer to section section “[TOP_MSG] and
[CUST_MSG]” on page 147.
Error description for ProAgent Server log window
To enable clear text messages for the ProAgent Server log window you can
replace journal text variable $DCMC_DEVICE_ERROR$ against
$DCMC_DEVICE_ERROR_INFO$. This variable contains the error message
description specified in parameter INFO of the CCERRMAP table.
VDM Activation for ProAgent
For systems which support Vendor Dependend Mode (VDM) please refer to
document ProAgent (Windows) V1.0 Administration & Management System
Manual Version 1.0/30 for detailed description of required registry parameter
settings.

Parameters in “CUSTOM.PPF” EMV parameters
EMV parameters
The following sections describe some important parameters that can be set in
configuration file CUSTOM.PPF.
Completion Objects
This parameter specifies the default Data Object list (list of TAGs) to be used in
Solicited Status Message extension, Last Transaction Status Extension and
Logical EMV error messages.
Parameter name: COMPLETION_OBJECTS
Sections in *.PPF: [LYNXCI_EMV]
Valid range: ASCII character string (max. 64)
Value description: list of TAGs to be sent
Default value: 9F27959B9F06
Contact Threshold
This parameter specifies after how many failed contact attempts an unsolicited
error message should be sent up to the network.
Parameter name: CONTACT_THRESHOLD
Valid range: 0 - 99
Value description: number of chip contact attempts
Default value: 9

Language support
The following parameter specifies a list of supported languages.

Parameter name: LANGUAGE_SUPPORTED
Valid range: ASCII character string (max 64)
Value description: the string can contain multiple two digit language codes.
Default value: ""
Example: "endefrsp"
represents the languages "English" (en), "German" (de),
"France" (fr), "Spain" (sp).
EMV Protocol Vendor Specification
This parameter specifies the vendor specific EMV protocol.

Parameter name: PROTOCOL_SPEC
Valid range: WN, NCR CAM II, Diebold D91x
Value description: specifies which EMV vendor protocol should be used.
WN - Wincor Nixdorf protocol specification
NCR CAM II - NCR protocol specification
Diebold D91x - Diebold protocol specification
Default value: not configured, WN used as default

Force decline AIDs
This parameter is used to specify a list of AIDs to force a decline (AAC),

regardless of what is specified in the EMV reply buffer and regardless of
transaction type (TAG 9C).
Parameter name: FORCE_DECLINE_AIDS
Section in *.PPF: [LYNXCI_EMV]
Valid range: comma separated list of AIDs
Value description: list of AIDs
Default value: not configured (empty)
Force decline AIDs for Transaction Type nn
This parameter is used to specify a list of AIDs to force a decline (AAC) for the
current transaction type match, regardless of what is specified in the EMV reply
buffer.
Parameter name: FORCE_DECLINE_TA_TYPE_nn_AIDS[1]
[1] nn = transaction type in range 00-99
Example: To request a decline in case of Balance inquiries for
MasterCard, the following has to be configured:
"FORCE_DECLINE_TA_TYPE_30_AIDS"="A000000004"

Force script error AIDs
This parameter is used to specify a list of AIDs where issuer script errors should
NOT be ignored.
Parameter name: FORCE_SCRIPT_ERROR_AIDS
Value description: list of AIDs where issue scripts should be ignored
Force script error AIDs for Transaction Type nn
This parameter is used to specify a list of AIDs for matching transaction types,
where issuer script errors should NOT be ignored.
Parameter name: FORCE_SCRIPT_ERROR_TA_TYPE_nn_AIDS[1]
Value description: list of AIDs where issue scripts should be ignored
[1] nn = transaction type in range 00-99

Code Tables
This parameter configures the font ESC sequence to be used/inserted if the

preferred name (TAG 9F12) shall be displayed for issuer code table index nn
(TAG 9F11 range 01-10) instead of the label (default).
Make sure the specified font exists and matches the ISO 8859 code table index.
Additionally the template should switch back to the standard font.
Parameter name: CODE_TABLE_nn_SEQ[1]
Valid range: valid escape sequence
Value description: font escape sequence
[1] nn = index in range 01-10
Example: The following setting specifies the font escape sequence for
issuer code table 05: CODE_TABLE_05_SEQ = "\1b(5"
Candidate list selection method
This parameter specifies the candidate list selection method.

Parameter name: SELECTION_METHOD
Valid range: 0-15
Value description: the valid values are bits and can be combined:
1 - If only one candidate this one must not have the 'must
confirm' bit (weight 0x80 in priority) set.
2 - If set then a 'must confirm' candidate can be
auto-selected.
4 - Canadian Interac selection.
8 - US common selection.
Default value: not configured (default = 0)

Ignore issuer script failures
This parameter can be used to enable if issuer script failures should be ignored.
Parameter name: IGNORE_ISSUER_SCRIPT_FAILURE
Valid range: 0, 1
Value description: 0 - do NOT ignore issuer script failures
Default value: not configured (default for DDC = 1, for CAM2/WN = 0)

Note: This parameter must be set when the
FORCE_SCRIPT_ERROR parameters are used
Transaction processing
This parameter specifies how to process EMV data in transaction requests and
transaction replies.
Parameter name: TRANSACTION_PROCESSING
Valid range: 0-2
Value description: 0 - If EMV sent in request, EMV must come back in reply
(default)
1 - EMV is sent once in request, no need to send EMV back
(no 2nd AC if no EMV from host, default for D91x)
2 - EMV sent in every request until 2nd AC performed,
no need to send EMV back (no 2nd AC if no EMV from
host)
Default value: not configured (default for DDC = 1, for CAM2/WN = 0)

Preferred AIDs
This parameter specifies the AIDs to be used/selected directly if found.

Parameter name: PREFERRED_AIDS
Valid range: comma separated AID list
Value description: list of AIDs (priority from left to right)
EMV error conditions
This parameter can be used to control the behavior for certain error conditions.
Parameter name: EMV_ERROR_CONDITIONS
Valid range:
Value description: the valid values are bits and can be combined:
1 - Simulate a blocked card if there is only one blocked
candidate
2 - Restore mag track 2 if 1st AC fails
4 - Ignore missing ATM use in AUC
Default value: not configured (internal default = 5)
Ignore extended authorize failure
This parameter is used to specify if the external authenticate failures should be

ignored.
Parameter name: IGNORE_EXT_AUTH_FAILURE
Valid range: 0,1
Value description: 0 - do NOT ignore failures
1 - ignore failures
Default value: not configured (default = 1)

Supported US common AIDs
This parameter defines the AID for which the US common selection logic shall
be activated (see parameter SELECTION_METHOD).
Parameter name: SUPPORTED_US_COMMON_AIDS
Valid range: comma separated AID list
TLV data for contactless EMV initial transaction
This parameter is used to specify TLV data to be set for a 1-TAP initial trans-
action, if contactless EMV shall be performed in the Card Read State (see
parameter CONTACTLESS_HANDLING = 4).
Parameter name: CONTACTLESS_TLV_DATA
Valid range: valid TLV data string
Value description: TLV data
Example: To perform a typical 0-amount initial transaction
the following TLV data has to be set:
"9F02060000000000005F2A0209785F360102"

Contactless EMV TAG extraction
Some contactless card readers return specific non-standard TAGs which

contain standard EMV TAGs required by the network.
This parameter is used to specify which TAGs should be extracted (eliminated)
so only the contents will be used for further processing.
Parameter name: CONTACTLESS_EXTRACT_TAGS
Valid range: comma separated list of TAGs
Value description: list of TAGs to extract
Contactless EMV TAG removal
With this parameter specific TAGs can be removed before sending the message
to the network. This can be 3-byte TAGs or specific non-standard TAGs
reported by the contactless reader. Removing TAGs is the final step (esp. after
extraction of TAGs) before the message is sent.
Parameter name: CONTACTLESS_REMOVE_TAGS
Valid range: comma separated list of TAGs (limited wildcard/* allowed)
Value description: list of TAGs to remove
Example: To remove specific TAGs the following can be set:
"DF*,FF*"

Contactless EMV error screens
This parameter specifies which screens to show in specific error scenarios.

These scenarios are documented in EMV Contactless Specifications for
Payment Systems, Book A chapter User Interface Standard Messages.
Parameter name: CONTACTLESS_ERROR_SCREENS
Valid range: comma separated list of "mgsid:screen:delay"
Value description: show screen for delay seconds when msgid is
received
Example: To show screen 900 for 2 seconds upon when collision
detected and screen 901 for 2 seconds in all other valid
scenarios, the following must be set:
"19:900:2,*:901:2"
Only the following Message Identifiers are supported and should be used:
0F - Processing error
18 - Please insert or swipe card (switch interface)
19 - Please present one card only (collision)
1C - Insert, swipe or try another card (switch interface)
20 - See Phone for instructions
21 - Present card again
* - used when TAP failed and no specific screen was shown

Contactless EMV offline error checking
This parameter specifies which offline checks to perform for specific schemes,
esp. VISA.
If a check is activated and fails then the transaction is aborted.
Parameter name: CONTACTLESS_CHECKS
Valid range: comma separated list of check keywords
Value description: list of offline checks to perform
The following offline checks are implemented:

VISA-IAD - Checks if card reports IAD (TAG 9F10), abort if not
VISA-ATM - Checks if the card can be used at ATM, abort if not
VISA-TC - Abort if approved (not allowed for ATM)
VISA-T2ED-PAN - Checks if track 2 equivalent and PAN matches,
abort if not
Transaction Objects (DDC only)
This parameter is used to configure TAGs to be sent to the host in transaction

request.
Parameter name: TRANSACTION_OBJECTS
Valid range: list of TAGs
Value description: list of TAGs to be sent

Acquirer Identifier 9F01
This parameter is used to configure an Acquirer Identifier, which uniquely

identifies the acquirer within each payment system. Please refer to the
EMV2000 Integrated Circuit Card Specification for Payment Systems Book1-4 for
Parameter name: ACQUIRER_IDENTIFIER_9F01
Sections in *.PPF: [EMV_TAGS]
Valid range: ASCII character string in byte value notation of 6 bytes.
Value description: Two numeric digits with a preceding backslash represents
one byte (example entry: \11\22\33\44\55\66).
Merchant Category Code 9F15
The following parameter can be used to configure the merchant category, which
classifies the type of business being done by the merchant, represented
according to ISO 8583: 1993 for Card Acceptor. Please refer to the EMV2000
Integrated Circuit Card Specification for Payment Systems Book1-4 for detailed
description.
Parameter name: MERCHANT_CATEGORY_CODE_9F15
one byte (example entry: \11\22).

Terminal Country Code 9F1A
The following parameter is used to specify the country code, which indicates the
country of the terminal, represented according to ISO 3166. Please refer to the
EMV2000 Integrated Circuit Card Specification for Payment Systems Book1-4 for
Parameter name: TERMINAL_COUNTRY_CODE_9F1A
one byte (example entry: \11\22).
Terminal Capabilities 9F33
The following parameter is used to specify the terminal capabilities, which

indicates the card data input, CVM, and security capabilities of the terminal.
Please refer to the EMV2000 Integrated Circuit Card Specification for Payment
Systems Book1-4 for detailed description.
Parameter name: TERMINAL_CAPABILITIES_9F33
one byte (example entry: \11\22\33).
Default value: not configured in CUSTOM.PPF, but set to default value
\60\48\20 in registry during installation.

Terminal Type 9F35
The following parameter is used to set the Terminal Type, which indicates the
environment of the terminal, its communications capability, and its operational
control. Please refer to the EMV2000 Integrated Circuit Card Specification for
Payment Systems Book1-4 for detailed description.
Parameter name: TERMINAL_TYPE_9F35
Valid range: ASCII character string in byte value notation of 1 byte.
one byte (example entry: \11).
\14 in registry during installation.
Additional Terminal Capabilities 9F40
This parameter is used to configure the Additional Terminal

Capabilities that indicates the data input and output capabilities of the terminal.
Please refer to the EMV2000 Integrated Circuit Card Specification for Payment
Systems Book1-4 for detailed description.
Parameter name: ADDITIONAL_TERMINAL_CAPABILITIES_9F40
one byte (example entry: \11\22\33\44\55).
\80\00\B0\53\FF in registry during installation.

Parameters in “CUSTOM.PPF” Vendor specific parameters
Vendor specific parameters
Number of physical cassettes names
The following parameter specifies how many physical cassettes names are
reported by the NCR or Diebold WOSA.
Parameter name: NUM_PHYS_NAMES
Section in *.NCR: [CASH_DISPENSER]
Section in *.DIB:
Valid range: 0 - 16
Value description: specifies the number of physical units provided by the NCR
or Diebold WOSA.
Default value: set to 4 on NCR or Diebold systems
Configure physical names of cassettes units
The following parameters specify the physical names of the cassette units that
are reported from NCR or Diebold WOSA.
Parameter name: PHYS_NAME_X [1]
Section in *.DIB:
Valid range: ASCII character string
Value description: physical cassette unit name
Default NCR: PHYS_NAME_1 = Unit 1 (top)
PHYS_NAME_2 = Unit 2 (next to top)
PHYS_NAME_3 = Unit 3 (next to bottom)
PHYS_NAME_4 = Unit 4 (bottom)
Default DIEBOLD: PHYS_NAME_1 = BIN1

PHYS_NAME_2 = BIN2
PHYS_NAME_3 = BIN3
PHYS_NAME_4 = BIN4
[1] - X = physical unit number

Set number of maximum rejected notes
The following parameter is required on NCR systems. This parameter sets the
number of maximum rejected notes in the cash unit structure. By default NCR
Wosa returns a zero value in the cash unit structure for the maximum rejected
notes. This has the effect that the application reports always an overfilled status
for the reject cassette because the current rejected notes counter is equal or
higher than the maximum rejected notes counter. This parameter will be
configured by default on DIEBOLD systems as well.
Parameter name: MAX_REJECT_NOTES
Section in *.DIB:
Value description: specifies the limit of maximum number of rejected notes.
Default value: 300
Set number of maximum retracts
The following parameter is required on NCR systems. This parameter sets the
number of maximum allowed retract operations in the cash unit structure. By
default NCR XFS returns a zero value in the cash unit structure for the
maximum allowed retracted notes. This has the effect that the application never
performs a cash retract operation, because for a ProCash/NDC or
ProCash/DDC application a zero value means retract inhibit.
Parameter name: MAX_RETRACT
Section in *.DIB:
Valid range: 0 - 99
Value description: specifies the maximum allowed retracts.
Default value: 99

Enable test dispense function
The following parameter is required on Diebold systems. This parameter can be

used to enable a test dispense function that can be called from a
ProTopas/SOP-NDC or ProTopas/SOP-DDC function.
Parameter name: MV_TESTDISPENSE
Section in *.DIB:
Valid range: 0-2
Value description: 0 - Test dispense switched off
1 - Dispense from all cassettes with the same currency.
Reject the bundle at the end (reject is called through
SOP).
2 - Dispense from each single cassette and reject each
single note after each single dispense.
Default value: 1 for Diebold systems, all others not configured 0
Divide remaining notes equally to physical cassettes
This parameter can be used to divide the logical number of notes remaining in
cassette equally to all existing physical cassettes units of the same
denomination. This parameter can be used only if parameter PHYS_NAME_X
is configured.
Parameter name: EQUAL_PHYS_CASS_COUNTERS
Section in *.DIB:
Valid range: 0, 1
Value description: 0 - logical number of remaining notes not divided
1 - divide logical number of remaining notes

Parameters in “CUSTOM.PPF” DDC Deposit Emulation Parameters
DDC Deposit Emulation Parameters

This section describes all configuration parameters which are involved in the
DDC Deposit Emulation feature. It also describes parameter dependencies,
how the setup print templates, and how to define regular expressions.
Enable DDC Deposit Emulation feature
This parameter enables the DDC Deposit Emulation feature.

Parameter name: ENABLE
Section in *.PPF: [DDC_DEPOSIT_EMULATION]
Valid range: 0, 1
Value description: 0 - disabled
1 - enabled

Operation Key Buffer Replacement
The following parameters are used for the Operation Key Buffer replacement in
the Consumer Request message.
Standard Deposit Op Key
This is the Operation Key (Op Key) Buffer that will be sent up to the host when
a deposit emulation transaction is initiated.
Parameter name: OPKEY_STD
Valid range: valid 8-character Op Key buffer field
Value description: The Deposit Op Key value for Standard Envelope deposits.
This entry contains an 8-character Op Key value which can
use a '?' digit as a placeholder. The placeholder is intended
to allow certain selections made during the course of the
transaction to pass through. Each position in the Standard
Deposit Op Key value using the placeholder is replaced
with the character in the position from the triggering Op Key.

Operation Key Buffer Triggers
The following parameters are the triggers used to initiate a deposit emulation
transaction. If an I or @I state is entered with any of the following Operation Key
(Op Key) Buffers then the corresponding deposit emulation transaction will be
initiated.
Deposit Op Keys
The following deposit type dependent parameters contain the Op Key value
generated by the states to trigger a Deposit Emulation Transaction. This entry
contains an 8-character Op Key value which can use a '?' digit as a placeholder.
The intend of the placeholder in this case is different than it is for the Standard
Deposit Op Key. It is intended here to allow a collection of similar Op Key values
to be accepted as a trigger.
Parameter names: OPKEY_CASH
OPKEY_SINGLE_CHECK
OPKEY_BUNDLE_CHECK
OPKEY_MIXED
Valid range: valid 8-character Op Key buffer field
Value description: The Deposit Op Key value for Standard Envelope deposits.
This entry contains an 8-character Op Key value which can
use a '?' digit as a placeholder. The placeholder is intended
to allow certain selections made during the course of the
transaction to pass through. Each position in the Standard
Deposit Op Key value using the placeholder is replaced
with the character in the position from the triggering Op Key.

Suppress Unsolicited Cash Status
This parameter can be used to suppress sending Unsolicited Cash Status

messages to the host.
Parameter name: SUPPRESS_UNSOL_CASH_STATUS
Valid range: 0, 1
Value description: 0 - Send unsolicited status
1 - Suppress sending unsolicited Cash Status
Redirect Function for host FID and Screen
This parameter specifies the Function ID or Enhanced Function ID which will be

compared with the content of the Function Command received from host. In
case of a match, the values and logic of parameter REDIRECT_NEXT_X[1]
takes place (where X will be used as the same numeric index).
Parameter name: REDIRECT_FUNC_X[1]
Valid range: valid FID [screen] or ENH FID [function] [screen]
Value description: This entry is used to match the FID or ENH FID of the
Function Command response from host. In case of a match,
the values of the paired parameter REDIRECT_NEXT_X[1]
will be processed.
Examples FID: "A" or "A123"
Examples EFID: "CI 001103" or "CI 001103467"
[1] - X = Index in range 1 to 99. It has to be started with index 1 continuing
without gaps with index 2, 3, and so on.
Important Note: The parameter with the most compare digits will be used
first to find a match. If there is no match, parameters with
less compare digits are verified. Max 12 verify digits for
Enhanced Function ID are allowed, otherwise no match.

Redirect Next Function processing
This parameter contains a list of values which defines the logic how the terminal
should process the Function Command, if the value of parameter
REDIRECT_FUNC_X is matching.
Parameter name: REDIRECT_NEXT_X[1]
Valid range: string parameter list (colon ’:’ separated)
Value description:
Index 0: Transaction Type
ALL - all types
CASH - cash deposit
SINGLE_CHECK - single Check deposit
BUNDLE_CHECK - bundle Check deposit
MIXED - mixed deposit
Index 1: Next State to match
valid next state (3 digits) which should match with Function
Command from host. Use * as a wild card value to force
matching all next states.
Index 2: New FID or ENH FID
valid FID with optional screen
or
valid ENH FID (with preceding semi colon ’;’ character)
Index 3: New Next State
valid next state (3 digits). Leave this field blank to keep the
existing next state.
Index 4: New Screen
valid screen which is displayed with the associated new
FID (not used for ENH FID). Leave this field blank to keep
the existing screen. Value 000 is not allowed.

Index 5: Honor Network Printer Flags

This field controls if host print data should be printed or
ignored. Valid values as bit combination (range: 0 - 15):
0 - use all print flags as set in host Function Command
1 - ignore host journal print data
2 - ignore host receipt print data
4 - ignore host statement print data
8 - ignore host envelope print data
Index 6: Printer Flags Form and Tags
This field consists of 3 semi colon ’;’ separated sub fields:
- Print destination
Valid values as bit combination (range: 1 - 15):
1 - used for journal print data
2 - used for receipt print data
4 - used for statement print data
8 - used for envelope print data
- Local print form parameter FORMx[1]
Specifies an index based form parameter where the local
print data with its variable placeholders are defined.
- Tag parameter TAGx[1]
Specifies an index based tag parameter where the rules
are defined how the associated form template will be
handled.

Example FID: ALL:J42:A:139:166:3:1;FORM1;TAG1
Example EFID: ALL:J42:;CI 001104:137:163:3:1;FORM2;TAG2
[1] - x = Index in range 1 to 99. It has to be started with index 1 continuing

Print Form Template
The following parameter is used to define a print template for printing on the
requested destination(s). The template can be set in the same format as it is
used in the print data buffer from host function commands. It can also contain
multiple variables as placeholders for data which can be parsed from original
host print data, downloaded screens, or certain Buffer ID’s.
Parameter name: FORM_X[1]
Valid range: character string of print data with optional variables.
Value description: The print data can be defined
Example data: "\\0d\\0aTHIS A DEPOSIT EMULATION\\0d\\0a
CONSUMER TRANSACTION\\0d\\0a
ATM : %#DEPEMU_VAR1%\\0d\\0a
DATE : %#DEPEMU_VAR2%\\0d\\0a
BANK : %#DEPEMU_VAR3%\\0d\\0a"
The example data contain three variables DEPEMU_VAR1, DEPEMU_VAR2
and DEPEMU_VAR3. These variables will be filled based on the definition of
parameter TAGx[1] which is set in parameter REDIRECT_NEXT_X[1] at index 4.
[1] - x = Index in range 1 to 99.

Print Tag and Rules
The following parameter is used to define a print template for printing on the
requested destination(s). The template can be set in the same format as it is
used in the print data buffer from host function commands. It can also contain
multiple variables as placeholders for data which can be parsed from original
host print data, downloaded screens, or certain Buffer ID’s.
Parameter name: TAG_X[1]
Valid range: comma separated list with semi colon separated sub fields
Source;SourceType;VarName;ParsingRule, ...
Value description: The sub fields are defined as follows:
Index 0 Source
Valid values:
0 - screen data
1 - buffer data
2 - printer data
Index 1 SourceType
If Source = 0: Specifies the screen to parse
If Source = 1: Specifies the Buffer ID to parse
If Source = 2: Specifies the kind of printer data to parse
Kinds are: JOURNAL, RECEIPT, STATEMENT, DEPOSIT
Index 2 VarName
Specifies the variable name which will be filled according
the parsing rule defined in Index 3. The variable has to be
defined with preceding bracket %# and trailing bracket %.
Example: %#MyVarName%
Index 3 ParsingRule
Can be a match pattern value or parameter REGEXx[1] with
a regular expression rule.
Example: If value "Amount:" is set, the data will be parsed
until a match, the next non space data block will be taken.
Examples: "2;JOURNAL;%#MyVarName1%;REGEX1"
"2;RECEIPT;%#MyVarName2%;Amount:"

Regular Expressions
The following parameter can be used to define Regular Expressions. Supported

is the syntax specification according ECMA Script syntax for C++ 2011.
Details can be taken from Internet page:
http://www.cplusplus.com/reference/regex/ECMAScript/
Parameter name: REGEX_X[1]
Valid range: valid regular expression syntax.
Value description: visit web page mentioned on top for details.
Example: To retrieve data like a date 21/03/2018 you can use
following regular expression:
"((\\d{1,2})/(\\d{1,2})/(\\d{4}|\\d{2}))"
Suppress sending Buffer IDs from ’@I ’ state
This parameter can be used to suppress sending certain Buffer IDs in the
Consumer Request message which are defined in a ’@I ’ state downloaded
from host. Typically a host has not configured Buffer IDs in the state table if
native Cash Deposit is not supported. But just in case the host downloads Buffer
IDs which needs to be ignored, the following parameter will do the job.
Parameter name: CLEAR_BUFFERIDS_X[1]
Valid range: state;bufferId1,bufferId2,bufferId3,...
Value description: state valid 3 digit state number
bufferIdx 3 digit Buffer ID which should be suppressed
Example: J33;310,311,320,321
[1] - x = Index in range 1 to 99. It has to be started with index 1 continuing

Suppress Cash In Buffer in Consumer Request message
This parameter can be used to suppress sending native Cash In Buffer content
in a Consumer Request message. If the parameter is enabled the internal
variable "DCMC_CIN_DATA_REQ" will be cleared before the ’I’ state is entered.
Parameter name: CLEAR_CIN_TRAN_BUFFER
Valid range: comma separated list of valid 3 digit state numbers
Value description: The value list defines the Consumer Request states
the buffer should be cleared
Suppress Cheque Buffer in Consumer Request message
This parameter can be used to suppress sending native Cheque Buffer content
in a Consumer Request message. If the parameter is enabled the internal
variable "DCMC_CHQ_DATA_REQ" will be cleared before the ’I’ state is
entered.
Parameter name: CLEAR_CHQ_TRAN_BUFFER
Valid range: comma separated list of valid 3 digit state numbers
Value description: The value list defines the Consumer Request states
the buffer should be cleared

Parameter Management The PARAC run
Parameter Management
The PARAC run

During the J/Install installation process, but after installation of PARAC/NT, an
automatic call is initiated to the PARAC interface to preset the Windows registry
with default parameter definitions for each product.
The following graphics show four pop up windows which are indicating the
progress of the update steps. The last window shows the PARAC return code.
If PARAC returns with an error code (other than 0 or 7), an error description in
red color appears in the second line of the last pop up window.
Figure 4: PARAC Start window
Figure 5: PARAC Update window
Figure 6: PARAC Finish window with return code (0)

Parameter Management Parameter update process via PARAC
The fourth pop up window is a PARAC error window with an example error
return code. All finish pop up windows with return codes other than 0 or 7 come
up with a second line in red color as a short description of the error. (The only
exception is return code 7. This is only a warning: Missing parameter restored).
Figure 7: PARAC Finish window with error return code
Parameter update process via PARAC

After the installation in most cases some parameters must be additionally set or
changed. All parameters which are included in the Definition Files of PARAC
(located in C:\PARAC\DEF as binary files *.BIN), can be set in the customization
file CUSTOM.PPF. If the PARAC program is called after the installation it looks
for an existing CUSTOM.PPF file in C:\PARAC. If the PPF file exists and a new
parameter is defined or value of an existing parameter has been changed,
PARAC stores the new parameters or changed values into the WINNT Registry.
The correct syntax and value ranges of valid ProCash/NDC or ProCash/DDC
specific parameters for the CUSTOM.PPF can be taken from this manual. But
this is only a very small part of the parameters from the whole ProCash/NDC-
DDC environment. A huge number of basic parameters for each product like
ProBase/C, Protopas and ProCash/NDC or ProCash/DDC will be installed
automatically during the installation. To avoid any confusion we only have
included the most important parameters which are often changed after
installation.

Parameter Management PCEDT - PARAC Parameter Editor
PCEDT - PARAC Parameter Editor

If you want to view the whole set of defined parameters you have to use the
program PCEDT.EXE. This program is a frontend program where you can
search for parameters or select one for modification. With this program you can
create a new CUSTOM.PPF file where you can include parameters selected by
PCEDT. The new CUSTOM.PPF can be stored in C:\PARAC. If you then call
PARAC, the contents of CUSTOM.PPF will be moved into the Registry. After the
parameter move, the CUSTOM.PPF will be deleted.
Figure 8: Workbench of PCEDT

Parameter Management Vendor and AddOn depended configuration
Vendor and AddOn depended configuration

After the PARAC configuration was finished, additional batch routines will be
called within "C:\PROTOPAS\UPDCONF.CMD". Depending on what hardware
vendor (Wincor Nixdorf, NCR or Dienbold) and what AddOn product will be
installed different batch routines with specific parameter settings are called. The
vendor- and AddOn depended configuration- and batch routines will be stored
in several sub folders under "C:\PROTOPAS\CONF". During installation the
files from those sub folders are moved up to the working folder
"C:\PROTOPAS\CONF". Please refer to the tables in section ”ProCash/NDC
parameters” on page 313 and section ”ProCash/DDC parameters” on page 319
to get a short description about the contents of the vendor- and AddOn depened
sub folders.
One additional part of parameter configuration will be performed through
"CCRCCONV.EXE". These parameter files (*.INA format) are delivered via the
update diskettes of ProCash/NDC or ProCash/DDC and will be copied to
"C:\PROTOPAS\CONF" and to the vendor- and AddOn depended sub folders.
These parameters are completely independent from PARAC.
The INA files contain SECTIONS and PARAMETERS as we know it from the
Windows INI format. The INA files can be modified with any ASCII or ANSI
editor.
A converter program named "KCONF.EXE" (located in
"C:\PROTOPAS\CONF") converts the ’INA’ format to ’RCK’ format. The RCK
format can be used by "CCRCCONV.EXE" for the Registry update procedure.
During the installation, comfortable batch routines do the job to update the "INA"
contents automatically.
After J/Install installation the sub folders like \BAS, \BATCH, etc. located
in "C:\PROTOPAS\CONF" will not be used any more during the runtime.

ProCash/NDC parameters
The following table gives a short description about the configuration files and
batch routines that are compressed in file update.z on the Update Disk:
Table 22: List of files in sub folder \BAS
FILE NAME DESCRIPTION

CONV-ALL.BAT Batch program which is called during the installation. The batch program
updates the registry with all INA files of directory ’C:\PROTPAS\CONF’ using
the batch files described in this table. After the call this file will be renamed to
’CONV-ALL.OK’
CONV.BAT 1. Calls KCONF.EXE to convert *.INA files to *.RCK
2. Calls CCRCCONV.EXE which uses *.RCK
CONV.BAT can be used to update one particular INA file if you call CONV.BAT
with one INA file as the parameter (without extension).
Example: CONV ccerrmap
CCERRMAP.INA Parameters of CSC-W32 error codes and NDC/DDC error mapping table
LYNXSOP.INA Rear balancing step table (header only)
PRTMACRO.INA Parameter definition for macro settings in the printer ’INIT’ phase (see
Protopas "Programmers Reference" for detailed description)
PRTMACRO.BAT Calls KCONF and CCRCCONV to update parameters from PRTMACRO.INA.
LOGON.INA Parameters for automatic logon
LOGON.BAT Calls KCONF and CCRCCONV to update parameters from LOGON.INA.
CSCW32.INA Parameters to be set for CSCW32.
CSCW32.BAT Calls KCONF and CCRCCONV to update parameters from CSCW32.INA.
SMI30.INA Parameters to be set for SMI30
SMI30.BAT Calls KCONF and CCRCCONV to update parameters from SMI30.INA
PROVIEW.INA Parameters to be set for the ProAgent.
PROVIEW.BAT Calls KCONF and CCRCCONV to update parameters from PROVIEW.INA.
CCCDMFW.INA Parameters for CDM service of Protopas
CCCDMFW.BAT Calls KCONF and CCRCCONV to update parameters from CCCDMFW.INA.
NDC.INA Parameters of NDC message protocol
NDC.BAT Calls KCONF and CCRCCONV to update parameters from NDC.INA.
CCERRDIF.BAT Used by Configuration Manager only
CFGMANAG.LNK Connection to the Configuration Manager to call it from the Start Menu
DATADICT.INA Variable definitions needed for the data dictionary framework
NDCSOPDIA.CFG Dialog definitions for ProTopas/SOP-NDC
NDCSOPSTP.CFG Step definitions and common parameters for ProTopas/SOP-NDC
NDCSOPTXT.CFG SOP Text definitions for ProTopas/SOP-NDC
CCSOPSTEP.BAT Calls KCONF and CCRCCONV to update parameters of *.CFG files
GDI_PRT.INA Parameters needed for GDI printing
GDI_PRT.BAT Calls KCONF and CCRCCONV to update parameters from GDI_PRT.INA
WOSAKEYS.INA Key definitions for FDK’s, EPP and PIN Pad
NDCSOPSKE.INA Secure Key Entry configuration for ProTopas/SOP-NDC

NDCSOPSKE.BAT Calls KCONF and CCRCCONV to update parameters from

NDCSOPSKE.INA
NDCSOPBKE.INA Basic Key Entry configuration for ProTopas/SOP-NDC
NDCSOPBKE.BAT Calls KCONF and CCRCCONV to update parameters from
NDCSOPBKE.INA
UNI-CHAR.REG Default character sets for Unicode journal logging
Table 23: List of files in sub folder \BATCH

ADDONCHK.BAT Calls utility ADDONCHK.EXE
RM2.BAT Called on systems with Recycling Module 2 if CashIn is enabled
CCD.BAT Called on systems with CCDM if CashIn is enabled
CDM.BAT Called if the system has a Cash Dispenser
CHQ.BAT Called on systems with CCDM if Cheque In is enabled
CRS.BAT Called on CRS systems
COINOUT.BAT Called on systems with integrated CoinOut module
COININ.BAT Called on systems with integrated CoinIn module
EMV.BAT Called if AddOn ProChip/EMV will be installed
EPP.BAT Called for some EPP specific configuration
P36.BAT Called if AddOn ProCash/Signature will be installed
REGF.DEF Definition file for ADDONCHK.EXE
VERS.DEF Definition file for ADDONCHK.EXE
RKL.BAT Called if AddOn ProRkl will be installed
RXE.BAT Called if an CRS 3100xe is found
WEB.BAT Called if AddOn WEB-Extensionswill be installed
FLOWEXT.BAT Called if AddOn ProTopas flow extensions will be installed
WN.BAT Called on Wincor Nixdorf hardware platforms
NCR.BAT Called on NCR hardware platforms
NCRUSB.BAT Called on NCR hardware platforms that have USB printer devices
NCRF.DEF Definition file for ADDONCHK.EXE
DIEBOLD.BAT Called on Diebold hardware platforms
NAUTILUS.BAT Called on Nautilus-Hyosung hardware platforms
GRG.BAT Called on GRG hardware platforms
Table 24: List of files in sub folder \CDM

WOSALATM.INA Parameters for logical WOSA CDM service
WOSALATM.BAT Calls KCONF and CCRCCONV to update parameters from WOSALATM.INA.

Table 25: List of files in sub folder \CCD

NDCCDMDIA.CFG Specific dialog configuration for CCDM of ProTopas/SOP-NDC
NDCCDMSTP.CFG Specific step configuration for CCDM of ProTopas/SOP-NDC
NDCCDMTXT.CFG Specific Text configuration for CCDM of ProTopas/SOP-NDC
NDCCRSDIA.CFG Specific dialog configuration for CRS + CCDM of ProTopas/SOP-NDC
NDCCRSSTP.CFG Specific step configuration for CRS + CCDM of ProTopas/SOP-NDC
NDCCRSTXT.CFG Specific Text configuration for CRS + CCDM of ProTopas/SOP-NDC
LYNXCAIN.INA CashIn step table (script) for ProTopas CashIn transaction framework
NDCCRS.INA Parameters with CRS extensions of NDC message protocol
Table 26: List of files in sub folder \CHQ

NDCCDMDIA.CFG Specific dialog configuration for CCDM of ProTopas/SOP-NDC
NDCCDMSTP.CFG Specific step configuration for CCDM of ProTopas/SOP-NDC
NDCCDMTXT.CFG Specific Text configuration for CCDM of ProTopas/SOP-NDC

Table 27: List of files in sub folder \CRS

CCERRMAP.911 Specific error mapping table for DDC 911 protocol including CRS extensions
CCERRMAP.INA Specific error mapping table including CRS extensions
NDCCRS.INA Parameters with CRS extensions of NDC message protocol
Table 28: List of files in sub folder \EMV

EMVDECRE.INA Parameters for EMV
EMVDECRE.BAT Calls KCONF and CCRCCONV to update parameters of EMVDECRE.INA

Table 29: Error class files of folder \CCERRMAP
SUB FOLDER DESCRIPTION

\BASIC Basic set of error class files
\COININ Specific set of error class files for coinin
\COINOUT Specific set of error class files for coinout
\CCD Specific set of error class files for CCDM
\RM2 Specific set of error class files for RM2 (PC4000)
\CDM Specific set of error class files for cash dispenser
\CRS Specific set of error class files for CRS (PC3100)
Table 30: List of files in sub folder \WEB\CONF

ACTIVEX.INA Parameters for ActiveX controls of WEB-Extensions
WEB_ONL.REG Additional parameters required for WEB-Extensions
Table 31: List of files in sub folder \WN

MV_CONF.BAT Specific batch file that contains vendor specific programs or batch routines
Table 32: List of files in sub folder \NCR\XFS30

MV_CONF.SAV Saved batch file that can be modified for specific programs or batch routines
CCCDMFW.INA Specific dispenser settings required on NCR hardware platforms
CCERRNCR.INA Specific error mapping table required for NCR WOSA
CCSOPNCR.INA Specific SOP modifications for ProTopas/SOP-NDC for NCR
PRTMANCR.INA Specific macro mappig table rewquired for NCR WOSA
WOSA-NCR.REG Specific modifications for NCR WOSA
WOSA-NCR.SAV Saved REG files contains some default parameters preconfigured
Table 33: List of files in sub folder \DIEBOLD\XFS30

CCCDMFW.INA Specific dispenser settings required on diebold hardware platforms
CCERRDIB.INA Specific error mapping table required for Diebold WOSA
CCSOPDIB.INA Specific SOP modifications for ProTopas/SOP-DDC for Diebold
PRTMADIB.INA Specific macro mappig table rewquired for Diebold WOSA
WOSA-DIB.REG Specific modifications for Diebold WOSA

Table 34: List of files in sub folder \FLX

flxScheme.ina General Scheme parameters
flxScheme.1366 Scheme for resolution 1366x768
flx.bat Batch file for INA configuration files to process
flx.ina PTFLEX configuration file with general parameters
flxada.INA Configuration file for ADA voice control
flxddc.ina DDC specific parameters
flxndc.ina NDC specific parameters
flxop_eng.ina Operation Code Buffers function mapping for english language
flxop_ger.ina Operation Code Buffers function mapping for german language
flxop_spa.ina Operation Code Buffers function mapping for spanish language
flxprinter.ina Printer parameters
flxtext.ina General text parameters
flxtext_eng.ina Specific text parameters for english language
flxtext_ger.ina Specific text parameters for german language
flxtext_spa.ina Specific text parameters for spanish language
flxtrace.ina Parameters to enable Java Script traces
flxtext_ger_uni.reg Unicode parameters for german language
Table 35: List of files in sub folder \ETS

ets.ina Configuration for ETS (Encrypting Touch Screen) systems (e.g. C2020)
ets.bat Batch file for INA configuration file to process

ProCash/DDC parameters
The following table gives a short description about the configuration files and
batch routines that are compressed in file update.z from the Update Disk:
Table 36: List of files in sub folder \BAS

CONV-ALL.BAT Batch program which is called during the installation. The batch program
updates the registry with all INA files of directory ’C:\PROTPAS\CONF’ using
the batch files described in this table. After the call this file will be renamed to
’CONV-ALL.OK’
CONV.BAT 1. Calls KCONF.EXE to convert *.INA files to *.RCK
2. Calls CCRCCONV.EXE which uses *.RCK
CONV.BAT can be used to update one particular INA file if you call CONV.BAT
with one INA file as the parameter (without extension).
Example: CONV ccerrmap
LYNXSOP.INA Rear balancing step table (header only)
PRTMACRO.INA Parameter definition for macro settings in the printer ’INIT’ phase (see
Protopas "Programmers Reference" for detailed description)
PRTMACRO.BAT Calls KCONF and CCRCCONV to update parameters from PRTMACRO.INA.
LOGON.INA Parameters for automatic logon
LOGON.BAT Calls KCONF and CCRCCONV to update parameters from LOGON.INA.
CSCW32.INA Parameters to be set for CSCW32.
CSCW32.BAT Calls KCONF and CCRCCONV to update parameters from CSCW32.INA.
SMI30.INA Parameters to be set for SMI30
SMI30.BAT Calls KCONF and CCRCCONV to update parameters from SMI30.INA
PROVIEW.INA Parameters to be set for the ProAgent.
PROVIEW.BAT Calls KCONF and CCRCCONV to update parameters from PROVIEW.INA.
CCCDMFW.INA Parameters for CDM service of Protopas
CCCDMFW.BAT Calls KCONF and CCRCCONV to update parameters from CCCDMFW.INA.
DDC.INA Parameters of DDC message protocol
DDC.BAT Calls KCONF and CCRCCONV to update parameters from DDC.INA.
CAS_SCR.INA Default screens for Countinous Availability (CAS) for DDC
CAS_SCR.BAT Calls KCONF and CCRCCONV to update parameters from CAS_SCR.INA.
CCERRDIF.BAT Used by Configuration Manager only
CFGMANAG.LNK Connection to the Configuration Manager to call it from the Start Menu
DATADICT.INA Variable definitions needed for the data dictionary framework
DDCSOPDIA.CFG Dialog definitions for ProTopas/SOP-DDC
DDCSOPSTP.CFG Step definitions and common parameters for ProTopas/SOP-DDC
DDCSOPTXT.CFG SOP Text definitions for ProTopas/SOP-DDC
GDI_PRT.INA Parameters needed for GDI printing
GDI_PRT.BAT Calls KCONF and CCRCCONV to update parameters from GDI_PRT.INA
WOSAKEYS.INA Key definitions for FDK’s, EPP and PIN Pad

DDCSOPSKE.INA Secure Key Entry configuration for ProTopas/SOP-DDC

DDCSOPSKE.BAT Calls KCONF and CCRCCONV to update parameters from
DDCSOPSKE.INA
DDCSOPBKE.INA Basic Key Entry configuration for ProTopas/SOP-DDC
DDCSOPBKE.BAT Calls KCONF and CCRCCONV to update parameters from
DDCSOPBKE.INA
UNI-CHAR.REG Default character sets for Unicode journal logging
Table 37: List of files in sub folder \BATCH

ADDONCHK.BAT Calls utility ADDONCHK.EXE
RM2.BAT Called on systems with Recycling Module 2 if CashIn is enabled
CCD.BAT Called on systems with CCDM if CashIn is enabled
CDM.BAT Called if the system has a Cash Dispenser
CHQ.BAT Called on systems with CCDM if Cheque In is enabled
CRS.BAT Called on CRS systems
COINOUT.BAT Called on systems with integrated CoinOut module
COININ.BAT Called on systems with integrated CoinIn module
EMV.BAT Called if AddOn ProChip/EMV will be installed
P36.BAT Called if AddOn ProCash/Signature will be installed
REGF.DEF Definition file for ADDONCHK.EXE
VERS.DEF Definition file for ADDONCHK.EXE
RKL.BAT Called if AddOn ProRkl will be installed
RXE.BAT Called if an CRS 3100xe is found
WEB.BAT Called if AddOn WEB-Extensionswill be installed
WN.BAT Called on Wincor Nixdorf hardware platforms
FLOWEXT.BAT Called if AddOn ProTopas flow extensions will be installed
NCR.BAT Called on NCR hardware platforms
NCRUSB.BAT Called on NCR hardware platforms that have USB printer devices
NCRF.DEF Definition file for ADDONCHK.EXE
DIEBOLD.BAT Called on Diebold hardware platforms
NAUTILUS.BAT Called on Nautilus-Hyosung hardware platforms
GRG.BAT Called on GRG hardware platforms
Table 38: List of files in sub folder \CDM

WOSALATM.INA Parameters for logical WOSA CDM service
WOSALATM.BAT Calls KCONF and CCRCCONV to update parameters from WOSALATM.INA.

Table 39: List of files in sub folder \CCD

DDCCDMDIA.CFG Specific dialog configuration for CCDM of ProTopas/SOP-DDC
DDCCDMSTP.CFG Specific step configuration for CCDM of ProTopas/SOP-DDC
DDCCDMTXT.CFG Specific Text configuration for CCDM of ProTopas/SOP-DDC
DDCCRSDIA.CFG Specific dialog configuration for CRS + CCDM of ProTopas/SOP-DDC
DDCCRSSTP.CFG Specific step configuration for CRS + CCDM of ProTopas/SOP-DDC
DDCCRSTXT.CFG Specific Text configuration for CRS + CCDM of ProTopas/SOP-DDC
Table 40: List of files in sub folder \CHQ

DDCCDMDIA.CFG Specific dialog configuration for CCDM of ProTopas/SOP-DDC
DDCCDMSTP.CFG Specific step configuration for CCDM of ProTopas/SOP-DDC
DDCCDMTXT.CFG Specific Text configuration for CCDM of ProTopas/SOP-DDC
Table 41: List of files in sub folder \CRS

CCERRMAP.911 Specific error mapping table for DDC 911 protocol including CRS extensions
CCERRMAP.INA Specific error mapping table including CRS extensions
Table 42: List of files in sub folder \EMV

EMVDECRE.INA Parameters for EMV
EMVDECRE.BAT Calls KCONF and CCRCCONV to update parameters of EMVDECRE.INA
Table 43: List of files in sub folder \WEB\CONF

ACTIVEX.INA Parameters for ActiveX controls of WEB-Extensions

WEB_ONL.REG Additional parameters required for WEB-Extensions
Table 44: List of files in sub folder \WN

MV_CONF.BAT Specific batch file that contains vendor specific programs or batch routines
Table 45: List of files in sub folder \NCR\XFS30

MV_CONF.SAV Saved batch file that can be modified for specific programs or batch routines
CCCDMFW.INA Specific dispenser settings required on NCR hardware platforms
CCERRNCR.INA Specific error mapping table required for NCR WOSA
CCSOPNCR.INA Specific SOP modifications for ProTopas/SOP-NDC for NCR
PRTMANCR.INA Specific macro mappig table rewquired for NCR WOSA
WOSA-NCR.REG Specific modifications for NCR WOSA
WOSA-NCR.SAV Saved REG files contains some default parameters preconfigured
Table 46: List of files in sub folder \DIEBOLD\XFS30

CCCDMFW.INA Specific dispenser settings required on diebold hardware platforms
CCERRDIB.INA Specific error mapping table required for Diebold WOSA
CCSOPDIB.INA Specific SOP modifications for ProTopas/SOP-DDC for Diebold
PRTMADIB.INA Specific macro mappig table rewquired for Diebold WOSA
WOSA-DIB.REG Specific modifications for Diebold WOSA

Table 47: List of files in sub folder \FLX

flxScheme.ina General Scheme parameters
flx.bat Batch file for INA configuration files to process
flx.ina PTFLEX configuration file with general parameters
flxada.INA Configuration file for ADA voice control
flxddc.ina DDC specific parameters
flxndc.ina NDC specific parameters
flxop_eng.ina Operation Code Buffers function mapping for english language
flxop_ger.ina Operation Code Buffers function mapping for german language
flxop_spa.ina Operation Code Buffers function mapping for spanish language
flxprinter.ina Printer parameters
flxtext.ina General text parameters
flxtext_eng.ina Specific text parameters for english language
flxtext_ger.ina Specific text parameters for german language
flxtext_spa.ina Specific text parameters for spanish language
flxtrace.ina Parameters to enable Java Script traces
flxtext_ger_uni.reg Unicode parameters for german language
Table 48: List of files in sub folder \ETS

ETS.INA Parameters for ETS (Encrypting Touch Screen) like touch sones and pictures
(e.g. C2020)
ETS.BAT Batch file for INA configuration file to process

Parameter Management Customize Error Mapping Table CCERRMAP
Customize Error Mapping Table CCERRMAP

Some of the most important customizing parameters are the NDC/DDC error
mapping definitions for CSC-W32 error codes, WOSA return codes and at least
the ProCash/NDC or ProCash/DDC (LYNX) errors. The file ’CCERRMAP.INA’
contains all these error mapping definitions. This file can be customized with
any standard ASCII or ANSI text editor. To update the CCERMAP.INA after
modification you should use CONV.BAT as described in the previous table.
The following table shows a single parameter block of one error:
Table 49: Error parameter block of CCERRMAP
PARAMETER DESCRIPTION
[CLASS\643A\0002_ERROR] CSC-W32 or LYNX Error class and error code section
TD_STATUS [1] Transaction Device status (see underlined Note)
SEVERITY [1] Error Severity
[1]
M_STATUS Maintenance Status
M_DATA [1] Maintenance Data (see section “Variables in M-Data status
field” on page 327)
REBOOT Reboot flag. System reboots if this error occurs and flag is 1
SYSMSG_NUMBER See section [TOPMSG] in CUSTOM.PPF for definition
[2]
DDC_STATUS Diebold 911 or 912 status code
DDC_MDS_STATUS [2] Diebold MDS i series status (see section “Variables in MDS i
series status:” on page 326
INFO Error short description. This description can be journaled
(TOPMSG) via variable $DCMC_DEVICE_ERROR_INFO$
[1] used by ProCash/NDC only

[2] used by ProCash/DDC only
For ProCash/NDC the TD-Status of solicited cash dispenser status

messages can be modified by the application during runtime. In case
the number of notes dispensed field is ZERO, the TD-Status is set to
’2’ and for Card before Cash (FC ’A’) the value is set to ’4’.
(CCERRMAP entry of TD_STATUS remain unchanged).
See ProCashNDC or ProCash/DDC User Guide for detailed descrip-
tions of NDC or DDC status fields. The CSC-W32 error codes are
described in the System Messages manual of CSC-W32.
Refer also to manual Error Mapping Cross Reference Tables for
NDC and DDC status codes.

Configure multiple CDM Error Reasons for DDC
For cash dispenser errors (only) you can define multiple Error Reasons for the
DDC911/912 status and DDC MDS i series status. The background why
multiple error reason configuration for some errors is neccessary can be
declared as follows:
In some cash dispenser error situations just the pure controller status will be
sent up via an error event to the application without logic in what function the
error has occurred. So, there could be situations where the same CSC-W32
error is sent up after a:
1. General dispense error (first entry)
2. Cassette pick failure (second entry)
3. Money present function with consumer access (third entry)
4. Money present function without consumer access (fourth entry)
That means for the ProCash/DDC application, that for the same CSC-W32 error
4 different DDC911/912 and DDC MDS i series status codes needs to be
configured. This parameterisation is optionally and can be used for those errors
where it is required.
Example: Assume you need to configure for CSC-W32 extended error
001D\1028 multiple 911/912 and MDS status codes.
The entries can be set as follows:
DDC_STATUS = "?3002,?0B75,@04,@00"
DDC_MDS_STATUS = "000DI01:3F:00:01,000DI01:3F:31p37,
000DR01:3A:41:40,000DR01:3A:37:41"
Note: The different status codes have to be configured as a comma

separated list, where the first 911/912 error code in the list
corresponds to the first MDS status code, the second 911/912 error
code to the second MDS status code, and so on.
It is only allowed to configure all 4 error codes or just 1 error code.

Variables in MDS i series status:
This section describes the field variables of parameter DDC_MDS_STATUS,

which are replaced by ProCash/DDC at runtime if the parameter
STATUS_CODE_HANDLING is set to ’0’. See the following figures for the
meaning of the variables:
a) money low (m, n) or money out (M, N)
DDC_MDS_STATUS = "000DI01:2D:0m:0n"
DDC_MDS_STATUS = "000DI01:3D:0M:0N"
cassette type E-H

cassette type A-D
see NOTE
replaced with the function ID index
b) feed failure for specific cassette

DDC_MDS_STATUS = "000DI01:3F:31p37"
value varies on physical cassette position 1-4.

replaced as ':' from DDC-Emulation
if last digit gets zero this value is added plus one
see NOTE
replaced with the function ID index
'I' is set to 9 if the error has to be sent as a solicited status message.
Example 1: money low

If denomination D and E are low, ProCash/DDC sends following MDS status:
000D901:2D:08:01
Example 2: money out

If denomination C and F are low, ProCash/DDC sends following MDS status:
000D901:3D:04:02
Example 3: pick error

If the second physical cassette has a pick error, ProCash/DDC sends following
MDS status: 000D901:3F:31:38

Cassette specific variable in DDC912 status:
This section describes the variable that can be set if the specific DDC912 error
code is cassette specific. The variable set in parameter DDC_STATUS is
replaced by ProCash/DDC at runtime.
The following parameter value contains the specific error code ’B7’, which is
replaced to the number that represents the physical cassette position.
DDC_STATUS = "?0B75"
If for example the third cassette gets an error during a dispense, ProCash/DDC
replaces the B7 to 19. The DDC912 error code ?0195 is sent to the host.
Variables in M-Data status field
This section describes the field variables of parameter M_DATA, which are
replaced by ProCash/NDC during runtime. See the following figure for the
meaning of the variables:
M_DATA = "XXCCPPPPPPPPXXXXXXXXXXXXXXXXXX"
cassette type 4 (see Note 1)

cassette type 2, 1 are low (see Note 2)

cassette type 4, 3 are low (see Note 2)
only if value 00; 01 or 02 is set, the
cassette low or pick failure fields are
updated !!!
"PP" can be replaced with the pick error code for all four cassette
types. Depending on which position the error occurs only the error
code of one cassette type will be sent to the network. All other fields
are set to zero.
Value "C" is updated by ProCash/NDC.

Error Class mapping of CSC-W32 and XFS classes
CSC-W32 generates several error classes that cannot be mapped to an NDC

or DDC device class, the same has to be done for some XFS error classes.
Therefore the Device Status Framework (dcDevSta.dll) assigns those errors to
a valid NDC or DDC device class. See also contents of the Error Mapping Table
CCERRMAP.INA located in "C:\PROTOPAS\CONF".
Please refer to the "System Messages" manual of CSC-W32 for detailed

error description of error CSC-W32 error classes.
The following table illustrates which CSC-W32 and XFS error classes are
currently assigned to the internal generated device class.
Table 50: CSC-W32 and XFS class assign table
CSC-W32 class Assigned Device description

Class
0005 (V.24 comm.) 0008 Card Reader
0003 (USB comm.) AA08
0005 (V.24 comm.) 0033 Journal printer
0032 (global PRT class
0005 (V.24 comm.) 0038 Receipt printer
0032 (global PRT class)
0005 (V.24 comm.) 0039 Document printer
0032 (global PRT class)
0005 (V.24 comm.) 0018 Cash dispenser (CDM)
0005 (V.24 comm.) 0017 Deposit module
0003 (USB comm.) AA18_CIN CRS (CashIn)
0005 (V.24 comm.) 0018_CIN
0018 (CDM basic error) 0018_CIN
001D (CDM extended error) 001D_CIN
0003 (USB comm.) CC1A CCDM (CashIn)
0004 (IEEE 1394 class) BB1A
0005 (V.24 comm.) EE1A
0003 (USB comm.) DD1A CCDM (Cheque In)
0004 (IEEE 1394 class) AA1A
0005 (V.24 comm.) FF1A
005A (RM2) 005A_CIN RM2 (CashIn)
005E (RM2) 005E_CIN RM2 (CashIn)

00B9 (XFS 2.0 CDM errors) 00B9_CIN CRS (CashIn)

6752 (XFS 3.0 CDM errors) 001D CDM (CashOut)
6751 (XFS 3.0 CRS errors) 001D CRS (CashOut)
Error mapping of XFS30 (WOSA) error events
Some error events generated from the XFS30 layer, especially from the cash
dispenser and cash recycler service, are necessarily remapped internally to an
existing CSC-W32 StClass and StCode by the Device Status framework
(dcDevSta.dll).
The following table illustrates which XFS30 classes and error codes are
currently remapped.
Table 51: XFS30 - CSC-W32 class assign table
XFS30 Assigned XFS30 Assigned Involved XFS Service

class CSC-W32 code range CSC-W32
class code range
6751 001D Dxxx 1xxx PSCDM30 (Cash Dispenser Service)
6752 001D Dxxx 3xxx PSCRS30 (Cash Recycler Service)
Error Suppression
During the runtime ist can happen that one of the application level generates
error codes which have no influence to the device operation. Those errors are
just non relevant warnings. To prevent confusions by the service operators the
Device Status Framework (dcDevSta.dll) ignors error A200 (Software Error) of
class 0018 (class Cash Dispenser).
Furthermore for specific errors you can configure in CCERRMAP.INA to
suppress sending a message to the host and displaying the error on the SOP
panel if you set parameter SEVERITY = "0" and TD_STATUS = "0".
For ProCash/DDC you can suppress sending an error to the host if you set
parameter DDC_STATUS = "" (as empty value) in the requested error section.

Parameter Management Configure DDC 911 protocol
Configure DDC 911 protocol

This section describes how to setup ProCash/DDC to run in Diebold 911 mode.
The default configuration of ProCash/DDC is based on DDC 912 mode.
The following actions have to be completed to run in Diebold 911 mode:
• Use ’CCERRMAP.INA’ for 911 mode
• Setup hardware configuration status fields for 911 mode
• Dispenser configuration for HI and LO denomination bills
Use ’CCERRMAP.INA’ for 911 mode
ProCash/DDC will be delivered with a predefined error mapping file named

’CCERRMAP.911’.
After the installation you will find this file in ’C:\PROTOPAS\CONF’.
To use the Diebold 911 specific device status you have to fill the CCERRMAP
section of the WINNT Registry with the contents of ’CCERRMAP.911’ in the
following way:
1. Rename the existing ’CCERRMAP.INA’ to ’CCERRMAP.912’ in directory
’C:\PROTOPAS\CONF’
2. Copy ’CCERRMAP.911’ to ’CCERRMAP.INA’
3. Call the batch job ’CONV CCERRMAP’
Setup hardware configuration status fields for 911 mode
To set the hardware configuration for Diebold 911 mode you have to set the
following parameters in ’CUSTOM.PPF’:
Section in *.PPF: [PROTOCOL\DDC\T2HHWConfigurationStatus]
Parameters: PREP_FIELD_22 = PREP_FIXED,0C
NUM_FIELDS = 27
The value ’0C’ for parameter PREP_FIELD_22 represents

denomination C and D in the hardware configuration status info.

Dispenser configuration for HI and LO denomination bills
The cash dispenser configuration for Diebold 911 mode can be done via the
installation dialog or the direct setting in ’CUSTOM.PPF’. For 911 mode there
are only two denominations possible (HI and LO indication). Therefore you have
to set following parameters:
Parameters: NUM_LOG_CASS = 2
CURRENCY_1 = "USD"
VALUE_1 = 10
CURRENCY_2 = "USD"
VALUE_2 = 20
The first denomination (’CURRENCY_1’ and ’VALUE_1’) indicates

the HI denomination. The second denomination (’CURRENCY_2’
and ’VALUE_2’) indicates the LO denomination (the currency and
value entry are examples only).
To enable the full Diebold 911 compatible mode you have to set
parameter DDC_NINE_ELEVEN_DENOM, and you need to
configure CURRENCY_3, CURRENCY_4 and VALUE_3, VALUE_4.
Please refer to section ”Diebold 911 compatible HI and LO denomi-
nation mode” on page 332 for details.

Diebold 911 compatible HI and LO denomination mode
In the standard Diebold 911 protocol the LO and HI denominations are

represented as letter C and letter D, where the LO denomination is assigned to
letter C and the HI denomination is assigned to letter D.
To enable the Diebold 911 compatible mode, the following parameter has to be
set:
Parameter name: DDC_NINE_ELEVEN_DENOM
Valid range: 0, 1
Value description: 0 - compatible mode disabled
1 - compatible mode enabled
If the parameter DDC_NINE_ELEVEN_DENOM is set,

the parameters CURRENCY_x and VALUE_x of section
[CASH_DISENSER] have to be set as follows:
Parameters: NUM_LOG_CASS = 4
CURRENCY_3 = "USD"
VALUE_3 = 10
CURRENCY_4 = "USD"
VALUE_4 = 20

Specific Step for dispense FID ’8’ in 911 Mode
If ProCash/DDC should work in 911 Mode, you have to configure step

"DC_F_DISPENSE_911" for dispense FID ’8’. In case of a present/retract
failure, this function sends a solicited message to the central.
You can setup this step in configuration file CUSTOM.PPF.
Section in *.PPF: [FUNC_ID_MAP]
Parameter: STEP_NAME_X[1] = "DC_F_DISPENSE_911"
[1] X = represents the number that has to correspond to parameter

REPLY_ID_X, where FID ’8’ is configured.

Parameter Management Printer initialisation via macro tables
Printer initialisation via macro tables

This section describes parameters which can be used to send specific printer
control sequences to the receipt or/and journal printer during the startup phase.
The control sequences can be taken from the printer specification manuals.
Within Protopas it is possible to setup user defined macro tables with your own
defined control sequences. With user defined macros you are able to send any
control sequence (which is supported) to the printers in the startup phase that
you need for your environment.
The following parameters can be set in configuration file "PRTMACRO.INA"
located in "C:\PROTOPAS\CONF".
Macro parameters for Journal and Receipt printer
[Wincor Nixdorf\ProTopas\CurrentVersion\CCOPEN\JOURNAL]
[Wincor Nixdorf\ProTopas\CurrentVersion\CCOPEN\RECEIPT]
Macro sub section

Parameter name: MACRO_TABLE
Parameter values: JOURNAL_MACROS
RECEIPT_MACROS
Value description: specifies the sub section name that is appended to
..\CCOPEN\CCPRTFW\
The sub section specifies the location of the macro
parameters
Macro activation
Parameter name: MACRO_TABLE_ACTIVE
Value Range: 0, 1
Value description: Activates or deactivates the user defined macro
table.
Default value: 0

Macro interpretation
Parameter name: HALF_DOUBLE_NUMBER_SIGNS
Value Range: 0, 1
Value description: 0 - two ## are reduced to one # or #MACRO# is
interpreted as a macro;
1 - two ## characters are printed has normal
characters and will not be interpreted as a macro.
This parameter usually has to be enabled if the Protopas environment is running
on an NCR or Diebold ATM where no CSCW32 application is installed.
Default value: 0
Printer INIT
Parameter name: INIT
Value Range: any legal macro name
Value description: This parameter can be used to send additional
macro sequences to the printer during printer
initialisation in the startup phase.
Default value: ""
Example:
If you like to enable variable receipt length and no black dot mark recognition
for the Receipt printer, you have to set the following:
INIT = #VLM##MRKC#

User defined Macros
The user defined macros for each printer type has to be defined in the sub
section that is defined via parameter "MACRO_TABLE".
Example:
If you like to set a specific initialisation sequence for the ND9A or ND9E, the
entries could be the following:
[Wincor Nixdorf\ProTopas\
CurrentVersion\CCOPEN\CCPRTFW\RECEIPT_MACROS]
USERINIT = "1b2b011b5834001b76"
"USERINIT" is any macro name.

The value are the control sequences supported by ND9A or ND9E.
1b2b01 = data request
1b583400 = cancel
1b76 = send status to application
Now the parameter "USERINIT" has to be set as macro #USERINIT# in section:

INIT = "#USERINIT#"

Configurable ESC xx mapping to Macros
The following parameter can be used to assign printer macros to specific

escape control sequences which are sent in the print data buffer of the NDC or
DDC host reply.
This feature is supported for following ESC sequences:
ProCash/NDC
ESC p - prints a Cheque Image
ProCash/DDC
ESC R - prints Cheque Image front side
ESC r - prints Cheque Image back side
ESC Q - prints a configurable part of a Cheque Image
Parameter name: ESC_xxn[1]

Section: ..\LYNXPAR\PRINTER\RECEIPT
..\LYNXPAR\PRINTER\DOCUMENT
..\LYNXPAR\PRINTER\JOURNAL
Value range: valid macro sequence
Description: This parameter can be used to set a macro sequence
which will be inserted in the PrintRaw data stream
when the specifc ESC sequence as listed above is
detected.
[1] XX = hex value of the character after the ESC sign.
n = additional mandator or optional parameters which are additonaly
appended.
Examples:
ESC_51 = "%DATDICT_VAR%" (ESC Q)
ESC_52020 = "#PIC:WHITEF.JPG#" (ESC Rxxx)
ESC_72020 = "#PIC:WHITEB.JPG#" (ESC rxxx)
ESC_7000 = "#PIC:WHITEF.JPG#" (pxx) xx = front with codeline unchanged
ESC_7001 = "#PIC:WHITEF.JPG;PRT_IMG.JPG,BLACKEND#"
(pxx) xx = front codeline blackend
ESC_7002 = "#PIC:WHITEF.JPG;PRT_IMG.JPG,REMOVED#"
(pxx) xx = front codeline removed
ESC_7010 = "#PIC:WHITEB.JPG#" (pxx) xx = back
ESC_7000001 = "#PIC:GREENF.JPG#"
(pxxxxx) xxxxx = front with codeline type index 001

Parameter Management Enable/Disable Secure Key Entry (SKE) mode
Enable/Disable Secure Key Entry (SKE) mode

Secure Key Entry mode SOP function is activated as default (changed with
version 3.1/20). The configuration file NDCSOPSKE.INA / NDCSOPBKE.INA
for NDC or DDCSOPSKE.INA / DDCSOPBKE.INA for DDC and the belonging
batch routines are stored in folder C:\PROTOPAS\CONF. The configuration
update can be performed via the
"Configuration Manager" using menu "Update", "Update INA or REG files"
select the required INA file and press the Update button. You can also use the
command prompt if you call the batch routine NDCSOPSKE.BAT /
NDCSOPBKE.BAT or DDCSOPSKE.BAT / NDCSOPBKE.BAT.
Enable Triple DES operation

This section describes how to configure Triple DES operation for ProCash/NDC
and ProCash/DDC.
Triple DES enabled via J/Install installation
Triple DES operation is activated during J/Install installation using parameter

"DOUBLE_LENGTH_KEYS" set to "10" in configuration file "CUSTOM.PPF".
This can be changed in menu "Encryption Security" of the J/Install installation
dialog.
Switch to triple or single DES via SOP
If you like to set the single or triple DES configuration via SOP, you can set up
the file SOPCOPY.TXT where executables and batch commands can be
integrated. Refer to section ”Software updates via SOP” on page 365.

Parameter Management Enable GDI Windows print
Enable GDI Windows print

Since release 1.2/10 ProCash/NDC and ProCash/DDC support GDI windows
print for receipt and document printers that can be installed as windows printers.
These printers needs to be installed as a Windows printer through a Windows
printer driver.
Following printers provided by Wincor Nixdorf can operate as Windows printers:
Printer Model Windows Name supp. Print Mode

ND9G (receipt) Wincor Nixdorf ND9G GDI only
TP07 (receipt) Wincor Nixdorf TP07 GDI / PrintRaw
TP27 (receipt) Wincor Nixdorf TP27 GDI / PrintRaw
TH21 (receipt 80 mm width) WN TH21 GDI / PrintRaw
TH22 (receipt 120 mm width) WN TH22 GDI / PrintRaw
TP23 (receipt/document) WN TH23 GDI only
TH97/G (document) Wincor Nixdorf TH97/G GDI / PrintRaw
TP01 (document) Wincor Nixdorf TP01 GDI / PrintRaw
Automatic Installation
GDI Windows printer can be automatically installed via J/Install installation. For
printers, which can operate as GDI Windows printer or in raw print mode (see
table), you have to specify the GDI mode in configuration file CUSTOM.CUS.
Refer to section ”GDI Windows name for receipt printer” on page 269 and
section ”GDI Windows name for document printer” on page 269 for detailed
description how to enable GDI windows printer. Pure GDI printer like ND9G are
installed automatically as a Windows printer.
GDI operation and configuration parameters
A detailed description of GDI operation, GDI print architecture and all possible
configuration parameters are described in ProTopas Module Construction Kit
Programming Guide Version 5.1/xx.
The document is stored as file name ProTopas_Modul Construction Kit.pdf
in folder \DOC\ProTopas\Kit\V5140 on Install CD NDC/DDC V3.1/20.

Parameter Management Enable GDI Windows print
Configuration settings for TH23 on Cineo 4090
The TH23 needs some specific configuration settings for the operation on a
Cineo 4090 system. On the Cineo 4090 system the TH23 is acting like a
document printer in the application layer. Therefore it is mandatory to specify
specific application parameters for the document print processing.
Following parameters and values are mandatory to be configured:
Required settings in GDI_PRT.INA:
[GDI_PRINTER\DOCUMENT]
PRINTER_NAME = "WN TH23"
TEXT_HEIGHT = "0"
MAX_LINES = "0"
MIN_LINES = "54"
[GDI_PRINTER\DOCUMENT\FONT_005]
MAX_LINES = "40"
TEXT_WIDTH = "2000"
TEXT_HEIGHT = "2000"
TEXT_HORZ_OFFSET = "50"
TEXT_VERT_OFFSET = "50"
Note: The above parameters will be stored in registry section:
[..\Wincor Nixdorf\ProTopas\Currentersion\
LYNXPAR\GDI_PRINTER\DOCUMENT\..]
Required settings in CUSTOM.PPF:

[DOCUMENTPRINTER]
NO_OF_DOC_BEFORE_EJECT = 1
Required settings in PROBASE.CUS:

cscw32.CSC-W.TH23_RETRACTCAPACITY = 30
cscw32.CSC-W.TH23_RETRACTHIGHTHRESHOLD = 25
cscw32.CSC-W.TH23_RETRACTTIME = 120000

Parameter Management Enable card less transactions
Enable card less transactions

The following parameters can be used to enable cardless transactions. Cardless
transactions means that consumer transactions can be initiated via inserting a
consumer card or via pressing a button on the EPP or through FDK’s. The idle
dialog will be configured as a FDK selection dialog where you can enable the
buttons via local parameters. In addition you can locally define card track data and
next state exits.
Repository configuration of CLTSTTFW.DLL
The card less transaction framework overlay CltSttFw.DLL has to be appended to

the framework(s) configured via CUSTOM.PPF parameter TRANSACT_FRAME.
Refer also to section ”Transaction framework” on page 72.
Dialog configuration parameters
The following parameters can be configured either in section

..\Wincor Nixdorf\ProTopas\Currentversion\LYNXPAR\APPLICATION]
where the parameters are valid for all screens, or in section
..\Wincor Nixdorf\ProTopas\Currentversion\LYNXCI\SCREEN\XXX]
where the parameters can be configured for each single screen.
XXX = represents the screen number subsection.
Table 52: Card less transaction parameters
IDLE_ENTER allows to start the card less transaction via pressing the Enter KEY
IDLE_CANCEL allows to start the card less transaction via pressing the Cancel KEY
IDLE_TIMEOUT specifies the TIMEOUT and the TIMEOUT NEXT STATE
IDLE_A allows to start the card less transaction via pressing the A KEY
IDLE_B allows to start the card less transaction via pressing the B KEY
IDLE_C allows to start the card less transaction via pressing the C KEY
IDLE_D allows to start the card less transaction via pressing the D KEY
IDLE_F allows to start the card less transaction via pressing the F KEY
IDLE_G allows to start the card less transaction via pressing the G KEY
IDLE_H allows to start the card less transaction via pressing the H KEY
IDLE_I allows to start the card less transaction via pressing the I KEY

Parameter fields
The parameters in table “Card less transaction parameters” on page 341 except
the parameter IDLE_TIMEOUT (see description in section ”Timeout parameter” on
page 343), use following parameter values:
Each parameter value comma separated is a separate parameter.
Table 53: Card less parameter fields
Field Range Size Description

Index
0 VAR VAR Track1 data (without start/end sentinel)
3 VAR VAR PIN block buffer

- This field can contain the PIN number in clear text format. The PIN should
NOT be padded.
- If the field is empty, no PIN buffer is sent to the host, unless one of the
following state is a PIN entry state where a PIN number has been entered.
4 0-999 3 Good next state number
5 0-999 3 Cancel exit next state
6 0-1 1 Start transaction flag

0 - using card data which are already loaded (if it isn't set in the Parameter
value list, will be used the default)
1 - using card data which are set in Track1, Track2, ... (default)
Example with predefined PIN 1234:

IDLE_ENTER = ",;5890049999999999=49121200000000000000?,,1234,510"
IDLE_A = ",;5890049999999999=49121200000000000000?,,1234,510"
Example without PIN:

IDLE_A = ",;5890049999999999=49121200000000000000?,,,510"

Timeout parameter
The parameter IDLE_TIMEOUT can be used to configure a specific timeout

handling during a card less transaction. This parameter should be configured only if
card less transaction processing should be enabled in the middle of a transaction.
These parameters specify the parameter values for the timeout handling how long
this card less transaction should be taken.
Each parameter value comma separated is a separate parameter. If this parameter

is not set, no timeout will be used.
Table 54: Parameter fields for IDLE_TIMEOUT
Field Range Size Description

Index
0 0-999 3 Timer in seconds
1 0-999 3 Timeout next state number
Example:
IDLE_TIMEOUT = "30,555"
Screen display and exit for parallel FDK press
The following parameter can be used to define a specific screen and next state
number to force control of the screen that should be displayed and the next state
number in the case a card is inserted and the consumer has pressed an FDK at the
same time.
Parameter name: CARDLESS_PARALLEL_FDK_CARD_EXIT
Section in Registry: ..\LYXPAR\APPLICATION
or ..\LYNXCI\SCREEN\xxx
Valid range: "sss,eee"
Value description: sss = Screen to display
eee = Next state exit

Parameter Management Alpha numeric SMS key input style on EPP
Alpha numeric SMS key input style on EPP

The following parameters can be set to enable alpha numeric SMS key input on
the Electronic Pin Pad (EPP). This can be used to display alpha numeric
characters on the consumer screen and to send alpha numeric letters to the
host. The technique of value input is quiet similar as it is used for mobile phones.
The alpha numeric input will be processed in the Information Entry State H.
Assign values for Left/Right keys of the ’0’ key

The following parameters can be used to specify, which alpha numeric digits are
set when the left side key or the right side key from the ’0’ key is pressed.
Parameter name: KEY_LEFT_0_CHARS

Registry Key: [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXCI\SCREEN]
Value description: specifies the digits to be padded
Default value: “” - not configured
Example value: 00
Parameter name: KEY_RIGHT_0_CHARS

Value description: specifies the digits to be padded
Example value: 000

Parameter Management Specify cursor character for input position
Dependent parameters
The following parameters are required to assign the key code 5 for the left side
key from the ’0’ key. Usually on Wincor Nixdorf systems for this key the decimal
key code is assigned be default. Please refer to the vendor specific
documentation how to assign key codes to EPP keys.
Parameter name: PINKEY_11
ProTopas\CurrentVersion\WOSAKEYS\ASC_KEY]
Valid range: numeric values
Value description: specifies the key code for the left side key
Example value: 5
Specify cursor character for input position

The following parameter is used to configure the input cursor character for the
input position o the consumer screen.
Parameter name: ALPHA_CURSOR
Value description: specifies the cursor character for the input position on the
consumer display.
Example value: <

Parameter Management Specify cursor character for input position
Specify cursor character for input position

The following parameter is used to configure the input cursor character for the
input position o the consumer screen.
Parameter name: ALPHA_CURSOR
Value description: specifies the cursor character for the input position on the
consumer display.
Example value: <
Set up character sequences for single EPP keys

The following parameter are used to configure the character sequence, which
is displayed on the consumer screen after EPP keypress.
Parameter names: ALPHA_X_SEQ[1]
Valid range: 1-4 numeric and alpha numeric digits
Value description: specifies the character sequence to display on the
consumer screen. The curser can be moved to the next
position to the right after each key press within the allowed
input time specified via parameter ALPHA_TIMER.
[1] - X = specifies the numeric key on the EPP (range 0-9)
See configuration parameter examples on the following page ...

Parameter Management Input options for SMS input (NDC only)
The following parameters specify the character sequences for the keys
0 - 9 on the EPP:
"ALPHA_0_SEQ"="0_+-"
"ALPHA_1_SEQ"="1QZ"
"ALPHA_2_SEQ"="2ABC"
"ALPHA_3_SEQ"="3DEF"
"ALPHA_4_SEQ"="4GHI"
"ALPHA_5_SEQ"="5JKL"
"ALPHA_6_SEQ"="6MNO"
"ALPHA_7_SEQ"="7PRS"
"ALPHA_8_SEQ"="8TUV"
"ALPHA_9_SEQ"="9WXY"
Input options for SMS input (NDC only)

The following parameter can be used to set specific input options that have
influence to the screen display and input.
Parameter name: INPUT_HANDLING
Valid range: 0-31
Value description: 0 - clear input field and start input from the left hand side if
maximum digits in input field has been reached
1 - ignore further inputs if amount buffer field is full
2 - ignore further inputs if numeric buffer field is full
4 - clear the last input in amount entry state using the clear
key
8 - clear the last input in information entry state using the
clear key
16 - do not show leading zeros in amount entry state
Default value: 0 - not configured

Parameter Management Dialog options for SMS input
Dialog options for SMS input

The following parameter can be used to set specific dialog options that have
influence to the screen display. This parameter can be globally set in the
SCREEN section or/and specifically in screen sub sections.
Parameter name: DIALOG_OPTIONS
Registry Keys: [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
or/and [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXCI\SCREEN\XXX] [1]
[1] - XXX = screen sub section
Valid range: 0-55
Value description: 0 - no options configured
1 - ignore horizontal and vertical offset when displaying a
picture as cursor @@
2 - auto end numeric input when length reached
4 - do not add extra space when switching to G font
(DDC only)
16 - disable alphanumeric entry
32 - wrap bottom text line overflow to the top screen line
Default value: 0 - no options configured

Parameter Management Allowed alpha numeric characters for SMS input
Allowed alpha numeric characters for SMS input

The following parameter specifies the range of characters that are allowed to be
used for alpha numeric SMS key inputs in Amount Entry State (F) and
Informatio Entry State (H).
Parameter name: KBD_ALLOW_CHARS
Valid range: string with valid alpha numeric characters
Value description: see above
Example value:
01234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ,.-;:=

Parameter Management Enable timer restart for input dialogs
Enable timer restart for input dialogs

The following parameter can be used to enable restarting the input timer after
keypress in input dialogs of Amount Entry State (F), PIN Entry State (B),
Information Entry State (H) or Enhanced Information Entry State (’@D ’) (DDC).
That means with every keypress, the consumer get a specified extra time for a
new input.
Parameter name: RESTART_TIMER_ON_KEYPRESS
Valid range: Bit order
0x01 - Amount Entry state
0x02 - Pin Entry state
0x04 - Information Entry state
0x08 - Enhanced Information Entry state
Value description: specifies for which state the input timer restart handling is
enabled.
Default value: 15 - input restart enabled for all states

Parameter Management Encrypting Touch Screen (ETS) Systems
Encrypting Touch Screen (ETS) Systems

Encrypting Touch Screen Systems do not have a ’normal’ PIN pad, but emulate
the PIN pad on the screen (like a C2020).
The touch areas / zones for such PIN pad must be configured and appropriate
pictures must be provided.
Since the C2020 uses a 16:9 landscape monitor with a resolution of 1366*768
this is pre-configured by shifting the native (or WEB) window with a resolution
of 1024*768) to the left which results in a window on the right with a resolution
of 342*768 which is used to show a virtual PIN pad or just a CANCEL button.
To provide maximum security this PIN pad ’floats’ vertically in that window
whenever a PIN entry is performed (different positions).
The following illustrates some samples.
Figure 9: ETS PIN entry

Figure 10: ETS transaction selection
Figure 11: ETS amount entry

To change the zones and pictures the following parameters can be modified
(see ETS.INA in the \PROTOPAS\CONF folder).
Parameter name: ETS_LAYOUT_xxx
Value description: specifies the layout for dialog type xxx:
FDK - Function selection dialog (e.g. state E)
PIN - PIN entry dialog (e.g. state B)
AMT - Amount entry dialog (e.g. state F)
NUM - Numeric entry dialog (e.g. state H)
ENH - Enhanced entry dialog (only DDC, state @D )
Default values: can be found in ETS.INA
The layout is defined as

"mode,swidth,sheight:frame"
mode - can be DATA for numeric, or PIN for PIN entry.
swidth - specifies the reference width resolution.
sheight - specifies the reference height resolution.
frame - specifies the frame.
The frame is defined as
"xpos,ypos,width,height,float;key1;key2;..."
xpos - left position of the frame.
ypos - top position of the frame.
width - width of the frame.
height - height of the frame.
float - indicates if the frame shall float (X-0x01 and/or Y-0x02).
key1,...- specifies the keys inside the frame.
The keys inside the frames are defined as
"keytype,xpos,ypos,width,height"
keytype - the EPP key (numeric, special and FDKs):

FK_0|...|FK_9|
FK_ENTER|FK_CLEAR|FK_CANCEL|
FK_HELP|FK_DEC|FK_RES1|
FDK01|...|FDK08
xpos - left position relative to the frame left edge.
ypos - top position relative to the frame top edge.
width - width of the key.
height - height of the key.
Frame and key coordinates are relative to metric definition of layout (swidth
and sheight).
On 16:9 (C2020) screens the reference metric should be 0 and all coordi-
nates are then specified in absolute pixel coordinates.
Parameter name: ETS_PICTURE_xxx

Value description: specifies the picture and position for dialog type lll, with lll
FDK - Function selection dialog (e.g. state E)
PIN - PIN entry dialog (e.g. state B)
AMT - Amount entry dialog (e.g. state F)
NUM - Numeric entry dialog (e.g. state H)
ENH - Enhanced entry dialog (only DDC, state @D )
Default values: can be found in ETS.INA
The picture is defined as

"path,xpos,ypos"
path - the picture path and filename.
xpos - left position in pixel.
ypos - top position in pixel.

Parameter Management Configure Dial Up communication
Configure Dial Up communication

The following parameters are used to configure dial up communication settings in
configuration file CUSTOM.PPF.
Repository section [STARTUP]
Protocol Type
The following parameter specifies the path and filename of the protocol type
specific framework that should be used by the dial up communication.
Parameter name: COMPROT1_FRAME
Default value: “C:\PROTOPAS\BIN\ProtVisa.DLL”
Modem Interface DLL
The following parameter specifies the path and filename of the framework that
communicates with the modem interface.
Parameter name: COM50_FRAME
Default value: “C:\PROTOPAS\BIN\ComModem.DLL”

Serial Interface DLL
The following parameter specifies the path and filename of the framework that
communicates with the serial interface protocol.
Parameter name: COM51_FRAME
Default value: “C:\PROTOPAS\BIN\ComSerial.DLL”
Communication Yield DLL
The following parameter specifies the path and filename of the communication
yield framework.
Parameter names: COM52_FRAME
COM53_FRAME
COM54_FRAME

Default value: “C:\PROTOPAS\BIN\ComYield.DLL”

Restart Manager section [START_APPLICATION]
Load dial up frameworks
The following parameter contains the Restart Manager command line with
frameworks that are needed to be loaded to enable the dial up environment.
Parameter name: DIAL_UP
Valid range: Parameter,Parameter,Parameter,...,...,...
Value description: Each Parameter contains a program with execution
parameters which are loaded in the specified order from left
to right.
Default value: “C:\PROTOPAS\BIN\FwLoadPm.EXE,4,1,21,,,
CCCommProtocol1 CCCommunication50
CCCommunication51 CCCommunication52
CCCommunication53 CCCommunication54"

Specific communication settings
Modem automatic dial up number
Following parameters are configured as default in CUSTOM.PPF:

Parameter name: MODEM_AUTO_NUMBER
Sections in *.PPF: [MODEM_COMMANDS]
[MODEM_EVENTS]
[MODEM_PROJECT]
[MODEM_PROJECT_ALTERNATE]

Value description: Refer to ProTopas "Host Protocol and Communication
Frameworks" Programming Guide for detailed description
Modem initialisation command
Parameter name: MODEM_CMD_CONFIG

Section in *.PPF: [MODEM_COMMANDS]
[MODEM_EVENTS]
[MODEM_PROJECT]
[MODEM_PROJECT_ALTERNATE]

Default value: “AT&F1E1X3M1”

Serial interface line attributes
Parameter name: SERIAL_LINEATTR

Section in *.PPF: [SERIAL_COMMANDS]
[SERIAL_EVENTS]
[SERIAL_PROJECT]
[SERIAL_PROJECT_ALTERNATE]

Default value: “57600,N,8,1”
Serial interface port name
Parameter name: SERIAL_PORTNAME

Section in *.PPF: [SERIAL_COMMANDS]
[SERIAL_EVENTS]
[SERIAL_PROJECT]
[SERIAL_PROJECT_ALTERNATE]

Default value: “COM1”

Project settings
COM channel
The following parameter specifies modem communication channel.

Parameter name: COM_CHANNEL
Sections in *.PPF: [PROTOCOL_PROJECT]
Default value: “50”
Protocol channel
The following parameter specifies protocol channel.

Parameter name: PROT_CHANNEL
Protocol type
The following parameter specifies the protocol type.

Parameter name: COMM_PROTOCOL
Default value: “VS2”

Route ID
This parameter specifies the Route ID.

Parameter name: ROUTE_ID
Default value: “HANCO ”
Terminal ID
This parameter is used to configure a Terminal ID.

Parameter name: TERMINAL_ID

Parameter Management Changing Network settings under restricted User
Changing Network settings under restricted User

To allow changing Windows network communication settings (e.g. TCP/IP
settings) under restricted user, you have to add the restricted user (where the
application is running) into user group "Network Configuration Operators".
Add user "Wincor" to user group "Network Configuration Operators":
To add user "Wincor" in user group "Network Configuration Operators" you have
to configure following command lines in JINSTALL.CUS:
execute.end.2.Program = {E:WINDIR}\system32\cmd.exe
execute.end.2.Parameter = /c net localgroup "Network Configuration Operators" /ADD "Wincor"
Activation with PC/E Terminal Security – Access Protection:

If you are using PC/E Terminal Security – Access Protection you have to extend
the SECURITY.SEC file. Please refer to the documentation of PC/E Terminal
Security – Access Protection for details.
Parameters for Forms printing

To enable forms printing for Receipt or/and Document printers, you need to
replace the dcPrtGdi.dll against FormsPrt.dll of the Repository Manager
configuration for the CCRecPrtFW or/and CCDocPrtFW framework. During
installation default parameters are set in sections
..\LYNXPAR\PRINTER\RECEIPT and ..\LYNXPAR\PRINTER\DOCUMENT.
Please refer to manual ProTopas Module Construction Kit Programming Guide
Version 5.1 for detailed description of parameters and functional details.

Parameter Management Rich Client Manager (RCM)
Rich Client Manager (RCM)
Journal Event handling
Journal messages (Joker and Free journal), which should be sent to the server
via Rich Client Manager must be configured with the Journal Event destination
flag (bit value 4) in the DESTXXX parameter either in CUSTMSG or TOPMSG
section. In addtion parameter CUST_EVENTS_WITH_NUMBERS or
TOP_EVENTS_WITH_NUMBERS needs to be enabled. Please refer to
ProTopas Module Construction Kit Programming Guide Version 5.1/xx for
parameter details. In customizing file CUSTOM.RCC you will find a default set
of journal messages assigned to section [CUSTMSG], where the journal event
destination flag is enabled.
Free Journal
Free Journal means, the server receives the journal data and formats the
journal contents based on the variables and transaction type as specified for the
journal numbers via parameters MAPXXXX in registry section
..\CCSYSMG\RCCMSG]. Please refer to Rich Client Manager User Manual for
details. Defaults are specified in configuration file RCCMSG.INA.
Joker Journal
Joker Journal means, the server receives the journal data and stores it in the
data base without any formatting rules.

Parameter Management Rich Client Manager (RCM)
Client Settlement
If Settlement transactions should be sent via RCM to a PC/E server, you have
to configure the types of Settlement transactions assigned to the operation code
buffer of the Transaction Request and which print data should be used from
Transaction Reply.
Parameter name: RCC_STLMT_OP_CODES
Section in *.RCC: [HARDWARE_CONFIGURATION]
Valid range: comma separated list with following format:
8 digit Operation Code buffer
: (colon)
Receipt or Journal buffer
: (colon)
Settlement Type
, (comma)
...
Value description: 8 digit Operation Code buffer
This field has to contain the operation code buffer of the
Transaction Request which belongs to the type of
Settlement transaction
Receipt or Journal buffer

Specifies which print data should be parsed from
Transaction Reply.
’R’ - parse receipt data
’J’ - parse journal data
Settlement Type
Specifies the type of Settlement transaction:
TERMINAL_CLOSE, CLEAR_CASH, ADD_CASH
SUBTRACT_CASH, PRINT_TOTALS, ...
(further types can be found in the RCM Programmers
Reference *.CHM manuals)
Exampe: "IGA :R:TERMINAL_CLOSE,
IGA I :J:TERMINAL_CLOSE"

Software updates via SOP Update diskette creation
Software updates via SOP

This section describes an easy way to transfer new software modules and
parameter settings from a floppy diskette onto the harddisk without an additonal
keyboard. For the data transfer from floppy to harddisk you can use the SOP
function "Copy Files". See also details in the ProTopas/SOP User Guide.
Update diskette creation

For the "Copy Files" function the configuration file "SOPCOPY.TXT" must be
created on a diskette. The "Copy Files" function can copy files from source to
destination. This function can also call *.EXE programs. Therefore the
DESTINATION PATH has to be replaced against "run" instead of the path.
The three parameters have to be separated with one space (blank).
SOPCOPY.TXT contents have the following structure for example:
FILE NAME SOURCE PATH DESTINATION PATH
$update$.z a:\ c:\protopas
custom.ppf a:\ c:\parac
$update$.reg a:\ c:\protopas
$UPDATE$.Z
The compressed file $UPDATE$.Z can be created with ICOMP.EXE. You need
to call ICOMP.EXE with option "subdirectories included". The modules have to
be compressed in the same directory structure as on the harddrive.
CUSTOM.PPF
The configuration file CUSTOM.PPF can be created or modified with PCedt.exe
$UPDATE$.REG
WINNT Registry configuration file, called via REGEDIT -S in "startupappl.bat".
To the example above the diskette consists of following files:
• SOPCOPY.TXT
• $UPDATE$.Z
• CUSTOM.PPF
• $UPDATE$.REG

Software updates via SOP Automatic update process
Automatic update process

After you have called the function "Copy Files" you have to open the operator
door if necessary. Then you can put the diskette into the floppy drive. If you
confirm the function, all the files defined in SOPCOPY.TXT are transfered to the
harddisk. If the function has been finished correctly, you have to restart the
system via SOP function "Restart System". Now the application shuts down and
the system reboots. Before the application comes up the contents of
CUSTOM.PPF are updated via an automatic call of PARAC.EXE. The second
step is the extraction of UPDATE.Z via ICOMP.EXE. After extraction the file
$UPDATE$.Z will be deleted on the harddisk. The third step is a call of
"regedit -s c:\protopas\$update$.reg" if the file $update$.reg exists in the
c:\protopas harddisk directory.
Now in the last step the application will be started. The automatic update
process also checks for an existing $update$.bat and calls the batch file if it
exists in "C:\PROTOPAS". After the batch call the file $update$.bat will be
deleted.
The automatic PARAC call, the call of REGEDIT and the extraction routine are
defined in batch file STARTUPAPPL.BAT located in \PROTOPAS\BIN folder.
This software update procedure via ProTopas/SOP has the

advantage that no additional keyboard is required for updating
parameters or new software modules which are common for rear load
systems.

Start and Stop Application services Start application services
Start and Stop Application services
Start application services

After J/Install has finished the installation the application will be started automat-
ically via batch file "STARTUP.BAT" located in folder C:\PROTOPAS\BIN.
STARTUP.BAT calls several steps for logging and services and finally it calls the
application specific batch file STARTUPAPPL.BAT.
The second option to start the application manually is using the batch file
"FWSTRT.BAT" located in C:\PROTAPAS. FWSTRT.BAT contains just the
application start routines without any preceding application update steps.
Stop application services

The application can be stopped (killed) via "FWKILL.BAT" located in
C:\PROTOPAS.

Application Error Classes Transaction Framework (Class 6434)
Application Error Classes

The following sections describe the application specific errors which are
generated by ProCash/NDC or ProCash/DDC. Typically those errors are used
in cases if no CSC-W32 device error is available from the operating system. In
addition the application generates internal error messages for some return
codes of the ProDevice (WOSA) interface. Details about NDC and DDC status
code mapping are described in manual Error Mapping Cross Reference Tables.
Transaction Framework (Class 6434)

The following table lists those errors which are generated by the Transaction
Framework (dcsttfw.dll).
Table 55: Transaction Framework Error Table
Class Error Code [1] TOPMSG Description

Number
6434 0001 1031 Card was captured
6434 0002 1032 Receipt printer not configured
6434 0003 1032 Statement printer not configured
6434 0004 1032 Statement has been retracted
6434 0005 1039 Deposit error
6434 0006 1021 Deposit canceled
6434 0007 1022 Deposit timeout
6434 0008 1023 Deposit not configured
6434 0009 1029 Cash dispenser not configured
6434 000A 1033 Journal printer general error
6434 000B 1036 Receipt printer general error
6434 000C 1035 Document printer general error
6434 000D 1031 Card reader general error
6434 000E 1033 Journal printer error, spooler active
6434 0010 "" Cash has been retracted
6434 0011 1039 Deposit shutter could not be opened
6434 0012 1038 Vandal Guard could not be opened
6434 0013 1031 Card read treshold maximum reached
6434 0014 "" Cassette has low bills
6434 0015 1049 Paper low on journal printer

6434 0016 1050 Paper low on receipt printer

6434 0017 1051 Paper low on document printer
6434 0018 1501 Try to dispense with money in transport
6434 0019 1031 Card write attempt but no data to write
6434 0020 1029 Cash dispenser shutter error
6434 0021 1039 Deposit bin missing
6434 0022 1039 Deposit jam
6434 0023 1039 Deposit envelope jam during dispense
6434 0024 1039 Deposit no envelopes available
6434 0025 1039 Deposit printer failure
6434 0026 1039 Deposit wrong envelope size
6434 0027 1039 Deposit shutter not closed
6434 0028 1039 Deposit bin is overfilled
6434 0029 1031 Card Reader bin is overfilled
6434 002A 1029 CAS: dialog (907) timeout while service dispenser
6434 002B 1029 CAS: dialog (907) cancel while service dispenser
6434 002C 1023 CAS: dialog (906) timeout while service deposit module
6434 002D 1023 CAS: dialog (906) cancel while service deposit module
6434 002E 1035 CAS: dialog (907) timeout while service statement printer
6434 002F 1035 CAS: dialog (907) cancel while service statement printer
6434 0030 1039 Envelope dispenser low
6434 0031 1039 Envelope dispenser empty
6434 0032 1039 Envelope dispenser error
6434 0033 1039 Envelope dispenser jam
6434 0034 1039 Envelope dispenser shutter not close
6434 0035 1039 Envelope dispenser shutter not open
6434 0036 1032 Statement capture bin full
6434 0037 1033 Journal paper nearly empty
6434 0038 1033 Receipt paper nearly empty
6434 0039 1039 Shutter not close or money jam, no dispense operation
6434 003A 1031 Card manipulation detected while waiting for card
6434 003B 1033 Journal printer error, spooler active
6434 003C 1033 Journal printer ok, reprint started
6434 003D 1033 Journal printer ok, reprint finished
6434 003E 1033 Journal printer error, spooler error
6434 003F 1500 GetPIN error, PIN dialog was cancelled via command

6434 0040 1033 Receipt paper jam or paper empty

6434 0041 1033 Journal paper jam or paper empty
6434 0042 1031 Card was captured after jam
6434 0043 1033 Hard disk free space low (warning) / out (error)
6434 0044 1031 Card write attempted but track for writing not installed
6434 0045 1031 Card write command failed
6434 0046 1031 Card trap active (Lebanese Loop)
6434 0047 1031 Mouth piece removed (vandalism)
6434 0048 1031 Card reader skimming active
6434 0049 1031 Too many consecutive card jams
6434 004A 1031 Shutter not close and cash tray not empty, dispense
operation declined
6434 004B 1031 Shutter not close but cash tray empty, dispense operation
declined
6434 004C 1031 Shutter closed but cash tray not empty, dispense
operation declined
6434 004D 1031 Shutter closed, cash tray empty, but transport way not
free, dispense operation declined
6434 004F 1031 DIP Card not taken
6434 0050 1061 CoinOut hopper low or out
6434 0051 1061 CoinOut low condition not set
6434 0052 1061 CoinOut hopper empty, no dispense attempted
6434 0053 1061 CoinOut module inoperative before dispense
6434 0054 1061 CoinOut hopper low, no dispense attempted
6434 0055 1061 CoinOut dispense error, but coins dispensed
6434 0056 1061 CoinOut dispense error, hopper jam, but partial dispense
possible
6434 0057 1061 CoinOut dispense fatal error, no coins dispensed

Application Error Classes Cash Dispenser Framework (class 643A)
Cash Dispenser Framework (class 643A)

The following table lists all errors which are generated by the Cash Dispenser
Framework (dccdmfw.dll).
Table 56: Cash Dispenser Framework Error Table

Number
643A 0001 1029 Invalid cassette number
643A 0002 1041 Cash cannot be dispensed
643A 0003 1029 Cash cannot be dispensed while safe door open
643A 0004 1029 Reject cassette or whole dispenser not operational
643A 0005 1029 Reject cassette overfilled
643A 0006 1029 Maximum retracts reached
643A 0007 1029 Reject cassette missing
643A 0008 1029 Maximum consecutive present errors reached
643A 0009 1029 The cash dispenser status is fatal
643A 000B 1029 Partial/short dispense/present

Application Error Classes Cash Dispenser Framework (class 643A)
The following table lists ProTopas return codes from the Cash Dispenser device
Framework which are mapped to the hexadecimal error codes assigned to class
643A.
Table 57: Cash Dispenser return code table
Class CDM Error TOPMSG Description

return Code [1] Number
Code
643A -331 FEB5 1029 Order not allowed
643A -330 FEB6 1029 Shutter not closed
643A -324 FEBC 1029 Present job active
643A -323 FEBD 1029 No items to present
643A -322 FEBE 1029 Unknown present error
643A -321 FEBF 1029 Error in bills presentation
643A -320 FEC0 1029 Denomination error
643A -317 FEC3 1029 No documents (no bills)
643A -316 FEC4 1029 Invalid cash unit
643A -315 FEC5 1029 Shutter closed
643A -314 FEC6 1029 Shutter open
643A -313 FEC7 1029 Shutter not open
643A -312 FEC8 1029 Invalid retract
643A -311 FEC9 1029 Safe door open
643A -310 FECA 1029 Position locked
643A -309 FECB 1029 Invalid position
643A -308 FECC 1029 Documents, bills left in transport
643A -307 FECD 1029 Too many documents dispensed
643A -306 FECE 1029 The requested notes are not dispensable
643A -305 FECF 1029 No currency mix
643A -304 FED0 1029 Invalid mix type
643A -303 FED1 1029 Invalid denomination
643A -302 FED2 1029 Cash unit error
643A -301 FED3 1029 Invalid teller ID
643A -300 FED4 1029 Invalid currency
643A -48 FED0 1029 Error timeout
643A -14 FFF2 1029 Hardware error, cannot dispense or deliver
643A -13 FFF3 1029 Hardware error, device not ready
643A -1 FFFF 1029 General error, device not ready

Application Error Classes Security Overlay Framework (Class 643C)
Security Overlay Framework (Class 643C)

The following table lists those errors which are generated by the Security
Overlay Framework (dcsecure.dll).
Table 58: Transaction Framework Error Table

Number
643C 0001 1500 Set key error, possibly wrong security keys loaded
643C 0002 1500 PIN check error, possibly wrong security keys
643C 0003 1500 Error while creating PIN block for remote PIN block buffer
included in transaction request message
643C 0004 1500 The correct MAC could not be calculated
643C 0005 1500 Key error while initializing transaction, possibly no keys
loaded in EDM or EPP
[1] This error code can be interpreted as a WARNING or ERROR class by

the ProCash/NDC or ProCash/DDC application.

Registry Cross Reference

The following tables show the cross link of "User Area" (Section) and
"User Name" (Parameter) defined in "CUSTOM.PPF" to the Windows Registry
section location and parameter name.
Table 59: Registry cross link [STARTUP]
USER AREA in"CUSTOM.PPF" REGISTRY LOCATION
[STARTUP] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\
CCREPMGR\FRM_REPOSITORY]
USER NAME REGISTRY PARAMETER
SEL_FRAME CCSelFW
BARCODE_FRAME CCBcrFW
JOURNAL_FRAME CCJournal
SERVICE_FRAME CCServiceFW
OPL_FRAME CCOplFW
APPLICATION_FRAME CCApplFW
CDM_FRAME CCCdmFW
CDM2_2_FRAME CCCdmFW2_2
CDM3_FRAME CCCdmFW3
COINOUT_FRAME CCCoinOutFW
APPL_DATA_FRAME CCDataFW
SMI_FRAME CCSmiFW
DLG_FRAME CCDlgFW
COM_FRAME CCCommunication1
SEC_FRAME CCSecFW
CARD_FRAME CCCardFW
CAMERA_FRAME CCCamFW
EPP_FRAME CCEppFW
DIALOG_FRAME CCDialog
SCRIPT_FRAME CCSCRIPTFW
CONVERTER_FRAME DCConvFW
SYNC_FRAME CCSyncFW
JOURNAL_FRAME CCJourPrtFW
MSGCTRL1_FRAME CCMessageControl1
RECPRT_FRAME CCRecPrtFW
PROT1_FRAME CCProtFW1
PRESS_FRAME CCPresFW
DEVSTA_FRAME CCDeviceStatusFW
DEPOSIT_FRAME CCDepositFW
TRANSACT_FRAME CCTransactionFW
USEREXIT_FRAME CCSUEFW
VARIABLE_FRAME CCVarFW
SECURE_FRAME CCSecureFW
DOCPRT_FRAME CCDocPrtFW
CCSOP_DIALOG CCSopDialog

Table 60: Registry cross link [START_APPLICATION]

START_APPLICATION [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\RESTART\APPLICATION_1]
APPLICATION_SET ApplPM
PROGRAMLIST PROGRAMS
Table 61: Registry cross link [DEFAULT]

DEFAULT [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\RESTART\DEFAULTS]
SHUTDOWN_ACTIVE SHUTDOWN_ACTIVE
MAXREBOOT MAXREBOOT
POWER_UP_PERIOD POWER_UP_PERIOD
SHUTDOWN_EXE SHUTDOWN_EXE
Table 62: Registry cross link [CCProtFW1]

CCProtFW1 [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\CCProtFW1]
PROTOCOL PROTOCOL
CCVTABLE CCVTABLE
LOG_FILE LOG_FILE
LOG_FILE_SIZE LOG_FILE_SIZE
HANDLE_ETX HANDLE_ETX

Table 63: Registry cross link [MODEM]

MODEM_COMMANDS [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\COMMUNICATION\
MODEM\COMMANDS]
MODEM_AUTO_NUMBER AUTO_NUMBER
MODEM_CMD_CONFIG CMD_CONFIG
MODEM_EVENTS [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
MODEM\EVENTS]
MODEM_PROJECT [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
MODEM\PROJECT]
MODEM_PROJECT_ALTERNATE [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
MODEM\PROJECT_ALTERNATE]

Table 64: Registry cross link [SERIAL]

SERIAL_COMMANDS [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
SERIAL\COMMANDS]
SERIAL_LINE_ATTR LINE_ATTR
SERIAL_PORTNAME PORTNAME
SERIAL_EVENTS [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
SERIAL\EVENTS]
SERIAL_PROJECT [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
SERIAL\PROJECT]
SERIAL_PROJECT_ALTERNATE [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
SERIAL\PROJECT_ALTERNATE]
Table 65: Registry cross link [PROTOCOL\PROJECT]

PROTOCOL_PROJECT [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
PROTOCOL\PROJECT]
COM_CHANNEL ComChannel
COMM_PROTOCOL ComProtocol
PROT_CHANNEL ProtocolChannel
ROUTE_ID RouteID
TERMINAL_ID TerminalID

Table 66: Registry cross link [HARDWARE_CONFIGURATION] (DDC)

[HARDWARE_CONFIGURATION] [HKEY_LOCAL_MACHINE\SOFTWARE\
Wincor Nixdorf\ProTopas\CurrentVersion\
CCOPEN\PROTOCOL\PARAMETER]
EXPANDED_HW_CONF_BYTE_0 EXPANDED_HW_CONF_BYTE_0
DOUBLE_EXPANDED_HW_CONF_BYTE_16 DOUBLE_EXPANDED_HW_CONF_BYTE_16
DOUBLE_EXPANDED_HW_CONF_BYTE_17 PREP_FIELD_029
DOUBLE_EXPANDED_HW_CONF_BYTE_18 PREP_FIELD_030
SEND_TVN_MAC SEND_TVN_MAC
CHECK_TVN_MAC CHECK_TVN_MAC
SEND_MACHINE_NO SEND_MACHINE_NO
CHECK_MACHINE_NO CHECK_MACHINE_NO
SEND_TVN_MAC_SOL SEND_TVN_MAC_SOL
MAC_FLD_SELECTED MAC_FLD_SELECTED
MAC_ASCII MAC_ASCII
STATUS_CODE_HANDLING STATUS_CODE_HANDLING
RKL_ENCODING RKL_ENCODING
SAF_MACH_NO SAF_MACH_NO

Table 67: Registry cross link [HARDWARE_CONFIGURATION] (NDC)

[HARDWARE_CONFIGURATION] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\PROTOCOL\PARAMETER]
HW_CONF_0_PROD_CLASS HW_CONF_0_PROD_CLASS
HW_CONF_1_NOCONFIG HW_CONF_1_NOCONFIG
HW_CONF_2_DISK HW_CONF_2_DISK
HW_CONF_3_CARD_READER HW_CONF_3_CARD_READER
HW_CONF_4_CASH_HANDLER HW_CONF_4_CASH_HANDLER
HW_CONF_5_PPD HW_CONF_5_PPD
HW_CONF_6_REC_PRINTER HW_CONF_6_REC_PRINTER
HW_CONF_7_JRN_PRINTER HW_CONF_7_JRN_PRINTER
HW_CONF_8_RESERVED HW_CONF_8_RESERVED
HW_CONF_10_NIGHT_DEPOSIT HW_CONF_10_NIGHT_DEPOSIT
HW_CONF_11_ENCRYPTOR HW_CONF_11_ENCRYPTOR
HW_CONF_12_CAMERA HW_CONF_12_CAMERA
HW_CONF_13_DOOR_ACCESS HW_CONF_13_DOOR_ACCESS
HW_CONF_14_FLEX_DISK HW_CONF_14_FLEX_DISK
HW_CONF_15_TAMPER_BINS HW_CONF_15_TAMPER_BINS
HW_CONF_16_CARDHOLDER_KEYB HW_CONF_16_CARDHOLDER_KEYB
HW_CONF_17_OPERATOR_KEYB HW_CONF_17_OPERATOR_KEYB
HW_CONF_18_DISPLAY_VOICE HW_CONF_18_DISPLAY_VOICE
HW_CONF_21_STATEMENT_PRT HW_CONF_21_STATEMENT_PRT
HW_CONF_22_SIG_DISPLAY HW_CONF_22_SIG_DISPLAY
HW_CONF_24_COIN_DISP HW_CONF_24_COIN_DISP
HW_CONF_25_SYSTEM_DISPLAY HW_CONF_25_SYSTEM_DISPLAY
HW_CONF_26_MED_ENT_IND HW_CONF_26_MED_ENT_IND
HW_CONF_27_ENV_DISP HW_CONF_27_ENV_DISP
HW_CONF_28_DOC_PROC_MOD HW_CONF_28_DOC_PROC_MOD
HW_CONF_29_COIN_TAMP_IND HW_CONF_29_COIN_TAMP_IND
HW_CONF_30_DOC_TAMP_IND HW_CONF_30_DOC_TAMP_IND
HW_CONF_32_DIG_AUDIO_SERV HW_CONF_32_DIG_AUDIO_SERV

MESSAGE_LOGGING MESSAGE_LOGGING
SEND_TVN_MAC SEND_TVN_MAC
CHECK_TVN_MAC CHECK_TVN_MAC
SEND_MACHINE_NO SEND_MACHINE_NO
CHECK_MACHINE_NO CHECK_MACHINE_NO
SEND_TVN_MAC_SOL SEND_TVN_MAC_SOL
MAC_FLD_SELECTED MAC_FLD_SELECTED
MAC_ASCII MAC_ASCII
STATUS_CODE_HANDLING STATUS_CODE_HANDLING
GO_OFFLINE_AFTER_TIMEOUT GO_OFFLINE_AFTER_TIMEOUT

Table 68: Registry cross link [LYNXCI_PARAMETER]

[LYNXCI_PARAMETER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXCI\PARAMETER]
PARAMETER_00 PARAMETER_00
LUNO LUNO
CONFIG_ID CONFIG_ID
Table 69: Registry cross link [LYNXCI_TIMER]

[LYNXCI_TIMER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXCI\TIMER]
TIMER_00 TIMER_00
TIMER_01 TIMER_01
TIMER_02 TIMER_02
TIMER_03 TIMER_03
TIMER_04 TIMER_04
TIMER_05 TIMER_05
TIMER_06 TIMER_06
TIMER_07 TIMER_07
TIMER_09 TIMER_09
TIMER_10 TIMER_10
TIMER_94 TIMER_94
TIMER_95 TIMER_95
TIMER_96 TIMER_96
TIMER_99 TIMER_99

Table 70: Registry cross link [LYNXCI_EMV]

[LYNXCI_EMV] [HKEY_LOCAL_MACHINE\SOFTWARE\
LYNXCI\EMV]
COMPLETION_OBJECTS COMPLETION_OBJECTS
CONTACT_THRESHOLD CONTACT_THRESHOLD
LANGUAGE_SUPPORTED LANG_SUPPORTED
PROTOCOL_SPEC PROTOCOL_SPEC
FORCE_DECLINE_AIDS FORCE_DECLINE_AIDS
FORCE_DECLINE_TA_TYPE_nn_AIDS FORCE_DECLINE_TA_TYPE_nn_AIDS
FORCE_SCRIPT_ERROR_AIDS FORCE_SCRIPT_ERROR_AIDS
FORCE_SCRIPT_ERROR_TA_TYPE_nn_AIDS FORCE_SCRIPT_ERROR_TA_TYPE_nn_AIDS
CODE_TABLE_nn_SEQ CODE_TABLE_nn_SEQ
SELECTION_METHOD SELECTION_METHOD
IGNORE_ISSUER_SCRIPT_FAILURE IGNORE_ISSUER_SCRIPT_FAILURE
TRANSACTION_PROCESSING TRANSACTION_PROCESSING
PREFERRED_AIDS PREFERRED_AIDS
EMV_ERROR_CONDITIONS EMV_ERROR_CONDITIONS
IGNORE_EXT_AUTH_FAILURE IGNORE_EXT_AUTH_FAILURE
SUPPORTED_US_COMMON_AIDS SUPPORTED_US_COMMON_AIDS
CONTACTLESS_TLV_DATA CONTACTLESS_TLV_DATA
CONTACTLESS_EXTRACT_TAGS CONTACTLESS_EXTRACT_TAGS
CONTACTLESS_REMOVE_TAGS CONTACTLESS_REMOVE_TAGS
CONTACTLESS_ERROR_SCREENS CONTACTLESS_ERROR_SCREENS
CONTACTLESS_CHECKS CONTACTLESS_CHECKS
TRANSACTION_OBJECTS TRANSACTION_OBJECTS
ACQUIRER_IDENTIFIER_9F01 ACQUIRER_IDENTIFIER_9F01
Table 71: Registry cross link [EMV_TAGS]

[EMV_TAGS] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\EMVDEBITCREDITFW\
TERMINAL_PROPERTIES\TAGS]
ACQUIRER_IDENTIFIER_9F01 9F01
MERCHANT_CATEGORY_CODE_9F15 9F15
TERMINAL_COUNTRY_CODE_9F1A 9F1A
TERMINAL_CAPABILITIES_9F33 9F33
TERMINAL_TYPE_9F35 9F35
ADDITIONAL_TERMINAL_ 9F40
CAPABILITIES_9F40

Table 72: Registry cross link [CASH_DISPENSER]

[CASH_DISPENSER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\CASH_DISPENSER]
NUM_LOG_CASS NUM_LOG_CASS
CURRENCY_1 CURRENCY_1
VALUE_1 VALUE_1
VALUE_2 VALUE_2
VALUE_3 VALUE_3
VALUE_4 VALUE_4
VALUE_5 VALUE_5
VALUE_6 VALUE_6
VALUE_7 VALUE_7
VALUE_8 VALUE_8
DEFAULT_NUM_NOTES_1 DEFAULT_NUM_NOTES_1
AUTO_LOGON_CASSETTES AUTO_LOGON_CASSETTES
AUTO_LOGON_IN_SOP AUTO_LOGON_IN_SOP
AUTO_LOGON_NOTES AUTO_LOGON_NOTES
DENOMINATION_LOW_MSG DENOMINATION_LOW_MSG
CLEAR_MISS_COUNTER CLEAR_MISS_COUNTER
DISPENSE_ALGO DISPENSE_ALGO
SEND_CASSETTE_LOW_ALWAYS SEND_CASSETTE_LOW_ALWAYS
MAX_PRESENT_ERRORS MAX_PRESENT_ERRORS
SEND_SOL_RETRACT SEND_SOL_RETRACT
SOLICITED_IF_RETRACT_INHIBIT SOL_RETRACT_INHIBIT
CAS_WAIT_TIME CAS_WAIT_TIME
FATAL_CASS_AS_MISSING FATAL_CASS_AS_MISSING
DISPENSE_BELOW_ZERO DISPENSE_BELOW_0
LOGICAL_MAPPING LOGICAL_MAPPING
DENOM_ID_UPPERCASE DENOM_ID_UPPERCASE
CHECK_STATUS_AFTER_MONEY_TAKEN CHECK_STATUS_AFTER_MONEY_TAKEN
PRESENT_FAILURE_SCREEN PRESENT_FAILURE_SCREEN
NUM_PHYS_NAMES NUM_PHYS_NAMES

PHYS_NAME_X PHYS_NAME_X
DISPENSE_RETRIES DISPENSE_RETRIES
PRESENT_TIMER PRESENT_TIMER
MAX_REJECT_NOTES MAX_REJECT_NOTES
REJECT_FATAL_STATUS REJECT_FATAL_STATUS
MV_TESTDISPENSE MV_TESTDISPENSE
EQUAL_PHYS_CASS_COUNTERS EQUAL_PHYS_CASS_COUNTERS
CHECK_FATAL_BEFORE_DISPENSE CHECK_FATAL_BEFORE_DISPENSE
MAX_DISPENSE_ERRORS MAX_DISPENSE_ERRORS
HWERR_DISPENSE_RETRIES HWERR_DISPENSE_RETRIES
EXPONENT_CORRECTION EXPONENT_CORRECTION
DISPLAY_PRESENT_SCREEN DISPLAY_PRESENT_SCREEN
PHYS_GOOD_NOTES PHYS_GOOD_NOTES
MAX_DISPENSE_TIME MAX_DISPENSE_TIME
DO_CIN_RETRACT DO_CIN_RETRACT
ProTopas
[CCCDMFW] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CurrentVersion\CCOPEN\CCCdmFW]
MAXRETRACT MaxRetract
AUTO_SWITCH_GUIDLIGHT AutoSwitchGuidLight

Table 73: Registry cross link [COIN_DISPENSER]

[COIN_DISPENSER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\COIN_DISPENSER]
NUM_LOG_HOPPERS NUM_LOG_HOPPERS
NUM_HOST_HOPPERS NUM_HOST_HOPPERS
DISPENSE_FLAGS DISPENSE_FLAGS
VALUE_1 VALUE_1
VALUE_2 VALUE_2
VALUE_3 VALUE_3
VALUE_4 VALUE_4
VALUE_5 VALUE_5
VALUE_6 VALUE_6
VALUE_7 VALUE_7
VALUE_8 VALUE_8
Table 74: Registry cross link [BARCODE]

[BARCODE] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\BARCODE]
ACCEPT_CODE_FORMAT READ_CODE

Table 75: Registry cross link [DEPOSIT]

[DEPOSIT] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\DEPOSIT]
DISPENSE_SCREEN DISPENSE_SCREEN
DISPENSE_WAIT_SCREEN DISPENSE_WAIT_SCREEN
DISPENSE_ENVELOPE DISPENSE_ENVELOPE
CANCEL_ACTIVE CANCEL_ACTIVE
PRINT_ON_ENVELOPE PRINT_ON_ENVELOPE
DEPOSIT_CHARTABLE_LOW CHARTABLE_LOW
DEPOSIT_CHARTABLE_HIGH CHARTABLE_HIGH
DEPOSIT_USER_CHARSET USER_CHARSET
[DEP] [HKEY_CLASSES_ROOT\WOSA/XFS_ROOT\
PHYSICAL_SERVICES\DEVICES\DEP]
CONTPOLLTIME ContPollTime
ENTRYSPLIT EntrySplit
PREPAREDISPENSE PrepareDispense
Table 76: Registry cross link [CARD_READER]

[CARD_READER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\CARD_READER]
DEFAULT_READ_TRACK1 DEFAULT_READ_TRACK1
DEFAULT_READ_CHIP DEFAULT_READ_CHIP
IDLE_REMOVE_SCREEN IDLE_REMOVE_SCREEN
EJECT_IN_OUT_TIMER EJECT_IN_OUT_TIMER
MANIP_THRESHOLD MANIP_THRESHOLD
JAM_THRESHOLD JAM_THRESHOLD
DIP_EJECT_SCREEN DIP_EJECT_SCREEN
CONTACTLESS_HANDLING CONTACTLESS_HANDLING

Table 77: Registry cross link [ELECTRONIC_JOURNAL]

[ELECTRONIC_JOURNAL] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\JOURNAL]
TOP_MAX_FILES TOP_MAXFILES
CUST_MAX_FILES CUST_MAXFILES
SPOOLER_RESET RESET
SPOOLER_PRINT_CACHE_TIMER PRINT_CACHE_TIMER
SPOOLER_PRINT_CACHE_THRESHOLD PRINT_CACHE_THRESHOLD
SPOOLER_MAX_SPOOL_FILE MAX_SPOOL_FILE
SPOOLER_MAX_SPOOL_AREA MAX_SPOOL_AREA
Table 78: Registry cross link [JOURNALPRINTER]

[JOURNALPRINTER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\PRINTER\JOURNAL]
CPI CPI
LPI LPI
USER_CHARSET USER_CHARSET
PAPER_JOURNAL PAPER_JOURNAL
ELECTRONIC_JOURNAL ELECTRONIC_JOURNAL
JRN_FONT_ENTRIES FONT_ENTRIES
SPOOLER_KEEP_PRINTER_STATUS SPOOLER_KEEP_PRT_STATUS
SEND_SPOOLER_ERROR SEND_SPOOLER_ERROR
FORCE_PAPER_OUT_SUPPLY FORCE_PAPER_OUT_SUPPLY
CP_JOURNAL_FONT_TYPE_NNN CP_FONT_TYPE_NNN
PRINT_JOURNAL_ALWAYS PRINT_JOURNAL_ALWAYS
HDD_SPACE_LOW_LIMIT HDD_SPACE_LOW_LIMIT
CHECK_FILE_JOURNAL CHECK_FILE_JOURNAL
EJU_SAF_MAX_FILE_SIZE EJU_SAF_MAX_FILE_SIZE
EJU_SAF_FILE_NAME EJU_SAF_FILE_NAME
EJU_CONVERT_HOST_DATA EJU_CONVERT_HOST_DATA
ALL_CHARS_IN_EJRN ALL_CHARS_IN_EJRN
PRINT_UNICODE PRINT_UNICODE
Table 79: Registry cross link [JOURNAL_FONT_XXX]

[JOURNAL_FONT_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
LYNXPAR\PRINTER\JOURNAL\FONT_XXX]
JOURNAL_CONDENSED CONDENSED
JOURNAL_FONT_TYPE FONT_TYPE
JOURNAL_DOUBLE_WIDTH DOUBLE_WIDTH

JOURNAL_CHARTABLE_LOW CHARTABLE_LOW
JOURNAL_CHARTABLE_HIGH CHARTABLE_HIGH
JOURNAL_USER_CHARSET USER_CHARSET
JOURNAL_MACRO MACRO
JOURNAL_PRINT_UNICODE PRINT_UNICODE

Table 80: Registry cross link [RECEIPTPRINTER]

[RECEIPTPRINTER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\PRINTER\RECEIPT]
CPI CPI
LPI LPI
RECEIPT_FONT_ENTRIES FONT_ENTRIES
RECEIPT_PAGE_HEADER PAGE_HEADER
FORCE_PAPER_OUT_SUPPLY FORCE_PAPER_OUT_SUPPLY
CP_RECEIPT_FONT_TYPE_NNN CP_FONT_TYPE_NNN
RECEIPT_PAGE_FOOTER PAGE_FOOTER
RECEIPT_FOOTER_LINE FOOTER_LINE
REAR_BAL_OPTIONS REAR_BAL_OPTIONS
MERGE_R01 MERGE_R01
[RECEIPTPRINTER] [HKEY_CLASSES_ROOT\WOSA/XFS_ROOT\
PHYSICAL_SERVICES\DEVICES\NDXXR]
LEDTIMER LedTimer
Table 81: Registry cross link [RECEIPT_FONT_XXX]

[RECEIPT_FONT_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
LYNXPAR\PRINTER\RECEIPT\FONT_XXX]
RECEIPT_CONDENSED CONDENSED
RECEIPT_FONT_TYPE FONT_TYPE
RECEIPT_DOUBLE_WIDTH DOUBLE_WIDTH
RECEIPT_CHARTABLE_LOW CHARTABLE_LOW
RECEIPT_CHARTABLE_HIGH CHARTABLE_HIGH
RECEIPT_USER_CHARSET USER_CHARSET
RECEIPT_MACRO MACRO
RECEIPT_PRINT_UNICODE PRINT_UNICODE

Table 82: Registry cross link [DOCUMENTPRINTER]

[DOCUMENTPRINTER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\PRINTER\DOCUMENT]
CPI CPI
LPI LPI
NO_OF_DOC_BEFORE_EJECT NO_OF_DOC_BEFORE_EJECT
CANCEL_ACTIVE CANCEL_ACTIVE
FONT_ENTRIES FONT_ENTRIES
DOC_PAGE_HEADER PAGE_HEADER
DOC_PAGE_FOOTER PAGE_FOOTER
DOC_FOOTER_LINE FOOTER_LINE
Table 83: Registry cross link [DOCUMENT_FONT_XXX]

[DOCUMENT_FONT_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
LYNXPAR\PRINTER\DOCUMENT\FONT_XXX]
DOCUMENT_CONDENSED CONDENSED
DOCUMENT_FONT_TYPE FONT_TYPE
DOCUMENT_DOUBLE_WIDTH DOUBLE_WIDTH
DOCUMENT_CHARTABLE_LOW CHARTABLE_LOW
DOCUMENT_CHARTABLE_HIGH CHARTABLE_HIGH
DOCUMENT_USER_CHARSET USER_CHARSET
DOCUMENT_MACRO MACRO
DOCUMENT_PRINT_UNICODE PRINT_UNICODE

Table 84: Registry cross link [VIEWER]

[VIEWER] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\VIEWER]
MODE MODE
BELL_TIME BELL_TIME
CURSOR CURSOR
ProTopas\CurrentVersion\CCOPEN\VIEWER\FONT]
TABLE_ENTRIES TABLE_ENTRIES
ProTopas\CurrentVersion\CCOPEN\VIEWER\FONT\FONT_XXX]
NAME NAME
SIZE SIZE
NDC_DOUBLE NDC_DOUBLE
NDC_FONT NDC_FONT
HEIGHT HEIGHT
PROPORTIONAL PROPORTIONAL
Table 85: Registry cross link [SNA]

[SNA] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCOPEN\COMMUNICATION\SNA]
OPENTIME OPENTIME
Table 86: Registry cross link [SNA_PROJECT]

[SNA_PROJECT] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\COMMUNICATION\SNA\PROJECT]
ADDSNAINFO ADDSNAINFO
NAUTYPE NAUTYPE
PROJECT_RECEIVE_BUFFER_SIZE RECEIVE_BUFFER_SIZE
LUNAME LUNAME
STRIPFMH STRIPFMH
SENDINITSELF SENDINITSELF
RSPTIMER RSPTIMER

Table 87: Registry cross link [SNA_PROJECT_INITSELF]

[SNA_PROJECT_INITSELF] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\COMMUNICATION\SNA\PROJECT\INITSELF]
OPLIB OPLIB
DLUNAME DLUNAME
OPPASS OPPASS
OPMODE OPMODE
OPUID OPUID
Table 88: Registry cross link [X25]

[X25] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\COMMUNICATION\X25]
CALLDELAY CALLDELAY
CORESYNC CORESYNC
CONTABSIZE CONTABSIZE
CALLRETRY CALLRETRY
POLLTIME POLLTIME
CLOSETIME CLOSETIME
SHMDELAY SHMDELAY
NETTIME NETTIME
OPENTIME OPENTIME

Table 89: Registry cross link [X25_PROJECT]

[X25_PROJECT] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\COMMUNICATION\X25\PROJECT]
PROJECT_RECEIVE_BUFFER_SIZE RECEIVE_BUFFER_SIZE
SHMCLRCAUSEDIAG SHMCLRCAUSEDIAG
MAXSENDSIZE MAXSENDSIZE
SHM_PASSIVE SHM_PASSIVE
CUGSELECTION CUGSELECTION
D_BIT_PROC D_BIT_PROC
REMRESCAUSEDIAG REMRESCAUSEDIAG
OFFRESCAUSEDIAG OFFRESCAUSEDIAG
VCTYPE VCTYPE
PASSIVE_START PASSIVE_START
CALLUSERDATA_P CALLUSERDATA_P
NOTRACE NOTRACE
MAXRECVSIZE MAXRECVSIZE
PVCNO PVCNO
CALLUSERDATA_A CALLUSERDATA_A
CUGOUTSELECT CUGOUTSELECT
INDEX INDEX
SEND_RECONNECT SEND_RECONNECT
REVERSECHRG_PAS REVERSECHRG_PAS
SHMDELAY_FLAG SHMDELAY_FLAG
REVERSECHRG_ACT REVERSECHRG_ACT
LOCALADR LOCALADR
REMOTEADR1 REMOTEADR1

Table 90: Registry cross link [TCPIP_PROJECT]

[TCPIP_PROJECT] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
CCOPEN\COMMUNICATION\TCPIP\PROJECT]
REMOTEPEER REMOTEPEER
REMOTEPEER_X REMOTEPEERX
KEEPALIVES KEEPALIVES
TRANSPORTSIZE TRANSPORTSIZE
CLOSETIMEOUT CLOSETIMEOUT
CLIENTOPENRETRY CLIENTOPENRETRY
CODINGDLL CODINGDLL
TYPE TYPE
PORTNUMBER PORTNUMBER
ADMINSIZE ADMINSIZE
OPENTIMEOUT OPENTIMEOUT
SENDTIMEOUT SENDTIMEOUT
LOCALPORT LOCALPORT
Table 91: Registry cross link [TOPMSG]

[TOPMSG] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCSYSMSG\TOPMSG]
DESTXXXX DESTXXXX
MSGXXXX MSGXXXX
Table 92: Registry cross link [CUSTMSG]

[CUSTMSG] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\CCSYSMSG\CUSTMSG]
DESTXXXX DESTXXXX
MSGXXXX MSGXXXX

Table 93: Registry cross link [LYNXCI_SCREEN]

[LYNXCI_SCREEN] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
SCREEN_FOREGROUND_COLOR FOREGROUND_COLOR
SCREEN_BACKGROUND_COLOR BACKGROUND_COLOR
SCREEN_TRANSPARENT_MODE TRANSPARENT_MODE
PICTURE_GXX PICTURE_GXX
PICTURE_LXX PICTURE_LXX
PICTURE_XX PICTURE_XX
PICTURE_XXX PICTURE_XXX
PICTURE_XXXX PICTURE_XXXX
PALETTE_XXX PALETTE_XXX
PALETTE_DEFAULT PALETTE_DEFAULT
BLINK_RATE BLINK_RATE
CHARACTER_WIDTH CHARACTER_WIDTH
CHARACTER_HEIGHT CHARACTER_HEIGHT
PICTURE_BACKGROUND PICTURE_BACKGROUND
VERTICAL_OFFSET VERTICAL_OFFSET
HORIZONTAL_OFFSET HORIZONTAL_OFFSET
PICTURE_EXT_X PICTURE_EXT_X (X = file extensions)
SCREEN_FULL_SCREEN_VIDEO FULL_SCREEN_VIDEO
PIN_TOUCH_ENABLE PIN_TOUCH_ENABLE
PIN_CONFIRM_KEY PIN_CONFIRM_KEY
AUDIOX_PATH AUDIOX_PATH
AUDIOXXX_PATH AUDIOXXX_PATH
STOP_VIDEO_AFTER_DELAY STOP_VIDEO_AFTER_DELAY
SPECIFIC_SV_MODE_SCREEN SPECIFIC_SV_MODE_SCREEN
ESC_SUB ESC_SUB
SUBST_CHAR_SCREEN SUBSTITUTION_CHARACTER
SCREEN_MIN_PIN_LEN MIN_PIN_LEN

Table 94: Registry cross link [SCREEN_XXX]

[SCREEN_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXCI\SCREEN\XXX]
FOREGROUND_COLOR FOREGROUND_COLOR
BACKGROUND_COLOR BACKGROUND_COLOR
IDLE_NEXT_SCREEN IDLE_NEXT_SCREEN
IDLE_TIME IDLE_TIME
CHARACTER_WIDTH CHARACTER_WIDTH
CHARACTER_HEIGHT CHARACTER_HEIGHT
VERTICAL_OFFSET VERTICAL_OFFSET
HORIZONTAL_OFFSET HORIZONTAL_OFFSET
TRANSPARENT_MODE TRANSPARENT_MODE
PICTURE_BACKGROUND PICTURE_BACKGROUND
DISPLAY_CONTENTS DISPLAY_CONTENTS
INPUT_FIELD_LEFT INPUT_FIELD_LEFT
INPUT_FIELD_TOP INPUT_FIELD_TOP
INPUT_FIELD_RIGHT INPUT_FIELD_RIGHT
INPUT_FIELD_BOTTOM INPUT_FIELD_BOTTOM
INPUT_FIELD_ADJUST INPUT_FIELD_ADJUST
SCREEN_CONTENTS CONTENTS
Table 95: Registry cross link [OPERATOR_SCREENS]

[OPERATOR_SCREENS] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\OPERATOR_SCREENS]
PRINTER_HEADER_RECEIPT PRINTER_HEADER_RECEIPT
PRINTER_HEADER_JOURNAL PRINTER_HEADER_JOPURNAL
PRINTER_HEADER_DOCUMENT PRINTER_HEADER_DOCUMENT

Table 96: Registry cross link [APPLICATION_XXX]

[APPLICATION_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\APPLICATION]
CLEAR_HWFITNESS CLEAR_HWFITNESS
RESEND_POWER_UP RESEND_POWER_UP
SUSPEND_TIMEOUT SUSPEND_TIMEOUT
SEND_POWER_UP SEND_POWER_UP
SEND_DOOR_CHANGE SEND_DOOR_CHANGE
Q_UNSOL_IN_TRAN_REQ Q_UNSOL_IN_TRAN_REQ
Q_OFFLINE_TRAN_READY Q_OFFLINE_TRAN_READY
SVRMODE_WHEN_DOOR_OPEN SVRMODE_WHEN_DOOR_OPEN
SWITCH_LOGO SWITCH_LOGO
DEFAULT_MISC_FEATURE_1[1] DEFAULT_MISC_FEATURE_1
DEFAULT_MISC_FEATURE_2[1] DEFAULT_MISC_FEATURE_2[1]
DEFAULT_MISC_FEATURE_3[1] DEFAULT_MISC_FEATURE_3[1]
DEFAULT_CARD_READ_THRESHOLD DEFAULT_CARD_READ_THRESHOLD
DEFAULT_CARD_WRITE_THRESHOLD DEFAULT_CARD_WRITE_THRESHOLD
DEFAULT_SUPPLY_READY_AMOUNT_ DEFAULT_MISC_FEATURE_1
OPTIONS[2]
OOS_AFTER_ONLINE OOS_AFTER_ONLINE
REAR_BALANCE_TIMEOUT REAR_BALANCE_TIMEOUT
OFFLINE_REBOOT_TIMER OFFLINE_REBOOT_TIMER
LED_IN_SERVICE LED_IN_SERVICE
LED_SERVICE LED_SERVICE
LED_CUSTOMER LED_CUSTOMER
LED_SVR_MODE LED_SVR_MODE
LED_CASH LED_CASH
LED_PAPER LED_PAPER
DOUBLE_LENGTH_KEYS DOUBLE_LENGTH_KEYS
ADJ_GEN_BUF_FROM_AMT ADJ_GEN_BUF_FROM_AMT
JOU_NAME_CASS JOU_NAME_CASS
JOU_NAME_CASSN JOU_NAME_CASSN
JOU_NAME_REJECT JOU_NAME_REJECT
JOU_TXT_REJECTS JOU_TXT_REJECTS
JOU_TXT_RETRACTS JOU_TXT_RETRACTS
ADRS_OPTIONS ADRS_OPTIONS
ADRS_MAX_RETRIES ADRS_MAX_RETRIES
STORE_COM_KEY STORE_COM_KEY
CARD_RETAIN_DISPLAY CARD_RETAIN_DISPLAY
ALARM_SENSORS ALARM_SENSORS
PRINT_IMMEDIATE_OPTIONS PRINT_IMMEDIATE_OPTIONS
[1] - APPLICATION_DDC only
[2] - APPLICATION_NDC only

Table 97: Registry cross link [APPLICATION_XXX] part 2

[APPLICATION_XXX] [HKEY_LOCAL_MACHINE\SOFTWARE\Wincor Nixdorf\
ProTopas\CurrentVersion\LYNXPAR\APPLICATION]
USE_CLOSE_TIMER_ALWAYS USE_CLOSE_TIMER_ALWAYS
RECEIPT_DELIVERED RECEIPT_DELIVERED
TRAN_DELAY_TIME TRAN_DELAY_TIME
FID_Z_WAIT_TIME FID_Z_WAIT_TIME[1]
PAN_HANDLING PAN_HANDLING
MONITOR_BOOT_SWITCH MONITOR_BOOT_SWITCH
MONITOR_SAFE_DOOR MONITOR_SAFE_DOOR
RECONNECT_DELAY RECONNECTDELAY
POWER_SAVE_DELAY POWER_SAVE_DELAY
NDC_LTS_OPTIONS NDC_LTS_OPTIONS[2]
HP_HANDLING HP_HANDLING[3]
D91X_OPTIONS[1] D91X_OPTIONS[1]
[1] - APPLICATION_DDC only
[2] - APPLICATION_NDC only
[3] - Defined in CUSTOM.RCC for the Rich Client Manager
Table 98: Registry cross link [DDC_DEPOSIT_EMULATION]

[DDC_DEPOSIT_EMULATION] [HKEY_LOCAL_MACHINE\SOFTWARE\
LYNXPAR\DDC_DEPOSIT_EMULATION]
ENABLE ENABLE
OPKEY_STD OPKEY_STD
OPKEY_CASH OPKEY_CASH
OPKEY_SINGLE_CHECK OPKEY_SINGLE_CHECK
OPKEY_BUNDLE_CHECK OPKEY_BUNDLE_CHECK
OPKEY_MIXED OPKEY_MIXED
SUPPRESS_UNSOL_CASH_STATUS SUPPRESS_UNSOL_CASH_STATUS
REDIRECT_FUNC_X REDIRECT_FUNC_X
REDIRECT_NEXT_X REDIRECT_NEXT_X
FORM_X FORMX
TAG_X TAGX
REGEX_X REGEXX
CLEAR_BUFFERIDS_X CLEAR_BUFFERIDS_X
CLEAR_CIN_TRAN_BUFFER CLEAR_CIN_TRAN_BUFFER
CLEAR_CHQ_TRAN_BUFFER CLEAR_CHQ_TRAN_BUFFER

Installation and Configuration ToolsProCash/NDC-DDC Configuration Manag
Installation and Configuration Tools

This section describes tools and utilities for the configuration of hardware device
settings or application specific parameter settings. Additionally you get infor-
mation about trace and analyzing tools.
ProCash/NDC-DDC Configuration Manager

The ProCash/NDC-DDC Configuration Manager is a Windows frontend for
operators. Several utilities can be called via pull down menus in one main
window. All menu functions contain context sensitive help items where the
menu functions are described in detail. Help for each menu can be reached if
you open the pull down menu item. Then you have to press the F1 key. The
manager can be called in C:\PROTOPAS\TOOLS\CFGMANAG.EXE.
Short overview about Configuration Manager functions:
• View CI configuration (States Previewer, Screens, Parameters, Timers, FIT table)
• Trace and analyzing, trace file transfer to floppy
• Bitmap Previewer for BMP, PCX, ICN, DDU,JPG graphic or AVI video files
• Printer test programs
• Error Map configuration
• PCedit interface
• Parameterisation
• Integrated Windows Explorer and Regedit
• Windows context sensitive Help for each Menu and Dialog Item (F1 key)

Installation and Configuration Tools Font and Graphic utilities
Font and Graphic utilities

FONTEDIT.EXE
FontEdit.exe is a Windows program which is used to read, enhance and modify
characters from Windows font files. Windows font files which are currently in
use are typically placed in the directory WINNT\FONTS. These fonts cannot be
modified by FONTEDIT. If you want to modify those fonts you have to move
them via the Control Panel to a separate directory where they do not have
access from Windows anymore.
Syntax: FONTEDIT WINNTfontfile
The following graphic shows the main screen with one loaded NDC font
named "NDC-SA1.FON".

FON2ASC.EXE
Fon2asc.exe is used to extract WINNT font files to ASCII matrix font files.
The ASCII file can be used to modify or enhance characters of a font file via any
standard text editor. The modificated file can be reconverted to the *.FON
format via ASC2FON.EXE.
The ASCII file must have following header parameter:
Font - sets the font name which must match (case sensitive)
with parameter "NAME" of section [VIEWER_FONT_XXX]
Width - sets the character width
Height - sets the character Height.
Character XX - sets the character ASCII position (XX represents the hex
value of the position) and must exist for each defined
character.
Syntax:
FON2ASC fontfile > ASCIIfile
ASC2FON.EXE
Asc2Fon.exe converts ASCII matrix font files to WINNT font files. The file name
of the new font file is the same as the name specified behind the header
parameter ’Font’ of the ASCII file but included with extension *.FON.
Syntax:
ASC2FON [-SCREEN] [-PRINTER] ASCIIfile
Options:
-SCREEN Creates font files according ANSI standard
-PRINTER Creates font files according OEM ASCII standard

CPYNTFNT.EXE
Cpyntfnt.exe detects the current Windows display resolution than it copies and
registers fonts of the detected resolution in the Windows environment. Font files
(*.FON) will be automatically copied from directory
C:\PROTOPAS\FONTS\XXX (’XXX’ stands for 640x480, 800x600, 1024x768)
to the \WINNT\FONTS directory. Afterwards they will be automatically
registered for immediate access. Furthermore you can enable copying
resolution dependent Bitmaps or Icons from the C:\PROTOPAS\BITMAPS\XXX
resolution sub folder to C:\PROTOPAS\BITMAPS. The register and copy
processes are protocolled in log file "CPYNTFNT.INF" located in
C:\PROTOPAS. Optionally this tool registers GDI printer fonts that are required
for GDI print operation.
Syntax:
CPYNTFNT [-R] [-B] [-0] [-1] [-2] [-G] [fontfile]
Options:
-R Enables font installation with automatic detection
-B Enables copying Bitmaps or Icons in the selected or detected
resolution.
-G Registers all GDI printer fonts located in
C:\PROTOPAS\FONTS\GDI_PRT
-W Registers all kind of windows fonts located in
C:\PROTOPAS\FONTS\WEB
-0 Sets resolution 640x480
fontfile Registers a single font in the selected or detected resolution.
The call without parameter -0, -1 or -2 (CPYNTFNT -R) enables

automatic detect. The resolution of the current Windows display
setting is used.
This utility is called by the "Configuration Manager" where you can

use font registration via an user friendly dialog window. See main
menu "Update" and sub menu "Install Fonts and Bitmaps".

ASC2ICN.EXE
Description:
ASC2ICN is used to convert an ASCII icon file into a *.icn file.
Syntax:
ASC2ICN sourcefile [destfile]
If destfile is not specified, $tmp$.icn is used or ASC2ICN -I destfile with

stdin as the input
ICN2ASC.EXE
Description:
Icn2asc.exe can be used to extract ICN icon files to ASCII matrix files for modifi-
ations.
Syntax:
ICN2ASC.EXE ICNfile > destfile
EXAMPLE:
ICN2ASC.EXE 0000.ICN > 0000.txt
If you change the 'X's of the matrix file to 0 - F (1 digit hex value) you
get the specific color for the modified pixels. See also Table 7-3 Color
table for the color definitions.

ASC2PCC.EXE
Description:
ASC2PCC is used to convert an ASCII icon file into a *.PCC or *.PCX file.
Syntax:
ASC2PCC [-V] [-Wwidth] [-Hheight] [-Ttop] [-Lleft]
sourcefile [destfile]
If destfile is not specified, $tmp$.pcc is used or ASC2PCC -I [-V]

destfile with stdin as the input.

MFCFONT.EXE
This Utility can be used to create own Windows fonts that can be used for
screen display and GDI printing. Please press F1 button for detailed help
description how to use this tool.

Installation and Configuration Tools Analyzing utilities
Analyzing utilities
PROTLOG.EXE
ProtLog.exe analyzes the messages of the log file ’CCProt.LOG’ and inserts
structured descriptions of the message types and its fields.
Syntax:
PROTLOG CCProt.LOG > destinationfile
Options:
-D analyzes ProCash/DDC messages (DIEBOLD)
-S extracts messages for simulation
-L extracts download messages only (3...) useful for ndc-sim.dll
Font tools for journal and receipt printers

PRT-DOF.EXE
Prt-Dof.exe can be used to load native control sequences, resp. user defined
character sets into receipt or/and journal printers. You have to create an ASCII
file usually with the extension *.dof , which has to contain the control characters
that should be loaded into the printer. The format of this ASCII file is described
on the next pages.
Prt-Dof.exe can be used with the dot matrix printers ND71, ND98,
ND9A and the new series printers ND9x, TH21, TH22, TP06, TP07,
TP27 and TH30 printers.
IMPORTANT NOTE: For printers which are installed as a GDI
Windows printer, loading of user defined characters is not supported
via CSCW32 interface.
Syntax:
prt-dof <DEVICE ID> filename.dof [-Z]

Installation and Configuration ToolsFont tools for journal and receipt printer
Option: -Z This option is needed if you get time-out errors from CSC-W32 because
of large printer data. If this option is in use, the CSC-W32 command
TraPrint is called for each singe line. Without -Z option only one single
TraPrint command is called for the whole contents of the DOF file.
Important Note: You also have to create the DOF file with -Z option
if you use utility ASC-DOF.EXE or ND9C-DOF.EXE.
NOTE: Do NOT use the -Z option for TP06 and TP07 or TP27.
The DEVICE ID must be the logical name of the printer used

by CSCW32. The names which are typically used are JOURNAL1
for the journal printer and BON1 for the receipt printer.
The CSCW32 environment must be installed !
Structure and description of a download file for needle printers ND71 and ND9x:
All escape sequences must be entered in hex format !!!!!
Creation of an user-defined character file:

The file must be in the following format:
First line: /h 1b26024141
Next lines: /h 0900001f80200044008000440020001f800000
You can use any text editor you wish.
First line:
In the first line you must enter the load command ESC &, then set 02 for 2 bytes
(9 needles for each column) The next two digits specify the start position; the
last two digits specify the last character.
For example the entry 4141 means: Load one character to position 41H.

Next lines:
The next lines are the pixel control of each character. You can create 95 user-
defined characters from hex position 20H to 7EH in any style you like.
ND71: Use 9 columns for 10 and 12 cpi; 7 columns for 15 cpi.
ND9x: Use 5 columns for 10, 12 and 25 cpi; 7 columns for 15 cpi.
Note: Thermal printers ND9C, ND99, TP06, TP07, TP27, TH21, TH22
and TH30 need different formats. Those formats are described in
following sections.
The bit matrix of a 9-column character is shown here:
Columns 1 2 3 4 5 6 7 8 9
-------------------------
Needle 1 Byte1 7 0 0 0 0 0 0 0 0 0
Needle 2 Byte1 6 0 0 0 0 0 0 0 0 0
Needle 3 Byte1 5 0 0 0 0 0 0 0 0 0
Needle 4 Byte1 4 0 0 0 0 0 0 0 0 0
Needle 5 Byte1 3 0 0 0 0 0 0 0 0 0
Needle 6 Byte1 2 0 0 0 0 0 0 0 0 0
Needle 7 Byte1 1 0 0 0 0 0 0 0 0 0
Needle 8 Byte1 0 0 0 0 0 0 0 0 0 0
Needle 9 Byte2 7 0 0 0 0 0 0 0 0 0
Example 1:
Creation of the character A with 9 columns:
Columns 1 2 3 4 5 6 7 8 9
-------------------------
Needle 1 Byte1 7 0 0 0 0 1 0 0 0 0
Needle 2 Byte1 6 0 0 0 1 0 1 0 0 0
Needle 3 Byte1 5 0 0 1 0 0 0 1 0 0
Needle 4 Byte1 4 0 1 0 0 0 0 0 1 0
Needle 5 Byte1 3 0 1 0 0 0 0 0 1 0
Needle 6 Byte1 2 0 1 0 1 0 1 0 1 0
Needle 7 Byte1 1 0 1 0 0 0 0 0 1 0
Needle 8 Byte1 0 0 1 0 0 0 0 0 1 0
Needle 9 Byte2 7 0 1 0 0 0 0 0 1 0
When the bits are set in the desired positions, you should count in the following
way. For example in column two byte 1, the bits 0, 1, 2, 3, 4 are set.
Count 1+2+4+8+16 = 31 decimal = 1FH. In byte 2 only bit 7 is used. That means
128 in decimal and 80H. The needle control code is 1F80 for column two.

Two needles may not be set directly after another in the horizontal
line. The printer will, however, correct that itself.
code = set /h before each command line
col = how many columns
1b = byte 1
2b = byte 2
1 2 3 4 5 6 7 8 9
code col 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b
---------------------------------------------------------
/h 09 0000 1f80 2000 4400 8000 4400 2000 1f80 0000
For the ND9x printers the number of columns (col) must be specified
only for the first character.
Example 2:
Creation of the character 'A' with 7 columns:
Columns 1 2 3 4 5 6 7
-------------------
Needle 1 Byte1 7 0 0 0 1 0 0 0
Needle 2 Byte1 6 0 0 1 0 1 0 0
Needle 3 Byte1 5 0 1 0 0 0 1 0
Needle 4 Byte1 4 0 1 0 0 0 1 0
Needle 5 Byte1 3 0 1 0 0 0 1 0
Needle 6 Byte1 2 0 1 0 1 0 1 0
Needle 7 Byte1 1 0 1 0 0 0 1 0
Needle 8 Byte1 0 0 1 0 0 0 1 0
Needle 9 Byte2 7 0 1 0 0 0 1 0
1 2 3 4 5 6 7
code col 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b 1b2b
----------------------------------------------
/h 07 0000 3f80 4000 8400 4000 3f80 0000
Userdefined character sets can be activated via macro #CCT#.

Standard character sets can be set via macro #NCT#.

ASC2DOF.EXE
Asc2dof.exe converts characters which are created in an ASCII matrix file to the
hexa decimal byte definition of the *.DOF (DownLoadFile) which can be used
to load them with prt-dof.exe. The style of the ASCII files are the same as the
screen font files which are stored in C:\PROTOPAS\TOOLS\FONTS. The only
change is the number of columns and lines (needles) represented in the file as
"Width" and "Height". "Height" is divided in two bytes. The first byte has the
range from line 1-8 and the second byte is the ninth line. This results in Height
9 for a two byte character definition. The needle printer ND71 permits 9 and 7
columns and the printers ND98/ND9A/ND9E permit 5 and 7 columns. This utility
cannot be used for ND9C. See section “Font and Logo tools for printers” on
page 412 for ND9C utilities.
Syntax:
ASC2DOF [-Z] ASCIIfile > DOFfile
Example:
ASC2DOF ND98_7 > ND98_7.DOF

Example:
Creation of character 'A' in 7 and 5 columns:
Structure of the ASCII file with 7 Structure of the ASCII file with 5
columns characters: columns characters:
Font 7 columns Font 5 columns
Width 7 Width 5
Height 9 Height 9
Character 41 Character 41
..X.X.. .XXX.
.X...X. X...X
X.....X X...X
X.....X X...X
X.X.X.X XXXXX
X.....X X...X
X.....X X...X
....... .....
....... .....
After conversion with asc2dof.exe:

/h 41 3e00400088000000880040003e00/h 41 7e008800880088007e00
The number 41 is the hexadecimal position which is defined in the

ASCII file before. This is not needed for the downloading process. For
the character downloading process you need to add the ESC &
loading command and the number of columns as described in section
"Structure and description of the download file".

Installation and Configuration Tools Font and Logo tools for printers
DOF2ASC.EXE
Dof2asc.exe can be used to convert hexadecimal font files (*.dof), which are used
to load characters into the printer with utility prt-dof.exe, to an ASCII matrix file.
The matrix file can be edited with any standard editor.
Syntax:
DOF2ASC [-Z] doffile > filename
Example:
DOF2ASC ND9A.DOF > ND9A.ASC
This utility cannot be used for ND9C printer. For the ND9C printer you
have to use dof-nd9c.exe or nd9c-dof.exe. See section “Font and Logo
tools for printers” on page 412.
Font and Logo tools for printers

LDND9X.EXE
Ldnd9x.exe loads Fonts and user defined Logos into the receipt printers ND9x,
TP06, TP07, TP27 or journal printer TH30. Furthermore ldnd9x.exe can delete
logos and user defined fonts of ND99. The font and logo files are in a special
binary format. The printer ND99 needs files with the extension *.SWF for fonts
and *.LOG for logos, which can be extracted into matrix files for modifications
with utilities described later on. The new series printers ND9x or TH30 need files
with extension *.FNT for standard fonts, *.MOD for firmware and *.BMP for logo
bitmaps. TP07, TP27 and TP06 support *.BMP format only. To load font and
logo files into ND99, you need the configuration file LD_ND99.CFG and for the
ND9x printers you need the file LD_ND9X.CFG in the path
C:\PROBASE\CSCW32\FRM.
LD_ND99.CFG or LD_ND9X.CFG is divided into two sections named
[FONTS] and [LOGOS].
In these sections you have to specify the directory path where the Font and
Logo files are stored.

Font files with extension *.FNT are standard fonts which are loaded
in the standard area of the printer.
Fonts for the userdefined area can be created with the ASCII to DOF
utilities and must be loaded via PRT-DOF.EXE.

Contents example of LD_ND99.CFG for printer ND99:

[FONTS]
C:\PROBASE\CSCW32\FRM\FONT10.SWF
[LOGOS]
C:\PROBASE\CSCW32\FRM\LOGO1.LOG
C:\PROBASE\CSCW32\FRM\LOGO2.LOG
The space for Logos and Fonts are limited and can be read from the
test printout of the ND99. If a font or Logo reaches the maximum
space during the load process, it will not be recognised during the
load. But it can be verified after the load if you make a test printout
where you can see how many Fonts and Logos are successfully
loaded.
ND99 logos can be controlled via macros #LOGO1# - #LOGO9#.
User defined Fonts can be activated via macro #CCT#.
Standard Fonts can be set via macro #NCT#.
Contents example of LD_ND9X.CFG for printers ND9C, ND9D, ND9E, TH30:

[FONTS]
C:\PROBASE\CSCW32\FRM\FIRMW.MOD
C:\PROBASE\CSCW32\FRM\FONT_437.FNT
[LOGOS]
C:\PROBASE\CSCW32\FRM\LOGO1.BMP
C:\PROBASE\CSCW32\FRM\LOGO2.BMP
For ND9X printers logos can be controlled via macro #LOGO1#
With ldnd9x.exe you are able to load 4 Fonts and 10 Logos.
ATTENTION: If you need to load new firmware please make 100%

sure that the firmware file (*.MOD) you have configured is the right
one for the printer type you have connected. Wrong FW destroys
the printer. For (*.FNT) files it is the same.

Function description of LDND9X:

The loader can be started from any directory you like but it needs the CSCW32
environment. When you call the program it checks first if the file LD_ND99.CFG
(option -ND99) or LD_ND9X.CFG (option -ND9X) exist. Then it shows the
number of Fonts or Logos depending on which loading process is selected (See
parameter options for load and delete options). If option -ND99 is in use, the
next step deletes all existing fonts or Logos first before the load for the new fonts
or Logos will be started. If option -ND9X is used, the deleting process is skipped
and the loading process starts immediately. Each process will be displayed on
screen to show information whether the load is successfully finished or if parts
of the process fail.
Syntax call:
LDND9X
Options:
-ND99 need to be set for ND99 printer
-ND9X need to be set for ND9C, ND9D, ND9E or TH30 printers
-TP07 need to be set for TP07 or TP27 receipt printer (non GDI mode)
-TP06 need to be set for TP06 journal printer (requires option -J too)
-L deletes and loads Fonts
-G deletes and loads Logos (not supported for TH30)
-D deletes Fonts only (ND99 only)
-E deletes Logos only (ND99 only)
-J specifies device JOURNAL1
NOTE1: Logo loading via this utility is supported for ND99, ND9C, TP07
and TP06 printer.
NOTE2: For TP07, Tp27 only option -G (loading a LOGO) is supported.
For TP06 only options -G together with -J are supported.
As example for a 450 x 100 BMP, the printed size corresponds to
5,5cm * 1cm.
The TP07, TP27 and TP06 printers support loading of one Logo
only. Therefore only macros #LOGO# or #LOGO1# are supported
for the logo print.

ND99LOGO.EXE
Nd99logo.exe extracts binary logo files of ND99 into an ASCII matrix file. This text
file can be modified with any standard text editor. This utility is useful to make
modifications for some pixels of an existing logo to obtain a better logo quality.
The typical way to create Logos will be to draw a PCX graphic with a graphic
program. This utility can help you to tune your Logo.
Syntax:
ND99LOGO logofile > filename
The ASCII file must have the following header parameter:

Logo Type: - specifies the logo number which is used by the macro
#LOGO1# - #LOGO9#.
Logo Width: - specifies the width of the Logo in bytes. 1 byte represents
eight pixels in one line.
Logo Height: - specifies the Logo height. The number of lines represents
the Logo height.
Logo Name: - the file name of the logo (8.3 format) must be entered
there. The name will be printed in the test printout of ND99.
The ’Width’ and ’Height’ parameter should be in the range of

70 (560 pixel) and 200 (lines). This depends on the available memory
of the ND99.
ASC2LOGO.EXE
Asc2logo.exe converts ASCII logo files to the binary logo format for ND99
printers. See also utility ND99LOGO.EXE for the structure of the ASCII logo file
format.
Syntax:
ASC2LOGO ASCIIfile logofile

PCX2ASC.EXE
Pcx2asc.exe is used to convert *.pcc or *.pcx files into ASCII matrix files. This
ASCII file can be used as a source file for the conversion of ASC2LOGO.EXE
to a logo file format for the ND99 printer.
The header parameter must be changed to the format as described

by utility ND99LOGO.EXE. It is important that the value of parameter
’Width’ is divided by eight if you need it for the logo conversion,
because of the 1 byte steps for the logo width (1 byte represents eight
pixels).
Syntax:
PCX2ASC [-D] [-E] [-W] sourcefile
Options:
-D On CGF icons double horizontal pixels. On VGA icons
compress every 2 lines (24 -> 12 lines)
-E On CGF icons double lines 5 and 9 (12 -> 14 lines). On VGA
icons do not compress lines 9 and 17 if -D option is set
(24 -> 14 lines)
-Wsize Set horizontal size in characters.
ND99-ASC.EXE
Description:
Nd99-asc.exe extracts characters stored in *.swf format to ASCII format which
can be modified by the customer.
Syntax:
ND99-ASC FONTfile > ASCII file
Example:
ND99-ASC ARIAL10.SWF >ARIAL10

ASC-ND99.EXE
Description:
Asc-nd99.exe converts extracted characters stored in ASCII format back to the
*.swf format which has to be used to download the font to the ND99 printer.
Syntax:
ASC-ND99 ASCIIfile FONTfile
Example:
ASC-ND99 ARIAL10 ARIAL10.SWF
DOF-ND9C.EXE
Description:
Dof-nd9c.exe can be used to convert hexadecimal font files (*.dof) to an ASCII
matrix file. The ASCII matrix file can be edited with any standard text editor.
The ND9C and TH30 printer can load 5 character sizes: 10, 12, 14, 16, 20
with fixed Height = 22 pixels. The TH21 or TH22 needs three sizes: 10, 13, 18
with the fixed Height = 24 pixels.
Syntax:
DOF-ND9C [-Z] FONTfile > ASCIIfile
Example:
DOF-ND9C USR_CPI12.DOF > USR_CPI12.ASC
Example contents of a DOF file (character ’B’) for the ND9C printer:
/h 1c2603424210
/h 10000000c000c0ffffc0ffffc0c0c0c0c0c0c0c0c0c0c0c0c0c0c0c0
f3f3c07f3f803f3f000c0c00000000000000000000
If you have a printer that has a firmware version loaded older than
December 1999 the load sequence is /h 1b26 instead of /h 1c26.
DOF-ND9C.EXE supports /h 1b26 and /h 1c26 within a DOF file.
Use utility PRT-DOF.EXE to load the hexa decimal contents of a DOF

file into the ND9C, TH30 and TH21 or TH22 printer.

ND9C-DOF.EXE
Description:
Nd9c-dof.exe converts characters from an ASCII matrix file to the hexa decimal
byte definition of the *.DOF (DownLoadFile), which can be used to load them
with prt-dof.exe. Use utility dof-nd9c.exe to reconvert characters from the
hexadecimal format of a DOF file to an ASCII matrix format. The ND9C printer
needs five sizes to be loaded: Width = 10, 12, 14, 16, 20. The Height is fixed
and always 22 pixels. The TH21 or TH22 needs three sizes: 10, 13, 18 with fixed
height of 24 pixels. This makes sure that for all cpi sizes the characters are able
to be printed. Parameter "Character" represents the character postion. The
range of the character positions is between 21H - 7FH. Position 20H (SPACE)
is not allowed to be overloaded. This utility can be used for TH21, TH22 or TH30
as well.
Syntax:
ND9C-DOF [-Z] ASCIIfile > FONTfile
Example:
ND9C-DOF USR_CPI12.ASC > USR_CPI12.DOF
Example contents of an ASCII matrix file (character ’B’) for the ND9C printer:
Width 16
Height 22
Character 42
.XXXXXXXXX...... CPI macro reference:
.XXXXXXXXXX..... Width CPI macro
..XX.....XXX.... 10 17
..XX.....XXX.... 12 15
..XX......XXX... 14 14
..XX......XXX... 16 12
..XX.....XXX.... 20 10
..XX.....XXX....
..XXXXXXXX......
..XXXXXXXX......
..XX.....XXX....
..XX.....XXX....
..XX......XXX...
..XX......XXX... User defined character sets can be deleted via
..XX.....XXX....
..XX.....XXX....
ESC ’ (1B 27) with sequence "/h 1b27" using
.XXXXXXXXXX..... utility PRT-DOF.EXE.
.XXXXXXXXX......
................ (Supported with firmware since Dec. 1999)
................
................
................
If you have a printer that has a firmware version loaded older than
December 1999 the old load sequence /h 1b26 has to be used
instead of /h 1c26. ND9C-DOF.EXE always converts to /h 1c26.

Logo print with ND9E
The ND9E printer is able to print one logo that can be stored into the E-PROM
of the printer. The utility ND9E-DOF.EXE can be used to create hexa decimal
sequences that can be loaded via PRT-DOF.EXE into the printer.
ND9E-DOF.EXE
Description:
Nd9e-dof.exe can be used to convert logo data from ASCII format to hexa
decimal sequences in a DOF file.
Syntax:
ND9E-DOF ASCIIfile > DOFfile
Example:
ND9E-DOF STDLOGO.ASC > STDLOGO.DOF
How to Load one logo:
You can load two different kinds of logos either standard or extended format:
Standard format: Width: 144; Height: 104 (13 lines x 8 pixel or smaller)
Extendend format: Width: 200; Height: 144 (18 lines x 8 pixel or smaller)
Step1: Create a 16 color PCX graphic in Z-Soft Paintbrush format for
standard logo within range 144 x104 or extended logo within
200 x 144 (width x height).
Step2: Use utility PCX2ASC.EXE to convert the PCX graphic to an ASCII file.
Step3: Use utility ND9E-DOF.EXE to convert the ASCII matrix file to a DOF
that contains hexa decimal sequences for the printer.
Step4: Use utility PRT-DOF.EXE to load the DOF contents into the printer.
NOTE: See also detailed descriptions of PRT-DOF.EXE and PCX2ASC.EXE
in the previous sections.
How to print the logo:

The hexa decimal sequence to print the logo is 1b6f. This sequence can be
inserted in a DOF file as: /h 1b6f0d0a0c
To print the logo via the application you can define an own macro in section
"..\CCOPEN\CCPRTFW\RECEIPT_MACROS" like MYLOGO = \1b\6f that can
be configured via parameter RECEIPT_PAGE_HEADER = #MYLOGO# in
CUSTOM.PPF.

Font utilities for RJ03 series printers
DOF-RJ03.EXE
Description:
Dof-rj03.exe can be used to convert hexadecimal font files (*.dof) to an ASCII
matrix file. The ASCII matrix file can be edited with any standard text editor.
The thermal printers TP06 (journal) and TP07/TP27 (receipt) need two
character sets with pixel format: 10x17 and 14x24 (width x height). The dot
matrix (needle) printers NP06 (journal) and NP07 (receipt) need two character
sets with pixel format: 7x9 and 9x9 (width x height) (see option -N). The RJ03
series printers accept loading of user defined characters in range 0x20H -
0xFFH.
IMPORTANT NOTE: If TP07 or TP27 is installed as a GDI Windows printer,
user defined characters cannot be loaded.
Syntax:
DOF-RJ03 [-N] FONTfile > ASCIIfile
Options:
-N must be set for 7x9 or 9x9 fonts needed for dot matrix printers
NP06 or NP07.
Example 1:
DOF-RJ03 USR10x17.DOF > USR10x17.ASC
Example 2:
DOF-RJ03 -N USR7x9.DOF > USR7x9.ASC

RJ03-DOF.EXE
Description:
Rj03-dof.exe converts characters from an ASCII matrix file to the hexa decimal
byte definition of the *.DOF (DownLoadFile), which can be used to load them
with prt-dof.exe. Use utility dof-rj03.exe to reconvert characters from the
hexadecimal format of a DOF file to an ASCII matrix format. The RJ03 series
thermal printers TP06 (journal) and TP07/TP27 (receipt) need two character
sets, which needs to be loaded: 10x17 and 14x24 (width x height). The dot
matrix (needle) printers NP06 (journal) and NP07 (receipt) need two character
sets in pixel format: 7x9 and 9x9 (width x height).
The printers accept to load characters in range 20H - FFH.
IMPORTANT NOTE: If TP07 or TP27 is installed as a GDI Windows printer,
user defined characters cannot be loaded.
Syntax:
RJ03-DOF [-N] ASCIIfile > DOFfile
Options:
-N must be set for 7x9 or 9x9 fonts needed for dot matrix printers
NP06 or NP07.
See examples on the following page ...

Example 1:
RJ03-DOF USR14x24.ASC > USR14x24.DOF
Example contents of an ASCII matrix file (character ’B’) for the TP07 printer:
Width 14
Height 24
Character 42
..............
..............
.XXXXXXXXX....
.XXXXXXXXXX...
..XX.....XXX..
..XX.....XXX..
..XX......XXX.
..XX......XXX.
..XX.....XXX..
..XX.....XXX..
..XXXXXXXX....
..XXXXXXXX....
..XX.....XXX..
..XX.....XXX..
..XX......XXX.
..XX......XXX.
..XX.....XXX..
..XX.....XXX..
.XXXXXXXXXX...
.XXXXXXXXX....
..............
..............
..............
..............
Example 2:
RJ03-DOF -N USR7x9.ASC > USR7x9.DOF
Example contents of an ASCII matrix file (character ’B’) for the NP06 printer:
Width 7
Height 9
Character 42
.......
.XXXX..
.X...X.
.X...X.
.XXXX..
.X...X.
.X...X.
.XXXX..
.......

Installation and Configuration Tools Miscellaneous tools
Miscellaneous tools
WRITE-ID.EXE
Write-ID.exe can be used to write data on track1,2 or/and 3 of ID cards.
Therefore you need a card reader which is able to write on the ID card tracks.
The data definition of the tracks has to be edited in a batch file e.g.
’write_id.cmd’. The batchfile must contain the path of the program and as
parameters 3 string definitions which indicates the track data.
Example:
You want to write track 2 data on the card but track 1 and 3 are empty:
Syntax of the batch file:
c:\protopas\tools\Write-Id "" "99999999999=999999999" ""
The WRITE-ID.EXE tool cannot work if the ATM is in service mode

or/and a card insert job has been already started.
MDS2WNC.EXE
MDS2WNC.exe can be used to replace MDS i series status codes or/and
Maintenance Data of parameter DDC_MDS_STATUS or/and M_DATA of
configuration file CCERRMAP.INA to CSCW32 StClass and StCodes for Wincor
Nixdorf ATM’s. Error Class and Error Code (StClass, StCode) will be copied and
concatenated from the section line and will be inserted in the value field of
parameter DDC_MDS_STATUS or M_DATA.
Syntax:
MDS2WNC [-M] [-D] sourcefile destfile
Options:
-D Inserts CSCW32 StClass & StCode to DDC_MDS_STATUS
-M Inserts CSCW32 StClass & StCode to M_DATA
Example:
MDS2WNC -M -D C:\PROTOPAS\CONF\CCERRMAP.INA CCERRMAP.NEW

COMPREGF.EXE
COMPREGF.exe compares an extracted Regfile (REGEDIT4 format) with the
contents of the Windows registry.
Syntax:
COMPREGF -Rregfile [-Llogfile]
Options:
-Rregfile specifies the extracted registry file
(must be extracted in ASCII text (REGEDIT4) format)
-Llogfile specifies the logfile name where the differencies are stored
Example:
COMPREGF -Rwincor.reg -Lwincor.log
PRT-RAW.EXE
PRT-RAW.exe uses the CSCW32 interface to print macros and printer data from
an ASCII file to the selected printer station (BON1, JOURNAL1 or BELEG1). It
can be used to preset printers with default settings before application start or if
you like to test the printer functionality.
Syntax:
PRT-RAW -PDEVICE -Ffilename
Options:
-PDEVICE DEVICE specifies the device station:
BON1 - receipt printer
JOURNAL1 - journal printer
BELEG1 - document printer
-Ffilename specifies the filename that contains the printer data.
Example:
PRT-RAW -PBON1 -Ftest-bon.txt
Contents of the print data file (test-bon.txt) could be:
#CPI12#TEST DATA TO PRINT#CR##LF##FF#

PRINTRAW.EXE
PrintRaw.exe calls the "Print" or "PrintRaw" method of the ProTopas API to print
macro sequences and printer data configured via a formular number or from an
ASCII file to the requested printer destination specified via parameters.
Syntax:
PRINTRAW [-Fnnn][-E] -Pprinter
Options:
Parameter -Fnnn is optional and enables the formular "Print" method of
ProTopas. If the parameter is NOT set, the "PrintRaw" method of the ProTopas
API is used (on the document printer "Eject" is called after the print).
-Fnnn nnn - specifies a formular number that has to be configured via
parameter MSGnnn in follwing registry locations depending on
which printer type has been selected:
..\LYNXPAR\PRINTER\RECEIPT
..\LYNXPAR\PRINTER\JOURNAL
..\LYNXPAR\PRINTER\DOCUMENT
-Pprinter printer - specifies the printer type:

REC - receipt printer
JRN - journal printer
DOC - document printer
JOU - E-journal destination
-E Calls ProTopas Eject() method if -PREC is set
Example 1:
The following command line initiates a formular "Print" on receipt using printer data
defined via parameter MSG400 in section ..\LYNXPAR\PRINTER\RECEIPT.
PRINTRAW -F400 -PREC
Contents of parameter MSG400 could be (max. 1024 characters):
#CPI12#FORMULAR PRINT DATA#CR##LF##FF#
Example 2:
The following command line initiates a "PrintRaw" on the journal printer using the
printer data defined in C:\PROTOPAS\RAWDATA.TXT.
PRINTRAW -PJRN
Contents of file rawdata.txt could be (max. 1024 characters):
#CPI12#TEST RAWDATA PRINT#CR##LF#

SETHWPPF.EXE
SETHWPPF.exe is called once during the installation phase in the batch file
UPDCONF.CMD. Depending on the configured WOSA device service it
disables the paper journal if the WOSA journal printer service is not configured
to be loaded.
It supports following WOSA service names: PRJ,PRR,PRD,DEP.
Syntax:
SETHWPPF -DWOSA-SERVICE1,WOSA-SERVICE2,WOSA-SERVICEn,...
Options:
-DWOSA-SERVICEx specifies the WOSA service names that can be
configured in parameter CCBase in section
..\CCOPEN\RESTART\APPLICATION_1
-T Sets parameters for Triple DES
-GND9G,TH21,TH22,TH97 Checks if the printers în the list are installed as
GDI printers and sets the required parameters for
GDI print operation in ProCash/NDC or
ProCash/DDC.
Example:
SETHWPPF -DPRJ,PRR,PRD,DEP -T -GND9G,TH21,TH22,TH97
Function Description for -D option:

When the utility is called following functions are performed:
1. It checks if PRJ, PRR, PRD, DEP is configured in Registry parameter CCBase.
2. It sets Parameter ACTIVE = N for the sections [SERVICES_PRJ], [SERVICES_PRR], [SERVICES_PRD],
[SERVICES_DEP] in CUSTOM.PPF and parallel the value is set in the registry if the belonging service is
not configured.
3. If the PRJ service is not configured it sets in addition to parameter ACTIVE parameter
PAPER_JOURNAL = 0 in section [JOURNALPRINTER] of CUSTOM.PPF and parallel it
sets the value in the registry.
Function Description for -T option:
1. Calls batch program Sop3Des.bat to set parameters for ProSop Triple DES key input. Refer also to
Abschnitt ”Enable Triple DES operation” on page 338.
Function Description for -G option:
1. Includes the GDI Printer Overlay Framework (dcPrtGdi.DLL) in the repository configuration for the Receipt
or/and Document printer. Scans the CSC-W32 printer configuration. If a valid GDI printer configuration is
found in the CSC-W32 section, the repository configuration for the detected printer is modified.
In addition the Windows printer name is set for parameter PRINTER_NAME in section
GDI_XXX_PRINTER (xxx = REC or DOC) of "CUSTOM.PPF".

INITEPP.EXE
InitEpp.exe initializes the EPP and deletes all loaded keys. After INITEPP.EXE
has been called with option -D and -E, the security keys have to be entered via
SOP function.
If INITEPP.EXE is called with option -I, just EPP information is displayed, the
status of the EPP will not be changed.
Syntax:
INITEPP [-D -E] [-I]
Options:
-D calls CSC-W32 function CscEdmInit() to initialize the EPP
-E calls CSC-W32 function CscEdmExport() after CscEdmInit() to
remove the key names from the EPP. This function returns
successfully if an EPP V4 or higher is installed.
"EPP export error" is returned if the function call is not supported
because of an old EPP version. This parameter has to be set
together with parameter -D
-I displays detailed information about EPP Type, Status, Capabilities
and the loaded Firmware Version
EXTERRMP.EXE
ExtErrMp.exe can be used to convert the sections of CCERRMAP.INA to a new
registry structure where the different error classes from section [CLASS] are
grouped to devices in a new section [DEVICES]. The tool can also be used to
split all error classes from an existing CCERRMAP.INA to multiple files. Each
file is named as the class name.
Syntax:
EXTERRMP [-Soldfile -Eoldfile] > newfile
Options:
-S Creates a new errmap file where the old error mapping
registry format is converted to section [CLASS\...] and
[DEVICES\...]
-E In addition to option -S, multiple files of each class are created,
where the filename is the class name.

Installation and Configuration Tools Simulation utilities
Simulation utilities
HOSTSIM.EXE
Hostsim.exe is a windows program which can be started parallel to the running
application to simulate several host messages and ’Online’ - ’Offline’ events.
After the program has been called, the following window appears on the screen:
If you select "Enter Message" you get a text input field on the bottom line. Any
valid host to terminal message can be entered.
Example entry: 1\1c\1c\1c4
The backslash (\) for the field separator (1c) must be entered via
[STRG] + [ALT] + [\]
After entering the message you have to click on the ’Send Message’ button,
then the message is send to the communication framework.
If you press "Select Message" you get a new dialog window where you can
select a message that you like to be sent. You have to create your own message
list in a separate ASCII file named "NDC-SIM.MSG" stored in "C:\PROTOPAS".
Each line should contain one host command (without leading spaces) only.

Installation and Configuration Tools Simulation utilities
MFCDLG.EXE
MfcDlg.exe is a dialog window where you can enter a screen number which is
displayed immediately parallel to the running customer application. This is
useful to check specific screens for its contents and availability.
The program shows the following dialog window on the screen:
MFCVAR.EXE
MfcVar.exe is a windows program which shows the entered steps and contents
of variables (e.g. Operation Code buffer) for the actual step.
The program shows the following window on the screen:

Installation of communication SW Installation of Eicon Wan Adapter
Installation of communication SW
This section describes how to install and configure the software of network
cards and communication add on products.
Installation of Eicon Wan Adapter

Wincor Nixdorf currently uses the EICON card for X.25 native and SNA connec-
tions. For SNA you have to install the add on product Microsoft SNA Server
(Workstation).
Types of EICON cards

Wincor Nixdorf has released model EC/PC, C21 and S51 card. In the first half
of 2000 the new C91 board will be released which will not be supported in the
DOS environment. The release V4R2 supports the EC/PC, C21 and S51 cards
under WindowsNT 4.0 with service pack 3 or higher. You have to use a driver
update if your PC has a Pentium II or III processor. This patch (ECNB.SYS
23.07.98 4.2 Build 88) is included in release V4R2S1.
The S51 card was released for the installation of OS/2.
Internet links
EICON TECHNOLOGY
http://www.eicon.com/
WINCOR NIXDORF INTRANET

BS P42 Software integration and Pilot support
http://seeus.pdb.sni.de/ftp-user3/index.htm

Installation
Select "SETTINGS" from the Windows "START" button. Open "CONTROL

PANEL" and double click "NETWORK". Go to folder "ADAPTERS" and click
"ADD".
Now click on HAVE DISK...

The INSERT DISK window appears and prompts for a path to the EICON
software:
The next window lets you choose a software variant. Just click OK.

Now you have to select "AUTOMATIC" or "MANUAL" installation. For PnP OS

systems you can use use the automatic installation procedure. The system
automatically detects the card and defines the hardware resources. "Manual"
will be used in systems without PnP capabilities or if the automatic detection
fails or if the card has to have special resources. In that case you will have to
select the card type and assign its resources manually.
The next dialog box is just an information window in case if you have selected
"Automatic" installation. Just click OK. If the card could not be detected
automatically you have to use the manual setup for configuration.

Now you will be asked for the destination directory and Installation Group:
After selecting ’OK’ the software will be installed on your hard disk.

The results of the automatic detection are displayed in the dialog window
"DETECTION RESULTS". If the parameters for IRQ and/or I/O address are not
shown, manual installation is recommended. Comments in the lower part
maybe helpful for error analysis.
Now run the EICON configuration program by clicking Yes in the following
window.

Now you can configure your EICON card and the protocols. Specific sections
can be selected inside the directory structure. The dependent data is displayed
on the right side and can be changed. Please ask your network administrator
for the relevant parameters of protocol configuration. The protocol configuration
of the card can be saved with the function "FILE-IMPORT". By doing this, the
configuration set can be used in other systems.
Note: Hardware settings, like I/O address and IRQ, are not overwritten.

...window and packet size...

In the next dialog box you have to set the physical line settings. An important
setting is the field "DATA ENCODING", where you have to set NRZ or NRZI.
The clocking setting is usually "EXTERNAL".
After the configuration changes it is neccessary to save the data.
The last dialog asks you if you want to install the EICON WAN services for
Routers, PAD's and so on. Select the NO button at this time.

Several settings have to be done from the application side. These are for
instance Local and remote address, buffer sizes and call user data.
Testing connection
From the DOS command prompt you can call some test programs. The call
"ECCARD START" is used to start the EICON service.
"ECCARD STOP" disables the EICON service.
With command "ECCARD STATUS" you get information of the line activity.

Tables
Tables
Table 1: External Products . . . . . . . . . . . . . . . . . . . . . . 31
Table 2: Components on "ProBase/C CD" . . . . . . . . . . . . . . 31
Table 3: Core products and AddOns on "J/Install CD" . . . . . . . . 32

Table 4: Structure of the Customizing Media . . . . . . . . . . . . . 41
Table 5: Optional Parameters (NDC) . . . . . . . . . . . . . . . . . 111
Table 6: Miscellaneous Features I (DDC) . . . . . . . . . . . . . . . 113
Table 7: Miscellaneous Features II (DDC) . . . . . . . . . . . . . . . 114
Table 8: Miscellaneous Features III (DDC) . . . . . . . . . . . . . . 115
Table 9: SUnsupported timers by ProCash/NDC-DDC . . . . . . . . 122

Table 10: RGB values for 16 standard colors . . . . . . . . . . . . . . 123
Table 11: Screen parameters reference table . . . . . . . . . . . . . 126
Table 12: Parameters supported in language banks (DDC only) . . . . 146

Table 13: Variables and formats for event and error messages . . . . 148
Table 14: Hardware Configuration Parameters (NDC) . . . . . . . . . 150
Table 15: Hardware Configuration Parameters (DDC) . . . . . . . . . 152
Table 16: Default NDC font names . . . . . . . . . . . . . . . . . . . 271
Table 17: Default DDC font names . . . . . . . . . . . . . . . . . . . 271
Table 18: DDC resolution dependent values for "SIZE" and "HEIGHT" 273
Table 19: NDC resolution dependent values for "SIZE" and "HEIGHT" 274
Table 20: Standard NDC and DDC font identifiers . . . . . . . . . . . 275
Table 21: Default settings for NDC and DDC fonts . . . . . . . . . . . 276
Table 22: List of files in sub folder \BAS . . . . . . . . . . . . . . . . 313
Table 23: List of files in sub folder \BATCH . . . . . . . . . . . . . . . 314
Table 24: List of files in sub folder \CDM . . . . . . . . . . . . . . . . 314

Tables
Table 25: List of files in sub folder \CCD . . . . . . . . . . . . . . . . 315
Table 26: List of files in sub folder \CHQ . . . . . . . . . . . . . . . . 315

Table 27: List of files in sub folder \CRS . . . . . . . . . . . . . . . . 316
Table 28: List of files in sub folder \EMV . . . . . . . . . . . . . . . . 316
Table 29: Error class files of folder \CCERRMAP . . . . . . . . . . . . 317

Table 30: List of files in sub folder \WEB\CONF . . . . . . . . . . . . 317
Table 31: List of files in sub folder \WN . . . . . . . . . . . . . . . . . 317
Table 32: List of files in sub folder \NCR\XFS30 . . . . . . . . . . . . 317
Table 33: List of files in sub folder \DIEBOLD\XFS30 . . . . . . . . . 317
Table 34: List of files in sub folder \FLX . . . . . . . . . . . . . . . . . 318
Table 35: List of files in sub folder \ETS . . . . . . . . . . . . . . . . 318

Table 36: List of files in sub folder \BAS . . . . . . . . . . . . . . . . 319
Table 37: List of files in sub folder \BATCH . . . . . . . . . . . . . . . 320
Table 38: List of files in sub folder \CDM . . . . . . . . . . . . . . . . 320

Table 39: List of files in sub folder \CCD . . . . . . . . . . . . . . . . 321
Table 40: List of files in sub folder \CHQ . . . . . . . . . . . . . . . . 321
Table 41: List of files in sub folder \CRS . . . . . . . . . . . . . . . . 321
Table 42: List of files in sub folder \EMV . . . . . . . . . . . . . . . . 321
Table 43: List of files in sub folder \WEB\CONF . . . . . . . . . . . . 321
Table 44: List of files in sub folder \WN . . . . . . . . . . . . . . . . . 322
Table 45: List of files in sub folder \NCR\XFS30 . . . . . . . . . . . . 322
Table 46: List of files in sub folder \DIEBOLD\XFS30 . . . . . . . . . 322
Table 47: List of files in sub folder \FLX . . . . . . . . . . . . . . . . . 323
Table 48: List of files in sub folder \ETS . . . . . . . . . . . . . . . . 323
Table 49: Error parameter block of CCERRMAP . . . . . . . . . . . . 324
Table 50: CSC-W32 and XFS class assign table . . . . . . . . . . . . 328

Tables
Table 51: XFS30 - CSC-W32 class assign table . . . . . . . . . . . . 329
Table 52: Card less transaction parameters . . . . . . . . . . . . . . 341

Table 53: Card less parameter fields . . . . . . . . . . . . . . . . . . 342
Table 54: Parameter fields for IDLE_TIMEOUT . . . . . . . . . . . . 343
Table 55: Transaction Framework Error Table . . . . . . . . . . . . . 368

Table 56: Cash Dispenser Framework Error Table . . . . . . . . . . . 371
Table 57: Cash Dispenser return code table . . . . . . . . . . . . . . 372
Table 58: Transaction Framework Error Table . . . . . . . . . . . . . 373
Table 59: Registry cross link [STARTUP] . . . . . . . . . . . . . . . . 374
Table 60: Registry cross link [START_APPLICATION] . . . . . . . . . 375
Table 61: Registry cross link [DEFAULT] . . . . . . . . . . . . . . . . 375

Table 62: Registry cross link [CCProtFW1] . . . . . . . . . . . . . . . 375
Table 63: Registry cross link [MODEM] . . . . . . . . . . . . . . . . . 376
Table 64: Registry cross link [SERIAL] . . . . . . . . . . . . . . . . . 377

Table 65: Registry cross link [PROTOCOL\PROJECT] . . . . . . . . . 377
Table 66: Registry cross link [HARDWARE_CONFIGURATION] (DDC) 378
Table 67: Registry cross link [HARDWARE_CONFIGURATION] (NDC) 379
Table 68: Registry cross link [LYNXCI_PARAMETER] . . . . . . . . . 381
Table 69: Registry cross link [LYNXCI_TIMER] . . . . . . . . . . . . . 381
Table 70: Registry cross link [LYNXCI_EMV] . . . . . . . . . . . . . . 382
Table 71: Registry cross link [EMV_TAGS] . . . . . . . . . . . . . . . 382
Table 72: Registry cross link [CASH_DISPENSER] . . . . . . . . . . 383
Table 73: Registry cross link [COIN_DISPENSER] . . . . . . . . . . . 385
Table 74: Registry cross link [BARCODE] . . . . . . . . . . . . . . . 385
Table 75: Registry cross link [DEPOSIT] . . . . . . . . . . . . . . . . 386
Table 76: Registry cross link [CARD_READER] . . . . . . . . . . . . 386

Tables
Table 77: Registry cross link [ELECTRONIC_JOURNAL] . . . . . . . 387
Table 78: Registry cross link [JOURNALPRINTER] . . . . . . . . . . 387

Table 79: Registry cross link [JOURNAL_FONT_XXX] . . . . . . . . . 387
Table 80: Registry cross link [RECEIPTPRINTER] . . . . . . . . . . . 389
Table 81: Registry cross link [RECEIPT_FONT_XXX] . . . . . . . . . 389

Table 82: Registry cross link [DOCUMENTPRINTER] . . . . . . . . . 390
Table 83: Registry cross link [DOCUMENT_FONT_XXX] . . . . . . . 390
Table 84: Registry cross link [VIEWER] . . . . . . . . . . . . . . . . 391
Table 85: Registry cross link [SNA] . . . . . . . . . . . . . . . . . . . 391
Table 86: Registry cross link [SNA_PROJECT] . . . . . . . . . . . . 391
Table 87: Registry cross link [SNA_PROJECT_INITSELF] . . . . . . . 392

Table 88: Registry cross link [X25] . . . . . . . . . . . . . . . . . . . 392
Table 89: Registry cross link [X25_PROJECT] . . . . . . . . . . . . . 393
Table 90: Registry cross link [TCPIP_PROJECT] . . . . . . . . . . . 394

Table 91: Registry cross link [TOPMSG] . . . . . . . . . . . . . . . . 394
Table 92: Registry cross link [CUSTMSG] . . . . . . . . . . . . . . . 394
Table 93: Registry cross link [LYNXCI_SCREEN] . . . . . . . . . . . 395
Table 94: Registry cross link [SCREEN_XXX] . . . . . . . . . . . . . 396
Table 95: Registry cross link [OPERATOR_SCREENS] . . . . . . . . 396
Table 96: Registry cross link [APPLICATION_XXX] . . . . . . . . . . 397
Table 97: Registry cross link [APPLICATION_XXX] part 2 . . . . . . . 398
Table 98: Registry cross link [DDC_DEPOSIT_EMULATION] . . . . . 398

Figures
Figures
Figure 1: Product Overview . . . . . . . . . . . . . . . . . . . . . 30
Figure 2: ProBase/C Installation Medias . . . . . . . . . . . . . . 35
Figure 3: J/Install Installation medias . . . . . . . . . . . . . . . . 39

Figure 4: PARAC Start window . . . . . . . . . . . . . . . . . . . 309
Figure 5: PARAC Update window . . . . . . . . . . . . . . . . . . 309
Figure 6: PARAC Finish window with return code (0) . . . . . . . . 309
Figure 7: PARAC Finish window with error return code . . . . . . . 310
Figure 8: Workbench of PCEDT . . . . . . . . . . . . . . . . . . 311
Figure 9: ETS PIN entry . . . . . . . . . . . . . . . . . . . . . . 351

Figure 10: ETS transaction selection . . . . . . . . . . . . . . . . . 352
Figure 11: ETS amount entry . . . . . . . . . . . . . . . . . . . . 352

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
DDC DIEBOLD Direct Connect (equals 911/912 Protocols)
DES Data Encryption Standard
EBCDIC Extended Binary Coded Decimal Interchange Code
ETS Encrypting Touch Screen
FDK Function Display Key
FIT Financial Institution Table
ID IDentification
IDCU ID Card Unit
MAC Message Authentication Code
MDS Modular Delivery System
NCR National Cash Register
NDC NCR Direct Connect

Abbreviations
OAR Open Account Relationship
PAN Primary Account Number
PC Personal Computer
PIN Personal Identification Number
POS Point of Sales (Cash Registers)
QLLC Qualified Logical Link Control
SDLC Synchronous Data Link Control
SNA System Network Architecture
PU Physical Unit
LU Logical Unit
SSCP System Server Control Point
PLU Primary Logical Unit
TABS Total Automatic Banking System
PPF Parac Parameter File
CFGM ProCash-NDC/DDC Configuration Manager

Related publications
Available manuals
Basically all the manuals you need to get information about configurations and
functionality of ProCash/DDC, ProConsult/DDC, ProDevice (WOSA),
CSC-W32 and AddOn products are available on the product cd.
Sub folder: \DOC\NDC-DDC\
ProCash/DDC & ProCash/NDC

DESIGNATION VERSION ORDER NUMBER
ProCash/DDC User Guide manual 3.1/20 (PDF file)
ProCash/NDC User Guide manual 3.1/20 (PDF file)
ProFlex/NDC-DDC Programming Guide 3.1/20 (PDF file)
Protopas Module Construction Kit 5 (PDF file)
Programming Guide
Protopas Framework Documentation 5 (PDF file)
Programming Guide
Protopas Host Protocol and 5 (PDF file)
Communication Frameworks
Programming Guide
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.

Related publications
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/DDC User Guide manual
Provides detailed function description about ProCash/DDC operation and DDC
Host to terminal and Terminal to Host messages (Write Commands, Function
Commands, Operational Commands, Status messages, etc.).
ProCash/NDC User Guide manual
Provides detailed function description about ProCash/NDC operation and NDC
Host to terminal and Terminal to Host messages (Download Commands, Trans-
action Request and Reply messages, Terminal Commands, Status messages,
etc.).
ProFlex/NDC-DDC Programming Guide
Describes function details of the Addon product ProFlex/NDC-DDC.
It gives detailed programming descriptions for developers how to set up the
transaction flow and how to install and configure the product for a host
connection.

Last Page
Published by
Diebold Nixdorf
Heinz-Nixdorf-Ring 1
D-33106 Paderborn
Germany
www.dieboldnixdorf.com
© Copyright Wincor Nixdorf International GmbH
All product names are registered trademarks of Wincor Nixdorf International

GmbH.
All rights reserved, particularly in relation to the grant of a patent or the
registration of a utility model.
Subject to availability and technical modifications.
Published in Germany, September 11, 2018.

ProCash NDC-DDC InstallationManual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ProCash NDC-DDC InstallationManual

Uploaded by

Copyright:

Available Formats

Installation Guide

Document version: 001

copyright © Wincor Nixdorf International GmbH, 2018 1

Names and Other Data

copyright © Wincor Nixdorf International GmbH, 2018 2

Software Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

copyright © Wincor Nixdorf International GmbH, 2018 3

PROEINFO installation log folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Parameter Configuration Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

copyright © Wincor Nixdorf International GmbH, 2018 4

Barcode Reader framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

copyright © Wincor Nixdorf International GmbH, 2018 5

– Buffer size in send direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

copyright © Wincor Nixdorf International GmbH, 2018 6

– SSL Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

copyright © Wincor Nixdorf International GmbH, 2018 7

Play videos in full screen mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

copyright © Wincor Nixdorf International GmbH, 2018 8

MACing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

copyright © Wincor Nixdorf International GmbH, 2018 9

Guide Light flash rate control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

copyright © Wincor Nixdorf International GmbH, 2018 10

Send cash low message only if whole denomination low . . . . . . . . . . . 203

copyright © Wincor Nixdorf International GmbH, 2018 11

Disable printing on retracted envelopes . . . . . . . . . . . . . . . . . . . . . . . . 228

copyright © Wincor Nixdorf International GmbH, 2018 12

Journal Spooler reset sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

copyright © Wincor Nixdorf International GmbH, 2018 13

Printer character mapping table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

copyright © Wincor Nixdorf International GmbH, 2018 14

Supported US common AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Parameter Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309

copyright © Wincor Nixdorf International GmbH, 2018 15

PCEDT - PARAC Parameter Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

copyright © Wincor Nixdorf International GmbH, 2018 16

Specify cursor character for input position . . . . . . . . . . . . . . . . . . . . . . . . . 345

Software updates via SOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

copyright © Wincor Nixdorf International GmbH, 2018 17

Start and Stop Application services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Application Error Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368

Registry Cross Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Installation and Configuration Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 399

Installation of communication SW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Related publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

copyright © Wincor Nixdorf International GmbH, 2018 18

copyright © Wincor Nixdorf International GmbH, 2018 19

copyright © Wincor Nixdorf International GmbH, 2018 20

Since December 2012 until October 2013:

Since June 2012 until December 2012:

Since May 2011 until June 2012:

Since March 2011 until May 2011:

copyright © Wincor Nixdorf International GmbH, 2018 21

• New section ”Changing Network settings under restricted User” on

Since November 2010 until March 2011:

Since October 2010 until November 2010:

Since April 2010 until October 2010:

Since January 2010 until April 2010:

Since June 2009 until January 2010:

Since August 2008 until June 2009:

copyright © Wincor Nixdorf International GmbH, 2018 22

Since May 2007 until August 2008:

copyright © Wincor Nixdorf International GmbH, 2018 23

Since July 2006 until May 2007:

Since September 2005 until July 2006: