ethernet adapter installation and commissioning manual...10 spa-zc 400 1mrs755347 ethernet adapter...

SPA-ZC 400Ethernet Adapter

Installation and Commissioning Manual

Ethernet AdapterInstallation and Commissioning Manual

SPA-ZC 4001MRS755347Issued: 06.10.2004Version: A/06.10.2004

1. About this manual .....................................................................71.1. Copyrights .....................................................................................71.2. Trademarks ...................................................................................71.3. General .........................................................................................71.4. Use of symbols ..............................................................................81.5. Document conventions ..................................................................91.6. Terminology ................................................................................101.7. Abbreviations ..............................................................................111.8. Related documents .....................................................................111.9. Document revisions .....................................................................121.10.Safety information .......................................................................12

2. Introduction .............................................................................132.1. SPA-ZC 400 Product Overview ...................................................132.2. Introduction to IEC 61850 standard ............................................142.3. SPA-ZC 400-BB and SPA-ZC 400-MM Product Overview .........142.4. SPA-ZC 400 Features .................................................................152.5. Ordering information ...................................................................16

2.5.1. SPA-ZC 400 product package .........................................16

3. Installation ...............................................................................193.1. Mechanical Installation ................................................................193.2. Communication Engineering Tool (CET) ....................................19

3.2.1. System requirements .......................................................193.2.2. Installing CET ...................................................................193.2.3. Uninstalling CET ..............................................................27

3.3. Installing Connectivity Packages .................................................273.3.1. Uninstalling Connectivity Packages .................................33

4. Engineering .............................................................................354.1. About this section ........................................................................354.2. Overview of engineering .............................................................354.3. Creating project ...........................................................................364.4. Configuring SPA-ZC 400 by using Connectivity Packages .........364.5. Building object tree ......................................................................37

4.5.1. Adding IEC 61850 Device object .....................................384.5.2. Adding Logical Device objects .........................................384.5.3. Importing IEC 61850 data object model of IED ................40

4.6. Configuring SPA-ZC 400 using imported CID file .......................414.7. Configuring SPA-ZC 400 using IEC 61850 data model

components .................................................................................424.8. Configuring communication parameters .....................................44

©Copyright 2004 ABB Oy, Distribution Automation, Vaasa, FINLAND 3

1MRS755347 Ethernet AdapterInstallation and Commissioning Manual

SPA-ZC 400

4.8.1. SPA Communication parameters .................................... 454.9. Using Dataset Editor ................................................................... 474.10.Configuring report control blocks ............................................... 474.11.Downloading configuration and exporting CID file ..................... 504.12.Commissioning SPA-ZC 400 ..................................................... 51

4.12.1.Checking SPA communication ........................................ 514.12.2.Obtaining diagnostic data through ftp .............................. 52

5. Technical data ........................................................................ 535.1. Interfaces .................................................................................... 535.2. Test and conditions ..................................................................... 55

6. Maintenance and service ....................................................... 576.1. General about service ................................................................. 57

6.1.1. LED indicators ................................................................. 576.2. SPA-ZC 400 communication settings ......................................... 57

7. Technical reference ................................................................ 597.1. About this section ....................................................................... 597.2. ACSI conformance statement .................................................... 60

7.2.1. ASCI basic conformance statement ............................... 607.2.2. ACSI models conformance statement ............................. 607.2.3. ACSI service conformance statement ............................. 62

7.3. Model conformance statement ................................................... 667.3.1. Common data attribute classes ....................................... 66

7.3.1.1. Quality ................................................................ 667.3.1.2. Analogue value .................................................. 677.3.1.3. Configuration of analogue value ........................ 677.3.1.4. Range configuration ........................................... 677.3.1.5. Step position with transient indication ................ 68

7.3.2. Originator ......................................................................... 687.3.2.1. Unit definition ..................................................... 697.3.2.2. Vector definition ................................................. 69

7.3.3. Common data classes ..................................................... 697.3.3.1. Single point status (SPS) ................................... 697.3.3.2. Double point status (DPS) ................................. 707.3.3.3. Integer status (INS) ............................................ 717.3.3.4. Protection activation information (ACT) ............. 727.3.3.5. Directional protection activation information

(ACD) ................................................................. 737.3.3.6. Security violation counting (SEC) ...................... 747.3.3.7. Binary counter reading (BCR) ............................ 747.3.3.8. Measured value (MV) ........................................ 75

4

1MRS755347 SPA-ZC 400 Ethernet AdapterInstallation and Commissioning Manual

7.3.3.9. Complex measured value (CMV) .......................777.3.3.10.Sampled value (SAV) .........................................787.3.3.11.WYE ...................................................................797.3.3.12.Delta (DEL) ........................................................807.3.3.13.Sequence (SEQ) ................................................817.3.3.14.Harmonic Value (HMV) ......................................817.3.3.15.Harmonic value for WYE (HWYE) .....................837.3.3.16.Harmonic value for DEL (HDEL) ........................847.3.3.17.Controllable single point (SPC) ..........................857.3.3.18.Controllable double point (DPC) ........................877.3.3.19.Controllable integer status (INC) ........................887.3.3.20.Binary controlled step position information

(BSC) .................................................................907.3.3.21.Integer controlled step position information

(ISC) ...................................................................917.3.3.22.Controllable analogue set point information

(APC) .................................................................937.3.3.23.Single point setting (SPG) ..................................947.3.3.24.Integer status setting (ING) ................................947.3.3.25.Analogue setting (ASG) .....................................957.3.3.26.Setting curve (CURVE) ......................................967.3.3.27.Device name plate (DPL) ...................................97

7.3.4. Logical node name plate (LPL) ........................................977.3.4.1. Curve shape description (CSD) .........................98

7.4. SCL conformance statement .......................................................997.5. SCL control block ......................................................................1007.6. Protocol implementation conformance statement .....................101

7.6.1. Profile conformance .......................................................1017.6.1.1. MMS conformance ...........................................1017.6.1.2. GOOSE services ..............................................102

5


1. About this manual

1.1. CopyrightsThe 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 must ABB Oy be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor must ABB 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 permission 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 © 2004 ABB Oy All rights reserved.

1.2. TrademarksRegistrations and trademarks used in this document include:

Windows: Registered trademark of Microsoft Corporation.

1.3. GeneralThis manual provides thorough information on the SPA-ZC 400 Ethernet adapter used for connecting REF 541/3/5, REM 543/5 and RET 541/3/5 Intelligent Electronic Devices (IED) to IEC 61850 Station bus and the central concepts related to it. You will find information on SPA-ZC 400 and its components, an introduction to engineering tasks and a description of the basic operations.

Information in this manual is intended for application engineers, who install and configure SPA-ZC 400. As a prerequisite, you should have basic knowledge of IEC 61850 client and server architectures in general.

In this manual RE_54_ contains only REF 541/3/5, REM 543/5 and RET 541/3/5 products.

7


SPA-ZC 400

This manual is divided into following sections:

Chapter 2. Introduction

This section gives an overview of SPA-ZC 400, its components and functionality and the engineering tool, and introduces the IEC 61850 data modeling principles.

Chapter 3. Installation

This section provides you with general information on installing the SPA-ZC 400 components.

Chapter 4. Engineering

In this section you will find an overview of engineering tasks of SPA-ZC 400.

Chapter 5. Technical data

This section provides you the SPA-ZC 400 technical data.

Chapter 6. Maintenance and service

In this section you will find information about self-diagnostics and troubleshooting of SPA-ZC 400.

Chapter 7. Technical reference

This section defines the SPA-ZC 400 compliance to IEC 61850 in terms of service, modeling and engineering interfaces.

1.4. Use of symbolsThis publication includes caution and information where appropriate to point out safety related or other important information. The corresponding symbols should be interpreted as follows:

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.

Information icon alerts the reader to relevant facts and conditions.

8


1.5. Document conventionsThe 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 dialog, 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 CTRL 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, Enter 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: Menu Name > Menu Item > Cascaded Menu Item. For example: select File > Open > New Project.

The Start menu name always refers to the Start menu on the Windows Task Bar.

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

9


SPA-ZC 400

1.6. TerminologyThe following is a list of terms associated with SPA-ZC 400 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.

Term Description

Connectivity Package Software and description XML files to provide device specific information about certain relays or device, used to ease and simplify the engineering

SPA Data communication protocol developed by ABB

ST Connector type for glass fibre cable

Snap-in Connector type for plastic fibre cable

MT-RJ Connector type for glass fibre cable

Data Object (DO) Part of a logical node object representing specific information, for example 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 structures.

Data Set (DS) The data set is the content basis for reporting and logging. The data set contains references to the data and data attribute values.

Intelligent Electronic Device (IED)

This includes devices containing advanced logics such as meters, relays, and trip units. In this article IED means a physical IEC 61850 device that behaves as its own communication node in the IEC 61850 protocol.

Logical Device (LD) Representation of a group of functions. Each function is defined as a logical node. A physical device has one or several LDs.

Logical Node (LN) The smallest part of a function that exchanges data. A LN is an object defined by its data and methods.

Report Control Block (RCB) The report control block controls the reporting process for event data as they occur. The reporting process continues as long as the communication is available.

sAddr Short Address InformationThe sAddr attribute allows the allocation of a short address to DO attributes. Short addresses can be used within the communication to be more efficient either in the communication, or in the handling of messages at client or server. Furthermore, they can be used as IED internal identification for the attribute.

Substation Configuration description Language (SCL)

XML-based description language for configurations of electrical substation IEDs. Defined in the IEC 61850 standard.

10


1.7. Abbreviations

1.8. Related documents

Abbreviation Description

CET Communication Engineering Tool

CID Configured IED Description(a type of SCL file)

DO Data Object

DS Data Set

ICD IED Configuration Description template(a type of SCL file)

IEC International Electrotechnical Commission

IED Intelligent Electronic Device(usually a protection and control relay device)

IP Internet Protocol

LAN Local Area Network

LD Logical Device

LED Light-emitting diode

LN Logical Node

LON Local Operating Network

MMS Manufacturing Message Specification

RCB Report Control Block

SCD System Configuration Description(a type of SCL file)

SCL Substation Configuration description Language

SNTP Simple Network Time Protocol

Name of the manual Document IDSPA-ZC 400 configuration CD 1MR151048CAP 505 Users Guide 1MRS752292-MUMSPA-ZF Optical glass fibres,multimode graded index type

1MRS755371

Plastic-core fibre optic cables, Features and instructions for mounting

1MRS752089

IEC 61850 Standard(parts -6, -7-2, -7-3, -7-4, -8-1)

11


SPA-ZC 400

1.9. Document revisions

1.10. Safety information

Version Date HistoryA 06.10.2004 Document created

Dangerous voltages can occur on the connectors, even though the auxiliary voltage has been disconnected.National and local electrical safety regulations must always be followed.The device contains components which are sensitive to electrostatic discharge. Unnecessary touching of electronic components must therefore be avoided.The frame of the device has to be carefully earthed.Only a competent electrician is allowed to carry out the electrical installation.Non-observance can result in death, personal injury or substantial property damage.Breaking the sealing tape on the upper handle of the device will result in loss of warranty and proper operation will no longer be guaranteed.Do not touch the inside of the case. The adapter case internals may contain high voltage potential and touching these may cause personal injury.

�

12


2. Introduction

2.1. SPA-ZC 400 Product OverviewSPA-ZC 400 is used to connect one RE_54_ device to the IEC 61850-8-1 Station bus. The IEC 61850 standard defines the IEC 61850 communication and engineering specifications. In addition to the IEC 61850-8 communication, SPA-ZC 400-BB and SPA-ZC 400-MM versions provide the simultaneous dual port communication for fibre-optic SPA and LON®. SPA-ZC 400 offers also possibility to access the device with the SPA protocol over TCP/IP using the same Ethernet link.

A040001

Fig. 2.1.-1 Conceptual picture of a typical system setup

The mechanical and electrical connection of Ethernet adapter to a RE_54_ interface is described in Chapter 3. Installation. The Ethernet adapter programming is described in Chapter 4. Engineering.

As a prerequisite, you should understand the communication properties of Intelligent Electronic Devices (IED) that is to be connected to Ethernet adapter. This information is available in the manual for the protection relay in question. It is also necessary to have basic understanding of the IEC 61850 system, in which IED is going to be connected to.

�

�

��

�

��

�

�

�

�

��

��

��

��

�� !"��#��$��#

%"��"��"��

�� "��$��

��&'�(�)!(��"��

��*��#��!+&))��)�

�� "�,"��"��-��&"��"

��-��.

13


SPA-ZC 400

2.2. Introduction to IEC 61850 standardThe IEC 61850 standard defines the communication between IEDs in substations.

IEDs support the following functions: - Protection and control- Integration of innovative sensor and switch technologies- Metering, supervisory control and data acquisition (SCADA)- Remote monitoring and fault diagnostics- Automated dispatch and control- Asset management- Condition monitoring and diagnostics

IEC 61850 provides:- Standardized information models for all kind of protection relays, controllers,

circuit-breakers, transformers, etc.- Information exchange methods to access the information models data: report

sequences-of-events, log historical data, control devices, sampled value distribution, fast peer-to-peer process data exchange, etc.

- A unified system configuration language (XML based) and device on-line self-description.

Compared to other communication standards for substation automation, the IEC 61850 standard defines data modeling and communication services for this specific domain. Data modeling is mapped to a communication protocol, Manufacturing Message Specification (MMS, ISO 9506 protocol), which uses TCP/IP and Ethernet. In addition to the communication specifications, engineering information exchange is defined in SCL, which is a XML based language. For more information on the IEC 61850 standard documentation, see Section 1.8. Related documents.

2.3. SPA-ZC 400-BB and SPA-ZC 400-MM Product OverviewSPA-ZC 400-BB and SPA-ZC 400-MM versions have the same IEC 61850 functionality as described in Section 2.1. SPA-ZC 400 Product Overview. In addition, these versions include an optional fibre optic interface.

This optional interface provides connection between the RE_ 54_ device and the fibre-optic SPA, LON® and IEC 60870-5-103 buses. The bus connection module converts incoming optical signals from the SPA, LON® and IEC 60870-5-103 bus to electrical RS-485 signals for the RE_54_ devices and vice versa. It contains a service pin for LON® nodes.

The optional interface can be used in the Loop and Star type bus topologies. Also the modules line idle state is selectable. The light can be turn on or off. The jumpers select the bus topology (Loop or Star) depending on whether the light is turned on/off.

14


In the Loop topology, the interface receives the message from the fibre-optic interface and passes it both to the fibre-optic transmitter and to the RS-485 interface. In the Star topology, the interface receives the message from the fibre-optic receiver and passes it only to the RS-485 interface. If the message is received from the RS-485 interface, it is passed to the fibre-optic transmitter in both bus topologies.

The SPA bus communication uses Loop and light off modes, when the module jumpers are in the Loop and light off positions. The LON® bus communication uses Star and light off modes, when the module jumpers are in the Star and light off positions. The IEC 60870-5-103 bus communication uses Star and light on/off modes, when the module jumpers are in the Star and light on/off positions.

In the LON® bus communication the optional interface supports collision detection. The Service Pin is connected via the RS-485 interface to the devices Neuron® chip, which is connected to the interface.

2.4. SPA-ZC 400 Features IEC 61850 connectivity for RE_54_ Internal power supply Easy-to-use configuration tool for the IEC 61850 data mapping Simultaneous dual port communication (SPA-ZC 400-MM and SPA-ZC 400-BB

versions) for LON® and SPA Support of SPA communication over TCP/IP

All relay data can be routed through SPA-ZC 400. It is intended to route the process data (status, measurements and commands) through the IEC 61850-8-1 bus and the rest of the available data can be routed through SPA over TCP/IP.

Table 2.3.-1 Settings of the jumper

Topology Light on/off Protocol

Star Light off LON or IEC 60870-5-103

Star Light on IEC 60870-5-103

Loop Light off SPA

Loop Light on Not supported

It is not possible to use IEC 60870-5-103 and IEC 61850 simultaneously.

15


SPA-ZC 400

Module parts

Fig. 2.4.-1 Parts of SPA-ZC 400

2.5. Ordering information

2.5.1. SPA-ZC 400 product package

SPA-ZC 400 SPA-ZC 400 module SPA-ZC 400 Installation and Commissioning Manual

