UnityPro V130 HF2 Readme PDF

UNITYPRO_V130_HF2
README
What is new with UnityPro_V130_HF2 ...................................................................................................... 2
Compatibility ................................................................................................................................................ 3
What to do after installation of UnityPro_V130_HF2 ............................................................................... 3
S_GUARD_LOCKING .................................................................................................................................. 5
comments of S_AIHA and S_DIHA ............................................................................................................ 6
S_MUTING_SEQ .......................................................................................................................................... 8
S_MUTING_PAR .......................................................................................................................................... 9
Modicon M580 safety CPU: BMEP582040S ............................................................................................. 10
UnityPro_V130_HF_BMENOP0300 Improvements ................................................................................. 10
UnityPro_V130_HF0435420R_Simulator_Windows10_v1709) .............................................................. 11
UnityPro_V130_HF_ENOC_UPGRADE_STEP2 ...................................................................................... 12
Notes ....................................................................................................................................................... 12
What is new with UnityPro_V130_HF_ENOC_UPGRADE_STEP2 ....................................................... 12
1- BMENOC03x1.4 supports slow Device/Gateways devices with MB scanner. ................................... 12
2 - BMENOC03x1.4 supports IP address assignment via BootP/DHCP server. .................................... 12
3 - BMENOC03x1.4 use a new DTM dataset not compatible with BMENOC03x1.2 or BMENOC03x1.3
DTM dataset. ........................................................................................................................................... 17
4 - Get the IP address used by the BMENOC03x1.4 module online. ..................................................... 17
5 - Management of IPA / IPB addresses for M580 PLC and BMENOC03x1.y modules. ....................... 18
6 - Update of M580 CPU clock with BMENOC0301/0311.4 NTP time from xbus. ................................. 18
7 - Support IP Secure (IPSEC) ............................................................................................................... 18
UnityPro_V130_HF1 .................................................................................................................................. 19
PEP0389578R M580 CPU Address Setting: Identifier doesn't accept "-" ............................................. 19
PEP0418945R FB display difference in FBD between Unity 8.1 and 12 .......................................... 19
PEP0424927R Properties for section LL994 change when opening ZEF file ................................... 20
PEP0425574R Unity pro crash after several Rebuild all ................................................................... 20
PEP0425608R ST language - JMP instruction after jump never executed ....................................... 21
PEP0426236R after DTM update on the computer ,DTM instances are not updated ...................... 21
PEP0427752R Variable name not displayed in LL984 network ............................................................. 21
PEP0427910R Free running control variable in FOR loop ................................................................ 22
PEP0429424R Animation issue on private variable of DFB .............................................................. 22
PEP0432754R Reopening the .STA project file isn’t possible ................................................................ 23
PEP0432500R UP V12.0 - Bug in Unity Pro ProWORX conversion ................................................. 23
PEP0436088R UP12, FOR loop doesn't work when JMP is programmed just after ........................ 24
PEP0437627R Data dictionary signature not updated upon bias change ....................................... 24
PEP0431497R Unity12-Nested DFBs do no inherit the “Exchange on STBY” data ......................... 25
UnityPro_V130_HF_DRA0815................................................................................................................... 25
Installation procedure ............................................................................................................................... 26
How to know which hot fix or updates are already installed? .............................................................. 26
Note: TüV certificate .................................................................................................................................. 26
Page 1 of 27
What is new with UnityPro_V130_HF2
This Hot Fix fixes the following issues (Quality Q), or brings additional features
(Enhancements E) as listed in table below.
Some had yet been released in previous Hot Fixes.
Q/E Fixed in Issue

Quality
Enhancement
previous Hot found on
Fix Unity Pro
Id Short description Version
Fix of S_GUARD_LOCKING DFB Q / V13.0
WARNING
UNEXPECTED BEHAVIOR OF THE APPLICATION
Do not use version V1.00 of function block

S_GUARD_LOCKING in your application.
Failure to follow these instructions can result in death,

