ABB COM600 series User manual

COM600 Station Automation Series
COM600 3.2
User's Guide

Contents:
1. About this manual .................................................................................. 5
1.1. Copyrights ...................................................................................... 5
1.2. Trademarks .................................................................................... 5
1.3. General .......................................................................................... 5
1.4. Document conventions .................................................................. 6
1.5. Use of symbols .............................................................................. 6
1.6. Terminology .................................................................................... 7
1.7. Abbreviations ................................................................................. 8
1.8. Related documents ........................................................................ 9
1.9. Document revisions ..................................................................... 10
2. Product overview .................................................................................. 11
2.1. About this section ......................................................................... 11
2.2. Product overview ......................................................................... 11
2.3. Features ....................................................................................... 12
2.3.1. Gateway functionality .................................................... 12
2.3.2. HMI ................................................................................ 14
2.3.2.1. HMI functions ............................................. 14
2.3.2.2. Predefined user account ............................ 15
2.3.3. OPC server ................................................................... 15
2.3.4. OPC client ..................................................................... 16
2.3.5. IEC 61850 data modelling ............................................. 17
2.3.6. Station/Remote switch function ..................................... 19
2.3.7. COM600 Watchdog ....................................................... 20
2.3.8. External watchdog for COM600 .................................... 20
2.3.9. Network Fault Tolerance for COM600 ........................... 20
2.3.10. Queuing of Process Data Updates ............................... 21
2.4. Hardware ..................................................................................... 22
2.4.1. Mechanical properties ................................................... 22
2.4.2. Mounting of COM600 computer .................................... 23
2.4.3. Setting up the COM 2 port for RS-232/RS-485 ............ 24
3. Installation ............................................................................................. 26
3.1. About this section ......................................................................... 26
3.2. Requirements for Communication Engineering Tool ................... 26
3.3. Installing Communication Engineering Tool ................................. 26
3.4. Updating CET .............................................................................. 27
3.5. Setting up the COM600 computer ............................................... 27
3.5.1. Accessing the COM600 computer ................................ 27
3.6. Uninstalling Communication Engineering Tool ............................ 30
3.7. Turning off COM600 computer ..................................................... 31
4. Configuration ........................................................................................ 32
3
COM600 3.2
COM600 Station Automation Series1MRS756125
User's Guide
Issued: 16.10.2006
Version: E/17.06.2008

4.1. About this section ........................................................................ 32
4.2. Configuration and maintenance ................................................... 32
4.3. Configuration process .................................................................. 33
4.3.1. Overview of configuration process ................................ 33
4.3.2. Building object structures .............................................. 35
4.3.2.1. OPC servers ............................................... 35
4.3.2.2. Substation structure for HMI ...................... 35
4.3.2.3. OPC clients ................................................ 36
4.3.3. Configuring objects ....................................................... 37
4.3.3.1. General about configuring objects .............. 37
4.3.3.2. SCL Import function .................................... 38
4.3.3.3. Cross-References function ......................... 39
4.3.4. Configuration of Station/Remote switch ........................ 40
4.3.5. Event definitions ............................................................ 40
4.3.5.1. Creating event definitions ........................... 40
4.3.5.2. Configuring event definitions ..................... 41
4.3.6. Grouping Alarms ........................................................... 42
4.3.7. Using scales .................................................................. 44
4.3.7.1. General about using scales ........................ 44
4.3.7.2. Creating scales ........................................... 44
4.3.7.3. Configuring scales ..................................... 45
4.4. Backup and restore ...................................................................... 47
4.5. Retrieving a previous configuration ............................................. 47
4.6. SCL Export ................................................................................... 48
4.7. Configuring external watchdog for COM600 ................................ 48
4.8. Installing Duo Driver ..................................................................... 49
5. Operation ............................................................................................... 51
5.1. Activating Gateway with new configurations ................................ 51
Index .............................................................................................................. 53
4
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