SPA-ZC 400-MM SPA-ZC 400 module with simultaneous dual port communication

ST connectors for glass fibre SPA-ZC 400 Installation and Commissioning Manual

�

�

�

1. 100BaseFX connector 2. LON/ SPA/ IEC 60870-5-103

bus connector (optional)3. LON/ SPA/ IEC 60870-5-103

Rx LED4. LON/ LAN service pin5. LAN and diagnostics LEDs

A040138

16


SPA-ZC 400-BB SPA-ZC 400 module with simultaneous dual port communication

Snap-in connectors for plastic fibre SPA-ZC 400 Installation and Commissioning Manual

SPA-ZC 400 Configuration CD Engineering tool, Communication Engineering Tool (CET) for SPA-ZC 40x Connectivity Packages for RE_54_

Order at least one SPA-ZC 400 configuration CD with your delivery to get the Communication Engineering Tool and the Connectivity Packages. SPA-ZC 400 packages do not include the configuration CD by default.

17


3. Installation

This chapter describes the installation of the SPA-ZC 400 module and the Communication Engineering Tool (CET). For additional information, such as technical data, maintenance and service, refer to Chapter 5. Technical data and Chapter 6. Maintenance and service.

3.1. Mechanical InstallationConnect the SPA-ZC 400 module to RE_54_ and screw SPA-ZC 400 to the 9-pin type D-connectors. Connect the fibre optic LAN cable to the LAN connector of SPA-ZC 400. The other end of the cable is connected to the IEC 61850-8 Station bus via Ethernet switch.

3.2. Communication Engineering Tool (CET)

3.2.1. System requirementsCommunication Engineering Tool (CET) runs on Windows 2000, Windows XP and Windows Server 2003 Operating Systems. A PC capable of running one of these operating systems and applications is usually sufficient also for CET. For more information, refer to the Section 1.8. Related documents. The detailed system requirements can be seen below.

20 MB free hard disk space, if Microsoft .NET Framework 1.1, which is required for running CET, has been installed already.

100 MB free hard disk space, includes installation of Microsoft .NET Framework 1.1. It is installed automatically, if it is not found.

3.2.2. Installing CET1. Close all the open programs and insert the CET installation CD to the CD-ROM

drive of your PC.2. The Installation program starts automatically. If this is not the case, open the

program by browsing it to the CD drive and start setup.exe.3. First, the installation wizard extracts the installation files to your local computer,

see Fig. 3.2.2.-1.

A040005

Fig. 3.2.2.-1 Extracting installation files

19


SPA-ZC 400

4. Then the CET Installation program opens. In this dialog click Next, see Fig. 3.2.2.-2.

With the Back button you can return to the previous dialog, and with the Cancel button exit the installation wizard. This applies to all the dialogs in the installation wizard.

A040006

Fig. 3.2.2.-2 CET Installation Program

20


5. Read the License Agreement, then check the option I accept the license agreement and click Next to continue the installation, see Fig. 3.2.2.-3.

If you check the option I do not accept the license agreement, the Next button is not available and you cannot continue the installation.

A040007

Fig. 3.2.2.-3 License Agreement dialog

21


SPA-ZC 400

6. Select the folder in which the application is to be installed, see Fig. 3.2.2.-4. To select the default folder shown at the bottom of the dialog, click Next. To select another folder, click Browse, choose the folder you want and click

Next.

A040008

Fig. 3.2.2.-4 Selecting installation folder

22


7. Both manuals are installed by default in your local hard drive, see Fig. 3.2.2.-5.By clicking Next you can continue the installation.

To install a manual, click the respective manual and select Will be installed on local hard drive.

To install the documentation feature, click the respective manual and select Entire feature will be installed on local hard drive.

To install the manual when required, click the respective manual and select Feature will be installed when required.

Not to install the manual, click the respective manual and select Entire feature will be unavailable.

A040004

Fig. 3.2.2.-5 Installing manuals

23


SPA-ZC 400

8. On this stage installation can begin, see Fig. 3.2.2.-6. Click Next to begin the installation.

A040009

Fig. 3.2.2.-6 Ready to install

24


9. You can follow the progress of the installation in a dialog that also shows the directory path where the files are copied, see Fig. 3.2.2.-7. At this point, you can still cancel the installation by clicking Cancel.

A040010

Fig. 3.2.2.-7 Installation

25


SPA-ZC 400

10.Then a dialog opens to show that the gateway has been successfully installed, see Fig. 3.2.2.-8. Close the dialog and finish the installation by clicking Finish.

A040011

Fig. 3.2.2.-8 Installation complete

11.When clicking Finish the wizard also installs the Microsoft SQL Server automatically, if it is not installed on the hardware already.

12.Now, you can start CET by selecting Start > Programs > Communication Engineering Tool for SPA-ZC 40x > Communication Engineering Tool in the Windows task bar.

26


3.2.3. Uninstalling CET1. Open the Add or Remove Programs dialog by selecting Start > Settings >

Control Panel > Add or Remove Programs in the Windows task bar.2. Select CET and click Remove, see Fig. 3.2.3.-1.

A040012

Fig. 3.2.3.-1 Add or Remove Programs dialog

3.3. Installing Connectivity Packages1. Close all the open programs and insert the SPA-ZC 400 configuration CD to the

CD-ROM drive of your PC.2. Double-click the Connectivity Package installation program and select the

relevant IED (.msi) to start the installation.

3. First, the installation wizard extracts the installation files to your local computer.

Note that the uninstallation only removes CET, in order for you to install a new version and to update the software. It does not remove the Microsoft SQL Server and .NET Framework. Removing these programs may infect the functionality of the other ABB applications.

Detailed instructions for upgrading the software will be provided when the upgrade is available.

It is recommended to install the Connectivity Package after installing the Communication Engineering Tool (CET), see Section 3.2.2. Installing CET. If this is not the case, re-install the Connectivity Package after installing the CET.

27


SPA-ZC 400

4. Then the Connectivity Package Installation program opens. In this dialog click Next, see Fig. 3.3.-1.

With the Back button you can return to the previous dialog, and with the Cancel button exit the installation wizard. This applies to all the dialogs in the installation wizard.

A040016

Fig. 3.3.-1 Connectivity Package for REF 541/3/5 installation program

28


5. Read the License Agreement, then check the option I accept the license agreement and click Next to continue the installation, see Fig. 3.3.-2.

If you check the option I do not accept the license agreement, the Next button is not available and you cannot continue the installation.

A040017

Fig. 3.3.-2 License Agreement

29


SPA-ZC 400

6. Select the folder in which the application is to be installed, see Fig. 3.3.-3. To select the default folder shown at the bottom of the dialog, click Next. To select another folder, click Browse, choose the folder you want and click

Next.

A040018

Fig. 3.3.-3 Selecting installation folder

30


7. On this stage installation can begin, see Fig. 3.3.-4. Click Next to begin the installation.

A040019

Fig. 3.3.-4 Ready to install

31


SPA-ZC 400

8. You can follow the progress of the installation in a dialog, which also shows the directory path where the files are copied to, see Fig. 3.3.-5. At this point, you can still cancel the installation by clicking Cancel.

A040020

Fig. 3.3.-5 Installation

32


9. Then a dialog opens to show that the Connectivity Package has been successfully installed, see Fig. 3.3.-6. Close the dialog and finish the installation by clicking Finish.

A040021

Fig. 3.3.-6 Installation complete

3.3.1. Uninstalling Connectivity Packages1. Open the Add or Remove Programs dialog by selecting Start > Settings >

Control Panel > Add or Remove Programs in the Windows task bar.2. Select the relevant Connectivity Package and click Remove, see Fig. 3.3.1.-1.

A040015

Fig. 3.3.1.-1 Add or Remove Programs dialog

33


4. Engineering

4.1. About this sectionThis section guides you in the engineering tasks required before using SPA-ZC 400. For more information on the IEC 61850 data modeling, refer to the IEC 61850 standards listed in Section 1.8. Related documents.

4.2. Overview of engineering The engineering and maintenance of SPA-ZC 400 is done by using the Communication Engineering Tool (CET). The devices communication structure is described in the Project Explorer dialog. The structure is built by using device objects. These objects have communication properties that can be accessed via the Object Properties dialog. These properties define for example the IP addresses, unit addresses, descriptions etc.

The process data accessible on devices is modeled according to the IEC 61850 standard. In the communication structure this is seen as logical devices (LD), logical nodes (LN), data objects (DO) and their data attributes (DA). The data model is imported from the pre-configured object types of devices, which have the objects defined and configured. These object types are defined in the standardized IED Connectivity Packages. The data model can also be created manually by using CET functions.

When the structure is complete and all the objects have been set up properly the configuration is downloaded via FTP to SPA-ZC 400 by using the CID (Configured IED Description) Export function.

The engineering work can be divided into four separate tasks:

1. Building an object tree according to the IEC 61850 data model by importing the Connectivity Package.

2. Configuring object properties, for example adding mapping to the SPA references in the IED (Intelligent Electronic Device).

3. Configuring communication addresses.4. Exporting the configuration data to SPA-ZC 400 and to the IEC 61850 system

configuration tool.

Note that all the possible engineering scenarios are not included in this manual. You must have engineering rights to be able to perform the tasks described in this section.

35


SPA-ZC 400

4.3. Creating projectYou need to start the SPA-ZC 400 Communication Engineering Tool (CET) to open and name a project, see Fig. 4.3.-1 and Fig. 4.3.-2.

A040014

Fig. 4.3.-1 Creating a new CET project

A040013

Fig. 4.3.-2 Opening a CET project

4.4. Configuring SPA-ZC 400 by using Connectivity PackagesFirst, you need to install the Connectivity Packages from the SPA-ZC 400 configuration CD, see Section 3.3. Installing Connectivity Packages. The RE_54_ Connectivity Packages contain needed data and tools to facilitate the building of an object tree. It is strongly recommended to use Connectivity Packages to add engineering efficiency.

It is recommended to install the Connectivity Package after installing the Communication Engineering Tool (CET), see Section 3.2.2. Installing CET. If this is not the case, re-install the Connectivity Packages after installing the CET, see Section 3.3. Installing Connectivity Packages.

36


4.5. Building object treeAfter installing the Connectivity Package you need to build and configure an object tree in the SPA-ZC 400 Communication Engineering Tool (CET) to define the Communication structure.

The Fig. 4.5.-1 shows an example of how the object tree may look like when it has been built. In the example tree you can see the SPA-ZC 400 object and its child objects as devices and data objects. Indentation is used to indicate the parent-child relationship between the objects.

A040137

Fig. 4.5.-1 Example view of the SPA-ZC 40x Communication Engineering Tool

You have several possible ways to add objects to the object tree in the Communication structure:

You can use the right mouse button (right-click) to select the object, which you want to add a child object.

You can copy the object. You can select the object using a drag-and-drop operation

37


SPA-ZC 400

Add the objects in the following order:

1. IEC 61850 Device object (SPA-ZC 40x)2. Logical Device objects3. Logical Node objects4. Data objects

4.5.1. Adding IEC 61850 Device objectTo start building the object tree, add an IEC 61850 Device object in the Communication structure by selecting the project name, that is Protocol Test in this case. Then right-click to select Protocol Test and select New > IEC 61850 > SPA-ZC 40x, see Fig. 4.5.1.-1. Project can contain several IEC 61850 Device objects, for example all substation feeder configurations and exported communication must be done separately for every device.

A040023

Fig. 4.5.1.-1 Adding an IEC 61850 Device object

4.5.2. Adding Logical Device objects1. Right-click to select an IEC 61850 Device object (SPA-ZC 40x) and select

New > Communication > Logical Device. This generates the mandatory logical device LD0, logical node LLN0 and its data structure for SPA-ZC 400. Logical device LD0 describes SPA-ZC 400 and includes the data objects for diagnostics and description. All data sets and report control blocks (RCB) will be collected to LLN0.

38


2. Add a new Logical Device object (REF 541/3/5), see Fig. 4.5.2.-1.This is possible only after you have installed connectivity packages to your computer. The IEDs data model behind SPA-ZC 400 is described in the logical device LD1.

A040024

Fig. 4.5.2.-1 Adding Logical Device objects

3. The logical device object is now shown as a sub-object to the IEC 61850 Device object, see Fig. 4.5.2.-2.

A040025

Fig. 4.5.2.-2 Logical node is shown as sub-object

You should have at least one Logical Device object as a child object to each IEC 61850 Device object.

You can have at maximun seven (7) Logical Device objects under one Device object (LDO and six (6) IED logical nodes).

39


SPA-ZC 400

When the actual IEC 61850 data model is created the logical device name has two parts:

Device Object name Logical Device name

for example SPAZC40xLD0.

4.5.3. Importing IEC 61850 data object model of IED1. Right-click to select a Logical Device object (for example REF 541/3/5).2. Import the project created with CAP 505, the Relay Product Engineering Tools

software. Communication Engineering Tool (CET) converts the project files with the help of the Connectivity Packages to a IEC 61850 data object model.

CET builds the IEDs IEC 61850 data model from the selected Connectivity Package to the Project Explorer dialog under the selected logical device.

The tool imports default data sets and report control blocks (RCB) to logical device LD0, see Fig. 4.5.3.-1. Data sets include a set of selected data attributes from IEDs IEC 61850 data model. These data sets are used in the IEC 61850-8-1 event reporting model. If data attributes are selected to the data set and the same data set is used in report control block (RCB), the data set generates a spontaneous event which will be sent to the IEC 61850 client. If the data set is not defined in the RCB, IEC 61850-8-1 reads the data separately. You can modify data sets with Dataset Editor, see Section 4.9. Using Dataset Editor.

The imported file, which is in the specified directory, is a compressed archive file with the file extension .AR.

40


A040026

Fig. 4.5.3.-1 Project Explorer dialog in the Communication Engineering Tool window

4.6. Configuring SPA-ZC 400 using imported CID fileIf you have to configure several SPA-ZC 400 with the similar IEC 61850 data object model, it is possible to import a previously generated CID file and change the communication addresses, typically by changing the IP address.

Add the project and the logical device LD0 like in Section 4.4. Configuring SPA-ZC 400 by using Connectivity Packages. Add a logical device to the SPA-ZC 40x Device object by right-clicking to select SPA-ZC 40x > New > Communication > Logical Device.You have to select the CID Import function by choosing a new empty logical node and then right-click to select the CID Import function.In the CID Import dialog you can select the right CID file from the workstation directory and import it to a previously created logical node. LD0 contains the data sets and reporting control blocks. Other logical devices describe the data model of a connected IED.

41


SPA-ZC 400

4.7. Configuring SPA-ZC 400 using IEC 61850 data model componentsYou can configure the IED model from the beginning. You have to be familiar with the IED, SPA model and how the IED model can be converted to the IEC 61850 model. If this configuration method is used, it is recommended that you familiarize yourself with Connectivity Packages as an example. Contact ABB if you have unresolved problems.

You can start building the IEC 61850 data model by creating an empty logical device, see Section 4.5.2. Adding Logical Device objects. The IEC 61850 standard defines a mandatory logical node LLN0 for every device and for its objects. You can add a logical node (LN) with the LN wizard tool, see Fig. 4.7.-1. You can open a logical node by right-clicking the respective logical device. You have to choose the logical node type and add a unique instance number for the logical node type. A prefix is an additional naming parameter for a logical node.

A040131

Fig. 4.7.-1 LN wizard

When the logical node is ready, you have to define data objects (DO) to it. You can add data objects with DO Wizard, see Fig. 4.7.-2. You can open the logical node by right-clicking the logical device. You have to choose the data object type and give a unique name within the selected logical node. DO Wizard has a set of pre-defined data objects with hard-coded data attributes. For more information on data objects, refer to Section 7.3. Model conformance statement.

42


A040132

Fig. 4.7.-2 DO Wizard

To get the data from the SPA model to the IEC 61850 model, you have to give SPA point data for selected data object in DOI Editor.

To open Data Object Instance (DOI) Editor, first you have to select the data object. Then right-click to select DOI Editor, see Fig. 4.7.-3. The Object Properties dialog shows different SPA point data properties that you can edit. SPA point data is written to the sAddr field in the CID file for the selected data object. SPA-ZC 400 uses this field to poll data and events from IED.

A040133

Fig. 4.7.-3 Data Object Instance Editor

