user's guide · • the start menu name always refers to the start menu on the windows...

COM 600 Station Automation SeriesCOM 600 3.0

User's Guide

Contents:

1. About this manual .................................................................................. 5

1.1. Copyrights ...................................................................................... 51.2. Trademarks .................................................................................... 51.3. General .......................................................................................... 51.4. Document conventions .................................................................. 61.5. Use of symbols .............................................................................. 61.6. Terminology .................................................................................... 71.7. Abbreviations ................................................................................. 81.8. Related documents ........................................................................ 91.9. Document revisions ..................................................................... 10

2. Product overview .................................................................................. 11

2.1. About this section ......................................................................... 112.2. Product overview ......................................................................... 112.3. Features ....................................................................................... 14

2.3.1. Gateway functionality .................................................... 142.3.2. HMI ................................................................................ 16

2.3.2.1. HMI functions ............................................. 162.3.2.2. Predefined user account ............................ 17

2.3.3. OPC server ................................................................... 172.3.4. OPC client ..................................................................... 182.3.5. IEC 61850 data modelling ............................................. 182.3.6. Station/Remote switch function ..................................... 202.3.7. Watchdog timer ............................................................. 212.3.8. Queuing of Process Data Updates ............................... 212.3.9. Hardware ....................................................................... 22

2.3.9.1. Mechanical properties ................................ 222.3.9.2. Environmental conditions ........................... 232.3.9.3. Setting up the COM 2 port for RS-232/RS-485

.................................................................... 23

3. Installation ............................................................................................. 25

3.1. About this section ......................................................................... 253.2. Hardware requirements for Communication Engineering Tool .... 253.3. Installing Communication Engineering Tool ................................. 253.4. Mounting of COM 600 computer .................................................. 303.5. Setting up the COM 600 computer .............................................. 31

3.5.1. Accessing the COM 600 computer ............................... 313.6. Uninstalling Communication Engineering Tool ............................ 353.7. Turning off COM 600 computer .................................................... 36

4. Configuration ........................................................................................ 37

4.1. About this section ........................................................................ 37

3

COM 600 3.0COM 600 Station Automation Series1MRS756125

User's GuideIssued: 16.10.2006Version: B/22.1.2007

4.2. Configuration and maintenance ................................................... 384.3. Backup and restore ...................................................................... 394.4. SCL Export ................................................................................... 394.5. Configuration process .................................................................. 40

4.5.1. Overview of configuration process ................................ 404.5.2. Building object structures .............................................. 41

4.5.2.1. OPC servers ............................................... 414.5.2.2. Substation structure for HMI ...................... 414.5.2.3. OPC clients ................................................ 42

4.5.3. Configuring objects ....................................................... 434.5.3.1. General about configuring objects .............. 434.5.3.2. SCL Import function .................................... 444.5.3.3. Cross-References function ......................... 45

4.5.4. Configuration of Station/Remote switch ........................ 464.5.5. Event definitions ............................................................ 47

4.5.5.1. Creating event definitions ........................... 474.5.5.2. Configuring event definitions ..................... 48

4.5.6. Using scales .................................................................. 494.5.6.1. General about using scales ........................ 494.5.6.2. Creating scales ........................................... 504.5.6.3. Configuring scales ..................................... 50

5. Operation ............................................................................................... 53

5.1. Activating Gateway with new configurations ................................ 53

Index .............................................................................................................. 55

4

1MRS756125COM 600 Station Automation SeriesCOM 600 3.0

User's Guide

About this manual1.

Copyrights1.1.

The information in this document is subject to change without notice and should not beconstrued as a commitment by ABB Oy. ABB Oy assumes no responsibility for anyerrors that may appear in this document.

In no event shall ABB Oy be liable for direct, indirect, special, incidental or consequentialdamages of any nature or kind arising from the use of this document, nor shall ABB Oybe liable for incidental or consequential damages arising from use of any software orhardware 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 partynor used for any unauthorized purpose.

The software or hardware described in this document is furnished under a license andmay be used, copied, or disclosed only in accordance with the terms of such license.

Copyright © 2006 ABB Oy

All rights reserved.

Trademarks1.2.

ABB is a registered trademark of ABB Group. All other brand or product names men-tioned in this document may be trademarks or registered trademarks of their respectiveholders.

General1.3.

This manual provides thorough information on the Station Automation COM 600 Seriesand the central concepts related to it. For more information on each topic related to aspecific protocol, refer to the list of related documents in 1.8, Related documents.

Information in this user's guide is intended for apllication engineers who install theservers and clients needed to configure the different components. As a prerequisite, youshould have basic knowledge of client and server architectures in general. Note that theprotocol specific server and client user's guides contain more detailed information andshould be used to complement this manual.

5


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 > MenuItem> CascadedMenuItem. For example: select File > New > Type.

• The Start menu name always refers to the Start menu on the Windows 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 followsin 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 safetyrelated conditions or other important information. It also includes tip icons to point outuseful information to the reader. The corresponding icons should be interpreted as follows.

The electrical warning icon indicates the presence of a hazardwhich could result in electrical shock.

The warning icon indicates the presence of a hazard whichcould result in personal injury.

6


User's Guide

The caution icon indicates important information or warningrelated to the concept discussed in the text. It might indicatethe presence of a hazard which could result in corruption ofsoftware or damage to equipment or property.

The information icon alerts the reader to relevant facts andconditions.

The tip icon indicates advice on, for example, how to designyour project or how to use a certain function.

Terminology1.6.

The following is a list of terms associated with the Station Automation COM 600 Seriesthat you should be familiar with. The list contains terms that are unique to ABB or havea 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 andevents to OPC clients.

Alarms and Events; AE

An OPC service for providing information about process data toOPC clients.

Data Access; DA

Part of a logical node object representing specific information,e.g., status or measurement. From an object-oriented point ofview a data object is an instance of a class data object. DOs arenormally 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. Thedata set contains references to the data and data attribute val-ues.

Data Set

A physical device that behaves as its own communication nodein the network, e.g. protection relay.

Device

Change of process data or an OPC internal value. Normally, anevent 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 definedas a logical node. A physical device consists of one or severalLDs.

Logical Device; LD

7


