SoMove V2.9.4
  - Release Notes -  

  This document contains important information about the SoMove software component and
Release Content.  
 
     

        1.    Package Content

Software Component Name Version

SoMove V2.9.4

Modbus Communication DTM Library V2.6.16

CANopen Communication DTM Library V1.2.3

Schneider Electric Software Update V2.6.3

Schneider Electric License Manager V2.8.2

Modbus Driver - 7/8.1/Win10 Pro (64 bits) V3.21IE31

Modbus Driver - 7/8.1/Win10 Pro (32 bits) V2.21IE31

2.   Features

2.1  What's new in V2.9.4

    2.1.1 Features

> Integration of SESU V2.6.3.

> Integration of 1Licensing Brick V2.8.2

> New Tool integrated - Secure Firmware Update

Secure firmware update tool , helps the user to flash the firmware to the device.
Currently supports only Altivar soft starter ATS480 DTM version V1.1.5 and above.

    2.1.2 Bugs Fixes

>>243084: SoMove Missing ReadMe file in SoMove_FDT.zip - Fix provided, Readme and Release note included
as part of SoMove_FDT.zip.

2.2  What's new in V2.9.2

    2.2.1 Evolutions

>>220054: Support for ATS480 DTM Library

>>225739: Support for ATV6000C DTM Library

>>226621: Support for Import of security backup Image file.

>>230599: Integration of 1Licensing Brick V2.8.1

>>234638: Integration of new SESU Brick V2.5.3

    2.2.2 Bugs Fixes

>>200205: SoMove License activation error 0x800008FF - caused due to corrupt trusted storage.

>>164179: SoMove crashed with exception "Unrecognized configuration section system.serviceModel" - caused
due to corrupt .net framework installation.

2.3  Features of V2.9.0

> Device Conversion UI evolution

> Adaptations to support Fortis Shadow offer references for ATV9xx DTM Library

> Integration of new SESU Brick V2.5.1

> Integration of 1Licensing Brick V2.6.0

> Integration of new Modbus Comm DTM Library V2.6.16

> Integration of new Modbus Driver Suite V14.15.1

> Bug Fixes

2.4  Features of V2.8.402

> Fix for SoMove licensing issue

2.5  Features of V2.8.4

> IPV6 adaptations to support Secure connection on ATV DTMs

> Bug fixes .

2.6  Features of V2.8.3

> Securing the assemblies by code signing

> Bug Fixes.

2.7  Features of V2.8.2

> Integration of new One Licensing brick V2.5.0.(CVE-2019-8960, CVE-2019-8961)

> Includes new version of SESU V2.5.0.(CVE-2020-7520)

> Integration of Modbus Comm DTM library V2.6.14.

> Integration of Modbus Driver Suite V14.15.0.0 (CVE-2020-7523).

> Bug Fixes.

2.8  Features of V2.8.1

> One Licensing brick V2.4.0 implemented.
 > Updated version of SESU V2.4.0 is included.

> Updated version of Modbus Driver Suite V14.14 is included.

> Bug fixes .

2.9  Features of V2.7.6

> Updated version of CANopen Communication DTM Library V1.2.3 is included.

> Updated version of SESU V2.3.1 is included.

> ATV12 and ATS22 DTM not working during start up in SoMove V_2.7.5 issue fixed.

> Bug fixes .

2.10  Features of V2.7.5

> Start Page improvement (Frequently Asked Questions, Schneider Electric Latest News, Survey Link).

> IPV6 discovery improvement.

> Support for IPV6 discovery and locate function for TeSys Island.

> Updated version of Modbus Communication DTM Library V2.6.12 is included.

> Updated version of SESU V2.3.0 is included.

> Updated version of Modbus Driver Suite V14.13 is included.

> Bug fixes.

2.11  Features of V2.6.5

> Support for the latest Modbus Driver (14.12.1.0).

2.12  Features of V2.6.4

> Support for the latest Modbus Driver (14.11.0.0).

> Bug fixes.

2.13  Features of V2.6.3

> Updated version of Schneider Modbus Driver Suite V14.10.0.0 is included .

> Updated version of SESU V2.1.2 is included.

> Bug fixes.

2.14  Features of V2.6.2

> Support for IPV6 device discovery - Edit connection dialog now has additional button Modbus IPV6.

> Start page shows additional content and links on supported products and MySchneider app.