43


SPA-ZC 400

4.8. Configuring communication parametersSPA-ZC 400 communication parameters are located in the Device Properties. SPA-ZC 400 uses static IP addresses, which have to be defined in the planned network structure, see Fig. 4.8.-1.

IP Address

IP address identifies SPA-ZC 400 in Local Area Network (LAN). All communication via SPA-ZC 400 uses this address. The default value is 192.0.2.10 and it has to be changed to a unique address according to the planned network structure.

Default Gateway

This IP address defines the gateways address, which forwards IP traffic between the local subnet and outside world. The default value is 192.0.2.1 and it has to be changed according to the planned network structure.

Subnet Mask

This address defines which addresses have access to the default gateway.

SNTP Servers

SPA-ZC 400 uses SNTP for its own realtime clock. Time is used for synchronizing IED with SPA time synchronization and for analog event time stamping. One SNTP Server has to exist in the accessible network, otherwise SPA-ZC 400 event time stamping is not working properly. The secondary SNTP server is used, if the primary SNTP server for some reason drops from the network.

Time Zone Correction

Due to the SNTP time synchronization, a time offset must be added to the SPA time synchronization message depending on the time zone. It affects the IED HMI event list and analog event time stamping. The value is minutes between -720 and 720 and it is comparable to Greenwich Mean Time (GMT).

OSI addresses are read-only and they are always the same. The IEC 61850-8-1 client uses these addresses to access SPA-ZC 400 over MMS.

44


A040022

Fig. 4.8.-1 Communication Parameters

4.8.1. SPA Communication parametersSPA-ZC 400 needs also IED SPA address to access the SPA data. Every logical device has SPA Communication Parameters Object properties expect LD0, which describes the SPA-ZC 400. The SPA Address object property has to be the same as the configured SPA unit number in IED.

SPA-ZC 400 uses default bit rate 9600 bits/s. Other possible values are 1200, 2400, 4800, 9600 and 19200 bits/s. Used value has to be same as the configured value in IED.

SPA-ZC 400 has three different modes of the IED time synchronization. The mode is selected from the logical device object describing the IED, for example LD1.

SPA-ZC 400 has to know the SPA Password to write the data to IED. Password (SPA parameter 0V160) is needed only for controllable integer status (INC). The SPA Password has to be same as defined in IED MMI.

45


SPA-ZC 400

Enabled

This is the default operation mode. When the operation is selected, you can synchronize SPA-ZC 400 with SNTP as it is defined in the IEC 61850-8-1 standard and SPA-ZC 400 is also synchronizing IED over SPA.

Disabled

In this mode, you can only synchronize SPA-ZC 400 with SNTP and IED has a different source of time synchronization.

Read from device if supported

When this operation mode is selected, the time for SPA-ZC 400 is read from IED over SPA. SNTP is not in use.

.

A040135

Fig. 4.8.1.-1 SPA Communication Parameters

46


4.9. Using Dataset EditorDataset groups selected data, so that client can access to it easily with a single read operation. Dataset is also the basic part of event reporting; data is linked to spontaneous event sending only via report control blocks data set definition. Client reads other data separately. Datasets definitions locate always under the logical device LD0 and logical node LLN0. Dataset Editor modifies selected data set.

Open Dataset Editor by selecting the data set and right-click to open Dataset Editor. Dataset has a set of data attributes: logical device instance name, optional prefix, logical node instance name, logical node class, data object name and functional constraint. Functional constraint divides data attributes to groups, which have the same functional constraint under the same data object. For example functional constraint ST (status information) groups stVal, q and t data attributes together, and then you do not have to add data attributes one by one to data set. Data attributes are collected to the data set in groups, and functional constraint defines the data attributes. This is MMS protocols naming feature, which is the base of naming and protocol definition in the IEC 61850 standard.

You can drag the data objects from data structure to data set entry. Delete data set entry by choosing Edit > Delete function or by selecting line and right-click to select Delete.

A040028

Fig. 4.9.-1 Dataset Editor

4.10. Configuring report control blocksReport control block (RCB) controls the spontaneous event reporting and client can modify report sending behaviour by setting RCB attributes. RCB attributes have suitable default values for following ABB products: COM 610 and MicroSCADA Pro IEC 61850-8-1 Client. RCBs locate always under the logical device LD0 and logical node LLN0.

47


SPA-ZC 400

Following RCBs default type is defined for data set: Buffered reporting

IEC 61850-8-1 buffers events also during the communication break.

Buffer Time

Default value for buffered reporting is 100 milliseconds (ms). With this value RCB waits 100 ms for other events after the first change before sending the report.

Integrity Period

Default value for Integrity Period is 0. If this attribute has value > 0 ms, SPA-ZC 400 sends a report with all data listed in linked data set with this period. By default this feature is not enabled because it generates unnecessary load to server and network.

Report ID

By default this attribute is empty and SPA-ZC 400 uses it for RCB MMS address.

Option Field defines what information is sent with report

By default SPA-ZC 400 adds buffer over-flow information, report entryID, sequence number and allows segmentation. Other fields are RCB configuration version, data reference in MMS address format, name of the used data set and report sending time.

Max property defines how many clients are using this RCB the number of needed RCB instances. If you define two clients for buffered reporting, then Max has to be two. SPA-ZC 400 creates two instances of RCB name, for example. rcbStatNrml01 and rcbStatNrml02. For unbuffered reporting Max has to be same as number of defined clients or higher. This is defined in the IEC 61850 standard.

Trigger Options

SPA-ZC 400 uses Data Change and Quality Change triggers by default, for example changes in value and quality generates information reports. Data Update and Period triggers are not supported.

48


A040134

Fig. 4.10.-1 Report Control Block

Buffered reporting needs mandatory Report Client definitions. Report Client definitions links certain RCB to certain client. Client can import the CID file to check what RCB instance it has to use. If Max property is defined to two, configuration must have two clients with buffered reporting. In the list first defined client uses first RCB instance (rcb name ...01) and second RCB uses second instance (rcb name ...02 ). It is not mandatory to define clients in unbuffered reporting, but it is recommended for clarity. Client IED Name has to match with the client name in Substation Configuration description Language (SCL).

Every modification in RCB increases the rcb Configuration Revision property by one. This integer value is also an exported CID file and the IEC 61850-8-1 client can check between the received revision and file configuration revision.

49


SPA-ZC 400

4.11. Downloading configuration and exporting CID fileAfter you have built the IEC 61850 data model and done the SPA mapping, it is possible to download the configuration to SPA-ZC 400. Select the IEC 61850 Device object and right-click to select the CID Export. You can also export the CID file to your workstations file system and use it in system level tools, for example to configure your IEC 61850-8-1 client.

If you download configuration to SPA-ZC 400 the first time, change the IP address from default address (192.0.2.10) to new IP address according to planned network structure.

CET and SPA-ZC 400 have a checking mechanism to avoid IP addressing problems. If you select another subnet against current IP address, CET cannot connect anymore to SPA-ZC 400 after the configuration downloading. You have to change the used IP address and workstation/laptop address to access the configuration again. If IP address changes radically, CET asks if you are aware of it. If you accept the changed subnet, SPA-ZC 400 resets used IP address and takes the new address in to use. If you do not accept changes, SPA-ZC 400 uses the old IP address against the configuration.

A040029

Fig. 4.11.-1 Downloading the devices configuration

50


4.12. Commissioning SPA-ZC 400The downloaded CID file is taken into use when restarting SPA-ZC 400.

Normally, the reset happens automatically after the configuration is downloaded with Communication Engineering Tool.

You can see how the configuration process is progressing from the diagnostic LEDs. When the SPA-ZC 400 configuration is completed, then the green LED is on. If SPA-ZC 400 is online with the IEC 61850 client, you can check the general configuration status of SPA-ZC 400 from the data model LD0.LLN0.Health.stVal:

1. OK, configuration is completed succesfully.2. Warning, no clock synchronization.3. Alarm, during the configuration appeared errors.

If the configuration fails, first you should check the error log files from the SPA-ZC 400 file system.The status and error logs locate in the /log directory.

4.12.1. Checking SPA communicationIn case the configuration is completes succesfully, you can check the resetable diagnostic counters through the IEC 61850 data model or SPA-ZC 400 file system.

