Porovnávané verzie

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Full nameMeaningUnitDefault value
Kotva
cmdc
cmdc
Command Confirm
Confirmation of control ASDUs.
If CMDC=0, the process D2000 KOM is not waiting for confirmation of control ASDUs from the partner station using reply ASDU with a different CauseOfTransmission. The ASDU is considered to be confirmed when a packet containing the corresponding ReceiveSequenceNumber is received.
If CMDC=1, the process D2000 KOM is waiting for confirmation with CauseOfTransmission=7 (Activation Confirmation).
If CMDC=2, the process D2000 KOM is waiting for confirmation with CauseOfTransmission=10 (Activation Termination).
If CMDC=3, the process D2000 KOM is waiting for confirmation with CauseOfTransmission=7 or 10 (if both of them are received, just the first of them is taken into account).
Having received the corresponding confirmation means that writing is finished (the Transient attribute of written value is cleared and the WTn timer is reset).
If a confirmation with other CauseOfTransmission than the D2000 KOM process is expecting 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.
The value from a received ASDU is written into the corresponding I/O tag and it 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), then this value will be sent to the system by the D2000 KOM process.
-3
Kotva
dbgi
dbgi
Debug Input
A mask for a debug level of the input data. Meaning of individual bits:
  • 1. bit - information about the number of points received within General Interrogation
  • 2. bit - information about received values of I/O tags
  • 3. bit - balanced mode: information about received Interrogation command 
  • 4. bit - information about discarded values due to the setting of the Ignore Flagged parameter
0 .. 2550
Kotva
dbgo
dbgo
Debug Output
A mask for a debug level of the output data. Meaning of individual bits:
  • 1.bit - balanced mode: information about the number of points sent within General Interrogation
  • 2.bit - information about sent values of I/O tags
0 .. 2550

Kotva
iccpf
iccpf
ICCP compatible flags

It allows a flag mapping that is compatible with the Sinaut Spectrum ICCP OPC communication. For more information see ICCP compatible flag mapping.YES/NONO

Kotva
if
if
Ignore Flagged

The parameter allows specifying the flags of values (data ASDU 1-40), which - if set - will cause the incoming value to be discarded. The parameter was implemented when it was necessary to filter out the "Non-topical" flag values that came from the communication partner.

The mapping of individual flags from ASDU to A..H flags is as follows:

  • A - Overflow (OV) - ASDU 5-14, 20, 32-36
  • B - no mapping (according to standard this bit should be 0)
  • C - no mapping (according to standard this bit should be 0)
  • D - Elapsed Time Invalid (EI): ASDU 17-19, 38-40
  • E - Blocked (BL) - ASDU 1-14, 17-20, 30-36, 38-40
  • F - Substituted (SB) - ASDU 1-14, 17-20, 30-36; Counter overflow (CY) - ASDU 15, 16, 37
  • G - Non-topical (NT) - ASDU 1-14, 17-20, 30-36; Counter adjusted (CA) - ASDU 15, 16, 37
  • H - Invalid (IV) - ASDU 1-20, 30-40