> Language selection option is now available on Start page.

> Help Manual not displayed in some languages has been resolved.

> Updated version of Schneider Modbus Driver Suite V14.9.0.0 is included.

2.15  Features of V2.6

> Start page action buttons now has Schneider style icons.

> Start Page has a New Device Conversion actions button under tools section.
 > Dpi issues has been resolved.

> Edit Connection screen now has Help button for connection specific help

2.16  Features of V2.5

> More than one instance of SoMove application can be launched.

> Start Page actions buttons are now organized thoughtfully.

> Start Page improvement (Last Connected Device Information Installed DTM information, updated icons).

> Edit Connection screen (Updated icons)

2.17  Features of V2.4

> Match DTM feature for unidentified device reference.

> Updated version of Modbus driver (V14.4).

> Updated version of Modbus Library.

2.18  Features of V2.3

> Updated version of Modbus Library.

2.19  Features of V2.1

> Online Save of project configuration.

> Updated version CANopen Library.

> Updated version of Modbus Library.

> Updated version of Modbus driver.

2.20  Features of V2.1

> New device selection screen with device icons grouped according to device type and custom.

> Improved device scan window.

> List of installed DTM's in the start page.

2.21  Features of V2.0

> Improved connection configuration which gives better device identification in supported network.

> Option to choose between "Upload and connect" or "Download and Connect" of the configuration when the
Connect button is clicked.

> Updated tool bar icons.

3.   Some Restrictions

> In the second instance of the SoMove application, Devices connected on Modbus Serial Link / CANOpen /
Bluetooth communication do not work if the same COM Port is used in other instance.

> SoMove will not run properly if Chinese fonts are not available in the system. You need to relaunch the
application and the language will be English by default. You may change the language after this relaunch.

> Com port setting are disabled sometimes (Random behaviour).

> SoMove crashes with COM port configured to COM3 in some laptops.

> SoMove Installation will not work in Chinese Windows XP machine.

 > Manual device catalog update is required once for CANOpen connection.

> 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 Manager and
Drivers will be un-installable/installable by any admin user. In case the old version of Driver Manager or 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.

4.   Troubleshoot

4.1  Concurrent Connection on Modbus Serial Link

The maximum number of concurrent Modbus connections is limited to four connections. After installation of the
Modbus Driver, one Modbus connection is created by default

If more connections are required, perform the following steps:

> Open the Windows Control Panel.

> Double-click the Driver Manager icon.

> Open the Modbus Serial Driver tab Configure and start all four instances of the Modbus serial PC driver.

> Check if all instances are running (four icons of the Modbus serial driver in the system tray).

NOTE: To perform these steps, administrator access rights are required.

4.2  Connection lost in Serial Communication

  In Case of “Connection Lost” when using Serial Communication, configure the Inter-Char Timeout from the
Modbus Driver as follows:

> Step1: Select the Modbus driver from the taskbar. The default settings for Inter-Char Timeout will be automatic.

> Step2: Select the COM Port to be used and change the Inter-Char Timeout value to higher value. E.g. 50 ms.

4.3 SoMove asks for old SESU/License manager files during uninstall

> Step: To overcome this issue, unzip the current installed SoMove setup and browse to the corresponding
component (SESU/ License Manager) MSI installer to uninstall

4.4  Modbus Driver Instantiation In Virtual Machine

  When SoMove V2.8.2 and above is installed on Virtual Machines with Win7/Win8.1 OS, the Modbus driver
instance is not started automatically after restart, if the Auto login option is enabled in the VM settings

 > Step: To work around this issue, the Autologin option needs to be disabled before SoMove installation

4.5 License Activation via SoMove Offline

Below troubleshooting steps needs to be followed, if the user is unable to activate the License offline through
SoMove

> Step1: Launch License Manager

> Step2: Click on Activate

> Step3: Click on Use another activation method

> Step4: Copy the instructions mentioned in the Activation Method dialog to the notepad and click on next

> Step5: Enter the SoMove activation key "A-XSJP-FS8N-B8V2" in the field

> Step6: Follow the instructions that is copied in the notepad

5  Security Updates
5.1  The following security vulnerabilities have been addressed in this release

  > CVE-2020-12525: SoMove - Deserialization vulnerability in fdtCONTAINER component and fdtCONTAINER

application

  > CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component
('Injection')