EcoStruxure Control Expert V15 - Release Notes

Contents

1 What’s new in Control Expert V15 1

2.1 Table 1 Unity Pro Versions and PLC OS compatibility 9

2.2 Table 2: XEF and ZEF Files on PC 11

2.3 Table 3: STA Files on PC 17

2.4 Table 4: STU Files on PC 21

2.5 Table 5: PLC <=> PC Transfer 24

2.6 Table 6: Online modification 28

2.7 LL984 Libraries 32

2.8 DTM Version matrix 34

3 Important information 35

4 Additional information from previous releases 35

1 What’s new in Control Expert V15

New features coming with Control Expert V15 are:

· Topology Manager (available in 2^nd step : Control Expert V15.0 Service Pack 1)

o a new multi-controllers configuration environment to reduces engineering hours, commissioning and start-up time. An innovative client server architecture and central repository allow multiple users to work in parallel.

o Centralized Security Editor

· Communication Function Blocks: easy to configure and simulate PAC to PAC communication (M580 and M340)

· Improvements on DFB search

· Global Name Space

· Data Memory Protect: protect data against unwanted update (on M580 and M340)

· More data logged in Syslog

And Control Expert V15 supports Modicon range new features:

· MC80 is now by default in catalog

· BMXERT1604.2 can be used on M580 HSBY

· Monotonic time: In Safety communication, the NTP Time synchronization is improved.

· Support BMENUA V1.1

In synchronization with OFS V3.63:

· SCADA Access to variables within nested DFBs

· Display in SCADA of forced bits status (including EBOOL)

Note: firmware versions (3.20 for M580 / M580 Safety , and 3.3 for M340) and BMECRA modules is required to access new features Communication Function Blocks, Monotonic time In Safety communication and Data Memory Protect.

For details see attached pdf file (Adobe Acrobat Reader is necessary to open the file)

Hot Fixes listed below are implemented in Control Expert V15

ControlExpert_V141_HF_MC80

ControlExpert_V140_HF0567175R

ControlExpert_V141_HF_Multilanguages_Online_Help

ControlExpert_V141_HF0570819R

ControlExpert_V141_HF_Integrity_Check

ControlExpert_V141_BMENOR2200H

ControlExpert_V141_HF1

ControlExpert_V141_HF0583313R

ControlExpert_V141_HF0578777R

ControlExpert_V141_HF0586008

ControlExpert_V141_HF_EPE_Evolution1

ControlExpert_V140_HF0540480

ControlExpert_V141_HF0598509R

ControlExpert_V141_HF0608820R

ControlExpert_V141_HF0591961R

Enhancement listed below are implemented in Control Expert V15 :

Id #	Adaptation	Title	Description of the enhancement
PEP0534777R	Adaptation	DTM versions are not documented	A matrix for native Control Expert DTMs. Is now available in Control Expert Release Notes (see 2.8)
PEP0540775R	Adaptation	bad restore messages of located EBOOL variables	On Restore Data, the message BOX note is adapted to indicate that : Forcing status of EBOOL variables is not restored.
PEP0543486R	Adaptation	validation with 'VMware vSphere Hypervisor- ESXi'	Control Expert V15 is tested on VMware vSphere Hypervisor- ESXi.
PEP0566614R	Adaptation	Search Windows size not correct in German Language	in German language, the pop-up window size is now appropriate.
PEP0578391R	Adaptation	CIP Safety DTM update	In the DTM, the description of the path to access a CIP Safety Device was only using "Instance" name and not "Connection point" EDS syntax allow now the "Connection point"
PEP0541852R	Adaptation	Tech Support Diagnostic	Tech Support Diagnostic Wizard is improved in Topology Manager
PEP0533619R	Adaptation	Inspect Windows in ST for strings	“inspect windows” displays now the complete string for string type value in Structure Test (ST),
PEP0531707R	Adaptation	Data Memory Protect	Data Memory Protect feature.
PEP0498028R	Adaptation	BMEAHI BMEAHO CCOTF	It is possible to add/delete BME AHI/AHO modules in RUN in a rack (CCOTF). But DTM configuration (HART) cannot be updated.
PEP0432844R	Adaptation	BMXNOM0200 on ERIO	BMXNOM0200 Ch0, Master RS232; configuration is the same on main rack or ERIO

Issues listed below are fixed in Control Expert V15 :

