Category: ABB

The LHMI presents pages in two categories: the Operator

pages and the Engineer pages. The Operator pages include the

ones which are typically required as a part of an operator’s

normal activities, such as a single-line diagram, controls,

measurements, events, alarms, and so on. The Engineer’s

pages include specifically designed pages supporting relay

parametrization, troubleshooting, testing and commissioning

activities.

The Operator pages can be used as such or customized

according to the project’s requirements using Graphical Display

Editor (GDE) within the PCM600 software tool. The Engineer

pages are fixed and cannot be customized.

The Operator pages can be scrolled either by tapping the Home

button or by swiping the actual pages. The Engineer pages are

accessible by touching the upper horizontal section of the

screen.

The LHMI is an accessory for the relay which is fully operational

even without the LHMI. The relay communication card has a

dedicated port where the LHMI is connected using an RJ-45

connector and a CAT6 S/FTP cable. The LHMI can be

connected to the relay also via station communication network

if a longer distance is required between the relay and the LHMI.

Additionally, the LHMI contains one Ethernet service port with

an RJ-45 connector and one USB port. The service port can be

used for the PCM600 connection or for Web HMI connection.

Data transfer to a USB memory is enabled via the USB port. By

default the USB port is disabled and has to be taken into use

with a specific parameter.

Local HMI

The LHMI uses rugged 7-inch high resolution color screen with

capacitive touch sensing technology. The user interface has

been carefully designed to offer the best situational awareness

to the user. Visualization of the primary process measurements,

events, alarms and switching objects’ statuses makes the local

interaction with the relay extremely easy and self-evident. The

LHMI provides a control point for the selected primary devices

via pop-up operator dialogs.

Additionally, the LHMI supports the engineer during the relay’s

testing, commissioning and troubleshooting activities. The

information, traditionally accessible through different paths

within the menu structure, is provided in collectively grouped

and visualized format.

The Home button at the bottom of the LHMI indicates the

relay’s status at a glance. In normal situations, the Home button

shows a steady green light. Any other situation that requires the

operator’s attention is indicated with a flashing light, a red light

or a combination of these.

Description

REX640 is a powerful all-in-one protection and control relay for

use in advanced power distribution and generation applications

with unmatched flexibility available during the complete life

cycle of the device – from ordering of the device, through

testing and commissioning to upgrading the functionality of the

modular software and hardware as application requirements change.

The modular design of both hardware and software elements

facilitates the coverage of any comprehensive protection

application requirement that may arise during the complete life

cycle of the relay and substation.

REX640 makes modification and upgrading easy and pushes

the limits of what can be achieved with a single device.

Application packages

REX640 offers comprehensive base functionality. However, it is

possible to further adapt the product to meet special installation

needs by including any number of the available optional

application packages into a single REX640 relay. For the

selected application packages, the functionality can be

extended by including the related add-on package. The

REX640 connectivity package guides the engineer in optimizing

the application configuration and its performance.

Local HMI

The LHMI uses rugged 7-inch high resolution color screen with

capacitive touch sensing technology. The user interface has

been carefully designed to offer the best situational awareness

to the user. Visualization of the primary process measurements,

events, alarms and switching objects’ statuses makes the local

interaction with the relay extremely easy and self-evident. The

LHMI provides a control point for the selected primary devices

via pop-up operator dialogs.

• The default 615 series IED SCL export from PCM600 contains five default

client definitions, “Client1”…”Client5”, which are used by all the RCBs.

MicroSCADA and COM600 clients can use the client definitions directly. If

other clients need to be added to the IET600 project, import the ICD file

describing the client data model to the project and attach the file to the same

IEC 61850 subnetwork in the Communication tab.

• Create the bus connections for the IEC 61850 clients.

Importing a new IEC 61850 client

Adding a new IEC 61850 client to an IET600 project is a two-step operation. The

client must be first created using the Create New IED function, after which the

Update IED function can be used to import the related ICD (or CID) file.

1. To create an IED, click the IEDs tab in the navigation pane.

2. Click the root node in the IED tree.

3.Right-click the node and click Create New IED on the shortcut menu.

Creating a GOOSE data set

Define the sending data set used by the GOOSE control block. With the 615 series

IEDs, the sending GOOSE data set can have at maximum 20 data attributes to

minimize the message handling load in receiver and sending IEDs.

All data sets must be configured under the logical node LLN0 and must be

provided with names unique within the IED. In 615 series IEDs there are a

maximum of four GOOSE control blocks allowed, which effectively limits the

relay to four data sets for GOOSE as there is a one-to-one correspondence between

the GOOSE control blocks and GOOSE data sets. Typically it is sufficient to

define a single data set and control block for an application.

When a 615 series IED is configured to send measurements, the analog, integer or