User's Guide

DescriptionTerm

The smallest part of a function that exchanges data. A LN is anobject 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 forsubstation automation; LAG

Series of standards specifications aiming at open connectivityin industrial automation and the enterprise systems that supportindustry.

OPC

Representation of a connection to the data source within theOPC server. An OPC item is identified by a string <objectpath>:<property name>. Associated with each OPC item areValue, Quality and Time Stamp.

OPC item

Named data item.Property

The report control block controls the reporting processes forevent data as they occur. The reporting process continues aslong as the communication is available.

Report Control Block

ABB proprietary communication protocol used in substationautomation.

SPA

Protection and/or Control Product supporting the SPA protocolversion 2.5 or earlier.

SPA device

XML-based description language for configurations of electricalsubstation IEDs. Defined in IEC 61850 standard.

Substation Configuration Lan-guage; SCL

Abbreviations1.7.

The following is a list of abbreviations associated with the Station Automation COM 600Series 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


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. Inthis document the term is used for devices that do not support the ABBLON/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

1MRS756121COM 605 3.0 Operator's Manual



1MRS756124COM 605, COM 615 HMI 3.0 ConfigurationManual

1MRS755496DNP3.0 Slave LAN/WAN (OPC) 3.0

1MRS755495DNP3.0 Slave Serial (OPC) 3.0

9


User's Guide

MRS numberName of the manual

1MRS755564External OPC Client Access 3.0

1MRS755382IEC 60870-5-101 Slave (OPC) 3.0

1MRS752278IEC 60870-5-103 Master (OPC) 3.0

1MRS755384IEC 60870-5-104 Slave (OPC) 3.0

1MRS755321IEC 61850 Master Protocol (OPC) 3.0

1MRS755284LON-LAG Master Protocol (OPC) 3.0

1MRS756126Modbus Master (OPC) 3.0

1MRS752275SPA Master Protocol (OPC) 3.0

1MRS755497SPA Router (OPC) 3.0

Document revisions1.9.

HistoryProduct revisionDocument version/date

Document created3.0A/16.10.2006

Document revised3.0B/22.1.2007

10


User's Guide

Product overview2.

About this section2.1.

This section gives an overview of the COM 600 Series, its components and functions,as well as the IEC 61850 data modelling principles.

Product overview2.2.

Station Automation COM 600 Series includes the following three products:• Control and Monitoring Unit COM 605• Communication Gateway COM 610• Station Computer COM 615

Ordering codes

COM605S0M00_kuva3.jpg

Figure 2.2-1 Ordering code for COM 605

11


User's Guide

COM610S0M00S0_kuva2.jpg


COM615S0M00S0_kuva1.jpg


Product functionalities

Table 2.2-1 shows the basic functionalities of the products.

Table 2.2-1 Product functionalitiesHMI functionalityGateway functionalityProduct

xCOM 605

xCOM 610

xxCOM 615

12


User's Guide

Control and Monitoring Unit COM 605 allows easy access to the protection and controldevices of a substation with HMI functionality. The substation can be accessed eitherlocally or remotely through a built-in web server.

Communication Gateway COM 610 acts as an embedded communication gatewaybetween substation automation protection and control devices and Network ControlCenters (NCC).

Station Computer COM 615 combines the features and functions of COM 605 and COM615.

All products in COM 600 Series use an embedded operating system and run in a dedicatedindustrial computer without moving parts.

The products are configured using a separate engineering PC that is connected via thelocal area network (LAN). For more information, refer to COM 600 User's Guide.

Gateway functionality

The gateway functionality provides a framework that enables the use of OPC server andclient components, such as OPC Client for IEC 60870-5-101 and OPC Server for LONLAG 1.4. This manual presents the principles that are common to the protocols availableat the moment as well as to those that will be applicable in the future. For protocol specificinformation, refer to the respective client and server user’s guides.

An overview of a typical system is shown in Figure 2.2-4.

system_overview.jpg

Figure 2.2-4 System overview

(1) Network Control Center (NCC)

(2) Engineering PC with Communication Engineering Tool (CET)

13


User's Guide

(3) COM 610/615 with embedded operation system, OPC client(s) for NCC connection(s),OPC server(s) for process connection

(4) Protection and control devices

HMI functionality

The features of HMI include a Single Line Diagram, Busbar coloring, lists of events andalarms, disturbance data upload, system supervision, control of breakers and switches,parameter settings, measurement display, and user management.

Features2.3.

Gateway functionality2.3.1.

The Gateway functionality provides a framework that enables the use of OPC server andclient components, such as OPC Client for IEC 60870-5-101 and OPC Server for LONLAG 1.4. This manual presents the principles that are common to the protocols availableat the moment as well as to those that will be applicable in the future. For protocol specificinformation, refer to the respective client and server user’s guides.

Figure 2.3.1-1 Conceptual view of COM 610 Gateway

14


User's Guide

Normally, there is one OPC client per NCC connection. If you want to create severalNCC connections with the same protocol, you have to use multiple instances.

COM 610/615 consists of OPC Data Access (DA) server and client components. OPCServers are used mainly for master/client protocol stacks to provide access to the datain the devices connected with the protocol. OPC Clients are used for slave/server protocolstacks to enable external systems to access data available in the OPC Servers.

GWComponents.jpg

Figure 2.3.1-2 Example of COM 610 Gateway components

Available protocols

Protocols that are supported by COM 610 Gateway are shown in the table below. Thenumber of supported protocols will increase as new protocols come to the market. Themaster protocols are used in process communication and the slave protocols are used inupper level communication. For more detailed information on the protocols refer touser’s guides listed in 1.8, Related documents.

Slave protocolsMaster protocols

IEC 60870-5-101LON-LAG

IEC 60870-5-104SPA

DNP 3.0 SerialIEC 60870-5-103

DNP 3.0 LAN/WANIEC 61850

SPA RouterModbus Serial (RTU)

15


User's Guide

HMI2.3.2.

HMI functions2.3.2.1.

The HMI enables the user to access the COM 600 computer via a web browser.

The HMI offers the following functions:• single line diagram• alarm and event lists• system supervision• user management• disturbance data upload• limited parameter settings• measurement display

sld_example.jpg

Figure 2.3.2.1-1 Example view of the COM 600 HMI

The HMI can be accessed:• locally via an optional local HMI screen• locally by connecting your laptop to COM 600 via LAN• remotely through the internet or over LAN/WAN

16


User's Guide

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 passwordbefore you can proceed using HMI. If you forget the new password, restore the factorysettings 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.

This chapter describes the structure of a typical OPC server component developed forthe gateway. The OPC server component consists of a Master/Client Protocol Stack,OPC DA/AE Server and Configuration SCL.

The protocol stack component implements the protocol functions, such as handshakingsignal handling, message coding/decoding, check sum calculations, polling logic, protocollevel timers and so on. The OPC server/protocol handler implements the functionalityfor publishing and updating data on the OPC interfaces and protocol conversion betweenthe 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 accordingto the IEC 61850 SCL specification. When the OPC server is started, the configurationinformation is read from the file.

ServerConcept_a.jpg

Figure 2.3.3-1 Conceptual view of OPC server

17


User's Guide

OPC client2.3.4.

This chapter describes the structure of a typical OPC client component developed forthe OPC Gateway. The OPC client software consists of a Slave/Server Protocol Stack,OPC DA Client, Configuration SCL, OPC Data Access Server and Alarm&Event servercomponents for diagnostic and control.

The protocol stack component implements the protocol functions, such as handshakingsignal handling, message coding/decoding, check sum calculations, polling logic, protocollevel timers and so on. The OPC client/protocol handler implements the functionalityfor data subscription from the OPC servers and protocol conversion between the OPCand 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. Theconfiguration information is exported to the SCL/XML configuration file according tothe IEC 61850 SCL specification. When the OPC client is started the configurationinformation is read from the file.

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 componentuses a common data model. The data model is based on common data classes and servicesspecified in the IEC 61850 standard. Each client and server component is a separateprogram. The components interact with each other only via OPC interfaces. This meansthat they can be developed and used independently as a part of the gateway as long asthey conform with the OPC DA and common data model specifications.

Protection and control products are connected to the gateway via OPC interfaces. AlthoughOPC provides means to access data on devices, it does not specify the semantics of the

18


User's Guide

data. This means that the same information is available in different formats dependingon which device and communication protocol is used. In addition, services, such asbreaker operation, vary among devices and protocols.

These differences complicate the reuse of gateway applications. To overcome thisproblem, all the applicable data and services are remodeled in OPC servers accordingto 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.

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 anOPC item in the OPC server. A data attribute can be, for instance, the state value of adouble point object (stVal), quality information (q), or timestamp (t). In the OPC serversome 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 doublepoint object are available as OPC items.

For different types of data, the IEC 61850 standard defines over 30 common data classesincluding a set of mandatory and optional attributes and services. For example, commondata 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 oncommon data classes. These groups are called logical nodes. Examples of logical nodesare controllable switch (CSWI) and distance protection (PDIS).

Logical nodes can be further grouped below logical devices (LD), forming logical groupswithin a physical device (IED), see Figure 2.3.5-2.

19


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 COM 610/615 gateway provides a common Station/Remote (S/R) switch function-ality for OPC servers and clients. The S/R switch is used to determine whether the objectsin a logical device of an IED can be controlled within the station or remotely via agateway.

A station can have one or more S/R switches. The switches are either physical switchesor software switches in a simulated IED of an OPC server. The S/R switches are modeledusing 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 configurationprocess. If a logical device has no linking information configured, the linking informationof the IED is used instead. At run-time, an OPC server publishes the logical device S/Rswitch linking information for the OPC clients of the COM 610/615 gateway. Each timean OPC client sends a command to a device, it first checks the S/R switch position todetermine whether the operation is allowed or not: the COM 610/615 gateway OPC clientis allowed to operate only if the S/R switch is in remote position.

A COM 610/615 gateway OPC client has the operation modes disabled and enabled forS/R switch handling. When the switch is in the enabled mode, the values for S/R switchposition failures are Allow controls if position unknown and Reject controls if positionunknown.

HMI is considered a local station HMI if it uses the local display of the COM 600 com-puter or if the ip address of the HMI client is in the range specified with a Station IPAddress Filter property in the Gateway object. Otherwise HMI is considered a remoteHMI. The state of the station/remote switch controls whether the operations are allowedfrom HMI or not.

The station/remote switch for the HMI is configured with the SLD editor by insertingthe Station Switch Indicator symbol to the substation SLD and specifying the data object

20


User's Guide

for the position information. If a real switch indication is not available, it is possible touse a simulated data from virtual IED. This can be done by creating an IED configurationin the communication structure and setting the simulation mode of the IED to true.

Watchdog timer2.3.7.

The COM 600 computer has a built in hardware watchdog function. The function canbe enabled with CET from the Gateway object properties. When enabled, the watchdogmonitors the COM 600 software. If the COM 600 software fails to send the keep-alivetriggering to the watchdog within a certain time, the watchdog will restart the COM 600computer.

Queuing of Process Data Updates2.3.8.

This section describes the common queue mechanism for OPC Clients (slave protocols)in COM 610/615. There might be additional queuing mechanisms on different levels ofthe protocol stacks, that are specific for the protocol, which are not described here.

Process data updates are mainly queued in the OPC Clients of the COM 610/615. EachOPC Client has its own queues independent from other clients, which prevents disturb-ances on one client connection from interfering with other connections. There are fourseparate queues for different type of data with configurable length.

• High Priority• command replies/confirms• internal protocol stack control commands• protocol stack database initialization commands

• State Indications• binary data and other state indications

• Measurements• analog data

• Interrogated• interrogation related data and commands

Queue logic

For high priority and interrogated queues the oldest message is skipped when the queuesfill up. Generally these queues should never fill up since they contain a limited numberof updates (proportional to the number of OPC items).

When the state indication queue is full, the new updates are always skipped until thereis free space in the queue.

When the measurement queue is full, an older update is always skipped when a newupdate is pushed on the queue.

21


User's Guide

The updates are skipped according to the following logic:• If an item has two or more updates, the oldest update is skipped• If no item has two or more updates, the oldest update in the queue is skipped.

