CPI CLS Advance Operator's Manual page 47

CLS Advance
10.2 Status & error messages
The CLS transmits detailed status and error messages to the control software.
The messages report on events of interest that happen while the CLS is operating. Errors can be
generated by every intelligent CLS unit such as the coin validator or the hoppers also attempting
to resolve their own errors. If they cannot clear the errors, the CLS will pass the relevant error
code to the control software.
Usually, the error codes are translated to explicit error messages in the control software describing
the error location and tips on how to correct the errors. In this case you will not need the tables below.
If not, the Troubleshooting Tables below list the error category depending on the gravity of the
error concerning the CLS operation as well as related information also useful in helping how to
handle the error.
10.2.1 Error categories
The CLS will attempt to resolve any errors or problem situations without external intervention.
Events are prioritized in the categories defined below:
Category Description
The event will be recorded and transmitted to the control software
Informa-
but the CLS will continue to operate correctly and no intervention is
tional
required.
This error will require intervention by the operator and indicates the CLS
is currently not operating or shortly will not be capable of correct opera-
Attention
tion without intervention by the attendant/service. Examples might be a
coin jam, a hopper running out of coins
This error indicates that it is likely that some component in the CLS has
failed and needs to be replaced. The error is severe enough to cause the
machine to stop operating and intervention by the attendant will likely
Critical be insufficient to repair the problem, although the control software can
recommend a course of action involving the attendant. One example
might be an output failure on the CLS main PCB or a communication
failure between the CLS units.
OM_CLS_-_EN_2-0
10.2.2 Troubleshooting tables
The following tables list the error codes transmitted by the
• CLS control unit
• CLS coin validator
• CLS coin hoppers
10.2.2.1 Error codes transmitted by the CLS control unit
Error code Description/Cause
Hopper count mismatch after
system start-up. Number of
hoppers identified are not
0x0001
matching with the number
configured in the system
Hopper denomination
mismatch after system
start-up. Hopper denomina-
0x0002
tions and country code are
not matching with the payout
Who can
configuration
help?
Main controller RAM fault. Its
0x0010
memory is defect
–
Main controller warning. Its
0x0012 stack-based memory has
run out
Attendant/
Service
Main controller warning.
0x0013 Its non-volatile memory is
defect
Main controller warning.
0x0014 Real-time clock battery for
Attendant/
backup missing
Service
Main controller warning.
0x0020 Its internal CX2 queue has
run out
Main controller warning. Its
0x0021 internal hopper queue has
run out
Main controller warning.
0x0022 Its internal control request
queue has run out
Category Remedy/hints
Critical • Make sure that all hoppers are
installed and engaged correctly
(cf. Chap. "7.5 Removing and reinstall-
ing a coin hopper", p. 30)
• Configuration failure, contact
service
Critical Configuration failure, contact service
Critical Hardware replacement, contact
service
Critical Programming failure, contact Service Service
Critical Hardware replacement, contact
service
Critical Initialization, Hardware replacement,
contact service
Critical Programming failure, contact Service Service
Critical Programming failure, contact Service Service
Critical Programming failure, contact Service Service
Troubleshooting
By whom
• Attendant possess-
ing the key for the
lower lock
• Service
Service
Service
Service
Service
47