SPA-ZC 400 Diagnostic counters are part of the LD0.LLN0.Mod attributes. The data object type is ABB specific extension in IEC 61850 data model and contains the counters as data attibutes. It is possible to reset the counters by writing 1 into ctlVal. It is not recommended to put the counters into the data set because the counter values are updated only during a read operation.

A040136

Fig. 4.12.1.-1 Diagnostic counters

51


SPA-ZC 400

4.12.2. Obtaining diagnostic data through ftpThe following session gets the diagnostic counters through ftp.

C:\>ftp x.x.x.x

User: abb

Password: abb

ftp> cd d:

ftp> get diagnostic.txt

ftp> quit

The q attribute quality bits of the properly updated data objects indicate GOOD or DEFAULTED. If this is not the case, SPA-ZC 400 and RE_54_ configurations are not equal. If all the data objects have INVALID quality, the SPA communication is not running.

52


5. Technical data

5.1. Interfaces

SPA-ZC 400 - IED interface- Fixed mechanics and fixed connectors for REF 541/3/5, REM 543/5 and

RET 541/3/5 protection relays D-type subminiature connector for IEC 61850 traffic D-type subminiature connector for simultaneous dual port communication

(optional, see Section 2.3. SPA-ZC 400-BB and SPA-ZC 400-MM Product Overview)

IEC 61850 interface Fibre optic LAN connector MT-RJ multimode glass fibre transceiver

LON/SPA/IEC 60870-5-103 interface (Optional)- Fibre optic connector options

ST multimode glass fibre transmitter/receiver pair or snap-in multimode plastic fibre transmitter/receiver pair

Optical fibres- See fibre optic guides:

SPA-ZF Optical glass fibres, multimode graded index type Plastic-core fibre optic cables, features and instructions for mounting

For more information, see Section 1.8. Related documents.

Diagnostic LEDsSPA-ZC 400 common diagnostic LEDs

- Power- Diagnostic

Red Green

LAN diagnostic LEDs

- LINK- TX- RX

53


SPA-ZC 400

LON/SPA/IEC 60870-5-103 diagnostic LED

- RX

Dimensions and weight

A040130

Fig. 5.1.-1 Dimensions of the SPA-ZC 400 module

Table 5.1.-1 Dimensions and weight

Type Dimensions [mm] Weight [g]SPA-ZC 400 195 x 50 x 26 130

��

��

��

��

��

��

��

�

��

��

�

��

��

�� !

��"��

��

�/

�

��

))!)&!)�!0)!&&!))

�)

�)1

�'

54


5.2. Test and conditions

Table 5.2.-1 Environmental test and conditions

Recommended service temperature range (continuous)

-10...+55°C

Transport and storage temperature range -40...+70°C according to the IEC 60068-2-48

Dry heat test According to the IEC 60068-2-2

Dry cold test According to the IEC 60068-2-1

Damp heat test, cyclic According to the IEC 60068-2-30

Table 5.2.-2 Electromagnetic compatibility tests

EMC immunity test level meets the requirements listed below

1 MHz burst disturbance test, class III According to the IEC 60255-22-1

Common mode 2.5 kV

Differential mode 1.0 kV

Electrostatic discharge test, class III According to the IEC 61000-4-2 and IEC 60255-22-2

For contact discharge 6 kV

For air discharge 8 kV

Radio frequency interference tests

Conducted, common mode According to the IEC 61000-4-6 and IEC 60255-22-6 (2000) 10 V (rms), f=150 kHz...80 MHz

Radiated, amplitude-modulated According to the IEC 61000-4-3 and IEC 60255-22-3 (2000)10 V/m (rms), f=80...1000 MHz

Radiated, pulse-modulated According to the ENV 50204 and IEC 60255-22-3 (2000) 10 V/m, f=900 MHz

Fast transient disturbance tests According to the IEC 60255-22-4 and IEC 61000-4-4

All terminals 4 kV

Surge immunity test According to the IEC 61000-4-5

Power supply 4 kV, line-to-earth2 kV, line-to-line

Power frequency (50 Hz) magnetic field IEC 61000-4-8

300 A/m continuous

55


SPA-ZC 400

Electromagnetic emission tests According to the EN 55011

Conducted, RF-emission (Mains terminal) EN 55011, class A, IEC 60255-25

Radiated RF-emission EN 55011, class A, IEC 60255-25

CE approval Complies with the EMC directive 89/336/EEC and the LV directive 73/23/EEC

Table 5.2.-3 Standard tests

Mechanical tests

Vibration tests (sinusoidal) According to the IEC 60255-21-1, class I

Shock and bump test According to the IEC 60255-21-2, class I

Table 5.2.-4 Standard tests

Supply current consumption

Running 340 mA

Start up 430 mA

Table 5.2.-2 Electromagnetic compatibility tests

56


6. Maintenance and service

6.1. General about serviceIf the SPA-ZC 400 module or a part of it is found to be faulty, the normal service operation is to replace the entire module. For more details, refer to the ordering information.

6.2. LED indicators

Possible sequences are:

1 3 5 Normal situation1 2 Missing boot image1 3 4 Configuration file is missing1 3 6 Unrecoverable error situation

6.3. SPA-ZC 400 communication settingsRE_ 54_ addresses are not properly configured if

diagnostic counter SPAReplyTimo increases constantly and SPAReplyData remains 0

quality of the data is INVALID

The following protocol specific settings have to be checked when setting up RE_ 54_:

Protocol selection for SPA-ZC 400

Table 6.3.-1 explains the possible port configuration of REF_ 54_ when SPA-ZC 400 is connected.

Table 6.2.-1 LED indicators

LED Color State Sequence number DescriptionPower Green On Power on

Link LAN Green On Indication for LAN link OKRX LAN Green On Indication for incoming LAN trafficTX LAN Green On Indication for outgoing LAN traffic

DIAG Green Red OffFlashingOnFlashingOnOff

OnOnOnOffOffFlashing

123456

Bootloader bootingBootloader, missing boot imageStartingOK, missing configurationEverything OKUnrecoverable error situation

