8VZZ001554T2200 A en Splus Engineering 2.2 Release Notes

—
POWER GENERATION & WATER
ABB Ability™ Symphony® Plus

S+ Engineering 2.2
Release Notes
—
POWER GENERATION & WATER
ABB Ability™ Symphony® Plus

S+ Engineering 2.2
Release Notes
Notice
This document contains information about one or more ABB products and may include a description of or
a reference to one or more standards that may be generally relevant to the ABB products. The presence of
any such description of a standard or reference to a standard is not a representation that all of the ABB
products referenced in this document support all of the features of the described or referenced standard.
In order to determine the specific features supported by a particular ABB product, the reader should con-
sult the product specifications for the particular ABB product.
ABB may have one or more patents or pending patent applications protecting the intellectual property in
the ABB products described in this document.
The information in this document is subject to change without notice and should not be construed as a
commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document.
Products described or referenced in this document are designed to be connected and to communicate in-
formation and data through network interfaces, which should be connected to a secure network. It is the
sole responsibility of the system/product owner to provide and continuously ensure a secure connection
between the product and the system network and/or any other networks that may be connected.
The system/product owners must establish and maintain appropriate measures, including, but not limit-
ed to, the installation of firewalls, application of authentication measures, encryption of data, installation
of antivirus programs, and so on, to protect these products, the network, its system, and interfaces
against security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or
information.
ABB performs functionality testing on the products and updates that we release. However, system/prod-
uct owners are ultimately responsible for ensuring that any product updates or other major system up-
dates (to include but not limited to code changes, configuration file changes, third-party software
updates or patches, hardware change out, and so on) are compatible with the security measures imple-
mented. The system/product owners must verify that the system and associated products function as ex-
pected in the environment in which they are deployed.
In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any na-
ture or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential
damages arising from use of any software or hardware described in this document.
This document and parts thereof must not be reproduced or copied without written permission from ABB,
and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and may be used, cop-
ied, or disclosed only in accordance with the terms of such license.
This product meets the requirements specified in EMC Directive 2014/30/EU and in Low Voltage Directive
2014/35/EU.
The crossed-out wheeled bin symbol on the product and accompanying documents means
that used electrical and electronic equipment (WEEE) should not be mixed with general house-
hold waste. If you wish to discard electrical and electronic equipment (EEE), please contact
your dealer or supplier for further information.
Disposing of this product correctly will help save valuable resources and prevent any potential negative
effects on human health and the environment, which could otherwise arise from inappropriate waste
handling.
Trademarks and copyright

Symphony and Symphony Plus are registered or pending trademarks of ABB S.p.A.
Ability is a trademark of ABB.
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Copyright © 2011-2019 ABB. All rights reserved.
Release: June 2019

Document number: 8VZZ001554T2200
Revision: A
TABLE OF CONTENTS
TABLE OF CONTENTS
About this book ..........................................................................................................................................................1

General .....................................................................................................................................................................1
Document conventions ..........................................................................................................................................1
Document icon ........................................................................................................................................................1
1. Introduction ........................................................................................................................................................3
1.1 Executive summary .....................................................................................................................................3
1.2 Version designation ....................................................................................................................................3
1.3 Revision history ......................................................................................................................................... 4
1.4 Compatibility .............................................................................................................................................. 4
1.4.1 Hardware and software requirements...................................................................................................... 5
1.5 Restrictions................................................................................................................................................. 6
1.6 Reference documents ................................................................................................................................ 6
1.7 Product support ..........................................................................................................................................7
2. Modifications in 2.2 release ............................................................................................................................. 9

2.1 New functions and improvements ........................................................................................................... 9
2.2 Fixed problems ..........................................................................................................................................10
2.2.1 Configuration............................................................................................................................................... 10
2.2.2 Operation.......................................................................................................................................................17
2.3 Discontinued and replaced functions .....................................................................................................18
2.4 Known problems and workarounds ........................................................................................................18
2.4.1 Installation.................................................................................................................................................... 19
2.4.2 Configuration...............................................................................................................................................20
2.4.3 Operation...................................................................................................................................................... 41
3. Installation ....................................................................................................................................................... 53
3.1 Initial installation ..................................................................................................................................... 53
3.2 Upgrade ..................................................................................................................................................... 53
3.3 Backup and restore .................................................................................................................................. 53
A. Attribute Validation Range ............................................................................................................................ 55
B. Uninstallation....................................................................................................................................................57
B.1 Uninstallation of S+ Engineering 2.1.1 ....................................................................................................57
B.2 Post uninstallation ................................................................................................................................... 58
8VZZ001554T2200 A i
TABLE OF CONTENTS
ii 8VZZ001554T2200 A
LIST OF TABLES
LIST OF TABLES
Table 1-1: Version Designation ............................................................................................................... 3

Table 1-2: Revision Table ..........................................................................................................................4
Table 1-3: Hardware and Software Requirements ..............................................................................5
Table 1-4: Reference Documents ............................................................................................................6
Table 2-1: Fixed Configuration Issues ................................................................................................. 10
Table 2-2: Fixed Operation Issues ........................................................................................................ 17
Table 2-3: Known Installation Issues ................................................................................................... 19
Table 2-4: Known Configuration Issues ..............................................................................................20
Table 2-5: Known Operation Issues ..................................................................................................... 41
Table A-1: Attributes Validation Range ...............................................................................................55
Table B-1: List of Software for S+ Engineering 2.1.1 uninstallation ...............................................57
Table B-2: Symphony Plus related folder details ...............................................................................58
8VZZ001554T2200 A iii
LIST OF TABLES
iv 8VZZ001554T2200 A
About this book
About this book
General
This release notes provides a brief overview on new functions, enhancements, and functionality changes in
this product release. It lists the issues that existed in previous versions that are now corrected in this release.
It also enumerates known problems found or carried over in this release and identifies workarounds that help
overcome those issues. It contains additional notes that may be valuable to customers and service personnel
working with the product.
Document conventions
Microsoft Windows conventions are normally used for the standard presentation of material when entering
text, key sequences, prompts, messages, menu items, screen elements, etc.
Document icon
This release notes uses the following document icon with a corresponding statement, wherever applicable, to
point out important information or useful hints to the user.
Information icon alerts the reader to pertinent facts and conditions.
NOTE: The note statement highlights important information pertaining to a particular descriptive text in the
document.
8VZZ001554T2200 A 1
About this book
2 8VZZ001554T2200 A
1. Introduction Executive summary
1. Introduction
This document represents the release notes for S+ Engineering Version 2.2.
This Release Note document provides a brief overview of the new functions, enhancements, and functionality
changes in this product release. It lists the issues that existed in previous versions that are now corrected in
this release. It also enumerates known problems found in this release or found in previous releases and
identifies workarounds for the known issues. It contains additional notes that may be valuable to customers
and service personnel working with the product.
S+ Engineering is the Engineering tool for a Symphony Plus control system. It offers all the necessary
functionality needed to engineer, configure, administrate, secure, commission and maintain every
component in the Symphony Plus control system - from control and I/O, field instrumentation and electrical
devices to network architecture, and Operations, Engineering, and advanced system applications.
S+ Engineering allows for easy reuse and upgrade of Symphony, INFI 90 OPEN, INFI 90, and Network 90
control system engineering projects. In addition, the extensive reuse concept of S+ Engineering allows users
to optimize plant design with field-proven solutions based on ABB’s in-depth experience in the power and
water industries.
It is of utmost importance that the installation procedure is properly followed.
Refer to S+ System Installation user manual (2VAA008303 Rev E) for installation procedure of S+ Engineering
2.2 software.
It is recommended to read this Release Note document and referred user manuals before installing or
upgrading to the S+ Engineering version 2.2 software.
1.1 Executive summary

S+ Engineering software has a highly modular design. It comprises following major software components
that are integrated and harmonized to deliver a highly efficient engineering workflow.
• Engineering Workbench provides the framework to fully integrate different software components
that interact with one another. It also provides system level tools for project administration, user
management, bulk engineering tool, and topology design.
• Control Engineering provides all the functionality necessary to develop and maintain control logic
configurations of Symphony Plus SD and HR Series control & I/O, and also handles run-time
communications of S+ Engineering to SD and HR Series control networks.
• Operations Engineering provides integrated and centralized configuration, management, and remote
deployment for S+ Operations run-time servers and clients.
• Field Engineering provides a FDT/DTM technology based user friendly environment to configure,
commission, and manage intelligent field and electrical devices using PROFIBUS and HART protocols.
• Connectivity Engineering provides configuration for horizontal and/or vertical integration of foreign
device communications using standard protocols like IEC 60870-5-104, DNP 3.0, Modbus TCP, OPC,
IEC 61850.
• Harmony Gateway Software provides configuration of Modbus TCP communications for SD Series
HPC800 and HR Series BRC410 controllers.
• Batch Data Manager provides a set of tools for creating, editing, managing and debugging batch,
sequential and User Defined Function (UDF) code configurations.
1.2 Version designation

The following table (Table 1-1) lists the version designation of various components of S+ Engineering 2.2
software:
Table 1-1:Version Designation
Component Name Version Build Version

ABB S+ Engineering Composer Field 2.2 2.2.0000.121
ABB S+ Engineering Composer Harmony 7.1.0 7.1.0.343
ABB S+ Engineering Composer Harmony PowerTools 7.1 7.1.0.5
8VZZ001554T2200 A 8
Revision history 1. Introduction
Table 1-1:Version Designation (Continued)
Component Name Version Build Version

ABB S+ Engineering Composer Operations 3.2 3.2.0000.279
ABB S+ Engineering Harmony API Runtime 4.3.0 4.3.0.6
ABB S+ Engineering Harmony Batch Data Manager 7.1 7.1.0.3
ABB S+ Engineering Harmony Field Device Components 7.1.0 7.1.0.343
ABB S+ Engineering Harmony Soft Controller 2.2 2.2.0.2
ABB S+ Engineering IEC 61850 2.2 2.2.0000.12
ABB S+ Engineering Workbench 2.2 2.2.0000.294
ABB S+ Installation Manager 2.1 2.1.0000
ABB Basic HART DTM-HART DTM Builder 6.0.3-1 6.0.3 6.0.00300.1
ABB Basic PROFIBUS DTM - PROFIBUS DTM Builder 6.0.0-0 6.0 6.0.0.16
ABB Central Licensing System 6.1 6.1.00000.18
ABB FDT Base Container 14.0.3-1 14.0.3 14.0.00300.1
ABB FDT Shared Components 14.0.3-1 14.0.3 14.0.00300.2
ABB HAIHAO805 DTM 1.0 1.00.3044
ABB HARTSDIO DTM 1.0 1.00.3004
ABB Harmony Gateway Software 7.1 7.1 7.1.0.0
ABB PDP800 DTM 1.0 1.00.3040
ABB S+ Acronis Integration 1.1 1.1.1001
ABB S+ Audit Trail 1.3 1.3.0.6
1.3 Revision history

Table 1-2:Revision Table
Rev No. Description Date

A. Initial version May 2019
1.4 Compatibility
S+ Engineering compatibility information follows:
• Full integration and centralized engineering for S+ Operations 3.2.
• Compatible with S+ Operations 2.x with the same HMI Engineering workflow as in previous S+
Engineering for Harmony 1.x versions.
• Compatible with 800xA for Symphony Plus Harmony 6.x with the same HMI engineering workflow as
in previous S+ Engineering for Harmony 1.x versions.
• This release was tested with Microsoft Office Professional Plus 2016 (32-bit) software.
The following Antivirus Scanner program is compatible with S+ Engineering 2.2 software.
Refer to the Using McAfee Antivirus with Symphony Plus manual (2VAA000400) for more information.
• McAfee VirusScan® Enterprise 8.8.011000
The following virtualization software is compatible with S+ Engineering 2.2 software.
• VMWare ESXi 6.0
4 8VZZ001554T2200 A
1. Introduction Hardware and software requirements
• Hyper-V in Windows Server 2016

Firmware compatibility
The firmware compatibility for Harmony Gateway Software are as follows:
• The Harmony Gateway module (HPG-800) requires firmware revision L_9 or later.
• BRC-410 (firmware M_0).
NOTE: For the HPG-800 and BRC-410 rev M_0, only use the Test and Accept when doing online con-
figuration. Users should be aware of possible Bad Quality of values when performing a Go Back or
Additional during online configuration.
• The BRC-410 (firmware M_1 or later) is required in order to use the Online Configuration Go Back or
Additional features. Refer to the module hardware instructions for additional hardware and firmware
requirements.
• HPC800 (firmware A_2 or later).
Support configuration for controller feature based on the controller firmware. Refer the following matrix.
Figure 1: Controller Firmware Matrix
1.4.1 Hardware and software requirements

Table 1-3 contains the minimum recommended hardware and software requirements for installing S+
Engineering application:
Table 1-3:Hardware and Software Requirements
Hardware and
Engineering Server Engineering Client
Software Component
CPU Intel Xeon quad-core E5 Series 3.2 Intel Xeon quad-core E5 Series 2.4
GHz and 8 MB Cache or above. GHz and 8 MB Cache or above.
RAM 16 GB DDR4 (2 x 8GB) or above. 8 GB DDR4 (2 x 4GB) or above.
Hard disk 1 TB or above. (Capacity on C 320 GB or above.
drive min.500GB).
Display 1280x800 per screen or above. 1280x800 per screen or above.
RAID Level Default RAID 1 (with 1 additional Default RAID 1 (with 1 additional
disk). Option: none or RAID 5. disk). Option: none or RAID 5.
Network Cards for one 1 x NIC Dual Port or 2 x NIC single 1 x NIC Dual Port or 2 x NIC single
network port, 100 Mbps. port, 100 Mbps.
Network Cards for two 1 x NIC Dual Port 1Gbps or 2 x NIC 1 x NIC Dual Port, 1 Gbps or 2 x NIC
networks single port 1Gbps. Plus 1xNIC single port 1Gbps.
single port 100Mbps.
8VZZ001554T2200 A 5
Restrictions 1. Introduction
Table 1-3:Hardware and Software Requirements (Continued)
Hardware and
Engineering Server Engineering Client
Software Component
WDDM Driver WDDM 1.3 or above. WDDM 1.3 or above.
Virtual Processors 4 4
(Vcpu)
Virtualization VMWare ESXi 6.0 VMWare ESXi 6.0
Hyper-V Hyper-V
Adobe Reader Adobe Reader (latest) version Adobe Reader (latest) version
McAfee Edition McAfee Enterprise 8.8.011000 McAfee Enterprise 8.8.011000
Operating System Windows server 2016 (64-bit) Windows 10 IoT Enterprise LTSB
Windows 10 IoT Enterprise LTSB 2016 (64-bit)
2016 (64-bit)
Microsoft Office Microsoft Office Professional Microsoft Office Professional Plus
Plus 2016 (32-bit) 2016 (32-bit)
Refer Technical guideline for standard Hardware document (8VZZ000590D0001*) for more details.
1.5 Restrictions
There are no restrictions specific to this release.
1.6 Reference documents

The following table lists (Table 1-4) the documents that have been updated with respect to S+ Engineering 2.2
and can be referred for additional information.
Table 1-4:Reference Documents
Document Number Document Title

2VAA008303* S+ System Installation user manual
2VAA003191-200 S+ System Installation manager 2.0 user manual
2VAA000400* Symphony Plus Using McAfee Antivirus with Symphony Plus
2VAA000491* Symphony Plus Using McAfee ePO with Symphony Plus
2VAA001442* Security Updates Validation Status for Symphony Plus
2VAA003195-130 S+ System Logging and audit trail 1.3 user manual
2VAA003209-220 S+ Engineering 2.2 User management user manual
2VAA005210-220 S+ Engineering 2.2 Third party software licenses reference
manual
8VZZ000133T2200 S+ Engineering 2.2 Bulk engineering user manual
8VZZ000130T2200 S+ Engineering 2.2 Project administrator user manual
8VZZ000131T2200 S+ Engineering 2.2 System topology user manual
2VAA000812-710 S+ Engineering 2.2 Harmony engineering user manual
2VAA000813-710 S+ Engineering 2.2 Automation architect user manual
2VAA000844R0001 S+ Engineering Function code reference user manual
2VAA000828-710 S+ Engineering 2.2 View and monitor user manual
6 8VZZ001554T2200 A
1. Introduction Product support
Table 1-4:Reference Documents
Document Number Document Title

2VAA001872-710 S+ Engineering 2.2 Batch data manager user manual
2VAA001905-710 S+ Engineering 2.2 Batch 90 and UDF programming language
user manual
2VAA001978-710 S+ Engineering 2.2 Automation interface user manual
2VAA006938-320 S+ Engineering 2.2 Operations engineering user manual
2VAA001570-220 S+ Engineering 2.2 Field engineering user manual
8VZZ000132T2200 S+ Engineering 2.2 Connectivity engineering user manual
2VAA002581-710 S+ Engineering 2.2 Harmony gateway software user manual
8VZZ001714T2200 S+ System SOE Workflow user manual
(*) - Implies the latest version of the respective manuals.
All related documents are provided in PDF format and most of them are included in the Symphony Plus DVD
and MyControlSystem. To access documents on the DVD, select System Installer > Browse Documentation
from the System Installer Window.
1.7 Product support

Contact ABB local business organization, local service organization, or L3 Supportline in your region if any
product support is needed.
8VZZ001554T2200 A 7
Product support 1. Introduction
8 8VZZ001554T2200 A
2. Modifications in 2.2 release New functions and improvements
2. Modifications in 2.2 release

2.1 New functions and improvements
The following new functions and functional changes were added in S+ Engineering 2.2 software:
Platform:
• Support virtualization by Hyper-V in Windows Server 2016, in addition to existing VMWare ESXi 6.0
support
Symphony System Installer:
• Symphony System Installer modified to install the following products in addition to S+ Engineering
2.2.
– S+ Operations 3.2
– S+ Calculations 3.2
– S+ Analyst 7.1
IEC 60870-5-104 Control Network- Communications between SPC700 Controller and S+ Operations:
• Support open IEC 60870-5-104 protocol for Control Network based on the project type configuration.
NOTE: Only one type of control network can be present in any project at the same time.
• Reuse of existing Function Codes for IEC 60870-5-104 configurations with minimal changes.
• Support of 8 Master- Slave configurations.
• Automatic conversion of Signals with respect to IEC 60870-5-104 standards.
User Management:
• New options to better adapt the Windows domain interaction to existing corporate domains and
corporate IT requirements, e.g. read-only domains.
Control Engineering:
• Configuration support for new SD Series SPC600 controller.
• Extended PROFIBUS diagnostic support for SD Series controllers and PDP800.
• Support HN800 and CW800 bus statistics diagnostic for SD Series controllers.
• New firmware revision D introduced for HC800, SPC700, and SPC600 controllers.
• Set of Control Logic Documents (CLDs) can be exploded through a single click.
Bulk Engineering:
• Improved Logic state descriptor update using customized logic templates.
• Seamless configuration of Sequence of events (SOE) points from bulk engineering to S+ Operations.
• Select HMI fields option introduced to import optional HMI parameters.
• Improved support for the MACRO import functionality.
Signal Manager:
• Dynamic and predefined queries.
• Improved search criteria.
• Better navigation to access the validation errors.
• Separate tab of viewing SOE points.
Topology Design:
• Improved Network Distribution Class (NDC) configuration.
• Improved Node configurations for S+ Operations systems.
8VZZ001554T2200 A 9
Fixed problems 2. Modifications in 2.2 release
Operations Engineering:
• Automatic upgrade of the following databases from S+ Operations 2.0.x to 3.0.x.
– Alarm Category
– Alarm Printer
– Logical Colors
– Plant Area
– NDC
• Enhancement of system and database settings.
• Improved deployment on:
– Easy search of deploy action
– Option to select the various actions
– Single or multiple tag deployment
– Possibility to deploy the difference through difference viewer
• Possibility to compare system settings through difference viewer.
2.2 Fixed problems

Fixed problems are classified into the following functional categories:
• Configuration
• Operation
2.2.1 Configuration
Table 2-1: Fixed Configuration Issues
Fixed Issue Correction or Fix

Error occurs while trying to open Bulk Fixed.
Engineering, if any Control Logic Diagram (CLD)
is already opened.
COMP-CN-6500-164441
When the CLT property for Type and Firmware are The Module Type and Firmware Version information is
not properly updated, the CLT handling process is correctly configured when creating a CLT.
impacted. An “unexpected error” occurs when a
defaulted value with type = GenericModule and
firmware = A is saved for the CLT.
COMP-CN-7100-197001
COMP-CN-7010-197673
When a configuration contains large Black Box Optimized memory handling for verify and compile
Configurable Function Codes, the Verify CLD operations when a controller configuration contained Black
versus Configuration (CFG file or Controller) a Box Configurable Function Codes.
pop-up message identifies that Control
Engineering is out of memory.
COMP-CN-7000-196510
10 8VZZ001554T2200 A
2. Modifications in 2.2 release Configuration
Table 2-1: Fixed Configuration Issues (Continued)

Control Engineering Automation Architect issue IREF/OREF connection handling was corrected to recognize
with VISUAL identification of IREF/OREF connection points in the same CLD and connection points in
connections when the IREF/OREF pairs are on the other CLDs.
same CLD. The IREF/OREF information is
incomplete when there is an IREF/OREF pair on
the same page. The information is VISUAL and the
linking references are static.
When an engineer wants to navigate from OREF
to IREF, the navigation is executed using the
IREF/OREF property dialog. The property dialog
correctly displays the IREF/OREF links and
navigation is successful.
COMP-CN-7000-197370
COMP-CN-7000-197047
20180903-679388
When the Configurable Function Code contains Added the RMUX (FC 120) and RDMUX (FC 126) to the list of
multiple RMUX (FC 120) or RDMUX (FC 126) Function Codes with adaptable specs that can exist in a
function codes that are linked together via the H2 configurable function code.
lines, the compiler doesn't tune spec 12 to the
required linked/referenced block number.
COMP-CN-7000-191543
COMP-CN-7100-205335
When using Automation Architect, the Cut and Improved the Cut and Paste operation when logic includes
Paste of logic which includes OREF cross OREFs with cross reference text.
references from a Control Logic Document does
not remove the existing OREF cross reference and
its properties from the project.
COMP-CN-7000-191542
When a Control Logic Document configured with Navigate to the unpacked Control Logic Document with the
a CFC with multiple tags is packed and then CFC configured with multiple tags. The tags associated with
unpacked into another project, the multiple tags the CFC are correctly unpacked.
defined for the CFC are not correctly unpacked.
COMP-CN-7000-191592
In S+ Engineering Topology Design, the user can The Topology Design feature has been improved and
connect a single HNET network to two different associates control units and controllers with the associated
controllers (HPC800 or SPC700). The Topology configured HN800 network. This issue is not reproduced in
Design and Control Engineering data become SPE 2.2.
inconsistent.
COMP-CN-6300-67332
It is not possible to create new devices from Synchronization between Control Engineering and Topology
Topology Design below a control network, if all Design is improved in latest releases. A hardware structure
devices below the control network are not can be created in Control Engineering and modified in
synchronized between Topology Design and Topology Design without issue as synchronization between
Control Engineering. these applications is improved.
COMP-CN-6300-69550
8VZZ001554T2200 A 11
Configuration 2. Modifications in 2.2 release

If a network is created through Topology Design Synchronization between Control Engineering and Topology
and additional networks are created through Bulk Design is improved in latest releases. A hardware structure
Engineering, then only a partial topology is can be created in Control Engineering and modified in
created in Control Engineering. Topology Design without issue as synchronization between
COMP-CN-6300-69665 these applications is improved.
Topology Design Diagram templates are not When the user creates a DIAGRAM template with S800 and
reusable in another project, when user creates S900 I/O, the user must make sure that the SLOT ADDRESSES
the diagram template with S800 and S900 IO created for the S800 I/O or S900 I/O are unique and not
modules. duplicates of one another. Correctly configured DIAGRAMs
COMP-CN-6300-94238 can be reused.
COMP-CN-6500-115286
IEC 61850 signal search function is not locating to The Signal Search feature is enhanced to search for a Signal
the correct function code, when user searches the Name in any sheet in a CLD. In Automation Architect, select a
signal from different sheets which are located in CLD sheet. Select the Edit -> Select By-> Signal Name feature
the same CLD. and enter a Signal Name, the CLD sheet with the signal is
COMP-CN-6400-105381 active and the signal is highlighted.
COMP-CN-7100-190016
The CLD Export/CLD Import feature does not CLD Export/CLD Import feature is improved to properly
support export/import of the multiple tags handle a configuration which includes a Configurable
configured for a Configurable Function Code.The Function Code with multiple tags.
Tag Name field is BLANK. Other Configurable
Function Code information is exported and
imported using CLD Export/CLD Import.
COMP-CN-7000-176726
COMP-CN-7000-179834
Copy of logic containing a Configurable Function Copy of logic containing a Configurable Function Code with
Codes with multiple tags does not successfully multiple tags functions as expected.
make copies of the multiple tags.
COMP-CN-7000-187012
COMP-CN-7000-188682
Automation Update notification is not sent to An Automation Update notification is sent to Topology
Topology Design when a CLT name is changed. Design when a CLT name is changed after a device is created.
COMP-CN-7000-140854
GSLV script not correct after a Project Restore The GSLV script is modified to reflect the new project
with new name operation. The GSLV script is not directory and new project name.
updated with the new project name but retains
the original project name.
COMP-CN-7000-185192
When defining a CFC, the folder containing the When defining a CFC, a folder copy operation is not
CFC definition components (shape, logic, input supported.A message is added warning the user “Copying a
mapping, output mapping, specification folder containing a Configurable Function Code is not
mapping, and tag mapping) can be copied. The supported”.
copy of the data does not hold all CFC definition
components.
COMP-CN-6500-177984
COMP-CN-7100-196702
12 8VZZ001554T2200 A

When an IREF connection and OREF connection IREF/OREF connection logic was modified to automatically
are configured within the same control logic update the XREF text for these IREF connection and OREF
document and/or controller, the XREF text is not connection bubbles.
updated automatically in the XREF text for these
IREF connection and OREF connection bubbles.
COMP-CN-7000-174011
Anytime the “Add new record…” menu item in the The “Add new record ..." to add tags through the Data
Data Browser is clicked, it will result in the Browser is rewritten to correctly INSERT a new tag into the
following: database.
“Invalid format for Replication ID.”
COMP-CN-7000-187292
If a user performs a cut/paste of a CFC defined The cut/paste functionality is improved to support
with multiple tags or deletes a CFC defined with Configurable Function Codes configured with multiple tags.
multiple tags and then decides to quit without
saving the CLD, the CFC defined multiple tags will
not be automatically re-link.
COMP-CN-7000-189916
COMP-CN-7100-206238
The CUT operation for logic that includes a The cut/paste functionality is improved to support
Configurable Function Code (CFC) defined with Configurable Function Codes configured with multiple tags.
multiple tags, does not successfully change the The linked tags are now visible upon pasting the logic.
assignment of the multiple tags when pasted.
COMP-CN-7000-189403
COMP-CN-7100-205472
Deleting a Configurable Function Code (CFC) with The delete is improved to support Configurable Function
multiple tags will fail to properly unlink the Codes configured with multiple tags. The deletion of a CFC
multiple tags. now unlinks all assigned tags.
COMP-CN-7000-189505
While setting bus parameters for CI840 slave, the Issue is resolved with delivery of new DTMs.
following error message is displayed and a new
PROFIBUS device is not created in Control
Engineering sometimes.
“Unable to add device to Field Engineering: DTM
does not accept bus address 40."
COMP-CN-1500-110312
Automation Architect will freeze during normal Fixed.
compilation and modification if the log feature is
enabled.
20181113-790336
COMP-CN-7000-201115
COMP-CN-7000-202403
8VZZ001554T2200 A 13

Error when copying a CLD from project to project Modified symbol and shape lookup function to support case
that contains a user shape or symbol. The error sensitive symbol and shape names. Symbol and shape names
window text is “Please do not delete files while a are NOT case insensitive.
copy is in progress! Object not found in the
Project database, please refresh Project.”
In the Output window the error message is Failed
copying “CLD Name” to “Controller Name”.
COMP-CN-7000-202413
COMP-CN-7000-202647
20181116-798334
When using Control Engineering, configuration Control Engineering is enhanced to correctly calculate the FC
for FC 227 S4 string value MNSI required manual 227 S4 MNSI value.
input to correct the value.
COMP-CN-7000-203468
MODBUS TCP Connectivity signal search function Enhancement.
is not locating to the correct function code, when The Signal Search feature is enhanced to search for a Signal
user searches the signal from different sheets Name in any sheet in a CLD. In Automation Architect, select a
which are located in the same CLD. CLD sheet. Select the Edit -> Select By-> Signal Name feature
COMP-CN-6500-155996 and enter a Signal Name, the CLD sheet with the signal is
active and the signal is highlighted.
IEC104 Connectivity signal search function is not Enhancement.
locating to the correct function code, when user The Signal Search feature is enhanced to search for a Signal
searches the signal from different sheets which Name in any sheet in a CLD. In Automation Architect, select a
are located in the same CLD. CLD sheet. Select the Edit -> Select By-> Signal Name feature
DNP3 Connectivity signal search function is not Enhancement.
locating to the correct function code, when user The Signal Search feature is enhanced to search for a Signal
searches the signal from different sheets which Name in any sheet in a CLD. In Automation Architect, select a
are located in the same CLD. CLD sheet. Select the Edit -> Select By-> Signal Name feature
The CLD dynamic border updated to include 3 Enhancement.
more entities: Customer Ref 1, Customer Ref 2, Job Number, Customer Ref 1, and Customer Ref 2 information
and Job Number. entered when creating a project is used in the CLD dynamic
COMP-CN-7000-169765 border.
Explode CLD feature enhanced to provide Enhancement.
capability to rename the exploded sheets from Explode CLD features allows user to enter a CLD name for the
default internal sheet name. “Exploded CLD”.
COMP-CN-7100-194212
When the same cross reference text is used more Enhancement.
than once within a controller configuration to The compiler was modified to report an error when the same
import the same digital or analog input from cross reference text is used more than once within a
another control unit via AI/I, AI/L, DI/I, or DI/L the controller configuration to import the same digital or analog
following warning is listed in the compiler log: " input from another control unit.
Input Reference has already been accessed”.
While a warning is better than no indication at all
the condition would be best if treated as an error.
COMP-CN-7000-195525
20180802-642556
14 8VZZ001554T2200 A

than once within a CLD to import the same digital The compiler was modified to report an error when the same
or analog input from another control unit via cross reference text is used more than once within a
AI/B, AIL/B, DI/B, or DIL/B rather than filling in controller configuration to import the same digital or analog
the reference specs SPE will set them all to zero. input from another controller.
The compiler will offer the following warning to
alert the user of the condition of the duplicate
use of the cross reference input string. “Input
Reference has already been accessed”.
COMP-CN-7000-195526
20180802-642556
than once within a controller configuration to The compiler was modified to report an error when two input
import the same digital or analog input from from the loop function codes access the same source
another control unit via AI/I, AI/L, DI/I, or DI/L the function block address because the condition results in logic
following warning is listed in the compiler that does not work as expected by the user.
log:“Input Reference has already been
accessed”.However, when no cross reference text
is used on the input function code allowing the
user to manually enter the reference
specifications the compiler does not identify the
duplicate. The case where two input from the
loop function codes access the same source
function block address should be flagged as an
error since the condition results in logic that does
not work as expected by the user.
COMP-CN-7000-195527
A CFC with NO mapped specifications cannot be CFC specification mapping improved to handle the use case
verified or viewed using Configuration Viewer where NO mapped specifications.
application. Error in Open Configuration. Error
reading CFG file.
COMP-CN-7000-196172
When upgrade project from previous versions of This issue has been corrected.
Composer Harmony or S+ Engineering, if project
path plus CLT name exceeds 128 characters, the
CLT and instantiated CLDs will be missing in the
upgraded project.
COMP-CN-7000-199836
COMP-CN-7100-197514
COMP-CN-7000-199958
20181022-758221
COMP-CN-7000-202510
20181129-816861
In Bulk Engineering Tool, created custom Fixed.
attribute is part of Signal Manager view, but it is Required HMI attributes can now be configured using 'select
not part of Operations Engineering tag view. HMI field’s.
WBBE-CN-2100-177012
The change in Role property for HPC800 and Fixed.
SPC700 controllers from backup to primary is not
supported in Topology Design.
WBST-CN-1100-69545
8VZZ001554T2200 A 15

