...
- 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 of 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 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).
Kotva | ||||
---|---|---|---|---|
|
...
- 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.
...
Parameter | Meaning | Unit / Type | Default value | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Address parameters of the local side (D2000 KOM process) | ||||||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 | |||||||||||||||||||||
| Integer value used to identify the local Application Entity. | string | 1 | |||||||||||||||||||||
Address parameters of the remote side (the IED device) | ||||||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 | |||||||||||||||||||||
| 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 address parameters | ||||||||||||||||||||||||
| Name of the bilateral table. In the case of IEC 61850, this can be an empty string. | - | ||||||||||||||||||||||
| Maximum size of MMS messages. | bytes | 32000 | 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 | ||||||||||||||||||
| Maximum proposed transactions that could be sent and unacknowledged. The Kotva | | mrp | mrp | Max Requests Pending1 .. 32 | 5 | ||||||||||||||||||
| Maximum proposed transactions that could be received without sending an acknowledgment. The parameter value is sent to the other party. | 1 .. 32 | 5 | |||||||||||||||||||||
| The 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 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 restoringrestoration. | sec | 0 | |||||||||||||||||||||
| Delay inserted before repeated attempt 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 | |||||||||||||||||||||
| 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 parallelized. | YES/NO | NO | |||||||||||||||||||||
| 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:
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 | |||||||||||||||||||||
| 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):
Note: ABB Substation Management Unit COM600 required 0x64, it did not support bit 3 - data-update. | 1-byte octet string | 74 | |||||||||||||||||||||
| 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). | |||||||||||||||||||||||
| Type of authentication. These types of authentication are supported:
| None Password | None | |||||||||||||||||||||
| Password used if Authentication Type = Password | string | Debug settings||||||||||||||||||||||
Write settings | ||||||||||||||||||||||||
Write Mode - Select/Execute
| Enables debug information on the level of binary packets. See Note 1. | YES/NO | NO | |||||||||||||||||||||
Kotva |
| Method of writing for WriteType of SelectWithValue, Operate, Cancel, and TimeActivatedOperate types:
| One structured write | |||||||||||||||||||||
Control - Originator Category
| 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 | ||||||||||||||||||||||
Control - Originator Identifier
| 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 | ||||||||||||||||||||||||
| isolpd | isolpd | Debug ISO packet level infoEnables debug information on the ISO OSI layer. See Note 1. | YES/NO | NO | |||||||||||||||||||
Kotva | mmslpd | mmslpd | Debug MMS level infoEnables debug information on the MMS data level. See Note 1. | YES/NO | NO |
tase2lpd | tase2lpd | Full IEC61850 level info | Enables debug information on the top level of IEC 61850 databinary packets. See Note 1. | YES/NO | NO | |||||||||||||
| Enables debug information on the ISO OSI layer. See Note 1. | YES/NO | NO | |||||||||||||||||||||
| Enables debug information on the 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 detailed debug information about incoming values (data values). See Note 1. | YES/NO | NO | |||||||||||||||||||||
| Enables detailed debug information about outgoing values (data values). See Note 1. | YES/NO | NO |
...
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.
...
The station corresponds to one logical device. In In one physical device, one or more logical devices can be defined. The domain is the name of the logical device values of 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 button enables getting a list of logical devices (if the KOM process is running and communication is established). For For Browsing functionality, the device must implement support for getNameList request with parameter ObjectClass the parameter ObjectClass = DOMAIN.
Kotva | ||||
---|---|---|---|---|
|
...
- 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).
...
- 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
...
According to the standard ISO/IEC IEC 61850-8-1, the reference is in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName> (napre.g. XCBR1$ST$Pos$stValXCBR1$ST$Pos$stVal)
respectively - if subattributes are used - in the form
<LNVariableName>$<FC>$<LNDataName>$<AttributeName>$<subDataAttributeName> (napre.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 is a Functional Constraint. Table 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 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.
...
Attribute Name | Description |
---|---|
ctlModel | Specifies the control model of IEC 61850-7-2 that corresponds to the behavior of the data. |
d | Textual description of the data. |
evalTm | Time window applied to interharmonic calculations. The value shall be represented in ms. |
frequency | Nominal frequency of the power system or some other fundamental frequency in Hz. |
instMag | Magnitude of the instantaneous value of a measured value. |
mag | Deadbanded value. Shall be based on a dead band calculation from instMag. |
numCyc | The number of cycles of power frequency, which are used for harmonic, subharmonic, and interharmonic calculations. |
numHar | The number of harmonic and subharmonics or interharmonic values that are to be returned as the value attribute. |
phsAHar, phsBHar, phsCHar | This array shall contain the harmonic and subharmonics or interharmonic values related to phase A (resp. B, C). |
phsABHar, phsBCHar, phsCAHar | This array shall contain the harmonic and subharmonics or interharmonic values related to phase A to phase B (resp. B to C, resp. C to A). |
q | Quality of the attribute(s) representing the value of the data |
setCharact | This attribute shall describe the curve characteristic. |
setMag | The value of an analog setting or set point. |
stVal | The status value of the data |
swRev | SW-revision |
t | The timestamp of the last change in one of the attribute(s) representing the value of the data or in the q attribute. |
units | Units of the attribute(s) representing the value of the data (ISO/IEC IEC 61850-7-3 Annex A) |
vendor | Name of the vendor. |
...
Data Type | Popis | ||||||
| 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. | ||||||
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 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) | ||||||
| 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 * - types marked with an asterisk (*) are used in in IEC 60870-6 ICCP/TASE.2 protocol (which uses a common MMS framework). For IEC 61850, we recommend not using these types. Kotva IccpTypes IccpTypes
...
For the Structure object type: it is necessary to specify a complex address of of an 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 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.2Log 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: Communication line The communication line log shows an array consisting of two structures that contain structures that contain elements of the 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 ofthe 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
...
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 Quality is of Bitstring type with a length of 2 bytes. 13 quality bits are defined as follows (the standard numbers is numbering the bits so that the highest bit is 0 and the lowest is 15):
...
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 , and Time Index = 2.
Log line | Note |
---|---|
14:35:36.198 09-07-2018|D|MMS> [1] STRUCTURE{ | Object 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
...
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.
Write Parameters Kotva write_parameters write_parameters
This section allows you to set parameters for writing.
Write type - the type of writing. IEC-61850 defines 4 write models (IEC 61850-7-2): Kotva write_type write_type
- 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)
Kotva | ||||
---|---|---|---|---|
|
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.
...
By pressing the Refresh button it is possible to enforce the re-querying of the list of objects from the device. By default, the KOM process reads the list of objects and their respective data types only during the first browse request and stores them in memory. This reading can take a longer time, depending on the number of objects and the speed of the device. These cached lists are sent to the CNF process(es), so that consecutive filling of the Browse window is fast.
...
In D2000 versions from 20th December 2018 and newerlater, the recycling of browser dialog has dialog 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.
...
Writing to I/O tag with the Array data type (Array of *) is supported for text I/O tags (TxtO). When writing, individual values must be separated by commas, e.g. "1, 2, 3, 7"., 7".
Note 4
In the versions from 28th March 2023 and later, icon support was implemented for objects with quality and time. If the object is followed in the defined position by the tag of quality ($q) and time ($t), then one of the icons will appear next to the name of the object. By clicking on such an object with an icon, the Array Index, Quality Index and Time Index items in the address of the I/O tag will also be filled. This feature was tested with ABB Feeder protection and control REF615
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 the 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 The value of the Report Trigger Options parameter had to be 64 (hexadecimal). That means, the device did not support bit 3 - data-update during the activation of buffered reports.
- The value of the Additional Browse Items parameter had to be LLN0 so that multiple objects and information reports are found during browsing.
- The buffered reports supported the Integrity Period parameter.
- The individual items of the information reports were of different structurestructures:
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] }
...
- 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 | ||
---|---|---|
| ||
You can read blogs about the IEC 61850 protocol: IEC 61850 |
Kotva | ||||
---|---|---|---|---|
|
...
- 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 | ||
---|---|---|
| ||
...