100% found this document useful (1 vote)
1K views26 pages

NV10USB Software Implementation Guide

NV10 USB Software Implementation Guide

Uploaded by

Apple Pie
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
1K views26 pages

NV10USB Software Implementation Guide

NV10 USB Software Implementation Guide

Uploaded by

Apple Pie
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SECTION

NV10 USB
MANUAL SET
SOFTWARE
IMPLEMENTATION
GUIDE

NV10 USB Manual Set Section 5

NV10 USB MANUAL SET SECTION 5


5.

SOFTWARE IMPLEMENTATION GUIDE

5.1

Communication Protocols

5.2

Configuration Card Programming

5.3

SSP and eSSP

13

5.4

ccTalk

19

5.5

Escrow Control

22

5.6

SSP Escrow Function

23

5.7

Credit Hold Function

23

5.8

Connection Options

24

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.

SOFTWARE IMPLEMENTATION GUIDE

5.1

Communication Protocols

The NV10 USB validator can use several different communication protocols, including
eSSP, SIO, ccTalk, MDB, Parallel, Binary and Pulse. Use of the MDB protocol requires
the use of an external IF5 interface unit.
Smiley Secure Protocol (SSP) is a secure serial interface specifically designed to
address the problems experienced by cash systems in gaming machines. Problems
such as acceptor swapping, reprogramming acceptors and line tapping are all
addressed.
Encrypted Smiley Secure Protocol (eSSP) is an enhancement of SSP. eSSP uses the
same 16 bit CRC checksums on all packets as SSP, but also uses a Diffie-Hellman key
exchange to allow the host machine and validator to jointly establish a shared secret
key over an insecure communications channel. The encryption algorithm used is AES
with a 128-bit key; this provides a very high level of security.
The recommended communication protocol for the NV10 USB validator is eSSP, as this
provides the highest level of data transfer security. A ccTalk interface protocol is also
available.
For detailed information and the full protocol specifications please read the following
documents, which can be downloaded from the Innovative Technology Ltd website
([Link]):

SSP Interface Specification (ITL Document number GA138)

ITL Bank Note Reader ccTalk Specification (ITL Document number GA966)

Summaries of the NV10 USB validator socket connections for the supported interfaces
are shown below:
WARNING!
Risk of unit damage

Information
Encryption of data strongly
recommended

Do not make any connections to the interface socket


pins marked Do not connect making connections
to these pins could cause severe damage to the unit.

It is recommended that all transactions with the NV10


USB validator be encrypted to prevent commands
being recorded and replayed by an external device. If
this is not possible, then other (mechanical) measures
should be used to prevent physical bus tapping.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

NV10 USB SSP Interface:


Pin
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Name
Vend 1

Type
Output

Factory use only


Inhibit 1

Do not connect
Input

Factory use only

USB D+
USB DUSB Vcc
Factory use only
V In
GND

Description
Serial data out (Tx)

Serial data in (Rx)

Do not connect

Data
Data
Power
Power
Ground

USB Data +
USB Data USB +V (+5V)
Do not connect
+V
GND

NV10 USB ccTalk Interface:


Pin

Name

Vend 1

2
3
4

Factory use only

Inhibit 1

6
7
8
9
10
11
12
13
14
15
16

Type
Output

Do not connect
Input

Factory use only

USB D+
USB DUSB Vcc
Factory use only
V In
GND

Description
Serial data must also be
connected to pin 5

Serial data must also be


connected to pin 1

Do not connect

Data
Data
Power
Power
Ground

Copyright Innovative Technology Ltd 2013

USB Data +
USB Data USB +V (+5V)
Do not connect
+V
GND

GA00450-4

NV10 USB Manual Set Section 5

NV10 USB SIO Interface:


Pin
Name
Type
Description
1
Vend 1
Output
Serial data
2
3
Factory use only
Do not connect
4
5
Inhibit 1
Input
Serial data
6
7
8
Factory use only
Do not connect
9
10
11
USB D+
Data
USB Data +
12
USB DData
USB Data 13
USB Vcc
Power
USB +V (+5V)
14
Factory use only
Do not connect
15
V In
Power
+V
16
GND
Ground
GND
When operating with this interface, the host machine does not echo messages
back to the validator, and the NV10 USB does not operate in true RS232 mode
(only TTL level).

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

