Annex - Optional Intermediate Goose Reception Objects; Logical Nodes Communicate With Logical Nodes - GE UR Series Manual

Hide thumbs Also See for UR Series:
Table of Contents

Advertisement

G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
<LDevice inst="LD1">
<LN0 inst="" lnClass="LLN0" lnType="LN0">
<DataSet name="GOOSE1DS">
<FCDA ldInst="LD1" prefix="" lnClass="PIOC" lnInst="1" doName="Op" fc="ST" daName="general"/>
</DataSet>
<GSEControl name="GoCB1" datSet="GOOSE1DS" appID="E1Q1BP1LD1_GOOSE1"/>
</LN0>
<LN lnClass="PIOC" inst="1" lnType="PIOC">
<DOI name="Op" desc="Instantaneous Overcurrent Operated" />
</LDevice>
</Server>
</AccessPoint>
3
</IED>
<DataTypeTemplates>
...
In this simple case, the rest of this file is the same as the ICD file.

3.10.8 Annex - Optional intermediate GOOSE reception objects

3.10.8.1 Introduction
IEC 61850 standards require that "logical nodes communicate with other logical nodes" (IEC 61850-7-1 Edition 2.0 2011-07
clause 9.6). That is to say, from an application viewpoint, the logical nodes (and only the logical nodes) can be understood
as being in communication with one another. As illustrated in the following figure, the receiving logical nodes directly
reference the sending logical node without an intermediate object in either the sending IED or the receiving IED. This is
accomplished in the preceding implementation model through the use of an ORG object in the receiving logical nodes that
contains a reference to the sending logical node.
3-176
Figure 3-17: Logical nodes communicate with logical nodes
Sending IED
Logical Node
Op
GOOSE
ACT
CHAPTER 3: IEC 61850 COMMUNICATION
Receiving IED
Logical Node
InRef1
ORG
Reference
Logical Node
InRef1
ORG
Reference
Logical Node
InRef1
ORG
Reference
859737A1.vsd
UR SERIES – COMMUNICATIONS GUIDE

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents