IEC62850 Configurator

Versions of the MiCOM S1 studio software prior to V4.0.0 could use the IEC61850 configuration tool. This meant that devices which were compatible with the IEC 61850 Edition 1 could be supported.

Version 4.0.0 of the MiCOM S1 studio software uses an updated version of the IEC configuration tool so that devices which are compatible with the IEC 61850 Edition 2 can be supported. The new Configuration tool can handle SCLSubstation Configuration Language files based on Schema 3.0 and later, and can pass UCA IEC 61850 Edition 2 conformance tests. The updated IEDIntelligent Electronic Device. A device that initiates the disconnection of part of an electrical installation, and / or operates a warning signal when a fault or abnormal condition occurs, with minimum disruption of service. May also be known as a Relay. Configuration tool is only available for rejuvenated Px40 devices. As a consequence, older MiCOM Px40 devices with IEC61850 Edition 1 are not supported by the updated tool (but they are still supported by the old tool).

To Access the IEC61850 Configuration Tool

1. Click the Tools + IEC61850 IED Configurator menu option.
2. The main MiCOM S1 Studio window will then be locked and will show an appropriate reminder message, and the IEC61850 IED Configurator window will be opened. The MiCOM S1 Studio window will remain locked for as long as you are using the configuration tool.
3. For more details of how to use the IEC61850 Configuration, see the on-line help which is included with the tool.
4. When you have finished using the IEC61850 Configuration tool, either click the close icon on the top-right hand side of the window, or click the File + Exit menu options.
   The MiCOM S1 Studio window will then be unlocked.

Key Changes with the latest IEC Configurator Tool (Version 3.5.0 to 4.0.0)

Here is a summary of the main changes introduced by the updated configuration tool:

• The configurator tool now implements dynamic analyzing of the IEC61850 data model. Consequently this uses the CIDConfigured IED Description file format (based on Scheme 3.1); and no longer uses the MCL file format. The basic layout of the configurator is unchanged, but only those parts which can be configured are shown.
• The CID file format generally results in larger file sizes than the MCL file format. It may be necessary to use the VxWorks Deflate tool to reduce a file size for devices which have restricted flash memory sizes. The configuration tool automatically compresses uploaded CID files.
• The older configurator tool could import SCDSubstation Configuration Description, CID and IIDInstantiated/Individual IED Description files based on SCL Scheme 1.4; and export SCD, CID, IID and ICDIED Capability Description files based on SCL Scheme 1.4. The latest configurator tool can import SCD, CID, IID and CID files based on SCL Scheme 3.1; and export SCD, CID, IID and ICD files based on SCL Scheme 3.1. The Scheme version for the current template is shown in the Template Details dialog box.
• The older configurator tool could validate configuration settings using the Validate Configuration button. The latest configurator tool can validate configuration settings, but based on the IEC61850 Schema 3.0 or later, which means that schemes can be validated as being fully compatible with the IEC61850 Edition 2 standard.
• A series of technical changes has been made to the data file parameters between MiCOM S1 Studio version 3.5.0 and 4.0.0. These include:
• Version 4.0.0 of the MiCOM S1 studio software removes the recommendation that an IED name should be no longer than 8 characters. The new maximum name length for a logical device is 64 characters. Assuming the longest instance name (Measurements) is 12 characters, this means the IED Name can be set within the IED Configurator up to 52 characters in length. The SCL File ID is directly linked with the CID file name - this having a maximum length of 32 characters. You can now rename Report Control Blocks using up to 32 characters. The old RCB names were either urcbA - urcbP (unbuffered RCBs) or brcbA - brcbH (buffered RCBs). The SCL Details section now includes an additional field to record the Revision status of the ICD file.
• The Configurator tool handles fields differently, depending on whether they are deemed to be mandatory or non-mandatory parameters. In the MiCOM S1 Studio software, Mandatory fields and referred to as standard parameters; and non-mandatory ones referred to as private parameters. For example; the TCP Keepalive communications setting is non-mandatory so is retrieved from the CID file by S1 Studio and then stored in the communications section of the data file as a private parameter.
• As some MiCOM products are being produced with dual Ethernet ports, you may need to be able to store details of any such second ports, so you configure their network connection parameters. It is possible to add a second tab under the current AddressA unique number, between 1 and 254, that identifies a device to the computer. Configuration tabs, so that you can store the IP Address, Subnet Mask and Gateway Address of the Second Ethernet port. These configured parameters are then stored as private types in the ICD/CID files.
• In a similar way to the Ethernet ports, the SNTP configurations are not standard IEC61850 communications parameters. They too are extracted from the CID file are stored as private parameters in the ICD/CID file; under the headings of SNTP Poll Rate, SNTP External Server 1 IP Address and SNTP External Server 2 IP Address.
• The configurator tool includes a pre-configured dataset called "HighPerformGOOSE", which includes all the data attributes of 32 virtual outputs. It is possible to edit this dataset, although this may result in a loss of performance if inappropriate changes are made. The IED Configurator can provide error information to you if it includes data attributes which exceed pre-defined limits.
• The new IED Configurator can also provide error information when certain datasets include attributes that exceed MaxAttributes settings.
• MiCOM S1 Studio version 3.5.0 can support 8 GoCB for configuring under GOOSE; and conforms to IEC61850 Ed. 1 standard.
  Version 4.0.0 can support up to 16 GoCB; and conforms to IEC61850 Ed. 2 standard. It also supports the three new GOOSE parameters under Ed.2, namely MinTime, MaxTime and FixedOffs. The increment of the Repeat message transmission parameters is mapped to a private field in the CID file.
• As MiCOM S1 Studio version 3.5.0 conforms to IEC61850 Ed. 1 standard, it does not support fixed length GOOSE messages.
  Version 4.0.0 does support the fixed length messages; which it stores in the read only FixedOffs parameter. The default value in each GOOSE publisher control block is FALSE. Note that the Fixed-Length GOOSE requires hardware (FPGA) support.
• There is a preconfigured dataset for GOOSE Control Block. The HighPerfGOOSE dataset has a default value of GoCB01. This assignment can now be changed, but a warning may be given if the change may affect the GOOSE performance.
• Under MiCOM S1 Studio software version 3.5.0, GOOSE subscription parameters are not defined by the IEC61850 standard. Accordingly, the parameters for GOOSE subscribing were stored in the MCL file and transferred to the S1 Studio software by parsing the MCL file. Under software version 4.0.0, these parameters are mapped to dofferent Data Attributes of GOOSE virtual input LN. For example, the GOOSE identifier Ind1 will be mapped to the Inref1 of GosGGIO1. Note that private data attributes are used for some parameters.
• The Configuration Revision number is increased by 1 for each config change under MiCOM S1 Studio software version 3.5.0. Under version 4.0.0, it is increased by 10000, this being defined in the confRev parameter in data files.
• Px4x devices which were programmed using MiCOM S1 Studio software version 3.5.0, did not support RCB naming. The new IED Configurator (which ships with S1 Studio software version 4.0.0) allows you to set the report control block name, with a maximum length of 32 characters.
• The new version of the IED Configurator also now supports Reserve RCB for a client. It does this because data files now include a Reserved Client section, which is added below the Report Parameters section for each RCB.
• Under MiCOM S1 Studio software version 3.5.0, the configurable parameters for uniqueness control checking were mostly stored in the MCL file. Under version 4.0.0, they are stored as private parameters in the ICD/CID file.