Opteva Status Reference Manual (Mas Completo)

21/1 21/10/ 0/20 2014 14

(CONFIDENTIA (CONFIDENTIAL L - Trade Trade Secret Secret Materia Material) l) TP-820 TP-82074 741-0 1-001 01F F * Agilis® Agilis® 91x 91x (XV) (XV) and and Agilis® Agilis® 91x 91x for for Opte Opteva va Stat Status us Refere Referenc nce e Manu Manual al

Agilis® 91x (XV) and Agilis® 91x for Opteva Status Reference Manual Copyright ©D iebold, iebold, Incorporated Incorporated TP-820741-001F TP-820741-001F PD 5234 September 2013 CONFIDENTIAL - Trade Secret Material Only Diebold and entities granted an express written license by Diebold may possess or use this material. Unauthorized possession or use is illegal and is punishable by fine and/or imprisonment. Important - click here for terms and conditions governing the use of this document. Document History Document Number

Date

Remarks

TPTP-820741-001A

2/20 /2003 Agil Agilis is 91x ver versio sion 1.0

TPTP-820741-001B

3/20 /2004 Add Additio ition nal devi device ces s add added

TP-82 TP-8207 0741 41-0 -001 01C C

12/20 12/2004 04 Gene Genera rall update update for for Agilis Agilis 91x XV, Versio Version n 1.2 and and Agilis Agilis 91x 91x for Opteva Opteva 1.3 1.3

TPTP-820741-001D

4/20 /2005 Title Title of th the man manual cha changed

TP-82 TP-820 0741741-00 001E 1E

8/20 8/2010 10 Upda Update ted d Stat Status us Descri Descript ptio ion n for for DR01: DR01:3A 3A:3 :33: 3:41 41 Statu Status s Messag Message e

TPTP-820741-001F

9/20 /2013 Add Added the the DR0 DR01:23 :23:00 :00:30 :30 Sta Status tus Messa Messag ge

Section 1 Introduction This manual provides device status information for Agilis® 91x operating in both an Extensions for Financial Services (XFS) environment and the Agilis Module Interface (AMI) environment. Device status messages can be printed on the journ journal al printer printer.. Device status st atus message messages s might also be be sent sent to the network. network. The manual describes the standard Agilis 91x status messages only. For information about customizing status and Agilis 91x for Opteva Opteva Terminal Terminal Program Programming ming Manua Manual l (TP-820740-001C messages, refer to the Agilis 91x (XV) and (TP-820740-001C). ).

1.1 Manual Organization For genera generall informa i nformation tion about status st atus messages, refer t o Section 2. 2. Section 3 provides 3 provides a detailed description of the status messages for each terminal device. The devices are in alphabetical order by the device type and number. Refer to the appendixes for help in interpreting the 911 and 912 status messages, and English-language status messages. These appendixes appendixes include the following follow ing information: A hexade hexadecimal-to cimal-to-d -decima ecimall conversion conversion chart chart and and hexade hexadecimal-to cimal-to-bin -binar ary y conversion conversion chart chart ( Appen Appendix dix A) A) Cross-references to match the 911 status messages and 912 status messages sent to the network with the fault status messages described in this manual ( Appen Appendix dix B and B and App Appen endix dix C) C) A cross-refere cross-reference nce to match match the Eng English-la lish-lang ngua uage ge messag messages es printed printed on the the journa journall printer printer with the fault status messages described in this manual ( Appen Appendix dix D) D)

1.2 Related Documents For a detailed description of status messages sent to the network, refer to the Agilis 91x (XV) and Agilis 91x for Opteva Terminal T erminal Programming Manual (TP-820740-001C (TP-820740-001C). ). That manual also provides information about filtering and http://techpubs.di ebol d.com /techpubs/books/TP- 820741- 001/TP- 820741- 001- 1.htm

1/107

21/1 21/10/ 0/20 2014 14


customizing statuses sent to the network.

Section 2 Overview This section contains general information about fault status messages. This general information can be useful in interpreting and managing fault status messages. The following topics are discussed in this section: Format of status messages printed on the journal printer ( Section 2.1) 2.1) Status handler definitions (Section (Section 2.2) 2.2)

2.1 Format of Status Messages Printed on the Journal Printer This section provides a description of how the following status messages are printed on the journal printer: Fault status messages (Section (Section 2.1.1) 2.1.1) Status messages for maintenance procedures (Section ( Section 2.1.2) 2.1.2)

2.1.1 Fault Status Messages Fault status messages print on the journal printer in the following format:

001CR01:3E:48:40 The entry entry includes the t he following information: 001 - Solicited or Unsolicited CR01 - Device Type and Number :3E:48:40 - Fault Status Solicited statuses and unsolicited statuses are indicated by the following codes: 000 - unsolicited status; 001 through 009 - solicited status. The solicited status code 001 through 009 provides service personnel with an indication of when the status st atus occurre occ urred d during during the processing. As an examp example, le, assume that the receipt receipt printer printer is directed to do a print, print, then a deliver, deliver, and and then then a retain retain.. If this field is 002, the deliver is the function that caused the status because it is the second function. To determine determine the devices, devices , refer to t o Table 2-1 for 2-1 for the device type and number.

DEVICE TYPE AND NUMBER

Table 2-1 Device Type and Number DEVICE

AL01 AL01

Alarms Alarms

C NS

State/function processing

CR01

Card reader

DI01 or D901

Cash dispenser (not including present, dump, and restore functions)

DP01

Depositor (not including envelope dispensing functions)

DR01

Cash presenter (present, dump, and restore functions for cash dispenser)

ED01

Encryption/decryption

EP01

Encrypting PIN pad

KE01

Consumer keypad

LT01

Indicators and contacts

MN01

Modem

PB01

Passbook printer (Opteva only)

PF01

PIN/FIT

http://techpubs.di ebol d.com /techpubs/books/TP- 820741- 001/TP- 820741- 001- 1.htm

2/107

21/1 21/10/ 0/20 2014 14


****

Power-up

PR01

Receipt printer

PR02

Journal printer

PR03

Electronic Data Capture

SD01

Envelope dispenser (envelope dispense functions for a depositor)

SP01

Statement printer (Opteva only)

TS01

Touch screen

VC01

Voice

To determine the meaning of the fault status, find the status from the appropriate table in Section 3. 3. Those tables are in alphabetical order by device type and number. You may also refer to the table of contents to find the appropriate table. For example, example, to determine what CR01:3E:48:40 means, means, refer to Table 3-5 in 3-5 in Section 3.6. 3.6. The table indicates that the card retain bin is full and must be emptied.

2.1.2 Status Messages for Maintenance Procedures Whenever an operator logs on the Maintenance software and the terminal is communicating with the network, an entry is printed on the journal printer. This entry is shown in the following format:

000MNT:XX:YY The XX indicates the code number of the operator who is logged on. The first X identifies the group range (0 through 5) and the second X identifies the operator range (1 through 8). EXAMPLE

00 - Maintenance mode requested (no items selected) 01 - group 0, operator 1 02 - group 0, operator 2 . . . 08 - group 0, operator 8 11 - group 1, operator 1 12 - group 1, operator 2 . . . 18 - group 1, operator 8 . . . 58 - group 5, operator 8 The YY indicates the maintenance item selected as shown in Table 2-2. 2-2. Table 2-2 Maintenance Items MAINTENANCE ITEM (YY in mes message)

ITEM ITEM SE SEL LECT ECTED

00

Logon

01

Manager

02

DES Keys

03

Installation

04

Supply


3/107

21/10/2014

(CONFIDENTIAL - Trade Secret Material) TP-820741-001F * Agilis® 91x (XV) and Agilis® 91x for Opteva Status Reference Manual

06

Status List

07

Clear List

0A

Attention message

0B

Log Off

For example, 000MNT:07:04 indicates that operator 7 from group 0 has selected Supply. If the terminal is not communicating with the network when the maintenance item is selected, the selection is saved. Up to six selections can be saved. If more than six selections are made, only the most recent six are saved. When the terminal communicates with the network, the maintenance selections that have been saved are printed on the journal printer in the following format:

000MNT:XX:YY:XX :YY:XX:YY :XX:YY:XX :YY:XX:YY The first entry printed is the most recent maintenance selection. The second entry printed is the next most recent maintenance selection, and so on, up to six entries.

2.2 Status Handler Definitions The first byte of a status message is called the status handler byte. The definitions for this byte are in Table 2-3. NOTE Within the device status descriptions in Section 3, there are some exceptions to the information found in this table.

Status

Status Description

Table 2-3 Status Handler Definitions Can the Logged Did the Did the Operation on Unsolicited Solicited Operation Operation Occur Journal Repairable Status Status Start Finish Again Printer by Comments

:21

Operation completed

No

No

Yes

Yes

Yes

No

Not needed No problem

:23

Timeout

No

Yes

Yes

No

Yes

Yes

Not needed The terminal timed-out waiting for a response

:24

Cancel

No

Yes

Yes

No

Yes

Yes

Not needed The consumer pressed the CANCEL key.

:2D

Attention required

No [1]

Yes

Yes

Yes

Yes

Yes

Institution

:30

Reject

No [1]

Yes

No

No

Yes

Yes

Not needed Device dependent

:31

Idle

No

No

Yes

Yes

Yes

No


:38

Communications Yes [1]

Yes [1]

Yes

No

No

Yes [1]

Service technician

No response

:39

Fault

Yes

Yes

No

No

No

Yes

Service technician

No attempt to start operation

:3A

Fault

Yes

Yes

Yes

No

No

Yes

Service technician

May have started

http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

Supplies low

4/107

21/10/2014


:3B

Fault

No

No

Yes

No

Maybe

No

operation Not needed Try operation again

:3C

Warning

Yes

No

Yes

Yes

Yes

Yes

Institution

Degraded performance

:3D

Fault

Yes

Yes

Yes

No

No

Yes

Institution

Supplies out

:3E

Fault

Yes [1]

Yes [1]

Yes

No

No

Yes

Institution

Institution repair

:3F

Warning

No [1]

Yes [1]

Yes

No

Yes

Yes [1]


[1] Within

the device status descriptions in Section 3, there are some exceptions to this table.

Section 3 Status Message Descriptions This section provides descriptions of the status messages for each device. The devices are in alphabetical order by device type and number. For example, the status message description for the card reader status CR01:3E:48:40 includes the information shown in following table:

Status Message

Description

Sent to Journal

CR01:3E:48:40 The card is jammed in the card Yes reader. The card cannot be returned to the consumer. It might be possible to retain the card.

Network Action Attempt to clear the jam by retaining the card. If successful, display a screen to notify the consumer that the card was retained, then continue with normal operation. If unsuccessful, remove the terminal from service.

Onsite Action Clear the jam.

The status message tables include the following information: Status Message - the device fault status message Description - a description of the status message Sent to Journal - set to yes or no to indicate if the status is printed on the journal printer. Network Action - a guide to the network programmer. This column represents only suggestions, and indicates the message level action to be taken at the time the condition occurs. Follow-up physical action may be required. If a status message is not sent to the network, no network action will be included.

Refer to Appendix B and Appendix C for a list of 911 and 912 network status messages and cross-references to help you locate the descriptions for the network status messages in Section 3. A particular 911 or 912 status may be generated by several different Agilis 91x MDS statuses. On-site Action - contains information for the operator at the terminal to correct the problem. The column indicates if you need to contact your service technician.

With some statuses, an English-language message prints on the journal printer to help the operator. Refer to Appendix D for a cross-reference to help you locate the descriptions in Section 3 for the English-language message that prints on the journal printer. An English-language message may be generated by any one of several different Agilis 91x MDS statuses.

3.1 AH01 (After Hour Depository Status Messages) This section describes the After Hour depository fault status messages. The device type and number as it appears in the status message is AH01. Refer to Table 3-1 for the After Hour depository fault status messages. Table 3-1 AH01 - After Hour Depository Status Message Descriptions http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

5/107

21/10/2014


Status Message

Description

Sent to DAL/Journal

Network Action

On-site Action

AH01:23:00:00 Consumer timeout

No/No

N/A

None

AH01:24:00:00 Consumer cancel

No/No

N/A

None

AH01:38:nn:nn Communications problem

No/No

N/A

A service investigation is required

AH01:3A:41:40 Failure to unlock

No/No

Remove AHD from the transaction selection choices.

A service investigation is required

AH01:3E:00:00 Network fault - an attempt to operate an AHD with the device configured to off

No/No

N/A

None

AH01:3E:42:40 Failure to lock

No/No

Remove AHD from the transaction selection choices.

Check to see if the door is jammed. If it is not, contact service.

N/A

None. If frequent, contact service.

[1]

AH01:3F:48:40 Device timeout - door unlocked but No/No not opened. (Sent to the network as :23:00:00.) [1] nn

can be any number

3.2 AL01 (Alarm Status Messages) This section describes the alarm fault status messages. The device type and number as it appears in the status message is AL01. Refer to Table 3-2 for the alarm fault status messages.

Status Message

Table 3-2 AL01 - Alarm Status Message Descriptions Sent to Description Journal Network Action

On-site Action

AL01:3F:00:00 Ambush detector ON, burglary sensor OFF, safe door OPEN

Yes

Take an appropriate security action.

No action is required.

AL01:3F:01:00 Ambush detector ON, burglary sensor OFF, safe door CLOSED

Yes



AL01:3F:40:00 Ambush detector ON, burglary sensor ON, safe door OPEN

Yes



AL01:3F:41:00 Ambush detector ON, burglary sensor ON, safe door CLOSED

Yes



AL01:3F:80:00 Ambush detector OFF, burglary sensor OFF, safe door OPEN

Yes



AL01:3F:81:00 Ambush detector OFF, burglary sensor OFF, safe door CLOSED

Yes



AL01:3F:C0:00 Ambush detector OFF, burglary sensor ON, safe door OPEN

Yes



AL01:3F:C1:00 Ambush detector OFF, burglary sensor ON, safe door CLOSED

Yes



3.3 CI01 (Bulk Note Acceptor Currency Acceptor Messages) This section describes the BNA currency acceptor fault status messages. The device type and number as it appears in the status message is CI01. Refer to Table 3-3 for the BNA currency acceptor fault status messages.

Status Message \ Device Status CI01:00:00:00

Table 3-3 CI01 - BNA Currency Acceptor Status Message Descriptions Sent to DAL \ Description Journal Network Action This is a status received from the Yes /


N/A

On-site Action N/A 6/107

21/10/2014


Yes device indicating that a self-test was performed and no errors were found. CI01:23:00:00

Consumer Timeout

No / Yes

Send a function command to exit None the consumer request state and continue or send another function command to operate the currency acceptor again

CI01:24:00:00

Consumer cancel

No / Yes

Send a function command to exit None the Consumer Request state and continue.

CI01:30:35:30

Command reject

Yes / Yes

N/A

CI01:38:00:00

Communications problem with device.

Yes / Yes

Remove currency acceptor from Service the the transaction selection choices. currency acceptor.

CI01:38:40:00

The device application is not responding.

Yes / Yes


CI01:3A:33:41

The shutter would not open.

Yes / Yes


CI01:3A:39:39

Hardware error.

Yes / Yes


CI01:3C:33:45

The shutter would not close.

Yes / Yes


Yes / Yes

Continue with the transaction processing.

Replace with an empty cassette. The cassette counts must be reset in Supply mode.

CI01:3D:37:mm Deposit cassette is full. The Yes / operation completed successfully. Yes Where mm has the following bit value:


Replace with an empty cassette. The cassette counts must be reset in Supply mode.

Remove currency acceptor from the transaction selection

Replace with an empty cassette(s). The cassette counts must be reset in Supply mode

CI01:3D:26:mm Deposit cassette is almost full. The operation completed successfully. Where mm has the following bit value: 1 Cassette 0

Ensure proper selection and configuration of the device.

2 Cassette 1 4 Cassette 2 8 Cassette 3 16 Cassette 4

1 Cassette 0 2 Cassette 1 4 Cassette 2 8 Cassette 3 16 Cassette 4 CI01:3D:50:00

Reject cassette(s) are full at the Yes / end of the operation. The Yes operation completed successfully.


7/107

21/10/2014


CI01:3D:51:00

Reject cassette(s) are full at the beginning of the operation. The operation was not started.

Yes / Yes

Remove currency acceptor from the transaction selection

Replace with an empty cassette(s). The cassette counts must be reset in Supply mode

CI01:3D:60:00

Reject cassette is absent.

Yes / Yes

Remove currency acceptor from the transaction selection.

Insert the cassette.

CI01:3E:40:34

The operation could not be performed due to improper network command data. There is a state or function format error.

Yes / Yes

Take the currency acceptor out of No on-site action service. Correct the function required. command or the state data.

CI01:3E:40:35

Error in loading buffers for the cash deposit.

Yes / Yes

Take the currency acceptor out of No on-site action service. Correct the function required. command or the state data.

CI01:3F:31:30

Cash retracted during the close state

Yes / Yes

Continue with the transaction processing

No on-site action required

CI01:3F:31:31

There is no cash in the cash pocket when the cash verify operation was attempted.

Yes / Yes


No on-site action required.

CI01:3F:31:32

There is no cash in escrow when the cash return operation was attempted.

Yes / Yes



CI01:3F:31:33

There were one or more bills rejected during the cash verification

Yes / Yes

Prompt the customer to remove the rejects.


CI01:3F:31:34

The currency acceptor escrow Yes / stacker limit was exceeded. The Yes consumer inserted more bills than the device could escrow.

Prompt the customer to remove the excess deposit stack and continue processing.


CI01:3F:31:35

There is a cash position error in the cash pocket or cash pocket stack limit has been exceeded..

Yes / Yes

Prompt the customer to remove No on-site action the deposit stack and make sure required. the note edges are even and to remove any excess deposit stack and re-insert.

CI01:3F:31:37

All bills were rejected during the cash verification

Yes / Yes

Prompt the customer to remove the rejects.

CI01:3F:31:38

Bill reject limit reached, no bills verified

Yes / Yes

Prompt the customer to remove No on-site action the rejects and any remaining bills required. that were not processed.

CI01:3F:31:39

Bill reject limit reached, some bills Yes / verified Yes

Prompt the customer to remove No on-site action the rejects and any remaining bills required. that were not processed.

CI01:3F:32:30

Cash retracted during a clear cash Yes / operation Yes



CI01:3F:32:31

Cash retracted during a deposit operation

Yes / Yes



CI01:3F:36:35

Cassette shuffle

No /Yes Take the currency acceptor out of Look for unseated service. Ask the terminal for a or swapped hardware configuration message cassettes. and try the cash deposit again.

CI01:3F:40:31

The device is not in the proper mode to accept the network command requested. The command is out of sequence or the CAS mode is active.

Yes / Yes


Make sure that the currency acceptor operations are being commanded in the proper order.



8/107

21/10/2014


CI01:3F:40:40

An unexpected or unknown fault was returned from the currency acceptor.

Yes / Yes

If repetitive, take the currency acceptor out of service.


3.4 CN01 (Coin Dispenser Status Messages) This section describes the coin dispenser fault status messages. The device type and number as it appears in the status message is CN01. Refer to Table 3-4 for the coin dispenser status messages. The following example is a typical coin dispenser fault as it is printed on the journal printer:

001CN01:3D:31:39

:31:41:30 :34:32:42

:30:30:33

:44:30:30

:34:40:30 :30

The first field of three hex bytes is the fault as reported by the dispenser, in this case 3D 31 39. The remaining data is grouped into four byte fields (every other four-byte field is bold) that indicate the hopper position, denomination, and how many coins were dispensed from that hopper. In this case, the remaining data indicates that position 1 contains a hopper with denomination A and that four coins were dispensed from it. Position 2 contains a hopper with denomination B, position 3 contains a hopper with denomination D, and position 4 contains no hopper (denomination @). No coins were dispensed from positions 2, 3, or 4. Table 3-4 CN01 - Coin Dispenser Status Message Descriptions Sent to DAL/ Status Message and Description Journal Network Action On-site Action

Next State

CN01:00:00:00

N/A

Yes/ Yes

This is a status received from the device indicating that a self-test was performed and no errors were found. CN01:2D:0m:0n Yes/ Yes The supply is low. Where m has the following bit value: 1 Denomination A

N/A

N/A

Schedule Replace with a full cassette. Enter the Supply N/A replenishment of mode and perform the test dispense. the coins and continue dispensing

2 Denomination B 4 Denomination C 8 Denomination D Where n has the following bit value: 1 Denomination E 2 Denomination F 4 Denomination G 8 Denomination H http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

9/107

21/10/2014


The bit being set means supply is low. For example,:2D:04:00 indicates that denomination C is low on coins. CN01:38:nn:nn (nn can be any number)

Yes/ Yes

Do not authorize Check the PosiDoc connector for proper N/A any more coin mating. Check that the happy light on the dispenses until device is blinking (indicating that the device is the unit is alive). Check the cables that connect the repaired. Exit the dispenser to the PosiDoc connector and those current that connect the PosiDoc connector to the transaction and terminal wiring harness assembly. Run either direct the CSSEDT to see if the Coin Dispenser terminal to a connection is defined. Run a trace (using close state or comm subsystem) and check that the device ask the is being polled. If no problems can be found, consumer if he or replace the dispenser. If the terminal still she wants reports this comm fault, call service. another transaction.

Yes/ Yes

Don't authorize Replace the Coin Dispenser CCA. any more coin dispenses until the unit is repaired. Exit the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction.

N/A

Yes/ Yes

Don't authorize TBD any more coin dispenses until the unit is repaired. Exit the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction.

N/A

Yes/ Yes

Don't authorize TBD any more coin dispenses until the unit is repaired. Exit the current transaction and either direct the terminal to a close state or ask the

N/A

Communications problem

CN01:3A:36:33 RAM error

CN01:3B:30:31 Unsolicited coin from hopper 1



10/107

21/10/2014


consumer if he or she wants another transaction. CN01:3B:30:33

Yes/ Yes


N/A

Yes/ Yes


N/A

Yes/ Yes

Refrain from Check the hopper. If it is empty, refill it and N/A dispensing from indicate your activity by updating the this hopper until appropriate bin counter. If the hopper is it is repaired or jammed, clear the jam and perform a coin refilled. dispense from diagnostics or with a teller card to make sure it works.

Unsolicited coin from hopper 3


CN01:3D:31:37

Feed failure in hopper 1. This fault can occur during normal transaction processing as the hoppers run out of coins. If a low condition was reported prior to receiving this fault, it is most likely an out condition. If the low status was not reported recently, then it is either an indication of a coin jam or improper settings of the coin counters. CN01:3D:31:38 Yes/ Yes Feed failure in hopper 2. This fault can occur during normal transaction processing as the hoppers run out of coins. If a low condition was reported prior to receiving this fault, it is most likely an out condition. If the low status was not reported recently, then it is either an indication of a coin jam or improper settings of the coin counters.



11/107

21/10/2014


CN01:3D:31:39

Yes/ Yes


Yes/ Yes


Yes/ Yes

The network Make sure that the installed coin hoppers are requested a those required by the network. denomination that is not present in the Coin Dispenser. Remix and retry.

Yes/ Yes

Don't authorize Make sure the Coin Dispenser is fully docked. N/A any more coin If the dispenser is docked and still reports this dispenses until error, check the docking sensor. unit is docked. Exit the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction.

Yes/ Yes

N/A

Feed failure in hopper 3. This fault can occur during normal transaction processing as the hoppers run out of coins. If a low condition was reported prior to receiving this fault, it is most likely an out condition. If the low status was not reported recently, then it is either an indication of a coin jam or improper settings of the coin counters. CN01:3D:32:30 Feed failure in hopper 4. This fault can occur during normal transaction processing as the hoppers run out of coins. If a low condition was reported prior to receiving this fault, it is most likely an out condition. If the low status was not reported recently, then it is either an indication of a coin jam or improper settings of the coin counters. CN01:3D:33:35 Network error (invalid coin amount field)

