Schneider Electric Altivar Machine ATV320 DTM Library V1.7.

9
- Release Notes -
This document contains important information about the Altivar Machine ATV320 DTM Library software
component and Release Content.

1 Package Content

Software Component Name Version

Altivar Machine ATV320 DTM Library V 1.7.9

ATV320 V 1.7.9.0

2 Features

2.0 What's New in V1.7.9

2.0.1 Evolutions
>> 322937: Added Sensorless Flow Estimation Sketch-view layout.

>> 326005: Support of ATV320(Solar) V3.8IE49 firmware.

2.0.2 Bugs Fixes

>> 268602: DTM Altivar Machine "My Menu" customization

>> 242419: IO scanner data type change from "WORD" to "UINT"

>> 308527: Scope display issue

>> 269229: DeviceNet configuration issue.

>> 230461: Missing troubleshooting hint in Error 1010 message.

>> 213268: LO1 state animation is wrong in Operate tab

2.1 Features V1.7.7

2.1.1 Evolutions
>> Support for Solar family

280308: Support for references ending with C412

281802: Support of ATV320 V3.6IE47 firmware

288295: Added Anti-Jam Sketch-view layout.

2.1.2 Bugs Fixes

>> 212969: Corrected trailing zeros issue on ATVLogic password.

>> 279047: Corrected wrong configuration issue that was leading to Error-1006.

>> 267493: Corrected label for "Mains Voltage".

>> 278522: Resolved safety configuration transfer issue that was leading to INFE fault.
 >> 279566: Corrected the LAC (Level Access Control) refresh issue.

>> 278935: Corrected the SS1 wrong display issue on SSRU value.

2.2 Features V1.7.2

>> 236173: Large ATV Logic is not uploaded correctly.

>> 223589: 'Modify' topology wipes out all the customized parameters.

2.3 Features V1.6.1

2.3.1 Evolutions
>> 225354: Support of a new firmware V3.5IE46.

2.3.2 Bugs Fixes

>> 173263: In saved SoMove project, ATV logic program is lost while performing modify topology.

>> 191262: Somove Monitoring error, LO1 state is not updated with the device value in online mode.

>> 191263: PUC parameter is not available as part of scope tab channel parameters.

>> 200600: Motor parameters like RSA, LFA, IDA and TRA values remain at zero while using multi-motor function.

>> 232563: Missing long labels when SoMove language is Italian.

>> 206766: Wrong monitoring parameter, the display shows "19 2" instead of the actual frequency.

2.4 Features V1.5.0

> Support for new firmware version V3.4IE45

> Support Powerlink option card VW3A3619

2.5 Features V1.4.1

1. As part of the California CS Law compliance (IEC-62443-4-2 CR 1-1 Human user identification and authentication),
the DTM comes with a new set of features meant to provide a more secured connection to the device over Modbus
TCP (only applies to Ethernet and PROFINET fieldbuses)

In a few words:

a. User authentication will be required at every attempt to connect to the device.

Note: this mechanism is by default enabled but the user can still disable it if required.

b. A default password is provided by the factory setting (available in the Keypad), however the user will be
requested at each authentication attempt, to define a different and secured password. It remains possible to keep the
default password temporarily, but the same reminder will pop up over again during next connection attempts.

c. The User authentication can be enabled/disabled, from the Security node (Parameters List tab) of the
considered fieldbus.

Note: For legacy option card (Modbus TCP/ PROFINET), User authentication will be deactivated since they
are not supported by these versions of cards

2. Support for new firmware version

a. V3.2IE43 ==> Support the User authentication for California Law compliance purposes.

3. Bug fixes.

4. Updated help and programming manuals

2.6 Features V1.3.3

 >CR Fixes.

2.7 Features V1.3.2

> Support for Firmware version V3.1IE38

> Feature : Displays IE version of the product

> CR : Import of ATV32 to ATV320 gives incorrect values for few parameters

> CR : Missing parameters during import of ATV32 to ATV320

> CR : Screen display resolution issues

> CR : Modify topology book-size to compact not working for ATV320U55N4

> CR : Drive unlocks after transfer through Multi Loader

> CR : Issue with conversion of few parameters value in German and French

> CR : ATV320 DTM does not follow the right address to connect

2.8 Features V1.2.6

>Support for Firmware Patch version V2.9IE37

>Features : Support for viewing bit wise details for Safety Fault Registers.

>GEDEC00254657 Bug 132601 : Export Multiloader.

>GEDEC00256852 Bug 144520 : Multi-configuration - drive trips in FCF1 or EEF1 fault.

>GEDEC00253930 Bug 127212 : Multi-configuration - drive trips in FCF1 or EEF1 fault.

>GEDEC00218907 Bug 54552 : SAFF at next PON after safety transfer GDL done.

>CR Fixes.

2.9 Features V1.2.4

>CR Fixes.

2.10 Features V1.2.3

>Support for IP66 drives.

>Device conversion from ATV31C to ATV320 IP66 supported drives.

>CR Fixes.

2.11 Features V1.1.9

>Firmware V2.9 support.

>Updated Help Manuals.

