SIEMENS 6MD84 Protection Relays Digital Substation User Manual

SIPROTEC 5 IO-Box 6MD84
V9.50 and higher
Manual
C53000-G5040-C032-2

6MD84 Protection Relays Digital Substation

NOTE
For your own safety, observe the warnings and safety instructions contained in this document, if available.
Disclaimer of Liability
Subject to changes and errors. The information given in this document only contains general descriptions and/or performance features which may not always specifically reflect those described, or which may undergo modification in the course of further development of the products.
The requested performance features are binding only when they are expressly agreed upon in the concluded contract.
Document version: C53000-G5040-C032-2.01
Edition: 03.2023
Version of the product described: V9.50 and higher
Copyright
Copyright © Siemens 2023. All rights reserved.
The disclosure, duplication, distribution and editing of this document, or utilization and communication of the content are not permitted, unless authorized in writing. All rights, including rights created by patent grant or registration of a utility model or a design, are reserved.
Trademarks
SIPROTEC, DIGSI, SIGRA, SIGUARD, SIMEAS, SAFIR, SICAM, and MindSphere are trademarks of Siemens. Any unauthorized use is prohibited.
Preface
Purpose of the Manual
This manual describes the functions of SIPROTEC 5 IO-Box 6MD84.
Target Audience
Protection system engineers, commissioning engineers, persons entrusted with the setting, testing and maintenance of automation, selective protection and control equipment, and operational crew in electrical installations and power plants.
Scope
This manual applies to the SIPROTEC 5 device family.
Further Documentation

• Device manuals
  Each Device manual describes the functions and applications of a specific SIPROTEC 5 device. The printed manual and the online help for the device have the same informational structure.

• Hardware manual
  The Hardware manual describes the hardware building blocks and device combinations of the SIPROTEC 5 device family.

• Operating manual
  The Operating manual describes the basic principles and procedures for operating and assembling the devices of the SIPROTEC 5 range.

• Communication protocol manual
  The Communication protocol manual contains a description of the protocols for communication within the SIPROTEC 5 device family and to higher-level network control centers.

• Security manual
  The Security manual describes the security features of the SIPROTEC 5 devices and DIGSI 5.

• Process bus manual
  The process bus manual describes the functions and applications specific for process bus in SIPROTEC 5.

• Product information
  The Product information includes general information about device installation, technical data, limiting values for input and output modules, and conditions when preparing for operation. This document is provided with each SIPROTEC 5 device.

• Engineering Guide
  The Engineering Guide describes the essential steps when engineering with DIGSI 5. In addition, the Engineering Guide shows you how to load a planned configuration to a SIPROTEC 5 device and update the functionality of the SIPROTEC 5 device.

• DIGSI 5 online help
  The DIGSI 5 online help contains a help package for DIGSI 5 and CFC.
  The help package for DIGSI 5 includes a description of the basic operation of software, the DIGSI principles and editors. The help package for CFC includes an introduction to CFC programming, basic examples of working with CFC, and a reference chapter with all the CFC blocks available for the SIPROTEC 5 range.

• SIPROTEC 5/DIGSI 5 Tutorial
  The tutorial on the DVD contains brief information about important product features, more detailed information about the individual technical areas, as well as operating sequences with tasks based on practical operation and a brief explanation.

• SIPROTEC 5 catalog
  The SIPROTEC 5 catalog describes the system features and the devices of SIPROTEC 5.

Indication of Conformity
** This product complies with the directive of the Council of the European Communities on harmonization of the laws of the Member States concerning electromagnetic compatibility (EMC Directive 2014/30/EU), restriction on usage of hazardous substances in electrical and electronic equipment (RoHS Directive 2011/65/EU), and electrical equipment for use within specified voltage limits (Low Voltage Directive 2014/35/EU).
This conformity has been proved by tests performed according to the Council Directive in accordance with the product standard EN 60255-26 (for EMC directive), the standard EN IEC 63000 (for RoHS directive), and with the product standard EN 60255-27 (for Low Voltage Directive) by Siemens.
The device is designed and manufactured for application in an industrial environment. The product conforms with the international standards of IEC 60255 and the German standard VDE 0435.
Standards**
IEEE Std C 37.90
The technical data of the product is approved in accordance with UL.
For more information about the UL database, see ul.com
You can find the product with the UL File Number E194016.

IND. CONT. EQ.
69CA

Additional Support
For questions about the system, contact your Siemens sales partner.
Customer Support Center
Our Customer Support Center provides a 24-hour service.
Siemens AG
Smart Infrastructure – Protection Automation Customer Support Center
Tel.: +49 911 2155 4466
E-Mail: energy.automation@siemens.com
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG
Siemens Power Academy TD
Humboldtstraße 59
90459 Nuremberg Germany
Phone: +49 911 9582 7100
E-mail: poweracademy@siemens.com
Internet: www.siemens.com/poweracademy
Notes on Safety
This document is not a complete index of all safety measures required for operation of the equipment (module or device). However, it comprises important information that must be followed for personal safety, as well as to avoid material damage. Information is highlighted and illustrated as follows according to the degree of danger:
DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
◊ Comply with all instructions, in order to avoid death or severe injuries.
WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
◊ Comply with all instructions, in order to avoid death or severe injuries.
CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
◊ Comply with all instructions, in order to avoid moderate or minor injuries.
NOTICE
NOTICE means that property damage can result if the measures specified are not taken.
◊ Comply with all instructions, in order to avoid property damage.
NOTE
Important information about the product, product handling or a certain section of the documentation which must be given attention.
Qualified Electrical Engineering Personnel
Only qualified electrical engineering personnel may commission and operate the equipment (module, device) described in this document. Qualified electrical engineering personnel in the sense of this document are people who can demonstrate technical qualifications as electrical technicians. These persons may commission, isolate, ground and label devices, systems and circuits according to the standards of safety engineering.
Proper Use
The equipment (device, module) may be used only for such applications as set out in the catalogs and the technical description, and only in combination with third-party equipment recommended and approved by Siemens.
Problem-free and safe operation of the product depends on the following:

• Proper transport
• Proper storage, setup and installation
• Proper operation and maintenance

When electrical equipment is operated, hazardous voltages are inevitably present in certain parts. If proper action is not taken, death, severe injury or property damage can result:

• The equipment must be grounded at the grounding terminal before any connections are made.
• All circuit components connected to the power supply may be subject to dangerous voltage.
• Hazardous voltages may be present in equipment even after the supply voltage has been disconnected (capacitors can still be charged).
• Operation of equipment with exposed current-transformer circuits is prohibited. Before disconnecting the equipment, ensure that the current-transformer circuits are short-circuited.
• The limiting values stated in the document must not be exceeded. This must also be considered during testing and commissioning.

Selection of Used Symbols on the Device

in Morocco

OpenSSL
This product includes software developed by the OpenSSL Project for use in OpenSSL Toolkit (http://www.openssl.org/).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).

Introduction

1.1 General
The digital multifunctional protection and bay controllers of the SIPROTEC 5 device series are fitted with a powerful microprocessor. As a result, all tasks, from acquiring measurands to entering commands in the circuit breaker, are processed digitally.

Microprocessor System
All device functions are processed in the microprocessor system.
This includes, for example:

• Filtering and preparation of the measurands
• Constant monitoring of the measurands
• Monitoring of the pickup conditions for the individual protection functions
• Querying of limiting values and time sequences
• Control of signals for logic functions
• Control of open and close commands
• Recording of indications, fault data, and fault values for fault analysis
• Administration of the operating system and its functions, for example data storage, real-time clock, communication, interfaces
• External distribution of information

Binary Inputs and Outputs
Using the binary inputs and outputs, the device receives information from the system or from other devices (such as locking commands). The most important outputs include the commands to the switching devices and the indications for remote signaling of important events and states.
Front Elements
For devices with an integrated or offset operation panel, LEDs and an LC display on the front provide information on the device function and report events, states, and measured values. In conjunction with the LC display, the integrated keypad enables on-site operation of the device. All device information such as setting parameters, operating and fault indications or measured values can be displayed, and setting parameters changed. In addition, system equipment can be controlled via the user interface of the device.
Serial Interfaces
The serial interface in the front panel enables communication with a personal computer when using the DIGSI operating program. As a result, the operation of all device functions is possible. Additional interfaces on the rear are used to implement various communication protocols.
Power Supply
The individual functional units of the device are powered by an internal power supply. Brief interruptions in the supply voltage, which can occur during short circuits in the system auxiliary voltage supply, are bridged by capacitor storage (see also the Technical Data).
1.2 Properties of SIPROTEC 5
The SIPROTEC 5devices at the bay level are compact and can be installed directly in medium and high-voltage switchgear. They are characterized by comprehensive integration of protection and control functions.
NOTE
The 6MD84 I/O box has no current or voltage transformer inputs and does not support the common protection functions.
General Properties

• Powerful microprocessor
• Fully digital measured-value processing and control, from sampling and digitizing of measurands to closing and tripping decisions for the circuit breaker
• Complete galvanic and interference-free isolation of the internal processing circuits from the system measuring, control, and supply circuits through instrument transformers, binary input and output modules, and DC and AC voltage converters
• Easy operation using an integrated operator and display panel, or using a connected personal computer with user interface
• Continuous display of measured and metered values at the front
• Continuous monitoring of the measurands as well as the device hardware and software
• Communication with central control and storage devices possible via the device interface
• Battery-buffered, synchronizable clock

Modular Concept
The SIPROTEC 5 modular concept ensures the consistency and integrity of all functionalities across the entire device series. Significant features here include:

• Modular system design in hardware, software, and communication
• Functional integration of various applications, such as protection, control, and fault recorder
• The same expansion and communication modules for all devices in the family
• Innovative terminal technology with easy assembly and interchangeability and the highest possible degree of safety
• The same functions can be configured individually across the entire family of devices
• Ability to upgrade with innovations possible at all times through libraries
• Open, scalable architecture for IT integration and new functions
• Multi-layered security mechanisms in all links of the security chain
• Self-monitoring routines for reliable localization and indication of device faults
• Automatic logging of access attempts and security-critical operations on the devices and systems

Available Modules
The 6MD84 I/O box can be complemented with the following modules:

• CB202 for 3 plug-in modules, port positions: M, N, and P
• IO204 with 10 binary inputs and 8 binary outputs (4 standard relays and 4 power relays)
• IO205 with 12 binary inputs and 16 binary outputs (16 standard relays)
• IO206 with 6 binary inputs and 7 binary outputs (7 standard relays)
• IO207 with 16 binary inputs and 8 binary outputs (8 standard relays)
• IO209 with 8 binary inputs and 4 binary outputs (4 high-speed relays)
• IO212 with 8 binary inputs and 8 analog inputs 20 mA/10 V
• IO216 with 16 binary inputs with extremely robust design for special applications; fixed pickup threshold value of DC 170 V, fixed dropout threshold value of DC 132 V
• IO218 analog inputs 20 mA/10 V
• IO230 with 48 binary inputs
• IO231 with 24 binary inputs (common potential in blocks of 4 inputs), 24 binary outputs (standard relays, common potential in blocks of 8 relays)
• IO232 with 24 binary inputs and 15 binary outputs
• IO233 with 48 binary inputs; a fixed pickup threshold value of DC 105 V is valid for all binary inputs
• PS203 power supply for 2nd device row (plugged in position 7)
• PS204 redundant power supply for PS203
• ANAI-CA-4EL: 4 analog inputs 20 mA, screw terminals
• ANAI-CE-2EL: 1 analog input DC 0 V to 300 V (CH2), screw terminals

Redundant Communication
SIPROTEC 5devices maintain full communication redundancy:

• Multiple redundant communication interfaces
• Redundant and independent protocols to control centers possible (such as IEC 60870-5-103 and IEC 61850, either single or redundant)
• Redundant time synchronization (such as IRIG B, SNTP or IEEE 1588).

Basic Structure of the Function

2.1 Embedding of Functions in the Device
General
SIPROTEC 5 devices offer great flexibility in the handling of functions. Functions can be individually loaded into the device. Additionally, it is possible to copy functions within a device or between devices. The necessary integration of functions in the device is illustrated by the following example.
NOTE
The availability of certain settings and setting options depends on the device type and the functions available on the device!
Several predefined function packages that are tailored to specific applications exist for each device family. A predefined functional scope is called an application template. The existing application templates are offered for selection automatically when you create a new device in DIGSI 5.
Function Groups (FG)
Functions are arranged in function groups. This simplifies handling of functions (adding and copying). The function groups are assigned to primary objects, such as transformer, or circuit breaker.
2.2 Application Templates/Adaptation of Functional Scope
Application Template
The application template defines the preconfigured functional scope of the device for a specific use case. A certain number of application templates is predefined for each device type. DIGSI 5 automatically offers the application templates for selection when a new device is installed. The available application templates with the respective functional scope are described in more detail in 4 Applications.
The selection of the application template first predefines which function groups and functions are present in the device (see also in 2.1 Embedding of Functions in the Device).
You can adjust the functional scope to your specific application.
Adjusting the Functional Scope
Adjust the functional scope based on the selected application template. You can add, copy or delete functions, tripping stages, function blocks, or complete function groups.
In the DIGSI 5 project tree, this can be done via the following Editors:

• Single-line configuration
• Information routing
• Function settings

Siemens recommends the Single-line configuration Editor to adjust the functional scope.
Complete missing functionalities from the Global DIGSI 5 Library. Then, the default settings of the added functionality are active. You can copy within a device and between devices as well. Settings and routings are also copied when you copy functionalities.
NOTE
If you delete a parameterized function group, function, or stage from the device, all settings and routings will be lost. The function group, function, or tripping stage can be added again, but then the default settings are active.
In most cases, the adaptation of the functional scope consists of adding and deleting functions, stages, and function blocks. As previously described, the functions, tripping stages, and function blocks automatically connect themselves to the measuring points  assigned to the function group.
In few cases, it may be necessary to add a protection or circuit-breaker function group. These newly added function groups do not contain (protection) functions. You must individually load the (protection) functions for your specific application. You must also  connect the protection or circuit-breaker function group to one or more measuring points (see 2.1 Embedding of Functions in the Device). You must connect newly added protection function groups to a circuit-breaker function group (see 2.1 Embedding of  Functions in the Device).
Functions, tripping stages, function blocks, and function groups can be added up to a certain maximum number. The maximum number can be found in the respective function and function-group descriptions.
Function Points
Function points (FP) are assigned to specific functions, but not to other functions. You can find more detailed information in the description of application templates, in 4 Applications.
The device is supplied with the acquired function-point credit. Functions with function points can be loaded into the device only within the available function-point credit. The functional scope cannot be loaded into the device if the required number of points of  the functional scope is higher than the function-point credit. You must either delete functions or upgrade the function-point credit of the device.
In addition to function-point classes (10, 20, 30, 40, 50, 75, 100 to 1400) beginning with firmware version V09.20, any function-point values in the range from 0 to 5000 are supported as a credit in the device. Thus, the precise function-point credit required can  be loaded into the device by the Function- Point Manager. Alternatively, you can order classless devices with 0 points (new option beginning with V09.20) or class-bound with the required function- point class.
Extending the Function-Point Credit
You can reorder function points if the function-point credit for the device is not enough or if you have ordered a classless device with 0 points. Proceed as follows:

• etermine the function-point requirement of certain functions, for example, with DIGSI 5 or the SIPROTEC 5 Configurator.
• Create a signed license file for your device with the SIPROTEC Function-Point Manager at www.siprotecfunction-point-manager.siemens.com or order the license file from your sales partner.
• Once you have ordered the license file using the Function-Point Manager, you can download it from there directly.
• Once you have ordered the license file from your sales partner, you will receive it by e-mail or to download.
• Use DIGSI 5 to load the signed license file onto your device. The procedure is described in the Online Help of DIGSI 5.

2.3 Function Control
Function control is used for:

• Functions that do not contain stages or function blocks
• Stages within functions
• Function blocks within functions

NOTE
Simplifying functions and function control will be discussed in the following. The description also applies to tripping stage control and function block control.

Functions can be switched to different operating modes. You use the parameter Mode to define whether you want a function to run ( on) or not ( off). In addition, you can temporarily block a function or switch it into test mode for the purpose of commissioning  (parameter Mode = test). Furthermore, the state of the tripping stage can be influenced with the help of the controllable Mod in the IEC 61850 representation. The controllable Mod (in the DIGSI 5 information routing _:51 Mode (controllable)) supports the  states On, Off, Test, Relay blocked, and Test/Relay blk..
The function shows the current status – such as an Alarm – via the Health signal.
The following explains the different operating modes and mechanisms and how you set the functions into these modes. The function control is shown in Figure 2-1. It is standardized for all functions. Therefore, this control is not discussed further in the  individual function descriptions.

State Control
You can control the state of a function via the parameter Mode, the controllable Mod and the input Superordinate state.

You set the specified operating state of the function via the parameter Mode. You can set the function mode to on, off and test. The operating principle is described in Table 2-2. You can set the parameter Mode via:

• DIGSI 5
• On-site operation at the device
• Browser-based user interface
• Certain systems control protocols (IEC 61850, IEC 60870-5-103)

You can also set the setpoint operating state of the function through the controllable Mod. You can set the function mode to On, Off, Test, Relay blocked and Test/Relay blk.. The operating principle is described in Table 2-2. You can set the controllable Mod via:

• IEC 61850-8-1
• CFC

The superordinate state can accept the values On, Relay blocked Test and Test/Relay blk..
The state of the function resulting from the parameter Mode, the controllable Mod and the Superordinate state is shown in the following table. The resulting state of the function results from the combination of all sources (parameters Mode, Controllable Mod  and Superordinate state). For simplicity, the table represents only the combination of 2 sources.

Table 2-1 Resulting State of the Function

NOTE
The browser-based user interface shows an easy-to-read list of the states of all functions if they deviate from the state On.

The following table describes the possible states of a function:
Table 2-2 Possible States of a Function

that the health of the function is OK.
Relay blocked| The function is activated and operating as defined. The prerequisite is that the health of the function is OK. All outputs of indications of this function to relays are blocked.
Note:
Logics outside this function block, for example, superordinate group indications, are not affected by the blocking. Their output to a relay still leads to an activation.
Off| The function is turned off. It does not create any information. The health of a disabled function always has the value OK.
Test| The function is set to test mode. This state supports the commissioning. All outgoing infor- mation from the function (indications and, if present, measured values) is provided with a test bit. This test bit significantly influences the  further processing of the information, depending on the target.
For instance, among other things, it is possible to implement the functionality Blocking of the command relay known  from SIPROTEC 4.
| Target of the Informa- tion| Processing
Log| The indication is labeled Test in the log.
Contact| An indication routed to contact is not triggering the contact.
Light-emitting diode (LED)| An indication routed to the LED triggers the LED (normal processing)
CFC| Here, the behavior depends on the state of the CFC chart.
•  CFC chart itself is not in test state:
The CFC chart is not triggered by a status change of infor- mation with a  set test bit. The initial state of the informa- tion (state before test bit was set) is not processed during execution of the CFC chart.
•  CFC chart itself is in test state:
The CFC chart continues to process the information (indica- tion or  measured value) normally. The CFC outgoing infor- mation is provided  with a test bit. The definitions in this table apply to its continued  processing.
A CFC chart can be set to the test state only by switching the entire device to test mode.
Protocol| Indication and measured value are transmitted with set test bit, provided that the protocol supports this functionality.
If an object is transmitted as a GOOSE message, the test bit is set spontaneously and the GOOSE message is transmitted imme- diately. The receiver of the GOOSE message is automatically noti- fied of  transmitter test mode.
If an object is transmitted via the protection interface, the test bit is not transmitted. The Test state must also be transmitted as information for this state to be taken into account in the application on the receiver side. You must route the Test signal in the DIGSI 5 project tree → Device → Communication routing.
The test mode of the differential protection is dealt with sepa- rately in the application.
Test/Relay blk.| The function works as described under Test. All output information (indications) of this function which is routed to a relay is blocked.
All output information from the function (indications and, if available, measured values) is provided with a test bit.  This test bit significantly influences the further processing of the information, depending on the target.
Logics outside this function block, for example, superordinate group indications, are not affected by the blocking. If  the state of these functions allows the processing of indications with a test bit (target function in the state Test or  Test/Relay blk. ), the output information routed to a relay continues to the control of the relays.

Health
Health signals if a selected function can perform its designated functionality. If so, the health is OK. In case the functionality is only possible in a limited way or not at all, due to state or problems within the device, the health will signal Warning (limited  functionality) or Alarm (no functionality).
Internal self-monitoring can cause functions to assume the health Alarm (see 7 Supervision Functions). If a function assumes the health state Alarm, it is no longer active (indication not active is generated).
Only a few functions can signal the health state Warning. The health state Warning results from functionspecific supervision and – where it occurs – it is explained in the function description. If a function assumes the Warning status, it will remain active, that is,  the function can continue to work in a conditional manner and trip in the case of a protection function.

Not Active
The indication Not active signals that a function is currently not working. The indication Not active is active in the following cases:

• Function is disabled
• The function is in the health state Alarm
• Function is blocked by an input signal (see Figure 2-1)
• All protection-function steps are disabled via the Enable protection controllable (state = false). The indication Protection inactive is active.

2.4 Text Structure and Reference Number for Settings and Indications
Each parameter and each indication has a unique reference number within every SIPROTEC 5 device. The reference number gives you a clear reference, for example, between an indication entry in the buffer of the device and the corresponding description in the manual. You can find the reference numbers in this document, for example, in the application and setting notes, in the logic diagrams, and in the parameter and information lists.
In order to form unique texts and reference numbers, each function group, function, function block/stage, and indication or parameter has a text and a number. This means that structured overall texts and numbers are created.
The structure of the texts and reference numbers follows the hierarchy:

• Function group:Function:Stage/Function Block:Indication
• Function group:Function:Stage/Function Block:Parameter

The colon serves as a structure element to separate the hierarchy levels. Depending on the functionality, not all hierarchy levels are always available. Function Group and Stage/Function block are optional. Since the function groups, functions as well as tripping  stages/function blocks of the same type can be created multiple times, a so-called instance number is added to these elements.

EXAMPLE

The structure of the text and reference number is shown in the protection- function group Line as an example of the parameter Threshold value and the indication Pickup of the 2nd definite-time overcurrent protection stage of the function Overcurrent  protection, phases (see Figure 2-2). Only one function and one function group exist in the device. The representation of the stage is simplified.

The following table shows the texts and numbers of the hierarchy elements concerned:

| Name| Number of the Type| Instance Number
---|---|---|---
Protection function group| Line| 2| 1
Function| Overcurrent 3ph| 20| 1
Stage| Definite-time overcurrent protection| 66| 2
Settings| Threshold value| 3| –
Indication| Pickup| 55| –

The instance numbers arise as follows:

• Function group: Line 1
  1 instance, because only one Line function group exists in the device

• Function: Overcurrent 3ph 1
  1 instance, because only one Overcurrent 3ph function exists in the Line function group

• Stage: Definite-time overcurrent protection 2
  2 instances, because 2 definite-time overcurrent protection stages exist in the Overcurrent 3ph function
  (here the 2nd instance as an example)

This results in the following texts and numbers (including the instance numbers):

Line 1:Overcurrent 3-ph 1:Definite-time overcurrent protection 2:Threshold value| 21:201:662:3
Indication:| Number
Line 1:Overcurrent 3-ph 1:Definite-time overcurrent protection 2:Pickup| 21:201:662:55

The structure is simplified accordingly for parameters and indications with fewer hierarchy levels.

2.5 Information Lists
For the function groups, functions, and function blocks, settings and miscellaneous signals are defined that are shown in the settings and information lists.
The information lists merge the signals. The data type of the information may differ. Possible data types are ENS, ACD, ACT, SPS and MV.
One type is assigned to the individual data types. The following table shows the possible types:

EXAMPLE:
The following table shows the types for some data types as examples:

For further information, refer to 3.6.2 Basic Data Types.

System Functions

3.1 Indications
3.1.1 General
During operation, indications deliver information about operational states. These include:

• Measured data
• Power-system data
• Device supervisions
• Device functions
• Function procedures during testing and commissioning of the device

In addition, indications give an overview of important fault events after a failure in the system. All indications are furnished with a time stamp at the time of their occurrence.
Indications are saved in logs inside the device and are available for later analyses. The following number of indications are saved at least in the respective buffer (depending on the scope of the indications):

• Operational log 2000 indications
• Switching-device log 2000 indications
• User-defined log 200 indications

If the maximum capacity of the user-defined log or of the operational log is exhausted, the newest entries overwrite the oldest entries. If indications in the information routing of DIGSI 5 are routed to a log, then they are also saved. During a supply-voltage  failure, recorded data are securely held by means of battery buffering or storage in the flash memory. You can read and analyze the log from the device with DIGSI 5. The device display and navigation using keys allow you to read and analyze the logs on site.
Indications can be output spontaneously via the communication interfaces of the device and through external request via general interrogation. In DIGSI 5, indications can be tracked spontaneously duringonline mode in a special indication window. Indications  can be made accessible to higher-level control systems through mapping on various communication protocols.

NOTE
All indications are assigned to certain device functions. The text of each indication contains the corresponding function designation. You can find explanations of the meaning of indications in the corresponding device functions. However, you can also define  indications yourself and group them into your own function blocks. These can be set by binary inputs or CFC logic.

Reading Indications
To read the indications of your SIPROTEC 5 device you can use the on-site operation panel of the device or a PC on which you have installed DIGSI 5. The subsequent section describes the general procedure.

3.1.2 Reading Indications on the On-Site Operation Panel
Procedure
The menus of the logs begin with a header and 2 numbers at the top right corner of the display. The number after the slash signifies the number of indications that are available. The number before the slash indicates how many indications have just been selected  or shown. The end of the indication list is closed with the entry END.

Figure 3-1 On-Site Display of an Indication List (Example: Operational Indications)

Switch. device log Ground-fault log Setting-history log User log 1
User log 2
Motor-starting log
Com supervision log
Main Menu → Test & Diagnosis → Log →| Device diagnosis Security log
Communication log

To reach the desired log from the main menu, use the navigation keys of the on-site operation panel.

• Navigate inside the log using the navigation keys (top/bottom). You will find the most current indication at the top of the list. The selected indication is shown with a dark background.

Which indications can be shown in the selected log depends on the assignments in the DIGSI 5 information routing matrix or is predefined. Every indication contains date, time, and its state as additional information.
You will find information about this in chapter 3.1.5.1 General.
In some logs, you are given the option of deleting the entire indication list by softkey in the footer of the display. To learn more about this, read chapter 3.1.6 Saving and Deleting the Logs.

NOTE
No password entry is necessary to read indications from the device.

3.1.3 Reading Indications from the PC with DIGSI 5

Procedure

Switch. device log Ground-fault log Setting-history log User log 1
User log 2
Motor-starting log
Com supervision log
Online access → Device → Device information →  Logs tab →| Device- diagnosis log
Security indications
Online access → Device → Test suite → Communica- tion module →  Hardware2| Communication log

To read the indications with DIGSI 5 your PC must be connected via the USB user interface of the on-site operation panel or via an Ethernet interface of the device. You can establish a direct connection to your PC via the Ethernet interfaces. It is also possible to  access all connected SIPROTEC 5 devices via a data network from your DIGSI 5 PC.

• You reach the desired logs of the SIPROTEC 5 device using the project-tree window. If you have not created the device within a project, you can also do this via the Online access menu item.

After selecting the desired log, you are shown the last state of the log loaded from the device. To update, it is necessary to synchronize with the log in the device.

• Synchronize the log. For this purpose, click the appropriate button in the headline of the log (see the ground-fault indications example in Figure 3-2 a)).

Figure 3-2 DIGSI 5 Display of an Indication List (Example of Ground-Fault Log)

You will find additional information about deleting and saving logs in chapter 3.1.6 Saving and Deleting the Logs.
Which indications can be shown in the selected log depends on the assignments in the DIGSI 5 information routing matrix or is predefined. You will find information about this in chapter 3.1.5.1 General.

Setting Relative Time Reference

• Reference the display of log entries, if needed, to the real time of a specific entry. In this way, you determine a relative time for all other indications. The real-time stamps of events remain unaffected.

3.1.4 Displaying Indications
Displayed indications are supplemented in DIGSI 5 and on the on-site operation panel with the following information:

Table 3-1 Overview of Additional Information

Indications in| DIGSI 5 Information| Device Display Information
---|---|---
Log for operational indications and log for user-defined and switching- device indications| Time stamp (date and time), Relative time, Entry number, Function structure, Name,
Value, Quality, Cause, Number| Time stamp (date and time), Function structure, Name, Value
Log for parameter changes| Time stamp (date and time), Relative time,
Entry number, Function structure, Name, Value, Quality, Cause, Number| Time stamp (date and time), Function structure, Name, Value
Spontaneous indication window  (DIGSI 5)| Time stamp (date and time), Relative time, Indication, Value, Quality,  Additional Information| Time stamp (date and time), Fault  number, Value
Log for safety indications3| Time stamp (date and time), Indication number, Indication| Time stamp (date and time), Indication
Log for device-diagnostic indica- tions3| Time stamp (date and time), Indication number, Indication| Time stamp (date and time), Indication
Log for communication indications3| Time stamp (date and time), Indication number, Indication| Time stamp (date and time), Indication
Log for communication supervision (GOOSE)| Time stamp (date and time), Relative time, Entry number, Function  structure, Name, Value, Quality, Cause, Number| Time stamp (date and time), Function  structure, Name, Value

Overview of Displayed Quality Attributes
If values are shown on the device display or in DIGSI, the following quality attributes are different for measured values and metered values.
Table 3-2 Measured Values

angle between current and voltage if 1 of the 2 variables is missing).
Bad Reference| | | X| ≈ Value| The measured value can be inac- curate (for example, outside the frequency-tracking range).
Out of Range| | | X| > Value| The measured value exceeds the measuring range.

Table 3-3 Metered Values

Validity
Good| Invalid| Questionable
X| | | Value| The metered value is invalid.
| X| | —| The metered value was not calcu- lated.
| | X| ≈ Value| The metered value has no refer- ence.

Indication Columns
The following table shows the meaning of the individual columns in the log:

zone of the device or the query time for the motor log
Relative time| Relative time to a reference entry
Error number| Number of the error that occurred in the device. This number incre- ments continuously.
Entry number| Entry identification of buffer entries. This identification displays the sequence of buffer entries.
Indication number| Number of the indication that occurred in the device. This number increments continuously and is necessary for an analysis by Siemens.
Indication| Indication text
Function structure| Path of the signal with the signal name
Name| Signal name
Value| Current state of the command. Also pay attention to the value quality to check whether the value is up to date.
Quality| The quality of the value shows the source of the value and whether the value is up to date.
Cause| Additional information such as the cause and validity
Number| DIGSI address of the signal

3.1.5 Logs
3.1.5.1 General
Indications are saved in logs inside the device and are available for later analyses. Different logs allow categorization of indication logging based on operating states (for example, operational and fault logs) and based on fields of application.
Table 3-4 Log Overview
Log Management
Logs have a ring structure and are automatically managed. If the maximum capacity of a log is exhausted, the oldest entries disappear before the newest entries. If the maximum capacity of the fault or ground-fault log is reached, the number of the last fault is  output via the signal Fault recording buffer is full. You can route this signal in the information routing. If indications in the information routing of DIGSI 5 are routed to a log, then they are also saved. During a supply-voltage failure, recorded data are securely  held by means of battery buffering or storage in the flash memory. You can read and analyze the log from the device with DIGSI 5. The device display and the navigation allow you to read and evaluate the logs on site using keys.

Configurability of Logs
The indication capacity to be recorded in configurable logs (for example, ground-fault log) is laid down in columns of the information routing (matrix) of DIGSI 5 specifically defined for this purpose.

Procedure
To reach the information routing of your SIPROTEC 5 device, use the project- tree window. Access is only through the project:

• Open the information routing.
  Project → Device → Information routing

• Select the appropriate routing column.
  Destination → Logs → Column Ground-fault log (G)

The routing of the selected indication is done via right click.

• Select one of the options in the list box shown:
  – Routed (X)
  – Unrouted

Figure 3-3
Indication Configuration in DIGSI 5 (Example: Ground-Fault Log, Column G)
For non-configurable logs (for example, setting-history logs) scope and type of logged indications are described separately (see following chapter about logs).
3.1.5.2 Operational Log
Operational indications are information that the device generates during operation. This includes information about:

• State of device functions
• Measured data
• Power-system data

Exceeding or dropping below limiting values is output as an operational indication. Up to 2000 indications can be stored in the operational log.
Reading from the PC with DIGSI 5

• To reach the operational log of your SIPROTEC 5 device, use the project-tree window.
  Project → Device → Process Data → Log → Operational log

• The status of the operational log last loaded from the device is shown to you. To update (synchronization with the device), click the button Read log entries in the headline of the indication list (Figure 3-4 a)).Figure 3-4
  Reading the Operational Log with DIGSI 5
  Reading on the Device via the On-Site Operation Panel

• To reach the operational log via the main menu, use the navigation keys of the on-site operation panel.
  Main Menu → Indications → Operational log

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

• Using the Info softkey, you can retrieve auxiliary information on the entry depending on the context.

Figure 3-5 On-Site Display of an Indication List (Example: Operational Indications)
Deletability
The operational log of your SIPROTEC 5 device can be deleted. This is done usually after testing or commissioning the device. To know more about this, read chapter
3.1.6 Saving and Deleting the Logs.
Configurability
The indication scope of the operational log is configured in a specifically defined column of the information routing (matrix) of DIGSI 5:
Target → Log → Operational log column
Selected application templates and functions from the library bring with them a predefined set of operational indications which you can adjust individually at any time.
3.1.5.3 Setting-History Log
All individual setting changes and the downloaded files of entire parameter sets are recorded in the log for setting changes. This enables you to determine setting changes made are associated with events logged (for example faults). On the other hand, it is possible to obtain verification with fault analyses, for example, that the current status of all settings truly corresponds to their status at the time of the fault. Up to 200 indications can be stored in the setting-history log.
Reading from the PC with DIGSI 5

• To reach the log for setting changes of your SIPROTEC 5 device, use the project-tree window.
  Project → Device → Process data → Log → Setting changes
  The status of the setting-history log last loaded from the device is shown to you.

• To update (synchronization with the device), click the Read log entries button in the headline of the indication list (Figure 3-6).

Figure 3-6 Reading the Setting- History Log with DIGSI 5

Reading on the Device through the On-Site Operation Panel

• To reach the setting-history log from the main menu, use the navigation keys of the on-site operation panel.
  Main menu → Indications → Setting changes

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

Figure 3-7 Reading the Setting-History Log on the On-Site Operation Panel of the Device
Indication Categories in the Setting-History Log
For this log, there is selected information that is stored in case of successful as well as unsuccessful setting changes. The following list gives you an overview of this information.
Table 3-5 Overview of Indication Types

NOTE

• The logged indications are preconfigured and cannot be changed!
• The log, which is organized as a ring buffer, cannot be deleted by the user!
• If you want to archive security-relevant information of the device without loss of information, you must regularly read this log.
• You cannot route additional indication objects to the setting-history log.

3.1.5.4 User Log
With the user-defined log (up to 2), you have the possibility of individual indication logging parallel to the operational log. This is helpful, for example, in special monitoring tasks but also in the classification into different areas of responsibility of the logs. Up to 200 indications can be stored in the user-defined log.
Reading from the PC with DIGSI 5

• To reach the user-defined log of your SIPROTEC 5 device, use the project-tree window.
  Project → Device → Process Data → Log → User log 1/2
  The status of the user-defined log last loaded from the device is shown to you.

• To update (synchronization with the device), click the Read log entries button in the headline of the indication list (Figure 3-8 a)).

Figure 3-8 Reading the User-Defined Log with DIGSI 5
Reading on the Device through the On-Site Operation Panel

• To reach user-specific logs from the main menu, use the navigation keys of the on-site operation panel.
  Main Menu → Indications → User-defined log 1/2

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

• Using the Info softkey, you can retrieve auxiliary information on the entry depending on the context.

Figure 3-9 Reading the User-Defined Log on the On-Site Operation Panel of the Device
Deletability
The user-defined log of your SIPROTEC 5 device can be deleted. You will find details about this in chapter 3.1.6 Saving and Deleting the Logs.
Configuration of a User-Defined Log
The indication capacity of a created user-defined log can be configured freely in the associated column of the information routing (matrix) of DIGSI 5:
Target → Log → U1 or U2Figure 3-10 Indication Configuration in DIGSI 5 (Example: User-Defined Log U1/2)
3.1.5.5 Security Log
Access to areas of the device with restricted access rights is recorded in the security log. Unsuccessful and unauthorized access attempts are also recorded. Up to 2048 indications can be stored in the security log.
Reading from the PC with DIGSI 5

• To reach the security log of your SIPROTEC 5 device, use the project-tree window. The device must be in Online access.
  Project → Online access → Device → Device Information → Logs tab → Security logs
  The state of the security log last loaded from the device is displayed.

• Before this, refresh the contents by clicking the update arrows in the headline.

Figure 3-11 Reading the Security Indications with DIGSI 5
Reading on the Device through the On-Site Operation Panel

• To reach the security log from the main menu, use the navigation keys of the on-site operation panel.
  Main menu → Test & Diagnosis → Logs → Security log

• You can navigate on the on-site operation panel using the navigation keys (top/bottom) inside the displayed indication list.

Figure 3-12 Reading the Security Log on the On-Site Operation Panel of the Device
NOTE

• The logged indications are preconfigured and cannot be changed!
• This log, which is organized as a ring buffer, cannot be deleted by the user!
• If you want to archive security-relevant information of the device without loss of information, you must regularly read this log.

3.1.5.6 Device-Diagnosis Log
Concrete take-action instructions are logged and displayed in the device- diagnosis log for the following items:

• Required maintenance (for example, battery supervision)
• Identified hardware defects
• Compatibility problems

Up to 500 indications can be stored in the device-diagnosis log. In normal operation of the device, it is sufficient for diagnostic purposes to follow the entries of the operational log. This specific significance is assumed by the device-diagnosis log when the device is no longer ready for operation due to hardware defect or compatibility problems and the fallback system is active.
Reading from the PC with DIGSI 5 in Normal Operation

• To reach the device-diagnosis log of your SIPROTEC 5 device, use the project-tree window.
  Project → Online access → Device → Device information → Logs tab → Device- diagnosis log The status of the device-diagnosis log last loaded from the device is shown to you.

• Before this, refresh the contents by clicking the update arrows in the headline.

Figure 3-13 Reading the Device- Diagnosis Log with DIGSI 5
Reading on the Device through the On-Site Operation Panel in Normal Operation

• To reach the diagnosis log from the main menu, use the navigation keys of the on-site operation panel.
  Main Menu → Test & Diagnosis → Logs → Device diagnosis

• You can navigate on the on-site operation panel using the navigation keys (top/bottom) inside the displayed indication list.

Figure 3-14 Reading the Device-Diagnosis Log on the On-Site Operation Panel of the Device
NOTE

• The device-diagnosis log cannot be deleted!
• The logged indications are preconfigured and cannot be changed!

3.1.5.7 Communication Log
The logging of the respective status such as ensuing faults, test and diagnosis operation, and communication capacity utilizations is done for all hardware-based configured communication interfaces. Up to 500 indications can be stored in the communication log. Logging occurs separately for each communication port of the configured communication modules.
Reading from the PC with DIGSI 5

• Use the project-tree window to reach the communication logs of your SIPROTEC 5 device.
  Online access → Device → Test suite → Communication module

• Then select:
  J:Onboard Ethernet → Communication log
  The communication log is shown to you in the state last loaded from the device.

• Before this, refresh the contents by clicking the update arrows in the headline.

Figure 3-15 Reading the Communication Log with DIGSI 5
Reading on the Device through the On-Site Operation Panel

• To reach the communication log from the main menu, use the navigation keys on the on-site operation panel.
  Main Menu → Test & Diagnosis → Logs → Communication logs

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

Figure 3-16 Reading the Communication Log on the On-Site Operation Panel of the Device
Deletability
The communication logs of your SIPROTEC 5 device can be deleted. Read details about this in chapter
3.1.6 Saving and Deleting the Logs.
Configurability
The communication logs are not freely configurable. The entries are preconfigured.
3.1.5.8 Communication-Supervision Log
The communication-supervision log is used to log communication events.
The following events are currently logged:

• Status for each GOOSE subscription (if configured)
  A log is kept of whether the GOOSE subscription has received valid messages or not.

• Aggregated status for all GOOSE subscriptions
  The status is TRUE if at least one GOOSE subscription does not receive any valid message.

• Subscriber in simulation mode
  GOOSE messages are processed with a simulation flag. The status is TRUE if at least one GOOSE subscription processes simulated messages.

Reading from the PC with DIGSI 5

• To reach the communication-supervision log of your SIPROTEC 5 device, use the project-tree window.
  Project → Device → Process data → Logs → Com supervision log
  The status of the communication-supervision log last loaded from the device is shown.

• To update (synchronization with the device), click the button Read log entries in the headline of the indication list.

Figure 3-17 Reading the Communication- Supervision Log with DIGSI 5
Reading on the Device through the On-Site Operation Panel

• To reach the communication-supervision log from the main menu, use the navigation keys on the on-site operation panel.
  Main menu → Logs → Com supervision log

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

Figure 3-18
Reading the Communication-Supervision Log on the On-Site Operation Panel of the Device
Deletability
The communication-supervision log of your SIPROTEC 5 device can be deleted. Read details about this in chapter 3.1.6 Saving and Deleting the Logs.
Configurability
The communication-supervision log cannot be freely configured. The entries are preconfigured.
3.1.6 Saving and Deleting the Logs
Deleting the logs of the device in the operating state is unnecessary. If storage capacity is no longer sufficient for new indications, the oldest indications are automatically overwritten with new incoming events. In order for the memory to contain information about the new faults in the future, for example, after a revision of the system, a deletion of the log makes sense. Resetting the logs is done separately for the various logs.
NOTE
Before you delete the content of a log on your SIPROTEC 5 device, save the log with DIGSI 5 on the hard disk drive of your PC.
NOTE
Not all logs of your SIPROTEC 5 device can be deleted. These limitations apply especially to logs with relevance for security and after-sales (security log, device-diagnosis log, setting-history log).
NOTE
If the device executes an initial start, for example after an update of the device software, the following logs are automatically deleted:

• Operational log
• Switching-device log
• Setting-history log
• User-defined log
• Communication-supervision log
  Back up the deletable logs using DIGSI 5.

NOTE
If a ground fault is currently active, the ground-fault log cannot be deleted.
Deleting Logs on the On-Site Operation Panel

• To reach the selected log from the main menu, use the navigation keys of the on-site operation panel (example operational log):
  Main menu → Logs → Operational log

Figure 3-19 Deleting the Operational Log on the On-Site Operation Panel

• You can navigate within the displayed indication list using the navigation keys (up/down) on the on-site operation panel.

• The option to delete the entire log is offered to you in the footer of the display at the bottom left. Use the softkeys below under the display to activate the command prompts. Confirm the request to Delete.

• After being requested, enter the password and confirm with Enter.

• After being requested, confirm the Deletion of all entries with Ok.
  Deleting Logs from the PC with DIGSI 5

• To reach the selected log of your SIPROTEC 5 device, use the project-tree window (for example operational log).
  Project → Device → Process data → Logs → Operational log

3.1.7 Spontaneous Indication Display in DIGSI 5
With DIGSI 5 you have the possibility of displaying all currently transmitted indications of the selected device in a special indication window.
Procedure

• Call up the spontaneous indications of your selected device in the navigation window under Online access.

• Click Indications in the path:
  Online access → Interface → Device → Indications

• The raising indications appear immediately without you having to wait for a cyclical update or initiate the manual update.

Figure 3-20 Displaying Spontaneous Device Indications in DIGSI 5
3.1.8 Spontaneous Fault Display on the On-Site Operation Panel
After a fault, the most important data of the last fault can be displayed automatically on the device display without further operational measures. In SIPROTEC 5 devices, protected objects and even circuit breakers can be freely created and configured depending on the application (even several instances). In DIGSI 5, several spontaneous fault displays can be configured, depending on the application, with each individual one being assigned a particular circuit breaker. These displays remain stored in the device until they are manually confirmed or released by LED reset.
Configuration of a Spontaneous Fault Display with DIGSI 5

• To reach the Fault-display configuration of your SIPROTEC 5 device, use the project-tree window.
  Project → Device → Display pages → Fault-display configuration

• In the main window, all configured circuit breakers are displayed. A list of a maximum of 6 configurable display lines is offered for each circuit breaker. The activation of a spontaneous fault display occurs for each circuit breaker by selection via checkmark in the column Display.

• With the parameter (_:139) Fault-display (under Device → Parameter → Device settings) you determine whether spontaneous fault displays should be shown for each pickup or only pickups with the trip command.

Figure 3-21 Configuration of the Spontaneous Fault Display on the Device
For every display line the following display options can be selected:
Table 3-6 Overview of Display Options

as needed with auxiliary information (phases, ground, direction)
PU time| Display of the entire pickup duration of the fault
Operate indication| Display of the first function stage triggered in a fault, as needed with auxiliary information (phases)
Trip time| Display of the operate time related to the beginning of the fault (pickup start)
Fault distance| Display of the measured fault-location distance
Operate result indication| Display of the control or switching device triggered in a fault, with auxiliary information (phases) where necessary

Acknowledgment of the Spontaneous Fault Display on the Device
After faults, the last occurred fault is always displayed to you. In cases where more than one circuit breaker is configured, several stored fault displays can be present after faults, with the latest being displayed. These displays remain stored in the device until manual acknowledgment or release by LED reset. Figure 3-22 Spontaneous Fault Display on the Device
Method 1: Manual acknowledgment

• Press the softkey button Quit in the base bar of the display. The display is irretrievably closed. Repeat this step until no further spontaneous fault displays appear.

• After completion of all confirmations the last display view is showed before the faults.
  Method 2: Acknowledgment via LED reset

• An LED reset (device) causes the reset of all stored LEDs and binary output contacts of the device and also to the confirmation of all fault displays stored in the display.

You can find more details on the topic of LED reset in chapter 3.1.9 Stored Indications in the SIPROTEC 5 Device
3.1.9 Stored Indications in the SIPROTEC 5 Device
In your SIPROTEC 5 device, you can also configure indications as stored. This type of configuration can be used for LEDs as well as for output contacts. The configured output (LED or contact) is activated until it is acknowledged. Acknowledgment occurs via:

• On-site operation panel
• DIGSI 5
• Binary input
• Protocol of substation automation technology

Configuration of Stored Indications with DIGSI 5
In the Information Routing of each device set up in DIGSI 5, you can route binary signals, among others, to LEDs and output contacts.

• To do this, proceed in the project tree to:
  Project → Device → Information routing

• Right-click the routing field of your binary indication in the desired LED or binary output column in the routing range of the targets.

You are offered the following options:
Table 3-7 Overview of Routing Options

reset of the output (LED, BO) occurs automatically via the binary-signal value.
G| (latched)| X| X| | The binary signal is latched when the output (LED) is activated. To reset, a targeted confirmation must occur.
NT| (conditioned latching)| X| | | Fault indications are stored during control of the output (LED) as a function of the parameter (_: 91 :139) Fault-display. In the event of a new fault, the previously stored states are reset.
•If the fault gets terminated via a trip command from the assigned circuit breaker, the status of an indication remains as latched with the setting option with trip. Without a trip command, the status is displayed before the fault (if necessary, the status of the last fault) is restored.
•With the setting option with pickup the current indication image of a pickup gets stored. The image comprises all indications of functions that are effective in the event of tripping on the same circuit breaker, like the picked up function.
TL| (stored only with tripping)| | X| | Routing option TL (tripping, stored) is only possible for the switching object circuit breaker.
The output is saved with protection tripping. The contact remains activated until acknowledged.
Control commands are not affected. A control command
is pending above the parameterized command period until feedback has been successfully received.
Note:
You can realize the functionality of the Lockout (ANSI 86) by storing the output relay with the routing option TL.

3.1.10 Resetting Stored Indications of the Function Group
You can configure indications of individual functions as “stored” in a function group. This type of configuration can be used for LEDs as well as for output contacts. The configured output (LED or contact) is activated until it is acknowledged.
The protection and the circuit-breaker function groups contain the block Reset LED FG. The block Reset LED FG is visible only in the Information routing under the corresponding function group in DIGSI 5. You use the binary input signal >Reset LED to reset the stored LEDs in the respective function group. The configured outputs (contacts) are not reset.
3.1.11 Application Mode/Test Mode and Influence of Indications on Substation Automation Technology
With the controllable Application mode = Test or Test/Relay blk., you switch on or off the test mode for the entire device.
If the test mode of the device or of individual functions is switched on, the SIPROTEC 5 device marks indications sent to substation automation technology station control system with an additional test bit. This test bit makes it possible to determine that an indication was set during a test.
3.2 Processing Quality Attributes
3.2.1 Overview
The IEC 61850 standard defines certain quality attributes for data objects (DO), the so-called Quality. The SIPROTEC 5 system automatically processes some of these quality attributes. In order to handle different applications, you can influence certain quality attributes and also the values of the data objects depending on these quality attributes. This is how you can ensure the necessary functionality.
The following figure describes roughly the general data flow within a SIPROTEC 5 device. The following figure also shows at which points the quality can be influenced. The building blocks presented in the figure are described in more detail in the following.Figure 3-23 Data Flow within a SIPROTEC 5 Device
Supported Quality Attributes
The following quality attributes are automatically processed within the SIPROTEC 5 system.

• Validity using the values good or invalid
  The Validity quality attribute shows if an object transferred via a GOOSE message is received (valid, invalid) or not received (invalid). The invalid state can be suppressed in the receiver device by also setting a substitute value for the object that is not received (see 3.2.2 Quality Processing/Affected by the User for Received GOOSE Values). The substitute value is forwarded to the functions.
  If the device receives one of these values, it is replaced by the invalid value and thus processed further as invalid.
  If one of the detailed quality attributes (detailQual) has the value TRUE, then Validity is set to the invalid value, unless this was already done at the transmitter end.

• Test using the values TRUE, FALSE
  The Test quality attribute indicates to the receiver device that the object received via a GOOSE message was created under test conditions and not operating conditions.

• OperatorBlocked using the values TRUE, FALSE
  The OperatorBlocked quality attribute indicates whether an object transferred via GOOSE message originates from a device that is in a functional logoff state. When the sending device is switched off, the object is no longer being received and assumes the invalid state. However, since the OperatorBlocked quality was previously identified on the receiver device, the object can be treated differently at the receiving end (see 3.2.2 Quality Processing/Affected by the User for Received GOOSE Values). At the receiving end, the object may be treated like a dropped signal.

• Source using the values process, substituted
  The Source quality attribute indicates whether the object was updated in the sending device.
  You can find more detailed information in 3.7.2 Acquisition Blocking and Manual Updating.

Influencing Quality by the Operating Modes
In addition to the normal operation, the device also supports further operating modes that influence quality:

• Test mode of the device
  You can switch the entire device to test mode. In this case, all data objects generated in the device (state values and measured values) receive the quality attribute Test = TRUE.
  The CFC charts are also in test mode and all output data receive the quality attribute Test =TRUE.

• Test mode for individual functions, stages, or function blocks
  You can switch individual functions, stages, or function blocks into test mode. In this case, all data objects generated by the function, stage, or function block (state values and measured values) receive the quality attribute Test = True.

• Functional logoff of the device
  If you take the device out of operation and want to isolate it from the supply voltage, you can functionally log off the device ahead of time. Once you functionally log off the device, all data objects generated in the device (state values and measured values) receive the quality attribute OperatorBlocked =TRUE.
  This also applies to the output from CFC charts.
  If objects are transferred via a GOOSE message, the receiver devices can assess the quality. The receiver device detects a functional logoff of the transmitting device. After shutting down the sending device, the receiver device identifies that the sending device has been logged off operationally and did not fail. Now the receiving objects can automatically be set to defined states (see chapter 3.2.2 Quality Processing/Affected by the User for Received GOOSE Values).

• Switching off individual functions, stages, or function blocks
  You can switch off individual functions, stages, or function blocks. In this case, all data objects generated by the function, stage, or function block (state values or measured values) receive the device-internal quality attribute Off. The states of the inputs and measured values remain unchanged in this case; input changes are not processed. As the quality attribute Off is not provided for in communication protocol IEC 61850, the data objects are transferred with the quality attribute Invalid.

Influencing the Quality through Hardware Supervision
Supervision functions monitor the device hardware (see 7.3 Supervision of the Device Hardware). If the supervision functions identify failures in the data acquisition of the device, then all recorded data will receive the quality attribute Validity = invalid.
Influencing the Quality by the User
You can influence the processing of data and their quality differently. In DIGSI 5, this is possible at the following 3 locations:

• In the Information routing editor for external signals from GOOSE connections
• In the CFC chart
• In the Information routing editor for binary input signals of device-internal functions

The following chapters describe in more detail the options regarding this influence as well as the automatic quality processing.
If a GOOSE connection is the data source of a binary input signal of a device- internal function, you can influence processing of the quality at 2 locations: at the GOOSE connection and at the input signal of the function. This is based on the following: A GOOSE date can be distributed within the receiving device to several functions. The GOOSE connection setting (influence) affects all functions. However, if different functions require customized settings, these are then set directly at the binary input signal of the function.
3.2.2 Quality Processing/Affected by the User for Received GOOSE Values
The properties of quality processing have changed with the introduction of GOOSE Later Binding. You can find information about the former quality processing in Previous Quality Processing/Affected by the User for Received GOOSE Values, Page 62.
In the Information Routing Editor, you can influence the data value and quality of all data types. The following figure shows the possible influence using the example of a DPC data type. All setting options are effective for the device receiving the data.

• In the DIGSI 5 project tree, double-click Information Routing.
• Select either the desired signal in the External Signals group or the signal of a function activated via the GOOSE column.
• Open the Properties window and select the Processing Quality Attributes sheet.

Figure 3-24 Influence Option When Linking a DPC Type Data Object
Depending on the selected data type of the object, various selection options are offered to you for the Safe state item in the Common settings section. At this point, you select the manually updated values that allow a safe operating state as soon as the data access via the communication path is disturbed.

• Select the property for the selected data object.

You can also set the Advanced quality attributes of the data object for GOOSE Later Binding.
The following figure shows the advanced quality attributes using the example of a DPC data type.

• Open the Properties window and select the Advanced quality attributes sheet.

Figure 3-25 Advanced Quality Attributes for GOOSE Later Binding
With the following advanced quality attributes, you can filter the transmitted GOOSE indications and check and set their quality. The values that have been adapted, if necessary, are forwarded to the receiver.
For the tests, you can select from the following setting options depending on the data type.
Table 3-8 Value Definitions

valid to the application as soon as communication disturbance occurs.
Keep value| The disturbed quality attribute is overwritten with good and the received value is forwarded as valid to the application. If no value was received, the output value is assumed being in safe state.
Keep last valid value| If an invalid quality attribute is received, the last valid value is forwarded to the application. If no value has yet been received, the output value is assumed being in safe state.
Set value to “false”| Applies only to Boolean communication objects. Every invalid quality attribute causes the valid value false to be forwarded to the application.
Set value to “true”| Applies only to Boolean communication objects. Every invalid quality attribute causes the valid value true to be forwarded to the application.

These settings of the Advanced quality attributes apply to the advanced quality attributes listed below. The selection can vary depending on the data type.Figure 3-26
Value Definition of a Data Object of the SPS Type
You can also forward the quality attributes unchanged. To do this, you must mark the Keep flag check box.
Functional Logoff by Operator Blocked
You have set the Operation mode to Device logoff = true in the transmitting device. As a result, every indication issued from the functions and subject to Device logoff is transmitted with the quality information operator blocked and Validity = good. The receiver recognizes this for this indication and reacts according to the settings (Table 3-8). A different quality processing can take place only once you have set the Operation mode to Device logoff = false in the transmitting device.
Communication Outage
There is communication disturbance (time allowed to live) between the transmitter and the receiver indicated by the transmitter. The indication is set in accordance with the settings (Table 3-8).
Invalidity
The transmitting device sends this indication with the quality information Validity = invalid. The receiver recognizes this for this indication and reacts according to the settings (Table 3-8).
Questionable
The transmitting device sends this indication with the quality information Validity = questionable. The receiver recognizes this for this indication and reacts according to the settings (Table 3-8).
Test Mismatch
The transmitting device or the function in the transmitting device that issues this indication is in test mode. As a result, the indication is transmitted with the quality information test. The receiving function block recognizes this for this indication and reacts, depending on its own test-mode state (specified in IEC 61850-7-4 Annex A), according to the settings (Table 3-8).
NOTE
Follow the sequence of tests. First, the Functional logoff by operator blocked is tested. Then comes Communication outage and so on. If a case is recognized as active, the test chain is canceled with the configured setting for the active case.
In the case of Invalidity, the tests are first performed for Functional logoff by operator blocked (not applicable) and then for Communication outage (not applicable) and canceled with the configured action for Invalidity.
If an indication is routed into the log, manual updating of a value is also logged based on the conditions listed above and on the reason for the manual update. Manually updating a value based on the conditions listed above causes a change in the Health Warning function block, inherited up to Device health (specified in IEC 61850-7-4).
Keep Flag
The quality attributes and values indicated by the transmitter are accepted without change. Quality processing must be performed by the user via a logic diagram. The outputs of the logic diagram following the userspecific quality processing can be connected to the function-block inputs as before.
Data Substitute Values
Depending on the data type, different data substitute values must be used.

The directional information is manually updated with unknown if the option Apply safe state value, Set value to “false”, and Set value to “true” are selected; or maintain the received value with the options Keep value or Keep last valid value selected.
PhsA, phsB, phsC, and neut are manually updated with the same value just like how the general value is set.)
BAC, APC| mxVa I| Floating-point range and range of values according to IEEE 754 (single precision)
BCR| actVal| —263 to 263— 1
CMV| mag, ang| Floating-point range and range of values according to IEEE 754 (single precision)
DPC, DPS| stVal| 0, 1, 2, 3 (intermediate-state, off, on, bad-state)
INC| stVal| —2 147 483 648 to 2 147 483 647
INS| stVal| —2 147 483 648 to 2 147 483 647
ISC, BSC| valWTr.posVal| —64 to 64
valWTr.translnd| 0 (False), 1 (True)
SPC, SPS| stVal| 0 (False), 1 (True)
MV| mag| Floating-point range and range of values according to IEEE 754 (single precision)

For controllable types, the following substitute values apply in addition to the settable state values or measured values:
ctlNum = 0
stSeld = False
origin.orIdent = Substituted by quality processing
origin.orCat = AUTOMATIC_BAY
Previous Quality Processing/Affected by the User for Received GOOSE Values
In the Information Routing editor, you can influence the data value and quality of all data types. The following figure shows the possible influence using the example of a DPC data type.

• In the DIGSI 5 project tree, double-click Information Routing.
• Select the desired signal in the External Signals group.
• Open the Properties window and select the Processing Quality Attributes sheet.

Figure 3-27 Influence Option When Linking a DPC Type Data Object
The setting options work for the device receiving the data.

Quality Attribute: Validity

The validity values reserved and questionable are replaced at the receiving end by the invalid value.
• Check box is not set.
• Check box is set and receipt of Validity = good| The validity attribute and data value are forwarded without change.
Check box is set and receipt of Validity = invalid is set (also applies to values reserved and ques-tionable).|  The validity attribute is set to good and processed further using this value. is set (also applies to values reserved and ques-tionable).
• The data value is set to the defined substitute value and processed further using this substitute value.
Quality Attribute: OperatorBlocked (opBlk)

• Check box is not set.
• Check box is set and received OperatorBlocked = FALSE| The OperatorBlocked attribute and data value are forwarded without change.
Check box is set and received OperatorBlocked = TRUE| • The OperatorBlocked attribute is set to FALSE and processed further using this value.
• The data value is set to the defined substitute value and processed further using this substitute value.
Interaction of the Quality Attribute Validity and OperatorBlocked

OperatorBlocked check box is set and receipt of OperatorBlocked =
TRUE| Regardless of whether the validity check box is set or not, and regardless of the current validity, the validity attribute is set to good and the substitute value of the OperatorBlocked data object is set. That is, the OperatorBlocked settings overwrite the Validity settings.
OperatorBlocked check box is not set and receipt of
OperatorBlocked = TRUE| The OperatorBlocked attribute remains set and is forwarded.
If the Validity check box is set and the receipt of validity = invalid is set, the respective data object substitute value is used.
For continued signal processing and influence, it must be taken into account that in this configuration thedata object substitute value for validity = invalid is set, but the quality attribute  peratorBlocked is not
yet set.

3.2.3 Quality Processing/Affected by the User in CFC Charts
In DIGSI 5, you can control the quality processing of CFC charts. In the project tree, you can find the CFC building block (see the following figure) under Device name →, Settings → Device settings in the editor:Figure 3-28 Influencing CFC Quality Handling in DIGSI 5
With the CFC chart quality handling parameter, you control whether you want to influence the quality of CFC charts in a Manual or Automatic (default setting) manner.
If you select Manual, the quality attribute of the CFC chart is always valid regardless of the quality of individual signals (Validity = good)!
Only the Test quality attribute of the CFC chart is processed. If the device is in test mode or the input TEST of the CHART_STATE CFC building block is set, the quality attribute of the CFC chart is set to Test.
If you select Automatic, the quality processing of the CFC charts is influenced as follows:
In the case of CFC charts, a distinction has to be made between the general quality processing and certain CFC building blocks that are specifically designed for quality processing.
Most of the CFC building blocks do not have an explicit quality processing. For these building blocks, the following general mechanisms shall apply.
Quality Attribute: Validity
If one invalid signal is received in the case of CFC input data, then all CFC output data will also be set to invalid if they originate from building blocks without explicit quality processing. In other words, the quality is not processed sequentially from building block to building block but the output data are set globally.
This does not apply to CFC output data that originate from building blocks with explicit quality processing (see next section).

Quality Attribute: Test

CFC chart is in normal state.| CFC input data with the Test = TRUE attribute are ignored. When the CFC chart is executed, then the data value that was used before the Test = TRUE attribute is used. The quality of this old value is also processed.
This means that on the output side, the attribute Test = FALSE.
CFC chart is in Test 1)  state.| If the CFC chart is executed, then the attribute Test = TRUE is set for all data leaving the CFC chart. This does not depend on whether the data are formed via CFC building blocks with or without quality processing.

1)A CFC chart can be switched to the test state by switching the entire device to test mode or the input TEST of the CFC building block CHART_STATE is set.

Quality Attribute: OperatorBlocked

CFC chart is in normal state.| In CFC charts for incoming data, the OperatorBlocked attribute is ignored.
CFC chart is in functionally logged off 1) state .| In CFC charts for incoming data, the OperatorBlocked attribute is ignored. All CFC output data are labeled as functionally logged off.

1)This state only occurs if the device is functionally logged off. In this case, the quality attributes of all CFC outputs are labeled as functionally logged off.
Quality Processing Building Blocks (Condition Processing)
The first 3 building blocks (x_SPS) process the quality automatically according to the stated logic. The other building blocks are used to isolate the quality from a data object and add them back after separate logical processing.

OR_SPS AND_SPS
NEG SPS
—| The building blocks also process the supported quality attributes according to their logic. The following tables describe the logic using input values in connection with the quality attribute Validity. The input values are 0 or 1, the quality attribute Validity can have the value good (=g) or i nva7 i d(ai).
x = placeholder for the input value and quality attribute Validity
OR_SPS
A (Value, Attribute)| B (Value, Attribute)| Q (Value, Attribute)
0, i| 0, x| 0, i
0, g| 0, g| 0, g
1,g| x, x| 1,g
1,i| 0,x| 1, i
1,i| 1,i| Li
The output thus has the logica value 1 with Validity = good as soon as at least 1 input has the logical value 1 with Validity = good. Otherwise, the inpu s are treated according to the OR operation and the INVALID bit is OR- gated for the quality.
AND_SPS
A (Value, Attribute)| B (Value, Attribute)| Q (Value, Attribute)
0, g| x, x| 0, g
O,i| 1,x| 0,i
1,i| 1,x| 1, i
1,g| 1,g| 1,g
The output thus has the logical value 0 with Validity= good as soon as at least 1 input has the logical value 0 with Validity = good. Otherwise, the inputs are treated according to the AND operation and the INVALID bit is OR- gated for the quality.
NEG_SPS
A (Value, Attribute)| Q (Value, Attribute)|
0,i| 1, i|
0,g| 1,g|
1, i| 0,i|
1,g| 0,g|
SPLIT_DPS
SPLIT_DPS
SPLL XMV| The building blocks isolate the data value and quality of a data object.
The requirement is that the quality is available from the input end. This is the case if the building block is interconnected with CFC input data, or is connected downstream with a quality processing building block (x_SPS). In other cases, the CFC editor does not allow a connection.
SPL1T_Q| The building block performs binary separation of the quality into good, bad (= i nval to), test, off and Opera torelocked.
These 5 attributes can then be processed individually in a binary operation. The building block must be connected downstream to a SPLIT (DO) building block.
BUILDQ| The building block enters a binary value for good and bad (= invalid) in each quality structure. Thus, with this building block the quality attributes good and bad (=invalid) can be set explicitly, for example, as the result of a monitoring logic. All other quality attributes are set to the default state, for instance, Test = FALSE. If, for example, the entire CFC chart is in the test state (see Quality Attribute: Test Under General Processing), this default status can again be overwritten on the CFC output side.
The building block is normally connected downstream to a BUILD(DO) building block.
BUILD_ACD
BUILD_ACT
BUILD_BSC
BUILD_DPS
BUILD_ENS
BUILD_SPS
BUILD_XMV| These building blocks merge data value and quality. The building- block output is generally used as a CFC output.
Generally, the BUILD_Q building block is connected upstream from these building blocks.

CFC charts have a standard behavior in the processing of signals. If an input signal of the CFC chart has the quality invalid, all output signals of the CFC chart also get the quality invalid. This standard behavior is not desirable in some applications. If you use the building blocks for quality processing, the quality attributes of the input signals in the CFC chart are processed.

EXAMPLE: Switchgear Interlocking via GOOSE
The following conditions apply to the example:
• The interlocking condition for switchgear interlocking protection is stored in the device as a CFC chart.
• The removed device sends the release signal for the interlocking condition via a GOOSE telegram.
If the communication connection has been interrupted, the release signal (GOOSEStr) incoming via the GOOSE telegram gets the quality invalid. If the CFC chart obtains an invalid input signal, there are the following possibilities: The last signal valid before the communication interruption is used (quality = good) or a substitute data value with the quality good is used (True, False).
To do this, you have to create a separate CFC chart in addition to the interlocking plan of the switchgear interlocking. Use the building blocks for quality processing in a separate CFC chart. With the SPLIT_SPS building block, split the input signal (data type = SPS) into data value and quality information. You can then continue to process these signals separately in the CFC chart. Use the quality information as an input signal for a BUILD_SPS building block and assign the quality good to the signal. You obtain an SPS signal as a result, with the quality good. You can use this to process release messages correctly. You can process the release messages with the quality good in the CFC chart of the actual interlocking. Therefore, the release signal for a switch illustrated in the interlocking logic is available as a valid result with the quality good. The following figure shows an example of the CFC chart with the building blocks for quality processing:

Figure 3-29 CFC Chart with Building Blocks for Quality Processing (Switchgear Interlocking via GOOSE)
If you do not want to convert the invalid release signal to a valid signal, as described, during the communication interruption, you can also assign a defined data value to the release signal. Proceed as follows: With the SPLIT_SPS building block, split the input signal (data type = SPS) into data value and quality information. Link the VALID output of the SPLIT_SPS building block with the data value of the input signal (AND gate). This way, you can set the value to a non-risk state with the valid input signals. In the example, the output of the CFC chart is set to the value FALSE when the input signal is invalid.

3.2.4 Quality Processing/Affected by the User in Internal Device Functions
Figure 3-30 provides an overview for processing the quality of data objects within a device-internal function.
A function can receive internal data or input data that is routable by the user (binary input signal or double commands). The respective quality attributes supported are evaluated by the function on the input side. The attributes are not passed through the specific algorithm/the specific logic of the function. The output data are supplied with a quality that is specified by the function state and device-operating mode.

NOTE Take into account that pickup of chatter blocking (see chapter 3.7.1 Signal Filtering and Chatter Blocking for Input Signals) sets the corresponding Validity attribute to invalid.

Figure 3-30 Overview for Processing Quality within an Internal Function

Internal Input Data
The quality processing is automatic for internal input data.

• If invalid, the function health is set to Alarm and the function is reset.
Causes for invalid internal data are, for example:
• The frequency operating range of the device was left.
• The device is not calibrated.
• The A/D converter monitoring identified an error.

Routable Binary Input Signals (SPS Data Type)
Figure 3-31 shows the possible sources for connecting a binary input signal. Depending on the source, different quality attributes can be set:

• CFC chart: See description in chapter 3.2.3 Quality Processing/Affected by the User in CFC Charts
• GOOSE connection: See description in chapter 3.2.2 Quality Processing/Affected by the User for Received GOOSE Values
• Device hardware: No quality attributes are set and supported.

Figure 3-31 Sources for Connecting a Binary Input Signal
For this signal type (SPS), you can influence the processing of the quality, see overview in Figure 3-30.
The following figure shows the possible influence on a binary input signal of a protection stage.

• In the DIGSI 5 project tree, double-click Information routing.
• In the operating range, select the desired binary input signal.
• In the Properties window, select the Details entry. There, you will find the item Processing quality attributes.

Figure 3-32 Influence Options for a Binary Input Signal (SPS Input Signal)

Quality Attribute: Validity

The Validity attribute can have the values good or invalid (reserved and questionable were already replaced at the input end of the device by the value invalid).
The input signal source is invalid.| The current data value of the source signal is ignored. You can select between the following options:
• Further process last valid data value of the source signal (this is the default setting with only a few exceptions)
• Set the binary value to be processed further to 0.
• Set the binary value to be processed further to 1.
This configuration option is necessary to satisfy different applications.
The function health switches to Warning.
The input signal source is good.| The source signal data value is processed further.

Quality Attribute: Test

• The input signal source and processed function are in test state.
• The input signal source is not in test state and the function to be processed is in test state.| The source signal data value is processed further.
---|---
The input signal source is in a test state and the function to be processed is in normal state.| The data value of the source signal is ignored. You can select between the following options:
• Further processing of the last valid source signal data value, before the source switches to the test state (that is the default setting)
• The binary value to be processed further is set to 0.
• The binary value to be processed further is set to 1.
This configuration option is necessary to satisfy different applications.

Quality Attribute OperatorBlocked
The quality cannot be influenced at this position and does not lead to a response within the logic

Output Data
The quality is not processed through the actual algorithm/logic of the function. The following table displays the conditions required to set the quality of output signals of a function.

Functional state = Test (thus, result of device operating mode = Test or function mode = Test)| Unchanged| Test = TRUE| Test = TRUE
Functional state = Off
(thus, result of device operating mode = Off)| Function-specific, corresponding to the definition for switched off| Validity = good| Validity = invalid
Function health = Alarm
(for example, result of invalid receive data)| Function-specific, corresponding to the definition for reset| Validity = good| Validity = invalid
Device operating mode = functionally logged off| Unchanged| Validity = good
OperatorBlocked = TRUE| Validity = good
detailQual = oldData
OperatorBlocked = TRUE

3.3 Trend Recorder
3.3.1 Overview of Functions
Trend recorders are used for long-term recording and monitoring the following processes or measurement:

• Voltage change within tolerance ranges that can be set using parameters
• Frequency change within tolerance ranges that can be set using parameters
• SPS-binary change
• Flicker measurement

3.3.2 Structure of the Function
The Trend recorder function is not preconfigured at the factory. Within the Recorder function group, the Trend recorder can be operated a maximum of 2 times.

Figure 3-33 Structure/Embedding of the Function

3.3.3 Function Description
The trend recorder ensures capture and long-term supervision of frequency and voltage when the voltage and frequency change. If a change occurs in the measurand with respect to the last captured RMS value during the parameterized measuring interval, and this change exceeds the set tolerance range, the new RMS value is recorded.

Figure 3-34 Operation of the Trend Recorder, Voltage Interruption

For the parameterization, specify a maximum memory capacity for the storage of recordings. The trend recorder is organized as a ring buffer. When the memory is filled completely, the oldest data are overwritten automatically.

Mode
The trend recorder operates only if the Mode is set to on.
Recording is interrupted if Mode is set to off during recording. Recording starts again if Mode is set again to on.

NOTE
In the mode off, the continuous recorder no longer records any measured values, but continues to record device statuses (time jumps, modes on/ off, as well as disconnection and recovery of the supply voltage).
PQDif recordings are still generated, even though the trend recorder is set to the mode off. It is recommended to delete the recorder instance in case of long-term non-use.

Ring-Buffer Mode
With the trend recorder, data is stored on the flash memory in blocks. The new data of the last 10-minute interval are available every 10 minutes. If, while recording of a record, the device determines that the free space remaining on the recorder partition is too small, the oldest data block is erased automatically. During this process, complete time segments in the specified grid are always lost.

Disconnection and Recovery of Supply Voltage

NOTE
If the supply voltage of the device is disconnected intentionally or by mistake, measuring gaps appear for the period of the disconnection. However, the recorded data remains stored and can be read after recovery of the supply voltage.

3.3.4 Application and Setting Notes
Settings of the Trend-Recorder Function

Figure 3-35 Settings of the Trend Recorder Function (as an Example)

Parameter: Flash-Memory Size
• Recommended setting value (_:10111:161) Flash-memory size = 10 MB
With the parameter Flash-memory size, you specify a maximum memory capacity of the trend recorder on the mass storage.
If the flash memory becomes full while recording new fault records, the device automatically deletes the oldest data in order to continue recording (ring buffer).
The record time is limited by the set flash-memory size and the number of events occurring.

NOTE If you change the capacity of the recorder or delete a recorder instance, the flash memory of the device is reorganized and all recordings of the device – not just those of the changed recorder – are automatically and irrevocably deleted.
Before this, save your recordings by exporting them manually in DIGSI 5 or archiving them in SICAM PQS. Then, delete your recordings in DIGSI 5 to avoid inconsistencies between new and old recordings.

3.3.5 Settings

General
_:27311| General: Mode| | •off
•on| on
Control
:15361:161| Trend 1:Flash-memory size| | 2 MB to 25 MB| 10 MB

3.3.6 Information List

Binary 10
:2731 :51| General: Mode (controllable)| ENC| C
:2731 :52| General: Behavior| ENS| 0
:2731 :53| General: Health| ENS| 0
Binary 10
:1 5361:322| Trend 1: Recorder formatted| SPS| 0

3.4 Protection Communication
3.4.1 Overview
The Protection communication includes all functionalities necessary for data exchange via the protection interface (PI).
Devices that communicate with each other via protection interfaces form a device combination. A device combination consists of 2 to 6 devices. The devices communicate via point-to-point connections (protection connections). In this case, a device has only one connection to another device via a protection interface (PI).
With a 2nd protection interface, you can establish a connection to another device or a redundant connection to the same device. With their protection connections, the devices form a protection topology in the form of a redundant ring (ring topology) or as a chain structure (chain topology).

Within a device combination, the point-to-point connections can have different bandwidths. Depending on the bandwidth, a certain amount of binary information and measured values can be transmitted bidirectionally between the devices. The connection with the lowest bandwidth defines the amount of binary information and measured values.
The following information is important for protection communication and is transmitted additionally. You cannot change this information:

• Topology data and values are exchanged for monitoring and testing the connection and displayed on the device or with DIGSI 5.
• Protection data and measured values, such as line differential protection data or binary data of the teleprotection schemes for distance protection and ground-fault protection are transmitted.
• The time synchronization of the devices is possible directly via the connection, whereby a device of the protection topology assumes the role of the timing master.
  The point-to-point connection between the devices is continuously monitored for data faults and failure and the signal-transit time of the data is measured.

The protection communication is typically used for line differential protection and with the teleprotection schemes for distance protection and ground-fault protection. In SIPROTEC 5, you can configure the protection communication in all devices and use it for further protection applications. At the same time, any binary information and measured values can be transferred between the devices.

NOTE
The protection communication is compatible with the successor versions from firmware version V04.00 and higher.

3.4.2 Protection Communication in the Overall System
The following figure illustrates the interaction of protection communication, protection function groups, and communication modules. The Protection communication is integrated as follows in the overall system:

Figure 3-39 Protection Communication in the Overall System

If protection functions want to use the protection interfaces, their superordinate protection function group, for example, the FG Line 1, must be connected to a Protection communication function group. With this connection, each protection function in the FG Line 1 can use protection communication.
In addition, a connection must be configured between the logical protection interface in the FG Protection communication and a channel on the physical communication module. The physical communication module must support the protection-interface protocol.
The following chapters describe the configuration of the connections.

3.4.3 Function Description
Type of Protection Communication
The protection communication in a device can be either type 1 or type 2. The following table shows the typical applications:

Type 1
Application during use of Line differential protection| With type 1, the Line differential protection function is the primary application. This application requires the greatest portion of the bandwidth, so that with type 1 the quantity of customer-pecific remote data available is lower. This becomes noticeable with a 64 kBit/s protection connection via a G703.1 or X21 interface. If a multiple-end line differential protection application is realized, all protection communications in the devices must be of type 1. A maximum of 6 line ends (devices) is possible. If the Line differential protection and Teleprotection scheme functions are to operate in parallel in the device, the bit rate must not be less than 512 kBit/s!
Type 2
Application without use of Line differential protection| Type 2 provides considerably more bandwidth for customer-specific remote data, as the line differential protection application is not used in this example. The transmission of protection data and other data, such as measured values as well as the teleprotection scheme, is  redominant here.
Using type 2 protection communication, a maximum of 6 devices can be connected to one another and different device types (for example, 6MD, 7VK, 7SA, and 7SJ) can exchange data.

NOTE
In the case of devices with the Line differential protection function, for instance 7SD and 7SL, protection communication type 1 is preset in the application templates of the devices. Type 2 is preset in the application templates for other devices, and is used for other data transmission.
Type 1 and type 2 protection communication do not work together in pairs via a protection function.
The protection interfaces (PI) establish a direct point-to-point connection between devices via different communication media. Devices connected to one another via protection interfaces form a protection topology. See following figure.

Figure 3-40 Data Exchange between 4 Devices with Protection Communication of Type 1 or Type 2 in a Protection Topology

Device Combination with 2 Devices: Simple or Redundant Transmission
In a device combination with 2 devices, one protection communication with a protection interface is required per device to establish a protection connection (see next figure).
The most frequent application is the two-line-end differential protection (the protection communication is of type 1) or the point-to-point exchange of data between 2 devices (the protection communication is of type 2), as performed by protection transmission devices.

Figure 3-41 Data Exchange for 2 Devices, Each with Protection Connection

NOTE
The index describes the consecutive numbering of the devices in a device combination (see parameter (_:5131:101) Local device is device).
A maximum of 2 protection interfaces per FG Protection communication are possible in one device, see following figure. If the Protection communication function groups are connected to each other in the devices via 2 protection connections of the same type, this results in 100 % redundancy regarding the transmission route. The devices then search for the communication connection with the highest bandwidth (for example, optical fiber). If this protection connection fails, the system switches over automatically to the 2nd protection
connection until the 1st protection connection is available again. As the protection connection with lower bandwidth defines the maximum amount of transferable information, the same information is exchanged via both protection connections. One application of this is line differential protection routed via a redundant communication connection. Both protection communications in the device are then of type 1.

Figure 3-42 Data Exchange for 2 Devices, Each Having 2 Protection Connections, Redundant Transmission Route

Device Combination with more than 2 Devices: Ring or Chain Topology
When there are more than 2 devices, a communication chain (chain topology) or a communication ring (ring topology) can be established. An arrangement with a maximum of 6 devices is possible.
To enable the devices in their device combination to communicate with one another, all devices must contain the FG Protection communication of the same type. The devices automatically detect the type of topology and their position within this topology.
A distinction is made between the following types of topology:

• Chain topology
• Ring topology

The chain topology is shown in the following figure.
This configuration shows that the indexing of the devices does not have to correspond to the order in the communication chain.

Figure 3-43 4 SIPROTEC Devices in a Chain Topology

The ring topology is shown in the following figure.
The communication ring has the advantage over the communication chain that the entire communications system and, for example, the Line differential protection function also works if one of the communication connections fails or if any desired device in the device combination is taken out of operation.
For more information, refer to 3.4.5.5 Setting Notes for the Device Combination.
The devices detect failure or logging off, and switch over automatically to the remaining transmission routes.
The following figure shows, for example, a four-line-end differential- protection application if all FGs Protection communication are of type 1 in the devices. A typical application with protection communications of type 2 is the exchange of indications and measured values between 4 devices, for example, between switchgears, whereby the protection connection can occur via different communication media. This is the application for a protection-data transmission device.

Figure 3-44 4 SIPROTEC Devices in a Ring Topology

NOTE If a connection fails in the ring topology, this configuration continues to function as a chain topology. In a ring topology, any device can be logged off from the device combination, for example, during inspection works at a line end without current flow (open disconnector).

Remote Data
With the Remote data function, customer-specific indications and measured values can be communicated via the protection interface with settable update cycles (priorities).
There are 3 different priorities for the transmission of remote data:

• Priority 1: Use Priority 1 for the transmission of fast protection signals that are transferred and updated at a maximum of every 20 ms in a telegram.
• Priority 2: Use Priority 2 for the transmission of fast single-point or double-point indications that are transferred and updated at a maximum of every 40 ms.
• Priority 3: Use Priority 3 for all indications, measured, and metered values that are transferred and updated a maximum of every 100 ms.

The number of customer-specific signals, indications, and measured values available conform with the remaining bandwidth. The remaining bandwidth is lower when using Line differential protection (type 1) than with all other protection functions (type 2). Customer-specific measured values consume more bandwidth than single-point indications.
Communication Media
The communication takes place via direct fiber-optic connections, via communication networks or via 2-wire copper conductors. Siemens recommends a direct fiber-optic connection, as this offers a high transmission rate and is immune to failures in the transmission route while offering the shortest transmission time. This also enables the transmission of a large amount of remote data in line differential protection applications and the remote control of remote devices with DIGSI 5.
The distance to be bridged and the transmission paths (communication media) available determine the settings of the protection interface. External communication converters are used for the connection to communication networks via G703.1-, X21-, or G703.6 interfaces. The connection to 2-wire copper cores also takes place via a communication converter. The C37.94 interface, for example, with 2 MBit/s, offers a direct fiber-optic connection to a multiplexer with the corresponding interface.
Table 3-9 to Table 3-10 show examples of communication connections.
In the case of a direct connection, the transmission distance depends on the fiber type of the optical fiber. This distance can also be extended via external repeaters.
The modules in the device can be replaced from outside, so that adaptation to a transmission route is possible.
In the case of the 820-nm double module USART-AE-2FO, 2 protection-interface channels can be operated on one module.
The modules can be located at slots E and F in the base device, and at slots N and P in the plug-in module assembly with integrated power supply.
When using communication converters, the connection from the device to the communication converter by a module is established via optical fibers.

Table 3-9 Plug-In Modules for Applications with Protection Communication

4 USART-AH-1LDFO only pairs with USART-AJ-1LDFO or USART-AY-2LDFO
5 USART-AJ-1LDFO only pairs with USART-AH-1LDFO or USART-AX-2LDFO
6 USART-AX-2LDFO only pairs with USART-AJ-1LDFO or USART-AY-2LDFO
7 USART-AY-2LDFO only pairs with USART-AH-1LDFO or USART-AX-2LDFO
8 Suitable for DIGSI 5, IEC 61850, process bus, busbar protection etc.

Table 3-10 Plug-In Modules USART-AD-1FO and USART-AE-2FO

1 x optical serial, 820 nm, ST connector, 2 km via 62.5/125 μm multimode optical fiber| ●|
2 x optical serial, 820 nm, ST connector, 2 km via 62.5/125 μm multimode optical fiber| | ●
Application| |
Protection interface (Sync. HDLC, IEEE C37.94)| ●| ●

NOTE The USART plug-in module types can be used in slots E and F in the base module as well as in slots N and P in the CB202 expansion module. They are not suitable for use in port M in the CB202 expansion module.

Figure 3-48 Optical Remote Connection with Attenuators

NOTE
Connect two 7XV5107-0AA00 attenuators if you use the communication modules USART-AV-2LDFO or USART-AK-1LDFO for transmission routes of less than 30 km. To continue using the duplex LC plug, attach both attenuators to one end of the protection connection (see Figure 3-48).

The connection to the multiplexer is established via a communication converter with a G703.1 interface (64 kBit/s) or X21 interface (64 kBit/s to 512 kBit/s). You can set the bit rate for the KU-XG-512 (for X21), KUXG-256 (for X21), KU-XG-128 (for X21), and KU-XG-64 (for X21 or G703.1) with the parameter Connection via.
You can find more detailed information in Table 3-11.

Figure 3-51 Connection via Communication Network with a G703.6 Interface

The connection to the multiplexer is established with 512 kBit/s via a communication converter with a G703.6 interface (E1 with 2 MBit/s or T1 with 1.44 MBit/s). The communication converter offers a 2nd interface for connecting an additional protection interface.
Adjust the setting for the bit rate with KU-2M-512 at 512 kBbit/s in accordance with Table 3-11 with the parameter (_:105) Connection via.

The connection to a communication converter with an integrated isolation voltage of 5 kV is established with 128 kBit/s (KU-KU-128 setting in accordance with Table 3-11). An isolation of 20 kV of the 2-wire connection is possible via an external 7XR9516 isolating transformer.

Figure 3-53 Direct Fiber-Optic Connection via an External Repeater

The repeater offers an interface for connecting an additional protection interface. The connection to a repeater is established with 512 kBit/s (repeater 512 kBit/s setting in accordance with Table 3-11).

Figure 3-54 Direct Optical Connection to a Multiplexer with a C37.94 N * 64 kBit/s Interface (Time Slot N = 1; 2 or 8)

NOTE
The redundancy of different communication connections (for the ring topology) requires rigorous separation of all devices involved in the communication. Therefore, avoid different transmission routes via the same multiplexer board, as no more substitute paths are possible if the board fails.
Supervision of the Communication
Communication is continuously monitored by the devices and displayed with indications and measured values.
If a number of defective data telegrams, or no data telegrams at all, are received, this is regarded as a failure in the communication as soon as a failure time of 100 ms (default setting can be changed) is exceeded.
For each protection interface, a list of the measured values is shown in a window in DIGSI 5 (defective telegrams per minute/hour; transmitted and received telegrams per minute/hour, percentage fault rate per minute/hour). A corresponding failure indication is always available. If no alternative transmission route exists (as in the ring topology), the protection function operating with the protection interface is not operating and remote data is not updated on the receiver side.
If the communication is interrupted for longer than an adjustable time Data- connection failure, this is regarded as a communication failure. A corresponding failure indication is always available.
Time Synchronization via the Protection Interface, Timing Master
All devices in a device combination can synchronize their time with each other. Synchronization is carried out with millisecond accuracy. The synchronization works independently of the protection function and is used exclusively for simultaneous time keeping in the devices of a device combination.
The device you set in the parameter (_:5131:102) Address of device 1 is the device with index 1.
This device functions takes on the role of the timing master in a device combination. If the timing master is logged off and switched off, the device with the next highest device index takes on the function of the timing master. The timing master synchronizes the clocks of the other devices via the protection interfaces.
The time of the timing master itself can be synchronized via the following time sources:

• IRIG B
• DCF77
• IEEE 1588
• SNTP

For this, these time sources must be set as the 1st time source and optionally as the 2nd time source in the timing master. If available, the system switches over to the 2nd time source upon failure of the 1st time source in the timing master.
The following chapters describe how a device is set as a timing master:

• For classic protection communication, see Parameter: Address of Device x, Page 97.
• For advanced protection communication, see Parameter: Device index, Page 135.

Set the protection interface as the 1st time source in the other devices of the device combination. You can find the setting value in DIGSI 5 via the Project tree → Parameters → Time settings → Timer → Time source 1 → PI.
In this way, all events in the devices of the device combination are recorded with the same time and are time-synchronized even across different switchgears. This simplifies fault analysis and the fault records are recorded with the same time in all devices.

Figure 3-55 Time Synchronization in a Device Combination

Figure 3-55 shows how device 1 with index 1 is synchronized with devices 2, 3, and 4 via the protection interface. Device 1 is the timing master, whose time is synchronized with a selectable, external time source.

Time Synchronization of the Line Differential Protection Measured Values with Millisecond Accuracy
The measured values of the devices connected via the protection interfaces are synchronized via telegram measurement with microsecond accuracy (1*10E-06 s). The protection interface displays this state with the indication PI synchronized RAISING.
If communications problems occur, it is possible that the measured values may not be properly synchronized.
In this case, the protection interface generates the indication PI synchronized CLEARED. The line differential protection is blocked. This state can be corrected only manually.
NOTE
You can reset the synchronization of the protection interface directly in the device. Proceed as follows: Device functions > x Device protection comm. > Protection interface y > Reset synchron.
For special line differential protection applications or synchrophasor measuring devices, you can also timesynchronize the measured values with microsecond accuracy as follows:

• Via a high-precision electrical synchronization pulse (PPS electrical, 1-second pulse) from a satellite receiver at time-synchronization port G
• Via a high-precision optical synchronization pulse (PPS optical, 1-second pulse) from a satellite receiver at a USART communication module
• Via the IEEE 1588 time-synchronization protocol

This allows you to measure and display the signal-transit time of the transmission route in transmit and receive direction separately. This lets you achieve the maximum responsivity with the line differential protection in communication networks even with differences in the signal-transit time in the transmit and receive direction (unbalanced runtimes). For the transmission of protection data in type 2 protection communication, different signal-transit times are irrelevant.
Log Off the Device
A device can be logged off for protection-function tests, system inspections, or disconnection of a feeder for operational reasons from the device combination. The logged off device no longer participates in the distributed functionality and is therefore no longer an active component of the device combination. The protection functions are still in operation for the other end or ends.
The following conditions are necessary for a successful logoff of the device from the point of view of protection communication:

• The device combination is not in a transient state and is stable in operation without switchovers of the protection connections. This displays the message of the device combination Status of topo. recog. with the value Valid.
• In a given chain topology, the device to be logged off is one of the 2 devices at the end of the communication chain.
• The circuit breaker must be open on the side of the device to be logged off and current must not be flowing.

NOTE If one of these conditions is not fulfilled, the device cannot be logged off.
You can find more detailed information in 3.7.4 Device Logout.
Constellation Measured Values
Constellation measured values are measured values predefined by Siemens with the following properties:

• They are synchronized in the devices in a device combination.
• They are substituted using the protection interface.
• They are available on every device.

You can view the constellation measured values with DIGSI 5.
In the device, current and voltage measured values are displayed in absolute value and phase as a percentage.
100 % conform to the rated current or the rated voltage of the line (see next figure). These measured values are recorded every 2 seconds by the devices participating in the device combination and then sent to the other respective devices. At the same time, the current and voltage values of the different devices are time-synchronous with one another.
When displaying the constellation measured values the local device is prioritized. The device connected directly with DIGSI 5 is the local device.
For the protection communication, the display of the constellation measured values differs between Type 1 and Type 2.

• Protection communication Type 1:
  The phasors of the current and voltage measured values of the local device have an angle of 0°. The angles of the measured values of the other devices relate to the local values, meaning that the angle difference to the remote ends is displayed.

• Protection communication Type 2:
  The voltage phasor VA of the local device has an angle of 0°. The angles of the other local measured values and the measured values of the remote devices relate to VA (0°).

You can find these measured values in the device under the following DIGSI mask:

Figure 3-56 Example of Constellation Measured Values with Phases

Multiplex Operation
With extended protection communication, you have the option of having a physical USART channel used by 2 logical protection interfaces. In this way, a transmission route can be double used, for example to implement Parallel line protection with Line differential protection without additional hardware. To do this, configure the channel according to chapter 3.4.6.4 Configuration of the Advanced Protection Communication in DIGSI 5.

Figure 3-57 Multiplex Operation

NOTE Note that in case of multiple use of a physical channel, the available bandwidth is divided equally between the logical protection interfaces. Therefore, this operating mode is not suitable for baud rates under 128 kBit/s.
NOTE In case of multiple use of a physical USART connection – for example, for protection of a double line – you must provide further redundancy concepts.

3.4.4 Available Variants for the Protection Communication
The following variants are available for protection communication:

• Classic protection communication
  The scope of parameterization is small for the classic protection communication. The following constraints exist:
  – IP-based communication protocols are not supported.
  – Increased parameterization effort when changing the number of devices in the device combination subsequently, for example, protection of a multi-terminal line.

• Advanced protection communication
  The advanced protection communication provides greater flexibility and is used with IP-based communication protocols. For this purpose, the devices must be equipped with an Ethernet BD module. The following advantages also exist for devices equipped with USART communication modules:
  – Easy subsequent expansion of the number of devices in a device combination
  – Multiple function groups Protection communication can be instantiated
  – Multiplex operation of a physical protection connection
  – Hierarchically structured representation in DIGSI 5 project tree
  For further information on the 2 variants, refer to 3.4.5 Classic Protection Communication and 3.4.6 Advanced
  Protection Communication .

NOTE Do not confuse the 2 variants of the protection communication with type 1 and type 2 of the protection communication!
NOTE If you are unsure about the suitable variant for your use case during selection, use the advanced protection communication.
NOTE If you want to change an existing classic protection communication to an advanced protection communication or vice versa, a window appears in DIGSI where you are asked  whether you want to keep the mapping or not – that is, the communication settings or communication-information routing that has previously been set. In this case, click No

3.4.5 Classic Protection Communication
3.4.5.1 Overview
The classic protection communication enables the data exchange between the devices via synchronous serial point-to-point connections from 64 kBit/s to 2 mBit/s. These connections can be directly via optical fiber or via other communication media, for example, via dedicated lines or via communication networks. IP-based communication is not supported.
The function groups of the classic protection communication always support a fixed number of devices in the device combination:

• 2-device protection communication
• 3-device protection communication
• 4-device protection communication
• 5-device protection communication
• 6-device protection communication

3.4.5.2 Classic Protection Communication in the Overall System
The classic protection communication is integrated as follows in the overall system:

Figure 3-58 Classic Protection Communication in the Overall System

(1) The device automatically routes the connection between the protection FG and the Protection communication FG in DIGSI 5.

3.4.5.3 Structure of the Function Group
If you select the communication protocol Protection interface and the number of devices on a channel in the communication module, the classic function group Protection communication is automatically created in the DIGSI 5 information routing.
The classic function group Protection communication contains the following functionalities and function blocks (FB):

• Device combination
• Protection interface
• FBs for Remote data
• FB External synchronization for the synchronization of the transferred data through an external synchronous pulse (1-second-pulse, PPS 9 )

Figure 3-59 Structure of the Classic FG Protection Communication
The function Device combination manages the devices that exchange data via protection communication.
In the device-combination settings, you set the general settings for the device combination and the device addresses.
The function Device combination issues the following indications:

• General indications like the
  – Number of devices
  – Type and status of the device topology

• Indications of the devices in the device combination like:
  – The availability of the device
  – The state of the device, that is whether the device is logged on or off in the device combination

Measured values are transmitted via protection communication and are acquired and exchanged at the same time in the devices. The synchronization of the measured-value acquisition can be done either internally via the telegram measurement or via an external synchronous pulse (1-second pulse, PPS) using the function block External synchronization. The external synchronization is switched on in the function block of the protection interface. You can find the indications of the external synchronization in the function block
External synchronization.
The function block Remote data is used to transfer selected and user-specific signals and measured values from the SIPROTEC 5 system. You select the signals and measured values to be transmitted in the communication mapping of DIGSI. The remote data does not issue status indications.
The function block Protection interface is automatically connected to a physical channel of a communication module and can therefore send signals and measured values to the neighboring device or receive them from the neighboring device. You can find the status indications of the FB Protection interface in the DIGSI 5 information routing in the function group Protection communication.

NOTE
In contrast to the protection interface in extended protection communication, the protection interface in classic protection communication is automatically connected to a physical channel of the communication module (refer to Figure 3-58).

3.4.5.4 Configuration of the Protection Interface in DIGSI 5
If the device is provided with modules, proceed as follows:

• Select the desired communication module in the rear view of the device.
• In the Properties of the communication module > Protocols > Channel x Protocols, select the Protection interface protocol.

Figure 3-60 Selection of the Communication Protocol

• Then select the number of devices under Mapping (see next figure).
  Depending on the device, the selection of device combinations can be restricted to 2 or 3 devices.
  The number of devices is an order option with regard to the line differential protection.

Figure 3-61 Selecting the Device Combination

NOTE
The function groups shown in Figure 3-61 are not available in the DIGSI library.
You can change the number of devices (for example 2 protection communication devices) depending on the product code any way you like via the Mapping text box.
If you change the number of devices via the Mapping text box, all activated remote data, settings of the device combination and of the protection interface are lost.

If the module slot is not yet provided with modules, proceed as follows:

• Select the desired communication module in the rear view of the device.
• Select the module from the catalog and drag it to a channel. Thus is the channel configured with a module. DIGSI 5 indicates whether the module can be used for protection communication under Device Information.
• Use the Protocols text box to select the Protection interface, see Figure 3-60.
• Then use the Mapping text box to select the number of devices, for example 2 devices protection com., see Figure 3-61.

3.4.5.5 Setting Notes for the Device Combination
Select the communication module in the Project tree > Hardware and protocols in the Device view. In the properties of the communication module, you can find the setting sheets for the parameterization of the device-combination settings and the settings for protection communication.

Changes in the device-combination settings are always visible on the other channel as well. All further parameters can be set separately for individual channels.

Parameter: Address of Device x

• Default setting (_:5131:102) Address of device 1 = 101
• Default setting (_:5131:103) Address of device 2 = 102
• Default setting (_:5131:104) Address of device 3 = 103
• Default setting (_:5131:105) Address of device 4 = 104
• Default setting (_:5131:106) Address of device 5 = 105
• Default setting (_:5131:107) Address of device 6 = 106

The parameters Address of device 1 to Address of device 6 can be used to give an address to each device. Set a unique and unambiguous address for each device.

NOTE The number of device addresses displayed corresponds to that of the number selected during the device combination configuration.
NOTE The device 1 is the timing master device in a device combination.
If all other devices in the device combination are to obtain their time from the timing master device, note the following:

• Under Address of device 1 set the address for the timing master device.
• Parameterize the other devices such that they get their time from the timing master device via the protection connections.
  For more information, refer to 3.5.3 Function Description. Select as the adjustable synchronization option Protection interface.
  In the timing master device you must not set the protection interface as the synchronization source!

Parameter: Local device is device

• Default setting (_:5131:101) Local device is device = 1
  With the parameter Local device is device, you set the index (number) of your device in the device combination. A maximum of 6 devices can be present in one device combination.

APPLICATION EXAMPLE
You have a device combination with 2 devices.
For example, in DIGSI 5, select the parameter setting Address of device 1 with the parameter value 101 for device 1 and the parameter setting Address of device 2 with the parameter value 102 for device 2.
Then, use the Local device is device parameter to set the index of the local device. The local device is the device that you parametrize.
The addresses must be set identically for all devices in the device combination. Functional protection communication requires that you also assign the same index in all devices of the device combination for a device with a unique address.

Parameter: Lowest appearing bit rate

• Default setting (_:5131:122) Lowest appearing bit rate = 64 kBit/s

With the parameter Lowest appearing bit rate, you set the lowest bit rate occurring in the device group. Set the lowest value in each device with a three-end constellation with 2 fiber-optic connections (2 MBit/s) and one 64 kBit/s connection with the lowest value (64 kBit/s). This value determines the maximum number of selected and self-created signals and measured values which are to be transmitted within the device combination (refer to 3.4.5.9 Configuring Remote Data).
Apart from the default value, you can also set the following bit rates:

• 128 kBit/s
• 512 kBit/s
• 2048 kBit/s

NOTE
If you use optical fibers for a connection between the devices, set the value to 2048 kBit/s.

Parameter: Number of devices

• Default setting (_:5131:125) Number of devices = 6
  With the parameter Number of devices, you set the number of devices actually connected via protection interfaces. This parameter is set by default to the maximum number of devices permitted in the device combination.
  This parameter lets you configure a planned final expansion of a system with a planned number of devices already at this point in time and to put it into operation with a lower number of devices. When configuring the protection interface, select the number of devices present in the final phase of the system in the Mapping text box. If you set the parameter Number of devices to a smaller value than the maximum value, you achieve functional protection communication with fewer devices. In this procedure, all settings, for example, routing, you made for the device combination are retained, even if you subsequently increase the number of devices. If you wish to operate, for example, a planned 3-device protection communication as a 2-device protection communication, you must set the parameter Number of devices to 2. If you expand the system later, change the Number of devices parameter to the planned maximum number.
  For more detailed information regarding the configuration of the protection interface, refer to 3.4.5.4 Configuration of the Protection Interface in DIGSI

NOTE
The Number of devices parameter is only visible for device combinations with more than 2 devices.
Set the same number of devices used in all devices that are part of the device combination.

Connection mode
• Default setting Connection mode = SIPROTEC 5
With the parameter Connection mode, you select the device type with which the SIPROTEC 5 device is to work in the device combination. As soon as a SIPROTEC 4 device works in the device combination, you must set the parameter Connection mode accordingly.

device combination.
SIPROTEC 4 7SD610| The SIPROTEC 5 device works with at least one SIPROTEC 4 Differential protection device 7SD610 with firmware version V4.72 and higher in the device combination.
SIPROTEC 4 7SD5| The SIPROTEC 5 device works with at least one SIPROTEC 4 Differential protection device 7SD5x with firmware version V4.72 and higher in the device combination.
SIPROTEC 4 7SA5/6| The SIPROTEC 5 device works with at least one SIPROTEC 4 Distance protection device 7SA522 and 7SA6x with firmware version V4.72 and higher in the device combination.

3.4.5.6 Setting Notes on Selecting the Communication Medium
• Default setting (_:105) Connection via = fiber optic

The Connection via parameter is used to set the bit rate required for the protection interface. Different discrete values can be entered depending on the means of communication (see following table).
Also refer to Communication Media, Page 81
Table 3-11 Means of Communication

kBit/s
CC-CC-128 Communication converter| Figure 3-5 2| CCPW 128 kBit/s| 128 kBit/s
CC-2M-512 Communication converter| Figure 3-5 1| CC2M 512 kBit/s| 512 kBit/s
Multiplexer with C37.94 interface| Figure 3-5 4| C37.94 1 64 kBit/s
C37.94 2 64 kBit/s
C37.94 8 * 64 kBit/s| 64 kBit/s
128 kBit/s
512 kBit/s
Other (freely adjustable bit rates for a direct
connection for special applications)| | 64 kBit/s
128 kBit/s
512 kBit/s
2048 kBit/s| 64 kBit/s
128 kBit/s
512 kBit/s
2,048
kBit/s

3.4.5.7 Setting Notes for the Classic Protection Interface

Parameter: Max. error rate per hour

• Default setting (_:5161:105) Max. error rate per hour = 1.0%
  If the number of faulty telegrams per hour exceeds the value set in the parameter Max. error rate per hour, you receive the error message Error rate / hour exc..

Parameter: Max. error rate per min

• Default setting (_:5161:106) Max. error rate per min = 1.0%
  If the number of faulty telegrams per minute exceeds the value set in the parameter Max. error rate per min, you receive the error message Error rate / min exc..

Parameter: Disturbance alarm after

• Default setting (_:5161:107) Disturbance alarm after = 100 ms
  With the parameter Disturbance alarm after, you determine the time delay after which defective or missing telegrams are signaled as faulty where the indication Status of lay. 1 and 2 is PI data fault.

Parameter: Transm. fail. alarm after

• Default setting (_:5161:108) Transm. fail. alarm after = 6.0 s
  With the parameter Transm. fail. alarm after, you determine the time delay after which a communication failure is signaled where the indication Status of lay. 1 and 2 is
  PI data failure.

Parameter: Delay time threshold

• Default setting (_:5161:109) Delay time threshold = 30.0 ms

The time taken to transmit and receive a signal via a protection connection is the signal-transit time. You can monitor the signal-transit time. For the Delay time threshold, the default setting is selected in such a way that normal communication networks do not exceed the signal-transit time. If this signal-transit time is exceeded during operation (for example upon switchover to another transmission route), the indication Time delay exceeded is issued.
Increased runtimes only affect the operate time, and therefore the fault- clearing time of the protection functions using the protection interface. If you use the Line differential protection function, this remains in effect.
Parameter: Difference Tx and Rx time

• Default setting (_:5161:110) Difference Tx and Rx time = 0.1 ms

For time synchronization of the measured values with microsecond accuracy using telegram measurement, the signal-transit times in the send and reception direction must be approximately the same. The device monitors the signal- transit times in the send and reception direction.
With the parameter Difference Tx and Rx time, you set a maximum permitted signal-transit time difference between the send and reception paths (runtimes unbalanced). Set the parameter Difference Tx and Rx time to the maximum difference expected.
Set this value to 0 for a direct fiber-optic connection. A higher value is necessary for transmission via communication networks. Reference value: 0.1 ms (recommended setting value).
If the difference in the signal-transit times between the send and reception path exceeds the value set, the indication Time delay jump is issued.
If the difference from consecutive measurements of the signal-transit times between the send and reception paths exceeds the set value and remains for more than 5 s, the indication Time delay different is issued. The Line differential protection function is no longer working properly and is ineffective.

NOTE The parameter Difference Tx and Rx time only shows when the function Line differential protection is instantiated and the parameter Synchronization is not set to External synch. only.
NOTE If you use a multiplexer with a C37.94 interface as a means of communication, Siemens recommends a setting value of 0.25 ms to 0.6 ms.

Parameter: Synchronization
• Default setting (_:5161:113) Synchronization = External synchron. off
With the parameter Synchronization, you control the time synchronization of the measured values with microsecond accuracy.
If the SIPROTEC device operates with the external synchronization, use the Synchronization parameter to define how the protection is activated after restoration of the communication connection (basic state or after transmission fault). See Figure 3-65.

No external synchronization is performed at the protection interface. Select this setting value if you do not expect any differences between the signaltransit times in the transmission and reception directions. Then the measured values are only synchronized internally with the telegram measurement.
Telegr. and ext. synch.| Synchronization via telegram measurement and external synchronization:
The measured values are synchronized internally with the telegram measurement, supported by the external synchronization. You can set the external synchronization with the parameter External
synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of a satellite receiver.
In this case, an existing line differential protection is only released when a new connection is established and one of the following conditions is met.
• The protection connection is synchronized with the help of the external synchronization.
• Symmetric signal-transit times are signaled via the binary input signal

Sync reset or the controllable Reset synchronization. This means that the signal-transit times are the same in the send and
receive direction.
Telegr. or ext. synch.| Synchronization via telegram measurement or external synchronization:
The measured values are synchronized internally with the telegram measurement, supported by the external synchronization. You can set the external synchronization with the parameter External synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of a satellite receiver.
An available line differential protection is enabled immediately upon renewed establishment of connection (data telegrams are received).
The internal synchronization is used up to synchronization.
External synch. only| External synchronization only:
The measured values are synchronized only through the external synchronization.
You can set the external synchronization with the parameter
External synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of a satellite receiver.

Parameter: External synchronization
• Default setting (_:5161:117) External synchronization = PPS electrical (Port G)
The parameter External synchronization is visible only if the parameter Synchronization is not set to External synchron. off.
External synchronization is possible separately for each protection interface.

receiver (1-second-pulse, PPS 10 ) is the synchronization source on the port G, the time synchronization interface.
IEEE 1588| The time synchronization protocol IEEE 1588 for an Ethernet-BD communication module is used for synchronization.

NOTE The configuration option IEEE 1588 is only visible if the device has an Ethernet-BD communication module and you have selected the communication protocol IEEE 1588, see following figure.

Figure 3-64 Ethernet-BD Communication Module: Selection of the IEEE 1588 Protocol

NOTE
External synchronization takes into account the signal-transit time in the transmission and reception directions. If external synchronization fails for a short time, for example, due to a receiving interference or an unfavorable satellite position for a brief period, internal synchronization via telegram measurement is still active.

NOTE
In contrast to the protection interface in extended protection communication, the protection interface in classic protection communication is automatically connected to a channel of a communication module (see Figure 3-58).

Parameter: Max. inaccuracy

• Default setting (_:5161:119) Max. inaccuracy = 0.500 ms

With the parameter Max. inaccuracy, you configure the maximum expected inaccuracy of the synchronization sourced used. The set value is only effective if the synchronization source used does not supply any information on the current inaccuracy in the synchronization signals. If you have not used any of the information on the inaccuracy of the synchronization source used, use the default setting.

NOTE
The inaccuracy of the synchronization source enters the stabilization of the Line differential protection as an error signal.
This means that a greater inaccuracy increases the calculated restraining quantity and makes the Line differential protection less sensitive.
If IEEE 1588 is used as the synchronization source in the synchronization status SmpSynch = global, accuracy values are supplied with the synchronization signals and the parameter Max. inaccuracy is not used. If the supplied accuracy values become invalid, the value set in the parameter Max. inaccuracy is used.
If the synchronization source IEEE 1588 works in the synchronization status SmpSynch = local, then the value set in the parameter Max. inaccuracy is used as permanently available inaccuracy.
If the synchronization source PPS electrical (Port G) or PPS optical (USART) is used, then the value set in the parameter Max. inaccuracy is used as permanent inaccuracy. If a USART communication module with the PPS protocol and the PPS generatoroperating mode is also used as a synchronization source at the same time, the value set in the parameter Max. inaccuracy is used as permanent inaccuracy.

Parameter: Check synchron.-source
• Default setting (:5161:121) Check synchron.-source = yes
With the parameter Check synchron.-source, you can switch on or off the synchronization-sources check. During the check of the synchronization sources on the ends of a protection connection, a check is conducted as to whether both synchronization sources are working in the same synchronization status SmpSynch.
If both synchronization sources are working in the synchronization status SmpSynch = global, the check has been passed.
If both synchronization sources are working in the synchronization statusSmpSynch = local, that is decoupled from a global reference time, an additional check is conducted as to whether the synchronization source ( gmIdentity) is the same. Synchronicity can only be guaranteed if the synchronization sources are the same.
If the synchronization sources display a different synchronization status, that is one displays the synchronization status SmpSynch = local and the other the synchronization status SmpSynch = global, synchronization cannot be guaranteed. Siemens recommends using the default setting Check synchron.-source = yes.
If you have problems with the synchronization-source check, you can switch off the synchronization-source check. Switch off the synchronization-source check only if the synchronization sources are synchronous at the end of their protection connection. The parameter
Check synchron.-source is visible only if the parameter (:5161:113) Synchronization is set to External synch. only.
NOTE
If you use PPS electrical (port G) as the synchronization source, the synchronization status (SmpSynch) is permanently set to global.
If you use PPS optical (USART) as the synchronization source, you can use the setting (:107) Received. SmpSynch to set the synchronization status to (SmpSynch) local or global.
For synchronization with microsecond accuracy, for example with Line differential protection, adjust the parameter (:107) to Accepted. SmpSynch = global.
3.4.5.8 Indications and Measured Values in the Classic Protection Interface
Each individual protection interface provides different indications for commissioning and diagnostics of communication:

Indication (:5161:301) Status of lay. 1 and 2
The indication (:5161:301) Status of lay. 1 and 2 informs you about the status of the connection. The following indications are possible:

Table 3-12 Status Indications Status of lay. 1 and 2

state.
PI connected:| The protection interface is connected to the protection interface of the partner device.
PI data fault:| The protection interface has not received any valid telegrams for the time set in parameter (:5161:107) Disturbance alarm after  .
PI data failure:| The protection interface has not received any valid telegrams for the time set in parameter (:5161:108) Transm. fail. alarm after .
not existing:| The protection interface has not been assigned to a communication channel.

Indication (:5161:302) Status of lay. 3 and 4
The indication (:5161:302) Status of lay. 3 and 4 informs about errors during the connection establishment. The following indications values are possible:

versions of the devices are incompatible.
Update the firmware.
wrong dev. ID:| The connection is not established because the device address of the local device or the partner device is incorrect or set incorrectly.
Check the settings for the parameters Address of device 1 to Address of device n ( :5131:102 and following).
const.sett.error:| The connection is not established because the parameters are set differently.
Check whether the parameter (:5131:122) Lowest appearing bit rate has been set the same in all devices in the device combination.
diff.sett error:| The connection is not established because the parameters are set differently.
The line differential protection settings for the connected devices are incompatible. Check whether the devices are set to operate with or without line differential protection.
The rated current of the line (parameter (:9001:101) Rated current) must have the same setting in all devices.
With a transformer in the line, the (:9001:103) Rated apparent power must be set to the same value in all devices.
net mirroring| The connection is not established. The protection interface is receiving its own data.
Check the wiring.
wrong dev. idx.| The connection is not established because the device index of the local device or the partner device is incorrect.
Check the setting for the parameter (_:5131:101) Local device is device.

Furthermore, the following output signals are available:

during a parameterized time (parameter (:5161:107) Disturbance alarm after) no telegrams or faulty telegrams were continuously received. If the indication Connection broken is issued, the affected protection connection is reset. This can cause the blocking of an active line differential protection or a ring topology can change to a chain topology.
(:5161:316) Error rate / min exc.| The signal Error rate / min exc. indicates that the set maximum error rate per minute (parameter (:5161:106) Max. error rate per min) has been exceeded.
In this manner, a brief increase of the operate time and thus of the faultclearing time is possible for the protection functions using the protection interface. If you use the Line differential protection function, this remains in effect.
(:5161:317) Error rate / hour exc.| The signal Error rate / hour exc. indicates that the set maximum error rate per hour (parameter (:5161:105) Max. error rate per hour) has been exceeded.
In this manner, a brief increase of the operate time and thus of the faultclearing time is possible for the protection functions using the protection interface. If you use the Line differential protection function, this remains in effect.
(:5161:318) Time delay exceeded| The signal Time delay exceeded indicates that the threshold value for the set signal-transit time (parameter (:5161:109) Delay time threshold) has been exceeded.
Increased transmission times only affect the operate time, and therefore the fault-clearing time of the protection functions using the protection interface. If you use the Line differential protection function, this remains in effect.
(:5161:319) Time delay different| The signal Time delay different indicates that the threshold value for the difference in signal runtimes in the transmission and reception direction (asymmetrical runtimes) has been exceeded. The setting value results from the setting value of the parameter (:5161:110) Difference Tx and Rx time.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch. only.
If the indication Time delay different appears, the Line differential protection function is no longer working properly and is ineffective.
(:5161:320) Time delay jump| The signal Time delay jump indicates that the signal runtimes of the data changed abruptly. This is caused by a switchover of the communication path in the communication network.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch. only.
(:5161:321) PI synchronized| The signal PI synchronized indicates that the synchronization with microsecond accuracy of the measured values transferred between the local device and partner device is working correctly.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch. only.
(:5161:340) Telegram lost| The signal Telegram lost indicates that an expected telegram has failed to arrive or a faulty telegram has been received. Reasons for this can be for example switching operations in the primary system or operations on the
components of the communication network.
If you want to assign the communication failures or faults to other events, route the signal Telegram lost temporarily into the operational log.
Note: If the signal is constantly routed, the operational log can overflow. Siemens recommends routing the signal only for clarification of problems.
(:5161:343) Partner| The indication shows the address of the partner device. A value of 0 means that no partner address is available.
(:5161:323) PPS: time del. unsym.| This indication is only visible if you are working with a synchronous pulse.
The indication shows that the difference in the signal runtimes between the sending and receiving path exceeds the value set with the parameter (:5161:110) Difference Tx and Rx time.
Note: The Line differential protection function remains effective.
(_:5161:324) PI with PPS synchron.| This indication is only visible if you are working with a synchronous pulse.
This indication is only visible if, in parallel to synchronization with the synchronization pulse, you are also working with the synchronization via telegram measurement. If both synchronization methods are working properly, the indication PI with PPS synchron. = RAISING is generated.

Measured Values of the Protection Interface
The protection interface provides the following measured value for the diagnosis of the protection-interface communication:

transmission and reception path divided by 2, without external synchronization)
(:5161:326) Rec. Δt| Signal runtime for reception path (with external synchronization)
(:5161:327) Sen. Δt| Signal runtime for transmission path (with external synchronization)
(:5161:334) Miss.tel/min| Number of telegram failures within the last minute
(:5161:335) Miss.tel/h| Number of telegram failures within the last hour
(:5161:336) Miss.tel/d| Number of telegram failures within the last day
(:5161:337) Miss.tel/w| Number of telegram failures within the last week
(:5161:338) M. loss/d| Longest lasting telegram failure within the last day
(:5161:339) M. loss/w| Longest lasting telegram failures within the last week
(_:5161:331) Recept.| Receipt of a telegram (0 = no receipt, 1 = receipt)
You can use this indication to make the telegram exchange visible in the fault record.

NOTE
You can reset the measured values of the protection interface directly in the device. Proceed as follows:
Device functions > x Device protection comm. > Protection interface y > Release measured values.

Indications of External Synchronization
The following indications are visible only if the parameter (_:5161:117) External synchronization is set to PPS electrical (Port G).

• (_:9181:501) >PPS pulse loss
• (_:9181:301) PPS pulse loss
• (_:9181:302) PPS pulse
• (_:9181:303) PPS pulse OK

The following indications are visible only if the parameter (_:5161:117) External synchronization is set to IEEE 1588.

• (_:304) Synchronization loss
• (_:305) Synchronization OK
• (_:306) Synchronization pulse

synchronization via a binary input. The external synchronization can be set to inactive through this binary input indication.
(:9181:501) >PPS pulse loss| The binary input (:9181:501) >PPS pulse loss can be used to signal an externally detected failure in the PPS synchronous pulse (for example, an error message from the satellite receiver). Setting this binary
input also leads to the indication (:9181:301) PPS pulse loss. The external synchronization detects immediately that there is a problem with the connected synchronization pulse. Otherwise, the problem will only be noticed after approx. 2.1 s – after the test for synchronous-pulse failure.
(:9181:301) PPS pulse loss| This indication shows that the synchronization has failed. This can be due to the following reasons:
• The input indication (:9181:501) >PPS pulse loss has occurred.
• The synchronous pulse has failed.
• The quality of the synchronous pulse is inadequate.
• There is another problem with the synchronization source.
If no further PPS synchronous pulse is received within 2.1 s, the time-out monitoring responds. If no new second pulse occurs after the expiry of the monitoring time, the indication (:9181:301) PPS pulse loss is issued (see Figure 3-65).
(:9181:302) PPS pulse| This indication displays the synchronous pulse directly. As a rule, one pulse is generated per second. This indication works well to make the synchronous pulse visible.
(:9181:303) PPS pulse OK| This indication shows that the synchronization is working properly.
(:9181:304) Synchronization loss| The synchronization has failed. This can be due to a problem with the synchronization source.
(:9181:305) Synchronization OK| The synchronization is working properly.
(:9181:306) Synchronization pulse| You can use this indication to make the virtual synchronous pulse visible. As a rule, one pulse is generated per second.
(:9181:307) Synchron. Imprecise| If the set synchronization source operates in the global synchronization status (SmpSynch) and the time of the synchronization source deviates from the global time by more than 0.5 ms, the indication Synchron.
impreciseis generated and the Line differential protection becomes ineffective.
The indication Synchron. imprecise is visible only if the parameter External synchronization is set to IEEE 1588.

Figure 3-65 Logic for the Generation of the Indication PPS pulse loss

3.4.5.9 Configuring Remote Data
Between the devices in a device combination, a data bar is exchanged which can be described or read by the devices. This can be used for exchanging various signals between the devices. In this case, each signal demands a certain number of data fields.

Figure 3-66 Data Bar Exchanged Between Devices

The data bar is divided into 3 priorities, which also have different transmission rates and data volumes.
For all signals to be sent, the basic principle is that only pure data contents are transmitted. The quality (for example, Valid) is not automatically transmitted as well. If you want to transmit the quality as well (for example, for further processing of GOOSE messages), the quality must be transmitted separately (for example, by using CFC). If a signal that has a test flag is transmitted (because its function is in test mode, for example), all signals are provided with a test flag on the receiving side. If the connection is broken, all received signals are flagged with the quality Invalid. If desired, the value can also be set to a predefined state after a selectable dropout time or the last value received can be retained (Hold setting). This can be configured separately for each received signal (see Table 3-16).
NOTE
For ACT type signals, only the phase information is transmitted.
Signals that are transferred data fields of priority 1 are sent with every telegram. They are preferably used for the transmission of rapid signals, for example, release for circuit-breaker intertripping. A strictly deterministic, rapid transmission is required there.
Signals of priority 2 are transmitted with at least every 2nd telegram. For bit rates >256 kBit, there are no differences between priority 1 and priority 2.
Priority 3 signals are transmitted at least every 100 ms. This priority is used for transmission of measured and metered values. Complex values must be routed separately as the real and the imaginary part for transmission. Measured-value thresholds that lead to an updating of a measured value are set centrally as a property of the measured value. These measured-value thresholds apply with the corresponding reporting, for example, also for the transfer via IEC 61850 to a substation automation technology. Signals which are written to a data area x under a priority on the data bar must be routed to an indication of the same type in the device reading this information. Otherwise, they are processed incorrectly on the receiving side. The data bar is organized in terms of bits. For information on the bit requirement of each signal type, refer to Table 3-15.
Table 3-13 and Table 3-14 show the number of data areas in the data bar in relation to the available baud rate.
NOTE
Adjust the parameter (_:5131:122) Lowest appearing bit rate in each device for the protection interfaces in a device combination. This determines the number of data areas.
If, for example, in a device combination with 3 devices with a type 2 chain topology 2 devices are connected via direct optical fibers and 2 devices with a bit rate of 64 kBit/s, the 64 kBit/s section is the limiting factor for the entire device combination.

Table 3-13 Available Bits – Minimum Constellation Baud Rate 64/128 kBit/s

| Priority 1| Priority 2| Priority 3
---|---|---|---
Type 1| 8 bits| 24 bits| 128 bits
Type 2| 32 bits| 64 bits| 256 bits

Table 3-14 Available Bits – Minimum Constellation Baud Rate 512/2048 kBit/s

| Priority 1| Priority 2| Priority 3
---|---|---|---
Type 1| 48 bits| 128 bits| 384 bits
Type 2| 96 bits| 200 bits| 1024 bits

Table 3-15 Requirement in Bits

Table 3-16 Possible Dropout Values

Position, Hold
IN (metered values)| 0, Hold
MW (measured values)| 0, Hold
ACT| Hold

NOTE If the protection link fails, these values can be set on the receiver side.
EXAMPLE
2 devices are connected with line differential protection via a 64-kBit channel. This is a type 1 protection communication. There are 8 bits available for priority 1. Now, for example, 4 SPS and 2 DPS can be routed: 4 x 1 Bit + 2 x 2 Bits = 8 Bits
NOTE Measured values are transmitted as primary values.
EXAMPLE
For the display of the rated current in the receiving device
When Irated = 1000 A in the transmitting device and ILoad = 200 A, the number 200 is displayed in the receiving device.
Configuration of Remote Data in DIGSI 5:
To configure remote data, navigate in DIGSI 5 through the project tree to the communication mapping.
11 The complex phasors of a measuring point are prerouted

Figure 3-67 Communication Mapping in DIGSI 5

Figure 3-68 to Figure 3-72 show the routing for a type 1 protection communication.
To transmit signals to other devices, these signals must be routed in the communication matrix under Transmit. Binary inputs 1 and 2 are single-point indications (SPS) and are routed to bit position 1 and bit position 2 of the transmission with the highest priority (priority 1). For 64 kBit/s, for example, only 8 of these data areas are available for type 1 protection communication; they are exchanged between the devices with each telegram. Signals 3 and 4 are double-point indications (DPS), for example, a switch position that is transmitted by device 1. A double-point indication occupies 2 bit positions on the data bar. In addition, a measured and metered value are communicated with priority 3.
As a measured or metered value uses 32 bits, value 2 starts at bit position 33. DIGSI 5 shows the next free bit position.

Figure 3-68 Routing of Single-Point Indications to Protection Communication in Device 1

Figure 3-69 Routing of Measured Values to Protection Communication in Device 1

Figure 3-70 Routing of Metered Values to Protection Communication in Device 1

Device 1 also receives signals (in the communication mapping under Receive, see next figure). These signals must be routed with the other devices under Transmit. The binary outputs 1 and 2 in device 1 receive their information via the protection communication. This is priority 1 information, which has been routed in another device to position 3 and 4 of the data bar for transmission. The secure state is predefined in the Fallback value column. If the protection connection fails, the single-point indication is reset to raising or cleared as the fallback value or its value is retained ( Hold). For signals of the various priorities, you can also set a dropout time after which the reset (see following figure) to the fallback value occurs, in order to retain the original state for a short time in the event of brief interruptions. These 3 dropout times apply for all signals of one transmission priority and are set as parameters.

Figure 3-71 Parameterization of Dropout Time for Signals of Different Priorities

Figure 3-72 Routing of Single-Point Indications (Receive) to Protection Communication in Device 1

The following figure shows the routing in the 2nd device. Binary inputs 1 and 2 are routed with priority 1 to bit positions 3 and 4 there. In device 1, bit positions 1 and 2 are already occupied (see Figure 3-68). If you also route the signals to bit positions 1 and 2, the signals of both devices are then connected to the corresponding bit position with a logical OR operation. If measured and metered values are routed in the same data areas, this results in implausible values for the receivers. As a user, you are therefore responsible for the correct
routing.

Figure 3-73 Routing of Single-Point Indications to be Sent to Protection Communication in Device 2

The binary outputs 1 and 2 (Receive) in the 2nd device are connected to priority 1 signals 1 and 2 from the 1st device. This takes place via the data areas at positions 1 and 2 of the data bar, which transfer the state of the signals. Other devices can also read this information and logically link it to their internal signals.
Here, too, the secure state, which is assumed when the protection connection is interrupted, is entered. This state depends on the information. With single-point indications, states 0 or 1 make sense. In the case of double- point indications, bit combinations 00, 01, 10, or 11 are possible to directly signal a disturbed position upon failure of the protection connection, for example.
Hold is used to retain the state before the failure of the protection connection.

Figure 3-74 Routing of Received Single-Point Indications to Protection Communication in Device 2

Figure 3-75 Routing of Received Measured Values to Protection Communication in Device 2

Figure 3-76 Routing of Metered Values to Protection Communication in Device 2

3.4.5.10 Constellation Measured Values for Type 1 and Type 2

NOTE
The constellation measured values are only available for the FG Line.
Each device in the device combination determines measured values predefined by Siemens, known as constellation measured values. You can find the constellation measured values in the DIGSI 5 information routing under the FG n Device protection comm. > Constell. measured values. The following measured values and indications are issued for each device:

that is synchronized with all devices of the device combination. The absolute value and angle are issued for each phase.
(:1351:6811:303) Iph| This measured value shows the current of the 3 phases that is synchronized with all devices of the device combination. The absolute value and angle are issued for each phase.
(:1351:6811:300) Dev.adr.| This indication shows the device address. This allows you to assign the measured values and the circuit-breaker position in a better way.
(_:1351:6811:301) CB| This indication shows the position of the local circuit breaker and can have the following values:
• 0: The switch position of the local circuit breaker is unknown.
• 1 The local circuit breaker is open.
• 2 The local circuit breaker is closed.

The constellation measured values have the following properties:

• They are synchronized in the devices in a device combination.
• They are substituted using the protection interface.
• They are available on every device in the device combination.

You can view the constellation measured values with DIGSI 5.
In the device, current and voltage measured values are displayed in absolute value and phase as a percentage.
100 % conform to the rated current or the rated voltage of the line (see Figure 3-77). These measured values are recorded every 2 seconds by the devices and then sent to the other respective devices. At the same time, the current and voltage values of the different devices are time-synchronous with one another.
When displaying the constellation measured values, the local device is prioritized. The device connected directly with DIGSI 5 is the local device.
The angle reference depends on the type of the FG Protection communication used:

• Protection communication Type 1:
  – The angle values of the voltages show the angle difference between the local and the remote voltage. The local voltage serves as the reference with an angle of 0°.
  – The angle values of the currents show the angle difference between the local and the remote current. The local current serves as the reference with an angle of 0°.

• Protection communication Type 2:
  The angles of the phase-to-ground voltages and the phase currents relate to the voltage VA of the remote device.

You can find these measured values in the device under the following DIGSI mask:

Figure 3-77 Example of Constellation Measured Values with Phases

3.4.5.11 Settings

Device combin.
:5131:102| Device combin.:Address of device 1| | 1 to 65534| 101
:5131:103| Device combin.:Address of device 2| | 1 to 65534| 102
:5131:104| Device combin.:Address of device 3| | 1 to 65534| 103
:5131:105| Device combin.:Address of device 4| | 1 to 65534| 104
:5131:106| Device combin.:Address of device 5| | 1 to 65534| 105
:5131:107| Device combin.:Address of device 6| | 1 to 65534| 106
:5131:101| Device combin.:Local device is device| | 1 to 6| 1
:5131:122| Device combin.:Lowest appearing bit rate| | • 64 kBit/s
• 128 kBit/s
• 512 kBit/s
• 2048 kBit/s| 64 kBit/s
:5131:125| Device combin.:Number of devices| | 2 to 6| 6
:5131:127| Device combin.:Dev. comb. is time source| | • no
• yes| yes
Prot. interf.1
:5161:1| Prot. interf.1:Mode| | • off
• on| on
:5161:105| Prot. interf.1:Max. error rate per hour| | 0.000 % to 100.000 %| 1.00%
:5161:106| Prot. interf.1:Max. error rate per min| | 0.000 % to 100.000 %| 1.00%
:5161:107| Prot. interf.1:Disturbance alarm after| | 0.05 s to 2.00 s| 0.10 s
:5161:108| Prot. interf.1:Transm. fail. alarm after| | 0.0 s to 6.0 s| 6.0 s
:5161:109| Prot. interf.1:Delay time threshold| | 0.1 ms to 30.0 ms| 30.0 ms
:5161:110| Prot. interf.1:Difference Tx and Rx time| | 0.000 ms to 3.000 ms| 0.100 ms
:5161:113| Prot. interf.1:Synchronization| | • External synchron. off
• Telegr. and ext. synch.
• Telegr. or ext. synch.
• External synch. Only| External synchron. Off
_:5161:117| Prot. interf.1:External synchronization| | • PPS electrical (Port G)
• IEEE 1588| PPS electrical (Port G)

3.4.5.12 Information List

Device combin.
:5131:52| Device combin.:Behavior| ENS| O
:5131:53| Device combin.:Health| ENS| O
:5131:301| Device combin.:Status of topo. recog.| ENS| O
:5131:302| Device combin.:Topology is| ENS| O
:5131:303| Device combin.:Devices form| ENS| O
:5131:304| Device combin.:Number of detect. dev.| INS| O
:5131:305| Device combin.:Fct. logout device 1| SPS| O
:5131:306| Device combin.:Fct. logout device 2| SPS| O
:5131:307| Device combin.:Fct. logout device 3| SPS| O
:5131:309| Device combin.:Fct. logout device 4| SPS| O
:5131:310| Device combin.:Fct. logout device 5| SPS| O
:5131:311| Device combin.:Fct. logout device 6| SPS| O
:5131:312| Device combin.:Device 1 available| SPS| O
:5131:313| Device combin.:Device 2 available| SPS| O
:5131:314| Device combin.:Device 3 available| SPS| O
:5131:315| Device combin.:Device 4 available| SPS| O
:5131:316| Device combin.:Device 5 available| SPS| O
:5131:317| Device combin.:Device 6 available| SPS| O
Prot. interf.1
:5161:81| Prot. interf.1:>Block stage| SPS| I
:5161:500| Prot. interf.1:>Sync reset| SPS| I
:5161:341| Prot. interf.1:Reset synchronization| SPC| C
:5161:342| Prot. interf.1:Reset measurements| SPC| C
:5161:52| Prot. interf.1:Behavior| ENS| O
:5161:53| Prot. interf.1:Health| ENS| O
:5161:301| Prot. interf.1:Status of lay. 1 and 2| ENS| O
:5161:302| Prot. interf.1:Status of lay. 3 and 4| ENS| O
:5161:303| Prot. interf.1:Connection broken| SPS| O
:5161:316| Prot. interf.1:Error rate / min exc.| SPS| O
:5161:317| Prot. interf.1:Error rate / hour exc.| SPS| O
:5161:318| Prot. interf.1:Time delay exceeded| SPS| O
:5161:319| Prot. interf.1:Time delay different| SPS| O
:5161:320| Prot. interf.1:Time delay jump| SPS| O
:5161:321| Prot. interf.1:PI synchronized| SPS| O
:5161:340| Prot. interf.1:Telegram lost| SPS| O
:5161:308| Prot. interf.1:Tx tel/h| MV| O
:5161:309| Prot. interf.1:Rx tel/h| MV| O
:5161:310| Prot. interf.1:Tx tel/min| MV| O
:5161:311| Prot. interf.1:Rx tel/min| MV| O
:5161:312| Prot. interf.1:Tx err/h| MV| O
:5161:313| Prot. interf.1:Rx err/h| MV| O
:5161:314| Prot. interf.1:Tx err/min| MV| O
:5161:315| Prot. interf.1:Rx err/min| MV| O
:5161:334| Prot. interf.1:Miss.tel/min| MV| O
:5161:335| Prot. interf.1:Miss.tel/h| MV| O
:5161:336| Prot. interf.1:Miss.tel/d| MV| O
:5161:337| Prot. interf.1:Miss.tel/w| MV| O
:5161:338| Prot. interf.1:M. loss/d| MV| O
:5161:339| Prot. interf.1:M. loss/w| MV| O
:5161:331| Prot. interf.1:Recept.| MV| O
:5161:323| Prot. interf.1:PPS: time del. unsym.| SPS| O
:5161:324| Prot. interf.1:PI with PPS synchron.| SPS| O
:5161:325| Prot. interf.1:Aver.Δt| MV| O
:5161:326| Prot. interf.1:Rec. Δt| MV| O
:5161:327| Prot. interf.1:Sen. Δt| MV| O
Ext. Synchron.
:9181:500| Ext. Synchron.:>Block stage| SPS| I
:9181:501| Ext. Synchron.:>PPS pulse loss| SPS| I
:9181:52| Ext. Synchron.:Behavior| ENS| O
:9181:54| Ext. Synchron.:Inactive| SPS| O
:9181:53| Ext. Synchron.:Health| ENS| O
:9181:301| Ext. Synchron.:PPS pulse loss| SPS| O
:9181:303| Ext. Synchron.:PPS pulse OK| SPS| O
:9181:302| Ext. Synchron.:PPS pulse| SPS| O
:9181:304| Ext. Synchron.:Synchronization loss| SPS| O
:9181:305| Ext. Synchron.:Synchronization OK| SPS| O
:9181:306| Ext. Synchron.:Synchronization pulse| SPS| O
Meas.val.dev.1
:1351:6811:300| Meas.val.dev.1:Dev.adr.| INS| O
:1351:6811:301| Meas.val.dev.1:CB| ENS| O
:1351:6811:302| Meas.val.dev.1:Vph| WYE| O
:1351:6811:303| Meas.val.dev.1:Iph| WYE| O
Meas.val.dev.2
:1351:6841:300| Meas.val.dev.2:Dev.adr.| INS| O
:1351:6841:301| Meas.val.dev.2:CB| ENS| O
:1351:6841:302| Meas.val.dev.2:Vph| WYE| O
:1351:6841:303| Meas.val.dev.2:Iph| WYE| O
Meas.val.dev.3
:1351:6871:300| Meas.val.dev.3:Dev.adr.| INS| O
:1351:6871:301| Meas.val.dev.3:CB| ENS| O
:1351:6871:302| Meas.val.dev.3:Vph| WYE| O
:1351:6871:303| Meas.val.dev.3:Iph| WYE| O
Meas.val.dev.4
:1351:6901:300| Meas.val.dev.4:Dev.adr.| INS| O
:1351:6901:301| Meas.val.dev.4:CB| ENS| O
:1351:6901:302| Meas.val.dev.4:Vph| WYE| O
:1351:6901:303| Meas.val.dev.4:Iph| WYE| O
Meas.val.dev.5
:1351:6931:300| Meas val.dev.5:Dev.adr.| INS| O
:1351:6931:301| Meas val.dev.5:CB| ENS| O
:1351:6931:302| Meas val.dev.5:Vph| WYE| O
:1351:6931:303| Meas val.dev.5:Iph| WYE| O
Meas.val.dev.6
:1351:6961:300| Meas.val.dev.6:Dev.adr.| INS| O
:1351:6961:301| Meas.val.dev.6:CB| ENS| O
:1351:6961:302| Meas.val.dev.6:Vph| WYE| O
_:1351:6961:303| Meas.val.dev.6:Iph| WYE| O

3.4.6 Advanced Protection Communication
3.4.6.1 Overview
The advanced protection communication contains all functionalities of classic protection communication. The view of parameters and indications is structured differently in DIGSI 5. In addition, the advanced protection communication supports the IP-based communication protocol.
You can easily change the number of devices in the device combination. Further differences include support for external synchronization sources and an exchange of phase-selective information while sending and receiving.
In the DIGSI 5 library, you can find the available function groups for the advanced protection communication in the Advanced protection communication folder. The following function-group types can be instantiated:
• FG Protection communication type 1 (line differential protection)
• FG Protection communication type 2
For configurations with line differential protection, instantiate the FG Protection communication type 1 (line differential protection). In all other cases, instantiate the FG Protection communication type 2.
3.4.6.2 Advanced Protection Communication in the Overall System
The Advanced protection communication is integrated as follows in the overall system:

Figure 3-78 Advanced Protection Communication in the Overall System

1. The following applies for the FG Line and the FG Voltage/Current 3-phase: You must route the connection between the protection FG and the FG Protection communication in DIGSI 5.
2. You must assign a channel to the protection interface, see Parameter: PI assignment, Page 126.

3.4.6.3 Structure of the FG Protection Communication916fc571a17ec17e9da35239179b658b
The instantiated FG Protection communication contains the FBs for a protection interface and for the device combination. If you need a 2nd protection interface, add another instance.
The FG Protection communication contains the following functionalities and function blocks (FB):

• FB Device combination

• FB for the Protection interface
  In addition, the following FBs can be instantiated:

• A 2nd protection interface
  You can find the 2nd protection interface in the Global DIGSI 5 library under Extended protection communication > Second protection interface.

• 1 or 2 FBs for the External synchronization of the transmitted measured values by an external synchronization pulse (1-second pulse, PPS) or via the IEEE 1588 synchronization protocol You can find the FB External synchronization in the Global DIGSI 5 library under Extended protection communication > Synchronization.

• The FB Remote data is instantiated automatically, as soon as you configure remote data.

• The FB Phase swap

Figure 3-79 Structure of the FG Extended Protection Communication

Device Combination
The function Device combination manages the devices that exchange data via the protection communication.
The following FBs are preconfigured in the device combination:

• FB General

• FBs for each device in the device combination
  In the Device combination, you configure general settings for the protection communication and the device addresses. The function Device combination issues the following indications:

• General indications like the
  – Amount of devices
  – Type and status of the device topology

• Indications of the devices in the device combination like:
  – The availability of the device
  – The state of the device, that is whether the device is logged on or off in the device combination
  – Measured values of the device that have been recorded and synchronized through the device combination (constellation measured values)
  – Test of the function Line differential protection in the device combination (only for protection communication type 1)
  – Test of the function Line differential protection in the local device (only for protection communication type 1)

Protection Interface
The FB Protection interface transmits and receives signals and measured values to/from the partner device.
For this, the protection interface uses the channel of a communication module.

External Synchronization
Measured values that are acquired and exchanged in the devices at the same time, with microsecond accuracy are transmitted via the protection communication. The measured values can be synchronized as follows:

• Internally via the telegram measurement with the Ping-Pong method
• Externally via
  – An external, synchronous pulse 1-second-pulse (PPS)
  – Via the IEEE 1588 protocol

If you want to use an external synchronization, you must instantiate the FB External synchronization.
You can use a different synchronization procedure for the 2nd protection interface than for the 1st protection interface.

Remote Data
If you want to exchange selected and user-specific data or measured values via the protection communication, you must use the Remote data function. If you route a specific signal or a measured value to the protection communication, the device automatically creates the Remote data functionality. The routed signals are then transmitted and received via the protection interface. The available bandwidth limits the amount of remote data that can be transmitted.

Phase Swap
If you want to exchange information via the protection communication with a device showing phases with a different sequence but with the same rotating field as your device, the SIPROTEC 5 device can swap the phase information when sending and receiving. It is no longer necessary to swap phases when connecting the current transformers.
This use case exists on some tie lines of different power-system operators.
For more information, refer to 3.4.6.12 Description Phase Swapping and 3.4.6.13 Setting Notes for Phase Swapping.

3.4.6.4 Configuration of the Advanced Protection Communication in DIGSI 5
Steps during Configuration
Siemens recommends the following procedure when configuring the advanced protection communication:

• Select the desired communication module.
• Select the protocol Adv.Prot.Intf..
• The further parameterization depends on the selected communication module and is described in the following under:
  – Advanced Protection Interface for a USART Communication Module, Page 123
  – Advanced Protection Interface for an Ethernet-BD Communication Module, Page 125

Advanced Protection Interface for a USART Communication Module

Figure 3-80 USART Communication Module: Selection of the Protocol Advanced Protection Interface
After selecting the protocol, click Settings in the right column to get to the connection settings of the USART protection-interface module for channel 1.

Figure 3-81 USART Communication Module: Settings for the Advanced Protection Interface

Parameter: Connection via
• Default setting (_:105) Connection via = fiber optic
The Connection via parameter is used to set the bit rate required for the protection interface. Different discrete values can be entered depending on the means of communication (see following table).

Table 3-17 Communication Media

5 to
Figure 3-4 9| fiber optic| 2 MBitls
CC-XG-512 communication converter| Figure 3-5 0| CCXG 512 kBit/s| 512 kBitls
CC-XG-128 communication converter| Figure 3-5 0| CCXG 128 kBit/s| 128 kBitls
CC-XG-64 communication converter| Figure 3-5 0| CCXG 64 kBit/s| 64 kBitls
Repeater 512 communication converter| Figure 3-5
3| repeater 512 kBit/s| 512 kBitls
CC-CC-128 communication converter| Figure 3-5 2| CCPW 128 kBit/s| 128 kBit/s
CC-2M-512 communication converter| Figure 3-5 1| CC2M 512 kBit/s| 512 kBitls
Multiplexer with C37.94 interface| Figure 3-5
4| C37.94 1 64 kBit/s
c37. 94 2 64 kBit/s
C37.94 8 * 64 kBit/s| 64 kBitls 128 kBitls 512 kBitls
Other (freely adjustable bit rates for a direct connection for special applications)| | 64 kBit/s 128 kBit/s 512 kBit/s 2048 kBit/s| 64 kBitls 128 kBitls 512 kBitls 2048 kbitis

Parameter: Multiplex operation
• Default setting (_:112) Multiplex operation = no
With the parameter Multiplex operation, you can designate the physical channel for multiplex operation. You can then route 2 protection interfaces to this channel.
Refer to 3.4.3 Function Description.
NOTE For safety reasons, you cannot route 2 protection interfaces from the same device combination to one channel, as this results in apparent redundancy.

Advanced Protection Interface for an Ethernet-BD Communication Module

Figure 3-82 Ethernet-BD Communication Module: Selection of the Protocol Advanced Protection Interface

After selecting the protocol, click Settings in the right column to get to the connection settings of the Ethernet-BD communication module for channel 1.

Figure 3-83 Ethernet-BD Communication Module: Settings for the Advanced Protection Interface

Parameter: UDP Port
• Default setting (_:112) User port = 33000
With the UDP port parameter, you set the value of the destination port in the UDP header of the protection interface IP messages. You must set the same value for the parameter UDP
port for all protection devices of a device combination that use the IP-based protection interface. Different device combinations can use the same value for the
UDP port parameter. Normally, the default setting can always be applied. It can be necessary, for example, due to firewall policies, to configure a UDP port that differs from the default setting.
Parameterize the IP address of the Ethernet-BD communication module in the properties of the module.

Figure 3-84 Parameterization of the IP Address for the Ethernet-BD Communication Module

The configuration and parameterization of the protection-interface communication module is now complete.

3.4.6.5 Setting Notes for the Protection Interface
The chapters provides setting notes for the logical protection interface (FB Protection interface).

Parameter: PI assignment
• Default setting (_:5161:120) PI assignment = Setting options depend on configuration
In addition, you must select the channel for the protection interface in DIGSI 5 as follows: Project tree > Prot. com. > Prot. interf..
In the input area under PI assignment, select the channel of a communication module that supports the required protection-interface protocol. As a prerequisite for this, you must have selected the protocol Advanced protection interface for the channel of the desired communication module, see
3.4.6.4 Configuration of the Advanced Protection Communication in DIGSI 5.

Figure 3-85 Assignment of the Protection-Interface Channel to the Protection Interface

Parameter: Max. error rate per hour
• Default setting (_:5161:105) Max. error rate per hour = 1.0%
If the number of faulty telegrams per hour exceeds the value set in the parameter Max. error rate per hour, you receive the error message Error rate / hour exc..

Parameter: Max. error rate per min
• Default setting (_:5161:106) Max. error rate per min = 1.0%
If the number of faulty telegrams per minute exceeds the value set in the parameter Max. error rate per min, you receive the error message Error rate / min exc..

Parameter: Disturbance alarm after
• Default setting (_:5161:107) Disturbance alarm after = 100 ms
With the parameter Disturbance alarm after, you determine the time delay after which faulty or missing telegrams are signaled as disturbed with the indication Status of lay. 1 and 2 = PI data fault.

Parameter: Transm. fail. alarm after
• Default setting (_:5161:108) Transm. fail. alarm after = 6.0 s
With the parameter Transm. fail. alarm after, you determine the time delay after which a communication failure is signaled with the indication Status of lay. 1 and 2 = PI data
failure.

Parameter: Delay time threshold
• Default setting (_:5161:109) Delay time threshold = 30.0 ms
The time taken to transmit and receive a signal via a protection connection is called the signal-transit time.
You can monitor the signal-transit time. For the Delay time threshold, the default setting is selected in such a way that it is not exceeded by normal communication networks. If the signal-transit time is exceeded during operation (for example, upon switchover to another transmission path), the indication Time delay exceeded is issued.
Increased runtimes only affect the operate time, and therefore the fault- clearing time of the protection functions that use the protection interface. If you use the Line differential protection function, this remains in effect.

Parameter: Difference Tx and Rx time
• Default setting (_:5161:110) Difference Tx and Rx time = 0.1 ms
For a time synchronization of the measured values with microsecond accuracy by means of telegram measurement, the signal-transit times in the transmission and receive direction must be approximately the same.
The device monitors the signal-transit times in the transmission and reception direction.
With the Difference Tx and Rx time parameter, you can set a maximum permitted signal-transit time difference between the transmission and reception paths (runtimes unbalanced). Set the parameter Difference Tx and Rx time to the maximum difference expected. Set this value to 0 for a direct fiber-optic connection. A higher value is necessary for transmission via communication networks. 0.1 ms (recommended setting value) is the reference value. If the difference in the signal-transit times between the transmission and reception path exceeds the set value, the indication Time delay jump is issued. If the difference in the signal-transit times between the transmission and reception path exceeds the set value and remains for more than 5 s, the indication Time delay different is issued. The Line differential protection function is no longer working properly and is ineffective.

NOTE The Difference Tx and Rx time parameter only visible if the Line differential protection function is instantiated and the parameter Synchronization is not set to External synch. only.
NOTE If you use a multiplexer with a C37.94 interface as a communication medium, Siemens recommends a setting value of 0.25 ms to 0.6 ms.

Parameter: Synchronization

• Default setting (_:5161:113) Synchronization = External synchron. off
  With the parameter Synchronization, you control the time synchronization of the measured values with microsecond accuracy.
  The parameter Synchronization is only visible if you have instantiated the FB External synchronization from the Global DIGSI 5 library in the FG Protection communication.
  If you have not instantiated the FB External synchronization, the measured values are time-synchronized internally with microsecond accuracy.

No external synchronization is performed on the protection interface. Select this setting value if you do not expect any differences between the signaltransit times in the transmission and reception directions. Then, the
measured values are only synchronized internally with the telegram measurement.
Telegr. and ext. synch.| Synchronization via telegram measurement and external synchronization:
The measured values are synchronized internally with the telegram measurement, supported by the external synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of
a satellite receiver and configurable in the FB External synchronization.
In this case, an existing line differential protection is only enabled when a new connection is established and one of the following conditions is met.
• The protection connection is synchronized with the help of the external synchronization.
• Symmetric signal-transit times are signaled via the binary input signal <Sync-Reset or the controllable Resetting sync.. This means that the signal- transit times are the same in the send and receive direction.
Telegr. or ext. synch.| Synchronization via telegram measurement and external synchronization:
The measured values are synchronized internally with the telegram measurement, supported by the external synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of
a satellite receiver and configurable in the FB External synchronization.
In this case, an existing line differential protection is only enabled when a new connection is established and one of the following conditions is met.
• The protection connection is synchronized with the help of the external synchronization.
• Symmetric signal-transit times are signaled via the binary input signal <Sync-Reset or the controllable Resetting sync.. This means that the signal- transit times are the same in the send and receive direction.
Telegr. or ext. synch.| Telegram measurement or external synchronization:
The measured values are synchronized internally with the telegram measurement, supported by the external synchronization. The synchronization is possible via the IEEE 1588 protocol or via the synchronous pulse of
a satellite receiver and configurable in the FB External synchronization.
An existing line differential protection is enabled immediately upon renewed establishment of a connection (data telegrams are received).
The internal synchronization is used up to synchronization.
External synch. Only| External synchronization only:
The measured values are synchronized only via the external synchronization.
You can set the external synchronization in the FB External synchronization. This enables synchronization via the IEEE 1588 protocol or via the synchronous pulse of a satellite receiver.

NOTE
If the protection interface is connected to a channel on a USART communication module (see Parameter: PI assignment, Page 126), the external synchronization is used to take into account the signal-transit times in the transmission and receive direction.
If the external synchronization fails for a short time, for example, due to a receiving interference or an unfavorable satellite position for a brief period, the internal synchronization via the telegram measurement is still active.

NOTE
If the protection interface is connected to a channel on an Ethernet-BD communication module (see Parameter: PI assignment, Page 126), the parameter Synchronization is permanently set to External synch. only.

Parameter: FB External synchron.
• Default setting (_:5161:117) FB External synchron. = Ext. synchronization 1
With the external synchronization, the time synchronization of the measured values with microsecond accuracy is possible through an external synchronization source.
The parameter FB External synchron. is only visible if you have instantiated at least 1 FB External synchronization from the Global DIGSI 5 library into the FG Protection communication. You can instantiate a maximum of 2 FBs for external synchronization.
With the parameter FB External synchron., you specify whether the protection interface uses the FB Ext. synchronization 1 or the FB Ext. synchronization 2 for the synchronization. You parameterize the synchronization source in the corresponding FB External synchronization, see 3.4.6.9 Setting Notes for External Synchronization.

NOTE
The external synchronization is possible separately for each protection interface.

Parameter: Check synchron.-source
• Default setting (:5161:121) Check synchron.-source = yes
With the parameter Check synchron.-source, you can switch the synchronization- sources check on or off. During the check of the synchronization sources on the ends of a protection connection, a check is conducted as to whether both synchronization sources are working in the same synchronization status SmpSynch.
If both synchronization sources are working in the synchronization status SmpSynch = global, the inspection has been passed.
If both synchronization sources are working in the synchronization status SmpSynch = local, that is decoupled from a global reference time, an additional check is conducted as to whether the synchronization source ( gmIdentity) is the same. Synchronicity can only be guaranteed if the synchronization sources are the same.
If the synchronization sources display a different synchronization status, that is one displays the synchronization status SmpSynch = local and the other the synchronization status SmpSynch = global, synchronization cannot be guaranteed.
Siemens recommends using the default setting Check synchron.-source = yes.
If you have problems with the synchronization-source check, you can switch off the synchronization-source check. Switch off the synchronization-source check only if the synchronization sources are synchronous at the end of their protection connection. The parameter Check synchron.-source is visible only if the parameter (:5161:113)  ynchronization is set to External synch. only.

NOTE
If you use PPS electrical (port G) as the synchronization source, the synchronization status (SmpSynch) is permanently set to global.
If you use PPS optical (USART) as the synchronization source, you can use the parameter (:107) Received. SmpSynch to set the synchronization status to (SmpSynch) local or global.
For a synchronization with microsecond accuracy, for example, for the Line differential protection, set the parameter (:107) Received. SmpSynch = global.

3.4.6.6 Indications and Measured Values of the Advanced Protection Interface
Each individual protection interface provides different indications for commissioning and diagnostics of communication:
Indication (_:5161:301) Status of lay. 1 and 2
The indication (_:5161:301) Status of lay. 1 and 2 informs you about the status of the connection. The following indications are possible:

Table 3-18 Status Indications Status of lay. 1 and 2

state.
PI connected:| The protection interface is connected to the protection interface of the partner device.
PI data fault:| The protection interface has not received any valid telegrams for the time set in parameter (:5161:107) Disturbance alarm after.
PI data failure:| The protection interface has not received any valid telegrams for the time set in parameter (:5161:108) Transm. fail. alarm after.
not existing:| The protection interface has not been assigned to a communication channel.

Indication (_:5161:302) Status of lay. 3 and 4
The indication (_:5161:302) Status of lay. 3 and 4 informs about errors during the connection establishment. The following indications are possible:

versions of the devices are incompatible.
Update the firmware.
wrong dev. ID:| The connection is not established because the device address of the local device or the partner device is incorrect or set incorrectly.
Check the settings for the parameters Address of device 1 to
Address of device n ( :5131:102 and following).
const.sett.error:| The connection is not established because the parameters are set differently.
Check whether the parameter (:5131:122) Lowest appearing bit rate has been set the same in all devices in the device combination.
diff.sett error:| The connection is not established because the parameters are set differently.
The line differential protection settings for the connected devices are incompatible. Check whether both devices are set to operate with or without line differential protection.
The rated current of the line (parameter (:9001:101) Rated current) must have the same setting in all
devices.
With a transformer in the line, the (:9001:103) Rated apparent
power must be set to the same value in all devices.
net mirroring| The connection is not established. The protection interface is receiving its own data.
Check the wiring.
wrong dev. idx.| The connection is not established because the device index of the local device or the partner device is incorrect.
Check the setting for the parameter (_:5131:101) Local device is device.

Furthermore, the following output signals are available:

(:5161:303) Connection
broken| The signal Connection broken indicates that during a parameterized time (parameter (:5161:107) Disturbance alarm after) no telegrams or faulty telegrams were continuously received. If the indication Connection broken is issued, the affected protection connection is reset. This can cause the blocking of an active line differential protection or a ring topology can change to a chain topology.
(:5161:316) Error
rate / min exc.| The signal Error rate / min exc. indicates that the set maximum error rate per minute (Parameter (:5161:106) Max. error rate per min) has been exceeded.
In this manner, a brief increase of the operate time and thus of the faultclearing time is possible for the protection functions using the protection interface. If you use the Line differential protection function, this remains
in effect.
(:5161:317) Error
rate / hour exc.| The signal Error rate / hour exc. indicates that the set maximum error rate per hour (Parameter (:5161:105) Max. error rate per hour) has been exceeded.
In this manner, a brief increase in operate time and thus the fault-clearing time is possible for the protection functions using the protection interface. If you use the Line differential protection function, this remains in effect.
(:5161:318) Time delay
exceeded| The signal Time delay exceeded indicates that the threshold value for the set signal runtime (parameter (:5161:109) Delay time threshold) has been exceeded.
Increased runtimes only affect the operate time, and therefore the faultclearing time of the protection functions using the protection interface.
If you use the Line differential protection function, this remains in effect.
(:5161:319) Time delay different| The signal Time delay different indicates that the threshold value for the difference in signal runtimes in the transmission and reception direction (asymmetrical runtimes) has been exceeded. The setting value results from
the setting value of the parameter (:5161:110) Difference Tx and Rx time.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch.
only.
If the indication Time delay different appears, the Line differential protection function is no longer working properly and is ineffective.
(:5161:320) Time delay jump| The signal Time delay jump indicates that the signal runtimes of the data changed abruptly. This is caused by a switchover of the communication path in the communication network.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch.
only.
(:5161:321) PI synchronized| The signal PI synchronized indicates that the synchronization with microsecond accuracy of the measured values transferred between the local device and partner device is working correctly.
The indication is visible only if the parameter (:5161:113) Synchronization is not set to External synch. only.
(:5161:340) Telegram lost| The signal Telegram lost indicates that an expected telegram has failed to arrive or a faulty telegram has been received. If you want to assign the communication failures or faults to other events, route the signal Telegram lost temporarily into the operational log. Such events can be switching operations in the primary system or operations on the components of the communication network.
Note: If the signal is constantly routed, the operational log can overflow.
Siemens recommends routing the signal only for clarification of problems.
(:5161:343) Partner| The indication shows the address of the partner device. A value of 0 means that no partner address is available.
(:5161:323) PPS: time del. unsym.| This indication is only visible if you are working with a synchronous pulse.
The indication shows that the difference in the signal runtimes between the sending and receiving path exceeds the value set with the parameter (:5161:110) Difference Tx and Rx time.
Note: The Line differential protection function remains effective.
(:5161:324) PI with PPS synchron.| This indication is only visible if you are working with a synchronous pulse.
This indication is only visible if, in parallel to synchronization with the synchronization pulse, you are also working with the synchronization via telegram measurement. If both synchronization methods are working properly, the indication PI with PPS synchron. = RAISING is generated.

Measured Values of the Protection Interface
The protection interface provides the following measured value for the diagnosis of the protection-interface communication:

transmission and reception direction divided by 2, without external synchronization)
(:5161:326) Rec. Δt| Signal runtime for reception path (with external synchronization)
(:5161:327) Sen. Δt| Signal runtime for transmission path (with external synchronization)
(:5161:334) Miss.tel/min| Number of telegram failures within the last minute
(:5161:335) Miss.tel/h| Number of telegram failures within the last hour
(:5161:336) Miss.tel/d| Number of telegram failures within the last day
(:5161:337) Miss.tel/w| Number of telegram failures within the last week
(:5161:338) M. loss/d| Longest lasting telegram failure within the last day
(:5161:339) M. loss/w| Longest lasting telegram failures within the last week
(_:5161:331) Recept.| Receipt of a telegram (0 = no receipt, 1 = receipt)
You can use this indication to make the telegram exchange visible in the fault record.

NOTE
You can reset the measured values of the protection interface directly in the device. Proceed as follows:
Device functions > Protection comm. (Type x) > Protection interface y > Reset measured values.

3.4.6.7 Setting Notes for the Device Combination
In the Project tree > Settings > Protection comm. (type 1) or Protection comm. (type 2), select the function block Device combination. In the input area, you parameterize the general settings for the device combination, instantiate the number of devices in the device combination, and set the parameters for each device. A device combination consists of at least 2 devices.

Parameter: Local device is device
• Default setting (_:2311:101) Local device is device = 1
With the Local device is device parameter, you set the index (number) of your device in the device combination. A maximum of 6 devices can be present in a device combination.

Parameter: Lowest appearing bit rate
• Default setting (_:2311:122) Lowest appearing bit rate = 64 kBit/s
With the parameter Lowest appearing bit rate, you set the lowest bit rate occurring in the device combination. This value determines the maximum number of signals and measured values to be transferred in the Remote data function within the device combination.

EXAMPLE:
For a device combination consisting of 3 devices in a ring topology with 2 fiber-optic connections (2 MBit/s) and a 64-kBit/s connection, set the smallest value (64 kBit/s) in each device.

Apart from the default value, you can set the following bit rates:

• 128 kBit/s
• 512 kBit/s
• 2048 kBit/s

NOTE If you use optical fibers for all protection connections, set the value to 2048 kBit/s.

Connection mode
• Default setting (_:2311:126) Connection mode = SIPROTEC 5
With the parameter Connection mode, you select the device type with which the SIPROTEC 5 device works in the device combination via the protection connections.

NOTE As soon as a SIPROTEC 4 device is present in the device combination, the SIPROTEC 5 devices must operate in a compatibility mode. For this reason, the parameter Connection mode must be set to the same value in all SIPROTEC 5 devices in the device combination. Select the type of SIPROTEC 4 device from the following table:

combination.
SIPROTEC 4 7SD610| The SIPROTEC 5 device works with a SIPROTEC 4 differential protection device 7SD610 with firmware version V4.72 and higher in the device combination.
SIPROTEC 4 7SD5| The SIPROTEC 5 device works with a SIPROTEC 4 differential protection device 7SD5x with firmware version V4.72 and higher in the device combination.
SIPROTEC 4 7SA5/6| The SIPROTEC 5 device works with a SIPROTEC 4 distance protection device 7SA522 and 7SA6x with firmware version V4.70 and higher in the device combination.

Parameter: Dev. comb. is time source
• Default setting (_:2311:129) Dev. comb. is time source = yes
The parameter Dev. comb. is time source is only visible if you have instantiated several function groups Protection comm. and you have selected the setting value PI for the parameters Time source 1 or Time source 2.
The parameter Dev. comb. is time source determines from which FG Protection comm. the time is taken over.

Parameter: Protection com.
• Default setting (_:2311:128) Protection com. = Type 1 (Line diff. prot.)
The parameter Protection com. is write-protected and displays only the type of the instantiated device combination.
The device combination Type 1 (Line diff. prot.) supports the function Line differential protection.
The device combination Type 2 (no Line diff. pr.) does not support the function Line differential protection.

NOTE In the Global DIGSI 5 library, the function groups Protection communication type 1 (line diff. protection) and Protection com. Type 2 are available for the advanced protection communication. When instantiating the respective function group, the corresponding type of the device combination is automatically pre-instantiated.

NOTE If you have instantiated the FG Protection com. Type 2, the Device combination Type 2 is automatically pre-instantiated in this FG and the Line differential protection function is not supported. If you subsequently want to use the Line differential protection function in the device combination of the
FG Protection com. Type 2, proceed as follows:

• In the DIGSI 5 project tree, delete the function block Device combination from the FG protection comm. (type 2).
• Instantiate the function block Device combination type 1 (line diff. protection) from the Global DIGSI 5 library into the FG Protection com. Type 2.
• Parameterize the device combination in the input area again.
• Reroute the indications of the device combination in the DIGSI 5 information routing. All other parameterizations and routings are retained!

Parameter: Device index

• Default setting (_:22711:101) Device index = 1
• Default setting (_:22712:101) Device index = 2
• Default setting (_:22713:101) Device index = 3
• Default setting (_:22714:101) Device index = 4
• Default setting (_:22715:101) Device index = 5
• Default setting (_:22716:101) Device index = 6

The value of the parameter Device index is the number of the device in the device combination. Set the device index in all devices of a device combination for the same devices in the same way. The device indices must start with 1 and be incremented continuously. DIGSI 5 assigns the device indices automatically. You can change the device indices if necessary.

NOTE
The device with the Device index = 1 is the timing-master device in a device combination.
If all other devices in the device combination are to obtain their time from the timing-master device, consider the following

• Set the Device index to 1 for the timing-master device.
• Parameterize the other devices in such a way that they get their time from the timing-master device via the protection connections.

For more information, refer to 3.5.3 Function Description. Select Protection interface as the adjustable synchronization option.
In the timing-master device, you must not set the protection interface as the synchronization source!

Parameter: Address in Device combi.

• Default setting (_:22711:102) Address in Device combi. = 101
• Default setting (_:22712:102) Address in Device combi. = 102
• Default setting (_:22713:102) Address in Device combi. = 103
• Default setting (_:22714:102) Address in Device combi. = 104
• Default setting (_:22715:102) Address in Device combi. = 105
• Default setting (_:22716:102) Address in Device combi. = 106
  With the parameter Address in Device combi., you assign a unique and unambiguous address for each device.

NOTE
If the preset values do not fit, Siemens recommends the following procedure:
Define a number for the device combination that is unambiguous in your area of responsibility and that must be at least 2 digits, for example, 100. The setting value of the parameter Address in Device combi. is then calculated as follows: Number in the device combination + Device index. For device 2, this leads to Address in Device combi. = 102.

Parameter: IP Address

• Default setting (_:22711.103) IP address = 0.0.0.0
• Default setting (_:22712.103) IP address = 0.0.0.0
• Default setting (_:22713.103) IP address = 0.0.0.0
• Default setting (_:22714.103) IP address = 0.0.0.0
• Default setting (_:22715.103) IP address = 0.0.0.0
• Default setting (_:22716.103) IP address = 0.0.0.0

The IP address of the local device is taken from the settings of the Ethernet- BD communication module and displayed. The local IP address cannot be edited at this point.

NOTE
If all devices of a device combination are equipped with an Ethernet-BD communication module and use the IP communication, you must enter the IP addresses for all other devices in the device combination here. The topology detection automatically sets a ring or chain topology.

NOTE
If you have a hybrid configuration, that is not all protection connections of a device combination use the IP communication, you must observe the following when setting the IP addresses:

• The topology detection does not generate the topology automatically.
• First define the order for the communication between the devices. Define chain or ring topologies for this purpose.

The defined topology results in the partner devices for each device, with which the device communicates directly.
Only set the IP addresses for the partner devices that are equipped with an Ethernet-BD communication module here.

• You can find examples of the parameterization of the IP addresses in hybrid configurations in the chapters 3.4.8.4 Device Combination of 3 Devices and Hybrid Communication Media and 3.4.8.5 Device Combination of 6 Devices and Hybrid Communication Media.

Indications and Measured Values in the Device Combination

(:3321:2311:301)
Status of topo. recog.| The devices form a topology via the protection connections. This indication shows the status of the topology detection and can have the following values:
• Unknown: The topology is unknown.
• Invalid: The detected topology is not supported.
• Transient: The topology has just been modified.
• Valid: The topology has been detected. The indication Devices form shows the type of the detected topology.
(:3321:2311:302)
Topology is| The indication shows whether all configured devices in the device combination communicate with each other via the protection connections.
The indication can have the following values:
• Unknown: The topology is unknown.
• Incomplete: At least one device in the device combination does not communicate via the protection connections.
• Complete: All configured devices in the device combination communicate via the protection connections.
(:3321:2311:303)
Devices form| This indication shows the type of the detected topology that the devices in the device combination form via the protection connections. The indication can have the following values:
• Unknown topol: The topology is unknown.
• Chain topology: The devices and their protection connections form a chain topology.
• Ring topology The devices and their protection connections form a ring topology.
(:3321:2311:304)
Number of detect. dev.| The indication shows the number of devices that communicate via the
protection connections in the device combination.

Indication and Measured Values of the Devices
The following indications and measured values are displayed for each device in the device combination and are explained using the example of a device.

in protection communication.
(:22711:317) is logged off| This indication shows whether the local device has been logged off. If the device has been logged off, it is no longer involved in communication via the protection interfaces. If a device has been logged off, information relevant for the protection functions is no longer exchanged.
(:22711:301) circuit breaker| This indication shows the position of the circuit breaker and can have the following values:
• 0: The switch position of the circuit breaker is unknown.
• 1 The circuit breaker is open.
• 2 The circuit breaker is closed.
(:22711:328) Line  diff. test 12| This message indicates whether the function Line differential protection is in the state Test or Test/Relay blk..
(:22711:329) Local Line diff. test 12| This message indicates whether the function Line differential protection is in the special test mode Test local device.

NOTE
The constellation measured values are only available for the FG Line.
Each device in the device combination determines measured values predefined by Siemens, known as constellation measured values. You can find the constellation measured values in the DIGSI 5 information routing under the FG Protection comm. (Type x) > Device combination > Device x. The following measured values and indications are issued for each device:

that is synchronized with all devices of the device combination. The absolute value and angle are issued for each phase.
(:3321:22711:303) Iph| This measured value shows the current of the 3 phases that is synchronized with all devices of the device combination. The absolute value and angle are issued for each phase.
(:3321:22711:304) f| The measured value supplies the locally calculated frequency of the measured voltage or the current.

The constellation measured values have the following properties:

• They are synchronized in the devices in a device combination.
• They are substituted using the protection interface.
• They are available on every device.

You can view the constellation measured values with DIGSI 5.
In the device, current and voltage measured values are displayed in absolute value and phase as a percentage.
100 % conform to the rated current or the rated voltage of the line (see Figure 3-86). These measured values are recorded every 2 seconds by the devices involved in the device combination and then sent to the other respective devices. At the same time, the current and voltage values of the different devices are time-synchronous with one another.
When displaying the constellation measured values the local device is prioritized. The device connected directly with DIGSI 5 is the local device.
The reference of the angle information depends on whether a line differential protection has been instantiated in the FG Line. If a line differential protection is instantiated, the protection communication is type 1, otherwise type 2.

• Protection communication Type 1:
  – The angle values of the voltages show the angle difference between the local and the remote voltage. The local voltage serves as the reference with an angle of 0°.
  – The angle values of the currents show the angle difference between the local and the remote current. The local current serves as the reference with an angle of 0°.

• Protection communication Type 2:
  The angles of the phase-to-ground voltages and the phase currents relate to the voltage VA of the relevant device.

You can find these measured values in the device under the following DIGSI mask:

Figure 3-86 Example of Constellation Measured Values with Phases

3.4.6.9 Setting Notes for External Synchronization
With the FB External synchronization, you can synchronize the measured values of the devices connected via protection connections with microsecond accuracy using external synchronization sources (1*10E-06 s). The measured values transmitted via protection communication for the line differential protection must be time-synchronized. The synchronization is possible as follows:

• Internally via telegram measurement
• Externally via the IEEE 1588 protocol
• Externally via a synchronous pulse from a satellite receiver

If you use Ethernet-BD communication modules for the protection communication of the line differential protection, the external synchronization of the measured values transmitted via the protection interface is mandatory.
If you use USART communication modules, you can synchronize the transmitted measured values either internally via telegram measurement or via external synchronization. If you do not use the external synchronization, the device automatically uses the internal synchronization.
If you want to use the external synchronization of the measured values, you must instantiate the FB External synchronization from the Global DIGSI 5 library into the FG Protection
comm.. You can find the External synchronization in the Global DIGSI 5 library under Advanced protection communication > Synchronization.
The external synchronization is possible for line differential protection applications or synchrophasor measuring devices as follows:

• Via a high-precision electrical synchronous pulse ( PPS electrical (Port G), 1-second pulse) from a satellite receiver at the time-synchronization interface (Port G)
• Via a high-precision optical synchronous pulse (PPS optical (USART), 1-second pulse) from a satellite receiver at a USART communication module
• Via the IEEE 1588 time-synchronization protocol

With external synchronization, you can measure and display the signal-transit time of the transmission and receive path separately. This allows you to achieve maximum sensitivity even with unequal (unbalanced) signal-transit times in communication networks with the line differential protection. For the transmission of protection data in the type 2 protection communication, different signal-transit times do not play a role.
If an FB External synchronization is instantiated, the parameter Synchronization is visible in the FB Protection interf.. With this parameter, you establish the connection between the protection interface and the type of external synchronization. See 3.4.6.5 Setting Notes for the Protection Interface. If you use 2 protection interfaces in the FG Protection comm., you can set a different synchronization source for each protection interface if required. For this use case, you must instantiate 2 FBs External synchronization into the FG Protection comm. and set the desired synchronization source separately.

Parameter: Name of synchron. block
• Default setting (_:101) Name of synchron. block = Ext. synchronization 1
The parameter FB External synchron. shows the name of the FB External synchronization.
If you have instantiated 2 FBs External synchronization into the FG Protection comm., you can use this parameter to switch between the FB Ext. synchronization 1 and the FB Ext. synchronization 2.

Parameter: Synchronization source
• Default setting (_:117) Synchronization source = nothing
With the parameter Synchronization source, you select the desired synchronization source for the external synchronization of the measured values.

NOTE The possible setting options of the parameter Synchronization source depend on the configuration of the protocol for the respective channel of the communication module.
To display the selection text for the selection of an optical synchronous pulse, you must configure the protocol PPS on a USART communication module as follows:

Figure 3-87 Configuration of the Optical Synchronous Pulse (PPS) on a Channel of a USART Communication Module

To display the selection text for the selection of the protocol IEEE 1588, you must configure the protocol IEEE 1588 on an Ethernet-BD communication module as follows:

Figure 3-88 Configuration of the Protocol IEEE 1588 on an Ethernet-BD Communication Module

The setting options for the parameter Synchronization source then look as follows, for example:

Figure 3-89 Possible Setting Options for the Synchronization Source

Depending on the configuration, the following synchronization sources are displayed:

receiver (PPS: 1 Pulse Per Second) at the time-synchronization interface Port G is the synchronization source.

1.PPS| The optical synchronization pulse of a satellite receiver (PPS: 1 Pulse Per Second) on channel 1 of a USART communication module is the synchronization source.

2.PPS| The optical synchronization pulse of a satellite receiver (PPS: 1 Pulse Per Second) on channel 2 of a USART communication module is the synchronization source.

1.IEEE 1588| The time-synchronization standard IEEE 1588 on an Ethernet-BD communication module is the synchronization source.

NOTE
You can select different synchronization sources for the same protection connection in the devices involved, for example, the synchronization via the IEEE 1588 protocol in device 1 and via the protocol PPS electrical in device 2.
Siemens recommends using the same synchronization source for the same protection connection. If it is not possible to use the same synchronization source, check the differential current in the line differential protection in the mode Test on all devices. If the differential current is not in the expected range, the set synchronization sources are not synchronous to each other and therefore not usable.

NOTE
For detailed information on the communication protocols, refer to the SIPROTEC 5 manual Communication Protocols.

Parameter: Synchronization using

• Default setting (_:118) Synchronization using = nothing
  This parameter Synchronization using cannot be adjusted. The parameter shows further information for the selected synchronization source:

receiver (PPS: 1 Pulse Per Second) at the time-synchronization interface Port G is the synchronization source.
PPS optical (USART)| The optical synchronization pulse of a satellite receiver (PPS: 1 Pulse Per Second) on channel 1 of a USART communication module is the synchronization source.
IEEE 1588| The time-synchronization standard IEEE 1588 on a BD communication module is the synchronization source.

Parameter: Max. inaccuracy
• Default setting (_:119) Max. inaccuracy = 0.500 ms
With the Max. inaccuracy parameter, you set the maximum expected inaccuracy of the synchronization sourced used. The set value is only effective if the synchronization source used does not supply any information on the current inaccuracy in the synchronization signals. If you no information on the inaccuracy of the synchronization source used, use the default setting.

NOTE The inaccuracy of the synchronization source enters the stabilization of the Line differential protection as an error signal.
This means that greater inaccuracy increases the calculated stabilization quantity and makes the Line differential protection less sensitive.
If IEEE 1588 is used as the synchronization source in the synchronization status SmpSynch = global, accuracy values are supplied with the synchronization signals and the parameter Max. inaccuracy is not used. If the supplied accuracy values become invalid, the value set in the parameter Max. inaccuracy is used.
If the synchronization source IEEE 1588 works in the synchronization status SmpSynch = local, then the value set in the parameter Max. inaccuracy is used as permanently available inaccuracy.
If PPS electrical (Port G) or PPS optical (USART) are used as synchronization source, then the value set in the parameter Max. inaccuracy is used as permanently available inaccuracy.
If a USART communication module with the PPS protocol and the PPS generator operating mode is also used as a synchronization source at the same time, the value set in the parameter Max. inaccuracy is used as permanently available inaccuracy.

3.4.6.10 Indications and Measured Values of the External Synchronization

visible with the following setting options of the parameter (:117) Synchronization source:
• G:Timesynchron.PPS
• Port:USART-AD-1FO.Channel x.PPS
• Port:USART-AE-2FO.Channel x.PPS
The binary input (:501) >PPS pulse loss can be used to signal an externally detected failure in the PPS synchronous pulse, for example, an error message from the satellite receiver. If the binary input (_:501)

PPS pulse loss is set, this leads to the indication (:304) Synchronization loss. The external synchronization detects immediately that there is a problem with the connected synchronization pulse.
Otherwise, the problem will only be noticed after approx. 2.1 s – after the test for synchronous-pulse
failure.
(:304) Synchronization loss| The synchronization has failed. This can be due to a problem with the synchronization source.
The indication (:304) Synchronization loss shows that the synchronization has failed. This can be due to the following reasons:
• The input indication (:501) >PPS pulse loss has occurred.
• The synchronous pulse has failed.
• The quality of the synchronous pulse is inadequate.
• There is another problem with the synchronization source.
(:305) Synchronization OK| The synchronization is operating correctly.
(:306) Synchronization pulse| You can use this indication to make the synchronous pulse visible. As a rule, one pulse is generated per second.
(:307) Synchron. Imprecise| If the set synchronization source operates in the global synchronization status and the time of the synchronization source deviates from the global time by more than 0.5 ms, the indication Synchron. imprecise is generated and the line differential protection becomes ineffective.
The indication Synchron. imprecise is visible if you select ETHBD- 2FO.Channel1.IEEE1588 in the parameter :103 Synchronization
source. The read-only parameter (_:118) Synchronization using
then displays IEEE 1588.

Figure 3-90 Logic for the Generation of the Indication >PPS pulse loss

3.4.6.11 Setting Notes for the Remote Data
Parameter: Dropout Time Prio. x

• Default setting (_:22741:111) Dropout time prio. 1 = 2.00 s
• Default setting (_:22741:112) Dropout time prio. 2 = 2.00 s
• Default setting (_:22741:113) Dropout time prio. 3 = 2.00 s

If you use user-specific remote data, you can set how long the last received state of your remote data is held in case of a communication failure. This allows you to bridge short-term communication failures. The time can be set separately for each priority of the remote data.

3.4.6.12 Description Phase Swapping
Phase Swap
If you want to exchange information via the protection communication with a device showing phases with a different sequence but with the same rotating field as your device, the SIPROTEC 5 device can swap the phase information when sending and receiving. It is no longer necessary to swap phases when connecting the current transformers.
This use case exists on some tie lines of different power-system operators. Figure 3-91 shows an example of the different designation of the same phases at the line ends. For example, phase A on the left side of the line becomes phase C on the right side. If a SIPROTEC 5 device is used on the right side, you can instantiate the FB Phase swap in the FG Advanced protection communication. Use the FB Phase swap to set how the phases are swapped when sending and receiving phase-selective information via the protection interface.
This results in the following SIPROTEC 5 device behavior:

• Connect the current and voltage transformers to the terminals A, B, and C of the protection device as usual.
• Connect the circuit breaker without swapping phases.
• The protection functions in both devices, such as Line differential protection or Teleprotection with distance protection cooperate without any problems.
• The phase-selective messages and measured values are displayed correctly from the point of view of the respective device.

Figure 3-91 Differing Phase Designations Are Compensated for while Sending and Receiving

(1) Other phase designations than at the opposite end for the same physical phase

NOTE Phase swapping does not support the I2-DIFF stage of the function Line differential protection.
Swapping of user-specific phase-selective information sent and received using the function Remote data is not supported.

3.4.6.13 Setting Notes for Phase Swapping
Swap in Send Direction

• Default setting (_:101) Swap in send direction = No phase swap
  With the parameter Swap in send direction, you select phase swapping. The phases are swapped from the send direction view. The following options are possible:

swap.
A → B, B → C, C → A| The local data such as measured values and status information of the phases are swapped and sent to the neighboring device as follows:
• The local data of phase A as data of phase B
• The local data of phase B as data of phase C
• The local data of phase C as data of phase A
A → C, B → A, C → B| The local data such as measured values and status information of the phases are swapped and sent to the neighboring device as follows:
• The local data of phase A as data of phase C
• The local data of phase B as data of phase A
• The local data of phase C as data of phase B

Swap in Receive Direction
Depending on the setting value of the parameter Swap in send direction, the reverse swap direction results from the receive direction view. The read-only parameter (_:102) Swap in receive direction then indicates the resulting phase swap.

swap.
A → C, B → A, C → B| The data received from the neighboring device such as measured values and status information of the phases are used as follows:
• The received data of phase A as local data of phase C
• The received data of phase B as local data of phase A
• The received data of phase C as local data of phase B
A → B, B → C, C → A| The data received from the neighboring device such as measured values and status information of the phases are used as follows:
• The received data of phase A as local data of phase B
• The received data of phase B as local data of phase C
• The received data of phase C as local data of phase A

Examples of a Device Combination with 3 Devices:
For a device combination with more than 2 devices, you need to mentally divide the device combination into a section using the phase swap and a section not using the phase swap. In the section using the phase swap, you need to instantiate the FB Phase swap in the SIPROTEC 5 devices. When using SIPROTEC 4 devices, you need to swap phases when connecting the transformers and the circuit breaker. The following figure shows a device combination with 3 devices. The device on the left can be a SIPROTEC 4 or SIPROTEC 5 device. There is a SIPROTEC 5 device in the middle and a SIPROTEC 4 device on the right side. The device in the middle swaps phases by using the FB Phase swap. The FB Phase swap is used for
both protection interfaces, but it is instantiated only once for each FG Advanced protection communication.
In the SIPROTEC 4 device on the right, you can implement the phase swap only by changing the wiring of the current and voltage transformers and of the circuit breaker. You must reinterpret the phase-selective indications accordingly.

Figure 3-92 Device Combination with 3 Devices

3.4.6.14 Settings

Remote data
:22741:111| Remote data:Dropout time prio. 1| | 0.00 s to 300.00 s| 2.00 s
:22741:112| Remote data:Dropout time prio. 2| | 0.00 s to 300.00 s| 2.00 s
:22741:113| Remote data:Dropout time prio. 3| | 0.00 s to 300.00 s| 2.00 s
Prot. interf. /
:5161:1| Prot. interf.1:Mode| | •off
•on| on
:5161:105| Prot. interf.1:Max. error rate per hour| | 0.000 % to 100.000 %| 1.%
:5161:106| Prot. interf.1:Max. error rate per min| | 0.000 % to 100.000 %| 1.%
:5161:107| Prot. interf.1:Distur- bance alarm after| | 0.05 s to 2.00 s| 0.10 s
:5161:108| Prot. interf.1:Transm. fail. alarm after| | 0.0 s to 6.0 s| 6.0 s
:5161:109| Prot. interf.1:Delay time threshold| | 0.1 ms to 30.0 ms| 30.0 ms
:5161:110| Prot. interf.1:Difference Tx and Rx time| | 0.000 ms to 3.000 ms| 0.100 ms
:5161:113| Prot. interf.1:Synchroni- zation| | •External synchron. off
•Telegr. and ext. synch.
•Telegr. or ext. synch.
•External synch. only| External synchron. off
:5161:117| Prot. interf.1:FB External
synchron.| | • Ext. synchronization 1
• Ext. synchronization 2| Ext. synchronization
1
:5161:120| Prot. interf.1:Check
synchron.-source| | • no
• yes| yes
:5161:120| Prot. interf.1:PI assignment| | Setting options depend on
configuration|

3.4.6.15 Information List

Prot. interf.1
:5161:81| Prot. interf.1:>Block stage| SPS| I
:5161:500| Prot. interf.1:>Sync reset| SPS| I
:5161:341| Prot. interf.1:Reset synchronization| SPC| C
:5161:342| Prot. interf.1:Reset measurements| SPC| C
:5161:52| Prot. interf.1:Behavior| ENS| O
:5161:53| Prot. interf.1:Health| ENS| O
:5161:301| Prot. interf.1:Status of lay. 1 and 2| ENS| O
:5161:302| Prot. interf.1:Status of lay. 3 and 4| ENS| O
:5161:303| Prot. interf.1:Connection broken| SPS| O
:5161:316| Prot. interf.1:Error rate / min exc.| SPS| O
:5161:317| Prot. interf.1:Error rate / hour exc.| SPS| O
:5161:318| Prot. interf.1:Time delay exceeded| SPS| O
:5161:319| Prot. interf.1:Time delay different| SPS| O
:5161:320| Prot. interf.1:Time delay jump| SPS| O
:5161:321| Prot. interf.1:PI synchronized| SPS| O
:5161:340| Prot. interf.1:Telegram lost| SPS| O
:5161:323| Prot. interf.1:PPS: time del. unsym.| SPS| O
:5161:324| Prot. interf.1:PI with PPS synchron.| SPS| O
:5161:343| Prot. interf.1:Partner| INS| O
:5161:308| Prot. interf.1:Tx tel/h| MV| O
:5161:309| Prot. interf.1:Rx tel/h| MV| O
:5161:310| Prot. interf.1:Tx tel/min| MV| O
:5161:311| Prot. interf.1:Rx tel/min| MV| O
:5161:312| Prot. interf.1:Tx err/h| MV| O
:5161:313| Prot. interf.1:Rx err/h| MV| O
:5161:314| Prot. interf.1:Tx err/min| MV| O
:5161:315| Prot. interf.1:Rx err/min| MV| O
:5161:334| Prot. interf.1:Miss.tel/min| MV| O
:5161:335| Prot. interf.1:Miss.tel/h| MV| O
:5161:336| Prot. interf.1:Miss.tel/d| MV| O
:5161:337| Prot. interf.1:Miss.tel/w| MV| O
:5161:338| Prot. interf.1:M. loss/d| MV| O
:5161:339| Prot. interf.1:M. loss/w| MV| O
:5161:331| Prot. interf.1:Recept.| MV| O
:5161:325| Prot. interf.1:Aver.Δt| MV| O
:5161:326| Prot. interf.1:Rec. Δt| MV| O
:5161:327| Prot. interf.1:Sen. Δt| MV| O
Prot.interf.1B
:23461:81| Prot.interf.1B:>Block stage| SPS| I
:23461:500| Prot.interf.1B:>Sync reset| SPS| I
:23461:341| Prot.interf.1B:Reset synchronization| SPC| C
:23461:342| Prot.interf.1B:Reset measurements| SPC| C
:23461:52| Prot.interf.1B:Behavior| ENS| O
:23461:53| Prot.interf.1B:Health| ENS| O
:23461:301| Prot.interf.1B:Status of lay. 1 and 2| ENS| O
:23461:302| Prot.interf.1B:Status of lay. 3 and 4| ENS| O
:23461:303| Prot.interf.1B:Connection broken| SPS| O
:23461:316| Prot.interf.1B:Error rate / min exc.| SPS| O
:23461:317| Prot.interf.1B:Error rate / hour exc.| SPS| O
:23461:318| Prot.interf.1B:Time delay exceeded| SPS| O
:23461:340| Prot.interf.1B:Telegram lost| SPS| O
:23461:323| Prot.interf.1B:PPS: time del. unsym.| SPS| O
:23461:324| Prot.interf.1B:PI with PPS synchron.| SPS| O
:23461:343| Prot.interf.1B:Partner| INS| O
:23461:308| Prot.interf.1B:Tx tel/h| MV| O
:23461:309| Prot.interf.1B:Rx tel/h| MV| O
:23461:310| Prot.interf.1B:Tx tel/min| MV| O
:23461:311| Prot.interf.1B:Rx tel/min| MV| O
:23461:312| Prot.interf.1B:Tx err/h| MV| O
:23461:313| Prot.interf.1B:Rx err/h| MV| O
:23461:314| Prot.interf.1B:Tx err/min| MV| O
:23461:315| Prot.interf.1B:Rx err/min| MV| O
:23461:334| Prot.interf.1B:Miss.tel/min| MV| O
:23461:335| Prot.interf.1B:Miss.tel/h| MV| O
:23461:336| Prot.interf.1B:Miss.tel/d| MV| O
:23461:337| Prot.interf.1B:Miss.tel/w| MV| O
:23461:338| Prot.interf.1B:M. loss/d| MV| O
:23461:339| Prot.interf.1B:M. loss/w| MV| O
:23461:331| Prot.interf.1B:Recept.| MV| O
:23461:325| Prot.interf.1B:Aver.Δt| MV| O
:23461:326| Prot.interf.1B:Rec. Δt| MV| O
_:23461:327| Prot.interf.1B:Sen. Δt| MV| O

3.4.7 Assignment of the Protection Function Group to the FG Protection Communication
If protection functions want to use the protection interfaces in a protection function group, you must route the connection of the protection function group, for example, the FG Line 1, with a function group Protection communication in DIGSI 5. Then, each protection function in the FG Line 1 can use the protection communication. Route the connection between the FG Line and the FG Protection communication in DIGSI 5 as follows: Project tree > Function-group connections > Tab Protection FG ↔ Protection
FG. Right-click to route the connection in the desired line/column.

Figure 3-93 Routing of the Connection between the Protection FG and the FG Protection Communication in DIGSI 5

NOTE
If only one protection function group and one FG Protection communication are instantiated in the device, DIGSI 5 connects both function groups automatically.

3.4.8 Application Examples and Setting Notes for IP Communication
3.4.8.1 Overview
The advanced protection communication supports the IP communication via MPLS communication networks. 13

• If existing systems are to be upgraded for protection-interface communication via IP, you must retrofit an
  Ethernet-BD communication module in the respective SIPROTEC 5 devices.

• The protection-interface communication via IP requires an Ethernet-BD communication module per device in the device combination.

• In a device, only one Ethernet-BD communication module can be used per device combination.

• However, another device combination can use the same Ethernet-BD communication module of the device.
  The following application examples show what you must consider when using the IP communication via MPLS communication networks.

3.4.8.2 Device Combination of 2 Devices and Redundant Communication Connection
If redundancy of the communication connection is required for a device combination consisting of 2 devices, 2 different procedures are possible:

• You can use the redundancy mechanisms of the LAN and the Ethernet-BD communication module (PRP, HSR, RSTP). In this case, the redundant communication route runs through the same Ethernet-BD communication module.
• You can set up a 2nd communication connection via a physically separate path. It is best to use a different medium for this, for example, a fiber-optic direct connection, a direct cable connection (pilot wire), or a connection based on C37.94. That is, for the 2nd communication connection, you must use another communication module in each device. The following figure shows this case from a physical and logical view:

Figure 3-94 Device Combination with 2 Devices and Redundant Communication Connection

3.4.8.3 Device Combination of 3 Devices and Only IP Communication
If you configure a device combination with 3 devices and all devices are using the IP communication, then, from the view of a device, the 2 other devices in the network are visible and reachable. For this, you configure in each device the protocol Advanced protection interface on the Ethernet-BD communication module and the Protection interface
1. The Ethernet-BD communication module is assigned to the Protection interface 1.
The special feature of this configuration is that the topology detection automatically generates a 3-device ring topology (logical view). That is, 3 point-to-point communication connections are established between the devices. In addition, another Protection interface 1B is automatically visible in each device, which provides the necessary 2nd communication channel for the ring topology, see the following figure:

Figure 3-95 Device Combination with 3 Devices in the IP Communication Network
The Protection interface 1B takes over the settings of Protection interface 1, that is Protection interface 1B does not have its own settings view. The Protection interface 1B has its own indications and measured values, which you can see in the information routing.

NOTE If you use 3 devices in the device combination with IP communication, the aim of the topology detection is to form a ring topology, as in addition to a redundant connection, shorter transmission times are also possible.
If you have instantiated a 2nd protection interface, for example to establish a communication connection via another medium, the device hides the Protection interface 1B.

NOTE
In the following cases, the Protection interface 1B becomes inactive and does not have any messages or measured values:

• A 2nd protection interface is instantiated.
• Only 2 devices are present in the device combination.
• No protection interface is assigned to an Ethernet-BD communication module.

3.4.8.4 Device Combination of 3 Devices and Hybrid Communication Media
If you extend a system, it can be necessary to extend a device combination consisting of 2 existing devices by 1 device, see the following figure.
The previous 2 devices are connected to each other, for example, via a fiber- optic direct connection or via other communication media. The left device, for example, a SIPROTEC 4 device, and the middle SIPROTEC 5 device are the 2 devices previously present in the system. This device combination is to be extended by adding the right SIPROTEC 5 device. The communication between the middle and the right device is to take place via an IP communication network.

Figure 3-96 Device Combination with 3 Devices and Hybrid Communication Media

For this configuration of a 3-device chain topology, you must configure a device combination with 3 devices in all devices.
In the middle device, an Ethernet-BD communication module is additionally required. Configure the protocol Advanced protection interface in the properties of the Ethernet-BD communication module. Instantiate the function block Protection interface 2 in the FG Protection communication. Assign the Ethernet-BD communication module to the Protection interface 2.
The device on the right must also have an Ethernet-BD communication module. Also configure here the protocol Advanced protection interface in the properties of the Ethernet-BD communication module and assign the Ethernet-BD communication module to the Protection interface 1. Protection interface 1B is created here as a special feature, but it is not used.
If a redundant communication connection is required for this configuration, Siemens recommends establishing a 3-device ring topology. For this purpose, you must connect the left and right devices via another communication channel. This creates the 3-device ring topology. The following figure shows this configuration:

Figure 3-97 Device Combination with 3 Devices and Hybrid Communication Media and Redundant Communication Connection
The SIPROTEC 4 device (left device) does not support any IP communication. In this case, you must switch to another communication medium and retrofit a corresponding SIPROTEC 4 communication module. In any case, the communication medium used is also supported by the SIPROTEC 5 device on the right side, by retrofitting a corresponding equivalent communication module there. Configure this communication module with the protocol Advanced protection interface, add an additional Protection interface 2 to the FG
Protection communication. Assign the Protection interface 2 to the communication module.

3.4.8.5 Device Combination of 6 Devices and Hybrid Communication Media
IP Addresses in Hybrid Topologies
To ensure redundancy or downward compatibility, the devices also allow a mix of classic and IP-based communication media.
In such applications, special consideration must be given to the configuration of the IP addresses. When parametrizing the devices, you must first clarify which path the communication is to take through the network.
That is, it must be clear which devices communicate with each other. To define a route, you may only configure its planned communication partners in a device. The following examples illustrate the correct IP configuration.
For device combinations with more than 3 devices and hybrid communication media, different configurations are possible. If you want to use the IP communication, consider that only one Ethernet-BD communication module per device combination is supported for the protection-interface communication.
The following figure shows a device combination with 6 devices. In the example, several devices are connected by other communication media, which form 3 device groups. The device groups are connected by an IP network. The result is a 6-device chain topology. The yellow line illustrates the communication route.
To establish this communication route, you may only parameterize the IP addresses of their direct communication partners in the devices. The following example applies:

• The devices 2 and 4 only know the IP address of device 3.
• Device 3 only knows the IP addresses of the devices 2 and 4.
• Leave all other IP addresses at 0.0.0.0.

Figure 3-98 Example 1 of a Device Combination with 6 Devices

Another example shows 2 device groups whose devices are connected to each other via IP networks. The 2 device groups are connected to each other by a different communication medium. The topology detection in turn forms a 6-device chain topology.

To establish this communication route, you may only parameterize the IP addresses of their direct communication partners in the devices. The following example applies:

• Device 1 only knows the IP addresses of the devices 2 and 3.
• The devices 2 and 3 only know the IP address of device 1.
• Device 5 only knows the IP addresses of the devices 4 and 6.
• The devices 4 and 6 only know the IP address of device 5.
• Leave all other IP addresses at 0.0.0.0.

Figure 3-99 Example 2 of a Device Combination with 6 Devices

3.4.8.6 Unsupported Configurations
The following figure shows an example of a device combination with 3 devices. In the example, all devices use the IP communication. The middle device contains 2 Ethernet-BD communication modules, which are both configured with the Advanced protection interface protocol.

NOTE
You can only use 1 Ethernet-BD communication module in one device!
2 Ethernet-BD communication modules with the Advanced protection interface protocol are not supported.

Figure 3-100 Unsupported Configuration of a Device Combination with 3 Devices

NOTE
If you use the IP communication, the aim of the topology detection is to form a chain topology if there are 4 or more devices. For certain configurations, the topology detection cannot form a working chain topology.
The following figure shows an example of a device combination with 6 devices and hybrid communication media. In this case, the topology detection cannot form a functioning 6-device chain topology.

Figure 3-101 Unsupported Configuration of a Device Combination with 6 Devices

3.5 Date and Time Synchronization
3.5.1 Overview of Functions
Timely recording of process data requires precise time synchronization of the devices. The integrated date/ time synchronization allows the exact chronological assignment of events to an internally managed device time that is used to time stamp events in logs, which are then transmitted to a substation automation technology or transferred via the protection interface. A clock module internal to the device and having battery backup is synchronized cyclically with the current device time so that the right device time is available and used even in case of auxiliary-voltage failure. At the same time, this permits hardware-supported monitoring of the device time.

3.5.2 Structure of the Function
The integrated date/time synchronization is a supervisory device function. Setting parameters and indications can be found in the following menus for the DIGSI and the device:
Set date and time:

• DIGSI: Online access -> Interface -> Device -> Device Information -> Time Information
• Device: Main menu → Device functions → Date & Time Parameter:
• DIGSI: Project -> Device -> Parameter -> Time Settings Indications:
• DIGSI: Project -> Device -> Information routing ->Time keeping or Time Sync.

3.5.3 Function Description
Every SIPROTEC 5 device maintains an internal device time with date. The date and time can also be set on the device via the on-site operation panel or via DIGSI 5. Within a system, or even beyond, it is usually necessary to record the time of process data accurately and to have exact time synchronization of all devices. For SIPROTEC 5 devices, the sources of time and synchronization options can be configured.

Configurable Synchronization Options:

• None (default setting)
  The device functions without any external time synchronization. The internal time synchronization continues to work with the help of the back-up battery even when the auxiliary voltage is shut down temporarily. The time can be adjusted manually.

• Telegram
  The time is synchronized via a telegram with an appropriately configured communication interface in accordance with the IEC 60870-5-103 or DNP3 protocol.

• Connection to a radio clock
  The time synchronization takes place with the set time telegram from an external IRIG B or DCF77 receiver via the time synchronization interface of the device.

• Ethernet
  The time synchronization is done via Ethernet-based SNTP protocol (Simple Network Time Protocol), for example with IEC 61850 stations or via IEEE 1588. If you enable both services during configuration of
  Ethernet interfaces, these protocols are available as an option for the time synchronization.

• Protection interface
  The time synchronization takes place via the protection interfaces configured for your SIPROTEC 5 device. Here, the timing master takes over the time management.

Configurable Time Sources:

• 2 time sources can be taken into consideration with the SIPROTEC 5 devices. For each time source, the synchronization type may be selected based on the options provided.
• Time source 1 takes precedence over Time source 2, that is, Time source 2 will be effective for the synchronization of the device time only if Time source 1 fails. If only one time source is available and it fails, then only the internal clock continues unsynchronized. The status of the time sources is indicated.
• For every time source, it is possible to define via the Time zone time source 1 parameter (or Time zone time source 2) if this source transmits its time by UTC (universal time) or if the settings correspond to the local time zone of the device.

NOTE
Make sure that the settings for the time sources coincide with the actual hardware configuration of your SIPROTEC 5 device. In any event, incorrect settings cause the status indications of time sources to pick up.

Configurable Date Format
Regardless of a feed time-synchronization source, a uniform format is maintained internally within the device.
The following options are available for the customary local representation of the date format:

• Day.Month.Year: 24.12.2009
• Month/Day/Year: 12/24/2009
• Year-Month-Day: 2009-12-24

Taking Local Time Zones into Account
The internal device time is maintained in universal time (UTC). To display time stamps in DIGSI and on the device display, you can define the local time zone of the device (parameter Offset time zone for GMT), including the applicable daylight saving times (start, end, and offset of daylight saving time) using parameters. This allows the display of the local time.

NOTE

• For time sources that transmit the status of the switch to daylight saving time, this will be taken into account automatically when creating the internal device time in the UTC format. The differential time of the daylight saving time set in the device (parameter Offset daylight saving time) is taken into consideration. However, in contrast, the settings of the start of daylight saving time and end of the daylight saving times are ignored when converting into the device internal UTC format.
• For active time sources, it is not possible to set the time via the device display or DIGSI 5. An exception is setting the calendar year for active time protocol IRIG B.

Status, Supervision, and Indications of Time Management
Your SIPROTEC 5 device generates status and monitoring indications that provide important information regarding the correct configuration of the time source and the status of the internal time management during startup and device operation.
Internal time synchronization is monitored cyclically. Important synchronization processes, the status of the time sources and errors detected are reported. A device time that has become invalid will be marked accordingly so that affected functions can go to a safe state.

Device:
Clock fail| This indication signals a high difference between the internally managed time and the time of the clock module that is not permissible. The pickup of the indication can point to a defect in the clock module or to an unacceptable high drift of the system quartz crystal. The time maintained internally is marked as invalid.
Time management:
Daylight saving time| This indication signals whether daylight saving time has been enabled.
Time management: Clock set manually| This indication signals that the device time has been set manually via the on-site operation panel or via DIGSI 5.
Time synchronization:
Status time source 1
Status time source 2| These 2 indications signal whether the active time sources are recognized as valid and active from the device point of view. When the indications pick up, it can also be an indication that an incorrect configuration of the port or channel numbers was done at the on-site operation
panel.
Time synchronization:
Time sync. Error| This indication signals after the parameterized time Fault indication after that synchronization
using an external time source has failed.
Time synchronization:
Leap second| This indication signals that a Leap second has occurred during time synchronization using
an external GPS receiver (protocol variant IRIG B 005(004) with extension according to IEEE
C37.118-2005).
Time synchronization:
High accuracy| This indication signals that the device is synchronized with an accuracy better than 1 μs The indication is only of significance when the PMU function is used.

NOTE In case of a missing or discharged battery, the device starts without active external time synchronization with the device time 2011-01-01 00:00:00 (UTC).
For the device, DIGSI 5 provides a compact overview of the status of the time synchronization of your SIPROTEC 5 device in online mode. All displays are updated continuously. You can access the overview in the project-tree window via Online access.
DIGSI: Online access -> Interface -> Device -> Device Information -> Time Information

Figure 3-102 Time Information in DIGSI

For every time source, you see the following:

• Last received time (with date)
• Receipt time of the last received time telegram
• Configured type of timer
• Indication of timer outage or failure
• Whether the device time is currently synchronized from the time source

The lower section displays the device time, which is continuously updated. If the internal device time and the infeed time source were synchronous at the time of telegram receipt, both displayed times are identical.

NOTE All times displayed (also the time source) take into consideration the local time settings (zone and daylight saving time of the device) in the form of a numerical offset for UTC (universal time).

3.5.4 Application and Setting Notes
Parameter: Date Format

• Default setting Date format = YYYY-MM-DD

With the parameter Date format, you define the local customary format of the date display.

Example: 24.12.2010
MM/DD/YYYY| Month/Day/Year: Typical US representation
Example: 12/24/2010
YYYY-MM-DD| Year-Month-Day: Typical Chinese display
Example: 2010-12-24

Parameter: Time zone time source 1, Time zone time source 2

• Default setting Time zone time source 1 = local, Time zone time source 2 = local

With the parameters Time zone time source 1 and Time zone time source 2, you define the handling of time zones of the external timer.

offsets to GMT.
UTC| Time format according to UTC (universal time)

Parameter: Time source 1, Time source 2

• Default setting Time source 1 = none, Time source 2 = none

With the parameters Time source 1 and Time source 2, you can configure an external timer. The prerequisite is to have the corresponding hardware configuration of the communication interfaces of your SIPROTEC 5 device. This is listed as a prefix when making a selection in DIGSI 5.

SIPROTEC 5 devices support several protocol variants of the IRIG-B standard:
•         IRIG-B 002(003)
The control function bits of the signal are not occupied. The missing year is formed from the current device time. In this case, it is possible to set the year via the online access in DIGSI 5.
•         IRIG-B 006(007)
The bits for the calendar year are not equal to 00. The calendar year is set automatically by the time protocol.
•         IRIG-B 005(004) with extension according to IEEE C37.118-2005
If, in the time signal, other control function bits are occupied in addi- tion to the calendar year, then the device takes the additional informa- tion into consideration for leap seconds, daylight saving time, time offset (zone, daylight saving time), and time accuracy.
Time zone time source 1 or Time zone time source 2 : The value of this setting is not evaluated by the device, since this protocol either transmits in UTC or in the case of local time, specifies the appropriate offset to UTC in each set time telegram.
DCF77| Time synchronization by an external DCF77 receiver
Time zone time source 1 or Time zone time source 2 = local
Note: There are also clocks that generate a DCF77 signal representing UTC. In this case, UTC must be set.
PI| The time synchronization takes place via the protection interfaces config- ured for your SIPROTEC 5 device. Here, the timing master takes over the time management. Signal-transit times of the protection interface commu- nication are calculated automatically.
Time zone time source 1 or Time zone time source 2 = UTC
A slave that receives a time or a SIPROTEC 5 master, receives its system time kept in UTC.
Parameter Value| Description
---|---
SNTP| The time synchronization is done via the Ethernet service SNTP (SNTP server or via IEC 61850).
SIPROTEC 5 devices support both Edition1 and Edition2 in accordance with IEC 61850-7-2. In Edition2, the logical attributes LeapSecondsKnown, Clock- Failure, ClockNotSynchronized, and the value TimeAccuracy are maintained in each time stamp. For Edition1, these signals contain default settings.
Thus, the interoperability for substation automation technology is ensured for both editions!
The SNTP service must be enabled during configuration of Ethernet inter- faces so that it is available as an option for the time synchronization.
Time zone time source 1 or Time zone time source 2 = UTC
IEC 60870-5-103| The time is synchronized via telegram with an appropriately configured communication interface in accordance with the IEC 60870-5-103 protocol. Time zone time source 1 or Time zone time source 2 = local
However, there are also T103 systems that send the UTC.
DNP3| The time is synchronized via telegram with the appropriately configured communication interface in accordance with the DNP3 protocol.
2 characteristics are supported in the process:
•         Time synchronization via UTC
•         Time synchronization with local time
The daylight saving time status is not transmitted. The device assumes that the DNP3 master follows the same rules for the start and end of the daylight saving time as those that were set for the device.
Time zone time source 1 or Time zone time source 2 = UTC is the current implementation, local concerns older implementa- tions.
IEEE 1588| Time is synchronized via an IEEE 1588 timing master. In this case, SIPROTEC 5 devices operate as slave-only clocks. IEEE 1588 v2 is supported with P2P and Ethernet Transport.
The IEEE 1588 service must be enabled during configuration of Ethernet interfaces so that it is available as an option for the time synchronization. Time zone time source 1 or Time zone time source 2 = UTC.

Parameter: Fault indication after

• Default setting Fault indication after = 600 s

With the parameter Fault indication after, you set the time delay after which the unsuccessful attempts of time synchronization with external time sources configured are indicated.
Parameter: Time Zone and Daylight Saving Time
This parameter block contains all the settings for the local time zone and daylight saving time of your SIPROTEC 5 device. In addition to the individual parameters, configure the basic settings by preselecting via the option buttons or check box. Figure 3-103 Settings for Time Zone and Daylight Saving Time in DIGSI

setting must be selected if you want to select the local time zone and daylight saving time zone regulations of your SIPROTEC 5 device regardless of the PC settings.
Input: Offset time zone for GMT [min] Selection: Switchover to daylight saving time [yes/no] via check box •         Input: Start of daylight saving time [Day and time] •         Input: End of daylight saving time [Day and time] •         Input: Offset daylight saving time [min] • Default settings as in the picture above

3.5.5 Settings

Time sync.
:102| Time sync.:Time source 1| | •         none
•         IRIG-B
•         DCF77
•         PI
•         SNTP
•         IEC 60870-5-103
•         PROFIBUS DP
•         Modbus
•         DNP3
•         IEEE 1588
•         IEC 60870-5-104| none
:103| Time sync.:Time source 1 port| | •         port J
•         port F
•         port E
•         port P
•         port N
•         port G|
:104| Time sync.:Time source 1 channel| | •         Ch1
•         Ch2|
Addr.| Parameter| C| Setting Options| Default Setting
---|---|---|---|---
:105| Time sync.:Time source 2| | •         none
•         IRIG-B
•         DCF77
•         PI
•         SNTP
•         IEC 60870-5-103
•         PROFIBUS DP
•         Modbus
•         DNP3
•         IEEE 1588
•         IEC 60870-5-104| none
:106| Time sync.:Time source 2 port| | •         port J
•         port F
•         port E
•         port P
•         port N
•         port G|
:107| Time sync.:Time source 2 channel| | •         Ch1
•         Ch2|
:108| Time sync.:Time zone time source 1| | •         UTC
•         local| local
:109| Time sync.:Time zone time source 2| | •         UTC
•         local| local
_:101| Time sync.:Fault indica- tion after| | 0 s to 3600 s| 600 s

3.5.6 Information List

Time managem.
:300| Time managem.:Daylight saving time| SPS| O
:301| Time managem.:Clock set manually| SPS| O
No.| Information| Data Class (Type)| Type
---|---|---|---
Time sync.
:303| Time sync.:Status time source 1| SPS| O
:304| Time sync.:Status time source 2| SPS| O
:305| Time sync.:Time sync. error| SPS| O
:306| Time sync.:Leap second| SPS| O
_:307| Time sync.:High accuracy| SPS| O

3.6 User-Defined Objects
3.6.1 Overview
With help from user-defined function groups and user-defined functions you can group user-defined objects, for example user-defined function blocks. 2 user- defined function blocks are available (see following figure). Figure 3-104 User-Defined Objects in the DIGSI 5 Library
The user-defined function block allows you to add (see following figure) single-point indications, pickup indications, operate indications (ADC, ACT), single and double commands, commands with a controllable whole number as well as measured values. You can assign the group a superordinate name (for example process indications for a group of single-point indications which are read via binary inputs). This function can be deactivated using the mode. The standby mode is also analyzed or displayed.
The user-defined function blocks can be instantiated at the highest level (alongside other function groups) as well as within function groups and functions.
In addition, there is a user-defined function block [control]. Alongside the aforementioned possibilities presented by user-defined function blocks, this block offers additional tests for user-defined control signals, for example SPC or DPC.
These are described in chapter 6.6.1 Overview of Functions.Figure 3-105 Information Routing with Incorporated User-Defined Function Block: Process Indications and some Single-Point Indications
3.6.2 Basic Data Types
The following data types are available for user-defined objects in the DIGSI 5 library under the heading Userdefined signals. Additionally, a folder for external signals is available (see chapter 3.6.5 External Signals).
User-Defined Signals Figure 3-106 User-Defined Signals
Single-Point Indication (Type SPS: Single-Point Status)
The status of a binary input can be registered in the form of a single-point indication or forwarded as the binary result from a CFC chart.
EXAMPLE
Acquisition using binary input, further processing in a CFC and/or signaling using an LED.
Single-Point Indication (Type SPS unsaved: Single-Point Status Unsaved)
In contrast to SPS single-point indications, the state of the SPS unsaved indication is not maintained after the device restarts.
For this purpose, go to Properties > Details > Initialization > Restart and set the Value.Figure 3-107 Single-Point Indication SPS Unsaved (Example: 7KE85 Fault Recorder)
Double-Point Indication (Type DPS: Double-Point Status)
When using a double-point indication, the status of 2 binary inputs can be captured simultaneously and mapped in an indication with 4 possible conditions ( ON, Intermediate position, OFF, Disturbed position).
EXAMPLE
Acquisition of a disconnector or circuit-breaker switch position.
Marker Command (Type SPC, Single-Point Controllable)
This data type can be used as a command without feedback for simple signaling or as an internal variable (marker).
Integer Status Value (Type INS)
The data type INS is used to create a whole number that represents a CFC result.
EXAMPLE
The output of the CFC block ADD_D can, for example, be connected with the data type INS. The result can be shown on the display of the device.
State of an Enumeration Value (Type ENS)
The data type ENS is used to create an enumerated value that represents a CFC result.
Controllable Single-Point Indication (SPC, Single-Point Controllable)
This can be used to issue a command (to one or several relays, selectable under information routing) that is monitored via a single feedback.
Command with Double-Point Feedback (DPC, Double-Point Controllable)
This can be used to issue a command (to one or several relays, selectable under information routing) that is monitored via double-point indication as feedback.
Command with a Whole Number (INC, Controllable Integer Status)
This can be used to issue a command (to one or more relays, selectable under information routing) that is monitored via a whole number as feedback.
Complex Measured Values (CMV)
This data type provides a complex measured value that can be used as a CFC result, for example.
Measured Values (MV)
This data type provides a measured value that can be used as a CFC result, for example.
NOTE
Additional data types can be found under other headings in the DIGSI 5 library as well as in the corresponding function blocks. This applies to the following data types:

• Pulse-metered values (see User-defined functions in the DIGSI 5 library)
• Transformer taps
• Metered values

Phase-to-Ground Measured Values (WYE)
This data type represents the phase-to-ground measured values of a 3-phase system.
Phase-to-Phase Measured Values (DEL, Delta)
This data type represents the phase-to-phase measured values of a 3-phase system.
Protection Activation Information (ACT)
This object type is used by the protection functions for Tripping. It is available in the library for receiving protection information via the protection interface, which could also indicate Tripping.
The status indications for the ACT data type are built as follows: Figure 3-108 Building of the Status Indications ACT
Protection Activation Information with Direction (ACD)
This object type is used by the protection functions for Pickup. It is available in the library for receiving protection information via the protection interface, which could also indicate Pickup. In addition, both ACD and ACT, can be generated and processed by CFC charts.
The status indications for the ACD data type are built as follows:

Figure 3-109 Building of the Status Indications ACD (1) Further information, see Table 3-19
Table 3-19 Building of the Direction Information for the Data Type ACD

has picked up in backward direction.

3.6.3 Pulse and Energy Metered Values
Pulse-Metered Values
Pulse-metered values are available as data types BCR (Binary Counter Reading) in the DIGSI library under User-defined Functions.
You can find the functionality and the settings of the pulse-metered values in 8.2.1 Function Description of Pulse-Metered Values.
3.6.4 Additional Data Types
The following data types are also used in the system but are not available for general use as user-defined signals in the library:

• ENC (Enumerated Setting Controllable)
  The data type ENC models a command with which the user can set predefined values.

• SEQ (Sequence)

• BSC (Binary Controlled Step Position)
  The data type BSC can, for example, be used to control a transformer tap changer. The commands up, down can be given.

NOTE
Transformer taps are included in the Transformer tap changer switching element. If this switching element is created in the device, the transformer tap position is available as a data object of type BSC (binary controlled step position information).
3.6.5 External Signals
User-defined signals of different types (see Figure 3-110) are available for GOOSE Later Binding. After instantiation in a logical node, an external reference is generated during IID export and provided to a IEC 61850 system tool (for example, System Configurator) for GOOSE Later Binding (according to the Later-Binding procedure specified in IEC 61850-6).

Figure 3-110 External Signals
NOTE
Consider the chapter on GOOSE Later Binding in the DIGSI Online Help. User- defined signals exist as external signals and as preconfigured inputs that have been activated via the GOOSE column.
3.7 Other Functions
3.7.1 Signal Filtering and Chatter Blocking for Input Signals
Input signals can be filtered to suppress brief changes at the binary input. Chatter blocking can be used to prevent continuously changing indications from clogging the event list. After an adjustable number of changes, the indication is blocked for a certain period.
The settings for indication filtering can be found at the individual signals. The next figure shows the settings using the example of a controllable (circuit-breaker switch position). ii
NOTE
The software filtering time is available only for the circuit breaker and disconnector in the controllable Cmd. with feedback (control function block), as this is used for logging purposes. The controllable position (circuit breaker or disconnector function block) is used for interlocking conditions and must always show the unfiltered position of the switching object.Figure 3-111 Settings for Circuit-Breaker Switch Position
The setting range for the Software filter time parameter ranges from 0 ms to 100 000 ms in ms increments. The Retrigger filter check box can be used to select whether to restart the filtering time whenever a status change is performed within the software filtering time. When activated, the Indication timestamp before filtering check box backdates the time stamp by the set software filtering time. In this case, the time stamp corresponds to the actual status change of the signal. If you activate the Suppress intermediate position check box, the intermediate position is suppressed for the duration of this software filtering time.
If you leave the software filtering time at 0 ms, the time for the suppression of the intermediate position is also 0 ms. The activated Suppress intermediate position check box then remains ineffective.
If you do not activate the Suppress intermediate position check box, the software filtering time affects the on, off, intermediate, and disturbed positions of the circuit breaker or disconnector switch.
With the parameter Spontaneous position changes filtered by:, you set how such position changes are to be filtered. Spontaneous position changes are caused by external switching commands, for example. If you select the General software filter setting, the general settings for software filtering of spontaneous position changes and for position changes caused by a switching command apply. The settings for spontaneous position changes then cannot be edited. A separate filtering for spontaneous position changes is activated with the Spontaneous software filter setting and you can edit the settings for this.
Chatter blocking can be activated or deactivated as an input parameter, for example as a parameter of the position in the Circuit breaker or Disconnector function block.Figure 3-112 Setting Chatter Blocking
The settings for the chatter blocking function are set centrally for the entire device in DIGSI. They are accessible as settings in the General function group (see the following figure).
The chatter-blocking settings have the following meaning (see also Figure 3-113 and Figure 3-114 in the examples shown in the following):

• No. permis.state changes

This number specifies how often the state of a signal may toggle within the chatter-test time and the chatter-checking time. If this number is exceeded, the signal will be or remains blocked.
Enter a number from 0 to 65535 in this field. If the entry is 0, chatter blocking is essentially inactive.

• Initial test time

During this time, the number of times a signal changes its status is checked. This time is started if chatter blocking is configured for at least one signal and this signal changes its status. If the configured number of permissible status changes is exceeded during the initial test time, the signal is temporarily blocked and the indication Chatter blocking is set.
Enter a number from 1 to 65535 in this field. The number entered corresponds to the time in seconds.
When the set time has expired, the timer restarts automatically (cycle time).

• No. of chatter tests
  This number specifies the maximum number of test cycles to be run. If the number of permissible status changes of the signal stays exceeded during the initial test time of the last test cycle, the signal is finally blocked. In this case, the indication Group warning (Alarm handling group and Device group) is set additionally to the Chatter blocking indication after expiry of the set number. Restarting the devices removes this block again.
  Enter a number from 0 to 32767 in this field. The value Infinite (∞) is also permissible here.
  Enter this value as character string oo.

• Chatter idle time
  If the number of permissible status changes for a signal is exceeded during the initial test time or the subsequent test time, the Chatter idle time starts. Within this time, this signal is blocked temporarily and the Chatter blocking indication is set. The blocked input signal is assigned the oscillatory quality.
  Enter a number from 1 to 65535 in this field. The number entered corresponds to the time in minutes. An entry here is only considered if the number of chatter tests does not equal to 0.

• Subsequent test time
  During this second test time, the number of times a signal changes its status is checked once again.
  The time begins when the Chatter idle time expires. If the number of status changes is within the permissible limits, the signal is released. Otherwise, an additional dead time begins, unless the maximum number of chatter tests has been reached.
  Enter a number from 2 to 65535 in this field. The number entered corresponds to the time in seconds. An entry here is only considered if the number of chatter tests does not equal 0.

Example 1: Permanent Blocking
The chatter-blocking settings are set as follows:

• No. permis.state changes = 4
• No. of chatter tests = 2

After more than 4 state changes within the Initial test time, the input signal is set to the original state by the chatter blocking and the oscillatory quality is assigned. Additionally, a corresponding indication is added to the operational log. At the same time, the Chatter blocking indication is set. After expiry of the settable Chatter idle time, during the following Subsequent test time, it is checked whether the input signal is still chattering. This check is repeated, as the No. of chatter tests is set to 2 in this example.
If, during the 2nd Subsequent test time, it has been detected that the number of status changes of the input signal exceeds the set No. permis.state changes, the chatter blocking detects a persistent violation of the signal stability and sets the Group warning indication. The original state of the signal is permanently frozen. Only a device restart removes the chatter blocking again.Figure 3-113 Signal Change during Chatter Blocking with too Important Number of Signal State Changes During 2nd Subsequent Test Time
(1) The input signal is permanently blocked starting from this point in time.
Example 2: Temporary Blocking
The chatter-blocking settings are set as follows:

• No. permis.state changes = 4
• No. of chatter tests = 2

After more than 4 state changes within the Initial test time, the input signal is set to the original state by the chatter blocking and the oscillatory quality is assigned. Additionally, a corresponding indication is added to the operational log. At the same time, the Chatter blocking indication is set. After expiry of the settable Chatter idle time, during the following Subsequent test time, it is checked whether the input signal is still chattering. This check is repeated, as the No. of chatter tests is set to 2 in this example.
If, during the 2nd Subsequent test time, it has been detected that the number of state changes of the input signal is within the set No. permis.state changes, the temporary blocking of state changes of the signal is removed and the actual signal state is released.
The quality bit oscillatory is removed and the Chatter blocking indication is reset. As the temporary blocking of the signal is removed, the Group warning indication is not set. The chatter test starts again.Figure 3-114 Signal Change during Chatter Blocking with Permissible Number of Signal State Changes During 2nd Subsequent Test Time
3.7.2 Acquisition Blocking and Manual Updating
During commissioning, maintenance, or testing, a brief interruption of the connection between the logical signals and binary inputs may be useful. It allows you to manually update the status of a switching device that is not providing feedback correctly. Before this can take place, you must first set acquisition blocking.
To set the acquisition blocking, proceed as follows:

• Using the navigation keys, move in the main menu of the device display to
  Commands→Equipment→Aq.blkman. update.

• Select the appropriate device (for example, a circuit breaker) from among the several switching devices using the navigation keys.

• Press the Change softkey.

• Enter the confirmation ID (not relevant for active role-based access control (RBAC) in the device).

• Confirm the process with the softkey marked OK in the display.
  After entering the confirmation ID (only with the RBAC inactive), acquisition blocking is switched on.

Figure 3-115 Activating the Acquisition Blocking
Manual updating of the switching device is possible from within the same menu.

• Select Manual update (Figure 3-116) using the navigation keys.
• Select the switching device setting to be manually updated using the navigation keys (for example, off, Figure 3-117).
• Confirm the process with the softkey marked Ok in the display.

Figure 3-116 Activating Manual Update Figure 3-117 Selecting Position
The manually updated position of the switching device will be displayed. Figure 3-118 Position of the Switching Device
NOTE
For security reasons, manual updating is possible only directly through the on-site operation panel of the device and not through DIGSI 5.
NOTE
Setting acquisition blocking and the subsequent manual updating are also possible via the IEC 61850 system interface.
You can set acquisition blocking also via a binary input. If you want to put in the feeder or the switching device in revision, you can set the acquisition blocking with an external toggle switch for one or more switching devices. For this purpose, every switching device in the Switch function block (circuit breaker or disconnector switch) has the input signal >Acquisition blocking. This signal can also be set from the CFC.Figure 3-119 Input Signals >Acquisition Block and

Release Acquisition Block & Manual Updating on the Switching Device
NOTE
Interlockings are carried out with the status changes of the switching device. Remove acquisition blocking again manually. Otherwise, position changes of the switching device are not detected and interlockings are ineffective.
If the acquisition blocking and the manually updated position are set using the operation panel of the device or the system interface IEC 61850, these are retained until the acquisition blocking is manually deactivated.
When you initially start the device, the acquisition blocking is deactivated.
Except for a restart, the acquisition blocking and the manually updated position are retained.
If the acquisition blocking is activated via the input signal >Acquisition blocking, it is retained as long as the binary input is active.
To set the acquisition blocking of a switching device, the following sources are possible:

• Operation panel of the device
• System interface IEC 61850
• Input signal >Acquisition blocking

All sources undergo OR operations, that is, the acquisition blocking remains set until all the sources are deactivated.
After deactivation of the acquisition blocking, the actual position of the switching device is adopted and displayed in the operation panel of the device.
NOTE
When the acquisition blocking is activated or the switching device updated manually while the entire device or the switching device is in application mode, these states are not saved. The acquisition blocking and the manual updating are not retained after a restart.
The acquisition blocking and the manual update for the circuit breaker, the disconnector, and the tap changer are reset by way of the >Reset AcqBlk&Subst binary input. Setting acquisition blocking and manual update is blocked with the input activated.
3.7.3 Persistent Commands
In addition to the switching commands, which are issued as pulse commands, and stored for the standard switching devices (circuit breaker, disconnector switch), persistent commands are also possible. In this case, a distinction must be drawn between controllables with the Continuous output operating mode and a stored signal output that is immune to reset.
You can change a controllable from pulse to persistent command with the Command output parameter.![SIEMENS 6MD84 Protection Relays Digital Substation

• System Functions 57](https://manuals.plus/wp-content/uploads/2023/12 /SIEMENS-6MD84-Protection-Relays-Digital-Substation-System- Functions-57.jpg)Figure 3-120 Setting the Command Type in DIGSI 5
  Select Pulse output or Continuous output for the command output type. If a persistent command is selected, the Pulse parameter is irrelevant.
  3.7.4 Device Logout
  3.7.4.1 Overview
  In the case of multibay functions, a device uses information from one or more other devices. For some applications, it may be necessary for you to remove a device with all effective functions temporarily from the plant and even to switch it off. These applications are, for example:

  • Maintenance work
  • System upgrades
  • Testing the local protection functions, for example, the local line differential protection

The Device logout functionality informs the receiver devices about the imminent disconnection of the transmitter devices. To do this, the last valid received information is stored in the receiver devices and used for the multibay functions.
NOTE
If you need to remove a device temporarily from the plant, you must log off the device.
Protection functions distributed to several devices operate in a healthy manner with the remaining devices only if you have logged off the device.
You can log off the device as follows:

• Via the on-site operation panel
• Via a communication interface using the Device logout (_:319) controllable
• Via the binary inputs, general: >Dev. funct.logout on (:507) or >Dev. funct.logout off (:508)

You can find the controllable and the binary inputs in the DIGSI 5 project tree under Name of the device → Information routing in the working area in the General block.
During the log-off process, the device checks whether all conditions for a logout have been met. If the conditions for the log off have not been met, the logout is rejected.
The logout is rejected under the following conditions:

• The devices are communicating via the protection interface and switching off the device leads to an interruption in protection-interface communication.
• The Line differential protection function is operating in the device and the local circuit breaker is still switched on.

In this case, you must switch off the local circuit breaker and repeat the log-off process for the device.
After the logout, the local Line differential protection function is removed from the summation of the currents for the Line differential protection of the other devices. The Line differential protection function remains active in the other devices.
NOTE
The path used to log the device off is stored in the operational log.
Even if you switch off the device after logout, the Device logged off (_:315) state is stored.
If you want to establish the initial state again after logging off the device, you must log on the device again.
To log on the device, you must use the same option used for logout. For example, if you have logged off the device via binary inputs, you must log it on again via the binary inputs. This applies in similar manner if you have logged off the device via DIGSI or via on-site operation.
3.7.4.2 Application and Setting Notes
Logoff Options for a Device
You can log a device off as follows:

• Via the on-site operation panel
• Via communication through the controllable Device logout (_:319)
• Via the binary inputs, general: >Dev. funct.logout on (:507) or >Dev. funct.logout off (:508)

Conditions for Logging off the Device Figure 3-121 Logic for Logging off the Device
The conditions for a successful logout of the device result from the conditions for every activated protection function.
Logoff of a Device from a Device Combination with Communication via the IEC 61850-8-1 (GOOSE) Protocol If devices are exchanging data using the IEC 61850-8-1 (GOOSE) protocol – for example in the case of substation interlocking – for each received data point the value of this data point can be set in the receiver device when the transmitter device logs off. This value remains effective in the receiver device until the logout is canceled by the transmitter device, even if the transmitter and/or the receiver are switched off in the meantime.
Logoff of a Device from a Device Combination Using Protection Communication
If devices in a device combination communicate via the protection interface, you can only log off a device under the following conditions:

• Logging off and switching off a device in a device combination must not result in an interruption in the protection communication.
• For series-connected topologies, the device must be located at one end of the communication chain as otherwise the protection communication is interrupted when the device is logged off and switched off.

For this reason, devices not at one of the ends in series-connected topologies cannot be logged off.
Logout via Binary Inputs
The following diagrams show potential variants on how to control binary inputs. If you want to use pushbuttons, switch on this function as shown in the following figure. Log off the device using the push-button
Key2; log on the device again with the push-button Key1.Figure 3-122 External Push- Button Wiring for Logging off the Device
If a switch is being used for control, route the binary input >Dev. funct.logout on as H (active with voltage) and the binary input >Dev. funct.logout off as L (active without voltage). If the switch S is closed, the device is logged off.Figure 3-123 External Switch Wiring for Logging off the Device
Indications
The logged-off device reports the status ((:315) Device logged off) and cause of the logout.
If you have logged off the device using binary inputs, the indication (:313) Logged off via BI results.
If you have logged off the device using on-site operation, via DIGSI 5 or via the protection interface,the indication (_:314) Logged off via control is issued.
The indications are stored in the operational log.
3.7.4.3 Information List

General
:507| General:>Dev. funct.logout on| SPS| I
:508| General:>Dev. funct.logout off| SPS| I
:319| General:Device logout| SPC| C
:313| General:Logged off via BI| SPS| O
:314| General:Logged off via control| SPS| O
:315| General:Device logged off| SPS| O

3.8 Device Settings
3.8.1 Settings-Group Switching
3.8.1.1 Overview of Functions
For different applications you can save the respective function settings in so-called Settings groups, and if necessary enable them quickly.
You can save up to 8 different settings groups in the device. In the process, only one settings group is active at any given time. During operation, you can switch between settings groups. The source of the switchover can be selected via a parameter.
You can switchover the settings groups via the following alternatives:

• Via the on-site operation panel directly on the device
• Via an online DIGSI connection to the device
• Via binary inputs
• Via a communication connection to the substation automation technology.

The communication protocols IEC 60870-5-103, IEC 60870-5-104, IEC 61850, DNP, or Modbus TCP can be used for switching the settings groups.
A settings group includes all switchable settings of the device. Except for a few exceptions (for example, general device settings such as rated frequency), all device settings can be switched.
For detailed information about the settings groups, refer to the Operating Manual and to the DIGSI 5 Online Help.
3.8.1.2 Structure of the Function
The function of the Settings group switching is a supervisory device function. Accordingly, the settings and indications of the settings group switching can be found in DIGSI 5 and at the on-site operation panel of the device, below the general device settings respectively.
If you want to switchover a settings group, navigate to DIGSI 5 or proceed on the on-site operation panel of the device, as follows:

• Via the project tree in DIGSI 5: Project -> Device -> Settings -> Device settings
• Via the on-site operation panel of the device: Main menu → Settings → General → Group switchover

The indications for the settings group switching can be found in the DIGSI 5 project tree under: Project → Device → Information routing → General
3.8.1.3 Function Description
Activation
If you want to use the Settings group switching function, you must first set at least 2 settings groups in DIGSI 5 (parameter Number of settings groups > 1). You can set up a maximum of 8 settings groups. The settings groups set in DIGSI 5 are subsequently loaded into the device.
Mechanism of the Switchover
When switching over from one settings group to another, the device operation is not interrupted. With the 2dfcbba843c4f68d9da3529601704025 parameter, you are either specifying a certain settings group or you allow switching via control (IEC 60870-5-103, IEC 61850) or via binary input.
Switching via Control
When using the Control function for switching, the settings groups can be switched via a communication connection from the substation automation technology or via a CFC chart.
The communication protocols IEC 60870-5-103, IEC 60870-5-104, IEC 61850, DNP, or Modbus TCP can be used for switching the settings groups via a communication connection.
In order to use a CFC chart for switching, you must create a new CFC chart in DIGSI 5. Create the CFC chart in the DIGSI 5 project tree under Name of the device →Charts →Add new chart. Link the signals that control settings group switching in the CFC chart.
Switching via Binary Input
There are 3 appropriate input signals available for switching via binary inputs. These input signals allow selection of the settings group via a binary code. If one of the 3 signals changes, the signal image present will, after 100 ms (stabilization time), result in switching over to the appropriate settings group. If only 2 settings groups must be switched over, only 1 binary input is required. The following table shows the possible binary codes (BCD) and applicable settings groups (PG).
Table 3-20 Binary Codes of the Input Signals and Applicable Settings Groups

BCD Code via Binary Inputs| PG 1| PG 2| PG 3| PG 4| PG 5| PG 6| PG 7| PG 8
---|---|---|---|---|---|---|---|---

PG selection bit 3| 0| 0| 0| 0| 1| 1| 1| 1
PG selection bit 2| 0| 0| 1| 1| 0| 0| 1| 1
PG selection bit 1| 0| 1| 0| 1| 0| 1| 0| 1

Copying and Comparing Settings Groups
In DIGSI 5, you can copy or compare settings groups with each other.
If you want to copy settings groups, select a source and target parameter group in DIGSI 5 in the device settings, and then start the copy process. The device settings can be found in the DIGSI 5 project tree under Project → Device → Settings → Device settings.
If you want to compare settings groups, it is possible to do so in all setting sheets for settings. You will then select in addition to the active settings group, a 2nd settings group for comparison. Active setting values and the comparable values are displayed next to each other. For settings that cannot be switched over, no comparable values are displayed.
Indication of Settings Group Switchings
Every settings group shows an applicable binary indication as well as its activation and deactivation. The process of settings group switching is also logged in the log for settings changes.
3.8.1.4 Application and Setting Notes
Parameter: Number settings groups

• Default setting (_:113) Number settings groups = 1
  With the parameter Number settings groups, you can set the number of available settings groups; you can switch between these.
  Parameter: Activat. of settings group

• Default setting (_:114) Activat. of settings group = settings group 1
  With the parameter Activat. of settings group, you specify the settings groups that you want to activate, or the mechanisms via which the switchover is allowed. You can switchover only between the settings groups specified with the parameter Number settings groups.

initiated via a communication connection from a substation automation technology or via a CFC chart.
The communication protocols IEC 60870-5-103, IEC 60870-5-104, IEC 61850, DNP, or Modbus TCP can be used for switching the settings groups via a communication connection.
via binary input| The switchover between the settings groups functions exclusively via the binary input signals routed to the settings group switching.
settings group 1
…
settings group 8| They define the active settings groups. You can define the active settings groups in DIGSI 5, or directly on the device via the on- site operation.

3.8.1.5 Settings

Change group
:113| General:Number settings groups| | 1 to 8| 1
:114| General:Activat. of settings group| | •         via control
•         via binary input
•         settings group 1
•         settings group 2
•         settings group 3
•         settings group 4
•         settings group 5
•         settings group 6
•         settings group 7
•         settings group 8| settings group 1

3.8.1.6 Information List

General
:500| General:>SG choice bit 1| SPS| I
:501| General:>SG choice bit 2| SPS| I
:502| General:>SG choice bit 3| SPS| I
:300| General:Act. settings group 1| SPC| C
:301| General:Act. settings group 2| SPC| C
:302| General:Act. settings group 3| SPC| C
:303| General:Act. settings group 4| SPC| C
:304| General:Act. settings group 5| SPC| C
:305| General:Act. settings group 6| SPC| C
:306| General:Act. settings group 7| SPC| C
_:307| General:Act. settings group 8| SPC| C

3.8.2 General Device Settings
3.8.2.1 Overview
In Device settings in DIGSI 5, you find the following general settings.Figure 3-124 General Device Settings
The following list shows you the chapters containing the desired information.
You can find more about:

• Chatter blocking in 3.7.1 Signal Filtering and Chatter Blocking for Input Signals.
• Control in 6.3 Control Functionality.
• Continuous Function Chart Quality Treatment in 3.2.3 Quality Processing/Affected by the User in CFC Charts.

Under Device, you set the parameters for the device that are valid across functions.
With Test support, indications issued via communication interfaces are labeled with an additional test bit, if this is supported by the protocol. With this test bit you can determine whether an indication is generated in a test and all or individual functions of the device are in the test mode. In this manner the reactions that are necessary in normal operation due to an indication can be suppressed in other devices that receive these indications. You can also permit, for example, a trip command to close an energized binary output for test purposes. Siemens recommends deactivating the Test support again after the test phase.
3.8.2.2 Application and Setting Notes
The major portion of the settings is described in the chapters cited above. Then, the parameters on the section Device, Spontaneous indication, and Test support are described.
Parameter: Rated frequency

• Default setting (_:101) Rated frequency = 50 Hz
  With the parameter Rated frequency, you set the rated frequency of the electrical power system.
  Parameter: Minimum operate time

• Default setting (_:102) Minimum operate time = 0.00 s
  With the parameter Minimum operate time, you set the minimum duration for the trip command of the functions. The trip command is maintained for the set duration.
  Parameter: Block monitoring dir.

• Default setting (_:138) Block monitoring dir. = off
  With the parameter Block monitoring dir., you set whether indications are output via the system interface(s) of the SIPROTEC 5 device or not.
  If transmission blocking is switched on, no indications are output via the system interface(s) of a SIPROTEC 5 device, except via the IEC 61850 interface(s).
  To avoid receiving IEC 61850 data, the corresponding IEC 61850 Client must stop the reporting or freeze the data. You can find more information in the Communication Protocols Manual (C53000-L1840-C055-3).
  Parameter: Fault-display

• Default setting (_:139) Fault-display = with pickup
  With the parameter Fault-display, you set whether spontaneous fault indications which are signed as NT (conditioned latching) in the matrix, get stored with every pickup or only for one tripping.
  Keep the DIGSI 5 routing options in chapters 3.1.7 Spontaneous Indication Display in DIGSI 5 and 3.1.9 Stored Indications in the SIPROTEC 5 Device in mind.
  Parameter: Activate device test mode

• Default setting (_:150) Activate device test mode = inactive
  With the parameter Activate device test mode, you can activate the test mode for the complete device. This means that all indications generated in the device are given a test bit.
  For further information, refer to 3.8.3 Enabling/Disabling the Application/Test Mode for the Entire Device.
  Apart from activating the test mode via this parameter, you can also activate the test mode using the IEC 61850-8-1 protocol. For more information, refer to the SIPROTEC 5 Communication protocol manual.
  When the test mode is activated for the complete device, but the parameter Oper.bin.outp. under test is not, the routed relay outputs of the device are not activated by the generated the indications.

NOTE
The device remains in test mode during every restart until you intentionally set the device back into the process mode or you have carried out an initial start.
You can set the process mode by switching the parameter Activate device test mode to inactive again (removing the check mark) or by deactivating the test mode again via the IEC 61850-8-1 protocol.
NOTE
Besides the cross device test mode, you also have the option to place an individual function or stage into test mode depending on the supported operating modes of a function or stage. To do this, see the description of the relevant function or stage.
When you place an individual function or stage into the test mode, all indications issued by this function or stage are given a test bit.
When you activate the test mode for an individual function or stage, but not the parameter Oper.bin.outp. under test, the routed relay outputs of the function or stage are not activated by the generated indications.
An individual function or stage remains in the test mode during every restart until you have intentionally deactivated the test mode for this function or stage again or carried out an initial start.
Parameter: Oper.bin.outp. under test

• Default setting (_:151) Oper.bin.outp. under test = inactive

If you activate the parameter Oper.bin.outp. under test, the indications generated in the device and marked with a test bit can be issued to a routed relay output of the device, that is, you enable the relay outputs of the device to be opened and closed.
If only one individual function or stage of the device is in test mode, that is, the cross device tested mode has not been activated, only the indications of this function or stage are marked with a test bit and the routed relay outputs of the device are activated.
NOTE
If the parameter Oper.bin.outp. under test is inactive (default setting), the Test state of a function or stage is changed to Test/Relays blocked.
Output Signal: Functions in Test mode
Normally, the output signal Functions in Test mode is prerouted to the last LED of the device base module. If one or more protection or control functions are in test mode, the output signal Functions in Test mode is generated and the corresponding LED of the device lights up red.
3.8.2.3 Settings

Device
:101| General:Rated frequency| | •         50 Hz
•         60 Hz| 50 Hz
:102| General:Minimum operate time| | 0.00 s to 60.00 s| 0.00 s
_:138| General:Block moni- toring dir.| | •         off
•         on| off
Setting change
_:163| General:Reserv.time for com.prot.| | 0 s to 65535 s| 120 s
Spontan.indic.
_:139| General:Fault-display| | •         with pickup
•         with trip| with pickup
Control
_:166| General:Shows inter- lock.cond. HMI| | •         0
•         1| false
Addr.| Parameter| C| Setting Options| Default Setting
---|---|---|---|---
Test support
:150| General:Activate device test mode| | •         0
•         1| false
:151| General:Oper.bin.outp. under test| | •         0
•         1| false

3.8.2.4 Information List

General
:500| General:>SG choice bit 1| SPS| I
:501| General:>SG choice bit 2| SPS| I
:502| General:>SG choice bit 3| SPS| I
:503| General:>Sw. authority local| SPS| I
:504| General:>Sw. authority remote| SPS| I
:505| General:>Sw. mode interlocked| SPS| I
:506| General:>Sw. mode non-interl.| SPS| I
:510| General:>Test mode on| SPS| I
:511| General:>Test mode off| SPS| I
:507| General:>Dev. funct.logout on| SPS| I
:508| General:>Dev. funct.logout off| SPS| I
:512| General:>LED reset| SPS| I
:513| General:>Light on| SPS| I
:300| General:Act. settings group 1| SPC| C
:301| General:Act. settings group 2| SPC| C
:302| General:Act. settings group 3| SPC| C
:303| General:Act. settings group 4| SPC| C
:304| General:Act. settings group 5| SPC| C
:305| General:Act. settings group 6| SPC| C
:306| General:Act. settings group 7| SPC| C
:307| General:Act. settings group 8| SPC| C
:318| General:Active settings group| INS| O
:308| General:Switching auth. station| SPC| C
:324| General:Enable sw. auth. 1| SPC| C
:325| General:Enable sw. auth. 2| SPC| C
:326| General:Enable sw. auth. 3| SPC| C
:327| General:Enable sw. auth. 4| SPC| C
:328| General:Enable sw. auth. 5| SPC| C
:311| General:Switching authority| ENS| O
:312| General:Switching mode| ENS| O
:309| General:Sw.authority key/set| ENS| O
:310| General:Sw.mode key/set| ENS| O
:52| General:Behavior| ENS| O
:53| General:Health| ENS| O
:51| General:Test mode| ENC| C
:321| General:Protection on| SPC| C
:54| General:Protection inactive| SPS| O
No.| Information| Data Class (Type)| Type
---|---|---|---
:319| General:Device logout| SPC| C
:313| General:Logged off via BI| SPS| O
:314| General:Logged off via control| SPS| O
:315| General:Device logged off| SPS| O
:323| General:LED reset| SPC| C
:320| General:LED have been reset| SPS| O
:509| General:>Block monitoring dir.| SPS| I
:317| General:Block monitoring dir.| SPS| O
:329| General:Functions in Test mode| SPS| O

3.8.3 Enabling/Disabling the Application/Test Mode for the Entire Device
Siemens recommends to enable the test mode for the entire device before you start testing protection functions.
You can enable or disable the test mode for the entire device as follows:

• Via the on-site operation panel under Device functions > Operating states > Application mode = Test or Test/Relay blk.
• Via the binary inputs (:91:510) General:>Test mode on and (:91:511) General:>Test mode off You can find the binary inputs in the DIGSI information routing under General.
• Via communication (IEC 61850) with the controllable (_:91:56) General:Application mode You can find the controllable in the DIGSI information routing under General.

When the test mode for the entire device is enabled, the indication (:91:329) Functions in Test mode is generated.
In the test mode of the device all device indications are marked with a test bit. This prevents the circuit breaker from switching unintentionally or protection functions from starting unintended actions. If you enable or disable the test mode for the entire device using the controllable (:91:56) General:Application mode, the device stores the state of the controllable in a voltage-fail-safe memory. Figure 3-125 Logic Diagram: Enabling/Disabling the Test Mode for the Entire Device
The following figures show possible variants for enabling and disabling the test mode for the entire device using binary inputs. The following figure shows the use of push-buttons Ta1 and Ta2:Figure 3-126 External Wiring of Push-Buttons for Enabling/Disabling the Test Mode for the Entire Device
The following figure shows the use of a switch S. Route the logical binary input (:91:510)
General:>Test mode on as H (high-active) and the logical binary input (:91:511) General:>Test mode off as L (low-active) to a physical binary input.
Figure 3-127 External Wiring of Switches for Enabling/Disabling the Test Mode for the Entire Device
3.8.4 Device Logout
3.8.4.1 Overview
In the case of multibay functions, a device uses information from one or more other devices. For some applications, it may be necessary for you to remove a device with all effective functions temporarily from the plant and even to switch it off. These applications are, for example:

• Maintenance work
• System upgrades
• Testing the local protection functions, for example, the local line differential protection

The Device logout functionality informs the receiver devices about the imminent disconnection of the transmitter devices. To do this, the last valid received information is stored in the receiver devices and used for the multibay functions.
NOTE
If you need to remove a device temporarily from the plant, you must log off the device.
Protection functions distributed to several devices operate in a healthy manner with the remaining devices only if you have logged off the device.
You can log off the device as follows:

• Via the on-site operation panel
• Via a communication interface using the Device logout (_:319) controllable
• Via the binary inputs, general: >Dev. funct.logout on (:507) or >Dev. funct.logout off (:508)

You can find the controllable and the binary inputs in the DIGSI 5 project tree under Name of the device → Information routing in the working area in the General block.
During the log-off process, the device checks whether all conditions for a logout have been met. If the conditions for the log off have not been met, the logout is rejected.
The logout is rejected under the following conditions:

• The devices are communicating via the protection interface and switching off the device leads to an interruption in protection-interface communication.
• The Line differential protection function is operating in the device and the local circuit breaker is still switched on.

In this case, you must switch off the local circuit breaker and repeat the log-off process for the device.
After the logout, the local Line differential protection function is removed from the summation of the currents for the Line differential protection of the other devices. The Line differential protection function remains active in the other devices.
NOTE
The path used to log the device off is stored in the operational log.
Even if you switch off the device after logout, the Device logged off (_:315) state is stored.
If you want to establish the initial state again after logging off the device, you must log on the device again.
To log on the device, you must use the same option used for logout. For example, if you have logged off the device via binary inputs, you must log it on again via the binary inputs. This applies in similar manner if you have logged off the device via DIGSI or via on-site operation.
3.8.4.2 Application and Setting Notes
Logoff Options for a Device
You can log a device off as follows:

• Via the on-site operation panel
• Via communication through the controllable Device logout (_:319)
• Via the binary inputs, general: >Dev. funct.logout on (:507) or >Dev. funct.logout off (:508)

Conditions for Logging off the Device Figure 3-128 Logic for Logging off the Device
The conditions for a successful logout of the device result from the conditions for every activated protection function.
Logoff of a Device from a Device Combination with Communication via the IEC 61850-8-1 (GOOSE) Protocol If devices are exchanging data using the IEC 61850-8-1 (GOOSE) protocol – for example in the case of substation interlocking – for each received data point the value of this data point can be set in the receiver device when the transmitter device logs off. This value remains effective in the receiver device until the logout is canceled by the transmitter device, even if the transmitter and/or the receiver are switched off in the meantime.
Logoff of a Device from a Device Combination Using Protection Communication
If devices in a device combination communicate via the protection interface, you can only log off a device under the following conditions:

• Logging off and switching off a device in a device combination must not result in an interruption in the protection communication.
• For series-connected topologies, the device must be located at one end of the communication chain as otherwise the protection communication is interrupted when the device is logged off and switched off.

For this reason, devices not at one of the ends in series-connected topologies cannot be logged off.
Logout via Binary Inputs
The following diagrams show potential variants on how to control binary inputs. If you want to use pushbuttons, switch on this function as shown in the following figure. Log off the device using the push-button
Key2; log on the device again with the push-button Key1. Figure 3-129 External Push-Button Wiring for Logging off the Device
If a switch is being used for control, route the binary input >Dev. funct.logout on as H (active with voltage) and the binary input >Dev. funct.logout off as L (active without voltage). If the switch S is closed, the device is logged off.Figure 3-130 External Switch Wiring for Logging off the Device
Indications
The logged-off device reports the status ((:315) Device logged off) and cause of the logout.
If you have logged off the device using binary inputs, the indication (:313) Logged off via BI results.
If you have logged off the device using on-site operation, via DIGSI 5 or via the protection interface,the indication (_:314) Logged off via control is issued.
The indications are stored in the operational log.
3.8.4.3 Information List

General
:507| General:>Dev. funct.logout on| SPS| I
:508| General:>Dev. funct.logout off| SPS| I
:319| General:Device logout| SPC| C
:313| General:Logged off via BI| SPS| O
:314| General:Logged off via control| SPS| O
:315| General:Device logged off| SPS| O

3.9 Display Pages
3.9.1 Display-Page Setting
3.9.1.1 Overview
Specific SIPROTEC 5 devices can be ordered with the operation-panel option Large display, display-page size config., dual c.LEDs. In this case, the size of the configurable display pages is settable by the user, and is function- points dependent:

• Small display pages can be configured without extra function points.
• Large display pages for large control displays require extra function points.

For devices with the operation panel Large display, display-page size config., dual c.LEDs, you can find the block Display pages in Device settings in DIGSI 5. Figure 3-132 Block Display pages in DIGSI 5 3.9.1.2 Application and Setting Notes
Parameter: Functionality

• Default setting (_:139) Functionality = small size

With the parameter Functionality, you set the size of the display pages that are shown in DIGSI 5 and in the HMI.

With this size, usually up to 8 operational values or very small control displays with, for example, up to 3 switches can be configured.
Figure 3-133    Example of Display Page in DIGSI 5 (Small Size)| Figure 3-134    Example of Display Page in the HMI (Small Size)
Large control display| The size of the display page is 240 x 320 pixels.
With this size, large control displays or a large number of operational values, or a combination of both can be configured.
Figure 3-135    Example of Display Page in DIGSI 5 (Large Control Display)| Figure 3-136    Example of Display Page in the HMI (Large Control Display)

Applications

4.1 Overview
The function library in DIGSI 5 provides application templates for the standard applications of the devices. The application template

• Supports the fast realization of complete protection solutions for standard applications

• Contains the basic configuration for the use case

• Contain functions and default settings for the use case
  When using an application template, note the following:

• Adapt the application template to your specific application (check/adapt default settings, delete/add functions).
  You can find more detailed information on this in 2.1 Embedding of Functions in the Device.

• Check the routing of binary outputs with respect to fast and normal relay.

• Check the logic block chart for the group warning indication

The following describes the application templates of the 6MD84 I/O box.
NOTE
The availability of certain settings and setting options depends on the device type and the functions available on the device!
4.2 Application Template and Functional Scope for the 6MD84 Device
The following application template is available for the device 6MD84 in the DIGSI 5 function library:

• Not pre-configured

Application Template: 6MD84 not configured
An unconfigured application template is available for the IO box 6MD84, from which you do not have to delete anything. You can set up your own configuration on it.

Function-Group Types

5.1 Function-Group Type Circuit Breaker
5.1.1 Overview
The Circuit-breaker function group combines all the user functions that relate to a circuit breaker.
You will find the Circuit-breaker function group under each device type in the function library in DIGSI 5. The Circuit-breaker function group contains all of the control and supervision functions that you can use for this device type. The following figure shows, for example, the functional scope of the Circuit-breaker function group.Figure 5-1 Circuit-Breaker Function Group – Functional Scope
The Circuit-breaker function group includes 2 different types of circuit breakers:

• Circuit breaker [control]
• Circuit breaker [status only]

The type circuit breaker [status only] is used only for acquiring the circuit- breaker switch position. This type can be used to model switches that can only be read but not controlled by the SIPROTEC 5 device.
5.1.2 Circuit Breaker
5.1.2.1 Overview
The function block Circuit breaker represents the physical switch in the SIPROTEC 5 device.
The basic tasks of this function block are:

• Operation of the circuit breaker (CB)
• Acquisition of the circuit-breaker auxiliary contacts
• Acquisition of other circuit-breaker information

The function block Circuit breaker provides the following information:

• Number of switching cycles
  5.1.2.2 Opening, and Closing the Circuit Breaker
  The circuit breaker is operated in the following situations:

• Opening of the circuit breaker as a result of control operations

• Closing of the circuit breaker as a result of control operations

For the operational handling of the circuit breaker, the function block Circuit breaker provides the output signals that must be routed to the corresponding binary outputs of the device (see Table 5-1).

Figure 5-2 Opening and Closing the Circuit Breaker
Table 5-1 Description of the Output Signals

The Output time parameter affects the signal.
The signal is pending for the duration of the output
time, with the following exceptions:
• Only when switched off by the control:
The signal is reset before expiration of the period if the auxiliary contacts report that the circuit breaker is open before expiration of the period.| • Unlatched
Close command| This signal executes all closing operations.
The Output time parameter affects the signal.
The signal is pending for the duration of the output time, with the following exception: The signal is canceled before expiration of the period if the auxiliary contacts report that the circuit breaker is closed
before expiration of the period.| Normal routing
Command active| This signal is active if one of the following binary outputs is active:
• Open command
• Close command
The binary outputs are active as long as a switching command is being executed by the control.| Normal routing

5.1.2.3 Acquisition of Circuit-Breaker Auxiliary Contacts and Further Information
To determine the circuit-breaker position, the function block Circuit breaker provides position signals. These signals are of the Double-point indication (DPC) type. A double-point indication can be routed to 2 binary inputs so that the open and closed circuit-breaker switch positions can be reliably acquired.

Figure 5-3 Acquisition of the Circuit-Breaker Information

The switch position CB 3-pole open and/or the position CB 3-pole closed can be detected by routing  to 1 or 2 binary inputs.

The signals must be routed to the binary input that is with the CB auxiliary contacts. The open and closed signals do not necessarily have to be routed in parallel. The advantage of parallel routing is that it can be used to determine an intermediate or disturbed  position. If you route only one signal (open or closed), you cannot determine an intermediate position or a disturbed position.
In the monitoring direction, the position signals generate the following information when the open andb closed positions are detected (see following table). This information is further processed by the Circuitbreaker position recognition and Control function blocks.

intermediate position. The signal open and the signal  closed have not been set.
Disturbed position| SPS| The circuit-breaker switch position is in the disturbed position. The signal open and the signal  closed have been set simultaneously.
Not selected| SPS| The circuit breaker is not selected for a control operation.

The following table shows the additional input signals:

the circuit-breaker auxiliary contacts (see Other  Functions 3.7.3 Persistent Commands for a description of acquisition blocking).

Reset AcqBlk&Subst| SPS| This is used to reset acquisition blocking and manual update of the circuit breaker. If the signal is  active, acquisition blocking and manual update are reset.
Ready| SPS| The active signal indicates that the circuit breaker is ready for an OpenClosed-Open cycle.
The signal remains active as long as the circuit breaker is unable to trip.
The signal is used in the Automatic reclosing and Circuit-breaker test functions.

The following table shows one additional output signal:

circuit breaker.
For this, all failure information of the circuit breaker must be detected via a binary input. This  failure information can set the appropriate state of the External health signal with a CFC chart  (using the BUILD_ENS block).
The signal has no effect on the health of the function block.

5.1.2.4 Application and Setting Notes
Routing to Evaluate the Circuit-Breaker Switch Position

The operating principle of the auxiliary contacts is described in the individual functions.
Siemens recommends capturing the information Circuit breaker is open in 3 poles and Circuit breaker is closed in 3 poles via auxiliary contacts. This is the optimal configuration for the control functionality. For purely protection applications, it is also sufficient  to acquire just one of the 2 circuit- breaker switch positions. When used as a protection and control device, Siemens recommends the following evaluation of the circuit-breaker switch position:

Figure 5-4 Recommended Evaluation of the Circuit-Breaker Switch Position
The following diagram shows the recommended routing, in which OH stands for active with voltage.

Figure 5-5 Routing for Acquisition of the Circuit-Breaker Switch Position via 2 Auxiliary Contacts
The device can also function without the analysis from the circuit-breaker auxiliary contacts, that is, routing of the auxiliary contacts is not absolutely necessary. However, this is a requirement for control functions.

Parameter: Output Time

• Default setting (_:101) Output time = 0.10 s
  The Output time parameter acts on the signals for tripping, opening, and closing of the circuit breaker.

CAUTION
Do not set a time that is too short.
If you set a time that is too short, there is a danger that the device contacts will interrupt the control
circuit. If this happens, the device contacts will burn out.

• Set a time that is long enough to ensure that the circuit breaker reliably reaches its final position (open or closed) after a control operation.

5.1.2.5 Settings

Circuit break.
_:101| Circuit break.:Output time| | 0.02 s to 1800.00 s| 0.10 s

5.1.2.6 Information List

No.| Information| Data Class
(Type)| Type
---|---|---|---
Circuit break.
:500| Circuit break.:>Ready| SPS| I
:501| Circuit break.:>Acquisition blocking| SPS| I
:502| Circuit break.:>Reset switch statist.| SPS| I
:504| Circuit break.:>Reset AcqBlk&Subst| SPS| I
:503| Circuit break.:External health| ENS| I
:53| Circuit break.:Health| ENS| O
:58| Circuit break.:Position| DPC| C
:300| Circuit break.:Trip/open cmd.| SPS| O
:301| Circuit break.:Close command| SPS| O
:302| Circuit break.:Command active| SPS| O
_:306| Circuit break.:Op.ct.| INS| O

5.2 Function-Group Type Analog Units
5.2.1 Overview

The function group Analog units is used to map analog units and communicate with them. Analog units are external devices, such as RTD units, or analog plug-in modules or measuring-transducer modules.
You can find the function group Analog units for many device types in the Global DIGSI 5 library.

Figure 5-6 Analog Unit Function Group in DIGSI

5.2.2 Structure of the Function Group
If the device has a measuring transducer, it is automatically mapped in the function group Analog units. If one or more RTD units are connected to the device, you have to load one or more RTD unit Ether. or RTD unit serial functions from the Global DIGSI 5  library in order to map the RTD units.
If the device is connected to a power-plant control system or another protection device, you must load one or more Temperature acquisition via protocols functions from the Global DIGSI 5 library to form the protocols.
The following figure shows the structure of the function group.

Figure 5-7 Structure of the Function Group Analog Unit

Gray: Optionally wired, optionally available
White: Always wired, always available

The function group Analog units has interfaces to protection function groups. The function group Analog units provides, for example, measured temperature values that come from an external RTD unit , a measuring transducer or via protocols. These measured  temperature values are available for all protection function groups in which a temperature monitoring function works.
The function RTD unit Ether. is not preconfigured by the manufacturer. A maximum of 20 function instances can operate simultaneously.
The structure of the function RTD unit serial is identical to the structure of the function RTD unit Ether..
The function 20-mA unit Ether. is not preconfigured by the manufacturer. A maximum of 4 function instances can operate simultaneously. The structure of the function 20 mA serial unit is identical to the structure of the function 20-mA unit Ether..

The function Temperature acquisition via protocols has 2 stage types: The Temperature acquisition via PROFINET IO or IEC 61850 and the Temperature acquisition via GOOSE. One instance of the Temperature acquisition via PROFINET IO or IEC 61850 is  preconfigured by the manufacturer. A maximum of 12 instances can operate simultaneously for both stage types.

5.2.3 20-mA Unit Ethernet
5.2.3.1 Overview
The function 20-mA unit Ether.:

• Communicates in series with a 20-mA unit via the Slave Unit Protocol (SUP) and records the values measured by the 20-mA unit
• Transforms the measured 20-mA values into slowly changing process tags such as temperature or gas pressure
• Makes the recorded process tags available to CFC, GOOSE, protocols and the device display
• Monitors communication with the 20-mA unit

5.2.3.2 Structure of the Function
The function 20-mA unit Ether. can only work in the function group Analog units. A maximum of 4 function instances can work simultaneously. Each instance contains 12 preconfigured channel function blocks.
The function 20-mA unit Ether. contains input and output channels which can be configured independently of one another.

Figure 5-8 Structure/Embedding of the Function

5.2.3.3 Communication with 20-mA Unit Ethernet

Logic

Figure 5-9 Logic of the Function 20-mA Unit Ethernet

Communication with 20-mA Unit
The function is used to communicate with a 20-mA unit connected via an Ethernet connection. When a connection of the function to an external 20-mA unit via an Ethernet interface has successfully been established, the 20-mA unit sends the measured values  of all connected channels to the function 20‑mA unit.
Ether.. For the connection to be established successfully, specific communication settings must be specified.
You can find more detailed information in 5.2.3.4 Application and Setting Notes.
The 20-mA measuring unit 7XV5674 is supported.

Error Responses
The following table lists the conditions under which the status Health transitions to the Alarm or Warning state.
Table 5-2 Error Responses

The function 20-mA unit Ether. cannot establish a connection witha communication module.| Alarm
The function 20-mA unit Ether. sends TCP settings to the  communication module, which evidently would like to  connect to the 20-mA unit via a  serial protocol.
This communication module does not establish a connection  to the 20-mA unit.| Alarm
The connection between the communication module and the 20-mA unit  causes a time-out indication.| Warning
A communication module has not received any more data from the 20-mA  unit for 9 sec.| Warning

5.2.3.4 Application and Setting Notes
Parameter: Port

• Default setting (_:2311:103) Port = port J
  With the parameter Port, you define the port connecting the 20-mA unit to the SIPROTEC 5 device.

Parameter: IP address

• Default setting (_:2311:104) IP address = 10.16.60.1
  With the parameter IP address, you set the IP address of the 20-mA unit connected to the communication module via the TCP protocol. You must assign each 20-mA unit an unambiguous IP address. The IP address to be set depends on your network  configuration. You can set any valid IPv4 address that does not cause conflicts with other IP addresses in the network. First set an IP address for the 7XV5674 20-mA unit. Then specify the parameter IP address for the communication module to the same  address.

Settings on the 20-mA Unit
Set the 7XV5674 20-mA unit with a Web browser on the laptop computer via the latter’s Ethernet interface.
Set Modbus TCP as a bus protocol/operating mode.
You can find detailed notes on the settings in the 7XV5674 manual that accompanies the 20-mA unit. The documents are also available in the SIPROTEC download area (www.support.industry.siemens.com).

5.2.3.5 20-mA Channel
Logic

1. If the setting Range active is set to test , the setting Transformation ratio is not displayed.
2. If the setting Range active is set to false, the settings Upper limit, Transformation ratio upper limit, Lower limit and Transformation ratio are not displayed.

Measured-Value Calculation
The function 20-mA channel processes a single 20-mA current signal supplied by the 20-mA unit of the corresponding channel. The 20-mA current measured value is converted into the correct physical quantities such as temperature or pressure. In each 20-mA  functional unit (Ether. and serial) there are always 12 of the 20-mA channel function blocks, even if fewer channels are connected with the 20-mA unit. The calculated values are available for further processing via CFC, GOOSE, protocols, and the display image.

Measured-Value Processing
The 20-mA unit typically transmits a value which represents a physical quantity, such as a temperature or a pressure. Therefore, the device must contain a characteristic curve that maps the physical quantity to the 20-mA value. If you do not activate the Range  active setting (no x in the check box), the function operates over the range 0 mA to 20 mA. If a value smaller than 0 mA or greater than 20 mA is active at the input of the 20-mA unit, the measured value is identified as invalid. The setting of the range for the scaled value goes from a usable range of 0 mA to 20 mA. The following figure shows an example.

In this example, the measured value 0 mA means a temperature of 0 °C and the measured value 20 mA means a temperature of 100 °C. So enter as Unit = °C and Conversion factor = 100. The resolution (decimal place) of the temperature value can be chosen; for  a decimal place, select Resolution = 0.1.

If you activate the Range active setting, then 4 additional parameters Upper limit, Lower limit, Upper limit – Sensor, and Lower limit – Sensor appear. The parameters Upper limit and Lower limit indicate the range of the input current in mA. The setting Upper  limit – Sensor is the calculated measured value if the input current corresponds to the value in the Upper limit setting. The setting Lower limit – Sensor is the calculated measured value if the input current corresponds to the value in the Lower limit setting. The  setting of the range for the scaled value corresponds to the useable range between Lower limit and Upper limit (see following figure).

In this example, the Range active setting is selected. The setting Upper limit is at 20 mA, the setting
Lower limit is at 4 mA. The setting Upper limit – Sensor is at 55 and the setting Lower limit Sensor is at -33. If the input current is smaller than 4 mA or greater than 20 mA, the quality of the scaled measured value in this example is invalid.
Each 20-mA channel makes available the scaled measured value in the information routing (these are the temperature values in the examples) and the original current measured value in mA for further processing.
The 20-mA values can be displayed in the display page and processed with CFC charts.

Error Responses
If the current input value is determined to be incorrect, the quality attribute of the output value is set to invalid That status for Health and the defect status assume the states displayed in the table.

Table 5-3 Error Responses

5.2.3.6 Application and Setting Notes
Parameter: Unit

• Default setting (_:13111:103) Unit = °C

With the Unit parameter, you set the physical unit of measurement the measured values. The possible setting values are listed in the settings table.

Parameter: Conversion factor

• Default setting (_:13111:104) Conversion factor = 100

With the Conversion factor parameter, you set the conversion factor for the measuring transducer.

Parameter: Resolution

• Default setting (_:13111:108) Resolution = 0.1

With the Resolution parameter, you set the resolution of the scaled values.

Parameter: Range active

• Default setting (_:13111:107) Range active = false

If you do not activate the parameter Range active (no x in the check box), the function operates over the range 0 mA to 20 mA. The setting of the range for the scaled value goes from a usable range of 0 mA to 20 mA.
If you activate the parameter Range active, the 4 additional parameters Upper limit, Upper limit Sensor, Lower limit, and Lower limit – Sensor appear.

Parameter: Upper limitLower limitUpper limit – Sensor and Lower limit – Sensor

• Default setting (_:13111:105) Upper limit = 20.000 mA
• Default setting (_:13111:109) Upper limit – Sensor = 100
• Default setting (_:13111:106) Lower limit = 4.000 mA
• Default setting (_:13111:110) Lower limit – Sensor = 100

If you activate the parameter Range active , the 4 additional parameters Upper limit, Lower limit, Upper limit – Sensor, and Lower limit – Sensor appear. The parameter Upper limit Sensor is the calculated measured value if the input urrent corresponds to the value in the Upper limit setting. The parameter Lower limit – Sensor is the calculated measured value if the input current corresponds to the value in the Lower limit setting.
The following settings and information table shows only 1 of the 12 channels, as the setting possibilities of the 12 channels do not differ.

5.2.3.7 Settings

• port F
• port J
• port N
• port P| port J

5.2 Function-Group Type Analog Units

Channel 1
:13111:103| Channel 1:Unit| | • %
• °
• °C
• °F
• Ω
• Ω/km
• Ω/mi
• 1/s
• A
• As
• cos φ
• cycles
• dB
• F/km
• F/mi
• h
• Hz
• Hz/s
• in
• J
• J/Wh
• K
• l/s
• m
• mi
• min
• p.u.
• Pa
• periods
• rad
• rad/s
• s
• V
• V/Hz
• VA
• VAh
• var
• varh
• Vs
• W
• W/s
• Wh| m
:13111:108| Channel 1:Resolution| | • 1
• 0.1
• 0.01
• 0.001| 0.1
:13111:107| Channel 1:Range active| | • 0
• 1| FALSE
:13111:104| Channel 1:Conversion factor| | 1 to 1000000| 100
:13111:105| Channel 1:Upper limit| | 0.00 mA to 20.00 mA| 20.00 mA
:13111:109| Channel 1:Upper limit Sensor| | -1000000 to 1000000| 100
:13111:106| Channel 1:Lower limit| | 0.00 mA to 20.00 mA| 4.00 mA
:13111:110| Channel 1:Lower limit Sensor| | -1000000 to 1000000| 100

5.2.3.8
Information List

General
:2311:53| General: Health| ENS| O
:2311:56| General: Failure| SPS| O
Channel 1
:13111:53| Channel 1: Health| ENS| O
:13111:71| Channel 1: Failure| SPS| O
:13111:301| Channel 1: 20-mA output scale| MV| O
:13111:302| Channel 1: 20-mA output raw| MV| O

5.2.4 20-mA Unit Serial
5.2.4.1
Overview

The function 20-mA unit Serial:

• Provides serial communications with a 20-mA unit via the Modbus protocol and records the values measured by the 20-mA unit
• Transforms the measured 20-mA values into slowly changing process variables such as temperature or gas pressure
• Makes the recorded process tags available to CFC, GOOSE, protocols and the device display
• Monitors communication with the 20-mA unit

The function 20-mA unit Serial is structured in the same way as the function 20-mA Unit Ether.. The mode of operation is also identical. The only difference is that the measured values are transferred to the communication module via a serial connection instead of an Ethernet connection.
You can find more information in Chapter 5.2.3.2 Structure of the Function.

5.2.4.2 Application and Setting Notes

Parameter: Port

• Default setting (_:2311:103) Port = Port J
  With the parameter Port, you specify the slot for the communication module that will be used for the connection with an external 20-mA unit.

Parameter: Channel number

• Default setting (_:2311:105) Channel number = 1
  A serial communication module optionally uses 2 channels. With the parameter Channel number, you specify the channel number (1 or 2) used to connect the 20-mA unit to the device. The communication module inputs are labeled with the channel numbers.

Parameter: Slave address

• Default setting (_:2311:106) Slave address = 1
  With the parameter Slave address, you define the device address of the 20-mA unit. If only one 20-mA unit is connected to the serial bus, the default value 1 can be used. Set the same device address as used with the 20-mA unit. The device address is important for distinguishing several 20-mA units that are connected to a serial bus. Set an unambiguous device address on every 20-mA unit, for example, 1, 2 and 3 when connecting 3 of the 20-mA units. On every 20-mA unit, set for the parameter Slave address in the 3 functions 20-mAUnit Serial.

Parameter: Unit

• Default setting (_:13111:103) Unit = °C
  With the parameter Unit, you set the physical unit of measurement the measured values. The possible setting values are listed in the settings table.

Parameter: Conversion factor

• Default setting (_:13111:104) Conversion factor = 100
  With the parameter Conversion factor, you set the conversion factor for the measuring transducer.

Parameter: Resolution

• Default setting (_:13111:108) Resolution = 0.1
  With the parameter Resolution, you set the resolution of the scaled values.

Parameter: Range active

• Default setting (_:13111:107) Range active = false
  If you do not activate the parameter Range active (no x in the check box), the function operates over the range 0 mA to 20 mA. The setting of the range for the scaled value goes from a usable range of 0 mA to 20 mA.
  If you activate the parameter Range active, the 4 additional parameters Upper limit, Upper limit Sensor, Lower limit, and Lower limit – Sensor appear.

Parameter: Upper limit, Lower limit, Upper limit – Sensor, and Lower limit – Sensor

• Default setting (_:13111:105) Upper limit = 20 mA
• Default setting (_:13111:109) Upper limit – Sensor = 100
• Default setting (_:13111:106) Lower limit = 4 mA
• Default setting (_:13111:110) Lower limit – Sensor = 100

If you activate the parameter Range active, the 4 additional parameters Upper limit, Lower limit, Upper limit – Sensor, and Lower limit – Sensor appear. The parameter Upper limit Sensor is the calculated measured value if the input current corresponds to the value in the Upper limit setting. The parameter Lower limit – Sensor is the calculated measured value if the input current corresponds to the value in the Lower limit setting.
The following settings and information table shows only 1 of the 12 channels, as the setting possibilities of the 12 channels do not differ.

5.2.4.3 Settings

General
:2311:103| General:Port| | • port F
• port E
• port J
• port N
• port P| port J
:2311:105| General:Channel number| | 1 to 2| 1
:2311:106| General:Slave address| | 1 to 247| 1
Channel 1
:13111:103| Channel 1:Unit| | • %
• °
• °C
• °F
• Ω
• Ω/km
• Ω/mi
• 1/s
• A
• As
• cos φ
• cycles
• dB
• F/km
• F/mi
• h
• Hz
• Hz/s
• in
• J
• J/Wh
• K
• l/s
• m
• mi
• min
• p.u.
• Pa
• periods
• rad
• rad/s
• s
• V
• V/Hz
• VA
• VAh
• var
• varh
• Vs
• W
• W/s
• Wh| m
:13111:108| Channel 1:Resolution| | • 1
• 0.1
• 0.01
• 0.001| 0.1
:13111:107| Channel 1:Range active| | • 0
• 1| FALSE
:13111:104| Channel 1:Conversion factor| | 1 to 1000000| 100
:13111:105| Channel 1:Upper limit| | 0.00 mA to 20.00 mA| 20.00 mA
:13111:109| Channel 1:Upper limit Sensor| | -1000000 to 1000000| 100
:13111:106| Channel 1:Lower limit| | 0.00 mA to 20.00 mA| 4.00 mA
_:13111:110| Channel 1:Lower limit Sensor| | -1000000 to 1000000| 100

5.2.4.4 Information List

General
:2311:53| General:Health| ENS| O
:2311:56| General:Failure| SPS| O
Channel 1
:13111:53| Channel 1:Health| ENS| O
:13111:71| Channel 1:Failure| SPS| O
:13111:301| Channel 1:20-mA output scale| MV| O
:13111:302| Channel 1:20-mA output raw| MV| O

5.2.5 Communication with 20-mA Unit
5.2.5.1 Integration of a Serial 20-mA Unit
Connection of the Communication Lines
Figure 5-15 shows how to connect the 20-mA unit to the SIPROTEC 5 device. Note that Pin 1 of the RJ45 plug is connected to RTD-B and Pin 2 is connected to RTD-A.

Adding a USART Module
Add a USART-AB-1EL or a USART-AC-2EL USART module in DIGSI to the device. The USART module must be inserted at one of the plug-in positions for communication modules in the base module or in the CB202 expansion module (refer to the following figure).

Selecting the SUP Protocol
Select the Slave Unit Protocol (SUP). This protocol is responsible for the communication between the SIPROTEC 5 device and the 20-mA unit.

Communication Settings
Make the communications settings for the relevant serial channels. For this, use the default settings specified by the 20-mA unit. Normally, you must adapt only the parameterization of the SIPROTEC 5 device to the settings of the 20-mA unit. Make sure that the setting values in both devices are the same. The setting of the parameter Non-flickering light (on/off): is not relevant for the RS485 interface.

NOTE
The driver for the USART module for the SUP protocol is not preinstalled as standard for the initial use of this interface (following the firmware update).

With the selection of the SUP protocol for the 20-mA unit DIGSI automatically adds the function group Analog units to your device configuration. You can now instantiate the  function 20-mA unit serial 1 (see the following figure).

Now, set the channel number over which the SUP protocol runs. In addition, set the slave address of the 20‑mA unit. This address must be set with the same value in the 20-mA unit (refer to the following figure).
For the first use of the 20-mA unit, the following device configuration must be set on the 20-mA unit:

• Bus protocol: mod
• Device address: 1
• Baud rate: 9600
• Parity: no

Finally, load the configuration in the device.
5.2.5.2 Integration of a 20-mA Unit Ethernet
Device Configuration
In DIGSI, insert an Ethernet module into the provided slot, thus adding the module to the device configuration.
Figure 5-21 displays the available slots in the base module or on the expansion module CB202.
Alternatively, you can also use the integrated Ethernet interface Port J.

Communication Settings
Activate the SUP Ethernet protocol for the Ethernet module.

This protocol is also available for Port J of the integrated Ethernet interface of the base module (refer to following figure).

With the selection of the SUP protocol for the 20-mA unit, DIGSI automatically adds the Analog units function group and the 20-mA unit Ether. 1 function to your device configuration (refer to the following figure).

Now, set the port over which the SUP protocol runs. In addition, set the IP address of the 20-mA unit (refer to the following figure). This address must be set with the same value in the 20-mA unit.

Finally, load the configuration in the device.

5.2.6 V/I-Measuring-Transducer Unit with Fast Inputs
5.2.6.1 Overview
The fast analog measuring-transducer inputs process voltage values (DC -10 V to +10 V) as well as current values (DC -20 mA to 20 mA).
The function MT fast input:

• Provides sampled values for recording in the fault record (the maximum sampling frequency is 8 kHz for all other SIPROTEC 5 devices). The recorded sampling frequency results from the setting of the fault-recorder function.
• Calculated measured values from the sampled values. These measured values have been deduced from the arithmetic mean values. The measuring range for the mean-value calculation is adjustable in the interval from 10 ms to 100 ms.
• Converts the measured current or voltage values into process values, for example, temperature, gas pressure, etc.
• Provides the recorded process variables for further processing by the fault recorder, the CFC, and in GOOSE-applications for transmission via communication protocols, and for visualization

The fast measuring-transducer inputs are located on the IO212 module with 8 inputs (optionally current or voltage inputs), and the IO210 module with 4 inputs (optionally current or voltage inputs).

5.2.6.2 Structure of the Function
The function MT fast input works in the function group Analog units and contains the number of available measuring-transducer inputs, depending on the hardware configuration. You can configure these channels independently from one another either as current or voltage inputs.
5.2.6.3 Function Description
Once you have instantiated the MT fast input function, it will be visible in the project tree in the function group Analog units. You can find the function group Analog units in DIGSI in the Settings folder.
If you open the subdirectory MT fast input, you reach the setting sheet for the respective input (for more details, see 5.2.6.4 Application and Setting Notes).
The hardware is designed in such a way that either a current or a voltage can be processed at each input.
Use the corresponding terminals (see Hardware manual). Configure the input in accordance with the selected connection (Parameter TD input-signal type). With the parameter Measuring window, you set the measuring range with which the arithmetic mean value is determined. With the parameter Measuring window, you also determine measurement speed for the input. For example, a setting of 100 ms means that the measured value is updated every 100 ms.

The fast measuring-transducer channels can be configured either as current or as voltage inputs. Apart from this, their function corresponds to the basic function of the 20-mA channels (see chapter 5.2.3.5 20-mA Channel).

5.2.6.4 Application and Setting Notes

Parameter: TD input-signal type

• Default setting (_:101) TD input-signal type = Current input
  With the parameter TD input-signal type, you determine whether the measuring- transducer input channel works as a Current input or as a Voltage input.
  Make sure that the selected channel has also been wired correctly (see Hardware manual, Input and Output Module IO212).

Parameter: Unit

• Default setting (_:103) Unit = A
  With the parameter Unit, you set the physical unit of measurement of the measured values. The possible setting values are listed in the settings table.

Parameter: Measuring window

• Default setting (_:142) Measuring window = 10 ms
  With the parameter Measuring window, you set the measuring window that is used to determine the arithmetic mean value from the sampled values. In case of slowly varying signals, Siemens recommends setting the top value to 100 ms. With this value, a new, current measured value is provided every 100 ms for further processing.

Parameter: Range active

• Default setting (_:107) Range active = false

If you do not activate the Range active parameter, the function assumes a range of -20 mA to +20 mA or -10 V to +10 V. The setting of the range for the scaled value then assumes a usable range of -20 mA to +20 mA or -10 V to +10 V.
If you activate the parameter Range active, the 4 additional parameters Upper limit ,Upper limit Sensor, Lower limit, and Lower limit – Sensor appear.
Note that this setting is activated by either placing, or not placing the relevant check mark in DIGSI (see Figure 5-27).

Parameter: Conversion factor

• Default setting (_:104) Conversion factor = 1.00
  With the parameter Conversion factor, you set the conversion factor for the measuring transducer.

Parameter: Upper limit, Upper limit – Sensor, Lower limit, and Lower limit – Sensor
With the following parameters, you set the scaling of the measuring variables. By that, you can scale in an application-specific way:

• Default setting Upper limit = 20.00 mA
• Default setting Upper limit – Sensor = 1.00
• Default setting Lower limit = -20.00 mA
• Default setting Lower limit – Sensor = 1.00
  With these setting parameters, you set the operating range of the measuring transducer as well as the conversion of the values transmitted to the sensor values. Harmonize the operating range of the measuring transducer with the transmitter of the sensor. Using the free scalability of the system, you can meet different requirements. The following  figure shows the setting parameters in general terms.

If you keep the preset limiting values, the following conditions are possible:

• If the input current is < 2.000 mA
  The function issues the indication Broken wire and the quality of the output value is invalid. The functions that use the output value as the measured value can be deactivated.

• If the input current is > 2.500 mA
  The indication Broken wire drops out.

Setting Example 1:
A measuring transducer transmitting a current signal of 4 mA to 20 mA is used as a transmitter. Currents well below -25.6 mA or above +25.6 mA indicate a transmitter failure. A  sensor detecting a temperature is attached to the transmitter. The upper value corresponds to 200 °C and the lower value to -100 °C. This results in the following characteristic. In accordance with the set characteristic curve, the function calculates the sensor value from the measured current. The coefficients of the linear equation (gradient and foot point) are calculated from the set threshold and the sensor values are determined. A supplied current of 9.333 mA corresponds to a temperature of 0 °C.

NOTE
The hardware of the measuring transducer has been designed in such a way that measured values are transmitted and analyzed using the setting range (Upper limit orLower limit). Therefore, special applications are possible, if necessary. The limits are at approx. +20 mA and -20 mA or +10 V and -10 V.

Setting Example 2:
For special applications, the transmitter sends a maximum of ±12 V. This voltage shall be issued accordingly as sensor voltage.

Set the parameters as follows:

• Upper limit = 10.00 V
• Upper limit – Sensor = 10.00 V
• Lower limit = -10.00 V
• Lower limit – Sensor = -10.00 V
  With this setting, a signal of 12 V is issued as a 12-V measured value (see following figure).

5.2.6.5 Settings

MT fast #
:101| MT in #:TD input-signal type| | • Voltage input
• Current input| Current input
:103| MT in #:Unit| | • %
• °
• °C
• °F
• Ω
• Ω/km
• Ω/mi
• 1/s
• A
• As
• cos φ
• cycles
• dB
• F/km
• F/mi
• h
• Hz
• Hz/s
• in
• J
• J/Wh
• K
• l/s
• m
• mi
• min
• p.u.
• Pa
• periods
• rad
• rad/s
• s
• V
• V/Hz
• VA
• VAh
• var
• varh
• Vs
• W
• W/s
• Wh| A
:142| MT in #:Measuring window| | • 10 ms
• 20 ms
• 40 ms
• 60 ms
• 80 ms
• 100 ms| 10 ms
:107| MT in #:Range active| | • 0
• 1| FALSE
:104| MT in #:Conversion factor| | -1000000.00 to 1000000.00| 1
:105| MT in #:Upper limit| | -20.00 m Ato 20.00 mA| 5.00 mA
:109| MT in #:Upper limit Sensor| | -1000000.00 to 1000000.00| 1
:106| MT in #:Lower limit| | -20.00 m Ato 20.00 mA| 4.00 mA
_:110| MT in #:Lower limit Sensor| | -1000000.00 to 1000000.00| 1

5.2.6.6 Information List

MT in #
:307| MT in #:Broken wire| SPS| O
:302| MT in #:TD scale MV| MV| O
_:306| MT in #:TD scale SAV| SAV| O

5.2.7 RTD Unit Ethernet
5.2.7.1 Overview

The RTD unit Ether. function:

• Communicates with an external RTD unit via the Slave Unit Protocol (SUP) and records the measured temperatures from the RTD unit
• Provides the captured temperatures to the temperature monitoring function
• Monitors communication with the RTD unit

5.2.7.2 Structure of the Function
The RTD unit Ether. function can only work in the Analog units function group. A maximum of 20 function instances can work simultaneously. Each instance contains 12 preconfigured sensor function blocks.

5.2.7.3 Communication with an RTD Unit Logic

Communication with an RTD Unit
The function is used to communicate with an RTD unit connected via an Ethernet connection. If the connection of the function is successfully established to the external RTD unit via the Ethernet interface, the RTD unit transmits the temperatures of all connected sensors to the RTD unit Ether. function. For the connection to be established successfully, specific communication settings must be set, see chapter 5.2.7.4 Application and Setting Notes.
The RTD unit Ziehl TR1200 IP supports only an Ethernet connection of 10 MBit/s. A direct connection to a 100-Mbit communication module is therefore not possible. For this reason, you must connect the RTD unit to the communication module via a 10/100 MBit/s autosensing switch which automatically recognizes the transmission rates and adapts them accordingly. Further information can be found in the Application and setting notes, see chapter 5.2.7.4 Application and Setting Notes.

Error Responses
The following table lists the conditions under which the Health status transitions to the Alarm or Warning state.
Table 5-4 Error Responses

The RTD unit Ether. function cannot establish a connection with a communication module.| Alarm
The connection between the communication module and the RTD unit causes a time-out.| Warning
A communication module has not received any more data from the RTD unit for 9 sec.| Warning

The Failure signal is issued as soon as one of the sensor function blocks reports a failure.

5.2.7.4 Application and Setting Notes

Parameter: Port

• Default setting (_:2311:103) Port = port J Use the Port parameter to define over which port the external RTD unit is connected to the SIPROTEC 5 device.
  If you want to connect the external RTD unit to the integrated Ethernet interface, set the parameter Port = Port J. If you want to connect the external RTD unit to an Ethernet plug-in module, set the parameter Port = Port F, Port E, Port P, or Port N.
  You can connect directly the RTD unit to the device via the internal 10-Mbit Ethernet port J. If you operate the RTD unit on another port via a 100-Mbit communication module, you need an interconnected 10/100-Mbit autosensing switch, which adapts transmission rates accordingly.

Parameter: IP address

• Default setting (_:2311:104) IP address = 10.16.60.1
  With the parameter IP address, you set the IP address of the RTD unit connected to the communication module via the SUP protocol. Every RTD unit has to be assigned a unique IP address. The IP address to be set depends on your network configuration. You can set any valid IPv4 address that does not cause conflicts with other IP addresses in the network. Set an appropriate IP address first at the Ziehl TR1200 IP RTD unit. Then specify the parameter IP address for the communication module to the same address.

Settings on the RTD Unit
The Ziehl TR1200 IP RTD unit is set with the front keys or in a Web browser on a laptop computer via its Ethernet interface. Set the connection type of the sensors (3-wire connection or resistance value for 2-wire connection), the idle state of the fault-indication relay, as well as the IP interface setting.
The code lock has to be switched off for parameterization. This is only possible using the front keys of the RTD unit. The code lock is off (switched off) in as-delivered condition and has pin 504.
For detailed information on the settings, refer to the TR1200 IP manual that comes with the RTD unit. The documents are also available in the SIPROTEC download area (http://www.siprotec.de) under Accessories -> 7XV5662-xAD.
For an Ethernet connection to a SIPROTEC 5 device communicating with the RTD unit TR1200 IP via the SUP protocol (Slave Unit Protocol), the Modbus TCP setting must be activated in the RTD unit. You can activate the Modbus TCP protocol using the function keys under the tcP. → Mod / on menu item or with the Web browser in the TCP/UDP Config tab. The RTD (RTD protocol) and UDP Port settings have no effect here. The Modbus TCP port is permanently set to 502 and cannot be changed.

5.2.7.5 Temperature Sensor
Logic

Measured Temperature Value
The Temperature sensor function block processes one single measured temperature value delivered from the RTD unit for the assigned sensor. 12 temperature sensor function blocks are always available in each RTD unit function (both via Ethernet and serial), even if fewer sensors are connected to the RTD unit.
Various temperature sensor types are supported: Pt100, Ni100, and Ni120 sensors. The function block is notified regarding the selection of connected type via the Sensor type parameter.
The function block delivers a measured temperature value in °C or °F as an output variable. The measured temperature value is available as an operational measured value and can be monitored by the Temperature supervision function.

Error Responses
If the measured input value is determined to be incorrect, the quality attribute of the output measured temperature value is set to invalid. The statuses for Health and Error take the statuses in accordance with the following table:

Table 5-5 Error response

Measured temperature value outside the valid measuring range specified in the technical data. The valid measuring range depends on the sensor type.| Alarm| Yes
Sensor not connected| OK| No

5.2.7.6 Application and Setting Notes
Parameter: Sensor type
• Default setting (_:11611:102) Sensor type = Pt 100
The Sensor type parameter is used to set the sensor element used. You can select between Pt 100, Ni 100 and Ni 120.

Parameter: Temperature unit
To change the display and evaluation of measured temperature values from °C to °F, adapt the DIGSI user default settings accordingly.
Proceed as follows:

• In DIGSI select the menu item Extras –> Settings.
• In the Settings view select the menu item DIGSI 5 User preferences.
• Under Standard unit system change the setting value of the unit system used from SI units to US units.

The following settings and information table shows only 1 of the 12 sensors, as the setting possibilities of the 12 sensors do not differ.

5.2.7.7 Settings

General
:2311:103| General:Port| | • port E
• port F
• port J
• port N
• port P| port J
Sensor 1
:11611:102| Sensor 1:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100

5.2.7.8 Information List

General
:2311:53| General:Health| ENS| O
:2311:56| General:Failure| SPS| O
Sensor 1
:11611:52| Sensor 1:Health| ENS| O
:11611:60| Sensor 1:Failure| SPS| O
_:11611:80| Sensor 1:TmpOut| MV| O

5.2.8 RTD Unit, Serial
5.2.8.1 Overview
The RTD unit serial function:

• Communicates with an external RTD unit serial via the Slave Unit Protocol (SUP) and records the measured temperatures from the RTD unit
• Provides the captured temperatures to the temperature supervision function
• Monitors communication with the RTD unit

The RTD unit Serial function is set up structurally in the same manner as the RTD unit Ether. function. The mode of operation is also identical (see 5.2.7.3 Communication with an RTD Unit).

5.2.8.2 Application and Setting Notes
Parameter: Port
• Default setting (_:2311:103) Port = F
With the parameter Port, you set the slot for the communication module that will be used for the connection with an external RTD unit.
If you want to connect the external RTD unit to an Ethernet plug-in module, set the parameter Port = Port F , Port E, Port P, or plug-in module position.

Parameter: Channel number
• Default setting (_:2311:105) Channel number = 1
A serial communication module optionally uses 2 channels. With the parameter Channel number, you set the channel number (1 or 2) through which the RTD unit is connected to the device. The communication module inputs are labeled with the channel numbers.

Parameter: Slave address
• Default setting (_:2311:106) Slave address = 1
With the parameter Slave address, you define the device address of the RTD unit. If only one RTD unit is connected to the serial bus, the default value 1 can be used. The same device address has to be set on the RTD unit. The device address is important for distinguishing among several RTD units connected to a serial bus. Set a unique device address (for example 1, 2, and 3 when connecting 3 RTD units) for each RTD unit and the same device address for the parameter Slave address in the 3 RTD unit serial functions.
The following settings and information table shows only 1 of the 12 sensors, as the setting possibilities of the 12 sensors do not differ.

5.2.8.3 Parameter

General
:2311:103| General:Port| | • port F
• port E
• port P
• port N
• port J| port J
:2311:105| General:Channel number| | 1 to 2| 1
:2311:106| General:Slave address| | 1 to 254| 1
Sensor 1
:11611:102| Sensor 1:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 2
:11612:102| Sensor 2:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 3
:11613:102| Sensor 3:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 4
:11614:102| Sensor 4:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 5
:11615:102| Sensor 5:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 6
:11616:102| Sensor 6:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 7
:11617:102| Sensor 7:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 8
:11618:102| Sensor 8:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 9
:11619:102| Sensor 9:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 10
:11611:102| Sensor 10:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 11
:11611:102| Sensor 11:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100
Sensor 12
_:11611:102| Sensor 12:Sensor type| | • Pt 100
• Ni 100
• Ni 120| Pt 100

5.2.8.4 Information List

General
:2311:53| General:Health| ENS| O
:2311:56| General:Failure| SPS| O
Sensor 1
:11611:52| Sensor 1:Health| ENS| O
:11611:60| Sensor 1:Failure| SPS| O
:11611:80| Sensor 1:TmpOut| MV| O
Sensor 2
:11612:52| Sensor 2:Health| ENS| O
:11612:60| Sensor 2:Failure| SPS| O
:11612:80| Sensor 2:TmpOut| MV| O
Sensor 3
:11613:52| Sensor 3:Health| ENS| O
:11613:60| Sensor 3:Failure| SPS| O
:11613:80| Sensor 3:TmpOut| MV| O
Sensor 4
:11614:52| Sensor 4:Health| ENS| O
:11614:60| Sensor 4:Failure| SPS| O
:11614:80| Sensor 4:TmpOut| MV| O
Sensor 5| | |
:11615:52| Sensor 5:Health| ENS| O
:11615:60| Sensor 5:Failure| SPS| O
:11615:80| Sensor 5:TmpOut| MV| O
Sensor 6| | |
:11616:52| Sensor 6:Health| ENS| O
:11616:60| Sensor 6:Failure| SPS| O
:11616:80| Sensor 6:TmpOut| MV| O
Sensor 7| | |
:11617:52| Sensor 7:Health| ENS| O
:11617:60| Sensor 7:Failure| SPS| O
:11617:80| Sensor 7:TmpOut| MV| O
Sensor 8| | |
:11618:52| Sensor 8:Health| ENS| O
:11618:60| Sensor 8:Failure| SPS| O
:11618:80| Sensor 8:TmpOut| MV| O
Sensor 9| | |
:11619:52| Sensor 9:Health| ENS| O
:11619:60| Sensor 9:Failure| SPS| O
:11619:80| Sensor 9:TmpOut| MV| O
Sensor 10| | |
:11611:52| Sensor 10:Health| ENS| O
:11611:60| Sensor 10:Failure| SPS| O
:11611:80| Sensor 10:TmpOut| MV| O
Sensor 11| | |
:11611:52| Sensor 11:Health| ENS| O
:11611:60| Sensor 11:Failure| SPS| O
:11611:80| Sensor 11:TmpOut| MV| O
Sensor 12| | |
:11611:52| Sensor 12:Health| ENS| O
:11611:60| Sensor 12:Failure| SPS| O
:11611:80| Sensor 12:TmpOut| MV| O

5.2.9 Communication with RTD Unit
5.2.9.1 Integration of a Serial RTD Unit (Ziehl TR1200)
Connection of the Communication Lines
Figure 5-35 shows how you connect the RTD unit to the SIPROTEC 5 device. Note that Pin 1 of the RJ45 plug is connected to RTD-B and Pin 2 is connected to RTD-A.

Figure 5-35 Connection of the RTD Unit to the SIPROTEC 5 Device

Adding a USART Module
Add a USART-AB-1EL or a USART-AC-2EL USART module in DIGSI to the device. The USART module must be inserted at one of the plug-in positions for communication modules in the base module or in the CB202 expansion module (refer to the following figure).

Figure 5-36 Insertion Position for a USART Module

Selecting the SUP Protocol
Select the Slave Unit Protocol (SUP). This protocol is responsible for the communication between the SIPROTEC 5 device and the RTD Unit.

Figure 5-37 Selecting the SUP Protocol

Communication Settings
Make the communications settings for the relevant serial channels. For this, use the default settings specified by the RTD box. Normally, you must adapt only the parameterization of the SIPROTEC 5 device to the settings of the RTD box. Make sure that the setting values in both devices are the same. The setting of the parameter Non-flickering light (on/off): is not relevant for the RS485 interface.

NOTE
The driver for the USART module for the SUP protocol is not preinstalled as standard for the initial use of this interface (following the firmware update).

Figure 5-38 Making the Communication Settings

With the selection of the SUP protocol for the RTD box DIGSI automatically adds the function group Analog units to your device configuration. You can now instantiate the function RTD unit serial 1 (refer to the following figure).

Figure 5-39 Analog-Unit Instance

Now, set the channel number over which the SUP protocol runs. In addition, set the slave address of the RTD unit. This address must be set with the same value in the RTD box (refer to the following figure).
The following device configuration must be set on the TR1200 RTD unit when the RTD unit is used for the first time:

• Bus protocol: mod
• Device address: 1
• Baud rate: 9600
• Parity: no

Figure 5-40 Setting the Port, Channel Number, and Slave Address

Finally, load the configuration in the device.
5.2.9.2 Integration of an RTD Unit Ether. (TR1200 IP)
Device Configuration
In the DIGSI, insert an Ethernet module into the provided slot, thus adding the module to the device configuration.
Figure 5-41 displays the available slots in the base module or on the expansion module CB202.
Alternatively, you can also use the integrated Ethernet interface port J.

Figure 5-41 Inserting an Ethernet Module

Communication Settings
Activate the SUP Ethernet protocol for the Ethernet module.

Figure 5-42 SUP Ethernet Protocol Activation

This protocol is also available for Port J of the integrated Ethernet interface of the base module (refer to following figure).

Figure 5-43 SUP Ethernet Protocol Activation (Base Module)

With the selection of the SUP protocol for the RTD unit, DIGSI automatically adds the Analog units function group and the RTD unit Ether. function to your device configuration (refer to the following figure).

Figure 5-44 Analog Unit Instance

Now, set the port over which the SUP protocol runs. In addition, set the IP address of the RTD unit (refer to the following figure). This address must be set with the same value in the RTD unit.

Figure 5-45 Setting the Port and IP Address

Finally, load the configuration in the device.

5.2.9.3 Temperature Simulation without Sensors
Connect a resistor on the sensor terminals of the RTD unit. Using this resistor, simulate a constant temperature. The resistance value should be around 50 Ω to 200 Ω.
If you want to simulate a changeable temperature, connect an adjustable resistor of maximum 470 Ω instead of a fixed resistor.

5.2.10 Temperature Acquisition via Protocols
5.2.10.1 Overview
The function Temperature acquisition via protocols:

• Obtains the temperature from a power-plant control system or from another protection device
• Processes the temperature, for example, supervises the temperature in the CFC
• Transfers the temperature to other protection devices

5.2.10.2 Structure of the Function
The function Temperature acquisition via protocols can work only in the function group Analog units. In this function, the following stages can operate simultaneously:

• 12 stages Temperature acquisition via PROFINET IO or IEC 61850
  The stage can obtain the temperature from a power‑plant control system via the PROFINET IO protocol or the IEC 61850 protocol.

• 12 stages Temperature acquisition via GOOSE
  The stage can obtain the temperature from another SIPROTEC 5 protection device via the GOOSE protocol.

The function Temperature acquisition via protocols comes factory‑set with 1 stage Temperature acquisition via PROFINET IO or IEC 61850.

Figure 5-46 Structure/Embedding of the Function

5.2.10.3 Stage Temperature Acquisition via PROFINET IO or IEC 61850
Logic

Figure 5-47 Logic Diagram of the Stage

The stage Temperature acquisition via PROFINET IO or IEC 61850 supports 2 protocols:

• PROFINET IO protocol
  If you set the PROFINET IO protocol for the temperature acquisition, you can only get the analog value.

• IEC 61850 protocol
  If you set the IEC 61850 protocol for the temperature acquisition, you get the analog value, the quality, and the time stamp.

Invalid Temperature Indication
If the received temperature is invalid, the failure indication Temperature failure is issued.

Stage Application
You can use the stage Temperature acquisition via PROFINET IO or IEC 61850 for the following purposes:

• Acquire the cold‑gas temperature from the power‑plant control system
• Process the received cold‑gas temperature value
• Send the processed cold‑gas temperature value to other functions for further processing

Figure 5-48 Application Example

The following table explains the data.

protocol for the temperature acquisition.
In the stage Temperature acquisition via PROFINET IO or IEC 61850, the data type is APC.
Unit| With this parameter, you can select the unit °F or °C for the temperature which is acquired from the power‑plant control system.

5.2.10.4 Stage Temperature Acquisition via GOOSE
Logic

Figure 5-49 Logic Diagram of the Stage

Invalid Temperature Indication
If the received temperature is invalid, the failure indication Temperature failure is issued.

Stage Application
The following terms are used for the stage Temperature acquisition via GOOSE:

• Source device
  SIPROTEC 5 protection device that provides data

• Target device
  SIPROTEC 5 protection device that requests data from the source device In the target device, you can use the stage Temperature acquisition via GOOSE for the following purposes:

• Acquire the cold‑gas temperature from the source device

• Process the received cold‑gas temperature value

• Send the processed cold‑gas temperature value to other functions for further processing

In the following figure, the source device is SIPROTEC 5 device 2 and the target device is SIPROTEC 5 device 1.

Figure 5-50 Application Example

The following table explains the data.

acquisition. In the stage Temperature acquisition via GOOSE, the input measured value with a COM template is designed to acquire the data from another SIPROTEC 5 protection device.
Unit| With this parameter, you can select the unit °F or °C for the temperature which is acquired from another SIPROTEC 5 protection device.

5.2.10.5 Application and Setting Notes
Change of the Temperature Unit
Commonly, the temperature unit °C is used in the display and evaluation of measured temperature values.

• To change the temperature unit from °C to °F for all devices in the current DIGSI project, proceed as follows:
  – In DIGSI, select the menu item Options > Settings.
  – In the Settings view, select the menu item DIGSI 5 user preferences.
  – Set the parameter Standard unit system to US units.
  Figure 5-51 Change of the Temperature Unit between °C and °F for all Devices

• To change the temperature unit from °C to °F for 1 device, proceed as follows:
  – In the project tree, navigate to your device and select Settings > Device settings.
  – In the Device settings view, navigate to the menu item Localization.
  – Set the parameter Unit system to ANSI.
  Figure 5-52 Change of the Temperature Unit between °C and °F for 1 Device

NOTE
If the parameter Unit system is set to ANSI, only the unit of the measuring values and parameters changes to °F.
The unit of the following data is still °C:

• Other temperature data in the device
• The temperature thresholds in DCF

Parameter: Unit
• Default setting (_:19801:101) Unit = °C
You use the setting Unit to specify which physical unit of the source data the measured values represent. The possible setting values are listed in the settings table.

5.2.10.6 Settings

Tmp.Ctl 1
_:19801:101| Tmp.Ctl 1:Unit| | • °C
• °F| °C

5.2.10.7 Information List

Control Functions

6.1 Introduction
6.1.1 Overview
The SIPROTEC 5 series of devices offers powerful command processing capability as well as additional functions that are needed when serving as bay controllers for the substation automation technology or when providing combi- protection. The object model for the devices is based on the IEC 61850 standard, making the SIPROTEC 5 series of devices ideally suited for use in systems employing the IEC 61850 communication protocol. In view of the function blocks necessary for the control functions, other logs are also used.

6.1.2 Concept of Controllables
The concept of so-called controllables is based on the data model described in IEC 61850. Controllables are objects that can be controlled, such as a switch with feedback. The model of a transformer tap changer, for example, contains controllables. The controllables are identifiable by their last letter C of the data type (for example, DPC = Double Point Controllable/Double Command with feedback or BSC = Binary-Controlled Step Position Indication / transformer tap command with feedback).

(1) Position (connect with binary inputs)
(2) Signalization of the current condition
(3) Command output (connect with relay)
The trip, opening, and the close commands are connected to the relays. For the trip command, a choice between saved and unsaved output is possible. The position is connected with 2 binary inputs (double-point indication). In addition, signals are available that display the current state of the switch (not selected, off, on, intermediate position, disturbed position). These signals can be queried in CFC, for example, in order to build interlocking conditions.

Control Models
You can set the operating mode of the controllables by selecting the control model.
4 different control models are available:

• Direct without feedback monitoring (direct w. normal secur.)
• With reservation (SBO) 14 without feedback monitoring (SBO w. normal secur.)
• Direct with feedback monitoring (direct w. enh. security)
• With SBO with feedback monitoring (SBO w. enh. security)

The next figure shows the command sources, command types, and control models.

Figure 6-1 Command Sources, Command Types, and Control Models

The figure shows the control models (right) with the respective control mechanisms (center). The standard control model for a switching command in an IEC 61850 compliant system is SBO with feedback monitoring ( SBO w. enh. security). This control model is the default setting for newly created switching devices.

6.2 Switching Devices
6.2.1 General Overview
You can find the following switching devices in the DIGSI 5 library in the function groups Circuit breaker and Switching devices (see following figures).

Figure 6-2 Selecting the Remaining Switching Devices Using the DIGSI Switching-Devices Menu

6.2.2 Switching Device Circuit Breaker
6.2.2.1 Structure of the Circuit-Breaker Switching Device
This chapter describes the control properties of the Circuit-breaker switching device.
The Circuit-breaker switching device contains the following function blocks that are needed for control:

• Function block Circuit breaker
• Function block Control
• Function block Interlocking

This corresponds to the logical nodes XCBR, CSWI, and CILO in IEC 61850.

Figure 6-3 Control Function Blocks of the Circuit-Breaker Switching Device

The circuit breaker in DIGSI 5 is linked with the binary inputs that acquire the switch position via information routing. The circuit breaker in DIGSI 5 is also linked with the binary outputs that issue the switching commands. The Circuit-breaker switching device is available in the DIGSI 5 library in 2 different variants:

• Circuit-breaker control
  This switching device contains the function blocks Control, Interlocking, and Circuit breaker needed for control. The standard situation for the control function is that the SIPROTEC 5 device switches all 3 poles of the circuit breaker On or Off together.

• Circuit breaker [status only] This switching device contains only the function block Circuit breaker. It is used to acquire the position of a switch, for example, from a neighboring bay. This object type can be used to model switches that can only be read but not controlled by the SIPROTEC 5 device.

Function Blocks of the Circuit Breaker
Table 6-1 Function Blocks of the Circuit-Breaker Function Group

switch position from the positions of the binary inputs and also outputs the command via the binary outputs.
Control| Command processing| Control model SBO time-out
Feedback monitoring time Check switching authority Check if pos. is reached Check double activat. blk. Check blk. by protection| Command check, communication with the command source and with the function block Circuit breaker
Inter- locking| Switchgear interlocking protection| Interlocking condition (depos- ited in CFC)| The functionality Interlocking generates the releases
for switchgear interlocking protection.

For the setting values of the parameter, refer to 6.2.2.2 Application and Setting Notes.

Additional Setting Options of the Circuit-Breaker Switching Element
The setting options of the circuit breaker are assigned to the function blocks on the basis of their relevance.
Additional setting options of the circuit breakers that cannot be directly assigned to one of the 3 function blocks are nevertheless available:
Table 6-2 Setting Options of the Controllable Cmd. with feedback in the Function Block Control of the Circuit Breaker.

Position of the function block Control 15
Retrigger filter (yes/no)| Switching retriggering of the filtering time on/off by changing the position| Position of the function block Control 15
Message time before
filtering (yes/no)| Consideration of the hardware filtering time for position- detection time stamp| Position of the function block Control 15
Suppress intermediate position (yes/no)| When activated, only the intermediate position is
suppressed by the duration of the software filtering
time.| Position of the function block Control 15

15 First click Position and then click the Details key in the Properties window (below).

Treatment of spontaneous position changes (Gen. Software Filt./Spont. Software Filt.)| If you select the General software filter setting, the general settings for software filtering of spontaneous position changes and for position changes caused by
a switching command apply. By selecting Spontaneous
software filter, a separate filtering is activated for spontaneous position changes.| Position of the function block Control 15
Spontaneous software filtering time| Software filtering time for spontaneous position
changes| Position of the function block Control 15
Spontaneous retrigger filter (yes/no)| Switching on/off retriggering of the filtering time by spontaneous position change| Position of the function block Control 15
Spontaneous indication timestamp before filtering (yes/no)| Consideration of the hardware filtering time for position-detection time stamp in case of a spontaneous change| Position of the function block Control 15
Inhibit intermediate position for a
spontaneous chng. (yes/no)| When activated, only the spontaneous change to the
intermediate position is suppressed by the duration of the software filtering time.| Position of the function block Control 15

Table 6-3
Setting Options of the Controllable Position in the Circuit-Breaker Function Block (Chatter Blocking)

function block Circuit breaker 15

Table 6-4 Additional Settings in the Device Settings Having Effects on the Circuit Breaker

Chatter test time
Number of chatter tests
Chatter idle time
Chatter check time

The inputs and outputs as well as the setting options of the function blocks Circuit breaker and Control are described in the next section (refer to 6.2.2.3 Connection Variants of the Circuit Breaker).

Interlocking
The function block Interlocking generates the releases for switchgear interlocking protection. The actual interlocking conditions are deposited in CFC. For more information on this, refer to the general chapter 6.3.1 Command Checks and Switchgear Interlocking Protection.

6.2.2.2 Application and Setting Notes
Circuit Breaker
The Circuit-breaker function block in the SIPROTEC 5 device represents the physical switch device. The task of the circuit breaker is to replicate the switch position from the status of the binary inputs.

The following figure shows the logical inputs and outputs of the Circuit- breaker function block.

Figure 6-4
Logical Inputs and Outputs of the Circuit-Breaker Function Blocks
Table 6-5 and Table 6-6 list the inputs and outputs with a description of their function and type. For inputs, the effect of Quality = invalid on the value of the signal is described.

EXAMPLE
If the signal >Ready has the Quality = invalid, then the value is set to cleared. In problematic operating states, the circuit breaker should signal that it is not ready for an Off-On-Off cycle. Table 6-5
Inputs of the Circuit-Breaker Function Block

Signal Name| Description| Type| Default Value if Signal Quality = invalid
---|---|---|---

Ready| The signal >Ready indicates that the OFF-ON-OFF
cycle is possible with the circuit breaker.
This signal is used for the AREC standby status.| SPS| Going
Acquisition blocking| The binary input activates acquisition blocking. You
can also set this binary input with an external toggle
switch.| SPS| Unchanged
Reset AcqBlk&Subst| Acquisition blocking and the substitution of the circuit
breaker are reset with this input. If the input is activated, setting the acquisition blocking and the substitution is
blocked.| SPS| Unchanged
Reset switch statist.| Among other things, the binary input sets the operation counter for the switch to the value 0.| SPS| Unchanged
External health| The binary input External health reflects the circuit-breaker status (EHealth). This input will be set by the CFC using the BUILD_ENS block. In turn, BUILD_ENS can query binary inputs that represent the conditions OK, Warning, or Alarm (as a result of the function Trip-circuit supervision).| ENS| Unchanged
Position| The signal Position can be used to read the circuitbreaker position with double-point indication.| DPC| Unchanged

If the quality of the input signal assumes the status Quality = invalid, then the standby status (EHealth) of the Circuit-breaker function block is set to Warning.
Table 6-6 Outputs of the Circuit-Breaker Function Block

suppressed during the runtime of automatic reclosing (optional) as well as during the command output of switching commands.| SPS
Op. ct.| The information counts the number of switching cycles of the circuit breaker.| INS
Trip/open cmd.| This logic output is responsible for the command output Off.| SPS
Close command| This logic output is responsible for the command output On.| SPS
Command active| The binary output Command active is responsible for signaling a running command (relay active or selected switching device (SEL)).| SPS
CB open hours| The statistical value counts the hours the circuit breaker is open.| INS
Operating hours| The statistical value counts the hours where at least one phase current is greater than the Current thresh. CB open parameter.| INS

Control
It is the task of the controls to execute command checks and establish communication between the command source and the circuit breaker. Using the control settings, you specify how the commands are to be processed (see also chapter 6.3.1 Command Checks and Switchgear Interlocking Protection).
Through the function SBO (Select Before Operate, reservation 16 ), the switching device is reserved prior to the actual switching operation, thus it remains locked for additional commands. Feedback monitoring provides information about the initiator of the command while the command is in process, that means, informing whether or not the command was implemented successfully. These 2 options can be selected individually in the selection of the control model, so that 4 combinations in total are available (see the following table).
The control makes the following settings available (see next table).

SBO w. normal secur.
direct w. enh. security
SBO w. enh. security
(_:4201:102) SBO time-out| 30.00 s| 0.01 s to 1800 s
(Increment: 0.01 s)

16 In the IEC 61850 standard, reservation is described as Select before Operate (SBO).
17 This default setting is the standard control model for a switching command in an IEC 61850-compliant system.

0.01 s)
(:4201:104) Check switching authority| yes| no
yes
advanced
(:4201:105) Check if pos. is reached| yes| no
yes
(:4201:106) Check double activat. blk.| yes| no
yes
(:4201:107) Check blk. by protection| yes| no
yes

The following figure shows the logical inputs and outputs of the Control function block.

Figure 6-5 Logical Inputs and Outputs of the Control Function Block
Table 6-7 Control Function Block Input and Output

Signal Name| Description| Type| Value if Signal
Quality=Invalid
---|---|---|---
Cmd. with
feedback| With the Cmd. with feedback signal, the circuitbreaker position is accepted via the double-point indication of the Circuit-breaker function block and
the command is issued.| Controllable
(DPC)
Unchanged| Unchanged

In the information routing of DIGSI 5, you may select a function key as a possible command source. In addition, it is displayed here if the command is activated by CFC. The logging is routed here.

6.2.2.3 Connection Variants of the Circuit Breaker

For each switching device, you can establish the number of poles (for example, 1-pole, 1.5-pole or 2-pole) that are switched with or without feedback. This results in the necessary amount of information to be processed, thus establishing the command type.
Whether the circuit breaker is triggered 1-, 1.5-, or 2-pole, depends on the design of the auxiliary and control-voltage system. In most cases, the activation of the opening coil of the circuit breaker is 1-pole.

Table 6-8 Meaning of the Abbreviations of the Connection Variants

Table 6-9 Meaning of the Abbreviations in DIGSI

Click the right mouse button and enter V.
X| Close Command
Click the right mouse button and enter X for the respective binary output.
OH| The switching-device feedback is in the position OFF, if there is voltage present at the
routed binary input (H).
Click the right mouse button and enter OH.
OL| The switching-device feedback is in the position OFF, if there is no voltage present at
the routed binary input (L).
Click the right mouse button and enter OL.
CH| The switching-device feedback is in the position ON, if there is voltage present at the
routed binary input (H).
Click the right mouse button and enter CH.
CL| The switching-device feedback is in the position ON, if there is no voltage present at
the routed binary input (H).
Click the right mouse button and enter CL.
TL| Trip command stored
Click the right mouse button and enter TL.

Connection Variant: 3-Pole Circuit Breaker
This is the standard type for the control function. All 3 individual poles of the circuit breaker are triggered together by a double command.

Figure 6-6 3-Pole Circuit Breaker
1-Pole Triggering

Figure 6-7 1-Pole Triggering

Figure 6-8 1-Pole Triggering, Routing in DIGSI
You can select the contacts for On and Off as desired. They need not necessarily be next to one another. The letter U represents an unlatched command. Alternatively, TL (latched tripping) can be selected.

1.5-Pole Triggering

Figure 6-9 1.5-Pole Triggering

Figure 6-10 1.5-Pole Triggering, Routing in DIGSI

2-Pole Triggering

Figure 6-11 2-Pole Triggering

Figure 6-12 2-Pole Triggering, Routing in DIGSI

Connection Variant: 1-Pole Circuit Breaker
The 1-pole circuit breaker is used for separate activation and acquisition of the individual poles of a circuit breaker. It is intended for joint use by 1-pole protection and control functions.
NOTE The wiring of the Circuit-breaker function group with binary inputs and binary outputs occurs 1 time per device.
The control function in this type switches all 3 poles on or off simultaneously.
The protection functions can switch off 1-pole. The close command is always 3-pole. Optionally only the open poles are closed.

Figure 6-13 Circuit Breaker with 1-Pole Triggering
For the circuit breaker with 1-pole triggering, triggering takes place via one relay per phase for the trip command and via a 4th relay for the close command (see next figure).

Figure 6-14 1-Pole Connection of a Circuit Breaker

Figure 6-15 Routing in DIGSI
In the previous figure, the switch is connected 1-pole. The protection trip command is routed individually for the 3 phases (Trip only pole A to Trip only pole C). The protection trip command is routed for the 3 phases ( Trip/open cmd. 3-pole). The control always switches off the 3 poles of the switch. In addition, the 3 U (Unlatched) routings of the trip command and open command are set to 3-pole. This routing is also used by protection functions that trip 3 poles. The close command is issued simultaneously for all 3 phases.
Example: Trip Command during Transition from 1-Pole to 3-Pole
During a transition from 1-pole to 3-pole tripping Trip only pole A remains active. When, for example informing an external AREC whether it is a 1-pole or 3-pole tripping, you can use the indication Trip logic:Trip indication:1-pole and Trip logic:Trip indication:3-pole.

Acquisition of the Circuit-Breaker Position
The binary inputs for feedback of the switch position are routed as shown in the previous figure (see also see
5.1.2.3 Acquisition of Circuit-Breaker Auxiliary Contacts and Further Information ).

Figure 6-16 Routing of the 1-Pole in DIGSI

You can find the meaning of abbreviations in Table 6-8 and Table 6-9.
The indication Command active can also be routed to a binary output. This binary output is always active if either a close or trip command is pending, or the switching device was selected by the command control.

6.2.2.4 Settings

Ref. for %-values
:2311:101| General: Rated normal current| | 0.20 A to 100000.00 A| 1000.00 A
:2311:102| General: Rated voltage| | 0.10 kV to 1200.00 kV| 400.00 kV
Breaker settings
:2311:112| General: Current thresh. CB open| 1 A @ 100 !rated| 0.030 A to 10.000 A| 0.100 A
5 A @ 100 !rated| 0.15 A to 50.00 A| 0.50 A
1 A @ 50 [rated| 0.030 A to 10.000 A| 0.100 A
5A @50 [rated| 0.15 A to 50.00 A| 0.50 A
1 A @ 1.6 lrated| 0.001 A to 1.600 A| 0.100 A
5 A @ 1.6 Irated| 0.005 A to 8.000 A| 0.500 A
:2311:136| General: Op. mode BFP| | • unbalancing
• 1> query| unbalancing
5341:103| Trip logic: Reset of trip command| | • with 1<
• with 1< & aux.contact
• with dropout| with l<
Circuit break.
:4261:101| Circuit break.: Output time| | 0.02 s to 1800.00 s| 0.10 s
:4261:105| Circuit break.: Indicat. of breaking values| | • with trip
• always| always
Manual close
:6541:101| Manual close: Action time| | 0.01 s to 60.00 s| 0.30 s
s6541:102| Manual close: CB open dropout delay| | 0.00 s to 60.00 s| 0.00 s
Control
:4201:101| Control: Control model| | • status only
• direct w. normal secur.
• SBO w. normal secur.
• direct w. enh. security
• SBO w. enh. security| SBO w. enh. security
s4201:102| Control: SBO time- out| | 0.01 s to 1800.00 s| 30.00 s
:4201:103| Control: Feedback monitoring time| | 0.01 s to 1800.00 s| 1.00 s
:4201:104| Control: Check switching authority| | • no
• yes
• advanced| yes
:4201 :105| Control: Check if pos. is reached| | • no
• yes| yes
:4201:106| Control: Check double activat. blk.| | • no
• yes| yes
:4201:107| Control: Check blk. by protection| | • no
• yes| yes
Switching authority
:4201:151| Control: Swi.dev.
related sw.auth.| | • 0
• 1| false
:4201:152| Control: Specific sw. authorities| | • 0
• 1| true
:4201:115| Control: Specific sw.auth. valid for| | • station
• station/remote
• remote| station/remote
:4201:153| Control: Num. of specific sw.auth.| | 2 to 5| 2
:4201:155| Control: ldent. sw.auth. 1| | Freely editable text|
:4201 :156| Control: Ident. sw.auth. 2| | Freely editable text|
:4201:157| Control: Ident. sw.auth. 3| | Freely editable text|
:4201:158| Control: Ident. sw.auth. 4| | Freely editable text|
:4201:159| Control: Ident. sw.auth. 5| | Freely editable text|
:4201:154| Control: Multiple
specific sw.auth.| | • 0
• 1| false
CB test
:6151:101| CB test: Dead time| | 0.00 s to 60.00 s| 0.10 s
:6151:102| CB test: Trip only| | • 0| false
| | | • 1|
:6151:103| CB test: Consider current criterion| | • 0
• 1| false
:6151:104| CB test: Current threshold| 1 A @ 100 !rated| 0.030 A to 10.000 A| 0.100 A
5 A @ 100 !rated| 0.15 A to 50.00 A| 0.50 A
1 A @ 50 Irated| 0.030 A to 10.000 A| 0.100 A
5 A @ 50 Irated| 0.15 A to 50.00 A| 0.50 A
1 A @ 1.6 Irated| 0.001 A to 1.600 A| 0.100 A
5 A @ 1.6 Irated| 0.005 A to 8.000 A| 0.500 A

6.2.2.5 Information List

Trip logic
:5341 :300| Trip Iogic:Trip indication| ACT| O
Circuit break.
:4261:500| Circuit break.:>Ready| PLC| I
:4261:501| Circuit break.:>Acquisition blocking| PLC| I
:4261:502| Circuit break.:>Reset switch statist.| PLC| I
:4261:504| Circuit break.:>Reset AcqBIk&Subst| PLC| I
:4261:503| Circuit break.:External health| ENS| I
:4261:53| Circuit break.:Health| ENS| O
:4261:58| Circuit break.:Position 3-pole| DPC| C
:4261:300| Circuit break.:Triplopen cmd. 3-pole| PLC| O
:4261:301| Circuit break.:Close command| PLC| O
:4261:302| Circuit break.:Command active| PLC| O
:4261:303| Circuit break.:Definitive trip| PLC| O
:4261:304| Circuit break.:Alarm suppression| PLC| O
:4261:306| Circuit break.:Op.ct.| INS| O
:4261:307| Circuit break.:El Brk.| BCR| O
:4261:308| Circuit break.:IIA Brk.| BCR| O
:4261:309| Circuit break.:XIB Brk.| BCR| O
:4261:310| Circuit break.:XIC Brk.| BCR| O
:4261 :311| Circuit break.:Break.-current phs A| MV| O
:4261:312| Circuit break.:Break.-current phs B| MV| O
:4261:313| Circuit break.:Break.-current phs C| MV| O
:4261:317| Circuit break.:Break. current 3I0/IN| MV| O
:4261:314| Circuit break.:Break. voltage phs A| MV| O
:4261:315| Circuit break.:Break. voltage phs B| MV| O
:4261:316| Circuit break.:Break. voltage phs C| MV| O
:4261:322| Circuit break.:CB open hours| INS| O
:4261:323| Circuit break.:Operating hours| INS| O
Manual close
:6541:501| Manual close:>Block manual close| PLC| I
:6541:500| Manual close:>Input| PLC| I
:6541:300| Manual close:Detected| PLC| O
Reset LED Group
:13381:500| Reset LED Group:>LED reset| PLC| I
:13381:320| Reset LED Group:LED have been reset| PLC| O
Control
:4201:503| Control:>Sw. authority local| PLC| I
:4201:504| Control:>Sw. authority remote| PLC| I
:4201:505| Control:>Sw. mode interlocked| PLC| I
:4201:506| Control:>Sw. mode non-interl.| PLC| I
:4201:53| Control:Health| ENS| O
:4201:58| Control:Cmd. with feedback| DPC| C
:4201:302| Control:Switching auth. station| SPC| C
:4201:308| Control:Enable sw. auth. 1| SPC| C
:4201:309| Control:Enable sw. auth. 2| SPC| C
:4201:310| Control:Enable sw. auth. 3| SPC| C
:4201:311| Control:Enable sw. auth. 4| SPC| C
:4201:312| Control:Enable sw. auth. 5| SPC| C
:4201:313| Control:Switching authority| ENS| O
:4201:314| Control:Switching mode| ENS| O
Interlocking
:4231:500| Interlocking:>Enable opening| PLC| I
:4231:501| Interlocking:>Enable closing| PLC| I
:4231:502| Interlocking:>Enable opening(fixed)| PLC| I
:4231:503| Interlocking:>Enable closing (fixed)| PLC| I
:4231:53| Interlocking:Health| ENS| O
CB test
:6151:53| CB test:Health| ENS| O
:6151:301| CB test:Test execution| ENS| O
:6151:302| CB test:Trip command issued| ENS| O
:6151:303| CB test:Close command issued| ENS| O
:6151:304| CB test:Test canceled| ENS| O
_:6151:311| CB test:3-pole open-close| SPC| C

6.2.3 Disconnector Switching Device
6.2.3.1 Structure of the Disconnector Switching Device
Like the circuit breaker, the Disconnector switching device contains the following 3 function blocks:

• Function block Disconnector
• Function block Control
• Function block Interlocking
  This corresponds to the logical nodes XSWI, CSWI, and CILO in IEC 61850.

NOTE
In contrast to the Circuit-breaker switching device, the Disconnector switching device cannot contain any additional functions because protection functions or synchronization can have no effect on the disconnector.
The following figure shows the structure of the Disconnector switching element:

The Disconnector switching device behaves like the Circuit-breaker switching device. The only difference is the designation of the function block that the physical switch provides (disconnector instead of circuit breaker). Blocking by protection is not provided in the analysis of the Control function block.
The Disconnector switching device is available in the DIGSI 5 library in 2 different variants:

• Disconnector with 3-pole connection
  The device switches all 3 poles of the disconnector on or off simultaneously.

• Disconnector without triggering (only status detection, no control)
  This variant is rarely encountered. It is encountered with grounding switches that frequently cannot be controlled, but only provide their current position. In addition, the position of a disconnector in a neighboring bay can be acquired.

Function Blocks of the Disconnector
Table 6-10 Function Blocks of the Disconnector Function Group

Function
Block| Description| Parameter| Function
---|---|---|---
Discon- nector| The disconnecter represents the physical switch in the SIPROTEC 5 device.| Maximum output time Seal-in time Switching-device type| The disconnecter replicates the switch position from the status of the binary inputs and also transmits the command via the binary outputs.
Control| Command processing| Control model SBO time-out
Feedback monitoring time Check switching authority Check if pos. is reached Check double activat. blk.| Command checks. commu- nication with the command source and with the tune- tion block Disconnecter
Inter- locking| Switchgear interlocking protection| Interlocking condition (deposited in CFC)| The Interlocking function- ality generates the releases for switchgear interlocking protection.

You can find the setting values of the parameter in 6.2.3.2 Application and Setting Notes.

Additional Settings of Disconnector Switching Element
The settings of the disconnector are assigned to the function blocks on the basis of their relevance. Additional disconnector settings that cannot be directly assigned to one of the 3 function blocks and are identical to the circuit-breaker settings are available:

Table 6-11
Setting Options of the Controllable Command with Feedback in the Control Function
Block of the Circuit Breaker

Position of the Control(1) function block
Retrigger filter (yes/no)| Switching retriggering of the filtering time on/off by changing the position| Position of the Control (1) function block
Message time before
filtering (yes/no)| Consideration of the hardware filtering time for position- detection
time stamp| Position of the Control(1) function block
Suppress intermediate
position (yes/no)| When activated, only the intermediate position is suppressed by the duration of the software filtering time.| Position of the Control(1) function block
Spontaneous position changes filtered by (Gen.Software Filt./Spont. Software Filt.)| If the General software filter setting is selected, the general settings for software filtering of spontaneous position changes and for position changes caused by a switching command apply. By selecting Spontaneous software filter, a separate filtering is activated for  spontaneous position changes.| Position of the Control(1) function block
Spontaneous software filter time| Software filtering time for spontaneous position changes| Position of the Control(1) function block
Spontaneous retrigger
filter (yes/no)| Switching on/off retriggering of the filtering time by spontaneous position change| Position of the Control(1) function block
Spontaneous indication timestamp before filtering
(yes/no)| Consideration of the hardware filtering time for position-detection
time stamp in case of a spontaneous change| Position of the Control (1) function block
Spontaneous suppress intermediate position (yes/no)| When activated, only the spontaneous change to the intermediate
position is suppressed by the duration of the software filtering
time.| Position of the Control(1) function block

(1) First click Position and then click the Details button in the Properties window (below).
Table 6-12
Setting Options of the Controllable Position in the Disconnector Function Block (Chatter Blocking)

Disconnector (1) function block

(1) First click Position and then click the Details button in the Properties window (below).
Table 6-13
Additional Settings in the Device Settings with Effects on the Disconnector

Chatter test time
Number of chatter tests
Chatter dead time
Chatter test time

The inputs and outputs as well as the setting options of the Disconnector switch function block are described in 6.2.3.3 Trigger Variants of the Disconnector. The Control function block is described identically as the Circuit-breaker function block, with the exception that the command check blocking is available through protection only with the circuit breaker.
You can find more information on this in 6.2.2.2 Application and Setting Notes.

Interlocking
The Interlocking function block generates the releases for switchgear interlocking protection. The actual interlocking conditions are deposited in CFC. For more information on this,  see the general chapter
6.3.1 Command Checks and Switchgear Interlocking Protection.
6.2.3.2 Application and Setting Notes
Disconnector
The disconnector represents the physical switch in the SIPROTEC 5 device. The task of the disconnector is to replicate the switch position from the status of the binary inputs.
The Disconnector function block is linked automatically via the information matrix with the binary inputs that register the switch position and with the binary outputs that issue the switching commands.
The Disconnector function block makes the following settings available (see next table).

(:5401:101) Maximum output time
The Maximum output time specifies the duration of the output pulse created by the switching command.| 10.00 s| 0.02 s to 1800 s
(Increment: 0.01 s)
(:5401:102) Seal-in time
If the target actuating position is not yet attained although feedback has already been received, the output time is extended by the Seal-in time.
The Seal-in time is relevant for equipment that sends feedback before the switching operation is completely performed. The Seal-in time is only
considered for control models with feedback monitoring.| 0.00 s| 0 s to 60 s
(_:5401:103) Switching-device type
The Switching-device type specifies the type of the switching device.| disconnector| switch-disconnector disconnector
grounding switch fast grounding switch

NOTE
The parameter Switching-device type is effective only on the IEC 61850 interface. This parameter is used to set the disconnector switching device type for communication via IEC 61850. It is a mandatory data object in the IEC 61850 standard.
The following figure shows the logical inputs and outputs of the Disconnector function block.

Figure 6-18 Logical Inputs and Outputs of the Disconnector Function Block
Table 6-14 and Table 6-15 list the inputs and outputs with a description of their function and type. For inputs, the effect of Quality = invalid on the value of the signal is described.
Table 6-14
Inputs of the Disconnector Function Block

Signal Name| Description| Type| Value if Signal
Quality=Invalid
---|---|---|---

Acquisition blocking| The binary input activates acquisition blocking. You can also set this binary input with an external toggle switch.| SPS| Unchanged
Reset
AcqBlk&Subst| Acquisition blocking and the substitution of the circuit breaker are reset with this input. If the input is activated, setting of the acquisition blocking and of the substitution is blocked.| SPS| Unchanged
Reset switch statist.| The binary input sets the operation counter for the switch to the value 0.| SPS| Unchanged
Position| The binary input Position can be used to read the disconnector position with double-point indication.| DPC| Unchanged

If the quality of the input signal assumes the status Quality = invalid, then the standby status (Health) of the Disconnector function block is set to Warning.
Table 6-15
Outputs of the Disconnector Function Block

SPS
Close command| This binary output is responsible for the command output On.| SPS
Command active| The binary output Command active is a running command for the signalization (command active or selected switching device). During Command active either an On or Off command is active.| SPS
Op.ct.| The information counts the number of disconnector switching cycles.| INS

Control
It is the task of the controls to execute command checks and establish communication between the command source and the disconnector. Using the control settings, you specify how the commands are to be processed (see also chapter 6.3.1 Command Checks and Switchgear Interlocking Protection).
Through the function SBO (Select Before Operate, reservation18), the switching device is reserved prior to the actual switching operation, thus it remains locked for additional commands. Feedback monitoring provides information about the initiator of the command while the command is in process, that means, informing whether or not the command was implemented successfully. These two options can be selected individually in the selection of the control model, so that 4 combinations in total are available (see the following table).
The control makes the following settings available (see next table).