Schneider PLCUSB Driver

Release Notes

Service Release June 2020

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

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

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

4 RELEASE NOTES LAST MINUTE INFORMATION..............................................................................22

Schneider PLCUSB Driver – Release Notes Page 1 / 23

1 SYSTEM REQUIREMENTS
Schneider PLCUSB 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.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

Microsoft Windows Server 2019

Win10 IoT (64)

2 SETUP PROCEDURE

Schneider PLCUSB Driver Suite

PLCUSB driver is required to exchange data with Modicon M340, Modicon M580, Momentum Unity and
MC80 through the USB console port. To install the PLCUSB driver, please proceed as follows:
1. Run the executable file "SchneiderPLCUSBDriverSuite.exe".
2. Wait until installation is finished.

Schneider PLCUSB Driver – Release Notes Page 2 / 23

4 NEW FEATURES AND BUG FIXES

Service Release June 2020

Schneider PLCUSB Driver Suite

Setup Version 14.15.0.0 brings the following features and bug fixes:

- Driver Manager - Vulnerability VMT-1905: Local privilege escalation

o Setup creates a local non-administrator user account, dedicated only for Schneider Electric
communication drivers. This account has a strong password and is managed exclusively by
Driver Manager and the driver setup.
o GUI processes of Modbus and XIP drivers are created under this user account.

- PLCUSB Driver Suite - Bugfix UNITY00088306

o "Remote NDIS Compatible Device" network adapter is now replaced by “SE RNDIS xxx"
network adapter as soon as Schneider Electric USB driver is installed.

- PLCUSB Driver - Modification of M262-USB IP configuration

o M262-USB IP configuration looks initially as follows:

M262_USB_IP_ADDR = "192.168.200.1"
M262_USB_CLIENT_IP_ADDR = "192.168.200.2"
M262_USB_SUBNET_MASK = "255.255.255.0"

Note: Parameter value of M262_USB_IP_ADDR is only used for visualization purposes by

the driver and must be set by other means in the target device.

o The initial M262-USB IP configuration can be found after driver installation in the file
“%ProgramData%\Schneider Electric Communication Drivers\M262_USB_IP_Addr.cfg”.
Any modifications of this file become active the next time the target device is connected via
USB.

- PLCUSB Driver - Visualization of inactive RNDIS networks

o Standard SE USB connections (modem- or RNDIS-based) use the same IP addresses

90.0.0.1/90.0.0.2. That’s why after the first USB connection becomes active, all other
connections become inactive.
Inactive RNDIS-based network connections now visualize this state in their connection name
in 'Control Panel\All Control Panel Items\Network and Sharing Center'.
Note: An inactive modem-based connection behaves like a non-existing connection.

- PLCUSB Driver - Performance improvement

o Device arrival and removal events are now handled by dedicated threads for modem-based,
Standard SE-RNDIS-based and M262-RNDIS devices.

- PLCUSB Driver – Support for new SE-RNDIS device

o SE RNDIS PSX TM3 Bus Coupler (USB\VID_16DE&PID_0089)

Schneider PLCUSB Driver – Release Notes Page 3 / 23

 - PLCUSB Driver – Improved event logging and diagnostic information

Schneider PLCUSB Driver – Release Notes Page 4 / 23

Service Release November 2019

Schneider PLCUSB Driver Suite

Setup Version 14.14.0.0 brings the following features and bug fixes:

- PLCUSB Driver Suite - Silent installation of SE-customized FTDI- and SiLab- Virtual Com Port
Drivers.
o FTDI’s and SiLab’s SE-customized VCP Drivers are now WHCP-certified for all supported
Windows versions (Windows7, Windows7 x64, Windows8.1, Windows8.1 x64, Windows10,
Windows10 x64).

- PLCUSB Driver Suite - Installation for all users

o Driver Manager and PLCUSB Driver are no longer installed per user - like in the past -, but
for all users.
Possible conflicts due to this new paradigm: The installation of the new driver version must
be done by the same admin user, who did the old installation (<= V14.13.0.0).
This constraint won’t appear with future driver versions (>= V14.14.0.0), where driver will be
un-installable/installable by any admin user.
In case the old version of Driver Manager or PLCUSB Driver has been installed by a different
admin user, a user conflict message pops up, showing the user that must do the installation.
If the owning user account is orphaned, it must be deleted.

