História stránky

...

The protocol is a modification of the protocol the IEC 870-5-104 protocol working on the basis of TCP network communication. The protocol has been modified specifically for redundant communication with the Siemens Sinaut Spectrum system. It supports the balanced mode and both active and passive 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.

...

• 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 one line, a different ASDU address must be defined.
  

  Kotva
  NOTE_ASDUADDR NOTE_ASDUADDR

  Note: Because of the Sinaut data model, the low and high address bytes are 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
  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 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 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.
  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.

...

Note: The individual bites Individual bits of the quality byte (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), FLB B (bit 1) .. FLH H (bit 7).
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 bits 0..4, FLFF=CY bit, FLGG=CA bit, FLHH=IV bit

Moreover:

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

Kotva
pozn1 pozn1

* - T-bit of the value of these ASDUs is mapped to the FI I flag, a number in range -64 .. +63 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), FLB B (bit 1) .. FLH H (bit 7), 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)

...

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

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

• writing Writing is considered successful , if there is a packet with RSN confirming the SSN packet with the write command is received.
• writing Writing is considered finished , if there is a response with CauseOfTransmission=7 [Activation Confirmation] and/or 10 [Activation Termination] is received. Success/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 a TCP/IP-TCP Redundant type communicates with two redundant Sinaut partners, one of them is HOT, the other is STANDBY.
• Communication with each of the partners is performed through via two redundant networks (i.e. two TCP connections are created for each Sinaut, so altogether there are four TCP connections by every D2000 KOM process).
• Only the HOT partner (D2000 or Sinaut) is allowed to send new values and reply to ASDU 100 [Interrogation Command]. Having established the connection, the STANDBY partner only sends confirmations (S-frames) and test frames. The However, the STANDBY partner may also send ASDU 100 [Interrogation Command].
• Each partner communicates to the other participant communicates with a partner through a single TCP connection. It sends new values, command confirmations, ASDU 100, and replies to ASDU 100 through this connection. The second connection is not used (except for sending test frames) and it is only used when a failure on the first connection is detected.

...

• In the active mode, the D2000 KOM process connects to specified TCP ports. It sends a StartDT Act U-frame to each of the ports and waits for a StartDT Con 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 a StartDT Act U-frame and sends a StartDT Con reply.
• Further communication is completely symmetrical. 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.

...

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

Forced sending of Interrogation Command or Counter Interrogation Command: If a station is not in the simulation mode and the communication is not disabled (the Parameters tab of the Station type object), the 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, so it must comply with the rules of server protocols.

...

• 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, to which the 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 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 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.
• 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 2,1 is the same as 513 (2*256 + 1). See 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

...

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

Kotva
merany_bod merany_bod

IO tag configuration

...

• 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 a note about the IOA address.
  The I/O tag with an address starting with %IGNORE will be ignored.
• The input Input I/O tags must have corresponding types (Ai, Ci, Di, Qi) for received ASDU, see the see table 1.
• For a 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 see Table 1 and table 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.
• 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

...

• 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

...