PEP0445924R serious injury, or equipment damage.
Minor fixes on DFBs Q / V13.0
• S_AIHA
• S_DIHA
• S_MUTING_SEQ
/ • S_MUTING_PAR
Support new Modicon M580 safety CPU : E / /
/ BMEP582040S
On M580, the user can’t declare more than one E UnityPro_V130_ /
BMENOP0300 module with the IP Forwarding HF
configuration. BMENOP0300
And with a M580 HSBY the user cannot validate enhancements
/ the configuration with the address xx.xx.0.xx
Fix for: The following dialog box appears when Q UnityPro_V130_ V13.0
simulator is started: "Error allocating PAT HF0435420R_Si
memory space" mulator_Window
Condition are systematic using windows 10 s10_v1709
version 1709 and later versions and the
PEP0435420R simulator does not start.
Two new versions of communication modules E UnityPro_V130_ /
are now available: BMENOC0301.4 and eNOC_Upgrade
/ BMENOC0311.4. See description below _Step2
Modules BMXDRA0815 are not available in E UnityPro_V130_ /
/ Unity Pro DRA
M580 CPU Address Setting: Identifier doesn't Q UnityPro_ /
PEP0389578R accept "-" V130_HF1
FB display difference in FBD between Unity 8.1 Q V12
PEP0418945R and 12.
Properties for section LL994 change when Q V12
PEP0424927R opening ZEF file.
Q V12
PEP0425574R Unity pro closes after several Rebuild all,
ST language - JMP instruction after jump never Q V12
PEP0425608R executed.
Page 2 of 27
after DTM update on the PC,DTM instances are Q V12
PEP0426236R not updated in t.
Q V12
PEP0427752R variable name not displayed in LL984 network.
Q V12
PEP0427910R Free running control variable in FOR loop.
Q V12
PEP0429424R Animation issue on private variable of DFB.
Q V11.1
PEP0432754R Reopening the .STA project file isn’t possible
Q V12
PEP0432500R Bug in Unity Pro ProWORX conversion.
FOR loop doesn't work when JMP is Q V12
PEP0436088R programmed just after.
PLC datadic signature not updated upon bias Q V12
PEP0437627R change.
Nested DFBs do no inherit the “Exchange on Q V12
PEP0431497R STBY” data
See below for each issue:

• Description or behavior (before installation of UnityPro_V130_HF2)
• New behavior after installation of UnityPro_V130_HF2
• What to do after installation of UnityPro_V130_HF2
Compatibility
No compatibility break.
• Project done with Unity Pro V13.0 can be open and built (stu, sta or zef) with
Unity Pro V13.0 + UnityPro_V130_HF2
• Project done with Unity Pro V13.0 + UnityPro_V130_HF2 can be open and
built (stu, sta or zef) with Unity Pro V13.0
What to do after installation of UnityPro_V130_HF2

• UnityPro_V130_HF BMENOP0300 enhancements: A build of project is
required
• S_GUARD_LOCKING:
After opening .stu, or .sta files:
Update in project the S_GUARD_LOCKING DFB with the last
version (1.01) brought by HF2:
▪ Open the “Types Library Manager” tool
▪ Go to S_GUARD_LOCKING (in the application part)
▪ Select “Compare Project with Library “
▪ Then “Update All “
▪ perform a Rebuild All.
After opening .zef file: perform a Rebuild All.
• S_AIHA , S_DIHA , S_MUTING_SEQ, S_MUTING_PAR
Page 3 of 27
Update in project the DFB with the last version brought by HF2:
▪ Go to the DFB (in the application part)
Page 4 of 27
S_GUARD_LOCKING
To read carefully before integration of a
M580 Safety PAC using BMEP584040S CPU.
WARNING
UNEXPECTED BEHAVIOR OF THE APPLICATION
Do not use version V1.00 of function block

S_GUARD_LOCKING in your application.
Failure to follow these instructions can result in death,

serious injury, or equipment damage.
Use version V1.01 or a higher version of function block S_GUARD_LOCKING provided

by the UnityPro_V130_HF2 hotfix and by all Unity Pro XLS version > V13.0.
Description of the issue before HotFix installation:

if the entry UnlockRequest becomes true while the entry S_SafetyActive is false
then the output S_UnlockGuard becomes true (S_UnlockGuard has the value 1
despite the fact S-SafetyActive=0)
Green=1
Red=0
Description of the new behavior after HotFix installation:

The normal behavior, when the UnlockRequest input becomes true (the user
wants to open the door) is to keep the S_UnlockGuard output at false until the
S_SafetyActive becomes true.
Only after S_SafetyActive becomes true the S_UnlockGuard becomes true also.
Page 5 of 27
What must be done after HotFix installation (ie : rebuild all ,etc…)
After opening. stu, or .sta files:
Update in project the S_GUARD_LOCKING DFB with the last version (1.01)
brought by HF2:
• Open the “Types Library Manager” tool
• Go to S_GUARD_LOCKING (in the application part)
• Select “Compare Project with Library “
• Then “Update All “
• perform a Rebuild All.
comments of S_AIHA and S_DIHA

ISSUE: the comments describing the two DFB S_AIHA and S_DIHA are inverted
as shown below:

NO CHANGE IN BEHAVIOR: only the two comments have been changed while the
code of both modules stays the same.
Page 6 of 27
Page 7 of 27
S_MUTING_SEQ
Wrong DiagCode following a sequence error caused by MutingEnable=false: If a

wrong muting sequence happens because the MutingEnable input is false, then
the error code which is presented on the diag output hasn’t the second digit of
the error code set to the value ‘F’ .
In the example below the DiagCode shows C114 instead of CF14 when
MutingEnable was set to false in the state 8011.
Right Diag Code is displayed
Page 8 of 27
S_MUTING_PAR
This module is used to verify the correct entry of transported material into a
danger zone which is protected by a light curtain (Active Opto-electronic
Protective Device).
while material is returning from the danger zone (backward sequence), if the light
curtain is cut while one single sensor is pressed (so while in any of the four
states 8122, 8422, 8114 or 8414), then the module eventually reaches an
incorrect state where it stays definitely stuck while its outputs show the following
constant values:
- 16#8000 on the the diag port,
- False on the S_AOPD_Out output
- False on the Error output
- True on the Ready output
The only way to get out of this inconsistent state is to put the entry Activate to
false, which resets its internal data and puts it back in service.

The module will behave normally
Page 9 of 27
Modicon M580 safety CPU: BMEP582040S

Description of behavior (before installation of UnityPro_V130_HF2)
BMEP582040S are not available in Unity Pro.
New behavior after installation of UnityPro_V130_HF2)

BMEP582040S are available in Unity Pro.
Note: above documentation has been adapted but it is not available in Unity Pro On Line
Help.
• Modicon M580 Safety System Planning Guide
• Modicon M580 Safety Manual
• Unity Pro Safety Block Library
Documentation is available in pdf format on Schneider-Electric.com (in English

language only)
• Modicon M580, Safety Manual: https://www.schneider-
electric.com/en/download/document/QGH46982
• Unity Pro - Safety Block Library: https://www.schneider-

• Modicon M580, Safety System Planning Guide: https://www.schneider-

UnityPro_V130_HF_BMENOP0300 Improvements
Description of issue or behavior (before installation of

UnityPro_V130_HF_BMENOP0300 Improvements)
Page 10 of 27
• On M580, the user can’t declare more than one BMENOP0300 module
with the IP Forwarding configuration.
• with a M580 HSBY the user cannot validate the configuration with the
address xx.xx.0.xx
New behavior after installation of UnityPro_V130_HF_BMENOP0300

Improvements
• On M580, user can declare more than one BMENOP0300 module with the
IP Forwarding configuration.
Note: limitation is unchanged with BMENOC0321. This Hot Fix is only
related to BMENOP0300
• With a HSBY CPU user can validate the configuration with the address
xx.xx.0.xx
• Note : IP forwarding improvement is only supported with BMENOP0300

Firmware version V2.0
What to do after installation of UnityPro_V130_HF_BMENOP0300 Improvements
A build of project is required
UnityPro_V130_HF0435420R_Simulator_Windows10_v1709)
Description of issue or behavior (before installation of

UnityPro_V130_HF0435420R_Simulator_Windows10_v1709)
The following dialog box appears simulator is started: "Error allocating PAT
memory space"
Condition are systematic using windows 10 version 1709 and later versions
and the simulator does not start.
New behavior after installation of

UnityPro_V130_HF0435420R_Simulator_Windows10_v1709
No error message, and Simulator starts
What to do after installation of

UnityPro_V130_HF0435420R_Simulator_Windows10_v1709
Rebuild all application for simulator
Page 11 of 27
UnityPro_V130_HF_ENOC_UPGRADE_STEP2
Notes
In M580ApplicationUpdate tool, conversion from BMENOC03x1.3 to
BMENOC03x1.4 cannot be done if M580 CPU version is < V2.30. It is OK on
V2.30 and superior.
CIP request to read status from M580 CPU must not be used in M580 HSBY
configurations.
NOTICE
UNEXPECTED APPLICATION BEHAVIOR
If CIP request is used it may cause a temporary drop loss when