For measurements, older updates for an item are also skipped when the queue reachesa configurable percent of the maximum capacity (but only if there is an item with multipleoutstanding updates to send).

Queue priorities

If a high priority queue contains an update, it is always sent first. After that, the interrog-ated queue is checked. If none of these queues has updates, the state indications andmeasurements are checked in round-robin fashion.

Queue capacities

The capacity (maximum size) of each queue is independently configured. If one queuefills up, capacity from another, possibly non-full queue is not used.

Hardware2.3.9.

Mechanical properties2.3.9.1.

Mechanical information:• Dimensions (without fastening brackets): 214 mm (W) x 122.5 mm (H) x 313 mm

(L)• Net weight 6.8 kg• Degree of protection IP 4x• EMC CE/FCC class B• Antivibration and antishock tests

Hardware Design:• Ruggedized mechanics:

• No moving parts - no fans, no hard disks• System:

• Intel® Pentium® M 1.6 GHz• 1 GB SDRAM System Memory• 2 GB Industrial SSD Compact Flash memory

• Watchdog timer• Interfaces:

• 3 x RS 232 serial ports DB9 male connector• 1 x RS 232/485 serial port DB9 male connector• 2 x 10/100Base-TX RJ-45 connector• 4 x USB 2.0 port

22


User's Guide

• Optional PCI extensions:• 1 x LON interface (Operating temperature 0°C...+70°C)• 4 x RS232/422/485 serial interfaces (Operating temperature 0°C...+65°C)• 2 x 10/100Base-TX RJ-45 connector (Operating temperature 0°C...+60°C)

• 1 x VGA display connector• 1 x Audio connector (adapter cable for 3.5 mm stereo plug included)

• Power supply units:• high voltage: 76-240 V dc

COM600_connectors.jpg

Figure 2.3.9.1-1 COM 600 interfaces

Environmental conditions2.3.9.2.

The environmental conditions of the COM 600 computer are:• Operation -25°C...+70°C• Storage -40°C...+70 °C• Humidity during operation: 5 - 95%@40°C, non-condensing

Setting up the COM 2 port for RS-232/RS-4852.3.9.3.

By default the COM 2 port is configured to RS-232 mode. The mode of the port (RS-232/RS-485) can be changed via the computer's BIOS setup.

COM 2 port in RS-232/RS-485 mode can only be used withModbus protocol. For more information on configurationsettings, see Modbus Master User's Guide.

23


User's Guide

To change the mode of the port:1. Connect a local keyboard and display to the COM 600 computer.2. Restart the computer and press the Del key during restart to access the BIOS setup.3. Select Integrated Peripherals from the main SETUP menu. Use the cursor keys for

moving and enter key for selection.4. Select SuperIO Device from the next menu.5. On the SuperIO Device configuration page, go to the COM2 Select parameter and

press ENTER. Now you can choose between RS-232 and RS-485.6. Press the F10 key to save the changes and exit the BIOS setup.

Pinout of COM 2 port when RS-485 mode is used:

DB9 connector:1. TX-/RX-2. N/A3. TX+/RX+4. N/A5. GND6. N/A7. N/A8. N/A9. N/A

24


User's Guide

Installation3.


This section describes the installation and uninstallation of the Communication Engin-eering Tool (CET) and modifying and setting up of the COM 600 computer. For moredetailed instructions on installation of the gateway components, refer to the 1.8, Relateddocuments.

Hardware requirements for CommunicationEngineering Tool

3.2.

Hardware requirements for CET:• Microsoft® Windows® XP• Microsoft® .NET Framework 2.0 (installed automatically during CET installation,

if it is not already on the PC)• Free hard disk space: minimum 500 MB, recommended 1GB

Installing Communication Engineering Tool3.3.

To install CET:1. Close all open programs and insert the Communication Engineering Tool installation

CD to the CD-ROM drive of your PC.2. The Installation program should start automatically. If this does not happen, open the

program by browsing to the CD drive, and starting COM_600.exe.3. Wait for the Wise Installation Wizard to extract the installation files to your PC.

Installation_extracting.png

Figure 3.3-1 Extracting installation files

4. The Communication Engineering Tool Installation program opens. Click Next.At any stage of the installation, you can return to the previous window by clickingBack or exit the Installation Wizard by clicking Cancel.

25


User's Guide

InstStarts.jpg

Figure 3.3-2 Communication Engineering Tool Installation program

5. Read the License Agreement, then check the option I accept the license agreementand click Next to continue the installation.If you check the option I do not accept the license agreement, the Next button isnot available and you cannot continue the installation.

26


User's Guide

InstLicens.jpg

Figure 3.3-3 License Agreement

6. Select the folder where you want to install CET.• To select the default folder shown at the bottom of the window, click Next.• To select another folder, click Browse, select the folder you want, and click Next.

27


User's Guide

InstFolder.jpg

Figure 3.3-4 Selecting installation folder

7. Select the desired installation type

InstSelect.jpg

Figure 3.3-5 Selecting Installation type

28


User's Guide

The Typical installation type is recommended for most installations. SelectingComplete will install all features of CET and selecting Custom allows you to choosethe features you want to install.

8. Click Next to begin the installation.

InstReady.jpg

Figure 3.3-6 Ready to install

You can follow the progress of the installation in a window that also shows thedirectory path where the files are copied. At this point, you can still cancel theinstallation by clicking Cancel.

9. A window opens showing that the Communication Engineering Tool has been suc-cessfully installed. Close the window and finish the installation by clicking Finish.

29


User's Guide

InstOK.jpg

Figure 3.3-7 Installation complete

10. After clicking Finish the wizard automatically installs the Microsoft SQL Server ifit is not already installed on your PC.

InstSQLServ.jpg

Figure 3.3-8 Installing the MS SQL Server

11. Restart your computer.

You can now start CET by selecting Start > Programs > Communication EngineeringTool > Communication Engineering Tool in the Windows task bar.

Mounting of COM 600 computer3.4.

The COM 600 computer is designed for mounting at a control panel.

To mount the COM 600 computer to the wallmount kit:1. See Figure 3.4-1 for mounting instructions.

30


User's Guide

2. After the brackets have been installed, fasten four screws on each bracket.3. After fastening the two brackets on the bottom lid of COM 600 computer, the wall-

mount kit installation is finished.

COM600_mounting.jpg

Figure 3.4-1 Mounting diagram of the COM 600 computer

For mechancal properties of the COM 600 computer, see 2.3.9.1, Mechanical properties.

Setting up the COM 600 computer3.5.

Accessing the COM 600 computer3.5.1.

Local and Remote LAN ports

The COM 600 computer has by default two LAN ports, a local (LAN 2) and a remoteport (LAN 1). The local port is used for local connection in a secure network within thesubstation, for example for engineering and process communication with the IEDs. Thelocal port has no firewall configured and it allows complete access to the COM 600computer. The remote port is used for communication outside the substation. It has a

31


User's Guide

firewall pre-configured to allow communication only with web clients and remotecommunication using protocols for example IEC 870-5-104 and DNP 3.0 LAN/WAN.

Table 3.5.1-1 shows the default IP addresses for the LAN ports.

Table 3.5.1-1 Default IP addresses for the LAN portsIP AddressMaskGatewayLAN Port

Local Area Con-nection (Remote)

10.0.0.11255.255.255.0Not definedLAN 1

Local Area Con-nection (Local)

192.168.2.11255.255.255.0Not definedLAN 2

Some tasks, for example changing the IP addresses or adding users, require access directlyto the COM 600 computer either locally or via the remote desktop software.

Accessing the COM 600 computer:• Locally by connecting a USB keyboard, a USB mouse and a display to the computer.• Remotely with the remote desktop program via LAN. By default the security settings

allow the remote desktop connection only via the interface reserved for the local use.

Regional settings

The default regional setting is English (United States).

Remote desktop

You can use the COM 600 computer as a local console from an engineering computerwith remote desktop.

32


User's Guide

RemoteDesk.jpg

Figure 3.5.1-1 Remote desktop

The COM 600 computer can be restarted remotely by running restart.bat command fromthe root of C drive. The COM 600 computer can also be shut down by running shut-down.bat command.

If you enter the command shutdown.bat, the Gateway com-puter shuts down and you cannot restart it remotely.

Built-in user accounts

Two user accounts are predefined in the COM 600 computer:• Username: Administrator• Password: pwd2004

This account is disabled by default for security reasons. Youcan enable it temporarily during the configuration phase toenable access to the COM 600 computer if the COM600password is lost. It is recommended that you disable theAdministrator account later when the COM 600 computer isconnected to the actual network.

• Username: COM600• Password: aEc2006rs

33


User's Guide

This is the main account of the COM 600 computer. It is used for configuration purposes.Processes of the COM 600 computer are run under this account.

Connecting configuration computer with CET to COM 600 computer

1. Configure the network settings of the configuration computer and the COM 600computer to allow them to communicate with each other. This is done by configuringthe IP addresses of the computers into the same subnetwork. Configure (or disable)the possible firewall in the configuration computer to pass DCOM.

2. Connect either a crossover LAN cable between the computers or connect both com-puters to a network switch. Use the LAN port used for local use in COM 600 computer.

3. Create a COM600 user account with administrator rights to the configuration computer.The password must be the same as in the COM 600 computer.

4. Log in to the configuration computer as a COM600 user and launch CET.5. Create a project and add the Gateway object to the communication structure.6. Type the IP address of the COM 600 computer LAN port used for configuration to

the IP address property of the Gateway object.7. Right-click the Gateway object and select Management. Verify that the communica-

tion with the COM 600 computer is working properly. The first time you open themanagement tool, you are required to change the COM600 user password. ClickChange password to change the password both in the COM 600 computer and inthe configuration computer.You have to close CET and log in to windows to activate the new password.The COM600 user password must always be changed as described above to ensurethat the password is changed correctly for each component in the COM 600 computer.

If you lose the password you will not be able to access theCOM 600 computer anymore either locally or remotely.

If you want to run CET using a different user account than COM600 in the configurationcomputer, you must do the following. If you use the COM600 user, you can skip thephases below.

To run CET using a different user account than COM 600 in the configuration computer:1. Add the COM600 user to the configuration computer as described above.2. Add the new configuration user to COM 600 computer with administrator rights and

with the same password as in the configuration computer.3. Configure the DCOM permissions for the new user in the COM 600 computer as

described below.

DCOM settings are used to define permissions to use the COM 600 computer.

To start the DCOM configuration:1. Select Start > Settings > Control Panel > Administrator Tools > Component

Services or run the command dcomcnfg. The Component Services dialog opens.2. Browse to My Computer and right-click the My Computer icon. Select Properties

from the shortcut menu.

34


User's Guide

3. Select Default COM Security tab from the My Computer Properties dialog.4. Created user account must be added to both access permissions and launch permissions.

To add permission:1. Click Edit Default. The permission dialog opens.2. Select the user you want to give a permission to use the COM 600 computer.3. Click Add and then OK.4. Mark the check boxes for local and remote access, launch and activation.

After changing the settings it is recommended to restart both computers to activate thechanges.

Uninstalling Communication Engineering Tool3.6.

To uninstall CET:1. Open the Add or Remove Programs dialog by selecting Start > Settings > Control

Panel > Add or Remove Programs in the Windows task bar.2. Select Communication Engineering Tool and click Remove.

Note that this uninstallation only removes the CommunicationEngineerign Tool so that you can install a new version andupdate the software. It does not remove the Microsoft SQLServer and .Net Framework. Removing these programs mayinfect the functionality of any other ABB applications installedon your PC.

UnInst.jpg

Figure 3.6-1 Add or Remove Programs dialog

35


User's Guide

Turning off COM 600 computer3.7.

If a local display, keyboard and mouse are connected to the COM 600 computer:1. Press CTRL+ALT+DEL and choose Shutdown from the dialog.2. Wait until the It is now safe to turn off your computer message appears on the

display.3. Press and hold the front panel power button for a few seconds until the SYS led on

the front panel turns off.

If the remote desktop session is active:1. Run the shutdown.bat located in the C:\ of the COM 600 computer.2. Wait for about 30 seconds. Then press and hold the front panel power button for a

few seconds until the SYS led on the front panel turns off.