NV10 USB Pulse Interface:


Pin
1
2
3
4

Name
Vend 1

Type
Output

Factory use only

Do not connect

Inhibit 1

Input

Inhibit 2

Input

Inhibit 3

Input

Inhibit 4

Input

Busy

Output

10

Escrow

Input

11
12
13
14
15
16

Factory use only


V In
GND

Description
Credit pulse stream output

Inhibit Channel 1 by holding this


pin HIGH
Inhibit Channel 2 by holding this
pin HIGH
Inhibit Channel 3 by holding this
pin HIGH
Inhibit Channel 4 by holding this
pin HIGH
Busy signal output is pulled
low when the validator is busy
Enable Escrow function by
holding this pin LOW
Do not connect

Power
Ground

+V
GND

When operating in Pulse mode the NV10 USB outputs a number of pulses on Vend 1.
The number of pulses for each channel is different and set to default values within the
dataset. The number of pulses and the pulse duration can be modified using the Bank
Note Validator Currency Manager Software, and a maximum of 16 channels can be
used.
NV10 USB Multi Drop Bus (MDB) Interface:
MDB is a serial bus interface commonly used in electrically controlled vending
machines. This is a 9600 Baud Master Slave system where the NV10 USB validator
is a slave to master controller.
To use the NV10 USB with MDB protocol, an IF5 external interface convertor is
required. The IF5 regulates the power supply and opto-isolates the communication
lines. The NV10 USB validator supports the MDB Protocol Version 1, Level 1.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

NV10 USB Parallel Interface:


Pin

Name

Type

Vend 1

Output

Vend 2

Output

Vend 3

Output

Vend 4

Output

Inhibit 1

Input

Inhibit 2

Input

Inhibit 3

Input

Inhibit 4

Input

Busy

Output

10

Escrow

Input

11
12
13
14
15
16

Factory use only


V In
GND

Description
Channel 1 credit, 100ms active
low pulse
Channel 2 credit, 100ms active
low pulse
Channel 3 credit, 100ms active
low pulse
Channel 4 credit, 100ms active
low pulse
Inhibit Channel 1 by holding this
pin HIGH
Inhibit Channel 2 by holding this
pin HIGH
Inhibit Channel 3 by holding this
pin HIGH
Inhibit Channel 4 by holding this
pin HIGH
Busy signal output is pulled
low when the validator is busy
Enable Escrow function by
holding this pin LOW
Do not connect

Power
Ground

+V
GND

When operating in Parallel mode the NV10 USB will issue a 100ms active LOW pulse
on the relevant vend line, and a maximum of 4 channels can be used. There is also
the option to use a binary output where the NV10 USB will output a binary pattern on
vend lines 1 4. Binary mode can be set as an option using a configuration card or
with the Bank Note Validator Currency Manager Software.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.2

Configuration Card Programming

Please consult ITL technical document GA959 for further information on configuration
card programming the GA959 document includes a printable template for the
configuration card and this can be downloaded from the Support section of the ITL
website the sample shown here should not be used for programming as it
is not to scale.
Configuration Card - instructions
for use:
1. Cut card around the outline check the measurements are as
printed. Make sure that Page
scaling is set to None in your
print options to ensure the
correct size.
2. Fill in sections as required. Take
care to fill in the sections
correctly, keep inside the lines
and fill boxes fully as shown
here:

3. Power-up the validator and wait


until it resets.
4. Press the configuration button
once to enter programming
mode (the bezel LEDs should
flash at 1 second intervals).
5. Insert the card into the validator
face up and in the direction
indicated by the arrows.
6. The configuration card will be
ejected and if the configuration
was good the bezel LEDs will
flash at a fast rate while
programming takes place. After
completion of programming the
validator will reset.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

Information
Check print settings.

Make sure that Page scaling is set to None in your


print options to ensure the correct size when printing
the configuration card.

If an error has occurred, the card will be rejected and the bezel LEDs will flash slowly
a number of times to indicate the cause of the error:
Number
of flashes
2
3
4
5
6
7
8
9

Indicated error
Invalid card read card entered wrong way around, misread or
wrong card version used
No interface selection was detected on the card
Multiple interface selections detected
Invalid interface detected the selected interface is not available
for this validator
Selected interface is not compatible with this validator version
Pulse configuration error selected pulse options are invalid
ccTalk configuration error the selected ccTalk options are invalid
(ccTalk 8 bit checksum not allowed without ccTalk plain)
Low power mode not available for this validator version

WARNING!
Risk of unit damage

When in programming mode, do not turn off the


power before the operation is complete as this will
make the unit unusable.

There are different options available to use with the validator, depending on which
interface is selected. Full details on programming the NV10 USB Validator using
software can be found in Section 3 of this manual set (ITL Software Support Guide)
details of programming the various interfaces by use of configuration card are detailed
on the next pages.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

10

SSP configuration card options:


When using the configuration card to set
SSP mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes

ccTalk configuration card options:


When using the configuration card to set
ccTalk mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes
ccTalk plain fill in this box to use unencrypted ccTalk
ccTalk 8 bit checksum if ccTalk plain is
selected, leave this box blank for 16 bit
CRC checksum. Fill in this box to use
simple 8 bit checksum
No escrow timeout fill in this box to
disable the escrow timeout

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

11

MDB configuration card options:


When using the configuration card to set
MDB mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes

Parallel configuration card options:


When using the configuration card to set
Parallel mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes

Binary fill in this box to enable binary


output mode
No escrow timeout fill in this box to
disable the escrow timeout

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

12

Pulse configuration card options:


When using the configuration card to set
Pulse mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes

Pulse settings set the required pulse


widths and pulse multiplier
Credit hold fill in this box to enable the
credit hold function

SIO configuration card options:


When using the configuration card to set
SIO mode, the following options are
available:

Note inhibits fill in the boxes to inhibit


notes
High speed fill in this box to use high
speed (9600 baud) data transfer rates
output mode

No escrow timeout fill in this box to


disable the escrow timeout

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.3

13

SSP and eSSP

Smiley Secure Protocol (SSP) is a secure serial interface specifically designed to


address the problems experienced by cash systems in gaming machines. Problems
such as acceptor swapping, reprogramming acceptors and line tapping are all
addressed.
Encrypted Smiley Secure Protocol (eSSP) is an enhancement of SSP. eSSP uses the
same 16 bit CRC checksums on all packets as SSP, but also uses a Diffie-Hellman key
exchange to allow the host machine and validator to jointly establish a shared secret
key over an insecure communications channel. The encryption algorithm used is AES
with a 128-bit key; this provides a very high level of security.
The encryption of the SSP protocol ensures superior protection and reliability of the
data, which is transferred between validator and host machine. The encryption key is
divided into two parts:

The lower 64 bits are fixed and specified by the machine manufacturer allowing
control of which devices are used in their machines.

The higher 64 bits are securely negotiated by the slave and host at power up,
ensuring each machine and each session are using different keys.

The interface uses a master-slave model; the host machine is the master and the
peripherals (note acceptor, coin acceptor or coin hopper) are the slaves. Data transfer
is over a multi-drop bus using clock asynchronous serial transmission with simple
open collector drivers. Each SSP device of a particular type has a unique serial
number; this serial number can be checked by the host on start up and receipt of a
credit event to ensure that the device has not been changed.

Information
200 ms command spacing

When communicating with the NV10 USB validator,


poll commands should be sent at least 200 ms
apart.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

14

SSP Commands and Responses


a. Commands
Action

Command Code (Hex)

Reset

0x01

Host Protocol Version

0x06

Poll

0x07

Get Serial Number

0x0C

Synchronisation command

0x11

Disable

0x09

Enable

0x0A

Program Firmware / currency

0x0B (Programming Type)

Set inhibits

0x02

Display On

0x03

Display Off

0x04

Set-up Request

0x05

Reject

0x08

Unit data

0x0D

Channel Value data

0x0E

Channel Security data

0x0F

Channel Re-teach data

0x10

Last Reject Code

0x17

Hold

0x18

Command Set

Generic

Copyright Innovative Technology Ltd 2013

Validator

GA00450-4

