Beruflich Dokumente
Kultur Dokumente
2
- Release Notes Table of contents
1. System requirements ................................................................................................. 2
2. Process Expert System software installation ............................................................ 3
3. Process Expert System software licensing................................................................ 4
3.1. Licensing PES for the first time ............................................................................. 4
3.2. Updating PES licenses ........................................................................................... 5
4. Software compatibilities (software Participants) ...................................................... 5
4.1. Compatibility with Unity Pro V11.0...................................................................... 5
4.2. Compatibility with Vijeo Citect 2015 / V7.50 SP1 ............................................... 6
4.3. Compatibility with OFS V3.50 SP8 ...................................................................... 6
4.4. Compatibility with Advantys Configuration Software V8.0 ................................. 6
4.5. Compatibility with the automation platform firmware .......................................... 6
5. Targeted architectures ............................................................................................... 6
5.1. Hardware components supported ........................................................................... 6
5.1.1. Automation platform and embedded modules ................................................... 6
M580 Automation Platform ...................................................................................... 6
Quantum Automation Platform ................................................................................ 7
M340 Automation Platform ...................................................................................... 8
5.1.2. Remote and distributed I/Os............................................................................... 8
5.1.3. Fieldbus and networks........................................................................................ 8
5.1.4. List of devices configured and supported in PES .............................................. 9
5.1.5. Control network ................................................................................................. 9
5.2. Architectures and Scalability of the control system application............................ 9
6. New features in PES V4.2 ...................................................................................... 10
2. Recommendations / Main known issues ................................................................. 11
Topology ................................................................................................................. 12
Operation ................................................................................................................ 14
1. System requirements
The system requirements (hardware requirements and recommended operating system)
are dependent of the role of the machine: Server or client.
Due to various criteria to know the CPU performance, the required processor is defined
according to an average CPU mark given by PassMark(R) Software.
To check a CPU performance, for example for a Core i3 CPU, type passmark Core i3 in the
search engine of your Internet navigator to get the list of known processors and get the average
CPU mark for a selected one.
Workstation embedding the Process Expert System Server
System: processor with average CPU Mark: 5000 minimum
RAM memory: 8 GB minimum, 16 GB recommended
Hard disk: 250 GB / Fast disk 7200 rpm; format: NTFS file system and not FAT32
40 GB of free memory space on the hard disk is required to install and run the software
Recommended display: 1024-768 or more with true color 24-bit
Pointing device: mouse or compatible device
Operating system on the physical machine:
Windows Server 2012 R2 (recommended)
Windows 7 Pro or Windows 8.1 Pro 64-bit
Workstation embedding an Operation Server
System: processor with average CPU Mark: 3000 minimum
RAM memory: 4 GB minimum, 8 GB recommended
Hard disk: 80 GB (SSD recommended) / Fast disk 7200 rpm
Operating system on the physical machine:
Windows Server 2012 R2
Windows 7 Pro or Windows 8.1 Pro
Workstation embedding a Process Expert Engineering Client
System: processor with average CPU Mark: 3000 minimum
RAM memory: 8 GB minimum
Hard disk: 250 GB / Fast disk 7200 rpm; format: NTFS file system
Operating system on the physical machine:
Windows 7 Pro or Windows 8.1 Pro (recommended) 64-bit
Workstation embedding Process Expert Engineering & Operation Clients
System: processor with average CPU Mark: 3000 minimum
RAM memory: 8GB minimum
Hard disk: 250 GB / Fast disk 7200 rpm; format: NTFS file system
Operating system on the physical machine:
Windows 7 Pro or Windows 8.1 Pro (recommended) 64-bit
Workstation embedding a Process Expert Operation Client
System: processor with average CPU Mark: 2000 minimum
RAM memory: 3GB minimum
Hard disk: 250 GB / Fast disk 7200 rpm
Operating system on the physical machine
Windows 7 Pro or Windows 8.1 Pro
A mouse and a keyboard are required to use runtime navigation services on a workstation
embedding an Operation Client.
Disclaimer:
The correct mode of operation is obtained only with the software versions that are installed by
the PlantStruxure PES installer and following the above instructions.
Ticket
number
7439
12922
Description
User must have administrator rights on the computer to install and launch PES.
To avoid the request to provide the rights each time the software is launched,
please check the Windows User Control account settings and configure them
accordingly.
Some genies in the SGC Include2 require the installation of Microsoft form 2.0
(FM20.dll). The workaround consist in installing Microsoft ActiveX Control Pad
to obtain this dll. Non-exhaustive list of the concerned genies: sgc_client_10,
23329
23421
Link 2 was added manually in a former version of PES and removed during
generation in V4.1.
This use case is managed correctly when migrating a database from PES V4.1
to V4.2.
Following a migration of supervision project to PES V4.2, the user may face to
issues to build the supervision project. This is the consequences of changes in
the compilation rules in Vijeo Citect 2015 / V7.50.
For Global library and market/application libraries, the adaptations have been
done to fulfill to the new rules. Issues may occur for user defined templates.
In windows server 2012 R2, the below pop up appears while installing PES and
interrupts the installation.
PES V4.1 requires a license for each individual software component to operate.
Ordering PES part numbers leads to receiving an entitlement at the e-mail address that was
entered when placing the order. The entitlement file includes one or many activation IDs
corresponding to the licenses that were ordered.
To activate the licenses, proceed as follows:
3.2.
The installed base of PlantStruxure PES V3.1 / V3.1 SP1 and PES V4.0 / V4.0 SP1 / V4.1
requires updating the pool of installed licenses to run PlantStruxure PES V4.2. PES V4.2
licenses allow running former versions of PES, with a restriction for PES V4.0. The table below
gives the license compatibility for each version:
Installed
version
PES V3.1 or
PES V3.1
SP1
PES V4.0
PES V4.0
SP1
PES V4.1
PES V4.2
Licenses
required
V3.1 or V4.0
or V4.1 or
V4.2
V4.0 (*)
V4.0 or V4.1
or V4.2
V4.1 or V4.2
V4.2
(*) V4.1 & V4.2 licenses are not compatible with PES V4.0.
Two scenarios are possible to get the updated version of the licenses
1- A set of license updates has been ordered to cover the whole PES configuration. The
ordering process is the same as for a new license. It is required to provide the license ID of
each original license when ordering the corresponding update.
2- A service contract Gold or Gold Plus has been ordered
The update of existing licenses can be done through the PES Support PES Web site
(www.pes.schneider-electric.com). Proceed as follows:
-
Go to the PES Support Web site (you need to register on the portal to get access)
Post a request: Enter the activation ID and the e-mail address to receive the
update. It is required to submit a request for each unitary license.
Enter the license ID of the update you received by e-mail. The prerequisite is
having the full license corresponding to this license ID activated on this computer.
Press the Update button; the request is processed (connection to the software
licensing portal) and the license on the computer is updated: The version shown is
now V4.2. Alternative registration processes (by mail and through the software
licensing portal) are available also.
The system platform PES embeds the services to edit and operate the control program
by using Unity Pro V11.0 installed in a virtual machine, so Unity Pro standalone is not required.
PES V4.2 embeds PlantStruxure Unity Pro DTM library V3.4.16 and the two hot fixes:
Unity_Pro_V110_HF1 and Unity_Pro_V110_HF_PES_Adaptation on the top of Unity Pro.
Anyway, if you want to install Unity Pro V11.0 aside PES on the computer, refer to the
installation guide to proceed to the installation. In that case it is recommended to install the hot
fixes mentioned above and the same release of the DTM library as embedded in PES V4.2 to
be able to import projects from Unity Pro standalone in PES.
4.2.
Compatibility with Vijeo Citect 2015 / V7.50
SP1
The system platform embeds the services to edit and build the SCADA application by
using Vijeo Citect installed in a virtual machine. Nevertheless, for operation it is required to
install Vijeo Citect as well as the regular SCADA environment. It is mandatory to install Vijeo
Citect 2015 (V7.50) plus the Service Pack 1 (SP1) to run the SCADA project generated by
Process Expert System platform. Former versions of Vijeo Citect are not supported by PES
V4.2
4.3.
Vijeo Citect 2015 / V7.50 SP1 includes OFS 3.50 SP7. So installation of Vijeo Citect leads
to install OFS V3.50 SP7.
To benefit of the last updates, it is recommended to update OFS V3.50 SP7 with Service
Pack 8, which is available on the PES Support Web site.
4.4.
Compatibility with Advantys Configuration
Software V8.0
The system platform embeds the services to configure Advantys STB islands on
Ethernet through the Advantys Configuration Software (ACS) installed in a virtual machine. So
this configuration software is not required as standalone software.
4.5.
Compatibility with the automation platform
firmware
Except in case of migration of a PES V4.0 database, PES V4.1 embeds an updated set
of templates which allows you to benefit of the capabilities of the hardware abstraction layer
HAL 2.0. This set of templates allows engineering the program independently of the automation
platform and hardware modules that run the application. Some of these templates use the
ANY_BOOL data type, which requires a minimum version of the firmware of processors.
Minimum firmware version required for the CPU:
Modicon M580 standalone CPU (OS version equal or > V2.10 IR7)
Modicon M580 Hot standby CPU (OS version equal or > V 2.15)
Modicon Quantum (OS version equal or > V3.30)
Modicon M340 (OS version equal or > V2.70)
For more details, you can refer to the appendices of the Installation Guide.
5. Targeted architectures
5.1.
All modules compatible with the X80 I/O platform on Quantum are supported except the
following modules that cannot be configured by PES:
Communication modules:
BMX NOC 0402 (Ethernet MB/TCP & IP)
PMX NOW 0300 (Wi-Fi access point) It is ignored in the controller configuration, but
can be used in PES architectures
5.2.
Architectures and Scalability of the control
system application
The engineering configuration that is used to design the control system application can be
installed on a single workstation or on several engineering clients connected remotely to the
system server.
The typical control system application that can be designed with this release has the
following characteristics:
- 20 000 object instances (control modules) within the application.
- A controller supports 1000 object instances maximum (Quantum). An object
instance corresponds to the instantiation of an object template in the Application
Explorer.
The topology can support 50 control nodes (entities) with field busses and
networks. The supervision application can be distributed among 20 station nodes,
with standalone or redundant operation servers.
Architecture capabilities
10
Description
Runtime navigation services to the Ethernet module Web server work correctly
with the following version of the Ethernet module or later:
Minimum versions:
140 NOE 771 11: Version V5.1
Exe Version : 5.10
Kernel Version : 4.60
Web Server Version : 2.2.0
Web Page Version : 5.00
BMX NOE 110-2 :
Exe Version: 5.00
Kernel Version : 1.15
Web Server Version: 2.2.0
Web Pages Version: 5.00.08
Note: Various browsers may have different behaviors. In case of issue with the
navigation service after a change of the application, it is recommended to clear
the cache of the embedded explorer.
11
It requires connecting to the CPU module of the controller by using a USB cable. An alternate
method is also available.
Prerequisites:
- The configuration of the controller entity in the Topology Explorer matches the hardware in
terms of CPU module and communication modules.
- The IP addresses that you want to assign to the hardware are configured for the controller
entity.
1- Connect the USB cable to the PC running the engineering client and to the controller.
2- Right-click a built Control project executable and click Open Built Project.
3- In the menu of the Control Participant, click PLC->Set Address.
4- SYS and USB need to be displayed in the Address and Media fields of the PLC section
respectively (90.0.0.1 and TCP/IP can be used also for a USB connection).
5- Click Test Connection to verify that you can connect to the controller. Upon successful
connection, close the Set Address dialog box.
6- In the menu of the Control Participant, click PLC->Connect.
7- When the connection is established, click Transfer project to PLC.
This transfers the program, the configuration, and the IP addresses to the hardware.
NOTE:
- Do not use this procedure to perform the deployment of a built Control Participant project as
defined in the system engineering life cycle.
- If the hardware already has an IP address that you can connect to but you want to change it,
instead of using a USB connection, you can enter the current address in the Address field of
the Set Address dialog box and select the corresponding media. The rest of the procedure is
unchanged.
- If the built Control project is large, you can create an empty Control project in the Project
Explorer, create an executable, map it to the controller whose IP address you want to set
(service mapping), and build the Control executable. Select the Open Built Project command
from this executable instead.
For more information, refer to Accessing a PLC via a Network in the Help of the Control
Participant.
Topology
Ticket
number
9310/12214
18950
23016
Description
Changing the communication configuration (memory size for data exchanges in
the client ClientMemoryLength ) needs to be done carefully because the new
value entered is not checked for validity by PES.
An instance of a device template in a specific case of the $PM800EM template
must not be renamed.
Renaming an instance of a device management on Ethernet (Explicit
Messaging) and deploying the change may lead to not having the device
operating correctly or halt the controller.
To manage Quantum drop with an M580 controller, it is mandatory to configure
the IO vision through State Ram I/O data type for each module. But the status
bit of the module is not managed (set to true by PES), because the M580
doesnt manage the corresponding the system bits
If it is required to check module health, refinement must be done in the Control
project to replace the referenced variable "PES_CONST_TRUE" with the bit
address extracted from word Drop_x.IO_HEALTH_RACKx.(Y-1), which
corresponds to the slot Y where the module is located. Here after the data
structure associated to the two racks of a Quantum drop named DROP_1:
12
Project Explorer
Ticket
number
4912
9261
10373
10756
20966
21266
21303
Description
When a TeSys T instance is connected to an instance of the $Motor2 template,
the execution order of the blocks may not be correct. In such case, the logic of
the motor cannot be reset from the Supervision faceplate.
Solution: Refine the section and check the execution order of the F_TRIG block
in regard to MOTOR2 block; F_TRIG block needs to be executed after
MOTOR2 block.
When modifying the name of a program section online, the renamed section is
considered as a new one when the Control project is updated in PES.
Recommendation: Do not modify the section name when performing refinement
online but make the modification from the PES Project Explorer.
The modification done during the refinement is not detected in case of a
negation of the output pin of an object instance
Use case: Generate a project with an object instance having a graphical link
connected to the output. Then negate the output pin during refinement.
The consistency check does not detect the change and the next generation
does not revert the change to the original setting.
Dont rename sections generated by PES in refinement.
In such case, following a Generate and Build, a new section is created with
the new name and it contains the program of the original section. The section
with the old name still exists as empty.
Workaround:
Delete the section with the old name manually in a new session of refinement.
Management of settings in Vijeo Citect: Setting the language:
For VJC Base project: The user should set up the default language to be used
during Operation from the VJC Base Project if it is common to all Operator
Stations.
For Operator Stations: The user should set up the default language to be used
during operation from the computer setup if it is not same for all Operator
Stations.
In addition, the user should set up the startup code so that InitEvents code in
sgc_include2 is called. It could be called directly or as part of any other code
defined by the user and be started up when the client is started. Such
parameter could be set up from VJC Project Editor in the parameters of the
VJC Base Project (in case all Operator Stations need to execute identical code
on startup) or with Computer Setup as part of the Operator Station setup (in
case the startup code is not identical for all Operator Stations).
Refinement online of control projects, which impact program sections
containing SFC language, may require that the user has to stop the controller
to download the changes.
Adding an ActiveX control called _is FDT AboutBox Control in a Supervision
page causes the Virtual Machine sessions to stop working.
Recommendation:
Although it is listed in the Insert ActiveX Control dialog box, this entry is not a
valid ActiveX control. Avoid selecting this entry.
Moving sections from one Control Project to another is not supported in PES
13
21352
21466
21944
21983
22950
23351
Operation
Ticket
number
18869
18964
Description
Server internal exception during runtime navigation services (RTNS)
operation In some specific scenarios when user configures the PES
Operation Client to use the local VM (and not the VM of the system server), an
exception may be reported.
Runtime Navigation Services (RTNS): The user is able to write values in the
14
21989/22042
672
23415
animation table of a function block (for example, PV and SP for PID DFB) when
viewing a section in the Operation Client Viewer. The values are accepted by
the controller.
Stop/Start of a controller is possible when Unity Pro is opened in Monitoring
mode through the RTNS of PES.
Adjusting the timeout communication parameter between a controller and PES
(control participant/Unity Pro)
PES doesnt provide the service to adjust the communication parameters. In
case of this need (for example during commissioning a control project), go to
the Projects explorer, select the control project / executables. Select and Open
Build Project and modify the communication settings.
Communication between the supervision (with VJC 7.50/2015) using OFS 5.30
SP8 and a Tesys T through Ethernet MB/TCP (without a controller in between)
doesnt start.
Workaround:
OFS client must be launched by the user.
23249
Description
Problem when creating a genie facet template from a CTZ (include project)
constituent including another CTZ.
PES does not manage internal dependencies in Vijeo Citect in case of nested
include projects.
Workaround: When templatizing a genie which could require the use a nested
include project, in addition, the user needs to create, at least, one genie facet
using a genie of the nested include project and assign this genie to a page of
the Supervision Project. This way, the nested include project is added
automatically to the content repository.
Another alternative is to add such Include project manually in the
corresponding Supervision Project by using the Include Projects command.
PES doesnt allow to instantiate an object template containing several times the
same instance of a DFB. In such case, links between elements of the FBD
section generated (DFBs, EFs) may be lost and it leads to not be able to
generate the section.
Recommendation:
Dont create an object template with the same instance of a DFB several times.
15