d instruction manual

1CPTD

Subestation Central Unit

Instruction Manual

BCPT0906Dv01© ZIV GRID AUTOMATION, S.L. 2011

ZIV APLICACIONES Y TECNOLOGÍA, S.L.

End-User Software License Agreement THIS IS A LEGAL AGREEMENT BETWEEN YOU (AS "LICENSEE") AND ZIV APLICACIONES Y TECNOLOGIA, S.L. (AS "LICENSOR") FOR THE SOFTWARE PROGRAM YOU HAVE PURCHASED. PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE USING THE PROGRAM DISKETTES. THE PROGRAM IS COPYRIGHTED AND LICENSED TO YOU (NOT SOLD). IF YOU INSTALL, USE OR COPY THE SOFTWARE PROGRAM, YOU ARE ACCEPTING AND AGREEING TO THE TERMS OF THIS LICENSE AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THE TERMS OF THIS LICENSE AGREEMENT, YOU SHOULD PROMPTLY RETURN THE ENTIRE CONTENTS OF THIS PACKAGE TO YOUR SELLER.

Terms and Conditions of License

1. License Grant. Licensor hereby grants to you, and you accept, a nonexclusive license to use the Program Diskettes and the computer programs contained therein in machine-readable, object code form only, and the accompanying documentation (collectively referred to as the "Software"), only as authorized in this License Agreement. You may use the program(s) solely in your internal operations at all facility sites you own but only with the type of machines and equipment specified in the printed material furnished by Licensor and only in accordance with the instructions given in such material.

2. Restrictions. You may not: (a) use, copy, modify or transfer the Software except as expressly provided

in this or another Agreement with Licensor, (b) reverse engineer, decompile or disassemble or separate the components of the Software, or (c) rent, sell or lease the Software or make the Software available to others to do any of the foregoing.

3. Back-Up. Upon loading the Software into your computer, you may retain the Program Diskette for

backup purposes. In the event the program diskettes are damaged, you may return them to Licensor, at your expense, and obtain a new copy free of charge. 4. No Assignment. The License is intended for your exclusive use. You agree that you will not assign, sublicense, transfer, pledge, lease, rent or share your rights under this License Agreement. 5. Licensor's Rights. You acknowledge and agree that the Software is the proprietary product of Licensor protected under International laws and treaties. You further acknowledge and agree that all right, title and interest in and to the Software, including associated intellectual property rights, are and shall remain with Licensor. This License Agreement does not convey to you an interest in or to the Software, but only a limited right of use revocable in accordance with the terms of this License Agreement. 6. Confidentiality. The Software is confidential and no details or information relating to the same shall be disclosed to any third party without the prior written consent of Licensor.

7. Term. This License Agreement is effective upon your opening of the package and shall continue until

terminated. You may terminate this License Agreement at any time by returning the Software and all copies thereof and extracts therefrom to Licensor, or by destroying all tangible copies of the Software. Licensor may terminate this License Agreement upon your breach of any term hereof. Upon such termination by Licensor, you agree to return to Licensor the Software and all copies and portions thereof, or destroy all tangible copies of the Software, and to erase all copies of the Software held in computer memory or otherwise.

8. AS IS. THE SOFTWARE IS LICENSED "AS IS" AND WITHOUT A WARRANTY OF ANY KIND.

LICENSOR EXPRESSLY DISCLAIMS ANY AND ALL OTHER WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING, WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. LICENSOR DOES NOT WARRANT THAT THE FUNCTIONS CONTAINED IN THE SOFTWARE WILL MEET UNINTERRUPTED OR ERROR FREE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU.

9. Limitation of Liability. Licensors sole and entire liability, and your exclusive remedy, with respect to

any claims relating to the Software shall be to provide a new set of diskettes free of charge. In no event shall Licensor be liable for any indirect, incidental, consequential, special, or exemplary damages or lost profits, even if Licensor has been advised of the possibility of such damages,

10. Licensee's lndemnity. You shall defend, indemnify and hold Licensor harmless against any loss or

damage of any kind arising from a breach by you of this License Agreement, or any use or misuse of the Software by you or your employees, agents, or representatives, and from any other of your conduct or from any claim or action by any of your customers in connection with the Software or this License Agreement.

11 Governing Law. This License Agreement shall be construed and governed in accordance with the

internal laws of the State of Illinois, U.S.A.. 12. No Waiver. The failure of either party to enforce any rights hereunder or to take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequent actions in the event of future breaches.

13. Entire Agreement. This License Agreement is the entire agreement between you and Licensor with

respect to the use of the Software and supersedes all prior understandings or agreements between the parties. This License Agreement may be amended only by a writing by an officer of Licensor.

ZIV Aplicaciones y Tecnología, S.L. Parque Tecnológico, 210

48170 ZAMUDIO (Vizcaya) Apartado de Correos 757

48080 BILBAO SPAIN

Telephone: 34 94 452 20 03

WARNING ZIV Aplicaciones y Tecnología, S.L. has all rights reserved on this manual. No part of this manual shall be reproduced, stored in a retrieval system, or transmitted by any means, electronic, mechanical, photocopying, recording, or otherwise, without written permission from the Licensor. All terms mentioned in this manual are only for information purposes. ZIV Aplicaciones y Tecnología, S.L. does not assume any liability for damages resulting from the unilateral use of the information contained in this manual.

Index

BCPT0906D © ZIV Aplicaciones y Tecnología, S. L. Zamudio, 2009

I

Index CHAPTER 1. Description ............................................................................................. 1-1 1.1 General ............................................................................................................. 1-2 1.2 CPT-D Functions .............................................................................................. 1-2 1.3 Model Selection ................................................................................................ 1-3 CHAPTER 2. Technical Data ........................................................................................ 2-1 CHAPTER 3. Standards and Type Tests .................................................................... 3-1 CHAPTER 4. Physical Architecture ............................................................................ 4-1 4.1 General ............................................................................................................. 4-2 4.2 Dimensions ....................................................................................................... 4-2 4.3 Connection Elements ....................................................................................... 4-2 4.3.1 Terminal blocks ................................................................................................ 4-2 4.3.2 Connectors ....................................................................................................... 4-3 4.3.3 Removing of Printed Circuit Boards (Non Self-shorting) .................................. 4-4 4.4 Human-Machine Interface ................................................................................ 4-4 CHAPTER 5. Description of Operation ....................................................................... 5-1 5.1 Introduction ....................................................................................................... 5-2 5.2 Communications ............................................................................................... 5-2 5.2.1 Physical Medium .............................................................................................. 5-2 5.2.2 Communication of the CPT-D with the DBC-*********G** ................................. 5-2 5.2.3 Ethernet Communication .................................................................................. 5-2 5.2.4 IEC61850 ......................................................................................................... 5-3 5.2.5 Commands sent to IEC61850 devices ............................................................. 5-3 5.3 LEDs ................................................................................................................. 5-4 5.4 Digital Inputs ..................................................................................................... 5-4 5.5 Digital Outputs .................................................................................................. 5-4 CHAPTER 6. Alphanumeric Keyboard and Display .................................................. 6-1 6.1 Alphanumeric Keyboard and Display ............................................................... 6-2 6.2 Keys, Functions and Operation Mode .............................................................. 6-3 6.3 Access to functions through the keyboard ....................................................... 6-6 6.4 Access to IEC61850 Menu ............................................................................... 6-8 CHAPTER 7. Receiving Test ........................................................................................ 7-1 7.1 General ............................................................................................................. 7-2 7.2 Preliminary Inspection ...................................................................................... 7-2 7.3 In Service Test ................................................................................................. 7-2 7.4 Configuration .................................................................................................... 7-3 7.5 Port Test ........................................................................................................... 7-3 7.6 LEDs Status ..................................................................................................... 7-3 7.7 Installation ........................................................................................................ 7-4 CHAPTER. 8 Figures .................................................................................................... 8-1

