xrio user manual

7/25/2019 XRIO User Manual

1/38

XRIOUser Manual


2/38

2

OMICRON Test Universe

Article Number: VESD 5015 - Manual Version: XRIO.AE.3 - Year 2011

OMICRON electronics. 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, optical

character recognition and/or storage in electronic data processing systems, requires the explicit consent of

OMICRON electronics.

Reprinting, wholly or in part, is not permitted. The product information, specifications, and technical data

embodied in this manual represent the technical status at the time of writing and are subject to change without

prior notice.

We have done our best to ensure that the information given in this manual is useful, accurate, up-to-date and

reliable. However, OMICRON electronics does not assume responsibility for any inaccuracies which may be

present.

The user is responsible for every application that makes use of an OMICRON product.

OMICRON electronics translates this manual from the source language English into a number of other

languages. Any translation of this manual is done for local requirements, and in the event of a dispute between

the English and a non-English version, the English version of this manual shall govern.


3/38

OMICRON Test Universe XRIO User Manual

Table of Contents

1 Introduction .............................................................................................................................................. 52 RIO and XRIO............................................................................................................................................ 5

2.1 Purpose of Data in RIO and XRIO ...................................................................................................... 52.2 RIO and its Limitations ........................................................................................................................ 62.3 XRIO and its Enhancements ............................................................................................................... 6

3 The Test Object User Interface ............................................................................................................... 83.1 User Roles........................................................................................................................................... 83.2 The Generic User Interface................................................................................................................. 8

3.2.1 Standard Mode.............................................................................................................................. 93.2.2 Advanced Mode........................................................................................................................... 11

3.3 The Classic User Interface................................................................................................................ 13

4 The XRIO Structure................................................................................................................................ 14

4.1 Technical Details behind XRIO ......................................................................................................... 144.2 Blocks and Parameters ..................................................................................................................... 144.3 Block Properties ................................................................................................................................ 154.4 Parameter Properties ........................................................................................................................ 16

5 Global Test Object with Multiple Function Blocks ............................................................................. 18

6 Custom Section Create your own Parameters................................................................................. 20

7 XRIO Scripting........................................................................................................................................ 217.1 Setting up Formulas for Values and Enabled Flags.......................................................................... 21

7.1.1 Basics about Formulas................................................................................................................ 227.1.2 Arithmetic Operators.................................................................................................................... 247.1.3 Comparison Operators ................................................................................................................ 247.1.4 Logical Operators ........................................................................................................................ 24

7.1.5 IIF Statement............................................................................................................................ 247.1.6 Predefined References................................................................................................................ 25

7.2 Script Functions Section with Global Functions................................................................................ 257.2.1 Programming in the Script Functions Section ............................................................................. 277.2.2 Adding Script References............................................................................................................ 287.2.3 Compilation and Execution of the Script in the Background ....................................................... 28

8 Organizing XRIO files ............................................................................................................................ 298.1 Left Tree The Test Object .............................................................................................................. 298.2 Right Tree The XRIO File............................................................................................................... 308.3 Merging the two Trees....................................................................................................................... 30

8.3.1 Blocks with fixed Destination....................................................................................................... 308.3.2 Blocks with variable Destination.................................................................................................. 30

9 XRIO Converter Input Genuine Relay Settings................................................................................ 31

10 Testing and Debugging of XRIO Converter....................................................................................... 33

11 Filters..................................................................................................................................................... 35

12 Fully Parameterized Tests LinkToXRIO.......................................................................................... 37

3


4/38


Glossary

Abbreviations

OTU : OMICRON Test UniverseRIO : Relay Interface by OMICRONXRIO : eXtended Relay Interface by OMICRONOCC : OMICRON Control CenterXML : eXtensible Markup LanguageSEL : Schweitzer Engineering LaboratoriesVB.Net : Visual Basic .NetMSDN : Microsoft Developer NetworkSDK : Software Developer Kit

Definitions

Test Object : Component of the Test Universe software describing the device under testXRIO : Specification for Test Object definitions introduced with Test Universe 2.0XRIO File : Saved XRIO Test Object as a fileXRIO Converter : Test Object with automatic calculation of parameters from settings

4


5/38


1 Introduction

The XRIO concept was introduced with the OMICRON Test Universe (OTU) 2.0 as an improvement of theRelay Interface by OMICRON (RIO). It represents the second generation to model test objects in the OTU.

A test object can be a protection relay, a meter, or other devices, which are physical test objects in aprotection environment.

The purpose of this manual is to illustrate the features of XRIO. All the explanations in this manual arebased on an example XRIO converter for the protection relay SEL-421 from Schweitzer EngineeringLaboratories and show the concept behind XRIO. With this knowledge, it should be possible to createXRIO files with XRIO converter functionality for any test object. It is also shown how to use the XRIO filesin a test plan in the OMICRON Control Center (OCC).

It is required to be familiar with the OTU, the OCC and RIO before reading this manual.

The following chapter points out the reason for introducing XRIO in the OTU 2.0 and the advantagescompared to RIO, which was used in previous versions of the OTU.

2 RIO and XRIO

2.1 Purpose of Data in RIO and XRIO

RIO was developed out of a need for a uniform data format for the parameters of protective relaysproduced by different manufacturers. It provides a common structure for functionally similar relays fromdiverse manufacturers to be tested with similar test procedures. Moreover, RIO permits relaycharacteristics to be imported into the OTU software from external sources.

The following excerpt of the SEL-421 RIO file illustrates the structure of a RIO file. Each Test Objectcontains of a DEVICE block with general parameters and optional function blocks with protection functionspecific parameters (e.g. DISTANCE block).

BEGIN TESTOBJECTBEGIN DEVICEDEVICE_MODEL "SEL-421"MANUFACTURER SchweitzerDEVICE_TYPE 21PHASES 3VNOM 115VMAX-LL 200VPRIM-LL 230000INOM 5IMAX 50IPRIM 1000FNOM 50ININOM 1VLNVN 1.732

END DEVICEBEGIN DISTANCE

ACTIVE TRUELINEANGLE 84LINELENGTH 7.8...BEGIN ZONE

LABEL "Z1 L-L"INDEX 1TYPE TRIPPINGFAULTLOOP LL

ACTIVE trueTRIPTIME 0...

END ZONE...

END DISTANCEEND TESTOBJECT

Figure 1: RIO structure shown by an excerpt of the SEL-421 RIO file

5


6/38


The XRIO concept introduced in the OTU 2.0 is based on the RIO file technology. The "X" in the nameXRIO stands for eXtended RIO. XRIO implements some enhancements to RIO to overcome its limitationsand fulfill future requirements of automated testing. The most important aspect of XRIO is that a tester canwork directly with the relay specific parameter settings. Therefore, a XRIO file includes additionalinformation and functionality compared to a RIO file.

