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 45 of 71
cctalk note processing
Fault Events
Shortly after start-up the cctalk command “Do self Test” is sent to the acceptor. The response is
queued as an event with the first byte of the response in RawEvent and an EventCode type of
IMHEI_NOTE_NOW_OK or IMHEI_NOTE_UNIT_REPORTED_FAULT.
Some acceptors reply to this command with a NAK, these are reported as
IMHEI_NOTE_SELF_TEST_REFUSED.
If the unit is reset (the sequence number is found to be zero) or repeated messages are ignored
IMHEI_NOTE_UNIT_RESET or IMHEI_NOTE_UNIT_TIMEOUT event is queued.
Whenever any of these faults have been reported, the handler will continually “poll” the acceptor with
“Do Self Test” commands until a “non-faulty” response is returned.
Note Events
When the acceptor reports an event other than an accepted note, this is queued as an
NOTE_DISPENSER_EVENT event, with the actual event byte reported in RawEvent.
The events categorised as MISAREAD, JAM & INTERNAL_PROBLEM, are also reported as self test
faults on some acceptors. They are therefore automatically latched as faults (without sending the self
test fault) and hence a NOW_OK “fault” is generated when they clear.
The handler classifies cctalk events as:
Bill returned from escrow
Invalid bill ( due to validation fail )
Invalid bill ( due to transport problem )
Inhibited bill ( on serial )
Inhibited bill ( on DIP switches )
Bill jammed in transport ( unsafe mode )
Bill jammed in transport ( safe mode )
Anti-string mechanism faulty
To Next Page
Loading...