NV10 USB Manual Set Section 5

15

Notes:
Action

Comments

Reset:

Single byte command, causes the slave to reset

Host Protocol Version:

Dual byte command, the first byte is the command; the


second byte is the version of the protocol that is
implemented on the host.

Poll:

Single byte command, no action taken except to report


latest events.

Get Serial Number:

Single byte command, used to request the slave serial


number. Returns 4-byte long integer.

Sync:

Single byte command, which will reset the validator to


expect the next sequence ID to be 0.

Disable:

Single byte command, the peripheral will switch to its


disabled state, it will not execute any more commands or
perform any actions until enabled, any poll commands
will report disabled.

Enable:

Single byte command, the peripheral will return to


service.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

16

b. Responses
Action

Command Code (Hex)

OK

0xF0

Command not known

0xF2

Wrong number of parameters

0xF3

Parameter out of range

0xF4

Command cannot be
processed

0xF5, Error Code

Software Error

0xF6

FAIL

0xF8

Key Not Set

0xFA

Slave Reset

0xF1

Read, n

0xEF, Channel Number

Credit, n

0xEE, Channel Number

Rejecting

0xED

Rejected

0xEC

Stacking

0xCC

Stacked

0xEB

Safe Jam

0xEA

Unsafe Jam

0xE9

Disabled

0xE8

Fraud Attempt, n

0xE6, Channel Number

Stacker Full

0xE7

Note cleared from front at


reset

0xE1, Channel Number

Copyright Innovative Technology Ltd 2013

Command Set

Generic

Validator

GA00450-4

NV10 USB Manual Set Section 5

Action

Command Code (Hex)

Note cleared into cash box at


reset

0xE2, Channel Number

Note path open

0xE0

Channel Disable

0xB5

17

Command Set

Validator

Notes:
Action

Comments

Command Not Known: Returned when an invalid command is received by a


peripheral.
Wrong Number Of
Parameters:

A command was received by a peripheral, but an incorrect


number of parameters were received.

Parameter Out Of
Range:

One of the parameters sent with a command is out of


range.

Command Cannot Be
Processed:

A command sent could not be processed at that time


this will return a corresponding error code.

Software Error:

Reported for errors in the execution of software e.g.


Divide by zero. This may also be reported if there is a
problem resulting from a failed remote firmware upgrade,
in this case the firmware upgrade should be redone

Key Not Set:

The slave is in encrypted communication mode but the


encryption keys have not been negotiated

Jammed:

Five-byte response that indicates that the validator is


jammed; this is reported until it is un-jammed or reset. It
will also become disabled.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

18

Example SSP Communications


Here is an example of the communication between host and slave. Both the typical
commands from the host and responses from the validator are detailed.
Host
> SYNC
> SET_GENERATOR, [64 bit

Slave
< OK
< OK

> SET_MODULUS, [64 bit prime

< OK

> REQUEST_KEY_EXCHANGE

< OK, [64bit slave

> GET_SERIAL

< OK < [SERIAL


NUMBER]
< OK < [SETUP
INFORMATION]
< OK
< OK
< OK < DISABLED
< OK
< OK < NOTE READ
< 00
< OK < NOTE READ
< 03
< OK
< OK < STACKING
< OK < CREDIT
<
03 < STACKING <
STACKED
< OK

prime number]
number]

[64 bit host intermediate key]

> SETUP_REQUEST
>
>
>
>
>

SET_INHIBIT > 07 > 00


ENABLE
POLL
POLL
POLL

> POLL
> HOLD
> POLL
> POLL
> POLL

intermediate key]

Comments
Synchronisation command
Set the encryption key
generator
Set the encryption key modulus
Host sends the host
intermediate key, slave
responds with the slave
intermediate key. The
encryption key is then calculated
independently by both host and
slave.
NV10 USB Serial Number
NV10 USB Setup
Enable channels 1,2 and 3
Enable NV10 USB

NV10 USB currently reading a


note
Note has been recognised as
channel 3 (20)
Hold the note in escrow
Stack the note
Credit given for channel 3 (20),
note stacked

Full support is available from ITL and local support offices for implementing eSSP this support includes libraries and example applications. When requesting this
information, please specify your preferred language(s) and operating system.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.4