>CR Fixes.

2.12 Features V1.1.8

>Support for IP66 drives.

>Device conversion from ATV31C to ATV320 IP66 supported drives.

>CR Fixes.

2.13 Features V1.1.6

 > CyberSecurity Fixes

> CR Fixes

3 System Requirement

3.0 Minimum PC Requirements

Equipment Minimum

Processor Pentinum 4 / Core 2 Duo, 2 GHz

RAM 2 GB

Free Hard Disk Space 1 GB

Resolution: 1024 x 768 pixels.

Display
DPI: 96 (100%).

3.1 Recommended PC Requirements

Equipment Recommended

Processor Intel(R) Core(TM) i3

RAM 4 GB

Free Hard Disk Space 2 GB

Resolution:1920 x 1080 pixels.

Display
DPI: 96 (100%).

4 Container Supported

> SoMove V2.0 onwards (California CS Law compliance support from SoMove V2.8.4 onwards)

> EcoStruxure Machine Expert V2.2

> M&M FDT Container V4.8

> EcoStruxure Control Expert V15.3

5 IMPORTANT NOTICE

1. Device conversion will work only with SoMove (not supported for other FDT containers).

2. For the device conversion of ATV32 project file (*.psx) to ATV320 project, you need SoMove v2.8.1 version update.

6 Restrictions
 1. ATV logic sub menu in the device menu is disabled until the ATV logic tab is selected for the first time after the
launch of FDT container.

2. Connection lost issues are observed when the application is connected with the device for more than 30 minutes.

3. For ATV320 Solar family :

a. The partial factory reset will execute the factory reset for complete parameters on DTM and partial reset on the
device, to achieve the partial factory reset use the keypad only.

b. The Store to device operation from V3.6 FW to another solar FW version will result in CFI(Incorrect
configuration).

c. The Store to device operation to a V3.8 FW protected device with "Tranfer rights" as "Always" is not possible as it
results in connection lost.

7 Known Issues

1. DTM libraries cannot be installed on some computers due to access restriction of certain folder. => See
troubleshooting section 8.0

2. Store to device is not permitted when the ATV Logic is running in the connected device, a popup error indicates
«Store to device is not possible».

3. Command panel sometimes cannot be made inactive when the ADC parameter in automatic DC injection is
changed to continuous and executed a Run and stop.

4. ATVLogic: Execution order for Constant function blocks is not stored and retrieved back.

5. When device is locked with Level 2 password, password needs to be entered twice during connect in FDT
containers other than SoMove.

6. When the device is being connected from two instances of the DTM, upon the second connection attempt the first
connection is also lost.

7. In EcoStruxure Control Expert and EcoStruxure Machine Expert, the Return/ Tab/ Esc keys are not processed in
the Login, Change Password, Security panels and notification dial

8. EcoStruxure Machine Expert => PRM file transfer is failing

9. In EcoStruxure Control Expert, DTM will end up in connection lost while switching the multiconfiguration through
LI's

10. The help information for the Sensorless Flow Estimation feature is available only in English language.

11. Translation for new screens are not available in other languages.

12. Sensorless flow panel control values must be applied clicking on OK from the panel before performing Store to
device operation for the values to be applied to the device to avoid non-sync between the values in the DTM and the
Device.

8 Troubleshoot

1. Store to Device through MBTCP : When the Channel policy is Disabled in the drive, and Enabled in the DTM, first
attempt of the transfer would enable the channel policy and transfer is aborted, same operation needs to be
performed again The second attempt will pop up with the login dialog for the user to enter the proper credentials to
proceed with the transfer

2. Load from Device - If a load from device action is interrupted by a device power OFF, then the subsequent load
from device actions will fail. Resolution: * Power ON the device and try Load from device again, or if problem persists
still then * Restart SoMove and try Load from device again operating systems

3. Functional Block - In ATVLogic configuration dialog box, an error message warns “Date is integer”. Resolution: *
The date must be entered in the required format: 8 digits: MMDDYYYY

4. Functional Block - If you want copy / paste a whole program from the PRE to the AUX for example, we have the
following behavior: > Only blocks are pasted (no Inputs/outputs and no links will be pasted). > The paste operation
will not paste all blocks copied from the PRE section. It depends on the position of the last click in the window. >
Create link on 'paste blocks' is not always possible. In this case, it is necessary to delete blocks and create new one.
 5. Online help: Adobe version 10 and above, the user has to disable the Protected Mode at startup in the Adobe
Reader preference: In Adobe Reader X, go to Edit>Preferences>General and uncheck "Enable Protected Mode at
startup".

6. Connection lost occurs sometimes when using Ethernet option card

7. Before installing the new DTM version, ensure that SoMove is not running in your PC/system.

8.0 Modify Temp location:

> Press ‘Windows Key’ and ‘R Key’ together, It will open “Run Window”.

> Type “sysdm.cpl” in "Run Window", Click on “OK”

> Navigate to Advanced tab, Click on environment variables button.

> Edit the temp variable entry from "%USERPROFILE%\AppData\Local\Temp" to "C:\Temp".

If the issue still persists, please contact the support team.