XRio Reference Manual

XRIO
Reference Manual
OMICRON Test Universe
Manual Version: XRIO_REFERENCE.AE.1

© OMICRON electronics 2006. All rights reserved.
This manual is a publication of OMICRON electronics GmbH.
All rights including translation reserved. Reproduction of any kind, e.g., photocopying, microfilming or
storage in electronic data processing systems, requires the explicit consent of OMICRON electronics.
Reprinting, wholly or in part, is not permitted.
This manual represents the technical status at the time of printing. The product information,
specifications, and all technical data contained within this manual are not contractually binding.
OMICRON electronics reserves the right to make changes at any time to the technology and/or
configuration without announcement. OMICRON electronics is not to be held liable for statements and
declarations given in this manual. The user is responsible for every application described in this manual
and its results. OMICRON electronics explicitly exonerates itself from all liability for mistakes in this
manual.
2
XRIO Reference
Table of Contents
1 Introduction............................................................................................................................................. 10
2 Basic Elements of the XRIO Format ..................................................................................................... 11
2.1 XRIO Format Structure ...................................................................................................................... 11
2.2 Value types ........................................................................................................................................ 12
3 DEVICE block.......................................................................................................................................... 13
3.1 NAMEPLATE Block ........................................................................................................................... 13
3.2 LOCATION Block............................................................................................................................... 14
3.3 NOMINALVALUES Block .................................................................................................................. 14
3.3.1 PHASES....................................................................................................................................... 15
3.3.2 FNOM........................................................................................................................................... 15
3.3.3 VNOM .......................................................................................................................................... 15
3.3.4 VPRIM_LL.................................................................................................................................... 15
3.3.5 INOM............................................................................................................................................ 15
3.3.6 IPRIM ........................................................................................................................................... 15
3.4 RESIDUALFACTORS Block .............................................................................................................. 15
3.4.1 VLNVN and ININOM .................................................................................................................... 15
3.5 LIMITS Block...................................................................................................................................... 16
3.5.1 VMAX_LL ..................................................................................................................................... 16
3.5.2 IMAX ............................................................................................................................................ 16
3.6 MISC Block ........................................................................................................................................ 17
3.6.1 DEBOUNCETIME ........................................................................................................................ 17
3.6.2 DEGLITCHTIME .......................................................................................................................... 17
3.6.3 OVERLOADSUPTIME ................................................................................................................. 18
4 DISTANCE Block .................................................................................................................................... 19
4.1 Description ......................................................................................................................................... 19
4.2 Structure of the DISTANCE block...................................................................................................... 24
4.3 PROTECTEDOBJECT Block............................................................................................................. 24
4.3.1 PTCONN ...................................................................................................................................... 25
4.3.2 CTSTARPOINT............................................................................................................................ 25
4.3.3 LINEANGLE ................................................................................................................................. 25
4.3.4 LINELENGTH .............................................................................................................................. 25
4.3.5 GRF_MODE................................................................................................................................. 26
4.3.6 KL_MAG....................................................................................................................................... 26
4.3.7 KL_ANGLE................................................................................................................................... 26
4.3.8 ZN_R............................................................................................................................................ 26
4.3.9 ZN_X ............................................................................................................................................ 26
4.3.10 Z0Z1_MAG ................................................................................................................................ 26
4.3.11 Z0Z1_ANGLE ............................................................................................................................ 26
4.3.12 MCF_MODE .............................................................................................................................. 27
4.3.13 KM_MAG.................................................................................................................................... 27
4.3.14 KM_ANGLE ............................................................................................................................... 27
4.3.15 ZM_R ......................................................................................................................................... 27
4.3.16 ZM_X.......................................................................................................................................... 27
4.3.17 Z0MZ1_MAG ............................................................................................................................. 27
4.3.18 Z0MZ1_ANGLE ......................................................................................................................... 27
3
4.4 PROTECTIONDEVICE Block ............................................................................................................ 28

4.4.1 ARCRES ...................................................................................................................................... 28
4.4.2 IMPCORR .................................................................................................................................... 28
4.4.3 IMPPRIM...................................................................................................................................... 28
4.4.4 CALC_RERL_XEXL..................................................................................................................... 28
4.4.5 TOLERANCES............................................................................................................................. 28
4.4.5.1 TTOLPLUS ........................................................................................................................... 29
4.4.5.2 TTOLMINUS ......................................................................................................................... 29
4.4.5.3 TTOLREL.............................................................................................................................. 29
4.4.5.4 ZTOLREL.............................................................................................................................. 29
4.4.5.5 ZTOLABS ............................................................................................................................. 29
4.4.6 ZONES......................................................................................................................................... 29
4.4.7 ZONE ........................................................................................................................................... 30
4.4.7.1 ACTIVE................................................................................................................................. 30
4.4.7.2 MAN_LABEL......................................................................................................................... 30
4.4.7.3 LABEL................................................................................................................................... 31
4.4.7.4 INDEX................................................................................................................................... 31
4.4.7.5 TYPE .................................................................................................................................... 31
4.4.7.6 FAULTLOOP ........................................................................................................................ 31
4.4.7.7 TRIPTIME ............................................................................................................................. 32
4.4.7.8 TOLERANCES Block ........................................................................................................... 32
4.4.7.8.1 TTPL_VALID .................................................................................................................. 32
4.4.7.8.2 TTOLPLUS..................................................................................................................... 32
4.4.7.8.3 TTMI_VALID .................................................................................................................. 32
4.4.7.8.4 TTOLMINUS .................................................................................................................. 32
4.4.7.8.5 TTRL_VALID.................................................................................................................. 32
4.4.7.8.6 TTOLREL ....................................................................................................................... 32
4.4.7.8.7 ZTRL_VALID.................................................................................................................. 33
4.4.7.8.8 ZTOLREL ....................................................................................................................... 33
4.4.7.8.9 ZTAB_VALID ................................................................................................................. 33
4.4.7.8.10 ZTOLABS..................................................................................................................... 33
4.4.7.9 MHOSHAPE Block ............................................................................................................... 33
4.4.7.9.1 ANGLE ........................................................................................................................... 33
4.4.7.9.2 REACH........................................................................................................................... 33
4.4.7.9.3 OFFSET ......................................................................................................................... 33
4.4.7.9.4 INVERT .......................................................................................................................... 33
4.4.7.10 LENSTOMATOSHAPE Block............................................................................................. 34
4.4.7.10.1 ANGLE ......................................................................................................................... 34
4.4.7.10.2 REACH......................................................................................................................... 34
4.4.7.10.3 OFFSET ....................................................................................................................... 34
4.4.7.10.4 INVERT ........................................................................................................................ 34
4.4.7.10.5 SHAPE_MODE ............................................................................................................ 34
4.4.7.10.6 WIDTH ......................................................................................................................... 34
4.4.7.10.7 RATIO_AB ................................................................................................................... 34
4.4.7.11 GENERICSHAPE Block ..................................................................................................... 35
4
XRIO Reference
4.4.7.12 LINE Block .......................................................................................................................... 35

4.4.7.12.1 REFPOINT_TYPE ....................................................................................................... 36
4.4.7.12.2 REFPOINT_R .............................................................................................................. 36
4.4.7.12.3 REFPOINT_X .............................................................................................................. 36
4.4.7.12.4 REFPOINT_MAG......................................................................................................... 36
4.4.7.12.5 REFPOINT_ANGLE..................................................................................................... 36
4.4.7.12.6 ANGLE ......................................................................................................................... 36
4.4.7.12.7 INSIDE ......................................................................................................................... 36
4.4.7.13 ARC Block .......................................................................................................................... 37
4.4.7.13.1 REFPOINT_TYPE ....................................................................................................... 37
4.4.7.13.2 REFPOINT_R .............................................................................................................. 37
4.4.7.13.3 REFPOINT_X .............................................................................................................. 37
4.4.7.13.4 REFPOINT_MAG......................................................................................................... 37
4.4.7.13.5 REFPOINT_ANGLE..................................................................................................... 37
4.4.7.13.6 RADIUS........................................................................................................................ 37
4.4.7.13.7 STARTANGLE ............................................................................................................. 37
4.4.7.13.8 ENDANGLE ................................................................................................................. 37
4.4.7.13.9 DIR ............................................................................................................................... 38
4.4.7.13.10 INSIDE ....................................................................................................................... 38
4.4.7.14 INVERT............................................................................................................................... 35
4.4.7.15 AUTOCLOSE...................................................................................................................... 35
5 CBCONFIGURATION Block ................................................................................................................... 39
5.1 TRIPTIME .......................................................................................................................................... 39
5.2 CLOSETIME ...................................................................................................................................... 39
5.3 P52AB ................................................................................................................................................ 39
6 VISTARTING Block ................................................................................................................................. 40
6.1 ITOL ................................................................................................................................................... 40
6.2 VTOL.................................................................................................................................................. 40
6.3 CHARVIS ........................................................................................................................................... 40
6.3.1 IG ................................................................................................................................................. 40
6.3.2 IGG............................................................................................................................................... 40
6.3.3 VLNIG .......................................................................................................................................... 41
6.3.4 VLNIGG........................................................................................................................................ 41
6.3.5 VLLIG ........................................................................................................................................... 41
6.3.6 VLLIGG ........................................................................................................................................ 41
7 SYNCHRO Block ..................................................................................................................................... 42
7.1 TG_PHASE_SHIFT ........................................................................................................................... 43
7.2 STARTING......................................................................................................................................... 43
7.3 PHASE_SEQUENCE1 ...................................................................................................................... 43
7.4 PHASE_SYSTEM1 ............................................................................................................................ 43
7.5 PHASE_SEQUENCE2 ...................................................................................................................... 43
7.6 PHASE_SYSTEM2 ............................................................................................................................ 44
7.7 USE_RATIO_SYS1 ........................................................................................................................... 44
7.8 VNOM_SEC_SYS2............................................................................................................................ 44
5
7.9 CHARSYNC Block ............................................................................................................................. 45

7.9.1 D_VMAX ...................................................................................................................................... 45
7.9.2 D_VMIN........................................................................................................................................ 45
7.9.3 VTOLABS..................................................................................................................................... 45
7.9.4 VTOLREL..................................................................................................................................... 46
7.9.5 D_FMAX....................................................................................................................................... 46
7.9.6 D_FMIN........................................................................................................................................ 46
7.9.7 FTOLABS..................................................................................................................................... 46
7.9.8 FTOLREL ..................................................................................................................................... 46
7.9.9 D_PHASEANGLE ........................................................................................................................ 46
7.9.10 PHASEANGLE_TOLABS .......................................................................................................... 46
7.9.11 PHASEANGLE_TOLREL........................................................................................................... 46
7.9.12 INNER_LIMIT............................................................................................................................. 47
7.9.13 OUTER_LIMIT ........................................................................................................................... 47
7.9.14 MIN_SYNC_TIME...................................................................................................................... 47
7.9.15 MIN_SYNC_TIME_TOL............................................................................................................. 47
8 DIFFERENTIAL Block............................................................................................................................. 48
8.1 WINDING_COUNT ............................................................................................................................ 48
8.2 REF_WINDING.................................................................................................................................. 48
8.3 OBJECT_TYPE ................................................................................................................................. 49
8.4 ITOL_REL .......................................................................................................................................... 49
8.5 ITOL_ABS.......................................................................................................................................... 49
8.6 TTOL_REL......................................................................................................................................... 49
8.7 TTOL_ABS......................................................................................................................................... 49
8.8 TREF.................................................................................................................................................. 49
8.9 TRET.................................................................................................................................................. 49
8.10 TMAX ............................................................................................................................................... 49
8.11 IREF ................................................................................................................................................. 49
8.12 USECT ............................................................................................................................................. 50
8.13 DELTACT......................................................................................................................................... 50
8.14 WINDING ......................................................................................................................................... 50
8.14.1 NAME......................................................................................................................................... 51
8.14.2 INULL_ELIMINATION................................................................................................................ 51
8.14.3 CONNECTION........................................................................................................................... 51
8.14.4 CONNECTIONNUMBER ........................................................................................................... 51
8.14.5 NOM_PD_PH............................................................................................................................. 51
8.14.6 NOM_CT_PH ............................................................................................................................. 51
8.14.7 GROUNDING_CT_PH............................................................................................................... 51
8.14.8 NOM_PD_N ............................................................................................................................... 51
8.14.9 NOM_CT_N ............................................................................................................................... 51
8.14.10 GROUNDING_CT_N ............................................................................................................... 51
8.14.11 VN ............................................................................................................................................ 52
8.14.12 SN ............................................................................................................................................ 52
8.14.13 GROUNDING_TRF.................................................................................................................. 52
8.14.14 TAP_SETTING ........................................................................................................................ 52
8.14.15 DELTA_CONN_CT .................................................................................................................. 52
6
XRIO Reference
8.15 DIFFBIAS......................................................................................................................................... 52
8.15.1 ACTIVE ...................................................................................................................................... 52
8.15.2 DIFF Block ................................................................................................................................. 52
8.15.2.1 IDIFFGG ............................................................................................................................. 53
8.15.2.2 TDIFFGG ............................................................................................................................ 53
8.15.2.3 IDIFFG ................................................................................................................................ 53
8.15.2.4 TDIFFG............................................................................................................................... 53
8.15.3 BIAS Block ................................................................................................................................. 53
8.15.3.1 DEFBIAS ............................................................................................................................ 53
8.15.3.2 BIASDIVISOR..................................................................................................................... 54
8.15.3.3 TOLHARM_ABS ................................................................................................................. 54
8.15.3.4 TOLHARM_REL ................................................................................................................. 54
8.15.3.5 CHARHARM ....................................................................................................................... 54
8.15.3.5.1 ORDERHARM ............................................................................................................. 54
8.15.3.5.2 DELAYHARM............................................................................................................... 54
8.15.3.5.3 CHARTABLE ............................................................................................................... 54
8.15.4 TRIPCHAR................................................................................................................................. 54
8.15.4.1 POINT................................................................................................................................. 54
9 OVERCURRENT Block ........................................................................................................................... 55
9.1 ITOLREL ............................................................................................................................................ 55
9.2 ITOLABS............................................................................................................................................ 55
9.3 TTOLREL........................................................................................................................................... 55
9.4 TTOLABS........................................................................................................................................... 56
9.5 PTCONN............................................................................................................................................ 56
9.6 CTSTARPOINT.................................................................................................................................. 56
9.7 DIRECTIONAL................................................................................................................................... 56
9.8 AUTORESET ..................................................................................................................................... 56
9.9 Groups ............................................................................................................................................... 57
9.9.1 NAME........................................................................................................................................... 57
9.9.2 RESET_RATIO ............................................................................................................................ 57
9.9.3 UNIT............................................................................................................................................. 58
9.9.3.1 NAME ................................................................................................................................... 58
9.9.3.2 ACTIVE................................................................................................................................. 58
9.9.3.3 IPICKUP ............................................................................................................................... 58
9.9.3.4 TINDEX................................................................................................................................. 58
9.9.3.5 CHARTYPE .......................................................................................................................... 59
9.9.3.6 PREDEFCHAR ..................................................................................................................... 60
9.9.3.7 CHAR block .......................................................................................................................... 61
9.9.3.8 CHARIAC block .................................................................................................................... 62
9.9.3.9 CHARI2T block ..................................................................................................................... 63
9.9.3.10 TABLE block ....................................................................................................................... 63
9.9.3.10.1 POINT .......................................................................................................................... 63
7
10 METER Block ........................................................................................................................................ 64