CN01:3D:40:4B Coin Dispenser is not docked.

CN01:3E:00:00 If this status is received during an op-commanded self-test, the device was specifically requested to do a self-test but was not enabled or present. CN01:3E:00:01 Coin Dispenser is disabled in device properties.

Yes/Yes Don't authorize any more coin dispenses. Exit the current transaction and


N/A

N/A

N/A

Make sure the Coin Dispenser is installed N/A correctly. This could be the result of improper cabling, a defective Coin Dispenser PWB, or failure to install the dispenser in the first place. 12/107

21/10/2014


CN01:3E:01:01 Coin Dispenser not docked.

CN01:3E:32:35

either direct the terminal to a close state or ask the consumer if he or she wants another transaction. Yes/Yes Don't authorize Make sure the Coin Dispenser is fully docked. N/A any more coin If the dispenser is docked and still reports this dispenses until error, check the docking sensor. the unit is docked. Exit the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction. Yes/Yes Refrain from dispensing from this hopper until it is repaired.

Check for a coin jam in hopper 1. If no jam is found, check the coin s ensor on this hopper.

N/A

Yes/Yes Refrain from dispensing from this hopper until it is repaired.


N/A



N/A



N/A

Yes/Yes Refrain from dispensing any A jam between picker and delivery. more coins until None of the dispensed coins were the dispenser is seen at the chute sensor. If at repaired. least one coin gets to the sensor, the fault will not be reported. CN01:3E:36:30 Yes/Yes Refrain from dispensing any Jam at chute sensor before more coins until dispense. No coins are dispensed. the dispenser is A possible jam scenario is that jam repaired. occurs during a dispense but at least one coin gets passed the chute sensor. No faults will be reported on that dispense. On the next coin dispense, however, the sensor will be checked prior to delivery and the 3E:36:30 fault will be reported immediately with no

Check for a coin jam between picker and delivery sensor. If no jam is found, check the delivery sensor.

N/A

Check for a coin jam at the chute sensor.

N/A

Jam failure in hopper 1 CN01:3E:32:36 Jam failure in hopper 2 CN01:3E:32:37 Jam failure in hopper 3 CN01:3E:32:38 Jam failure in hopper 4 CN01:3E:33:33


13/107

21/10/2014


coins dispensed. CN01:3E:38:41

Yes/Yes Refrain from dispensing from Hopper 1 coin sensor is stuck this hopper until clear/blocked. A coin is jammed or it is repaired. a sensor has failed. CN01:3E:38:42 Yes/Yes Refrain from dispensing from Hopper 2 coin sensor is stuck this hopper until clear/blocked. A coin is jammed or it is repaired. a sensor has failed. CN01:3E:38:43 Yes/Yes Refrain from dispensing from Hopper 3 coin sensor is stuck this hopper until clear/blocked. A coin is jammed or it is repaired. a sensor has failed. CN01:3E:38:44 Yes/Yes Refrain from dispensing from Hopper 4 coin sensor is stuck this hopper until clear/blocked. A coin is jammed or it is repaired. a sensor has failed.


N/A


N/A


N/A


N/A

3.5 CNS (State/Function Processing) If an error occurs during the processing of a state (probably an invalid next state number), an error message is printed on the journal printer. This message is structured in the following format:

CNS:nn:mm Where mm nn is the state number in hexadecimal (the indication shown on the printer is byte-reversed). For example, if the message is CNS:1A:00, an error occurred trying to process state number 26 (decimal). CNS:03:01 indicates an error on state number 259 (decimal). Refer to Table A-1 in Appendix A for help in converting hexadecimal numbers to decimal. If the conversion of mm nn to its decimal equivalent yields a number greater than 999, then the state number falls in the range A00 through ZZZ. Refer to the paragraphs at the end of this section to determine the actual state number in this range. A common error message received is CNS:00:00. This message indicates that a GO In-service command was received by the terminal and the terminal did not have a state 000 configured. When a State ESC process occurs, the LUNO number is included in the Power Fail message. The 911/912 status is in the following format:

XXX,1/XXX,1 State Numbers from A00 through ZZZ If the conversion of mm nn to its decimal equivalent yields a number greater than 999, then the state number falls in the range A00 through ZZZ. State numbers in that range can be obtained using the following procedure, where RawNumber is the decimal equivalent of mm nn. To derive the first digit of the state number, evaluate the following expression:

( Integer (( RawNumber - 1000 ) / 1296 )) + 65 The result is the ASCII code for the first digit. To derive the second digit of the state number, use the remainder from the preceding division by 1296 to evaluate the following expression:

( Integer ( Remainder / 36 )) + X http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

14/107

21/10/2014


If (Integer(Remainder/36)) is less than 10, use the value 48 for X. If (Integer(Remainder/36)) is equal to or greater than 10, use the value 55 for X. The third digit is the remainder from the preceding division by 36, adjusted to an ASCII code as described for the second digit:

Remainder + X EXAMPLE As an example, assume that the raw decimal form of the state number is 1621 (RawNumber). For the first digit, the calculation is as follows:

( Integer (( 1621 - 1000 ) / 1296 )) + 65 = ( Integer ( 621 / 1296 )) + 65 = 0 + 65 = 65 Decimal 65 is the ASCII code for the letter A, so the first digit of the state number is A. The remainder from the division by 1296 is 621. Therefore, for the second digit, the calculation is as follows:

( Integer ( 621 / 36 )) + X = 17 + X = 17 + 55 = 72 Decimal 72 is the ASCII code for the letter H, so the second digit of the state number is H. The remainder from the division by 36 is 9. Therefore, for the third digit, the calculation is as follows:

9 + X = 9 + 48 = 57 Decimal 57 is the ASCII code for the number 9, so the third digit is 9. Therefore, the actual state number is AH9.

3.6 CR01 (Card Reader Status Messages) This section describes the card reader fault status messages. The device type and number as it appears in the status message is CR01. Refer to Table 3-5 for the card reader fault status messages.

Status Message

Table 3-5 CR01 - Card Reader Status Message Descriptions Sent to Description Journal Network Action On-site Action

CR01:00:00:00 The card reader performed a Yes self-test, and no errors occurred.

Not applicable


CR01:23:00:00 Consumer timeout. The card Yes was moved to the return position but was not removed within the allotted time.

Retain the card.


CR01:38:00:00 The card reader is unavailable or inoperative.

Yes

Retry the operation.

If this problem persists, a service investigation is required.

Yes

If this problem persists, cease card reader operation. If appropriate, take the terminal out of service. Initiate a service investigation. Not applicable Service investigation

CR01:38:62:40 Self-test open failure. The card reader is not available.

CR01:3C:00:00 1) Read operation is No incomplete due to timeout or cancellation. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

If this problem If this problem persists, a service persists, discontinue investigation is required. card reader operation. 15/107

21/10/2014


If appropriate, take the terminal out of service. Initiate a service investigation.

2) Eject or retain command was rejected due to unsupported data type. CR01:3E:00:00 Network error. The card reader was directed to perform an operation that it does not have the capability to perform.

1) Yes, if due to function command processing. 2) No, if due to state processing.

CR01:3E:00:40 The operation cannot be performed due to improper network data. There is a format fault in state data or in Function Command message data.

Yes

CR01:3E:40:42 Unable to write data to track Yes 3 (state processing). The write fault limit in the device propertieshas been exceeded.

CR01:3E:40:53 Unable to write data to track Yes 1 (state processing). The write fault limit in the device properties has been exceeded.

CR01:3E:40:55 Unable to write data to track Yes 2 (state processing). The write fault limit in the device properties has been exceeded.

CR01:3E:42:40 The read conditions cannot be satisfied (state processing). The read fault limit in the device properties

Yes


1) Check the Function 1) No action is required. Command message 2) Not applicable for correctness. 2) Check state processing for correctness.

Correct the state data No action is required. or Function Command message data.

Return the card and display a screen informing the consumer that the card might no longer be usable. If this problem persists, remove the terminal from service and initiate the on-site action. Return the card and display a screen informing the consumer that the card might no longer be usable. If this problem persists, remove the terminal from service and initiate the on-site action. Return the card and display a screen informing the consumer that the card might no longer be usable. If this problem persists, remove the terminal from service and initiate the on-site action. Return the card and exit from the Transaction Request state.

If this problem persists, clean the read head with a head-cleaning card. If the problem persists, a service investigation is required.



If this problem persists, clean the read head with a head-cleaning card. If the problem persists, a service investigation is required. 16/107

21/10/2014


DIT has been exceeded.

If this problem persists, remove the terminal from service and initiate the on-site action.

CR01:3E:44:40 The card retain bin is full. Yes The card reader cannot retain the card. It might be possible to return the card.

If card retain capability Clear the jam. is required for terminal operation, remove the terminal from service and initiate the on-site action.

CR01:3E:48:40 The card is jammed in the Yes card reader. The card cannot be returned to the consumer. It might be possible to retain the card.

Attempt to clear the Clear the jam. jam by retaining the card. If successful, display a screen to notify the consumer that the card was retained, then continue with normal operation.

CR01:3E:58:60 The card is jammed in the card reader.

Yes

CR01:3E:60:48 A card was partially inserted, Yes rather than fully inserted (state processing). The partial insertion was repeated several times, or the card stayed partially inserted for a length of time. CR01:3F:40:41 An unsolicited card retain has occurred, due to one of the following situations.

Yes

If unsuccessful, remove the terminal from service and initiate the on-site action. Attempt to clear the Clear the jam. jam by retaining the card. If successful, display a screen to notify the consumer that the card was retained, then continue with normal operation. If unsuccessful, remove the terminal from service and initiate the on-site action. Remove the terminal from service and initiate the on-site action.

Clear the card (or other object) from the card reader.

Not applicable

If this problem persists, a service investigation is required.

Return the card and

If this problem persists, clean the

1) The card was present in the card reader on powerup. 2) The card was moved to the return position, but the consumer did not take the card within the allotted time. CR01:3F:40:42 Unable to write data to track Yes http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

17/107

21/10/2014


3 (function command processing).

display a screen informing the consumer that the card might no longer be usable.

read head with a head-cleaning card. If the problem persists, a service investigation is required.

If this problem persists, remove the terminal from service and initiate the on-site action. CR01:3F:40:53 Unable to write data to track Yes 1 (function command processing).

Return the card and display a screen informing the consumer that the card might no longer be usable.


If this problem persists, remove the terminal from service and initiate the on-site action. CR01:3F:40:55 Unable to write data to track Yes 2 (function command processing).

CR01:3F:40:60 The card was not retained. No The card was removed from the card reader, the card was held by the user, or the card is jammed in the card reader. CR01:3F:42:40 The read conditions cannot be satisfied (function command processing).

Yes

CR01:3F:48:40 The card is jammed in the Yes card reader. The card cannot be returned to the consumer. It might be possible to retain the card.

Return the card and display a screen informing the consumer that the card might no longer be usable.


If this problem persists, remove the terminal from service and initiate the on-site action. Discontinue the Check for a jammed card. transaction.

Return the card and exit from the Transaction Request state.

If this problem persists, check for and remove the jam. If no jam is found, use a test card to verify the read operation. If bad results occur, clean the head with a head-cleaning card. If the problem persists, a service investigation is required.

If this problem persists, remove the terminal from service and initiate the on-site action. Attempt to clear the Clear the jam. jam by retaining the card. If successful, display a screen to notify the consumer that the card was retained, then continue with normal operation. If unsuccessful,


18/107

21/10/2014


remove the terminal from service and initiate the on-site action. CR01:3F:60:48 A card was partially inserted, Yes rather than fully inserted (function c ommand processing). The partial insertion was repeated several times, or the card stayed partially inserted for a length of time.

If this problem Clear the card (or other object) persists, remove the from the card reader. terminal from service and initiate the on-site action.

3.7 DI01 or D901 (Cash Dispenser Status Messages) This section describes the cash dispenser fault status messages. The device type and number as it appears in the status message is DI01 or D901. Refer to Table 3-6 for the cash dispenser fault status messages. NOTE This section provides the status messages for the dispense function only. For fault status messages for the cash presenter functions (present, dump, and restore), refer to Section 3.9. If the cash dispenser status is unsolicited, the device type appears as DI instead of D9 and is a single line format as described in Section 2.1.1. Cash Dispenser Status Format For systems operating in Diebold 912 Native mode, cash dispenser status is printed on the journal printer in the single-line format described in Section 2.1.1. For systems operating in Diebold 911 Native mode, the cash dispenser status is printed on the journal printer in six fields. An example printout would appear in the following format:

001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00 :00:00 These fields are defined as follows (the field that is being described is bold): Field #1 (shown below in bold) is three bytes long and indicates the status of the withdrawal area before the dispense (if 00:00:00, no fault).

001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00 :00:00 Field #2 (shown below in bold) is three bytes long and indicates the high-side cash dispenser status (if: 21:00:00, no fault).

001D901:00:00:00 :2D:08:00

:0F:21:00 :00:07:00 :00:00

Field #3 (shown below in bold) is one byte long and indicates the number (in hexadecimal) of high-side bills dispensed. Also, refer to Table A-1. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

19/107

21/10/2014


001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00 :00:00 Field #4 (shown below in bold) is three bytes long and indicates the low-side cash dispenser status (if: 21:00:00, no fault).

001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00 :00:00 Field #5 (shown below in bold) is one byte long and indicates the number (in hexadecimal) of low-side bills dispensed. Also, refer to Table A-1.

001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00 :00:00 Field #6 (shown below in bold) is three bytes long and indicates the status of the withdrawal area after the dispense (if :00:00:00, no fault).

001D901:00:00:00 :2D:08:00 :0F:21:00 :00:07:00

:00:00

The dispense status for the cash dispenser may have a device type and device number of DI01 or D901. Refer to the status messages in Table 3-6 for either device type and number. Cassette Tamper Feature The Cassette Tamper feature allows the terminal to generate a status message when a cash dispenser cassette is removed or inserted. This includes all cash cassettes and the divert cassette. By default, a message is not sent to the network when this status is generated. To enable this feature, select Cassette Tamper Enable in the Dispenser device properties. Refer to the Agilis 91x XV Maintenance Manual (TP-820744-001J). The format of the status is DI01:61:xx:00 (this is an example status). xx is the second hexadecimal byte of the status and is defined as follows: Bit 7 Not used

Always set to 0

Bit 6 Feed module 6 0 cassette present, 1 no cassette Bit 5 Feed module 5 0 cassette present, 1 no cassette Bit 4 Feed module 4 0 cassette present, 1 no cassette Bit 3 Feed module 3 0 cassette present, 1 no cassette Bit 2 Feed module 2 0 cassette present, 1 no cassette Bit 1 Feed module 1 0 cassette present, 1 no cassette Bit 0 Reject cassette 0 cassette present, 1 no cassette Perform the following functions to generate a network status message when the cassette tamper fault occurs: Activate status reporting in Write Command III. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

20/107

21/10/2014


Refer to the Agilis 91x (XV) and Agilis 91x for Opteva Terminal Programming Manual (TP-820740-001C ) Select unsolicited status message reporting in System Control 2 DIT, option 5. Refer to the Agilis 91x XV Maintenance Manual (TP-820744-001J). Enabling this network status affects other device-related solicited and unsolicited statuses because of the global nature of these items. The network status includes the following information: Device ID - DI01 MDS status - 000DI01:61:xx:00 The denomination IDs of each cassette position

Status Message

Table 3-6 DI01 or D901 - Multi-media Dispenser Status Message Descriptions Sent to Description DAL/Journal Network Action On-site Action

DI01:00:00:00 This is a status received from the device indicating that a self-test was performed and no errors were found.

Yes/Yes

N/A

DI01:22:00:00 Network error.

No/Yes

Possible problems N/A are that the network requested more than 50 bills or the network requested 0 bills.

DI01:2D:0m:0n Supply is low. Where m has the following bit value:

Yes/Yes

Schedule the replenishment of the notes and continue dispensing.

Replace with a full cassette. Enter Supply mode and perform the test dispense.

Yes/No

N/A

Check the cassette codes and replace with the correct cassettes. Verify that the network has requested valid denominations.

1 Denomination A 2 Denomination B

N/A

4 Denomination C 8 Denomination D Where n has the following bit value: 1 Denomination E 2 Denomination F 4 Denomination G 8 Denomination H

DI01:30:yy:xx

The bit being set means the supply is low. For example, 2D:04:00 indicates that denomination C is low on notes. A dispenser command reject. The command rejected is yy and the reason code is xx. This status is converted to status :3D:33:35 before being sent to the network. See DI01:3D:33:35 for further status processing. No notes are dispensed. The valid commands yy are: 30 - reset device 31 - idle device


21/107

21/10/2014


34 - return device configuration data 37 - return device CRCs 41 - purge mechanism 42 - dispense 4A - purge notes The valid reason codes xx are: 30 - invalid command 31 - command received out of sequence 32 - buffer overflow 33 - device ID incorrect 40 - denomination error 41 - dispense data invalid DI01:30:yy:xx

A dispense command reject while in the No/No diagnostics mode. The command rejected is yy and the reason code is xx. The valid commands yy are:

None. Only occurs in the Supply mode or diagnostics as seen on the CRT display.

Make sure the cassettes are installed and properly seated.

43 - test dispense 47 - operate motor 48 - operate diverter 53 - adjust double detect 54 - last dispense data dump The valid reason codes xx are: 30 - invalid command 31 - command received out of sequence 41 - dispense data invalid DI01:38:00:00 ExpressBus communications problem. Notes may or may not have been dispensed.

Yes/Yes

Remove dispense Service the from the transaction dispenser. selection choices.

DI01:38:39:31 The dispenser returned garbled status. No retry is attempted.

No/Yes

Remove dispense If consistent, from the transaction service the selection choices. dispenser.

DI01:39:00:00 Dispenser shutdown (broken). This fault is No/Yes caused by a previous fault occurrence (probably a jam not being physically cleared at the ATM and not entering Supply mode and running a test dispense.)


Remove dispense Clear the jam if from the transaction there is one selection choices. and run the test dispense. Service the dispenser if necessary.

22/107

21/10/2014


DI01:39:00:01 The drawer sensor is blocked prior to more than No/Yes [1] three consecutive dispenses.

Remove dispense from the transaction selection choices. (Subsequent dispense attempts without going into the Supply mode to clear the fault will result in this status being repeated.)

Go into the Supply mode, clear the material from the withdrawal area, and exit the Supply mode.

DI01:39:00:03 The drawer sensor is not blocked after three [1] consecutive dispenses. The status is first reported prior to the fourth dispense attempt. (This status is repeated in Section 3.12.)

No/Yes

Remove dispense from the transaction selection choices. (Subsequent dispense attempts without going into the Supply mode to clear fault will result in this status being repeated.)

Go into the Supply mode, check the withdrawal area for a possible money catch device, and exit the Supply mode.

DI01:39:00:05 The drawer sensor is blocked after a power fail [1] or the sensor is clear after previous but blocked before the current dispense.

No/ Yes


Go into the Supply mode, check the withdrawal area for cash or foreign material, and exit the Supply mode.

DI01:39:00:07 The drawer sensor is blocked leaving the Supply No/ Yes [1] mode or fascia diagnostic routine.


Go into the Supply mode, check the withdrawal area for cash or foreign material, and exit the Supply mode.

DI01:39:36:33 RAM error. No retry is attempted. This status No/ Yes was converted from dispenser status :3A:36:33.


DI01:3A:30:31 An unsolicited note from feed module 1. The No/ Yes retry option is disabled or the dispense recovery preceding the retry failed. This status was converted from dispenser status :3B:30:31.






DI01:3A:30:34 An unsolicited note from feed module 4. The No/Yes retry option is disabled or the dispense recovery preceding the retry failed for the retry attempt.



23/107

21/10/2014


This status was converted from dispenser status :3B:30:34. DI01:3A:33:37 The diverter does not go to reject during the No/Yes dispense operation. The retry option is disabled or the dispense recovery preceding the retry failed. This status was converted from dispenser status :3B:33:37.


DI01:3A:35:39 A timing wheel error. The retry option is disabled No/Yes or the dispense recovery preceding the retry failed. This status was converted from either of the following dispenser statuses :3B:35:39 or 3B:38:34.


DI01:3A:36:30 The counting sensor is blocked. This status was No/Yes converted from dispenser status :3E:36:30. The possible dispense operation completion is as follows:

Remove dispense Check for from the transaction debris near the selection choices. exit sensor. If consistent, service the dispenser.

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. DI01:3A:36:33 A RAM error as reported by the dispenser. No retry is attempted. This status is converted to status :39:36:33 before being sent to the network.

Yes/No

N/A

Service the dispenser.

DI01:3A:36:37 The diverter does not energize prior to a dispense operation. The retry option is disabled or the purge before the retry failed. No retry is attempted. This status was converted from dispenser status :3B:36:37

No/Yes


DI01:3A:38:31 A dispense timeout as reported by the No/Yes dispenser. No retry is attempted. This status was converted from dispenser status :3C:38:31.

Remove dispense If consistent, from the transaction service the selection choices. dispenser.

DI01:3A:39:38 No dispense due to cash pocket obstruction.

N/A

Remove the obstruction.

DI01:3B:30:31 An unsolicited note from feed module 1 as Yes/No reported by the dispenser. This status is converted before being sent to the network to either :3F:30:31 if the retry is attempted but resulted in the same fault, or :3A:30:31 if otherwise. See DI01:3F:30:31 or DI01:3A:30:31 for further status processing.

N/A

If consistent, service the dispenser.

DI01:3B:30:32 An unsolicited note from feed module 2 as Yes/No reported by the dispenser. This status is converted before being sent to the network to either :3F:30:32 if the retry is attempted but resulted in the same fault, or:3A:30:32 if otherwise. See DI01:3F:30:32 or DI01:3A:30:32 for further status processing.

N/A


DI01:3B:30:33 An unsolicited note from feed module 3 as Yes/No reported by the dispenser. This status is converted before being sent to the network to either :3F:30:33 if the retry is attempted but resulted in the same fault, or :3A:30:33 if otherwise. See DI01:3F:30:33 or DI01:3A:30:33 for further status processing.

N/A



Yes/Yes

24/107

21/10/2014


DI01:3B:30:34 An unsolicited note from feed module 4 as Yes/No reported by the dispenser. This status is converted before being sent to the network to either:3F:30:34 if the retry is attempted but resulted in the same fault, or:3A:30:34 if otherwise. See DI01:3F:30:34 or DI01:3A:30:34 for further status processing. DI01:3B:33:33 A jam between double detect and exit. The retry No/Yes is attempted but resulted in the same fault. This status was converted from dispenser status :3E:33:33

N/A

DI01:3B:33:37 The diverter does not go to reject during a dispense operation. The possible dispense operation completion is as follows:

1) Yes/No

1) N/A

2) Yes/Yes

2) Remove dispense from the transaction selection choices.

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. This status is converted to status :3A:33:37 before being sent to the network. See DI01:3A:33:37 for further status processing.


Remove dispense Clear the bill from the transaction jam. If selection choices. consistent, service the dispenser. 1) If consistent, service the dispenser. 2) If consistent, service the dispenser.

2) The retry is attempted but resulted in the same fault. DI01:3B:35:38 Too many notes are dispensed as reported by Yes/No the dispenser. This status is converted to :3F:35:38 before being sent to the network. See DI01:3F:35:38 for further status processing.

N/A


DI01:3B:35:39 A timing wheel or dispense purge error. If there is no corresponding DAL status, then this network status was converted from dispenser :3B:38:34 status. The possible dispense operation completion is as follows:

1)Yes/ No

1) N/A

1) Service the dispenser.

2)Yes/ Yes


3) No/ Yes

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. This status is converted to status :3A:35:39 before being sent to the network. See DI01:3A:35:39 for further status processing.


