About this chapter
This chapter describes how the data objects in IEC 61850 are configured to data sets. How the different control blocks are configured and how the links for the control blocks to clients or other IEDs is done.
1 IEC 61850 Attribute Editor
The IEC 61850 attribute editor in this CCT version is not used for editing. It is only allowed and possible to view the structure and contents of Logical nodes and their data objects and data at-tributes. The organization of Logical nodes and their contents is under control and responsibility of the IED vendor.
The structure and content of a Logical node is defined in IEC 61850–7–3 and IEC 61850–7–4.
It describes the data objects, the data attribute classes and the base types as mandatory or option-al elements of a Logicoption-al node. The IED products define their Logicoption-al nodes based on this stan-dards. But these Logical nodes are described as LN types, because these LN contain only the used and available data objects etc. So each IED product will have its own set of used Logical node types.
The SCL structure takes care of this in the Data Type Templates section where all used and available Logical node types, their data object types and their data attribute types and when giv-en their additional base types of type Enumerated are included. The refergiv-ence to the LN types is given in the IED section for each logical node by the LN type name as part of the Logical node identification.
Figure 65: CCT: IEC 61850 Attribute editor (viewer)
The attribute editor can be used to get an overview and to verify the content of a Logical node.
Select a Logical node or a data object below the LN in the Project Navigator. Select Attribute Editor in the IEC 61850 Data Engineering pane.
en06000045.vsd
The visible list may be sorted in the sequence as shown in the figure above. In the example figure a Logical node of type CVMMXU is selected. This LN type is used in IED 670 products and represents the standard measured values of a bay. A part of the list of data attributes of the data object “TotW” is shown. The different columns from left to right contain the description values of each data attribute in a row listed in column one (Name).
No. Title IEC 61850– Description (taken from the standard)
1 Name 6, clause 9.5.4, table 44 Reference of the last named data attribute or basic type described in this row
2 Descr. 6, clause 9.5.4, table 44 Description in free text form of the data attribute 3 FC 6, clause 9.5.4, table 44;
7–2, clause 10.2.2.4.2;
7–3 in data class tables
Functional constraint of this data attribute
4 TrigOPt.
Trigger a report transmission when the value changes. E.g. new position of a disconnector.
5 TrigOpt.
Trigger a report transmission when the quality value changes.
E.g. oscillatory of a binary signal because of a sensor failure etc.
Trigger a report transmission when a data value is updated.
E.g. counter values are frozen and ready for transmission
7 Basic
Basic type according to definition in IEC 61850–7–2 clause 5.5.2 and the enumerated types in IEC 61850–7–3 clause 6
8 Type 6, clause 9.5.4, table 44 only used if “Basic Type” = Struct or Enum to refer to the appro-priate enumeration type or DAType when Struct is given.
9 Value 6, clause 9.5.4.4 Value of the data attribute when it can be taken from the SCL file
10 Short Address
6, clause 9.5.4.3 The short address of a data attribute which can be used for sev-eral purposes. Do not modify them.
11 Value Kind
6, clause 9.5.4.1 Special information about the state of engineering process.
Used / modified by the engineering tools
12 Count 6, clause 9.5.4, table 44 Used by the engineering tools internal. Optional for data attribute of type structure. Shall state the number of array ele-ments in the case where the attribute is an array.
2 Data set engineering
The concept of DataSets is described in a brief form in chapter 2, section 3.4 "Signal engineer-ing".
Figure 66: CCT: Generating a DataSet
When the Data Set Engineering pane is selected you will get a pane which includes four list box-es. One is for information only (Filtered Preview). The other three are needed to configure a DataSet:
• Data Sets
- lists all available DataSets with their names located in that Logical node
en06000043.vsd add DataSet
select FC
select LN
select DO select DA
- allows to add a new DataSet
- allows to remove (delete) an existing DataSet
- to change the name of a DataSet select the DataSet and click again. The field is ready to accept a new name entry
- regard the rules for DataSet naming according to IEC 61850–7–2 clause 11.2.2.1
• Data Set Entries
- lists all selected Logical nodes, Data objects or data attributes which are se-lected to be a member of the DataSet.
- the used functional constraint (FC) is shown in brackets at the end - allows to remove (delete) a selected member out of the list.
- the address (reference) of each selected FCD or FCDA is shown. The refer-ence includes the logical device part below the server as start point. This gives the possibility to select any FCD, FCDA within the IED to be a mem-ber of the DataSet. In which way this is useful to get the right information sorted logically is a question to the project.
- the selected Logical nodes with their data objects or the selected data objects directly are called Functional Constraint Data (FCD) or Functional Con-straint Data attributes (FCDA) when the member is a direct data attribute
• IED Data Model
- lists all Logical nodes within the IED with their data objects and data at-tributes in a tree structure
- each element can be selected to be a member of a DataSet
- allows, requests to select a FC to separate those attributes which will be member of the DataSet entry. Only FC = MX or ST are possible constraints for reports to clients.
- allows to add the selected object to the list box of Data Set Entries. It will be then a member of the DataSet (Add)
- allows to modify an already available member by overwriting its contents with the one of the selected object (Modify)
• Filtered Preview
- This list box shows all data attributes of the selected FC of the selected object in the IED Data Model list box. These attributes will be transmitted in case one of the data attributes has forces a trigger to send the DataSet member.
Remark
Analyzing all defined data attributes defined in IEC 61850–7–3 only data attributes with FC = MX or ST are marked with the capability to generate a trigger. And they belong to process data objects which contain the process information used at runtime. All other data attributes belong to control (commands), settings, functional configuration parameters or descriptions. These in-formation are handled by other IEC 61850 communication services and are not part of a report.
Figure 67: CCT: DataSet with FCDA member
Remark
CCT has to update the contents of all four list boxes whenever a new object, item etc. is selected.
To do this it reads the main part of data base to identify which objects etc. have to be presented.
This takes some time and it is not directly shown by an hourglass or similar. A small help in this situation would be to start the Windows Task Manager and minimize it. The small dynamic icon in the low right corner shows when the CPU is active.
Figure 68: CCT: CPU activity
en06000048.vsd select DA only
DO with stVal; q; t
en06000204.vsd Task Manager
To configure a DataSet the following steps are requested in CCT:
• select the Data Set Engineering tab in the IEC 61850 Data Engineering pane
• select the Logical node where the new DataSet should be located. This should be in normal cases the LLN0 of a LD.
• when requested and agreed in a project it is possible by the IEC 61850 standard to locate the DataSet in any LN. This is not allowed for DataSets which are used by GOOSE messages. These DataSets are only allowed in LLN0 !
• press the Add button to add a new Data Set in the Data Sets list box
• give the DataSet a name. The name must be unique within the station to be able to identify it in the communication between a client and a server IED.
• select the FCD or FCDA which should be member of the DataSet in the IED Data Model list box.
• select the correct FC out of the list in the Func. Constraint list box
• click Add to add the FCD, FCDA to the Data Set Entries list box
• click Modify when the selected member of the Data Set Entries list box should be replaced or modified by the FCD, FCDA selected in the IED Data Model list box
Repeat the procedure for all DataSets which are needed in this IED. Continue to do it for all IEDs where additional DataSets are requested.
2.1 Predefined DataSet
The IEC 61850 standard allows to have predefined DataSets which the vendor of an IED has included in his product. These predefined DataSets will be visible when you open an IED and will be listed under the LLN0.
These DataSets may be modified or extended in a project. The possibility to do it must be an-nounced by the vendor of the IED.
ABB has defined four predefined DataSets for the IED 670 products:
• MeasFlt
- includes those measured values which will be transmitted on dchg trigger given by a threshold value (deadband)
• StatIed
- includes the behavior status of all Logical nodes
• StatNml
- includes the trip signals (operate) of all protection Logical nodes
• StatUrg
- includes the urgent alarms of the Logical nodes. The definition of what is ur-gent was done by ABB experts and may be checked by the project
3 BRCB engineering
The concept of buffered report control blocks (BRCB) is described in a brief form in chapter 2, section 3.4 "Signal engineering".
Figure 69: CCT: Generating and link of a BRCB
When the Report Control Engineering pane is selected you will get a pane which contains a list with several columns and some or a lot of rows. Each row represents a BRCB description with all BRCB attributes which are of interest.
When already client IEDs are linked to that BRCB this is visible by the icon element to expand the BRCB for next level rows. Each next level row contains the identification of a linked client IED.
The five main steps to generate a BRCB are:
• add a new BRCB row to the list by clicking Add... Report Control in the bottom en06000047.vsd
• give the BRCB a unique name according to the rules described in IEC 61850–7–2 clause 14.2.2.2 and the rules defined in the project
• select the DataSet out of the list of available DataSets for this BRCB. Always only one DataSet per BRCB. See the example in the figure above
• link the BRCB to the client IEDs which should receive these event telegrams.
This is done by selecting the icon of the Logical node of the client IED (e.g. ITCI or IHSI) and link it to the name field of the corresponding BRCB by using the drag-and-drop method. Repeat this for all client IEDs which should receive the information. See the arrow in the figure above.
• configure the BRCB attributes to the standards defined in the project.
• do Update DataFlow by selecting this task via the menubar Tools > IEC 61850 Data Flow Engineering. CCT will now add the needed information in the SCL file in:
- the IED section for the 'BRCB' in the Logical node defined for this DataSet and therefore for the BRCB. Should be normally LLN0
- the IED section with the identification of the connected client IEDs per BRCB
Figure 70: CCT: Update Dataflow Configuration of the BRCB attributes
The possible attributes which are needed to describe the operation etc. of a BRCB are included in
• IEC 61850–6 clause 9.3.8 and listed in table 22, table 23 and table 24
• IEC 61850–7–2 clause 14.2 and mainly listed in table 23
• the attributes used by the CCT to get the description from the user are all listed in the CVC selection box for the BRCB.
For the identification of a column the same text is used in the BRCB list and in the CVC. To see them in the CVC completely you have to select an element. The complete description will pop up, when there is more text then in the visible part. The sorting order for the column may be changed to your demands. So the only element to make the link to CVC is the identification text of the column. How to operate the CVC see chapter 4, section 6.3 "CCT Column visibility con-trol".
en06000036.vsd
Figure 71: CCT: CVC for BRCB
en06000205.vsd Client IED attributes BRCB attributes 1
23
Table 1: BRCB attributes
No. Title IEC 61850– Description (taken from the standard) 1 Name 6, clause 9.3.8, table
22,1; 7–2, clause 14.2, table 23,1
Name of the report control block. This name is relative to the LN hosting the RCB, and shall be unique within the LN
2 Descr. 6, clause 9.3.8, table 22,2
The description text
3 DataSet 6, clause 9.3.8, table 22,3; 7–2, clause 14.2, table 23,5
The name of the data set to be sent by the report control block;
datSet can only be empty within an ICD-File.
4 Identifier 7–2, clause 14.2, table 23,3
The attribute RptID shall be the client-specified report identifier of the BRCB that has caused the generation of the report. If the report identifier value of the BRCB is NULL, then the instance name (the whole path-name) of the BRCB shall be reported as the report identifier.
NOTE: The report identifier field may be used by clients to dis-tinguish between reports from various BRCBs. This value is mirrored by the server.
5 Integrity Period
6, clause 9.3.8, table 22,4; 7–2, clause 14.2, table 23,19
Integrity period in milliseconds see IEC 61850-7-2. Only rele-vant if trigger option period is set to true
If TrgOp is set to integrity, the attribute IntgPd shall indicate the period in milliseconds used for generating an integrity report.
An integrity report shall report the values of all members of the related DATA-SET. BufTm shall have no effect when this change issues a report.
A value of 0 shall indicate that no integrity reports shall be issued.
NOTE: An integrity scan may transmit the same values as a general interrogation. The integrity scan is issued by the server.
The general-interrogation is issued by the client.
6 Config.
Ref.
6, clause 9.3.8, table 22,6; 7–2, clause 14.2, table 23,6
The configuration revision number of this report control block
7 Buff 6, clause 9.3.8, table 22,7
Specifies if reports are buffered or not; see IEC 61850-7-2
8 Buff.
Time
6, clause 9.3.8, table 22,8; 7–2, clause 14.2, table 23,16
Buffer time; see IEC 61850-7-2
The attribute BufTm shall specify the time interval in millisec-onds for the buffering of internal notifications caused by data-change (dchg), quality-change (qchg), dataupdate (dupd) by the BRCB for inclusion into a single report.
Upon receipt of the first internal event notification of the refer-enced DATA-SET, the BRCB shall start a timer of the duration buffer time. When the timer expires, the BRCB shall combine all internal events that have been received during the time inter-val into a single report. The next internal event following the timer expiration shall signal the new start of that timer. The default value of 0 shall be reserved to indicate that the buffer time attribute is not to be used by the BRCB. Each internal event shall cause the BRCB to send a single report. The value shall be settable in 1 ms increments and shall be able to con-vey up to 1 h of buffer time
9 Max.
Enabled
6, clause 9.3.8, table 23,2
Defines the maximum number of report control blocks of this type, which are instantiated at configuration time in the LN (and then used online)
10 Report Enabled Descrip-tion
6, clause 9.3.8, table 23,1
The description text
11 TrigOpt.
Dchg
7–2, clause 14.2, table 23,18
The attribute TrgOp shall specify the trigger conditions which shall be monitored by this BRCB. The following values are defined:
7–2, clause 14.2, table 23,18
The trigger options dchg, qchg, and dupd refer to the attribute trigger option (TrgOp) of the DataAttribute of the common DATA classes in IEC 61850-7-3. The trigger options integrity and general-interrogation shall be trigger conditions defined by the attributes IntgPd and GI of the BRCB respectively
Details related to the generation of a report based on the differ-ent trigger options shall be as specified in 14.2.3.2.3.
13 TrigOpt Dupd
7–2, clause 14.2, table 23,18
If a BRCB does not support one or more of the trigger options, the attempt to set the TrgOp attribute to TRUE for one of these not supported values, shall cause a negative response of the SetReportControlValues service.
14 TrigOpt.
Period
7–2, clause 14.2, table 23,18
15 Seq. No. 7–2, clause 14.2, table 23,8
The attribute SqNum shall specify the sequence number for each BRCB that has report enable set to TRUE. This number is to be incremented by the BRCB for each report generated and sent. The increment shall occur once the BRCB has formatted the report and queued the report to the N-1 protocol layer. The first report following the setting of the report enable to TRUE shall contain sequence number 0.
If TRUE SqNum shall be included in the report.
16 Time Stamp
7–2, clause 14.2, table 23,9
The attribute TimeOfEntry shall be the time, when the entry is added to the buffer. That time may be different to the time stamp of the data, which shall be the time when the event occurred that caused the entry to be created.
If TRUE TimeOfEntry shall be included in the report.
17 Data Set 7–2, clause 14.2, table 23,11
DataSet-name; If TRUE DatSet shall be included in the report.
No. Title IEC 61850– Description (taken from the standard)
18 Reason Code
7–2, clause 14.2, table 23,10
The reason for inclusion shall be included in the report if the optional fields to include in report attribute (OptFlds) of the BRCB includes reason for inclusion (=TRUE); otherwise, it shall be omitted. The value for the reason for inclusion shall be set according to the TrgOp that caused the creation of the report. The value range for reasons for inclusion shall be as listed
• data-change (caused by TrgOp = dchg in an instance of DATA)
• quality-change (caused by TrgOp = qchg in an instance of DATA)
• data-update (caused by TrgOp = dupd in an instance of DATA)
• integrity (caused by the attribute IntgPd in the BRCB)
• general-interrogation (caused by setting the attribute GI of the BRCB to TRUE by a client).
reason-for-inclusion. If TRUE ReasonCode shall be included in the report.
19 Data Ref.
7–2, clause 14.2, table 23,12
The parameter DataRef shall contain the functional constrained data (FCD) of the DataAttribute values included in the report.
data-reference. If TRUE DataRef or DataAttributeReference shall be included in the report.
20 Buffer Overfl.
7–2, clause 14.2, table 23,13
BufOvl – buffer overflow occurred
The parameter BufOvl shall indicate to the client that a buffer overflow occurred. The BRCB shall set this field in the first report that is sent with events that occurred after the overflow.
buffer-overflow. If TRUE BufOvfl shall be included in the report.
21 Entry Id. 7–2, clause 14.2, table 23,14
EntryID = entry identifier
The parameter EntryID shall represent an arbitrary OCTET STRING used to identify an entry in a sequence of events of a
The parameter EntryID shall represent an arbitrary OCTET STRING used to identify an entry in a sequence of events of a