GE UR series, Руководство пользователя

Страница: 380 / 432

3-164 UR SERIES – COMMUNICATIONS GUIDE
G2 IMPLEMENTATION MODEL FOR GOOSE CONFIGURATION VIA SCL CHAPTER 3: IEC 61850 COMMUNICATION
3
When project configuration is complete, the Configurator prepares a CID file for each IED. Each CID file contains at least all
of the configuration/settings relevant to the target IED. In addition to the IED element of the target IED, the CID files have
IED elements for each IED that the target IED subscribes to; these other IED elements contain descriptions of the GOOSE
messages subscribed to.
When the project IEDs have been installed and connected, the CID files are transmitted to their target IED using an
available file transfer protocol, such as SFTP or MMS. Before transfer is initiated, the target IED needs to have settings
required by the file transfer protocol entered, such as the IP address. Also, the target IED needs to already have its project
specific IED name setting made so that the target IED can determine which of the IED elements in the CID file applies to
itself. The IED parses the received file and checks that the CID settings can be implemented; if so it adjusts its internal
settings and re-starts using the new set of settings.
At this point, the GOOSE configuration process is complete. However, there can be other settings, such as for protection
pickup, that the Configurator did not or cannot set. In this case, the manufacturer's IED setup tool (lower right in the figure)
or perhaps the IED's front panel is used to complete these settings. To update the project records (that is, the SCD file) the
Configurator obtains and imports an IID (an acronym for Instantiated IED Description) file from the IED. IID files contain a
description of the capabilities of the IED and the values of its configuration/settings as of the moment the IID file was
retrieved. The IED element for the concerned IED is the only IED element in the file. As a result, the values of the subscribed
GOOSE message fields datSet, goID, and confRev, and the structure of the dataset are not contained in IID files unless non-
standard means, such as Private elements or logical node extensions, are used. This information can be obtained from the
CID or SCD files.
A variation of this sequence is to use the manufacturer's IED setup tool before the Configurator. In this case, the
Configurator begins by importing the IID file rather than the ICD file.
IID files can also be used long after the project is over to verify that the project settings are still present in the IED. The IID
file contains the values of configRev, paramRev, and confRev, which are identical to those in the CID file if no setting
changes have been made since the CID file was loaded.
3.10.3 Configuration process with IED setup tool
The GOOSE configuration process can also be completed up to the point where the configuration is sent to the IED without
involving the IED. The IED setup tool provides the same ability as the IED to generate ICD and IID files and to consume CID
files. See the following figure.
Use of the IED setup tool for configuring GOOSE is optional under normal conditions. However, if the hardware
configuration of the IED is changed, for instance by changing the number or type of contact I/O modules, use of the IED
setup tool can be required.