TP 820803

PRELIMINARY - DRAFT COPY
Tue Apr 08 15:32:44 2003
Agilis NDx™ Configuration Guide

TP-820803-001B PD 5371
Tue Apr 08 15:32:44 2003
Document History
Document Number Date Remarks

TP-820803-001A 1/2003 Original edition - Version 1.0 - Diebold ix Series
and foreign vendor Terminals
TP-820803-001B 3/2003 Version 1.1 - Diebold Opteva™ Series terminal
hardware information added
Copyright protection is claimed for each revision listed in the document history, as of the date indicated.
Any trademarks, service marks, product names or company names not owned by Diebold that appear in this
document are used for informational purposes only and Diebold claims no rights thereto, nor does such use indicate
any affiliation with or any endorsement of Diebold or Diebold products by the owners thereof.
This document contains proprietary information. If the document pages state the information is confidential
(or words of similar import), then this document is intended solely for the use of the copyright owner’s
employees or other personnel expressly authorized in writing by the copyright owner. Other uses of this
information without the express written consent of the copyright owner are prohibited. This document should
be treated as confidential material for security reasons. Any unauthorized disclosure or use of confidential
material may violate Section 1832 of Title 18 of the United States Code as well as other laws, and may be
punishable by fine and imprisonment.
The information contained in this document is subject to change without notice. When using the document for system
implementation, please call your authorized sales or service representative for any applicable changes.
This document and the information contained herein are provided AS IS AND WITHOUT WARRANTY. In
no event shall the copyright owner or its suppliers be liable for any special, indirect, or consequential damages
of any nature resulting from the use of information in this manual.
No part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any
means: electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from the
copyright owner.
Your use of this document and/or any of the inform ation contained herein constitutes your agreement to all of the
terms stated on this page.
ii
©Diebold, Incorporated (3/2003) - All Rights Reserved
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Contents
Section 1 Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Section 2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1.1 System Hardware Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.2 Agilis NDx Devices and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.3 System Hardware Not Supported . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
2.2 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
2.3 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.4 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Section 3 Setup and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

3.1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.1 Installation on Opteva™ Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.2 Installation on Diebold ix or Foreign Vendor Systems . . . . . . . . . . . . . . . . . 3-1
3.1.3 Executing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1.4 Files Installed after Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.2 Uninstalling the NDx Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Section 4 Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.1 Manual Configuration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2 Agilis NDx Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.1 Setting Up Internet Explorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.2.2 Accessing the NDx Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.2.1 Diebold ix and Foreign ATM Terminals . . . . . . . . . . . . . . . . . . 4-2
4.2.2.2 Diebold Opteva ATM Terminals . . . . . . . . . . . . . . . . . . . . . . 4-2
4.2.3 Agilis 91x Required Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.3 Agilis NDx Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.4 Configuration File Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
4.4.1 Clear Static Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
4.4.2 General Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.4.2.1 NDC Host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.4.2.2 Diebold Write Command III . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.4.2.3 Local Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
4.4.2.4 Transaction Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.4.2.5 Function Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
4.4.2.6 Operational Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
4.4.2.7 IDM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
4.4.2.8 Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.4.3 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
4.4.4 Sensors Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
4.4.5 Supplies Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.4.6 Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.4.6.1 Card Before Cash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
4.4.6.2 Default Touch Template . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
4.4.6.3 Diebold Reserved Screens . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.4.6.4 Error Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.4.6.5 Function ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
4.4.6.6 IDM Document Enable Code . . . . . . . . . . . . . . . . . . . . . . . . 4-33
4.4.6.7 Logo Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
4.4.6.8 Picture Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
4.4.6.9 Print Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
4.4.6.10 Reject Reason Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
4.4.6.11 Screen Control Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
iii
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Contents
4.4.6.12 Screen Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

4.4.6.13 Timer Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
4.4.6.14 Diebold Timer Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
4.4.6.15 Touch Screen Key Codes . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
4.4.6.16 Voice Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Appendix A NDC+ Transaction Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

A.1 Function Command Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
A.2 Function Command Screen Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
A.3 Function Command Print Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
A.4 Default Deposit Print Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
A.5 Open Account Relationship (OAR) Transactions . . . . . . . . . . . . . . . . . . . . . . . A-4
Appendix B NDC+ Terminal Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

B.1 Terminal Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
B.2 Configuration Information Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C Agilis NDx Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D Translation File Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Appendix E Configuration Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Appendix F Required Agilis 91x System Settings for Agilis NDx . . . . . . . . . . . . . . . . . . . . . . F-1
Appendix G Native NDC+ and Agilis NDx DPM Differences . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Figures
Figure 4-1 Agilis 91x NDx Configurator for Diebold ix and Foreign Terminals . . . . . . . . . . . . . . 4-2
Figure 4-2 Agilis 91x NDx Configurator for Opteva Terminals . . . . . . . . . . . . . . . . . . . . . . 4-3
Figure 4-3 Agilis NDx Configuration Selections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Figure 4-4 Clear Static Data Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Figure 4-5 Agilis NDx General Settings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-6 NDC Host Component Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-7 Diebold Write Command III Component Screen . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-8 Local Control Component Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Figure 4-9 Transaction Request Component Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Figure 4-10 Function Command Component Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-11 Operation Command Component Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Figure 4-12 Default Touch Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-13 Doc Enable Code Mapping Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
iv
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Tables
Table 2-1 Basic Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Table 2-2 Agilis NDx Devices and Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Table 2-3 Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Table 4-1 Miscellaneous Features 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Table 4-5 Local Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Table 4-6 Local Control Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Table 4-7 NDC Hardware Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Table 4-8 Reserved Screen Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Table A-1 Diebold TABS 9000 Series Messages to NDC SST messages . . . . . . . . . . . . . . . . . A-1
Table A-2 Function Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Table D-1 Translation File Default Conversions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Table E-1 Configuration Registry Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Table F-1 Required Agilis 91x System Settings for Agilis NDx . . . . . . . . . . . . . . . . . . . . . . F-1
Table G-1 Error Severity Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-1
Table G-2 Supplies Status Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
v
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Section 1
Purpose and Scope
This manual describes the Agilis NDx™ Configuration Guide and gives
instructions for installing and configuring the application. Refer to Section 2 for
an overview of the Agilis NDx Configuration application. Refer to Section 3
for setup and installation procedures, and refer to Section 4 for configuration
instructions.
The Agilis NDx™ product requires the following software and hardware for
different Windows operating systems, as follows:
• Microsoft® Windows® NT 4.0 operating system using Diebold ix Series and

foreign vendor terminals, such as NCR®
• Microsoft® Windows® XPe operating system using the Diebold Opteva™

Series terminals
For an overview and for more information on the Agilis NDx™ application
product, refer to Agilis NDx™ Product Description (TP-820802-001B).
1-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Section 2
Overview
The Agilis NDx product is a terminal resident software application developed

as a User Exit.
Terminal Hardware/Software
The Agilis NDx product can be installed on different operating systems, as
well as hardware, as follows.
Microsoft® Windows® NT Operating System. If using the Diebold ix Series

or foreign vendor ATM terminals, such as NCR®, the Agilis NDx application
and other system software use the Microsoft® Windows® NT 4.0 operating
system with Service Pack 6. The Agilis NDx product is installed as an optional
application.
Microsoft® Windows® XPe Operating System. If using the Diebold Opteva

Series ATM terminal, the Agilis NDx product and other system software use
the Microsoft® Windows® XPe operating system.
The Agilis NDx product coexists with the Agilis 91x terminal software and can
be enabled by the terminal Administrator.
Overview
The Agilis NDx application, enables the terminal in an NCR Direct Connect or
NCR Director Connect+ (NDC or NDC+) network. The Agilis NDx application
allows the Diebold, NCR, or foreign vendor terminal to work in the NDC or
NDC+ network with no modifications to the host terminal driver application.
Product Attributes
The Agilis NDx product consists of the following attributes:
• Communicates with the Agilis 91x system terminal and the NDC/NDC+ host
driver. Refer to Appendix A for information on these transaction messages.
• Allows Diebold terminals to report various statuses to the host by mapping

Diebold MDS statuses into appropriate NCR statuses.
• Includes a web-based configurator that allows simple manual configuration

of the Agilis NDx application’s parameters.
2.1 Hardware Requirements
The Agilis NDx Configuration application operates with the following minimum
hardware for the Agilis 91x software package and must coexist with the following
standard ATM hardware devices. Listed are those hardware components
supported and not supported for the Agilis NDx Configuration application.
2-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
2.1.1 System Hardware Supported
The following hardware is supported for the Agilis NDx Configuration

application.
Table 2-1 Basic Hardware Requirements
HARDWARE Diebold ix and Opteva™ NCR® and foreign

Series Terminals vendor Terminals
Processor 500 MHz or better 500 MHz or better
(May require additional
hardware as specified by
the ABC product.)
RAM (memory) 256 Megabytes 256 Megabytes
Network Card Compatible with Operating Compatible with
System Operating System
Hard Drive As needed As needed
Video Card Compatible with Operating Compatible with
System Operating System
Minimum of 640x480 Minimum of 640x480
resolution. However, resolution. However,
1024x768 resolution 1024x768 resolution
is recommended for is recommended for
graphics. graphics.
Sound Card Operating System Operating System
compatible sound card compatible sound card
to support voice to support voice
Protocols Agilis Base Agilis Base
Communications (ABC) Communications
supporting all protocols (ABC) supporting
all protocols
2.1.2 Agilis NDx Devices and Features
The following table displays the full scope of functional devices for the Agilis
NDx product that may or may not be supported.
Table 2-2 Agilis NDx Devices and Features
Device Diebold ix Series NCR and Foreign Diebold Opteva Series

Terminals Vendor Terminals Terminals
Cash Dispenser MMD (Multi media Dispenser, 4-high, Advanced Function
dispenser) Standard Cassette Dispenser (AFD)
Product ID 5875-F525 Supported
Cash Presenter Supported Supported as a feature Supported as a feature
of the Cash dispenser of the Cash dispenser
Coin Dispenser Not Supported Not Supported Not Supported
Consumer Video Supported Supported Supported
2-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 2-2 Agilis NDx Devices and Features (continued)
Device Diebold ix Series NCR and Foreign Diebold Opteva Series

Terminals Vendor Terminals Terminals
Dip Card Reader Supported Not Supported Supported
(No smart card
application support)
Encrypting Pin Pad Supported with single Supported Supported
(EPP) 4 /Consumer key encryption only EPP Std Sec US
Keypad Stainless Steel ANSI
Keyboard
Product ID: 5805-K115
Intelligent Depositor Not Supported Not Supported Supported
Module (IDM)
Journal Printer Supported Supported Supported
Part Number Graphics Thermal
00-050496-000A Journal Printer
Product ID: 5875-F213
Lead Through Supported Supported Supported
Indicators Media Entry Indicators
Linear Depositor Supported Supported Supported
DEPOSITORY WITH
STD BIN
ENVELOPE
DISPENSER - STD
CAPACITY
Motorized Card Supported Supported Supported
Reader MCRW TK 1/2/3 Smart
with Cropf/SE
Operator Video Supported Not Supported Supported
Supplemental Supported for Envelope Supported as a feature Supported as a feature
Dispenser Module Dispensing only of the linear depository of the linear depository
(SDM)
Swipe Card Reader Supported Not Supported Not Supported
Thermal Receipt Supports 40-column Supports 40-column
Printer Part Number: Supports Graphics Dual Part Number:
00-101670-000A Mode Thermal Receipt 00-101670-000A
Printer:Product ID:
5875-F204
Thermal Statement Not Supported Supports LQ Printer Supported
Printer with Graphics - Parallel
(NT)
Touch Screen Supported Not Supported Supported
TTU (Terminal Text Supported Supports Operator Not Supported
Unit ) Panel - Rear Access
Enhanced - 16 line by
40 character
Product ID:5875-F630
2-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Other hardware devices supported by the Agilis NDx software running on

Diebold Opteva Series terminals, are as follows:
• Fifth Cassette for the Cash Dispenser
• Lead Thru programming color capability Sensors (Red, Yellow, and Green
notification sensors)
• Writable CD-ROM
Any ATM hardware device not listed above is assumed not supported with
the Agilis NDx application.
NOTE
TTU for Maintenance, on Diebold ix Series and foreign vendor

terminals ONLY using the Windows NT operating system,
does not support the following languages:
• Chinese
• Arabic and Hebrew - XFS does not support right to

left oriented languages
• Arabic and Thai - XFS does not support complex scripts

in which characters combine or change shape based
on context
• Polish
• Russian
• Turkish
2.1.3 System Hardware Not Supported
The Agilis NDx application does not support the following ATM hardware
devices:
• Bar Code Reader

• Biometrics Interface
• Bulk Cash Acceptor
• Cash Pocket Fascia
• Coin Dispenser
• Encrypting Pin Pad 2 (EPP2)
• MMD (Multi media dispenser) with manual or motorized door only
• Money Order Printer
• Passbook Printer
• Single Note Acceptor
• Smart Card
• Statement Printer
2-4
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
2.2 Software Requirements
The Agilis NDx application requires the following software products for proper
operation of this product.
Table 2-3 Software Requirements
Diebold ix Series NCR and foreign Diebold Opteva

Platform vendor Platforms Series Platform
Windows NT 4.0 Windows NT 4.0 Windows XPe
operating system with operating system operating system
Service Pack 6 with Service Pack 6
Agilis 91x terminal Agilis 91x terminal Agilis 91x terminal
application application application
INvolve (supports Diebold INvolve (supports INvolve (supports
2.0 XFS SPs) foreign vendor 2.0 foreign vendor 3.0
XFS SPs) XFS SPs)
Diebold XFS 2.0 SPs Foreign vendor AMI, Diebold’s
for all supported Diebold vendor XFS 2.0 SPs Agilis Module
i or ix series terminal for all supported Interface; name
hardware foreign vendor of components that
terminal hardware form the lowest level
device software
interface on the
Opteva™ Terminals
Agilis Base Agilis Base Agilis Base
Communications (ABC) Communications Communications
supporting all protocols (ABC) supporting all (ABC) supporting all
and virtual LE support protocols and virtual protocols and virtual
LE support LE support
Mayfair Agilis software Mayfair Agilis Mayfair Agilis
software software
Agilis Base Communications (ABC)

The Agilis Base Communications (ABC), based on Diebold’s Communications
Subsystem, provides the communications between the Agilis applications
and the host(s). The operator interface for the communication subsystem
(Communication Subsystem Editor (CSSEDT)) allows the operator to monitor
communication status and activity, and to initiate and view message traces. The
communication subsystem dynamically updates the various statistics, providing
an accurate view of communication status at all times.
AMI for Opteva (Windows XPe ONLY)

AMI is an acronym for Diebold’s Agilis Module Interface; name of components
that form the lowest level device software interface on the Opteva™ Terminal
product family. The Agilis AMI (Agilis Modular Interface) is the interface layer
for Diebold Opteva ATM terminals. The AMI adapter, receives CSS express bus
messages and translates them into AMI messages.
Electronic Data Capture (EDC) - Coexists

The Electronic Data Capture application allows the terminal to store information
which is traditionally sent to the Journal Printer. This data can include transaction
data, terminal statuses, printer diagnostics, and cassette counters.
2-5
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
NOTE
The term coexists means that the application or user exit is

provided but not mandatory for the NDx application.
Event Management System (EMS/Remote Notifier) - Coexists

The EMS/Remote Notifier is a User Exit that sends copies of ATM status and
event messages directly from an ATM to the Diebold EMS (Event Management
System) Server. The EMS/Remote Notifier also sends another copy of the
messages to the institution network. The direct routing of the messages to EMS
does not affect transaction messages and transaction flows.
Iq CRM Agent - Coexists

The Iq CRM Agent is a Diebold online transaction processing system (transaction
interaction management) that delivers customer specific marketing content to
SST (self service terminal) users.
Iq ESD Agent - Coexists

The Iq ESD Agent is an independent application that runs on Diebold Self
Service Terminals (SST’s). The iq ESD Agent works with iq ESD as the host
server. It then provides package monitoring, scheduling, activation, and
cancellation functions, depending on file transport capabilities between the
iq ESD host and the SST.
Local Screen Changes (LSC) - Coexists

The LSC (Local Screen Changes) is a User Exit application that can save
network download data, load the terminal from the saved network download
data, and load additional custom configuration data. This essentially allows
screen overrides and states.
Message Authentication Code (MAC) - Coexists

The MAC (Message Authentication Code) is a data security feature which helps
prevent unauthorized tampering with messages between an ATM and a network.
The application monitors messages between the network and Agilis (or other
ATM-resident applications, such as SXA) by adding a MAC code and a Time
Variant Number (TVN) to critical messages.
Mayfair Software
The Mayfair software consists of foreign vendor required applications. Contact
your Diebold Service Representative to request more information on these
applications.
Software Extended Application (SXA)

SXA is a Software Extended Application that routes messages between the
network and the Agilis 91x application. SXA can route the same messages to
multiple applications, allowing it to support as many as 13 user exits on each
ATM. By adding user exits to an ATM, you can add functions and enhancements
to the ATM. SXA receives incoming messages, categorizes the messages based
on the message type, and then determines the destination of the messages. It uses
any network protocol format compatible with ABC.
NOTE
The Agilis NDx application was developed as a User Exit.
2-6
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Windows NT 4.0 Operating System

Windows NT 4.0 with Service Pack 6, is the operating system for the Agilis NDx
software application running on Diebold ix Series and foreign vendor terminals.
Windows XPe Operating System

Windows XPe is the operating system for the Agilis NDx software application
running on Diebold Opteva Series terminals.
XApWare Plus - Coexists

XApWare Plus are software programs that perform specific tasks (such as
coupon dispensing or video surveillance system) to enhance ATM functionality.
The XApWare Plus applications allow institutions to add new functions to
ATMs without requiring changes to the existing network software used by the
institution. They include the following applications:
• XAp Coupon Plus

• XAp Com
• XAp Logo
2.3 Terminology
The following table defines the terms, acronyms, and abbreviations used in
this document.
Term Definition
91x A true 911 or 912 network infrastructure
ABC Agilis Base Communications (Subsystem)
Agilis A Diebold software environment for Diebold and foreign vendor ATMs
AMI Acronym for Diebold’s Agilis Module Interface; name of components that form the lowest level
device software interface on the Opteva Terminal product family
ATM Automated Teller Machine
CSS Communication Subsystem
DIT Device Initialization Table
EDC The Electronic Data Capture application allows the terminal to store information which is
traditionally sent to the Journal Printer. This data can include transaction data, terminal statuses,
printer diagnostics, and cassette counters.
EMS A User Exit that sends copies of ATM status and event messages directly from an ATM to the
Diebold EMS (Event Management System) Server.
iq CRM Iq Customer Relationship Management
iq ESD Iq Electronic Software Distribution
LSC The LSC (Local Screen Changes) is a User Exit application that can save network download data,
load the terminal from the saved network download data, and load additional custom configuration
data. This essentially allows screen overrides and states. Therefore, the LSC (Local Screen
Change) application is used to locally load customized screens.
MAC Message Authentication Code (MAC 2.0.0) is a terminal application that prevents unauthorized
tampering with messages between an automated teller machine (ATM) and a network. MAC 2.0.0
is a terminal applet and does not require SXA to run.
2-7
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Term Definition
Mayfair Mayfair is a suite of applications that extend the functionality of the Agilis 91x system and NDx
Software software and its components.
NCR® National Cash Register
NDC/NDC+ NCR® Direct Connect and NCR® Direct Connect extension

OAR Open Account Relationship
Opteva™ The next generation Diebold ATM hardware, using the Windows XPe operating system.
Subsystem An application or product such as, SXA, LSC, Adobe Acrobat Reader, and others
TTU A user interface supporting text-based displays with no graphic capabilities (Windows NT
operating system ONLY)
SXA SXA is a Software EXtended Application that routes messages between the network and the Agilis
91x application. SXA can route the same messages to multiple applications, allowing it to support
as many as 13 user exits on each ATM. By adding user exits to an ATM, you can add functions
and enhancements to the ATM. SXA receives incoming messages, categorizes the messages
based on the message type, and then determines the destination of the messages. It uses any
network protocol format compatible with ABC.
XFS eXtensions for Financial Services (XFS)
2-8
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
2.4 Documentation
This section lists Diebold documentation that provides more information

concerning the terminal and utility software related to the Agilis NDx application.
• Agilis 91x™ Product Description (TP-820845-001B)
• Agilis 91x™ Installation and Configuration for Diebold ix Terminals

(TM-000057-001A)
• Agilis 91x Installation and Configuration Guide for Opteva Terminals

(TP-820742-001A)
• Agilis 91x™ Installation and Configuration for Foreign Terminals

(TM-000053-001A)
• Agilis NDx™ Product Description (TP-820802-001B)
• Agilis 91x™ Terminal Programming Manual (TP-820740-001B)
• Agilis 91x™ User’s Guide (TP-820746-001A)
• Agilis 91x™ Maintenance Manual (TP-820744-001B)
• Agilis 91x™ Status Reference Manual (TP-820741-001B)
• Agilis™ Base Communications (ABC) User’s Guide 1.0. (ABC is part of

the Agilis 91x software installation package.)
• Software Extended Application (SXA) 2.0.0 Operating Guide

(TP-820593-001A)
• Local Screen Changes (LSC) Version 2.0.0 Operating Guide

(TP-820594-001A)
• Message Authentication Code (MAC) Version 2.0.0 Operating Guide

(TP-820597-001A)
• Diebold i Series/MDS Data Security Procedures and Reference

(TP-799530-001C)
• XApWare 2000 Product Description (TP-820598-001A)
• Diebold XApCoupon 2.0 Operating Guide (TP-820713-001A)
2-9
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Section 3
Setup and Installation
The following paragraphs describe the required setup and installation files and
procedures necessary for correct operation of the Agilis NDx application.
3.1 Installation Overview
Setup files for the Agilis NDx application reside on a CD-ROM and can be used
at any time after the installation of the Agilis 91x terminal software package.
3.1.1 Installation on Opteva™ Systems
Set up files for the Agilis NDx application reside on the Agilis NDx Application
Suite CD-ROM. Agilis NDx Application Suite can be installed at any time after
the installation of the following software packages:
• Agilis 91x - NDx System Software

• Agilis 91x - NDx Mayfair Software
3.1.2 Installation on Diebold ix or Foreign Vendor Systems
Set up files for the Agilis NDx application reside on a CD-ROM and can be used
at any time after the installation of the Agilis 91x terminal software package.
3.1.3 Executing Setup
Follow these steps to install the Agilis NDx application.
1. Insert the correct CD-ROM into the drive.
2. On the Windows NT or Windows XPe desktop, select the My Computer

icon and browse for the CD-ROM drive.
3. Double-click on the CD-ROM drive to display the files on the disk.
4. Select the SETUP.EXE file and double-click on the file.
5. The setup installation begins.
3.1.4 Files Installed after Setup
After the Setup installation, a log file is created to keep track of main operations
and installation errors. This file is called AgilisNDx.log and is located in the
C:\Diebold\ACO2 directory.
3-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
The following files reside in their designated directories after setup completes.
Directory C:\Diebold\ACO2
ACO2PData.exe
AgilisNDx.log
readme.txt
Directory C:\Diebold\ACO2\data
ACO2CFG.xml
ACO2CFG.xsd
CardCash.xml
CardCash.xsd
FuncID.xml
FuncID.xsd
IDMDEC.xml
IDMDEC.xsd
KeyCodes.xml
KeyCodes.xsd
Logo.xml
Logo.xsd
NDCStat.xml
NDCStat.xsd
Picture.xml
Picture.xsd
PrintDat.xml
PrintDat,xsd
ReservedScrnNumList.xml
ReservedScrnNumList.xsd
RRCTrans.xml
RRCTrans.xsd
ScreenNum.xml
ScreenNum.xsd
ScrnSq.xml
ScrnSq.xsl
tch_def.xml
tch_def.xsd
TimerNum.xml
TimerNum.xsd
TimerVal.xml
TimerVal.xsd
Voice.xml
Voice.xsd
Directory C:\Diebold\ACO2\dll
ACO2Trns.dll
ACO2UEJ.dll
ACO2Util.dll
LangCode.dll
Directory C:\Diebold\ACO2\Logs
This directory will remain empty until an
application log file is created.
Directory C:\Diebold\TCS\App
ScrnCtrl.adt
ScrnCtrl.dll
ScrnRef.adt
ScrnRef.dll
3-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
StXlate.adt
StXlate.dll
Directory C:\Diebold\Web\Scripts
ACO2.pm
ACO2Config.pl
3.2 Uninstalling the NDx Application
To uninstall the NDx application, you must use the system registry and delete the
designated keys. You can then remove the application from the Windows NT or
Windows XPe operating system. Refer to Appendix E for a complete listing
of the configuration registry and the keys and files which must be deleted to
remove the Agilis NDx application.
You can NOT use the Windows Control Panel to uninstall the Agilis
NDx application.
3-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Section 4
Manual Configuration
The following sections provide required manual configuration information for the
Agilis NDx application through the Windows NT or the Windows XPe (Agilis
91x) terminal application desktop, after you have installed the NDx application.
The Agilis NDx application is part of the Agilis 91x software package, but is
installed separately from the Agilis 91x terminal software system.
Because the Agilis 91x software package and the Agilis NDx application
requires that necessary parameters be set in order for the Agilis NDx application
to run properly, the following sections offer instructions on these required and
user-configurable settings, as follows:
• Section 4.2 - Agilis NDx Configurator

