STS Advance

User Manual

COPYRIGHT  2018 Crane Payment Innovations. All rights reserved.

The information contained here-in is the property of Crane Payment Innovations and is not to be disclosed or used
without the prior written permission of Crane Payment Innovations. This copyright extends to all the media in
which this information may be preserved including magnetic storage, punched card, paper tape, computer printout
or visual display.
 Table of Contents
1 Document History ..................................................................................................................................................... 5
2 Document Scope ....................................................................................................................................................... 5
3 Product overview ...................................................................................................................................................... 6
3.1 System Requirements ....................................................................................................................................... 6
4 Installation ................................................................................................................................................................ 6
5 Getting Started .......................................................................................................................................................... 6
6 Main Functionality .................................................................................................................................................... 7
6.1 Home Screen Options ....................................................................................................................................... 7
6.2 STS Advance Action Bar .................................................................................................................................... 8
6.3 STS Advance Device Selector BNR .................................................................................................................... 9
7 Product Configuration ............................................................................................................................................. 11
7.1 Build Standard ................................................................................................................................................. 13
7.2 BNR Firmware ................................................................................................................................................. 13
7.3 Device Configuration....................................................................................................................................... 14
7.3.1 Special Configuration .............................................................................................................................. 14
7.4 Bill Settings ...................................................................................................................................................... 14
7.4.1 Adding/deleting denominations ............................................................................................................. 14
7.4.2 Assigning notes to a recycler/loader module ......................................................................................... 15
7.4.3 Changing Physical modules. .................................................................................................................... 16
7.5 Module Threshold Settings ............................................................................................................................. 16
8 Audit ........................................................................................................................................................................ 18
8.1 Audit Selector.................................................................................................................................................. 19
8.2 Audit Export .................................................................................................................................................... 19
8.2.1 Export from summary page .................................................................................................................... 20
8.2.2 Export from home store .......................................................................................................................... 20
8.3 Display Audit Screen ....................................................................................................................................... 21
8.4 BNR Audit Summary Tab ................................................................................................................................. 23
8.4.1 Simple Report .......................................................................................................................................... 25
8.4.2 System ..................................................................................................................................................... 26
8.4.3 System Jams ............................................................................................................................................ 26

Page 2 of 89
 8.4.4 System Failures ....................................................................................................................................... 27
8.4.5 Main Module ........................................................................................................................................... 28
8.4.6 Main Module Bill Intake .......................................................................................................................... 28
8.4.7 Main Module Positioner ......................................................................................................................... 29
8.4.8 Main Module Recognition Sensors ......................................................................................................... 29
8.4.9 Main Module Bottom Transport ............................................................................................................. 30
8.4.10 Main Module Bundler ............................................................................................................................. 30
8.4.11 Spine Module .......................................................................................................................................... 31
8.4.12 Loaders .................................................................................................................................................... 31
8.4.13 Recyclers ................................................................................................................................................. 32
8.5 Audit Details Tab ............................................................................................................................................. 33
8.5.1 System ..................................................................................................................................................... 34
8.5.2 System Jams ............................................................................................................................................ 35
8.5.3 System Failures ....................................................................................................................................... 36
8.5.4 Main Module ........................................................................................................................................... 36
8.5.5 Main Module Bill Intake .......................................................................................................................... 37
8.5.6 Main Module Spine Interface Diverter Cycle Count ............................................................................... 37
8.5.7 Main Module Positioner ......................................................................................................................... 38
8.5.8 Main Module Recognition Sensors ......................................................................................................... 38
8.5.9 Main Module Bottom Transport ............................................................................................................. 38
8.5.10 Main Module Bundler ............................................................................................................................. 39
8.5.11 Loaders .................................................................................................................................................... 40
8.5.12 Recyclers ................................................................................................................................................. 41
8.6 Audit Devices Tab............................................................................................................................................ 42
8.6.1 Overall Performance ............................................................................................................................... 44
8.6.2 Main Module Performance ..................................................................................................................... 45
8.6.3 Spine Performance .................................................................................................................................. 47
8.6.4 Loader and Recycler Performance .......................................................................................................... 49
8.6.5 Cashbox Performance ............................................................................................................................. 50
8.6.6 Denomination Performance ................................................................................................................... 51
8.7 Bulk Load ......................................................................................................................................................... 53

Page 3 of 89
 8.7.1 Adding files to the list ............................................................................................................................. 54
8.7.2 Adding extra data .................................................................................................................................... 55
8.7.3 Removing files from the list .................................................................................................................... 55
8.7.4 Load Files To Screen ................................................................................................................................ 55
8.7.5 Load Files To Store .................................................................................................................................. 55
9 Product Maintenance/Diagnostics ......................................................................................................................... 56
9.1 BNR Diagnostics .............................................................................................................................................. 57
9.2 Module Performance checking ....................................................................................................................... 59
9.3 Calibrate Unit .................................................................................................................................................. 59
9.4 Park Recyclers ................................................................................................................................................. 60
9.5 Update Mfr Serial Number.............................................................................................................................. 61
9.6 Sensor Values .................................................................................................................................................. 61
9.7 Use History ...................................................................................................................................................... 63
9.8 Module Test .................................................................................................................................................... 64
9.8.1.1 Module test action bar operations. .................................................................................................... 67
9.9 Recycler purge................................................................................................................................................. 68
9.10 Note test ......................................................................................................................................................... 69
9.11 Use History ...................................................................................................................................................... 70
9.12 Update Manufacturer Serial Number ............................................................................................................. 71
9.13 Bundler Slippage ............................................................................................................................................. 71
10 STS Advance Settings .......................................................................................................................................... 73
10.1 Application Settings ........................................................................................................................................ 74
10.2 Manage License............................................................................................................................................... 75
10.3 Manage Templates.......................................................................................................................................... 75
10.4 Manage Database ........................................................................................................................................... 76
12 STS Advance Connectivity ................................................................................................................................... 78
12.1 Simplifi Store ................................................................................................................................................... 78
12.2 Product File Catalog ........................................................................................................................................ 79
13 BNR Step by Step Programming Guide ............................................................................................................... 85

Page 4 of 89
1 Document History

Rev Change
1.12 Initial Release BNR
2.0 Added Simplifi, Product Catalog topics

2 Document Scope
This document describes the usage and general functionality of STS Advance.

Page 5 of 89
3 Product overview
STS Advance is CPI’s new support tool platform for its suite of products. At this time STS Advance only supports the
BNR, SCN and SCR products. The proposal is that other products will be added in future releases.
The user functionality enabled on installation will depend on the type of license, but it may include:

 Configuration – Allows the user to create a new product configuration which can then be downloaded to a
connected product. This configuration can be saved and re-opened for later use.
 Audit – Allows the user to retrieve audit files from connected products as well as store them locally.
 Diagnostics – Allows the user to diagnose and repair some rare product issues, including bill jams and faulty
modules.

3.1 System Requirements