Index

© ZIV Aplicaciones y Tecnología, S. L. Zamudio, 2009 BCPT0906D

II

SCHEMES AND DRAWINGS ANNEX A. Protocol Implementation Conformance Statement (PICS) ..................... A-1 A.1 Profile CONFORMANCE Statement ................................................................. A-2 A.1.1 Profile Support .................................................................................................. A-2 A.1.2 T-Profile Support ............................................................................................... A-2 A.1.3 ACSI Basic Conformance Statement ................................................................ A-2 A.1.4 ACSI Models Conformance Statement ............................................................. A-3 A.1.5 ACSI Service Conformance Test ...................................................................... A-5 A.2 MMS CONFORMANCE Statement ................................................................... A-9 A.2.1 Environmental Services .................................................................................... A-9 A.2.1.a MMS InitiateRequest General Parameters ....................................................... A-9 A.2.1.b MMS InitiateResponse General Parameters ..................................................... A-9 A.2.1.c MMS Service Supported Conformance Table ................................................... A-10 A.2.1.d MMS Parameter Conformance Building Block (CBB) ....................................... A-13 A.2.1.e GetNameList Conformance Statement ............................................................. A-14 A.3 VARIABLE ACCESS CONFORMANCE Statement .......................................... A-14 A.3.1 Supporting Productions ..................................................................................... A-14 A.3.1.a VariableAccessSpecification Conformance Statement ..................................... A-14 A.3.1.b VariableSpecification Conformance Statement ................................................. A-14 A.3.2 Read Conformance Statement .......................................................................... A-15 A.3.3 Write Conformance Statement .......................................................................... A-15 A.3.4 InformationReport Conformance Statement ..................................................... A-15 A.3.5 GetVariableAccessAttributes Conformance Statement .................................... A-16 A.3.6 GetNamedVariableListAttributes Conformance Statement ............................... A-16 A.4 GOOSE SERVICES .......................................................................................... A-16 A.4.1 GOOSE Conformance Statement ..................................................................... A-16 A.5 Further Specification of Device Capabilities ..................................................... A-17 A.6 Physical Layer ................................................................................................... A-17 ANNEX B. Protocol Implementation Extra Information for Testing (PIXIT) ............. B-1 B.1 Introduction ....................................................................................................... B-2 B.1.1 Contents of this Document ................................................................................ B-2 B.2 PIXIT for Association Model .............................................................................. B-2 B.3 PIXIT for Server Model ...................................................................................... B-3 B.4 PIXIT for Data Set Model .................................................................................. B-4 B.5 PIXIT for Substitution Model ............................................................................. B-4 B.6 PIXIT for Setting Group Control Model ............................................................. B-4 B.7 PIXIT for Reporting Model ................................................................................. B-5 B.8 PIXIT for Logging Model ................................................................................... B-6 B.9 PIXIT for Generic Substation Events Model ...................................................... B-6 B.10 PIXIT for Transmission of Sample Values Model .............................................. B-7 B.11 PIXIT for Control Model ..................................................................................... B-7 B.12 PIXIT for Time and Time Synchronisation Model .............................................. B-9 B.13 PIXIT for File Transfer Model ............................................................................ B-9

CHAPTER 1

Description

Chapter 1


1-2

1.1 General CPT-D relays are designed to operate with Busbar Differential Protection Systems DBN (DBC-B ********G*) for IEC61850 communications protocol conversion.

1.2 CPT-D Functions CPT-D relays are linked to DBN devices through fibre optic via a proprietary communications protocol and configure their internal functions at logic level according to standard IEC61850. Said functions will be visible to other substation IEDs via network interface Ethernet 100-Base T. The CPT-D also features an interface to capture the GPS master signal, both directly from a GPS aerial and through connection to a GPS receiver device.

Description


1-3

1.3 Model Selection

Figure 1.1: Model Selection.

Chapter 1


1-4

Notes:

CHAPTER 2

Technical Data

Chapter 2


2-2

Power Supply Voltage Terminals are provided with an auxiliary power supply the value of which is: 110 Vdc/Vac (±20%) Note: in case of failure of the auxiliary power supply a maximum outage of 100 ms. at 110 Vcc is allowed. Hardware Data - CPU board with microprocessor at 533MHz with industrial temperature range (includes two

chips for Ethernet Network with 100Base-T connection, Compact-Flash and master USB controller).

- 128 Mb of RAM. - Internal Flash Memory of 16 Mb. - Removable Compact-Flash disk of 256 Mb (expandable). - 2 Ethernet ports type 100Base-T. - Coaxial connector for IRIG-B123 signal. - 8 digital status contact inputs and 8 digital status contact outputs. - USB master port. - Front panel with MMI (keyboard and display) and LEDs (optional). Status Contact Inputs (*) 8 digital status contact inputs with polarity. Rated Voltage Load V on 125 Vdc 800 mW 75 Vdc Status Contact Outputs (*) Double Contact Outputs. Power Make and carry (with resistive load) 30 A for 1 s Power in Continuous service (with resistive load) 8 A Connection capability 2500 W Break capability (resistive) 150W -max. 8A- (up to 48 Vdc) 55W (80Vdc - 250Vdc) 1250 VA Break capability (L/R = 0.04 s) 60 W to 125 Vdc Switching voltage 250 Vdc (*) These Status Contact Inputs/Outputs are not operatives.

Technical Data


2-3

Communication Data Communications Ports GFO, PFO, RS232C, RS232, RS485 LAN Ports (RJ45) Glass Fiber Optics Transmission Type Multimode Wavelength 820 nm Connector ST Transmitter minimum power 50/125 fiber - 20 dBm 62.5/125 fiber - 17 dBm 100/140 fiber - 7 dBm Receiver sensitivity - 25.4 dBm Plastic Fiber Optics (1 mm) (*) Wavelength 660 nm Transmitter minimum power - 16 dBm Receiver sensitivity - 39 dBm RS232-Full Modem Transmission DB-9 connector (9 pins), signals used Pin 1 - DCD (P1 and P2) Pin 2 - RXD Pin 3 - TXD Pin 4 - DTR Pin 5 - GND Pin 6 - DSR Pin 7 - RTS Pin 8 - CTS Pin 9 – RI Synchronous Special Communication Port DB-25 connector (25 pins), signals used: Pin 2 - TX (P5) Pin 3 - RX Pin 4 - RTS Pin 5 - CTS Pin 7 - GND Rest - N/C (*) Although these ports are physically available, are not operative.

Chapter 2


2-4

Communication Data RS485 Transmission (*) Signals used: Pin 1- GND Pin 2 - (A) TX+ / RX+ Pin 3 - (B) TX- / RX- RJ45 Transmission (*) Signals used: Pin 1 - TX+ Pin 2 – TX- Pin 3 - RX+ Pin 4 - N/C Pin 5 - N/C Pin 6 - RX- Pin 7 - N/C Pin 8 - N/C Coaxial Connector for Synchronizer Clock with IRIGB-123 Interface B: 100pps 1: Amplitude modulated wave 2: 1kHz/1ms 3: BCD, SBS BNC Connector Internal Connection - Signal External Connection - GND (*) Although these ports are physically available, are not operative.

CHAPTER 3

Standards and Type Tests

Chapter 3


3-2

