SoMove_V2.10.0_ReleaseNotes
SoMove_V2.10.0_ReleaseNotes
0
- Release Notes -
This document contains important information about the SoMove software component and Release Content.
1. Package Content
SoMove 2.10.0
FTDIDriver64Bit V1.0.0
FTDIDriver32Bit V1.0.0
2. Features
2.1.1 Features
2.2.1 Features
> Streamlined Firmware Login Mechanism in California Law (CAL) security enable flow.
> >317601: Connection to the device is not working after Auto-Adaption scanning for few scenarios.
> >261199, 261599: SoMove: Disconnection takes long time and exception occurs when restarting the device through IPV6.
2.3.1 Features
> Import project functionality in SoMove Home page for ATV6000 (Commissioning Assistant)
> Support of ATS430, ATS490 and ATV6000 firmware updates through Secure Firmware Update tool.
> >319980: SoMove opening takes 5 to 10 minutes, when Ethernet cable is plugged to the PC.
> >328667: SoMove ATV320 Solar: Frequent disconnection between device and DTM in SoMove.
> >335410: SoMove ATV12 : Connection lost for Serial Modbus Connection.
2.4.1 Features
> Integration of Modbus Communication DTM Library V2.6.36
> >299989: SoMove (ATV320)- Difficult/Impossible to change Ethernet parameters online with SoMove 2.9.5
> >306458: SoMove (ATV320)- SoMove freezes when trying to change the option board setting
> >132626: SoMove - scanning the drive by Modbus serial/Auto-Adaptation does not work reliably
> >305625: SoMove - installation fails: Schneider Electric Modbus Communication DTM Library cannot be installed
> >302086: SoMove 2.9.5 – Edit Connection/Advanced Settings does not respond (Please refer 4.6 section).
> >305625: SoMove - installation fails: Schneider Electric Modbus Communication DTM Library cannot be installed
> >297357: SoMove - Spanner Icon is not coming for the modified parameters in print PDF file
2.4.3 Updates
> > From SoMove Version 2.9.7 Windows 7 support has been discontinued. Please use SoMove 2.9.6 or lower versions for the support.
> > 211959: Release notes - Added information about supported DTMs
> > 301956: Release notes - Added list of trusted certificates required in case of facing Error 1330 and installation without internet.
2.5.1 Features
> Integration of Modbus Communication DTM Library V2.6.29
> >210382: SoMove does not comply with 150% Scale and Layout display setting
> >231690: SoMove does not correctly recognize the PC display scaling (dpi).
2.5.3 Updates
> > Opening of PowerSuite(.psd,.31c,.312,.61c,.61p,.lif,.71p,.71f,.71c,) files are no more supported. Please use SoMove 2.9.5 or lower version for this support.
2.6.1 Features
> >218973: SoMove 2.9 cannot open older, password-protected .PSX projects.
> >260843: SoMove 2.9.2.0 cannot convert TeSysT (Power Suite2:.impr) files.
> >253525: SoMove Power Suite file conversion error
> >273038: SoMove : Installation error Popup Shown while Installing SoMove when newer version of Microsoft edge webview2 runtime is installed.
> >200207: SoMove Catalog update is happening for every user, instead of common catalogue update.
> >278387: SoMove installation will fail if existing License Manager version is not older than the one being installed.
> >271197: SoMove cannot be installed - 1330/1712 errors on components, outdated/missing certificates
2.7.1 Features
> >243084: SoMove Missing ReadMe file in SoMove_FDT.zip - Fix provided, Readme and Release note included as part of SoMove_FDT.zip.
2.8.1 Evolutions
>>164179: SoMove crashed with exception "Unrecognized configuration section system.serviceModel" - caused due to corrupt .net framework installation.
> Adaptations to support Fortis Shadow offer references for ATV9xx DTM Library
> ATV12 and ATS22 DTM not working during start up in SoMove V_2.7.5 issue fixed.
> Start Page improvement (Frequently Asked Questions, Schneider Electric Latest News, Survey Link).
> Support for IPV6 discovery and locate function for TeSys Island.
> 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.
> Help Manual not displayed in some languages has been resolved.
> Start page action buttons now has Schneider style icons.
> Start Page has a New Device Conversion actions button under tools section.
> Edit Connection screen now has Help button for connection specific help
> Start Page improvement (Last Connected Device Information Installed DTM information, updated icons).
> 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.
3. Some Restrictions
> In the second instance of the SoMove application, Devices connected on Modbus Serial Link / CANOpen 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.
> SoMove crashes with COM port configured to COM3 in some laptops.
> 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
> 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.2 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
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
> 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
4.5 Error 1330 - Trusted Certificate Error/Invalid Digital Signature Error in case of installation without internet.
If user is unable to install SoMove in offline mode. Please verify if any of the below digital certificate is/are missing, please install the digital certificate and continue
with installation.
> Entrust
> VeriSign
> GlobalSign
1. Please upgrade the system with latest Microsft software and security updates.
6. Click on "Details".
Certificate has to be installed/updated on following setups: SoMove, CANopenDtmLibrary, LicenseManager, ModbusDtmLibrary, SESU.
4.6 If Edit Connection/Advanced Settings does not respond then please follow the below steps.
2. Locate the Windows Font Cache Service. Double click on this service to open its properties dialog. Click Stop under "Service status" to stop this service, and then
select Disabled from the "Startup type" list to completely disable this service. Finally, click Apply.
3. Locate the "Windows Presentation Foundation Font Cache 3.0.0.0" service.(If exists) Double click on this service to open its properties dialog. Similarly, click Stop
and select Disabled to stop and disable this service. Click Apply to save the changes.
4. Navigate to the path C:\Windows\ServiceProfiles\LocalService\AppData\Local. If a warning dialog pops up saying you don't have permission to access this folder,
just click on Continue to allow access. Then delete all .dat files that start with FontCache. (If Delete is not allowed then restart the system and try to delete)
5. Once delete operation is done then restart the SoMove and try to launch the Edit Connection/Advanced Settings.
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')