10.1 TYPE................................................................................................................................................ 64
10.2 SINGLEPHASE................................................................................................................................ 65
10.3 GATED_MECHANISM .................................................................................................................... 65
10.4 THREEWIRE ................................................................................................................................... 65
10.5 DIRECTION ..................................................................................................................................... 65
10.6 EXPORTDIR .................................................................................................................................... 65
10.7 QUADRANT..................................................................................................................................... 65
10.8 PULSE_TYPE.................................................................................................................................. 66
10.9 CERTIFIED ...................................................................................................................................... 66
10.10 CLASS ........................................................................................................................................... 66
10.11 PULSES_PER_REV ...................................................................................................................... 66
10.12 SETTLING ..................................................................................................................................... 66
10.13 CONSTANT ................................................................................................................................... 66
11 TRANSDUCER Block............................................................................................................................ 67
11.1 TRDCR_OUT................................................................................................................................... 67
11.2 ANGLE_REF.................................................................................................................................... 67
11.3 ERROR_REF................................................................................................................................... 68
11.4 SETTLING ....................................................................................................................................... 68
11.5 CTSTARPOINT................................................................................................................................ 68
11.6 FUNCTION Block............................................................................................................................. 68
11.6.1 TYPE.......................................................................................................................................... 69
11.6.2 TOLERANCE ............................................................................................................................. 69
11.6.3 PHASES..................................................................................................................................... 69
11.6.4 CHAR Block ............................................................................................................................... 70
11.6.4.1 TYPE .................................................................................................................................. 71
11.6.4.2 SYMMETRICAL.................................................................................................................. 72
11.6.4.3 MIN_INP ............................................................................................................................. 72
11.6.4.4 MIN_OUT............................................................................................................................ 72
11.6.4.5 KNEE_INP .......................................................................................................................... 72
11.6.4.6 KNEE_OUT ........................................................................................................................ 72
11.6.4.7 MAX_INP ............................................................................................................................ 72
11.6.4.8 MAX_OUT .......................................................................................................................... 72
11.6.4.9 SAT_OUT ........................................................................................................................... 73
Appendix: From RIO to XRIO 2.0 ............................................................................................................. 74
1 About XML............................................................................................................................................... 74
2 Comparison of XRIO 2.0 and RIO test object definitions ................................................................... 74
2.1 DEVICE.............................................................................................................................................. 75
2.2 DISTANCE......................................................................................................................................... 76
2.3 CBCONFIGURATION........................................................................................................................ 80
2.4 VISTARTING ..................................................................................................................................... 81
2.5 SYNCHRONIZER .............................................................................................................................. 82
2.6 DIFFERENTIAL ................................................................................................................................. 83
2.7 OVERCURRENT ............................................................................................................................... 86
2.8 METER .............................................................................................................................................. 88
2.9 TRANSDUCER .................................................................................................................................. 89
8
XRIO Reference
Glossary
Abbreviations
OTU : OMICRON Test Universe

RIO : Relay Interface by OMICRON
XRIO : eXtended Relay Interface by OMICRON
OCC : OMICRON Control Center
XML : eXtensible Markup Language
SEL : Schweitzer Engineering Laboratories
VB.Net : Visual Basic .Net
MSDN : MicroSoft Developer Network
SDK : Software Developer Kit
CLR : Common Language Runtime
Definitions
Test Object : Component of the Test Universe software describing the device under
test
XRIO : Specification for Test Object definitions introduced with Test Universe
2.0
XRIO File : Saved XRIO Test Object as a file
XRIO Converter : Test Object with automatic calculation of parameters from settings
9
1 Introduction
The XRIO concept was introduced with the OMICRON Test Universe (OTU) 2.0 as the evolution of the
Relay Interface by OMICRON (RIO). It represents the second generation of Test Object models in the
OTU. A test object can be a protection relay, a meter, or any other device that can be tested with the
OMICRON Test Universe.
The purpose of this manual is to describe the structure of the XRIO file and the parameters contained
in it. For a general complete description of the XRIO functionality and usage please refer to the
XRIO User Manual. Since the Custom section is user-defined, only the RIO section will be described
here.
10
XRIO Reference
2 Basic Elements of the XRIO Format

The XRIO format is stored in XML. In principle, XRIO files should be editable by any XML editor.
However, since the editor would not understand the underlying structure, XRIO files should only be
modified with OMICRON-provided tools.
The principle of a block, row and value structure from the RIO format has been kept in XRIO, only now
it is embedded and expressed in XML instead of in plain ASCII, as it was before. In this structure, a
block is a group containing parameters and other blocks. It is used to group data that belong logically
together. A row corresponds to a parameter, and it has a value. In XRIO, parameters will always have
a single value; no multiple values are allowed.
For an overview of the different XML definitions and descriptions, please look into the OMICRON\Test
Universe\Apps\XRIO folder, where all XML structures are available. ATTENTION: Do not modify any
of these files in any way.
2.1 XRIO Format Structure

RIO data is organized in a block structure. A block can aggregate rows (parameters) and other blocks,
called sub blocks. Sub blocks and parameters within a block normally must appear in a predefined
order; the block hierarchy must be preserved. Every block and row has a unique ID, plus a Name and
a Description. Both Name and Description are localizable and may vary; the ID is fixed, and so it is
used to identify the block or row in the XRIO file. In this document, we will also use the ID to identify
blocks and parameters.
A parameter will have one single value in XRIO; the multiple values in one single line that were so
common in RIO are no more. These cases have been converted into blocks, with the necessary sub
blocks to ensure that each parameter has one and only one value associated to it.
In the XRIO format, each block and parameter may store additional information, such as a description,
an Enabled flag or a formula for this flag; in the case of parameters, the value, unit, multiplier and
Value formula, where applicable, are stored too. In this document, we will focus only on the structure
of the data and on the meaning and effects of each block and parameter. For full information on block
and parameter properties, and on how to link a parameter's value to a formula, please consult the
XRIO User Manual.
11
2.2 Value Data Types

Parameters in XRIO may have values of the following types:
• Real
• Integer
• Boolean
• String
• Enumeration
XRIO is implemented in the Microsoft .Net Framework, and the value types correspond to the following
in the Common Type System of the CLR (Common Language Runtime):
XRIO CTS Description

Real Double A double-precision (64-bit) floating-point number
Integer Int32 A 32-bit signed integer
Boolean Boolean A Boolean value (true or false)
String String An immutable, fixed-length string of Unicode characters
Table 1: XRIO data types
Enumeration values consist of a certain number of Strings, only one of which may be selected at any
given moment.
12
XRIO Reference
3 DEVICE block
The DEVICE block must always be present in an XRIO file – all others are optional. Additionally, there
may be only one DEVICE block in the file. All others can be repeated as many times as necessary.
The DEVICE block describes general data for the relay - the only data stored here are those that are
not specific to any given protection function. Examples of this are the nominal current and voltage, the
relay's serial number, etc.
The structure of the DEVICE block is as follows:
ID Type Description Refer to

NAMEPLATE Block Device identification Page 13
LOCATION Block Location of the device Page 14
NOMINALVALUES Block Nominal Values Page 14
RESIDUALFACTORS Block Residual Factors Page 15
LIMITS Block Device limits Page 16
MISC Block Miscellaneous settings Page 17
3.1 NAMEPLATE Block

The NAMEPLATE block contains descriptive relay parameters. These are:

DEVICE_MODEL String Device model Page 13
MANUFACTURER String Device manufacturer Page 13
DEVICE_TYPE String Device type Page 13
SERIALNR String Device Serial number Page 13
ADDITIONAL_INFO2 String Additional info Page 13
All strings in this block are user-definable and have no influence on the test. They exist for
documentation purposes, and they will appear in the report exactly as entered.
13
3.2 LOCATION Block

The LOCATION block contains parameters to describe the relay's location. These are:

DEVICE_ADDRESS String Device address Page 14
SUBSTATION String Substation name Page 14
SUBSTATION_ADDRESS String Substation address Page 14
BAY String Bay name Page 14
BAY_ADDRESS String Bay address Page 14
PROTECTED_OBJECT_NAME String Relay name Page 14
All strings in this block are user-definable and have no influence on the test. They exist for
documentation purposes, and they will appear in the report exactly as entered.
3.3 NOMINALVALUES Block

This block contains the nominal values of the protection and of the CTs and PTs to which it is
connected. These values are:

PHASES Integer Number of phases Page 15
FNOM Real Nominal Frequency Page 15
VNOM Real Nominal voltage (secondary) Page 15
VPRIM_LL Real Nominal voltage (primary) Page 15
INOM Real Nominal current (secondary) Page 15
IPRIM Real Nominal current (primary) Page 15
14
XRIO Reference
3.3.1 PHASES
The number of phases of the system. This number may be 2 or 3. The setting determines the available
fault loops in some of the modules, and the calculation of the LN voltages from the LL voltages:
Phases Calculation
2 VLN = VLL / 2
3 VLN = VLL / √3
3.3.2 FNOM
This parameter represents the nominal frequency of the system in cycles per second (Hz).
3.3.3 VNOM
The nominal or secondary voltage in volts L-L.
3.3.4 VPRIM_LL
The primary voltage in volts L-L.
3.3.5 INOM
The nominal or secondary current in A.
3.3.6 IPRIM
The primary current in A.
3.4 RESIDUALFACTORS Block

Contains the residual factors. These are:

VLNVN Real VLN / VN Page 15
ININOM Real IN / Inom Page 15
3.4.1 VLNVN and ININOM

