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 44 of 71
cctalk coin processing
Fault Events
During 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_COIN_NOW_OK or IMHEI_COIN_UNIT_REPORTED_FAULT.
If the unit is reset (the sequence number is found to be zero) or repeated messages are ignored
IMHEI_COIN_UNIT_RESET or IMHEI_COIN_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.
Coin Events
When the acceptor reports an event other than an accepted coin, this is queued as a
COIN_DISPENSER_EVENT event, with the actual event byte reported in RawEvent.
The events categorised as OUTPUT_PROBLEM, 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:
Validation sensor not ready
Coin too fast ( over credit sensor )
Coin too slow ( over credit sensor )
C.O.S. mechanism activated ( coin-on-string )
Credit sensor reached too early
Reject coin ( repeated sequential trip )
Max. coin meter pulses exceeded
To Next Page
Loading...