Alberici AVENTADOR User manual

Combi coin counting system
AVENTADOR
User Manual
AVENTADOR, piling coin counting system
User
Manual
Rev. 1.01

1. General
Congratulations on the purchase of the AVENTADOR counting s stem
for heaping mixed coins, developed and produced b Alberici SpA.
This s stem is designed in such a wa as to cut down routine
maintenance calls.
At ever power up, the device automaticall carries out various
cleaning operations.
As an option, it can be supplied with the intelligent iS3 sorter,
to separate the counted coins into 3 different directions.
Rejected coins are ousted directl b the coin acceptor, without
passing through the sorter.
It get easil installed in Cross-Change machines, where it is
necessar to count and rec cle large quantities of.
1.1 Operation
The massive coin cunting unit Aventador can identif and various currencies and coin denominations, poured in as
mixed masses, provided that the diameter of such coins ranges between 21mm and 31.5mm (on request 16mm-
24mm), and that their thickness stands between 1.7mm and 3.4mm.
The s stem consists of the following components, all of them working b the ccTalk protocol:
a. A entador self-cleaning feeder hopper: receives the heap of coins to be counted, and starts one b one
deliver to the inlet of the coin acceptor. The dispensing hopper is equipped with various elements (*) meant to
remove dirt from the coins poured in, to clean the coin belt, as well as to eliminate debris, dust and electrostatic
charges from the coins to be counted. Speed of the hopper is around 4,5 coins/sec.
b. SV (super high speed) coin alidator, capable of processing and identif ing up to 10 coins per second.
c. Automatic reset motor: in case of jamming problems, the s stem automaticall opens the side flap of the coin
acceptor, so unjamming the coin path. The jammed coins get returned out through the reject path, without being
counted.
d. Intelligent 3-way iS1 coin sorter (optional): it communicates with the s stem via the SPI port or via its 10p
connector, reporting an address error or coin jamming or operation fault, in order to hold or stop promptl the
counting process if necessar .
(*) Description of the picture next page:
1. The insertion basket is pierced with large holes to drain liquids and larger impurities.
2. A ventilating fan blows through the basket to separate volatile debris (e.g. cigarette butts, scraps of paper, fluff
and fabric bolls, etc.) from the coins.
3. The smallest and heaviest debris that have not been blown awa will fall through the expulsion slots located at
the bottom of the hopper tank and along the belt track.
4. The belt slides against a rotating brush that removes residues and scrubs grease off. In turn, the rotating brush is
kept clean b a comb tooth.
5. The outgoing coins drag against a carbon bristle brush, which cancel an electrostatic charges.
6. The clear channel between the hopper outlet and the inlet of the coin acceptor is equipped with a second
ventilating fan that expels the remaining impurities through the holes in the channel.
7. In addition, the Aventador is equipped with an eas accessible button that starts belt cleaning on command.
This button illuminates in different colours to signal different status of the s stem :
- stead green: the s stem is in stand-b ; or, the s stem will start operation and automatic cleaning when coins are
poured in; or, the s stem can be manuall cleaned b pressing the button;
- slow intermittent ellow: the s stem is counting;
- fast flashing ellow: the manual cleaning operation is in progress;
- red: the s stem is out of service.

1.2 Safety
The Aventador system must be installed in machines equipped with devices apt to disconnect power
supply.
Alwa s power off before removing or installing the Hopper Aventador.
The s stem contains moving mechanical parts: DO NOT PUT fingers or objects other than coins while the device
is operating, or when power is switched on.
PAY ATTENTION:
DANGER!
MECHANICAL PARTS IN MOTION

2. Technical specs
Protoco
ll
ccTalk 24V
peed
2
00
coins
/min.
Mixed coins c
apacit
y
per counting cycle
400
mi
xed
Accepted coin diameter
(mm)
2
1
÷
3
2
mm
(
option
: 16
÷
24
mm
)
Accepted coin thickness
(mm)
1,7
÷
2,
4
mm
Max
current draw
1
,40
A
S
tand
-
by
current draw
22
0 mA
Operating voltage
24 Vc
c
Operating t
emperatur
e
0°C ÷
75
°C
Humidity
20%
÷
75%
(non cond
ens
ed
)
Weight
(
Kg
)
2,366
3. Mechanical description
3.1 Dimensions
225,50
111,90
126
,
60
87
,
40
250
,
80
286
,
50
125
,
80

