...
Parameter | Meaning | Unit / Type | Default value | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Adress parameters of local side (D2000 KOM process) | |||||||||||||
| Octet string that represents the local Transport Selector. It identifies the Transport SAP. The maximum size is 32 octets (64 ASCII encoded hexadecimal digits). | octet string | 00 01 | ||||||||||
| Octet string that represents the local Session Selector. It identifies the Session SAP. The maximum size is 16 octets (32 ASCII encoded hexadecimal digits). | octet string | 00 01 | ||||||||||
| Octet string that represents the local Presentation Selector. It identifies the Presentation SAP. The maximum size is 16 octets (32 ASCII encoded hexadecimal digits). | octet string | 00 00 00 01 | ||||||||||
| 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 | ||||||||||
| Integer value used to identify the local Application Entity. | string | 1 | ||||||||||
Adress parameters of remote side (the IED device) | |||||||||||||
| Octet string that represents the remote Transport Selector. It identifies the Transport SAP. The maximum size is 32 octets (64 ASCII encoded hexadecimal digits). | octet string | 00 01 | ||||||||||
| Octet string that represents the remote Session Selector. It identifies the Session SAP. The maximum size is 16 octets (32 ASCII encoded hexadecimal digits). | octet string | 00 01 | ||||||||||
| Octet string that represents the remote Presentation Selector. It identifies the Presentation SAP. The maximum size is 16 octets (32 ASCII encoded hexadecimal digits). | octet string | 00 00 00 01 | ||||||||||
| 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 | ||||||||||
| Integer value used to identify the remote Application Entity. | string | 1 | ||||||||||
Common adress parameters | |||||||||||||
| Name of the bilateral table. In case of IEC 61850 this can be an empt string. | - | |||||||||||
| Maximum size of MMS messages. | bytes | 32000 | ||||||||||
| Maximum proposed transactions that could be sent and unacknowledged. The value can be reduced if the other party suggests lower value at negotiation. | 1 .. 32 | 5 | ||||||||||
| Maximum proposed transactions that could be received without sending an acknowledge. The value is sent to the other party. | 1 .. 32 | 5 | ||||||||||
| Maximum level of nesting for MMS data structures. | 1 .. 10 | 5 | ||||||||||
| The maximum packet size for "ISO over TCP" protocol level (according to RFC 1006) | 8192/4096/2048/1024/512/256/128 bytes | 1024 bytes | ||||||||||
| Timer, which permits the sending 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 TCP/IP level, the fast detection ensures its faster restoring. | sec | 0 | ||||||||||
| Delay inserted before repeated attempt to establish the connection after it has been broken. If the connection should be restored as fast as possible, set the low value or 0 seconds. | sec | 10 sec | ||||||||||
| Maximum waiting time to receive TCP data. After this timeout elapses, the possible requirements (data) for sending to a communicating party are checked. | msec | 100 msec | ||||||||||
| The parameter activates creating TCP connections for each station. If the device supports multiple clients, communication can be parallelised. | YES/NO | NO | ||||||||||
| The way IEC 61850 flags are mapped into D2000 flags FA..FM. IEC 61850 protocol has quality flags mapped into 13 bits of Quality attribute, details are given in the description of the parameter Quality Index: Mapping can be:
Note: after the change of this parameter we recommend a restart of KOM process or communication partner so that all values come into the system with properly set flags. | None / Simple | None | ||||||||||
| Setting of Trigger prameters 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):
Note: ABB Substation Management Unit COM600 required 0x64, it did not support bit 3 - data-update. | 1 byte octet string | 74 | ||||||||||
| Type of authentication. These types of authentication are supported:
| None Password | None | ||||||||||
Kotva | pa | pa | PasswordPassword used if Authentication Type = Password | string | |||||||||
Debug settings | |||||||||||||
| Parameter enables to specify 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). | ||||||||||||
| Type of authentication. These types of authentication are supported:
| None Password | None | ||||||||||
| Password used if Authentication Type = Password | string | |||||||||||
Debug settings | |||||||||||||
| Enables debug information on the level of binary packets. See Note 1. | YES/NO | NO | ||||||||||
| Enables debug information on ISO OSI layer. See Note 1. | YES/NO | NO | ||||||||||
| Enables debug information on MMS data level. See Note 1. | YES/NO | NO | ||||||||||
| Enables debug information on the top level of IEC 61850 data. See Note 1. | YES/NO | NO | ||||||||||
| Enables a detail debug information about incoming values (data values). See Note 1. | YES/NO | NO | ||||||||||
| Enables a detail debug information about outgoing values (data values). See See Note 1. | YES/NO | NO |
Kotva | ||||
---|---|---|---|---|
|
...
Data Type | Popis | ||||||
| The Data Type will be queried by a GetVariableAccessAttributes-Request message after the conection 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. | ||||||
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 binarny 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 + miliseconds) | ||||||
TimeOfDay | Absolute/relative time (format seconds and miliseconds of a day + optionally number of days since 1.1.1984) | ||||||
Array of Boolean | Array of Boolean values | ||||||
Array of Float32 | Array of 32-bit real values | ||||||
Array of Float64 | Array of 64-bit real values | ||||||
Array of Integer8 | Array of 8-bit signed integer values | ||||||
Array of Integer16 | Array of 16-bit signed integer values | ||||||
Array of Integer32 | Array of 32-bit signed integer values | ||||||
Array of Integer64 | Array of 64-bit signed integer values | ||||||
Array of Unsigned8 | Array of 8-bit unsigned integer values | ||||||
Array of Unsigned16 | Array of 16-bit unsigned integer values | ||||||
Array of Unsigned24 | Array of 24-bit unsigned integer values | ||||||
Array of Unsigned32 | Array of 32-bit unsigned integer values | ||||||
Array of OctetString | Array of variable-length binarny strings | ||||||
Array of VisibleString | Array of variable-length text strings | ||||||
Array of UnicodeString | Array of variable-length text string in UTF8 encoding | ||||||
Array of BitString | Array of variable-length bit strings | ||||||
Array of UtcTime | Array of absolute times (format seconds since 1.1.1970 + miliseconds) | ||||||
Array of TimeOfDay | Array of absolute/relative times (format seconds and miliseconds of a day + optionally number of days since 1.1.1984) | ||||||
| Structure or Array. 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. |
...
Array Index Kotva array_index array_index
- For the Autodetect object type and for arrays of elementary types (Array of): it it spossible to specify an index of 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 Structure object type: it is necessary to specify a complex addresss of element (of simple type) within a structure.Kotva cplx_addr cplx_addr
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 descend deeper.
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.2Log line Note Simple element 08:08:14.322 29-06-2018|D|MMS> [1] STRUCTURE{ 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 Structure object Example 2: Communication line log shows an array consisting of two structures that contain structures that contain elements of 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{
Object of 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 29-06-2018|D|MMS> [1] }
End of structure 08:08:14.188 29-06-2018|D|MMS> [1] }
End of Array
...
Quality Index Kotva qualityoffset qualityoffset
For the Structure object type: it is possible to specify index where IEC 61850 Quality is located. Format of Quality Index is the same as a complex address.
IEC 61850 Quality is of Bitstring type with length of 2 bytes. 13 quality bits are defined as follows (the standard numbers the bits so that the highest bit is 0 and the lowest is 15):
...
If at least one of bits number 2-12 is set, value in D2000 has a Weak attribute.
See the example in Time Index.
Time Index Kotva timeoffset timeoffset
For the Structure object type: it is possible to specify index where timestamp is located. Format of 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.
...
If this choice is active, the Data Type will be set to Autodetect, otherwise to value discovered during browsing , e.g. Boolean or Integer32.
...
The browse windows enables filtering by the object name and data type. Tt is not necessary to enter the full text in filter field. Notation "*FILTERED EXPRESSION*" is supported. The symbol * represents any text before and after the expression (e.g. *momen*).
Note 1
In addition to objects with supported data types (Boolean, Integer32 ...), the object list can contain objects with Structure type. These are the structured objects that can not be directly read. The implementation only supports work with simple types and fields whose elements are simple types, therefore individual items of structured objects need to be communicated.
Note 2
In versions from 20th December 2018 and newer, recycling of browser dialogue has been implemented. If the dialog is closed by the Cancel button or after selecting an object, it is actually only hidden and it is available for browsing by another I/O tag within the same station so that the tree structure of the browsed objects is preserved. Clicking on the close icon at the top right corner will cause the dialog to be really closed.
Kotva | ||||
---|---|---|---|---|
| ||||
Kotva | ||||
|
...
During the testing of the ABB Substation Management Unit COM600 the following facts were found:
- The device contained several configurable logical names, so it required configuration of several stations on the line (addresses e.g. RF_TS3CTRL, RF_TS3DR, RF_TS3LD0).
- The device has implemented buffered reports. For each report, it supported several instances differing by number (e.g., LLN0$BR$rcbStatUrg01 .. LLN0$BR$rcbStatUrg05, LLN0$BR$rcbMeasReg01 .. LLN0$BR$rcbMeasReg05). For multiple clients, each one had to subscribe to a specific instance of the report in order to avoid conflict.
- Value of Report Trigger Options parameter had to be 64 (hexadecimal). That means, the device did not support bit 3 - data-update during activation of buffeerd reports.
- The value of Additional Browse Items parameter had to be LLN0 so that multiple objects and information reports are found during browsing.
- The buffered reports supported Integrity Period parameter.
- The individual items of the information reports were of different structure:
Booleans with quality flags and a timestamp (Array Index = 0, Quality Index = 1, Time Index = 2):15:59:54.444 07-12-2018|D|MMS> [1] STRUCTURE{
Integers with quality flags and a timestamp (Array Index = 0, Quality Index = 1, Time Index = 2):
15:59:54.446 07-12-2018|D|MMS> [1] Boolean=FALSE
15:59:54.448 07-12-2018|D|MMS> [1] Bitstring=<00><03>
15:59:54.450 07-12-2018|D|MMS> [1] seconds= 1544108937 fraction= 3898870784 (06-12-2018 16:08:57.908) quality 1 (Accuracy of fraction: 1 bits)
15:59:54.452 07-12-2018|D|MMS> [1] }15:59:54.432 07-12-2018|D|MMS> [1] STRUCTURE{
Floats (inside a structure) with quality flags and a timestamp (Array Index = 0.0, Quality Index = 1, Time Index = 2):
15:59:54.434 07-12-2018|D|MMS> [1] Integer8= 1
15:59:54.436 07-12-2018|D|MMS> [1] Bitstring=<00><03>
15:59:54.438 07-12-2018|D|MMS> [1] seconds= 1544108937 fraction= 3834446336 (06-12-2018 16:08:57.893) quality 1 (Accuracy of fraction: 1 bits)
15:59:54.440 07-12-2018|D|MMS> [1] }16:00:03.979 07-12-2018|D|MMS> [1] STRUCTURE{
16:00:03.980 07-12-2018|D|MMS> [1] Structure{
16:00:03.981 07-12-2018|D|MMS> [1] Float32= 3.11465E+01
16:00:03.982 07-12-2018|D|MMS> [1] }
16:00:03.982 07-12-2018|D|MMS> [1] Bitstring=<00><03>
16:00:03.984 07-12-2018|D|MMS> [1] seconds= 1544184591 fraction= 1623978240 (07-12-2018 13:09:51.378) quality 0 (Accuracy of fraction: 0 bits)
16:00:03.984 07-12-2018|D|MMS> [1] }More complicated structures - e.g. multiple Booleans with common quality flags and a timestamp:
16:00:04.118 07-12-2018|D|MMS> [1] STRUCTURE{
16:00:04.119 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.120 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.120 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.121 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.122 07-12-2018|D|MMS> [1] Bitstring=<00><03>
16:00:04.123 07-12-2018|D|MMS> [1] seconds= 1544108877 fraction= 3564805632 (06-12-2018 16:07:57.830) quality 0 (Accuracy of fraction: 0 bits)
16:00:04.124 07-12-2018|D|MMS> [1] }or multiple Booleans and Integers with common quality flags and a timestamp:
16:00:04.107 07-12-2018|D|MMS> [1] STRUCTURE{
16:00:04.108 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.109 07-12-2018|D|MMS> [1] Integer8= 0
16:00:04.110 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.111 07-12-2018|D|MMS> [1] Integer8= 0
16:00:04.112 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.112 07-12-2018|D|MMS> [1] Integer8= 0
16:00:04.113 07-12-2018|D|MMS> [1] Boolean=FALSE
16:00:04.114 07-12-2018|D|MMS> [1] Integer8= 0
16:00:04.115 07-12-2018|D|MMS> [1] Bitstring=<00><03>
16:00:04.116 07-12-2018|D|MMS> [1] seconds= 1544184591 fraction= 2075243776 (07-12-2018 13:09:51.483) quality 0 (Accuracy of fraction: 0 bits)
16:00:04.117 07-12-2018|D|MMS> [1] }
Kotva | ||||
---|---|---|---|---|
|
...
Command | Syntax | Description |
STWATCH | STWATCH StationName | Tell command sends requests for reading values of all I/O tags. |
...