2.2 RIO and its Limitations

The OMICRON test modules can be divided in two groups. There are function specific test modules forspecific protection functions, and general test modules. The RIO specification defines how to store thesefunctions with its parameters in a RIO file. A Test Object function is a block in the RIO file with a definedstructure as shown by the DISTANCE block in Figure 1.

Some examples for general test modules are QuickCMC, State Sequencer, andRamping.

The function specific test modules are closely coupled to a Test Object function and a set of parametersdescribing this function. Examples for function specific test modules are Overcurrent, Distance, andDifferential. The so called RIO functions for specific protection functions are always developed togetherwith the according test modules. If test modules would have also access to parameters from otherfunction specific blocks and/or access to new blocks with freely definable parameters the usability of theconcept would be increased enormously.

Another serious drawback of the RIO concept is that each Test Object function block can only occur oncein a Test Object. This becomes especially obvious when testing overcurrent functions because relayshaving more overcurrent functions than can be covered by one RIO Test Object. With the RIO filetechnology, the workaround was to insert multiple Test Objects in an OCC document, which can becumbersome.

Although RIO gained wide acceptance, the data sheet of a relay does not contain the parameters in theRIO representation. This concept has some good reasons, but also has disadvantages. It would beadvantageous to work directly with the relay specific parameters. Therefore, the relay parameters must betransformed into RIO parameters, which can be done by human or by program (Excel macros, relaysoftware export,). A RIO converter is a utility to transform relay parameters from a specific source (file,

database) into a RIO file.

RIO Converter

TEST OBJECTRelay Specific Parameters

OMICRON Test Universe

RIO File

XRIO File

Figure 2: RIO converter needed for RIO file technology

2.3 XRIO and its Enhancements

The XRIO implementation includes some enhancements to overcome the limitations and disadvantagesof RIO which are described above. The basic concept to implement the XRIO features is a generaldefinition of XRIO as a tree structure with blocks and parameters. Parameters are the leaves of the treeand contain the real information. A block can contain parameters and sub blocks. This concept is a usual

technique to structure data (e.g. file systems).

6


7/38


Generally, there are three sections in XRIO to group the data file according to its purpose and origin.

The RIO section holds conventional RIO blocks for function specific test modules which are required forthe test modules in the OTU. The structure of this section is based on the RIO specification.

The Customsection can be freely defined. The main purpose is to map the relay specific parametersettings. These parameters are the same as the parameters which an engineer uses to configure the test

object. Additionally, the Custom section can include other user-defined helper parameters.

The Script Functions section has no sub-blocks and parameters. In this section it is possible to declareglobal functions which are used for the transformation of the relay specific parameters into the RIOparameters.

The XRIO tree structure with its three sections is shown in Figure 3. The detailed structure of XRIO isdescribed in chapter 4 The XRIO Structure.

Figure 3: XRIO tree structure

The following list includes all XRIO enhancements which are introduced in the XRIO concept to improvethe Test Object settings architecture.

XRIO StructureHierarchical tree structure with blocks, sub-blocks, and parameters.

Global Test Object with repeated Function BlocksUsage of multiple function specific blocks of the same kind in a Test Object.

Custom Section Create Your Own ParametersUser-defined parameters (relay specific parameters and helper parameters) with references toother parameters and the possibility of using formulas.

XRIO ScriptingCreation of formulas in the RIO section for converting the relay specific parameters in the Customsection into the RIO parameters. Global functions can be defined in the Script Functions section.

XRIO OrganizerA tool to organize the content of XRIO files. There are import, merge, and export functions.

XRIO Converter Input Relay Settings Only

Usage of the relay specific parameters as input. The XRIO converter connects the inputparameters into the OMCIRON Test Object parameters.

Testing and Debugging of XRIO Files

FiltersImport/Export relay settings into a XRIO file.

LinkToXRIOThe OTU test modules can link test settings to any Test Object parameter in the XRIO file.

The above mentioned enhancements included in the XRIO concept are explained in detail in chapters 4to 12. In the following chapter, the features and commands of the new Test Object user interface areshown.

7


8/38


3 The Test Object User Interface

The Test Object user interface in the OTU combines a new generic user interface with the classic TestObject user interfaces from previous OTU versions.

The generic user interface is designed to browse and manipulate the whole contents of a Test Object. Theclassic user interface for the device settings and the function specific blocks can be accessed in the RIOsection in the generic user interface. Both parts of the user interface are used to create a Test Object withXRIO converter functionality. It is possible to edit the parameter values in both user interface types.

3.1 User Roles

There are the following three groups of users who work with the Test Object user interface. Each groupperforms different tasks and has different requirements to the user interface.

Test Object DesignerThe designer of a Test Object with XRIO converter functionality is an expert for protection and/ormeasuring devices and needs in-depth knowledge about OMICRON test modules and Test

Objects. His task is to generate Test Objects from scratch. The sophisticated work can be dividedinto several tasks which are described in detail in chapter 9.

Test DesignerThe test designer creates OCC documents, where he imports an existing Test Object and modelsthe test settings. XRIO allows him to link test settings to any Test Object parameter. This conceptis called LinkToXRIOand is described in chapter 12.

TesterThe tester primarily executes the test. Sometimes he switches to the test designer role to makesome adaptations to the test.

3.2 The Generic User Interface

The generic user interface is shown at opening of the Test Object and represents the main window. For aseparation of the above described different user roles, the Test Object can change between two modes.The flag in the menu VIEW| ADVANCEDis used to switch between the two modes. Depending on theselected mode, there are different commands available for the user. The mode of the Test Object of thelast session is always saved and used when opening the Test Object next time.

Figure 4: Generic user interface of Test Object in standard mode (Customsection)

8


9/38


3.2.1 Standard Mode

A tester and the test designer work in this mode to import an existing XRIO file and configure the TestObject with the current settings of the relay. There are only the enabled parameters and blocks visible inthe Customsection. This can be achieved by some logic depending on the current relay configuration tomake only the configured features available.

The parameter table shows the Status, Name, Foreign ID, Description, Value, and Unitof the parameters.Only the parameter value can be entered, all other fields are read-only. Parameters, which are disabled,are not visible in the parameter table. The status of a parameter can be

parameter is okay ( means that a comment is defined)

or

parameter has a disabled value formula.

In the RIOsection, it is only possible to view or edit the OMICRON Test Object settings in the classic userinterfaces (with the exception of the CB Configuration function block that has no classic user interface).The inner structure of the function specific blocks in the RIOsection is not visible to a user in standardmode. Instead of the parameter table there is an Editbutton to open the classic user interfaces for the

