Scl Log Messages - GE UR Series Manual

SCL LOG MESSAGES

722 — In UR ICD/IID files, "h" and "min" have not been added to SIUnitKind.
926 — In UR ICD/IID files "RangeConfig_0" is not used and should be removed.
831 — The ConfRevNum "q" component is not set as per the Tissue resolution.
1178 — The objectReference of the "Oper" component is returned, which is allowed, but is not the recommended value.
3.9 SCL log messages
Logs are kept by UR devices for Substation Configuration Language (SCL) files received. These messages are associated
with errors/incompatibilities in received SCL.
UR firmware 7.3 and up with the IEC 61850 software option accepts a CID file. This file is parsed and validated when
received and on each start-up. All errors and warnings encountered in this process are logged in a file on the RAM file
3
system. As the RAM file system is volatile, the file content is lost whenever the UR device is powered down. The name of the
file is URscl.log. It can be accessed by any of the supported file transfer protocols.
This section outlines all errors and warnings that are logged in the file, meaning the SCL log messages.
Any text that follows a heading gives additional explanation of the log entry.
SCL Parsing Started <Timestamp>
This is the first message logged after a reboot and just before the start of parsing of CID/ICD file. This is logged from
mmsServer task.
Error parsing SCL file
SCL file parsing error.
apply_private_settings: <Modbus address in hex>(<Modbus address in decimal> - <format code>) <Modbus
Setting name>- error value not set = <value>
Provides the address of the Private setting value that has an issue when writing the value to the NOR flash.
apply_private_settings: <Modbus address in hex>(<Modbus address in decimal> - <format code>) <Modbus
Setting name>- invalid value = <value>
Provides the address of the Private setting that has an issue when performing an ASCII conversion and reading from the
NOR flash.
apply_private_settings: invalid addr <Modbus address in hex>
Provides the address of the Private setting that has an issue finding the MODBUS address in the memory map.
CID FLASH file copy: CRC Error
Each CID file is compressed and stored on the FLASH. Before compression a small header is added to the CID file. A CRC is
added to this header. On decompression, if the CRC in this header does not match the one calculated on the
decompressed file, then the message is logged.
CID FLASH file copy: Error order code or FW version
This message is logged when the uncompressed CID header fails for any of the following:
• Order code length
• The order code in the header must start with GE_Digital_Energy_UR
• If the order code in the header does not match the order code of the relay in SYS_Permanent data
CID FLASH file uncompress error
This message is logged when the decompression of the CID file fails.
3-144
CHAPTER 3: IEC 61850 COMMUNICATION
UR SERIES – COMMUNICATIONS GUIDE