EcoStruxure Control Expert V14.1 - Release Notes

Table of content

2.1 Table 1 Unity Pro Versions and PLC OS compatibility

2.2 Table 2: XEF and ZEF Files on PC

2.3 Table 3: STA Files on PC

2.4 Table 4: STU Files on PC

2.5 Table 5: PLC <=> PC Transfer

2.6 Table 6: Online modification

2.7 LL984 Libraries

3 Important information.

1 What’s new in Control Expert V14.1

Unity Pro is a key engineering tool, used at Edge Control level of Schneider Electric EcoStruxure Plant architecture: it is now renamed EcoStruxure Control Expert.

Same software - New name and look - More benefits!

To increase productivity during engineering, commissioning and operation, reducing time to market:

· Time to upload program from controller is reduced 25%

· Device Management : DIO numbers can be edited and changed

· Installation of old Libset versions < V10 is optional

· Init values can be set even on private variable of DFB instances

· New SET_VAL function block

· SRAM is now available on all M580 controllers

· LL984 display for 32 bit data is improved in Animation tables

· AKF library is supported on M580

· It’s possible to save Data from M340 and restore to M580

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

Hot Fixes listed below are implemented in Control Expert V14.1

· ControlExpert_V140_HF0556733R

· ControlExpert_V140_HF0544798R

· ControlExpert_V140_HF0537032R

· ControlExpert_V140_HF1

· ControlExpert_V140_HF2

· ControlExpert_V140_HF_PMEPXM0100_HF0312169E

· ControlExpert_V140_HF0556733R

· ControlExpert_V140_HF0544798R

Enhancement listed below are implemented in Control Expert V14.1 :

Id #	Adaptation	Title	Description of the enhancement
PEP0470939R	Adaptation	Save Data from M340 and RESTORE DATA to M580	possibility to restore a DTX file generated from M340 (using SAVE DATA, option DTX) on M580 application (using RESTORE DATA)
PEP0474558R	Adaptation	M580 supports AKF EFB library in Unity Pro	The AKF library is supported on Quantum, Momentum, M340 and now on M580.
PEP0482580R	Adaptation	Sort Data Editor and search results by logical numbering,	Data Editor and search results are now sorted in numerical order (instead of alphabetical) , for variables with number. Example : %MW100 is after %MW2, t200 after t3
PEP0488813R	Adaptation	When add / remove device in Premium ETC Ethernet DTM browser, the connections bits associated with the remaining equipment change (shift). It is OK on M580	On TSX Premium NOC module, when add / remove device DTM browser, the connections bits associated with the remaining equipment does not change any more.
PEP0495610R	Adaptation	140CRA31200 minimum version in his M580 Hot Standby is not displayed	When 140CRA31200 is selected, the minimum version for use in M580 Hot Standby is displayed
PEP0498078R	Adaptation	Animation Table enhancement to LL984 REAL data	LL984 display is enhanced to display 16 bits data in 32 bits format
PEP0502968R	Adaptation	M580 Application Update tool enhancement	In M580 Application Update tool, conversion from BMENOC03x1.3 to BMENOC03x1.4 cannot be done if M580 CPU version is < V2.30. It is OK on V2.30 and superior.” M580ApplicationUpdate tool now display a message when user convert an application with a CPU firmware version <2.3
PEP0532699R	Adaptation	DDDT aliases lost by modifying the DTM instance name	on DTM DDDT with Alias variables connected, when the name of the device and attached DDDT are changed, the aliases are no more lost.
PEP0546345R	Adaptation	State RAM size improvement on M580	on M580 , SRAM limits are extended, for easy migration of large Quantum projects
PEP0401364R	Adaptation	Remove and add DIO device without impact on status #	After addition or update a device, the Device Number can be selected among valid range, thus allowing easy update.
PEP0464306R	Adaptation	State Ram Viewer is not available on all M580	SRAM and State Ram Viewer is now available on all M580 CPUs
PEP0486029R	Adaptation	Indicate the CPU load to ensure correct application transfer between M580 HSBY Primary and secondary	CPU load (%SW100, 101…) is displayed on PLC screen
PEP0502971R	Adaptation	Control Expert compliant with Windows 10 LTSB	EcoStruxure Control Expert V14.1 has been tested with Microsoft Windows 10 Enterprise 2016 LTSB (Build 14393)