• Section 4.3 - Agilis NDx Configuration Settings
4.1 Manual Configuration Overview
The Agilis NDx Configurator provides configuration access for the Agilis
NDx application using a web-based interface. The following sections provide
instructions for activating and configuring the Agilis NDx application on the
Agilis 91x terminal system.
4.2 Agilis NDx Configurator
The following sections list the required Agilis settings necessary before the
Agilis NDx application can run successfully.
4.2.1 Setting Up Internet Explorer
Before using the Agilis NDx Configurator correctly, it is necessary that Internet
Explorer’s settings be changed in the following steps.
1. Right-click on Internet Explorer’s icon on your desktop.
2. From the General tab, click the Settings option. (You can also access
these settings by launching Internet Explorer, selecting the Tools option
and then clicking on the Internet Options selection.)
3. On the checkbox named "Check for newer versions of stored pages:",

select "Every visit to the page".
4. Select OK.
You are now ready to access the NDx Configurator.
4-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.2.2 Accessing the NDx Configurator
The following sections cover accessing the NDx Configurator for the following
ATM terminals:
• Diebold ix and Foreign ATM Terminals

• Diebold Opteva ATM Terminals
4.2.2.1 Diebold ix and Foreign ATM Terminals
To access the NDx Configurator, follow these steps.
1. From the START button, select PROGRAMS.
2. Select the Agilis 91x NDx option and then select the Agilis 91x NDx
Configurator, as shown in Figure 4-1.
G5371_004
Figure 4-1 Agilis 91x NDx Configurator for Diebold ix and Foreign Terminals
Refer to Figure 4-3 for the resulting screen that appears after following these
steps.
4.2.2.2 Diebold Opteva ATM Terminals
To access the NDx Configurator on Diebold Opteva terminals, follow these steps.
1. On the Windows XPe desktop, right-click on the My Computer icon, as

shown in the example screen below.
4-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_004A
2. Select the Manage option.
3. Select the Diebold_ATM option. The following screen appears.
G5371_004B
Figure 4-2 Agilis 91x NDx Configurator for Opteva Terminals
4. Select the Extended Features option.
5. Select the ACO2 option.
Refer to Figure 4-3 for the resulting screen that appears after following these
steps.
4-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.2.3 Agilis 91x Required Settings
The Agilis 91x required settings are either automatically set by default parameters
when the Agilis NDx application is enabled, or can be user-configured, as
listed in the following paragraphs. For more information, refer to Appendix F
of this manual.
Required Settings for Agilis NDx (Set by Default)

The following required settings are automatically set by default, when enabling
the Agilis NDx application:
• Send MDS Status always
• Send Supervisory Status at Logon
• Send Supervisory Status at Logoff
• Send Unsolicited Status during Maintenance
• Cassette Tamper Enabled must be set to "On"
• Language Translation of Fault Status should always be set to "Send to

Journal Printer".
• Consumer Display option OAR (Open Account Relationship) Transaction

screen should always be set to "enabled".
• Presenter action after customer timeout feature should be set to the Retain
and do not report status (default). However, this is only applicable when
the No Retract feature under the Local Control option (General
Settings) is turned OFF.
NOTE
If any of the Agilis NDx required settings are manually

changed by the user, the Agilis NDx application might not
function properly. Therefore, it is very important that the
required settings are not changed.
Default Settings for NDx (Set Internally - No User Interaction)

The following lists the default settings for the Agilis NDx application:
• Remapping the F, G, H, and I function keys to I, H, G, and F, respectively to

emulate NCR terminal key positions
• Relocation of default Agilis 91x Reserved screens - Refer to Section 4.4.6.3

and Table 4-8 for more information.
4-4
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
User-configurable Settings
The following lists the settings and options the user can configure for the Agilis
NDx application :
• Maintenance option should be set to the following parameter: After Logoff,

return to Previous State or Out-of-service (set this option according
to Host’s request).
• Number of Operation Keys on Consumer Keypad
• Ability to choose NCR’s default background and foreground color for screen
display as an alternate selection. This configuration applies to VGA Plus
(high and low resolution) video emulation mode only.
NOTE
The following settings under Presenter Options, must be

manually configured when the No Retract feature under the
General Settings, Write Command III, is turned ON.
• Do not retract - go out of service after close state if

money is forgotten.
• Do not retract - go back in service after forgotten money

is removed.
• Do not retract - send forgotten money status after timeout

and money removed status if removed.
4.3 Agilis NDx Configuration
The configuration of the Agilis NDx application is available only through the use
of the Agilis NDx Configurator, shown in Figure 4-3.
NOTE
The NDC+ and Diebold Programmer’s Reference manuals are

necessary references when properly configuring the Agilis
NDx application.
4-5
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_005
Figure 4-3 Agilis NDx Configuration Selections
4.4 Configuration File Interface
The following sections include configuration file interface format information

allowing the end-user to configure the Agilis NDx application.
There are 6 groups that comprise the Agilis NDx application configuration,
as follows:
• Clear Static Data

• General Settings
• Hardware Configuration
• Sensor Status
• Supplies Status
• Translations
4-6
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.1 Clear Static Data
The Clear Static Data selection clears ALL static data being used by the Agilis
NDx application being saved between power fails. Refer to Figure 4-4.
G5371_001
Figure 4-4 Clear Static Data Screen
It is necessary that the Agilis NDx application store the following entries and
persist them through powerfails in order to emulate entries persisted by NCR
terminals.
Static Data Items

The following list of items are entries which are stored by the Agilis NDx
application as static data:
• Extended Range For Message Coordination Number

• Envelope Dispenser Status Option
• Accumulated Transaction Count
• State of ’Automatic Return to Previous Mode’ flag
• Original Configuration ID sent by the NDC host
• Hardware Fitness
• State of ’Insert Last Transaction Status Data’ flag
• Last Transaction Status Data
• Logical Unit Number (LUNO)
• Machine Number
• Sensors Status
• Supplies Status
• Date Format
• ’R00’ and ’R01’ Screens
• State of ’Send Reject Reason Codes To Network’ flag
• State of ’Transmit Tamper Indicators’ flag
• Lift Front Rear Image
• Enhanced TI Sensor Status
• Read Zone VS Buffer ID
• NDC Document Enable Code
However, the following static data items, taken from the above listing, are read
again from the main Agilis NDx configuration whenever a powerfail message
is received by the Agilis NDx application . The value of these items can then
be modified by the network load.
• Extended Range For Message Coordination Number

• Envelope Dispenser Status Option
• State of ’Automatic Return to Previous Mode’ flag
• State of ’Insert Last Transaction Status Data’ flag
• Date Format
4-7
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
• ’R00’ and ’R01’ Screens

• State of ’Send Reject Reason Codes To Network’ flag
• State of ’Transmit Tamper Indicators’ flag
The remaining static data items, listed below, are persisted by the Agilis NDx
application through powerfails. To reconfigure these values and to clear the entire
list of persistent data items, select the OK button on the Clear Static Data screen.
• Accumulated Transaction Count

• Original Configuration ID sent by the NDC host
• Hardware Fitness
• Last Transaction Status Data
• Logical Unit Number (LUNO)
• Machine Number
• Sensors Status
• Supplies Status
• Lift Front Rear Image
• Enhanced TI Sensor Status
• Read Zone VS Buffer ID
• NDC Document Enable Code
4.4.2 General Settings
Figure 4-5 displays the Agilis NDx application General Settings configuration
screen, consisting of 8 configurable components, briefly detailed in the following
subsections:
• NDC Host
• Write Command III
• Local Control
• Transaction Request
• Function Command
• Operational Command
• IDM Settings
• Tracing
4-8
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_002
Figure 4-5 Agilis NDx General Settings Screen
4-9
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Field Column Headings

There are three field headings in each of the eight components in the Agilis NDx
General Settings screen, as follows:
• The Description field describes the Agilis NDx setting for a particular
parameter.
• The Current Value field represents the default or changed value for that
setting.
• The New Value field contains a drop-down menu box or a blank user-entry
box (end-user can insert alternative information) of values that can replace
the current value.
4.4.2.1 NDC Host
The end user can select the type of host emulation type that will be used,
as follows:
• NDC
• NDC+
G5371_002A
Figure 4-6 NDC Host Component Screen
4.4.2.2 Diebold Write Command III
The Diebold Write Command III screen contains various settings for the Diebold
Write Command III message translation being sent to the Agilis system.
Possible selections display in the drop-down boxes. Table 4-1, Table 4-2, and
Table 4-3 details default and optional selections for each message translation,
as shown in the following screen.
4-10
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_002B
Figure 4-7 Diebold Write Command III Component Screen
Diebold Write Command III Fields

There are 4 types of Diebold Write command III Miscellaneous Feature settings,
as listed in the following tables.
Table 4-1 Miscellaneous Features 1
Field Description/Flag Default Value

Options
Separate Ready Yes or No No
Dollar Buffer Size 8 or 12 8

Dollar Decimal Places 2 or 3 2
Deposit Cancel Status Yes or No No
Decimal Style Yes or No No

Options
MMD Mispick Timer Yes or No No
Send Reject Reason Yes or No No
4-11
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003

Options
Extended range for Yes or No No
message coordination
number
Automatic Picture Camera Control Value/ Yes
Taking Yes or No
No Retract When this feature is set Yes
to Yes, refer to the Agilis
ATM Configurator screen,
Devices selection, and
Presenter option section
for further configuration.
When this feature is set to
No, the Presenter action
after customer timeout
setting will be Retain and
do not report status.
Yes or No
Extended Range for Message Coordination Number. Selecting this feature

increases the range for the Message Coordination Number from 31-3F to 31-7E
(hex).

Options
Envelope Dispenser 000 to 003 000
Envelope Dispenser Status Options. Corresponding values for this feature is

shown in the following table.
Flag Flag Description

000 Do not send envelope dispenser status messages; set
the remote status indicators or activate the remote relay
(default)
001 Send envelope dispenser status messages
002 Set the remote status indicators and activate the remote
relay
003 Send envelope dispenser status messages; set the
remote status indicators and activate the remote relay
4-12
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.2.3 Local Control
The Local Control screen contains configurable values that can affect the
behavior of the emulated NDC terminal.
G5371_002D1
Figure 4-8 Local Control Component Screen
Local Control Description Fields

Table 4-5 below, describes the fields in the Local Control screen (Figure 4-8).
Table 4-5 Local Control Settings
Field Default Description/Flag Options

Value
Cassette Type 1 A Maps current NCR currency type 1 for
Diebold cassette type.
@, A, B, C, D, E, F, G, H
Cassette Type 2 B Maps current NCR currency type 2 for
@, A, B, C, D, E, F, G, H
Cassette Type 3 C Maps current NCR currency type 3 for
@, A, B, C, D, E, F, G, H
Cassette Type 4 D Maps current NCR currency type 4 for
@, A, B, C, D, E, F, G, H
NOTE
All mapped NDC cassette

type values must be unique,
even if the Diebold dispenser
contains two cassettes with
the same denomination. It is
valid to have more than one
unmapped cassette.
The @ represents an
unmapped cassette.
4-13
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 4-5 Local Control Settings (continued)