2) Service the dispenser. 3) Service the dispenser.

2) The retry is attempted but resulted in the same fault. c) The retry is attempted but resulted in the same fault. The fault is originally due to dispense purge error:3B:38:34. DI01:3B:36:37 The diverter does not energize prior to the dispense operation. The possible dispense operation completion is as follows:

1) Yes/ No

1) N/A

2) Yes/ Yes


1) The retry option is disabled or the dispense recovery preceding the retry failed. No recovery is attempted. This status is converted to status :3A:36:37 before being sent to the network. See DI01:3A:36:37 for further status processing.

1) Service the dispenser. 2) Service the dispenser.

2) The retry is attempted but resulted in the same fault. DI01:3B:37:32 A purge failure. No retry is attempted. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

Yes/ Yes

Remove dispense Clear the bill from the transaction jam. If 25/107

21/10/2014


selection choices.

DI01:3B:38:31 A dispense timeout. The retry is attempted but resulted in the same fault. This status was converted from dispenser status :3C:38:31.

No/ Yes

Remove denomination from the transaction selection.

consistent, service the dispenser. If consistent, service the dispenser.

DI01:3B:38:34 A purge error following a dispense as reported Yes/ No by the dispenser. This status is converted before being sent to the network to either :3B:35:39 if the retry is attempted but resulted in the same fault, or:3A:35:39 if otherwise. See DI01:3B:35:39 or DI01:3A:35:39 for further status processing.

N/A


DI01:3C:38:31 A dispense timeout as reported by the Yes/No dispenser. This status is converted to either:3B:38:31 if the retry is attempted but resulted in the same fault or:3A:38:31 otherwise. See DI01:3A:38:31 or DI01:3B:38:31 for further status processing.

N/A

Check for poor quality money. If consistent, service the dispenser.

DI01:3D:0m:0n The supply is out. Where m has the following bit Yes/Yes value:

Remove the denomination from the transaction selection.

Replace with a full cassette. Enter the Supply mode and perform the test dispense.

N/A

Check for an empty cassette or replace the cassette.

DI01:3D:31:38 A feed failure from feed module 2 as reported by Yes/No the dispenser.

N/A



N/A


1 Denomination A 2 Denomination B 4 Denomination C 8 Denomination D Where n has the following bit value: 1 Denomination E 2 Denomination F 4 Denomination G 8 Denomination H The bit set means the supply is out. For example, :3D:08:00 indicates that denomination D is out of notes. DI01:3D:31:37 A feed failure from feed module 1 as reported by Yes/No the dispenser.


26/107

21/10/2014



DI01:3D:33:35 A command reject while the terminal is inservice due to a command reject sent from the dispenser. This could be the result of a network dispense request of a denomination that is not present. No retry is attempted. This status was converted from any of the dispense statuses :30:yy:xx. See DI01:30:yy:xx for further status processing.

Yes/Yes

N/A

Check for an empty cassette or replace the cassette. Remove the Replace with denomination from the correct the transaction cassette or the selection choices cassette is (911). missing. Check the Ask the terminal for cassette a hardware codes. configuration message and try the dispense again (912).

DI01:3D:33:36 An unidentified cassette code as reported by the Yes/No dispenser. This status is converted to status :3F:33:36 before being sent to the network. See DI01:3F:33:36 for further status processing.

N/A

Replace with the correct cassette or the cassette is missing. Check the cassette codes.

DI01:3D:33:41 The feed module 1 notes are thicker than the key data as reported by the dispenser. This status is converted to status :3F:34:30 before being sent to the network. See DI01:3F:34:30 for further status processing.

Yes/No

N/A

Verify the cassette coding. If the status is consistent, service the dispenser.


Yes/No

N/A



Yes/No

N/A



Yes/No

N/A


DI01:3D:35:26 The divert cassette is near full. This status is converted to status 3D:37:26 before being sent to the network. See DI01:3D:37:26 for more details. Note that for dispenser units containing a separate cassette or compartment for retracted bills, this status only applies to the

Yes/Yes

None

Empty the divert cassette. The divert counters must be reset through


27/107

21/10/2014


divert cassette or compartment.

Maintenance.

DI01:3D:35:38 The divert cassette is full. This status is converted to status 3D:37:38 before being sent to the network. See DI01:3D:37:38 for more details. Note that for dispenser units containing a separate cassette or compartment for retracted bills, this status only applies to the divert cassette or compartment.

Yes/Yes

Remove dispense Empty the from the transaction divert selection choices. cassette. The divert counters must be reset through Maintenance.

DI01:3D:35:39 The divert cassette is missing. This status is converted to status 3D:37:39 before being sent to the network. See DI01:3D:37:29 for more details. Note that for dispenser units containing a separate cassette or compartment for retracted bills, this status only applies to the divert cassette or compartment.

Yes/Yes

Remove dispense Insert the from the transaction divert selection choices. cassette.

DI01:3D:35:41 The feed module 1 notes are thinner than the key data as reported by the dispenser. This status is converted to status :3F:34:30 before being sent to the network. See DI01:3F:34:30 for further status processing.

Yes/No

N/A



Yes/No

N/A



Yes/No

N/A



Yes/No

N/A


DI01:3D:36:26 The retract cassette is near full. This status is converted to status 3D:37:26 before being sent to the network. See DI01:3D:37:26 for more details. Note that this status is only applicable for dispenser units containing a separate retract cassette or compartment for retracted bills.

Yes/Yes

None

Empty the retract cassette or compartment. The retract counters must be reset through Maintenance.

N/A

Look for unseated or swapped cassettes, or look for cassette tampering.

DI01:3D:36:35 The cassettes are shuffled as reported by the Yes/No dispenser. This status is converted to status :3F:36:35 before being sent to the network. See DI01:3F:36:35 for further status processing.


28/107

21/10/2014


DI01:3D:36:38 The retract cassette is full. This status is converted to status 3D:37:38 before being sent to the network. See DI01:3D:37:38 for more details. Note that this status is only applicable for dispenser units containing a separate retract cassette or compartment for retracted bills.

Yes/Yes

Empty the retract cassette or compartment. The retract counters must be reset through Maintenance.

DI01:3D:36:39 The retract cassette is missing. This status is converted to status 3D:37:39 before being sent to the network. See DI01:3D:37:29 for more details Note that this status is only applicable for dispenser units containing a separate retract cassette or compartment for retracted bills.

Yes/Yes

Insert the retract cassette.

DI01:3D:36:41 Feed module 1 notes are shorter than the key Yes/No data as reported by the dispenser. This status is converted to status :3F:34:30 before being sent to the network. See DI01:3F:34:30 for further status processing.

N/A



N/A



N/A



N/A


DI01:3D:37:26 The divert cassette is near full. Note this status Yes/Yes is translated from either a DI01:3D:35:37 or a DI01:3D:36:37. See these statuses for more details.

None

Empty the divert cassette, and/or the retract cassette if present. The divert and retract counters must be reset through maintenance.

DI01:3D:37:38 The divert cassette is full. Note this status is translated from either a DI01:3D:35:38 or a

Remove dispense Empty the from the transaction divert


Yes/Yes

29/107

21/10/2014


DI01:3D:36:38. See these statuses for more details.

selection choices.

DI01:3D:37:39 The divert cassette is missing. Note this status Yes/Yes is translated from either a DI01:3D:35:39 or a DI01:3D:36:39. See these statuses for more details.

cassette, and/or the retract cassette if present. The divert and retract counters must be reset through maintenance. Remove dispense Insert the from the transaction divert selection choices. cassette, and/or the retract cassette if present.

DI01:3D:37:41 Feed module 1 notes are longer than the key Yes/No data as reported by the dispenser. This status is converted to status :3F:34:30 before being sent to the network. See DI01:3F:34:30 for further status processing.

N/A



N/A



N/A



N/A


DI01:3E:00:00 1) Network error

1) The possible problems are that the network requested more than 50 bills or the network requested 0 bills. Check the function for correctness.

1) None

2) If this status is received during a opcommanded self-test, the device was specifically requested to do a self-test but was not enabled or present.

1) No/Yes 2) Yes/Yes

2) N/A

2) N/A DI01:3E:01:01 The door is open before the dispense. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

No/Yes

The dispense was

Ensure that the 30/107

21/10/2014


DI01:3E:02:00 Attempted a dispense with the chest door open. Yes/Yes

not performed. Send a function to exit the Consumer Request state. No dispense is possible until the condition is rectified. With this write command III security option set, a network dispense cannot be performed with the chest door open.

door closes and locks properly.

See network action.

DI01:3E:02:01 Attempted a dispense with one or more service cassettes installed.

Yes/Yes

With this write See network command III action. security option set, a network dispense cannot be performed with a service cassette installed.

DI01:3E:02:02 A self-test was performed with a service cassette installed.

Yes/Yes

With this write III command security option set, a selftest cannot be performed with a service cassette installed.

DI01:3E:02:03 A Dispense Test diagnostic ran without service cassettes installed on a non-presenter unit.

Yes/Yes

With this write See network command III action. security option set, the Dispense Test diagnostic will not dispense unless all cassettes are service cassettes.

DI01:3E:03:03 A dispense was attempted after currency that had been presented was not removed. This status only appears if the no retracts feature was selected.

Yes/Yes

N/A

The currency must be removed before dispenses can be performed.

DI01:3E:32:35 A jam failure from feed module 1 as reported by Yes/No the dispenser. This status is converted to status :3F:31:37 before being sent to the network. See DI01:3F:31:37 for further status processing.

N/A

Clear the bill jam. If necessary, service the dispenser.


N/A



N/A



See network action.

31/107

21/10/2014



N/A


DI01:3E:33:33 A jam between double detect and exit. This status is converted to status :3B:33:33 before being sent to the network if the retry was attempted but resulted in the same fault or was sent unchanged. The possible dispense operation completion is as follows:


1) Clear the bill jam. If consistent, service the dispenser.

1) Yes/Yes 2) Yes/No

2) N/A 2) Clear the bill jam. If consistent, service the dispenser.

1) The retry option is disabled or the dispense recovery preceding the retry failed. 2) The retry is attempted but resulted in the same fault. See DI01:3B:33:33 for further status processing. DI01:3E:33:34 A jam between double detect and reject. This status is converted to status :3F:33:34 before being sent to the network if the retry was attempted but resulted in the same fault or was sent unchanged. The possible dispense operation completion is as follows:

1) Yes/Yes 2) Yes/No

1) Remove dispense from the transaction selection choices. 2) N/A

1) The retry option is disabled or the dispense recovery preceding the retry failed. 2) The retry is attempted but resulted in the same fault. See DI01:3F:33:34 for further status processing.

1) Clear the bill jam. If the status is consistent, service the dispenser. 2) Clear the bill jam. If the status is consistent, service the dispenser. Check for debris near the exit sensor. If the status is consistent, service the dispenser.

DI01:3E:36:30 The counting sensor is blocked as reported by Yes/No the dispenser. This status is converted to status :3A:36:30 before being sent to the network. See DI01:3A:36:30 for further status processing.

N/A

DI01:3E:38:41 A double detect fault from feed module 1 as reported by the dispenser. This status is converted to status :3F:31:37 before being sent to the network. See DI01:3F:31:37 for further status processing.

Yes/No

N/A

Clear the bill jam. If the status is consistent, service the dispenser.


Yes/No

N/A



Yes/No

N/A


DI01:3E:38:44 A double detect fault from feed module 4 as reported by the dispenser. This status is converted to status :3F:32:30 before being sent

Yes/No

N/A

Clear the bill jam. If the status is


32/107

21/10/2014


to the network. See DI01:3F:32:30 for further status processing.

consistent, service the dispenser. Clear the material from the withdrawal area.

DI01:3F:00:01 The drawer sensor is blocked prior to dispensing No/Yes the first, second, or third consecutive time

Money has been dispensed. The decision to deliver is left to the network's discretion.

DI01:3F:00:03 The drawer sensor is not blocked after the first, No/Yes second, or third consecutive dispense operation.

Money has been dispensed. The decision to deliver is left to the network's discretion.

DI01:3F:30:31 An unsolicited note from feed module 1. The No/Yes retry resulted in the same fault. This status was converted from dispenser status :3B:30:31.

Remove dispense Replace the from the transaction cassette. selection choices.







DI01:3F:31:37 A feed failure from feed module 1. This status could have been converted from any of the following dispenser statuses: :3E:32:35, or:3E:38:41. The possible dispense operation completion is as follows:

No/Yes

Remove the denomination from the transaction selection choices.


No/Yes



No/Yes



Check the withdrawal area for cash or foreign material.

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. DI01:3F:31:38 A feed failure from feed module 2. This status could have been converted from any of the following dispenser status: :3E:32:36, or:3E:38:42. The possible dispense operation completion is as follows: 1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. DI01:3F:31:39 A feed failure from feed module 3. This status could have been converted from any of the following dispenser status :3E:32:37, or:3E:38:43. The possible dispense operation completion is as follows: 1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

33/107

21/10/2014


attempted. 2) The retry is attempted but resulted in the same fault. DI01:3F:32:30 A feed failure from feed module 4. This status could have been converted from any of the following dispenser statuses :3E:32:38, or:3E:38:44. The possible dispense operation completion is as follows:

No/Yes



1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. DI01:3F:33:34 A jam between double detect and reject. The No/Yes retry is attempted but resulted in the same fault. This status was converted from dispenser status :3E:33:34.

Remove dispense Clear the bill from the transaction jam. If the selection choices. status is consistent, service the dispenser.

DI01:3F:33:36 An unidentified cassette code. The retry is attempted but resulted in the same fault. This status was converted from dispenser status :3D:33:36.

No/Yes

Remove the denomination from the transaction selection choices (911). Ask the terminal for a hardware configuration message and try the dispenser again (912).

DI01:3F:34:30 The bill size does not match the cassette coding. This status could have been converted from any of the following dispenser statuses: 3D:33:41, :3D:33:32, :3D:33:43, :3D:33:44, :3D:35:41, :3D:35:42, :3D:35:43, :3D:35:44, :3D:36:41, :3D:36:42, :3D:36:43, :3D:36:44, :3D:37:41, :3D:37:42, :3D:37:43, or :3D:37:44

No/Yes

Remove dispense If the status is from the transaction consistent, selection choices. service the dispenser.

Replace with the correct cassette or the cassette is missing. Check the cassette codes.

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. DI01:3F:34:39 Too few notes are dispensed from feed module Yes/Yes 1. The possible dispense operation completion is as follows:



1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. 3) If the transport bill count is lower than the feed module bill count, this status will be set but http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

34/107

21/10/2014


the feed module bill count is used to determine if the number of bills dispensed matches the number of bills requested. DI01:3F:35:30 Too few notes are dispensed from feed module Yes/Yes 2. The possible dispense operation completion is as follows:








If this status is consistent, service the dispenser.

1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. 3) If the transport bill count is lower than the feed module bill count, this status will be set but the feed module bill count is used to determine if the number of bills dispensed matches the number of bills requested. DI01:3F:35:31 Too few notes are dispensed from feed module Yes/Yes 3. The possible dispense operation completion is as follows: 1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. 3) If the transport bill count is lower than the feed module bill count, this status will be set but the feed module bill count is used to determine if the number of bills dispensed matches the number of bills requested. DI01:3F:35:32 Too few notes are dispensed from feed module Yes/Yes 4. The possible dispense operation completion is as follows: 1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the same fault. 3) If the transport bill count is lower than the feed module bill count, this status will be set but the feed module bill count is used to determine if the number of bills dispensed matches the number of bills requested. DI01:3F:35:38 Too many notes are dispensed. This status was No/Yes converted from dispenser status :3B:35:38. The possible dispense operation completion is as follows: 1) The retry option is disabled or the dispense recovery preceding the retry failed. No retry is attempted. 2) The retry is attempted but resulted in the http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

35/107

21/10/2014


same fault. DI01:3F:36:31 The counting sensor is dirty. No retry is attempted. This status is not reported to the network. This status will only appear in the Device Activity Log. It will not affect dispense operation.

Yes/No

N/A

If this status is consistent, service the dispenser.

No/Yes

Remove dispense from the transaction selection choices (911). Ask the terminal for a hardware configuration message and try the dispense again (912).

Look for unseated or swapped cassettes.

DI01:3F:39:34 Unable to dispense on feed module 1. Dispense No/No (911) completed on another feed module. No retry is Yes/Yes attempted. (912)

None



None



None



None


DI01:3F:36:35 The cassettes are shuffled. This status was converted from dispenser status :3D:36:35. A retry is only attempted for 911 emulation if it is enabled.

[1] indicates

a trap condition

3.8 DP01 (Depositor Status Messages) This section describes the depositor fault status messages. The device type and number as it appears in the status message is DP01. Refer to Table 3-7 for the depositor fault status messages. NOTE For depositors that combine deposit functionality with envelope dispensing functionality, this section provides the status messages for the deposit functions only. For fault status messages for the envelope dispensing functions, refer to Section 3.23.

Status Message

Table 3-7 DP01 - Depositor Status Message Descriptions Sent to Description Journal Network Action

DP01:23:00:00 Consumer timeout


On-site Action

No/Yes Send a function None command to exit the Consumer Request state and continue, or send another function c ommand to operate the 36/107

21/10/2014


depositor again. DP01:23:00:01 Possible incomplete deposit. Both switches Yes/Yes Mark the transaction None are blocked at the end of the deposit. as subject to verification. DP01:23:00:02 Device timeout. No deposit after 15 minutes.

Yes/Yes Send a function None command to exit the Consumer Request state and continue, or send another function c ommand to operate the depositor again.

DP01:23:00:03 Possible incomplete deposit. Both switches Yes/Yes Mark the transaction None are blocked at the end of the deposit. as subject to verification. DP01:24:00:00 Consumer cancel

Yes

Send a Function No action is required. Command message to exit the Transaction Request state and continue.

DP01:30:41:32 Unsupported command or invalid data (internal error)

TBD

TBD


DP01:34:31:30 Configuration data status (34) with the data TBD to follow (31:30).

TBD

TBD

DP01:38:00:00 Internal communications error

Remove deposit transactions from the transaction selection choices. Initiate a service investigation.

Check the depositor cables for a loose connection. If the problem persists, a service investigation is required.

Yes

DP01:3C:42:56 Jam at the front switch at the beginning and No/Yes N/A end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch.

Check for and remove the jam at the front switch. If no jam is found and occurrence is consistent, service is required.

DP01:3C:42:69 Jam at the rear switch at the beginning and No/Yes N/A end of the transaction. The front switch is activated in the normal manner. There is a possible broken rear switch.

Check for and remove the jam at the rear switch. If no jam is found and occurrence is consistent, service is required.

DP01:3C:42:6F Jam at the rear switch at the end of the No/Yes N/A transaction. The front switch is activated in the normal manner. There is a possible broken rear switch.

Check for and remove the jam at the rear switch. If no jam is found and occurrence is consistent, service is required.

DP01:3C:42:7F The deposit gate is jammed open.

Yes

Not applicable

Clear the jam.

DP01:3D:50:6F The deposit cassette is nearly full.

TBD

Not applicable

Empty the deposit cassette.

DP01:3D:50:7F The deposit cassette is full.

Yes

Not applicable

Empty the deposit cassette.

DP01:3D:60:6C The deposit cassette is inoperative.

TBD

Remove deposit transactions from

Check that the deposit cassette is installed


37/107

21/10/2014


the transaction selection choices. Initiate the on-site action.

correctly, and that there is no blockage of the deposit transport. If the problem persists, a service investigation is required.

Remove deposit transactions from the transaction selection choices. Initiate the on-site action.

Check for a missing deposit cassette, or for a cassette that is not correctly installed.

DP01:3D:60:7C The deposit cassette is absent.

Yes

DP01:3E:40:4F During a self-test this status message indicates that the switches are blocked.

No/Yes N/A

Check for and remove the jam at both the front and rear switches.

DP01:3E:40:54 Jam at the front switch at the beginning and No/Yes N/A end of the transaction. The rear switch is not activated.

Check for and remove the jam at the front switch.

DP01:3E:40:56 Jam at the front switch at the beginning and No/Yes N/A end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch.

Check for and remove the jam at the front switch. If no jam is found and the occurrence is consistent, service is required.

DP01:3E:40:5D Jam at the front switch at the end of the transaction. The rear switch is not activated.

No/Yes N/A


DP01:3E:40:5F Jam at the front switch at the end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch.

No/Yes N/A


DP01:3E:40:6C Soft fault, device cannot operate / no errors. TBD The front switch was closed and the rear switch was open at completion (not a normal finish). The front switch was closed and the rear switch was closed at the beginning (a normal entry).

TBD

TBD

DP01:3E:40:70 Soft fault, device cannot operate/ no errors. TBD Front and rear switches were closed at completion (a normal finish). The front and rear switches were open at the beginning (not a normal entry).

TBD

TBD

DP01:3E:40:74 Soft fault, device cannot operate / no errors. TBD The front and rear switches are closed at completion (a normal finish). The front switch was open and the rear switch was closed at the beginning (not a normal entry).

TBD

TBD

DP01:3E:40:7C The deposit gate did not open.

TBD

Check the gate and the transport for a blockage. If there is no blockage, a service investigation is required.

Remove deposit

Check the gate and the

TBD

DP01:3E:42:40 An envelope is jammed in the transport or is Yes http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

38/107

21/10/2014


present in the transport.

transactions from the transaction selection choices. Initiate the on-site action.

transport for a blockage. If there is no blockage, a service investigation is required.

DP01:3E:42:46 Jam at the front switch at the beginning and Yes/Yes N/A both switches at the end of the transaction.

Check for and remove the jam at both front and rear switches.

DP01:3E:42:48 Soft fault, device cannot operate / envelope TBD detect, gate switch fault. The front and rear switches were open at completion (not a normal finish). The front was closed and the rear switch was open at the beginning (not a normal entry). Neither switch changed status

TBD

TBD

DP01:3E:42:49 Jam at the rear switch at the beginning and Yes/Yes N/A both switches at the end of the transaction.


DP01:3E:42:4F Jam at both switches at the end of the transaction.

Yes/Yes N/A




DP01:3E:42:5F Jam at the front switch at the end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch.


No/Yes N/A

DP01:3E:42:68 Jam at the rear switch at the beginning and No/Yes N/A the end of the transaction. The front switch is not activated.

Check for and remove the jam at the rear switch.

DP01:3E:42:6E Jam at the rear switch at the end of the transaction. The front switch is not activated.

No/Yes N/A

Check for and remove the jam at the rear switch.

DP01:3E:42:7C Gate is jammed open. Neither the front nor No/Yes N/A rear switch is activated.

Check for and remove the jam at the gate.



DP01:3F:40:4F Jam at both switches at the end of the transaction (sent to the network as 3E:40:4F).

Yes/No N/A

Check for and remove the jam at both the front and rear switches.

DP01:3F:40:54 Jam at front switch at the beginning and end of the transaction. The rear switch is not activated (sent to the network as 3E:40:54).

Yes/No N/A


DP01:3F:40:56 Jam at the front switch at the beginning and Yes/No N/A end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch (sent to network as 3E:40:56).


DP01:3F:40:5D Jam at the front switch at the end of the transaction. Rear switch is not activated

Check for and remove the jam at the front


Yes/No N/A

39/107

21/10/2014


(sent to network as 3E:40:5D). DP01:3F:40:5F Jam at the front switch at the end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch (sent to network as 3E:40:5F).

switch. Yes/No N/A


DP01:3F:42:54 Jam at the front switch at the beginning and Yes/No N/A end of the transaction. The rear switch is not activated (sent to network as 3E:42:54).


DP01:3F:42:56 Jam at the front switch at the beginning and Yes/No N/A end of the transaction. The rear switch is activated in the normal manner. There is a possible broken front switch (sent to network as 3C:42:56).

