...
Communication lines - configuration dialog box - tab Protocol parameters.
These parameters influence some optional parameters of protocol. You can define the following parameters:
Table 1
Parameter | Meaning | Unit | Default value |
---|
| Name of the bilateral table. The basic data for identification of connection between centers. | - | |
| Maximum size of MMS messages. | bytes | 32000 |
| Maximum proposed transactions that could be sent and unacknowledged. The value can be reduced if a co-center suggests lower value at negotiation. | 1 .. 32 | 5 |
| Maximum proposed transactions that could be received without sending an acknowledge. The value is sent to a partner. | 1 .. 32 | 5 |
| Maximum level of nesting for MMS data structures. | 1 .. 10 | 5 |
| TCP port number where KOM process accepts the incoming requests for connection from the external centers. If the value is 0, KOM process does not accept external requests for connection. | 0 .. 65535 | 102 |
| The maximum packet size |
on the level of 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 Remote control center to find out the validity of TCP/IP connection. |
Timer must be enabled, i.e. you must enter the nonzero value 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. This parameter is recommended in situations when transmitting data via large networks, when the less data are transmitted via the active connection or there are high timeouts for transmission of Reports (e.g. value of Interval parameter). The value 0 (implicit) turns out HeartBeat timer. Other positive values means the seconds to send Heartbeat message. If any message is sent, the Heartbeat timer is reset and Heartbeat message is sent only after timeout elapses without any communication between partners. | sec | 0 |
| Delay inserted before repeated attempt to establish the connection after it has been broken (if D2000 System activated this connection). 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 partner center are checked. As the communication with the partner center is executed via one thread, the high value can reduce speed of interaction between centers. The recommended value is 50 to 150 milliseconds. | msec | 100 msec |
| Hexadeciml number (0000-80FF) defining a bitmask for declaration of supported protocol functionality, which is divided into blocks (Conformance Blocks). Default value of 00C0 (binary 1100_0000 i.e support for blocks 1 and 2). Bits are numbered from lowest (1st bit) to highest (8th bit).- Lower byte
- 8.bit - block 1 - Basic Services
- 7.bit - block 2 - Extended Data Set Condition Monitoring
- 6.bit - block 3 - Blocked Transfers
- 5.bit - block 4 - Information Message
- 4.bit - block 5 - Device Control
- 3.bit - block 6 - Programs
- 2.bit - block 7 - Events
- 1.bit - block 8 - Accounts
- Higher byte
- 8.bit - block 9 - Time Series
- 7-1.bit - unused
A specific client (SISCO AX-S4 ICCP) required setting the parameter to value D8 (i.e. support of blocks 1,2,4,5) - otherwise it closed the connection. | - | 00C0 |
| A mode of reading values of I/O tags for Remote Control Center station:- Subscribe: on-change reading of values by defining a list of variables (message DefineNamedVariableList-Request) followed by sending of changed values (message InformationReport)
- Read: perioding polling of values of all variables. Time parameters (periode/delay) are defined on a station
Optimal mode of reading values is Subscribe, usage of Read is recommended only in case of communication problems with Subscribe. Periodic polling burdens both communicating parties. | Subscribe/Read | Subscribe |
| The way ICCP flags are mapped into D2000 flags FA..FH. ICCP protocol has following quality flags mapped into 8 bits of Quality attribute:- unused [8.bit] *
- unused [7.bit] *
- Validity_hi [6.bit]
- Validity_lo [5.bit]
- CurrentSource_hi [4.bit]
- CurrentSource_lo [3.bit]
- NormalValue [2.bit]
- TimeStampQuality [1.bit]
Note (*): in case of state values (State, StateQ, StateQTimeTag and StateExtended) the highest 2 bits are used to encode a state value (State_hi [8.bit] and State_lo [7.bit]). Mapping can be:- None - flags FA .. FH are not set
- Simple - Quality attribute directly maps to flags FA .. FH
- Sinaut - a mapping compatible with Sinaut Spectrum system.
The Sinaut mapping is based on following ICCP flags:- Validity: can have values VALID (0), HELD (1), SUSPECT (2), NOTVALID (3)
- CurrentSource: can have values TELEMETERED (0), CALCULATED (1), ENTERED(2), ESTIMATED (3)
Validity \ CurrentSource | TELEMETERED (0) | CALCULATED (1) | ENTERED (2) | ESTIMATED (3) |
---|
VALID (0) | Actual (FA) | Calcul (FB) | Manual (FC) | Calcul (FB) | HELD (1) | Blocked (FD) | BlCalcul (FE) | BlManual (FF) | BlCalcul (FE) | SUSPECT (2) | Suspect (FG) | Suspect (FG) | Suspect (FG) | Suspect (FG) | NOTVALID (3) | NotValid (FH) | NotValid (FH) | NotValid (FH) | NotValid (FH) |
Note 1: 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. Note 2: unlike None/Simple mappings, the Sinaut mapping does not change the attribute VLD, only the FH flag.
| None / Simple / Sinaut | None |
Debug I/O binary packets info | Enables debug information on the level of binary packets. See Note 1. | YES/NO | NO |
Debug ISO packet level info | 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 TASE.2 data. See Note 1. | YES/NOO | 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 Note 1. | YES/NO | NO |
Note 1...
- Communication protocol "IEC 60870-6 ICCP/TASE.2".
- Polling parameters are not used.
- This protocol Protocol does not support a time synchronization between the control centers.
...
- Control Center type
- Local Control Center (LCC)
In LCC, there are only data values that are transmitted to the partner centers. It means, that only the output I/O tags (Ao, Co, Dout) are relevant for this station. If the I/O tag value is changed, by the control objects, data are then published outward of D2000 System. In the opposite direction - to LCC, the values can be transmitted by the commands. These objects could be the input values (Ai, Ci, Di, Qi).
Exactly one station of LCC type must be configured on the line. - Remote Control Center (RCC)
In RCC, there are only data values that are transmitted form the partner centers to D2000 System. It means, that only the input I/O tag values (Ai, Ci, Di, Qi) are relevant for this station. The values of output I/O tags are transmitted as commands via RCC from D2000 System.
One or more stations of RCC type can be configured on the line.
- Domain
- For LCC - Local Domain
It is a domain name that executes Local Control Center for the remote client (center). The text string is max. 32 characters. It consists of alphanumeric characters ("a…z", "A…Z", and "0…9"), underscore ("_") or dollar sign ("$"). The first sign must be a letter. - For RCC - Remote Domain
It is a domain name that executes Remote Control Center for a local client (D2000). The text string is max. 32 characters. It consists of alphanumeric characters ("a…z", "A…Z", and "0…9"), underscore ("_") or dollar sign ("$"). The first sign must be a letter.
The Browse button, which is enabled only for RCC, enables (if a KOM process is running and if a communication is established) to obtain a list of domains from a remote control center. For browsing functionality to work, the remote control centre must support handling of getNameList request with parameter ObjectClass=DOMAIN.
- Remote Control Centre Parameters
Permitted only for RCC.- Initiate
It enables an active initiation of TCP connection to the remote control center. It means, D2000 System initiates this connection. - Role
The parameter Service Role belongs to Bilateral Table Agreement. It indicates the ICCP activity that is required for Remote Control Center - Client, Server, or Client & Server. The value is set according to an agreement with the partner local center. Usually, when enabling the parameter Initiate, you should set a pro-active communication, i.e. Client or Client & Server value.
If the Initiate parameter is on, a handler task is created for every RCC with Client or Client & Server role and connects to the ICCP server according to the line configuration.
If the Initiate parameter is off, the KOM process is waiting for ICCP client to connect, and according to the station's protocol parameters (TSEL, SSEL, PSEL, AP Title, AE Qualifier) is matching an ICCP client to a RCC with Server or Client & Server roles.
Kotva |
---|
| stanica_parametre |
---|
| stanica_parametre |
---|
|
Station protocol parameters
...
Communication station - configuration dialog box - tab Protocol parameters.
These parameters influence some optional parameters of protocol. You can set the following station parameters:
Table 2
Object group | Parameter | Meaning | Unit / size | Default value |
---|
Address parameters | | Octet string that represents the 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 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 Presentation Selector. It identifies the Presentation SAP. The maximum size is 16 octets (32 ASCII encoded hexadecimal digits). | octet string | 00 00 00 01 |
| Application Process Title is an identifier that is assigned by an address manager. It represents a |
proper specific application process. | string | 1.3.9999.1 |
| Integer value |
which marks used to identify the local Application Entity. | string | 1 |
Data Set parameters (only for RCC) | | Data Set (DS) name. Data set is a group of all I/O tags, i.e. data values, which are configured on RCC station. You can create only one data set within the RCC station. | string | |
Transfer Set Name in Inf. Report | It enables the transmission of DS Name in each message with Information report. The reserved MMS object name is "Transfer_Set_Name". | YES/NO | YES |
Transfer Set Time Stamp in Inf. Report | It enables the transmission of DS Time Stamp in each message with data Information report. A time stamp is a time, when the Information report was generated. The reserved MMS object name is "Transfer_Set_Time_Stamp". | YES/NO | YES |
DS Conditions Detected in Inf. Report | It enables the transmission of conditions of data report creation in each Information report. The reserved MMS object name is "DS_Conditions_Detected". | YES/NO | YES |
Data Set Transfer Set parameters (only for RCC) | | Time parameter for TASE.2 server that defines a delay of data monitoring. If Start Time is 0, then TASE.2 server starts the data monitoring immediately. | sec | 0 |
| Required time interval between Data Set Transfer Reports. The Interval starts after Start Time. If RBE is set on NO, the current status of all objects in data set is sent every time after "Interval". If RBE = YES, the current status of objects, which were changed since the last sending the Data Set Transfer Report, is sent. If one object was changed several times during the "Interval", only the last value is sent. See Note 2. | sec | 10 |
| Time Limit for Execution (in seconds). It is used for TASE.2 server. It is a timeout during which TASE.2 server tries to send Data Set Transfer Report TASE.2 to a client. If TASE.2 server founds out that it cannot send Data Set Transfer Report TASE.2 to the client till TLE timeout, it could remove these data. It means, the client cannot receive data older then TLE. If the problem is the communication line, the connection probably breaks up and must be restored. There is no reason to decrease this timeout under limit of 60 seconds in TCP/IP communication. | sec | 60 |
| Time interval for data buffering if "ObjectChange condition" occurs before sending them to TASE.2 client. Buffer Time starts when the first condition "ObjectChange condition" occurs. If RBE = NO, the current status of all objects in Data Set is sent after "Buffer Time". If RBE = YES, the values of objects, which were changed till the expiration of "Buffer Time", are sent. If "Buffer Time" is 0, the report is generated for each value change. If one object was changed several times during the "Buffer Time", only the last value is sent. Warning: When the parameter "Buffer Time" is 0 seconds, it can cause the overload of system or communication line because of the large number of messages (reports). See Note 2. | sec | 2 |
| Time interval for "integrity check", if "DS Conditions - Integrity Timeout" and RBE are set on YES. See Note 2. | sec | 30 |
DS Conditions - Interval Timeout | Enables TASE.2 server to send reports after elapsing the "Interval". See Note 2. | YES/NO | YES |
DS Conditions - Integrity Timeout | Enables TASE.2 server to send a complete Data Set of all objects after elapsing "Integrity Timeout". It is relevant only if RBE is set on YES. See Note 2. | YES/NO | YES |
DS Conditions - Object Change | Enables TASE.2 server to send the report after the value of any object has changed in Data Set. It involves the change of value, status or quality flags. See Note 2. | YES/NO | YES |
DS Conditions - Operator Request | Enables TASE.2 server to send the report when an operator on TASE.2 server control center sends a request. | YES/NO | NO |
DS Conditions - External Event | Enables TASE.2 server to send the report, if an external incident occurs. | YES/NO | NO |
| Control type of Transfer Report. The setting on YES means that Transfer Report is critical and needs an acknowledgement from TASE.2 client back to TASE.2 server. | YES/NO | NO |
| A flag that controls the mechanism of "Report By Exception". See Note 2. | YES/NO | YES |
Interpretation of quaternary values | | Interpretation of Quaternary value Error from the received integer value or from 2-bit State value. | 0, 1, 2, 3 | 3 (11 binary) |
| Interpretation of Quaternary value Off from the received integer value or from 2-bit State value. | 0, 1, 2, 3 | 2 (10 binary) |
| Interpretation of Quaternary value On from the received integer value or from 2-bit State value. | 0, 1, 2, 3 | 1 (01 binary) |
| Interpretation of Quaternary value Transient/Moving from the received integer value or from 2-bit State value. | 0, 1, 2, 3 | 0 (00 binary) |
Note 1
The identification of incoming client is executed according to all address parameters, i.e. TSEL, SSEL, PSEL, SSEL, AP Title and and AE Qualifier. If the connected ICCP client proves itself by the provides different address parameters than the above mentioned to parameters which do not match parameters configured on any RCC-type station configured in D2000 system, the connection is rejected.
Note 2Too much So many parameters needed for setting the "Data Set Transfer Set" can seem complicated. To set RBE (Report By Exception) parameter (i.e. the functionality of "Conformance Block" No. 2, "Extended Data Set Condition Monitoring") is, however, very important.
...
I/O tag configuration
...
Permitted I/O tagstag types: Ai, Ci, Di, Qi, Ao, Co, Dout
I/O address
...
Imgmg. No. 2, I/O tag address / (Data Value address)
![Data Value Address Data Value Address](/download/attachments/3444925/protokol_iccp_adrpt.png?version=1&modificationDate=1507883134023&api=v2)
The configuration of Data Values (according to ICCP terminology) requires the following data:
...
The list of permitted data types:
Data Type | Meaning |
State | Discrete 2-bit value |
StateQ | Discrete 2-bit value + ICCP Validity |
StateQTimeTag | Discrete 2-bit value + ICCP Validity + Time stamp |
StateExtended | Discrete 2-bit value + ICCP Validity + Current Source + Extended time stamp |
Discrete | Integer |
value 32-bit value signed |
DiscreteQ | Integer |
value 32-bit signed value + ICCP Validity |
DiscreteQTimeTag | Integer |
value 32-bit signed value + ICCP Validity + Time stamp |
DiscreteExtended | Integer |
value 32-bit signed value + ICCP Validity + Current Source + Extended time stamp |
Real | Float 32 |
RealQ | Float 32 + ICCP Validity |
RealQTimeTag | Float 32 + ICCP Validity + Time stamp |
RealExtended | Float 32 + ICCP Validity + Current Source + Extended time stamp |
--- Autodetect --- | For I/O tags on a Local Control Center station the Data Type will be derived from the Value Type:- DiscreteQTimeTag for Integer output (Cout)
- RealQTimeTag for Analog output (Ao)
- StateQTimeTag for Logical output (Dout)
For I/O tags on a Remote Control Center station 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. 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. |
ICCP Validity is converted to D2000 UniVal as follows:
...