The table below displays the minimum system requirements for running STS Advance.
Component Recommended Requirement
Processor Intel Pentium 4, 2GHz or higher recommended.
RAM 2GB or greater.
Hard Disk 50MB before installation and 25 MB after the installation
is complete.
Display Screen resolution set to at least 1024x768, small fonts
setting, and 16-bit colours or greater.
Operating System Windows 7 (SP1), Windows 8.1 or Windows 10
supported.
Privileges Administrative privileges on the system.

4 Installation
STS Advance will be distributed as a one file executable installer, STS Advance Setup.exe. To install, simply double-
click the exe file to start the installation and follow the on screen instructions.

5 Getting Started
Once STS Advance has been installed, the user can double-click on the following desktop icon to start the program.

Alternatively, the program can be started from the Windows All Programs menu. The program can be found in the
Crane Payment Innovations Inc folder.

Page 6 of 89
STS Advance WILL work without a valid license and will provide basic functionality i.e. basic diagnostics and the
ability to collect an audit file from a connected device. A valid license is required for any of the more in depth
functionality.

6 Main Functionality
6.1 Home Screen Options
When STS Advance is first started the user will be presented with the following home screen from which one of the
available options can be selected. Some of these options may not be available, depending on license functionality.

Configuration –Allows the user to create new configurations which can then be saved for use later or if a device is
connected, downloaded to the connected device. Configuration information can also be read from the connected
device. A configuration file can contain one or all of the following items: firmware, bill set (variant) data and
configuration options.
Audit – Allows the user to read and analyze audit from a connected device. The user will also have the capability of
saving the audit data to a file or a local database as well as exporting the data to an excel format.

Page 7 of 89
Maintenance – Allows the user to run maintenance operations on a connected device. This can include diagnosing
current failures on the device, analyzing historical performance data or simply performing routine maintenance
tasks.
Settings – Allows the user to read, modify and save STS Advance settings and preferences.
Exit – Closes the application. Easier to close on a touch-screen.

6.2 STS Advance Action Bar

The action bar is displayed along the bottom of the main STS Advance window.

The example above shows the bar when the configuration has been read from the device. The icons displayed in
there are context specific, i.e. only relevant icons are displayed/enabled, depending on the active screen. For

example, the write icon is only active if the device is connected.

The following example shows the action bar when device is connected and the file configuration option has been
selected

Page 8 of 89
6.3 STS Advance Device Selector BNR
The STS Advance Device Selector is displayed on the left or right side of the STS Advance window when a connected
device or device type needs to be selected. If a physical device is selected, the selector will be displayed on the left
hand side of the application.

If a device type needs to be selected, then the selector will appear on the right hand side of the application.

Page 9 of 89
In either case, simply click the appropriately configured device to select and continue. The filter boxes can be used to
narrow down the available selections. If the appropriate device configuration is not displayed, then simply click on
the Other Build Type option button and select the desired configuration. When complete, it can be saved for future
use.

Page 10 of 89
7 Product Configuration
With a valid license, STS Advance allows the user to update product firmware, bill sets and any configuration options
available on any supported product. When Configuration is selected on the home screen, the user will be presented
with some or all of the following options (depending on type of license):

Read Configuration – Allows the user to read the configuration from the connected device. If no device is connected,
this button will be disabled.
New Configuration – Allows an experienced user to create new configurations.
Load Configuration – Allows the user to open a previously created and saved configuration file.
Write To Device – Allows user to write a previously saved configuration file directly to the product without opening
it first.

Page 11 of 89
BNR configuration is broken down into 5 different areas. These are
 Build Standard
 Bill Settings
 Product Firmware
 Device Configuration Options
 Module Threshold Settings

When the user creates a new configuration in advanced mode or reads a configuration from a device they will first
be asked to select the product configuration (for a new configuration) or device (when reading configuration) before
the following screen is displayed showing these sections.

STS Advance gives the user the ability to update one, two or all of the above groups. This is done by selecting the

icon. When the group is selected, the icon will change to green and the settings can be edited. The whole
group will also be highlighted as shown below.

If selected, STS will always load the product firmware first followed by the other groups.

Page 12 of 89
7.1 Build Standard
The options displayed in this section are mainly read only. They are set when the appropriate BNR configuration is
selected in the device selector, when a new configuration is selected (see section 6.3). The only option that is not
read only is the ability to set the cash box type.

7.2 BNR Firmware

The firmware section is split into Product firmware and Firmware to Download. When the configuration is read from
the device, the product firmware section will show the firmware versions of the BNR modules as shown below

If the firmware in the product needs to be updated then this is done by going to the Firmware to download section,
and clicking the edit button. Once this is done the user will be able to select the official MEI BNR firmware zip file, as
shown below.

Only zip files can be loaded at this time. Once selected, the grid below will be populated with all of the files and
versions included in the zip file that can then be downloaded.

Depending on license options, the user will also have the ability of selecting one of the download options.

Normal – This is the default operation and means that only files in the package that are newer than the version in
the product will be upgraded. This allows the upgrade operation to be done in the most efficient manner.
Force Download – When selected, this option forces all the files in the package to be downloaded to the product,
irrespective of whether the version in the product is the same or older.
Downgrade – This allows the user to downgrade the software in the product if required, if the version in the package
file is older than that in the device.

Page 13 of 89
7.3 Device Configuration
The device configuration section contains all of the software configuration options of the BNR. This section also
includes routine maintenance information. New capabilities items under Device Configuration, Report USB
consumption, Auto retract and Reject via outlet is supported by Firmware versions 1.13.0 and above.

7.3.1 Special Configuration

This option is for special circumstances and should only be used if directed to by CPI.

7.4 Bill Settings

The bill settings configuration section allows the user to add/remove bills, assign them to and remove them from the
recycler modules.

7.4.1 Adding/deleting denominations

To add a denomination, the user should click the include button for the Bill Settings section and then click on the

Add Denomination button . They will then be able to select one or more denomination “.DLD” files for download
to the BNR device.

If replacing one currency with another (e.g. changing from EUR to USD) the “Delete Existing Denominations” box
must remain checked. This allows STS Advance to remove all current files before adding the new ones. If the user
simply wants to add a new note to the existing device (e.g. a new note is released into circulation), then the same
process can be used, but, as the note is being added to the existing notes, the “Delete Existing Denominations”
checkbox should be unchecked.

To delete a denomination from a configuration, the user must click on the button. This will remove the
denomination from the configuration. It will NOT, however, remove the denomination from the device. In order to
do this, the user will need to create a new configuration and add the denominations to the product that need to
remain in the product as well as ensuring that the “Delete Existing Denominations” box is checked.

When the arrow is displayed. This represents that the associated denomination includes several different series of
notes. To see the extra information for a denomination (as shown below), simply slick on the arrow.

Page 14 of 89
7.4.2 Assigning notes to a recycler/loader module
To assign notes to a recycler module simply check the box for all denominations that can be routed to a recycler. The
example below shows the current settings: US $1 being assigned to the 1st loader and 1st recycler, the $5 being
assigned to 2rd recycler, $10 to 3nd recycler and the $20 to 4th recycler.

STS Advance will not check that the notes are all of the correct value and size – this is the user’s responsibility – but
the following warning will be displayed in this document and on the appropriate help screen.

