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 43 of 71
Events (Faults / Auditing)
Introduction
The Paylink system design is based around the handling of money in and money out. The peripherals
used are also capable of providing notifications that are not related to money, primarily faults and
fraud attempts.
This information is captured by Paylink, and is provided to the application as “Events”, which are
queued and passed to the application on request.
There is no intention that these events would be used for the normal operation of the application.
Rather, the intention is that they can be captured and presented in “management” reports.
(Obviously, the application can respond automatically to events such as fraud, by disabling
everything f
or a while, but this doesn’t form part of the algorithms by which the application manages
the peripherals.)
The event codes used have an internal structure, allowing cateogizations. The bottom 6 bits are the
unique event classification code, fault related codes have bit 5 set and otherwise overlap these
events code, whilst more significant bits describe the type of unit affected.
For details of the exact makeup of the values of these codes, users are refered to the ImheiEvent.h
header file.
Events fall into two categories, notifications and faults. Notifications are just that, the incoming
information is passed along to the application.
On the other hand, Paylink remembers the fact of a fault having happened, and when the fault clears,
a NOW_OK “fault” event will be generated.
A specific bit in the event code is reserved for indicating fault events.
Full details on the make up of the event codes are given in the
“Milan / Paylink Programmers Manual”
document.