Check for and remove the jam at the front switch. If no jam is found, and occurrence is consistent, service is required.

DP01:3F:42:5F Jam at the front switch at the end of the transaction. The rear switch is activated in the normal manner. Possible broken front switch (sent to network as 3E:42:5F).

Yes/No N/A


DP01:3F:42:7C The deposit gate is jammed open.

No

Not applicable


DP01:3F:42:80 Deposit printer is inoperative.

TBD

TBD

Service investigation

DP01:3F:42:81 Printer error. The XFS SP has reported an unspecified problem with the depository printer.

TBD

Not applicable


DP01:3F:42:85 Gate error. The XFS SP has reported an unspecified problem with the deposit gate.

TBD

Not applicable


DP01:3F:42:86 Transport error. The XFS SP has reported an unspecified problem with the depository transport.

TBD

Not applicable


DP01:3F:42:87 The envelope is the wrong size.

TBD

Not applicable


DP01:3F:50:00 Ink Low Status

Yes/Yes

Replace ink cartridge.

Table 3-8 DP01 - IDM Status Message Descriptions Status Message and Description DP01:00:00:00

Sent to DAL/ Journal Yes/Yes

Network Action N/A

On-site Action N/A

Next State N/A

This is a status received from a device indicating that a self-test was http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

40/107

21/10/2014


performed and no errors were found. DP01:23:00:00 Consumer timeout

DP01:24:00:00 Consumer cancel

DP01:30:41:30

No/No (state) No/Yes (function)

The consumer either did not insert a N/A document into the depositor or failed to remove the document in the allowed time. If the document was being returned, it has been captured and placed in the specified bin. The host/controller must be aware of this. The consumer should also be alerted by directing the ATM to a state displaying a screen to this effect. In either case, cancel the current transaction and direct the terminal to a close state or ask the consumer if he or she wants another transaction.

Timeout next state

No/No (state) No/Yes (function)

The consumer has indicated that he or N/A she wants to cancel the deposit operation in process. Cancel the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction.

Cancel next state (if supplied) else timeout next state

Yes/Yes

Remove all deposits from the selection list.

Reject of Deposit Envelope command

DP01:30:44:30

N/A

Note: The PPM will not accept this command. It is not capable of accepting envelope deposits. Remove all deposits from the selection list.

Reject of Document Accept command

DP01:30:45:30

This fault indicates a Fault next software/ hardware state misalignment and must be corrected by replacing the depositor or depositor firmware. Call service.

Yes/Yes


This fault indicates a Fault next software/hardware state misalignment and must be corrected by replacing the depositor or depositor firmware. Call service.

N/A


This fault indicates a Fault next software/hardware state misalignment and must be corrected by replacing the depositor or depositor firmware.

Reject of deposit document (Escrow to Cassette) command DP01:30:46:30

Check the service manual Fault next for the correct jumper state position settings.

Reject of return document command

DP01:30:xx:yy

Yes/No, N/A except for The IDM3 rejected a 30:50:30 command. The which command rejected is only xx and the reason appears code is yy. Valid on commands xx are: diagnostic screen 30 - reset device 31 - idle device

Make sure that the proper N/A device revision, firmware revision, and device properties settings are used. These statuses may indicate a configuration incompatibility and not a hardware problem. If the problem is consistent, service is required.

34 - return device configuration data http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

41/107

21/10/2014


35 - return statuses 37 - return device CRCs 41 - deposit envelope 42 - print on document after power fail 44 - check accept 45 - retain 46 - return 48 - enable check scan 49 - unlock envelope door 50 - calibrate Valid reason codes yy are: 30 - invalid command 31 - command received out of sequence 32 - buffer overflow 33 - device ID incorrect 34 - data format error DP01:38:nn:nn (nn can be any number) Communications problem

Yes/Yes

Exit the current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction. The terminal will attempt to restore communications with the depositor as soon as the consumer is off the terminal. If communications cannot be restored, the depositor will be disabled by the terminal itself and subsequent depositor function IDs will be answered with a 39 00 0x status.

DP01:39:00:01

Check all cables and Fault next connectors. Run state CSSEDT to see if the Check depositor's connection is defined. Run a trace (using comm subsystem) and check that the device is being polled. If no problems can be found, replace the depositor. If the terminal still reports this comm fault, call service.

Yes/ Yes Remove all deposits from the selection list until the unit is repaired. Exit the Depositor is disabled current transaction and either direct the due to a fault terminal to a close state or ask the condition. consumer if he or she wants another transaction.

Check for and remove the Fault next jam. If unsuccessful, call state service.

DP01:39:00:02

Check for and remove the Fault next jam. If unsuccessful, call state

Yes/ Yes Remove all deposits from the selection list until the unit is repaired. Exit the


42/107

21/10/2014


Depositor is disabled by the network.

current transaction and either direct the terminal to a close state or ask the consumer if he or she wants another transaction.

DP01:39:00:03

Yes/ Yes Remove all deposits from the selection list until the unit is repaired. Exit the Depositor is disabled current transaction and either direct the due to a fault terminal to a close state or ask the condition and the consumer if he or she wants another network. transaction. DP01:3A:XX:4F

Yes/Yes

One or more document sensors are blocked. The document is jammed, or there is a defective sensor. Refer to Table 2 in Appendix A for a hexto-binary conversion chart and an example conversion.

service.

Check for and remove the Fault next jam. If unsuccessful, call state service.

If the check involved is already posted, Check for and remove the Fault next exit the current transaction and either jam. If unsuccessful, call state direct the terminal to a close state or ask service. the consumer if he or she wants another transaction. The terminal will automatically attempt to retain the check into the depository cassette at the close state. However, if the check is not yet posted, attempt to return it to the consumer either by sending a check return function ID or direct the terminal to a check return state. If this operation fails as well, make a note that the unposted check is captured by the terminal and either direct the terminal to a close state or ask the consumer if he or she wants another transaction. The terminal will automatically attempt to retain the check into the depository cassette at the close state.

XX = document sensor states (0 = clear, 1 = blocked) bit 0 = left entry and/or right entry bit 1 = throat

Do not disable the check depositor because of this fault.

bit 2 = middle (not yet implemented) bit 3 = left escrow and/or right escrow bit 4 = transport exit bit 5 = camera exit bit 6 always = 1 bit 7 always = 0 DP01:3A:45:4B

Yes/Yes

Disable the depositor for all deposit transactions.

Check for proper bin operation in diagnostics.

Fault next state

Bin mechanism failure during a document retain. DP01:3A:80:80

Yes/Yes

Disable the check deposits with image scanning in conjunction with an image character recognition state.

Check software configuration and setup for the image scanner.

Scanner Fault Next State [2]

The scanner image buffer is not allocated by the device driver or the device driver is not installed. (not applicable for Opteva terminals)

Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes.


43/107

21/10/2014


DP01:3A:80:81

Yes/Yes

PCISCAN.SYS device driver could not find the PCI Scanner card. (not applicable for Opteva terminals) DP01:3A:80:82

Yes/Yes

Yes/Yes

Character recognition is not available.

DP01:3A:81:XX

Check installation of PCI Scanner scanner card. Fault Next State [2]


PCI Scanner card configuration error. (not applicable for Opteva terminals) DP01:3A:81:20

Disable the check deposits with image scanning in conjunction with an image character recogntion state.

Yes/Yes

Image Processor internal fault.

Disable the check deposits with image scanning in conjunction with an image character recognition state.

Check installation of the PCI scanner card


Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Disable the check deposits with image scanning in conjunction with an image character recognition state.

Check software configuration and make sure RSS is installed.


Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Disable check deposits with image scanning in conjunction with an image character recognition state.

Check hardware installation and software configuration.


Check hardware installation and software configuration.


Call a service representative



Scanner Fault Next


Fault Decoding is bitmapped as follows: 0 - Reserved 1 - Reserved 2 - Recognition Initialization fault 3 - ICS.CFG file not found 4 - Reserved 5 through 7 Reserved DP01:3A:82:00

Yes/Yes

Image Processor not responding.

DP01:3A:A0:01

Yes/Yes

Buffer allocation failed.

DP01:3A:A0:02

Yes/Yes

Disable check deposits with image scanning in conjunction with an image character recognition state. Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Disable the check deposits with image scanning in conjunction with an image character recognition state. Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Disable the check deposits with image scanning in conjunction with an image


44/107

21/10/2014


Document image display request failed.

DP01:3A:A0:03

character recognition state. Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Yes/Yes

Video rejected image icon.

DP01:3A:A0:04

State [1]

Yes/Yes

Image icon storage failed.

Disable the check deposits with image scanning in conjunction with an image character recognition state. Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. Disable check deposits with image scanning in conjunction with an image character recognition state.







Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. DP01:3A:A0:XX

Yes/Yes

Scan operation failed.

DP01:3B:XX:71 The front sensors(s) never became blocked while attempting to return a check to a consumer Refer to Table 2 in Appendix A for a hexto-binary conversion chart and an example conversion. XX = documented sensor state (0 = clear, 1 = blocked) bit 0 = left entry and/or right entry bit 1 = throat bit 2 = middle bit 3 = left escrow and/or right escrow

Yes/Yes

Disable check deposits with image scanning in conjunction with an image character recognition state.

Note that this fault does not prevent envelope deposits. The terminal remains capable of accepting envelopes. If the check involved is already posted, Check for and remove the Fault next exit the current transaction and either jam. If unsuccessful, call state direct the terminal to a close state or ask service. the consumer if he or she wants another transaction. The terminal will automatically attempt to retain the check into the depository cassette at the close state. However, if the check is not yet posted, attempt to return it to the consumer either by sending a check return function ID or directing the terminal to a check return state. If this operation fails as well, make a note that the unposted check is captured by the terminal and either direct the terminal to a close state or ask the consumer if he or she wants another transaction. The terminal will automatically attempt to retain the check into the depository cassette at the close state. Do not disable the check depositor because of this fault.

bit 4 = transport exit bit 5 = camera exit bit 6 = always 1 bit 7 = always 0 http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

45/107

21/10/2014


DP01:3B:80:XX

Yes/Yes

Try operation again.

If persistant, check the minimum system requirements.


Yes/Yes

Try operation again

N/A


Yes/Yes

N/A

Verify proper operation with a test document. If unsuccessful, call service.

MICR fault next state (if supplied) else good next state


N/A


Image Processor communication error. DP01:3B:81:XX RSS software exception. XX is the code indicating the software exception module. DP01:3C:00:30

No MICR data is detected on the check. The MICR fault limit is reached. This fault will only occur during a deposit state. DP01:3C:80:00 Yes/Yes Multiple failures to locate RSS window data. DP01:3D:30:4A

Yes/Yes

(service should replace CCA)

Fault nextstate

PLD failure during reset. DP01:3D:30:4B

No need for network action, because TCS will shutdown the depositor when this fault occurs.

No/No

Call service

Fault next state

Bin mechanism failure during reset DP01:3D:30:4C

Shutdown depositor for any deposit operation and direct the terminal to a close state.

Yes/Yes

Call service

Fault next state

Gate mechanism failure during reset. DP01:3D:30:4D

Shutdown the depositor for any deposit operation and direct the terminal to a close state.

Yes/Yes

Scanner not latched during reset. DP01:3D:30:4E


Check to see if the Fault next scanner is latched. If it is state latched, call service.

Yes/Yes

Printer not latched during reset. DP01:3D:30:4F


Check to see if the printer Fault next is latched. If it is latched, state call service.

Yes/Yes

Call service

Fault next state

Printer failure during reset. DP01:3D:41:4A


Ys/Yes

(service should replace CCA)

Fault nextstate

PLD failure during envelope deposit. DP01:3D:41:4B


Yes/Yes

Fault next state

Bin mechansim failure duiring envelope deposit DP01:3D:41:4C

Shutdown depositor for any deposit Call service. operaion and direct the terminal to a close state.

Yes/Yes

Abort the operation. Either direct the

Fault next


Call service

46/107

21/10/2014


Gate failure during envelope deposit. DP01:3D:41:4F

terminal to a close state or ask the customer if he or she wants another transaction.

state

Yes/Yes

Abort the operation. Either direct the terminal to a close state or ask the customer if he or she wants another transaction.

Call service

Fault next state

Yes/Yes

TBD

TBD

Fault next state


Call service

Fault next state

Yes/Yes


Check to see if the Fault next scanner is latched. If it is state latched, call service.

DP01:3D:44:4E

Yes/Yes

Printer not latched during a check deposit. DP01:3D:44:4F


Check to see if the printer Fault next is latched. If it is latched, state call service.

Yes/Yes


Call service

Fault next state

Yes/Yes


Call service

Fault next state

DP01:3D:46:4C

Yes/Yes

Call service

Fault next state

Gate mechanism failure during a document return. DP01:3D:46:4F


Yes/Yes


Call service

Fault next state

Yes/Yes


Inspect scanner

ScannerFault nextstate

Yes/Yes


Inspect install


Printer failure during an envelope deposit. DP01:3D:44:4B

Bin mechanism failure during a check deposit. DP01:3D:44:4C Yes/Yes Gate failure during a check deposit. DP01:3D:44:4D Scanner not latched during a check deposit.

Printer failure during a check deposit. DP01:3D:45:4F Printer failure during a deposit.

Printer failure during a document return. DP01:3D:51:nn Note: nn = status of bottom scanner(Possibly 50 55) Scanner hardware error DP01:3D:52:nn Note: nn = status of bottom scanner(Possibly 50 55)


47/107

21/10/2014


Scanner init error DP01:3D:53:nn

Yes/Yes


Check cabling on IDM scanner card.

Yes/Yes


Inspect configuration and ScannerFault IEEE 1394 driver. nextstate

Yes/Yes

N/A

N/A

N/A

Verify proper operation with a test document. If unsuccessful, call service.

MICR fault next state (if supplied) else good next state

Note: nn = status of bottom scanner(Possibly 50 55)


Scanner host error DP01:3D:54:nn Note: nn = status of bottom scanner(Possibly 50 55) Scanner interface error DP01:3E:00:00 If this status is received during an op- commanded selftest, the device was specifically requested to do a self-test but was not enabled or present. DP01:3F:00:30

Yes/ Yes N/A

No MICR data is detected on the check. DP01:3F:40:41

Yes/ Yes Note that a document was placed in the Attempt a normal check Deposit Cassette and continue normal accept and retain with a Abnormal document transaction processing. A persistent test document. If retain. A document warning of this type indicates either a unsuccessful, call was either jammed in hardware problem preventing normal service. the IDM or check retains or improper network abandoned by the programming. transaction s equence and retained into the Deposit Cassette during the close state. DP01:3F:44:31 Yes/ Yes Display a screen message indicating a Verify proper operation wrong sized document. Offer the choice with a test document. If The document that of retrying the deposit, canceling the unsuccessful, call was inserted was not session, or selecting another transaction. service. a check. It could be too short or too long. DP01:3F:55:5t Yes/Yes Network should direct terminal to attempt N/A the deposit again Note: 5t = status of top scanner (Possibly 50 - 55)

N/A

Media fault next state (if supplied) else fault next state Scanner Fault next state

Scan error DP01:3F:XX:3b

Yes/Yes

Try to retain to a different bin first. If unsuccessful, retain to bin 0. If s till


Clear bin deposits

Fault next state 48/107

21/10/2014


Document jam or b bin full during retain operation.

unsuccessful, shutdown depositor for any deposit operation and direct terminal to a close state

XX = document sensor states (0 = clear, 1 = blocked) Refer to Table 2 in Appendix A for a hexto-binary conversion chart and an example conversion. bit 0 = left entry and/or right entry bit 1 = throat bit 2 = middle (not yet implemented) bit 3 = left escrow and/or right escrow bit 4 = transport exit bit 5 = camera exit bit 6 = always 1 bit 7 = always 0n DP01:3F:80:XX

Yes/Yes

Try the operation again.

If frequent, call a service representative.

Scanner fault next state [1]

Yes/Yes


If frequent, check/replace Scanner fault the scanner. Call a next state. service representative. [1]

Yes/Yes


N/A

Recognition software error. XX is the recognition software error code. DP01:3F:81:00 Display image error. DP01:3F:81:XX Generate display fault.

Scanner fault next state. [1]

Fault decoding for XX is as follows: 01 - RAW_IMAGE_ TOO_SMALL 02 IMAGE_LENGTH_ LT_MINIMUM 03 IMAGE_WIDTH_ LT_MINIMUM 04 - FAIL_TO_FIND_ http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

49/107

21/10/2014


LEADING_EDGE 05 - FAIL_TO_FIND_ TRAILING_EDGE 06 - FAIL_TO_FIND_ LEFT_EDGE 07 - FAIL_TO_FIND_ RIGHT_EDGE 81 DISPLAY_BUFFER_ GT_MAX 82 DISPLAY_BUFFER_ TOO_SMALL 83 - ORIENTATION_ PARM_NOT_VALID 84 - RESOURCE_ MALLOC_FAILURE FE - Deskew Move it Error FF - Deskew Process Error DP01:3F:82:XX

Yes/Yes


Check document identification parameter and/or check scanner connection.

Yes/Yes


If frequent, check/replace Scanner fault scanner; call your service next state. representative [1]

Image operation error.


Decoding is bitmapped as follows: 0 - No template size match to document image 1 - IP has no image present 2 - Reserved 3 through 7 reserved DP01:3F:9M:XX Scanner operational error. The decoding for M is bitmapped as follows: 0 - FIFO 0 Empty, 0=true, 1=false 1 - FIFO 1 Empty, http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

50/107

21/10/2014


0=true, 1=false 2 - FIFO 2 Empty, 0=true, 1=false 3 - FIFO 3 Empty, 0=true, 1=false The decoding for XX is bitmapped as follows: 0 - LED State 1 - FIFO 3 FULL, 0=false, 1=true 2 - FIFO HALFFULL, 0=false, 1=true 3 - FIFO UNDERRUN, 0=false, 1=true 4 - FIFO OVERRUN, 0=false, 1=true 5 - FAULT, 0=false, 1=true 6 - SCAN INTERRUPT, 0=false, 1=true 7 - STT, 0=false, 1=true DP01:3F:A0:00

Yes/Yes


Check software configuration for consumer display.


Yes/Yes


N/A


Kernal mismatch. DP01:3F:A0:XX RAM manager access failed. [1] If

scanner fault next state exit is not defined for any deposit state operation, the fault next state exit will be taken.

[2]

This is the next state exit taken from Image character recognition state.

Status Message \ Device Status

Table 3-9 DP01 - BNA Emulated Depositor Status Message Descriptions Sent to DAL \ Description Journal Network Action On-site Action

DP01:30:41:32 Command reject

Yes /Yes

N/A

DP01:38:00:00 Communications problem.

Yes / Yes

Remove the Service required. deposit from the transaction selection choices.

DP01:3D:50:7F The cassette is full at the end of the transaction

Yes /

Remove the


Ensure proper selection and configuration of the device.

Remove the 51/107

21/1 21/10/ 0/20 2014 14


Yes

deposit from the deposit cassettes transaction and replace with selection choices. empty ones.

DP01:3D:60:7C Ca C assette is absent

Yes / Yes

Remove the Replace the deposit from the cassette. transaction selection choices.

DP01:3E:00:0 DP01:3E:00:00 0 1) Network Network fault, invalid ope opera ration tion req reque uested sted

1) No / Yes

DP01:3E:42:40 Hardware error

Yes / Yes

1) Make sure the 1) No action function command command required. 2) If this status is received during a opdata is correct. commanded self-test, the device was specifically 2) Yes / 2) N/A commanded to do a self-test but was not enabled Yes 2) N/A or present. Remove the Service required. deposit from the transaction selection choices.

3.9 DR01 (Cash Presenter Status Messages) This section describes the cash presenter fault status messages. The device type and number as it appears in the status message is DR01. Refer to Table 3-10 for 3-10 for the cash presenter fault status messages. NOTE This section provides the status messages for the cash presenter functions only (present, dump, and restore). For fault status messages for the dispense function, refer to Section 3.7. 3.7.

Status Message

Table 3-10 DR01 - Cash Presenter Status Message Descriptions Sent to Description Journal Network Action On-site Action

DR01:23:00:0 DR01:23:00:01 1 Consumer Consumer timeout. timeout. Yes The consumer had access to the cash but did not take all of it.

The resul sult of the the delive liverry is uncertain. The consumer might have received all or part of the cash. Continue normal transaction processing.

DR0 DR01:23 :23:00 :00:30 :30 Money no not re removed ved.

Con Consum sumer tim timeout. The Clear bills or other material consumer had access to the cash from the withdrawal area. but did not take all of it. The terminal is configured to not retract after the consumer timeout. Continue normal transaction processing.

Yes

DR01:38 DR01:38:00 :00:00 :00 Intern Internal al Yes communications error error

Clear bills or other material from the withdrawal area.

Remove cash dispense Check the cash dispenser transactions from the transaction cables for a loose connection. selection choices. If the problem persists, a service investigation is Initiate a service investigation. required.

DR01:3A DR01:3A:31 :31:41 :41 This This status may may Yes/Yes The pre present sent was not perform performed ed.. appear because of one With the first situation in the of the following: description, remove dispense from the list of transaction 1) The money tray choices. No dispense is possible does not move during until the condition is rectified. the present.

With the first situation in the description, check for mechanical binding of the cash tray. Check the cam belt, motor, and fuse. Check the cam sensors and connections.

2) This status also appears in diagnostics and indicates indicates that http://techpubs.di ebol d.com /techpubs/books/TP- 820741- 001/TP- 820741- 001- 1.htm

52/107

21/1 21/10/ 0/20 2014 14


there is no money to present. DR01:3A:31:4 DR01:3A:31:44 4 The money money tray does does not move during the Restore.

Yes/Yes The Restore was not not completed. completed. Send function to exit the Consumer Request State. No dispense is possible until the condition is rectified.

DR01:3A:31:4 DR01:3A:31:46 6 A hardwar hardware e erro error r occurred during a dump operation.

Yes

Check for mechanical binding of the cash tray. Check the cam belt, motor, and fuse. Check cam sensors and connections.

Remove cash dispense Service investigation transactions from the transaction selection choices. Initiate a service investigation.

DR01:3A:32:4 DR01:3A:32:46 6 The divert divert does does not Yes/Yes The pur purge ge was was not completed. completed. move during the purge. Remove dispense from list of transaction choices. No dispense is possible until the condition is rectified.

Check for the mechanical binding of the divert door. Check the cam belt, motor, and fuse. Check the cam sensors and connections.

DR01:3A:33:4 DR01:3A:33:41 1 The cash was was not not presented to the customer but is in transport and may be vulnerable.

Yes Yes

Mark th the tra transact sactio ion n as “su “sub bject ject Check for mechanical binding to verification" and do not reverse of the exit shutter. the tran t ransact saction ion amount. amount.

DR01:3A:33:4 DR01:3A:33:44 4 Exit shutter does does not not open during Restore.

Yes/Yes The Restore was not not completed. completed. Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified.

Check for the mechanical binding of the shutter and the proper adjustment of the switch. switc h. Check the cam belt, belt, motor, and fuse. Check the cam sensors and connections.

DR01:3A:33:4 DR01:3A:33:45 5 Exit shutter does does not not open during Retract.

Yes/Yes The Retract Retract was not complete completed. d. Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified.

Check for the mechanical binding of the shutter and the proper adjustment of the switch. switc h. Check the cam belt, belt, motor, and fuse. Check the cam sensors and connections.

DR01:3A:34:4 DR01:3A:34:45 5 A hardwar hardware e erro error r occurred during the dump operation.

Yes


The dump operatio tion was was no not completed. Remove cash dispense transactions from the transaction selection choices. Initiate a service investigation.

DR01:3A:34:4 DR01:3A:34:46 6 The tran transpor sportt motor is Yes/Yes The pur purge ge was was not completed. completed. locked in purge. Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified.