NB: You can only program billsets and recyclers together by creating a new configuration. If you ‘Load’ configuration
and want to change billsets and recyclers, you will need to do this in two stages.

WARNING: Module Configuration Restrictions

All of the notes routed to a single module (loader or recycler) must have the same physical length as each other
(with a 5mm tolerance). For notes that will be configured in the loader, these must also have the same width (with a
1mm tolerance).

Routing multiple denominations to the same recycler will cause the following warning to be displayed.

Page 15 of 89
However, STS Advance will not prevent the user from writing the configuration to the device. It will however,
prevent a user from writing a configuration that has a module with no bills routed to it. In this case, the error
message displayed will be

If the desire is to permanently not route any bills to the module, then it must be done by creating a configuration
that does not contain that module. See section 7.4.3. If the desire is to temporarily disable the module (but keep the
configuration) then this can be done in the Module Threshold Settings section (see section 7.5).

7.4.3 Changing Physical modules.

If the user wishes to change the physical configuration of the BNR, then the only way to do this is to create a new
configuration. When the device selector dialog is displayed (see section 6.3), select the physical configuration
required and configure it accordingly. Ensure that the physical configuration of the BNR is modified before the
software configuration is written to the device.

7.5 Module Threshold Settings

The section allows the user to configure all of the associated module thresholds as well as disable a module, from a
software point of view, such that it is no longer considered active by the BNR Device.

The threshold definitions are as follows:

Full: This is the maximum amount of bills that can be placed onto the Physical Cash Unit (PCU). Under normal
circumstances, these will be limited to the allowable 30/60 note capacity for the recyclers or 250 note capacity for
the loader. The Full Threshold can be modified to be below these maximums. In the case of the recycler, if a FULL
threshold of 50 notes was applied to a 60-note capacity recycler, the 51st (and subsequent) note(s) would be routed
to the Cashbox.

Page 16 of 89
High: This threshold signifies the point at which the BNR will alert the host that the PCU in question is approaching
its Full Capacity.

Low: This is the lower threshold, commonly referred to as the “Float” level. During replenishment, the PCU in
question will show a LOW condition until the threshold is filled. When the PCU CashType matches the set CashType
of the Loader Module, a PCU count of that recycler lower than the LOW threshold will initiate a dispense from the
Loader Module for replenishment.

Empty: By default this value is set to 0. Setting the value to a higher number will result in an EMPTY status when
triggered. Once EMPTY status is obtained, notes cannot be removed from the unit via host commands.

Page 17 of 89
8 Audit

With a valid license, STS Advance allows the user to retrieve and store audit information (where available) from any
connected and supported CPI product. When Audit is selected on the home screen, the user will be presented with
some or all of the following options (depending on type of license):

Read Audit – Allows the user to read the audit from the connected device. The resultant data will be displayed on a
summary page.
Read To File – Allows the user to read the audit from the connected device straight to a file. This option is available
without the need for a valid license.
Load From File – Allows the user to read audit that has previously been saved to a file and display it on a summary
page.
Read to Store – Allows the user to read audit to local database.
Load From Store – Allows the user to read audit that has previously been saved to the local database and display it
on a summary page.

Page 18 of 89
Export from Store – Allows the user to export audit data that has been saved to the local store (Database) to an
excel spreadsheet. One or many files can be exported. See section Error! Reference source not found. for more d
etails.
Bulk Load – Allow user to load multiple audit files into STS Advance audit store.

8.1 Audit Selector

The audit data stored in the BNR is total historic data (there is no interim data stored in the device). The BNR device
now (since firmware 1.7) does however store historic audits whenever a set number of system cycles has been
reached as well as when the firmware or module configuration is changed. This then allows the possibility to look at
differences in the counters between two historic audit reports. In order to do this in STS Advance, the user can use
the audit selector to determine the start audit and the end audit to be compared, using the selector at the top of the
audit selector page.

When using the audit selector, the user must select the start point audit report to be more recent than the end
point audit report. STS will then calculate the differences between two different audit or history points within the
file.

8.2 Audit Export

Audit data can be exported from STS to other formats. Currently, the only supported format is Excel (xml file type).
There are two ways of doing this which are detailed below.

Page 19 of 89
8.2.1 Export from summary page

After an audit file has been read from the device or loaded in from a file, it can be exported to excel by

clicking the following button in the action bar. Once clicked the file same dialog will be shown as
follows.

Simply enter a file name and click saves. This file can then be opened in Excel.

8.2.2 Export from home store

To export previously stored audit data, simply click the Export button on the STS Advance home screen. The audit
selector will be displayed on the right hand side of the application. This will display all of the audits that are stored in
the audit database.

Page 20 of 89
The user can then select one or more files to be exported to the excel XML spreadsheet format. When the files have
been selected, simply click the export button. The Save as dialog will then be displayed. Simply enter a file name and
click save. This file can then be opened in Excel.

8.3 Display Audit Screen

The audits loaded into STS Advance are displayed on 3 tabs as shown below.

Page 21 of 89
Summary Report Tab – This tab shows a summary of all the audits loaded. Counter values displayed on this form are
the sum of the values obtained from all audits currently loaded.

Details Report Tab – This tab shows the totals (sum) of the counters and the value for each device.

Devices Tab – This tab has a sub tab for each of the devices loaded. It provides detailed information for each device.

Save to Store

Page 22 of 89
By pressing the "Save to Store" button the user can save the loaded audits to the local store so that they can be
retrieved at a later date.

Save To File

The "Save to file" button is only enabled when the audit has been read from a device. It enables the user to save the
audit file read from the device to a file.

Export to Excel

By pressing the "Export to Excel" button the user can export the currently loaded audits to a spreadsheet. The user is
presented with a file save dialog to enable them to specify the filename and location. Once the file is saved the user
is presented with the dialog shown below which allows them to open the file in Excel.

8.4 BNR Audit Summary Tab

Page 23 of 89
 This Summary Report tab shows a summary of all the audits loaded. Counter values displayed on this form are the
sum of the values obtained from each device. The information is displayed in a number of sections as shown below.

Simple Report - This section show a simple overview of the audits loaded.

System - This section shows details of system items.

System Jams - This section shows details of system jams

System Failures - This section shows details of system failures

Main Module - This section shows details of the main modules.

Main Module Bill Intake - this section shows details of the bill intake.

Main Module Positioner - This section shows details of the positioner.

Main Module Recognition Sensors - This section shows details of the Recognition Sensors.

Page 24 of 89
Main Module Bottom Transport - This section shows details of the Bottom Transport.

Main Module Bundler - This section shows details of the Bundler.

Spine Module - This section shows details of the Spine module.

Loaders - This section shows details of the loaders found in the audits. There is a section for each loader found. The
loaders are numbered with the top most loader being the first.

Recyclers - This section shows details of the recyclers found in the audits. There is a section for each recycler found.
The recyclers are numbered with the top most loader being the first.

8.4.1 Simple Report

Summary Report - Simple Report