If no desktop is available, press and hold the front panel power button for a few secondsuntil the SYS led on the front panel turns off.

To turn on the COM 600 computer, press the power button briefly.

36


User's Guide

Configuration4.


This section describes the configuration tasks common to all OPC servers, and gives anoverview of the configuration tasks related to OPC clients.

All the possible configuration scenarios are not included inthis manual. Refer to the corresponding user’s guides listedin 1.8, Related documents for more detailed instructions. Youmust have configuration rights to be able to perform the tasksdescribed in this section.

The configuration tasks described in this section apply onlyto COM 610.

First you need to start Communication Engineering Tool (CET) to open and name aproject.

CET.jpg

Figure 4.1-1 Opening a project in Communication Engineering Tool (CET)

37


User's Guide

NewProject.jpg

Figure 4.1-2 Naming a new project

A project can have one Gateway configuration.

Configuration and maintenance4.2.

Communication Engineering Tool is used to configure and maintain the Gateway.Communication networks are described in the Communication structure of the ProjectExplorer window. The structure is built using OPC server/client, communication channel/subnetwork and device objects. These objects have communication properties that canbe accessed via the Object Properties window. The properties define for example thecommunication port, bit rate, timing parameters, unit addresses and so on.

The substation structure of CET is used to configure the HMI functions of the COM 600products. The substation structure presents the functional view of the substation. Itincludes substation, voltage level, bay, busbar and conducting equipment objects.

The Single line diagram is a graphical presentation of the process objects in the substation.The Single line diagram can be edited on different levels. The bay layout can be con-figured by opening the SLD Editor from a bay object. When the SLD Editor is openedfrom a voltage level object, it is possible to assign the positions of the bays within avoltage level. The position of the voltage levels in the complete substation single linediagram is done by opening the SLD editor from the substation object.

Substation objects are linked to communication structure objects by using the DataConnection tool. For example the circuit breaker object in the substation structure is

38


User's Guide

linked to the CSWI logical node in the communication structure. The link between thestructures is also used on the event list, to present the events using the names accordingthe substation structure.

Process data accessible on the devices is modeled according to the IEC 61850 standard.In the communication structure this is seen as logical devices (LD), logical nodes (LN)and data objects (DO). It is possible to insert an empty device into the structure and thenmanually add and configure LD, LN and DO objects. It is also possible to use pre-con-figured object types of the devices, which have the objects defined and configured toadd efficiency. The device configuration can also be imported from an IED SCLdescription. Data objects include configuration properties, that contain cross-referencinginformation between protocol and the OPC/IEC 61850.

Process data is connected to a Gateway client using a Cross-Reference function availablein the client IED object. Data objects that are transferred to the client are dragged fromthe servers on the structure to the function tool. Cross-referencing information is filledin the function window. The Cross-Reference function supports import and export withMicrosoft Excel.

When the structure is complete and all the objects have been set up properly the config-uration is downloaded to the Gateway using the Gateway Management function availableon the Gateway object.

Backup and restore4.3.

To Backup MSDE database:1. Select File > Open/Manage Project.2. Select the project you want to back up.3. Select Export Project on the left.4. The File dialog opens. Select the location where to export the database.

To restore your backup:1. Select File > Open/Manage Project.2. Select Projects on my computer.3. Select Import Project on the left.4. The File dialog opens. Choose the exported database you want to import.

SCL Export4.4.

It is possible to export the configuration files of the COM 600 OPC Servers and Clientsin SCL format using the SCL Export function in the Gateway object. This function canbe used to transfer the configuration information to other systems and tools.

To export configuration files in SCL format:1. Right-click the Gateway object in the Communication tree and select SCL Export.

39


User's Guide

2. The Gateway - SCL Export window opens. Select whether you want to export allconfigurations or a certain OPC Server or Client configuration.

3. Click Export and select the location where you want to save the SCL file. Click OK.

Configuration process4.5.

Overview of configuration process4.5.1.

Before you can start using COM 600, you need to build and configure the communicationand substation structure of your project in Communication Engineering Tool CET.

Figure 4.5.1-1 shows an example view of CET including an object tree in the Commu-nication structure on the left and property window displaying the object properties onthe right.

IECCETMain.jpg

Figure 4.5.1-1 Example view of Communication Engineering Tool

The configuration can be divided into three tasks:1. Building the object tree and configuring the object properties for OPC servers (process

communication)2. Building the substation object tree and configuring the object properties for HMI

functions

40


User's Guide

3. Exporting the configuration data.

First, you need to build an object tree by adding objects to the object tree. For moreinformation refer to the respective user’s guide listed in 1.8, Related documents. Con-nectivity packages for certain protection and control products usually contain preconfig-urations and tools to facilitate the building of the object tree.

Building object structures4.5.2.

OPC servers4.5.2.1.

Start the configuration work from the server objects. Before an OPC client can be takeninto use, an OPC server has to be configured for the process communication.

The object tree is built in the communication tab of CET. There are several possibleways to build an object tree. One of them is to build the object tree by adding objects inlogical order starting from the OPC server object. You can either use basic or pre-definedobjects. Using basic objects means that you have to configure the objects manually. Ifobjects are pre-defined, they are preliminary configured and all the necessary childobjects are automatically added.

Add the objects in the following order:1. OPC server object2. Channel/Subnetwork object depending on protocol3. Device object4. Logical device object(s)5. Logical node object(s)6. Data objects.

If you want to connect events or scales to data objects ordevice connection status event classes to device objects at thispoint, make sure that you have already created and configuredthe event and scale objects.

For more detailed information on adding objects to the object tree, refer to the appropriateprotocol manual (see 1.8, Related documents).

Substation structure for HMI4.5.2.2.

Configuring the substation is the main task in configuring HMI functionality. If connectiv-ity packages or IED SCL description files with substation structure information are used,most of the substation structure can be built automatically when the IEDs are added tothe communication structure. If no substation structure information is available thestructure must be built manually.

41


User's Guide

Before you can create a substation structure, you have to createa communication structure with OPC Server and communica-tion channel objects, IEDs, Logical Devices, Logical Nodesand Data objects.

To create the substation structure manually:1. Create Gateway, Substation and Voltage level objects to the substation structure.2. Add bays and busbars, and design their layout using the SLD Editor. Connect your

substation structure objects to communication structure (logical nodes) using the dataconnection function.

If the configurations of the bays are similar, you can copy thebay object and the data it contains. This way you do not haveto add each bay separately to the substation structure.

3. Design your voltage level layout by connecting busbars and bays and relocating themwith the SLD Editor. Open the SLD Editor by right-clicking the voltage level object.

4. Design your substation layout by connecting possible transformer windings betweenvoltage levels. Relocate voltage levels with the SLD Editor. Open the SLD Editor byright-clicking the substation.

5. Fine tune SLD settings, for example fonts and colors.

For more detailed information, refer to COM 605 COM 615 HMI Configuration manual.

OPC clients4.5.2.3.

The object tree is built in the communication structure. Note that before an OPC clientcan be taken into use, an OPC server has to be configured for the process communication.

42


User's Guide

ClientComStruc.jpg

Figure 4.5.2.3-1 Example of OPC client communication structure

The OPC client object is added to the same hierarchy level as the OPC server, see Fig-ure 4.5.2.3-1. Below the OPC client object, you can add only channel and device objects.The data objects are linked using the Cross-References function from the servers to theclient and further to the NCC. The Cross-References function can be also used to configurethe data object’s parameters.

Add the objects in the following order:1. OPC client object2. Channel/Subnetwork object depending on protocol3. Device object.

Configuring objects4.5.3.

General about configuring objects4.5.3.1.

Each configurable object, such as server and channel/subnetwork objects, can be con-figured with object properties. The source data is configured with a data object OPCserver configuration. This defines the addresses and type of data in the device providingthe data. Process data is connected to the COM 610/615 gateway client by adding the

43


User's Guide

OPC client properties to the data objects below an OPC Server. Note that the name ofthe data object should be the same as specified in the client object’s Data Object Propertiesand it specifies to which client instance that property belongs. This property, togetherwith the station address on the data object, connects the data object to a specific OPCclient. The protocol used defines which properties are added to a particular object. Referto the respective client and server user’s guides listed in 1.8, Related documents.

SCL Import function4.5.3.2.

You can import a complete communication structure under an OPC Server with newconfigurations from an existing file. This is done using the SCL import function. Thefile extentions for the import files can be .icd, .cid, .scd or .xml. Right-click the IEC61850 OPC Server and select SCL Import from the shortcut menu.

To import a new configuration file:1. Click Choose File.2. Browse for a new configuration file from the dialog that opens.3. Select the file and click Open.4. Select the device to import from the drop-down menu. You can preview the configur-

ation on the right.5. Click Import.

The new preconfigured objects will appear in the object tree. If the configuration file isvery large the import may take time.

44


User's Guide

SCLImport.jpg

Figure 4.5.3.2-1 Example of IEC 61850 OPC Server SCL Import

Cross-References function4.5.3.3.

Data objects are added differently for OPC clients than for the upper level objects. Dragand drop the data objects you need from an OPC server to the slave. Note that you alsocan select an upper level (server, channel, and so on) object and drag and drop it intothe Cross-Reference window. As a result, all the data objects within the selected objectappear in the Cross-References window and can be connected to the slave OPC client.

45


User's Guide

CrossRefFunc.jpg

Figure 4.5.3.3-1 Cross-References window

In the Cross-References window, you can use a filter file to leave out some of the dataobjects to be connected to the Slave Device. Select the filter file to be used from thedrop-down menu under Active Filter. If there are no filter files listed in the drop-downmenu, you can create your own filter file by clicking Modify Filter File.

You can also modify an existing filter file to meet your needs. The Cross-Referencestable allows you to view the data objects by type. Use the tabs in the upper part of thetable to do this. Under the General tab, you can see all the data objects and their propertyvalues. Here you can sort the data objects by clicking the column heading (Object Name,Description, 61850-Type and so on).

There is a possibility to export the cross-references table to Microsoft Excel and to importthe table from Microsoft Excel. Clicking Apply connects the data objects to the SlaveDevice. After that you can change the data object values either in the Object Propertieswindow or in the Cross-References window. For more detailed instructions on configuringthe data object properties in the Cross-References window, refer to the slave protocoluser’s guides listed in 1.8, Related documents.

Configuration of Station/Remote switch4.5.4.

Each IED and logical device in the OPC Server has a configuration parameter definingthe OPC node path for the S/R switch that is used for that IED/logical device. If a logicaldevice does not have an S/R switch path configured, the path defined in the IED is usedinstead. At run-time, the S/R path of a logical device can be read from the OPC Server;

46


User's Guide

the LD S/R switch path is located in the LD node. The OPC server that has the S/R switchposition information must have at least one signal mapped to the OPC client using thisinformation.

The S/R switch OPC path points to an OPC node modeled according to one of the sup-ported IEC 61850 data classes. The stVal OPC item of the S/R object presents the stateof the S/R switch, 1 = station and 0 = remote. If the stVal item has the vartype VT_BOOL,VARIANT_TRUE is interpreted as 1 and VARIANT_FALSE as 0.

The same S/R switch OPC path can be shared by several IEDs/LDs, or each IED/LDcan have an own S/R switch OPC path. The OPC node pointed by the path can be locatedin an OPC server providing the S/R information from a physical switch or from a simu-lated software switch.

The web HMI is considered to be local or remote based on the IP-address of the webclient. The gateway object has a configuration property which defines the addresses thatwill be handled as local. It can be either a single IP address or using wild cards a rangeof IP addresses.

Event definitions4.5.5.

Creating event definitions4.5.5.1.

To create event classes:1. Right-click the Events group in the Communication Engineering Tool (CET), see

Figure 4.5.5.1-1.2. Select New -> Event classes.3. Select the event class you want to add.4. The new event class appears in the Process Definitions below the selected event group.

Enter a unique name for the event class by right-clicking it and selecting Rename.The new event class can be configured and connected to a data object.

47


User's Guide

creating_events.jpg

Figure 4.5.5.1-1 An example of creating event classes

Configuring event definitions4.5.5.2.