About this manual1.
Copyrights1.1.
The information in this document is subject to change without notice and should not be
construed as a commitment by ABB Oy. ABB Oy assumes no responsibility for any
errors that may appear in this document.
In no event shallABB Oy be liable for direct, indirect, special, incidental or consequential
damages of any nature or kind arising from the use of this document, nor shallABB Oy
be liable for incidental or consequential damages arising from use of any software or
hardware described in this document.
This document and parts thereof must not be reproduced or copied without written per-
mission from ABB Oy, and the contents thereof must not be imparted to a third party
nor used for any unauthorized purpose.
The software or hardware described in this document is furnished under a license and
may be used, copied, or disclosed only in accordance with the terms of such license.
©Copyright 2006 ABB. All rights reserved.
Trademarks1.2.
ABB is a registered trademark ofABB Group. All other brand or product names men-
tioned in this document may be trademarks or registered trademarks of their respective
holders.
General1.3.
This manual provides thorough information on the StationAutomation COM600 Series
and the central concepts related to it. For more information on each topic related to a
specific protocol, refer to the list of related documents in 1.8, Related documents.
Information in this user's guide is intended for application engineers who install the
servers and clients needed to configure the different components.As a prerequisite, you
should have basic knowledge of client and server architectures in general. Note that the
protocol specific server and client user's guides contain more detailed information and
should be used to complement this manual.
5
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

Document conventions1.4.
The following conventions are used for the presentation of material:
•The words in names of screen elements (for example, the title in the title bar of a
window, the label for a field of a dialog box) are initially capitalized.
•Capital letters are used for the name of a keyboard key if it is labeled on the keyboard.
For example, press the ENTER key.
•Lowercase letters are used for the name of a keyboard key that is not labeled on the
keyboard. For example, the space bar, comma key, and so on.
•Press CTRL+C indicates that you must hold down the CTRL key while pressing
the C key (to copy a selected object in this case).
•Press ESC E C indicates that you press and release each key in sequence (to copy
a selected object in this case).
•The names of push and toggle buttons are boldfaced. For example, click OK.
•The names of menus and menu items are boldfaced. For example, the File menu.
•The following convention is used for menu operations: MenuName > Menu-
Item > CascadedMenuItem. For example: select File > New > Type.
•The Start menu name always refers to the Start menu on theWindows taskbar.
•System prompts/messages and user responses/input are shown in the Courier font.
For example, if you enter a value out of range, the following message is displayed:
Entered value is not valid. The value must be 0 to 30.
•You may be told to enter the string MIF349 in a field.The string is shown as follows
in the procedure:
MIF349
•Variables are shown using lowercase letters:
sequence name
Use of symbols1.5.
This publication includes warning, caution, and information icons that point out safety
related conditions or other important information. It also includes tip icons to point out
useful information to the reader. The corresponding icons should be interpreted as follows.
The electrical warning icon indicates the presence of a hazard
which could result in electrical shock.
The warning icon indicates the presence of a hazard which
could result in personal injury.
6
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

The caution icon indicates important information or warning
related to the concept discussed in the text. It might indicate
the presence of a hazard which could result in corruption of
software or damage to equipment or property.
The information icon alerts the reader to relevant facts and
conditions.
The tip icon indicates advice on, for example, how to design
your project or how to use a certain function.
Terminology1.6.
The following is a list of terms associated with the Station Automation COM600 Series
that you should be familiar with. The list contains terms that are unique to ABB or have
a usage or definition that is different from standard industry usage.
DescriptionTerm
An abnormal state of a condition.Alarm
An OPC service for providing information about alarms and
events to OPC clients.
Alarms and Events; AE
An OPC service for providing information about process data to
OPC clients.
Data Access; DA
Part of a logical node object representing specific information,
e.g., status or measurement. From an object-oriented point of
view a data object is an instance of a class data object. DOs are
normally used as transaction objects; i.e., they are data struc-
tures.
Data Object; DO
The data set is the content basis for reporting and logging. The
data set contains references to the data and data attribute val-
ues.
Data Set
A physical device that behaves as its own communication node
in the network, e.g. protection relay.
Device
Change of process data or an OPC internal value. Normally, an
event consists of value, quality and timestamp.
Event
A physical IEC 61850 device that behaves as its own commu-
nication node in the IEC 61850 protocol.
Intelligent Electronic Device
Representation of a group of functions. Each function is defined
as a logical node. A physical device consists of one or several
LDs.
Logical Device; LD
7
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