The equipment satisfies the standards indicated below. When not specified, the standard is UNE 21-136 (IEC-60255). Insulation Test (Dielectric Strength) IEC-60255-5 Between all circuit terminals and ground 2 kV, 50/60 Hz, for 1 minute or 2.5 kV, 50/60 Hz, for 1 second Between all circuit terminals 2 kV, 50/60 Hz, for 1 minute or 2.5 kV, 50/60 Hz, for 1 second Insulation resistance measurement IEC -60255-5 Common Mode: R ≥ 100 MΩ or 5μA Differential Mode: R ≥ 100 kΩ or 5mA Voltage Impulse Test IEC -60255-5 (UNE 21-136-83/ 5) Common Mode (Digital Inputs, Outputs and Power Supply): 5 kV; 1.2/50 μs; 0.5 J Differential Mode (Digital Outputs): 1 kV; 1.2/50 μs Differential Mode (Power Supply): 3 kV; 1.2/50 μs 1 MHz Burst Test IEC -60255-22-1 Class III (UNE 21-136-92/22-1) Common Mode: 2.5 kV Differential mode: 2.5 kV Fast Transient Disturbance Test IEC -60255-22-4 Class IV (UNE 21-136-92/22-4) (IEC 61000-4-4) 4 kV ±10 % Radiated Electromagnetic Field Disturbance IEC 61000-4-3 Class III Amplitude modulated (EN 50140) 10 V/m Pulse modulated (EN 50204) 10 V/m Conducted Electromagnetic Field Disturbance IEC 61000-4-6 Class III (EN 50141) Amplitude modulated 10 V Surge immunity IEC -61000-4-5 (UNE 61000-4-5) (1.2/50μs – 8/20μs) Between conductors: 4 kV Between conductor and ground: 4 kV Electrostatic Discharge Test IEC 60255-22-2 Class IV (UNE 21-136-92/22-2) (IEC 61000-4-2) Contact ±8 kV ±10 % In the air ±15 kV ±10 %

Standards and Type Tests


3-3

Electromagnetic immunity at IEC 61000-4-8 industrial frequency (50/60Hz) Conducted and radiated EN55022 (Radiated) electromagnetic emissions EN55011 (Conducted) Temperature Operating Range: From -20º C to + 85º C Power Supply Ripple in the power supply IEC 60255-11 / UNE 21-136-83 (11) < 20 % and 100 ms Supply voltage polarity reversal IEC 61131-2 Vibration Test (sinusoidal) IEC -60255-21-1 Class I Shock and Bump Test IEC -60255-21-2 Class I CPT models comply with the 89/336/EEC standard of electromagnetic compatibility

Chapter 3


3-4

Notes:

CHAPTER 4

Physical Architecture

Chapter 4


4-2

4.1 General The CPT-D is made up of several cards with different functions:

• Power Supply • Digital Status Contact Inputs / Outputs • Communication Ports • IRIG-B Synchronization Interface • Ethernet Connection • Processor Module • Frontal Card

Figure 4.1 represents the front view of a CPT-D.

Figure 4.1: Front View of a CPT-D.

4.2 Dimensions The IEDs are fixed to enclosures of 1 19" rack width and 2 rack heights. They are designed to be installed semi-flush mounted in panels. The enclosure is graphite grey.

4.3 Connection Elements 4.3.1 Terminal blocks The terminal blocks are arranged horizontally at the rear part of the CPT-D. They are distributed as follows:

• 1 terminal block with 20 terminals for the power supply and 8 digital status contact outputs.

• 1 terminal block with 16 terminals for 8 digital status contact inputs. The terminals can take wire up to #14 AWG.

Physical Architecture


4-3

4.3.2 Connectors The equipment is supplied with a number of connectors, as follows:

- Power supply connector (B1..B3): Located on the back of the equipment, at the 20 terminal block.

- Connector for 8 digital outputs (B5..B20): Located on the back of the equipment, at the 20 terminal block. Said connector is not operative for this model.

- Connector for 8 digital inputs (A1..A16): Located on the back of the equipment, at the 16 terminal block. Said connector is not operative for this model.

- Connector RS-232 for remote control communication (P1). Located on the back of the equipment and tagged as P1. Said connector is not operative for this model.

- Connector RS-232 for communication with miscellaneous equipment (P2). Located on the back of the equipment and tagged as P2. Said connector is not operative for this model.

- Connector for external synchronizing clock input. Located on the back of the equipment. CPT-D equipment are provided with a BNC connector arranged for connection to IRIG-B external synchronizing system.

- Optical fibre connectors for communication with protection and recording equipment (P3, P4). Located on the back of the equipment. 2 pairs (TxD and RxD) of connectors for plastic or crystal optical fibre are incorporated.

- Connector for synchronous special communications port (P5). Located on the back of the equipment and tagged as P5. Said connector is not operative for this model.

- Connection Ethernet 100 Base-T RJ-45 (LAN1 and LAN2): Located on the back of the equipment. To connect the CPT-D to an Ethernet LAN over which communications via TCP/IP protocol can be established. It is used for communications between the CPT-D, and IEC-61850 relays.

- Earthing screw. Located on the back of the equipment. The rear view of a generic CPT-D is shown at Figure 4.2.

Figure 4.2: Rear View of a CPT-D.

Chapter 4


4-4

Figures 4.3 and 4.4 show in detail the digital input and output diagram, respectively.

Figure 4.3: Digital inputs of the CPT-D. Figure 4.4: Power Supply and Digital outputs of the CPT-D.

4.3.3 Removing of Printed Circuit Boards (Non Self-shorting) The equipment has been designed to enable removal of some printed circuit boards. The Current Analog Input terminal connector block, where the external wiring is landed, is attached to both the terminal connector on the printed circuit board and the equipment case, using self-tapping screws. These screws must be removed before the board is withdrawn. Whenever this operation is performed, the protection should be placed in the “Not In Service” mode, and turned off.

4.4 Human-Machine Interface Front peripherals allow the interaction between user and CPT-D. The following can be found among them:

• Display and Keyboard A display composed of 20 columns and 4 rows is provided to show operation menus and data. It features a function keyboard composed of 4 keys F1 to F4, and 16 additional keys to access the different menu options.

• USB Master Port This port allows connecting a USB key to transfer files between the CPT-D Compact-Flash and the final user.

• LEDs The equipment is provided with 5 pairs of LEDs (transmission and reception) to indicate whether communication in one or other direction is active:

• green lamp for reception: signal RxD • red lamp for transmission: signal TxD

There is also an additional LED to show relay Ready and there are 4 LEDs to signal the DBC and CPT-D statuses.

CHAPTER 5

Description of Operation

Chapter 5


5-2

5.1 Introduction The main task of a CPT-D is to collect information from a Bus Differential Protection IED (DBN) by it Central Unit (DBC-********G**), process it and serve it to a higher conceptual level equipment with the IEC61850 protocol.

5.2 Communications Communications are the key element of the CPT-D, that is the responsible for collecting the information from a Bus Differential Protection IED (DBN), to convert it and operate as data server via IEC61850 protocol.

5.2.1 Physical Medium The connection between the CPT and bay devices is carried out mainly by:

- Fiber Optic. Available only for the CPT-D connection with the DBC-********G**. There are two reasons why this physical medium is used: one, to isolate the CPT-D from possible damage from overvoltages in the rest of the equipment; and two, to prevent possible interference with communications caused by existing wires at the installations. The CPT-D has 2 fiber optic ports, labelled as P3 and P4.

- Twisted pair Ethernet 10-100 Base-T. Used for communications over IEC-61850

Ethernet networks. The CPT is provided with 2 net ports with RJ-45 electrical type interface, labelled LAN1 and LAN2.

5.2.2 Communication of the CPT-D with the DBC-*********G** Communications between CPT-D and DBC is through a proprietary protocol via fibre optic. Communications parameters (baud rate, parity bits, stop bits, etc.) are factory set.

5.2.3 Ethernet Communication The CPT-D operates as IEC - 61850 server to allow communications with higher level devices using IEC-61850 MMS protocol. This IEC-61850 communications is available through only one of the CPT-D Ethernet ports (LAN1 or LAN2); so that the port must be selected in advance through the CPT-D configuration. The CPT-D is factory configured with the following IP addresses:

- LAN 1: 192.168.1.50 - LAN 2: 192.168.1.51.

To modify said IPs, file tcp.cfg, located in CFDISK/cfg, must be accessed through FTP.

Description of Operation


5-3

5.2.4 IEC61850 Standard IEC61850 defines the substation communications bus, mainly to define:

- Which data are available and how to name and describe them. - How data are accessed and interchanged between the different devices. - How to connect the different elements to the communications networks.

One of the benefits worth mentioning of IEC61850 is to avoid the loss of context suffered by data transmitted using standard communications protocols (DNP3.0, etc). When a standard protocol is used data to be transmitted must be arranged within the applicable protocol format, making use of a method to establish which data go into each message so as to be able to use it correctly by the receiver. However, IEC61850 segregates data into groups, these at the same time into classes and finally data are mapped into a given logic device within a physical element. Each IEC61850 element gains access to data, without loss of context, through a tree formed by the different data classifications. On the one hand, the CPT-D incorporates standard IEC-61850 at substation bus level through the communications protocol MMS and, on the other hand, makes use of IEC-61850 data model to shape its own internal functions. The CPT-D IEC61850 server uses IEC61850 data to shape at logic level the CPT-D internal functions that have to be visible by other substation IEDs. The CPT-D IEC61850 server features the following elements and services:

- A logic device that includes a number of logic nodes to show data of interest for other IEDs.

- Capacity to publish GOOSE messages, from GOOSE-Control-Blocks s. - Capacity to publish Buffered type Reports, from Report-Control-Blocks. - Capacity to publish Unbuffered type Reports, from Report-Control-Blocks. - Capacity to accept commands from other IEDs on IEC61850 controllable data.

IEC61850 server data model is a fixed model represented in the ICD file delivered with the relay. Said file can be configured (Modification of Data Set, ReportControlBlocks, Gooses, settings, etc) creating the CID configuration file that can be uploaded into the CPT-D in order that the configuration changes can be applied.

5.2.5 Commands sent to IEC 61850 devices Commands sent to IEC61850 bay devices will be managed by the main IEC61850 task itself owing to command singularities described in standard IEC61850, where different procedures for IED control command execution are proposed.

Chapter 5


5-4

5.3 LEDs The CPT-D features 4 LEDs to the left of the front panel:

- LED 1: CPT-D Alarm. This LED lights on when a critical CPT-D error occurs. It is normally off.

- LED 2: Time SYNC. This LED lights on when communications with the GPS clock fails. - LED 3: Coms DBC. This LED is on when communications with the DBC is not

established. - LED 4: Coms Ethernet. This LED is on when communications with the Ethernet network

fails.

5.4 Digital Inputs The CPT-D features 8 digital inputs, but they will not be operative.

5.5 Digital Outputs The CPT-D features 8 digital outputs, but they will not be operative.

CHAPTER 6

Alphanumeric Keyboard and Display

Chapter 6


6-2

6.1 Alphanumeric Keyboard and Display The liquid crystal alphanumeric display has a 4-row by 20-character matrix. It displays information about IED alarms, settings, metering, states, etc. There are 4 auxiliary function keys (F1, F2, F3 and F4) under the display. The next section explains their functions. Figure 6.1 shows the default graphic display and the function keys. Figure 6.1: Alphanumeric Display.

• Default Display As you can see in figure 6.1, the default display shows the IED model, the date and the time. During the start-up process, an icon can appear on the upper right corner of the screen (alternating between and ) to show that the different software modules that constitute the relay are being initiated (as well as first update of the real time database).

Finally, to point out that if the removable USB device is connected, the corresponding icon will appear to the right of the second line.

• Alphanumeric Keyboard The keyboard consists of 16 keys arranged in a 4 x 4 matrix. Their properties are specified next. Figure 6.2 shows the layout of this keyboard. In addition to the keys corresponding to the digits (keys from 0 to 9), there are the selection keys (↑ and ↓), the confirmation key (ENT), the escape key (ESC) and the contrast key ( ).

Figure 6.2: Keyboard Layout.



6-3

6.2 Keys, Functions and Operation Mode This section explains the functions of the keys, both the ones associated with the alphanumeric display as well as those on the keyboard.

• Keyboard and Associated Functions

Confirmation Key Key ENT (Enter) is used to confirm a selection or after changing settings.

Contrast Key Press this key to modify the contrast level of the CPT-D display.

Display Selection Keys Use the arrow keys to browse through the different options of the menus available in the CPT-D.

Escape Key The ESC key is used to quit a screen in case no settings changes are required or to quit a data screen or go back to previous menus. In any case, pressing this key the system goes back to the previous screen.

Chapter 6


6-4

When this key is pressed, you access a looped display with information about the CPT-D. The number of screens depends on the amount of separate modules installed in the CPT-D.

The first display shows information about the executable file:

• Equipment Model • UCS Software Model • UCS Software Version • UCS Software Checksum • Version of the multitask operating

system • Version of the TCP library

The second screen shows data on the CPT operative system:

• Version of the real time operative system.

• Version of the application programming interface layer.

Next screen shows data on the rest of DLL type CPT-D modules (Dynamic Link Library):

• Version of first DLL module. • Version of second DLL module. • ...

In the next screen, shows information about the status of certain of the CPT-D's internal parameters:

• The configuration’s IP address. • Size (in bytes) of the logic • Size (in bytes) of free memory • Status of the sockets: C = Central, P = Protection, M = Monitor. • 00 = Waiting for connection; 03 = Connection established



6-5

A new screen shows information on the identification number of each CPT-D software component, according to ZIV internal identification system:

• Operative system drawing number. • UCS/RTU application drawing

number. • Drawing number of the rest of DLL

type modules. Next screens show information on the checksum codes for each CPT-D software component:

• Operative system Checksum • UCS/RTU application Checksum. • Checksums for the rest of DLL type modules.

Finally, we go back to the default display, access to which can again be gained pressing ESC.

Pressing this key, while at CPT-D home screen, displays a screen requesting the password to reboot the relay. After introducing the correct password, the operator is prompted to confirm reboot, via F1 and F2 keys.

Chapter 6


6-6

6.3 Access to functions through the keyboard Pressing any key (except ESC and contrast keys), while at home screen, displays the main menu. After previous selection, a number of submenus arranged by levels are associated to this main menu. The figures below schematically represent relay menu architecture.

• Relay status This option of the main menu is used to gain access to data of the two relay network adapters, as well as data on the status of relay synchronization with an external GPS clock.

Network adapter data For each network adapter incorporated into the relay, the network adapter name, the IP address, the sub-network mask, the MAC address (hardware), the internal adapter index, the DHCP client status (Enabled or disabled) and the default gateway IP address are shown separately. These data are shown in two windows, and switching between windows is done by pressing ↓ or ↑ key. DHCP client is a network service that enables the relay to get IP addresses automatically if its network is provided with a DHCP server. Pressing ESC displays again the menu Relay status. These data are important for maintenance operations: installation of devices into the local network.



6-7

External clock information An option within the Relay status menu shows information on the external GPS clock used as a relay time synchronization source, including the status of relay synchronisation with the external clock.

• Maintenance options Access to relay maintenance operations via keyboard is restricted by the use of a specific password. Factory set password for maintenance is 0412. Users logged on as maintenance user can modify the password. The figure shows the available options.

Pressing this key, while at CPT-D home screen, displays a screen requesting the password to reboot the relay. After introducing the correct password, the operator is prompted to confirm reboot, via F1 and F2 keys.

Chapter 6


6-8

6.4 Access to IEC61850 Menu A number of screens provide information on IEC61850 communications.

These are displayed pressing key and from the CPT-D home screen. A screen similar to the one below will be displayed. It shows the relay model, application versions, active IP, and Ethernet MAC.

Pressing in this menu, displays an extended information screen: It shows Eboot versions, ID of IEC61850 communications board, Operative System version, version of the running application and whether the application is running (RUN) or in test mode (TEST).

Scrolling across the screen is possible with keys and , to display Ethernet port information: IP, MAC, Gateway and whether any connection is active.

Pressing in this menu, displays SNTP client information screen: This screen shows information about the version of the Operative System, SNTP client version, whether the server is enabled or not, the time of the CPT-D after the last synchronization followed by an i if the synchronization is incorrect or v if it is correct.

CHAPTER 7

Receiving Test

Chapter 7


7-2

7.1 General Improper handling of electrical equipment is extremely dangerous, therefore, only skilled and qualified personnel familiar with appropriate safety procedures and precautions should work with this equipment. Damage to equipment and injury to personnel can result when proper safety precautions are not followed.

The following general safety precautions are provided as a reminder:

• High magnitude voltages are present in auxiliary supply and metering circuits even after equipment has been disconnected.

• Equipment should be solidly grounded before handling or operating. • Under no circumstances should the operating limits of the equipment be exceeded

(auxiliary voltage, current, etc.). • The auxiliary supply voltage (AC or DC) should be disconnected from the

equipment before extracting or inserting any module, otherwise damage may result. The number, the type and the specific characteristics of the acceptance tests are model dependent and are detailed in the following table.

CPT-D

Preliminary Inspection “In Service” Test Ports Test LEDs Supervision Test Installation Start up

7.2 Preliminary Inspection Examine the following aspects to conduct the preliminary inspection:

• The relay is found in perfect physical condition, all of the parts are securely attached and no assembly fasteners are missing.

• The front board is perfectly centred and aligned. • The protective cover and the box are in perfect condition. • The model numbers and specifications agree with the equipment order.

7.3 In Service Test Verify the In Service/Out of Service contact closes when the auxiliary power supply voltage is removed from the equipment and opens when the auxiliary power supply voltage is restored.

!CAUTION!

Receiving Test


7-3

7.4 Configuration The CPT-D, by default, leaves the factory with defined software and configuration. Therefore, configuration by the final user is not required. IP addresses assigned by default are:

- LAN 1: 192.168.1.50 - LAN 2: 192.168.1.51

In case said IP addresses need modifying, file tcp.cfg located in CFDISK/cfg must be accessed via FTP.

7.5 Port Test A PC will be connected to the CPT-D via the system LAN and a ping to the CPT-D will be sent writing from the PC the following command: PING MMM.NNN.XXX.YYY, where MMM.NNN.XXX.YYY is the CPT-D IP address, checking that the CPT-D responds to ICMP messages generated by the PC PING programme. This network port checking procedure must be repeated for the second CPT-D network port.

7.6 LEDs Status The default configuration of user LEDs to the left of the relay front panel will be as follows:

- LED 1: CPT Alarm. LED lights up when a critical error occurs in the CPT-D. It is off under normal conditions.

- LED 2: Time SYNC. This LED lights on when communications with the GPS clock fail. - LED 3: Coms DBC. This LED is on when communications with the DBC fails. - LED 4: Coms Ethernet. This LED is on when Ethernet network communications fails.

Schemes

and Drawings

The following planes are attached

Dimension and drill hole schemes >> 4BF0100/0011 External connection schemes >> 3RX0188/0002

Chapter 7


8-4

7.7 Installation • Location The location where the Terminal Unit is to be installed should meet the following minimum conditions to ensure correct operation, long service life, ease of installation and ease of maintenance:

• Absence of dust • Absence of dampness • Absence of vibration • Adequate lighting • Easy access • Front panel in an upright and vertical position

Mounting should be in accordance with the instructions regarding installations in the dimension diagram (at the end of this Instruction Manual).

• Connection Terminal 1 should be solidly grounded to ensure disturbance filtering circuits operate properly. The wire used for grounding these terminals should be stranded 14 AWG. Ground wire length should be minimized and should not exceed 12”. The ground terminal of the enclosure located on the rear panel of the equipment should also be grounded.

ANNEX A

Protocol Implementation Conformance Statement (PICS)

Annex A


A-2

Protocol Implementation Conformance Statement (PICS) ofthe IEC 61850 communication interface in DBN

A.1 Profile CONFORMANCE Statement A.1.1 Profile Support

Profile Client Server Comments A1 Client/server N Y

A2 GOOSE/GSE Management N Y Only GOOSE (limited)

A3 GSSE N N A4 Time sync Y Y

A.1.2 T-Profile Support

Profile Client Server Comments T1 TCP/IP profile N Y T2 OSI T profile N N T3 GOOSE/GSE T profile N Y Only GOOSE (limited) T4 GSSE T profile N N T5 Time sync T profile Y Y

A.1.3 ACSI Basic Conformance Statement

Table A.1: Basic Conformance Statement

Client/ subscriber

Server/ publisher

Value/ comments

Client-server roles

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

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

SCSMs supported

B21 SCSM: IEC 61850-8-1 used – X

B22 SCSM: IEC 61850-9-1 used

B23 SCSM: IEC 61850-9-2 used

B24 SCSM: other

Annex A


A-3

Table A.2: Basic Conformance Statement

Client/ subscriber

Server/ publisher

Value/ comments

Generic substation event model (GSE)

B31 Publisher side – X

B32 Subscriber side X –

Transmission of sampled value model (SVC)

B41 Publisher side – –

B42 Subscriber side – –

c1 – shall be ‘M’ if support for LOGICAL-DEVICE model has been declared.

O – Optional M – Mandatory

A.1.4 ACSI Models Conformance Statement

Table A.3: ACSI Models Conformance Statement

Client/ subscriber

Server/ publisher

Value/ comments

If Server side (B11) or Client side (B12) supported

M1 Logical device – X

M2 Logical node – X

M3 Data – X

M4 Data set – X

M5 Substitution – –

M6 Setting group control – –

Reporting

M7 Buffered report control – X

M7-1 sequence-number – X

M7-2 report-time-stamp – X

M7-3 reason-for-inclusion – X

M7-4 data-set-name – X

M7-5 data-reference – X

M7-6 buffer-overflow – X

M7-7 entryID – X

M7-8 BufTm – X

Annex A


A-4

Table A.4: ACSI Models Conformance Statement

Client/ subscriber

Server/ publisher

Value/ comments

M7-9 IntgPd – X

M7-10 GI – X

M8 Unbuffered report control – X

M8-1 sequence-number – X

M8-2 report-time-stamp – X

M8-3 reason-for-inclusion – X

M8-4 data-set-name – X

M8-5 data-reference – X

M8-6 BufTm – X

M8-7 IntgPd – X

M8-8 GI – X

Logging

M9 Log control – –

M9-1 IntgPd – –

M10 Log – –

M11 Control – X

If GSE (B31/B32) is supported

GOOSE – X

M12-1 entryID – X

M12-2 DataRefInc – X

M13 GSSE – –

If SVC (B41/B42) is supported

M14 Multicast SVC – –

M15 Unicast SVC – –

M16 Time – X

M17 File Transfer – X

c2 – shall be ‘M’ if support for LOGICAL-NODE model has been declared. c3 – shall be ‘M’ if support for DATA model has been declared. c4 – shall be ‘M’ if support for DATA-SET, Substitution, Report, Log Control, or Time model has been declared. c5 – shall be ‘M’ if support for Report, GSE, or SV models has been declared.

M – Mandatory

Annex A


A-5

A.1.5 ACSI Service Conformance Test

Table 3: ACSI Service Conformance Statement Services AA:

TP/MC Client/

subscriber Server/

publisher Comments

Value Server (Clause 6)

S1 ServerDirectory TP X −

Application association (Clause 7) S2 Associate – X

S3 Abort – X

S4 Release – X

Logical device (Clause 8) S5 LogicalDeviceDirectory TP – X

Logical node (Clause 9) S6 LogicalNodeDirectory TP – X

S7 GetAllDataValues TP – X

Data (Clause 10) S8 GetDataValues TP – X

S9 SetDataValues TP – X

S10 GetDataDirectory TP – X

S11 GetDataDefinition TP – X

Data set (Clause 11) S12 GetDataSetValues TP – X

S13 SetDataSetValues TP – –

S14 CreateDataSet TP – –

S15 DeleteDataSet TP – –

S16 GetDataSetDirectory TP – X

Substitution (Clause 12) S17 SetDataValues TP – –

Setting group control (Clause 13) S18 SelectActiveSG TP – –

S19 SelectEditSG TP – –

S20 SetSGValues TP – –

S21 ConfirmEditSGValues TP – –

S22 GetSGValues TP – –

S23 GetSGCBValues TP – –

Annex A


A-6

Table 3: ACSI Service Conformance Statement

Services AA: TP/MC

Client/ subscriber

Server/ publisher

Comments Value

Reporting (Clause 14) Buffered report control block (BRCB)

S24 Report TP – X

S24-1 data-change (dchg) – X

S24-2 qchg-change (qchg) – X

S24-3 data-update (dupd) – –

S25 GetBRCBValues TP – X

S26 SetBRCBValues TP – X

Unbuffered report control block (URCB)

S27 Report TP – X

S27-1 data-change (dchg) – X

S27-2 qchg-change (qchg) – X

S27-3 data-update (dupd) – –

S28 GetURCBValues TP – X

S29 SetURCBValues TP – X

c6 – shall declare support for at least one (BRCB or URCB).

Logging (Clause 14)

Log control block

S30 GetLCBValues TP – –

S31 SetLCBValues TP – –

Log

S32 QueryLogByTime TP – –

S33 QueryLogAfter TP – –

S34 GetLogStatusValues TP – –

c7 – shall declare support for at least one (QueryLogByTime or QueryLogAfter).

Annex A


A-7


Services AA: TP/MC

Client/ subscriber

Server/ publisher

Comments Value

Generic substation event model (GSE) (14.3.5.3.4)

GOOSE-CONTROL-BLOCK

S35 SendGOOSEMessage MC – X

S36 GetGoReference TP – –

S37 GetGOOSEElementNumber TP – –

S38 GetGoCBValues TP – X −

S39 SetGoCBValues TP – –

GSSE-CONTROL-BLOCK

S40 SendGSSEMessage MC – –

S41 GetGsReference TP – –

S42 GetGSSEElementNumber TP – –

S43 GetGsCBValues TP – –

S44 SetGsCBValues TP – –

c8 – shall declare support for at least one (SendGOOSEMessage or SendGSSEMessage). c9 – shall declare support if TP association is available.

Transmission of sampled value model (SVC) (Clause 16)

Multicast SVC

S45 SendMSVMessage MC – –

S46 GetMSVCBValues TP – –

S47 SetMSVCBValues TP – –

Unicast SVC

S48 SendUSVMessage TP – –

S49 GetUSVCBValues TP – –

S50 SetUSVCBValues TP – –

c10 – shall declare support for at least one (SendMSVMessage or SendUSVMessage).

Annex A


A-8


Services AA: TP/MC

Client/ subscriber

Server/ publisher

Comments Value

Control (17.5.1)

S51 Select – –

S52 SelectWithValue TP – –

S53 Cancel TP – –

S54 Operate TP – X

S55 Command-Termination TP – X

S56 TimeActivated-Operate TP – –

File transfer (Clause 20)

S57 GetFile TP – x

S58 SetFile TP – –

S59 DeleteFile TP – x

S60 GetFileAttributeValues TP – x

Time (5.5)

T1 Time resolution of internal clock

10 Nearest negative power of 2 in seconds

T2 Time accuracy of internal clock T0

X T1

T2

T3

T4

T5

T3 Supported TimeStamp resolution

0.001

Nearest value of 2**-n in seconds according to 5.5.3.7.3.3

Annex A


A-9

A.2 MMS CONFORMANCE Statement A.2.1 Environmental Services

A.2.1.a MMS InitiateRequest General Parameters

InitiateRequest Client-CR Server-CR

Base F/S Value/range Base F/S Value/range InitiateRequest

localDetailCalling m m m Y proposedMaxServOutstandingCalling m m 1 or greater m Y 6

proposedMaxServOustandingCalled m m 1 or greater m Y 6 initRequestDetail m m m Y

InitiateRequestDetail

proposedVersionNumber m m Shall be 2.1 m Y 2.1

proposedParameterCBB m m See 24.2.2.2.1.1 m Y

servicesSupportedCalling m m m Y

additionalSupportedCalling c1 x c1 N

additionalCbbSupportedCalling c1 x c1 N

privilegeClassIdentityCalling c1 x c1 N

A.2.1.b MMS InitiateResponse General Parameters

InitiateResponse Client-CR Server-CR

Base F/S Value/range Base F/S Value/range InitiateResponse

localDetailCalled m m m Y negotiatedMaxServOutstandingCalling m m 1 or greater m Y 6

negotiatedMaxServOustandingCalled m m 1 or greater m Y 6 initResponseDetail m m m Y

InitiateResponseDetail

negotiatedVersionNumber m m Shall be 2.1 m Y 2.1

negotiatedParameterCBB m m See 24.2.2.2.1.2 m Y

servicesSupportedCalled m m See 24.2.2.2.1.1 m Y

additionalSupportedCalled c1 x c1 N

additionalCbbSupportedCalled c1 x c1 N

privilegeClassIdentityCalled c1 x c1 N

Annex A


A-10

A.2.1.c MMS Service Supported Conformance Table

MMS Service Supported CBB Client-CR Server-CR

realized value/ range realized value/ range

status Y getNameList Y identify Y rename N read Y write Y getVariableAccessAttributes Y defineNamedVariable N defineScatteredAccess N getScatteredAccessAttributes N deleteVariableAccess N getNamedVariableListAttributes Y deleteNamedVariableList N defineNamedType N defineNamedVariableList N

Annex A


A-11



getNamedTypeAttributes N

deleteNamedType N

input N

output N

takeControl N

relinquishControl N

defineSemaphore N

deleteSemaphore N

reportPoolSemaphoreStatus N

reportSemaphoreStatus N

initiateDownloadSequence N

downloadSegment N

terminateDownloadSequence N

initiateUploadSequence N

uploadSegment N

terminateUploadSequence N

requestDomainDownload N

requestDomainUpload N

loadDomainContent N

storeDomainContent N