Id #	Quality	Title	New behavior / solution
PEP0427129R	Quality	HART configuration does not transfer in FDR server.	on BMEH584060, HART modules configuration files are correctly transfered in FDR server.
PEP0493214R	Quality	Unity Pro DFB Template Signature	DFB Template signature remains consistent between projects after import of DFB Template
PEP0536726R	Quality	open .zef M580 on previous versions	on M580 project with a 140CRA31200 with SV equal or higher than 2.30, it is now possible try to open .zef file on previous versions of Unity Pro or Control Expert
PEP0537172R	Quality	M580 Master DTM Connection bit deletion and addition.	On M580 Master DTM , when many connection bits were added (Limit is 127 in total), and deleted , then the bit assignment may be out of 1-127 range When adding new connections, gaps are now filled correctly. NOTE : some projects done in previous versions may not build correctly : delete requests that are "out of range" and add it again so that valid connection bits (1-64) are reassigned.
PEP0538093R	Quality	NOC Time zone Offset Wrong Calculation	Unity in win10 performed a wrong calculation( display 0) of BMENOC Time zone Offset no matter what was put in Time Zone. This issue is now fixed
PEP0539808R	Quality	Restored 'ERRORID' value cannot be over written.	after Restore Data from file to PLC', the value in the 'ERRORID' register for the 'CAN_HANDLER' block could not be overwritten. This is now fixed.
PEP0541135R	Quality	BMENOC0301.4 configuration	on BMENOC0301.4: connection numbers and ID numbers are correct
PEP0542097R	Quality	BMEENOC321 looses its IP forwarding service on build All	after changing the IP forwarding setting changes itself enable -> disable, the IP addresses for fieldbus network are no more lost.
PEP0544933R	Quality	Control Expert stops working when click mouse on Ethernet Network windows	in "Ethernet Network" window, after single click mouse, behavior is now correct
PEP0546693R	Quality	M580 HSBY working as Standalone CPU : CCOTF not allowed	CCOTF is possible on a M580 HSBY controller, even if no Secondary CPU is used (so HSBY is used as a Standalone controller)
PEP0546976R	Quality	DFB export type always enabled in XVM	option "DFB type" is disabled in export to XVM, sa types are exported in any case
PEP0547179R	Quality	Sections print distorted when a .pdf is printed	print of sections improved
PEP0548563R	Quality	Function Block IS_PAR_CON reports wrong status	Function Block IS_PAR_CON reports right status
PEP0551621R	Quality	M580 DTM I/O scanner calculations causes Build error.	on project created with previous Control Expert versions, the M580 DTM bandwidth calculation is now correct.
PEP0553522R	Quality	CYB - Unity Pro PLC simulator - Buffer Overflow	for further information, please refers to CVE-2020-7475
PEP0556594R	Quality	Warning Popups windows with EIP device	a lot of Warning Popups windows appeared when adding EDS file with some unsupported data types ... show dialog with Error for each line of issue. This is now minimized with one single dialog box
PEP0558943R	Quality	STU file size increase after save.	STU file size does not increase any more after save.
PEP0559234R	Quality	IP address difference between Ethernet Network and DTM Browser	When BMENOC0301 was configured at Fieldbus Network of BMENOC0321, the IP Address displayed in Ethernet Network tool were not correct. This is now fixed
PEP0560974R	Quality	Error when adding Can Open EDS with Hardware Catalog Manager	No more error when adding Can Open EDS with Hardware Catalog Manager
PEP0561914R	Quality	An error is displayed when adding a new MFB axis in M580 Safety	Error is no more displayed when adding a new MFB axis in M580 Safety (Process part)
PEP0567142R	Quality	M580S go to SAFE HALT when link on S_SEL is used	Problem : In Safety mode, SAFE HALT is displayed in Control Expert when a direct link is used between S_SEL Function Block and another Function Block . This issue is now fixed
PEP0567143R	Quality	Checking extra Can Open PDO, configuration causes binary error at build	Checking extra Can Open PDO, configuration does not any more cause binary error at build
PEP0567943R	Quality	rename "maintenance Input" in Safety CPU Config screen	The Safety CPU configuration screen is updated: "Maintenance input" is replaced by "Maintenance authorization"
PEP0571606R	Quality	Description in German not complete in BMENOC03x1 config screen	Description in German in BMENOC03x1 config screen is updated.
PEP0571898R	Quality	Concept Converter: type INT is converted to ZONE with array of 4 INT.	Concept Converter: type INT was converted to ZONE with array of 4 INT, when multiple variables were assigned to same address. This is now fixed.
PEP0572105R	Quality	L9_SUB UINT data type behaves as INT	L9_SUB function did not behave correctly according the defined types in the block. All the parameters in the block defined as UINTS but the operation behaved as if they were INT. This is now fixed
PEP0573324R	Quality	Fail gcc compilation error	"fail gcc compilation" after Rebuild All does not occur any more in above conditions.
PEP0573422R	Quality	Problem when Cyrillic characters in name or folder name.	error when opening a CE file including Cyrillic characters or open a CE file without Cyrillic characters but from a folder name which includes Cyrillic characters. This error is now fixed.
PEP0573497R	Quality	Missing T850_to_T870 and T870_to_T850 EF safety	when selecting a Safety processor, the EF T850_to_T870 and T870_to_T850 are now available.
PEP0573929R	Quality	Increase the size of refine dialog box	Refine on DFB Instance dialog box : long names were not fully visible, user had to scroll to the right to read displayed names. The Dialog box size is now increased
PEP0573940R	Quality	Data search drop down list Scope truncates names	On data search on "project scope", in the drop down list showing the scope, names are now visible.
PEP0574067R	Quality	Initial value save on application closure.	After setting %S94 and so "update initial value with the current values" inside the PLC if the application were closed, then a window opens: customer can then save his application and “Update local init value with PLC init value”. This last option is now working, and the local init value are correctly updated.
PEP0575706R	Quality	CYB - Adaptation of the Integrity Check	for further information, please refers to CVE-2020-7475
PEP0575805R	Quality	Copy/Paste from digital IO configuration window does not work.	Copy/Paste from digital IO configuration window is correct
PEP0576007R	Quality	M580 Safety : Process variables export file empty	Filtered variable could only be exported once, doing a second filter would export a blank .xsy. This is now fixed
PEP0576129R	Quality	Third party DTM instantiation issue under BMEAHI	under a BMEAHI/BMEAHO , when adding a device an error message appeared “"this version of control Expert does not support DTM devices". This error is now fixed (note: it was fixed in V14.1 by hot fix CONTROLEXPERT_V141_HF0608820R)
PEP0576134R	Quality	No "Replace" option" in the Program Unit 'Import Trouble Report' window	When importing a Program Unit that conflict with an existing Program Unit ( same name), a "replace" option is now available
PEP0576165R	Quality	module compatibility issue on ProWORX project	Message "AS-H827-103 is not compatible with Drop " is now fixed
PEP0577416R	Quality	Changing SFC block name stops Control Expert	In an SFC section, renaming an Instance of a block, inside an Action, to the Action name is now possible.
PEP0577417R	Quality	Process Forced Bit table does not show symbol name.	On M580 Safety controller, if a process variable were forced and the forced table called up, it brought up the %Mxxx address : Now, it brings up the Name in the Name Column and the Address in the address Column.
PEP0578784R	Quality	Time Stamping ID lost in project	In a M580 Safety application TS ID were lost on STU, STA, ZEF. This is now fixed.
PEP0579494R	Quality	Device list description in M580 DTMs is incorrect	in M580 DTM, the description of Device List is now correct.
PEP0579729R	Quality	Adding a profile in private family does not work for BMXEIA0100	In BMXEIA0100 configuration screen, a new profile in the Private family can now be added
PEP0580247R	Quality	BMXEIA0100 configuration issue	private family in Chinese language text is now correct.
PEP0580408R	Quality	Overview 140CRA31210	Indication "400Word in /out" was misleading as size is limited by 1400 bytes in /out of ethernet buffer. Overview is now updated.
PEP0581511R	Quality	CE v14.1 - Error to add a Profibus Slave	The following issue is fixed : On M580, after add a PRM gateway in DTM browser, and add a GSD file to library, and Update catalog. Then, in DTM browser, add the device created from GSD under the PRM gateway: an error message appears “"this version of control Expert does not support DTM devices". (note: it was fixed in V14.1 by hot fix CONTROLEXPERT_V141_HF0608820R)
PEP0582379R	Quality	M340, IOStructure Name Error with BMXNOC0401	After adding the DTM device under BMXNOC0401.2 changing the "IO Structure NAME" is now possible.
PEP0582801R	Quality	Windows folder which contains Chinese characters	Stu/Sta projects stored in folder named with Chinese characters, can now be open without error.
PEP0584471R	Quality	RESTORE DATA from Premium to M580 error	DTX file created by SAVE_DATA from Premium project can be RESTORE_DATE to M580 project.
PEP0587180R	Quality	Text error on Spanish version	“Types Library Manager” screens updated
PEP0587223R	Quality	Multime ENO abnormal behavior	ENO of Multime Function Block was stack at "0" even if EN was set to 1. This is now fixed.
PEP0587762R	Quality	thread tried to read from or write to …	On project using EXTERNAL Variables inside Program Units and message appeared: "The thread tried to read from or write to a virtual address for which it does not have the appropriate access". This issue is now fixed.
PEP0588566R	Quality	wrong grammar in warning message	message " this variable doesn't longer exist" is corrected.
PEP0589681R	Quality	Hot fixes do not completely uninstall	Hot fixes are uninstalled when Control Expert is uninstalled
PEP0589803R	Quality	Unity DIF shows different results for REAL in .zef and .sta	REAL variable value appears as 400 (for example) in ZEF but value will be 400.0 (floating point) in sta and Unity DIF will show a difference between the two applications. Value appears now as 400,0 in both.
PEP0590044R	Quality	Right click on DFB & initialize search return nothing	Search on DFB type is now done on All scope of project, so all instances are found (in DFBs, nested, in Program Units..)
PEP0591961R	Quality	invalid assignment using LENGTH_ARSTRING	issue with LENGTH_ARSTRING function is now fixed
PEP0592027R	Quality	BMXDRA0815 3.3V power budget	BMXDRA0815 3.3V power budget is corrected
PEP0592805R	Quality	RIO / CRA can build with all the PLC security enabled	in14.1 project with remote rack I/O could build with all the PLC security enabled. But this is wrong. It is now highlighted that TFTP, EIP, and DHCP/BOOTP must be enabled
PEP0596346R	Quality	Search function Scope Global default doesn't work	Search on DFB type is now done on all scope of project
PEP0598891R	Quality	CANopen size error at build when changing Premium CPU reference	Changing CPU, with TSXCPP110 , and rebuild all, may cause an error on CANopen channel: {Channel (0.0.1 ) CANopen} : Error in definition of configuration size This error is now fixed
PEP0599967R	Quality	CE 14.1 Implicit Type Conversion	in Mathematics operations literal value conversion is now correctly managed
PEP0600506R	Quality	SEARCH in Program Unit : variable used in another Program Unit cannot be found	Search is now done on all scope of project, so all instances are found (in DFBs, or in Program Units)
PEP0603047R	Quality	changing LID/DID cause an error on BMENUA (message: BadWaitingForInitialData)	BME NUA module connection to an OPC client application is now OK , without error message BadWaitingForInitialData, after online changes.
PEP0608820R	Quality	CE V14.1 Import of provided XSY file generates an error at analyze	The following issue is fixed: When importing XSY file, with variables and Function Block instances already existing in the project, then during import a “Replace” is proposed on these variables and FB instances. In some cases, when “replace” option is selected for both variables and FB instances, the FBD section using the instance and variables may be in error. (note: it was fixed in V14.1 by hot fix CONTROLEXPERT_V141_HF0608820R)
/	Quality	New Modbus driver	for further information, please refers to CVE-2020-7523
PEP0609251R	Quality	REF TO BOOL issue	The following issue is fixed: REF TO BOOL is reset when used on a Reset Coil
PEP0593950R	Quality	Arrays conversion from CONCEPT	The following issue is fixed: Arrays on project converted from CONCEPT are offset by 2 registers
PEP0584212R	Quality	GET_TS_EVT_M error & status	GET_TS_EVT_M error & status are now correct (to 0) and no more to 1
PEP0574773R	Quality	Access Rights Overridden by MDT Autosave	The following issue is fixed: Some Control Expert access Rights (set in Security Editor) were overridden by MDT Autosave.
PEP0572624R	Quality	DDDT name under NOC401 & 402	Device DDT created from Modbus DTM added under NOC0402, or NOC0401, can now be renamed correctly.
PEP0546596R	Quality	BMENOC0321 Ethernet Network screen	On BMENOC0321, the configuration screen for Sub-network mask of IP Forwarding is now consistent with what is displayed in Ethernet Network tool
PEP0578777R	Quality	Open STA file with several BMECXM0100 (so several CANopen buses).	ControlExpert_V141_HF0578777R The following issue is fixed: It is not possible to open a STA file when there are several BMECXM0100 (so several CANopen buses). The problem is reproducible when we have 2 different devices at same address on different CANopen buses. The “open STA” command fails without any explanation