device settings and the function specific blocks.

Figure 5: Generic user interface of Test Object in standard mode (RIOsection)

Standard Commands

The standard commands of the Test Object are available in both standard and advanced mode. These

commands are used to work with existing XRIO files.

FILEmenu commands:

IMPORT andEXPORTOpens a dialog to import a new RIO / XRIO file or to export the current Test Object to a RIO /XRIO file.

IMPORT RELAY SETTINGSImporting relay settings with an existing filter from an appropriate file (e.g. XML file, Excel sheet)

REVISIONDisplay and update the XRIO Converter Version

SAVE AND EXIT andEXIT WITHOUT SAVE

Exit from the Test Object and optional save the changes of the Test Object to the test module orOCC document. The OKand Cancelbutton provide the same way to exit the Test Object.

9


10/38


10

FUNCTIONmenu commands to manipulate RIO functions:

ADD andDELETE

EDITShow the classic test object user interface of the RIO function.

VIEWmenu commands:

ADVANCEDThis switches between standard and advanced mode of the Test Object. In advanced mode, acheck mark is shown.

RIOShow or hide the RIO subtree of the XRIO file.

ERRORSA list of information, warnings, and errors of the current XRIO file.

In Figure 7there is the Errorsview window shown of a sample XRIO file with its error messages. The

amount of errors, warnings, and information in a XRIO file are also shown in the status bar of the TestObject (see bottom of Figure 5).

Figure 6: Number of errors, warnings, and information shown in the status bar

Besides the three mentioned categories, there are different groups of messages for each category. Theline and column number of the errors and warnings in the XRIO file are also displayed in the Errors view.Additionally, there is a Description, the Name-Path, and the Id-Pathshown for each message.With all thisinformation it is possible to find errors and warnings in a XRIO file.

If the source of an error can directly been viewed in the XRIO user interface (parameter, formula code,

script,), the context menu of the error entry contains the "Goto Error" command that directly jumps tothe cause of the error. This is also possible with just double-clicking the error entry.

Figure 7: Errors view in the Test Object

The information messages show which parameter values have changed to a new value by an import ofrelay settings with a filter. The way how filters work is described in detail in chapter 11.

In the OMICRON test modules only the error messages of the Test Object are shown in the status historyview as shown below.

Figure 8: Status history view in OMICRON test modules

Note:as long as an error exists in XRIO, calculating formulas is temporarily disabled.


11/38


3.2.2 Advanced Mode

The designer of a XRIO file with its XRIO converter functionality works in the advanced mode of the TestObject. Besides the standard commands there are the advanced commands available.

In the Custom section there are all blocks and parameters visible. The designer can add, delete, cut, copy,paste, and modify parameters and blocks. The parameter table shows additionally to the standard mode

the parameter's ID, Minand Maxvalue, and value Formula. By right-clicking the header of the parametertable the visibility of the single columns can be customized.

There is also an additional parameter status for disabled parameters shown with the following icon.

parameter which is disabled

Disabled blocks are also visible and marked with a cross over the block icon as it is shown in Figure 9.

Figure 9: Generic user interface of Test Object in Advanced Mode

In the RIOsection the inner structure of blocks with their parameters is shown. Designers can defineformulas to calculate a parameter value from other parameters and to control the Enabledattribute ofblocks and parameters. It is only possible to add new function specific blocks as sub blocks of the RIOroot block.

Figure 10: Add function specific blocks in the RIOsection

11


12/38


The data type, Minvalue, Maxvalue, Name, ID, and Description of RIO parameters cannot be changed.Block names can be changed to distinguish blocks of the same type (e.g. labels for distance zones).Function specific RIO sub block can only be changed by a designer in the classic user interfaces of thespecific functions blocks and/or with the integrated XRIO organizer, which is described in chapter 8.Additionally, the Script Functions section of a XRIO file is accessible. The purpose of the Script Functionssection is described in chapter 7.2.

Advanced Commands

FILE menu commands:

ORGANIZEOpens the XRIO organizer. The organizer includes two panes. There is one for the Test Objectand one for a XRIO file, which can be imported and exported.

BLOCKand PARAMETER menu commands:

ADD CTRL+B for block andCTRL+P for parameter

DELETE

CUT

COPY

PASTE

DETAILS

MOVE UP

MOVE DOWN

SET AS ACTIVE FUNCTION only in block menu

As mentioned above, blocks and parameters can be added in the Custom section in the generic TestObject user interface. In the RIO section only test module function blocks can be added as sub block ofthe RIO block. For this reason there are different block or parameter commands available depending onwhich block or parameter is marked. There is also a toolbar available which includes the import buttonand buttons to add, remove, and show details of blocks and parameters.

Figure 11: Toolbar of the Test Object

The tree view shows the nested block structure and offers the commands for blocks in the context menu.Additionally, there is the possibility to open the classic user interface for the device block and the functionspecific blocks in the RIO section.

The Script Functions section of the Test Object contains global functions which are useful for the XRIOconverter functionality. It is possible to add external references to the script, and compile or debug thescript. XRIO scripting is described in detail in chapter 7.

12


13/38


Cut / Copy / Paste

These commands appear in the main XRIO block and parameter menus and in the context menu.The functionality does not use the clipboard of the operating system. Therefore a cut/copy/paste is onlyavailable within a single Test Object and not between multiple Test Objects.

The items are copied with the current contents and references to other items. The existence ofdependencies (e.g. input parameter of formulas) inside the item and from other items is taken intoconsideration. The manipulations will be only allowed when the resulting context will make sense. Thelogic of formula reference handling is as follows:

1. If a tree is copied/moved which has internal formula references, these references are internal inthe copied tree too.

2. If a tree is copied/moved which has input parameters from outside the tree, these fixed referencesstay the same.

3. If a tree is copied which has parameters that are references to outside formulas (its parametersare input to outside formulas), these outside formulas keep the source tree parameters as input.

4. If a tree is cut/pasted in the same way, the outside references are applied to the new target.

5. If a tree is deleted which has parameters that are references to outside formulas, these outside

formulas are disabled.6. Disabled formulas, which are only disabled because of missing references, are enabled again, if

all references with the same ID paths are recreated.

3.3 The Classic User Interface

The classic user interfaces to work with Test Objects from older versions of the OTU are still available andneeded for some function specific RIO blocks to generate the structure of the corresponding part in theRIOsection. They are accessed through the context menu of the device block and the particular functionblocks in the RIO section.

