História stránky

...

The protocol is a modification of the protocol IEC870-5-104 working on the basis of TCP network communication. The protocol has been modified specifically for redundant communication with the system Siemens Sinaut Spectrum. It supports the balanced mode and active and passive establishing the communication (connecting party and listening party) according to the station protocol parameters, and therefore allows to interconnect not only D2000 system with Sinaut system but also two D2000 systems.

Picture: D2000 redundant system communicating with Sinaut redundant system in redundant network

Image Modified

The picture above shown TCP connections - each process D2000 KOM(D2000 Hot, D2000 StandBy) with eachSinaut (Sinaut Hot, Sinaut StandBy)

Implementation according to the standard IEC870-5-104 is following:

• Originator ASDU address - is 1 byte, it is defined as a line number.
• ASDU address - is 2 bytes, it is defined as station address. Foe each station on one line, there must be defined different ASDU address.
  Note: Because of Sinaut data model, the low and high address bytes are changed unlike the standard IEC 104 implementation, i.e. big endian instead of little endian.
  Example: 
  station address=1, ASDU address is sent as 0, 1 bytes
  station address=513 (2*256+1), ASDU address is sent as 2, 1 bytes
  For better orientation, station address may be defined in the form of ByteHI,ByteLO, i.e. address  2,1 instead of 513
• Cause of transmission - is 2 bytes (it also contains Originator ASDU address)
• Information object address - 3 bytes, it is defined as I/O tag address
  Note: Because of Sinaut data model, the low and high address bytes are changed unlike the standard IEC 104 implementation, i.e. big endian instead of little endian.
  Example:
  I/O tag address=1, ASDU address is sent as 0, 0, 1 bytes.
  I/O tag address=66051(1*65536+2*256+3), ASDU address is sent as bytes 1, 2, 3.
  For better orientation, I/O tag address may be defined in the form of ByteLO,ByteMIDDLE,ByteHI, i.e. address 1,2,3 is sent as bytes 1, 2, 3.

There are implemented the following ASDU types in the direction of logging (from Sinaut system to D2000 system and also vice-versa in balanced mode):

Kotva
tab1 tab1

Table 1

Note: The individual bites of the byte that inform us on quality (SIQ for ASDU 1,2,30; DIQ for ASDU 3,4,31; QDS for 5..14,20,32..36) are mapped to the flags FLA (0.bit),FLB (1.bit) ..FLH (7.bit).
For example:
for ASDU 4: FLA=DPI bit 0, FLB=DPI bit 1, FLC=0, FLD=0, FLE=BL bit, FLF=SB bit, FLG=NT bit,FLH=IV bit.
for ASDU 16: FLA..FLE Sequence number bity 0..4, FLF=CY bit, FLG=CA bit, FLH=IV bit

...

Kotva
pozn1 pozn1

* - T-bit of the value of these ASDUs is in the flag FI, a number within -64 .. +63 is in a variable of Ci/Ai type

Kotva
pozn2 pozn2

** - ASDU 17 and 38: SEP byte is in the flags FLA (0.bit),FLB (1.bit) ..FLH (7.bit), following 2 bytes (CP16Time2a) are in a variable of Ci/Ai type as a positive number (0-60 000) or they are in a variable of TiR type as a relative time (0-60 seconds)

Kotva
pozn3 pozn3

The following ASDU types are implemented in the control course (from D2000 system to Sinaut system and vice-versa in balanced mode):

Kotva
tab2 tab2

Table 2

To set the bites of "status" (SCO for ASDU 45,58; DCO for ASDU 46,59; RCO for ASDU 47,60; QOS for ASDU 48..50,61..63), there are used the flags FLA (0.bit),FLB (1.bit) ..FLH (7.bit) except the bites, which are directly set by the variable value ( SCO bit 0, DCO and RCS bites 0-1). Having received a response (positive/negative), the flags FLA..FLH are set according to the bites of the "status" byte.

...

The protocol IEC870-5-104 Sinaut supports the balanced mode described in the communication protocol IEC 870-5-104 - it is server in part, so the rules of  server protocols are valid for it.

...

Kotva
komunikacna_stanica komunikacna_stanica

Communication station configuration

...

• Communication protocol: IEC870-TCP Sinaut.
• Station address is a decimal number within the range of 0 až 65535, defines the ASDU address.
  For better orientation, station address may be defined in the form of ByteLO,ByteHI,ByteLO, i.e. address 2,1 instead of 513address 1,2 is the same as 513 (1+2*256).

Note: The protocol supports sending long time stamps (CP56Time2a tag) in local time or UTC time with defined offset (see the parameter Use monotonic UTC time +).

...

Station configuration dialog box - tab Protocol parameters.
They influence some of optional protocol parameters. There can be defined the following station protocol parameters:

Table 3

The defined parameters, except for Order of IC and Order of Counter IC, are valid for the entire line, i.e. they can be set only for one station on the line.

Kotva
iccp iccp

ICCP compatible flag mapping

A status byte of ASDU, unlike ICCP OPC communication, enables the transmission only 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.

Table 4

Kotva
merany_bod merany_bod

IO tag configuration

...

Permitted I/O tag types: Ai, Ao, Ci, Co, Di, Dout, Qi

• I/O tag address is mapped to Information object address, i.e. contains 3 bytes and must be within the interval of 0...16777215.
  For better orientation, I/O tag address may be defined in the form of ByteHIByteLO,ByteMIDDLE,ByteLOByteHI, i.e. address 1 address 3,2,3 instead of 660511 is the same as 66051 (3 + 2*256 + 1*256*256).
• Input I/O tags must have corresponding types (Ai, Ci, Di, Qi) for received ASDU, see the table 1.
• For particular type of output I/O tag (Ao, Dout, Co), it is necessary to set an 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 output I/O tags on the same address, while 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 a new value to the I/O tagM1. Writings of the I/O tags M2, M3 gives a new value to the I/O tag P2on the partner's side.

...