2 Compatibility rules

2.1 Table 1 Unity Pro Versions and PLC OS compatibility

This table gives the application version created with the different Unity Pro versions.

Application version corresponds to the processor OS version displayed in Unity Pro configuration screen.

The OS version corresponds to the minimum version required to execute an application functional level.

Higher OS versions ensure compatibility with a lower application version.

As example: an application version V2.00 generated by Unity Pro V3.0 can be executed by a PLC OS version V2.30.

Control Expert / Unity Pro Version	PREMIUM Minimum OS Version	QUANTUM Minimum OS Version	QUANTUM SAFETY Minimum OS Version	Momentum Minimum OS Version	M340 Minimum OS Version	M580 Minimum OS Version	M580 SAFETY Minimum OS Version
V15	/	/	NA	/	3.3	3.2	3.2
V14.1	/	/	NA	/	3.2	3.1	3.1
V14	/	/	NA	/	/	2.9(***) 2.8	2.9(***) 2.8
V13.1	/	/	NA	/	/	2.7	2.7
V13	/	/	NA	2.0	/	2.4	2.4 (**)
V12	/	/	NA	/	/	2.3	NA
V11.1	/	/	NA	1.3	/	2.2	NA
V11	/	/	NA	/	/	2.1	NA
V10	/	3.3 (*)	NA	/	2.7	2.0	NA
V8.1	3.10	3.2x (*)	NA	/	2.60	1.1x	NA
V8.0	/	3.20	NA	1.0	/	1.0	NA
V7.0	3.0	3.10	3.0	NA	2.50	NA	NA
V6.1	/	/	NA	NA	2.40	NA	NA
V6.0	2.90	3.00	NA	NA	2.30	NA	NA
V5.0	2.60 / 2.70 (2)	2.80	NA	NA	2.20	NA	NA
V4.1	2.60 / 2.50 (2)	2.70	2.0	NA	2.10	NA	NA
V4.0	2.60 / 2.50 (2)	2.60	NA	NA	2.00	NA	NA
V3.1	2.50 (2)	2.40	1.0	NA	1.00	NA	NA
V3.0	2.40	2.40	NA	NA	1.00	NA	NA
V2.3SP1	2.30	2.30	NA	NA	NA	NA	NA
V2.2	2.21 (1)	2.00	NA	NA	NA	NA	NA
V2.1	2.00 MFB	2.00	NA	NA	NA	NA	NA
V2.0	2.00	2.00	NA	NA	NA	NA	NA

(1)      Only TSX P 57 5634 M.
(2)      Only TSX H57 24 M and TSX H57 44 M
NA     Not Applicable: Applications not supported.

/ No evolution

(*) Quantum minimum OS version for Unity Pro V8.1 is 3.20 (standalone) or 3.21 (Hot Stand By CPUs)

Quantum minimum OS version for Unity Pro V10 is 3.3 (high end CPUs 140CPU6xx) or 3.20 (others)

(**) OS version 2.6 with UnityPro_V130_HF2

(***) M580 Version 2.9 support comes with CONTROLEXPERT_V140_HF_PMEPXM0100_HF0312169E or CONTROLEXPERT_V140_HF2

2.2 Table 2: XEF and ZEF Files on PC

Open XEF Files

With
Unity Pro V2.3 SP1

With
Unity Pro V3.0

With
Unity Pro V3.1

With
Unity Pro V4.0

With
Unity Pro V4.1

With
Unity Pro V5.0

With
Unity Pro V6.0 (1)

With
Unity Pro V6.1 (2)

With
Unity Pro V7.0 (3)

With
Unity Pro V8.0 (4)

With
Unity Pro V8.1 (4)

With
Unity Pro V10 (4)

With
Unity Pro V11 (4)

With
Unity Pro V11.1 (4)

With
Unity Pro V12 (4)

With
Unity Pro V13 (4)

With
Unity Pro V13.1 (4)

With
Control Expert V14

(4)

With
Control Expert V14.1

(4)

With
Control Expert V15

(4) (6)

Modicon M580 Safety application

NA (5)

Modicon M580application

NA (5)

Momentum Unity

V1.0 application

YES

Momentum Unity

V1.3 application

YES

Momentum Unity

V2.0 application

YES

Premium / Quantum
V2.00 application *

YES

Premium / Quantum
V2.30 application

YES

Premium / Quantum
V2.40 application

YES

Premium
V2.50 application

YES

Premium / Quantum
V2.60 application

YES

Premium / Quantum
V2.70 application

YES

Premium
V3.00 application

YES

Premium
V3.10 application

YES

Quantum
V2.80 application

YES

Quantum
V3.00 application

YES

Quantum
V3.10 application

