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 25 of 71
Component Identity
The general approach to identifying these devices is that the acceptor part usually contains the
overall description of the unit, and the dispensers are identified by an address (which is often a
sequence number from 1 upwards that is an intrinsic part of the protocol) together with the value that
they dispense. . If the unit only has one dispenser, the address will be 1.
Where necessary a dispenser can be tied to acceptor by type and by having the same serial number.
The DispenserBlock.m_UnitAddress field(s) will contain the above address that identifies the
dispenser
On multi-drop system, such as cctalk and MDB, the UnitAddress will contain the address of the
parent acceptor OR’ed with this dispenser address number so that multiple units can be
distinguished.
Routing
Dispenser Destination Initialisation
Paylink, during its initialisation of the unit, determines the value of the coin / bill in the dispenser(s)
and which coins / bills are routed into which dispensers. The adress(es) of the dispensers are stored
into the AcceptorCoin.Path field(s). All the other AcceptorCoin.Path fields will be zero.
When a coin / bill is accepted and routed into a dispenser this fact is always identified by Paylink and
the AcceptorCoin.PathCount is accurately incremented to show this.
Paylink then updates the DispenserBlock.CoinCount field by actually querying the unit.
Depending upon the actual unit this will be either accurate or an approximation. With a bill recycler
the result is usually an accurate figure, with an MDB changer the result is often approximate.
The value returned will however always be that reported by the device, any systematic corrections
will have to be handled by the application.
Routing Control.
For coin recycler units the routing is fixed and it is not possible for Paylink, and hence the application,
to change this.
For bill recyclers units, the routing can be changed by Paylink. The application notifies Paylink of the
desired routing by changing the AcceptorCoin.Path fields of the incoming Coin (Bill) array item to
contain the associated dispenser address, as described in Component Identity above.
The precise actions that occur when an AcceptorCoin.Path field is changed:
• If the AcceptorCoin.Path field for a currently recycled bill is changed to zero, Paylink set the
unit to stop diverting bills into the recycler. If there are no bills stored, then the Dispenser value
will go to 999999999, (this is irrelevant to payouts, as the dispenser will return “empty” if it is
attempted to be used), if bills are currently stored they may remain available to be paid out
(depending upon the device capabilities.)
• If the AcceptorCoin.Path field for a currently non recycled bill is changed from zero to a non
zero value, Paylink will set the unit to start diverting these bills into a recycler. Where possible the
recycler used to contain the bills will be that identified by the value in the AcceptorCoin.Path
field - but this is device specific. This may cause different value bills already in that recycler to be
dumped to the cashbox.