Schneider Unitelway Driver - Release Notes

Download as rtf, pdf, or txt
Download as rtf, pdf, or txt
You are on page 1of 14

Schneider Unitelway Driver

Release Notes

Service Release February 2019

Table of Contents
1 SYSTEM REQUIREMENTS.................................................................................................................... 2

2 SETUP PROCEDURE............................................................................................................................. 3

3 NEW FEATURES AND BUG FIXES........................................................................................................ 4

4 RELEASE NOTES LAST MINUTE INFORMATION................................................................................5

Schneider Unitelway Driver – Release Notes Page 1 / 14


1 SYSTEM REQUIREMENTS
Schneider Unitelway Driver is compliant with the following Operating Systems:

Microsoft Windows XP Professional 32 bit SP3 (up to version 14.4.0.0)

Microsoft Windows Server 2003 32 bit (up to version 14.4.0.0)

Microsoft Windows Vista Professional 32 & 64 bit (up to version 14.4.0.0)

Microsoft Windows 7 Professional 32 & 64 bit SP1

Microsoft Windows 8 Pro 32 & 64 bit

Microsoft Windows 8.1 Pro 32 & 64 bit

Microsoft Windows 10 Pro 32 & 64 bit

Microsoft Windows Server 2008 R2

Microsoft Windows Server 2012

Microsoft Windows Server 2012 R2

Microsoft Windows Server 2016

2 SETUP PROCEDURE

Schneider Unitelway Driver Suite


Unitelway driver is required to exchange data with Premium TSX PLC platforms via a serial connection. To
install the Unitelway driver, please proceed as follows:
1. Run the executable file "SchneiderUnitelwayDriverSuite.exe".
2. Wait until installation is finished.

Schneider Unitelway Driver – Release Notes Page 2 / 14


3 NEW FEATURES AND BUG FIXES

Service Release February 2019


Schneider Unitelway Driver Suite
Setup Version 14.13.0.0 brings the following features and bug fixes:

- Unitelway Driver – PEP0475142R, Driver doesn’t work after Windows Upgrade


o Driver setup copied driver files directly to their final locations and the driver’s inf-file didn’t
use CopyFiles-instructions to support driver activation from DriverStore.
Driver Package is now consistent and complete.
o Driver uninstallation cleans the driver package from DriverStore and removes the driver’s
device node from device tree.
o Orphaned driver packages (resulting from former driver setup versions) are removed from
DriverStore (Precondition: Powershell version >= 2.0).

Note: After a driver upgrade it is necessary to reset a connection (DRIVERS Manager ->
UNITELWAY Driver -> Configuration -> Edit… -> OK -> OK) before establishing a connection.

- Unitelway Driver – Migration of driver project


o ConfigurationType: Application -> Driver
o PlatformToolset: v140 -> WindowsKernelModeDriver10.0
o Driver Name: DuntlwNT.sys -> DUNTLW.sys
o Inf-file Name: Duntlwdm.inf -> DUNTLW.inf
o Use of POOL_NX_OPTIN opt-in mechanism to have a single driver binary that runs under
Windows8 and later (NonPagedPool-allocations have to be done with NonPagedPoolNx-
flag) and under Windows7 (NonPagedPool-allocations can only be done with
NonPagedPool-flag).

- Driver Manager - FTDI- and SiLab-Drivers don’t work after Windows Upgrade
o Driver setup copied driver files directly to their final locations and the driver inf-files didn’t use
CopyFiles-instructions to support driver activation from DriverStore.
Driver Packages are now consistent and complete. Drivers are now actived from DriverStore
after one of the supported Schneider Electric devices has been plugged for the first time.
o It’s no longer necessary to unplug SE-devices on driver installation
o Driver uninstallation cleans driver packages from DriverStore
o Orphaned driver packages (resulting from former driver setup versions) are removed from
DriverStore (Precondition: Powershell version >= 2.0).

- Driver Manager - PCR- PEP0486984R, PL7 cannot establish XIP-connection


