GE B30 Communications Manual page 260

CONFIGURING THE UR USING SCL CHAPTER 3: IEC 61850 COMMUNICATION
lower level in the UR device/UR Setup/SCT chain be propagated up to the other levels as well. Changes made through the
front panel can be propagated to EnerVista UR Setup using the traditional Add Device to Offline Window selection in the
Online Window. Changes made through the front panel can be propagated to the SCD by retrieving the IID file from the
device using any of the supported file transfer protocols, and by using the SCT to merge that IID into the SCD. Changes
made offline with the EnerVista UR Setup file can be propagated to the SCD by right-clicking on the file name in the Offline
Window, selecting Create IID File, and using the SCT to merge that IID into the SCD.
As shown in the configuration figure earlier in this section, CID files can be retrieved for UR devices using any of the
supported file transfer protocols. However, note that the CID that can be retrieved is the most recently received and
accepted CID, renamed ur.cid. It does not contain any setting changes that have been made via the front panel. Neither
does it contain any setting changes made by EnerVista UR Setup, unless the online IEC 61850 screen has been saved.
Saving the online IEC 61850 screen sends a CID file to the UR.
EnerVista UR Setup can also generate a CID from a URS, using the Create CID File option in the Offline Window area. These
CID files are the only ones sensitive to the Configuration Type setting on the Settings > Product Setup > Communications
3
> IEC 61850 > Server Configuration panel. The UR 7.3 and later series devices implement two profiles of SCL, these being
the G2implementation model and the E3-2.0 implementation model, both of which are outlined near the end of this
chapter. These vary in how GOOSE subscription configuration is represented. In the G2 model, either an ORG data object
mapped to the final destination or a ExtRef in @Master/GGIO3 has an object reference to the quantity subscribed to and
the GOOSE control block that transmits it, and the IED element of the publisher must be consulted to find information on
the GOOSE message and where in the message is the subscribed quantity. In the E3-2.0 model, all the information
necessary to subscribe to a published quantity is contained within the subscriber's IED element, using data objects that
extend the standard logical node class LGOS. The G2 model is the way the standard intended GOOSE subscription to be
configured. While the E3-2.0 model does not employ the standard's vision for subscription, it only requires CID files to
contain one IED element, and the extensions do conform to the standard's rules for extensions.
Figure 3-11: Creating CID file
3-22 UR FAMILY – COMMUNICATIONS GUIDE