RX Green On Indication for incoming LON traffic (LON, SPA, IEC 60870-5-103

The protocol selection is active only after rebooting the relay. For more information, see RE_54_ Technical Reference Manuals.

57


SPA-ZC 400

SPA command timeout

Spa command timeout should be < 1 second when LON interlocking is not in use.

SPA baud rate and SPA slave number

Baud rate and slave number have to be according to the SPA-ZC 400 configuration.

Table 6.3.-1 Protocol selection for RE_54_

Connectors/Communication parameters

X3.2/Protocol 2 X3.3/Protocol 3 Front connector

SPA (SMS) LON SPA

SPA (SMS) SPA -

IEC_103 LON (SMS) SPA

IEC_103 SPA (SMS) -

IEC_103 - SPA

DNP 3.0 LON (SMS) SPA

DNP 3.0 SPA (SMS) -

DNP 3.0 - SPA

Modbus LON (SMS) SPA

Modbus SPA (SMS) -

Modbus - SPA

- SPA SPA

It is not possible to use IEC 60870-5-103 and IEC 61850 simultaneously.

58


7. Technical reference

7.1. About this sectionThis chapter defines the compliance to IEC 61850 in terms of service, modeling, engineering interfaces and also exceptions and local adaptations. The information gives you a detailed explanation of the IEC 61850 capabilities of a product.

This chapter provides information about the following issues:

ACSI conformance statement Model conformance statement SCL conformance statement SCL control block Protocol implementation conformance statement

The ACSI conformance statement describes the abstract service interfaces, which are normally mapped to specific communication service (SCSM) and therefore indirectly stated in the protocol implementation conformance statement. The conformance statements and documents are referred to as Protocol Implementation Conformance Statement (PICS) and Model Implementation Conformance Statement (MICS).

NotationsFor the following clauses, the following definitions apply:

m Mandatory support. The item must be implemented.

c Conditional support. The item must be implemented if the stated condition exists.

o Optional support. The implementation may decide to implement the item.

x The implementation must not implement this item (excluded).

i The implementation of the item is not within the scope of this product (out-of-scope).

F/S Functional Standard. Should be applied.

Base Must be applied in any application claiming conformance to this standard.

59


SPA-ZC 400

7.2. ACSI conformance statement

7.2.1. ASCI basic conformance statement

7.2.2. ACSI models conformance statement

Table 7.2.1-1 ASCI basic conformance statement

Client/Subscriber

Server/Publisher

SPA-ZC 400/Comments

Client-Server roles

B11 Server side (of TWO-PARTY-APPLICATION-ASSOCIATION)

a Supported

B12 Client side (of TWO-PARTY-APPLICATION-ASSOCIATION)

a

SCSMs supported

B21 SCSM: IEC 6185-8-1 used Supported

B22 SCSM: IEC 6185-9-1 used Not Supported

B23 SCSM: IEC 6185-9-2 used Not Supported

B24 SCSM: other

Generic substation event model (GSE)

B31 Publisher side O Not Supported

B32 Subscriber side O Not Supported

Transmission of sampled value model (SVC)

B41 Publisher side O Not Supported

B42 Subscriber side O Not Supported

a. must be M if support for LOGICAL-DEVICE model has been declared

Table 7.2.2-1 ACSI models conformance statement

Client/Subscriber

Server/Publisher

SPA-ZC 400/Comments

If Server side (B1) supported

M1 Logical device a a Supported

M2 Logical device b b Supported

M3 Data c c Supported

M4 Data set d d Supported

M5 Substitution O O Supported

M6 Setting group control a a Supported

60


Reporting

M7 Buffered report control O O Supported

M7-1 sequence-number

M7-2 report-time-stamp

M7-3 reason-for-inclusion

M7-4 data-set-name

M7-5 data-reference

M7-6 buffer-overflow

M7-7 EntryID

M7-8 BufTim

M7-9 IntgPd

M7-10 GI

M8 Unbuffered report control M M Supported

M8-1 sequence-number

M8-2 report-time-stamp

M8-3 reason-for-inclusion

M8-4 data-set-name

M8-5 data-reference

M8-6 BufTim

M8-7 IntgPd

Logging O O Not Supported

M9 Log control O O Not Supported

M9-1 IntPd

M10 Log O O Not Supported

M11 Control M M Supported

If GSE (B31/32) is supported

Goose O O Not Supported

M12-1 EntryID

M12-2 DataRefInc

M13 GSSE O O Not Supported

Table 7.2.2-1 ACSI models conformance statement (Continued)

Client/Subscriber

Server/Publisher

SPA-ZC 400/Comments

61


SPA-ZC 400

7.2.3. ACSI service conformance statementThe table below defines the ACSI service conformance statement depending on the statement defined in Table 7.2.1-1.

If SVC (41/42) is supported

M14 Multicast SVC O O Not Supported

M15 Unicast SVC O O Not Supported

M16 Time M M Supported

M17 File Transfer O O Not Supported

a. Must be M if support for LOGICAL-DEVICE model has been declared.b. Must be M if support for LOGICAL-NODE model has been declared.c. Must be M if support for DATA model has been declared.d. Must be M if support for DATA-SET model has been declared.

Table 7.2.2-1 ACSI models conformance statement (Continued)

Client/Subscriber

Server/Publisher

SPA-ZC 400/Comments

Table 7.2.3-1 ACSI service conformance statement

Services AA: TP/MC

Client (C)

Server (S)

SPA-ZC 400/Comments

Server

S1 ServerDirectory TP M

Application association

S2 Associate M M Supported

S3 Abort M M Supported

S4 Release M M Supported

Logical device

S5 LogicalDeviceDirectory TP M M Supported

Logical node

S6 LogicalNodeDirectory TP M M Supported

S7 GetAllDataValues TP O M Supported

Data

S8 GetDataVelues TP M M Supported

S9 SetDataVelues TP O O Supported

S10 GetDataDirectory TP O M Supported

S11 GetDataDefinition TP O M Supported

62


Data set

S12 GetDataSetValues TP O M Supported

S13 SetDataSetValues TP O O Not Supported

S14 CreateDataSet TP O O Not Supported

S15 DeleteDataSet TP O O Not Supported

S16 GetDataSetDirectory TP O O Supported

Substitution

S17 SetDataValues TP M M Supported

Setting gropu control

S18 SelectActiveSG TP O O Not Supported

S19 SelectEditSG TP O O Not Supported

S20 SetSGValues TP O O Not Supported

S21 ConfirmEditSGValues TP O O Not Supported

S22 GetSGValues TP O O Not Supported

S23 GetSGCBValues TP O O Not Supported

Reporting

Buffered report control block (BRCB)

S24 Report TP a a Supported

S24-1 data-change (dchg)

S24-2 qchg-change (qchg)

S24-3 data-update (dupd)

S25 GetBRCBValues TP a a Supported

S26 SetBRCBValues TP a a Supported

Unbuffered report control block (URCB)

S27 Report TP a a Supported

S27-1 data-change (dchg)

S27-2 qchg-change (qchg)

S27-3 data-update (dupd)

S28 GetURCBValues TP a a Supported

Table 7.2.3-1 ACSI service conformance statement (Continued)

Services AA: TP/MC

Client (C)

Server (S)

SPA-ZC 400/Comments

63


SPA-ZC 400

S29 SetURCBValues TP a a Supported

Logging

Log control block

S30 GetLCBValues TP M M Not Supported

S31 SetLCBValues TP O M Not Supported

Log

S32 QueryLogByTime TP b M Not Supported

S33 QueryLogByEntry TP b M Not Supported

S34 GetLogStatusValues TP M M Not Supported

Generic substation event model (GSE)

GOOSE-CONTROL-BLOCK

S35 SendGOOSEMessage MC c c Not Supported

S36 GetReference TP O d Not Supported

S37 GetGOOSEElementNumber TP O d Not Supported

S38 GetGoCBValues TP O O Not Supported

S39 SetGoCBValues TP O O Not Supported

GSSE-CONTROL-BLOCK

S40 SendGSSEMessage MC c c Not Supported

S41 GetReference TP O d Not Supported

S42 GetGSSEElementNumber TP O d Not Supported

S43 GetGsCBValues TP O O Not Supported

S44 SetGsCBValues TP O O Not Supported

Transmission of sampled value model (SVC)

Multicast SVC

S45 SendMSVMessage MC e e Not Supported

S46 GetMSCVCBValues TP O O Not Supported

S47 SetMSVCBValues TP O O Not Supported

Unicast SVC

S48 SendUSVMessage MC e e Not Supported


Services AA: TP/MC

Client (C)

Server (S)

SPA-ZC 400/Comments

64


S49 GetUSCVCBValues TP O O Not Supported

S50 SetUSVCBValues TP O O Not Supported

Control

S51 Select M M Supported

S52 SelectWithValue TP M M Supported

S53 Cancel TP O M Supported

S54 Operate TP M M Supported

S55 Command-Termination TP M M Supported

S56 TimeActivated-Operate TP O O Not Supported

File Transfer

S57 GetFile TP O M Not Supported

S58 SetFile TP O O Not Supported

S59 DeleteFile TP O O Not Supported

S60 GetFileAttributeValues TP O M Not Supported

Time

T1 Time resolution of internal clock 2-10 (1ms)

(nearest negative power of 2 in seconds)

T2 Time accurancy of internal clock X T1

T2

T3

T3 Supported TimeStamp resolution 2-10 (1ms)

(nearest negative power of 2 in seconds)

a. Must declare support for at least one (BRCB or URCB).b. Must declare support for at least one (QueyLogByTime or QueyLogByEntry).c. Must declare support for at least one (SendGOOSEMessage or SendGSSEMessage).d. Must declare support if TP association is available.e. Must declare support for at least one (SendMSVMessage or SendUSVMessage).


Services AA: TP/MC

Client (C)

Server (S)

SPA-ZC 400/Comments

65


SPA-ZC 400

7.3. Model conformance statementIn this chapter the Model Implementation Conformance Statement (MICS) is defined detailing the standard data object model elements supported by SPA-ZC 400. It is also possible to export the information in MICS to a CID file. The CID file can be used in the system tool, see Section 4.11. Downloading configuration and exporting CID file. Some of the data cannot be retrieved from the IED, but it is the default value in the SPA-ZC 400.

7.3.1. Common data attribute classes

7.3.1.1. QualityTable 7.3.1.1-1 Quality

Quality Type Definition

Attribute Name AttributeType Value/ Value Range M/O/C SPA-ZC 400/Comments

PACKED LIST

validity CODED ENUM good | invalid | reserved | questionable

M Supported

detailQual PACKED LIST M Supported

overflow BOOLEAN M Defaulted

outOfRange BOOLEAN M Supported

badRefererence BOOLEAN M Defaulted

oscillatory BOOLEAN M Defaulted

failure BOOLEAN M Defaulted

oldData BOOLEAN M Supported

inconsistent BOOLEAN M Defaulted

inaccurate BOOLEAN M Defaulted

source CODED ENUM process | substituted DEFAULT process

M Supported

test BOOLEAN DEFAULT FALSE M Defaulted

operatorBlocked BOOLEAN DEFAULT FALSE M Defaulted

The DEFAULT value must be applied, if the functionality of the related attribute is Not Supported. The mapping may specify to exclude the attribute from the message, if it is Not Supported or if the DEFAULT value applies.

66


7.3.1.2. Analogue value

7.3.1.3. Configuration of analogue value

7.3.1.4. Range configuration

Table 7.3.1.2-1 Analogue value

AnalogueValue Type Definition


I INT32 integer value GC_1 Not Supported

f FLOAT 32 floating point value GC_1 Supported

Table 7.3.1.3-1 Configuration of analogue value

ScaledValueConfig Type Definition


scaleFactor FLOAT 32 M Not Supported

offset FLOAT 32 M Not Supported

Table 7.3.1.4-1 Range configuration

RangeConfig Type Definition


hhLim AnalogueValue M Supported

hLim AnalogueValue M Supported

ILim AnalogueValue M Supported

IILim AnalogueValue M Supported

min AnalogueValue M Supported

max AnalogueValue M Supported

67


SPA-ZC 400

7.3.1.5. Step position with transient indication

7.3.2. Originator

Table 7.3.1.5-1 Step position with transient indication

ValWithTrans Type Definition


posVal INT8 -64 ... 63 M Supported

transInd BOOLEAN O Not Supported

Table 7.3.2-1 Step position with transient indication

OriginatorType Definition


orCat ENUMERATED not-supported | bay-control | station-control | remote-control | automatic-bay | automatic-station | automatic-remote | maintenance | process

M Supported

orIdent OCTET STRING64 M Supported

Table 7.3.2-2 Values for orCat

Value Explanation

bay-control Control operation issued from an operator using a client located at bay level

station-control Control operation issued from an operator using a client located at station level

remote-control Control operation from a remote operater outside the substation (e.g. network control center)

automatic-bay Control operation issued from an automatic function at bay level

automatic-station Control operation issued from an automatic function at station level

automatic-remote Control operation issued from an automatic function outside of the substation

maintenance Control operation issued from a maintenance / service tool

process Status change occurred without control action (e.g. external trip of a circuit breaker or failure inside the breaker)

68


7.3.2.1. Unit definition

7.3.2.1. Vector definition

7.3.3. Common data classes

7.3.3.1. Single point status (SPS)The table below defines the common data class of single point status.

Table 7.3.2-3 Unit

Unit Type Definition


SIUnit ENUMERATED According to table in Annex A

M Supported

multiplier ENUMERATED According to table in Annex A

O Supported

Table 7.3.2-4 Vector

Vector Type Definition


mag AnalogueValue M Supported

ang AnalogueValue O Not Supported

Table 7.3.3.1-1 Single point status (SPS)

SPS class

Attribute Name

Attribute Type

FC TrgOp Value/ Value range

M/O/C SPA-ZC 400/Comments

DataName Inherited from Data Class (refer to IEC 61850-7-2) Supported

DataAttribute

Status

stVal BOOLEAN ST dchg TRUE | FALSE M Supported

q Quality ST qchg M Supported

t TimeStamp ST M Supported

Substitution

subEna BOOLEAN SV PICS_SUBST Not Supported

subVal BOOLEAN SV TRUE | FALSE PICS_SUBST Not Supported

69


SPA-ZC 400

7.3.3.2. Double point status (DPS)The table below defines the common data class of double point status.

subQ Quality SV PICS_SUBST Not Supported

subID VISIBLE STRING64 SV PICS_SUBST Not Supported

Configuration, description and extension

d VISIBLE STRING255 DC Text O Supported

cdcNs VISIBLE STRING255 EX AC_DLNDA_M Not Supported

cdcName VISIBLE STRING255 EX AC_DLNDA_M Not Supported

dataNs VISIBLE STRING255 EX AC_DLNDA_M Not Supported

Table 7.3.3.1-1 Single point status (SPS) (Continued)

SPS class

Attribute Name

Attribute Type



Table 7.3.3.2-1 Double point status (DPS)

DBS class

Attribute Name

Attribute Type




DataAttribute

Status

stVal CODED ENUM ST dchg intermediate-state | off | on | bad-state

M Supported



Substitution


subVal INT32 SV PICS_SUBST Not Supported



Configuration, Description and extension



70


7.3.3.3. Integer status (INS)The table below defines the common data class of integer status.


dataNs VISIBLE STRING255 EX AC_DLNDA_M Not Supported

Table 7.3.3.2-1 Double point status (DPS) (Continued)

DBS class

Attribute Name

Attribute Type




DataAttribute

Table 7.3.3.3-1 Integer status (INS)

INS class

Attribute Name

Attribute Type




DataAttribute

Status

stVal INT32 ST dchg M Supported



Substitution


subVal INT32 SV PICS_SUBST Not Supported



Configuration, Description and Extension




dataNs VISIBLE STRING255 EX AC_DLN_M Not Supported

71


SPA-ZC 400

7.3.3.4. Protection activation information (ACT)The table below defines the common data class of protection activation information.

Table 7.3.3.4-1 Protection activation information (ACT)

ACT class

Attribute Name

Attribute Type




DataAttribute

Status

general BOOLEAN ST dchg M Supported

phsA BOOLEAN ST dchg O Supported

phsB BOOLEAN ST dchg O Supported

phsC BOOLEAN ST dchg O Supported

neut BOOLEAN ST dchg O Supported




operTm TimeStamp CF O Not Supported





Different variants of the type exist based on the connectivity package short address information (sAddr). Underlined information indicates the basic type.

72


7.3.3.5. Directional protection activation information (ACD)The table below defines the common data class of directional protection activation information.

Table 7.3.3.5-1 Directional protection activation information (ACD)

ACD class

Attribute Name

Attribute Type




DataAttribute

Status

general BOOLEAN ST dchg M Supported

dirGeneral ENUMERATED ST dchg unknown | forward | backward | both

M Supported

PhsA BOOLEAN ST dchg GC_2 (1) Supported

dirPhsA ENUMERATED ST dchg unknown | forward | backward

GC_2 (1) Supported

PhsB BOOLEAN ST dchg GC_2 (2) Supported

dirPhsB ENUMERATED ST dchg unknown | forward | backward

GC_2 (2) Supported

PhsC BOOLEAN ST dchg GC_2 (3) Supported

dirPhsC ENUMERATED ST dchg unknown | forward | backward

GC_2 (3) Supported

Neut BOOLEAN ST dchg GC_2 (4) Supported

dirNeut ENUMERATED ST dchg unknown | forward | backward

GC_2 (4) Supported








73


SPA-ZC 400

7.3.3.6. Security violation counting (SEC)The table below defines the common data class of security violation counting.

7.3.3.7. Binary counter reading (BCR)The table below defines the common data class of binary counter reading.

Table 7.3.3.6-1 Security violation counting (SEC)

SEC lass

Attribute Name

Attribute Type



DataName Inherited from Data Class (refer to IEC 61850-7-2) Not Supported

DataAttribute

Status

cnt INT32U ST dchg M Not Supported

sev ENUMERATED ST unknown | critical | major | minor | warning

M Not Supported

T TimeStamp ST M Not Supported

addr OCTET STRING64 ST O Not Supported

addInfo VISIBLE STRING64 ST O Not Supported


D VISIBLE STRING255 DC O Not Supported




Table 7.3.3.7-1 Binary counter reading (BCR)

BCR class

Attribute Name

Attribute Type

FC TrgOp Value/ Value

ethernet adapter installation and commissioning manual...10 spa-zc 400 1mrs755347 ethernet adapter...

Documents