Check the transport belts, motor, and fuse. Check the timing wheel, sensor, and connections.

DR01:3A DR01:3A:36 :36:41 :41 Bill sensor sensor stuck clear clear Yes/Yes Present Present was not not perform performed ed.. during Present. Remove dispense from list of transaction choices. No dispense is possible until the condition is rectified.

Check for money jam in bill path. Check the transport and pushplate mechanism for proper proper bill movement c apability apability .

DR01:3A:36:4 DR01:3A:36:44 4 The bill sensor sensor stuck clear during the Restore.

Yes/Yes The Restore was not not completed. completed. Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified.

Check for the binding of the pushplate. Check the pushplate motor and fuse. Check the bill sensor and connections.

DR01 DR01:3A: :3A:3 36:46 :46 The The bill ill sen sensor sor is

Yes/Y Yes/Ye es The The purge was was no not com complete leted d.

Che Check for for the the bind inding ing of th the


53/107

21/1 21/10/ 0/20 2014 14


stuck clear during the purge.

DR01:3A:37:4 DR01:3A:37:41 1 A hardwar hardware e erro error r Yes occurred during the present operation. No bills were presented to the consumer.

Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified. Remove cash dispense transactions from the transaction selection choices.

pushplate. Check the pushplate motor and fuse. Check bill sensor and connections. Service investigation

Initiate a service investigation.

DR01:3A:37:4 DR01:3A:37:45 5 Pushplate Pushplate stepper stepper Yes/Yes The Retract Retract was not complete completed. d. Check for a money jam at the clock timeout during a Remove dispense from the list of bill sensor. Check the sensor Retract. transaction choices. No dispense operation and connections. is possible until the condition is rectified. DR01:3A:37:4 DR01:3A:37:46 6 Pushplate Pushplate stepper stepper Yes/Yes The pur purge ge was was not completed. completed. Check for a money jam at the clock timeout during a Remove dispense from the list of bill sensor. Check the sensor purge. transaction choices. No dispense operation and connections. is possible until the condition is rectified. DR01:3A:38:4 DR01:3A:38:46 6 Pushplate Pushplate sensor sensor blocked during purge.

Yes/Yes The pur purge ge was was not completed. completed. Remove dispense from the list of transaction choices. No dispense is possible until the condition is rectified.

Check for mechanical binding of the cash tray. Check the cam belt, motor, and fuse. Check the cam sensors and connections.

DR01:3A:39:4 DR01:3A:39:44 4 Pushplate Pushplate sensor sensor failure during a Restore.

Yes/Yes The Restore was not not completed. completed. Send a function to exit the Consumer Request state. No dispense is possible until the condition is rectified.

Check for mechanical binding of the cash tray. Check the cam belt, motor and fuse. Check the cam sensors and connections.

DR01:3A:39:4 DR01:3A:39:46 6 Pushplate Pushplate sensor sensor failure during a purge.

Yes/Yes The pur purge ge was was not completed. completed. Remove dispense from list of transaction choices. No dispense is possible until the condition is rectified.

Check for the mechanical binding of the cash tray. Check the cam belt, motor, and fuse. Check the cam sensors and connections.

DR01:3A:41:4 DR01:3A:41:40 0 The cash canno cannott be Yes presented to the consumer. (Some bills might have been presented to the consumer.)

The resul sult of the the delive liverry is uncertain. The consumer might have received all or part of the cash. Continue normal transaction processing.


DR01:3B:30:4 DR01:3B:30:45 5 The bills canno cannott be Yes retracted and dumped. All the cash was taken.

Assu ssume tha that th the prior de delive liverry was complete. Continue C ontinue normal normal transaction processing.

No action act ion is required required..

DR01:3C:33:44 DR01:3C:33:44 The exit shutter doe does s not close after the Restore.

Yes/Yes The Restore was not not completed completed due to an obstruction of normal shutter movement. C Continue ontinue normal transaction processing. If the fault is truly a hardware error, it will prevent further dispenses by reporting Door Open Prior.

Check for the mechanical binding of the shutter and the proper adjustment of the switch. switc h. Check the cam belt, belt, motor, and fuse. Check the cam sensors and connections. (This fault may be consumerinduced.)

DR01:3C:33:45 DR01:3C:33:45 The exit shutter shutter will not close after the dump operation. The dump operation was not completed due to some obstruction at

Yes

Check for mechanical binding of the exit shutter.

Con Contin tinue normal tr transact sactiion processing.


54/107

21/10/2014


the exit shutter. DR01:3E:00:00 The terminal attempted No to perform an illegal operation.


Check that the Fascia (FCA) device property has Device Enable set to ON.

DR01:3E:35:45 The bill sensor is jammed during the Retract.

Yes/Yes The Retract was not completed. Check for a money jam at the Remove dispense from the list of bill sensor. Check sensor transaction choices. No dispense operation and connections. is possible until the condition is rectified.

DR01:3E:35:46 The bill sensor is jammed during the purge.

Yes/Yes The purge was not completed. Check for a money jam at the Remove dispense from list of bill sensor. Check sensor transaction choices. No dispense operation and connections. is possible until the condition is rectified.

DR01:3F:00:40 The forgotten cash has Yes been removed.



DR01:3F:30:41 The cash cannot be presented to the consumer. There are no bills to present.

If there should have been bills to present, discontinue cash dispense and present operations, and initiate a service investigation. Otherwise, continue normal transaction processing.

No action is required for infrequent occurrences of t his status.

DR01:3F:30:45 The bills cannot be Yes retracted and dumped. All the cash was taken.

Assume that the consumer took the cash. Continue normal transaction processing.


DR01:3F:46:?? One or more bills have Yes been dumped. The last two digits of the status indicated the number of bills dumped.

Not applicable


No

If the problem persists, a service investigation is required.

3.10 ED01 (Encryption/Decryption Status Messages) This section describes the encryption/decryption fault status messages. Refer to Table 3-11 for the encryption/decryption status messages. The device type and number as it appears in the status message is ED01.

Status Message

Table 3-11 ED01 - Encryption/Decryption Status Message Descriptions Sent to Network Description Journal Action On-site Action

ED01:38:00:0F Internal communications error

Yes

Not Service investigation applicable

ED01:39:00:64 General error. This status is used for any error Yes not covered by one of the other status messages.

Not If the problem persists, a applicable service investigation is required.

ED01:39:00:7E Software error. Object creation failed.

Yes


ED01:3F:00:04 PIN format not supported, algorithm not supported, or command not supported

Yes


ED01:3F:00:05 Encryption module is neither ready nor initialized.

Yes


ED01:3F:00:0D Invalid data or no data

Yes


ED01:3F:00:12 The PIN has been cleared.

Yes

Not No action is required. applicable


55/107

21/10/2014


ED01:3F:00:19 Out of memory. Object creation failed.

Yes

ED01:3F:00:1C Invalid key length, or a key with that name already exists and cannot be overwritten.

Yes

ED01:3F:00:1E The terminal attempted to use a nonexistent Yes key, or the number of keys imported exceeded the limit.

Not Service investigation applicable Not Service investigation applicable Not Verify that the keys have been applicable loaded. If the keys have not been loaded, load the keys. If the problem persists, a service investigation is required.

ED01:3F:00:27 Incorect key. The key does not support the specified use.

Yes


ED01:3F:00:56 The PIN block format is not supported, or the Yes minimum length of the PIN exceeds the maximum PIN length.

Not No action is required. applicable

ED01:3F:00:B2 User error


Yes

3.11 EP01 (Encrypting PIN Pad Status Messages) This section describes the encrypting PIN pad (EPP) fault status messages. The device type and number as it appears in the status message is EP01. Refer to Table 3-12 for the EPP fault status messages. Table 3-12 EP01 - EPP Status Message Descriptions Sent to Description Journal Network Action

Status Message

Not applicable

On-site Action

EP01:38:00:0F Internal communications error

Yes


EP01:39:00:1C Key storage error

Yes/Yes Remove terminal from Service investigation service.

EP01:39:00:64 Crypto hardware error


EP01:39:00:7E Internal EPP firmware error


EP01:39:00:A0 EPP key management failure


EP01:3C:00:nn A battery low or alarm status. nn is one hex byte of bit mapped data:


bit 7 - Reserved bit 6 - NVRAM loss of integrity bit 5 - Grid cut bit 4 - Grid over voltage bit 3 - Temperature out of limit - high bit 2 - Temperature out of limit - low bit 1 - Battery low bit 0 - Intrusion latch set Bits 2 through 7 are not set unless bit 0 is set. EP01:3F:00:02 Unknown option


Yes/Yes If the condition persists, remove

Service investigation. Check 56/107

21/10/2014


terminal from service. revision level of EPP. EP01:3F:00:04 Unsupported command

Yes/Yes If the condition Service persists, remove investigation. Check terminal from service. revision level of EPP.

EP01:3F:00:05 Unauthorized command

Yes/Yes If the condition Service persists, remove investigation. terminal from service.

EP01:3F:00:0D Invalid data


EP01:3F:00:0E Checksum mismatch


EP01:3F:00:16 Too little data


EP01:3F:00:17 Too much data


EP01:3F:00:19 Data area is full


EP01:3F:00:27 Incorrect token


EP01:3F:00:70 Invalid version number in ASN.1 structure EP01:3F:00:71 Invalid digest algorithm identifier EP01:3F:00:72 Invalid issuer and serial number structure EP01:3F:00:80 Invalid input parameter to function EP01:3F:00:81 ASN.1 object missing EP01:3F:00:82 Bad formatted ASN.1 structure EP01:3F:00:83 Unknown certificate version (!=3) EP01:3F:00:84 Unknown signature algorithm identifier EP01:3F:00:85 Unsupported string type EP01:3F:00:86 Bad formatted CommonName element EP01:3F:00:87 'Host' or EPP serial number cannot be found in CommonName field in Subject section of the certificate EP01:3F:00:88 Not E or V key types EP01:3F:00:89 No recognized primary or secondary id in certificate EP01:3F:00:8A Cannot change mode in this state: S->P. EP01:3F:00:8B Cannot read from the MPA EP01:3F:00:8C Cannot write to the MPA EP01:3F:00:8D Invalid attribute field EP01:3F:00:8E Key usage not recognized EP01:3F:00:8F PKCS, Encryption algorithm not supported EP01:3F:00:90 Unknown certificate identifier EP01:3F:00:91 Internal problem in generation of certificate request http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

57/107

21/10/2014


EP01:3F:00:92 Bad structure of the validity element or data format not in UTC. PKCS, invalid date or time format EP01:3F:00:93 Structure of public key element incorrect EP01:3F:00:94 Modulus is not as expected an integer element EP01:3F:00:95 Exponent is not as expected an integer element EP01:3F:00:96 Mismatch in data length of OAEP decoding EP01:3F:00:97 The key usage specified is not supported EP01:3F:00:98 The requested certificate is empty EP01:3F:00:99 Signature cannot be verfied EP01:3F:00:9A Mismatch when comparing internal key modulus length with received modulus EP01:3F:00:9B Mismatch when comparing internal key modulus value with received modulus EP01:3F:00:9C Mismatch when comparing internal key exponent value with received modulus EP01:3F:00:9D Unknown host serial number EP01:3F:00:9E Mismatch between own random number received or bad length of field EP01:3F:00:9F PKCS msg#2, bad message digest EP01:3F:00:A1 Mismatch in calculated pHash and given value EP01:3F:00:A2 Invalid key index EP01:3F:00:A3 Invalid OAEP padding EP01:3F:00:A4 RSA decryption error, passed from the RSA system EP01:3F:00:A5 Length of DES KTK is different from 8 or 16 bytes EP01:3F:00:A6 Key block format error EP01:3F:00:A7 Input length too short or too long EP01:3F:00:A8 The key structure type is invalid EP01:3F:00:A9 The specified modulus length cannot be handled EP01:3F:00:AA The specified exponent length cannot be handled EP01:3F:00:AB The value of the public exponent is invalid EP01:3F:00:AC The public exponent is not invertible modulo n EP01:3F:00:AD Length of message is illegal EP01:3F:00:AE Message size is NOT less than modulus EP01:3F:00:AF Modulus too short EP01:3F:00:B0 Flash PROM is not erased EP01:3F:00:B1 Flash PROM is not programmable EP01:3F:00:B2 Command Sequence error EP01:3F:00:B3 Flash PROM programming error EP01:3F:00:C0 Stuck key detected EP01:3F:00:C1 EPP API already locked http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

58/107

21/10/2014


EP01:3F:00:D0 GIE-CB Command Sequence error EP01:3F:00:D1 A certificate check has failed

3.12 EX01 (Signage Unit Status Messages) This section describes the signage unit fault status messages. The device type and number as it appears in the status message is EX01. Refer to Table 3-13 for the signage unit fault status messages. Table 3-13 EX01 - Signage Unit Status Message Descriptions Sent to Description DAL/Journal

Status Message

EX01:38:nn:nn Communications problem

Network Action

On-site Action

No/No

N/A

N/A

EX01:3E:00:00 Network fault - attempted to perform a EXO operation with No/No the device turned off.

N/A

N/A

[1]

[1] nn

can be any number

3.13 EX02 (Safe Door Solenoid Status Messages) This section describes the safe door solenoid fault status messages. The device type and number as it appears in the status message is EX02. Refer to Table 3-14 for the chest door solenoid fault status messages. Table 3-14 EX02 - Safe Door Solenoid Status Message Descriptions Status Message

Description

EX02:3E:00:00 Network fault - attempted to perform a safe door operation with the device turned off.

Sent to DAL/Journal No/No

Network Action

Onsite Action

Check the device properties to see if it is on. N/A If it is not, turn it on and repeat the function. If it is on, check the function for correctness.

3.14 KE01 (Consumer Keypad Status Messages) This section describes the consumer keypad fault status messages. The device type and number as it appears in the status message is KE01. Refer to Table 3-15 for the consumer keypad fault status messages. Table 3-15 KE01 - Consumer Keypad Status Message Descriptions Sent to Network Description Journal Action On-site Action

Status Message

KE01:3F:00:C0 Stuck key. This status is sent every Yes five minutes until the key is no longer stuck.

Remove the terminal from service.

Check for a stuck key. If the problem persists, a service investigation is required.

Initiate the onsite action.

3.15 LCD Failure Detection Device (LFD) This section describes the LCD Failure Detection Device (LFD) fault status messages. The device type and number as it appears in the status message is LC01. Refer to Table 3-16 for the LCD Failure Detection Device (LFD) fault status messages. Table 3-16 LC01 - LCD Failure Detection Device (LFD) Status Message Descriptions Sent to On-site Status Description Journal Network Action Action LC01:3A:31:01

LCD temperature is greater than 65C.

Yes

If persistent begin Service service investigation investigation

LC01:3A:31:02

LCD temperature is less than 0C.

Yes



59/107

21/10/2014


LC01:3A:32:01

Voltage (5V or 3.3V) is high by more than 10%.

Yes


LC01:3A:32:02

Voltage (5V or 3.3V) is low by more than 10%.

Yes


LC01:3A:33:xx where xx is bit mapped using bits 0-6 to indicate which inverter malfunctioned

LCD Inverter malfunction

Yes


LC01:3C:34:01

At least one of the following colors Yes was not displayed properly: Black, White, Blue, Red, Green.


LC01:3C:34:02

No colors are being displayed.

Yes


LC01:3C:35:01

LCD display is not as bright as it should be.

Yes


LC01:3C:35:03

Timeout

Yes


LC01:3A:36:01

Video signal is missing.

Yes

Take terminal out of Service service and begin investigation service investigation

LC01:3A:37:01

LCD temperature protection is activated.

Yes


LC01:3A:90:xx

LCD AMI reported an unknown error.

Yes


LC01:3A:91:00

LCD Self Test command was not able to be executed.

Yes


LC01:38:00:00

Comm fault on power up. Device did not go online after 2 minutes.

Yes


LC01:38:00:01

Could not establish connection with AMI but devices is on line.

Yes


LC01:38:00:02

Device went offline after being online.

Yes


LC01:38:00:03

Device reported a fault but there were no status entities were returned.

Yes


3.16 LT01 (Indicators and Contacts Status Messages) This section describes the indicators and contacts fault status messages. The device type and number as it appears in the status message is LT01. Refer to Table 3-17 for the indicators and contacts fault status messages. Table 3-17 LT01 - Indicators and Contacts Status Message Descriptions Status Message Description Sent to Journal Network Action On-site Action LT01:38:00:00

Internal communications error Yes

TBD


3.17 PF01 (PIN/FIT Status Messages) This section describes the PIN/FIT fault status messages. The device type and number as it appears in the status message is PF01. Refer to Table 3-18 for the PIN/FIT status messages.

Status message

Table 3-18 PIN/FIT Status Message Descriptions Sent to Description DAL/Journal Network Action


On-site Action 60/107

21/10/2014


PF01:38:00:0F Communications problem

Yes/Yes

If the condition persists, remove terminal from service.


PF01:39:00:1C Key storage error

Yes/Yes

Remove terminal from service.


PF01:39:00:64 Crypto hardware error

Yes/Yes



PF01:39:00:7E Internal EPP firmware error

Yes/Yes



PF01:39:00:A0 EPP key management failure

Yes/Yes



PF01:3F:00:02 Unknown option

Yes/Yes


Service Investigation. Check revision level of EPP.

PF01:3F:00:04 Unsupported command

Yes/Yes


Service Investigation. Check revision level of EPP.

PF01:3F:00:05 Unauthorized command

Yes/Yes


Service investigation.

PF01:3F:00:0D Invalid data

Yes/Yes



PF01:3F:00:0E Checksum mismatch

Yes/Yes



PF01:3F:00:12 Sequence error

Yes/Yes

Check that customer has entered PIN before it is verified or a PIN buffer is created.

None

PF01:3F:00:16 Too little data

Yes/Yes



PF01:3F:00:17 Too much data

Yes/Yes



PF01:3F:00:19 Data area is full

Yes/Yes



PF01:3F:00:1A Key parity error. An attempt was Yes/Yes made to use a non-parity adjusted key (PEKEY) or down-load a nonparity adjusted key (write command VII).

Check that correct DES keys are None loaded at terminal before DES keys are sent in the FIT (PEKEY). Adjust the parity of the key if required by the device.

PF01:3F:00:1E Invalid key. An attempt was made to use a nonexistent key.

Yes/Yes

Remove terminal from service. Check DES keys are loaded at terminal.

None

PF01:3F:00:27 Incorrect token

Yes/Yes



PF01:3F:00:50 Invalid format control or input mode Yes/Yes

Check FIT for proper data. If None condition persists, remove terminal from service.

PF01:3F:00:51 Invalid PIN format

Yes/Yes


PF01:3F:00:54 Decimalization table error. Possible Yes/Yes problem in FIT decimalization table.

Check decimalization table in FIT. None

PF01:3F:00:55 Generation data error

Check FIT for proper data. If None condition persists, remove terminal

Yes/Yes


61/107

21/10/2014


from service. PF01:3F:00:56 PIN formatting failure or PIN length Yes/Yes

Check that customer has entered None a PIN with a minimum of 4 digits before it is verified or a PIN buffer is created. (Use PANLN in FIT to specify PIN length check).

PF01:3F:00:57 PIN block consistency check error Yes/Yes


PF01:3F:00:A2 Illegal key data index

Yes/Yes

If condition persists, remove terminal from service.


PF01:3F:00:C1 EPP API already locked

Yes/Yes

If condition persists, remove terminal from service.


3.18 PB01 (Passbook Printer Status Messages) (Opteva only) This section describes the Passbook Printer fault status messages. Refer to Table 3-19 for the Passbook Printer status messages. The device type and number as it appears in the status message is PB01.

Status Message

Table 3-19 PB01 - Passbook Printer Status Message Descriptions Sent to Network Description DAL/Journal Action On-site Action

PB01:21:00:00 Good operation

yes/yes

None

None

PB01:23:67:81 Timeout - Passbook not taken

yes/yes

None

None

PB01:24:51:81 Passbook failed printing header

Check the integrity of the header data

PB01:24:51:82 Passbook - end of document

Eject the book and turn the page

PB01:24:67:87 Passbook Full

Obtain new passbook

PB01:38:68:88 Comm fault

yes/yes

Take passbook printer out of service


PB01:39:00:00 Passbook is in escrow yes/yes


Remove escrowed book

PB01:3A:40:34 Data error - invalid operation

yes/yes

Ensure the state/function command has valid parameter

PB01:3A:40:35 Unsupported command yes/yes

Ensure the hardware supports the operations required by the command

PB01:3A:41:FF Enable error

yes/yes

Check for a passbook in escrow or retain bin full

PB01:3A:51:FF Print exception

yes/yes

Ensure configuration parameters are correct. Check for jammed, missing, or misaligned passbook in terminal.

PB01:3A:56:FF Shutter error

yes/yes

Check for jammed passbook in terminal.

PB01:3A:5A:FF Present book failure

yes/yes


PB01:3A:5B:FF Retain book failure

yes/yes


PB01:3A:68:FF Comm fault

yes/yes




62/107

21/10/2014


PB01:3A:71:FF Magnetic stripe read error PB01:3A:72:FF Magnetic stripe write error

yes/yes yes/yes

PB01:3A:81:FF Page number bar code yes/yes read error

Check the integrity of the bar code marks

PB01:3A:82:FF Line number optical sensing error

yes/yes

Check for proper LPI setting and passbook compatibility with this feature. Check for adequate print contrast.

PB01:3A:91:FF Automatic page turn error

yes/yes

Check for jammed, misaligned, or missing passbook

PB01:3E:40:34 Data error - invalid operation

yes/yes

Ensure the state/function command has valid parameter

PB01:3E:40:35 Unsupported command yes/yes

Ensure the hardware supports the operations required by the command

PB01:3E:41:FF Enable error

yes/yes

Check for a passbook in escrow or retain bin full

PB01:3E:51:71 Print exception

yes/yes

PB01:3E:51:FF Print exception

yes/yes

Ensure configuration parameters are correct. Check for jammed, missing, or misaligned passbook in terminal.

PB01:3E:56:FF Shutter error

yes/yes


PB01:3E:5A:FF Present book failure

yes/yes


PB01:3E:5B:FF Retain book failure

yes/yes


PB01:3E:68:FF Comm fault

yes/yes

PB01:3E:71:FF Magnetic stripe read error

yes/yes

PB01:3E:72:FF Magnetic stripe write error

yes/yes





PB01:3E:81:FF Page number bar code yes/yes read error

Check the integrity of the bar code marks

PB01:3E:82:FF Line number optical sensing error

yes/yes

Check for proper LPI setting and passbook compatibility with this feature. Check for adequate print contrast.

PB01:3E:91:FF Automatic page turn error

yes/yes

Check for jammed, misaligned, or missing passbook

PB01:3F:43:83 Purge book error


Check printer for jammed passbook

PB01:3F:53:85 State query sensor error

yes/yes



PB01:3F:56:77 Open gate error

yes/yes




63/107

21/10/2014


PB01:3F:57:78 Close gate error

yes/yes

Take passbook printer out of service Take passbook printer out of service


PB01:3F:5A:81 Present book error

yes/yes

PB01:3F:5B:82 Retain book error

yes/yes



PB01:3F:5C:77 Selftest - feed motor error

yes/yes



PB01:3F:5C:78 Selftest - print head motor error

yes/yes



PB01:3F:5C:7B Selftest - platen error

yes/yes



PB01:3F:5C:7C Selftest - inserter error yes/yes



PB01:3F:5D:70 Abnormal medium length

Reset passbook printer

None

PB01:3F:5D:71 Conditional check, data format, or LCU protocol error

Reset passbook printer

None







PB01:3F:5D:72 Hardware error

PB01:3F:67:81 Wait book error

yes/yes

PB01:3F:68:46 Reset - error

Check printer for jammed book