- Driver Manager - Bugfix of V14.10.0.0-regression of NA_Config graphical user interface.

o Drivers can be started via NA_Config-GUI.

o Enhanced event logging of Driver activation and deactivation.

- Driver Manager - Removed Install/update button

o Install/update button has become useless, since multiple driver setups are now contained in
a DriverSuite and there is no way to select a specific driver setup in the file system.

- PLCUSB Driver - Avoid illegal USB Driver initialization requests

o UsbConnect service filters now DBT_DEVICEARRIVAL- and

DBT_DEVICEREMOVECOMPLETE-notifications of all devices and delegates only those of
supported Schneider Electric devices to UsbConsole.
-

Schneider PLCUSB Driver – Release Notes Page 5 / 23

 - Service Release February 2019

Schneider PLCUSB Driver Suite

Setup Version 14.13.0.0 brings the following features and bug fixes:

- PLCUSB Driver - 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. Driver is now actived from DriverStore after
one of its supported devices has been plugged for the first time.
o Microsoft’s Driver Install Framework for API library (DIFxAPI.dll) is now used in the driver’s
InstallShield project to add the driver to the system.
o It’s no longer necessary to unplug the device on driver installation
o Driver uninstallation cleans the driver package from the DriverStore
o Orphaned driver packages (resulting from former driver setup versions) are removed from
DriverStore (Precondition: Powershell version >= 2.0).

BSOD after plugging M262 on PCs, running Windows10 V1709 (and

- RNDIS-based USB Driver -
above)
o This is a Windows 10 regression, introduced in V1709.
The following fixes are available via Microsoft’s Update Catalog:
Cumulative Non-Security (Update) DCAT for Windows 10 1709 - KB4480967 - 2019.01 C
Cumulative Non-Security (Update) DCAT for Windows 10 1803 - KB4480976 - 2019.01 C

o The very unstable USB-communication on virtual machines is still existing, because M262 is
constantly sending device-removal and device-arrival notifications.

- 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 PLCUSB Driver – Release Notes Page 6 / 23

Service Release March 2018
Schneider PLCUSB Driver Suite
Setup Version 14.12.0.0 brings the following features and bug fixes:

- PLCUSB Driver Suite - Issues with upgrade installations

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

- Driver Manager
o Bugfix: UNITY00086799
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 3 rd
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 Modbus-cable to a physical USB-port to see one of the following VCP-devices
appearing
 “Sepam Series (COMx)”
 “TSX C USB 485 (COMx)”
3) Select the appearing VCP-device and check that the expected DriverVer (see above) is
associated to this physical USB-port in its context menu’s “Properties->Driver-tab“.
4) If another DriverVer is associated, “Uninstall” the VCP-device via its context menu and
then unplug and replug the Modbus-cable to the same physical USB-port.
Select once again the appearing VCP-device and verify in its “Properties->Driver-tab“
that the expected DriverVer (see above) is now associated to the physical USB-port.

Schneider PLCUSB Driver – Release Notes Page 7 / 23

 - PLCUSB Driver – WHCP-certified for Windows 10 Version 1607, supporting now secure boot on
modern PCs, having UEFI_BIOS.

o This fixes the following PCRs:

 PCR - PEP0394694R - USB and UnitelWay driver doesn't work on Win10 X64
V1607 with secure boot enabled
 PCR - PEP0408952R - USB driver does not work with Windows 10 anniversary
update
 PCR - PEP0418905R - Unity Pro USB driver appeared unsigned in Windows 10

- PLCUSB Driver – Preparation for new M262 Controller.

o RNDIS-based USB-connection for M262 Controller gets Host-IP-Address 192.168.200.2
instead of 90.0.0.2
o PLC USB Driver Diagnostic shows the two possible USB-connections.
 Upper connection for Standard Schneider Electric USB IP-Addresses
(90.0.0.1 / 90.0.0.2)
 Lower connection for M262 USB IP-Addresses (192.168.200.1 / 192.168.200.2)

Schneider PLCUSB Driver – Release Notes Page 8 / 23

Service Release December 2017
Schneider PLCUSB 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

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

o Avoid crash by using undefined configuration (sometimes SubmitUrb returns
STATUS_SUCCESS without having filled m_Config).
o Cleanup of failed USB device initialization before retrying to activate configuration.
o Avoid deadlocks by no longer calling IoCompleteRequest while holding a spin lock.
o Avoid that on a failing device start there is an orphaned registry key remaining (and
interpreted by USBConnect-service as a connected modem cable).

o The PLCUSB-Driver is not WHCP-certified, because Microsoft’s Hardware Lab Kit Test
“DF Reinstall with IO Before and After (Reliability)” is still failing.
This causes a secure boot problem, existing since Window10 V1607, where only WHCP-
certified Kernel-Mode-Drivers are accepted.
The issue becomes visible after the device has been connected: Device Manager ->
BMX CPU Properties -> General tab -> “Windows cannot verify the digital signature for the
drivers required for this device. A recent hardware or software change might have installed a
file that is signed incorrectly or damaged, or that might be malicious software from an
unknown source. (Code 52)”.
The only workaround for that is to disable the secure boot functionality in the PC’s BIOS.
A successful certification to enable the installation under secure boot conditions is targeted
for March 2018.

- PLCUSB Driver – Improved USB-device initialization

o Service UsbConnect is now not only managing the dialing for modem-based USBCON-
connections but also the IP address assignment and network adapter renaming for RNDIS-
based network connections.
o There no longer a need for a reboot on Windows 8 / 8.1 / 10 after connecting an RNDIS-
device for the first time to an USB-port.
o No more dialing deadlocks by using RasDial in asynchronous mode and improved error
handling.
o Better visibility of dialing process by extensive event logging (Event Viewer -> Windows Logs
-> Application -> Source = {UsbConnect | UsbConsole | UsbRun | RasClient})
o In case there are multiple PLCs with a physical USB-connections (modem- or RNDIS-
based), only one USB-connection becomes the active one (gets assigned client IP-address
90.0.0.2). All inactive physical USB-connections remain inactive when the active USB-
connection gets unplugged. An inactive physical USB-connection only becomes active when
there is no active connection and it is unplugged and replugged.
o Improved messages, shown in PLC USB Driver Diagnostics dialog
o Service UsbConnect is now removed on driver deinstallation

- PLCUSB Driver – PCR - PEP0424610R

o Fixed: RasDial no longer uses the phonebook file ‘usb.pbk’ for establishing the modem
connection USBCON. (In case of dialing problems, usb.pbk sometimes got empty and
because of that a modem connection was no longer possible.)

- PLCUSB Driver – Preparation for new M262 Controller.

Schneider PLCUSB Driver – Release Notes Page 9 / 23

 o Future USB-Device with Vendor-ID/Product-ID 0x16DE/0x0300 should be identified as an
“SE RNDIS PSX M262 Controller”-network and get assigned client IP-address 90.0.0.2.
o

Schneider PLCUSB Driver – Release Notes Page 10 / 23

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

- Driver Manager and PLCUSB Driver - “SchneiderPLCUSBDriverSuite.exe” is sometimes crashing

o Driver Manager and PLCUSB 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

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

o Fixed: Polymorphous function interpreted string-parameter as handle, causing a test system
crash during test with Windows Hardware Lab Kit
o Applied Extended Validation-Certificate to Kernel-Mode-Driver files.

- PLCUSB Driver – PCRs - PEP0423128R, PEP0422506R

o Fixed: Setup applies work-around proposed by Microsoft for modem connectivity issue,
introduced in Windows10, Version 1703, by appending the String "SeLoadDriverPrivilege".
to the Multi-String-Key "RequiredPrivileges" of
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan]

Schneider PLCUSB Driver – Release Notes Page 11 / 23

Service Release January 2017
Schneider PLCUSB Driver Suite
Setup Version 14.9.0.0 brings the following features and bug fixes:

- Driver Manager and PLCUSB Driver projects are build with Visual Studio 2015
---> Driver Manager and PLCUSB Driver projects migrated from VS2008 SP1 to VS2015
---> Driver Manager and PLCUSB 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:

- Windows 10 Version 1607 (or later), if Quantum- or Premium-PLC is used:

In case USB communication between PC and Quantum-/Premium-PLC is not working please refer also
to "Hint - what users need to do" described in section “Service Release October 2016”

- 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 PLCUSB Driver – Release Notes Page 12 / 23

Service Release October 2016
Schneider PLCUSB Driver Suite
Setup Version 14.8.0.0 brings the following features and bug fixes:

- PCR PEP0351008R, OEM00065141 reported for ATV-IMC and M258 with SoMa 4.2
The USB communication on Win 10 / 64Bit version 1607 with M340 / M258 / ATV-IMC PLC fails.
After installation of PLCUSB driver and connection of the PLC error code 28 can be observed in
Windows Device manager for BMX CPU / M258 / ATV-IMC device.
Error 28 means: Device driver device could not be installed.
The issue is specific for the Win 10 / 64Bit version 1607 (Microsoft anniversary Windows 10 update
2016/07)
With former Versions of Windows 10 the issue does not show up.
---> fixed: Obsolete entries removed from PLCUSB.INF file
Microsoft handles INF file content more restrictive beginning with Windows 10 version
1607

- PCR PEP0356427R reported for Quantum Unity PLC with Unity 11.1

The USB communication on Win 10 version 1607 with Quantum Unity PLC fails.
The issue is specific for the Win 10 version 1607 (Microsoft anniversary Windows 10 update
2016/07)
With former Versions of Windows 10 the issue does not show up.
---> fixed: Obsolete entries removed from PLCUSB.INF file
Microsoft handles INF file content more restrictive beginning with Windows 10 version
1607

Hint - what users need to do:

1. Installation of latest SchneiderPLCUSBDriverSuite

2. Connect the USB cable between PC and PLC

The following steps 3. 4. and 5. needs to be done only in case communication between PC and PLC is not working.

It might happen that the Windows Device manager does not show a PLC USB Device under Modems but it does show a
USB Serial Device under COM ports.
Reason: Older PLC USB Device Driver (before V14.8.0.0) fails to install on Windows 10 Version 1607.
Windows registers that a device is plugged but it does not find the suitable driver for the device. Instead Windows
installs the default USB Serial driver usbser.sys (virtual COM port driver) automatically.

Schneider PLCUSB Driver – Release Notes Page 13 / 23

This behavior results in the entry "USB Serial Device" under "COM ports" of Windows Device Manager.

3. In Windows Device Manager uninstall USB serial device under COM ports (if it is listed)

4. Disconnect and reconnect the USB cable

Schneider PLCUSB Driver – Release Notes Page 14 / 23

5. In Windows Device Manager the PLC USB Device is listed under Modems now and works as expected.

Schneider PLCUSB Driver – Release Notes Page 15 / 23

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 PLCUSB Driver – Release Notes Page 16 / 23

Service Release September 2016
Schneider PLCUSB Driver Suite
Setup Version 14.7.0.0 brings the following features and bug fixes:

- OEM00063914 - Issue (the device cannot start. (Code 10)) with PLC USB driver (V3.7 IE17) and
ATV-IMC
---> fixed: ATV-IMC (Start Code 10, regression since Version 14.4.0.0)
Restored missing code in repository (Max. output size for ATV-IMC is 60 bytes)
- Driver Manager versions incremented

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 PLCUSB Driver – Release Notes Page 17 / 23

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

- PLCUSB Driver signing

---> PLCUSB Driver setup and components are signed with SHA2 certificate.

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

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

- UNITY00080899 - F1 button in USB Diagnostic screen leads to an error message: Failed to launch
help
---> fixed: As long as there is no help provided by PLC USB Driver Diagnostic, error message is
suppressed.

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 PLCUSB Driver – Release Notes Page 18 / 23

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