DescriptionTerm
The smallest part of a function that exchanges data. A LN is an
object defined by its data and methods.
Logical Node; LN
A communication protocol developed by Echelon.LON
A proprietary method of ABB on top of the standard LON pro-
tocol.
LON Application Guideline for
substation automation; LAG
Series of standards specifications aiming at open connectivity
in industrial automation and the enterprise systems that support
industry.
OPC
Representation of a connection to the data source within the
OPC server. An OPC item is identified by a string <object
path>:<property name>. Associated with each OPC item are
Value, Quality and Time Stamp.
OPC item
Named data item.Property
The report control block controls the reporting processes for
event data as they occur. The reporting process continues as
long as the communication is available.
Report Control Block
ABB proprietary communication protocol used in substation
automation.
SPA
Protection and/or Control Product supporting the SPA protocol
version 2.5 or earlier.
SPA device
XML-based description language for configurations of electrical
substation IEDs. Defined in IEC 61850 standard.
Substation Configuration Lan-
guage; SCL
Abbreviations1.7.
The following is a list of abbreviations associated with the StationAutomation COM600
Series that you should be familiar with. See also 1.6, Terminology.
DescriptionAbbreviation
Alarms and EventsAE
Application Service Data UnitASDU
Buffered Report Control BlockBRCB
Communication Engineering ToolCET
Data AccessDA
Data Message Code DefinitionDMCD
Data ObjectDO
Gateway, component connecting two communication networks togetherGW
Human Machine InterfaceHMI
International Electrotechnical CommissionIEC
8
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

DescriptionAbbreviation
Intelligent Electronic DeviceIED
LON Application Guideline for substation automationLAG
Local Area NetworkLAN
Logical DeviceLD
LonMark interoperable device communicating in LonWorks network. In
this document the term is used for devices that do not support the ABB
LON/LAG communication.
LMK
Logical NodeLN
LON SPA GatewayLSG
Network Control CenterNCC
Network VariableNV
Object Linking and EmbeddingOLE
OLE for Process ControlOPC
Protection & ControlP&C
Request To SendRTS
Substation AutomationSA
Substation Configuration LanguageSCL
Single Line DiagramSLD
Simple Network Time ProtocolSNTP
Simple Object Access ProtocolSOAP
Report Control BlockRCB
Unbuffered Report Control BlockURCB
eXtended Markup LanguageXML
Related documents1.8.
MRS numberName of the manual
1MRS756121COM605 Operator's Manual
1MRS756122COM610 Operator's Manual
1MRS756123COM615 Operator's Manual
1MRS756124COM605, COM615 HMI Configuration Manual
1MRS756566DNP LAN/WAN Master (OPC)
1MRS756567DNP Serial Master (OPC)
1MRS755496DNP LAN/WAN Slave (OPC)
9
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

MRS numberName of the manual
1MRS755495DNP Serial Slave (OPC)
1MRS755564External OPC Client Access
1MRS755382IEC 60870-5-101 Slave (OPC)
1MRS752278IEC 60870-5-103 Master (OPC)
1MRS755384IEC 60870-5-104 Slave (OPC)
1MRS755321IEC 61850 Master (OPC)
1MRS755284LON-LAG Master (OPC)
1MRS756569MNS iS Connectivity (OPC)
1MRS756126Modbus Serial Master (OPC)
1MRS756445Modbus TCP Master (OPC)
1MRS752275SPA Master (OPC)
1MRS755497SPA Router (OPC)
Document revisions1.9.
HistoryProduct revisionDocument version/date
Document created3.0A/16.10.2006
Document revised3.0B/22.1.2007
Document revised3.0C/8.6.2007
Document revised3.1D/21.12.2007
Document revised3.2E/17.06.2008
10
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