Issues listed below are fixed in Control Expert V14.1 :

Id #	Quality	Title	Issue Description
PEP0455003R	Quality	M580 HSBY Standby fails to go to Wait state on "build changes" if LOGIC_MISMATCH_ALLOWED bit is set but "Number of modifications" is set to zero	In Control Expert V14.1, if LOGIC_MISMATCH_ALLOWED bit is set but then an error is reported in case "Number of modifications" is set to zero
PEP0459022R	Quality	Import of ProWORX application loses SYMAX RIO drops	Import of ProWORX application allow to keep SYMAX RIO drops
PEP0466000R	Quality	CPU goes to HALT after download project	CPU goes to HALT after download project
PEP0471323R	Quality	After Restore DTX Data from file to PLC, Control Expert stops working	After Restore DTX Data from file to PLC, Control Expert does not stop working
PEP0471980R	Quality	missing input in DFB causes M580 to STOP	Control Expert will report a Build Error when IN-OUT parameters are set in DFBs without effective parameter (on the left part)
PEP0476538R	Quality	DTX file with Unlocated Variable not restored when unlocated Extracted bits are used.	DTX file can be restored, even with unlocated Extracted bits.
PEP0482122R	Quality	Any_array_string processing for file management to the M580 SD card : with DFB entry pass in Any_Array_String, the file is not filled by the entire string array.	In case of assignment of two arrays, an error is displayed if the size of the elements is not the same. It's the size of an element and not the array size. Size of INT -> 2, DINT -> 4, STRING -> 16, STRING[32] -> 32, ... e.g. ANY_ARRAY_STRING := Array[1..10]_OF_STRING[32] In dynamic array of STRING, the default size for an element is 16. It's not possible to affect a different size because the Offset to access the next element is based on this default value.
PEP0487189R	Quality	Unity Pro generates wrong XML and Unity DIF will report difference.	Unity DIF does not any more report "non-significant" changes on some IO initial values.
PEP0495456R	Quality	Fail GCC compilation (Section 406)	The specific project does not any more report compilation error
PEP0496372R	Quality	Changed fallback mode of IO when converting from Concept	fallback mode of IO when converting from Concept is now correct.
PEP0496665R	Quality	“Unknown Error” message on STA or upload from V13.0 project	Project can be open from sta or uploaded with Control Expert V14.1
PEP0497248R	Quality	M580 Application Update Tool documentation update	Documentation describes now the conversion from BMENOC03x1 version .3 to version .4
PEP0497287R	Quality	in V13.1 Unlocated EBOOL does not change color when forced off (F0)	Unlocated EBOOL used in structured text section change changes now color when the bit is forced to F1 and F0
PEP0499858R	Quality	in specific project, Unknown Error occurs on open .STA or upload from BMEH586040	No more "Unknown Error" occurs on open .STA or upload from HSBY BMEH586040
PEP0500068R	Quality	Memory overflow on Build all after Sub Routine deletion	After SR deletion, Rebuild All project works fine.
PEP0500748R	Quality	Conversion from Concept : "Symbols Instead of Direct Addresses"	information is added in documentation : Modify the help to explain that only one array will be created for the same start address and that this array size will have the bigest found while converted
PEP0500867R	Quality	Conversion from PWX fails because specific DFB	Conversion from PWX is OK
PEP0500894R	Quality	Conversion from Momentum Concept	After conversion of Momentum Concept architecture, with GET_4X and PUT_4X. T, an interface function is created in Control Expert
PEP0502991R	Quality	Issue restoring data DTX file for 2 dimensions Table ARRAY[0..n,0..m] of INT.	Save Restore Data is now Ok for 2 dimensions, TabL3 ARRAY[0..49,0..19] of INT.
PEP0503264R	Quality	Save STA duration is too long	save STA or STU is now faster.
PEP0503501R	Quality	PLC scan time is higher onM580 6040 than on 4040	PLC scan time is optimized on both M580 6040 and 4040
PEP0503821R	Quality	SHR block function does not behave the same according to "optimized code" project setting.	Whatever the project option "optimized code" SHR behavior is now OK.
PEP0503943R	Quality	M580 CPU stops working after enable "NOP850_EVTS"	enable "NOP850_EVTS" does not any more stops CPU
PEP0504465R	Quality	Dynamic array not allowed in safety FBD section but multi-dimensional array is allowed	When multi-dimensional array is used in safety sections, an error is now displayed at build
PEP0505769R	Quality	Confusing Message after importing section or functional group	the message is now consistent with Unity Pro V13.0 behavior "The variable exists already"
PEP0509025R	Quality	When Variable name ( device name) is changed in DTM device list, new variable names are not updated in program.	When Variable name ( device name) is changed in DTM device list, variable names are now updated in program.
PEP0516265R	Quality	Unexpected behavior with instruction WHILE … DO	Mathematical operation is now correct in an expression with literal value , even when "Implicit Type conversion" project setting is enabled.
PEP0517927R	Quality	Build Time too long when BME NOC with local slaves are configured.	Build time is now optimized.
PEP0522307R	Quality	Sorting variables by Address column is incorrect	Sorting variables by Address column is correct
PEP0523418R	Quality	PLC fails because of Time Stamp variables not declared as "HMI"	A Time Stamped variable is automatically added to Data Dictionary
PEP0523628R	Quality	Incorrect input types on PWS_DIAG function blocks	Type expected on LEFT_PWS pin and RIGHT_¨PWS pin is ANY.
PEP0524131R	Quality	"Unknown error" at build	new consistency checks provides now more detailed diagnostic
PEP0524586R	Quality	Excel tool Variables Management.xlsm : Expand is not working.	Excel tool Variables Management.xlsm is updated.
PEP0526906R	Quality	Project takes too long to open	open time is optimized.
PEP0528727R	Quality	file converted from ProWORX has no RIO drops	Remote IO drops are kept after conversion
PEP0532222R	Quality	"Multi-Assignment" feature is not working with "Implicit conversion"	"Multi-Assignment" feature is now OK when “Implicit Type Conversion" is set
PEP0532458R	Quality	Vulnerability in License Manager (CVE-2018-20033)	Control Expert installs last available version of License Manager/ Floating License Manager
PEP0532706R	Quality	Since V13.0, "Item not found" is displayed by searching an Alias variable	Search on Alias is now possible.
PEP0533007R	Quality	SHR block switch left when the project option "optimized code" is checked and data input is INT.	SHR block behavior is now consistent.
PEP0533012R	Quality	Control Expert V14.0 stops working without warning	Problem fixed.
PEP0533265R	Quality	Build exception error is displayed after changing CXM Can Open device name	in BME CXM 0100 DTM, after modification of the name of CAN open Device, project can be built
PEP0533284R	Quality	a pixel is missing on SFC branch drawing	SFC branch drawing is OK
PEP0534117R	Quality	Date attribute of DFB is updated after Project Setting change	The date of last modification of the DFB is no more modified after an update of Project Settings (such as Variables : Allow leading digits, Character set, Allow Usage of EBOOL edge, …etc.)
PEP0534760R	Quality	With user profile Operate ,"Control via PLC" cannot be selected after "Control via User"	With "Operate profile", by clicking on "Control via User", button is now maintained and it is possible to select "Control via PLC" again.
PEP0535004R	Quality	Safety STA archive file cannot be open, when Project Setting "Optimize data-online change" was set	Safety STA archive file can be open and built
PEP0535039R	Quality	Control Expert V14 does not accept New Profile from Security Editor	New Profile can be created and used
PEP0535822R	Quality	S_EMERGENCYSTOP_0 do not display status values	S_EMERGENCYSTOP_0.DiagCode is now displayed
PEP0536068R	Quality	the " HMI variable" setting is unselected from Device DDT after Rebuild All	After Rebuild All , the "HMI variable" setting is unchanged.
PEP0537490R	Quality	"Invalid File Format" error in DTM Audit Tool	DTM Audit Tool does not any more report wrong error
PEP0539041R	Quality	After addition of an output pin to a DFB & Build Change the code will not work correctly.	After addition of an output pin to a DFB & Build Change, behavior is correct.
PEP0540995R	Quality	in some conditions, M580 password protection can be bypass	M580 password protection is improved
PEP0541156R	Quality	Ladder animation shows error when animated	Ladder animation is correct.
PEP0541418R	Quality	Unable to load configuration by adding .CO file in TSXCPP110	Configuration is OK after adding .CO file in TSXCPP110
PEP0542123R	Quality	LD logic execution issue if extracted bit from Word used as contact	LD logic execution is now correct with extracted bit from Word
PEP0542715R	Quality	Control Expert stops working in several program operation scenarios	Control Expert does not stops working in related scenario
PEP0543432R	Quality	BCD_TO_INT instruction in nested DFB is not executed on BMEH584040 / 2040	BCD_TO_INT instruction in nested DFB is correctly executed
PEP0544042R	Quality	Vulnerability to file access	fixed vulnerability
PEP0544778R	Quality	V14 Safety project upload fails (reason is : EBOOL variables must not be used in PROCESS and SAFE as input or output variables)	Error is displayed when EBOOL variables are used in PROCESS and SAFE as input or output variables
PEP0548076R	Quality	incorrect behavior Technical Support Diagnostic Wizard not working fine	Technical Support Diagnostic Wizard is correct and documented
PEP0548255R	Quality	After update on S908 drop with 140CRA31908, Build Change is not correct	After add/delete module in S908 drop managed by 140CRA31908 and Build Change , the behavior is correct.
PEP0550768R	Quality	In V14, Change CPU from M580 v2.2 to v2.8 is not possible	Change CPU from M580 v2.2 to v2.8 is possible
PEP0428837R	Quality	in Advantys V11, if option ‘configure Runtime parameter’ is checked then Input / Output physical mapping is not correct in Control Expert.	When option ‘configure Runtime parameter’ is checked in Advantys V11, then Input / Output physical mapping is correct in Control Expert.
PEP0532236R	Quality	Fix Open SSL vulnerabilities	Updated to Open SSL v 1.1.1c to fix vulnerabilities
PEP0532459R	Quality	Denial of Service in License Manager (CVE-2018-20031)	EcoStruxure Control Expert implements last available version of License Manager/Floating License Manager.
PEP0532460R	Quality	Denial of Service in License Manager (CVE-2018-20032)	EcoStruxure Control Expert implements last available version of License Manager/Floating License Manager.
PEP0532461R	Quality	Denial of Service in License Manager (CVE-2018-20034)	EcoStruxure Control Expert implements last available version of License Manager/Floating License Manager.
PEP0536860R	Quality	Restore located data is not working from a V12.0 .DTX file to V14.0 (when M580 CPU changed)	Restore data is correct from a V12.0 .DTX file to V14.0
PEP0540480R	Quality	Inconsistent section code execution versus Unity Pro V13.1	Section code is execute as expected.
PEP0540503R	Quality	SFC section with same name in 2 different Program Units : after Export/Import the Actions and Transitions of the two Programs are duplicated	If SFC section have same name in 2 different Program Units, then after Export/Import the Actions and Transitions are not duplicated
PEP0541995R	Quality	Control Expert stop working after Restore DTX file on 140CPU53414	"Restore Data from File to PLC" is correct on 140CPU53414U
PEP0543956R	Quality	Error after Rebuild All of V12 project with new version of DTMs	Rebuild All of V12 project with new version of DTMs is correct.
PEP0544798R	Quality	Control Expert stops working after copying VJD object and right click in LD editor	After copying an object from Vijeo Designer (Ctrl C on a green rectangle for example) or copy of an object in Microsoft WORD , Control Expert does not stop working after right click in LD (LADDER) editor
PEP0545900R	Quality	"Process Interface" variable cannot be linked to "actual parameter"	Actual Parameter can be correctly added to variable interface
PEP0551406R	Quality	"PLC Memory Overflow" error at build on specific project.	Related project is built correctly
PEP0448366R PEP0491622R	Quality	Remove Microsoft XML Parser version 4 (that shows Cybersecurity vulnerability) , and go to V6	Control Expert V14.1 does not require any more Microsoft XML Parser version 4 It requires version 3 (for DTM part) and version 6.

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
V14.1	/	/	/	/	3.2	3.1	3.1
V14	/	/	/	/	/	2.9()* 2.8	2.9()* 2.8
V13.1	/	/	/	/	/	2.7	2.7
V13	/	/	/	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)

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

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

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)

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

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

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

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.

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)

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

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

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

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

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

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

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

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

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

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

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

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

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)

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

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

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

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 V14

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 in Unity Pro DVD (*) or 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 Unity Pro 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 V14.1, please uninstall Unity984Library before installing Control Expert V14.1

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