Value
Report Partial Yes Yes turns this feature to ON allowing a
Dispense number of bills dispensed, in a status
message to the Host.
No turns this feature to OFF creating a
’no note dispensed’ status, which will
always be sent to the Host, unless a ’low’
condition exists.
Send Software Data No Should the NDC Release Number and
Software ID be sent to the host in
the Configuration Information Solicited
Status?
Yes or No
Release Number (6-digit The current NDC/NDC+ Release number.
current
release #)
Software ID (Current The NDC/NDC+ Software Identifier
ID)
Transmit Tamper No Should an extra NDC Tamper Indicator
Indicators Status be sent to the Host?
Yes or No
Append Field No Should a Field Separator be appended to
Separators all Host messages?
Yes or No
4.4.2.4 Transaction Request
The Transaction Request screen contains the following setting for the Transaction
Request message translation that is sent to the NDC host. If this parameter is
turned on, the last transaction status data will be appended to every outgoing
NDC+ transaction request message sent to the Host.
G5371_002E
Figure 4-9 Transaction Request Component Screen
4.4.2.5 Function Command
The Function Command screen contains various settings for the Function
Command message translation that is sent to the Agilis 91x system.
4-14
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_002F
Figure 4-10 Function Command Component Screen
Function Command Description Fields

The following descriptive fields shown in the Function Command screen explain
their usage, as follows.
Table 4-6 Local Control Settings

Value
Print At Far Left Yes Should Print At Far Left escape
sequence be added to receipt print
data, allowing the first character to
print to the far left of the paper? /
Yes or No
Decimal Delimiter For . What decimal delimiter (decimal
Deposit Print Amount period or comma) will be used in
the default deposit print data in the
amount field? / . or ,
Date Format MMDDYY What date format should be used
in the default deposit print data? /
MMDDYY or DDMMYY
4.4.2.6 Operational Command
The Operational Command screen contains various settings for the Operational
Command message translation that is sent to Agilis 91x system.
G5371_002G
Figure 4-11 Operation Command Component Screen
4-15
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
These parameters provide additional out of service screens that can be displayed
instead of the default Out-Of-Service screen. These are only used when a
Shutdown command is received containing an additional command modifier.
Operational Command Description Fields

The following descriptive fields shown in the Operational Command screen
explain their usage, as follows.
Standard Out-Of-Service Screen. This is the Standard Out-of-Service screen

number used when the Shutdown command contains a command modifier of 0
(zero). The default is AY2.
Temporary Out-Of-Service Screen. This is the Temporary Out-of-Service

screen number used when the Shutdown command contains a command modifier
of 1. The default is AY2.
4.4.2.7 IDM Settings
The IDM Settings screen, as shown below, contains various settings for the IDM
device translation that is sent to the Agilis 91x system.
G5371_002H
The following settings for this screen are explained in the following paragraphs.
Pocket Destination
The Pocket Destination parameter specifies where to deposit the document
currently present, into the IDM device. This parameter is used when the host
requires depositing the document being processed by the IDM, to the locally
configured bin.
The Pocket Destination parameter ranges can be from the character values of ’0’
through ’3’. The values for these ranges are, as follows:
• ’0’ - Use reject bin/envelope deposit
• ’1’ - through ’3’ - Use pocket A through C respectively. However, the

parameter ’3’ should only be used for NCR 5665 Self-Service terminal
emulation.
The default value is ’1’ for use pocket A.
4-16
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Lift Image
The Lift Image parameter is used when the Host lifts the rear image for archive
and/or display. The IDM device is able to capture only the front image.
Therefore, this parameter allows the Agilis NDx application to change the
request ‘lift rear image’ to ‘lift front image’, otherwise the message is rejected.
The Lift Image parameter ranges can be from the character values of ’0’ through
’3’. The default value is ’1’. The values for these ranges are, as follows:
• ’0’ - Do not lift any image

• ’1’ - Lift front image (default)
• ’2’ - Lift rear image. In this case, the message is rejected.
• ’3’ - Lift front and rear images. In this case, the message is rejected.
DPM Message Format

The DPM Message Format parameter is used to handle error messages in two
different ways by the Host. The DPM Message Format parameter has two
values, as follows:
• 5665 (NCR 5665 Self-Service terminal emulation)

• DP-ATM
The LSC (Local Screen Change) application is used to download terminal

parameters for each of these Diebold screens:
• Please Insert Document Screen

• Processing Document Screen
• Unacceptable Document Screen
• NDC+ Further Processing Screen
For more information on the LSC application, refer to the Local Screen Changes
(LSC) Version 2.0.0 Operating Guide (TP-820594-001A).
4.4.2.8 Tracing
Turning the Tracing feature on produces additional Agilis NDx trace files
that are stored in the \Diebold\aco2\logs folder. This feature also allows for
addition troubleshooting.
4.4.3 Hardware Configuration
The Hardware Configuration screen consists of the following 25 options:
• Product Class
• Card Reader
• Cash Handler
• Depository
• Receipt Printer
• Journal Printer
• Night Safe Depository
• Encryptor
• Security Camera
• Door Access
4-17
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
• Flex Disk
• Tamper Indicating Bins
• Cardholder Keyboard
• Operator Keyboard
• Cardholder Display
• Statement Printer
• Signage Display
• Coin Dispenser
• System Display
• Media Entry Indicators
• Envelope Dispenser
• Document Processing Module
• CDM Tamper Indication
• DPM Tamper Indication
• Digital Audio Service
The Hardware Configuration screen is used to set up the initial hardware

configuration of the terminal. Because there are certain NCR devices for which
there are no Diebold device equivalents, or devices that may not be supported by
a Diebold terminal, some device entry configurations are strictly taken from
this page to report the existence of these devices to the NDC+ Host. Refer to
Table 4-7 for more details.
The following 3 screens are all part of one Hardware Configuration screen.
4-18
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
g5371_024
4-19
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
g5371_024a
4-20
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
g5371_024b
The following table lists every device, defining if the configuration is overridden
by the Agilis 91x system message (Programmatic), or taken from this file
(Configuration).
Table 4-7 NDC Hardware Devices
NDC Hardware Determination Possible Programmatically

Device Technique Determined Values
Product/Class Configuration -
System Disk Configuration -
4-21
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 4-7 NDC Hardware Devices (continued)

Magnetic Card Programmatic 01 Track 2 (read only)
Reader/Writer 03 Track 1/2/3 MCRW (write on track 3
only)
Cash Handler Programmatic 00 Standard cash handler not configured
01 Standard cash handler configured
Depository Programmatic 00 Not configured
02 PPD
Receipt Printer Programmatic 00 Not configured
01 Plain paper
02 black dot papoer
05 Thermal printer - no black mark
06 Thermal printer - black mark
Journal Printer Programmatic 00 Not configured
01 Integral journal printer
80 Electronic journal
Electronic journal and integral journal
printer
Night Safe Programmatic 00 No configured
Depository 01 Configured
Encryptor Programmatic 00 Not configured
01 NBS encryptor
Security Programmatic 00 Not Configured
Camera 01 fixed format (for instance, 3M)
Door Access Configuration -
Flex Disk Configuration -
Tamper Configuration -
Indicating Bins
Cardholder Configuration -
Keyboard
Operator Configuration -
Keyboard
Cardholder Programmatic BIT 2 - Voice not supported
Display / Voice BIT 2 1 - Voice supported if digital audio
present
BIT 3 0 - Standard FDKs
BIT 3 1 - Touch screen
Statement Programmatic 00 Not configured
Printer 01 Configured
Signage Display Configuration -
Coin Dispenser Programmatic 00 None

02 S4
System Display Configuration -
Media Entry Programmatic 00 Not configured

Indicators 01 Configured
Envelope Programmatic 00 Not configured
Dispenser 01 Configured
4-22
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 4-7 NDC Hardware Devices (continued)

Document Configuration 00 - Not Configured
Processing 01 - 5665 DPM
Module 02 - DP-ATM
Coin Dispensing Configuration -
Module Tamper
Indication
Document Configuration -
Processing
Module Tamper
Indication
Digital Audio Configuration -
Service
4.4.4 Sensors Status
The Sensors Status selection displays initial device sensors information for all
SST devices. This configuration is used for initial sensors status configuration of
the terminal. Agilis NDx automatically updates these values when it receives
status information from Agilis 91x system indicating changes in sensor statuses
for these devices. A sample screen follows.
G5371_025
New Value options available can be Active or Inactive, and In or Out which
determines the initial state of the device.
4-23
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.5 Supplies Status
The Supplies Status selection displays initial supplies status information for all
SST devices. This configuration is used for initial supplies status configuration
of the terminal. Agilis NDx automatically updates these values when it receives
supplies status information for Agilis 91x system indicating changes in the
supplies statuses for these devices.
G5371_026
New Value options available are as follows:
• 0 - Not Configured
• 1 - Good State
• 2 - Media Low
• 3 - Media Out
• 4 - Overfill
4.4.6 Translations
The Translations selection consists of the following configurable options:
• Card Before Cash

• Default Touch Template
• Diebold Reserved Screens
• Error Status
• Function ID
• IDM Document Enable Code
• Logo Number
• Picture Number
• Print Data
• Reject Reason Codes
• Screen Number
• Screen Control Sequence
• Timer Number
• Timer Value
4-24
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
• Touch Screen Key Codes

• Voice Number
NOTE
Please note that NDC/NDC+ does NOT support 5-digit screen

numbers.
Although some screens may vary, there are three optional buttons available for
most of the Translations screens, as follows.
Add
Allows for additional user-entry parameters and values.
Delete
Eliminates currently selected parameters or values from the current screen.
Modify
Changes currently selected parameters or values.
4.4.6.1 Card Before Cash
The Card Before Cash Screens example screen selection, as shown below, is
normally empty by default. The screen displays the association between an
NDC Card Before Cash screen number to Diebold Card Before Cash screens. If
this selection is not being used, the file can be left empty. All information is used
while converting the screen number in an NCR Transaction Message Reply to
screen numbers in the Diebold Function command message.
A single NDC+ Card Before Cash screen, containing overlays, can be mapped
to two separate Diebold screens, which are used in the translated function
command sent to Agilis 91x system.
G5371_006
To create values for this function, select the Add button. An example Add
screen follows.
4-25
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_006A
NOTE
The "Diebold Screen 1" parameter displays during a ’card

take’. The "Diebold Screen 2" parameter displays during
a ’cash take’.
4.4.6.2 Default Touch Template
NCR has a default touch template that it associates with screens that do not
have an explicitly defined touch template. This file specifies the layout of this
default touch template. The Default Touch Template selection allows you to
define as many touch areas as needed. Each touch area is defined by the X and Y
coordinates of its opposite corners and the associate Key code. A default NCR
touch template definition already exists in this file. This layout should be
defined in Diebold format.
G5371_007
Figure 4-12 Default Touch Template
NOTE
If no entries are defined in this file, the Agilis NDx application

will NOT send down default touch template definitions to the
Agilis 91x software system.
Add Values
After selecting the Add button in Figure 4-12, the following screen appears.
4-26
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_007A
New values can be inserted into each Value field. Select OK to accept values
and return to the previous screen. Select Cancel to return to the previous screen
without adding any values.
Delete Values
After selecting the first parameter line (A) of information and then selecting
the Delete button in Figure 4-12, the first line (A) is removed. A new screen
appears with the remaining values.
G5371_007C
All values for that parameter line are removed.
Modify Values
After selecting the A parameter and then the Modify button in Figure 4-12, the
following screen appears.
G5371_007D
All values in the screen can be changed or modified. To keep new changes, select
the OK button. To cancel changes and return to the previous screen, select
the Cancel button.
4-27
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.6.3 Diebold Reserved Screens
The Diebold Reserved Screens file contains the list of Diebold screen numbers,
the content of which does not have to be translated. A valid screen number in
this file would be 3 characters long and can range from 000 to 999 and A00 to
AZZ. All Diebold screen numbers which do not need to be translated, must
be included in this file. Refer to the Agilis NDx Reserved Screen Numbers
main screen below.
G5371_008
The following screen displays the Add option display selected from the Reserved
Screen Numbers screen.
G5371_008A
Selecting the OK button accepts the user’s value field entry. Selecting the Cancel
button cancels the entry and returns the user to the previous screen.
Table 4-8 displays available Diebold Reserved Screen Numbers and their
definitions.
NOTE
The Diebold Reserved Screen Numbers, 000-009, 900-950,

and 999 have been remapped to AYO though AZH.
Table 4-8 Reserved Screen Numbers
TCS Reserved Definition

Screens Screen
000 AY0 More Time Screen
001 AY1 Off Line Screen
002 AY2 Out-Of-Service Screen Supply Screen
003 AY3 Supply Screen
4-28
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 4-8 Reserved Screen Numbers (continued)

Screens Screen
004 AY4 Currency Characters Screen
005 AY5 Thousands Seperator Characters Screen
006 AY6 Decimal Character Screen
007 AY7 Door Retry Screen
008 AY8 Rear Balancing Function Menu
009 AY9 Rear Balancing Function Definition Data
900 AYA OAR Screen
901 AYB Select Language Screen
902 AYC Rear Balancing “Function Failure” message
903 AYD Continous Avaliablity Service “Continue ?”
904 AYE Continous Avaliablity Service “Take Card”
905 AYF Voice Guidance Enable Screen
906 AYG Screen for depositor when device is being
serviced is Continuous Availability
907 AYH Screen for dispenser when device is being
serviced is Continuous Availability
908 AYI Screen for coin dispenser when device is being
serviced in Continuous Availability
909 AYJ Screen for statement printer when device is
being serviced in Continuous Availability
910 AYK Screen for Automatic media dispenser customer
prompting
911 AYL Screen for supplemental dispenser device not
available message and do you want to continue
question. Used during auto dispense and state
C.
912 AYM Screen used in consumer input DSA for bogus
screen change used to force a touch screen
enable message.
913 AYN Screen for supplemental dispenser device not
available message. Used during state C.
914 AYO Screen for supplemental dispenser device is
being serviced in Continuous Availability
915 AYP Screen to prompt removal of card from DIP card
reader
916 AYQ Screen for AHD when device is being serviced in
CAS Rss bit map screen
918 AYS Screen for auto balance function menu
919 AYT Screen for alternate "Please Wait" message
while auto balance is executing
920 AYU Auto balancing function definition data
4-29
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table 4-8 Reserved Screen Numbers (continued)

Screens Screen
922 – 950 AYV – AZG Reserved
999 AZH More time screen (internal)
4.4.6.4 Error Status
The Error Status selection converts Diebold device fault status messages to an
equivalent NDC form. The file associated with this screen contains records
consisting of the MDS Status string, or a portion of it, that is received as part
of the Diebold device fault status message, equivalent NDC device ID, NDC
M-Status and M-Data translations, and other information used to translate the
status message. Refer to the Error Status Mapping main screen below.
The only parameter/value fields on the Error Status Mapping screen that can be
modified or changed are as follows:
• M-Status
• M-Data
• Suppress in Maintenance Mode
• Dump Cash
G5371_009
The following parameter/value fields on the Error Status Mapping screen

CANNOT be modified or changed:
• Device ID
• MDS Status
• Host Type
• Transaction Status
• Device Status
• Severity
• Event Handlers
The M-Status and M-Data portion of each entry can be modified using the Modify
option and are used to construct the associated portions of the NDC device fault
status message translation. Refer to the Error Status Mapping main screen below.
4-30
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_009A
New values can be inserted into each user-entry Value field. Select OK to accept
the new values and return to the previous screen. Select Cancel to return to the
previous screen without adding or changing any new values.
4.4.6.5 Function ID
The Function ID Mapping translations file contains information for converting

NDC function ID from a Transaction Reply Message to one or more Diebold
Function IDs in Diebold’s Function Command. It also specifies the screen that
displays while the function is being performed.
If an NDC Function ID received in a Transaction Reply Message is not present in

the file, then the Transaction Reply Message is rejected.
The options for the Function ID are as follows:
• NONE - Do not change screen display
• SAME - The screen number received in the NDC Function Command

displays
• CBC1 - Card Before Cash Screen 1
• CBC2 - Card Before Cash Screen 2
An example screen follows.
4-31
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_010E
The following screen displays the Add option screen selected from the Main
Function ID Mapping screen.
G5371_010A
The following screen displays the Modify option screen selected from the
Main Function ID Mapping screen.
G5371_010B
4-32
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.6.6 IDM Document Enable Code
Selecting the IDM Document Enable Code option displays a list of the
configured NDC Doc Enable Codes and their corresponding Diebold values for
the IDM device, as shown in the following screen.
G5371_010C
The NDC Document Enable Codes are contained in the NDC downloaded ‘Q’
state. All NDC Document Enable Codes received into the downloaded ‘Q’ State,
must be configured in this screen selection.
From the Main IDM Document Enable Code Mapping selection, you can select
one of the Document Enable Codes listed, or select the Add button to access the
following screen, as shown below.
G5371_010F
Figure 4-13 Doc Enable Code Mapping Screen
4-33
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
The options for the IDM Document Enable Code selection, are as follows:
• NDC Document Enable Code - The NDC value is downloaded into the ’Q’
State field. Format can be 5 numeric digits.
• 912 Type - Format can be a number from 1 to 999
• 912 Index - Format can be a number from 1 to 999
• MICR Reading - Options can be either"Yes" or "No" and indicate whether or

not the MICR data must be sent to Host.
• MICR Read Zone - Indicates which Read Zone data Agilis NDx should be
used to insert the MICR data. Format can be a number from 1 to 10.
• Courtesy Amount Auxiliary Status - Format must be 4-digit hexidecimal

from 0001 to FFFF
• Courtesy Amount Window - Parameter specifies the document window for

the courtesy amount. This field will be used in the ‘P’ state processing.
Format can be a number from 1 to 999
• 912 Windows - You can list up to 10 parameters4. The format can be

a number from 1 to 999.
From the 912 Windows selection, you can select one of the 912 Windows listed,
or select the Add button to access the following screen, as shown below.
G5371_010D
The windows position (sequence) maps the read zone sequence to be inserted into
the transaction request message. From this screen, you can select each parameter
setting. You can use the numeric format from 1 to 999.
Select OK to accept the new values and return to the previous screen. Select
Cancel to return to the previous screen without adding or changing any new
values.
4-34
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
The values configured into the 912 type, 912 index, and 912
window(s) must have corresponding entries in the ics.cfg
(IDM device configuration file).
For instance, configure the parameters shown in Figure 4-13 with the following
values:
• 912 type parameter - configured as ’1’

• 912 index parameter - configured as ’1’
• 912 windows(s) - configured as ’[1]’, ’[2]’
• MICR Reading parameter - configured as "Yes"
• MICR Read Zone parameter - configured as ’2’
The Agilis NDx application reads, as follows:
• US Personal and commercial Check Courtesy Amount - referred to the IDM

Doc Enable Codes parameters values:
- 912 type=1
- 912 index=1
- 912 windows=1
• US Check E13B MICR Line - referred to the IDM Doc Enable Codes
parameters values:
- 912 type=1
- 912 index=1
- 912 windows=2
The Agilis NDx application will fill in the NDC Transaction Request Message,
inserting the "US Personal and Commercial Check Courtesy Amount" data
into the "Read Zone 1" field and "US Check E13B MICR Line" data into the
"Read Zone 2" field.
4.4.6.7 Logo Number
The Logo number contains mapping between NDC logos and Diebold icon
numbers. A valid NDC logo number is 2 characters long with a range of 00
to 99. A valid Diebold icon number is 3 characters long and must be numeric
with a range of 000 to 999. The NDC Logo Number to Diebold Icon Number
screen is empty by default.
NOTE
Use this translation with the host-sent ESC ’P’ ’1’ Parameter
ESC ’\’ screen control sequence for picture control.
An example Logo Number Reference main screen follows.
4-35
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_012
The following screen appears after selecting the Add option from the Logo
Number Reference main screen.
G5371_012A
The following screen appears after selecting the Modify option from the Logo
G5371_012B
4.4.6.8 Picture Number
The Picture Number translation file contains mapping between NDC picture
and Diebold icon numbers. A valid NDC picture number is 1 to 3 characters
long with numbers ranging from 000 to 999. A valid Diebold icon number is 3
characters long and must be numeric with a range of 000 to 999.
NOTE
Use this translation with the host-sent ESC ’P’ ’2’ Parameter
ESC ’\’ screen control sequence for picture control.
4-36
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
An example Picture Number Reference main menu screen follows.
G5371_013
The following screen appears after selecting the Add option from the Picture
G5371_013A
The following screen appears after selecting the Modify option from the Picture
G5371_013B
4.4.6.9 Print Data
The Print Data Translation file contains information for the conversion of the
NDC Printer Data Control Sequences to Diebold Printer Data Control Sequences.
Each entry consists of the character set, NDC Print Data and Diebold Print Data.
If the specified NDC Print Sequence in the specified character set is found in
the print data in a Transaction Reply, it is replaced with the equivalent Diebold
print data in the Function Command.
4-37
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
NOTE
All characters must be entered using their hexadecimal values,

except the character set numbers (first column), such as ’01’,
’02’, and so forth, as shown in the example screen below. For
further information on character sets, refer to the NDC+ 6.02
Programmer’s Reference Manual.
The following is a Print Data Mapping example main screen.
G5371_014
The following screen appears after selecting the Add option from the Print
Data Mapping main screen.
G5371_014A
The following screen appears after selecting the Modify option from the Print
Data Mapping main screen.
G5371_014B
4-38
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
The following screen appears after selecting the Add option from the Print
Data Mapping Modify screen.
G5371_014C
4.4.6.10 Reject Reason Codes
The Reject Reason Codes are used as translations between NDC and Diebold.
The codes are transmitted to the network as part of a Solicited Status message.
These codes indicate why a message from the network was rejected by the ATM.
This file is used to convert Diebold Reject Reasons Codes to corresponding
NDC reject reason codes.
The following screen is the Reject Reason Codes main screen.
G5371_015
The following screen appears after selecting the Modify option from the Reject
Reasons Codes main screen.
G5371_015A
4-39
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
4.4.6.11 Screen Control Sequence
The Screen Control Sequence file contains the following three functions.
1. Function Key row mapping
2. Left and right sequence characters
3. NDC/NDC+ screen data control sequence to Diebold screen data

sequence
Setting the data appropriately in the Screen Control Sequence screens allows
the Agilis NDx application software to convert an NDC/NDC+ Screen Data
Sequence to a Diebold Screen Data sequence. All characters must be entered,
using their hexadecimal value. There are no maximum sequence lengths.
The following screen displays the Screen Control main screen.
G5371_017
The following screen appears after selecting the Add option from the Screen
Control main screen.
G5371_017A
4-40
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
The following screen appears after selecting the Modify option from the Screen
G5371_017B
Wildcard Characters
The Screen Control Sequence file accepts wildcard characters, such as the
following:
• ’7F’ - behaves like ’*’, which replaces any number of contiguous characters
• ’07’ - behaves like ’?’, which replaces one character in the screen data
sequence
An example of using a wildcard character is ESC * n. ’n’ is the terminating

character.
If it is necessary that the NDC+ control sequence, "EscP 2 050 Esc \" be mapped
to a Diebold escape sequence, "Esc O 050 EscP 050 0", the following control
sequence mapping using wildcard characters, as shown below, can be used. In
the following scenario, wild card characters can be used to convert the above
NCR escape sequence to a Diebold escape sequence, for all occurrences of
parameters for NDC+ picture control.
The function Key Row section in this file is reserved for cursor position data,
which translates function key rows. If set, the NDC Function Key Row causes
the NDC Function Key Row to be mapped to the Diebold function Key Row
when a set cursor position is sent in the Screen Data. For more information,
refer to Appendix D.
Therefore, NDC Function Key Row #1 translates to Diebold function Key Row 2
and/or NDC Function Key Row #2 translates to Diebold function Key Row 1.
4-41
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Left Sequence
Most loads use either an ICON or a series of characters to point to a function key.
This defines the sequence that points to a left-side key. When converting screen
data, if this sequence is found, then the screen row will be left-justified.
Right Sequence
This defines the sequence that points to a right-side key. When converting screen
data, if this sequence is found, then the screen row will be right-justified.
G5371003
4.4.6.12 Screen Number
The Screen Number Reference Mapping file contains mapping between NDC
and Diebold screen numbers. A valid NDC screen number is 3 characters long.
All three can be digits between 0 and 9, the digits can consist of one alpha
character followed by two digits, such as A00 or A01. A valid Diebold screen
number is also 3 characters long, can be numeric and alphanumeric and range
from 000-999 and A00 to AZZ. For more information on Diebold Reserved
Screens, refer to Section 4.4.6.3 and Table 3-7.
The following screen displays the Screen Number Reference Mapping main
screen.
G5371_016
4-42
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
By default, all NDC Reserved screen numbers are mapped to valid Diebold
screens. If the user wants to map an NDC Reserved Screen to a Diebold Reserved
Screen, they would use this file to map the screen. An example of screen control
mapping, which would go in the screen control sequence translation file with
an NDC Value of C00, "want more time" Reserved Screen (C00) to a Diebold
Reserved Screen (AY0). An example ADD screen control mapping follows.
G5371_016A
The following screen displays the Modify option for the Screen Number
Reference mapping screen.
G5371_016B
New values can be inserted into each user-entry Value field. Select Ok to
accept the new values and return to the previous screen. Select Cancel to return
to the previous screen without adding or changing any new values. To delete
an entry, select the Delete button.
4.4.6.13 Timer Number
The Timer Number file contains information for converting NDC Timer Numbers
to Diebold Timer Numbers. The information is used while converting an NDC
Configuration Parameters Load or NDC Enhanced Configuration Parameters
Load to a Diebold Write III Command.
The following screen is the Timer Number Reference Mapping main screen.
4-43
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_018
The following screen appears after selecting the Add option from the Screen
G5371_018A
G5371_018B
4.4.6.14 Diebold Timer Value
The Diebold default timer values file specifies default values for the Diebold
Timers. If a timer value is not specified in an NDC Configuration Parameters
Load or an NDC Enhanced Configuration Parameters Load, then the default
values are used.
The following screen is the Diebold Timer Value Mapping main screen.
4-44
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_019
The following screen appears after selecting the Modify option from the Diebold
Timer Value Mapping main screen.
G5371_019A
4.4.6.15 Touch Screen Key Codes
The Touch Screen key codes mapping file contains information that converts
an NDC key code to a Diebold key code in Touch Template data. The file
contains some default entries and does not need to be modified if you are
not using a Touch Screen.
The following screen is the Touch Screen Key Code main screen.
G5371_011
The following screen appears after selecting the Add option from the Touch
Screen Key Code main screen.
4-45
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_011A
The following screen appears after selecting the Modify option from the Touch
Screen Key Code main screen.
G5371_011B
4.4.6.16 Voice Number
The Voice Number translation file contains mapping between NDC voice
numbers and Diebold voice control file numbers. A valid NDC voice message
number is 2 to 3 characters long and are numbers ranging from 00 to 999.
A valid Diebold voice control file number is 3 characters long that must be
numeric, ranging from 000 to 999.
The following screen is the Voice Number Reference main screen.
G5371_020
The following screen appears after selecting the Add option from the Voice
4-46
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
G5371_020A
The following screen appears after selecting the Modify option from the Voice
G5371_020B
For more information on how Voice Control Files operate, refer to the Voice
Prompting Using Control Files section, in the guide, Agilis 91x™ Terminal
Programming Manual (TP-820740-001B).
NOTE
The Delete option on the majority of the screen menus

described in the Translations section (Section 4.4.6), allows the
deletion of a selected parameter. In most cases, the Add option
allows you to place additional parameters in the transaction
file for each particular Agilis NDx screen. Therefore, if you
have deleted a parameter by mistake, it can be added back into
the data file.
4-47
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix A
NDC+ Transaction Messages
The Agilis NDx application supports NDC/NDC+ messages. NDC/NDC+

transaction messages include transaction requests, transaction replies, and
solicited status messages, which are equivalent to the Diebold Consumer
Requests (CREQ), function commands, and solicited status messages,
respectively. NDC/NDC+ can also use an interactive transaction response which
is equivalent to the Diebold Open Account Relationship (OAR) message.
The NDC+ transaction request is very similar to the Diebold CREQ, so Agilis
NDx typically does not modify it. However, the NDC+ transaction request may
have the previous transaction data appended to it. In order to append the previous
transaction, an enhanced configuration parameters customization data message
feature is turned on in NDC+. If this feature is turned on, Agilis NDx also
appends the previous transaction data to the end of the transaction request.
The Agilis NDx application supports NDC messages. Table A-1 displays the
Diebold TABS 9000 series messages that equate to the NDC SST messages.
Table A-1 Diebold TABS 9000 Series Messages to NDC SST

messages
NDC+ SST Messages Diebold Messages

Transaction Request ? Consumer Request[1]
Unsolicited Status ? Unsolicited Status
Solicited Status ? Solicited Status
Transaction Reply Command ? Function Command[2]
Terminal Command ? Operational Command
State Table Load ? Write Command I
Screen/Keyboard Data Load ? Write Command II
Configuration Parameters Load ? Write Command III
Enhanced Configuration Parameters ? Write Command III
Load
Pin Data Load ? Not Supported
Interactive Transaction Response ? Write Command V (OAR)
FIT Data Load ? Write Command VI
Encryption Key Change ? Write Command VII
Configuration ID Number Load ? Write Command VIII
A-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table A-1 Diebold TABS 9000 Series Messages to NDC SST

messages (continued)
NDC+ SST Messages Diebold Messages

Date and Time Load ? Enhanced Operational Command
Message
[1] The Agilis NDx application typically does not modify the NDC/NDC+
Transaction Request messages because it is similar to the Diebold Consumer
Request message. However, the NDC/NDC+ Transaction Request may have
the last transaction data appended to it. When an enhanced configuration
parameters customization data message feature is turned on, the previous
transaction is appended.
[2] The Agilis NDx application converts NDC/NDC+ transaction reply messages
to Diebold Function Command messages. Refer to Table A-2 for more
information.
A.1 Function Command Translation
The NDC+ function command, like the Diebold 911 function command, contains
one function identifier. This function identifier will do the multiple task functions
such as deliver and print, deposit and print, and so on. Diebold 912 function
commands contain multiple function identifiers. Agilis NDx converts the NDC+
function identifier into 912 function identifiers. The NDC+ function identifiers
and their Diebold conversions are shown in Table A-2. There are default entries
in the file which can be modified, if necessary.
Table A-2 Function Identifiers
NDC or NDC+ Function

Diebold Function IDs
Function ID
1 A, D Deposit and print
7 A, D Deposit and print
2 B, C, D Dispense, deliver, and print
8 B, C, D Dispense, deliver, and print
B H, B, U, C Parallel dispense, deliver, and print
C H, B, U, C Parallel dispense, deliver, and print
4 4 OR P [1] Print immediate
5 5 Set next state and print
6 G, D Night safe deposit and print
A B, E, Z, C, D Card before cash and print
3 [2] Z, D Display and print
9 [2] Z, D Display and print
3 [2] C, D Deliver and print
A-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table A-2 Function Identifiers (continued)
NDC or NDC+ Function

Diebold Function IDs
Function ID
9 [2] C, D Deliver and print

[1] The NDC or NDC+ host may send a print immediate function command (function ID 4
with no next state. If there is a transaction in progress (a CREQ has already been
sent), then the function identifier will be changed to a P. If there is no transaction in
progress, then the function identifier will remain a 4. If the print immediate function
command has a next state, then the function identifier will remain a 4.
[2] The configuration file must specify 3 and 9 as either display and print, or deliver
and print. Some NDC/NDC+ hosts use the 3 or 9 function ID to deliver money, if a
partial dispense has occurred.
A.2 Function Command Screen Data
The Agilis NDx application also converts screen data in the NDC/NDC+
function command from the 32x16 character NDC+ screen into the Diebold
40x20 character screen. For more information on the Agilis NDx Screen Control
Translation, refer to Section 4.4.6.11.
The Agilis NDx application, with the help of its Screen Control Translation file,
can perform translations such as the following:
• Converts the NDC+ select normal primary character set control sequence
to the Diebold default character set. If any other character set control
sequences are used, they must be converted in the Agilis NDx screen
control sequence file.
• Converts screen insertions. The NDC+ screen number will be converted

into the corresponding Diebold screen number.
• Blinking screen, Color Control Sequences, etc.
A.3 Function Command Print Data
The Agilis NDx application converts the NDC+ printer data into Diebold format.
Although most printer data commands are the same and convert directly, some of
the printer character sets are different. Agilis NDx application includes a print
data conversion file to convert special print data. For more information on the
Print Data Translation file, refer to Section 4.4.6.9.
The Agilis NDx application also converts the special screens used by NDC+
as headers on printed receipts. Refer to Section 4.4.6.12 Screen Number
Translations, for more information.
A-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
A.4 Default Deposit Print Data
The NDC+ deposit printer can print 80 columns of print data, while the Diebold
can only print 55. Agilis NDx converts the deposit print data for the Diebold
terminals so that the most pertinent information is included. The transaction
serial number is printed twice for the 8-character amount buffer, but only once
for the 12-character amount buffer. Agilis NDx converts 20 bytes of Track 2 card
data instead of 30, and Agilis NDx does not convert the machine number. The
Diebold print data includes all other NDC+ print data.
A.5 Open Account Relationship (OAR) Transactions
The NDC+ interactive transaction reply is similar to the Diebold Open Account
Relationship (OAR) Write V command. This command writes OAR screen
configuration data to the terminal during a transaction. The OAR command
enables specific function keys, and Agilis NDx will convert the NDC+ left-hand
keys of F, G, H, and I into the corresponding Diebold left-hand keys of I, H,
G, and F. Agilis NDx will modify the 32x16 cursor position within the OAR
screen data by centering the data on the 40x20 screen. If the screen row is a
function key row with a key that is enabled, Agilis NDx converts the cursor
position as follows:
• If only the right key is enabled, it will be right-justified.
• If only the left key is enabled, it will be left-justified.
• If both keys are enabled, eight spaces will be inserted at the center of
the screen.
A-4
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix B
NDC+ Terminal Commands
NDC+ terminal commands are similar to the Diebold operational command

messages. The startup and go-in-service and shutdown or go-out-of-service
messages are identical and the Agilis NDx application passes these commands
directly to the Agilis 91x software system.
B.1 Terminal Commands
The Agilis NDx application translates the NDC+ Send Configuration ID message
and Send Configuration Information message into a Diebold Configuration
Information Request message. The solicited status that is received is used to
create the NDC+ solicited status. The hardware status, sensor status, and supplies
status that are part of the NDC+ configuration information response are stored by
the Agilis NDx application in its persistent layer. The NDC+ release number
and software ID are retrieved from the Agilis NDx Configuration file and
sent in the solicited status.
The NDC+ Send Supply Counters message is translated into the Diebold
Retrieve Enhanced Supply Counts Message. The accumulated transaction
count, last transaction notes dispensed, and last transaction serial number are
stored by the Agilis NDx application.
The NDC+ send tally information and error log information are not currently
supported by the Agilis NDx application. If the Agilis NDx application receives
these messages, a fixed solicited status message is sent to the host.
The NDC+ Send Date and Time information causes Agilis NDx to send an
enhanced Operational Command message to the Agilis 91x system and send the
response in a solicited status message to the host.
B.2 Configuration Information Response
The Send Configuration Information Terminal Command responds with a

Solicited Status that contains information about the hardware configuration,
fitness of each of the devices, and supplies status for each of the media
containers. This information is stored by the Agilis NDx application and is
returned to the host.
The Agilis NDx application returns configuration information about the

following hardware devices:
• Magnetic Card Reader/Writer

• Cash Handler
• Depository
• Receipt Printer
• Journal Printer
• Encryptor
• Security Camera
• Door Access
B-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
• Flex Disk
• Tamper Indicating Bins
• Cardholder Keyboard
• Operator Keyboard
• Cardholder Display/Voice
The Agilis NDx application returns status information concerning the following
devices:
• Cash Handler
• Depository
• Receipt Printer
• Encryptor
• Security Camera
• Door Access
• Magnetic Card Read/Writer
• Cassette type 1
• Cassette type 2
• Cassette type 3
• Cassette type 4
• Time of Day Clock (Agilis NDx does not change)
• High Order Communications (Agilis NDx does not change)
• System Disk (Agilis NDx does not change)
• Flex Disk (Agilis NDx does not change)
The device status of each of the devices can be as follows:
• No error
• Routine errors have occurred
• Warning conditions have occurred, investigation required
• Suspend (not used by Agilis NDx)
• Fatal error condition exists
The Agilis NDx application returns supply status information for the following
devices and supplies:
• Card Capture Bin

• Cash Handler Reject Bin
• Deposit Bin
• Receipt Paper
• Journal Paper
• Night Safe
• Type 1 Currency
• Type 2 Currency
• Type 3 Currency
• Type 4 Currency
• Statement Paper
The supply status for each of the devices or supplies can be as follows:
• Not Configured
• Good State
• Media Low
• Media Out
• Overfill
B-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
An example Supply Status screen, where all statuses are determined, displays
below.
G5371_021
B-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix C
Agilis NDx Error Processing
The Agilis NDx application executes internal error functions or event handlers.
These internal functions do such things such as update supplies and sensor
statuses, convert unsolicited statuses into solicited statuses, and sends a function
command to the Agilis 91x system. Additional unsolicited statuses can be
sent to the host.
The Agilis NDx application has an error translation table that it uses for the
translation of Diebold MDS status messages into an NDC+ error messages.
When Agilis NDx receives a solicited or unsolicited status, it looks up the MDS
status in the error translation table, and then uses the information to send the
translated message to the host. If there is no match in the status translation table,
the error is logged in the Agilis NDx main error log file and discarded.
NDC+ Error Message

After translating the MDS status into NDC+ status, Agilis NDx sends the
following error information to the host:
• A message class indicating that the status is solicited or unsolicited
• A device ID to identify the device on which the error occurred
• Transaction status that tells the host what happened to the transaction
in process when the error occurred. The transaction status is used for a
solicited status message.
• A device status that tells the host what happened to the transaction in
process when the error occurred. The device status is used for an unsolicited
status message.
• A severity code that tells the host whether the error was fatal or a warning
• A supplies status that gives the state of the media bin. The Agilis NDx
application updates and sends the supplies status in both solicited and
unsolicited status messages.
• M-status which shows the precise error that occurred at the terminal
• M-data which provides further information about the error
C-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
While constructing the error message for the host, the Agilis NDx application
also executes other functions depending on the configuration of the translation
tables. The Agilis NDx application performs the following functions during
error processing:
• If the dump cash during next function command is set in the status
translation table, then the Agilis NDx application will place a dump function
identifier at the beginning of the next function command that it receives.
• If the unsolicited status is received in Maintenance Mode and the suppress

when in Maintenance Mode flag is set, then the Agilis NDx application will
not send the message to the host.
NOTE
If an MDS Status is sent from the Agilis 91x system as part of a

Solicited Status message, for which there is no mapping found
in the Error Translation Table, the Agilis NDx application
simply logs the status in its main error log file and does not
respond. The recovery situation in this scenario will be an
eventual timeout on the terminal side. For more information on
statuses, refer to the Agilis 91x™ Status Reference Manual
(TP-820741-001B).
Paper Low Status for Receipt Printer

The TCS file, c:\diebold\tcs\TRANSTBL.TXT controls filtering and translating
of network statuses. By default, this file filters out the paper low status (:2D) for
the Receipt printer (PR01).
A file, c:\diebold\tcs\CUSTSTAT.TXT, can be created to override the

TRANSTBL.TXT file.
The following is an example of a CUSTSTAT.TXT entry to send Receipt printer

paper low unsolicited status to the network.
EXAMPLE
PR01 :2D
:2D "SUPPRESS" "4828000"
END PR01
The first parameter is the MDS status to be filtered. In this example, any MDS
status beginning with :2D will be filtered using this entry in the file.
The second parameter is the 9000-style solicited status value to send to the
network. SUPPRESS is a reserved keyword that indicates no status will be sent.
The third parameter is the 9000-style unsolicited status value to send to the
network. In this example, 4828000 will be sent to the network.
The table for PR01 (Thermal consumer printer) shows that paper low is
suppressed in TRANSTBL.TXT.
For more information , refer to Agilis 91x™ Terminal Programming Manual

(TP-820740-001B) in Section C, "Filtering and Translating Network Status."
C-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
For more information about the TRANSTBL.TXT file, refer to the Agilis 91x™
Status Reference Manual (TP-820741-001B).
C-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix D
Translation File Descriptions
Table D-1 displays examples of default conversions for translation files.
Table D-1 Translation File Default Conversions
Translation File Description Translation From? Translation To

Card-before-Cash NDC/NDC+ card-before-cash screen? Diebold card-before-cash screens
Default Touch template[1] NDC/NDC+ screen? Diebold Touch Template Excape
Sequence
Diebold Reserved Screens NDC/NDC+ screen number? Diebold screen number
Error Status 912 MDS status? NDC/NDC+ Error status
Function ID NDC/NDC+ Function IDs ? Diebold Function IDs, Diebold Screens
+. Refer to Table A-2.
IDM document Enable Code
conversion fil
Key Codes NDC/NDC+ Touch Screen Key Codes? Diebold Touch Screen Key Codes
Logo number NDC/NDC+ logo number ? Diebold icon number
Picture Number NDC/NDC+ picture number? Diebold icon number
Print Data NDC/NDC+ print data character set ? Diebold print data character set
Reject Reason Diebold Reject Reason Code ? NDC/NDC+ Reject value
Screen Control Sequences NDC/NDC+ screen control conversion Diebold screen control sequence.
sequence ?
Screen number NDC/NDC+ screen number ? Diebold screen number
Timer Number NDC/NDC+ timer number ? Diebold timer number
Timer Value NDC/NDC+ timer valuer ? Diebold timer value number
Touch Screen Key Codes NDC/NDC+ touch screen key codes? Diebold touch screen key codes
Voice Number NDC/NDC+ voice control number ? Diebold voice control file number
[1] NCR has a default touch template that it associates with screens that do not have an explicitly defined touch template. This file
specifies the layout of this default touch template. As many touch areas can be defined as needed in this file. Each touch
area is defined by the X and Y coordinates of its opposite corners and the associated Key code. This layout should be
defined in Diebold format.
D-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix E
Configuration Registry
The following listing displays the Configuration Registry file entries for the NDx
application installation. These are the keys and files that are installed after Setup
is selected from the CD-ROM and the installation is complete. To uninstall the
Agilis NDx application, these registry files must be manually deleted. To do this,
select the STARTbutton on the Windows NT or Windows XPe desktop. Select
the Run option. Type Regedit to open the registry.
NOTE
Be sure to backup the registry before you proceed to delete

these entries. To do so, while in the Regedit program. select
the Registry option on the top menu. Select the Export Registry
Files option and create a new file name, saving the current
registry. Do this before deleting any of the following entries.
Table E-1 Configuration Registry Entries
Configuration Registry Entries
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\ACO2] "Version"="product version number"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2] "path"="none"