deleteDomain N

getDomainAttributes Y

createProgramInvocation N

deleteProgramInvocation N

�ill� N

stop N

resume N

reset N

�ill N

getProgramInvocationAttributes N

obtainFile N

devineEventCondition N

deleteEventCondition N

getEventConditionAttributes N

Annex A


A-12



getEventConditionStatus N

getEventConditionMonitoring N

triggerEvent N

defineEventAction N

deleteEventAction N

alterEventEnrollment N

reportEventEnrollmentstatus N

getEventEnrollmentAttributes N

acknowledgeEventNotification N

getAlarmSummary N

getAlarmEnrollmentSummary N

readJournal N

writeJournal N

initializeJournal N

reportJournalStatus N

createJournal N

deleteJournal N

fileOpen N

fileRead N

fileClose N

fileRename N

fileDelete N

fileDirectory N

unsolicitedStatus Y

informationReport Y

eventNotification N

attachToEventCondition N

attachToSemaphore N

conclude Y

cancel Y

getDataExchangeAttributes N

exchangeData N

defineAccessControlList N

getAccessControlListAttributes N

Annex A


A-13



reportAccessControlledObjects N deleteAccessControlList N alterAccessControl N reconfigureProgramInvocation N

A.2.1.d MMS Parameter Conformance Building Block (CBB)

MMS parameter CBB

Client-CR Server-CR Base F/S Value/range Base F/S Value/range

STR1 o o o Y STR2 o o o Y

NEST 1 1 or greater 1 Y 6

VNAM o o o Y VADR o o o N VALT o o o Y bit 5 x x x N TPY o o o Y VLIS o c1 o Y bit 8 x x x N bit 9 x x x N CEI o i o N ACO o c4 o N SEM o c4 o N CSR o c4 o N CSNC o c4 o N CSPLC o c4 o N CSPI o c4 o N

Annex A


A-14

A.2.1.e GetNameList Conformance Statement

GetNameList Client-CR Server-CR

Base F/S Value/range Base F/S Value/range

Request

ObjectClass m m m Y

ObjectScope m m m Y

DomainName o o 24.2.2.1.1 m Y

ContinueAfter o m 24.2.2.1.1 m Y

Response+

List Of Identifier m m 24.2.2.1.1 m Y

MoreFollows m m m Y

Response

Error Type m m m Y

A.3 VARIABLE ACCESS CONFORMANCE Statement A.3.1 Supporting Productions

A.3.1.a VariableAccessSpecification Conformance Statement

VariableAccessSpecification Client-CR Server-CR


listOfVariable o o o Y

variableSpecification o o o Y

alternateAccess o o o Y

variableListName o o o Y

A.3.1.b VariableSpecification Conformance Statement

VariableSpecification Client-CR Server-CR


name o o o Y

address o o o N

variableDescription o o o N

scatteredAccessDescription o x o N

invalidated o x o N

Annex A


A-15

A.3.2 Read Conformance Statement

Read Client-CR Server-CR


Request

specificationWithResult o o o Y

variableAccessSpecification m m See 24.2.2.3.1.2 m Y

Response

variableAccessSpecification Y

ListOfAccessResult o o o Y

A.3.3 Write Conformance Statement

Write Client-CR Server-CR


Request

variableAccessSpecification m m See 24.2.2.3.1.2 m Y See

24.2.2.3.1.2 listOfData m m m Y

Response

failure m m m Y

success m m m Y

A.3.4 InformationReport Conformance Statement

InformationReport Client-CR Server-CR


Request

variableAccessSpecification m m See 24.2.2.3.1.2 m Y

listOfAccessResult m m m Y

Annex A


A-16

A.3.5 GetVariableAccessAttributes Conformance Statement

GetVariableAccessAttributes Client-CR Server-CR


Request

name o o m Y

address o o m Y

Response

mmsDeletable m m m Y

address m m m Y

typeSpecification m m m Y

A.3.6 GetNamedVariableListAttributes Conformance Statement

GetNamedVariableListAttributes Client-CR Server-CR


Request

ObjectName m m m Y

Response Y

mmsDeletable m m m Y

listOfVariable m m m Y

variableSpecification m m m Y

alternateAccess o m o N

A.4 GOOSE SERVICES A.4.1 GOOSE Conformance Statement

Subscriber Publisher Value/comment

GOOSE Services N Y

SendGOOSEMessage N Y

GetGoReference N Y

GetGOOSEElementNumber N Y

GetGoCBValues N Y

SetGoCBValues N Y

GSENotSupported N Y

GOOSE Control Block (GoCB) o Y

Annex A


A-17

A.5 Further Specification of Device Capabilities The following table lists additional items we need to know in order to setup the information exchange between clients and servers from the different participants.

Value

If Server side (B11) supported

F1 Number of buffered report control blocks 7 F2 Number of unbuffered report control blocks 7 F3 Number of log controls 0 F4 Number of client associations supported 6 F5 Number of clients that can connect and control the device 6

If Client side (B12) supported

F11 Number of buffered reports the device can subscribe to – F12 Number of unbuffered reports the device can subscribe to – F14 Number of server associations supported –

A.6 Physical Layer

Value P1 Network Type (e.g. 100BaseFX) 100BaseTX P2 Connector Type RJ45 P3 VLAN support X

Annex A


A-18

Notes:

ANNEX B

Protocol Implementation Extra Information for Testing (PIXIT)

Annex B

B-2 BCPT0906D © ZIV Aplicaciones y Tecnología, S. L. Zamudio, 2009

B.1 Introduction This document specifies the protocol implementation extra information for testing (PIXIT) of the IEC 61850 interface in DBN. Together with the PICS and the MICS the PIXIT forms the basis for a conformance test according to IEC 61850-10.

B.1.1 Contents of this document Each chapter specifies the PIXIT for each applicable ACSI service model as structured in IEC 61850-10.

B.2 PIXIT for Association Model

Description Value / Clarification Maximum number of clients that can set-up an association simultaneously 6

Lost connection detection time range (default range of TCP_KEEPALIVE is 1 – 20 seconds)

10 Seconds

Is authentication supported Y/N

What association parameters are necessary for successful association

Transport selector Y /N Session selector Y /N Presentation selector Y /N AP Title Y /N AE Qualifier Y /N

What is the maximum and minimum MMS PDU size

Max MMS PDU size : 65000 Min MMS PDU size : 2048

What is the typical startup time after a power supply interrupt More than 170 seconds

<additional items>

Annex B

B-3 © ZIV Aplicaciones y Tecnología, S.L. Zamudio, 2009 BCPT0906D

B.3 PIXIT for Server Model

Description Value / Clarification

Which analogue value (MX) quality bits are supported (can be set by server)

Validity: Y/N Good, Y/N Invalid, Y/N Reserved, Y/ N Questionable Y/ N Overflow Y/ N OutofRange Y/ N BadReference Y/ N Oscillatory Y/ N Failure Y/ N OldData Y/ N Inconsistent Y/ N Inaccurate Source: Y/ N Process Y/ N Substituted Y/ N Test Y/ N OperatorBlocked

Which status value (ST) quality bits are supported (can be set by server)

Validity: Y/N Good, Y/ N Invalid, Y/ N Reserved, Y/ N Questionable Y/ N BadReference Y/ N Oscillatory Y/ N Failure Y/ N OldData Y/ N Inconsistent Y/ N Inaccurate Source: Y/ N Process Y/ N Substituted Y/ N Test Y/ N OperatorBlocked

What is the maximum number of data values in one GetDataValues request 1000

What is the maximum number of data values in one SetDataValues request 1000

<additional items>