3 Important information

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.

BMENUA0100 is not yet commercialized at Control Expert V14.1 commercialization date.

A Hot Fix may be necessary to use BMENUA0100 with Control Expert V14.1 : be sure you activate SESU Schneider Electric Software Update on your computer , or check updates availability on Schneider-Electric.com.

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, …)

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

· 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

· When Project Setting "IO scanning mode" is changed (enhanced / legacy) the Modbus TCP Device DDT structures of existing devices can been changed, so application behavior can be changed.

· On Quantum and M580, State Ram has same size 130048 Bytes. But on Quantum, Boolean objects (%I and %M) are stored in 3 bits while on M580 they are stored in 8 bits. So for the same number of Word objects (%IW and %MW), it is possible to configure 2,5 times more Boolean objects (%I and %M) on Quantum versus M580.

· As CXM module is not allowed in M580 HSBY configuration, the associated CRA (BME CRA 312 10 (SV>=2.10)) is not allowed on the HSBY CPUs . So only BME CRA 312 10 (SV>=2.00) can be selected. But a minimum version of the embedded software (firmware) must be 2.14

· New : Unity Translator is an open source tool that allows to fasten the translation of comments (variables, sections…) from one language to another. This tool is delivered “as is”, and has not been tested nor verified by Schneider-Electric.

Unity Translator source code, binary and documentation is available on https://schneider-electric-unitypro.github.io/unityTranslator/

· DTM Audit Tool cannot be used with .sta generated by Unity Pro versions V11 and before.

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

· IPSEC on BMENOC03x1 : When IPSec is enabled on the BMENOC03x1, its addresses IPA & IPB become inactive. This is managed internally in the NOC, and is not reflected in the configuration screens.

Only Main IP (and the related Main IP+1 if Standby) is enabled in this configuration.

· Default setting of BMENOC's backplane port : In order to avoid a potential broadcast storm, the default setting of the BMENOC's backplane port is now "disabled". Refer to the user documentation for more details.

· FDR sync button in M580 CPU DTM : In a HSBY system, the FDR servers of the paired BMENOC's are automatically synchronized. You can remove the auto-synch by disabling this service in the DTM.

If, for some reason, you want to manually re-sync the servers, you can do it by pressing this button. Note that it will also reactivate the auto-sync, as this is the normally recommended sync mode.

· Silent mode installation : install may be stopped (requiring manual acknowledge) due to .NET prerequisite check. To avoid manual acknowledge, edit install.bat file and remove the lines :

:ver_dotnet_35

"%DIRMSI%\ISSetupPrerequisites\{074EE22F-2485-4FED-83D1-AAC36C3D9ED0}\dotnetfx35.exe" /s/q:a

· On Windows Server 2012 it may be needed to adapt default Firewall configuration to enable OS Loader read/write access to Ethernet module (CRP31xxx , NOE77xx., NOC78xxx,, TSXETYxxx, ..) :

· use default Windows 8.1 configuration (check : notify when Firewall block an app)

· check if OS Loader is allowed : Control Panel > System and Security > Windows Firewall> Allowed apps

· 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

· 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

· On Windows 7 64 bits, or Windows Server 2008 64 bits, the Source IP field inside Master or device DTM may be reset to default address (127.0.0.1) and in read-only.

So it is no more possible to update IP address and hence no more possible to connect to the target devices from the DTM menus. Only way to make it work again is to restart UnityPro.

The issue is due to wrong Windows 64 bits API Network function behavior.

Microsoft delivered fix for computers where this issue is found.

The problem is described in Microsoft KB article https://support.microsoft.com/en-us/kb/2588507

From Microsoft recommendation, the fix should only be applied on machines with the mentioned configuration, and where issue described above occurs

· When using Modbus Plus Proxy (TCSEGDB23F24A) with the M580, it is recommended to not use the Modbus Plus Connection with Unity to download application to the M580. The Ethernet connection would be lost at the end of download and will not be re-established via Modbus Plus, until PLC is put into run mode via another connection (eg : via USB or Ethernet direct connection.).

· NULL is a reserved word in Unity pro V8.0 (REFERENCES initializations) . So any application done with previous versions of Unity Pro and containing a variable or a program section named “NULL” will report build errors.

