Beruflich Dokumente
Kultur Dokumente
Compact HMI
Getting Started Guide
System Version 6.0.1
TRADEMARKS
All rights to copyrights, registered trademarks, and trademarks reside with their respective owners.
Section 3 - Installation
Supported Standard PLCs................................................................................................27
Overview..........................................................................................................................28
System Functions and Node Types ......................................................................28
Compact HMI Installation Workflow ..............................................................................29
Prepare ................................................................................................................29
Setup ....................................................................................................................30
Configure .............................................................................................................30
Prerequisites ....................................................................................................................30
For Workgroup Environment ...............................................................................30
For Domain Environment.....................................................................................35
3BSE040587-601 5
Table of Contents
Section 4 - Engineering
Working with Object Types............................................................................................. 73
Creating an Object Type ...................................................................................... 74
Adding Signals to an Object Type ....................................................................... 75
Adding Graphical Elements................................................................................. 77
Adding Faceplates................................................................................................ 79
Adding Alarm and Event Handling ..................................................................... 80
Adding History Logging ...................................................................................... 81
Adding Trend Display.......................................................................................... 82
Creating the Device Object Instances ............................................................................. 83
Creating Instances................................................................................................ 83
Connecting the Instances to Real Signals ............................................................ 86
Building the Functional Structure ................................................................................... 90
Adding Process Displays ..................................................................................... 95
Adding Trends...................................................................................................... 97
Adding Alarm and Event list for a Plant Area................................................... 100
6 3BSE040587-601
Table of Contents
Section 5 - Operation
Workplace Layout and Tools .........................................................................................115
Tabbed Menu......................................................................................................117
Application Bar ..................................................................................................117
Panel Area ..........................................................................................................118
Display Bar.........................................................................................................119
Tool Bar..............................................................................................................120
Status Bar ...........................................................................................................121
Navigation .....................................................................................................................122
General ...............................................................................................................122
Recommended Tools for Navigation..................................................................122
Faceplate Usage.............................................................................................................128
Trends ............................................................................................................................131
Trend Usage .......................................................................................................131
Alarm and Event Usage.................................................................................................133
Section 6 - Administration
Allocating the Functions to the System and the Nodes .................................................139
Deploying Individual or All Nodes in a System............................................................139
Expanding an Existing System ......................................................................................140
Excluding a Node ..........................................................................................................141
3BSE040587-601 7
Table of Contents
8 3BSE040587-601
Table of Contents
Index
3BSE040587-601 9
Table of Contents
Revision History
Introduction ................................................................................................................... 243
Revision History............................................................................................................ 243
10 3BSE040587-601
About This User Manual
General
Any security measures described in this User Manual, for example, for user
access, password security, network security, firewalls, virus protection, etc.,
represent possible steps that a user of Compact HMI System may want to
consider based on a risk assessment for a particular application and installation.
This risk assessment, as well as the proper implementation, configuration,
installation, operation, administration, and maintenance of all relevant security
related equipment, software, and procedures, are the responsibility of the user of
the Compact HMI System.
This User Manual describes the Compact HMI product, System Version 6.0.1. The
Compact HMI product helps the user to operate, configure and administrate a plant.
The Compact HMI is based on 800xA SV 6.0.1, which provides an HMI with easy
installation, configuration and operation suited for connection to PLCs.
For more information on the 800xA Base System, refer to the instructions available
in Reference Documentation or User Documentation in ABB Start Menu >
ABB Industrial IT 800xA > 800xA Documentation.
The following users are recommended to use this document:
• Process operators with experience of process control systems or PLC products.
• System engineers with experience of installation, configuration and set-up of
process control systems or PLC products.
• System administrators with experience of process control systems or PLC
products and Microsoft® Windows® operating systems.
3BSE040587-601 11
User Manual Conventions About This User Manual
Warning icon indicates the presence of a hazard that could result in personal
injury.
Caution icon indicates important information or warning related to the concept
discussed in the text. It might indicate the presence of a hazard that could result
in corruption of software or damage to equipment/property.
Information icon alerts the reader to pertinent facts and conditions.
Tip icon indicates advice on, for example, how to design your project or how to
use a certain function
Although Warning hazards are related to personal injury, and Caution hazards are
associated with equipment or property damage, it should be understood that
operation of damaged equipment could, under certain operational conditions, result
in degraded process performance leading to personal injury or death. Therefore,
fully comply with all Warning and Caution notices.
12 3BSE040587-601
About This User Manual Terminology
Terminology
A complete and comprehensive list of terms is included in System 800xA System
Guide Functional Description (3BSE038018*). The listing includes terms and
definitions that apply to the 800xA System where the usage is different from
commonly accepted industry standard definitions and definitions given in standard
dictionaries such as Webster’s Dictionary of Computer Terms. Terms that uniquely
apply to this User Manual are listed in the following table.
Term Description
ActiveX Microsoft standard for user interface components, based
on definition of software interfaces.
AS Aspect Server. The “central” intelligence in the system,
including the aspect directory and other services related
to object management, names, security, etc.
Aspect See Aspects on page 21
Aspect Objects See Aspect Objects on page 21
BDM Bulk Data Manager
CEXbus Communication module expansion bus used in the AC
800M Controller.
CNCP Control Network Clock Synchronization Protocol
COM (Microsoft) Component Object Model
CS Connectivity Servers provide access to controllers and
other data sources.
CTK Configuration Tool Kit
DCS Distributed Control System. A generic term for control
systems for Process Automation, normally with a
distributed database and real time data access.
DCU Distributed Control Unit
3BSE040587-601 13
Terminology About This User Manual
Term Description
DTM The Device Type Manager - DTM - is a software module
delivered by the manufacturer together with a device. As
an “FDT device driver” the DTM contains all device-
specific data, functions, and graphical user interfaces
and provides uniform access to these device-specific
internals via the standardized FDT interfaces.
ECCP Ethernet Communications Controller for the PCI bus
EPA Environmental Protection Agency
ERP Enterprise Resource Planning
ES Engineering System, which is used for engineering and
potential test of applications intended for Production
System.
FDT Field Device Tool. It is an open standardized
communication interface for integrating field devices and
their application into control systems or device
management tools, e.g. Engineering Tools and Asset
Management Tools.
FF FOUNDATION Fieldbus
GSM Global System for Mobile communication
HSE High Speed Ethernet (FOUNDATION Fieldbus)
HSI Human System Interface
HMI Human Machine Interface
MES Manufacturing Execution System
Node A computer communicating on a network, e.g. the
Internet, Plant, Control or I/O network. Each node
typically has a unique node address with a format
depending on the network to which it is connected.
ODBC Open Data Base Connectivity
OCS Open Control System. Similar meaning as DCS
14 3BSE040587-601
About This User Manual Released User Manuals and Release Notes
Term Description
OLE Object Linking and Embedding
OPC OLE for Process Control, a standard interface for data,
event and history access based on COM.
PCA Process Control Aspect
Plant Explorer An application that is used to create, delete and organize
Aspect Objects and Aspects in the
Compact HMI. The plant explorer organizes the Aspect
Objects in structures according to functionality, location,
etc. You can also use it to browse and search the
structures of the plant.
PLC Programmable Logic Controller. Controller for primarily
discrete logic control.
PNSM PC, Network and Software Monitoring
PS Production System which is used for controlling a real
process.
RNRP Redundant Network Routing Protocol
SIL Safety Integrity Level
SIS Safety Instrumented System
SMS Short Messaging Service
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SOE Sequence of Events
3BSE040587-601 15
Released User Manuals and Release Notes About This User Manual
16 3BSE040587-601
About This User Manual Released User Manuals and Release Notes
3BSE040587-601 17
Released User Manuals and Release Notes About This User Manual
18 3BSE040587-601
Section 1 Compact HMI Overview
The IndustrialIT Compact HMI supports 800xA Smart Client by sharing the
Compact HMI800 Graphics.
3BSE040587-601 19
Section 1 Compact HMI Overview
20 3BSE040587-601
Section 2 Terms and Common Principles
This section describes the terms and principles used in the Compact HMI system.
For more information, refer to System 800xA, Operations, Operator Workplace
Configuration (3BSE030322*) and System 800xA, Operations (3BSE036904*).
Aspect Objects
A plant consists of real entities, such as pipes, tanks, valves, and motors. In the
Aspect Object solution these entities or objects are modeled in the control system. A
modeled object is called an Aspect Object. This can be a simple lowest level object
or can contain other objects. Objects containing other objects are called composite
objects. The Aspect Object system can also handle computer related objects (for
example, user object, node object, and workplace object) similar to real entity
objects.
Aspects
There are a number of different types of information connected to each object.
These types of information are called Aspects in the Aspect Object solution. For
example a valve may have a mechanical drawing, a faceplate (for control purposes),
a graphical representation in a graphical display and so on. Aspect Objects have a
number of default aspects, for example, the Name aspect.
Aspect Objects are visualized with different tools, like Process Graphics, alarm lists,
and Plant Explorer. Right-click an aspect object to display a context menu. This
context menu contains a list of aspects from which a desired aspect can be selected.
Depending on the aspect and the environment, the information will be presented
using the appropriate tool.
3BSE040587-601 21
Aspects Section 2 Terms and Common Principles
Aspect View
A view is a visual representation of an aspect on the screen. Some aspects have
more than one view. For example, a Faceplate aspect can have three views.
Figure 2 shows how the concepts fit together. The physical valve is modeled and
represented in a graphical display. This valve that is now an Aspect Object, has a
number of Aspects, of which four are presented here. Each aspect has at least one
view.
22 3BSE040587-601
Section 2 Terms and Common Principles Structures
Structures
The Aspect ObjectTM concept allows organization of objects and aspects into
different structures, depending on which context is to be viewed.
Structures are the graphical representations of the relations that exist between
different aspect objects. An aspect object can be part of more than one structure
because there exist different types of relation between the objects.
The Plant Explorer includes different structures representing the same plant.
Structures can be built and improved at any time. Examples of the most common
structures are Object Type Structure, Control Structure and Functional Structure.
3BSE040587-601 23
The Operator Workplace and Plant Explorer Workplace Section 2 Terms and Common Principles
These areas contain important information and are never covered by displays. The
tools in these toolbars represented by icons are used to interact with the process and
the Compact HMI.
24 3BSE040587-601
Section 2 Terms and Common Principles The Operator Workplace and Plant Explorer Workplace
3BSE040587-601 25
The Operator Workplace and Plant Explorer Workplace Section 2 Terms and Common Principles
For more information on the Plant Explorer, refer to System 800xA, Operations,
Operator Workplace Configuration (3BSE030322*).
26 3BSE040587-601
Section 3 Installation
3BSE040587-601 27
Overview Section 3 Installation
Before proceeding with this chapter, make sure that all prerequisites required to
configure an Compact HMI System are completed, refer Appendix A,
Prerequisites.
Overview
Compact HMI installation includes the following:
• Centralized and automated software installation and configuration
• System deployment
The Compact HMI 6.0.1 is installed with minimal user interaction. It automates the
installation and configuration (adding of System Functions and allocating functions
to nodes) of an existing Compact HMI System. The configuration of all nodes in the
system can be done from one place, except for the preparation of nodes which is
done at each node.
28 3BSE040587-601
Section 3 Installation Compact HMI Installation Workflow
Prepare
The main purpose of this phase is to configure a node to be a Compact HMI node.
Use the System 800xA 6.0 System Guide Technical Data and Configuration
(3BSE041434*), and System 800xA 6.0 System Planning (3BSE041389*)
documents to plan the hardware and software requirements for a Compact Node. A
node must comply with the hardware and Operating System requirements to be
configured as an Compact HMI.
The following tasks are carried out in the prepare phase:
1. Selecting, and installing the Windows Operating System
2. Configuring Network Adapters
3. Configuring Domain Controller and DNS Server
4. Configuring Users and Groups
5. Setting up the Other Third Party Software
6. Preparing the node using the Node Preparation Tool
These procedures remain the same for any node selected to be configured as a
Compact HMI.
See the Industrial IT Certification home page for a complete and up to date list of
certified computers: http://www.abb.com/product/us/9AAC171278.aspx
Note that the certification itself is performed towards one or more specific
versions of Compact HMI.
3BSE040587-601 29
Setup Section 3 Installation
Setup
Select from the list of System Functions applicable to the system and the Node
Functions intended to run on the individual nodes to setup the system.
Deploying the System installs the Compact HMI software on all the nodes in a
centralized approach where the overall progress is indicated on Compact HMI
Server. The system configuration information including system functions, nodes
and associated node functions, node function properties and so on are stored in the
Aspect Directory. This enables and ensures smooth updates and upgrades of the
installed system.
Do not install Compact HMI software product manually. This will cause
inconsistencies in the information stored in the aspect directory which will lead to
unforeseen consequences in future maintenance of the system.
Configure
Most of the post installation configuration of the system and node functions is done
before the system is deployed. However, there are post installation configuration
steps that are not automated. Refer the System 800xA 6.0 Post Installation
(2PAA111693*) manual along with the product specific configuration manuals to
carry out the configurations.
Refer the Product Specific configuration manual for specific configurations related
to specific functions and features.This phase deals with configuring the 800xA Base
System and Functional Areas.
The system is now ready for application engineering.
Prerequisites
For Workgroup Environment
Following are the system setup that has to be done on Workgroup Environment
before starting Compact HMI 6.0.1 installation:
1. Right click on My Computer and click Manage. The Computer
Management window appears.
30 3BSE040587-601
Section 3 Installation For Workgroup Environment
2. Select Users under Computer Management (Local) > System Tools > Local
Users and Groups. All the users of the computer will be listed on the right side
as shown in Figure 6.
3. Right click on the window and click New User… to create a new user
SwServiceAccount.
3BSE040587-601 31
For Workgroup Environment Section 3 Installation
4. Fill in the required details such as User Name, Password as shown in Figure 7.
5. Click Create and Close the window. The SwServiceAccount will appear in the
user list as shown in Figure 8.
32 3BSE040587-601
Section 3 Installation For Workgroup Environment
6. Select Groups under Computer Management (Local) > System Tools >
Local Users and Groups. All the user groups of the computer will be shown
on the right side.
7. Right click and select New Group… to create a new group IndustrialITUser.
See Figure 9.
3BSE040587-601 33
For Workgroup Environment Section 3 Installation
d. In Select Groups window, write the name of the Group and click OK. See
Figure 10.
34 3BSE040587-601
Section 3 Installation For Domain Environment
10. Log out from the current user and log in as SwServiceAccount.
It is required to reset the password while logging in for the first time in a user
account.
3BSE040587-601 35
For Domain Environment Section 3 Installation
36 3BSE040587-601
Section 3 Installation Node Preparation Tool
3BSE040587-601 37
Installation of Compact HMI Server Section 3 Installation
38 3BSE040587-601
Section 3 Installation Installation of Compact HMI Server
3BSE040587-601 39
Installation of Compact HMI Server Section 3 Installation
6. In the Node Options window, select Compact HMI Server Node checkbox
and click OK. See Figure 15.
7. Click Start node preparation in the 800xA System Setup window. The
preparation process starts. A progress bar shows the progress of the
preparation.
40 3BSE040587-601
Section 3 Installation System Configuration Console
The system reboots when the Compact HMI 6.0.1 preparation is complete. Wait
until all the core products are prepared.
3BSE040587-601 41
Configure System Section 3 Installation
2. Select System configuration Console from the ABB Start Menu. See
Figure 17.
3. Click Yes on the confirmation message box shown in Figure 18. The System
800xA Configuration Console window appears as shown in Figure 19.
42 3BSE040587-601
Section 3 Installation Configure System
3BSE040587-601 43
Configure System Section 3 Installation
44 3BSE040587-601
Section 3 Installation Configure System
3BSE040587-601 45
Configure System Section 3 Installation
8. All the selected functions will be displayed in the System nodes tab with their
Property and Installation status. See Figure 22. Click Deploy system.. to
deploy all the functions.
46 3BSE040587-601
Section 3 Installation Configure System
9. The Deploy window shows the summary of the deploy. It will show the nodes
affected by the deploy and the status. Click Deploy to start the deploy. See
Figure 23.
3BSE040587-601 47
Configure System Section 3 Installation
10. The deploy progress bar will turn into green color once the deploy is
completed. See Figure 24. Click Close once all the nodes are deployed.
48 3BSE040587-601
Section 3 Installation Installation of Compact HMI Client
3BSE040587-601 49
Installation of Compact HMI Client Section 3 Installation
7. Click Start node preparation in the 800xA System Setup window. The
installation process starts. A progress bar shows the progress of the installation.
50 3BSE040587-601
Section 3 Installation Installation of Compact HMI Client
3BSE040587-601 51
Installation of Compact HMI Client Section 3 Installation
10. Go to System nodes tab and click Add node… in System 800xA
Configuration Console window. See Figure 28. The Add node window
appears.
11. In Add node window, enter the hostname. In Node Types, select Client and
click OK. See Figure 29.
52 3BSE040587-601
Section 3 Installation Configuring Multiple Network Cards
12. Click Deploy system.. in System 800xA Configuration Console window. The
Deploy window appears.
13. Click Deploy to start the deploy. See Figure 30.
14. The deploy progress bar will turn into green color once the deploy is
completed. Click Close once all the nodes are deployed.
3BSE040587-601 53
Configuring Multiple Network Cards Section 3 Installation
54 3BSE040587-601
Section 3 Installation License Installation
License Installation
After purchasing a Compact HMI license the license is downloaded from the ABB
Software Factory (SOFA) or delivered from a sales representative. The download
requires a registration prior to the download. The license is installed in the system
by following the following steps:
1. Log in as SysAdmin.
2. Open the License entry application available in ABB Start Menu > ABB
Industrial IT 800xA > System > Licensing.
3BSE040587-601 55
Compact HMI Upgrade Workflow Section 3 Installation
56 3BSE040587-601
Section 3 Installation Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to Compact HMI 6.0
3BSE040587-601 57
Upgrade from Compact HMI 5.1 FP4 Rev D RU1 to Compact HMI 6.0 Section 3 Installation
7. click on Next.
58 3BSE040587-601
Section 3 Installation Upgrade to 800xA from Compact HMI
8. Click on Select Path, then click add and browse for the backup folder.
3BSE040587-601 59
Start Up Section 3 Installation
Connectivity to AC 800M
If AC 800M controllers are used, the Compact HMI is ready to be connected to
the AC 800M controller after installation. The OPC server is installed with the
Compact HMI software install and the Compact HMI is configured accordingly.
The following figure describes how to connect to the AC 800M controller.
Power Cord
Start Up
After installing the hardware, the system is started as follows:
• Power up network switches and other communication equipment.
• Power up the server node.
• Power up the clients.
• Power up PLCs and other equipment.
60 3BSE040587-601
Section 3 Installation Connectivity to AC 800M
After the system start up, a welcome screen appears for the log in. The normal login
name for application engineering is AppEng (Application Engineer) use this to start
the engineering of the system.
Connectivity to AC 800M
The Compact HMI uses PLC Connect to connect to all PLCs and Controllers.
PLC Connect can be used to connect AC 800M/C controllers versions 3.0- using the
corresponding Control IT OPC Server 3.0-. PLC Connect can also be used to
directly connect AC 800M 2.0/2.1/2.2/3.0/3.1/3.2 and AC800C 2.2/3.2 versions,
using any of the following protocols with PLC Connect acting as master and AC
800M/C as slave:
• Serial connection and the Comli protocol (Limited Comli).
• SattBus on TCP/IP (Ethernet).
3BSE040587-601 61
Connectivity to AC 800M Section 3 Installation
3. Browse to the event collector service, right-click and create a new object. In the
dialog give the Service group a name e.g. “AC 800M OPC Collector” and click
Create as shown below in the Figure 36.
62 3BSE040587-601
Section 3 Installation Connectivity to AC 800M
4. Right-click on the created object and select create object, select Service
Provider, give it a name as shown below (e.g. Collector HMI_Server).
3BSE040587-601 63
Connectivity to AC 800M Section 3 Installation
5. Now the service needs to be allocated to the node where it should run. This is
done by selecting the service provider aspect and select the CHMI_Server node
in the Node drop-down list as shown below. Click Apply.
64 3BSE040587-601
Section 3 Installation Connectivity to AC 800M
6. In the created Service Group object (the parent in the structure) double-click
the Service Group Definition aspect. Configure it as shown below and click
Apply.
3BSE040587-601 65
Connectivity to AC 800M Section 3 Installation
7. Expand the window to see the bottom part and click Upload as shown below.
66 3BSE040587-601
Section 3 Installation Installation and Configuration of OPC Servers for PLCs
3BSE040587-601 67
Connection to Third Party Alarm & Event OPC Server Section 3 Installation
This aspect is normally added to the PLC signal object. Put the same name in this
aspect as the name defined as the object name in the controller generating the alarm.
The Name property in the OPC Source Name should be the same as in the OPC
AE server. Do not select the Is an Event and Is an Alarm check boxes in Alarm
Event Configuration for these signals.
Avoid identical names of PLC Process Object and PLC Signal Object.
68 3BSE040587-601
Section 3 Installation Connection to Third Party Alarm & Event OPC Server
3BSE040587-601 69
Connection to Third Party Alarm & Event OPC Server Section 3 Installation
5. Select This user. Provide the user name and password for the user to login
while using the AC 500 Control Builder (typically the user AppEng).
6. Click OK and close the application. The system is ready to be used for both
configuration and operation with the AC 500 controller.
70 3BSE040587-601
Section 3 Installation IP Addresses
IP Addresses
The tables below give a recommendation on IP addresses that will work for most
installations. If this suggestion is followed, the reader can disregard much of the
details about RNRP configuration. Table 2 suggests which NetIDs to use.
3BSE040587-601 71
IP Addresses Section 3 Installation
Addr on
Node Addr on Primary
Nodes Secondary
number Network
Network
Servers 11-20 172.16.4.11 - 172.17.4.11-
172.16.4.20 172.17.4.20
Workplace Clients 71- 150 172.16.4.71 - 172.17.4.71 -
172.16.4.150 172.17.4.150
Controllers 151- 172.16.4.151 - 172.17.4.151 -
220/255 172.16.4.220/255 172.17.4.220/255
Backup CPUs for 663-767 172.16.6.151 - 172.17.6.151 -
Redundant Controllers 172.16.6.255 172.17.6.255
Switches, Gateways, (501-511) 172.16.5.245- 172.17.5.245 -
Firewalls 172.16.5.255 172.17.5.255
(not RNRP addresses) (1013- 172.16.7.245- 172.17.7.245 -
1022) 172.16.7.254 172.17.7.254
72 3BSE040587-601
Section 4 Engineering
3BSE040587-601 73
Creating an Object Type Section 4 Engineering
Figure 43. New PLC Object Type in the Object Type Structure
3. Enter the name of the device type (for example SimpleOnOffMotor) and click
Create. This creates the object type.
74 3BSE040587-601
Section 4 Engineering Adding Signals to an Object Type
The newly created object type can be used to create instances which will be
connected to the individual signals existing in the PLCs.
3BSE040587-601 75
Adding Signals to an Object Type Section 4 Engineering
2. In the preview area you can create signal object by clicking om the I/O icons as
shown below.
3. Select the I/O type signal that represents the property to be accessed.
4. Enter the signal name (for example Motor_ON).
Repeat the above procedure for all the signals to be accessed for this device
type.
The OPC Server does not allow names of the signals as two words. The name of
the signal should be, for example, Motor_ON.
For more information on creating instances of this object type, refer to Creating
Instances on page 83.
76 3BSE040587-601
Section 4 Engineering Adding Graphical Elements
3BSE040587-601 77
Adding Graphical Elements Section 4 Engineering
For example, to write an expression to change the color of the ellipse when the value
of Motor_ON is True or False, execute the following steps:
1. In the Expression Editing area, enter if with a <space>.
2. In Process Data, click and browse for the Motor_ON signal object.
3. Select the Value property and click to insert the property into the
Expression Editing Area.
4. In Resources, click to define a color for the property.
5. Select symbol1Normal from Object Colors and click to insert the
property into the Expression Editing Area.
78 3BSE040587-601
Section 4 Engineering Adding Faceplates
6. Similarly select the color to be used if the value of Motor_ON signal object is
False.
The expression should be:
if S’Motor_ON:Value’ then
symbol1Normal
else
deviation
where, symbol1Normal and deviation are Logical Colors.
7. Click Apply and then click OK to save the changes and close the Expression
Editor.
8. Select File > Save to save the graphic element.
9. Select File > Exit to close the Process Graphics Editor.
Adding Faceplates
Faceplates are used to view, interact and change properties for devices and other
process objects. The operator of the plant opens the faceplates by clicking on
objects in graphic displays. For more information about the operator handling of
faceplates, refer to System 800xA, Operations (3BSE036904*).
Consider an example to create a faceplate aspect that activates the start signal for the
SimpleOnOffMotor object type representing a motor. The faceplate is created on the
object type.
Execute the following steps to create the faceplate:
3BSE040587-601 79
Adding Alarm and Event Handling Section 4 Engineering
iif($’./[Control Structure]:ObjectPCA:LOCK’=3,True,False)
10. The 1-Icon button is now configured to send the value True to the PLC signal
Motor_ON if the object is reserved (for example, LOCK=3).
11. Click the Tooltip text column. Select Label and enter Start motor. Click OK.
12. Click Apply to save the changes. This creates a faceplate with a button that sets
a property in PLC. A warning dialog appears, but it can be ignored in this
example.
13. Double-click the faceplate aspect to view the faceplate.
For more information on configuring the faceplates, refer to System 800xA,
Engineering, Process Graphics (3BSE049230*).
80 3BSE040587-601
Section 4 Engineering Adding History Logging
example for a section of the site or a single motor. For more information, refer to
System 800xA, Operations, Operator Workplace Configuration (3BSE030322*).
To create an event or alarm, the signal has to be configured. This is done using the
Alarm and Event Configuration aspect on an object type or on the individual signal
instance.
Object instances that generates events and alarms are recommended to be placed in
the Functional Structure to have alarm lists that covers only parts of the plant.
Building the Functional Structure on page 90 describes how to create an appropriate
Functional Structure.
The configuration of an event or alarm can be done either on the signal type or on
each instance. To define an event execute the following steps:
1. Select the device object for which alarm handling is required (either an
instance or an object type). For example, SimpleOnOffMotor in the Object
Type Structure.
2. Create a new signal called Motor_tripped of the type PLC Binary Type
representing the signal for which alarm handling is required.
3. In the Alarm and Event Configuration aspect of the signal below the Event tab,
select Is an event and Log status changes on.
4. Click Apply to save the changes.
The signal object is configured to generate an event when the value changes to on.
An instance of the object type must be created and connected to the PLC to
generate the event.
To see an event for a specific area, select the event list aspect for that area. To define
an alarm for the object select the Alarm tab instead and configure the alarm.
3BSE040587-601 81
Adding Trend Display Section 4 Engineering
82 3BSE040587-601
Section 4 Engineering Creating the Device Object Instances
Creating Instances
To create device instances that can be utilized for data presentation, do the
following.
1. In the Control Structure and select the OPC server for the PLC that contains the
properties you want to access.
2. Right-click the OPC server and create a New Object. Select any object type,
for example, SimpleOnOffMotor and enter a name (for example, M1).
Figure 48 shows the Control Structure:
3BSE040587-601 83
Creating Instances Section 4 Engineering
84 3BSE040587-601
Section 4 Engineering Creating Instances
3BSE040587-601 85
Connecting the Instances to Real Signals Section 4 Engineering
2. Click the yellow cube with the star and the dialog as shown in Figure 49.
86 3BSE040587-601
Section 4 Engineering Connecting the Instances to Real Signals
3. Click Apply in the OPC browser window to save the changes as shown in
Figure 52.
4. Repeat the procedure for configuring each signal.
Note that the Browse function is only available if the OPC server supports
browsing.
A signal can also be connected by adding the address string for the property.
3BSE040587-601 87
Connecting the Instances to Real Signals Section 4 Engineering
5. To test the connection, select the PLC Connect Server objects and the Deploy
aspect. Click Deploy.
88 3BSE040587-601
Section 4 Engineering Connecting the Instances to Real Signals
6. Click one of the signal object and select the binary PCA (Process Control
Aspect).
7. Select the Subscribe for live data check box to verify that data is retrieved
from the PLC.
Another method to retrieve live data is to select the Object Dialog aspect, see
Figure 55.
3BSE040587-601 89
Building the Functional Structure Section 4 Engineering
This retrieves live data from all the signals that are placed in this object. The alarm
indication icon appears. It also allows the user to view if a signal is forced or not.
Receiving live values for signals indicate that PLC Connect functions as required.
90 3BSE040587-601
Section 4 Engineering Building the Functional Structure
3. Right-click and select New Object from the context menu to add objects to
define the structure of the plant. Select one of the objects in the list, give it a
name and click Create.
Use the Bulk Data Manager (BDM) tool to move the device objects in the Control
Structure to the Functional Structure.
4. Switch to the Control Structure and select the root object.
5. Open the Bulk Data Manager from ABB Start Menu > ABB Industrial IT
800xA > Engineering.
6. In the Plant Explorer, right-click the BDM Place Objects aspect in the
Functional Structure and select Edit and Check Out.
3BSE040587-601 91
Building the Functional Structure Section 4 Engineering
Delete the data present in the spreadsheet in addition to the column headings.
7. Select one of the OPC servers objects (for example, Matricon OPC Server) in
the Control Structure and drag and drop the values in the Bulk Data Manager.
See Figure 57 below.
92 3BSE040587-601
Section 4 Engineering Building the Functional Structure
8. Move contents of column F to column E, select all texts in the column and cut
it and paste it in column E. Deselect the items in column F and click Save all
objects, a button located in the toolbar menu below Add-ins.
3BSE040587-601 93
Building the Functional Structure Section 4 Engineering
10. Exit the Excel file and do not save the changes.
In the Functional Structure, the objects can be dragged and dropped to the preferred
places.
94 3BSE040587-601
Section 4 Engineering Adding Process Displays
To add new objects, simply copy the new or changed objects from column F to
column E.
3BSE040587-601 95
Adding Process Displays Section 4 Engineering
8. In the Element Explorer, select the Control Structure and then browse to the
object containing the graphic element. The graphic elements belonging to the
object are displayed in the lower pane of the element explorer.
9. Double-click the graphic element to add it to the graphic display. The user can
also drag and drop the graphic element to the graphic display.
10. Select View > Toolboxes to view the toolbox of the Process Graphics Editor.
This allows the user to add graphic primitives to the graphic display.
To add a set of symbols to the graphic display, select Symbol Factory Bar
(this primitive adds a bar item) or Symbol Factory Symbol (this primitive adds
a graphic symbol such as motor, or valve) from Toolboxes > Special.
Right-click the control and select Edit from the context menu to edit the
symbol or bar.
96 3BSE040587-601
Section 4 Engineering Adding Trends
Adding Trends
Follow the steps below to create a Trend Display aspect:
1. Right-click the object to create the Trend Display and select New Aspect from
the context menu.
2. Select the Trend Display aspect category.
3. Enter a name for the aspect and click Create.
There are several different aspect categories of Trend Displays, the Operator
Trend, the Trend Display and the Object Trend.These categories are
dependent on the user roles required to modify them (Operator- and Object-
trend can be accessed by Show All in the new aspect dialog).
4. Select the newly created aspect in the aspect list. Figure 62 shows the Trend
Display.
3BSE040587-601 97
Adding Trends Section 4 Engineering
98 3BSE040587-601
Section 4 Engineering Adding Trends
3BSE040587-601 99
Adding Alarm and Event list for a Plant Area Section 4 Engineering
7. Select the Property and Log Name. Modify the data in other columns if
required.
Press SHIFT while selecting property in the Property selection column. This
displays only the logged properties.
If Log Name is not selected, SEAMLESS will be selected by default.
For more information regarding Trends, refer to System 800xA, Operations,
Operator Workplace Configuration (3BSE030322*).
100 3BSE040587-601
Section 4 Engineering Basic Navigation
1. In the Functional Structure, select an object for which an Alarm and Event list
is required. This includes alarms of all the objects belonging to the selected
object.
2. Right-click the object and select New Aspect.
3. Select the Alarm and Event list category.
4. Enter a name for the aspect and click Create.
For more information refer to System 800xA, Operations, Operator Workplace
Configuration (3BSE030322*).
Basic Navigation
Below the four most common ways to navigate are listed:
• Shortcuts make it easy to navigate to the most important and/or most frequently
used aspects of different aspect objects. You can find different shortcuts in the
Application Bar.
• To move back to the previous display click the Back to Previous Display
button. If the button is disabled, it is not possible to go backward.
• By clicking the Aspect Menu icon in the Tool Bar the Aspect Menu will be
presented. From the Aspect Menu you can navigate to different displays by
clicking on your Aspect Favorites.
• From the context menu you can e.g. select an aspect, action or a referenced
display for the object or aspect. The contents of the context menu may differ
depending on which object or aspect you have selected.
For more information refer to System 800xA, Operations, Operator Workplace
Configuration (3BSE030322*).
3BSE040587-601 101
Adding Shortcuts for Navigation Section 4 Engineering
This means that by adding a shortcut to the RC1 Robot Cell object, we can use the
shortcut from all views of the cell. For example, to add a shortcut to RC1 that points
to RC2, navigate to RC2 aspects from RC1 Graphical Display, RC1 Trends Display,
RC1 Mechanical Drawing.
The figure below shows how the navigation works:
Added Shortcut
Resulting
Navigation Functions
By adding a shortcut to the RC1 object, pointing to the RC2 Graphic Display, the
RC2 Graphic Display can be accessed both from the RC1 Graphics Display and the
RC1 Trend Display.
102 3BSE040587-601
Section 4 Engineering Adding Shortcuts for Navigation
3BSE040587-601 103
Adding Shortcuts for Navigation Section 4 Engineering
104 3BSE040587-601
Section 4 Engineering Adding Shortcuts for Navigation
3BSE040587-601 105
Adding Shortcuts for Navigation Section 4 Engineering
106 3BSE040587-601
Section 4 Engineering Messaging Configuration
7. A Display Shortcut will be displayed in the Display Bar, to the right of the
other tools. See Figure 69.
Messaging Configuration
The messaging function is used to forward important alarms and/or events to user on
the move. The messages can be forwarded using SMS, e-mail or paging services.
The example below shows how to configure the system to forward messages using
the SMS distribution channel.
To configure the Messenger function, to send alarm and events using SMS
messages, please go through the steps described below. For detailed configuration
information use the help button in the corresponding aspects. Login as a SysAdmin
to continue the process.
3BSE040587-601 107
SMS Messaging Configuration Section 4 Engineering
5. In the Services tab, you find the GSM predefined. Manually select the port
being used (normally port 3).
6. In the General tab, activate Outbox and Inbox Spoolers.
7. To configure, click ConfigureSMSDevice and open the Ports tab. Click Add.
8. Select the Port that you got above (normally port 3), click Next.
9. Enter the phone number for the phone that is used including country code.
10. Enter the Initialization string for the phone (look in help for initialization
strings).
For newer models of SonyEricsson phones use the Initialization command
string:
“AT+CBST=0,0,1;+CHSN=4,2,0,12” (omit the “characters)
11. Go to the General tab and select the Activate Outbox Spooler and the
Activate Inbox Spooler check box.
12. Configure the user that is supposed to receive the messages. This is done in the
Message Subscriber and Message Schedule aspects on the user objects in the
User Structure.
13. Define the alarms and events that should be sent as SMS messages by adding
and configure an Alarm and Event list aspect that defines which messages that
should be sent out.
108 3BSE040587-601
Section 4 Engineering e-Mail Messaging Configuration
14. To direct the messages in the list to be sent as SMS messages you need to
configure a Message Handler and an Alarm and Event Message Source aspect
on the same object as where the alarm list is located. (No shortcuts available.)
Enable the function in the Message source tab in the Message Handler aspect.
15. When the configuration is completed, start the messenger service by enabling
the service using the aspect:
[Service Structure]Services/Messenger Server/Basic:Service Group Definition
16. Test the messenger function. A message should be sent by SMS after
generating an alarm that is displayed in the alarm list aspect.
3BSE040587-601 109
Audit Trail Section 4 Engineering
the initial configuration phase, this should be changed later to correspond to the
required function.
4. To link the messages from the messages source to the user, add the Message
Handler aspect to the same object as where the message source aspect is
defined. Click New to select to which user and through which user device these
messages should be sent and click OK. Go to the Message source tab and
select the message source aspect to be used as source.
Select Enabled and click Apply to save the changes. The messages that should
be sent to which user and through which device are defined.
5. To define the information required to send e-mail messages from the system,
open the Aspect System Structure and browse to the object Messenger >
Email Device > Email Device and select the Email Device aspect. In this
aspect specify the e-mail address of the system in From field. This e-mail
address will be shown as the sender in the e-mail when it is received by the
user.
6. The next field is the SMTP Relay server, which can be left blank because the
Default SMTP Virtual Server is used on the server node to path the messages to
an SMTP server according to the suggestion received from the DNS.
Audit Trail
The Audit Trail function is by default enabled in Compact HMI. To view the Audit
Trail, open the Audit Trail List aspect on the plant object in the Functional
Structure.
To enable / disable the Audit Trail function follow the steps below:
1. Log in as SysAdmin.
2. Open the Plant Explorer and expand the Admin Structure.
3. Select Administrative Objects > Domains > CHMI_ServerSystem > Audit
Trail Config.
4. Double-click the Audit Trail Config aspect to open the configuration view.
5. Clear the selection in the Audit Trail active check box, and click Apply to
disable the Audit Trail function.
110 3BSE040587-601
Section 4 Engineering Security Configuration
6. Select the Audit Trail active check box. This enables the Audit Event
Filtering area.
7. Select the Log Generic Audit Events check box to log all the audit events that
are predefined in the system without details.
8. Select the Log Selected Audit Event Classes check box to select the audit
event message classes to be included.
9. Click Apply to save the changes.
Re-authentication is required to apply changes in the Audit Trail Configuration if
Advanced Access Control is activated.
Security Configuration
The default configuration contains a security setting valid for all objects in the
system. This default configuration is available in Admin Structure >
Administrative Objects > Inventory Object > Domain > [System Name] >
Security Definition.
The default configuration provides permissions for Operators, Application
Engineers and System Engineers.
Consider an example, where there are different groups of operators having different
access rights to application areas. This can be achieved by adding a Security
Definition aspect range on the particular object in the Functional Structure.
Individual objects can also have extended protection by adding a Security Definition
aspect with object range directly on the object.
For more information on configuring security, refer to System 800xA,
Administration and Security (3BSE037410*).
3BSE040587-601 111
Import of Controller Communication Application to Compact HMI Section 4 Engineering
112 3BSE040587-601
Section 4 Engineering Hardware and Software Supervision
11. In the Placements dialog right-click on the controller object and select new
insertion point.
12. Select the location of the PLC Controller type object in the Control Structure
and click OK.
13. Click OK for each imported item.
14. Before the objects will start communicating a deploy has to be done on the
PLC Connect Servers object (in the Control Structure).
3BSE040587-601 113
Hardware and Software Supervision Section 4 Engineering
114 3BSE040587-601
Section 5 Operation
This section describes how to operate the IndustrialIT Compact HMI. Also refer to
System 800xA, Operations (3BSE036904*) and System 800xA, PLC Connect,
Operation (3BSE035040*).
3BSE040587-601 115
Workplace Layout and Tools Section 5 Operation
Legend Description
1 Tabbed Menu
2 Application Bar
3 Panel Area
4 Display Bar
5 Tool Bar
6 Status Bar
116 3BSE040587-601
Section 5 Operation Tabbed Menu
Tabbed Menu
The Tabbed Menu is used to navigate to the different areas of the plant. Figure 71
shows tabbed menu mapped to the corresponding plant element in the Engineering
Workplace.
Application Bar
The Application Bar is used to show information that must be present all the time,
regardless of what displays are shown. One example is the alarm line. Tools in the
application bar influence the system or handles aspect objects. Some of the tools are
very useful for navigating.
For more information on customizing the Application Bar, refer to Application Bar
on page 125.
3BSE040587-601 117
Panel Area Section 5 Operation
Panel Area
The Panel is the main area for displays. It is used to show a view of an aspect (a
display), and can be used to present information like process displays, trend
displays, alarm lists, etc. Displays can appear as base displays covering the entire
Display area or as one or more overlap displays. The tools in the Display bar can be
used to control and identify the contents of the Display area.
118 3BSE040587-601
Section 5 Operation Display Bar
Display Bar
The Display Bar is used to navigate between displays. It changes when the base
display is changed.
For more information on customizing the Application Bar, refer to Display Bar on
page 125
3BSE040587-601 119
Tool Bar Section 5 Operation
Tool Bar
The Tool bar is used to access different aspects and manage workplace.
120 3BSE040587-601
Section 5 Operation Status Bar
Status Bar
The Status Bar is used to show who the current user is.
Users have different roles and privileges depending on security settings. The log-
over function can be accessed from this too.
3BSE040587-601 121
Navigation Section 5 Operation
Navigation
General
An operator working with the Operator Workplace wants to, in an easy way, address
and find elements such as graphic displays, faceplates, trend displays and alarm
lists. The Operator Workplace in IndustrialIT Compact HMI contains a tabbed menu
as a default set of tools to navigate among structures, aspects and objects.
A process industry site is often divided into different process sections, where the top
level display shows an overview of the entire section with details. Underlying
details may be accessed via the top level display or via other tools.
This section includes recommendations of how to use these tools to navigate
through displays. The recommended tools and methods are adequate for most
applications.
In the Compact HMI application the basics for presenting information from the
system is based on the Aspect Object concept.
Tabbed Workplace
Tabbed Workplace allows the user to navigate between graphic displays using
buttons, tabs, and drop-down lists. Tabbed Workplace is used for easy navigation
and responsiveness to alarms and events. A Tabbed Workplace is created by copying
predefined Tabbed Workplace, located in the Workplace Structure. This workplace
includes a breadcrumb list and status indicators for each tab.
The Breadcrumb list shows the object path, starting from the currently displayed
object back to the root object (see Figure 76). The breadcrumbs show where the
122 3BSE040587-601
Section 5 Operation Recommended Tools for Navigation
operator has navigated and allows for quick navigation to the immediate parent or to
the overview display.
The Status Indicators include an Alarm Indicator and a Status Indicator (see
Figure 77). The Alarm Indicator shows the alarm severity. These indicators guide
the user through the object hierarchy to locate the display that contains the alarm.
This saves engineering time for navigation configuration.
3BSE040587-601 123
Recommended Tools for Navigation Section 5 Operation
The Status Indicator shows the alarm status information. For example, the status can
be hidden or shelved.
Figure 77. Tabbed Workplace (With the Drop-down and Status Indicators)
Start Display
At log in as an Operator, the start display will be presented on the screen. It is
recommended to program one of the functional keys F1-F12 or the HOME key to
bring up this display.
124 3BSE040587-601
Section 5 Operation Recommended Tools for Navigation
Display Bar
For more information on Display Bar, refer to Display Bar on page 119.
Application Bar
For more information on Display Bar, refer to Application Bar on page 117.
Context Menu
By right-clicking an object in a display (or alarm list etc), a list of aspects associated
to the object is presented. If right-clicking the background, a list of underlying
displays is presented, provided that they are configured to show up.
By left-clicking an object, the default aspect of the object is invoked. Normally that
is the Faceplate for the object, but it might also be configured to be another Graphics
display, a trend display etc.
3BSE040587-601 125
Recommended Tools for Navigation Section 5 Operation
Hot Keys
A Hot Key is a specific predefined key combination (or a single key) that perform a
specific function. For example opening an aspect view, activating a verb or
accessing an object.
Function keys F1-F12 or any standard key can be configured to bring up displays,
typically different sections of the plant and / or to important displays.
The hot keys operations can be global, i.e. independent of selected or highlighted
object or affect the selected or the highlighted object.
There is a difference between a selected and a highlighted object. Current
selection is displayed in the Object Shortcuts tool. Selection is set for example
when clicking a Graphic Element in the object browser.
An object is highlighted when placing the mouse pointer over a graphic element.
The following tables show available predefined Hot Keys in the Operator
Workplace.
126 3BSE040587-601
Section 5 Operation Recommended Tools for Navigation
3BSE040587-601 127
Faceplate Usage Section 5 Operation
Faceplate Usage
A Faceplate is a process dialog for supervision and control.
The most common method to open the faceplate for on object is to left-click on the
object in a graphic display.
128 3BSE040587-601
Section 5 Operation Faceplate Usage
3BSE040587-601 129
Faceplate Usage Section 5 Operation
• Extended View. This view usually has two groups of tabs with additional
process information and functionality.
This view is used to display the maximum amount of information and is
intended for the process engineer or the advanced operator.
The active Faceplate view is indicated at the bottom of the Faceplates, the
corresponding view selection button is pressed. A non-existing view has the
corresponding view selection button disabled.
130 3BSE040587-601
Section 5 Operation Trends
Trends
The Trend Display can present data seamlessly from both run-time and historical
data. When a Trend Display for an object is selected all available data can be viewed
via the trend. This also means that it is possible to move the time range back and
forth without worrying about where data is coming from provided that the seamless
function is enabled in the Trend Display.
The Trend Display can hold a number of Trend Traces and it is possible to trend any
numerical property. It is possible to insert new traces for comparison with the
existing in all trends but the modified trend can only be saved if it is an Operator
Trend.
Functions for rulers, time zooming, magnifying glass etc. are available in the Trend
Display. The time-offset function can be used to trace a signal in real time and
compare it with values from yesterday. It is possible to present trend relationship
between two values as XY plots.
Trend Usage
The two most common ways to access a Trend Display for an object are from a
shortcut in the Application Bar or from the context menu.
3BSE040587-601 131
Trend Usage Section 5 Operation
The Trend Display is divided into three areas: the Trend Area, the Tool Bar and the
Trend Table. See Figure 81.
Trend
Areas
Trend
Tool Bar
Trend
Table
Different tools are provided to be able to modify the view of the traces in a variety
of ways. Examples are: Dragging the Split Bar, which is located between the Tool
Bar and the Trend Table, to desired size. Possibilities to enlarge the Trend Table to
visualize all rows in the Trend Area.
There is also a set of keyboard shortcuts that can be used to modify the Trend Area.
The Trend area is edge (border) sensitive. Clicking in the trend area and drag it over
the grid edge, the Trend Area will starts to scroll in that direction.
Each trace can have its number drawn in the Trend Area to help identify the
different traces. The number can be drawn above, below or centered on the trace.
When right-clicking in the Trend Area a pop-up configuration menu is displayed.
Please note that this also can be configured on the Trend Template.
132 3BSE040587-601
Section 5 Operation Alarm and Event Usage
For more detailed information regarding Trends refer to the System 800xA,
Operations (3BSE036904*).
Process Alarms
Process Alarms are alarms that are generated from the process, such as failure in a
valve or pump or an overpressure in a tank.
3BSE040587-601 133
Alarm and Event Usage Section 5 Operation
Alarm Line
Alarm Band Button
134 3BSE040587-601
Section 5 Operation Alarm and Event Usage
Right-click on an alarm line to bring up the context menu. From the context menu
you can perform actions on the alarm, or access any aspect of the object in the alarm
state.
You can acknowledge alarms for an object in the following ways:
• By clicking on the Ack State box for the alarm in the list.
• By right-clicking on an alarm land selecting Acknowledge (all alarms for that
object will be acknowledged) or Acknowledge Selected (only the selected
object will be acknowledged) from the context menu.
• By selecting one or several alarms in the alarm list and clicking the
Acknowledge button (green check mark).
• By clicking on the alarm status button in a faceplate.
3BSE040587-601 135
Alarm and Event Usage Section 5 Operation
Alarm Band
The Alarm Band provides a link to the Alarm List Display. The number within the
band represents the number of unacknowledged alarms. The color of the band
represent the highest priority alarm present. Click on the Alarm Band (button) to go
to the Alarm List.
Alarm Band
A red cross over the Alarm Band indicates that the alarm band does not have contact
with any server. If the cross is orange some server providing alarms is not
accessible.
If the button looks like in the figure above (Figure 84), the alarm band has lost
contact with some server (partially connected). In this case it is still possible to for
example make acknowledge.
System Alarms
System Alarms are alarms generated from the Compact HMI System, such as
network problems, file system errors or server errors. In many cases these alarms
need to be taken care of by your system administrator. There are several ways to
access the System Alarm List for an object. The following are some typical
examples:
• from the System Alarms button in the Tool Bar.
136 3BSE040587-601
Section 5 Operation Alarm and Event Usage
• from an Alarm Line in the Application Bar using the context menu.
• from an Alarm Band button in the Application Bar (Figure 85).
Process Events
There are several ways to access a Process Event List for an object. The following
are some typical examples that may be configured:
• from an Event Line in the Application Bar using the context menu.
3BSE040587-601 137
Alarm and Event Usage Section 5 Operation
System Events
There are several ways to access a System Event List for an object. The following
are some typical examples that may be configured:
• from an Event Line in the Application Bar using the context menu.
• from the System Event List button in the Tool Bar.
138 3BSE040587-601
Section 6 Administration
This section describes how to add users, make a Backup and Restore and other
system administration and maintenance tasks. Also refer to System 800xA,
Administration and Security (3BSE037410*).
Refer the System 800xA 6.0 System Guide Technical Data and Configuration
(3BSE041434*) to know and plan the number of nodes and the functions that can
be deployed.
3BSE040587-601 139
Expanding an Existing System Section 6 Administration
140 3BSE040587-601
Section 6 Administration Excluding a Node
Ensure that there are no reserved entities in a system before deploying the system
with new System functions. Use the Find Tool to identify the reserved entities
f
and release them. Refer System 800xA Operations 6.0 Operator Workplace
Configuration (3BSE030322*) manual for more information.
Excluding a Node
It might be needed to exclude a node or nodes from being deployed either because:
• It is disconnected from the system
• Is in an error state
• The user does not want to deploy on a particular node.
It is possible to exclude the erroneous node and continue the system deploy process.
A node can be excluded only if it is not already deployed.
It is highly recommended to include all the nodes for a system to be fully
deployed.
Replacing a Node
A node can be replaced by using the Replace node button. It can be used to redeploy
nodes that for example:
• have become corrupt
• have hardware issues.
Replacing a node will reset the node's installation status but it will retain its
configuration (the configured Node Functions and their property values). Once the
replace node process has been initiated, the node status will change to “Needs
Redeploy”.
When a node is replaced, the replacement node needs to have the same computer
name and network configuration.
To replace a node:
1. Restore the faulty node to a clean Windows installation. Prepare it according to
the instructions in Appendix A, Prerequisites.
3BSE040587-601 141
Adding and/or Removing a Node Section 6 Administration
2. Ensure that it has the same computer name and network configuration as
earlier.
3. Run the Node Preparation Tool on it.
4. Go to the node where the deploy was initiated and from the System nodes tab
of the Configure System task, and click on Replace node command on the
node. Once completed, the node's status will be 'Needs Redeploy'
5. Click the Deploy command to install the configuration on the node once again.
6. The node will have the same configuration installed as previously.
142 3BSE040587-601
Section 6 Administration Excluding a Node before Deploy
3BSE040587-601 143
Adding New Users Section 6 Administration
3. Click Users.
4. Click Users.
5. Click Add a new User.
144 3BSE040587-601
Section 6 Administration Adding New Users
3BSE040587-601 145
Backup and Restore Section 6 Administration
146 3BSE040587-601
Section 6 Administration Backup and Restore of Configuration Data
3. Select the Summary tab and click Start Backup to start the backup procedure.
4. Click OK to start the backup. This also displays the status of the backup
process.
Restore System
To restore the system go through the following steps.
1. In the Configuration Wizard, select Restore System and click Next.
2. If the backup does not show up in the window, click select Path, and add, and
then browse to the folder shown below.
3. Click OK to proceed.
4. Select the backup and click Next. (If the change of Computer Name has been
done before the system has been configured, use the restore dump available on
the DVD supplied in the Compact HMI delivery (another path needs to be
added)).
5. Select Generate New System ID and enter the system name. For example,
HMI Server55 System and click Next.
3BSE040587-601 147
Store Controller Application in the System Section 6 Administration
148 3BSE040587-601
Section 6 Administration Other Maintenance
5. Select the File Viewer aspect and enter a name. For example, Control
Application 1.3-2006-05-23.
6. Right-click the selected aspect and select Config View.
7. Click Attach in the Public Document part of the window, and browse to the
newly created zip-file. Select the file and click Open.
8. The file is now stored in the system and will be part of any future system
backup.
Other Maintenance
To Stop and Start the System
The Compact HMI server nodes contains a set of software services that are running
continuously in the background in the computer. These services are often referred to
as the system or Compact HMI system. During some maintenance activities it is
necessary to stop and start these services. This is described below. When switching
on the power to a Compact HMI server the system is automatically started.
Stop System
To stop the system without switching off the power follow these steps:
1. Log in as SysAdmin.
3BSE040587-601 149
To Stop and Start the System Section 6 Administration
150 3BSE040587-601
Section 6 Administration To Stop and Start the System
Start System
To start the system without switching off and on the power follow these steps:
1. Log in as SysAdmin.
2. Open the Configuration Wizard (ABB Start Menu> ABB Industrial IT
800xA > System > Configuration Wizard).
3. In the dialog above select System Administration.
4. Then click Next and Next again.
5. In the window below select Systems and press Next.
6. Select Start and press Next and then Finish.
3BSE040587-601 151
Autonomous Redundancy Setup Section 6 Administration
7. Wait until the system has started. (The dialog in Step 2 is displayed).
152 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Server Node
5. Delete the system, by opening the Configuration Wizard (ABB Start Menu >
ABB Industrial IT 800xA > System > Configuration Wizard).
6. Select System Administration and click Next, and then Next again.
7. Select System Start, Stop or Delete and press Next.
8. Select Delete System on a Node and click Next.
9. Be aware of that all configuration data will be lost if you proceed and has not
done step 1 and 2.
10. Click Next and Finish.
11. Now wait until the system has been deleted (the dialog in step 6 shows up, with
some fewer options), then Exit the Configuration Wizard.
12. Restart the computer and log in as SysAdmin.
3BSE040587-601 153
Change the Windows Computer Name in the Server Node Section 6 Administration
13. Now change the Windows Computer Name and if needed the IP address of the
computer. Remember to update the Host file (in both server and clients).
(“C:\WINDOWS\system32\drivers\etc\hosts”).
14. The server address for the license system has to be adjusted. To do this open
ABB Start Menu> ABB Industrial IT 800xA > System > Licensing >
License Status Viewer.
15. Select Tools > Change CLS Machine, to get the dialog below.
16. Enter the new name e.g. “HMI-Server55” and press Apply and exit the License
Status Viewer.
17. Restart the computer and log in as SysAdmin.
18. If you are using the AC 800M OPC server, open the OPC server configuration
dialog and disconnect and connect each of the controllers once. After this save
the configuration.
19. If you are setting up an autonomous redundant backup system (otherwise skip
this step) please copy the backup files from the main system server (typically
from folder located on "Backup Disc:\Backup" in the server workplace) to the
backup system server (same location).
20. Open the Configuration Wizard and select Restore System and click Next.
154 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Server Node
21. If the backup shows up in the window go to step 22. If the backup does not
show up in the window, click select Path and add, and then browse to the folder
shown below.
3BSE040587-601 155
Change the Windows Computer Name in the Server Node Section 6 Administration
156 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Server Node
b. Click on each of the objects of the type PLC Controller Type and select
the PLC controller configuration aspect as shown in the figure below.
3BSE040587-601 157
Change the Windows Computer Name in the Server Node Section 6 Administration
c. Click the Edit Driver button and the dialog in the figure below is
displayed.
d. Click the Update button and select the OPC server to be used as shown
above.
e. Click OK and then Apply to save the new configuration.
28. Select the object PLC Connect Servers and the Deploy aspect.
29. Click Deploy.
30. When deploy has ended, the Node name change for the server is completed.
31. If clients are connected to the server each client needs to be updated as
described in the following four steps:
a. Log in as SysAdmin in the Client.
b. Open the Hosts file using Notepad and update the file with the new name
of the server.
c. Restart the client.
d. Connect the client to the system server as described in Connect and
Disconnect Client Nodes on page 159.
158 3BSE040587-601
Section 6 Administration Change the Windows Computer Name in the Client Node
3BSE040587-601 159
Connect and Disconnect Client Nodes Section 6 Administration
7. In the dialog shown below select the client to be added e.g. HMI-Client01.
Disconnect a Client
To Disconnect a client from a system go through step 1-5 above, and then continue
with these steps:
1. Select Client node and click Remove node.
2. In the dialog below select the client to be removed.
160 3BSE040587-601
Section 6 Administration Defragmentation
3. If the client exists on the network, keep the switch Update Node selected. If the
client is not available on the network remove the switch.
4. Click Next and then Finish.
5. The client has now been removed.
Defragmentation
Defragment the hard drive regularly. This helps keeping the good performance of
your computer.
Virus
Do not connect the computers directly to the internet. The computers must be
protected behind a hardware firewall. Refer to the section about computer security
in the System 800xA, Administration and Security (3BSE037410*) instruction.
3BSE040587-601 161
Windows Update Section 6 Administration
Windows Update
Update Windows regularly. This helps keeping the good performance of your
computer and the stability of your software.
This must be done in a secure manner, as recommended below.
The system administrator or a central engineering department can make the updates
available on a dedicated distribution server on the office or corporate network by
installing them from CD/DVD, or by downloading them from a trusted server e.g.
on the Internet.
162 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Configuration Settings
McAfee VirusScan® Enterprise can be configured for on-access and on-demand
virus scanning.
• On-access scanning is automatically activated at system startup and will check
files as they are accessed. To prevent this from causing performance
degradation, folders containing files that are frequently accessed need to be
excluded from on-access scanning.
• On-demand scanning can be configured to run cyclically at predetermined
times or intervals, or be manually initiated. All files that are excluded from on-
access scanning should be scanned on-demand at regular intervals. However,
since this scanning will impact system performance and reaction times, it
should be done when normal system activity is low.
This section describes the specific VirusScan configuration setting that need to be
made. All other settings should be left at their defaults.
Some of the VirusScan configuration settings require that the computer is
restarted before the changes take effect.
3BSE040587-601 163
Using Virus Protection with Compact HMI Section 6 Administration
On-access Scanning
General Settings. Below the General tab, deselect the Processes on enable check
box. Select Disabled in the Sensitivity level drop-down menu1.
1. If enabled, when this feature detects a suspicious file it will send a DNS request containing a fingerprint of the
suspicious file to McAfee Avert Labs, which then communicates the appropriate action back to VirusScan
Enterprise 8.7i. This behavior may cause problems in a Compact HMI system.
164 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Below the Messages tab, deselect the Delete files check box in the Actions
available to user area.
3BSE040587-601 165
Using Virus Protection with Compact HMI Section 6 Administration
166 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
3BSE040587-601 167
Using Virus Protection with Compact HMI Section 6 Administration
In the Additional File Types dialog box, add the AFW file type in the User-
specified additional file types area. Click OK.
Below the Exclusions tab click the button Exclusions. A list of disks, files and
folders that are excluded from on-access scanning is presented.
To add items to the list, click Add … and fill in relevant folders, files, and file types
as shown in Figure 108.
The items that need to be excluded depend on which products are installed. A list
is provided in Folders Excluded from On-access Scanning on page 180.
The file types LDF, MDF, and NDF are related to SQL Server and should be
excluded from scanning. Scanning these files may under certain circumstances
cause a deadlock, see Microsoft KB 309422.
168 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
For each item that is added, select Also exclude subfolders, On read, and On
write, as shown in Figure 109.
3BSE040587-601 169
Using Virus Protection with Compact HMI Section 6 Administration
Below the Actions tab make the settings shown in Figure 110.
Settings for Low Risk Processes. Add the Compact HMI system function
Afwworkplaceapplication.exe to the list of low risk processes1.
1. Certain low risk processes may already be listed as defaults by McAfee. These can be left as is.
170 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Apply the same settings below the Scan Items tab as were made for default
processes (see Figure 106).
Apply the same settings below the Exclusions tab as were made for the default
processes. In addition, exclude the following folder:
\Program Files\ABB Industrial IT\Operate IT\Process Portal A\bin
Apply the same settings below the Actions tab that were made for default processes.
Settings for High Risk Processes. Apply the same settings below the Scan Items
tab as were made for default processes (see Figure 106).
Apply the same settings below the Exclusions tab as were made for the default
processes.
Apply the same settings below the Actions tab that were made for default processes.
3BSE040587-601 171
Using Virus Protection with Compact HMI Section 6 Administration
On-demand Scanning
The folders that are excluded from on-access scanning should be scanned regularly,
either at scheduled intervals, or manually initiated. Note that scanning these folders
will impact system performance and reaction times; it should therefore be done
when normal system activity is low.
In applications where it is not possible to select a regular time when on-demand
scanning can be done without disturbing operation of the system, there should be
procedures for manually initiating the scanning as often as practical.
The default setting for on-demand scanning is to include all local drives. However,
the time to complete the scanning with this setting can be excessive. In order to
minimize this time, scanning could alternatively be limited to those items that are
excluded from on-access scanning.
172 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
To remove locations for on-demand scanning, click Remove, to add items, click
Add.
At least all items excluded from on-access scanning should be covered by on-
demand scanning (except file types MDF, LDF, and NDF, see below).
Make sure that the scan options Include subfolders and Scan boot sectors are
selected.
3BSE040587-601 173
Using Virus Protection with Compact HMI Section 6 Administration
To specify a schedule, click on Schedule. Select the Scan Item tab and make the
selections shown in Figure 113.
Select the Exclusions tab and click Exclusions … and add the file types LDF, MDF,
and NDF. These file types are related to SQL Server and should be excluded also
from on-demand scanning. Scanning these files may under certain circumstances
cause a deadlock, see Microsoft KB 309422.
174 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Select the Performance to limit the performance impact from on-demand scanning,
as shown in Figure 115.
The optimal value for this setting is installation specific and depends on many
factors, including the system configuration and load, the application, and the
operating conditions during the on-demand scanning. The value shown in Figure
13 is intended as guidance only. Try out a value that allows the scanning to finish
within an acceptable amount of time while keeping the impact on system
performance and reaction times at a level that is tolerable.
Select Disabled in the Sensitivity level drop-down menu1.
1. If enabled, when this feature detects a suspicious file it will send a DNS request containing a fingerprint of the
suspicious file to McAfee Avert Labs, which then communicates the appropriate action back to VirusScan
Enterprise 8.7i. This behavior may cause problems in a Compact HMI system.
3BSE040587-601 175
Using Virus Protection with Compact HMI Section 6 Administration
176 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Select the Actions tab and make the settings shown in Figure 116.
3BSE040587-601 177
Using Virus Protection with Compact HMI Section 6 Administration
1. If the infected node is critical for the operation of the system, stop the system in
a controlled way. Nodes that are critical should be clearly identified in the
security policy (examples are non-redundant Aspect or Connectivity Servers,
however, this is highly application dependent).
2. Disconnect the infected node from all networks.
3. Restore the infected node from a disk image if available, or re-install from
scratch (see the section about Node Replacement in System 800xA,
Administration and Security (3BSE037410*).
4. Verify that the node is no longer infected by running a complete virus scan.
5. Reconnect the node to the network and restart it.
If a virus is found on one node, it is likely that also other nodes are infected. An
on-demand scanning of all nodes is therefore recommended.
Access Protection
Messaging function in System 800xA. In systems where this function is used, the
process AdvMsgEngine.exe therefore needs to be added to the Excluded Processes
list on the server where the Messenger Service runs (normally the Aspect Server).
Open the VirusScan console, right-click on Access Protection and select
Properties.
178 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Select the Access Protection tab, then select Prevent mass mailing worms from
sending mail (Port 25) and click Edit…:
In the Processes to exclude area add AdvMsgEngine.exe to the list (separated from
other items by a comma).
3BSE040587-601 179
Using Virus Protection with Compact HMI Section 6 Administration
Click OK twice, and then close the VirusScan Console. SMS & e-mail Messaging
can now send e-mails.
AutoUpdate
AutoUpdate is a feature that can be used to ensure that the latest McAfee virus
definitions are downloaded and installed on every machine. However, this feature
requires a direct connection between the automation system network and the
Internet. Enabling AutoUpdate on hosts connected to the automation system
network is therefore not a recommended practice.
For a more secure and reliable deployment of virus definitions, a central
management and update deployment host can be set up on a corporate intranet. This
allows a system administrator to have control over when updates are made, and an
opportunity to test the updates before they are deployed. The white paper "IS
Security Considerations for Automation Systems" (3BSE032547) provides general
guidelines for how this could be arranged.
180 3BSE040587-601
Section 6 Administration Using Virus Protection with Compact HMI
Product Path
800xA Base System <drive>:\OperateITData*\
<drive>:\OperateITTemp*\
<drive>:\Program Files\ABB Industrial IT\Operate IT\Process Portal
A\AppLog\
<drive>:\Program Files\ABB Industrial IT\Operate IT\Process Portal A\bin\
(for low risk processes only)
File types MDF, LDF, NDF (exclude also from on-demand scanning)
Engineering Studio <drive>:\Program Files\Common Files\ABB Industrial IT\
MSSQL$EBINSTANCE\Data\
Control IT <drive>:\ABB Industrial IT Data\
3BSE040587-601 181
Using Virus Protection with Compact HMI Section 6 Administration
182 3BSE040587-601
Section 7 Using the PLC Device Library
PLC Device Library has a number of predefined object types for motors, valves,
PID, analog types, binary types, etc. with predefined process graphics such as
faceplates, alarm lists and signal lists to facilitate connections to different PLC's.
Information on how to create graphics in general is described in the System 800xA,
Engineering, Process Graphics (3BSE049230*) instruction, which can be found in
ABB Start Menu> ABB Industrial IT 800xA > Engineering.
3BSE040587-601 183
Section 7 Using the PLC Device Library
It is also possible to create your own defined objects, see Working with Object
Types on page 73.
The following chapter describes how to create graphic displays by using the
predefined graphic elements and object types in the PLC Device Library.
184 3BSE040587-601
Section 7 Using the PLC Device Library Creating PLC Device Library Instances
The example below will create a graphic display containing a tank, pipes, valves and
a motor representing a chemical process.
To instantiate the different types a PLC Generic Control Connection object is
needed in the Control Structure. This is described in the Installation and
Configuration of OPC Servers for PLCs on page 67 and in Creating the Device
Object Instances on page 83.
3BSE040587-601 185
Creating PLC Device Library Instances Section 7 Using the PLC Device Library
3. In the Create New Object dialog select the VALVtype, the controller and enter
a name for the valve instance. In this case create only one instance even though
it is possible to create several instances at one time.
186 3BSE040587-601
Section 7 Using the PLC Device Library Creating PLC Device Library Instances
3BSE040587-601 187
Creating PLC Device Library Instances Section 7 Using the PLC Device Library
188 3BSE040587-601
Section 7 Using the PLC Device Library Creating PLC Device Library Instances
5. Connect the signals for the motor and the valve. The main parameters for the
PLC Device objects are described in the Data Sheet aspect for the represented
object as shown in Figure 124.
6. Select each of the signal objects in the motor and the valve that has a
representation in the OPC server and select the Signal Configuration aspect.
3BSE040587-601 189
Creating PLC Device Library Instances Section 7 Using the PLC Device Library
7. To connect the signal, select the Connected radio button and then click Browse
to open the OPC Browser dialog and connect the signals according to the signal
data sheet for the type.
190 3BSE040587-601
Section 7 Using the PLC Device Library Creating PLC Device Library Instances
3BSE040587-601 191
Creating the Display Section 7 Using the PLC Device Library
The motor and the valve are now configured and deployed and are now ready to be
used in a graphic display.
192 3BSE040587-601
Section 7 Using the PLC Device Library Creating the Display
4. Create a tank element by selecting the tank body, tank neck and tank bottom
element from the Shapes toolbox. Also add pipes using the flexible pipes
element.
5. In the toolbox, select the Element Explorer and browse to the Control Structure
and the motor and the valve created in the previous example.
6. Select the Display Element Reduced Icon for the motor and the valve to insert
them into the display.
3BSE040587-601 193
Creating the Display Section 7 Using the PLC Device Library
7. Click Save, and the display is ready for operation, as shown in Figure 130.
194 3BSE040587-601
Section 7 Using the PLC Device Library Creating the Display
3BSE040587-601 195
Creating the Display Section 7 Using the PLC Device Library
196 3BSE040587-601
Appendix A Prerequisites Windows Operating System
Appendix A Prerequisites
The user performing the procedures in this section must be proficient in the use of
Windows Operating Systems. This section may not include detailed procedures
on how to perform the described settings.
There may be differences in accessing the Microsoft Operating System settings
described in this section depending on the selected operating system. It is the
responsibility of the user to consult Microsoft documentation and online help to
accurately make the settings.
Use the System 800xA 6.0 System Planning (3BSE041389*) document to help
plan the requirements, both hardware and software, for the 800xA System.
This section lists the prerequisites required to configure a node for an 800xA
System.
It is recommended to make a full backup of all disks. With such a backup all work
will be saved in the event of a disk crash or other serious malfunction. Make sure
to place proper identification on the backup media or backup files.
Install optional hardware drivers if not supplied by the Windows Operating
System (video card, network adapter, sound card, etc.).
3BSE040587-601 197
Considerations for Disks and File System Appendix A Prerequisites
The supported operating systems, service packs, and hot fixes are listed in System
800xA 6.0, 5.1, 5.0, 4.x, 3.1 Third Party Software (3BUA000500). For security
updates refer System 800xA - Third Party Security Updates Validation Status
(3BSE041902). These documents can be found in ABB SolutionsBank.
The US English version of the operating system is required even if a translation
NLS package for System 800xA is used.
The following conditions affect the decision on which operating system to use:
• Server roles can be allocated to nodes running either a workstation or server
operating system of Windows. Using workstation operating system helps in
keeping the cost down for smaller installations. Refer to the System 800xA 6.0
System Guide Technical Data and Configuration (3BSE041434*) for rules that
apply in selecting the type of Operating System.
• There are limitations on number of nodes used in the system when using the
Workstation Operating System for Server nodes. These limitations depend on
Microsoft licensing rules for the Workstation Operating System. Refer to
System 800xA System Guide Technical Data and Configuration
(3BSE041434*) for the details on the limitations.
• The Windows Operating System may be purchased from any Microsoft
reseller.
• The nodes with pre-installed operating system shall be checked and configured
as per the system 800xA specifications.
198 3BSE040587-601
Appendix A Prerequisites Considerations for Disks and File System
Installation Directory
It is generally recommended to use the Windows default location, the program files
directory on the boot disk, for installation.
A faster disk subsystem will improve performance.
Defragmenting Disks
The file system must be in a consistent state at all times. Size disks so they will be
25 percent empty for defragmentation purposes. Defragment disks on a regular basis
using the defragmentation software provided with the operating system. Check the
system for fragmented files and defragment them as required:
• On all nodes where trend and history logs reside.
• History Server disks and disks on the Connectivity Servers where trend or
history logs reside as History configuration impacts not only the History Server
disks.
• Extensive use of the Bulk Configuration tool may cause associated disks to
become fragmented.
• Configuration procedures that involve creating, deleting, and then recreating of
a large quantity of objects may cause associated disks to become fragmented.
• Deleting and then creating the Aspect System may cause associated disks to
become fragmented.
3BSE040587-601 199
Windows Installation Guidelines Appendix A Prerequisites
Step Description
Choosing a partition for It is recommended that all server nodes (Aspect Directory, Connectivity
installing the operating Servers, Applications Servers, etc.) use at least one additional partition for
system. the operateITData and operateITTemp folders. For best performance, the
additional partition should be on a separate disk or disk array from the
operating system.
There may be additional disk requirements for Applications Servers. If
installing the Information Management Server function on this node, at
least one additional NTFS partition is needed for storing historical data.
This partition can be the same as the operateITData and operateITTemp
partition or be a separate partition. The amount of disks, disk space, and
disk I/O needed for the Information Management node are dependent on
the final configuration for the node.
To maximize the performance for any server, any additional partitions
should be a separate disk or disk array from the root partition.
Selecting Regional Refer to Regional and Language Options on page 223.
Settings
Time Zone Make sure the Automatically adjust clock for daylight saving changes
check box is enabled (if daylight saving time is used).
200 3BSE040587-601
Appendix A Prerequisites Windows Operating System Updates
3BSE040587-601 201
Configuring Network Adapters Appendix A Prerequisites
Refer to Windows Help > Networking for more information on how to install and
configure TCP/IP network adapters.
Refer to System 800xA Network Configuration (3BSE034463*) for configuration
of DNS.
The following procedure applies to the Workstation Operating System nodes. The
procedure for the Server Operating System nodes may vary from the one shown
here.
To configure the network adapters:
1. Open Windows Control Panel.
2. Double-click Network and Sharing Center to open the Network and Sharing
Center.
3. Click Change Adapter Settings.
4. Right-click on the network adapter and select Properties from the context
menu to open the Connection Properties dialog box.
5. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties to open
the Internet Protocol (TCP/IP) Properties dialog box.
6. Select Use the following IP address.
7. Enter the IP address in the IP address and the subnet mask in the Subnet fields
according to the planning done in Installation and Configuration Parameter
Worksheet.
8. Enter the IP address of the default gateway in the Default gateway field (if
required by topology).
9. Enter the IP address of the Primary Domain Server in the Preferred DNS
server field.
10. Enter the IP address of the Secondary Domain Server in the Alternate DNS
server field.
Always specify the Domain Servers with their primary client/server network
addresses. This is true for all network adapters, including the ones for secondary
client/server networks.
202 3BSE040587-601
Appendix A Prerequisites Configuring Network Adapters
11. Repeat for all network adapters in the servers and workstations.
Use the same DNS settings for all network adapters.
12. For all interfaces on separate Control Networks three configuration changes
(compared to the default settings) must be done to reduce the amount of traffic
on the Control Network.
a. Disable IPv6 by clearing the check box Internet Protocol Version 6
(TCP/IPv6).
b. Click Properties in the Internet Protocol (TCP/IP) Properties dialog to
open the Advanced TCP/IP settings dialog.
c. Click the DNS tab.
d. Clear the check box Register this connection's addresses in DNS.
e. Click the WINS tab.
f. Select Disable NetBIOS over TCP/IP.
13. Click OK as necessary to save the newly configured values, and then click
Close to close the Connection Properties dialog box.
14. Connect the Ethernet cables. Match each of the icons with its corresponding
Ethernet connector on the server or workstation.
15. Use ping -a from a Windows command prompt to verify the server or
workstation has contact with the Domain Controller:
C:\>ping -a 172.16.40.1
Pinging MM-DC1 [172.16.40.1] with 32 bytes of data:
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Reply from 172.16.40.1: bytes=32 time<1ms TTL=128
Ping statistics for 172.16.40.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0%
loss),
Approximate round trip times in milli-seconds:
3BSE040587-601 203
Configuring Domain Controller and DNS Server Appendix A Prerequisites
The connection may not work through more than one network adapter before
RNRP is installed.
Verify the port speed and duplex configuration on both ends (Network Adapter
and network switch). Refer to System 800xA Network Configuration
(3BSE034463*).
16. Verify the primary Client Server network is bound first for RNRP
configurations.
From the Change Adapter Settings:
a. Use the Alt key to expose the Advanced Settings menu.
b. Select Advanced Settings.
c. Verify the Primary Client Server Network is bound first and the
Redundant Client Server Network is second.
d. Make corrections as needed.
17. Disable all unused NIC cards.
The primary NIC card can only have one TCP/IP address. If the card consists
more than one TCP/IP address, RNRP will not function correctly.
If the Domain Controller uses any network interface in addition to the ones for
the client/server network, the DNS Server need to be configured to only listen to
DNS requests on the client/server network. Perform the following for all Domain
Controllers.
• Open the Interfaces tab under Properties for the DNS Server.
• Make sure that only the IP addresses for the client/server network are
selected.
The below 800xA software must be installed on the standalone domain controllers
manually browsing the media for:
204 3BSE040587-601
Appendix A Prerequisites Configuring Domain Controller and DNS Server
3BSE040587-601 205
Configuring Domain Controller and DNS Server Appendix A Prerequisites
Ensure that Internet Protocol Version 4 (TCP/IP V4) is the only protocol
configured on the node.
Create a new domain by setting up a new Domain Controller and DNS server using
the Server Manager.
To set up a new domain, configure the IP addresses of the Domain Server node if
this is not already done.
• Set the IP addresses.
• Set the IP address of this computer as the Preferred DNS Server on the
primary network adapter.
• If using, or planning on using two Domain Servers, set the IP address of the
other Domain Server as the Alternate DNS Server on the primary network
adapter.
• If using a redundant network, use the same DNS settings on the secondary
network adapter.
206 3BSE040587-601
Appendix A Prerequisites Configuring Domain Controller and DNS Server
3BSE040587-601 207
Configuring Domain Controller and DNS Server Appendix A Prerequisites
Membership in the Domain Admins group for the domain in which the second
Domain Controller is being installed is the minimum required to complete this
procedure. Details about using the appropriate accounts and group memberships
can be found at http://technet.microsoft.com/en-us/library/dn487460.aspx.
To install AD DS on a Domain Controller in an existing domain:
1. Go to Server Manager
2. Click Add Roles in the Roles Summary dialog box.
3. Review the information in the Before You Begin dialog box (if necessary) and
click Next.
4. Select the Active Directory Domain Services check box in the Select Server
Roles dialog box and click Next.
5. Review the information in the Active Directory Domain Services dialog box
and click Next.
208 3BSE040587-601
Appendix A Prerequisites Configuring Domain Controller and DNS Server
3BSE040587-601 209
Adding Nodes to a Domain Appendix A Prerequisites
210 3BSE040587-601
Appendix A Prerequisites Configuring Users and Groups
3BSE040587-601 211
Configuring Users and Groups Appendix A Prerequisites
For 800xA Systems in a Windows Workgroup all the users and groups shall be
created locally on each node with same user group name, user name and
password.
The following procedure is used to create various domain accounts to be used in
System 800xA. Create two domain accounts with administrator privileges.
The 800xA Service User will be reserved for use by the 800xA System Services.
This account will NOT be used for installation, administration, configuration, or any
other system related procedures.
The 800xA Installation account must be created to complete the 800xA System
software installation and post installation procedures. Create other user accounts for
other 800xA System activities such as Application Engineer, System Engineer, and
Operator.
Define separate accounts and different passwords for the 800xA Service User and
the 800xA installing User.
212 3BSE040587-601
Appendix A Prerequisites Configuring Users and Groups
Domain Administrator users are powerful for administrative purposes but could
by this also be dangerous from a security perspective. For security reasons the
number of users in the Domain Administrator group should be kept to a
minimum.
The 800xA Service User and 800xA Installing User do not need to be members
of the Domain Administrators group. They both need to be members of the
Builtin Administrators group on the 800xA System nodes but not on the Domain
Controller, unless it is combined with an 800xA Server.
The 800xA Installing User could be a Domain Administrator but should be set to
passive after the installation of the System. The 800xA Service User should not
be a Domain Administrator and also not a local administrator on the Domain
Controller.
The various users and groups required by the 800xA System are described in
Table 8. All groups/users must reside on the 800xA System domain.
This setup may be performed by yourself, or the domain administrator may perform
the setup. In either case, use the guidelines in Table 8, and follow the step-by-step
procedures following Table 8.
Groups/Users Description
IndustrialITAdmin Group Create the IndustrialITAdmin Group. All 800xA System
administrators (including the 800xA Service User) must be
a member of the IndustrialITAdmin group.
IndustrialITUser Group Create the IndustrialITUser Group. All 800xA System
users must be a member of the IndustrialITUser group.
3BSE040587-601 213
Configuring Users and Groups Appendix A Prerequisites
Groups/Users Description
800xA Service User Create a new user for 800xA System services. Make this
user a member of the IndustrialITAdmin Group, the
IndustrialITUser Group, and the local administrator group
on every system node.
All 800xA System services will run under this account.
Make the name easy to recognize (for example:
800xAService).
NOTE 1: Creating this user requires being logged in as
domain administrator. Adding this user to the local
administrator group on every system node requires being
logged in as local administrator.
NOTE 2: The 800xA Service User must not be a member
of the Domain Administrator group. These users should be
members of the Built-in Administrators group on the
Domain Controller node.
Other 800xA System users Create additional users for system configuration and
operation. These users are added to the IndustrialITUser
Group. Refer the System 800xA 6.0 Administration and
Security (3BSE037410*) for more information on user
permissions.
214 3BSE040587-601
Appendix A Prerequisites New Organizational Unit
Groups
This procedure assumes the Industrial IT organization unit has been created.
3BSE040587-601 215
Users, Groups, and Rights Assignments Appendix A Prerequisites
Organizational
User Group User Account Description
Unit
Industrial IT IndustrialITAdmin SwServiceAccount CHMI System service account
SysAdmin CHMI System account
Administrator Built-in account
IndustrialITUser SwServiceAccount CHMI System service account
SysAdmin CHMI System account
Operator Default operator 1
AppEng Application Engineer
Administrator Windows default administrator
account
216 3BSE040587-601
Appendix A Prerequisites Users, Groups, and Rights Assignments
3BSE040587-601 217
800xA Service User Appendix A Prerequisites
2. Click Add User or Group... button to add the user or groups as per Table 11.
3. Click OK to close the policy.
Creating this user requires being logged in as domain administrator. Adding this
user to the local administrator group on every system node requires being logged
in as local administrator.
Create the CHMI Service User. This is the user account that all 800xA System
services will run under. Make this new user a member of the following groups:
• IndustrialITAdmin Group
• IndustrialITUser Group
218 3BSE040587-601
Appendix A Prerequisites 800xA Service User
3BSE040587-601 219
800xA Service User Appendix A Prerequisites
e. Select the new user (for example, SwService) and click Add.
f. Repeat Step e to add other users to the IndustrialITAdmin group.
g. Click OK when finished.
h. Click OK on the Members tab of the Properties dialog box.
8. Add this user to the Built-in Administrators group on the Domain Controller
node.
220 3BSE040587-601
Appendix A Prerequisites Other Users
9. Add this user to the local administrator group on every system node.
Other Users
Add other IndustrialIT users and make them members of the IndustrialIT User
Group. Set passwords according to company policy, and change them frequently.
Examples of users who can be members of the IndustrialITUser groups is as shown
in Table 12.
Ensure that the User Account names do not exceed the 20 character limit.
3BSE040587-601 221
Adding 800xA Domain Users to the Local Administrator Group Appendix A Prerequisites
222 3BSE040587-601
Appendix A Prerequisites Operating System Setup Use with Compact HMI
3BSE040587-601 223
Enable Write Caching on Hard Disks Appendix A Prerequisites
6. Verify that the value in the Decimal symbol field drop-down list is a dot (.). If
it is not, change it to a dot (.) and click Apply and then OK.
7. Click the Administrative tab.
8. Click Change system locale... to launch the Region Settings dialog box.
9. Verify that the value in the Current system locale drop-down list is English
(United States). If it is not, change it to English (United States) and click OK
to return to the Administrative tab of the Region dialog box.
10. Click Copy settings to launch the Welcome Screen and New User Accounts
Settings dialog box.
11. Enable the Welcome screen and system accounts and New User Accounts
check boxes and click OK.
12. Click OK to exit the Region dialog box.
13. Close Windows Control Panel.
224 3BSE040587-601
Appendix A Prerequisites Internet Explorer Enhanced Security
3BSE040587-601 225
Internet Security Settings for Digital Signature Validation Appendix A Prerequisites
226 3BSE040587-601
Appendix A Prerequisites Energy Saver and Screen Saver Configuration
8. Click Apply, wait, and then click OK to close the Performance Options dialog
box.
9. Click OK to close the System Properties dialog box.
3BSE040587-601 227
Enable the Change Sharing Options for Different Network Profiles Appendix A Prerequisites
To disable the automatic updates by setting the Windows Automatic Updates feature
to never check for updates:
1. Open Windows Update
2. In the left pane, click Change Settings
3. Under Important Updates choose Never check for updates
228 3BSE040587-601
Appendix A Prerequisites Group Policy Management
Domain Environment
Perform this procedure before installing 800xA System and Functional Area
software.
2. Navigate to the following in the left pane of the Group Policy Object Editor:
Forest:domain name >Domains >domain name >Group Policy Objects
3. Right-click on Group Policy Objects in the left pane of the Group Policy
Management Console, and select Create a GPO in this domain from the
context menu to open the New GPO dialog box.
3BSE040587-601 229
Group Policy Management Appendix A Prerequisites
4. Type in a name for the new Group Policy Object in the New GPO dialog box;
for example, IntranetName and click OK to return to the Group Policy
Management Console.
5. Right-click on the new Group Policy Object in the left pane of the Group
Policy Management Console, and select Edit from the context menu to open
the Group Policy Object Editor.
6. Navigate to the following in the left pane of the Group Policy Object Editor:
User Configuration > Policies > Administrative Templates >
Windows Components > Internet Explorer >
Internet Control Panel > Security Page
7. Double-click Turn on automatic detection of intranet, a dialog box appears.
8. Click Disabled and click OK.
9. Double-click Intranet Sites: Include all local (intranet) sites not listed in
other zones, a dialog box appears.
10. Click Enabled and click OK.
11. Double-click Intranet Sites: Include all sites that bypass the proxy server, a
dialog box appears.
12. Click Disabled and click OK.
13. Double-click Intranet Sites: Include all network paths (UNCs), a dialog box
appears.
14. Click Disabled and click OK.
15. Close the Group Policy Object Editor.
16. Reboot the node.
230 3BSE040587-601
Appendix A Prerequisites Group Policy Management
Forest: Domain Name > Domains > Domain Name > Group Policy
Objects > Default Domain Controllers Policy
3. Right-click Default Domain Controllers Policy and select Edit from
the context menu to launch the Group Policy Management Editor.
4. Navigate to the following:
Default Domain Controllers Policy > Computer Configuration
Policies > Windows Settings > Security Settings > Local Policies >
User Rights Assignment
5. In the right pane, double-click Add workstations to domain to launch the
Add workstations to domain Properties dialog box.
6. Select Authenticated Users and click Remove.
7. Click Add User or Group to launch the Add User or Group dialog box.
8. Click Browse to launch the Select Users, Computers, or Groups dialog box.
9. Select the users and/or groups that are to have the authority to add workstations
to the domain and click OK twice to return to the Add workstations to domain
Properties dialog box.
Click Find Now in the Select Users, Computers, or Groups dialog box to display
the available users and groups.
10. Click Apply and then OK to close the dialog box.
11. Close the Group Policy Management Editor.
Group Policy. This procedure must be performed on every node in the Windows
Workgroup. If the system is expanded at a later time, this procedure must be
performed on each node added during the expansion.
3BSE040587-601 231
Remote (Thin) Client for the Server Operating System Appendix A Prerequisites
232 3BSE040587-601
Appendix A Prerequisites Other Third Party Software
6. On Select destination server page, click select a server from the pool for
new roles.
7. Click Next.
8. On Select server roles page, select Remote Desktop Services as additional
role.
If Terminal Services is already installed on the server, the Terminal Services
check box will be selected and dimmed.
9. Click Next.
10. On Select features page, click Next without changing the features.
11. On Remote Desktop Services page, click Next.
12. On Select role services page, select Remote Desktop Licensing role.
If installing the Terminal Server role service on a Domain Controller, a warning
message indicating that Installing the Terminal Server role service on a Domain
Controller is not recommended will appear.
13. Click Add Features and click Next.
14. Verify the added roles and features on Confirm installation selections page
and click Install.
15. Restart the node when the installation is complete.
3BSE040587-601 233
Microsoft Word Appendix A Prerequisites
Microsoft Word
When installing Microsoft Word it is required to select Office Shared Features
from the Installation Options dialog box and to accept the default subfeatures
under the Office Shared Features selection.
Microsoft Word, which is part of the Microsoft Office Professional suite, must be
installed on all nodes where the following functions will be used:
• Process Graphics (for Reference Documentation Tool)
• Engineering Studio (for Document Manager Functions)
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.
234 3BSE040587-601
Appendix A Prerequisites Microsoft Excel
Microsoft Excel
When installing Microsoft Excel 2010 or 2013 it is required to select Office
Shared Features from the Installation Options dialog box and to accept the default
subfeatures under the Office Shared Features selection.
When installing Microsoft Excel, select the Custom installation. When the
Installation Options dialog box appears. select the Visual Basic for Applications
option under Shared Features.
Open Microsoft Excel and perform the recommended settings, if prompted.
Navigate to File > Options > General, and clear the Show the start screen
when this application starts check box.
Microsoft Excel, which is part of the Microsoft Office Professional suite, must be
installed on all 800xA System nodes where engineering tools or Excel based reports
will be used. This can include the following:
• Process Graphics (for Display Documentation Tool)
• Engineering Studio (for Bulk Data Manager Functions)
• DataDirect - Excel Data Access
This software is available from any Microsoft reseller. Follow the installation
procedure described in the documentation provided by Microsoft.
3BSE040587-601 235
Crystal Reports Appendix A Prerequisites
Crystal Reports
Crystal Reports can be used to create reports of System 800xA Data. When used
with the application scheduler, the reports can be automatically executed.
Crystal Reports will typically be installed on nodes where the, Information
Manager, node function is allocated. However, it can be installed on any node that
has access to 800xA data reporting interfaces (800xA DataDirect or ODBC). Follow
the procedure to install Crystal Reports.
System 800xA latest release supports Crystal Reports 2013 version. Table 13 lists
the installed versions and available builds in the SAP portal.
Build Website
Crystal reports 2013 + It will be available as part of Crystal reports 2013
Crystal Reports Runtime install media.
(CRforVS_redist_install_32bit_13_0_14) Download the Crystal Reports Runtime from the
location specified below.
• From the URL
http://scn.sap.com/docs/DOC-7824
• Click 32bit.msi from MSI 32 bit column as
shown in the Figure 133 to install.
236 3BSE040587-601
Appendix A Prerequisites Autocad Integration
Autocad Integration
As a prerequisite to use AutoCAD for Document Manager and Parameter Manger,
install AUTOCAD VBA Enabler by downloading the software from the AutoCAD
website.
<
McAfee Integration
McAfee VirusScan® Enterprise has been tested and qualified virus scanner that is
used on all System 800xA servers and workstations. Refer to System 800xA
Installing and Configuring McAfee ePO Server (9ARD107543-005), for more
information.
McAfee need not be disabled during installation, however this might impact
Installation performance of 800xA Software.
Symantec
Symantec Endpoint Protection (SEP) has been tested and qualified virus scanner
that is used on all System 800xA servers and workstations. Refer to System 800xA
Using Symantec Endpoint Protection (9ARD119854-002), for more information.
3BSE040587-601 237
Bulk SPL Template Appendix A Prerequisites
Backup Software
It is recommended that a third party backup/restore and/or disk imaging utility be
used to save (and restore if necessary) server and workstation hard drives. A valid
backup insures that the system can be restored.
238 3BSE040587-601
Index
A
Acknowledge 133
Adding nodes to domain 210
Alarm Band 136
Alarms and events 133
Aspect Object 21
Aspect View 22
Aspects 21
Alarm and Event 80
Alarm and Event Configuration 81
Graphical Elements 77
History Logging 81
Log Configuration 81
Process Displays 95
Security Definition 111
Audit Trail
disable 110
enable 110
Automatic updates 227
B
Back to Previous Display 115, 117, 119
Backup software 238
Backup/Restore
Ghost 146
Breadcrumb list 122
C
Connectivity to AC 800M 60
Context Menu 125
D
Default user groups and users 216
Defragmenting disks 199
Disks and file system 198
Display bar 119
Display links 125
3BSE040587-601 239
E IP addresses 71
Energy saver 227
Excel 235 L
License installation 55
F Log Configuration 81
Faceplate views
Extended 129 M
Faceplate 129 Microsoft Excel 235
Reduced 129 Microsoft Word 234
Faceplates 79
File system 198 N
Function keys 126 Network adapters 201
Functional Structure 90
O
G OPC names 76
Graphical displays 77 OPC Server for PLC 67
Groups 211 Operator Workplace 24
Other Third Party Software 233
H
Hidden alarms 133 P
Hot Keys 126 Plant Explorer 24
Hot keys 124 PLC signal 75
Preparing the node 53
I Process Alarms 133
IE enhanced security configuration 225 Process Event List 137
Installation Process Events 137
Directory 199
Prerequisites R
Adding nodes to domain 210 Remote client 232
Backup software 238
Microsoft Excel 235 S
Microsoft Word 234 security setting 111
Miscellaneous Windows setup 223 Start display 124
Network adapters 201 Status Bar 121
Remote client 232 Structures 23
Terminal server 232 Control Structure 90
Users and groups 211 Object Type Structure 74
Windows 197 Supervision 128
Windows installation guidelines 200 System Alarms 136
240 3BSE040587-601
System Event List 138
System Events 138
System startup 60
T
Terminal server 232
Trend Display 97
U
Upgrade from Compact HMI SP2 Rev C to 5.1 57
Upgrade to 800xA 59
User groups and users
Default 216
Users 211
W
Windows operating system 197
Installation guidelines 200
Miscellaneous setup 223
Word 234
3BSE040587-601 241
242 3BSE040587-601
Revision History
Introduction
This section provides information on the revision history of this user manual.
The revision index of this user manual is not related to the Compact HMI 6.0.1
System Revision.
Revision History
The following table lists the revision history of this user manual.
Revision
Description Date
Index
- First version published for Compact HMI 6.0.1 February 2016
3BSE040587-601 243
Revision History
244 3BSE040587-601
Contact us
www.abb.com/compactproductsuite
3BSE040587-601
Copyright © 2005-2015 by ABB.
www.abb.com/controlsystems All rights reserved.