...
If the ICCP connection is initiated by D2000 (the address Initiate address parameter Initiate), you must enter a valid hostname of the ICCP server according to the above-mentioned rules. If, on the contrary, D2000 accepts the received request for ICCP connection, you must enter the text "ALL" to the Host field. It means that the D2000 System will listen on all interfaces that belong to the particular server (with running D2000 KOM process). If the listening is required only on the particular interface, enter the IP address of this server interface in INET format.
If D2000 System initiates this connection (the address Initiate address parameter Initiate), you must also enter the port number on which a target ICCP server listens. The protocol ISO over TCP/IP protocol uses port 102. If D2000 System only accepts the incoming connections, the port number is not used (enter for example 1). The number of bound TCP port is defined by the line protocol parameter "Bind TCP port". This feature enables the operation of ICCP protocol as a client and server simultaneously.
...
| Parameter | Meaning | Unit | Default value |
|---|
| Name of the bilateral table. The basic data for the identification of the 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 a lower value during 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 |
| The maximum level of nesting for MMS data structures. | 1 .. 10 | 5 |
| TCP port number where the D2000 KOM process accepts the incoming requests for connection from the external centers. If the value is 0, the D2000 KOM process does not accept external requests for connection. | 0 .. 65535 | 102 |
| 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 Remote control center 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 restoring.
This parameter is recommended in situations when transmitting data via large networks when fewer 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 HeartBeat timer off. Other positive values mean the seconds to send a Heartbeat message. If some 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 |
| 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 communication with the partner center is handled via one thread, the high value can reduce the speed of interaction between centers. The recommended value is 50 to 150 milliseconds. | msec | 100 msec |
| Hexadecimal 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 the lowest (1st bit) to the 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 the changed values (InformationReport message)
- Read: perioding polling of values of all variables. Time parameters (period/delay) are defined on a station
The optimal mode of reading values is Subscribe, usage of Read mode 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 A..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 the Sinaut Spectrum system.
The Sinaut mapping is based on the 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 (FAA) | Calcul (FBB) | Manual (FCC) | Calcul (FBB) | | HELD (1) | Blocked (FDD) | BlCalcul (FEE) | BlManual (FFF) | BlCalcul (FEE) | | SUSPECT (2) | Suspect (FGG) | Suspect (FGG) | Suspect (FGG) | Suspect (FGG) | | NOTVALID (3) | NotValid (FHH) | NotValid (FHH) | NotValid (FHH) | NotValid (FHH) |
Note 1: after the change of this parameter we recommend a restart of the D2000 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 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 TASE.2 data. See Note 1. | YES/NOO | NO |
| Enables detailed debugging information about incoming values (data values). See Note 1. | YES/NO | NO |
| Enables detailed debugging information about outgoing values (data values). See Note 1. | YES/NO | NO |
...
- 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 out 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 from the partner centers to the 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 the D2000 System (MMSWriteRequest message).
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 the 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.
...
A unique text string that identifies Data Value. The maximum size is 32 characters.
Note: if the I/O tag's address is specified as %IGNORE, such an I/O tag will be ignored.
...
- VMD Specific - Data Value is defined on a Virtual Manufacturing Device level
- Domain Specific - Data Value is defined on inside within a specific domain inside a device
...