· Use of multiple Unity Pro instances limits the number of simultaneous opened editors to 15 for the first session and 6 editors for the following.
This limitation caused by a Windows parameter can be removed by modifying the registry as indicated here after:

Run Registry editor (Regedit)

From the Registry editor search the following registry key :
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems

In the right screen, double click on the Windows name to open the string modification window.

Find the SharedSection string in the data value. This parameter specifies the system and desktop heaps using the following format:
SharedSection=xxxx,yyyy,zzzz
The values are specified in kilobytes.

The second SharedSection value (yyyy) controls the size of the desktop heap (used for windows objects).
If on your machine, yyyy is < 8192 then set yyyy to 8192.
The system MUST be restarted before the changes take effect.

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

· Port Mirroring:

Use this feature for debugging purpose only and not in normal operating mode. Under heavy load conditions, when Port Mirroring is enabled, it could impact IO connections, especially for DIO traffic. It is recommended to turn-off the Port Mirroring feature in normal operating modes and use CIP object to turn ON and OFF this feature.

· NOC DTM not removed from configuration

If NOC DTM is connected to a device and NOC module is removed from the configuration, the NOC module is removed but not its DTM. To remove the NOC DTM, it is necessary to disconnect DTM before.

· Rack Viewers

When a 140NOE77101 resides in a rack with ERIO, but with no S908 network, it displays the ERIO head (140CRP31200) as an S908 (140CRP93xxx). It also will display ERIO remote racks, but these remote racks have no data.

Quantum CPU's, 140NOE77101 and 140NOC7710X may not display ERIO module (140CRP31200) in the Rack Viewer.

Quantum CPU's, 140NOE77101 and 140NOC7710X do not display remote drops on S908 networks when the RIO Drops are selected by right clicking the CRP93xxx.

· Import from Concept / ProWORX :

WARNING

UNEXPECTED APPLICATION BEHAVIOR

· The Concept / ProWORX application converter translates the application but does not ensure its correct operation. Test the application after the conversion.

Failure to follow these instructions can result in death, serious injury or equipment damage.

o When converting legacy 984 PLC with local IOs , a new option "Shift 984 remote" allows to import Serie 800 local IOs to Quantum Remote drop #1.

