© Schneider Electric, 1995-2016; All Rights Reserved
Accéder à la version française
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.5
Table 5: PLC <=> PC Transfer
2.6
Table 6: Online modification
Unity Pro V11 support new Modicon M580 Controllers :
· Support new Modicon M580 High End
· Support new Modicon M580 HSBY CPUs
· Support LL984 language on Modicon M580
· Quantum Ethernet IO drops is now supported on Modicon M580
For details see attached pdf file
(Adobe Acrobat Reader is necessary to open the file)
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.
|
Unity
Pro Version |
PREMIUM |
QUANTUM |
QUANTUM SAFETY Minimum OS Version |
M340 |
M580 |
Momentum Minimum OS
Version |
|
V11 |
/ |
/ |
NA |
/ |
2.1 |
/ |
|
V10 |
/ |
3.3 (*) |
NA |
2.7 |
2.0 (**) |
/ |
|
V8.1 |
3.10 |
3.2x (*) |
NA |
2.60 |
1.1x |
/ |
|
V8.0 |
/ |
3.20 |
NA |
/ |
1.0 |
1.0 |
|
V7.0 |
3.0 |
3.10 |
3.0 |
2.50 |
NA |
NA |
|
V6.1 |
/ |
/ |
NA |
2.40 |
NA |
NA |
|
V6.0 |
2.90 |
3.00 |
NA |
2.30 |
NA |
NA |
|
V5.0 |
2.60 / 2.70 (2) |
2.80 |
NA |
2.20 |
NA |
NA |
|
V4.1 |
2.60 / 2.50 (2) |
2.70 |
2.0 |
2.10 |
NA |
NA |
|
V4.0 |
2.60 / 2.50 (2) |
2.60 |
NA |
2.00 |
NA |
NA |
|
V3.1 |
2.50 (2) |
2.40 |
1.0 |
1.00 |
NA |
NA |
|
V3.0 |
2.40 |
2.40 |
NA |
1.00 |
NA |
NA |
|
V2.3SP1 |
2.30 |
2.30 |
NA |
NA |
NA |
NA |
|
V2.2 |
2.21 (1) |
2.00 |
NA |
NA |
NA |
NA |
|
V2.1 |
2.00 MFB |
2.00 |
NA |
NA |
NA |
NA |
|
V2.0 |
2.00 |
2.00 |
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)
(**) A M580 application with CPU V1.1x
(developed with Unity Pro V8.0 or 8.1, or 10.0) cannot be updated to CPU V2.0 : due to
compatibility issues, the “Change CPU” option is not allowed. The proposed
solution is to export/import variables and program into a new application.
2.2 Table 2: XEF and ZEF Files on PC
|
Open XEF Files |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
|
Modicon M580 ≤ V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NA (5) |
NA (5) |
NA (5) |
NA (5) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
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 should not be opened and run with DTMs version n-1 (or prior)
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 avaialble on M580 platform
(zef format only is available for M580 platform).
|
Open ZEF Files |
With |
With |
With |
With |
With |
With |
With |
With |
|
Modicon M580 V1.0 application |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NA |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
||||||
|
Momentum Unity V1.0 application |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
||||||
|
Premium / Quantum |
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
||||||
|
Quantum |
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
||||||
|
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
|
Modicon M340 |
NA |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
||||||
|
Quantum safety |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
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
(4) Downward
compatibility of DTM's is not garanteed : so If an application created with Unity Pro
contains DTMs version n, it should not be opened and run with DTMs
version n-1 (or prior)
Upward compatibility of DTMs is garanteed : 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 STA Files on PC |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With (4) |
With (4) (5) |
With (4) (5) |
With (4) (5) |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium /
Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium /
Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
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 can not 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
(4) Downward compatibility of DTM's is not
guaranteed : so If an application created with Unity Pro contains DTMs version n, it should not be opened and run with DTMs version n-1 (or prior)
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
Restrictions:
Downward compatibility of DTM's is not guaranteed : so If an application
created with Unity Pro contains DTMs
version n, it should not be opened
and run with DTMs version n-1 (or prior)
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 |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
|
Application generated with |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
|
Application generated with |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
2.5 Table 5: PLC <=> PC Transfer
|
PLC
<=> PC |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
With |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
||||||||||
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
||||||||||
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
||||||||||
|
Quantum |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
||||||||||
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|||||||||
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
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 |
With Unity
Pro V3.0 |
With Unity
Pro V3.1 |
With Unity
Pro V4.0 |
With |
With Unity
Pro V5.0 |
With |
With |
With |
With |
With |
With |
With |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES
(2) |
YES
(2) |
YES
(2) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES
(2) |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
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
(4) Downward
compatibility of DTM's is not garanteed : so If an application created with Unity Pro
contains DTMs version n, it should not be opened and run with DTMs
version n-1 (or prior)
Upward compatibility of DTMs is garanteed : If an application created with Unity Pro contains DTMs
version n, it can be opened and run with DTMs version n+1 and above.
.
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 Unity V11.
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 8.1 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
8.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 Unity Pro V11, please uninstall Unity984Library
before installing Unity Pro V11.
If you have un-installed the Unity984 Library
with already installed Unity Pro V11, run the repair function of Unity Pro V11
to re-install the help for the (now integrated) UnityLL984Library.
Additional useful information may be available on
Schneider-electric.com (Support / FAQ Frequently Asked Questions).
· To enable the
configuration of Quantum Remote EIO drop (140CRA31200) on M580 Controller it is
mandatory to install update UnityPro_V110_HF1
· When M580 is configured as NTP Client, a
Rebuild All is mandatory after an update of Primary NTP Server address to take
into account the new address.
· Although Unity Pro 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
· When new profile is
created in Unity pro Security Editor (example : MySuperProfile), the
users associated to this new profile does not have right to add or update DTM
in configuration (eg : create a new M580 application)
To enable right to add or update DTMs in configuration a .config file can be updated :
please see FAQ FA245141 available on
Schneider-electric.com (go to Support >> FAQ)
· A M580 application with CPU V1.1 (developed with Unity Pro
V8.0 or 8.1, or 10.0) cannot
be updated to CPU V2.0 : due to compatibility issues, the “Change CPU”
option is not allowed. The proposed solution is to export/import variables and
program into a new application.
· It is not
recommended to run Unity Pro on Windows 8.1 Operating System running on VMWare.
· 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 Pannel > 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 , 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 v10, or v11) 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 adress 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 http://support.microsoft.com/kb/2588507/en
From Microsoft recommendation, the fix should only be applied on machines with the
mentioned configuration, and where issue described above occurs
·
Unity Pro requires Microsoft .NET 3.5. Depending on the target
Windows version and Windows configuration, .Net 3.5 may be
-
not installed
-
installed but not enabled ( the related "windows
feature" is not set ON )
-
installed and enabled
See Read Me Unity Pro V8.1 for more
details
· On Windows 8 and 8.1, a reboot of computer is
required after USB driver installation to connect to Momentum, M580 or MC80 controllers : reboot is necessary to assign correct IP
address in the driver.
· 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.
· 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.
·
On
Windows 8.1, for some applications, Unity Po simulator may not work. To avoid
this wong behaviour, modify the Windows registery :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel "DisableExceptionChainValidation"=dword:00000001
· 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.
Under Windows XP and some Windows Vista machine, this value is by default 3072.
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.
·
Hot Standby : Standby PLC overrun case
When the Standby PLC is in overrun, it goes to Run
Offline state until the overrun situation ends. One way to
fix the problem is to increase the MAST task period of the system.
·
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 31st
and/ or 32nd 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 by eliminated.
This may cause different variable to get the same name in Unity Pro (in case only 32nd 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 The TCP/IP IO Scanner information from a
Concept application may not get imported.
IO Scanner definitions of Concept originated
applications must be re-entered manually after import.
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.
Table des matières
2.1
Tableau 1: Compatibilité entre applications Unity Pro et OS automate
2.2
Tableau 2: Fichiers XEF et ZEF sur l'ordinateur
2.3
Tableau 3: Fichiers STA sur l'ordinateur
2.4
Tableau 4: Fichiers STU sur l'ordinateur
2.5
Tableau 5: Transfert Automate <=> PC
2.6
Tableau 6: Modification en ligne
Unity
Pro V11 supporte les nouveaux processeurs de la famille Modicon M580 :
·
nouveaux
processeurs Modicon M580 High End
·
nouveaux
processeurs Modicon M580 HSBY.
·
Support
du langage LL984 sur Modicon M580
·
Support
des IO drops Quantum Ethernet sur Modicon M580
Pour
plus de details voir
le document attached pdf file (Adobe Acrobat Reader est nécessaire)
En Anglais uniquement
2.1
Tableau 1: Compatibilité entre applications Unity Pro et OS automate
La version
d’application correspond à la version de l’OS choisi dans l’écran de sélection
du processeur
La version de l’OS correspond à la version minimale requise pour exécuter un niveau
fonctionnel de l'application.
Une version ultérieure d’OS garantit la compatibilité avec les applications
existantes
par exemple, une application version V2.00 générée par Unity Pro peut être
exécutée par un automate V2.30.
Une version Unity Pro gère les applications des versions précédentes.
|
Unity
Pro Version |
PREMIUM |
QUANTUM |
QUANTUM SAFETY Minimum OS Version |
M340 |
M580 |
Momentum Minimum OS
Version |
|
V11 |
/ |
/ |
NA |
/ |
2.1 |
/ |
|
V10 |
/ |
3.3 (*) |
NA |
2.7 |
2.0 |
/ |
|
V8.1 |
3.10 |
3.2x (*) |
NA |
2.60 |
1.1x |
/ |
|
V8.0 |
/ |
3.20 |
NA |
/ |
1.0 |
1.0 |
|
V7.0 |
3.0 |
3.10 |
3.0 |
2.50 |
NA |
NA |
|
V6.1 |
/ |
/ |
NA |
2.40 |
NA |
NA |
|
V6.0 |
2.90 |
3.00 |
NA |
2.30 |
NA |
NA |
|
V5.0 |
2.60 / 2.70 (2) |
2.80 |
NA |
2.20 |
NA |
NA |
|
V4.1 |
2.60 / 2.50 (2) |
2.70 |
2.0 |
2.10 |
NA |
NA |
|
V4.0 |
2.60 / 2.50 (2) |
2.60 |
NA |
2.00 |
NA |
NA |
|
V3.1 |
2.50 (2) |
2.40 |
1.0 |
1.00 |
NA |
NA |
|
V3.0 |
2.40 |
2.40 |
NA |
1.00 |
NA |
NA |
|
V2.3SP1 |
2.30 |
2.30 |
NA |
NA |
NA |
NA |
|
V2.2 |
2.21 (1) |
2.00 |
NA |
NA |
NA |
NA |
|
V2.1 |
2.00 MFB |
2.00 |
NA |
NA |
NA |
NA |
|
V2.0 |
2.00 |
2.00 |
NA |
NA |
NA |
NA |
(1) uniquement
TSX P 57 5634 M.
(2) uniquement TSX H57 24 M and TSX H57 44
M
NA Non Applicable : Applications non supportée.
X
Pas d’évolution
(*) Quantum minimum OS version avec Unity Pro V8.1 : 3.20 (standalone) ou 3.21 (Hot Stand By CPUs)
Quantum minimum OS version avec Unity Pro V10 : 3.3 (high end
CPUs 140CPU6xx) ou 3.20 (autres CPUs)
(**) Une application M580 développée pour une CPU V1.1x (avec Unity Pro V8.0 , 8.1, ou
10.0) ne peut pas être mise à jour avec
CPU V2.0 : en raison de problèmes de compatibilité l’option « Remplacer le
processeur « n’est pas disponible. Il est nécessaire d’exporter/exporter
les variables et le programme pour réaliser une nouvelle application.
2.2 Tableau 2: Fichiers XEF et
ZEF sur l'ordinateur
|
Ouverture fichier XEF |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
|
Modicon M580 ≤ V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NA (5) |
NA (5) |
NA (5) |
NA (5) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
NA : Non Applicable / Sans Objet (les fonctions de sécurité
Quantum n'existent que pour Unity Pro V3.1, V4.1 et V7.0).
Ø La version d'application correspond au choix
de l'automate dans l'écran de configuration Unity Pro lors de la création d'un
projet (V2.00, V2.30, etc.).
Voir Compatibilité entre Unity Pro, applications et SE de l'automate.
Restrictions:
(1)
Quand le fichier XEF créé avec Unity Pro ≥ V6.0 contient des sections
LL984 l’application ne peut pas être ré ouverte par une version d’Unity Pro
inférieure.
(2) Quand le fichier XEF créé avec Unity Pro ≥
V6.1 pour un automate M340 contient des sections LL984 l’application ne peut
pas être ré ouverte par une version d’Unity Pro inférieure.
(3) Quand le fichier XEF créé avec Unity Pro
V7.0 contient des Bits extraits de DDT l’application ne peut pas être ré
ouverte par une version d’Unity Pro inférieure
(4) La compatibilité descendante des
DTMs n’est pas garantie : une application créée avec des DTMs version n, ne
doit pas être utililsée avec des DTMs version n-1 ou
antérieures.
(5) Seul le format ZEF est supporté avec la plateforme M580 : le format
XEF n’est pas supporté.
|
Ouverture fichier ZEF Files |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
|
Modicon M580 V1.0 application |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NA |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
||||||
|
Momentum Unity V1.0 application |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
||||||
|
Premium / Quantum |
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
||||||
|
Quantum |
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
||||||
|
Modicon M340 |
NA |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NA |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
||||||
|
Quantum safety |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
NA : Non Applicable / Sans Objet (les fonctions de
sécurité Quantum n'existent que pour Unity Pro V3.1, V4.1 et V7.0).
Ø La version d'application correspond au choix
de l'automate dans l'écran de configuration Unity Pro lors de la création d'un
projet (V2.00, V2.30, etc.).
Voir Compatibilité entre Unity Pro, applications et SE de l'automate.
Restrictions:
(1)
Quand le fichier ZEF créé avec Unity Pro ≥ V6.0 contient des sections
LL984 l’application ne peut pas être ré ouverte par une version d’Unity Pro
< V6.0.
(2) Quand le fichier ZEF créé avec Unity Pro ≥
V6.1 pour un automate M340 contient des sections LL984 l’application ne peut
pas être ré ouverte par une version d’Unity Pro < V6.1.
(3) Quand le fichier ZEF créé avec Unity Pro
V7.0 contient des Bits extraits de DDT l’application ne peut pas être ré
ouverte par une version d’Unity Pro inférieure
(4) La compatibilité descendante des
DTMs n’est pas garantie : une application créée avec des DTMs version n, ne
doit pas être utililsée avec des DTMs version n-1 ou
antérieures.
2.3
Tableau 3: Fichiers STA sur l'ordinateur
|
Ouverture
fichier STA sur l’ordinateur |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec (4) |
Avec (4) (5) |
Avec (4) (5) |
Avec (4) (5) |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium /
Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium /
Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
NA : Non Applicable / sans objet (les fonctions de sécurité Quantum n'existent
que pour Unity Pro V3.1, V4.1 et V7.0).
Restrictions:
(1) Quand le fichier STA créé avec Unity Pro ≥ V5.1 contient
des sections LL984 l’application ne peut pas être ré ouverte par une version
d’Unity Pro inférieure.
(2) Quand l’application contient des écritures sur des variables
en lecture seule, le STA ne peut pas être ouvert, les corrections doivent être
apportées avant de créer le fichier d’archive STA
(3) Quand le fichier STA créé avec Unity Pro V7.0 contient des Bits extraits de
DDT l’application ne peut pas être ré ouverte par une version d’Unity Pro
inférieure
Quand le fichier STA créé avec Unity Pro Unity Pro V5.1, 6.0 or 6.1
contient des sections LL984 : voir chapitre 2.7
(4) La compatibilité descendante des
DTMs n’est pas garantie : une application créée avec des DTMs version n, ne
doit pas être utilisée avec des DTMs version n-1 ou antérieures.
(5) En raison d’une modification du format de
structures de module (ou Device DDT - voir liste
ci-dessous) , un fichier STA créé avec Unity V8.1 ne
peut pas être ouvert avec Unity Pro
V8.0. Les fichiers ZEF ou XEF peuvent être ouverts correctement.
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
Exemple : Une application de niveau V2.4 développée avec Unity pro V3.0 peut être
ouverte via le fichier STA avec un Unity Pro de version V5.0.
Note : Afin de permettre la modification en ligne de l’application
sans contrainte, Unity Pro conserve la version de bibliothèque de fonctions qui
a servi lors de la création de l’application.
Dans l’exemple, la version de bibliothèque V3.0 sera conservée lors de
l’ouverture du projet sur Unity Pro V5.0
2.4
Tableau 4: Fichiers STU sur l'ordinateur
Restrictions:
La compatibilité descendante des DTMs n’est pas
garantie : une application créée avec des DTMs version n, ne doit pas être
utilisée avec des DTMs version n-1 ou antérieures.
|
Ouverture fichier STU sur l’ordinateur |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
|
Application générée
avec |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
NO |
|
Application générée
avec |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
2.5
Tableau 5: Transfert Automate <=> PC
|
PLC
<=> PC |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
||||||||||
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
||||||||||
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
||||||||||
|
Quantum |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
||||||||||
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|||||||||
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
NA : Non Applicable / sans objet (les fonctions de
sécurité Quantum n'existent que pour Unity Pro V3.1, V4.1 et V7.0).
Restrictions:
(1) Quand l’application créée avec Unity Pro ≥
V6.0 contient des sections LL984, elle ne peut pas être transférée par une
version d’Unity Pro < V6.0.
(2) Quand l’application créée avec Unity Pro ≥
V6.1 contient des sections LL984 sur automate M340, elle ne peut pas être
transférée par une version d’Unity Pro < V6.1.
2.6 Tableau 6: Modification en
ligne
|
Modification en ligne |
Avec |
Avec Unity
Pro V3.0 |
Avec Unity
Pro V3.1 |
Avec Unity
Pro V4.0 |
Avec |
Avec Unity
Pro V5.0 |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
Avec |
|
Modicon M580 V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Modicon M580 V1.1x application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M580 V2.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
Modicon M580 V2.1 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Momentum Unity V1.0 application |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Premium / Quantum |
YES
(2) |
YES
(2) |
YES
(2) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES
(3) |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
YES |
YES
(2) |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
YES |
YES
(2) |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium / Quantum |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Premium |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
|
Quantum |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Modicon M340 |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
YES |
|
Modicon M340 |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
NO |
YES |
YES |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Quantum safety |
NA |
NA |
YES |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
YES |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
|
Quantum safety |
NA |
NA |
NO |
NA |
NO |
NA |
NA |
NA |
YES |
NA |
NA |
NA |
NA |
NA : Non Applicable / sans objet (les fonctions de sécurité Quantum
n'existent que pour Unity Pro V3.1, V4.1 et V7.0).
Restrictions :
(1) Quand l’application créée avec Unity
Pro V6.0 contient des sections LL984, elle ne peut pas être modifiée par une version
d’Unity Pro inférieure.
(2) L'ajout d'un nouveau type d'EFB dans
une application initialement créée avec une version précédente d’Unity Pro,
nécessite la mise à jour de la bibliothèque dans le projet (regénération
totale).
(3) La gestion automatique des bibliothèques,
apparue avec la version Unity Pro V4.0, gère toutes les bibliothèques de
fonction des versions antérieure jusqu'à la version V2.2.
Les applications créées avec
des versions V2.0 et V2.1 nécessitent la mise à jour de la bibliothèque de
fonction en V2.2 minimum pour assurer l’ajout de nouveau type d’EFB en ligne.
(4) La compatibilité descendante des
DTMs n’est pas garantie : une application créée avec des DTMs version n, ne
doit pas être utililsée avec des DTMs version n-1 ou
antérieures.
(information disponible en Anglais uniquement)
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 Unity V11.
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 8.1 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
8.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
Unity Pro V11, please uninstall Unity984Library before installing Unity Pro
V11.
If you have un-installed the Unity984 Library with already installed
Unity Pro V11, run the repair function of Unity Pro V11 to re-install the help
for the (now integrated) UnityLL984Library.
Des information additionnelles sont
disponibles sur Schneider-electric.com
(rubrique : Support
/ FAQ Frequently Asked Questions).
· Il est nécessaire d’installer la
mise à jour UnityPro_V110_HF1 pour pouvoir configurer des Quantum Remote EIO drops (140CRA31200) sur une plateforme M580
· To enable the configuration of Quantum EIO drop
(140CRA31200) on M580 Controller it is mandatory to install update
UnityPro_V110_HF1
· Quand M580 est configuré en NTP Client, après
une modification de l’adresse IP du Serveur NTP Primaire il est nécessaire de
« Régénérer Tout le Projet », afin que cette nouvelle adresse soit
prise en compte par l’automate (une génération simple ne suffit pas).
· Bien que Unity Pro ne signale aucune erreur lorsqu’un module BMENOC avec
version de logiciel < V2.05 est utilisé avec un M580 HSBY, une version de
logiciel V2.05 (ou supérieur) est obligatoire pour tout module BMENOC3x1
utilisé dans une configuration M580 HSBY.
La version de firmware BMENOC3x1 peut être
vérifiée dans le sous champ du DDT d’équipement (BMENOC0301_2.FIRMWARE_VERSION
= 16#0205),ou dans les pages web embarquées.
· Dans certains programmes Ladder
utilisant des instructions JUMP avec des processeurs M580 High End
BMEH ou BMEP 585040 / 6040, un
message d’erreur "Fail gcc compilation"
peut apparaitre lors de la génération.
Pour éviter ce problème, sélectionner l’option « Avec l’animation de
lien LD » dans l’option « Paramètres de génération » des Options
du Projet.
Regénérer l’application.
· Sur les processeurs M580 High End BMEH ou BMEP 585040 / 6040, a
message d’erreur "Fail gcc compilation"
peut apparaitre si une section ST utilise des assignations immédiates de
caractères dont la taille totale dépasse 4k octets.
Exemple
: MyStringVar := 'abcdef' ;
utilise 6 octets (1 par caractère)
MyStringVar1
:= 'abcdef'; MyStringVar2 := 'ghijklmnop' utilize 16 octets.
Pour éviter ce problème, séparer la section concernée en 2 (ou plus)
sections, afin que la taille des données dans chaque section soit inférieure à
4k octets.
· IPSEC sur BMENOC03x1 : Lorsque IPSec est
activé sur BMENOC03x1, les adresses IPA & IPB deviennent inactives.
Ce comportement est géré en interne dans le module NOC, et n’apparait pas dans
l’écran de configuration.
Seules les adresses IP Principale et Principale +
1 (sur HSBY) sont alors actives..
· Paramètrage par défaut du Port d’Embase BMENOC : Afin d'éviter une
possible surcharge réseau (Broadcast-storm), le port Ethernet de rack est maintenant
désactivé par défaut sur les BMENOC03x1.
Référez vous au guide d'utilisateur pour plus d’informations.
· Bouton "FDR sync" dans la DTM de la CPU
Hot Standby : Dans un système HSBY de redondance d'UC, les
serveurs FDR des BMENOC appairés sont automatiquement
synchronisés. Vous pouvez supprimer la synchronisation automatique en
désactivant ce service dans le DTM.
Si, pour une raison quelconque, vous souhaitez
resynchroniser manuellement les serveurs, vous pouvez le faire en appuyant sur
ce bouton.
Notez que la synchronisation automatique sera
alors réactivée, puisque c'est le mode de synchronisation recommandé.
· Installation en mode silencieux : l’installation peut être interrompue et
nécessiter une validation manuelle d’un écran lors du contrôle des pré requis
.NET. Pour éviter cette interruption : éditer install.bat et supprimer les
lignes :
:ver_dotnet_35
"%DIRMSI%\ISSetupPrerequisites\{074EE22F-2485-4FED-83D1-AAC36C3D9ED0}\dotnetfx35.exe" /s/q:a
· Lorsque un nouveau profil utilisateur est créé
dans Unity pro Security Editor
(exemple : MySuperProfile),
les utilisateurs associés à ce profil n’ont, par défaut, aucun droit d’édition
ni de modification sur les DTM. En conséquence il est impossible de
créer une nouvelle application M580.
Pour mettre à jour ces droits, il est possible
d’éditer et modifier un fichier de configuration .
Consulter la FAQ FA245141 disponible sur Schneider-electric.com (rubrique
Support >> FAQ)
· Une application M580 développée avec une CPU
V1.1 (créée avec Unity Pro V8.0 ou 8.1, ou 10.0) ne peut pas être upgradée vers CPU V2.0
: les versions de CPU ne sont pas compatibles entre elles et l’option
« Remplacer le processeur « n’est pas disponible.
Il est nécessaire d’exporter/exporter les
variables et le programme pour réaliser une nouvelle application
· Il n’est pas recommandé d’utiliser Unity pro avec Windows 8.1 sur virtual machine VMWare.
· Sur Windows Server
2012 il peut être nécessaire d’adapter la configuration Firewall
configuration pour qu’
OS Loader accède aux modules Ethernet (CRP31xxx ,
NOE77xx., NOC78xxx,, TSXETYxxx, ..) :
·
Utiliser la
configuration par défaut Windows 8.1 (check : notify when Firewall
block an app)
·
Vérifier que OS Loader est une app autorisée : Control Pannel > System and Security > Windows Firewall>
Allowed apps
· L’information suivante
concerne des applications M580 utilisant le module PRM compilées
avec Unity Pro V8.0
Lorsqu’on ouvre
un fichier archive STA d’une telle application, alors il est nécessaire de mettre
à jour la configuration de PRM GTW
DTM puis Régénérer tout le projet
Ouvrir le menu
Tools/ DTM Browser
Ouvrir PRM
GTW DTM et forcer une
modification :
Par exemple :
1. Modifier l’adresse MAC dans le dossier General Properties
et appuyer sur le bouton APPLY
2. Puis remettre
cette adresse MAC à sa précédente valeur et ré appuyer
sur le bouton APPLY
fermer PRM GTW DTM
Régénérer tout
le projet
· En raison d’une
modification du format des DDT d’équipement (voir liste ci-dessous) , un fichier STA créé avec Unity V8.1 ne peut pas
être ouvert avec Unity Pro V8.0. Les
fichiers ZEF ou XEF peuvent être ouverts correctement.
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
· Sur Windows 64 bits (Seven ou 8) certains drivers de communication peuvent ne
pas être visibles dans l’écran Unity V8.1 de connexion à l’automate. Pour
corriger ce problème il suffit de réinstaller le driver XIP.
· Sur certains PC le message suivant peut apparaitre lors
de l’installation de Unity V8.1 : “Mx80HARTGatewayDTM - 1.0…Error 1904. Module C:\Program Files..
\isCompanionATL.dll failed to register…
Ce message peut être ignoré.
L’installation se poursuivra correctement , et sans
erreur.
· Sur Windows 7 64
bits, ou Windows Server 2008 64 bits, le champ “Source IP field”
de la DTM peut dans certains cas être en mode « Lecture Uniquement »
et mis à sa valeur par défaut 127.0.0.1
Il est alors impossible de modifier
cette adresse, et donc impossible de ce connecter à
l’équipement.
Il est alors nécessaire de redémarrer
Unity Pro.
Le problem
est lié à un mauvais fonctionnement de la fonction « Windows 64 bits API
Network »
Microsoft a fourni une mise à jour.
Le problème est décrit dans l’article http://support.microsoft.com/kb/2588507/en
Microsoft
recommande de n’installer cette mise à jour que sur les ordinateurs ayant la configuration décrite et sur
lesquels le problème est rencontré.
·
Unity Pro nécessite Microsoft .NET 3.5. Selon la version du système Windows, et sa configuration,
il se peut que, .Net 3.5 soit :
-
non installé.
-
installé mais pas activé.
-
installé et activé.
Consulter le fichier Lisez Moi Unity Pro V8.1 pour plus de detail.
· Sur Windows 8 and 8.1, un redémarrage de
l’ordinateur est nécessaire après installation du driver
USB pour se connecter aux automates Momentum,
M580 or MC80. Ce redémarrage est nécessaire pour que la bonne
adresse IP soit mise à jour dans le driver.
· Il est
recommandé de ne pas utiliser la connexion Modbus Plus (avec Proxy TCSEGDB23F24A) pour télécharger une
application dans le M580. La connexion Ethernet serait perdue à la fin du
transfert, et ne pourrait pas être rétablie. L’automate devra alors être mis en
RUN en utilisant un autre driver de connexion (eg :
USB, direct Ethernet…) pour que la connexion puisse être rétablie
· NULL est un
mot clé réservé dans Unity pro V8.0 (initialisation des REFERENCES) . Une application réalisée avec un
version précédente de Unity Pro et contenant
une variable ou une section nommée NULL ne pourra pas être générée avec
Unity Pro (il faudra renommer NULL en NUL par exemple avant de générer)
· Si le driver
USB livré avec Unity Pro n,’est pas installé sur l’ordinateur, il est
recommandé de ne pas se connecter à l’automate par le port USB. En effet le système
d’exploitation Windows va installer automatiquement un driver USB par défaut, qui
ne permettra pas la connexion à l’automate. Dans ce cas il faudra désinstaller
le driver USB défectueux et réinstaller le driver USB livré avec Unity Pro (SchneiderPLCUSBDriverSuite.exe).
· Le simulateur d’automate Unity Pro peut ne pas fonctionner correctement
avec certaines application sur Windows Serveur 2008 et
Windows 8.1. Pour corriger le problème, il peut être nécessaire de modifier la
clef de registre suivante :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel "DisableExceptionChainValidation"=dword:00000001
·
L’utilisation de plusieurs
instances d’Unity Pro limite le nombre d’éditeurs ouvert simultanément à 15
pour la première session et à 6 éditeurs pour les suivantes.
Cette limitation, due à un paramètre de réglage Windows XP, peut être supprimée
en modifiant la base de registre comme indiqué ci-dessous :
-
Lancer l’éditeur de registre (Regedit)
-
Dans l’Editeur du Registre, recherchez la clé de registre suivante :
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems
-
Dans le volet droit de l’Editeur du Registre, Double cliquer sur le nom
Windows pour ouvrir la fenêtre de modification de la chaine.
-
Recherchez le paramètre SharedSection dans la
zone donnée de la valeur.
-
Note : Le paramètre SharedSection définit le
système et le bureau en utilisant le format suivant :
SharedSection=xxxx,yyyy,zzzz (Les valeurs sont
définies en kilobytes).
-
La seconde valeur SharedSection (yyyy) contrôle la taille de la zone mémoire (segment du
bureau).
Si la valeur de votre machine est yyyy
< 8192 alors mettre yyyy à 8192.
Sous Windows XP et quelques machines Windows Vista la
valeur est 3072 par défaut.
-
Le système doit être redémarré avant que les changements soient effectifs.
·
Mémoire application saturée
lors de la génération d’une application contenant des équipements DTM
Lorsque les informations d’Upload sont choisies
dans les options du projet, le code source du projet est chargé avec le code
exécutable lors du transfert du projet vers l'automate.
Le code source contient également la configuration DTM lorsqu'ils sont
utilisés.
Certains DTM peuvent utiliser une grande quantité de mémoire (essentiellement
les DTM génériques utilisés pour des équipements modulaires), conduisant à un
message d'erreur "mémoire saturée" lors de la génération.
Dans ce
cas, il est possible d'optimiser la mémoire de l'application:
-
En réduisant la taille de la mémoire de "Stockage des données"
pour augmenter la mémoire dédiée à l'application.
-
En ajoutant une carte mémoire ou en augmentant la taille de la carte
mémoire utilisée.
-
En réduisant la taille des informations de chargement en décochant les commentaires
et les table d'animation.
Si ces actions ne sont pas suffisantes, il faudra
désélectionner l'option "information chargement" afin de pouvoir
générer l'application correctement.
·
Information importante
sur l’utilisation du conteneur DTM
-
Le conteneur DTM est validé pour l’utilisation des DTM de Schneider
Electric associés aux offres PROFIBUS PRM (TCSEGPA23F14F et TCSEGPA23F14FK) et
Ethernet IP (140 NOC 77101, BMX NOC 0401 et TSX ETC 101).
-
Pour plus de détails, veuillez vous référer aux informations de la release
note relative à ces produits.
·
Port Mirroring:
Utiliser cette fonctionnalité uniquement pour le débogage, ne pas utiliser
en mode de fonctionnement normal. Dans des conditions de charge lourde, l’activation
du Port Mirroring peut avoir un impact sur la
connexion des E/S et en particulier pour le trafic DIO. Il est recommandé de
mettre hors-fonction le Port Mirroring en mode de
fonctionnement normal et d’utiliser les objets CIP pour activer ou désactiver
cette fonctionnalité si besoin.
·
Hot Standby : Cas où le
Standby PLC est en over run (dépassement de temps de
tâche)
Quand le PLC Standby est en overrun, il passe en état Run
Offline jusqu'à ce que la situation d'overrun se
termine. Un moyen de corriger ce problème est d'augmenter la période de la
tâche MAST du système.
·
Supprimer la DTM NOC de la configuration
Si la DTM NOC est connectée à un équipement, lorsque le
module NOC est supprimé de la configuration la DTM n'est pas automatiquement
supprimée. Il est nécessaire de déconnecter la DTM de l'équipement avant de la
supprimer.
·
Compatibilité descendantes des DTMs
La compatibilité descendante des DTMs n’est pas garantie : une application
créée avec des DTMs version n, ne doit pas être utililsée
avec des DTMs version n-1 ou antérieures.
·
Rack Viewers
Dans le cas ou un module 140NOE77101 est inséré dans un
rack local supportant une architecture EIO mais pas d'architecture S908, le rackviewer indique un coupleur S908 (140CRP93xxx) au lieu
d'un coupleur EIO (140CRP31200). Il identifie egalement
les drops EIO, mais aucune donnée n'est remontée a
l'utilisateur.
Le rackviewer des UC Quantum,
140NOE77101 et 140NOC7710X peut dans certains cas ne pas indiquer le module EIO
(140CRP31200).
Le rackviewer des UC Quantum,
140NOE77101 et 140NOC7710X n'identifie aucun rack distant sur S908 lorsque
l'operateur fait un click droit sur le coupleur CRP93xxx
· Import from Concept / ProWORX (information
disponible en Anglais uniquement) :
|
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 31st and/ or 32nd 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 by eliminated.
This may cause different variable to get the same name in Unity Pro (in case only 32nd 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 Analyze fails with "E1163 use of unconfigured direct address" when addresses more than
the maximum allowed are configured in the legacy application
Note
Quantum allows %M65280 as the highest 0x reference. This error will be observed
when the application is using an address that is more than allowed
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 Errors generated during build "The
instance is located on an address that isn't configured"
These type of
errors can be eliminated by reserving more memory words in the CPU State RAM
definition.
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 After import from Compact to M340, ADU-210
modules with inactive points are set to Used.
After the import, an ADU210 I/O point that was set to inactive will become an AMI0410 I/O
point with a default setting of +-10v and being active. As a workaround,
remove the "Used" checkbox for these channels manually to de-activate
the unused Channels.
o The TCP/IP IO Scanner information from a
Concept application may not get imported.
IO Scanner definitions of Concept originated
applications must be re-entered manually after import.
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.
o After import from Compact to M340, ADU-256
module replacement (BMXDDI1602) requires configuration
After importing a Compact application containing the ADU-256 module, it will be
replaced by BMXDDI1602 in the M340 and with topological addressing. The
addressing scheme should be manually changed to Mixed Topological addressing
after import.
· LL984 Editor (information disponible en Anglais
uniquement) :
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.