Grupo Azkoyen MODULAR X6 CCTALK Manual
  1. Manuals
  2. Brands
  3. Grupo Azkoyen Manuals
  4. Bank Note Validator
  5. MODULAR X6 CCTALK
  6. Manual

Grupo Azkoyen MODULAR X6 CCTALK Manual

Hide thumbs
Table of Contents

Advertisement

Quick Links

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

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MODULAR X6 CCTALK and is the answer not in the manual?

Questions and answers

Related Manuals for Grupo Azkoyen MODULAR X6 CCTALK

Summary of Contents for Grupo Azkoyen MODULAR X6 CCTALK

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

  • Page 2: Table Of Contents

    Protocols: MODULAR X6 CCTALK VALIDATOR INDEX CCTALK® SERIAL COMMUNICATION PROTOCOL ............. 6 Introduction ....................6 PHYSICAL LEVEL ................8 Voltage levels and transmission speeds ............. 8 Connector ..................... 8 LOGIC LEVEL ................. 10 Message structure ..................10 Destination address ..................10 Number of data bytes ...................
  • Page 3 Protocols: MODULAR X6 CCTALK VALIDATOR 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...
  • Page 4 Protocols: MODULAR X6 CCTALK VALIDATOR 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...
  • Page 5 Protocols: MODULAR X6 CCTALK VALIDATOR 5.68 CLEAR COMMS STATUS VARIABLES [ 3 ] ............85 5.69 REQUEST COMMS STATUS VARIABLES [ 2 ] ............. 85 5.70 RESET DEVICE [ 1 ] ..................87 TELE-PROGRAMMING PROCESS ................. 87 FIRMWARE PROGRAMMING PROCESS ..............89...

  • Page 6: Cctalk® Serial Communication Protocol

    Protocols: MODULAR X6 CCTALK VALIDATOR CCTALK® SERIAL COMMUNICATION PROTOCOL This technical manual comprises the serial communication protocol cctalk® implemented on the X6 validators. 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.
  • Page 7 Protocols: MODULAR X6 CCTALK VALIDATOR 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.

  • Page 8: Physical Level

    Protocols: MODULAR X6 CCTALK VALIDATOR PHYSICAL LEVEL 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.
  • Page 9 Protocols: MODULAR X6 CCTALK VALIDATOR 10 pins connector, equivalent to Molex serial 862, P/N 10-89-1101 (10µ gold). The description is as follows: NAME DESCRIPTION /DATA Data line N.C. Not connected Sorter coil 1 Sorter coil 3 N.C. Not connected Sorter coil 2...

  • Page 10: Logic Level

    Protocols: MODULAR X6 CCTALK VALIDATOR LOGIC LEVEL 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.

  • Page 11: Number Of Data Bytes

    Protocols: MODULAR X6 CCTALK VALIDATOR 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).

  • Page 12: Data

    Protocols: MODULAR X6 CCTALK VALIDATOR 6: BUSY, the Validator is busy doing an operation and cannot attend the command. 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.

  • Page 13: Start Up Procedure

    Protocols: MODULAR X6 CCTALK VALIDATOR 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.

  • Page 14: List Of Commands

    Protocols: MODULAR X6 CCTALK VALIDATOR 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.
  • Page 15 Protocols: MODULAR X6 CCTALK VALIDATOR : LIST OF COMMANDS Table 1 Header Command Page (decimal) Simple Poll Address Poll Address Clash Address Change Address Random Request polling priority Request status Request manufacturer id Request equipment category id Request product code...
  • Page 16 Protocols: MODULAR X6 CCTALK VALIDATOR Read buffered credit or error codes Modify master inhibit status Request master inhibit status Request insertion counter Request accept counter Modify sorter override status Request sorter override status Enter new a PIN number Enter a PIN number...
  • Page 17 Protocols: MODULAR X6 CCTALK VALIDATOR Request default sorter path Modify coin id Request coin id Modify security setting Request security setting Modify bank select Request bank select Request alarm counter Request base year Request address mode Modify inhibit and override registers...
  • Page 18 Protocols: MODULAR X6 CCTALK VALIDATOR (decimal) Request data storage availability Read data block Write data block Teach mode control Request teach status Modify coin id Modify security setting Request security setting Modify bank select Request bank select Upload firmware Begin firmware upgrade...
  • Page 19 Protocols: MODULAR X6 CCTALK VALIDATOR defin ido. Modify master inhibit status Not available Request master inhibit status Not available Modify sorter override status Not available Request sorter override status Not available Request option flags Not available Request coin position Not available...

  • Page 20: Simple Poll [254]

    Protocols: MODULAR X6 CCTALK VALIDATOR 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.

  • Page 21: Address Clash [252]

    Protocols: MODULAR X6 CCTALK VALIDATOR If the Machine receives all the bytes 1.5 seconds after sending the command, it can determine the quantity and the addresses of the devices connected. The Validator always responds to this command: command not protected by a PIN Notes: a) The Validator will not receive any more commands until 1.2 seconds after having...

  • Page 22: Address Change [251]

    Protocols: MODULAR X6 CCTALK VALIDATOR Although there exists the possibility that two devices share the same address generate the same random number, the probability that this occurs is very small (1 in 254*256 = 1 in 65.024). The Validator always answers to this command: command not protected by a PIN.

  • Page 23: Address Random [250]

    Protocols: MODULAR X6 CCTALK VALIDATOR d) If the new address is 0 or 1 the Validator takes the default address (2). Example: The Machine programmes the Validator whose address is 3 with the new address 13 Send: [3] [1] [1] [251] [13] [243]...

  • Page 24: Request Polling Priority [249]

    Protocols: MODULAR X6 CCTALK VALIDATOR Example: The Machine indicates to the Validator whose address is number 3 that it will be programmed with a random value. Send: [3] [0] [1] [250] [2] Reply: [1] [0] [3] [0] [252] After the reply the Validator is programmed with a random address.

  • Page 25: Request Manufacturer Id [246]

    Protocols: MODULAR X6 CCTALK VALIDATOR Where Dir = address of the corresponding validator Data 1 = Status shown in Table 6 Table 6: Status codes Code Status O.K. Coin return mechanism activated String detector system activated Command protected by a PIN.

  • Page 26: Request Equipment Category Id [245]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 2 = ’Z’ Data 3 = ’K’ Two strings can be returned: the default value – ‘AZK’ and a string whose value is programmed in the Factory (maximum 10 characters) Command protected by a PIN.

  • Page 27: Request Database Version [243]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 1 - Data n = ASCII characters n = Quantity of data to send Two strings are returned: the default value (‘X6’: 2 characters) and a string whose value is programmed in the Factory or with the user tools (maximum 20 characters) Command protected by a PIN.

  • Page 28: Request Serial Number [242]

    Protocols: MODULAR X6 CCTALK VALIDATOR 5.12 REQUEST SERIAL NUMBER [242] In reply to this command, the serial number of the Sensor module is returned. This number is required to generate the corresponding data for tele-programming this Sensor module in the Factory.

  • Page 29: Test Solenoids [240]

    Protocols: MODULAR X6 CCTALK VALIDATOR Product code: same string that the command REQUEST PRODUCT CODE [244] returns, followed by the string “ cctalk”. String ‘Vxx.y’ indicating the software version of the Exit module. ‘xx’ corresponds to the version. ‘.’ is a separator. ‘y’ corresponds to the subversion.

  • Page 30: Read Input Lines [237]

    Protocols: MODULAR X6 CCTALK VALIDATOR Each solenoid is activated for 500 ms. if the corresponding bit is at “1”. The ACK reply of the Validator is produced after the end of the command, 2 seconds maximum in depends of the number of solenoids to activate.

  • Page 31: Read Opto States [236]

    Protocols: MODULAR X6 CCTALK VALIDATOR Where: Dir = address of the corresponding validator Data 1 = Values Bit 0 – Bit 3: always at 0 (is equivalent to closed switches) Bit 4: String detector mechanism (0 = closed / 1 = open) The X6 validator does not have any switches, thus it returns always 0: closed switches Command protected by a PIN.

  • Page 32: Perform Self-Check [232]

    Protocols: MODULAR X6 CCTALK VALIDATOR If the optic beam is blocked the value of the corresponding bit is 1 and is returned 0 if the beam is not blocked. The Bit 3 is only used if the Validator is NOT programmed in “L66 compatibility” mode. The L66-cctalk Validator does not make any test of the string detector in this command.
  • Page 33 Protocols: MODULAR X6 CCTALK VALIDATOR Data 2 = Complementary error code The different error codes are presented in Table 7. Table 7: Hardware Test – Error Codes Complementary Type of Error Information Code [Data 1] [Data 2] OK (no fault has been detected )
  • Page 34 Protocols: MODULAR X6 CCTALK VALIDATOR Fault in temperature sensor of the Sensor module. Hardware test not valid: Validator is measuring a coin in the Sensor module If the code 255 is returned (Code of a non specific fault), it means that is has carried out a hardware test with a coin in the interior of the Sensor module.

  • Page 35: Modify Inhibit Status [231]

    Protocols: MODULAR X6 CCTALK VALIDATOR The Machine requests to Validator 2 to carry out a Hardware Test: Send: [2] [0] [1] [232] [21] Reply: [1] [2] [2] [0] [2] [3] [246] The Validator informs that it has detected an error in electromagnetic sensor number 3: (reply = 3: 0000.0100B)

  • Page 36: Request Inhibit Status [230]

    Protocols: MODULAR X6 CCTALK VALIDATOR bit 7 (in Data 1): coin 8 bit 8 (in Data 2, equivalent to bit 0 of Data 2): coin 9 bit 9 (in Data 2, equivalent to bit 1 of Data 2): coin 10 bit 15 (in Data 2, equivalent to bit 7 of Data 2): coin 16 The inhibit data is saved in RAM.

  • Page 37: Read Buffered Credit Or Error Codes [229]

    Protocols: MODULAR X6 CCTALK VALIDATOR Reply: [1] [2] [Dir] [0] [Data 1] [Data 2] [Chk] -> ACK with 2 data Where Dir = address of the corresponding validator [Data 1] = Inhibit Byte 1 (LSB: coins 1 to 9) [Data 2] = Inhibit Byte 2 (MSB: coins 10 to 16) The coins that are activated have the bit at “1”.
  • Page 38 Protocols: MODULAR X6 CCTALK VALIDATOR the Machine to carry out the request at a speed faster than the introduction of coins and not lose any information of credits or events. Send: [Dir] [0] [1] [229] [Chk] Reply: [1] [11] [Dir] [0] [Data 1] [Data 2] ... [Data 11] [Chk] ->...
  • Page 39 Protocols: MODULAR X6 CCTALK VALIDATOR In Table 8 the error codes that give information on the possible causes of the rejection of the coin are presented. Table 8: Command Read Buffered Credit: Error codes Code Error Empty event (no error)

  • Page 40: Modify Master Inhibit Status [228]

    Protocols: MODULAR X6 CCTALK VALIDATOR No coin is accepted until the command READ BUFFERED CREDIT OR ERROR CODES [229] is received. Each time the first command is received (229) the validator can accept coins and starts a timer that if 1 second passes without receiving this command the validator stops accepting coins.

  • Page 41: Request Master Inhibit Status [227]

    Protocols: MODULAR X6 CCTALK VALIDATOR Reply: [1] [0] [Dir] [0] [Chk] -> ACK without data Where Dir = address of the corresponding validator Only bit 0 of Data1 is used. Data1.bit0 = 0: Inhibit activated, coins not accepted Data1.bit0 = 1: Normal working mode.

  • Page 42: Request Insertion Counter [226]

    Protocols: MODULAR X6 CCTALK VALIDATOR b) This bit will be at 0: normal working mode, after a reset or power-up. c) The Validator does not answer if it is programmed in “L66 compatibility” mode. 5.23 REQUEST INSERTION COUNTER [226] This command requests the Validator for information about the counter of coins inserted:...

  • Page 43: Request Accept Counter [225]

    Protocols: MODULAR X6 CCTALK VALIDATOR Reply: [1] [3] [2] [0] [208] [57] [2] [197] From this reply we deduce that the validator has detected the insertion of 145.872 coins: LSB = 208, 2SB = 57, MSB = 2. If now the command COUNTERS TO EEPROM [198] is used:...

  • Page 44: Modify Sorter Override Status [222]

    Protocols: MODULAR X6 CCTALK VALIDATOR Notes: a) A NACK is returned if the Exit module does not have its software correctly loaded 5.25 MODIFY SORTER OVERRIDE STATUS [222] This command is not available if the Validator is programmed in “L66 compatibility” mode.

  • Page 45: Request Sorter Override Status [221]

    Protocols: MODULAR X6 CCTALK VALIDATOR The value of the default classification path is indicated to the Validator using the command MODIFY DEFAULT SORTER PATH [189]. Command protected by a PIN. Notes: a) A NACK is returned if the Exit module does not have its software correctly loaded..

  • Page 46: Enter A New Pin Number [219]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 1. Bit7 = Path 8 Bit = 1: path permitted. Bit = 0: path prohibited. These values can be modified using the command MODIFY SORTER OVERRIDE STATUS [222]. Command protected by a PIN. Notes: a) A NACK is returned if the Exit module does not have its software correctly loaded.

  • Page 47: Enter A Pin Number [218]

    Protocols: MODULAR X6 CCTALK VALIDATOR Reply: [1] [0] [Dir] [0] [Chk] -> ACK without data Where Dir = address of the corresponding validator Data 1, Data 2, Data 3, Data 4: new PIN number This command is protected by a PIN, so to execute it, it is necessary to have previously introduced the PIN stored in the Validator (see command ENTER A PIN NUMBER [218].

  • Page 48: Request Data Storage Availability [216]

    Protocols: MODULAR X6 CCTALK VALIDATOR 5.29 REQUEST DATA STORAGE AVAILABILITY [216] Command not available in “Secure Mode”. The Validator has one zone into its Flash memory used only for data storage from the Machine. Using this command the Machine can be informed about the type of memory and the...

  • Page 49: Read Data Block [215]

    Protocols: MODULAR X6 CCTALK VALIDATOR Command protected by a PIN. Notes: a) A NACK is returned if the Exit module does not have its software correctly loaded b) This command is not available if the Validator is working in “Secure Mode”.

  • Page 50: Write Data Block [214]

    Protocols: MODULAR X6 CCTALK VALIDATOR The Exit module does not have its software correctly loaded It is requested to read data out of the user zone or the number of bytes to be read is 0. b) This command is not available if the Validator is working in “Secure Mode”.

  • Page 51: Request Option Flags [213]

    Protocols: MODULAR X6 CCTALK VALIDATOR Command protected by a PIN. The response time is 5 mseg. approximately Notes: a) A NACK is returned if: The Exit module does not have its software correctly loaded It is requested to write data out of the user zone or the number of bytes to write is 0.

  • Page 52: Modify Sorter Paths [210]

    Protocols: MODULAR X6 CCTALK VALIDATOR Using this command the Validator informs the Machine what the inhibit bit corresponding to the coin code is: Send: [Dir] [1] [1] [212] [Data 1] [Chk] Reply: [1] [2] [Dir] [0] [Data 2] [Data 3] [Chk] -> ACK with two data...
  • Page 53 Protocols: MODULAR X6 CCTALK VALIDATOR Where Dir = address of the corresponding Validator [Data 1] = Code of coin [Data 2] = Path of sorter assigned. If the assigned classification path (Data 2) is prohibited the coin will go to the default path.
  • Page 54 Protocols: MODULAR X6 CCTALK VALIDATOR 1: sorter path 1 2: sorter path 2 3: sorter path 3 4: sorter path 4 5: sorter path 5 To permit or prohibit a determined path the command MODIFY SORTER OVERRIDE STATUS [222], is used.

  • Page 55: Request Sorter Paths [209]

    Protocols: MODULAR X6 CCTALK VALIDATOR The Machine configures the Validator number 2 so that coin 6 is sent to sorter path 1. If it is busy it should leave through path 2 and if this is also busy it should leave through path 3. If this is busy it should be sent to the default path.

  • Page 56: Teach Mode Control [202]

    Protocols: MODULAR X6 CCTALK VALIDATOR a) A NACK is returned if the Exit module does not have its software correctly loaded. Example: The Machine requests Validator number 2 for information about the assigned sorter path of a coin with code 6.

  • Page 57: Request Teach Status [201]

    Protocols: MODULAR X6 CCTALK VALIDATOR All introduced coins will be accepted by the Validator. The state of the auto programming of coins can be consulted using the command REQUEST TEACH STATUS [201]. Command protected by a PIN. Notes: a) A NACK is returned if: - The Exit module does not have its software correctly loaded.

  • Page 58: Configuration To Eeprom [199]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 3 = code of state as explained in Table 9: Table 9: Auto programming state Code Error Auto programming cancelled Error in the Auto programming Auto programming in progress Auto programming completed As the possibility of the machine finishing the Auto programming command does not exist, this is finalised on introducing 25 coins.

  • Page 59: Counters To Eeprom [198]

    Protocols: MODULAR X6 CCTALK VALIDATOR Only the configuration of paths permitted and prohibited is implemented at the moment. See command MODIFY SORTER OVERRIDE STATUS [222]. This configuration will be read after a reset or power-up. If this command is not used, the configuration data corresponds to the default data: all the paths are prohibited.

  • Page 60: Calculate Rom Checksum [197]

    Protocols: MODULAR X6 CCTALK VALIDATOR At the moment of receiving the command it writes the present value of the counters in memory. Said counters are read from the Flash memory immediately after a reset or power- up. Initially they are at 0.

  • Page 61: Request Creation Date [196]

    Protocols: MODULAR X6 CCTALK VALIDATOR a) The checksum only includes the programme area of the Exit module. The tables and data programming are not included. In consequence, any modification of the tables in the Validator or of the data does not modify the checksum calculated.

  • Page 62: Request Last Modification Date [195]

    Protocols: MODULAR X6 CCTALK VALIDATOR - The Exit module does not have its software correctly loaded. - The Validator does not have its tables correctly programmed. b) The Validator does not answer if it is programmed in “L66 compatibility” mode.

  • Page 63: Request Fraud Counter [193]

    Protocols: MODULAR X6 CCTALK VALIDATOR Where Dir = address of the corresponding validator Data 1 = number of coins rejected (LSB) Data 2 = number of coins rejected (2SB) Data 3 = number of coins rejected (MSB) The validator keeps a counter with the number of coins rejected by different reasons than not being in the tables: inhibited coins, string detector mechanism activated, etc.

  • Page 64: Request Build Code [192]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 3 = number of coins rejected (MSB) The validator keeps a counter with the number of coins rejected for not being in the coin tables: it is assumed that these coins are fraud attempts. This counter is of three bytes and can store up to 16.777.215 coins.

  • Page 65: Modify Default Sorter Path [189]

    Protocols: MODULAR X6 CCTALK VALIDATOR Notes: a) A NACK is returned if something of the following occurs: the Exit module does not have its software correctly loaded or does not have its tables correctly programmed The Sensor module does not answer, its software is not correctly loaded or its tables are not correctly programmed.

  • Page 66: Request Default Sorter Path [188]

    Protocols: MODULAR X6 CCTALK VALIDATOR The value of the default classification path is stored in the Flash memory of the Validator. The values that [Data 1] should take are one of the following: 1: path 1 2: path 2 3: path 3...

  • Page 67: Modify Coin Id [185]

    Protocols: MODULAR X6 CCTALK VALIDATOR This command requests the Validator for information about the default classification path to which the coins are sent. Send: [Dir] [0] [1] [188] [Chk] Reply: [1] [1] [Dir] [0] [Data 1] [Chk] -> ACK with a data...

  • Page 68: Request Coin Id [184]

    Protocols: MODULAR X6 CCTALK VALIDATOR Command protected by a PIN. Notes: a) A NACK is returned if: - The Exit module does not have its software correctly loaded - The Exit module does not have its tables correctly programmed. - It has received an incorrect coin code - There has been an error in the programming of the Flash memory of the Validator.

  • Page 69: Modify Security Setting [181]

    Protocols: MODULAR X6 CCTALK VALIDATOR Notes: a) A NACK is returned if: - The Exit module does not have its software correctly loaded - The Exit module does not have its tables correctly programmed. - It has received an incorrect coin code 5.50 MODIFY SECURITY SETTING [181]...

  • Page 70: Request Security Setting [180]

    Protocols: MODULAR X6 CCTALK VALIDATOR The modification of the level of security or band of admission is carried out gradually indicating to the Validator how much it should increase or decrease the present level of security. It is necessary to take into consideration the following: - The value 0 indicates to the Validator that the band of acceptance is “Normal Band”.

  • Page 71: Modify Bank Select [179]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 2 = -1: Wide band 0: Normal band (default) 1: Narrow band 2: Super narrow band The modification process of security level and its characteristics is indicated in the command MODIFY SECURITY SETTING [181].

  • Page 72: Request Bank Select [178]

    Protocols: MODULAR X6 CCTALK VALIDATOR Notes: a) A NACK is returned if: - The Exit module does not have its software correctly loaded - The Exit module does not have its tables correctly programmed. - It has received an incorrect bank number - There has been an error to the programming of the Flash memory of the Validator.

  • Page 73: Request Base Year [170]

    Protocols: MODULAR X6 CCTALK VALIDATOR This command requests the Validator for information about the number of times that an alarm situation has occurred in the validator. Send: [Dir] [0] [1] [176] [Chk] Reply: [1] [1] [Dir] [0] [Data 1] [Chk] ->...

  • Page 74: Request Address Mode [169]

    Protocols: MODULAR X6 CCTALK VALIDATOR The Machine requests the Validator for information about the base year, from which the calculation of dates is carried out: Send: [Dir] [0] [1] [170] [Chk] Reply: [1] [4] [Dir] [0] [‘2’] [‘0’] [‘0’] [‘0’] [Chk] -> ACK with 4 data...

  • Page 75: Modify Inhibit And Override Register [162]

    Protocols: MODULAR X6 CCTALK VALIDATOR The validator returns the value 132 (decimal) = 0x84 (hexadecimal) = 1000.0100 (binary) Command protected by a PIN. 5.57 MODIFY INHIBIT AND OVERRIDE REGISTER [162] This command is not available if the Validator is programmed in “L66 compatibility” mode.

  • Page 76: Upload Firmware [140]

    Protocols: MODULAR X6 CCTALK VALIDATOR Send: [Dir] [0] [1] [141] [Chk] Reply: [1] [1] [Dir] [0] [Data 1] [Chk] -> ACK with a data Where Dir = address of the corresponding validator Data = 1: Firmware in Flash memory 0: Firmware not updateable if the Validator is working in “Secure Mode”.

  • Page 77: Begin Firmware Upgrade [139]

    Protocols: MODULAR X6 CCTALK VALIDATOR The values corresponding to Data 1 and Data 2 (block and line counter) are not used by the Validator. The control of the integrity of the data is in the block of data provided by Azkoyen.

  • Page 78: Finish Firmware Upgrade [138]

    Protocols: MODULAR X6 CCTALK VALIDATOR a) A NACK is returned if the Validator has not been able to start the modification of the firmware. b) This command is not available if the Validator is working in “Secure Mode”. 5.61 FINISH FIRMWARE UPGRADE [138] Command not available in “Secure Mode”.

  • Page 79: Begin Tables Upload [99]

    Protocols: MODULAR X6 CCTALK VALIDATOR The Validator will not accept any coin once it has reached the maximum number of accepted coins, indicated in [Data 1]. Every valid inserted coin will be rejected and the code returned will be 127+n (inhibited coin). See paragraph 5.20- READ BUFFERED CREDIT OR ERROR CODES [229].

  • Page 80: Upload Tables [98]

    Protocols: MODULAR X6 CCTALK VALIDATOR Note: a) A NACK is returned if the Validator does not have its software correctly loaded or there has been an error in starting the modification of the tables of the Validator. c) This command is not available if the Validator is working in “Secure Mode”.

  • Page 81: Finish Tables Upload [97]

    Protocols: MODULAR X6 CCTALK VALIDATOR - There has been an error in programming the Flash memory of the Validator. b) After the coin tables of the Validator have been modified, any coin introduced will be rejected. c) This command is not available if the Validator is working in “Secure Mode”.
  • Page 82 Protocols: MODULAR X6 CCTALK VALIDATOR The meaning of the data transmitted by the Validator is the following: Data 1: Type of Validator. The value transmitted by the A6-cctalk validator is the character ‘8’. Data 2: Type of sensor system the Sensor module has. The most usual values are the following: - ‘E’: High performance...
  • Page 83 Protocols: MODULAR X6 CCTALK VALIDATOR Data 32 – 45: String of 14 chars: - “00000000-0,v00” if something of the following occurs: The Sensor module has its firmware incomplete or it does not respond, the Exit module has its firmware incomplete, the Validator is not or bad programmed or the data configuration are not valid.

  • Page 84: Request Comms Revision [ 4 ]

    Protocols: MODULAR X6 CCTALK VALIDATOR Incorrect values of the Exit Module configuration data (user data) Countries id. of the coin programming not compatible The programming data references of the Sensor Module and Exit Module are not coincident The data received by the Validator is used by the corresponding programming tools to obtain the coin programming data files and the firmware data files.

  • Page 85: Clear Comms Status Variables [ 3 ]

    Protocols: MODULAR X6 CCTALK VALIDATOR Data 2 = Major revision Data 3 = Minor revision Dir = address of the corresponding validator The version presently implemented is: Level = 1 Major revision = 4 Minor revision = 3 Command protected by a PIN.
  • Page 86 Protocols: MODULAR X6 CCTALK VALIDATOR Reply: [1] [3] [Dir] [0] [Data 1] [Data 2] [Data 3] [Chk] -> ACK with 3 data Where Dir = address of the corresponding validator Data 1 = Rx_timeouts Data 2 = Rx_bytes_ignored Data 3 = Rx_bad_checksum - Rx_timeouts: this counter accumulates the number of times the validator gives a time- out in the reception of data.

  • Page 87: Reset Device [ 1 ]

    Protocols: MODULAR X6 CCTALK VALIDATOR 5.70 RESET DEVICE [ 1 ] This command makes the Validator carry out a hardware reset. At the moment of execution the Validator programme goes into the reset vector. The affected Validator sends an ACK string immediately before carrying out the reset.
  • Page 88 Protocols: MODULAR X6 CCTALK VALIDATOR [n][cctalk command n][Data 1n]... [Data n]: string 1 [m][cctalk command m][Data 1m]... [Data m]: string 2 [x][cctalk command x][Data 1x]... [Data x]: string z Each string has: [n]: number of bytes to transmit to the Validator [cctalk command n]: cctalk command to transmit to the Validator [Data 1]...

  • Page 89: Firmware Programming Process

    Protocols: MODULAR X6 CCTALK VALIDATOR FIRMWARE PROGRAMMING PROCESS When it is necessary to modify the firmware of the Validator (the Sensor module and the Exit module) due to updates or error corrections, Azkoyen will provide a file with the data to transmit to the Validator.

Table of Contents