counter type of data should be placed on its own dataset. The triggering of analog

type of data sending is controlled by deadband handling, zero-point clamping and

limit supervision.

The horizontal communication configuration consists of the IEDs’ GOOSE control

block, data set and GOOSE input configuration. The result of the configuration

work is a system configuration file which can be downloaded to the IEDs. The

used files in the workflow are IEC 61850 standard format SCL files.

Configuring horizontal communication

See detailed descriptions of the steps in corresponding chapters.

1. Add devices to a PCM600 project.

2. Export the SCD file.

3. Import the SCD file to IET600.

4. Engineer the GOOSE connections between the devices

4.1. Define the published GOOSE data and control blocks.

4.2. Define the subscribing IEDs for the GOOSE data.

5. Export the SCD file back to PCM600.

6. In PCM600. engineer the IED applications with GOOSE inputs.

GOOSE is used in substation automation for fast horizontal communication

between the IEDs. GOOSE can be used for direct data exchange, for example, of

interlocking and blocking information between IEDs. According to the IEC

61850-8-1 standard, GOOSE uses a publisher/subscriber profile in which

information is shared from one IED to one or several IEDs by using Ethernet

multicast messages. A message is an image of a sent IEC 61850 data set that is

defined in the configuration.

IET600 is used to configure the vertical and horizontal communication properties

of the 615 series IEDs.

A 615 series IED can send any type of status or measurand data in the GOOSE

messages from its IEC 61850 data model. The status data response time, that is, the

time it takes for the application to handle a received GOOSE message and to send

the concerned data back to the network, is with the 615 series IEDs below 3 ms.

The response time fulfils the tightest Type 1A, Class P2/3 requirements of the

standard.

A PC with PCM600 can be connected to any 615 series IED within a station by

using the Ethernet connection. The connection can also be used for service and

maintenance purposes. In addition, the connection is used to handle disturbance

records from the protection IEDs using the IEC 61850 file transfer.

The modern-day IEDs are designed using the concept of the IEC 61850 standard.

This is primarily in regards to how functions within the IED are modelled and how

the IED is represented in the substation. See the IEC 61850 parameter list for the

list of logical nodes available in the IED and observe how they follow the structure

and rules as defined in part 7 of the standard.

The engineering of the used communication protocols is a separate task and an

addition to the engineering of protection and control functions.

PCM600 can be used for different purposes throughout the IED life cycle. A set of

special tools is available for different applications.

Protection and Control IED Manager PCM600 offers all the necessary functionality

to work throughout all stages of the IED life cycle.

• Planning

• Engineering

• Commissioning

• Operation and disturbance handling

• Functional analysis

With the individual tool components, you can perform different tasks and functions

and control the whole substation. PCM600 can operate with many different

topologies, depending on the customer needs.

PCM600 is used to conduct complete engineering and configuration activities

needed for the bay level IEDs.

Connectivity Packages are separate software packages that provide type and

version information to PCM600. Further Connectivity Packages assist the tool with

communications.

PCM600 uses IEC 61850 over Ethernet to communicate with bay IEDs. This

communication allows PCM600 to configure and monitor the IEDs. In addition to

IEC 61850 the IEDs have optional communications protocols and hardware to

connect to station engineering tools. PCM600 provides the ability to export the

configuration of the IEDs or entire substation in a standard file format which

allows for station engineering.

The standard supports free allocation of functions to devices. With efficient

communication facilities, the functions can be located anywhere in the system, that

is, an interlocking function can reside in the IED or on the station level.

Additionally, the standard is open for different system implementations, that is,

different integration levels and allocation of functions to different devices is

supported.

The standard also defines an XML description language for substation automation

systems. The language facilitates efficient integration of devices into systems in an

automated fashion. Additionally the standard supports a comprehensive and

consistent system definition and engineering, which makes not only the devices,

but also their tools and systems interoperable (standard part 6).

The standard uses Ethernet and TCP/IP for communication. Since Ethernet and TCP/

IP are widely accepted and used, the application of these technologies provide a

broad range of features from mainstream communication (standard parts 8-1. 9-2).

However, IEC 61850 is also open for possible new communication concepts in the

future.

The international IEC 61850 standard defines a framework for substation

communications networks and systems. The standard consists of several parts

ranging from the requirements on substation automation systems to the details of a

communication protocol.

One major difference between the other communication protocols applied in

substation automation and IEC 61850 is that the latter is not only a communication

protocol, but a whole framework for specifying, engineering and operating

substation automation systems. The communication part covers the connection

between the IEDs and the substation clients, for example, SCADA and gateways.

The IEC 61850 standard specifies an expandable data model and services for

substation automation (standard parts 7-x). The standard does not specify any

protection or control functions, but specifies how the functions expose their

information to a communication network.