19

ccTalk

This section should be read in conjunction with the full ccTalk specification, which can
be downloaded from the internet ([Link]).
ccTalk is a serial communications protocol in widespread use throughout the money
transaction industry. Peripherals such as coin acceptors, note validators and hoppers
found in a diverse range of automatic payment equipment use ccTalk to communicate
with the host controller.
The protocol uses an asynchronous transfer of character frames in a similar manner to
RS232. The main difference is that it uses a single two-way communication data line
for half-duplex communication rather than separate transmit and receives lines. It
operates at TTL voltages and is multi-drop (peripherals can be connected to a
common bus and are logically separated by a device address) - each peripheral on the
ccTalk bus must have a unique address.
Each communication sequence (a command or request for information) consists of 2
message packets structured in one of the formats detailed below. The first packet will
go from the master device to the slave device and then a reply will be sent from the
slave device to the master device.
Commands can have 3 primary formats:

8 Bit Checksum No Encryption


16 Bit CRC No Encryption
16 Bit CRC BNV Encryption

As it is possible to use the ccTalk protocol without encryption, suitable physical


security should be employed to protect the ccTalk bus.

Information
200 ms command spacing

When communicating with the NV10 USB validator,


Read Buffered Bill events (command 159) should be
sent at least 200 ms apart.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

20

ccTalk Command Summary


Command

Header

Parameters

Example

Reset Device
Request Comms
Revision
Read Barcode Data
Store Encryption
Code
Switch Encryption
Code
Request Currency
Revision
Operate Bidirectional Motors
Stacker Cycle
Request Bill
Operating Mode
Modify Bill
Operating Table
Route Bill
Request Bill Position

001
004

None
None

ACK
X.Y

129
136

None
None

ACK
ACK

137

ACK

146

3 bytes Encryption
key
None or Country
Code (2 digit)
None

147
152

None
None

ACK
3

153

Escrow & Stacker

ACK

154
155

ACK/254
00000111 00000000

Request Country
Scaling
Request Bill ID
Read Buffered Bill
Events
Request Address
Mode
Request Base Year
Request Build Code
Request Last Mod
Date
Calculate ROM
Checksum
Request Option
Flags
Request Data
Storage Av.
Enter Pin

156
157
159

0/1
Country Code (2
digit)
Country Code (2
digit)
None
None

169

None

170
192
195

None
None
None

2006
161209
00

197

None

4 byte checksum

213

None

3 (stacker & escrow)

216

None

00000

218

ACK

Enter New Pin

219

Request Accept
Count
Request Insertion
Count
Request Master
Inhibit

225

Pin1, Pin2, Pin3,


Pin4
Pin1, Pin2, Pin3,
Pin4
None

226

None

227

None

145

Copyright Innovative Technology Ltd 2013

GBP02113
ACK

100
GB0010A
10000000000

ACK
3

GA00450-4

NV10 USB Manual Set Section 5

21

Command

Header

Parameters

Example

Set Master Inhibit


Request Inhibits

228
230

Bit Mask
None

Set Inhibits
Perform Self Check
Request Software
Version
Request Serial
Number
Request Product
Code
Request Equipment
Category
Request
manufacturer ID
Request Polling
Priority
Simple Poll

231
232
241

Channels
None
None

ACK
Inhibit Low, Inhibit
High
ACK
0
[Link]

242

None

3 byte serial number

244

None

NV9 USB

245

None

Bill Validator

246

None

ITL

249

None

200

254

None

ACK

Monetary Values
Values are represented as 32 bit unsigned integers (4 bytes) and in the lowest value
of currency. For example:
50.00 would be 0x00001388
When sending or receiving a value the least significant byte is sent first. So in this
example [0x88] [0x13] [0x00] [0x00] will be sent.
Each type of note is identified by its value and represented using the standard format
outlined above. As an example, the values for Euro notes are:
Note ()
5.00
10.00
20.00
50.00
100.00
200.00
500.00

Hex value

Data to Send

0x000001F4
0x000003E8
0x000007D0
0x00001388
0x00002710
0x00004E20
0x0000C350

[0xF4] [0x01] [0x00] [0x00]