The ININOM and VLNVN parameters are only relevant if the relay has separate potential/current
transformers for the residual voltage/current (to increase the device's sensitivity). The ratios of these
separate transformers relative to the transformer ratios of the single phases are expressed as these
two factors.
15
3.5 LIMITS Block

This block contains the maximum values that the relay can accept without damage. No module in the
Test Universe will exceed these values, regardless of the test settings. If a certain test would exceed
the limits set in this block, the test is not performed and it is adequately reported.

VMAX_LL Real Maximum voltage Page 16
IMAX Real Maximum current Page 16
3.5.1 VMAX_LL
The maximum voltage in volts L-L that the device under test can withstand in permanence.
3.5.2 IMAX
The maximum current in A that the device under test can withstand in permanence.
16
XRIO Reference
3.6 MISC Block

This block contains varied settings that do not fit in any other of the DEVICE sub blocks:

DEBOUNCETIME Real De-bounce filter time Page 17
DEGLITCHTIME Real De-glitch filter time Page 17
OVERLOADSUPTIME Real Overload Detection Sensitivity Page 18
3.6.1 DEBOUNCETIME
The de-bounce time in seconds. This value is used where signal-smoothing algorithms are
implemented. When the de-bouncing filter is in operation, the system will wait for DEBOUNCETIME
after any change in the binary inputs, before registering another change. A value of zero in
DEBOUNCETIME will disable the feature.
t
Signal before filtering:
t = DEBOUNCETIME
Signal after filtering:
3.6.2 DEGLITCHTIME
The deglitch time in seconds. This value is used where signal-smoothing algorithms are implemented.
When the deglitching filter is in operation, the system will only register signal changes if they last at
least for DEGLITCHTIME. A value of zero in DEGLITCHTIME will disable the feature.
t t
Signal before filtering:
t = DEGLITCHTIME
Signal after filtering:
17
3.6.3 OVERLOADSUPTIME
The Overload Detection Suppression Time, in seconds. After any change in the values of the analog
outputs, overload detection will be disabled during this time. This will prevent false positives while the
system adapts to the new load conditions. A value of zero in OVERLOADSUPTIME will disable the
feature, and will therefore detect the overload condition at all times.
18
XRIO Reference
4 DISTANCE Block
The DISTANCE block holds the settings for Distance units. It is the required block of the Distance and
Advanced Distance test modules, and must therefore be present when one of these modules is
inserted in the OCC file. Quick CMC, Sequencer and Autoreclosure also automatically create a
DISTANCE block. For all the rest of the modules, the DISTANCE block is optional.
The DISTANCE block has a more complex structure than the device block. This is mostly due to the
need to describe arbitrary zone shapes; today's distance protections may have any number of
protection zones, each of then having any shape, and the DISTANCE block is designed to model them.
The following is an overview of the functionality described by the block.
4.1 Description
The DISTANCE block is divided in two sub-blocks: PROTECTEDOBJECT and PROTECTIONDEVICE.
PROTECTEDOBJECT holds the general settings of a Distance protection, while
PROTECTIONDEVICE holds the zone settings. In turn, PROTECTIONDEVICE contains two sub-
blocks: TOLERANCES and ZONES. The TOLERANCES block contains the general tolerances, which
will apply to all the zones by default, unless zone-specific tolerances are defined. The ZONES block,
on the other hand, contains any number of ZONE blocks. A ZONE block describes the shape of a
zone, and the zone-specific tolerances if defined (otherwise, the general tolerances will be used).
Tolerances for trip times are set both relative in percent (TTOLREL) and absolute in Ohms
(ZTOLABS). Tolerances for impedances are also set both relative in percent (ZTOLREL) and absolute
in Ohms (ZTOLABS). The relative impedance tolerance for a zone is converted into an absolute value
on the line angle. Specifically, the reach of the zone on the line angle is multiplied by the percent value.
|Z|
φL
R
Figure 1: Tolerance bands in a Distance zone
The grounding factor can be set either with kL, RE/RL and XE/XL or Z0/Z1. The user must select
which of these methods they desire to use. All parameters are present in the XRIO file, and an
additional parameter (GRF_MODE) determines which one of them is active.
19
In addition, the mutual coupling factor can also be described in three different ways. It can be set
either with kM, RM/RL and XM/XL or Z0M/Z1. Again, all parameters are present in the XRIO file, and
an additional parameter (MCF_MODE) determines which one of them is active.
There are three different types of shapes for a zone: a generic shape defined by individual lines and
arcs, the mho shape, and the lens/tomato shape. A given zone may have only one of these shapes.
A generic shape is constructed from multiple individual elements; an individual element may be a line
or an arc.
Lines are defined by a point and an angle. The point in turn may be defined in Cartesian or Polar
coordinates.
The following data define an arc:

• center point (in Cartesian or Polar coordinates)
• radius
• direction (clockwise or counterclockwise)
• start and end angles
It is assumed that a shape is only a "single" shape, which means that there is only one single
connected area where all points are considered "inside" of the shape and only one additional area (the
inversion in relationship to the whole Cartesian space) where all points are considered "outside".
A shape does not necessarily have to be "closed". An "open" shape divides the Cartesian space into
two areas (half-spaces), both of which extend to infinity. A "closed" shape defines a finite area for
"inside" and an infinite area for "outside".
Because each characteristic shape is considered a "single" shape, there are a few constraints for the
elements that constitute a valid characteristic:
• Two adjacent elements in the ordered list of elements must have at least one intersection
point. Thus, two adjacent lines cannot be parallel, and arcs must intersect the adjacent
element if prolonged sufficiently.
• No intersection between two non-adjacent elements in the ordered list of elements is allowed
within the segment that is defined by the two intersection points with the preceding and
succeeding element. Otherwise, the characteristic would fall apart into multiple independent
parts and would no longer be "single".
The software will verify these constraints, and reject as invalid any shape that does not fulfill them.
20
XRIO Reference
Figure 2: Example of an invalid shape

The geometrical algorithms calculate a tolerance band around the nominal characteristic shape with a
constant width, which is the calculated Z tolerance. The tolerance band is constructed in such a way
that the Euclidian distance from the nominal shape for all point on the tolerance border is constant
(and is equal to the Z tolerance). Therefore, the edges around vertices of the nominal shape are
rounded in the tolerance shapes.
With the implementation of the impedance tolerance, an "outer" and an "inner" tolerance figure can be
constructed. The tolerance figures do not necessarily have to be single shapes any more.
There are cases where the figures can fall apart into separate shapes. Additionally, not all border
elements from the nominal shape need to be part of the tolerance figures (such as whenever their
"size" is smaller than the tolerance value).
Figure 3 illustrates a tolerance diagram with some interesting characteristics. It has two separate inner
tolerance shapes, and not all border elements are used as border elements for the tolerance shapes.
Figure 3: Shape tolerances
21
A mho characteristic is a special kind of zone, with a circular shape. The mho characteristic is defined
by an angle, a reach and an offset.
The center of the circle is located on a line going through the origin, and with an angle with the X axis
equal to the mho angle; The radius r is calculated as follows:
r = (REACH + OFFSET) / 2
Figure 4: MHO characteristic (picture quality good enough ??)

A lens / tomato shape is defined by the following values:
• ANGLE φ
• REACH
• OFFSET
• either WIDTH or AB segment
Figure 5: lens / tomato shape
The distance B on the figure is calculated according to the following equation:
B = REACH + OFFSET
22
XRIO Reference
WIDTH and AB ratio are mutually exclusive. Only one of these values is taken as a parameter – the
SHAPE_MODE parameter selects which one is used.
If A < B, the shape is a lens. For A > B, the shape is a tomato - the valid part is just the outer arcs of
the two circles in the figure. For A = B, the lens/tomato resolves to a standard mho shape.
23
4.2 Structure of the DISTANCE block

PROTECTEDOBJECT Block Properties of the device Page 24
PROTECTIONDEVICE Block Zone-oriented properties Page 28
4.3 PROTECTEDOBJECT Block

This block contains parameters for the Distance functionality of the Test Object. The parameters are:

PTCONN Enumeration Connection of the PT Page 25
CTSTARPOINT Enumeration Connection of the CT Page 25
LINEANGLE Real Line Angle Page 25
LINELENGTH Real Length of the Line Page 25
GRF_MODE Enumeration Grounding factor selector Page 26
KL_MAG Real Magnitude of the kL factor Page 26
KL_ANGLE Real Angle of the kL factor Page 26
ZN_R Real Real part of the ZN factor Page 26
ZN_X Real Imaginary part of the ZN factor Page 26
Z0Z1_MAG Real Magnitude of the Z0Z1 factor Page 26
Z0Z1_ANGLE Real Angle of the Z0Z1 factor Page 26
MCF_MODE Enumeration Selector of the Mutual Coupling factor Page 27
KM_MAG Real Magnitude of the kM factor Page 27
KM_ANGLE Real Angle of the kM factor Page 27
ZM_R Real Real part of the ZM factor Page 27
ZM_X Real Imaginary part of the ZM factor Page 27
Z0MZ1_MAG Real Magnitude of the Z0MZ1 factor Page 27
Z0MZ1_ANGLE Real Angle of the Z0MZ1 factor Page 27
The detailed meaning and usage of these parameters is described in the following sections.
24
XRIO Reference
4.3.1 PTCONN
This parameter controls the connection of the power (voltage) transformer. There are two possible
values: BUS (direction busbar) and LINE (direction line). In the Distance module and in some other
modules, this setting determines whether the voltages are turned off (dir busbar) or go back to nominal
(dir line) in the post-fault stage if a trip has occurred.
PT on line side PT on busbar side

Busbar Busbar
Relay
PT
PT
Relay
4.3.2 CTSTARPOINT
This parameter controls the connection of the star point of the current transformer. There are two
possible values: BUS (direction busbar) and LINE (direction line). This setting determines whether the
currents are rotated. If the CT is grounded towards the line, the currents are output as calculated by
the test module; if the CT is grounded towards the busbar (that is, towards the protected object) all
currents are rotated by 180° before being sent to the relay.
CT towards line CT towards busbar
Busbar Busbar
Protection relay Protection relay
4.3.3 LINEANGLE
The line angle in degrees.
4.3.4 LINELENGTH
The length of the line in Ohms.
25
4.3.5 GRF_MODE
This parameter selects which of the different versions of the Grounding Factor is used. Possible
values for this setting are KL, ZNR_ZNX and Z0Z1.
Setting Factor selected
KL kL
ZNR_ZNX RE/RL and XE/XL
Z0Z1 Z0 / Z1
4.3.6 KL_MAG
Magnitude of the complex grounding factor.
4.3.7 KL_ANGLE
Angle of the complex grounding factor, in degrees.
4.3.8 ZN_R
This is the real part of the second option for describing the complex grounding factor.
4.3.9 ZN_X
This is the imaginary part of the second option for describing the complex grounding factor. The first
value ZN_R (RE/RL) and the second value ZN_X (XE/XL) are calculated into kL according to the
following equations for each individual ZL:
RE
fR =
RL
XE
fX =
XL
Z E RE + jX E
kL = =
Z L RL + jX L
f R ⋅ RL + jf X ⋅ X L
kL =
RL + jX L
4.3.10 Z0Z1_MAG
This is the magnitude of the third way to express the complex grounding factor.
4.3.11 Z0Z1_ANGLE
This is the angle of the third way to express the complex grounding factor, in degrees. Z0 and Z1 are
converted into kL according to the following equation:
1⎛ Z ⎞
k L = ⎜⎜ 0 − 1⎟⎟
3 ⎝ Z1 ⎠
26
XRIO Reference
4.3.12 MCF_MODE
This parameter selects which of the different versions of the mutual coupling factor is used. Possible
values for this setting are KM, ZMR_ZMX and Z0MZ1.
Setting Factor selected
KM kM
ZMR_ZMX RM/RL and XM/XL
Z0MZ1 Z0 / Z1
4.3.13 KM_MAG
Magnitude of the complex mutual coupling factor.
4.3.14 KM_ANGLE
Angle of the complex mutual coupling factor, in degrees.
4.3.15 ZM_R
This is the real part of the second option for describing the complex mutual coupling factor.
4.3.16 ZM_X
This is the imaginary part of the second option for describing the complex mutual coupling factor. The
first value ZM_R (RM/RL) and the second value ZM_X (XM/XL) are calculated into kM according to the
following equations for each individual ZL:
RM
fR =
RL
XM
fX =
XL
Z M RM + jX M
kM = =
ZL RL + jX L
f R ⋅ RL + jf X ⋅ X L
kM =
RL + jX L
4.3.17 Z0MZ1_MAG
This is the magnitude of the third way to express the mutual coupling factor.
4.3.18 Z0MZ1_ANGLE
This is the angle of the third way to express the mutual coupling factor, in degrees. Z0 and Z1 are
converted into kM according to the following equation:
Z0
kM =
3⋅ Z1
27
4.4 PROTECTIONDEVICE Block

This block contains zone-related data, as follows:

ARCRES Boolean Separate fault from arc resistance Page 28
IMPCORR Boolean Allow automatic impedance correction Page 28
IMPPRIM Boolean Use primary impedances Page 28
CALC_RERL_XEXL Boolean Use RE/RL for grounding factor Page 28
TOLERANCES Block Global tolerances for all zones Page 28
ZONES Block Distance zones Page 29
4.4.1 ARCRES
If set, the arc resistance is separated from the fault resistance so that the fault resistance is composed
of the part on the line plus the pure resistive arc resistance. In this case, for phase-to-ground faults,
the arc resistance is not compensated with the grounding factor (multiplied by (1 + kL)).
4.4.2 IMPCORR
If set, the fault impedance is multiplied by (1 A / lnom) before the fault quantities are calculated.
4.4.3 IMPPRIM
If set, all impedances are considered as primary impedances and are multiplied by Vnom / Vprim Iprim / Inom
before the fault quantities are calculated.
4.4.4 CALC_RERL_XEXL
If set, the grounding factor is calculated using RE/RL and XE/XL.
4.4.5 TOLERANCES
This block holds the default tolerances for the zones. Each zone may define its own tolerances, which
will then supersede the ones defined in this block.

TTOLPLUS Real Positive time tolerance (absolute) Page 29
TTOLMINUS Real Negative time tolerance (absolute) Page 29
TTOLREL Real Relative time tolerance Page 29
ZTOLREL Real Relative impedance tolerance Page 29
ZTOLABS Real Absolute impedance tolerance Page 29
28
XRIO Reference
4.4.6 TTOLPLUS
Positive time tolerance, in seconds.
4.4.7 TTOLMINUS
Negative time tolerance, in seconds.
4.4.8 TTOLREL
Relative time tolerance, in times percent.
4.4.9 ZTOLREL
Relative Z tolerance, in percent.
4.4.10 ZTOLABS
Absolute Z tolerance, in Ω.
4.4.11 ZONES
This block is a container for all the distance zones defined in the XRIO file. The ZONES block may
contain any number of ZONE sub-blocks. Each ZONE sub-block in turn defines a Distance zone.
29
4.4.12 ZONE
The ZONE block is composed of zone settings, the zone tolerance blocks and one zone shape block.
There are three possible types of shape blocks, but they are mutually exclusive: only one of them may
appear in the XRIO file for a given zone. The Classic UI in the Test Object enforces this constraint
(zones cannot be added via the standard UI). Anyone wishing to generate an XRIO file externally must
be aware of this and make sure only one shape block per zone is present in the XRIO file.

ACTIVE Boolean Select whether the zone is active Page 30
MAN_LABEL Boolean Flag for manual naming of the zones Page 30
LABEL String Zone label Page 31
INDEX Integer Zone index Page 31
TYPE Enumeration Type of zone Page 31
FAULTLOOP Enumeration Fault loop to which the zone applies Page 31
TRIPTIME Real Nominal tripping time Page 31
TOLERANCES Block Zone-specific tolerances Page 32
MHOSHAPE Block Describes the shape of the zone as mho. Page 33
Mutually exclusive with GENERICSHAPE and
LENSTOMATOSHAPE.
LENSTOMATOSH Block Describes the shape of the zone as lens/tomato. Page 34
APE Mutually exclusive with MHOSHAPE and
GENERICSHAPE.
GENERICSHAPE Block Describes the shape of the zone. Mutually Page 35
exclusive with MHOSHAPE and
LENSTOMATOSHAPE.
4.4.13 ACTIVE
Indicates if the zone is active or not. Inactive zones remain defined, but are not used by the test
modules.
4.4.14 MAN_LABEL
If set, the label displayed for the zone will be the one entered in the LABEL setting; otherwise, the
software will ignore the value of the LABEL setting and will display an automatically generated label.
30
XRIO Reference
4.4.15 LABEL
Descriptive label for the zone. Please see the section 4.4.14 MAN_LABEL for details on when this
label will be used.
4.4.15.1 INDEX
INDEX sets a unique index for all zones with the same TYPE and FAULTLOOP. This is necessary to
reassign relative shots to the different zones of different relays. It is recommended to number the
zones from inside to outside as usual (first zone number 1, second zone number 2...).
4.4.15.2 TYPE
Selects the type of the zone. The following values are possible:
The following different zone types are available:
• TRIPPING
• EXTENDED
• STARTING
• NONTRIPPING
Tripping zone Zone where the relay is supposed to trip in the specified time.
Extended zone It behaves exactly like normal tripping zones. The difference is that it is
possible to activate or deactivate all extended zones from a single setting
in the Distance module.
The software keeps no links between extended zones and tripping zones.
Thus, no automatic activation of an extended zone related to the
corresponding tripping zone or automatic deactivation of the tripping zone
if the corresponding extended zone is active is possible.
Starting zone This kind of zone cuts across all the tripping and extended zones. They
have an associated trip time, and trip is blocked outside of the zone.
Starting zones are always non-directional.
Non-tripping zone Do not have an associated trip time (and therefore no time tolerances).
They cut across all the tripping and extended zones. Non-tripping zones
are always non-directional.
Table 2: Types of Distance zones
4.4.15.3 FAULTLOOP
Selects the fault loop to which the zone applies. The following values are possible (grouped by type):
L1N L2N L3N One single Line-to-ground fault loop

LN Any Line-to-ground fault loop
L1L2 L2L3 L3L1 One single Line-to-line fault loop
L1L2L3 Three-phase faults
LL Any Line-to-line fault loop, including L1L2L3
ALL All fault loops
Table 3: Grouping of Fault Loops in Distance
31
4.4.15.4 TRIPTIME
The nominal trip time for the zone, in seconds.
4.4.15.5 TOLERANCES Block

This block contains the zone-specific tolerances, and the flags to indicate whether they apply. If a flag
is set to False, the corresponding tolerance in this block is not applied. Instead, the software will use
the appropriate tolerance from the DISTANCE.PROTECTIONDEVICE.TOLERANCES block.

TTPL_VALID Boolean TTOLPLUS is used Page 32
TTOLPLUS Real Positive time tolerance (absolute) Page 32
TTMI_VALID Boolean TTOLMINUS is used Page 32
TTOLMINUS Real Negative time tolerance (absolute) Page 32
TTRL_VALID Boolean TTOLREL is used Page 32
ZTRL_VALID Boolean ZTOLREL is used Page 33
ZTOLREL Real Relative impedance tolerance Page 33
ZTAB_VALID Boolean ZTOLABS is used Page 33
ZTOLABS Real Absolute impedance tolerance Page 33
4.4.15.5.1 TTPL_VALID
If True, the TTOLPLUS tolerance is taken from this block; if False, from the
DISTANCE.PROTECTIONDEVICE.TOLERANCES block.
4.4.15.5.2 TTOLPLUS
Positive time tolerance, in seconds.
4.4.15.5.3 TTMI_VALID
If True, the TTOLMINUS tolerance is taken from this block; if False, from the
4.4.15.5.4 TTOLMINUS
Negative time tolerance, in seconds.
4.4.15.5.5 TTRL_VALID
If True, the TTOLREL tolerance is taken from this block; if False, from the
4.4.15.5.6 TTOLREL
Relative time tolerance, in times percent.
32
XRIO Reference
4.4.15.5.7 ZTRL_VALID
If True, the ZTOLREL tolerance is taken from this block; if False, from the
4.4.15.5.8 ZTOLREL
Relative Z tolerance, in percent.
4.4.15.5.9 ZTAB_VALID
If True, the ZTOLABS tolerance is taken from this block; if False, from the
4.4.15.5.10 ZTOLABS
Absolute Z tolerance, in Ω.
4.4.15.6 MHOSHAPE Block

This block contains the necessary data to define a mho shape. See Figure 4 for the representation of
a mho shape.

ANGLE Real Angle of the mho shape Page 33
REACH Real Reach of the mho shape Page 33
OFFSET Real Offset of the mho shape Page 33
INVERT Boolean Allows inversion of the zone Page 33
4.4.15.6.1 ANGLE
The angle of the mho shape in degrees.
4.4.15.6.2 REACH
The reach of the mho shape in forward direction in Ohms.
4.4.15.6.3 OFFSET
The offset of the mho shape in backward direction in Ohms.
4.4.15.6.4 INVERT
The INVERT flag indicates which part of the Impedance Plane belongs to the zone. Normally (INVERT
= False) the inside of the circle delimited by the mho shape is the zone, and all the rest of the plane is
outside of the zone. If INVERT is True, the entire plane belongs to the zone except for the area inside
the mho shape.
33
4.4.15.7 LENSTOMATOSHAPE Block

This block contains the necessary data to define a lens/tomato shape. See Figure 5 for the
representation of a lens/tomato shape.

ANGLE Real Angle of the shape Page 34
REACH Real Reach of the shape Page 34
OFFSET Real Offset of the shape Page 34
SHAPE_MODE Enumeration Select which parameter will define the shape Page 34
WIDTH Real Width of the shape Page 34
RATIO_AB Real Ratio of segments A and B Page 34
4.4.15.7.1 ANGLE
The angle of the lens/tomato shape in degrees.
4.4.15.7.2 REACH
The reach of the lens/tomato shape in forward direction in Ohms.
4.4.15.7.3 OFFSET
The offset of the lens/tomato shape in backward direction in Ohms.
4.4.15.7.4 INVERT
The INVERT flag indicates which part of the Impedance Plane belongs to the zone. Normally (INVERT
= False) the inside of the lens/tomato shape is the zone, and all the rest of the plane is outside of the
zone. If INVERT is True, all the plane belongs to the zone except the area inside the lens/tomato
shape.
4.4.15.7.5 SHAPE_MODE
This parameter selects which parameter between WIDTH and RATIO_AB will be used to determine
the shape of the zone. Possible values for this setting are WIDTH and RATIO_AB.
4.4.15.7.6 WIDTH
The width of the lens/tomato shape in Ohms.
4.4.15.7.7 RATIO_AB
The ratio A/B of the lens/tomato shape.
34
XRIO Reference
4.4.15.8 GENERICSHAPE Block

This block contains the necessary data to define any shape from lines and arcs.

AUTOCLOSE Boolean Forces automatic closing of the zone Page 35
LINE Block One or more blocks describing the line(s) that Page 35
make up the shape.
ARC Block One or more blocks describing the arc(s) that Page 37
make up the shape.
4.4.15.9 INVERT
The INVERT flag indicates which part of the Impedance Plane belongs to the zone. Normally
(INVERT = False) the inside of a closed shape is the zone, and all the rest of the plane is outside of
the zone. If INVERT is True, the entire plane belongs to the zone except for the area inside the closed
shape.
For open shapes, the flag inverts the effect of the individual INSIDE parameters for each shape
element.
4.4.15.10 AUTOCLOSE
With the AUTOCLOSE flag, a shape can be made to be closed automatically. This is done by implicitly
setting the LEFT/RIGHT flag for the last border element so that the shape is closed. Additionally the
AUTOCLOSE flag sets the "inside" notion of the shape so that the inside of the closed shape is
INSIDE.
4.4.15.11 LINE Block

The LINE block describes a line in the characteristic. It is structured in the following way:

REFPOINT_TYPE Enumeration Selects how the reference point is defined Page 36
REFPOINT_R Real Real part of the Cartesian point coordinates Page 36
REFPOINT_X Real Imaginary part of the Cartesian point Page 37
coordinates
REFPOINT_MAG Real Magnitude of the Polar point coordinates Page 36
REFPOINT_ANGLE Real Angle of the Polar point coordinates Page 36
ANGLE Real Angle of the line with the X axis Page 36
INSIDE Enumeration Position of the zone relative to the line Page 36
35
4.4.15.11.1 REFPOINT_TYPE
Selects whether the Cartesian or the Polar coordinates of the Reference Point will be used. Possible
values for this parameter are CARTESIAN and POLAR.
4.4.15.11.2 REFPOINT_R
Real part of the Cartesian coordinates of the reference point.
4.4.15.11.3 REFPOINT_X
Imaginary part of the Cartesian coordinates of the reference point.
4.4.15.11.4 REFPOINT_MAG
Radial coordinate (distance) of the Polar coordinates of the reference point.
4.4.15.11.5 REFPOINT_ANGLE
Angular coordinate (angle) of the Polar coordinates of the reference point in degrees.
4.4.15.11.6 ANGLE
Line angle referred to the X-axis.
4.4.15.11.7 INSIDE
The inside flag for a border element (LINE or ARC) defines which part of the plane split by this border
element is considered inside the shape. By default, the left half-plane defined by the line is considered
inside, since it is supposed that the shape is constructed by the border elements in a counter-
clockwise direction. If the flag is set to RIGHT, it is the opposite. Instead of switching the flag, it would
be possible to change the angle of the line by 180° - this flag is simply a more convenient way of
achieving the same effect.
For auto-closed figures (AUTOCLOSE parameter is True) INSIDE will have no effect, since the rule
that the figure must be closed has precedence over the INSIDE settings of individual elements.
INSIDE is useful when AUTOCLOSE has not been selected.
Please note that GENERICSHAPE.INVERT exchanges inside and outside for the complete figure.
36
XRIO Reference
4.4.15.12 ARC Block

The ARC block describes an arc in the characteristic. It is structured in the following way:

REFPOINT_TYPE Enumeration Selects how the reference point is defined Page 37
REFPOINT_R Real Real part of the Cartesian point coordinates Page 37
REFPOINT_X Real Imaginary part of the Cartesian point Page 37
coordinates
REFPOINT_MAG Real Magnitude of the Polar point coordinates Page 37
REFPOINT_ANGLE Real Angle of the Polar point coordinates Page 37
RADIUS Real Radius of the arc Page 37
STARTANGLE Real Starting angle of the arc Page 37
ENDANGLE Real End angle of the arc Page 37
DIR Enumeration Rotational direction of the arc Page 38
INSIDE Enumeration Position of the zone relative to the arc Page 38
4.4.15.12.1 REFPOINT_TYPE
Selects whether the Cartesian or the Polar coordinates of the Reference Point will be used. Possible
values for this parameter are CARTESIAN and POLAR.
4.4.15.12.2 REFPOINT_R
Real part of the Cartesian coordinates of the reference point.
4.4.15.12.3 REFPOINT_X
Imaginary part of the Cartesian coordinates of the reference point.
4.4.15.12.4 REFPOINT_MAG
Radial coordinate (distance) of the Polar coordinates of the reference point.
4.4.15.12.5 REFPOINT_ANGLE
Angular coordinate (angle) of the Polar coordinates of the reference point.
4.4.15.12.6 RADIUS
Arc radius.
4.4.15.12.7 STARTANGLE
Starting angle of the arc in degrees.
4.4.15.12.8 ENDANGLE
Ending angle of the arc in degrees.
37
4.4.15.12.9 DIR
Rotational sense of the arc. This parameter selects between the two possible ways to go from
STARTANGLE to ENDANGLE. Possible values are CW (clockwise) and CCW (counterclockwise).
4.4.15.12.10 INSIDE
Possible values are LEFT and RIGHT. Please see section 4.4.15.11.7 in page 36.
38
XRIO Reference
5 CBCONFIGURATION Block
The CBCONFIGURATION block contains the settings for the CB Simulation and affects all the
modules that use it. This functionality was previously part of the DISTANCE module, but has been
moved into this independent block.
CB Simulation is now performed in the CMC 256 test set and its function is completely independent of
any test module. It is configured with the Circuit Breaker Configuration module, which can be inserted
in Control Center test plans. The timing parameters of CB Simulation are stored in the XRIO file so
they are part of the data of a specific relay.
The CBCONFIGURATION block is composed of the following parameters:

TRIPTIME Real Opening time of the breaker Page 39
CLOSETIME Real Closing time of the breaker Page 39
P52AB Real Percentage for the operation of the 52a/52b signals Page 39
5.1 TRIPTIME
The delay time between the start of the relay's Trip command until the breaker opens. This time is in
seconds.
5.2 CLOSETIME
The delay time between the start of the relay's Close command until the breaker closes. This time is in
seconds.
5.3 P52AB
Percentage of the maneuver time at which the 52a and 52b outputs change configuration. If this
setting were 100%, then the outputs would not change until the maneuver is fully completed.
39
6 VISTARTING Block
The VISTARTING block contains the settings for the VI-Starting module. This module is designed to
verify the characteristic of a voltage-dependent Overcurrent starting function (VI-Starting function),
The VISTARTING block is composed of the following parameters:

ITOL Real Current tolerance Page 40
VTOL Real Voltage tolerance Page 40
CHARVIS Block VI characteristic Page 40
6.1 ITOL
Specifies the relative tolerance for the test current threshold, in percent.
6.2 VTOL
Specifies the relative tolerance for the test voltage threshold, in percent.
6.3 CHARVIS
Describes the characteristic. The block is structured as follows:

IG Real First pick-up current Page 40
IGG Real Second pick-up current Page 40
VLNIG Real Voltage to IG for line-neutral faults Page 41
VLNIGG Real Voltage to IGG for line-neutral faults Page 41
VLLIG Real Voltage to IG for line-line faults Page 41
VLLIGG Real Voltage to IGG for line-line faults Page 41
6.3.1 IG
Defines the first pick-up current threshold (I> stage).
6.3.2 IGG
Defines the second pick-up current threshold (I>> stage).
40
XRIO Reference
6.3.3 VLNIG
Defines the voltage threshold of the I> stage for line-neutral faults.
6.3.4 VLNIGG
Defines the voltage threshold of the I>> stage for line-neutral faults.
6.3.5 VLLIG
Defines the voltage threshold of the I> stage for line- line faults.
6.3.6 VLLIGG
Defines the voltage threshold of the I>> stage for line-line faults.
41
7 SYNCHRO Block
The SYNCHRO block contains the parameters for the Synchronizer module.
Synchronization relays are used to assist:
• connecting a generator to the network or power grid;

• re-establishing the connection between two parts of the network;
• manually closing breakers, and
• performing a synchronism check.
Synchronizing relays are designed to measure two voltages with respect to phase angle, frequency,
and magnitude to safeguard against the interconnection of two unsynchronized systems.
Synchronizing relays are also used in switching operations to link two parts of a system that are
already synchronously connected via other paths in the system. Autoreclose is a good example of
such a switching operation.
The structure of the SYNCHRO Block is as follows:

TG_PHASE_SHIFT Real Phase shift from transformer Page 43
STARTING Enumeration Type of starting signal Page 43
PHASE_SEQUENCE1 Enumeration System 1 rotation sense Page 43
PHASE_SYSTEM1 Enumeration System 1 voltages used for synchronization Page 43
PHASE_SEQUENCE2 Enumeration System 2 rotation sense Page 43
PHASE_SYSTEM2 Enumeration System 2 voltages used for synchronization Page 44
USE_RATIO_SYS1 Boolean Flag for separate ratio of nominal voltage for Page 44
system 2
VNOM_SEC_SYS2 Real Nominal secondary L-L voltage system 2 Page 44
CHARSYNC Block Synchronizing characteristic Page 45
42
XRIO Reference
7.1 TG_PHASE_SHIFT
This value defines the phase shift (if any) coming from an optional block or coupling transformer. This
value is given in degrees.
7.2 STARTING
Defines the type of start signal to be applied to the test object after the pre-synchronization time. The
following table describes the effect of each of the possible values of the setting:
Value Effect
PULSE A 50 ms start pulse is output at the same time that the maximum
synchronization time starts
CONTINUOUS The start signal is active during the maximum synchronization and post
synchronization times.
NONE No signal is applied
This setting also defines the type of release signal to be applied either at the end of the maximum
synchronization time (test failed) or at the end of the post-synchronization time (test passed).
7.3 PHASE_SEQUENCE1
This setting describes the direction of the phase rotation in the System 1. Possible values are L1L2L3
and L1L3L2.
7.4 PHASE_SYSTEM1
The phase or phases from the system to use for synchronization and whether they are Wye or Delta.
Systems 1 and 2 must be configured either both as Wye or both as Delta. When testing Wye, you can
configure any combination of line-to-neutral voltages going from System 1 to System 2. Likewise when
testing Delta, you can configure any combination of line-to-line going from System 1 to System 2.
Possible values for this setting are L1N, L2N, L3N, L1L2, L2L3, L3L1, L1L3, L3L2, L2L1, L1L2L3,
L1L3L2, L12L23L31 and L13L32L21.
7.5 PHASE_SEQUENCE2
This setting describes the direction of the phase rotation in the System 2. Possible values are L1L2L3
and L1L3L2.
43
7.6 PHASE_SYSTEM2
The phase or phases from the system to use for synchronization and whether they are Wye or Delta.
Systems 1 and 2 must be configured either both as Wye or both as Delta. When testing Wye, you can
configure any combination of line-to-neutral voltages going from System 1 to System 2. Likewise when
testing Delta, you can configure any combination of line-to-line going from System 1 to System 2.
Possible values for this setting are L1N, L2N, L3N, L1L2, L2L3, L3L1, L1L3, L3L2, L2L1, L1L2L3,
L1L3L2, L12L23L31 and L13L32L21.
7.7 USE_RATIO_SYS1
This setting allows for cases in which the test object is fed with voltages from two voltage transformers
having different ratios. If the setting is False, a value can be set for Vnom (secondary) of system 2 in
the VNOM_SEC_SYS2 setting. When the setting is True, both systems function as if the transformers
feeding the test object would have the same ratio Vprim/Vsec. The VNOM_SEC_SYS2 setting is then
ignored.
7.8 VNOM_SEC_SYS2
If the secondary voltage of System 2 is different from that of System 1, it is possible to enter the
System 2 voltage in this parameter.
Depending on the phase system setting made at "Connected voltage", this voltage is either the phase-
phase or the phase-neutral voltage: for L1-L2, L2-L3 and L3-L1 phase systems the system voltage to
be set is the phase-phase voltage, while for L1-E, L2-E, L3-E and L1-L2-L3 phase systems the system
voltage to be set is the phase-neutral voltage.
If the secondary voltage of system 2 is different from the one of system 1, Synchronizer operates in
relative mode and the output of system 2 is calculated accordingly.
44
XRIO Reference
7.9 CHARSYNC Block

This block describes the synchronizing characteristic. The structure of the block is as follows:

D_VMAX Real Maximal voltage difference Page 45
D_VMIN Real Minimum voltage difference Page 45
VTOLABS Real Absolute tolerance for D-Vmin and D-Vmax Page 45
VTOLREL Real Relative tolerance for D-Vmin and D-max Page 46
D_FMAX Real Maximal frequency difference Page 46
D_FMIN Real Minimum frequency difference Page 46
FTOLABS Real Absolute tolerance for frequency difference Page 46
FTOLREL Real Relative tolerance for frequency difference Page 46
D_PHASEANGLE Real Maximal phase difference Page 46
PHASEANGLE_TOLABS Real Absolute tolerance of phase difference Page 46
PHASEANGLE_TOLREL Real Relative tolerance of phase difference Page 46
INNER_LIMIT Real Inner limit of the dead zone Page 47
OUTER_LIMIT Real Outer limit of the dead zone Page 47
MIN_SYNC_TIME Real Minimum synchronization time Page 47
MIN_SYNC_TIME_TOL Real Minimum synchronization time tolerance Page 47
7.9.1 D_VMAX
System 1 and System 2 are required to have approximately the same voltage at the moment of
synchronism and actual CB closure.
A maximum overvoltage (D_VMAX) and undervoltage (D_VMIN) can be entered for the difference in
System 1 and System 2 voltages. In addition, the over- and undervoltages can have a tolerance. The
tolerances can be entered either as an absolute value (VTOLABS) in volts or as a percentage of the
(DV) value (VTOLREL). For any given voltage, both tolerances are calculated and the larger of the two
is used.
7.9.2 D_VMIN
Maximum undervoltage. See 7.9.1 for details.
7.9.3 VTOLABS
Absolute voltage tolerance. See 7.9.1 for details.
45
7.9.4 VTOLREL
Relative voltage tolerance. See 7.9.1 for details.
7.9.5 D_FMAX
System 1 and System 2 are required to have the same frequency at the moment of synchronism and
actual CB closure.
A maximum oversynchronous (D_FMAX) and subsynchronous (D_FMIN) value can be entered for the
difference in System 1 and System 2 frequencies. In addition, these frequencies can have a tolerance.
The tolerances can be entered either as an absolute value (FTOLABS) in volts or as a percentage of
the (DF) value (FTOLREL). For any given frequency, both tolerances are calculated and the larger of
the two is used.
7.9.6 D_FMIN
Maximum subsynchronous value. See 7.9.5 for details.
7.9.7 FTOLABS
Absolute frequency tolerance. See 7.9.5 for details.
7.9.8 FTOLREL
Relative frequency tolerance. See 7.9.5 for details.
7.9.9 D_PHASEANGLE
System 1 and System 2 are required to be in phase after taking into consideration any CB closure
delays and coupling transformer phase shifts.
The maximum difference in phase angle between System 1 and System 2 at the moment of
synchronism and actual CB closure can be set to +/-360 degrees.
In addition, the phase difference can have a tolerance. The tolerances can be entered as either an
absolute value in degrees (PHASEANGLE_TOLABS) or as a percentage of the value
(PHASEANGLE_TOLREL) . For any given angle, both tolerances are calculated and the larger of the
two is used.
7.9.10 PHASEANGLE_TOLABS
Absolute phase tolerance. See 7.9.9 for details.
7.9.11 PHASEANGLE_TOLREL
Relative phase tolerance. See 7.9.9 for details.
46
XRIO Reference
7.9.12 INNER_LIMIT
Generally, the synchronizing relay controls one of the systems (e.g., a generator) in order to get it to
match the reference system in terms of voltage, phase, and frequency. The control signals are V> and
V< for raising and lowering the output voltage and f> and f< for raising and lowering the output
frequency.
The Dead Zones are areas where the synchronizing relay is not allowed to output any adjustment
control commands.
The Dead Zones are defined by OUTER_LIMIT and INNER_LIMIT. The Synchronizer Test Module
verifies that the entered values are within the upper and lower limits for oversynchronous and
subsynchronous operation.
7.9.13 OUTER_LIMIT
Outer limit of the dead zone. See 7.9.12 for details.
7.9.14 MIN_SYNC_TIME
Some synchronization relays only release the CB close command if the synchronization conditions
(DV, Df, DPhi) are met for a certain time. This minimum synchronization time can be defined here. If
defined, the minimum synchronization time is considered for the calculation of the expected nominal
response of the relay.
The minimum synchronization time is entered in seconds, the tolerance for the synchronization time
(MIN_SYNC_TIME_TOL) is entered as a percentage of the time.
7.9.15 MIN_SYNC_TIME_TOL
Relative tolerance for the minimum synchronization time. See 7.9.14 for details.
47
8 DIFFERENTIAL Block
This block contains the settings for Differential protection.
The DIFFERENTIAL block is structured in the following way:

WINDING_COUNT Integer Number of Windings Page 48
REF_WINDING String Defines the reference winding Page 48
OBJECT_TYPE Enumeration Type of protected object Page 49
ITOL_REL Real Relative current tolerance Page 49
ITOL_ABS Real Absolute current tolerance Page 49
TTOL_REL Real Relative time tolerance Page 49
TTOL_ABS Real Absolute time tolerance Page 49
TREF Enumeration Time reference for the shot (Obsolete) Page 8.8
TRET Real Reset (delay) time of device Page 49
TMAX Real Maximum test time Page 49
IREF Enumeration Reference for the normalization of currents Page 49
USECT Boolean Use ground current measurements inputs (CT) Page 50
DELTACT Boolean Activates compensation for delta-connected CTs Page 50
WINDING Block Describes an individual winding Page 50
DIFFBIAS Block Other settings, including operating Page 52
characteristics
8.1 WINDING_COUNT
The number of windings in the protected object. Possible values for this setting are 2 and 3.
If the OBJECT_TYPE is not TRANSFORMER, this setting may only be 2.
8.2 REF_WINDING
This setting is used to select the reference winding for fault calculations. It must contain a string equal
to the name of one of the existing windings (DIFFERENTIAL.WINDING.NAME).
48
XRIO Reference
8.3 OBJECT_TYPE
The type of the protected object. Possible values for this setting are TRANSFORMER, GENERATOR,
BUSBAR and MOTOR.
8.4 ITOL_REL
Relative current tolerance, in percent.
8.5 ITOL_ABS
Absolute current tolerance, in times the nominal current.
8.6 TTOL_REL
Relative time tolerance, in percent.
8.7 TTOL_ABS
Absolute time tolerance, in seconds.
8.8 TREF
This setting is obsolete and has no effect.
8.9 TRET
Reset or delay time. This time will be kept after every Differential shot to allow the protection device to
reset.
8.10 TMAX
Maximum fault time. If a trip is not detected during this time, the software will consider that the relay
has not tripped.
8.11 IREF
Reference for the normalization of currents. The possible values for this setting are INOM_PRO
(normalize using the protected object nominal current) and INOM_CT (normalize using the nominal
T
current of the CT).
49
8.12 USECT
True if the protected object uses CT grounding transformers, False otherwise.
CONVRELAY (?? optional in XRIO)

True if the transformer model should be deactivated, otherwise False.
8.13 DELTACT
Selects whether the compensation for Delta-connected CTs is activated.
8.14 WINDING
The WINDING block contains the parameters that define an individual winding. The number of
WINDING sub-blocks in the DIFFERENTIAL block must be equal to the number set in the
DIFFERENTIAL.WINDING_COUNT setting.
Please note that the Differential modules use the transformer ratios in this block rather than those in
the DEVICE block for calculation of the currents.
Each WINDING block is structured in the following way:

NAME String Winding/Leg Name Page 51
INULL_ELIMINATION Enumeration Zero sequence elimination method Page 51
CONNECTION Enumeration Bay Connection Page 51
CONNECTIONNUMBER Integer Connection number Page 51
NOM_PD_PH Real Nominal Current of the CT Page 51
NOM_CT_PH Real Nominal primary current of the CT Page 51
GROUNDING_CT_PH Enumeration Grounding of the CT star point Page 51
NOM_PD_N Real Ground CT nominal current Page 51
NOM_CT_N Real Ground CT nominal primary current Page 51
GROUNDING_CT_N Enumeration Grounding of the Ground CT star point Page 51
VN Real Nominal voltage of the winding Page 52
SN Real Nominal power of the winding Page 52
GROUNDING_TRF Boolean Star point is grounded Page 52
TAP_SETTING Real Divisor for the output currents Page 52
DELTA_CONN_CT Boolean Activates compensation for delta-connected Page 52
CTs
50
XRIO Reference
8.14.1 NAME
The name of the winding.
8.14.2 INULL_ELIMINATION
Method for the elimination of I0. The following values are possible:
Value Meaning
NONE No elimination method is used
IL_I0 Line current – Zero sequence current
YD YD interposing transformer
YDY YDY interposing transformer
8.14.3 CONNECTION
The connection of the winding. Possible values are Y (Wye), D (Delta) and Z.
8.14.4 CONNECTIONNUMBER
Connection number of the winding, from 0 to 11. Please note that not all connection numbers are
compatible with all the possible CONNECTION values.
8.14.5 NOM_PD_PH
The nominal current of the protection device current transformer.
8.14.6 NOM_CT_PH
The nominal primary current of the protection device current transformer.
8.14.7 GROUNDING_CT_PH
The star point grounding of the CT. Possible values can be BUS (toward busbar) or TRANSFORMER
(toward protected object).
8.14.8 NOM_PD_N
The nominal current of the ground CT.
8.14.9 NOM_CT_N
The nominal primary current of the ground CT.
8.14.10 GROUNDING_CT_N
The star point grounding of the ground CT. Possible values can be BUS (toward busbar) or
TRANSFORMER (toward protected object).
51
8.14.11 VN
The nominal voltage of the winding, in V.
8.14.12 SN
The nominal power of the winding, in VA.
8.14.13 GROUNDING_TRF
Indicates whether the star point of the CT is grounded.
8.14.14 TAP_SETTING
Divisor for the output currents of this winding.
8.14.15 DELTA_CONN_CT
If True, this setting enables compensation of Delta-connected CTs.
8.15 DIFFBIAS
The DIFFBIAS block is structured in the following way:

ACTIVE Boolean Active flag (Obsolete) Page 52
DIFF Block Tripping units limits Page 52
BIAS Block Ibias-related definitions and harmonic settings Page 53
TRIPCHAR Block Defines the operating characteristic Page 54
8.15.1 ACTIVE
This parameter is obsolete and has no effect.
8.15.2 DIFF Block

IDIFFGG Real Higher differential (I>>) current Page 53
TDIFFGG Real Higher differential (I>>) trip time Page 53
IDIFFG Real Differential (I>) current Page 53
TDIFFG Real Differential (I>) trip time Page 53
52
XRIO Reference
8.15.2.1 IDIFFGG
The setting for the Idiff>> unit in times the nominal current (DEVICE.NOMINALVALUES.INOM).
8.15.2.2 TDIFFGG
Nominal trip time for the Idiff>> unit, in seconds.
8.15.2.3 IDIFFG
The setting for the Idiff> unit in times the nominal current (DEVICE.NOMINALVALUES.INOM).
8.15.2.4 TDIFFG
Nominal trip time for the Idiff> unit, in seconds.
8.15.3 BIAS Block

DEFBIAS Enumeration Ibias calculation formula Page 53
BIASDIVISOR Real Divisor for the Ibias calculation formula Page 53
TOLHARM_ABS Real Absolute harmonic tolerance Page 54
TOLHARM_REL Real Relative harmonic tolerance Page 54
CHARHARM Block Harmonic characteristic Page 54
8.15.3.1 DEFBIAS
This setting selects the formula that will be used for the calculation of Ibias. The following values are
possible:
Value Formula
IPIS_SUM_ABS Ibias = (|Ip|+|Is|)/K1
IPIS_SUM Ibias = (Ip+Is)/K1
IPIS_SUM_ABS_K2 Ibias = (|Ip|+|Is|*K2)/K1
IPIS_MAX Ibias = max(Ip,Is)
IPIS_MIN Ibias = min(Ip,Is)
IPIS_SQRT Ibias = sqrt(Ip*Is*cos(a))
Table 4: Methods of Ibias calculation

In these formulas, K1 is the programmable divisor, that is, the value of the BIASDIVISOR setting.
53
8.15.3.2 BIASDIVISOR
The K1 divisor for the Ibias calculation formulas.
8.15.3.3 TOLHARM_ABS
Absolute tolerance for the harmonic restraint function.
8.15.3.4 TOLHARM_REL
Relative tolerance for the harmonic restraint function, in percent.
8.15.3.5 CHARHARM
The BIAS block may contain any number of CHARHARM blocks. Each block describes the restraint
characteristic for a single harmonic. It is possible for the number of CHARHARM block in BIAS to be
zero. Each CHARHARM has the following structure:

ORDERHARM Integer Order of the harmonic to which the characteristic applies Page 54
DELAYHARM Real Delay time for the harmonic (Obsolete) Page 54
CHARTABLE Block Point table that defines the characteristic Page 54
8.15.3.5.1 ORDERHARM
The order of the harmonic, starting at 2.
8.15.3.5.2 DELAYHARM
This setting is obsolete and has no effect.
8.15.3.5.3 CHARTABLE
The CHARTABLE contains any number of POINT sub-blocks, with a minimum of 2. These points
define the harmonic restraint characteristic. See 8.15.4.1 for the definition of the POINT block.
8.15.4 TRIPCHAR
The TRIPCHAR block contains the operating characteristic of the differential protection. It is composed
of any number of POINT sub-blocks, with a minimum of 2. These points define the harmonic restraint
characteristic.
8.15.4.1 POINT
The POINT block is structured as follows:
ID Type Description
X Real X coordinate of the point
Y Real Y coordinate of the point
54
XRIO Reference
9 OVERCURRENT Block
The OVERCURRENT block holds the settings for the Overcurrent function. It is structured as follows:

DISPLAY_ABSOLUTE Boolean Display absolute or relative currents Page
(Obsolete)
ITOLREL Real Relative current tolerance Page 55
ITOLABS Real Absolute current tolerance Page 55
TTOLABS Real Absolute time tolerance Page 56
PTCONN Enumeration The connection of the voltage transformer Page 56
CTSTARPOINT Enumeration The grounding of the current transformer star Page 56
point
DIRECTIONAL Enumeration Overcurrent function under test is directional Page 56
AUTORESET Boolean Use the automatic calculation of the Reset Page 56
time
GROUPLN Block Line-to-Neutral protection group Page 57
GROUPLL Block Line-to-Line protection group Page 57
GROUPI2 Block Negative sequence protection group Page 57
GROUPI0 Block Zero sequence protection group Page 57
9.1 DISPLAY_ABSOLUTE
This parameter is obsolete and has no effect.
9.2 ITOLREL
Relative current tolerance, in percent.
9.3 ITOLABS
Absolute current tolerance, in times the nominal current.
9.4 TTOLREL
Relative time tolerance, in percent.
55
9.5 TTOLABS
Absolute time tolerance, in seconds.
9.6 PTCONN
This parameter controls the connection of the power (voltage) transformer. There are two possible
values: BUS (direction busbar) and LINE (direction line).
9.7 CTSTARPOINT
currents are rotated by 180° before being sent to the relay
9.8 DIRECTIONAL
Defines whether the Overcurrent unit under test is directional. In the case of the Overcurrent unit,
voltages will be turned on to test directional units, but no test of the directional behavior itself will be
performed.
9.9 AUTORESET
W hen True, the reset time for each shot is calculated automatically from the characteristic's
parameters. W hen False, the times set in the test module are used.
56
XRIO Reference
9.10 Groups
An Overcurrent group describes the behavior of the Overcurrent functions for one or more fault loops.
The appropriate group is selected automatically according to the fault loop set in the Overcurrent test
module. Each group is defined independently, and will be stored in the XRIO file even if it is not used
for the test.
All groups must be present in the XRIO file, whether or not they are used for the test. There are four
Overcurrent groups, as follows:
Group XRIO ID Name Fault loops

Line-to-Neutral GROUPLN LN L1N, L2N, L3N
Line-to-line GROUPLL LL L1L2, L2L3, L3L1, L1L2L3
Negative sequence GROUPI2 I2 I2
Zero sequence GROUPI0 I0 3I0
Table 5: Overcurrent protection groups

Therefore, there must be four and only four GROUP sub-blocks in the OVERCURRENT block. All
groups share the same structure and parameters.
The structure of a group block is as follows:

NAME String Name of the group Page 57
RESET_RATIO Real Nominal Dropout / Pickup ratio Page 57
UNIT Block Each of the Overcurrent protective units Page 58
9.10.1 NAME
The NAME string identifies the group. It must be one of the following strings: LN, LL, I2 or I0. Each
group must have a specific Name depending on the XRIO ID, as seen in the table in section 9.10 .
9.10.2 RESET_RATIO
The ratio is defined as the Reset value divided by the Pickup value.
The Reset or Dropout value is the value of the current for which a unit that has tripped goes back to
the non-tripped state.
The Pickup value is the value of the current for which an inactive protection unit becomes active or
started.
57
9.10.3 UNIT
The UNIT block contains the settings for an individual Overcurrent unit. The number of UNIT sub-
blocks in the GROUP block must be equal to the number of possible units, whether they are actually
used in the test or not. Currently, the number of units in a group is three (I>, I>> and I>>>). Therefore,
there will be three and only three UNIT blocks in each GROUP.
The I> unit may have any operating characteristic, the I>> and I>> may only have Definite Time
characteristics. All the data in the Group that has to do with the characteristic refers only to the I> unit.
The UNIT block is structured as follows:

NAME String Name of the unit Page 58
ACTIVE Boolean Determines whether or not the unit is active Page 58
IPICKUP Real Starting value for the unit Page 58
TINDEX Real Time index Page 58
CHARTYPE Enumeration Type of the operating characteristic for I> Page 59
PREDEFCHAR Enumeration Determines the type of predefined characteristic, Page 60
if applicable
Characteristic Block Non-predefined char, if applicable Page 61
9.10.3.1 NAME
The name of the unit. It must be one of the following: IG, IGG or IGGG.
9.10.3.2 ACTIVE
If the unit is not active, it will not be considered when the module calculates the expected behavior of
the relay.
9.10.3.3 IPICKUP
Pickup value of the unit, in times the nominal current.
9.10.3.4 TINDEX
Time index. For Definite Time characteristics, this will be the nominal operating time of the unit. For
curve characteristics, this value is a factor that, when multiplied by the trip time obtained from the
characteristic for a given operating current, will give us the nominal operating time.
For example, let's suppose that the characteristic is set to IEC Normal Inverse, TINDEX is 0.5 and the
operating current is 3 times the Ipickup of the I> unit. The IEC Normal Inverse equation will return an
operating time of 6.3019 s for that current. Therefore, the nominal trip time for the test will be
6.3019 x 0.5 = 3.1510 s.
58
XRIO Reference
9.10.3.5 CHARTYPE
This Enumeration setting defines the type of the characteristic. Different types of characteristics have
different equations. The types supported by the software are:
Type Description
PREDEFINED One of the characteristics that are predefined in the Overcurrent Test Object.
When the type is PREDEFINED, the PREDEFCHAR setting is used to specify
the exact characteristic used.
2
I2T The I t characteristic is defined by the following equation:
MP
t = A ⋅ D ⋅ ln P
M −Q
⎛ I ⎞
where M = ⎜⎜ T ⎟⎟
⎝ IS ⋅ In ⎠
t is the nominal operating time in seconds, D is the time dial (TINDEX) and A, P
and Q are user-defined parameters.
IAC This is the characteristic of the GE IAC – type relays. Its equation is:
⎡ B D E ⎤
t = Td ⋅ ⎢ A + + + 3⎥
⎣ M − C (M − C ) (M − C ) ⎦
2
⎛ I ⎞
where M = ⎜⎜ T ⎟⎟
⎝ IS ⋅ In ⎠
t is the operating time in seconds, Td is the time dial (TINDEX) and A, B, C, D

and E are user-defined parameters.
INVERSE Generic inverse characteristic. Its equation is based on the IEEE Standard
Equation, with two additional coefficients (K1 and K2) that offer extra flexibility:
A ⋅ D + K1
t= P
+ B⋅ D + K2
⎛ IT ⎞
⎜⎜ ⎟⎟ − Q
⎝ IS ⋅ In ⎠
where t is the nominal operating time in seconds, D is the time dial (TINDEX)
and A, B, P, Q, K1 and K2 are user-defined parameters.
USERDEFINED Defined by the used by means of a current / time point table.
Table 6: Overcurrent editable characteristics
59
It is important to note that the value of this setting determines which type of characteristic block will be
included in the UNIT block, if any. Of the possible CHAR, CHARI2T, CHARIAC and TABLE blocks,
only one of them may be present; which one it will be is determined by the value of CHARTYPE, with
the following correspondence:
CHARTYPE Type of characteristic block present

PREDEFINED No characteristic block is present
I2T CHARI2T
IAC CHARIAC
INVERSE CHAR
USERDEFINED TABLE
9.10.3.6 PREDEFCHAR
This setting is effective only when CHARTYPE is set to PREDEFINED. The possible values of the
setting are:
Type Description
DEFTIME Definite time characteristic.
INVERSE IEC Normal Inverse. It uses the INVERSE equation (9.10.3.5 ) with the
following values for the coefficients:
A = 0.14
P = 0.02
Q=1
B, K1 and K2 are zero
VERY_INVERSE IEC Very Inverse. It uses the INVERSE equation (9.10.3.5 ) with the
A = 13.5
P=1
Q=1
EXTR_INVERSE IEC Extremely Inverse. It uses the INVERSE equation (9.10.3.5 ) with the
A = 80
P=2
Q=1
Table 7: Overcurrent predefined characteristics

Predefined characteristics are fixed and cannot be modified. The software will ignore the values in the
CHAR block if a predefined characteristic is selected.
60
XRIO Reference
9.10.3.7 CHAR block

Present in the UNIT block when CHARTYPE is set to INVERSE, the CHAR block describes the
INVERSE characteristic type (see Table 6 for details).
The CHAR block is structured as follows:
ID Type Description
NAME String Name of the characteristic. It can be any string.
A Real Parameter A of the INVERSE equation (see Table 6)
B Real Parameter B of the INVERSE equation (see Table 6)
P Real Parameter P of the INVERSE equation (see Table 6)
Q Real Parameter Q of the INVERSE equation (see Table 6)
K1 Real Parameter K1 of the INVERSE equation (see Table 6)
K2 Real Parameter K2 of the INVERSE equation (see Table 6)
AUTORESR Real R parameter of the INVERSE auto-reset equation
AUTOREST Real T parameter of the INVERSE auto-reset equation
The A, B, P, Q, K1 and K2 parameters are fed directly into the INVERSE equation.
The INVERSE auto-reset equation is the following:
R ⋅ Td
tr =
1− M T
where:
tr Reset time in seconds

Td Time dial (TINDEX)
R AUTORESR parameter
T AUTOREST parameter
M Post-fault current in times the pickup current
61
9.10.3.8 CHARIAC block

Present in the UNIT block when CHARTYPE is set to IAC, the CHARIAC block describes the IAC
characteristic type (see Table 6 for details).
The CHARIAC block is structured as follows:
ID Type Description
A Real Parameter A of the IAC equation (see Table 6)
B Real Parameter B of the IAC equation (see Table 6)
C Real Parameter C of the IAC equation (see Table 6)
D Real Parameter D of the IAC equation (see Table 6)
E Real Parameter E of the IAC equation (see Table 6)
AUTORESR Real R parameter of the IAC auto-reset equation
AUTOREST Real T parameter of the IAC auto-reset equation
The A, B, C, D and E parameters are fed directly into the IAC equation.
The IAC auto-reset equation is the following:
R ⋅ Td
tr =
1− M T
where:
tr Reset time in seconds

Td Time dial (TINDEX)
R AUTORESR parameter
T AUTOREST parameter
M Post-fault current in times the pickup current
62
XRIO Reference
9.10.3.9 CHARI2T block

Present in the UNIT block when CHARTYPE is set to I2T, the CHAR block describes the I2T
characteristic type (see Table 6 for details).
The CHARI2T block is structured as follows:
ID Type Description
A Real Parameter A of the I2T equation (see Table 6)
P Real Parameter P of the I2T equation (see Table 6)
Q Real Parameter Q of the I2T equation (see Table 6)
The A, P and Q parameters are fed directly into the I2T equation.
The I2T characteristic does not support the auto-reset feature.
9.10.3.10 TABLE block

Present in the UNIT block when CHARTYPE is set to USERDEFINED, the TABLE block describes the
user-defined characteristic.
The TABLE block has a NAME parameter, which can be any string, and any number of POINT sub-
blocks. The POINT blocks define the shape of the characteristic in the current / time plane.
The POINT blocks must be in sorted by growing currents and decreasing times. This means, that each
point must have equal or greater current and equal or smaller time than the preceding POINT. The first
POINT may be anywhere in the plane. The program will perform linear interpolation between points,
so it is up to the user to provide a sufficient number of points to obtain a smooth characteristic. The
first and last segments will be prolonged to infinity.
9.10.3.10.1 POINT
The POINT block is structured as follows:
ID Type Description
X Real X coordinate of the point (current in times the pickup
value of the I> unit)
Y Real Y coordinate of the point (operating time)
63
10 METER Block
The METER block describes a metering function. The device under test (meter) may be single-
function or multifunctional, may measure energy or other quantities. The structure of the METER block
is as follows:

TYPE Enumeration Type of meter Page 64
SINGLEPHASE Boolean Controls whether the test is single-phase Page 65
GATED_MECHANISM Boolean Special mechanism test desired Page 65
THREEWIRE Boolean Meter is 3-wire Page 65
DIRECTION Enumeration Energy direction Page 65
EXPORTDIR Enumeration Defines which direction is considered Page 65
"Exporting"
QUADRANT Enumeration Meter quadrant Page 65
PULSE_TYPE Enumeration Flank of the meter pulse for measurement Page 66
CERTIFIED Strings Declaration of certification Page 66
CLASS Real Meter class Page 66
PULSES_PER_REV Integer Pulses per rotation Page 66
SETTLING Real Settling time for the meter Page 66
CONSTANT Real Meter constant Page 66
10.1 TYPE
Defines the type of the meter. In case of single-functional meters, the metering function is predefined
and cannot be changed. Multifunctional meters may test any number of functions, to be selected in the
Test Module. The possible values for this setting are:
Value Meter type

W_H Active power meter (Watt hour)
Q_H Q hour meter
VAR_H Reactive power meter (var hour)
VA_H Apparent power meter (VA hour)
2
V2_H Voltage squared hour meter (V h)
V_H Voltage hour meter
2
I2_H Current squared hour meter (I h)
I_H Current hour meter
Multifunctional Any combination of the above, selectable in the test module
Table 8: Meter types
64
XRIO Reference
10.2 SINGLEPHASE
When True, testing of single-phase meters and single-phase testing of three-phase meters will be
enabled.
10.3 GATED_MECHANISM
When True, the Mechanism test in the Meter module will use a binary input to signal different test
stages.
10.4 THREEWIRE
Allows choosing between 3-phase 4-wire meters (False) and 3-phase 3-wire meters (True).
10.5 DIRECTION
Specifies the energy direction that the meter will measure. This setting applies only if the meter type
(TYPE) was either W_H or VAR_H. The possible values for this setting are:
Value Meter behavior
EXPORTING The meter will measure energy in the Exporting direction only
IMPORTING The meter will measure energy in the Importing direction only
BIDIRECTIONAL The meter will measure energy in either direction
Table 9: Energy directions
10.6 EXPORTDIR
Selects which direction is considered Exporting and which is Importing. The possible values for this
setting are:
Value Definition
POSITIVE Power flowing from generator to consumer is "Exporting"
NEGATIVE Power flowing from consumer to generator is "Exporting"
Table 10: Definitions of Exporting
10.7 QUADRANT
Specifies the quadrant in which the meter will measure. This setting applies only if an apparent power
meter (VA_H) was selected in TYPE. The possible values for this setting are:
Value Meter behavior
Q1 The meter will measure energy in the first quadrant only
Q2 The meter will measure energy in the second quadrant only
Q3 The meter will measure energy in the third quadrant only
Q4 The meter will measure energy in the fourth quadrant only
Q_ALL The meter will measure energy in all quadrants
Table 11: Quadrants
65
10.8 PULSE_TYPE
This setting selects which of the edges of the meter pulse will be considered the "Pulse" that the meter
module will use. If the value of the setting is RISING, the leading edge of the pulse is used; if the value
is FALLING, the trailing edge of the pulse will be used.
10.9 CERTIFIED
This string has no influence in the test, but it will appear in the report. It is possible to assign any value
to the string.
10.10 CLASS
The class of the meter. This value will be used by the module to provide a default value for the test
tolerances.
10.11 PULSES_PER_REV
Number of pulses the meter will emit during a complete revolution of the meter disk.
10.12 SETTLING
Settling time of the meter in seconds. This time should be sufficient for the meter to stabilize and
measure correctly after a change in the input magnitudes.
10.13 CONSTANT
The meter constant, in Pulses per Quantity. The meaning of Quantity depends on the metering
function; for example, for a Watt hour meter, the value of CONSTANT is in Pulses per kWh.
66
XRIO Reference
11 TRANSDUCER Block
The TRANSDUCER block holds the settings for testing Measurement Transducers. The structure of
the block is the following:

TRDCR_OUT Enumeration Type of transducer output Page 67
ANGLE_REF Enumeration Selects the reference for angles Page 67
ERROR_REF Enumeration Method for the calculation of errors Page 68
SETTLING Real Settling time of the transducer Page 68
CTSTARPOINT Enumeration The grounding of the current transformer star point Page 68
FUNCTION Block One or more transducer function blocks Page 68
11.1 TRDCR_OUT
This setting selects the type of transducer output. Its possible values are the following:
Value Type of output

CURRENT Output is DC current in the 0… ± 20 mA range
VOLTAGE Output is DC voltage in the 0… ± 10 V range
OPEN_LOOP The user must enter transducer readings manually
Table 12: Types of Transducer output
11.2 ANGLE_REF
This setting reflects the method used to calculate the phase angle of the power system:
Value Angle calculation

CURRENT φ (system) = φ (V) - φ(I)
VOLTAGE φ (system) = φ (I) - φ(V)
Table 13: Transducer angle calculation
67
11.3 ERROR_REF
Selects the reference for the full-scale error calculation. This reference may be the range from 0 to the
maximum characteristic value or the range from –max to +max; the latter is only possible if a
symmetrical characteristic was defined; else "0...+max." is set by default and cannot be changed.
Possible values for this setting are ZERO_MAX (0...+max.) and MAX_MAX (–max… +max).
11.4 SETTLING
The stabilization time of the transducer. This time must be sufficient so the transducer provides a
correct measurement after a change in the input values.
11.5 CTSTARPOINT
currents are rotated by 180° before being sent to the transducer.
11.6 FUNCTION Block

Each FUNCTION block defines one transducer function. Each FUNCTION block has a TYPE
parameter, defining which kind of magnitude the transducer function measures. In a TRANSDUCER
block, there may be only one FUNCTION of each TYPE. There must be at least one FUNCTION in the
TRANSDUCER block.
The structure of the FUNCTION block is as follows:

TYPE Enumeration Type of transducer function Page 69
TOLERANCE Real Tolerance for the test (relative) Page 69
PHASES Enumeration Number of phases of the system Page 69
CHAR Block Transducer characteristic for the function Page 70
68
XRIO Reference
11.6.1 TYPE
This setting defines the type of the transducer function. It must be one of the following:
Value Description
ACT_PWR Active Power
REACT_PWR Reactive Power
APP_PWR Apparent Power
FREQUENCY Frequency
AC_CURRENT Current
AC_VOLTAGE Voltage
PWR_FACTOR Power Factor
LF_TRDCR LF [(1-P/S)*sign Q]
VV_PHASE Phase [V-V]
VI_PHASE Phase [V-I]
II_PHASE Phase [I-I]
I_AVG_SIGNED Signed Average Current
DC_CURRENT DC Current
DC_VOLTAGE DC Voltage
DC_PWR DC Power
LL_VOLTAGE L-L Voltage
Table 14: Transducer functions
11.6.2 TOLERANCE
The relative tolerance for the test, in percent.
11.6.3 PHASES
Number of phases of the transducer. The possible values are P1 (single phase) and P3 (three phase).
69
11.6.4 CHAR Block

The operating characteristic reflects how the transducer transforms the input physical quantity to the
output physical quantity; that is, the characteristic provides the expected value of the transducer output
for every value of the input.
Each characteristic is defined by means of a minimum and a maximum point, plus a knee point in the
case of Compound characteristics. All these points, and in general the operating characteristic, are
defined in the first quadrant. If the SYMMETRICAL setting is True, the characteristic is mirrored into
the third quadrant.
The CHAR block has the following structure:

TYPE Enumeration Type of characteristic used Page 71
SYMMETRICAL Boolean Choose whether the char is symmetrical Page 72
MIN_INP Real Transducer's minimum input value Page 72
MIN_OUT Real Transducer's minimum output value Page 72
KNEE_INP Real Input value for the Knee point in a compound Page 72
char
KNEE_OUT Real Output value for the Knee point in a compound Page 72
char
MAX_INP Real Maximum input value Page 72
MAX_OUT Real Maximum output value Page 72
SAT_OUT Real Limit of the operating characteristic Page 73
70
XRIO Reference
11.6.4.1 TYPE
The following types of operating characteristics are possible:
Value Description Graphic

LINEAR Straight-line segment
COMPOUND Two linear segments
QUADRATIC Quadratic equation
Table 15: Types of Transducer characteristics
71
11.6.4.2 SYMMETRICAL
Check here whether your transducer's operating characteristic is symmetrical. Whether or not a
characteristic is symmetrical depends on the transducer's output range. If you are in doubt, please
refer to the transducer's operating instructions.
For example, a symmetrical compound characteristic would look like this:
Figure 6: Symmetrical transducer characteristic
11.6.4.3 MIN_INP
The transducer's minimum input value. Together with MIN_OUT, this setting defines the initial point of
the characteristic.
11.6.4.4 MIN_OUT
The transducer's minimum output value. Together with MIN_INP, this setting defines the initial point of
the characteristic.
11.6.4.5 KNEE_INP
Input of the knee point of the compound characteristic.
11.6.4.6 KNEE_OUT
Output of the knee point of the compound characteristic.
11.6.4.7 MAX_INP
The transducer's maximum input value. Together with MAX_OUT, this setting defines the final point of
the characteristic.
11.6.4.8 MAX_OUT
The transducer's maximum output value. Together with MIN_OUT, this setting defines the final point of
the characteristic.
72
XRIO Reference
11.6.4.9 SAT_OUT
Value of the output after which the response of the transducer becomes flat. It must be equal or
greater than MAX_OUT.
The following example shows how these values define the characteristic:
SAT_OUT
MAX_OUT
KNEE_OUT
MIN_OUT
KNEE_INP
MIN_INP MAX_INP
73
Appendix: From RIO to XRIO 2.0
1 About XML
The XRIO format is now defined with an XML schema. However, the principle of a block, row and
value structure was kept in the transition. For an overview of the different schema definitions, please
have a look in the OMICRON\Test Universe\Apps\XRIO folder, where the schema definitions are
available as XML schema files (*.xsd).
ATTENTION: It is strongly recommended not to change any of these files in any way.
2 Comparison of XRIO 2.0 and RIO test object definitions

The following tables compare XRIO 2.0 with the RIO format. For a convenient reading of the
differences, colors are used to highlight them. Green is used on the XRIO 2.0 side marking completely
new parameters. Red on the RIO side is used for parameters that were completely canceled. Yellow
on the RIO side shows parameters of the old RIO format that were replaced or changed in XRIO. The
corresponding parameter in XRIO is always in the same row.
One basic change for the new format is the usage of “single value“ parameters only. The old format
allowed defining parameters (rows) with multiple values (ARCP in Distance for example). Those
parameters are all shown in extra lines and are marked with an index like for example ARCP [1] for the
first value of the parameter ARCP in the old RIO format. The second value is written in a new line and
shown as ARCP [2], and so on. The new parameters in XRIO are always in the same row. In the
previous example, ARCP [1] in RIO was replaced by REFPOINT_MAG in XRIO, ARCP [2] by
REFPOINT_ANGLE, etc.
The block structure of RIO was also changed on some places. Blocks in XRIO and in RIO are marked
in dark gray. If the RIO format does not have a corresponding sub block of the structure in XRIO, the
row is left empty.
Multipliers in XRIO are used in a much simpler way than in the old RIO format. Instead of having XOR
relations or an extensive use of optional parameters, described with a cardinality of 0..1 or 0..n, as was
the case in RIO, most of the blocks and parameters in XRIO are defined with a constant multiplier of 1.
In some cases, some rows of the RIO format are shown using the same multiplier (again, ARCP is an
example). This is used for multi-value parameters of the old RIO format. Although in XRIO any of
those parameter / value pairs are shown in an extra row, it was formerly used in one row with a unique
cardinality but with many values. This also has the advantage to mark the beginning and the end of a
previous multi-value parameter more clearly.
74
XRIO Reference
2.1 DEVICE
The DEVICE Block in XRIO has no longer a flat structure. The list of parameters is now grouped in the
sub blocks: NAMEPLATE, LOCATION, NOMINALVALUES, RESIDUALFACTORS, LIMITS, and MISC.
All new blocks have a fixed cardinality of one.
The list of parameters is extended by the new parameter OVERLOADSUPTIME. This parameter
describes the time of the overload suppression. The overload indication is suppressed by 50ms per
default.
XRIO 2.0 RIO

Mult. Default Min Max Mult.
DEVICE DEVICE 1
NAMEPLATE 1
DEVICE_MODEL 1 "" DEVICE_MODEL 0..1
MANUFACTURER 1 "" MANUFACTURER 0..1
DEVICE_TYPE 1 "" DEVICE_TYPE 0..1
SERIALNR 1 "" SERIALNR 0..1
ADDITIONAL_INFO2 1 "" ADDITIONAL_INFO2
LOCATION 1 0..1
DEVICE_ADDRESS 1 "" DEVICE_ADDRESS 0..1
SUBSTATION 1 "" SUBSTATION 0..1
SUBSTATION_ADDRESS 1 "" SUBSTATION_ADDRESS 0..1
BAY 1 "" BAY 0..1
BAY_ADDRESS 1 "" BAY_ADDRESS 0..1
PROTECTED_OBJECT_NAME 1 "" PROTECTED_OBJECT_NAME 0..1
NOMINALVALUES 1
PHASES 1 3 2 3 PHASES 0..1
FNOM 1 50.0 Hz 0 FNOM 0..1
VNOM 1 100.0 V 0 VNOM 0..1
VPRIM_LL 1 110.0 kV 0 VPRIM-LL 0..1
INOM 1 1.0 A 0 INOM 0..1
IPRIM 1 1 kA 0 IPRIM 0..1
RESIDUALFACTORS 1
VLNVN 1 1.732 VLNVN 0..1
ININOM 1 1.0 ININOM 0..1
LIMITS 1
VMAX_LL 1 200.0 V 0 VMAX-LL 0..1
IMAX 1 50.0 A 0 IMAX 0..1
MISC 1
DEBOUNCETIME 1 3.0 ms 0 DEBOUNCETIME 0..1
DEGLITCHTIME 1 0.0 ms 0 DEGLITCHTIME 0..1
OVERLOADSUPTIME 1 50 ms 0 800
Table 16: DEVICE block of XRIO 2.0 vs. RIO:
75
2.2 DISTANCE
DISTANCE required many structural changes. Most of the general DISTANCE settings of RIO were
put in a new sub block called “PROTECTEDOBJECT”. The old “DEFAULT” settings block was
completely removed, together with some of the general settings. All multi-value rows are now replaced
by additional parameter rows. Those lines are marked with yellow. For example the multi-value KL-line
of the old RIO, where the first value described the magnitude and the second described the angle, is
now replaced by the two parameters KL_MAG, and KL_ANGLE.
The new PROTECTIONDEVICE block is organized in the sub blocks TOLERANCES and ZONES.
The formally known sub block ZONE of the old RIO format is now a sub block of ZONES. Furthermore,
the ZONE sub-block structure is more detailed in XRIO. Instead of having a single SHAPE sub-block,
it is now divided in sub-blocks for TOLERANCES, GENERICSHAPES, MOSHAPE, and
LENSTOMATOSHAPE, where the last two ones were formally part of the SHAPE block of the old RIO.
The LINE and ARC parameters are no longer multi-value. They are described now with extra
parameter lines in the corresponding sub-blocks of the GENERICSHAPE block, accordingly called
LINE and ARC.
Circuit breaker time could now be set in the new CB Simulation module and the corresponding XRIO
definition, so the corresponding parameters were removed.
XRIO 2.0 RIO

DISTANCE 0..1 DISTANCE 0..1
ACTIVE 0..1
TCBTRIP 0..1
TCBCLOSE 0..1
PERC52A 0..1
PERC52B 0..1
PROTECTEDOBJECT 1
PTCONN 1 LINE PTCONN 0..1
CTSTARPOINT 1 LINE CTSTARPOINT 0..1
LINEANGLE 1 75.0 ° -360.0 360.0 LINEANGLE 0..1
LINELENGTH 1 1.0 Ω 0 LINELENGTH 0..1
GRF_MODE 1 KL
KL_MAG 1 1.000 0 KL[1]
0..1
KL_ANGLE 1 0.0 ° -360.0 360.0 KL[2]
ZN_R 1 1.0 RERL_XEXL[1]
0..1
ZN_X 1 1.0 RERL_XEXL[2]
Z0Z1_MAG 1 4.0 0 Z0Z1[1]
0..1
Z0Z1_ANGLE 1 0.0 ° -360.0 360.0 Z0Z1[2]
MCF_MODE 1 KM
KM_MAG 1 0.000 0 KM[1]
0..1
KM_ANGLE 1 0.0 ° -360.0 360.0 KM[2]
76
XRIO Reference
ZM_R 1 1.0 0 RMRL_XMXL[1]

0..1
ZM_X 1 1.0 0 RMRL_XMXL[2]
Z0MZ1_MAG 1 1.0 0 Z0MZ1[1]
0..1
Z0MZ1_ANGLE 1 0.0 ° -360.0 360.0 Z0MZ1[2]
PROTECTIONDEVICE 1
ARCRES 1 false ARCRES 0..1
IMPCORR 1 false IMPCORR 0..1
IMPPRIM 1 false IMPPRIM 0..1
CALC_RERL_XEXL 1 false
TOLERANCES
TTOLPLUS 1 50.0 ms 0 TTOLPLUS 0..1
TTOLMINUS 1 0.0 ms 0 TTOLMINUS 0..1
TTOLREL 1 5.0 % 0.0 100.0 TTOLREL 0..1
ZTOLREL 1 5.0 % 0.0 100.0 ZTOLREL 0..1
ZTOLABS 1 50.0 ms 0 ZTOLABS 0..1
ZONES
ZONE 0..n ZONE 0..n
ACTIVE 1 true ACTIVE
MAN_LABEL 1 false
LABEL 0..1 “” LABEL 0..1
INDEX 1 1 INDEX 1
TYPE 1 TRIPPING TYPE 1
FAULTLOOP 1 ALL FAULTLOOP 0..1
TRIPTIME 1 0s 0 TRIPTIME 0..1
INVERT 0..1
TOLERANCES 0..1
TTPL_VALID 1 false
TTOLPLUS 0..1 50.0 ms 0 TTOLPLUS 0..1
TTMI_VALID 1 false
TTOLMINUS 0..1 0.0 % 0 TTOLMINUS 0..1
TTRL_VALID 1 false
TTOLREL 0..1 5.0 % 0.0 100.0 TTOLREL 0..1
ZTRL_VALID 1 false
ZTOLREL 0..1 5.0 % 0.0 100.0 ZTOLREL 0..1
ZTAB_VALID 1 false
ZTOLABS 0..1 50.0 ms 0 ZTOLABS 0..1
GENERICSHAPE 0..1 SHAPE 0..1
INVERT 1 false INVERT 0..1
AUTOCLOSE 1 true AUTOCLOSE 0..1
77
LINE 0..n
REFPOINT_TYPE 1 POLAR
REFPOINT_R 1 0.0 Ω LINE[1] 0..1
REFPOINT_X 1 0.0 Ω LINE[2] 0..1
REFPOINT_MAG 1 0.0 Ω 0 LINEP[1]
REFPOINT_ANGLE 1 0.0 ° -360.0 360.0 LINEP[2]
0..1
ANGLE 1 0.0 ° -360.0 360.0 LINE(P)[3]
INSIDE 1 LEFT LINE(P)[4]
ARC 0..n
REFPOINT_TYPE 1 POLAR
REFPOINT_R 1 0Ω ARC[1]
0..1
REFPOINT_X 1 0Ω ARC[2]
REFPOINT_MAG 1 0Ω 0 ARCP[1]
REFPOINT_ANGLE 1 75.0 ° -360.0 360.0 ARCP[2]
RADIUS 1 0.0 Ω 0 ARC(P)[3]
STARTANGLE 1 260.0 ° -360.0 360.0 ARC(P)[4] 0..1
ENDANGLE 1 300.0 ° -360.0 360.0 ARC(P)[5]
DIR 1 CCW ARC(P)[6]
INSIDE 1 LEFT ARC(P)[7]
MHOSHAPE 0..1 MHOSHAPE 0..1
ANGLE 1 75.0 ° -360.0 360.0 ANGLE 1
REACH 1 1.0 Ω REACH 1
OFFSET 1 0.0 Ω OFFSET 1
LENSTOMATOSHAPE 0..1 LENSTOMATOSHAPE 0..1
ANGLE 1 75.0 ° -360.0 360.0 ANGLE 1
REACH 1 1.0 Ω REACH 1
OFFSET 1 0.0 Ω OFFSET 1
SHAPE_MODE 1 WIDTH
WIDTH 0..1 0.8 Ω WIDTH 0..1
RATIO_AB 0..1 0.8 AB 0..1
78
XRIO Reference
DEFAULTS 0..1
TESTMODE 0..1
ITEST 0..1
VTEST 0..1
TPREFAULT 0..1
TMAXFAULT 0..1
TPOSTFAULT 0..1
FAULTINCMODE 0..1
FAULTINCANGLE 0..1
DCOFFSET 0..1
TREF 0..1
ALLOWRED 0..1
KS[1]
0..1
KS[2]
KSISKL 0..1
ZS[1]
0..1
ZS[2]
Table 17: DISTANCE block of XRIO 2.0 vs. RIO
79
2.3 CBCONFIGURATION
This completely new XRIO definition describes test object settings for the new CB Configuration
module that was introduced in TU 2.0. Therefore, there is no existing RIO definition to change.
XRIO 2.0
Mult. Default Min Max
CBCONFIGURATION 0..n
TRIPTIME 1 50 ms 20 ms 500 ms
CLOSETIME 1 100 ms 20 ms 1000 ms
P52AB 1 20.0 % 0.0 % 45.0 %
Table 18: CBCONFIGURATION block of XRIO 2.0 vs. RIO
80
XRIO Reference
2.4 VISTARTING
As in the other RIO test object definitions, the ACTIVE parameter was removed. Furthermore, some
syntactical changes were done to avoid XML language character conflicts. So, any ‘ > ‘ character was
replaced by a ‘ G ‘.
XRIO 2.0 RIO

VISTARTING 0..n VISTARTING 0..n
ACTIVE 1
ITOL 1 5.0 % 0.1 % 10.0 % ITOL 1
VTOL 1 5.0 % 0.1 % 10.0 % VTOL 1
CHARVIS 1 CHARVIS 1
IG 1 0.2 A 0.05 A I> 1
IGG 1 1.8 A 0.05 A I>> 1
VLNIG 1 48.0 V 0.0 V VLN(I>) 1
VLNIGG 1 48.0 V 0.0 V VLN(I>>) 1
VLLIG 1 80.0 V 0.0 V VLL(I>) 1
VLLIGG 1 80.0 V 0.0 V VLL(I>>) 1
Table 19: VISTARTING block of XRIO 2.0 vs. RIO
81
2.5 SYNCHRONIZER
Only a few changes were done in SYNCHRONIZER. The ACTIVE parameter and the TCBCLOSE
parameter were removed.
XRIO 1.0 RIO

Mu
Mult. Default Min Max lt.
0
..
SYNCHRO 0..n SYNCHRO 1
ACTIVE 1
TCBCLOSE 1
TG_PHASE_SHIFT 1 0.0° -360.0 360.0 TG_PHASE_SHIFT 1
STARTING 1 PULSE STARTING 1
PHASE_SEQUENCE1 1 L1L2L3 PHASE-SEQUENCE1 1
PHASE_SYSTEM1 1 L1L2 PHASE-SYSTEM1 1
PHASE_SEQUENCE2 1 L1L2L3 PHASE-SEQUENCE2 1
PHASE_SYSTEM2 1 L1L2 PHASE-SYSTEM2 1
USE_RATIO_SYS1 1 true
VNOM_SEC_SYS2 1 0.0 V 0.0 V
CHARSYNC 1 CHARSYNC 1
D_VMAX 1 2.0 V 0.0 V D-VMAX 1
D_VMIN 1 -2.0 V 0.0 V D-VMIN 1
VTOLABS 1 0.06 V 0.0 V VTOLABS 1
VTOLREL 1 3.0 % 0.0 % 100.0 % VTOLREL 1
D_FMAX 1 0.1 Hz 0.0 Hz D-FMAX 1
D_FMIN 1 -0.1 Hz 0.0 Hz D-FMIN 1
FTOLABS 1 3 mHz 0.0 mHz FTOLABS 1
FTOLREL 1 3.0% 0.0 % 100.0 % FTOLREL 1
D_PHASEANGLE 1 20.0 ° 0.0 ° 180.0 ° D-PHASEANGLE 1
PHASEANGLE_TOLABS 1 0.6 ° 0.0 ° 180.0 ° PHASEANGLE-TOLABS 1
PHASEANGLE_TOLREL 1 3.0 % 0.0 % 100.0 % PHASEANGLE-TOLREL 1
INNER_LIMIT 1 0.04 Hz 0.0 Hz INNER_LIMIT 1
OUTER_LIMIT 1 0.08 Hz 0.0 Hz OUTER_LIMIT 1
MIN_SYNC_TIME 1 0.0 s 0.0 s
MIN_SYNC_TIME_TOL 1 0.0 % 0.0 % 100.0 %
Table 20: SYNCRHONIZER block of XRIO 2.0 vs. RIO
82
XRIO Reference
2.6 DIFFERENTIAL
In DIFFERENTIAL, the ACTIVE parameter was removed (as in all other object types). Furthermore,
the LINEDIFF sub block was completely removed. This block was introduced in the past as a possible
extension of the differential functionality. However, this functionality was never implemented and
therefore this block was never needed. The tolerance settings (ITOL, TTOL, and TOLHARM) moved
from multi- to single-value parameters.
Significant changes were done for the definitions of the characteristics CHARHARM and TRIPCHAR.
They are not described any more with multi value lines START, LINE, and STOP, where START and
STOP has to be defined once. Instead, these characteristics are defined in extra sub blocks called
POINT, which consist of the two coordinate parameters X and Y. Every sub block of the “POINT” type
that describes the characteristic coordinates has to be included twice as a minimum. This reflects the
necessity of the START and STOP parameters in the old RIO format.
One small syntactical change was done for the DIFF parameter group (IDFF>, etc.). Due to the fact
that the ‘ > ‘ and ‘ < ‘ characters form part of the XML language definition, those characters were
replaced by G and GG respectively.
TAP_SETTING and DELTA_CN_CT are completely new parameters for new features in TU 2.0, which
supports delta connected CTs.
The CONVREALY setting was removed; its functionality is now invoked automatically, depending on
the type of the protected object.
83
XRIO 2.0 RIO

DIFFERENTIAL 0..1 DIFFERENTIAL 0..1
ACTIVE 0..1
WINDING_COUNT 1 2 2 3 WINDING-COUNT 0..1
REF_WINDING 1 "" REF-WINDING 0..1
OBJECT_TYPE 1 TRANSFORMER OBJECT-TYPE 0..1
ITOL_REL 1 2.0 % 0.0 % 100 % ITOL [1]
0..1
ITOL_ABS 1 0.05 In 0.0 In ITOL [2]
TTOL_REL 1 3% 0.0 % 100 % TTOL [1]
0..1
TTOL_ABS 1 0.01 s 0.0 s TTOL [2]
TREF 1 FAULT TREF 0..1
TRET 1 0.25 s 0.0 s TRET 0..1
TMAX 1 1.5 s 0.0 s TMAX 0..1
IREF 1 INOM_PO IREF 0..1
USECT 1 false USECT 0..1
CONVRELAY 0..1
DELTACT 1 false DELTACT 0..1
WINDING 0..n WINDING 0..1

NAME 1 "" NAME 0..1
INULL_ELIMINATION 1 IL_I0 INULL_ELIMINATION 0..1
CONNECTION 1 Y CONNECTION 0..1
CONNECTIONNUMBER 1 0 0 11 CONNECTIONNUMBER 0..1
NOM_PD_PH 1 0.0 A 0.0 A NOM-PD-PH 0..1
NOM_CT_PH 1 0.0 A 0.0 A NOM-CT-PH 0..1
GROUNDING_CT_PH 1 TRANSFORMER GROUNDING_CT_PH 0..1
NOM_PD_N 1 0.0 A 0,0 A NOM-PD-N 0..1
NOM_CT_N 1 0.0 A 0.0 A NOM-CT-N 0..1
GROUNDING_CT_N 1 TRANSFORMER GROUNDING-CT-N 0..1
VN 1 0.0 V 0.0 V VN 0..1
SN 1 0.0 VA 0.0 VA SN 0..1
GROUNDING_TRF 1 false GROUNDING-TRF 0..1
TAP_SETTING 1 1.0
DELTA_CONN_CT 1 false
84
XRIO Reference
DIFFBIAS 0..1 DIFFBIAS 0..1

ACTIVE 1 false ACTIVE 0..1
DIFF 1 DIFF 0..1
IDIFFGG 1 2.0 In 0.0 In IDIFF>> 0..1
TDIFFGG 1 0.03 s 0.0 s TDIFF>> 0..1
IDIFFG 1 0.3 In 0.0 In IDIFF> 0..1
TDIFFG 1 0.03 s 0.0 s TDIFF> 0..1
BIAS 1 BIAS 0..1
DEFBIAS (2) 1 IPIS_SUM_ABS DEFBIAS 0..1
BIASDIVISOR 1 1.0 BIASDIVISOR 0..1
TOLHARM_ABS 1 1.0 0.0 TOLHARM [1]
0..1
TOLHARM_REL 1 3.0 % 0.0 % 100.0 % TOLHARM [2]
CHARHARM 0..n CHARHARM 0..1
ORDERHARM 1 1 0 ORDERHARM 0..1
DELAYHARM 1 0.0 s 0.0 s DELAYHARM 0..1
CHARTABLE 1
POINT 2..n
START [1]
1
START [2]
X 1 0.0 Ixf/Idiff[%] 0.0 LINE [1]
0..n
Y 1 0.0 Idiff/Inom 0.0 LINE [2]
STOP [1]
1
STOP [2]
TRIPCHAR 0..1 TRIPCHAR 0..1
POINT 2..n
START [1]
1
START [2]
X 1 0.0 IBias/In 0.0 LINE [1]
0..n
Y 1 0.0 Idiff/In 0.0 LINE [2]
STOP [1]
1
STOP [2]
LINEDIFF 0..1
ACTIVE 0..1
METHOD 0..1
I-PICKUP 0..1
D-PHI 0..1
TRIP> 0..1
Table 21: DIFFERENTIAL block of XRIO 2.0 vs. RIO
85
2.7 OVERCURRENT
Significant changes in OVERCURRENT were done in the characteristic description. All multi-value
parameters (CHAR and CHARI2T, POINT) were replaced by sub blocks where all parameter values
are listed explicitly in single value parameters. The tolerance settings in the upper level were replaced
by single value parameters too, but without an extra sub block. As usual, the ACTIVE line was
completely removed.
XRIO 2.0 RIO

OVERCURRENT 0..n OVERCURRENT 0..1
ACTIVE 1
DISPLAY_ABSOLUTE 1 false DISPLAY_ABSOLUTE 0..1
ITOLREL 1 5% 0.0 % 95.0 % ITOL[1]
0..1
ITOLABS 1 0,1 In 0.0 In 1.0 In ITOL[2]
TTOLREL 1 10 % 0.0 % 95.0 % TTOL[1]
0..1
TTOLABS 1 0,1 s 0.0 s 838.0 s TTOL[2]
PTCONN 1 LINE PTCONN 0..1
CTSTARPOINT 1 LINE CTSTARPOINT 0..1
DIRECTIONAL 1 false DIRECTIONAL 0..1
AUTORESET 1 false
GROUP 0..n GROUP 0..n
NAME 1 LN NAME 1
RESET_RATIO 1 0,95 0.1 1.0
UNIT 1..n UNIT 0..n

NAME 1 IGG NAME 1
ACTIVE 1 true ACTIVE 1
IPICKUP 1 1.0 In 0.001 In 1000 In IPICKUP 1
TINDEX 1 1.0 0.0 5000.0 TINDEX 1
CHARTYPE 1 PREDEFINED
PREDEFCHAR 1 DEFTIME PREDEFCHAR 0..1
CHAR 0..1
NAME 1 "Name" CHAR [1]
A 1 0.14 CHAR [2]
B 1 0.0 CHAR [3]
0..1
P 1 0.02 CHAR [4]
Q 1 1.0 CHAR [5]
K1 1 0.0 CHAR [6]
K2 1 0.0 CHAR [7]
AUTORESR 1 1.0
AUTOREST 1 2.0
86
XRIO Reference
CHARIAC 0..1
NAME 1 "Name"
A 1 0.20780 s
B 1 0.86300 s
C 1 0.80000
D 1 -0.41800 s
E 1 0.19470 s
AUTORESR 1 1.0
AUTOREST 1 2.0
CHARI2T 0..1
NAME 1 "Name" CHARI2T [1]
A 1 100.0 CHARI2T [2]
0..1
P 1 2.0 CHARI2T [3]
Q 1 1.0 CHARI2T [4]
TABLE 0..1 TABLE 0..1
NAME 1 "Name" NAME 1
POINT 1..n
X 1 2.0 IPickup 0 POINT [1]
0..1
Y 1 20.0 s 0 POINT [2]
Table 22: OVERCURRENT block of XRIO 2.0 vs. RIO
87
2.8 METER
The ACTIVE parameter of RIO was removed. V_PRIM, V_SEC, I_PRIM, I_SEC were removed too.
They are handled now in the DEVICE block.
Some parameters for the METER block were added in XRIO. They came along with new features
available in TU 2.0. The first three parameters are Boolean and the forth parameter called
EXPORTDIR is an enumeration with the possible settings POSITIVE or NEGATIVE.
XRIO 2.0 RIO

METER 0..n METER 0..1
ACTIVE 1
TYPE 1 W_H TYPE 0..1
SINGLEPHASE 1 false
GATED_MECHANISM 1 false
THREEWIRE 1 false
DIRECTION 1 EXPORTING DIRECTION 0..1
EXPORTDIR 1 POSITIVE
QUADRANT 1 Q_ALL QUADRANT 0..1
PULSE_TYPE 1 RISING PULSE_TYPE 0..1
CERTIFIED 1 "" CERTIFIED 0..1
CLASS 1 0.5 0.01 10.0 CLASS 0..1
PULSES_PER_REV 1 1 0 65535 PULSES_PER_REV 0..1
SETTLING 1 5.0 s 0.0 s 18000 SETTLING 0..1
CONSTANT 1 750 Pul/Quant 2e-12 5e+11 CONSTANT 0..1
V_PRIM 0..1
RIO -> XRIO 0..1
V_SEC
METER now uses the values in the DEVICE Block
I_PRIM 0..1
I_SEC 0..1
Table 23: METER block of XRIO 2.0 vs. RIO
88
XRIO Reference
2.9 TRANSDUCER
XRIO 2.0 RIO

TRANSDUCER 0..n TRANSDUCER 0..1
ACTIVE 1
TRDCR_OUT 1 CURRENT TRDCR_OUT 1
ANGLE_REF 1 CURRENT ANGLE_REF 1
ERROR_REF 1 ZERO_MAX ERROR_REF 1
SETTLING 1 1.0 s 0.0 s 838.0 s SETTLING 1
CTSTARPOINT 1 LINE
FUNCTION 1..n FUNCTION 1..n
TYPE 1 ACT_PWR TYPE 1
TOLERANCE 1 0.5 % 0.0 % 100.0 % TOLERANCE 1
PHASES 1 P1 PHASES 1
CHAR 0..1 CHAR 0..1
TYPE 1 SINGLE TYPE 1
SYMMETRICAL 1 false SYMMETRICAL 1
MIN_INP 1 0.0 MIN_INP 1
MIN_OUT 1 0.0 MIN_OUT 1
KNEE_INP 1 0.0 KNEE_INP 1
KNEE_OUT 1 0.16 KNEE_OUT 1
MAX_INP 1 173.205 MAX_INP 1
MAX_OUT 1 0.02 MAX_OUT 1
SAT_OUT 1 0.22 SAT_OUT 1
Table 24: TRANSDUCER block of XRIO 1.0 vs. RIO
89

XRio Reference Manual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

XRio Reference Manual

Uploaded by

Copyright:

Available Formats

XRIO

Manual Version: XRIO_REFERENCE.AE.1

4.4 PROTECTIONDEVICE Block ............................................................................................................ 28

4.4.7.12 LINE Block .......................................................................................................................... 35

7.9 CHARSYNC Block ............................................................................................................................. 45

10 METER Block ........................................................................................................................................ 64

OTU : OMICRON Test Universe

2 Basic Elements of the XRIO Format

2.1 XRIO Format Structure

2.2 Value Data Types

XRIO CTS Description

ID Type Description Refer to

3.1 NAMEPLATE Block

ID Type Description Refer to

3.2 LOCATION Block

ID Type Description Refer to

3.3 NOMINALVALUES Block

ID Type Description Refer to

3.4 RESIDUALFACTORS Block

ID Type Description Refer to

ININOM Real IN / Inom Page 15

3.4.1 VLNVN and ININOM

3.5 LIMITS Block

ID Type Description Refer to

3.6 MISC Block

ID Type Description Refer to

Signal after filtering:

Signal after filtering:

Figure 1: Tolerance bands in a Distance zone

The following data define an arc:

Figure 2: Example of an invalid shape

Figure 3: Shape tolerances

Figure 4: MHO characteristic (picture quality good enough ??)

Figure 5: lens / tomato shape

The distance B on the figure is calculated according to the following equation:

4.2 Structure of the DISTANCE block

ID Type Description Refer to

4.3 PROTECTEDOBJECT Block

ID Type Description Refer to

PT on line side PT on busbar side

CT towards line CT towards busbar

Protection relay Protection relay

4.4 PROTECTIONDEVICE Block

ID Type Description Refer to

ID Type Description Refer to

ID Type Description Refer to

L1N L2N L3N One single Line-to-ground fault loop

4.4.15.5 TOLERANCES Block

ID Type Description Refer to

4.4.15.6 MHOSHAPE Block

ID Type Description Refer to

4.4.15.7 LENSTOMATOSHAPE Block

ID Type Description Refer to

4.4.15.8 GENERICSHAPE Block

ID Type Description Refer to

4.4.15.11 LINE Block

ID Type Description Refer to

4.4.15.12 ARC Block

ID Type Description Refer to

The CBCONFIGURATION block is composed of the following parameters:

ID Type Description Refer to

The VISTARTING block is composed of the following parameters:

ID Type Description Refer to

ID Type Description Refer to