Schneider PLCUSB Driver

Schneider PLCUSB Driver
Release Notes
Service Release January 2017
Table of Contents
1 SYSTEM REQUIREMENTS ..................................................................................................................... 2
2 SETUP PROCEDURE .............................................................................................................................. 2
3 NEW FEATURES AND BUG FIXES ........................................................................................................ 3
4 RELEASE NOTES LAST MINUTE INFORMATION.............................................................................. 14
Schneider PLCUSB Driver – Release Notes Page 1 / 14

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 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
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.

3 NEW FEATURES AND BUG FIXES
Service Release January 2017

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 - 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.
- Driver Manager and PLCUSB Driver install projects are build with InstallShield 2016
---> Driver Manager and PLCUSB Driver install projects migrated from IS2015 to IS2016
- Klocwork static code analysis issues

---> fixed: Klocwork issues.
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
Windows 7 / 32 Bit:
- 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.

Service Release October 2016
- 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.

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

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

General Remarks:

Windows 7 / 64 Bit:
Windows 7 / 32 Bit:

Service Release September 2016
- 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:

Windows 7 / 64 Bit:
Windows 7 / 32 Bit:

Service Release July 2016
- 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:

Windows 7 / 64 Bit:
Windows 7 / 32 Bit:

Service Release May 2016
- 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

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

Service Release November 2015

- 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.

---> 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

Service Release March 2015

- 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.

Service Release September 2014
- 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


network window
automatically
Internal Service Release July 2014


network window
automatically

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.
- 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

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Schneider PLCUSB Driver - Release Notes

Uploaded by

Copyright:

Available Formats

Service Release January 2017

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

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

4 RELEASE NOTES LAST MINUTE INFORMATION.............................................................................. 14

Schneider PLCUSB Driver – Release Notes Page 1 / 14

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

Schneider PLCUSB Driver Suite

Schneider PLCUSB Driver – Release Notes Page 2 / 14

Service Release January 2017

- Klocwork static code analysis issues

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

- SHA2 signed driver software:

The following patches provide basic SHA2 support for Windows 7:

- 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 3 / 14

Hint - what users need to do:

1. Installation of latest SchneiderPLCUSBDriverSuite

2. Connect the USB cable between PC and PLC

Schneider PLCUSB Driver – Release Notes Page 4 / 14

4. Disconnect and reconnect the USB cable

Schneider PLCUSB Driver – Release Notes Page 5 / 14

Schneider PLCUSB Driver – Release Notes Page 6 / 14

- SHA2 signed driver software:

The following patches provide basic SHA2 support for Windows 7:

- 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 7 / 14

- SHA2 signed driver software:

The following patches provide basic SHA2 support for Windows 7:

- 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 8 / 14

- PLCUSB Driver signing

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

- SHA2 signed driver software:

The following patches provide basic SHA2 support for Windows 7:

- 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 9 / 14

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

- Klocwork static code analysis issues

- 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 10 / 14

Schneider PLCUSB Driver Suite

- Klocwork static code analysis issues

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

- Driver Manager Repair functionality uses wrong cached MSI file.