História stránky

...

Periodic reading of values (polling)
Reading of values from predefined Datasets made available in predefined Information Reports - both buffered and unbuffered
Reading of array elements which are simple values
Writing to simple types of values (writing to structures is not implemented yet)
Writing to array elements of which are simple values
Writing - control according to the "Select Before Operate With Enhanced Security" model
Browsing - when communication is established, the following items can be browsed:

...

The protocol was tested with:

software simulators

...

ABB Substation management unit COM600

...

ABB Feeder protection and control REF615

...

communication adapter ABB SPA-ZC 400

Note for ABB SPA-ZC 400: when adding objects to the dataset (in Communication Enginering Tool for SPA-ZC40x), it is necessary to check the option "Export Datasets DO Level" so that the entire object (e.g. Pos) is added as one structured variable (otherwise, its components are added as independent report items, e.g. Pos$stVal, Pos$q, Pos$t).

Image Added

Kotva
komunikacna_linka
komunikacna_linka
Communication line configuration

...

Communication line category: TCP/IP-TCP.
TCP Parameters:
- Host: string max. 80 characters – server name in INET format (a name or numerical address a.b.c.d)
- Port: TCP port number (0 to 65535), port 102 is used by default.
- Line number:

...

Communication line category: TCP/IP-TCP.
TCP Parameters:
- Host: string max. 80 characters – server name in INET format (a name or numerical address a.b.c.d)
- Port: TCP port number (0 to 65535), port 102 is used by default.
- Line number: not used, set to 1

A valid hostname or IP address of the device must be entered according to the rules above.

...

Debug ISO packet level infoDebug MMS level infoFull IEC61850 level infoEnables debug information on the top level of IEC 61850 data. See Note 1 .Incoming values infoOutgoing values infoEnables detailed debug information about outgoing values (data values). See Note 1.

Parameter

Meaning

Unit / Type

Default value

Address parameters of the local side (D2000 KOM process)

Kotva

	ltsel
	ltsel

Local TSEL (hex)

Octet string that represents the local Transport Selector. It identifies Transport SAP. The maximum size is 32 octets (64 ASCII-encoded hexadecimal digits).

octet string

00 01

Kotva

	lssel
	lssel

Local SSEL (hex)

Octet string that represents the local Session Selector. It identifies Session SAP. The maximum size is 16 octets (32 ASCII-encoded hexadecimal digits).

octet string

00 01

Kotva

	lpsel
	lpsel

Local PSEL (hex)

Octet string that represents the local Presentation Selector. It identifies Presentation SAP. The maximum size is 16 octets (32 ASCII-encoded hexadecimal digits).

octet string

00 00 00 01

Kotva

	lapt
	lapt

Local AP Title

The Local Application Process Title is an identifier that is assigned by an address manager. It represents a specific application process.

string

1.3.9999.1

Kotva

	laeq
	laeq

Local AE Qualifier

Integer value used to identify the local Application Entity.

string

1

Address parameters of the remote side (the IED device)

Kotva

	rtsel
	rtsel

Remote TSEL (hex)

Octet string that represents the remote Transport Selector. It identifies Transport SAP. The maximum size is 32 octets (64 ASCII-encoded hexadecimal digits).

octet string

00 01

Kotva

	rssel
	rssel

Remote SSEL (hex)

Octet string that represents the remote Session Selector. It identifies Session SAP. The maximum size is 16 octets (32 ASCII-encoded hexadecimal digits).

octet string

00 01

Kotva

	rpsel
	rpsel

Remote PSEL (hex)

Octet string that represents the remote Presentation Selector. It identifies Presentation SAP. The maximum size is 16 octets (32 ASCII-encoded hexadecimal digits).

octet string

00 00 00 01

Kotva

	rapt
	rapt

RemoteAP Title

Remote Application Process Title is an identifier that is assigned by an address manager. It represents a specific application process.

string

1.3.9999.1

Kotva

	raeq
	raeq

Remote AE Qualifier

Integer value used to identify the remote Application Entity.

string

1

Common address parameters

Kotva

	btid
	btid

Bilateral Table ID

Name of the bilateral table. In the case of IEC 61850, this can be an empty string.

-

Kotva

	mmmss
	mmmss

Max MMS Message Size