3.19 Power-up / SYS Status Messages This section describes the power-up/SYS fault status messages. A power-up message is identified by four asterisks ( **** ) before the status message. Refer to Table 3-20 for the power-up/SYS fault status messages. Table 3-20 Power-up Status Message Descriptions Status Message

Description

****:3E:00:00 The terminal's power switch was turned on, or power returned after a power failure. The battery backed-up data is no longer valid. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

Sent to Network Journal Action Yes

On-site Action

Not No action applicable is 64/107

21/10/2014


required. ****:3F:00:00 Power returned after a power failure. The battery backed-up data is still Yes valid.

Not No action applicable is required.

3.20 PR01 (Receipt Printer Status Messages) This section describes the receipt printer fault status messages. The device type and number as it appears in the status message is PR01. Refer to Table 3-21 for the receipt printer status messages.

Status Message

Table 3-21 PR01 - Receipt Printer Status Message Descriptions Sent to Description Journal Network Action On-site Action

PR01:00:00:00 The receipt printer performed a Yes self-test, and no errors occurred.

Not applicable


PR01:23:00:00 Consumer timeout. The receipt Yes was presented to the consumer, but the consumer did not take the receipt.

Clear the receipt No action is required. printer by retaining or dumping the receipt. Continue normal transaction processing.

PR01:2D:50:00 Supply of paper is running low. Yes

Continue normal transaction processing.

Replenish the supply of paper.

Initiate the on-site action. PR01:30:??:?? The receipt printer rejected a command.

Yes

PR01:38:23:30 The receipt printer failed to Yes respond to a command (reset device) within the allotted time.

PR01:38:23:31 The receipt printer failed to Yes respond to a command (idle device) within the allotted time.

PR01:38:23:34 The receipt printer failed to respond to a command (return device configuration data)

Yes




If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation is required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation is required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions,

Restart the terminal software. If the problem persists, a service 65/107

21/1 21/10/ 0/20 2014 14


within the allotted time.

remove the investigation investi gation is required required.. terminal from service. If the terminal remains remains in service, discontinue using the receipt printer.

PR01:38:23 PR01:38:23:37 :37 The receipt receipt printer printer failed to Yes respond to a command (return device device ROM CRCs) CRC s) within the allotted time.

Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action.

PR01:38 PR01:38:30 :30:?? :?? During During the the initializatio initialization n of the receipt printer, the t he printer responded to a command (reset device) with an invalid completion status.

PR01:38 PR01:38:31 :31:?? :?? During During the the initializatio initialization n of the receipt printer, the t he printer responded to a command (idle device) with an invalid completion status.

Yes

Yes

PR01:38 PR01:38:34 :34:?? :?? During During the the initializatio initialization n of the Yes receipt printer, the t he printer responded to a command (return (return device devic e configur c onfiguration ation data) with an invalid completion status.

If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site


66/107

21/1 21/10/ 0/20 2014 14


action. PR01:38 PR01:38:37 :37:?? :?? During During the the initializatio initialization n of the receipt printer, the t he printer responded to a command (return device ROM CRCs) with an invalid completion status.

Yes

PR01:38:51 PR01:38:51:?? :?? The receipt receipt printer printer is not not Yes communicating with Agilis 91x.

PR01:38:60 PR01:38:60:?? :?? The receipt receipt printer printer failed to initialize.

Yes

PR01:38:62 PR01:38:62:?? :?? The receipt receipt printer printer is not not Yes communicating with Agilis 91x.

PR01:38:?? PR01:38:??:?? :?? The receipt receipt printer printer failed to respond to a command within the allotted time.

Yes


If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Restart the terminal software. required for If the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains remains in

Check the receipt printer cables for a loose connection. Restart the terminal software. If the problem persists, a service investigation investi gation is required required..

67/107

21/1 21/10/ 0/20 2014 14


service, discontinue using the receipt printer.

PR01:39:40:01 Hardware error

PR01:39:40 PR01:39:40:02 :02 The receipt receipt printe printerr detected detected a voltage error and has failed to complete the operation

PR01:39:40 PR01:39:40:04 :04 The receipt receipt printe printerr detected detected a print head unlocked error and has failed to complete the operation

Yes

Initiate a service investigation. If receipts are required for transactions, remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer.

Check for a paper jam or other blockage in the receipt printer. If the problem persists, a service investigation investi gation is required required..

Initiate the on-site action. Yes/Yes Yes/Yes If rece receipts ipts are are Power the terminal off and back on. If required for the problem persists, a service transactions, investigation investi gation is required required.. remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer. Initiate the on-site action. Yes/Yes Yes/Yes If rece receipts ipts are are required for transactions, remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer.

PR01:39:50 PR01:39:50:01 :01 Supply Supply of pape paperr is run runnin ning g low. low. Yes A hardwa hardware re erro errorr might might have have occurred at the same time.

Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains remains in service, discontinue using the receipt printer.

Make sure the printer's hinged hinged cover is in the locked position. If the problem persists, a service investigation investi gation is required required..

Replenish the supply of paper. Check for a paper jam or other blockage in the receipt printer. If the problem persists, a service investigation investi gation is required required..

Initiate the on-site action. PR01:39:50 PR01:39:50:04 :04 The receipt receipt printe printerr detected detected a print head unlocked error and

Yes/Yes Yes/Yes If rece receipts ipts are are required for


Install and new roll of forms and make sure the printer's hinged hinged cover 68/107

21/10/2014


low supplies. It has failed to complete the operation

transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer.

is in the locked position. If the print head unlocked error persists or paper low is reported errantly, a service investigation is required.

Initiate the on-site action. PR01:39:60:01 Supply of paper has run out. A Yes hardware error might have occurred at the same time.

PR01:39:60:04 The receipt printer detected a print head unlocked error and supplies out. It has failed to complete the operation

PR01:3C:42:00 The receipt printer cannot detect a top-of-form mark.

PR01:3D:40:05 The reject bin is full.

PR01:3D:60:00 Supply of paper has run out.

If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer.

Initiate the on-site action. Yes/Yes If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer.

Yes

Yes

Yes


Initiate the on-site action. If the problem is infrequent, action might not be justified. If the problem persists, initiate the on-site action.


Replenish the supply of paper. Check for a paper jam or other blockage in the receipt printer. If the problem persists, a service investigation is required.

Install and new roll of forms and make sure the printer's hinged cover is in the locked position. If the print head unlocked error persists or paper out is reported errantly, a service investigation is required.

Check for a paper jam in the receipt printer. Verify that the paper is loaded correctly, with the top-of-form mark oriented properly. Verify that the TOF parameter is set correctly in the printer device properties. If the problem persists, a service investigation is required. Empty the reject bin. Check for a possible paper jam. If the problem persists, a service investigation is required.

Initiate the on-site action. If receipts are Replenish the supply of paper. 69/107

21/10/2014


required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. PR01:3D:60:0D The retain bin is full or jammed. Yes/Yes Remove the printer Empty the delivery module's retain [1] This status corresponds to from service and bin. Remove any receipts that may Statement Printer status perform the on-site have jammed at the entry of the bin. SP01:3D:00:0D. action. PR01:3E:00:00 1) Self-test failed (operational 1) Yes command processing). The receipt printer is not present or 2) Yes is not enabled.

1) Not applicable

1) No action is required.

2) Not applicable


2) Format error detected in the print data. The most likely cause is an incomplete control sequence or too much print data between line terminators (CR or LF). PR01:3E:00:01 Data error. The data error Yes status could be the result of incorrect print data, an incorrect software device configuration, or a problem with XFS forms and media definitions.

PR01:3E:01:04 Continuous Availability spool Yes file error (too many open files).

PR01:3E:01:05 Continuous Availability spool file error (access denied).

Yes

PR01:3E:01:08 Continuous Availability spool Yes file error (not enough memory).

PR01:3E:01:20 Continuous Availability spool file error (sharing violation).

Yes

If receipts are Service investigation required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate a service investigation. Initiate the on-site action.

Initiate the on-site action.



Close unneeded files and programs. If the problem persists, a service investigation is required. Check the access attributes on the receipt.tmp file. If the problem persists, a service investigation is required. Close unneeded files and programs. If the problem persists, a service investigation is required. Check for an editing program that has the receipt.tmp file open. If the problem persists, a service investigation is required.

PR01:3E:01:70 Continuous Availability spool file error (disk full).

Yes



Increase available disk space by removing or deleting unneeded files. 70/107

21/10/2014


If the problem persists, a service investigation is required. PR01:3E:02:05 The hinged print head is unlocked with the thermal statement printer. This status corresponds to Statement Printer status SP01:3E:00:05.

Yes/Yes Remove the printer Make sure the printer's hinged print from service and head is in the locked position with the perform the on-site thermal statement printer. action.

PR01:3E:02:06 The ribbon switch indicates [1] that the ribbon cartridge is missing. This status corresponds to Statement Printer status SP01:3E:00:06.

Yes/Yes Remove the printer Verify that the ribbon cartridge is from service and properly installed and the hinge lid is perform the on-site fully closed. If the fault is repetitive, action. service is required.

PR01:3E:02:07 There is a delivery module Yes/Yes If the fault is [1] positioning fault. There may be repetitive, remove a paper jam in the Delivery the printer from Module. This status operation and call corresponds to Statement service. Printer status SP01:3E:00:07.

Clear any paper jams in the delivery module. If the fault is repetitive, service is required.

PR01:3E:02:0A There may be a paper jam in the delivery module. This status corresponds to Statement Printer status SP01:3E:00:0A.

Yes/Yes Remove the printer Clear any paper jams beneath the from service and delivery module's sensors. If the fault perform the on-site is repetitive, service is required. action.

PR01:3E:02:0E The cutter has failed or the paper is out. This status corresponds to statement printer status SP01:3A:00:0E.

Yes/Yes If the fault is A possible cutter failure or paper jam. repetitive, remove Confirm the cutter operation by the printer from printing a test form. If the fault still operation and call exists, service is required. service.

PR01:3E:10:01 Data error. A paper supply low Yes condition occurred at the same time. The data error status could be the result of incorrect print data, an incorrect software device configuration, or a problem with XFS forms and media definitions.

PR01:3E:20:01 Data error. A paper supply out Yes condition occurred at the same time. The data error status could be the result of incorrect print data, an incorrect software device configuration, or a problem with XFS forms and media definitions.

If receipts are Replenish the supply of paper. required for Also, a service investigation is transactions, required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Replenish the supply of paper. required for Also, a service investigation is transactions, required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action.

PR01:3E:40:03 The receipt printer detected a print head overheat error and has failed to complete the operation

Yes/Yes Leave the terminal None in service. The printer will continue to operate, slower,


71/107

21/10/2014


in a degraded mode. If the error persists, a service investigation is required. PR01:3E:40:03 The receipt printer detected a print head overheat error and has failed to complete the operation

Yes/Yes Leave the terminal None in service. The printer will continue to operate, slower, in a degraded mode. If the error persists, a service investigation is required.

PR01:3E:40:06 Dump error. The receipt might not have been dumped.

Yes

PR01:3E:40:07 Paper jam

Yes

PR01:3E:40:08 Deliver error. The receipt might Yes not have been delivered to the consumer.

PR01:3E:40:09 Cut error. The receipt might not Yes have been delivered to the consumer.


If receipts are Check for a paper jam in the receipt required for printer. If the problem persists, a transactions, service investigation is required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Check for a paper jam in the receipt required for printer. If the problem persists, a transactions, service investigation is required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Check for a paper jam in the receipt required for printer. If the problem persists, a transactions, service investigation is required. remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are Check for a paper jam. If the problem required for persists, a service investigation is transactions, required. remove the terminal from service. If the terminal remains in 72/107

21/10/2014


service, discontinue using the receipt printer.

PR01:3E:50:03 The receipt printer detected a print head overheat error and low supplies. It has failed to complete the operation

PR01:3E:50:06 Dump error. The receipt might not have been dumped. A paper supply low condition occurred at the same time.

Initiate the on-site action. Yes/Yes Leave the terminal in service. The printer will continue to operate, slower, in a degraded mode. Initiate onsite action. Yes


Install and new roll of forms. If the print head overheat error persists or paper low is reported errantly, a service investigation is required.

Replenish the supply of paper. Check for a paper jam in the receipt printer. If the problem persists, a service investigation is required.

Initiate the on-site action. PR01:3E:50:07 Paper jam. A paper supply low Yes condition occurred at the same time.

PR01:3E:50:08 Deliver error. The receipt might Yes not have been delivered to the consumer. A paper supply low condition occurred at the same time.

PR01:3E:50:09 Cut error. The receipt might not Yes have been delivered to the consumer. A paper supply low condition occurred at the same time.


If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains in service,



Replenish the supply of paper. Check for a paper jam. If the problem persists, a service investigation is required.

73/107

21/10/2014


discontinue using the receipt printer. Initiate the on-site action. PR01:3E:60:03 The receipt printer detected a print head overheat error and supplies out. It has failed to complete the operation

PR01:3E:60:06 Dump error. The receipt might not have been dumped. A paper supply out condition occurred at the same time.

Yes/Yes If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer.

Yes

PR01:3E:60:07 Paper jam. A paper supply out Yes condition occurred at the same time.

PR01:3E:60:08 Deliver error. The receipt might Yes not have been delivered to the consumer. A paper supply out condition occurred at the same time.

Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action. If receipts are required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the receipt printer.

Install and new roll of forms. If the print head overheat error persists or paper out is reported errantly, a service investigation is required.




Initiate the on-site action. PR01:3E:60:09 Cut error. The receipt might not Yes have been delivered to the http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

If receipts are required for

Replenish the supply of paper. Check for a paper jam. If the problem 74/107

21/10/2014


consumer. A paper supply out condition occurred at the same time.

transactions, persists, a service investigation is remove the required. terminal from service. If the terminal remains in service, discontinue using the receipt printer. Initiate the on-site action.

PR01:3F:00:03 Corrupted print data

Yes

If the problem No action is required. persists, a service investigation is required.

PR01:3F:00:08 A document was not found Yes/Yes If the fault is during the presentation repetitive, remove attempt. There is a possible the printer from sequence error, paper jam in operation and call the delivery module, or sensor service. failure. This status corresponds to statement printer status SP01:3F:00:08.

Clear any jams. If the fault is repetitive, call service.

PR01:3F:00:0B Difficulty locating the top-ofYes/Yes If the fault is [1] form marks on the paper. The repetitive, remove printer settings may not match the printer from the actual form. The form operation and call lengths may be incorrectly cut. service. This status corresponds to statement printer status SP01:3F:00:0B.

Verify that the actual top-of-form marks match the statement printer settings. The settings can be checked in Maintenance mode using the Edit Device Parameters command in the Installation menu. Correct any settings that do not match the actual form. If the fault persists, call service.

PR01:3F:00:0F The midway sensor is not operating. This status corresponds to statement printer status SP01:3F:00:0F.

Yes/Yes Schedule service. The statement printer can be operated in the degraded mode.

Verify proper operation of the midway sensor using Maintenance diagnostics.

PR01:3F:00:10 Document not found during [1] retain operation. Possible jam or sequence error caused by consumer removing jam. This message corresponds to statement printer status SP01:3F:00:10

Yes/Yes If the fault is Clear delivery area for a possible repetitive, call jam. If repetitive, verify proper service. This fault operation of the midway sensor using may be sent as Maintenance diagnostics . part of a terminal software attempt to automatically clear a sequence fault.

PR01:3F:23:30 The receipt printer failed to Yes respond to a command (reset device) within the allotted time.


PR01:3F:23:31 The receipt printer failed to Yes respond to a command (idle device) within the allotted time.


PR01:3F:23:34 The receipt printer failed to respond to a command (return device configuration data) within the allotted time.


Yes


75/107

21/10/2014


PR01:3F:23:37 The receipt printer failed to Yes respond to a command (return device ROM CRCs) within the allotted time. PR01:3F:23:41 The receipt printer failed to Yes respond to a command (print on device) within the allotted time.

If the problem No action is required. persists, a service investigation is required. If the problem No action is required. persists, a service investigation is required.

PR01:3F:23:42 The receipt printer failed to Yes respond to a command (enable paper advance button on printer) within the allotted time.


PR01:3F:23:43 The receipt printer failed to respond to a command (burst and deliver form) within the allotted time.

Yes


PR01:3F:23:45 The receipt printer failed to Yes respond to a command (move to top of form, burst and deliver form) within the allotted time.


PR01:3F:23:47 The receipt printer failed to respond to a command (retain form) within the allotted time.

Yes


PR01:3F:23:48 The receipt printer failed to respond to a command (dump form) within the allotted time.

Yes


PR01:3F:40:0A There is no receipt for the Yes receipt printer to deliver. The printer might have attempted a deliver operation before performing a print operation.



PR01:3F:40:0B There is no receipt for the Yes receipt printer to retain. The consumer might have taken the receipt before the printer could retain it, or the printer might have attempted a retain operation before performing a print operation.



PR01:3F:40:40 Unexpected or unknown fault

Yes

If the problem No action is required. persists, discontinue using the receipt printer, and initiate a service investigation.

PR01:3F:40:60 A document retain command [1] was automatically done. The presented documents have been retained.

Yes/Yes The network No action required should be aware that the consumer may not have taken the document.

PR01:3F:40:61 A document dump was performed automatically.

Yes


Continue normal transaction processing. Note


76/107

21/10/2014


that the consumer might not have received a receipt. PR01:3F:??:?? The receipt printer responded No to a command with an invalid completion status. The format is :3F:xx:yy, where xx represents the command code, and yy represents the completion status code.


Not applicable

The valid command codes are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device ROM CRCs41 - print on device 42 - enable paper advance button on printer 43 - burst and deliver form 45 - move to top of form, burst and deliver form 47 - retain form 48 - dump form The valid completion status codes are as follows: 31 - device idling34 - device configuration data 37 - device ROM CRCs 39 - device hard fault 3E - device fault 3F - device warning 41 - print command completed 42 - paper advance button enabled 43 - form burst and delivered 45 - TOF search, burst, and deliver completed 47 - form retained 48 - form dumped [1]

This status message is not applicable to the thermal statement printer when emulating a receipt printer.

3.21 PR02 (Journal Printer Status Messages) This section describes the journal printer fault status messages. The device type and number as it appears in the status message is PR02. Refer to Table 3-22 for the journal printer status messages.

Status Message

Table 3-22 PR02 - Journal Printer Status Message Descriptions Sent to Description Journal Network Action On-site Action

PR02:00:00:00 The journal performed a self-test, Yes and no errors occurred.

Not applicable


PR02:2D:50:00 Supply of paper is running low.

Yes



PR02:30:??:?? The journal printer rejected a

Yes




77/107

21/10/2014


command. PR02:38:23:30 The journal printer failed to respond to a command (reset device) within the allotted time.

PR02:38:23:31 The journal printer failed to respond to a command (idle device) within the allotted time.

No

No

If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.

Restart the terminal software. If the problem persists, a service investigation is required.


Initiate the on-site action. PR02:38:23:34 The journal printer failed to No respond to a command (return device configuration data) within the allotted time.

PR02:38:23:37 The journal printer failed to respond to a command (return device ROM CRCs) within the allotted time.

PR02:38:30:?? During the initialization of the journal printer, the printer responded to a command (reset device) with an invalid completion status.

No

No

If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.




Initiate the on-site action. PR02:38:31:?? During the initialization of the journal printer, the printer responded to a command (idle device) with an invalid

No


If a printed journal is required for transactions, remove the terminal from

Restart the terminal software. If the problem persists, a service investigation is 78/107

21/10/2014


completion status.

service. If the terminal remains in service, discontinue using the journal printer.

required.

Initiate the on-site action. PR02:38:34:?? During the initialization of the No journal printer, the printer responded to a command (return device configuration data) with an invalid completion status.

PR02:38:37:?? During the initialization of the No journal printer, the printer responded to a command (return device ROM CRCs) with an invalid completion status.

PR02:38:51:?? The journal printer is not communicating with Agilis 91x.

PR02:38:60:?? The journal printer failed to initialize.

PR02:38:62:?? The journal printer is not communicating with Agilis 91x.

No

No

No


If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.






79/107

21/10/2014


PR02:38:??:?? Internal communications error. The journal printer did not respond within the allotted time.

No

Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.

Check the journal printer cables for a loose connection. Restart the terminal software. If the problem persists, a service investigation is required.

Initiate a service investigation. PR02:39:40:01 Flash error

No

If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.

Initiate a service investigation. PR02:39:40:04 The journal printer detected a Yes/Yes Take the ATM out of print head unlocked error and has service if journal record failed to complete the operation. of transaction is required. If the ATM is left in-service, discontinue using the printer. Initiate the onsite action. PR02:39:44:00 Hardware error

No


Initiate a service investigation. PR02:39:50:04 The journal printer detected a Yes/Yes Take the ATM out of print head unlocked error and low service if journal record supplies. It has failed to of transaction is complete the operation. required. If the ATM is left in-service, discontinue using the printer. Initiate the onsite action. PR02:39:50:07 The journal printer detected a jam and low supplies. It has failed to complete the operation.

Check the journal printer cables for a loose connection. Restart the terminal software. If the problem persists, a service investigation is required.

Make sure the printer's hinged cover is in the locked position. If the error persists, a service investigation may be required.


Install a new roll of forms and make sure the printer's hinged cover is in the locked position. If the print head unlocked error persists or paper low is reported errantly, a service investigation may be required.

Yes/Yes Take the ATM out of Install a new roll of forms and service if journal record inspect for a possible paper of transaction is jam. If the jam error persists or required. If the ATM is paper low is reported errantly, a left in-service, service investigation may be discontinue using the required. printer. Initiate the onsite action.


80/107

21/10/2014


PR02:39:54:00 Supply of paper is running low. A No hardware error might have occurred at the same time.


Replenish the supply of paper. Check for a paper jam or other blockage in the journal printer. If the problem persists, a service investigation is required.

Initiate the on-site action. PR02:39:60:04 The journal printer detected a print head unlocked error and supplies out. It has failed to complete the operation.

Yes/Yes Take the ATM out of service if journal record of transaction is required. If the ATM is left in-service, discontinue using the printer. Initiate the onsite action.

PR02:39:50:07 The journal printer detected a jam and supplies out. It has failed to complete the operation.

Yes/Yes Take the ATM out of Install a new roll of forms and service if journal record inspect for a possible paper of transaction is jam. If the jam error persists or required. If the ATM is paper out is reported errantly, a left in-service, service investigation may be discontinue using the required. printer. Initiate the onsite action.

PR02:39:64:00 Supply of paper has run out. A hardware error might have occurred at the same time.

No

PR02:3D:60:00 Supply of paper has run out.

No

PR02:3E:00:00 1) Self-test failed (operational 1) No command processing). The receipt printer is not present or is 1) No not enabled.

If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer. Initiate the on-site action. If a printed journal is required for transactions, remove the terminal from service. If the terminal remains in service, discontinue using the journal printer.

Install a new roll of forms and make sure the printer's hinged cover is in the locked position. If the print head unlocked error persists or paper out is reported errantly, a service investigation may be required.



Initiate the on-site action. 1) Not applicable


2) Not applicable


2) Format error detected in the print data. The most likely cause is an incomplete control sequence or too much print data between line terminators (CR or LF). http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

81/107

21/10/2014


PR02:3E:00:01 Data error. The data error status No could be the result of incorrect print data, an incorrect software device configuration, or a problem with XFS forms and media definitions.



Initiate a service investigation. PR02:3E:01:04 Continuous Availability spool file No error (too many open files).

PR02:3E:01:05 Continuous Availability spool file No error (access denied).

PR02:3E:01:08 Continuous Availability spool file No error (not enough memory).

PR02:3E:01:20 Continuous Availability spool file No error (sharing violation).

PR02:3E:01:70 Continuous Availability spool file No error (disk full).


Close unneeded files and programs.


If the problem persists, a service investigation is required. Check the access attributes on the journal.tmp file.


