Schneider Unitelway Driver - Release Notes
Schneider Unitelway Driver - Release Notes
Schneider Unitelway Driver - Release Notes
Release Notes
Table of Contents
1 SYSTEM REQUIREMENTS.................................................................................................................... 2
2 SETUP PROCEDURE............................................................................................................................. 3
2 SETUP PROCEDURE
Note: After a driver upgrade it is necessary to reset a connection (DRIVERS Manager ->
UNITELWAY Driver -> Configuration -> Edit… -> OK -> OK) before establishing a connection.
- 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 - 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
- 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
- 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:
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.
Windows 7 / 32 Bit:
Windows6.1-KB3033929-x86.msu
Windows6.1-KB3035131-x86.msu
- 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:
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.
Windows 7 / 32 Bit:
Windows6.1-KB3033929-x86.msu
- Unitelway Driver projects are now build with Visual Studio 2008 SP1
---> Unitelway Driver projects migrated from VS2005 to VS2008 SP1
- Unitelway Driver install projects are now build with InstallShield 2015
---> Migration of Unitelway Driver install projects from IS2008 to IS2015
General Remarks:
- Windows 10 support
- 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.
- 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.