But in all Serie 800 or Quantum Remote IO drops are then shifted by 1 (drop #1 is converted to #2, drop#2 to #3..etc).

Thus all original drop address in the traffic Cop (I/O mapping) must be adapted accordingly.

To avoid this behavior, user must unselect option "Shift 984 remote".

o Conversion from Modsoft application using Legacy 984 Controllers with local 800 series rack and multiple remote drops (either 800 of Quantum) may fail.

We identified different uses cases where drops or modules may be lost or incorrectly converted.

This issue will be fixed in next release of Unity Pro software.

o Conversion to M340 digital modules BMX DDM16022 or BMXDDM16025 or BMXDDM3202K

When converting legacy applications with digital mixed modules (ie : with both input & outputs) is converted to M340 controller, the corresponding modules (BMX DDM16022 or BMXDDM16025 or BMXDDM3202K) must be deleted then re-created in the configuration.

This issue will be fixed in next release of Unity Pro software.

o Unity Pro Converter adds a “_r” at the end of some variable names

Unity Pro Converter add a “_r” at the end of variable names when variable is used in both IEC and LL984 programs.

Unity Pro, like Legacy software packages, limits variable names to 32 character. If the original variable name is 31 or 32 characters in length, the last character(s) of that variable is replaced by “_r”.

This may cause different variable to get the same name in Unity Pro (in case if 31^st and/ or 32^nd character is different)

o Unity Pro Converter adds a “_” at to the beginning of variable names that originally started with a number

Unity Pro Converter add a “_” at to the beginning of variable names when the variable name started with a number.

Unity Pro, like Legacy software packages, limits variable names to 32 character. If the original variable name is 32 characters in length, the last character of that variable is replaced.

This may cause different variable to get the same name in Unity Pro (in case only 32^nd character is different)

o Import fails when a Concept application in .asc format with "project with used DFBs" selection is opened
It is not possible to import an asc file which was created with the menu item "project with used DFBs (Re-Connect to Equal)". The Concept Converter allows only asc files which are created like described in the Unity online help. While exporting the application from Concept, do not use the export range "Project with used DFBs(Re-connect to Equal)".

o Broken wire information for an analog module may not be available in the status word.

If wiring control for the analog module is used in the imported application, the user has to configure it manually after import.

o Manual work may be required after import of some 984 applications with B800 series I/O for ProWorx32

The import log and messages should be checked and the application corrected manually.

o Legacy application configured with 984-351 CPU can’t be imported.
The applications with the 984-351 CPU must be changed to another CPU, e.g. 984-785E and then can be successfully imported to Unity.

o Concept IEC import
Concept IEC applications that are using the section disable component (SectionName.disable) will need this logic reviewed for correct execution after the Unity import. It has been seen that the import may incorrectly invert this Boolean causing the section to be executed when its execution should have been disabled.

· LL984 Editor :

o M340 in Mixed Mode (Topologic & State RAM)

It is advised to reserve in State RAM (in CPU configuration) one more object than necessary.

o Network editing problem.

If you delete a column located on the right of a vertical link, not all horizontal links connected on the right of the vertical links will be maintained, except for the top and bottom ones.

To re-establish the link you have to delete and insert again the disconnected element. You may also drag and drop the effected elements within the network to re-establish the visibly disconnected links.

o MSTR Function not working on the M340 platform
The LL984 function block MSTR is only working on Quantum platform, but not on M340. As a workaround for M340 the IEC function blocks READ(WRITE)_VAR can be used instead by creating IEC sections.

o Disable states are not part of the application download in Unity Pro.

When importing an LL984 application that contains disabled inputs or coils an Animation table named “Disables” will be created. This Animation Table contains the reference addresses and disabled states from the original application. When the application is Built and downloaded to the PLC, prior to starting the PLC, the data in the “Disables” Animation table can be transferred to the PLC. Refer to the user documentation for more information on this procedure.

o The Unity OS doesn’t prohibit the operator from modifying and forcing Boolean states.

With the Memory Protect switch on in LL984 PLC’s the operator using the programming software was prohibited from disabling and forcing coil and input states. Unity’s Memory protect scheme does not prevent Booleans from being forced. Refer to the user documentation for more information on the Memory protect switch operation.

o Unity utilizes variables of the proper data type but doesn’t allow the data to be viewed in the Animation Table in various formats, as in other LL984 editors.

In ProWORX, you can view any 4x reference pair in a “Floating Point” format, In Concept it would be displayed as a “Real”. Since Unity displays the data in the format of the defined variable this option is not available without creating another variable. To view some Math function data correctly the user can either select the “Show instruction” window to view the data when online, or in the Animation tables you can view the data using the formatting option of “%MFxx”, where xx is the first of the 2 %MWxx data words used. (IE: If 400200 and 400201 are used to hold Floating Point data, using %MF200 in the Animation table will allow you to display the proper Floating Point data in Unity.)

o Prior to converting a Hot Standby application the following issues should be checked and corrected to assure a successful conversion.

§ In order to successfully convert a Quantum LL984 Hot Standby application it is required that you configure your LL984 application to account for the 2 slot CPU replacement required for Unity Hot Standby applications. If the slot to the right of the CPU is the CHS module the configuration will convert correctly. If the slot to the right of the CPU is a CRP, NOM, or NOE, the associated information (RIO drops etc.) will not be converted.

§ LL984 Hot Standby applications could be configured with a Hot Standby configuration extension, or with a CHS or HSBY loadable. The Unity Import will only look for the Hot Standby configuration extension in order to convert the application to the Unity Hot Standby Processor (140CPU67160).

o Compact and M340 discrete module configured in WORD format work differently

In the case of Compact application, BCD data value of 0001 turns on output #16 (1-16) I/O module. On the M340 the corresponding module turns on output #00 (0-15). This issue can be resolved by either making an application change or rewiring the I/O.

o In M340 state Ram mode, the discrete and the analog input are not refreshed when %S30 or %S31 are reset

Do not use the %S30 and %S31 words when the M340 is in state RAM or mixed topological mode.

o The bottom output of the LL984 timer function block is not activated if in the first scan the bottom input "is active" and the top input is not active.

As a workaround, the top input of the timer needs to be activated during the initial scan to get the bottom output to energize. The timer function blocks will function as expected after that.