Item Type Comment
Number Of Devices Calc The number of devices that have audits loaded
systemCyclesCount From File systemCycleCount
SumSystemJams Sum billJamCount ,billErrorCount, transportErrorCount
hardwareFailureWithBillStoppedCount,
MCBJ (+1) systemCyclesCount / (1 + SumSystemJams)
Jams ExLo Calc SumSystemJams – Loader Jams
MCBJ ExLo (+1) Calc systemCyclesCount / (1 + Jams ExLo)

Page 25 of 89
8.4.2 System

Summary Report - System

Item Type Comment
Cycles From File systemCycleCount
Days of Operation Calc totalUpTime / Seconds in day
Cycles Per 24hrs Calc systemCycleCount / Days of Operation
Resets With Cover From File resetWithCoverOpenCount
Open
Resets With Interlock From File resetWithInterlockOpenCount
Open

8.4.3 System Jams

Page 26 of 89
Summary Report – System Jams
Item Type Comment
SumSystemJams Sum billJamCount ,billErrorCount, transportErrorCount
hardwareFailureWithBillStoppedCount,
MCBJ (+1) Calc systemCycleCount / (1+ SumSystemJams)
Loader Jams Calc Sum of Jams for the loaders fitted
Jams ExLo Calc SumSystemJams – Loader Jams
MCBJ ExLo (+1) Calc systemCycleCount / (1+ Jams ExLo)
Main Module Jams If version is V1.8.0 or newer.

Sum Main Section Bill Ending counters

If version before V1.8.0

billJamCount + billErrorCount + transportErrorCount

Recycler Jams Calc Sum of Jams for the recyclers fitted.

8.4.4 System Failures

Summary Report – System Failures

Item Type Comment
System Failures Calc hardwareFailureCount + hardwareFailureWithBillStoppedCount +
operationalDegradedCount
MCBF (+1) Calc systemCycleCount / (1+ System Failures)
Total Interventions Calc SumSystemJams + System Failures

Page 27 of 89
8.4.5 Main Module

Summary Report – Main Module

Item Type Comment
Main Module Cycles Calc mainTransportCycleCount + bundlerDivSystemCycleCount +
positionerCycleCount
Incident Start MM From File incidentStartSectionCounters
Bill Ending MM From File billEndingInMMSectionCounters
Sum MM Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Main Module Cycles / (1 + Sum MM Jams)
MCBF (+1) Calc Main Module Cycles / (1 + Hardware Failure Count)

8.4.6 Main Module Bill Intake

Summary Report – Main Module Bill Intake

Item Type Comment
Bill Intake Cycles From File billIntakeCycleCount

Page 28 of 89
8.4.7 Main Module Positioner

Summary Report – Main Module Positioner

Item Type Comment
Positioner Cycles From File positionerCycleCount
Incident Start PR From File incidentStartSectionCounters
Bill Ending PR From File incidentStartSectionCounters
MCBJ PR (+1) Calc Positioner Cycles / (1 + Bill Ending PR)

8.4.8 Main Module Recognition Sensors

Summary Report – Main Module Recognition Sensors

Item Type Comment
Incident Start RS From File incidentStartSectionCounters
Bill Ending RS From File billEndingInMMSectionCounters

Page 29 of 89
8.4.9 Main Module Bottom Transport

Summary Report – Main Module Bottom Transport

Item Type Comment
Incident Start BT From File incidentStartSectionCounters
Bill Ending BT From File billEndingInMMSectionCounters
MCBJ BT (+1) Calc mainTransportCycleCount / (1 + Bill Ending BT)

8.4.10 Main Module Bundler

Summary Report – Main Module Bundler

Item Type Comment
Bundler Cycles From File bundlerDivSystemCycleCount
Incident Start BU From File incidentStartSectionCounters
Bill Ending BU From File billEndingInMMSectionCounters
MCBJ BU (+1) Calc Bundler Cycles / (1 + Bill Ending BU)

Page 30 of 89
8.4.11 Spine Module

Summary Report – Spine Module

Item Type Comment
Cycles From File cycleCount
Sum SP Jams From File billJamCount + billErrorCount + transportErrorCount
Incident Start From File incidentStartSectionCounters
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

8.4.12 Loaders

Summary Report – Loader

Page 31 of 89
Item Type Comment
Cycles From File cycleCount
Incident Start Module From File incidentStartSectionCounters
Incident Start Interface From File incidentStartSectionCounters
Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

8.4.13 Recyclers

Summary Report – Recycler

Item Type Comment
Cycles From File cycleCount
Incident Start Module From File incidentStartSectionCounters
Incident Start Interface From File incidentStartSectionCounters
Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

Page 32 of 89
8.5 Audit Details Tab

This Details Report tab shows the totals (sum) of the counters for all devices and the value for each device loaded.
The information is displayed in a number of sections as shown below.

Information - This section show information about the store and lane that the devices were installed at. The
information is not read from the files but has to be added by the user when the files are loaded.

System - This section shows details of system items.

System Jams - This section shows details of system jams.

System Failures - This section shows details of system failures.

Main Module - This section shows details of the main modules.

Main Module Bill Intake - This sections shows details of the bill intake.

Main Module Positioner - This section shows details of the positioner.

Page 33 of 89
Main Module Recognition Sensors - This section shows details of the Recognition Sensors.

Main Module Bottom Transport - This section shows details of the Bottom Transport.

Main Module Bundler - This section shows details of the Bundler.

Spine Module - This section shows details of the Spine module.

Loaders - This section shows details of the loaders found in the audits. There is a section for each loader found. The
loaders are numbered with the top most loader being the first.

Recyclers - This section shows details of the recyclers found in the audits. There is a section for each recycler found.
The recyclers are numbered with the top most loader being the first.

8.5.1 System

Detail Report - System

Item Type Comment
Start Point The audit point used for the initial audit.
End Point The audit point used for the final audit.
Unit Firmware From File
System Cycle Count From File
Days of Operation Calc totalUpTime / Seconds in day

Page 34 of 89
 Cycles Per Day Calc systemCycleCount / Days of Operation
Resets With Cover From File resetWithCoverOpenCount
Open
Resets With Interlock From File resetWithInterlockOpenCount
Open
Notes :-

1. The values displayed on the form are interim audit values. They are calculated by subtracting the start
point value from the end point value. Thus giving the value for the selected time period.
2. When the audits are loaded the end point is set to the current audit which is the counter values at the time
the audit was read. The start point is set to the last audit point where a configuration change occurred.

8.5.2 System Jams

Detail Report – System Jams

Item Type Comment
SumSystemJams Sum billJamCount ,billErrorCount, transportErrorCount
hardwareFailureWithBillStoppedCount,
MCBJ (+1) Calc systemCycleCount / (1+ SumSystemJams)
Loader Jams Calc Sum of Jams for the loaders fitted
Jams Ex Lo Calc SumSystemJams – Loader Jams
MCBJ ExLo (+1) Calc systemCycleCount / (1+ Jams ExLo)
Main Module Jams If version is V1.8.0 or newer.

Sum Main Section Bill Ending counters

If version before V1.8.0

billJamCount + billErrorCount + transportErrorCount

Recycler Jams Calc Sum of Jams for the recyclers fitted.

Page 35 of 89
8.5.3 System Failures

Detail Report – System Failures