For example, the block structure of the distance function block (distance zones definitions) has to begenerated in the Characteristic Editor of the classic user interface before the XRIO converter functionalitycan be implemented. The shape of the zones can be defined in the Characteristic Editor as shown below.

Figure 12: Classic user interface (Distance) and Characteristic Editor for distance zones

Note that the classic test object user interface is not directly aware of the XRIO specific infrastructure likeformulas and their dependencies. If for example a value is changed in an edit field that is a calculationresult of a formula, the corresponding formula will be disabled as the value is not any more the result of

the calculation.When the classic UI is closed with the OK button, XRIO checks for such problems and warns the user ifhe has destroyed formulas by changing values. The user can cancel the changes.

13


14/38


4 The XRIO Structure

4.1 Technical Details behind XRIO

The specification of the technical details how XRIO file has to be constructed is described in the

XRIO Technical Referencemanual which comes with the documentation of the OTU.

4.2 Blocks and Parameters

The Test Object is a container for the whole information about a device.

A single piece of information is a parameter. A block can include a group of parameters and other subblocks. A Test Object has the same structure as a file system in a computer (you can compare a XRIOparameter with a file and a XRIO block with a folder).

A parameter in the Customsection is used to define a relay specific setting or a helper parameter for theXRIO converter. The parameters in the RIO section represent the Test Object settings for the testmodules.

Figure 13: Block structure (tree view left side) and parameters of

a block (parameter table right side)

Parameters and blocks have some common properties. Actually the parameters have the same propertiesas the blocks plus the value properties. The properties can be edited in the appropriate details pages.

14
http://xrio%20technical%20reference.pdf/http://xrio%20technical%20reference.pdf/


15/38


4.3 Block Properties

The following figure shows the block details page which can be accessed via the BLOCKmenu in theadvanced mode or the context menu of the selected block.

Figure 14: Block details page

Note that the explanations of the block properties are also valid for parameter properties because theseare common properties.

NameShort name for a block or a parameter.

IDAnidentifier for a block or a parameter. It must start with a letter (A..Z) and must be a unique key(sequence of capitalized letters and digits) for all parameters and sub blocks within a block. Thefrequently used character ">" (for overcurrent pick up levels I>, I>>) is not allowed in ID's.

Identifiers are used as names for variables in the formulas. Therefore, IDs have to be differentfrom the keywords of the script language (VB .Net).

DescriptionA comment to describe the block and parameter.

Foreign IDSupplier specific parameter address.

CommentAny additional information about the parameter can be stored here.

EnabledThis flag enables a block or parameter. A logical expression can be used to calculate the Enabledflag. Whether a block or parameter is enabled or not then depends on a formula which caninclude other parameters and global functions.

The Enabled flag is available in the Custom section and the RIO section. Generally, blocks andparameters which are disabled are not visible in the standard mode. In the advanced mode, they arevisible but marked as disabled blocks or parameters. Note that the disabled blocks and parameters in theRIOsection are not passed to the test modules of the OTU. All disabled blocks and parameters are stillavailable for the references used in a XRIO converter and the LinkToXRIO concept.

15


16/38


4.4 Parameter Properties

Beside the common properties of blocks and parameters the parameters have some additional properties.These properties are called Value andDisplay Properties and are used to define the value relatedinformation of a parameter. The following figure shows the parameter details page which can be accessedvia the PARAMETERmenu in advanced mode or the context menu of the selected parameter.

Figure 15: Parameter details page

The additional value and display properties for a parameter are explained in the following section:

Data TypeThe data type can be String, Enumeration, Boolean, Integer, or Real.This information is also used to provide a comfortable data input (e.g. a combo box forEnumerationtype and a checkbox for Booleantype).

The Define Values button opens a dialog to define the values of an enumeration. Eachenumeration item contains an internal used identifier and a name.

Figure 16: Enumeration value definition

16


17/38


If a Boolean type is chosen the value can only be true or false. The Integer and Real types haveminimum and maximum values.

Value, Multiplier, Unit, Digits after decimalA value is a constant or the evaluated formula expression. It is possible to define a unit and amultiplier for a value. The available units are V, A, s, cy, Hz, C, F, W, VA, var, and Ohm. Theuser can also define any string as unit. Multipliers are used to represent a value in the userinterface as a combination of an adjusted value with its multiplier. They can be ufor 10-6, m for10

-3, k for 10

3, and M for 10

6and can be used with the predefined units and with custom defined

units.If a parameter value is defined with a multiplier, the value is converted internally to a value withouta multiplier (e.g. 3kV is stored as 3000V).Using the digits after decimalthe default display of the parameter value can be controlled.For the predefined non SI unit cycles (cy), the input value is automatically converted internally thefollowing way:cy Value = Input / fn SI-Unit = s

It is recommended to use values, which represents the quantity in basic SI units.

Min Value and Max Value

Boundary values of the parameter. If these values are defined they are used to validate the input.

FormulaIt is possible to define a formula for a parameter value. Therefore, a parameter can be set directlywith a new value or the value is the result of an expression defined in the formula element.

17


18/38


5 Global Test Object with Multiple Function Blocks

Modern protection devices are getting more complex and include many protection functions. If deviceshave more than one protection function of the same kind, a Test Object needs to have multiple instancesof this device function. This was not possible in the RIO file technology, which was a drawback of RIO as

mentioned in chapter 2.2. A workaround was to insert multiple Test Objects in an OCC document whichcan be cumbersome.

A typical case is that a protection relay has more overcurrent functions. Another example is the use of onedistance function block for the tripping zones, another one for the starting zones, and eventually anotherone for the power swing detection zones.

The solution is that a function block can occur as often as needed in a Test Object but the instances needto have unique names. In the Test Object settings of a test module one of the available function blocks isselected as the active function block which is actually used in the test module.

Figure 17: Set RIO function block as active function in the Test Object

In an OCC document only one global Test Object needs to be included. In the test modules of the OCCdocument, a specific block is selected as the active function as shown above.

To reduce the complexity for the user, there are the following rules defined:

Each test module must have a corresponding function block. Therefore, a default function block isgenerated and filled with default values at startup of the Test Object.

One of the multiple function blocks of the same kind is the active one.

The local Test Object shows the settings of the currently assigned block.

In an OCC document, there are some additional aspects for the global Test Object to know:

A function block must exist, if a corresponding test module is embedded.

If a test module (e.g. Overcurrent) is inserted into an OCC document, then the default overcurrentfunction block is assigned to the module.

In the Test Object settings of a test module the assignment can be changed.

18


19/38


Figure 18: OCC document with a global Test Object, hardware configuration, and four test modules

A Test Object can change due to example by deleting a RIO function block or importing a RIO functionblock from a file in the XRIO organizer. In such situations the existing assignments to the availablefunction blocks remain as valid assignments. If an assignment could not be resolved the default functionblock is assigned.

