Schneider Electric EcoStruxure Hybrid DCS 2018 Platform User Guide
Schneider Electric EcoStruxure Hybrid DCS 2018 Platform is a powerful and versatile automation platform that can be used in a wide variety of applications. It offers a number of features and benefits that make it an ideal choice for users looking for a reliable and efficient way to manage their automation systems. Some of the key features of the platform include:
Advertisement
Advertisement
EcoStruxure Hybrid DCS 2018 R2
- Platform Release Notes –
8.1.2.
8.1.3.
8.1.4.
9.
10.
10.1.
10.2.
10.3.
10.4.
10.5.
10.6.
10.7.
Table of Contents
New Features in EcoStruxure Hybrid DCS 2018 R2 ......................................................... 2 1.
1.1.
1.2.
1.3.
1.4.
1.5.
2.
3.
3.1.
4.
4.1.
5.
5.1.
Improved user interface functionality: ................................................................................ 2
Performance and productivity improvements in the engineering of Supervision
Participant projects: ........................................................................................................... 2
Schneider Electric license management and the database management software are upgraded for increased cybersecurity. .............................................................................. 2
Support for running Hybrid DCS in a virtualized (VMware ESXi) environment ................. 2
Foundation and Global Templates .................................................................................... 2
EcoStruxure Hybrid DCS 2018 R2 System Requirements ............................................... 2
EcoStruxure Hybrid DCS 2018 R2 Installation .................................................................. 3
5.2.
5.3.
6.
6.1.
6.2.
7.
7.1.
7.2.
7.3.
Additional Information Related to the Installation .............................................................. 3
EcoStruxure Hybrid DCS 2018 R2 Software Licensing .................................................... 4
Licensing EcoStruxure Hybrid DCS 2018 for the First Time ............................................. 4
First Installation or Upgrade of Process Expert 4.3/SP1.................................................... 5
Overview ............................................................................................................................ 5
Prerequisites to Migrate a Database of a Supported Earlier Version ............................... 5
Getting Started .................................................................................................................. 5
Upgrading EcoStruxure Hybrid DCS 2018 ........................................................................ 7
Overview ............................................................................................................................ 7
7.4.
7.5.
7.6.
8.
8.1.
Getting Started .................................................................................................................. 7
Software Compatibility with Participants ........................................................................... 8
Compatibility with Unity Pro V13.0 .................................................................................... 8
Compatibility with Citect SCADA 2016 .............................................................................. 8
Compatibility with OFS V3.60 SP4 .................................................................................... 8
Compatibility with Advantys Configuration Software V11.0 .............................................. 8
Compatibility with the Automation Platform Firmware ....................................................... 8
Configuration Limitation of Ethernet modules for M580 High End CPU (40, 50, 60) ........ 8
Targeted Architectures ...................................................................................................... 9
Hardware Components Supported .................................................................................... 9
8.1.1. Automation platform and embedded modules .................................................................. 9
8.1.1.1. M580 Automation Platform ................................................................................................ 9
8.1.1.2. Quantum Automation Platform ........................................................................................ 10
8.1.1.3. M340 Automation Platform .............................................................................................. 11
Fieldbus and networks .................................................................................................... 11
List of devices configured and supported in EcoStruxure Hybrid DCS ........................... 12
Control network ............................................................................................................... 12
Enhancements and Fixed Issues Included in this Release ............................................. 13
Recommendations and Known Issues ............................................................................ 14
Systems Management ..................................................................................................... 14
Application Explorer......................................................................................................... 14
Topology .......................................................................................................................... 14
Project Explorer ............................................................................................................... 15
Operation ......................................................................................................................... 17
Template Edition / Library Management ......................................................................... 19
Installer ............................................................................................................................ 19
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 1 of 21
1. New Features in EcoStruxure Hybrid DCS 2018 R2
The following is an overview of the new features of EcoStruxure Hybrid DCS 2018 R2:
1.1. Improved user interface functionality:
In the Application Explorer, the structure of the application is shown only in the
Application Browser pane. In addition, properties of folders and instances, as well as the Links Editor open in tabbed windows, turning the workspace into a work area that you can divide.
The layout of tree views is enhanced to optimize space management.
You can now extract any pane to reposition it and retract panes to their previous docked position.
1.2. Performance and productivity improvements in the engineering of Supervision
Participant projects:
The Build command can be used to integrate a larger number of changes to a
Supervision Participant project.
During deployment from the executable or the station node, you can select to deploy only the master Supervision project or also OFS configuration files and/or included projects.
The Deploy Changes command is introduced to deploy certain supported changes incrementally.
Significant time savings when you perform various operations, such as editing
Supervision pages, building, and deploying Supervision projects or changes.
You can save changes made to a Supervision page while changes made to another page are being saved.
1.3. Schneider Electric license management and the database management software are upgraded for increased cybersecurity.
1.4. Support for running Hybrid DCS in a virtualized (VMware ESXi) environment
Hybrid DCS 2018 R2 is now tested on a virtual environment, implemented by using VMware
ESXi, which is an enterprise class type-1 / bare metal hypervisor from VMWare. As it is a type-1 hypervisor, ESXi is a not software application which is installed on an Operating
System, it is directly installed on the physical hardware. After installation of ESXi, user can create virtual machine through the ESXi management console.
Please refer the Application Note “EcoStruxure Hybrid DCS System Infrastructure
Virtualized” for more details.
1.5. Foundation and Global Templates
For more information on new and/or updated templates, refer to the General Purpose
Library and Foundation Library release notes.
With the software installed, to get detailed information about these new features, go to the
“What’s New” page in the “Overview” topic of the HTML help and navigate to the description.
2. EcoStruxure Hybrid DCS 2018 R2 System Requirements
The system requirements (hardware requirements and recommended operating system) are dependent of the role of the machine: Server or client.
Refer to System Requirements in the Installation and Configuration Guide for details.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 2 of 21
3. EcoStruxure Hybrid DCS 2018 R2 Installation
It is recommended to first read the Installation and Configuration Guide before proceeding with the software installation. This document is in the software delivery ISO file, in the root of the installation package .
To browse the content of the ISO file, you have two possibilities: a. Use a tool to mount the image file as a virtual drive. b. 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
Before installing EcoStruxure Hybrid DCS 2018 R2, it is recommended to back up the
database if you are updating a previous version.
3.1. Additional Information Related to the Installation
Reference
User account used for the installation
Citect SCADA installation
Operating system compatibility
Changes to the system server console Action menu
Opening a pdf document
User guides
Default configuration of the simulator
Management of extensions in the VM
Description
User must have administrator rights on the computer to install and launch EcoStruxure Hybrid DCS. This is to avoid the request to provide the rights each time the software is launched. Please check the Windows User Account Control settings and configure them appropriately.
When installing Citect SCADA 2016 after EcoStruxure Hybrid DCS
2018 R2, it is required to disable the installation of the License Manager in the setup interface (So that the installed version is not replaced).
PES V4.3 and later versions are compatible with Windows 10. It is not the case for the earlier releases, including PES V4.2 SPx.
The "Launch Engineering Client" and "Launch Operation Client" commands are removed from the Action Menu.
Open the client by using the desktop shortcut icons or from the
EcoStruxure Hybrid DCS folder in the Windows Start menu.
It may not be possible to open a PDF document with the default PDF viewer delivered with Windows 8.1\Windows 10. A PDF viewer is therefore included inside the release. It is located in the root node of the ISO, in a folder called PDF Xchange Viewer.
EcoStruxure Hybrid DCS 2018 R2 supports contextual help. The user guides in PDF format are not delivered with the software (except for the
Installation and Configuration Guide and the Licensing Guide). The other user guides can be downloaded from the EcoStruxure Hybrid
DCS support Web site (https://app.schneider-electric.com/ecostruxurehybrid-dcs ). Registration required.
It is required to define the default configuration of the controller simulator when launching the controller simulator during the installation of EcoStruxure Hybrid DCS. Launching the simulator by loading a predefined password-protected application to the simulator helps prevent non-authorized access to the computer through the simulator when it is running. The behaviour is configurable at the installation and can be changed later. For more information, refer to chapter 3, System
and Installation Requirements in the Installation and Configuration
Guide.
Upgrading to EcoStruxure Hybrid DCS 2018 R2 removes the current virtual machine and installs a new one. The windows Operating System in the VM must be reactivated if you are upgrading from PES V4.3 to
Hybrid DCS 2018 R2.
Extensions (DTMs, GSD files,…) are backed up automatically in the path %localappdata%\Schneider Electric\Hybrid
DCS\ExtensionBackup and user must reinstall in the VM (Refer to chapter 5, Upgrading the Software in the Installation and
Configuration Guide.)
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 3 of 21
The use of some genies requires an additional installation
Floating license management
Consequence of
“Repair”
Some genies in the SGC Include2 included project require the installation of Microsoft form 2.0 (FM20.dll). The workaround consists in installing the Microsoft ActiveX Control Pad to obtain this dll. Nonexhaustive list of the concerned genies: sgc_client_10, sgc_iodev_10, sgc_m340_iodev_10, sgc_premium__iodev_10, sgc_quantum_iodev_10.
The Floating License Manager must not be uninstalled; otherwise
EcoStruxure Hybrid DCS cannot start.
Using the “Repair” feature leads to replacing the Virtual Machine (VDI file) in any case on the computer.
(For details, refer to chapter 10, Repairing the Software in the
Installation and Configuration Guide.” )
4. EcoStruxure Hybrid DCS 2018 R2 Software Licensing
4.1. Licensing EcoStruxure Hybrid DCS 2018 for the First Time
The table below gives the license compatibility for each version:
Installed release
Licenses required
PES V3.1 or PES
V3.1 SP1
V3.1 or
V4.0 or
V4.1 or
V4.2 or
V4.3 or
EcoStruxure
Hybrid DCS
2018
PES
V4.0
V4.0
(*)
PES V4.0
SP1
V4.0 or
V4.1 or
V4.2 or
V4.3 or
EcoStruxure
Hybrid DCS
2018
PES V4.1 PES V4.2 or V4.2
SPx
V4.1or V4.2 or V4.3 or
EcoStruxure
Hybrid DCS
2018
V4.2 or
V4.3 or
EcoStruxure
Hybrid DCS
2018
PES V4.3 or PES
V4.3 SP1
V4.3 or
EcoStruxure
Hybrid DCS
2018
EcoStruxure
Hybrid DCS
2018/R2
EcoStruxure
Hybrid DCS
2018
(*) PES V4.0 does not run with a PES V4.1, V4.2 or V4.3 or EcoStruxure Hybrid DCS license.
Main changes with this release
Change of the Server Port (license managers)
The installation of EcoStruxure Hybrid DCS 2018 R2 may modify the default settings of licensing software that was installed on the computer running the system server with Process
Expert V4.3/Sp1. The table below indicates which parameters are modified and the new value.
Software component
Parameter Parameter value after installing
EcoStruxure Hybrid
DCS 2018 R2
Comment
Floating
License
Manager
License
Manager
License Server
Port
Vendor
Daemon/Server
Port
27011
27011
If you have modified the default IP address (127.0.0.1) in the Host
Name / IP Address field of the
License Manager, the license server port is not changed.
For information on how to verify and/or modify the server port setting, refer to the topic describing how to configure an Enterprise License Server in the Licensing Guide.
In case another software acquires license rights from a Floating License Manager whose license server port was changed, you may need to modify the server port value of the corresponding entry in the License Manager that is used by this software.
Settings of the Floating License Manager and the License Managers that are installed on other computers are not modified.
In case two Floating License Managers are installed on the same computer, the installation of
EcoStruxure Hybrid DCS may not change the license server port. Please uninstall both FLM
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 4 of 21
versions and re-install FLM 2.2.0 from the EcoStruxure Hybrid DCS 2018 R2 ISO. Then install
EcoStruxure Hybrid DCS 2018 R2.
Security Information: Schneider Electric Floating License Manager affected by
Vulnerability:
Check the information concerning Security on the EcoStruxure Hybrid DCS support Website.
It is recommended to install the latest release of the Floating License Manager (FLM) that is available on the EcoStruxure Hybrid DCS support Website to help prevent malicious access to
EcoStruxure Hybrid DCS when connected on a network.
5. First Installation or Upgrade of Process Expert 4.3/SP1
5.1. Overview
This topic outlines the workflow that is required to get started with EcoStruxure Hybrid DCS in the following cases:
You are installing the software for the first time.
You are upgrading Process Expert 4.3 or its service pack with or without migrating a database.
If you want to reuse one or more of your databases with the new version of the software, refer to the prerequisites before proceeding with the upgrade.
If you are upgrading EcoStruxure Hybrid DCS 2018, refer to the procedure in the next topic.
In case you experience difficulties, refer to the troubleshooting topic ( see page 165 of
Installation and Configuration Guide ) or contact EcoStruxure Hybrid DCS support by visiting app.schneider-electric.com/ecostruxure-hybrid-dcs.
5.2. Prerequisites to Migrate a Database of a Supported Earlier Version
Before installing the software upgrade, you need to prepare the database ( see page 74 of
Installation and Configuration Guide ) of Process Expert for migration.
This step requires using the system server of your current version. Perform this step for each database that you want to reuse.
5.3. Getting Started
Step
The table outlines the steps to follow if you are installing the software for the first time or upgrading Process Expert 4.3 or its service pack. Each step contains a reference to the topic describing the step more in detail.
Action
1
2
3
4
5
Verify that the computers of the Process Expert system infrastructure still fulfill the system requirements ( see page 39 of Installation and Configuration Guide ).
If you are upgrading and had customized any setting in one of the configuration wizards
( see page 113 of Installation and Configuration Guide ), write down the modifications because you need to make them again after the installation of the upgrade is completed
(for example, the system server IP address, the folder shared with the virtual machine).
NOTE: The software automatically backs up the extensions ( see page 77 of Installation and Configuration Guide ) that are installed in the virtual machines.
Extract the files of the installation package ( see page 43 of Installation and Configuration
Guide ) to disk or mount the image (.iso).
Install the software ( see page 58 or 84 of Installation and Configuration Guide ) by launching the installer.
For a first-time installation, install at least the system server.
If you are upgrading, perform this step on the computer on which the Process Expert system server is installed. You can add and/or remove clients.
Select the authentication type ( see page 93 of Installation and Configuration Guide ) during installation.
NOTE: The steps to follow when you install clients are described at the end of this table.
Purchase or update licenses and activate them by using the Floating License Manager
(see EcoStruxure™ Hybrid DCS, Licensing Guide).
Page 5 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
6
7
8
9
10
11
12
13
14
15
16
17
If you selected the domain authentication, the system/network administrator must create a group ( see page 94 of Installation and Configuration Guide ) for each EcoStruxure
Hybrid DCS role.
(If you selected local authentication, the groups have been created automatically on the computer on which the system server has been installed.)
The system/network administrator must add users ( see page 87 of Installation and
Configuration Guide ) who need to use the software to one or more groups either:
•
On the system server computer for a local authentication type. Use the Windows®
ComputerManagement or lusrmgr (.msc) UI.
On the domain controller for a domain authentication type. Use the Windows®
Active Directory Administrative Center.
Open the system server console and log in by entering the username without domain or prefix and your password that correspond to the user added in step 7
(From the Windows® Start menu, click EcoStruxure Hybrid DCS → System Server.)
Create and/or install certificates ( see page 95 of Installation and Configuration Guide ) by using the Security section of the System Server Configuration Wizard (Settings menu of the system server console).
You can let the software create a root CA certificate or you may be able to use your own.
Activate ( see page 68 of Installation and Configuration Guide ) the virtual machine by entering an appropriate Windows® product key ( see page 27 of Installation and
Configuration Guide ) in the Virtual Machine section of the System Server Configuration
Wizard.
Share a folder ( see page 129 of Installation and Configuration Guide ) with the virtual machine.
The shared folder is required when you want to manage files within the virtual machine or exchange them between the virtual machine and the local computer.
If you are upgrading and had customized any setting by using the System Server
Configuration Wizard, re-configure the system server with these modifications.
If you want to migrate ( see page 79 of Installation and Configuration Guide ) a Process
Expert 4.3/SP1 database, re-install extensions ( see page 77 of Installation and
Configuration Guide ) in the virtual machine of the system server.
If you want to migrate ( see page 79 of Installation and Configuration Guide ) a Process
Expert 4.3/SP1 database, restore the database backup file (.mdbk) ( see page 145 of
Installation and Configuration Guide ).
Start the system server ( see page 143 of Installation and Configuration Guide ) by clicking Action → Start in the menu bar of the server console.
Wait until Server is ready appears in the console. This may take a moment the first time.
Install clients by launching the installer on other computers that you want to be part of the
EcoStruxure Hybrid DCS infrastructure:
For engineering clients, repeat steps 1, 3, 9, 10, and 11 of this procedure. Use the
Engineering Client Configuration Wizard (from the EcoStruxure Hybrid DCS folder of the Windows® Start menu).
For operation clients, repeat steps 1, 3 and 9 of this procedure. Use the Operation
Client Configuration Wizard (from the EcoStruxure Hybrid DCS folder of the
Windows® Start menu).
Install certificates only once per computer even if you are installing both types of clients.
NOTE: If you are upgrading, perform this step on each computer on which a Process
Expert client is installed.
If you are upgrading and had customized any setting by using a client configuration wizard, re-configure clients with these modifications before starting them.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 6 of 21
6. Upgrading EcoStruxure Hybrid DCS 2018
6.1. Overview
This topic outlines the steps that you need to complete to get started if you are upgrading
EcoStruxure Hybrid DCS 2018.
In case you experience difficulties, refer to the troubleshooting topic ( see page 165 of
Installation and Configuration Guide ) or contact EcoStruxure Hybrid DCS support by visiting app.schneider-electric.com/ecostruxure-hybrid-dcs .
6.2. Getting Started
Step
1
2
3
4
Each step contains a link to the topic describing the step more in detail.
Action
If you had customized any setting in one of the configuration wizards ( see page 113 of
Installation and Configuration Guide ), write down the modifications because you need to make them again after the installation of the upgrade is completed (for example, the system server IP address, the folder shared with the virtual machine).
NOTE: The software automatically backs up the extensions ( see page 77 of Installation and Configuration Guide ) that are installed in the virtual machines.
If you want to retain the HTML help of templates that you have used with version 2018, you need to copy the corresponding help files before proceeding with the upgrade.
Without this step, the help of version 2018 is replaced by the help of version 2018 R2.
For details, refer to Using Help for Different Versions of Schneider Electric Templates in the User Guide of version 2018.
Extract the files of the installation package ( see page 43 of Installation and Configuration
Guide ) to disk or mount the image (.iso).
) by launching the installer.
Perform this step on each computer on which version 2018 is installed. You can remove and/or add software components on each computer during installation.
NOTE:
The following items of version 2018 are still valid given that they are not expired (if applicable):
•
The authentication type ( see page 93 of Installation and Configuration Guide ) that you had selected is retained (for system server computer). However, you can change it.
•
User groups and user memberships for RBAC.
•
Licenses. (The Schneider Electric license management software may be upgraded as part of the installation. In such case, licenses remain activated.)
•
Certificates ( see page 95 of Installation and Configuration Guide ). Except for the root certificate file (.pfx), which is deleted during the upgrade if you had created it at the default path. In such case, retrieve the file first.
5
6
7
8
Activate the virtual machine by entering your Windows® product key ( see page 28 of
Installation and Configuration Guide ) in the Virtual Machine section of the System
Server Configuration Wizard. You can reuse the one that you had used for version
2018.
Re-configure the software components by using the appropriate configuration wizards
( see page 114 of Installation and Configuration Guide ).
Re-install extensions ( see page 77 of Installation and Configuration Guide ) in the virtual machine of the system server.
Starting the system server migrates the database ( see page 79 of Installation and
Configuration Guide ) that was mounted on the previously installed version of the software.
NOTE: You have the possibility to start using version 2018 R2 with a new database
( see page 66 of Installation and Configuration Guide ) instead.
Page 7 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
7. Software Compatibility with Participants
Software compatibilities of the software participants and controller firmware are listed below as a reminder:
7.1. Compatibility with Unity Pro V13.0
The system platform of EcoStruxure Hybrid DCS 2018 R2 embeds the services to edit and operate the control program by using Unity Pro V13.0 installed in a virtual machine. EcoStruxure
Hybrid DCS 2018 R2 embeds Unity Pro DTM library V3.9.3.
If you want to install Unity Pro V13.0 aside EcoStruxure Hybrid DCS 2018 R2 on the computer, refer to the Installation and Configuration Guide, chapter 3, topic Software Requirements for how to proceed with the installation.
7.2. Compatibility with Citect SCADA 2016
The system platform embeds the services to edit and build the SCADA application by using
Citect SCADA 2016 installed in a virtual machine. Nevertheless, for operation it is required to install
Citect SCADA as well as the regular SCADA environment. It is mandatory to install Citect SCADA
2016 to run the SCADA project generated by EcoStruxure Hybrid DCS 2018 R2 platform. Former versions of Vijeo Citect are not supported by EcoStruxure Hybrid DCS 2018 R2.
For details, refer to the Installation and Configuration Guide, chapter 4, topic Installing Supervision
Software.
7.3. Compatibility with OFS V3.60 SP4
The installation package of Citect SCADA 2016 includes OFS 3.60 SP2.
To benefit of the last updates, it is recommended to update OFS V3.60 with Service Pack 4, which is available on the EcoStruxure Hybrid DCS Support Website.
For details, refer to the Installation and Configuration Guide, chapter 4, topic Installing Supervision
Software.
7.4. Compatibility with Advantys Configuration Software V11.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.
7.5. Compatibility with the Automation Platform Firmware
Starting with PES V4.1 (except if a V4.0 database was migrated), the Global Templates library 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 Quantum Hot Standby (OS version equal or > V3.10)
Modicon M340 (OS version equal or > V2.70)
7.6. Configuration Limitation of Ethernet modules for M580 High End CPU (40, 50, 60)
The embedded version of the control Participant in this release is more restrictive in possibilities to support communications modules in a M580 High End controller.
Following are the maximum number of modules that you can configure:
Page 8 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
NOP = 4
NOC CTRL = 2
NOP + NOC CTRL = 4
NOP + NOC CTRL + NOC Generic when at least 1 NOC Generic is used in the configuration = 3
Max number of Generic NOC = 3
NOTE :
“NOP” = BMENOP61850 : communication module for the IEC 61850 protocol
“NOC CTRL” = BMENOC0321 : Control NOC (with IP Forwarding function) allowing transparency
“NOC Generic” = existing BMENOC0301 or BMENOC0311
8. Targeted Architectures
8.1. Hardware Components Supported
8.1.1. Automation platform and embedded modules
8.1.1.1. M580 Automation Platform
Standalone and redundant controller configurations are supported
•
All processors for standalone configurations.
•
All processors for redundant configurations
•
Non-redundant and redundant power supplies.
Following hardware modules are supported in EcoStruxure Hybrid DCS 2018 R2
Family HW (CPU/Rack/Module)
BME P58 4040/5040/6040 [v2.4]
M580
BME H58 4040/6040 [v2.4]
BME NOC 321 (NOC CTRL)
BMX ETM 0200
PMX NOW 0300
PME SWT 0100
BME XBP 0602/1002
BMX CPS 3522/4002/4022
BME NOC 3x1.3
All modules that are compatible with the M580 automation platform, including the X80 I/O platform are supported except the following modules that cannot be configured by using EcoStruxure Hybrid DCS:
Communication modules:
•
BMX NOC 0402 (Ethernet MB/TCP & IP)
•
BMX NGD 0100 (Ethernet Global Data)
•
PME UCM 0202
•
BME CXM 0100 ( CANopen communication)
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 EcoStruxure Hybrid DCS, but management of AS-I devices must be done by project refinement (no ready-to-configure services to manage devices)
•
PMX CDA 0400 (Diagnostic Module)
Remote and distributed I/O’s
•
X80 I/O platform
•
Quantum drops on Ethernet RIO
•
Intelligent remote stations through Peripheral Remote IO Adaptor (PRA)
•
Advantys STB islands on Ethernet Modbus TCP. All modules are supported, except o STBXBE1100 (EOS internal bus expansion module) o STBXBE1300 (BOS internal bus expansion module)
Page 9 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
o STBXMP1100 (Bus terminator) o STBCPS2111 (Auxiliary power supply) o STBEHC3020 (Counter module)
•
Profibus Remote Master(PRM) on Ethernet Modbus TCP
•
Third-party (STAHL I/Os) I/O modules in island on Ethernet Modbus TCP
•
Premium Racks & I/O modules, except : o TSX PAY 262 (Preventa safety) o TSX CTY 2A (counting) o TSX ISPY 101 (weighing)
•
Quantum S908 remote IOs using 140 CRA 31908. All modules supported in a S908 Quantum drop, except: o GEN IO (Generic digital I/O) o GEN ANA IO (Generic analog I/O) o 140 ESI 062 10 (Asynchronous serial link) o 140 DCF 077 00 o 140 XCP 900 00 (Battery holder) o 140 ERT 854 30 (time stamping) o 140 MSB 101 00 (motion) o 140 MSC 101 00 (motion) o 140 XBE 100 00 (rack expansion module) o 140 EIA 921 00 (ASi interface)
8.1.1.2. Quantum Automation Platform
Following hardware modules are supported in EcoStruxure Hybrid DCS 2018 R2
Family HW (CPU/Rack/Module)
Quantum 140 NOC 780.2
140 NOC 781.2
All modules on Quantum Ethernet RIO drop or Quantum S908 RIO drop are compatible with the
Quantum automation platform, except the following modules that cannot be configured by
EcoStruxure Hybrid DCS:
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 EcoStruxure Hybrid DCS:
•
Communication modules: o BMX NOC 0402 (Ethernet MB/TCP & IP) o BMX NGD 0100 (Ethernet Global Data) o PME UCM 0202 o BME CXM 0100 ( CANopen communication)
Page 10 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
•
Application specific modules: o BMX MSP 0200 (pulse train outputs) o BMX EAE 0300 (SSI encoder) o BMX EIA 0100 (AS-I V3 master) – Can be configured through EcoStruxure Hybrid
DCS, but management of AS-I devices must be done by project refinement (no readyto-configure services to manage devices) o PMXCDA0400 (Diagnostic Module)
Remote and distributed I/O’s on Quantum
•
X80 I/O platform
•
Quantum drops on Ethernet RIO
•
S908 Quantum drops
•
Advantys STB islands on Ethernet Modbus TCP.
•
Profibus Remote Master(PRM) on Ethernet Modbus TCP
•
Third-party (STAHL I/Os) I/O modules in island on Ethernet Modbus TCP
8.1.1.3. M340 Automation Platform
Following hardware modules are supported in EcoStruxure Hybrid DCS 2018 R2
Family HW (CPU/Rack/Module)
BME XBP 0602/1002
M340
BMX CPS 3522/4002/4022
PMX NOW 0300
BMX ETM 0200
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 EcoStruxure Hybrid DCS:
•
Communication modules: o BMX NOC 0401/ 0401.2 (Ethernet MB/TCP & IP) o BMX NGD 0100 (Ethernet Global Data) o PME UCM 0202 o BME CXM 0100 ( CANopen communication)
•
Application specific modules: o BMX MSP 0200 (pulse train outputs) o BMX EAE 0300 (SSI encoder) o BMX EIA 0100 (AS-I V3 master) – Can be configured through EcoStruxure Hybrid
DCS, but management of AS-I devices must be done by project refinement (no ready-to-configure services to manage devices) o PMXCDA0400 (Diagnostic Module)
NOTE - Premium controllers are not supported.
8.1.2. 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 and communication management of devices on Ethernet IP (explicit messaging through function blocks)
•
Configuration of Profibus Remote Master (PRM) within EcoStruxure Hybrid DCS
•
Configuration of BME NOP 0300 module for Modicon M580 using IEC61850 configurator tool.
Page 11 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
8.1.3. List of devices configured and supported in EcoStruxure Hybrid DCS
On Modbus serial
Automation devices: ATV 12, 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, MasterPactMTZ
Safety device: XPSMC
Templates for generic device on Modbus Serial
Communication management on Modbus Serial bus through an embedded port on CPU or NOM or
Ethernet/Modbus serial gateway
On Ethernet MBTCP (implicit & explicit messaging)
Automation devices: ATV32, ATV 61, ATV 71, Tesys T, ATV6xx, ATV9xx
Power devices: AccusineE, PM800, Compact NSX, Masterpact, PM5320, PM5340, PM82xx
Template for generic device on Modbus TCP/IP
Communication management on Modbus TCP/IP bus through an embedded port on CPU or NOE or
NOC.
On Ethernet IP (explicit messaging only)
Automation Device – Weighing Module
Templates for generic device on Ethernet IP
Communication management on Ethernet IP bus through an embedded port on CPU or NOC.
On Profibus (through the Profibus Remote Master – PRM)
Automation devices : ATV61, ATV 71, Tesys T
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
On Hardwired
Power devices : Compact, Masterpact & Support for third Party Circuit Breakers by means of
CircuitBreakerHW
8.1.4. Control network
•
Automation platforms (controllers) to SCADA communication: Ethernet Modbus/TCP through the controller’s 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 station node embedding the SCADA.
- Single configurations and redundant configuration are supported (automation platform and SCADA)
•
SCADA communication through OFS V3.60 SP4.
•
Connectivity from SCADA to devices through Modbus/TCP: communication through OFS V3.60
SP4 to exchange data between devices connected on Ethernet MB/TCP with the supervision, or with devices on Modbus serial behind a gateway.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 12 of 21
9. Enhancements and Fixed Issues Included in this Release
Additional improvements in EcoStruxure Hybrid DCS 2018 R2
Ticket number
Description
29063 Unable to undo changes of logic added in refinement
Control Project BuildAll fails sometimes for Large projects with many IO Scanning lines,
25909
34121 however the failure messages are inconsistent
Migration of Database from one version to other does not upgrade the INI file of
Supervision project
34654 Language change settings done through server configuration is not updating in VM
Global Template Editor - user cannot select any more an element and when trying to
34830 move it in the canvas it does move the whole canvas
34832 Global Template Editor - Element Alignment is not working well
33818 DATA not exchanged during a swap in M580 Redundant Controllers.
34816 Error reported while editing a $AISignal_UL
32841 Issue with example inside document of HART template $AISignalHART_UL
36543 Link broken following template object move
45498
ETM0200 with M340, move the facet between section following by Generate and Build doesn't work.
Hybrid DCS control project Build fails for STB on Quantum controller with NOC 7800 -
47006 Ethernet DIO Head.
47415 In certain scenarios, backup of system is not possible, in multiple client environment.
48029 The tree is not built properly because of the presence/absence of checkboxes
48125 Text in Tooltip in Engineering Client's Toolbar are not consistent in wordings
48375
48675
Citect OFSDriver issue: after deploy changes of OFS reload data dictionary: the result is #BAD in supervision
When user starts the PLC Simulator, a dialog box appears : "Error allocating PAT memory space" and the PLC simulator does not start.
48431
Hybrid DCS is not respecting supervision advanced settings General:
AddressonBoundary
48981
RBAC - Unauthorized person can break into Hybrid DCS Software that is locked without providing the Password
47512 Advantys Module STBEHC3020 is not available for Hardware Mapping
49607 Certificate installation is not possible for mapped network drive
28972
Deploy is aborted when using a structure of structure and when in that the last structure you use bit rank.
49904 Build all operation is failing with redundant cluster configuration
49959 Control Project Build (Incremental) fails after performing update control project
Start VM failed when user configure PC's name instead of IP@ in Address field of
44221 Engineering client wizard
35094 Save As of templates returns error "An Expression is too long or complex to Compile"
40917
Alias of attributes for the variables which were templatized in template before PES
V4.1 is not available
47683 Supervision Participant help for Hybrid DCS 2018 is not working
49946 Change in IODevice Protocol are not correctly propagated
46712 Closing an Extracted Participant window needs multiple clicks.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 13 of 21
10. Recommendations and Known Issues
10.1.
Ticket number
25566
Systems Management
Description
Backup / restore of a system: The “Restore” window does not provide the option to rename the system. It can be updated later after the restore.
10.2.
Ticket number
NA
Application Explorer
NA
Description
10.3.
Ticket number
1324
Topology
1717
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 EcoStruxure Hybrid DCS.
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 EcoStruxure Hybrid DCS), because the M580 doesn’t manage the corresponding 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”:
46232
Not able to save the Advantys configuration on computer with Windows7
Professional OS.
Workaround
When user saves the Advantys configuration and if it does not succeed, then user has to acknowledge the error and press OK on the UI which is present inside the Advantys configuration.
After that close the Advantys configuration and then it will save the settings.
Page 14 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
10.4.
Ticket number
1036
10756
1787
1807
1972
35043
Project Explorer
Description
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.
Do not rename sections generated by EcoStruxure Hybrid DCS 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 should stop the controller to download the changes.
Moving sections from one Control Project to another is not supported in PES although not restricted. Doing so renders unusable Control projects.
Recommendation:
Do not move sections from one Control Project to another.
If user negates a Pin to which a Link / Binding is generated by EcoStruxure
Hybrid DCS, 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 Non
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 EcoStruxure Hybrid
DCS 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.
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
The Change password and Clear Password option that is accessible in refinement mode, Controller Configuration, and Open Built project mode is disabled. However, when the window is opened, the Change / Clear password option is enabled for a couple of seconds and then disabled. Users are advised not to use this option.
It is observed in $MOTOR2 template, when opening the Control Participant in
$MOTOR2_UL, while you are trying to save the Participant control facet, an error message "Save is not successful" is displayed, because of ORDFB DFB in the UL having different signature but with same version in global constituent.
Page 15 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
41961
41496
46240
48433
The reason being, the code signature is different between ORDFB used in two different templates. That is because the position of the OR function block inside the section of the ORDFB type is different between two templates. Due to this, save operation restricts to keep the ORDFB updated in $Motor2_UL.
Recommended Steps
Option 1:
Modify the DFB version and continue saving the template changes.
Option 2:
Update the ORDFB in $Motor2_UL. To do so, Export ORDFB from
$SDDDEVCTL or another template referencing it and import it in $Motor2.
M580 HSBY, having Fast Task without section cause a Fast Overrun error in
Unity
Workaround
User has to create a FAST section with some Logic to get rid of the error.
DFB pin description truncate issue - DFB pin description is not fully visible and appears truncated. (Refresh Issue)
Workaround
User need to zoom in/zoom out and restore to default
If a control project contains FBD and non-FBD sections (specifically LL984), is already deployed to a controller, and is in "RUN" state, if the execution order of the project sections has been changed (either in the Project Explorer or refinement), then deploying the new execution order by using the Deploy
Changes command requires stopping the controller.
Sometimes in Windows 10 or Windows Server 2012, when user tries to open the Advanced Settings of a Supervision project for modifying the tagstartdigit, user will not be able to open it and it displays "updating participant display”.
Workaround
1. Export the supervision project from Project Explorer.
2. Delete this project from Project Explorer
3. Create a supervision project with the same name, as the one exported in step 1.
4. Import the exported supervision project from step1.
Note: For any other parameter changes in advanced settings, apart from
tagstartDigit, the user has to manually change it in Citect studio.
After restore of any project with peer to peer (P2P) communication mapping, export and import of the Project in a new system is giving error message.
Workaround
After migrating the project from 4.3 or 4.3 SP1 to EcoStruxure Hybrid DCS
2018 R2, open the Project Explorer and look for Control projects with P2P communication channels and make sure the below mentioned steps are completed before performing any operation (for example, export, import, refinement, build, generation) on the Control projects with P2P communication channels:
1. Open all the server-side control projects with P2P communication channels by using the Refine command, click Build->Rebuild All
Project, and make sure the project is built successfully.
2. Save the project refinement.
3. Open all the client-side control projects with P2P communication channels by using the Refine command, click Build->Rebuild All
Project, and make sure the project is built successfully.
4. Save the project refinement.
On performing Generation and Build, after assigning facets, instantiating
Genies, Map Service, Map Communication an error “Unable to compile
Supervision Project. Either connection to the server is lost or valid entity certificate of VM not found” is displayed occasionally.
Workaround
Subsequent Generation and Build or Build All operations ensures that the issue does not occur.
Page 16 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
49735 Vijeo Citect Participant version is not displayed in Supervision Refinement
10.5. Operation
Ticket number
18964
21989/22042
672
Description
Runtime Navigation Services (RTNS): The user is able to write values in the 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 EcoStruxure Hybrid DCS.
Adjusting the timeout communication parameter between a controller and PES
(control participant/Unity Pro)
EcoStruxure Hybrid DCS does not 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.
If user uses “Wonderware InBatch SFC Control” ActiveX, it is recommended to uncheck the option “Auto Initialize” from the “Wonderware BatchGuiConfig
Class” ActiveX as shown in the below image.
And user should write Cicode to initiate and terminate the connection between ActiveX and InBatch Server “on page shown” and “On page exit” as shown in the sample code below.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 17 of 21
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 18 of 21
10.6.
1532
1964
46586
Template Edition / Library Management
Ticket number Description
Problem when creating a genie facet template from a CTZ (include project) constituent including another CTZ.
EcoStruxure Hybrid DCS 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.
EcoStruxure Hybrid DCS does not allow instantiating 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:
Do not create an object template with the same instance of a DFB several times.
“Unity Elementary Variable” facet templates of the Foundation Library (for example, $Bool_UL) that were delivered with Process Expert V4.0 or earlier do not feature the AliasOf attribute. The value that is entered for this attribute is used in the Control Participant project for the Alias of attribute of the variable that is generated by the corresponding facet.
Restoring a database that contains these templates and starting the version
2018 R2 system server makes the attribute available in the variable element.
Thereafter, you can access the attribute in these facet templates and any of their references by editing them with the Facet Editor. You can then connect a platform input or parameter to the input pin of the attribute to be able to enter a value either during template edition or instantiation respectively.
NOTE:
•
When you install EcoStruxure Hybrid DCS 2018 R2 for the first time or upgrade and start fresh with a new database, the AliasOf attribute is available.
•
You may need to use the Show Unbound command on the variable element to view the attribute when you edit the facet template.
10.7. Installer
Ticket number
50423
Description
Starting With a New Database
If you are upgrading version 2018, you have the possibility to start fresh with version 2018 R2 by using a new database instead of migrating the database of version 2018. This database contains the latest templates provided with the software upgrade.
To use this database, download the database backup file (.dbk) from the
EcoStruxure Hybrid DCS Support Portal (registration required) and restore it before starting the version 2018 R2 system server.
You can also use this backup file to start fresh with a new database at any time.
When you restore a database backup file, the software creates a copy of the database that is mounted.
While installing from a network location or locally, ensure that the path doesn’t exceed 260 characters, else Installation does not complete .
Redistributable installation not successful while installing Hybrid DCS
If you encounter a message about redistributable installation, proceed as follows:
1. Skip the error message.
Page 19 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
44569
45958
2. Finish the EcoStruxure Hybrid DCS installation.
3. Install the respective redistributable software manually. Setups for redistributables are available in the ISO in the “ISSetupPrerequisites” folder.
Impossible to Log in using Domain user account.
If the message "Unable to authenticate user, Verify that the user has been added to the appropriate group on the system server computer or domain controller” Pops up, then verify that the SMB2 protocol is enabled in the domain server.
Using the Deploy Built Project command after migrating from v4.3 to
EcoStruxure Hybrid DCS 2018 R2 crashes PLC simulator.
Workaround
To modify following registry key,
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\kernel "DisableExceptionChainValidation"; = dword:00000001
Floating License Manager installation does not succeed when .Net
Framework 3.5 is not enabled in the machine.
Perform the following steps to enable the .Net Framework on the machine before launching the EcoStruxure Hybrid DCS setup:
1. In the Control Panel, select Programs.
2. Under “Programs and Features”, click “Turn Windows features on or off”.
3. Select .Net Framework 3.5, then click OK.
This will install .Net Framework 3.5 on the machine. Once the installation is successful, start the installation EcoStruxure Hybrid DCS.
Any user with customised Libset or MMM Library Patch batch file, prevents the installation of the Libset for the Control Participant when migrating to
EcoStruxure Hybrid DCS 2018 R2.
Resolution
Because the VM is upgraded to a 64-bit OS, the Execute.bat Batch file for the
Library Patch that the user wishes to run needs to be updated with a path pointing to the folder in a 64-bit environment. "Program Files" needs to be replaced with "Program Files (x86)".
If Archestra\Wonderware software is installed on the machine, the web port
8090 is used. This makes the Floating License Manager (FLM) V2.2.0 installation through the EcoStruxure Hybrid DCS installer unsuccessful and report error code 0x2015. In this case:
1. Uninstall the already installed FLM manually by using the Control
Panel.
2. Install the FLM V2.1.0 manually and enter an available web port number in the appropriate installation dialog box.
The FLM setup is available in the ISO in the “LicenseManagers” folder. After successful installation of the FLM, you can continue installing EcoStruxure
Hybrid DCS 2018 R2.
For information on the installation and configuration of the FLM, refer to
Appendix A of the Installation and Configuration Guide.
Installation not done with Full Administrator Privilege
If the installation is not done by a user with full administrator privileges and user starts the VM (for example, by starting the system server), an error is detected related to Oracle VM VirtualBox drivers not installed properly.
To resolve the problem, two options are available:
1. Uninstall Oracle VM VirtualBox and reinstall it with full administrator privilege (Run as administrator) which will eventually start all the VM
VirtualBox drivers, including those that were not installed earlier due to insufficient privileges.
2. Manually install the drivers for VM VirtualBox (instead of the complete software). To install the VM VirtualBox drivers:
Page 20 of 21 EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes
A. Go to the Oracle VM VirtualBox installation location and browse to the drivers folder (typically located at the path C:\Program
Files\Oracle\VirtualBox).
The folder contains the following three subfolders:
B. Open vboxdrv, right-click VBoxDrv.inf, and select Install.
C. In the USB folder, open filter, right-click VBoxUSBMon.inf, and select Install.
D. Restart the operating system.
After performing the steps of either option, browse to
“%localappdata%\Schneider Electric\Hybrid DCS 2018\Vm”, delete all the contents of the Vm folder, and start the Hybrid DCS system server. It should start properly.
Using Hybrid DCS with Non-English Operating System
While using Operating System with language other than English, please ensure to create username with English Characters only and not in local language.
EcoStruxure Hybrid DCS 2018 R2 – Platform Release Notes Page 21 of 21
Download
Public link updated
The public link to your chat has been updated. You may view and manage your chat links after registration here.
Document public link
Advertisement
Key features
Improved user interface functionality
Performance and productivity improvements in the engineering of Supervision Participant projects
Schneider Electric license management and the database management software are upgraded for increased cybersecurity
Support for running Hybrid DCS in a virtualized (VMware ESXi) environment
Foundation and Global Templates
Frequently asked questions
The EcoStruxure Hybrid DCS 2018 Platform is a powerful and versatile automation platform that can be used in a wide variety of applications.
Some of the key features of the platform include improved user interface functionality, performance and productivity improvements in the engineering of Supervision Participant projects, Schneider Electric license management and the database management software are upgraded for increased cybersecurity, support for running Hybrid DCS in a virtualized (VMware ESXi) environment, and Foundation and Global Templates.
The EcoStruxure Hybrid DCS 2018 Platform offers a number of benefits, including improved efficiency, reliability, and security.