Porovnávané verzie

Kľúč

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

IEC 60870-5-104 Server communication protocol


Supported device types a and versions  
Communication line configuration
Communication station configuration
I/O tag configuration
Tell TELL commands
Literature
Document revisions

...

  • Originator ASDU address is 1 byte, it is defined as a line number.
  • ASDU address is 2 bytes, it is defined as station address. For each station on a line, a different ASDU address must be defined.
  • Cause of transmission is 2 bytes (it also contains Originator ASDU address)
  • Information object address IS 3 bytes, it is defined as an I/O tag address.
  • The following ASDU types in the direction of monitoring are implemented (from the D2000 system to the control station and also vice-versa in balanced mode):


Kotva
tab1
tab1
Table nr. 1Table 1


ASDU typeI/O tag type
1 - Single-point informationDout
2 - Single-point information with time tagDout
3 - Double-point informationDout,Cout
4 - Double-point information with time tagDout,Cout
5 - Step position informationCout
6 - Step position information with time tagCout
7 - Bitstring of 32 bitsCout
8 - Bitstring of 32 bits with time tagCout
9 - Measured value, normalized valueAo
10 - Measured value, normalized value with time tagAo
11 - Measured value, scaled valueCout
12 - Measured value, scaled value with time tagCout
13 - Measured value, short floating point valueAout
14 - Measured value, short floating point value with time tagAout
15 - Integrated totalsCout
16 - Integrated totals with time tagCout
20 - Packed single-point information with status change detectionCout *
21 - Measured value, normalized value without quality descriptorAi
30 - Single-point information with time tag CP56Time2aDout
31 - Double-point information with CP56Time2a tagDout,Cout
32 - Step position information with CP56Time2a tagCout
33 - Bitstring of 32 bits with CP56Time2a tagCout
34 - Measured value, normalized value with CP56Time2a tagAout
35 - Measured value, scaled value with CP56Time2a tagCout
36 - Measured value, short floating point value with time tag CP56Time2aAout
37 - Integrated totals with time tag CP56Time2aCout
241 - 64-bit floating point value (Ipesoft & URAP implementation)Ao
243 - 64-bit floating point value with time tag CP56Time2a (Ipesoft & URAP implementation)Ao
251 - Archive data values (Ipesoft's implementation)none **
252 - D2000 Unival (Ipesoft's implementation)all

...

The exception is the bits, which are set directly by a value (e.g. for ASDU 1, the 0.bit is not set by the FLA flag but by the value of output I/O tag).
If the Invalid attribute is set for a new value, the highest bit (IV) will be set in the status byte of for all ASDUs (except for ASDU 21, which does not have a status byte).

...

The following ASDU types in the direction of control are implemented (from the control station to D2000, also the opposite direction in balanced mode):


Kotva
tab2
tab2
Table nr. 2 Table 2


ASDU typeI/O tag type
45 - Single commandDi, Qi
46 - Double commandQi
47 - Regulating step commandDi, Qi
48 - Set point command, normalised valueAi
49 - Set point command, scaled valueCi
50 - Set point command, short floating point valueAi
51 - Bitstring of 32 bitCi
58 - Single command with time tag CP56Time2aDi, Qi
59 - Double command with time tag CP56Time2aQi
60 - Regulating step command with time tag CP56Time2aDi, Qi
61 - Set point command, normalised value with time tag CP56Time2aAi
62 - Set point command, scaled value with time tag CP56Time2aCi
63 - Set point command, short floating point value with time tag CP56Time2a Ai
64 - Bitstring of 32 bit with time tag CP56Time2aCi
250 - Archive data request command (Ipesoft's implementation)none **
252 - D2000 Unival (Ipesoft's implementation)all (except Qi)

...

The following parameters can be defined as station protocol parameters:


Table nr. 3Table 3


KeywordFull nameMeaningUnitDefault value
Kotva
cmdc
cmdc
CMDC
Command ConfirmConfirmation of control ASDU.
If CMDC=0, the D2000 KOM process does not confirm any control ASDU from the partner station by replying with an ASDU with an appropriate CauseOfTransmission.
If CMDC=1, the D2000 KOM process confirms control ASDUs with CauseOfTransmission=7 (Activation Confirmation).
If CMDC=2, the D2000 KOM process confirms control ASDUs with CauseOfTransmission=10 (Activation Termination).
If CMDC=3, the D2000 KOM process confirms control ASDUs with CauseOfTransmission=7 and CauseOfTransmission=10.
-1
Kotva
d2cls
d2cls
D2CLS
D2CPA
D2VCO
The 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 ...
Kotva
d2h64
d2h64
D2H64
D2000 64-bit Historical ValuesWhen sending historical values (as an answer to a request for historical data), ASDU 249 will be used, which uses a 64-bit representation of floating points (the same as D2000 internally), instead of default ASDU 251 (which encodes the values as 32-bit floating points) to improve precision.
Note: Before enabling this parameter, you should verify that also the client supports ASDU 249. This support was implemented in November 2011 for D2000 v8.00.011.
-False
Kotva
dbgi
dbgi
DBGI
Debug InputA mask for debug levels of input data. The meaning of bits is as follows:
  • 0.bit - displays a number of incoming values during General Interrogation
  • 1.bit - displays all incoming values
  • 2.bit - balanced mode: requesting Interrogation command was received
-0
Kotva
dbgo
dbgo
DBGO
Debug OutputA mask for debug levels of output data. The meaning of bits is as follows:
  • 0.bit - balanced mode: displays a number of outgoing values during General Interrogation
  • 1.bit - displays all outgoing values
-0
Kotva
eoi
eoi
EOI
End of initializationIf EOI=0, the D2000 KOM process doesn't send ASDU 70 (End of initialisation). If EOI=1 and a client sends StartDT U-frame Act, the D2000 KOM process responds by StartDT Con and sends ASDU 70.-0
Kotva
gisn
gisn
GISN
GI Send NewIf GISN=True, then the D2000 KOM process after receiving the General Interrogation command sends also values with newer times than is the time when the command is received. The value of the GI Send New parameter must be True to send values with future times in a reply to the General Interrogation command.-False
Kotva
icf3
icf3
ICF3
Ignore Control Field 3 bit 0Determines behavior if ASDU contains Control Field with bit 0 (test) set in the 3rd byte (Receive).
  • if ICF3=False (default), ASDU content is to be processed
  • if ICF3=True, ASDU content is to be ignored
The feature is useful when creating a redundant TCP connection (TCP Redundant line + IEC 870-5-104 protocol). That active client should send ASDUs without the Test bit set and the passive client should send ASDUs with the Test bit set.
-False
Kotva
iii
iii
III
Ignore Invalids on InterrogationIf this parameter is set on a station, the D2000 KOM process will not send values of I/O tags which are Invalid or Unknown, in a reply for ASDU 100 and 101 (Interrogation/Counter interrogation commands). The parameter can be used e.g. for control applications - if sending Invalid values causes problems in control.-False
Kotva
it
it
IT
Ignore Tests

Determines behavior if ASDU contains the highest 7th bit (Test) set in CauseOfTransmission.

  • if IT=0 (default), ASDU content will be processed
  • if IT=1, ASDU content will be ignored
  • if IT=2, a Weak attribute will be set
The feature is useful when creating a redundant TCP connection. The active client should send ASDUs without the Test bit set and the passive client should send ASDUs with the Test bit set.
-0
Kotva
iua
iua
IUA
Ignore Unknown AddressesIf IUA=TRUE, the D2000 KOM processD2000 Komwill 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
Kotva
ii
ii
II
Implicit InterrogationBalanced mode: After connecting the client, the values of all variables are automatically sent without any need for ASDU 100 and 101 [Interrogation/Counter Interrogation Command] requests.-False
Kotva
icci
icci
ICCI
Interrogation Covers Counter InterrogationAs a reply to Interrogation, ASDUs 15,16,37 (Integrated Totals) will be also sent, which are by default requested by ASDU 101 [Counter Interrogation].-False
Kotva
igo
igo
IGO
Interrogation Groups ObjectsOptimization of sending values during General Interrogation (answer to Interrogation Command/Counter Interrogation Command). If IGO=True, multiple values will be sent inside a single ASDU (so that the length of ASDU is within maximum defined by the standard - 253 Bytes). This parameter does not influence change-based sending of values during normal communication.-False
Kotva
iua
iua
IWOT
Interrogation WithOut TimestampsIf Interrogation WithOut Timestamp=True then values sent as a response to ASDU 100 [Interrogation Command] 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 a situation when the values have been invalidated as a result of communication error and, after the communication is re-established, the values come with old timestamps which causes problems in the D2000 Archive (if the values change only rarely, calculated historical values 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
Kotva
k
k
K
KSending window size i.e. packet quantity, which is 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
mc
mc
MC
Maximum ClientsThe maximum number of connected clients. The parameter is needed for D2000 OpenVMS, where a task pool containing 2 * MC tasks for client handling (one task for receiving data, one task for sending data) is created during KOM startup. If the value of the Maximum Clients parameter is equal to 0, the number of clients is not limited and threads are created dynamically as needed.-0
Kotva
nf
nf
NF
No FlagsIf the value of 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 don't influence the status byte.-False

Kotva
ocic
ocic
OCIC

Order of Counter ICBalanced mode: Order of sending of ASDU 101 [Counter Interrogation Command] when initializing the connection. If OCIC<OIC, then ASDU 101 is sent before ASDU 100. If OCIC= 0, ASDU 101 is not sent. The parameter can be defined for each of the stations.-0

Kotva
oic
oic
OIC

Order of ICBalanced mode: Order of sending of ASDU 100 [Interrogation Command] when initializing the connection. If OIC<OCIC, then ASDU 100 is sent before ASDU 101. If OIC= 0, ASDU 100 is not sent. The parameter can be defined for each of the stations.-0
Kotva
pw
pw
PW
Pessimistic WriteDefines the evaluation of writing success in case of a connection of more than one client. If PW=0, writing a value is considered to be successful if at least one client confirms it (confirmation method is defined by the CMDC parameter). If PW=1, writing must be confirmed by all connected clients. If at least one client doesn't confirm it (e.g. connection failure occurs or the confirmation is negative), writing is considered to be unsuccessful.-0
Kotva
ssn
ssn
SSN
Send sequence numberThe initial Send sequence number after the TCP connection is established. 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
Kotva
sko
sko
SKO
Standby Keep OpenIf True, after changing the status of the D2000 Server process (the  D2000 KOM process is connected to) from Hot to Standby state (in a redundant system), connections with clients will not be closed, and listening for new clients will not be aborted.-False
Kotva
sscf3
sscf3
SSCF3
Standby Set Control Field

If True, after changing the status of the D2000 Server process (the  D2000 KOM process is connected to) from Hot to Standby state (in 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 behavior does not strictly follow the standard and we recommend using the Standby Set Test Bit parameter instead of this parameter if it is possible.

-False
Kotva
sstb
sstb
SSTB
Standby Set Test BitIf True, after changing the status of the D2000 Server process (the  D2000 KOM process is connected to) from Hot to Standby state (in a redundant system), the Test bit will be set in Cause Of Transmission.-False
Kotva
swv
swv
SWV
Standby Write ValuesIf True, after changing the status of the D2000 Server process (the  D2000 KOM process is connected to) from Hot to Standby state (in a redundant system), the server will send new values to clients.-False
Kotva
w
w
W
WThe number of received I-frames, after which the D2000 KOM process sends 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
Kotva
wt1
wt1
WT1
Wait Timeout T1

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 D2000 KOM process does not receive the confirmation within Wait Timeout T1 time, it closes the TCP connection. According to the standard, the Wait Timeout T1 default value is 15000 ms

ms15 000
Kotva
wt2
wt2
WT2
Wait Timeout T2

Timeout for sending the confirmation of a received I-frame. Wait Timeout T2 < Wait Timeout T1. If another I-frame (which confirms the received I-frame) is not sent within Wait Timeout T2 time since the I-frame was received, the D2000 KOM process sends an S-frame confirming the received I-frame to the partner. According to the standard, the Wait Timeout T2 default value is 10000 ms.

ms10 000
Kotva
wt3
wt3
WT3
Wait Timeout T3

Timeout for sending test frames ( TEST ACT U-frame). If no data are sent in any direction for a long time, a TEST ACT U-frame will be sent after the expiration of the Wait Timeout T3 time by the D2000 KOM process, and a TEST CON U-frame is expected (within Wait Timeout T1 time after sending). If the Wait Timeout T3 on the partner side is set to a lower value, it sends the test frames, and the D2000 KOM 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.

ms20 000
Kotva
wtn
wtn
WTN
Wait Timeout No answer

Balanced mode: Timeout for receiving the confirmation of a sent value in a control direction (ASDUs 45 - 64). 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. Within the Wait Timeout No answer time interval, the D2000 KOM process waits for receiving the response (e.g. after sending ASDU with TypeIdentificator=45 [Single Command] with CauseOfTransmission=6 [Activation], the receiving of Single Command with CauseOfTransmission=7 [Activation Confirmation] is expected. 

After the expiration of the Wait Timeout Tn, the D2000 KOM process closes the TCP connection.

ms60 000

...

If a keyword with an invalid value in the initialization string is found, a corresponding default value according to the table Table 3 will be used. Defined parameters, except for OIC, OCIC and FST are valid for the entire line - i.e. it is enough to define them for one station on the line.

...