A..H-
Kotva
iua
iua
Ignore Unknown Addresses
If this parameter is set to True, the D2000 KOM processD2000 Komwill not report an error (display an error on its console or write it into the line log file) in case that incoming value has an address which does not match any of the addresses of I/O tags defined in the D2000 system.-False
Kotva
icci
icci
Interrogation Covers Counter Interrogation
As a reply to Interrogation, there also the ASDU 15,16,37 (Integrated Totals) will be sent, which are usually requested by ASDU 101 [Counter Interrogation].-True
Kotva
k
k
K (max outstanding I APDUs)
Sending window size i.e. number of packets, which are 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
Kotva
nf
nf
No Flags
If the parameter is True, then the status byte of incoming ASDUs is ignored and not saved into the flags FA ... FH. Flags of output I/O tags are also ignored and they not written to the status byte.-False
Kotva
oic
oic
Order of IC
The order for sending ASDU 100 [Interrogation Command] when the station starts to communicate or when a new station is created. If OIC<OCIC, ASDU 100 will be sent before ASDU 101. If OIC=0, ASDU 100 will not be sent. The parameter can be set separately for each station.-1
Kotva
ocic
ocic
Order of Counter IC
The order for sending of sending ASDU 101 [Counter Interrogation Command] when the station starts to communicate or when a new station is created. If OCIC<OIC, ASDU 101 will be sent before ASDU 100. If OCIC=0, ASDU 101 will not be sent. The parameter can be set separately for each station.-0
Kotva
pcnt
pcnt
Ping Count
A number of repetitions, after which the IP address not responding to ping is to be known as non-functional.
See the parameter Ping TimeOut.
-3
Kotva
pto
pto
Ping TimeOut
If the parameter is non zero, it defines the timeout (in milliseconds) of a server response to a ping (ICMP echo) packet. In the background, the D2000 KOM process sends ping packets to all four configured IP addresses. If an IP address repeatedly does not respond Ping Count-times, it is marked as non-functional and the connection is terminated. If the parameter PTO=0, sending ping packets to IP addresses is disabled.-0
Kotva
psd
psd
Post Start Delay
When the connection is being established, this parameter defines the delay between receiving StartDT Con response and sending Interrogation Command and/or Counter Interrogation Command.ms0

Kotva
ssn
ssn
Send Sequence Number

Initial SSN. According to the standard, after establishing the connection the SSN is set to 0, values other than zero could be used e.g. for testing.-0
Kotva
spsh
spsh
Server Port, Server Host
The port number and IP address of the interface where the D2000 KOM process should listen (in a listening mode). If both the parameters are defined, the D2000 KOM process is working as passive (it is waiting for connecting Sinaut clients). If the process should listen on all network interfaces, Server Host must be set to ALL.-
Kotva
sko
sko
Standby Keep Open
If this parameter is set to True, the connection to the partners will not be closed when the status of the D2000 Server process (the process D2000 KOM is connected to) is changed from Hot to Standby state (in a redundant D2000 system).-True
Kotva
st_ce
st_ce
Station Communication Error
The number of unsuccessful attempts to connect after a communication error, after which the station status is changed into the St_CommErr state. For redundant lines, the communication must fail on both TCP connections.-2
Kotva
st_he
st_he
Station Hard Error
The number of unsuccessful attempts to connect after a communication error, after which the station status is changed into the St_HardErr state. For redundant lines, the communication must fail on both TCP connections.-5
Kotva
srcs
srcs
Strict Redundancy Connection Signalisation
The number of TCP connections, which must be opened so that the line could be considered as OK. There are 4 connections (2x Sinaut servers, each of them has 2 network addresses).-4
Kotva
tki
tki
Tcp Keep Init
The parameter is implemented for OpenVMS platforms only. If it is other than zero, then defines the timeout (in seconds) for opening a new connection to the server. For OpenVMS, the default value is 75 seconds, for Windows, it is 20 seconds.-0
Kotva
tnd
tnd
TCP NoDelay
TND parameter sets a low-level parameter of TCP_NODELAY sockets which disables a default TCP packet coalescing.

Kotva
w
w
W (ack after receiving W APDUs)
The number of received packets, after which the D2000 KOM process sends an S-frame confirmation. According to the standard, the default value is 8. It must be true that W < K, the standard recommends W = 2/3 * K.-8
Kotva
wt1
wt1
Wait Timeout T1
The timeout for receiving the a confirmation of a sent I-frame sent (either the a confirmation within the a received I-frame or the individual S-frame itselfis expected) or a sent U-frame. If the process D2000 KOM process does not get receive the confirmation in the time within WT1 limit, it closes the TCP connection. According to the standard, the WT1 default value of WT1 is 15000 ms.ms15 000
Kotva
wt2
wt2
Wait Timeout T2
Timeout The timeout for sending the a confirmation of a received I-frame received. WT2 < WT1. If another I-frame (which confirms the the received I-frame received) is not sent in within the time WT2 limit since the I-frame was received, so then the process D2000 KOM process sends an S-frame confirming the received I-frame to the partner. According to the standard, the WT2 default value of WT2 is 10000 ms.ms10 000
Kotva
wt3
wt3
Wait Timeout T3
Timeout The timeout for sending test frames (U-frame TEST ACT). If no data are sent in any direction for a long longer time than WT3, an a TEST ACT U-frame TEST ACT will be sent to by the process D2000 KOM after expiration of the WT3 time and there process and a U-frame TEST CON is expected (in within the WT1 time after sending) receiving a U-frame TEST CONlimit). If the WT3 on the partner side is partner's WT3 is set to a lower value, it sends the test frames and the process D2000 KOM process replies to them. According to the standard, the WT2 default value of WT3 is 20000 ms. Setting the value to 0 disables sending test frames.ms20 000
Kotva
wtn
wtn
Wait Timeout N
Timeout for The timeout for receiving the confirmation of a sent value sent. 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 WTn time limit, the process D2000 KOM waits for receiving the process expects a response (e.g. after sending ASDU with TypeIdentificator=45 [Single Command] with CauseOfTransmission=6 [Activation] there is expected receiving it expects to receive a Single Command with CauseOfTransmission=7 [Activation Confirmation].
After the expiration of the WTn time timeout, the process D2000 KOM process closes the TCP connection.
ms60 000

The defined parameters, except for with the exception of Order of IC and Order of Counter IC, are valid for the entire communication line, i.e. they can have to be set only for one a single station on the line.

Kotva
iccp
iccp
ICCP compatible flag mapping

A status byte of ASDU, unlike Unlike ICCP OPC communication, enables a status byte of individual ASDUs permits the transmission only of a limited group of flags. In Table 4 you can see a conversion of bits of the status byte to the flags which are compatible with ICCP OPC communication (see the ICCP compatible flags parameter).

Table 4

Bits of status byte

DescriptionICCP OPC mapping
8 [IV invalid]7 [NT non topical]6 [SB substituted]5 [BL blocked]1 [OV overflow]
1xxxxINVALIDFH (NotValid)
0x00xVALIDFA (Actual)
0x01xBLOCKEDFD (Blocked)
0x10xSUBSTITUTEDFC (Entered)
0x11xSUBSTITUTED + BLOCKEDFF (Blocked Manual)

...

  • I/O tag address is mapped to the Information object addressObject Address, i.e. contains 3 bytes and must be within the interval of 0...16777215.
    For better orientation, the I/O tag address may be defined in the form of ByteHI, ByteMIDDLE, ByteLO, i.e. address 1,2,3 is the same as 66051 (1*256*256 + 2*256 + 3). See a See note about the IOA address.
  • Input The input I/O tags must have corresponding types (Ai, Ci, Di, Qi) for received ASDU, see the see table 1.
  • For particular type of output I/O tag (Ao, Dout, Co), it is necessary to set an ASDU type of ASDU that should be used, see the table 1 and table 2.
  • It is possible to configure one input I/O tag and more multiple output I/O tags on the same address, while as long as the output I/O tags have different ASDUs. Example:
    • I/O tag M1, Di type, address 1,
    • I/O tag M2, Dout type, address 1, ASDU 1 (single-point information)
    • I/O tag M3, Dout type, address 1, ASDU 45 (single command)

    Configuration on partner's side:
    • I/O tag P1, Dout type, address 1, ASDU 1 (single-point information)
    • I/O tag P2, Di type, address 1

    Writing into the I/O tag P1 from the partner's side gives results in a new value written to the I/O tagM1. Writings of tag M1. Writing to the I/O tags M2, M3 gives results in a new value to the I/O tag P2on P2 on the partner's side.


Kotva
tell_cmd
tell_cmd
Tell commands

...