How can we help you today?
Why IEC61850 Module (BMENOP0300) configuration tool (IEDCT) will return "Invalid file" error after importing 3rd party device CID/SCD files?
IEC61850 standard specifies four kinds of configuration file defining device attribution, including ICD (IED Capability Description), SSD (System Specification Description), SCD (Substation Configuration Description) and CID (Configured IED Description) files. Modicon IEC61850 module configuration tool (IEDCT) parser is fully compliant with IEC61850-6 international standard (Configuration description language for communication in electrical substation related IEDs) and supports validate configuration file (ICD/SCD) during import/export or saving.
To mitigate compatibility issues and interoperation capability, all configuration files (CID/SCD) in one system must follow SCL (System Configuration description Language) schema to describe their IED configurations and communication systems according to IEC 61850-5, IEC61850-8-x and IEC 61850-7-x. Otherwise, invalid configuration will lead IEC61850 system including our Modicon IEC61850 module running under abnormal behavior.
To prevent unexpected behavior caused by invalid configuration file, IEDCT will pop-up an error message and generate an error log file after detecting mistakes from CID/SCD files. (see an example below).
But sometimes, IEDCT will still allow to import CID/SCD files but it may lead some unexpected behavior. This situation should be analyzed case by case. Normally it's caused by some abnormal/unsupported parameters or Schneider Electric private requirements. IEDCT cannot identify all abnormal parameters in configuration file but will continuously improve "compatibility check" to provide more error logs after importing/saving invalid files. Before that, customer need to self-validate (e.g. by FAQ, by IEDScout) or consult with 3rd party vendor first when he observes such error, then manually correct his ICD/SCD files and import to IEDCT again. The purpose of this FAQ is to list typical issues and guide customer to perform self-validation.
In the file attached, you will find typical examples for some unexpected behaviors caused by invalid/abnormal ICD/SCD files.
To mitigate compatibility issues and interoperation capability, all configuration files (CID/SCD) in one system must follow SCL (System Configuration description Language) schema to describe their IED configurations and communication systems according to IEC 61850-5, IEC61850-8-x and IEC 61850-7-x. Otherwise, invalid configuration will lead IEC61850 system including our Modicon IEC61850 module running under abnormal behavior.
To prevent unexpected behavior caused by invalid configuration file, IEDCT will pop-up an error message and generate an error log file after detecting mistakes from CID/SCD files. (see an example below).
But sometimes, IEDCT will still allow to import CID/SCD files but it may lead some unexpected behavior. This situation should be analyzed case by case. Normally it's caused by some abnormal/unsupported parameters or Schneider Electric private requirements. IEDCT cannot identify all abnormal parameters in configuration file but will continuously improve "compatibility check" to provide more error logs after importing/saving invalid files. Before that, customer need to self-validate (e.g. by FAQ, by IEDScout) or consult with 3rd party vendor first when he observes such error, then manually correct his ICD/SCD files and import to IEDCT again. The purpose of this FAQ is to list typical issues and guide customer to perform self-validation.
In the file attached, you will find typical examples for some unexpected behaviors caused by invalid/abnormal ICD/SCD files.
Released for:Schneider Electric Australia
Attachment(s)
Explore more
Product:
Explore more
Product: