| 
CHAPTER 3: IEC 61850 COMMUNICATION OVERVIEWUR FAMILY – COMMUNICATIONS GUIDE 3-133• Communications, which describes which IED access points (for example, IED Ethernet ports) are connected to whichcommunications subnetworks, and describes the communications addresses used by the IED access points• IED, each of which describes for a single IED its access points, logical devices, logical nodes, control blocks, anddatasets. The logical nodes are described using templates. The IED element can also contain some or all of its settingsand factory configured values.• DataTypeTemplates, which describes the logical nodes used in the IED section(s) and their contained data objects anddata attributes. The DataTypeTemplates element can also contain settings and factory configured values.These elements are so-called "Public" elements, in that they are precisely defined in IEC 61850-6, a publically availabledocument. These elements are expected to be understood by all IEC 61850 configuration tools, and any tool is allowedmodify the settings in them. UR 7.30 and later SCL files contain in these Public elements all settings that directly controlimplemented IEC 61850 services, including GOOSE publish and subscribe, and MMS services such as reports andcommands. UR 7.30 and later SCL files also contain for each of the UR elements that have so far been mapped to IEC61850 a description of the UR element's FlexLogic and FlexAnalog operands and of the UR element's settings that selectan operand. Thus configuration tools of any manufacturer can be used to configure the IEC 61850 communication aspectsof UR 7.30 and later devices.In addition to Public elements, SCL allows elements named "Private," whose content is not defined by the standard andwhich is contained within a tag. The content and format of Private elements is determined by themanufacturer of the tool that inserts them into an SCL file, and as such is in general understood only by that tool. Only theowner's tools are allowed to modify a Private element. Other tools are required to preserve Private elements unchanged.Different manufacturers, indeed even different tools from the same manufacturer, use Private elements for differentpurposes. A UR SCL file has two Private elements. The first Private section contains all the settings not in a Public element.The second Private section contains an authentication code that allows the UR and UR Setup to determine if a non-GE toolhas modified the first one. Thus between the Public and Private elements, a UR SCL file contains all of the device's settingsin that single file. In IID files, there can be a third Private element that contains information regarding subscribed GOOSEmessages, information that in CID and SCD files is in Public elements.3.1.8.1 File typesSCL file names are given different extensions based on where they have been created in the substation configurationprocess and where they are intended to be used, as follows.• .icd — Default settings on UR — An IED Capability Description (ICD) SCL file describes to a system configurator tool asingle type of IED. For UR 7.30 and later, an ICD file describes a UR with a particular order code. It includes all the dataattributes, control blocks, and settings with the factory default values for that order code. A copy of it can be obtaineddirectly from a UR device, or from EnerVista UR Setup.• .ssd — A System Specification Description (SSD) SCL file describes the single line diagram and functions of thesubstation and the required logical nodes. It is intended for exchange from a system specification tool to a systemconfigurator and as such is not used by UR 7.30 and later.• .scd — A System Configuration Description (SCD) SCL file describes the complete system configuration, including thesingle line diagram, all the IEDs and their information models, and the data flow between IEDs. It is intended forconfiguration exchange from the system configurator tool to each of the IED configurator tools. Typically a systemconfiguration tool creates an SCD file by merging an ICD file for each IED in the substation with an SSD file, thenconfiguring the GOOSE and report communications. EnerVista UR Setup is an IED configurator tool, and can accept anSCD file and save the settings for any UR devices it contains in URS files. EnerVista UR Setup can then send thesettings in these URS files to the corresponding UR devices.• .cid — Settings sent to UR (may or may not contain the present settings) — A Configured IED Description (CID) filedescribes the required settings of an IED and is intended for transmission of configuration from an IED configurator tothe IED. It is an SCD file, possibly stripped down to what the concerned IED needs to know. EnerVista UR Setup createsand sends a CID file to the UR device when IEC 61850 settings are involved. A UR 7.30 and later CID file includes alldata attributes of the target IED, control blocks and settings, and completely re-programs the receiving device. UR7.30 and later devices also accept a CID file from a third-party configuration tool provided that the CID file is derivedfrom a UR ICD file and contains the elements of the ICD file, possibly with modified settings. Supported file transferformats are SFTP and 61850 MMS. TFTP can be used to get files, but a TFTP "put" command cannot be used forsecurity reasons. The port number can be set as per the settings in the Instruction Manual. |