If the problem persists, a service investigation is required. Close unneeded files and programs.



PR02:3E:40:03 The journal printer detected a Yes/Yes Leave the terminal in print head overheat error and has service. The printer will failed to complete the operation continue to operate, slower, in a degraded mode. If the error persists, a service investigation is required. PR02:3E:40:07 Paper jam

No


If the problem persists, a service investigation is required. Check for an editing program that has the journal.tmp file open. If the problem persists, a service investigation is required. Increase available disk space by removing or deleting unneeded files. If the problem persists, a service investigation is required. None

If a printed journal is Check for a paper jam in the required for journal printer. If the problem transactions, remove persists, a service investigation the terminal from is required. service. If the terminal remains in service, discontinue using the journal printer. 82/107

21/10/2014


Initiate the on-site action. PR02:3E:50:03 The receipt printer detected a Yes/Yes Leave the terminal in print head overheat error and low service. The printer will supplies. It has failed to continue to operate, complete the operation slower, in a degraded mode. If the error persists, a service investigation is required.

Install a new roll of forms. If the print head overheat error persists or paper low is reported errantly, a service investigation is required.

PR02:3E:50:07 Paper jam. A paper supply low condition occurred at the same time.

Replenish the supply of paper. Check for a paper jam or other blockage in the journal printer.

PR02:3E:60:03 The receipt printer detected a print head overheat error and supplies out. It has failed to complete the operation

PR02:3E:60:07 Paper jam. A paper supply out condition occurred at the same time.

No


Initiate the on-site action. Yes/Yes Leave the terminal in service. The printer will continue to operate, slower, in a degraded mode. If the error persists, a service investigation is required. No


If the problem persists, a service investigation is required.

Install a new roll of forms. If the print head overheat error persists or paper out is reported errantly, a service investigation is required.


Initiate the on-site action. If the problem persists, No action is required. a service investigation is required.

PR02:3F:00:03 Corrupted print data

No

PR02:3F:23:30 The journal printer failed to respond to a command (reset device) within the allotted time.

No

If the problem persists, No action is required. a service investigation is required.

PR02:3F:23:31 The journal printer failed to respond to a command (idle device) within the allotted time.

No


PR02:3F:23:34 The journal printer failed to No respond to a command (return device configuration data) within the allotted time.


PR02:3F:23:37 The journal printer failed to respond to a command (return device ROM CRCs) within the allotted time.

No


PR02:3F:23:41 The journal printer failed to

No

If the problem persists, No action is required.


83/107

21/10/2014


respond to a command (print on device) within the allotted time.

a service investigation is required.

PR02:3F:23:42 The journal printer failed to No respond to a command (enable paper advance button on printer) within the allotted time.


PR02:3F:23:43 The journal printer failed to respond to a command (burst and deliver form) within the allotted time.

No


PR02:3F:23:45 The journal printer failed to No respond to a command (move to top of form, burst and deliver form) within the allotted time.


PR02:3F:40:40 Unexpected or unknown fault

If the problem persists, No action is required. discontinue using the journal printer and initiate a service investigation.

No

PR02:3F:??:?? The journal printer responded to No a command with an invalid completion status. The format is :3F:xx:yy, where xx represents the command code, and yy represents the completion status code.


Not applicable

The valid command codes are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device ROM CRCs41 - print on device 42 - enable paper advance button on printer 43 - burst and deliver form 45 - move to top of form, burst and deliver form The valid completion status codes are as follows: 31 - device idling 34 - device configuration data 37 - device ROM CRCs 39 - device hard fault 3E - device fault 3F - device warning 41 - print command completed 42 - paper advance button enabled 43 - form burst and delivered 45 - TOF search, burst, and deliver completed

3.22 PR03 (Electronic Data Capture Status Messages) http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

84/107

21/10/2014


This section describes the electronic data capture (EDC) fault status messages. The device type and number as it appears in the status message is PR03. Refer to Table 3-23 for the EDC fault status messages.

Status Message

Table 3-23 PR03 - EDC Status Message Descriptions Sent to Description Journal Network Action

On-site Action

PR03:00:00:00 EDC performed a self-test, and no Yes errors occurred.

Not applicable

PR03:2D:50:40 EDC detected a Disk Low condition. At this point, 100 more records can be written.

Yes

If EDC is required for Install a formatted disk. transactions, remove the terminal from service. If the terminal remains in service, discontinue using EDC until a formatted disk has been installed.

PR03:30:??:?? EDC rejected a command. The format is :30:yy:xx, where the command rejected is yy and the reason code is xx.

Yes

Not applicable

The valid yy commands are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device CRCs 41 - print on device 42 - enable paper advance button on printer43 - burst and deliver form 45 - move to top of form, burst, and deliver form


For status code :30:41:34 verify that the data sent to the terminal is correct and contains only valid printable characters. For any other printer command reject status, leave the terminal in-service but initiate a service investigation.

The valid xx reason codes are as follows: 30 - invalid command for a printer device 31 - command received out of sequence 32 - device buffer overflow33 printer device ID is incorrect 34 - data format error PR03:38:23:?? EDC failed to respond to a No command (represented by the last two digits of the status) within an expected period for five consecutive times during initialization of the device. Four :3F:23:?? faults should have already been logged.

If EDC is required for Service investigation transactions, remove the terminal from service. If the terminal remains in service, discontinue using EDC.

The valid commands are as follows: 30 - reset device 31 - idle device34 - return device http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

85/107

21/10/2014


configuration data 37 - return device ROM CRCs PR03:38:60:?? Internal communications error

No


PR03:38:62:?? EDC is not communicating with the system communications handler.

No


PR03:38:64:?? EDC is continually rejecting commands (NAKing).

No


PR03:38:??:?? During the initialization of EDC, the device responded to a command with an invalid completion status. The format is :38:yy:zz, where the command that was issued is yy and the invalid completion status is zz.

No


The valid yy commands are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device ROM CRCs. The possible zz invalid completion codes are as follows: 31 - device idling 34 - device configuration data 37 - device ROM CRCs39 device hard fault 3F - device warning fault 41 - print command completed 42 - paper advance button enabled 43 - form burst and delivered 45 - TOF search, burst, and deliver completed PR03:39:44:40 EDC reported an operating system Yes fatal error when it attempted to access the EDC diskette.


If EDC is required for Service investigation transactions, remove the terminal from service. If the terminal remains in service, discontinue using EDC until the terminal 86/107

21/10/2014


has been serviced. PR03:3D:40:46 File does not exist (no local data Yes file to archive; response to archive command)



PR03:3D:40:47 Unable to access file (max archives [10] performed for the day)

Yes


Delete some of the older files.

PR03:3D:40:48 Timeout (file locked by another process)

Yes



PR03:3D:40:49 Archive command disabled (user- Yes specified local data file enabled in EDCOPTN)



PR03:3D:50:40 EDC detected a Disk Out condition.

Yes


PR03:3D:60:40 EDC detected a Disk Full condition.

Yes


PR03:3D:60:41 There is no diskette in the EDC drive.

Yes


PR03:3D:60:42 The diskette in the EDC drive is write- protected.

Yes

If EDC is required for Un-write protect the EDC transactions, remove diskette. the terminal from service. If the terminal remains in service, discontinue using EDC until the terminal has been serviced.

PR03:3D:60:43 The diskette in the EDC drive has Yes not been formatted.

If EDC is required for Install a formatted diskette. transactions, remove the terminal from service. If the terminal remains in service, discontinue using EDC until a formatted disk has been installed.

PR03:3D:60:44 The diskette in the EDC drive does not have an EDC file.

If EDC is required for Install a formatted diskette. transactions, remove

Yes


87/107

21/10/2014


the terminal from service. If the terminal remains in service, discontinue using EDC until a formatted disk has been installed. PR03:3D:60:45 EDC detected an unknown error accessing the EDC diskette.

Yes

If EDC is required for Service investigation transactions, remove the terminal from service. If the terminal remains in service, discontinue using EDC until the terminal has been serviced.

PR03:3E:00:00 Self-test failed (operational Yes command processing). EDC is not present or is not enabled.

Not applicable


PR03:3E:00:01 The system firmware detected a Yes format error while processing print data before transmission to EDC. The most likely causes are an incomplete escape sequence or too much print data between line terminators (CR or LF).



PR03:3E:01:?? Continuous Availability spool file error.

Yes


Make sure the disk is not full, that there are not too many files open, and that the printer temp files are not being examined in an editor (journal.tmp, receipt.tmp, and edc.tmp). Otherwise, if persistent, service is required.

PR03:3F:23:?? EDC has failed to respond to a Yes command (represented by the last two digits of the status) within an expected period of time.


If the status is persistent, a service investigation is required.



The last two digits of the status are an error code. Common values include the following: 04 - too many open files 05 - access denied 08 - not enough memory 20 - sharing violation 70 - disk full

The valid commands are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device CRCs41 - print on device 42 - enable paper advance button on printer 43 - burst and deliver form 45 - move to top of form, burst, and deliver form PR03:3F:40:46 In response to an archive Yes command, this message indicates that no local data file currently exists to be archived. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

88/107

21/10/2014


PR03:3F:40:48 The local data file is locked and a timeout has occurred.

Yes


Shut down and restart the EDC application.

PR03:3F:40:49 A Remote Interface Command Yes (RCI) has been sent to EDC (such as archive), but the RCI interface has been disabled.


Enable the RCI by selecting the default location for the local data file. If you wish to control the location of the local data file, do not send the archive command to EDC.

PR03:3F:??:?? EDC responded to a command No with an invalid completion status. The format is :3F:yy:zz, where the command that was issued is yy and the invalid completion status is zz.


Not applicable

The valid yy commands are as follows: 30 - reset device 31 - idle device 34 - return device configuration data 37 - return device ROM CRCs 41 - print on device 42 - enable paper advance button on printer 43 - burst and deliver form 45 - move to the top of form, burst, and deliver form. The possible zz invalid completion codes are as follows: 31 - device idling 34 - device configuration data 37 device ROM CRCs 39 - device hard fault 41 - print command completed 42 - paper advance button enabled 43 - form burst and delivered45 TOF search, burst, and deliver completed

3.23 SD01 (Envelope Dispenser Status Messages) This section describes the envelope dispenser fault status messages. The device type and number as it appears in the status message is SD01. Refer to Table 3-24 for the envelope dispenser fault status messages. NOTE For depositors that combine deposit functionality with envelope dispensing functionality, this section provides the status messages for the envelope dispensing functions only. For fault status messages for the deposit functions, refer to Section 3.8.

Status Message

Table 3-24 SD01 - Envelope Dispenser Status Message Descriptions Sent to Description Journal Network Action On-site Action

SD01:23:40:02 The consumer did not take the envelope in the time allowed.

Yes

Continue normal transaction processing.


SD01:24:40:00 The envelope dispense

Yes

Continue normal



89/107

21/10/2014


operation was cancelled.

transaction processing.

SD01:2D:00:01 The supply of envelopes is running low.

Yes

Continue envelope Replenish the supply of dispensing. Initiate the envelopes. on-site action.

SD01:38:40:00 The envelope dispenser is inoperative or is not supported, or the envelope dispenser is unlocked.

Yes

Remove the envelope dispenser from operation. Initiate a service investigation.

Check the envelope dispenser cables for a loose connection. If the problem persists, a service investigation is required.

SD01:38:40:01 Internal communications error

Yes



SD01:3D:00:01 The envelope dispenser is empty or missing.

Yes

Remove the envelope Replenish the supply of dispenser from envelopes. operation. Initiate the on-site action.

SD01:3E:00:35 A jam has occurred in the envelope dispenser.

Yes

Remove the envelope Clear the jam. dispenser from operation. Initiate the on-site action.

SD01:3E:40:01 A device error occurred in the envelope dispenser.

Yes

Not applicable


SD01:3F:40:01 Internal communications error

TBD



SD01:3F:40:31 Envelope dispenser error. The XFS SP has reported an unspecified problem with the envelope dispenser.

Yes

No action is required. If this problem persists, initiate a service investigation.


3.24 SP01 (Statement Printer Status Messages) (Opteva Only) This section describes the statement printer fault status messages. The device type and number as it appears in the status message is SP01. Refer to Table 3-25 for the statement printer fault status messages.

Status Message

Table 3-25 SP01 - Statement Printer Status Message Descriptions Sent to Description DAL/Journal Network Action On-site Action

SP01:00:00:00 This is a status Yes/Yes received from the device indicating that a self-test was performed and no errors were found.

N/A

N/A

SP01:23:nn:00

Take the statement printer out-ofservice.


[1]

The device Yes/Yes application did not start a command request within the expected period of time. The device is busy or is out-of-service.


90/107

21/10/2014


SP01:24:nn:00 [1]

The consumer Yes/Yes has canceled the requested operation.

Retry the transaction at a later time No action required. if necessary.

SP01:2D:30:04 The paper supply Yes/Yes is low.

Schedule the paper replenishment.

Replenish the paper supply.

SP01:2D:30:06 The ribbon (reserved for cartridge is future use) [2] depleted.

Yes/Yes

Schedule the ribbon cartridge replacement.

Replace the ribbon cartridge.

SP01:2D:30:09 The print head (reserved for needs servicing. future use) [2]

Yes/Yes

Schedule the print head replacement.

Inspect the print quality. Adjust or replace the print head as required.

SP01:2D:30:0D The retain bin is (reserved for almost full. future use) [2]

Yes/Yes

Schedule the removal of supplies from the retain bin.

Empty the delivery module's retain bin.

SP01:38:30:nn Device timeout Yes/Yes while performing command nn. There is a possible hardware or software problem with the printer.

If nn is a print command (41), do a If fault is repetitive, call retain/form feed/retain and retry the service. transaction. If nn is a paper handling command (43, 46), retry the command.

SP01:38:40:nn The device Yes/Yes application is not responding to the command requests. There is an unknown command, or the device application is not running.

Take the statement printer out-ofservice.

If the command is a valid one for the device, try to restart the ATM. If the condition persists, a service investigation is required.

SP01:39:00:00 A Flash memory Yes/Yes or programming error. There is a possible hardware problem with the printer's control card or communication cable.

Remove the printer from service and perform the on-site action.

A service investigation is required. There is a possible problem with the printer hardware or there is a file access problem. Verify that the Flash file is installed on the hard drive and that the installation setup paths are valid.

SP01:3A:00:0A The statement Yes/Yes printer has detected a cut failure and has failed to complete the operation.

Take the statement printer out of service. Initiate on-site action.

Inspect for possible paper jam in cutter. If the error persists, a service investigation is required.

SP01:3A:00:0E The cutter has failed.

Yes/Yes

If the fault is repetitive, remove the A possible cutter failure or printer from operation and call paper jam. Confirm the cutter service. operation by printing a test form. If the fault still exists, call service.

SP01:3B:00:09 A print head [2] stall/position error. There is a possible paper jam in the print

Yes/Yes

If the fault is repetitive, remove the Clear any paper debris in the printer from operation and call print head area. If the fault is service. repetitive, call service. There is a possible interference problem between the print


91/107

21/10/2014


head area.

head and the document plate.

SP01:3D:nn:04 The paper supply Yes/Yes [1] is out.


Replenish the paper supply.

SP01:3D:nn:0D The retain bin is [1] [2] full or jammed.


Empty the delivery module's retain bin. Remove any forms that may have jammed at the entry to the bin.

SP01:3E:00:00 If this status is Yes/Yes received during an op-commanded self-test, the device was specifically requested to do a self-test but was not enabled or present.

N/A

N/A

SP01:3E:00:02 There is a top-of- Yes/Yes form sensor fault. The sensor is stuck at black.

If the fault is repetitive, remove the Clear any paper jams in the printer from operation and call entry guide. If the fault is service. repetitive, call service.

SP01:3E:00:03 There is a top-of- Yes/Yes form sensor fault. The sensor is stuck at white.

If the fault is repetitive, remove the Assure that the paper is printer from operation and call loaded with the TOF marks service. facing downward and located on the correct side. Clear any paper jam in the print area. If the problem is repetitive, call service.

SP01:3E:00:05 The hinged print Yes/Yes head is unlocked with the thermal statement printer.

Remove the printer from service and perform the on- site action.

Make sure the printers hinged print head is in the locked position with the thermal statement prnter.

SP01:3E:30:05 The hinged print Yes/Yes head is unlocked with the thermal statement printer.


Make sure the printer's hinged print head is in the locked position with the thermal statement printer.

SP01:3E:nn:06 The ribbon switch Yes/Yes [1] [2] indicates that the ribbon cartridge is missing.


Verify that the ribbon cartridge is properly installed and the hinge lid is fully closed. If the fault is repetitive, call service.

SP01:3E:00:07 There is a [2] delivery module positioning fault. There may be a paper jam in the Delivery Module.

Yes/Yes

If the fault is repetitive, remove the Clear any paper jams in the printer from operation and call delivery module. If the fault service. is repetitive, call service.

SP01:3E:nn:0A There may be a [1] paper jam in the delivery module. The sensors are blocked.

Yes/Yes


SP01:3E:nn:0C There is a print [1] [2] head paper jam. Unable to move head to or away from home

Yes/Yes

If the fault is repetitive, remove the Clear any jams beneath the printer from operation and call hinged lid. If the fault still service. appears, call service.

Yes/Yes


Clear any paper jams beneath the Delivery Module's sensors. If the fault is repetitive, call service.

92/107

21/10/2014


sensor. SP01:3E:40:03 The state/function Yes/Yes handler has detected invalid or corrupted print data in the print file and was unable to send the data to the printer.

Check that the print file name is correct and that the state/function data format is correct. If the condition persists, service is required.

N/A

SP01:3E:40:04 The state/function Yes/Yes handler could not find the requested print file. No print data was sent to the printer.

Check that the print file name is correct and that the state/function data format is correct. If the condition persists, service is required.

N/A

SP01:3E:40:05 The state/function Yes/Yes handler could not build a print data buffer. The requested print file or print data request size is either too large or is corrupted.

Check the print data or the file. Correct the function command or state data. If the fault persists, service is required.

N/A

SP01:3E:40:30 The device Yes/Yes application could not accept the command. This is an invalid command for this device.

Take the statement printer out of service. Correct the function command or state data.

N/A

SP01:3E:40:34 The print Yes/Yes command could not be built due to improper network command data. There is a state or function format fault.

Take the statement printer out of service. Correct the function command or the state data.

N/A

SP01:3F:00:01 There is an invalid Yes/Yes command or sequence. There is a possible software fault, or there is a failed attempt to stack forms longer than the stackers capability.

If the fault is repetitive, remove the Verify that the statement printer from operation and call printer configuration is set up service. for the required form dimensions. Otherwise, if restarting the ATM application does not solve the problem, call service.

SP01:3F:00:08 A document was not found during the presentation attempt. There is a possible sequence error, paper jam in delivery module,

If the fault is repetitive, remove the Clear any jams. If the fault is printer from operation and call repetitive, call service. service.

Yes/Yes


93/107

21/10/2014


or sensor failure. SP01:3F:00:10 Document not [2] found during retain operation. Possible jam or sequence error caused by consumer removing form.

Yes/Yes

If the fault is repetitive, call service. Note: This fault may be sent as part of a terminal software attempt to automatically clear a sequence fault.

Check delivery area for a possible jam. If repetitive, verify proper operation of the midway sensor using Maintenance diagnostics.

SP01:3F:00:11 Command [2] aborted. The specified form cannot be stacked.

Yes/Yes

For print and wait operations, resend the command with nonstacking operation request. Print and don't wait operations were completed with the forms not stacked.

To allow the stacking of the forms, verify that the paper size and printer setup is correct.

SP01:3F:nn:0B Difficulty locating Yes/Yes [1] [2] the top-of- form marks on the paper. The printer settings may not match the actual form. The form lengths may be incorrectly cut.

If the fault is repetitive, remove the Verify that the actual top-ofprinter from operation and call form marks match the service. statement printer settings. The settings can be checked in Maintenance mode using the Edit Device Parameters command in the Installation menu. Correct any settings that do not match the actual form. If the fault persists, call service.

SP01:3F:00:0F The midway Yes/Yes sensor is not operating. Unable to confirm retract operations.

Schedule service. The statement printer can be operated in the degraded mode.

SP01:3F:40:31 The device is not Yes/Yes in the correct operating mode to handle the network command requested. The command is out of sequence or the CAS mode is active.

The requested network command No action required. was not sent to the printer. A possible cause would be an improper attempt to operate the printer before the form has cleared the mechanism as a result of a deliver and don't wait. Another cause would be that the printer is in use by CAS and the consumer did not elect to cancel the operation in an expected time period.

SP01:3F:40:40 An unexpected or Yes/Yes unknown fault was returned from the statement printer.

If repetitive, take the statement printer out of service.

No action required. Contact service if the error persists.

SP01:3F:40:60 A document retain Yes/Yes [2] command was automatically done. The presented documents have been retained.

The network should be aware that the consumer may not have received the requested document.

No action required.

SP01:3F:40:61 A document dump Yes/Yes [2] command was automatically done. Present

The network should be aware that the consumer may not have taken the document.

No action required.


Verify proper operation of the midway sensor using Maintenance diagnostics.

94/107

21/10/2014


documents have been dumped to the ground. SP01:3F:40:62 A document was Yes/Yes [2] presented to the customer but was not taken in the programmed amount of time. [1] nn

A document retain or dump must be No action required. performed to clear the statement printer.

can be any number

[2] This

status message is not applicable to the thermal statement printer.

3.25 TS01 (Touch Screen Status Messages) This section describes the touch screen fault status messages. The device type and number as it appears in the status message is TS01. Refer to Table 3-26 for the touch screen fault status messages.

Status Message

Table 3-26 TS01 - Touch Screen Status Message Descriptions Sent to Network Description Journal Action On-site Action

TS01:38:00:00 Internal communcations error. Touch screen is out of service.

Yes

No If it is the only consumer keyboard in the action is system, shut down the terminal. If it is not, required. reconfigure the terminal without touch templates so consumers will not try to use the touch screen. A service investigation is required.

TS01:39:00:00 Memory allocation error

Yes

No If the terminal is still in-service, shut down the action is terminal. A service investigation is required. required.

TS01:3A:40:40 Controller error. Touch screen is out-of-service.

Yes

No If it is the only consumer keyboard in the action is system, shut down the terminal. If it is not, required. reconfigure the terminal without touch templates so consumers will not try to use the touch screen. A service investigation is required.

TS01:3E:41:40 The touch screen has been Yes enabled the maximum number of times specified in the Touch Screen Settings without receiving any touch input.

No If it is the only consumer keyboard in the action is system, shut down the terminal. If it is not, required. reconfigure the terminal without touch screen templates so consumers will not try to use the touch screen. A service investigation is required.

3.26 VC01 (Voice Status Messages) This section describes the voice fault status messages. The device type and number as it appears in the status message is VC01. Refer to Table 3-27 for the voice fault status messages.

Status Message

Table 3-27 VC01 - Voice Status Message Descriptions Sent to Network Description Journal Action On-site Action

VC01:30:??:?? A Voice command No reject. The format is :30:xx:yy, where the command rejected is xx and the reason code is yy.

The network No action is required. programmer should check the screen data for voice commands containing


95/107

21/10/2014


The valid commands xx are as follows:

message numbers out of range.

31 Abort/Clear/Idle 34 - Return device configuration data 35 - Return current status 37 - Return device ROM CRCs 42 - Speak (terminate current message) 44 - Speak (do not terminate current message). The valid reason codes for yy are as follows: 30 - Invalid command 31 - Command received out of sequence32 Buffer overflow 33 - Device ID incorrect34 Message format error (such as a missing field) VC01:38:00:00 Internal communications error

No

Not applicable