YES

Quantum
V3.2x application

YES

Quantum
V3.3 application

YES

Modicon M340
V1.0 application

YES

Modicon M340
V2.0 application

YES

Modicon M340
V2.1 application

YES

Modicon M340
V2.2 application

YES

Modicon M340
V2.3 application

YES

Modicon M340
V2.4 application

YES

Modicon M340
V2.50 application

YES

Modicon M340
V2.60 application

YES

Modicon M340
V2.7 application

YES

Modicon M340
V3.2 application

YES

Modicon M340
V3.3 application

YES

Quantum safety
V1.0 application

YES

Quantum safety
V2.0 application

YES

Quantum safety
V3 .0 application

YES

NA: Not Applicable (Quantum Safety only exists for Unity Pro V3.1, V4.1 & V7.0)

Ø Application version corresponds to the choice of PLC version in Unity Pro configuration screen (V2.00, V2.30 …)

See Unity Pro, application and PLC OS compatibility (Table 1).

Restrictions:

(1) When XEF file created with Unity Pro ≥ V6.0 contains LL984 sections, XEF file cannot be open by Unity Pro version < V6.0

(2) When XEF file created with Unity Pro ≥ V6.1 for the M340 platforms contains LL984 sections, XEF file cannot be open by Unity Pro version < V6.1

(3) When XEF file created with Unity Pro V7.0 contains Extracted bits in DDT, XEF file cannot be open by Unity Pro version < V7.0

(4) Downward compatibility of DTM's is not guaranteed : so If an application created with Unity Pro contains DTMs version n, it may not be opened and run with DTMs version n-1 (or prior) : Status is displayed in DTM Audit Tool.

Upward compatibility of DTMs is guaranteed : If an application created with Unity Pro contains DTMs version n, it can be opened and run with DTMs version n+1 and above.

(5) XEF format is not available on M580 platform (zef format only is available for M580 platform).

(6) XEF import format is only supported by Control Expert Classic. It is not supported by Control Expert Topology Manager

Open ZEF Files

With
Unity Pro ≤ V5.0

With
Unity Pro V6.0 (1)

With
Unity Pro V6.1 (2)

With
Unity Pro V7.0 (3)

With
Unity Pro V8.0 (4)

With
Unity Pro V8.1 (4)

With
Unity Pro V10 (4)

With
Unity Pro V11 (4)

With
Unity Pro V11.1 (4)

With
Unity Pro V12

(4)

With
Unity Pro V13

(4)

With
Unity Pro V13.1

(4)

With
Control Expert V14

(4)

With
Control Expert V14.1

(4)

With
Control Expert V15

(4) (5)

Modicon M580 safety

V2.4 or 2.6 application

YES

Modicon M580 safety

V2.7 application

YES

Modicon M580 safety

V2.9 & V2.8 application

YES

Modicon M580 safety

V3.1 application

YES

Modicon M580 safety

V3.2 application

YES

Modicon M580

V1.0 application

YES

Modicon M580

V1.1x application

YES

Modicon M580

V2.0 application

YES

Modicon M580

V2.1 application

YES

Modicon M580

V2.2 application

YES

Modicon M580

V2.3 application

YES

Modicon M580

V2.4 application

YES

Modicon M580

V2.7 application

YES

Modicon M580

V2.9 & V2.8 application

YES

Modicon M580

V3.1 application

YES

Modicon M580

V3.2 application

YES

Momentum Unity

V1.0 application

YES

Momentum Unity

V1.3 application

YES

Momentum Unity

V2.0 application

YES

Premium / Quantum
≤ V2.70 application *

YES

Premium
V3.0 application

YES

Premium
V3.10 application

YES

Quantum
≤ V3.00 application

YES

Quantum
V3.10 application

YES

Quantum
V3.2x application

YES

Quantum
V3.3 application

YES

Modicon M340
≤ V2.3 application

YES

Modicon M340
V2.4 application

YES

Modicon M340
V2.50 application

YES

Modicon M340
V2.60 application

YES

Modicon M340
V2.7 application

YES

Modicon M340
V3.2 application

YES

Modicon M340
V3.3 application

YES

Quantum safety
≤ V3 .0 application

YES

NA: Not Applicable

Ø Application version corresponds to the choice of PLC version in Unity Pro configuration screen (V2.00, V2.30 …)

See Unity Pro, application and PLC OS compatibility (Table 1).

Restrictions:

(1) When ZEF file created with Unity Pro ≥ V6.0 contains LL984 sections, ZEF file cannot be open by Unity Pro version < V6.0

(2) When ZEF file created with Unity Pro ≥ V6.1 for the M340 platforms contains LL984 sections, ZEF file cannot be open by Unity Pro version < V6.1

(3) When ZEF file created with Unity Pro V7.0 contains Extracted bits in DDT, ZEF file cannot be open by Unity Pro version < V7.0

Upward compatibility of DTMs is guaranteed : If an application created with Unity Pro contains DTMs version n, it can be opened and run with DTMs version n+1 and above.

(5) Control Expert Topology Manager supports ZEF import from V15. To import ZEF from previous versions : import ZEF in Control Expert Classic >> Export ZEF >> import new ZEF in Control Expert Topology Manager

2.3 Table 3: STA Files on PC

Open STA Files on PC

With
Unity Pro V2.3 SP1

With
Unity Pro V3.0

With
Unity Pro V3.1

With
Unity Pro V4.0

With
Unity Pro V4.1

With
Unity Pro V5.0

With
Unity Pro V6.0 (1)

With
Unity Pro V6.1

With
Unity Pro V7.0 (3)

With
Unity Pro V8.0

(4)

With
Unity Pro V8.1

(4) (5)

With
Unity Pro V10

(4) (5)

With
Unity Pro V11

(4) (5)

With
Unity Pro V11.1

(4) (5)

With
Unity Pro V12

(4) (5)

With
Unity Pro V13

(4) (5)

With
Unity Pro V13.1

(4) (5)

With
Control Expert V14

(4) (5)

With
Control Expert V14.1

(4) (5)

With
Control Expert V15

(4) (5) (6)

Modicon M580 safety

V2.4 or 2.6 application

YES

Modicon M580 Safety

V2.7 application

YES

Modicon M580 Safety

V2.9 & V2.8 application

YES

Modicon M580 Safety

V3.1 application

YES

Modicon M580 Safety

V3.2 application

YES

Modicon M580

V1.0 application

YES

Modicon M580

V1.1x application

YES

Modicon M580

V2.0 application

YES

Modicon M580

V2.1 application

YES

Modicon M580

V2.2 application

YES

Modicon M580

V2.3 application

YES

Modicon M580

V2.4 application

YES

Modicon M580

V2.7 application

YES

Modicon M580

V2.9 & V2.8 application

YES

Modicon M580

V3.1 application

YES

Modicon M580

V3.2 application

YES

Momentum Unity

V1.0 application

YES

Momentum Unity

V1.3 application

YES

Momentum Unity

V2.0 application

YES

Premium / Quantum
V2.00 application

YES (2)

YES

Premium / Quantum
V2.30 application

YES

Premium / Quantum
V2.40 application

YES

Premium
V2.50 application

YES

Premium / Quantum
V2.60 application

YES

Premium / Quantum
V2.70 application

YES

Premium
V3.00 application

YES

Premium
V3.10 application

YES

Quantum
V2.80 application

YES

Quantum
V3.00 application

YES