Annex B


B.4 PIXIT for Data set Model

Description Value / Clarification What is the maximum number of data elements in one data set

There is “no limit”. In the ICD file an estimated value of ‘1000’ is given.

How many persistent data sets can be created by one or more clients 0

How many non-persistent data sets can be created by one or more clients 0

<additional items>

B.5 PIXIT for Substitution Model

Description Value / Clarification <additional items> Not supported

B.6 PIXIT for Setting Group Control Model

Description Value / Clarification What is the number of supported setting groups for each logical device Not supported

What is the effect of when and how the non-volatile storage is updated (compare IEC 61850-8-1 $16.2.4)

Not supported

<additional items>

Annex B


B.7 PIXIT for Reporting Model


The supported trigger conditions are

integrity Y/N data change Y /N quality change Y /N data update Y/N general interrogation Y /N

The supported optional fields are

sequence-number Y /N report-time-stamp Y /N reason-for-inclusion Y /N data-set-name Y /N data-reference Y /N buffer-overflow Y /N entryID Y /N conf-rev Y /N segmentation Y /N

Can the server send segmented reports Y /N Mechanism on second internal data change notification of the same analogue data value within buffer period (Compare IEC 61850-7-2 $14.2.2.9)

Replace analogue value in pending report.

Multi client URCB approach (compare IEC 61850-7-2 $14.2.1)

Each client has its own set of URCB’s.

What is the format of EntryID It follows an internal rule based on internal reporting buffers pointers.

What is the buffer size for each BRCB or how many reports can be buffered

In this revision of the IED firmware, there is a buffer size of 20 Kbytes available for each BRCB.

Pre-configured RCB attributes that cannot be changed online when RptEna = FALSE

<data set name>

<additional items>

Annex B


B.8 PIXIT for Logging Model

Description Value / Clarification What is the default value of LogEna (Compare IEC 61850-8-1 $17.3.3.2.1, the default value should be FALSE) Not supported

What is the format of EntryID (Compare IEC 61850-8-1 $17.3.3.3.1) Not supported

If there are multiple Log Control Blocks that specify the Journaling of the same MMS NamedVariable and TrgOps and the Event Condition (Compare IEC 61850-8-1 $17.3.3.3.2)

Not supported

Pre-configured LCB attributes that cannot be changed onlie Not supported

B.9 PIXIT for Generic Substation Events Model

Description Value / Clarification What elements of a subscribed GOOSE header are checked to decide the message is valid and the all Data values are accepted? If yes, describe the conditions. For Example: destination MAC address = as configured gocbRef = valid reference, not NULL timeAllowedtoLive > 0 datSet = valid reference, not NULL goID = as defined in the SCL t = ? stNum/sqNum = see below test = FALSE (Not checked) confRev = as configured ndsCom = FALSE numDatSetEntries = matches with number of datSet members & allData members

Not supported

What is the behaviour when one subscribed GOOSE message isn’t received or syntactically incorrect (missing GOOSE) Not supported

What is the behaviour when one subscribed GOOSE message exceeds the previous time Allowed to Live (TAL) Not supported

What is the behaviour when one subscribed GOOSE message has the time Allowed to Live (TAL) to zero Not supported

What is the behaviour when a subscribed GOOSE message is out-of-order Not supported What is the behaviour when a subscribed GOOSE message is duplicated Not supported What is the behaviour when one subscribed GOOSE message exceeds the number of element expected Not supported

What is the behaviour when one subscribed GOOSE message has incorrect elements Not supported

What is the behaviour when one subscribed GOOSE message has test flag set Not supported

Annex B


B.10 PIXIT for Transmission of Sample Values Model • Not supported Compare the “Implementation Guidelines for Electrical Current and Voltage Transducers according to IEC 60044-7/8 with Digital Output according to IEC 61850-9-2; Version 1.0; as specified by ABB, Areva, Landis+Gyr, OMICRON and SIEMENS.

B.11 PIXIT for Control Model


What control modes are supported

Y/N status-only Y /N direct-with-normal-security Y/N sbo-with-normal-security Y /N direct-with-enhanced-security Y/N sbo-with-enhanced-security

Is Time activated operate (operTm) supported Y/ N What is the behaviour of the DUT when the test attribute is set in the SelectWithValue and/or Operate request

DUT doesn’t execute the Operate request but generates a CommandTermination as if command had been really executed.

What are the conditions for the time (T) attribute in the SelectWithValue and/or Operate request

Not supported

Is “operate-many” supported No Is pulse configuration supported No

What check conditions are supported Y/N synchrocheck Y/N interlock-check

What service error types are supported

Y/N instance-not-available Y/N instance-in-use Y/N access-violation Y/N access-not-allowed-in-current-state No MMS reference in part 8-1 Y/N parameter-value-inappropriate Y /N parameter-value-inconsistent Y/N class-not-supported No MMS reference in part 8-1 Y /N instance-locked-by-other-client Y/N control-must-be-selected No MMS reference in part 8-1 Y /N type-conflict Y/N failed-due-to-communications Y/N constraint failed-due-to-server-constraint

Annex B



What additional cause diagnosis are supported

Y/N Blocked-by-switching-hierarchy Y/N Select-failed Y/N Invalid-position Y/N Position-reached Y/N Parameter-change-in-execution Y/N Step-limit Y/N Blocked-by-Mode Y/N Blocked-by-process Y/N Blocked-by-interlocking Y/N Blocked-by-synchrocheck Y/N Command-already-in-execution Y/N Blocked-by-health Y/N 1-of-n-control Y/N Abortion-by-cancel Y/N Time-limit-over Y/N Abortion-by-trip

How to force a “test-not-ok” respond with SelectWithValue request? Not supported

How to force a “test-not-ok” respond with Operate request? Not supported

Which origin categories are supported? What happens if the orCat is not supported?

Categories supported: not-supported | bay-control | station-control | remote-control | automatic-bay Command isn’t executed and the response

is MMS_ Data Object Value Invalid message (we haven’t found the link between this message and ACSI messages in 8-1 part).

What is the behaviour when a direct-with-normal-security control is made? What is the behaviour when Test or Check flags are enabled?

DUT ignores all other attributes in the control data excepts ‘ctlVal’. No response is sent when a invalid orCat or the same ‘ctlVal’ value is written. Check and Test flag are ignored.

What is the behaviour when a direct-with- enhanced -security control is made? What is the behaviour when Test or Check flags are enabled?

Check flag is ignored. When the test flag is enabled the DUT sends an affirmative response but the control is not done.

Annex B


B.12 PIXIT for Time and Time Synchronisation Model


What quality bits are supported Y/N LeapSecondsKnown Y/N ClockFailure Y/N ClockNotSynchronized

What is the behaviour when the time synchronization signal/messages are lost Like the synchronized behaviour

When is the quality bit "Clock failure" set?

When the connection between the inner clock and the communication system is broken this bit is set. (It cannot be test if the DUT works properly).

When is the quality bit "Clock not synchronised” set?

The quality bit will remain set until a valid SNTP message is received. If after a time adjusted in the HMI, no other valid SNTP message is received, the quality bit will be set again.

<additional items>

B.13 PIXIT for File Transfer Model


What is structure of files and directories? IEC-61850’s proposal. Ex. TEMPLATELD1/comtrade/Osc07110919481175.cfg

Is the IETF FTP protocol also implemented NODirectory names are separated from the file name by a “/”

The maximum file name size including path (recommended 64 chars) 64 char

Are directory/file name case sensitive NOMaximum file size Depends on the maximum free IED’s memory <additional items>

Annex B


Notes:

d instruction manual

Documents