Batch Data Manager configuration fails when Batch Data Manager application can now be configured using
using the VPNI. VPNI as well as physical PNI800 or IET800 communication
BDM-CN-7000-183783 modules.
Cannot save a configuration from the SEM or The Runtime operation SAVE has been updated to correctly
MFP. An error message “Fatal 100(ICI) Undefined save a configuration from SEM and MFP modules.
message type” appeared and save configuration
failed.
COMP-OL-7000-201097
COMP-OL-7000-202653
COMP-OL-7000-202654
COMP-OL-7000-201661
COMP-OL-7000-201739
20181115-795031
20181113-790331
View and Monitor revision order is not correct on The revision order is corrected.
the drawing.
COMP-OL-7000-186740
When closing the S+ Engineering program or This issue has been corrected.
project, a Composer.exe Application Crash event
message, and possibly a GMC32.exe Application
Crash event message will show in the Windows
Application Event Log. In some systems, a pop-up
window with the “Composer Navigator has
stopped” message might display too.
COMP-OL-6600-196155
COMP-OL-6600-197450
COMP-OL-6600-196511
20180525-549877
16 8VZZ001554T2200 A
2. Modifications in 2.2 release Operation
2.2.2 Operation
Table 2-2: Fixed Operation Issues
Fixed Issues Correction or Fix

After upgrading a Control Engineering 6.1 or Fixed.
lower versions project, user is unable to make a
backup of the project to SPE 2.1/2.1.1. When
attempting to backup the project, user receives
error messages in the output window during the
backup of Operations Engineering.
WBPA-OL-2100-196647
20180928-725080
WBPA-OL-2100-198374
20181003-729924
Project restore failed when it is performed in Fixed.
another/new machine which does not have the
same user name who created the backup.
WBPA-OL-2100-198513
20180928-725048
Load data does not support loading of changed Fixed.