"color"="black"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Clear Static Data]

"path"="scripts/ACO2Config.pl?ClearStaticData"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\General Settings]

"path"="scripts/ACO2Config.pl?ACO2CFG"
E-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table E-1 Configuration Registry Entries (continued)
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Hardware

Configuration] "path"="scripts/ACO2Config.pl?HwConfig"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Sensors Status]

"path"="scripts/ACO2Config.pl?Sensors"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Supplies Status]

"path"="scripts/ACO2Config.pl?Supplies"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations]

"path"="none" "color"="black"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Card

Before Cash] "path"="scripts/ACO2Config.pl?CardCash"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\De-

fault Touch Template] "path"="scripts/ACO2Config.pl?Tchdef"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Transla-

tions\Diebold Reserved Screens] "path"="scripts/ACO2Config.pl?ReservedScrnNumList"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Error

Status] "path"="scripts/ACO2Config.pl?NDCStat"

tions\Function ID] "path"="scripts/ACO2Config.pl?FuncID"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Logo

Number] "path"="scripts/ACO2Config.pl?Logo"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Pic-

ture Number] "path"="scripts/ACO2Config.pl?Picture"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Print

Data] "path"="scripts/ACO2Config.pl?PrintDat"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Extended features\ACO2\Translations\Re-

