Professional Documents
Culture Documents
Mei-Bnr-Rnt-118 - ST - 2020
Mei-Bnr-Rnt-118 - ST - 2020
BNR AdvanceTM
Release Notifications
Java runtime
Included with the installer
PC platform
Celeron 600 MHz or better processor
COPYRIGHT © 2020 2 / 21 MEI-BNR-RNT-118- ST_2020
All Rights Reserved
BNR-RNT-118
In addition, if one audit file is detected as invalid in a directory where several audit files are located,
only audit files checked before the “invalid” one are displayed, and after doing a Refresh, no audit
files at all are displayed.
Audit files handling has been reviewed, now BNR Support Tools software checks and fixes audit
files when it detects some issue; a .bak copy of original file is kept.
Replication Instructions:
n/a
6. History of changes
-------------------------- 2017 to 2018 ------------------------
In response to bnr.GetLog(1) command, one can see state changes of new SpineInterfaceDiverter
element:
NOTE: The configuration wizard does not work with polling activated.
NOTE: For more detailed descriptions of the features above, please refer to BNR Firmware 1.13.0
Release Notes (MEI-BNR-RNF-043).
START
The connected BNR resets to update internal parameters. Then, a START report is created
and the BNR automatically fills the “Maintenance Started” status list. The operator is free
disconnect power, clean, and exchange needed parts on the device.
CANCEL
The connected BNR or - if none is connected - any BNR in the “Maintenance Started”
status list can have its status cancelled. The selected BNR quits the list and its START report is
erased.
COMPLETE
The connected BNR – if already in the list – or any BNR in the “Maintenance
Started” status list completes its maintenance procedure. A reset indicates if the BNR is
Operational. The operator enters the list ofexchanged parts and the corresponding START report
is encapsulated into a COMPLETE report, including up-to-date internal parameters. A daily report
is then created/updated with all maintenance operations performed to date. If any step fails, an
error is indicated and the operation stops. If the operation is a success, the BNR quits the list.
Reason for Change: Log files have been enabled for the different API embedded into the Support
Tool software.
Replication Instructions: N/A
By default, the log files of the different API embedded into the BNR Support Tool product are
activated. Their location can be modified:
for the Win32 API via the file ../BNR Support Tool/BnrCtl.ini
for the Java API via the file ../log4j-bnrCtlJava.properties
If the BNR Support Tool has been installed into an unprotected directory (D:\...), by default, the
logs are located at ../BNR Support Tool/logs/.
If the BNR Support Tool has been installed into a protected directory (C:\Program Files
(x86)), on Windows 7 and newer operating systems, by default, the logs are located at
C:\Users\ userName \AppData\Local\VirtualStore\Program Files (x86)\MEI\BNR Support
Tools\BNR Support Tool\logs.
The log file of the BNR Support Tool is not modifiable. On Windows 7 and newer operating
systems, it is located at C:\Users\userName\AppData\Local\MEI\BNR Support
Tool\log\BnrSupportTool.log.
Denomination Files
COPYRIGHT © 2020 13 / 21 MEI-BNR-RNT-118- ST_2020
All Rights Reserved
BNR-RNT-118
Monitor Tool
Change Type: Product Enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.12.0
Replication Instructions: N/A
Added support for the new bnr.QueryBillsetIds command if the permission
MONITOR_QUERY_BILLSET_IDS is granted to the user
Configuration Tool
Change Type: Product enhancement
Reason for Change: Configuration Tool removed
Replication Instructions: N/A
The Configuration Tool has been removed for the following reasons:
o The distinction between configuration to load into the BNR and the configuration
already loaded is not clear in the tool
o The tool was redundant with the Configuration Files Wizard
To inspect the content of the BNR, the Diagnostics Tool can be used
The Configuration Files Wizard will allow a user to setup or modify a configuration, save as a
file or package, and download to a connected BNR
Monitor Tool
Change Type: Product Enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.9.0
Replication Instructions: N/A
Added support for the new module.getMaintenanceInfo commands and responses
Added BNA6F as new type to setup the BNA6/BNR using bnr.SetSystemConfiguration
Diagnostic Tool
Change Type: Product enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.9.0
Replication Instructions: N/A
Added display information to the diagnostics tool for the new module.getMaintenanceInfo
parameters (reasons, sensors cleanness and bundler slippage)
Added BNA6F as new type
Configuration Wizard
Change Type: Product enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.9.0
Replication Instructions: N/A
Added support to configure the new module.getMaintenanceInfo configurations in the
configuration wizard
Added support to assign BNA6F as new unit type in the configuration wizard
Diagnostic Tool
Change Type: Product enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.8.1
Replication Instructions: N/A
The BillAcceptanceHistory, BillDispenseHistory and SystemFailureHistory and History Reports
dialog boxes have been updated to display modified counters
Monitor Tool
Change Type: Product enhancement
Reason for Change: Handling new functionality of the BNR firmware version 1.8.1
Replication Instructions: N/A
Update currency code filter in dialog box for CashIn, Denominate and Dispense commands.
Figures (ciphers) are now allowed for specific coupons to be accepted.
The BillAcceptanceHistory, BillDispenseHistory and SystemFailureHistory and History Reports
dialog boxes have been updated to display modified counters
CCR case fixed: ALAI-99RDR9
Configuration Wizard
Change Type: Correction
Reason for Change: The option to configure the Loader CashType was not operational in the
previous version
Replication Instructions: With the 2013 Support Tool, attempt to configure the Loader CashType
with a different value. The new value will not be set.
The option ALWAYS_SET_CASH_TYPE is now taken into account.
CCR case fixed: FXDU-9A3H6U
Install/Uninstall Tool
Change Type: Correction
Reason for Change: All files under MEI directory were removed
Replication Instructions: With the 2013 Support Tool uninstaller, uninstall the Support Tool. All files
in the MEI directory will be uninstalled
When uninstalling BNR Support Tools now, only files related to this tool are removed from the
directory Program Files/MEI/.
CCR case fixed: SWMH-99WRCA
Configurator Tool
Change Type: Product enhancement
Reason for Change:
Correcting issues.
Handling new functionality of the BNR firmware version 1.7.0
When uncompressing ".zcf" configuration files, temporary data files are stored in the “official”
temporary directory, depending on the operating system. These data files as well as unzipped audit
or configuration files are automatically deleted when the BNR Support Tool is closed.
Configuration tool: every configuration page can be activated or inactivated using the flag “Add to
configuration file”, whatever was the option in the referenced file.
When there is no change in the “Configure Cash Unit” page, the cash units remain unchanged (and
are no longer erased).
Fixed: The previous CashUnits configuration could be faulty, due to a bug in the Java API (fixed in
the 1.6.0 version of the API). Some problems formally observed include:
faulty LogicalCashUnit counts (Cashbox);
Loader created instead of a pair of Recylcers;
unable to apply the requested configuration even if correct (ParameterInvalid or CashUnitError
returned).
Some windows have been resized.
Diagnostic Tool
Change Type: Product enhancement
Reason for Change:
Correcting issues.
Handling new functionality of the BNR firmware version 1.7.0
Diagnostic files can be created as compressed files. The default option is “not compressed” and
can be modified in the bnrCtl.properties file. Both compressed and uncompressed files can be
opened with the Diagnostic Tool.
When saving an audit file, the checking of mandatory fields (in UserInfo, the company name and a
comment) has been improved. When these fields are not set, the GenerateAuditFile icon is grayed
(inactive) but a tool tip text has been added.
Refresh feature enhancement (regulation values and diagnosis pages).
Memory leak fixed. This problem could lead to OutOfMemory error or blank page display.
The transportCount was not retrieved by the Diagnostic Tool so its value was always 0. This count
was also faulty in audit reports generated with old versions of the BNR Support Tool (≤ 1.4.0).
Display enhancement. In the UseHistory window, times and voltage display has been modified. In
the BillAcceptanceHistory window, the counters display has been corrected.
Tool Bar
Change Type: Product enhancement
Reason for Change: Improving user friendliness
Each tool icon is now disabled either if no BNR is connected or if the user doesn’t have the access
to the tool according to the permission’s list of his profile.
User profiles
The default Standard User profile includes the ability to access to the BNR transaction status
command.
Reliability
The launch process has been reviewed and secured, in order to identify why the product cannot
start (or can start but with some features unavailable) and provide clear information to the user.
Fixes :
Unable to download Cashbox firmware.
Changes on loader depositCount not applied to BNR.
Unable to delete only one denomination.
Diagnostic tool:
“Save diagnostic“ operation can be cancelled.
Monitor tool :
Bnr.Reject and Bnr.Retract ready for use with the next BNR firmware.
Macro folder can be changed.
USB communication :
The library javaxusb.dll is renamed megjavaxusb.dll to avoid potential conflict with other
existing libraries.
Memory leakage fixes in megjavaxusb.dll
Fixes to support communication through hubs USB 2.0.
-------------------------- 2009 to 2010 ------------------------
Configuration Tool:
PCUs and LCUs can be managed using this tool. It is now possible to add, delete and change
cash units from this tool.
Configuration wizard:
Configuration process has been reviewed. It is now more secure and a default configuration is
proposed.
Configuration file management:
The “File” view is now used to list configuration files. Those files can be directly opened by
double-click on it.
Possibility to add, delete or change the firmware in a configuration file.
User folders:
For compatibility with latest Microsoft operating systems, user created folders and files are now
located under C:\Documents and Settings\”username”. The following structure is created:
MEI\BNR Support Tool
\Configurations
\Diagnostics
\Data
\Bills
\Firmwares
User interface:
New buttons “Expand” and “Collapse” to open or close all sections in a view at once.
“Serial Number” field is renamed “MSN” (Module Serial Number).
Dynamic help has been added from all tools. Documentation has been updated with latest
changes.
Audit report:
Component versions have been added in the generated audit files.
------------ USB Driver 1.25.0 to 1.27.0 ------------
1.27.0
Delivered with Java SDK 1.1.0, Win32 SDK 1.2.1, .NET SDK 1.2.1 and BnrFlash 1.2.1
o - Since 1.26.0, only megjavaxusb.dll is updated.
o - megjavaxusb.dll (1.2.0.1) - Memory leakage fixes.
1.26.0
o - Delivered with BNR ST 2010a
o - megjavaxusb.dll (1.2.0) - The library javaxusb.dll is renamed megjavaxusb.dll to avoid
potential conflict with other existing libraries. Memory leakage fixes and support for
communication through USB 2.0 hubs.
1.25.0
o - Delivered with BNR ST 2009, 2010
o - megusb.dll (1.0.0) - Replaces motusb.dll. Support for USB communication through USB 2.0
hubs.
-------------------------- 2009 ------------------------
First official product release to the public