| Full name | Meaning | Unit | Default value |
|---|
Asymmetric Redundancy Mode Periodicity | The parameter can be used for a TCP Redundant line with defined backup servers (see the parameters AS1, AP1, BS1, BP1 ..). The non-zero value of ARMP parameter means that if this number of ASDUs is received (after a successful reconnect), both connections are checked whether they're not going through the same network (IPs and ports defined in the line settings or ASx:APx and BSx:BPx). If they do, the connection to the standby server (see the Asymmetric Redundancy Mode Slave Detection parameter) will be closed and an attempt to establish a connection through another network will be made. If unsuccessful, the next IP address will be tried (i.e. Alternate Server 1, Alternate Server 2, line IP, Alternate Server 1, etc).
Note: When the parameter Asymmetric Redundancy Mode Periodicity is enabled, the second connection is established to "B-Alternate Server 1":"B-Alternate Port 1" and not to the IP address and port defined for the line after running the D2000 KOM process (so that it wouldn't be immediately closed). | - | 0 |
Asymmetric Redundancy Mode Slave Detection | The detection method of standby server for Asymmetric Redundancy Mode Periodicity:- 0 - no detection: the first connection, that detects it is working via the same network, is to be disconnected
- 1 - if ASDU contains the least significant bit of the 3rd Control Field byte set to 1
- 2 - if ASDU in CauseOfTransmission contains a bit set to 8
| - | 0 |
Alternate Server 1/ Alternate Port 1/ Alternate Server 2/ Alternate Port 2/ | Extension for redundant systems: besides the IP address defined in the configuration of the Line, it is possible to define 2 alternative IP addresses. In case of a connection failure, the D2000 KOM process is attempting to connect to the next address in the list.
Note 1: All IP addresses and ports must be defined gradually for one station (i.e. at first "Alternate Server 1", "Alternate Port 1" and then "Alternate Server 2", "Alternate Port 2").
Note 2: These parameters are obsolete since it's possible to define several IP addresses in the configuration of the line (separated by comma or semicolon, e.g. 10.0.0.1;10.0.0.2). | - | - |
B-Alternate Server 1/ B-Alternate Port 1/ B-Alternate Server 2/ B-Alternate Port 2/ | Can be used when the protocol IEC 870-5-104 is configured for a TCP redundant line. The meaning of the parameters is the same as for the primary connection, but they are valid for the backup connection.
Note 1: All IP addresses must be defined stepwise for one station (i.e. at first "Alternate Server 1", "Alternate Port 1" and then "Alternate Server 2", "Alternate Port 2").
Note 2: These parameters are obsolete since it's possible to define several IP addresses in the configuration of the line (separated by comma or semicolon, e.g. 10.0.0.1;10.0.0.2). | - | - |
| Confirmation of control ASDU.
If Command Confirm=0, the D2000 KOM process is not waiting for confirmation of control ASDU from the partner station using a reply ASDU with a different CauseOfTransmission. ASDU is considered to be confirmed when a packet containing the corresponding ReceiveSequenceNumber is received.
If Command Confirm=1, the D2000 KOM process is waiting for confirmation with CauseOfTransmission=7 (Activation Confirmation).
If Command Confirm=2, the D2000 KOM process is waiting for confirmation with CauseOfTransmission=10 (Activation Termination).
If Command Confirm=3, the D2000 KOM process waiting for confirmation with CauseOfTransmission=7 or 10 (if both of them are received, only the first of them is taken into account).
Having received corresponding confirmation means that writing is finished (the Transient attribute of written value is cleared and the "Wait Timeout Tn" timeout stops elapsing).
If a confirmation with a CauseOfTransmission different from the one the D2000 KOM process expects, is received, it will be ignored.
Writing is successful if the received ASDU contains the P/N bit set to 0. Otherwise, writing is unsuccessful.
Value from received ASDU is written back into a particular I/O tag and is sent to the system. E.g. if an ASDU of type 50 (short floating point) with the value of 1200.0 is sent and the partner station sends an ASDU of type 50 as a reply, P/N bit=0, the value of 999.0 (e.g. due to physical limitations of the given parameter) as a response, then the value will be sent to the D2000 system by the D2000 KOM process. | - | 1 |
These parameters are intended for the configuration of a communication station for communication between two D2000 systems using ASDU 252 - D2000 Unival (Ipesoft's implementation). more ... |
| A mask for debug levels of input data. The meaning of bits is as follows:- 1.bit - displays a number of incoming values during General Interrogation
- 2.bit - displays all incoming values
- 3.bit - balanced mode: requesting Interrogation command was received
| - | 0 |
| A mask for debug levels of output data. The meaning of bits is as follows:- 1.bit - balanced mode: displays a number of outgoing values during General Interrogation
- 2.bit - displays all outgoing values
| - | 0 |
| Extension for ABB MicroScada: If End of initialization=1, having received ASDU 70 (End of initialisation) resends Interrogation Command and/or Counter Interrogation Command. | - | 0 |
| If Force Master Time=True, then the D2000 KOM process will accept ASDU 103 (Clock synchronisation command) with CauseOfTransmission=6 [Activation] or 3 [Spontaneous] from the server and saves it will save the time difference between the server's time and its time. If CauseOfTransmission=6, it replies with CauseOfTransmission=7 [Activation Confirmation].
Then the time of all values, which are received with timestamps, is decreased by this difference, i.e. a correction to the time of D2000 is made.
The parameter allows solving the problem when some values from the server are received with the timestamps and others without timestamps and times from D2000 and server differ. In this case, without parameter Force Master Time=True the values received without timestamps are tagged by D2000 time and the values with the timestamps are tagged by the server time. With parameter Force Master Time=True the time, sent by the server, is corrected to D2000 time using the time difference, which is computed from the received ASDU 103 (Clock synchronisation command). | - | False |
| Extension for ABB MicroScada: If Force Slave Time=True, then the D2000 KOM process will accept ASDU 103 (Clock synchronisation command) with CauseOfTransmission=6 [Activation] or 3 [Spontaneous] from the server and saves the time difference between server time and its time. If CauseOfTransmission=6, it replies with CauseOfTransmission=7 [Activation Confirmation].
Then all values, which are received with no timestamps, are to be marked by the current time plus time difference (if the station is not configured to use the communication computer time).
The parameter The Force Slave Time parameter allows to solve solving the problem, that after receiving ASDU 100 or 101, the ABB MicroScada sends "interrogated" values without timestamps. However, however, during the communication, the values are sent with the timestamps - problems can occur, when which may cause problems if the times of the MicroScada and the D2000 system are not synchronized. | - | False |
| If GI Send New=True, then the D2000 KOM process, after receiving the General Interrogation command, sends also values with more recent times than the time when the command was received. The value of the GI Send New parameter must be True to send values with future times as a reply to the General Interrogation command. | - | False |
Ignore Control Field 3 bit 0 | Determines behavior, when ASDU contains Control Field with the lowest bit (1) of the 3rd-byte set.- if Ignore Control Field 3 bit 0=False (default), ASDU content is to be processed
- if Ignore Control Field 3 bit 0=True, ASDU content is to be ignored
The feature can be used when creating a redundant TCP connection (TCP Redundant line + IEC 870-5-104 protocol). The active server should send ASDU with the lowest bit of the 3rd Control Field byte set to 0, the passive server should send ASDU with the lowest bit of the 3rd Control Field byte set to 1. | - | False |
Ignore Invalids on Interrogation | Balanced mode: if this parameter is set on a station, the D2000 KOM process will not send as a reply for ASDU 100 and 101 (Interrogation / Counter interrogation command) values of I/O tags which are Invalid or Unknown. The parameter can be used e.g. when controlling if sending Invalid values causes a breakdown of control. | - | False |
| Determines behavior, when ASDU contains bit 8 (test) set in CauseOfTransmission.- if Ignore Tests=0 (default), ASDU content is to be processed
- if Ignore Tests=1, ASDU content is to be ignored
- if Ignore Tests=2, a Weak attribute is to be set
The feature can be used for creating a redundant TCP connection (TCP Redundant line + IEC 870-5-104 protocol). A hot An active server should send ASDU with the Test bit=0, a standby passive server should send ASDU with the Test bit=1. | - | 0 |
| If Ignore Unknown Addresses=TRUE, the D2000 KOM process will not show an error on its console or write it into log files in case that incoming value has the address not matching any of the addresses of I/O tags defined in the D2000 system. | - | False |
| Balanced mode: After connecting to the IEC104 server, the D2000 KOM process sends the values of all variables without waiting for ASDU 100 or 101 [Interrogation/Counter Interrogation Command] requests. | - | False |
Interrogation Covers Counter Interrogation | Balanced mode: As a reply to Interrogation, also values of I/O tags configured as ASDU 15, 16, 37 (Integrated Totals) are sent. (They are normally requested by ASDU 101 [Counter Interrogation].) | - | False |
Interrogation WithOut Timestamps | If Interrogation WithOut Timestamps=True, then values sent as a response to ASDU 100 [Interrogation Command] in balanced mode will be sent as ASDUs without timestamps.
For example instead of ASDU 2 (Single-point information with time tag) or ASDU 30 (Single-point information with time tag CP56Time2a) ASDU 1 (Single-point information) will be sent.
This behavior is suitable in the situation when the values have been invalidated as a result of communication error and after the communication is reestablished the values come with old timestamps which causes problems in the archive (if the values change only rarely, calculated archives depending on them will be also invalid till a new value arrives). At the same time, this behavior is strictly according to the IEC standard, which says that the response to Interrogation should not use ASDUs with time stamps. | - | False |
| Sending window size i.e. number of I-frames sent by the D2000 KOM process without receiving a confirmation (S-frame or I-frame). According to the standard, the default value is 12. | - | 12 |
| The parameter may be used to read historical values for communication with LFC terminals or other devices that support ASDU 250 defined by Ipesoft. Unlike the primary use of ASDU 250, the LFC terminal can only transmit one value for interval begin time, while the end time is ignored. The value will not be received as ASDU 251 but as one of the standard ASDU with a timestamp. Moreover, the values (with the same timestamp) of other tags may be received along with the value of the required tag. LFC terminal does not send ASDU 250 (with CauseOfTransmission=7, 10) as part of the response to ASDU 250 and the D2000 KOM process considers the reading done as soon as it gets the value of the required I/O tag. If the value is not received within the time defined by the Wait Timeout T1 parameter, the reading of historical value is considered unsuccessful, however, the connection to the LFC terminal is not closed. If the values of other I/O tags are received along with the value of the required I/O tag, they must be received before the value of the required tag is received, otherwise, they are not considered as historical values (because reading is considered to be done after the value of required I/O tag is received).
Example: After the request for the values of I/O tags with the addresses of 1,2..16, the LFC terminal always sends the values of all the tags in the order of 1,2..16, therefore we must ask for the value of the I/O tag with the address of 16. If the parameter is not defined or LFC History=0, reading of historical data is defined by Ipesoft (D2000 IEC104 Server partner is assumed). If LFC History=1, then the value is considered to be historical (it will go to the archive but not to the I/O tag, etc.) if its timestamp belongs to the time interval specified by the GETOLDVAL action (and is received as ASDU 250). If LFC History=2 then the behavior is as for LFC History=1 except if the timestamp of the received value is newer than the timestamp of the current value of the I/O tag, the received value will be sent into the D2000 Server process as a new one and not as a historical one. Note: When reading historical data of the LFC terminal, theGETOLDVAL action may not contain station name (thestatIdent parameter) but the I/O tag name. If the action contains a station name, ASDU 250 will be sent for one I/O tag only. | - | 0 |
| Maximum acceptable time difference (in hours) between the time of received data and the time of the D2000 KOM process. If the partner station sends a value with a timestamp older or later than MDT hours, the value will be ignored and an error log will be written into the line's trace file. If the Maximum Time Difference parameter is a negative value (e.g. Maximum Time Difference=-5), its absolute value is used and the system alarm SystemError will be generated as well. If the parameter's value is zero, the time difference will not be checked. | hrs | 0 |
| If the parameter is True, then the status byte of incoming ASDUs is ignored and not saved into the FA...FH flags. Flags of output I/O tags are also ignored and they are not written to the status byte. | - | False |
| Order of sending ASDU 100 [Interrogation Command] during connection initialization. If OIC<OCIC Order of IC < Order of Counter IC, ASDU 100 will be sent before ASDU 101. If OIC Order of IC=0, ASDU 100 will not be sent. The parameter can be set extra for each station. | - | 1 |
| Order of sending ASDU 101 [Counter Interrogation Command] during connection initialization. If Order of Counter IC < Order of Counter IC, ASDU 101 will be sent before ASDU 100. If Order of Counter IC=0, ASDU 101 will not be sent. The parameter can be set extra for each station. | - | 2 |
| Number The number of repetitions, after which the IP address not responding to the ping is known as considered non-functional.
See the parameter Ping TimeOut. | - | 3 |
| If the parameter is other than non-zero, then it defines the timeout (in milliseconds) of server response for ping (ICMP echo) packet. In the background, the process the D2000 KOM process sends ping packets to all defined IPs - Line IP address and Alternate Server 1, Alternate Server 2, B-Alternate Server 1, B-Alternate Server 2. If some of the addresses does do not response for respond Ping Count-times, it is designated as non-functional. If the line is connected to this IP address, the connection is terminated. New A new connection is established just only to a functional IP address. If the parameter Ping TimeOut=0, sending the ping packet to IP addresses is disabled. | ms | 0 |
| A delay between receiving StartDT Con response and sending Interrogation Command and/or Counter Interrogation Command in the initialisation initialization phase. | ms | 0 |
| A delay before connecting and reconnecting (after starting the process D2000 KOM process and after communication break-up). | ms | 0 |
| Initial Send sequence number. According to the standard, having established the connection the Send sequence number is set to 0, other than zero could be appropriate e.g. for testing. | - | 0 |
| Number The number of values that must be identical in the Smart Redundancy Minimum mode to consider the connections synchronized. The following parameters are taken into account:- I/O tag and station addresses
- value
- time
- flags (FA..FH)
| - | 5 |
| Can be used for TCP Redundant line as an alternative to Ignore Tests=1 or Ignore Control Field 3 bit 0=1. The process D2000 KOM process assumes that the identical values go via the both connection of the TCP Redundant line in the same order. The process D2000 KOM process is attempting to synchronize the connections. If the D2000 KOM process receives a number of identical values defined by the parameter the Smart Redundancy Minimum parameter, data are synchronized. After synchronisation synchronization is done, the value that comes earlier is taken into account, the same value via the other connection is ignored.
When the TCP connection is broken or two different values comescome, the synchronisation synchronization is broken.
Compared to the detection hotof active/standby passive partner by means of "Ignore Tests"/"Ignore Control Field 3 bit 0", an advantage is that after communication failure with the hot active server, there is no data loss , because the communication is still working with the standby passive partner and the D2000 KOM process is attempting to recover the connection with the hot active server.
Having recovered the connection (if the second connection is working), there are ignored the values which are acquired by the command General Interrogation. | - | False |
| If True, after changing the status of process the D2000 Server process (the process D2000 KOM process is connected to) from Hot into Standby state (in a redundant system), connection with the IEC104 server will not be closed. | - | False |
Standby Set Control Field | If TRUE, after changing the status of process the D2000 Server process (the process D2000 KOM process is connected to) from Hot to Standby state (in the a redundant system), the lowest bit of the 3rd Control Field byte of information APDUs (APDU containing data or commands) will be set to 1 instead of the standard value of 0. The behaviour behavior does not strictly follow the standard and we recommend you to use using the parameter Standby Set Test Bit parameter instead of this parameter if it is possible. | - | False |
| If True, the Cause Of Transmission will have a Test bit set if the process D2000 KOM process is connected to the Standby server (in a redundant system) or is a passive instance. | - | False |
| If True, after changing the status of process the D2000 Server process (the process D2000 KOM process is connected to) from Hot into Standby state (in a redundant system), there the new values will be sent new valuesto the IEC104 server. | - | False |
Station Communication Error | Number The number of unsuccessful connection attempts after the communication failure after which the station status is changed to St_CommErr. For redundant lines, the communication must be either failed on both TCP connections or only a TCP connection to standby-server must be a passive server is established (see the parameters Ignore Control Field 3 bit 0 and Ignore Tests), i.e. data from the such a server are ignored. | - | 2 |
| The status of all stations on the line is changed into the state St_HardErr state if the following conditions are met:- number of unsuccessful connection attempts reaches the value of ST_HE Station Hard Error or higher,
- an attempt to restore the communication lasts at least the time defined by the parameter Time filter parameter (maximum value of all stations on the line is taken into account),
- for redundant lines, the communication must be either failed for both TCP connections or there is only a working TCP connection only to a standby-passive server is established (see the parameters Ignore Control Field 3 bit 0 and Ignore Tests), i.e. the data from the such a server are ignored.
| - | 5 |
Stop Data Confirm Ignored | Workaround due to for the MetsoDNA server error: after connecting to the IEC870-5-104 server from the firm Metso company, the server sends a StopDT Con U-frame STOPDTcon (thereby confirms interruption in confirming the end of sending data). If the parameter Stop Data Confirm Ignored parameter is True, this frame will be ignored and the communication will continue. Without the parameter Stop Data Confirm Ignored parameter set, the connection will be aborted. | - | False |
Strict Redundancy Connection Signalisation | Determines behaviourbehavior, when the protocol is used for TCP Redundant line- if Strict Redundancy Connection Signalisation=False, the line is in order ok (TRUE), if at least 1 connection is working
- if Strict Redundancy Connection Signalisation=True, the line is in error state (FALSE), if both connections are working
| - | False |
| The parameter is implemented for use on OpenVMS platforms only. If it is other than zero, then defines the timeout (in seconds) for opening a new connection to the IEC104 server. For OpenVMS, the default value is 75 seconds, for Windows, it is 20 seconds. When the timeout expires, the connect procedure returns an error. | - | 0 |
| Setting Tcp No Delay parameter causes low-level socket option TCP_NODELAY being set, thus turning off the default packet coalesce feature. | - | False |
| Number The number of received I-frames, after which the process D2000 KOM process sends a an S-frame confirmation. According to the standard, the default value is 8. The relation W < K must be true, the standard recommends W = 2/3 * K. | - | 8 |
| Timeout for receiving the confirmation of a sent I-frame (either confirmation within the I-frame or the S-frame itself) or a U-frame. If the process D2000 KOM process does not get receive the confirmation in the time within Wait Timeout T1T1 time, it closes the TCP connection. According to the standard, the Wait Timeout T1 default value is 15000 ms. | ms | 15 000 |
| Timeout for sending the confirmation of a received I-frame. Wait Timeout T2 < Wait Timeout T2. If other another I-frame (which confirms the received I-frame) is not sent in the time within Wait Timeout T2 time since the I-frame was received, so the process D2000 KOM process sends a an S-frame confirming the received I-frame to the partner. According to the standard, the Wait Timeout T2 default value is 10000 ms. | ms | 10 000 |
| Timeout for sending test frames ( TEST ACT U-frame TEST ACT). If no data are sent in any direction for a long time, an a TEST ACT U-frame TEST ACT will be sent to after the process D2000 KOM after expiration of the Wait Timeout T3 time and there by the D2000 KOM process, and a TEST CON U-frame is expected (in the within Wait Timeout T1 time after sending) receiving a U-frame TEST CON. If the Wait Timeout T3 on the partner side is set to a lower value, it sends the test frames, and the process D2000 KOM reply process replies to them. According to the standard, the Wait Timeout T2 default value is 20000 ms.
Setting the value to 0 disables sending test frames. | ms | 20 000 |
| Timeout for receiving the confirmation of a sent value. Receiving e.g. S-frame with RSN (Receive Sequence Number) confirming, that the other party received the previous I-frame doesn't mean, that the I-frame was processed. In Within the Wait Timeout Tn time interval, the process D2000 KOM process waits for receiving the response (e.g. after sending ASDU with TypeIdentificator=45 [Single Command] with CauseOfTransmission=6 [Activation] there is expected , the receiving of Single Command with CauseOfTransmission=7 [Activation Confirmation] is expected.
After the expiration of the Wait Timeout Tn, the process D2000 KOM process closes the TCP connection. | ms | 60 000 |