19


20/38


6 Custom Section Create your own Parameters

The Customsection is used to map any type of relay specific parameter and other useful helperparameters. As mentioned earlier, it is organized in a tree structure. Each block can include parameters

and sub-blocks. The values of the parameters represent the current relay settings and are the inputvalues for an integrated XRIO converter which generates the RIO parameters in the RIO section. TheXRIO converter is described in detail in chapter 9.

Figure 19: Custom section with the relay parameter of the SEL-421 relay (advanced mode)

It is recommended to create the Customsection with the same structure as in the relay handbook or therelay settings software. The creation of the Customsection is done in the advanced mode. A tester worksin the standard mode and should be able to enter all the relay settings in the Custom section.

Mostly, availability of settings depends on logical conditions. For example, this means that only theparameters for enabled relay functions are editable. This mechanism should also be implemented in theCustom section. The figure below shows such an example of a logical condition.

Figure 20: Realize logic conditions in the Custom section

The two Boolean parameters in the Relay Configuration block specify if the blocks with the correspondingrelay function parameters are enabled and therefore visible in the Custom section in standard mode. Theadvantage of this logic is that the tester who works in standard mode only sees the important parametersfor the current relay configuration.

20


21/38


21

7 XRIO Scripting

All the calculations in the XRIO concept are implemented in a script-language. Microsoft VB.Net is used.The XRIO scripting is needed to create XRIO converter functionality. Generally, there are two cases

where XRIO scripting is used: Setting up formulas for parameter values and Enabled flags

Script Functionssection with useful global functions

There are some different rules for scripting in these two cases which are illustrated below. The VB.Netscripting language is a high-level programming language and is powerful enough to satisfy the needs ofexperienced programmers. Generally, all features of the .Net framework are available but only some ofthem are needed for XRIO.

The System.Mathnamespace is very useful for implementing formulas and script functions in the XRIOconcept. Therefore, it is included by default. This has the advantage that frequently used mathematical

operations can be written in the short form (e.g. TAN()instead of MATH.TAN()). Note that VB.Netscripting language is not case-sensitive.

In this manual only some basics of the VB.Net scripting language are shown which are typically neededfor modeling a XRIO converter.For detailed information on the VB.Net scripting language refer to theMSDN VB.Net documentation

1.

7.1 Setting up Formulas for Values and Enabled Flags

It is possible to calculate a parameter's value and an Enabledflag for parameters and blocks by formulas.A formula is a single-line expression with the structure result = formula expression.Therefore, formulasshould be as short and simple as possible. This can be achieved by implementing useful functions in theScript Functions section and use them in the formulas. The creation of these functions is described in 7.2.