[0xE8] [0x03] [0x00] [0x00]
[0xD0] [0x07] [0x00] [0x00]
[0x88] [0x13] [0x00] [0x00]
[0x10] [0x27] [0x00] [0x00]
[0x20] [0x4E] [0x00] [0x00]
[0x50] [0xC3] [0x00] [0x00]

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.5

22

Escrow Control

The NV10 USB has a single note escrow facility (pin 10) used in Parallel, Pulse and
Binary modes. This allows the Validator to hold onto the note once accepted, and only
stack the note into the cash box when the host machine confirms that the vend
operation has been completed.
If no confirmation of vend is received then the note will be returned to the customer
after 30 seconds (see the escrow timing diagrams below):

Do not wait
more than 30
seconds for
the 2nd vend
confirmation
signal
Inhibit
rejection can
be at any time
during the 30
second
decision period
after
completion of
the vend
If the host machine itself aborts the transaction by setting the corresponding inhibit
input high, the note is returned immediately.
The sequence of operations is as follows:

Pin 10 is held low awaiting note insertion


Note inserted. Validator issues a 100 ms pulse on the appropriate channel
The host machine initiates the vend process
The host machine sets pin 10 high to indicate that it wants the note. If this is
not done within 30 seconds the Validator will return the note
The Validator issues a 100 ms pulse on the appropriate channel after pin 10
going high to indicate final acceptance of the note. If the signal has not been
received within 30 seconds it indicates the customer has forcibly retrieved the
note and the vend will be aborted
The vend process is completed
The host machine sets pin 10 low ready for the next vend operation

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

23

The host machine can force the return of the note to the customer by setting the
inhibit line high at any time before the end of the 30 second time-out. For channels
above 4 setting all inhibits high will cause a note reject.
In the event of a note being forcibly removed from the mouth of the NV10 USB during
the 30 second interval, the NV10 USB will go out of service for 45 seconds.

5.6

SSP Escrow Function

To hold a note in the escrow position when using SSP, the POLL command should be
replaced with the HOLD (0x18) command after NOTE READ > 0 for as long as the
note is to be held in escrow.
A POLL (0x07) command will then accept the note; the REJECT (0x08) command will
return the note to the customer
5.7

Credit Hold Function

This function is only available if the validator is set to operate in Pulse mode.
If the credit hold function is enabled (either by configuration card or BNV Currency
Manager Program), the validator will take the note as normal but then wait until the
escrow line is toggled low/high. It will then give out the number of pulses per note
denomination as set when programmed. After the pulses have been generated, the
validator will then wait for another low/high toggle until the full value of credit pulses
are given.
As an example, with a setting of 4 pulses per banknote, a 5 euro note will give 4
pulses, 5 times. A typical use of this option would be for a pool table with a game
price of 1. You could insert a 5 note and press a button that toggles the escrow line
and releases the pool balls; this would then allow you to play the first game. The
validator holds onto the remaining credits until the game has finished and the button
is pressed again allowing the next game to begin, this continues until all the credits
have been used.
The busy line remains low throughout the whole process and the validator remains
inhibited until all pulses are given.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set Section 5

5.8

24

Connection Options

The NV10 USB Validator has a single connector that is used to allow interfacing and
programming.
Information
Power always required
regardless of connection
type.

Power is always required on pins 15 and 16 of the


16 way connector.

The connector is a 16 pin socket located on the side of the validator head. This
connector is used to interface the NV10 USB to the host machine. The pin numbering
of the socket is shown below, as well as an overview of the socket connections:

Interface Socket

Pin
1
5
11
12
13
15
16

15

16

Description
Serial Data Out (Tx)
Serial Data In (Rx)
USB Data +
USB Data USB Power (+5V)
+V
0V / Ground Connection

To use a USB connection with the NV10 USB, a USB cable with a 16 way connector on
one end (ITL Part Number CN392) should be used. The CN392 cable fits into the 16
way connector and allows high speed programming and serial communications when
used in SSP, ccTalk and SIO modes.

Copyright Innovative Technology Ltd 2013

GA00450-4

NV10 USB Manual Set

MAIN HEADQUARTERS

Innovative Technology Ltd


