GE B30 Communications Manual

Also see for b30: Maintenance manual Instruction manual Instruction manual Instruction manual Communications manual

Contents

3-236 UR FAMILY – COMMUNICATIONS GUIDESCL LOGGING CHAPTER 3: IEC 61850 COMMUNICATION3• ERROR — This entry indicates that the UR encountered some type of problem when parsing, validating, or applying thedata in the CID file• INTERNAL ERROR — This entry indicates that the UR encountered an internal error. This type of entry does not normallyoccur.The text after the category describes in more detail what was encountered. ERROR entries commonly describe the processor element that was in progress when the error occurred. Examples include "Parsing", "GOOSE subscription", "GOOSE e3-2.0", "ReportControl", and "DAI." Additional contextual information is provided so that the location of the problem can befound in the file.The following is an example of a log file for a successful CID file import. Note that there are no errors reported and the CIDfile loaded successfully.2015-12-08 09:00:27.823752 : === INFORMATION: SCL file parsing started. ===2015-12-08 09:01:09.138276 : INFORMATION: Number of ExtRef elements = 0. Number of successful GOOSE/R-GOOSE subscriptions = 0/0.2015-12-08 09:01:09.900773 : INFORMATION: Total number of different data in fast scan list: 0.2015-12-08 09:01:09.900773 : INFORMATION: Total number of different data in slow scan list: 0.2015-12-08 09:01:17.173752 : INFORMATION: File '/ram:1/ur.cid' imported.In the following log file, the CID file load fails because the target IED IP address does not match the actual IP address of theUR.2015-12-08 09:20:29.890419 : === INFORMATION: SCL file parsing started. ===2015-12-08 09:20:30.311192 : ERROR: target IED not found in file.2015-12-08 09:20:30.311192 : ERROR: Parsing SCL file failed.In the following log file, the CID file load fails because the lnType (logical node type) for the PhsIocPIOCx logical nodes ismissing.2015-12-08 09:24:23.357086 : === INFORMATION: SCL file parsing started. ===2015-12-08 09:24:42.152856 : ERROR: lnType for Logical Node 'TEMPLATEProt/PhsIocPIOC1' not found.2015-12-08 09:24:42.152856 : ERROR: lnType for Logical Node 'TEMPLATEProt/PhsIocPIOC2' not found.2015-12-08 09:24:42.152856 : ERROR: lnType for Logical Node 'TEMPLATEProt/PhsIocPIOC3' not found.2015-12-08 09:24:42.152856 : ERROR: lnType for Logical Node 'TEMPLATEProt/PhsIocPIOC4' not found.In the following log file, the CID file load fails because the IED name attribute is set to "&Test," which is not valid accordingto the standard as the "&" character is not allowed here.2015-12-08 09:34:55.007086 : === INFORMATION: SCL file parsing started. ===2015-12-08 09:34:55.423761 : ERROR: Parsing, IED name='&Test' is invalid.2015-12-08 09:34:55.423761 : ERROR: Parsing SCL file failed.In the following log file, the CID file load fails because the DAI value for 'SPCSO01.sboTimeout' differs from the non-configurable value given in the ICD file.2015-12-08 09:47:29.540418 : === INFORMATION: SCL file parsing started. ===2015-12-08 09:47:48.471606 : ERROR: Read only DAI 'SPCSO01$sboTimeout' (valKind="RO") in LN'TestMaster/GGIO2' cannot be changed.In the following log file, the CID file import is successful. Note also that the UR Private element contained some non IEC61850 settings that have been stored in the UR but do not take effect until the UR is rebooted. Most UR settings take effectwithout a reboot, and all others generate log entries as shown.2015-12-09 03:10:55.329941 : === INFORMATION: SCL file parsing started. ===