o Security fixes, being introduced in V14.10.0.0 in component NetAccess, caused regressions
in WNETWAY2.dll methods “xip_init” and “XipAutoStart”.
These methods are now accessing shared memory with access right “FILE_MAP_WRITE”
instead of “FILE_MAP_ALL_ACCESS”.

- Driver Manager - Start menu shortcut according to Schneider Electric’s new branding guide line
o Windows 7: Schneider Electric -> Communication Drivers -> Driver Manager
o Windows 8 and above: Schneider Electric Communication Drivers -> Driver Manager

Schneider Unitelway Driver – Release Notes Page 3 / 14


Service Release March 2018

Schneider Unitelway Driver Suite


Setup Version 14.12.0.0 brings the following features and bug fixes:

- Unitelway Driver Suite - Issues with upgrade installations


o In case a Driver Manager and Unitelway Driver are installed, they are uninstalled to assure a
subsequential full installation of the new Driver Manager and Unitelway Driver.

- Unitelway Driver – Use of Windows version’s native DotNet version


o Unitelway Configuration uses DotNet 2 for Windows 7 and now DotNet 4 for Windows 8 and
following Windows versions. By this there is no longer a need to check for and install DotNet
3.5-SP1 as a prerequisite on Windows 8 and following Windows versions.

- Driver Manager
o Bugfix: UNITY00086799
FeaturesDriver Manager can now be uninstalled via Programs and Features.
Since SE-Communication-Drivers are depending on Driver Manager, all SE-Communication-
Drivers must be uninstalled before Driver Manager can be uninstalled.

o Digital signature error (Code 52), although there are WHCP-certified drivers installed

Note:
 New driver versions don’t become active automatically, if once an older version had
been associated to a physical USB-port (e.g. by plugging a Modbus cable to the physical
USB-port). An indication for such a still existing USB-port association to an older driver
version is a device digital signature error (Code 52).
 Different physical USB-ports may be associated to different driver versions!

Driver Manager brings since version 14.11.0.0 new WHCP-certified versions of the two 3rd
Party Virtual Com-Port drivers "Sepam Series", based on silabser.sys from Silicon Labs Inc,
DriverVer=11/30/2016,6.7.4.261 and "TSX C USB xxx"", based on ftdibus.sys and
ftser2k.sys from Future Technology Devices International Limited
DriverVer=02/24/2017,2.12.26.0.

Please assure that the latest installed VCP-driver version is associated to all physical USB-
ports by applying the following procedure to all physical USB-ports:

1) Open Device Manager and expand the node “Ports (COM & LPT)”
2) Plug Unitelway-cable to a physical USB-port to see the VCP-device
“TSX C USB 485 (COMx)” appearing
3) Select the appearing VCP-device and “Uninstall device” via context menu
4) Unplug and replug Unitelway-cable

Schneider Unitelway Driver – Release Notes Page 4 / 14


Service Release December 2017
Schneider Unitelway Driver Suite
Setup Version 14.11.0.0 brings the following features and bug fixes:

- Driver Manager – WHCP-certified


o 3rd Party Virtual Com-Port drivers "Sepam Series" based on silabser.sys from Silicon Labs
Inc, DriverVer=11/30/2016,6.7.4.261 and "TSX C USB xxx"", based on ftdibus.sys and
ftser2k.sys from Future Technology Devices International Limited
DriverVer=02/24/2017,2.12.26 are now WHCP-certified for Windows 10 Version 1607 for
supported Schneider-Devices.
o Improved error messages in MODBUS-Test dialog

- Unitelway Driver – Windows Hardware Compatibility Program (2. Step)


o Driver passed all of Microsoft’s Hardware Lab Kit Tests and got WHCP-certified.
It is now running on modern PCs, having secure boot enabled and Windows 10 Version
1607 or later installed.

Schneider Unitelway Driver – Release Notes Page 5 / 14


Service Release July 2017
Schneider Unitelway Driver Suite
Setup Version 14.10.0.0 brings the following features and bug fixes:

- Driver Manager and Unitelway Driver - “SchneiderUnitelwayDriverSuite.exe” is sometimes crashing


