Milan / Paylink System Manual Issue 1.5 29 January 2020
CONFIDENTIAL
Not to be disclosed without prior written permission from Aardvark Embedded Solutions Ltd
Page 53 of 71
CLS Fault Processing
All errors are reported against the acceptor device, except for hopper error 0x65 (lost connection)
which is reported against the failing hopper.
The current Paylink API design only allows for a single byte of error data. The CLS provides 2 bytes
in the event codes.
To allow for this the error byte is encoded when they are reported following the CLS entering an error
state.
The reported errors come from two sources, the CLS controller and the acceptor, but can be merged
into one list as they do not have overlapping values in the 2nd byte. (All acceptor faults have a first
byte value of 0x20)
The encoding for the single byte in the RawEvent byte is as follows (in hex):
To allow the application to confirm the encoding if necessary, an event of
IMHEI_COIN_INTERNAL_PROBLEM is also queued, with the RawEvent field containing the first of the two
error bytes.
F53/F56 Fault Processing
The F56 is complex mechanically, so a jam situation is reported as an error for a number of specific
reasons, which are reported via the Event mechanism.
The F56 handler generates events to notify the application of these jam situations. Specifically, the
handler will return an
EvenCode = IMHEI_NOTE_DISPENSER_PROBLEM
RawEvent = the returned F56 error code (as described in the Fujitsu “F56-BDU ERROR
CODE LIST” manual.)
Index = F56 Cassette.
To Next Page
Loading...