História stránky

...

...

If all debug info is enabled, it could cause an overload of a communication workstation and a decrease of the data transfer rate from IED to D2000. After the communication is tuned and debugged, we recommend minimizing the amount of debugging information.

...

• Communication protocol "IEC 61850".
• Polling parameters are used for reading I/O tags of the "Periodically polled value" type.
• The protocol does not support time synchronization.
• in the Time parameters tab, monotonic UTC time (with offset 0) should be set, as IEC 61850 uses UTC-based timestamps (unless a specific implementation is non-compliant with this part of the standard).

Station address

Img. No. 1, Station address

Image Removed

The station corresponds to one logical device. In one physical device, one or more logical devices can be defined. The domain is the name of the logical device values which we want to read. Multiple stations can be on one line. For each station, a dedicated TCP connection to a defined physical device will be created.

The Browse button enables getting a list of logical devices (if the KOM process is running and communication is established). For Browsing functionality, the device must implement support for getNameList request with the parameter ObjectClass = DOMAIN.

...

Communication station - configuration dialog box - tab Protocol parameters.
These parameters influence some optional parameters of the protocol. You can set the following station parameters:

Table 2

...

Interpretation of Quaternary value Error from the received integer value or from 2-bit State value.

...

If all debug info is enabled, it could cause an overload of a communication workstation and a decrease of the data transfer rate from IED to D2000. After the communication is tuned and debugged, we recommend minimizing the amount of debugging information.

Kotva
komunikacna_stanica komunikacna_stanica

Communication station configuration

...

• Communication protocol "IEC 61850".
• Polling parameters are used for reading I/O tags of the "Periodically polled value" type.
• The protocol does not support time synchronization.
• in the Time parameters tab, monotonic UTC time (with offset 0) should be set, as IEC 61850 uses UTC-based timestamps (unless a specific implementation is non-compliant with this part of the standard).

Station address

Img. No. 1, Station address

Image Added

The station corresponds to one logical device. In one physical device, one or more logical devices can be defined. The domain is the name of the logical device values which we want to read. Multiple stations can be on one line. For each station, a dedicated TCP connection to a defined physical device will be created.

The Browse button enables getting a list of logical devices (if the KOM process is running and communication is established). For Browsing functionality, the device must implement support for getNameList request with the parameter ObjectClass = DOMAIN.

Kotva
stanica_parametre stanica_parametre

Station protocol parameters

...

Communication station - configuration dialog box - tab Protocol parameters.
These parameters influence some optional parameters of the protocol. You can set the following station parameters:

Table 2

Kotva
merany_bod merany_bod

I/O tag configuration

...

Permitted I/O tag types: Ai, Ao, Ci, Co, Di, Dout, TiA, ToA, TiR, ToR, Qi, TxtI, TxtO

Kotva
adresa_bodu adresa_bodu

I/O tag address

...

Img. No. 2, I/O tag address (Data Value)

Image Added

The configuration of the I/O tag address requires the following data:

Kotva
tag_type tag_type

I/O Tag Type 

Type of I/O tag:

• Buffered/unbuffered report value - the I/O tag represents the value obtained from a buffered or unbuffered report. Such values are sent by the device spontaneously after they are changed.
• Periodically polled value - the I/O tag represents the periodically read value (polling). The reading period is configured in the station parameters. 
  Note: Periodic reading may result in loss of values as a result of rapid changes, so it should only be used for slowly changing values or if the value can not be retrieved from the report.
• Buffered/unbuffered report - the I/O tag represents a buffered or unbuffered report. It is important that all reports that are used (i.e. which contain the requested data) are configured as I/O tags. Based on these I/O tags, a report is activated when a communication is established (write is performed to its attributes $TrgOps, $RptEna, $GI, and if the parameter Integrity period is specified, also to the attribute $IntgPd).

If the I/O tag representing the report has a text value, the value will be set to the name of the Dataset (the $DatSet attribute) that the report publishes.
If the I/O tag representing the report has an integer or a real value, the value will be

• • 0 - when a communication has been established - after receiving the initiate-Response message and requesting the reading of the Dataset name ($DatSet attribute) that the report publishes
  • 1 - after reading the Dataset name (receiving the device response to the Dataset name read request)
  • 2 - after reading the report parameters
  • 3 - after reading a list of objects that are contained in the Dataset
  • 4 - after successful report activation
  • 5 and more - with the arrival of each additional Information Report, the value of the object that represents it will be increased
  • invalid - if any of the communication steps fails

This mechanism can be used to define "watchdogs" guarding, for example, a communication failure, connection failure, or non-working sending of Information Reports.

Name

A unique text string that identifies the IEC 61850 object or its attribute (a reference). The maximum size is 64 characters.
Note: if the I/O tag's address is specified as %IGNORE, such an I/O tag will be ignored.

According to the standard ISO/IEC IEC 61850-8-1, the reference is in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName> (e.g. XCBR1$ST$Pos$stVal)
respectively - if subattributes are used - in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName>$<subDataAttributeName> (e.g. XBCR1$ST$Pos$origin$orCat)
where:

• LNVariableName is a name of a Logical Node. The name can be arbitrary, e.g. LLN0, Obj1XCBR1, Obj2XSWI1
• FC is a Functional Constraint. A table of defined functional constraints can be seen below.
• LNDataName is the name of a DataObject. The name can be arbitrary, the standard contains recommended rules concerning naming conventions.
• AttributeName is the name of the Attribute of a DataObject. A table of frequently used attributes can be seen below.
• subDataAttributeName is the name of the Attribute of a SubDataObject. A table of frequently used attributes can be seen below.

The standard defines the following naming conventions for individual components of a reference:

Defined Functional Constraints according to ISO/IEC IEC 61850

...

Permitted I/O tag types: Ai, Ao, Ci, Co, Di, Dout, TiA, ToA, TiR, ToR, Qi, TxtI, TxtO

...

Img. No. 2, I/O tag address (Data Value)

Image Removed

The configuration of the I/O tag address requires the following data:

...

Type of I/O tag:

• Buffered/unbuffered report value - the I/O tag represents the value obtained from a buffered or unbuffered report. Such values are sent by the device spontaneously after they are changed.
• Periodically polled value - the I/O tag represents the periodically read value (polling). The reading period is configured in the station parameters. 
  Note: Periodic reading may result in loss of values as a result of rapid changes, so it should only be used for slowly changing values or if the value can not be retrieved from the report.
• Buffered/unbuffered report - the I/O tag represents a buffered or unbuffered report. It is important that all reports that are used (i.e. which contain the requested data) are configured as I/O tags. Based on these I/O tags, a report is activated when a communication is established (write is performed to its attributes $TrgOps, $RptEna, $GI, and if the parameter Integrity period is specified, also to the attribute $IntgPd).

If the I/O tag representing the report has a text value, the value will be set to the name of the Dataset (the $DatSet attribute) that the report publishes.
If the I/O tag representing the report has an integer or a real value, the value will be

• • 0 - when a communication has been established - after receiving the initiate-Response message and requesting the reading of the Dataset name ($DatSet attribute) that the report publishes
  • 1 - after reading the Dataset name (receiving the device response to the Dataset name read request)
  • 2 - after reading the report parameters
  • 3 - after reading a list of objects that are contained in the Dataset
  • 4 - after successful report activation
  • 5 and more - with the arrival of each additional Information Report, the value of the object that represents it will be increased
  • invalid - if any of the communication steps fails

This mechanism can be used to define "watchdogs" guarding, for example, a communication failure, connection failure, or non-working sending of Information Reports.

Name

A unique text string that identifies the IEC 61850 object or its attribute (a reference). The maximum size is 64 characters.
Note: if the I/O tag's address is specified as %IGNORE, such an I/O tag will be ignored.

According to the standard ISO/IEC IEC 61850-8-1, the reference is in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName> (e.g. XCBR1$ST$Pos$stVal)
respectively - if subattributes are used - in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName>$<subDataAttributeName> (e.g. XBCR1$ST$Pos$origin$orCat)
where:

• LNVariableName is a name of a Logical Node. The name can be arbitrary, e.g. LLN0, Obj1XCBR1, Obj2XSWI1
• FC is a Functional Constraint. A table of defined functional constraints can be seen below.
• LNDataName is the name of a DataObject. The name can be arbitrary, the standard contains recommended rules concerning naming conventions.
• AttributeName is the name of the Attribute of a DataObject. A table of frequently used attributes can be seen below.
• subDataAttributeName is the name of the Attribute of a SubDataObject. A table of frequently used attributes can be seen below.

The standard defines the following naming conventions for individual components of a reference:

Defined Functional Constraints according to ISO/IEC IEC 61850-8-1:

...

Data Type

The list of permitted data types:

Data Type

The list of permitted data types:

...

• For the Autodetect object type and for arrays of elementary types (Array of): it is possible to specify an index of an element within an array. The arrays in the IEC 61850 protocol are indexed from 0. Not specifying the index results in accessing the 0-th element.

...

• For the Autodetect object type and for arrays of elementary types (Array of): it is possible to specify an index of an element within an array. The arrays in the IEC 61850 protocol are indexed from 0. Not specifying the index results in accessing the 0-th element.