3.2 Installation
Follow steps below:
. fasten the slide base to the machine shelf
. place the hopper with the Aventador unit over the slide base and shift the hopper on it until it gets to the bottom
end
. before switching power on, read section 4
To remove the Aventador s stem, hold the base, and slide the hopper outwards.
Installation must be done in compliance with the instructions given in this section 3.2, for the guarantee to be valid.
4. Electrical description
4.1 Power supply
Power suppl to Hopper Aventador must be 24V d.c.. Leads cross section must be compatible with current draw
showed in section 2.
4.2 Pin-outs
The Hopper cctalk 10p connector is located in the rear side
of the hopper slide base, beside the dip-switch row for
setting the serial address.
The cctalk communication between the machine host
and the Aventador s stem runs through this 10p connector.
Connect to Ground (GND) all the plate terminals of the hopper.
All the devices in the s stem connect each other through the sockets hub, as per diagram below:
SLIDE BASE
244
,
00
92,00
9
,
00
68
,
00
25
,
00
10 pin
92,00

4.3 Setting the serial address by Dip-Switches
If necessar , the serial address of the hopper can be modified via the Dip-Switch row. The three dip-switches can
be combined as follows, to set the needed address:
Default address is 3 (all switches to OFF)
SW1 position
SW2 position
SW3 position
Serial
Address
OFF
OFF
OFF
3
ON
OFF
OFF
4
OFF
ON
OFF
5
ON
ON
OFF
6
OFF
OFF
ON
7
ON
OFF
ON
8
OFF
ON
ON
9
ON
ON
ON
10
The status of the dip-switches can be detected onl at power up or at reset, therefore an setting will not have an
effect until when the unit is switched off and on again.
5. Maintenance
Before an maintenance operation that requires disassembling the s stem, turn off the power and disconnect the
cable.
Watching from the coin insertion basket, check if debris or rubbish are la ing at the bottom of the dispenser belt,
and remove them (if necessar use a jet of compressed air). Their presence can obstruct the output of the coins,
hinder chain movement, spoil the components of the Aventador or alter its performance.
It is good practice to periodicall activate the automatic cleaning button : the hoper will start the belt in the
direction opposite to the standard rotation, thus forcing it to be cleaned b the built-in brush. Keep the button
pressed for as long as necessar . It is also useful to blow compressed air onto the slots for draining debris and
liquids (see the picture on page 4), to release an obstructions. Carr out the same operation on the holes of the
channel between the hopper outlet and the coin validator input.
The coins will get into the coin acceptor alread abundantl treated clean; however, over time it is possible to
accumulate debris in the acceptor reading path. The reading path can be accessed b opening the side flap door of
the acceptor: remove the debris that have been deposited b blowing compressed air, and then rub the walls with a
soft clean cloth, lightl soaked in a cleaning solution for glass and plastic surfaces.
CAUTION:
1) do not use alcohol, diluent, turpentine essence, acetone, petrol or other petroleum products, or containing citric acid.
2) the lenses of the sensors are made of transparent polymers, and must be cleaned with great caution so as not to
scratch them. Gently wipe several times, until the dirt is removed.
1 2 3

6. ccTalk protocol
ccTalk® communication protocol is the Mone Controls (formall Coin Controls) serial communication protocol for low speed control
networks. It was designed to allow the interconnection of various cash handling devices (Hopper, Card reader, Bill validators, Coin
selectors etc.), mostl in AWP and gaming Industr , but also in other devices that use those components.
ccTalk® is an open standard. All documentation is available at web site: www.cctalk.org .
Communication protocol of Alberici Aventador is implemented according to generic specification 4.4
1 Communication specifications
ccTalk serial communication is derivation of RS232 standard.
Low data rate NRZ (Non Return to Zero) as nchronous communication:
Baud rate 9600, 1 start bit, 8 data bits, no parit , 1 stop bit.
RS232 handshaking signals ( TS, CTS, DT , DCD, DS ) are not supported.
Message integrit is controlled b means of checksum calculation.
1.1 Baud rate
The baud rate of 9600 was chosen as compromise between cost and speed.
Timing tolerances is same as in RS232 protocol and it should be less than 4%.
1.2 Voltage level
To reduce the costs of connections the “Level shifted “ version of RS232 is used. The idle state on serial connector is 5V, and active
state is 0V.
Mark state (idle) +5V nominal from 3.5V to 5V
Space state (active) 0V nominal from 0.0V to 1.0V
1.3 Connection
The connection of Hopper at network is achieved b means of 10 pole IDC connector compatible with standard ccTalk 2+2 (Two
wires for power suppl + two for GND connector). Connector is used for power suppl and communication as well.
For schematics and connector la -out see image and table below.
Fig. 1 - ccTalk connector lay-out
1.4 Message structure
Each communication sequence consists of two message packets.
Message packets for simple checksum case is structured as follows:
[ Destination address ]
[ Nr. of data bytes ]
[ Source address ]
[ Header ]
[ Data 1 ]
...
[ Data n ]
[ Checksum ]
There is an exception of message structure when device answer to instruction 253 “Address poll” and 252 “Address clash”. The
answer consists of onl one b te representing address dela ed for time proportional to address value or random dela .
PIN Nr. Function
1 ccTalk Data
2 Not used
3 Not used
4 GND
5 Not used
6 Not used
7 +24 V
8 GND
9 Not used
10 +24 V
10p
ccTalk
connector
pin-out

