1
00:00:22,955 --> 00:00:23,627
XRIO

2
00:00:23,652 --> 00:00:29,338
The first matter that should be discussed in the “XRIO” part of the instruction is the reason for turning to these files.

3
00:00:29,363 --> 00:00:33,758
The first reason was that “RIO” files did not have a specific set of standards for coding.

4
00:00:33,783 --> 00:00:39,864
For example, if from the list of “RIO” files of the relays on the “Load XRio and Rio File From list”page

5
00:00:39,889 --> 00:00:49,774
which is provided in the software, the (lz91-lz92rio) and (11-6-1rio) files are opened in the notepad,

6
00:00:49,799 --> 00:00:55,603
you can see that these two files have different coding and there is no specific standard to them.

7
00:00:55,628 --> 00:01:01,094
The second reason was that when an "RIO" file was loaded, only "RIO" information was available.

8
00:01:01,119 --> 00:01:05,378
"RIO" information is that into which all relay settings can be translated.

9
00:01:05,403 --> 00:01:11,475
For example, when “Distance” characteristic of the “Micom” relay is translated and the characteristic curve is formed,

10
00:01:11,500 --> 00:01:15,025
, there is some information that is not inserted into the software.

11
00:01:15,050 --> 00:01:19,124
For example, it is possible that it exists in the relay of “Power swing blocking” function

12
00:01:19,149 --> 00:01:24,890
but its information is not inserted into the “RIO” because, basically, it is not possible to do so.

13
00:01:24,915 --> 00:01:30,109
The third reason was that specification changes of the relay were not the same in relay and the software.

14
00:01:30,134 --> 00:01:34,695
It means that, if the user made a change to the translated “RIO” which was a known format,

15
00:01:34,720 --> 00:01:41,284
it is not clear that which settings needed to change in the relay so that it could follow the curve of specified characteristics.

16
00:01:41,309 --> 00:01:47,890
The fourth reason was that if a parameter was changed from the setting of the relay, it was necessary to get those settings, again,

17
00:01:47,915 --> 00:01:50,549
from the “RIO” relay and this file had to be loaded

18
00:01:50,574 --> 00:01:55,236
and translated in the software so that the relay and software settings were exactly the same.

19
00:01:55,261 --> 00:02:01,385
The second important matter which is related to “XRio” is that the user needs to know the components of an “XRio” file

20
00:02:01,410 --> 00:02:04,520
and what happens when it is loaded in the Vebko software

21
00:02:04,545 --> 00:02:11,189
To explain this a little further, a “XRio” file is loaded from the “Micom p441” relay,

22
00:02:11,214 --> 00:02:15,251
You can see that the first thing that happens is that a “SCRIPT FUNCTION”

23
00:02:15,276 --> 00:02:18,957
and a tree diagram of the settings are formed in this section of the software

24
00:02:18,982 --> 00:02:23,873
In the end, the “RIO” which is a translated version of the relay characteristics is completed.

25
00:02:23,898 --> 00:02:29,041
We will discuss more the concept of “XRIO” and its components in future videos.