Product overview2.
About this section2.1.
This section gives an overview of the COM600 Series, its components and functions, as
well as the IEC 61850 data modelling principles.
Product overview2.2.
Station Automation COM600 Series includes the following three products:
•Control and Monitoring Unit COM605
•Communication Gateway COM610
•Station Computer COM615
Control and Monitoring Unit COM605 allows easy access to the protection and control
devices of a substation with HMI functionality. The substation can be accessed either
locally or remotely through a built-in web server.
CommunicationGatewayCOM610 acts as an embedded communication gatewaybetween
substation automation protection and control devices and Network Control Centers
(NCC).
Station Computer COM615 combines the features and functions of COM605 and
COM615.
All products in COM600 Series use an embedded operating system and run in a dedicated
industrial computer without moving parts.
The products are configured using a separate engineering PC that is connected via the
local area network (LAN). For more information, refer to COM600 User's Guide.
Table 2.2-1 shows the basic functionalities of the products.
Table 2.2-1 Product functionalities
HMI functionalityGateway functionalityProduct
xCOM605
xCOM610
xxCOM615
Available protocols
Protocols that are supported by COM600 are shown in the table below. The master pro-
tocols are used in process communication and the slave protocols are used in upper level
communication. If a required protocol is not supported, please contact your local ABB
11
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

DistributionAutomation representative. For more detailed information on the protocols
refer to user’s guides listed in 1.8, Related documents.
Master protocols are supported by all products, where as Slave protocols are only sup-
ported by COM615 and COM610.
Slave protocolsMaster protocols
DNP 3.0 LAN/WANDNP 3.0 LAN/WAN
DNP 3.0 SerialDNP 3.0 Serial
External OPCIEC 61850
IEC 60870-5-101IEC 60870-5-103
IEC 60870-5-104LON-LAG
SPA RouterModbus Serial
Modbus TCP
MNSiS
SPA
Features2.3.
Gateway functionality2.3.1.
The Gateway functionality provides a framework that enables the use of OPC server and
client components, such as OPC Client for IEC 60870-5-101 and OPC Server for LON
LAG 1.4. This manual presents the principles that are common to the protocols available
at the moment as well as to those that will be applicable in the future. For protocol specific
information, refer to the respective client and server user’s guides.
12
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

Figure 2.3.1-1 Conceptual view of COM610 Gateway
1. Network Control Center (NCC)
2. Engineering PC with Communication Engineering Tool (CET)
3. COM610/615 with embedded operation system, OPC client(s) for NCC connection(s),
OPC server(s) for process connection
4. Protection and control devices
Normally, there is one OPC client per NCC connection. If you want to create several
NCC connections with the same protocol, you have to use multiple instances.
COM610/615 consists of OPC Data Access (DA) server and client components. OPC
Servers are used mainly for master/client protocol stacks to provide access to the data
in the devices connected with the protocol. OPC Clients are used for slave/server protocol
stacks to enable external systems to access data available in the OPC Servers.
13
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

GWComponents.jpg
Figure 2.3.1-2 Example of COM610 Gateway components
HMI2.3.2.
HMI functions2.3.2.1.
The HMI enables the user to access the COM600 computer via a web browser.
The features of HMI include:
•Single Line Diagram
•Busbar coloring
•Event lists
•Alarm lists
•Parameter settings
•Disturbance data upload
•System supervision
•Breaker and switch control
•Measurement display
•User management
14
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