For CRC checksum case format is:
[ Destination address ]
[ Nr. of data b tes ]
[ CRC 16 LSB ]
[ Header ]
[ Data 1 ]
...
[ Data n ]
[ CRC 16 MSB ]
1.4.1 Address
Address range is from address 0 to address 255. Address 0 is special case or so called “broadcast” address and address 1 is default
host address.
The recommendations for address value of different devices are presented in table below.
De ice category
Address
Additional addr.
Note
Coin Acceptor
2
11
-
17
Coin alida
tor, selector, mech...
Payout
3
4
-
10
Hopper
Bill validator
40
41
-
47
Banknote reader
Card Reader
50
-
Displa
60
Alphanumeric LC displa
Ke pad
70
-
Dongle
80
85
Safet equipment
Meter
90
Replacement for el.mec. counters
Power
100
Power s
uppl
1.4.2 Number of data byte
Number of data b te in each transfer could be from 0 to 252. Value 0 means that there are no data b tes in the message, and total
length of message packet will be 5 b tes. Although theoreticall it will be possible to send 255 b tes of data because of some
limitations in small micro controllers the number is limited to 252.
.
1.4.3 Command headers (Instructions)
Total amount of possible ccTalk command header is 255, with possibilit to add sub-headers using headers 100, 101, 102 and 103.
Header 0 stands for ACK (acknowledge) repla of device to host.
Header 5 stands for NAK (No acknowledge) repla of device to host.
Header 6 is BUSY repla of device to host.
In all three cases no data b tes are transferred. Use of ACK and NAK headers is explained separatel for each specific message
transfer.
Commands are divided in to several groups according to application specifics:
- Basic general commands
- Additional general commands
- Commands for Coin acceptors
- Commands for Bill validators
- Commands for Pa out
- MDCES commands
1.4.4 Data
There is no restrictions for data format use. Data could be BCD (Binary Coded Decimal)numbers, Hex numbers or ASCII strings.
Interpretation as well as format is specific to each header use, and will be explained in separate chapter.
1.4.5 Checksum
Message integrit during transfer is checked b use of simple zero checksum calculation.
Simple checksum is made b 8 bit addition (modulus 256) of all the b tes in the message.
If message is received and the addition of all b tes are non-zero then an error has occurred
3
.

1.5 Timing specification
The timing requirements of ccTalk are not ver critical but there are some recommendation.
1.5.1 Time between two bytes
When receiving b tes within a message packet, the communication software must wait up to 50 ms for next b te if it is expected. If
time out occurs, the software should reset all communication variables and get read to receive next message. The inter b te dela
during transmission should be ideall less than 2 ms and not greater than 10 ms.
1.5.2 Time between command and replay
The time between command and repl is dependent on application specific for each command. Some commands return data
immediatel , and maximum time dela should be within 10 ms.
Other commands that must activate actions in device ma return repl after action is finished.
1.5.3 Start-up time
After the power-up sequence Hopper should be read to accept and answer to a ccTalk message within less than 250 ms.
During such period all internal check-up and s stem settings must be done, and hopper should
1.6 Error handling
If slave device receive the message with bad checksum or missing data no further action is taken and receive buffer will be cleared.
Host software should decide to re-transmit message immediatel or after a fixed amount of time. In case when host receive message
with error it has same options.
2. Hopper A entador Command header set
Command header set, that host could use in communication with Hopper is given in table below.
Command headers are divided into 4 different groups:
- Common command headers
- Hopper command headers
- MDCES command headers
Code / Hex.
Command header
Note
254
FE
Simple poll
Return ACK
253
FD
Address poll
MDCES support
252
FC
Address clash
MDCES support
246
F6
Request manufacturer id
“
Alberici”
245
F5
Reque
st equipment categor id
“
Pa out”
244
F4
Request product code
“HopperTwo ccTalk”
242
F2
Request serial number
[Ser nr
-
L][Ser nr][Ser nr
-
H]
241
F1
Request software revision
un.n pm.m.m
217
D9
Request pa out high/low status
Return empt /full status
210
D2
Modif sorter path
Supported
:
as man directions as allowed b the Sorter (2, 3, or 5)
197
C5
Calculate ROM checksum
[Mon][Prog][Data]
164
A4
Enable hopper
Enable = 0xA5
163
A3
Test hopper
Supported
134
86
Dispense hopper value
Supported
133
85
R
equest hopper polling value
Supported
132
84
Emergenc stop value
Supported
131
83
Request hopper coin value
Supported
130
82
Request indexed hopper dispense count
Supported
1 1 Reset device
Software reset