Quantum
V3.10 application

YES

Quantum
V3.2x application

YES

Quantum
V3.3 application

YES

Modicon M340
V1.0 application

YES

Modicon M340
V2.0 application

YES

Modicon M340
V2.1 application

YES

Modicon M340
V2.2 application

YES

Modicon M340
V2.3 application

YES

Modicon M340
V2.50 application

YES

Modicon M340
V2.60 application

YES

Modicon M340
V2.7 application

YES

Modicon M340
V3.2 application

YES

Modicon M340
V3.3 application

YES

Quantum safety
V1.0 application

YES

Quantum safety
V2.0 application

YES

Quantum safety
V3 .0 application

YES

NA: Not Applicable (Quantum Safety only exists for Unity Pro V3.1, V4.1 & V7.0)

Example: An application level V2.4, developed with Unity Pro V3.0, can be opened through the STA file with Unity Pro version V5.0.

Note: To allow online modification without constraint of the application, Unity Pro keeps the functions library version that has been used for the application creation.

In the example, the library version V3.0 will be retained when opening the project in Unity Pro V5.0

Restrictions:
(1) When STA file created with Unity Pro ≥ V5.1 contains LL984 sections application cannot be open by Unity Pro version < V5.1
(2) STA file cannot be opened, when application contains writings on read-only variables. Corrections must be made then recreate the archive file STA

(3) When STA file created with Unity Pro V7.0 contains Extracted bits in DDT, application cannot be open by Unity Pro version < V7.0
When STA file created with Unity Pro V5.1, 6.0 or 6.1 contains LL984 sections : refer to chapter 2.7

Upward compatibility of DTMs is guaranteed : If an application created with Unity Pro contains DTMs version n, it can be opened and run with DTMs version n+1 and above.

(5) Because of format changes in the Device DDT types, a ≥ V8.1 STA file containing one of the following DDDT cannot be open with Unity V8.0 . ZEF or XEF file can be open successfully

T_M_COM_ASI, T_M_COM_NOM,

T_M_CPT_STD_IN_2, T_M_CPT_STD_IN_8

T_M_DIS_ERT

T_M_SSI_3

T_U_ANA_STD_IN_4, T_U_ANA_STD_IN_4_OUT_2, T_U_ANA_STD_IN_8, T_U_ANA_STD_OUT_2, T_U_ANA_STD_OUT_4, T_U_ANA_STD_OUT_8, T_U_ANA_TEMP_IN_4

T_U_ANA_TEMP_IN_8, T_U_DIS_STD_IN_16, T_U_DIS_STD_IN_16_OUT_16, T_U_DIS_STD_IN_32, T_U_DIS_STD_IN_64, T_U_DIS_STD_IN_8,

T_U_DIS_STD_IN_8_OUT_8, T_U_DIS_STD_OUT_16, T_U_DIS_STD_OUT_32, T_U_DIS_STD_OUT_64, T_U_DIS_STD_OUT_8

(6) STA import format is only supported by Control Expert Classic. It is not supported by Control Expert Topology Manager

(7) Because of format changes in the Device DDT types, a V8.1 (or superior) STA file containing one of the following DDDT cannot be open with Unity V8.0 (ZEF or XEF file can be open successfully)

T_M_COM_ASI, T_M_COM_NOM,

T_M_CPT_STD_IN_2, T_M_CPT_STD_IN_8

T_M_DIS_ERT

T_M_SSI_3

T_U_ANA_STD_IN_4, T_U_ANA_STD_IN_4_OUT_2, T_U_ANA_STD_IN_8, T_U_ANA_STD_OUT_2, T_U_ANA_STD_OUT_4, T_U_ANA_STD_OUT_8, T_U_ANA_TEMP_IN_4

T_U_ANA_TEMP_IN_8, T_U_DIS_STD_IN_16, T_U_DIS_STD_IN_16_OUT_16, T_U_DIS_STD_IN_32, T_U_DIS_STD_IN_64, T_U_DIS_STD_IN_8,

T_U_DIS_STD_IN_8_OUT_8, T_U_DIS_STD_OUT_16, T_U_DIS_STD_OUT_32, T_U_DIS_STD_OUT_64, T_U_DIS_STD_OUT_8

2.4 Table 4: STU Files on PC

Restrictions:
Downward compatibility of DTM's is not guaranteed : so If an application created with Unity Pro contains DTMs version n, it may not be opened and run with DTMs version n-1 (or prior) : Status is displayed in DTM Audit Tool.

Upward compatibility of DTMs is guaranteed : If an application created with Unity Pro contains DTMs version n, it can be opened and run with DTMs version n+1 and above.

Open STU Files on PC

With
Unity Pro V2.3 SP1

With
Unity Pro V3.0

With
Unity Pro V3.1

With
Unity Pro V4.0

With
Unity Pro V4.1

With
Unity Pro V5.0

With
Unity Pro V6.0

With
Unity Pro V6.1

With
Unity Pro V7.0

With
Unity Pro V8.0

With
Unity Pro V8.1

With
Unity Pro V10

With
Unity Pro V11

With
Unity Pro V11.1

With
Unity Pro V12

With
Unity Pro V13

With
Unity Pro V13.1

With
Control Expert V14

With
Control Expert V14.1

With
Control Expert V15

(1)

Application generated with
Unity Pro V2.3 SP1

YES

Application generated with
Unity Pro V3.0

YES

Application generated with
Unity Pro V3.1

YES

Application generated with
Unity Pro V4.0

YES

Application generated with
Unity Pro V4.1

YES

Application generated with
Unity Pro V5.0

YES

Application generated with
Unity Pro V6.0

YES

Application generated with
Unity Pro V6.1

YES

Application generated with
Unity Pro V7.0

YES

Application generated with
Unity Pro V8.0

YES

Application generated with
Unity Pro V8.1

YES

Application generated with
Unity Pro V10

YES

Application generated with
Unity Pro V11

YES

Application generated with
Unity Pro V11.1

YES

Application generated with
Unity Pro V12

YES

Application generated with
Unity Pro V13

YES

Application generated with
Unity Pro V13.1

YES

Application generated with
Control Expert V14

YES

Application generated with
Control Expert V14.1

YES

Application generated with
Control Expert V15 (1)

YES

(1) STU import format is only supported by Control Expert Classic. It is not supported by Control Expert Topology Manager

2.5 Table 5: PLC <=> PC Transfer

PLC <=> PC
Transfer

With
Unity Pro V2.3 SP1

With
Unity Pro V3.0

With
Unity Pro V3.1

With
Unity Pro V4.0

With
Unity Pro V4.1

With
Unity Pro V5.0

With
Unity Pro V6.0 (1)

With
Unity Pro V6.1 (2)

With
Unity Pro V7.0

With
Unity Pro V8.0

With
Unity Pro V8.1

With
Unity Pro V10

With
Unity Pro V11

With
Unity Pro V11.1

With
Unity Pro V12

With
Unity Pro V13

With
Unity Pro V13.1

With
Control Expert V14

With
Control Expert V14.1

With
Control Expert V15

Modicon M580 safety

V2.4 or 2.6 application

YES

Modicon M580 Safety

V2.7 application

YES

Modicon M580 Safety

V2.9 & V2.8 application

YES

Modicon M580 Safety

V3.1 application

YES

Modicon M580 Safety

V3.2 application

YES

Modicon M580

V1.0 application

YES

Modicon M580

V1.1x application

YES

Modicon M580