o Driver Manager and Unitelway Driver setup projects are migrated back from IS2016 to
IS2015

- Driver Manager – Update and Refactoring


o Updated Virtual Com-Port driver "Sepam Series", based on silabser.sys from Silicon Labs
Inc., from DriverVer=04/24/2012,6.5.3.0 to DriverVer=11/30/2016,6.7.4.261
o Updated Virtual Com-Port driver "TSX C USB xxx", based on ftdibus.sys and ftser2k.sys from
Future Technology Devices International Limited, from DriverVer=03/18/2011,2.08.14 to
DriverVer=02/24/2017,2.12.26
o Refactored (reduced) deployed files

- Unitelway Driver – Windows Hardware Compatibility Program (1. Step)


o Fixed: Implemented missing dispatch routine for the required major function code
IRP_MJ_SYSTEM_CONTROL, causing a test system crash during test with Windows
Hardware Lab Kit
o Applied Extended Validation-Certificate to Kernel-Mode-Driver files.

- Unitelway Driver – Vijeo Connect request


o Increase maximal Link-Timeout from 99 up to 5000 msec.

Schneider Unitelway Driver – Release Notes Page 6 / 14


o Service Release January 2017

Schneider Unitelway Driver Suite


Setup Version 14.9.0.0 brings the following features and bug fixes:

- Driver Manager and Unitelway Driver projects are build with Visual Studio 2015
---> Driver Manager and Unitelway Driver projects migrated from VS2008 SP1 to VS2015
---> Driver Manager and Unitelway Driver setup projects migrated from IS2015 to IS2016

- Driver Manager - Correction Modbus test tool and XWAY test tool
---> fixed: Modbus test tool respectively XWAY test tool might hang up when playing with
Start / Stop / Connect / Disconnect – buttons.

General Remarks:

- SHA2 signed driver software:

All available Windows service releases and patches shall be installed to ensure a proper behavior of the
SHA2 signed driver software. This is mandatory prerequisite especially for Windows 7.

The following patches provide basic SHA2 support for Windows 7:


Windows 7 / 64 Bit:
Windows6.1-KB3033929-x64.msu
Windows6.1-KB3035131-x64.msu

Windows 7 / 32 Bit:
Windows6.1-KB3033929-x86.msu
Windows6.1-KB3035131-x86.msu

- This driver release no longer supports Windows XP.

- This driver release no longer supports Windows Vista.

- Driver usage in Virtual BOX environment is not supported.

Schneider Unitelway Driver – Release Notes Page 7 / 14


Service Release July 2016
Schneider Unitelway Driver Suite
Setup Version 14.6.0.0 brings the following features and bug fixes:

- Unitelway Driver signing


---> Unitelway Driver setup and components are signed with SHA2 certificate

- Unitelway Driver installation - Exclusion of Windows XP and Windows Vista


---> Installation of Unitelway Driver on Windows XP / Windows Server 2003 and
Windows Vista / Windows Server 2008 is no longer possible.

- UNITY00081130 - Unknown software named "Duntlw" after Unity Pro V11.1 installation

Background:
Starting with PCDrivers_ServiceRelease_November_2015, there is an upgrade issue with
the 32-bit Unitelway Driver, due to changed 'Product Code' and 'Product Name'.
'Product Code' changed from {3CEB7206-AFB6-4838-B8C9-012E7B67F708} to {055D0121-
0A40-42AD-AD01-0F52A94B7B64} and
'Product Name' changed from 'Unitelway Driver' to 'Duntlw'.

---> fixed: 'Product Code' and 'Product Name' are changed back to the one's of
PCDrivers_ServiceRelease_March_2015, but there is no automatic way to get rid of old 'Duntlw'-
installations: 'Duntlw'-installations have to be uninstalled manually.
Note: as long as 'Duntlw'-installations represent the newest 32-bit Unitelway Driver version, old
'Unitelway Driver'-installations have to be uninstalled manually, too.

- UNITY00081638 - Unitelway communication software needs .Net Framework V3.5 and Unity loader
doesn't install it.

