Relay settings

State: modelled. Tested on a hand-written IED with four setting groups; RiseClipse 1.3.0 found nothing new in what the setting edits write on the public files. No real vendor SCL file with settings has been read, and no file edited here has been opened in PCM600, DIGSI 5, SEL tools or any IED configurator.

This page covers the settings an SCL file carries. Settings kept only in vendor projects (PCM600, DIGSI 5, SEL) are not read; see What's next. Nothing on this page writes to a relay: only the SCL file changes.

View an IED's settings

1. Open the SCL file and run Open Relay Settings, then pick the IED.
2. The Relay Settings editor groups the settings by logical device and logical node, with one column per setting group. The active group is marked, and values that differ from the template default are highlighted.

What is read: every data attribute with functional constraint SP, SG, SE or CF in every logical node, found through its type templates, with:

• its value per setting group: the IED's own Val first (a Val with the group's sGroup before one with none), then the template's Val, else not set;
• its FC, basic type, enumeration, and unit and multiplier where the file gives them;
• where each value came from (IED or template), and its place in the file.

The groups of a logical device come from SettingControl (numOfSGs, actSG) in its LN0. Notes at their place say what stops a setting from being read: a missing template, an sGroup that is not a number or beyond numOfSGs, an active group beyond the groups.

Compare as-issued against as-left

1. With the settings open, run Compare Relay Settings With.... It offers the workspace files that have the IED.
2. Pick the other file. Both files' values show in one table, with before > after in the cells that differ, and the differences as sentences below.
3. Click a value to open it at its place in the file.

Compared per group: values changed, added or removed; whole settings added or removed; a setting's type; numOfSGs and actSG; an IED in only one file. Numbers compare as numbers (0.80 equals 0.8). A comparison has no editable cell.

Try it: comparing two releases of IED F21 where the zone 2 reach PoRch.setMag.f of group 2 went from 9 to 9.5 and OpDlTmms.setVal of group 3 from 350 to 300 lists exactly those two changes on PROT / Z2PDIS1.

Edit settings in the SCL file

Work on a copy of the file. In the Relay Settings editor:

1. Click a cell, type the value and press Enter. Escape or leaving the cell cancels.
2. A value the type cannot take keeps the cell open with the reason, for example "nine" is not a number, which FLOAT32 needs.; an enumeration lists its allowed values.
3. Reset to Template Default removes the IED's own value.
4. Copy Setting Group... copies one group's values to another, for one function (logical device and node) or the whole IED.
5. Change Active Group of <LD>... sets actSG of SettingControl. The commands Change Active Setting Group... and Copy Setting Group... do the same from the Command Palette.

Every change is one Undo step in the text and is not saved.

Where a value goes: an existing Val of the group gets the new text; else a Val sGroup is added in group order; else the DOI, SDI and DAI chain is created in the logical node, in the file's indentation, line endings and namespace prefix. Reset removes the Val and any element it leaves empty; set then reset gives the file back byte for byte.

Value checks by basic type:

Other types (Dbpos, Timestamp, Octet64 and others) are not edited and say so. A value per group is accepted only for FC SG or SE and a group within numOfSGs.

Compare with a live relay

The Commissioning view reads the active setting group from a connected IED and compares it with the SCL file, read only.

Limits

• Values are not checked against the data object's minVal, maxVal and stepSize.
• Private elements of the SCL file are not read.
• Array elements are named only by the IED's own indexed values.
• The table draws every row.

Not verified

• How vendors fill setting group values in exported IID and CID files.
• Whether a vendor tool reads back the values set here unchanged. Check in your configurator before relying on it.
• The setting FCs, element order and value forms follow IEC 61850-6 and 7-2 as understood here, not the standards' text.
• A large IED with a real configurator's file; Windows.