3-162
UR SERIES – COMMUNICATIONS GUIDE
G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL
CHAPTER 3: IEC 61850 COMMUNICATION
3
Settings that require a reboot have been changed. Please restart the relay.
A few settings from the Private section require a reboot to take effect. Private settings are validated and applied after the
IEC 61850 data model is validated and the relay is rebooted. This message is logged when configuration changes to such
Private settings are detected.
3.10 G2 implementation model for GOOSE configuration via SCL
3.10.1 Introduction
This section specifies the G2 implementation model for configuring the publishing and subscription of GOOSE messages
using Substation Configuration Language (SCL) files compliant with IEC 61850 6:2009(E). For context, read the next section
(E3-2.0 implementation model).
GOOSE is a communication service defined in the standards and is used to connect virtually an output signal of a logical
node in one IED to an input of a logical node in another IED. In this section, the terms input and output are references to
signal inputs to and outputs of logical nodes. In the standards, input and output often refer to signals from the process to
an IED and from an IED to the process.
Figure 3-12: Generic logical node interfaces for the "logical nodes communicate with logical nodes" standard
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).
Inputs
Controls
Reports
Logs
From logical nodes
possibly via GOOSE
Process interface
(if any)
Self description
Settings
Logical node
ORGs
Outputs
To logical nodes
possibly via GOOSE
ACTs
SPSs
MVs
etc.
LN’s
function
859730A1.vsd
Summary of Contents for UR series
Page 5: ...TABLE OF CONTENTS UR SERIES COMMUNICATIONS GUIDE v INDEX...
Page 6: ...vi UR SERIES COMMUNICATIONS GUIDE TABLE OF CONTENTS...
Page 20: ...1 14 UR SERIES COMMUNICATIONS GUIDE FOR FURTHER ASSISTANCE CHAPTER 1 INTRODUCTION 1...
Page 216: ...2 196 UR SERIES COMMUNICATIONS GUIDE MEMORY MAP CHAPTER 2 MODBUS COMMUNICATION 2...
Page 428: ...A 2 UR SERIES COMMUNICATIONS GUIDE REVISION HISTORY APPENDIX A MISCELLANEOUS A...
