GE B30 Communications Manual page 481

Universal relay family
Hide thumbs Also See for B30:
Table of Contents

Advertisement

CHAPTER 3: IEC 61850 COMMUNICATION
G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
Each GSE element is to contain one Address element, one MinTime element, and one MaxTime element. The Mintime
element contains the factory-configured value of the sending delay on a data change between the first immediate
sending of the change and the first repetition (the value of T1 in IEC 61850 8 1:2011 Figure 8). The Maxtime element
contains the factory-configured value of the source supervision time in ms (within this time a failed message from the
source is to be detected by the client, some multiple of the time T0 in IEC 61850 8 1:2011 Figure 8).
Each of the Address elements of the previous paragraph is to contain four P elements: one with type="MAC-Address"
containing the factory configured destination address of the GOOSE message, one with type="APPID" containing the
Application Identification number as four hexadecimal characters, one with type="VLAN-ID" containing the VLAN ID
number as three hexadecimal characters, and one with type="VLAN-PRIORITY" containing the VLAN priority code.
Each GSE element in a given ConnectedAP element is to reference a different GOOSE control block using its cbName and
ldInst element attributes. GSE elements in different ConnectedAP elements can reference the same GOOSE control block
provided all GSE elements referencing a given GOOSE control block have the same address and time values.
3
3.10.4.5 IED element
The IED element is to have an element attribute name with a value equal to the factory-configured IED name, which is
"TEMPLATE".
The IED element is to contain one Services element. This Services element is to contain a GSESettings element having
element attributes cbName, datSet, and appID. The values of each of these element attributes are to be "Fix", "Conf", or
"Dyn", depending on how the GOOSE control block attributes GoCBName, DatSet, and GoID can be modified. The value is
to be "Conf" when the element attribute value can be modified via CID file transfer to the IED but not via MMS
communication services, "Dyn" when the element attribute value can be modified via MMS communication services and
via CID file transfer to the IED, and otherwise is to be "Fix".
The Services element also contains a GOOSE element having element attribute max. The value of this element attribute is
set to the maximum number of GOOSE control blocks that the IED can support (max="0" means the IED is only a GOOSE
subscriber).
The Services element is not to contain a ClientServices element with element attribute called goose.
The IED element also contains one AccessPoint element corresponding to each ConnectedAP element required for the
Communication element. Each of these AccessPoint elements is to contain a Services element that in turn contains a
ClientServices element having element attribute goose="true". Each of these AccessPoint elements also is to contain one
GOOSE element. These GOOSE elements are to have element attribute max with value equal to the number of GOOSE
messages that can be transmitted on the port. The IED element can contain other AccessPoint elements, but these are to
have a ClientServices element having element attribute goose="false".
One of the AccessPoint elements is to contain one Server element. All other AccessPoint elements are to contain one
ServerAt element having element attribute apName with value equal to the name of the AccessPoint element containing
the Server element.
The Server element is to contain at least one LDevice element. Each LDevice element is to contain one LN0 element.
The LN0 elements are to contain amongst them a GSEControl element for each GOOSE control block that the IED is
capable of implementing. In cases where the IED element contains multiple LN0 elements, the GSEControl elements can be
distributed among the LN0 elements in any fashion.
Each GSEControl element is to have element attributes name, appID, and confRev. In cases where there is a factory-
configured GOOSE dataset, the GSEControl element also is to have element attribute datSet. The datSet element attribute
is to be omitted where the dataset is not factory-configured. The value of these element attributes are to be the factory
configured values of the GOOSE control block attributes GoCBName, GoID, and ConfRev respectively. If element attribute
datSet exists, its value is to be the factory-configured value of the GOOSE control block attribute DatSet.
Each GSEControl element having a datSet attribute is to have a corresponding DataSet element located in the same LN0
element as the GSEControl element. Each DataSet element is to contain an FCDA element for each factory-configured
member of the dataset. The FCDA elements can reference any data attribute defined in the Server element that the IED is
capable of publishing via GOOSE. FCDA elements are not to reference data objects (that is, omit the daName element
attribute) except where the IED and all subscribing IEDs are capable of using such in GOOSE messages.
UR FAMILY – COMMUNICATIONS GUIDE
3-243

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents