Grupo Azkoyen MODULAR X6 CCTALK User manual

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 1
MODULAR X6 CCTALK

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 2
INDEX
1. CCTALK®SERIAL COMMUNICATION PROTOCOL .....................................................6
1.1 Introduction ..................................................................................................6
2. PHYSICAL LEVEL ..............................................................................8
2.1 Voltage levels and transmission speeds .............................................................8
2.2 Connector .....................................................................................................8
3. LOGIC LEVEL .........................................................................10
3.1 Message structure ........................................................................................10
3.2 Destination address ......................................................................................10
3.3 Number of data bytes ................................................................................... 11
3.4 Origin address ............................................................................................. 11
3.5 Header .......................................................................................................11
3.6 Data .......................................................................................................... 12
3.7 Checksum ...................................................................................................12
3.8 Temporary requirements ...............................................................................12
4. START UP PROCEDURE ................................................................................13
5. LIST OF COMMANDS ..............................................................................14
5.1 SIMPLE POLL [254] ......................................................................................20
5.2 ADDRESS POLL [253] ................................................................................... 20
5.3 ADDRESS CLASH [252] .................................................................................21
5.4 ADDRESS CHANGE [251] ..............................................................................22
5.5 ADDRESS RANDOM [250] .............................................................................. 23
5.6 REQUEST POLLING PRIORITY [249] ................................................................24
5.7 REQUEST STATUS [248] ............................................................................... 24
5.8 REQUEST MANUFACTURER ID [246] ............................................................... 25
5.9 REQUEST EQUIPMENT CATEGORY ID [245] ......................................................26
5.10 REQUEST PRODUCT CODE [244] .................................................................... 26
5.11 REQUEST DATABASE VERSION [243] .............................................................. 27

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 3
5.12 REQUEST SERIAL NUMBER [242] ...................................................................28
5.13 REQUEST SOFTWARE REVISION [ 241] ...........................................................28
5.14 TEST SOLENOIDS [240] ................................................................................ 29
5.15 READ INPUT LINES [237] ..............................................................................30
5.16 READ OPTO STATES [236] ............................................................................ 31
5.17 PERFORM SELF-CHECK [232] ......................................................................... 32
5.18 MODIFY INHIBIT STATUS [231] ..................................................................... 35
5.19 REQUEST INHIBIT STATUS [230] ...................................................................36
5.20 READ BUFFERED CREDIT OR ERROR CODES [229] ............................................ 37
5.21 MODIFY MASTER INHIBIT STATUS [228] ......................................................... 40
5.22 REQUEST MASTER INHIBIT STATUS [227] .......................................................41
5.23 REQUEST INSERTION COUNTER [226] ............................................................42
5.24 REQUEST ACCEPT COUNTER [225] ................................................................. 43
5.25 MODIFY SORTER OVERRIDE STATUS [222] ...................................................... 44
5.26 REQUEST SORTER OVERRIDE STATUS [221] .................................................... 45
5.27 ENTER A NEW PIN NUMBER [219] ..................................................................46
5.28 ENTER A PIN NUMBER [218] ..........................................................................47
5.29 REQUEST DATA STORAGE AVAILABILITY [216] ................................................48
5.30 READ DATA BLOCK [215] ..............................................................................49
5.31 WRITE DATA BLOCK [214] ............................................................................ 50
5.32 REQUEST OPTION FLAGS [213] ...................................................................... 51
5.33 REQUEST COIN POSITION [212] ....................................................................51
5.34 MODIFY SORTER PATHS [210] ....................................................................... 52
5.35 REQUEST SORTER PATHS [209] .....................................................................55
5.36 TEACH MODE CONTROL [202] ....................................................................... 56
5.37 REQUEST TEACH STATUS [201] .....................................................................57
5.38 CONFIGURATION TO EEPROM [199] ...............................................................58
5.39 COUNTERS TO EEPROM [198] ........................................................................59

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 4
5.40 CALCULATE ROM CHECKSUM [197] ................................................................60
5.41 REQUEST CREATION DATE [196] ....................................................................61
5.42 REQUEST LAST MODIFICATION DATE [195] ..................................................... 62
5.43 REQUEST REJECT COUNTER [194] .................................................................. 62
5.44 REQUEST FRAUD COUNTER [193] ..................................................................63
5.45 REQUEST BUILD CODE [192] .........................................................................64
5.46 MODIFY DEFAULT SORTER PATH [189] ........................................................... 65
5.47 REQUEST DEFAULT SORTER PATH [188] ......................................................... 66
5.48 MODIFY COIN ID [185] .................................................................................67
5.49 REQUEST COIN ID [184] ............................................................................... 68
5.50 MODIFY SECURITY SETTING [181] ................................................................. 69
5.51 REQUEST SECURITY SETTING [180] ...............................................................70
5.52 MODIFY BANK SELECT [179] .........................................................................71
5.53 REQUEST BANK SELECT [178] ....................................................................... 72
5.54 REQUEST ALARM COUNTER [176] ..................................................................72
5.55 REQUEST BASE YEAR [170] ........................................................................... 73
5.56 REQUEST ADDRESS MODE [169] .................................................................... 74
5.57 MODIFY INHIBIT AND OVERRIDE REGISTER [162] ............................................75
5.58 REQUEST FIRMWARE UPGRADE CAPABILITY [141] ............................................75
5.59 UPLOAD FIRMWARE [140] .............................................................................76
5.60 BEGIN FIRMWARE UPGRADE [139] ................................................................. 77
5.61 FINISH FIRMWARE UPGRADE [138] ................................................................78
5.62 SET ACCEPTANCE LIMIT [135] ....................................................................... 78
5.63 BEGIN TABLES UPLOAD [99] .........................................................................79
5.64 UPLOAD TABLES [98] ................................................................................... 80
5.65 FINISH TABLES UPLOAD [97] ........................................................................81
5.66 REQUEST MODULES INFORMATION [96] .........................................................81
5.67 REQUEST COMMS REVISION [ 4 ] .................................................................. 84

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 5
5.68 CLEAR COMMS STATUS VARIABLES [ 3 ] ......................................................... 85
5.69 REQUEST COMMS STATUS VARIABLES [ 2 ] ..................................................... 85
5.70 RESET DEVICE [ 1 ] ..................................................................................... 87
6. TELE-PROGRAMMING PROCESS .........................................................................87
7. FIRMWARE PROGRAMMING PROCESS ................................................................. 89

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 6
1. CCTALK®SERIAL COMMUNICATION PROTOCOL
This technical manual comprises the serial communication protocol cctalk®implemented on
the X6 validators.
1.1 Introduction
The communication protocol that has been implemented in the Validator is compatible with
cctalk®. The specification used for the implementation of this communication protocol is the
following: cctalk Serial Communication Protocol, Generic Specification, Issue 4.3.
General characteristics of working in serial mode:
¾The validator will have a default address assigned in the factory, but this can be
changed with cctalk commands (“Address change” “Address poll”).
¾The validator can work with a total of 16 different types of coins.
¾It has 16 inhibit bits, one for each type of coin (command “Modify inhibit status”).
¾The validator can work with a 5 or 3 ways sorter.
¾The default sorter path can be programmed with the command “Modify default sorter
path”.
¾The sorter paths can be inhibited: command “Modify sorter override status”. Each coin
has programmed 4 possible sorter paths. If the path programmed as a first optin (path
1) is inhibited the coin will be diverted to path 2. If this is inhibited will be diverted to
path 3 and if it is inhibited the coin will go to path 4. If all the paths are inhibited the
coin will go to the default path.
¾After the switching on the validator or after a reset all the coins will be inhibited.
¾The exit code of the coins that are being accepted by the validator can be transmitted to
the machine in reply to the command “Read buffered credit or error codes”. It is advised
that the machine poll the validator with this command at intervals from 100 ms. to 900
ms.. If the time is above 1 second without the machine polling, the validator inhibits the
acceptance of all coins until it receives a new “Read buffered credit or error codes”
command. This way of working avoids the validator admitting coins when the machine is
not working correctly.
¾The Validator has the possibility to work in “secure mode”: certain commands are not
admitted in order to avoid the modification of the working way of the Validator.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 7
Additionally, the validator can work in mode “L66 cctalk compatibility”. In this mode
some commands have changed its behaviour in order to be compatible with the L66
cctalk validator.
¾The Validator has one zone with 64 bytes of data available to the user into the Flash
memory. This zone is read and written by the means of the commands “Read data
block” and “Write data block”.
¾Following the CCTALK specifications, Appendix 6, the CCTALK interface identification
can be one of the following:
cctalk b96.p0.v12.a5.d0.c7.m0.x8.e0.i3.r4: conector de tipo 7.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 8
2. PHYSICAL LEVEL
2.1 Voltage levels and transmission speeds
The data is established using TTL levels: 5 volts is a ‘1’ logic and 0 volts is a ‘0’ logic, being the
level of rest of 5 volts. The validator has a “pull-up” resistor at 5 Vdc.
Mark (idle): +5Vdc.
Space (activates): 0Vdc
The communication is asynchronous and half-duplex, that is, it cannot simultaneously transmit
more than one element on the bus.
The ‘timing’ of the communication meets the characteristics of the RS232 industrial standard.
RS232 communication has various parameters that in this application are configured as
follows:
9600 bauds, 1 start bit, 8 data bits, without parity, 1 stop bit
2.2 Connector
The validator has two connectors:
Type 7 connector, following the CCTALK specification: 4 ways “standard interface, JST
connector”. The description is as follows:
PIN NAME DESCRIPTION
1 VIN Power supply of the validator
2 N.C. Not connected
3 GND Ground, internally connected to 0V
4 /DATA Data line
Table 1: 4 pins Conector CCTALK

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 9
10 pins connector, equivalent to Molex serial 862, P/N 10-89-1101 (10µgold). The description
is as follows:
PIN NAME DESCRIPTION
1 /DATA Data line
2 N.C. Not connected
3 S1 Sorter coil 1
4 S3 Sorter coil 3
5 N.C. Not connected
6 S2 Sorter coil 2
7 VIN Power supply of the validator
8 GND Ground, internally connected to 0V
9 N.C. Not connected
10 N.C. Not connected
Table 2: 10 pins CCTALK connector
Nota 1: This connector is designed to work with a sorter of 3 or 5 ways.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 10
3. LOGIC LEVEL
3.1 Message structure
The format of the messages is the following:
[Destination address]
[Nº of data bytes]
[Origin address]
[Header]
[Data 1]
[Data 2]
...
[Data N]
[Checksum]
Each sequence of communication is made up of two strings. The first corresponds to the
command sent by the Machine to the Validator, and the second is the reply sent by the
Validator to the Machine. Both strings have the format indicated previously.
3.2 Destination address
The ‘Destination address’ byte indicates the node on the bus (slave) Where the message is
directed. The range of addresses goes from 0 to 255 (of those 254 correspond to Validator
addresses as is explained further on).
0: Used in messages that affect all the Validators simultaneously, (Broadcast
messages).
1: Machine address. When the message is directed from the Validator to the Machine.
2 to 255: addresses of the Validators in multi-slave communication, configurable using
software with MDCES commands. The default address of the Validator is 2
although it can be modified using commands.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 11
3.3 Number of data bytes
This byte indicates the number of data bytes in the message and not the number total of bytes
of the message. If it is ‘0’, it means that the message does not have any data and in this case
the number total number of bytes of the message will be of 5 bytes (The minimum permitted).
The values 253 to 255 are not permitted in this field and would be considered as the value
252.
The X6 Validator has the capacity to receive up to a maximum of 66 bytes in each string. In
reception, it can receive and calculate the checksum of a string up to 252 bytes, although it
can only process the first 66 (see command REQUEST COMMS STATURS VARIABLES [2]).
3.4 Origin address
The byte ‘Origin address’ indicates the node on the bus that sends the message. The range of
addresses goes from 1 to the 255 (of those 254 correspond to possible addresses of the
Validator).
1: address of the Machine. When the message is sent by the Machine.
2: default address of the Validator on leaving the factory,in communication with only one
slave. When the message is sent by the Validator.
2 to 255: addresses of the Validator in multi-slave communication, configurable using
software with MDCES commands.
3.5 Header
The range of header bytes goes from 0 to 255. The “Header” will never have the value ‘0’ in
the case of messages sent by the Machine.
The Validator can return the following values in the header byte:
0: ACK, the Validator has carried out the command correctly
5: NACK, an error has occurred in the processing of the command or the command has
not been carried out due to the present validator configuration.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 12
6: BUSY, the Validator is busy doing an operation and cannot attend the command.
3.6 Data
The range of values that each data byte can take is from 0 a 255.
The meaning of the data depends on the command to execute.
3.7 Checksum
The “Checksum” is the value that makes the 8 lower bits of the sum of all the bytes in the
message, including the checksum, give result ‘0’.
For example, the message [01] [00] [02] [00] will be followed by the checksum [253]
because:
1 + 0 + 2 + 0 + 253 = 256 = 0.
3.8 Temporary requirements
Maximum time between bytes:
The maximum time between two bytes in the same message is 50 ms. If it is exceeded the
communication programme will reset the communication variables and will prepare for the
reception of a new message.
Maximum time between command and reply:
The maximum reply time to a command depends on the time that it takes the Validator to
process the command. This time is, by default, 50 ms, if another value has not been specified
in the definition of the command.
Minimum time from the power on until the sending of the first command:
The minimum time it takes from power on to the Validator until the first command is sent is
250 ms.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 13
3.9 Error management
If a Validator receives an incomplete message (reception timeout) or with an incorrect
checksum, it will not carry out another action and it will reset the communication variables and
prepare to receive a new message. The Machine, on not receiving a reply to any message sent,
can choose to resend the same message.
On the other hand, if the Machine receives an incomplete message (reception timeout) or with
an incorrect checksum, it can choose to resend the same message.
In any case, when there is an error in the reception of a message, there is no defined NACK
message, which simplifies the implementation of multi-slave protocol and reduces collisions.
If a Validator receives a command that it is not ready to execute, it responds with a NACK
message.
4. START UP PROCEDURE
In the following paragraphs the sequence of commands necessary for the Validator to be able
to accept coins after a reset or power-up is indicated. The sequence indicated is the minimum
necessary. Another sequence can be used: with a different order of commands and/or more
complex.
It is assumed that:
-There is a Validator programmed with the coins to use, powered at the recommended
voltage (12 Vdc to 24 Vdc.)
-The CCTALK address of the Validator is known (default: 2)
-The poll time required is known
Sequence of commands:
-Command ENTER PIN NUMBER [218]. This command is only necessary if a PIN
protection is used.

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 14
-Command REQUEST STATUS [248]: if the reply is not OK the Validator will not be able
to accept coins. Optionally the command PERFORM SELF-CHECK [232] can be used.
-Command MODIFY INHIBIT STATUS [231]: Activate the coins that should be
admitted.
-Command MODIFY SORTER OVERRIDE STATUS [222]. This command tells the
validator the available sorter paths. It is not necessary to send this command if the
sorter is not utilised. In this case, it is assumed that the coins have not programmed
their own sorter path.
-Command READ BUFFERED CREDIT OR ERROR CODES [229]. Retransmit this
command with adequate frequency (one command in less than 1 second) so that the
Validator can accept coins and the machine can read the coin data.
5. LIST OF COMMANDS
All the commands implemented comply with cctalk® standards. Among the specific cctalk
commands, the first group is general, that is, commands valid for any type of device. The rest
of the specific cctalk commands are designed to be used with Vaidators.
A PIN can protect all the commands, except “Address Poll (253)” and “Simple Poll (254)”. If it
receives a command and a valid a PIN has not previously been introduced, the Validator will
not answer the command. The value a PIN = 0 will deactivate this protection.
The X66 validator can work in one of the 3 following modes:
-Normal mode: the majority of the cctalk commands are available. See Table 3, page 11.
-Secure mode: some commands are not available. See Table 4, page 13.
-“L66 compatibility” mode: it is similar to “Secure Mode”, some commands are not
available (see Table4, page 17). Additionally, some others commands have their
behaviour modified or are not available. See Table, page 14 .

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 15
Table 1: LIST OF COMMANDS
Header
(decimal) Command Page
254 Simple Poll 19
253 Address Poll 20
252 Address Clash 21
251 Address Change 22
250 Address Random 23
249 Request polling priority 23
248 Request status 24
246 Request manufacturer id 25
245 Request equipment category id 26
244 Request product code 26
243 Request database version 27
242 Request serial number 27
241 Request Software Revision 28
237 Read Input lines 29
240 Test Solenoids 30
236 Read opto states 31
232 Perform self-check 32
231 Modify inhibit status ¡Erro
r!
Marc
ador
no
defin
ido.
230 Request inhibit status 36

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 16
229 Read buffered credit or error codes 37
228 Modify master inhibit status 40
227 Request master inhibit status 41
226 Request insertion counter 41
225 Request accept counter 43
222 Modify sorter override status 43
221 Request sorter override status 45
219 Enter new a PIN number 46
218 Enter a PIN number 47
216 Request data storage availability 47
215 Read data block 48
214 Write data block 49
213 Request option flags 50
212 Request coin position 51
210 Modify sorter paths 52
209 Request sorter paths 54
202 Teach mode control 56
201 Request teach status 57
199 Configuration to EEPROM 58
198 Counters to EEPROM 59
197 Calculate ROM checksum 60
196 Request creation date 60
195 Request last modification date 61
194 Request reject counter 62
193 Request fraud counter 63
192 Request build code 64
189 Modify default sorter path 65

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 17
188 Request default sorter path 66
185 Modify coin id 67
184 Request coin id 68
181 Modify security setting 69
180 Request security setting 70
179 Modify bank select 71
178 Request bank select 72
176 Request alarm counter 72
170 Request base year 73
169 Request address mode 74
162 Modify inhibit and override registers 75
141 Request firmware upgrade capability 75
140 Upload firmware 76
139 Begin firmware upgrade 77
138 Finish firmware upgrade 78
135 Set acceptance limit 78
99 Begin tables upload 79
98 Upload tables 80
97 Finish tables upload 81
96 Request modules information 81
4 Request comms revision 84
3 Clear comms status variables 85
2 Request comms status variables 85
1 Reset device 87
Table 4: Commands not accepted in “Secure Mode”
Header Command Page

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 18
(decimal)
216 Request data storage availability 47
215 Read data block 48
214 Write data block 49
202 Teach mode control 56
201 Request teach status 57
185 Modify coin id 67
181 Modify security setting 69
180 Request security setting 70
179 Modify bank select 71
178 Request bank select 72
140 Upload firmware 76
139 Begin firmware upgrade 77
138 Finish firmware upgrade 78
99 Begin tables upload 79
98 Upload tables 80
97 Finish tables upload 81
Table 5: Modified commands in “L66 compatibility” mode
Header
(decimal) Command Observations Page
248 Request status Not available 24
237 Read Input lines Available only in “L66
compatibility” mode 30
236 Read opto states Funcionamiento modificado ¡Erro
r!
Marc
ador

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 19
no
defin
ido.
228 Modify master inhibit status Not available 40
227 Request master inhibit status Not available 41
222 Modify sorter override status Not available 43
221 Request sorter override status Not available 45
213 Request option flags Not available 50
212 Request coin position Not available 51
199 Configuration to EEPROM Not available 58
198 Counters to EEPROM Not available 59
197 Calculate ROM checksum Not available 60
196 Request creation date Not available 60
195 Request last modification date Not available 60
194 Request reject counter Not available 61
193 Request fraud counter Not available 62
189 Modify default sorter path Not available 63
188 Request default sorter path Not available 65
176 Request alarm counter Not available 66
170 Request base year Not available 72
162 Modify inhibit and override
registers
Not available 73
135 Set acceptance limit Not available 75
3 Clear comms status variables Not available 78
2 Request comms status variables Not available 85

E 10210 12 - 2005
Protocols: MODULAR X6 CCTALK VALIDATOR 20
5.1 SIMPLE POLL [254]
Command for checking communication is working correctly and for confirming the presence in
the bus of a Validator.
Send: [Dir] [0] [1] [254] [Chk]
Reply: [1] [0] [Dir] [0] [Chk] →ACK without data
In the case that no answer is received to the request sent (reception timeout in the
Machine) it will be a sign that the corresponding validator is faulty or not connected.
The Validator always responds to this command: command not protected by a PIN.
5.2 ADDRESS POLL [253]
This command is used to request all the slave devices to return their addresses. To do this, it
is sent with destination address 0 (Broadcast). To avoid collisions, only the byte of address is
returned with a delay proportional to the value of the address.
Send: [0] [0] [1] [253] [2]
Reply: {Delay variable} [Dir]
Where: Dir = address of the corresponding validator
The algorithm to calculate the delay with which it responds is the following:
Deactivate port rx
Delay (4*Dir) ms
Send [Dir]
Delay 1200 – (4*Dir) ms
Activate port Rx