V2.0 application

YES

Modicon M580

V2.1 application

YES

Modicon M580

V2.2 application

YES

Modicon M580

V2.3 application

YES

Modicon M580

V2.4 application

YES

Modicon M580

V2.7 application

YES

Modicon M580

V2.9 & V2.8 application

YES

Modicon M580

V3.1 application

YES

Modicon M580

V3.2 application

YES

Momentum Unity

V1.0 application

YES

Momentum Unity

V1.3 application

YES

Momentum Unity

V2.0 application

YES

Premium / Quantum
V2.00 application

YES

Premium / Quantum
V2.30 application

YES

Premium / Quantum
V2.40 application

YES

Premium
V2.50 application

YES

Premium / Quantum
V2.60 application

YES

Premium / Quantum
V2.70 application

YES

Premium
V3.00 application

YES

Premium
V3.10 application

YES

Quantum
V2.80 application

YES

Quantum
V3.00 application

YES

Quantum
V3.10 application

YES

Quantum
V3.2x application

YES

Quantum
V3.3 application

YES

Modicon M340
V1.0 application

YES

Modicon M340
V2.0 application

YES

Modicon M340
V2.1 application

YES

Modicon M340
V2.2 application

YES

Modicon M340
V2.3 application

YES

Modicon M340
V2.4 application

YES

Modicon M340
V2.50 application

YES

Modicon M340
V2.60 application

YES

Modicon M340
V2.7 application

YES

Modicon M340
V3.2 application

YES

Modicon M340
V3.3 application

YES

Quantum safety
V1.0 application

YES

Quantum safety
V2.0 application

YES

Quantum safety
V3.0 application

YES

NA: Not Applicable (Quantum Safety only exists for Unity Pro V3.1, V4.1 & V7.0)

Restrictions:
(1) When application created with Unity Pro ≥ V6.0 contains LL984 sections, application cannot be transferred with Unity Pro version < V6.0

(2) When application created with Unity Pro ≥ V6.1 contains LL984 sections for the M340 platforms, application cannot be transferred with Unity Pro version < V6.1

Upload from controller to PC (System Project) is not supported by Control Expert Topology Manager.

Upload must be done in 3 steps:

1. Upload from controller with Control Expert Classic

2. Export as ZEF

3. Import new ZEF in Topology Manager

2.6 Table 6: Online modification

Online modification

With
Unity Pro V2.3SP1

With Unity Pro V3.0

With Unity Pro V3.1

With Unity Pro V4.0

With
Unity Pro V4.1

With Unity Pro V5.0

With
Unity Pro V6.0 (1)

With
Unity Pro V6.1

With
Unity Pro V7.0

With
Unity Pro V8.0 (4)

With
Unity Pro V8.1 (4)

With
Unity Pro V10 (4)

With
Unity Pro V11 (4)

With
Unity Pro V11.1 (4)

With
Unity Pro V12 (4)

With
Unity Pro V13 (4)

With
Unity Pro V13.1 (4)

With
Unity Pro V14 (4)

With
Unity Pro V14.1

(4)

With
Unity Pro V15

(4)

Modicon M580 safety

V2.4 or 2.6 application

YES

Modicon M580 Safety

V2.7 application

YES

Modicon M580 Safety

V2.9 & V2.8 application

YES

Modicon M580 Safety

V3.1 application

YES

Modicon M580 Safety

V3.2 application

YES

Modicon M580

V1.0 application

YES

Modicon M580

V1.1x application

YES

Modicon M580

V2.0 application

YES

Modicon M580

V2.1 application

YES

Modicon M580

V2.2 application

YES

Modicon M580

V2.3 application

YES

Modicon M580

V2.4 application

YES

Modicon M580

V2.7 application

YES

Modicon M580

V2.9 & V2.8 application

YES

Modicon M580

V3.1 application

YES

Modicon M580

V3.2 application

YES

Momentum Unity

V1.0 application

YES

Momentum Unity

V1.3 application

YES

Momentum Unity

V2.0 application

YES

Premium / Quantum
V2.00 application

YES (2)

YES (3)

YES

Premium / Quantum
V2.30 application

YES

YES (2)

YES

Premium / Quantum
V2.40 application

YES

YES (2)

YES

Premium
V2.50 application

YES

Premium / Quantum
V2.60 application

YES

Premium / Quantum
V2.70 application

YES

Premium
V3.00 application

YES

Premium
V3.10 application

YES

Quantum
V2.80 application

YES

Quantum
V3.00 application

YES

Quantum
V3.10 application

YES

Quantum
V3.2x application

YES

Quantum
V3.3 application

YES

Modicon M340
V1.0 application

YES

Modicon M340
V2.0 application

YES

Modicon M340
V2.1 application

YES

Modicon M340
V2.2 application

YES

Modicon M340
V2.3 application

YES

Modicon M340
V2.4 application

YES

Modicon M340
V2.50 application

YES

Modicon M340
V2.60 application

YES

Modicon M340
V2.7 application

YES

Modicon M340
V3.2 application

YES

Modicon M340
V3.3 application

YES

Quantum safety
V1.0 application

YES

Quantum safety
V2.0 application

YES

Quantum safety
V3.0 application

YES

NA:       Not Applicable (Quantum Safety only exists for Unity Pro V3.1, V4.1 & V7.0)

Restrictions:
(1)        When application created with Unity Pro V6.0 contains LL984 sections, application cannot be modified with Unity Pro version < V6.0
(2)        Adding a new EFB Type needs to update the library in the project (rebuild all)
(3)        Automatic management of libraries, occurred with Unity Pro version V4.0, manages all function libraries of previous versions up to version V2.2.
            Applications created with versions V2.0 and V2.1 require to update the library function in V2.2 minimum to ensure adding of new type of EFB online

Upward compatibility of DTMs is guaranteed : If an application created with Unity Pro contains DTMs version n, it can be opened and run with DTMs version n+1 and above.

2.7 LL984 Libraries

There are 2 different LL984 libraries:

LL984 (EFs named LL_xxxx), this library was used before Unity Pro V5.1 and not delivered with Unity Pro. It was used only to convert Modsoft and ProWORX projects and Concept LL984 sections to Unity Pro.

Latest version of LL984 library : V4.1.17, is available from Schneider Electric Services only (Please contact your local Schneider Electric correspondent to receive a copy of this library).

UnityLL984 (EFs named L9E_xxxx), is used since Unity Pro V5.1

Opening an application (sta file) done with V5.1, V6.0, or v6.1 and that contains LL984

Unity LL984 libraries were not installed with Unity Pro prior to v7.0 (ie in versions V5.1, V6.0, or v6.1) and had to be installed separately.

So, Unity LL984 libraries corresponding to those versions (V5.1, V6.0, or v6.1) are not installed with Control Expert V15

If user wants to open an application (sta file) done with V5.1, V6.0, or v6.1 and that contains LL984 sections, he has 2 possibilities :

· Use the last version of the Unity LL984 library

o Select " Update with latest version available" in the "Libset Version" part of the opening windows.

o A Rebuild All of the application is then necessary

o The latest (ie 11.1) version of LL984 library is used.

· Keep the previous Unity LL984 library version :

o User must first install the Unity LL984 library corresponding to the version used (V5.1, V6.0, or v6.1)

§ Legacy Unity Pro LL984 libraries are available on schneider-electric.com

o Select " Keep project version" in the "Libset Version " part of the opening windows.

o No Rebuild All is necessary

