Process Expert Software V4.

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

Compatibility / Hardware configuration ................................................................. 11

Connecting to controller before first deployment ................................................... 11

Topology ................................................................................................................. 12

Project Explorer ...................................................................................................... 13

Operation ................................................................................................................ 14

Template edition / libraries management ................................................................ 15

PSX PES V4.2 - Release Notes

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.

PSX PES V4.2 - Release Notes

2. Process Expert System software installation

It is recommended to first read the Installation Guide before proceeding with the
software installation. This document is located in the software delivery ISO file.
To browse the content of the ISO file, you have two possibilities:
1- Use a tool (for example: Daemon Tools v10) to mount the image file as a virtual drive.
2- Open the ISO by using a ZIP utility and extract to the computer or a hard drive.
It is recommended to use 7-Zip. You can download it at www.7-zip.org
PlantStruxure PES allows several types of configurations, from all-in-one on a single station to
distributed architectures on several stations. Refer to the Installation Guide (chapter 1: Process
Expert Infrastructure) to understand the possible roles of the workstations and the software that
needs to be installed on each machine. This chapter provides three examples of physical
architectures and describes the software components that need to be installed on each
workstation depending on its role. It is required to get two software deliverables (ISO files) to set
up PES on the workstations:
PlantStruxure PES V4.2 ISO files to install PES:
- System Server on the System Server station
- Engineering Client on the Engineering station
- Operation Client on the Operator station
Vijeo Citect 2015 / V7.50 SP1 ISO files to install PES on:
- Supervision Server on the Operation server station
- Supervision Client on the Operator station
Before installing PES V4.2, it is recommended to back up the database if you are
updating a previous version.
Migration of existing applications:
Applications that were designed with former versions of PES need to be migrated to the
new release in two steps, with a first step that must be done before uninstalling PES V4.1. The
second step must be done after the installation of V4.2. Refer to the installation guide for the
operating modes. If you experience difficulties during step 1 or step 2 of the migration (detected
errors messages), contact support. The migration procedure requires installing a migration
patch in PES V4.1 before starting step 1.
Post the database migration to V4.2, if you encounter a message that reads "Invalid Constraint
while processing your action" when editing an application, then contacts Customer Support.
If you want migrate a database from an older version (e.g. V4.0 SP1), you need to migrate the
database to PES V4.1 (it requires to install PES V4.1) before the migration to PES V4.2.
In the specific case of the migration of the database from a release earlier than V4.1, to
configure any application with an M580 controller, you need to import the templates
corresponding to the M580 controller hardware configuration. Refer also to the appendices of
the Installation Guide for additional information.
PES V4.2 no longer supports 32-bit Operating Systems. To migrate a PES V4.1 32-bit
database, refer to the Installation Guide for details.

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,

PSX PES V4.2 - Release Notes

sgc_iodev_10, sgc_m340_iodev_10, sgc_premium__iodev_10,

sgc_quantum_iodev_10.
Uninstalling the migration patch in PES V4.1 to migrate applications to V4.2
may lead to get a message as error during installation, but the un-installation
is done successfully. It occurs on a computer with Windows 8.1 only.
Take note that the Repair procedure leads to replacing the Virtual Machine
(VDI file) in any case on the computer.
Database migration:
If a link is created manually in a previous version of PES (for ex. V3.1,
V3.1SP1, V4.0, V40SP1) and it is migrated to V4.1 then the manually added
link is getting deleted after the first generation in V4.1. One of the reasons
could be that the section was not generated between V4.0 and V4.1 as there
was no change in templates impacting the respective facet. So, the next
generation happening for the impacted facet in V4.1 leads to removing the
graphical link now. It occurs specifically in the following scenario:

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.

Workaround: Click No in the pop up and Restart the installation again.

3. Process Expert System software licensing

3.1.

Licensing PES for the first time

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:

PSX PES V4.2 - Release Notes

1- Install the software (if not already done)

