January 2016 Page 7–11
Chapter 7. Communication Protocols
7
<Private type="AMETEK_GooseSubscription">
<eapi:GooseSubscription iedName="SEL_421_1" ldInst="CFG" cbName="Conf" datSet="PLC"
confRev="1" mAddr="01-0C-CD-01-00-02" maxTime="500" vlanPriority="4" appId="SEL_421_1"
goCbRef="SEL_421_1CFG/LLN0$GO$PLC" datSetRef="SEL_421_1CFG/LLN0$PLC">
<eapi:GooseRxEntry gooseData="FSKTripTestDisable" type="Bool" />
<eapi:GooseRxEntry gooseData="ONOFFCarrierStart" type="Bool" />
<eapi:GooseRxEntry gooseData="ONOFFCarrierStop" type="Bool" />
<eapi:GooseRxEntry gooseData="ONOFFCheckbackReset" type="Bool" />
<eapi:GooseRxEntry gooseData="UPLCNoFunction" type="Bool" />
<eapi:GooseRxEntry gooseData="UPLCNoFunction" type="Bool" />
</eapi:GooseSubscription>
</Private>
Figure 7–7.
Example GOOSE Subscription Block
7.5.3 Overview
The UPLC-II™ is capable of using the Configured
IED Description file as a means of defining the
communications parameters and the data of
GOOSE Messages that the user needs the UPLC-
II™ to “listen” to and perform functions based upon
the data received. This definition of the Goose mes-
sage is accomplished by using an IEC private data
block containing the information in a structured
manner. The private data block is contained within
the UPLC-II™’s .cid file, and can be edited to pro-
duce the desired data to function mapping.
When editing the .cid file, you should use a non-for-
matting editor such as Windows
®
Notepad, or if a
formatting editor is used then be sure to save the file
as a plain ASCII text file. The SCL interpreter is
sensitive to embedded formatting characters, or
ANSI escape sequences. If the .CID file contains
these characters the file will not load.
Figure 7–7 shows an example of the UPLC-II™
<Private /> GOOSE subscription block.
The color coding is as follows:
Green
–
The
<Private>
</Private>
block
as
described in the IEC61850 section “Private
parts”
Blue – The UPLC-II™ private definition of a
“GooseSubscription”.
Proper XML and IEC formatting require the use of
a “Private namespace” denoted by the eapi: prefix,
and an opening item paired with a closing item. i.e.
< e a p i : G o o s e S u b s c r i p t i o n > . . . . . . . . . . . . . . . .
</eapi:GooseSubscription>. Note that all IEC defi-
nitions ARE case sensitive. The GooseSubscription
contains the communication parameters, and the
IEC data that uniquely identify the incoming
GOOSE. Due to publication formatting, this line
has been split into multiple lines, but in the actual
.cid file, it is one long line.
Orange – order sensitive multiple definitions
that correspond with the data order of the
incoming GOOSE message.
These definitions allow the UPLC-II™ to call func-
tions based upon the incoming data value. Note that
the number of definitions MUST correspond to the
number of data items contained in the received
GOOSE message, EXACTLY. For example, if the
GOOSE message contains 6 items, then there
MUST be 6 definitions. This is true regardless if the
data is to be used by the UPLC-II™ as an input to
the function or if the UPLC-II™ is to ignore the
data. The null function “UPLCNoFunction” is pro-
To Next Page
Loading...
Need help?
General