Maximum size of MMS messages.
Some ABB devices need to increase this parameter (e.g. to 100,000) because they do not support sending a list of objects (GetNameList message) in parts.

bytes

32000

Kotva

	mrp
	mrp

Max Requests Pending

Maximum proposed transactions that could be sent and unacknowledged. The value can be reduced if the other party suggests a lower value at negotiation.

1 .. 32

5

Kotva

	mip
	mip

Max Indications Pending

Maximum proposed transactions that could be received without sending an acknowledgment. The parameter value is sent to the other party.

1 .. 32

If the IED device is on a remote network segment, we recommend increasing the value of the parameter to suppress the effect of latency.

1 .. 32

5

Kotva

	mnl
	mnl

Max Nesting Level

The maximum level of nesting for MMS data structures.

1 .. 10

5

Kotva

	tpdus
	tpdus

ISO TPDU Size

The maximum packet size for "ISO over TCP" protocol level (according to RFC 1006)

8192/4096/2048/1024/512/256/128 bytes

1024 bytes

Kotva

	htb
	htb

Heartbeat

Timer, which permits the sending of an ICCP message Identify request to the communicating party to find out the validity of TCP/IP connection. To enable the timer a nonzero value must be specified. If the connection was aborted on the TCP/IP level, fast detection ensures its faster restoration.
This parameter is recommended in situations when transmitting data via large networks or when a small amount of data is transmitted via the active connection. The value 0 (implicit) turns off the HeartBeat timer. A positive value means the seconds to send a Heartbeat message. If any message is sent, the Heartbeat timer is reset and the Heartbeat message is sent only after a timeout elapses without any communication between partners.

sec

0

Kotva

	rd
	rd

Retry Delay

Delay inserted before repeated attempts to establish the connection after it has been broken. If the connection should be restored as fast as possible, set a small value or 0 seconds.

sec

10 sec

Kotva

	irt
	irt

Inter Read Timeout

Maximum waiting time to receive TCP data. After this timeout elapses, the possible requirements (data) for sending to a communicating party are checked.
As communication is executed via one thread, the high value can reduce the speed of interaction with the party. The recommended value is 50 to 150 milliseconds.

msec

100 msec

Kotva

	ps
	ps

Parallel Stations

The parameter activates creating TCP connections for each station. If the device supports multiple clients, communication can be parallelized.
If the parameter is set to NO, a single TCP connection will be created for all communication stations.

YES/NO

NO

Kotva

	if
	if

Map IEC 61850 flags

The way IEC 61850 flags are mapped into D2000 flags A .. M.

IEC 61850 protocol has quality flags mapped into 13 bits of the Quality attribute, details are given in the description of the parameter Quality Index:

Mapping can be:

None - flags A .. M are not set
Simple - Quality attribute directly maps to flags A .. M

Note: after the change of this parameter we recommend a restart of the KOM process or communication partner so that all values come into the system with properly set flags.

None
/
Simple

None

Kotva

	to
	to

Report Trigger Options

The setting of Trigger parameters used to trigger reports (TrgOps). The following bits are used according to the standard (the numbering is from the highest bit, which is bit 0):

bit 0 - reserved
bit 1 - data-change
bit 2 - quality-change
bit 3 - data-update
bit 4 - integrity
bit 5 - general-interrogation

The default value is 0x74 (all bits are active except integrity - this is activated if the parameter Integrity Period is specified in the report configuration.
Note: ABB Substation Management Unit COM600 required 0x64, it did not support bit 3 - data-update.

1-byte octet string

74

Kotva

	ab
	ab

Additional Browse Items

The parameter enables specifying additional names of objects to query during browsing for I/O tags. Names must be separated by a space, e.g. "Obj1 Obj2". This makes it possible to handle the situation when IED deliberately does not list some objects in the GetNameList-Response message (response to a requested list of objects within a logical device).
Note: The ABB Substation Management Unit COM600 required parameter setting to LLN0 - this object was not propagated but it was important (it contained e.g. buffered and unbuffered reports).

Kotva

	at
	at

Authentication Type

Type of authentication. These types of authentication are supported:

None - no authentication
Password - password-based authentication. The password is transmitted unencrypted within ISO 8650-1 OSI Association Control Service layer.

None
Password

None

Kotva

	pa
	pa

Password

Password used if Authentication Type = Password

string

Debug

Write settings

Write Mode - Select/Execute

Kotva

	iobpdwm	iobpd

Debug I/O binary packets info

Enables debug information on the level of binary packets. See Note 1.

YES/NO

NO

Kotva

isolpd

Enables debug information on the ISO OSI layer. See Note 1.

YES/NO

NO

Kotva

	wm

Method of writing for WriteType of SelectWithValue, Operate, Cancel, and TimeActivatedOperate types:

One structured write - one request is generated with a single write for all items of the control structure.
Multiple simple writes - one request is generated with several writes for individual components of the control structure ($ctlVal, $origin$orCat, $origin$orIdent, $ctlNum, $T, $Test, $Check, and optionally $operTm)

One structured write

Control - Originator Category

Kotva

	coc
	coc

Parameter Originator Category ($origin$orCat) for WriteType of SelectWithValue, Operate, Cancel, and TimeActivatedOperate types. The parameter is a numeric value representing the category of the device performing the write:

0 - not-supported
1 - bay-control
2 - station-control
3 - remote-control
4 - automatic-bay
5- automatic-station
6- automatic-remote
7 - maintenance
8 - process

0

Control - Originator Identifier

Kotva

	coi
	coi

Parameter Originator Identifier ($origin$orIdent) for WriteType of SelectWithValue, Operate, Cancel, and TimeActivatedOperate types. The parameter is a text identifier of the device that performs the write.

D2000

Debug settings

Kotva

	iobpd
	iobpd

Debug I/O binary packets info

Enables debug information on the level of binary packets. See

mmslpd

Enables debug information on the MMS data level. See Note 1.

YES/NO

NO

Kotva

tase2lpd

YES/NO

NO

Kotva

vilpd

Enables detailed debug information about incoming values (data values). See Note 1.

YES/NO

NO

Kotva

volpd

YES/NO

NO

Kotva

...

	isolpd

...

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.

...

	isolpd

Debug ISO packet level info

Enables debug information on the ISO OSI layer. See Note 1.

YES/NO

NO

Kotva

	mmslpd
	mmslpd

Debug MMS level info

Enables debug information on the MMS data level. See Note 1.

YES/NO

NO

Kotva

	tase2lpd
	tase2lpd

Full IEC61850 level info

Enables debug information on the top level of IEC 61850 data. See Note 1 .

YES/NO

NO

Kotva

	vilpd
	vilpd

Incoming values info

Enables detailed debug information about incoming values (data values). See Note 1.

YES/NO

NO

Kotva

	volpd
	volpd

Outgoing values info

Enables detailed debug information about outgoing values (data values). See Note 1.

YES/NO

NO

Kotva

	poznamka1
	poznamka1

Note 1

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

Object group

Parameter

Meaning

Unit / size

Interpretation of quaternary values

Kotva

	qerr
	qerr

QERR Value

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

0, 1, 2, 3

3 (11 binary)

Kotva

	qoff
	qoff

QOFF Value

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

0, 1, 2, 3

2 (10 binary)

Kotva

	qon
	qon

QON Value

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

0, 1, 2, 3

1 (01 binary)

Kotva

	qtrans
	qtrans

QTRANS Value

Interpretation of Quaternary value Transient/Moving from the received integer value or from 2-bit State value.

0, 1, 2, 3

0 (00 binary)

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-8-1:

FC Name	Description
MX	Measurands (analog values)
ST	Status information
CO	Control service parameters
CF	Configuration
DC	Description
SP	Setting (outside setting group)
SG	Setting group
RP	Unbuffered report control blocks
LG	Log control blocks
BR	Buffered report control blocks
GO	GOOSE control blocks
GS	GSSE control blocks
SV	Substituted values
SE	Setting group editing
MS	Multicast Sampled Values control block
US	Unicast Sampled Values control block
EX

...

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:

FC Name	Description
MX	Measurands (analog values)
ST	Status information
CO	Control service parameters
CF	Configuration
DC	Description
SP	Setting (outside setting group)
SG	Setting group
RP	Unbuffered report control blocks
LG	Log control blocks
BR	Buffered report control blocks
GO	GOOSE control blocks
GS	GSSE control blocks
SV	Substituted values
SE	Setting group editing
MS	Multicast Sampled Values control block
US	Unicast Sampled Values control block
EX	Name space for model extension
SR	Service tracking
OR	Operate received
BL	Blocking

...

Structure

Data Type

Popis

Kotva

	auto
	auto

--- Autodetect ---

The Data Type will be queried by a GetVariableAccessAttributes-Request message after the connection establishment.

Note 1: information is currently stored only in KOM process memory, therefore after its restart and the first connection establishment the data type detection is performed for all Autodetect I/O tags.
Note 2: data types State and StateQ are undistinguishable by this mechanism, therefore objects of these types are detected as StateQ.
Note 3: the same mechanism for data type detection is used in browsing.

Discrete *

ICCP: Integer 32-bit value signed

DiscreteQ *

ICCP: Integer 32-bit signed value + ICCP Validity

DiscreteQTimeTag *

ICCP: Integer 32-bit signed value + ICCP Validity + Time stamp

DiscreteExtended *

ICCP: Integer 32-bit signed value + ICCP Validity + Current Source + Extended time stamp

Real *

ICCP: Float 32

RealQ *

ICCP: Float 32 + ICCP Validity

RealQTimeTag *

ICCP: Float 32 + ICCP Validity + Time stamp

RealExtended *

ICCP: Float 32 + ICCP Validity + Current Source + Extended time stamp

State *

ICCP: Discrete 2-bit value

StateQ *

ICCP: Discrete 2-bit value + ICCP Validity

StateQTimeTag *

ICCP: Discrete 2-bit value + ICCP Validity + Time stamp

StateExtended *

ICCP: Discrete 2-bit value + ICCP Validity + Current Source + Extended time stamp

Boolean

Boolean value

Float32

32-bit real value

Float64

64-bit real value

Integer8

8-bit signed integer value

Integer16

16-bit signed integer value

Integer32

32-bit signed integer value

Integer64

64-bit signed integer value

Unsigned8

8-bit unsigned integer value

Unsigned16

16-bit unsigned integer value

Unsigned24

24-bit unsigned integer value

Unsigned32

32-bit unsigned integer value

OctetString

Variable-length binary string

VisibleString

Variable-length text string

UnicodeString

Variable-length text string in UTF8 encoding

BitString

Variable-length bit string

UtcTime

Absolute time (format seconds since 1.1.1970 + milliseconds)

TimeOfDay

Absolute/relative time (format seconds and milliseconds of a day + optionally number of days since 1.1.1984)

Array of Boolean

An array of Boolean values

Array of Float32

An array of 32-bit real values

Array of Float64

An array of 64-bit real values

Array of Integer8

An array of 8-bit signed integer values

Array of Integer16

An array of 16-bit signed integer values

Array of Integer32

An array of 32-bit signed integer values

Array of Integer64

An array of 64-bit signed integer values

Array of Unsigned8

An array of 8-bit unsigned integer values

Array of Unsigned16

An array of 16-bit unsigned integer values

Array of Unsigned24

An array of 24-bit unsigned integer values

Array of Unsigned32

An array of 32-bit unsigned integer values

Array of OctetString

An array of variable-length binary strings

Array of VisibleString

An array of variable-length text strings

Array of UnicodeString

An array of a variable-length text string in UTF8 encoding

Array of BitString

An array of variable-length bit strings

Array of UtcTime

An array of absolute times (format seconds since 1.1.1970 + milliseconds)

Array of TimeOfDay

An array of absolute/relative times (format seconds and milliseconds of a day + optionally number of days since 1.1.1984)

Kotva

structure

Structure or Array. The structure can contain simple types, arrays, and nested structures. Arrays consist of elements that can be simple types (here, however, it is more efficient to use some of the Array of types), structures, and arrays. If a data type of an I/O tag is configured as a Structure, the Array Index parameter specifies the complex address of the structure element to be read in the I/O tag.
Note: multiple I/O tags can have the same Name parameter, the Structure data type, and differ only by the Array Index parameter to access the various elements of the structure. If these I/O tags are configured with the I / O Tag Type = Periodically polled value, a single reading request will be sent for all such points.

...

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.

...

of Unsigned8

An array of 8-bit unsigned integer values

Array of Unsigned16

An array of 16-bit unsigned integer values

Array of Unsigned24

An array of 24-bit unsigned integer values

Array of Unsigned32

An array of 32-bit unsigned integer values

Array of OctetString

An array of variable-length binary strings

Array of VisibleString

An array of variable-length text strings

Array of UnicodeString

An array of a variable-length text string in UTF8 encoding

Array of BitString

An array of variable-length bit strings

Array of UtcTime

An array of absolute times (format seconds since 1.1.1970 + milliseconds)

Array of TimeOfDay

An array of absolute/relative times (format seconds and milliseconds of a day + optionally number of days since 1.1.1984)

Kotva

	structure
	structure

Structure

Structure or Array. The structure can contain simple types, arrays, and nested structures. Arrays consist of elements that can be simple types (here, however, it is more efficient to use some of the Array of types), structures, and arrays. If a data type of an I/O tag is configured as a Structure, the Array Index parameter specifies the complex address of the structure element to be read in the I/O tag.
Note: multiple I/O tags can have the same Name parameter, the Structure data type, and differ only by the Array Index parameter to access the various elements of the structure. If these I/O tags are configured with the I / O Tag Type = Periodically polled value, a single reading request will be sent for all such points.

Kotva

	IccpTypes
	IccpTypes

Note * - types marked with an asterisk (*) are used in IEC 60870-6 ICCP/TASE.2 protocol (which uses a common MMS framework). For IEC 61850, we recommend not using these types.

Kotva

	array_index
	array_index

Array Index

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
Log line Note Simple element
08:08:14.169 29-06-2018|D|MMS> [1] ARRAY{
The object of the Array type
08:08:14.172 29-06-2018|D|MMS> [1] Structure{
Level 0
08:08:14.173 29-06-2018|D|MMS> [1] Structure{
Level 0.0
08:08:14.175 29-06-2018|D|MMS> [1] Float32= 0.00000E+00
Level 0.0.0 yes
08:08:14.177 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
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
08:08:14.322 STRUCTURE{The object of Structure type323 Structure{
Log line Note Simple element
29-06-2018|D|MMS> [1]
}
End of structure
08:08:14.
188 29-06-2018|D|MMS> [1] }
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
Log lineNoteSimple element
08:08:14.169 29-06-2018|D|MMS> [1] ARRAY{
The object of the Array type
08:08:14.172 29-06-2018|D|MMS> [1] Structure{
Level 0
08:08:14.173 29-06-2018|D|MMS> [1] Structure{
Level 0.0
08:08:14.175 29-06-2018|D|MMS> [1] Float32= 0.00000E+00
Level 0.0.0yes
08:08:14.177 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.0yes
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

...

For the Structure object type: it is possible to specify the index where IEC 61850 Quality is located. The format of the Quality Index is the same as a complex address.
IEC 61850 Quality is of Bitstring type with a length of 2 bytes. 13 quality bits are defined as follows (the standard is numbering the bits so that the highest bit is 0 and the lowest is 15):

...

0-1

Validity:

Value	Description	D2000 attribute
0 0	Good	Valid
0 1	Invalid	Invalid
1 0	Reserved	-
1 1	Questionable	Weak

...

2

...

3

...

4

...

If at least one of bits number 2-12 is set, the value in D2000 has a Weak attribute.
See the example in Time Index.

...

For the Structure object type: it is possible to specify the index where the timestamp is located. The format of the Time Index is the same as a complex address.

If the Time Index is not specified, the timestamp of the information report (for I/O Tag Type=Buffered/unbuffered report value) or the current time (for I/O Tag Type=Periodically polled value) will be used.

Example: information report contains a structure that contains a Bitstring value followed by quality and timestamp. Therefore the object's address has Array Index = 0, Quality Index = 1, and Time Index = 2.

...

14:35:36.198 09-07-2018|D|MMS> [1] STRUCTURE{

...

14:35:36.200 09-07-2018|D|MMS> [1] Bitstring=<80>

...

14:35:36.202 09-07-2018|D|MMS> [1] Bitstring=<00><00>

...

14:35:36.204 09-07-2018|D|MMS> [1] seconds= 1531115260 fraction= 3223372800 (09-07-2018 07:47:40.751)

...

End of Array

Kotva

	qualityoffset
	qualityoffset

Quality Index
For the Structure object type: it is possible to specify the index where IEC 61850 Quality is located. The format of the Quality Index is the same as a complex address.
IEC 61850 Quality is of Bitstring type with a length of 2 bytes. 13 quality bits are defined as follows (the standard is numbering the bits so that the highest bit is 0 and the lowest is 15):
Bit(s) Note
0-1
Validity:
Value Description D2000 attribute
0 0 Good Valid
0 1 Invalid Invalid
1 0 Reserved -
1 1 Questionable Weak

2
Overflow
3
OutofRange
4
BadReference
5 Oscillatory
6 Failure
7 OldData
8 Inconsistent
9 Inaccurate
10 Source ( 0-Process, 1-Substituted)
11 Test
12 OperatorBlocked
13-15 unused bits
If at least one of bits number 2-12 is set, the value in D2000 has a Weak attribute.
See the example in Time Index.

Kotva
timeoffset
timeoffset
Time Index
For the Structure object type: it is possible to specify the index where the timestamp is located. The format of the Time Index is the same as a complex address.
If the Time Index is not specified, the timestamp of the information report (for I/O Tag Type=Buffered/unbuffered report value) or the current time (for I/O Tag Type=Periodically polled value) will be used.
Example: information report contains a structure that contains a Bitstring value followed by quality and timestamp. Therefore the object's address has Array Index = 0, Quality Index = 1, and Time Index = 2.
Log line Note
14:35:36.198 09-07-2018|D|MMS> [1] STRUCTURE{
An object of Structure type
14:35:36.200 09-07-2018|D|MMS> [1] Bitstring=<80>
Value (Array Index = 0)
14:35:36.202 09-07-2018|D|MMS> [1] Bitstring=<00><00>
Quality (Quality Index = 1)
14:35:36.204 09-07-2018|D|MMS> [1] seconds= 1531115260 fraction= 3223372800 (09-07-2018 07:47:40.751)
Timestamp (Time Index = 2)
14:35:36.206 09-07-2018|D|MMS> [1] } End of Structure object

Integrity Period
This parameter is enabled for the I/O tags of the "Buffered/unbuffered Report" type and it specifies a period (in ms) after which a report containing the values of all objects in the given datasheet is generated. Therefore, if a loss of value has occurred in some way, this Integrity Report will periodically restore the integrity of the data. Value 0 turns off the generation of the Integrity Report. The non-zero value causes a write to the $IntgPd report attribute during the report activation.
Note: Not all IEC 61850 servers support this parameter.

Kotva
write_parameters
write_parameters
Write Parameters
This section allows you to set parameters for writing.
Image Added
Kotva
write_type
write_type
Write type - the type of writing. IEC-61850 defines 4 write models (IEC 61850-7-2):
Direct control with normal security: services Operate, TimeActivatedOperate, Cancel
SBO control with normal security (SBO): services Select, Cancel, Operate, TimeActivatedOperate
Direct control with enhanced security: services Operate, Cancel, TimeActivatedOperate
SBO control with enhanced security (SBOw): services SelectWithValue, Cancel, Operate, TimeActivatedOperate
The following options are available:
Simple - simple, standard write
Select (SBO) - the first phase (Select) of the two-phase writing model "Select Before Operate With Normal Security" - reading the text variable $SBO (e.g. Obj3CSWI2$CO$Pos$SBO)
SelectWithValue (SBOw) - the first phase (SelectWithValue) of the two-phase writing model "Select Before Operate With Enhanced Security" - writing to the item $ctlVal (and others) of the control structure $SBOw (e.g. Obj3CSWI2$CO$Pos$SBOw) which contains items $ctlVal, $origin$orCat, $origin$orIdent, $ctlNum, $T, $Test, $Check, and optionally $operTm (support for TimeActivatedOperate).
Operate (*) - the Operate phase in all models - writing to the $ctlVal item (and others) of the $Oper control structure (e.g. Obj3CSWI2$CO$Pos$Oper) which contains the items $ctlVal, $origin$orCat, $origin$orIdent, $ctlNum, $T, $Test, $Check, and optionally $operTm.
Cancel (*) - the cancellation of the writing in all models after the 1st phase (Select/SelectWithValue) by writing to the $ctlVal item of the $Cancel control structure (e.g. Obj3CSWI2$CO$Pos$Cancel) which contains the items $ctlVal, $origin$orCat, $origin$orIdent, $ctlNum, $T, $Test, $Check, and optionally $operTm.
TimeActivatedOperate (*) - similar to the Operate phase in all models, but a non-zero value is also written to the $operTm item, which causes the operation to be performed at the scheduled time (if Cancel is not performed by then).
The following write parameters do not apply to the Simple write type.
Synchro Check - setting the appropriate bit in the $Check item for the SelectWithValue/Operate/TimeActivatedOperate write types.
Interlock Check - setting the appropriate bit in the $Check item for the SelectWithValue/Operate/TimeActivatedOperate write types.
Test - the value written to $Test item (True/False) for the SelectWithValue/Operate/TimeActivatedOperate/Cancel write types.
Time - if the option is checked, the time of the written value is written into the $T item (otherwise zero time) for the SelectWithValue/Operate/TimeActivatedOperate/Cancel write types.
OperTm - if the option is checked, the optional item $operTm is also written to (the value 0 is written) for the SelectWithValue/Operate/Cancel write types. The $operTm item is always written for the TimeActivatedOperate write type (time of the written value).
Note:
for WriteType = Select, the Name must end with the string $SBO, e.g. CBCSWI1$CO$Pos$SBO
for WriteType = SelectWithValue/Operate/Cancel/TimeActivatedOperate, the Name must end with the string $ctlVal, e.g. CBCSWI1$CO$Pos$SBOw$ctlVal (SelectWithValue/TimeActivatedOperate), CBCSWI1$CO$Pos$Oper$ctlVal (Operate), CBCSWI1$CO$Pos$Cancel$ctlVal (Cancel)
Integrity Period
This parameter is enabled for the I/O tags of the "Buffered/unbuffered Report" type and it specifies a period (in ms) after which a report containing the values of all objects in the given datasheet is generated. Therefore, if a loss of value has occurred in some way, this Integrity Report will periodically restore the integrity of the data. Value 0 turns off the generation of the Integrity Report. The non-zero value causes a write to the $IntgPd report attribute during the report activation.
Note: Not all IEC 61850 servers support this parameter.
Kotva
browse
browse
Browse
For the I/O tags, it is possible to find a list of objects and their data types, as long as the KOM process is running and communication is established.
When a Browse button is clicked, the IEC61850 Browser window opens, and the KOM process begins to query the list of objects with the GetNameList-Request message and then their data types with the GetVariableAccessAttributes-Request message.
...
RFC 1006 (ISO Transport Service on top of the TCP, Version: 3)
International Standard ISO/IEC 8073 (Open Systems Interconnection — Protocol for providing the connection-mode transport service)
International Standard ISO/IEC 8327-1 (Open Systems Interconnection — Connection-oriented Session protocol: Protocol Specification)
International Standard ISO/IEC 8823-1 (Open Systems Interconnection — Connection-oriented Presentation protocol: Protocol Specification)
International Standard ISO/IEC 8650-1 (Open Systems Interconnection — Connection-oriented protocol for the Association Control Service Element: Protocol Specification)
International Standard ISO/IEC IEC 61850-1 (Communication networks and systems in substations – Part 1: Introduction and overview)
International Standard ISO/IEC IEC 61850-2 (Communication networks and systems in substations – Part 2: Glossary)
International Standard ISO/IEC IEC 61850-3 (Communication networks and systems in substations – Part 3: General requirements)
International Standard ISO/IEC IEC 61850-4 (Communication networks and systems in substations – Part 4: System and project management)
International Standard ISO/IEC IEC 61850-5 (Communication networks and systems in substations – Part 5: Communication requirements for functions and device models)
International Standard ISO/IEC IEC 61850-6 (Communication networks and systems in substations – Part 6: Configuration description language for communication in electrical substations related to IEDs)
International Standard ISO/IEC IEC 61850-7-1 (Communication networks and systems in substations – Part 7-1: Basic communication structure for substation and feeder equipment – Principles and models)
International Standard ISO/IEC IEC 61850-7-2 (Communication networks and systems in substations – Part 7-2: Basic communication structure for substation and feeder equipment – Abstract communication service interface (ACSI))
International Standard ISO/IEC IEC 61850-8-1 (Communication networks and systems in substations – Part 8-1: Specific Communication Service Mapping (SCSM) – Mappings to MMS (ISO 9506-1 and ISO 9506-2) and to ISO/IEC 8802-3)
International Standard ISO/IEC IEC 61850-9-1 (Communication networks and systems in substations – Part 9-1: Specific Communication Service Mapping (SCSM) – Sampled values over serial unidirectional multidrop point to point link)
International Standard ISO/IEC IEC 61850-9-2 (Communication networks and systems in substations – Part 9-2: Specific Communication Service Mapping (SCSM) – Sampled values over ISO/IEC 8802-3)

Info
title Blog
You can read blogs about the IEC 61850 protocol: IEC 61850

Kotva
zmeny_upravy
zmeny_upravy
Changes and modifications
...
Ver. 1.0 - June 20, 2018 - Creation of document.
Ver. 1.1 - March 28, 2023 - Extension of browsing with icons for objects with time and quality
Ver. 1.2 - June 19, 2023 - Expanding the dialog to support different types of writing (Select/Operate/Cancel)

Info
title Related pages:
Communication protocols
...

Strom stránky

Page Not Available

Porovnávané verzie

Stará verzia 13

Nová verzia Aktuálny

Kľúč

Kotva
komunikacna_linka
komunikacna_linka
Communication line configuration

Station address

Kotva
komunikacna_stanica
komunikacna_stanica
Communication station configuration

Station address

Kotva
stanica_parametre
stanica_parametre
Station protocol parameters

Kotva
merany_bod
merany_bod
I/O tag configuration

Kotva
adresa_bodu
adresa_bodu
I/O tag address

Kotva
tag_type
tag_type
I/O Tag Type

Kotva
zmeny_upravy
zmeny_upravy
Changes and modifications

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

Log line	Note	Simple element
08:08:14.169 29-06-2018\|D\|MMS> [1] ARRAY{	The object of the Array type
08:08:14.172 29-06-2018\|D\|MMS> [1] Structure{	Level 0
08:08:14.173 29-06-2018\|D\|MMS> [1] Structure{	Level 0.0
08:08:14.175 29-06-2018\|D\|MMS> [1] Float32= 0.00000E+00	Level 0.0.0	yes
08:08:14.177 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

Log line	Note	Simple element
29-06-2018\|D\|MMS> [1]	}	End of structure
08:08:14.	188 29-06-2018\|D\|MMS> [1] }	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

Log line	Note
14:35:36.198 09-07-2018\|D\|MMS> [1] STRUCTURE{	An object of Structure type
14:35:36.200 09-07-2018\|D\|MMS> [1] Bitstring=<80>	Value (Array Index = 0)
14:35:36.202 09-07-2018\|D\|MMS> [1] Bitstring=<00><00>	Quality (Quality Index = 1)
14:35:36.204 09-07-2018\|D\|MMS> [1] seconds= 1531115260 fraction= 3223372800 (09-07-2018 07:47:40.751)	Timestamp (Time Index = 2)
14:35:36.206 09-07-2018\|D\|MMS> [1] }	End of Structure object

Strom stránky

História stránky

Porovnávané verzie

Stará verzia 13

Nová verzia Aktuálny

Kľúč

Kotvakomunikacna_linkakomunikacna_linka Communication line configuration

Station address

Kotvakomunikacna_stanicakomunikacna_stanicaCommunication station configuration

Station address

Kotvastanica_parametrestanica_parametre Station protocol parameters

Kotvamerany_bodmerany_bodI/O tag configuration

Kotvaadresa_boduadresa_boduI/O tag address

Kotvatag_typetag_typeI/O Tag Type

Kotvazmeny_upravyzmeny_upravyChanges and modifications

Kotva
komunikacna_linka
komunikacna_linka
Communication line configuration

Kotva
komunikacna_stanica
komunikacna_stanica
Communication station configuration

Kotva
stanica_parametre
stanica_parametre
Station protocol parameters

Kotva
merany_bod
merany_bod
I/O tag configuration

Kotva
adresa_bodu
adresa_bodu
I/O tag address

Kotva
tag_type
tag_type
I/O Tag Type

Kotva
zmeny_upravy
zmeny_upravy
Changes and modifications