- PLCUSB Driver projects are now build with Visual Studio 2008 SP1
---> PLCUSB 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

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

- Klocwork static code analysis issues

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

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.

Schneider PLCUSB Driver – Release Notes Page 19 / 23

Service Release November 2015

Schneider PLCUSB Driver Suite

Setup Version 14.4.0.0 brings the following features and bug fixes:

- Windows 10 support

- PCR - PEP0292604R Ext-Unity8.1-USB driver does not reload when the PC is rebooted
Caterpillar has a problem with the SchneiderPLCUSBDriverSuite. The driver does not reload when
the M340 is connected to the PC during a reboot of the Laptop. In Windows Device Manager the
Error Code 10 is displayed (Driver Start error).
---> fixed: The PLCUSB driver is modified to do a more error tolerant USB device configuration
procedure.

- 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 PLCUSB Driver – Release Notes Page 20 / 23

Service Release March 2015

Schneider PLCUSB 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 PLCUSB Driver – Release Notes Page 21 / 23

Service Release September 2014
Schneider PLCUSB Driver Suite
Setup Version 14.2.0.0 brings the following features and bug fixes:

- PLCUSB Driver enhancements for MC80 controller

---> fixed: UNITY00070046 [Unity Service]: M80 USB connection driver displayed Momentum in OS
network window
---> fixed (by ReleaseNotes / Readme) UNITY00071266 Unity Pro V9 can not install M80 usb driver
automatically

- PLCUSB Driver does not connect to M258, ATV-IMC and M340 on Win8 and Win8.1 if USB cable is
disconnected and re-connected or PLC is power cycled - Icon does not appear in system tray.
---> fixed: UNITY00071284 USB driver: M340 USB driver icon disappear from status bar after power
cycle CPU,and can't reconnect again before restart win

- 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 PLCUSB Driver Suite

Setup Version 14.1.0.0 brings the following features and bug fixes:

- PLCUSB Driver enhancements for MC80 controller

---> fixed: UNITY00070046 [Unity Service]: M80 USB connection driver displayed Momentum in OS
network window
---> fixed (by ReleaseNotes / Readme) UNITY00071266 Unity Pro V9 can not install M80 usb driver
automatically

- PLCUSB Driver does not connect to M258, ATV-IMC and M340 on Win8 and Win8.1 if USB cable is
disconnected and re-connected or PLC is power cycled - Icon does not appear in system tray.
---> fixed: UNITY00071284 USB driver: M340 USB driver icon disappear from status bar after power
cycle CPU,and can't reconnect again before restart win

Internal Service Release July 2014

Schneider PLCUSB Driver Suite

Setup Version 14.0.1.0 brings the following features and bug fixes:

- PLCUSB Driver enhancements for MC80 controller

---> fixed: UNITY00070046 [Unity Service]: M80 USB connection driver displayed Momentum in OS
network window
---> fixed (by ReleaseNotes / Readme) UNITY00071266 Unity Pro V9 can not install M80 usb driver
automatically

- PLCUSB Driver does not connect to M258, ATV-IMC and M340 on Win8 and Win8.1 if USB cable is
disconnected and re-connected or PLC is power cycled - Icon does not appear in system tray.
---> fixed: UNITY00071284 USB driver: M340 USB driver icon disappear from status bar after power
cycle CPU,and can't reconnect again before restart win

Schneider PLCUSB Driver – Release Notes Page 22 / 23

 5 RELEASE NOTES LAST MINUTE INFORMATION

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

- The following restriction of older versions does no longer apply since Version 14.11.0.0:

- On Windows 8 / 8.1 / 10 - for IP address assignment (90.0.0.2) for USB network connection with
M580, Momentum Unity or MC80 controller a reboot is required after device is connected first
time to USB port and USB RNDIS driver installation has finished.

- For detailed information how to install the USB RNDIS Driver when M580, Momentum Unity,
MC80 controller is connected refer to document:

 Readme - USB Driver Installation M580 - Momentum Unity - MC80 controller.doc - Version
1.0

Schneider PLCUSB Driver – Release Notes Page 23 / 23