Derker Street Oldham England - OL1 4EQ
Tel: +44 161 626 9999 Fax: +44 161 620 2090
E-mail: support@[Link]
Web site: [Link]

BRAZIL
suporte@[Link]
CHINA
support@[Link]
GERMANY
supportDE@[Link]
SPAIN
supportES@[Link]
UNITED KINGDOM
support@[Link]
UNITED STATES OF AMERICA
supportusa@[Link]
REST OF THE WORLD
support@[Link]

Copyright Innovative Technology Ltd 2013

NV10 USB Manual Set

CONFIGURATION CARD

Copyright Innovative Technology Ltd 2013

Common questions

Powered by AI

The 200 ms command spacing requirement ensures reliable communication and prevents command collision or data overload, which is essential for maintaining system stability, especially in high-traffic environments. Failure to adhere to this may result in communication errors or device malfunction. By spacing commands adequately, vending machines can ensure smooth transaction processing under peak loads, minimizing customer wait time and error rates .

In the SSP protocol, setting up inhibits involves sending specific command codes to disable or enable note acceptance. The system uses a command set including 'Set inhibits' that the host must send to configure which denominations are accepted or rejected . In contrast, the ccTalk protocol utilizes command headers and parameter packets to achieve similar outcomes, emphasizing a simpler binary or bitmask approach for logical interpretation by the validator . Each method reflects the unique structural criteria of the protocols where SSP commands focus on secure sessions and ccTalk utilizes broader but precise message packets.

Physical bus security acts as a primary defense preventing unauthorized physical access to communication lines, thus complementing electronic security like eSSP encryption. As electronic measures protect against logical intrusions, physical protections ensure that even if electronic failures occur or encryption is bypassed, physical access remains a limiting factor for unauthorized parties, particularly vital where encryption is not feasible such as with basic ccTalk implementations .

The IF5 interface converter is necessary when using the MDB protocol as it regulates the power supply and opto-isolates the communication lines from the NV10 USB validator. This is crucial for maintaining stable and secure communication between the validator as a slave and the vending machine's controller as the master .

Without encryption, ccTalk communications can be susceptible to eavesdropping, where attackers could intercept and reconstruct sensitive command data. A potential scenario might involve an attacker monitoring communications between a note validator and host controller to capture sensitive transactional commands. Mitigation strategies include implementing mechanical measures like physical security covering communication lines, regularly changing device addresses, and moving to CRC with BNV encryption where possible, to add a layer of security to data exchanges .

A multi-drop bus system allows multiple devices to communicate over a single communication line, reducing the complexity and number of wires needed. This is particularly advantageous in protocols like SSP and ccTalk which enable multiple peripherals to connect to a single host. It supports asynchronous data transfer and logical separation through device addresses, facilitating efficient and scalable system design .

The configuration card allows users to set operational modes such as MDB, Parallel, Pulse, and SIO by filling in specific sections that dictate functions like note inhibition and control over binary output mode. Security implications include the potential for unauthorized changes if card programming is not properly secured or if the procedure for inserting and using these cards is not controlled, as misconfiguration could disrupt proper validator operations or weaken security settings such as disabling escrow timeout .

The NV10 USB validator's escrow function allows the validator to hold onto a note temporarily until the transaction is confirmed as successful by the host machine. This mechanism prevents immediate stacking of notes, thereby giving customers assurance that their cash will only be processed upon successful transaction completion. This can mitigate customer frustration from faulty vend operations or mechanical errors and enhance security by reducing the risk of stacking unvalidated transactions .

The eSSP protocol enhances security by incorporating a Diffie-Hellman key exchange to establish a shared secret key between the host machine and validator over an insecure channel, coupled with AES encryption using a 128-bit key. This method provides a higher level of security compared to SSP, which does not employ such encryption methods. eSSP uses the same 16-bit CRC checksums on all packets like SSP, but adds the encryption layer for additional protection .

Incorrect connections to the NV10 USB validator's interface socket pins can lead to severe damage to the unit, particularly if connections are made to pins marked as 'Do not connect.' These risks can be mitigated by strictly adhering to the connection diagrams provided in the manual and utilizing appropriate protective measures like opto-isolation where possible .

You might also like