transferring project to HSBY Standby controller.
CIP request to read status from M580 CPU must not be used in M580
HSBY configuration.
Failure to follow these instructions can result in equipment damage.
What is new with UnityPro_V130_HF_ENOC_UPGRADE_STEP2
Two new of communication modules are now available: BMENOC0301.4 and

BMENOC0311.4.
Characteristics of those modules are:
1- BMENOC03x1.4 supports slow Device/Gateways devices with MB scanner.
This feature is implemented in the DTM. DTM supporting slow Device/Gateways

devices with MB scanner is installed with the Hot Fix .
2 - BMENOC03x1.4 supports IP address assignment via BootP/DHCP server.
Get the IP address of the BMENOC03x1.4 from DHCP / BOOTP server for
standalone PLC system.
• On the configuration screen of BMENOC03x1.4, a drop down box called
configuration is added allowing to choose one of the following values:
Static, DHCP, BOOTP.
• If Static is selected, all IP addresses can be configured by the user as
described below:
Page 12 of 27
• If DHCP is selected, a new disabled text field called DHCP Identifer display
the identifier defined in the Ethernet Network Manager for the
BMENOC0301/0311.4 module.
The default value of DHCP Identifier is generated as below:

 Backplane Head ID_ slot location_module type ID
 e.g: using the M580 CPU backplane head ID with value 10: ‘010M_02_NOC0311’
 e.g: using the M580 HSBY CPU A backplane head ID with value 10: ‘010A_02_NOC0311’
 e.g: using the M580 HSBY CPU B backplane head ID with value 10: ‘010B_02_NOC0311’
If DHCP identifier is blank, then the DHCP request will use the MAC address as ID.
The Main IP address is used to set the Default IP address in case of the
BMENOC03x1.4 cannot succeed to get the IP address from the DHCP server.
If DHCP is selected, Unity Pro will check that the Main IP address respect the
following format:
 10.10.MAC5.MAC6
• If Static or BOOTP is selected, the Text field DHCP Identifier is not editable
by the user (grayed)
Page 13 of 27
• If DHCP is selected, only the Main IP address can be configured by the
user as described below:
Page 14 of 27
If BOOTP is selected only the Main IP address can be configured by the user as
described below:
The Main IP address is used to set the Default IP address in case of the
BMENOC03x1.4 cannot succeed to get the IP address from the BOOTP server.
If BOOTP is selected, Unity Pro will check that the Main IP address respect the
following format:
 10.10.MAC5.MAC6
Page 15 of 27
Ethernet Network manager:
A new column called "Configuration Mode" with read only access is added in the
Ethernet Network manager.
Page 16 of 27
On DHCP and BOOTP configuration mode:
• In "IP Address" column, Main, A and B IP addresses are displayed like this:
o Main: 10.10.MAC5.MAC6
Gateway address is the IP defined in the screen of the NOC.
On DHCP configuration mode, "Identified By" column is initialized with the "Device
Name". The identifier is in read only and the identifier is editable in the screen of
the NOC
3 - BMENOC03x1.4 use a new DTM dataset not compatible with BMENOC03x1.2 or

BMENOC03x1.3 DTM dataset.
A converter will allow replacing BMENOC03x1.3 by BMENOC03x1.4
4 - Get the IP address used by the BMENOC03x1.4 module online.
When Unity Pro is connected to the M580 PLC, the IP address, the subnet mask
and the gateway address used by the BMENOC03x1.4 module are displayed in the
Debug screen:
This debug screen shall display the IP parameters in all following modes:
 Static
 DHCP/BOOTP
Page 17 of 27
 Default IP
 Current IP parameters defined by application
5 - Management of IPA / IPB addresses for M580 PLC and BMENOC03x1.y modules.
IPA and IPB are removed from the screen of BME NOC 0301.4/311.4
6 - Update of M580 CPU clock with BMENOC0301/0311.4 NTP time from xbus.
When M580 CPU clock is updated with the BMENOC0301/0311.4 NTP time by xbus,
Unity Pro must check that it is the unique NTP source configure in the application.
During the build of the application, if more than one NTP source is enabled in the
application, the following error is displayed in the output windows: More than one
NTP source is enabled. Please choose the unique NTP source you want to use to
manage time.
7 - Support IP Secure (IPSEC)

