Instantiated Ied Capability Description (Iid) File; Configured Ied Description (Cid) File - GE B30 Communications Manual
Universal relay family
Hide thumbs
Also See for B30:
- Instruction manual (633 pages) ,
- Communications manual (526 pages) ,
- Technical reference manual (252 pages)
Table of Contents
G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
3.10.4.6 GOOSE subscription
For each GOOSE message that can be subscribed to, there is to be in the LDevice element an LN element with element
attribute lnClass="LGOS". The LN element is to contain a DOI element with element attribute name="GoCBRef". The DOI
element is to contain a DAI element with element attribute name="setSrcRef", and the corresponding DA element is to
contain the element attribute valKind="Set". The DAI element is to contain a Val element. The content of the Val elements is
to be empty.
Note that it is not practical under this implementation model to have factory-configured GOOSE subscription down to the
individual input level. Configuration of inputs for GOOSE subscription consists of a reference to the external IED, and the
factory is unaware of what external IEDs are to be connected or what their names are when the IED is deployed.
For this reason, external references are not included in ICD files.
3.10.5 Instantiated IED capability description (IID) file
3
IEDs conforming to this implementation model are to have the ability to export an IID file compliant with the standards.
This IID file is to be as specified for the ICD file, except that rather than describing the IED with factory configuration and
settings, it describes the configuration and settings in effect at the time of IID file export.
Note that it can happen that unbeknownst to the IED, a GOOSE message that it is subscribing to has been reconfigured,
changing the outputs published. As the IED is unaware of this, it cannot be certain that the external object references given
to it in a CID file continue to be correct.
Also, it can happen that means outside of the standards such as the IED setup tool or front panel can have been used to
reconfigure which GOOSE message or which GOOSE dataset member is used by an input, changing the output used by the
input without the IED having knowledge of the name of that output.
Nevertheless, the external references in the IID file are to be those in the last accepted CID file.
3.10.6 Configured IED description (CID) file
The CID file is to be equivalent to an ICD or IID file from the target IED for all elements and element attributes specified for
the ICD file, except as provided in this clause, and except that rather than describing the IED with factory configuration and
settings, it describes the required configuration and settings.
The value of the id element attribute in the Header element can be any string of length not greater than 64.
Modify the following reference names to their project-specific names. Where the name/id of an element is modified,
change all references to it so as to maintain the integrity of the references.
•
Sub-network name
•
Access point name
•
IED name
•
Logical device ldName
•
Data set name, provided the value of GSESettings element's element attribute datSet is other than "Fix"
•
GOOSE control block name, provided the value of GSESettings element's element attribute cbName is other than "Fix"
•
Logical node type id
•
DO type id
•
EnumType id
Change the following parameters to their project values:
•
MAC address
•
APPID
•
VLAN ID
•
VLAN priority
•
MinTime
•
MaxTime
3-244
CHAPTER 3: IEC 61850 COMMUNICATION
UR FAMILY – COMMUNICATIONS GUIDE
- Quick Links:
- Communication Ports
Hide quick links:
Table of Contents
