IEC

...

60870-5-104 Sinaut communication protocol

Supported device types and versions
Communication line configuration
Communication station configuration
Station protocol parameters
I/O tag configuration
Tell commands
Literature
Document revisions

...

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

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

Image Modified

The picture above shown shows TCP connections - each process D2000 KOM (D2000 Hot, D2000 StandBy) with eachSinaut each Sinaut (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 For each station on one line, there a different ASDU address must be defined different ASDU address.
  

  Kotva
  NOTE_ASDUADDR NOTE_ASDUADDR

  Note: Because of the Sinaut data model, the low and high address bytes are changed unlike exchanged (in contrast to the standard IEC 104 implementation), i.e. a big-endian instead of a little-endian is used.
  Example: 
  station address=1, ASDU address is sent as bytes 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 is the same as 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
  

  Kotva
  NOTE_IOA NOTE_IOA

  Note: Because of the Sinaut data model, the low and high address bytes are changed unlike are exchanged (in contrast to the standard IEC 104 implementation), i.e. a big-endian instead of a little-endian is used.
  Example:
  I/O tag address=1, ASDU address is sent as bytes 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, the 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 The following ASDU types in the monitoring direction of logging (from Sinaut system to D2000 system and also vice-versa in balanced mode) are implemented:

Kotva
tab1 tab1

Table 1

Note: The individual bites Individual bits of the quality 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 A (bit 0.bit), FLB B (bit 1.bit) .. FLH H (bit 7.bit).
For example:
for ASDU 4: FLA  A=DPI bit 0, FLBB=DPI bit 1, FLCC=0, FLDD=0, FLEE=BL bit, FLFF=SB bit, FLGG=NT bit, FLHH=IV bit.
for ASDU 16: FLAA..FLE E = Sequence number bity bits 0..4, FLFF=CY bit, FLGG=CA bit, FLHH=IV bit

Moreover:

• if a bit is set to IV (Invalid) bit is set, the value state status will be Invalid
• if some any of the bits are set to NT (Not topical), SB (Substituted), BL (Blocked), OV (Overflow), CA (Counter adjusted), CY (Counter overflow) bits are set for corresponding ASDU types, the value state status will be Weak.

Kotva
pozn1 pozn1

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

Kotva
pozn2 pozn2

** - ASDU 17 and 38: SEP byte is in the flags FLA A (bit 0.bit), FLB B (bit 1.bit) .. FLH H (bit 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 direction (from D2000 system to Sinaut system and vice-versa in balanced mode):

Kotva
tab2 tab2

Table 2

To set the bites bits of the "status" byte (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 A (bit 0.bit), FLB B (bit 1.bit) .. FLH H (7.bit) are used except the bitesbits, which are directly set by the variable value ( SCO bit 0, DCO and RCS bites bits 0-1). Having received a response (positive/negative), the flags FLAA .. FLH H flags are set according to the bites bits of the "status" byte.

When sending commands (ASDU ASDUs 45-64), the value of 6 [Activation] is used as CauseOfTransmission. Expecting Whether a response is expected from the controlled station depends on the parameter CMDC parameter. There are the following possibilitiesThese options are available:

• write Writing is considered successful , if there is a packet with RSN confirming the SSN packet with the logwrite command is received.
• Writing is considered finished if write is finished, if there is a response with CauseOfTransmission=7 [Activation Confirmation] and/or 10 [Activation Termination] is received. Success/Unsuccess failure depends on the setting of the P/N bite bit in received CauseOfTransmission.

Redundant communication with Siemens Sinaut system - 

...

basic features:

• One communication line of CP Redundant type a TCP/IP-TCP Redundant type communicates with two redundant Sinaut partners Sinaut, where one of them is HOT, the other is STANDBY.
• Communication to with each of the partners is performed through via two redundant networks (i.e. there are created two TCP connections are created for each Sinaut, together so altogether there are four TCP connections by every D2000 KOM process).
• Sending Only the HOT partner (D2000 or Sinaut) is allowed to send new values and replying reply to ASDU 100 [Interrogation Command] is allowed just HOT partner (D2000 eventually Sinaut). Having established the connection, the STANDBY partner only sends confirmations (S-frames) and test frames. However, the STANDBY partner may also send ASDU 100 [Interrogation Command].
• Each partner communicates to the other just through one participant communicates with a partner through a single TCP connection. It sends new values, command confirmations, ASDU 1000 100, and replies to ASDU 100 through the this connection. Second The second connection is standing not used (except for sending test frames through it) and it is only used when a failure on the first connection is detected.

Establishing a connection:

• In the active mode, the process D2000 KOM process connects to specified TCP ports. It sends to a StartDT Act U-frame to each of the ports an U-frame StartDT Act, and waits for a StartDT Con as reply.
• In the passive mode, the process the D2000 KOM process waits on a specified TCP port (see the parameters SP, SH parameters). When the clients are connected, the process waits for an a StartDT Act U-frame StartDT Act, and sends a StartDT Con as reply.
• Further communication is completely symmetrical one. Both partners can send ASDU 100 [Interrogation Command] in order to read all current values and then the partners receive and sends send changed values and commands.

Having established the connection, a partner may send I-frame with ASDU 100 [Interrogation Command] with CauseOfTransmission=6 [Activation] and with ASDUAddres=FFFF, whereby it requests the values of I/O tags for all stations.   As a replay, the partner waits for:

• receiving an I-frame with ASDU 100 [Interrogation Command] and with CauseOfTransmission=7 and ASDUAddresASDU Address=FFFF
• receiving the current values of all I/O tags
• receiving an I-frame with ASDU 100 [Interrogation Command] and with CauseOfTransmission=10 and ASDUAddresASDU Address=FFFF

Forced disconnection: If all communication stations on the line are in the simulation mode or the communication is disabled stopped for them, the communication line will be disconnected (closing communication sockets will be closed). If When the simulation mode is not enabled and turned off or the communication is not disabled enabled for at least one one station (the the Parameters tab Parameters of object of the Station type object), the line will be reconnected (and Interrogation Command eventually and/or Counter Interrogation Command will be send sent to the this active station). Then after enabling each next station, there is send an Interrogation Command , when other stations are enabled, the Interrogation Command and/or Counter Interrogation Command is sent to the this station; see the next point.

Forced sending of Interrogation Command or Counter Interrogation Command: If a station is in the status, that it is not in the simulation mode and the communication is not disabled (the Parameters tab Parameters of object of the Station type object), the process D2000 KOM process sends Interrogation Command and/or Counter Interrogation Command (see the parameters OIC,  and OCIC parameters).

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

Kotva
komunikacna_linka komunikacna_linka

Communication line configuration

...

• Communication line category: TCP/IP-TCP Redundant
• TCP parameters:
  • Host: string containing at most 80 characters – two comma-separated server IP addresses in the form of a.b.c.d
    In the active mode, they are the addresses of the server, where to which the process D2000 KOM process is connecting to.
    In the passive mode (see the parameters SP, SH), they are the IP addresses of a clientclients, which are accepted by the process D2000 KOM process (if the client is connecting from other IP address, it will be disconnected).
  • Port: TCP port number (0...65535)
    In the active mode, it is the server port, where the process D2000 KOM process is connecting to.
    In the passive mode (see the parameters SP, SH parameters), the parameter will be ignored (but however it must be specified, set , it e.g. to the value of 0).
  • Line number: it is used as Originator ASDU address (1 byte, 0-255).

Kotva
komunikacna_stanica komunikacna_stanica

Communication station configuration

...

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

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

Kotva
stanica_parametre stanica_parametre

Station protocol parameters

...

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

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.

...

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

...

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

...

• 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)

...

• I/O tag P1, Dout type, address 1, ASDU 1 (single-point information)
• I/O tag P2, Di type, address 1

...

The defined parameters, 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 a single station on the line.

Kotva
iccp iccp

ICCP compatible flag mapping

Unlike ICCP OPC communication, a status byte of individual ASDUs permits the transmission 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

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 the Information Object 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 note about the IOA address.
  The I/O tag with an address starting with %IGNORE will be ignored.
• The input I/O tags must have corresponding types (Ai, Ci, Di, Qi) for received ASDU, see table 1.
• For a particular type of output I/O tag (Ao, Dout, Co), it is necessary to set an ASDU type that should be used, see Table 1 and Table 2.
• It is possible to configure one input I/O tag and multiple output I/O tags on the same address, 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 results in a new value written to the I/O tag M1. Writing to the I/O tags M2, M3 results in a new value to the I/O tag P2 on the partner's side.
• If the Destination Column is configured, then the values received from the address configured at the I/O tag and above are stored in the corresponding items (e.g. objects with addresses 10, 11, 12 ... according to the number of rows of the destination structure).

Kotva
tell_cmd tell_cmd

Tell commands

...

Kotva
literatura literatura

Literature

...

• Ver. 1.0 – December 15th, 2004
• Ver. 1.1 – February 21st, 2011
• Ver. 1.2 – November 16th, 2023 (support for the Destination Column)

Info
title Related pages:
Communication protocols

...