sld_example.png
Figure 2.3.2.1-1 Example view of the COM600 HMI
The HMI can be accessed:
•locally via an optional local HMI screen
•locally by connecting your laptop to COM600 via LAN
•remotely through the internet or over LAN/WAN
Predefined user account2.3.2.2.
HMI has a predefined user account with administrator rights.
•User name: admin
•Password: adminadmin
When you log in for the first time as an administrator, you have to change the password
before you can proceed using HMI. If you forget the new password, restore the factory
settings with the Management tool in CET.After the factory settings have been restored,
you can only log in with the predefined administrator password mentioned above.
OPC server2.3.3.
The OPC server component consists of a Master/Client Protocol Stack, OPC DA/AE
Server and Configuration SCL.
15
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

The protocol stack component implements the protocol functions, such as handshaking
signal handling, message coding/decoding, check sum calculations, polling logic, protocol
level timers and so on. The OPC server/protocol handler implements the functionality
for publishing and updating data on the OPC interfaces and protocol conversion between
the OPC and the protocol stack using the common IEC 61850 data model.
The configuration of the OPC server and the protocol stack is handled using a configur-
ation parser. The OPC server is configured using Communication Engineering Tool.
The configuration information is exported to an SCL/XML configuration file according
to the IEC 61850 SCL specification. When the OPC server is started, the configuration
information is read from the file.
ServerConcept_a.jpg
Figure 2.3.3-1 Conceptual view of OPC server
OPC client2.3.4.
The OPC client software consists of a Slave/Server Protocol Stack, OPC DA Client,
Configuration SCL, OPC DataAccess Server andAlarm&Event server components for
diagnostic and control.
The protocol stack component implements the protocol functions, such as handshaking
signal handling, message coding/decoding, check sum calculations, polling logic, protocol
level timers and so on. The OPC client/protocol handler implements the functionality
for data subscription from the OPC servers and protocol conversion between the OPC
and the protocol stack using the common IEC 61850 data model.
The configuration of the OPC client and the protocol stack is handled using a configura-
tion SCL. The OPC server is configured using Communication Engineering Tool. The
configuration information is exported to the SCL/XML configuration file according to
the IEC 61850 SCL specification. When the OPC client is started the configuration
information is read from the file.
16
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

ClientConcept_b.jpg
Figure 2.3.4-1 Conceptual view of OPC client
IEC 61850 data modelling2.3.5.
To simplify protocol conversion and signal mapping in the gateway, each component
uses a common data model. The data model is based on common data classes and services
specified in the IEC 61850 standard. Each client and server component is a separate
program. The components interact with each other only via OPC interfaces. This means
that they can be developed and used independently as a part of the gateway as long as
they conform with the OPC DA and common data model specifications.
Protection and control products are connected to the gateway via OPC interfaces.Although
OPC provides means to access data on devices, it does not specify the semantics of the
data. This means that the same information is available in different formats depending
on which device and communication protocol is used. In addition, services, such as
breaker operation, vary among devices and protocols.
These differences complicate the reuse of gateway applications. To overcome this
problem, all the applicable data and services are remodeled in OPC servers according
to the data and service model specified in the IEC 61850 standard. This provides a pro-
tocol and device independent interface between the applications and the process. Fig-
ure 2.3.5-1 presents an overview of the IEC 61850 model usage.
17
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

IECmodeling.jpg
Figure 2.3.5-1 Overview of IEC 61850 model usage
The smallest unit in the IEC 61850 modelling is a data attribute which is linked to an
OPC item in the OPC server. A data attribute can be, for instance, the state value of a
double point object (stVal), quality information (q), or timestamp (t). In the OPC server
some of the services are also mapped to the same level as the attributes. This means that,
for example, control services (such as ctlOperOn, ctlOperOff) for operating a double
point object are available as OPC items.
For different types of data, the IEC 61850 standard defines over 30 common data classes
including a set of mandatory and optional attributes and services. For example, common
data classes are defined for Controllable double point (DPC), Single point status (SPS)
and Measured value (MV).
Furthermore, the standard defines approximately 90 functional groups of data, based on
common data classes. These groups are called logical nodes. Examples of logical nodes
are controllable switch (CSWI) and distance protection (PDIS).
Logical nodes can be further grouped below logical devices (LD), forming logical groups
within a physical device (IED), see Figure 2.3.5-2.
18
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide

LONNamespace.jpg
Figure 2.3.5-2 LON OPC Server name space in relation to IEC 61850 model
Station/Remote switch function2.3.6.
The COM610/615 gateway provides a common Station/Remote (S/R) switch functionality
for OPC servers and clients. The S/R switch is used to determine whether the objects in
a logical device of an IED can be controlled within the station or remotely via a gateway.
A station can have one or more S/R switches. The switches are either physical switches
or software switches in a simulated IED of an OPC server. The S/R switches are modeled
using the IEC 61850 SPS, SPC, DPS, DPC, INS or INC data class.
Each IED or logical device in an IED is linked with an S/R switch during the configuration
process. If a logical device has no linking information configured, the linking information
of the IED is used instead. At run-time, an OPC server publishes the logical device S/R
switch linking information for the OPC clients of the COM610/615 gateway. Each time
an OPC client sends a command to a device, it first checks the S/R switch position to
determine whether the operation is allowed or not: the COM610/615 gateway OPC client
is allowed to operate only if the S/R switch is in remote position.
A COM610/615 gateway OPC client has the operation modes disabled and enabled for
S/R switch handling. When the switch is in the enabled mode, the values for S/R switch
position failures are Allow controls if position unknown and Reject controls if position
unknown.
HMI is considered a local station HMI if it uses the local display of the COM600 computer
or if the ip address of the HMI client is in the range specified with a Station IPAddress
19
COM600 3.2
COM600 Station Automation Series
1MRS756125
User's Guide

Filter property in the Gateway object. Otherwise HMI is considered a remote HMI. The
state of the station/remote switch controls whether the operations are allowed from HMI
or not.
The station/remote switch for the HMI is configured with the SLD editor by inserting
the Station Switch Indicator symbol to the substation SLD and specifying the data object
for the position information. If a real switch indication is not available, it is possible to
use a simulated data from virtual IED. This can be done by creating an IED configuration
in the communication structure and setting the simulation mode of the IED to true.
COM600 Watchdog2.3.7.
The COM600 computer has a built in hardware watchdog function. The function can be
enabled with CET from the Gateway object properties. When enabled, the watchdog
monitors the COM600 software. If the COM600 software fails to send the keep-alive
triggering to the watchdog within a certain time, the watchdog will restart the COM600
computer.
External watchdog for COM6002.3.8.
COM600 can be configured to periodically send a command to an IED connected to
COM600. This can be used to monitor the health of the COM600. For example, SACO
16D2 can be connected with SPA protocol to COM600 and configured to create an alarm
if no command from COM600 is received within specified time. Configuration of an
external watchdog device is described in 4.7, Configuring external watchdog for COM600
Network Fault Tolerance for COM6002.3.9.
The COM600 can be configured to provide a certain level of tolerance against network
failure by using either theABB DuoDriver feature or the Intel Teaming Feature, Switch
Fault Tolerance. These features are available when the optional dual port PCI Ethernet
network adapter is used.
DuoDriver
DuoDriver implements the Parallel Redundancy Protocol (PRP) for Ethernet as specified
in IEC 62439 DIS. PRP is based on duplicated networks, where each message is sent
via both networks, the receiver node will accept the first received message and discard
the duplicate. Message replication and discard function is done by the DuoDriver and it
hides the two networks from the upper level applications. In PRP there is practically no
switch over time in the case of one of the network fails as every message is always sent
toboth networks.DuoDriver hasdiagnostic data,which canbe readwith IEC61850OPC
server. The diagnostic data can be further used on COM600 HMI and gateway applica-
tions. See 4.8, Installing Duo Driver for installation and configuration details.
20
1MRS756125
COM600 Station Automation Series
COM600 3.2
User's Guide