IPSecure communication can be configured with BMENOC0301/0311.4
Page 18 of 27
UnityPro_V130_HF1
PEP0389578R M580 CPU Address Setting: Identifier doesn't accept "-"
1/ Description of the issue before HotFix installation:
With M580, It is not possible to write “-“ in the DHCP identifier.
2/ Description of the new behavior after HotFix installation
With M580, It is possible to write “-“ in the DHCP identifier.
3/ What must be done after HotFix installation (ie : rebuild all ,etc…)
nothing
PEP0418945R FB display difference in FBD between Unity 8.1 and 12

The issue occurs in FBD language when importing on Unity Pro V12.0 (or later
version) a FBD section built on Unity Pro V11.0 (or previous version).
Issue description : For a function bloc (ie : FB1), the size of this Function Bloc (FB1)
after import is not the same as the size of the same function bloc (FB1) created
directly with Unity Pro V12.0

The issue no more occurs .
Now, in FBD language when importing on Unity Pro V12.0 (or later version) a FBD
section built on Unity Pro V11.0 (or previous version), for a function bloc (ie : FB1), the
size of this Function Bloc (FB1) after import is now the same as the size of the same
function bloc (FB1) created directly with Unity Pro V12.0
user have to re-import the section after HF installation to solve the issue
Page 19 of 27
PEP0424927R Properties for section LL994 change when opening ZEF file
1/ Description of the issue before HotFix installation

If a project contains sections which have ONE Remote IO associated (either Read or
Write), and the customer exports, imports, and then builds, Build fails.

With this kind of project, after import, then the Build succeeds.
Nothing mandatory to do.
If customer has ZEF files containing sections with one Remote IO Drop configured,
he can now build them successfully.
PEP0425574R Unity pro crash after several Rebuild all

Issue linked with the project setting “Program Viewer Information”. Unity Pro can crash
after a BUILD action (during the generation of the information for the program viewer)

When the project setting “Program Viewer Information” is enabled, and a build action is
performed, no crash for UnityPro
Launch again UnityPro with the HotFix installed.
Page 20 of 27
PEP0425608R ST language - JMP instruction after jump never executed

The code of the FB instance right after the LABEL is not executed when PLC execution
goes through the JMP instruction
JMP Label1
….
Label1: MyTimerInstance(…);

The code of the FB instance right after the LABEL is executed when PLC execution
goes through the JMP instruction
The program section having the JMP instruction must be re-compiled
The best solution is to perform a full application build (Build All)
PEP0426236R after DTM update on the computer ,DTM instances are not
updated
- PEP0426236R: in an application, in case there are two different DTM instances with a
different dataset version, the tool was detecting only one instance (the first one). So, in
case the second DTM instance was not supported on the computer, the user could not
see the problem.
- Fix PEP0426236R: the tool now displays properly all the DTM instances of the
application.
- Improvement: the tool now displays not only DTM information but also Device
information. This allows to easily show when a EDS/GSD file is missing from the
configuration. Previously the tool was showing that the DTM was not installed, this was
actually not true since the DTM was property installed but not the EDS/GSD file.
Nothing
PEP0427752R Variable name not displayed in LL984 network

- Open the customer sta application : case 41029424.sta
- Open the section named 'Pump_5_GM_7I_remote_start_sto_14'
- Try changing the views (Ctrl+W)
 Variables names on contacts are not displayed. We see their %Mx address instead of
name
Page 21 of 27
- Try changing the views (Ctrl+W)
 Variables names on contacts are displayed, according to the view1-2-3-4 project settings
Nothing to do on the customer application.
PEP0427910R Free running control variable in FOR loop

If there is a Label just before the FOR statement, the FOR statement goes in infinite loop
and keeps running without stopping when PLC execution goes through the JMP
instruction
JMP Label1
….
Label1:
FOR Index :=1 TO 10 DO
….
END_FOR;

The FOR statement runs as expected.
Solution is to perform a full application build (Build All)
PEP0429424R Animation issue on private variable of DFB

Open STA:« case_41683267.auto.sta>>
Build, download application into simulator, and run
Open section containing DFB instance
Do a refine on the instance of the DFB
We see #Err!# instead of the values, on DFB pins
Page 22 of 27
Do a refine on the instance of the DFB
We see the current values, on DFB pins
Nothing to do on the customer application.
PEP0432754R Reopening the .STA project file isn’t possible

Create new M580 application
Add CXM
Rebuild
Add a CANOpen device + change function
Build changes
Save STA
Open STA: FAILED

Create new M580 application
Add CXM
Rebuild
Add a CANOpen device + change function
Build changes
Save STA
Open STA: SUCCEED
If a STA cannot be opened, open the corresponding ZEF and rebuild it.
PEP0432500R UP V12.0 - Bug in Unity Pro ProWORX conversion

After Import of a converted Proworx32 project which contains a DDM16025 module, if
the user double click on this module, this will lead to a UnityPro crash.
Page 23 of 27
After Import of a converted Proworx32 project which contains a DDM16025 module, if
the user double click on this module, this will not lead to a UnityPro crash.
need to re-open the Proworx32 project (it will re-convert and re-import it)
PEP0436088R UP12, FOR loop doesn't work when JMP is programmed just
after

- Inside a FOR statement use a JMP with label just before the END_FOR statement (PLC
execution goes out of the FOR loop)
- Inside a WHILE statement use a JMP with label just before the END_WHILE statement
(PLC execution goes out of the WHILE loop)
- Inside a CASE statement use a JMP with label just before the next value test (PLC
execution continues to the next case value)
Index :=2;
%MW1:=0;
%MW2:=0;
CASE Index OF
2:
%MW1:=2;
JMP LABEL1;
%MW2:=2;
LABEL1:
3:
%MW1:=3;
END_CASE;

The program is executed as expected.
Solution is to perform a full application build (Build All)
PEP0437627R Data dictionary signature not updated upon bias change

For the variables not embedded in the data dictionary, when
Page 24 of 27
- renaming these variables, or
- relocating these variables, or
- delete these variables, or
- changing the type of these variables,
this will lead to a SCADA issue : animation is stopped

For the variables not embedded in the data dictionary, when
- renaming these variables, or
- relocating these variables, or
- delete these variables, or
- changing the type of these variables,
this will not lead to a SCADA issue : animation is not stopped
Rebuild all
or
If the process cannot be stopped: Force the generation of data dictionary, (doing for
example : remove it from project settings and build changes application, and put it
again in project settings and build changes application)
PEP0431497R Unity12-Nested DFBs do no inherit the “Exchange on STBY”

data

Nested DFB RTE is listed (in Binary, not visible by customer) to be exchanged on HSBY
when parent is set explicit not to be.
Customer vision: If the customer choose not to exchange on HSBY a DFB father, his
nested DFB is still exchanged.
2/ Description of the new behavior after HotFix installation:

Nested DFB RTE is not listed (in Binary, not visible by customer) to be exchanged on
HSBY when parent is set explicit not to be.
Customer vision : If the customer choose not to exchange on HSBY a DFB father, his
nested DFB is not exchanged.
Rebuild all must be performed after HotFix installation.
UnityPro_V130_HF_DRA0815
Description of behavior (before installation of UnityPro_V130_HF2)
Page 25 of 27
Modules BMXDRA0815 are not available in Unity Pro.
New behavior after installation of UnityPro_V130_HF2)

Modules BMXDRA0815 are available in Unity Pro.
Note: Online Help
UnityPro_V130_HF_Multilanguages_Online_Help should be installed prior