You can configure event definitions in Communication Engineering Tool (CET). Eventdefinitions specify the type of events that are created for HMI event and alarm lists. Youcan specify whether an event appears only on the event list, on both event and alarmlists, or whether it is displayed at all. You can also add event texts for the events andspecify whether alarms have to be acknowledged by the user.

Event definitions are linked to data objects by configuring the event properties availablefor data objects. When importing IED configurations from connectivity packages or IEDSCL description files, event definitions are linked to data objects by default. For exampleswitch position data object CSWIx.Pos is linked by default to switch position eventdefinition. The default linking rules are specified in a DOParamsDefaults.xml file locatedin the \Program files\ABB\COM600\bin\Tools\SCLImport in the computer where CETis installed.

To configure event definitions:1. Select the event you want to configure in the object tree.2. The object properties appear now in the Object Properties window, see Figure 4.5.5.2-

1.3. You can assign the event with parameter values.

Table 4.5.6.3-1 lists the available scales.

48


User's Guide

ScaleDefObjProp.jpg

Figure 4.5.5.2-1 An example of object properties of events

Using scales4.5.6.

General about using scales4.5.6.1.

You may need to use scaling if a measurement value provided by the device is not assuch suitable for the applications, and you need to change the provided value to another.

With a scale you can convert one value to another by using a scaling algorithm. OPCservers support two types of scales: Stepwise Linear and Look-up Table. The StepwiseLinear scale multiplies the value to be converted with a scale factor and adds an offsetvalue to the result, and the Look-up Table scale uses a look-up table to find the requiredvalue.

Before you can connect a scale to a data object, you need toadd and configure the scale in the Communication EngineeringTool (CET). It is advisable to add and configure the scalesbefore adding and configuring any other objects.

49


User's Guide

Creating scales4.5.6.2.

To create scales:1. Right-click Scale Definitions in the Communication Engineering Tool (CET), see

Figure 4.5.6.2-1.2. Select New -> Scales.3. Select the scale you need to add (a Look-up Table or Stepwise Linear).4. The new scale appears in the Scale Definitions. Enter a unique name for the scale by

right-clicking it and selecting Rename. It can be configured and connected to a dataobject.

creating_scales.jpg

Figure 4.5.6.2-1 Creating scales

Configuring scales4.5.6.3.

You can configure scales in Communication Engineering Tool (CET).

To configure scales:1. Select the scale you want to configure in the object tree.2. The object properties appear now in the Object Properties window, see Figure 4.5.5.2-

1.3. You can assign the scale with parameter values.

50


User's Guide

ScaleDefObjProp.jpg

Figure 4.5.6.3-1 Object properties of the scales

Table 4.5.6.3-1 ScalesDescriptionValue or value range/ DefaultProperty/Para-

meter

Basic

Look-up Table andStepwise Linear

Value to be scaled-01 In Value

Scaled value-01 Out Value











51


User's Guide

DescriptionValue or value range/ DefaultProperty/Para-meter









52


User's Guide

Operation5.

Activating Gateway with new configurations5.1.

After the configurable objects in the object tree have been created, the configurationsmust be transferred to the COM 600 computer:

• To copy the configurations of all servers and clients to the COM 600 computer, clickUpdate configuration.

• To transfer only the changed configurations and to restart only the changed server orclient with new configurations, click Update & reload configuration.

• To force a complete configuration reset of the COM 600, mark the reset check boxbefore updating the configuration. All instances of OPC servers and clients will berecreated in COM 600. This normally has to be done only if the same COM 600computer is configured using several engineering computers with different projects,for example during training or testing.

53


User's Guide

Index

Aactivating Gateway ............................................................................................. 53

Bbackup ............................................................................................................... 39building

object tree ...................................................................................................... 41

CCET

installing ......................................................................................................... 25uninstalling ..................................................................................................... 35

COM 600 computeraccessing ....................................................................................................... 31environmental conditions ................................................................................. 23mounting ........................................................................................................ 30remote desktop ............................................................................................... 32user accounts ................................................................................................. 33

Communication Engineering Toolstarting ........................................................................................................... 37

configuration ...................................................................................................... 40Gateway ........................................................................................................ 38general ............................................................................................... 37, 40, 43server objects ................................................................................................. 41Station/Remote switch .................................................................................... 46

creatingsubstation structure ........................................................................................ 41

cross-references ................................................................................................. 45

DDCOM ............................................................................................................... 34

Eevent definitions

configuring ..................................................................................................... 48creating .......................................................................................................... 47

exportingconfiguration files ............................................................................................ 39project ............................................................................................................ 39

55


User's Guide

Ffunctionality

Gateway ................................................................................................... 13–14HMI .......................................................................................................... 14, 16

GGateway

functionality .................................................................................................... 14Gateway Management ........................................................................................ 53

HHMI

accessing ....................................................................................................... 16functionality .................................................................................................... 16

IIEC 61850 data modelling ................................................................................... 18importing

configuration file ............................................................................................. 44project ............................................................................................................ 39

Mmaintenance

Gateway ........................................................................................................ 38

Oobject tree .......................................................................................................... 40

building .......................................................................................................... 41OPC client

adding ........................................................................................................... 42structure ......................................................................................................... 18

OPC serverstructure ......................................................................................................... 17

Pprocess data ...................................................................................................... 39project

exporting ........................................................................................................ 39

56


User's Guide

Qqueuing

capacities ....................................................................................................... 22logic ............................................................................................................... 21priorities ......................................................................................................... 22process data updates ...................................................................................... 21

Rregional settings ................................................................................................. 32restore ............................................................................................................... 39

Sscales

configuring ..................................................................................................... 50creating .......................................................................................................... 50using .............................................................................................................. 49

SCL export ......................................................................................................... 39SCL import ......................................................................................................... 44Station/Remote switch ........................................................................................ 20structure

OPC client ...................................................................................................... 18OPC server .................................................................................................... 17

substation structurecreating .......................................................................................................... 41

supported protocols ............................................................................................ 15

57


User's Guide

1MR

S756

125

B/22

.1.2

007

ABB OyDistribution AutomationP.O. Box 699FI-65101 VAASAFINLANDTel. +358 10 22 11Fax. +358 10 224 1094www.abb.com/substationautomation

user's guide · • the start menu name always refers to the start menu on the windows...

Documents