IEC61850 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.
• 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 setting is non-mandatory so is stored by S1 Studio as a private parameter.