Note:  For arrays of elementary types (Array of), the IEC61850 supports writing the received values to a target column of a structured variable. 
If the Destinationtab in the configuration of the I/O tag has a Destination column set to a column of a structured variable, the corresponding array items will be written into it. This only works if the Array Index is not entered or is equal to 0.

• Kotva
  cplx_addr cplx_addr

  For the Structure object type: it is necessary to specify a complex address of an element (of simple type) within a structure.
  The complex address is in form x.y.z.. e.g. 0.2. Individual indices indicate order within a structure or field, a dot indicates a descent deeper.
  Note: In the versions from 30.3.2023 and newer, the option to enter the text address of the component was also implemented (e.g. $t, $q, or $mag$f).
  Example 1: Communication line log shows a structure consisting of VisibleString elements. Individual elements will be accessed by complex addresses 0.0, 0.1 and 0.2

  Log line	Note	Simple element
  08:08:14.322 29-06-2018|D|MMS> [1] STRUCTURE{	The object of Structure type
  08:08:14.323 29-06-2018|D|MMS> [1]   Structure{	Level 0
  08:08:14.325 29-06-2018|D|MMS> [1]     VisibleString=INFO TECH	Level 0.0	yes
  08:08:14.327 29-06-2018|D|MMS> [1]     VisibleString=1.0	Level 0.1	yes
  08:08:14.329 29-06-2018|D|MMS> [1]     VisibleString=Current harmonics measurement	Level 0.2	yes
  08:08:14.332 29-06-2018|D|MMS> [1]   }	End of structure
  08:08:14.334 29-06-2018|D|MMS> [1] }	End of the Structure object

  Example  2: The communication line log shows an array consisting of two structures that contain structures that contain elements of the Float32 type. Individual elements will be accessed by complex addresses 0.0.0 and 1.0.0

  Kotvacplx_addrcplx_addrFor the Structure object type: it is necessary to specify a complex address of an element (of simple type) within a structure.
  The complex address is in form x.y.z.. e.g. 0.2. Individual indices indicate order within a structure or field, a dot indicates a descent deeper.
  Note: In the versions from 30.3.2023 and newer, the option to enter the text address of the component was also implemented (e.g. $t, $q, or $mag$f).
  Example 1: Communication line log shows a structure consisting of VisibleString elements. Individual elements will be accessed by complex addresses 0.0, 0.1 and 0.2
  yesyes

  Log line	Note	Simple element
  08:08:14. 322 169 29-06-2018|D|MMS> [1] STRUCTURE ARRAY{	The object of Structure the Array type
  08:08:14. 323 172 29-06-2018|D|MMS> [1]   Structure{	Level Level 0
  08:08:14. 325 173 29-06-2018|D|MMS> [1]     VisibleString=INFO TECH Structure{	Level 0.0
  08:08:14. 327 175 29-06-2018|D|MMS> [1]       VisibleString Float32= 1 0. 0 00000E+00	Level 0.0.10	yes
  08:08:14. 329 177 29-06-2018|D|MMS> [1]     VisibleString=Current harmonics measurement	Level 0.2	}	End of structure
  08:08:14. 332 179 29-06-2018|D|MMS> [1]   }	End of structure
  08:08:14. 334 181 29-06-2018|D|MMS> [1] }	End of the Structure object

  Example  2: The communication line log shows an array consisting of two structures that contain structures that contain elements of the Float32 type. Individual elements will be accessed by complex addresses 0.0.0 and 1.0.0

  Simple element169 ARRAY{The object of the Array type172   Structure{173 Structure{Level 0.0yes

  Structure{	Level 1	Log line	Note
  08:08:14.	183 29-06-2018|D|MMS> [1]	Structure{	Level 1.0
  08:08:14.	185 29-06-2018|D|MMS> [1]	Float32= 1.00000E+02	Level 1.0.0	yes
  08:08:14.	186 29-06-2018|D|MMS> [1]	}	End of structure
  08:08:14.175 188 29-06-2018|D|MMS> [1]       Float32= 0.00000E+00	Level 0.0.0	}	End of structure
  08:08:14.177 188 29-06-2018|D|MMS> [1]     }	End of structure	08:08:14.179 29-06-2018|D|MMS> [1]   }	End of structure	08:08:14.181 29-06-2018|D|MMS> [1]   Structure{	Level 1	08:08:14.183 29-06-2018|D|MMS> [1]     Structure{	Level 1.0
  08:08:14.185 29-06-2018|D|MMS> [1]       Float32= 1.00000E+02	Level 1.0.0	yes
  08:08:14.186 29-06-2018|D|MMS> [1]     }	End of structure	08:08:14.188 29-06-2018|D|MMS> [1]   }	End of structure	08:08:14.188 29-06-2018|D|MMS> [1] }	End of Array
  }	End of Array