(*) Previous versions of Unity LL984 Libraries (V6.0, or v6.1) are available in Control Expert DVD

Folder : “Previous Unity LL984 Library”

Containing the LL984 library zipped file.
For installing, Unzip, Setup_UnityLL984Library_Vxxx.zip file in a hard drive directory and launch Setup.exe file.

Library registration is required for installing. It requires no serial number

UnityLL984Library On Line Help

If you have Unity984Lib from Unity Pro 6.0 or 6.1 installed prior installing Control Expert V15, please uninstall Unity984Library before installing Control Expert V15

If you have un-installed the Unity984 Library with already installed Control Expert V15, run the repair function of Control Expert V15 to re-install the help for the (now integrated) UnityLL984Library.

2.8 DTM Version matrix

DTMs version per Control Expert version
DTM name	With Unity Pro V11.0	Unity Pro V11.0 Hotfix	With Unity Pro V11.1	Unity Pro V11.1 Hotfix	With Unity Pro V12.0	Unity Pro V12.0 Hotfix	With Unity Pro V13.0	Unity Pro V13.0 Hotfix	With Unity Pro V13.1	Unity Pro V13.1 Hotfix	With Control Expert V14.0	Control V14.0 Hotfix	With Control Expert V14.1	Control V14.1 Hotfix	With Control Expert V15.0
BME NOC 03x1.x	2.4.13	2.4.27	2.6.18	2.6.24	2.7.17	2.7.19	2.9.3	2.9.15	2.11.9	2.11.11	2.12.20	2.12.23	2.13.36	2.13.37	2.14.23
BME H58 x040	2.4.13	2.4.27	2.6.18	2.6.24	2.7.17	2.7.19	2.9.3	2.9.15	2.11.9	2.11.11	2.12.20	2.12.23	2.13.36	2.13.37	2.14.23
BME P58 x0x0	2.4.13	2.4.27	2.6.18	2.6.24	2.7.17	2.7.19	2.9.3	2.9.15	2.11.9	2.11.11	2.12.20	2.12.23	2.13.36	2.13.37	2.14.23
BME H58 x040S	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	2.12.20	2.12.23	2.13.36	2.13.37	2.14.23
BME P58 x040S	NA	NA	NA	NA	NA	NA	2.9.3	2.9.15	2.11.9	2.11.11	2.12.20	2.12.23	2.13.36	2.13.37	2.14.23
NOC 78x00	2.4.1	2.4.1	2.5.8	2.5.9	2.6.9	2.6.9	2.9.0	2.9.1	2.11.3	2.11.3	2.12.7	2.12.7	2.13.32	2.13.32	2.14.11
NOC 78x00.2	2.4.1	2.4.1	2.5.8	2.5.9	2.6.9	2.6.9	2.9.0	2.9.1	2.11.3	2.11.3	2.12.7	2.12.7	2.13.32	2.13.32	2.14.11
M_NOC 0402	3.4.0	3.4.2	3.5.7	3.5.10	3.6.8	3.6.8	3.9.0	3.9.1	3.11.3	3.11.3	3.12.7	3.12.7	3.13.34	3.13.34	3.14.11
Advanced_Generic_EDS	1.1.19	1.1.20	1.2.1	1.2.1	1.3.7	1.3.7	1.6.0	1.6.0	1.7.4	1.7.4	1.8.5	1.8.5	1.9.32	1.9.32	1.10.11
Generic_Device	1.1.19	1.1.20	1.2.1	1.2.1	1.3.7	1.3.7	1.6.0	1.6.0	1.7.4	1.7.4	1.8.5	1.8.5	1.9.32	1.9.32	1.10.11
Modbus_Device	1.1.12	1.1.12	1.1.12	1.1.12	1.1.12	1.1.12	1.1.12	1.1.12	1.1.13	1.1.13	1.2.5	1.2.5	1.2.5	1.2.5	1.2.5
BME CXM 0100	NA	NA	1.00.0001	1.00.0001	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003	1.00.0003
PME Generic DTM	1.0.22	1.0.22	1.0.22	1.0.22	1.0.22	1.0.22	1.0.30	1.0.30	1.0.30	1.0.30	1.0.32	1.0.32	1.0.32	1.0.32	1.0.32
BME AHI 0812	1.1.4	1.1.4	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.7	1.1.23	1.1.7	1.1.7	1.1.9
BME AHO 0412	1.1.4	1.1.4	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.5	1.1.7	1.1.23	1.1.7	1.1.7	1.1.9
BME NOR 2200	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	1.0.061	1.0.087
ModbusPlaceHolder	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	1.0.9
EIPPlaceHolder	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	NA	1.0.9

3 Important information

Additional useful information may be available on Schneider-electric.com (Support / FAQ Frequently Asked Questions)

Control Expert installation hangs

On some computers , Control Expert installation may hangs or freeze.

This issue is caused by incompatibility between embedded MSI and Windows Installer Coordinator. Suggestion is to enable "Turn off Windows Installer RDS Compatibility" for the duration of the installation.

See procedure on : https://support.accessdata.com/hc/en-us/articles/203263539-Windows-Installer-Coordinator-hangs

M580 Safety library

The following EFs are not available in Safety library

S_EXP, S_LOG, S_LN, S_SIN, S_COS, S_TAN et S_INT_TO_REAL

PLC Simulator

PLC simulator runs on PC and allows to simulate a real controller CPU behavior, but it is not intended to be used as a controller CPU in a production environment.

Even if PLC simulator fits the Cyber Security requirements, it is not intended to be as robust as real controller CPU.

The PCs located in the control room , or used to run PLC Simulator are highly exposed to attacks. Those PCs need to be hardened.

See “cyber security reference manual” for details.

Overlapping on %MW variables

In case of overlapping on %MW variables (ie: different variables mapped on same %MW), it is mandatory to set the “SAVE” attribute in Data Editor on one of the variables only.

Data Memory Protect

In Program Unit, the WRITE PROTECT attribute cannot be set (because it would be useless) on variables that cannot be modified (ie : Read Only)

consequently :

input variable can be “WRITE PROTECT” when there is no effective parameter on it.

An output or in/out variable cannot be “WRITE PROTECT”, and it is always read.

An external variable cannot be “WRITE PROTECT” : it inherits of attribute of the reference

A private or public variable can be “WRITE PROTECT”.

984 Quantum application from ProWORX

When converting a 984 Quantum application from ProWORX (pwx or cfg file) if project has more than 2 x Serie 800 drops, then option "shift 984 remote » must be checked.

If "shift 984 remote " option is not checked, converted project have a number of racks greater than 2 on local bus (while maximum should be 2)

Security Editor Configuration and Topology Manager

Control Expert Topology Manager does not manage user rights access details. As far as User is configured in Security Editor, Whatever the rights he has, this user can open Topology Manager and update a project.

4 Additional information from previous releases

Additional useful information may be available on Schneider-electric.com (Support / FAQ Frequently Asked Questions).

Rotate Function blocks

Behavior of rotate operation with EFs ROL_XXX (ROL_BYTE, ROL_DWORD, ROL_WORD, ROL_DINT, ROL_INT) and S_ROL_XXX (S_ROL_BYTE, S_ROL_DWORD, S_ROL_WORD) on BYTE, INT, DINT, UINT, UDINT, WORD and DWORD type , is now :

type	Number of Rotations	Valout	%s17
BYTE	0	= val. input	0
	1-31	= val. input rotated	MSB
	>31	0	0
