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 33 of 71
When the counter of the number of bills in a recycle stacker reaches zero Paylink will still attempt to
pay bills - if this succeeds the UBA counter will remain at zero - it will not go negative.
Similarly, if the recycle stacker runs out of bills when the counter is non-zero, the will zeroize the
counter.
Note that the recycler itself uses the routing / recycler specification during payout. All notes paid out
undergo the normal input validation process and any that fail this validation are stack into the
cashbox without comment.
F56 / F53 Bill Dispenser
The F56 device comes with a number of different options. Although the F53 is a different device
number, Paylink just regards it as another option of an F56. All descriptions are therefore of an F56.
The F56 has a number of unique characteristics:
• The F56 only reports cassettes that are present; the existence of a location for a cassette is not
discoverable. Paylink therefore only reports the status of cassette locations in which it has seen a
cassette.
• A cassette can have a pattern of magnets set into it to indicate the type of bills with which it is
loaded. The F56 configuration can include bill descriptions corresponding to these magnet
patterns, which can specify value, bill length and bill thickness. If a newly discovered cassette
matches such a pattern specification, then the bill value and sizes are set from the specification.
• If no magnet specification is given, or if there is no match, then the sizes default to a generic
accept all size and the value is set as 999999999. This can be overridden to its correct value
using the standard Paylink facilities.
• A pool area / note delivery option is possible, with delivery to the front or to the rear. Part of the
configuration specification of an F56 has to include whether or not a delivery option is fitted.
• The F56 records in non-volatile memory the number of bills delivered from a payout position. This
value is reported to the application in the DispenserBlock.Count field.
• Some F56 models allow for the recovery of a failed dispense operation - on others this
information is not available. Where this information is not available and the unit has a final
dispense stage, then the notes are left in the pool area and Unpaid Bill processing performed.
• An F56 can be fitted with a shutter at the bill delivery stage. Paylink will automatically send a
close shutter command when bills have been taken from the delivery stage by the user.
• An F56 can reject bills as they are being paid out. Although it does not “fit” the API as specified,
the handler actually returns the cumulative total of the in the DispenserBlock.CoinCount field.
F56 / F53 Jams
The F56 is complex mechanically, so a jam situation can be reported for a number of specific
reasons. To allow the application to handle this the F56 handler will generate specific event (vie the
NextEvent() system) to notify the application of these. Details on this can be fuind in the F53/F56
Fault Processing subsection.
Cashcode B2B-300
The Cashcode B2B-300 accumulates bills to be dispensed in separate unit before presenting them to
the user. When bills are “found” in the dispenser during startup, the only thing the unit can do is to
dispense them.
When Paylink discovers this situation, during startup, or following a “long” power fail, it will undertake
Unpaid Bill processing as above.
To Next Page
Loading...