to UnityPro_V130_HF_DRA0815
Note: If UnityPro_V130_HF_Multilanguages_Online_Help is installed after
UnityPro_V130_HF_DRA0815, then On Line Help updates for DRA0815 will
be lost.
On Line Help updates for DRA0815 are in English language only : after
installation of UnityPro_V130_HF_DRA0815, the On Line Help for X80
modules (chapter "Modicon X80 Discrete inputs outputs" will be in English
Only.
Multilanguage On Line Help will be updated in next Unity Pro release (V13.1
planned Q3 2018).
Installation procedure
• Download attached file on your computer.
• Prior to installation make sure Unity Pro is closed.
• Run UnityPro_V130_HF2 to install the update
UnityPro_V130_HF2 can be installed over Unity V13.0

Versions:
S ☒ L ☒ XL ☒ XLS (*) ☒
(*) see notice below
How to know which hot fix or updates are already installed?

Open Unity Pro, click on “Help”, “about Unity Pro” and “Technical
Information”:
The list of installed hot fixes is displayed.
Note: TüV certificate

Before installing this Hot Fix on Unity Pro V13.0 XLS version, and generate
Safety projects, you must check the TüV certification status on web site:
Page 26 of 27
Go to : https://www.tuvasi.com/
Select « Certification Database »
Search for SCHNEIDER ELECTRIC certificate 01/205/5610/00/17
(Safety-related Programmable Electronic System - M580 Functional Safety
Controller System)
Select “View Details”
Open revision list in Appendixes and check that UnityPro_V130_HF2 is part of
the list.
Page 27 of 27

UnityPro V130 HF2 Readme PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UnityPro V130 HF2 Readme PDF

Uploaded by

Copyright:

Available Formats

UNITYPRO_V130_HF2

Q/E Fixed in Issue

UNEXPECTED BEHAVIOR OF THE APPLICATION

Do not use version V1.00 of function block

Failure to follow these instructions can result in death,

See below for each issue:

What to do after installation of UnityPro_V130_HF2

After opening .zef file: perform a Rebuild All.

• S_AIHA , S_DIHA , S_MUTING_SEQ, S_MUTING_PAR

After opening .zef file: perform a Rebuild All.

UNEXPECTED BEHAVIOR OF THE APPLICATION

Do not use version V1.00 of function block

Failure to follow these instructions can result in death,

Use version V1.01 or a higher version of function block S_GUARD_LOCKING provided

Description of the issue before HotFix installation:

Description of the new behavior after HotFix installation:

After opening .zef file: perform a Rebuild All.

comments of S_AIHA and S_DIHA

Description of the new behavior after HotFix installation:

After opening .zef file: perform a Rebuild All.

Description of the issue before HotFix installation:

Wrong DiagCode following a sequence error caused by MutingEnable=false: If a

Description of the new behavior after HotFix installation:

Right Diag Code is displayed

Description of the issue before HotFix installation:

Description of the new behavior after HotFix installation:

After opening .zef file: perform a Rebuild All.

Modicon M580 safety CPU: BMEP582040S

BMEP582040S are not available in Unity Pro.

New behavior after installation of UnityPro_V130_HF2)

Documentation is available in pdf format on Schneider-Electric.com (in English

• Unity Pro - Safety Block Library: https://www.schneider-

• Modicon M580, Safety System Planning Guide: https://www.schneider-

Description of issue or behavior (before installation of

New behavior after installation of UnityPro_V130_HF_BMENOP0300

• Note : IP forwarding improvement is only supported with BMENOP0300

What to do after installation of UnityPro_V130_HF_BMENOP0300 Improvements

A build of project is required

Description of issue or behavior (before installation of

New behavior after installation of

What to do after installation of

If CIP request is used it may cause a temporary drop loss when

Failure to follow these instructions can result in equipment damage.

What is new with UnityPro_V130_HF_ENOC_UPGRADE_STEP2

Two new of communication modules are now available: BMENOC0301.4 and

1- BMENOC03x1.4 supports slow Device/Gateways devices with MB scanner.

This feature is implemented in the DTM. DTM supporting slow Device/Gateways

2 - BMENOC03x1.4 supports IP address assignment via BootP/DHCP server.

The default value of DHCP Identifier is generated as below:

Gateway address is the IP defined in the screen of the NOC.

3 - BMENOC03x1.4 use a new DTM dataset not compatible with BMENOC03x1.2 or

A converter will allow replacing BMENOC03x1.3 by BMENOC03x1.4

4 - Get the IP address used by the BMENOC03x1.4 module online.

7 - Support IP Secure (IPSEC)

2/ Description of the new behavior after HotFix installation

With M580, It is possible to write “-“ in the DHCP identifier.

PEP0418945R FB display difference in FBD between Unity 8.1 and 12

1/ Description of the issue before HotFix installation:

2/ Description of the new behavior after HotFix installation

1/ Description of the issue before HotFix installation

2/ Description of the new behavior after HotFix installation

PEP0425574R Unity pro crash after several Rebuild all

1/ Description of the issue before HotFix installation