2- Open the Floating License Manager (FLM). A shortcut has been created on the desktop
during the installation of PES.
3- Activate; Select the preferred method to activate your software license :
by Web
Through the Software Licensing Portal on schneider-electric.com
By e-mail
For more information on licensing, refer to the Licensing Guide.

3.2.

Updating PES licenses

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)

Go to the License Generator

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.

Installation of the update through le Floating License Manager:

-

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.

4. Software compatibilities (software Participants)

4.1.

Compatibility with Unity Pro V11.0

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.

PSX PES V4.2 - Release Notes

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.

Compatibility with OFS V3.50 SP8

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.

Hardware components supported

5.1.1. Automation platform and embedded modules

M580 Automation Platform

PSX PES V4.2 - Release Notes

Standalone and redundant (New 4.2) controller configurations are supported

New processors and modules are configured with PES V4.2:
Processors for standalone configurations: BME P585040, BME P586040 in addition to
the other models already supported with PES V4.1.
Redundant configuration with M580 processors: BME H582040, BME P H585040, BME
H586040.
Redundant power supply BMX CPS4002.
Embedded switch BME NOS0300
BMX NRP 0200 / BMX NRP 0201 (EIO drop optical repeaters)
All modules compatible with M580 automation platform, including X80 I/O platform 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
The embedded communication routing capabilities in BMX NOC are not supported in
this release of PES.
Application specific modules:
BMX MSP 0200 (pulse train outputs)
BMX EAE 0300 (SSI encoder)
PME SWT 0100 (Scaime partner weighing module)
BMX EIA 0100 (AS-I V3 master) Can be configured through PES, but management
of AS-I devices must be done by project refinement (no ready-to-configure services to
manage devices)
BMEAHI0812 & BMEAHO0412 (Hart modules) They are configured through PES,
but require program refinement in addition to the hardware configuration and objects
Instantiation to use the other data than the process value. Refer to the application note
posted on the PES Support Web site to configure the modules with full features.
Quantum Automation Platform
All modules on Quantum Ethernet RIO drop or Quantum S908 RIO drop are compatible with
Quantum automation platform, except the following modules that cannot be configured by PES:
Communication modules:
140 NOC 771 01 (Ethernet IP)
140 NOM 2xx 00 (Modbus Plus)
140 NWM 100 00 (Web server Factory Cast)
140 ESI 062 10 (Ascii serial line)
140 EIA 921 00 (AS-I master)
140 PTQ PDP MV1 (Profibus master DPV1)
140 NPP 954 00 (Fiber optical repeater)
Application specific modules:

140 HLI 340 00 (High speed inputs)

140 MSB 101 00 (mono axis with encoder)
140 MSC 101 00 (mono axis with resolver)
140 MMS 425 01 (Sercos 66Mhz)
140 MMS 535 02 (Sercos 133Mhz)

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)

PSX PES V4.2 - Release Notes

PMX NOW 0300 (Wi-Fi access point) It is ignored in the controller configuration, but
can be used in PES architectures

Application specific modules:

BMEAHI0812 & BMEAHO0412 (Hart modules) They are configured through PES,
but require program refinement in addition to the hardware configuration and objects
Instantiation to use the other data than the process value. Refer to the application note
posted on the PES Support Web site to configure the modules with full features.
New modules for Quantum configurations configured with PES V4.2:
140 ERT 854 20 (time stamping),
BMX NRP 0200 / BMX NRP 0201 (EIO drop optical repeaters)
M340 Automation Platform
All modules compatible with the M340 automation platform, including in X80 I/O platform are
supported except the following modules that cannot be configured by PES:
Communication modules:
BMX NOC 0401/ 0401.2 (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
Application specific modules:
BMX MSP 0200 (pulse train outputs)
BMX EAE 0300 (SSI encoder)
BMX EIA 0100 (AS-I V3 master) Can be configured through PES, but management
of AS-I devices must be done by project refinement (no ready-to-configure services to
manage devices)
New modules for M340 configurations configured with PES V4.2:
BMX NRP 0200 / BMX NRP 0201 (EIO drop optical repeaters)
Premium controllers are not supported.

5.1.2. Remote and distributed I/Os

Remote I/Os:
Quantum: Quantum drops on S908, or Quantum drops on Ethernet RIO
Quantum, M580: X80 I/O platform and Quantum drops on Ethernet RIO (only for some M580
processors)
Distributed I/Os:
Quantum, M580 and M340: Intelligent remote stations through Peripheral Remote IO Adaptor
(PRA)
Advantys STB islands on Ethernet Modbus TCP.

5.1.3. Fieldbus and networks

Configuration and communication management of devices on Modbus Serial (NOM

module) in M580 & M340 local rack and M580 & Quantum x80 remote racks.
Configuration and communication management of devices on Ethernet Modbus TCP
(explicit messaging through function blocks) and Implicit messaging through Ethernet
I/O scanner.
Configuration of Profibus Remote Master (PRM) within PES

PSX PES V4.2 - Release Notes

5.1.4. List of devices configured and supported in PES

On Modbus serial:
Automation devices: ATV 12, ATV 32, ATV 312, ATV 61, ATV 71, TesysT, TesysU (5 models),
ATS 22, ATS 48, ATV212
Power devices: Compact NSX, Masterpact, Sepam 20, Sepam 40, Sepam 80, PM710, PM800,
PM1200, PM9, PM5350, SmartUPS,
Others: XPSMC
Communication management on Modbus serial through NOM module or through a gateway
Ethernet / Modbus serial.
On Ethernet MBTCP (implicit & explicit messaging):
Automation devices: ATV 61, ATV 71, Tesys T, ATV6xx, ATV9xx (new with PES V4.1)
Power devices: AccusineE, PM800, Compact NSX (New V4.2), Masterpact (New V4.2),
PM5320, PM5340 (New V4.2)
Template for generic device on Modbus/TCP
Communication management on Ethernet through NOE and NOC modules (refer to limitations
in support of communication modules in the previous paragraph).
On Profibus (through the Profibus Remote Master PRM):
Automation devices: ATV61, ATV 71, Tesys T (New V4.2)
Device profile for generic devices through two GSD files
Support of devices on CANopen bus in an Advantys STB island:
Tesys U, Tesys T, ATV31, ATV61, ATV71

5.1.5. Control network

Automation platforms (controllers) to SCADA communication: Ethernet Modbus/TCP

through PLC communication modules:
o NOE communication module or embedded communication port of the CPU, NOC
communication module for Quantum and M580, through a Network Interface
Communication (NIC) module for the SCADA.
- Single configurations and redundant configuration are supported (automation
platform and SCADA)
SCADA communication through OFS V3.50 SP8.
Connectivity from SCADA to devices through Modbus/TCP (New V4.2)
Communication through OFS V3.50 SP8 to exchange data between devices connected on
Ethernet MB/TCP with the supervision, or with devices on Modbus serial behind a gateway.

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.

PSX PES V4.2 - Release Notes

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

6. New features in PES V4.2

Redundant M580 controller.

Three models of processors.
Configurations with remote I/Os (x80) or distributed I/Os (Advantys STB).
Support of new hardware for M580.
New High End processor for M580 standalone configurations (model 5040
& 6040).
Embedded Switch NOS0300 in M580 (3 Ethernet ports embedded) to
reduce the footprint and simplify the cabling.
Support of redundant power supply for x80 racks.
Requires a specific backplane.
Support of new devices (new application templates).
Motion: motor starter Tesys T on Profibus DP.
Power management: circuit breakers Compact NSX and Masterpact on
Ethernet.
Communication between devices and Supervision (without any controller).
Communication through Ethernet Modbus/TCP through OFS installed on
the station node as supervision server; possibility to access to devices on
Modbus serial, through a gateway.
PES configures the communication between devices and the supervision.
Restricted access to controllers and events logging (Cyber security).
Restrict the access to the Ethernet networks through FTP / TFTP/ HTTP.
o Global for Quantum & M340.
o M580: Access Control List of IP@ enabled for each service.
Use of Internet Protocol Security (IPsec) services for communication
between an M580 controller and a station node (for example, a Supervision
node) that makes IP communication session private and secure.

PSX PES V4.2 - Release Notes

10

Traceability of events: Detection and log in a SYSLOG server of events

from a M580 controller and log activities issued from the Control Participant
on a controller (configuration, reboot, run/stop,).
Extended possibilities to make changes in objects.
Replace a template (works like an Update) while keeping the refinement
connected to the instance and the selected options of the instance, when
they are valid with the new template.
Easier navigation in a control program with a display of the containers (program
sections) according to the application tree.
The user has the choice: Flat list or filtered list of containers (new).
Object instances are instantiated in the application tree and the facets of
instances are assigned to containers (program sections).
Grouping of containers to match the application tree to facilitate the
navigation in the control project.
Improvement of performances when performing incremental changes in control
projects (new operating modes).
The build and deployment stages can be skipped to generate and deploy
changes directly in a controller during refinement when the controller
accepts them on-line.
The user has a new service to import Sections from Logical Project,
allowing to list the sections changed since the last deployment and update
only those that are selected.
Consistency Check runs only on the sections refined by users, and not on
the sections which are generated and not modified by users.
Migration of applications from V4.1 to V4.2.

2. Recommendations / Main known issues

Compatibility / Hardware configuration
Ticket
number
11334

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.

Connecting to controller before first deployment

Setting the IP Address of the CPU or Communication Module of a Controller
This procedure applies when the controller has no IP address or an address that is different
from the one configured for the controller entity in the Topology Explorer.

PSX PES V4.2 - Release Notes

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:

PSX PES V4.2 - Release Notes

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

PSX PES V4.2 - Release Notes

13

21352

21466

21944

21983

22950
23351

although not restricted. Doing so renders unusable Control projects.

Recommendation:
Do not move sections from one Control Project to another.
After importing a Control Project export file, if you need to rename a section in
the Projects Explorer, the following workaround needs to be followed; otherwise
generation does not complete.
Workaround:
After importing the Control project, User should perform a refine action before
performing the Generate or Generate and Build command.
During refine, it is not necessary to do any changes, simple refine and close
action on imported project is sufficient to avoid this issue.
Following the migration of the database from V4.0 to V4.0 SP1, the supervision
project may not be completed because multiple entries are found in the
Variable.DBF and Trend.DBF files.
Workaround:
Delete the duplicate entries manually
If user negates a Pin to which a Link / Binding is generated by PES, this will
lead of inconsistency and in next generation of the section (resulted due to any
facet in this section being Out of Date / Assigned and not generated state) will
lead to removal of the negation of pin.
User should ideally modify the template if they want the pin to treat the value
with negate value Or Unlink the facet to keep it inconsistent with PES
generated code.
Workaround:
Please use the NOT block in Unity Pro wherever you have used the negate pin
with the graphical link in the project.
Currently, PES does not allow performing some activities concurrently:
- Assigning facets of a same instance to a Control and Supervision
project.
- Generating of Control and Supervision projects for the same
instance.
Changing the area parameter value of an instance to blank (for example, from
1 to blank) in the Application Explorer is not propagated to genies referenced
by the instance, which are already assigned to a Supervision page when you
generate the Supervision project. You need to apply the change manually in
the properties of the genie by editing the page to which the genie is assigned
and double-clicking the genie.
For more information on the propagation of the area parameter, refer to the
Process Expert user Guide, chapter 13, section 13.1, topic Organizing the
System Application.
In some scenario of intensive activities running in parallel with the control
participant, Unity Pro may stop working unexpectedly in seldom cases
In Refine on-line, the reset of the property constant of a variable is not
working correctly through the Unity Pro data editor property window.
Workaround:
Set / reset the constant attribute of a data through the data editor spreadsheet

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

PSX PES V4.2 - Release Notes

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.

Template edition / libraries management

Ticket
number
11864

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.

PSX PES V4.2 - Release Notes

15