Item Type Comment
System Failures Calc hardwareFailureCount + hardwareFailureWithBillStoppedCount
+ operationalDegradedCount
Failures Per 24Hrs Calc System Failures / Days of Operation
MCBF (+1) Calc systemCycleCount / (1+ System Failures)
Total Interventions Calc SumSystemJams + System Failures

8.5.4 Main Module

Detail Report – Main Module

Item Type Comment
MM MSN From File
MM Firmware From File
Main Module Cycles Calc mainTransportCycleCount + bundlerDivSystemCycleCount +
positionerCycleCount

Page 36 of 89
Incident Start Main From File incidentStartSectionCounters
Module
Bill Ending Main From File billEndingInMMSectionCounters
Module
Sum MM Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Main Module Cycles / (1 + Sum MM Jams)
MCBF (+1) Calc Main Module Cycles / (1 + Hardware Failure Count)
Cycles to PM Calc maintenanceInterval - cycleSinceLastMaintenance
Days to PM Calc Cycles until PM / Cycles per day
Cycles Calc mainTransportCycleCount + bundlerDivSystemCycleCount +
positionerCycleCount

8.5.5 Main Module Bill Intake

Detail Report – Main Bill Intake

Item Type Comment
Bill Intake Cycles(IN) From File billIntakeCycleCount

8.5.6 Main Module Spine Interface Diverter Cycle Count

Detail Report – Main Module Spine Interface Diverter Cycle Count

Item Type Comment
Diverter Cycle Count From File spineInterefaceDiverterCycleCount, introduced for BNR Advance
when 0 is not supported

Page 37 of 89
8.5.7 Main Module Positioner

Detail Report – Main Module Positioner

Item Type Comment
Postioner Cycles From File positionerCycleCount
Incident Start PR From File incidentStartSectionCounters
Bill Ending PR From File incidentStartSectionCounters
MCBJ BR (+1) Calc Positioner Cycles / (1 + Bill Ending PR)

8.5.8 Main Module Recognition Sensors

Detail Report – Main Module Recognition Sensors

Item Type Comment
Incident Start RS From File incidentStartSectionCounters
Bill Ending RS From File billEndingInMMSectionCounters

8.5.9 Main Module Bottom Transport

Detail Report – Main Module Bottom Transport

Item Type Comment
Incident Start BT From File incidentStartSectionCounters

Page 38 of 89
Bill Ending BT From File billEndingInMMSectionCounters
MCBJ BT (+1) Calc mainTransportCycleCount / (1 + Bill Ending BT)

8.5.10 Main Module Bundler

Detail Report – Main Module Bundler

Item Type Comment
Bundler Cycles (BU) From File bundlerDivSystemCycleCount
Incident Start BU From File incidentStartSectionCounters
Bill Ending BU From File billEndingInMMSectionCounters
MCBJ BU (+1) Calc Bundler Cycles / (1 + Bill Ending BU)

Spine Module

Detail Report – Spine Module

Item Type Comment
SP MSN From File
SP Firmware From File
SP Cycles to PM Calc maintenanceInterval - cycleSinceLastMaintenance
SP Days to PM Calc Cycles until PM / Cycles per day
Cycles From File cycleCount
Sum SP Jams From File billJamCount + billErrorCount + transportErrorCount

Page 39 of 89
Incident Starts From File incidentStartSectionCounters
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

8.5.11 Loaders

Detail Report – Loader Module

Item Type Comment
MSN From File
Firmware From File
Cycles From File cycleCount
Cycles to PM Calc maintenanceInterval - cycleSinceLastMaintenance
Days to PM Calc Cycles until PM / Cycles per day
Incident Start Module From File incidentStartSectionCounters
Incident Start Interface From File incidentStartSectionCounters
Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

Page 40 of 89
8.5.12 Recyclers

Detail Report – Recycler Module

Item Type Comment
MSN From File
Firmware From File
Cycles From File cycleCount
Cycles to PM Calc maintenanceInterval - cycleSinceLastMaintenance
Days to PM Calc Cycles until PM / Cycles per day
Incident Start Module From File incidentStartSectionCounters
Incident Start Interface From File incidentStartSectionCounters
Jams Calc billJamCount + billErrorCount + transportErrorCount
Hardware Failure Count From File hardwareFailureCount
MCBJ (+1) Calc Cycles / (1 + Jams)
MCBF (+1) Calc Cycles / (1 + Hardware Failure Count)

Page 41 of 89
8.6 Audit Devices Tab

The Devices tab has a sub tab for each of the devices loaded. It provides detailed information for each device.

Page 42 of 89
Devices
Item Type Comment
Start Point The audit point used for the initial audit.
End Point The audit point used for the final audit.
Cashbox Accessible Defines if the operator can access the cash box or not. Some
calculation will change depending on this value. E.G Interventions as
if the cash box is not accessible a service call will be required to clear
Bottom Transport jams.
Notes :-
1. The values displayed on the form are interim audit values. They are calculated by subtracting the
start point value from the end point value. Thus giving the value for the selected time period.
2. When the audits are loaded the end point is set to the current audit which is the counter values at
the time the audit was read. The start point is set to the last audit point where a configuration
change occurred.

Overall Performance – This section shows the overall system performance for a BNR.

Main Module Performance – This section shows the main module details and performance counters.

Spine Performance - This section shows the spine details and performance counters.

Loader and Recycler Performance – This section shows the performance counters and details for the loader and
recycler modules.

Denomination Performance - This section shows the noteset/variant performance overall and for each note.

Page 43 of 89
8.6.1 Overall Performance

The overall performance section shows a summary of the whole BNR system. The data shown includes
Systems cycles and Mean Cycles between interventions. A full description of all of the audit fields in this
section and how they are calculated is shown below

Devices – Overall Performance

Item Type Comment
System Cycles From File systemCycleCount
Mean Cycles Between Calc systemCycleCount / (1 + Jams + Failures)
Intervention
Days of Operation Calc totalUpTime / seconds in a day
Cycles per 24hrs Calc systemCycleCount / Days of Operation
Resets with cover open From File resetWithCoverOpenCount (V1.8.0 or newer)
Resets with Interlock From File resetWithInterlockOpenCount (V1.8.0 or newer)
open
Jams Calc billJamCount + billErrorCount + transportErrorCount
hardwareFailureWithBillStoppedCount +
MCBJ Calc systemCycleCount / (1 + Jams)
Jams per 24hr Calc Jams / Cycles per 24hrs
Failures Calc hardwareFailureCount + hardwareFailureWithBillStoppedCount +
operationalDegradedCount
MCBF Calc systemCycleCount / (1 + Failures)
Loader Jams Calc Sum of the jams for the loaders

Page 44 of 89
8.6.2 Main Module Performance

This is data specific to the main module and its elements. A full description of all of the audit fields in this
section and how they are calculated is shown below

Devices – Main Module Performance

Item Type Comment
Serial Number From File Module serial number
Firmware From file Module firmware version
Cycles until PM Calc maintenanceInterval - cycleSinceLastMaintenance
Estimated PM date Calc Cycles until PM / Cycles per day
Bundler Slippage Calc Bundler slippage calculated from audit file

Page 45 of 89
Devices – Main Module Performance – Summary
Item Type Comment
Cycles From File Inlet – billIntakeCycleCount

Positioner – positionerCycleCount

Recognition Sensor – No counter available

Bottom Transport – mainTransportCycleCount

Bundler – bundlerDivSystemCycleCount

Total – mainTransportCycleCount + bundlerDivSystemCycleCount +

positionerCycleCount
Jams Calc billJamCount + billErrorCount + transportErrorCount
Failures From File hardwareFailureCount
Inc Start From File incidentStartSectionCounters
Bill Ending From File billEndingInMMSectionCounters
MCBJ Calc For each main module section

SectionCycles / (1 + Section Bill Ending)

The Total value calculation depends on the MM version.

If the version is V1.8.0 or newer

Total Cycles / (1 + Sum of Bill Endings)

If older than V1.8.0

Total Cycles / (1 + Jams)

MCBF Calc Total Cycles / (1 + hardwareFailureCount)

Note: - Incident Start and Bill Ending are only available for V1.8.0 or newer.

Page 46 of 89
Devices – Main Performance – Regulated sensor calibration values
Item Type Comment
Threshold From File threshold
Offset From File offset
Value From File value
Gain From File gain
Cleanness From File maintenanceCleanness

8.6.3 Spine Performance

This is data specific to the spine module and its elements. A full description of all of the audit fields in this section
and how they are calculated is shown below.

Page 47 of 89
Devices – Spine Performance
Item Type Comment
Serial Number From File Module serial number
Firmware From File Module firmware version
Cycles until PM Calc maintenanceInterval - cycleSinceLastMaintenance
Estimated PM date Calc Cycles until PM / Cycles per day

Devices – Spine Performance – Summary

Item Type Comment
Cycles From File cycleCount
Jams Calc billJamCount + billErrorCount + transportErrorCount
Failures From File hardwareFailureCount
Inc Start From File incidentStartSectionCounters
MCBJ Calc Cycles / (1 + Jams)
MCBF Calc Cycles / (1 + Failures)
Note:- Jam and Failure counters are not available for the individual slots

Page 48 of 89
Devices – Spine Performance - Regulated sensor calibration values
Item Type Comment
Threshold From File threshold
Offset From File offset
Value From File value
Gain From File gain
Cleanness From File maintenanceCleanness

8.6.4 Loader and Recycler Performance

This is data specific to the loader and recycler modules. A full description of all of the audit fields in this section and
how they are calculated is shown below.

Devices – Loader and Recycler Performance

Item Type Comment
Serial Number From File Module serial number
Firmware Version From File Module firmware version
Cycles From File cycleCount
Cycles until PM Calc maintenanceInterval - cycleSinceLastMaintenance
Estimated PM Date Calc Cycles until PM / Cycles per day
Jams Calc billJamCount + billErrorCount + transportErrorCount
Failures From File hardwareFailureCount
Inc Start Mod From File incidentStartSectionCounters
Inc Start IF From File incidentStartSectionCounters
MCBJ Calc Cycles / (1 + Jams)
MCBF Calc Cycles / (1 + Failures)

Page 49 of 89
Devices – Loader and Recycler Performance - Regulated sensor calibration values
Item Type Comment
ID From File id
Slot Calc Id – Base module ID (Loader = 918528; Recycler = 918272)
Sensor ID Calc Slot + Base module sensor ID (Loader = 198479; Recycler =
198449)
Threshold From File threshold
Offset From File offset
Value From File value
Gain From File gain

8.6.5 Cashbox Performance

Devices – Cashbox Performance

Item Type Comment
Removal Count From File moduleRemovalCount
Full Count From File moduleFullCount
Stacked While Recycler From File stackedWhileRecyclerFullCount
Full Summary

Page 50 of 89
8.6.6 Denomination Performance

This section covers the performance of the note set in general. A full description of all of the audit fields in this
section and how they are calculated is shown below.

Devices – Denomination Performance –

Item Type Comment
Overall Acceptance Calc (validCount / positionerCycleCount) * 100
Quotient of Calc mainTransportCycleCount / validCount
Performance
Notes Stacked per 24 Not used
hrs
Days of Operation Not used
Dispense Amount From File dispenseAmountCount
Denomination Amount From File denominateAmountCount
Amount Not Available From File amountNotAvailableCount
Bills Requested From File billRequestedCount
Bill Not Available From File billNotAvailableCount
Too Many Bills From File tooManyBillsCount
Direct From Loader From File directFromLoaderCount

Page 51 of 89
Devices – Denomination Performance – Summary
Item Type Comment
Validation Rate Calc (validCount / validUnfitCount) * 100
Notes Recognized Calc validCount + validUnfitCount
Notes Validated From File validCount
Confusion Count From File confusionCount
Fitness Count From File fitnessCount
Forgery Count From File forgeryCount
Suspect Count From File suspectCount

Devices – Denomination Performance – Loader Acceptance History

Item Type Comment
Bills Extracted From File billExtractedCount
Bill Shape Rejects From File badShapeRejectCount
Extraction Rejects From File extractionRejectCount
Recognition Rejects From File recognitionRejectCount

Page 52 of 89
Devices – Denomination Performance – Dispense History
Item Type Comment
Bills Requested From File billRequestedCount
Bills Not Available From File billNotAvailableCount

Devices – Denomination Performance – Recycler History

Item Type Comment
Stacked When Recycler From File stackedWhileRecyclerFullCount
Full

8.7 Bulk Load

In order for audit calculations to be performed by STS Advance on audit files that were not collected using STS
Advance, they first need to be loaded into STS Advance. This is done with the bulk load option on the audit home
screen. When selected, the user will be presented with the following screen and options.

Page 53 of 89
8.7.1 Adding files to the list

The user has the choice of loading one file at a time, by pressing the Add File button or by loading multiple files by
pressing the Add Files from Folder Structure button.

When adding multiple files there are 2 options.

 If the “Extract Customer Data” check box is unchecked all audit files found under the selected folder are
added to the list.
 If the “Extract Customer Data” check box is checked the names of the folders are used specify the Store and
Lane for the audit. The folder structure must be in the following format

Date (yyyy-mm-dd)\Location(Store/Place name)\Lane (identifies individual BNR)

Page 54 of 89
8.7.2 Adding extra data

The user also has the option of adding extra data to be stored in the database by checking the Set Default Customer
Data check box and filling in the OEM, End User and Location fields.

8.7.3 Removing files from the list

The user can remove a file from the list by selecting the file in the list and pressing the “Delete File” button.

8.7.4 Load Files To Screen

By pressing the “Load to Screen” button the audits from the selected files are displayed on the screen. The user can
then view the data and have the options to save the audits to the store or export them to an Excel spreadsheet.

8.7.5 Load Files To Store

By pressing the “Load to Store” button the audits from the selected files are saved to the store. Once in the store the
audits can be retrieved from the store and displayed on the screen or exported to an Excel spreadsheet file. When
the files are successfully save the following dialog will be displayed.

Page 55 of 89
9 Product Maintenance/Diagnostics
With a valid license, STS Advance allows the user to run product diagnostics on any connected and supported CPI
product. When Maintenance is selected on the home screen, the user will be presented with some or all of the
following options (depending on type of license):

Run Diagnostics – Runs the various maintenance operations on a connected device. This can include diagnosing
current failures on the device, analyzing historical performance data or simply performing routine maintenance
tasks. When complete these diagnostic results can be saved to a file. This option is available without the need for a
valid license.
Open Saved Performance – Allows the user to run module performance checking on previously saved audit files.
Calibrate Unit – Allows the user to run the calibration process on the BNR. Calibration paper (Part Number:
675032001P10) is required for this process.

Park Recyclers – Allows the user to “park” the recyclers before the modules are shipped.
Update Mfr Serial Number – Allows service centers to configure serial numbers of replacement PCBs.
Sensor Values – Allows users to look at sensor values to ascertain whether they need cleaning or not. This
functionality is limited if connected device has application firmware version less than V1.9.0.

Page 56 of 89
Use History - Allows users to view the cycle and repair counts of the various BNR modules.
Module Test – Allows users to insert notes to test the operation of the BNR modules once all diagnostics operations
have been completed.
Bundler Slippage – Allows the user to run a test that will calculate the slippage value of the bundler belt. This
calculation is also run as part of the diagnostics tests, see next section.
Note Test - A basic version of the module test functionality. Allows all configured modules to be tested quickly using
a minimum amount of notes.
Recycler Purge – Allows the user to empty the configured recyclers. This operation may result in a loss of
accountancy between the BNR and host cash management.

9.1 BNR Diagnostics

When the run diagnostics button is pressed, the device selector will appear prompting the user to select the
connected device. When the device is selected, STS Advance will begin to run diagnostics commands on the device.
When complete, the user will be presented with the following summary screen.

Page 57 of 89
The summary screen will show the state of all of the modules. The states are Error, Warning and OK. Looking at the
diagram above, we can see that the recycler, loader and cashbox modules have warnings and the main module has
an error. To further investigate the errors or warnings on each module, simply double-click the picture of the module
and where possible, STS Advance will obtain more details and provide instructions for the user to try and resolve the
issue.

An example is shown below for the main module error.

Once the user has followed the on-screen instructions, the continue button can then be pressed. STS Advance will
run through the relevant tests again, to see if the error has been cleared. If it has not and if available, different and
more in-depth instructions may be displayed, which can then be followed to see if the error can be corrected. If the
error cannot be corrected the user will be instructed to replace the module in question or, if the appropriate feature
is licensed, carry out a modular repair.

Once all persistent errors have been cleared, STS Advance will perform some basic tests to check the performance of
the individual modules.

Page 58 of 89
9.2 Module Performance checking
If there are no errors present (or the errors have been cleared), STS Advance will then run the performance
monitoring algorithm. The performance checking algorithm will look at past and present data to determine how the
module is performing. If the performance is below a certain threshold the user will be notified of what, if any action
needs to be taken to try and improve the performance. With a valid license, this check can also be run on stored
audit files from the main diagnostics menu (Open Saved Performance)

9.3 Calibrate Unit

On occasion, the BNR will need calibrating. To do this the user will need some calibration paper and then simply click
on the Calibrate Unit button and follow the instructions shown on the wizard.

Page 59 of 89
When the internal calibration process has been completed the coupon will be presented to the user, the user must
then remove the coupon from the outlet in order to complete the process. The result of the process will then be
displayed. To exit the wizard and return to the Maintenance Home screen, simply click the finish button.

9.4 Park Recyclers

Sometimes the recycler modules need to be removed from the unit and sent for repair or routine maintenance. Prior
to their removal, the recyclers must be “Parked”. This is the process of tightening the internal tape such that it
doesn’t become loose or detached in transit. To complete this process with STS Advance, the user selects the Park
Recyclers option on the Maintenance home screen.

When selected, the user will be shown the diagnostics screen with all the available recycler modules highlighted in
RED as shown below.

To park one or all recyclers, double-click the recycler and select whether the selected recycler or all recycler modules
should be parked. When the parking process has been completed, the parked modules will be displayed in green.
They can then be removed, ready for shipment.

Page 60 of 89
9.5 Update Mfr Serial Number
To run this operation the user must have a valid ASC license. This operation will generally be used by service centers
when replacing PCB’s in any of the modules. Once the button has been pressed, the user will be prompted to enter a
new number. This can be done by entering a new 11 digit serial number manually or by pressing the Generate
Number button.

If the generate number option is used, STS Advance will generate a random number preceded with 6 zeroes as
shown above. Once the number has been entered, the user simply needs to press the write button, shown in the
action bar, to write the new module serial number to the connected BNR device.

9.6 Sensor Values

To run this operation the user must have a valid ASC license. This functionality allows the user to get an up to date
status of all the sensors on the product as shown below. These values are reported directly from the product. An
example of the sensor values page is shown below.
Note: If the BNR application firmware of the connected product is less than V1.9.0, then the sensor cleanliness
values cannot be displayed – the user will only be able to see the regulated calibration values.

Page 61 of 89
Page 62 of 89
9.7 Use History
This functionality allows the user to get a snapshot of the number of cycles that the BNR and its various modules
have been through, as shown below.

Page 63 of 89
9.8 Module Test
When the module test button is clicked, the module test home screen will be displayed, as shown below.

The user then has the option to select which modules they wish the tests to be run on by checking the box next to
the relative module. When the desired tests have been selected, the user simply needs to click on the Run tests
button to initiate the tests.

At the start of the test the user will be informed what equipment will be required for the test including the amount
and type of notes as shown below.

Page 64 of 89
If the notes displayed are not available, the user will be prompted to reconfigure the BNR appropriately such that
the BNR asks for the available notes. For example, if the BNR is configured to accept Euro notes and only British
pounds are available, the user should reconfigure the BNR to accept British pounds for the purposes of the test and
then configure it back to Euros once the test has been completed.

During the tests the user will be presented with HTML instructions to follow as shown below.

Page 65 of 89
Once the tests have been completed, the results of the test will be displayed in the same way as the results for
diagnostics as shown below.

Page 66 of 89
9.8.1.1 Module test action bar operations.
Located in the action bar at the bottom of the STS Advance screen, are two action buttons.

The reset device button can be used, before the tests are run, if the connected BNR is reporting an error or is
showing a status of Idle, then chances are it simply needs to be reset.

The empty device button can be used if there are notes still in the modules of the BNR from a failed test. When
clicked the BNR will move all of the notes currently in the BNR modules into the recycler so that they can easily be
removed.

Page 67 of 89
Bundler Slippage
This functionality allows the user to obtain a value for the Bundler Slippage percentage. This value determines how
much the bundler belt has slipped over time and is displayed as shown below

With firmware version V1.9 or greater, this value is calculated and returned by the BNR itself. For firmware version
prior to this, the value is calculated by STS Advance.

9.9 Recycler purge

When this option is selected, STS Advance will interrogate the device in order to display the recycler configuration.
Once this has been done, the following screen will be displayed.