Background:
Unitelway drivers 32 and 64bit require .Net Framework 2.0. Windows 10 doesn't provide this by
default. Therefore the Windows feature .Net Framework 3.5 (includes .Net 2.0 and 3.0) has to be
installed. When Unitelway driver 'Configuration' button is pressed a dialog appears with the option to
'Download and install this feature'; this has to be chosen.

---> fixed: .Net Framework 3.5 (Windows feature) is now an installation pre-requisite of the Unitelway-
driver, meaning the .Net Framework 3.5 is requested to be installed before the driver installation.

General Remarks:

- SHA2 signed driver software:

All available Windows service releases and patches shall be installed to ensure a proper behavior of the
SHA2 signed driver software. This is mandatory prerequisite especially for Windows 7.

The following patches provide basic SHA2 support for Windows 7:


Windows 7 / 64 Bit:
Windows6.1-KB3033929-x64.msu
Windows6.1-KB3035131-x64.msu

Windows 7 / 32 Bit:
Windows6.1-KB3033929-x86.msu

Schneider Unitelway Driver – Release Notes Page 8 / 14


Windows6.1-KB3035131-x86.msu

- This driver release no longer supports Windows XP.

- This driver release no longer supports Windows Vista.

- Driver usage in Virtual BOX environment is not supported.

Schneider Unitelway Driver – Release Notes Page 9 / 14


Service Release May 2016
Schneider Unitelway Driver Suite
Setup Version 14.5.0.0 brings the following features and bug fixes:

- Unitelway Driver projects are now build with Visual Studio 2008 SP1
---> Unitelway Driver projects migrated from VS2005 to VS2008 SP1

- Newer Version of Microsoft Windows Driver Development Kit (WinDDK) used


---> Replaced WinDDK\6000 by WinDDK\7600.16385.1

- Unitelway Driver install projects are now build with InstallShield 2015
---> Migration of Unitelway Driver install projects from IS2008 to IS2015

- Klocwork static code analysis issues


---> fixed: Klocwork issues, mainly in the area memset, memcpy, sprintf, strcpy, strlen

- UNITY00073081, PCR - PEP0323597R UNITELWAY Driver configuration with "CnfUTW3.dat" file at


wrong place
The file path to write the configuration file was wrong in seldom cases.
---> fixed: File path used to read and write the configuration file are identical now.

General Remarks:

- This driver release no longer supports Windows XP.

- This driver release no longer supports Windows Vista.

- Driver usage in Virtual BOX environment is not supported.

- In PCDrivers_ServiceRelease_November_2015 and PCDrivers_ServiceRelease_May_2016 , there is an


upgrade issue with the 32-bit version of Unitelway Driver, due to changed 'Product Code' and 'Product
Name'. Product Name changed from 'Unitelway Driver' to 'Duntlw'.
Old 'Unitelway Driver'-installation is remaining inactive beside the current active 'Duntlw'-installation.
There is no automatic way to get rid of old 'Unitelway Driver'-installations. 'Unitelway Driver'-installations
have to be uninstalled manually.
In the next planned PCDrivers_ServiceRelease in 2016, 'Product Code' and 'Product Name' will be
changed back to the one's of PCDrivers_ServiceRelease_March_2015.

- Unitelway drivers 32 and 64bit require .Net Framework 2.0


Windows 10 doesn't provide this by default. Therefore the Windows feature .Net Framework 3.5 (includes
.Net 2.0 and 3.0) has to be installed.
When Unitelway driver 'Configuration' button is pressed a dialog appears with the option to 'Download
and install this feature'; this has to be chosen.
In the next planned PCDrivers_ServiceRelease in 2016 this will be an installation pre-requisite, meaning
the .Net Framework 3.5 is requested to be installed before the driver installation.

Schneider Unitelway Driver – Release Notes Page 10 / 14


Service Release November 2015
Schneider Unitelway Driver Suite
Setup Version 14.4.0.0 brings the following features and bug fixes:

- Windows 10 support

- Klocwork static code analysis issues


---> fixed: Klocwork Cyber Security Top10 issues are fixed

- Specific usage of XWAY Test tool blocks restart of Driver Manager.


--->fixed: Correction of XWAY Test termination.

- Driver Manager Repair functionality uses wrong cached MSI file.


--->fixed: To ensure that Driver Manager Repair uses the correct MSI file old MSI files are deleted but
the new MSI file remains in cache.

- New automated build environment

Schneider Unitelway Driver – Release Notes Page 11 / 14


Service Release March 2015

Schneider Unitelway Driver Suite


Setup Version 14.3.0.0 brings the following features and bug fixes:

- Support of Windows Server 2012 R2


---> fixed: UNITY00075091 In order to align with Unity Pro V10, Modbus, USB, Unitelway, XIP,
USBFIP Drivers should be supported on Windows Server 2012

- PCR - PEP0262253R EXT(CPCU COMPAGNIE PARISIENNE DE)XWAY_Driver_Manager-pb with


WIN8 server PC
A customer is not able to restart the XIP driver from the XWAY driver manager menu.
---> fixed: Driver Manager / NA_Service changed to allow driver access also from Remote Desktop
connection.

- NA_config tool shows error message "Cannot StartDriver (error 0)" when driver start is executed
---> fixed: Driver Manager / NA_Config tool correction done in Driver Start Stop method.

- Install Repair functionality for Driver Manager


---> fixed: Driver Manager is visible in Control Panel under Programs and Features now and provides
Repair functionality. This enables user to repair the Driver Manager in case of files are modified or
deleted.

- Driver Setup should run without user interaction.


---> fixed: To allow complete silent installation, interactive message boxes displayed during Driver
setup are deactivated.

- Empty folder "Drivers" is created during installation


---> fixed: UNITY00073029 : Windows Vista/7/8/8.1 (32bit) Empty folder "Drivers" is created during
installation
The issue is caused by a wrong setting inside the DriverManager setup.
Driver Manager Setup is corrected to prevent creation of empty folder c:\Windows\Program Files\
Schneider Electric\Drivers

- Schneider Electric should be displayed with capital letters Windows StartMenue


---> fixed: For 32bit version of Windows Vista (and higher) the entry in StartMenue is "schneider
electric" and not "Schneider Electric" as expected.
Driver Manager Setup is corrected to show the expected entry "Schneider Electric".

- Installation finished information is missing.


---> fixed: A message is displayed now when installation is finished.

Schneider Unitelway Driver – Release Notes Page 12 / 14


Service Release September 2014

Schneider Unitelway Driver Suite


Setup Version 14.2.0.0 brings the following features and bug fixes:

- Unitelway Driver does not install on Win8.1/32Bit and Win8.1/64Bit


---> fixed: UNITY00071434 Installation: Unitelway can't be used in Windows 8.1. Device can't be find

- Temporary Setup directory not removed after installation of Driver Suite


---> fixed: UNITY00073023 Regression: Three folders about Modbus, USB and Unitelway in the path
...\Schneider Electric\ are NOT removed after install

Internal Service Release September 2014

Schneider Unitelway Driver Suite


Setup Version 14.1.0.0 brings the following features and bug fixes:

- Unitelway Driver does not install on Win8.1/32Bit and Win8.1/64Bit


---> fixed: UNITY00071434 Installation: Unitelway can't be used in Windows 8.1. Device can't be find

Internal Service Release July 2014

Schneider Unitelway Driver Suite


Setup Version 14.0.1.0 brings the following features and bug fixes:

- Unitelway Driver does not install on Win8.1/32Bit and Win8.1/64Bit


---> UNITY00071434 Installation: Unitelway can't be used in Windows 8.1. Device can't be find

Schneider Unitelway Driver – Release Notes Page 13 / 14


4 RELEASE NOTES LAST MINUTE INFORMATION

- To prevent wrong device detection (“Other device”) in Windows Device Manger, do not connect
device/controller to USB port before the relevant Schneider PC Driver Suite is installed.

Schneider Unitelway Driver – Release Notes Page 14 / 14

You might also like