WORD/INT	0	= val. input	0
	1-16	= val. input rotated	MSB
	17-31	Incorrect value	x
	>31	0	0
DWORD/DINT	0	= val. input	0
	1-32	= val. input rotated	MSB
	>32	0	0

In summary, behavior of the Rotate function blocks ROL_XXX and S_ROL_XXX operator is guaranteed when the number of rotations is less or equal the size of the operand :

For BYTE number of rotations is 8 max

For WORD / INT number of rotations is 16 max

For DWORD / DINT number of rotations is 32 max

BMENUA0100

BMENUA module will accept (but not utilise) incorrectly formatted IPV6 addresses.

For the BMENUA0100 OPC UA Module for M580, it is possible to enable IPSec via the web interface even if the Control Port of the BMENUA is not enabled. This is potentially misleading as IPSec is available only on the Control Port of the BMENUA0100, and hence IPSec will not be available until the Control Port is enabled.

During the firmware upgrade of the BMENUA0100 module with EcoStruxure Automation Device Maintenance tool,

· user must be connected as an Installer

· It is recommended to disconnect all clients connected to this module (OPC-UA, Web, inter-PLC connection, …)

Internet Explorer under Windows 7 is not supported to access to the Web site of the BMENUA0100 module. Please use another updated internet browser (Chrome, Firefox…).

PME SWT 0100 configuration may be lost in redundant M580 (Hot Standby) after swap or switchover.

If PMESWT0100 module is used in redundant M580 (Hot Standby) system, do not use option “Clear Files in Primary” (in Hot Standby Synchronization options) : in this case, after a swap or a switchover from primary to standby, the PMESWT0100 module configuration would be lost,

Use option “Copy Files from Primary to Standby” instead.

GET_TS_EVT_M

To ensure correct behavior of GET_TS_EVT_M in Hot Standby configuration please follow instructions given in the Notice message

NOTICE

LOST EVENTS

· GET_TS_EVT_M must only be executed on Primary PAC (it must not be executed on Standby PAC)

· The Task period must be larger than the actual running time (no task OverRun).

Failure to follow these instructions can result in loss of data

Recommendations to start Schneider USB driver :

· Do not try to connect to PLC if USB driver delivered with Unity Pro is not installed on the computer : Windows system would install a default USB device, and you would not be able to connect to PLC any more, unless you un-install the faulty USB device (via Windows Device Manager) and re-install Unity Pro USB driver : SchneiderPLCUSBDriverSuite.exe

· Connect USB cable to M580 Controller and restart computer before you connect to M580 Controller for the 1^st time.

· On Win 10 64-bit version EN(1703) it may be necessary to set manually the IP address 90.0.0.2 of USB Driver…to do so

§ Start Windows Settings > Network > Change Adapter Options

§ Right click on SE RNDIS PSX M580 and select “Properties”

§ Right click on “Internet protocol Version 4 (TCP IP V4) “ and select “Properties”

§ Prompt IP address 90.0.0.2 and subnet mask 255.255.255.0

Recommendation about Unity Pro multi-instances:

At first launch after Installation, Unity Pro will make some updates. It is recommended to let those updates go all the way before launching other instances, as it may cause dysfunctions.

Implicit Conversion

Even if Implicit Type Conversion is enable in Project settings, a link connected to an EN/ENO pin MUST be defined as BOOL.

Error bits on IODDT of 140 AII330 module does not report a channel issue. The right information is available in %IW associated to module.

With some “old generation” DTMs, Windows detects an incompatibility with DEP. So DTM, cannot be executed in Unity Pro V13. Symptoms may be : Unity Pro update catalog fails or DTM cannot be open. To fix the issue, DTM must be updated by manufacturer. Other solution : DEP protection must be disabled on Windows 7 and 10 Operating Systems. See FAQ FA304292 on Schneider-electric.com

· Schneider Communication drivers are signed with SHA-2 certificates (see https://technet.microsoft.com/en-us/library/security/2880823.aspx for details).
Be sure Window7 has the latest security updates for proper installation of Schneider Communication drivers.

· Control Expert V14.1 is only compatible with PROFIBUS Remote Master PRM V1.3 : with previous PRM versions the PRM Function Block Library cannot be installed, and DTM Catalog Update will fail.

· XMIT & XXMIT on Momentum : the buffer MSGIN is cleared before each execution of function block , in order to avoid leftovers from the previous transaction.

· To enforce cyber security, it is strongly advised to run PLC Simulator with a password protected application : A valid application with Password protection is mandatory to enforce security on computer’s Ethernet port (by default port 502).

In Simulator Panel Option, user may choose to

1. Check option “Use default application (Enforce Security)” , and prompt a valid password protected application path. Security is then enforced on Ethernet Port. Password is required anytime Simulator is started.

2. Uncheck option “Use default application (Enforce Security)”. But Security is then not correctly enforced on Ethernet Port. No password is required to start Simulator

Options dialog box is automatically displayed at first Simulator start, it can also be started with the menu command Options in the context menu of the simulator symbol in the task bar or the simulator symbol.

· Although Control Expert does not report any error if BMENOC3x1 with Firmware version < 2.05 is used in M580 HSBY, it is mandatory to check that Firmware version V2.05 (or higher) is used in any BMENOC3x1 modules in M580 HSBY configuration.

BMENOC3x1 Firmware version can be checked in BMENOC3x1 DeviceDDT (BMENOC0301_2.FIRMWARE_VERSION = 16#0205), or in embedded web pages

· In some Ladder program using JUMP instruction, with M580 High End BMEH or BMEP 585040 / 6040 processors, a build message "Fail gcc compilation" may occur.

To avoid this code generation issue go to “Project Settings”, in the “Build settings” check "Generate with LD link animation".

Then rebuild the application.

· In ST program with M580 High End BMEH or BMEP 585040 / 6040 processors, a build message "Fail gcc compilation" may occur.

Issue occurs when ST statements in section use immediate STRING values of more than 4K bytes.

Eg : MyStringVar := 'abcdef' takes 6 bytes ; MyStringVar1 := 'abcdef'; MyStringVar2 := 'ghijklmnop' takes 16 bytes.

To avoid this code generation issue, split the statements in different sections to limit the size per section below 4k bytes.

PRM module built with Unity Pro V8.0

The following information concerns M580 application using PRM module built with Unity Pro V8.0,

When opening such sta file in Unity Pro V8.1 (or superior), it is mandatory to update the PRM GTW DTM configuration and Rebuild All Project:

Open Tools/ DTM Browser

Open PRM GTW DTM and do a “fake” update.

For example :

1. Update MAC Address in General Properties Screen and click on APPLY

2. Update back the MAC Address to the former value and click on APPLY

Close PRM GTW DTM

Rebuild All Project

Memory full when building application containing DTM devices:

When Upload information is selected from project options, the project source code is loaded with the executable code when transferring the project to the PLC. These upload information contains also DTM configuration when used.
Some DTMs may use a very large amount of memory (mainly generic DTMs used for modular devices). PLC memory could be saturated in certain cases, leading to a "Memory full" error message at build time.

In that case it is possible to optimize the application memory by:

- Reducing "Data storage" size, increasing the memory size dedicated to the application.

- Adding a memory card or increasing it size.

- Reducing Upload information size by uncheck Comments and Animation table in project settings

If these actions are not successful, it will be necessary to deselect the upload information in order to build correctly the application.