Page 68 of 89
The user then has the ability to empty the recyclers to the cashbox. When a recycler is selected, the user will be
prompted with the following dialog and then has the option of continuing or not.

If the user continues, all of the notes in the selected recycler will be moved to the cashbox.

9.10 Note test

When the note test button is pressed, STS Advance will read the configuration of the device and then display the
base diagnostics page.
STS Advance will then check that the user has the interlock key and is ready to start.

Page 69 of 89
The test will then utilize the money within the device to test all of the fitted modules, as long as the module contains
at least 2 notes. If there are not enough notes in the system, the user will be informed with the following message.

The user must follow all screen prompts.

First, the notes will be dispensed to the user. This tests the movement of the notes out of each module. Then, with
the dispensed notes, the user must re-insert the notes. Depending on the configuration of the unit, the inserted
notes will either be route to the cashbox or the recyclers.

9.11 Use History

This functionality allows the user to get a snapshot of the number of cycles that the BNR and its various modules
have been through, as shown below.

Page 70 of 89
9.12 Update Manufacturer Serial Number
To run this operation the user must have a valid ASC license. This operation will generally be used by service centers
when replacing PCB’s in any of the modules. Once the button has been pressed, the user will be prompted to enter a
new number. This can be done by entering a new 11 digit serial number manually or by pressing the Generate
Number button.

If the generate number option is used, STS Advance will generate a random number preceded with 6 zeroes as
shown above. Once the number has been entered, the user simply needs to press the write button, shown in the
action bar, to write the new module serial number to the connected BNR device.

9.13 Bundler Slippage

This functionality allows the user to obtain a value for the Bundler Slippage percentage. This value determines how
much the bundler belt has slipped over time and is displayed as shown below

Page 71 of 89
With BNR application firmware version V1.9.0 or greater, this value is calculated by the BNR itself. For firmware
versions prior to this, the value is calculated by STS Advance.

Page 72 of 89
10 STS Advance Settings
The settings menu on STS Advance allows the user to see and in some cases modify the application settings. When
settings is selected on the home screen, the user will be presented with the following options

General App Settings – Allows the user to modify the general application settings, such as default file paths.
Manage License – Allows the user to view current license details or add a new license. This option is available
without the need for a valid license.
Manage Templates – Allows the user to view the versions of and update the system template files. The files define
the options and behavior within STS Advance.
Manage Database – Allows the user (with an appropriate license) to delete any old/unwanted audit files from the
STS Advance database.

Page 73 of 89
10.1 Application Settings
From this page, the user can set the locations that STS Advance will look in for various file types. A screenshot is
displayed below.

The default locations are under the public documents area and can be reset by clicking the button.

Application Data Directory – STS Advance uses directory to store audits so that users can load and analyze them at a
later date.

Templates Directory – STS Advance uses template files as an easy way of configuring the way the application is used,
specifically the product options that the customer is able to read/write from a device. Sometimes it will be necessary
to distribute updates to these templates files.

Licence ID – Users can set up type of the product variable used by Licence Manager.

HTML File Resource Location - Users set up HTML file resource location in the application data directory.

Page 74 of 89
10.2 Manage License
If no valid license has been loaded into STS Advance, the user can click the Add License button and select a valid
license file. The details of that license (including available features as well as valid license dates) can then be seen by
clicking on the License Details button.

10.3 Manage Templates

STS Advance uses template files as an easy way of configuring the way the application is used, specifically the
product options that the customer is able to read/write from a device. Sometimes it will be necessary to distribute
updates to these template files.
One the Manage template button has been clicked the following screen is displayed.

Page 75 of 89
Users can then check the versions of the files. If a template file needs updating, the user simply clicks on the
icon and selects the appropriate replacement file. If the selected file is not valid, the file selection dialog will be
displayed again, until the user either selects the correct type of presses cancel on the dialog.

10.4 Manage Database

STS Advance uses a database to store audits so that users can load and analyze them at a later date. The mange
database form enables the user to manage this database.

Page 76 of 89
The table shows the audits that are saved in the store. The user can select one, or many, audits in the table, then
press the "Delete" button to remove the audits from the store.

Page 77 of 89
12 STS Advance Connectivity
12.1 Simplifi Store
With the version V3.00 STS Advance will be connected to simplify Store. Simplifi store is an online server to which
STS Advance connects. Users will login to the store via STS Advance and have access to the firmware and currency
files to which they have purchased or have approved access to. These files will be displayed in the product file
catalog and will be available to download directly to the product or supported handheld as necessary.

By starting of any STS Advance Product modules, the login will be asked.

If login skipped, or cannot login, limited functionality will be available.

Page 78 of 89
12.2 Product File Catalog
Once logged in, STS Advance automatically updates local product file catalog cache based on authenticated user and
associated customer account, and if the supported product is connected, based on that product portfolio. At this
point, there are 3 scenarios for extracting/updating product catalog and its contents.

Create new configuration. Select new configuration, load firmware and/or currency set. The product catalog
presents list of files, this listing only displays latest files (by default although option to show all versions should be
enabled/disabled in settings). The display also indicates whether file is local or requires downloading from compass
server as well as whether it is chargeable or not. When file is selected, it will be downloaded if necessary and then
loaded into configuration.

Page 79 of 89
When configuration includes the file consisting charging information the wallet screen appears as below. Select
wallet and hit pay before writing configuration. The amount of credits will be deducted from available credit
balance.

Page 80 of 89
Write configuration offline using PPM. First add credits using Add Credit control on tool bar. Number of credits
appears on the handheld page. Offline means the PPM is used for credit store and that it needs to be connected to
PC.

Write configuration using PPM wallet presented to confirm payment. Credits will be deducted from PPM balance on
successful configuration write.

Page 81 of 89
Read configuration. Select read configuration from configuration menu and select a device. Device settings are then
displayed. If currency set or firmware version are older than versions in product catalog, then Info message will be
displayed on main configuration form along the lines of "There is a newer version of currency set/firmware/both".
Now select files as above.

Page 82 of 89
"View catalog" option. This is option under the settings menu. Selects this option from settings menu.

The product catalog is displayed. Only files that are marked as server are available for download.

Page 83 of 89
Page 84 of 89
13 BNR Step by Step Programming Guide

Step 1 – Loading Firmware into SCN/SCNR

 Connect PC to front USB port on SCN head

 Open STS Advance SCN-SCR – select ‘Configuration’

 Select ‘New Configuration’, choose BNR and click ‘continue’

Page 85 of 89
 Select the model of BNR you are going to program and click ‘Continue’:

Page 86 of 89
 In the @Bill Settings’ option click ‘Add Denomination’

 Choose the billset from the Product Catalog and click ‘Load’

 Under ‘Denominations to be added to device:’ select the bills you want to be recycled

Page 87 of 89
 Select ‘Save’ to create a configuration file (.sac) which you can use to load in other BNR units.
 Select ‘Write to Device’ – select BNR connected to PC – select ‘Continue’
 Select the Wallet from where the credits are to be consumed and press ‘Pay’

Page 88 of 89
 Once download completed BNR will power-cycle – ‘Configuration written successfully’ message will appear
on screen.

Page 89 of 89