Configuration Process - 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
CHAPTER 3: IEC 61850 COMMUNICATION
Figure 3-13: Generic logical node interfaces for the "logical nodes communicate with logical nodes" standard
3
The standards provide for the GOOSE configuration process to begin with each IED providing the names of the outputs it
can publish in an SCL file. The SCL files at this stage have the file-name extension .icd (an acronym for IED Capability
Description). The names and semantics of the outputs are strictly defined in the standards. As the names are standardized,
and as SCL standardizes how they are presented in ICD files, all standards-compliant configuration tools are able to
recognize the function of each output, even outputs of an IED of a manufacturer unknown to the tool.
However, definition and naming of logical node inputs are left almost exclusively to the IED manufacturer. There is no
requirement in the standards for the ICD file to include descriptions of the logical node inputs or their function. Instead, the
intent of the standards is that the IED manufacturer provides an "IED configurator" tool specific to the IED that this
configurator knows what inputs each logical node has and their function, so that the IED configurator can determine
which of the available outputs each can be connected to. The standards suggest but do not require that the IED
configurator sends the input to output bindings and other settings to the IED through the use of an SCL file with the file
extension .cid (an acronym for Configured IED Description).
In practice, a problem with this approach is that it requires the configuration engineers to use as many IED configurators
as there are IED manufactures. As the configurators are from different manufacturers, the engineer needs to learn how to
use each. Another problem is that many IEDs do not handle GOOSE publishing and subscribing in the "Logical nodes
communicate with logical nodes" (that is, end-to-end) paradigm of the standards. Instead inputs and/or outputs are
mapped to and from intermediate objects, such as GGIO using proprietary means, hiding their standardized names and
thus their function from generic configurators.
The purpose of this section is to specify means to use the standards such that a single generic implementation model
compliant Configurator can interoperate with all G2 implementation model-compliant IEDs sufficiently well that
configuration of GOOSE publishing and subscription can be accomplished with moderate effort on the part of the engineer
supervising the process. The means do not require proprietary IED configuration tools for GOOSE configuration. The
method is strictly compliant with the standards, only requiring that some items optional in the standards be either
mandatory or restricted.
3.10.2 Configuration process
The figure shows the SCL file flow in the configuration process under this implementation model.
3-238
UR FAMILY – COMMUNICATIONS GUIDE
- Quick Links:
- Communication Ports
Hide quick links:
Table of Contents
