Ametek UPLC CU44-VER04 Applications Manual page 123

You are encouraged to seek the relevant sections of
the standards for further information regarding
GOOSE message definitions.
For the purposes of this section, it is necessary to
determine the number of entries in the GOOSE
message subscription, what type they are, and the
order the entries are in.
For each entry in the GOOSE message there MUST
be a corresponding entry in the UPLC™
GooseSubcription block. Both the order and the
number of entries must be exact.
Note: The UPLC™ at this time is only capable of
receiving BOOLEAN entries from a GOOSE mes-
sage.
As an example, suppose that IED "OaklandPark" is
issuing a GOOSE message containing the follow-
ing:
<Communication>
< SubNetwork name="W01" type="8-MMS">
<ConnectedAP iedName="OaklandPark" apName="S1">
<GSE ldInst="C1" cbName="TripControl" >
<Address>
<P type="MAC-Address">01-0C-CD-01-00-01</P>
<P type="APPID">1001</P>
<P type="VLAN-PRIORITY">4</P>
</Address>
<MaxTime unit="s" multiplier="m">500</MaxTime>
</GSE>
</ConnectedAP>
</SubNetwork>
<Communications>
(The above example is edited to show only the
items that are needed to define the UPLC™
GOOSE subscription. In an actual .cid file, there
will be more blocks between <ConnectedAP> and
</ConnectedAP> defining the systems' OSI
addressing, and optionally other interfaces, such as
serial, and possibly other GOOSE messages.)
Further, suppose that IED "OaklandPark" has the
following located in the <IED> section:
(For clarity, there are line breaks between the
<FCDA> entries. Normally this is not done within
May 2012
the file. Also, the <FCDA> entries are contained in
one line, however due to the limitations of the width
of this section, the entry wraps around. The same
wrap around occurs in the <GSEControl>)
<IED name="OaklandPark">
...(Services are defined here)
<AccessPoint name="S1">
<Server>
<LDevice desc="description" inst="C1">
<LN0 desc="description" lnType="LN0" lnClass="LLN0" inst="">
<DataSet name=" TripControlData" desc="Goose Trip Control
Data">
<FCDA ldInst="C1" lnClass="LLN1" lnInst="1" doName="TripOne"
daName="stVal" fc="ST" />
<FCDA ldInst="C1" lnClass=" LLN1" lnInst="1" doName="TripTwo"
daName="stVal" fc="ST" />
<FCDA ldInst="C1" lnClass=" LLN1" lnInst="1" doName="52B"
daName="stVal" fc="ST" />
<FCDA ldInst="C1" lnClass="
doName="DisableTx" daName="stVal" fc="ST" />
<FCDA ldInst="C1" lnClass="
doName="TripTestStart" daName="stVal" fc="ST" />
</DataSet>
<GSEControl name="
appID="TripControlappID" datSet="TripControlData" desc="Station
Trip Control"/>
</LLN0>
</LDevice>
</Server>
</AccessPoint>
</IED>
Using the data above, the UPLC™ Goose subscrip-
tion can be constructed:
<Private type="Ametek GooseSubscription">
<eapi:GooseSubscription iedName=" OaklandPark " ldInst="CFG"
cbName="TripControl " datSet=" TripControlData " confRev ="1"
mAddr="01-0C-CD-01-00-01" maxTime="500" vlanPriority="4"
appId=" TripControlappID
g o C b R e f = " O a k l a n d P a r k C 1 / L L N 0 $ G O $ T r i p C o n t r o l "
datSetRef="OaklandParkC1/LLN0$TripControlData"">
<eapi:GooseRxEntry gooseData="FSKTripKey" type="Bool"/>
<eapi:GooseRxEntry gooseData="FSKTripKey" type="Bool"/>
<eapi:GooseRxEntry gooseData="FSK52BKey" type="Bool"/>
.....<eapi:GooseRxEntry gooseData="FSKTripTestInitiate"
type="Bool"/>
<eapi:GooseRxEntry gooseData="FSKPowerOff" type="Bool"/>
<eapi:GooseSubscription/>
Chapter 8. Protocols
LLN1" lnInst="1"
LLN1" lnInst="1"
TripControl" confRev="1"
"
Page 8–13
8