ject Reason Codes] "path"="scripts/ACO2Config.pl?RRCTrans"

tions\Screen Control Sequence] "path"="scripts/ACO2Config.pl?ScrnSq"

tions\Screen Number] "path"="scripts/ACO2Config.pl?ScreenNum"

tions\Timer Number] "path"="scripts/ACO2Config.pl?/TimerNum"

tions\Timer Value] "path"="scripts/ACO2Config.pl?TimerVal"

tions\Touch Screen Key Codes] "path"="scripts/ACO2Config.pl?KeyCodes"
E-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table E-1 Configuration Registry Entries (continued)

tions\Voice Number] "path"="scripts/ACO2Config.pl?Voice"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files\Installation]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files\Installation\ACO2

main] "path"="scripts/dispLog.pl?Log~files:~ACO2~main&c:\\\\diebold\\\\ACO2\\\\AgilisNDx.log"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files\Installation\ACO2

silent] "path"="scripts/dispLog.pl?Log~files:~ACO2~silent&c:\\\\diebold\\\\tcs~plus~applications\\\\aco2.log"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files\Runtime system]
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View

log files\Runtime system\ACO2 Language Code Log]"path"="scripts/dispLog.pl?Log~files:~ACO2~Lan-
guage~Code~Log&c:\\\\diebold\\\\ACO2\\\\logs\\\\aco2lgcd.log"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log

files\Runtime system\ACO2 Screen Control Log] "path"="scripts/dispLog.pl?Log~files:~ACO2~Screen~Con-
trol~Log&c:\\\\diebold\\\\ACO2\\\\logs\\\\aco2scct.log"

files\Runtime system\ACO2 Screen Reference Log] "path"="scripts/dispLog.pl?Log~files:~ACO2~Screen~Refer-
ence~Log&c:\\\\diebold\\\\ACO2\\\\logs\\\\aco2scrf.log"

files\Runtime system\ACO2 State Translation Log] "path"="scripts/dispLog.pl?Log~files:~ACO2~State~Transla-
tion~Log&c:\\\\diebold\\\\ACO2\\\\logs\\\\aco2stxl.log"
[HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\Configuration menu\General settings\Log files\View log files\Runtime sys-

tem\ACO2 User Exit Log] "path"="scripts/dispLog.pl?Log~files:~ACO2~User~Exit~Log&c:\\\\diebold\\\\ACO2\\\\logs\\\\aco2uej.log"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID}]"UninstallString"="RunDll32
C:\\PROGRA~1\\COMMON~1\\INSTAL~1\\engine\\6\\INTEL3~1\\Ctor.dll,LaunchSetup \"C:\\Program Files\\InstallShield
Installation Information\\{ GUID}\\Setup.exe\" -l0x9 " "DisplayName"="Agilis NDX" "LogFile"="C:\\Program Files\\InstallShield
Installation Information\\{GUID}\\setup.ilg"
E-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix F
Required Agilis 91x System Settings for Agilis NDx
The following table lists the required Agilis 91x system settings for either the
system registry or system files, that are necessary for the Agilis NDx application
software to function properly.
All the following settings must be manually configured by setting the appropriate
bits in the registry. The weight values correspond to the weight values in the
MDS Maintenance manual to select an appropriate option value, while the hex
value indicates the actual setting in the registry.
Calculating the Offset (DIT Option)

The offset should be calculated as a zero-based (0) offset as shown in the
following example.
EXAMPLE
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19? .
Combination of Options
To use a combination of options, review the following example.
EXAMPLE
In System Control 2 Device Properties, Option 2 settings, add the values of the
desired options and use the sum for the setting of Option 2. For example,
a value of 024 defines a terminal that accepts and performs print-immediate
Function Commands while it is in the Maintenance mode (option value 008)
and rejects any Write Command messages received while it is in an In-service
mode (option value 016). Next, calculate the corresponding hex value of the sum
and enter that value in the registry.
NOTE
The ditparam settings in the registry shown below are

examples of what someone might examine during the time of
the configuration. These parameters or settings might not be
the actual values when you are trying to configure Agilis 91x
system. The objective is to set the appropriate weights into
the bit settings for the option selected.
Table F-1 Required Agilis 91x System Settings for Agilis NDx
1
Status Always send MDS status
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\system3]
Setting "ditparam"=hex:4f,44,5f,44,49,54,00,0d,00,53,59,30,33,01,ff,ff,00,00,50,00,01,\
00,00,00,02,5a,00,da,bc,f6,77
DIT Option System Control 3 DIT->Option 1: Offset 16 – Bit 2 (hex: 04) (Weight 004)
F-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table F-1 Required Agilis 91x System Settings for Agilis NDx (continued)
2
Status Send Supervisory status at Logon
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\high side comm]
Setting "ditparam"=hex:4f,44,5f,44,49,54,00,0d,00,48,43,30,31,01,00,00,30,64,00,ff,ff,\
ff,cc,f0,00,00,00,40,40,40,40
DIT Option High-Side Comm DIT->Option 1: Offset 16 – (hex: 31) (Weight 049) [Send status
at logon]
00,00,00,02,5a,00,da,bc,f6,77
DIT Option SYSTEM Control 2 DIT->Option 2: Offset 17 – Bit 2 (hex: 04) (Weight 004)
3
Status Send Supervisory status at Logoff
00,00,00,02,5a,00,da,bc,f6,77
DIT Option SYSTEM Control 2 DIT->Option 2: Offset 17- Bit 7 (hex: 80) (Weight 128)
4
Status Terminal rejects any Write Command messages received while it is in an in-service
mode
00,00,00,02,5a,00,da,bc,f6,77
DIT Option SYSTEM Control 2 DIT->Option 2: Offset 17- Bit 4 (hex: 10) (Weight 16)
5
Status Send Unsolicited Status during Maintenance
00,00,00,02,5a,00,da,bc,f6,77
6
Status Cassette Tamper enabled must be set to "On"
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\cash dispenser]
Setting "ditparam"=hex:4f,44,5f,44,49,54,00,10,00,44,49,30,31,01,46,31,01,00,00,00,00,\
00,08,32,32,07,9c,00,00,00,00
DIT Option Cash Dispenser DIT->Option 1: Offset 16 – Bit 1 (hex: 02) (Weight 002)
7
Status English Language translation of fault statuses should be set to "Send to journal printer"
00,00,00,02,5a,00,da,bc,f6,77
8
F-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Status Consumer Display OAR transaction screen should be set to Enabled

Registry HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\system2]
00,00,00,02,5a,00,da,bc,f6,77
DIT Option SYSTEM Control 2 DIT->Option 5: Weight 008 (Offset 20) [Show Transaction Request
State screen after operation key is pressed on an OAR screen]
9
Status Maintain Configuration ID after Write Cmd VII
00,00,00,02,5a,00,da,bc,f6,77
DIT Option System Control 3 DIT->Option 1: Offset 16 – Bit 5 (hex: 20) (Weight 032)
10
Status Consumer Keypad Operation keys to 12 Operation Keys
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\consumer key-
Setting board] "ditparam"=hex:4f,44,5f,44,49,54,00,0d,00,4b,45,30,31,01,38,31,01,00,ff,ff,ff,\
ff,08,32,32,5a,00,da,bc,f6,77
DIT Option Consumer Keypad DIT->Option 1: Offset 16 – Bit 2 (hex: 04) (Weight 004)
[For this option, do not add the weights, simply change 01 to 04]
11
Status Presenter - Action after customer timeout to "Retain and Do Not Report Status"
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\consumer facia]
Setting "ditparam"=hex:4f,44,5f,44,49,54,00,0d,00,44,52,30,31,01,46,32,00,06,00,00,00,\
01,e5,e7,00,00,00,00,00,00,00
DIT Option Fascia DIT->Option 4: Offset 19 (hex: 00) (Weight 000)
Fascia DIT->Option 5: Offset 20 (hex: 00) (Weight 000)
12
Status Continuous Availability feature turned Off
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\AFW.INI\CASOption]
Setting "enableCAS"=hex:4f,44,5f,52,45,47,49,53,54,52,59,5f,55,53,48,4f,52,54,00,01,00
# Second to last character is the CAS enable flag 00=>disabled, 01=>enabled
DIT Option CASOption-> Offset 19 - Set to 00 (disabled)
13
Status Invert function keys FGHI to IHGF.
This setting is automatically set by the installation procedure.
F-3
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\consumer
Setting keyboard]
"ditparam"=hex:4f,44,5f,44,49,54,00,0d,00,4b,45,30,31,01,38,31,01,00,ff,ff,ff,\
ff,08,32,32,5a,00,da,bc,f6,77
# The ditparam data type is based on the following:
# byte 14 is the device enabled flag. The dit data follows the option number
# information in the Maintenance Manual. The two bytes before ff are the
# reserved crc data.
"Product Type"="telephone layout, 16 key, decimal point"
# reserved
"Product Description"="Telephone layout, 16 key, decimal point"
# reserved
"Image Name"="TEL01.jpg"
# reserved
"invert_keys"="off"
# reserved
"Keyboard Template"="epp\\epptel01.dat"
# reserved
"Keyboard DEA Template"="epp\\epptel02.dat"
# reserved
DIT Option Set "invert_keys"="on"
14
Status Relocation of Agilis NDx default Reserved Screens
Registry Import newreserved.reg file into the registry with the following command from
Setting or File c:\Diebold\web\scripts\
“reg.pl IMPORT newreserved.reg”

NOTE: This setting is automatically set by the installation procedure.
DIT Option or NONE
Change
15
Status LSC Setting
Registry In c:\Diebold\lsc\lsc.ini file:
Setting [Stored Network Loads]
DIT Option Notify Host After Successful Local Load => "Yes"
16
Status SXA Settings
Registry 1. In SXA.ini file:
Setting or File Section [Configurables]
Enabled = Yes
91xMessage = No
2. In UserExit.lst file, add the following line in the User Exit list section:
[ User Exit List ]
ACO="C:\diebold\ACO2\Dll\ACO2UEJ.dll"

DIT Option OR NONE
Change
17
F-4
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Status TCS.SDT File Settings

Registry TCS.SDT File Settings
Setting or File In c:\Diebold\tcs\tcs.sdt file, comment out the following line:
comment out the following line:
//#include "app\scvcsd.adt"
and ADD the following entries:

#include "app\StXlate.adt"
#include "app\ScrnCtrl.adt"
#include "app\scrnRef.adt"

DIT Option OR NONE
Change
OPTIONAL
Status To change default foreground and background colors:
Registry [HKEY_LOCAL_MACHINE\SOFTWARE\Diebold\TCS\DEVICE.INI\consumer display]
Setting "ditparam"=hex:4f,44,5f,44,49,54,00,10,00,44,53,30,31,01,00,60,01,3c,03,1b,0f,\
00,4e,00,02,ea,bd,ff,ff,ff,ff
# byte 14 is the device enabled flag. The dit data follows the option number.
# information in the Maintenance Manual. The two bytes before ff are the
# reserved crc data.
"vid1"="consumer"
# reserved
"vid2"="system"
# reserved
"Service Monitor"="Color"
# reserved
"browser_timeout"="15"
# reserved
"background"="0"
# reserved
"foreground"="7"
# reserved
DIT Option Change foreground and background parameters accordingly:
OR Parameter White - Black (0 fore 7 back)
Change White - Red (4 fore 7 back)
Yellow - Blue (14 fore 1 back)
F-5
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Appendix G
Native NDC+ and Agilis NDx DPM Differences
The differences between native NDC+ document processing and Agilis NDx
document processing is detailed in the following paragraphs.
Because of several hardware differences between DPM (Document Processing

Module) and IDM, some information cannot be reported. If so, the corresponding
character in the message will assume a default value as indicated.
Agilis NDx will not send the detail of the DPM cassettes supplies and fitness
status. The Agilis 91x IDM cassette errors do not detail which cassette generates
the error. Therefore, Agilis NDx will always set the first cassette supply and
fitness (pocket A).
The following tables describes the contents of the DPM Device Fault Status
message.
Table G-1 Error Severity Field
Character Description Agilis NDx
1 DPM core and DPU core (incorporating Handled

SCSI/TCM interface, DPU firmware,
front camera, transport)
2 DPU rear camera Always 0 (no error)
3 DPU front printer Handled
4 DPU rear printer Always 0 (no error)
5 DPU encoder Always 0 (no error)
6 DPM magnetic ink detector Always 0 (no error)
7 DPU recognition board (incorporating Handled
omnifont, handprint and CAV
capabilities)
8 DPM statement printer interface (only Always 0 (no error)
significant on 5665 - always ‘no error’
on DP-ATM)
9 DPM reject/envelope bin (Bin 1) Handled
11 DPM pocket A Handled
11 DPM pocket B Always 0 (no error)
12 DPM pocket C (only significant on 5665 Always 0 (no error)
- always ‘no error’ on DP-ATM)
13 DPM escrow (only significant on 5665 - Always 0 (no error)
always ‘no error’ on DP-ATM)
14 DPM double document detect (not Always 0 (no error)
supported - always ‘no error’)
G-1
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
Table G-2 Supplies Status Field
Character Description Agilis NDx
1 DPU encoder ribbon Always 1 (good)

2 DPU front printer inkwell Always 1 (good)
3 DPU rear printer inkwell Always 1 (good)
4 DPM statement printer capture bin Always 0 (no new state or state not
determined)
5 DPM reject/envelope bin (Bin 1) Handled
6 DPM pocket A Handled
7 DPM pocket B Always 1 (good)
8 DPM pocket C (only significant on 5665 Always 1 (good)
- always ‘good’ on DP-ATM)
Device fault messages will not report the following status fields in NDx:
• M-Status and M-data fields

• Transaction/Device status sub fields related to candidate document
However, in Agilis NDx, the Sensor Device Fault Status message, the DPM
sensor character (19) will always be set to 1 (DPM pockets closed).
Other Unsupported NDx Fields and Features

The following fields are NOT supported under Agilis NDx, as follows:
• Control Candidates/Identify field in the NDC+ ’Q’ State
• Zone Verify Control field in the NDC+ ’Q’ state
• Magnetism Check control field in the NDC+ ’Q’ State
• Document Already Present Next State Exit in the ’Q’ extension, State 3
• Exception Type 1 Next State Exit field in the ’Q’ extension, State 3
• The download of 5-digit screen numbers
• The Image List Lift Contol field in Extension 1 to State ’Q’
• NDC Timer Number 87
• NDC+ Timer Number 94
• Device fault message will not report Transaction/Device status sub fields
related to candidate document
G-2
TP-820803 (Ed. B)
Tue Apr 08 15:32:44 2003
• NDC images archive and handling feature
The following error conditions cannot be detected:
- NDC+ ’Q’ state "Upside Down Document Screen" - extension 2 to State Q

- NDC+ ’Q’ state "Wrong Way Up Document Screen" - extension 2 to
State Q
- NDC+ ’P’ state "CAV Unavailable Next State Exit"
- NDC+ ’P’ state "No Document Present Next State Exit"
• Never includes the ’Zone Verification Data’ fields in the Transaction

Request Message
• Does not insert the Read Zone Data Identifier into the Transaction Request
Message
NDx Supported Features

The following features are supported under Agilis NDx, as follows:
• Documents are processed only via "Q-DPM Document Accept State"
• Only the full front section of the paper check is lifted.
• IDM prints a single line of up to 100 characters on the deposited document.

However, the location of the printed line is a variable determined by
configuration values. NDx prints the data present into the transaction reply
message of up to 100 characters. If a reference to the configuration data is
referenced in the message, then the NDx application prints the default data.
• Sets the DPM pocket C supply status to 0 (zero)
• Processes the check retain error recovery action without showing the DPM
Document Captured screen during Close State processing.
• If the value in the Lift Front/Rear Image field in the NDC+ ’Q’ state
is anything other than a zero (0) or 1 (supported) value, the NDx
application reads the value of the related configuration parameter from the
main configuration file. This state is included in the Agilis NDx state
flow. However, if the value indicated in the configuration file is 2 or 3
(unsupported NDx values), the resulting state is invalid and will be rejected.
G-3
TP-820803 (Ed. B)

TP 820803

Uploaded by

Copyright:

Available Formats

TP 820803

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TP 820803

Uploaded by

Copyright:

Available Formats

PRELIMINARY - DRAFT COPY

Tue Apr 08 15:32:44 2003

Agilis NDx™ Configuration Guide

Document Number Date Remarks

Section 1 Purpose and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Section 2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Section 3 Setup and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Section 4 Manual Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

4.4.6.12 Screen Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

Appendix A NDC+ Transaction Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B NDC+ Terminal Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C Agilis NDx Error Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix D Translation File Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Appendix E Configuration Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1

Appendix G Native NDC+ and Agilis NDx DPM Differences . . . . . . . . . . . . . . . . . . . . . . . . . G-1

Table 2-1 Basic Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

• Microsoft® Windows® NT 4.0 operating system using Diebold ix Series and

• Microsoft® Windows® XPe operating system using the Diebold Opteva™

The Agilis NDx product is a terminal resident software application developed

Microsoft® Windows® NT Operating System. If using the Diebold ix Series

Microsoft® Windows® XPe Operating System. If using the Diebold Opteva

• Allows Diebold terminals to report various statuses to the host by mapping

• Includes a web-based configurator that allows simple manual configuration

2.1 Hardware Requirements

2.1.1 System Hardware Supported

The following hardware is supported for the Agilis NDx Configuration

Table 2-1 Basic Hardware Requirements

HARDWARE Diebold ix and Opteva™ NCR® and foreign

2.1.2 Agilis NDx Devices and Features

Table 2-2 Agilis NDx Devices and Features

Device Diebold ix Series NCR and Foreign Diebold Opteva Series

Table 2-2 Agilis NDx Devices and Features (continued)

Device Diebold ix Series NCR and Foreign Diebold Opteva Series

Other hardware devices supported by the Agilis NDx software running on

• Fifth Cassette for the Cash Dispenser

TTU for Maintenance, on Diebold ix Series and foreign vendor

• Arabic and Hebrew - XFS does not support right to

• Arabic and Thai - XFS does not support complex scripts

2.1.3 System Hardware Not Supported

• Bar Code Reader

2.2 Software Requirements

Table 2-3 Software Requirements

Diebold ix Series NCR and foreign Diebold Opteva

Agilis Base Communications (ABC)

AMI for Opteva (Windows XPe ONLY)

Electronic Data Capture (EDC) - Coexists

The term coexists means that the application or user exit is

Event Management System (EMS/Remote Notifier) - Coexists

Iq CRM Agent - Coexists

Iq ESD Agent - Coexists

Local Screen Changes (LSC) - Coexists

Message Authentication Code (MAC) - Coexists

Software Extended Application (SXA)

The Agilis NDx application was developed as a User Exit.

Windows NT 4.0 Operating System

Windows XPe Operating System

XApWare Plus - Coexists

• XAp Coupon Plus

NCR® National Cash Register