História stránky

...

The protocol is a modification of the protocol IEC 870-5-104 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 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

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

...

• 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 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 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 (bit 0.bit), FLB (bit 1.bit) .. FLH (bit 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 bits 0..4, FLF=CY bit, FLG=CA bit, FLH=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 FI 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 (bit 0.bit), FLB (bit 1.bit) .. FLH (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):

...

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 (bit 0.bit), FLB (bit 1.bit) .. FLH (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 FLA .. FLH are set according to the bites bits of the "status" byte.

When sending commands (ASDU 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
• write writing is considered finished, if there is a response with CauseOfTransmission=7 [Activation Confirmation] and/or 10 [Activation Termination]. Success/Unsuccess failure depends on the setting of the P/N bite in received CauseOfTransmission.

Redundant communication with Siemens Sinaut system -  Basic features:

• One communication line of CP Redundant type 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 two redundant networks (i.e. there are created two TCP connections are created for each Sinaut, together so altogether there are four TCP connections).
• 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. The STANDBY partner may also send ASDU 100 [Interrogation Command].
• Each partner communicates to the other just through one 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 StartDT Con as reply.
• In the passive mode, the process D2000 KOM waits on a specified TCP port (see the parameters SP, SH). When the clients are connected, the process waits for an a StartDT Act U-frame StartDT Act, and sends 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 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 for them, the communication line will be disconnected (closing communication sockets). If the simulation mode is not enabled and communication is not disabled for at least one station (the tab Parameters of object of Station type), the line will be reconnected (and Interrogation Command eventually Counter Interrogation Command will be send to the station). Then after enabling each next station, there is send an Interrogation Command or Counter Interrogation Command to the station; see the next point.

...

...