GE B30 Communications Manual page 252

OVERVIEW
• .iid — Actual settings on UR — An Instantiated IED Description (IID) SCL file describes a specific IED to a system
configurator tool, typically more or less as configured for its role in the system. For UR 7.30 and later, an IID file
includes all the data attributes of the UR device, control blocks and settings, with setting values all as they were at the
moment that the IID file was generated. A copy of it can be obtained directly from a UR device or from EnerVista UR
Setup. If obtained from the EnerVista UR Setup Offline Window, the settings are from the URS file selected. See the next
section for more information.
• .sed — A System Exchange Description (SED) file is intended for configuration exchange between system
configurators of different projects. This file describes the interfaces of one project to be used by the other project, and
as such is not used by UR 7.30 and later.
3.1.8.2 SCL file example
To illustrate what an SCL file looks like, this section presents parts of an ICD file generated by a D60 UR with firmware 7.40.
The following appears at the beginning of UR SCL files. The first line identifies this file as an XML formatted file. The second
3
line is a comment unique to UR devices. The third line indicates that it is an SCL file conforming to IEC 61850-6 edition 2.0
schema revision "B." The fourth line is a mandatory element that can be used by SCL tools to identify the specific
configuration in this file and its version.
1 <?xml version="1.0" encoding="UTF-8"?>
2 <!--Created by GE Digital Energy UR 7.40 on Tue Dec 1 05:38:26 2015-->
3 <SCL xmlns="http://www.iec.ch/61850/2003/SCL" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
instance" xsi:schemaLocation="http://www.iec.ch/61850/2003/SCL SCL.xsd" version="2007" revision="B"
xmlns:eGE="http://www.gedigitalenergy.com/multilin">
4 <Header id="" nameStructure="IEDName"/>
Following the Header element is the Communication element. The Communications element contains a ConnectedAP
element for each of the three UR Ethernet ports. Each ConnectedAP element is within its own SubNetwork element, as it is
expected that each Ethernet port is connected to a separate network. Ethernet port 1 has ConnectedAP apName S1, while
port 2 is S2 and port 3 is S3. The Address element at line 9 contains the IP address of the S1 port. The GSE element at line
20 contains address information of the first TxGOOSE, the interval to the first TxGOOSE message retransmission following
an initial event message (MinTime), and the time allowed to live value. In the ICD file but not shown here, following this are
the GSE elements for the remaining TxGOOSE, and then the SubNetwork elements for the other Ethernet ports, which are
similar to the first.
5 <Communication>
6 <SubNetwork name="W1">
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
3-14
<ConnectedAP iedName="TEMPLATE" apName="S1">
<Address>
<P type="IP">127.0.0.1</P>
<P type="IP-SUBNET">255.0.0.0</P>
<P type="IP-GATEWAY">127.0.0.1</P>
<P type="OSI-AP-Title">1,3,9999,1</P>
<P type="OSI-AE-Qualifier">12</P>
<P type="OSI-PSEL">00000001</P>
<P type="OSI-SSEL">0001</P>
<P type="OSI-TSEL">0001</P>
<P type="OSI-AP-Invoke">102</P>
<P type="OSI-AE-Invoke">103</P>
</Address>
<GSE ldInst="Master" cbName="GoCB01">
<Address>
<P type="VLAN-ID">000</P>
<P type="VLAN-PRIORITY">4</P>
<P type="MAC-Address">01-0C-CD-01-00-00</P>
<P type="APPID">0000</P>
<P type="TransportInUse">0</P>
<P type="IPClassOfTraffic">46</P>
<P type="IPv6FlowLabel">0</P>
CHAPTER 3: IEC 61850 COMMUNICATION
UR FAMILY – COMMUNICATIONS GUIDE