There is a bad physical (cable) connection to the voice hardware, or there is a problem with the hardware itself. If possible, check the integrity of the cable connection. Also, the voice board has a strap option (strap E5, position E-F) which, when removed, will put the hardware in self-test and the contents of the voice PROM will be spoken. You can also run the voice system diagnostics.

VC01:3C:??:?? An invalid device No response was received. The format is :3C:xx:yy, where xx is the response expected and yy is the response received.

Not applicable


Appendix A Hexadecimal-to-decimal and Hexadecimal-to-binary Conversion Refer to Table A-1 for hexadecimal-to-decimal conversion information and to Table A-2 for hexadecimal-to-binary conversion information. Table A-1 Hexadecimal-to-decimal Conversion First Digit Middle Digit Last Digit http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

96/107

21/10/2014


Hexadecimal Hexadecimal Hexdecimal 0=0

0=0

0=0

1 = 256

1 = 16

1=1

2 = 512

2 = 32

2=2

3 = 768

3 = 48

3=3

4 = 1024

4 = 64

4=4

5 = 1280

5 = 80

5=5

6 = 1536

6 = 96

6=6

7 = 1792

7 = 112

7=7

8 = 2048

8 = 128

8=8

9 = 2304

9 = 144

9=9

A = 2560

A = 160

A = 10

B = 2816

B = 176

B = 11

C = 3072

C = 192

C = 12

D = 3328

D = 208

D = 13

E = 3584

E = 224

E = 14

F = 3840

F = 240

F = 15

For example, 1A2 in hexadecimal = 256+160+2 = 418 decimal. Table A-2 Hexadecimal-to-binary Conversion Binary Weights Hex

8

4

2

1

0

= 0

0

0

0

1

= 0

0

0

1

2

= 0

0

1

0

3

= 0

0

1

1

4

= 0

1

0

0

5

= 0

1

0

1

6

= 0

1

1

0

7

= 0

1

1

1

8

= 1

0

0

0

9

= 1

0

0

1

A

= 1

0

1

0

B

= 1

0

1

1

C

= 1

1

0

0

D

= 1

1

0

1

E

= 1

1

1

0

F

= 1

1

1

1

Refer to the following example:

7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 - Bit Numbers --------------------------------0 1 0 0 0 0 1 0 : 0 1 1 0 1 0 0 1 - Binary Conversion --------------------------------| 4 | | 2 | : | 6 | | 9 | - Hexadecimal Bytes http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

97/107

21/10/2014


Appendix B 911 Status Cross-reference Use this appendix to determine the meaning of a 911 status message. This appendix contains a cross-reference list of 911 status as compared to the MDS status. A particular 911 status may be generated by several different MDS statuses. First, find the 911 status in the first column of the tables in this appendix. To determine the corrective action necessary and to obtain additional information, refer to the status definitions in Section 3. Refer to Table B-1 for a cross-reference of 911 alarm statuses.

911 Status MDS Statuses

Table B-1 AL01 (Alarms) Description

12 00


12 01


12 02


12 03


12 04


12 05


12 06


12 07


Refer to Table B-2 for a cross-reference of 911 card reader statuses.

911 Status MDS Statuses 2> 02

Table B-2 CR01 (Card Reader) Description

CR01:3F:40:42 Solicited write track 3 error CR01:3F:40:53 Solicited write track 1 error CR01:3F:40:55 Solicited write track 2 error

2= 81

CR01:23:00:00 Consumer timeout

2= 84

CR01:3F:42:40 Read conditions cannot be satisfied. CR01:3F:48:40 Card is jammed in the card reader. CR01:3F:60:48 Card partially inserted repeatedly or for a length of time.

2= ?: or 15 CR01:38:00:00 Card reader is unavailable or inoperative. ?: CR01:38:62:40 Self-test open failure CR01:3E:00:00 Network error. The card reader was directed to perform an operation that it does not have the capability to do. CR01:3E:44:40 Card retain bin is full. CR01:3E:48:40 Card is jammed in the card reader. CR01:3E:58:60 Card is jammed in the card reader. 15 81

CR01:3F:40:41 Unsolicited card retain occurred.

15 84

CR01:23:00:00 Consumer timeout CR01:3E:42:40 Read conditions cannot be satisfied. CR01:3E:60:48 Card partially inserted repeatedly or for a length of time.

17 02

CR01:3E:40:42 Unsolicited write track 3 error CR01:3E:40:53 Unsolicited write track 1 error CR01:3E:40:55 Unsolicited write track 2 error

Refer to Table B-3 for a cross-reference of 911 cash dispenser statuses. http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

98/107

21/10/2014


Table B-3 DI01 or D901 (Cash Dispenser) MDS Statuses Description

911 Status 28 0080HHLL04040000 (HI) or 28 8000HHLL04040000 (LO)

DI01:3E:03:03 Consumer did not take all the bills.

28 0180HHLL00000000 (HI) or 28 8001HHLL00000000 (LO)

DI01:3A:38:31 Dispense timeout

28 0180HHLL00000020 (HI) or 28 8001HHLL00000010 (LO)

DI01:38:00:00 Internal communications error

28 0180HHLL00000200 (HI) or 28 8001HHLL00000100 (LO)

DI01:3D:33:35 Cash dispenser rejected a command. DI01:3E:02:00 Cash dispenser attempted a dispense with the safe door open. DI01:3F:31:37 Cash unit 1 is empty or inoperative. DI01:3F:31:38 Cash unit 2 is empty or inoperative. DI01:3F:31:39 Cash unit 3 is empty or inoperative. DI01:3F:32:30 Cash unit 4 is empty or inoperative.

28 0180HHLL08080000 (HI) or 28 8001HHLL08080000 (LO)

DI01:3D:37:39 Reject container is missing or inoperative.

28 0181HHLL00000000 (HI) or 28 8101HHLL00000000 (LO)

DI01:3F:36:35 Cassettes have been shuffled.

28 0181HHLL00000002 (HI) or 28 8101HHLL00000002 (LO)

DI01:3F:33:36 Unidentified cassette in the cash dispenser.

28 0381HHLL00000001 (HI) or 28 8103HHLL00000001 (LO)

DI01:3A:35:39 Hardware error

28 0484HHLL00000<00 (HI) or 28 8404HHLL00000<00 (LO)

DI01:3D:37:38 Reject container is full.

28 9080HHLL00000000 (HI) or 28 8090HHLL00000000 (LO)

DI01:2D:0?:0? Cash supply low. The format is :2D:0m:0n, where m and n indicate the denominations that are running low.

Refer to Table B-4 for a cross-reference of 911 depositor statuses.

911 Status MDS Statuses 2: 0100

Table B-4 DP01 (Depositor) Description

DP01:3F:42:80 Deposit printer is inoperative DP01:3F:42:81 Unspecified printer error DP01:3F:42:85 Unspecified gate error DP01:3F:42:86 Unspecified transport error DP01:3F:42:87 Envelope is the wrong size

2: 0200

DP01:3D:50:6F Deposit cassette is nearly full

2: 0400

DP01:38:00:00 Internal communications error DP01:3E:42:40 Envelope is jammed in the transport or is present in the transport.

2: 0800

DP01:3D:60:6C Deposit cassette is inoperative DP01:3D:60:7C Deposit cassette is absent

2: 1000

DP01:23:00:02 Device timeout DP01:24:00:00 Consumer cancel

Refer to Table B-5 for a cross-reference of 911 cash presenter statuses.

911 Status MDS Statuses 29 00

Table B-5 DR01 (Cash Presenter) Description

DR01:3A:33:41 The cash was not presented but is in the transport and may be vulnerable. Transaction “subject to verification", do not reverse the transaction amount.


99/107

21/10/2014


DR01:3A:37:41 Hardware error 29 04

DR01:23:00:01 Consumer timeout DR01:23:00:30 Money not removed DR01:38:00:00 Internal communications error DR01:3A:41:40 Cannot present the cash

29 07

DR01:3F:30:41 No bills to present

29 40 DR01:3F:00:40 Forgotten cash has been removed (solicited) or 2< 40 (unsolicited) Refer to Table B-6 for a cross-reference of 911 consumer keypad statuses. Table B-6 KE01 (Consumer Keypad) 911 Status MDS Statuses Description 15 06

KE01:3F:00:C0 Stuck key

Refer to Table B-7 for a cross-reference of 911 receipt printer statuses.

911 Status

MDS Statuses

Table B-7 PR01 (Receipt Printer) Description

14 820700 PR01:39:40:01

Hardware error

PR01:3E:40:06

Dump error

PR01:3E:40:07

Paper jam

PR01:3E:40:08

Deliver error

PR01:3E:40:09

Cut error

PR01:3E:50:07

Paper jam and paper supply low

PR01:3E:50:08

Deliver error and paper supply low

PR01:3E:50:09

Cut error and paper supply low

PR01:3E:60:07

Paper jam and paper supply out

PR01:3E:60:08

Deliver error and paper supply out

PR01:3E:60:09

Cut error and paper supply out

14 820800 PR01:3C:42:00

Cannot detect a top-of-form mark

14 822000 PR01:3D:40:05

Reject bin is full.

PR01:3D:60:00

Paper supply out

14 824100 PR01:38:23:??

Printer failed to respond within the allotted time

PR01:38:30:?? to PR01:38:37:?? During initialization, the printer responded with an invalid status. PR01:38:51:??

Printer is not communicating

PR01:38:60:??

Printer failed to initialize

PR01:38:62:??


PR01:38:??:??


14 828000 PR01:2D:50:00

Paper supply low

Refer to Table B-8 for a cross-reference of 911 journal printer statuses. Table B-8 PR02 (Journal Printer) 911 Status

MDS Statuses

14 810007 or PR02:39:44:00 22 810007 PR02:39:54:00 PR02:39:64:00

Description Hardware error Paper supply low and possible hardware error Paper supply out and possible hardware error


100/107

21/10/2014


14 810020 or PR02:2D:50:00 22 810020 PR02:3D:60:00

Paper supply low Paper supply out

14 810041 or PR02:38:23:?? Printer failed to respond within the allotted time. 22 810041 PR02:38:30:?? to PR02:38:37:?? During initialization, the printer responded with an invalid status. PR02:38:60:??


PR02:38:62:??


PR02:38:??:??


14 910000 or PR02:30:??:?? 22 910000 PR02:3E:00:01

Printer rejected a command Data error

PR02:3F:00:03

Corrupted print data

PR02:3F:23:??


PR02:3F:??:??

Printer responded with an invalid completion status

Refer to Table B-9 for a cross-reference of 911 electronic data capture statuses.


Table B-9 PR03 (Electronic Data Capture) Description

14 810007 or PR03:39:44:40 EDC reported an RMX fatal error when it attempted to access the EDC diskette. 22 810007 14 810020 or PR03:3D:40:46 File does not exist 22 810020 PR03:3D:40:47 Unable to access file (max archives performed for the day) PR03:3D:40:48 Timeout (file locked by another process) PR03:3D:40:49 Archive command disabled PR03:3D:50:40 EDC detected a Disk Low condition. At this point, 100 more records can be written. PR03:3D:60:40 EDC detected a Disk Full condition PR03:3D:60:41 There is no diskette in the EDC drive PR03:3D:60:42 The diskette in the EDC drive is write-protected PR03:3D:60:43 The diskette in the EDC drive has not been formatted PR03:3D:60:45 EDC detected an unknown error accessing the EDC diskette 14 810041 or PR03:38:23:?? Failed to respond to command yy within an expected period for five consecutive times 22 810041 during initialization of the EDC. PR03:38:60:?? Internal communications error PR03:38:62:?? Not communicating with the system communications handler PR03:38:64:?? Continually rejecting commands (NAKing) PR03:38:??:?? During initialization, the EDC responded to a command with an invalid completion status. The command that was issued is yy and the invalid completion status is zz.

Appendix C 912 Status Cross-reference Use this appendix to determine the meaning of a 912 status message. This appendix contains a cross-reference list of 912 status as compared to the MDS status. A particular 912 status may be generated by several different MDS statuses. First find the 912 status in the first column of the tables in this section. To determine the corrective action necessary and to obtain additional information, refer to the status definitions in Section 3. Refer to Table C-1 for a cross-reference of 912 alarms statuses.


Table C-1 AL01 (Alarms) Description


101/107

21/10/2014


12 00


12 01


12 02


12 03


12 04


12 05


12 06


12 07


Refer to Table C-2 for a cross-reference of 912 card reader statuses. Table C-2 CR01 (Card Reader) 912 Status

MDS Statuses

Description

2> 0040 CR01:3F:42:40 Read conditions cannot be satisfied. CR01:3F:48:40 Card is jammed in the card reader. CR01:3F:60:48 Card was partially inserted repeatedly or for a length of time. 2> 008< CR01:3F:40:42 Solicited write track 3 error CR01:3F:40:53 Solicited write track 1 error CR01:3F:40:55 Solicited write track 2 error 2> 0082 CR01:38:00:00 Card reader is unavailable or inoperative. CR01:38:62:40 Selt-test open failure 2= 0190 CR01:3E:00:00 Network error. The card reader was directed to perform an operation that it does not have the capability to do. 2> 4081 CR01:23:00:00 Consumer timeout 2> 8082 CR01:3E:44:40 Card retain bin is full. CR01:3E:48:40 Card is jammed in the card reader. CR01:3E:58:60 Card is jammed in the card reader. 15 ?:

CR01:38:00:00 Card reader is unavailable or inoperative. CR01:38:62:40 Selt-test open failure CR01:3E:00:00 Network error. The card reader was directed to perform an operation that it does not have the capability to do. CR01:3E:44:40 Card retain bin is full. CR01:3E:48:40 Card is jammed in the card reader. CR01:3E:58:60 Card is jammed in the card reader.

15 81

CR01:3F:40:41 Unsolicited card retain occurred.

15 84

CR01:23:00:00 Consumer timeout CR01:3E:42:40 Read conditions cannot be satisfied. CR01:3E:60:48 Card was partially inserted repeatedly or for a length of time.

17 82

CR01:3E:40:42 Unsolicited write track 3 error CR01:3E:40:53 Unsolicited write track 1 error CR01:3E:40:55 Unsolicited write track 2 error

Refer to Table C-3 for a cross-reference of 912 cash dispenser statuses. Table C-3 DI01 or D901 (Cash Dispenser) 912 Status 2? 0000

MDS Statuses

Description

DI01:2D:0?:0? Cash supply low. The format is :2D:0m:0n, where m and n indicate the denominations.


102/107

21/10/2014


2? 0175 or 2? 5175

DI01:3F:31:37 Cash unit 1 is empty or inoperative.

2? 0185 or 2? 5185


2? 0195 or 2? 5195


2? 0205 or 2? 5205


2? 0354 or 2? 5354

DI01:3D:33:35 Cash dispenser rejected a command.

2? 0363 or 2? 5363

DI01:3F:33:36 Unidentified casette in the cash dispenser.

2? 0592 or 2? 5592

DI01:3A:35:39 Hardware error

2? 0654 or 2? 5654

DI01:3F:36:35 Cassettes in the cash dispenser have been shuffled.

2? 0782 or 2? 5782

DI01:3D:37:38 Reject container is full.

2? 0793 or 2? 5793

DI01:3D:37:39 Reject container is missing or inoperative.

2? 0812 or 2? 5812

DI01:3A:38:31 Dispense timeout

2? 0912 or 2? 5912

DI01:38:00:00 Internal communications error

2? 1000

DI01:3E:03:03 Consumer did not take all the bills.

DI01:3E:02:00 Cash dispenser attempted a dispense with the safe door open.

Refer to Table C-4 for a cross-reference of 912 depositor statuses. Table C-4 DP01 (Depositor) 912 Status MDS Statuses Description 2A 010000 DP01:3F:42:80 Deposit printer is inoperative. DP01:3F:42:81 Unspecified printer error DP01:3F:42:85 Unspecified gate error DP01:3F:42:86 Unspecified transport error DP01:3F:42:87 Envelope is the wrong size. 2A 020000 DP01:3E:40:7C Deposit gate did not open 2A 100000 DP01:23:00:02 Device timeout 2A 101000 DP01:24:00:00 Consumer cancel 2A 400000 DP01:38:00:00 Internal communications error DP01:3D:50:6F Deposit cassette is nearly full DP01:3E:42:40 Envelope jammed or present in the transport 2A 480000 DP01:3D:60:6C Deposit cassette is inoperative DP01:3D:60:7C Deposit container is absent Refer to Table C-5 for a cross-reference of 912 cash presenter statuses.

912 Status MDS Statuses 2@ 00

Table C-5 DR01 (Cash Presenter) Description

DR01:3A:33:41 The cash was not presented but is in the transport and may be vulnerable. Transaction “subject to verification", do not reverse the transaction amount. DR01:3A:37:41 Hardware error


103/107

21/10/2014

2@ 04


DR01:23:00:01 Consumer timeout DR01:23:00:30 Money not removed DR01:38:00:00 Internal communications error DR01:3A:41:40 Cannot present the cash. DR01:3F:30:41 No bills to present

@ 40 DR01:3F:00:40 Forgotten cash has been removed (solicited) or < 40 (unsolicited) Refer to Table C-6 for a cross-reference of 912 consumer keypad statuses. Table C-6 KE01 (Consumer Keypad) 912 Status MDS Statuses Description 15 06

KE01:3F:00:C0 Stuck key

Refer to Table C-7 for a cross-reference of 912 receipt printer statuses. Table C-7 PR01 (Receipt Printer) 912 Solicited Status 22 820700

912 Unsolicited Status 14 820700

MDS Statuses

Description

PR01:39:40:01

Hardware error

PR01:3E:40:06

Dump error

PR01:3E:40:07

Paper jam

PR01:3E:40:08

Deliver error

PR01:3E:40:09

Cut error

PR01:3E:50:07

Paper jam and paper supply low

PR01:3E:50:08

Deliver error and paper supply low

PR01:3E:50:09

Cut error and paper supply low

PR01:3E:60:07

Paper jam and paper supply out

PR01:3E:60:08

Deliver error and paper supply out

PR01:3E:60:09

Cut error and paper supply out

22 820800

14 820800

PR01:3C:42:00

Cannot detect a top-of-form mark

22 822000

14 822000

PR01:3D:40:05

Reject bin is full

PR01:3D:60:00

Paper supply out

22 828000

14 828000

PR01:2D:50:00

Paper supply low

22 824100

14 824100

PR01:38:23:??


PR01:38:30:?? to PR01:38:37:??

During initialization, the printer responded with an invalid status.

PR01:38:51:??


PR01:38:60:??


PR01:38:62:??


PR01:38:??:??

Printer failed to respond within the allotted time.

14 920000 [2]

PR01:23:00:00

Consumer timeout

[2]

PR01:30:??:??

Printer rejected a command

[2]

PR01:3E:00:01

Data error

[2]

PR01:3F:23:??

Printer failed to respond within the allotted time.

PR01:3F:40:0A

No receipt to deliver

PR01:3F:40:0B

No receipt to retain

22 920000


104/107

21/10/2014


[2]

PR01:3F:40:40

Unexpected or unknown fault

[1]

PR01:3F:40:60

Document retained

[1]

PR01:3F:40:61

Document dumped

PR01:3F:??:??

Printer responded with an invalid completion status.

[2] [1] A

solicited status does not occur for this MDS status. Only the unsolicited status occurs.

[2] An

unsolicited status does not occur for this MDS status. Only the solicited status occurs.

Refer to Table C-8 for a cross-reference of 912 journal printer st atuses.

912 Status 14 810007 or 22 810007

Table C-8 PR02 (Journal Printer) MDS Statuses Description PR02:39:44:00

Hardware error

PR02:39:54:00

Paper supply low and possible hardware error

PR02:39:64:00

Paper supply out and possible hardware error

14 810020 or 22 810020

PR02:2D:50:00

Paper supply low

PR02:3D:60:00

Paper supply out

14 810041 or 22 810041

PR02:38:23:??


PR02:38:30:?? to PR02:38:37:??

During initialization, the printer responded with an invalid completion status.

PR02:38:60:??


PR02:38:62:??


PR02:38:??:??


PR02:30:??:??

Printer rejected a command

PR02:3E:00:01

Data error

PR02:3F:00:03

Corrupted print data

PR02:3F:23:??


PR02:3F:??:??

Printer responded with an invalid completion status

14 910000 or 22 910000

Refer to Table C-9 for a cross-reference of 912 electronic data capture statuses.

912 Status

Table C-9 PR03 (Electronic Data Capture) MDS Statuses Description

14 810007 or 22 810007

PR03:39:44:40 EDC reported an RMX fatal error when it attempted to access the EDC diskette.

14 810020 or 22 810020

PR03:3D:40:46 File does not exist. PR03:3D:40:47 Unable to access file (max archives performed for the day) PR03:3D:40:48 Timeout (file locked by another process) PR03:3D:40:49 Archive command disabled PR03:3D:50:40 EDC detected a disk low condition. At this point, 100 more records can be written. PR03:3D:60:40 EDC detected a disk full condition. PR03:3D:60:41 There is no diskette in the EDC drive. PR03:3D:60:42 The diskette in the EDC drive is w rite-protected. PR03:3D:60:43 The diskette in the EDC drive has not been formatted. PR03:3D:60:45 EDC detected an unknown error accessing the EDC diskette.

Appendix D English-language Status Messages http://techpubs.diebold.com/techpubs/books/TP-820741-001/TP-820741-001-1.htm

105/107

21/10/2014


English-language status messages appear on the journal printer to help the terminal operator determine the outcome of an abnormal transaction without having to interpret the MDS status. Use Table D-1 to find status messages in Section 3 that may appear because of the same fault that caused the English-language message to print. The table has the following columns: The English-language message that appears on the journal printer. The table is arranged in alphabetical order by the English-language messages. The MDS status messages that may appear because of the same fault that caused the English-language message to print. The device table in Section 3 where you can find descriptions of the status messages. Table D-1 English-language Status Messages English-language Message Status Message

Device

Bills Dumped nn

DR01:3F:46:??

Cash presenter - Table 3-10

Card Entry Blocked - Card in Slot

CR01:3E:60:48

Card reader - Table 3-5

Card Jam

CR01:3E:48:40, CR01:3E:58:60 Card reader - Table 3-5

Card Retained

CR01:3F:40:41

Card reader - Table 3-5

Cass Shuffle

DI01:3F:36:35

Cash dispenser - Table 3-6

Check for Empty Cass 1

DI01:3D:31:37, DI01:3F:31:37



DI01:3F:31:38



DI01:3F:31:39



DI01:3F:32:30


Command Reject

SD01:3F:40:31

Envelope dispenser - Table 3-24

Command Rejected

PR01:30:??:??

Receipt printer - Table 3-21

Customer Cancel

SD01:24:40:00


Customer Timeout

DR01:23:00:01


Customer timeout due to CAS

SD01:23:40:02


Cut failure

PR01:3E:40:09


Cut failure and low supplies

PR01:3E:50:09


Cut failure and supplies out

PR01:3E:60:09


Denom Error/Cass Missing

DI01:3D:33:35


Deposit Cancel

DP01:24:00:00

Depositor - Table 3-7

Deposit Cass Absent

DP01:3D:60:7C


Deposit Cass Full

DP01:3D:50:7F, DP01:3E:40:7C Depositor - Table 3-7

Deposit Jam

DP01:3E:42:40


Deposit Jam - Gate

DP01:3C:42:7F


Deposit Timeout

DP01:23:00:02


Depositor Comm Problem

DP01:38:00:00


Dispense Error - Call Service

DI01:3A:38:31


Divert Cass Absent

DI01:3D:37:39


Divert Cass Full

DI01:3D:37:38


Document dumped

PR01:3F:40:61


Document presented and not taken

PR01:23:00:00


Document retained

PR01:3F:40:60


Door Not Opened - Clear Pocket

DR01:23:00:01


Equipment failure

SD01:38:40:01



106/107

Opteva Status Reference Manual (Mas Completo)

Recommend Documents