spec values from a function code.
WBCE-OL-2100-145610
Channel tab of FC224 is not activated when HSOE Fixed.
spec enabled via Bulk import. FC224 channel tab is now activated.
WBBE-OL-2100-180014
Control Engineering, Function Code’s (FC) Fixed.
removed tags are getting listed in the Signal Refer S+ Engineering 2.2 Harmony engineering user
Manager. In case after removal any tags added to manual(2VAA000812*) for more information.
that same FC, both the tags are listed in the
Signal Manager.
WBSM-OL-2100-186239
Renamed signals are get removed from CLD when Fixed.
user perform the import of new tag or spec
modification for existing tags during sub sequent
import.
WBCE-OL-2100-185923
Error message is displayed when sample pattern Fixed.
file for IEC 60870-5-104and Modbus located in Sample pattern mapping shall be used.
..\SymphonyPlus\templates\ExampleIOFiles\HM
I signal list is imported during the data type
mapping.
OPE-OL-3100-191622
Deployment issue is faced in S+ Operations While Fixed.
using special characters in string references Remove the special character (' single quote) from string
fields (Tag_S_R 1-50). reference fields.
OPE-OL-3100-198262
20180917-700065
Few of the attributes are restricted within the Fixed.
limited ranges. Hence, the attribute values cannot The validation range for the attributes are now revised.
be extended as per the project requirement. Refer Attribute Validation Range for more details on the new
WBSM-OL-2110-204454 range of the attributes.
20190115-877561
8VZZ001554T2200 A 17
Discontinued and replaced functions 2. Modifications in 2.2 release
Table 2-2: Fixed Operation Issues (Continued)
Fixed Issues Correction or Fix

Once the higher priority alarm is reported at the This Features can be enabled by system setting configuration
same time, Alarm sound is not getting changed under ‘Apps\Alarms\Audible InterceptAudibleByPriority=1’.
according to the highest priority. For more information, refer to Audible Alarm for High Priority
WBOBE-OL-2200-200350 section in S+ Operations engineering user manual
(2VAA006938-320*).
When using a VPNI, the configuration download The performance for configuration download to a controller
to a controller is slow. via VPNI is improved.
HAPI-OL-4210-197542
HAPI-OL-4200-194565
HAPI-OL-3200-120493
20180726-633360
When VPNI is started after network is not This issue has been corrected.
available (cable disconnected or network adapter
disabled), the computer will freeze after running
for approximately 13 hours.
HAPI-OL-4200-197888
HAPI-OL-4200-193422
20180130-405821
When running the Harmony Soft Controller The user must enable the Harmony Soft Controller and then
application, the verify of Configuration or Control connect to it each time it is enabled. This is documented in
Logic Documents against the running Harmony the instructions. When the WB Logical ICI identifies
Soft Controller fails. CONNECTED, then communicating with the Harmony Soft
HSC-OL-2100-186803 Controller is successful.
The function code configuration inside a The Function Code configuration (blocks and specifications)
Controller running as a soft controller cannot be can be viewed from the soft controller.
viewed using the Configuration Viewer
application.
HSC-OL-2100-186802
2.3 Discontinued and replaced functions

There are no functions discontinued as part of SPE 2.2.
2.4 Known problems and workarounds

Known problems are classified into the following functional categories:
• Installation
• Configuration
• Operation
18 8VZZ001554T2200 A
2. Modifications in 2.2 release Installation
2.4.1 Installation
The following table (Table 2-3) lists the installation problems or issues known to exist with the current
release. A workaround, when possible, has been identified for each problem or issue.
Table 2-3: Known Installation Issues
Issues Workaround/Clarification/Helpful hints

CLS 6.1 compatibility issues. No workaround.
Single node is not possible with SPE & 800xA using CLS
(Central Licensing Server) 6.1.0.18 and CLS 6.0.3 due to
compatibility issues.
COMP-IN-2100-181779
On installation, the new ABB certificate used with Remove the ABB certificate, reinstall the certificate by
theIET800 A.6 firmware for Advanced Mode connections is following the procedures described in Technical
not placed in the correct Windows certificate store. It Description for SPIET800 Advanced
should be in Trusted Root. Security Level PC Client Certificate Installation
HAPI-IET-IN-6300-68289 document (2VAA006026*).
When installing S+ Engineering, the S+ Engineering User should enter a name followed by number. For
Database Server component cannot be installed under a example- ABC123.
Windows account with a name that begins with a number
(For example, “800xA Install”).
COMP-IN-6000-0001
Field Engineering:
If a project has no license to support Field Engineering, the If the project has no license to support Field
Launch Field Engineering function in Control Engineering Engineering, do not right-click in Control Engineering to
will not execute. launch Field Engineering function.
No warning message is available.
COMP-IN-6500-114239
Workbench:
'Index was outside the bounds of the array' error occurs Remove any empty spaces available in CONTEXT.TXT file.
when generating media with Official DVD.
WBIM-IN-2000-186457
Uninstallation steps in installation manual for S+ Refer the uninstallation and post uninstallation steps
Engineering do not completely list all items that must be covered for s+ Engineering 2.1/2.1.1 for in the
removed prior to reinstallation. Uninstallation section.
WBIM-IN-1400-203723
8VZZ001554T2200 A 19
2.4.2 Configuration
The following table (Table 2-4) lists the configuration issues known to exist with the current release.
Solutions or workarounds have been provided for the issues.
Table 2-4: Known Configuration Issues

S+ Engineering 2.1 Control Engineering does not support Remove the User View that references fields related to
User Views that reference fields related to Trend Lists. If a Trend Lists.
project is upgraded to SPE 2.1 and it still contains Trend
1. In the Tools menu in the Control Engineering Ribbon
Lists or User Views that reference fields related to Trend
Bar, select “Manage Views” to open the Manage Views tool.
Lists, a project backup cannot be successfully upgraded to
the next S+ Engineering 2.2 version. 2. In the DataTypes drop-down select “Trend”.
3. A list of “Trend” related views is displayed with View-

Type of “System” or “User”.
Those views marked as “System” will be handled

correctly by the upgrade
The views marked as “User” will not be handled
correctly by the upgrade. Delete the “User” related
Trend Views.
COMP-CN-7100-209555
4. Take a new project backup after the User Views with
COMP-CN-7100-209589 Trend List references is removed.
To support a S+ Engineering project configured for IEC104 A NOTE in Section 23.2 item 9 identifies that the
communications backbone, a user created IEC104 network SPC700 must be properly formatted and in “Configure”
configuration file must be downloaded to a "C" memory mode when downloading the IEC 60870-5-104
partition in the controller. The S+ Engineering 2.2 Harmony configuration. For further details, reference Section
engineering user manual (2VAA000812*) Section 23.2 5.6.18 Format Memory for instructions to manually
describes how to create the file but does not contain format the controller with memory space. For a
instructions on how to format the “C” memory partition MANUAL Format, identify Number of Files 1; NVRAM for
into which the network configuration file must be C as 3000; RAM for C as 3000.
downloaded.
COMP-CN-7100-209771
When loading firmware to an SPC600, only FW revision D is As designed.
allowed. However, when using S+ Engineering Control User must be aware that SPC600 supports FW revision
Engineering, FW revision C can be selected and D.
downloaded. Once the download is complete, the
controller red lights with 2/5/6 error.
COMP-CN-7100-201294
The new Profibus Extended Diagnostic feature requires As designed.
identical device/module name in Control Engineering and It is important to maintain consistent naming between
Field Engineering for proper synchronization of the DIAG= Control Engineering and Field Engineering for correct
string value. Profibus Extended Diagnostic functionality.
Renaming a GSD based FD module makes it impossible to
configure the PDP800 DIAG= for Profibus Extended
Diagnostic functionality.
COMP-CN-7100-206085
COMP-CN-7100-206913
When a change is made on a CLD in Control Engineering, no Changes from Control Engineering propagate to Signal
notification is given in Signal Manager that a Manager; however this is no indication that
synchronization is needed. synchronization is required.
COMP-CN-7100-204099
20 8VZZ001554T2200 A
Table 2-4: Known Configuration Issues (Continued)

The Update Device cross-references function does not Use the Device Templates versus Generate CLD option
work on the first attempt when the devices are created when creating the devices.
using the Generate CLD option. As alternative, if use the Generate CLD option, then the
engineer would be responsible for “linking” the Device
COMP-CN-7000-195549 Cross References manually.
SOE Point Names are case sensitive with the S+ As designed.
Engineering 2.1 release. Confirm the SOE Point Names when configuring SOE
COMP-CN-7000-205554 information.
CLT names are case sensitive with the S+ Engineering 2.1 As designed.
release. Confirm the CLT name case when creating a Control
COMP-CN-7000-205554 Logic Template.
Tag Names are case sensitive with the S+ Engineering 2.1 As designed.
release. Confirm the tag name case when creating a Control
COMP-CN-7000-205554 Logic Documents and Tag Lists.
There is no warning message for a Configurable Function Modify the order of the Configurable Function Code
Code configured with an input mapped to multiple internal mapped inputs for compatible default settings for the
Function codes where the default setting for the first input Function codes.
Function code mapped input is not compatible with other
default settings of Function Code mapped inputs.
COMP-CN-7000-196946
COMP-CN-7000-196786
When using the Tag Property dialog or Data Browser view, A Refresh View may be needed to see consistent
changes to some fields, such as, Engineering Unit updates for the tag property fields, as example,
Description/Engineering Unit Index or Alarm Comment Engineering Unit Description/Engineering Unit Index or
Description/Alarm Comment Index, may not be Alarm Comment Description/Alarm Comment Index.
consistently updated.
COMP-CN-7000-180831
COMP-CN-7000-177628
The Project Binding feature only updates the project that is As designed.
opened performing the binding function.
COMP-CN-7000-179970
CLD names are case sensitive with the S+ Engineering 2.1 As designed.
release. Confirm the CLD name case when creating a Control
COMP-CN-7000-147133 Logic Document.
Topology Design: A “Multiple Error Occur” message may be When using Topology Design to manually configure
displayed when saving a Topology Diagram created multiple PDP800 modules, multiple S800 I/O modules,
manually in Topology Design where the Topology Design or multiple Generic HART devices, confirm that the
includes multiple PDP800 modules, multiple S800 I/O addresses and names are uniquely defined in the
modules, or multiple HART devices. configuration. For a PDP800 module, confirm that the
COMP-CN-6300-68191 Bus Address is unique and not consistently “0”. Make
COMP-CN-7000-184747 the Bus Addresses unique. For multiple S800 I/O
modules, confirm that the Slot Number is unique and
COMP-CN-7000-188094
not consistently “1”. Make the Slot Number unique. For
multiple Generic HART devices, confirm that the HART
Channel is unique and not consistently “1”. Make the
HART Channel unique.
Recording Modify and Tune function block operations in an After Project Upgrade, close the upgraded project and
Event Log may not be recorded after a project upgrade. then open the upgraded project. When enabled, the
event logging to record Modify and Tune function block
COMP-CN-7000-177571 operations should be visible.
8VZZ001554T2200 A 21

S+ Engineering Harmony does not support adding or As designed.
deleting a Configurable Function Code to or from a No workaround.
controller in Config mode using the Controller
Configuration Viewer application.
COMP-CN-7000-184308
COMP-CN-7000-184309
Signal line type are not automatically propagated for pass Close the Control Logic Document and then re-open
through cross-reference pairs. Control Logic Document to observe that change in the
COMP-CN-7000-181180 signal line type.
If a Configurable Function Code contains a FC 24 ADAPT It is recommended that the logic for the Configurable
and the FC 24 ADAPT is misconfigured, the Controller Function Code be confirmed in a control logic
compile operation will not identify the error as a COMPILE
document with a Controller compiler operation before
FAILED error. it is used in a CFC. If logic in a control logic document
has a misconfigured FC 24 ADAPT block, a COMPILE
COMP-CN-7000-176833 FAILED message is generated.
In the Data Browser View, when an alarm inhibit tag is When configuring an inhibit tag via the tag property
configured using the tag property dialog, if the INHIBIT TAG dialog, if the error dialog indicates the following, the
is configured as a self-reference, the error reported is not root cause is that the inhibit tag configured is self-
understandable. referenced.
Error Message: Failed to update tag settings! Unknown Error Message: Failed to update tag settings! Unknown
error: 8004186D. HRESULT = 8004186D. error: 8004186D. HRESULT = 8004186D.
The error reported indicates that the tag cannot be Properly configure the inhibit tag to be a tag other than
updated, however there is no indication that the result of itself.
the tag not being updated is because the inhibit tag is a
self- referenced tag.
COMP-CN-7000-175838
Control Engineering Configurable Function Code feature The Configurable Function Code designer should
does not identify a configuration issue when the number of properly configure the Configurable Function Code
output mapped in the Output Mapping dialog does not such that the number of Shape Outputs matches the
match the corresponding Configurable Function Code number of output mapped in the Output Mapping
shape output. dialog.
COMP-CN-7000-168724
When the connection with Control Engineering is lost, Close the project, Close the Workbench. Open the
communication with other applications in the work bench Workbench, open the project. Communication between
are not automatically re-established. the S+ Engineering applications is re-established.
COMP-CN-7000-172133
Configuration for Configurable Function Blocks (CFB) is not No workaround.
fully supported in the S+ Engineering 2.1 or 2.2 releases. Suggest to rework the CFB defined function blocks
using the new Configurable Function Code
COMP-CN-7000-165412 functionality.
When the user configures a turbine module using the As designed.
Turbine Configuration right-click option at the turbine The turbine module CLD must contain a FC 248.
module, an error message may indicate “An error occurred Properly configure the turbine module function block
during SDTM configuration”. logic in the CLD to include a FC 248. It is recommended
to use the defined ABB_CH_TP01, ABB_CH_AS01, and
ABB_CH_VP01 system templates when configuring
turbine modules as these templates contain FC 248 and
standardized supporting logic.
COMP-CN-7000-189323
22 8VZZ001554T2200 A

Cannot manually modify a Controller configuration Modify the controller configuration by modifying the
containing a Black Box CFC using the Configuration Viewer Control Logic Documents or using the Monitor and
application. Tune application with SAVE of the modified
COMP-CN-7000-186969 specifications. Recompile the Controller configuration
COMP-CN-7000-187008 and download to the Controller.
Data Browser not updating after renaming DNP3 signals. When rename a tag in DNP3 Connectivity interface, a
message in the WB message window identifies that a
rename command is issued.
COMP-CN-7000-185846 The data browser view must be refreshed to see the tag
change.
Cross Reference properties (IREF/OREF) are case sensitive As designed.
with the S+ Engineering 2.1 release. Confirm the Cross Reference properties (IREF/OREF)
COMP-CN-7000-143945 when creating a Control Logic Document.
When using a Rosemount 5300 v4.1 device, the configured Modify the default config.ini file located in the
timing parameters may need to be extended to ensure following directory:
communication between Field Engineering, the control C:\Program Files (x86)\ABB Symphony
hardware, and the device. Plus\Engineering\Composer Harmony\DTM\ABB
COMP-CN-6500-205275 HAIHAO805 DTM
Increase the following timeout parameters to 600000
connect=600000
disconnect=600000
transaction=600000
Save the modified config.ini file to the following
directories:
C:\Program Files (x86)\ABB Symphony
Plus\Engineering\Composer Harmony\DTM\ABB
HARTSDIO DTM
C:\Program Files (x86)\ABB Symphony
Plus\Engineering\Composer Harmony\DTM\ABB
HAIHAO805 DTM
Restart S+ Engineering so that the Control Engineering
and Field Engineering processes can read the new
config.ini file defaults and allow more time for
communication.
When configuring and downloading the configuration file Control Engineering and Field Engineering
of a SPC700 with PDP800 Profibus Master with a Cavotec configuration for the Cavotec Radio Controller Profibus
Radio Controller Profibus GSD file, the SPC700 controller using GSD file is not correct. When the Cavotec Radio
module goes into Error Mode. Controller is configured, the user must unassign the
COMP-CN-6400-208344 CLD from the module and then delete the CLD from the
20190326-992116 controller. The SPC700 controller will then transition to
Execute Mode.
COMP-CN-6400-208758
COMP-CN-1400-208681
While performing Disturbance Testing with Field Masters No workaround.
(PDP800 or HA0805 as example), an incorrect popup
message is displayed with “Upload Failed” text instead of
“Download Failed.”
COMP-CN-6000-32990
COMP-CN-6000-40453
8VZZ001554T2200 A 23

S+ Engineering for Harmony, Control Engineering, the Refer to Knowledge Bank Article(ABB20170502KB0001).
Update Device Cross Reference feature is supported when The cross reference links must be updated manually for
the device CLD is configured using either the product's the device configuration.
system template or a “generated CLD”. This feature is
currently not supported when User defined templates are
used to configure the device CLD.
COMP-CN-6400-133852
COMP-CN-6400-156308
ABB20170502KB0001
S+ Engineering, Control Engineering, when copying a CLD Works as designed.
containing a Configurable Function Code (CFC)
from one project (source project) to another project
(destination project), the CFC needs to be installed in
the destination project.
COMP-CN-6600-141144
S+ Engineering, Control Engineering, there is no option to A new Configurable Function Code must be created.
copy and create a new Configurable Function Code in the
Exchange or within a User Folder in the Exchange.
COMP-CN-6500-111129
S+ Engineering, Control Engineering, display of mixed The engineer must type words in reverse order. As
English and Right to Left language words reversed for example, Tank Level High would be entered as High
some text fields in the Data Browser when the machine is Level Tank for languages written right to left.
set for Right To Left language (as example, Hebrew).
COMP-CN-6600-147487
Cannot download and modify or upload a configuration to Refer to Product Bulletin (3BUA002453).
an IIT02 or IIT12 module. Control Engineering displays the Control Engineering does not allow the user to
error “Fatal 104 (ICI): Function block is not valid” when download a configuration into an IIT02/12 at module
attempting to download the module configuration that address zero or two in the Composer project tree.
includes a Function Code 202 into an IIT02/12 module. Control Engineering does not recognize address zero
as a valid module address for the IIT02/12 module
types. The IIT02/12 requires some configuration
updates to setup the serial ports, so the user does need
to be able to make these configuration changes. A
workaround for the issue is to set the module address
of the IIT02/12 hardware to one by changing pole 8 of
dipswitch SW3 to a 1. Change the module address of
the IIT02/12 in Composer project tree to one. Download
the configuration of the IIT02/12 at module address
one from Composer. Restore the module address of the
IIT02/12 hardware to zero by changing pole 8 of
dipswitch SW3 back to a 0. Restore the module address
of the IIT02/12 in Composer project tree back to two
for monitoring and status reporting. The specifications
(specs) of function code 202 can also be updated
without changing the module address of the IIT02/12
hardware or in Composer project tree. In Composer,
right-click on the IIT02/12 module in the project tree
and then select Run Time > View Configuration
function. Clear the All Blocks option and enter the FC
202 block number 1 in the "Block Range" in upload
window. Select the function code 202 that users want
to update. Change the specs of the function code and
then click OK.
COMP-CN-6000-31062
24 8VZZ001554T2200 A

HART channels are not getting updated properly or not able Delete operation will delete from both Control
to delete the device from Field Engineering, if device Engineering and Field Engineering.
creation is manually aborted.
COMP-CN-6100-33718
The Data Browser “Select View” command may fail if the Use only alphanumeric characters in view names.
view name selected contains apostrophe characters.
COMP-CN-5010-001
During Online configuration, when the backup controller No workaround. Wait at least a minute before
resets, it may take a minute or more to complete and there determining that the process has stalled and taking
is no indication in Control Engineering that it is still waiting other actions.
for this process to complete.
COMP-CN-4200-001
Specification values for Function Codes 26 and 42 go back Prior to changing OREF descriptors connected to
to their previous values when the function codes are bound Function Codes 26 or 42, it is recommended to check
via cross-references and the OREF descriptors are cleared the specification values and ensure they are correct
and the option to clear matching IREF descriptors is afterwards.
chosen.
COMP-CN-4100-002
When performing Online configuration with a mismatched No workaround.
pair of controllers (BRC400 & BRC410), the “Online
Configuration” Window (which contains the “Test” and “Go
Back” buttons, etc.) does not update the backup controller
type after the new configuration tests successfully. The
primary controller type is updated whether users Accept or
Go Back, but backup controller type appears to be static.
COMP-CN-5100-006
Control Engineering does not support multiple compile Works as designed. No workaround. When compiling a
operations on the same project simultaneously. controller module configuration, the database records
COMP-CN-6300-64430 are locked. Thus, user must wait until the compilation is
finished before starting another compilation.
When upgrading Control Engineering Harmony projects, User must re-implement the tag filters after upgrading
the user defined list of tag filters are not transferred to the the project.
upgraded project.
COMP-CN-6200-49511
When configuring Control Logic with S+ Engineering for Works as designed. The database record is being
Harmony, a user may experience an Object Lock or Record accessed by another user or process. The user cannot
Lock message. edit data when the record is locked by another user.
COMP-CN-6400-110521 Acknowledge the message box and retry the operation.
8VZZ001554T2200 A 25

S+ Engineering, Control Engineering, the AI830 DTM text For S+ Engineering, Control Engineering, the engineer
information for the AI830 range selection is ambiguous and must manually modify the channel specifications to the
is as follows: correct value for proper RTD configuration.
13th item - Text: -200..880C Pt100 U ---> Pt100 - Follow the steps below:
200..880C US Ind Std When compiling for the 1st time, compile after Update
15th item - Text: -200..880C Pt100 U ---> Pt100 - FC data option selected.
200..880C US Lab Std Then Manually modify the channel specifications to the
Thus the engineer is unable to automatically configure a correct value for proper RTD configuration.
channel as "US lab standard Ohm platinum RTD On subsequent compile operations, do not use the
(TCR=0.003926)" in which case S2 = 200. The RTD channel is Update FC Data option. This option will overwrite the
wrongly configured as "US industrial standard Ohm data entered manually above.
platinum RTD (TCR=0.003926)" in which case S2 = 201.
COMP-CN-6600-166520
COMP-CN-6600-168585
When upgrading a project to the latest S+ Engineering On project upgrade, navigate to Composer Field
release, the list of supported Field Masters is the list (Library Structure > Engineering Definitions > Field
identified in the project prior to upgrade thus not those Devices) and scan for current supported Field Master
supported in the latest S+ Engineering release. DTMs. The DTMs will be loaded automatically after scan
COMP-CN-6500-113329 process if not available in projects library.
If a redundant control unit is configured (HPC800 or Refresh the Navigator view tree structure.
SPC700) and the controller address is changed, then the
Control Engineering Navigator view will not display the
updated address until the tree is refreshed.
COMP-CN-6200-51017
If the Data Browser view is modified and the user is still Save the modified browser view prior to exiting S+
working in that modified browser view without saving it Engineering.
and the user attempts to close S+ Engineering, then S+ As alternative, when using the Data Browser view and
Engineering becomes not responsive. As example, view the making changes to the selected view, switch to the
EUD list in the Data Browser view and sort in EUD ID document view BEFORE attempting to close the
ascending order. When navigating away from the Data project. As part of this work flow, the user is asked to
Browser view to Project Admin, there is no message box save the changed data browser view. Navigation to
asking the user to save the changed Data Browser view. Project Admin to CLOSE the project is successful.
COMP-CN-6400-127407
ABB20160623E0015
COMP-CN-6400-128329
COMP-CN-7000-134484
COMP-CN-7000-184468
The Control Engineering navigation tool only supports the As designed. The Control Engineering tool only
display and configuration of redundant controllers. This supports the display and configuration of redundant
tool does not support the display of redundant networks, controllers.
field masters (PDP, HAI805, HAO805, AI02, AO02, AI05,
A005, …), field slaves (CI840), or field I/O modules (S800
I/O modules).
COMP-CN-6300-66930
26 8VZZ001554T2200 A

The Tag Name length and Tag Description length are Engineer to confirm that the Tag Name and Tag
console dependent yet not enforced. Description configuration is within the identified
constraints.
Max Length
Max Length
Console Tag
Tag Name
Description
S+ 32 64
Operations
800XA for 32 64
Refer to S+ Engineering 2.2 Harmony engineering user

manual (2VAA000812*) for additional console or Tag limits.
COMP-CN-6200-61582
COMP-CN-6300-69025
ABB20141219-0083
The hSyscfg Help document is not current. Refer to S+ Engineering 2.2 Harmony engineering user
manual (2VAA000812*) or S+ System Virtual PNI
installation & configuration user manual(2VAA003419 F)
for current information.
COMP-CN-6600-162892
In S+ Engineering for Harmony, the Control Engineering As designed for S+ Engineering.
Hardware Structure Import/Export functionality is not
designed to support CI850 with IEC 61850 I/O
configuration or SCI200 with IEC 104 or DNP3 I/O
configuration or SPC700 Modbus Configuration.
COMP-CN-6300-67092
In S+ Engineering for Harmony, the Bulk Engineering and As designed for S+ Engineering.
Topology functionality is not designed to support SCI200
with IEC 104 I/O configuration.
For more information, refer to Connectivity Engineering
section > IEC 60870-5-104 Configuration in S+ Engineering
2.2 Harmony engineering user manual (2VAA000812*).
COMP-CN-6300-66926
Topology functionality is not designed to support SCI200
with DNP3 I/O configuration.
For more information, refer to section Connectivity
Engineering DNP3 Configuration for the workflow to
configure SCI200 with DNP3 I/O configuration in S+
Engineering 2.2 Harmony engineering user manual
(2VAA000812*).
COMP-CN-6500-66926
Topology functionality is not designed to support CI850
with IEC 61850 I/O configuration.
For more information, refer to section Connectivity
Engineering IEC 61850 for the workflow to configure CI850
with IEC 61850 I/O configuration in S+ Engineering 2.2
Harmony engineering user manual (2VAA000812*).
COMP-CN-6300-66925
8VZZ001554T2200 A 27

The network icon remains unchanged when a control As designed. The icon representing INFI-NET versus
network type is changed from INFI-NET to PN800. PN800 is updated on a Navigator Refresh. After
COMP-CN-6300-63628 Refresh, the icon is correct.
Field device masters support the RBSTAT keyword for The S800 Analog Output and Digital Output modules
determining the location in the PROFIBUS telegram of support RBSTAT as a hardware function. The S800
readback status on output values. Control Engineering Analog Output and Digital Output module DTMs do not
does not set the RBSTAT value from DTM configurations. provide a RBSTAT indication to automatically configure
When configuring PROFIBUS S800 I/O modules for Analog the FC string specifications.
Output or Digital Output, RBSTAT= is not added to the
function code string specification.
COMP-CN-6000-25496
COMP-CN-6300-63414
When using the S900 IO DTM with the setting State LSB, Only allow MSB and/or NoState for S900 UINT15
the AI930 and AI950 modules are not receiving data modules.
correctly because the location of data in Spec 23 is Alternatively, manually modify Analog Input Module
incorrect. The values from these modules read 0*. configuration FC 222 - ANALOG IN/CHANNEL S23 from
DATA x:6 to DATA x:7. Similarly, modify Analog Output
Module configuration FC 223 - ANALOG OUT/CHANNEL
S23 from DATA x:6 to DATA x:7.
COMP-CN-6600-167758 On subsequent compile operations, do not perform an
Update FC Data operation else the modified
COMP-CN-6600-168587
configuration will need to be corrected again.
Copy/Paste of CI850/IEC61850, SCI200/IEC 60870-5-104, As designed.
and SCI200/DNP3 devices is not supported.
COMP-CN-6200-48021
COMP-CN-6200-47800
COMP-CN-6200-47530
Re-engineering to rename networks, controllers, field Follow these steps while performing rename function in
masters, and field devices is not supported between re-engineering:
Topology Design and Control Engineering applications. 1. Explicitly delete the network, controller, field master,
or field device that is planned for rename operation.
2. Create the required network, controller, field master,
COMP-CN-6600-159752 or field device with the new name.
In the Control Engineering configuration for PROFIBUS Delete components in the hardware structure starting
and/or HART, Field Engineering may become not with the lowest level. For example, I/O modules (S800
responsive when an engineer deletes the hardware I/O), then Field Slaves (CI840), then Field Masters
structure (network, controller, and devices) at the network (PDP800, HAI805, HAO805, AI02, AO02, AI05, AO05),
level. then controllers, then control units, and then finally
COMP-CN-6100-40306 control network.
The S+ Engineering for Harmony does not include CLTs for

The S+ Engineering for Harmony only contain
some S800 and S900 I/O cards. templates for modules/devices that have been tested
and officially supported. The reported “missing” S800
and S900 modules have not been officially validated. As
a workaround, users can make their own user-defined
COMP-CN-6100-40010
templates to work with any PROFIBUS module/device.
CLD Import progress bar counter does not count Control None.
Logic Documents correctly. CLD Import operation is not impacted.
COMP-CN-6000-26471
28 8VZZ001554T2200 A

CLD Block Manager operation for a field configuration is At the controller level or any hardware device level, in
performed for each CLD. There is no option to select the left window pane, use the F10 feature to list all the
multiple CLDs. CLDs. In right window pane with the list of CLDs, select
COMP-CN-6100-40233 the CLDs, at the right click menu select Block Manager
for Auto Block of the CLDs.
Cutting and pasting CLDs (or Controllers or control units or Use Copy then Paste, and then Delete items from
IO modules) to a different project may give an error. source project in a second step.
COMP-CN-6000-13172
Deleting CLDs from a project while attempting to copy Do not delete CLDs when any user is attempting to
CLDs to a different project may result in an unexpected copy them or use them in similar ways.
error.
COMP-CN-6010-13076
When copying CLDs or hardware nodes (controllers, If the errors cannot be determined and corrected, the
control units, and control networks), tags are copied as recommended procedure is to:
well. 1. Export the desired tags.
This includes tags defined but not linked to function codes
NOTE: The Data Browser can be used to export the
in CLDs. Various errors may occur when Composer tries to required tags by selecting the appropriate hardware
copy these tags. Conditions generating these errors can be
node in the System Architecture tree and then using the
if console contexts are different between projects and the
Data Browser Export function.
values in tag fields are invalid for the destination context,
2. Import the tags into the destination project
N90Status tags missing node information, etc. correcting any errors found.
3. Copy the CLDs or hardware objects without tags
(using the new Don’t Copy Tag Data option) (Tools >
COMP-CN-5010-005 Options > Copy Options).
The CLD Export to Excel does not support export to a *.xlsx Use the *.xls document type for the CLD Export to Excel
document type. operation.
COMP-CN-6301-112343
When multiple users working on a project and if a user is As designed. Suggested the CLD Import operation to
performing CLD Import operation, engineers on other be performed exclusive and be complete before other
clients should observe that a CLD impacted by the CLD engineers work to modify data on a CLD imported
Import operation is in read only mode. before the CLD Import operation is completed.
COMP-CN-6500-115899
The grid resolution on CLDs created using Update CLD for a The user must change to a grid resolution of 10 X 10 or
IEC 60870-5-104, DNP3, and Modbus configuration does in some cases even 5 X 5 to make signal line
not match the user configured grid resolutions. The connections.
placement of the function codes on the grid and the line
resolution results in difficulty in connecting user generated
signal lines.
COMP-CN-6500-125343
[Automation Architect] Internal Microsoft ADO errors Retry the operation when it can be done without other
(0x800a0e21) have been reported when doing repeated users handling (copying, editing, unpacking, importing,
multiple operations in Automation Architect involving etc.) CLDs.
creating cross-references while other users on different
workstations are simultaneously copying large numbers of
CLDs (with respective cross-references). The error
displayed and the transaction rolled back, so no data is lost.
COMP-CN-5010-009
8VZZ001554T2200 A 29

Cannot copy a SD IO configuration from a controller in one
Use the Hardware Structure Import along with Pack and
project to a controller in a different project. Unpack of CLDs to copy a controller configuration
using SD IO modules from one project to project:
1. Pack the CLDs at project, control network, control
unit, or controller in the source project.
2. Perform a hardware structure export at project,
control network, control unit, or controller in the source
project.
3. Perform a hardware structure import at project,
control network, control unit, or controller in the
destination project. This step creates the hardware
structure in the destination project.
4. Unpack the CLDs at project, control network, control
unit, or controller in the destination project. This step
creates the CLDs at the controller level.
destination project. This step moves the CLDs from the
COMP-CN-6200-41501
controller level to the device level.
S+ Engineering, Control Engineering, Pack/Unpack 1. Pack the CLDs at project, control network, control
functionality does not preserve the type of network or unit, or controller in the source project.
control unit. 2. Perform a hardware structure export at project,
project.
COMP-CN-6100-50377 controller level to the device level.
Interchanging of tag name between devices is not possible, No workaround.
during signal re-import, Error identified and indicates that NOTE: Manually change the tag names for the swapped
the Tag is already available for a different device. exception report function code in specific Control Logic
COMP-CN-6300-137499 Diagrams.
COMP-CN-6300-116596
COMP-CN-6300-177558
Control Engineering did not generate the correct number of For the FAU810 and other devices that have logical
blocks for FAU810 when using the ABB DTM FAU 810. modules (groups of channels), refer to Special Notes on
Using Field Devices with Logical Modules in the S+
Engineering 2.2 Harmony engineering user manual
(2VAA000812*) for information.
Use GSD and .CSV files to configure the device in Field
Engineering. Use a Control Engineering CLT or
configure a CLD with the correct number of function
COMP-CN-6010-30544 code blocks for these devices.
30 8VZZ001554T2200 A

Use of indirect cross-reference links is not currently No workaround. The IREF in the destination controller
supported. If user has one FC output connected to an should reference the correct OREF in the source
OREF, and that OREF is connected to an IREF in a different controller and not the indirect OREF. Alternately, note
CLD where it only connects to another OREF that the address and block number specifications can
(e.g., to marshall OREFs), the compiler will not identify the be filled in manually in the FC205.
correct source block output number when the source is in a
different controller (e.g. when using FC205 AIL/CW).
COMP-CN-6010-30556
Control Engineering FD Master Name, Field Engineering The current behavior is that if the Control Engineering
device name, and FC 227 (Gateway) spec 1 (Harmony FD Master Name is changed on the next Field
Communication HCB Label) should all match. Engineering Update FC Data, the Field Engineering
Device name will also be changed to match. The master
device name cannot be changed in Field Engineering.
That action must occur indirectly by changing the name
in Control Engineering. The FC 227 (Gateway) spec 1
(Harmony Communication HCB Label) needs to be
changed manually as the engineer must recognize that
COMP-CN-6100-32306 the PDP800 module needs to be re-labeled.
Modbus re-engineering: An error is displayed when adding Close and relaunch the workbench to perform import
signals to an existing MODBUS server/client CLD. and update CLD again.
COMP-CN-6600-155821
Modbus re-engineering: Modbus deletion of signals does Manually delete the signals without using 'DELETE' re-
not work when performing re-engineering. Deleting a tag engineering option from template engineering.
deletes the function code associated with the tag, this
disrupts the connection of the previous function code. So
the XY position of the newly added signals are not placed
properly in the existing CLD.
COMP-CN-6600-152621
When configuring a system for IEC 61850, IEC 104, DNP3, or Delete the misconfigured/disappearing signal lines.
Modbus TCP, and connecting an OREF to an existing signal Manually reconfigure the signal lines from the FC
line connecting to the NEXT input of a set of signals, most output to the OREF and the NEXT input of the set of
of the newly added signal line disappears after the signals.
connection to the OREF is configured.
COMP-CN-6500-127105
When configuring a system for IEC 61850, IEC 104, DNP3, or Configure the connected OREF/IREF logic, recognize
Modbus TCP, and connecting an OREF to an existing IREF that the IREF connection remains not resolved. Save the
that was created by an Update CLD operation, the logic in CLD. Open the CLD. The configured connected
the created CLD does not resolve the function code input OREF/IREF logic is resolved for the input IREF
IREF connection. It remains SOLID RED SQUARE. connection. The connection is an OPEN BLACK SQUARE.
COMP-CN-6500-127208
CLD Import/Export Utility formats the EXCEL file such that As designed.
the CLD export puts function code specifications those are
ASCII strings after the field labeled Spec64 in a field labeled
“StringSpec1.” There are 10 contiguous fields (StringSpec1
through StringSpec10) specifically for function code
specifications those are ASCII strings.
COMP-CN-6200-51833
While changing the device name (all field masters) in As designed.
Control Engineering's tree structure, the device label is not Manually change the label name in the CLD.
updated in the module's CLD.
COMP-CN-6300-63614
8VZZ001554T2200 A 31

In S+ Engineering for Harmony, when configuring Manually modify the S23 specification from TYPE=S16
PROFIBUS S800 I/O modules DI810 and DO810, the S23 to TYPE=U16.
presents an incorrect status TYPE.
COMP-CN-6300-64461
If Field Engineering device templates (e.g., S800 IO Field device template instances shall be created only
modules) are instantiated through Topology Design, then through Control Engineering with the proper template
the devices are created in Control Engineering, but the selection.
related CLDs are not created.
COMP-CN-6300-69548
Cannot copy a Field Master configuration in S+ Engineering
Use the Hardware Structure Import along with Pack and
2.1 from one controller to another controller in the same
Unpack of CLDs to copy a controller with Field Master
project. Cannot copy a Field Master configuration in S+ configuration from project to project:
Engineering 2.1 Control Engineering from a controller in one
project to a controller in a different project. unit, or controller in the source project.
project.
COMP-CN-6000-32106 controller level to the device level.
Removing a CFB from a project where the CFB was To remove a CFB, first remove all instances of the CFB
previously instantiated on a CLD may cause an internal from CLDs where it has been used. Then recreate the
system error when viewing or compiling that CLD. function code database by starting from the default
COMP-CN-6010-94945 and merging in only the desired CFBs.
For Configurable Function Code (CFC) functionality, the Open the Input/Output/Spec mapping dialog box from
user is not able to close Logic or Shape editor if the S+ exchange rather than the GMC exchange.
Input/Output/Spec mapping dialog box is opened from
GMC exchange.
COMP-CN-6500-113651
In a multi-user system, it is important to realize that a user As designed.
may get a notification “Cannot open CLD” when another
user is compiling a controller.
COMP-CN-6210-75654
COMP-CN-6210-75055
ABB20150909E9506
When a PROFIBUS device is configured in the system and As designed.
the PROFIBUS device CLDs were created using a CLT, the The unused IREF (input cross reference) will be
Update Device Cross Reference feature does not remove identified during a compile operation. It is then the
the IREF (input cross reference) at the last function block. responsibility of the engineer to make the decision that
COMP-CN-6400-114435 the IREF will not be required and thus should remove it.
32 8VZZ001554T2200 A

When compiling a controller the following error message S+ Engineering for Harmony, Control Engineering,
may be reported: compile feature is enhanced to automatically open and
“Control Logic Document xxxxx was not closed properly. close CLDs when marked invalid. A message is
Try opening CLD to correct. May have been open for Edit at displayed to inform the user that this action was taken.
the time of System Failure”.
COMP-CN-6300-91138
COMP-CN-6600-155661
ABB20151026E3312
ABB20151110KB0004
During the Verify operation of either the Online Controller Compile the controller. If warning messages related to
or an older CFG, S+ Engineering may become not “Improper Signal Connections” are displayed, then
responsive. perform the following procedure:
This issue is caused by a CLD that has not been closed 1. Double-click the warning to open the related CLD.
successfully. 2. Save and close the CLD.
ABB20160225E0127
COMP-CN-6300-103884
COMP-CN-6500-104414
When multiple users are working on a project, when a user Acknowledge the ADO error. Reopen the Control
is performing a copy/paste operation of a large number of Engineering.
CLDs in parallel with a different user performing a parallel
function, for example, pack/unpack a large number of
CLDS, Control Engineering may display ADO error.
COMP-CN-6500-117400
Grid settings keyboard shortcut no longer functions. This is not a bug in Control Engineering. Microsoft
Entering Ctrl+Shift+0 does not cause the grid settings to changed the default key sequence for switching
revert to 100x100 ratios. keyboard layouts in Vista - which takes precedence over
Control Engineering's use of Ctrl+Shift+0.
The workaround is to follow the given steps to change
the default key sequence in Windows and then
Ctrl+Shift+0 will work in Control Engineering.
Refer to this Microsoft knowledge base article
http://support.microsoft.com/kb/967893 stating that
Ctrl+Shift+0 is the default hot key sequence to switch
input language keyboard layout in Windows Vista (and
later), and that it may conflict with other software
using that sequence.
Following is the suggested workaround:
Remove the shortcut assignment to make the
application work as expected.
1. Click Start, and then Click Control Panel.
2. Double-click Regional and Language option.
3. Click Keyboards and Languages, and then Click
Change keyboards.
4. Click Advanced Key Settings, and select Between
Input languages.
5. Click Change Key Sequence.
6. For Switch Keyboard Layout, select Not Assigned.
7. Click OK to close each dialog box.
COMP-CN-6100-38254
8VZZ001554T2200 A 33

When configuring a CI850, the S+ Engineering -Control Logical Node prefix and suffix should be created only
Engineering -Create CID Signal configuration, allows to with capital case letters, small case letters are not
create a logical node prefix starting with small letters. This allowed in logical node prefix or suffix.
is not supported functionality.
COMP-CN-6200-53222
Drag and drop functionality to copy CI850 and IED devices Do not use Drag and Drop.
in Control Engineering Harmony is not supported.
COMP-CN-6200-49132
The packing and unpacking of complex or large numbers of The packing and unpacking functions have been
control logic documents may fail if there are configuration
improved however the packing and unpacking of large
problems or incompatibilities between projects or quantities of control logic documents should be
sufficiently large numbers of control logic documents in the
avoided. Refer to the following guidelines when packing
unpack file. and unpacking:
Avoid using wild card characters in tag names and
cross reference names. Wildcard characters include?,*,
_, #, and%.
Avoid using tag names and descriptions that are longer
than those supported in the destination project
context. Ensure all control logic documents will compile
(all errors corrected) before packing.
Ensure all control logic documents contain valid
function codes for the controller module.
Pack and unpack smaller quantities of control logic
documents at a time. The context menu options
(Unpack CLD Selection window) now provide expanded
selection capabilities.
If necessary, unpack to an empty project and copy the
control logic documents to the final destination
project.
If necessary, export tags to the destination project first
(this may reveal additional configuration errors with
the tags), unpack the control logic document, and (if
necessary) use the Tag Sync feature to reconnect the
tags to the control logic documents.
COMP-CN-6100-36513 NOTE: Also refer to knowledge base article
(ABB20130408KB0004). Control Engineering unpack
COMP-CN-5020-013
feature does not restore Logic State Descriptors.
COMP-CN-5020-014
The Lock All Records and Auto Lock features may result in No workaround.
“Object locked” errors when attempting to make changes
to the locked records.
COMP-CN-5100-013
When a FC 63 or 64 has text in all 8 cross references and has Click Apply then OK, not just OK, when editing the
S3-S10 tuned to non-default numbers, if a change is made specifications for these function codes and changing
to one of the cross references, specs S3-S10 reverts back to bound cross-references.
default values. Also, if a FC64 has text in all 8 cross
references and has S3-S10 tuned to non-default numbers, if
the cross-reference text is deleted for one of the inputs, the
tuned spec remains tuned.
COMP-CN-5000-004
34 8VZZ001554T2200 A

Errors may occur during copy/paste of tags or CLDs with Restrict tag names to using alphanumeric characters.
tags if tag names contain non-alphanumeric characters. Control Engineering uses Microsoft database
technology and Microsoft recommends not using the
following characters:
Space
Apostrophe '
Quotation mark "
Apostrophe '
At sign @
Grave accent `
Number sign #
Percent %
Greater than sign >
Less than sign <
Exclamation mark !
Period .
Brackets [ ]
Asterisk *
Dollar sign $
Semicolon ;
Colon :
Question mark ?
Caret ^
Braces { }
Plus sign +
Hyphen -
Equal sign =
Tilde ~
COMP-CN-5021-004 Backslash \
Using the Lock All Records function in the Data Browser No workaround.
view may result in other Control Engineering instances Open the project in both Control Engineering instances
being unable to open that project. prior to using the Lock All Records function (when
COMP-CN-6000-8088 possible).
When opening a CLD and then closing the CLD without No workaround.
making changes, Automation Architect may prompt to save There are various checks performed by Automation
changes. Architect when opening a CLD (e.g., line connections)
which may change non-visible contents of the CLD,
which triggers the prompt to save changes when
COMP-CN-6000-8064 closing. The prompt is an indication that something
was corrected or updated internally and the
recommendation is to perform the save.
8VZZ001554T2200 A 35

S+ Engineering, Control Engineering, Pack/Unpack featurePerform the following procedures:
does not support restoring a fieldbus configuration or an
SDIO device configuration into a new project. The CLDs in
unit, or controller in the source project.
the configuration can be packed and unpacked but fieldbus
field masters, field slaves, field devices and SDIO modules
will not be recreated. For example, packing a set of CLDs
project.
for PDP800, HAI805, HAO805 or PROFIBUS or HART devices
will pack, and will appear as CLDs in the S+ controller.
controller level.
NOTE: In S+ Engineering, the Hardware Structure
Import/Export functionality should be used to
automatically create the field master, slave, and I/O
module devices in Control Engineering and to Assign
CLDs to these devices.
Refer to sub-section Control Engineering
COMP-CN-6600-164495 Import/Export Hardware Structure in S+ Engineering
2.2 Harmony engineering user manual (2VAA000812*)
COMP-CN-6000-23248
for more information.
If a CLD assigned to a field device is left open in As designed.
Automation Architect and users try to delete the field Make sure all CLDs are closed before attempting to
device in Control Engineering, the device is deleted, but the delete field devices.
CLD is not deleted. It does not immediately show up under
the HC800, but will appear after a refresh or reopening of
the project.
COMP-CN-6010-31701
In S+ Engineering and Control Engineering, when viewing This deficiency only applies to the view, _DataBroswer
tag lists in the Data Browser an icon is displayed in the CLD Tag Single List Minimal. Other view selections work
field for each tag. When this icon is clicked, the CLD will properly. Also the functionality works properly when
open and the associated function block should be selected viewing the global list of tags with this view.
automatically. When using the standard view, As a workaround, modify the view to create a custom
_DataBrowser Tag Single List Minimal, the CLD will open, view with one additional field. Use the customized view
but the associated function block will not be selected for proper functionality.
COMP-CN-6400-133861
COMP-CN-6400-137259
COMP-CN-6400-137260
ABB20160913E0169
ABB20170109KB0002
Control Engineering Configurable Function Code feature The Configurable Function Code designer should
does not identify a configuration issue when an input is remember that 1 input can be mapped to 1 block or
mapped to multiple blocks. more than 1 block however, more than 1 input cannot be
mapped to 1 block.
COMP-CN-6600-157285
36 8VZZ001554T2200 A

I/O modules are allowed to be created under slaves that do None.
not support modules. As an example, the New->Field Check the documentation for the slave modules to
Module option is enabled (not greyed out) for a PROFIBUS determine which ones support I/O modules.
device TTX300.
COMP-CN-6010-31456
COMP-CN-6100-40599
In Topology Design, a CI801 device can be created, In Control Engineering, at the CI801 device, right-click
however, the device will not have an associated CLD until on the device and navigate to the Properties dialog.
the engineer manually configures this CLD in Control Identify to Generate CLD. Identify to Update Device. A
Engineering. CLD will be automatically be created for this device.
COMP-CN-6000-179089
After upgrading Composer Harmony 6.0, 6.0 SP1, or 6.1 As designed. A Composer Harmony 6.0, 6.0 SP1, or 6.1
projects to S+ Engineering, user must make sure that all project identified a INFI-NET/PN800 network as the
device types are consistent in each upgraded network. same network type. In S+ Engineering 1.0 and later,
Composer Harmony uniquely identifies a INFI-NET
network and a PN800 network.
On a project upgrade, the Control Engineering network
type is defaulted to a INFI-NET network. The user must
recognize that a network change is needed and
manually change the network type using the Properties
dialog. An INFI-NET network supports BRC, HAC, and
SEM modules. A PN800 network supports HPC800,
COMP-CN-6200-48949 SPC700 modules,
COMP-CN-7000-172180
Modifications to the combo box size of History Tool Update the default initialization value for the System
through the following System Settings is not working. The Settings entry “RecentFilesComboWidth” to 150 pixels.
modified combo box size values are present between 0 and
300.
System Settings location:
..\Operations\APPS\Layout\RecentFilesComboWidth\
OPE-CN-3000-101567
The configuration of SMS tool is not available in S+ SMS configuration tool is available in S+ Operations >
Engineering. bin folder.
Refer S+ Engineering 2.2 Operations engineering user
OPE-CN-3100-159970 manual (2VAA006938*) for more information.
Full deploy fails for some actions whereas for incremental The entries are to be replaced with different and higher
deploy, there is no failure. number.
OPE-CN-3100-162193
Missing Text appears in the Tag Extra References Tab in No workaround available.
“DIGITAL IN ALARM” Tag configuration Window.
OPE-CN-3100-176751
Modbus multi-driver is unable to receive the values for The data type for the PGIM driver needs to be
Counter32 data type. corrected.
OPE-CN-3100-177149
NDC assigned to tags does not get updated automatically Sync with Operations Engineering from Topology
if performed sync with Operations Engineering in Topology Design should be done manually.
Design.
OPE-CN-3100-179690
8VZZ001554T2200 A 37

The “\” character in the tag name was skipped during tag No workaround available.
import process.
OPE-CN-3100-180271
The lock is not released for export file from Pattern sheet in No workaround available.
the Universal Connect as the file is in read only mode.
OPE-CN-3100-180444
In Universal Connect, the standard data types are not The drop-down with standard/all supported data types
appearing while performing manual mapping. is helpful for the user to select easily irrespective of the
format used in Symphony plus Operations. Drop-down
as UINTEGER for user selection which will be UINT in
SPO should be handled internally. And user should not
be able to change the TAGTYPE in Universal Connect.
OPE-CN-3100-180914
Online engineering is crashed while deploying the Bulk Online engineering workflow can be performed after
SCADA workflow in the Engineering Workbench. Bulk engineering.
OPE-CN-3100-181560
When bulk no. of tags (like 1000,2000,etc.,) are deleted in No workaround available.
Composer-Data Base, it hangs the Workbench for some
time.
OPE-CN-3100-181688
When deploying tag database from Operations Engineering No workaround available.
to Symphony Plus Operations, the column "State 0 is Alarm" Note: PN800 Control Network functions in same way as
changes from "N" to "Y". There is no way to manually before. In case of IEC 60870-5-104 Control Network,
change back. this value shall be changed/updated from the Signal
OPE-CN-3100-181765 Manager and sync with Operations Engineering.
SPO tags name, description, engineering unit, status length No workaround available.
verification allows more than limited characters through
excel import.
OPE-CN-3100-182614
After deployment of the database from S+ Engineering to Engineering server displaying as “Operation server”.
S+ Operations and While selecting the S+ Engineering and The list displaying all the nodes as (OpServer)EngServer
S+ Operations show blank database in the difference name. In case of Engineering server, select “Offline”.
viewer. Reopen the Workbench for one time only.
OPE-CN-3100-183710
Multi monitor information is not able to propagate to No workaround available.
Operations Engineering from Topology Design.
OPE-CN-3100-183880
The Topology Design creates the computers as required Enable “build Client Nodes” option in Operations
and creates the node list containing the servers as Engineering and deploy to all 64 clients.
required. All computers are listed and when deployment to
a client node not listed in Node list are failed.
OPE-CN-3100-183947
Atoms configuration is not properly set and in S+ Edit the C5 Data Processor manually.
Operations is not possible to see tag values changes for
example in Tag Sum.
OPE-CN-3100-187487
AC800M Importer generates tags DB without informations User must edit manually the tags configuration
about alias file. according to the alias designed in S+ Engineering
OPE-CN-3100-188968 Topology.
38 8VZZ001554T2200 A

On S+ Operations server, online values cannot be Create a copy of registry folder and rename as per ICI
monitored or controlled for soft-controller communicating number.
on other than ICI 1&2
OPE-CN-3100-189259
Field Engineering:
In a HART Pass Through configuration (PDP800 with CI840, The PDP800 must complete its failover operation for
HART S800 modules, and HART devices), the Field the Field Engineering Observe operation. When
Engineering Observe operation may stop reading values complete, use Field Engineering to reconnect to the
from the HART devices when the primary PDP800 is HART device and initiate the Observe operation.
stopped with failover to a redundant PDP800.
COMP-CN-6300-69140
DTM500 Library: Upload/Download success message is No workaround. Rely on the connection and
displayed even if the connection is disturbed. Some communication errors provided by communication
DTM500 Library objects (DTMs) will indicate a successful components previous to the final successful message.
upload/download action even if the action has been
disturbed:
Parameter upload successful
Parameter download successful
In most cases, the disturbance has been indicated with
several warnings and errors in advance:
Connection Aborted
Communication Failure
Harmony Error
Fatal 103 (ICI) …
COMP-CN-6000-32990
COMP-CN-6000-40453
COMP-CN-6500-116641
COMP-CN-6500-116643
Workbench:
While importing the IEC 104 IO list in the IEC 104 user As designed. While importing a progress bar is
interface or updating the CLD, users cannot do any work in displayed and the S+ Engineering software is getting
Control Engineering. hanged. When Update CLD function is in progress,
WBCE-CN-1100-59646 users must not interact with the S+ Engineering
software.
Mapping of network drive or share location by Machine's Use the IP address of the machine instead of the
name throws error while lunching the User Management hostname while mapping the network drive.
page.
WBUM-CN-1400-210730
20190606-1196126
Reengineering of protocol change is not supported during No workaround. Particular signal needs to be deleted
bulk import of signals. from signal manager before changing the protocol type
WBBE-CN-2000-102285 for signal.
CLD name is replaced with existing CLD name during the No workaround available. User has to verify the CLD
CLT instantiation without warning message if user name before CLT instantiation.
provides same name during the tag spec update instead of
new/other name.
WBBE-CN-2100-173963
8VZZ001554T2200 A 39

IEC 60870-5-104 vertical engineering either BET or This special data type shall be update in atom database
Connectivity Engineering is not supported to configure the manually.
special data types
(i) M_BO_NA_1
(ii) M_PS_NA_1
(iii) M_ME_ND_1
(iv) M_ST_TB_1
(v) M_BO_TB_1.
WBBE-CN-2100-180922
Tag names are not getting updated during the CLT Make sure that Function Codes are configured either
instantiation when Function Code configured with Bulk with Bulk Engineering Tool script nor tag name in the
Engineering Tool script and tag name in CLT. CLT.
WBBE-CN-2100-186751
Redundant OPC driver configuration support is not No workaround available.
available in SCADA Bulk Engineering Tool.
WBBE-CN-2100-186798
Under Control Engineering, if a Tag is created through the Refer to the S+ Engineering 2.2 Operations engineering
Tag List, then error gets reported in Signal Manager as CLD user manual (2VAA006938-320) for the steps to be
Name is not associated for type N90STA. This error gets performed for Symphony Tags Diagnostic tag creation
reported upon trying to perform synchronize with Signal section.
Manager option for this specific tag type only.
WBSM-CN-2100-187211
User Management prevents the creation of a user with a user management supports the following characters
hyphen (and some other special characters) in the user due to database restriction:
name. • Numeric
WBUM-CN-2110-210712 • Alphanumeric
20190604-1190999 • (_, @,#)
WBUM-CN-2110-210861
During specific scenarios, Span value results in validation User can update the Alarm Limits in Operations
error for the Alarm limits even if it is within the instrument Engineering under respective tag configuration
range. window.
WBSM-CN-2200-200198
WBSM-CN-2200-211025
All the SOE points are listed in the Signal Manager Follow the existing method to configure the INFINET
irrespective of the Control Network i.e. PN800 or INFINET. SOE engineering.
In this version, SOE engineering considered for PN800
network only.
WBSM-CN-2200-205382
NDC matrix cell are protected when cut & paste is Configure the NDC matrix from the drop-down
performed during the NDC assignment. selection in respective cells.
WBST-CN-2200-197059
In Topology Design, there is a restriction of configuring Update Alias.xml file manually with the second \third
more than one OPC server on a single node. OPC server information.
WBST-CN-2200-204115 Refer to S+ Operations Scanner reference user manual
(2VAA000725-320*) for more details
In diagram wizard, server selection and redundant partner No workaround available
information does not populate server names for any
HSI/Historian servers.
WBST-CN-2100-183877
40 8VZZ001554T2200 A

The PNI configuration “Max no of Tags” can not avoid No workaround available
Harmony tags from same controller coming from different
PNIs, which may cause potential communication problem.
WBST-CN-2100-183704
Infi-Net network type is listing as PN800 type in Topology Perform reconcile from Control Engineering to correct
Design. the network type in System Topology.
WBST-CN-2100-179713
COMP-CN-7000-168048
Navigation between Control Engineering and Topology Works as designed. Use the left panel navigation to
Design at the controller level is not supported. move between Control Engineering and Topology
WBST-CN-1000-47661 Design.
In horizontal Connectivity Engineering, few attributes are User has to correct the fields which are listed with
not listed properly like IOA for IEC 60870-5-104 during the validation error and then perform re-import to update
load data action. It results in validation error during re- in the Control Engineering.
import.
WBCE-CN-2200-208048
Import is not allowed during Modbus horizontal User has to keep the server details in one sheet and
engineering when excel sheet contains the server list and client details in another sheet. Perform the import
client list of Modbus signals. sheet by sheet.
WBCE-CN-2200-206794
Upon performing Object Based Engineering workflow and User must filter the signals using the query as tag
after exporting the signals, the signals are created in Signal source type with “Composer Harmony” and update the
Manager with Tag Source as “Composer Harmony”. Further respective information like “EXT” for Modbus or IEC
“Validate or Update Data” gives error. 60870-5-104 and “OPC” for OPC.
WBSM-CN-3200-205789
Batch Data Manager:
Batch Data Manager running in SPC700 is not supported at Batch Data Manager running in HPC800 is supported.
this time.
BDM-CN-7000-185543
BDM-CN-7000-171909
2.4.3 Operation
The following table (Table 2-5) lists the operational issue known to exist with the current release. Solutions or
workarounds have been provided for the issues.
Table 2-5: Known Operation Issues
Issue Workaround/Clarification/Helpful hints

Bulk engineering:
Saved tag manager query in server will not be reflected in Tag manager is renamed to Signal Manager in S+
client machine when tag manager view is already opened Engineering 2.1. User has to switch between different
in the client. modules when new query saved in server node to refresh
WBBE-OL-1100-65662 the view.
When users upgrade a project, the module status of that Users have to manually update the existing module
project is not updated due to the nonavailability of the status.
object names of the module status bubble's.
WBBE-OL-1200-94319
8VZZ001554T2200 A 41
Operation 2. Modifications in 2.2 release
Table 2-5: Known Operation Issues (Continued)

The performance of S+ Engineering slows No workaround.
down, when one of the domain controllers (primary or
secondary) is turned off, while performing tasks related to
User Management, Project Admin, Bulk Engineering and
Topology Design.
WBUM-OL-1200-94320
In CLT Instantiation user interface of Bulk Engineering Enter signal data manually in the CLDs group box of CLT
tool, the FillSeries function from the context menu is not Instantiation user interface.
working while filling signal data in the CLDs group box.
WBBE-OL-1300-113459
I/O assignment function list all the signals and I/O No workaround. I/O assignment and Control
modules which is imported through bulk engineering tool Engineering data are not in sync. This functionality shall
only. Not from the Control Engineering tree structure. be used if the import is performed from Bulk
WBBE-OL-1400-164437 Engineering Tool and CLD is updated.
“Object reference not set” error is reported at times Remove the conditional formatting from the MS Excel.
during the export from bulk engineering tool. Navigate to 'Conditional Formatting >> Manage rules -
WBBE-OL-2200-205913 Select 'This worksheet' and Click 'Delete rule' then save
the worksheet.
System out memory exception error may occur during the Recommended to close and re-open the S+ Engineering
bulk import of 20000 signals consecutively. application to clear memory when consecutive imports
WBBE-OL-2200-206973 are required.
Third party device details are not updated in topology Navigate to topology design, refresh the diagram page.
design during the re-engineering.
WBST-CN-2200-207143
CFC tags are de-linked and incorrect tags are created CFC tags are not listed in the data editor, user has to
during the tag update action from data editor. manually correct the tags.
As alternative, the CLD Export application can be used to
export information from a CLD to EXCEL. Tag names and
tag descriptions associated with the CFC can be
modified in the EXCEL file. The CLD Import application
can be used to import the CFC tag information into the
WBBE-OL-2200-207122 CLD.
Items with “Name” attribute exceeding 50 characters Reduce the length of the “Name” attribute before
leads to deployment issue. deployment.
Example: Ensure the Tagname length is within 50
WBOE-OL-3200-210084 characters.
For SPC700 running IEC104 backbone, when the controller Refer to SPC700 SD Series Controller user manual
is in error mode, the module status report does not (2VAA003572*) for correct decoding of the SPC700
interpret the error codes correctly. module status report information.
COMP-OL-7100-208332
Prior releases of S+ Engineering do not support As designed.
communication with recently released Control and I/O S+ Engineering 2.2 is enhanced to support
hardware - Control Unit/Controller pairs. communication with the recently released SPC600.
COMP-OL-7100-203375
Battery Low Status bit not correctly reported by SPE when Create control logic that uses FC 95 Module Status
using BRC4xx controllers. Monitor to alarm for Battery Low Status.
COMP-OL-7010-206993
42 8VZZ001554T2200 A

Loading CFG to Controller resulted in error - Warning 69 Repeat the operation to load the CFG to the Controller.
(SUBS): Reply to general message was too small. Block
xxxx FC yyy.
COMP-OL-7000-138551
Publish CLD of a CLD with multiple sheets fails to group Modify a CLD Name to avoid using the double quote "
the sheets under a single node if a double “special special characters. If the CLD Name is not modified, the
character is present in the CLD Name. The Publishing of published CLD navigation is still functional for each
the CLD is repeated with each Publish CLD operation thus sheet published. To address the issue regarding multiple
multiple published CLD sheets exist. copies of the published CLD sheets, use the View and
Monitor Publish CLD option to Remove Drawings to
delete published CLDs and thus avoiding a multiple
copies of the same published CLD.
COMP-OL-7000-187399
The S+ Engineering Control Engineering connection to None. This is the current design.
communication modules is used for all online related
runtime activities (inspect, download configuration,
download firmware, and so on). The Disconnect button
will disconnect S+ Engineering Control Engineering from
an application executing online related runtime activities.
Thus, there may be times when the Inspect Window will
remain open.
COMP-OL-6500-114432
S+ Engineering (Control Engineering) may stop As designed. The Monitor and Tune feature is designed
responding in Monitor and Tune online mode when to monitor all the function codes that are visible in the
switching between different sheets in a single CLD that current view, whether that be the whole sheet or zoomed
contains 30 sheets or more. in on a single function code. It is designed to monitor the
current sheet.
The monitor value refresh rate is a result of the number
of function code outputs being monitored and the
communication properties.
COMP-OL-6500-117180
When using the Inspect function in Control Engineering Close the Inspect window. When the Inspect window
and selecting a VPNI as the communication interface, closes, the S+ Engineering should return to normal
while inspecting if the VPNI is restarted, then the S+ operation.
Engineering may stop responding and take most of the
CPU cycles.
COMP-OL-6500-124532
The S+ Engineering module problem report does not Engineer can obtain the requested data from the S+
inform engineers which node is offline Operations Harmony Status problem report. This report
identifies which node(s) is/are offline.
COMP-OL-6500-175236
COMP-OL-6500-177699
20171025-310913
At times, there is a delay in opening S+ Engineering for This is not an S+ Engineering (Control Engineering)
Harmony on either a reboot or log off/log on procedure issue. Wait for two minutes and then retry to open S+
with the following message: Engineering
“Base License request failed. Temporary Licenses have
been granted.”
COMP-OL-6400-110515
External applications cannot be added into the ribbon No workaround.
toolbar using Customize dialog box.
COMP-OL-6400-113810
8VZZ001554T2200 A 43

On a single computer, one cannot simultaneously use On a single computer, one can use a single HART Device
multiple HART Device DTM dialogs if they are DTM dialog when communicating through the AI02 or
communicating through the AI02 or AO02 modules. AO02 modules.
COMP-OL-6301-75680
When using IEC 61850 configured in a system using Change the S+ Engineering for Harmony machine
Chinese language Windows operation system, the CCF file Operating system to English language before
cannot be downloaded to the CI850 module. downloading the CCF file, after that user can change to
The *.scd file contained Chinese characters which cannot Chinese language.
be interpreted.
COMP-OL-6300-107936
COMP-OL-6300-126440
ABB2016041400047
Excessively long file download times. If users have long communication times with IET800
CIUs, ensure that the Global Network Adapter Parameter
Tuning checkbox in hSysCfg for that ICI is checked for
the network adapter that is used to communicated with
that IET800.
If already checked, uncheck it, reboot, recheck it, and
then reboot. This setting updates the TcpAckFrequency
value for that adapter to 1 for proper communication on
COMP-OL-6200-48470 that adapter with the IET800.
Leaving a device DTM Window open for extended period No workaround. Recommend closing DTM Window when
of time may result in a S+ Engineering for Harmony it is not in use.
Engineering tool crash.
COMP-OL-6200-57347
After a network disturbance, a device DTM may not As designed. The behavior is dependent on the device
function correctly when using S+ Engineering for type and the DTM.
Harmony.
COMP-OL-6200-57348
Local or domain non-Administrator user might not be able As designed. Use by non-administrators is not
to start up Control Engineering, getting a dialog box of supported.
“Please wait while Windows configures....”
COMP-OL-6100-41523
Control Engineering only supports one Return To Normal Currently none. 800xA for Harmony 5.1 and later's Tag
Priority per tag. 800xA for Harmony 5.1 supports multiple Importer Exporter will no longer overwrite RTN priority
RTN priorities. columns with the BAD/PRI0 value if the tag already
exists in the Config Server database. BAD/PRI0 value is
COMP-OL-6000-7999 used to fill in other /PRI0 fields if the tag is created
during import into 800xA for Harmony.
Control Engineering does not detect NVRAM Failure No workaround. Check the controllers status reports
conditions present in controllers prior to initiating the prior to starting online config when possible.
Online Configuration sequence.
COMP-OL-6000-8057
44 8VZZ001554T2200 A

Simultaneous use of multiple PROFIBUS device DTM online No workaround. The HC800 controller communication
functions from multiple engineering workstations with PDP800, HAI805, HAO805, AI05, AO05, AI02, AO02,
communicating through the same PDP800 PROFIBUS RAI02, RAO02, AD01, and AD02 modules does not
master is not possible. support multiple simultaneous access.
Therefore, there are the following restrictions with
respect to using PROFIBUS/HART DTM dialogs and the
Harmony Fieldbus Analyzer.
1. In a given system, one cannot simultaneously use
the Fieldbus Analyzer and HART/PROFIBUS Device DTM
dialogs if they are communicating to a fieldbus device
through the same PDP800, HAI805/HAO805,
AI05/AO05, AI02/AO02, RAI02/RAO02, and AD01/ AD02
fieldbus master module.
2. In a given system, one cannot simultaneously use
multiple HART/PROFIBUS Device DTM dialogs if they are
being called up on different computers and communi-
cating through the same PDP800, HAI805/HAO805,
AI05/AO05, AI02/AO02, RAI02/RAO02, and AD01/ AD02
fieldbus master module.
3. On a single computer, however, one can simultane-
ously use multiple HART/PROFIBUS Device DTM dialogs
if they are communicating through the same PDP800,
HAI805/HAO805, AI05/AO05, AI02/AO02, RAI02/RAO02,
and AD01/ AD02 module. The Harmony Connection han-
dler sends read/write commands sequentially to the
PDP800, HAI805/HAO805, AI05/AO05, AI02/AO02,
RAI02/RAO02, and AD01/ AD02 modules.
COMP-OL-6000-16829
S+ Engineering Harmony Engineering does not handle Restart Control Engineering and/or restart the
network disruption when connected to projects or computer to correct the issue. Communication between
communications across the network. A Workbench engineering nodes require a stable/connected network.
messages may indicate “Connection failed to the server:
“server name”. Control Engineering may display an ADO
ERROR CONDITION 80004005 which indicates the
following: Description: Could not send Query (connection
dead).
COMP-OL-6000-40308
Printing CLDs to PDF fails - Control Engineering becomes
Printing CLDs to PDF will work, however sometimes the
non-responsive. error dialogs will be displayed but appear behind the
main Control Engineering window, which cause Control
Engineering to not respond to input. Solution is to use
Windows' Alt-Tab to cycle through open windows and
look for other dialogs waiting for acknowledgment or
COMP-OL-6000-7719 user input when Control Engineering appears to hang.
Print preview of CLDs within Automation Architect is No workaround. Print can still be previewed, but controls
missing the toolbar. (zoom, print, etc.) cannot be accessed. To close the
preview window, press "Esc" key or click on the
document "X" button (not the Automation Architect "X"
button which is just above it).
COMP-OL-6000-7977
Upgrading S+ Engineering projects does not copy the Reconfigure View and Monitor settings after upgrading
View and Monitor settings. a S+ Engineering project to the latest version.
COMP-OL-5100-012
8VZZ001554T2200 A 45

Failure to connect to the INIET800 with Control No workaround. Ignore this error message and resolve
Engineering may result in an error message which the initial connection failure error. The error message is
indicates RPC server is unavailable and that DCOM inaccurate.
settings may need to be checked. If Control Engineering's first attempt to connect to the
INIET800 fails, it uses DCOM to have the remote server
start the communications driver. The INIET800 is a
remote communication server, but does not support
remote starting through DCOM.
COMP-OL-5100-017
Importing a taglist exported with alarm inhibit tag Create a copy of the exported taglist file and clear the
reference generates an error: data in inhibit tag name field and value field. Import this
• Resolving alarm inhibit tag references modified tag list, to get all tags used as inhibit tags into
• Unknown non-COM Exception occurred the project. Then import the original full tag list to set
the alarm inhibit tag fields. Compacting the project prior
• Non-recoverable error encountered, DBImport
to importing may also help to resolve these errors.
terminating.
COMP-OL-5020-001
View and Monitor Publishing SOE point names are not No workaround.
displayed in the CLD Viewer.
COMP-OL-5010-014
When performing a verify and there are function codes No workaround. FC81 is misidentified as an extra block
with unassigned block numbers on the CLD, an 'extra when there are function codes without assigned block
block' verify message appears pointing to FC81, even if numbers on a CLD, but there is no error.
the CLD has a FC81, When compiled and downloaded, a
verify indicates no mismatches.
COMP-OL-4300-002
Harmony Soft Controller or Harmony Training Simulator When S+ Operations is connected to the Harmony Soft
do not assign quality correctly when REDAI is used to Controller or Harmony Training Simulator, the setting
force Bad Quality. DelayBeforeSetBadQuality should be modified to 0 for
HSC-OL-7100-209440 correct behavior of REDAI and REDDI quality.
Once enabled and connected, it may take 30 seconds to As designed. It may take up to 30 seconds to disable the
disable the Harmony Soft Controller. Harmony Soft Controller when Runtime Connect was not
performed. Connect the Harmony Soft Controller using
HSC-OL-2100-177326 the Runtime Connect feature for better “disable”
performance.
If Control Engineering is terminated unexpectedly and Terminate ScMgr.exe using Task Manager. Harmony Soft
Harmony Soft Controller is running, the user will not be Controller can then be Enabled.
able to start the Harmony Soft Controller.
HSC-OL-2100-177488
The Harmony Soft Controller does not support simulation The function code configuration (blocks and
of controller configuration logic that includes a Black Box specifications) can be viewed from the Harmony Soft
Configurable Function Code. If a Harmony Soft Controller Controller.
is executing on logic with a Black Box Configurable NOTE: At this time, the Harmony Soft Controller does
Function Code, the block outputs will identify CIU Error not support Black Box Configurable Function Codes.
104 and double clicking the Configurable Function Code
for its properties will display Fatal 105 (ICI): Function
blocks not configured error message.
HSC-OL-2100-178924
46 8VZZ001554T2200 A

The Locking mechanism is not available in Before starting the deployment process, make sure that
S+ Engineering while working in the same project with only one instance of S+ Engineering (that is, from which
multiple instances (for example, performing the deployment process has to be initiated) is present in
simultaneously the Operations Engineering settings, running status.
Topology Design, Deployment process, User Management
activities, and so on).
OPE-OL-3000-134501
The following error message is displayed while reversing Follow the given steps to reverse the indexes of multiple
the indexes of multiple items in Operations Engineering. items in Operations Engineering:
This issue continues even after the database initialization.
1. Switch the index using Operations Engineering.
“UID already defined.”
2. Export the existing items to an *.xlsx file format.
3. Delete the UID column from the *.xlsx file.
4. Delete all the existing items from the database in
Operations Engineering.
5. Import the updated *.xlsx file to S+ Operations
Engineering application.
6. Initialize the target database on S+ Operations
Server.
7. Align the database.
OPE-OL-3000-139974
IEC61850 driver goes to generic error state and After full deployment, copy the recently
communication fails to be established between IED and imported/created *_S1.CCF file from
HMI due to incomplete deployment action when S+ <Installed drive>\SymphonyPlus\Projects\<Project
Engineering and S+ Operation are installed in single node.
name>\IE\<project name>\<latest folder with time
stamp> to c:\ProgramData\ABB Symphony
Plus\Operations\SV3\config\iec61850\CCF
NOTE:
1. CCF file name should be changed to *.CCF (i.e.
excluding _S1)
OPE-OL-3200-208388 2. Make sure CCF files are copied to the destination
folder when ever new *.scd file import performed.
Local/ Global Trends created on one of the redundant S+ Compare node by node with Offline (SPE) in Difference
Operations Servers does not appear in the Difference Viewer and use the "Sync" functionality. Assign NDC and
Viewer due to unavailability of NDC details (only when two
deploy to reflect the changes.
S+ Operations Servers are selected). For more information on "Sync" functionality, refer to S+
Engineering 2.2 Operations engineering user
OPE-OL-3200-203744 manual(2VAA006938-320*).
Existing Sequence of Event (SOE) driver name is not Delete the old driver name manually from the system
updated when loop, module and controller address is setting.
changed during the engineering phase. Instead created
with new SOE driver name.
OPE-CN-3200-207161
In Power explorer, the alarms are not reported in Alarm Create a Alarm Category and assign it to respective tags.
List for IEC61850 and OPC tags. Then perform Deploy.
OPE-CN-3200-202076
Grey colors cannot be selected using the mouse pointer. Use the Option “More Colors” and select the required
OPE-CN-3200-205054 RGB combinations.
8VZZ001554T2200 A 47

Error is reported for Themes database while performing Create a new Custom action set and copy the “Full
Deploy_Full or Deploy_Full (local node- Step 3) actions deploy” or “Full deploy step 3" action sets and clear
from Operations Engineering using SPE 2.2 to SPO 3.1.1. “Theme” specific actions to resolve this issue.
OPE-CN-3200-205188
Field Engineering:
Incorrect status information of AI810/AI820 modules No workaround.
related to channel 9 are broadcasted by S800 I/O DTM
5.3.0/3 TC1.
ABB20141020-0712
COMP-OL-1100-58696
DI831 module is not available in the Control Engineering As designed.
Refer to the S+ Engineering 2.2 Harmony engineering
user manual Table A-1 (2VAA000812*) where a
workaround is documented.
COMP-OL-2100-172781 DI825, DI830, DI831 & DI885 are a SOE modules, to load
DTMs successfully, the user must manually edit the file
COMP-OL-7000-172782
C:\ProgramData\ABB\800xA\S800DTM\ServiceEntries.
COMP-OL-7000-172783
xml. Search for
COMP-OL-7000-172784
“EnableSOE”, modify Value=”0” to Value=”1”.
Tag’s HMI Attributes along with tags are not getting No workaround available.
copied from One project to another project.
COMP-OL-7000-181243
Field Engineering's Excel export uses macros for As designed.The user should enable macros for Excel’s
grouping, layout. re-import,. all features, otherwise only the raw data are visible.
COMP-OL-2100-177615
DTM communication error identified when observing Live Contact the ABB support for guidance in modifying
values in Field Engineering default communication timeout values.
COMP-OL-6500-116703
Batch Data Manager:
BDM requires multiple retries when reading the Batch UDF Multiple retries result in success of the requested
directory of the HC800 controller. Operations like Batch operation.
Download Utility, File Download from BDM context menu,
Batch Debugger sometimes might prompt error or retry
message dialog.
BDM-OL-6700-49058
BDM-OL-6700-140958
Debugger locks up when user attempts to inspect string None.
array.
48 8VZZ001554T2200 A

B90 compiler is very sensitive to hard line returns. A code Modify the code following the below example:
containing an AND statement does not work correctly Original code for SBLC 3.2.2:
with the new compiler, as it did with the older DOS based slot2 = SLOT_FIRST-1
Batch 90 compiler.
FOR slot1 = SLOT_FIRST+1 TO
SLOT_LAST DO
IF (slot2<SLOT_FIRST AND
SL_DATA(SL_ACCEPT, slot1-1)
<= \ ST_BUF_EMPTY) slot2 =
slot1-1
IF (slot2>=SLOT_FIRST AND
SL_DATA(SL_ACCEPT, slot1) > \
ST_BUF_EMPTY) BREAK
ENDFOR
New code (for BDM 5.0):
{find a valid empty and a
valid filled slot}
slot2 = SLOT_FIRST-1
SLOT_LAST DO
IF (slot2 < SLOT_FIRST) THEN
IF(SL_DATA(SL_ACCEPT, slot1-
1) <= ST_BUF_EMPTY) THEN
slot2 = slot1-1
ENDIF
ENDIF
IF (slot2>=SLOT_FIRST)THEN
IF (SL_DATA(SL_ACCEPT, slot1)
> ST_BUF_EMPTY) THEN
BREAK
ENDIF
ENDIF
ENDFOR
This condition has been around since the existence of
the DOS based B90 compiler. To correct this condition
use braces, as follows:
slot2 = SLOT_FIRST-1
SLOT_LAST DO
IF ( ( slot2 < SLOT_FIRST )
AND (SL_DATA(SL_ACCEPT,
slot1-1) <= \ ST_BUF_EMPTY)
)slot2 = slot1-1
IF ( ( slot2 >= SLOT_FIRST )
AND ( SL_DATA(SL_ACCEPT,
slot1) \ >ST_BUF_EMPTY) )
BREAK
ENDFOR
8VZZ001554T2200 A 49

When using the debugger installed with OperateIT None.
Process
Portal B the properties does not display the unit data
section information if the B90 class is unit relative. The
dialog always displays as if the class is non-unit relative.
The B90 compiler generates incorrect code for an The problem can be avoided by doing the assignment in
assignment statement with the following form: the left two steps, using an intermediate variable:
side is an element of a string array AND the right side is an For example:
element of a DataExpt array. For example: myStrArray(1) = tempStr = myDataExptArray(1).ostr
myDataExptArray(1).ostr. Once such a statement has been myStrArray(1) = tempStr
executed, the B90 program may misbehave in an
unpredictable way. This may cause the controller to red
light.
Noted difference in operation of the value of The workaround to monitor the value of This.csts would
CSEQName.csts or This.csts. CSEQName.csts displays be to add a statement to the B90 code that assigns a
essentially a Boolean value connected/not connected (it is global variable to the This.csts to display the correct
supposed to count up while trying to connect). This.csts value.
(on the server program) is supposed to show the number For example: in a global monitor insert the line:
of active supported connections. In the debugger it is not. Var1 = This.csts
It displays a value of 0.
where Var1 is a global variable. Since the global monitor
updates each cycle the variable will always have the value
of This.csts.
The display of CSEQ Unit Parameters of Master and None.
Control recipes will revert to the Internal reference name
(defined in the train) from the External Reference
class/unit when internal and external names reference the
same CSEQ address. The name selected has no effect on
behavior during runtime since the B90 program will
connect to the same class either using internal or external
reference names.
Renamed Class is not propagated to Unit Procedure/MRE None
references. Using the Rename feature of BDM the new
class name is not propagated into the properties of
recipes that referenced the old class name. This effectively
prevents the user from using the rename feature because
it makes all of the recipes created for the class unusable.
All the recipes must be re-entered by hand.
When changing the name of a unit procedure within a None. Refer to subsequent Technical Bulletins made
segment of a train in a master recipe, the related common available to the ABB Automated Technical Services Web
sequence internal reference name is not updated in the Site for the list of all known problems and their
recipe. workarounds in the current version of the product.
Please review these documents in the event that a
problem is uncovered.
BAL sometimes fails to update, for example when two Do not allow multiple users to open the same project.
users have the same BDM project opened, the BAL events
generated by the second user will be lost until both users
close the project, as a result the events are not included in
BAL.
BDM-OL-6800-95650
Compiler Settings: Justify caused incorrect characters to Do not select the Justify Compiler Setting.
be inserted into the Debug listing.
BDM-OL-6600-0537
50 8VZZ001554T2200 A

Workbench:
During the re-engineering of Sequence of events (SOE), SOE points to be manually deleted from the Function
SOE points are listed in the data browser or Signal Code (FC224) to avoid listing in the Signal Manager view.
Manager view when "HSOE disabled"(S10) spec changed
to value '0'.
WBSM-OL-2200-202909
Deleting signals & Function Codes are not proper, No workaround available. User has to manually delete
especially when one signal receives & sends command for signals and Function Codes in such case.
specific IEC 60870-5-104 protocol.
WBBE-OL-2100-169072
Plant area is not reflected in the Topology Design No workaround available. User has to define the Plant
Reference Pallet when it is imported via Bulk Engineering Area.
tool.
WBBE-OL-2100-170185
Diagram Wizard is not creating the Plant Area when user User has to define Plant Area once diagram is created
provides the Plant Area information in the Wizard using the Diagram Wizard.
property.
WBST-OL-2100-176959
CLT Instantiations fails to show up CFC with assign tag Manually update the CFC tags in the control logic
functions. document.
WBBE-OL-2100-180848 CLD.
CFC tags are not listed in the tag view of Data Editor. Manually update the CFC tags in the control logic
document.
WBBE-OL-2100-182362 CLD.
User is not able to do modification in a single click from No workaround available

the Tag editor.
WBBE-OL-2100-183121
During import process of Bulk Engineering Tool, if the User would require the PGAdmin privilege to release the
Workbench is forcefully closed and relaunched, Import lock.
locks occurs as pop up.
WBBE-OL-2100-183388
Copy paste does not work for exported IO list when Data changes shall be handled in the exported excel
reimported to Bulk Engineering Tool for any vertical sheet like copy/paste, then it can be imported via Bulk
engineering. Engineering Tool.
WBBE-OL-2100-183849
Error occurs while exporting CLD with the blank row in Perform CLT instantiation grid export without having
CLT instantiation User Interface. blank row to avoid errors.
WBBE-OL-2100-186752
8VZZ001554T2200 A 51

Errors are reported when user performs validation in Navigate to Operations Engineering and switch back to
Signal Manager without navigating to Operations Signal Manager if any signal import is done.
Engineering at least once after the installation.
WBSM-OL-2100-181813
Tag's N90sta type can't be listed in Signal Manager view N90sta tag type shall be created in Operations
since it does not have module and node address. Engineering as a new tag for further engineering.
WBSM-OL-2100-184460
NDC names are updated in the Network Distribution Class As designed. But user shall be able to modify the NDC, if
fields of Signal Manager view only when performing required for specific project.
validate action.
WBSM-OL-2100-185223
Deleted signals/tags from the Operations Engineering are Make sure that signal/tags are deleted from Signal
not reflected in Signal Manager and Control Engineering. Manager to sync the Control Engineering and
WBSM-OL-2100-186463 Operations Engineering.
The export of default rules is empty in Signal Manager. It is allowed to export only custom rules.
WBSM-OL-2100-183707
validation error occurs in the Connectivity Engineering Please do not keep blank cell with any format/alignment
template when grid has a blank value or format during the in excel before loading into Connectivity Engineering
excel sheet load in to the grid. template.
WBCE-OL-2100-185239
Navigation of a signal from Signal Manager to its Atom in No workaround available.
Operation Engineering and vice-versa is not available.
WBSM-OL-2000-130096
52 8VZZ001554T2200 A
3. Installation Initial installation
3. Installation
3.1 Initial installation
Refer to S+ System Installation user manual (2VAA008303 Rev E) for installation procedure of S+ Engineering
2.2 software.
3.2 Upgrade
S+ Engineering 2.2 supports Windows 10 IoT Enterprise LTSB 2016 and Windows Server 2016 operating
systems.
For upgrade, it is recommended to use the S+ Engineering Project Administration tool backup feature to
create a complete offline backup then store it in a safe location.
For the general procedure to upgrade from S+ Engineering 2.1/2.1.1 to the latest version of S+ Engineering for
Harmony, refer Uninstallation section.
Install a fresh copy of supported Windows operating system on the PC, then install S+ Engineering 2.2
following procedures in S+ System Installation user manual(2VAA008303 Rev E).
Use the S+ Engineering Project Administration tool restore feature to restore and upgrade the project
backup created by previous version.
Older versions Composer Harmony.ebp project file can also be upgraded into S+ Engineering 2.2.
Refer to S+ Engineering 2.2 Project administration user manual (8VZZ000130T2200) for more information on
project upgrade.
Operations Engineering upgrade does not support automatically for S+ Engineering 2.2, user needs to
configure the HMI parameters manually.
3.3 Backup and restore

Not applicable for this release.
8VZZ001554T2200 A 53
3. Installation Backup and restore
8VZZ001554T2200 A 54
A. Attribute Validation Range
Table A-1: Attributes Validation Range
Attributes Description Existing Range New Range
ALRMCMNT1 Return to normal 0-100 0-32767

comment
ALRMCMNT2 High Alarm Comment 0-100 0-32767
ALRMCMNT3 Low Alarm Comment 0-100 0-32767
ALRMCMNT4 2-High Alarm Comment 0-100 0-32767
ALRMCMNT5 2-Low Alarm Comment 0-100 0-32767
ALRMCMNT6 3-High Alarm Comment 0-100 0-32767
ALRMCMNT7 3-Low Alarm Comment 0-100 0-32767
ALRMCMNT8 High deviation alarm 0-100 0-32767
ALRMCMNT9 Low deviation alarm 0-100 0-32767
ALRMCMNT10 Increasing r.o.c. alarm 0-100 0-32767

comment
ALRMCMNT1 1 Decreasing r.o.c. alarm 0-100 0-32767

comment
ALRMCMNT1 2 Status change comment 0-100 0-32767
ALRMCMNT1 3 Hardware failure 0-100 0-32767

comment
PLANTAREA PLANTAREA 0-256 0-99
8VZZ001554T2200 A 55
56 8VZZ001554T2200 A
B. Uninstallation Uninstallation of S+ Engineering 2.1.1
B. Uninstallation
B.1 Uninstallation of S+ Engineering 2.1.1
Following table lists the Software details that must be uninstalled manually in the order mentioned for S+
Engineering 2.1.1.
NOTE: It is mandatory to take the project backup before uninstalling the S+ Engineering application.
Table B-1: List of Software for S+ Engineering 2.1.1 uninstallation
Serial Number Software name Version number
1 ABB S+ Engineering Server Environment 2.1.0.1
2 PostgreSQL 9.4
3 psqlODBC 9.3.400
4 ABB S+ Audit Trail 13.0.6
5 ABB S+ Engineering Core 2.1.0.9
6 ABB S+ Engineering Workbench 2.1.1000
7 ABB S+ Engineering IEC 61850 2.1.0000.41
8 ABB S+ Acronis Integration 1.1.1001
9 ABB S+ Engineering Harmony Field Device Components 7.0.1.238
10 ABB S+ Engineering Composer Harmony 7.0.1.238
11 ABB S+ Engineering Composer Harmony Documentation 2.1.1000.4
12 ABB S+ Engineering Composer Harmony Help 2.1.0000.36
13 ABB S+ Engineering Composer Harmony Power Tools 7.0.0.8
14 ABB S+ Engineering Harmony API Runtime 4.2.1.1
15 ABB S+ Engineering Harmony Batch Data Manager 7.0.0.5
16 ABB HAIHAO805 DTM 1.00.3044
17 ABB HARTSDIO DTM 1.00.3004
18 ABB PDP800 DTM 1.00.3044
19 ABB HGS 7.0 7.0.0.0
20 ABB S+ Engineering Composer Field 2.1.0000.81
21 ABB FDT Shared Components14.0.3-1 14.0.00300.2
22 ABB FDT Base Container 14.0.3-1 14.0.00300.1
23 ABB Basic HART DTM / HART DTM Builder 6.0.3-1 6.0.00300.1
24 ABB Basic PROFIBUS DTM/ PROFIBUS DTM Builder 6.0.0-0 6.0.0.16
25 ABB Central Licensing System 6.1.00000.18
26 Qt Runtime 4.8.7.2
27 ABB S800 I/O DTM 6.0.3-1 6.0.00300.5
28 ABB S+ Common Documentation 2.1.1000
29 ABB S+ Engineering Composer Operations 3.1.1000
30 ABB S+ Engineering Harmony Soft Controller 2.1.0.6
31 ABB S+ Engineering Services 2.1.0000.35
8VZZ001554T2200 A 57
Post uninstallation B. Uninstallation
Table B-1: List of Software for S+ Engineering 2.1.1 uninstallation (Continued)
Serial Number Software name Version number

(1)
32 ABB S+ Engineering System Variables Server 2.1.0.3
33 ABB S+ Operations SDK 3.1.1000
34 IIS Settings 2.1.0.1
35 VB60SP6-KB957924-v2-ENU 1.00.0000
(1)
- This component is applicable only for the S+ Engineering Server node installation.
For S+ Engineering Client node, “ABB S+ Engineering System Variables Client” needs to be uninstalled.
Note: If temporary correction software version is available, it’s recommended to uninstall them.
B.2 Post uninstallation

Following table lists the folder details that are created during installation and are not deleted during
uninstallation of S+ Engineering 2.1.1, It is recommended to delete the folders manually.
Remove the key (folder) completely from below location in registry.exe if present.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ABB Symphony Plus - Composer Operations
Table B-2: Symphony Plus related folder details
Serial Symphony Plus Related Folder

Path
number
1 Program files(x86) ABB Symphony Plus
2 Program files(x86) Installshield Installation Information

3 Program files(x86) ABB Industrial IT
4 Program files(x86) PostgreSQL
5 Program data ABB Symphony Plus
6 Program data SafeNet Sentinel
7 Program data ABB
8 ..\Installation path (C:\) Symphony Plus(1)
(1)
- If the computer has a 'D' drive, then this folder is created in D drive by default.
Restart the machine once the post uninstallation is complete.
58 8VZZ001554T2200 A
—
Visit us
www.abb.com/powergeneration
Document Number: 8VZZ001554T2200 A

www.abb.com/water
www.abb.com/symphonyplus
Back Cover

8VZZ001554T2200 A en Splus Engineering 2.2 Release Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

8VZZ001554T2200 A en Splus Engineering 2.2 Release Notes

Uploaded by

Copyright:

Available Formats

—

POWER GENERATION & WATER

ABB Ability™ Symphony® Plus

ABB Ability™ Symphony® Plus

Trademarks and copyright

Release: June 2019

About this book ..........................................................................................................................................................1

2. Modifications in 2.2 release ............................................................................................................................. 9

A. Attribute Validation Range ............................................................................................................................ 55

Table 1-1: Version Designation ............................................................................................................... 3

About this book

Information icon alerts the reader to pertinent facts and conditions.

1.1 Executive summary

1.2 Version designation

Table 1-1:Version Designation

Component Name Version Build Version

Table 1-1:Version Designation (Continued)

Component Name Version Build Version

1.3 Revision history

Rev No. Description Date

• Hyper-V in Windows Server 2016

Figure 1: Controller Firmware Matrix

1.4.1 Hardware and software requirements

Table 1-3:Hardware and Software Requirements

Table 1-3:Hardware and Software Requirements (Continued)

1.6 Reference documents

Table 1-4:Reference Documents

Document Number Document Title

Table 1-4:Reference Documents

Document Number Document Title

1.7 Product support

2. Modifications in 2.2 release

2.2 Fixed problems

Table 2-1: Fixed Configuration Issues

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Table 2-1: Fixed Configuration Issues (Continued)

Fixed Issue Correction or Fix

Fixed Issues Correction or Fix

Load data does not support loading of changed Fixed.

Table 2-2: Fixed Operation Issues (Continued)

Fixed Issues Correction or Fix

2.3 Discontinued and replaced functions

2.4 Known problems and workarounds

Table 2-3: Known Installation Issues

Issues Workaround/Clarification/Helpful hints

Table 2-4: Known Configuration Issues

Issues Workaround/Clarification/Helpful hints

3. A list of “Trend” related views is displayed with View-

Those views marked as “System” will be handled

Table 2-4: Known Configuration Issues (Continued)

Issues Workaround/Clarification/Helpful hints

Table 2-4: Known Configuration Issues (Continued)

Issues Workaround/Clarification/Helpful hints