The operands can be numbers, or other parameters (ID's) defined in the Test Object. These ID's are

references to other parameters and are added with a right-mouse click at the current cursor position in theformula. The dialog for inserting a formula reference shows the XRIO tree to select the desired parameter.Additionally, the reference ID name can be changed and the name path location in the XRIO tree isshown.

To calculate formulas of enabled conditions it is often necessary to compare an enumeration value withone of its definitions. Therefore this dialog also allows inserting enumeration value definitions. They canbe found as sub-nodes of the enumeration value in the tree.

1http://msdn.microsoft.com/library/en-us/vbls7/html/vbSpecStart.asp


22/38


Figure 21: "Add Reference" with "Insert Formula Reference" dialog

7.1.1 Basics about Formulas

The Test Object parameter values can be calculated from other parameters by formulas. These formulasare single-line expressions and are often one-to-one relationships to other parameters or simple formulasas shown below.

VNOM / SQRT(3) nominal voltage divided by square root of 3

(INOM IMEAS) / 2 nominal current minus measured current; difference divided by two

Z1ANG + 180 line angle plus 180 degrees

Figure 22: Example for parameter value formula expressions

Note that inserting or editing a parameter ID (e.g. Z1ANG) is not permitted in the formula field. It is onlypossible with the Insert Formula Reference dialog shown in Figure 21. Other tokens like operators,VB.Net mathematical function, and global functions of the Script Functions section are typed text.

Independent of the country settings the decimal separator is always the period.When several mathematical operators occur in an expression, they are evaluated in a predeterminedorder called operator precedence. The operator precedence corresponds to the common mathematicalconventions and is therefore not explained here any further.

Boolean expressions are used for block and parameter Enabled flags. The result of the Booleanexpression is the value for the Enabled flag.

22


23/38


Figure 23: Example for block Enabledflag formula

If a parameter is deleted, which is referenced in a formula of a parameter or block the following warning isdisplayed.

Figure 24: XRIO warning if a parameter for deletion is referenced in a formula

When a referenced parameter is deleted, all formulas using the ID of the deleted parameter are disabledbecause they can not be calculated anymore. The advantage of disabling the formulas instead of deletingthem is that they can be used again after enabling them. If the formula still contains errors after enabling,a script error message is displayed.

Figure 25: Enabling of disabled formulas (context menu)

The following section shows examples from the wide variety of possibilities and the most commonoperations in XRIO.

23


24/38


7.1.2 Arithmetic Operators

Operation Operator Example Result

Addition + 2.25+2.5 4.75

Subtraction - 5.5-3 2.5

Multiplication * 3.25*2 6.5Floating point division / 11 / 4 2.75

Integer division \ 11 \ 4 2

Exponentiation ^ 2.5 ^2 6.25

pow pow(2.5,2) 6.25

Square root sqrt sqrt(3) 1.732

Trigonometric functions sin sin(30 * PI/180) 0.5

(arguments in Radians) cos cos(45 * PI/180) 0.71

7.1.3 Comparison Operators

Operator True if False if

< (less than) expression 1 < expression 2 expression 1 >= expression 2

(greater than) expression 1 > expression 2 expression 1 = (greater than or equal to) expression 1 >= expression 2 expression 1 < expression 2

= (equal to) expression 1 = expression 2 expression 1 expression 2

(not equal to) expression 1 expression 2 expression 1 = expression 2

7.1.4 Logical Operators

Boolean Operation Operator Example Result

Logical and AND 23 > 12 AND 12 > 4 true

Logical or OR 23 > 12 OR 4 > 12 true

Logical negation NOT NOT 23 > 12 false

7.1.5 IIF Statement

As mentioned, formula expressions in XRIO can only by single-line expressions. Therefore, the IIF statement, which is a one-line IF-ELSE statement of VB.Net, is useful for creating formulas. It returns oneof two values, depending on the evaluation of an expression.

iif(expression, trueValue, falseValue)

If the expression is true, the trueValueis returned as the result, otherwise the falseValue.

Figure 26: Example of an IIF Statement (NFREQ enumeration shown in Figure 16)

24


25/38


7.1.6 Predefined References

A set of frequently used parameters are available in formulas as a list box. In the context menu offormulas there is an item Predefined Referenceswhich opens a list box. The shortcut Ctrl+Shift+I alsoopens the list box in a formula field to select one of the listed parameters.

Figure 27: List box with often used parameters in formulas (Ctrl+Shift+I)

7.2 Script Functions Section with Global Functions

For a comfortable creation of XRIO converters it is necessary to define arbitrary global functions.Therefore, the Test Object has a development environment for creating and editing functions in theVB.Net script language. These global functions are placed in the Script Functionssection of the TestObject. The syntax is checked by the integrated compiler. A complex script development is only possiblewith an additional debug feature.

An example for a useful global function is the calculation of the constraint for drawing the line element 4 ofthe quadrilateral distance protection zones in the SEL-421 protection relay. The quadrilateral grounddistance zone 1 is defined with the relay parameters resistive reach RG1, reactive reach XG1, and lineangle Z1ANG in the Customsection. The appropriate RIO parameters for this zone in the RIOsection canbe referenced to these parameters with formulas. Depending on the SEL-421 relay configuration (R1G,

X1G, Z1ANG) the line element 4 of the quadrilateral zone 1 may not exist. This constraint for the lineelement 4 is graphically illustrated in the figure below.

Figure 28: Constraint for line element 4 of quadrilateral zone (SEL-421)

25


26/38


The line element 4 only exists when the following constraint is true. Otherwise the element is disabled andthe shape only exists of three remaining line elements.

)1cos( ANGZ

XGRG <

Since the same constraint is used for all the quadrilateral ground distance zones, it is useful to define afunction in the Script Functions section, which calculates the right side of the equation.

The following figure shows the Script Functions section for the Schweitzer SEL-421 User Manual.xrio file(located in OMICRON Test Library) with the function to calculate the constraint for the line element 4 ofthe quadrilateral distance protection zones.

Figure 29: Script Functions section for global functions (e.g. SEL-421 constraint)

The constraint is used for the Enabledflag of the line element 4 (e.g. for zone 1). The verification of theconstraint can be done directly in the formula field of the Enabledflag as shown below.

Figure 30: Calculation of the constraint for line element 4 in the block Enabled formula

As an alternative the constraint can be verified in a new Boolean helper parameter in the Customsection.In this case, only the helper parameter has to be referenced in the formula field of the Enabledflag for theline element 4. The Enabled flag of the blocks in the Custom section which contain such helperparameters should be false. As a result, these blocks are not visible in the standard mode, which isdescribed in detail in chapter 3.2.

Figure 31: Definition of the constraint as a Boolean helper parameter in the Customsection

26


27/38


7.2.1 Programming in the Script Functions Section

Note that the angle values have to be converted into Radians for the calculation with trigonometricfunctions. For example, this can be solved by a multiplication with a defined constant Deg2Radas shownin Figure 29.

The implementation of functions in the Script Functions section of XRIO does not require muchprogramming skills. Generally, the following things should be known to create script functions in a TestObject.

Defining Constants:

Const c1 as Integer = 10

Defining Variables:

Dim R as Double

Structure of a Function:

Function TheFuncName(Par1 As Double, Par2 As Double) As DoubleDim R As Double

Const Deg2Rad As Double =PI / 180R = Par1 + Par2Return R

End Function

Public and Private Keywords:

Each constant, variable, and function can be defined as a public or private member. Publicmembers can be used in the whole Test Object. This means they are also available in theformulas for parameter values and Enabled flags. If a member is declared as private in the ScriptFunctions section, it can only be used inside the Script Functionsection.

Shortcuts to insert templates for constants and functions:

It is a common task to create constants and functions in the Script Function section. Therefore, a

context menu offers a quick way to insert templates for constants and function, which can also bedone with the appropriate shortcuts shown below.

Figure 32: Shortcuts to insert templates for constants and functions

27


28/38


7.2.2 Adding Script References

It is also possible to reference other VB.Net or own assemblies into a XRIO file. This is done with theReferences button. Script references can be included from files or the GAC (global assembly cache).

Figure 33: Add a script reference

All the functions defined in the added script references can be used in formulas and the Script Functions

section of the XRIO file.Note that the fully qualified names for assembly members and operations have to be used.

7.2.3 Compilation and Execution of the Script in the Background

A VB.Net script with all the formulas and the functions in the Script Functions section is automaticallygenerated. This script is compiled after any code changes in the Test Object or when a user forces thescript compilation by pressing the Compile button in the Script Functions section. If a parameter value ischanged which is involved in a formula, the script is executed.

28


29/38


8 Organizing XRIO files

Unlike RIO, the XRIO concept implements a Test Object with a very variable content. This new conceptneeds a tool to organize the content of the Test Object or an XRIO file. Typical operations with the XRIO

organizer are: Save a subset of blocks to an XRIO file

Get blocks from an existing XRIO file

Put blocks into an existing XRIO file

Delete blocks from the current Test Object

Duplicate blocks in the current Test Object

There are many different use cases where these operations of the XRIO organizer are used. An examplescenario is that over time several XRIO converters are developed for a device. Maybe one XRIOconverter supports the distance protection and another one supports the overcurrent protection. Thesoftware does not have to merge two XRIO converters automatically into one file. The XRIO organizer can

be used to merge two converters temporarily.

With the menu FILE | ORGANIZE in the advanced mode a Test Object and a XRIO file can be organized.The organizer includes two XRIO trees as shown in the figure below.

Figure 34: XRIO organizer

8.1 Left Tree The Test Object

The left tree holds the current Test Object. Two buttons provide functions for deletion and duplication ofblocks. A duplication of a block generates a copy of the selected block at the same location in the treestructure. The ID of the copied block is derived from the original ID by appending a number. In the RIOsection only the RIO function blocks and blocks in a collection of equal block types can be duplicated.

The organizer can be closed with the OK button for saving or with the Cancel button for discarding the

changes made to the current Test Object.

29


30/38


8.2 Right Tree The XRIO File

The right tree holds an XRIO file. At startup time of the organizer the tree is empty. RIO or XRIO files canbe imported into the right tree which represents a temporary XRIO file. After merging of the two trees asdescribed below, the content of the right tree can be exported into a new RIO or XRIO file.

8.3 Merging the two Trees

Single parts of the two trees can be merged in both ways. Therefore, there are two buttons with arrows indifferent directions between the two trees. Generally, the block which should be moved from one tree tothe other has to be selected. In the other tree the destination location can be selected. These buttons willbe enabled or disabled depending on the selected blocks in both trees because some block types canonly be moved to predefined locations.

If an arrow button is enabled, a tool-tip is shown moving the mouse pointer over the button. This tool-tipexplains which block is moved to which destination location if the arrow button will be pressed. In Figure34there is an example for such a tool-tip shown.

There are some block types which can only be moved to a predefined location in a tree. In these casesthe destination in the other tree needs not to be selected because the blocks move to the correctdestination automatically. For all the other blocks the destination is defined by the current selection in theopposite tree.

8.3.1 Blocks with fixed Destination

Script Functions sectionReplaces the Script Functions section in the destination tree with the Script Functions section insource tree.

Custom sectionCopies all blocks in the Custom section of the source tree to the Custom section in the destinationtree. Identical blocks (same ID's) can be overwritten or skipped and new blocks are added to theCustom section of the destination tree.

Custom section blocks (no selection in the Custom section of the destination tree)Insert the selected block in the source tree as a child of the Customroot block of the destinationtree.

RIOsectionCopies the RIO section of the source tree to the destination tree. Identical blocks (same ID's) canbe overwritten or skipped and new blocks are added to the RIO section of the destination tree.

Sub blocks of the RIO root blockInsert the selected block in the source tree as a child of the RIO root block of the destination tree.

8.3.2 Blocks with variable Destination

Custom section blocks (destination is specified in the Custom section)If there is a sub block in the Custom section of the destination tree selected, the moved bock willbecome a sub block of this block.

All blocks in the RIO section except the sub blocks of the RIO root blockThe right destination according to the RIO specification has to be selected in the destination tree.

30


31/38


9 XRIO Converter Input Genuine Relay Settings

The test modules work with the RIO parameters represented in the RIO format. Mostly a tester has onlythe relay settings from the data sheet or the relay software. Therefore, a RIO converter is needed togenerate the RIO parameters from the original relay settings. In the OMICRON Test Library there are

many RIO files for different protection devices available which have predefined values for a typical deviceconfiguration.

In the past, the term RIO converter was used for a utility, which generates the RIO data from the originalrelay settings and stores the result in a RIO file. The new XRIO concept has a so called XRIO converterintegrated in the XRIO data structure, so that the transformation logic is part of the XRIO file.

XRIO converters are distributed in XRIO files for various protection or measurement devices. These nextgeneration Test Object templates contain the relay settings in the Custom section and automaticallycalculate the RIO parameters in the RIO section. The RIO parameters depend on the relay parameters infollowing ways:

Parameters correspond to a relay parameter in a one-to-one relation

Parameters can be calculated from relay parameters with a simple formula (e.g. Z = ZSM / 2)

The number of items in a collection of blocks or parameters depends on the relay settings

Note that the XRIO converter logic is not protected. Any user can read and copy the complete content ofthe file including values, formulas and constraints.

The integrated XRIO converter uses the formula field of a parameter to calculate its value from otherparameters. The formulas of the Enabled flag are used to determine if blocks and parameters are enabledor not. The operands of these expressions are mainly relay parameters of the Custom section. A formulacan use any parameter in the Test Object as an operand. Circular references are not permitted andtherefore detected.

A XRIO converter must implement this mechanism for at least one of the RIO function blocks. If a XRIOconverter supports a RIO function block, the parameters of this block must be calculated from relay

settings, wherever possible. The final goal of the integrated XRIO converter is that only the relay settingsdescribe the Test Object.

The following figure shows the different sections of a XRIO file with its dependencies. It is obvious that theRIOsection is generated out of the Custom and Script Functions section.

XRIO file

RIO Section:

The Enabled flag andthe RIO parametervalues are calculated.Script functions and

parameter identifiers areused in formulas.

Only a designer of aXRIO converter needsto modify this section. Atester has only accessto the classic userinterfaces.

Custom Section:

Blocks with relaysettings. Eachparameter has a uniqueidentifier.

The UI shows theparameters in a table.The tester can modifythe values.

Script FunctionsSection:

Global scriptfunctions.(e.g. for constraint

calculation,)

Figure 35: XRIO Test Object with its dependencies

31


32/38


It is recommended for a designer of a Test Object with integrated XRIO converter to use the followingsequence of steps. Note that a designer has to work in the advanced mode.

Step 1: Create the Block Structure in the RIO Section:

If there exists a RIO file for the protection test object in the OMICRON Test Library, this RIO filecan be imported into the Test Object to fill the RIOsection with the appropriate data.

Some relay manufacturer offer a RIO export option in their relay software. The resulting RIO filecan also be imported into the Test Object to generate the structure in the RIOsection.

Additional RIO functions blocks can be added. This is also used when there is no RIO fileavailable for a protection test object and the RIO block structure has to be created from scratch.The following dialog box shows all possible RIO functions blocks which can be added.

Figure 36: Add new test module function blocks to the RIO section

These RIO function blocks are filled with the default values which can be changed in thecorresponding classic user interface.

It is recommended that designers always generate the maximum content in the RIO sectionwith the classic user interface before adding formulas in step 4 (e.g. maximum zone elementsfor distance protection zones).

Step 2: Create Relay Parameters in the Custom Section:

The designer uses the generic user interface to add blocks with parameters in the Customsection. These parameters map the relay parameters with their current settings and additionalhelper parameters for the XRIO converter.

It is recommended to use the same structure in the Custom section as in the relay handbook orthe relay software.

Step 3: Add Global Functions in the Script Functions Section:

Global function can be added into the Script Functionssection of the Test Object. Thesefunctions are written in the VB.Net scripting language and can be used in any formula field ofany parameter in the generic user interface.

Step 4: Add Formulas for the XRIO Converter Functionality in the RIO Section:

In the generic user interface, formulas can be added for calculation of parameter values in theRIOsection. Additionally formulas for the Enabledflags of parameters and blocks can bedefined. All parameters and script functions can be used in formulas.

After completing the design a Test Object with XRIO converter functionality has to be verified. There is arecommended checklist for testing of XRIO converter in the following chapter. Sometimes it can benecessary to debug a XRIO converter.

32


33/38


10 Testing and Debugging of XRIO Converter

During the creation of a Test Object with XRIO converter functionality, error messages and warnings willpossibly show up in the Errors view. These messages have to be eliminated by removing their cause. TheXRIO converter functionality can be tested by changing relay parameters in the Custom section and

analyzing the changes of the related RIO parameters in the RIOsection. For a verification of a XRIOconverter the following conditions should be fulfilled.

Checklist for a XRIO Converter

All device parameter can be entered in the Custom section

Limits and default values match the ones from the device

Minimum and maximum values do not lead to problems within formulas (e.g. invalidcharacteristics)

All formulas and functions used in the Test Object are used and verified

One test plan for each protective function of the relay is created

One real world test for each protection function is performed

Besides the recommendations listed above, the most important thing is that there is no need for the userto enter RIO parameters.

As mentioned, syntax errors and warnings are shown in the Errors view but there is no information abouta calculation in the XRIO converter which returns a wrong result. If there are many complex formulas andscript functions in a XRIO converter, it is difficult to find the reason for such a wrong calculation. For thistask, the Test Object offers the possibility of debugging. The debug feature is available in the ScriptFunctions section. The associated debugger loads the VB.Net script which is always generated in thebackground of the Test Object. This VB.Net script includes all formulas and script functions of the TestObject. Setting of breakpoints in the debugger makes it easy to analyze critical parts of the XRIOconverter and watch the results of each single calculation. The following figure shows the debugging ofthe script function for the calculation of the constraint of line element 4 of quadrilateral zones in the

SEL-421 protection relay. For this example, the Microsoft Common Language Runtime (CLR) debugger isused.

Figure 37: Debugging of the SEL-421 XRIO converter with the CLR Debugger

33


34/38


34

Requirements for Debugging

For the debugging of a XRIO converter, an external debugger is needed. If there is no debugger installedon the machine, the free .Net Framework Software Development Kit (SDK) 1.1 can be used. The SDK canbe downloaded from the internet

2. After the installation of the .Net Framework SDK the including CLR

debugger has to be started (the default installation location isC:\Program Files\Microsoft.NET\SDK\v1.1\GuiDebug\DbgCLR.exe). The just-in time debugging option for"Common Language Runtime"has to be enabled in the CLR debugger options.

Figure 38: Enabling just-in time debugging for "Common Language Runtime" in the CLR debugger

2http://www.microsoft.com/downloads/
http://www.microsoft.com/downloads/http://www.microsoft.com/downloads/http://www.microsoft.com/downloads/http://www.microsoft.com/downloads/


35/38


35

11 Filters

Typically, the Custom section holds the relay specific settings. If the configuration of a test object ischanged, the same changes have to be applied to the parameters in the Custom section. This can be a lotof work if there are many relay parameters involved. Additionally, it has to be verified that the

configuration values of the physical test object are identical with the parameter values in the Customsection.

For the automation of these tasks, filters can be used. A filter is software that reads/writes data from/to anexternal source. A standard XML filter is shipped with the OTU. User specific filters can be developed andinstalled if necessary.

Figure 39: Filling the parameters of the Customsection with the standard XML filter

If another data format is used a corresponding filter is needed.

The structure of a filter allows import and export functionality. Some filters will provide both, some onlyimport depending on the usage of the filter.

There are many situations where it is useful to import data from a different source outside the OTU. Forexample, this can be a relay settings file of any format created by a relay software. In this case, the valuesof the parameters in the Customsection have to be updated. Another scenario is that relay settings fromIEC61850-conformant devices will be read either from a file or even directly from a protection device. Thedata input is not only possible from a file but in general from any source.

Normally, a filter only manipulates the data in the Customsection. However, there is the possibility to

change the complete XRIO tree.

Filters are accessed via the FILE | IMPORT RELAY SETTINGS menu in the Test Object. Thefollowing dialog offers the possibility to select one of the available filters and set it as the default one.Export is in the moment only accessible via Automation.

Figure 40: Relay settings import with filters

The Standard Filter for XML Files which comes with the OUT is simple and effective. This filter reads anXML file which contains the current relay configuration and performs an update of the parameters in theCustom section. The XML file must have the same structure as blocks and parameters in the Customsection. Every relay parameter which is found in the XML file depending on the ID path is updated in theCustom section.

If a relay manufacturer wants to supply a XRIO converter with configuration data from the relay softwarethere is just an XML export option needed to generate an appropriate XML file. The manufacturer thatexports this structure does not have to provide any additional software.

RelaySoftware

XMLFile

Standard XMLFilter

Export Functionfor Relay

Parameter Values

Test Object


36/38


An excerpt of a XML file with configuration data of the SEL-421 protection relay is shown below. This XMLfile can be used to update the Custom section's relay parameters of the SEL-421 XRIO converter with thestandard XML filter.

58424.8081.50

404

RFF

46101015

Note that filters can be developed separately and added as additional packages to the OTU.

36


37/38


12 Fully Parameterized Tests LinkToXRIO

The test modules in the OTU can link most test settings to any Test Object parameter. This concept iscalled LinkToXRIO.

In the RIO concept all test modules had access to the parameters of the DEVICE block in the RIO file.The function specific test modules had in addition access to the set of protection specific parameters. Forexample it could be useful, if the State Sequencer module could link a value directly to a parameter fromthe Overcurrent block. This is possible with the LinkToXRIO concept.

A typical use case is in the Ramping module to ramp a current from a minimal to a maximal current. It isan obvious wish to define these values for example as IMin= 0.9 IPickUpand IMax= 1.1

.IPickUp.This is possible,

if IPickUpis used as the reference value for IMinand IMax. We would say, IMinand IMaxare linked to theparameter IPickUp.

Figure 41: LinkToXRIOin the Ramping module (relative mode)

Establishing a Link

All Test Object parameters are potential targets for a link. From possibly hundreds of parameters only a

few parameters will be mostly used for linking. It is recommended to use a short name for a linkedparameter, because the user interface must show the value as 'Factor Name'.

The dialog to link a test setting to a Test Object parameter is launched from the context menu of the testsetting.

Figure 42: LinkToXRIOin the context menu of a value in the Test view

LinkToXRIO is only possible if this feature is activated for the value. This command opens a dialog tobrowse the XRIO tree. The LinkToXRIO dialog remembers the last selected parameter to reconstruct thestate of the tree from the last usage. If the dialog is called for an already linked value, then the linkedparameter is selected.

37


38/38


Figure 43: Selecting a parameter for LinkToXRIO

The link name is predefined with the name of the selected parameter. Since the length of this name is notrestricted and the test module user interface need short names, the user can change the name.Additionally, the factor for the linked parameter can be defined. The test module in relative mode shows'Factor Name' and in absolute mode it shows the result of the multiplication Factor* Name. A tool tip for alinked value shows the full XRIO path of the parameter plus the current value.

Figure 44: Tool tip of a linked parameter (relative mode)

As shown in the figure above, test results can also be linked to XRIO parameters (e.g. Act., Dev.). Forsuch fields, no factor for the linked parameter can be defined. By doing so, test results will be displayedrelative to the linked parameter.

xrio user manual

Documents